fix: refactor sign in methods

What kind of change does this PR introduce?

Split up the signIn method into their respective use cases (e.g. password sign-ins, passwordless sign-ins, oauth sign-ins)
Removed signIn with refreshToken because the getSession() method already handles that and it seems incorrect to "sign-in with a refresh token" when the user is just refreshing the session
Removed sign in with oidc capabilities since we need to rework the implementation in gotrue first

To-Dos

[x] Get tests to pass
[x] Captcha token field in gotrue should be renamed from hcaptcha_token to captcha_token for generalisability
[x] ~Add a is_new_user field in the response for the passwordless and oauth endpoints in gotrue so that the developer can tell if it was a new user that signed up or not~

hi @kangmingtay, I can see you added the types for signInWithPasswordless(), but not the implementation. Is that something you plan on adding later?
Great work by the way.

hey @vbylen, you should use signInWithOtp() instead, it uses the SignInWithPasswordlessCredentials and is the method you want to use for passwordless sign-ins. We won't be adding a signInWithPasswordless() method for now.

hey @vbylen, you should use signInWithOtp() instead, it uses the SignInWithPasswordlessCredentials and is the method you want to use for passwordless sign-ins. We won't be adding a signInWithPasswordless() method for now.

Thanks for clarifying!

I’m just throwing this here as I happened to be here, the new release notes for v2 use passwordless and not OTP. Customers are encountering.  I’ll try and get a issue generated soon.

thanks for catching this @GaryAustin1! i've made a PR to amend it already

@kangmingtay the refresh token login is used by the React Native example to work with Magic Links, what's the right way to do this now that you removed this functionality? Thanks!


Running azd up on an existing ai studio resource fails

Describe the bug
Running azd up on an existing ai studio resource fails
To Reproduce

run azd up on this template https://github.com/Azure-Samples/contoso-creative-writer
once it completes, run azd up again
it will fail on creating ai endpoints in ai studio.

Expected behavior
it skips creation of existing endpoints and moves to next step

azd version? @cassiebreviu

Tracking this - seeing the same error in Contoso Chat sample (aitour-fy25 branch) which worked previously.
Deployment details indicates Status was "BadGateway"
Status message was:
{
    "status": "Failed",
    "error": {
        "code": "UserError",
        "message": "Create workspace connection failed.",
        "details": []
    }
}

I believe the errors you are referring to are related to the Connections created for AI services such as the following:

Azure Open AI Connection
Azure Search Service Connection
Azure Content Safety Connection

The error message returned from the ARM/Bicep deployment are the following:
{
    "status": "Failed",
    "error": {
        "code": "UserError",
        "message": "Create workspace connection failed.",
        "details": []
    }
}

This point to an issue with the AI services resource provider and not an azd issue.  If the connection metadata requirements have introduced a breaking change then the templates will need to be updated.

Following up on the AI Services side. Closing here. Thanks!


Example one-liner input for GPT2?

@e4c6 if you’re still looking for example data to use with megatron you can download some data we use for testing. It’s about 500MB.
https://deepspeed.blob.core.windows.net/megatron-data/webtext.tgz

Thank you Jeff, that's perfect.


BHM target selection issues - transform target photometry onto the SDSS griz psfmag system

Several BHM cartons currently derive griz photometry from non-SDSS catalogue - these are labelled as such via the 'optical_prov' field returned by Carton.build_query().
However, the new goal is now to transform all griz photometry onto a common system (equiv. to sdss_psfmag)
Reminder - these griz mags are only used to judge the SN2 vs mag relation during observations - so the main goal here is to remove systematic biases.
BHM cartons potentially requiring transformations to griz:

bhm_spiders_agn_lsdr8
bhm_spiders_agn_efeds_stragglers
bhm_spiders_agn_gaiadr2
bhm_spiders_agn_sep
bhm_spiders_agn_ps1dr2
bhm_spiders_agn_skymapperdr2
bhm_spiders_agn_supercosmos
bhm_spiders_clusters_lsdr8
bhm_spiders_clusters_efeds_stragglers
bhm_spiders_clusters_ps1dr2
bhm_csc_boss_dark
bhm_csc_boss_bright
bhm_csc_apogee
bhm_rm_core
bhm_rm_known_spec
bhm_rm_var
bhm_rm_ancillary

This also needs to be done (at higher priority) for the ops_std_boss_lsdr8 carton

Now implemented in all cartons that need it - a larger fix than anticipated.
See dedicated wiki page:
https://wiki.sdss.org/display/BHM/BHM+magnitude+transformations+for+v0.5
I decided in the end that bhm_rm_* cartons had photometry from too many different sources to do this properly, and so have just favoured sdss photometry where this exists.
I will close this issue when last cartons have been re-run

Closing this issue now that bhm_v05_4 has been merged into main


Some issue at Organization page

Hello again, synthtech.
I found some bugs at Org page.
1: Organization visibility popup at https://github.com/orgs/{OrgName}/people
when hover popup items, I think strong string color should be changed to white. (e.g. Public/Private)

2: List items and account dropdown at https://github.com/orgs/{OrgName}/people and https://github.com/orgs/{OrgName}/teams
List items and account dropdown has z-index issue.

Fixed in 2684081 and 10a9ec3

Seems fixed perfectly! Big thanks!


Multi GPU Error

训练时, 使用单个GPU 不会报错,但指定多个GPU,就会报错:
使用的命令: CUDA_VISIBLE_DEVICES=2,3,4,5,6,7 python tools/train.py -f exps/example/yolox_voc/yolox_myvoc_s.py -d 6 -b 96 -o -c /path/to/the/pretrained/weights
RuntimeError: Caught RuntimeError in replica 1 on device 1.
Original Traceback (most recent call last):
File "/data4/wensongli/anaconda3/envs/torch1.7/lib/python3.8/site-packages/torch/nn/parallel/parallel_apply.py", line 61, in _worker
output = module(*input, **kwargs)
File "/data4/wensongli/anaconda3/envs/torch1.7/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/data4/wensongli/projects/YOLOX_train/yolox/models/yolox.py", line 34, in forward
loss, iou_loss, conf_loss, cls_loss, l1_loss, num_fg = self.head(
File "/data4/wensongli/anaconda3/envs/torch1.7/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/data4/wensongli/projects/YOLOX_train/yolox/models/yolo_head.py", line 168, in forward
output, grid = self.get_output_and_grid(
File "/data4/wensongli/projects/YOLOX_train/yolox/models/yolo_head.py", line 234, in get_output_and_grid
output[..., :2] = (output[..., :2] + grid) * stride
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:1 and cuda:0!

are you slove the problem?

What was the solution?


setting a random seed to generate figures (mostly for figure4, but doesn't hurt to have for others, too)

I tried setting that inside the cenGen() and regGen() in figure 4, but didn't work. I tried placing it just on the top of figureCommon, didn't work either.
If I have to place it where the random values are being generated, maybe I should go inside lineageTree. @aarmey

Try using this in genFigures.py:
https://docs.scipy.org/doc/numpy-1.15.1/reference/generated/numpy.random.seed.html
https://github.com/meyer-lab/tHMM/blob/549a7ad724913e6048a6284f3555d49dbbb52db2/genFigures.py#L11


Add  testcases for reference test vectors

Add testcases to tb_md5_core for reference test vectors.

Reference test vectors was added a while ago. Closing this.


Upgrade node to 8.11.2

Coverage remained the same at 57.65% when pulling 4fcbfb7adcacfcd5fa2bdfd3cdb85454bbfab6f2 on update-node into c3a0f90cc2ac14685f12e13c32701b857def2ee5 on master.


If I'm a new user, I want tips showing all the new features in Graph Explorer

In the new Graph Explorer, we have new features, they are:

Permissions Tab
Auth Tab
Adaptive cards,
Graph Toolkit
Code Snippets
All samples together
Expand response header
Hide/show sidebar component.

A new user may miss out on all these new features or struggle finding things in the new version, for this reason, there is need to add tips for new users showing them around the new Graph Explorer.
AB#7488

@bettirosengugi
I'd like to understand how we would define what a new user is and when the user is no longer new. Currently we do not store any user data.

UPDATE This would be a great component to utilize Feature flags! We can set a time window feature to filter it to two weeks. Then after two weeks the timer can switch off the new feature display
@adhiambovivian


Why there is no c/c++ code

Hello,
Thank you for reaching out. At this moment, we have not provided a C/C++ implementation. We appreciate your feedback and will consider it for future updates.


README.md: Update build instructions

The 'make binaries' command requires the existence of ibc.a.  On Fedora this file is included in the glibc-static package.  If this is not installed the user will get the error '/usr/bin/ld: cannot find -lc'.  On Ubuntu this is not an issue.  The README was updated to reflect this dependency.

Looks good but you need to sign the CLA. Follow the details link.

I just signed the CLA.  Is there a way I can rerun the checks?

Seems to have resolved maybe by repush.

Can you squash the commits?

All done

LGTM

@14rcole Nice work, hope school is going well.


Add custom margins

I would like to be able to add margins for the top, bottom, left, and right side of the page. The images should respect the margins but NOT the background.  It seems the thumbnails are right up to the left and right edges of the paper and I would like to put a 40px margin on the left and right.

Um, margins for what?


Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.

I have this warning when running react-svg from create-react-app boilterplate.
Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.
Could you consider replacing this by below in src/index.js?
import React, { Component, PropTypes } from 'react'
to
import React, { Component } from 'react'
import PropTypes from 'prop-types'
Thanks in advance

Resolved with #23, just waiting for a maintainer :+1:

@tanem do you have an idea of when you might be able to review the two open pulls? i don't really wanna fork this, but i understand if you guys are too busy

Much needed update indeed ! This warning is not cool to look at 😄

Hey all, sorry for the delay, been tied up on other things. Just looking at that PR now.

Just pushed 2.1.20, should be all good now 👍


Add onStatusBarTapped event callback on Scaffold

When you tap the status bar on iOS, the PrimaryScrollController scrolls to the top. However, when a Scaffold contains multiple scrollable widget, we cannot controller which scroll controller to animated.
This pull request introduces an onTapBarTapped callback function in the Scaffold. With this callback, you can customize the behavior when the status bar is tapped, such as scrolling to the top with your specific scroll controller or performing other actions.
@Piinks
As we discussed on Discord, we don't need to implement this feature for Android.
MitchellGoodwin said we need to test it works properly, but we don't need to add test case because this test already implemented on https://github.com/flutter/flutter/blob/master/packages/flutter/test/material/scaffold_test.dart#L510
And we need to followed up PR that separate Navigator and PrimaryScrollController, but we still need this feature (onStatusBarTapped). Because if there are multiple scrollable widgets (i.e. TabBarView, IndexedStack), develop may want to implement event.
Fixes #85603
Pre-launch Checklist

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[X] I read the Tree Hygiene wiki page, which explains my responsibilities.
[X] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[X] I signed the CLA.
[X] I listed at least one issue that this PR fixes in the description above.
[X] I updated/added relevant documentation (doc comments with ///).
[X] I added new tests to check the change I am making, or this PR is test-exempt.
[X] I followed the breaking change policy and added Data Driven Fixes where supported.
[X] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Hi @Piinks , I would appreciate it if you could let me know how do you think about this idea!

Hey @SuhwanCha would you like to continue working on this change?


When not passing an object the parameter sets the description rather than the template

Here's my configuration:
const meta: Meta<typeof ButtonComponent> = {
  title: 'lib/ButtonComponent',
  component: ButtonComponent,
  parameters: {
    slots: {
      default: 'Click Me',
    },
  },
  args: {},
}

But when I view the story there is no slot.
When I view the docs page I see the parameter description is set to Click Me, but according to the docs and what would probably be most useful, when passing a string to a slot it should set the template rather than the description.

Ah sorry I misread the documentation


momentumbots api returns little results

The momentumbots API that lists the search results of momentum tokens returns little results and at times none. Using this ticket to capture some searches. Note that this could either be expected due to market conditions or a bug somewhere in the code.
even searching for https://momentumbots.palomachain.com/?dex=uniswap_v2&lag_return=0&daily_volume=0&vol_30=0&market_cap=0 only returns one token and at times none
Separately or related
<IP_ADDRESS> - - [18/May/2023 19:40:26] "POST /get_high_returns HTTP/1.0" 500 767
Traceback (most recent call last):
  File "/root/.cache/pypoetry/virtualenvs/trading-bots-Fx44JTns-py3.10/lib/python3.10/site-packages/bottle.py", line 876, in _handle
    return route.call(**args)
  File "/root/.cache/pypoetry/virtualenvs/trading-bots-Fx44JTns-py3.10/lib/python3.10/site-packages/sentry_sdk/integrations/bottle.py", line 140, in wrapped_callback
    raise exception
  File "/root/.cache/pypoetry/virtualenvs/trading-bots-Fx44JTns-py3.10/lib/python3.10/site-packages/sentry_sdk/integrations/bottle.py", line 130, in wrapped_callback
    res = prepared_callback(*args, **kwargs)
  File "/root/.cache/pypoetry/virtualenvs/trading-bots-Fx44JTns-py3.10/lib/python3.10/site-packages/bottle.py", line 1759, in wrapper
    rv = callback(*a, **ka)
  File "/root/app/momentum_cache_refresh/app.py", line 25, in get_high_returns
    df = momentum_scanner_intraday.get_high_returns(
  File "/root/app/momentum_cache_refresh/momentum_scanner_intraday.py", line 73, in get_high_returns
    vols = gecko.exchanges(dex)
  File "/root/app/momentum_cache_refresh/gecko.py", line 29, in exchanges
    for ticker in get("exchanges", dex)["tickers"]
KeyError: 'tickers'

That last bit means it's straight from coingecko's API.

This is fixed by https://github.com/VolumeFi/trading-bots/pull/22

fixed with #22


make fields optionals and implement super field

so, you want to add the "super" property to master? I don't mind, but why?

it was already implemented in master.


[Minor] Fix unpaired quote in message pattern

Why are the changes needed?

Remove the existing single quote in message format which causes the argument 0 is not used
A single quote itself must be represented by doubled single quotes '' throughout a String. https://docs.oracle.com/javase/8/docs/api/java/text/MessageFormat.html

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

PS: This issue is scanned and reported by Qodana on local IDEA 2023.2.

The oracle docs you linked seem invalid.

The oracle docs you linked seem invalid.

Oops. Updated with a correct link.

Thanks, merged to master(1.8.0) and 1.7.2.


i18n(ko-KR): update configuration-reference.mdx

Description (required)

update configuration-reference.mdx
#9933

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ko
reference/configuration-reference.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


pkg/ciliumidentity: Fix cell config

ciliumidentity cell config struct has been introduced in a previous commit to enable the management of Cilium Identities from the operator. However, an instnace of the new config type has not been registered into the cell with cell.Config. This makes the cell not usable, since when it is added into the operator hive (to be done in a future commit), the operator is not able to startup correctly anymore:
level=error msg="Invoke failed" error="missing dependencies for function \"github.com/cilium/cilium/operator/pkg/ciliumidentity\".registerController\n\t/go/src/github.com/cilium/cilium/operator/pkg/ciliumidentity/controller.go:92:\nmissing type:\n\t- ciliumidentity.config (did you mean to Provide it?)" function="ciliumidentity.registerController (pkg/ciliumidentity/controller.go:92)"
time=2024-09-03T13:53:39Z level=info msg=Stopping

Moreover, since the config struct field EnableOperatorManageCIDs does not match exactly the related config option name
operator-manages-identities, a mapstructure tag should be added to the field, so that the hive can correctly load the option value into the struct.
Fixes: 78463ff993 ("pkg/ciliumidentity: Use cell flag for EnableOperatorManageCIDs")

/cc @ovidiutirla

/test

PTAL @dlapcevic


[Multi SDFG, Fortran] Prune redundant uses, which in turn allows pruning redundant objects more aggressively.

Please add a test to check the functionality. LGTM otherwise

Thanks for pointing out. Turns out there was indeed a missing case.

Have you also checked how it works when applied to ECRAD? (just as a side-note)

Have you also checked how it works when applied to ECRAD? (just as a side-note)

Yeah, now it fails at a different place than GET_COMMAND; I guess that's a progress.


does upgrade 1.9 of vscode broke the plugin

Hi.
Today I upgrade Astyle to 2.06 and vscode to 1.9.And evidently either of them broke the formatter.Then I switch astyle to old 2.05,the problem is still.
Issue:

It seems somethings changed in vscode 1.9. I'm looking for the problem now.

vscode 1.9.1 fixed this

I have the same problem with VSCode 1.9.1 and astyle 3. An empty lined is added to every other line in the file. This gets repeated every time formatting is invoked.

The problem still exists, and it seems to be related to files with LF line endings, at least on Windows. CRLF works fine. Tested using VS Code 1.12.2 and AStyle 3 on a Windows 10 machine.

Hi @strike-zero,
Can you try add line ending options in astylerc?
--lineend=windows  OR  -z1
--lineend=linux    OR  -z2
--lineend=macold   OR  -z3
Force use of the specified line end style. Valid options
are windows (CRLF), linux (LF), and macold (CR).
thanks

@welkineins
I tried with all of the line ending options with the same results. Unless you change the end of line sequence from LF to CRLF in VS Code itself, the bug will occur.
Also one thing to note from the AStyle docs:
"When redirection is used on Windows the output will always have Windows line ends. This option (referring to line ending options) will be ignored."

Seems need to be reopen?

I have the same problem

Environment
version

Visual Studio Code version
1.13.1

Astyle extension version
0.6.2

Astyle binary
3.0.1

Windows OS
Win10 x64

Hi guys,
I finally have time to update the way to handle newline issue. Please help me to test if it's fix on 0.7.0. Hopes it does!
Thanks.

I gave it a quick test, and unfortunately it's still not fixed. I have also tried with all the line ending options.

Hi @strike-zero,
Thanks with the quick test. But sorry I didn't fix it in 0.7.0.
I take other steps trying to fix the issue in 0.7.1.
Can you help to run the test again?
Thanks

Happy to report that the issue is finally fixed!
Thank you for the quick update.


lib/options: Add mkPackageOption

Motivation for this change
Many modules have the option to declare a different package than the default one. These options almost always follow a similar format. This is replicated here.
Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

O K.
I did a new implementation… it’s kinda OK, I think?

I think this works

OK, I think this is a reasonably convenient function.

Generally I feel indifferent to this function... but I do have one request: Please add documentation stating what overlays are and how they often achieve the same result. I find a large number of PRs which add a package option only exist because the author isn't familiar with overlays.

@aanderse overlays can be used for many package options, but probably not for all of them. package options are quite useful in container situations where you want one version of the package in a container and another outside of it without the overhead of instantiating nixpkgs multiple times, for example.

@aanderse overlays can be used for many package options, but probably not for all of them. package options are quite useful in container situations where you want one version of the package in a container and another outside of it without the overhead of instantiating nixpkgs multiple times, for example.

I completely agree. And even in the scenario where overlays can be used it can still be desirable to include a package option. But let's not lose this opportunity to include some documentation which may teach users something valuable... right?

agreed! overlay docs would be nice to have as well. :)

@aanderse Overlays can slow down building your entire system because the package is replaced everywhere, not just in user-facing conditions. (i.e. packages that depend on it also use the other version in their dependencies)

Is the documentation autogenerated from the comment or does a doc file need updating as well?

documentation isn't autogenerated from comments unfortunately, it lives in nixos/doc/manual as a set of markdown files. see eg https://nixos.org/manual/nixos/stable/index.html#sec-writing-docs-building-the-manual on how to deal with those :)

just looking at the signature again and thinking of how it'd be used, as it stands now it doesn't feel like it'd be a great improvement over the current verbosity. you'd still have quite a block:
package = mkPackageOption {
  name = "Package";
  inherit pkgs;
  default = "package";
};

this would generate the defaultText you wouldn't get for free otherwise of course, but it's still a bit too much to call it "convenient". maybe if it were
package = mkPackageOption pkgs "Package" {
  default = "package";
};

don't know, honestly. maybe attacking user and group options first would be better to establish a pattern of how these things could look and what they'd do. :thinking: any thoughts?

@pennae I implemented that

No, I haven’t found precisely where I should put this in the docs
Does nixpkgs recommend a nix formatter? I have nixfmt setup to auto-format on save usually and it messes up all the files…

I was searching through ^/doc/functions/library, and there’s attrsets.xml, but nothing else… and ^/doc/functions/library.xml says “<xi:include href="./library/generated/…>”, which suggests things are autogenerated.
And I searched through the code for some phrases from the manual about some of the functions and I can’t actually find those exact phrases anywhere.

If you’re talking about the NixOS manual, mkEnableOption isn’t even documented there…

nixos/doc/manual/development/option-declarations.section.md is probably a good place to put docs for this. if you're up to mkEnableOption would fit in there too :) the xml files are generated from md with md-to-db.sh, and from there you can build the manual as usual.
nixpkgs does not currently recommend any formatter (or even format). as long as new code roughly matches what surrounds it things are pretty much fine.

Also, it seems to me that the docs for the nixpkgs library itself in ^/doc/functions/… are auto-generated (at least the part containing the lib.options functions), and I’ve tried to rebuild them by doing nix-shell and then make all, but the built docs (which include mkEnableOption) never change. Do I need to format my comment specially? (I’m pretty sure the comment is the source of the text, no-where else is it to be found)

some documentation is generated, but module documentation isn't (see doc/doc-support/lib-function-docs.nix for details). modules, options, types are written rather than generated at this point.

OK, but how do I get the autogenerated library docs to update? make all inside nix-shell in doc doesn’t work.

(sorry for force push, I forgot to add the comment)

OK so this manual thing evidently isn’t working out. Can anybody help with the formatting/syntax?

the docs texts looks good! :+1:
you can regenerate the xml files with nixos/doc/manual/md-to-db.sh. after that you can build the manual as you had tried, or build it as part of a full system.

OK, I’m now getting a weird error when building the manual.

 (Click to expand) Abridged output of make
…
./man-nixos-version.xml: OK
The component XML files aren't valid as subcomponents.

Trying the whole document just in case.

----

Doing a combined check...
from_md/development/option-declarations.section.xml:114: parser error : Opening and ending tag mismatch: name line 114 and quote
        <name>.</quote>.
                       ^
from_md/development/option-declarations.section.xml:115: parser error : Opening and ending tag mismatch: quote line 113 and para
      </para>
             ^
from_md/development/option-declarations.section.xml:157: parser error : Opening and ending tag mismatch: name line 157 and quote
          description <quote>The <name> package to use.</quote>. You can
                                                               ^
from_md/development/option-declarations.section.xml:160: parser error : Opening and ending tag mismatch: quote line 157 and para
        </para>
               ^
from_md/development/option-declarations.section.xml:321: parser error : Opening and ending tag mismatch: para line 155 and section
      </section>
                ^
from_md/development/option-declarations.section.xml:323: parser error : Opening and ending tag mismatch: para line 112 and section
  </section>
            ^
from_md/development/option-declarations.section.xml:325: parser error : Premature end of data in tag section line 100

^
from_md/development/writing-modules.chapter.xml:187: element include: XInclude error : could not load from_md/development/option-declarations.section.xml, and no fallback was found
./manual-combined.xml: Not valid:
Line 12168:
 12165	 };
 12166	}
 12167	</programlisting>
 12168	 <xi:include href="option-declarations.section.xml"/>
 12169	 <section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="sec-option-types">
 12170	 <title>Options Types</title>
 12171	 <para>
     error: element "xi:include" not
    allowed here; expected the element
    end-tag or element "address", "anchor",
    "annotation", "bibliography",
    "bibliolist", "blockquote",
    "bridgehead", "calloutlist", "caution",
    "classsynopsis", "cmdsynopsis",
    "constraintdef", "constructorsynopsis",
    "destructorsynopsis", "epigraph",
    "equation", "example", "fieldsynopsis",
    "figure", "formalpara", "funcsynopsis",
    "glossary", "glosslist", "important",
    "index", "indexterm",
    "informalequation", "informalexample",
    "informalfigure", "informaltable",
    "itemizedlist", "literallayout",
    "mediaobject", "methodsynopsis",
    "msgset", "note", "orderedlist",
    "para", "procedure", "productionset",
    "programlisting", "programlistingco",
    "qandaset", "refentry", "remark",
    "revhistory", "screen", "screenco",
    "screenshot", "sect1", "section",
    "segmentedlist", "sidebar", "simpara",
    "simplelist", "simplesect", "synopsis",
    "table", "task", "tip", "toc",
    "variablelist" or "warning"

Ok, I think that's done. Should the commits be squashed?

Is there a way to squash non-adjacent/-consecutive commits into multiple separate commits? Or should this just be one commit?

OK, I’ve squashed it down to two commits

Somewhere along the way the typo fix got lost. It’s back.

( I probably just forgot to pull )

Actually, I got an idea for a new feature. Hold on.

I think this could be improved further, I have it on patch-mkPackageOption-extra, but maybe that’s beyond the scope of this pull request or this function.

improvements can always be made if and when they turn out to be helpful :) looks good as is. let's hope users will appear, then we'll have a base of experience for improvements.


Remove containerRuntime config

Describe the issue you're reporting
The containerRuntime setting is used to route the incoming logs using expressions.
The collector works well if we keep this field blank, but we saw in issue that if we change the timezone for contained runtime, it breaks our hardcoded logic.
The CRI-O and contained logs are similar,
<timestamp> <stdout|stderr> <logtag> <log message>
The timestamp is of the rfc3339Nano specification. The PR #817 has updated the timestamp to rfc3339Nano.
I think we can get keep two routers only and remove containerRuntime config:

One for docker
One for cri-o/containerd

Might be worth creating a related ticket in our sibling project https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector so we can influence the community and stay in sync where possible.

Sure, will do

Will work on rolling out PR by today.


Calculate speed of travel

From user research. Not sure how possible this is. Also, does it need to be displayed, or recorded on forms?

Non essential, would be purely for user interest and would not need to be recorded by the app. Users need to know speed of the vessel for different aspects of the survey method, however if the app cannot provide this information, then they can use a hand held GPS.


[Bug]: Huge number of unused variables in the code base

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
while running my frontend i found warnings of  huge number of unused variables
I'd be happy to remove them
Expected behavior
clean codebase
Add ScreenShots

On which device are you experiencing this bug?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Is there an existing issue for this?

[x]  I have searched the existing issues

Describe the bug
while running my frontend i found warnings of huge number of unused variables
I'd be happy to remove them
Expected behavior
clean codebase
Add ScreenShots

On which device are you experiencing this bug?
No response
Record

[x]  I have read the Contributing Guidelines
[x]  I'm a GSSOC'24 contributor
[x]  I have starred the repository

Hello @puneeth072003, Go for it
All the Best

Hii @Trisha-tech I'd like to work on this issue, could you please assign it to me?

@arduvey29 Sorry, I'm working on it.


fix issue where portfolio filled orders doesn't automatically update …

…when user is filled
https://github.com/AugurProject/augur/issues/5812
portfolio filled-orders wasn't updating automatically when user's order gets filled and user is on portfolio page.
to repro:
have 2 UIs open with different users logged in. MM and portis for example.
have user one create order on market and nav to Portfolio page
have second user take the order, should see filled-orders update when order gets filled. Filling an order takes awhile. just FYI.

updated


[SPARK-35173][SQL][PYTHON][FOLLOW-UP] Use DataFrame.sparkSession instead of DataFrame.sql_ctx in withColumns

What changes were proposed in this pull request?
This PR is a followup for both https://github.com/apache/spark/commit/8853f286371bcc1d44762a0a8ed5bf1a40cdbbd5 and https://github.com/apache/spark/commit/88696ebcb72fd3057b1546831f653b29b7e0abb2. There was a logical conflict here:
We should make it use DataFrame.sparkSession instead of DataFrame.sql_ctx
https://github.com/apache/spark/runs/5193146096?check_suite_focus=true
======================================================================
FAIL: test_with_columns (pyspark.sql.tests.test_dataframe.DataFrameTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/__w/spark/spark/python/pyspark/sql/tests/test_dataframe.py", line 484, in test_with_columns
    keys = self.df.withColumns({"key": self.df.key}).select("key").collect()
  File "/__w/spark/spark/python/pyspark/sql/dataframe.py", line 3009, in withColumns
    self._jdf.withColumns(_to_seq(self._sc, col_names), self._jcols(*cols)), self.sql_ctx
  File "/__w/spark/spark/python/pyspark/sql/dataframe.py", line 123, in __init__
    assert not os.environ.get("SPARK_TESTING")  # Sanity check for our internal usage.
AssertionError

Why are the changes needed?
To fix the build, and remove deprecated usage of SQLContext.
Does this PR introduce any user-facing change?
No, it's not released out yet.
How was this patch tested?
CI should test it out.

cc @ueshin @Yikun mind taking a quick look please?

Tests passed
Merged to master.


 Errors from invalid pipeline stage flags are legitimate but the rest seem rather suspicious.
Example errors from dEQP-VK.image.texel_view_compatible.compute.basic.image_load.bc1_rgb_unorm_block.r16g16b16a16_unorm

ERROR: vkCreateImage: usage bit VK_IMAGE_USAGE_STORAGE_BIT is not supported for format VK_FORMAT_BC1_RGB_UNORM_BLOCK with tiling VK_IMAGE_TILING_OPTIMAL. The spec valid usage text states 'If tiling is VK_IMAGE_TILING_OPTIMAL, and VkFormatProperties::optimalTilingFeatures (as returned by vkGetPhysicalDeviceFormatProperties with the same value of format) does not include VK_FORMAT_FEATURE_STORAGE_IMAGE_BIT, usage must not contain VK_IMAGE_USAGE_STORAGE_BIT' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkImageCreateInfo-tiling-00984) (code 0x09e007b0 from IMAGE at Unknown:726)

ERROR: vkCreateImage: The combination of format, type, tiling, usage and flags supplied in the VkImageCreateInfo struct is reported by vkGetPhysicalDeviceImageFormatProperties() as unsupported. The spec valid usage text states 'The combination of format, imageType, tiling, usage, and flags must be supported, as indicated by a VK_SUCCESS return value from vkGetPhysicalDeviceImageFormatProperties invoked with the same values passed to the corresponding parameters.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkImageCreateInfo-format-00940) (code 0x09e00758 from IMAGE at Unknown:771)

These errors are produced when creating a VK_FORMAT_BC1_RGB_UNORM_BLOCK image with (VK_IMAGE_USAGE_TRANSFER_SRC_BIT | VK_IMAGE_USAGE_TRANSFER_DST_BIT | VK_IMAGE_USAGE_SAMPLED_BIT | VK_IMAGE_USAGE_STORAGE_BIT) usage flags and (VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT | VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT_KHR | VK_IMAGE_CREATE_EXTENDED_USAGE_BIT_KHR) create flags.
The validation layer skips checks for VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT and VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT usage if VK_IMAGE_CREATE_EXTENDED_USAGE_BIT_KHR is included in VkImageCreateFlags, but the checks for VK_IMAGE_USAGE_SAMPLED_BIT and VK_IMAGE_USAGE_STORAGE_BIT are always performed. Until a proper support for extended usage validation is implemented, these checks should probably be skipped as well.

ERROR: vkCreateImageView() pCreateInfo->format VK_FORMAT_BC1_RGB_UNORM_BLOCK cannot be used with an image having the VK_IMAGE_TILING_OPTIMAL and VK_IMAGE_USAGE_STORAGE_BIT flags set. The spec valid usage text states 'If image was created with VK_IMAGE_TILING_OPTIMAL and usage contains VK_IMAGE_USAGE_STORAGE_BIT, format must be supported for storage images, as specified by the VK_FORMAT_FEATURE_STORAGE_IMAGE_BIT flag in VkFormatProperties::optimalTilingFeatures returned by vkGetPhysicalDeviceFormatProperties with the same value of format' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkImageViewCreateInfo-image-01014) (code 0x0ac007ec from IMAGE at Unknown:3514)

This seems to happen because the validation layer checks the implicit usage flags inherited from image creation time instead of usage flags from VkImageViewUsageCreateInfoKHR. The latter should override the former if VkImageViewUsageCreateInfoKHR is chained to VkImageViewCreateInfo.
TLDR:

Image usage flags in vkCreateImage are not validated correctly if VK_IMAGE_CREATE_EXTENDED_USAGE_BIT_KHR is used
Image usage flags in vkCreateImageView are not validated correctly if VkImageViewUsageCreateInfoKHR is used

@pppessi, thanks for the report.  We have a TODO in place at the moment and will bump the priority on this issue.

The first will be easy to avoid with the existing work-around which avoids probably- false positives when the EXTENED_USAGE bit is set. The full solution will require an exhaustive search of all compatible formats, unless we can get clever about caching the app's queries.
The second is harder to triage, because the VkImageViewUsageCreateInfoKHR is only allowed to include a subset of the image's creation-time usage bits so can only make the check more restrictive, so the fact we're not traversing the chain currently is probably not the root cause of the false positive.

The linked PR will avoid false positives mentioned in the first part of the issue, and adds support for a chained VkImageViewUsageCreateInfo struct mentioned in the second part.  It's not clear to me whether this actually fixes the errors of the second part.


Feat: Added useHover hook

What's this PR do?
This PR adds useHover hook (issue #94) and a story for ease of review. Since other stories rely on imports from the published packages I suggest reviewing PR as is and changing the import path after that.
@ulises-jeremias @rpmolina

Summary by CodeRabbit
New Feature:

Added a new useHover custom hook in the @nanlabs/react-hooks library. This hook allows tracking the hover state of a target element and provides optional callback functions for hover events.
Introduced an interactive Example component in the playground app to demonstrate the usage of the useHover hook. The component changes its appearance based on hover state and allows toggling of memoization and target type.

Refactor:

Updated the exports in the react-hooks package to include the new useHover module.

@boredcity wow! this pr is amaizing 🔥 I've just requested small changes

I've fixed whatever I agreed with our robotic overlords on :)
Please, @ulises-jeremias, @rpmolina review the changes and see if you agree with the concerns raised by the bot 🙏


adding_icon

[x ] I have tested my component
[ ] I have updated the documentation or there is no documentation needed

Libraries that use the DS (need to merge first)

[- ] BCF Components
[- ] BIMData Components
[- ] Building maker

Repos that use the DS (and that I need to check after libraries have been merged)

[x ] Viewer
[x ] Platform
[ -] SDK
[- ] Marketplace
[ ]- Documentation

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


chore(op-payload-builder): Refactor optimism_payload into smaller, reusable functions

Addresses #10935
This PR refactors the OP block building logic from the optimism_payload function  into smaller methods implemented on the OptimismPayloadBuilder struct.
This change enhances the re-usability of the default OptimismPayloadBuilder logic, which is useful when implementing a custom OP Stack Payload builder.

My mistake, I realized that I had not opened an issue. I opened a new issue just now and linked it in the PR description.
Please let me know what the best direction is for this PR, happy to adjust if there is a better approach!

My mistake, I just realized that I had not opened an issue. I opened a new issue just now and linked it in the PR description. Please let me know your thoughts on the direction for this PR, happy to adjust if there is a better approach!

valid issue! thanks for implementing!

could you please run this against hive also

I ran Hive against these these changes locally and received the following results. It looks like there are some expected failures defined in  .github/assetshive/expected_failures.yaml, is there a preferred output that you would like me to produce?
Also please let me know if there is a workflow or set of commands that I should run to evaluate the results against the expected outcomes.
 # Pass
-  "smoke/genesis" ""
    - Pass
-  "smoke/network" ""
    - Pass
 - "ethereum/engine" "engine-auth"
    - Pass
 - "devp2p" "discv4"
    - Pass
 - "ethereum/engine" "engine-exchange-capabilities"
    - Pass

 # Fail
- "ethereum/rpc-compat" ""
    - 21 tests failed
 - "ethereum/engine" "engine-withdrawals"
    - 18 tests failed
 - "ethereum/engine" "engine-api"
    - 8 tests failed
- "ethereum/engine" "cancun"
    - 12 tests failed
 - "ethereum/sync" ""
    - 1 test failed
 - "devp2p" "eth"
    - 6 tests failed

@emhane Any thoughts on how best to proceed to get this merged in?

I ran Hive against these these changes locally and received the following results. It looks like there are some expected failures defined in  .github/assetshive/expected_failures.yaml, is there a preferred output that you would like me to produce?
Also please let me know if there is a workflow or set of commands that I should run to evaluate the results against the expected outcomes.
 # Pass
-  "smoke/genesis" ""
    - Pass
-  "smoke/network" ""
    - Pass
 - "ethereum/engine" "engine-auth"
    - Pass
 - "devp2p" "discv4"
    - Pass
 - "ethereum/engine" "engine-exchange-capabilities"
    - Pass

 # Fail
- "ethereum/rpc-compat" ""
    - 21 tests failed
 - "ethereum/engine" "engine-withdrawals"
    - 18 tests failed
 - "ethereum/engine" "engine-api"
    - 8 tests failed
- "ethereum/engine" "cancun"
    - 12 tests failed
 - "ethereum/sync" ""
    - 1 test failed
 - "devp2p" "eth"
    - 5 tests failed

it shouldn't be performing worse than the latest run on main, which it seems to do now. on main only the engine tests fail. https://github.com/paradigmxyz/reth/actions/runs/10875392078

After merging the latest changes on main and rerunning hive against this branch, it looks like the result is the same compared to running against reth:latest. Thanks for the help! Let me know if you want me to produce a specific output or this looks good to merge in.

I don't necessarily agree with some decisions in this PR
for example:
this is redundant:
https://github.com/paradigmxyz/reth/blob/668807802b9120343a084963005fbda7ece314f6/crates/optimism/payload/src/builder.rs#L85-L85
all these functions accept &self, when not required.
and I find this a bit harder to read now


Update law

Check this repository to see if it is still up to date

Interview works and word doc appears sufficient- no template, general motion submission.

Interview works and pdf is up to date.


Universal control on macOS Sonoma (14.4.1) stop working when Orbstack is launched

Describe the bug
I love Orbstack and use it regularly! Thanks for making a great replacement for Docker desktop!
I use an iPad next to my Mac and can usually control it using my Mac's keyboard and trackpad via Universal Control. However, with Orbstack 1.5.1, Universal Control stops working as soon as I launch Orbstack. It resumes working as soon as I quit Orbstack (with no other changes made to the system).
To Reproduce

Set up Universal Control between a Mac and an iPad, ensuring it's working correctly.
Launch Orbstack version 1.5.1 on the Mac.
Observe that Universal Control stops functioning, and the Mac's keyboard and trackpad no longer control the iPad.
Quit Orbstack.
Notice that Universal Control resumes working, allowing the Mac's keyboard and trackpad to control the iPad once again.

Expected behavior
Universal Control should continue to function as normal when launching Orbstack 1.5.1.
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.5.1
Commit: 4cfac15e1080617c70eb163966e1cb2009dac1c2 (v1.5.1)
System info:
macOS: 14.4.1 (23E224)
CPU: arm64, 16 cores
CPU model: Apple M3 Max
Model: Mac15,9
Memory: 64 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-04-03T21-24-20.675456Z.zip

Screenshots and additional context (optional)
I also tried turning off proxies in Orbstack network settings but it doesn't seem to many any difference.

Can't reproduce. Does disabling Settings > Network > "Allow access to container domains & IPs" help?

No, that doesn't seem to help.


Add colab notebooks links

Fixes https://github.com/artefactory/choice-learn/issues/172
Add colab links and necessary requirements to example notebooks.
Add colab links to the top of each example notebook in the notebooks directory.
Add a cell that installs necessary requirements (!pip install choice-learn) in each notebook.
Fix minor formatting issues in some notebooks.

Thanks @chicham !


Paging resets to #1 after deleteItem

Hi, I'm not sure if this is intended, but I'm finding that if I delete a row on the last page I get kicked back to page 1. It also happens on this jsfiddle (http://jsfiddle.net/tabalinas/zeLnh4qs/) which leads me to think it's intended behaviour rather than me getting something wrong.
It'd be really nice to stay on the page I'm on, so that the next record can easily be deleted too. Any advice?
(Many thanks for awesome tool by the way)

Returning to the beginning is the default behavior of the delete.
This is mentioned here, for your future documentation needs. Also mentioned is a method of creating a new finishDelete strategy to simple refresh the grid on delete.
I have implemented the documentation suggestion in a fork of your original fiddle, located here. Note both the custom strategy defined at the top of the Javascript, and the configuration of the JsGrid object at the bottom.

@richraid21, your answer is just great!

Thank you so much.


Impement missing core types.

Filing this placeholder issue for the remaining work with core types.

[x] Plane
[x] Array
[x] Dictionary
[x] PoolStringArray
[x] PoolByteArray
[x] PoolVector2Array
[x] PoolVector3Array
[x] PoolIntArray
[x] PoolRealArray
[x] PoolColorArray
[x] enums
[ ] read access arrays
[ ] write access arrays
[x] String

As nical is likely not working on this currently, I'm going to start implementing array accesses, starting with known-repr types:

[ ] Known-repr read/write access (u8, i32, f32, Color)

These should just Deref/DerefMut to plain slices through godot_pool_*_array_*_access_ptr and godot_pool_*_array_size?
godot_pool_*_array_write_access_copy - What? How? That copy constructor doesn't seem to be doing copy-on-write. What's the point of CoW when you can still alias? I don't get these...

[ ] Opaque read/write access (GodotString)

Can Deref to GodotString slices as well?

[ ] Opaque...? read/write access (Vector2, Vector3)

Vectors are defined on the Godot side as opaque but represented here as euclid types. Need to verify if those transmutes really do what they claim.

Need to verify if those transmutes really do what they claim.

Having tests for that (if we don't already have some) would be great. I think in theory this should work for now, but I realized a while ago that all the GDNative C types do not specify alignments and are represented as byte arrays, so they might be unaligned and that might be UB. We could do a read_unaligned and write_unaligned when we change representation, then it should be okay to use.


Add validation for VkExportMemoryAllocateInfo

Changelog:
### Breaking changes
- `ExternalBufferInfo::sparse` was replaced by a `flags` field.

### Bugs fixed
- Added missing validation for `MemoryAllocateInfo::export_handle_types`.

I'm unsure whether this belongs in Bugs fixed or Additions, since we knew this validation wasn't present.

Looks good, thanks!


bump dependencies, fixes build error in gltf 0.11

Trying to install gltf-viewer on Rust nightly 1.41 fails with an error in gltf version 0.11. This bumps gltf and several other dependencies. Left image at version 0.21 (to match the version used by gltf), and leaves glutin at version 0.18 (latest versions do not have an events_loop.poll() method).

Was just running into this issue, thanks for the PR. I hope it gets merged into master.

Thanks, and sorry for the late reply!


Upgrade Rust toolchain to nightly-2024-01-23

Try upgrading Rust toolchain to 2024-01-22, however, regression isn't working yet due to an issue with our assertion override hack.  Related PRs so far:

https://github.com/rust-lang/rust/pull/119869
https://github.com/rust-lang/rust/pull/120080
https://github.com/rust-lang/rust/pull/120128
https://github.com/rust-lang/rust/pull/119369
https://github.com/rust-lang/rust/pull/116672

Resolves #ISSUE-NUMBER
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

Some perf benchmarks regress from success to failure. We should not merge this PR until we fix them.
An example: https://github.com/model-checking/kani/actions/runs/7674225174/job/20918412309?pr=2983#step:13:237

I did a quick research, the loop unwind assertion fails in function: ... My hypothesis is that the change in behavior we are seeing is due to https://github.com/rust-lang/rust/pull/111803 where the threshold for calling nonoverlapping swap changed. Increasing the unwind limit seems to suffice to fix most harnesses. Unfortunately, check_insert_two_concrete harness runs out of memory.


Update lang-swift.js

associatedtype: https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/Generics.html
fileprivate|open: https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/AccessControl.html
Self: https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/Declarations.html
#column|#file|#function: https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/Expressions.html
#colorLiteral|#fileLiteral|#imageLiteral|#selector|#sourceLocation : https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/LexicalStructure.html#//apple_ref/doc/uid/TP40014097-CH30-ID410

I signed it!


Link to release process

Feature Request
Motivation Behind Feature

I think that it would be good for outside contributors to see a direct link to the release process, which we maintainers know has both the tooling and the documentation within https://github.com/apache/cordova-coho.
Feature Description

I think there should be a link to the release process in https://cordova.apache.org/contribute/.
Alternatives or Workarounds

I cannot think of any decent workarounds for this. I can think of a couple possible lame workarounds such as posting this information on somewhere on GitHub.

Might it be intentionally slightly obscure? If not, please feel free to make a PR to change the footer.


front end setup willing to pay

willing to buy a front end for the engine?? and setup ?? willing to pay

My team are working on a frontend for this exchange: http://github.com/testnet-exchange/
You can star our project to motivate us to continue the development!

Look at https://p2pb2b.io/
We provide  frontend and setup of servers and nodes.


V27.1 Homebrew

When I tried to install 27.1 from Homebrew, I hit an error. I noticed the file links to 27.0, so I updated the download URLs to point to 27.1 and changed the class name.
Error: No available formula with the name<EMAIL_ADDRESS>Did you mean<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>or<EMAIL_ADDRESS>In formula file<EMAIL_ADDRESS>Expected to find class TypesenseServerAT271, but only found: TypesenseServerAT270.

Thanks @thedevdavid!


Detect Gzip and convert data to seq

for issue #58 #54

Looks like there are some style errors, no big deal.
Would you mind writing something up that explains the high level approach? Reading through code and want to make sure I understand it.

I will revise my code

Any more updates @ChuyuHsu?

Going to plan on cutting a new release to have SQLite3 support. Let me know if you have time sometime to finish the PR. If you happen to be busy, I can rebase on your changes/commits and finish it up when I get time.

Any updates @ChuyuHsu? If you happen to be too busy, I could work off your branch and merge everything in eventually.

@ChuyuHsu I am planning on finishing up the last few issues targeted for 0.7.0 this week to release sometime next week. Let me know if you still want to work on this. If I don't hear anything back I will locally merge your commits and finish up the remaining work.

Update: working on completing PR for 0.7.0 release next week. Thanks for the great work!
This PR should auto-close when I push your merged commits to master once i am done.

I finished up the PR over the past week and have pushed the result. Thanks for the great work!


Loop-file should support additional filters

At the moment it's possible to filter the filenames returned by a file-loop based on the pattern of the filename. It would be helpful to have the possibility to add additional filters based on creation and  update dateTime but also on size. These filters should be supported by native transformations related to file (or path) and the predicates.
<loop-file path="c:\temp\">
   <filter>
      <predicate operand="value | file-to-size">
        <more-than>30000</more-than>
      </predicate>
   </filter>
</loop-file>

NBi.Core implementation of the three filters is already committed with #486

Beta available at https://ci.appveyor.com/project/Seddryck/nbi/builds/28765756/artifacts or 1.22.0-beta0027


(doc) Add info about new Authenticode signature

Description Of Changes
Add a new section about the updated Authenticate signature that is applied to all official Chocolatey releases.
Motivation and Context
A new certificate has been purchased, since the previous one expired, and we needed to update this section with the correct information.
Testing

[x] I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made

[ ] Minor documentation fix (typos etc.).
[x] Major documentation change (refactoring, reformatting or adding documentation to existing page).
[ ] New documentation page added.
[ ] The change I have made should have a video added, and I have raised an issue for this.

Issue #

Change Checklist

[ ] Requires a change to menu structure (top or left-hand side)/
[ ] Menu structure has been updated

Related Issue
N/A

@AdmiringWorm this is marked as draft, as it won't be merged until the 2.3.0 release happens, but it is ready for a review.  Thanks

@AdmiringWorm thank you for the review, I will merge once the CI build completes.