Week 1: Network Configuration (Re) Routing

Set up and configure two compute nodes, one as a head node and the other as a compute node, to begin establishing the foundation of the cloud infrastructure.

 For any project related communication, please write a comment under the issue that you are working on e.g. if you have a problem with a task in week 1, you would write a comment in the issue under week 1 and similar for all other weeks.
Please @ me when you need me to attend to something so that I can get a notification and I will do the same.
Please make sure that everybody in your team and the mentor has accepted the git invite and are added to the project.
Good Luck


1.1.0

Added support for msngr.drop(message, handler) / msngr.drop(topic, category, dataType, handler) to allow individual handlers to be targeted versus a scorch-the-Earth removal as before.
Added more code coverage for accidental omissions.
Added multiple utility methods; is() does single checking and as() will check all arguments to ensure same type. The odd man out is the addition of msngr.utils.exist() and exists(); exist for single and exists for multiple.
Dev dependency updates
Added unit tests to run against minified file to ensure good minfication.

This also fixes #24


Enhancement Support transaction for benchmarks loading

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Warn about Partial in union where is another object

Because TypeScript does not have exact types, suddenly the result of such a union can accept any object, which is pretty tricky.

Please respect the issue template for bug reports and for feature requests.


Add a "hint" to the offset manifests about what minimum version the symbol was added

Originally posted by @MrAlias in https://github.com/open-telemetry/opentelemetry-go-instrumentation/issues/740#issuecomment-2079705634

@MrAlias Can we close this after #809?


Reverse proxy

I am trying to use this server behind the reverse proxy with custom subpath. Is it possible to set up information about it to bot? Currently I am getting the next answer from Telegram system due to an incorrect subpath:
{"ok":false,"error_code":404,"description":"Not Found"}

You need to rewrite the path at the reverse proxy level. But it is better to place on a separate domain / subdomain.


Macos rebranding

I need to finish the MacOS side of the CI/CD and the naming for launching the templates, etc etc are needed to be done a specific way so now that i found this need to modify it.
Can peeps help look it over?

Looks good, but this will anyway build a .universal file. I wonder how godot does when exporting a build, as they have a .app file in the end. The .app file opens when double clicking it, while the .universal file you need to run from terminal to start it.


[DOC] Inconsistent double tick quotes in docstrings

Describe the issue linked to the documentation
Single ticks render as italics while double ticks render as code in the api docs, e.g. int v.s. int. Various methods use this inconsistently, example from the HIVECOTE 2.0 docs below:
Docstring for random_state uses single ticks (italics) for all references to code, i.e. int, RandomState, and None.

Docstring  for n_jobs uses double ticks for -1 to represent it referring to code.

Suggest a potential alternative/fix
Select preferred approach out of single and double ticks for referring to code in docstrings and apply consistently throughout aeon.

I think double ticks is preferable


Rotate animation doesn't work

Rotate animation doesn't work when I save the frame with object rotated, I need to manually edit the rotation values in the json

Thanks man for reporting this. I've made quick fix that should make it to work in Sketch 3.8. This was because they have changed how rotation values is used in Sketch after 3.8 version.


to function can be applied to strings as well

Add "to" for Strings.

closing due to age but handling via https://www.mulesoft.org/jira/browse/DOCS-10747

As DOCS-10747 is not public please be so kind to give a summary here.

@dukesphere

Sure, the Jira points to your suggested example. We will assess it for addition to the docs.

Similar example is handled via https://github.com/mulesoft/data-weave/pull/1261/files


[4.3] Added validator element to pack element in DTD

According to Pack.java, validators are already supported. The DTD does not reflect that fact. This is simple fix of the installation DTD.

IzPack project » izpack #716 SUCCESS
This pull request looks good
(what's this?)

Thank you.


Add a Rust CLI

r? @PaulGrandperrin

As a next step we should add a way to easily collect the results of the fuzzers in a convenient way.

Oh: We could rename the run subcommands a bit (mainly "run" to "target") and get rid of the -- in the docs (cargo supports this):
$ cargo run target
$ cargo run continuously
$ cargo run list-targets

I can't really review the structopt DSL as I have no experience with it but from a user perspective I think it works great!
I think the only feature "lost in translation" is the ability to put weights on each targets, but it can be done later.
You can merge as soon as you want, I'd like to start doing something about the "compile all targets at one" problem.

Either of you: Feel free to merge, we can easily add more stuff in follow up PRs.

I think the only feature "lost in translation" is the ability to put weights on each targets, but it can be done later.

Ah yes, I explicitly skipped this feature for now. I thought I had commented on that in a commit message, but it seems I forgot. Sorry about that.
What was you main goal with that? To make sure expensive fuzzers get some more time to get through a useful number of iterations?

I like the fact that now this list is automatically extracted from the code

It's currently done in quite a hack-y way (regex), and I'm not sure how best to add a multiplier there.
By the way, I was surprised to see there was no timeout to stop after ≥x seconds of no new branch found, by the way.


Test the time taken for jiva controller during reschedule

What is it all about ?

It is required to learn the time taken for jiva controller during reschedule
The lesser the value (i.e. lesser than 30 secs) the better handling of HA

How ?


CB-10486 renaming host groups

This renames master to main and gateway to admin for SDX HA in 7.2.7+.
See detailed description in the commit message.

@orngejaket can you please add this new group to the {cloud}-vm-recommendation.json?

@orngejaket can you please add this new group to the {cloud}-vm-recommendation.json?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@orngejaket do we still need this?


Minor update DG

Codecov Report

Merging #91 (3aa9c2e) into master (8493eb4) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #91   +/-   ##
=========================================
  Coverage     72.02%   72.02%
  Complexity      581      581
=========================================
  Files            97       97
  Lines          1902     1902
  Branches        202      202
=========================================
  Hits           1370     1370
  Misses          447      447
  Partials         85       85

Impacted Files
Coverage Δ

.../seedu/address/model/person/GradeProgressList.java
70.37% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


<EMAIL_ADDRESS>

No matching version found for<EMAIL_ADDRESS>

Hi @PandaPeter, seams that something with your npm isn't right. Here all is fine.
$ npm info caldate

<EMAIL_ADDRESS>| ISC | deps: 1 | versions: 5
calendar date for date-holidays
https://github.com/commenthol/caldate
...

npm i caldate
+<EMAIL_ADDRESS>added 3 packages from 7 contributors and audited 3 packages in 2.707s
found 0 vulnerabilities


Exceptions for better performance

A comparison of the monadic call chain interface from std::optional in C++23 and using exceptions to handle error cases instead.

I would upvote this 10x if I could. I have long theorized, but never had the chance/taken the time to prove, that using exceptions to report uncommon conditions can be measurably faster than manually checking and propagating error return values, especially with a deep-ish call stack.

could you add std::expected to the comparison?

could you add std::expected to the comparison?

Good idea. I've observed that it's shockingly easy to use std::expected inefficiently.
cough implicit conversions cough


Kafka fails due to inability to load snappy library

docker exec openbmp_kafka tail -f /var/log/kafka.log
....
java.lang.UnsatisfiedLinkError: /tmp/snappy-1.1.2-5395f0cd-f2e4-4d77-ae88-69b6bb215bae-libsnappyjava.so: Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /tmp/snappy-1.1.2-5395f0cd-f2e4-4d77-ae88-69b6bb215bae-libsnappyjava.so)
This error is then seen repeatedly:
2017-05-19 22:44:23,552] ERROR [Replica Manager on Broker 0]: Error processing append operation on partition openbmp.bmp_raw-1 (kafka.server.ReplicaManager)
java.lang.NoClassDefFoundError: Could not initialize class org.xerial.snappy.Snappy

I'll be building the AIO which has an upgraded kafka version, which should fix this issue.  I'll send a note when that container has been published.

Hi @TimEvens, while it works on the aio container, it looks like the problem is still present on the latest kafka container - the issue is caused by missing glibc dependency on the base alpine used on the container. I've been able to workaround the issue by changing the base container image to frolvlad/alpine-glibc.

Have you fixed this issue?

@xubo245 , yes as of today.  Kafka has been upgraded to 1.0.1 as well.

ok, my problem also was fixed


[DML] Scala/Java API for OPTIMIZE

This tracks the ongoing work and discussions for building the Scala/Java APIs for optimizing the data layout of Delta tables by coalescing small files into larger files.

At this point, there are no plans to open-source the OPTIMIZE command, as the actual implementation is pretty deeply tied to other functionality that is only present in Databricks Runtime.
That said, it is really easy to coalesce small files into bigger, more efficient ones as long as you have the power of ACID transaction. The real hard part of this operation is making sure you do not corrupt the table while updating it in-place, and this comes out of the box with Delta!
Example:
val table = "..."
val partition = "year = 2019"
val numFiles = 10

spark.read
  .format("delta")
  .load(table)
  .where(partition)
  .repartition(numFiles)
  .write
  .format("delta")
  .mode("overwrite")
  .option("replaceWhere", partition)
  .save(table)

Does that imply that if I am using the delta table as a stream input, the rewritten files are not taken into consideration by the stream job as the original file where already processed ?

@btbbass that is an excellent point and I am missing something in that example. Thanks for pointing that out!
We need to expose the ability for writes to be marked as "rearranging data only" in order to avoid breaking streams that are querying this data. This is the API that OPTIMIZE uses internally and we should expose that in OSS too.
I opened #146 to track, should be pretty easy to implement as all the protocol support is already there.

You need to add single quotes to val partition = "year = '2019'" to make Michael's answer work (for anyone else silly enough to get caught on this).
Thanks for the great answer @marmbrus and happy Delta makes this so easy!


Update configuration: add a note about updating SSH keys from user profile

Author Name: EOLE Team (EOLE Team)
Original Redmine Issue: 4741, https://dev.opennebula.org/issues/4741
Original Date: 2016-08-24
Original Assignee: Javi Fontan

Hello,
A user updated its SSH keys in his profile and wonder how to get the SSH key updated for his VMs automatically.
I found by trying:

that it can not be automatic
the easiest way is to

go in @Update Configuration > Context@
make sure @Add SSH contextualization@ is enabled
empty the @SSH public key@ text area
With this, OpenNebula will reimport the user SSH keys in the VM context.
I think this deserve a note in the documentation about updating the configuration as this behaviour may not be an evidence for everybody
Regards.

Original Redmine Comment
Author Name: Ruben S. Montero (@rsmontero)
Original Date: 2016-08-29T12:13:23Z

Agree THANKS!


Discord Webhook integration

What part of Adonis is this related to?
Other
What are you suggesting?
Discord Webhook integration for warns, bans, etc. Im thinking of something like this:

I can update the current mockup if you want

Already exists https://github.com/Epix-Incorporated/Adonis-Plugins/blob/master/Server/Server-DiscordWebhookLogs.lua

oh didnt see that. Thank you!


overload method startforeground for API under 29

Pull Request Template
Types of changes
What types of changes does your code introduce to Woosmap Geofencing?
Put an x in the boxes that apply

[X] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Before you submit a pull request, please make sure you have to following:

[X] I've read contributing guidelines
[X] My code contain tests relevant for the problem I'm solving
[X] I have added tests that prove my fix is effective or that my feature works
[X] I have added necessary documentation (if appropriate)

https://github.com/woosmap/woosmap-geofencing-android-sdk/issues/31


Filter posts pulled

With the recent Tumblr nonsense pushing artists to twitter it would be great if this bot could be selective about what type of post it pulled. Such as only tweets that had media etc.

Yeah that should be easy enough to add as a filter. It's possible to tell whether the post has media attachments, so I could filter based on that.

Theoretically, you should be able to add :media-only? true under :mastodon section to filter posts containing media. Let me know if that looks good.


Style/TrailingUnderscoreVariable cop leaves an unclosed parenthesis

Style/TrailingUnderscoreVariable cop wrongly fixes
(foo, _) = [1, 2, 3]

into
(foo, = [1, 2, 3]

and breaks the syntax.
Maybe the problem is not with this specific cop and the parenthesis should be removed first by another cop.
Otherwise, it should not remove the closing parenthesis.

Expected behavior
It should replace to foo, = [1, 2, 3] or (foo, ) = [1, 2, 3]
Actual behavior
It leaves an unclosed parenthesis and breaks the syntax.
Steps to reproduce the problem
# test.rb
(foo, _) = [1, 2, 3]
puts foo

rubocop -a test.rb

RuboCop version
$ rubocop -V
0.49.1 (using Parser <IP_ADDRESS>, running on ruby 2.3.3 x86_64-darwin15)

Maybe the problem is not with this specific cop and the parenthesis should be removed first by another cop.

There might be room for another cop to remove the parentheses, but we can't rely on that being enabled, so you're correct in saying this cop should not break the code. 🙂


Shared global fallback context

I really want to understand this and get the scenario right. It seems bad to rush something in without understanding a use case for it, and it's just as bad to prevent real-world apps from using AmbientTasks out of some kind of idealism. Instead of the strategy of dragging my feet and hoping things magically solve themselves, I'm proposing a compromise. See the final question in the 'Outstanding questions' section.
Goals
The best outcome from my point of view would be to play around with an example app until we come to a full understanding of the problem space.
The next best outcome—with the same disclaimer—is to add a back door with the guidance that we don't fully understand why it exists (until this changes) and that it should only be used as a last resort
The worst outcome is to delay this many more weeks. Nearly the worst outcome is to block the folks that need this from being able to use the NuGet package.
Problem description
/cc @YairHalberstadt who found it necessary in their project to add the following code (https://gitter.im/dotnet/csharplang?at=5d039b76e527d95addd12695):

private static AmbientTaskContext _globalContext = new AmbientTaskContext(null);
private static readonly AsyncLocal<AmbientTaskContext> _localContext = new AsyncLocal<AmbientTaskContext>();

private static AmbientTaskContext CurrentContext => _localContext.Value ?? (_localContext.Value = _globalContext);

/// <summary>
/// <para>
/// Replaces the current async-local scope with a new scope which has its own exception handler and isolated set
/// of tracked tasks.
/// </para>
/// <para>If <paramref name="exceptionHandler"/> is <see langword="null"/>, exceptions will be left uncaught. In
/// the case of tracked <see cref="Task"/> objects, the exception will be rethrown on the synchronization
/// context which began tracking it.
/// </para>
/// </summary>
public static void BeginContext(Action<Exception> exceptionHandler = null)
{
	_localContext.Value = new AmbientTaskContext(exceptionHandler);
}

/// <summary>
/// <para>
/// Sets a global context which will be used by any tasks which do not have a scope.
/// </para>
/// <para>If <paramref name="exceptionHandler"/> is <see langword="null"/>, exceptions will be left uncaught. In
/// the case of tracked <see cref="Task"/> objects, the exception will be rethrown on the synchronization
/// context which began tracking it.
/// </para>
/// </summary>
public static void SetGlobalContext(Action<Exception> exceptionHandler = null)
{
	_globalContext = new AmbientTaskContext(exceptionHandler);
}

Reasons to avoid this
Subverting the purpose of BeginContext
Using a single shared global context takes less thought than thinking about what contexts mean. I'm afraid people will use this when AmbientTasks.BeginContext is actually possible, so I'll make the XML documentation obnoxious.
Shared global locks
There is a possibility of throughput issues due to context-wide locks in AmbientTask methods. If everything is using the same global context, there are now global locks between all AmbientTask calls.
Could these locks be removed? Probably yes, if we have the time and expertise to do something lock-free.
Outstanding questions

Has the need for this disappeared along with the five significant fixes and changes that I implemented before publishing the MyGet package? Maybe the whole thing was/is due to a bug.

If not, can the use case be clarified? Why is AmbientTasks.Add/Post being called from a place where there was no execution context flow from the AmbientTasks.BeginContext call?

Was the AmbientTasks.BeginContext call too late in the program?
Is the program using Unsafe methods to opt out of flowing ExecutionContext? Why? (Using AmbientTasks across this boundary seems very bad.)
Is the use case only for AmbientTasks.Add/Post, or does AmbientTasks.WaitAllAsync have this same need? I'd like to make WaitAllAsync throw.
Can I see an example that I can run? ❤

Is it acceptable to add this API as AmbientTasks.Experimental.SetGlobalFallbackHandler with warnings in the XML docs?

I added a proposed API in the branch https://github.com/Techsola/AmbientTasks/compare/backdoor and published the built package to the MyGet feed so that you can try it out and see if it does what is needed:
https://www.myget.org/feed/ambienttasks/package/nuget/AmbientTasks/0.1.0-60.backdoor
If we aren't able to gather more insight about the use case, I'll probably go ahead and pull request some version of this into the master branch so that we can release to the nuget.org community feed.

Closing due to lack of interest.


Add CLOSED to issue states for non-open tickets

ok, what's the benefit? what does it fix?

I think forgot some cases of closed issues.
Eg https://progress.opensuse.org/issues/200 wouldn't be detected as
closed without this patch.

ah, it's about redmine. I thought only bugzilla. makes sense.


proposal: Bags

This issue has been discussed before: #3462 etc. This proposal is still a bit rough around the edges, but it would be great to get some ideas/thoughts/corrections from others.
Here is my take on the first iteration of such a feature. There are natural extensions of this feature that I will not go into detail about, but I will just briefly touch the most relevant ones to see if my model clashes.
So, given this simple dummy site:
├── _index.md
├── a-site-logo.jpg
└── blog
    ├── _index.md
    ├── blog-content.md
    ├── blog-logo.jpg
    ├── categories
    │   └── cats
    │       └── _index.md
    └── funny-cats
        ├── anothercat.jpg
        ├── cat-article.md
        ├── cat.jpg
        ├── even-more-content.md
        └── more-content.md

The branch pages (i.e. pages with children, home page, section lists, taxonomy lists, taxonomy terms) are by definition bags.
The leaf pages (i.e. regular content pages) can be configured to be a bag by setting bag=true in front matter. They will then become branch pages with potential children.
We may need a special bag.toml configuration file at some point, but let's leave that out for now.
I know many currently use the index.md workaround for bags, so we should probably also make a special case to make these into bags.

So, given the example above, cat-article.md is configured to be a bag (bag=true in front matter).
Thinking in Go terms, we add a new Resource type (a Page is a Resource):
interface Resource {
   Permalink() string
   RelPermalink() string
}

$funnyCatsPage.Pages => [even-more-content.md, more-content.md]
$funnyCatsPage.Resources => [even-more-content.md, more-content.md, cat.jpg, another-cat.jpg]
$funnyCatsPage.Resources.ByType "image" => [cat.jpg, another-cat.jpg]
The sub-content-pages will not have Permalink, i.e they will not be rendered to disk on its own, but will typically be used to compose the "bag page".

A Page is a Resource, but we will need others, one example would be Image, which would have some additional image related properties, such as Width and Height, but also methods to generate alternate versions of that image:
$cat := $funnyCatsPage.GetResource "image" "cat.jpg"
$scaled := $cat.Scale "1000x600"

<img src="{{ $scaled.Permalink }}" width={{ $scaled.Width }} height={{ $scaled.Height }}>

The API above is just an example. But I think this "processing only when needed" will scale better than, say, create 5 different version of every image, even if only a small fraction is in actual use.
NOTE: This proposal is about how the bags in Hugo should look like at its core -- it is not about details in a future image scaling APIs etc. The only way to get this done is to define a fairly narrow scope.
TODO: Permalinking, ...
Related

Galleries
Image cropping, resizing and compression, see #3207 etc.
Resource linking in markdown (with cropping, resizing etc.)
??

When I hear about a bundle, I cannot prevent me from thinking about extending the software or having a specific software distribution/flavor. IMHO, as it is the case in other projects, a bundle in itself would sound as Hugo extensions.

Why having a new term and not sticking with sections?

Because a Section would contain 0:* bundles. I'm not married to that term, but it cannot be Section, because that is already taken.

I like the approach of only producing scaled images when actually used. Very cool indeed.
A couple of additional points \ features I would like to see (which you may have already thought of, but thought I would mention anyway):
Being able to set a quality of image (0 - 100) on a per image basis, or global default setting.
Being able to set jpg to be progressive.
I don't know how you will be implementing the image processing, but gulp-imagemin appers to have some custom plugin options that allow for the points I mentioned https://github.com/imagemin/imagemin

@thewebmastercom I put a NOTICE in bold above; what you talk about is interesting, but is far outside of the scope of this issue.

Bundle does sound like some kind of extension/plugin for Hugo. Possible suggestion:

Collection
Packet / Pack

I like the sound of Collection.

I like the sound of Collection.

The sound is fine, but will be confused by Jekyll's collections: https://jekyllrb.com/docs/collections/
Pack sounds snappy, but what abut Bag? Even shorter.

Bag sounds great. It even describes itself perfectly. I like it!

I've thoughtfully read the posts above, but is bag predicated on the coupling of content files with image files?
In other words, if we don't store our cat images in the same folder as in which cat-article.md defines that folder to be a funnyCatsPage bag, then the images and other files are not part of the bag, right?
I can see the appeal of adding non-content files (like .jpg) to a taxonomy collection (what bag basically seems to be), but from my standpoint it also seems quite complicated to explain to new users.
And it also feels limiting that defining a bag does not seem possible if one separates images (in /static/) from content files (/content/) -- which is what we all do now.
(Don't mean to be negative, just hope to help a bit in this way.)

Not quite sure about bag LOL! It reminds of leather goods (obviously). I prefer pack but it's your call @bep
Other than that I really like this blueprint and how it opens up a whole new set of features to be developed in the future.

It's all about establishing community standards :stuck_out_tongue:
Plugin, Bundle, Package - each has their own well established meanings. Who knows, years from now, maybe there will be some project on GitHub looking for a name for their new feature and somebody would say, "We can't name this feature Bag! Hugo used this for a completely different thing!"
I've seen the term Pack being used here and there. But Bag! Nowhere :joy: Maybe it's a good thing :wink: @onedrawingperday

We already have Scratch, which is also a little bit funky, and Bag fits nicely into that.
@Jos512 I think most people are familiar with grouping related files in the same folder, and this is just the foundation. But I'm not building a Swiss Army knife until I know I really need it -- and it is still possible to use Hugo as is.

@bep scratch the bag! LMAO!!

But Bag! Nowhere

Hibernate (Java ORM library) uses Bag for one their collection types ...

@bep,
First of all, this would be another fantastic step forward for Hugo.  It's also another item on Steve's "Future of Hugo" brain dump.
Second, I suppose it doesn't really matter, but I like Bundle over Bag.  I think Steve called them Bundles.  The context here is "content."  It's a content bundle, not a software bundle.  "Bag" sounds like a bag of crap, which I hope my content is not. :wink:
Now, on to my main question:

└── blog
    └── funny-cats
        ├── anothercat.jpg
        ├── cat-article.md
        ├── cat.jpg
        ├── even-more-content.md
        └── more-content.md

Would the default URL for this be /blog/funny-cats/cat-article/ or /blog/funny-cats/. It's a little confusing to me either way.  It would normally be created as /blog/funny-cats/cat-article/, but it feels odd to have all of the extra files in a path on disk that doesn't match the path of the output.  However, creating /blog/funny-cats/ feels abnormal since the "bag" file is called cat-article.
Surprises and oddities create confusion, add to the cognitive load on the user, and make writing docs harder (and way more necessary).
Suggested Solution
Why not require the use of index.md to create a bag?
└── blog
    └── funny-cats
        ├── anothercat.jpg
        ├── index.md
        ├── cat.jpg
        ├── even-more-content.md
        └── more-content.md

If bag=false for index.md, we treat it as we do now and create three pages:

/blog/funny-cats/
/blog/funny-cats/even-more-content/
/blog/funny-cats/more-content/

If bag=true for index.md, we create only:

/blog/funny-cats/

Nothing about that feels surprising to me.

/blog/funny-cats/

Yes, however we do it, the "file slug" for the path will be the container, i.e. the folder, so it should in the URL department behave much like how the `/myarticle/index.md" works today.

As to bundles, I think we should reserve that for "something else" in the future, like "shortcode bundles", plugins, theme bundles, whatever.

With apologies for being dense: Do "bags" stand next to Sections, or are Sections inside of "bags." And/or why can't "bags" just be Sections?
I think the concept of sections and subsections and types gives one quite a bit of flexibility and I fear another concept will cause ongoing confusion for users.
And, for what it's worth, I think "collections" is a much more meaningful word and I don't think it matters what Jekyll uses.

A bag is a Page with some additional Resources. I think all of this would be easier if we just dropped the special name and just call it a Page.

I see, so it's an article. Your original proposal seems clearer now that you said that, because "bags" makes it seem like something else entirely.

pack = 👍
collection = 👍
article = 👍
bag = 👎
bundle = 👎
That said, pack: true is probably my favorite, since this is, from what I can tell, kind of the confluence between an article and list page with the assets packed along with it.

If bag=false for index.md...

Just for my own clarity @moorereason, do you mean _index.md? I only ask because your comments regarding cognitive load might apply to asking users to concomitantly balance the distinctions between index.md and _index.md...just a thought. So perhaps just _index.md with the pack: true front matter?

For what I've understood for now, I assume we may not really need such a term. At least it could be transparent for the end user.
What we want to do is add resources to a content, whatever it be a section or a leaf page. It would simply sound natural to me to add a collection of resources inside the front matter, just like this:
resources:
  - res/
  - images/   # directory relative to the current post's location
  - /my-journey-throught-scotland/
  - my-beautiful-landscape.jpg

Note that I have mixed absolute directories, relative ones, and direct links to files. This may be discussed.
But why do we need more than a resource name? IMHO it would simply sound more natural. In the end, the Bag, Bundle or whatever would be transparent if this is a name that is implemented in the code. And inside the code we could use something more descriptive, such as ContentResources.
Do I have I missed something?

What we want to do is add resources to a content, whatever it be a section or a leaf page. It would simply sound natural to me to add a collection of resources inside the front matter.

I like this approach. Also because it can be used to specify which files from /static/ belong to the bag (or what the name becomes). With that, people who like to put their static files in /content/ alongside the content file can do that (for the automatic generation of bag).
And people with 'legacy' websites made with Hugo don't have to restructure their content to use bags but can simply do so with the front matter. And with the imageConfig function we already have, Hugo can already read files on the system so it might probably not be that hard to implement.

Do I have I missed something?

Yes. This is kind of what we have today, but with a less formal definition.
Have a look at this commit:
https://github.com/bep/bepsays.com/commit/994d0fec8475d98458268bfadd51a67026087ab8#diff-e6986871ee8d4815fbc2b3a88f636658R9
This is me announcing a new Hugo release. This announcement/pack/bag/article contains 1 markdown file and 1 image. The image is used both in markdown and in the template (Twitter image).
So I do this:

I copy the image to a path in /static
I carefully insert the path in the front matter
I carefully insert the path in a image link in markdown

This is for one image, and I already hate it.
So, currently, what people do is this, inside /myarticle:
index.md
myimage.jpg

This solves some of the pain, but the URL to /myarticle/myimage.jpg will be broken if I (or the editor I send this article to), decides to move it to /my-cool-article.
So how do I avoid the two pains described above?
I create a naming convention where I can "bundle" content and images etc. together with as little work as possible, and let Hugo handle all the URLs for me.
The folder or Zip file analogy is easy to understand for most people.
And then you will notice above that I have said that this "naming convention" most likely will be followed up with a configuration extension (front matter, bag.toml) where one can manually define resources (external?).

OK, I see an even amount of want/do not want -- so I guess this isn't something I'm going to spend more time on. Maybe I'll revisit this in the future.

I accidentally voted for ‘Rucksacks’ (I didn’t examine the URLs closely enough, I didn’t see the animation and I thought it was a plain image), and there’s currently no way to undo a vote (tj/gh-polls#8).
@bep, any reason why Page isn’t on the list? You said previously about dropping the special name, “I think all of this would be easier if we just dropped the special name and just call it a Page.” Seems like that would be better than adding new terminology.

@neeklamy it was just a joke (and a test of the polls, see https://github.com/tj/gh-polls )... None of the options (other than the first one) make much sense...

Phew! You got me!
Are you not considering just naming them Page? Or does that not distinguish the idea enough? If not how about some modifier, not so catchy, for sure, but something like Self-contained Page?

Are you not considering just naming them Page?

Yes, I will not give them a name. It will be a characteristic of a Page.

it was just a joke

Just when I was getting attached to "briefcases."

Rucksacks would have been my favorite as a German :wink:

Nowvegian humor is underrated 😄

Thanks for taking this on, I intended to contribute myself but then I realized I have no capacity left to learn GO.

Hey gang,
What do you say about my now simplified definition of "how to identify a bundle":

A content folder is identified as a bundle if it contains either a _index.* or an index.* file.
For  index.* files (i.e. single content pages) type of bundles, the bundle will also include any sub folders (i.e. /mypost/images etc.).

We may add metadata in the future, and I'm just calling it bundle here to have a name to pin to the term.

I like it quite a lot. Simple and intuitive. Also, I think "bundle" is a pretty intuitive term, although used in other contexts for different purposes. Nothing wrong with a "Hugo bundle" meaning something very specific. Thanks, @bep!

For index.* files (i.e. single content pages) type of bundles, the bundle will also include any sub folders (i.e. /mypost/images etc.).

I'm not yet sold on the bundle including any sub-folders idea, mainly because it's not clear to me what happens to the sub-folders.  Does the parent bundle gobble up all of the sub-folders or can I continue to deal with the sub-folders individually if I want to?
For example, say I have a Products section on a site which includes sub-sections for Desktops & Servers.  And let's say I want to bundle resources within the content folder.
products
├── desktops
│   ├── index.md
│   ├── product-1.png
│   ├── product-2.png
│   └── quotes.md
├── feature.md
├── index.md
├── products-1.png
├── products-2.png
└── servers
    ├── index.md
    ├── product-1.png
    ├── product-2.png
    └── quotes.md

Let's assume that I want to build a shared template for the product sub-sections (and I give them a special "section" in their front matter).  When I'm building the sub-section template, I would expect to be able to use .Pages (as [quotes.md]) and .Resources (as [product-1.png, product-2.png, quotes.md]).

This seems a similar idea to TextBundle which already has some support among Markdown clients.

I really like the idea of a bundle. It has always been my intuition to keep text content and assets together. Thank you for working on this!
On a lot of websites I already use it like @bep described above with index.md or _index.md:
├── content/
    └── _index.md
    └── home-image.jpg
    └── about/
    │   └── _index.md
    └── blog/
        ├── _index.md
        ├── firstpost/
        │   └── index.md
        │   └── post-image-1.jpg
        └── secondpost/
            └── index.md
            └── post-image-2.jpg

This works fine. See also Structure B in this Discussion: Content Organization Best Practice.
@bep, you write:

This solves some of the pain, but the URL to /myarticle/myimage.jpg will be broken if I (or the editor I send this article to), decides to move it to /my-cool-article.

This has not been a probem for me (except for multilingual sites - see below). I use relative paths in my front matter and markdown like `. With this I can rename the folder and the images still work.
Multilingual Sites
The relative paths to images as described above break in multilingual sites!
I know my example gets a bit complicated since it is nested and multilingual content. But I would like to use it in this form for a larger tutorial collection with translations in more than ten languages (see live example here which is not migrated to Hugo yet).
├── content/
    └── _index.md
    └── home-image.jpg
    └── library/
        ├── _index.md
        ├── html-tutorial/
            └── _index.de.md
            └── _index.en.md
            └── tutorial-overview-de.jpg
            └── tutorial-overview-en.jpg
            └── part1/
            │   └── _index.de.md
            │   └── _index.en.md
            │   └── part1-image-de.jpg
            │   └── part1-image-en.jpg
            └── part2/
            │   └── _index.de.md
            │   └── _index.en.md

In this form the relative images do not work any more. Hugo adds a language prefix, e.g. /de/ for German as the root path. The German page for part1 will be in /de/library/html-tutorial/part1/index.html while the images are under the path without language prefix, for example /library/html-tutorial/part1/part1-image-de.jpg.
To consider for Bags/Bundles
Sorry for the long post. I just hope to add some thoughts that might need to be considered for the Bag/Bundle implementation:

They could help with bundling multilingual assets together with their text content (if done right!).
Handling nested content with a bundle seems tricky: include subfolder or not as mentioned by @moorereason above. I would consider every folder a separate bundle. This way we can have nested bundles as would be needed in my example above.
Another thing to consider is how bundles relate to assets stored in an external storage (necessary for large projects since you shouldn't have gigabytes of binaries in a Git repo). See Structure C in this discussion.
I think bundles/bags would be an awesome Hugo feature!

Hi, @all
Forgive my Lack of formatting this Mail, i am texting with shitty reception
on my old mobile.
All these posts talk about keeping pictures with hugo, so in most
deployment scenarios, in a git repo. I don't know but i am quite unhappy
with keeping large blobs in a git. Some Photos i take and want to publish
have around 5MB in file size.
I know there are imagemagick scripts for decreasing file size, but maybe it
could be possible to create some kind of subcommand into Hugo that can
compress images. I know that it is not easy, since deployment to a git Repo
and hugoing this Repo happens with almost no Hugo, just with git, but maybe
we can find a solution.
I just wanted to let you know that there are people like me who have large
(Image) blobs with Hugo, like this Directory Layout, but are wondering
about keeping These pictures (a Gallery has like 20x5MB) reasonably in a
git.
On Sun, Oct 8, 2017, 00:43 Marco Jakob<EMAIL_ADDRESS>wrote:

I really like the idea of a bundle. It has always been my intuition to
keep text content and assets together. Thank you for working on this!
On a lot of websites I already use it like @bep https://github.com/bep
described above with index.md or _index.md:
├── content/
└── _index.md
└── home-image.jpg
└── about/
│   └── _index.md
└── blog/
├── _index.md
├── firstpost/
│   └── index.md
│   └── post-image-1.jpg
└── secondpost/
└── index.md
└── post-image-2.jpg
This works fine. See also Structure B in this Discussion: Content
Organization Best Practice
https://discourse.gohugo.io/t/discussion-content-organization-best-practice/6360/3
.
@bep https://github.com/bep, you write:
This solves some of the pain, but the URL to /myarticle/myimage.jpg will
be broken if I (or the editor I send this article to), decides to move it
to /my-cool-article.
This has not been a probem for me (except for multilingual sites - see
below). I use relative paths in my front matter and markdown like `[image:
My Image] http://myimage.jpg. With this I can rename the folder and the
images still work.
Multilingual Sites
The relative paths to images as described above break in multilingual
sites!
I know my example gets a bit complicated since it is nested and
multilingual content. But I would like to use it in this form for a larger
tutorial collection with translations in more than ten languages (see live
example here http://code.makery.ch/library/javafx-8-tutorial/part1/
which is not migrated to Hugo yet).
├── content/
└── _index.md
└── home-image.jpg
└── library/
├── _index.md
├── html-tutorial/
└── _index.de.md
└── _index.en.md
└── tutorial-overview-de.jpg
└── tutorial-overview-en.jpg
└── part1/
│   └── _index.de.md
│   └── _index.en.md
│   └── part1-image-de.jpg
│   └── part1-image-en.jpg
└── part2/
│   └── _index.de.md
│   └── _index.en.md
In this form the relative images do not work any more. Hugo adds a
language prefix, e.g. /de/ for German as the root path. The German page
for part1 will be in /de/library/html-tutorial/part1/index.html while the
images are under the path without language prefix, for example
/library/html-tutorial/part1/part1-image-de.jpg.
To consider for Bags/Bundles
Sorry for the long post. I just hope to add some thoughts that might need
to be considered for the Bag/Bundle implementation:

They could help with bundling multilingual assets together with
their text content (if done right!).
Handling nested content with a bundle seems tricky: include
subfolder or not as mentioned by @moorereason
https://github.com/moorereason above
https://github.com/gohugoio/hugo/issues/3651#issuecomment-322300105.
I would consider every folder a separate bundle. This way we can have
nested bundles as would be needed in my example above.
Another thing to consider is how bundles relate to assets stored in
an external storage (necessary for large projects since you shouldn't have
gigabytes of binaries in a Git repo). See Structure C in this
discussion
https://discourse.gohugo.io/t/discussion-content-organization-best-practice/6360/9
.
I think bundles/bags would be an awesome Hugo feature!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gohugoio/hugo/issues/3651#issuecomment-334970587, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAqxIxPrlsFmpa_umYF68noZh5_CpIwFks5sp_52gaJpZM4OGNPQ
.

--
Before printing this email, think if it is really needed.

@simonszu Yes, handling large blobs is what I was referring to with this:

Another thing to consider is how bundles relate to assets stored in an external storage (necessary for large projects since you shouldn't have gigabytes of binaries in a Git repo). See Structure C in this discussion.

Let's leave the storage management to the users. In my opinion it's not HUGO mission to lay down restrictions in order to avoid GIT storage issues. I'd be surprised if it wasn't possible to remove history of the file and thus avoid taking up too much space due to versioning.
By the way, isn't the external storage supported already? Just just need to paste link to your images.

@simonszu I use Git LFS for versioning images along with my content.  Works great.  Supported by GitHub and GitLab.

Please move the discussions about your personal storage preferences to the forums.  It's just noise here.

I have move on with my bundles PR now ... For the curious:
A sample bundle page with both images and content files:
http://hugotest.bep.is/2017/11/bundle-1/
How it looks in the Hugo project:
https://github.com/bep/hugotest/commit/c513a2635eb593275d21b4325beee35baf858c3e
I have also decided to do the image "addon" for this: I.e. add width/height attributes + scaling.

Responding to Bep's comment from yesterday:
I appreciate all the work put into this, but I'm concerned about how we're going to document this. Placing the bundles into the content directory (/content/bundles/) seems to have a couple of disadvantages:

It changes the meaning of sections, which are now 'subdirectories of your content folder'. With the new behaviour there can also be a 'bundles' subdirectory, which may or may not count as a section.
It may affect the meaning of content types, which are now derived from their section folder (or when set explicitly in the front matter). A bundle is likely not going to be a content type, however.
It changes the meaning of the content directory, whose defining features include 'all content files that are processed by Hugo'. Now with the 'bundles' stored in /content/, the content folder also contains static assets (like images) that are not processed (like Hugo does with Markdown files).
Hugo believes we organise our content in a manner that reflects the rendered website (source). By placing bundles in the content directory, we seem to move away from that point. Instead, we'll need to use permalink settings in the configuration file to turn non-descriptive /content/bundles/bundle1/ paths into actual URLs.

I like the idea of bundles and have tremendous respect for the all the work Bep does. But I'm quite concerned with how we're going to explain bundles when they're put in the content directory.
I think the bundle behaviour would be easier to explain and comprehend if bundles get their own directory. That way we have three distinct content directories: /content/ for everything that Hugo renders, /static/ for our truly static files, and /bundles/ for our custom content bundles (a mixture of static content and content that Hugo renders).
A specific /bundles/ directory at the root level also makes sense if we look at how we already treat the /data/ folder. The files we store in /data/ are static files, but Hugo doesn't treat them as regular static files (in /static/). And so they have their own folder, to set them apart from the other files Hugo uses.
I'd argue that the same applies to bundles too. Bundles are primarily content files (with a bit of static files too), but they aren't treated by Hugo in the same way as regular content. (Especially when image resizing and scaling also happens in a bundle.) So perhaps they also deserve their own directory.
When we give bundles their own directory, the meaning of the content directory, what sections are, and how content types work (see previous points) remains unaffected by bundles.
And so I think bundles would be much easier to explain when we can contrast them against regular content (/content/) and static (/static/) files, as opposed to treating bundles as a special /content/ subdirectory.

@Jos512 I think you misunderstand my example. There is nothing special about the bundles section (I just named it that way to separate it from the other example sections). If you want to comment, you should read and understand the specification in my first post. In any case, you come late to the party.

@Jos512 I have updated the example with less confusing names:
http://hugotest.bep.is/section3/2017/11/my-article-1/
https://github.com/bep/hugotest/commit/375ca10594827b1e7b4e7c3b1bba2593ea18dc40

I have added some examples of my suggested Image API:
http://hugotest.bep.is/section3/2017/11/my-article-1/
https://github.com/bep/hugotest/commit/f014cda2ff7fbb331b6b111c829797b11bf1b71f
3 methods: Fit, Fill and Scale. There are more to it than the above, but that is the core.

@bep this looks amazing!

I think you misunderstand my example. There is nothing special about the bundles section (I just named it that way to separate it from the other example sections).

Thanks for clarifying that, that wasn't clear to me.

If you want to comment, you should read and understand the specification in my first post.

Point taken, and I'll keep watching the discussion. Although it does feel a bit of a shame if only people with the technical Go may give input. (But I understand it gives a lot of noise for you otherwise.)

In any case, you come late to the party.

I already expressed a concern for how to document and explain the bundles feature to new users on June 27. So I'm not really late, just replying twice here. 😄
Good luck on finishing this feature.
(No need to reply to this post.)

Question:
resourceDirs:
		"processedImages": "res/gen/images"

I will introduce a new project folder, which first will contain generated resources/images (thumbnails etc.). I don't want to call it a cache, because I want people to think about it as something that belongs "in the project" (and should be committed to Git etc.)
One could imagine the need for more folders inside resourceDirs, so we might get the names right? Suggestions?

For the curious, I have updated the examples at
http://hugotest.bep.is/section3/2017/11/my-article-1/
This now shows a more diverse media types handling (including JSON, which I guess could open up a fair amount of use cases).
The implementation is mostly done, but there are still lots of TODOs sprinkled around. I think I implemented the bundle logic 4 times before I settled on this one. Mostly for performance reasons. Now it is slightly faster than the current Hugo. More for less.
I will try to wrap this up for X-mas. I will push this to a branch in the gohugoio repo in a couple of days asking people to take it for a spin.

@stp-ip you are a little late for suggestions and early for questions. I think you will be happy, I know I will. This is good stuff.

@bep was not so much thinking about implementation detail suggestions, but documentation and early testing, which might influence another iteration or bug fixes etc.
But me being happy seems like single pages might finally work without data files \o/.
Ping me, when the PR is ready and I might be able to take it for a spin.

To the curious:
I plan to cut a release sometime next week, I want to get this out before the new year.
This is going to be really, really cool.


Add awesome-code-schools

Thanks, but the list isn't very useful as is. Add some descriptions and stuff. Try submitting again in the future when it's more mature.

Will do.


Update hmac and sha2 crates

Resubmission of #1772 that will hopefully pass tests.
Please help keep the CHANGELOG up to date by providing a one sentence summary of your change:
Update to hmac 0.8 and sha2 0.9

Ugh, broken due to https://github.com/hyperium/hyper-tls/pull/72. Will update when the bad version of tokio-native-tls gets yanked.

Ok, fixed now.


style: Remove unnecessary commas

Looking at other codes, it seems better to eliminate these commas. So I'm going to remove these commas.

This likely isn't exhaustive, as I'm pretty sure I've run across more than just these in passing. Can you be sure that it is?

@jhpratt This is applied to lines which match rg -F "),)". So I cannot be sure that this is exhaustive.
First, I discovered a redundant comma in the following doctest:
https://github.com/time-rs/time/blob/2e68a36abc0d8cdc12638c0ed47b80cc9c07b7ab/time/src/offset_date_time.rs#L77
Next, I ran rg -F "),)" and discovered a similar redundant comma in the following line:
https://github.com/time-rs/time/blob/2e68a36abc0d8cdc12638c0ed47b80cc9c07b7ab/time/src/serde/mod.rs#L208

If cleanup like this is being done, I'd like to be at least reasonably confident that it is exhaustive, lest we have a number of PRs substantially similar to this.

@sorairolake What's the status of this?

@jhpratt I'm not confident that I can do cleanups like this thoroughly.

Closing for that reason. I'll probably end up digging through code myself with some more complicated regex in the near future.


Failed to resolve: com.afollestad:easyvideoplayer:0.2.2

Error:(99, 13) Failed to resolve: com.afollestad:easyvideoplayer:0.2.2
Show in FileShow in Project Structure dialog
Any idea what's up?  I tried the other versions as well....

Something odd is going on with jCenter, but you can reference the Bintray repository directly.
Add this to your repositories { }:
    maven { url "https://dl.bintray.com/drummer-aidan/maven" }

That did it but then I realized the minSDK is 14 :(

useful

Hey please update your Read me file regarding maven . I was also facing same issue.

Please tell how to resolve step by step. I am new to android
Error:(31, 13) Failed to resolve: com.afollestad:easyvideoplayer:<IP_ADDRESS>


Assembly part aggregation not set properly when the part is created via palette entry instead of drag & drop

Issue and tracking information
If you create a part in an assembly diagram using the palette entry then the part created does not have the correct aggregation kind which causes the deployment validation to fail.
A workaround is to use the drag & drop feature instead of using the palette entry.
Developer's time Estimated effort to fix (hours):
Developer's Actual time spent on fix (hours)
Issue reporter to provide a detailed description of the issue in the space below

fixed


parity missing in minimal config

Running nequip-train configs/minimal.yaml' fails on a key error because parityis missing.  Addingparity: o3_fulltoconfigs/minimal.yaml` fixes it.

Thank you. Fixed.


Wallet issues!

Hi the reason I'm writing is because since Sunday I haven't been able to log into the wallet when I click on the icon it goes into the app but the screen right away turns black if you can write back with guidance on how to solve the issue will b greatly appreciated thank you and be safe.

The black screen was caused by a mishandled data upgrade bug，you can stay on the black screen and wait for a while, the app will turn normal while connected to remote node.
And the bug was fixed in latest release: v1.1.5-beta.1, sorry for the inconvenience.


Deleting textures/resources from Tileset is permanent even if do not save and you also lose tilemap data

Godot version
3.3 stable
System information
linux mint 19
Issue description
If you delete an entry from the tileset:

For example I have removed the first texture, as you can see the scene file is marked as updated and needing saving:

If you then close the scene without saving, when you open, then any changes you have made to the tilemap that do not involve those deleted textures, such as tilemap and config updates updates, are back to normal as you would expect, however, the tileset change is permanent and you have lost not only the entry in the tileset, but every tile is permanently set to -1 and those are lost too.

Steps to reproduce
As above, remove a texture, do not save and you lose not only the tileset but every tile in the tilemap that ever used it on re-opening.
Minimal reproduction project
No response

This is most likely fixed in the new TileMap/TileSet editor in 4.0 as part of its rewrite.

I figured, but it's a pretty bad bug in my eyes and didn't know if it
sounded like a simple fix given 4 isn't it for a while a migration won't
happen for a lot of people.
On Sat, 9 Oct 2021, 21:36 Hugo Locurcio, @.***> wrote:

This is most likely fixed in the new TileMap/TileSet editor in 4.0 as part
of its rewrite.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/53605#issuecomment-939358275,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADCERRIDY4NG7QXTQXJ6X7TUGCRWTANCNFSM5FVOOLDA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Logo/Name in nav navigate to home page

Description
Per Divyanish’s comment in the livestream, the GitHub Repo logo doesn’t direct users to the list page
Screenshots
No response
Additional information
No response

Duplicate of https://github.com/EddieHubCommunity/RepoRater/issues/27


"Note" section of this QuickStart reads: This article has recently been updated to use commands from the new Azure PowerShell Az module. But it is still using old PS commands

For example: For sign-in, the article is using Connect-AzureRmAccount and not the new command Connect-AzAccount.
For creating Resource Group, it's using New-AzureRmResourceGroup and not New-AzResourceGroup.
etc., etc.....
Question: Has this article really been updated to use commands from the new Azure PowerShell Az module? Or, maybe, I'm missing something here.

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

ID: b04a28c3-81d7-123d-5b16-6642636c07a8
Version Independent ID: 2179498b-00e8-1c9d-bd11-4a903ae3ad52
Content: Azure Quickstart - Create a blob in object storage using Azure PowerShell
Content Source: articles/storage/blobs/storage-quickstart-blobs-powershell.md
Service: storage
GitHub Login: @roygara
Microsoft Alias: rogarana

@saf-itpro Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@saf-itpro Thanks for pointing this out! You weren't missing something, they weren't in the article. They are there now, though!
#please-close


runc: 1.1.3 -> 1.1.4

https://github.com/opencontainers/runc/releases/tag/v1.1.4
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 188330 run on x86_64-linux 1

11 packages built:

buildah
cri-o
flintlock
hci
hercules-ci-agent
ignite
img
k3s
nvidia-podman
podman
runc


hecate: 0.0.1 -> unstable-2022-05-23

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
22.11 Release Notes (or backporting 22.05 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Thanks but I've already submitted one here and updated the dependencies too: https://github.com/NixOS/nixpkgs/pull/171858

Could you please replace buildGoPackage  with buildGoModule  like I do?

@aaronjheng done. It's basically the same as yours only without the recursive and I've also got rid of the deps.nix now that buildGoModule handles that.

Nice


Kindly solve the Swedish localisation

The screens for settings etc. do not contain any Swedish texts.

thanks @stenerikbjorling   can you provide 1 - 2 screenshots for reference?

Hi,
Here you go…
Take care, all the best…
Stene

2 nov. 2019 kl. 16:36 skrev Kerry Washington<EMAIL_ADDRESS>thanks @stenerikbjorling can you provide 1 - 2 screenshots for reference?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

This seems to be there and localized (v2.4.1):
Am I missing something?

Hi, solven with the latent uppdatera.
Thanks for good work!
Stene
Skickat från min iPad

2 nov. 2019 kl. 22:05 skrev Kerry Washington<EMAIL_ADDRESS>
This seems to be there and localized (v2.4.1):
Am I missing something?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

My pleasure!  Please share LiteWallet with your friends!  And feedback is always welcome!


Enable Node.js Language Metrics

We lost some nodejs metrics graphs, update the build packs and see if that re-enables them.
Fixes https://github.com/github/ecosystem-primitives/issues/485

Waiting on feedback from Heroku on why this isn't working

Turns out our package.json had the engine set to >= 12.x. Now that heroku's buildpack has node 13.x in it, our build dutifully installed node 13 (non-LTS bleeding edge). This PR will revert to 12.x and has a guard in the version to prevent being 13.x (until we decide we want that)

The metrics are back (in staging)!

Related issue surfaced from this and Heroku Support: https://github.com/heroku/heroku-nodejs-plugin/issues/14


SysTime from ISOExtString not allways works

If you let the influxdb set the time and then try to read it back, you get:
Invalid ISO Extended String: 2017-05-10T14:47:38.582524801Z
/usr/include/dmd/phobos/std/datetime.d:8816 @safe std.datetime.SysTime std.datetime.SysTime.fromISOExtString!(immutable(char)[]).fromISOExtString(const(immutable(char)[]), immutable(std.datetime.TimeZone)) [0xf1a524]
../../../../../.dub/packages/influx-d-0.2.5/influx-d/source/influxdb/api.d:337 const(@safe std.datetime.SysTime function()) influxdb.api.MeasurementSeries.Rows.Row.time [0x115e36d]\nsource/dal/ntf/influxdb.d:130

Problem is that SysTime works only with hnsecs, but it receives nsecs and so input is too long.
I've some time ago filled this bug to phobos: https://issues.dlang.org/show_bug.cgi?id=16053
So it should probably get fixed in the phobos.

I can't fix Phobos here but I can try to work around it, so I have.


Overcome 16MB variant limit in Snowflake

Some users with very large projects have encountered issues in the https://github.com/brooklyn-data/dbt_artifacts/blob/main/macros/upload_artifacts.sql#L25 copy into step, where the manifest.json is too large to load into a variant column. We currently use a single table for all artifact types, and each artifact becomes a single row.
We can solve this issue by flattening the data before loading into a Snowflake table. The schema for each artifact differs at the first level of keys however, and so we will need a separate table for each artifact.
Transformations are heavily restricted in the existing copy into command (Snowflake docs). If we instead use an insert into command to load from stage to table, we can run any select statement needed without any transformation restrictions. For example, an illustrative command similar to https://docs.snowflake.com/en/user-guide/data-load-transform.html#flatten-semi-structured-data:
insert into {{ src_dbt_artifacts_manifest }}(node, generated_at, path, artifact_type)
    select
        nodes.name as name,
        nodes.unique_id as unique_id,
        nodes.package_name as package_name,
        nodes.path as path,
        nodes.value as value,
        artifacts.metadata:generated_at::timestamp_ntz as generated_at,
        metadata$filename as stage_filename,
        regexp_substr(metadata$filename, '([a-z_]+.json)') as artifact_type
    from  @{{ src_dbt_artifacts }} as artifacts,
        lateral flatten(input => artifacts.nodes) as nodes
    where regexp_substr(metadata$filename, '([a-z_]+.json)') = 'manifest.json'

I might have a go at this while I'm still up to speed on dbt artifacts code. I'm going to suggest that we aim at the new V4 schema for dbt rather than trying to also support the v3 manifest.
https://schemas.getdbt.com/dbt/manifest/v4/
https://schemas.getdbt.com/dbt/run-results/v4/
My planned approach is:

New run operations, specific to the manifest and run-results files.
Those run operations will:

upload to stage
insert into staging temporary tables (i.e. tables which are tied to the current session)
load into a persistent new table (separate tables for manifest nodes, run results, sources etc...)

Adjust the staging models in the package to UNION the "old" approach (i.e. loading the whole json file) and the "new" approach (i.e. flatten on load). So that teams can easily transition.
Provide a final run operation which can do a one-off load from the old approach to the new one.

How does that sound as an approach?

Sounds like a great plan @alanmcruickshank !

Hi!
Just gave the V2 uploader a spin, and I can't seem to get around the 16MB limit still. Am I doing something wrong?
Log:
dbt --no-write-json run-operation upload_dbt_artifacts_v2
13:52:38  Running with dbt=1.0.3
13:52:38  Clearing existing files from Stage:
    remove @analytics_dev.dbt_larspetter.dbt_artifacts_stage pattern='.*\/c39ee8dc-197a-454e-9814-b4dddd921eea\/.*\.json.gz';

13:52:39  Uploading manifest.json to Stage:
        put file://target/manifest.json @analytics_dev.dbt_larspetter.dbt_artifacts_stage/c39ee8dc-197a-454e-9814-b4dddd921eea auto_compress=true;

13:52:42  Persisting flattened manifest nodes manifest.json from Stage:

    -- Merge to avoid duplicates
    merge into analytics_dev.dbt_larspetter.dbt_manifest_nodes as old_data using (
        with raw_data as (

            select
                manifests.$1:metadata as metadata,
                metadata:invocation_id::string as command_invocation_id,
                -- NOTE: DBT_CLOUD_RUN_ID is case sensitive here
                metadata:env:DBT_CLOUD_RUN_ID::int as dbt_cloud_run_id,

    sha2_hex(coalesce(dbt_cloud_run_id::string, command_invocation_id::string), 256)
 as artifact_run_id,
                metadata:generated_at::timestamp_tz as generated_at,
                manifests.$1 as data
            from @analytics_dev.dbt_larspetter.dbt_artifacts_stage/c39ee8dc-197a-454e-9814-b4dddd921eea as manifests

        )

    select
        manifests.command_invocation_id,
        manifests.dbt_cloud_run_id,
        manifests.artifact_run_id,
        manifests.generated_at::timestamp_tz as artifact_generated_at,
        node.key as node_id,
        node.value:resource_type::string as resource_type,
        node.value:database::string as node_database,
        node.value:schema::string as node_schema,
        node.value:name::string as name,
        -- Include the raw JSON to unpack other values.
        node.value as node_json
    from raw_data as manifests,
        lateral flatten(input => manifests.data:nodes) as node

    union all

    select
        manifests.command_invocation_id,
        manifests.dbt_cloud_run_id,
        manifests.artifact_run_id,
        manifests.generated_at::timestamp_tz as artifact_generated_at,
        exposure.key as node_id,
        'exposure' as resource_type,
        null as node_database,
        null as node_schema,
        exposure.value:name::string as name,
        -- Include the raw JSON to unpack other values.
        exposure.value as node_json
    from raw_data as manifests,
        lateral flatten(input => manifests.data:exposures) as exposure

    union all

    select
        manifests.command_invocation_id,
        manifests.dbt_cloud_run_id,
        manifests.artifact_run_id,
        manifests.generated_at::timestamp_tz as artifact_generated_at,
        source.key as node_id,
        'source' as resource_type,
        source.value:database::string as node_database,
        source.value:schema::string as node_schema,
        source.value:name::string::string as name,
        -- Include the raw JSON to unpack other values.
        source.value as node_json
    from raw_data as manifests,
        lateral flatten(input => manifests.data:sources) as source

    ) as new_data
    -- NB: We dedupe on artifact_run_id rather than command_invocation_id for manifest nodes
    -- to avoid holding duplicate data.
    on old_data.artifact_run_id = new_data.artifact_run_id and old_data.node_id = new_data.node_id
    -- NB: No clause for "when matched" - as matching rows should be skipped.
    when not matched then insert (
        command_invocation_id,
        dbt_cloud_run_id,
        artifact_run_id,
        artifact_generated_at,
        node_id,
        resource_type,
        node_database,
        node_schema,
        name,
        node_json
    ) values (
        new_data.command_invocation_id,
        new_data.dbt_cloud_run_id,
        new_data.artifact_run_id,
        new_data.artifact_generated_at,
        new_data.node_id,
        new_data.resource_type,
        new_data.node_database,
        new_data.node_schema,
        new_data.name,
        new_data.node_json
    )

13:52:44  Encountered an error while running operation: Database Error
  100069 (22P02): Error parsing JSON: document is too large, max size 16777216 bytes
    File 'c39ee8dc-197a-454e-9814-b4dddd921eea/manifest.json.gz', line 1, character 16777216
    Row 0, column $1


STORM-1970: external project examples refator

refactor example projects:

storm-elasticsearch
storm-hbase
storm-hdfs
storm-hive
storm-jdbc
storm-kafka
storm-mongodb
storm-mqtt
storm-opentsdb
storm-redis
storm-solr

What is it doing ? Do you add more desc ?

hi @darionyaphet  sorry for the less information.
this PR address @abhishekagarwal87 's topic from dev@ mailing list.

Right now the example topologies/classes for some external modules are being put up in the test folder itself. The problem I see is that,
-> the example code isn't really test code so test folder isn't the right fit.
-> people, who are looking for example code, may not find the example code.

@abhishekagarwal87 Could you take a look?

@vesense Thanks for your efforts. can you upmerge this PR?

@abhishekagarwal87 Upmerged.

@abhishekagarwal87 is this should be continue?

+1 Post the conflicts merge.
@HeartSaVioR - can you also take a look?

I think we have to make sure that users can run example topologies with local and also remote.
(Yes these modules are just examples but 'runnable' examples.)
So it might be better to apply two things:

profile trick to change scope of 'storm-core' : other modules use 'intellij' profile
create fat jar for each project : change scope of external module to 'compile'. Is there a reason to set this to 'provided'?

Other things look good.

hi @HeartSaVioR
Of course, we should make sure that all examples are  'runnable'.

profile trick to change scope of 'storm-core' : other modules use 'intellij' profile

Actually, I can't see what you mean..

create fat jar for each project : change scope of external module to 'compile'

Yes, I will change the scope to compile and add maven-shade-plugin for building a fat jar.
Thanks.

@vesense You can refer pom.xml of storm-starter to see the trick. It determines whether we apply 'provided' or 'compile' via property and profile.
https://github.com/apache/storm/blob/master/examples/storm-starter/pom.xml#L35

Thanks @HeartSaVioR  I see. Will update.

Updated.
the travis-ci build error is because that Network is unreachable for https://clojars.org.

@HeartSaVioR Could you take a look again?

@vesense Thanks for the update. +1

I will add new external project examples (such as storm-druid, storm-kinesis) to the examples directory in a following up jira after this PR being merged.


Fix: pass doc to data type delete

we werent passing the original doc to delete, so when encoding the protobuf it would fail (since there were a bunch of missing fields)

can you add a test for this? ideally one that failed prior to this but now passes with the change?

I borked the branch when changing base, so here's the new PR #420  @achou11


add 'location' in example parameter

sdk issue: https://github.com/Azure/azure-sdk-for-js/issues/26370
sdk pr: https://github.com/Azure/azure-sdk-for-js/pull/26380

Should not be a breaking and do not need ARM review for this.


[BUG]: Theme lost on Reload

What happened?
When i shift to light mode and reload the age goes back to dark mode. i can fix that to remember the last desired setting.
How can we reproduce this bug?
as described above
Desktop Information (Optional)
No response
Urgency (Optional)
None

Hey I am a GSSOC contributor. Please let me know if there is a issue with my code

Can I work on this issue? If yes, please assign the task to me under GSSoC'23

Sure @L-Pircy


Errors in Docker version

Hi there,
Thanks for an excellent project!
Issues are disabled on @SeanRiggs' repo, so I'm posting this here.  I'm trying to run the Docker version of the repo on a Raspberry Pi 4, but I get this error:
pi@flight:~/docker $ docker compose up
Attaching to weather-station
weather-station  |
weather-station  | ><EMAIL_ADDRESS>start /app
weather-station  | > node ./server/index.js
weather-station  |
weather-station  | /app/node_modules/axios/index.js:1
weather-station  | import axios from './lib/axios.js';
weather-station  | ^^^^^^
weather-station  |
weather-station  | SyntaxError: Cannot use import statement outside a module
weather-station  |     at Module._compile (internal/modules/cjs/loader.js:892:18)
weather-station  |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)
weather-station  |     at Module.load (internal/modules/cjs/loader.js:812:32)
weather-station  |     at Function.Module._load (internal/modules/cjs/loader.js:724:14)
weather-station  |     at Module.require (internal/modules/cjs/loader.js:849:19)
weather-station  |     at require (internal/modules/cjs/helpers.js:74:18)
weather-station  |     at Object.<anonymous> (/app/server/geolocationCtrl.js:1:15)
weather-station  |     at Module._compile (internal/modules/cjs/loader.js:956:30)
weather-station  |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)
weather-station  |     at Module.load (internal/modules/cjs/loader.js:812:32)
weather-station  | npm ERR! code ELIFECYCLE
weather-station  | npm ERR! errno 1
weather-station  | npm ERR<EMAIL_ADDRESS>start: `node ./server/index.js`
weather-station  | npm ERR! Exit status 1
weather-station  | npm ERR!
weather-station  | npm ERR! Failed at the<EMAIL_ADDRESS>start script.
weather-station  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
weather-station  |
weather-station  | npm ERR! A complete log of this run can be found in:
weather-station  | npm ERR!     /root/.npm/_logs/2023-11-03T12_05_25_325Z-debug.log
weather-station exited with code 0

My Docker Compose file is:
version: '3'
services:
  weather-station:
    image: seanriggs/pi-weather-station:arm64 #or arm64 (i.e. RaspberryPi)
    container_name: weather-station
    ports:
      - "8080:8080"
    volumes:
      - appdata:/app
    restart: unless-stopped
volumes:
  appdata:

I can run pi-weather-station natively on the Pi and it works fine.

FWIW - I decided to try to build my own Docker image for the project until Sean gets a chance to update his image (if he decides to do so.)
It seems to work fine as long as the /server/index.js workaround described on the repo is done.  It's fairly basic and I'm sure doesn't follow any Docker best practices, but it works.
FROM node:18-alpine
RUN mkdir /home/node/app
RUN mkdir -p /home/node/app/node_modules && chown -R node:node /home/node/app
WORKDIR /home/node/app
COPY --chown=node:node pi-weather-station/package*.json ./
USER node
RUN npm install
COPY --chown=node:node pi-weather-station/. .
EXPOSE 8080
CMD [ "npm", "start" ]

Put the above commands in a file names Dockerfile in a build directory.
git clone https://github.com/elewin/pi-weather-station.git in that directory
Apply the server/index.js workaround mentioned above.
Run: docker build -t weather-station:0.0.1 . in the build directory.
Run the container using your preferred method:

CLI
docker run -itd --name weather-station -p 8080:8080 -v -v appdata:/app weather-station:0.0.1
Docker Compose (my preferred method)
version: '3'
services:
  weather-station:
    image: weather-station:0.0.1
    container_name: weather-station
    ports:
      - "8080:8080"
    volumes:
      - appdata:/app
    restart: unless-stopped
volumes:
  appdata:

Feel free to ping me if you have any questions (or spot any issues).

Hey there,Thank you for sending this. I am in the military and deployed right now but will be back next week. I will look at all of what you have posted when I return. I don’t have a stable connection to test where I am at though. Thank you,Sean @.*** from my iPhoneOn Nov 4, 2023, at 9:09 AM, Roddie Hasan @.**> wrote:
FWIW - I decided to try to build my own Docker image for the project until Sean gets a chance to update his image (if he decides to do so.)
It seems to work fine as long as the /server/index.js workaround described on the repo is done.  It's fairly basic and I'm sure doesn't follow any Docker best practices, but it works.
FROM node:18-alpine
RUN mkdir /home/node/app
RUN mkdir -p /home/node/app/node_modules && chown -R node:node /home/node/app
WORKDIR /home/node/app
COPY --chown=node:node pi-weather-station/package.json ./
USER node
RUN npm install
COPY --chown=node:node pi-weather-station/. .
EXPOSE 8080
CMD [ "npm", "start" ]
Put the above commands in a file names Dockerfile in a build directory.
git clone https://github.com/elewin/pi-weather-station.git in that directory
Apply the server/index.js workaround mentioned above.
Run: docker build -t weather-station:0.0.1 . in the build directory.
Run the container using your preferred method:
CLI
docker run -itd --name weather-station -p 8080:8080 -v -v appdata:/app weather-station:0.0.1
Docker Compose (my preferred method)
version: '3'
services:
weather-station:
image: weather-station:0.0.1
container_name: weather-station
ports:
- "8080:8080"
volumes:
- appdata:/app
restart: unless-stopped
volumes:
appdata:
Feel free to ping me if you have any questions (or spot any issues).
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Fail2Ban ignored IP are not persistent

The fail2ban ignored IP are not persistent.
Context
When restarting the docker-mailserver container, the ignored IP are lost.
By default, fail2ban will ban every IP that has too many failed login attempts.
It works as expected when I am using mail client like Thunderbird or Outlook, but if I use a web mail client like RoundCube, the RoundCube IP's ends up being banned, preventing any user to use it! I thought it may be related to #523 but it's not docker's gateway that gets banned but the container itself and banning the RC IP makes sense (technically speaking).
I am setting the mail server and roundcube through docker-compose.
I am using the fail2ban-client to add the IP of RoundCube instance to dovecot ignoreip list:
docker exec mail /bin/sh -c "fail2ban-client set dovecot addignoreip $IP"

It works great, but when I restart the mail container, the ignore IP list is reset and I must add the IP all over again.
Expected Behavior
The ignored IP is reloaded after restarting the container.
Actual Behavior
IP ignore list is lost on restart.
Possible Fix
It may be a fail2ban limitation... but if that's the case I guess we could have a function in the setup script to store and reload this.
We could have a function to add ignored IP to a file and call fail2ban-client. Then read the content of the file on startup and call fail2ban-client for each entry.
Steps to Reproduce

docker-compose.yml

  mail:
    image: tvial/docker-mailserver:release-v5.8.0
    container_name: mail
    restart: always
    environment:
      - DMS_DEBUG=1
      - ONE_DIR=1
      - ENABLE_SPAMASSASSIN=1
      - ENABLE_CLAMAV=1
      - ENABLE_FAIL2BAN=1
      - ENABLE_POSTGREY=1
    cap_add:
      - NET_ADMIN
      - SYS_PTRACE
    volumes:
      - /srv/mail/data:/var/mail
      - /srv/mail/state:/var/mail-state

  roundcube:
    image: roundcube/roundcubemail
    container_name: roundcube
    restart: always
    environment:
      # System properties
      - ROUNDCUBEMAIL_UPLOAD_MAX_FILESIZE=5M
      - ROUNDCUBEMAIL_LOG_DIR=/srv/logs
      # IMAP server connection
      - ROUNDCUBEMAIL_DEFAULT_HOST=tls://mail
      - ROUNDCUBEMAIL_DEFAULT_PORT=143
      # SMTP server connection
      - ROUNDCUBEMAIL_SMTP_SERVER=tls://mail
      - ROUNDCUBEMAIL_SMTP_PORT=587
    volumes:
      - /srv/roundcube/html:/var/www/html
      - /srv/roundcube/logs:/srv/logs

Add the roundcube container IP to fail2ban ignore list and confirm:

# We add the container name (will work even when container restart and changes IP)
docker exec mail /bin/sh -c "fail2ban-client set dovecot delignoreip roundcube"
docker exec mail /bin/sh -c "fail2ban-client get dovecot ignoreip"

Restart containers using docker-compose and check the ignore IP list:

docker-compose restart
# roundcube is not part of the ignore list anymore
docker exec mail /bin/sh -c "fail2ban-client get dovecot ignoreip"

Your Environment

Mailserver version used: 5.8.0
Docker version used: Docker version 18.03.0-ce, build 0520e24

I have a similar setup.
I think fail2ban is aimed at external IPs in any cases. When I mean external, I think of outside of docker. t we update the /etc/fail2ban/jail.conf ignoreip value with the LANs currently used by docker as we probably don't want to ban any of those IPs?
Or, a maybe simpler solution is to move database by changing its location to inside a persisted volume.
In /etc/fail2ban/fail2ban.conf dbfile = /var/lib/fail2ban/fail2ban.sqlite3. That would make it persisted through restarts.
What do you think?

Didn't get the time to report earlier but I have been testing @callmemagnus first solution (mounting a custom fail2ban-jail.cf with the ignoreip containing the docker LAN) for a few months and it works great.
I preferred this solution because it seemed simpler to automatize addition of docker LAN but it's just my opinion
Maybe these solutions could be added to the fail2ban configuration wiki page?
Anyway, thanks a lot @callmemagnus for your help.
I will close this issue now.


Error kernelSize.size() == coorDim assert failed

Hi,
I am trying to use the pre-trained PartA^2_fc model to run it on the NuScenes dataset. I have successfully generated the required annotation files, such as infos_train.pkl, infos_test.pkl and so on.
However, when I try to run the code by using the PartA2_fc.yaml, I get the following error:
File ".../lib/python3.7/site-packages/torch/nn/modules/module.py", line 541, in __call__
    result = self.forward(*input, **kwargs)
  File "PCDet/pcdet/models/detectors/PartA2_net.py", line 106, in forward
    rpn_ret_dict = self.forward_rpn(**input_dict)
  File "PCDet/pcdet/models/detectors/PartA2_net.py", line 33, in forward_rpn
    **kwargs
  File ".../lib/python3.7/site-packages/torch/nn/modules/module.py", line 541, in __call__
    result = self.forward(*input, **kwargs)
  File "PCDet/pcdet/models/rpn/rpn_unet.py", line 471, in forward
    x = self.conv_input(input_sp_tensor)
  File ".../lib/python3.7/site-packages/torch/nn/modules/module.py", line 541, in __call__
    result = self.forward(*input, **kwargs)
  File ".../lib/python3.7/site-packages/spconv/modules.py", line 123, in forward
    input = module(input)
  File ".../lib/python3.7/site-packages/torch/nn/modules/module.py", line 541, in __call__
    result = self.forward(*input, **kwargs)
  File ".../lib/python3.7/site-packages/spconv/conv.py", line 151, in forward
    self.stride, self.padding, self.dilation, self.output_padding, self.subm, self.transposed, grid=input.grid)
  File ".../lib/python3.7/site-packages/spconv/ops.py", line 89, in get_indice_pairs
    stride, padding, dilation, out_padding, int(subm), int(transpose))
RuntimeError: PCDet/spconv/include/spconv/spconv_ops.h 40
kernelSize.size() == coorDim assert faild. error

If I am guessing correctly, this is because after voxelization of the point cloud, the NN model expects a particular dimension of voxel grid. I can probably correct this by changing the VOXEL_SIZE in PartA2_fc.yaml. Is this true? How should I calculate how to set this parameter?
Thanks for your help!

I don't know which layer it is, and how about the shape of the input tensor to this layer?
Also, the given model use (Nx4) as the input with xyz+ one intensity. You should make sure your input is correct.
The intensity and point density of KITTI and NuScenes may be different so you could not directly achieve a well results on the NuScene dataset with the given KITTI model.

Hey, thanks for the hint. Yes, you were right, I was inferring on 1 point cloud at a time, and the coordinates (and points) were missing the extra dimension added to keep track of different point clouds when batch processing.


How to test database interactions

@scottescue
Do you have any pointers on how the database interactions can be tested?

I generally only test the database interactions in my integration/end-to-end tests. When I'm able to do that, I have the integration test fire up a light-weight database, run the application's Liquibase migrations, and seed any data needed for the test methods.  All that happens once per class.  Then the test methods use a REST client to test interactions with resource methods, which in turn trigger actual interactions with the database.
I have a dropwizard-entitymanager-example project that includes an example of such an integration test. But I haven't gotten around to polishing it up and publishing it. I'll try to find some time to get it pushed out in the next day or so.

I wanted to see if there was any way other than using full stack tests to invoke the Dao. I can make do with this approach for now.


Update vote_out.md

Rephrased parts to clarify the "vote out" mechanic

By @andr444 : Rephrased parts to clarify the "vote out" mechanic


REPL becomes unusable after inputting malformed text

At the prompt, type:
f("a")")

Press Enter. REPL displays continuation prompt, but pressing Enter and Esc do nothing, and the inputted text can't be edited.

Actually, on testing this some more, typing " (ie, closing the string) fixes this. I think pressing Esc should immediately break back to the prompt, though; that's what rgui.exe does.

ESC: #1066. REPL appears alive (enter works). If I do Up Arrow it bring up original expression from the history and it can be edited (or executed which brings back >)

https://github.com/Microsoft/RTVS/commit/6dfa10c44d8fd01bd13400c9188d3bc631b9099e


Adds docs for Display and Editor Templates

Fixes #25921
This PR creates a new section "Display and Editor Templates" within /mvc/views.
It describes the use case and usage for the DisplayTemplates, which are used by the DisplayFor and EditorFor HTML helper methods.
It also adds a reference to this section in the toc.yml file.
Additionally, it adds a minimal Razor Pages sample project in the appropriate directory, to showcase the usage in a working environment – and to be used by the code snippet references.
Please have a look at the YAML header of display-templates.md, I'm not sure if it contains all the necessary metadata, especially the missing 'ms.author' tag (I don't have one…).
Thank you very much! :)

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

@Ducki  I pushed a commit to fix a warning so you'll have to pull before you push again.

@Ducki  closing, I brought your commits to #25959


[Stemcell Builder] Problem with running vagrant up.

Hi, all.
I try to run vagrant up local --provider=virtualbox. And I get following error output:
==> local: Entering 'go/src/github.com/cloudfoundry/bosh-agent'
==> local: rbenv: version `2.0.0' is not installed
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chmod +x /tmp/vagrant-shell && /tmp/vagrant-shell

Stdout from the command:

Reinitialized existing Git repository in /bosh/.git/
[master e7d8555] updated rsync
 Committer: root<EMAIL_ADDRESS>Your name and email address were configured automatically based
on your username and hostname. Please check that they are accurate.
You can suppress this message by setting them explicitly:

    git config --global user.name "Your Name"
    git config --global user.email<EMAIL_ADDRESS>
After doing this, you may fix the identity used for this commit with:

    git commit --amend --reset-author

 3 files changed, 3 insertions(+), 1 deletion(-)
 create mode 100644 .ruby-gemset
 create mode 100644 .ruby-version
Entering 'go/src/github.com/cloudfoundry/bosh-agent'

Stderr from the command:

stdin: is not a tty
rbenv: version `2.0.0' is not installed

The most possible reason is problem in provision script, but still here is an information about my environment:
VBoxManage 4.3.14r95030
Vagrant 1.6.3
berkshelf (3.2.3)
omnibus (4.0.0)
vagrant-berkshelf (4.0.3)
vagrant-omnibus (1.4.1)

Best wishes,
Alex L.

Not sure. All versions look good. We do not use local provider to build stemcells in CI. I would recommend using AWS provider since that's what all officially published stemcells come from.

AWS provider is not always suitable option for building stemcells. There could be bunch of reasons, for instance company policy.


[WIP] Refactor tracker config using pydantic

Fairly big refactor to use pydantic for tracker configuration.
Closes #88

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@f20c4f9). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             main    #112   +/-   ##
======================================
  Coverage        ?   0.00%
======================================
  Files           ?      13
  Lines           ?    1443
  Branches        ?       0
======================================
  Hits            ?       0
  Misses          ?    1443
  Partials        ?       0

Continue to review full report at Codecov.

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

Thanks @paddyroddy for the review - I think most suggestions are taken care of now.

Great well I reckon you may as well merge as not sure the other guys will have time


Virusscanners report this as a Virus

Microsoft says its a RAT and Virustotal also has 35 Positives.
https://www.virustotal.com/gui/file/f0e6606c8c04ca6377c92d17c0622edb521a13c8689bc3568cef29c97b09327e

False positives, you can clearly see generic virus names in bad brands and no detections within Kaspersky or other better av's..


show currently applied shaders in the terrain tab

I've created a tileset using shaders but I can't really see what I'm doing in the terrain tab

Thanks for making such a useful plugin!

Hi, that could definitely be improved. I have no experience applying shaders to tile atlases. I'll give it a shot some time today, but if you have a small example for me to work with, that would help a lot.

Aha, I worked out how to apply shaders to individual tiles, so I will see how easy it is to fix.

Here's a godot 4.1 project with a pink shader applied to a tileset incase you could still use it (.godot folder removed).
shader_tiles.zip

I believe I have it working. I had to learn a bunch about RenderingServer and how Godot handles materials:

Will do some testing before pushing it.

This should be fixed on the latest commit a23515216e8b1b927e3b43e9b4bbf273b2b979ac
If you can confirm it works for you, then I will close this ticket. Cheers!

seems to work on my end, thanks for the fix


Support different begin/end characters for quotes

Support different begin/end characters for quotes

Thanks, this is a simple and great addition. Give me few days to make a new release. I have some dependencies to update as well.

@dirondin Awesome, thanks. Merged it and deployed the new version, 0.3.4. I tested it, simple and works beautifully!


Links are not opening app

The app is currently in TestFlight beta. The links were detecting and opening the app, but for some reason are not working any more.
Example link: https://otcmeds.app.link/eUrU7fBGJK
OK so this is my current setup.

When the link loads I see the following for like half a second:

Then it redirects to the mobile view of the website.

This wound being a problem with TestFlight more than anything. I deleted TestFlight and our app and then reinstalled both and it now works. Who knew? ;)


Cannot download some files

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.30.2
Regression From
No response
Architecture
arm64
Storage Explorer Build Number
20230721.7
Platform
macOS
OS Version
macOS Ventura
Bug Description
I can download files from blob container A, but not from blob container B.
Both are under the same storage account, and I can download from blob container B via Azure portal.
If I try generating a SAS for blob container B and running azcopy cp in the terminal, I get the same issue.
Steps to Reproduce
Tricky to reproduce as it seems specific to a blob container.
Actual Experience
I get an error as seen below. Despite the message, I'd be very surprised if the issue was related to formatting since it's automatically generated by Storage Explorer.
Expected Experience
I'd expect to be able to download files just as I can for other blob containers.
Additional Context
{
  "message": "\"failed to perform copy command due to error: cannot start job due to error: cannot list files due to reason -> github.com/Azure/azure-storage-blob-go/azblob.newStorageError, /Users/azcopydev/go/pkg/mod/github.com/!azure/azure-storage-blob-go@v0.15.0/azblob/zc_storage_error.go:42\\n===== RESPONSE ERROR (ServiceCode=AuthenticationFailed) =====\\nDescription=403 Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature., Details: (none)\\n   HEAD https://foo.blob.core.windows.net/bar/baz/qux?se=2023-08-23t12%3A46%3A32z&sig=-REDACTED&timeout=901\\n   User-Agent: [Microsoft Azure Storage Explorer, 1.30.2, darwin, azcopy-node/3.0.0-rc.4 (darwin)  AzCopy/10.19.0-Preview Azure-Storage/0.15 (go1.19.6; darwin)]\\n   X-Ms-Client-Request-Id: [REDACTED]\\n   X-Ms-Version: [2020-10-02]\\n   --------------------------------------------------------------------------------\\n   RESPONSE Status: 403 Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.\\n   Date: [Mon, 24 Jul 2023 12:46:33 GMT]\\n   Server: [Microsoft-HTTPAPI/2.0]\\n   X-Ms-Error-Code: [AuthenticationFailed]\\n   X-Ms-Request-Id: [REDACTED]\\n\\n\\n.\\n\""
}

@ffisc would you be able to share the full log file with us?

The log indicates the signature doesn't match the blob you are trying to download. In the error message, it says the SAS is generated for this blob container "att-fraud" in storage account "benchmarks" (/blob/benchmarks/att-fraud). The blob you are trying to download is in container "bar" in storage account "foo".

The log indicates the signature doesn't match the blob you are trying to download. In the error message, it says the SAS is generated for this blob container "att-fraud" in storage account "benchmarks" (/blob/benchmarks/att-fraud). The blob you are trying to download is in container "bar" in storage account "foo".

Thank you. Somehow the issue seems to have solved itself.