[11.x] Throw exception if named rate limiter and model property do not exist

Based on what we talked regarding https://github.com/laravel/framework/pull/50818
Handling strict mode is a bit annoying — if you have it set, it'd throw a bit of a cryptic error message since it'd fail with a different error. Another thing is that the array_key_exists solution doesn't deal with custom attributes.
Maybe it's an opportunity to introduce a strict-safe hasAttribute method within Eloquent?

I need to think about this one a bit. There could still be a virtual accessor for maxAttempts.

@taylorotwell thanks for merging that in. this one should be good to go.

Not entirely sure why AboutCommandTest is failing on 8.2. Seems unrelated as it's happening to other PRS too, but I'm seeing if I can figure out what's going on

Heya! We were having some failures in the testsuite at the base branch. Could you rebase this PR, make sure tests pass and mark for review again? Thanks!

@driesvints yessir!

@driesvints @taylorotwell  The deprecation of the api rate limiter is not documented anywhere? Or am i just being dumb here?
Getting: Rate limiter [api] is not defined. on a Laravel 11 app using the api middleware. It was working on a v11.1.0 installation.

@saade is this an app you upgraded to 11? Do you have the api rate limiter defined in any service providers? Prior to L11, it shipped by default on RouteServiceProvider

It is upgraded from L10, but it was running L11 perfectly in the last few weeks on a v11.1.0 installation.

@saade see this PR: https://github.com/laravel/framework/pull/50818
The problem is it was previously just silently introducing undesired behavior. If a named limiter did not exist, you wouldn't know -- now it throws an exception.

RouteServiceProvider

Hey, Did you call your RouteServiceProvider in the bootstrap/providers.php?
bootstrap/providers.php
return [
App\Providers\AppServiceProvider::class,
App\Providers\RouteServiceProvider::class, // <--
];
RouteServiceProvider.php
configureRateLimiter();

        $this->routes(function () {
            Route::middleware('api')
                ->prefix('api')
                ->as('api.')
                ->group(base_path('routes/api.php'));

            Route::middleware('web')
                ->group(base_path('routes/careers.php'));

            Route::middleware('web')
                ->group(base_path('routes/web.php'));
        });
    }

    protected function configureRateLimiter()
    {
        RateLimiter::for('api', function (Request $request) {
            return Limit::perMinute(60)->by($request->user()?->id ?: $request->ip());
        });
    }
}


Create a Readme file template for edenia repo

About Edenia

Edenia runs independent blockchain infrastructure and develops web3 solutions. Our team of technology-agnostic builders has been operating since 1987, leveraging the newest technologies to make the internet safer, more efficient, and more transparent.
edenia.com

this is for repos in the following github organization:
https://github.com/edenia


Is there no spotify widget working with SpotX?

🧐 Have you read the FAQ and viewed similar issues?

[X] I have read the FAQ
[X] I have checked older issues, open and closed
[X] I did a clean install of SpotX as described in the FAQ

Сountry of your account
India
What is your Spotify Plan?
Free
Do you have Spicetify installed?
No
ℹ Computer information
- Spotify: <IP_ADDRESS>5.g81fd6352
- Windows: Windows 10 Pro 22H2 19045.4780 Windows Feature Experience Pack 1000.19060.1000.0
- PowerShell: 5.1.19041.4780

📝 Description

In the original spotify app which I downloaded from the Microsoft store, there is possibility that we can have a desktop widget for the app.
Download Microsoft store spotify, play a song, press Win+G, it should be there.
It's a small window to control the music player and its very convinient.
The installer I downloaded from the Excel Sheet does not show up in the GameBar.

Is there any possibility that we can get this feature? Is there a different workaround for this?
📸 Screenshots

this widget is only available for the version from the Microsoft store, there are no plans to port it


n/a color not working

Color by "n/a" doesn't uncolor nodes on Safari.

NodeList doesn't inherit forEach in Safari — fixed by using Array.prototype.forEach.call instead.


navbar and link of the page

Naming Rules
Name your PR like this: ISSUENUMBER-TITLE-YOURNAME
Description
logo and navbar of home page
Related to
Make sure you include the issue number with a hash sign # so Github can link this PR to the right issue, like this:
Fixes #1
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have carefully reviewed my own code
[ ] I have commented my code
[ ] I have updated any documentation

@Sslim123 I think you might be running an old version of node/ npm - make sure you are running a recent enough version that it generates a package-lock.json file with a lockfileVersion of 2 (this is visible right near the beginning of that file).

The SVGs are rendered inline (there's nothing much wrong with that except that it's hard for other developers to know what the SVGs are) but also stored into the codebase without being referenced. It's probably best to have the images in the codebase only once - SVGR (for instructions with Webpack 5, see https://react-svgr.com/docs/webpack/) should help out with using SVG files as React components, which will probably make the code cleaner.
Also, please make sure that the images are named after what they are rather than "Vector 2" etc - this helps developers know what the image is without seeing it and important in the same way that naming code files is important.

hi shieldo, i updated the version of package-lock.json, also i followed your link and i get what you mean i try to make it work this is important , thank for this advice

Hey @Sslim123 - I think the update to package-lock.json is missing from that last commit.

Hi shieldo,  i do not saw this last time to update, but you remember my that good thank you, can i merge my PR if every thing is ok ?

The version of package-lock.json is unchanged from before, and the package.json file seems to just have changed its indentation plus the addition of a reference to a cypress config file, which doesn't seem like anything to do with this commit. Can you roll out the changes to package.json and package-lock.json on this branch, and rebase it so that it's clearer what has changed here?

a bout your  last commit i did not understood what you mean and  what i should  do , if can can make call to fix with my this issues

@Sslim123 I'm around for a call if you need :)

yes i need, i will share the link on the slack channel


OTPEnabled dependecies?

Hi Team, is the OTPEnabled boolean in dependency to the enabled OTP Provider in Azure AD or can we enable OME OTP without enabling OTP on Azure AD level at all?

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

ID: 9edd072e-c0a9-352b-05e0-1572d512d931
Version Independent ID: 6e8b9549-55f9-36bd-d8a1-8a219eaf0c71
Content: Set-OMEConfiguration (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Set-OMEConfiguration.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@SRE93, you should open a support ticket and ask. Report back here with any findings that can help improve documentation.

@SRE93 Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. You can contact Microsoft support via the need help section on the admin center. We proceed to close it as here we are limited to documentation fixes and improvements only.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


changes for SoulETH

TODO:

add initialization logic for SoulETH once this pr is merged.

Close since already merged into op-es branch.


[style]: updating and aligning the search bar and nav link items

What's the style idea?
We need to improve  the visual appearance and layout of the website's search bar and navigation link items.
Add screenshots
Add screenshots
Before:

After:

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@shreyT19 can you align just the logo of the free-hit in the latest update of the code

Sure  !! Should i make it a bit smaller and allign it with the right side nav items ?

I noticed that the Free-Hit logo in the desktop view is not aligned with the hamburger menu and search bar. Please work on fixing that


[stable/airflow] missing kubernetes section example in values.yml

Describe the bug
When deploying airflow in kubernetes mode I get the following error :
____    |__( )_________  __/__  /________      __
____  /| |_  /__  ___/_  /_ __  /_  __ \_ | /| / /
___  ___ |  / _  /   _  __/ _  / / /_/ /_ |/ |/ /
 _/_/  |_/_/  /_/    /_/    /_/  \____/____/|__/
Traceback (most recent call last):
  File "/home/airflow/.local/bin/airflow", line 37, in <module>
    args.func(args)
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/utils/cli.py", line 75, in wrapper
    return f(*args, **kwargs)
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/bin/cli.py", line 900, in webserver
    app = cached_app_rbac(None) if settings.RBAC else cached_app(None)
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/www/app.py", line 232, in cached_app
    app = create_app(config, testing)
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/www/app.py", line 87, in create_app
    from airflow.www import views
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/www/views.py", line 97, in <module>
    dagbag = models.DagBag(settings.DAGS_FOLDER, store_serialized_dags=STORE_SERIALIZED_DAGS)
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/models/dagbag.py", line 95, in __init__
    executor = get_default_executor()
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/executors/__init__.py", line 48, in get_default_executor
    DEFAULT_EXECUTOR = _get_executor(executor_name)
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/executors/__init__.py", line 87, in _get_executor
    return KubernetesExecutor()
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/contrib/executors/kubernetes_executor.py", line 715, in __init__
    self.kube_config = KubeConfig()
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/contrib/executors/kubernetes_executor.py", line 291, in __init__
    self._validate()
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/contrib/executors/kubernetes_executor.py", line 309, in _validate
    'In kubernetes mode the following must be set in the `kubernetes` '
airflow.exceptions.AirflowConfigException: In kubernetes mode the following must be set in the `kubernetes` config section: `dags_volume_claim` or `dags_volume_host` or `dags_in_image` or `git_repo and git_branch and git_dags_folder_mount_point`

A clear and concise description of what the bug is.
Version of Helm and Kubernetes:
helm version                                                                               jeu. 25 juin 2020 09:30:50
Client: &version.Version{SemVer:"v2.16.1", GitCommit:"bbdfe5e7803a12bbdf97e94cd847859890cf4050", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.16.1", GitCommit:"bbdfe5e7803a12bbdf97e94cd847859890cf4050", GitTreeState:"clean"}

Which chart:
stable/airflow
What happened:
Containers with unready status: [airflow-web]

What you expected to happen:
More documentation in https://github.com/helm/charts/blob/master/stable/airflow/values.yaml#L22

You must provide those configs when using KubernetesExecutor.
The reason we can't automatically set these from the dags.git.* is because there is a significant difference in the formatting of things like secrets for SSH keys. I am planning on moving the git-sync container to the same one that airflow uses, which means people will only have to set dags.git.* for it to work.
See here: https://github.com/helm/charts/issues/22637#issuecomment-637983741


Occluder rendering, improvements to box rendering and more exposed functions

Exposed the scale attribute for WorldNodeStaticSceneData and WorldNodeRuntimeSceneData
Added GetStreamedNodeScale function to retrieve node scale
Added option for CET overlay to render occluders as boxes, based on their scale
Boxes are now rendered with proper rotation
Exposed GetScannerFilteredTargets for the use with other mods

Occluder box should be calculated in cpp (as for other nodes). Current CET implementation rotates and scales non-occluder nodes twice. It should be enough to include occluder nodes in this block https://github.com/psiberx/cp2077-red-hot-tools/blob/master/src/App/Runtime/InspectionSystem.cpp#L147-L170 and set showBoundindBox for projection based on boundingBoxMode. I'd add new option as local BoundingBoxMode = enum('ForAreaAndOccluderNodes', 'ForAreaNodes', 'Never').


Add insight

Add RTCStatsInsight and its example. This is an EventEmitter class for polling getStats() to observe connection status.

Closes #6


Cannot pull image in OpenShift

Expected Behavior
It should download from the default OpenShift registry.
Actual Behavior
It cannot access internal OpenShift Docker registry:
2019/03/14 09:10:17 Unable to read "/home/.docker/config.json": open /home/.docker/config.json: no such file or directory
2019/03/14 09:10:17 No matching credentials were found, falling back on anonymous
{"level":"error","logger":"controller.taskrun-controller","caller":"taskrun/taskrun.go:312","msg":"Failed to create build pod for task \"could not get digest for docker-registry.default.svc:5000/common/teradata: failed to fetch remote image docker-registry.default.svc:5000/common/teradata: couldn't get container image info from registry docker-registry.default.svc:5000/common/teradata: Get https://docker-registry.default.svc:5000/v2/:  x509: certificate signed by unknown authority\" :extract-schema","knative.dev/controller":"taskrun-controller","stacktrace":"github.com/knative/build-pipeline/pkg/reconciler/v1alpha1/taskrun.(*Reconciler).reconcile\n\t/usr/local/google/home/jasonhall/go/src/github.com/knative/build-pipeline/pkg/reconciler/v1alpha1/taskrun/taskrun.go:312\ngithub.com/knative/build-pipeline/pkg/reconciler/v1alpha1/taskrun.(*Reconciler).Reconcile\n\t/usr/local/google/home/jasonhall/go/src/github.com/knative/build-pipeline/pkg/reconciler/v1alpha1/taskrun/taskrun.go:174\ngithub.com/knative/build-pipeline/vendor/github.com/knative/pkg/controller.(*Impl).processNextWorkItem\n\t/usr/local/google/home/jasonhall/go/src/github.com/knative/build-pipeline/vendor/github.com/knative/pkg/controller/controller.go:271\ngithub.com/knative/build-pipeline/vendor/github.com/knative/pkg/controller.(*Impl).Run.func1\n\t/usr/local/google/home/jasonhall/go/src/github.com/knative/build-pipeline/vendor/github.com/knative/pkg/controller/controller.go:223"}

So the problems seem to be:

It seems to not correctly configure the Docker daemon
It outputs the errors via a different logging method
It does not configure the internal OpenShift registry as insecure-registry (could be a result of 1.)

Steps to Reproduce the Problem

Create TaskRun in OpenShift, which uses internal registry.

Additional Info

Seems like the problem was, that I overwrote entrypoint. Seems to work when switching to command.


Issue with laravel (probably)

After using composer install --no-dev --no-interaction and php artisan migrate and configuring the files in app/config when i got to the page hosting solder i get this http://i.imgur.com/BsDpfIc.png It was working and then one day it stopped. I have reinstalled solder twice thinking it would fix it but got not results, only wasted time.

What web server are you using? Have you configured it to run php files?

as i said it was fully working so yes, and I am running apache with ubuntu 16.04

Did you fix this? If you did, could you leave your solution for future googlers?


feat: Add fetchTaskRequestById

closes #1273

Files changed and their respective coverage:

File
% Stmts
% Branch
% Funcs
% Lines
Uncovered Line #s

taskRequests.js
100
100
100
100

tasksRequests.js
84.78
92.85
100
84.78


make start fails with cert error

make start fails with cert error
Downloading clear-29690-cloud.img.xz image
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 54.8M  100 54.8M    0     0  3856k      0  0:00:14  0:00:14 --:--:-- 6320k
Verification failure
140168122532288:error:21075075:PKCS7 routines:PKCS7_verify:certificate verify error:../crypto/pkcs7/pk7_smime.c:285:Verify error:unsupported certificate purpose
Image verification failed, see error above.

"unsupported certificate purpose" is a known issue caused by an incompatible openssl
version (https://github.com/clearlinux/distribution/issues/85). Other errors might indicate
a download error or man-in-the-middle attack.

To skip image verification run:
TEST_CHECK_SIGNED_FILES=false make start
test/start-stop.make:17: recipe for target 'start' failed
make: *** [start] Error 2

Environment
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"

$docker info
Server Version: 18.09.6
Storage Driver: overlay2
...
containerd version: bb71b10fd8f58240ca47fbb579b9d1028eea7c84
runc version: 2b18fe1d885ee5083ef9f0838fee39b62d653e30
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 5.0.11-050011-generic
Operating System: Ubuntu 18.04.2 LTS
OSType: linux
Architecture: x86_64

https://github.com/clearlinux/distribution/issues/85#issuecomment-498424419

Workaround for now
TEST_CHECK_SIGNED_FILES=0 make -d start

This is an issue that I brought up with the Clear Linux team a while ago in https://github.com/clearlinux/distribution/issues/85#issuecomment-395354903 but that was closed without resolving that particular aspect of the problem.
We tried  to make the error message as obvious as possible. Do we need to improve it further? Or should we disable the check by default? But then we might as well just remove the check entirely, because no-one will remember to turn it on.

Closing as this works as intended and it isn't obvious how that could be improved.


NIFI-13560 Change Parameter Provider handling to avoid storing values

Summary
NIFI-13560 Refactors Parameter Provider handling to avoid storing fetched Parameter Values in the persisted flow configuration.
The implementation change retains memory-based storage of fetched Parameter Values ,but stores a reference string in the serialized flow configuration. When the framework starts, the flow synchronization process fetches current values from referenced Parameter Providers.
This change requires configured Parameter Provider services to be accessible on startup, but otherwise retains existing behavior. This strategy restores centralized management of external Parameter Values to referenced external services. The nature of external vaults and secrets managers necessitates high availability, so the requirement for accessibility on application start should be reasonable for production deployments.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

I'm fine tackling the start up issue in a separate ticket since it is really an existing problem. Everything else is good here so +1

Thanks @bbende! I created NIFI-13575 to address the Jetty Server startup behavior.


Private pypi repo injected with deprecated settings for poetry 1.5+

Now that Habushu requires 1.5+, projects will get a deprecation warning when leveraging the pypiRepoId to specify a private repository. The pyproject.toml entry created by Habushu leverages the deprecated "secondary" property and priority resulting in the two warnings below:
Warning: Found deprecated key 'default' or 'secondary' in pyproject.toml configuration for source private-pypi-repo. Please provide the key 'priority' instead. Accepted values are: 'default', 'primary', 'secondary', 'supplemental', 'explicit'.
Warning: Found deprecated priority 'secondary' for source 'private-pypi-repo' in pyproject.toml. Consider changing the priority to one of the non-deprecated values: 'default', 'primary', 'supplemental', 'explicit'.

Fixed in PR #53


Some more simplifications

See each commit message for details.
Still more other pull requests more to come asap

the config var name should be websocket.servers (without concrete). But i think this was also wrong before. so i merge it and correct it by my self. Thanks to you

Yep! https://github.com/lemonbrain-mk/graphql_websocket/blob/1.2.2/controller.php#L48


Feature request: option to disable console clearing

Some commands such as CRA's "start" script clear the console (see facebook/create-react-app#2495), causing the previous output of the other commands to disappear when used with concurrently.
Would it be possible to add a command-line option to concurrently to disable the console clearing for all the child commands?

My issue was "tsc -w" clearing the console and that was fixed in https://github.com/Microsoft/TypeScript/issues/21295. In this ticket there are also some workarounds that might help, like dropping the control character that clears the screen using sed or awk.

My issue was "tsc -w" clearing the console and that was fixed in https://github.com/Microsoft/TypeScript/issues/21295. In this ticket there are also some workarounds that might help, like dropping the control character that clears the screen using sed or awk.

Hi, after some investigations (I had the exact same problem with tsc -w), I feel like there's just the need to catch the character \x1Bc.
In the TypeScript compiler, we got the following line:
const clearScreen = () => {
  process.stdout.write("\x1Bc");
}

For sanity of concurrently, I think it would be better to have the non-clearing option opt-in, and letting the user disabling it if he wants. Otherwise it's really weird, you can pretty easily get some other messages cleared by your compiler, etc. (Which is my case for info, my frontend messages are cleaned by the TS compiler, and I couldn't see them properly.)


fix: relative path from repo root directory

What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 57.728%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/bootstrap/bootstrap.go
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

internal/gen/keys/keys.go
5
11.76%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
6383

Relevant Lines:
11057

💛  - Coveralls


Please put the source tarball on PyPI so that it would be possible to install it with python's distutils

https://pypi.org/project/netron/

Can you provide some context why this is needed?

To enable packaging. Packages for python projects are typically created with distutils. Otherwise most users have no chance to see netron because people mostly install software using packages these days.

What kind of "packaging", what are examples? How is this different from pip install netron and why does it require a source tarball?

packaging like OS-level package creation, for example rpm/yum in Renhat/Fedora, apt-get in Debian, pkg in FreeBSD.
They all require sources to build and install.
pip is a python-specific packaging system. People mosty use OS-level packages to search for/install software, which is language-neutral.
TensorFlow for example is available this way for many systems: https://repology.org/project/tensorflow/versions

The Netron pip package is used to launch Netron as a Python server and is language-specific. It should not be used without Python.
The Netron client app and website get packaged through electron-builder and uploaded as deb, AppImage including source to https://github.com/lutzroeder/netron/releases. The script also pushes to snap but it's still experimental.

When I take the tarball from GitHub and run a normal build procedure it fails:
error: can't copy 'node_modules/d3/dist/d3.min.js': doesn't exist or not a regular file

What is a normal build procedure (what does it trigger) and what should it produce?

python setup.py config && python setup.py build && python setup.py install
It takes the source tree and installs the package into a given directory.

Running npm install first should resolve this, and there might be a way to run it as part of python build but not sure this is what you are actually looking for? For example, apt install should probably install the actual client app which is built via npx electron-builder --linux and is not using the python setup scripts at all. It might be helpful if you can provide some context of what you are trying to accomplish. What is the scenario and why does it need to get solved?

Running npm install first should resolve this

npm install is unsafe. It downloads files from GitHub without checking their fingerprints. When a package is created all sources it is built from are fingerprinted. It is this way in for RedHat rpms, Debian debs, and FreeBSD pkg packages.
They just don't create packages for npm-based projects due to safety concerns.

Are you planning to work on electron-builder and npm to fix those issues? electron-builder has an option to publish rpm to GitHub releases but sounds like this is not what you are looking for and probably would require some evidence this is actually needed. What exactly is the scenario you are trying to solve and why?

What exactly is the scenario you are trying to solve and why?

I was trying to build a package for netron so that it could be installed by users, but it doesn't seem that this can be done, because NodeJS's npm is inherently unsafe, and you are just looking for ways to push that unsafe code to users. RedHat and debian don't build rpms for npm projects due to security concerns. You seem to be trying to just ignore this.

When I take the tarball from GitHub and run a normal build procedure it fails:
error: can't copy 'node_modules/d3/dist/d3.min.js': doesn't exist or not a regular file

Same here.... Exactly the same error message.


Support for graphene >= 2.0?

Looks like only graphene <2.0 is supported. Is there any plan to support 2.x in the near future?
Thanks,

Yes, I planned to work on it as soon as it was finalized. I can't promise a firm timeline, but I might get to it this weekend.

I am also looking to use this with graphene 2.0+. Any update on when this will be supported?

I pushed the 2.X release to pypi and promoted it to master. The old 1.X is still around in case we need to apply any bug fixes


Launching bash from a Windows program which was started from bash fails (with an incorrectly formatted error)

I have build 15063.138.
Steps to reproduce:

Open bash.
Start cmd.exe.
Start bash (or try starting a linux tool using bash -c something).
Or, alternatively, run cmd.exe /c bash in bash.

Expected result: bash starts cmd, cmd starts another bash. (Should continue as deeply as I want.)
Actual result: The second bash doesn't start, but instead displays an error, which is even formatted incorrectly (see #2024). The text in the screenshot below would (after fixing the missing umlauts) translate as "The process is not supported. Press any key to continue.".
It is the same when just running bash.exe from within bash.

Running lxrun /update gives an also incorrectly formatted "Searching updates..." but then exits without further action.

Launching bash.exe using interop from inside WSL isn't a supported scenario at the time.
@jackchammons can provide details.

#1228

Marking as a duplicate of #1228.


[Feature Request] Show claim boundary using WE CUI

With the help of WE CUI, we can see the boundary of the claim land when we try to claim it. However, is it possible to show it again whenever we use the command /claiminfo (or add it as a button in the claiminfo menu) so it is much easier for us to check the boundary of an existing claimland?
I found this feature useful when I use residence in 1.7.10. It will be nice if GP have something similar. Thanks.

https://github.com/MinecraftPortCentral/GriefPrevention/wiki/WECUI-(Improved-Visuals)
Are you using WECUI + Liteloader?

@bloodmc I am using forge + WECUI... I somehow missed that docs but I tried today it does not seem to be working (the glowstone and gold blocks did show up but the WECUI grid didn't)
Local plugins:
WE: worldedit-forge-mc1.12-6.1.8-dist
WECUI: WorldEdit+CUI+Forge+Edition+2-2.1.2-mf-1.12-<IP_ADDRESS>7
Server plugins:
Sponge 3206
Forge 2705
WE: worldedit-forge-mc1.12-6.1.8-dist
GP: <IP_ADDRESS>8

You must use WECUI with liteloader. Forge edition is NOT supported.


npm run build fails

Describe the bug
lerna run build

lerna notice cli v8.1.6
lerna info versioning independent

 Lerna (powered by Nx)   Running target build for 3 projects

   ✖  @stacks/connect-ui:build
      ERROR: [Errno 2] No such file or directory: 'build'

————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 Lerna (powered by Nx)   Ran target build for 3 projects (276ms)

   ✔  0/1 succeeded [0 read from cache]

   ✖  1/1 targets failed, including the following:

      - @stacks/connect-ui:build

To Reproduce

clone repository
npm run build

Expected behavior
Build should succeed.
Environment
Debian 12, AMD64

Thanks for the report 🙏
Which noce version are you using and how did you install the dependencies (yarn/npm/etc.)?

iam using npm on node v18.19.0 (default version on my debian 12)
I tried npm install. That fails first because of outdated dependencies. After updating dependencies I get this error:
> postinstall
> concurrently 'husky install .github/.husky' 'yarn build:connect-ui'

00h00m00s 0/0: : [1] ERROR: [Errno 2] No such file or directory: 'build:connect-ui'
[1] yarn build:connect-ui exited with code 1
[0] install command is deprecated
[0] husky install .github/.husky exited with code 0
npm ERR! code 1
npm ERR! path .../connect
npm ERR! command failed
npm ERR! command sh -c concurrently 'husky install .github/.husky' 'yarn build:connect-ui'

It should work when using the yarn package manager instead. Can you try that?

yarn install worked but only on yarn berry, not with yarn classic. Maybe you mention that somewhere in the documentation.


Null complex property issue with typescript client

Describe the bug
When there is a null complex type in response, I receive following error:
Cannot read property 'Value' of null.
To Reproduce
Return a null complex inside a dto object.
Expected behavior
It should return a dto with a property of that complex type which is null
Screenshots / Logs / Exception details
In
var itemKeyFn = function(di) {
     if (typeof di["Value"] === "undefined")
          return undefined;
     if (di["Value"] === null)
          return null;
...
};

di itself is null!
Bit Server side products (Bit.OData, Bit.Signalr, etc)

Bit nuget package's version. 2.0
ASP.NET or ASP.NET Core? ASP.NET Core
Operating System. Win 7 SP1
.NET Core, mono or .Net Framework? NET 4.6.1

Bit CSharp client (If applicable)
N/A
Bit TypeScript/JavaScript client (If applicable)

Bit npm package's version. 2.0
Mobile, desktop or web app? Web App
Which browser? (If applicable) Chrome 73
Which framework? For example angular 7

Additional context
N/A

JayData 1.5.19 has been released. You can get it to solve this issue in your own app.


Miner stats don't report mined blocks

Running v0.1.15, mining on 4 processes.
miner 3 found block: 00085200-000042332522a07c638e297befae59785540dd9a0bd7c022f4c820b963eb66ff
2021-06-07 10:18:52 | uptime: 0:37:00 |  45 hash/sec | mined:   0 SKEPTI |  0.00 SKEPTI/h

I found out this is just a symptom of a bigger problem.
The network thread seems to crash with multiple KeyErrors like this once a block is mined:
Traceback (most recent call last):
  File "/home/luuk/projects/skepticoin-mining/venv/lib/python3.8/site-packages/skepticoin/networking/peer.py", line 148, in broadcast_message
    peer.send_message(message)
  File "/home/luuk/projects/skepticoin-mining/venv/lib/python3.8/site-packages/skepticoin/networking/peer.py", line 460, in send_message
    self.check_message_backlog()
  File "/home/luuk/projects/skepticoin-mining/venv/lib/python3.8/site-packages/skepticoin/networking/peer.py", line 465, in check_message_backlog
    self.start_sending()
  File "/home/luuk/projects/skepticoin-mining/venv/lib/python3.8/site-packages/skepticoin/networking/peer.py", line 468, in start_sending
    self.local_peer.selector.modify(self.sock, selectors.EVENT_READ | selectors.EVENT_WRITE, data=self)
  File "/usr/lib/python3.8/selectors.py", line 379, in modify
    raise KeyError(f"{fileobj!r} is not registered") from None
KeyError: "<socket.socket fd=100, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('<IP_ADDRESS>', 51304), raddr=('<IP_ADDRESS>', 2412)> is not registered"

** snip more KeyError stacktraces with different ip address / port combinations **

miner 0 found block: 00085296-00002369321d709ea6faf7dd7ad95afafd576bc812a85d1786b09f7ddb9edfbb

The following is speculation:

The NetworkThread dies (but how does it show multiple KeyErrors then?)
This causes chain height to not be updated for miners
Miner(s) keep mining at same height
Miner(s) end up mining various blocks at same height (I have evidence for this in the chain folder, also observed in #66)

I have not seen this error. But also all my mining is single-threaded across multiple machines. So I'll hypothesize there is a race condition somewhere when updating all the various Dict[]s that make up the blockchain pseudo-database.

I don't think there's a race condition in the blockchain dictionaries, because those are in CoinState and there is only one CoinState object, which is part of MinerWatcher.
I think this is one of the many bugs related to peers and networking.

There are not many peers today. I think it's just you, me, and sashimi. And sashimi doesn't have a static IP address.

Hi @lk16. I've been running a multi-thread miner for the last 12 hours and have not seen this error.
Could this be caused by a corrupted blockchain in your machine, same as issue #66?

I haven't seen this one in a while either. Let's close it.


Vulnerability roundup 112: vim-8.2.4350: 7 advisories [8.8]

search, files

[ ] CVE-2022-0729 CVSSv3=8.8 (nixos-unstable)
[ ] CVE-2022-0572 CVSSv3=7.8 (nixos-unstable)
[ ] CVE-2022-0629 CVSSv3=7.8 (nixos-unstable)
[ ] CVE-2022-0685 CVSSv3=7.8 (nixos-unstable)
[ ] CVE-2022-0943 CVSSv3=7.8 (nixos-unstable)
[ ] CVE-2022-0696 CVSSv3=5.5 (nixos-unstable)
[ ] CVE-2022-0714 CVSSv3=5.5 (nixos-unstable)

CVE details
CVE-2022-0729
Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4440.
CVE-2022-0572
Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
CVE-2022-0629
Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
CVE-2022-0685
Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4418.
CVE-2022-0943
Heap-based Buffer Overflow occurs in vim in GitHub repository vim/vim prior to 8.2.4563.
CVE-2022-0696
NULL Pointer Dereference in GitHub repository vim/vim prior to 8.2.4428.
CVE-2022-0714
Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4436.

Scanned versions: nixos-unstable: 710fed5a248.
Cc @equirosa
Cc @lovek323

Fixed in #165807


"Custom formatters" docs mention subclassing/overriding in text but use notifications in the example

https://relishapp.com/rspec/rspec-core/v/3-4/docs/formatters/custom-formatters
It's unclear what you're actually expected to do.

You have to do the later regardless of wether you subclass or not.

@JonRowe Thank you. I was actually not asking for me but rather suggesting that those docs could be clarified to help others.
If I ever work on custom formatters enough to know how to clarify the docs myself, I might, but I don't think I will work on that today.

We always welcome PR improvements to the documentation if you have suggestions.


Choose status which abort the flow build.

You can choose the status (Success, Unstable or Failure), which abort the flow build. It also contains, that the build can not be 'better' than any build inside the flow build.

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

awesome that there are tests! :+1: please rebase and make sure that the feature is opt-in only. thanks a lot.

once you are done with your changes, I would also appreciate if you could squash relevant changes together. thank you!

All changes squashed together.


feat: Add support for auto add examples to readme

Description
Please include a summary of the change and which issue is fixed. Also, please include the motivation and context for the change. List any dependencies that are required for this change.
Check the relevant boxes:

[ ] Bug fix (nonbreaking change that fixes an issue)
[ ] New feature (nonbreaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI related update (pipeline, etc.)

Checklist

[ ] If relevant, a test for the change has been added or updated as part of this PR.
[ ] If relevant, documentation for the change has been added or updated as part of this PR.

Merge

Merge using "Squash and merge".
Make sure to use a relevant conventional commit message that is based on the PR contents. The commit message determines whether a new version of the modules needs to be released, and if so, which semver number to use).

issue: https://github.ibm.com/goldeneye/issues/issues/2177


mockup: Drawer nav on the leftmost bottom tab

Implemented:

Four buttons at the top gone :)
Hamburger icon to open the drawer from drawer nav's default screen
(labeled "Home" in the drawer)
Swipe from left to open the drawer
backBehavior="initialRoute" (my "resolved concern" in
https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/left-side.20drawer.20nav/near/1308981 )

Not implemented:

Full app bar (just a quick hamburger menu)
Resetting to default screen (dubbed "Home") when you go to a
different bottom tab and come back (don't think this would be too
hard?)
Sane deduplication of lots of code :P
…probably quite a bit more that I'm not remembering right now, but
it's a quick mockup ;P

Code details for developers:
I used copy-and-paste to an extent that would be irrational for
production code. :) It's why I was able to do a mockup so quickly.
It'll be tricky but informative to deduplicate well. I can talk more
about why I think so, or you might reach the same conclusion by just
studying the code and the APIs. (Maybe git diff has something to
help you see what tweaks I made after copy-pasting.)
Anyway, here's a sketch of how the code got to where it is:

HomeScreen was sitting on the main-tabs navigator, as the 'home'
screen (the leftmost tab). Now, a new HomeDrawerNavigator is in
its place there.
The stuff that was being rendered on HomeScreen has moved to a new
DefaultScreen, minus the four buttons at the top.
I made an AllNarrowScreen, StarredNarrowScreen,
MentionedNarrowScreen, and SearchInHomeDrawerScreen. The first
three were copied from ChatScreen (with the narrow hard-coded);
the last, from SearchMessagesScreen.

(This may be the first time I've been confident about correctly using the "experimental UI/UX" label!!)
Screenshots coming soon. 🙂

Also: Untested on Android, just my iPhone so far.

Closing as not planned.


chore: release main

:robot: I have created a release beep boop
app-info: 1.0.2
1.0.2 (2022-10-12)
Bug Fixes

add the @readonly tag to appInfo properties (8ea488a)

errors: 1.2.3
1.2.3 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)
use module.exports for consistency (8cdd4d7)

log-error: 1.3.7
1.3.7 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)
use module.exports for consistency (8cdd4d7)

Documentation Changes

use GitHub's note/warning highlights (4a40080)

Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/app-info bumped from ^1.0.1 to ^1.0.2
@dotcom-reliability-kit/serialize-error bumped from ^1.1.2 to ^1.1.3
@dotcom-reliability-kit/serialize-request bumped from ^1.0.1 to ^1.0.2

middleware-log-errors: 1.2.8
1.2.8 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)

Documentation Changes

use GitHub's note/warning highlights (4a40080)

Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/log-error bumped from ^1.3.6 to ^1.3.7

middleware-render-error-info: 1.1.6
1.1.6 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)

Documentation Changes

use GitHub's note/warning highlights (4a40080)

Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/app-info bumped from ^1.0.1 to ^1.0.2
@dotcom-reliability-kit/log-error bumped from ^1.3.6 to ^1.3.7
@dotcom-reliability-kit/serialize-error bumped from ^1.1.2 to ^1.1.3

serialize-error: 1.1.3
1.1.3 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)

serialize-request: 1.0.2
1.0.2 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/app-info-v1.0.2 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/errors-v1.2.3 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/log-error-v1.3.7 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/middleware-log-errors-v1.2.8 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/middleware-render-error-info-v1.1.6 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/serialize-request-v1.0.2 :sunflower:


Request changed from 'Intake in Progress' to 'Open' state - not posted to Comments tab

Describe the bug in current situation
Prior to release 8.0, when a request was moved from 'Intake in Progress' to 'Open' state, the state change was posted to the Comments tab.
However, after the 8.0 release, this is no longer being posted. See ECC-2023-31876 for example in PROD.
NOTE: users are still being sent the state change notification. In addition, this does not occur when changing a request from 'Call for Records' back to 'Open'. It appears to be tied specifically to the 'Intake in Progress' -> 'Open' state change.
Link bug to the User Story
#802
Impact of this bug
Low
Chance of Occurring (high/medium/low/very low)
High
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
PROD or TEST
Steps to Reproduce
Steps to reproduce the behavior:

Create a new request in TEST, save the request at 'Intake in Progress'
Change the state from 'Intake in Progress' -> 'Open'
Click on the Comments tab
See error, with the state change to 'Open' not being posted

Actual/ observed behaviour/ results
State change to 'Open' not being posted in Comments tab
Expected behaviour
A clear and concise description of what you expected to happen. Use the gherking language.
GIVEN a user is on a request in 'Intake in Progress'
WHEN the user changes the request to 'Open'
THEN the request moves to the 'Open' state
AND the state change is posted to the Comments tab
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.
State change that should be posted to Comments tab

Confirmed 'Open' state change is now posted to Comments tab when going from 'Intake in Progress' -> 'Open' and 'Intake in Progress' -> 'Peer Review' -> 'Open'


How to set screen size?

Hello the mouse only works on left two thirds of the screen. I gues it has something to do with screen size, my lapto has 1920x1080. Can I reconfigure it somewhere?

Hi, sorry for the late reply.
Thank you for setting up the issue.
Perhaps it is due to this part.
https://github.com/takeyamayuki/NonMouse/blob/c80fe96b51c20e6b39e463a8ca4861c56e62972a/app.py#L30-L31
I suspect it is a bug in tkinter, please try changing your tkinter version to the latest one.


False-positive diagnostics with sending parameters and use of RBI

Description
I've run into a several cases with compiler that in some of them to my understanding shouldn't produce an error while it does, and one of them should, while it doesn't.
Reproduction
Given that initially:
// snippet 1
protocol Command<In, Out> {
    associatedtype In
    associatedtype Out

    func execute(_ input: In) async throws -> Out
}

protocol CommandsFactory {
    associatedtype LoggerCommandType: Command<String, Void>
    func logger() -> sending LoggerCommandType
}

@MainActor
final class UseCase<Factory> where Factory: CommandsFactory {
    private let factory: Factory

    init(factory: Factory) {
        self.factory = factory
    }
}

If I add doSmth function to the UseCase in the following manner, there is an error, while I think it should be safe:
// snippet 2
extension UseCase {
    func doSmth() async throws {
        let command = factory.logger() // should be in a disconnected region here
        try await command.execute("did it!") // error: sending 'command' risks causing data races
    }
}

It is gone if CommandsFactory gets changed to be a concrete type instead of a protocol & generic constraint, so seems like compiler doesn't reason well for protocol case here.
When I wrap this is in a Task in a bit odd manner, the error is gone however:
// snippet 3
extension UseCase {
    func doSmthWithTask() async throws {
        let factory = factory
        try await Task {
            let command = factory.logger()
            try await command.execute("did it!") // ok
        }.value
    }
}

But it is gone too good, since it is missing when I think it should be:
// snippet 4
@MainActor
final class Wrapper<CommandType> where CommandType: Command<String, Void> {
    private let command: CommandType

    init(command: CommandType) {
        self.command = command
    }

    func execute() async throws {
        let command = command
        try await Task {
            try await command.execute("I'm wrapped!") // no complaints here
        }.value
    }
}

command isn't guaranteed to be a struct, so it might not get copied, causing potential data race.
Expected behavior
In snippet 2 I'd expect it to compile without the error, as it does currently when using a concrete type.
In snippet 4 I think there should be an error calling command.execute in that way, as command isn't in a disconnected region (at least, not that compiler can be certain about I guess).
Environment
swift-driver version: 1.115 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.10 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0
Additional information
No response

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Reproduced with Xcode 16 RC
cc @hborla

Just looked at this with ToT, we get no errors. The change that caused this to not emit errors was in between swift-DEVELOPMENT-SNAPSHOT-2024-08-21-a and swift-DEVELOPMENT-SNAPSHOT-2024-08-26-a.

So the fourth example should be safe since the isolation is:
@MainActor
final class Wrapper<CommandType> where CommandType: Command<String, Void> {
    private let command: CommandType

    init(command: CommandType) {
        self.command = command
    }

    func execute() async throws {
        let command = command // command is already in the main actor region
        try await Task {
            // Task's closure is inferred to be main actor isolated, so we are putting main actor region state into a main actor
            // isolated closure which is safe.
            try await command.execute("I'm wrapped!") // no complaints here
        }.value
    }
}

@gottesmm thank you for taking a look! Just checked and I also don't have error for the second snipped with the latest toolchain, that is pretty great news (at least for me for sure!) as it was a bit painful to deal with.

@gottesmm maybe it may help to diagnose the issue (seems like related): I've modified fourth snipped to have Task.detached after reading your comments that command might be inferred to be isolated, and with the latest toolchain got the crash on assertion:
Assertion failed: (!type->hasTypeParameter() && "must take a contextual type. if you really are ok with an " "indefinite answer (and usually YOU ARE NOT), then consider whether " "you really, definitely are ok with an indefinite answer, and " "use `checkConformanceWithoutContext` instead"), function checkConformance, file ConformanceLookup.cpp, line 757.

With stacktrace:
1.	Apple Swift version 6.1-dev (LLVM 9d655fdc6103926, Swift 0d16cbf5d5ef6f9)
2.	Compiling with the current language version
3.	While evaluating request ExecuteSILPipelineRequest(Run pipelines { Mandatory Diagnostic Passes + Enabling Optimization Passes } on SIL for swift_sending_check)
4.	While running pass #193 SILFunctionTransform "TransferNonSendable" on SILFunction "@$s19swift_sending_check7WrapperC7executeyyYaKF".
 for 'execute()' (at /Users/kyrylokhlopko/Projects/swift-sending-check/Sources/swift-sending-check/swift_sending_check.swift:52:5)
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
0  swift-frontend           0x0000000106808e0c llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 56
1  swift-frontend           0x00000001068074f0 llvm::sys::RunSignalHandlers() + 112
2  swift-frontend           0x0000000106809468 SignalHandler(int) + 304
3  libsystem_platform.dylib 0x000000018b24c184 _sigtramp + 56
4  libsystem_pthread.dylib  0x000000018b216f70 pthread_kill + 288
5  libsystem_c.dylib        0x000000018b123908 abort + 128
6  libsystem_c.dylib        0x000000018b122c1c err + 0
7  swift-frontend           0x0000000106db258c swift::TypeBase::isSendableType() (.cold.1) + 0
8  swift-frontend           0x000000010240f194 swift::checkConformance(swift::Type, swift::ProtocolDecl*, bool) + 176
9  swift-frontend           0x000000010240f3c4 swift::TypeBase::isSendableType() + 372
10 swift-frontend           0x00000001019fc958 swift::SILIsolationInfo::isNonSendableType(swift::SILType, swift::SILFunction*) + 512
11 swift-frontend           0x00000001017626cc (anonymous namespace)::TransferNonSendableImpl::emitVerbatimErrors() + 8856
12 swift-frontend           0x000000010175d838 (anonymous namespace)::TransferNonSendable::run() + 6756
13 swift-frontend           0x0000000101783cb0 swift::SILPassManager::runPassOnFunction(unsigned int, swift::SILFunction*) + 1440
14 swift-frontend           0x0000000101784b1c swift::SILPassManager::runFunctionPasses(unsigned int, unsigned int) + 1060
15 swift-frontend           0x0000000101787300 swift::SILPassManager::execute() + 596
16 swift-frontend           0x0000000101781bd4 swift::SILPassManager::executePassPipelinePlan(swift::SILPassPipelinePlan const&) + 72
17 swift-frontend           0x0000000101781b54 swift::ExecuteSILPipelineRequest::evaluate(swift::Evaluator&, swift::SILPipelineExecutionDescriptor) const + 68
18 swift-frontend           0x00000001017d2040 swift::SimpleRequest<swift::ExecuteSILPipelineRequest, std::__1::tuple<> (swift::SILPipelineExecutionDescriptor), (swift::RequestFlags)1>::evaluateRequest(swift::ExecuteSILPipelineRequest const&, swift::Evaluator&) + 28
19 swift-frontend           0x000000010179e724 swift::ExecuteSILPipelineRequest::OutputType swift::Evaluator::getResultUncached<swift::ExecuteSILPipelineRequest, swift::ExecuteSILPipelineRequest::OutputType swift::evaluateOrFatal<swift::ExecuteSILPipelineRequest>(swift::Evaluator&, swift::ExecuteSILPipelineRequest)::'lambda'()>(swift::ExecuteSILPipelineRequest const&, swift::ExecuteSILPipelineRequest::OutputType swift::evaluateOrFatal<swift::ExecuteSILPipelineRequest>(swift::Evaluator&, swift::ExecuteSILPipelineRequest)::'lambda'()) + 204
20 swift-frontend           0x0000000101781db0 swift::executePassPipelinePlan(swift::SILModule*, swift::SILPassPipelinePlan const&, bool, swift::irgen::IRGenModule*) + 64
21 swift-frontend           0x00000001017b40c0 swift::runSILDiagnosticPasses(swift::SILModule&) + 192
22 swift-frontend           0x0000000100f6ce5c swift::CompilerInstance::performSILProcessing(swift::SILModule*) + 80
23 swift-frontend           0x0000000100d1cc34 performCompileStepsPostSILGen(swift::CompilerInstance&, std::__1::unique_ptr<swift::SILModule, std::__1::default_delete<swift::SILModule>>, llvm::PointerUnion<swift::ModuleDecl*, swift::SourceFile*>, swift::PrimarySpecificPaths const&, int&, swift::FrontendObserver*) + 820
24 swift-frontend           0x0000000100d1c2b4 swift::performCompileStepsPostSema(swift::CompilerInstance&, int&, swift::FrontendObserver*) + 656
25 swift-frontend           0x0000000100d28788 withSemanticAnalysis(swift::CompilerInstance&, swift::FrontendObserver*, llvm::function_ref<bool (swift::CompilerInstance&)>, bool) + 160
26 swift-frontend           0x0000000100d1e180 performCompile(swift::CompilerInstance&, int&, swift::FrontendObserver*) + 716
27 swift-frontend           0x0000000100d1d84c swift::performFrontend(llvm::ArrayRef<char const*>, char const*, void*, swift::FrontendObserver*) + 2328
28 swift-frontend           0x0000000100af925c swift::mainEntry(int, char const**) + 3100
29 dyld                     0x000000018ae94274 start + 2840


Playwright - I.haveRequestHeaders doesn't set headers

What are you trying to achieve?
I'm trying to set headers using I.haveRequestHeaders.
What do you get instead?
The headers are not set.
Details

CodeceptJS version: 3.3.3
NodeJS Version:16.15.1
Operating System: Debian GNU/Linux 9.12
Playwright version: 1.22.2

It stopped working after upgrading to a new CodeceptJS version.

I'm using latest version of codeceptjs 3.3.4 and playwright 1.23.2 and unfortunately cannot reproduce this issue


Add support for JSON marshalling

Add support for JSON marshalling of tuples in response to #20

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1464

Relevant Lines:
1464

💛  - Coveralls


Error patch

Fixes an issue where error data was not cleared between invocations, and package was modifying the data type of the errors field to make it a list rather than passing the error

We should change this to create a new dict object on each invocation rather than keeping an instance var (just FYI)


Structs Lesson Broken Link

When accessing the Structs page from https://softchris.github.io/golang-book/ the link returns a 404 error

Hello @softchris ,
The folder name for 02-structs contains a whitespace which is causing this issue. As we cannot clone it, you need to fix this from your side.


[hotfix] cover non-tested data table v4 code path

At first I thought datatable version has been defaulted to v4 when committing #9731 . but apparently it is not even tested.
created this hotfix follow up as well as adding abundant tests.

Since this is labelled as hotfix, I am wondering if you have started using V4.
AFAIK, it wasn't tested and there was plan to move over to V4 since it also has NULL handling support IIRC. The current / default version is V3.

Since this is labelled as hotfix, I am wondering if you have started using V4.
AFAIK, it wasn't tested and there was plan to move over to V4 since it also has NULL handling support IIRC. The current / default version is V3.

label as hotfix because this was a regression introduced a bit earlier:

when i decouple the code in #9731 , the DataTableImplV4 becomes a copy of the original BaseDataBlock, but since it is no longer a data block, we dont have the test coverage via the DataBlockTest, and neither was it tested in the DataTableTest b/c it doesn't test V4 (only V3)
it is not being used after the decoupling, but it is still good to test the V4 impl.


Overheating/CPU

From @arnottcr on January 16, 2015 4:46
NFC, but it appears to be an issue.
Copied from original issue: winhowes/grd.me#9

From @floryst on February 1, 2015 2:23
Similar issue on Firefox 35.0.1. Opening a conversation results in ~4-5 sec page freeze.
EDIT: From what I can see, it's partly the ecc.decrypt() call, partially the crypto-detector. When viewing messages from the message full message view, crypto-detector takes 2*(~1s) because it first decrypts the message in the main window and then the blurb on the side. The rest of the 2-3s is likely the ecc.decrypt() call.

From @winhowes on January 23, 2015 9:37
hmm, yeah I'll keep looking into this. On a fresh version of the latest FF I only have about a 5-8% cpu increase.  And Chrome seems pretty much negligible.  I have a few potential optimizations in mind, but they may cause the crypto-detector to miss a few edge cases.

From @floryst on February 1, 2015 2:23
Similar issue on Firefox 35.0.1. Opening a conversation results in ~4-5 sec page freeze.
EDIT: From what I can see, it's partly the ecc.decrypt() call, partially the crypto-detector. When viewing messages from the message full message view, crypto-detector takes 2*(~1s) because it first decrypts the message in the main window and then the blurb on the side. The rest of the 2-3s is likely the ecc.decrypt() call.

From @winhowes on January 23, 2015 9:37
hmm, yeah I'll keep looking into this. On a fresh version of the latest FF I only have about a 5-8% cpu increase.  And Chrome seems pretty much negligible.  I have a few potential optimizations in mind, but they may cause the crypto-detector to miss a few edge cases.

We should probably compare the code base for Mailvelope/WebPG, as they either have the same problem, have solved it or cheated.

We should probably compare the code base for Mailvelope/WebPG, as they either have the same problem, have solved it or cheated.

From @winhowes on February 1, 2015 7:53
Yeah I totally agree - I also have a few new optimizations in mind that I'll play around with and report back here on.

From @winhowes on February 1, 2015 7:53
Yeah I totally agree - I also have a few new optimizations in mind that I'll play around with and report back here on.

From @winhowes on February 1, 2015 8:34
Looks like at they're using openpgp.js, https://github.com/openpgpjs/openpgpjs, or something similar in the case of webPG

From @winhowes on February 1, 2015 8:34
Looks like at they're using openpgp.js, https://github.com/openpgpjs/openpgpjs, or something similar in the case of webPG

If we move to a local database and place nonces with all messages, would it decrease lag due to decryption as it is now a constant time look-up, not a full decrypt operation?

If we move to a local database and place nonces with all messages, would it decrease lag due to decryption as it is now a constant time look-up, not a full decrypt operation?

From @winhowes on February 2, 2015 4:9
Potentially. Issues with that are: knowing everyone in the group, implementing the secondary channel (though you could also just cache things), and memory. Right now I'm limited to 5mb on Firefox and Chrome. There's a way for me to get more on Chrome that I'll eventually implement, but I still need to figure out Firefox

From @winhowes on February 2, 2015 4:9
Potentially. Issues with that are: knowing everyone in the group, implementing the secondary channel (though you could also just cache things), and memory. Right now I'm limited to 5mb on Firefox and Chrome. There's a way for me to get more on Chrome that I'll eventually implement, but I still need to figure out Firefox

can you write things to disk, or are you limited to 5mb total? also, how much text is a 5mb sqlite database?

can you write things to disk, or are you limited to 5mb total? also, how much text is a 5mb sqlite database?

From @winhowes on February 2, 2015 6:37
I think I can create files and so I could read/write things that way (assuming that's true)... Not sure how much text that is. The bigger concern is the secondary channel

From @winhowes on February 2, 2015 6:37
I think I can create files and so I could read/write things that way (assuming that's true)... Not sure how much text that is. The bigger concern is the secondary channel

From @floryst on February 2, 2015 15:28
The decryption/scanning blocks the main UI thread, which is something we don't want. I'm going to try using DOMWorkers to background the decryption task.

From @floryst on February 2, 2015 15:28
The decryption/scanning blocks the main UI thread, which is something we don't want. I'm going to try using DOMWorkers to background the decryption task.

From @winhowes on February 2, 2015 15:42
^ yep that was one thought I had

From @winhowes on February 5, 2015 2:5
So #16 has been implemented. I'm now only seeing a 3-10% cpu increase, but hardly any difference in responsiveness (web worker is keeping decryption from blocking page rendering). Are you  both still seeing performance issues?

From @winhowes on February 2, 2015 15:42
^ yep that was one thought I had

From @winhowes on February 5, 2015 2:5
So #16 has been implemented. I'm now only seeing a 3-10% cpu increase, but hardly any difference in responsiveness (web worker is keeping decryption from blocking page rendering). Are you  both still seeing performance issues?

will check tomorrow, busy tonight; sounds awesome though!

will check tomorrow, busy tonight; sounds awesome though!

This issue is far from solved on Firefox 35.0, but is much better on firefox-nightly with e10s enabled

From @winhowes on August 19, 2015 17:34
Can you see if this is any better on the latest version? It is on my machine, and I think we may be able to close this issue

From @winhowes on August 19, 2015 17:34
Can you see if this is any better on the latest version? It is on my machine, and I think we may be able to close this issue

This issue is far from solved on Firefox 35.0, but is much better on firefox-nightly with e10s enabled


Carthage - Mockingjay for iOS

I use Carthage and it uses shared schemes to build dependencies but there is only a target for Mac OS X, could iOS be added so it works with Carthage?

@TomasLinhart The target is not OS X, but a universal target supporting both iOS and OS X.
What error message are you seeing?

@kylef I don't see any error but Carthage produces only framework for Mac OS X and when I clone the repository and check the project there are only two targets. Mockingjay that has base SDK for OS X and MockingjayTests that doesn't produce any product, of course.
So there isn't any target that would have iOS as the base SDK.
You can check https://github.com/Quick/Nimble to see how others do it.

The Mockingjay target is capable of building iOS.

Which version of Carthage are you running?

Oh right, I see. I have Carthage 0.8.0.

Carthage 0.8.0 is unsupported. Please upgrade to Carthage 0.9 which should solve this problem.
Please let me know if you have any other issues.

I have upgraded to Carhage 0.9.3 and it doesn't work. Now it fails while it is building.
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_XCTest", referenced from:
      static ext.Mockingjay.ObjectiveC.XCTest.initialize (ObjectiveC.XCTest.Type)() -> () in XCTest.o
      @objc static ext.Mockingjay.ObjectiveC.XCTest.initialize (ObjectiveC.XCTest.Type)() -> () in XCTest.o
      l__CATEGORY_XCTest_$_Mockingjay in XCTest.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Does it work for you with Carthage?

There are two issues preventing carthage from building that I've found:
Undefined symbols for XCTest framework as described by @TomasLinhart. Further up in the error log this is what is the root cause of this message:
ld: warning: Auto-Linking supplied '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest', '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target.
Undefined symbols for architecture armv7:
  "_OBJC_CLASS_$_XCTest", referenced from:
      l__CATEGORY_XCTest_$_Mockingjay in XCTest.o
      static ext.Mockingjay.ObjectiveC.XCTest.initialize (ObjectiveC.XCTest.Type)() -> () in XCTest.o
      @objc static ext.Mockingjay.ObjectiveC.XCTest.initialize (ObjectiveC.XCTest.Type)() -> () in XCTest.o
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)

For some reason despite Xcode showing that Bitcode Enabled is set to No, after toggling this setting it will explicitly set ENABLE_BITCODE = NO; in project.pbxproj that fixes this issue.

The second issue that occurs is a code signing error for MockingjayTests target.
Check dependencies
CodeSign error: code signing is required for product type 'Unit Test Bundle' in SDK 'iOS 9.0'

There are two ways of fixing this:

Remove MockingjayTests from the Run setting in Mackingjay scheme.
Set the code signing explicitly for iOS SDK to 'iPhone Developer' mirroring the setting for Mockingjay framework target.

I've created a pull request that fixes these issues and will build on carthage 0.9.3, tested by cloning the repository down and running carthage build --no-skip-current in the repository root. See pull request kylef/mockingjay#30


gh/workflows: Update L4LB 1.1{0,1,2} jobs

This commit is a partly backport of [1] to the v1.1{0,1,2} branches.
Switching the KIND image is done in the [2][3][4] PRs.
[1]: https://github.com/cilium/cilium/pull/20682/
[2]: https://github.com/cilium/cilium/pull/20918
[3]: https://github.com/cilium/cilium/pull/20919
[4]: https://github.com/cilium/cilium/pull/20920

/ci-l4lb-1.10

/ci-l4lb-1.10


[SymbolGraph] Use the frontend option tables instead of llvm::cl for argument parsing

I found one spot where an optimizer test was accidentally using one of the symbol graph options via -Xllvm, but the main motivation here is to migrate swift-api-digester from a standalone tool to a frontend-integrated one. I was running into some issues because that also uses llvm::cl and a number of the option definitions were clashing with those of swift-symbolgraph-extract. I think gradually migrating all of the frontend tools to the shared option table should scale a little better in the long run.
The existing tests seemed to cover the existing options well, but I'm happy to add more if there's any I missed!

@swift-ci please smoke test

@bitjammer thanks for taking a look!

Rebasing to fix a minor merge conflict
@swift-ci please test


I need a good README to this project

The README file must gave some examples with some instruction points.
1 - A logo will be nice!
2 - Prettier template will be nice too...

Fallow below a simple ideia what you can do in this README file ('is not the rule')

3 - This project has two stage modes, development and production, you can change this config creating your own docker-compose file.
4 - Inside this project has a docker-compose.yaml and you can use that if you want.
5 - The Dockerfile and docker-compose can be easier edited conform you wanted. The production environment in stage "production"
6 - You can choose with you want to use sock unix to comunicate with PHP-FPM or TCP connection.

I have created a PR to solve this issue. Can you check it? https://github.com/matheusbloise/docker-multi-stage-php-nginx/pull/5

Thanks for all, i already linked and assigned the issues to your PR.


{containerapp} add random config directory for test

Related command

None
Description

Add random config directory to fix batch CI. Avoiding configure default location with az configure --default in containerapp test cases effect other services' test.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

containerapp


[FLPATH-461] Change phase for autoclean in workflow-service-sdk

What this PR does / why we need it:
When there is a change in any DTO file and that  mvn clean install is run, the build fails if the openapi.json file is not commited
The PR changes the phases in which skip-if-no-modifications and auto-clean are done
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story (FLPATH-xxxx):
Fixes #FLPATH-461
Change type

[ ] New feature
[x] Bug fix
[ ] Unit tests
[ ] Integration tests
[ ] CI
[ ] Documentation
[ ] Auto-generated SDK code

Impacted services

[ ] Workflow Service
[ ] Notification Service

Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.


Add "retry" to some base CI image

https://github.com/owncloud/ocis/pull/4223 fetched "retry" into the nodejs image that is used in ocis CI.
Maybe we should add this "retry" script into some "base" CI image so that it is "just there" for the JS, PHP etc images in CI.
@xoxys do you know if it is already somewhere in the chain of docker images?
Where is best to put it?

It is already in the node image but I mentioned it already in the initial discussion. Fetching it in ci is definetly the wrong way https://github.com/owncloud-ci/nodejs/blob/master/v16/Dockerfile.amd64#L15
Just add it in the same fashion to other reqired images so renovate will take care of uodates.

Unneeded curl removed in https://github.com/owncloud/ocis/pull/4247

I guess that we might have a use for retry in the:

owncloudci/php docker images. They do composer things fetch dependencies and might fail if upstream is rate-limiting, or behaving sub-optimally or...
owncloudci/golang - that is used in CI where make ci-go-generate make -C ocis build etc happens. Those sort of commands have the potential to fail due to network, upstream server... issue

@xoxys Should I make PRs to those repos to add the retry script"?

https://github.com/owncloud-ci/golang/pull/91
https://github.com/owncloud-ci/php/pull/153
now retry is available with the images of all 3 languages commonly used in CI - go, js, php. That should be enough - we will mostly use retry for getting building, checking dependencies etc, with "package manager" type of tools of those languages.


improving logging and save result on errors too

Summary

When an exception happens, the job returns "{ status_code: 500, response: nil }" and nothing gets logged. My suggestion is saving the error message as response and also add logs to the different job steps: processing, process succesfull and process failures.

@hdf1986 @Martum @sbalay @mishuagopian can we merge this?


[Math] Add a solution to Permutation Sequence

Already upgraded progress. Please check.

Hi Sorry seems there is a conflict in README file. I guess you have to update the question number we have resolved in progress session. Thanks.

Already Updated the progress to 276.


ConvertTo-Bicep defaults to overwriting existing files.

The default behaviour of the bicep cli when running bicep decompile template.json is to overwrote already existing .bicep files in the current folder, and as so, for parity, running ConvertTo-Bicep template.json also has this behaviour.
However, this does not seem to be the "powershell" way. Most powershell CmdLets / commands will not overwrite any existing files unless you use the -force flag.
Having ConvertTo-Bicep automatically overwrite files could lead to loss of data for someone who is not aware of this behaviour.
Adding to this, a normal workflow can be creating arm templates using Azure GUI, and saving those as arm, and after this converting to bicep. Since Azure automatically names these exports template.json chances of overwriting increases as all these exports will be named template.bicep
So: Should we take this in to concideration and follow the standard powershell way, or keep it as it is and follow bicep CLI behaviour?
changing: Is a breaking change but keeps powershell standard
keeping: consistent with Bicep CLI, but can be confusing for powershellers.

I vote for a breaking change to keep it more PowerShell-y, with a warning if there's a file that wasn't overwritten or vice versa.

the middle road would be the ConfirmPreference way:
If the file already exists ask for permission to overwrite if ConfirmPreference is not set to lower than the command implementation, or run with -Confirm:$false.
I honestly don't think that's a good idea, but for the sake of discussion I'm throwing it in here.

After some thinking I've come to the conclusion that I agree. We should stop overwriting the file unless the -Force switch is used. Build-Bicep also overwrites the file, but that is a completely different story.

Good! Since this is considered breaking though, it should be a major update to the module. Put it on a future feature list, or shall I implement it= How do you want to move ahead with it?

We will go for 2.0 when and if we can solve #182. Maybe we should ship this in 2.0 as well.


Ticking block entity NullPointerException server crash

Issue description:
The server crashed while no one was online and then crashed on startup due to "NullPointerException: Ticking block entity". The solution was to use NBTEditor to directly access the relevant entity and delete it from the world. The entity was a controller.
Version (Make sure you are on the latest version before reporting):
Minecraft: 1.10.2
Forge: forge-1.10.2-<IP_ADDRESS>.54
Refined Storage: 1.2.22
Does this issue occur on a server?  Y
If a (crash)log is relevant for this issue, link it here:
crash-2017-04-02_15.03.23-server.txt

Duplicate of #1016


[FEATURE] Question: is there a way of routing between several chatflows?

Describe the feature you'd like
I have several chatflows, each handling specific chatbot functionalities. I call these chatflows from the backend and wonder if there’s a way to dynamically route user queries to the appropriate chatflow.
For context:

Routing can sometimes be determined by conditions (e.g., if a user isn’t found in the database, route them to the register-chatflow).
However, in other cases, the decision isn’t straightforward based on context or user state.
I’m not aware of any built-in Flowise feature for routing but would like to know if anyone has a more efficient solution.

Ideas I’ve considered:

Create an additional chatflow to act as a router, analyzing user input and responding with the appropriate chatflow to call. This router would  know when each one of other chatflows should be called.
Use predefined user commands to switch functionalities (e.g., type "menu" to view the menu or "add dish" to modify it).

Both approaches have drawbacks, so I’m looking for a smarter way to implement routing.

You might be looking for agentflow condition agent: https://docs.flowiseai.com/using-flowise/agentflows/sequential-agents#id-8.-condition-agent-node
you can chain multiple agents/llm, but not chatflow (work in progress)


Document issue with LXD performance when backed by LVM with a large v…

…olume of archive metadata (high container, volume turnover)
Extension of https://github.com/lxc/lxd/issues/3942 which turned out to be a misconfiguration on my side. I consider my issue closed if the documentation is updated to reflect the fact that an external piece of software may be responsible for LXD slowdowns.
There's an argument about whether LXD can/should through some kind of doctor command check for this, but it's out of scope.

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

@leehambley

Will get to this shortly, sorry - drowning in client work, thanks for ping
:)
Lee Hambley
http://lee.hambley.name/
+49 (0)<PHONE_NUMBER>
On 29 November 2017 at 21:23, Stéphane Graber<EMAIL_ADDRESS>wrote:

@leehambley https://github.com/leehambley
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lxc/lxd/pull/4058#issuecomment-347984716, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABKCACnI1YckzH-P9JZjHR_68xhADfdks5s7b0ygaJpZM4Qrz7F
.

"Signed-off-by: Firstname Lastname " line.

And you're fine if I sign-off my own work? In the workflows I know usually this'd be signed off by a pairing partner or the code reviewer ?

The Signed-off-by line is standard in kernel-style development workflows. You can find more information here https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html if you're interested.

Thanks for the hint @brauner -- as I said, internally it's used for code review, but a "signing-off" of rights similar to a CLA makes sense too.

Thanks too for your patience in accepting a trivial one-liner patch. It's a sign of good stewardship to help build good contributions and resisting the temptation to "just do it yourself", especially when it's so trivial.


Fix bugs in small molecule topology proposal

This fixes a major bug in the proposal of new small molecule Topology objects in which newly-constructed Topology objects contained chain objects that incorrectly pointed to the old Topology object because deep copy was used instead of purely constructive Topology generation via the public API.
I'm not actually sure how this could have worked before. I just ran into ParmEd stack traces when I tried to run the imidazole test in explicit solvent. Perhaps it only worked in vacuum, where there was only one residue?
We should really get these fixes into master as well, but I'm merging into hybrid-tests since I started with that branch to try to get protonation state sampling to work.

Someone else can back-port this into master. I can't figure out the branch madness.

I'm going to close this since I've cherry-picked on another branch to accomplish that task.

Which branch? And shouldn't these fixes also go into hybrid-tests?
Also, what did you cherry pick? The whole fix was essential.

Which branch?

small-molecule-bugfix, see #281

And shouldn't these fixes also go into hybrid-tests?

They will when #281 is merged and then master is merged into hybrid-tests. Otherwise small-molecule-bugfix can be merged into hybrid-tests directly, but since we're about to merge #281 that seems pointless.

Also, what did you cherry pick?

The commit fc2fbb7.  If there are fixes in another commit, then we'll have to include those.


StyleGuideBaseURL is broken for rubocop cops

The StyleGuideBaseURL was added here. This overwrites the one defined in rubocop.

Expected behavior
https://rubystyle.guide/#if-as-a-modifier
Actual behavior
https://rails.rubystyle.guide/#if-as-a-modifier
Steps to reproduce the problem
Run rubocop against the following code
def test
  if expected?
    return 'expected'
  end

  'not_expected'
end

rubocop (0.74.0)
rubocop-rails: (2.2.1)
Style/IfUnlessModifier: Favor modifier if usage when having a single-line body. Another good alternative is the usage of control flow &&/||. (https://rubystyle.guide#if-as-a-modifier)
rubocop (0.74.0)
rubocop-rails: (2.3.0)
Style/IfUnlessModifier: Favor modifier if usage when having a single-line body. Another good alternative is the usage of control flow &&/||. (https://rails.rubystyle.guide#if-as-a-modifier)
RuboCop version
0.74.0 (using Parser <IP_ADDRESS>, running on ruby 2.5.5 x86_64-darwin17)

Thanks for the feedback. A patch to RuboCop core is required to use StyleGuideBaseURL in RuboCop Rails.  I revert #88 with the new Rails Style Guide URL.

Thanks

RuboCop Rails 2.3.1 has been released to resolve this issue. Thank you.


does THORIUM.BAT have an option to automatically select from Windows version?

does THORIUM.BAT have an option to automatically select from a Windows version like this?
@ECHO OFF
for /f "tokens=4-5 delims=. " %%i in ('ver') do set VERSION=%%i.%%j
if "%version%" == "10.0" echo Windows 10+ & START "" "%cd%\thorium\thorium.exe" --user-data-dir="%~dp0%\USER_DATA" --allow-outdated-plugins --disable-logging --disable-breakpad --disable-encryption --disable-machine-id
if "%version%" == "6.2" echo Windows 8. & START "" "%cd%\thorium-legacy\thorium.exe" --user-data-dir="%~dp0%\USER_DATA" --allow-outdated-plugins --disable-logging --disable-breakpad --disable-encryption --disable-machine-id
if "%version%" == "6.1" echo Windows 7. & START "" "%cd%\thorium-legacy\thorium.exe" --user-data-dir="%~dp0%\USER_DATA" --allow-outdated-plugins --disable-logging --disable-breakpad --disable-encryption --disable-machine-id

https://stackoverflow.com/questions/13212033/get-windows-version-in-a-batch-file/13212116#13212116

The contents of current THORIUM.BAT:
START "" "%cd%\BIN\thorium.exe" --user-data-dir="%~dp0%\USER_DATA" --allow-outdated-plugins --disable-logging --disable-breakpad --disable-encryption --disable-machine-id

So no, it has no automatic detection.

Anyway, I'm not sure mixing user data between legacy and the newer one is safe or not.
Let the experts answer for that.


Make Unikube CLI as binary executable available

I am currently experimenting with PyInstaller https://pyinstaller.readthedocs.io/en/stable/usage.html which will compile a platform-specific binary (executable) for the CLI

PyInstaller creates a binary which takes multiple seconds (on Mac > 10 s) to unfold and execute. This is probably not feasible to roll out to users.
Next attempt: https://github.com/indygreg/PyOxidizer
This creates huge binaries which execute very fast (~ 500 ms)


[UF-261] jbpm console's RepositoryEditor view does not reflect the co…

Proposal fix for UF-261 . Please review.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

Sorry, this is not a fix. Actually this is not even a bug, you should use port and hostport. Would be good to have a PR from you that would apply for ports the same logic used by host and hostname.
Anyway thank you @abhijithumbe - hope to see a new PR from you soon!


z-index

home page z-indexes of .right_part and its flex box are not working

i just deleted all zindexes and added it only to menu


Use<EMAIL_ADDRESS>

Codecov Report

Merging #7 (4c43aae) into main (b6db33a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #7   +/-   ##
=======================================
  Coverage   78.18%   78.18%
=======================================
  Files           2        2
  Lines          55       55
=======================================
  Hits           43       43
  Misses         12       12

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b6db33a...4c43aae. Read the comment docs.


add support for providing custom certs for OLS and Custom ca for UI

OLS-385, support user provided certs for OLS
Allow Providing Custom Certificates for OLS to be used in the Server Side,
Allow providing a custom CA certificate for the Plugin proxy in case of self signed certs,
both features are independent and can be used separately, unless the OLS Certs are self signed, it will be a must to trust them with the Custom CA.
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #OLS-385, #OLS-650
Closes #OLS-385

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing
Perform Manual Testing:
To test this feature, please make use of the examples under hack/custom_certs directory.
it contains an example CR, TLS-Secret, and an Optional Script for generating your own certs
the CR, already setting the property spec.ols.useUserProvidedTLSCerts=true
and it has a valid value (for the example TLS Secret provided ) for the CA cert for the Console Proxy,
you can see that under the field spec.ols.deployment.console.caCertificate
please make sure you apply the secret before the CR, as it needed for the OLS pods to start.
the example assume you have a bam-secret available, for using different models please do the changes required for that.
how the verification done:
tested regular scenario, of automated certs (supported previously.
tested using the custom ols-certs
tested behavior when adding the CA
tested behavior when applying CR with missing certs, then applying the certs
all the above went as expected.

/test bundle-e2e-4-16

/close
This PR is replaced by https://github.com/openshift/lightspeed-operator/pull/411


Demo Import

https://shweooyin.com/
<EMAIL_ADDRESS>Password: KJNOINOIWBIUW
I can't import demo. Please hlep  I want to import main demo. Thank you
Please make sure you describe the issue and your use case.
It is helpful if you provide details of your environment:

Webserver name and version
PHP version and handler type (e.g. mod_php, suPHP, PHP-FPM)
Database server name and version
WordPress core version
W3 Total Cache plugin version

Please provide an error log if you can by adding these lines to your wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
WordPress puts the error log in /wp-content/debug.log
If you are also proposing a solution then please make sure to elaborate on why your solution is adequate.

You shouldn't post credential on your website here.

this is a public page, now internet has your admin password. Please, change your password.

All social icons not appear with buttons, what should I do?


Where to provide HF access tokens for evaluating private/gated models

Do I need to put the tokens somewhere in the config files, or in code ? I have no clue. I am trying to evaluate llama-7b, but I dont see any obvious way of supplying the tokens in the eval/eval.py file

You can try something like this in your command line: mcli create secret env HUGGING_FACE_HUB_TOKEN=***.  This will set a secret (hf token) for you: https://docs.mosaicml.com/projects/mcli/en/latest/resources/secrets/index.html

You canset the huggingface env var before you run your script, e.g: something along the lines of export HUGGING_FACE_HUB_TOKEN=***.  Also make sure to do set use_auth_token to True in the yaml like this example

It worked, thanks!


chrootenv fails with main: execvp(*argv, argv): No such file or directory

Describe the bug
When using direnv and pkgs.buildFHSUserEnv, it fails with
** (process:2145): ERROR **: 15:36:44.639: main: execvp(*argv, argv): No such file or directory

I traced the error to chrootenv
Steps To Reproduce
Run
/nix/store/x242zl40s779s96zr02qbidxdyxvqwk0-chrootenv/bin/chrootenv echo

Expected behavior
No error
Screenshots
** (process:2202): ERROR **: 15:38:30.010: main: execvp(*argv, argv): No such file or directory

Additional context
I think this is the code causing this error:
https://github.com/NixOS/nixpkgs/blob/492d2256f4ad1450da8861063e97af2d0c0f94b9/pkgs/build-support/build-fhs-userenv/chrootenv/src/chrootenv.c#L152
I use Nixpkgs unstable commit 72d8853228c9758820c39b8659415b6d89279493
I use this flake.nix with direnv as a test case
{
  inputs.nixpkgs.url = "nixpkgs";
  inputs.utils.url = "flake-utils";

  outputs = { self, nixpkgs, utils }:
    utils.lib.eachDefaultSystem (system:
      let
        pkgs = nixpkgs.legacyPackages.${system};
        fhs = pkgs.buildFHSUserEnv {
          name = "openwrt-env";
          targetPkgs = pkgs: with pkgs; [
            unzip
          ];
          multiPkgs = null;
          extraOutputsToInstall = [ "dev" ];
          profile = ''
            export hardeningDisable=all
          '';
          runScript = "bash";
        };
      in
      { devShells.default = fhs.env; }
    );
}

Notify maintainers

@yanalunaterra
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
- system: `"x86_64-linux"`
 - host os: `Linux 5.15.77, NixOS, 22.11 (Raccoon), 22.11.20221110.72d8853`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.0`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos````

@yanalunaterra After checking chrootenv's source code I realized the cause was that I had mount something on /host. Maybe chrootenv could create some flag file to make the detection a little more resilient? The current error message is a little cryptic to debug.

Yeah frankly we should drop chrootenv completely in favor of bubblewrap...


token too long,  it can't be passed to client

when token is too long, client always complain 'TypeError： Cannot read property 'data' of underfined.'
seems that it happens on JWTFactory only, JWTAuth::attempt works fine.
We have to fix it by following:(
Laravel:
$customClaims = ['mobile' => $mobile, 'password' => $password];
$payload = JWTFactory::make($customClaims);
$token = JWTAuth::encode($payload);
$token1 = substr($token,0,150 );
$token2 = substr($token,150);
Angularjs:
var token1 = response.data.token1;
var token2 = response.data.token2;
var tokenStr = token1+token2;
this.$auth.setToken(tokenStr);

Hi @AndrewLaBabies
From the error message you posted, 'TypeError： Cannot read property 'data' of underfined.' it seems that there's another issue..
Could you send over a screenshot of a postman or chrome response?

here we go!
Rgds,
Andrew

在 2016年4月20日，下午10:05，Jad Joubran<EMAIL_ADDRESS>写道：
Hi @AndrewLaBabies https://github.com/AndrewLaBabies
From the error message you posted, 'TypeError： Cannot read property 'data' of underfined.' it seems that there's another issue..
Could you send over a screenshot of a postman or chrome response?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/jadjoubran/laravel5-angular-material-starter/issues/268#issuecomment-212439714

screenshot not showing

sorry, sent by email just now.

okay great, please send me a screenshot from the network tab > response or preview sub-tab
Also do you have some custom code in your responseInterceptor?

I see nothing in network tab, sources tab can help?

If you can just console.log(response) and show me the response collapsed of course

come again

sorry my bad, console.log(response.data)

Feel free to re-open in case you have more info
Thanks 😄


Support for disabled-text-color, highlighted-text-color and selected-text-color

Hello!
I noticed TypographyKit overrides in UIButtonAdditions.swift whatever title colors we have defined in IB/when setting up the button in code. To that end I added support for three new properties that apply to UIButtons only: disabled-text-color, highlighted-text-color and selected-text-color. If defined, they will be applied, if not, we will fall back to the current behavior.
I also added support for applying these extra properties for NSAttributedStrings and updated the README.md. Would be nice to see this in the main repo, I don't believe it has any drawbacks.
Thanks!

Now that I think about it, I think it would be better if the title color would not be applied to all control states in UIButtonAdditions:
if let textColor = newValue.textColor {
    for controlState in controlStates {
        self.setTitleColor(textColor, for: controlState)
    }
}

By doing so we lose the UIButton's automatic adjustment of the title label based on the highlighted state. Is there a reason I am missing why it would be preferable to set the textColor for all states?

Thanks for flagging this - you're absolutely right this behavior won't work for all developers.
As part of that method above, the text color is only applied if one has been explicitly specified as part of a typography style so if a style doesn't contain a color then the button title color won't be affected. A complaint I've had in the past is where a color has been specified in config and then not applied to all button states.
To try and give the developer more control over this, I've added the ability to specify the means by which the typography style color is applied to a button title, see commit https://github.com/rwbutler/TypographyKit/commit/927a216a7e6b175f22d724b40917d6d21f0e6c1a. As part of this, I've added a property titleColorApplyMode on UIButton so that this can be specified on a per-button basis or globally using the TypographyKit.buttonTitleColorApplyMode property.
Hope this solves your problem - let me know!

Thanks, this works.
However, I think support for extended button properties would still be welcome, I would love to be able to decide the entire look of a component directly from the typography spec file.
Actually, to that end, I was thinking that support could be added for more properties which would provide a more rounded experience, such as

background-color, which can be applied to most UI components
placeholder-color, for UITextFields
tint-color, for UIButtons, UISegmentedControl, UIProgressView and UISwitch

Sure, one could argue that some of these are out of scope for TypographyKit, but  I can tell you I would use it. In fact I have a similar system which is based around User-Defined Runtime Attributes and it helped me tremendously for styling apps quickly.
If there is interest in adding this to TK I could take on some of these tasks and create some PRs.