Errors on HA startup in beta 2021.4x

On HA 2021.4.x beta seeing multiple errors on startup.
The Integration works without issues, just for info.
2021-04-04 10:57:26 ERROR (SyncWorker_1) [mopidyapi.client] Could not decode json from Mopidy: Expecting value: line 1 column 1 (char 0)
--- Logging error ---
Traceback (most recent call last):
  File "/srv/ha/lib/python3.8/site-packages/mopidyapi/client.py", line 77, in rpc_call
    r = post(self.http_url,
  File "/srv/ha/lib/python3.8/site-packages/requests/models.py", line 900, in json
    return complexjson.loads(self.text, **kwargs)
  File "/usr/lib/python3.8/json/__init__.py", line 357, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.8/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.8/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/homeassi/.homeassistant/custom_components/mopidy/config_flow.py", line 102, in async_step_zeroconf
    await self.hass.async_add_executor_job(
  File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/homeassi/.homeassistant/custom_components/mopidy/config_flow.py", line 24, in _validate_input
    client.rpc_call("core.get_version")
  File "/srv/ha/lib/python3.8/site-packages/mopidyapi/client.py", line 100, in rpc_call
    raise ConnectionError(ex)
requests.exceptions.ConnectionError: Expecting value: line 1 column 1 (char 0)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.8/logging/handlers.py", line 1401, in emit
    self.enqueue(self.prepare(record))
  File "/usr/lib/python3.8/logging/handlers.py", line 1384, in prepare
    msg = self.format(record)
  File "/usr/lib/python3.8/logging/__init__.py", line 925, in format
    return fmt.format(record)
  File "/usr/lib/python3.8/logging/__init__.py", line 664, in format
    record.message = record.getMessage()
  File "/usr/lib/python3.8/logging/__init__.py", line 369, in getMessage
    msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
  File "/srv/ha/bin/hass", line 8, in <module>
    sys.exit(main())
  File "/srv/ha/lib/python3.8/site-packages/homeassistant/__main__.py", line 313, in main
    exit_code = runner.run(runtime_conf)
  File "/srv/ha/lib/python3.8/site-packages/homeassistant/runner.py", line 113, in run
    return asyncio.run(setup_and_run_hass(runtime_config))
  File "/usr/lib/python3.8/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.8/asyncio/base_events.py", line 603, in run_until_complete
    self.run_forever()
  File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
    self._run_once()
  File "/usr/lib/python3.8/asyncio/base_events.py", line 1859, in _run_once
    handle._run()
  File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
    self._context.run(self._callback, *self._args)
  File "/home/homeassi/.homeassistant/custom_components/mopidy/config_flow.py", line 106, in async_step_zeroconf
    _LOGGER.warning("Not a mopidy server", error)
  File "/usr/lib/python3.8/logging/__init__.py", line 1454, in warning
    self._log(WARNING, msg, args, **kwargs)
  File "/usr/lib/python3.8/logging/__init__.py", line 1585, in _log
    self.handle(record)
  File "/usr/lib/python3.8/logging/__init__.py", line 1595, in handle
    self.callHandlers(record)
  File "/usr/lib/python3.8/logging/__init__.py", line 1657, in callHandlers
    hdlr.handle(record)
  File "/srv/ha/lib/python3.8/site-packages/homeassistant/util/logging.py", line 50, in handle
    self.emit(record)
Message: 'Not a mopidy server'
Arguments: (ConnectionError(JSONDecodeError('Expecting value: line 1 column 1 (char 0)')),)

This happens when another http zerconf device is found.
the component tries to connect, but fails, throwing this error.
I'll see if I can turn it down a notch

@VDRainer
I believe I may have found the culprit for the overload in feedback.
I hope to have it fixed in my latest commit (a17d76875c442faf0cfb22d6e34aad5e5f6ec085)
Could you provide some feedback when you have time to try?

@bushvin , thanks for looking at this and your great integration.
Here's the log after first restart.
2021-04-05 22:27:26 ERROR (SyncWorker_19) [mopidyapi.client] Could not decode json from Mopidy: Expecting value: line 1 column 1 (char 0)
2021-04-05 22:27:26 ERROR (SyncWorker_3) [mopidyapi.client] Could not decode json from Mopidy: Expecting value: line 1 column 1 (char 0)
2021-04-05 22:27:27 ERROR (SyncWorker_3) [mopidyapi.client] Could not decode json from Mopidy: Expecting value: line 1 column 1 (char 0)
2021-04-05 22:27:27 ERROR (SyncWorker_2) [mopidyapi.client] Could not decode json from Mopidy: Expecting value: line 1 column 1 (char 0)
2021-04-05 22:27:27 ERROR (SyncWorker_11) [mopidyapi.client] Could not decode json from Mopidy: Expecting value: line 1 column 1 (char 0)
2021-04-05 22:27:27 WARNING (MainThread) [custom_components.mopidy.config_flow] NAS01.local.@5000 is not a mopidy server
2021-04-05 22:27:27 WARNING (MainThread) [custom_components.mopidy.config_flow] OSMC3.local.@8080 is not a mopidy server
2021-04-05 22:27:27 ERROR (SyncWorker_21) [mopidyapi.client] Could not decode json from Mopidy: Expecting value: line 1 column 1 (char 0)
2021-04-05 22:27:27 WARNING (MainThread) [custom_components.mopidy.config_flow] sonoff16apow01-2494.local.@80 is not a mopidy server
2021-04-05 22:27:27 WARNING (MainThread) [custom_components.mopidy.config_flow] milight-hub.local.@80 is not a mopidy server
2021-04-05 22:27:27 WARNING (MainThread) [custom_components.mopidy.config_flow] sonoff16a-7105.local.@80 is not a mopidy server
2021-04-05 22:27:27 WARNING (MainThread) [custom_components.mopidy.config_flow] 4C268D000000.local.@80 is not a mopidy server

This behaviour is consistent with the initial mopidy connection.
Unfortunately, the mopidy module doesn't have a decent way to detect if a device is a mopidy server or not.
might include this in a future release of the integration...

Hi,
I have a way to fix this, so I'm reopening to reference it from my PR.


refactor tests

Description

Deletes unnecessary tests.
Adds WaitTimeSeconds source parameter.
Adds different source and destination configuration constructors.
Adds CreateTestFifoQueue (will be used later on).

Quick checks:

[x] There is no other pull request for the same update/change.
[x] I have made sure that the PR is of reasonable size and can be easily reviewed.

@raulb @maha-hajja did revert the intent of the pr, this just tidies up tests for the later prs and deletes a redundant test.


symmetric_gauge function that takes network and message tensors

Add a symmetric_gauge function that takes a network and that network's message tensors. Currently it seems like we need to first transform to the Vidal gauge and then into the symmetric gauge.

Closed by #139.


Axis Scaling

Hello,
How can I make sure that the unit length on each axis is equal?
To give an example, I'm using a BubbleChartView. I have four bubbles at the points (1,1), (1,-1), (-1,1), (-1,-1) with the viewport set to [(-2,2), (-2,2)]. As you can see in the screenshot, the horizontal spacing between bubbles is smaller than the vertical spacing.

I want to make the spacing equal, is that possible?
Thanks!

Hi, it could work if the chart view were square. Because it is rectangular and the height/width ratio is not equal 1 bubble position is scaled.
Sorry, but there is no easy way to do what you want, I've prepared workaround that might help:
//prepare chart view, set all data etc. this can be done, for example, in onCreate() method of your activity
ViewTreeObserver observer = chart.getViewTreeObserver();
if (observer.isAlive()) {
    observer.addOnGlobalLayoutListener(new ViewTreeObserver.OnGlobalLayoutListener() {
		@Override
		public void onGlobalLayout() {
			float viewportLeft = -2;
			float viewportRight = 2;
			float viewportTop = 2;
			float viewportBottom = -2;
			Viewport v = new Viewport(chart.getMaximumViewport());

			float height = chart.getHeight();
			float width = chart.getWidth();
			float longEdgeToShortEdgeRatio = 1;

                        //calculate ratio and modify viewport according to the ratio
			if (height >= width) {
				longEdgeToShortEdgeRatio = height / width;
				float scaledViewportHeight = (viewportRight - viewportLeft) * longEdgeToShortEdgeRatio;
				v.set(viewportLeft, scaledViewportHeight / 2, viewportRight, -scaledViewportHeight / 2);
			} else {
				longEdgeToShortEdgeRatio = width / height;
				float scaledViewportWidth = (viewportTop - viewportBottom) * longEdgeToShortEdgeRatio;
				v.set(-scaledViewportWidth / 2, viewportTop, scaledViewportWidth / 2, viewportBottom);
			}
			chart.setMaximumViewport(v);
			chart.setCurrentViewport(v);
            //chart.setViewportCalculationEnabled(false);//optional
		}
	});
}

Hi Lecho, Thanks a lot for the response, and the code snippet is much appreciated!


Added support for meteor packaging

Hi @ncuillery,
I'm a package maintainer for Meteor.js, a popular full-stack JavaScript framework.
I'm also a developer on angular-meteor, a library that let's you work with AngularJS on top of Meteor.
A lot of our users use angular-breadcrumb and it right now there is a separate package and Github repo that simply manually copies your distribution and publish it to Meteor.
This PR will allow you to directly publish updated versions of angular-breadcrumb as they become available. All you have to do is create an account at https://meteor.com/ (click SIGN IN, then Create account). After you've done that, please let me know the name of the account, and I'll add you as a maintainer to the "ncuillery" organization there.
I've already published the current version of the package on Atmosphere (Meteor's package directory). When you release new versions of angular-breadcrumb, you'll be able to publish them to Atmosphere by running make meteor.
Thanks & best regards,
Dotan

Coverage remained the same at 96.67% when pulling eefdca3aae19478edbd68790572e4b73cbb33bd4 on dotansimha:master into ef735250f95be945f23e05aa71f29cc448529775 on ncuillery:master.

Hi,
Thank for facilititating the connection with the meteor ecosystem. The name of my account is nicolascuillery.
When everything will be ok, i'll try to release the 0.3.4

@dotansimha, please can you add my account nicolascuillery to the ncuillery organisation ?
Then we could close this PR and deploy the current version (some forks start to show up in atmosphere https://atmospherejs.com/?q=angular breadcrumb ).

@ncuillery , sure, done!


fix raft version to 22.12

Signed-off-by: Allen Xu<EMAIL_ADDRESS>Since https://github.com/rapidsai/raft/commit/79e1ce854329bd655f2b02c86e6ec39165eebfc6, raft changes their API again and this breaks our build pipeline. Since we don't plan to introduce any new functionalities to this repo, we fix the raft version to 22.12 to avoid such issue in the future.

@pxLi FYI, we now fix the raft version to 22.12 so we can just skip modifying raft version value when we want to release a new version of spark-rapids-ml.


Look ability not working

Warrior js version: 0.4.2
When I invoke warrior.look() I get the following error
Invalid Player code: warrior.look is not a function
Finally thank you for the great game and keep the good work (y)

Hello @wizeowl, thanks for your interest in the project!
What level are you at? Does the README in your profile say you have warrior.look() available?

I'm at the beginner tower.
I took the README as indication and didn't think the list of sense was exclusive
Now I understand why getLocation always returns [1,0]
Also thanks for the fast feedback :+1:

Hi, I'm at "baby steps level 6" and it's telling me that look is not a function. It is listed in the README and has worked previously. I'm in the web client, if that matters.

I encountered the same warning halfway through Baby Steps level 4 from one run to the next. Also going back to previous levels had previously successful code stop working. The level readme retained warrior.look() as an ability.
After restarting my browser, the ability disappeared from the readme as intended. So the actual bug is that future abilities were available in the first place.

@shiar Do you recall when was it that you experienced that problem? The reason I asked is because I deployed a fix for that issue last Friday, if it was later then I'll need to revisit the issue.
@bbugh sorry, I completely missed your comment!

It was in fact last Friday when this occurred IIRC, so it might have been your fix which broke things for me :)
Thanks!


How to train&eval hulk without slurm？

Is there any good way to train or evaluate Hulk without using Slurm?

In https://github.com/OpenGVLab/Hulk/blob/main/core/distributed_utils.py#L525-L533, the original code supports torch.distributed init. Create a new train.sh might be enough. You may find this blog helpful.

OK, Thank you~


Reconsider sampling shapes

Related issue: #12

Problem: when a 1-batch distribution is created, the loc is a matrix of 1 row, while this should be a unidimensional vector:

with inf.replicate(size=1):
    x = inf.models.Normal(loc=[88., 10.], scale=1.)

x.loc   #this is array([[88., 10.]]), but should be array([88., 10.])

with inf.replicate(size=10):
    y = inf.models.Normal(loc=[88., 10.], scale=1.)

y.loc   #this is array([[88., 10.], [88., 10.]]), and it's ok


[monorepo-builder] Merge of freshly initialized monorepo fails with "ComposerJsonSection not found"

Following monorepo-builder's README leads to this result:
$ composer require symplify/monorepo-builder --dev

./composer.json has been created
Running composer update symplify/monorepo-builder
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 0 updates, 0 removals
  - Locking symplify/monorepo-builder (11.1.24)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 0 updates, 0 removals
  - Installing symplify/monorepo-builder (11.1.24): Extracting archive
Generating autoload files
1 package you are using is looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found
Using version ^11.1 for symplify/monorepo-builder

$ vendor/bin/monorepo-builder init

 [OK] Congrats! Your first monorepo is here.
 ! [NOTE] Try the next step - merge "composer.json" files from packages to the root one:
 !         "vendor/bin/monorepo-builder merge"

$ vendor/bin/monorepo-builder merge

 [ERROR] Class "Symplify\ComposerJsonManipulator\ValueObject\ComposerJsonSection" not found

I don't have the required experience to properly investigate, but my guess would be that this is a regression of #3474 caused by #4510.

We have the same things from the latest version:
> vendor/bin/monorepo-builder validate
 [ERROR] Class
         'Symplify\ComposerJsonManipulator\ValueObject\ComposerJsonSection' not
         found
Script vendor/bin/monorepo-builder validate handling the validate-monorepo event returned with error code 1

Currently, to fix it, we must use 11.1.18 version, after that, in vendor folder of monorepo-builder has not anymore composer-json-manipulator folder.

Not currently, everything is on a private repository.

In fact just with symplify/monorepo-builder in composer.json and test with vendor/bin/monorepo-builder validate is enough.
With 1.1.18 it works but with 1.1.19 it does not works.

symplify/monorepo-builder already version <IP_ADDRESS>

latest version has .72 suffix to support php 7.2.

Okay but this is not a problem.
Since 1.1.18 it does not work at all after this version, event latest <IP_ADDRESS>.

we need a simple reproducible repository for that so we can resolve it.

@roukmoute This is the upgrade you need, probably in monorepo-builder.php:
https://github.com/symplify/monorepo-builder/commit/2766334c63b61452ed1c78206213f1d22a4a29b6


[WIP] Moved posts browse to v2 (example)

refs #9866
This example is not finished.

@gargol @rishabhgrg I just added this example controller action for post browse. It's not finished, but it shows how the controller copy works. The tests pass for v2 post browse.


MSID: 101244 Version: 2 DOI: 10.1101/2<IP_ADDRESS>4769

MSID: 101244
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>4769
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=101244
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>4769

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/101244v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>4769
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/101244/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Hi @acollings, just checking the eLife Assessment is OK here, no significance keyword, also the v1 uses incomplete while the v2 uses inadequate?

Thanks @rkcook312 I've edited this. No significance term, though.


watch only for tiled windows in X.L.IfMax

watching for floating windows can cause problems when using with X.L.MouseResizableTile and watching only for tiled is more intuitive.

Merged.


Multiple instances of "Tile Window to Left of Screen" on Catalina 10.15.6

Window menu contains multiple instances of "Tile Window to Left of Screen" and "Tile Window to Right of Screen" when running mvim from command line.  The number of instances of these menu items appears to be proportional to the number of mvim instances that are created after that window has been opened.
Version information:
(base) MacBook-Pro:~ paullric$ mvim --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Aug 15 2020 20:27:49)
macOS version
Included patches: 1-1456
Compiled by<EMAIL_ADDRESS>Huge version with MacVim GUI.  Features included (+) or not (-):
+acl               +file_in_path      -mouse_sysmouse    -tag_old_static
+arabic            +find_in_path      +mouse_urxvt       -tag_any_white
+autocmd           +float             +mouse_xterm       -tcl
+autochdir         +folding           +multi_byte        +termguicolors
-autoservername    -footer            +multi_lang        +terminal
+balloon_eval      +fork()            -mzscheme          +terminfo
+balloon_eval_term +fullscreen        +netbeans_intg     +termresponse
+browse            +gettext           +num64             +textobjects
++builtin_terms    -hangul_input      +odbeditor         +textprop
+byte_offset       +iconv             +packages          +timers
+channel           +insert_expand     +path_extra        +title
+cindent           +ipv6              +perl/dyn          +toolbar
+clientserver      +job               +persistent_undo   +transparency
+clipboard         +jumplist          +popupwin          +user_commands
+cmdline_compl     +keymap            +postscript        +vartabs
+cmdline_hist      +lambda            +printer           +vertsplit
+cmdline_info      +langmap           +profile           +virtualedit
+comments          +libcall           +python/dyn        +visual
+conceal           +linebreak         +python3/dyn       +visualextra
+cryptv            +lispindent        +quickfix          +viminfo
+cscope            +listcmds          +reltime           +vreplace
+cursorbind        +localmap          +rightleft         +wildignore
+cursorshape       +lua/dyn           +ruby/dyn          +wildmenu
+dialog_con_gui    +menu              +scrollbind        +windows
+diff              +mksession         +signs             +writebackup
+digraphs          +modify_fname      +smartindent       -X11
+dnd               +mouse             -sound             -xfontset
-ebcdic            +mouseshape        +spell             +xim
+emacs_tags        +mouse_dec         +startuptime       -xpm
+eval              -mouse_gpm         +statusline        -xsmp
+ex_extra          -mouse_jsbterm     -sun_workshop      -xterm_clipboard
+extra_search      +mouse_netterm     +syntax            -xterm_save
-farsi             +mouse_sgr         +tag_binary
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
defaults file: "$VIMRUNTIME/defaults.vim"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/Applications/MacVim.app/Contents/Resources/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe  -DMACOS_X -DMACOS_X_DARWIN  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -Wall -Wextra -Wshadow -Werror -Wno-error=missing-field-initializers -Wno-error=deprecated-declarations -Wno-error=unused-function
Linking: clang   -L. -fstack-protector-strong -L/usr/local/lib -L/usr/local/opt/libyaml/lib<EMAIL_ADDRESS>-L/usr/local/opt/readline/lib -L. -fstack-protector-strong -L/usr/local/lib -L/usr/local/opt/libyaml/lib<EMAIL_ADDRESS>-L/usr/local/opt/readline/lib  -L/usr/local/lib -o Vim -framework Cocoa -framework Carbon       -lm  -lncurses -liconv /usr/local/lib/libintl.a -framework AppKit   -fstack-protector  -L/System/Library/Perl/5.18/darwin-thread-multi-2level/CORE

Thanks for reporting. Duplicate of #992. Please use that for tracking.


No diagnostic on invalid type description in the config file

In GitLab by @croussel on Sep 29, 2016, 10:42
PDI is crashing if the dimension given in the config file are not the one of the array during export.
The api should not crash I think.
If a variable type is not as expected (i.e: int instead of double in the config file) nothing is exported.

closed

In GitLab by @croussel on Nov 14, 2016, 09:12
Changed title: Crash: dimension of array → Crash: dimension of array{+ and invalid datatype+}

I don't think this is possible in C at least. In C, we have no idea about the data size, so if the user provides an invalid size, we'll definitely behave badly...
In fortran, we might overload the function to get info about runtime type and check if it matches the type described by the user.

mentioned in commit 1a44a448feb521da220e23d48f1aef60797208b2


TEST PR

This PR is to test whether CI can properly checkout a fork or not

It does; so we should stick to actions<EMAIL_ADDRESS>with no parameters


Should report row numbers on data errors

The tool doesn't report row numbers on data errors. "The data in column 7 is inconsistent with others values in the same column" is too vague when you may have hundreds of rows. It's like going to a doctor for a checkup, and he says, "You've got cancer somewhere in the upper half of your body!"
Maybe row-by-row problem identification is outside the scope of this project, but for us it is a dealbreaker. If CSVLint is already doing full validation, it has the data and merely needs to record and report it. (I make it sound so easy, don't I? Ha... we users are so ungrateful.)
Enclosing screenshot of validations results page, CSV, and schema.

Links to CSV and schema respectively:
https://drive.google.com/file/d/0B3CDKorSOdGNNm1CbXFrUmlFY1U/view?usp=sharing
https://drive.google.com/file/d/0B3CDKorSOdGNN3JlZ2pDLWNKaXc/view?usp=sharing

csvlint does report row numbers, but as noted in #183 the schema is not being applied correctly so you're not seeing the expected results. Using the corrected schema at https://gist.githubusercontent.com/ldodds/b0ae664e623ec62f595c/raw/ce3180b10cf187903aed3df501aeac2fdd2d06be/fixed-schema.json
I get the following:

Nice. Clearly not an issue so I am closing this ticket...!


Terraform Apply Failure

Tectonic Version
1.7.3
Environment
Amazon Web Service Free Tier
Expected Behavior
Applye Terraform Installation
Actual Behavior
4 Errors Occured
module.masters.aws_autoscaling_group.masters: Still creating... (10m10s elapsed)
module.workers.aws_autoscaling_group.workers: Still creating... (10m10s elapsed)
Error applying plan:

* module.vpc.aws_eip.nat_eip[4]: 1 error(s) occurred:
* aws_eip.nat_eip.4: Error creating EIP: AddressLimitExceeded: The maximum number of addresses has been reached.
	status code: 400, request id: 4ea4ffb9-a04a-4237-a042-60c81053ddc6
* module.workers.aws_autoscaling_group.workers: 1 error(s) occurred:
* aws_autoscaling_group.workers: "tectonic-cluster-kube-0-workers": Waiting up to 10m0s: Need at least 4 healthy instances in ASG, have 0. Most recent activity: {
  ActivityId: "a5a57ab4-d23d-e797-27b5-fcb8bcdfc2ab",
  AutoScalingGroupName: "tectonic-cluster-kube-0-workers",
  Cause: "At 2017-09-23T05:27:34Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 4.",
  Description: "Launching a new EC2 instance.  Status Reason: You have requested more instances (1) than your current instance limit of 0 allows for the specified instance type. Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit. Launching EC2 instance failed.",
  Details: "{\"Subnet ID\":\"subnet-962b709a\",\"Availability Zone\":\"us-east-1f\"}",
  EndTime: 2017-09-23 05:27:36 +0000 UTC,
  Progress: 100,
  StartTime: 2017-09-23 05:27:36.569 +0000 UTC,
  StatusCode: "Failed",
  StatusMessage: "You have requested more instances (1) than your current instance limit of 0 allows for the specified instance type. Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit. Launching EC2 instance failed."
}
* aws_s3_bucket.tectonic: 1 error(s) occurred:
* aws_s3_bucket.tectonic: Error creating S3 bucket: timeout while waiting for state to become 'success' (timeout: 5m0s)
* module.masters.aws_autoscaling_group.masters: 1 error(s) occurred:
* aws_autoscaling_group.masters: "tectonic-cluster-kube-0-masters": Waiting up to 10m0s: Need at least 3 healthy instances in ASG, have 0. Most recent activity: {
  ActivityId: "cf357ab4-c34d-6b6e-fe43-322ae6584f4f",
  AutoScalingGroupName: "tectonic-cluster-kube-0-masters",
  Cause: "At 2017-09-23T05:23:29Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 3.",
  Description: "Launching a new EC2 instance.  Status Reason: You have requested more instances (1) than your current instance limit of 0 allows for the specified instance type. Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit. Launching EC2 instance failed.",
  Details: "{\"Subnet ID\":\"subnet-b345e7d7\",\"Availability Zone\":\"us-east-1a\"}",
  EndTime: 2017-09-23 05:23:31 +0000 UTC,
  Progress: 100,
  StartTime: 2017-09-23 05:23:31.802 +0000 UTC,
  StatusCode: "Failed",
  StatusMessage: "You have requested more instances (1) than your current instance limit of 0 allows for the specified instance type. Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit. Launching

Other Information
What should I request from aws to increase limits in free tier plan?
What quantities is needed for installing my first ten nodes? (3 etcds , 4 workers ,and 3 master nodes)

aws_eip.nat_eip.4: Error creating EIP: AddressLimitExceeded: The maximum number of addresses has been reached. status code: 400, request id: 4ea4ffb9-a04a-4237-a042-60c81053ddc6

That is the primary error that leads to the other errors. From the AWS console, under "support", you can request limit increase per region for more EIPs.

In the request	it has to options for EIPs.
On referes to EC2 and one refers to VPC.
They ask for the target limit, too.
Thank for support

On Sep 25, 2017, at 4:44 PM, Ed Rooth<EMAIL_ADDRESS>wrote:
aws_eip.nat_eip.4: Error creating EIP: AddressLimitExceeded: The maximum number of addresses has been reached. status code: 400, request id: 4ea4ffb9-a04a-4237-a042-60c81053ddc6

https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html

Hello
Is there any other solution except remove VPCs or increase the limit which is charged?
Error: Error creating VPC: VpcLimitExceeded: The maximum number of VPCs has been reached.
status code: 400
Thank you.


UI cosmetic changes

Wider sidebar with solid color
Longer Available tools

Any comments? If not, I'm merging in a few hours!


[SPARK-22230] Swap per-row order in state store restore.

What changes were proposed in this pull request?
In state store restore, for each row, put the saved state before the row in the iterator instead of after.
This fixes an issue where agg(last('attr)) will forever return the last value of 'attr from the first microbatch.
How was this patch tested?
new unit test

Test build #82566 has started for PR 19461 at commit 17ef8a8.

Test build #82566 has finished for PR 19461 at commit 17ef8a8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/82566/
Test PASSed.

Merged build finished. Test PASSed.

Thanks! Merging to master and 2.2.

Oh, there are some conflicts with 2.2. @joseph-torres could you submit a backport PR, please?

Discussed offline. We don't need to backport to branch-2.2.


Supported Systems column

Amazing project, thanks for creating this! Do you have any plans to add support for a systems column?
While I was building the DB, I ran into  error: attribute 'darwin-arm64' missing as I'm on Mac M1. That's when I realized that most packages before March 2021 would not be supported for darwin-arm64 and it might be helpful to have that information in the sqlite DB.

I'm not sure I know where to get the information from, do you have any idea?

Just found that adding --meta flag does the trick.
nix-env -qaP --meta --json -f https://github.com/NixOS/nixpkgs/archive/827232d.zip | jq . | less

On second thought- given that there's license info , unfree and potentially other useful information about a package in there- I wonder if it makes sense to store the entire meta block in the table.

I've added the field in 6542edc, but I'll have to reindex the whole database (or at least a portion of it), which is gonna take a while.


Manually Building EOSIO on centos 7 failed

I manual install the dependencies on centos 7 successfully. But it is failed when build EOS and I get the following error message.
`[kingnet@bctestnode3 build]$ cmake -DBINARYEN_BIN=/opt/tangy/eos.io/binaryen/bin -DWASM_ROOT=/opt/tangy/eos.io/wasm-compiler/llvm -DOPENSSL                                                                                _ROOT_DIR=/usr/local/opt/openssl -DOPENSSL_LIBRARIES=/usr/local/opt/openssl/lib -DBUILD_MONGO_DB_PLUGIN=true ..
-- Using custom FindBoost.cmake
-- Boost version: 1.66.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   filesystem
--   system
--   program_options
--   signals
--   serialization
--   chrono
--   unit_test_framework
--   context
--   locale
--   iostreams
-- Configuring Eos on Linux
-- binaryen building with -std=c++11
-- binaryen building for platform x86-64
-- binaryen building with -Wall
-- binaryen building with -Werror
-- binaryen building with -Wextra
-- binaryen building with -Wno-unused-parameter
-- binaryen building with -fno-omit-frame-pointer
-- binaryen building with -fPIC
-- binaryen building with -O2
-- binaryen building with -UNDEBUG
-- Using WASM clang => /opt/tangy/eos.io/wasm-compiler/llvm/bin/clang
-- Using WASM llc => /opt/tangy/eos.io/wasm-compiler/llvm/bin/llc
-- Using WASM llvm-link => /opt/tangy/eos.io/wasm-compiler/llvm/bin/llvm-link
-- Found Secp256k1: /usr/local/lib/libsecp256k1.a
-- Configuring fc to build on Unix/Apple
-- zlib found
-- bzip2 found
-- Configuring SoftFloat
-- Using custom FindBoost.cmake
-- Boost version: 1.66.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   filesystem
--   system
--   chrono
--   unit_test_framework
--   locale
-- Configuring ChainBase on Linux
-- Using custom FindBoost.cmake
-- Boost version: 1.66.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   filesystem
--   system
--   chrono
--   program_options
--   unit_test_framework
--   locale
-- Configuring AppBase on Linux
**CMake Error at plugins/mongo_db_plugin/CMakeLists.txt:22 (find_package):
By not providing "Findlibbsoncxx-static.cmake" in CMAKE_MODULE_PATH this
project has asked CMake to find a package configuration file provided by
"libbsoncxx-static", but CMake did not find one.
Could not find a package configuration file provided by "libbsoncxx-static"
with any of the following names:
libbsoncxx-staticConfig.cmake
libbsoncxx-static-config.cmake

Add the installation prefix of "libbsoncxx-static" to CMAKE_PREFIX_PATH or
set "libbsoncxx-static_DIR" to a directory containing one of the above
files.  If "libbsoncxx-static" provides a separate development package or
SDK, be sure it has been installed.**
-- Configuring incomplete, errors occurred!
See also "/opt/tangy/eos.io/eos/build/CMakeFiles/CMakeOutput.log".
See also "/opt/tangy/eos.io/eos/build/CMakeFiles/CMakeError.log".
`
After that, I and libbsoncxx-static_DIR. But I get another error mesage.
`[kingnet@bctestnode3 build]$ cmake -DBINARYEN_BIN=/opt/tangy/eos.io/binaryen/bin -DWASM_ROOT=/opt/tangy/eos.io/wasm-compiler/llvm -DOPENSSL                                                                                _ROOT_DIR=/usr/local/opt/openssl -DOPENSSL_LIBRARIES=/usr/local/opt/openssl/lib -DBUILD_MONGO_DB_PLUGIN=true -Dlibbsoncxx-static_DIR=/opt/t                                                                                angy/eos.io/mongo-c-driver-1.9.3/mongo-cxx-driver/build/src/bsoncxx ..
-- Using custom FindBoost.cmake
-- Boost version: 1.66.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   filesystem
--   system
--   program_options
--   signals
--   serialization
--   chrono
--   unit_test_framework
--   context
--   locale
--   iostreams
-- Configuring Eos on Linux
-- binaryen building with -std=c++11
-- binaryen building for platform x86-64
-- binaryen building with -Wall
-- binaryen building with -Werror
-- binaryen building with -Wextra
-- binaryen building with -Wno-unused-parameter
-- binaryen building with -fno-omit-frame-pointer
-- binaryen building with -fPIC
-- binaryen building with -O2
-- binaryen building with -UNDEBUG
-- Using WASM clang => /opt/tangy/eos.io/wasm-compiler/llvm/bin/clang
-- Using WASM llc => /opt/tangy/eos.io/wasm-compiler/llvm/bin/llc
-- Using WASM llvm-link => /opt/tangy/eos.io/wasm-compiler/llvm/bin/llvm-link
-- Found Secp256k1: /usr/local/lib/libsecp256k1.a
-- Configuring fc to build on Unix/Apple
-- zlib found
-- bzip2 found
-- Configuring SoftFloat
-- Using custom FindBoost.cmake
-- Boost version: 1.66.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   filesystem
--   system
--   chrono
--   unit_test_framework
--   locale
-- Configuring ChainBase on Linux
-- Using custom FindBoost.cmake
-- Boost version: 1.66.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   filesystem
--   system
--   chrono
--   program_options
--   unit_test_framework
--   locale
-- Configuring AppBase on Linux
CMake Error at /opt/tangy/eos.io/mongo-c-driver-1.9.3/mongo-cxx-driver/build/src/bsoncxx/libbsoncxx-static-config.cmake:36 (message):
File or directory
/opt/tangy/eos.io/mongo-c-driver-1.9.3/mongo-cxx-driver/include/bsoncxx/v_noabi
referenced by variable LIBBSONCXX_STATIC_INCLUDE_DIRS does not exist !
Call Stack (most recent call first):
/opt/tangy/eos.io/mongo-c-driver-1.9.3/mongo-cxx-driver/build/src/bsoncxx/libbsoncxx-static-config.cmake:52 (set_and_check)
plugins/mongo_db_plugin/CMakeLists.txt:22 (find_package)
-- Configuring incomplete, errors occurred!
See also "/opt/tangy/eos.io/eos/build/CMakeFiles/CMakeOutput.log".
See also "/opt/tangy/eos.io/eos/build/CMakeFiles/CMakeError.log".
`

check the openssl root path in the  eosio_build.sh file.

@YunZhuangCai
I checked the openssl root path, and change  "-DOPENSSL_ROOT_DIR=/usr/local/opt/openssl" to " -DOPENSSL _ROOT_DIR=/usr/include/openssl".
But it is also failed.

Are you check the DOPENSSL_LIBRARIES path?  Delete the build contents and rebuild

@YunZhuangCai
I checked the DOPENSSL_LIBRARIES. There is no DOPENSSL_LIBRARIES in eosio_build.sh. I have removed DOPENSSL_LIBRARIES from build command. But it it also failed.
I did not delete the build content. How to delete the build contents?

@YunZhuangCai
I delete the build contents and rebuild again.  It is also failed.

god, I know the reason.
There should be a command "sudo make install" after the commands of "Install mongo-cxx-driver (release/stable):"
because mongo-cxx-driver is not installed if current operation.

Manual installation of the dependencies miss one command.


Add ability to have multiple element areas

Similar to Content Blocks module, although I'd prefer to have two has_ones rather than defining it in YML.
$has_one = array(
"ContentArea" => "ElementArea"
"SideBarArea" => "ElementArea"
);

In progress on the SS4 branch, needs more testing.

This has now been implemented and tested.

Does this mean we can now have more than 1 ElementArea as show by codes from @pitchandtone ?
If so, it would be great to see some information in the Readme.md file
Regards,

Hey @sparkcom, I've raised the following issue to help you (and others) out https://github.com/dnadesign/silverstripe-elemental/issues/759


Fix/python max version

Disclaimer: This review was made by a crew of AI Agents.
Code Review Comment for PR #1777
Overview
This pull request effectively updates the Python version requirements across multiple project files, moving from <=3.12 to <3.13. Such maintenance updates are crucial for managing dependencies and ensuring compatibility with new Python releases.
Detailed Insights
1. Version Requirement Changes

The updated version constraints from >=3.10,<=3.12 to >=3.10,<3.13 foster better dependency management. This precision helps mitigate issues that may arise from untested releases.

2. Configuration Files Review

pyproject.toml and uv.lock were modified appropriately:requires-python = ">=3.10,<3.13"

This change aligns with best practices, ensuring clear and precise version specifications.

3. Documentation Updates
All associated documentation, including the README.md and docs/installation.mdx, is consistently updated to reflect the new requirements. This synchronization is critical for clarity in user setup processes.
4. Testing Enhancements
The changes in tests/cli/deploy/test_deploy_main.py confirm that the tests take into account the revised version requirements:
requires-python = ">=3.10,<3.13"

Recommendations for Improvement

Version Specification Format: Consider adding descriptive comments in pyproject.toml regarding the rationale for the version constraint:
[project]
# Version constraint excludes Python 3.13 until officially tested
requires-python = ">=3.10,<3.13"

Documentation Enhancement: A practical addition to the README could include:
> **Note:** While CrewAI supports Python versions from 3.10 up to (but not including) 3.13,
> we recommend using Python 3.11 or 3.12 for optimal performance.

Expanded Testing Coverage: Introduce specific version compatibility tests to ensure compatibility across supported Python versions:
@pytest.mark.parametrize("python_version", ["3.10", "3.11", "3.12"])
def test_python_version_compatibility(python_version):
    # Test core functionality under different Python versions

Conclusion
The changes proposed in PR #1777 have been executed systematically and represent a critical advancement in maintaining project integrity. The version updates are not only correct but also effectively documented. Implementing the recommendations outlined above could further enhance code clarity, maintainability, and robustness.
✅ Verdict: Approve
These updates pose no risks of introducing breaking changes and adequately align the project with the updated Python versioning standards.
Final Checklist

[x] Consistent version requirements across all files
[x] Documentation properly updated
[x] Test files adjusted accordingly
[x] Lock file properly updated
[x] No breaking changes introduced


Aepp browse

Added the aeHeader to aepp-identity

currently it looks strange but I'll review this again after we accepted #46 because this will also change stuff in Apps.vue

@muxe #46 is depend on #38 and only #38 changes Apps page, so I have rebased this PR on #38.

see https://github.com/aeternity/aepp-identity/pull/48


预览PDF添加水印

我想在预览PDF时在特定的页面添加水印，这个应该怎么做？
这个插件能不能以tab的形式预览多个PDF文件？

Probably duplicate of #7783
I don't think the watermarking feature will be implemented by pdf.js. You can render a watermark as a overlay.

To my knowledge, pdf.js doesn't have built-in support for rendering multiple pdf files each of which at their own tab, you need to implement at your own.

如果要实现多文件标签的方式，有没有可以参考的文档


specifically depends on at some times is duplicated in rev 302

From<EMAIL_ADDRESS>on June 29, 2012 14:27:03
BFO_0000169 and BFO_0000070
Original issue: http://code.google.com/p/bfo/issues/detail?id=83

From<EMAIL_ADDRESS>on June 29, 2012 11:27:58
same for has specific dependent at some times (BFO_0000168 and BFO_0000125)

From<EMAIL_ADDRESS>on June 29, 2012 12:40:41
Status: Fixed


Failed to execute goal io.fabric8:fabric8-maven-plugin:3.1.65:push (default-cli) on project awsome: Unable to push 'example/awsome:1.0.5' from registry '<IP_ADDRESS>:80': Get https://<IP_ADDRESS>:80/v1/_ping: http: server gave HTTP response to HTTPS client -> [Help 1]

please help me out of the problem

is this when running inside a Jenkins pipeline? It sounds like the jenkins container can't see the docker reigstry on <IP_ADDRESS>:80

No it looks like you haven't configured insecure registry for that address. It's a flag to the docker daemon & out of our control in afraid.

Is there a solution for this problem ? I am currently facing the same issue .
thanks in advance


Windows Bolt with apply block in plans fails silently and logs "Something's gone terribly wrong"

Describe the Bug
Running a plan with apply block, from a Windows Bolt Controller, fails silently .
There is only an INFO log entry appearing in bolt-debug.log
2020-11-25T09:05:21.567312 INFO   [] [Bolt::Executor] {"message":"Something's gone terribly wrong! STDERR is logged."}

Expected Behavior
Apply blocks that work perfectly fine when run from a Linux Bolt controller should work the same way on Windows.
Also, regardless of the issue, if there is an error that's gone terribly wrong, Bolt should show the error instead of hiding it in the bolt-debug.log file.
Steps to Reproduce

Create a bolt-project.yaml file with the following piece of yaml

---
name: boltcode

Create a file named plans/test_apply.pp with the following piece of code

plan boltcode::test_apply(
  TargetSpec $targets
) {
  apply($targets) {
    file {'c:/tempapplyblock':
      ensure => file
    }
  }
}

Run the plan on a target
Check that the standard output of Bolt shows no sign of errors like "apply catalog with 0 failures"
Check on the target that no resource was applied
Check in bolt-debug.log the "Something's gone terribly wrong" message

Environment

Version: 2.35.0
Platform: Windows Bolt controller
Platform: Windows or Linux target

Additional Context

Debugging the issue shows that libexec/bolt_catalog writes warnings in its standard output (see below). For this reason, the resulting JSON cannot be parsed.

E, [2020-11-25T09:04:53.025679 #31348] ERROR -- : Facter::InternalFactManager - "\xE9" to UTF-8 in conversion from ASCII-8BIT to UTF-8 to UTF-16LE

The above warning about UTF conversion also appears systematically at the start of every bolt command run from a Windows Bolt Controller

So far, I saw that this warning about UTF conversion disappears when I delete the bolt-project.yaml... But I could not run my plan under these conditions

@kev I'm not able to reproduce this issue, can you post a (redacted) version of your plan, and the output from Bolt? It seems to me like something else is going wrong and causing an undiagnosed error. I could be wrong and if Puppet is returning useless information at stderr we'll probably want to figure out what is being returned and remove it rather than just ignore it.

Also, regardless of the issue, if there is an error that's gone terribly wrong, Bolt should show the error instead of hiding it in the bolt-debug.log file.

That message is just printed from Bolt to be helpful, but it isn't obscuring anything - any errors should be logged at error level by Bolt, though there may be additional messages logged by Puppet that may not be logged at Bolt's default log-level for plans which is warn.
      # Any messages logged by Puppet will be on stderr as JSON hashes, so we
      # parse those and store them here. Any message on stderr that is not
      # properly JSON formatted is assumed to be an error message.  If
      # compilation was successful, we print the logs as they may include
      # important warnings. If compilation failed, we don't print the logs as
      # they are likely redundant with the error that caused the failure, which
      # will be handled separately.
      logs = err.lines.map do |line|
        JSON.parse(line)
      rescue JSON::ParserError
        { 'level' => 'err', 'message' => line }
      end

Thanks for raising this @kev-in-shu ! I'm asking our Facter team about it, as I don't think you should be seeing the UTF error to begin with. Rather than suppress it I'd like to see if we can fix it first.

Update: Looks like this is duplicates this Facter issue: https://tickets.puppetlabs.com/browse/FACT-2856 Devs tell me it's been fixed and will be released before the end of the year!
I'm concerned that non-JSON output was printed to stdout when the error is raised. I think the goal of this ticket is to figure out under what circumstances errors are printed to stdout instead of stderr and address that directly so this doesn't happen with other error messages.

Thanks @lucywyman for the feedback. It's great news that it will be fixed before the end of the year.

Hm, I'm having trouble reproducing the error. It seems like what happened was an error was raised ([2020-11-25T09:04:53.025679 #31348] ERROR -- : Facter::InternalFactManager - "\xE9" to UTF-8 in conversion from ASCII-8BIT to UTF-8 to UTF-16LE), which caused the apply block to fail and print the error. I don't think there's anything for us to do here, since if stdout isn't JSON it means somethings gone wrong (like the error above).
The error itself should be fixed soon, but for now I don't think there's any behavior we need to change. Let me know if you have ideas for how to make the error message more clear @kev-in-shu! If you're ok with it, I think we'll close this and verify the fix in Facter once it's released later this month.

Hi @lucywyman
I think Bolt apply should more clearly fail instead of just logging things in the background. It should not be that hard since erroneous JSON output detection is already implemented. The problem is that even though bolt detected the issue, it does not show up in regular user output, and only write a log hidden in bolt-debug.log
2020-11-25T09:05:21.567312 INFO   [] [Bolt::Executor] {"message":"Something's gone terribly wrong! STDERR is logged."}
It took me some time to realize it was the whole apply block that failed when I switched to running from Windows.

Hi,
Just wanted to let you know that I fetched the latest version of Bolt, Puppet and Facter, but I still have the issue

> bolt --version
2.40.2
> puppet --version
7.1.0
> facter --version
4.0.47

Hi,
Just wanted to let you know that I fetched the latest version of Bolt, Puppet and Facter, but I still have the issue

> bolt --version
2.40.2
> puppet --version
7.1.0
> facter --version
4.0.47

Hm, we actually just released 2.42.0 yesterday, which is the version that ships with Facter 4.0.47. Does it still happen if you upgrade to Bolt 2.42.0? I think Bolt might be using the Facter it ships with rather than another version installed on the system, and Bolt 2.40.2 shipped with Facter 4.0.38.

Hm, we actually just released 2.42.0 yesterday, which is the version that ships with Facter 4.0.47. Does it still happen if you upgrade to Bolt 2.42.0? I think Bolt might be using the Facter it ships with rather than another version installed on the system, and Bolt 2.40.2 shipped with Facter 4.0.38.

Thank you for your reply. I just installed bolt 2.42.0 and could test that the apply blocks work now.

Thank you for your reply. I just installed bolt 2.42.0 and could test that the apply blocks work now.

Yay!!

Yay!!


Feat:  Want to add like option for all resources  with complete backend intergration

Describe the feature
I want to add the likes option for the resources page
The logged in user can hit the like button if he likes any resource
Both logged in and not logged in users can see the resources likes
It will be very helpful to filter the resources on the basis of their choice
Add ScreenShots
For ex :- All social media handles have like button  and can like if they likes any content
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[ ] I'm a VSoC'24 contributor
[X] I want to work on this issue

@Ayushmaanagarwal1211 Issue acknowledgment! Issue assigned to you.


Fix description of antler-proj remove

Correct descriptions of the commands.
Example:
./antler-proj remove --help
returns wrong description:
Add an app, dependency, library or test to your project.

I thought we'd fixed this already. :-(


OwnerReference be added to the secret created by the ClusterIssuer and Issuer

Is your feature request related to a problem? Please describe.
The current implementation of ClusterIssuer and Issuer does not have an OwnerReference included in the secret they create. This absence can cause complications in overseeing and tracing the secret's ownership and lead to issues in deleting the secret when the corresponding ClusterIssuer/Issuer are removed.
Describe the solution you'd like
I would like to request that an OwnerReference be added to the secret created by the ClusterIssuer and Issuer
Describe alternatives you've considered
have not considered any alternatives.
Additional context
N/A
Environment details (remove if not applicable):

Kubernetes version:
Cloud-provider/provisioner:
cert-manager version:
Install method: e.g. helm/static manifests

/kind feature

in the secret they create

Which secret do you mean? There are different types of issuers and in most cases the Secrets are created by users and pre-populated with existing credentials.
In case of ACME issuer acme.privateKeySecretRef Secret can be created by user or by cert-manager and if created by cert-manager corresponds to creating a new ACME account. At the moment the flow is such that the Secret always remains in the cluster when the issuer is deleted and we most likely should not change the default behaviour to avoid extra requests to ACME in cases where issuer resources get redeployed. Because of this and because the Secrets can also be created by users I am not sure if owner refs are the best way track these resources. Perhaps they could be labelled if created by cert-manager, but this again requires consideration of whether we want to label Secrets that we did not create and how do we detemine if an existing Secret was created by us or by the user.
Perhaps you can write up a more detailed use case about what workflow you would like to implement?

I second this request, i want the ability to idempotently create and destroy workloads in my Kubernetes clusters which includes issuers, the lack of an ownerRef on this secret created by cert-manager makes this impossible.
steps to reproduce:
kubectl apply -f issuer.yaml
kubectl delete -f issuer.yaml
kubectl apply -f issuer.yaml < Issuer fails, secret already exists, specific error is:
Status:
  Acme:
  Conditions:
    Last Transition Time:  2023-05-22T16:55:56Z
    Message:               Failed to register ACME account: 400 urn:ietf:params:acme:error:badPublicKey: Account key is already in use.
    Observed Generation:   1
    Reason:                ErrRegisterACMEAccount
    Status:                False
    Type:                  Read

To me this seems like a straightforward bug, rather than a feature request; Is this a use-case cert-manager intends to support?

Ah, yes, the Secret resource that gets created by the Issuer or ClusterIssuer configured with ACME won't be configured with an owner reference, which means Kubernetes won't garbage collect it after the Issuer is removed.
This looks like a missing feature (or an oversight when we created the ACME issuer). The ACME private key is ephemeral anyways, it doesn't make sense to be careful not to remove it (unlike Secret resources created from Certificate resources; this has the potential of disrupting things).
And since it is already possible to tell cert-manager to add the owner reference for a Secret created by a Certificate, it would make sense to do the same for the Issuer or ClusterIssuer resource.
/good-first-issue


accept negative numbers in inspector

better text input formatter
fix bug in listview

Codecov Report

Merging #494 (3c559c7) into main (16bc080) will increase coverage by 0.83%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #494      +/-   ##
==========================================
+ Coverage   75.15%   75.98%   +0.83%
==========================================
  Files          32       32
  Lines        2483     2486       +3
==========================================
+ Hits         1866     1889      +23
+ Misses        617      597      -20

Impacted Files
Coverage Δ

packages/isar/lib/src/native/bindings.dart
92.38% <0.00%> (+0.55%)
:arrow_up:

packages/isar/lib/src/query_components.dart
79.03% <0.00%> (+3.22%)
:arrow_up:

packages/isar/lib/src/native/query_build.dart
88.84% <0.00%> (+3.86%)
:arrow_up:

packages/isar/lib/src/query_builder.dart
92.00% <0.00%> (+9.33%)
:arrow_up:

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 16bc080...3c559c7. Read the comment docs.


fix a bug where addToResourcePolicy was not working

Following code was not working due to policyDocument was evaluated immediately when constructor is called.
const repo = new ecr.Repository(this, 'Repo');
repo.addToResourcePolicy(new cdk.PolicyStatement().addAction('*'));

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

Thank you!


Localization question

Hi there, awesome location picker!
How can I change the language the addresses are written in. All addresses are in English, but I would like them to be in Spanish.
Thank you

The language depends on locale setting of the device because adresses are provided by this API. If you configured language setting properly and still can't get addresses in Spanish, then Apple may hasn't provided Spanish addresses yet.

Thank you for your answer. I will look into that


Keep going!

Thank you for your typo fixes. I was typing too fast maybe!.

No problem, I wonder why I'm thinking you did this on purpose, so people can contribute to your project :D. So thanks if that is the case or not.


-Three-Tier Architecture

word [REQUIRED]:Three-Tier Architecture
content [REQUIRED]: Three-tier architecture, which separates applications into three logical and physical computing tiers, is the predominant software architecture for traditional client-server applications.
learn more URL [REQUIRED]: https://www.ibm.com/in-en/cloud/learn/three-tier-architecture
tag [REQUIRED, select one]: Tech category the word fits in. Options: system design, cloud , architecture , three tier web application
abbreviation [OPTIONAL]: If the word is commonly abbreviated, please provide it. For example, command line interface is often abbreviated as CLI.
author name [REQUIRED]: Joseph Alan J
author link [REQUIRED]: josephalan.online

Added, thank you for your contribution.


Added get_cleaned_data method to modelforms

As you know if we want to get a data from our form we have to do this
form.cleaned_data["username"]

and for example if we want to create a user we have to do this
User.objects.create(username=form.cleaned_data["username"],email=form.cleaned_data["email"],password=form.cleaned_data["password"])

But with this commit we do like this
User.objects.create(**form.get_cleaned_data("username","password","email")

it will make our code more readable and easier

Thanks for the suggestion, but you can achieve this easily in the following way:
User.objects.create(**{
    k: v for k, v in form.cleaned_data.items()
    if k in ['username', 'password', 'email']
})

This is trivial enough not to need something added in Django.


feature request: config switch between legacy and RLS mode

Version of VSCode: 1.11.2 (1.11.2)
Version of the extension:  0.3.11
OS: OSX 10.10.5
There should be a configuration option to switch between legacy (racer, rustfmt, rustsym) and RLS mode.
If one of the legacy mode utilities is found, legacy mode is activated even if RLS is configured in settings.json via
{
    "rust.rls": {
        "executable": "rustup",
        "args": ["run", "nightly", "rls"]
    }
}

At the very least, if RLS is defined in user settings it should override the automatic detection of legacy mode.

@seanjensengrey,
Actually if RLS is found, it will use RLS.

How do i know if RLS mode is used? It says "Racer: on" in the bottom, but rls is definitely installed.

@buster,
What version do you use: from the marketplace or from the source?
If you use the version from the marketplace, you should set rust.rls.executable in order to make it work.
If you use the version from the source, you shouldn't set anything, it must work.

Is there a way to disable RLS mode on 0.3.13? I'm working on projects that use workspaces, and those aren't working well with RLS right now (see rust-lang-nursery/rls#263)

Remove RLS component from rustup. There is no other way.

@TedDriggs,
I will add "rust.forceLegacyMode: boolean" to allow this.


Added Shell sort

Added Shell sort

Hey @codingCapricorn, sorry but this issue was assigned to somebody else. Please ask for an assignment first. We have more issues. See if you can contribute to something else. For any queries, reach out to us on our Slack channel. Thankyou :)


Cleanup Page Object Locations

Move all page objects to packages that are domain-specific instead of the generic pages packages so that we follow the correct naming convention for page objects.

Done.


End to End testing for OpenRefine

Since the introduction of Cypress, more and more features of OpenRefine are tested.
The approach was to test individual functionalities of OpenRefine such facetting, reconciliation and so on ...
Now it would be good to have tests that reproduce a real user behavior, with a project tested from end to end.
It will allows us to test combos of functionalities, for example facetting + filtering + reconciliation + re-facetting.
Started as a thread on the mailing list
Proposed solution
Implement fully, or partially the tutorials by @ostephens as Cypress tests https://librarycarpentry.org/lc-open-refine/

We already have some tests which are drawn from tutorials, so I wonder if this can be closed, or if we want more of them?

@wetneb I think that as long as we have tests that incorporate transforms with history changes that also utilize all the object types @fgiroud mentioned, then I think we have things covered.  Generally, the object types and ensuring that memory/state is maintained well and restored well, no matter our object types (recon, etc.).  Which I think we already do.  So I think we can probably close this.

Yes, i think we cover the cases we wanted to have there


Add data-testid to LoadingOverlay

Allows us to target the LoadingOverlay in our tests without class name workarounds.
Closes https://github.com/orgs/user-interviews/projects/3/views/17?filterQuery=test

Ah! It seems so obvious now that I'm seeing it here 😆

No more find classes and randomly use the first one. Hurray! 🎉


VideoElement doesn't resume autoplay on route pop

Inserting a VideoElement with autoplay attribute set to true in a widget produce a weird behaviour when navigating to a second route and navigating back.
Steps to Reproduce
You can find a concrete sample in this repository: https://github.com/carlo-lucera-3r/flutter_web_video_test
Clone the sample repository and on the terminal use flutter run -d chrome
On run you will find a video and a button, clicking on a button will send you to a second page with only a text
Expected result:
Going back the video should continue to play
Actual result:
Going back the video doesn't restart

Logs
[✓] Flutter (Channel dev, 1.22.0-1.0.pre, on Linux, locale en_US.UTF-8)
    • Flutter version 1.22.0-1.0.pre at /home/carlo/flutter
    • Framework revision ce40de69b7 (4 weeks ago), 2020-08-20 07:31:50 -0700
    • Engine revision 81027ab0cc
    • Dart version 2.10.0 (build 2.10.0-45.0.dev)

[!] Android toolchain - develop for Android devices
    • Android SDK at /usr/lib/android-sdk
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, set ANDROID_HOME to that location.
      You may also want to add it to your PATH environment variable.

    ✗ No valid Android SDK platforms found in /usr/lib/android-sdk/platforms. Directory was empty.
    • Try re-installing or updating your Android SDK,
      visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).

[✓] Connected device (2 available)
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome 84.0.4147.125

I was able to reproduce this on latest master channel.
flutter doctor -v
[✓] Flutter (Channel master, 1.22.0-10.0.pre.251, on Mac OS X 10.15.6 19G2021 x86_64, locale en)
    • Flutter version 1.22.0-10.0.pre.251 at /Users/pedromassango/dev/SDKs/flutter_master
    • Framework revision d26268bb9e (12 hours ago), 2020-09-18 09:06:26 +0900
    • Engine revision 2abe69c608
    • Dart version 2.10.0 (build 2.10.0-136.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0, Build version 12A7209
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] IntelliJ IDEA Community Edition (version 2020.2.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 49.0.4
    • Dart plugin version 202.7319.5

[✓] VS Code (version 1.48.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.14.1

[✓] Connected device (4 available)
    • iPhone 11 Pro Max (mobile) • 7A82F29E-E49E-4B3C-8609-1570361DBC17 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)
    • macOS (desktop)            • macos                                • darwin-x64     • Mac OS X 10.15.6 19G2021 x86_64
    • Web Server (web)           • web-server                           • web-javascript • Flutter Tools
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 85.0.4183.102

! Doctor found issues in 1 category.
Process finished with exit code 0

One hypothesis is that this is caused by https://developers.google.com/web/updates/2017/09/autoplay-policy-changes, but it's hard to say for sure. A workaround may be to construct the video tag in a way that will allow the browser to autoplay.

@yjbanov In order to be compliant to the autoplay policy it should be enough the muted = true on the VideoElement also the video correctly run when the page is loaded or reloaded, the only case that interrupt the play is when you come back from another page with the browser back button

Verified this issue on latest versions and observed that behavior is still replicable.

 stable, master flutter doctor -v
[✓] Flutter (Channel stable, 3.3.7, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.3.7 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision e99c9c7cd9 (2 days ago), 2022-11-01 16:59:00 -0700
    • Engine revision 857bd6b74c
    • Dart version 2.18.4
    • DevTools version 2.15.0

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.5.0-12.0.pre.168, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 3.5.0-12.0.pre.168 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision a1432a9c5d (4 hours ago), 2022-11-07 19:17:03 -0600
    • Engine revision e7d7edab98
    • Dart version 2.19.0 (build 2.19.0-374.0.dev)
    • DevTools version 2.19.0
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.


Deprecate Client::__call()

I propose to merge this after 7.0.0 release.

IMHO I wouldn't like the helper functions to be removed.. Instead I would advise to be strictly declared and create them inside the client.

Agree with @gmponos, ->get(), ->post(),.. are very useful IMO and should stay. Implementation via __call() should be changed to usual methods though.

I think we should add these functions to the ClientInterface, since people tend to want to call them anyway, even when they only have something implementing the interface.

I've created https://github.com/guzzle/guzzle/pull/2513, which I think is a good solution. By providing a trait, we have effectively not really added more stuff to interface, from the perspective of someone looking to implement the interface for themselves. All they need to do is implement the old interface, and then "use" the trait.

I think we should add these functions to the ClientInterface

I just saw that I had upvoted this... my bad..  IMHO I am not in favor of moving these functions to an interface... Neither having them as trait and allowing developers to use it.

Developers use the dynamic methods anyway, even when they only know they have a ClientInterface. This way, we're just making it "official". Critically, we are making Guzzle easy to use.

Posted the question to twitter, in an unbiased way: https://twitter.com/GrahamJCampbell/status/1211338797314646020.

Feedback so far:

Yeah. I saw that.
Let’s deprecate the magic function and add proper ones. Just like you’ve done.
Thank you.

Excellent. I really think keeping these functions will help Guzzle appeal to new comers, and also help exiting users upgrade to Guzzle 7 when it comes out. 🚀

Just to be clear here... if I started the guzzle client from zero.. I would definetely not have these functions.. the only reason that I said that these should stay is that they are being used by the community and it will bring a lot of headaches... not because the community uses them makes it valid...
I hope that promoting PSR 18 into the client developers will go away from these functions..
Promoting these functions to an interface makes them more official and in a way suggested...
So yes in the future I would like to revise this and remove them...
At the moment I dont see neither a strong argument for removing neither a strong argument (at least for me) to promote them...

I guess we kinda have different visions. I am interesting in making the package as easy to use as possible. To me, this doesn't mean just saying it's an implementation of the PSR HTTP client spec. Guzzle has to differentiate itself from the crowd to stay the most popular choice, so it really doesn't make sense to throw away niceties that attract new users.

I think we only have a strong argument for leaving them in.

I don't see why we should remove those functions.
There are two major use cases for an HTTP Client:
1a. Write a nice wrapper around it for your HTTP endpoint, handle deserialization into DTOs, etc.
1b. Generate that wrapper
2. Just give me whatever is available on that URL.
I can't count the number of PHP scripts (actual scripts, not full applications) I wrote just to download a file and process it somehow. I never bothered using PSR-7/PSR-18 related stuff in those cases. Just installed Guzzel, ->get(), done.
There is essentially no maintenance cost.
I think this PR was based on a confusion anyway, at least we talked about this internally and we only wanted to remove the magic function, not the whole functionality. Can't find the discussion though.

I can't count the number of PHP scripts (actual scripts, not full applications) I wrote just to download a file and process it somehow. I never bothered using PSR-7/PSR-18 related stuff in those cases. Just installed Guzzel, ->get(), done.

This is 100% true, Guzzle has managed to combine ease of use and powerful features (line promises and concurrent execution) in one package. Ease of use is what makes it the most popular client there.

I guess we kinda have different visions. I am interesting in making the package as easy to use as possible. To me, this doesn't mean just saying it's an implementation of the PSR HTTP client spec. Guzzle has to differentiate itself from the crowd to stay the most popular choice, so it really doesn't make sense to throw away niceties that attract new users.

Everyone wants this.. Who will say the opposite.. That's not the point... Someone can use the same argument for not removing the getConfig because it makes it easy for him and attractive.. or even worse use this argument to add json or toString method to GuzzleHttp\Psr7\Response..
Just because something makes it easy and attractive does not make it correct...  There are more factors that need to be taken into consideration.

I think this PR was based on a confusion anyway

Yes I believe the same.. what I disagree is moving them to an abstract layer/interface.

Someone can use the same argument for not removing the getConfig because it makes it easy for him and attractive

Get config leaks internal concerns. There is nothing obviously wrong with HTTP methods in the client.

what I disagree is moving them to an abstract layer/interface.

The ClientInterface is not really an abstraction in this case. It does not abstract implementation details away, it's not there to allow providing alternative implementations. It probably once was though: before the MockHandler I think we had a MockClient.
I think the ClientInterface is only there to allow mocking the client. From this perspective not adding the new methods to the interface would be a mistake.
With PSR-18 in the picture I don't really see a major requirement to keep our interface/keep our interface "pure".
There is no obvious best solution in this case.

@sagikazarmark's comments were exactly my thinking for both PRs. I want Guzzle to be easy to use and attractive to new comers, but also to encourage good code by not exposing its internals.

closing as we all agree that we wont remove the helper function and the discussion continues here: https://github.com/guzzle/guzzle/pull/2513


internal/cmd/cue-ast-print: fix panic when printing the ast tree

Panic was observed when running cue-ast-print 2567.slice.1.cue or similar cue samples.
This commit fixes the problem by moving the test if !v.IsValid(){...} a few lines up, to prevent referencing a nil pointer.
The script issue-panic.txtar verifies that cue-ast-print works after this fix.
Running the script with a build of cue-ast-print before the fix demonstrates the panic about half-way into the printing.

Thanks! Importing as https://review.gerrithub.io/c/cue-lang/cue/+/1194721.

Happy to help!
Le mar. 14 mai 2024 à 17:23, Daniel Martí @.***> a
écrit :

Thanks! Importing as https://review.gerrithub.io/c/cue-lang/cue/+/1194721.
—
Reply to this email directly, view it on GitHub
https://github.com/cue-lang/cue/pull/2771#issuecomment-2110520776, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABKC5D6AY2FWUST3VMO2NTZCIT53AVCNFSM6AAAAABCDO3TK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJQGUZDANZXGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


⚠ ClamAV has degraded performance

In 48a0e52, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 69 ms

Resolved: ClamAV performance has improved in ba8632c.


Version for angular 10

I'm submitting a ...  (check one with "x")
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[ X] Feature request
[ ] Documentation issue or request

Any update on that?
We want to update our project to Angular version 10 and we cannot.

Works with Angular 11. Do you have troubles running with Angular 10?

see  https://github.com/fulls1z3/ngx-config/pull/169


Fail to connect to postgres DB - panic: dial tcp <IP_ADDRESS>:5432: connect: connection refused

Description
Below are the steps that leads to the issue and what I had tried to solve it.

After installing docker and docker-compose, running docker-compose run app ./lbrytv db_migrate_up will at first encounter the error lbry/odysee-api:latest-dev not found, fix it by changing the image tag to lbry/odysee-api:latest
After changing the image tag, all images are pulled successfully but docker-compose error out with panic: dial tcp <IP_ADDRESS>:5432: connect: connection refused. Full log are as shown in the section below.
I am not familiar with postgres so I perform some online searches and most of the results indicate that I should specify the ip address of the postgres docker container instead of localhost.

Search this repo and decided to trial and error by modify odysee-api/sqlboiler.toml and odysee-api/sqlboiler.toml to use the docker 172.x.x.x address.
The log still indicates that it is trying to use localhost, did more search and found the database connection config is acquired in odysee-api/main.go from github.com/lbryio/lbrytv/apps/lbrytv/config

I am not familiar with both postgres and Go so I am facing difficulty in moving forward. Any pointers for me to debug further or does this looks like an actual issue?
 Should be fixed now, just git pull and docker-compose up app is enough.


Release 1.6.4

On the docket:

[x] Restore pex.pex_bootstrapper.is_compressed API #684
[ ] Release more flexible pex binaries. #654

[x] If an --interpreter-constraint is set, it should always be honored. #656

I've short-cycled this in the interests of getting https://github.com/pantsbuild/pants/pull/7186 green - outstanding docket items moved to release 1.6.5 tracked in #690.


Update FAQs footer to reference valid url

The FAQs link along the footer is currently directing to a 404 page. This updates the link to the server section of the FAQ docs.

Thanks for pointing this out, but that link should work and wasn't because of website changes.  It's fixed now.


bdo

- Do you want to request a feature or report a bug?
- What is the current behavior?
- If the current behavior is a bug, please provide the steps to reproduce.
- What is the expected behavior?
- Please mention your node.js, NPM, Hugo and operating system version.

i am using your acceptor it is amazing, but sometimes when i use acceptor error comes and on my instagram account a popup comes saying"we have detected suspicious activity on your instagram account and have temporarily locked it as security precaution. it is likely that your account was compromised as a result of entering your password on a website designed to look like instagram . this is known as phishing.over the next few steps we will ask you to verify your identity to help secure your account ,and let you log in back." can you please update this error on your repl.it site for user it is a humble request to you ,as if this thing will happen again and again then instagram may deacivate our account ,so please look into it sir.


Keybindings | Add extra replacements or allow command substitution for custom report

Currently if i am creating a keybindings for a report it seems the only replacement i can use is {TASK_UUID} , however for some use cases this is not enough.
For example, If i want to create a key binding to show all open tasks in the project of the currently selected task, I need to either:

Have a replacement for TASK_PROJECT:
rt=:next project:{TASK_PROJECT}

Have the ability to to do command substitution:
rt=:next project:task _get {TASK_UUID}.project<Enter>

The second one sounds pretty dangerous, so that will probably not happen.
I'm open to a PR that exposes other task properties -- it's not something I would spend time on myself at this point.
Finally, I'm wondering if a {TASK.[prop]} syntax would be better? That would provide more flexibility to task properties, without having to individually expose a bunch of new tokens. It would probably even support UDA fields as a bonus.

@thehunmonkgroup makes sense :+1:

I have implemented TASK_PROJECT locally as can be seen here, and wanted to send it as a PR, but I noticed that when the task didn't have any project, returning an empty string caused an error in the tasklib expression that crashed vit.
I do think the {TASK.[prop]} syntax is a better idea and supporting UDAs would be great!

@nfraprado, @mohamed-osama-aboelkheir see https://github.com/scottkosty/vit/pull/248
That seems to work fine, and it wasn't too hard to implement.

Since #248 using {TASK_PROJECT} works, so this issue can be closed.

So closing....


Spacing issue for all inline notifications

An extra space must be introduced between the notification title and the description. Here is an example.

Hi @shailaskumar, as per our docs , we haven't really specified any spacing. The spacing seems visually adequate but it can be revisited incase of inconsistencies.

Thank you @alina-jacob The spacing issue that I am referring to is before the description. For example, "The server instance..." It looks like there is no space between the bold text and regular text.


Xamarin developers can maximize code shared across all platforms

o	Create a consistent cross-platform application lifecycle model M P1
o	Write cross platform application startup code to register of services, vendor controls, libraries, components S P1
o	Xamarin.Forms and Xamarin.Essentials will be combined to become Xamarin 6 and reduce API overlap S P0
o	Remove obsoleted code to improve developer clarity and reduce maintenance costs S P1
o	Combine Essentials codebase with Forms and reduce API overlap
o	Add multiple window support to applications L P0
o	Gesture recognizer implementations should be consistent across platforms XL P2
o	Accessibility features are easily accessed at a cross-platform level L P1
o	Support drag & drop in applications from shared code L P1

I apologise if this is not meant to be open for public discussion. I haven't seen this repo mentioned publicly, but I ended up here after following a discussion on a ticket elsewhere (dotnet/runtime probably).

Xamarin.Forms and Xamarin.Essentials will be combined to become Xamarin 6 and reduce API overlap

Will this still produce a separate Nuget package for Essentials? I can definitely see the benefit of Forms depending on Essentials, and having them in the same repo could make things simpler. But I also work on some non-Forms projects that are unlikely to ever adopt Forms, but do use Essentials.

Xamarin Tools comments... There might be some icon, layout changes in the solution explorer resulting from this.