Submission Team<PHONE_NUMBER>_2313787_2313940_2312995

Brief Policy's Description
Team's submission represents 3 policies to solve the 2D Cutting Stock problem

Policy 1: Best Fit
The Best-Fit method is a memory allocation technique utilized in resource management and operating systems. In order to reduce the amount of memory block that is wasted, it assigns a process to the smallest memory partition that can support it. Through the reduction of fragmentation and free space, this technique guarantees that the memory is used effectively. But its drawbacks induce the necessity to chose the best appropriate block, which increases computational cost, and the possibility of producing tiny, useless fragments over time, which might result in external fragmentation.

Policy 2: Backtracking
The Backtracking algorithm is a method of problem-solving that builds candidates sequentially and scraps a path as soon as it breaks constraints, therefore exploring every potential solution. Backtracking's main benefit is that it effectively reduces the size of the solution space by preventing needless investigation of invalid paths, which makes it appropriate for constraint satisfaction issues. Its performance is mostly dependent on how well the pruning technique works, and its brute-force approach can result in high computing costs for issues with huge search areas.

Policy 3: Column Generation
Column Generation is an optimization technique used to solve large-scale linear programming(LP) problems effectively. The main idea of this technique is solve the LP restricted master problem(minimize sum of used stock size) by solving sub-pricing-problem. The sub-pricing-problem will find the patterns which have best reduce by dual value( from master problem) then put it into the master problem. In the policy, we used dynamic programming technique to solve the sub-pricing-problem.

The commits of team members:
Nguyễn Triều Vĩ - 2313940: Code and optimize Best-Fit, Backtracking
Lê Đức Tài - 2312995: Code and optimize Column Generation
Kiều Chung Tú - 2313787: Check value and evaluate result
Trần Đức Mạnh - 2312035: Do research, assist in check value
Result
Environment = 50
Best-Fit :                   Avg Time =  9.8s    Avg Filled Ratio = 0.318    Avg Trim Loss = 0.362
Backtracking            Avg Time =   1.1s     Avg Filled Ratio = 0.157    Avg Trim Loss = 0.353
Column Generation Avg Time = 69.1s    Avg Filled Ratio = 0.152    Avg Trim Loss = 0.265

Please revise the PR in Dec 16. Otherwise, your group will get 0 score for code.


Safe Browsing Lookup API

https://developers.google.com/safe-browsing/lookup_guide
Which params should be passed into discovered_api for getting of Safe Browsing Lookup API?
[20] pry(main)> client.discovered_api('safebrowsing', 'v3.1')
Google::APIClient::ClientError: Not Found
[22] pry(main)> client.discovered_api('safebrowsing', '3.1')
Google::APIClient::ClientError: Not Found

and etc raises the same error.

That API isn't supported by any of the API clients. It doesn't conform to the conventions used by the other APIs.

:( Thanks!


Add declaration for liq_set_speed

Needed for the upcoming libvips 8.12.

Hey!
I was in the middle of reworking the build, so I added the method right there.
Also, I created a PR to libvips https://github.com/libvips/libvips/pull/2542, so we hopefully won't need these dirty hacks anymore :)
Thanks anyway!


bind git_repository_set_workdir

I need this for my project. Please let me know if there's anything I should change!

Thanks!


Review survey descriptions to ensure that they are indeed descriptive

Especially for ResearchKit -- we'll want better descriptions!

[ ] About Me
[ ] About My Family
[ ] Additional Information About Me
[ ] My Health Conditions
[ ] My Interest in Research
[ ] My Quality of Life
[ ] My Risk Profile
[ ] My Sleep Apnea
[ ] My Sleep Apnea Treatment
[ ] My Sleep Pattern
[ ] My Sleep Quality

@krand7 @remomueller OK -- I made some revisions and posted them above. I left the boxes unchecked in case you want to use those to indicate the change was made in the database. I don't know if these actually count as "descriptive" in all cases, but I would be fine fielding other suggestions/edits now or later. I'm particularly interested in how these will look/feel in the mobile app.

Thanks, changes have been made!


Update README.md

Corrected a few minor typographical errors and updated some of the English text to be more clear.

Coverage remained the same at 96.387% when pulling afc42f5d5b4627feb8a358bf4e0d914f4b450860 on tonedef71:patch-1 into 05b77e671465873a745b81b16e163d2f7e627387 on onelogin:master.

Thanks!


Maintainer team wanted for looking after pkgsStatic

It would be great to have pkgsStatic (or pkgsSharedStatic) a little better cared for in nixpkgs, see https://github.com/NixOS/nixpkgs/pull/89425, to stop things constantly bitrotting, breakages in pkgsStatic would have to block channel updates, but for this, there would need to be some people willing to maintain this package set.
I'm willing to be part of this team, would anyone else be willing?
If the burden of keeping pkgsStatic not breaking is too much, then this doesn't have to continue, but I think it's worth trying.

cc @matthewbauer @Mic92

@nh2 interested?

I am interested

Aside from a team it is important to decide what packages are considered blocking and should be built by Hydra.
pkgsStatic is listed in the RFC as Tier 4 (x86_64-linux, gcc+musl — static). To upgrade to Tier 3 we could make the stdenv blocking. To go to Tier 2, we need to start building a lot more on Hydra, at which point we need to consider resources.
So, what packages to build, and what to block on?
cc @7c6f434c

Aside from a team it is important to decide what packages are considered blocking and should be built by Hydra.

It's not really aside from a team. Anything above Tier-4 assumes ability to reasonably quickly find people who can investigate breakages…

pkgsStatic is listed in the RFC as Tier 4 (x86_64-linux, gcc+musl — static). To upgrade to Tier 3 we could make the stdenv blocking. To go to Tier 2, we need to start building a lot more on Hydra, at which point we need to consider resources.

If I am cc-ed as RFC-0046 specialist, I would like to remind that Tier-3 does not assume any channel blockers. Also, to claim full Tier-3 we need a team if only to understand what works and what doesn't. libX11 missing symbols needed by rev-deps doesn't sound compatible with «popular packages mostly work» to me, to be honest.
I think right now the static builds are actually close to Tier 3 both in Hydra support and impact tolerance, even if the platform seems to be in a shape closer to Tier-4 package-wise. I find it perfectly fine as long as nobody is specifically annoyed by the static-build-related changes. And of course there are some general benefits of having at least something static work.

I'm up for participating in such team, mainly for a pkgsSharedStatic as suggested.
I think build automation is important, and I could chip in another 30 EUR/month Hetzner build server from the extra funds that my static-haskell-nix OpenCollective provides (which is targeted at static Haskell builds, but to do them I need a healthy pkgsSharedStatic equivalent).

Maybe it could start with "ensuring when someone fixes a package, it does not regress"

I think that no-regressions doesn't even apply to The Tier-1 Platform…

I was more thinking of a notification on regression, like the emails hydra used to send.

I will pass on this one. I am not using pkgsStatic actively to recognize breakages.

So, what packages to build, and what to block on?

Most of the work in fixing these packages seems to stem from bespoke build systems used by packages. Packages which use well understood build systems seem to fare much better, for example Haskell package. Standard usage of autotools and CMake also seem to cope well. Perhaps to get a good bang-for-our-buck the dependencies to build CMake project, Haskell packages and sensible autotools projects would be a good start. I don't know much about other packaging ecosystems in nixpkgs, but I suspect that if we get one Rust package building then the rest probably fall out, similar for other languages maybe,

I was more thinking of a notification on regression, like the emails hydra used to send.

Where would be the best place to start on this? Alternatively is it possible to use github issues for this, i.e. the build failure triggers the creation of an issue in which the interested parties are @-mentioned?

mainly for a pkgsSharedStatic as suggested

@nh2 I believe that the closest we have at the moment is in the static-haskell-nix repo, what would it take to get pkgsSharedStatic in nixpkgs?

I was more thinking of a notification on regression, like the emails hydra used to send.

Where would be the best place to start on this? Alternatively is it possible to use github issues for this, i.e. the build failure triggers the creation of an issue in which the interested parties are @-mentioned?

I could think of a github action that is run periodically and just checks hydra. Github actions also have the API credentials to open issues.

I'm happy to help, as I see a lot of use for pkgsStatic/pkgsMusl for building embedded and docker images using nix

hi, yeah, just found this issue but have been going through a number of things trying to get pkgsMusl working again for essentially the same set of packages in release-small. so i'm interested in this and working on it, i guess.

hi, yeah, just found this issue but have been going through a number of things trying to get pkgsMusl working again for essentially the same set of packages in release-small. so i'm interested in this and working on it, i guess.


Multi-line prompt appears to function incorrectly

I'm attempting to create a multi-line prompt by using a newline character in the argument to Editor::readline, e.g. readline("foo\n> ")
I expected this to produce
foo
>

but it is instead producing
foo
   >

Is this a problem with rustyline, or am I doing something incorrectly?

Fixed in master


crash if x,y have not the same number of elements

Hi,
I have a crash if "x" and "y" have different sizes I got for instance
xp=jnp.linspace(-1.,1.,20)  # N
yp=jnp.linspace(-1.,1.,10)  # M

X, Y = np.meshgrid(xp, yp)

def func(x,y):
    return jnp.exp(-0.5*(x**2+y**2))

Z = func(X,Y)
plt.contourf(xp,yp,Z)  #### ici fp MxN

fp = Z.T    # N x M

x_star = jnp.array([-0.5,0.1])
y_star = jnp.array([0.7,-0.7,0.0])

ut.interp2d(x_star, y_star,xp,yp,fp)     # ut is just a link to your code

then
--------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
    [... skipping hidden 1 frame]

File python3.8/site-packages/jax/_src/util.py:219, in cache.<locals>.wrap.<locals>.wrapper(*args, **kwargs)
    218 else:
--> 219   return cached(config._trace_context(), *args, **kwargs)

File /python3.8/site-packages/jax/_src/util.py:212, in cache.<locals>.wrap.<locals>.cached(_, *args, **kwargs)
    210 @functools.lru_cache(max_size)
    211 def cached(_, *args, **kwargs):
--> 212   return f(*args, **kwargs)

File /python3.8/site-packages/jax/_src/lax/lax.py:126, in _broadcast_shapes_cached(*shapes)
    124 @cache()
    125 def _broadcast_shapes_cached(*shapes: Tuple[int, ...]) -> Tuple[int, ...]:
--> 126   return _broadcast_shapes_uncached(*shapes)

File /python3.8/site-packages/jax/_src/lax/lax.py:142, in _broadcast_shapes_uncached(*shapes)
    141 if result_shape is None:
--> 142   raise ValueError("Incompatible shapes for broadcasting: {}"
    143                    .format(tuple(shape_list)))
    144 return result_shape

ValueError: Incompatible shapes for broadcasting: ((2,), (3,))

During handling of the above exception, another exception occurred:

ValueError                                Traceback (most recent call last)

     55 # Using Wikipedia's notation ([https://en.wikipedia.org/wiki/Bilinear_interpolation)](https://en.wikipedia.org/wiki/Bilinear_interpolation)%3C/span%3E)
---> 56 z_11 = zp[ix - 1, iy - 1]
     57 z_21 = zp[ix, iy - 1]
     58 z_12 = zp[ix - 1, iy]

File /jax/_src/numpy/lax_numpy.py:3544, in _rewriting_take(arr, idx, indices_are_sorted, unique_indices, mode, fill_value)
   3541   return _getslice(arr, start, stop)
   3543 treedef, static_idx, dynamic_idx = _split_index_for_jit(idx, arr.shape)
-> 3544 return _gather(arr, treedef, static_idx, dynamic_idx, indices_are_sorted,
   3545                unique_indices, mode, fill_value)

File/python3.8/site-packages/jax/_src/numpy/lax_numpy.py:3553, in _gather(arr, treedef, static_idx, dynamic_idx, indices_are_sorted, unique_indices, mode, fill_value)
   3550 def _gather(arr, treedef, static_idx, dynamic_idx, indices_are_sorted,
   3551             unique_indices, mode, fill_value):
   3552   idx = _merge_static_and_dynamic_indices(treedef, static_idx, dynamic_idx)
-> 3553   indexer = _index_to_gather(shape(arr), idx)  # shared with _scatter_update
   3554   y = arr
   3556   if fill_value is not None:

File /python3.8/site-packages/jax/_src/numpy/lax_numpy.py:3723, in _index_to_gather(x_shape, idx, normalize_indices)
   3716 for idx_pos, i in enumerate(idx):
   3717   # Handle the advanced indices here if:
   3718   # * the advanced indices were not contiguous and we are the start.
   3719   # * we are at the position of the first advanced index.
   3720   if (advanced_indexes is not None and
   3721       (advanced_axes_are_contiguous and idx_pos == idx_advanced_axes[0] or
   3722        not advanced_axes_are_contiguous and idx_pos == 0)):
-> 3723     advanced_indexes = broadcast_arrays(*advanced_indexes)
   3724     shape = advanced_indexes[0].shape
   3725     ndim = len(shape)

    [... skipping hidden 14 frame]

File /python3.8/site-packages/jax/_src/numpy/util.py:338, in _broadcast_arrays(*args)
    334 if not shapes or all(core.symbolic_equal_shape(shapes[0], s) for s in shapes):
    335   # TODO(mattjj): remove the array(arg) here
    336   return [arg if isinstance(arg, ndarray) or np.isscalar(arg) else _asarray(arg)
    337           for arg in args]
--> 338 result_shape = lax.broadcast_shapes(*shapes)
    339 return [_broadcast_to(arg, result_shape) for arg in args]

    [... skipping hidden 1 frame]

File/python3.8/site-packages/jax/_src/lax/lax.py:142, in _broadcast_shapes_uncached(*shapes)
    140 result_shape = _try_broadcast_shapes(shape_list)
    141 if result_shape is None:
--> 142   raise ValueError("Incompatible shapes for broadcasting: {}"
    143                    .format(tuple(shape_list)))
    144 return result_shape

ValueError: Incompatible shapes for broadcasting: ((2,), (3,))

Well it might be that x,y with different size is not so well defined as
fpi,j = f(x_i, y_j)     does is means to run over all i at fixed j => n_i x n_j values
or when ni=nj then
fpi,i = f(x_i,y_i) only i: over n_i => n_i values
Well... the two use-cases can happen.

@jecampagne
xp and yp can have different size.
x_star and y_star should have same size, since point i coordinate is (xstar[i], ystar[i])!
If you want mesh semantic, you can use meshgrid and flatten output.
x_star = jnp.array([-0.5,0.1])
y_star = jnp.array([0.7,-0.7,0.0])
x_star, y_star = np.meshgrid(x_star, y_star)
x_star = x_star.reshape((-1,))
y_star = y_star.reshape((-1,))

Hum, sounds good :)


Power requrements and config.txt (max_usb_current=1)

is anyone using max_usb_current=1 in their config.txt?  I just read about it.  Supposedly on a Pi 2 or greater it enables 1.2Ah instead of 600mAh on the usb ports.  Since we already have to have a sufficient supply to power the ZWO, I don't see why this should not be enabled for the Allsky.

Just answered my own question.  Looks like it's set at 1.2Ah by default for the pi 3 and newer.  But this is something to look into for Pi2 and older and the zero. (Explains why my ASI120mini didn't even show up with the ZeroW.)

Ah! I didn't know about that option. Thanks for mentioning it. That will probably help a few users with power issues.

This issue is from a much older release of the AllSky software and the issue appears to have been resolved.  If you think it might still be relevant, please test it with the newest version and submit a new issue if needed.  Thanks


add api to merge AST's with extensions

A graphql document might have multiple schema/type/etc. declarations including extensions via the "extend" keyword.
As both parser & lexer are now able to deal with "extend" (#81 ) we should now add an api which enables to merge an extension into the original declaration within the ast.
Example:
before merging->
schema {
  query: Query
}

extend schema {
  mutation: Mutation
}

after merging ->
schema {
  query: Query
  mutation: Mutation
}

The same should apply to object type definitions etc.
Possible use case:
Having this feature implemented opens the way to build schema stitching ontop.
That is, parse two schemas and stitch them together via extensions.
This way one could build a proxy that automagically can stitch together multiple graphql endpoints.

Implemented by #108, thanks to @java-jonas!


JsonPropertyAttribute: CA1507 appears when using .NET 7 / MSBuild 17.5

We have a fairly large solution with multiple projects using Newtonsoft.Json and after upgrading Visual Studio to version 17.5 recently encountered a problem that I would like to bring to your attention and also document it here for others to find.
How to reproduce
The easiest way to reproduce the problem is to have a project targeting .NET 7 that has all .NET Analyzers enabled:
<Project Sdk="Microsoft.NET.Sdk">

    <PropertyGroup>
        <OutputType>Exe</OutputType>
        <TargetFramework>net7.0</TargetFramework>
        <ImplicitUsings>enable</ImplicitUsings>
        <Nullable>enable</Nullable>

        <EnableNETAnalyzers>true</EnableNETAnalyzers>
        <AnalysisLevel>latest</AnalysisLevel>
        <AnalysisMode>All</AnalysisMode>

        <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
    </PropertyGroup>

    <ItemGroup>
      <PackageReference Include="Newtonsoft.Json" Version="13.0.2" />
    </ItemGroup>

</Project>

If this project contains a class like the following,
using Newtonsoft.Json;

namespace ConsoleApp;

internal sealed class DataTransferObject
{
    [JsonProperty("Property")]
    public string? Property { get; set; }
}

the warning CA1507 appears when building:
Warning CA1507 : Use nameof in place of string literal 'Property'

If TreatWarningsAsErrors is enabled, the following error occurs:
Error CA1507 : Use nameof in place of string literal 'Property'

Excerpt from the Microsoft documentation explaining under which circumstances the rule CA1507 fires:

The declared name of the parameter is propertyName and the constant value of the string literal matches the name of a property of the type within which the method or constructor is being invoked.

This is precisely the case for JsonPropertyAttribute used here:
https://github.com/JamesNK/Newtonsoft.Json/blob/57025815e564d36821acf778e2c00d02225aab35/Src/Newtonsoft.Json/JsonPropertyAttribute.cs#L218

It seems that some change within the 17.5 release of MSBuild now makes this rule fire for attributes, which was not the case previously.
Related information:

https://github.com/dotnet/roslyn/issues/67195
https://stackoverflow.com/questions/75392668/how-to-remove-nameof-in-place-of-string-error-in-visualstudio

Possible solutions

Suppress the warning via #pragma:
--> Works, but if there are lots of occurrences, a lot of #pragmas have to be used, which makes the source code ugly.
Suppress the warning on project level, e.g. via .editorconfig.
--> Works as well, but silences this warning completely, so all valid use-cases (e.g. ArgumentNullException) also disappear.
Do not explicitly set propertyName if it matches the underlying property's name:using Newtonsoft.Json;

namespace ConsoleApp;

internal sealed class DataTransferObject
{
    [JsonProperty]
    public string? Property { get; set; }
}

--> The problem with this approach is that a future code refactoring might lead to bugs, e.g. if the property Property is renamed, but the name used in the JSON has to remain "Property" for compatibility with an external API. The person doing the refactoring has to pay attention when doing so, which is prone to errors.
Rename the JsonPropertyAttribute's constructor parameter propertyName to something else, therefore making sure CA1507 does not fire anymore.
--> The easiest solution for everybody using Newtonsoft.Json, but propertyName is the correct name for the parameter, finding another, fitting one might not be easy. System.Text.Json uses name in their JsonPropertyNameAttribute constructor: https://github.com/dotnet/runtime/blob/2b5f34218de7ff46dc9c0c37976c7a4abc64fcd2/src/libraries/System.Text.Json/src/System/Text/Json/Serialization/Attributes/JsonPropertyNameAttribute.cs#L17

Newtonsoft.Json is affected because the circumstances necessary apply to its JsonPropertyAttribute. It can also affect other code, for example:
The attribute
[AttributeUsage(AttributeTargets.Property)]
public sealed class DemoAttribute : Attribute
{
    public DemoAttribute(string propertyName)
    {
        PropertyName = propertyName;
    }

    public string PropertyName { get; }
}

applied to
    [Demo("Property")]
    public string? Property { get; init; }

leads to the same result:
Warning CA1507 : Use nameof in place of string literal 'Property'

fitting one might not be easy. System.Text.Json uses name

name is quite good, in my opinion. If that is not desired (but i could not image why), jsonPropertyName should also do the trick...


possible fix for cmake link bug

@kiritigowda : can you try this and see if it fixes the CMake issue. I have switched to hipcc and removed the clang commented code for HIP backend

@rrawther -- this PR has the same issue on RedHat & SLES as explained in #137
http://math-ci.rocm.amd.com/blue/organizations/jenkins/compute-rocm-dkms-no-npi-hipclang%2FShort-GPUOpen%2Frpp/detail/PR-136/1/pipeline/339

Since there is another PR which addresses the issue, closing this one


[DDW-746] Small UI and copy improvements

This PR improves small UI and copy elements.
Todos

[ ] 'GPU safe mode' should be moved to the bottom of the menu, under 'Known issues' item.
[ ] 'GPU safe mode' should be renamed to 'Blank screen fix'. Copy in the dialog window should also be updated, both for turning on and off of this setting.
[ ] 'Help and support' should be renamed to 'Help' in the application menu
[ ] 'TLS certificate is not valid. Please restart Daedalus' message should be changed to 'A configuration issue was detected and fixed. Please restart Dedalus to continue.'.
[ ] Add the "Hide Daedalus", "Hide Others", and "Show All" menu options to the OSX menu.
[ ] Move 'Block consolidation status' and 'Daedalus diagnostics' under the help menu. Help menu should have these items in this order, including separators:

- Known Issues
- Blank Screen Fix
- ----------------
- Support Request
- Download Logs
- ----------------
- Block Consolidation Status
- Daedalus Diagnostics

Screenshots
English

Japanese

Testing Checklist

Slack QA thread
Copy/Translation Thread
[ ] Test

Review Checklist
Basics

[ ] PR has been assigned and has appropriate labels (feature/bug/chore, release-x.x.x)
[ ] PR is updated to the most recent version of the target branch (and there are no conflicts)
[ ] PR has a good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[ ] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance and unit tests are passing (yarn test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn package / CI builds)
[ ] There are no flow errors or warnings (yarn flow:test)
[ ] There are no lint errors or warnings (yarn lint)
[ ] There are no prettier errors or warnings (yarn prettier:check)
[ ] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[ ] Japanese text changes are proofread and approved (Junko Oda)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (yarn storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly commented and documented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-renderings
[ ] Any code that only works in main process is neatly separated from components

Testing

[ ] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[ ] All existing acceptance tests are still up-to-date
[ ] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Merge the PR
[ ] Delete the source branch
[ ] Move the ticket to done column on the YouTrack board
[ ] Update Slack QA thread by marking it with a green checkmark

Thanks for Japanese screenshots! ❤


iOS iso7816 sendCommand Response Error

I'm working on reading an iso1443-4 card on iOS. It works well on Swift code but failed in the flutter project.
Code with flutter-nfc-manager
iso7816Tag.sendCommandRaw(Uint8List.fromList([0x00, 0xA4, 0x04, 0x00, 0x08, 0x50, 0x41, 0x59, 0x2E, 0x54, 0x49, 0x43, 0x4C, 0x00])).then((value) =>
{
   print("select App response ${value}")
});

flutter-nfc-manager Response
flutter: select App response []
[CoreNFC] 00000002 8001cb40 -[NFCTagReaderSession setAlertMessage:]:90  (null)

The command is correct, it works well in Xcode with swift.
Code with Swift
let selectApp : NFCISO7816APDU = NFCISO7816APDU(data: Data.init([0x00, 0xA4, 0x04, 0x00, 0x08, 0x50, 0x41, 0x59, 0x2E, 0x54, 0x49, 0x43, 0x4C, 0x00]))!

session.connect(to: tag0!) { (e: Error?) in tag?.sendCommand(apdu: selectApp, completionHandler: { (data: Data, sw1: UInt8, sw2: UInt8, error: Error?) in
  print("selectApp APDU Result \(data.hexDescription)")
})
}

Swift Response
selectApp APDU Result 6f3484085041592e5449434ca5289f0801029f0c21ffffffffffffffff000000000000000000000000000000002019082400000186a0

Please help to confirm the issues. 🙏

@whywilson Please tell me the version of the plugin.
I recommend to use the newer version as much as possible.

@whywilson Please tell me the version of the plugin.
I recommend to use the newer version as much as possible.

It's always the latest version.
I guess the tag used to connect was not converted to ISO7816TAG.
Here's the full swift code which works well.
        func tagReaderSession(_ session: NFCTagReaderSession, didDetect tags: [NFCTag]) {
            print("didDetect \(tags)")
            var nfcIso7816Tag: NFCISO7816Tag? = nil
            var nfcTag: NFCTag? = nil

            for tag in tags {
                if case let .iso7816(cTag) = tag {
                    nfcIso7816Tag = cTag
                    nfcTag = tag
                }
            }

            if nfcIso7816Tag == nil {
                session.invalidate(errorMessage: "Card not support")
            }

            let selectApp : NFCISO7816APDU = NFCISO7816APDU(data: Data.init([0x00, 0xA4, 0x04, 0x00, 0x08, 0x50, 0x41, 0x59, 0x2E, 0x54, 0x49, 0x43, 0x4C, 0x00]))!
            let readPurse : NFCISO7816APDU = NFCISO7816APDU(data: Data.init([0x80, 0x5C, 0x00, 0x02, 0x04]))!
                                   ⬇
            session.connect(to: nfcTag!) { (e: Error?) in
                         ⬇
                nfcIso7816Tag?.sendCommand(apdu: selectApp, completionHandler: { (data: Data, sw1: UInt8, sw2: UInt8, error: Error?) in
                    print("selectApp APDU Result \(data.hexDescription)")
                })

                nfcIso7816Tag?.sendCommand(apdu: readPurse, completionHandler: { (data: Data, sw1: UInt8, sw2: UInt8, error: Error?) in
                    let moneyString  = data.hexDescription
                    let moneyValue = Double(Int(moneyString, radix: 16)!) / 100.0
                    print("Data \(data.hexDescription)")
                    session.alertMessage = "羊城通 余额：￥\(moneyValue)"
                })
            }
        }

flutter: select App response []

@whywilson
It seems that the sendCommandRaw returns a list, so I guessed the version is old. (< 2.0.0)
But you say that you're using the latest version, so this is probably the plugin bug.
I will investigate in the near the future.

flutter: select App response []

@whywilson
It seems that the sendCommandRaw returns a list, so I guessed the version is old. (< 2.0.0)
But you say that you're using the latest version (>= 3.0.0), so this is probably the plugin bug.
I will investigate in the near the future.

Thank you for the work. Please also check here. https://github.com/nfcim/flutter_nfc_kit/issues/32


Support ingressClassName along side kubernetes.io/ingress.class

The AGW ingress controller still uses kubernetes.io/ingress.class but the AWS ALB ingress controller doesn't use it anymore but only uses ingressClassName.
Via the helm chart there is no way of setting ingressClassName of the ingress.

@krokofant Thank you for your advice. I' ll add ingressClassName in the next release

This issue is fixed in in the v0.0.7


Question model for each module in the module file

The question models are present in the module files. They can be moved to the models folder that exists.

i want to slve thsi issue


Email Regex not respecting RFC

In our project we validate email addresses using z.string().email(), a user reported that he couldn't signup since his email was containing an & (user&user@company.com).
According to the email RFC (section 3.4.1 and 3.2.4) it should allow the following special characters:
atext           =       ALPHA / DIGIT / ; Any character except controls,
                        "!" / "#" /     ;  SP, and specials.
                        "$" / "%" /     ;  Used for atoms
                        "&" / "'" /
                        "*" / "+" /
                        "-" / "/" /
                        "=" / "?" /
                        "^" / "_" /
                        "`" / "{" /
                        "|" / "}" /
                        "~"

but in the current regex the & is not included:
https://github.com/colinhacks/zod/blob/3032e240a0c227692bb96eedf240ed493c53f54c/src/types.ts#L600

If this is intentional i think it should be mentioned in the code with a comment, the current code is quite tricky to read due to old regexes comments:
https://github.com/colinhacks/zod/blob/3032e240a0c227692bb96eedf240ed493c53f54c/src/types.ts#L587-L602

MDN says the following

Browsers automatically provide validation to ensure that only text that matches the standard format for Internet email addresses is entered into the input box. Browsers use an algorithm equivalent to the following regular expression:

/^[a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-]+@[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*$/;

But like @rawnly , it seems this project has some history fighting with email regex's, so perhaps there is a reason why it isn't trying to be compliant.
Note as well that for non latin scripts, emails can have unicode characters as well.


CREATE INDEX = error

CREATE INDEX FieldPK IF NOT EXISTS FOR (field:Field) ON (field.name);

Causes error. Maybe it is not hard to change grammar to accept these?

(Thanks for FANTASTIC plugin!)

Hi @neopaf, thank you for logging this issue!
Support for new CREATE INDEX syntax was added in version 0.4.0 of the plugin. Which version are you using? It looks like it's working correctly on my side (I'm using version 0.5.0 of the plugin)

thanks, Alberto. Looks like I was using an outdated version somehow.
(Shame on me for not double-checking before reporting)
(Thanks to you for your patience ;)


Friendslist is inaccurate

Only 4 friends are shown as online, there's many many players missing from that list.
downlords-faf-client.log.2019-05-07.0.gz

Also i found not all players are shown on ne that are

i was missing one player and when i rejoined aeolus he reappeared


Please add without Shake for Tablets etc

Please add without Shake for Tablets etc
Thanks

Hi, you can use scripts/persistent/devtools.js for this - which doesn't include the shake to activate.


Gateway v2 - Getting error on docker logs of "Unexpected token...in JSON at position 0" when checking market prices for Uniswap

Describe the bug
While monitoring gateway on development branch, we noticed that when uniswap is checking for market prices it is getting error on docker logs of  Unexpected token...in JSON at position 0. While this has been observed on docker logs, so far it doesn't seem to have impact on the gateway connectors.
Ran endpoint test and getting the same behavior for the following:
Uniswap Kovan and Optimism

Error starts after Fetching trade data...
Despite getting the error, we noticed that it still managed to get the best trade
Tested with infura and ankr node, getting the same error
uniswap-kovan

uniswap-optimism

Uniswap Arbitrum_one

Getting the error below when using the ankr node for arbitrum

Tried to use infura node seems to work

Impact

Arbitrum_one is unusable when using ankr however for the workaround change the nodeURL to https://arbitrum-mainnet.infura.io/v3/enter-your-api should work fine
Execution of trades worked and checked Uniswap mainnet and Avalanche's pangolin and traderjoe both using infura, ankr and default rpc node are not affected

Steps To Reproduce

Setup simple AMM strategy using Uniswap kovan, arbitrum or optimism
Setup nodeURL for testing either infura, ankr or default rpc nodes
Start the strategy and check the client log panel
Split or open another terminal and run docker logs -f hummingbot-gateway-xxxx to monitor the docker logs
For endpoint testing, curl command used:

# make sure to modify which network you want to use eg. kovan, mainnet,  arbitrum, optimism and polygon
# modify amount
# export PORT=insert-docker-instance-port

curl -s -X POST -k --key $GATEWAY_KEY --cert $GATEWAY_CERT -H "Content-Type: application/json" -d "$(envsubst < ./requests/price_uniswap.json)" https://localhost:$PORT/amm/price | jq

Release version
development dev-1.8
Attachments
// Please attach your config file and log file to help us debug. It would be difficult for us to help you without those!
uniswap.zip

While checking arbitrum_one on uniswap we are getting an error upon starting the strategy which resulting the connector unusable. Tried to run on endpoint testing and found out we are getting Error: Price query failed: processing response error.. when running evm/price
This error occurs when using ankr as our nodeURL for arbitrum_one https://rpc.ankr.com/arbitrum

Client logs
2022-09-12 02:13:27,190 - 123404 - hummingbot.core.gateway.gateway_http_client - WARNING - Call to https://localhost:17539/amm/price failed. See logs for more details.
2022-09-12 02:13:27,191 - 123404 - GatewayEVMAMM - WARNING - Error on POST https://localhost:17539/amm/price Error: {'message': 'Price query failed: missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (data="0x", transaction={"to":"0x1F98415757620B543A52E61c46B32eB19261F984","data":"[encoded data, 4746 characters]","accessList":null}, error={"reason":"processing response error","code":"SERVER_ERROR","body":"{\\"jsonrpc\\":\\"2.0\\",\\"error\\":{\\"code\\":0,\\"message\\":\\"we can\'t execute this request\\"},\\"id\\":null}","error":{"code":0},"requestBody":"{\\"method\\":\\"eth_call\\",\\"params\\":[{\\"to\\":\\"0x1f98415757620b543a52e61c46b32eb19261f984\\",\\"data\\":\\"[encoded data, 4746 characters]\\"},\\"latest\\"],\\"id\\":71,\\"jsonrpc\\":\\"2.0\\"}","requestMethod":"POST","url":"https://rpc.ankr.com/arbitrum"}, code=CALL_EXCEPTION, version=providers/5.6.8)', 'httpErrorCode': 500, 'errorCode': 1013, 'stack': 'Error: Price query failed: missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (data="0x", transaction={"to":"0x1F98415757620B543A52E61c46B32eB19261F984","data":"[encoded data, 4746 characters]","accessList":null}, error={"reason":"processing response error","code":"SERVER_ERROR","body":"{\\"jsonrpc\\":\\"2.0\\",\\"error\\":{\\"code\\":0,\\"message\\":\\"we can\'t execute this request\\"},\\"id\\":null}","error":{"code":0},"requestBody":"{\\"method\\":\\"eth_call\\",\\"params\\":[{\\"to\\":\\"0x1f98415757620b543a52e61c46b32eb19261f984\\",\\"data\\":\\"[encoded data, 4746 characters]\\"},\\"latest\\"],\\"id\\":71,\\"jsonrpc\\":\\"2.0\\"}","requestMethod":"POST","url":"https://rpc.ankr.com/arbitrum"}, code=CALL_EXCEPTION, version=providers/5.6.8)\n    at /usr/src/app/dist/src/connectors/uniswap/uniswap.controllers.js:74:23\n    at Generator.throw (<anonymous>)\n    at rejected (/usr/src/app/dist/src/connectors/uniswap/uniswap.controllers.js:6:65)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)'}

Docker logs

2022-09-13 04:15:41 | error | 	Price query failed: missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (data="0x", transaction={"to":"0x1F98415757620B543A52E61c46B32eB19261F984","data":"[encoded data, 4746 characters]","accessList":null}, error={"reason":"processing response error","code":"SERVER_ERROR","body":"{\"jsonrpc\":\"2.0\",\"error\":{\"code\":0,\"message\":\"we can't execute this request\"},\"id\":null}","error":{"code":0},"requestBody":"{\"method\":\"eth_call\",\"params\":[{\"to\":\"0x1f98415757620b543a52e61c46b32eb19261f984\",\"data\":\"[encoded data, 4746 characters]\"},\"latest\"],\"id\":552,\"jsonrpc\":\"2.0\"}","requestMethod":"POST","url":"https://rpc.ankr.com/arbitrum"}, code=CALL_EXCEPTION, version=providers/5.6.8) | Error: Price query failed: missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (data="0x", transaction={"to":"0x1F98415757620B543A52E61c46B32eB19261F984","data":"[encoded data, 4746 characters]","accessList":null}, error={"reason":"processing response error","code":"SERVER_ERROR","body":"{\"jsonrpc\":\"2.0\",\"error\":{\"code\":0,\"message\":\"we can't execute this request\"},\"id\":null}","error":{"code":0},"requestBody":"{\"method\":\"eth_call\",\"params\":[{\"to\":\"0x1f98415757620b543a52e61c46b32eb19261f984\",\"data\":\"[encoded data, 4746 characters]\"},\"latest\"],\"id\":552,\"jsonrpc\":\"2.0\"}","requestMethod":"POST","url":"https://rpc.ankr.com/arbitrum"}, code=CALL_EXCEPTION, version=providers/5.6.8)
    at /usr/src/app/dist/src/connectors/uniswap/uniswap.controllers.js:74:23
    at Generator.throw (<anonymous>)
    at rejected (/usr/src/app/dist/src/connectors/uniswap/uniswap.controllers.js:6:65)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Tried to test different nodeURL using infura https://arbitrum-mainnet.infura.io/v3/enter-your-api and seems to work

Impact
This is observed happening when using ankr and not when using infura abitrum supported nodeURL which is working ok
https://user-images.githubusercontent.com/73840223/189801876-17f6953d-6ed3-41b1-8742-9e8a546e80b4.mp4
Steps to reproduce

Connect Arbitrum_one wallet
Setup simple AMM arbitrage with default settings
Start the strategy and observe the log panel
Test using cur testing found in gateway/manual-tests/

curl -s -X POST -k --key $GATEWAY_KEY --cert $GATEWAY_CERT -H "Content-Type: application/json" -d "$(envsubst < ./requests/price_uniswap.json)" https://localhost:$PORT/amm/price | jq

Release version
Development dev-1.8
logs_gateway_app.log.2022-09-12.zip


Updates for rustc nightly c89de2c56

A couple changes to update stainless to the rustc nightly as of 3/29/2015:

Remove unused core
replace deprecated as_slice with deref coercions
should_fail -> should_panic
remove unneeded u suffix

Thanks for the feedback, addressed comments and rebased =)


Issue with installing/Using

I am having problems with rbush is not defined
steps i did:

npm install https://github.com/IITC-CE/Leaflet.Canvas-Markers.git
require('leaflet-canvas-marker'); also tried import 'leaflet-canvas-marker'

Now i get error: rbush is not defined
Also tried to install rbush in my project.
Am I using this wrong?
Used this code to test
   // Adds a layer
    let ciLayer = L.canvasIconLayer({}).addTo(map);

      // Marker definition
    let marker =  L.marker([58.5578, 29.0087]);

      // Adding marker to layer
    ciLayer.addMarker(marker);

I also deleted node_modules and package-lock and npm install again to make sure...

After npm install have you got dist/leaflet.canvas-markers.js file (14436 b size)?

Also please note that original 'build system' is rather dumb and only tested way to use it - follow original guide literally: https://github.com/IITC-CE/Leaflet.Canvas-Markers#installation-and-basic-usage.
I'm not the author of that code, and in my project I use main source file directly https://github.com/IITC-CE/Leaflet.Canvas-Markers/blob/master/src/plugin/leaflet.canvas-markers.js (after including rbush 2.0.2).
I see that you prefer to install the plugin with require. I cannot tell if that should work.
So if that is not working - you can try to fix webpack.config.js or Leaflet.Canvas-Markers/src/_full.js
https://github.com/IITC-CE/Leaflet.Canvas-Markers/blob/affa3f5c1c5b8aee979fa79532a1223dcb3f7e34/src/_full.js#L1-L5


Add CodeQL Analysis (#8598)

Summary of the Pull Request
From  @jhutchings1 in https://github.com/microsoft/PowerToys/pull/8598, this would add in codeql.  Since we couldn't test this against branch before, i'm doing a branch then into master.
PR Checklist

[ ] Applies to #8570
[ ] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

@jhutchings1 this builds on our CI instance but not on the codeql instance :/  any ideas?

rebased on the latest master

The build has passed, but it took 85 minutes on CI. I think it's not worth it to enable it for each PR. Perhaps we could setup the CI to run it once a week or something?

That was the thought. Needed to verify it working so I turned on push. Did a little bit of looking and think we can leverage our CI too but that is more work

removed push due to increase time.  this will be run twice a day on crom

/azp run


Compile apollo Cyber RT in aarch64 platform, need fastrtps modification

Cyber RT depends on fastrtps.
But fastrtps is not open source in X86 cyber RT.
The eProsima Fast RTPS ( fastrtps 1.5.0 and fastcdr 1.0.7 ) in official website does't work well in aarch64 cyber RT.
What is the modification of fastrtps?

Cyber RT depends on fastrtps.
But fastrtps is not open source in X86 cyber RT.
The eProsima Fast RTPS ( fastrtps 1.5.0 and fastcdr 1.0.7 ) in official website does't work well in aarch64 cyber RT.
What is the modification of fastrtps?
What does “does't work well in aarch64 cyber RT” mean? Can't nodes communicate with each other or
or losting message？Can you describe it more specifically?

There are indeed some things that need to be changed in fast rtps:
Find the socket_ops.ipp file in third_party_src/fast_rtps/thirdparty/asio/asio/include/asio/detail/impl/ folder:
 #if defined(__MACH__) && defined(__APPLE__) \   || defined(__NetBSD__) || defined(__FreeBSD__) || defined(__OpenBSD__)   || defined(__NetBSD__) || defined(__FreeBSD__) || defined(__OpenBSD__) || defined(YOURPLATFORM)     // To implement portable behaviour for SO_REUSEADDR with UDP sockets we     // need to also set SO_REUSEPORT on BSD-based platforms.     if ((state & datagram_oriented)
add YOURPLATFORM to the macro definition.
Find multicast.cpp file in  third_party_src/fast_rtps/thirdparty/asio/asio/src/tests/unit/ip/multicast.cpp  folder,:
#if (defined(__MACH__) && defined(__APPLE__)) \   || defined(__FreeBSD__) \   || defined(__NetBSD__) \   || defined(__OpenBSD__)   || defined(__OpenBSD__) \   || defined(__QNX__)   const ip::address multicast_address_v6 = ip::make_address("ff02::1%lo0", ec); #else // (defined(__MACH__) && defined(__APPLE__))       //   || defined(YOURPLATFORM)
and  add YOURPLATFORM to the macro definition.

Hello @darbee ,  I run the talker/listener examples of Cyber RT, they can't communicate with each other.
Here is the log:
//////////////////////////////////////////////////////////////////////////////////////////////////////
taker.INFO:
I0212 22:14:20.124140  4517 init.cc:112]  Register exit handle succ.
I0212 22:16:26.607206  4517 talker.cc:42]  talker sent a message!
I0212 22:23:33.528126  4517 talker.cc:42]  talker sent a message!
W0212 22:23:33.528605  4517 rate.cc:95]  Detect forward jumps in time
I0212 22:23:33.528791  4517 talker.cc:42]  talker sent a message!
W0212 22:23:33.530519  4541 manager.cc:192]  !message::ParseFromString(msg_str,
&msg) is not met.
I0212 22:23:41.030671  4517 talker.cc:42]  talker sent a message!
W0212 22:23:41.030889  4517 rate.cc:95]  Detect forward jumps in time
listener.INFO:
I0212 22:13:49.499541  4491 init.cc:112]  Register exit handle succ.
W0212 22:23:30.697654  4515 manager.cc:192]  !message::ParseFromString(msg_str,
&msg) is not met.
///////////////////////////////////////////////////////////////////////////////////////////////////////
I am debuging this problem, and found some part of the string message is missing.
The string messages are published and received by these 2 functions. These 2 functions will call Fast-RTPS's functions.
apollo::cyber::service_discovery::Manager::Publish("\b\254\243\3... 001\030\000 \001(\002")
apollo::cyber::service_discovery::Manager::OnRemoteChange("\b\254\243\3... 001\030")
The \000 \001(\002 string is missing.
If I don't describe clearly, please let me konw. Thank you.

@darbee   I compiled fastrtps on the aarch64 platform. According to what you said, I defined AARCH64, and then added "||defined(AARCH64)" to the location of the socket_ops.ipp file and the multicast.cpp file. Compile cyber again. RTPS_ERROR Error] Reader 1.f.0.3.e2.1d.<IP_ADDRESS>.0.0|<IP_ADDRESS> cannot match write 1.f.0.3.c9.1d.<IP_ADDRESS>.0.0|<IP_ADDRESS> -> Function PairingReader" Am I doing right?  How can I solve this problem? Thank you.

Hello @darbee , I run the talker/listener examples of Cyber RT, they can't communicate with each other.
Here is the log:
//////////////////////////////////////////////////////////////////////////////////////////////////////
taker.INFO:
I0212 22:14:20.124140 4517 init.cc:112] Register exit handle succ.
I0212 22:16:26.607206 4517 talker.cc:42] talker sent a message!
I0212 22:23:33.528126 4517 talker.cc:42] talker sent a message!
W0212 22:23:33.528605 4517 rate.cc:95] Detect forward jumps in time
I0212 22:23:33.528791 4517 talker.cc:42] talker sent a message!
W0212 22:23:33.530519 4541 manager.cc:192] !message::ParseFromString(msg_str,
&msg) is not met.
I0212 22:23:41.030671 4517 talker.cc:42] talker sent a message!
W0212 22:23:41.030889 4517 rate.cc:95] Detect forward jumps in time
listener.INFO:
I0212 22:13:49.499541 4491 init.cc:112] Register exit handle succ.
W0212 22:23:30.697654 4515 manager.cc:192] !message::ParseFromString(msg_str,
&msg) is not met.
///////////////////////////////////////////////////////////////////////////////////////////////////////
I am debuging this problem, and found some part of the string message is missing.
The string messages are published and received by these 2 functions. These 2 functions will call Fast-RTPS's functions.
apollo::cyber::service_discovery::Manager::Publish("\b\254\243\3... 001\030\000 \001(\002")
apollo::cyber::service_discovery::Manager::OnRemoteChange("\b\254\243\3... 001\030")
The \000 \001(\002 string is missing.
If I don't describe clearly, please let me konw. Thank you.

Hi @bssung , through your description, it seems to be a problem of string truncation.
\b\254\243\3... 001\030\000 \001(\002"
the 000 may be treated as the end of string. I also fixed this bug of fast rtps.
You look the the site :
https://github.com/ApolloAuto/apollo-platform/blob/master/ros/third_party/FastRTPS_1.4.0.patch
It's the patch of string truncation.
What you should focus on is the function serialize modified in the cdr.h and cdr.cpp files.

@darbee I compiled fastrtps on the aarch64 platform. According to what you said, I defined AARCH64, and then added "||defined(AARCH64)" to the location of the socket_ops.ipp file and the multicast.cpp file. Compile cyber again. RTPS_ERROR Error] Reader 1.f.0.3.e2.1d.<IP_ADDRESS>.0.0|<IP_ADDRESS> cannot match write 1.f.0.3.c9.1d.<IP_ADDRESS>.0.0|<IP_ADDRESS> -> Function PairingReader" Am I doing right? How can I solve this problem? Thank you.

If this change is not suitable for your situation, you can restore the original code first, because I did not test the situation under arm linux, so I am not sure that this modification will adapt to your platform, if there is any progress or problem, You can inform me in time.

Thanks! The patch works well.

Hi guys, I'm trying to run the same example on aarch64 using the r6.0.0 branch. Even though running the example on x86_64 works fine, on aarch64 the listener seems not to receive the message. The talker says that it has sent the message but in the listener log there is no trace of it. I tried to sniff the packets using wireshark and there isn't trace of it! I'm trying to run the talker and the listener on different containers using how it is explained on #7050. This approach on x86_64, as I said, works fine with correct communication between them. Could you help me?


Dump the FieldOptions structure to a reference file

All options related to the processing of a field are stored in a FieldOptions structure that is passed into the prefect workflow.
This should be dumped to a dumb file in the output science folder for record keeping.

This is actually more important than first initially thought.
This should be done promptly as the holography needs to also be rotated. There are a number of implicit assumptions that will have to be made regarding the orientation of the third-axis and footprint when the holography data were formed.
We will need to provide the alpha (in rad) parameter to the linmos parset, which is the differential rotation between the science field's footprint PA and the holography footprint PA.
We can (should) be able to get the original third-axis rotation from the original MSs (or from the fixms corrected MSs after a patch and an appropriate column name change). Then we will just have to assume the footprint rotation is fixed, and the holography orientation (third-axis and footprint) remain fixed.

Not nearly as important as first thought.
Being addressed in dumpfield branch

Addressed in #136


[PDI-13748] Hide Template Sheet option

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f ui/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f ui/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  ui/src/org/pentaho/di/ui/trans/steps/excelwriter/ExcelWriterStepDialog.java


task/install/redhat: Removing packages based on OS in cleanup task

script modified to remove packages  based on OS in the cleanup task.While uninstalling packages, both rpm and deb packages are getting first and  in the next step checking the OS name and removing the packages.
As part of fix first checking the OS name after that getting the appropriate packages to remove.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

I wonder, does RedHat support deb packages?

I wonder, does RedHat support deb packages?

Teuthology Log-   http://pulpito.ceph.redhat.com/skanta-2021-01-12_07:32:23-rados:singleton-master-distro-basic-clara/

Teuthology Log-   http://pulpito.ceph.redhat.com/skanta-2021-01-12_07:32:23-rados:singleton-master-distro-basic-clara/

We support for some of the older versions

We support for some of the older versions

Currently we are supporting the deb packages.

Currently we are supporting the deb packages.

To clean up the branch and to raise the PR  only with required changes.

To clean up the branch and to raise the PR  only with required changes.


'incompatible with 44.0.{1,2}'

When using Firefox 44.0.1 or 44.0.2, Pentadactyl gets disabled. There are no problems with 44.0 itself.
Are there really addon-breaking changes in a minor upgrade, or is this merely an issue with version-detection?

The latest commit 0b835e1 works fine to me. (I am using Firefox 44.0.2)

Works for me too. I thought I'd already tried it, must have forgotten to actually load the new version in Firefox.


afterChange hook runs before data is persisted to the database ?

Link to reproduction
Private repo
Describe the Bug
We have been trying to use NextJS on-demand-revalidation for our Blog posts. To do this, we tried using the afterChange collection hook.
But it seems like the in the afterChange hook the data is not persisted to the DB when the hook is called, so calling revalidate only makes the NextJS app re-fetch the blog post as it was before it was updated.
Let's say we have a blog post which is named Blog Post ABC, and we are trying to change to Blog Post ABCDEF. This is what happens:

Collection afterChange hook starts running.
A revalidate request is sent to the NextJS application from the afterChange hook.
NextJS application revalidates the blog post
On revalidate, the NextJS application fetches the updated blog post from the database.

However, the blog post fetched by NextJS is still the old blog post that hasn't been updated.
To verify my suspicions I tried running a findById query in the hook:
const blogById = await payload.findByID({
  collection: "blogPosts",
  id: doc.id,
  draft: true,
});

// Returns Blog Post ABC for the title, not Blog Post ABCDEF

In this case, the Blog Post is still named Blog Post ABC. I also tried adding a fetch in the revalidate function of the NextJS app, and the same still happens there, the old Blog Post is fetched.
Is this the intended behaviour of the afterChange hook ? If so what am I supposed to use for revalidating something on my NextJS app whenever data is created, updated or deleted ? There doesn't seem to be any other hooks that seem to fit the use case. I also tried the afterOperation hook but it seems the behaviour is exactly the same there.
To Reproduce

Create a new collection called BlogPost
Set the title to ABC and save.
Now create a afterChange hook on the collection.
Change title of Blog post title to ABCDEF
In the afterChange hook, the document has updated its title to ABCDEF, however by fetching the BlogPost from payload, the Blog Post title is still ABC.

Ideally, you'd also have a frontend using NextJS + On-demand-isr that actually uses the revalidate function implemented something like this:
export default async function handler(req, res) {
  // Check for secret to confirm this is a valid request
  if (req.query.secret !== process.env.MY_SECRET_TOKEN) {
    return res.status(401).json({ message: 'Invalid token' })
  }

  try {
    // this should be the actual path not a rewritten path
    // e.g. for "/blog/[slug]" this should be "/blog/post-1"
    await res.revalidate('/blog/id-from-payload')
    return res.json({ revalidated: true })
  } catch (err) {
    // If there was an error, Next.js will continue
    // to show the last successfully generated page
    return res.status(500).send('Error revalidating')
  }
}```

And then confirm that on the frontend, the blog post is not updated.

### Payload Version

2.12.1

### Adapters and Plugins

postgres

Hey @Jonashr,
Thanks for that info, this is helpful and very clear to me of what the issue is.
Due to transactions you aren't able to fetch the content change "ABCDEF" at the time of the afterChange hook.
In your hook you can pass the req which includes a transactionID and any payload local operation or payload.db operation that have the req will use it. In that way your payload.findByID example could work to get "ABCDEF".
Thinking through the options here, you could disable transactions. If you are using mongoDB you'd do that with transactionOptions: false. Turning this off reduces your overall data integrity so errors that come up in normal operation might leave a bad state of data changes from one request.
Another option is to add a setTimeout() this isn't great because of course you won't really know how long to wait before knowing a transaction has completed and it is ugly. If an error occurs and revalidation occurs it shoudln't be a big deal since the content of the last validation will come up again on the next query after a rollback, so probably fine.
Ideally though we should have a pattern for this that would let you push callbacks after a commit. I want it to have a good DX of course, so I'm open to ideas.

Hey @Jonashr,
Thanks for that info, this is helpful and very clear to me of what the issue is. I'll add some ideas on top of what James has already stated.
In your hook you can pass the req which includes a transactionID to any payload local API functions or payload.db operationsto use the same transactions. In that way your payload.findByID example could work to get "ABCDEF".
You could pass your data to the validation endpoint from this fetch if you wanted one workaround option.
Another option is to add a setTimeout() this isn't great because of course you won't really know how long to wait before knowing a transaction has completed and it is ugly. If an error occurs and revalidation occurs it shoudln't be a big deal since the content of the last validation will come up again on the next query after a rollback, so probably fine.
You could disable transactions as another option. If you are using mongoDB you'd do that with transactionOptions: false. Turning this off reduces your overall data integrity so errors that come up in normal operation might leave a bad state of data changes from one request. Not ideal, but still an option.
Ideally we should have a pattern for this that would let you push callbacks after a commit. I want it to have a good DX of course, so I'm open to ideas.

@jmikrut @DanRibbens Thanks for the great suggestion!  You were right about the transaction not being completed being the issue here. As suggested I added the code to commit the transaction:
  const { payload, transactionID } = req

  await payload.db.commitTransaction(transactionID)

Once I committed the transaction it worked like a charm.  So I am just going to close this issue as it has been solved. Thanks again!

I just ran into this too. For me it was a quite confusing tbh, I did not expect the afterChangeHook to run before the changes are actually committed to the DB. After I read the source code, it made sense what was happening and your explanation confirms this.
Similarly to the op, in my use case I want to purge and prime a cache of an external app when the user has saved something in the CMS. The cache priming within the hook didn't work, as the external app would always pull the previous data from the CMS.
I understand that there may be other use cases where it is beneficial to have the transaction commit only after the hook has run. Your described solution with committing the transaction in the hook works for me well. I would appreciate a better API for this though (maybe an afterCommitHook)?


mapSeries added #11

Given the recent discussion about union types, I think that you could do the following replacement:
// promise of array with promises of value
static mapSeries<R, U>(values: Bluebird.Thenable<Bluebird.Thenable<R>[]>, iterator: (item: R, index: number, arrayLength: number) => U | Bluebird.Thenable<U>): Bluebird<U[]>;
// array with promises of value
static mapSeries<R, U>(values: Bluebird.Thenable<R>[], iterator: (item: R, index: number, arrayLength: number) => U | Bluebird.Thenable<U>): Bluebird<U[]>;
// array with values OR promise of array with values
static mapSeries<R, U>(values: R[] | Bluebird.Thenable<R[]>, iterator: (item: R, index: number, arrayLength: number) => U | Bluebird.Thenable<U>): Bluebird<U[]>;

// Promise OR array of Promises OR values:
static mapSeries<R, U>(values: (R | Bluebird.Thenable<R>)[] | Bluebird.Thenable<(R | Bluebird.Thenable<R>)[]>, iterator: (item: R, index: number, arrayLength: number) => U | Bluebird.Thenable<U>): Bluebird<U[]>;

This should prevent disjunctions and allow valid usages such as:
let array: (number | Thenable<number>)[] = [
  10,
  Bluebird.resolve(20)
];
Bluebird.mapSeries(array, ...);

Or
let eventualArray: number[] | Thenable<number[]> = getEventualArray(); // returns either an array or a promise for an array
Bluebird.mapSeries(eventualArray, ...);

Fixed.

Looks fine to me.
@louy, @unional: any comment ?

I think we should have something like type MaybeThenable<T> = T | Thenable<T>;.

Agreed


[bootstrap] Preemptively add argument for Foundation

https://github.com/apple/swift-corelibs-xctest/pull/43 will add a dependency between swift-corelibs-xctest and swift-corelibs-foundation. This will necessitate the path to a Foundation build be passed to the SwiftPM bootstrap script; see #177.
In order to prevent CI from breaking, we'll modify the Swift build script to pass the correct parameters before those parameters are actually used. To do that, this commit ensures the bootstrap script accepts the new parameter: "--foundation".

The README diff seems to remove the --build-tests part of the example invocation. No changes to the script seem to be related to that. Was this removed from the README in error or is that parameter not actually necessary?

@mike-ferris-apple I've decided to make the documentation changes in https://github.com/apple/swift-package-manager/pull/177, so I'll remove them from this pull request.
As for --build-tests: it's marked "deprecated" in the SwiftPM bootstrap script and is no longer used. I imagine it's still there because it used to be used by the Swift build script, but I removed it yesterday: https://github.com/apple/swift/pull/1547. I'll remove it altogether in a separate pull request.

@swift-ci please test

@swift-ci Please test

@swift-ci Please test

The tests pass! :tada:
@kostiakoval or @mxcl, how do you feel about merging this? It's crucial to delivering asynchronous tests in corelibs-xctest.

LGTM ✋

@aciidb0mb3r I don't suppose this could be the first pull request you merge? :pray:

@modocache Done! Thanks for your work and sorry for delay.

Thanks!!


Error with inclusivelint

The pipeline has a task for inclusivelint but doesnt install it.
E.g. in linter.yml
  - task: Npm@1
    displayName: "Run Inclusive Lint"
    continueOnError: true
    inputs:
      command: custom
      customCommand: "run inclusivelint"

But this step fails in the pipeline
/usr/local/bin/npm run inclusivelint
npm ERR! Missing script: "inclusivelint"
npm ERR!
npm ERR! To see a list of scripts, run:
npm ERR!   npm run

Thanks! It was removed from other files, but remain in the pipeline. Removed from there as well!


runSQL API supporting comments at end of line

Looks like QSYS/QZDFMDB2 is ignoring comments at the end of lines and thinks the rest of the script is a comment, but it does work when the line starts with a comment.
Not working
select *
from sample.employee --my table
limit 1

Working
select *
--my table
from sample.employee
limit 1

Manual intervention is required.

From @m-tyler.

Describe the bug
I use inline SQL comments A LOT.  I use it to deactivate sections of the query, like removing a result column, removing a join line, insert CTE test lines, etc.  However, it appears the parser for Code for IBM i does not correctly recognize these comments.
Inline comments are two dashes and a space.   It's the default comment for VS Code SQL language type shortcut Ctrl+/.
I noticed today that one of my CTE test lines (a line that ends with a semi colon but is in the commented state) will cause the statement to be parsed only to that point.
To Reproduce
Run this query.
with t1 as (select SYSTEM_TABLE_SCHEMA ,SYSTEM_TABLE_NAME  ,SYSTEM_TABLE_MEMBER from QSYS2.SYSPARTITIONSTAT)
-- select * from T1  where TABLE_SCHEMA = 'D1WFIQUAL' and TABLE_NAME like 'KRNMDA%';
select * from T1  where TABLE_SCHEMA = 'D1WFIQUAL' and TABLE_NAME like 'KRNMDA%';

Expected behavior
I expect comments to be excluded from the run query but I understand that is a bit harder than it sounds.
Environment (please complete the following information):

Extension version 1.2.6
IBM i OS version 7.3

From what I am seeing the statement "... but it does work when the line starts with a comment." needs to be modified to say "but it does work when the line starts with a comment in position 1"
This is unfortunate as the Generate SQL option often includes  generated comments that are indented. For example:
--  Generate SQL
--  Version:                   	V7R4M0 190621
--  Generated on:              	09/06/22 09:17:43
--  Relational Database:       	IDEVELOP
--  Standards Option:          	Db2 for i
CREATE
OR REPLACE TABLE PARTNER400.CUSTOMERS (
  --  SQL150B   10   REUSEDLT(*NO) in table CUSTOMERS in PARTNER400 ignored.
  --  SQL1506   30   Key or attribute for CUSTOMERS in PARTNER400 ignored.
  --  SQL1505   20   Number of members for CUSTOMERS in PARTNER400 not valid.
  CUSTNO CHAR(5) CCSID 37 NOT NULL DEFAULT '',
  NAME CHAR(30) CCSID 37 NOT NULL DEFAULT '',
  CITY CHAR(24) CCSID 37 NOT NULL DEFAULT '',
  STATE CHAR(2) CCSID 37 NOT NULL DEFAULT '',
  ZIP NUMERIC(5, 0) NOT NULL DEFAULT 0,
  ZIPPLUS NUMERIC(4, 0) NOT NULL DEFAULT 0
) RCDFMT CUSTREC;

If you try to run this generated statement it will error out at the first indented comment line.

@beckhamrryyaann Go for it! Any help is appreciated

@worksofliam I know you are super busy! alot of activity going on with this repo!  love it.   I just wanted you to confirm/deny my thinking before i start coding on this.
In short:
I am going to make sure comments always start in position one after the \n (newline)
If comment doesn't start in position one, then i'm going to add a new line break right before comment to always make sure its in pos 1.

@beckhamrryyaann that sounds about right! Appreciate all your work!


Integration tests + fixing filter setup

@erezlotan I missed a few important stuff in #8 - builder didn't pass the filters on to the reporter....
Added some integrative tests using WireMock to have better end-to-end coverage: using public API (Builder) and checking the data reported to Anodot.
Tests use Thread.sleep :pensive:, I'll fix this when I have a spare hour for some refactoring...

Overall looks good.
Have a question inside regarding the duplication between metrics2 and 3.
This is something to think about, but not a reason to block progress - hence merging.

@noamguy check out this one as well.


Possibly misnamed variable

Should this be shouldStartAtElement?
https://github.com/ethereum-optimism/core-utils/blob/98ef6e0f6b4b237c894b95b7e00153f889819e80/src/coders/sequencer-batch.ts#L14

Should this be shouldStartAtElement?
https://github.com/ethereum-optimism/core-utils/blob/98ef6e0f6b4b237c894b95b7e00153f889819e80/src/coders/sequencer-batch.ts#L14

This has been patched with #8
see https://github.com/ethereum-optimism/core-utils/blob/d4dcc4f598190f8c29261c5fcc78d9670c45b66e/src/coders/sequencer-batch.ts#L14

It should be shouldStartAtElement, the old name was shouldStartAtBatch which is misleading

Closing as this has been fixed - please reopen if there is an issue still


Armored Core 6 - Working Directory Woes

Unlike a lot of other FROM Software titles, Armored Core 6 needs to be launched from its working directory. Unfortunately, so does Mod Engine 2. This means that you're pretty much forced to have both Mod Engine 2 and Armored Core 6 in the same folder, so a multi-game config that has Mod Engine 2 in a different folder currently isn't feasible.

 HOWEVER, I CANT GET MINE TO WORK IN OR OUT OF THE GAME FOLDER. IS THERE PERHAPS A CONFLICT WITH USING WEMOD AND MOD ENGINE 2?


[19453] Remove Make generated example

Changes in this PR are not tested in the CI.

Manual CI action


Robustify debug output

Right now, it's extremely frustrating to debug this code, unless you can build from source and add print statements. We should implement various debug levels, similar to the way xrootd does the rest of its log levels.

@jhiemstrawisc is there someone who is the recognized expert in xrootd logging who could tell me/point me to the desired idioms?

Perhaps @matyasselmeci can point us in the right direction?

@bbockelm suggested that since you're writing a plugin, you should follow the example of another plugin instead of looking in XRootD itself, since logging code in XRootD may reach into the internals too much. xrootd-multiuser is a fine example.

We are going to move forward with this using the TRACE macros that we see being used in several places. We'll do some instrumentation that allows us to get some timing information for transfer speeds. But if there ends up being specific patterns to add, let us know.

Looks like we were both typing at the same time. Thanks for the guidance.

Looked at this again today and have a few questions. @matyasselmeci suggested following the xrootd-multiuser example, which draws a line approximately at the interface between xrootd and the plugin. This makes sense.
Looking at the code, it looks like @bbockelm did some refactoring that accomplishes this goal. Is it possible this issue has been resolved and just not marked as closed?

Closed after conversation with @bbockelm confirming that the initial goal of this issue has been accomplished even if "there is always more that could be done". :-)


Missing field in Strike

Describe the bug
NestedFutureOptionChainExpiration has a list of Strike.
But the Strike is missing the streamer-symbol fields.
https://github.com/tastyware/tastytrade/blob/master/tastytrade/instruments.py#L130
Here is an example JSON for strike:
{ "strike-price": "4400.0", "call": "./ESU4 EW3N4 240719C4400", "call-streamer-symbol": "./EW3N24C4400:XCME", "put": "./ESU4 EW3N4 240719P4400", "put-streamer-symbol": "./EW3N24P4400:XCME" }
How to reproduce
There is no error, just missing data in the json in the class.

Well I'll be darned! I wonder how long this has been there? I'm guessing the API got changed at some point. I'll definitely be adding this, it's so much easier to use. Thanks!
I wonder if this applies to the normal option chain as well...

Thanks @Graeme22 for the prompt response. I wholeheartedly appreciate this API. DXLink/DXFeed APIs are super helpful. I was about to give up until I discovered your SDK.


How to install Uptime Kuma on Replit

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
Peace be upon you. I have a problem with the database. Please help me. Thank you
👟 Reproduction steps

👀 Expected behavior

😓 Actual Behavior

🐻 Uptime-Kuma Version
V2
💻 Operating System and Arch
replit
🌐 Browser
Google Chrome
🐋 Docker Version
No response
🟩 NodeJS Version
No response
📝 Relevant log output
No response

I changed to a better title, see if anyone could help.
However, VPS is always suggested.

Ok Thank You , And Please Add Button sing up

@HOUSSAMATFI
I did some tweaking and found that with a couple of changes you can easily run the uptime kuma on replit.com. I'm not sure if any other functionality of uptime kuma will be impacted by shortcomings of repl from a full-fledged vps server.
Here's running screenshot of the repo on repl.com

Please follow these steps to get it running on your end.

Create a new repl > Choose "Import from Github" button
Use the Repository URL (https://github.com/louislam/uptime-kuma) and import
Create new file in the base of repo named .replit with the following content

run="npm run setup && node server/server.js port=80"
language="nodejs"

Use the "run" button
Use "open in new tab" button after the server starts up


Add feature to edit command detect duplicates and let user choose which of the duplicates they want to edit.

Currently edit command edits the first client whose name matches the given search term. This causes problems as users currenly are not able to edit the information of  clients that are not first in the list.
Let's

Change the way clients with names matching the search term are detected
Add a variable lastCommand to allow HustleBook to know which command the user last executed
Allow users to input a number to indicate the index of the client they wish to edit
Add logic to allow HustleBook to execute the right command when given a number as an input by checking against lastCommand

Tests for this new functionality will be added at a later date
This closes #103

Codecov Report

Merging #105 (97a9480) into master (c7866a7) will decrease coverage by 1.19%.
The diff coverage is 40.00%.

@@             Coverage Diff              @@
##             master     #105      +/-   ##
============================================
- Coverage     66.75%   65.56%   -1.20%
- Complexity      442      459      +17
============================================
  Files            81       84       +3
  Lines          1540     1661     +121
  Branches        163      176      +13
============================================
+ Hits           1028     1089      +61
- Misses          457      501      +44
- Partials         55       71      +16

Impacted Files
Coverage Δ

...a/seedu/address/logic/parser/HustleBookParser.java
72.72% <0.00%> (-11.49%)
:arrow_down:

.../java/seedu/address/logic/parser/NumberParser.java
0.00% <0.00%> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
73.43% <ø> (-13.60%)
:arrow_down:

...java/seedu/address/logic/commands/EditCommand.java
91.50% <58.82%> (-6.30%)
:arrow_down:

...rc/main/java/seedu/address/logic/LogicManager.java
76.19% <100.00%> (+1.19%)
:arrow_up:

src/main/java/seedu/address/model/HustleBook.java
76.19% <0.00%> (-5.87%)
:arrow_down:

...a/seedu/address/model/person/UniquePersonList.java
77.55% <0.00%> (-5.06%)
:arrow_down:

.../java/seedu/address/storage/JsonAdaptedPerson.java
79.54% <0.00%> (-3.79%)
:arrow_down:

... and 12 more

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 c7866a7...97a9480. Read the comment docs.


Continuous High CPU usage

Type: Bug
Constant high CPU usage by this task, no lower than 25% and increasing upto 50%. Killing it has effect, it starts again immediately. Only way to make it stop is to close and reopen the Local VSCode window (no issue seen on WSL side).
Issue is seen only since last 15 days.
From Process Explorer under Local > code main > extensionHost
electron-nodejs ("C:\Users\xyz\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node --max-old-space-size=3072 "c:\Users\xyz\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js" --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName C:\Users\xyz\AppData\Local\Temp\vscode-typescript\38388456fe3450ec9b41\tscancellation-6e23f13f2019cb0ad875.tmp* --locale en --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation --useNodeIpc)
VS Code version: Code 1.77.3 (704ed70d4fd1c6bd6342c436f1ede30d1cff4710, 2023-04-12T09:16:02.548Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: Yes
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (4 x 2400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.86GB (2.56GB free)

Process Argv
--crash-reporter-id 5beb9600-8880-40a9-ab9b-bda1e4070ff2

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (4 x 2400)

Memory (System)
1.94GB (0.40GB free)

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

remote-wsl
ms-
0.77.0

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30610678
nodejswelcome1:30587005
282f8724:30602487
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
a9j8j154:30646983
showlangstatbar:30672706
vsctsb:30705553
azdwalk:30721579
pythonms35:30701012
pythonfmttextcf:30716743

VSCode is impossible to use like this. Even restarting VSCode is no longer stopping this.

Ive narrowed it down as follows - as soon as a few pages are opened for editing, the issue starts. When I close the pages, it stops. And then the cycle continues.

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

(All extensions except WSL were uninstalled as part of my debugging before I raised this issue.)
Here's another update - the issue has completely disappeared. I downgraded to v1.76.2, and then VS Code updated itself back to 1.77.3 and now its back to normal. No persistent CPU usage anymore.

Closing since it sounds like the issue is not reproducible

And we are back with the exact same issue.

And we are back. This happened yesterday, but it wasnt for long.  No persistent CPU usage anymore since yesterday.

I am seeing this also on anything newer than v1.76. What would be useful information to collect and what would be the easiest way to do that?


Switch from HashMap -> FxHashMap for better compilation performance.

Rust's default HashMap Hash functions ( from SipHash ) are very slow since they do things like collision avoidance, and try to ensure uniform key distribution. These features seems un-needed, and for a library such as outlines-core focused on performance, it seems to be detrimental. Replacing the default rust HashMap with the hash map from rustc_hash makes this way faster, since it massively reduces hashing overhead.
Benchmarks Before & After:
| Change   | Before [617a2c8e] <0.1.19>   | After [175ea196] <main~1>   | Ratio   | Benchmark (Parameter)                                                                                |
|----------|------------------------------|-----------------------------|---------|--------------------------------------------------------------------------------------------------------------------|
| -        | 2.57±0.5s                    | 1.48±0.1s                   | 0.58    | bench_json_schema.JsonSchemaBenchmark.time_json_schema_to_fsm('complex_schema')                                    |
| -        | 1.35±0.5s                    | 786±70ms                    | 0.58    | bench_json_schema.JsonSchemaBenchmark.time_json_schema_to_fsm('simple_schema')                                     |
|          | 16.3±2μs                     | 15.6±0.3μs                  | 0.96    | bench_json_schema.JsonSchemaBenchmark.time_json_schema_to_regex('complex_schema')                                  |
|          | 6.10±2μs                     | 6.47±0.2μs                  | 1.06    | bench_json_schema.JsonSchemaBenchmark.time_json_schema_to_regex('simple_schema')                                   |
|          | 405M                         | 407M                        | 1.00    | bench_regex_guide.MemoryRegexGuideBenchmark.peakmem_regex_to_guide('complex_span_constrained_relation_extraction') |
|          | 401M                         | 403M                        | 1.01    | bench_regex_guide.MemoryRegexGuideBenchmark.peakmem_regex_to_guide('simple_phone')                                 |
| -        | 720±100ms                    | 351±10ms                    | 0.49    | bench_regex_guide.RegexGuideBenchmark.time_regex_to_guide('complex_phone')                                         |
| -        | 3.30±0.09s                   | 1.96±0.2s                   | 0.60    | bench_regex_guide.RegexGuideBenchmark.time_regex_to_guide('complex_span_constrained_relation_extraction')          |
| -        | 528±90ms                     | 279±20ms                    | 0.53    | bench_regex_guide.RegexGuideBenchmark.time_regex_to_guide('date')                                                  |
| -        | 387±50ms                     | 249±10ms                    | 0.64    | bench_regex_guide.RegexGuideBenchmark.time_regex_to_guide('email')                                                 |
|          | 381±60ms                     | 278±40ms                    | ~0.73   | bench_regex_guide.RegexGuideBenchmark.time_regex_to_guide('ip')                                                    |
| -        | 347±70ms                     | 216±6ms                     | 0.62    | bench_regex_guide.RegexGuideBenchmark.time_regex_to_guide('simple_phone')                                          |
| -        | 306±40ms                     | 207±9ms                     | 0.68    | bench_regex_guide.RegexGuideBenchmark.time_regex_to_guide('ssn')                                                   |
|          | 292±60ms                     | 253±30ms                    | ~0.87   | bench_regex_guide.RegexGuideBenchmark.time_regex_to_guide('time')                                                  |
|          | 479±80ms                     | 303±10ms                    | ~0.63   | bench_regex_guide.RegexGuideBenchmark.time_regex_to_guide('url')                                                   |

pyo3 already has built in conversion traits for FxHashMaps from rustc_hash, so python bindings / python usage does not change at all. All pre-commit hooks and tests pass.
This adds the dependency of rustc_hash, and the hashbrown feature of pyo3 for the conversion traits.

Thank you for the contribution! We'll review it shortly :)

@rlouf Actually it's okay to ignore it, it's just a coverage thing, which just notices changes in signatures.

I'm currently confirming a couple of things here, I'll leave a review mark soon.


New Release

Can you please make a new release? This is the only remaining dependency for mdformat-mkdocs that pins mdit-py-plugins to ^0.3, which is causing conflicts with mdformat-frontmatter which has recent fixes and a minimum of 0.4
If helpful, I opened a PR with a patch for CI: #30 (to address https://github.com/hukkin/mdformat-gfm/pull/28#issuecomment-1694216314)

Hey @hukkin , what's your opinion on granting @KyleKing maintainership of mdformat-gfm? He looks like a competent dev and is already managing a couple of mdformat-* plugins.

I'm happy to help as a maintainer!

The missing release has been a blocker, so I temporarily released mdformat-mkdocs (v2.0.1) with a copy of mdformat-gfm. Once the release of gfm is available, I can defer to this package and remove the copy
@hukkin, let me know if there is anything I can do help

Hi all, I've made a release.
Thanks for offering to help Kyle! :bow:    I invited you as a collaborator. I hope you can give me a couple weeks to review changes and only merge without a review if I still remain absent.

Thanks! Let me know if there is anywhere else I can help


￼

Coverage increased (+0.07%) to 92.925% when pulling bf1cd2db618c32d5e86d09c685108b30132f5b4b on outsideris:extract-authors into d0f04e994f3e78939f0a947ef064881c7fec5188 on mochajs:master.
Originally posted by @coveralls in https://github.com/mochajs/mocha/pull/4058#issuecomment-540079826

Coverage increased (+0.07%) to 92.925% when pulling bf1cd2db618c32d5e86d09c685108b30132f5b4b on outsideris:extract-authors into d0f04e994f3e78939f0a947ef064881c7fec5188 on mochajs:master.
Originally posted by @coveralls in https://github.com/mochajs/mocha/pull/4058#issuecomment-540079826

#4058 (comment)

Coverage increased (+0.07%) to 92.925% when pulling bf1cd2db618c32d5e86d09c685108b30132f5b4b on outsideris:extract-authors into d0f04e994f3e78939f0a947ef064881c7fec5188 on mochajs:master.
Originally posted by @coveralls in https://github.com/mochajs/mocha/pull/4058#issuecomment-540079826

#4058 (comment)

#4058 (￼
Coverage increased (+0.07%) to 92.925% when pulling bf1cd2d on outsideris:extract-authors into d0f04e9 on mochajs:master.
Originally posted by @coveralls in #4058 (comment)

#4058 (comment)


Auth store

Implemented the following things:

Added login form to app components.
Added authentication service that returns Promises related to authentication.

what's going on?

I made the pull request into the wrong repository by accident. Sorry for the confusion!


Issue with docs.zowe.org/stable/user-guide/api-mediation/discovery-service-configuration

Description

Pages to Update

Screenshots

Expected behavior

Additional context

Hi @SUNDONEcindy, can you please provide some additional information regarding the issue you're seeing in this page?

Closing this as it's been a month and we've received no additional information.


[WIP] API

[x] Migrate API to go-tide repo
[x] Ensure env variables are working
[x] Setup local environment
[x] Cleanup build script
[x] Add setup docs
[x] Remove Redis
[ ] Add Memcached
[ ] Setup GCP deployment & makefile
[ ] Test E2E
[ ] Update email in code of conduct + contributing

closes #37

Pull Request Test Coverage Report for Build 155

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 152:
0.0%

Covered Lines:
495

Relevant Lines:
495

💛  - Coveralls


Strange run._id Iteration Behavior With Multiple Observers

I've noticed that run._ids exhibit what is (at least to me) somewhat strange behavior when you have multiple observers which have different numbers of prior runs in them for a given experiment: namely, they take whichever observer was appended first, generate run._id as being that observer's max prior ID + 1, and then use that for both of the added observers. If you  have an observer with multiple runs within it, and decide you'd like to add another observer, let's say, a database observer, and you append the new observer before the old one, your code will break, because the new observer will generate an id of 1, which will throw a FileExists error within the FileStorageObserver.
At first glance, it seems like a possible fix here would be (at this line here: https://github.com/IDSIA/sacred/blob/master/sacred/run.py#L318), instead of adopting the run._id from the first observer in the list, instead to take the _ids generated by all observers, and then set the run._id as the max over all all returned observer _ids. However, this has the possibly undesirable property of breaking the coupling between run._id and each observer's notion of a run_id. This could maybe be fixed by having a separate observer method for "return max ID", since that would allow you to run that for each observer, get the max ID, and then call _started_event for each observer with id equal to that max ID. This has the nice property that IDs will be consistent across the set of all observers, since if observer 1 is already 15 runs in, and you add observer 2, it'll always automatically start at 16, regardless of the order of observer appending.
If the maintainers are up for having a PR submitted that implements something like this, I'd be up for taking on writing one. That said, I recognize this would be a decently involved bit of code surgery to fix what might be a niche issue, and that y'all might not prefer to go ahead with it. In that case, I'd advocate some warning box on the Observer page calling out the fact that you can see strange behavior when there are multiple run-offset observers.
(I've replicated the above-mentioned behavior in the code below with two FileStorageObservers, but from what I can tell in digging into the mechanics of the code, I'd expect this kind of issue for any observer that generates auto-incrementing IDs. To reproduce, first run the code as-is, and then run it a second time with the commented lines un-commented, so as to produce observers that are offset from one another in how many runs they have)
from sacred import Experiment
first_obs = FileStorageObserver.create("original_observer")
#second_obs = FileStorageObserver.create("added_observer")

test_ing = Experiment("cat_noise")
#test_ing.observers.append(second_obs)
test_ing.observers.append(first_obs)

@test_ing.config
def config_ing():
    noise = "meow"
    cat = "aegon"

@test_ing.automain
def make_a_noise(cat, noise):
    print(f"{cat} says {noise}")```

Thanks for reporting this issue! I believe that this would be worth a fix, but I also see that it might require extending the Observer interface. Right now finding the next id and creating the experiment is mangled into started_event. We would have to pull this apart and then take the max as you proposed. However, that would probably make the code a bit cleaner anyway. Something along the lines of
next_id = max(observer.next_id() for observer in self.observers)
for observer in self.observers:
    observer.started_event(next_id, ....)

We would also have to consider special cases, like overriding experiment with the MongoObserver. Please go ahead if you like to tackle this issue.

Observers are sorted by priority and the observer with the highest priority gets to choose the _id. The problem in your case is that you are adding a MongoObserver later on, which by default has priority over the FilestorageObserver.
If you are fine with the _id chosen by the FilestorageObserver, you could just reduce the priority of the MongoObserver to less than 20 (using the !15 suffix on the commandline or by passing a priority=15 argument to the constructor).
Otherwise, you could implement a custom observer with high priority that choses an appropriate _id in its started_event and does nothing else.

I was actually unaware of these priority semantics. Sorry for the misinformation.

@JarnoRFB Documentation on this could be a bit better I guess. Questions about the behavior of _id are rather common. Maybe we should add a section detailing the _id system and how to customize it?

@Qwlouse sounds like a good idea.


Update no-undef.js

propose to fix issue #4

Thank you for the commit.

Ah yes, thanks for the reminder.  Just published it as v0.1.0.

Ah, I see. This package is published as
https://www.npmjs.com/package/eslint-closure (no -plugin)
On Wed, Jun 27, 2018 at 2:26 AM Ron Apelbaum<EMAIL_ADDRESS>wrote:

I still don't see it in npmjs...
https://www.npmjs.com/package/eslint-plugin-closure
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/eslint-closure/pull/3#issuecomment-400605483,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABXcblxilWIicI4E2VUbqwLJOQElNKNks5uA0-wgaJpZM4UvPvK
.

I think I just need to publish the subpackages.  Gimme one sec.

Ok, everything is updated to v0.1.1

Hi @jschaf
it appears that although you've re-published the package, the dist/closure-eslint-plugin.js still doesn't contain my changes..


Advertise support for "cache versioning"

Introduced in https://github.com/rails/rails/pull/33943 Rails will attempt to interpret if a cache store supports "cache versioning" by looking for the predicate method supports_cache_versioning? on the cache store class. This PR advertises support that was introduced in https://github.com/petergoldstein/dalli/pull/698.

@schneems Thanks.


Variance bug

Summary
The variance in the Pauli_expectation.py is calculated with a bug. It uses the sqrt of the coefficients rather than the squares.
See https://arxiv.org/pdf/1704.05018.pdf supplement V for further details.
Details and comments

Accidentally created the branch for this PR from a different feature branch instead of from operator_refactor. Will re-do this at some point


Sorting data with decimals

Major Issue

when filtering through the data and sorting if a decimal is in the search criteria an error occurs
find the error and resolve the issue

    # filter the data by Age and further filter it by ages 20 to 70
    search_criteria = 'Balance'
    search_value = [900, 7000]
    # return an array of dictionaries of all data that meets the filter
    # criterias
    search_field = sorted_data.search(search_criteria, search_value)

Traceback (most recent call last):
  File "index.py", line 68, in <module>
    main()
  File "index.py", line 51, in main
    get_minimum_age = sorted_data.get_minimum_value('Age', search_field)
  File "/Users/jesseokeya/Documents/DataPlayground/src/sort.py", line 101, in get_minimum_value
    minimum_num = int(sorted_data[0][search_field])
IndexError: list index out of range

Issue Solved!!


added hide settings for line1/line2 in activepedom widget

Thanks! Nice clean addition :)

Thanks! Nice clean addition :)


add option to nice builds

Would be nice to have option in config to nice builds before running them. This can be done by just running "nice poudriere" instead of "poudriere" but I always forget. Having an option in config to have it do it automatically would be nice to have.

Absurdly simple hack of this in https://github.com/ceri/poudriere/commit/e44693288337fb697a5518b813e88bd1cd9acfb0


Kill switch at signing page

Is your feature request related to a problem? Please describe.
I find the dashboard really useful as a VPN kill switch. If I want to make my home network unreachable remotely, I just log on the app and tap the switch of the main wg configuration. This can be useful if you are physically under duress outside, you disable wireguard from the dashboard quickly and the bad guys cannot access anything even if they are threatering you. You will be able to restore the VPN later at home.
The problem is that I need to be logged on the dashboard to do that, it takes quite a bit of time to log in and tap the switch.
Describe the solution you'd like
I would find really cool to have a kind of "emergency button" on the signin page of the dashboard. It could be one emergency button for each configuration to disable them, or it can be only one switch to disable everything.
If you don't like the idea of having such button on the signin page, you can unset it by dfault and add an option to display it on the signin page for people who wants to have that.
It needs to be large enough but maybe not too obvious that this is a kill switch (like the text on the button could be just the name of the wireguard configuration it would kill)

Hi, this is an interesting idea. I'll look into it and to see how can I implement this ;) Thank you!


igdm application is not showing the chat list

sameeeeee

There's a new version of the application (2.4.3)

Refer to #235

Please Install the latest version from http://igdm.me


Extension is no longer available on the Chrome Store

Clicking on the Chrome Store link on the GitHub page leads to a 404 page:

https://chromewebstore.google.com/detail/japanesetab/jndamehabjcbgopalgabjpplldmjnnfn
For those who still want to use it, it's still possible to install the extension using Google Chrome's Developer Mode. By opening the Extensions page on your browser and enabling developer mode, you unlock the ability to load extensions from the file system. To install the extension this way, you must clone the Git repository to your PC and browse to the folder when prompted by the "Load unpacked" button.
Can you please reupload the extension so it may be used again by end users? Thank you!

Thank you for bringing this to my attention, looks like it's been down for 2 years 🙃 It's back up now.
https://chromewebstore.google.com/detail/japanesetab/jndamehabjcbgopalgabjpplldmjnnfn/related


Fix issue with resume combined with @parallel

@parallel uses the control task as a mapper task. This was not a situation the resume functionality for UBF handled well.
In the process, also cleared up some other bugs that could have cropped up later.
This should replace #2159.

Can we add on one more fix to handle the issue with @parallel inside of a foreach?
The regex in clone_original_run does not handle indexing properly in this case, causing the issues @saikonen and I were observing that lead to duplication of the @parallel task on resume, when it is inside a foreach. Currently the scheduler clones this task, but then doesn't find a hit in the index and runs only that task again.
The regex here can be replaced with this:
cloned_task_pathspec_index = re.sub(
      r"(\[\d+,\d+\])|(\[[^]]+\])",
      lambda m: m.group(1).replace(",0]", ",None]") if m.group(1) else "[None]",
      cloned_task_pathspec_index
  )

S3 tests are borked regardless of PR. Netflix tests are running fine (flaky issues).


Document delta kds flag

Description
This was missed in 2.2 I think.

It's missing here https://github.com/kumahq/kuma/blob/master/pkg/config/app/kuma-cp/kuma-cp.defaults.yaml let's see if can write a test to avoid this problem in the future.

done by https://github.com/kumahq/kuma/pull/7085 and also set as default