MB-5590 Add UpdateMTOServiceItem service object

Description
This PR adds an UpdateMTOServiceItem function to the services package. It also sets up this service object with the validator pattern used for UpdateMTOAgent (old PR): https://github.com/transcom/mymove/pull/4860
In addition to adding this service object, I also made some updates to the UpdateMTOAgent service object and validators that align with feedback I've gotten in the past. I did this so that the validation pattern could stay updated as I implemented it again with UpdateMTOServiceItem.
Note that there is no endpoint to test this service object currently.
Reviewer Notes
I wanted to keep validation bare so that I wasn't making too many assumptions, but I wasn't sure if I was missing anything for the SITDeparture validation in particular. Let me know if you think of any other rules for this update that I should implement! (Especially @shimonacarvalho)
Setup
Right now we only have the tests to go off of for this code. Feel free to write an adhoc script to call this service object against the dev database, but the goal is for the tests to be as comprehensive as possible.
You can run:
make server_test

for the full suite of tests. Or you can run:
go test ./pkg/services/mto_service_item -v

for the mto_service_item package's tests. If you want to run each set of tests individually, these are the functions you'll need to call (using the -testify.m flag):
TestMTOServiceItemUpdater
TestValidateUpdateMTOServiceItem
TestUpdateMTOServiceItemData

Code Review Verification Steps

[x] The requirements listed in Querying the Database Safely have been satisfied.
[ ] Request review from a member of a different team.
[x] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change.

Messages

:book:
:link: MB-5590

  Generated by :no_entry_sign: dangerJS against 45788f1957de0aa71f016c38aa333f34cadf9b0e


LGX (GC550) isn't happy when restarting application after initial bootstrap

Might be worth attempting to detect whether device is bootstrapped before bootstrapping?
Strategy could involve attempting a read with a rather low timeout; if the operation times out, we need to bootstrap, otherwise we're good to go?
The lowtech solution is to close the application and unplug and plug in the USB cable and restart the application.
Currently the audio comes through ok, but the video frames don't seem to update (the device is sending the same frame over and over or no start/end frame identifiers? Not investigated...)

The strategy of reading a frame and detecting a timeout works really well, it's in the gtk-window branch which will be pulled in soon!


Redesign monitored variables for hp_ilo sensor

Allow generating specific sensors without the need for template sensors
Description:
Major redesign on the hp_ilo component allowing generating specific sensors without the need for template sensors.
This means a small (but breaking) change for existing users, due to the monitored_variables configuration entry now requiring a sensor name and sensor type instead of being an plain list
I have added an example including a screenshot to the home-assistant.github.io PR.
Related issue (if applicable): n/a
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#2608
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: hp_ilo
    host: IP_ADDRESS or HOSTNAME
    username: USERNAME
    password: PASSWORD
    monitored_variables:
      - name: SENSOR NAME
        sensor_type: SENSOR TYPE

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

Hi @Juggels,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

@balloob I've done some changes, no longer requiring the external dependency. Also updated the docs in home-assistant/home-assistant#2608

Processes requested changes in latest commit

Processes requested changes in latest commit

Thanks! 🐬


Porch: Unable to have two git repos with same URL and different directories

Original issue URL: https://github.com/kptdev/kpt/issues/3601
Original issue user: https://github.com/LiptonB
Original issue created at: 2022-10-05T19:10:31Z
Original issue last updated at: 2023-01-26T04:38:30Z
Original issue body: ### Expected behavior
I would like to store multiple groups of configs in the same git repository. I thought I might be able to do so by creating multiple porch Repositories pointing to the same git repo. So I have the following repositories with the same repo URL but different directory values:
apiVersion: config.porch.kpt.dev/v1alpha1
kind: Repository
metadata:
  name: repo1
  namespace: default
spec:
  content: Package
  deployment: true
  description: Repo1
  git:
    branch: master
    createBranch: true
    directory: /repo1
    repo: https://github.com/[redacted]
    secretRef:
      name: github-pat
  type: git

apiVersion: config.porch.kpt.dev/v1alpha1
kind: Repository
metadata:
  name: repo2
  namespace: default
spec:
  content: Package
  deployment: true
  description: Repo2
  git:
    branch: master
    createBranch: true
    directory: /repo2
    repo: https://github.com/[same redacted URL]
    secretRef:
      name: github-pat
  type: git

I expected to be able to clone a package into either one of these repos:
kpt alpha rpkg clone porch-test-blueprints-cd096908f5390cc134a7b4d631cd3717b94b1b5e newpackage --repository repo1 -ndefault
kpt alpha rpkg clone porch-test-blueprints-cd096908f5390cc134a7b4d631cd3717b94b1b5e newpackage --repository repo2 -ndefault

Actual behavior
Though the above is the behavior I'd most prefer (package name independent of the repository), the commands above both produce the error message:
Error: Internal error occurred: cannot create newpackage outside of repository directory "repo1"

To work around this, I tried including the directory name in the package name. This one worked:
kpt alpha rpkg clone porch-test-blueprints-cd096908f5390cc134a7b4d631cd3717b94b1b5e repo1/newpackage --repository repo1 -ndefault

However this one:
kpt alpha rpkg clone porch-test-blueprints-cd096908f5390cc134a7b4d631cd3717b94b1b5e repo2/newpackage --repository repo2 -ndefault

still produces an error message that references the repo1 directory:
Error: Internal error occurred: cannot create repo2/newpackage outside of repository directory "repo1"

I was not able to find a way to clone into this second repository.
Information
kpt version: 1.0.0-beta.19
porch version: 1de5acf9cc65e99a9b491db2e5dd643c231767b0
porch UI version: https://github.com/GoogleContainerTools/kpt-backstage-plugins/commit/6334354fb4e880ef316ef447609b4f8765dccfa5
Steps to reproduce the behavior

Use Porch UI to register two git repositories with the same repo URL and different directories
Attempt to clone a package from a separate blueprint repository (doesn't matter whether it's in the same or a different git repo) into these two Porch repositories

Original issue comments:
Comment user: https://github.com/droot
Comment created at: 2022-10-05T21:17:12Z
Comment last updated at: 2022-10-05T21:17:12Z
Comment body: Given that both the repositories are deployment repos, I suspect cloning restrictions are kicking in. If repo1 was a not a deployment repository, it would have probably worked.
/cc @ChristopherFry @mortent @natasha41575
Comment user: https://github.com/droot
Comment created at: 2022-10-05T21:22:57Z
Comment last updated at: 2022-10-05T21:22:57Z
Comment body: I do want to point out that we are not testing this mode (registering separate porch repos for different directories in a single github repo) regularly so some more surprises may be in the store. Thanks for reporting it.
Comment user: https://github.com/LiptonB
Comment created at: 2022-10-05T21:43:11Z
Comment last updated at: 2022-10-05T21:43:11Z
Comment body: Thanks for the quick answer! In case this is useful information, I also saw similar behavior when a blueprint repo was involved. I didn't test as many permutations there, but I was unable to clone a package in blueprint repo blueprints into deployment repo repo2, getting an error message that it couldn't create the package outside of repository directory "blueprints".
Comment user: https://github.com/droot
Comment created at: 2022-10-05T22:02:14Z
Comment last updated at: 2022-10-05T22:02:14Z
Comment body: > Thanks for the quick answer! In case this is useful information, I also saw similar behavior when a blueprint repo was involved. I didn't test as many permutations there, but I was unable to clone a package in blueprint repo blueprints into deployment repo repo2, getting an error message that it couldn't create the package outside of repository directory "blueprints".
ok, so it is broken in all cases then. Thanks for confirming this.
@LiptonB I am curious about how are you planning to use kpt in general (use-case, what time configs, personas involved etc.). Feel free to share as much as detail possible, it can help us prioritize better.
Comment user: https://github.com/LiptonB
Comment created at: 2022-10-06T15:25:07Z
Comment last updated at: 2022-10-06T15:25:07Z
Comment body: I'll start by saying that I think I don't actually need multiple repositories. I do think they would be useful if they provided namespacing such that the repo name didn't have to be in the package name. But I think that I will be ok with one big repository for the time being, and will just name the packages clustername/packagename. The context here is that I would like to maintain many deployments of the same blueprint, where each one will be deployed to either a different cluster or a different namespace within a cluster.
What I'm trying to do is manage a repo that will be the source of a GitOps sync for a large number of GKE clusters. I want to be able to automate the following:

Standing up a new cluster and the applications that go on it. That means setting up a spot in the repo for it to sync from and putting the relevant application configs into that sync location.
(Gradually) rolling out new application versions when they are built in CI by updating the image tag
(Gradually) rolling out configuration changes to all the clusters

I think kpt, and porch in particular, is relevant because:

Deployments of the same blueprint to different clusters can be in different states but there is still a process to roll out a change to all of them
Puts an API surface in front of edits to the git repo, facilitating writes from CI jobs and custom kubernetes controllers
Kpt functions provide a nice way to structure those writes (rpkg pull | kpt fn eval | rpkg push)
UI opens up new possibilities for editing objects (in this case mainly company-internal CRDs) without much kubernetes knowledge

Comment user: https://github.com/droot
Comment created at: 2022-10-06T18:48:57Z
Comment last updated at: 2022-10-06T18:48:57Z
Comment body: > What I'm trying to do is manage a repo that will be the source of a GitOps sync for a large number of GKE clusters. I want to be able to automate the following:

Standing up a new cluster and the applications that go on it. That means setting up a spot in the repo for it to sync from and putting the relevant application configs into that sync location.
(Gradually) rolling out new application versions when they are built in CI by updating the image tag
(Gradually) rolling out configuration changes to all the clusters

I think kpt, and porch in particular, is relevant because:

Deployments of the same blueprint to different clusters can be in different states but there is still a process to roll out a change to all of them
Puts an API surface in front of edits to the git repo, facilitating writes from CI jobs and custom kubernetes controllers
Kpt functions provide a nice way to structure those writes (rpkg pull | kpt fn eval | rpkg push)
UI opens up new possibilities for editing objects (in this case mainly company-internal CRDs) without much kubernetes knowledge

Spot on. Makes perfect sense. The value prop of kpt stack is articulated even better than our copy of the website.

I'll start by saying that I think I don't actually need multiple repositories. I do think they would be useful if they provided namespacing such that the repo name didn't have to be in the package name. But I think that I will be ok with one big repository for the time being, and will just name the packages clustername/packagename. The context here is that I would like to maintain many deployments of the same blueprint, where each one will be deployed to either a different cluster or a different namespace within a cluster.

How do you setups roles (and permissions) for managing this configs or that is not a requirement in your case ?
Comment user: https://github.com/johnbelamaric
Comment created at: 2022-10-06T19:35:10Z
Comment last updated at: 2022-10-06T19:35:10Z
Comment body: @LiptonB we have many of these same use cases in Nephio, which is a new OSS project for edge fleet management, with a focus on Telco. When relevant, I am trying to upstream the things we need for Nephio into Porch, because I see - as you do - many other use cases for the same functionality.
In your case, take a look at https://github.com/GoogleContainerTools/kpt/issues/3488, which is all about generation of variants of an upstream package. For the broader question of rollouts and - in the Nephio case - multi-actor, coordinated editing of the deployment config, you may want to see the issues referenced here: https://docs.google.com/document/d/1E-pMeb8u46C-UayBSaYG_WeqDcRrpq8OhocW3mr65ws/edit?usp=sharing (you'll need to join<EMAIL_ADDRESS>to view and comment).
Comment user: https://github.com/johnbelamaric
Comment created at: 2022-10-06T19:36:44Z
Comment last updated at: 2022-10-06T19:36:44Z
Comment body: There is also a demo PoC referenced in the doc, that is sort of the precursor to the functionality in #3488. In that case, we assume separate repos per cluster, but you'll see in #3488 we generalize targets beyond that.
Comment user: https://github.com/LiptonB
Comment created at: 2022-10-06T22:27:32Z
Comment last updated at: 2022-10-06T22:27:32Z
Comment body: > How do you setups roles (and permissions) for managing this configs or that is not a requirement in your case ?
Well, this is all somewhat exploratory right now so I'm not completely sure 😄 We do need some access control over these configs - we'd want review of manual changes before applying them, though we might potentially be ok with system-driven rollouts happening automatically. Since I wasn't seeing those access controls in porch as it exists today and wasn't sure how things were going to evolve, I was thinking of starting by only using porch to create and edit draft revisions, and using GitHub PRs (with CODEOWNERS to control approvals) to make changes actually take effect. Haven't tested this workflow yet, though, so not sure how well it'll work.

Duplicate of #628

Duplicate of #628


Bot often ran into Network Error caused by httpx

I am hosting this bot on K8S and it always ran into this error and caused the bot stopped response:
Error:
    return await super().send_message(
  File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 331, in decorator
    result = await func(*args, **kwargs)  # skipcq: PYL-E1102
  File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 760, in send_message
    return await self._send_message(
  File "/usr/local/lib/python3.8/site-packages/telegram/ext/_extbot.py", line 488, in _send_message
    result = await super()._send_message(
  File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 512, in _send_message
    result = await self._post(
  File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 419, in _post
    return await self._do_post(
  File "/usr/local/lib/python3.8/site-packages/telegram/ext/_extbot.py", line 326, in _do_post
    return await self.rate_limiter.process_request(
  File "/usr/local/lib/python3.8/site-packages/telegram/ext/_aioratelimiter.py", line 247, in process_request
    return await self._run_request(
  File "/usr/local/lib/python3.8/site-packages/telegram/ext/_aioratelimiter.py", line 203, in _run_request
    return await callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 450, in _do_post
    return await request.post(
  File "/usr/local/lib/python3.8/site-packages/telegram/request/_baserequest.py", line 165, in post
    result = await self._request_wrapper(
  File "/usr/local/lib/python3.8/site-packages/telegram/request/_baserequest.py", line 288, in _request_wrapper
    raise exc
  File "/usr/local/lib/python3.8/site-packages/telegram/request/_baserequest.py", line 274, in _request_wrapper
    code, payload = await self.do_request(
  File "/usr/local/lib/python3.8/site-packages/telegram/request/_httpxrequest.py", line 223, in do_request
    raise NetworkError(f"httpx.{err.__class__.__name__}: {err}") from err
telegram.error.NetworkError: httpx.RemoteProtocolError: <ConnectionTerminated error_code:ErrorCodes.NO_ERROR, last_stream_id:95, additional_data:None>

Every time i need to fix it by restarting the pod
I have done some research online they said upgrading the httpx modules helps, but i don't familar with this package.

@simonlaw0711
I created branch http-version with possible fix of your problem. To apply updates:
git pull
git checkout http-version

Please, write here if it helps or not.

Hello @karfly
I have encountered another error:
  File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 512, in _send_message
    result = await self._post(
  File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 419, in _post
    return await self._do_post(
  File "/usr/local/lib/python3.8/site-packages/telegram/ext/_extbot.py", line 326, in _do_post
    return await self.rate_limiter.process_request(
  File "/usr/local/lib/python3.8/site-packages/telegram/ext/_aioratelimiter.py", line 247, in process_request
    return await self._run_request(
  File "/usr/local/lib/python3.8/site-packages/telegram/ext/_aioratelimiter.py", line 203, in _run_request
    return await callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 450, in _do_post
    return await request.post(
  File "/usr/local/lib/python3.8/site-packages/telegram/request/_baserequest.py", line 165, in post
    result = await self._request_wrapper(
  File "/usr/local/lib/python3.8/site-packages/telegram/request/_baserequest.py", line 290, in _request_wrapper
    raise NetworkError(f"Unknown error in HTTP implementation: {repr(exc)}") from exc
telegram.error.NetworkError: Unknown error in HTTP implementation: TypeError('Object of type PosixPath is not JSON serializable')

It works, thanks a lot @karfly

hey @karfly , can i know whats the different between the main version and the http-version?

@RaflyLesmana3003 you can see changes here: https://github.com/karfly/chatgpt_telegram_bot/commit/28e7426c2b248767774836db2281c20df1213b31


probe-run cannot detect pico

Description
probe-run is unable to detect my Raspberry Pi Pico. The pico is visible according to fdisk, so it is not a connection or permissions issue.
Example
$ probe-run --list-probes

Error: no probe was found.

Common reasons for this are faulty cables or missing permissions.
For detailed instructions, visit: https://github.com/knurling-rs/probe-run#troubleshooting

$ sudo fdisk -l

...

Disk /dev/sda: 128 MiB, 134217728 bytes, 262144 sectors
Disk model: RP2
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000a6117

It might be that you need to update the USB permissions. What is lsusb telling you? Refer to https://github.com/knurling-rs/probe-run/#error-no-probe-was-found for more steps.

Because you have shown fdisk output, I believe your RP2040 is in USB Bootloader mode. You cannot program an RP2040 in USB Bootloader mode with probe-run. Instead you must use a proper ARM SWD Debug Probe, like a SEGGER J-Link or a Raspberry Pi Debug Probe.
If you want to upload firmware to the RP2040 in USB Mass Storage mode, try elf2uf2, but then you won't get defmt logging.

Thanks @jonathanpallant
@colossalchicken Does this solve your question?


Create a module to transform TRAPI Query Graph

Expand node by its id, e.g. if user provides a MONDO ID as input, we will traverse MONDO hierarchy to get all its descendants.
Expand node by its category, e.g. if user provides a NamedThing category, we will traverse BioLink class hierarchy to get all descendants of NamedThing class.
Expand predicate, e.g. if user provides a related_to predicate, we will traverse BioLink predicate hierarchy to get all descendants of related_to predicate.

no issue created for this yet; Per Kevin (I think), "Can add query graph expansion here: https://github.com/biothings/bte_trapi_query_graph_handler/blob/018bc2fd0b7a1f2a230069b4fecd57841739944e/src/query_graph.js#L86)
addressed in https://github.com/biothings/BioThings_Explorer_TRAPI/issues/102
being addressed in https://github.com/biothings/BioThings_Explorer_TRAPI/issues/167

close this one now. the remaining issue of node expansion is moved into a separate issue: #196


Add simd_extmul_* support for x64

@abrown I will let @sparker-arm comment because he has done the same changes in PR #3070.


Add JavaScript export question

Checklist:

[X] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)

I have changes based on your feedback. Thanks a lot! There are lot of grammar mistakes from me before. Thank you for giving your time checking it. I also has resolved the conflict after pulling from main branch


Update the documentation for the file I/O calls.

I had to tinker with the Latex table rendering, because some very weird things were happening --- the table wasn't being page wrapped properly and pages were being floated to the end of the document.
The itemised lists probably also want a custom environment to remove the line spacing to improve readability a little.

Apparently it does that :) It is sortable. When I did it half the APIs were shoved to the back.


Remote method call to object instantiated from ES6 style class is not quite working

ES6 classes treat member functions as non-enumerable in the instantiated class. However remote currently only works with enumerable properties, which means I have to use the old school prototype style to define classes for remote use. I find it a little bit inconvenient.
Here is an example:
in main process
class ClientSocket {
    connect() {
        //..
    }
}
app.clientSocket = new ClientSocket();

in render process
const clientSocket = remote.app.clientSocket;
clientSocket.connect() // this doesn't work because connect() is not enumerable.

I mostly write new code in ES6 style and I'd like to keep my code style consistent. Is there any way to enable remote for ES6 class?

It is quite a surprise to me that ES6 class methods are not enumerable.

Taken from Dr. Axel Rauschmayer words: Prototype methods Foo.prototype.* are writable and configurable, but not enumerable.

@zcbenz Yeah, it's a surprise to me too. For now I can just use prototypes or reconfigure the properties. However to me it seems that it's necessary to provide some long term solution for this since eventually people will start using ES6 syntax and class is a nice feature to group functionalities.
One idea, is that possible to also include those non-enumerable own properties that are functions?
There is a stackoverflow answer here demonstrate some similar ideas:
http://stackoverflow.com/questions/31054910/get-functions-of-a-class
However I think this does need some consideration and discussion.

I just wrote a whole stack of classes, put them into my main js file and was stuck for hours trying to find out why there were no methods on the classes when getting them with remote.require
i would love to be able to use the syntax instead of rewriting all the classes, is there a way to bypass this issue or any plans for the next release to include such functionality?


[stress] The dashboard shows a "Completed" status for pods that are failed

I have an 'infiniteSendAndReceive' scenario for Go, where the last failure was actually that it never created the pod:
go               infinitesendandreceive-gosb-11--1-44p45               0/1     Init:Error         0                  3d13h
It looks like the dashboard isn't showing the most current status, but more the last completed status for the run. So since my pod didn't launch it's just showing me the last run instead.
I think the best outcome here is if the pod is in a failed state, or never launched or is still running then the status should reflect that (InitFailure|FailedToLaunch|InProgress), or similar.

Should mention that this is intended to be the "gateway to the world" for anybody trying to get a handle on how their team is doing. So accuracy here is important as those people might not even be looking at the cluster through kubectl.


finished exec_proc

Pull Request Test Coverage Report for Build 69

136 of 146 (93.15%)  changed or added relevant lines in 9 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-1.5%) to 97.913%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mltoolkit/utils/exec_proc.py
59
69
85.51%

Files with Coverage Reduction
New Missed Lines
%

mltoolkit/utils/doc_inherit.py
1
90.2%

mltoolkit/datafs/dataflow.py
2
97.96%

Totals

Change from base Build 34:
-1.5%

Covered Lines:
1190

Relevant Lines:
1203

💛  - Coveralls


How to use on 3070 graphics card？

My 3070 graphics card doesn't support cuda10.1. When I compile qd-3dt, it will report an error.

I have solved this issue.

Hi digitial,
Glad you figured it out. Would you please share how you solved the issue?
I am having a similar situation with "ValueError: Unknown CUDA arch (8.6) or GPU not supported" on RTX 3090.
Thank you very much.
Sincerely,
Ziheng

The environment I have:
RTX 3090
torch 1.8.0
cuda 11.3
Thanks

Hi digital. would you mind sharing with us how did you solve it?


Try Symfony 3.3 beta1

@tgalopin maybe it's time to try Symfony 3.3.0-RC1 and update your PR?

Yes, I will retry. I don't have time right now but in a few days

Blocked by https://github.com/symfony/symfony/issues/22854 (resolved in https://github.com/symfony/symfony/pull/22878, waiting for merging).


Pressing enter in search field triggers Create command button execution

In all forms when user search the list/grid and press Enter - it executed by default the CommandButton in the same form. That triggers Create request always.

i fixed this in branch. If you agree that this is a defect - i can do a pull request

Thanks man. Go ahead!


Feat: add initial version of github app

Signed-off-by: Jian GU<EMAIL_ADDRESS>

Thanks a lot Jian!


Subscriptions cant be run in GraphiQL

When starting a mesh via the cli a graphiql instance is started. While it was possible to run Queries and Mutations it is not possible to run subscriptions.
To Reproduce

Run any mesh with subscriptions
Use the graphiql instance to execute a subscription
This will fail with an invalid URL error since the subscription endpoint is not provided when graphiql is launched

Expected behavior

Ability to run Subscriptions in the GraphiQL instance that mesh starts.

Environment:

OS:
@graphql-mesh/latest:
NodeJS: 14.x

Turns out the issue is something else. Will investigate further and reopen when I can narrow it down further.

Hmm something seems to be changed in the dependencies. You're right and I noticed we have missing tests for subscriptions.


Add packageRoot directory to Typedoc output

Adds the root directory of the package to the Typedoc output
This is needed for the "Defined In" links on API reference pages

The data currently in Typedoc output is sometimes relative to repo's root and other times relative to package root. Likely due to Typedoc's file discovery algorithm.

@Mergifyio backport release/3.0.x


Better error message for missing gcp property

Better error message when "gcp" property is missing in now.json

Thanks!


feat(protocol): allow Taiko token as L2 fee token

Note that this is only the first step necessary. The bridge also needs to be changed so Ether on L2 will be wrapped as a BridgedERC20 token.
At this point, I think it may not be worthy it to support "Taiko token as the L2 fee token" due to unnecessary implementation complexity. @Brechtpd what do you think?

I don't think it's worth it, but I'm also very hesitant of doing it. It's something I think that is both very important and not important at all, at the same time.
Users in the future will be able to pay in any token using account abstraction, and so then it's only really the proposer that has to handle the L2 fee token. But the proposer needs ETH to pay the L1 gas fees so it will just require additional swaps between ETH and the fee token. So I don't think it adds value to the fee token.
Also adds some non-standard behavior (still a type 1? Apps using msg.value to accept ETH don't work anymore) and extra complexity (bridging between L2s with different fee tokens, also possible msg.value issues, ...).


Workflows: reflect that step.sleep do not count towards max step limits

Summary
Added info that step sleep do not count towards steps limit.

@cloudflare/pcx-technical-writing can you please take a look at this??


RX  Event Dwell Time

The dwell time for the RX event should be adaptable.
The spectrometer can still sample at maximum sampling frequency but we can decimate points accordingly.

This is now handled by the individual spectrometer modules.


Custom HTTP header

It tooks us quite a while to figur out why a custom header was missing while the other headers did show fine. Only then did we find out that HTTP headers may not contain an underscore. Would be nice if the Mendix modeler would already check this. Now at least it is in the documentation.
Regards,
Ronald

@MarkvanMents I think you've worked on docs for HTTP headers before?

Hi Ronald (@RCatersels)
I've updated your suggestion to be a warning box and included a link to the NGINX documentation.
Thanks very much for suggesting this change. I'm sure other developers will find it very useful.
As far as including a check in Studio Pro, I've confirmed with the developers that this is appropriate documentation, but I suggest you add your suggestion to the Mendix ideas forum as it is more likely to gain traction there than coming through documentation.
Mark


DGX2/UCX Usage Patch

This PR adds a patch from @pentschev which fixes an issue when using UCX on a DGX2:
Accepted UCX PR: https://github.com/openucx/ucx/pull/4906

Is this patch necessary for something right now? If not we could skip it and wait for until we're ready to release a 1.8 package.

Waiting for 1.8 makes sense


Replace MatchParam with std::optional where it makes more sense

Pull Request Test Coverage Report for Build 375465759

6 of 10 (60.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 81.563%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

common/goos/Interpreter.cpp
3
4
75.0%

goalc/compiler/Util.cpp
1
4
25.0%

Totals

Change from base Build 373541174:
0.005%

Covered Lines:
16585

Relevant Lines:
20334

💛  - Coveralls


Swift 2.2 + refactor ViewCells and sample controller

Sorry, this is kind of a large and unwieldy PR, but I merged the DateViewCell and ContentViewCell into one class, which allowed for some duplication with cell set up to be removed.
Also made a wrapper for NSIndexPath because this library turns sections into rows and rows into columns, so the property names were really confusing. There's probably a better way of doing that, but this is at least nicer than it was.
And I made some adjustments for Swift 2.2 + broke a large method in the sample controller down into multiple methods.

how can i get this code?

@farazhaider88 checkout the branch at https://github.com/kdazzle/CustomCollectionViewLayout


Init With No Template?

I was wondering if there is a way to init a new project without any UI frameworks, but still get the bare bones skeleton of the necessary files?
Or if don't have to init what would be the bare bones skeleton files that would otherwise be needed?
Thanks for the help.

Hello,
we should add it.
right now you can init vue template them remove vue files.


Regenerate speech and provide a synth script

Add a synth script for generating speech library, including transforms that invoke the partial gapic helper, and that remove the replaced streaming_recognize method and documentation. The method removal transform currently uses a regex and is rather brittle, but it works for now. I'll work on adding a more powerful method removal transform to synthtool later.
I ran regeneration, resulting in very minor changes.

Wow! This is great stuff!
Should V1p1beta1 be added to synth.py?

Whoops, thanks for catching that. I forgot about v1p1beta1. Added and regenerated.


How to extend with syntax --->  server.on("/get", HTTP_GET, [](AsyncWebServerRequest *request)

I discovered this ‘ESPAsync_WiFiManager_Lite’ project today, I find it great; It really makes it easy connecting to WiFi in Configuration Portal Mode.
What I don’t understand is: Once my ESP32 is effectively connected to my WiFi I want it to do “something”, specifically I want it to reply to GET requests to return whatever data
If this makes sense…
Another way to put it is once the WiFi is connected I want the module to serve AsyncWebServer on port 80 (else what the point of getting connected to the network if it’s not to serve data?)
I could I go about this?
I tried :
AsyncWebServer server(80);
then
server.on("/get", HTTP_GET, [](AsyncWebServerRequest *request){
      request->send(200, "text/plain", “Hello world");
});

But it does not work this way I think, I am confused with the various libraries.
A little help would be great.
Thank you very much in advance.

Have a look at Async_ESP32_FSWebServer_DRD example and see how to create and use AsyncWebServer in very similar case.
This ESPAsync_WiFiManager_Lite instance is short-lived and is dead after fulfilling its job, which has no intended purpose to serve any other data besides the Config Portal.
Even I'm glad to see your interest in this library, I'm afraid I won't spend time to help you out, if your problem persists.
Try to  study the  above-mentioned example


[23.11] opentofu: 1.6.2 -> 1.7.0

Description of changes
Manual backport of #295941. I did not spot any breaking changes, only deprecations in the changelog.
https://github.com/opentofu/opentofu/blob/v1.7.0/CHANGELOG.md

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

FWIW I'd rather we avoided feature-releases for the stable branch, even if you "don't spot any" breaking changes. New features can easily introduce new bugs and quirks, and people use the stable branch for stability.

First sentence of the changelog:

The default of use_legacy_workflow changed to false and is now deprecated.

The default changing is itself a potentially breaking change. People need to know they can more-or-less blindly stay up to date on the stable branch and it won't break any of their stuff.


Fixed adwords inclusion in responsive template

The old frontend_index_header_javascript_jquery block does not exist in the header of the new template which leads to the adwords code not being included in the finish action of the checkout.

Just realized that the block was just moved to the index.tpl


H2O model persistence - autogen main class

Downloading a POJO is actually kind of complicated—it still requires the user to build a main class. Can we write a class that will auto-gen and completely jar up a main class/method?

Have you ever used jinja? Its sole purpose is for templating in python. I believe we could autogen the java main class from a template using jinja, but I don't think this will be trivial. Here is a primer on jinja templating.
@tgsmith61591  Feedback?

@charlesdrotar yeah, not going to be easy. But certainly will be a cool—and extremely useful—feature.

This is the primer of sorts for jinja templating - jinja template guide.

Also it seems like if we want this all to run in an automated fashion we may want to consider doing some kind of subprocess call or something in that vein to chain the template generation to the fat-jarring since we are invoking various commands that are CLI-based.

H2O is moving away from POJOs and towards MOJOs. Let's move away from the Java templating; maybe at some point we can tie MOJOs in with skutil.


Add Laravel 9 support

And update PHPDoc.

@vpominchuk Thank you for merging😀

@issakujitsuk thank you for the request.


[Docs] Link old pages to new ones

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
I would like to suggest that docs for older versions of Bootstrap include links to the newest versions.
Motivation and context
This is a fast and convenient way for users to be able to access the latest versions of docs. It is especially useful when trying to search for a topic via a search engine, where users are often directed to articles for older Bootstrap versions. If their framework's major version number is not listed in the dropdown, they must either specify the desired version number in the search term, or navigate to getbootstrap.com's homepage and search there. This is unintuitive.

I would like to do this issue .
Please assign it to me.

Agree. When you google something, you might end up on 5.2 doc. And it states "Latest (5.2.x)".
I would expect that the old documentation tells me that currently 5.3 is the latest and directly links to it.


Make Control impl Send

This will allow controls to be cloned and reused from other threads. I'm not sure how to make this Rust-y, though, because perhaps each Control needs some more guarantees before it can impl Send.
Either way, it's working for me locally, so maybe it's useful for all

Oh, and I needed to base this off of #5 so that it would build locally. If this PR should be merged, it should happen after #5

Are you sure they are thread safe though? As faras I know GDI+ is not thread safe (I'm not sure if libui uses that though), so just putting impl Send there without verifying if the OS APIs are thread safe seems bad.

Hmm, I'm not 100% sure that it's thread safe, but it's a start. Right now, it's impossible to manipulate controls from other threads. Now, it appears to work with a dummy progress bar app: https://github.com/mitchhentges/libui-rs/blob/ecm-example/ui/examples/ecm-download.rs#L54
Maybe it's just thread safe if you use queue_main? I'm not sure.
So, if anything, I was hoping that this would start discussion on designing a safe way to use libui in a multithreaded environment.


[SILGen] Don't peephole closures with abstraction differences in the thrown error

The prolog and epilog code in SILGen is not set up to deal with abstraction differences in the thrown error type of closures, so disable the peephole optimization for closure literals.
Fixes https://github.com/apple/swift/issues/71401 / rdar://122366566, which I've stared at for waaaaay too many hours.

@swift-ci please smoke test


no-callback-literal

Hello,
Could you tell me where is the problem? It's on every first line:
2 Examples:

And the linter error:

Thanks!

Do you have standard locally installed? Does this error also occur when running standard from the command line?

Yes the error also occurred with the local installation in node_modules/.bin/standard running from the command line.
The issue was apparently that we had an old version of standard installed, because yarn did not correctly update the dependencies. A related issue is https://github.com/standard/snazzy/issues/16
Thanks for the fast response and the heads up and sorry for the delayed answer.
TL;DR;
We rm -rf node_modules/ and reinstall with yarn install or npm install.


[MySQL] Unknown column 'prefix' in 'field list'

Hello,
I've tried to fix this error for 2 hours.
I want to transfer the .sql files from my old mysql server to my new one.
My console gets spammend with the following message:
http://hastebin.com/elesehexap.pas
I've already changed "schema_version" from value 1 to 2.
My MySQL version:

mysql  Ver 14.14 Distrib 5.5.44, for debian-linux-gnu (x86_64) using readline 6.3

PermissionsEx version which I'm using:

PermissionsEx v1.23.3

Is there maybe a way to fix that?

#SOLVED
(MySQL files were broken.)


Create Remove functionality for Providers

Is there an existing issue for this?

[X] I have searched the existing issues

Current behavior
Currently CLI is providing it's first provider which as @expressots/prisma or prisma provider. Prisma provider is added using the CLI command:
expressots add prisma

We need to add a command to remove the provider and undo all it's installation changes. Example:
expressots remove prisma

During the installation prisma does:

Install prisma client
Install prisma
Install @expressots/prisma
Install driver
Install repository pattern
Create a prisma folder
Add prisma folder location to the package.sjon
Add prisma provider configuration in the expressots.config.ts
Add prisma command in package.json to generate prisma models

Steps to reproduce
expressots add prisma
Expected behavior
Remove all components below:

Install prisma client
Install prisma
Install @expressots/prisma
Install driver
Install repository pattern
Create a prisma folder
Add prisma folder location to the package.sjon
Add prisma provider configuration in the expressots.config.ts
Add prisma command in package.json to generate prisma models

Package version
@expressots/cli 1.5.0
Node.js version
18
In which operating systems have you tested?

[X] macOS
[X] Windows
[X] Linux

Other
No response

Done in the v3.0.0


Chain extension: unit tests

This PR:

increases testability of SnarcosChainExtension through abstracting away Environment and Runtime,
introduces a suite of 15 unit tests for SnarcosChainExtension that ensure correct charging, arguments reading and error passing

There is (at least) one controversial thing here - unstable feature of additional constant generics. It was introduced because all the main calls (pallet_snarcos::(store_key|verify)) are invoked as static methods of Runtime. Therefore, it makes testing different behaviors highly inconvenient (since we cannot change the mock behavior depending on any variable). Being able to introduce enums into generics gives us the possibility of concise defining scenarios.

I guess that we are looking forward to see https://github.com/rust-lang/rust/issues/95174 stabilized soon...


import files breaks folder hierarchy

as in the title
After importing the root folder, I have all my files "flat" on the website

Right, so you imported a set of files and folders, and all the files inside the folders were pulled out?

i selected all files/folders from the root folder and it has been flatten.
When I did it folder by folder, no problem. The website works here :
dat://426c383f2968f5b97d61573c75f06529a4c77186d5b37f6c5095a00488574bdd/
2018-03-19 14:45 GMT+01:00 Paul Frazee<EMAIL_ADDRESS>
Right, so you imported a set of files and folders, and all the files
inside the folders were pulled out?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/beakerbrowser/beaker/issues/897#issuecomment-374216343,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACazsD32CM3Fh9aP9MsiuRrvT1dIszVQks5tf7ZkgaJpZM4Sv8zm
.

Yeah, ok we'll get that fixed.

What operating system are you using?

Yeah I'm having trouble reproducing this issue. Can you describe it in full detail for me? What tool you're using, what you expect to happen, etc? A recording would be useful.

Mac os high Sierra
Select all files from a directory
Le ven. 23 mars 2018 à 23:38, Paul Frazee<EMAIL_ADDRESS>a
écrit :

Yeah I'm having trouble reproducing this issue. Can you describe it in
full detail for me? What tool you're using, what you expect to happen, etc?
A recording would be useful.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/beakerbrowser/beaker/issues/897#issuecomment-375816598,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACazsDEVCU1cPxraxrKR232JqO4Z9-iXks5thXmCgaJpZM4Sv8zm
.

Yeah I tried that and couldn't reproduce it, so I need more information. Can you step me through the entire process, from starting beaker to the end?

It is what I did. If you could not reproduce it. You can close it. No
worries
Le sam. 24 mars 2018 à 16:57, Paul Frazee<EMAIL_ADDRESS>a
écrit :

Yeah I tried that and couldn't reproduce it, so I need more information.
Can you step me through the entire process, from starting beaker to the end?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/beakerbrowser/beaker/issues/897#issuecomment-375901697,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACazsBd_QBTVny_fGybBFuN_TKwxPCGxks5thmzzgaJpZM4Sv8zm
.

I'm just trying to make sure I understand the issue. We have multiple file-importing tools, and I may be testing the wrong one.

It is through the bearer browser file uploader
Le sam. 24 mars 2018 à 22:29, Paul Frazee<EMAIL_ADDRESS>a
écrit :

I'm just trying to make sure I understand the issue. We have multiple
file-importing tools, and I may be testing the wrong one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/beakerbrowser/beaker/issues/897#issuecomment-375926219,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACazsE4PEo8fiDpFOUQflQrKl0DtL8sjks5thrq-gaJpZM4Sv8zm
.


version attribute not accessible

The version attribute doesn't appear to be part of the module. The issue happens with the following code:
import ipywidgets
ipywidgets.version
Result is:
AttributeError: 'module' object has no attribute 'version'
Anaconda environment:
ipython                   4.0.0                    py27_0
ipywidgets                4.0.2                    py27_0
I believe the version attribute should be there and that this is some sort of bug.

To add a bit more clarity, ipywidgets.__version__ was added by #147, but ipywidgets.version does not exist. (And if you don't escape __version__ markdown makes it look like version)

So this is closed by #147?

This should be closed by  #147 .
What confused me was that the version in _version.py on master is still 4.0.2. This is the version I have installed and it doesn't include the fix. I am not sure about the versioning conventions in ipywidgets, but once a version is released the version number on master should probably be modified?


jQuery mouse movement demo

e.g. http://www.felixandpaul.com/?projects/lebron

we're going with css animation across the board.

http://www.onextrapixel.com/2014/04/09/create-an-interactive-moving-backgroundobject-that-reacts-to-viewers-cursor/


build_runner [INFO]: Found 2 constructors for class ...; using constructor .

After that updated to angular 5.0.0-alpha+10 and Dart 2.0.0-dev.47.0 (run on Windows), when pub run build_runner serve is ran, the following message is presented Found 2 constructors for class ANYCLASS; using constructor .. See examples:

[INFO] angular on package:angular_components/material_input/material_number_accessor.dart:Found 2 constructors for class MaterialNumberValueAccessor; using constructor .
[INFO] angular on package:angular_components/material_input/material_auto_suggest_input.dart:Found 2 constructors for class MaterialAutoSuggestInputComponent; using constructor .
[INFO] angular on package:angular_components/material_menu/material_fab_menu.dart:Found 2 constructors for class MenuItemGroupsComponent; using constructor .

Thanks for filing. This was unintentional and it's fixed at HEAD (and in the next release).


AsyncProducer Close blocked for infinity

Versions
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.

Sarama
Kafka
Go

1.27.2
3.0.0
1.7.5

Configuration
What configuration values are you using for Sarama and Kafka?

	config.Metadata.Retry.Max = 3
	config.Metadata.Retry.Backoff = 250 * time.Millisecond
	config.Metadata.Timeout = 1 * time.Minute

	// Admin.Retry take effect on `ClusterAdmin` related operations,
	// only `CreateTopic` for cdc now. Just use default values.
	config.Admin.Retry.Max = 5
	config.Admin.Retry.Backoff = 100 * time.Millisecond
	config.Admin.Timeout = 3 * time.Second

	config.Producer.Retry.Max = 3
	config.Producer.Retry.Backoff = 100 * time.Millisecond

	config.Producer.Partitioner = sarama.NewManualPartitioner
	config.Producer.MaxMessageBytes = c.MaxMessageBytes
	config.Producer.Return.Successes = true
	config.Producer.Return.Errors = true
	config.Producer.RequiredAcks = sarama.WaitForAll

Logs
We are testing sarama in an extremely rare scenario:

producer can send request to the 1 machine Kafka cluster, but cannot get a response
Kill -s STOP the kafka broker process, this will make the TCP connection remain, but will not send a response.
Close the producer by call asyncProducer.Close()

we do not have a log from sarama, but have grabbed some goroutine stack, like the following one, it looks blocked on trying to receive a response from the broker.

Our purpose is that when try to close the producer, it should not be blocked for a long time, instead of return as soon as possible.

But the reality as shown in the picture above, 33 messages failed to deliver after 38minutes, and it was after the process resume by kill -s CONT
Problem Description

Our service need Success and Errors enabled, since we have to track message flushed offset and errors.

I added some logs to customize the sarama, and there is some of the output:
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=1"] [name=sarama]
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=2"] [name=sarama]
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=3"] [name=sarama]
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=4"] [name=sarama]
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=5"] [name=sarama]
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=6"] [name=sarama]
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=7"] [name=sarama]
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=8"] [name=sarama]
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=9"] [name=sarama]
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=10"] [name=sarama]
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=11"] [name=sarama]
[2022/02/07 11:05:33.083 +08:00] [DEBUG] [async_producer.go:574] ["add new message to retryState, retries=0, len=12"] [name=sarama]
....

more than 100 messages like this, I think the mount of this log has relations with the mount of messages.
Later happens this kind of messages.
[2022/02/07 11:06:48.427 +08:00] [DEBUG] [async_producer.go:592] ["try to updateLeader"] [name=sarama]
[2022/02/07 11:06:48.427 +08:00] [DEBUG] [async_producer.go:594] ["update leader meet error, err=circuit breaker is open"] [name=sarama]
[2022/02/07 11:06:48.528 +08:00] [DEBUG] [async_producer.go:592] ["try to updateLeader"] [name=sarama]
[2022/02/07 11:06:48.528 +08:00] [DEBUG] [async_producer.go:594] ["update leader meet error, err=circuit breaker is open"] [name=sarama]
[2022/02/07 11:06:48.628 +08:00] [DEBUG] [async_producer.go:592] ["try to updateLeader"] [name=sarama]
[2022/02/07 11:06:48.628 +08:00] [DEBUG] [async_producer.go:594] ["update leader meet error, err=circuit breaker is open"] [name=sarama]
....

And finally
[2022/02/07 11:06:48.831 +08:00] [DEBUG] [async_producer.go:592] ["try to updateLeader"] [name=sarama]
[2022/02/07 11:06:48.831 +08:00] [DEBUG] [async_producer.go:594] ["update leader meet error, err=circuit breaker is open"] [name=sarama]
[2022/02/07 11:06:48.932 +08:00] [DEBUG] [async_producer.go:580] ["fin received, try flushRetryBuffers, highWatermark=1"] [name=sarama]
[2022/02/07 11:06:48.932 +08:00] [DEBUG] [async_producer.go:632] ["producer/leader/fuck-sarama/0 state change to [flushing-1]"] [name=sarama]
[2022/02/07 11:06:48.932 +08:00] [DEBUG] [async_producer.go:654] ["producer/leader/fuck-sarama/0 state change to [normal]"] [name=sarama]
[2022/02/07 11:06:48.932 +08:00] [DEBUG] [async_producer.go:1065] ["asyncProducer shutdown, inflight wait, elapsed=65.626644333"] [name=sarama]
[2022/02/07 11:06:48.932 +08:00] [DEBUG] [async_producer.go:1072] ["asyncProducer shutdown, client close elapsed = 4.58e-07"] [name=sarama]
[2022/02/07 11:06:48.932 +08:00] [ERROR] [kafka.go:236] ["close async client with error"] [error="kafka: Failed to deliver 802 messages."] [duration=1m15.637246541s] [changefeed=747ff99b-56d4-4c22-b20f-d3b515417baf] [role=processor]
[2022/02/07 11:06:48.932 +08:00] [DEBUG] [sync_producer.go:167] ["syncProducer close, elapsed = 7.92e-07"] [name=sarama]
[2022/02/07 11:06:48.932 +08:00] [DEBUG] [async_producer.go:1058] ["Producer shutting down."] [name=sarama]
[2022/02/07 11:06:48.932 +08:00] [DEBUG] [async_producer.go:1061] ["asyncProducer send `shutdown`, input size=0"] [name=sarama]
[2022/02/07 11:06:48.932 +08:00] [DEBUG] [async_producer.go:1065] ["asyncProducer shutdown, inflight wait, elapsed=9.17e-07"] [name=sarama]
[2022/02/07 11:06:48.932 +08:00] [DEBUG] [async_producer.go:1072] ["asyncProducer shutdown, client close elapsed = 4.1e-08"] [name=sarama]

I think the steps like this:

send a message to brokerProducer, but failed, so the brokerProducer will be closed.
try to updateLeader, by using the breaker
updateLeader will not succeed, since the broker is already dead. For each message in the retryState, it will try to do that, and finally cost a lot of time.
receive a fin message, finally shutdown.

How about add a timeout for the close, or ForceClose()

We've seen this deadlock repeatedly on several Kafka clusters as soon as we picked up v1.31.x, and we haven't seen it since we rolled out back our vendored deps to v1.30.1, so there is definitely a bug in the code, it's not a problem due to a dead broker (our brokers are fine).

FWIW this is affecting us too, an upgrade to 1.31 caused our producers to lock up. Downgrading to 1.30 resolved the issue

This seems like a dupe of https://github.com/Shopify/sarama/issues/2129, which is fixed in the latest main: https://github.com/Shopify/sarama/pull/2133

It still exists in 1.32 (which includes fix #2133).
Downgrading to 1.30.1 resolved the issue.
Thanks, @tsuna

We believe this issue is fixed in recent versions of Sarama. Feel free to re-open if you're still seeing a problem on the latest


cannot access node native modules

I'm trying to use this repo with electron.
It runs without a problem until I need use http module. When I do let http = require('http') it returns a partial object without most of the functions and I got http.createServer is not a function error. How can I fix this? Thanks.

Now I use target: "electron" and set:
node: {
        global: 'window',
        crypto: 'empty',
        fs: true,
        http: true,
        process: true,
        module: false,
        clearImmediate: false,
        setImmediate: false
    }

it throws new exception:
vendor.bundle.js:77976 Uncaught SyntaxError: Unexpected token :
main.bundle.js:2 Uncaught ReferenceError: exports is not defined

If I add DEBUG to process.env manually, the error becomes:
node.js:122Uncaught ReferenceError: Invalid left-hand side in assignment
main.bundle.js:2Uncaught ReferenceError: exports is not defined

Now I really don't know what to do ...

Hi @naivefun , I spent some hours to finally find a solution, in case you, or others are still searching:
Use target: 'electron-renderer' and thanks to https://github.com/visionmedia/debug/issues/301, change https://github.com/AngularClass/angular2-webpack-starter/blob/master/config/webpack.dev.js#L137 to:
'process.env.ENV': JSON.stringify(METADATA.ENV),
'process.env.NODE_ENV': JSON.stringify(METADATA.ENV),
'process.env.HMR': METADATA.HMR

Should we open a PR for this ? (it applies only if you want to use electron/node)

@G-Ray: Thanks for your help, but it did not fully solve this problem for me still getting the errors
node.js:143Uncaught ReferenceError: Invalid left-hand side in assignment
vendor.bundle.js:1Uncaught ReferenceError: exports is not defined(anonymous function)
main.bundle.js:2Uncaught ReferenceError: exports is not defined

My issue was only when importing electron like this:
import * as electron from 'electron';
Or
import { ipcRenderer } from 'electron';
To fix it i used the node require function like this:
import electron = require('electron');
And accesing to the ipcRenderer like this:
electron.ipcRenderer;


Post Install README not linked

After install in Firebase the link to post install instructions links to: https://github.com/typesense/firebase-typesense-search-extension/POSTINSTALL.md which returns a "Not Found" error.
edit: This is after setup and before the install completes. On install the in firebase postinstall docs are displayed.
During install Firebase links to github with the above "Not Found" url. Not sure if it's a firebase bug?

@kylewill Would you be able to share a screenshot of where you see this in the Firebase UI?

Sure - I had to reinstall to get there.
After setting up the configuration but before the first install completes there's a link here:

Thanks @kylewill, I've pushed out a fix for this.


[WIP] add conda environment for Perl into snakemake execution

Note, merge into https://github.com/nih-cfde/update-content-registry/pull/11.

@abradyIGS would be interested to know if this works for ya. Just try running make.

Building DAG of jobs...
CreateCondaEnvironmentException:
Your conda installation is not configured to use strict channel priorities. This is however crucial for having robust and correct environments (for details, see https://conda-forge.org/docs/user/tipsandtricks.html). Please configure strict priorities by executing 'conda config --set channel_priority strict'.
make: *** [all] Error 1

yes, is ok to run.

make ran okay, make update and subsequent rebuild command propagated successfully to dev website. i think you were updating at the same time and we clobbered each other, but once i was sure that had stopped, it worked fine.
note my base environment already has access to perl -- the conda flow did install the YML for the dependency and i assume it pointed itself to the right place, but i can't swear to it without dumping a bunch of debug logic that would prolly be overkill.

I don't have mamba installed so I'm getting this message:
snakemake -j 1 --use-conda
Error: mamba package manager is not available. The mamba package manager (https://github.com/mamba-org/mamba) is an extremely fast and robust conda replacement. It is the recommended way of using Snakemake's conda integration. It can be installed with `conda install -n base -c conda-forge mamba`. If you still prefer to use conda, you can enforce that by setting `--conda-frontend conda`.
make: *** [all] Error 1

mamba is not easy to install.... 20 min later still trying...
(content-reg) raynamharris@ip-192-168-0-14 update-content-registry % conda install -n base -c conda-forge mamba
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: \


Enable locally built Dependency to override system installed version of the dependency

What:
Customer has a requirement to support building a dependency using non-default parameters. However, while the dependency is building in the workspace the system version of that dependency overrides the local version.
Why:
Customer requires a precision version of bullet3, which is not currently the default build.

In C:\opt\ros\noetic\x64\etc\catkin\profile.d\vcpkg.bat the following line overrides local builds:
set "CMAKE_PREFIX_PATH=C:\opt\ros\noetic\x64\tools\vcpkg\installed\x64-windows;%CMAKE_PREFIX_PATH%"
Recommend changing to:
`set "CMAKE_PREFIX_PATH=%CMAKE_PREFIX_PATH%;C:\opt\ros\noetic\x64\tools\vcpkg\installed\x64-windows"
So that locally built dependencies are found first.

Another issue I have ran into is that it finds the GTest package but all the cmake variables are empty except GTEST_INCLUDE_DIRS. Variables GTEST_LIBRARIES and GTEST_MAIN_LIBRARIES are empty. This is the case on both linux and windows, but was only an issue when building windows.
find_package(GTest REQUIRED)

if(NOT TARGET GTest::GTest)
  add_library(GTest::GTest INTERFACE IMPORTED)
  set_target_properties(GTest::GTest PROPERTIES INTERFACE_INCLUDE_DIRECTORIES "${GTEST_INCLUDE_DIRS}")
  if (${GTEST_LIBRARIES})
    set_target_properties(GTest::GTest PROPERTIES INTERFACE_LINK_LIBRARIES "${GTEST_LIBRARIES}")
  else()
    if (MSVC)
      set_target_properties(GTest::GTest PROPERTIES INTERFACE_LINK_LIBRARIES "gtest.lib")
    else()
      set_target_properties(GTest::GTest PROPERTIES INTERFACE_LINK_LIBRARIES "libgtest.so")
    endif()
  endif()
endif()

if(NOT TARGET GTest::Main)
  add_library(GTest::Main INTERFACE IMPORTED)
  set_target_properties(GTest::Main PROPERTIES INTERFACE_INCLUDE_DIRECTORIES "${GTEST_INCLUDE_DIRS}")
  if (${GTEST_MAIN_LIBRARIES})
    set_target_properties(GTest::Main PROPERTIES INTERFACE_LINK_LIBRARIES "${GTEST_MAIN_LIBRARIES}")
  else()
    if (MSVC)
      set_target_properties(GTest::Main PROPERTIES INTERFACE_LINK_LIBRARIES "gtest_main.lib")
    else()
      set_target_properties(GTest::Main PROPERTIES INTERFACE_LINK_LIBRARIES "libgtest_main.so")
    endif()
  endif()
endif()

The other issue I have ran into is related having dependencies in my workspace that are also installed on the system. The interesting thing is that find_package finds the correct config but when building it is using the system version for headers and libraries unless I add the BEFORE shown below. This means that I am unable to leverage cmake targets because of this issue for packages that are in workspace and also installed on the system.
Before:
include_directories(${FCL_INCLUDE_DIRS})
link_directories(${FCL_LIBRARY_DIRS})

After:
include_directories(BEFORE ${FCL_INCLUDE_DIRS})
link_directories(BEFORE ${FCL_LIBRARY_DIRS})

The other issue I ran into which is not related to this issue but explained here. Oddly this issue was not present until I started building on Windows, and not sure why this was not an issues when I was building the same package on linux.

@ooeygui I am working on getting the motion planning packages to build and ran into an issue where OMPL has incorrect include path for Eigen. Not sure if this an error in how ompl generates the its Config or related to how they are packaged for windows. When building the ros package for windows do they get moved? If so then this will be a problem for OMPL because it hard code the path for its dependencies in omplConfig.cmake instead of leveraging cmake find_dependency.
OMPL INCLUDE DIRS: C:/opt/ros/noetic/x64/include;/include/eigen3

OMPL is built using vcpkg. In the ROS deployment, the config file C:\opt\ros\noetic\x64\share\ompl\omplConfig.cmake, has this entry: set(OMPL_INCLUDE_DIRS "${OMPL_INCLUDE_DIR};${_IMPORT_PREFIX}/include/eigen3;;")
I'm rebuilding ompl in vcpkg to see where that is coming in from.

@ooeygui I opened up a PR against OMPL to fix the missing libraries boost, flann, etc which they were not including.

@ooeygui The fix for ompl has been merged. What is the process for getting the fix included into the ros windows release?


Move BrickProvider from com.wayfair.brickkit.brick to com.wayfair.brickkit.viewholder.factory

Fixes https://github.com/wayfair/brickkit-android/issues/181

Codecov Report

Merging #182 (dcbd4bf) into dev (9938b50) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev     #182   +/-   ##
=========================================
  Coverage     87.52%   87.52%
  Complexity      323      323
=========================================
  Files            32       32
  Lines           938      938
  Branches        143      143
=========================================
  Hits            821      821
  Misses           59       59
  Partials         58       58

Impacted Files
Coverage Δ
Complexity Δ

...in/java/com/wayfair/brickkit/BrickDataManager.java
85.00% <ø> (ø)
142.00 <0.00> (ø)

...kit/viewholder/factory/BrickViewHolderFactory.java
80.00% <ø> (ø)
8.00 <0.00> (ø)

...viewholder/factory/BrickViewHolderFactoryData.java
81.81% <ø> (ø)
4.00 <0.00> (ø)

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 9938b50...dcbd4bf. Read the comment docs.

Codecov Report

Merging #182 (dcbd4bf) into dev (9938b50) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev     #182   +/-   ##
=========================================
  Coverage     87.52%   87.52%
  Complexity      323      323
=========================================
  Files            32       32
  Lines           938      938
  Branches        143      143
=========================================
  Hits            821      821
  Misses           59       59
  Partials         58       58

Impacted Files
Coverage Δ
Complexity Δ

...in/java/com/wayfair/brickkit/BrickDataManager.java
85.00% <ø> (ø)
142.00 <0.00> (ø)

...kit/viewholder/factory/BrickViewHolderFactory.java
80.00% <ø> (ø)
8.00 <0.00> (ø)

...viewholder/factory/BrickViewHolderFactoryData.java
81.81% <ø> (ø)
4.00 <0.00> (ø)

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 9938b50...dcbd4bf. Read the comment docs.


debugInfoEnabled breaking dragNdrop functionality

We were using btf-dragon for dragNdrop functionality. Upgrading to 1.3  and adding...
.config(($compileProvider) ->
  $compileProvider.debugInfoEnabled debugInfoEnabled
)

... to our app,  killed the dragon. We are now using Sortable, but the problem remains. Disabling debugInfo stops reporting on DOM elements, but dragNdrop functionality depends on reporting from DOM elements.
If it helps, my colleague has a more specific use case issue.
I was hoping you might have some thoughts.
Thanks

This is probably because debugInfoEnabled = false does not attach the scope to elements, and that means also the functions scope() and isolateScope() do not work anymore. This is imo a wontfix - either btf-dragon needs to be rewritten to not rely on scope attachments or you cannot disable debugInfo

This is a wontfix. There are two options, keep the debug info or ask the btf-dragon owner not to use element.scope() and element.isolatedScope()


ENH Fix kernels that wasted overhead compute on out-of-bounds memory

On main branch currently, if the size of the window over centroids does not divide the size of the array of centroids, windows on the edge are filled with zeros, but compute still takes place for those zeros, In unlucky setups (e.g small number of dimensions and/or clusters, and increased size of window) most of the time can be spent there. The fix consists in exiting the loops over elements of the window so that no compute is performed over the extra zero padding.

So I just discovered that "Pending" on a comment means you can't see it :facepalm: including some that I thought were readable the past few days

@ogrisel about loop unrolling there are some more insights given on https://github.com/IntelPython/numba-dpex/issues/770

I've merged the factory classes into one class, and also applied to kmeans++ that just got merged.

TY for review, I'll go ahead and merge so the depending pr can move on now
(tests on master expected to fail as long as https://github.com/soda-inria/sklearn-numba-dpex/actions/runs/3495827078/jobs/5853027401 is pending, will trigger manually afterward)


Added accessibility criteria and remove unused parts

What was done

[x] Add accessibility criteria to PR template
[x] Remove unused # symbol
[x] Remove unused dev and approval branch sections

I like it!


Upcoming Release

:tada: This PR is included in version 2.6.6-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.6.6-rc.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


client: support create with context

Signed-off-by: disksing<EMAIL_ADDRESS>What problem does this PR solve?
Cherry-pick #1993
What is changed and how it works?
add NewClientWithContext
Check List
Tests

Unit test

Related changes

Need to be included in the release notes

/run-all-tests

Codecov Report

Merging #1994 into release-3.0 will increase coverage by 0.2%.
The diff coverage is 90%.

@@              Coverage Diff               @@
##           release-3.0    #1994     +/-   ##
==============================================
+ Coverage        69.32%   69.52%   +0.2%
==============================================
  Files              170      170
  Lines            16757    16764      +7
==============================================
+ Hits             11616    11655     +39
+ Misses            4157     4136     -21
+ Partials           984      973     -11

Impacted Files
Coverage Δ

client/client.go
73.81% <90%> (+2.57%)
:arrow_up:

server/schedulers/random_merge.go
62.5% <0%> (-5%)
:arrow_down:

server/namespace_cluster.go
81.81% <0%> (-3.9%)
:arrow_down:

server/cluster.go
81.72% <0%> (-0.51%)
:arrow_down:

server/handler.go
52.11% <0%> (+0.49%)
:arrow_up:

server/grpc_service.go
59.27% <0%> (+0.63%)
:arrow_up:

server/tso.go
76.59% <0%> (+2.12%)
:arrow_up:

server/leader.go
82.04% <0%> (+2.85%)
:arrow_up:

server/util.go
75.15% <0%> (+7%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

/merge


Consider moving code coverage to Code Climate

Code Climate is already used for tracking maintainability. The service also supports tracking code coverage. Either move the coverage report there or add it there without removing it from Codecov.

Code coverage is now also uploaded to Code Climate.
1a1634f1cf23bc905679ed4cf129dc803c234b3f


Next.js split chunks server side

Can Next.js emit split chunks for server side code? Does this provide any meaningful boost to the build speed?
We need to measure and test this theory.

/subscribe - also interested in this. Could avoid ever loading cold codepaths.

This issue has been automatically closed because it wasn't verified against next@canary. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you.


Fix #933 by adjusting the internals of smart rate limiter

This pull request resolves #933 by improving the internals of API clients' smart rate limiter. The key changes are:

Changed the interval of the background job from 50 milliseconds to 1,000 milliseconds (verified that there is almost zero downsize by changing this)
Enabled the maintenance job to skip updating metrics data if a team_id does not have any updates since the previous maintenance
Changed to disable the background thread If the statsEnabled is false
Added traceMode to the background job for easier debugging on the SDK maintainer side (disabled by default)

Category (place an x in each of the [ ])

[ ] bolt (Bolt for Java)
[ ] bolt-{sub modules} (Bolt for Java - optional modules)
[x] slack-api-client (Slack API Clients)
[ ] slack-api-model (Slack API Data Models)
[ ] slack-api-*-kotlin-extension (Kotlin Extensions for Slack API Clients)
[ ] slack-app-backend (The primitive layer of Bolt for Java)

Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to the those rules.

This should be good to go now. Let me merge this PR and release a new version including the fix.


fix: retention-period to be 1 day

tl;dr;
upload and download used for passing build artifact between current job. Therefore there are no reason to keep then default period, 90 days, but could be shorten.

important!


How to use with Private NPM Distribution?

First off, TSDX is great. Thank you all for open sourcing this.
I am building a React component library that needs to be published on a private Nexus NPM repo rather than actual NPM. So I need to be able to generate the tarball but push to a dedicated location besides NPM.
How can I configure TSDX to do this?

I think you can just add a script after build to zip the dist directory?

Oh so just a yarn pack after build? Sounds good to me. Thanks.

@neilchaudhuri TSDX does not currently touch your publish process at all, so this question is out-of-scope. I would recommend searching your question online because there are plenty of results, even plenty Nexus-specific -- here is one.
You don't need to generate a tarball and send it to some API, you can just set your publishConfig.registry in package.json as well as create an .npmrc so that you publish to a different registry. Nexus supports this format.

I appreciate the feedback. Thanks.

I've the same issue, I can't publish in private repository, when I run npm publish comand igone my private repository config and  try to publish my package on npm


onContentProcessDidTerminate not called in newer versions of react-native-webview + react-native

Thanks for making this library, here is my first bug report
Bug description:
I recently upgraded some of our packages, and noticed that the callback given to onContentProcessDidTerminate was no longer being called.  However, react-native-webview was detecting that the webview had terminated.  We use this callback to reload the webview if it is terminated due to OS memory constraints.
To Reproduce:

Create a fresh react-native project following instructions:
https://reactnative.dev/docs/environment-setup
i.e.

npx react-native init AwesomeProject

Install react-native-webview via npm + update pods

Import into App.js WebView

import { WebView } from 'react-native-webview';

Replace App.js rendering code with:

  return (
    <SafeAreaView style={{ flex: 1 }}>
          <WebView
          source={{ uri: 'https://google.com' }}
          onContentProcessDidTerminate={(event)=>{console.log("END OF A WEBVIEW!")}}
        />
    </SafeAreaView>
  );

Run on device from xcode as per:
https://reactnative.dev/docs/running-on-device

Trigger webViewWebContentProcessDidTerminate.  For example, by opening and refreshing many high-memory websites in Safari.
(If anyone knows of an easier and more reliable way to trigger this please let me know)

Result: No console message "END OF A WEBVIEW!"
Expected behavior:
onContentProcessDidTerminate, as provided in the react component property, is called.
Environments:
This occurs for me on:
node version: 16.15.1
react-native: 0.67.1
react-native-webview: 11.22.3
node version: 18.4.0
react-native: 0.69.0
react-native-webview: 11.22.3
node version: 16.15.1
react-native: 0.68.2
react-native-webview: 11.22.2
All using on-device development build + run from xcode:
xcode: 13.4.1
ios: 15.5
device: ipad 6th generation MR7J2B/A
The lack of auto-restart of the webview was also reported by users of our main app via test flight.
The issue does NOT occur for the following configuration (it runs successfully):
node version: 16.15.1
react-native: 0.67.1
react-native-webview: 11.6.4
Further investigations:
Further investigation proceeded with the following 'hack':
Adding the onScroll callback to the WebView component as follows in App.js
          onScroll={(event)=>{console.log("SCROLL!")}}

Then modifying node_modules/react-native-webview/apple/RNCWebView.m such that we disable the _onScroll(event); event at line 882 in the scrollViewDidScroll method.  And finally add the _onScroll(event); back in after _onContentProcessDidTerminate(event); on line 1186 in webViewWebContentProcessDidTerminate.
In this case, the onScroll callback fired on termination but still not onContentProcessDidTerminate.  This demonstrates that the _onContentProcessDidTerminate method exists (confirmed by the. debugger) and that the event can flow into the react-native component via onScroll, but not for onContentProcessDidTerminate!
Request:
My current thoughts are that this is something to do with react-native's upgrade limiting the props that can be called from the C function.
I would appreciate if anyone else can confirm they are experiencing this issue.  I'm not at all well versed in C or how react-native interacts with the C functions, so any suggestions on that front would be greatly appreciated.
For now we plan to downgrade react-native-webview to version 11.13.0

Thanks for the report! @Titozzz This looks to me like another regression from the recent refactor? Seems like useWebWiewLogic is expecting an onContentProcessDidTerminateProp that isn't being provided.

I'm anxiously awaiting this fix 🙏🏻

same here!

I've taken a look at the code and think I see the problem now so I am happy to give fixing this a go.

https://github.com/react-native-webview/react-native-webview/blob/a0f1e2641a733777e124e8396ee3b86ec4f3deb8/src/WebView.ios.tsx#L107
const { onLoadingStart, onShouldStartLoadWithRequest, onMessage, viewState, setViewState, lastErrorEvent, onHttpError, onLoadingError, onLoadingFinish, onLoadingProgress, onContentProcessDidTerminate } = useWebWiewLogic({
 ...
 onContentProcessDidTerminateProp: otherProps?.onContentProcessDidTerminate,
});

???

When is this going to be fixed?

@cblaze22 This was fixed well over a year ago.


Support Environment credential for Azure identity - ref. original #14544

Is your feature request related to a problem? Please describe.
Just opening to get an update on known issue in #14544
Describe the solution you'd like
We heard late last year that this was being implemented and moving into identity, but we have not heard anything further.  Can we get an update on this since it deals with automation and the potential to make a credential visible via the process table?
Additional context
All previous info should be in the prior issue here that was closed without clear path / updates:  https://github.com/Azure/azure-cli/issues/14544
This is also affecting implementations of GitHub Actions that provide for az cli / az login actions such as this one:  https://github.com/Azure/login/issues/27

@jiasli for awareness


Added brainfuck Hello world Program

Added a "Hello World!" program written in Brainfuck to complete the list of languages supported. This program prints "Hello World!" using Brainfuck's easy and minimalist commands.

Thanks for your contribution! @Sushant696


[BEAM-8639][BEAM-8774] Update Kafka dependencies

Update Kafka dependency from 1.0.0 to 2.6.0, Kafka clients from 1.0.0 to 2.4.1
Add tests for previous compatible versions
Add possibility to use testcontainers in the IT test suite

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @methodmissing Could I ask you for review? I removed the code enforcing kafka  clients 2.1.0 version since it's now 2.6.0 by default. I'm not sure whether I'm not missing something though.

Run Python PreCommit

Run Java KafkaIO Performance Test

I have a branch in progress to run the io/kafka tests with more kafka-client versions in https://github.com/apache/beam/compare/master...methodmissing:kafkaio-test-more-versions but haven't had a window to converge on that, but can prioritise otherwise.
Related, but forcing a newer kafka-clients version, I think that'll mostly invalidate ConsumerSpEL and ProducerSpEL as well.
@lukecwik thoughts on the implications of bumping default kafka-clients up from 1.0.0 to 2.4.1 in 1 fell swoop? It's runtime pluggable, at Shopify we already use 2.4.1 for a long time and moving towards 2.6.0 for Beam but I worry about backwards compatibility. Also admittedly biased because https://github.com/apache/beam/pull/12794 would have been way less complex to implement and users of 1.0.0 in the wild is setting themselves up for other problems moving forward too 🤷♂ :smile:
cc @sap1ens @vvuibert

I have a branch in progress to run the io/kafka tests with more kafka-client versions in master...methodmissing:kafkaio-test-more-versions but haven't had a window to converge on that, but can prioritise otherwise.
Related, but forcing a newer kafka-clients version, I think that'll mostly invalidate ConsumerSpEL and ProducerSpEL as well.
@lukecwik thoughts on the implications of bumping default kafka-clients up from 1.0.0 to 2.4.1 in 1 fell swoop? It's runtime pluggable, at Shopify we already use 2.4.1 for a long time and moving towards 2.6.0 for Beam but I worry about backwards compatibility. Also admittedly biased because #12794 would have been way less complex to implement and users of 1.0.0 in the wild is setting themselves up for other problems moving forward too 🤷♂ 😄
cc @sap1ens @vvuibert

The purpose of supporting multiple versions is to have greater flexibility for users so the change in #12794 would have been equally complex I believe.
Typically I would lean to allowing this because we typically do perform dependency updates regularly but we have had issues in the past with some libraries like Avro and since we were already doing something special here likely means that it is important to the user community. Its best to ask on<EMAIL_ADDRESS>for feedback on this change (@aromanenko-dev and @iemejia should know more about this).

Just two cents about Kafka compatibility, it's been working extremely well since 0.10.2 (this is a good overview about the design), so I believe the proposed upgrade here should be very straightforward.

I'll just metion one issue I ran into, poll can now throw RebalanceInProgressException that must be handled: https://kafka.apache.org/26/javadoc/org/apache/kafka/common/errors/RebalanceInProgressException.html.
This applies only to cases when consumer group id used, we don't use it by default, but when user specifies it, the handling probably should be added. This change was introduced in KIP https://cwiki.apache.org/confluence/display/KAFKA/KIP-429%3A+Kafka+Consumer+Incremental+Rebalance+Protocol

This is quite significant change since Beam tended to support most of the Kafka client versions almost from the beginning. I believe that there is still a decent amount of users that uses Beam with quite old Kafka client versions [1]. So, before making a final decision, I propose to do a survey on<EMAIL_ADDRESS>and see the results.

I've created a survey on the users mailing list but it was probably not accepted.

@piotr-szuberski What do you mean by "it was not accepted"? I can see you email "[DISCUSS] Update Kafka dependencies in Beam Java SDK" from Oct 22nd on user@

@piotr-szuberski What do you mean by "it was not accepted"? I can see you email "[DISCUSS] Update Kafka dependencies in Beam Java SDK" from Oct 22nd on user@

I just wasn't subscribed to user@ mailing list before and the thread was disappearing without any message.

Run Java KafkaIO Performance Test

Run Java KafkaIO Performance Test

Run Java PostCommit

Run Java KafkaIO Performance Test

Run Java PostCommit

Run Java KafkaIO Performance Test

Run Java KafkaIO Performance Test

Run Java PostCommit

Run Java PostCommit

Run Java PreCommit

Run Java_Examples_Dataflow PreCommit

@aromanenko-dev @iemejia Kafka previous versions tests (including IT) are now running in Java Postcommit - is this solution acceptable?

@piotr-szuberski Thanks, sorry for delay with answer, I'll take a look asap

Run Java KafkaIO Performance Test

Run Java PreCommit

Run Java_Examples_Dataflow PreCommit

Run Java PostCommit

Run Java PostCommit

Run Java KafkaIO Performance Test

Run Java KafkaIO Performance Test

Run Java KafkaIO Performance Test

Run Java PostCommit

Run Java KafkaIO Performance Test

Run Java PostCommit

Run Java KafkaIO Performance Test

Run Java PostCommit

Run Java PreCommit

For some reason the printed versions are correct when run locally and on Jenkins it's always INFO: Running test for Kafka version <IP_ADDRESS>.. I'll add some better asserion to IT tests and try to figure out what's going on. Maybe Gradle runs everything in parallel and overwrites the previous kafka clients jar versions?

Run Java PostCommit

Run Java PostCommit

Run Java PostCommit

@aromanenko-dev Ok, despite printing all the time the same version it looks like it's working. I tried to put Kafka 0.9 among the Kafka versions and it indeed failed (still printing 0.11.3).
So I removed the version printing and added a new test to the IT that verifies that the version from AppInfoParser is the same as in the kafka versions map.

Run Java_Examples_Dataflow PreCommit

@piotr-szuberski Actually, I proposed to print out the Kafka client version because now here we can see the list of the executed tests but if some of them failed, we can't say for sure which Kafka version were used. Do I miss something?

Run Java PostCommit

@piotr-szuberski Actually, I proposed to print out the Kafka client version because now here we can see the list of the executed tests but if some of them failed, we can't say for sure which Kafka version were used. Do I miss something?

You're right about it, I've tried to print some logs from the tests but they are not visible on Jenkins.
I'll try to add some gradle-level error logs. It looks like printing "info" logs is not sufficient because postcommit task doesn't have '--info' switch.

Run Java PostCommit

Run Java PostCommit

Run Java PostCommit

@aromanenko-dev Ok I'm out of ideas.
Jenkins takes **/build/test-results/**.xml files to print the result of executed tests.
All of the kafka versions tests are the same (KafkaIOIT, KafkaIOTest), so they override each other in the test result dashboard.
I tried to rename these xml files but it looks like Jenkins cares about the info inside them.
So there seems to be no simple way to just print the version for each test execution.
Maybe it's sufficient to just know that some Kafka version is broken and run the tests locally? They don't take much time and everything is printed nicely when run on a local machine.

@piotr-szuberski It seems a bit odd but I don't think it's a blocker for this PR. In any case, we have a Kafka version in the gradle task name. So if it fails then the corresponding task will fail too, right? And we can see that in Jenkins job logs, like here.
So, in general it LGTM. Do you have something to add to this PR? Otherwise, we can merge that I think.

@chamikaramj @boyuanzz I guess you can be interested in this PR too.

Run Java PostCommit

@piotr-szuberski It seems a bit odd but I don't think it's a blocker for this PR. In any case, we have a Kafka version in the gradle task name. So if it fails then the corresponding task will fail too, right? And we can see that in Jenkins job logs, like here.

Yes, exactly like here:
00:18:25 Execution failed for task ':sdks:java:io:kafka:kafkaVersion090BatchIT'.

So, in general it LGTM. Do you have something to add to this PR? Otherwise, please undraft it to make it possible to merge.

Great! I've made some cleanup and removed the xml renaming part. When it's green then it's ready for merge

Run Java_Examples_Dataflow PreCommit

@aromanenko-dev From my side it's ready to merge.

@piotr-szuberski @aromanenko-dev @iemejia
This broke the Spark postcommit: BEAM-11375
It looks like the cause is the mismatch between kafka_2.11 (2.4.1) and kafka-clients (2.6.0). Kafka 2.5.0 deprecated support for Scala 2.11, so I'm guessing we can't bring it up to date until upgrading Spark to Scala 2.12?

@piotr-szuberski @aromanenko-dev @iemejia
This broke the Spark postcommit: BEAM-11375
It looks like the cause is the mismatch between kafka_2.11 (2.4.1) and kafka-clients (2.6.0). Kafka 2.5.0 deprecated support for Scala 2.11, so I'm guessing we can't bring it up to date until upgrading Spark to Scala 2.12?

Sorry for that, I didn't take it into account. I'll try to either update the scala version of Kafka dependency or downgrade kafka clients to 2.4.1


[Plugin] No events on begin/end of compiling entry points

Hi,
I'm creating a custom plugin and I need to know the begin/end event of every entry point as I should change the plugin's configuration depending on a specific entry point.
Reading through the docs, I can't find that event.
Thanks,
Jakob

Can you go a bit into detail?
As in, as far as I understand, you want to change your plugin’s config per-entrypoint, right? If so, then the this-compilation event is what you need. That is used per entry.

Thank you, yeah, that's exactly what I need. Let me try that and get back to you.

I'm listening on this-compilation. It's getting called once, but I have 2 entrypoints. This is my code:
entry: {
   textX: legacyStylesShared.concat(styles),
   textY: styles,
 },

Plugin config:
compiler.plugin("this-compilation", function(compilation) {
       console.log("xxx");
       compilation.plugin("normal-module-loader", function(loaderContext, module) {
           console.log("yyy");
       });
   });

I don't know what you try to do, but I'm pretty sure it doesn't work that way.
Instead you should use multiple compilation:
[
  { entry: "a", plugins: [ new YourPlugin("a") ] },
  { entry: "b", plugins: [ new YourPlugin("b") ] }
]

I had only 1 compilation object. This will be helpful. Thank you for your help!


Hyper Parameter Search

Construct a HP search. The most important parameters being
num_transforms, and scheduler parameters.
It would be nice to simplify our scheduler such that it takes less parameters

this is already being done. closing.


Adding a Payment to a Closed/Lost Opportunity lands user on "Record Deleted" error page

Steps to reproduce:

Create a new Opportunity with Amount = 1, Stage = Closed Lost.
From Opportunity detail page, scroll to Payments related list and click "New Payment"
Create new Payment with Amount = 1, Paid = unchecked.
Click Save

Expected result:
A new, related, unpaid payment will be created.
Actual result:
User is navigated to error page: "Record Deleted: The record you attempted to access has been deleted. The user who deleted this record may be able to recover it from the Recycle Bin. Deleted data is stored in the Recycle Bin for 15 days."

We're too clever for our own good. I'll bet our code is seeing the closed oppty and deleting the payment in the after trigger, redirecting us back to the newly created, yet now deleted, payment record.

**lurch: add

Tracking W-008738

Included in beta release 3.111 (Beta 1)

Included in production release rel/3.111


Why are capacities defined for electric heatpumps?

In this LES the technologies tab shows 2 kWh buffersize for the three water heating buffers and 1.5 kWh for space heating. This is correct, I set these values.
I noticed that there is also a storage defined for the heating technologies (heat pump air). The size is 81 kWh for Heat pump for hot water (air) and 174 kWh for Heat pump for space heating (air). (This size does not change when I adjust the buffer size of the corresponding buffer)
This is the only technology that has a storage volume defined.
Is there a reason for this? I would say storage volume for the technology should be NaN.

Notifying @AlexanderWirtz
Assigning @grdw, please reassign if appropriate

In this LES the [...]

Is this the correct LES? If so, I think it has been edited since the screenshot and the heat pumps have been replaced with HHPs. Therefore I can't tell if it's a (weird) display issue, or if those volumes are actually being saved with the technology data.
I cloned the LES, added a heat pump and messed around with the attributes for the pump and the parent buffer, but I can't seem to reproduce this. Do you remember editing the LES in some way before you noticed this problem?

I'm sorry, I linked to the wrong LES. This LES (ID 949) has electric heatpumps and shows the storage volume for the heatpumps.
I now notice the values are also shown in the csv in the CSV of this LES.

Do you remember editing the LES in some way before you noticed this problem?
I did make changes to the LES, I'm not sure which and what cause the error.

Other LESses with heat pump air like this one do not show storage volume for the heatpumps.
I propose that if you can't find what's wrong with LES 949 I close this issue for the time being and reopen when the issue occurs again.

This doesn't appear to be a problem for newly-created LESes; this scenario may be a clone from a one created before we had shared buffers, or the problem has been fixed. The value shown won't have any effect on the calculation of the LES as the shared buffer will be used instead.
If it's annoying, we can remove the values manually from any affected scenario.
I'll close this; please reopen if you find this happens again.


[MQTT Agent] : MqttAgent Init and Resume Session Unit Tests

Looking at the coverage report, it looks like coverage is missing for when the following conditions are evaluated as false:
https://github.com/FreeRTOS/coreMQTT-Agent/blob/1d6c07a77e8ad98e08417dac573ff1cbd30fb30d/source/mqtt_agent.c#L744
https://github.com/FreeRTOS/coreMQTT-Agent/blob/1d6c07a77e8ad98e08417dac573ff1cbd30fb30d/source/mqtt_agent.c#L783
If we're not adding them in this PR, we should make a note of it, though it might make sense to add them now since MQTTAgent_ResumeSession() is the only function to use those functions

Approving, but I'd prefer if we get 100% branch coverage for the 2 cases noted above

Included the coverage for he 2 cases above.


error: bundling failed: Error: While resolving module react-native-vector-icons/FontAwesome

If you're getting the following error:

error: bundling failed: Error: While resolving module react-native-vector-icons/FontAwesome, the Haste package react-native-vector-icons was found. However the module FontAwesome could not be found within the package. Indeed, none of these files exist:

the following command should fix it:
rm ./node_modules/react-native/local-cli/core/__fixtures__/files/package.json
Source: https://github.com/oblador/react-native-vector-icons/issues/626

It's an RN issue https://github.com/facebook/react-native/issues/17610
Will be fixed by https://github.com/facebook/react-native/pull/17672
Workaround https://github.com/oblador/react-native-vector-icons/issues/626#issuecomment-362386341

import  {Ionicons} from '@expo/vector-icons'
this might help


Distinguish between queries and query options by using ()

Based on an internal Slack message:

Related PR for groupBy: https://github.com/prisma/docs/pull/5668

Strategy to make this simpler:

Replace existing correct usages with lalala( (by replacing e.g. findUnique( with that string)
Turn on case matching in searches to not match for link anchors
Go through all the occurrences
Undo the lalala( change