podman-1.3.2-1 busts --tmpfs=/var

I just noticed all my podman containers failed to come back up after the podman-1.3.2-1 release to RHEL 7.  I had to remove --tmpfs=/var...options in order to get podman to start without error... but that breaks things for those of us running systemd in a container... or depending on /var being a tmpfs for anything else.
I had previously posted about this in issue #2996
Anyways, this release is DOA for me at least - will try some workarounds before downgrading.

Can you get specific error messages?

Error: container create failed: container_linux.go:336: starting container process caused "process_linux.go:399: container init caused
"rootfs_linux.go:58: mounting \"tmpfs\" to rootfs \"/srv/machines/roots/php54/root\" at \"/tmp/runctop604820653/runctmpdir9856
91176\" caused \"tmpcopyup: failed to copy /srv/machines/roots/php54/root/var to /tmp/runctop604820653/runctmpdir985691176: write /t
mp/runctop604820653/runctmpdir985691176/cache/yum/x86_64/7/epel/gen/primary_db.sqlite: no space left on device\"""

May be worth noting I am using --rootfs  --rm=true --read-only

Tmpcopyup is running out of space copying up the contents of /var/ - eek.

There are other problems too...  the above error message is what I get if I use just --tmpfs /var  which I was only using to test out the new podman.  If I use what I want to actually use: --tmpfs=/var:rw,nosuid,nodev,size=524288000  I get this error: Error: nosuid: duplicate mount destination

That looks like a parsing error on our end - from the error format, it seems like we're actually trying to mount to /nosuid in the container, instead of parsing it as an option. Double eek.

I only get the "parsing error"  with both specified:  --tmpfs=/var:rw,nosuid,nodev,size=524288000   --tmpfs=/tmp:rw,nosuid,nodev,size=524288000

Ok - if I remove /var/lib/cache from my --rootfs image (uses 133MB - yum related it seems), I can get --tmpfs=/var:rw,nosuid,nodev,size=524288000 to work
Which is weird... but I can at least work with that.
Leaving the inability to to specify both --tmpfs=/var:rw,nosuid,nodev,size=524288000 --tmpfs=/tmp:rw,nosuid,nodev,size=524288000 as the remaining problem....

I can duplicate the parse error as follows:
sudo ./bin/podman run -t -i --tmpfs=/var:rw,nosuid,nodev,size=524288000 --rm --tmpfs=/tmp:rw,nosuid,nodev,size=524288000 --read-only fedora bash
(ignore the bin/podman here, that's my development copy)
Looking into it

It's StringArray vs StringSlice again.
@baude We have to do a survey for this, it's broken us a lot.

Fix for the parsing issue in #3435

Just using  --tmpfs=/tmp:size=524288000 works and results in the nosuid,nodev,noexec stuff defaults - so I have a workaround for that too now.
I know that podman is considered "experimental" in RHEL7 - so breakage on updates is to be expected, but I need to get this stuff in production soon - so am considering excluding podman from auto yum updates.  Any idea as to when/if it will be out of experimental status?

Actually - using --tmpfs=/tmp:size=524288000  --tmpfs=/var:size=524288000
Works without having to remove /var/cache as specified above - seems to indicate all of the above is parser related


Error: No module named 'faster_whisper'

Amateur question: When I execute the script ("python3 bulk_transcribe_youtube_videos_from_playlist.py"), I get the following error:
No module named 'faster_whisper'
Tried installing it via "python3 -m pip install faster_whisper"
Still module cannot be found. What am I missing? Thanks!

Are you running Linux? You should paste the entire block of commands from
the instructions that include creating a venv. If you just paste the whole
readme into ChatGPT it will explain what to do.
On Wed, Jan 17, 2024 at 3:20 AM LennartWer @.***> wrote:

Amateur question: When I execute the script ("python3
bulk_transcribe_youtube_videos_from_playlist.py"), I get the following
error:
No module named 'faster_whisper'
Tried installing it via "python3 -m pip install faster_whisper"
Still module cannot be found. What am I missing? Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/Dicklesworthstone/bulk_transcribe_youtube_videos_from_playlist/issues/5,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AILNF3QFGJ7USLD6OQHCGUTYO6CUXAVCNFSM6AAAAABB6DLP3GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA4DKNRVGUZDCNY
.
You are receiving this because you are subscribed to this thread.Message
ID:
<Dicklesworthstone/bulk_transcribe_youtube_videos_from_playlist/issues/5@
github.com>


jdspec tool needs to enforce register ranges

Just lost a few hours figuring why a RO register wasn't being updated and it was a reserved range issue.

@mmoskal are we set on ranges?

backround: i assigned a readonly address to a rw register.


[FAB-16844] Correct BYFN CC name/Add cli for org2

Correct chaincode name regexp in byfn.sh
Add in the useful cli for org2 in first-network

Change-Id: I6904db1786ae431f8a7069296ff610695d5a72c0
Signed-off-by: Matthew B. White<EMAIL_ADDRESS>

/azp run

/azp run

/azp run

/azp run

Hi,
I like having the org2cli too but without BFYN making use of it it's not that useful.
I had a chat with @nikhil550 a while ago and he agreed that we should move towards separating the operations done by the different orgs from one another and not use the same cli for both because that's not how a production system would get setup.

@lehors The new test network: https://github.com/hyperledger/fabric-samples/pull/80 actually removes the fabric tools cli all together. Removing the cli container makes it easier to install chaincode, create channels, and edit channels without having to be worried on what you mount in the container. The certificates are still different for each org, which requires you to set different environment variables depending on which org you are operating from.

Right, I actually meant to say that at the end of my comment but had to get on a plane and ended up posting it without it. My bad.
So, to finish my thought, given that direction there is no real value in adding the org2cli. I suggest dropping it from this PR.

The current chaincode container cleanup leaves the fabcar chaincode images if you use the fabcar tutorial. That part of the PR would be welcome. Those changes are in the new test network.

Will delete this PR and recreate one with just the byfn.sh cc name changes


Use F1 based reward distribution for v1

Background
We initially delayed the idea of using an F1-based reward distribution mechanism for Osmosis due to concerns on the timeline, but I do think we can adopt the F1-based module without significantly delaying the launch schedule. I believe there are minimal benefits of an epoch-based system over the F1-based system, and only opens up spam attack risk vectors as well as instability in the block times due to the iterations required.
The x/farm module provides a much more sustainable and manageable architecture, and I've made progress on the implementation that I believe it will create no delays for launch. (Refer to the pool-yield branch)
Below is an outline of how the current architecture functions.
Farm Module

Other modules create a farm
Farm module doesn't custody the shares, but the rewards are managed(and custodied) by the farm module
Farm module is created by an external module, but external accounts can provide additional incentives to farms that are already created
Users can request the farm module for unclaimed rewards

Pool-Yield (to be changed to Pool Incentive) Module

x/gamm afterPoolCreate hook created.
Pool-yield module sets the lockableDurations at genesis (i.e. 1 week / 2 week / 4 week)
Pool-yield module creates a farm (according to the number of lockableDurations) when the x/gamm afterPoolCreate is run
lockup module

onTokenLocked  - When the hook runs this, the pool-yield module checks if the locked token is the pool share token. If it is a pool share token, then it will check if the duration matches the  lockableDurations. If both conditions are true, it will get the farm and add the farm share according to the locked poolShare amount. (Because the farm module doesn't custody the farm's share, the lockup module custodies the shares.)
onTokenUnlocked  - This is the opposite process of onTokenLocked.

External accounts can query the x/pool-yield module by specifying the poolId and lockableDurations and find the farmId.
x/farm module supports external incentives, but the incentives must be added on a regular periodical basis for the duration that the additional incentives is active (i.e. reward added once per day).
AddPoolIncentives proposal can be used to add records. The records consist of farm Id and weight. When the record is added, reward is allocated according to the record's farm ID. The reward amount equals to weight/ totalWeight.

To consider the potential the amount of farms/lockable duration increases, the pool-yield module uses an unnormalized weight since normalizing becomes fairly inconvenient when the number of farm becomes large.

RemovePoolIncentives proposal is the opposite of the above proposal
Because feeCollector manages the entire minted inflation in the same module account as the previous block's transaction fees are handled, and the distribution module take the entire remaining amount that's left in the feeCollector module account, the pool-yield module's begin block must be run between the mint module and the distr module's begin block.
The pool-yield takes the mintedDenom according to the allocationRatio from the feeCollector module account then distributes the amount to farms according to the logic described above, then the distribution module uses the remaining amount.
Issue (TODO):

Each module has a specific set of order that it takes its allocated amount in
The allocation taken by each designation (i.e. pool incentives, developer DAO, etc) is relative to the remaining amount
Therefore, setting the parameter is not very logical:

i.e. 100 OSMO minted, 50% liquidity incentives, 20% developer dao)

liquidity incentives take the 50%
Developer dao parameter must be set to 0.4(40%) because the liquidity incentives already took half, and only half is remaining (20% of total, but relatively 40% of the remaining minted amount)

feeCollector account manages the transaction fee and the inflation minted amount in the same account, and can't know which % is the transaction fee. Therefore, the transaction fees are distributed in the same allocationRatio as the minted inflation amount.

If the mint module can specify the amount that is to be allocated to pool-yield/developer-dao, then this should be able to be resolved.

ACTION ITEM → merge new mint module implementation to Osmosis-Labs repository

[ ]  Create updatePoolIncentives proposal type.
[ ]  Need to create more CLI and gRPC queries
[ ]  DeveloperDAO (should be easy lift)

Discussion

It'd be good for the lockup module to send tokens that have expired lockup at each block, rather than having each user to manually unlock their tokens. (Because the amount of lock tx that can be included in a block is limited, and the amount of  unlock depends on the amount of lock, this alleviates concerns about spam)

Needed because the pool-yield module needs to remove expired lockup LP shares out of actively incentivized farms. and if this isn't done automatically, the pool-yield module needs to take care of this and having the lockup module handle this would simplify the design significantly while also making it easier for users.

Closing in favor of #542 existing


Set up unsuccessful

Any suggestions? Thanks

This looks like that there is a problem with permissions, which is preventing the supervisor process from starting those tool processes (jupyter, nginx...). This can happen if you have changed the root user to a different user (currently only the root user is supported, as explained in the FAQ section here). Or maybe you have mounted a volume into the home directory or any directory other than /workspace. Do you have additional information on your setup, e.g., docker run command, cloud provider or local computer? Is there any other error within the logs that might be related to permissions?


How it's different from Pixi Projection plugin?

Could you please explain in few words how Pixi3D is different from Pixi Projection plugin https://github.com/pixijs/pixi-projection?

Pixi3D was created to render 3D objects in a 3D world. It can load models created with a 3D modelling tool like Blender or Maya.
Pixi-projection was created to display 2D images with a 3D perspective/projection. I have not used pixi-projection myself, so my explanation may be too simplified.

For project like Spades (card game)

Would you suggest to use 2D plugin or your 3D renderer? Asking for a friend.

Both will probably work. That game is simple enough to create a small prototype with both libs and then you can choose the one you like most.

Thanks!


Contain nested rows to grid

This commit removes a single line that was recently added that results in the following style:
.row .row {
  max-width: none
}

The line was added in response to #8304. However, the appropriate solution would have been to add the expanded class to nested rows. Setting max-width to none introduces a break. If a nested row needs to be full width, the expanded class can be applied to that row; however, if nested row max-width is set to none, there's no way to contain a row to the grid inside of an expanded row.
If a row is nested inside of an expanded row, it should be contained to the grid unless the expanded class is explicitly added to the nested row.
This fixes #8886

For further reference, here's how this has worked up until 6.2.1. The expanded class already sets max-width:none so applying it to all nested rows is too broad.

```

:+1: I agree; this commit was a mistake.

@gakimball, are you okay with reverting this and requiring .expanded to fix nested rows? Other ideas?

I'll take this one! I'll test it and see if it's the way to go.

@rafibomb I believe this fix also needs to be made for the flex grid in _flex-grid.scss around line 165

@rafibomb I think there is a related issue on the flex-grid. It's missing the margin-left and margin-right for nested rows inside an expanded row.
In _flex-grid.scss around line 165 I think you need to add the margin stuff for the nested row:
    // Expanded row
    &.expanded {
      max-width: none;

        .row {
            margin-left: auto;
            margin-right: auto;
        }
    }

Small little anecdote that doesn't really change anything here...
We added a temporary fix for this which explicitly adds a max-width back to .row .row
which we just realized overrides the nested expanded rules which prevents us from doing nested expanded rows :(
If we get rid of our temporary rule, though, we're back to square one.
best bet is to undo that pesky one-liner


Align Constrained Execution Region with netcore for merging netcore/netfx

Attempting to align CER changes from netfx to netcore for code merging

Unfortunately it seems the diff that github creates looks really complicated.
The changes are not complicated at all...   I'll probably try to simplify this with multiple smaller PR's after gathering some feedback

Please use ?w=1 in the GitHub URL to ignore whitespace changes, and the diff looks much much cleaner!!

I'm not sure what your plan is for actually merging the two files after it the files are modified enough to look like each other.

Ideally, all the code is of course identical in the end, so you can just take one version of the file and move it to the shared project. But even if it's not 100% identical, doing it this way, and slowly aligning them still (IMHO) is a low-risk way to ease the way to merging them in the (hopefully near) future. If you think this is not a viable way to go - I'll stop with these, that's not an issue for me

My thought is that if there's something that can be done the some on netcore and netfx, we should try to get them doing things the same way (without making huge changes to the code). If it can't be done the same in both, eg constrained execution is only needed in netfx, then the merged version should have the constrained execution specific code wrapped in #if NETFRAMEWORK.
I'm happy to wrap them around #if NETFRAMEWORK, if that's the issue.
While deciding what to do, I was looking at the TdsParserStateObject.netcore.cs file, for example here:
https://github.com/dotnet/SqlClient/blob/17427932d35495675cf9f8d10e7d6ea939d35f3b/src/Microsoft.Data.SqlClient/netcore/src/Microsoft/Data/SqlClient/TdsParserStateObject.netcore.cs#L312-L320

it does not wrap the call into a conditional.
On another note, What does the #if NETFRAMEWORK give you in this case here?
We do agree that a merged version needs to have the CER in for netfx support, right? So it needs to be there.
The methods are marked as [Conditional("NETFRAMEWORK")], so they get optimized away in the netcore version, right?
To the point: the code also has a lot of Debug.Assert, and they are not wrapped in #if DEBUG
Just let me know what you prefer, and I'll adjust to that

@MichelZ Sorry if I sounded a bit harsh previously - I definitely appreciate the effort you're putting in, but just want to make sure we're working towards the same goals. It's also worth noting that I've only been (sorta) in charge of merging the two projects for a month or two. If there's an difference between older merging and newer merging, that's likely why. So, to address your points:

I think it's nice if we can have the code be identical, but it won't always be beneficial to have it be identical.

Eg, if netfx uses byte[] while netcore uses Span, we could migrate netfx to the Span. In that case, we still have the same functionality in netfx and netcore, but just aren't doing it with the same code.
Eg, if netfx does something extra that is not needed or not compatible with netcore, then we should retain the netfx code, wrapped in an #if NETFRAMEWORK. In this case, we want to only include the functionality in netfx, and make it clear that it only applies to netfx.

I'm honestly not super sure how much the compiler optimized away [Conditional] methods. I agree that it optimizes out the method, but since there's nothing else in that class, does it also optimize out the class?

Although in most cases we don't wrap Debug.Assert in #if DEBUG, there are a handful where we have to. Even if Debug.Assert becomes a no-op, expressions assigned to the arguments are still evaluated, even if they don't compile.
Ultimately, my philosophy on [Conditional] is that it's less obvious when reading the code that the call to a [Conditional] method does something verses doesn't do anything. Wrapping the method and calls to it #if NETFRAMEWORK makes it abundantly clear that the call only applies to one framework, and makes it easier to find blocks of similar functionality if we ever drop netfx support.
If it seems like there's a disconnect between Debug.Assert and other conditional method, I think it's mostly because Debug.Assert comes with the framework, and it's behavior is well known, regardless of the project we're working on. While it's fine to have project-specific conventions (ie, "oh this method doesn't do anything in netfx"), we can cut down on the learning curve and gotchas. For a project of this size, any reduction to those is greatly appreciated.

Re TdsParserStateObject.netcore.cs, that seems to me like an oversight. That class is obscenely large, so it doesn't surprise me something slipped through while merging it.

Understood, thanks.
I'll wrap them in #IF NETFRAMEWORK to make it clear then


Encryption ignored in iOS notification extension

Hello, I'm using Xamarin.iOS and noticed that opening a database connection with an encryption key does not work in iOS notification extensions, and instead the database will try to open without the key, as an unencrypted database. If creating a new database inside the extension, it works fine, but just ignores the key. Strangely enough, encryption does work in the iOS share extension. I've tried using cipher compatibility set to 3 and it didn't work. Any thoughts on what specifically about notification extensions might be blocking sqlite-net's ability to encrypt and decrypt? I'm on sqlite-net version 1.8.116 and iOS version 15.5. Thanks!

Hello @DemonicCoders can you provide a simple reproduction project that demonstrates this issue?


Sliders don't persist

I'm finding that my sliders don't persist over time -- when I create them, a couple of days later i see e.g. this:

instead of the actual slider. The content of that block is this:
[:span {:is "slider-uerfpdbe"}100]
value:: 60

To fix this I basically have to delete the first line and re-insert it, which is time-consuming of course.
For reference, in this case I have used block refs to display the same block elsewhere on the page (a table showing progress of multiple sliders). Perhaps that has something to do with it?

Apologies. Fixed in 1.0.3.


Port Description
The zlib data compression library provides in-memory compression and decompression functions, including integrity checks of the uncompressed data. A modified version of the zlib compression library is used by zEDC. The IBM-provided zlib compatible C library provides a set of wrapper functions that use zEDC compression when appropriate and when zEDC is not appropriate, software-based compression services are used.
Upstream Repository URL
No response
Additional Information (Optional)
This project only exports the IBM zedc flags, header and library paths.

Repository created: https://github.com/zopencommunity/zedcport


Use server for model validation

Our models are complex and have complex relationships to each other. Let's use Django-MPTT to do our validation on the server side.
This will involve doing saves, doing the validation on the server, and then properly handling error callbacks from the save request.

Are we still doing this given the problem with unique_together?

I still would like to avoid duplicating validation logic - but in the case of titles, it seems unavoidable to only do this on the client side.


Third priority: Update as much as possible based Ilona mocks

Contacts and credentials tabs, and verification button on the credential details all need better icons that avoid text if possible

See Ilona mocks https://www.figma.com/file/LHCGgzmUOnDuqs421g7sg2/Roots-id?node-id=0%3A1&t=DzTGtYE5gqTwihqQ-0


Relative URLs should not be used in feeds

Describe the bug
The Pixiv bridge caches images in a directory and returns a relative path to them. This works fine when displaying HTML but when reading the Atom or Mrss feeds, the readers I've tried treat the URLs as relative to the rel=alternate link which gives a 404.
To Reproduce
Steps to reproduce the behavior:

Generate a feed with the Pixiv bridge (e.g. https://rss-bridge.org/bridge01/?action=display&bridge=PixivBridge&context=User&userid=5611165&posts=10&mode=all&format=Html)
Add the Atom or Mrss feed to a feed reader
The image links appear as follows: https://www.pixiv.net/tags/cache/pixiv_img/100299997.jpg

Expected behavior
Images should be served with absolute paths.
Desktop:

OS: Debian 11.3
Browser: Firefox
Version: 103.0.1

Additional context
Both FreshRSS and newsboat parse the URLs this way. I can test other feed readers if necessary.
IMO a CacheInterface implementation that saves files and handles their URLs for you would be nice.

Thanks. Fixed.


[❓, 🚀] Use C code(Cython or mypyc) instead of full CPython ?

Hi, @RobertoPrevato!
I've been testing different ways to run rodi: CPython, PyPy, mypyc. And I got interesting results :)

CPython3.10: 0.28 - 0.33 average
mypyc 0.950: 0.13 - 0.16 average
PyPy3.9: 0.08-0.09 average

Benchmark
To run mypyc I fixed couple mypy issues: commit
Do you think this performance boost matters ?
Should some code be rewritten using 'Cython'?
Benchmark code:
from timeit import timeit

from rodi import Container

class A:
    pass

class B:
    def __init__(self, a: A):
        self.a = a

class Dog:
    def __init__(self, b: B):
        self.b = b

class Cat:
    def __init__(self, dog: Dog):
        self.dog = dog

container = Container()
container.add_transient(A)
container.add_transient(B)
container.add_transient(Dog)
container.add_transient(Cat)

services = container.build_provider()  # --> validation, generation of functions

cat = services.get(Cat)

print(
    "services.get(Cat)",
    timeit(
        "do()",
        globals={"do": lambda: services.get(Cat)},
        number=100_000
    )
)

# Before mypyc: 0.28 - 0.33 average
# After mypyc:  0.13 - 0.16 average (mypyc rodi)
# Diff: ~2 times

mypy --version -> mypy 0.950 (compiled: yes)

Hi @MaximZayats Thank You for this contribution!
Yes, I find this very interesting. 🎉
Using mypyc or Cython comes at a price though, for example that the package will require a bit more complex CI / CD pipelines (like BlackSheep's one), to distribute wheels. Therefore before opting-in for this, I wish to verify what is the performance boost of only resolving the services, without the build_provider() step.
Because the performance improvements of building a service provider is not so interesting, because this action is done rarely - generally once at application start-up.
I never tried mypyc and I'm going to try it, cloning your fork.

It looks very promising, if you make a pull request I'll be happy to merge your changes with type annotations.
I need a bit of time to consider whether to change the distribution package, though.

Hi @MaximZayats
Thank You again for your help. Sorry for taking several months, I struggled to find time for my open source projects lately. I am working to include mypyc in 1.1.4 - I am still resolving a couple of issues related to distributing compiled libraries instead of Python source code.
Anyway I can close this issue now, since your contribution has been merged to main.

Hi @MaximZayats
One more thing. I just noticed that, probably because I squashed the commit with the pull request or because I forked your fork to apply minor changes for linters, I lost track of your contribution in the git history. I will try to re-write the history of main to give you credit.

Done! Quel che è giusto, è giusto.

Hi @RobertoPrevato
Thanks for the release!
I tried to test the new version, but realized that it has not been released on pypi yet.
When do you plan to release it ?

Hi @MaximZayats
As soon as possible, as I wrote before I am still resolving a couple of issues related to distributing compiled libraries instead of Python source code.
If you take a look to the GitHub Workflows, you'll see that I already modified it to build wheels for several distributions of Linux, (manylinux Docker image), Mac OS, Windows. But I am still missing the step to:

create a pure Python distribution wheel
remove the Python source code from wheels that has the extension (I thought the compiled version would take precedence when installed, instead the source code takes precedence)

Nothing complex, I only need to apply a small change to the setup.py file and the wheel building steps.

Maybe implement acustom pep517 backend with build_wheel function?

Thanks for the recommendation, yes I think it's high time for me to start using pyproject.toml 😄
Another option I am considering is to distribute a stub-only package , alongside the C version of rodi.

I write an update here. I tried pyproject.toml using hatch, and they are capable of generating a wheel without __init__.py (necessary to distribute the optimized version) 🎉 . I verified this on a test package, a "stub-only" package used to distribute a single .pyi file. Apparently it is a limitation of bdist_wheel that it cannot generate a wheel respecting source code exclusion.
I'm going to improve this project to use pyproject.toml and the workflow accordingly.

Hi @MaximZayats and @q0w
Finally I am not going to distribute wheels having compiled versions of rodi, because the tests suite does not pass with the compiled version, it goes into segmentation fault. Anyway mypyc is alpha software and they don´t recommend it for general production use.
I was already planning to create an abstraction layer around the protocol of rodi, to support different kinds of DI containers in blacksheep. When that is done, I might distribute an alternative alpha package containing extensions built with mypyc, under a different namespace.
Thank You again for the interesting input! I learnt several new things thanks to you.


fix: Do not validate evaluator

There are some cases that contain more than 1 evaluator. It is to fix it.
/assign @ChanYiLin @terrytangyuan
Signed-off-by: cegao<EMAIL_ADDRESS>

Coverage decreased (-0.4%) to 71.479% when pulling 9bebb8a2f1af1052c4c21c19347ff5f1f8b2d119 on gaocegege:validator into 6a608a789930232ff05f4f04aa31eea845f99b20 on kubeflow:master.

/cc @oikomi


Code coverage integration with codecov

At first I tried to use OpenCover to calculate code coverage. But it doesn't run on Linux and faced some trouble running the script on Windows machine too. So now using coverlet for code coverage. So far working good.
Although  Web project's coverage is not calculated. May be because it is not referenced by the UnitTests test project.

May be AppVeyor is not building the Application. It shouldn't complete that fast. Moreover it doesn't show any logs, just build successful


Possible typo in the README

Hello,
The README states:

The GDS Accessibility team found that only ~30% of issues are found by automated testing.

But the blog post states:

While the tools picked up the majority of the accessibility barriers we created – 71% – there was a large minority that would only have been picked up by manual checking.

Should the README be changed to say that "~70% of issues are found by automated testing"?
Apologies if I misread or missed anything.

https://alphagov.github.io/accessibility-tool-audit/index.html
At best 40%


Expansion Panel hideToggle typo in docs

Bug, feature request, or proposal:
bug
What is the expected behavior?
the docs should say hideToggle
What is the current behavior?
toogleHide
What are the steps to reproduce?
https://github.com/angular/material2/blob/385272e5d3fb820a3cac52de6a5b1b852f0ef703/src/lib/expansion/expansion.md
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?

I think you're looking at @julianobrasil's unmerged PR https://github.com/angular/material2/pull/5823 as that file does not exist on master

😄 I'm going to fix the PR first thing in the morning. Thank you guys.

@willshowell thx! Forgot to mention that 😁

Fixed.


chore(main): release never-bot 2.6.0

:robot: I have created a release beep boop
2.6.0 (2024-05-13)
Features

Update dependencies and improve chatbot response handling (032cfd9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/neverased/NeverBot/releases/tag/never-bot-v2.6.0 :sunflower:


Error when uploading not sent back to the user in the front-end

I have this error when uploading:
15:25:50.202 [..ting.EditBatchProcessor] Requesting documents (1ms)
15:25:50.296 [..ting.EditBatchProcessor] IO error while editing: /…/Transferts (AQM)/2024-05 (Is a directory) (94ms)
15:25:50.422 [..ting.EditBatchProcessor] IO error while editing: /…/Transferts (AQM)/2024-05 (Is a directory) (126ms)

But I get nothing in the front-end.
Regards,
Antoine

Also, I have this error message that is not relayed to the front-end, but even if it was, I don't understand what’s the problem with the file name…
16:32:31.558 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_Carton_d'invitation_pour_«_Bastien_et_Bastienne_».jpg"} (69690ms)
16:32:42.236 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_Marionnettes_de_«_La_Boîte_à_joujoux_»_dans_les_décors.jpg"} (10678ms)
16:32:53.609 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_Programme_de_«_Bastien_et_Bastienne_»_de_Jacques_Chesnais.jpg"} (11373ms)
16:33:00.627 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_Programme_de_«_Les_Comédiens_de_bois_»_de_Jacques_Chesnais,_argument_de_la_pièce.jpg"} (7018ms)
16:33:03.326 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_Programme_de_«_Les_Comédiens_de_bois_»_de_Jacques_Chesnais,_distribution_des_rôles.jpg"} (2699ms)
16:33:04.473 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_Manipulateurs_de_«_La_Boîte_à_joujoux_».jpg"} (1147ms)
16:33:19.697 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_Affiche_de_«_Tintin_et_le_Temple_du_Soleil_»_en_anglais.jpg"} (15224ms)
16:33:41.356 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_«_Tintin_et_le_Temple_du_Soleil_»_de_Micheline_Legendre,_pour_Marionnettes_en_vitrine.jpg"} (21659ms)
16:33:57.972 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_«_Tintin_et_le_Temple_du_Soleil_»_de_Micheline_Legendre_pour_Marionnettes_en_vitrine_(2).jpg"} (16616ms)
16:34:09.691 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_Micheline_Legendre_avec_la_rose_du_«_Petit_Prince_».png"} (11719ms)
16:34:13.316 [..ting.EditBatchProcessor] Requesting documents (3625ms)
16:34:14.478 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_Le_Théâtre_«_Tintin_»_au_Parc_Lafontaine.jpg"} (1162ms)
16:34:15.432 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_Vitrine_de_Noël_de_«_Tintin_au_Tibet_»_1964.jpg"} (954ms)
16:34:19.638 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_«_Tintin_au_Tibet_»_au_Jardin_des_merveilles.jpg"} (4206ms)
16:34:30.142 [..ting.EditBatchProcessor] MediaWiki error while editing [Warning]: The file upload action returned the 'Warning' error code. Warnings are: {badfilename="ML_«_Hansel_et_Gretel_»_à_Stratford.jpg"} (10504ms)

Regards, Antoine

So, for the second problem, I figured out. It was the use of non-breakable spaces that are often used in French.
I think OR should warn the user about that…
Regards, Antoine

Commons disallows non-printing characters in the filename. IIRC the validation of this is all handled in FileNameScrutinizer which reflects the default values of wgLegalTitleChars.
That doesn't undermine the problem raised here of surfacing the errors in the frontend =)

The problem of surfacing the errors in the frontend should be addressed by https://github.com/OpenRefine/OpenRefine/pull/6555, although I did not test it specifically for media files upload. I wonder if @antoine2711 or @Vesihiisi would be interested in trying it out?

@lokal-profil @antoine2711 I have tested my PR https://github.com/OpenRefine/OpenRefine/pull/6555 with Commons upload and made some tweaks to improve the UX there.
See the screenshots there. Any feedback welcome.

@lokal-profil @antoine2711 I have tested my PR OpenRefine/OpenRefine#6555 with Commons upload and made some tweaks to improve the UX there.

I’m waiting for the next version that can load the Commons extension.
Regards, Antoine

@antoine2711 there is a new release for the Commons extension which should work with OpenRefine 3.8 and the development version of OpenRefine (master branch)

I took the latest OR snapshot (#2442) and tried uploading a file with a tab (0x09) in the name.
Some thoughts on the experience:

After assembling my schema, I got a warning in the Issues tab, which was nice. But I worry the warning would be not informative enough for inexperienced users.

I was still able to proceed to the upload stage, even though OR knows the filename won't be accepted by Commons. I was only uploading this one file, so ideally I shouldn't be able to start the upload at all.

I appreciate the new "Wikibase editing results" column, but the content is not helpful for inexperienced users.

[Warning] The file upload action returned the 'Warning' error code. Warnings are: {badfilename="Skövde_stadsbibliotek_interior-01.jpg"}
Again, if I didn't know about non-printable characters, I wouldn't be able to guess the reason for the error. I guess that's the raw error returned by the API.
I think the pain point is the fact that I was allowed to start uploading the file in the first place.

We used to have this warning with the highest severity level ("Critical") which prevents the user from doing the upload, but because our regular expression catching invalid characters had false positives (flagging characters which were actually allowed, https://github.com/OpenRefine/OpenRefine/issues/5656) we changed it to "Warning" so that the user is still able to attempt the upload (https://github.com/OpenRefine/OpenRefine/pull/6227).
We can of course revert this move, or somehow find a more reliable source of information for which characters are allowed in Commons filenames.
Highlighting the special characters (such as your tab character) makes sense in any case.

I appreciate the new "Wikibase editing results" column, but the content is not helpful for inexperienced users.

The idea is that it's at least something they can include in their report when asking for help (without having to check the server logs). If you have ideas of how to improve it, I am all ears.
We could add some logic to translate specific MediaWiki error messages to a different format so they can be more easily understood by the user, but aiming to cover all possible MediaWiki errors is beyond reach I would say.

The Gerrit issue https://gerrit.wikimedia.org/r/c/mediawiki/core/+/942710 where the configuration options for the forbidden characters were deprecated in Mediawiki 1.41+ has some interesting reading about Illegal File Chars, and links to the wikitech-l mailing list issue which is very interesting reading and points to a core problem<EMAIL_ADDRESS>


appengine/guestbook-cloud-datastore - doesn't appear in pom.xml

We should hook it up.

Notice: this issue has been closed because it has been inactive for 763 days. You may reopen this issue if it has been closed in error.


Fix #158: add missing hover-color case

#33 introduced an update to hover-color() that I think is missing the
force-use-color parameter.
When I have a style such as:
li {
  background-color transparent // or initial, to reset a background-color from above
  hover-color red true
}

The result is a list item whose background swaps to red on hover,
rather than respecting the second argument of true to hover-color().
Adding a force-use-color check fixes this.

This looks good. The test failures seems like a dependency update to me, I'm going to make sure they are passing then merge this. Thanks so much for the contribution!

Thanks. Yeah, I couldn't get npm test to succeed even with a fresh clone of the repo.

Hey @vevo-arthur-klepchukov -- just fixed the issue, sorry about that. Could you just rebase this on top of master then we'll merge?

Tests now pass :)

Perfect. Thanks for the contribution @vevo-arthur-klepchukov!


Can not animate this gif in iOS 7.1 Device and iOS 8.4 Simulator

the url is http://ww1.sinaimg.cn/bmiddle/b0cb01d6jw1eucbe6v54hg204604o1ky.gif

This seems to have somehow resolved itself. It seems to work for me (tested on iOS Simulator 14.4).


surplus 2.1.0 is unable handle comma-seperated local codes

$ s+ -d WF8Q+WF, Praia
surplus version 2.1.0-local, debug mode (latest@future, Tue 05 Sep 2023 12:57:15 +0800)
debug: parse_query: behaviour.query=['WF8Q+WF,', 'Praia']
debug: split_query=['WF8Q+WF,', 'Praia']
debug: original_query='WF8Q+WF, Praia' <_io.TextIOWrapper name='<stderr>' mode='w' encoding='utf-8'>
debug: cli: query=Result(value=StringQuery(query='WF8Q+WF, Praia'), error=None)
Traceback (most recent call last):
  File "/home/m/.cache/pypoetry/virtualenvs/surplus-CJ293Xyc-py3.11/bin/s+", line 6, in <module>
    sys.exit(cli())
             ^^^^^
  File "/home/m/works/surplus/surplus/surplus.py", line 1141, in cli
    print(f"error: {text.cry(string=not behaviour.debug)}", file=behaviour.stderr)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/m/works/surplus/surplus/surplus.py", line 253, in cry
    raise self.error
  File "/home/m/works/surplus/surplus/surplus.py", line 480, in to_lat_long_coord
    return Result[Latlong](geocoder(self.query))
                           ^^^^^^^^^^^^^^^^^^^^
  File "/home/m/works/surplus/surplus/surplus.py", line 501, in default_geocoder
    raise NoSuitableLocationError(
surplus.surplus.NoSuitableLocationError: No suitable location could be geolocated from 'WF8Q+WF, Praia'

seems like an easy fix, strip words of commas when checking words for a partial plus code

this is actually a regression from pre-2.0.0 releases
$ s+ -d WF8Q+WF, Praia
surplus version 1.1.0, debug mode
debug: args.query='WF8Q+WF Praia'
debug: squery=['WF8Q+WF', 'Praia']
debug: lat=14.9173125, lon=-23.5113125
debug: location={...}
Biblioteca Nacional de Cabo Verde
Avenida Machado Santos, Chã d’Areia
7600
Cabo Verde

tested on both windows and alpine linux, seems like somewhere in the cli argument handling commas were just taken care of

waiting for type-type conversion to be merged into future before branching off


Added remove nodes stage

Wow, once again, great job!  Just that minor formatting comment.
Nice work testing the edge cases.

Also, I merged in master and fixed the conflicts, so make sure to git pull.

Updated!


[INSTALLER] Multilanguage Support for the Installer

The first impression counts
Therefore it's just logical to support gettext and mutli languages in the installer aswell. As the installer is in the most parts independent from the main application I included the gettext lib in the installer aswell and adjusted it a bit.
The logic gets the default browser language and sets a cookie from it. So the user will directly see his native language (if everything is translated). He is still able to choose another language with a little button on the first page.
I will include the installer language as another component to our weblate platform

Tested with docker.
1st issue: Click on Language (at first page) and chose german: Redirects ultimate to http://<IP_ADDRESS>:8086/lang=de_DE/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/ and so on.
2nd issue: on first call it shows Warning: Undefined array key "install_lang" in /var/www/html/install/index.php on line 104
3rd issue: Continued with "english" as default-lang. When setup/migrations were finsished i see a german login-screen. after logging in my language is setted to Bulgarian

Issue 1 and 3 are fixed with your latest commit.
issue 2 still there.
Repro for #2: Delete Cookies or use incognito-mode for calling the installer


MB-16168: more auth failure fixes and logging

Jira ticket
Summary

Add a single retry when the connection to the database fails. Its hard to reproduce this problem on demand, but it testing in the loadtest environment, this retry seems to mitigate the problem.
Add some logging to try and see if we can determine a pattern for when we have the connect error in our deployed environment.

Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Loadtest environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.
Setup to Run the Code
Pretty much all the relevant logic only applies to deployed environments, so it's hard to test locally. As mentioned above, this is tested in the loadtest environment.

Messages

:book:
:link: MB-16168

  Generated by :no_entry_sign: dangerJS against 4d0242ca76ad91b5fe3a8f3f4f9cbaafc0548b9c


MacOS Pods Cache restore gets stuck indefinitely for the size more than 3gb

The macos cache restore process gets stuck for a long time(more than 1hr) and gets timed out. We have been facing this problem recently when our pods cache size jumped from 1.8gb to 3gb.

We couldn't find any possible reason why this happens and also not sure if we are hitting any storage limitations in the runner machines. May be related to this issue(https://github.com/actions/cache/issues/1115), but in our case the job gets cancelled automatically after 1.5hrs.
Let me know if any more information is needed

It's likely the same issue as #1115. Anyway I solved this issue by manually cloning the Specs repository and removing the caching mechanism altogether. It's more fast this way. This is the workflow's step.
- name: Add CocoaPods Specs
  run: |
    mkdir -p ~/.cocoapods/repos/cocoapods
    git clone --depth 1 -b master https://github.com/CocoaPods/Specs.git ~/.cocoapods/repos/cocoapods

@vsvipul is there any update?

@numandev1 I'm no longer working at GitHub. Please contact people on https://github.com/actions/toolkit to check who is the new owner for cache.


Fix a few tests that weren't getting run in CI

Fixing the broken build, this change has nothing to do with it


[AutoRelease] t2-msi-2023-02-02-42665(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/3737
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1025
BuildTargetingString
azure-mgmt-msi
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/3737


TimeoutError on page.goto means response object is not available

Our product crawls our customer's website as part of our overall solution.  We are using Puppeteer for this and, overall, it works great.  But we have the same problem discussed here.  We can't know a priori what the appropriate timeout behavior needs to be on any given page or site.
When page.goto throws a TimeoutError, it doesn't necessarily mean that the page is unusable -- but after catching the error we can't access the HttpResponse that is returned when there is no exception.  If a new method, page.response(), for example, returned the response object if it is available, we'd be happy.  I realize that in some timeout scenarios the response will not be available (such as if the timeout is at the network layer).  It may also be a good idea for Puppeteer to emulate a "stop" when it throws an error, but I don't see that I need to be part of that.
So something like the following would be desireable:
const browser = await launch();
const page = await browser.newPage();
try {
  await page.goto(url, {waitUntil: ['load', 'networkidle2'], timeout: 30000});
catch(err) {
  // perhaps check for errors other than timeout
}
const response = await page.response();
if (response) {
  // use various information from the page itself, but also from response, such as url, status, headers
}
// clean up

Originally posted by @kduffie in https://github.com/puppeteer/puppeteer/issues/3238#issuecomment-1856987366

Can you use the page.on('request', handler) to track if the request happens?


Wrong command in bounce processing

Cron command for processing bounced mails is written like this in the doc
php app/console mautic:fetch:email
While correct version is
php app/console mautic:email:fetch

Thanks for pointing it out! Do you think you'll be able to submit the fix? https://github.com/mautic/documentation#how-to-contribute-to-the-docs

I just did it, could you cofirm it is ok 3 pull requests for all the languages

All are merged. Thanks!


Add responsive menubar to complement current togglable sidebar.

Idea is to have most important pages directly accessible without additional clicking.

Points for discussion:

Burger menu moved to the right to somehow fill that emtpy spot (sidebar still opens on the left). Probably when authentication will be implemented the avatar / user menu would go there, and the burger will return to leftmost slot.
Do we need Fink logo in the leftmost spot? Would probably visually conflict with current 'search' entry.
Small shadow is added for the whole header to slightly better separate it from the page content. Probably will need some adjustment when backgrounds are changed.

I prefer the last option with the split :-)

The code looks good to me -- merging?

I have no objections and nothing to add here, so let's do it!


Bug in reporting of POP protocol logging

POP003 test has a bug causing all POP servers to be reported as a warning even when POP logging is disabled.
Line 36:
$WarningList += $PopSetting.Server

Should be:
$PassedList += $PopSetting.Server

Fixed in #120


Windows XP 64-bit boots to blank screen in 4.6.0

BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.
Describe the issue
Windows XP x64 boots to blank screen after updating to 4.6.0.
Splash screen displays normally:

After splash screen, there is just a blank screen:

The VM continues to work as expected in 4.5.4.
Configuration

UTM Version: 4.6.0
macOS Version: 15.0
Mac Chip (Intel, M1, ...): M2 Pro

Crash log
Not associated with crash.
Debug log
debug.log
Upload VM
config.plist.zip

@xadammr I noticed in your config that you are using pc-q35-2.9 which I have never gotten to work. When I try to run windows setup with your config, I get BSOD (0x0000007B) on both 4.5.4 and 4.6.0. Meanwhile, my Windows XP x64 install uses i440fx (pc) which still works. Any way you can either upload your VM or create a new VM and share it with me?

@osy I created a new virtual machine using the same config (pc-q35-2.9), reinstalled Windows XP x64 and everything is working. It must be some weirdness localised that particular Windows install.
Thanks for taking a look though -- but I blame Windows!


Expand community dropdown menu on click on smaller screens

Challenge Name

This is a global issue. Not specific to particular challenge
Issue Description

On smaller screens (width less than 768px) the top navigation menu is converted to a Menu button.
When menu is clicked, it shows navigation items. Point to Community submenu with your mouse. The submenu expands automatically. Now point to About and try going to the next primary menu item Donate. When the About menu loses focus, the Community submenu collapses and user has to go up again to click Donate button.
Browser Information

Browser Name, Chrome - Version 60.0.3112.113 (Official Build) (64-bit):
Operating System: Windows 10
Mobile, Desktop, or Tablet:  Desktop

Screenshot

Step 1 : Point to About Menu

Step 2 : Try to click Donate

Additional info:
This is correct behaviour for bigger screens where menu is fully visible. The collapsed submenu should expand on click (as opposed to on hover)

Thanks for reporting this @adityaparab! I just ran into https://github.com/freeCodeCamp/freeCodeCamp/issues/13450, and it looks like this is a duplicate of that, so I'm closing this issue.
Happy coding!


Updated to 16th of April patch

I've followed the guide from the description on where to change the code to share item in multiplayer, used https://github.com/0xd4d/dnSpy to decompile/compile.

Tested in two sessions with 4 players each. Works perfectly. Thanks.


Fix racy FrameworkVersion and Instance reconciliation

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/component generator
/component kudoctl

/component operator

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind feature
/kind enhancement
/kind infrastructure
/kind kep

What this PR does / why we need it:
Currently, there is a race condition when applying FrameworkVersion and Instance CRDs. The second one relies on the first one to exist for the reconciliation. However, there is no "happened-before" guarantee. To fix this, instance_controller now watches the FrameworkVersion too and reconciles accordingly.
Which issue(s) this PR fixes:

Fixes #274
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

I wrote in a comment on https://github.com/kudobuilder/kudo/pull/361#issuecomment-504101106, but thought I'd include it here too:
This integration test can be written using the declarative test harness. Create a test case with three steps:

Create Instance object.
Create Framework and FrameworkVersion object and assert that the Instance's objects are created successfully.


Error on Socket - LiveQuery Error (Cannot Connect)

Hi everyone -
I'm attempting to use livequery (using the js sdk) in my parse-server app hosted on AWS using SSL. I've attempted to connect and each time I get the following error:

WebSocket connection to 'ws://XXXXXXXXX.XXXXXXXXXXXXX.com/parse' failed: Error during WebSocket handshake: Unexpected response code: 403
error on socket

My livequery js code is quite simple:

let query = new Parse.Query('XXXXXXX');
query.equalTo('XXX', 'XXXXXXXXX');
let subscription = query.subscribe();
subscription.on('create', (obj) => {
     console.log(obj);
});

I'm not sure what I'm doing wrong exactly but if someone could point me in the right direction it'd be greatly appreciated! @hramos

Hey, thanks for reporting this issue.
Can you please add all the info specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.

@greggmojica I had a similar problem -- changing the protocols on my ELB seemed to do the trick.
The following is what I added to my elastic beanstalk env.yaml:
  aws:elb:listener:443:
    ListenerProtocol: SSL
    InstanceProtocol: TCP

@ChrisHawley did you create this env.yaml file (I don't have it in my config). I do have an app.yaml file.

@hramos
Environment Setup - AWS Beanstalk
parse-server version :2.2.2
Operating System: Linux
Hardware: Amazon Linux
Localhost or remote server? AWS
MongoDB version: 3.0.12
Hardware: mLab Dedicated Instance
Localhost or remote server? mLab
Expected to Connect to Socket, fails and throws error WebSocket connection to 'ws://XXXXXXXXX.XXXXXXXXXXXXX.com/parse' failed: Error during WebSocket handshake: Unexpected response code: 403 error on socket

@greggmojica Yea, I created env.yaml manually.  I think it's a way to pass additional config params into your ECS environment without going through the AWS Console UI. (http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environment-cfg-manifest.html)
Is websockets the only thing that's giving you trouble?  Are you able to connect parse-dashboard to your deployed environment for ordinary (non-LiveQuery) requests?

Hey @ChrisHawley I did add the env.yml file but no luck. I'm getting this error now:
WebSocket connection to 'ws://xxxxxxx.xxxxxxxxxxxx.com/parse' failed: Error during WebSocket handshake: Unexpected response code: 301 Did you have anything else in your env file?  Thoughts?
@hramos - I'd appreciate your input! Thanks!

@greggmojica Did you set up the InstancePort on your ELB?  I think 9091 is default, so:
  aws:elb:listener:443:
    ListenerProtocol: SSL
    InstanceProtocol: TCP
    InstancePort: 9091

Just updated the env.yaml file and I get this error again: WebSocket connection to 'ws://beanstalk.gradology.com/parse' failed: Error during WebSocket handshake: Unexpected response code: 403. No luck :(

Very clear that is the load balancer issue.  Currently aws does not supporting ws and wss redirections.  Plus , you need to set stickiness on the header redirection to pass token to live query server.

@lifeisfunny can you please give me more detailed info regarding this? I called AWS support and they are really not sure.

@greggmojica your Parse Server version, 2.2.2, was released on March 23 and therefore is very far behind the latest release as of this writing (2.2.18).
As it happens we can't provide a lot of support for troubleshooting individual deployments here in the issue tracker, so I'll need to close this issue out.

hi i have the same ptoblem here and i dont understand where to addt he env.yaml file

hi i have the same ptoblem here can you help me

I have the same roblem with livequery

@THEDOWNCOUNTRY can you please open a new issue filling the issue template so we can properly address it?


Fix grammar

Description:
Grammar fix.
Changes

A Scheduler lets you define in what execution context will an Observable delivers notifications to its Observer

to

A Scheduler lets you define in what execution context will an Observable deliver notifications to its Observer

Related issue (if exists):

LGTM

Merged with bdd957e, thanks @miguelmota . Fyi, I've amended commit message to follow guildeline (https://github.com/ReactiveX/rxjs/blob/master/CONTRIBUTING.md#-commit-message-guidelines) which being used for automatic changelog generation & others.


Add support CustomAction parameters

Add parameter support for custom field action including UI so user can input at design time. CustomAction model object would need generic parameters element inside it.
Parameters could be detected via method signature, like 1st arg is for input, and the others are action parameters.
Or introduce parameter annotation (#536) and let field action service set those parameters before invoke it. Note that it only works for non-static methods. Also if we cache field action class instance in the future for performance, it should clear all the parameters for each invocation.

Actually it would be more efficient to pass parameters as method arguments. The field action service should introspect the method parameters and see if there's @AtlasFieldActionParameter on that arguments. In that way that static/non-static problem I said in the description goes away.

Addressed by #877


OK, commands instead of keybinds

Could you create commands to use the mod, in addition to keyboard binds? No text in the chat only commands and please give me your discord or other contact link, I have a few questions so as not to stuff the github

I can and probably will add commands to control the PlayerController. However, I don't know when I will find the time to do so. If you want to contact me, feel free to do so via Discord. Also, feel free to implement the feature yourself and create a pull request.

Added commands with the newest version. Release can be found on GitHub or Modrinth.


Syntaxhighlighter for Constants?

I do not know if it is a bug or rather a request. It would be nice if constants were also highlighted.
Example
#constant KEY_A            65
KEY_A should then also be highlighted.

I'll move this to #3


Add example usage to docs

mkdocs automatically pulls out example usage of methods into a neato callout box. It's happening here. Polish that  one (present output on a separate line) and add example usage for all pandas-checks methods

Resolved by #37


Test accessibility of the edit item page

We should do this after the work form has implemented the full style from the mock-ups and design doc.

@astridu is this something you could work on now?

Yes, let me get in touch w/SODA to get our account configured. May take a day.

Just got access to the extension and working through the issues now.

@astridu Is this work complete now?

Yes, thanks!


feat(datepicker): implement auto position

Added popup-placement attribute that implements the auto position
feature that exists in the tooltip directive.  Accepts the same
placement options as the tooltip.
This plunk demos the feature.
I haven't added test for this as I'm not sure on what the best approach is for finding an elements position in a test and would like some guidance on that.  The 2 minor changes in the readme.md is a result of my editor trimming trailing whitespace.
If this approach is acceptable, I plan on doing the same thing to the typeahead directive.

Would it make sense to address #5414 with this commit as well?  That way you can work out the kinks before moving to typeahead and dropdown?
Linking in #4762 for tracking purposes.

Sounds good to me.

This LGTM too

Hm, I guess I forgot about the test part - how much testing does this need? We could perhaps test given certain CSS scenarios with regards to maybe display: block, position: relative/absolute, and floats.
Tooltip/popover would need them too.

@wesleycho I'm working on it still, will create another PR in the near future.


Update exchange-online-powershell-v2.md

Docs Build status updates of commit bc5891d:
:clock10: Full build: the average full build time is 11 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit bc5891d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 0cedec0:
:clock10: Full build: the average full build time is 11 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Per #4348

Docs Build status updates of commit 0cedec0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 7723426:
:clock10: Full build: the average full build time is 11 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 7723426:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


VDA5050 action to update certificates used for secure connection to MQTT-broker (TLS/SSL)

If using an encrypted connection to the MQTT-broker it will be necessary to update certificates on a regular basis. For this purpose we suggest to add a standardized action to VDA5050:
name = updateCertificates
parameters: address (where to download the new certificates from; string; mandatory), hash (string, optional)

@LukasSchwarz4202 : good idea
I would exchange address with url to be more precise what is expected and if a hash is specified we need also specify the hash algorithm.
Shall this action update only the certificate or also the private key? If the later case the vehicle should check the new certificate against a local root or intermediate certificate. Otherwise everyone with access to the MQTT Broker can exchange the certificate/key on the vehicle. This check has not to be mandatory, but I think the standard should recommend such a check and notice that this action may fail with an appropriate error message inside the state if such a check fails.
Nevertheless the vehicle should check if the new certificate match the private key.

address vs. url: good for me. Just checked the map download, there it is named mapDownloadLink so maybe also certificateDownloadLink
private key and check: good point


Documentation is fairly incomplete, the tool seems quite hard to use

As seen in https://github.com/garrigue/lablgtk/pull/38#issuecomment-462097726 , migrating packages to use dune-release is a very frustrating experience.
Contrary to what is claimed, many critical invariants [such as that homepage must be set to github, format of CHANGES, etc...] don't seem to be properly documented, and in the cases that the right hidden magic is not properly set the tool behaves in random ways [such as setting URLs incorreclty, publishing arbitrary changelogs, etc...]
IMHO what works and what does not should be much better documented, likely with a guiding example.
cc: @garrigue

I agree, specially about CHANGES.md where I had struggle about format of version.

Do you see concrete items that could be improved ? A random list, from what I understand:

[ ] improve version detection from CHANGES.md (and/or improve documentation)
[ ] better linting of which fields much be set
[ ] write a guiding examples.

Do you see something else?

Thanks @samoht , I think maybe the biggest remaining point for me is to detail what requires github and what not, in particular more info indeed about the fields.

improve version detection from CHANGES.md (and/or improve documentation)

The tools is now displaying more information during version detection (#135)

We'll try to also improve the documentation so new users have a good introduction before actually launching the tool!


Python script to run and debug ONNX models

This patch updates debug.py script that is used for running and debugging ONNX models.
Changing name from debug.py to RunONNXModel.py.
Adding multiple options to the script:

shape_info to set shape for dynamic inputs.
compile_args to use all compiler options from onnx-mlir command.
verify to verify the model by given reference inputs/outputs, rtol, and atol.
print_input, print_output to print out inputs and outputs.

All supported options:
$ ONNX_MLIR_HOME=./Debug/ python ../utils/RunONNXModel.py  --help
usage: RunONNXModel.py [-h] [--compile_args COMPILE_ARGS] [--shape_info SHAPE_INFO] [--verify {onnxruntime,ref}] [--ref_folder REF_FOLDER]
                       [--rtol RTOL] [--atol ATOL]
                       model_path

positional arguments:
  model_path            Path to the ONNX model.

optional arguments:
  -h, --help            show this help message and exit
  --compile_args COMPILE_ARGS
                        Arguments passed directly to onnx-mlir command. See bin/onnx-mlir --help
  --shape_info SHAPE_INFO
                        Shape for each dynamic input, e.g. 0:1x10x20,1:7x5x3
  --verify {onnxruntime,ref}
  --ref_folder REF_FOLDER
                        Path to the folder containing reference inputs and outputs stored in protobuf. Used when --verify=ref
  --rtol RTOL           Relative tolerance for verification
  --atol ATOL           Absolute tolerance for verification

E.g., MNIST using random inputs:
$ ONNX_MLIR_HOME=./Debug/ python ../utils/RunONNXModel.py mnist.onnx
Temporary directory has been created at /tmp/tmpj4trc3lz
Compiling the model ...
  took  0.61645632609725  seconds.
Generating random inputs ...
  done.
Running inference ...
  took  0.0016591008752584457  seconds.

E.g. MNIST with reference inputs/outputs for verification, and disable-memory-bundling:
$ ONNX_MLIR_HOME=./Debug/ python ../utils/RunONNXModel.py mnist.onnx --compile_args="--disable-memory-bundling" --verify=ref --ref_folder=mnist/test_data_set_0
Temporary directory has been created at /tmp/tmpn4k457pp
Compiling the model ...
  took  0.5986047498881817  seconds.
Reading inputs from mnist/test_data_set_0 ...
  done.
Running inference ...
  took  0.001661023125052452  seconds.
Reading reference outputs from mnist/test_data_set_0 ...
  done.
Verifying value of Plus214_Output_0
  correct with atol=0.05, rtol=0.01.

In case of mismatched elements, we print out:
Verifying value of lstm_Y ...
Not equal to tolerance rtol=0.0005, atol=5e-08

Mismatched elements: 986 / 14000 (7.04%)
Max absolute difference: 2.4974346e-05
Max relative difference: 52.30039
 x: array([[[1.732356e-01],
        [3.278255e-07],
        [1.345366e-03],...
 y: array([[[1.732354e-01],
        [3.665352e-07],
        [1.345384e-03],...
Print out all mismatched elements ...
At (0, 0, 0) mismatch 0.1732354313135147 (actual) vs 0.17323556542396545 (reference)
At (0, 1, 0) mismatch 3.6653520396612294e-07 (actual) vs 3.2782554626464844e-07 (reference)
At (0, 2, 0) mismatch 0.0013453837018460035 (actual) vs 0.0013453662395477295 (reference)
At (0, 3, 0) mismatch 0.0001463600929128006 (actual) vs 0.00014635920524597168 (reference)
At (0, 4, 0) mismatch 0.0007426320225931704 (actual) vs 0.0007425844669342041 (reference)
At (0, 5, 0) mismatch 6.357333290907263e-07 (actual) vs 6.258487701416016e-07 (reference)
At (0, 6, 0) mismatch 0.9974887371063232 (actual) vs 0.9974887371063232 (reference)

This tool will be really useful. Recently, I encountered an error in check-onnx-backend and was desperate for a tool to debug it. One issue with onnx backend test is that the output is not fully printed out. When the difference is small, I can not tell what's wrong. Can an option to show which elements are wrong with value compared?
Another question: how to generate the pb file for input? For backend test, the value of tensor is known as an bumpy tensor. Online document says that tensor flow is need to generate the pb file. But I do not have tensor flow installed.

@chentong319 yes, I can add that option. Thanks!
I often use this code to write a numpy array to protobuf: https://github.com/onnx/onnx/blob/master/docs/PythonAPIOverview.md#manipulating-tensorproto-and-numpy-array

I often use this code to write a numpy array to protobuf: https://github.com/onnx/onnx/blob/master/docs/PythonAPIOverview.md#manipulating-tensorproto-and-numpy-array

Thanks for the tip. Should it be added in the document?
Another comment: you may use git mv if RunONNXModel.py is modified from debug.py.

@jenkins-droid test this please

Jenkins Linux ppc64le Build #1001 [push] Python script to run and... started at 15:05

Jenkins Linux s390x Build #1879 [push] Python script to run and... started at 15:05

Jenkins Linux amd64 Build #1881 [push] Python script to run and... started at 14:05

Jenkins Linux s390x Build #1879 [push] Python script to run and... passed after 57 min

Jenkins Linux amd64 Build #1881 [push] Python script to run and... passed after 58 min

Jenkins Linux ppc64le Build #1001 [push] Python script to run and... passed after 1 hr 3 min


Software benchmarks

Description
Add simulator and compiler (software) benchmarks
Issue ticket number and link
None
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Simulator benchmarks passed peer review; compilation benchmarks are from the UCC team, with QrackCircuit added
Checklist:

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules (or not applicable)

Should we opt to potentially close this, @WrathfulSpatula ?

Should we opt to close this MR, @WrathfulSpatula ? Any thoughts, @cosenal


Better handling of 'Texture Error: frame does not fit inside the base Texture dimensions'

Hey there
I have a game where users can upload their own spritesheets. However when they make a mistake, e.g. a sprite that is 1 pixel too narrow, the error 'Texture Error: frame does not fit inside the base Texture dimensions' is thrown in the console. And the entire game stops loading. I currently do not see a way to try/catch that inside my game code. Is it possible to allow the the game developer to handle this exception ?
Or to provide a function to "test" assets before loading them
Thanks :+1:
My current workaround is
PIXI.Texture.prototype.setFrame = function(frame)
{

   ...

    if (!this.trim && (frame.x + frame.width > this.baseTexture.width || frame.y + frame.height > this.baseTexture.height))
    {
        this.valid = false;
        return;
        //throw new Error('Texture Error: frame does not fit inside the base Texture dimensions ' + this);
    }

I would check the user-supplied texture first.
The same logic check can be used - but applied sooner, and then resulting in a "friendly error".
However, if the texture is used then I think it is fitting that it's a should-not-be-handled exception: it's a programming boo boo.

Thanks, @pnstickne . Unfortunately it happens on the game.load[method] callback. So i have no chance to check anything before the texture is actually loaded. I would need to write a custom loader and then pass the texture to phaser. Seems a bit clumsy or do you have another solution?

The error doesn't come as the result of a load operation though - it arises when you try to apply it to a sprite. So you can easily load the image and manually check its dimensions well before you ever need to actually use it as a texture.

Actually scratch that - if it's a sprite sheet then you would need to specify the correct dimensions on load. However as you can't guarantee it just load it as an image. Then manually check the dimensions. If they're correct you can then pass it over to the sprite sheet parser and add it to the cache directly (just look at what load.spritesheet does when it completes - you can do the exact same call from your own code).

Ok cool thanks.
So i guess i will write a load.validateSpritesheet, and then have load.spriteSheet dispatch to that for the validity check.

If you look at Cache.addSpriteSheet that is all you need. You can simply call that after you've verified the image is correct and it'll parse and add the sprite sheet to the cache quite happily.

Ok i've tried but it gets uglier by the minute.
First of all, the setFrame check is per frame, so i have to reimplement walking through every frame in the spritesheet and checking it against the image's width supplied by the game.cache.
The other problem is that the engine doesn't really care about adding the Cache.addSpriteSheet after load, it will just use the image that got loaded with the same key.
Any ideas?

I also checked game.load.onFileError, unfortunately it doesn't fire otherwise i could catch the error and notify the user that his spritesheet is wrong. It would be really convenient if PIXI fired an event in case the  frame cant be set.

It's not a file error though, so the loader shouldn't fire it. The image loaded fine. It's just that you gave it bogus dimensions so the sprite sheet parser can't chop it up the way you've told it to. You need to give it accurate dimensions. If that means taking the source image width/height and doing a little simple division to work out if the given frame dimensions are right or not, then so be it - that's what needs to be done.
Alternatively patch your copy of Pixi to get around the error it throws, but it's not something that should be done on a framework level - because fundamentally the dimensions it was given were wrong. I think it's fair of Pixi to expect it is given the correct frame dimensions when creating a texture, and if there's any possibility they might be wrong then they need validating in userland code before it's asked to make a texture with them.

@fyyyyy If you could get the "on load" of the resource, would that be sufficient to handle this problem easily?

I assume not because it's trivial to get the load event for a specific
asset already. The issue is surely that you don't know the dimensions are
wrong until you try and make a sprite sheet from it, by which point it's
too late.
On Monday, January 26, 2015, pnstickne<EMAIL_ADDRESS>wrote:

@fyyyyy https://github.com/fyyyyy If you could get the "on load" of the
resource, would that be sufficient to handle this problem easily?
—
Reply to this email directly or view it on GitHub
https://github.com/photonstorm/phaser/issues/1556#issuecomment-71409073.

--
Photon Storm Ltd.
http://www.photonstorm.com
Skype: richard.davey
Twitter: @photonstorm
Registered in England and Wales.
Company ID: 8036404
VAT Number: 136 4333 27

I guess an onSpritesheetError event would be a candidate. I tried writing the logic for validating the spritesheet but its actually quite complex. Sometimes the image is like 2 pixels to wide and im not sure if the frames wrap around that or not, and wether the wrapping causes errors in itsself. Also it was difficult to add a spritesheet after the image had been loaded and notify pixi about that. It always added the image instead of frames in game. So in the end i gave up and just added one line of event firing to the phaser code :D lazy but at least it works. Maybe i'll make a request at pixi for adding another event.

There you go - it's not an event, but it at least doesn't crash your entire game any more and gives you the chance to do something about it.


[docs]Problem with Case Document Format in Quickstart

There is an issue with the format of three shell scripts

Thanks @ZmmBigdata for this contribution.
Could you rebase master and resolve conflicts?

@ZmmBigdata @Jiabao-Sun Issue was fixed in pr #3217 and merged.

@GOODBOY008 In PR # 3217, only two files were modified, while I modified three files

@GOODBOY008 Do I need to resynchronize the master repositories and resubmit the PR?

@ZmmBigdata yes, please go ahead.

Hi @ZmmBigdata, you don't need submit a new PR.
Just rebase the master branch into yours.

Hi @ZmmBigdata, you don't need submit a new PR. Just rebase the master branch into yours.

@Jiabao-Sun Ok, thank you for your reply. Will this PR still be merged？Not very familiar with this process.

Hi @ZmmBigdata, you don't need submit a new PR. Just rebase the master branch into yours.

@Jiabao-Sun Ok, thank you for your reply. Will this PR still be merged？Not very familiar with this process.

Yes


Automatically sync rooms

I love the new samechannelgateway configuration, it reduces the amount of configuration needed to sync many channels across platforms.
The next way it could get even better is if channels of the same name were automatically synced if the bot is invited to join them. This way I would never have to update my configuration file once I'd added the bot to a particular platform.

What would you think of using a REST API to join the bot to a channel and bridge it (instead of automatically sync on invite)

I have found that to some degree this feature is already "implemented", see #73. The problem with such an automatic syncing would be that town-square is always synced, as the relay bot is a member of town-square automatically.

What would you think of using a REST API to join the bot to a channel and bridge it (instead of automatically sync on invite)

The point is that the channel owner/moderator has the power to invite and kick the bot. How would you authenticate the REST API?


Improve performance database access

At the end of each report, we insert a record (and catch the potential DuplicateKeyException)
to testExecutionExperiment to keep the data up-to-date.
This PR also removes an unused class and does a minor refactoring.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

By saying "experiment", you mean to remove testid/testproject/testclass columns from testExecution? Not yet think about it.


Move test to test directory, update ribbon and hystrix libraries.

Hi,
I had these changes in my repo and I thought that maybe it could be interesting to try to get them merged.
I know it's a long commit but it's because I've moved all the tests to src/test/.... instead of being with the main code.
So the changes that I've done are:

Force Java 8.
Update hystrix, servo, archaius, and ribbon libraries.
Update jersey libraries.
Add an example in zuul-netflix-webapp of archaius fetching properties from dynamodb.
Change some println lines in some filters for LOGGER.info().
Update to gradle 2.10.
Allow to change Cassandra cql and target version with a property.
Add another constructor in RibbonCommand to be able to choose the commandKey. So in hystrix-dashboard multiple command can be shown separately.

I think this is all. I hope you find it useful ;)
Best Regards,
Jaume Pinyol

I'm going to vote no for java8 on 1.x

@jaume-pinyol I realize that unit test code in classes is a style preference, but we do prefer having the unit tests in the code. This keeps logic and testing close. I am going to reject the pull request because of this..


Create ua.txt

Official Website:  http://www.upa.edu.lb
IT Related Courses:  http://www.upa.edu.lb/unites-universitaires/facultes-et-departements/faculte-d-ingenieurs-en-informatique-multimedia-systemes-telecommunication-et-reseaux/options.html  (System Engineering, Télécommunication Engineering, Software Engineering, Multimedia Engineering)
WebMail: https://webmail.ua.edu.lb/

@jeanmarcazzi Could you please explain what is the relation between @ua.edu.lb and @uantonine.net? Where we can check that @uantonine.net is a student email indeed? Thank you.

@philipto Dear, here's my friend's email open being @uantonine.net . For the @ua.edu.lb it was more of a domain change as I was clarified now. So I guess for us students we can go with @uantonine.net only and will let you know later on if we need the ua.edu.lb .
Thank you.

@philipto do you need me to create a new pull request with only the uantonine.net file ?..

@jeanmarcazzi Pull request merged. Actually, it would be enough to give me this URL: http://www.upa.edu.lb/ar/circulaires-administratives/circulaire/article/circulaire-administrative-relative-aux-ecourses-et-aux-mails-universitaires.html, it is at the official university website and says "Tout étudiant est doté d’une adresse e-mail «<EMAIL_ADDRESS>», consultable depuis le SIS de l’UA. "
You don't need to make separate pull request for the second domain, your pull request is merged, and both university domains are now added to the repository.
Thank you!

@philipto Thank you for your quick response! Now we can enjoy your products!


update readme reference 1.9.0 to 1.10.0

@SalvadorSarpi Thank you for your contribution!

@SalvadorSarpi Thank you for your contribution!


possibility to visualize the difference between new and old mutation report

Is your feature request related to a problem? Please describe.
i'm trying to add mutation testing to MR pipeline, for that i'm using the incremental mode. but the result is always the full mutation test of all the code base what makes it hard to interpret how mutation test evaluates my code changes
Describe the solution you'd like

be able to compare 2 mutations tests reports and visualize the difference somehow (preferably UI or through gitlab integration)
be able to mutate only the changes pieces of code (not the whole file where we have some changes) to make mutation tests faster.

Describe alternatives you've considered
what i tried to do:

run mutation only on changed files but the results are still hard to interpret: i can't see how my changes exactly affected the mutation score: for that i need either to compare with previous results which is really hard or i have the results of the whole file and i need to dive in the whole file to find the mutations related to my changes and for that i need to remember where i did changes
run incremental mode on MR but still hard to interpret how my changes affected the mutation score
use Stryker-diff-runner but it needs to run all the tests against every change which is not efficient: "perTest" feature doesn't work

Hi @amalboushaki thanks for opening this issue.

be able to mutate only the changed pieces of code

This is actually what StrykerJS already does. But your meaning is evident here, you want it to only report on the change.
There are two ways of supporting this feature:

Change the HTML report to support showing a diff between reports (a lot of work)
Add a new reporter (html-diff?) that fills an HTML report with only the diff between the old and new report. (a relatively small change)

Would you be helped with solution 2?


Wrong row size

When there are brushed elements and the user adds new column or changes stratification, the new multiforms are not split correctly - the "brushed" multiforms also contain items that weren't brushed.

Same happens if one brushes too fast so that some of the elements are not included in the brush but still get bigger.

@katush, is this issue solved?
I will extract the problem from my comment to a separate issue.


Example Chat-UI (ChatGPT OSS Alternative) causing crash of API with preloaded model

LocalAI version:
quay.io/go-skynet/local-ai:latest
Environment, CPU architecture, OS, and Version:
IBM x3400 Server
with

VMware Host (x86-64 CPU Arch)
VM Guest: Ubuntu 20.04 (x86-64 CPU Arch)
Docker version 24.0.2, build cb74dfc
docker-compose version 1.29.2

Describe the bug
I'm new to localai and was trying to set-up the example "ChatGPT OSS Alternative" presented on localai-homepage. Link to example is: https://github.com/go-skynet/LocalAI/tree/master/examples/chatbot-ui
At first it looks like the localai-api is running fine, but sending any prompft using the chat-ui to the API causes crashing (see logs attached).
To Reproduce
Try this example:
https://github.com/go-skynet/LocalAI/tree/master/examples/chatbot-ui
This is my resulting docker-compose.yaml trying to adopt it:
version: '3.8'

services:
  api:
    # https://localai.io/basics/getting_started/index.html#run-localai-in-kubernetes
    #image: quay.io/go-skynet/local-ai:v1.18.0
    image: quay.io/go-skynet/local-ai:latest
    build:
      context: .
      dockerfile: Dockerfile
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8080/readyz"]
      interval: 1m
      timeout: 20m
      retries: 20
    ports:
      - 8080:8080
    env_file:
      - .env
    environment:
      #- DEBUG=true
      - MODELS_PATH=/models
      # You can preload different models here as well.
      # See: https://github.com/go-skynet/model-gallery
      - 'PRELOAD_MODELS=[{"url": "github:go-skynet/model-gallery/gpt4all-j.yaml", "name": "gpt-3.5-turbo"}]'
    volumes:
      - "./models:/models:cached"
    command: ["/usr/bin/local-ai" ]

  chatgpt:
    depends_on:
      api:
        condition: service_healthy
    image: ghcr.io/mckaywrigley/chatbot-ui:main
    ports:
      - 3000:3000
    environment:
      - 'OPENAI_API_KEY=sk-XXXXXXXXXXXXXXXXXXXX'
      - 'OPENAI_API_HOST=http://api:8080'

Expected behavior
I've expected a working example with at least any output to the chat-gpt like prompt. But there's only "internal error" response popping up.
Logs
Log file from docker-container
Additional context

local-ai_api_1_logs.txt

Possibly related to this issues as well:
#195

Just leaving it here in case others have similar problems ... obvisously my docker-machine had not enough RAM-Memory assigned, causing the crash when trying to load the models into RAM memory. Trying with more memory assigned to the VM and reporting here if it works then.

Tried with 16 GB RAM attached still crashes the docker-container for localai-api without useful exception pointing out what's going wrong.

I've cross checked now and deployed the same docker-compose setup on my notebook-workstation (Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz") with Ubuntu OS/Docker. There it works!
The previous deployment that caused problems was on my IBM Server which runs VMware ESXi using a Intel(R) Xeon(R) CPU E5620  @ 2.40GHz and Ubuntu OS/Docker VM.
So either local-ai stack has any kind of problems with VMware virtualisation or with Intel Xeon CPU or Xeon Model E5620?!

i have a Xeon E5649 CPU and have the same issue with the api crashing. I suspect it is an incompatible CPU.

Server specs

Dell R710

96 gig RAM

2x Xeon E5649 12 core @ 2.53GHz

28 TB storage

ubuntu 20.04 LTS 5.4.0-86-generic kernel

my docker compose file
version: '3.6'

services:
  api:
    image: quay.io/go-skynet/local-ai:latest
    # As initially LocalAI will download the models defined in PRELOAD_MODELS
    # you might need to tweak the healthcheck values here according to your network connection.
    # Here we give a timespan of 20m to download all the required files.
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8080/readyz"]
      interval: 1m
      timeout: 20m
      retries: 20
    build:
      context: ./
      dockerfile: Dockerfile
    ports:
      - 8050:8080
    environment:
      - DEBUG=true
      - REBUILD=true
      - BUILD_TYPE=generic
      - MODELS_PATH=/models
      - THREADS=14
      - CMAKE_ARGS="-DLLAMA_F16C=OFF -DLLAMA_AVX512=OFF -DLLAMA_AVX2=OFF -DLLAMA_FMA=OFF"
      # You can preload different models here as well.
      # See: https://github.com/go-skynet/model-gallery
      - 'PRELOAD_MODELS=[{"url": "github:go-skynet/model-gallery/mpt-7b-chat.yaml", "name": "mpt-7b-chat"},{"url": "github:go-skynet/model-gallery/gpt4all-j.yaml", "name": "gpt-3.5-turbo"}, { "url": "github:go-skynet/model-gallery/bert-embeddings.yaml", "name": "text-embedding-ada-002"},{"url": "github:go-skynet/model-gallery/stablediffusion.yaml"}]'
    volumes:
      - ./models:/models:cached
    command: ["/usr/bin/local-ai" ]
  chatgpt:
    depends_on:
      api:
        condition: service_healthy
    image: ghcr.io/mckaywrigley/chatbot-ui:main
    ports:
      - 3500:3000
    environment:
      - 'OPENAI_API_KEY=sk-XXXXXXXXXXXXXXXXXXXX'
      - 'OPENAI_API_HOST=http://api:8080'
    volumes:
      - ./models:/models:cached

failure message (there is additional output that i can provide but i will truncate it here as this seems the most relevant):
5:53PM DBG Loading model llama from WizardLM-7B-uncensored.ggmlv3.q5_1
5:53PM DBG Loading model in memory from file: /models/WizardLM-7B-uncensored.ggmlv3.q5_1
SIGILL: illegal instruction
PC=0xa1ab80 m=9 sigcode=2
signal arrived during cgo execution
instruction bytes: 0xc5 0xf9 0x6f 0x5 0x98 0xbe 0x8c 0x0 0xc7 0x47 0x10 0x0 0x0 0x0 0x0 0x48

note: i have tried multiple models. best case scenario they return no response. worst case is it crashes like this. Would love to get this working on my server just for funsies. but im pretty sure the CPU is the limiting factor here. I know for a fact it does not have AVX so... thats a bad sign from the get go

This is most likely caused by AVX support. You can compile local-ai on this machine to get a version optimized for it.

Anyone else scouring through the issues for a solution, build it locally like bnusunny mentions above like this, but it does make it incredibly slow
CMAKE_ARGS="-DLLAMA_F16C=OFF -DLLAMA_AVX512=OFF -DLLAMA_AVX2=OFF -DLLAMA_FMA=OFF" make build
https://github.com/go-skynet/LocalAI/issues/288#issuecomment-1580305158

Yeah, without AVX, ggml will be slow on CPU.

Anyone else scouring through the issues for a solution, build it locally like bnusunny mentions above like this, but it does make it incredibly slow CMAKE_ARGS="-DLLAMA_F16C=OFF -DLLAMA_AVX512=OFF -DLLAMA_AVX2=OFF -DLLAMA_FMA=OFF" make build
#288 (comment)

Does this work in the docker container? For me I got it to run locally with just CMAKE_ARGS="-DLLAMA_AVX2=OFF" but it was still crashing in the docker container.


Added weather field customizer sample

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Related issues?
n/a

What's in this Pull Request?
New sample field customizer showing how to display weather information using jQuery and the jQuery weather plugin.

@waldekmastykarz,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

thx Waldek, appreciated.


Subtractive brush corruptions due to Optimize Geometry

Please consider helping us!
 The bug lies in the Optimize Geometry algorithm somewhere.
Optimize Geometry Enabled:

Without Optimize Geometry:

Clues that may help track down the problem:

It's around BrushCache.OptimizeVisual -> Optimizer.CalculateConvexHulls and dealing with holes in polygons. I am highly suspicious of the PolygonFactory.SplitCoplanarPolygonsByPlane method as any slight modification to that will cause identical artifacts.
It appears that corruptions occur when near existing collinear edges from other subtractive brushes.
This exact same bug can be reproduced easily with my fixed point math version of SabreCSG so it's unlikely to be a floating point precision error. I also placed the brush near 0,0,0 where floating point precision is very high.
The size of the subtractive brushes doesn't matter.
Additive brushes never have a problem because they don't cause holes.
It's not related to the triangulation algorithm, using my T-Junction fix branch with a completely different triangulation is identical to this. So it's purely a polygon problem within the OptimizeVisual methods.

This is literally just a bug in the algorithm logic for cutting out holes.
If anyone's willing to give fixing this bug a shot... you will help so many people it's insane. That would be one of the greatest contributions yet.

I've had the same problem when making advance window shapes

Looking at this when using snapping in a simple test, this only appears to be happening at values less or equal to 0.0625, and without snapping around 0.601. Oddly enough, it doesn't happen in this case, which is to be expected:

It will still happen even with brush rotation.
It will still happen when inside of a subtractive-style map (large additive brush, subtractive sub-brushes).
This was an issue with CSG even in UE3, and dates back practically to the unreal classic era when CSG started becoming more commonly used. Often times when a brush was placed off the grid (without snapping and had a non-square location in the world), even if just a single vert of the brush was misaligned.
I did take a look at the code, but I didn't see anything that immediately stuck out to me as an issue. The only thought that crosses my mind is that perhaps the algorithm is too aggressive and attempts to round small values?

It seems that the root of this problem is not in Optimize Geometry. The CalculateConvexHulls function in Optimize Geometry assumes that all polygons in a group is coplanar, but this is not true. I add a test of PlaneEqualsLooser for every two polygons inside CalculateConvexHulls, and found that there are polygons not coplanar when this bug occurs.
So I think the bug is actually in the core algorithm. When building subtract brushes, polygons are not correctly grouped by plane, means there is wrong UniqueIndex.
I haven't fully understand the core algorithm yet, so I don't know how to fix it. But you can take it as a hint.


lodash file size ~1,4MB in size ?

Do you want to request a feature or report a bug?
bug

What is the current behavior?
I use dynamic module imports for importing lodash.js.  After executing  webpack it will create a separate file in the dist folder.  The problem is that the file has 1,4MB of size becaue it contains a bunch of source map data in it.
Why is that?
I don't use   // devtool: "inline-source-map",.
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
A small lodash file size in dist folder.
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
Win10 x64
"dependencies": {
    "@types/extract-text-webpack-plugin": "^3.0.1",
    "@types/html-webpack-plugin": "^2.30.2",
    "@types/node": "^9.4.5",
    "@types/source-map": "^0.5.2"
  },
  "devDependencies": {
    "@types/jquery": "^3.3.0",
    "@types/lodash": "^4.14.102",
    "@types/webpack": "^3.8.7",
    "bootstrap": "^4.0.0",
    "css-loader": "^0.28.9",
    "extract-text-webpack-plugin": "^3.0.2",
    "file-loader": "^1.1.6",
    "font-awesome": "^4.7.0",
    "html-loader": "^0.5.5",
    "html-webpack-plugin": "^2.30.1",
    "jquery": "^3.3.1",
    "less": "^3.0.0",
    "less-loader": "^4.0.5",
    "lodash": "^4.17.5",
    "node-sass": "^4.7.2",
    "optimize-css-assets-webpack-plugin": "^3.2.0",
    "postcss-loader": "^2.1.0",
    "raw-loader": "^0.5.1",
    "sass-loader": "^6.0.6",
    "style-loader": "^0.20.1",
    "ts-loader": "^3.5.0",
    "typescript": "^2.7.1",
    "uglifyjs-webpack-plugin": "^1.1.8",
    "webpack": "^3.11.0",
    "webpack-merge": "^4.1.1"
  },

I have used webpack with option parameters like this:
webpack -d --env.dev --display-modules --progress --display-error-details
The problem here was the -d flag.


docs(#283): example with ViewChild and ViewChildren

Closes #283

v11.6.0 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


💚 Fix the tag name

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 28.31%. Comparing base (809692c) to head (de7df6a).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #20   +/-   ##
=======================================
  Coverage   28.31%   28.31%
=======================================
  Files          22       22
  Lines         883      883
  Branches      883      883
=======================================
  Hits          250      250
  Misses        577      577
  Partials       56       56

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add project support for 2.5

Signed-off-by: Feng Xiang<EMAIL_ADDRESS>Issue:
https://github.com/stolostron/backlog/issues/25662
Currently search doesn't support finding project resources because the UID conflicts with namespace resources(in OCP project is essentially a copy of namespace). This fix is more like a workaround due to the search limitation.

Added support for project resources by looking for the corresponding namespace resource and attaching the namespace results to the project node

/test lint-check-unittests-sonarcloud

/test lint-check-unittests-sonarcloud