Feature Request: extra768 Only check latest version of ECS task definition

When running extra768, prowler checks ALL versions of a task definition.
Since we cannot delete specific task definitions from AWS, even if we fix the issue, prowler will still fail:
7.68 [extra768] Find secrets in ECS task definitions variables (Not Scored) (Not part of CIS benchmark)
INFO! Looking for secrets in ECS task definitions' environment variables across all regions...
FAIL! us-west-2: Potential secret found in ECS task definition XXX--celery_inspect:1 variables
FAIL! us-west-2: Potential secret found in ECS task definition XXX--celery_inspect:2 variables
PASS! us-west-2: No secrets found in ECS task definition  XXX--celery_inspect:3 variables
Is there a way to say "only check the latest version" of a task definition?

I quickly looked at how to get this information, and it's not trivial with Bash (especially if you're using bash 3.X, since that version does not support hashmaps).
I think the solution would be to have the checks/check_extra768 call an inline python script to figure that out.  Just my 2 cents, if you decide to support this enhancement.

How would you do that in bash 4? and in python? We can add that inline python code, that's not a big deal, people love python :)
If you give me info/steps to reproduce it I can try as well. Thanks!

I created a PR by what I mean by a python script to get the latest version:
https://github.com/toniblyx/prowler/pull/560
It's rough around the edges (and helper scripts are probably not in the right spot), but it's a start.

I'm all for Python, but just wondering if it's definitely needed here? Could it be achieved by calling list-task-definition-families to get the set of all families, and then for each family, calling list-task-definitions --family-prefix <family> --sort DESC using --max-items 1 or jq to just get the first result. This is on the basis that the docs for --sort say
Setting this parameter to DESC reverses the sort order on family name and revision so that the newest task definitions in a family are listed first.

You are absolutely right.
I updated the PR with your ideas: https://github.com/toniblyx/prowler/pull/560

#560 merged, thanks @grayaii


Project 4: Refactor with hooks.

Project 4: Refactor with hooks.
In this PR, I have implemented:-

Followed the correct Gitflow without linter errors
Refactored the Calculator component from a class-based component to a functional component with hooks.

Thank you @peterrobert for your feedback and approval.


If there is a pending order and delete that product. On the admin panel order history page, it continues to load but is not able to view the listing.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
master
Issue Description
If there is a pending order and delete that product. On the admin panel order history page, it continues to load but is not able to view the listing.
Preconditions

Admin should be logged in.
Admin should have at least one product

Steps to reproduce

Log in as Admin
Click on 'Sales/Orders'
See the error

Expected Result
should be shown the order listing.
Actual Result
not showing the listing. it continues to load. Here
Screenshots
No response
Additional context
No response

Now, this issue is fixed. so I am closing this issue.
And I have attached a screenshot Here, for future reference.


[Question] How to disable the filtering of cmp itself

I looked at the cmp-snip code and found the function source:complete(params, callback), which does the following steps (my guess) when I perform the completion:

the source:complete function is called, it gets all the fragment entries of the current file type, then it performs the show_condition function to filter, returning the filtered entries to nvim-cmp
nvim-cmp filters the returned information again according to 'line_to_cursor
Display the filtered entries

Now I want to write my own filtering logic in the show_condition function, then I don't want step 2 to be executed, how should I do it, thanks
function source:complete(params, callback)
    -- vim.api.nvim_err_writeln('11')
	init_options(params)

	local filetypes = require("luasnip.util.util").get_snippet_filetypes()
	local items = {}

	for i = 1, #filetypes do
		local ft = filetypes[i]
		if not snip_cache[ft] then
			-- ft not yet in cache.
			local ft_items = {}
			local ft_table = require("luasnip").get_snippets(ft, {
				type = "snippets"
			})
			if ft_table then
				for j, snip in pairs(ft_table) do
					if not snip.hidden then
						ft_items[#ft_items + 1] = {
							word = snip.trigger,
							label = snip.trigger,
							kind = cmp.lsp.CompletionItemKind.Snippet,
							data = {
								filetype = ft,
								snip_id = snip.id,
								show_condition = snip.show_condition,
							},
						}
					end
				end
			end
			snip_cache[ft] = ft_items
		end
		vim.list_extend(items, snip_cache[ft])
	end

	if params.option.use_show_condition then
		local line_to_cursor = params.context.cursor_before_line
		items = vim.tbl_filter(function(i)
			-- check if show_condition exists in case (somehow) user updated cmp_luasnip but not luasnip
			return not i.data.show_condition or i.data.show_condition(line_to_cursor)
		end, items)
	end

	callback(items)
end

You should use filterText.
Currently, nvim-cmp does not provide the disabling nvim-cmp's filtering process.

I can't find any option for 'filterText' in the help file, can you give me some more hints?

You should use filterText. Currently, nvim-cmp does not provide the disabling nvim-cmp's filtering process.

I can't find any option for filterText in the help file, can you give me some more hints?

See this thread https://github.com/hrsh7th/nvim-cmp/issues/1179

See this thread #1179

Thank you, it works fine now!


Production items not autocombining in queue

I went to the production templates screen and tried to add a few min terraforms to the existing one in the template. Normally, this should add it to the existing one (resulting in a single order for min terraform 2%), but it ended up resulting in a separate order instead.
Obviously very low impact but would be nice to see it fixed eventually.

After doing some testing, it appears this only happens when editing the default production template. Beats me why.


Mojo::UserAgent: Issues with EV

Running the following one liner generates a lot of warnings related to EV:
$ perl -MMojo::UserAgent -e 'Mojo::UserAgent->new->get("http://mirror6.bjtu.edu.cn/archlinux/core/os/x86_64/core.db.sig")'
setsockopt() on closed socket GEN0 at /usr/share/perl5/vendor_perl/Mojo/IOLoop/Client.pm line 80.
Use of uninitialized value in hash element at /usr/share/perl5/vendor_perl/Mojo/IOWatcher.pm line 72.
Use of uninitialized value $fd in hash element at /usr/share/perl5/vendor_perl/Mojo/IOWatcher/EV.pm line 18.
Use of uninitialized value in subroutine entry at /usr/share/perl5/vendor_perl/Mojo/IOWatcher/EV.pm line 27.
Timer b26b800edf0eaf3616d25372a4b9fee0 failed: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/vendor_perl/Mojo/IOWatcher/EV.pm line 27.
Use of uninitialized value in delete at /usr/share/perl5/vendor_perl/Mojo/IOWatcher/EV.pm line 33.

$ mojo version
CORE
  Perl        (5.014002, linux)
  Mojolicious (2.43, Leaf Fluttering In Wind)

OPTIONAL
  EV                       (4.03)
  IO::Socket::IP           (0.07)
  IO::Socket::SSL          (1.44)
  Net::Rendezvous::Publish (not installed)

Cannot reproduce on trunk:
CORE
Perl        (v5.14.1, darwin)
Mojolicious (2.46, Leaf Fluttering In Wind)
OPTIONAL
EV                       (4.03)
IO::Socket::IP           (not installed)
IO::Socket::SSL          (1.53)
Net::Rendezvous::Publish (not installed)

Just for the reference: the issue was caused be using IO::Socket::IP. After removing this model, the issues was "fixed".


Handle templated values as yaml data

Description:
Interpret templated service data as yaml values
If we use data_templates in the config, the whole service data will be
interpreted as templates. Since templates work only on strings it is
not possible to have other datatyes in templated service datas. This
causes problems on services, that rely on the correct data type given
by the user (as the pilight send service for example).
This fixes this issue by interpreting the templated value again as yaml
document. So a "evaluated" yaml number will be a number again instead
of a string.
This belongs to bug #5042 and #5043.
Related issue (if applicable): fixes #5042
Example entry for configuration.yaml (if applicable):
    service: pilight.send
    data:
      "off": 1
      protocol: elro_800_switch
      unitcode: 0
      systemcode: 8

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

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

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

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

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

We should not do this.
This is too unpredictable to the user what is happening. For example returning 'on' all of a sudden becomes True.
Instead, you could use voluptuous schemas on services to coerce the value to the right type.

@balloob Sadly a voluptuous scheme seems not to be possible fro a service like pilight.send. At least the discussion in bug #5043 leads to nothing.
I think, at least pure number values should remain numbers in data_templates. Baybe we can look at projects like ansible how they handle this?

@janLo Honestly your use case is very special (template resending data depending on data) and easy to work around (just define this rule for each device). If you find templating not powerfull enough you can also give AppDaemon a try? I think we should not rush features for rare cases at the expense of stability and maintainability.

Well, templates are not useable at all with pilight at the moment. As soon as there is any argument, which is a number in the pilight protocol we send wrong data if we use a data_template (no matter if we template the actual number or some other value). And the daemon then simply rejects it without telling what is wrong. This is unclear for the user and almost impossible to debug without instrumenting the code.
So either we fix this bug in any place or we should at least state a warning in the pilight component documentation, that the service does not work with templating at all.

@balloob Wouldn't be converting on to true exactly what the user expect? I mean, you can always put it in quotes.

No, that's not at all what the user expects. YAML has a lot of things that it converts that are not predictable. It's too much to teach the user and it is not feasible.
@DavidLP is right here that it only serves a small edge case. We have to think for the bigger picture and it is a change that will only lead to a lot of confusion.

@janLo I think if you find a way to allow explicit type conversion in templates instead of doing implicit type conversion defined by YAML this could be a usefull feature. I do not know how templating is implemented and even if this is feasible. But I could imagine something like:
{{int(senor.value)}}

@DavidLP this is not possible. It is not even possible to have an actual int without any templating and leave it an int. As soon as you use data_template you lose all type information and it's just text.
I don't really understand why we saw, it's OK for the user to understand that their service data is converted via the yaml parser with all the special yaml conversation but the template_data is not. I find it inconsistent, @balloob. But OK. Then please add a warning to the pilight documentation that it does not work with data templates at all.
I'm sad that I've to maintain a fork of ha to fix this bug and make this "edge case" work.

https://github.com/home-assistant/home-assistant.github.io/pull/1750

@janLo Wouldn't combing data and data_template fix your problem?
One of my scripts as an example:
office_worklight:
  sequence:
    - service: light.turn_on
      data:
        entity_id: light.desk_lamps
        rgb_color: [211, 191, 157]
        transition: 5
      data_template:
        brightness: '{{ brightness }}'

Not if I need the templated data as an int - for example if I want to choose the device depending on the event.


Fix NPE in events when no assigned topics

java.lang.NullPointerException: null
at java.util.ArrayList.<init>(ArrayList.java:177) ~[na:1.8.0_131]
at org.springframework.kafka.event.NonResponsiveConsumerEvent.<init>(NonResponsiveConsumerEvent.java:51) ~[spring-kafka-1.3.1.BUILD-SNAPSHOT.jar:na]

cherry-pick to 2.0.x, 1.3.x

... and cherry-picked to 2.0.x.
Back ported to 1.3.x as https://github.com/spring-projects/spring-kafka/commit/d06db1f1f2eb6f5402e74b581e28b9c7f8f88928 after resolving conflicts in the ListenerContainerIdleEvent


How to run SuperSet ouside the Virutal Environment

I have installed superset on in python virutal env, now i don't want to activate the environment every time to run Superset
I am running the following command
gunicorn -w 5 --timeout 120 -b <IP_ADDRESS>:8088  "superset.app:create_app()"
It works fine when inside the virutal env, but outside it throwing me this error:
ImportError: No module named superset.app
How i can run superset outside the virtual env and i am also running celery worker.

is this issue resolved?


rm: linux-extending: Add important note to FEATURES

Add a note that changing those variables result in significant change to the final artifact

Docs for e02f0bf1fbfee844f2d992c477f261e691d5862e are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2282/docs/artifacts/html/index.html

Docs for 7e851e8faf7c800ab7ebaa3fff97eb4998598919 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2288/docs/artifacts/html/index.html

@kprosise , changes done

Docs for 0c4c12575c0b0cecbc04fbce1dc177fe3eeada2c are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2289/docs/artifacts/html/index.html


Fix #8 General Localization - README

@auremoser The README-ch.md is in Chinese Language. Please review it!

@auremoser Thank you for the review! Review for Chinese language is difficult! Hindi is a second largest language spoken by Indians! So, I have made the Readme in Hindi! I know Hindi Language (Reading and Writing). If you are fine then we can merge it!

@auremoser surely will add that :)

Great job done with hindi language and updating the general readme.md file.
Two questions:
a) Dont think that is better delete the file finishing with ~ character? (it seems like used to be a temporary file)
b) With last update in the general readme.md file, it looks very diferent of the portuguese version, do you people think it is ok leave as is or change it to make a real translation of the new english version?

Hey @elionaimc !
@AnamikaD did the translation 🎊  to her!

a) Dont think that is better delete the file finishing with ~ character? (it seems like used to be a temporary file)

Yes, usually, what file are you referencing? I try to update the .gitignore file with unwanted commit files

b) With last update in the general readme.md file, it looks very diferent of the portuguese version, do you people think it is ok leave as is or change it to make a real translation of the new english version?

Good point, yes we changed the README in English and never updated the Portuguese equivalent for lack of experience with Portuguese. I'll add it as an issue to update the Portuguese readme.
Thank you for your comments!

I just removed the hidden file, thanks @elionaimc !

Great!
I will start working with README portuguese translation right now!


SparsePauliOp.apply_layout should do nothing if given None

What should we add?
Simulators give None for the layout when a circuit goes through the transpiler.  Currently this raises in SparsePauliOp.apply_layout.  Rather, it would be nice if None is a null op in apply_layout so that I can run the same code for a sim and a real backend.

From my understanding, the only change will be in the apply_layout function by adding the case for a null layout (in which case the function should do nothing). If this is good for a first issue I would like to help with this one :)

It is a good first issue, at least in my mind.

I've assigned this issue to you @SoranaAurelia

@mtreinish I think it's solved is it?

What behaviour would we expect here if num_qubits is given and is not equal to the number of qubits in the initial operator?  My first thought is that that must be an error, but I'm not certain.

I would also expand the operator.

Personally I'm not a fan of implicitly assuming that the given qubits are the "low" indexed ones - that's the kind of thing a layout is supposed to tell you - but looking at the code, it seems like we've already made that assumption, so it's most consistent to extend it to this case as well.  Thanks both.


Evaluate Catch2 as an alternative to Qt Test

Catch2 is a great test framework and the switch over is in progress.

Added in f9bf4c36780d571a3b2c5e220202423580dd74bb


Different methods of labeling for Computer Vision tasks

Is your feature request related to a problem? Please describe.
I don't want to have to click so often
Describe the solution you'd like
A drag tool would be great. semi-automated labeling would also be nice
Describe alternatives you've considered
coco-annotator](https://github.com/jsbroks/coco-annotator)

@imjwang we're working on improved object detection with less clicking required for the 1.1 release, visible in the roadmap: https://github.com/orgs/heartexlabs/projects/1
It should be available soon, but some of the functionality includes double click to create a bounding box or shape.

We support interactive pre-annotations now, check this article: https://labelstud.io/blog/release-130.html


Configuring default target branch

When having set up your branches to always track the same remote, running tests against the master (to test all commits in your branch) is a bit cumbersome.
You always have to run git test -v HEAD ^origin/master
It'd be nice to be able to set a default target branch/commit to test against, or a shorthand to test all commits since the merge-base


solve problem by multiple solvers

Description
As @erelsgl suggested in discussion #1522,
in some problems, some solvers may be better than others, but they might also fail with a SolverError.
Therefore, we've added a new method that allows sending a list of solvers rather than just one.
This function tries them in the order they are provided, and return the first solution for which no SolverError is raised.
Issue link: #1529
Type of change

[x] New feature (backwards compatible)
[ ] New feature (breaking API changes)
[ ] Bug fix
[ ] Other (Documentation, CI, ...)

Contribution checklist

[ ] Add our license to new files.
[x] Check that your code adheres to our coding style.
[x] Write unittests.
[x] Run the unittests and check that they’re passing.
[ ] Run the benchmarks to make sure your change doesn’t introduce a regression.

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

@PTNobel thank you for all your suggestions!

Overall I'm positive on this but not a huge fan of the current public API. I left my suggestions. Aditionaly, I don't like solve_multiple_solvers, could we call the method solve_via_chain, solve_with_fallback, try_solve, or try_solve_till_success? I think Stephen Boyd often uses the term solver chain for this feature; I can ask him next week.

That would be great, thanks!

Stephen said we should call it a "solver path" in the documentation; he also suggested making it a keyword argument to .solve instead of a new public function (maybe .solve(path=[...]). I'm wondering if maybe we could just specifialize on if the input is a string or a list to make .solve(solver=[cp.SCS, cp.CLARABEL]) the API. Thoughts on that @SteveDiamond @phschiele ?

I’m not sure about “path” as a keyword argument. I’d be in favor of
“solver_path” or “solver_priority” for keyword arguments to prob.solve.
On Mon, Jun 3, 2024 at 7:20 PM Parth Nobel @.***> wrote:

Stephen said we should call it a "solver path" in the documentation; he
also suggested making it a keyword argument to .solve instead of a new
public function (maybe .solve(path=[...]). I'm wondering if maybe we
could just specifialize on if the input is a string or a list to make .solve(solver=[cp.SCS,
cp.CLARABEL]) the API. Thoughts on that @SteveDiamond
https://github.com/SteveDiamond @phschiele
https://github.com/phschiele ?
—
Reply to this email directly, view it on GitHub
https://github.com/cvxpy/cvxpy/pull/2450#issuecomment-2146284194, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACRLIFCZAUD7QOITPGPDR7TZFT24BAVCNFSM6AAAAABH7TE5E2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBWGI4DIMJZGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I’m not sure about “path” as a keyword argument. I’d be in favor of “solver_path” or “solver_priority” for keyword arguments to prob.solve.

Fair! I don't like solver_priority since we fallback to the other solvers instead of giving up, so I think solver_path would be a good choice.

What if both "solver" and "solver_path" are given?

I think that should raise a runtime error.

That should raise a ValueError
On Wed, Jun 5, 2024 at 2:39 AM Parth Nobel @.***> wrote:

I think that should raise a runtime error.
—
Reply to this email directly, view it on GitHub
https://github.com/cvxpy/cvxpy/pull/2450#issuecomment-2148996445, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACRLIFC22NDBTSI3NOFMKCDZF2XCHAVCNFSM6AAAAABH7TE5E2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBYHE4TMNBUGU
.
You are receiving this because you commented.Message ID:
@.***>

Stephen said we should call it a "solver path" in the documentation; he also suggested making it a keyword argument to .solve instead of a new public function (maybe .solve(path=[...]). I'm wondering if maybe we could just specifialize on if the input is a string or a list to make .solve(solver=[cp.SCS, cp.CLARABEL]) the API. Thoughts on that @SteveDiamond @phschiele ?

How would this work when you have solver specific arguments to the solve method?

Stephen said we should call it a "solver path" in the documentation; he also suggested making it a keyword argument to .solve instead of a new public function (maybe .solve(path=[...]). I'm wondering if maybe we could just specifialize on if the input is a string or a list to make .solve(solver=[cp.SCS, cp.CLARABEL]) the API. Thoughts on that @SteveDiamond @phschiele ?

How would this work when you have solver specific arguments to the solve method?

Could be .solve(solver=[(cp.SCS, scs_args), (cp.CLARABEL, clarabel_args)]) but it might be getting complicated at this point.

I've made some changes according to your suggestions. Does this meet your expectations?

I like this PR with Oriya's changes. Since this is a change to the public API, let's get maintainer consensus on this proposal before writing the new docs and merging.

This approach looks good to me.

We're still missing the documentation for solve. Right now, only the private method is documented.

This does needs some docs. Certainly it should be added to the .solve docstring and added to this page: https://www.cvxpy.org/tutorial/solvers/index.html Maybe as a new section title "Solver paths" that discusses how this provides a fallback on failure to solve.

I hope I've placed the documentation correctly.
If any adjustments are needed, please let me know.
Thank you!

Hi, could you clarify what the tuple[str] case is for? Don't the str and tuple[str, dict] cover all cases, i.e. either no solver specific options, or some options?

Hi, could you clarify what the tuple[str] case is for? Don't the str and tuple[str, dict] cover all cases, i.e. either no solver specific options, or some options?

Hi @jonathanberthias,
Perhaps it should be written as tuple[str,] to indicate that the type is a tuple containing only str.
The list items can be in three formats:

tuple of (str, dict), such as ('OSQP', {'max_iter': 10000}).
tuple of (str,), such as ('CLARABEL',).
string, such as 'CLARABEL' or ('CLARABEL')

Thanks @oriyalperin for answering so quickly!
What I meant was, when would it be useful to use the 1-str tuple form (option 2. in your list)? As I see things, I either want to pass solver-specific options and would use option 1., or I don't in which case option 3. is perfect. And if I am writing some generic code where I sometimes want solver-specific options and sometimes not, then I can use option 1. with a perhaps empty dictionary.
But in no case I could think of would it be useful to pass the solver name in a tuple. 🤔

@jonathanberthias it would be useful only if the tuple contains multiple strings, e.g., ("CLARABEL", "ECOS").
On that note, though, let's update the documentation of both functions to use Iterable instead of tuple/list.

Thanks @oriyalperin for answering so quickly!
What I meant was, when would it be useful to use the 1-str tuple form (option 2. in your list)? As I see things, I either want to pass solver-specific options and would use option 1., or I don't in which case option 3. is perfect. And if I am writing some generic code where I sometimes want solver-specific options and sometimes not, then I can use option 1. with a perhaps empty dictionary.
But in no case I could think of would it be useful to pass the solver name in a tuple. 🤔

I agree, it's not necessary at all, it was just to offer an alternative option.
Thanks for pointing that out, I'll remove it.

@phschiele,

I need some clarification, does that require supporting all iterable types (dict, str...)?
Replacing tuple with Iterable - the tuple is only used as an inner type. Do you want to replace it in that context?

On that note, though, let's update the documentation of both functions to use Iterable instead of tuple/list.

@phschiele if we use iterable, we also implicitly allow solvers to be a string (an iterable of chars), which is of course incorrect. So maybe it is better to allow only list?

On that note, though, let's update the documentation of both functions to use Iterable instead of tuple/list.

@phschiele if we use iterable, we also implicitly allow solvers to be a string (an iterable of chars), which is of course incorrect. So maybe it is better to allow only list?

I concur that we should not allow str. I support requiring an explicit list.

I was suggesting
Iterable[tuple[str, dict] | str]

which a single string does not satisfy.
Requiring a list is also fine with me.

Thank you for your feedback and reviews! I really appreciate it.

@SteveDiamond did you have outstanding TODOs or can I merge this?


add the missing commit of PR 301

There are some commits of PR #301  missing in feature branch pipeline_refactor.
The PR syncs the differences.
@panpan0000 @iceiilin

BUILD on-build-config #914 : FAILURE


Add fix for issue #41

Add fix for:
[adsbexchange-stats] /usr/local/bin/json-status: line 299: vcgencmd: command not found

This is due to this inclusion by the adsbx team: https://github.com/adsbxchange/adsbexchange-stats/blob/50035d990a6270be9edfea30655558d9c89fa1cb/json-status#L299
I've experimented with adding vcgencmd to the image, however without presenting the device /dev/vchi into the container, the vcgencmd command errors with:
VCHI initialization failed

My proposed solution is:

During image build, modify the adsbexchange-stats/json-status script with sed to change STATUS=$(vcgencmd get_throttled) to STATUS=$(vcgencmd_get_throttled_wrapper.sh)
Create vcgencmd_get_throttled_wrapper.sh that attempts to call vcgencmd get_throttled.

If the exit status of vcgencmd is not 0, or of vcgencmd doesn't exist, then spoof the output with throttled=0x0
If the command works (ie, user is on RPi and has forwarded the /dev/vhci into the container), then use that output.

Further fix at https://github.com/mikenye/docker-adsbexchange/commit/842b85a6d4b77feb76d16cd2c08e72e2ac535e27


[image_picker] return thumbnail image for pick video functionality

It would be great to have a plugin for generating a video thumbnail from video files as a preview.

image_picker can be extended to return a thumbnail image for "pick video" functionality.
PickedFile can return path, bytes but also os filename and a thumbnail if the file is a video.
You can use content resolver to do this on Android. See:
https://developer.android.com/reference/android/provider/MediaStore.Video.Thumbnails for API < 29 and https://developer.android.com/reference/android/content/ContentResolver#loadThumbnail(android.net.Uri, android.util.Size, android.os.CancellationSignal) for the most recent API.

Was the initial request related to image_picker, or was it about wanting to be able to generate a thumbnail for an arbitrary video file that an app already has a path to (with permissions)? Those are very different features.

Any updates?

Absent clarity on what exactly is being requested here, closing.


Build -- Change project structure

    Pull Request #6 has been updated with:

    - 14441 changes

    - 14125 additions

    - 316 deletions

    Pull Request #6 has been updated with:

    - 14441 changes

    - 14125 additions

    - 316 deletions

    Pull Request #6 has been updated with:

    - 14422 changes

    - 14113 additions

    - 309 deletions

    Pull Request #6 has been updated with:

    - 14480 changes

    - 14171 additions

    - 309 deletions

    Pull Request #6 has been updated with:

    - 14480 changes

    - 14171 additions

    - 309 deletions

    Pull Request #6 has been updated with:

    - 14481 changes

    - 14171 additions

    - 310 deletions

    Pull Request #6 has been updated with:

    - 14370 changes

    - 14060 additions

    - 310 deletions

    Pull Request #6 has been updated with:

    - 14346 changes

    - 14035 additions

    - 311 deletions

    Pull Request #6 has been updated with:

    - 14321 changes

    - 14010 additions

    - 311 deletions

    Pull Request #6 has been updated with:

    - 14429 changes

    - 14118 additions

    - 311 deletions

    Pull Request #6 has been updated with:

    - 14440 changes

    - 14124 additions

    - 316 deletions

    Pull Request #6 has been updated with:

    - 14439 changes

    - 14123 additions

    - 316 deletions

    Pull Request #6 has been updated with:

    - 14440 changes

    - 14124 additions

    - 316 deletions

    Pull Request #6 has been updated with:

    - 14441 changes

    - 14125 additions

    - 316 deletions


[review] conformation v configuration

We seem to be using configuration and conformation pretty much interchangeably in the manuscript ( I suspect whoever wrote a section has a favourite term here). Should this be made more uniform? Thoughts anyone?

I have seen both terms used interchangeably, and I'd bet your suspicion is correct. I would say we should adhere to strict definitions to avoid potential confusion. I propose the following definitions:

Conformation: Positions and specific geometry of molecular structures, can refer to physical atoms/bonds/angles/etc.
Configuration: A set of options or choices made by the scientist or software about how a system is setup, run, physical conditions, alchemical paths, etc.

The only place I think it could be confusing is in the overloaded word "configuration" to also mean "set of options" which is why I proposed those definitions. I doubt that confusion would happen in the paper based on the context in which each word appears, but no harm in unifying it.

Interesting. I think it very much depends if you are a statmech person or a chemistry person. Because I would have said that a configuration is the spatial positions and conformation is more broadly a shape. I have never really thought about it though. I think your suggestion makes sense. And yes a configuration is also how you configure your software, but I would have not used it in this context probably. Anyone else got thoughts on this?

Should we just say they are used interchangeably to refer to the 3D coordinates of the system at given point in time?  I guess the one point of ambiguity is if "conformation" is being used as label for a bunch of 3D coordinates that together represent a metastable state.

we just say they are used interchangeably

That might be a better approach. Since this is meant to be a best practices paper, telling readers they could encounter both in the wild would be helpful. I still say we unify it throughout this paper just to unify the language more.

I would have said that a configuration

I also would say configuration over conformation in my own writing. My definitions above were to minimize any ambiguity independent of reader background.

Yes, I can’t really put into words what a difference would be. I think what Levi is describing with configuration I would call parameters.
Saying that they are both used interchangeably is probably best seeing as there’s no clarity!

Yes, I can’t really put into words what a difference would be. I think what Levi is describing with configuration I would call parameters.

I had exactly the same thought, but then thought parametrisation is also not quite right.

Saying that they are both used interchangeably is probably best seeing as there’s no clarity!

I may use configuration for when talking about position vectors, but will point out that there is mixed use.
Thanks for the input!

I believe chemists use conformations to mean different geometries with the same topology (so no bond breaking) and configurations instead include all possible geometries of the atoms (including those with different bond topologies). In stat mech the two are often interchangeable because we just integrate over the full Boltzmann distribution determined by a force field potential that doesn't allow bond breaking. I'm not a chemist though so I might be completely wrong.

Agree with @mrshirts here . Configuration = one microstate defined by position vector (hence configuration integral or configurational integral). Conformation = ambiguous meaning that depends on the context.

I updated the manuscript accordingly.


Fix empty JSON file for AFF based objects

Fixes: https://github.com/abapGit/abapGit/issues/6765

is it possible to add a unit test for this?

is it possible to add a unit test for this?

Possible: Sure. But I am not familiar with the test in this class. And to be honest I might not find enough time for that.
Would be great if maybe @mbtools could contribute a unit test.

I just wanted to quickly fix this bug.

This could have been caught by CI but I'm still missing a system where AFF is supported.
Hopefully, next release of ABAP Dev Edition will work.


Amplify LambdaInternal throttle

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v12.22.1
Amplify CLI Version
5.3.0
What operating system are you using?
Mac
Amplify Categories
function
Amplify Commands
push
Describe the bug
Hello,
I am trying to push all the latest changes to my environment and sync up with what the rest of the team has and I am getting endless throttle exceptions.
It seems to be something related with legacy lambda layer functions.
I just keep getting the below error over and over.
CREATE_FAILED      LambdaLayerPermissionPrivateLegacy63  AWS::Lambda::LayerVersionPermission Tue Aug 10 2021 17:21:21 GMT-0700 (Pacific Daylight Time) Rate exceeded (Service: AWSLambdaInternal; Status Code: 400; Error Code: ThrottlingException; Request ID: d6273ab7-afc3-4d6f-b8a6-e5e33bf28b9b; Proxy: null)

I am basically blocked on development unless I create a brand new environment.
Expected behavior
amplify push works
Reproduction steps
amplify push
GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

Hi @gakinson
From the error  LambdaLayerPermissionPrivateLegacy63  AWS::Lambda::LayerVersionPermission Tue Aug 10 2021 17:21:21 GMT-0700 (Pacific Daylight Time) Rate exceeded (Service: AWSLambdaInternal; Status Code: 400; Error Code: ThrottlingException;
It seems you have a lot of stale layers in the project as version is close to 63. Can you try to remove some of the stale layers using ```amplify remove function`` and then selecting those stale layers.
Let me know if this works for you?

I got another error:
Cannot read property 'filter' of undefined
TypeError: Cannot read property 'filter' of undefined
    at /Users/geoffreykinson/.nvm/versions/node/v12.22.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/src/provider-utils/awscloudformation/utils/layerHelpers.ts:248:33
    at Array.filter (<anonymous>)
    at Object.getLambdaFunctionsDependentOnLayerFromMeta (/Users/geoffreykinson/.nvm/versions/node/v12.22.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/src/provider-utils/awscloudformation/utils/layerHelpers.ts:245:45)
    at Object.removeWalkthrough (/Users/geoffreykinson/.nvm/versions/node/v12.22.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/src/provider-utils/awscloudformation/service-walkthroughs/removeLayerWalkthrough.ts:25:43)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at Object.run (/Users/geoffreykinson/.nvm/versions/node/v12.22.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/src/commands/function/remove.ts:30:29)
    at Object.executeAmplifyCommand (/Users/geoffreykinson/.nvm/versions/node/v12.22.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/src/index.ts:251:3)
    at executePluginModuleCommand (/Users/geoffreykinson/.nvm/versions/node/v12.22.1/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:177:3)
    at Object.executeCommand (/Users/geoffreykinson/.nvm/versions/node/v12.22.1/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:29:5)
    at Object.run (/Users/geoffreykinson/.nvm/versions/node/v12.22.1/lib/node_modules/@aws-amplify/cli/src/index.ts:151:5)

Hi @gakinson
Can you share  <root>/amplify/backend/amplify-meta.json  by redacting any secret info?

My workaround was to go into my lambda layer in console and delete them manually (used script actually), then do amplify env checkout, then modified the lambda layer, then did a push.

Hey @gakinson :wave: can you try running amplify remove function to remove some of the older layer versions?

Closing due to inactivity. @gakinson if you are still experiencing this issue with the latest version of the CLI please reply back to this thread and we can re-open to investigate further 🙂


How to get in touch regarding a security concern

Hey there!
I belong to an open source security research community, and a member (@akincibor) has found an issue, but doesn’t know the best way to disclose it.
If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.
Thank you for your consideration, and I look forward to hearing from you!
(cc @huntr-helper)

Feel free to report your findings here.
We have also been in contact over main, you can send us any details there.
We have yet to receive any information about what issue this is.

As we have renamed the org from AsynkronIT to asynkron, this opened up a security issue that someone could have registered the old org name and exploited any reference to those URLs.
We have no registered the old org name ourselves, preventing this from happening.
Also the new code of Proto.Actor only refers to the updated org name.
Many thanks to @JamieSlome for reporting this

@rogeralsing - thanks for following up 👍
Just for reference, the report can be found here. It is currently private, but if you could provide your assessment on the report using the maintainer controls, that would be much appreciated (@rogeralsing).


Document Typography Scale on Button

Please note that it appears that setting typography sizes on button breaks it's internal layout when an icon is present. The attached screenshot demonstrates changes I made to the (hard-coded) shadow styles in order to acheive a fix in a particular instance:

cc: @asyncLiz
https://github.com/material-components/material-components-web/issues/5812

That issue isn't about the line-height, but the explicit width, height, and font-size specified on icon elements in MDC.
It'd be somewhat related to https://github.com/material-components/material-components-web-components/issues/81 and density, but only if the icons are bigger than 36px. tl;dr, we need to override those lines to use var(--mdc-icon-size) as well if it's going to be customizable.


[VS Code] Sign-in failed.

Error:
Sign-in failed.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.2.399

protocolVersion
2.1

applicationName
VSCode

applicationVersion
1.22.2

platformName
MacOS

platformVersion
17.5.0

@BobbyBerberyan This appears to be a dupe of #220.

Hi Chuck,
Appreciate you helping out with this.  Please see attached.
Thanks!
On Fri, Apr 20, 2018 at 9:54 AM, Chuck Lantz<EMAIL_ADDRESS>wrote:

@BobbyBerberyan https://github.com/BobbyBerberyan This appears to be a
dupe of #220 https://github.com/MicrosoftDocs/live-share/issues/220.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/live-share/issues/221#issuecomment-383157557,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNBAOivNQ3PvlEOy1QzEkRsszGmAV6rks5tqhLAgaJpZM4Tdx0B
.


[BUG] Error 773 (0x305) on commission

Reproduction steps
Using off-the-shelf Nanoleaf A19 bulbs.
Commission with Google's Android sample app.
I also rebuilt the Android libs off from recent CHIP with no change.
Can someone show me where error 773 (0x305) can be generated in the CHIP code at the point shown in the log?
If I can locate the point where the error code is generated I can debug more.
Error is line 573
773.log
The Nanoleaf bulbs are on Thread so this may be thread related.
Bug prevalence
2-3 times a week
GitHub hash of the SDK that was being used
5b4f8004662d00bdb111367fec7d3ea978c23372
Platform
android
Platform Version(s)
No response
Anything else?
This problem is intermittent and unpredictable. I can commission four identical bulbs, three will work, one will fail.

If that 0x305 is a CHIP_ERROR value (which is not obvious from the logging), that would be an SDK error, SdkPart == 3 = kASN1, and then 05 is:
#define ASN1_ERROR_INVALID_ENCODING     CHIP_ASN1_ERROR(0x05)

@bzbarsky-apple Check out line 247. That looks like subscription data. Is that data coming from the node we are commissioning?
My app is listening to MDNS for commissioned nodes. As soon as it sees one it subscribes to it.
Does CHIP turn on the MDNS announcement before it sends OnCommissioningComplete?  It is possible my subscription got in front of OnCommissioningComplete on this slow Thread network?  Also notice there are a lot of retransmissions right before the error at 573.
I am counting on seeing the MDNS announcement as a signal it is safe to access the node.

I believe I found the problem. I was using random numbers for my certificate serial numbers. Sometimes those numbers were negative. OpenSSL does not consider this an error and let me generate the certificates.  However, mbed SSL does flag it as an error. If you go read the x509 spec, the spec says they have to be positive.  So 773, 0x305 was the real error. This also explains why it would work on a retry. 50/50 the serial number was negative.
What was very confusing was how this error did not show up until the onCommissioningComplete() command


Add g and path tags to ignored tags list.

What the tags g and path?

@wf9a5m75 please check the referenced issue, classNameis not a string on those 2 tags.
https://developer.mozilla.org/en-US/docs/Web/SVG/Element/g
https://developer.mozilla.org/en-US/docs/Web/SVG/Element/path

Since I inserted different code, I close this PR. But thank you for your PR anyway.


DRILL-4694: CTAS in JSON format produces extraneous NULL fields

Changed behavior of JSON CTAS to skip fields if the value is null. Added an option "store.json.writer.skip_null_fields" to enable old behavior.

Updated

LGTM.  +1

Merged in 6286c0a


When trying to drag window with touch interface (WASM on mobile) get stuck in moving window state

I compiled using emscripten (latest pre-compiled release as of today) with the example app in the main readme for imgui-app.  I then hosted the resulting html/wasm/js and tested on my mobile phone.
When I give the top of an imgui window a series of taps, it then glues to my finger and I can move it, however, all subsequent taps move the window to the new tap's location and there is no way to stop tat from happening save from restarting the application (refreshing the page).
This does not happen on the live imgui emscripten example: https://www.dearimgui.org/webdemo/master/example_emscripten.html
Any tips on how to fix this?  I don't mind working on a fix and submitting a pull request if I can figure this out.

this must be a sokol issue somehow, I haven't test it so I can't provide that much info.  Have you looked into sokol repo to see if the issue comes from event handling there?

Ah I see, I initially thought thought the events were handled in this repo for some reason.  Ill close this for now, and update here if I find a workaround.

Here is the issue as observed highly detailed as an issue on the sokol page: https://github.com/floooh/sokol/issues/759
Includes video of problem, and my attempted work-arounds so far.

See the pull request to fix in sokol, this is a simple change anybody can make themselves int he meantime: https://github.com/floooh/sokol/pull/760

I just merged the fix. Many thanks again for the investigation and PR, @Xadiant!


[🐞] Index route / 404s on 0.17.3 when installed with Qwik City

Which component is affected?
Qwik City (routing)
Describe the bug
I am following the Qwik "Getting Started" documentation.
I follow the standard installation flow, i.e.
npm create qwik@latest
...
Select a starter > Basic App (QwikCity)
...

and execute npm run start after dependencies are installed.
I expect to see the "Welcome to Qwik" screen when viewing locahost:5173.
Instead, I see a 404 page.
Repeating the above steps, subbing npm create<EMAIL_ADDRESS>for ...@latest, results in my expected outcome.
Reproduction
https://stackblitz.com/edit/qwik-starter-9bdzzv
Steps to reproduce
Run npm create qwik@latest, choosing QwikCity as an installation option, then run npm run start.
System Info
System:
    OS: macOS 13.0.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 1.32 GB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.4.0 - /usr/local/bin/node
    npm: 8.12.1 - /usr/local/bin/npm
  Browsers:
    Firefox: 108.0.2
    Safari: 16.1
  npmPackages:
    @builder.io/qwik: 0.17.2 => 0.17.2
    @builder.io/qwik-city: 0.0.128 => 0.0.128
    undici: 5.16.0 => 5.16.0
    vite: 4.0.4 => 4.0.4

Additional Information
No response

I'm seeing 404s too on an old project I'm trying to upgrade from 0.14 to the latest 0.17. I get 404s on every route on 0.17.3 but a different issue (which is likely not relevant to this particular ticket) if I use 0.17.2 instead.

Yep, I just attempted to boot up a Qwik project just now and got 404 instead of the welcome page. Interestingly, npm run build npm run start works.

Sorry for the bad release! we are supporting two very different versions of QwikCity! please update to 0.17.3


Remove run_sequential function

This was useful for globalnet workaround, but since we've added support
to deploy in parallel with globalnet this isn't used anymore, so
removing it.

I wonder if we could make use of this to make GH actions an option. By having a global flag that lets you select sequential mode.
What do you think?

I wonder if we could make use of this to make GH actions an option. By having a global flag that lets you select sequential mode.
What do you think?

GH actions is being silly and i dont think the parallel deployment is whats causing it,
E.G. I see right now this
default netshoot-785ffd8c8-2zq2r 0/1 CreateContainerError 0 2m6s

I doubt deploying in parallel caused netshoot pod to go into CreateContainerError state..
Let's debug GH action and get to the root of it, it can't be that travis works well (most of the time) but it doesn't if they both use VMs.

Closing since its being used in post mortem (PR #132)


Allow extension to implement mention providers

It would be awesome if tui.editor could provide an interface for mention support like here on github with @.
From the API standpoint, I think it would be a good fit for an extensions, where I can register a trigger character like @ or # and a async callback which returns either a string array or a key value object, where the key is the display value and the value the final markdown.
If you think this extension would is not in the focus of your project or you do not have time for this feature, could you please give me some pointers on how to implement this feature myself.
Ages ago I used ment.io, maybe there is some inspiration there.
Thanks for your great work, I could integrate it well into my project.
Refs https://github.com/datenknoten/ngx-ssb-client/issues/11 https://github.com/datenknoten/ngx-ssb-client/issues/10

Sorry is this issue implemented somewhere?
Is this fixed in your commit @seonim-ryu ?

Not sure if this is related to #968 ?

FWIW, (not tested) someone seems to have solved it https://github.com/nillith/circle-plus/blob/master/src/client/app/modules/markdown/markdown.service.ts#L1-L5

A quick way to resolve this without the editor API would be adding a plugin with tributejs:
import Tribute from 'tributejs';

export default function mentionsPlugin(editor, options = {}) {
  const tribute = new Tribute({
    values: (searchTerm, cb) => {
      options.listSuggestions(searchTerm, (suggestions) => cb(suggestions));
    },
    noMatchTemplate: function () {
      return '';
    }
  });

  tribute.attach(editor.getUI().el);
}

and my list suggestion looks like:

listSuggestions: async function (
        searchTerm,
        renderList,
        denotationCharacter
      ) {
        console.log('Search Term', searchTerm);
        console.log(denotationCharacter);
        const matchedPeople = await suggestPeople(searchTerm);
        renderList(matchedPeople);
      }
async function suggestPeople(searchTerm) {
    const allPeople = [
      {
        key: 'Michael Soni',
        value: 'Michael Soni'
      },
      {
        key: 'William Bedi',
        value: 'William Bedi'
      },
      {
        key: 'Patrik Harrison',
        value: 'Patrik Harrison'
      }
    ];
    return allPeople.filter((person) => person.value.includes(searchTerm));
  }

A quick way to resolve this without the editor API would be adding a plugin with tributejs:
import Tribute from 'tributejs';

export default function mentionsPlugin(editor, options = {}) {
  const tribute = new Tribute({
    values: (searchTerm, cb) => {
      options.listSuggestions(searchTerm, (suggestions) => cb(suggestions));
    },
    noMatchTemplate: function () {
      return '';
    }
  });

  tribute.attach(editor.getUI().el);
}

and my list suggestion looks like:

listSuggestions: async function (
        searchTerm,
        renderList,
        denotationCharacter
      ) {
        console.log('Search Term', searchTerm);
        console.log(denotationCharacter);
        const matchedPeople = await suggestPeople(searchTerm);
        renderList(matchedPeople);
      }
async function suggestPeople(searchTerm) {
    const allPeople = [
      {
        key: 'Michael Soni',
        value: 'Michael Soni'
      },
      {
        key: 'William Bedi',
        value: 'William Bedi'
      },
      {
        key: 'Patrik Harrison',
        value: 'Patrik Harrison'
      }
    ];
    return allPeople.filter((person) => person.value.includes(searchTerm));
  }

'editor.getui ().el' I didn't find this API, this is how I bound it:

However, there are various bugs in the Markdown mode of the TUI editor, such as:

@mananjadhav Please take a look at it for me, if you can

FWIW, (not tested) someone seems to have solved it https://github.com/nillith/circle-plus/blob/master/src/client/app/modules/markdown/markdown.service.ts#L1-L5

The address has been lost

@seanwang1998 Unfortunately I am not working on it at the moment. Whatever I had I’ve put it on the comment earlier.


Add option for class prefix for easier styling

The developer would add a property such as classPrefix: 'c-form' to the forms module. This would then put that class on the form, but also use that as a prefix (with BEM structure) for the minor widgets and elements.
So the submit button would be set up to get the class c-form__submit, given the setting above.
This would avoid a lot of styling based on Apostrophe classes and data attributes.
All included widgets should get this treatment, as well as all significant elements (e.g., submit button, after-submit text).

Hey @abea  something I also noticed was that the submit button currently renders with no class whatsoever. adding an apos-forms-submit class for now to the module can simplify style it. Did it with no issue for the other parts of the form

My goal with this issue is to get away from styling using .apos- classes. Generally speaking I don't think that's a good idea on the project level. The ones that area already in this module are really just to make it somewhat usable out of the box.
If you'd like to contribute to resolving this issue I'd really appreciate it. It'd basically involve 1) setting a classPrefix option on apostrophe-forms-widgets, 2) telling apos-forms-base-input-widgets to look for that and set the same on itself, and 3) adding conditionals to the templates to include relevant classes on all the elements (e.g., prefix__label, prefix__conditional). The second part is probably the more advanced piece, but it's the same method as this.

Got it, that makes sense. I was curious as to why it didn't follow the format that you use elsewhere (like in open museum). Overall, my coding knowledge is limited, so this may be too advanced for me. Happy to give it a go though.

Yeah, Open Museum is an example of a fully fleshed-out project. These modules are intentionally kept pretty simple in terms of styling for people to add their own.

@abea I'm taking a stab at resolving this, but I think I'm missing something in translating what was done in the second step you listed above. So far I've got the field added to the apostrophe-forms-widgets module and in the apostrophe-form-base-field-widgets, I'm looping over the addFields to find the classPrefix field. Where I'm having issue is getting it added to the base-field-widgets, which I think is the goal. Here is my code thus far in the apostrophe-forms-base-field-widgets:
const forms = self.apos.modules['apostrophe-forms-widgets'];
const classPrefix = forms.options.addFields.find(field => {
  return field.name === 'classPrefix';
});

// While this does the job of getting the field in the input fields, it doesn't carry
// the value along set in the forms-widgets level.
options.addFields.push(classPrefix);

I think I'm on the right track in accomplishing this, but just not sure where I'm going wrong with the addition of the classPrefix to the input fields.

The prefix shouldn't be added to the form schema. It would be an option the dev sets, since the CSS would also be something the dev is writing. So step one isn't much of a task for resolving this, but documenting it would be.
The dev would set a classPrefix: 'acme' option in lib/modules/apostrophe-forms/index.js along with other options.
Then:

In lib/modules/apostrophe-forms-base-field-widgets/index.js in the construct function you'd look at that base module (apostrophe-forms) and see if it had the classPrefix option. Since the prefix will be used in the widgets only, it could also be an option directly on apos-forms-base-field-widgets to make that easier.
If it does, you'd pass that into the template via self.load (see below) in the apostrophe-forms-base-field-widgets construct function as well.

  // ...
  construct: (self, options) => {
    // Get classPrefix from apos-forms option...
    // ...

    const superLoad = self.load;
    self.load = (req, widgets, callback) => {
      _.each(widgets, (widget) => {
        if (classPrefix) {
          widget.classPrefix = classPrefix;
        }
      });
      return superLoad(req, widgets, callback);
    };
  },
  // ...

Then in templates you can start looking for it (data.widget.classPrefix?) and add it to the templates as appropriate.

That's a bit of head coding, so it might not be 100%, but that's generally the plan.

@abea That helps a lot. I was sort of going another way. You were pretty much spot on as far as the code, so pretty good for "head coding" :) Hopefully I'll have a PR for you to take a look at in the  next day or so.


Change blocklist.csv: United Media Network AG

Address concern regarding United Media Network AG.
In iptv-org/iptv#6486,
The DMCA only states that N1 to be removed. It doesn't explicitly mentions to remove all channels from United Media Network AG.
I've kept the sports related channels in.

But the notice literally has the names of all these channels on it:

Sport Klub 1-10, HD, Sport Klub Golf, SK Fight, Sport Klub eSports, Lov i Ribolov, Pikaboo, Cinemania, Nova S, Nova Sport, Vavoom, Brainz. Moreover, UM is authorized, on behalf of its affiliated companies, to protect their copyrights and related rights over the following TV Channels: N1, Grand 1, Grand 2, NOVA TV, Doma, IDJTV, NOVA GR, NovaCinema 1-4, NovaLife, NovaSport 1-4, Nova Prime, Nova BG, Kino Nova, Nova Sport BG, Diema, Diema Family, Diema Sport 1-3

https://github.com/iptv-org/iptv/issues/6486

But the notice literally has the names of all these channels on it:

Sport Klub 1-10, HD, Sport Klub Golf, SK Fight, Sport Klub eSports, Lov i Ribolov, Pikaboo, Cinemania, Nova S, Nova Sport, Vavoom, Brainz. Moreover, UM is authorized, on behalf of its affiliated companies, to protect their copyrights and related rights over the following TV Channels: N1, Grand 1, Grand 2, NOVA TV, Doma, IDJTV, NOVA GR, NovaCinema 1-4, NovaLife, NovaSport 1-4, Nova Prime, Nova BG, Kino Nova, Nova Sport BG, Diema, Diema Family, Diema Sport 1-3

iptv-org/iptv#6486

Yes but the target of the infringment is N1 not all of the channels above:

Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.

N1 is a 24-hour cable news channel launched on 30 October 2014. The channel has headquarters in Belgrade, Sarajevo, Ljubljana, and Zagreb and covers events happening in Southeastern Europe.
Available on cable TV throughout former Yugoslavia, N1 is CNN International's local broadcast partner and affiliate via an agreement with the London-based Turner Broadcasting System Europe.
As it is focused on the audiences of the four countries in which it is headquartered, it has four separate editorial policies, separate reporters, TV studios as well as internet and mobile platforms.
In cases where news overlaps, it is presented jointly.

That's what I mentioned for clarification. I can close if it is not okay.

No, you're right, I missed that.


Error: Could not find a suitable OpenGL profile for this system

Hi
I'm on Linux and downloaded the zip file from the homepage and
I'm starting the project with:
./gtoolkit GToolkit-64-20200331015400-ba8f45f.image --interactive

And I get the error:
Error: Could not find a suitable OpenGL profile for this system

I found out that this project is using glutin, so I tested that out and it runs.
Can anyone give me a pointer on how to debug this?
Thanks a lot, this project looks glamorous!

What is the output of glxinfo?
The error is from here. Which gets executed when glutin_create_windowed_context returns a null pointer for every possible profile. If feenkcom/libglutin is build in debug mode, it prints the reason it couldn't create the context to the terminal. You could try to build feenkcom/libglutin in debug mode and place the resulting library next to gtoolkit overwriting the release mode build there is at the moment.

here is the output of glxinfo:
https://gist.github.com/archaeron/5c005675b1ca811ac2c5c58e62bfa6d4
I'll try to do the other one

here is the output from libglutin:
[Glutin] OpenGL Headless Context: ContextBuilder { gl_attr: GlAttributes { sharing: None, version: GlThenGles { opengl_version: (1, 4), opengles_version: (1, 4) }, profile: None, debug: true, robustness: TryRobustNoResetNotification, vsync: false }, pf_reqs: PixelFormatRequirements { hardware_accelerated: Some(true), color_bits: Some(8), float_color_buffer: false, alpha_bits: Some(0), depth_bits: Some(16), stencil_bits: Some(8), double_buffer: Some(false), multisampling: None, stereoscopy: false, srgb: false, release_behavior: Flush, x11_visual_xid: None } }
[Glutin] Primary monitor: MonitorHandle { inner: Wayland(MonitorHandle { name: Some("0x313d (AUO)"), native_identifier: 37, size: PhysicalSize { width: 1920, height: 1080 }, position: PhysicalPosition { x: 0, y: 0 }, scale_factor: 1 }) }
[Glutin] Could not create headless context NoAvailablePixelFormat

You seem to have OpenGL 1.4, which is from 2002.
What are the last few lines of errors by libglutin?

hi @syrel thanks for the answer :)
I'm on Fedora 31 (the latest one)
Please tell me if I can help debug this.

Hi @archaeron ,
We've recently done some work on supporting Gtoolkit on Fedora 31 and Wayland.
Could you try downloading the latest version of Gtoolkit, v0.7.896 (or later)?
There's additional information in https://github.com/feenkcom/gtoolkit/issues/983
Thanks,
Alistair

hi @akgrant43
thanks for the update!
This looks better but it still crashes.
This time I can very briefly see the main window before it closes again.
primitive #loadSymbol:module: in ExternalAddress class failed
ExternalAddress class(ProtoObject)>>primitiveFailed:
ExternalAddress class(ProtoObject)>>primitiveFailed
ExternalAddress class>>loadSymbol:module:
TFExternalFunction>>validate
TFPooledExternalAsyncCall(TFExternalAsyncCall)>>validateFunction
TFPooledExternalAsyncCall(TFExternalAsyncCall)>>prepareExecution
[ semaphore := aRunner semaphorePool takeOne.
self prepareExecution.
self doExecuteOn: aRunner ] in TFPooledExternalAsyncCall>>executeOn: in Block: [ semaphore := aRunner semaphorePool takeOne....
BlockClosure>>ensure:
TFPooledExternalAsyncCall>>executeOn:
TFSameThreadRunner(TFRunner)>>invokeFunction:withArguments:
LGitLibrary>>libgit2_init
TFCalloutAPI(FFICalloutAPI)>>function:library:
TFCalloutAPI(FFICalloutAPI)>>function:module:
LGitLibrary(FFILibrary)>>ffiCall:
LGitLibrary>>libgit2_init
[ self libgit2_init.
self recordInitializationSuccess ] in LGitLibrary>>initializeLibGit2 in Block: [ self libgit2_init....
BlockClosure>>on:do:
LGitLibrary>>initializeLibGit2
LGitLibrary class>>startUp:
ClassSessionHandler>>startup:
[ :each | each startup: isImageStarting ] in WorkingSession>>runStartup: in Block: [ :each | each startup: isImageStarting ]
[ aBlock value: each ] in [ :each |
[ aBlock value: each ]
	on: Exception
	do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ aBlock value: each ]
BlockClosure>>on:do:
[ :each |
[ aBlock value: each ]
	on: Exception
	do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ :each | ...
Array(SequenceableCollection)>>do:
WorkingSession>>runList:do:
WorkingSession>>runStartup:
WorkingSession>>start:
SessionManager>>launchSnapshot:andQuit:
[ isImageStarting := self launchSnapshot: save andQuit: quit.
wait signal ] in SessionManager>>snapshot:andQuit: in Block: [ isImageStarting := self launchSnapshot: save and...etc...
primitive #primitiveReleaseParameters:releaseReturn: in TFPooledExternalAsyncCall failed
TFPooledExternalAsyncCall(ProtoObject)>>primitiveFailed:
TFPooledExternalAsyncCall(ProtoObject)>>primitiveFailed
TFPooledExternalAsyncCall(TFExternalAsyncCall)>>primitiveReleaseParameters:releaseReturn:
TFPooledExternalAsyncCall(TFExternalAsyncCall)>>cleanUp
[ self cleanUp.
semaphore reset.
aRunner semaphorePool returnOne: semaphore ] in TFPooledExternalAsyncCall>>executeOn: in Block: [ self cleanUp....
Context>>resume:through:
BlockClosure>>ensure:
TFPooledExternalAsyncCall>>executeOn:
TFSameThreadRunner(TFRunner)>>invokeFunction:withArguments:
LGitLibrary>>libgit2_init
TFCalloutAPI(FFICalloutAPI)>>function:library:
TFCalloutAPI(FFICalloutAPI)>>function:module:
LGitLibrary(FFILibrary)>>ffiCall:
LGitLibrary>>libgit2_init
[ self libgit2_init.
self recordInitializationSuccess ] in LGitLibrary>>initializeLibGit2 in Block: [ self libgit2_init....
BlockClosure>>on:do:
LGitLibrary>>initializeLibGit2
LGitLibrary class>>startUp:
ClassSessionHandler>>startup:
[ :each | each startup: isImageStarting ] in WorkingSession>>runStartup: in Block: [ :each | each startup: isImageStarting ]
[ aBlock value: each ] in [ :each |
[ aBlock value: each ]
	on: Exception
	do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ aBlock value: each ]
BlockClosure>>on:do:
[ :each |
[ aBlock value: each ]
	on: Exception
	do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ :each | ...
Array(SequenceableCollection)>>do:
WorkingSession>>runList:do:
WorkingSession>>runStartup:
WorkingSession>>start:
SessionManager>>launchSnapshot:andQuit:
[ isImageStarting := self launchSnapshot: save andQuit: quit.
wait signal ] in SessionManager>>snapshot:andQuit: in Block: [ isImageStarting := self launchSnapshot: save and...etc...
[ self value.
Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....

should I open a new Issue?

Hi @archaeron ,
Can you follow the instructions in the attached pdf and script (renamed .txt to allow attachment)?
Thanks,
Alistair
central-HowtorunGtoolkitonFedora-170420-1144.pdf
gt_check_libs.txt

Hi @akgrant43
the output of lld lib/libgit2.so and lld libSkia.so both look good now (after the fixed from the PDF)
The errors are gone, but the programm still terminates half a second after having opened the main Window

Hi @archaeron ,
There should be a log file of some sort.  Pharo produces PharoDebug.log.  Ubuntu will normally produce a crash.dmp file, I assume Fedora will produce something similar.
Can you delete both of these, reproduce the problem and then send them through.
Thanks.

ah I had to use --no-quit :D sorry

Great to hear!


feat: Add Dockerfile for LMES job image

Add Dockerfile for LMES job image and the needed files
related: #274

@ruivieira I didn't update the GH action workflow. Please let me know if you want me to do that.

@ruivieira the error from the Build and Push workflow is:
unauthorized: access to the requested resource is not authorized

Can you help to fix this? I believe that's the permission settings on the query.io end for the access token used by this repo.

Thanks @yhwang, the destination quay.io wasn't created yet. It's fixed now.


Upgrade timescaledb to latest released version (v1.7.0) and PG12 [BREAKING]

Description of PR

What component(s) does this PR affect?

[x] Back-End (Database, Detection/Configuration/etc. Microservices)
[ ] Front-End (Flask, API, UI, etc)
[ ] Monitor (RIPE RIS, BGPStream RV/RIS/CAIDA, etc.)
[ ] Docs (incl. wiki)
[ ] Build System

Does the PR require changes on other components? If yes, please mark the components:

[ ] Back-End (Database, Detection/Configuration/etc. Microservices)
[ ] Front-End (Flask, API, UI, etc)
[ ] Monitor (RIPE RIS, BGPStream RV/RIS/CAIDA, etc.)
[ ] Docs (incl. wiki)
[ ] Build System

Related Issue

Resolves #
Solution

Type

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Docs update
[ ] None of the above

Checklist:

[x] I have read the contributing guide and my code conforms to the guidelines.
[x] This change requires a change in the documentation.
[x] I have updated the documentation accordingly.

TODO: if production/dev upgrade fails, form proper upgrade process.

Dumping the data and restoring should be sufficient in order to do the upgrade. I will try to do the upgrade and restore from our backup.tar file.

@slowr does the migration check fail https://travis-ci.org/github/FORTH-ICS-INSPIRE/artemis/jobs/679542540 maybe because the message "database system is ready to accept connections" has changed in the newer version? Could we do more checks to make sure that the testing is robust and nothing breaks across migrations?

@slowr does the migration check fail https://travis-ci.org/github/FORTH-ICS-INSPIRE/artemis/jobs/679542540 maybe because the message "database system is ready to accept connections" has changed in the newer version? Could we do more checks to make sure that the testing is robust and nothing breaks across migrations?

no the migration check fails because it cannot migrate from PG10 to PG12. The check is working correctly.

This will be release on a new minor version (v1.5.0) and not in a patch version. Putting this pull request to the backlog until we schedule the minor release.

I will reopen the PR when we want to upgrade the database version


Use facet-lib namespaces

Depends on:

[x] https://github.com/mareklibra/facet-lib/pull/13
[ ] #229

Closed in favour of #230


Language

hi um my genre and language is has stopped working i think , keep up the great work . cheers

my bad i didnt see the update


Make ParseDockerName() return an error.

This forces callers to handle cases where the container name could not
be parsed.

PTAL @yujuhong
Not as bad as I thought it would be :)

LGTM. Thanks!


Only run the workflow on release

If the push to main is done without changing the release version, the workflow fails. My question is if it is more practical to run the workflow only when a version of the chart is released

What do you think @catrielmuller

We can do release same way (by merging to main branch). I'll help create another workflow to make sure contributor bumping chart version before we merge the PR.
WDYT ?

I have pull-request for that here https://github.com/freifunkMUC/wg-access-server-chart/pull/11
Please let me know what do you think.

Thanks! Merged 😄


How can add prefix "m" in bind name?

Hi, I want add prefix "m" in bind name.
For example, the reousce id is “btn_hello",I want the bind name is "mBtnHello".

You can set prefix in plugin settings.

@destil
Thank you, I already fix this problem.
Android Studio->File->Settings->Other Settings->ButterKnifeZelezny


Run every tasks test exclusively

Run every tasks test exclusively, so that the data of the previous test is not utilised in any test. We should run the cleanDB function to clean the DB after every test so that the data added for the test1 does not affect test2.
This is currently causing the test: https://github.com/Real-Dev-Squad/website-backend/runs/2799769523?check_suite_focus=true#step:6:133 to fail in main branch.

cc: @bhk31 , @sumitd94


venv on arch/manjaro can't run fstcompile when using external mqtt

On Arch/Manjaro, I get:
rhasspyserver_hermes: Command 'fstcompile --keep_isymbols --keep_osymbols --isymbols=/tmp/tmp5wsmnw4z/isymbols.txt --osymbols=/tmp/tmp5wsmnw4z/osymbols.txt /tmp/tmp5wsmnw4z/graph.fst.txt "/tmp/tmp5wsmnw4z/graph.fst.fst"' returned non-zero exit status 127.

Running that alone, shows:
fstcompile: error while loading shared libraries: libfstscript.so.13: cannot open shared object file: No such file or directory

doing, export LD_LIBRARY_PATH=$(pwd)/.venv/lib makes fstcompile run, however, it still fails in the script?
How can I check if LD_LIBRARY_PATH is set correctly when running fstcompile from rhasspy?

Is this correct?
(.venv) [homeaut@router rhasspy]$ patchelf --print-rpath .venv/bin/fstcompile
/build/openfst/lib

no even after patching the path in, training always crashes with:
fstcompile --keep_isymbols --keep_osymbols --isymbols=/tmp/tmp0a6ou1ue/isymbols.txt --osymbols=/tmp/tmp0a6ou1ue/osymbols.txt /tmp/tmp0a6ou1ue/graph.fst.txt "/tmp/tmp0a6ou1ue/graph.fst.fst"

Oh, no: switching to internal mqtt makes the training possible again - I tested satellite funcitons on the router before. So, fsticuffs traingng doesn't work when enabling external local mqtt.

Based on other reports, it's sounding like something happened to satellite functionality in this latest release. Investigating today.

Closing due to inactivity. Please re-open if the problem persists.

Closing due to inactivity. Please re-open if the problem persists.


Recyclerview does no update

Using the method notifyDataSetChanged() does not update the recyclerview

when will it be merged to master?

@dvg4000  , @RamotionDev  ?

It's already merged.

Nothing works for me too. I tried everything.

Hello. In the current version of the lib, cards are getting updated when you set new items to recyclerview's adapter and call notifyDataSetChanged(). If this issue still reproducible, please provide us with source code, which describes how you use this lib.


Initial javascript support in html projects

Small tweaks to allow javascript files in HTML projects rather than relying on inline styles

This all works great Scott! Do we need any tests since HTMLRunner is going to be worked on and untangled soon?

Ideally yes however I really can't see a way of testing the code in the HTML iframe in it's current state 🤦 so I've added a little note here as a reminder because we'll likely want a bunch of tests to check this logic!


Limit shared mounts to specific VM (launcher) Pods - cleanup needed

Because of #613 the VM pod's are no longer trusted. User's need podExec access in order to access the vm's console.
This means all local shared data between VM pods in /var/lib/kubevirt needs to change to a pattern where VM pods can only see data directly pertaining to them.

@davidvossel is this still a thing?

/remove-lifecycle stale

/remove-lifecycle stale
On Wed, Dec 19, 2018 at 4:43 PM kubevirt-bot<EMAIL_ADDRESS>wrote:

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.


bug(client-mods): discord changes

they swapped from webpack to rspack, most likely will have to fix webpack searches.

#43


Occasional hardfault in lv_group_add_obj

I noticed that occasionally my microcontroller was hardfaulting when calling lv_group_add_obj.
I traced the error to lv_group_focus_next calling focus_cb on an uninitialised callback function.
Fix: In lv_group_create, add the line group->focus_cb = NULL;

Hi,
Thank you very much for reporting the issue!
This issue is already fixed in the beta branch and will be released soon as part of v5.1.1.


Activated environments not resolving PYTHONPATH=./ to a fully qualified value

Assume you have a .env file with the following contents
PYTHONPATH=./

When you debug a Python file, then the env variable is resolved and the PYTHONPATH value is fully resolved to the full path of the workspace. I.e. Workspace path is now in the current Python path (sys.path)
However when Jupyter extension gets the activated env variables the above value is not resolved, as a result the workspace directory is not added to the PATH or PYTHONPATH value in the env variables.
Looks like Python ext only resolves this for debugging of python code and not when returning activated variables.

debugpy doesn't know anything about workspaces. However, if you have a launch configuration with "program":"/foo/bar/baz.py" and no "cwd", it will assume that "cwd" should be "/foo/bar". Thus having . in PYTHONPATH works in practice in this scenario.
If the path is not absolute or you use "module", it will not do anything special, so all relative paths will be resolved depending on what the current directory is for the terminal running the debuggee.

How does pylance resolve relative paths in environment variables? especially if PYTHONPATH=./ does it expand the .?

We only support resolving a few environment variables in paths (ex. HOME, USERNAME, VIRTUAL_ENV), but yes we do support relative paths there.
The PYTHONPATH environment variable is handled differently. We don't support it in all paths. We just check if it's set (via the  python._envPYTHONPATH config setting) and if so, add it to our extraPaths. Although we support relative paths in PYTHONPATH (ex. ./foo), it appears that ./ gets incorrectly resolved to \\ rather than the workspace root. This is also true if you directly set "python.analysis.extraPaths": ["./"] though. I'm not sure we care about that scenario since I don't think it makes sense to add the workspace root to extraPaths.
Adding @heejaechang since, coincidentally, he was also looking at our code that handles the PYTHONPATH env var today.

Thank you both, as each tool/extension can have it's own cwd or preference to resolve relative paths such as ./, Python extension cannot always resolve the ./ to workspace root.
@DonJayamanne Based on this I think Jupyter extension should probably set the cwd when executing using the variables and paths can be resolved depending on what the current directory is, similar to how debugger does it. Closing this.

we get python search path from running python interpreter and ./ will be resolved to whatever python interpreter think current working folder is at the time, and in vscode/pylance, that's where our server starts which is .vscode\extensions\ms-python.vscode-pylance-xxxx\dist
but to help user to have similar impact, our import resolver will always try to resolve import at current folder if no module gets resolved with the name.
ex) /lib/lib1.py and /lib/nested/lib2.py and /lib/nested/test.py
in /lib/nested/test.py, one can refer lib2 as import lib.nested.lib2 or import lib2, this is to support a case where user runs test.py directly at /lib/nested and python will put /lib/nested in search path. our normal workspace set up with vscode can't support this since we will put only / as root.

@karrtikr
See here

When you debug a Python file, then the env variable is resolved and the PYTHONPATH value is fully resolved to the full path of the workspace. I.e. Workspace path is now in the current Python path (sys.path)

The Jupyter extension does not know what is in PYTHONPATH, hence we cannot add the path value.
Basically, from an end user perspective, when running Python code using the debugger (run with debugging or run without debugging), then Python extension will honour the value in PYTHONPATH found in the .env file.
However when Jupyter tries to get the same env varaibles for running python code outside the pytyhon extension, then pytohn extension does not honour the PYTHONPATH in .env file
Re-Opening this, as the Jupyter extension cannot add the values without knowing what is in it.
But the whole point of the API is for the python extension to return the same env variables that will be used by python extension when running python code.
but there is a descrepancy, hence this issue.

Please try debugging and you will see that python extension will honour the value in PYTHONPATH=./ found in .env file.
I agree the debugger might be doing something special, at the endc of the day thats part of the Python extension
and the user now sees a difference between running python with python extension and running with Jupyter.

@DonJayamanne I agree that there is a inconsistency but I'm not clear on why Jupyter cannot set the current working directory like other extensions/tools to solve this.

As noted earlier, the debugger doesn't do anything special. It just happens that it's usually running in an environment where the current directory is the same as workspace folder, and so normal resolution of relative paths by Python itself has the desired effect. But if you e.g. set "cwd" explicitly in launch.json, it will resolve relative to that, so it's not generally true that "./" always resolves to the workspace today. Changing it to do so would be a breaking change.

why Jupyter cannot set the current working directory like other extensions/tools to solve this.

This should not be done always. (we set CWD based on the file that is being run, i.e. CWD does not always point to workspace folder)
This is ONLY done based on the value in PYTHONPATH in .env
As mentioned if you try debugging python code you will see the difference in sys.path

it's usually running in an environment where the current directory is the same as workspace folde

I'm debugging a file in a nested folder within the workspace.

If the PYTHONPATH is not set in .env file, then the sys.path does not contain the workspace folder.
If the PYTHONPATH=./ is set in .env file, then the sys.path contain the workspace folder.
Here is my launch.json

    {
      "name": "Python: Current File",
      "type": "python",
      "request": "launch",
      "program": "${file}",
      "console": "integratedTerminal",
      "justMyCode": true
    },

Here is my folder structure

root folder has .env file which is empty
sub directory named iw and file named sample.py
contents of sample.py is

import sys
print(sys.path)

Debug above file and the workspace folder is not in the sys.path
Now update .env file as follows

PYTHONPATH=./

Now debug the same python file and watch how changing .env file results in sys.path now having an entry for the root workspace folder.

"cwd": "/tmp"

Sure sure, but thats an exception (as users have to makde changes to the default),
ie. with the default behaviour it works as described above

For it to resolve ./ relative to "cwd" in the debug config, it would have to know which config it needs to use. But that API is used in scenarios that don't involve debugging at all, so it's unclear what the answer should even be in that case.

I'm not asking for a change in the debugger or the python ext code
Just pointing out the descrepancy and the fact that Juptyer cannot work around this or handle this without any changes to some python ext API or the like.

The users don't actually even have to specify "cwd" explicitly for the difference to manifest. If it's not specified, but they have something like "program": "/foo/bar.py", then "cwd" is automatically assumed (by debugger magic) to be "/foo", and thus the resolution of ./ in PYTHONPATH will also be relative to that.
I might be missing something, but wouldn't the easiest way for Jupyter to get the same behavior be launching the debugger in the same manner? That is, if there is a workspace folder, then set it to be the current directory before spawning the adapter process, and let it resolve relative paths accordingly?

the debugger in the same manner? That is, if there is a workspace folder, then set it to be the current directory bef

this doesn’t apply to debugging Jupyter code, but just regular execution

Sorry forgot to close it out. After discussion with the team this is where we are at:
To summarize, users may expect that CWD is the workspace folder as that is how it is for rest of the extension. But Jupyter cannot launch using CWD as workspace folder as default as it uses CWD based on the file that is being run.
Python ext cannot resolve PYTHONPATH=./ as that is only resolved during execution, and we don't have a use-case to do that internally. So Jupyter has to do that itself if it wants to go that route.

OTOH if we need a feature to indicate that some variable in .env is always set to a full absolute path to the workspace folder, then why not come up with a new syntax specifically for that, and advertise it as such?

Alternatively as Pavel pointed out, we can provide ${workspaceFolder} support in .env files https://github.com/microsoft/vscode-python/issues/14518 and advertise it as such. Closing in favor of these alternatives.


Hidden Menu Option for TX Everywhere

I know this functionality can be kind of polarizing (even in a hidden menu), but I'd like to see the option to enable TX across all frequencies that this radio is capable of. This pull request adds a menu option to allow TX (although degraded) on all those other frequencies. I'm in the United States and enabling this functionality lets me talk to my local 6M repeater via the UV-K5. With great power comes great responsibility.

I'm leaving opening the TX to transmit anywhere/everywhere to everyone elses repos. I've deliberately not done that in my own version of the firmware (this repo).
The spurious content of the TX output when you start trying to transmit outside of the designed range is terrible. I'd say put your radio on your spectrum analyser and take a look at the spectral/harmonic content when you do try and transmit out of the specified range.
RX is different, you don't cause problems for anyone else by allowing it to cover a larger range than normal, but TX is a different matter altogether.

Ah, got it. Thanks for the explanation. I have been running my Quansheng with an old coaxial inline 6m bandpass filter that I had from a previous project. I know it sounds ridiculous but it still comes in cheaper than a handheld with 6m capabilities and removes all the harmonics when I look at it on my scope. TX power isn't as good as on 2m/70cm but it gets the job done.

But ..
don't delete this, as i may cave in and enable TX everywhere EXCEPT airband.

Ah, got it. Thanks for the explanation. I have been running my Quansheng with an old coaxial inline 6m bandpass filter that I had from a previous project. I know it sounds ridiculous but it still comes in cheaper than a handheld with 6m capabilities and removes all the harmonics when I look at it on my scope. TX power isn't as good as on 2m/70cm but it gets the job done.

No it doesn't sound ridiculous at all, I'd like the radio to TX on 6M and 4M as well, it's just the harmonic content that puts me off.
But as you say, a filter before the antenna solves that for you :)

This is how bad the K5 is when trying to TX in the 50 to 70Mz range (MOST of the TX power is in the harmonics) ...

Tested the latest commits with the new feature and everything works. You rock! (As always)


Chore/353 methodology data not flat with emission

polluted branch that this pr is based off. closing


[AIRFLOW-1686] Write list_objects, delete_object, and tests for boto3 s3_hook

[AIRFLOW-1686] Fix whitespace issue for get_credentials method call
[AIRFLOW-1686] Remove merged file
[AIRFLOW-1686] Fix Aws Hook
[AIRFLOW-1686] Add s3 list_objects and tests
[AIRFLOW-1686] Fix region for tests
[AIRFLOW-1686] Fix client not defined error s3 test
[AIRFLOW-1686] Move mock_s3 to class
Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1686

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
added useful boto3 methods to s3 hook, as well as new test file and tests.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
s3 hook unit test file

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2716 into master will decrease coverage by 0.07%.
The diff coverage is 63.63%.

@@            Coverage Diff            @@
##           master   #2716      +/-   ##
=========================================
- Coverage   72.47%   72.4%   -0.08%
=========================================
  Files         154     154
  Lines       11815   11821       +6
=========================================
- Hits         8563    8559       -4
- Misses       3252    3262      +10

Impacted Files
Coverage Δ

airflow/hooks/S3_hook.py
36.66% <63.63%> (+5.71%)
:arrow_up:

airflow/task_runner/bash_task_runner.py
93.33% <0%> (-6.67%)
:arrow_down:

airflow/utils/helpers.py
53.44% <0%> (-2.88%)
:arrow_down:

airflow/jobs.py
79.06% <0%> (-0.46%)
:arrow_down:

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 21257e8...2d57eca. Read the comment docs.

Please review your commit message.

@bolkedebruin Updated commit message, please review when you get a chance!

Note, this is one of the follow-ups to https://github.com/apache/incubator-airflow/pull/2532


Instructions for "enablement" of roku dashboards include feature not available

There is no "import dashboard" feature available on the New relic instance so i am unable to import the JSON. I have admin on my instance, and after opening a ticket with New Relic, they are a little unclear.

@rdobda-gaia the enablement readme does have a note after Step 2 that Steps 3-6 can only be performed by someone at New Relic.
If you have an account team you usually interface with you can ask them and they can help.
or...

@rdobda-gaia you can email me at<EMAIL_ADDRESS>with the account id you'd like to add the dashboard to and I can do it for you.


Toggling between ETH and USD in Send screen should not mess up the values #2244

Closes #2244, closes #2243

@hboon i updated commit with removing trailing zeros from text field, worked for me. Please check and let me know if this pr is ok.

Hmm. I thought the issue has been fixed, no?

Hmm. I thought the issue has been fixed, no?

yes it is, i made some updates for displaying large numbers, for case when we enter amount like 10000, then do convert to usd and then back , value i text field become 10,000.00, so this update remove .00 from string.

maybe it was better to create another issue?

maybe it was better to create another issue?

Yeah. Thanks :) I'll close the other 2 issues. I missed those earlier.


Patch for diffusers 0.21.0 release

[x] Check dependency availability
[x] Fix import breaks from diffusers 0.21.0
[x] Remove experimental compilation flag

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Oh right, I forgot that step again... will do @dacorvo !


Update version: Nutstore.Nutstore version 7.0.5

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115928&drop=dogfoodAlpha

This installer had a UAC prompt, despite being installed with Administrator permissions:


special modules

there are nothing that distinguish between special and normal modules.... like the shield generators and the prismatic shield generators

See: https://github.com/Marginal/EDMarketConnector/issues/40

Yes, the schema says that such modules should be omitted.
See comment under Marginal/EDMarketConnector#40 for rationale.

Is planned any schema for "special modules"

!if they are effectively dependant of the user sending the data, clearly not.

Also the datas sent by "OCR Elite" are dependant from the correctness of datas sent by users ,  are those datas planned to be refused too ?

Oh common, that is not comparable at all...
OCR Elite user all see the same commodities...

yep, but numbers correctness are checked by users...
I meant simply that they could be managed as 4th batch of data ( like "commodities", "modules" or "ships" are ) if the player has the possibility to send those datas...
This shouldn't affect eddn stability but simply has to implement that 4th schema... that it will be quite identical to "modules"

I personally don't see the point of having a schema if the special modules are dependant on power play in station.
It uses bandwidth and CPU, for something that is dependant for informations we do not send.
Again I'm not aware of the exact functioning process, so it must be discussed.

It simply sounds strange to me that those modules are ignored and that special rules was been created to ignore them and in  the other hand the info from Elite OCR are taken as they are, also if a cmdr simply forget to analyze a screenshot or forget to send part of its data or simply he sent wrong datas...

Marginal's comment at https://github.com/Marginal/EDMarketConnector/issues/40#issuecomment-155472176 explains why it doesn't make much sense to broadcast data about prices for these modules.


NuoDB SM is crashing post rescheduled, observed that zrepl is consuming > 200% CPU.

NuoDB SM is crashing post rescheduled, observed that zrepl is consuming > 200% CPU.
Steps Performed:

Deployed NuoDB with 3 Admin, 2 SM (consuming cstor volume of size 800G) and 3 TE configuration on OpenShift 3.10 EE.
Ran YCSB load for 8 days.
Performed SM-0 pod kill, observed that the rescheduled application pod took around 12 minutes to come to running state.
After that SM-0 started syncing data from SM-1, here observed that SM-0 crashed with below coredump

2019-02-21T16:10:46.516+0000 [46] (test node 9) GC visited 22419 of 22419 objects, 0 deleted, 0 purged, 20921 were purged, 0 hollow, 0 were hollow, 43338 skipped, 1470 dirty, 0.000000 KB reclaimed (4.87 GB -> 4.88 GB)
2019-02-21T16:10:46.529+0000 [46] (test node 9) computeTransactionGroups@630875: node 9, 12 active, 19004 committed, 1 in group 0, 18987 in group 1, 12 groups, 10115 usec
2019-02-21T16:10:46.539+0000 [46] (test node 9) ASSERT: /space/builds/RELEASE-PACKAGE50-RELEASELINUXTARBALL/Platform/MasterCatalog.tpp:59: FAILED: BUGCHECK: Unable to free memory for 300 seconds
*** Stacktrace:
0xb4fd51
0x8cca92
0x994c23
0x8cdd85
0xb8c93e
0xb8b31b
0x7fcb703eadd5
0x7fcb70113ead clone+109
*** Closing all network transports
*** Generating coredump: /var/log/nuodb/crash/core.nuodb.sm-test-0.46
*** Coredump completed.

Observed on the node when SM-0 is rescheduled has hit a CPU spike of > 200%

sm.log
target.log


SWDEV-411156 - Add basic tests for fp16

Change-Id: Ie4f00ebd198c8689d34757a3c27aaddb85d15370

Changes have been merged to internal repo.