(cmd/helm): No way of obtaining the chart version for a release when chart name + version > 60 chars

This is somehow related to #1914 and #1915.
helm version: 2.6.0
The MaxColumn is set to 60 on helm list and helm history.
Example:
helm list
NAME                            	REVISION	UPDATED                 	STATUS  	CHART                                                       	NAMESPACE
methode-article-image-set-mapper	5       	Fri Aug 18 15:37:00 2017	DEPLOYED	methode-article-image-set-mapper-1.3.0-k28s-helm-integrat...	default

Currently there is no way to obtain the version of the chart used for the release.
Proposed solutions:

allow setting the column max length from the command line  helm list --max-col-length=6000
introduce another flag to show full column values helm list --full-output

@sbuliarca Im not crazy about --max-col-length personally. It might be time to consider adding --output similar to Kubernetes to allow more output formatting options for all commands.

@jascott1 Indeed this would be a very nice option that would be more familiar to kubectl. I guess it implies more work though.

@sbuliarca We could just start with --o wide and expand the output options later.

@jascott1 Indeed, this sounds good.

@jascott1 Are there any plans to include this feature in the near future?

Excellent, thank you. I'll give it a go.

@bacongobbler I managed to test it, and it works as expected

My chart versions are like 3.0.0+build.123 , 3.0.0-alpha.123.
I am able to push chart but while pull how to specify chart version? I am trying to add regex in:
helm pull --version ${regexstr}
Regex not working any idea?


post: ann ipfs camp

//cc @cwaring @olizilla @angiemaguire

@daviddias wanna merge master up in here to  get that sweet pre-deploy preview?

@olizilla of course! :D

@angiemaguire, @cwaring preview is here \o/ https://ipfs.io/ipfs/QmX68GsR7PAavSKAowC7ZoTjiCmo8HFCfxwyaeBHEuqWy9/72-ann-ipfs-camp/

Can has title that fits in 1 line?


Name collision of security group in tf_admin with tf_instance

what

Fixed name collision of security group in tf_admin with tf_instance

why

Name collision of security group in tf_admin with tf_instance

@osterman @comeanother, should we split resource "aws_security_group" "default" on two different security groups e.g.  "${module.label.id}-ssh" with ingress rules and  "${module.label.id}-output"  with egress rules?


Write yosys.sdc file

I'm trying to fix a timing issue in my design, and I notice we are passing
an empty sdc file to yosys. This fixes it.

Seems that this happened since https://github.com/efabless/openlane/commit/cb0a62f3b59faf6cec188142fa2874e2c4921f4f. Merged, thanks!

Seems that this happened since https://github.com/efabless/openlane/commit/cb0a62f3b59faf6cec188142fa2874e2c4921f4f. Merged, thanks!


PgUp/PgDown keys don't work on a lage directory

DownArrow/UpArrow keys scroll by one, but PgUp/PgDown are also expected to scroll, by page. Otherwise it is hard to navigate in a large directory.

I have this functionality in rev 008d6ad so check that out and let me know if you encounter any bugs


Delegate tracking a delegate

Is there any way we can have one delegate know if another has fired? I'll explain, as that sounds weird...
I want to track all the SQL statements that are run for say, a Section save event (create/edit/delete delegates). I know there is the delegate that fires for each SQL statement, but at that point there is no context as to what called it, so I can't say "Ah, this group of SQL statements are from a Section being created!".
The same for Entries and other perts of the system too.

Is there any way we can have one delegate know if another has fired?

Yes, a simple array could do the trick... :)

"Ah, this group of SQL statements are from a Section being created!".

This is waaay trickier. By knowing which delegate got called, how would you deduce this ?

Our delegates system is too clunky. A better system would be one that used event triggering.
An extension could listen to two events (pseudo example here):

section.before.create - Where it starts to listen to database.query which emits it's SQL among other things.
Listening to the database.query event allows the extension to gather the SQL queries.
section.after.create - Where it stops listening database.query and processes the gathered results.

Obv, this is not possible in the current version, at least I don't think so?

Hmm, yeah, we don't have a central place for runtime delegate attachments, which is the clunky part I was on about. It's a shame.

Yeah delegates and events are two different beasts.
We currently use "automatic event registration" (registration is done once and cannot be undone)
Maybe it's a separate feature ?

I suppose it boils down to how the extension is instantiated during runtime.
Is the extension instantiated only once, or does it happen on a per delegate triggering basis?

Event registration can typically occur anytime after the creation of the event source...
Right now, I think we check the pool of listeners only when the actual delegate is called.

Could it be solved by subscribing to SectionPreCreate and PostCreate delegates and then calling Symphony::Database()->debug() to get the list of queries that have run? We do something similar in ExtensionManager->notifyMembers to find out what extension ran which queries. Alternatively, you can subscribe to PostQueryExecution and use some sort of timestamp to figure out what has run.

Is the extension instantiated only once, or does it happen on a per delegate triggering basis?

Once. Extensions are initialised once and saved into a static cache. The ExtensionManager is a singleton.

Right now, I think we check the pool of listeners only when the actual delegate is called.

Correct, the subscriptions are loaded on initialisation of the ExtensionManager, but we only check the subscriptions for matching listeners when the delegate is fired.

Given the delegate system was built nearly 10 years ago, it's definitely got it's flaws. Unlike modern event dispatcher's featured in Symfony2 or Laravel, the Symphony Extension Manager delegate system is immutable out of the box. Extensions register their events (delegates) when they are installed (tbl_extensions_delegates) and the Extension Manager uses these on each page load.
A more modern solution would be to decouple the delegates from the Extension Manager, allowing extensions and the core to be equal citizens. A central event dispatcher would allow both extensions and the core to listen to delegates. It's crazy at the moment that sometimes extensions have more power than the core because of the delegate system!

I like the debug idea!
Also, as the extension is initialised once, this means (correct me if I'm wrong), one delegate callback can affect the extension by adding say a cache, and a later callback can read it?

Also, as the extension is initialised once, this means (correct me if I'm wrong), one delegate callback can affect the extension by adding say a cache, and a later callback can read it?

Yes, this is how the Expression/Reflection Field does it's magic. One delegate sets a static variable on the extension, and then later in the lifecycle another delegate reads from that variable. It's not a 'modern' way of doing it, but it can work for the moment.

Closing...


Store .cfc files in the root of the inmanta project

Description
Same PR as #4424 but applied on the iso5 branch due to a merge conflict.
The compiler cache (.cfc) files are now stored in the .cfcache directory in the root of the inmanta project instead of in the __cfcache__ directory in the inmanta modules.
closes #4407
Self Check:

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches iso5 in c0f7646361c43a36dfa34460d191c8943540be09


feat: Support read text through text action

Allow reading text through text action.
Closes #22

Thanks very much for this PR, Kevin.  I'll release a new version with these changes soon.


Add redis filter commands support.

Description: Envoy redis filter has some commands not be supported, which has no effect just add these commands to commands list to have better compatibility with redis protocol.

RPOPLPUSH
SDIFF
SDIFFSTORE
SINTER
SINTERSTORE
SMOVE
SUNION
SUNIONSTORE
ZUNIONSTORE
PFADD
PFCOUNT
PFMERGE

And these commands should be used with hashtag keys, make sure multi-key hash to same slot.
Risk Level: Low
Testing: Passed

@HenryYYang PTAL

all of these commands(except PFADD and PFCount) require multiple keys that might or might not be on the same Redis node.  In the case of where the cluster is not an open source Redis cluster, they will return the wrong result without any error.  This is very dangerous and IMHO worst than not supporting the commands.
In order to add these commands we need these minimum requirements:

they either work correctly or return an error.  This means we need to ensure both these conditions are true:

the cluster is supporting Redis Cluster protocol or hashtagging is turned on.
they're using the same hashtag
Otherwise, we'll return an error.

These limitation should be clearly documented in the docs section.


Create a logo for nwbview

How about one of the 2 icons? Which one do you like more @adrien-berchet @crisely09 @rai-pranav @JCGoran ?
1) A rusted morphological neuron logo with blank  background

1) Updated: Removed white background

2) Rusted neuron with blank background, logo

I vote 1. I am not sure about the white background though.

It seems there's an online service to remove the white background :D

credits:
https://www.remove.bg/

I really like this one 🤩
Very nice work @anilbey , thanks!

I also like the first one. Did you generate this with text to image generation?

I'm also inclined to go with the first one, though they both look awesome!

@rai-pranav

Did you generate this with text to image generation?

@darshanmandge generated the first image using Stable Diffusion.

I also liked the first one more.

oh, I like 2 better, but I trust the majority.


No warning when using ambiguous column name

If a column name is repeated in the input file, and we are referencing it, scorify should at least throw a warning.

Added in https://github.com/uwmadison-chm/scorify/commit/bad4c42ef686bda37edfadd431e677451bc433ac

(bad commit message, I need to improve my dang git workflow, OOPS)


PMID:26205977

normal frequency of knob containing nuclei
decreased frequency of knob containing nuclei

How should we define these "knobs"?
And are these population phenotypes? Sounds like it from the names ...

d'oh, tI emant to include more information.
So knobs are highly condensed chromatin bodies formed from subtelomeric (ST-) heterochromatin. Knobs form on chromosomes 1 and 2 only from what is known so far.
I'm not sure if it is best to do it at a population level or at a cellular level. They measure it at the population level (this cell has a knob, this one doesn't). but I think it would also work at the cellular level (decreased subtelomeric chromatin condensation? synonymous to decreased knob formation?).

OK, I've done them as cell-level process terms:
normal subtelomeric chromatin knob formation FYPO:0005527
decreased subtelomeric chromatin knob formation FYPO:0005528

edit file: 3b73975600f7352daadf94928cd05c932c18a7de
release: 3e4b597b16433cc1d4ec56935ff216aaa2836528


'Object reference not set to an instance of an object.'

Hello,
Since today,
When I use Gl.Ortho, I've the following exception, I don't know why

can you help me ?
Thx.

Does this   solve your issue?

Thank you


Current font does not support math with Libertinus Math v7.051

Description
When using Libertinus Math Libertinus Fonts v7.051, I am getting a compile error: current font does not support math
#show math.equation: set text(
  font: (
    "Libertinus Math",
  ),
)
$f(x)$

There is no problem with v7.040.
Reproduction URL
No response
Operating system
Linux
Typst version

[X] I am using the latest version of Typst

I am the maintainer of the Libertinus family of fonts. I am not able to confirm this report. I tried your test file and also mocked up the same test in SILE where it is easy to get it to spit out the exact version of the font used at typesetting time:
$ cat math-typst.typ
#show math.equation: set text(
  font: (
    "Libertinus Math",
  ),
)
$f(x)$

$ typst compile math-typst.typ
typst compile math-typst.typ

$ cat cat math-sile.xml
cat: cat: No such file or directory
<sile>
<use module="packages.math"/>
<math>
f(x)
</math>
</sile>

$ sile -d versions math-sile.xml
sile -d versions math-sile.xml
SILE v0.15.7 (LuaJIT 2.1.1731486438) [Rust]
<math-sile.xml> as xml
[1]
Harfbuzz version: 10.1.0
Shapers enabled: graphite2, ot, fallback
ICU support enabled

Fonts used:
/usr/share/fonts/libertinus/LibertinusMath-Regular.otf:0        Version 7.051;RELEASE
/usr/share/fonts/TTF/GentiumPlus-Regular.ttf:0  Version 6.200

$ fc-list | grep 'Libertinus Math'
/usr/share/fonts/libertinus/LibertinusMath-Regular.otf: Libertinus Math:style=Regular

$ font-v report /usr/share/fonts/libertinus/LibertinusMath-Regular.otf

/usr/share/fonts/libertinus/LibertinusMath-Regular.otf:
----- name.ID = 5:
Version 7.051;RELEASE
----- head.fontRevision:
7.051

Reinstalling the font fixed the problem. Sorry for the confusion.


Documentation clarification on pipfile and pinned versions

In the doc section on importing from requirements.txt, it says:

Note, that when importing a requirements file, they often have version numbers pinned, which you likely won’t want in your Pipfile, so you’ll have to manually update your Pipfile afterwards to reflect this.

I'd like more explanation about why one wouldn't want pinned version numbers in a Pipfile. Is there a suggested workflow for teams with respect to committing Pipfile.lock (or not)?

the whole point of a lockfile is to commit it.

You'll want pinned versions sometimes in your Pipfile, but certainly not for all dependencies.

I found this looking for exactly this answer. Would be nice if the documentation included this explanation. Coming from pip I forgot that there is now a lockfile to track specific versions.

I found this thread googling this same question. I believe the answer is explained here: https://www.kennethreitz.org/essays/a-better-pip-workflow
Essentially, pinned versions are a best practice and let you have reproducible builds. Meanwhile, having ranges of acceptable versions (or any version at all) is easier for humans to specify and reason about. (Someone please correct me if I have this wrong.)


bonsai: 1.0.2 -> 1.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for bonsai is: Finite State Machine structured as a tree
meta.homepage for bonsai is: https://git.sr.ht/~stacyharper/bonsai
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.0 in filename of file in /nix/store/f1jb9lgsapf5j2l4n6zm6z77vhj55wpp-bonsai-1.1.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
bonsai

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/f1jb9lgsapf5j2l4n6zm6z77vhj55wpp-bonsai-1.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bonsai https://github.com/r-ryantm/nixpkgs/archive/8bc40ff57e69c3f54d9f6512a4b5bce6e8744b57.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8bc40ff57e69c3f54d9f6512a4b5bce6e8744b57#bonsai

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/f1jb9lgsapf5j2l4n6zm6z77vhj55wpp-bonsai-1.1.0
ls -la /nix/store/f1jb9lgsapf5j2l4n6zm6z77vhj55wpp-bonsai-1.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

bonsai

Maintainer pings
cc @uninsane for testing.

release notes

better usage of streams
Fix crash on exec command errors

in fact it's just 2 new commits since 1.0.2 -- one for each of those release points.


renaming "conditions" for clarity, so it isn't the same as the  macro

I found this example a little confusing, as the condition that gets interpolated in the where clause has the same name as the macro that's used to build it.
Proposing to give different names to these things for clarity, as I was initially wondering how a boolean could be callable! 🤯
dynamic = false
# ...
dynamic([p], p.is_public or ^dynamic)

Good call. I have dropped just one comment!


Count Distinct

Someone can give an example of count distinct ?
Im getting error when i try to query this,
select count( distinct AtBatting) from baseballStats limit 10
Or
select countDistinct ( AtBatting) from baseballStats limit 10

I think the syntax is distinctCount(AtBatting) for this.


[Main Issue] Accelerator and Plugin refactor

Proposed refactoring or deprecation

Motivation
Accelerator is not stable API yet, we can improve the Accelerator related logic and move towards stable Accelerator version for 1.6

Pitch
Steps

Collective refactor #7534

[x] deprecate accelerator collective directly call from TTP #9677
[ ] collective refactor #9414

Move Precision Plugin into TTP #7324
Move Accelerator into Strategy #10648
Simplify the Spawning logic #10059
[RFC] Simplifying the Accelerator Connector logic and flags (can be done in parallel with aboves) #11449  11449
[RFC] Revisit the inheritance of TTP #11863

More details in: Accelerator Refactor Proposal
[updating]
FAQ

Will this be a lot of breaking changes?
Not much user facing API changes from 1,2,3,4.(Unless we found out other existing bugs during refactor) The only breaking change will be for custom plugins
5 and 6 is still RFC stage, may have breaking changes which impact user facing APIs

How does this impact lightningLite?
Should be helpful for lightningLite too, there maybe function refactor/simplification could happen for lightningLite. (@awaelchli  any suggestion about this part?)

Follow up TODOs:

[ ] check if trainer.FITTING before setting up optimizers https://github.com/PyTorchLightning/pytorch-lightning/pull/10596#discussion_r753587321

[ ] Send a PR to  https://github.com/ray-project/ray_lightning  to update their plugins

If you enjoy Lightning, check out our other projects! ⚡

Metrics: Machine learning metrics for distributed, scalable PyTorch applications.

Lite: enables pure PyTorch users to scale their existing code on any kind of device while retaining full control over their own loops and optimization logic.

Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, fine-tuning, and solving problems with deep learning.

Bolts: Pretrained SOTA Deep Learning models, callbacks, and more for research and production with PyTorch Lightning and PyTorch.

Lightning Transformers: Flexible interface for high-performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.

cc @justusschock @awaelchli @akihironitta @tchaton @borda @kaushikb11 @ananthsub

Great summary! About

How does this impact lightningLite?

As best as I can see right now:
Step 1, 2 do not impact Lite. If there are changes in required in the Trainer, they will be mirrored directly by Lite. The Trainer as well as Lite do not make any strong assumptions on the internal composition of plugins.
Step 3: not sure
Step 4: Will impact Trainer more than Lite. Lite is sort of already setting an example here how it could/should look like in the Trainer.
Step 5, 6: should not impact Lite at all (accelerator connector is shared)

Yes, definitely really excited about this. I am quite eager to finally see the accelerators marked as a stable API targetting v1.6.

@ananthsub
https://github.com/PyTorchLightning/pytorch-lightning/pull/10570#pullrequestreview-807890492

It'd be very good to list what APIs this lets us simplify or remove from the Accelerator/strategy/precision plugin. Those could be listed as immediate followups to this PR

Here are some that I found and also some are mentioned in the doc
After 2)
Methods:

Accelerator.optimizer_step (move)
Accelerator.backward (move)
Accelerator.*_dispatch (move + reduce)
Accelerator.*_step (move)
some miscellaneous ones

Property:

Accelerator.amp_backend (move)
Accelerator.precision (move)
Accelerator.scaler (move)

After 3)

TrainingTypePlugin.on_gpu/on_tpu
TrainingTypePlugin.model_to_device

These will either make use of the accelerator or be moved to it.

Now that the precision plugin has moved, I will take a look at this TODO here:
https://github.com/PyTorchLightning/pytorch-lightning/blob/af0bb96f0ff645102680a7adc99dc131cfeb9c0b/pytorch_lightning/lite/lite.py#L433-L439

Here is another follow up we need to do IMO: #10686. This will unblock also #10657

Closing this issue in favor of the smaller linked issues for the pending tasks.


FR: Update nanopb because of security finding

Feature proposal

Firebase Component: Core

In our project we use whitesources to find security issues in the code.
We got an security finding in the nanopb library in the newest firebase 6.21.0
https://nvd.nist.gov/vuln/detail/CVE-2020-5235
Could you please update to a nanopb version that fixed this security issue?
Thank you

@karlkaminski Our nanopb migration is currently pending migrating the Firestore gRPC dependency from a nanopb-dependent version. See #4312.
Once that happens, we'll move the Firebase nanopb version forward.

@paulb777 What is approximate estimation for merging #4312?
We also use WhiteSource and saw the issue with the nanopb.

@tereznikov We don't make commitments about future releases, but will work on the nanopb update in the next month or two."

Now that #4312 has landed, I'm going to pick up the nanopb update project again and try to get it into the next release.


Bump dropwizard metrics-core for Spark 3 runner to match the version used in Spark 3.1

Bump dropwizard metrics-core for Spark 3 runner to match the version used in Spark 3.1 (addresses #23728)
https://github.com/apache/spark/blob/de351e30a90dd988b133b3d00fa6218bfcaba8b8/pom.xml#L149-L149

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

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

R: @aromanenko-dev

Run Java PreCommit

Run Spark ValidatesRunner

Run Spark ValidatesRunner

Wondering if a failed test is related or just flaky?

Run Spark ValidatesRunner

That's a known flaky one https://github.com/apache/beam/issues/23709 :/


Add Custom Messages support

Something like this: http://getgauge.io/documentation/user/current/test_code/csharp/custom_messages_in_reports.html
http://getgauge.io/documentation/user/current/test_code/java/custom_messages_in_reports.html

It is on the roadmap. Should be done sometime soon.

You can now pass custom messages using:
gaugeMessage("Hello, World!");

Detailed example is in the README :-)


NN scaling issue with Convolutional3DLayer

At some point there was code commited changing the behaviour of the net when scaling it.
If I use the code in the pip package everything works fine (0.0.11 seems to contain only code prior to the 7th of may).
https://user-images.githubusercontent.com/54776552/198372984-f704cceb-8582-4bf9-bc23-c15ebb836b34.mp4
However I'm forking the repo (with the latest commit from august) because I need to change some internal code and noticed this problem.
https://user-images.githubusercontent.com/54776552/198373792-fd672ec7-708e-4ebe-b353-e291c8a591dd.mp4
Maybe someone can pinpoint the exact commit which causes this behaviour?
Code used:
class Test(Scene):
	def construct(self):
		# Make the Layer object
		l1 = Convolutional3DLayer(4, 2, 2)
		l2 = Convolutional3DLayer(5, 1, 1)
		l3 = Convolutional3DLayer(2, 3, 3)
		layers = [l1, l2, l3]
		nn = NeuralNetwork(layers)
		nn.scale(2)
		nn.move_to(ORIGIN)
		# Make Animation
		self.add(nn)
		#self.play(Create(nn))
		forward_propagation_animation = nn.make_forward_pass_animation(run_time=5, passing_flash=True)

		self.play(forward_propagation_animation)

Additional note:
The reason I'm forking the project is because I created custom layers which also have corresponding ConnectiveLayers, but in order to make them work they need to be added to the connective_layers_list in the init file.
Perhaps let get_connective_layer in util.py take in an optional list with additional classes? That way one can add layers without modifying the source code.

Hey, sorry I haven't had time to work on this project for a while. I spent some time revamping how the convolutional neural network visualization is done and I think it is much more faithful to the actual algorithm. I will also look into a better solution for allowing the library to be extended (new layers, new animations, etc.) without modifying the code. It is still under development but here is an example of the new CNN visualization.
https://user-images.githubusercontent.com/14181830/210123663-a2814144-75e9-427e-a2dc-013f0870cbeb.mov


Updating CSS Selectors for Atom v1.13+

Hey there, @scottenriquez ! Great work on pulling together this color scheme and theme! I really like it, and I'm sure a couple more people also enjoy it. Just wanted to help out in updating this CSS style to ensure it lasts for a little bit longer without breaking. A couple of the selectors changed completely, so I went ahead and changed those accordingly. Feel free to suggest/add any further adjustments that I may have overlooked.

Greetings, @Kaitachi!
Thank you so much for the contribution! I've merged your changes and published them to APM (v1.1.0). I tested on the latest version of Atom (1.53.0) as well.
-Scottie


add appWidget

connect  and log in KUAS wifi by click appWidget

@vn7n24fzkq Please update widget preview image, the icon in the image scale is wrong.

@hearsilent I had replace widget preview image with correct scale.Please review.

@hearsilent I had replace widget preview image with correct scale.Please review.

@hearsilent I had already changed the image.


feat: add ability to user to set as open or resolved their reports

Hello 👋🏻
Moving forward, allowing users to interact with their reports:

Added ability for a user to set as open or resolve their reports

In addition:

Created a Status component to make SelectStatus less bulky
review the way I pass argument to slack_notification

To consider, PATCH on /issues/[id] is now pretty big, it might be worth improving that in the future.
-- To be reviewed and merged

After discussion with @amedeomajer we conclude to remove the ability to set to open

After an internal discussion, we will disregard this feature for now.


[BUG] Context empty in Wordpress Gutenberg blocks

Expected Behavior
In the Wordpress full site editor we have blocks that show the navigation menu's.
With the upgrade to Timber 2.0 via the composer packages the $context that is set in our timber.php and should provide us menu, options, theme and site in the context is empty.
Instead the $context seems to be re-initialised with the data for that block and current post. Al other data from the timber.php is gone.
timber.php example code:
$context['menu'] = Timber\Timber::get_menu();
       $context['topmenu'] = Timber\Timber::get_menu('top-menu');
       $context['primarymenumobile'] = Timber\Timber::get_menu('primary-menu-mobile');
       $context['primarymenudesktop'] = Timber\Timber::get_menu('primary-menu-desktop');

Navigation gutenberg block:
   $context = Timber::context();
            $context['attributes'] = $attributes;
            $context['block_attributes'] = get_block_wrapper_attributes();

            ob_start();
            Timber::render('blocks/heading.twig', $context);
            return ob_get_clean();

Actual behavior
With the old plugin implementation we had the context from the timber.php available in out blocks.
Now it seems te be loaded later than the blocks are rendered or it is not aware of the existing $context.
Steps to reproduce behavior

...
Notes
No response
What version of Timber are you using?
2.0
What version of WordPress are you using?
6.4
What version of PHP are you using?
8.2
How did you install Timber?
Installed or updated Timber through Composer

Hi @expedition-jeffrey-tempelman
I ran into this issue myself in Timber 1.x once. Also with ACF blocks and FSE. I think the issue was that the Timber::context() call is earlier called then your expansion of the timber/context in your timber.php file.
I did also test if this still occurs, but I have my full context available that is prepared via the timber/context filter in my theme.


Add a secondary battery

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Only one battery.
Expected behaviour
Show two batteries .
Possible Solutions
No response
Mode
Both
Context / Reason
In addition to displaying several strings, display two batteries, as I have two packs with two BMS and I use the data to set the parameters from the BMS and not from the inverter. That's why I want to ask if it would be possible to add a second battery even at the expense of some other parameter (I understand that there is little space), so that the user would choose what to display as a priority for him. I, for example I don't need grid, aux. Thank you.

Hi. Its not planned at the moment. Will keep it open to see if there is any other interest in this feature


Put trusted/untrusted folders into single table

open workspace trust editor
notice how there is a section for trusted/untrusted which identical wording and UI

Instead of the duplication the trust state should be inline, like a check box in front of a row or some toggle button as new trust column

By getting rid of the Unspecified state, users will only have to manage one list of folders - "trusted folders".

All locations that are not covered by the list of trusted folders will default to 'Untrusted`.

I don't think that will work. I have trusted /Users/jrieken/Code but untrusted /Users/jrieken/Code/_samples and I don't see how that will work with a simple trusted list

Yes this removes some fancy folder structures but it makes the question much simpler... where do you put your trusted source

I strongly disagree with this attitude. This already worked and a UI for this isn't rocket science. On the other hand we pushing a very disruptive change onto our users and our best answer shouldn't be that you need to move your folders around. I think this would have been acceptable when VS Code had started like that but given we are years into the project we shouldn't be that bold and more supportive to existing and working setups

@jrieken, sorry for not getting back to you on this until now. My hypothesis is that your response is mostly fuelled by the fact that something that was there, which was then taken away. If we would have shown workspace trust without the capability to specify untrusted folder, I am fairly confident that you wouldn't have had such a strong reaction.
I am adding the feature-request label to the issue and will be looking out for similar requests in the future.

If we would have shown workspace trust without the capability to specify untrusted folder, I am fairly confident that you wouldn't have had such a strong reaction.

The attitude is causing my reaction. The old model really matched to how my source files are organised on disk. All source is ~/Code/, random/untrusted stuff is in ~/Code/_samples, "untrusted" extensions are in ~/Code/_allExtensions. I wanna trust everything in ~/Code/ except for those two folders.

I don't believe I am the only user of VS Code with such a structure and I don't understand the resistance to support such a cases. Sure, moving folders around is easy but I will lose my history of recent files/folders and I am not accepting that. Also, generally, VS Code should adapt to my setup and not the other way around.

Closing this issue in favor of #126311 which already received the necessary community votes.


ERROR:  new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)

Clean Ubuntu 22.04 instance. Ran though the standard process, got to the question about setting up the DB. enter all the way though, and then yes for "create db". then i get the following error:
PG::InvalidParameterValue: ERROR:  new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)
HINT:  Use the same encoding as in the template database, or use template0 as template.

found the following: https://stackoverflow.com/questions/16736891/pgerror-error-new-encoding-utf8-is-incompatible ran the commands in the first answer and it worked...

Thanks for finding that. To confirm, you carried out the steps:
UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';
DROP DATABASE template1;
CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE';
UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1';
\c template1
VACUUM FREEZE;

On that system, could you tell me what shows up when you run locale?

i actually deleted the machine cause i was having issues with it building the public files (kept getting 500 errors). going to try build it again later... the other box was an LCX container, and a simular box has the following result when running locale:
LANG=C
LANGUAGE=
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=


Configure nav helpers with statsd

Trello: https://trello.com/c/S72dddmO/488-configure-navigation-helpers-with-statsd
Counters

Timers

Re-written based on comments from https://github.com/alphagov/frontend/pull/1157


Aqara Light Bulb

[12/28/2019, 11:10:44 AM] [ZigBee] Retrying connect to hardware
[12/28/2019, 11:10:51 AM] [ZigBee] Retrying connect to hardware
[12/28/2019, 11:10:58 AM] [ZigBee] Retrying connect to hardware
[12/28/2019, 11:11:05 AM] [ZigBee] Retrying connect to hardware
[12/28/2019, 11:11:12 AM] [ZigBee] Retrying connect to hardware
[12/28/2019, 11:11:18 AM] [ZigBee] ZigBee platform initialized, info:
[12/28/2019, 11:11:18 AM] [ZigBee] ------------------------------------
[12/28/2019, 11:11:18 AM] [ZigBee] channel: 11
[12/28/2019, 11:11:18 AM] [ZigBee] pan id: 0x5430
[12/28/2019, 11:11:18 AM] [ZigBee] extended pan id: 0xdddddddddddddddd
[12/28/2019, 11:11:18 AM] [ZigBee] ieee address: 0x00124b00193e50db
[12/28/2019, 11:11:18 AM] [ZigBee] nwk address: 0
[12/28/2019, 11:11:18 AM] [ZigBee] firmware version: 2.6.3
[12/28/2019, 11:11:18 AM] [ZigBee] firmware revision:<PHONE_NUMBER>
[12/28/2019, 11:11:18 AM] [ZigBee] ------------------------------------
[12/28/2019, 11:11:18 AM] [ZigBee] Unrecognized device: 0x00158d0002c65f0d LUMI lumi.light.aqcn02
spinlock: false []
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 1 of 17
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 2 of 17
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 3 of 17
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 4 of 17
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 5 of 17
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 6 of 17
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 7 of 17
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 8 of 17
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 9 of 17
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 10 of 17
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 11 of 17
[12/28/2019, 11:11:50 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 12 of 17
[12/28/2019, 11:11:51 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 13 of 17
[12/28/2019, 11:11:51 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 14 of 17
[12/28/2019, 11:11:51 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 15 of 17
[12/28/2019, 11:11:51 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 16 of 17
[12/28/2019, 11:11:51 AM] [ZigBee] Join progress: interview endpoint 1 of 1 and cluster 17 of 17
[12/28/2019, 11:11:51 AM] [ZigBee] Device announced incoming and is added, id: 0x00158d0002c65f0d
[12/28/2019, 11:11:52 AM] [ZigBee] Unrecognized device: 0x00158d0002c65f0d LUMI lumi.light.aqcn02
[12/28/2019, 11:12:18 AM] [ZigBee] [RouterPolling] ping device: 0x00158d0002c65f0d
[12/28/2019, 11:13:18 AM] [ZigBee] [RouterPolling] ping device: 0x00158d0002c65f0d
[12/28/2019, 11:14:18 AM] [ZigBee] [RouterPolling] ping device: 0x00158d0002c65f0d

[12/28/2019, 2:47:48 PM] [ZigBee] Registered device: 0x00158d0002c65f0d LUMI lumi.light.aqcn02
spinlock: false []
Uncaught Exception TypeError: this.clearTimeout is not a function
at Characteristic.onCharacteristic.on (/usr/local/lib/node_modules/homebridge-zigbee/lib/devices/lumi.light.aqcn02.js:33:12)
at Characteristic.emit (events.js:203:15)
at Characteristic.setValue (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Characteristic.js:321:10)
at Bridge. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:882:22)
at Array.forEach ()
at Bridge.Accessory._handleSetCharacteristics (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:822:8)
at HAPServer.emit (events.js:198:13)
at HAPServer._handleCharacteristics (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:974:10)
at HAPServer. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:209:39)
at IncomingMessage.emit (events.js:198:13)
[12/28/2019, 2:47:49 PM] TypeError: this.clearTimeout is not a function
at Characteristic.onCharacteristic.on (/usr/local/lib/node_modules/homebridge-zigbee/lib/devices/lumi.light.aqcn02.js:33:12)
at Characteristic.emit (events.js:203:15)
at Characteristic.setValue (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Characteristic.js:321:10)
at Bridge. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:882:22)
at Array.forEach ()
at Bridge.Accessory._handleSetCharacteristics (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:822:8)
at HAPServer.emit (events.js:198:13)
at HAPServer._handleCharacteristics (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:974:10)
at HAPServer. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:209:39)
at IncomingMessage.emit (events.js:198:13)

The problem only arises when i try to turn on/off the bulb or change the brightness. Chaning just the color temperature is working perfectly fine


Access attributes in XmlNode using Map instead of List

I think it would be much more convenient and faster (in terms of performance) to use something like this to access attribute on xmlNode:
element.attributes['attr1'].value

instead of:
element.attributes.firstWhere((XmlAttribute e)=>e.name.qualified=="attr1").value

Also this way would be much easier to detect attribute duplicates, which are not allowed in XML.

What about using
element.getAttribute('attr1')
?

Shame on me :)
ср, 3 Июн 2015, 21:53, Lukas Renggli<EMAIL_ADDRESS>
What about using
element.getAttribute('attr1')
?
—
Reply to this email directly or view it on GitHub
https://github.com/renggli/dart-xml/issues/14#issuecomment-108573719.


Generalize climo task

Generalize climo task:

Multiple components (eam, elm, mosart). Support for mpas is untested.
Option to regrid or not (mapping_file = file or mapping_file = "").
Diurnal cycle climatologies.
Option to include/exclude variables.

@forsyth2 : I have been using this branch for several days without any incident. I'm confident it doesn't break anything and it's ready to be merged. I have not yet validated the diurnal cycle climatologies, but we can do that as part of https://github.com/E3SM-Project/zppy/pull/2

@golaz Sounds good, I'll switch my zppy to a copy of this branch and submit the jobs to run on my model run before I log off. If everything looks good in the morning I'll approve this PR.

Thanks, @forsyth2. I did a squash and merge from here. Not sure if it's equivalent to what you suggested.


Simplify Development Setup

Context
The current development setup instructions are pretty long and complicated as seen in https://github.com/icefoganalytics/elcc-data-management#development.
Some easy wins would be:

Docker-izing the whole app so that you only need dev boot to boot all three containsers. - DONE
Automating the migration and seeding process of the database, so that it happens as part of initial container boot. - DONE
Moving development config variables inside of docker compose setup. - PARTIALLY COMPLETED
Installing mssql-cli in the database container so SQL usage is less painful. - fixing in https://github.com/icefoganalytics/elcc-data-management/issues/13
Switching to Sequelize over Knex. - fixing in https://github.com/icefoganalytics/elcc-data-management/issues/12

I broke this ticket into a bunch of smaller ones.


Links on spark-example/README.md are broken

The following links listed in the README.md file are broken:
https://firelyteam.github.io/spark/
https://firelyteam.github.io/spark/quickstart

Thanks, they have now been corrected


conus404_osn

I added the OSN copy of CONUS404 to the conus404-catalog and linked to the conus404-catalog from the main hytest catalog.
I did not delete the entries of CONUS404 from the main hytest catalog yet because I don't have time to scrape/update the notebooks catalog paths before I go on leave today. Feel free to merge this in, and I will make another PR next week to update any notebooks (unless someone else has time!).

I'll let @alaws-USGS be the official reviewer to merge this in, but also just want @gzt5142 @sfoks and @rsignell-usgs to know about this change


[UBS. Sign up] The verification email does not match the mockup UA/EN

Environment: all
Reproducible: always
Build found: 06.05.22
Steps to reproduce
1.Go to https://ita-social-projects.github.io/GreenCityClient/#/ubs
2.Click on 'Sign up' button
4. Enter valid values in all fields
5. Click on 'Sign up' button
6. Go to your mailbox and open the letter to complete the registration
7. Pay attention to the content of the letter
Actual result
After registering on the UBS page, the user receives an e-mail from Green City.
Expected result
After registering on the UBS page, the user receives an e-mail from UBS (see attached files).
The changes apply to the Ukrainian and English versions of the site.
User story and test case links
https://www.figma.com/file/JvDAu4MHnh1Vxc5FaokyiA/ITA-UBS-styles?node-id=12201%3A2

The verification email still does not match the mockup UA/EN
Below is the real verification email has got 03.06.22

The verification email's title has been reviewed and is now accurately displayed.


The Game not working on M1 macs

When I install the compiled binaries but the game just crashes straight up and don’t show and flashy screens

Ah, that's unfortunate. Sorry, I don't have an ARM mac yet, so I can't easily investigate this. Maybe someday, when I have one of the newer macs, I'll look into why it doesn't run natively. But with apple dropping support for OpenGL, it's only a matter of time before this older version of the game doesn't work at all on macs.
But there is a newer version of the game for gameboy advance, which can be run on macos in a gba emulator:
https://github.com/evanbowman/blind-jump-portable


nushell: 0.89.0 -> 0.90.1

Description of changes
update nushell and its plugins, following PR from ryan-tm https://github.com/NixOS/nixpkgs/pull/286923
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

After trying to disable just this test with "--skip=main" "--skip=const_string_interpolation" (which both didn't work). I'm disabling the test until the next update.


Remove ununsed tests in enmasse 1.0

Type of change

Refactoring

Description

Remove only tests for enmasse 0.3x, next PR must remove all lib function which we do not need for enmasse 1.0
Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@enmasse-ci run tests profile=systemtests test_only

FYI i'm trying to fix the tests that are failing for isolated-shared-infra in the remove-modules branch

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: systemtests
TEST_CASE:
TOTAL: 27
PASS: 23
FAIL: 0
SKIP: 4
BUILD_NUMBER: 1139
BUILD_ENV: oc cluster up


InlinedVector::clear() should lazily avoid deallocating out-of-line memory

abseil-cpp/absl/container/inlined_vector.h
Describe the bug
InlinedVector::clear() method should lazily avoid deallocating out-of-line memory, if already allocated.
This would be in line with the behavior of std::vector, for which it is designed to be a drop-in replacement.
Deallocation on clear() means that if any number of elements beyond the inline capacity are re-pushed into the container, it will reallocate and re-copy contents unnecessarily.
As of this writing, the master branch still has storage_.DeallocateIfAllocated(); in clear()
Steps to reproduce the bug
InlinedVector<int, 8> container;
container.reserve(max_size); // because I KNOW what the maximum required size is, but not necessarily at compile time
for (int count=max_size; count>0; --count) {
#if UGLY_WORKAROUND
    container.erase(container.begin(), container.end());  // does not deallocate
#else
    container.clear();  // deallocates storage :-(
#endif
    for (int i=0; i<count; ++i)
        container.push_back(i);
    do_something_with(container);
}

If called with max_size set to 16, the above code will trigger rellocation+copy at least 8 times.
With the workaround (or correct clear() behavior) it will never reallocate/copy.
What version of Abseil are you using?
Any, AFAIK.
Specifically, lts_2020_02_25 has it.
What operating system and version are you using
Irrelevant, but Ubuntu 18.04
What compiler and version are you using?
g++ 7.5.0
What build system are you using?
None (make)

@CJ-Johnson looked into making this change a year ago, but found it broke a lot of code and was unable to make the change.
@CJ-Johnson, are you willing to take another shot at this?

Tap on a clip to paste it in the text box.Touch and hold a clip to pin it. Unpinned clips will be deleted after 1 hour.Use the edit icon to pin, add or delete clips.Welcome to Gboard clipboard, any text you copy will be saved here.

I don't have the cycles at the moment, but it is on my list!
For tracking purposes, the corresponding bug ID is 138307414


UNIX epoch conversions issue

When I try and extract the date and time from a UNIX epoch it's returning in correct values.
$ sqlite3

.load ./libparquet

CREATE VIRTUAL TABLE trips USING parquet('parquet/000000_0');

select pickup_datetime,
       datetime(pickup_datetime, 'unixepoch')
from trips
limit 1;

1240714560000|-1413-03-01 13:07:12

1240714560000 should be Sunday, 26 April 2009 02:56:00. Any idea how I could extract the year at the very least? Is there another time extraction function I should be using?

I think that's ms since the epoch and datetime(..., 'unixepoch') wants seconds -- try dividing pickup_datetime by 1000 first?

Good spot, works a treat now.


Add conda installation

Create a conda installation. Waiting for a python3 Cassandra conda installation to be available.

Conda installation created! Closing PR.


AnimatableSectionModel.swift has a warning (0.5.0)

is:issue is:open .../Pods/RxDataSources/Sources/DataSources/AnimatableSectionModel.swift:96:61: 'HashableSectionModel' is deprecated: Please use AnimatableSectionModel or your own model implementing AnimatableSectionModelType

This should we fixed now. I've released a new version.


Fix domains.get documentation naming

The naming is misleading in the example

It's a generated doc and i probable must make the fix somewhere else


transaction w/o class method decorator

Firstly, thank for your awesome lib @odavid !
In our current project we're on the way to use this lib to resolve some issues which we're facing with TypeORM core transaction. But we found that this lib just supported class method decorator. I implemented two helpers that can help to run transaction in the middle of the method/function body or wrap the a function that will run in transaction
import { Transactional } from 'typeorm-transactional-cls-hooked';

export class TransactionRunner {
  @Transactional()
  static run<Func extends (this: any, ...args: any[]) => ReturnType<Func>>(fn: Func) {
    return fn();
  }
}

export function wrapInTransaction<Func extends (this: any, ...args: any[]) => ReturnType<Func>>(
  fn: Func
): Func {
  function wrapped(this: unknown, ...newArgs: unknown[]): ReturnType<Func> {
    return TransactionRunner.run(() => fn.apply(this, newArgs));
  }

  return wrapped as Func;
}

Then we can use it like this:
function myService() {
  // do something here, e.g. call external service to get data
  ....
  TransactionRunner.run(() => {
    ....
  })
}

Or wrap a function:
function myService() {
 // do something
 .....
}
export default wrapInTransaction(myService);

But the problem is that I couldn't found a way to pass Propagation and Isolation option to these functions. Is there any suggestion or it's reasonable to create a new PR that will extract the logic from Transactional.ts?

Hi,
PR will be reasonable...
Cheers

I think this can be closed now that the PR was merged, although this should probably be documented in the README.


Add new issues depending on feedback / optional features

WE have time to work on a few optional features, we should decide which ones we want to try to implement in this time frame

From the first 3 usertests all requests were implemented that could be made in the short time


Highlight matched parts in current candidate?

Currently, selectrum uses a single face selectrum-current-candidate with current candidate, so we can't see the matched parts. Ivy highlights the matched parts even in the current candidate. Could we make selectrum behave the same?

Ok, that seems reasonable. It seems this is not native functionality in Emacs; see ivy--add-face for the implementation.

Thanks!


SSA-Renaming-Fix

I changed up the order of renaming and using the names in loads from SSA to support the following example:
code_str = """
b = 10
b = b + 1
if b>0:
a = a+b
else:
a = 10
print(a)
"""
Before b = b + 1 resulted in b_1 = b_1 + 1 instead of b_1 = b_0 + 1

Thank you  for the fix!


fix: icon imports

as per https://github.com/carbon-design-system/carbon/issues/6602#issuecomment-729207760
we should be importing from the top level package '@carbon/icons-react' only, not via direct references to 'lib'

@asfordmatt good catch Matt -- this looks like it will help with optimising bundles. Thanks for opening this PR. I notice that ComboButton also uses the deprecated way to import icons, so I've added a fix for that too.


Cannot npm install with latest version of npm (npm ERR! ERESOLVE could not resolve)

Hello, with:
 ~  node -v
v18.12.0
 ~  npm -v
9.1.2

When I try npm i I am getting (on Windows 10, although I don't believe it matters):
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/common
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>|| ^15.0.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/@angular/cdk
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@angular/material
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!   5 more (@angular/forms, @angular/material, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@">= 6.0.0 < 11.0.2" from<EMAIL_ADDRESS>npm ERR! node_modules/an-qrcode
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@angular/common
npm ERR!   peer @angular/common@">= 6.0.0 < 11.0.2" from<EMAIL_ADDRESS>npm ERR!   node_modules/an-qrcode
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!

Sorry about this -- the an-qrcode demands an old version of Angular, so installing currently requires the --legacy-peer-deps flag while installing 😢
I'll try to fix this up somehow - at the very least with a comment in the README 🙇
Thank you for raising this issue 🤝

Thanks for the very prompt response! 😄 👍🏼
I tried this already, and I get 8 high vulnerabilities 😞
 ~  npm install --legacy-peer-deps
npm WARN deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm WARN deprecated<EMAIL_ADDRESS>Please use @electron/asar moving forward.  There is no API change, just a package name change
npm WARN deprecated<EMAIL_ADDRESS>Please use @electron/osx-sign moving forward. Be aware the API is slightly different

><EMAIL_ADDRESS>postinstall
> electron-builder install-app-deps

  • electron-builder  version=23.6.0
  • loaded configuration  file=D:\code\github\Video-Hub-App\electron-builder.json

added 1279 packages, and audited 1280 packages in 2m

190 packages are looking for funding
  run `npm fund` for details

11 vulnerabilities (3 moderate, 8 high)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

I'll be running npm audit fix (as usual) before I create the next release 🤝

Thank you, and kudos for this amazing project! 😄 👍🏼

ps - the repository that causes the error 😅
https://github.com/naimmalek/an-qrcode/issues/7
I created a PR for it to fix the problem too 😊
https://github.com/naimmalek/an-qrcode/pull/11

I updated the README to make sure others don't run into this annoyance 😅
https://github.com/whyboris/Video-Hub-App/pull/781/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R45
Cheers!


Version 0.2

I'm planning to finish all features at Version 0.5. Version 0.2 will still focus on the client part, and we will start the implementation of server/provider from Version 0.3.

[x] Finish Django Client
[x] Documentation on Django Client
[x] Simple OpenID Connect support (id_token parsing)
[x] Documentation on id_token parsing
[x] Making Client Apps stable

When the client part is finished, we will deploy a playground website for OAuth authentication.
It will be implemented with the Authlib Flask client.

[ ] create an online playground for OAuth clients (https://github.com/authlib/playground)

Version 0.2 is released. We'll track the progress of playground in its own repository.


fix: catch init failures during run

Motivation/Description of the PR
When running run-multiple and there's an error during initialization (such as an exception when loading helpers for example), codeceptjs would return a 0 exit code, because the error becomes an unhandled promise rejection.
With this change, the error is handled by run.js, and the process returns a non 0 exit code.
Type of change

[x] :bug: Bug fix

Checklist:

[x] Tests have been added
[ ] Documentation has been added (Run npm run docs)
[x] Lint checking (Run npm run lint)
[x] Local tests are passed (Run npm test)

Thanks!


[TRAVEL] Landing-page discover/activities/adventures

Adds blog-preview component, functional "Activities" filter, and interactive "Adventures" gallery.

I'm going to review this really quick, just noticed a few things that could be done to make the Google review of this PR a bit easier


Page header

Hey @ThePeach, here's the header work I've done so far. There's one outstanding thing that I wanted to add, but I've run out of time:

Make the nav menu collapsible on narrow viewports

My plan was to write some simle JS to let the menu button toggle an aria-expanded="true|false" attribute on the <nav> element and then use CSS to apply an open/close animation or transition.
I was reading stuff like https://inclusive-components.design/menus-menu-buttons/ to find a solution that will play nice with assistive tech.

Other than that, it's all good to go though. Here are the main things I've done (which'll hopefully aid your review):
SASS conventions
I had a stab at establishing some naming & coding conventions for the SASS code (see https://github.com/buildit/gravity-ui-sass/blob/page-header/docs/naming-conventions.md).
It's using HTML element & attribute selectors as much as possible and BEMIT for everything else.
A tad unusual perhaps, but I see a lot of people who are unfamiliar with HTML5's many built-in features and semantics and was hoping this might be a good way to raise awareness of those things.
However, if you feel strongly, you're welcome to adapt or modify these.
For now, I've tried to follow these conventions for my own code. And, FWIW, it's gone pretty smoothly so far.
SVG icons
I'm using inline SVG symbols and then referencing them by ID wherever icons need to be displayed in the UI. It's all wired up into PL.
I suggest pulling my branch, running locally and then reading the pattern info descriptions I added. Hopefully they explain what I did and why.
Page header
With the coding conventions and icon system in place, I've begun building all the parts I needed in order to assemble a header. I produced some extra atoms along the way (e.g. types of buttons).
I've made an effort to add solid documentation to each pattern to encourage correct usage and (hopefully) teach people a thing or two too. :-)
The nav-menu component uses Flexbox and I deliberately populated it with awkward content (long link labels & more links than fit in a single row) to stress test it. My intention was to make it as robust as possible.
The example page I added shows it populated with the links we'd actually use for the site.
Aesthetically it's basic for now. I think we should build out a skeletal UI in Pattern Lab first and then begin tweaking and tuning the visuals.

This is just the first of my review of this pull request, as I'm still going through it and it would take me a bit to finish it.
Code standards
Very good job 👍 , I think for now they work, as you said it's just an initial draft and I'm generally OK with it, both in using BEMIT and few additional stuff in the way selectors are used.
My main problem here is the amount of variables being generated, which IMO will soon become an impediment as we scale. The idea is that we should strive to keep them as easy to remember, and at the same time functional. A very good example is the amount of colours defined and aliased. Which is why probably having some mixins that give you the right colour might be a better choice (especially if you're looking for the accessible inverted colour for any given one.... (e.g. I want an orange tint that can go on black). Food for thought.
Regarding the various patterns that you created in the way of creating the navigation organism and the header in general I think you went a bit overboard. Nothing bad with it, but there's a lot of stuff we are not yet using which is why I'm struggling a bit to understand if it actually makes sense, while I would have probably created the barely minimum rather than having to go back and refactor. Just a thought as well. I think it's fine so far.
Same goes for the styling: I would have probably avoided making the menu this much styled, but I think it's fine for now.I already see that font sizes and line heights need to be adjusted; I'm saying this mostly because now I'm drawn into the trick of seeing something visual and catching a few things that don't really work IMO. An example is the colours used on the active state of the links.

I've noticed that some patterns are not being generated appropriately, I will try to double check this, but at the moment I had to go and re-save each pattern to have the output correctly generated.
This happened with the SVG icons, which didn't generate anything, and the menu links which outputted some undefined for some reason.

I've cleaned up some patternlab styles and markup to reuse a bit of the existing classes. I think we might need to write some documentation or either start switching to SASS compilation altogether, before it starts to become a mess. As a precaution I've started adding some @define before each class definition.

Regarding the collapsible menu, which is now the only thing I'd add, I wanted to implement it purely in HTML/CSS, similarly to this CodePen. TL;DR: the icon is basically a checkbox, that triggers the visibility of the menu itself.


Breakage caused by recent changes to tokio

As far as I can tell there are three changes: removal of poll_ready from the Service trait in tokio-service and tokio-proto; rename and changes to tokio_core::easy; changes to the ways that NewService can be implemented.
I was able to work around the first two by removing implementations of poll_ready and pulling a older copy of easy.rs into tarpc. I am struggling to understand how to respond to the NewService change though. This problem shows up when I try to build readme_future.rs.

I'm planning on updating for the latest tokio changes once the major tokio-proto churn is complete -- I think that essentially just means waiting for https://github.com/tokio-rs/tokio-proto/pull/75 to land.

Do note that I fully intend to support the latest versions of tokio in the future. Right now is particularly rough because so many of the dependencies haven't had a crates.io release yet.

👍


More detail in case of a FormatException: Input string was not in a correct format

Hi!
First of all great job with the lib.
Got a question regarding the exception we get when we try to parse with wrong type of argument:
We are seeing that the library will throw a 'FormatException: Input string was not in a correct format' with no information regarding which xml field is causing this problem. This is an issue with really long XMLs, let's say we are trying to parse an extensive XML with an argument with the wrong type, it would be useful to have more information about what XML element or entity object parameter is responsible for the exception.
Is there any way to get this information out of the lib? Setting... etc?
Keep up the good work!

Hey thanks for the kind words and for wriitng in, @caetanopaulo.  I believe we have what you are looking for here:
https://github.com/wojtpl2/ExtendedXmlSerializer/issues/214
Sample code is provided there, but the magic is using ConfigurationContainer().EnableMemberExceptionHandling().  Please let me know how that treats you and if you have any other questions/issues that arise from this. 👍

That worked!
Thanks for the quick reply.
:)


Suggestions

Piggy Custom Enchantment Doesn't Save

Piggy Custom Enchantment Doesn't Save

Basically, this plugin save item NBT, thats mean its save every item data. I don't know how PiggyCustomEnchants working now...


Add NFS server shares role

Old style NFS (no authentication)
There's a bug with the current NFS package which means you may error messages in the logs, and there may be delays when you first access a file https://bugzilla.redhat.com/show_bug.cgi?id=1285097

I assume this is already deployed somewhere?

Runnign this on a non-up-to-date system it was necessary to manually run systemctl start rpcbind before systemctl start nfs-server. TODO: If this still occurs after a full package upgrade it should be included in this role.

NFS now starts automatically after a system upgrade.


HUD Not Dismiss

While calling HUD frequently,I got a problem that the UI Jammed,the HUD stayed even I have called dismissMethod.And I'm sure I 'm running the latest version.

It looks like you're using the demo app. What steps did you perform to reproduce this?

Yep, I got this problem first on my App which integrates your code(thanks),It do fine on IOS9 but have little problem on IOS8 ,I guess there is some problem with my code But I found the same issue on your demo code while randomly click different HUD, and also this happens on IOS8 iphone4s
发自我的 iPhone

在 2016年9月1日，上午5:50，Lars Anderson<EMAIL_ADDRESS>写道：
It looks like you're using the demo app. What steps did you perform to reproduce this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


split: implement remaining -n variants and pass GNU tests/split/fail.sh

A draft PR to implement 2 missing variants of --number (-n) option for split
K/N
r/K/N

As well as passing GNU tests/split/fail.sh
NOTE: Includes code changes from PR #5222, so this one can be merged instead of #5222
Fixes #5033

@tertsdiepraam @sylvestre this is rather big one, but all of that had to be included to pass GNU test tests/split/fail.sh
It can replace the PR #5252 for split -1 in as it includes all its functionality (also required to pass that GNU test)
Please let me know how you would like to proceed between these two PRs

besides these minor two comments, great work :)

besides these minor two comments, great work :)

That you! :) I have refactored it a bit following your suggestions

@sylvestre could you please let me know if you have any other suggestions/comments before this PR can be merged?

it looks great. @tertsdiepraam don't hesitate if you want to do a post landing review


Documentation or a manual badly needed

Although the Javadoc is not bad, and the "examples" module provides quite some insight, a good manual ( on running / managing a network or cluster, on discovery, on NAT traversal ) would be very good. Any plans ?

The plan to start the documentation is when all testcases are green. This should be definitively before 16.2.2015 as we'll use TomP2P for the lecture: http://www.csg.uzh.ch/teaching/fs15/p2p.html

Can I ask some general high level questions here before I dive into the code ?

Where are the key,values stored, in memory? (I think answer is yet) can I provide my own storage mechanism?
Are key,values tied to a single peer? is that peer disappears does the key,value disappear? (I think answer is yet) Can key,values be distributed over many peers so that if one disappears they can still be found? (resiliance of data).
Can I send messages direct from one peer to another?

On 08/27/2015 03:35 PM, philip andrew wrote:

Can I ask some general high level questions here before I dive into the
code ?

Sure!

Where are the key,values stored, in memory? (I think answer is yet)
can I provide my own storage mechanism?

Its in memory by default, you can provide your own mechanism, or use a
disk-base storage using MapDB.

Are key,values tied to a single peer? is that peer disappears does
the key,value disappear? (I think answer is yet) Can key,values be
distributed over many peers so that if one disappears they can still
be found? (resiliance of data).

No, there is a replication factor, so a key,value will be on more than
one peer. There is the possibility to add replication to not loose the data.

Can I send messages direct from one peer to another?

Yes, direct messages are supported as well.

Thanks, I will attempt to use this as a discovery and transport mechanism for Akka Actor (Scala) message sending and receiving. It seems this has the right set of features but I still don't have much understanding on it, I need to read code.

The plan to start the documentation is when all testcases are green. This should be definitively before 16.2.2015 as we'll use TomP2P for the lecture: http://www.csg.uzh.ch/teaching/fs15/p2p.html

Hi. All the links on the lecture page to PDFs are all timing out from my location in the US.


Tremor cannot be run directly from windows

Problem
'tremor' is not recognized as an internal or external command,
operable program or batch file.
Steps

Download and unpack (tremor-0.12.4-x86_64-unknown-linux-gnu.tar.gz) directly on windows
Execute "tremor server run"

Possible Solution(s)

encourage users to install the system under WSL if tremor doesn't work directly on windows,
update installation instructions accordingly

Notes
None
Output of rustup --version:
rustup 1.27.1 (54dd3d00f 2024-04-24)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active rustc version is rustc 1.81.0 (eeb90cda1 2024-09-04)
Output of rustup show:
Default host: x86_64-pc-windows-msvc
rustup home:  C:\Users\Petri.rustup
stable-x86_64-pc-windows-msvc (default)
rustc 1.81.0 (eeb90cda1 2024-09-04)
Output of tremor --version:
bash: tremor: command not found

more appropriate issue raised under tremor-www:
(https://github.com/tremor-rs/tremor-www/issues/335)


Prebuilt binary (package) for Alpine Linux

Hi, I'm trying to get Dlib into Alpine Linux. This will allow Alpine users to install Dlib easily using the package manager with apk add dlib. Version 19.18 has been in the testing repo for a while now and it works fine. I'm trying to get 19.20 in the community repo with this merge request, but the build/tests have some problems. This depends on the platform on which is it built. See below for details.
Can anyone help me to get these sources to compile? Is it even realistic to get it working for all of these platforms?
Expected Behavior

Alpine Linux has a prebuilt binary package. This is attempted in this merge request.
Current Behavior

For some platforms source compilation fails, for some certain (but not all) tests fail.  See below under "Platform" for detailed logs.
Steps to Reproduce

Run abuild -r on https://gitlab.alpinelinux.org/agboom/aports/-/tree/master/community/dlib
Better: build it using the Alpine pipeline.

Version:  19.20
Where did you get dlib:  GitHub releases (see APKBUILD)
Platform:

aarch64 (https://gitlab.alpinelinux.org/agboom/aports/-/jobs/268168)
ppc64le (https://gitlab.alpinelinux.org/agboom/aports/-/jobs/268167)
s390x (https://gitlab.alpinelinux.org/agboom/aports/-/jobs/268166)
x86 (https://gitlab.alpinelinux.org/agboom/aports/-/jobs/268165)
x86_64 (https://gitlab.alpinelinux.org/agboom/aports/-/jobs/268164)
armv7 is the only platform that does build successfully  (https://gitlab.alpinelinux.org/agboom/aports/-/jobs/268169)

Compiler:

-- The C compiler identification is GNU 10.2.1
-- The CXX compiler identification is GNU 10.2.1

There is confusing stuff in https://gitlab.alpinelinux.org/agboom/aports/-/tree/master/community/dlib.  For instance, nothing in dlib uses C++20 features and similarly dlib does not use the Intel TBB.  It seems like something that was done external to dlib is causing this trouble.

Thanks for reaching out @davisking. That comment is pretty old and I could also be wrong there, my C++ is pretty rusty. Sorry for the confusion. In the more recent builds these problems don't happen anymore.
Looking closer at some of the logs, the x86_64 build seems to fail because of virtual memory exhaustion (logs here). That could easily be fixed by giving the build system more memory I think.
The x86 build has some failing tests, namely test_fhog, test_image, test_matrix, test_optimization, test_random_forest, test_sparse_vector and test_statistics (logs here). Do you have an idea why these tests could fail?
In the other builds (ppe64le, aarch64 and s390x ) build there's a segmentation fault (ARM64 logs here). Not sure how we could debug that, but I also don't know if it's feasible to support these platforms so I could also disable these.

Some of those tests might be because the testing epsilons are just slightly
too tight.  You should also try building without linking to any external
BLAS library.  Sometimes people build blas libraries badly and break them,
then that breakage shows up as failures in dlib's unit tests that
ultimately depend on BLAS.
If the compiler seg faults you should report that to the compiler project.
Although maybe you are just running out of RAM there too.
On Sun, Dec 13, 2020 at 3:44 PM Adriaan Groenenboom <
<EMAIL_ADDRESS>wrote:

Thanks for reaching out @davisking https://github.com/davisking. That
comment is pretty old and I could also be wrong there, my C++ is pretty
rusty. Sorry for the confusion. In the more recent builds these problems
don't happen anymore.
Looking closer at some of the logs, the x86_64 build seems to fail because
of virtual memory exhaustion (logs here
https://gitlab.alpinelinux.org/agboom/aports/-/jobs/268164/raw). That
could easily be fixed by giving the build system more memory I think.
The x86 build has some failing tests, namely test_fhog, test_image,
test_matrix, test_optimization, test_random_forest, test_sparse_vector and
test_statistics (logs here
https://gitlab.alpinelinux.org/agboom/aports/-/jobs/268165/raw). Do you
have an idea why these tests could fail?
In the other builds (ppe64le, aarch64 and s390x ) build there's a
segmentation fault (ARM64 logs here
https://gitlab.alpinelinux.org/agboom/aports/-/jobs/268168/raw). Not
sure how we could debug that, but I also don't know if it's feasible to
support these platforms so I could also disable these.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/davisking/dlib/issues/2257#issuecomment-744065883,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPYFRYKA5FB34UNATI6UZTSUURUVANCNFSM4UVQTUKA
.

Thanks, I'll try that. To achieve that, do I need to include the BLAS source in the build, instead of using openblas-dev as make depend?

There's also a blas package in Alpine. Maybe that would work better with dlib?

The build logs indicate that the examples get compiled as well. Are these needed for package binaries? If not, could I somehow exclude them?
For example:
[ 13%] Building CXX object examples/examples_build/CMakeFiles/queue_ex.dir/queue_ex.cpp.o

Just don't link dlib to any BLAS.  It will use its own internal code.  Like in CMake there is a DLIB_USE_BLAS setting. Make it false.
The unit test build script builds everything.  If there are things you don't want to build then comment them out.

I rebuilt with internal BLAS and the good news is: no segfaults anymore :tada:
However, some tests still fail. Less than before it seems, just one or two per platform. Except for x86, which has 7 failing tests.
Interestingly enough, now only x86_64 builds successfully, while the other platforms fail.
Link to build logs on all platforms: https://gitlab.alpinelinux.org/agboom/aports/-/pipelines/64794
Link to new APKBUILD: https://gitlab.alpinelinux.org/alpine/aports/-/blob/309fec5d61a86380ac2a43790d1843bc549d1e9f/community/dlib/APKBUILD
@davisking do you have an idea on how to proceed?

Can you pull the latest dlib and run again?  I made the unit tests not
print all those warnings about the DNN loss not liking the exact training
data.  So the actual failures will be visible again.
On Wed, Dec 16, 2020 at 4:16 PM Adriaan Groenenboom <
<EMAIL_ADDRESS>wrote:

I rebuilt with internal BLAS and the good news is: no segfaults anymore 🎉
However, some tests still fail. Less than before it seems, just one or two
per platform. Except for x86, which has 7 failing tests.
Interestingly enough, now only x86_64 builds successfully, while the other
platforms fail.
Link to build logs on all platforms:
https://gitlab.alpinelinux.org/agboom/aports/-/pipelines/64794
Link to new APKBUILD:
https://gitlab.alpinelinux.org/alpine/aports/-/blob/309fec5d61a86380ac2a43790d1843bc549d1e9f/community/dlib/APKBUILD
@davisking https://github.com/davisking do you have an idea on how to
proceed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/davisking/dlib/issues/2257#issuecomment-747033061,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPYFR7U342Z2OLXRUEPFBTSVEPSXANCNFSM4UVQTUKA
.

Sorry for my delayed question. I've tried to pull the latest Dlib by downloading the latest commit as archive, but the build fails because it cannot find a CMakeLists.txt in the directory. That wasn't a problem in the archive attached to the release, and I cannot find a difference between the two archives (CMakeLists.txt exists in both). I'm not sure what could cause this.
Relevant logs:
>>> dlib: Fetching dlib-19.20.tar.gz::https://github.com/davisking/dlib/archive/0fede57ed7ef756e98124be5743097f7321edd53.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   156  100   156    0     0    776      0 --:--:-- --:--:-- --:--:--   776
100 10.1M    0 10.1M    0     0  6875k      0 --:--:--  0:00:01 --:--:-- 10.3M
>>> dlib: Fetching dlib-19.20.tar.gz::https://github.com/davisking/dlib/archive/0fede57ed7ef756e98124be5743097f7321edd53.tar.gz
>>> dlib: Checking sha512sums...
dlib-19.20.tar.gz: OK
>>> dlib: Unpacking /var/cache/distfiles/dlib-19.20.tar.gz...
CMake Error: The source directory "/builds/agboom/aports/community/dlib/src" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
>>> ERROR: dlib: build failed

(it says dlib-19.20.tar.gz, but that's just a rename of the archive so  that the rest of the build script should work)
Build script can be found here: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/7177/diffs
The rest of the build log can be found here: https://gitlab.alpinelinux.org/agboom/aports/-/jobs/274401/raw

Sorry for my delayed question. I've tried to pull the latest Dlib by downloading the latest commit as archive, but the build fails because it cannot find a CMakeLists.txt in the directory. That wasn't a problem in the archive attached to the release, and I cannot find a difference between the two archives (CMakeLists.txt exists in both). I'm not sure what could cause this.
Relevant logs:
>>> dlib: Fetching dlib-19.20.tar.gz::https://github.com/davisking/dlib/archive/0fede57ed7ef756e98124be5743097f7321edd53.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   156  100   156    0     0    776      0 --:--:-- --:--:-- --:--:--   776
100 10.1M    0 10.1M    0     0  6875k      0 --:--:--  0:00:01 --:--:-- 10.3M
>>> dlib: Fetching dlib-19.20.tar.gz::https://github.com/davisking/dlib/archive/0fede57ed7ef756e98124be5743097f7321edd53.tar.gz
>>> dlib: Checking sha512sums...
dlib-19.20.tar.gz: OK
>>> dlib: Unpacking /var/cache/distfiles/dlib-19.20.tar.gz...
CMake Error: The source directory "/builds/agboom/aports/community/dlib/src" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
>>> ERROR: dlib: build failed

(it says dlib-19.20.tar.gz, but that's just a rename of the archive so  that the rest of the build script should work)
Build script can be found here: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/7177/diffs
The rest of the build log can be found here: https://gitlab.alpinelinux.org/agboom/aports/-/jobs/274401/raw


Download deobfuscated, file directly with a button

Its would be a good idea to make after deobfuscated, a button to download the file

That's being worked on in #79

That's being worked on in #79

Is this the web version or why i can't see it?

You mean the screenshot? idk

You mean the screenshot? idk

Allright 😂


Could not use TPU provided by Google Collab with custom training

I try to use TPU provided by Google Collab with custom training.
ANN-architecture - Transformer, with batch_size=128. I tested with GPU and all works fine. I wanted to speed up process and use larger batch. I modified code for TPU  but with TPU i got "Your session crashed for an unknown reason". I cant get it how to catch errors and etc.
Can you help me cause I cant train ANN with TPU.
Tensorflow version: 2.1.0 (also i used "%tensorflow_version 2.x" in collab notebook)
Warnings from logs:

2020-03-16 16:22:04.297929: W tensorflow/core/framework/cpu_allocator_impl.cc:81] Allocation of 780573800 exceeds 10% of system memory.

2020-03-16 16:22:03.324150: E tensorflow/stream_executor/cuda/cuda_driver.cc:351] failed call to cuInit: CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected

Preprocessing code
def _read_and_batch_from_files(input_arr, target_arr, shuffle=True, shuffle_val=20):

  dataset = tf.data.Dataset.from_tensor_slices((input_arr, target_arr))
  if shuffle:
    dataset = dataset.shuffle(buffer_size=6000, seed=shuffle_val,
                              reshuffle_each_iteration=True)
  else:
    dataset = dataset.batch(base_model_conf_obj.batch_size)
  dataset = dataset.repeat()
  return dataset

input_arr_test = np.load('/content/gdrive/My Drive/for_ds/x_test_tok.npy', allow_pickle=True)
target_arr_test = np.load('/content/gdrive/My Drive/for_ds/y_test_tok.npy', allow_pickle=True)
# i used this just for test before use init training/test files
train_dataset =  _read_and_batch_from_files(input_arr_test, target_arr_test,
                                            shuffle=True, shuffle_val=20)

Initialize TPU-strategy
class SingleDeviceStrategy(object):
  def __enter__(self, *args, **kwargs):
    pass

  def __exit__(self, *args, **kwargs):
    pass

  def scope(self):
    return self

  def experimental_distribute_dataset(self, dataset):
    return dataset

  def experimental_run_v2(self, func, args, kwargs):
    return func(*args, **kwargs)

  def reduce(self, reduction_type, distributed_data, axis):  # pylint: disable=unused-argument
    return distributed_data

def connect_to_tpu(tpu=None):
  if tpu:
    cluster_resolver = tf.distribute.cluster_resolver.TPUClusterResolver(tpu)
    tf.config.experimental_connect_to_host(cluster_resolver.get_master())
    tf.tpu.experimental.initialize_tpu_system(cluster_resolver)
    strategy = tf.distribute.experimental.TPUStrategy(cluster_resolver)
    return strategy, "/task:1" if os.environ.get("COLAB_TPU_ADDR") else "/job:worker"
  return SingleDeviceStrategy(), ""

Training procedure
worker_tpu = 'grpc://' + os.environ['COLAB_TPU_ADDR']
d_strat, device = connect_to_tpu(worker_tpu)
with d_strat.scope():
  dataset_iter = iter(d_strat.experimental_distribute_dataset(train_dataset))
  for epoch in range(starting_epoch, num_epochs):
    start = time.time()
    inp, tar = next(dataset_iter)
    def tpu_step(inp, tar):
      tar_inp = tar[:, :-1]
      tar_real = tar[:, 1:]
      enc_padding_mask, combined_mask, dec_padding_mask = create_masks(inp, tar_inp)
      with tf.GradientTape() as tape:
        predictions, _ = transformer(inp, tar_inp,
                                        True,
                                        enc_padding_mask,
                                        combined_mask,
                                        dec_padding_mask)
        loss = loss_function(tar_real, predictions)
        loss_ce = loss * (1.0 / base_model_conf.batch_size)
      variables = transformer.trainable_variables
      gradients = tape.gradient(loss_ce, variables)
      gradients = [(tf.clip_by_value(grad, -1.0, 1.0))
                        for grad in gradients]
      train_loss.update_state(loss_ce)
      train_op = optimizer.apply_gradients(zip(gradients, variables))
      with tf.control_dependencies([train_op]):
        return tf.cast(optimizer.iterations, tf.float32)

    @tf.function
    def train_step(inp, tar):
      distributed_metric = d_strat.experimental_run_v2(tpu_step, args=[inp, tar])
      step = d_strat.reduce(tf.distribute.ReduceOp.MEAN, distributed_metric, axis=None)
      return step

    step = tf.cast(train_step(inp, tar), tf.int32)
    train_loss.reset_states()
    train_loss_res = train_loss.result().numpy()
    print('Epoch {} Loss {:.4f}'.format(epoch + 1, train_loss_res,))
    print('Time taken for train 1 epoch: {} secs\n'.format(time.time() - start))
    ckpt_save_path = ckpt_manager.save()
    print('Saving checkpoint for epoch {} at {}'.format(epoch + 1, ckpt_save_path))
    print('Time taken for test 1 epoch: {} secs\n'.format(time.time() - start))

@pikaliov
i have tried to replicate the code shared by you,please find the gist here.
please note we cannot replicate the issue unless all dependencies are shared, along with the cuda version.
as per the error faced, could you please try CUDA_VISIBLE_DEVICES=0
as per error there are many similar issues already there,can you check if this helps link

@pikaliov
please update as per above comment

@pikaliov
Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Documentation: Use Monaco in Sandpack

Introduce a new guide into this page describing how to integrate Monaco editor in place of the CodeMirror. There is already a sandbox already properly working (here), but it would be important to describe how it has been achieved.
There is currently no "official" format for writing guides, so there is room for improvements and suggestions.

Hey @betomoedano I responded to you on Discord, for any further questions feel free to DM there.


Emit itemChanged on empty item

I'm trying to process the value selected using keyboard arrows. In the latest beta version, the plugin is emitting the itemChanged event (line 430 below).
The problematic scenario is:

Write something into the input field
Press the down key and select the first suggested option
Press the up key and revert the suggestion

Unfortunately, there is currently no event emitted in the third step. Shouldn't the component emit an empty itemChanged event?
The relevant code:
https://github.com/darrenjennings/vue-autosuggest/blob/eddb82d22437a61df40689f87625047edea71aab/src/Autosuggest.vue#L425-L438

@jkostolansky thanks for the issue, you discovered a hidden feature of the latest beta 😄
Might be time to make it stable/documented. I will add it, and make sure it's emitted even when it's empty. I will also change it to item-changed.

Thank you very much @darrenjennings 👍 I'm looking forward to the final release 🙂


Reopen #72 #76

#72 #76
# this is what I did afaik
git checkout main
git reset upstream main
git push -f
git checkout -b revert-to-beta
git merge feat-instantiate
git merge api-change-for-sendt
git commit -m "bump major"

Also check if you can reproduce the error in #82's description on this PR's branch


Store source cloud pulled mariadb data in env file

Allow resuming/starting test cases from the tasks like 'Verify MariaDB data imported', or 'Adopted Nova FFU post-checks' without loosing the facts for pulled source cloud data, which then is used for post-adoption verifications for MariaDB and Nova.
Allow using the source cloud data from env vars locally in each chapter, without carrying it over from another chapters. That is agreed aproach for documentation.  Achieve that by storing it in an env file, which can be sourced to get prepared values afterwards (those cannot be re-fetched again, after stopping the source cloud services).

please fix the conflict


Further removal of stale BlockwiseIO code

#7048 Reverted a recent attempt to implement read_parquet, read_csv, read_orc, and array creation as Blockwise layers.  This PR goes a bit further and removes the stale BlockwiseIO code that is no longer being used.  It will be easier to review the replacement with the "old"/"bad" code completely removed :)
My mistake for not removing this in the original reversion (git-related mix-up on my part).

@jsignell -  This PR includes changes that I thought were already included in #7048 . The BlockwiseIO code that is still in the master branch is not actually used anywhere, so it is not critical to get this in before the release.  However, it would be nice to remove the stale code as soon as we can (to confusion).  Appologies for not getting these changes in before!

@jsignell -  This PR includes changes that I thought were already included in #7048 . The BlockwiseIO code that is still in the master branch is not actually used anywhere, so it is not critical to get this in before the release.  However, it would be nice to remove the stale code as soon as we can (to confusion).  Appologies for not getting these changes in before!

I am retriggering the tests and then plan to merge

I am retriggering the tests and then plan to merge

FYI there is still one reference to BlockwiseIO in a docstring in blockwise.py.

FYI there is still one reference to BlockwiseIO in a docstring in blockwise.py.

FYI there is still one reference to BlockwiseIO in a docstring in blockwise.py.

Oops - Thanks for reporting that!

FYI there is still one reference to BlockwiseIO in a docstring in blockwise.py.

Oops - Thanks for reporting that!


Wheeler Kiladas

Revamp CD's legacy codes and use them for PMP metrics.

@doutriaux1 @sperber1 Had a powwow with KS and we agree this needs to be made a high priority... but we need CD help to get old codes working...

@doutriaux1  PG started branch 479_pjg_wheelerkaladis ... all CD legacy codes and test data are in there.

@gleckler1 @doutriaux1 could you please show me how this work, when you have time?

@lee1043 I can show you tomorrow, in the mean time look in the test directory, it's a bare bones example.

@gleckler1 this might be useful to get wavenumber frequency power spectrum for the MJO metrics. @doutriaux1 would you show me how the example work? I made few change in the code to make it work in Python 3 environment.

@lee1043 where did you get that code from? WK is already ported to py3 and has it's own pkg "wk" please use it. conda install -c cdat/label/nightly -c conda-forge wk

@lee1043 look at the tests directory that's tests everything.

definitely!

Is the test still valid with the new conda-installed wk?

which test? Look at the test in the wk repo.

Just found that there was a separated repo, https://github.com/CDAT/wk. Thanks, I will start from there.


Making team members public ?

Hey there !
I didn't realise the jupyter-server was in it's own org now ! Congrats !
Two things:

I realised when visiting https://github.com/jupyter-server, that only two person have their status as part of the team public, I know it's visible on the team compas, but maybe you want to make it public there as well.

And this is more for my own information, any reason for another org, and not using github teams ? I'm sure you discussed it and I was wondering if you have notes. As part of the security work, I realised it's much more painful to work across orgs than across teams.

Thanks !

Thanks, @Carreau!

I realised when visiting https://github.com/jupyter-server, that only two person have their status as part of the team public, I know it's visible on the team compas, but maybe you want to make it public there as well.

Thanks for mentioning this! I think each team member has to configure this themselves, right? I believe the default is set to private when inviting a team member. I'll mention this during the Jupyter Server meeting to ensure that more people set their membership to public.

And this is more for my own information, any reason for another org, and not using github teams ? I'm sure you discussed it and I was wondering if you have notes.

Good question.
I think the Jupyter Server team has outgrown the Github team model. Here is a couple of reasons I see:

We were starting to collect more repositories that fall under this team's responsibility and governance. Having those in own own separate org make this demarcation more clear and cleaner to manage.
Creating new (experimental) repos under the Github "Jupyter" namespace is questionable—it isn't clear if this action needs steering council approval. This has been brought up a few times in our team's history. The "Jupyter" Github org seems to be a higher ranked namespace in many people's minds.

While we could use Github Teams and blend ourselves into the Jupyter Github Org, it seemed to present a lot more friction than creating a separate org where we could operate more autonomously (of course, still under the broader Jupyter governance model). In the end, operating in a separate org made things more lightweight for this team's needs.

As part of the security work, I realised it's much more painful to work across orgs than across teams.

I'd love to brainstorm ways we could alleviate this pain in a multi-org model. I think it's the job of the Software Steering Council representative for each subproject (in the new governance model) to relay things like security issues back to their team.

There hasn't been any further activity here, so closing as finished/stale.


Add support for the MINIDUMP_HANDLE_DATA_STREAM stream

This covers part of issue #324

Tests are missing, I'll add them next week

I've manually tested this on Windows-generated minidumps that had the stream populated

@Gankra I've tested this with actual minidumps and everything seems to be working fine, but it seems like I messed up something in minidump-synth. Somehow the test fail with the value of handle being returned in the wrong endianness, so instead of 0x000000000000007b I get 0x7b00000000000000. I can't figure out what I'm doing wrong though.