add ctrl_state to MCMT gate

What should we add?
Add ctrl_state to multi-control multi-target gates

I think this would be a nice feature to add. Willing to help implement it if looking for help.

This is awesome, for any help, I'm here too!

Hi! I am interested in working on this issue. Can this be assigned to me? .I would like to make my first contribution to qiskit terra.

Yeah man, if @diemilio and @Marsmmz also agree, you can do this! And if during your task you find some issues, please tell us and we may help you😁

Sure! I had volunteered to take care of this a little while back cause I had the time, but I never got it assigned.

@diemilio Thanks for the opportunity. I have started working on the issue following the contribution guide.

Sorry for getting here late, I'll try my best to help!

@Marsmmz I have a question. Does MCMT controls need to be custom state?. Meaning should user given freedom to specify whether the state of control is 0 or 1 or mix like '01...' control state targeting q_k number of qubits. If yes what's best way to take that input from user, dictionary or list??

@Marsmmz I have a question. Does MCMT controls need to be custom state?. Meaning should user given freedom to specify whether the state of control is 0 or 1 or mix like '01...' control state targeting q_k number of qubits. If yes what's best way to take that input from user, dictionary or list??

I personally think users should have the freedom to specify the control state. Like if a 2-C-2-T gate is needed, users can specify which of '00', '01', '10', '11' they want to be the control state.  Perhaps taking a 01 binary string as input is enough?

@Marsmmz @diemilio @Dpbm I want feed back on this modified implementation of control function from source code of MCMT gate:
`[docs]    def control(self, num_ctrl_qubits=1, label=None, ctrl_state=None):
"""Return the controlled version of the MCMT circuit."""
mcmt_circuit = QuantumCircuit(self.num_ctrl_qubits + num_target_qubits)
if isinstance(ctrl_state, str):
if ctrl_state == '0':  # If '0', apply X gates to all control qubits (0-controlled)
for i in range(self.num_ctrl_qubits):
mcmt_circuit.x(i)
mcmt_circuit.append(MCMT(self.gate, self.num_ctrl_qubits + num_ctrl_qubits, self.num_target_qubits), mcmt_circuit.qubits)
for i in range(self.num_ctrl_qubits):
mcmt_circuit.x(i)
elif ctrl_state == '1':  # If '1', do nothing special to MCMT (1-controlled)
mcmt_circuit.append(MCMT(self.gate, self.num_ctrl_qubits + num_ctrl_qubits, self.num_target_qubits), mcmt_circuit.qubits)
else:  # If string of '0's and '1's, handle accordingly
for i in range(len(ctrl_state)):
if ctrl_state[i] == '0':
mcmt_circuit.x(i)
mcmt_circuit.append(MCMT(self.gate, self.num_ctrl_qubits + num_ctrl_qubits, self.num_target_qubits), mcmt_circuit.qubits)
for i in range(len(ctrl_state)):
if ctrl_state[i] == '0':
mcmt_circuit.x(i)
    return mcmt_circuit

`
In this version, if the ctrl_state is '0', X gates are applied to all the control qubits both before and after the MCMT gate, so we have a "0-controlled" MCMT. If ctrl_state is '1', the MCMT gate is implemented directly without any extra X gates, meaning it's a regular "1-controlled" MCMT. If ctrl_state is a string containing '0's and '1's, X gates are applied before and after the MCMT gate to the qubits corresponding to '0's in ctrl_state.
Also what additional test cases are needed apart from the defaulf ones already present for MCMT ? One that I could think is to check length of ctrl_state string matches the length of control qubits if ctrl_state is not None.

Close by #13150.
The new MCMTGate now has a ctrl_state parameter (and the original MCMT gate would be deprecated in Qiskit 2.0)


Create API key for Notify to use

Need to manually create a key for Notify only. Will be used as a github secret for MVP.

Likely 3 keys are required:

for Notify
for Route 53 health checks
for general usage (i.e. does not fall into any specific categories above)

Request
The API Key should be specified in HTTP Authorization header as a Bearer token, see: rfc6750 and  rfc7325:
   Authorization: Bearer <api key>

The API Key is base64 encoded (see: here)
Response
The WWW-Authenticate response header field must be used for authentication related error when a bearer token is used (see: here).
Error Codes
When a request fails, the respond contains an HTTP status code and includes one of the following error codes in the response:

invalid_request

The request is missing a required parameter, includes an unsupported parameter or parameter value, repeats the same parameter, uses more than one method for including an access token, or is otherwise malformed.
The resource server SHOULD respond with the HTTP 400 (Bad Request) status code.

invalid_token

The access token provided is expired, revoked, malformed, or invalid for other reasons.
The resource SHOULD respond with the HTTP 401 (Unauthorized) status code.

Furthermore, the error and error_description fields will be used to provide additional information about an error.
     HTTP/1.1 401 Unauthorized
     WWW-Authenticate: Bearer realm="UrlShortener",
                       error="invalid_token",
                       error_description="The api key is invalid"

If the request lacks any authentication information (e.g., the client was unaware that authentication is necessary or attempted using an unsupported authentication method), the resource server SHOULD NOT include an error code or other error information. For example:
     HTTP/1.1 401 Unauthorized
     WWW-Authenticate: Bearer realm="UrlShortener"

Notes

RFC 6750 forbids sending api key/access token in URI query parameter (see: here) due to security weakness , including the high likelihood of URL containing the api key/access token will be logged.
In terms of rotation requirements, in general, api key is not considered secure and should not be deployed in public environments. In controlled environments, manual rotation should be sufficient. The extra complexity required for rotating api key is not worth it. If/when there is a need to rotate api key in a scalable/automated manner, it is generally better to go with an access token implementation which is more secure and designed to work in public scalable environments. For a more elaborate discussion on this topic, see: here).

@cgye - the spec looks good to me.
Don't know if you thought about implementation yet, but Fastapi does provide some innate functionality for handling api tokens that you might want to take a look if you deem appropriate.

@cgye - the spec looks good to me. Don't know if you thought about implementation yet, but Fastapi does provide some innate functionality for handling api tokens that you might want to take a look if you deem appropriate.

Thanks for the link. Yes, this should make implementation easier :)

LGTM as well! I think the JWT route is interesting in terms of that requests after the initial authentication request have a time bound token. Having a fixed API key take away some complexity on the client side ex. reauthenticating after the JWT expires. In the past we just used a straight up fixed API key https://github.com/cds-snc/scan-websites/blob/main/api/api_gateway/routers/scans.py#L64-L75 but happy to try out the JWT route!

This has now been added.

Closed in #210, #212. #213


Alternate Approaches for the Julia code

Thanks for putting this together. I looked at the Julia code and keeping the calculation apples-to-apples (i.e. including the allocation of the mortality tables into an array), it could be up to ~7.3 faster than the current benchmark ("baseline"). In essence, the code is running fast enough that strategies to reduce the memory allocations are impactful in the average runtime. It's also perhaps more idiomatic Julia code (Python (numpy) encourages you to put everything into arrays first, that's not needed in Julia).
I also included an example showing using LifeContingencies.jl and Yields.jl to handle to decrements and discounting. This version is about 0.3x times as fast as the baseline, probably indicating that I could design some mutable structs into LifeContingencies to avoid needing to re-allocate across different sets of mortality rates.

benchmark
incl table allocation
mean time (absolute)
times faster

baseline
yes
1810μs
1x

mapreduce for
yes
325μs
5.6x

mapreduce for
no
325μs
7.7x

nested for loop
yes
247μs
7.3x

nested for loop
no
160μs
11.3x

LifeContigencies.jl + Yields.jl
yes
6854μs
0.3x

Here's the Pluto notebook:
https://gist.github.com/alecloudenback/e3dc7802a49b9d2f5e108cf322fb2e0b

Maybe it would be more general to say something like unit_claims = npx .* q and end the calculation right there? Here is my justification for the proposed change to the benchmark.
Having a unit_claims tensor will simplify any calculation that needs this sort of tensor down the line, so while it costs something up front, I view it as an investment in the speed of future calculations which are performed interactively and perhaps more often, as well as developer ergonomics.
Basically, I think we want all the information for every policy at every point in time, represented by tensors of shape

(policies,) for policy information like face amount, initial duration
(timesteps) for information like economic scenarios
(policies, timesteps) for things like unit claims

Without information for each policy at each point in time, I do not think we are providing the user with everything they could possibly want to know. It may cost memory/time to create such tensors, but I think it is necessary. Larger workloads can be calculated in batch or in parallel.
To recap:

Proposal to change benchmark to the creation of an array and not a reduction over an array
Design ideas for term life modeling software

Does this sound reasonable?

I think I had too strong an opinion on how to write the code.
I'm going to break up this benchmark into two benchmarks.

Benchmark now uses 8 threads and the nested for loop approach (it is fastest).
It does include table allocation. In the future maybe I will split the benchmark, in which case there will be separate benchmarks for

allocating the tables
doing the calculation


[ci skip] adding user @0xbe7a

Hi! This is the friendly automated conda-forge-webservice.
I've added user @0xbe7a as instructed in #3.
Merge this PR to add the user. Please do not rerender this PR or change it in any way. It has [ci skip] in the commit message to avoid pushing a new build and so the build configuration in the feedstock should not be changed.
Please contact conda-forge/core to have this PR merged, if the maintainer is unresponsive.
Fixes #3

LGTM! thanks again @0xbe7a


Clean up logUnknown() & exportPalImg() functions

Oops, I landed more commits just 2 minutes ago...if you can resolve the conflicts and update this branch I'll merge it.

ok should be resolved now


Added comma in README so that the example code is valid.

The code in the README wasn't valid and that's not a good thing.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks! This was already fixed here: https://github.com/prisma/prisma/pull/3341


Negative portal scissor size on 0.55 branch

On for-0.55.0/sync I periodically get errors about negative size from SetViewportAndScissor on map test-portals. This can be seen with r_checkGLErrors or the other GL debug callback thing, for example:
^3Warn: DEBUG_TYPE_ERROR: severity: high msg: GL_INVALID_VALUE error generated. Width and height must not be negative.

Some code to prevent negative values was removed on the branch by 948a3fea80d8105cbbacbc8e6d147912c277b179.

Looks like something wasn't merged properly because this was actually fixed in https://github.com/DaemonEngine/Daemon/commit/2ec4cb73e145633d3616f0d92781a7b9c24e8ffd, and the fix is there on master.

Fixed by #1306.


update include files

The publish is failed because these include files in this article are renamed in dependency repository.
We created this pull request to fix above issue and unblock docfx v3 migration.

NOTE
To make the OPS build pass for this Pull Request, please publish the master branch of this repository from OPS portal first and then re-open this Pull Request

Docs Build status updates of commit 9a943a3:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

tutorials/java.yml
:x:Error

Details

tutorials/java.yml

[Error] Cannot resolve 'java/tutorial/01-intro.md' relative to 'tutorials/java.yml'.
[Error] Cannot resolve 'java/tutorial/02-create-app.md' relative to 'tutorials/java.yml'.
[Error] Cannot resolve 'java/tutorial/03-register-app.md' relative to 'tutorials/java.yml'.
[Error] Cannot resolve 'java/tutorial/04-add-aad-auth.md' relative to 'tutorials/java.yml'.
[Error] Cannot resolve 'java/tutorial/05-add-ms-graph.md' relative to 'tutorials/java.yml'.
[Error] Cannot resolve 'java/tutorial/06-completed.md' relative to 'tutorials/java.yml'.

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

Closing this as I've merged the fix in #40. Not sure why OPS failed the build on this one, but the other went through :)


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_114eib99wf/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_114eib99wf/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /tmp/abs_114eib99wf/clone/recipe/meta.yaml:50: missing_description: The recipe is missing a description
Errors were found


Problem downloading profile's posts while unauthenticated

Your question here...
I noticed yesterday that one of the scripts I have to download posts while unauthenticated does not work anymore. Instead it says that the profile is not able to be found. It is a public profile and before the "outage" yesterday things were working normally, and I was able to download the public posts while unauthenticated.
Any Suggestions on what I may have to change to fix this issue?
I am using the most recent release 4.2.9.

Looks like its the same problem as in #381

I looked at that issue before I submitted and it seemed like the behavior exhibited was different but I see how it could be tied to it now that I look a little closer.
Here is the last block of the traceback in case it provides more context:
  return self._metadata('biography')   File "/usr/local/lib/python3.7/site-packages/instaloader/structures.py", line 541, in _metadata     self._obtain_metadata()   File "/usr/local/lib/python3.7/site-packages/instaloader/structures.py", line 532, in _obtain_metadata     raise ProfileNotExistsException('Profile {} does not exist.'.format(self.username)) from err instaloader.exceptions.ProfileNotExistsException: Profile PROFILE does not exist.

I'm getting the same issue with my script. Weirdly enough, it works in my local dev environment but not on my server.


Invalid parameter not satisfying : view

Is this a bug report?
YES
I am using facebook and google signin sdk into my project and after giving permission to facebook.com or google.com, app crashed and getting errors like -
Assertion failure in +[UIViewController _viewControllerForFullScreenPresentationFromView:]
and, Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: view'
There is no problem on sdk integration. I am using firebase too in my project.
Have you read the Contributing Guidelines?
YES
(Write your answer here.)
Environment
Environment:
OS:  macOS Sierra 10.12.6
Node:  v6.11.4
npm:  3.10.10
Watchman: 4.9.0
Xcode:  Xcode 9.2 (9C40b)
Android Studio:  3.0.1
Target Platform: iOS (11.2.1)

Any update?


Duplicate Datas

Im doing some joins. And when i search a common word, it tends to duplicate my display.
For example.
I have tags and genre. I have "Rock" tag in tags table and "Rock" genre in genre table. When i search "Rock", it displays the users, it duplicates my result.

@vireefdev you just need to add into  protected $searchable = []
protected $searchable = [
        'groupBy'=>['table.id'],
];


critters dependency issue

Critters seem to have a conflict with this package despite in here critters marked as ^0.0.10
Any ideas what the issue could be?

NPM log
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/critters
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/vite-ssg
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/critters
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/vite-ssg
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

@nandi95 have you added critters as dev dependency?


Add support for CLI tab completions

What does this PR do? Please describe:
This PR extends the CLI with support for tab completions. Initially, I tried using argcomplete, but it was slow and ran a Fairseq2 process each time I pressed tab, which was far from ideal.
I then discovered shtab, a package that generates shell tab completion scripts efficiently. According to its README:

What: Automatically generate shell tab completion scripts for Python CLI apps
Why: Speed & correctness. Alternatives like argcomplete and pyzshcomplete are slow and have side-effects
How: shtab processes an argparse.ArgumentParser object to generate a tab completion script for your shell

After implementing shtab, tab completion works beautifully. Here are some examples:
$ fairseq2 [TAB]
assets        llama         lm            mt            wav2vec2_asr

$ fairseq2 ll[TAB]
$ fairseq2 llama

It’s especially useful for things like presets. Instead of listing presets and copying them manually, you can now use tab completion:
$ fairseq2 lm [TAB]
chatbot               generate              instruction_finetune  preference_finetune
$ fairseq2 lm c[TAB]
$ fairseq2 lm chatbot

It also works with arguments:
$ fairseq2 lm chatbot --[TAB]
--cluster               --help                  --model                 --temperature           --top-p
--dtype                 --max-gen-len           --seed                  --tensor-parallel-size

Tab completions are specific to each shell and require the installation of corresponding scripts in the shell's directory.
Initially, I intended to extend the project by adding post-install scripts to automatically set up tab completion scripts (b63af9842eaba1521c00dd3f42ec3169b40a9f02). However, I discovered that this approach only worked with zip and tarball distributions, while fairseq2 uses wheel builds. As a result, I reverted that change.
Currently, you can enable tab completions manually by using --print-completions {bash|zsh|tcsh}. The output of this command can be saved to the shell's completion scripts directory for persistence or evaluated directly for the current session.
For example:
eval "$(fairseq2 --print-completion bash)"

Please note: each time the CLI interfaces are modified, the shell completion scripts need to be updated.
Does your PR introduce any breaking changes? If yes, please list them:
None.
Check list:

[X] Was the content of this PR discussed and approved via a GitHub issue? (no need for typos or documentation improvements)
[X] Did you read the contributor guideline?
[X] Did you make sure that your PR does only one thing instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests?
[X] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (no need for typos, documentation, or minor internal changes)

Most shells provide path completions by default. However, when using custom shell completions, this default behavior is overridden. To specify that an argument should use path completions, you need to use shtab.FILE for file completions and shtab.DIRECTORY for directory completions.
For example:
parser.add_argument(
    "input_dir",
    type=Path,
    help="Checkpoint directory",
).complete = shtab.DIRECTORY  # type: ignore[attr-defined]

parser.add_argument(
    "--config-file",
    dest="config_files",
    metavar="CONFIG_FILE",
    type=Path,
    nargs="*",
    help="YAML configuration file(s)",
).complete = shtab.FILE  # type: ignore[attr-defined]

This configuration ensures that input_dir will provide directory completions and --config-file will provide file completions.
I also had to ignore the type hints as I can't seem to find a better way to handle them.

Neat! Happy to merge this once ready. Any reason why it is draft at the moment?

Neat! Happy to merge this once ready. Any reason why it is draft at the moment?

I was waiting for further instructions on how to address the post-install issue. If we are not going to handle the shell completions setup automatically (i.e. post install code). Should I update some docs like INSTALL_FROM_SOURCE.md with instructions on how to setup and enable shell completions?

I was waiting for further instructions on how to address the post-install issue. If we are not going to handle the shell completions setup automatically (i.e. post install code). Should I update some docs like INSTALL_FROM_SOURCE.md with instructions on how to setup and enable shell completions?

Considering that our CLI commands are populated dynamically during runtime based on the packages installed in the Python environment, the safest would be to let users manually update their bashrc/zhrc once they have their environment fully set up. So adding some brief instructions in README (right after "Installing from Source") makes sense to me.

Should I add support for PowerShell and fish shell (if possible)?

I don't think they are necessary. PowerShell is mainly used on Windows. I haven't seen anyone using it on Linux/macOS. As long as we support bash and zsh, the rest is not really much relevant nowadays.

I have added a section in the Readme file on setting up shell completions in https://github.com/facebookresearch/fairseq2/pull/741/commits/4af2be410802a609e16ec79dd46a704efcf583cd. This PR should be ready for merging now.


Fix for issue - 933.

So we can incorporate your pull request, please share the following:

What issue are you addressing with this pull request? https://github.com/marklogic/java-client-api/issues/933
Are you modifying the correct branch? develop
Have you run unit tests? Yes
Version of MarkLogic Java Client API (see Readme.txt)
Version of MarkLogic Server (see admin gui on port 8001)
Java version (java -version)
OS and version
What Changed: The testcase "testPermissions_withTrx" was failing before. Now it is running successfully.

Fix for issue - 933. Added the merge code without the try catch block.


#Tracking text at the top nav bar in hour of code

@kiki-lee I am going to comment this out until we get the tracking pixel from HoC. I am going to reassign it to you until then and then just assign it back and I will add it in.

If you haven't heard from me by Friday afternoon, please ping me!

@ElizabethRiffle  Did Code.org send you a tracking pixel?


Add event when no more messages from the websocket

OBS might have crashed so it can't send a ServerStopping event.
For some reason OBS frequently crashes for me, so it would be nice to depend on another event to know it has crashed.
This event will be triggered when there will be no more messages in the websocket stream.
Which should indicate that the websocket has closed or crashed.

Thanks for this addition. In general this looks good but I prefer to handle a disconnect through the channels directly if possible.
What I mean is that most of the shutdown or disconnects result in some queues to finish and dropping senders and receivers internally that form a pipeline. So after a disconnect you'll get an error when trying to send a new request.
Similarly I would like to handle this for the events and a disconnect would result in the receivers not getting any events anymore (similar to reaching the end of an iterator). As the Client currently holds the sender, it will never be dropped and the receive streams never end.
Part of this motivation is that I plan to add automatic reconnect at some point in the future and then you would get multiple ServerStopped events without knowing which one means a real shutdown (the client side triggered one).
I'll experiment with this idea a bit and let you know. Nontheless this is a great find and the ability to detect a shutdown should definitely be added :+1:.

That sounds good, thanks for adding this so fast.
The ServerStopping event would still be nice since serverStoppped is not send in cases where OBS decides to crash.
And to solve the multiple ServerStopped events happening when you have added the auto-reconnecting.
Maybe the event should only be fired when you were actually connected and not while still trying to reconnect?
But then there should also be a way to know that you are actually connected again, in case someone is relying on this event :thinking:.

Both changes are merged now @715209, so you will get the ServerStopped event and then the event stream closes.
I have a few bits that I want to change before releasing the next version but you can use the latest changes with the following config until then:
[dependencies]
obws = { git = "https://github.com/dnaka91/obws.git" }

Thanks!


Corrosive Acid Upgrading

About the PR

Xenos can now apply corrosive acid onto entities that already had corrosive acid on them, as long as they are applying a stronger type of acid.
Weak acid can be replaced with normal or strong, normal can be replaced with strong.
Why / Balance

Drone or Sentinel applying weak corrosive acid can slow down entire xeno force, especially during hijack, and it feels like replacing/upgrading already applied acid was a missing feature.
Also, made a discord post here and feedback was positive.
Technical details

I also added a calculation on how much time should be applied when acid is replaced, so we won't end up in a situation where weak acid was 30 seconds away from melting an entity and it was replaced with strong acid that takes 60 seconds. This is the reason for keeping the extra data in CorrodingComponent.
Media

https://github.com/user-attachments/assets/e549fae8-7ec0-4a1f-acc6-4157c7118de2

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

add: Xenos can now apply stronger versions of corrosive acid onto already corroding structures.

I believe you should be able to apply all three types on the same entity, not replace, and their effects stack in CM13

Well, after last update we got corrosive acid reworked from 'delete after X seconds' into damage over time, and also different types of acid can now be applied onto the same entity, so this entire PR is redundant.


Delete the artifact renaming with -min as it has been added in opensearch repo

Signed-off-by: Xue Zhou<EMAIL_ADDRESS>Description
From issue #1094.
As the artifact name has been changed in PR 1251, we won't need the renaming here.
Issues Resolved
#1094
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #540 (e6795f2) into main (f12f416) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #540   +/-   ##
=======================================
  Coverage   69.62%   69.62%
=======================================
  Files          59       59
  Lines        1577     1577
=======================================
  Hits         1098     1098
  Misses        479      479

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 f12f416...e6795f2. Read the comment docs.


serverpod_cli, Windows 11 installation issue.

First of all I activated serverpod_cli
C:\Users\saifu>flutter pub global activate serverpod_cli Package serverpod_cli is currently active at version 0.9.5. Resolving dependencies... The package serverpod_cli is already activated at newest available version. To recompile executables, first run flutter pub global deactivate serverpod_cli. Installed executable serverpod. Warning: Executable "serverpod" runs "bin\serverpod_cli.dart", which was not found in serverpod_cli. Activated serverpod_cli 0.9.5.
And after that I was checking whether serverpod_cli activated or not so I ran this command
`C:\Users\saifu>serverpod
WARNING! Windows is not officially supported yet. Things may or may not work as expected.
Unhandled exception:
ProcessException: The system cannot find the file specified.
Command: which dart
#0      _ProcessImpl._start (dart:io-patch/process_patch.dart:401:33)
#1      Process.start (dart:io-patch/process_patch.dart:38:20)
#2      _runNonInteractiveProcess (dart:io-patch/process_patch.dart:578:18)
#3      Process.run (dart:io-patch/process_patch.dart:49:12)
#4      CommandLineTools.existsCommand (file:///C:/Users/saifu/AppData/Local/Pub/Cache/hosted/pub.dartlang.org/serverpod_cli-0.9.5/bin/create/command_line_tools.dart:22:32)
#5      main (file:///C:/Users/saifu/AppData/Local/Pub/Cache/hosted/pub.dartlang.org/serverpod_cli-0.9.5/bin/serverpod_cli.dart:43:31)
#6      _delayEntrypointInvocation. (dart:isolate-patch/isolate_patch.dart:295:32)
#7      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:192:12)
WARNING! Windows is not officially supported yet. Things may or may not work as expected.
Unhandled exception:
ProcessException: The system cannot find the file specified.
Command: which dart
#0      _ProcessImpl._start (dart:io-patch/process_patch.dart:401:33)
#1      Process.start (dart:io-patch/process_patch.dart:38:20)
#2      _runNonInteractiveProcess (dart:io-patch/process_patch.dart:578:18)
#3      Process.run (dart:io-patch/process_patch.dart:49:12)
#4      CommandLineTools.existsCommand (file:///C:/Users/saifu/AppData/Local/Pub/Cache/hosted/pub.dartlang.org/serverpod_cli-0.9.5/bin/create/command_line_tools.dart:22:32)
#5      main (file:///C:/Users/saifu/AppData/Local/Pub/Cache/hosted/pub.dartlang.org/serverpod_cli-0.9.5/bin/serverpod_cli.dart:43:31)
#6      _delayEntrypointInvocation. (dart:isolate-patch/isolate_patch.dart:295:32)
#7      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:192:12)
C:\Users\saifu>`

Windows is not yet supported. There is a pull request that should add Windows support, I'll look that over in the next few days!

any update? facing issue in windows 10.
may I know when will windows support be available?

@saiful00000 Can you please reinstall and check? The current version is 0.9.6. Please check this and update the ticket.


Fix missing import rename to identify permissions

When using<EMAIL_ADDRESS>with<EMAIL_ADDRESS>the process fails with the following error:
Error: Expected operator ':'. Instead found [object Object]
    at expectColonOperator (/Users/jpreynat/GitBook/gitbook-x/node_modules/firetree/src/parser/pipes/expectColonOperator.js:10:4)
    at /Users/jpreynat/GitBook/gitbook-x/node_modules/ramda/src/internal/_pipe.js:3:14
    at /Users/jpreynat/GitBook/gitbook-x/node_modules/ramda/src/internal/_pipe.js:3:27
    at /Users/jpreynat/GitBook/gitbook-x/node_modules/ramda/src/internal/_pipe.js:3:27
    at identifyAllowStatementChildren (/Users/jpreynat/GitBook/gitbook-x/node_modules/ramda/src/internal/_arity.js:11:19)
    at Object.identify (/Users/jpreynat/GitBook/gitbook-x/node_modules/firetree/src/parser/nodes/AllowStatement.js:40:10)
    at Object.identify (/Users/jpreynat/GitBook/gitbook-x/node_modules/firetree/src/parser/nodes/Statement.js:13:17)
    at /Users/jpreynat/GitBook/gitbook-x/node_modules/firetree/src/ast/identifyNode.js:10:21
    at /Users/jpreynat/GitBook/gitbook-x/node_modules/ramda/src/internal/_curryN.js:46:27
    at /Users/jpreynat/GitBook/gitbook-x/node_modules/ramda/src/internal/_arity.js:11:19

This PR fixes a small forgotten update of the import filename to identify allow statements with multiple permissions from https://github.com/brianneisler/firetree/pull/11

Great catch @jpreynat! Thanks for the PR!

You're most welcome @brianneisler 👌

@jpreynat just a heads up, I plan on writing a couple tests to cover this and then releasing a new version this weekend.

@brianneisler Cool, thanks for the heads up 👍
I tried to add some tests but couldn't figure out where was the right place and methods to call to do so.


No proximity routing

OctoDNS works well when it comes to creating record but there is no functionality that creates LoadBalancers and node pools. I haven't seen any information in the docs. I was wondering if you guys plan to add this in the future. This is important for because I use proxmity routing in CF.

Generally octoDNS's focus is on creating a unified set of functionality that is supported across all of it's providers to enable things like split authority. CloudFlare's proximity routing is pretty unique to CF and only has some conceptual overlap with Route53's. I haven't run across any other providers that support it.
So that's why it isn't already a supported thing, it's just not what octoDNS is/was focused on. That said there are provisions for providers to support one-off functionlity, which results in octoDNS being "only" a DNS config management, which imo it is still is the best option for :grin:
I'm not deeply familiar with CF's proximity routing stuff, but the configuration for it would likely look something likie:
foo:
  octodns:
    cloudflare:
      <whatever-goes-here...>
  type: A
  value: ...

The above is the way somethig CF specific would be configured. The details of what that would look like and how it would be implemented in the provider would be the hard part of implementing it. PRs are welcome, but outside of contracted development it's probably not something I'm likely to get to in the near future.


feat: resolve git conflicts with bitbucket-pipelines.yml when running yarn config-ci

References:
https://github.com/jonatanpedersen/git-json-merge
https://github.com/charpeni/merge-drivers-cli

Since the advent of cache versions https://bitbucket.org/blog/announcing-smarter-caches-bitbucket-pipelines


Enabled .NET 4.x for project

Overview
Added .NET 4.x support and added project dialog box to prompt users to switch.
Removed the compiler definitions for the reflection extensions.

So we are defintely agreed to drop 5.x support with this pr?

It's for the dev branch anyway, which is going to eventually be vNext. So I don't see why it should be a problem.


Darwin1

Mostly css fixes for pages
/ppc/digital-experience-platform/
/ppc/create-engaging-digital-experiences-at-scale/
please see commit message below
https://github.com/zesty-io/nextjs-website/issues/350

@darwin808 see change requests

@ardeay can you send again the change request thanks


General bugfixes

Continues the work of #253

[x] Fix multiple running of enable_charging
[x] Fix battery not found if not running in $PATH
[x] Fix not charging when disabeling limit
[x] Fixes validation of battery percentages
[x] Fix MagSafe charging colors
[x] Add more logging

I believe this fixes all the broken functions. Let me know if there is anything else I missed.

I really appreciate these bugfixes Chris!
Could you increment the version number in battery.sh? It is used to trigger updates.

Actually, don't worry about it. I'll do it manually.
Thank you very much for your work!


why the 2 extensions on AMO - detect feeds & list feeds?

Hello,
thanks for taking interesst.
Essentially both addons have a slightly differnt usercase and  permission set.

list-feeds, does nothing until a user clicks on the toolbar button and only required the activeTab permission  to work.
detect-feed, automatically injects a content-script in each visited page to find feeds and show the pageAction icon, when at least one is found. This requires the addional host permission <all_urls> , which is a very broad permission.

Since the <all_urls> permission ... is a very powerful one and some people might feel uncomfortable giving it to a rather minor addon, like a feed detection i thought giving them the power to choose would be a good idea.
Hope this explaination helps and that at least one of the addons fits your requirements.
Havea nice day. Later, maybe.

To be fair,  i could maybe merge the extensions ... and adding an optional permission for the user to grant ... to enable/disable the detection mechanism.
That might actually be a good idea.

i didn't pay close enough attn. when reading the descriptions - i get it now :)
regarding fingerprinting/privacy, detect feeds injects a script - assuming JS is enabled for the site, does this open a potential fingerprint avenue? there's nothing in the manifest about 'web accessible resources' so i wasn't sure

All good, i actually have to thank you for providing the idea of merging the addons.
Less code maintainace on my side.
Regarding the content script injection. The injected script is wrapped inside an anonymous function, and should not be directly  detectable. Double so, since it doesn't make any changes, but only reads (aka. parses)  some values and passes them onto the toolbar/pageAction  popup.
I am not 100% sure what the  ... web accessible resources ...  are for, but if you had to guess, i would say ... to connect/request external  assest or websites.  That is something this addon simply doesn't need.  No external site is requested / used in any way.
Everything happens locally.
Hope that answers your questions.

i believe (not 100% sure) web accessible resources are resources which an extension makes available to the page/server - i don't think it's about pulling remote resources
descrip. from 'pants' of the arkenfox user.js with regard to how they are listed in the manifest: "An array of strings specifying the paths of packaged resources that are expected to be usable in the context of a web page"
the reason i asked about it is because the use of them can, but not necessarily, leak the extension UUID which can aid in fingerprinting the browser - here's an issue i brought up if you're interested

You are right. From what i understand from the issue and the official mdn resource
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/web_accessible_resources
i would say, that list-feeds and none of my other addons expose their internal urls.
Simple reason being,  that the content-script injection is only/mostly done via tabs.executeScript (ref. https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/executeScript)
or via the manifest.json, via content-script.
I try to not use anything that isn't absolutely required, so no other resouces are injected, which might expose usable information for fingerprinting.
At least so long as there is no implementation bug with mozillas Web-Extension implementation that i am not aware of.

I try to not use anything that isn't absolutely required ...

i like your ethic - i always check extensions the best i can before installing, especially since the WE API change which seemed to bring all the unethical malware/adware/tracking/fingerprinting devs from Google Chrome to Firefox

i always check extensions the best i can before installing ...
A very wise decision.

... the WE API change ...  seemed to bring all the unethical malware/adware/tracking/fingerprinting devs from Google Chrome to Firefox
Yeah, the AMO review process isn't very strict, maybe in the future Mozilla will improve this, but i wouldn't hold my breath.

Anyway, If you have any further questions about this or any other addon of mine  feel free to open an issue, and i'll try to answer to the best of my abilites.


Missing event field names in post v14 metadata

After this PR (https://github.com/paritytech/substrate/pull/9993) textual description of event fields was removed from description field.
Eg. for balance Transfer event ot was changed from Transfer succeeded. \[from, to, value\] to Transfer succeeded.
This is really nowhere to be found in metadata that only returns data types like AccountId32,AccountId32,u128.
This change seems to broke many apis (like  https://polkascan.io/polkadot/event/6202002-3, https://polkascan.io/polkadot/event/8273065-21 ).
I understand the benefit of changing description into keys, but at the same time neither System.Events nor Metadata isn't carrying this information anymore. Is there any new, undocumented way to retrieve this keys? (polkadotjs isn't returning this data either).
And if not, would it be possible to revert the descriptions to how they were?
Maybe @Wizdave97 ? Since you're the one who changed it?

As you see here: https://github.com/paritytech/substrate/pull/9896#issue-1010768480
You can still access the data. This was removed by intention.
To know how to access this data with polkadotjs, you need to read the docs there or open an issue, but not in Substrate.

@bkchr I'm not using polkadotjs.  That was just an example of the code that is also not returning the fields.
I'm using pure ws storage requests to read the data. The issue you've linked does not explain in any way how to retrieve this value from node api. And obviously it is substrate - I even linked a PR in where this particular lines were removed.
https://github.com/paritytech/substrate/blob/master/frame/balances/src/lib.rs#L439 -> that's precisely an event substrate is producing.
And both state_getStorage SystemEvents and getMetadata are Substrate endpoints, this information is missing from both.
Would you be able to tell me then from where should I take this information using Substrate apis?

Why should the node api return this kind of information?
The node isn't interested in this data.
As the linked issue describes, the data is available in the scale-info metadata. See here: https://docs.rs/scale-info/latest/scale_info/struct.Field.html#method.name


Show Remaining Levels and XP in skill calculator

Closes #9260

I am open to other implementations

@Serpa88 What about adding a button that sorts the list for least actions or most xp per item made or done?

This also closes #4816 and supersedes #5789

Are those editable? If they're not, they're styled as if they are, that might be confusing.

They are not editable. I thought the same but I also wanted them to look similar as well, so I am not sure about it.

Make them regular labels I guess

Also, you're not just going to leave "Remaining Experie..." right?

Well I don't think regular labels is right either though

You could try adding a rectangular border to the label, this way, it would have the same shape as the text fields above, but not the same border or background, try it out

@Serpa88 What about adding a button that sorts the list for least actions or most xp from 1 item made or done?

That would have to be in another pull request

Just set the fields to disabled and make them grey.
I also don't think this should be implemented, but its spamming Discord.


ActiveField json parse error

What steps will reproduce the problem?

Load data from DB via ActiveRecord Model. One of the fields has JSON type, so starting from 2.0.14 it is converted to Array while populating
Use this model while building yii\widgets\ActiveForm. For example,

<?php
$form = ActiveForm::begin();
echo $form->field($model, 'data')->textarea();
ActiveForm::end();
?>

What is the expected result?
Form should be loaded and json field edited as string.
!Or make new method for json editing in Active field (see https://www.yiiframework.com/doc/api/2.0/yii-widgets-activefield)
What do you get instead?
yii\base\ErrorException: htmlspecialchars() expects parameter 1 to be string, array given in /var/www/dev/vendor/yiisoft/yii2/helpers/BaseHtml.php:111
Stack trace:
#0 [internal function]: yii\base\ErrorHandler->handleError(2, 'htmlspecialchar...', '/var/www/dev-ge...', 111, Array)
#1 /var/www/dev/vendor/yiisoft/yii2/helpers/BaseHtml.php(111): htmlspecialchars(Array, 11, 'UTF-8', true)
#2 /var/www/dev/vendor/yiisoft/yii2/helpers/BaseHtml.php(699): yii\helpers\BaseHtml::encode(Array, true)
#3 /var/www/dev/vendor/yiisoft/yii2/helpers/BaseHtml.php(1506): yii\helpers\BaseHtml::textarea('Menu[data]', Array, Array)
#4 /var/www/dev/vendor/yiisoft/yii2/widgets/ActiveField.php(513): yii\helpers\BaseHtml::activeTextarea(Object(app\modules\admin\models\Menu), 'data', Array)

Additional info

Q
A

Yii version
<IP_ADDRESS>

PHP version
7.0.28

Operating system
CentOS

I think the value formatting can solve your problem:
echo $form->field($model, 'data', [
    'inputOptions' => [
        'value' => is_array($model->data) ? Json::encode($model->data) : $model->data
    ]
])->textarea();

@berosoboy Thanks for decision, it has 1 problem:
After i save my form it saves this filed like that "{\"icon\":\"fa fa-circle-o\"}" and Model cant longer convert it to array.

@finnan444 Understood. In that case you need to decode the json field before saving to database (you can do this after $model->load())
...
if ($model->load(Yii::$app->request->post()) {
    $model->data = Json::decode($model->data);
    ...
}

Maybe these steps can be automated by framework.

@finnan444  Probably you have Json::encode() somewhere in you code. Since 2.0.14 the framework encodes json sql fields, so it isn't necessary to convert it. If you want to preserve old behavior (before 2.0.14) check https://github.com/yiisoft/yii2/issues/15716#issuecomment-368143206

Guys, i found where Json is encoded - look at the Class yii\db\pgsql\JsonExpressionBuilder
it has build method, see line 45:
$placeholder = $this->queryBuilder->bindParam(Json::encode($value), $params);

so as our form sends correct Json string via post, in JsonExpressionBuilder it is encoded again

@schmasterz I cant disable using yii\db\pgsql\JsonExpressionBuilder, because it is called in yiisoft/yii2/db/ActiveRecord::updateAll() and C:/PHPStormProjects/Genie-dev/vendor/yiisoft/yii2/db/QueryBuilder->update() methods!

@finnan444 , decoding the data before saving solved your problem?

@schmasterz if i disable this class in config like in #15716, it affects the whole project - so in other components JSON is decoded correctly while been populated.
Dont try to solve my specific issue. Look wider, is there a need to check strings in yii\db\pgsql\JsonExpressionBuilder and if they are already valid Json and there is no need to encode them again

This behavior is documented: https://github.com/yiisoft/yii2/blob/master/docs/guide/db-active-record.md#json-in-mysql-and-postgresql
I think we need to be aware of it before saving the ActiveRecord.


Add summary to Alertmanager rules where missing

Added summary to Alertmanager rules where missing. The summary is based off the description label, but contains less information - ideal for headers when sending notifications to Slack or HipChat.

Could you add these to the alert definitions in contrib/kube-prometheus/assets/prometheus/rules and the run make generate from the contrib/kube-prometheus/ directory? Otherwise lgtm!

To update the helm charts you should run this script  and follow this steps

lgtm on green


Changing Decide() to build a DecisionTree as a response

Fix: #31
Change Decide() signiture to:
func  (config) Decide(profile) *Decision

where Decision is a tree maintaining all decisions where the profile failed to meet the specification of config:
type Decision struct {
	children map[string]*Decision
	reasons  []string
	result   int
}

Schematic example:
Req-->Headers--> Content-Length --> "Out of range"
-->QueryString--> KnownKey 'name' --> Digits -->  "Out of range"
--> Unicodes -->  "Out of range"
The new code supports

Accumulating all errors for indicating to the user via log, and
Calculating integer result (currently a simple summation of errors, but can be weighted).

All Decide() methods of all objects were modified  - instead of building a string that concatenates all issues found (as done for the alpha) we build a tree of issues  - each node in the tree includes a score of that node and all its children, a map of children with score > 0 and a map of issues found in this node. A tree node is created only if one or more issues were detected. Hence in a normal case, where no issues found, no nodes are ever created.
The new implementation also greatly simplifies the code in each Decide() method by using two functions: DecideChild() and DecideInner() that implement common code required by all Decide() implementations.


fix: Change location of api spec and remove fields from App

Motivation
No JIRA
What
Change the location of api spec and removing disabled and disabledMessage fields from App level
Why
Adhering to Go folder structure by moving swagger spec file to api folder.
Removing disabled and disabledMessage fields due to change in UI.
Verification Steps
Not possible to verify the changes until they are in GitHub :-(

Coverage decreased (-10.5%) to 58.427% when pulling a5e7333d020bd7a0ce458cc3db9dfaa96ca0fdf6 on davidffrench:update_swagger_docs into ea77daef897701037803f37228cac267932736f0 on aerogear:master.

Coverage decreased (-10.5%) to 58.427% when pulling b141f9ccb7dc3d901e98c4c600153ee3dca7acca on davidffrench:update_swagger_docs into ea77daef897701037803f37228cac267932736f0 on aerogear:master.

Commit message isn't adhering to our new standard:
fix(scope): Change location of api spec and remove fields from App (AEROGEAR-XXXX)

I have found the first problem with the commit message format. If there is no JIRA associated. @laurafitzgerald What is your opinion on always having a JIRA for every change?

Commit message isn't adhering to our new standard:
fix(scope): Change location of api spec and remove fields from App (AEROGEAR-XXXX)

I have found the first problem with the commit message format. If there is no JIRA associated. @laurafitzgerald What is your opinion on always having a JIRA for every change?

This is also relevant to @austincunningham as he is working on the CircleCI regex rule for this.

(AEROGEAR-XXXX) will satisfy the rule at present

Modified now. I change it to (none) first but I didn't like it that way.


don't re-use connection objects on windows and mac either

This fixes ssl_server cluster tests failing on mac & windows.

http://jenkins01.arangodb.biz:8080/view/Mac/job/arangodb-ANY-mac-matrix/580/
http://jenkins01.arangodb.biz:8080/view/Windows/job/arangodb-ANY-windows-matrix/760/

tests mostly green.

Don't need backporting since no failures like this were observer for 3.5- branches (which doesn't use Fuerte here).


Got error when resizing columns

When we use the plugin to be able to resize columns in datatables we get a js error, but column resize succesfully.

Can you check whether v1.7.1 fixes this?


Support setCustomParameters() so Auth URI params can be set (e.g. 'prompt': 'select_account')

Upon logging the user out, I'd like to force an account selection prompt if the user has multiple Google accounts.  However, calling af.auth.login() seems to cache the selection and future logins use that selection without giving the user a chance to select a different account.
New versions of the Firebase API support this.  I suspect AngularFire will need to update the dependency.
See http://stackoverflow.com/questions/35778693/how-to-force-google-oauth-popup-in-firebase-when-user-already-authenticated-prev/40551683#40551683
The way I suggest it might be implemented is to add an optional parameters field to the authConfig that can be set to any of the OpenIdConnect parameters.
https://developers.google.com/identity/protocols/OpenIDConnect#prompt

This can be closed thanks to the new release.

AngularFire2 no longer provides these auth methods. If this problem still persists open a question on Stackoverflow for Firebase Authentication.


Image Not Getting Copied for Arista 7010T switches!

Hi Kirk,
When i use the netmiko_file_transfer module, I am getting the following error:
OSError: Search pattern never detected in send_command_expect: [\$#]
Nornir Code:
nr_arista = nr.filter(F(hostname__in=device_urlArray))
nornir_set_creds(nr_arista ,fabricList,device_urlArray)
source_file = project_path + "/media/" + BinFile
result = nr_arista.run(
task=netmiko_file_transfer,
source_file=source_file,
dest_file=BinFile,
direction='put',
num_workers=len(NodeSwitch_tmp),
)

I need the full stack trace.
Also really should re-submit this issue against the nornir_netmiko repository and not here.
Regards, Kirk

Please unsubscribe me fro this email thread. Thank you
Best,
Walter Luna
On Mar 18, 2021, at 5:57 PM, Kirk Byers @.***> wrote:

I need the full stack trace.
Also really should re-submit this issue against the nornir_netmiko repository and not here.
Regards, Kirk
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/ktbyers/pynet/issues/32#issuecomment-802426664, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACHMPGMKTTTNBOKWX4VDIBDTEKOP5ANCNFSM4ZNSS6PQ.

@Ziggy23810 I have no idea how you are subscribed to these message. You will need to look into your GitHub notification settings.
Regards, Kirk

Here you go :
2021-03-18 15:49:43,938: WARNING/ForkPoolWorker-7] Traceback (most recent call last):
  File "/home/sgang31/.venvs3/netadc3/lib64/python3.6/site-packages/nornir/core/task.py", line 67, in start
    r = self.task(self, **self.params)
  File "/home/sgang31/.venvs3/netadc3/lib64/python3.6/site-packages/nornir/plugins/tasks/networking/netmiko_file_transfer.py", line 28, in netmiko_file_transfer
    net_connect, source_file=source_file, dest_file=dest_file, **kwargs
  File "/home/sgang31/.venvs3/netadc3/lib64/python3.6/site-packages/netmiko/scp_functions.py", line 78, in file_transfer
    if scp_transfer.check_file_exists():
  File "/home/sgang31/.venvs3/netadc3/lib64/python3.6/site-packages/netmiko/arista/arista.py", line 82, in check_file_exists
    return self._check_file_exists_unix(remote_cmd=remote_cmd)
  File "/home/sgang31/.venvs3/netadc3/lib64/python3.6/site-packages/netmiko/scp_handler.py", line 188, in _check_file_exists_unix
    self.ssh_ctl_chan._enter_shell()
  File "/home/sgang31/.venvs3/netadc3/lib64/python3.6/site-packages/netmiko/arista/arista.py", line 39, in _enter_shell
    return self.send_command("bash", expect_string=r"[\$#]")
  File "/home/sgang31/.venvs3/netadc3/lib64/python3.6/site-packages/netmiko/base_connection.py", line 1337, in send_command
    search_pattern
OSError: Search pattern never detected in send_command_expect: [\$#]


HBASE-25922 - Disabled sanity checks ignored on snapshot restore (#4533)

Signed-off-by: Duo Zhang<EMAIL_ADDRESS>Signed-off-by: Bryan Beaudreault<EMAIL_ADDRESS>Conflicts:
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 49s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.4 Compile Tests _

+1 :green_heart:
mvninstall
2m  9s
branch-2.4 passed

+1 :green_heart:
compile
2m 14s
branch-2.4 passed

+1 :green_heart:
checkstyle
0m 28s
branch-2.4 passed

+1 :green_heart:
spotless
0m 38s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 13s
branch-2.4 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 54s
the patch passed

+1 :green_heart:
compile
2m  5s
the patch passed

+1 :green_heart:
javac
2m  5s
the patch passed

+1 :green_heart:
checkstyle
0m 27s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
14m 32s
Patch does not cause any errors with Hadoop 2.10.2 or 3.1.4 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 35s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 16s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m  9s
The patch does not generate ASF License warnings.

33m 27s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4734/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4734

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 0a5702186c2e 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / c8969e1859

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
65 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4734/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

This is probably safe, but i'll merge once CI finishes since it's already running.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  5s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+1 :green_heart:
mvninstall
2m 15s
branch-2.4 passed

+1 :green_heart:
compile
0m 37s
branch-2.4 passed

+1 :green_heart:
shadedjars
3m 56s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 26s
branch-2.4 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m  2s
the patch passed

+1 :green_heart:
compile
0m 36s
the patch passed

+1 :green_heart:
javac
0m 36s
the patch passed

+1 :green_heart:
shadedjars
3m 55s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 23s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
195m 45s
hbase-server in the patch passed.

213m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4734/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4734

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 17cb4b22e459 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / c8969e1859

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4734/1/testReport/

Max. process+thread count
2444 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4734/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  7s
Docker mode activated.

-0 :warning:
yetus
0m  8s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+1 :green_heart:
mvninstall
3m 46s
branch-2.4 passed

+1 :green_heart:
compile
0m 55s
branch-2.4 passed

+1 :green_heart:
shadedjars
6m  6s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 33s
branch-2.4 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 13s
the patch passed

+1 :green_heart:
compile
0m 59s
the patch passed

+1 :green_heart:
javac
0m 59s
the patch passed

+1 :green_heart:
shadedjars
5m 54s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 31s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
191m 16s
hbase-server in the patch passed.

217m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4734/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4734

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 76edb30c9c64 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / c8969e1859

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4734/1/testReport/

Max. process+thread count
2728 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4734/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Long-range weapon sights of other modules are invalid

When using a bow or crossbow in the over-the-shoulder perspective (I did not try the trident), the crosshair will adapt and aim, but it does not have such an effect on the ranged weapons of other mods.
For example: MrCrayfish's gun
version : 1.16.5
Forge : 36.1.25
mod : ShoulderSurfing-2.0.3.jar
Oh, I just found out that there is a new version. Is this resolved in the new version? I'll try it later.

This should not be resolved in newer versions but it should adapt the crosshair when a modded weapon uses certain properties (pull, throwing, charged). I could add a list as a config option for items that you want the adaptive crosshair on.


binutils: 2.31.1 -> 2.32

Motivation for this change
Submitting so folks can test or discuss :).
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Closing in favor of #55485 , since they appear largely the same (modulo specifying autoconfHook version I believe they're identical) and we don't need two :D.


Mm 37049 cta cloud

Summary
Change feature discovery so that cloud users are prompted to "Subscribe now" and see the upgrade modal.
Ticket Link
https://mattermost.atlassian.net/browse/MM-37049
Related Pull Requests
None
Screenshots
In the screenshot, I didn't locally have all the CWS settings set, so the upgrade options aren't right in the modal. But they should be right in test environments.
https://user-images.githubusercontent.com/13738432/128938819-5b01d3b0-ba3e-4ffc-aaca-45331dbeff46.mp4
Release Note
Launch the cloud upgrade modal in feature discovery if subscription is cloud.

Hello @neallred,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

/update-branch

Could the test server creation be failing due to some failing tests?

"Note locally I didn't have all the CWS settings set, so the upgrade options aren't right in the modal. But they should be right in test environments."
@neallred to mock the CWS calls you can set ENABLE_MOCK_CWS=true when starting the server and enterprise repos. If there're particular calls not yet mocked out, we can add them to the mock code.

Great work on adding the changes. All the code looks good. Just a small thing, with these changes, this line here
https://github.com/mattermost/mattermost-webapp/blob/e63a0ac2c5ea59b284854b97a2af67cca914fee0/components/admin_console/feature_discovery/feature_discovery.tsx#L114
would not be coherent if we have cloud license. @marianunez I think we would need to change the wording in that disclaimer.
Hello @marianunez , how about this?

Ok @stevemudie , it took a while, but this one should be testable now! Steps in https://mattermost.atlassian.net/browse/MM-37049

Great work on adding the changes. All the code looks good. Just a small thing, with these changes, this line here
https://github.com/mattermost/mattermost-webapp/blob/e63a0ac2c5ea59b284854b97a2af67cca914fee0/components/admin_console/feature_discovery/feature_discovery.tsx#L114
would not be coherent if we have cloud license. @marianunez I think we would need to change the wording in that disclaimer.

Missed your message before @AGMETEOR. Agreed this text here does not apply to cloud upgrade. @nathanaelhoun can we just hide that text under the buttons for cloud? Any other disclaimers or terms are shown in the actual upgrade modal so I don't see the need to add anything there

Looks like there's at least 2 Nathaniels contributing to mattermost :grin:

Looks like there's at least 2 Nathan{a,i}els contributing to Mattermost 😁

Oops apologies on incorrect ping here 🙈


Display Device Info in Settings

Users can view device, ios version, Folio version etc. for troubleshooting

@rachelsko first issue wooooooot

@lucaderosso this is an interesting issue - before Intercom, the "Support" button would generate an email to Artsy that included a ton of information about the device, iOS version, disk space, artwork count, etc. and it was quite useful (not that Intercom isn't).
Would it make sense to show the user this sort of stuff?

What do you mean by showing it to the user? This is information more valuable to us, is there a way to start a conversation in intercom by sending us all this information. It's quite surprising that they don't offer this option given that I'm pretty sure their product as well has the same needs.

@lucaderosso starting to think this might make sense as an auto-generated report to Artsy... something like Apple's 'Send to Developers' option after crashes


Make doc_type optional parameter to .index() operation.

Make doc_type an optional parameter
Description
Allows the user to define the _type parameter of the document when performing the .index() operation.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Are there other places where doc type is still required? I also understand we preserve it for 1.x compatibility, should be marked as deprecated somehow.

Please sign DCO
Update CHANGELOG

Hello @lschanner-tenchi, Please sign DCO and Update CHANGELOG.

I believe this was an attempt at compatibility at ES/older versions. Closing. Please feel free to reopen with issues above addressed.


cask/uninstall: skip quit/signal directives when upgrading or reinstalling

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

To ensure that a fresh copy of an application is installed correctly, and that the previous copy is removed entirely, when brew upgrade or brew reinstall is called, we first uninstall the prior version of the application.
This can have a side-effect of being destructive in that a running application can be closed using SIGTERM (or similar commands) in a forceful manner without an user confirmation. This is the reasonably expected behaviour when running brew uninstall as the user is explicitly asking for the application to be removed.
However, in cases where the user is running brew upgrade it may not be anticipated that the application will be forcefully terminated, potentially resulting in the loss of unsaved work.

@p-linnane
There's definitely some other cases like google-drive that upgrade a bit cleaner when they are quit, however it requires you to manually reopen to start it up again.
As a user, I think it's worse that you lose progress in an online form you're filling out in your browser, than having to close and reopen after a few minutes.
But it's not a clear-cut resolution either way.

Great work @bevanjkay. This makes a lot of sense to me. I wonder if there's any other stanzas this may apply to? I've personally hit a situation in the past where I wanted this to apply to a script but it may need to be opt-in for that case.

When I checked list, quit and signal were the two that made most sense to me to apply globally.
If we allowed a preference to skip additional on upgrade/reinstall I expect it would need to be on a per command level, not an environment variable. Otherwise maybe changing the uninstall stanza DSL, to codify directives as being skipping on uninstall/reinstall.
I'm not sure it is worth the extra effort at this stage, unless there are currently specific examples where this is problematic.

In the case of uninstall scripts often being overzealous (vendors often clear settings etc... because they are designed for an actual uninstall/cleanup), we usually skip them and use our own stanzas to replicate.
We have an issue open somewhere to allow these to be run from zap as they're currently broken. Hopefully can get this off the back burner soon.

There's definitely some other cases like google-drive that upgrade a bit cleaner when they are quit, however it requires you to manually reopen to start it up again.

I think these should opt-in to something like uninstall: ..., on_upgrade: true stanza or something.


Allow setting golang executable from environment variable

This will help us to easily use different golang versions in the Makefile. Usually required to test out dependency upgrades.
Eg:
GO=go1.17 make run

PTAL @vbnrh @umangachapagain
It's a small QOL commit.


adding fixes so transducer can work again

Merges:  https://github.com/CUNY-CL/yoyodyne/pull/233 https://github.com/CUNY-CL/yoyodyne/pull/197
Fixes: https://github.com/CUNY-CL/yoyodyne/issues/192 https://github.com/CUNY-CL/yoyodyne/issues/191
Dependent on: https://github.com/CUNY-CL/maxwell/pull/17
Summary: I fixed maxwell so TQDM isn't a property of the SED parameters anymore, this allows pickling of the expert module again and thus allows multigpu training across the transducer.
In progress I changed how the expert module initializes so that it just copies the index vocabulary from the dataloader that's passed to it.  So now you just need to pass an index to the action vocabulary and everything is managed in the backend. This allows free initialization of expert modules from checkpoints and thus skips epochs of em when resuming from a checkpointing. (I  just do the same thing we do with indexes in which you write the sed parameters to the experiment directory and load it when initializing the model.)
I also added new flags so that you can just skip em training for the expert. This is for an upcoming change in which the transducer is no longer dependent on having an oracle function. (I've found through training that the SED actually doesn't add that much to training.) It also allows the creation of dummy experts that just hold the action vocabulary. Added error checks to prevent unsafe use. Feel free to point out more.
I also moved adams changes from  https://github.com/CUNY-CL/yoyodyne/pull/233 into the trainer so that there's no weird attribute managing going on in the init anymore. ( Turns out that checkpointing pickles that kwargs dict, so simply adding the action vocabulary was creating too large an embedding space.)
I ran experiments over the Polish data and was able to write to predictions fairly easily. Only major issue is that we're wasting some parameters on creating target vocabulary embeddings that will never be used. But that's a low bar on the efficiency stack.

Thanks for these changes + cleaning this stuff up!!

Summary: I fixed maxwell so TQDM isn't a property of the SED parameters anymore, this allows pickling of the expert module again and thus allows multigpu training across the transducer.

Awesome!

In progress I changed how the expert module initializes so that it just copies the index vocabulary from the dataloader that's passed to it. So now you just need to pass an index to the action vocabulary and everything is managed in the backend. This allows free initialization of expert modules from checkpoints and thus skips epochs of em when resuming from a checkpointing. (I just do the same thing we do with indexes in which you write the sed parameters to the experiment directory and load it when initializing the model.)

"is managed in the backend" means in the expert.py code? 2. Are the expert modules deterministic given a dataset? For the index, this is the case and it will be created and written every time you run an experiment I think right? I believe we only load it when it is explicitly asked for in the args (e.g. for inference), though correct me if i'm wrong. So here, I guess if we default to epochs > 0,  then we just need to put something in the README that you can re-use the expert by setting epochs = 0 (and then maybe we raise an error if there is not expert where we expect it to be in this case.).

I also moved adams changes from https://github.com/CUNY-CL/yoyodyne/pull/233 into the trainer so that there's no weird attribute managing going on in the init anymore. ( Turns out that checkpointing pickles that kwargs dict, so simply adding the action vocabulary was creating too large an embedding space.)

Nice, thanks. Yeah I was worried about that but in a big rush trying to make a fix when I made the PR and then promplty disappeared. It looks like you cleaned up some naming, etc as well, so is it safe to assume that you have valdated that those are the correct changes, or should I do more testing?

I ran experiments over the Polish data and was able to write to predictions fairly easily. Only major issue is that we're wasting some parameters on creating target vocabulary embeddings that will never be used. But that's a low bar on the efficiency stack.

How was the accuracy w/ and w/out features?

1. "is managed in the backend" means in the expert.py code? 2. Are the expert modules deterministic given a dataset? For the index, this is the case and it will be created and written every time you run an experiment I think right? I believe we only load it when it is explicitly asked for in the args (e.g. for inference), though correct me if i'm wrong. So here, I guess if we default to epochs > 0,  then we just need to put something in the README that you can re-use the expert by setting epochs = 0 (and then maybe we raise an error if there is not expert where we expect it to be in this case.).

Yep, expert.py manages. No dataset is passed to expert anymore. It just reads from the index file.
Indexes are pickled between runs no? So it should be deterministic with new initialization. Regardless, the expert is pickled now so the weights remain same between runs.

Nice, thanks. Yeah I was worried about that but in a big rush trying to make a fix when I made the PR and then promplty disappeared. It looks like you cleaned up some naming, etc as well, so is it safe to assume that you have valdated that those are the correct changes, or should I do more testing?

I've validated but always a fan of triple checking.

How was the accuracy w/ and w/out features?

I forget off hand but they were on par with my usual runs with polish.

@kylebgorman @Adamits are there responses I missed at all? else i can work on linting for push

@kylebgorman @Adamits are there responses I missed at all? else i can work on linting for push

it’s LGTM modulo style/lint.
note that it’s ‘Any’ not ‘any’

@kylebgorman @Adamits are there responses I missed at all? else i can work on linting for push

it’s LGTM modulo style/lint.
note that it’s ‘Any’ not ‘any’

Kk, will run linting later in afternoon for merge.

@Adamits any pertinent issues limiting merge?

@Adamits any pertinent issues limiting merge?

Sorry, will go back through right now.

@kylebgorman checks passed. ready to merge. let's kill this issue

Sorry for slow responses, was traveling without laptop most of the last week.


⚠ BUILTINS : OUTPUT STREAM MISFUNCTIONS

export > file this commands writes to STDINPUT rather than writing to the given file
echo "some text" > file this as well falls into the same problem.
This concerns just BUILTINS

Detections:

The given file doesn't get created

This issue is true fixed in 2 steps:

When running a BUILTIN the app wasn't allocating for it the right output stream. So we had to add this piece of code to make it at least the outputting correct write_to(cmd->out_fd) .
Then it turns out that the application outputs to the right output stream but the program hangs there, the problem is when we specify for it the output stream and we are not doing it inside a child process since we running a builtin command we're reshaping the output stream and hence we lose STDOUT, the fix of this is reachable by saving the STDOUT before get in to the loop  the same thing we did in #6 but this time with STDOUT


[DEP-22] mkcert fixed #297

Description
Mkcert is fixed so that the certificate warning on Chrome will no longer appear. This is done by pointing SSL_CRT_FILE to /usr/app/localhost.pem and SSL_KEY_FILE to /usr/app/localhost-key.pem in the client package.json file.
This requires the user to copy the certificate keys from the server to the client folder for the docker builds to work.
Readme updated to reflect the need to copy the local certificate public and private keys into the client folder
Risks
This requires the user to copy the certificate keys from the server to the client folder for the docker builds to work.
Validation
Certificate Warning no longer appears.
Issue
#297
Operating System
Mac M Series

the client/.gitignore and server/.gitignore files are no longer needed as there is a main .gitignore in the root folder that already should be blocking localhost*.pem, cer, and key files. You are safe to ignore those two files when fixing the conflicts prior to merging in main.

for any folks who are unable to access the client's web pages after merging this PR to your local main, @raadelmsellati discovered that you're required to navigate into your client directory and execute the following command:
mkcert localhost


v2.0.31 Fails on ruby 2.7.x

PR https://github.com/rails/tailwindcss-rails/pull/280 replaces Gem::Platform#match to Gem::Platform#match_gem? This fixes deprecation warnings but breaks on ruby 2.7.? because match_gem? does not exist there (at least not on 2.7.3).
This causes errors like these:
bin/rails tailwindcss:watch
rails aborted!
NoMethodError: undefined method `match_gem?' for Gem::Platform:Class

Tasks: TOP => tailwindcss:watch

and
when running bin/rails s
ActionView::Template::Error (The asset "tailwind.css" is not present in the asset pipeline.
):
     5:     <meta name="viewport" content="width=device-width,initial-scale=1">
     6:     <%= csrf_meta_tags %>
     7:     <%= csp_meta_tag %>
     8:     <%= stylesheet_link_tag "tailwind", "inter-font", "data-turbo-track": "reload" %>
     9:
    10:     <%= stylesheet_link_tag "application", "data-turbo-track": "reload" %>
    11:     <%= javascript_importmap_tags %>

app/views/layouts/application.html.erb:8

Work around
Update your gemfile to fix tailwindcss-rails to version 2.0.30 and run bundle update.

Thanks for reporting, I'll take a look as soon as I can.

So Gem::Platform#match_gem? was introduced in https://github.com/ruby/ruby/commit/4aca77ed / Rubygems v3.2.0 which was released with just before Ruby 3.0 on 2020-12-10.
I think we've got three options

drop support for Ruby 2.7 in this gem

(which would be different from Rails's support matrix (this is not really an option))

set required_rubygems_version to >= 3.2.0 in tailwindcss-rails.gemspec

which might break some people's container configurations, but maybe that's OK

revert #280 until Rails drops support for Ruby 2.7

@rafaelfranca do you have an opinion between options 2 and 3 above?

2 is ok for me.

v2.0.32 has been released which fixes this.

Indeed, this broke all of my heroku apps that are on the heroku-20 stack...

@gxespino I'm sorry, I don't understand. If 2.0.32 broke something please open a new issue.


refactor: move deploy_account_tx next to peers

Moved next to similar constructors invoke_tx() and declare_tx().
NOTE: Only move, no internal changes.

This change is

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

Project coverage is 82.89%. Comparing base (64fab3b) to head (b1631d9).

Additional details and impacted files
@@                Coverage Diff                @@
##           gilad/deploy-gen     #458   +/-   ##
=================================================
  Coverage             82.89%   82.89%
=================================================
  Files                    37       37
  Lines                  1719     1719
  Branches               1719     1719
=================================================
  Hits                   1425     1425
  Misses                  217      217
  Partials                 77       77

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


fix: DropdownContainer resize algorithm

SUMMARY
Fixes a bug in the DropdownContainer resize algorithm. Previously, the algorithm did not consider moving more than one element simultaneously when there was enough width available.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
https://user-images.githubusercontent.com/70410625/205335437-cbfa7d86-4b38-49b1-a8c6-a9efd53032d4.mov
https://user-images.githubusercontent.com/70410625/205334932-ccf377b6-69e3-446d-a410-daf737d2c4cf.mov
TESTING INSTRUCTIONS

Open the Storybook or horizontal filter bar
Resize the screen and check the elements are correctly rendered

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up FEATURE_HORIZONTAL_FILTER_BAR=true

Hey @michael-s-molina I think there is still might be an issue. I added a 4th filter and the "more filters" is showing up even though there would be space for it

Hey @michael-s-molina I think there is still might be an issue. I added a 4th filter and the "more filters" is showing up even though there would be space for it

If you refresh the page, it shows? If not, then is because it doesn't fit.

/testenv up

/testenv up FEATURE_HORIZONTAL_FILTER_BAR=true

Works great now!


[iOS][WeexSDK] iconfont can not showed as expected where weex version is 0.26.0

Loading two iconfont ttf files at the same time, the fonts in one font library are not displayed, and are normal on the browser.
this is the test dotwe address
http://dotwe.org/vue/f378cb6fecaff54b6951326e4a2002a2
Environment
Device: [e.g. iPhone X]
OS: [e.g. iOS13.1]
Version [e.g. 0.26.0]
Build from source [e.g. yes]

@jianhan-he Have a look ?

The issue is very similar with https://github.com/apache/incubator-weex/issues/3014

The issue is very similar with #3014

Yes, They were both posted by me. Please help me to resolve this problem, thx

Close this issue as it solved in https://github.com/apache/incubator-weex/issues/3014#issuecomment-558519447


fix: add oac with cloudfront, edge lambda, updates to request/callback

Description
The PR updates

the authentication mechanism on the lambda url to AWS_IAM
Updated CloudFront to use the lambda updates
Added lambda edge function inject the header x-amz-content-sha256
Updated references of Terraform Cloud to HCP Terraform.
Added a tags variable to all feasible resources
Lambda version bumped to 3.11
sleep reference added for lambda@Edge deletion and Cloudfront resource.
fulfillment logic fix for No resource changes

Resolves #116
Closes #117
Resolves #115
Resolves #113
Resolves #119

Resolving #119 will require breaking change for existing customer, since we moved the state function log name space from /aws/state/ to /aws/vendedlogs/states/

/do-e2e-tests

/do-e2e-tests

/do-e2e-tests

/do-e2e-tests

/do-e2e-tests

/do-e2e-tests

/do-e2e-tests

error creating WAF log, might be relevant to this

/do-e2e-tests


Creating Project Tasks records wrong time

When you create a new task for a milestone through the +Add Task button next to the Milestone, it saves the start and end dates and seems to apply the timezone offset when it saves.
Eg a start date of 12/15/2011 09:00 with a default timezone from Administration Settings of GMT +10 will record the start date as 12/14/2011 23:00
When you edit the task and update the time it seems to fix it.

On my debian server I just set the server timezone using:
dpkg-reconfigure tzdata


rand module2

I get the riak_core_ng from the hex.pm, but found the random module is still being used. And I diff the riak_core_ng code with the branch 0.9.0, and they are the same. So I make the pr on the branch 0.9.0.
update the chash to version 0.1.2, and then update the lock file.

Hi getong, first of all thank you for this! using rand in newer versions of Erlang it definitely a needed improvement! But (there is always a but isn't there?) I think the approach is a bit problematic. The way you achived this cause a lot of code duplication and will later on make merging upstream changes a hell. A better approach would be to add a single random_uniform (and perhaps random_uniform_s) function to riak_core_util the same way it's for crypto functions. That way the code for calling random is only duplicated in a single place and everything else is just 1 line changes that later merges can work out nicely. Do you agree that this would be a approach more beneficial in the long urn?


Cursor disappears with syntax-highlighting plugin in the embedded terminal of Jetbrain IDEs

Description
A Jetbrains IDE offers an embedded terminal which I use quite often. If I enable syntax-highlighting and use the arrow keys to navigate, the cursor disappears and will only be visible when it blinks/flashes.
I don't know if this is an error of prezto (because it does work perfectly without the embedded terminal) or from Jetbrains - I guess Jetbrains.
I'm trying to find help to isolate the problem to raise an issue within the Jetbrains Bugtracker.

Steps to Reproduce

Enable the syntax-highlighting plugin
Start a Jetbrains IDE and open the embedded Terminal
Use arrow keys to navigate

Versions

Prezto commit: latest
ZSH version:  5.3 (x86_64-apple-darwin17.0)
OS information: OSX 10.13

I also asked on Stackoverflow but anybody has replied yet.

I did not make any heavy modifications.

Do you still see this issue if you disable the cursor highlighter? By default only the main highlighter is active... and I've seen a number of issues filed against the syntax highlighting module which seem similar to what you're seeing.
If you remove the 'cursor' \ line from the syntax highlighting config in your zpreztorc, this will disable the cursor highlighter and may fix this issue.
https://github.com/zsh-users/zsh-syntax-highlighting/blob/master/docs/highlighters.md
https://github.com/zsh-users/zsh-syntax-highlighting/issues/171

Yes, that did work! :)
For others, my enabled highlighters:
zstyle ':prezto:module:syntax-highlighting' highlighters \
   'main' \
   'brackets' \
   'pattern' \
   'line' \
   'root'

the same for me but in 'vi' editor - command mode, the cursor disappears, and removing the 'cursor' \ line in highlighters works great!

I had the same issue and wasn't able to resolve it by taking out the cursor syntax highlighting option.
I was only able to get my cursor back after I disabled zstyle ':prezto:*:*' case-sensitive 'yes'
I'd prefer to have colors, but it's better than nothing. Not sure what that happens. I'm using xfce terminal btw.


Cli version updated to 3, build fixed

Tested from 18882789

We have some problems with codegen as I need to fix

manually
We are waiting for fix in cli from subquery team. And I should try to clean cache, it can be a potential issue

test log from 18882789:
test.log


doesn't return results

I launch Grepper -tool ag  -open -switch in neovim 45b37 (<1 week) and then I launch a search for which I know for sure there are results. The research failed because it is interrupted by an error:
ERR: Skipping ./files-0/tmp/socket2: Error opening file: No such device or address

Erreur détectée en traitant function <SNR>96_on_stderr :
ligne    1 :
E900: Invalid job id

It happens systematically.

Hmm, I can't reproduce it on OSX.
Where is that ./files-0/tmp/socket2 file? Maybe it's tripped up by the socket file, although I wouldn't know why.

Can you verify that line 1 of s:on_stderr() in autoload/grepper.vim starts with silent!?
Does it work when you use a query that never matches?
Does it work if you change the working directory to a completely different directory?

File got permission:
srwxrwxr-x 1 teto teto 0 janv.  7 15:32 files-0/tmp/socket2=
I removed the file and it worked again. I have no autoload/grepper.vim. I just ran a PlugUpdate but I can't reproduce since I just deleted the socket and dunno how to recreate one easily (silly me).

It's fixed now. Thanks for reporting!

Thanks for fixing this and all your great plugins (I am mattX on neovim's irc ;) )

Hah, you're welcome!


protractor-istanbul-plugin didn't work

Hi there,
i just installed this plugin into my project and edited the protractor.conf.js per doc suggested.
When i ran the e2e testing, there's no code coverage json files generated under coverage folder.
Would u please give me some hints?
Thank you in advance.

Even i am facing the same issue


3rd Party Pen Test?

Are there any 3rd party research firms that have submitted pen test of Microsoft owned environments, like service fabric? If so could you share with me or post here? This is a requirement for many of our partners to share in RFPs as they compete for new business.

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

ID: 19cb71ec-6372-f406-8542-8058f59c7ec1
Version Independent ID: a3c05dfb-8f20-b364-526b-143f87582a18
Content: Pen Testing
Content Source: articles/security/azure-security-pen-testing.md
Service: security
GitHub Login: @TerryLanfear
Microsoft Alias: barclayn

@PATRICKwithMSFT Thank you for your feedback! We will review and provide an update as appropriate.

@PATRICKwithMSFT I am checking this internally with the product team and let you know of my findings.

@PATRICKwithMSFT Can you please send mail to azureblueprint[at]microsoft[dot]com so that someone from compliance can provide you this information.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Add beginner-level documentation for installation and use

This may seem very obvious to users of this repo but I couldn't quite recall the steps to install the latest version of wasi-sdk from the release binaries.

Great!  This looks good to me now.  We can remove the mentioning /opt as the default once we update to llvm 11 at which point we can rely instead on https://reviews.llvm.org/D76653.

@sunfishcode OK to land this?

Ok!


Replace Dijkstra (PriorityQueue) with BFS (normal queue) when picking landmarks

Currently we use LandmarkExplorer extends DijkstraBidirectionRef for the landmark selection but as we just use weight==1 for all edges we should switch to BreadthFirstSearch which is cleaner and should also give a minor speedup

Not yet worth the effort


Upgrade from gpt-3-encoder to gpt-tokenizer

https://github.com/niieani/gpt-tokenizer
The above package was originally a fork of gpt-3-encoder but has been upgraded to TypeScript and allows for selecting different encode types (e.g. default is cl100k_base, but if you're using davinci you can switch to cl50k_base).
Teams AI just switched to gpt-tokenizer as well :) 👍🏼

Thanks @corinagum... I'm planning to create a whole new collection of tokenizers to help address this.

If you would remove the gpt3-tokenizer reference, one could bring any other tokenizer implementation easily.