New vocab review component

Once we have a glossary for the data guide (#47) and a tool tip component to auto-populate glossary definitions (#48), a vocabulary review component that automatically creates a vocab review section at the bottom of articles with definitions from the glossary would be great.  You can find an explanation for the full proposal here.
Basically, if we have a glossary and tool tips, it'd be really helpful to have a component that auto-populates a "vocab review" or "terminology review" section at the end of articles.  The information would be populated based on:

The tool tips used within the article
The terms and definitions provided by the glossary
New terminology identified by glossary entries that use this article as their "Learn more" link

My initial idea behind the review section is to have it divided into two sections, each of which will only be displayed if the relevant content exists:

A "referenced terminology" section that reprises all of the tool tips included within the article.  The terms and definitions are provided once again in a group in this section to make it easy to review related or prerequisite knowledge.
A "new terminology" section that is populated based on entries within the glossary that use this article as their "Learn more" link.  The article will likely not use tool tips for terminology that it is introducing and instead will define the term inline.  However, using the "Learn more" links from the glossary is a good way to identify new terminology introduced and thoroughly defined by this article.  This section will contain all of the new terms that are in this article as identified by the links back to this article.

The design for this can be found in the figma file linked from here (sorry, I'm not sure how to link to specific images in the vast figma board view): https://www.notion.so/prismaio/Glossary-page-New-Glossary-tooltip-and-Vocab-review-components-for-the-Data-Guide-5270160d69bc4864acb69970b9968c74

Hi @imchairmanm Is this still relevant? If not, could you close this issue?
If yes, add me as assignee :)

@nikolasburk

Since we're not planning to invest further into the Data Guide, I think we can close this one 👍


Add simple DAStore analytics

what was searched for
what clauses were in the Airtable
what clauses were actually found in the GDrive
IP location

this is the tricky one. Maybe try https://pypi.org/project/IP2Location/?

The ip2location webservice I'm trying is actually scarily precise...put me in North Cambridge. So we might want to consider adding some fuzzing? That's unlikely to be relevant information.

I think I raised this in the PR, but do we even need lat/long? Should city / postal be good enough? Otherwise I think the next best option is rounding lat long to some fixed discretization,

Post code across dozens of countries sounds unmaintainable to me to
actually learn anything. I think lat/long will scale better. Just want to
think about precision.
My case might have just been coincidentally close to my real address.
On Mon, Jan 17, 2022, 5:30 PM Bryce Willey @.***> wrote:

I think I raised this in the PR, but do we even need lat/long? Should city
/ postal be good enough? Otherwise I think the next best option is rounding
lat long to some fixed discretization,
—
Reply to this email directly, view it on GitHub
https://github.com/LemmaLegalConsulting/docassemble-tclpgoogledocsmerger/issues/25#issuecomment-1014927640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2KTSJZYALGENKFMBUO5LLUWSKBPANCNFSM5L63L4DQ
.
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.
You are receiving this because you were assigned.Message ID:
<LemmaLegalConsulting/docassemble-tclpgoogledocsmerger/issues/25/1014927640
@github.com>


Effective date index is not set properly in Volto

Steps to reproduce:

login as admin
create a new page
publish the new page
check effective date of the new page
-> the effective date (both EffectiveDate and effective) indexes are set to None or the default value 1970

What happens in standard Plone is that if you publish an item the effective date index is set to now. We have to make sure this work similarly in Volto.

Fixed with https://github.com/plone/plone.restapi/pull/761


trojan-GFW failed

i often get the trojan-GFW failed after running the script. What could be the cause?

closed due to no activity


Api connection error

PHP Version
8.1
Shopware Version
6.4.18
Actual behaviour
When the plugin is anabled, I get many error in the Notifications.
Please also see https://shopwarecommunity.slack.com/archives/C011VFQT7GB/p1672588561377459

Expected behaviour
normal functioning / no error
Steps to Reproduce?
add theme and config theme
install bunnycdn plugin and config
enable filesystem on CDN
afbeelding

Hi,
I've transferred the issue to the correct repository.
Does it help to compile theme and install assets in cli?

Hi @tinect,
For the theme Yes. But I still get api errors.
FYI; Theme compiling took almost one hour.

FYI; Theme compiling took almost one hour.
Please read the hint marked with the blue bubble and the questions mark at the setting. This is no issue by this plugin, just for the count of data being transferred.

I cannot reproduce your problem with the error. It's thrown by shopware when you got logged out in background f.e.
But this seems unrelated to this plugin? 🤔

I'll have an look again on Monday, perhaps its something else.

If this is still relevant for you, feel free to come back with more details.


Implement NewSignerFromCertificate

This PR moves all the exported functions from github.com/notaryproject/notation/pkg/signature to notation-go/signature. After this PR is merged, that package can be deleted.
It also generalizes the API, so it is easier to test and to use from external plugins.
Open question: I think that with this PR we can delete the github.com/notaryproject/crypto/cryptoutil package, as once notation starts using the new APIs, it won't depend on cryptoutil anymore. Do you know of someone else who is using cryptoutil?
@shizhMSFT @SteveLasker

@qmuntal, with changes across multiple repos, is there a staging place where we can pull a collection of the binaries and validate end to end?

I've decided to retract this PR after thinking about the implications of @jaredpar and @rgnote comments.
My initial goal was to factor out NewSignerFromCertificate and Verifier.AddCertPEM from notation to notation-go, so it can be reused by other applications. What I didn't saw when doing the PR is that notation code could be simplified by reusing functions and methods from the standard library, leaving NewSignerFromCertificate and Verifier.AddCertPEM without much value.
I'll submit a PR to notation with the identified simplifications and submit another PR to notation-go adding documentation on tip about how to use our existing API to create signers and verifiers from PEM files. Thanks everyone!


VizPanelBuilder: Allow limiting number of frames initially rendered

The goal of this PR is to bring the UI we show in explore when there are more then N frames being rendered in a panel. This was implemented in Explore Logs, but I think this is something that all Scene apps could benefit from to prevent breakdown scenes with many timeseries from eating up browser resources.
This PR:

Hover header:

Current UI in explore:

Example usage:
PanelBuilders.timeseries()
.setData($data)
.setTitleItems([new LimitFramesTitleItemScene({
   frameLimit: 20, // limits the default number of frames that are rendered in the viz
 })])

If the LimitFramesTitleItemScene titleItem is not defined the panels will (attempt to) render everything.
Future work:

I mostly copied the UI from the existing feature in Explore, but it still uses quite a bit of panel header real estate, would be good to iterate on the UI in a future PR and find something a bit cleaner.

📦 Published PR as canary version: 5.27.0--canary.912.12014950388.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>

After the latest commit, findDescendent is no longer used in this PR, although it is still being used in the tests. We could remove that sceneGraph function in this PR if reviewers think that is out of scope, or unnecessary in this PR.

@gtk-grafana I really like this feature, much needed. While this solution works it feels unnecessarily complex (blaming scenes arch for here) , Tried to explore a different solution to this feature in this PR https://github.com/grafana/scenes/pull/978


Added Anadolu University

aof.anadolu.edu.tr

@mucahitcam81 I am sorry, the domain aof.anadolu.edu.tr is removed from our trusted domains list because the school allows to register an email address there even if you are not a student of the school. If you are the student of this school, please apply with official document (OFFICIAL DOCUMENT tab at https://www.jetbrains.com/shop/eform/students).


Refactor routes

Rewrote routes in separate files for easy collaboration in future. I utilized express.Router() and each "module" has it's own prefix for URLs.

[x] Move user routes to separate file with /user prefix
[x] Move review routes to separate file with /reviews prefix
[x] Move "courses" routes to separate file with /courses prefix
[x] Eliminate duplication of middlewares by moving them to middlewares/*fn-name.js

Redirect homepage to /courses for now.
This will close #67

Looks much better!


Unable to remove overlays

Version Number
1.18
What branch are you on?
master
Describe the Bug
I accidentally added resolution overlays for 1080p and can't remove them.
I have tried:

- remove_overlays: true
- reapply_overlays: true
- reset_overlays: plex

Any ideas on how to remove these overlays?
Relevant Collection/Overlay/Playlist Definition
No response
Logs
https://gist.github.com/TylerVigario/ab429b878a81fe3b5666bcad6cf1d6cb

Do you mean you've tried all three of those at once?

- remove_overlays: true

should remove the overlays by restoring the backup image and without reapplying any overlays that are defined in the config.
- reapply_overlays: true

Should reapply the same overlays as before, using the backup image, whether or not PMM thinks it has to do so.
- reset_overlays: [plex|tmdb]

Should retrieve a new image from the specified source and apply overlays on that image.

I've wrote on the discussion section about a similar problem.
With those options theoretically pmm should reset the overlay to the plex default one (the reapply gets ignored, if I understand correctly from the code).
The problem is the fact that on my instance not all overlays get removed.
On some movies/shows/season/episode the overlay remains the same as before (in some cases with a double overlay in different position, like the OP, if I have moved them for testing).
I can't understand why the overlays get doubled in the first place, then there's the "can't delete them" question also.

Here's one scenario where an overlay could get doubled.  Note that I am not saying this is what happened in your case, just offering it as a case where this could happen.
You run an overlay job.  PMM sets the artwork and the "Overlay" label on each item.  Now, you want to put some overlay in a new position, so you mass-remove the "Overlay" label to get PMM to reapply the new overlay.  PMM applies the new overlay, but the base image it pulls from Plex has overlays on it already, so the newly overlaid image has both.  Also, the backup image probably gets overwritten with the previously-overlaid image, so when you try to remove or reapply overlays the base will be the previously-overlaid image.
In your case it could be that the attempt to retrieve a new image from Plex fails, so the art doesn't get reset; I saw this a fair amount when testing this yesterday.  That should be shown in the log.
You  could take a look in the original artwork backup folder to see if some of these things are baked up with overlays already on them.

Here's one scenario where an overlay could get doubled.  Note that I am not saying this is what happened in your case, just offering it as a case where this could happen.
You run an overlay job.  PMM sets the artwork and the "Overlay" label on each item.  Now, you want to put some overlay in a new position, so you mass-remove the "Overlay" label to get PMM to reapply the new overlay.  PMM applies the new overlay, but the base image it pulls from Plex has overlays on it already, so the newly overlaid image has both.  Also, the backup image probably gets overwritten with the previously-overlaid image, so when you try to remove or reapply overlays the base will be the previously-overlaid image.
In your case it could be that the attempt to retrieve a new image from Plex fails, so the art doesn't get reset; I saw this a fair amount when testing this yesterday.  That should be shown in the log.
You  could take a look in the original artwork backup folder to see if some of these things are baked up with overlays already on them.

That seems like an issue with PMM.

The backup folder you mentioned, is those that gets created in the config/overlays folder?
In that case, every file in that folder doesn't have overlays, I've checked the ones that gives this problem (they are always the same, at every run that I try to delete them).
I never touch anything on plex, so I think that this labels problem it's not my case.
I just stop the docker, change the positions in the config (through template variables, I've the pmm default ones), and restart the docker, so the labels shoud be where they were before, am I wrong?
What else could be generating this double overlay?

Once the overlay label is removed from the item, PMM has no way to tell if the current poster has overlays on it.

The only thing that's going to generate a double-overlay, barring a config that is applying them deliberately, is PMM working with a base image that already has them.
I can't explain in a vacuum why this is happening in your specific case, but I tried to break it yesterday and couldn't.

But back to the original question.
Did you try all three of these at the same time, or one at a time, or what?  In testing yesterday, if I added
- remove_overlays: true

under overlay_path and left the rest of the overlay config stuff alone, all overlays were removed.

But back to the original question.
Do you want to remove all overlays, or just the 1080p one and leave some others?
Did you try all three of these at the same time, or one at a time, or what?  In testing yesterday, if I added
- remove_overlays: true

under overlay_path and left the rest of the overlay config stuff alone, all overlays were removed.

I tried them separately and at this point removing all of the overlays would work as well. However I do just want the 1080p overlays gone.
In all of your examples I can't understand how it's something I did versus a mishandling of "labels" (as you put) by PMM.
Maybe we need a better method of keeping track of what overlays are applied on any given poster?
For what it's worth this started roughly a month ago when `template_variables' weren't acting right. It erroneously added the 1080p overlays even though I had it set not to. And now I can remove them through any official PMM mechanism.

In my experiments,
- reset_overlays: tmdb

Has always grabbed new artwork from tmdb and reapplied appropriate overlays.  if the overlay config no longer includes the 1080p overlay, it won't be applied to the new artwork.
- reset_overlays: plex

In my experiments has been more hit-or-miss in that sometimes is seems to be unable to get new artwork from Plex.
Ordinarily, just removing an individual overlay from the config is sufficient to remove it
Going from this:
libraries:
  Movies:
    metadata_path:
    - pmm: actor
    - pmm: genre
    overlay_path:
    - pmm: ribbon
    - pmm: ratings

to
libraries:
 Movies:
   metadata_path:
   - pmm: actor
   - pmm: genre
   overlay_path:
   - pmm: ribbon

And rerunning PMM would remove the ratings overlays without any reset/remove/reapply required.
I didn't intend to say this was your fault.  Just providing an example scenario in response to "I can't understand why the overlays get doubled in the first place".
Chances are this was all initially triggered by some bug or another, but resetting to tmdb artwork has always worked for me.

There's a brute force way to do just the artwork reset here:
https://github.com/chazlarson/Media-Scripts

I think it's really a pmm thing, I'll explain why I think so.
When I've noticed the first time this "double overlay" behaviour, I've stopped pmm (and every other service that might act inside plex), I've emptied all plex libraries (moving everything out of the libraries and using the beautiful script of bullmoose20 (https://github.com/bullmoose20/Plex-Stuff/blob/main/plex-bloat-fix.py) to clean everything up).
Then I've launched pmm only with a single overlay for a library (like for example the defaults/overlays/resolution) without any template_variable, and the usual stuff on the metadata section.
After the first completed run, I've tried to move it, and it gets doubled only on some elements of the libraries like I was saying before.
So, I had to repeat the emptying part, and trying again, without anything in the metadata or operations, just the single overlay as before, with the same method: first run clean, second run moved.
It gets doubled again.
So, if it works ok for you, this narrows it down to two scenarios:

I have an error in the config
pmm bugs something out when it runs on my end

I'll attach my usual config, just to check if everything it's okay, but it's a pretty standard one:
libraries:
  Movies:
    report_path: config/Movies_report.yml
    template_variables:
      collection_mode: hide
      use_separator: true
    metadata_path:
      #award
    - pmm: separator_award
    - pmm: bafta
    - pmm: cannes
    - pmm: choice
    - pmm: emmy
    - pmm: golden
    - pmm: oscars
    - pmm: other_award
    - pmm: spirit
    - pmm: sundance
      # both
    - pmm: actor
    - pmm: audio_language
    - pmm: genre
    - pmm: resolution
    - pmm: streaming
    - pmm: studio
    - pmm: studio_anime
    - pmm: subtitle_language
    - pmm: year
      # chart
    - pmm: separator_chart
    - pmm: anilist
    - pmm: basic
    - pmm: flixpatrol
    - pmm: imdb
    - pmm: myanimelist
    - pmm: other_chart
    - pmm: tautulli
    - pmm: tmdb
    - pmm: trakt
      # movie
    - pmm: content_rating_us
    - pmm: country
      template_variables:
        style: color
    - pmm: decade
    - pmm: director
    - pmm: franchise
    - pmm: producer
    - pmm: seasonal
    - pmm: universe
    - pmm: writer
    overlay_path:
    #- remove_overlays: true
    #- reapply_overlay: false
    #- reset_overlays: plex
    - pmm: commonsense
    - pmm: flixpatrol
    - pmm: languages
      template_variables:
        use_it: true
        weight_it: 609
    - pmm: languages
      template_variables:
        use_it: true
        weight_it: 609
        use_subtitles: true
    - pmm: mediastinger
    - pmm: ratings
      template_variables:
        rating1: critic
        rating1_image: imdb
        rating2: audience
        rating2_image: tmdb
        rating3: user
        rating3_image: rt_tomato
    - pmm: resolution
    - pmm: ribbon
    - pmm: video_format
    operations:
      mass_genre_update: tmdb
      mass_content_rating_update: mdb_commonsense
      mass_originally_available_update: tmdb
      mass_audience_rating_update: tmdb
      mass_critic_rating_update: imdb
      mass_user_rating_update: mdb_tomatoes
      mass_imdb_parental_labels: without_none
      mass_collection_mode: hide
      split_duplicates: true
      delete_collections:
        managed: false
        configured: false
        less: 1
      metadata_backup:
        path: config/Movies_Metadata_Backup.yml
        sync_tags: true
        add_blank_entries: false
  Series:
    report_path: config/Series_report.yml
    template_variables:
      collection_mode: hide
      use_separator: true
    metadata_path:
      #award
    - pmm: separator_award
    - pmm: bafta
    - pmm: cannes
    - pmm: choice
    - pmm: emmy
    - pmm: golden
    - pmm: oscars
    - pmm: other_award
    - pmm: spirit
    - pmm: sundance
      # both
    - pmm: actor
    - pmm: audio_language
    - pmm: genre
    - pmm: resolution
    - pmm: streaming
    - pmm: studio
    - pmm: studio_anime
    - pmm: subtitle_language
    - pmm: year
      # chart
    - pmm: separator_chart
    - pmm: anilist
    - pmm: basic
    - pmm: flixpatrol
    - pmm: imdb
    - pmm: myanimelist
    - pmm: other_chart
    - pmm: tautulli
    - pmm: tmdb
    - pmm: trakt
      # show
    - pmm: content_rating_us
    - pmm: country
      template_variables:
        style: color
    - pmm: decade
    - pmm: franchise
    - pmm: network
    overlay_path:
    #- remove_overlays: true
    #- reapply_overlay: false
    #- reset_overlays: plex
    - pmm: commonsense
    - pmm: commonsense
      template_variables:
        overlay_level: season
    - pmm: flixpatrol
    - pmm: languages
      template_variables:
        use_it: true
        weight_it: 609
    - pmm: languages
      template_variables:
        overlay_level: season
        use_it: true
        weight_it: 609
    - pmm: languages
      template_variables:
        overlay_level: episode
        use_it: true
        weight_it: 609
    - pmm: languages
      template_variables:
        use_it: true
        weight_it: 609
        use_subtitles: true
    - pmm: languages
      template_variables:
        overlay_level: season
        use_it: true
        weight_it: 609
        use_subtitles: true
    - pmm: languages
      template_variables:
        overlay_level: episode
        use_it: true
        weight_it: 609
        use_subtitles: true
    - pmm: mediastinger
    - pmm: mediastinger
      template_variables:
        overlay_level: season
    - pmm: mediastinger
      template_variables:
        overlay_level: episode
    - pmm: ratings
      template_variables:
        rating1: critic
        rating1_image: imdb
        rating2: audience
        rating2_image: tmdb
        rating3: user
        rating3_image: rt_tomato
    - pmm: ratings
      template_variables:
        rating1: critic
        rating1_image: imdb
        rating2: audience
        rating2_image: tmdb
        rating3: user
        rating3_image: rt_tomato
        overlay_level: episode
    - pmm: resolution
    - pmm: resolution
      template_variables:
        overlay_level: season
    - pmm: resolution
      template_variables:
        overlay_level: episode
    - pmm: ribbon
    - pmm: ribbon
      template_variables:
        overlay_level: season
    - pmm: ribbon
      template_variables:
        overlay_level: episode
    - pmm: status
    - pmm: video_format
    - pmm: video_format
      template_variables:
        overlay_level: season
    - pmm: video_format
      template_variables:
        overlay_level: episode
    operations:
      mass_genre_update: tmdb
      mass_content_rating_update: mdb_commonsense
      mass_originally_available_update: tmdb
      mass_audience_rating_update: tmdb
      mass_critic_rating_update: imdb
      mass_user_rating_update: mdb_tomatoes
      mass_episode_audience_rating_update: tmdb
      mass_episode_critic_rating_update: imdb
      mass_episode_user_rating_update: tmdb
      mass_imdb_parental_labels: without_none
      mass_collection_mode: hide
      split_duplicates: true
      delete_collections:
        managed: false
        configured: false
        less: 1
      metadata_backup:
        path: config/Series_Metadata_Backup.yml
        sync_tags: true
        add_blank_entries: false
playlist_files:
- file: config/defaults/playlist.yml
settings:
  cache: true
  cache_expiration: 60
  asset_directory: config/assets
  asset_folders: true
  asset_depth: 0
  create_asset_folders: false
  prioritize_assets: false
  dimensional_asset_rename: false
  download_url_assets: false
  show_missing_assets: false
  show_missing_season_assets: false
  show_missing_episode_assets: false
  show_asset_not_needed: false
  sync_mode: sync
  default_collection_order:
  minimum_items: 1
  delete_below_minimum: true
  delete_not_scheduled: false
  run_again_delay: 30
  missing_only_released: true
  show_unmanaged: false
  show_filtered: false
  show_options: true
  show_missing: false
  show_unconfigured: false
  only_filter_missing: false
  save_report: true
  tvdb_language: eng
  ignore_ids:
  ignore_imdb_ids:
  item_refresh_delay: 0
  playlist_sync_to_users:
  playlist_report: true
  custom_repo:
  verify_ssl: true
  check_nightly: true

I can only offer that I've gone through another series of experiments today and I cannot reproduce any unexpected behavior.

So, I've no choice to use this feature without some errors?   xD
Maybe it's the size of my libraries, but I can't be the only one with a lot of stuff on plex, I've got like 5k movies and 1k series, a normal run with the config above lasts about 1.5-2 day.
That's the reason why I've been experimenting with the reapply_overlay flag, I don't need all the overlays recreated on every single item, but only if something changes on that element.
But that doesn't work either on my part, so I've given up and removed all overlays altogether.
It sucks that this can't be solved easily because it's a wonderful feature.

In my experiments,
- reset_overlays: tmdb

Has always grabbed new artwork from tmdb and reapplied appropriate overlays.  if the overlay config no longer includes the 1080p overlay, it won't be applied to the new artwork.
- reset_overlays: plex

In my experiments has been more hit-or-miss in that sometimes PMM seems to be unable to get new artwork from Plex.

I'll give this a shot when I get home

I've relaunched pmm with the overlays and I'm checking the labels.
It seems that the Overlay labels doesn't get applied on some items, even if the log doesn't show errors or anything strange as it applies the overlays.
So, that's the reason for the doubled overlays.
Now I've to understand why it happens, only on some items.

Odd; that's not something I've ever seen.

Don't know what to say, the docker should be the same as the rest, and the config is the one posted before.
For the series library it's even worse, we're like 60-70% with overlays and no labels.

More experiments today, and I think I've found a problem and a solution for this edge case.  I could only make it happen by forcing it, so it's likely that the initial situation arises due to some bug or other, and I can't reproduce or explain the "only applies overlay label to some of the items" scenario.
Basically, the reset_overlays: tmdb operation doesn't get applied to items without the "Overlay" label, so here was what I did to recover in my test library:

empty the backup images directory for the library, if there's anything in there.
manually apply "Overlay" label to everything in the library
run with reset_overlays: tmdb.  Now everything got a new poster with overlays applied and the backup images are all non-overlaid.
From here, if you want to remove all overlays, do a run with remove_overlays: true, then remove the overlay section from your config.
if you want to adjust the overlays [like getting rid of the 1080p overlay], edit the config as usual, remove the remove_overlays: true, and run PMM.

I'm planning to write this up with all the screenshots and configs I just saved and will post that here and in the discord.
Another option outside PMM would be to remove all the "Overlay" labels from everything and run the reset_posters_tmdb.py script from the repo I linked above.

I don't think the situation is caused by an external factor, it's the same even if I manually reset the library with the steps listed above:

moving everything out of the library
clearing pmm backup folders
clearing plex metadata with the script
moving the files back in the library, as a clean start

I've noticed that even in your script's README, you mention some problems with the labels, I think it's the same reason, but unknown cause.

At this point I think the problem lies on plex part, not pmm, maybe for some internal reason the labels aren't reliable, but I don't know how to test it for being sure.

manually apply "Overlay" label to everything in the library

Any easy way to do this? I have an expansive library.
Would it be more reliable to keep track of these labels internally in a database?

I don't think keeping track externally helps very much.  It's still a flag keeping track of whether a thing is in place or not, and presumably having the flag on the item in Plex's database is more reliable than having it in an external database that can be deleted at any time.

I don't think keeping track externally helps very much. It's still a flag keeping track of whether a thing is in place or not, and presumably having the flag on the item in Plex's database is more reliable than having it in an external database that can be deleted at any time.
Leaving aside this mysterious thing where sometimes G4Zz0L1's labels don't get updated consistently.

I respectfully disagree. Right now you rely on a field within Plex (also a database) which is easy to manipulate within the Plex web interface. This also opens up the opportunity that Plex doesn't properly set the flag or remove it for whatever reason, and there isn't much you can do about that.

I respectfully disagree. Right now you rely on a field within Plex (also a database) which is easy to manipulate within the Plex web interface. This also opens up the opportunity that Plex doesn't properly set the flag or remove it for whatever reason, and there isn't much you can do about that.

Any solution has tradeoffs, it's true.  Ultimately it's up to the author to make any changes he sees fit.

Any solution has tradeoffs, it's true. Ultimately it's up to the author to make any changes he sees fit.

Agreed. Thanks again for all your help!

Leaving aside this mysterious thing where sometimes G4Zz0L1's labels don't get updated consistently.

@chazlarson It's not mysterious, it's happened to you too, as far as I read on your repo.
There isn't something I can test, to check if the problem with these labels it's on plex side or on pmm?

I’ve never seen the case you describe where PMM, while setting overlays, only sets the overlay label on some of the items.  I have seen a limited issue on a fixed set of items in a library when attempting to remove labels.  In my case, it was always the same few movies.  I haven’t seen a general problem adding or removing labels.  The reason I described it as mysterious is that it’s not a common problem and apparently doesn’t have a repeatable recipe.  It could be a database issue, or a PlexAPI issue, or a Plex issue.  It’s mysterious in that it has an unknown cause and can’t be reproduced at will.

So, in short, there is a feature of pmm I can't use, because of this and the fact it can't be narrowed down to be solved   xD
As you've writed on you repo, the percentage of failure to edit labels (add or remove it's the same, for that matter) is roughly the same here, and on the same fixed set of items every run as you say, so I thought it was the same reason.
Maybe the devs can shed some light here, but if it's as you say it's not a thing that can be solved here on pmm, as far as I understand.
I'll try to wrap my head around this and give up, thanks for the help.

I've tried to search this on my own, even if I'm not great with python.
Can this be the cause of this issue? https://github.com/pkkid/python-plexapi/issues/988
I've searched around the code, if I'm not mistaken the only point where the labels are added is this one:
https://github.com/meisnate12/Plex-Meta-Manager/blob/nightly/modules/plex.py#L749
I don't see a reload like in the other issue, and if it's the same problem, maybe a fix on the PMM side is required to work, right?
Or maybe I overreached and it's not the same, tell me if I'm wrong.


Bravo

You should create a folder named bravo and create Welcome.php, instead of creating Bravo.php.
All class name should be capital, e.g. Bravo.php not bravo.php

closes #7


Apply Attack Surface Reduction (ASR) rules via MECM for Modern Unified Solution

Query - WIll Attack Surface Reduction (ASR) rules by configurable via MECM for 2016 & 2012 R2 servers utilising the Modern Unified Solution? Or is ASRs just configurable Windows server 1803+ via MECM?

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

ID: b77c40dd-e4d2-90f5-d70a-b0ee4b430136
Version Independent ID: f0ec110b-7938-5e22-d39e-6ded935a9ced
Content: Onboard Windows servers to the Microsoft Defender for Endpoint service
Content Source: microsoft-365/security/defender-endpoint/configure-server-endpoints.md
Product: m365-security
Technology: mde
GitHub Login: @mjcaparas
Microsoft Alias: macapara

@Phildo76 Thank you for your feedback.  We have added it to the Known issues and limitations as not all Attack Surface Reduction rules are available on all operating systems.  The minimum Windows Server build is version is 1809 or later for ASR.
You can find more information here- https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-reference?view=o365-worldwide#public-preview-supported-operating-systems
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @Phildo76 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


[Bug Report] Multiply and divide has different broadcasting rules

Describe the bug
I can't use ttnn.divide same way as ttnn.multiply. Multiply works as expected, divide crashes.
To Reproduce
import ttnn
import torch
import numpy as np

with ttnn.manage_device(device_id=0) as device:
    x = torch.ones((1, 2, 3, 4), dtype=torch.bfloat16)
    y = torch.ones((1, 1, 1, 1), dtype=torch.bfloat16) * 0.5

    x_tt = ttnn.from_torch(x, dtype=ttnn.bfloat16, layout=ttnn.TILE_LAYOUT, device=device)
    y_tt = ttnn.from_torch(y, dtype=ttnn.bfloat16, layout=ttnn.TILE_LAYOUT, device=device)

    x_y_mult_tt = ttnn.multiply(x_tt, y_tt)
    print(ttnn.to_torch(x_y_mult_tt))

    x_y_divide_tt = ttnn.divide(x_tt, y_tt)
    print(ttnn.to_torch(x_y_divide_tt))

Expected behavior
Divide should have same broadcasting rules to multiply.
Please complete the following environment information:

OS: Ubuntu 20.04
Version of software (eg. commit): 12fdb68d525ebc73c5e9e19db9a953e3640c5359

@eyonland I think you are owner of the unary/binary ops. Feel free to move to the right person.

HI @yugaoTT I've noticed that DIV is implemented as RECIP and MUL ops inside.
Looks like the case where broadcast should work was accidentally missed and seems easy to support it as everything is ready.

@umadevimcw,  it looks like your solution would generalize for both inputs automatically and possibly solve this as a general case on eltwise ops.   I think the return on this is high and we quickly get to better coverage of this functionality.

@umadevimcw  changes are not acceptable. It should be solved in the normal way.
Yo rub one simple DIV op we added a few more ops.
@eyonland It is a really bad solution for a couple of reasons:

we are adding specific changes to the generic binary function
we are making division slower. If we want to make it slower we can always call reciprocal and than multiplication like what we are doing right now as a workaround.

@umadevimcw Thanks for providing detailed explanation.
Could you please provide more information:

why ttnn::divide is executed as two operations? We are often work in bfloat16 which suffers from lack of precision and I would expect every operation takes a little bit of precision from the result.
why don't we re-use multiply broadcasting mechanism inside DIV_FAST? (In proposed solution we use redundant multiply to use it implicitly)
I think it's fair to have bunch of workarounds in the model (temporarily), but we shouldn't have hacks on top of hacks in ops development. What's our current position on this?
From performance perspective, when we perform divide we perform 3 operations: multiply, multiply, reciprocal (which is divide). I think it's unreasonable and be a hidden source of development slowdown. What's our policy here for adding overhead?

Thanks in advance!

@rfurko-tt and @dmakoviichuk-tt ,  if I understand this problem correctly, we cannot do broadcasting within the kernel operation itself because there is no clear way to identify the logical shape of the tiled tensor in the width and height dimensions.   We either need to allow this workaround to unblock models or we wait for the tensor layout and shape class to be rewritten and at that time we come back to this and fix the kernels to properly handle the broadcasting.    My position is that we allow this for now, knowing it is not an optimal solution, but then circle back and implement this properly in the kernel itself after the tensor layout is fixed.   @umadevimcw , please open a separate issue to track the work of implementing broadcasting in the kernel itself.  This needs to be done regardless of the outcome of this issue.

@eyonland
You understood the problem incorrectly.
If broadcasting works in multiply it must work in div operation. There are no excuses.
In my opinion this hot fix doesn't make any sense. Because it makes it work even slower than obvious workaround with 2 manuall calls.
We should never allow "fixes" like this. In order to unblock the issue we can simply call reciprocal and multiply manually.
It is a bug/issue in the binary op implementation where in one case div is treated ad chain of RECIP and MUL but when it goes broadcast way there is no support of it in both TTNN and kernel side. I expected you as an owner to drive this issue because it will require proper fixes in TTNN binary op.

Hi folks, we are hitting this issue in tt-mlir compiler so I just wanted to check with you what is the status of this issue and do you maybe have some estimate how long it will take to fix it?

The broadcasting generally is being fixed and will be delivered November 22, 2024.  Shortly afterwards we will look into how we support combining multiple operations for binary eltwise ops.  My expectation is currently the end of November for divide as it is a combination.

Keeping Priority label in sync with Priority field - P2

Hi @umadevimcw @eyonland I've noticed this has been moved to "In Progress", do you maybe have some estimate when you expect the fix to be in?


Omnisharp Sublime periodically uses up all memory

Sublime 3 and Omnisharp (installed from pkg manager) v1.9.6 after a while it uses gigabytes and I have to terminate it.
@DustinCampbell tells me it's using a very old version of Omnisharp. Is an update possible? Right now I can't practically use it.

Closing due to having outdated information.


UPSTREAM: : Add the upstream code rebase document

Description of your changes:
Create the upstream code rebase document, with the steps to upgrade Kubeflow Pipelines code with the Data Science Pipelines repository.
Checklist:

[X] The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 1 commits between a8fbbd2020d280f4cab31245a9639a350207b3f9...f5a03d13022b1e1ba3ba09129e840633982522ac

A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-76
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-76
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-76
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-76
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-76
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-76

An OCP cluster where you are logged in as cluster admin is required.
The Data Science Pipelines team recommends testing this using the Data Science Pipelines Operator.  Check here for more information on using the DSPO.
To use and deploy a DSP stack with these images (assuming the DSPO is deployed), first save the following YAML to a file named dspa.pr-76.yaml:
apiVersion: datasciencepipelinesapplications.opendatahub.io/v1alpha1
kind: DataSciencePipelinesApplication
metadata:
  name: pr-76
spec:
  dspVersion: v2
  apiServer:
    image: "quay.io/opendatahub/ds-pipelines-api-server:pr-76"
    argoDriverImage: "quay.io/opendatahub/ds-pipelines-driver:pr-76"
    argoLauncherImage: "quay.io/opendatahub/ds-pipelines-launcher:pr-76"
  persistenceAgent:
    image: "quay.io/opendatahub/ds-pipelines-persistenceagent:pr-76"
  scheduledWorkflow:
    image: "quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-76"
  mlmd:
    deploy: true  # Optional component
    grpc:
      image: "quay.io/opendatahub/mlmd-grpc-server:latest"
    envoy:
      image: "registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2"
  mlpipelineUI:
    deploy: true  # Optional component
    image: "quay.io/opendatahub/ds-pipelines-frontend:pr-76"
  objectStorage:
    minio:
      deploy: true
      image: 'quay.io/opendatahub/minio:RELEASE.2019-08-14T20-37-41Z-license-compliance'

Then run the following:
cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines.git
cd data-science-pipelines/
git fetch origin pull/76/head
git checkout -b pullrequest f5a03d13022b1e1ba3ba09129e840633982522ac
oc apply -f dspa.pr-76.yaml

More instructions here on how to deploy and test a Data Science Pipelines Application.

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 1 commits between a8fbbd2020d280f4cab31245a9639a350207b3f9...09d488109b1e5278677af9eeb05d5f4fa63774ce

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-76
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-76
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-76
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-76
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-76
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-76

/hold
Steps need change.

/unhold

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 1 commits between 0f96e42b1bd0968e898f6912a7b23f0a1285c6db...6c79f96c699c33f1c12f3124a3cbf0a3141f1661

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-76
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-76
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-76
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-76
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-76
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-76

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 1 commits between 0f96e42b1bd0968e898f6912a7b23f0a1285c6db...6c3fcd2ffb4471ac7b898e3b7176681cf60283cd

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-76
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-76
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-76
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-76
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-76
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-76

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 1 commits between 0f96e42b1bd0968e898f6912a7b23f0a1285c6db...96941d2b96471ca3c1dfaa865024b7701ea24a5e

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-76
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-76
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-76
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-76
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-76
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-76

content lgtm

This process this obviously very heavy-handed and destructive, and depends on there being no carries or downstream-only commits. We should adjust the procedure to account for this.

Didn't we decide we're going to do the rebase very differently next time and going forward? I recall that we agreed to not do the regular merge + merge conflict resolution (like we did this time) next time.
If that's correct, then I disagree with adding this document to this repository at all. This should just be a WIP google doc.

That wasn't my understanding, and we should keep doing the same process for next kfp upgrades. Anyway, I believe we can only confirm that when we upgrade to KFP 2.3.0, so let me know if I should keep this PR open until the next KFP upgrade or close it.

/lgtm

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between e27b68731776c35efe5e363295c3cc4a782cec4f...96941d2b96471ca3c1dfaa865024b7701ea24a5e


[Constraint solver] Type check captures as part of the constraint system

Rather than type-checking captures as separate declarations during
pre-check, generate constraints and apply solutions to captures in
the same manner as other pattern bindings within a constraint
system.
Fixes SR-3186 / rdar://problem/64647232.

@swift-ci please smoke test

@swift-ci please test source compatibility

@swift-ci smoke test macOS

@swift-ci test source compatibility Release


SystemView with AppTrace Lock does not work (IDFGH-1959)

This issue could be related to PlatformIO build, see analysis
Environment

Development Kit:      ESP32-DevKitC
Kit version: v4
Module or chip used:  ESP32-WROOM-32
IDF version (run git describe --tags to find it): 3.30300.190916
Build System:        PlatformIO
Compiler version 1.22.0-80-g6c4433a5
Operating System:     Windows
Power Supply:         USB
JTAG: Segger J-Link

Problem Description
Attempting to enable SystemView with CONFIG_ESP32_APPTRACE_LOCK_ENABLE results in the following errors:
(0) cpu_start: App cpu up.
(219) heap_init: Initializing. RAM available for dynamic allocation:
(226) heap_init: At 3FFAE6E0 len 0000F480 (61 KiB): DRAM
...
(257) cpu_start: Pro cpu start user code
assertion "res == coreID || res == portMUX_FREE_VAL" failed: file "portmux_impl.inc.h", line 105, function: vPortCPUAcquireMutexIntsDisabledInternal
abort() was called at PC 0x400d32e3 on core 0

where this section repeats and eventually resets:
assertion "res == coreID || res == portMUX_FREE_VAL" failed: file
"portmux_impl.inc.h", line 105, function: vPortCPUAcquireMutexIntsDisabledInternal

Expected Behavior
SystemView should work as described in the documentation.
Actual Behavior
SystemView can only be used when CONFIG_ESP32_APPTRACE_LOCK_ENABLE is 0
Steps to repropduce
Create a new project with one endless loop task and the following settings:
#define CONFIG_ESP32_APPTRACE_ENABLE 1
#define CONFIG_ESP32_APPTRACE_LOCK_ENABLE 1
#define CONFIG_SYSVIEW_ENABLE 1

//extras:
#define CONFIG_SYSVIEW_MAX_TASKS 15
#define CONFIG_FREERTOS_GENERATE_RUN_TIME_STATS 1
#define CONFIG_FREERTOS_USE_STATS_FORMATTING_FUNCTIONS 1
#define CONFIG_FREERTOS_USE_TRACE_FACILITY 1
#define CONFIG_ESP32_APPTRACE_POSTMORTEM_FLUSH_TRAX_THRESH 0
#define CONFIG_ESP32_APPTRACE_ONPANIC_HOST_FLUSH_TMO 10000
#define CONFIG_ESP32_APPTRACE_POSTMORTEM_FLUSH_THRESH 1
#define CONFIG_ESP32_APPTRACE_PENDING_DATA_SIZE_MAX 1024
#define CONFIG_ESP32_APPTRACE_DEST_TRAX 1
#define CONFIG_ESP32_DEBUG_STUBS_ENABLE 1
#define CONFIG_SYSVIEW_TS_SOURCE_ESP_TIMER 1
#define CONFIG_ESP32_TRAX 1
#define CONFIG_ESP32_TRAX_TWOBANKS 1

Analysis
At first it looked like the issue is in start_cpu0_default() where esp_apptrace_init() is not called at the correct location, but even after moving it above esp_timer_init() a different error started, I think the lock might not get released in the trax code so its causing other side effects, but I did not finish the analysis.
After disabling the AppTrace locks it seems to be working.
This issue could be related to the way PlatformIO builds esp-idf or a regression in AppTrace / SystemView implementation or inappropriate defines.

@drorgl CONFIG_ESP32_APPTRACE_LOCK_ENABLE is incompatible with SystemView tracing module and should be disabled.
SystemView uses its own locking mechanism.

@gerekon  I was a bit suspicious when I saw SystemView locks, thanks for clearing it up!


how to load npm module from ts_devserver with fine grained deps

say we setup the project like this:
.
├── BUILD.bazel
├── WORKSPACE
├── package.json
├── src
│   ├── BUILD.bazel
│   ├── index.html
│   └── index.ts
├── tsconfig.json
└── yarn.lock

src/BUILD.bazel:
package(default_visibility = ["//visibility:public"])

load("@build_bazel_rules_typescript//:defs.bzl", "ts_devserver", "ts_library")

ts_library(
    name = "ts_example",
    srcs = [
        "index.ts",
    ],
    deps = [
        "@npm//@types/lodash",
        "@npm//lodash",
    ],
)

ts_devserver(
    name = "devserver",
    entry_module = "bazel_ts_example/src/index",
    serving_path = "/bundle.min.js",
    static_files = [
        "index.html",
    ],
    deps = [
        ":ts_example",
    ],
)

src/index.ts
import { sample } from "lodash";
document.body.innerHTML = sample(['foo','bar'])!;

the bundle.min.js requests lodash from the server root path which will certainly fail.

I have the same problem. Please, do something about it.

@wayou Did you get it to work?
not yet.

Just need to include target @npm//node_modules/lodash:lodash__umd in the ts_devserver#deps
Behind the scenes, this uses browserify to create an UMD version of lodash which can be bundled in along with your sources.

https://github.com/alexeagle/repro_ts_310 shows how it works

Thank you very much. It's a super important issue for me.


chore(master): release 1.7.1

:robot: I have created a release beep boop
1.7.1 (2022-10-10)
Bug Fixes

修正types提示错误 (ef3e006)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/kailong321200875/vue-element-plus-admin/releases/tag/v1.7.1 :sunflower:


Enforce Event bus restrictions at register time.

What
Enforce event bus restrictions when a subscriber is being registered to the bus.
Why
Enforcing the event bus restrictions when registering means the IllegalAccessException thrown
when attempting to invoke a method on the subscriber should not occur during normal operation, so it becomes safe to throw a RuntimeException when an IllegalAccessException is caught.
How
Make sure subscribing instances conform to the following restrictions when the register method is
called or throw an IllegalArgumentException.

Subscriber class must be public
Methods with the @Subscribe annotation must be public.
Method with the @Subscribe annotation must have only one parameter.

Note: Previously the method and subscriber only needed to be visible to the EventBus class, this
has now been restricted to enforce public access for the subscription method and subscription class. This makes it easier to perform validation if
Testing
New tests added to the EventBusTest which test exception cases.

@rhyshort I think the 1 remaining change on this is to add the Notification type to the event.md documentation.

@ricellis done in 50f4317


LAB06_EX1: Create analytics rule

Contact Details
<EMAIL_ADDRESS>What happened?
Exercise : Lab6 01
Task: 02
Step: 08
Description of issue:
When I checked, "Create incidents - Recommended!" was greyed out and not selectable.
Therefore, I manually created the "Create incidents based on Microsoft Defender for Cloud" rule for the analysis rule.
Repro steps:
Select the "✖" in the upper right to close.
Select Analytics from the navigation menu.
Select "Create incidents based on Microsoft Defender for Cloud" from the rule templates.
Select Create rule in the connector information blade.
In the Analytics rule wizard, select Next: Automated response, Next: Review and create, save.
Lab
Lab 06 Exercise 01 Connect data to Microsoft Sentinel using data connectors
Relevant screenshots
paste here 😉
Do you want to help us? 👏

[ ] Create a Pull Requestt by following this project's Contribution Guide

Fixed in PR.


Fixed link to self hosting docs in readme.

The old link goes to an unused url.

thank you @Jeroenvb3!


vite cannot import react component from a workspace package

Describe the bug
I am trying to import a Button component from a workspace package shared-ui from a vite react app but i am getting 'Button' is not exported by ../shared-ui/dist/index.js, imported by src/App.tsx error.
Reproduction
https://github.com/unworthyEnzyme/react-monorepo
Steps to reproduce
To reproduce clone this repository and npm install and then run npx nx build my-vite-app.
I thought maybe i was doing something wrong and created a react app with create-react-app and if you npx nx build my-app you can see there are no errors.
System Info
Windows 10
Node v18.0
npm 8.6.0

Used Package Manager
npm
Logs
'Button' is not exported by ../shared-ui/dist/index.js, imported by src/App.tsx
file: C:/Users/asus/Desktop/package-based/packages/my-vite-app/src/App.tsx:1:9
1: import { Button } from 'shared-ui';
^
2: function App() {
3:   return (
error during build:
Error: 'Button' is not exported by ../shared-ui/dist/index.js, imported by src/App.tsx
at error (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:1858:30)
at Module.error (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:12429:16)
at Module.traceVariable (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:12788:29)
at ModuleScope.findVariable (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:11440:39)
at FunctionScope.findVariable (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:6372:38)
at ChildScope.findVariable (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:6372:38)
at Identifier.bind (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:7439:40)
at CallExpression.bind (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:5265:73)
at CallExpression.bind (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:8935:15)
at Property.bind (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:5269:23)
at ObjectExpression.bind (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:5265:73)
at CallExpression.bind (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:5265:73)
at CallExpression.bind (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:8935:15)
at ReturnStatement.bind (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:5269:23)
at BlockStatement.bind (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:5265:73)
at FunctionDeclaration.bind (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:5269:23)
at Program.bind (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:5265:73)
at Module.bindReferences (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:12425:18)
at Graph.sortModules (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:23062:20)
at Graph.build (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:22940:14)
at async file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:23730:13
at async rollupInternal (file:///C:/Users/asus/Desktop/package-based/node_modules/rollup/dist/es/shared/rollup.js:23727:5)
at async doBuild (file:///C:/Users/asus/Desktop/package-based/node_modules/vite/dist/node/chunks/dep-51c4f80a.js:45395:24)
at async build (file:///C:/Users/asus/Desktop/package-based/node_modules/vite/dist/node/chunks/dep-51c4f80a.js:45233:16)
at async CAC. (file:///C:/Users/asus/Desktop/package-based/node_modules/vite/dist/node/cli.js:756:9)
Validations

[x] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[ ] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Yup shared-ui needs to build out as ESM in order to work. Otherwise you have to add shared-ui to optimizeDeps.include to optimize the CJS -> ESM, but you won't get HMR when updating the components. https://vitejs.dev/guide/dep-pre-bundling.html#monorepos-and-linked-dependencies

Vite treat all modules as ES6 modules. However the shared-ui dist uses a commonjs export, not the es6 exports. Let typescript compile to es6 js can solve the problem.

// packages/shared-ui/tsconfig.json

{

  "compilerOptions": {

-   "module": "commonjs",

+   "moduleResolution": "Node", // for tsc types resolve

+   "module": "ES6", // export as ES6 module for vite resolve

+   "target": "ES6", // transform to ES6 code for vite resolve

  }

}

Then Vite may successfully resolve { Button } from dist/index.js
I also suggest building shared ui by Vite library mode

This worked perfectly thank you.

Indeed, it is defined like another dependency in the package.json and it's present in the node_modules folder. Do Vite knows that it's a monorepo package ?
More globally, how Vite recognise a CommonJS dependency and when do he decides to convert it ?

How Vite recognizes a dep should not be optimized by default is by checking if the path to it contains a /node_modules/ string. When you link the dep in a monorepo, you'll see the dep in node_modules, but the realpath points to a path that doesn't contain /node_modules/ (the path in your monorepo). So Vite doesn't optimize it.
Vite doesn't check if a dep is a CJS dep though, the above is probably the only special check it does.

Thanks for your answer, just not sure to understand when you say

checking if the path to it contains a /node_modules/ string

I'm not sure to understand exactly how the resolution is made though. Would it be possible to get an example please?

When you import 'shared-ui', Vite needs to resolve shared-ui to an actual file in your file system to load it. If that path doesn't include the /node_modules/ string, it's a linked package, e.g. /Users/bjorn/projects/my-linked-dep/index.js.
When using a monorepo that links packages up, you get a path like above so Vite can know it's a linked dep. About realpath, you can check out the nodejs docs. Because linking creates a symlink, you could be initially referring to /Users/bjorn/projects/my-project/node_modules/my-linked-dep/index.js. Calling realpath returns the actual file which is /Users/bjorn/projects/my-linked-dep/index.js.

Understood! Thanks for the clarification


Ternary Search in Kotlin

🚀Proposal
Ternary search is a type of searching technique, which is used to find an element of an array.
Have you read the Contributing Guidelines on Pull Requests?
Yes, I have read the contributing guidelines.
Motivation
I am participating in GSSoC'21, so I want to contribute to this project. Apart from this, I found this repository very knowledgeable, consisting data structures and algorithms of different programming languages.
Pitch
Ternary search is based on divide and conquer algorithm. In ternary search, we divide the array into 3 parts and used to determine which part of the array consists of the element to be found. It has time complexity better than linear search or binary search which is the main advantage of this algorithm.
I would like to implement ternary search using Kotlin programming language, with proper comments.
So, I request you to kindly assign this issue to me.

/assign


Smart TV support

Hi,
Do you have a plan to support smart tv?

None at all
You'd have to provide context to how it would be used on a smart tv.

I think the usecase is trivial:
I have #X SmartTVs where I want to show some static website on TVs' startup...
Anyway, do you mind if I make the modifications and publish a new app based on your code? (including the about_html of course)

Feel free to have a go, if it can be done as pull request so that both phone/tablet and TV versions can live in the same repo then all the better then there is only one place that needs updating in the furture


Concatenate records split because of the size into only one record

Logging records above a certain size (8k using CRI-O for instance) get split and "partial" records, that ultimately fail to be parsed once sent to the "Log Source" since it contains just part of the "full" record.
Using the CRI-O case as an example, the use of the already existing concat filter is recommended to concatenate the records in one single entry.
Please update the logging ConfigMaps accordingly to support this feature.

hi @edinardo,
Thanks for reaching out to us. Could you explain in detail what context of log(s) you are referring to ? For the Oracle defined configuration (for various Kubernetes System/Service logs) we are already using Concat plugin where applicable except for "Generic Container Logs". We can not use Concat plugin here as we will not be having context of log pattern (single line vs multi line, multi line start expression etc.,).
However, we have given the control to the users to modify/customise the configuration according to their needs using customLogs section. Please refer this section of README for details.

Let's use containers running on CRI-O as an example. If you have a single record with more than 8192 bytes, CRI-O will split the record into more than one line in the file. Once that file/record is read by Fluentd, the cri parser will split into multiple records like:
time: 2020-10-10 09:10:00.333333333Z
record: {"stream":"stdout","logtag":"P","message":"This is first record contains 8192 bytes ...","time":"2020-10-10T00:10:00.333333333Z"}

time: 2020-10-10 09:11:00.333333333Z
record: {"stream":"stdout","logtag":"F","message":"... this is the record with the content after 8192 bytes","time":"2020-10-10T00:11:00.333333333Z"}

These records need to be concatenated into one record before getting processed by another filter down in the pipeline. This can be achieved using @type concat filter plugin with use_partial_cri_logtag parameter.

Got it. We are talking about only for the part of handling partial log messages here. We will fix it.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 203 ms

Resolved: ClamAV performance has improved in 7033758.


feat: allow for aliasing icons

Description
Allows for aliases to be defined as:
{
  "chevron-left": "ri:arrow-left-s-line",
  "chevron-up": "ri:arrow-up-s-line",
  "chevron-right": "ri:arrow-right-s-line",
  "chevron-down": "ri:arrow-down-s-line",
  // ...
}

Aliases can either be defined in the settings.json or (inclusive) in linked JSON files.
Additionally, users can opt-in to ignoring unaliased icons.
Linked Issues
fix #58
Additional context
Adds options:

customAliases
customAliasesJsonPaths
customAliasesOnly

@antfu Sorry for the ping, I know you must be busy; just didn't want this to be forgotten about.

I am not sure if it's necessary to introduce so many options. Also, I think manually listing all icons one to one might be a scalable solution. I think we should better have a more generalized design.

I am not sure if it's necessary to introduce so many options.

customAliases probably isn't needed as I'd imagine everyone would rather use customAliasesJsonPaths, so I'll remove it.
customAliasesOnly could probably also be removed, but I thought I'd add it for those that want to use it as an extra step of visual validation that they are using allowed icons (in the case where all allowed icons are aliased). Would you like me to remove this one too?

listing all icons one to one might be a scalable solution

I assume you meant "might not be a scalable solution".
Listing all icons one to one is what my use case calls for so I would like to have this option. Also there's already the customCollectionIdsMap for aliasing full collections.


Cannot read properties of undefined (reading 'name')

ITS portal on testnet returns an error. To reproduce this, open https://testnet.interchain.axelar.dev/filecoin-2/0x16f9D9EABC2826333936e648Ea5A2437f381A59B

fixed with this merge: https://github.com/axelarnetwork/axelarjs/commit/f6855e34aed7c1945257ba47a49f5a22b4e382bf


feat: integrating PanelApp download for annonars (#79)

Download is here, import of annonars is pending https://github.com/bihealth/annonars/issues/225.


Add a few missing server settings and sort the list

Fixes #5093

added sched spread in another PR, so I'll close this one for now since the others aren't urgent to expose.


GH-4403: Migrate WireMock tests to JUnit 5

GitHub issue resolved: #4403
Briefly describe the changes proposed in this PR:
This migrates WireMock tests to JUnit 5 using the documented approach: https://wiremock.org/docs/junit-jupiter/.
Also upgrading WireMock to latest stable version to make the JUnit 5 integration available.

PR Author Checklist (see the contributor guidelines for more details):

[x] my pull request is self-contained
[ ] I've added tests for the changes I made
[x] I've applied code formatting (you can use mvn process-resources to format from the command line)
[x] I've squashed my commits where necessary
[x] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

I think that maybe this should be targeted at develop instead of main since it's not strictly a bug fix.

I think that maybe this should be targeted at develop instead of main since it's not strictly a bug fix.

This one doesn't touch any production/release code though, so arguably it can fit in either. But given that the other PR touches the testsuites, which are released artifacts, it might be good for consistency sake to merge all JUnit 5 stuff to develop instead of main.


Update python dependencies (security: requests)

requests update is not available yet due to toil constraint
  Collecting requests<=2.31.0 (from toil[aws,cwl,encryption,google,mesos]->-r requirements.in (line 7))
    Using cached requests-2.31.0-py3-none-any.whl.metadata (4.6 kB)

https://github.com/DataBiosphere/toil/blob/f237192ece8af88a107c55aa2ee8a2279a5a4e71/requirements.txt#L2
https://github.com/DataBiosphere/toil/pull/4943

Looks like we need to accept the risk for now.  Toil isn't merging the update to requests.


Replace @ngaox/seo library with something else

It's forcing use of --legacy-peer-deps given requires Angular v15 as peer dep. But app is using Angular v16 and soon will be v17. Which is a PIA. When using npm, bun doesn't care.
There's probably a more updated / popular dependency for metadata. We need:

Set the page title
Set the page description
Set Open Graph metadata
Set Twitter card metadata
Set extra metadata (keywords, author, ...)

Done, replaced by https://ngx-meta.dev/


Fix code error

The number between parenthesis in visual basic isn't the size of the array, it's the maximum index ( size - 1 )

@rpetrusha, I haven't tested from an IDE, but why not make CompareResult shared and use Module instead of Class ?

I noticed that the visual basic code uses args(1) and args(2), is it a mistake ? @rpetrusha

If you'd like to use Module...End Module, @Youssef1313, that's fine. It's even preferable.
In terms of the args array, args(0) is the executable, args(1) is the first argument, and args(2) is the second. So the code is correct.

I've used Module in vb and static class in c#.

In terms of the args array, args(0) is the executable, args(1) is the first argument, and args(2) is the second. So the code is correct.

I haven't tested myself, but then I think the following suggested change might have been wrong ?
https://github.com/dotnet/samples/pull/1169#pullrequestreview-276637215

Thanks for making the changes, @Youssef1313. I've made one additional change -- the Shared keyword cannot be used with a method (in this case the Main method) for a Visual Basic module; all members are implicitly Shared. I'll merge your PR now.


New disease Term overgrowth syndrome w/or without cerebral malformations[NTR]

Preferred term label:
Overgrowth syndrome w/or without cerebral malformations
Synonyms
Definition (free text, please give PubMed ID, if applicable, in format PMID:#######)
This disorder term will be used for several genes within the MTOR pathway (MTOR, PIK3CA, PIK3R2, AKT3). These genes result in very similar overlapping phenotypes which are often indistinguishable. Depending on where the somatic mutation occurs it can result in overgrowth in the brain or of a single limb or multiple limbs. Many of the diseases listed in OMIM under these genes are actually a spectrum of mosaicism. (PMID: 30197175, 28969385).
*Parent term (use OLS, or your favorite ontology browser)
Congenital Abnormality
Developmental abnormality during embryogenesis
overgrowth/obesity syndrome
Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?
Your nano-attribution (ORCID)
Brain Malformation Curation Expert Panel

@abbe-Lai

Many of the diseases listed in OMIM under these genes are actually a spectrum of mosaicism.

Should any of these OMIM terms be a child of this term?

@abbe-Lai following up, please let me know if the proposed label and definition above look okay, whenever you have a chance. Thanks!

Hello,
We have come up with a new idea! Should I submit it in a new github ticket? The majority of our panel members have decided that a single term would be sufficient.
Best,
Abbe Lai
From: Nicole Vasilevsky<EMAIL_ADDRESS>Reply-To: monarch-initiative/mondo<EMAIL_ADDRESS>Date: Monday, November 16, 2020 at 8:45 PM
To: monarch-initiative/mondo<EMAIL_ADDRESS>Cc: "Lai, Abbe"<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [monarch-initiative/mondo] New disease Term overgrowth syndrome w/or without cerebral malformations[NTR] (#1830) [EXTERNAL]

External Email - Caution *

@abbe-Laihttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_abbe-2DLai&d=DwMCaQ&c=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU&r=KR5yAFgzBYcGok2X41Irv5_RYq6gTQUTB2ejIsIeaF4&m=gSw6l76hnY6C_qLKz7k9EoLUJt7dReW_uVvBxmgsyt0&s=-8NXMiP53fcj1kWKK-6QCV_8cq1yO9tuFv07qeOKfXE&e= following up, please let me know if the proposed label and definition above look okay, whenever you have a chance. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_monarch-2Dinitiative_mondo_issues_1830-23issuecomment-2D728631783&d=DwMCaQ&c=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU&r=KR5yAFgzBYcGok2X41Irv5_RYq6gTQUTB2ejIsIeaF4&m=gSw6l76hnY6C_qLKz7k9EoLUJt7dReW_uVvBxmgsyt0&s=VTyV2byoMzWdp52zf8OY3Kr7FOIH8saXw4kerYK3pnA&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AO5W5QH5KJIEUB6FGNCY2QLSQHISFANCNFSM4PJMGJUQ&d=DwMCaQ&c=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU&r=KR5yAFgzBYcGok2X41Irv5_RYq6gTQUTB2ejIsIeaF4&m=gSw6l76hnY6C_qLKz7k9EoLUJt7dReW_uVvBxmgsyt0&s=uijczyQgMmzEI7BwMk2eLs7eZnTo3S81flQIhBGJjTE&e=.

Great - a new ticket is great, I'll close this one, thanks!


[Search Documents] Migrating search-documents to the new recorder

Packages impacted by this PR
search-documents
Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/19859
Describe the problem that is addressed by this PR
Migrating search-documents to the new recorder
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
N/A
Are there test cases added in this PR? (If not, why?)
N/A
Provide a list of related PRs (if any)
N/A
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

What do you think about doing al recorder start and setup inside createClient? Maybe it can take the recorder as parameter

Sounds good

Spoke with Harsha offline. Changes look good. Approving it


Two different interfaces on Pathvector

Hi, I have here a use case which doesn't seen to be covered by pathvector currently, and I want to confirm that.
I have two different interfaces: One for IX and one for a direct transit. On pathvector.yml I need to configure both source4 and source6 but they differ between the interfaces from IX and Transit.
Does pathvector has some way to deal with that?
Thanks

I made a PR for that ages ago (https://github.com/natesales/pathvector/pull/227) to add interface into the config, if that is what you are looking for.


Cost matrix: distance dependent cost

This PR changes the The histogram format and cost function completely. Here a few points that changed:

The histogram is now stored as an Eigen::Matrix
The histogram now contains only a distance and age layer, the binary is dropped
The cost of each histogram cell is stored in a cost matrix
A new cost-function is used, which contains the obstacle distance in the cost value
To smooth the cost matrix (former safety radius) the matrix is padded (wrapping correctly around elevation and azimuth). and then a max median filter is used on it.
A lot of tests for the new functions

We definitely have to flight test this before merging. It might fly a bit worse than before, as I did not yet spend too much time on re-tuning the costmatrix smoothing and costfunction.

Based on SITL testing I'm getting occasional tree hits, here's the flight plan I'm using. It is either hitting immediately after takeoff or just before waypoint 5.
test_mission.zip

@jkflying with the new tuning I managed to fly the mission you provided in most of the runs. The only critical situation is still before waypoint 5. If the drone steers directly into the hole in the tree, it will see the obstacle only when it is already in a concave gap. But this is a corner case which I think we should look into another time (also I pretty sure master won't be able to handle it either).

I will leave this open until we confirmed SITL results through flight testing

We flew successful flight tests. Big improvement in terms of safety, a nice distance to the tree is kept at all times. Regression in terms of speed, the drone stopped in front of the tree and took a while to decide which way to go. This problem will be treated in next PR.


Inline docs for can.Component cleanup

@retro any chance you are going to get to this?  Otherwise, please close.

We are planning to go through all inline docs and code organization for 3.0.


Travis CI failed with Node v4, 0.12, 0.10

Travis fails to build my repo with Node versions v4, 0.12, 0.10, while it passes with 5
Build system information
Build language: node_js
Build group: stable
Build dist: precise
Build image provisioning date and time
Thu Feb  5 15:09:33 UTC 2015
Operating System Details
Distributor ID:	Ubuntu
Description:	Ubuntu 12.04.5 LTS
Release:	12.04
Codename:	precise
Linux Version
3.13.0-29-generic
Cookbooks Version
a68419e https://github.com/travis-ci/travis-cookbooks/tree/a68419e
GCC version
gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
LLVM version
clang version 3.4 (tags/RELEASE_34/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
Pre-installed Ruby versions
ruby-1.9.3-p551
Pre-installed Node.js versions
v0.10.36
Pre-installed Go versions
1.4.1
Redis version
redis-server 2.8.19
riak version
2.0.2
MongoDB version
MongoDB 2.4.12
CouchDB version
couchdb 1.6.1
Neo4j version
1.9.4
RabbitMQ Version
3.4.3
ElasticSearch version
1.4.0
Installed Sphinx versions
2.0.10
2.1.9
2.2.6
Default Sphinx version
2.2.6
Installed Firefox version
firefox 31.0esr
PhantomJS version
1.9.8
ant -version
Apache Ant(TM) version 1.8.2 compiled on December 3 2011
mvn -version
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T17:29:23+00:00)
Maven home: /usr/local/maven
Java version: 1.7.0_76, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-oracle/jre
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux", version: "3.13.0-29-generic", arch: "amd64", family: "unix"
git.checkout
0.38s$ git clone --depth=50 --branch=master https://github.com/kbariotis/wsmanager.git kbariotis/wsmanager
Cloning into 'kbariotis/wsmanager'...
remote: Counting objects: 29, done.
remote: Compressing objects: 100% (20/20), done.
remote: Total 29 (delta 8), reused 27 (delta 6), pack-reused 0
Unpacking objects: 100% (29/29), done.
Checking connectivity... done.
$ cd kbariotis/wsmanager
$ git checkout -qf 190666d452eaa7102039465ac3fb72244d4e3a35
This job is running on container-based infrastructure, which does not allow use of 'sudo', setuid and setguid executables.
If you require sudo, add 'sudo: required' to your .travis.yml
See http://docs.travis-ci.com/user/workers/container-based-infrastructure/ for details.
4.35s$ nvm install v4
######################################################################## 100.0%
Checksums empty
Now using node v4.2.3
$ node --version
v4.2.3
$ npm --version
2.14.7
$ nvm --version
0.23.3
116.94s$ npm install
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>><EMAIL_ADDRESS>prepublish /home/travis/build/kbariotis/wsmanager
> npm run build -s
Success! All dependencies used in the code are listed in package.json
src/index.js -> dist/index.js
events.js:197
    throw new TypeError('listener must be a function');
    ^
TypeError: listener must be a function
    at SocketManager.addListener (events.js:197:11)
    at new SocketManager (index.js:12:10)
    at Object.<anonymous> (index.js:117:16)
    at Module._compile (module.js:435:26)
    at loader (/home/travis/build/kbariotis/wsmanager/node_modules/babel-cli/node_modules/babel-register/lib/node.js:130:5)
    at Object.require.extensions.(anonymous function) [as .js] (/home/travis/build/kbariotis/wsmanager/node_modules/babel-cli/node_modules/babel-register/lib/node.js:140:7)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
npm ERR! Linux 3.13.0-40-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v4.2.3/bin/node" "/home/travis/.nvm/versions/node/v4.2.3/bin/npm" "install"
npm ERR! node v4.2.3
npm ERR! npm  v2.14.7
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepublish: `npm run build -s`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script 'npm run build -s'.
npm ERR! This is most likely a problem with the wsmanager package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build -s
npm ERR! You can get their info via:
npm ERR!     npm owner ls wsmanager
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/kbariotis/wsmanager/npm-debug.log
The command "eval npm install " failed. Retrying, 2 of 3.
><EMAIL_ADDRESS>prepublish /home/travis/build/kbariotis/wsmanager
> npm run build -s
Success! All dependencies used in the code are listed in package.json
src/index.js -> dist/index.js
events.js:197
    throw new TypeError('listener must be a function');
    ^
TypeError: listener must be a function
    at SocketManager.addListener (events.js:197:11)
    at new SocketManager (index.js:12:10)
    at Object.<anonymous> (index.js:117:16)
    at Module._compile (module.js:435:26)
    at loader (/home/travis/build/kbariotis/wsmanager/node_modules/babel-cli/node_modules/babel-register/lib/node.js:130:5)
    at Object.require.extensions.(anonymous function) [as .js] (/home/travis/build/kbariotis/wsmanager/node_modules/babel-cli/node_modules/babel-register/lib/node.js:140:7)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
npm ERR! Linux 3.13.0-40-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v4.2.3/bin/node" "/home/travis/.nvm/versions/node/v4.2.3/bin/npm" "install"
npm ERR! node v4.2.3
npm ERR! npm  v2.14.7
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepublish: `npm run build -s`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script 'npm run build -s'.
npm ERR! This is most likely a problem with the wsmanager package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build -s
npm ERR! You can get their info via:
npm ERR!     npm owner ls wsmanager
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/kbariotis/wsmanager/npm-debug.log
The command "eval npm install " failed. Retrying, 3 of 3.
><EMAIL_ADDRESS>prepublish /home/travis/build/kbariotis/wsmanager
> npm run build -s
Success! All dependencies used in the code are listed in package.json
src/index.js -> dist/index.js
events.js:197
    throw new TypeError('listener must be a function');
    ^
TypeError: listener must be a function
    at SocketManager.addListener (events.js:197:11)
    at new SocketManager (index.js:12:10)
    at Object.<anonymous> (index.js:117:16)
    at Module._compile (module.js:435:26)
    at loader (/home/travis/build/kbariotis/wsmanager/node_modules/babel-cli/node_modules/babel-register/lib/node.js:130:5)
    at Object.require.extensions.(anonymous function) [as .js] (/home/travis/build/kbariotis/wsmanager/node_modules/babel-cli/node_modules/babel-register/lib/node.js:140:7)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
npm ERR! Linux 3.13.0-40-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v4.2.3/bin/node" "/home/travis/.nvm/versions/node/v4.2.3/bin/npm" "install"
npm ERR! node v4.2.3
npm ERR! npm  v2.14.7
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepublish: `npm run build -s`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script 'npm run build -s'.
npm ERR! This is most likely a problem with the wsmanager package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build -s
npm ERR! You can get their info via:
npm ERR!     npm owner ls wsmanager
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/kbariotis/wsmanager/npm-debug.log
The command "eval npm install " failed 3 times.
The command "npm install " failed and exited with 1 during .
Your build has been stopped.

hmm, it seems there is something wrong with my use of EventEmitter class.
sorry about that. :)

No problem :+1:


[proposal] merge into dash-core-components

I think quite some people are not happy with the standard dcc.Upload component as it simply does not work with large files and causes the entire app to crash.
You component looks very robust now and thus I would propose to start the discussion at github.com/plotly/dash whether they want to include your component...

Thanks for the suggestions. That is valid point. The dcc.Upload really needs an alternative for large files, and that was my motivation for forking the dash-resumable-upload and trying to make it easily accessible for anyone.
Merging into dash-core-components or similar has it's pros and cons. Maybe it would be good to discuss about the possibility. Perhaps the plotly community forum is the best place to open a discussion? Or GitHub page of dcc?

I think it is a good idea, we should be able to have a capable upload component right out of the box...
Hey @alexcjohnson , what do you think about that?

Thanks for the ping @GitHunter0! I haven't used dash-uploader myself but it looks great - I know we've heard frustrations with dcc.Upload, and I agree that it's pretty basic. So yes, I wholeheartedly support the idea of bringing this into dcc (you're probably all aware but please note this is part of the main dash repo now). Would also take care of #122 😎
A couple of things to note:

Not 100% clear to me whether this should be a flavor of dcc.Upload or a new component. There's a decent amount of overlap between the two use cases but also some important differences. For instance a lot of dcc.Upload use cases never intend to save the files, they're just uploading data to be analyzed during the user's session.
There's a lot of really cool functionality in here! I suspect though that we can make some of it into more standard Dash usage, like could du.callback be a regular dash.callback?
The bundle is fairly large for this component, which means when this is included in dcc it should be done as an async chunk.

@alexcjohnson , I really appreciate your willingness to incorporate dash-uploader, it is a very important component for many use-cases, so the merger would be a relief.

Not 100% clear to me whether this should be a flavor of dcc.Upload or a new component.

Yes, keeping them separately might be a good idea, each one with its own features.

like could du.callback be a regular dash.callback

Also a good call, du.callback() can be confusing for the beginning users.

Hi @alexcjohnson , are you folks still considering incorporating dash-uploader ? This is something that I'm really hoping for.

cc @gvwilson @ndrezn


Fix ci error comments

Objective

Fix a few errors on the workflow for leaving comments after ci failures

bors r+


Customers can now configure clustering on their ZR caches

@lasingam : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Arlonctl - Register/unregister Git

As a user of Arlon I would like the CLI to have a dedicated commnad for registering and unregistering the Git repo where my Porfiles will be written.
So that i do not need to manually place the Profile and Git and manually generate the path that Arlon will use during the Cluster Create command.
It would also be good if I could specify which repository should be used for deploying clusters and their related ArgoCD elements, VS which repositories are used for storing the Bundle, Profile and ClusterSpec data.
This is especially important when we start supporting #54 Cloned Clusters as the entire contents stored in Git will be duplicated.

We need to make it very clear how Git Authentication and authorization is handled. right now its not clear.

Aren't we planning to get rid of the git workspace repository in 0.9? cc: @bcle

According to the recent replanning, the current plan for 0.9.x is to use next-gen clusters with current-gen profiles. So the user still needs to supply a repo for storing dynamic profiles. Also, the base cluster itself needs to be in a repo that arlon can read/write (for the prep phase).

We need to make it very clear how Git Authentication and authorization is handled. right now its not clear.
Currently, the readme asks to set environment variables for $WORKSPACE_REPO and $ARLON_REPO and set these to the paths where these repositories have been checked out.

I just wanted to add that we were thinking of using this to verify the user permissions for a particular repo: We were thinking of using this : https://docs.github.com/en/rest/collaborators/collaborators#get-repository-permissions-for-a-user


deprecated APIs use on Android 15

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
There has been a report from Google:
Your app uses deprecated APIs or parameters for edge-to-edge
One or more of the APIs you use or parameters that you set for edge-to-edge and window display have been deprecated in Android 15. Your app uses the following deprecated APIs or parameters:

android.view.Window.setStatusBarColor
android.view.Window.setNavigationBarColor

These start in the following places:

com.google.android.material.bottomsheet.a.onCreate
m61.a

Expected Behavior
There is no deprecated APIs being used
Steps with code example to reproduce
No need of code example
Stacktrace/Logs
No need of stacktrace
Flutter version
v3.24.4
Operating System, Device-specific and/or Tool
Android 15
Plugin version
v6.1.5
Additional information
No response
Self grab

[ ] I'm ready to work on this issue!

Any fix yet?

As you can see, this is not caused by the plugin, but com.google.android.material.bottomsheet that is not used by this plugin.
Probably, you need to update the https://inappwebview.dev/docs/intro#enable-material-components-for-android component dependency.

@samueldubovec-embedit @vinaykharayat
I facing same issue.
Have you any update for this?

android.view.Window.setDecorFitsSystemWindows
android.view.Window.setStatusBarColor
android.view.Window.setNavigationBarColor
android.view.Window.setNavigationBarDividerColor

These start in the following places:

com.google.android.material.internal.c.a
io.flutter.embedding.android.g.I
io.flutter.plugin.platform.d.a
io.flutter.plugin.platform.h.C


Issue with Text Selection Background Color on iOS Browsers

Description:
This plugin works quite well on desktop. However, when selecting text in iOS browsers, the background color of the selected text changes to gray. Is there an easy fix for this issue?

You can remove caret-color: transparent; on iOS.


Upgrade to Tailwind CSS 3.0

According to the upgrade guide, I don't think this should require a lot of code changes. We are already using the JIT engine and not many customizations. Most of the changes might be the new class names.

Closed via #169.


NCTL :: further enhancements

New commands to view rpc schema/endpoint.
Updated erc20 commands.
Updated docs.
New composite commands to join/leave.

bors r+

bors r+


[QUARKS-88] [WIP] Add Apache licence headers to source files

I've checked with this command.
Cazens-MacBook-Pro:incubator-quarks Cazen$ find . -not -path '*/\.*' \
> -not -name "*.jar"   \
> -not -name "*.class" \
> -not -name "*.iml"   \
> -not -name "NOTICE"  \
> -not -name "README"  \
> -not -name "*.md"    \
> -not -name "*.json"  \
> -not -name "*.css"   \
> -not -name "*.png"   \
> -not -name "*.js"    \
> | xargs grep -L "http://www.apache.org/licenses/LICENSE-2.0" 2> /dev/null
./analytics/math3/ext/commons-math3-3.4.1/NOTICE.txt
./connectors/javax.websocket-client/src/main/resources/META-INF/services/quarks.javax.websocket.QuarksSslContainerProvider
./connectors/wsclient-javax.websocket/src/test/keystores/clientKeyStore.jks
./connectors/wsclient-javax.websocket/src/test/keystores/clientTrustStore.jks
./connectors/wsclient-javax.websocket/src/test/keystores/serverKeyStore.jks
./connectors/wsclient-javax.websocket/src/test/keystores/serverTrustStore.jks
./console/servlets/webapp_content/html/index.html
./console/servlets/webapp_content/js/ext/d3.BSD.LICENSE
./console/servlets/webapp_content/js/ext/jquery-ui-1.11.4.custom/jquery-ui.LICENSE
./console/servlets/webapp_content/js/ext/jquery-ui-1.11.4.custom/jquery.LICENSE
./console/servlets/webapp_content/js/ext/sankey.d3.BSD.LICENSE
./console/servlets/webapp_content/WEB-INF/console.xml
./ext/slf4j-1.7.12/LICENSE.txt
./KEYS
./quarks_overview.html
./samples/apps/src/main/java/quarks/samples/apps/applicationTemplate.properties
./scripts/apps/sensorAnalytics/sensorAnalytics.properties
./scripts/connectors/iotf/device.cfg
./scripts/connectors/jdbc/jdbc.properties
./scripts/connectors/jdbc/persondata.txt
./scripts/connectors/kafka/kafka.properties
./scripts/connectors/mqtt/mqtt.properties
Cazens-MacBook-Pro:incubator-quarks Cazen$

Nice, just to note the list of files in the description is the files without the licence header, I initially thought it was the files that were changed.

In the list without the only one I would expect to have the header is:
quarks_overview.html

Good Day @ddebrunner Thank you for detail review.

Yes. The list above are files that does not include Apache License
I thought "quarks_overview.html" file is snippet style(It start with just BODY tag. Not HTML tag) to assemble into another HEADER(license syntax included) file which explained in http://www.apache.org/legal/src-headers.html#faq-exceptions . But, I will create a new Jira Issue soon because it needs to be include.
I'm sorry. I didn't mean to change it. IntelliJ automatically adjust the order of import. I'll place back to previous version with above Jira issue.

Thank you :)


Update citation in readme to v1.4.0

Never mind. Maybe it should be the all version DOI, 10.5281/zenodo.592747, rather than a specific version. Let me know and I can update it.

Yeah now that all-version DOIs exist, that would be better. I think I also told @rbiswas4 to cite the ASCL entry at some point. Honestly not sure which should be preferred.

I think ASCL is nice, especially its integration with ADS, but it also just points to a DOI citation. There is always the option to write a "paper" for JOSS. It does make a new citation option, but one that is not version dependent.
I think my vote would be the all-version DOI.

Sounds good, let's go with the all-version zenodo DOI as the "recommended" citation, but also link to the ASCL entry for reference.

I also just noticed the CITATION.md file. I'll update that file as well.

Thank you!


pip intall error

Hello team :)
I have an error when i am trying to install tile server,
pip install -Ur tileserver/requirements.txt
Collecting AppDirs==1.4.3 (from -r tileserver/requirements.txt (line 1))
  Using cached appdirs-1.4.3-py2.py3-none-any.whl
Requirement already up-to-date: argparse==1.2.1 in /usr/lib/python2.7 (from -r tileserver/requirements.txt (line 2))
[...]
  Could not find a version that satisfies the requirement raw_tiles (from tilequeue->-r tileserver/requirements.txt (line 27)) (from versions: )
No matching distribution found for raw_tiles (from tilequeue->-r tileserver/requirements.txt (line 27))

can you help me to resolve this ?.
Thanks to you :)

Whoops, we were missing a requirement. I just pushed over a fix with bdc6ac0. Can you try again?

Good, it work now, thank you


Netbird script does not work on alpine containers

Please verify that you have read and understood the guidelines.
yes
A clear and concise description of the issue.
it is not possibile to install netbird on a container alpine_linux-based
What settings are you currently utilizing?
Default Settings
Which Linux distribution are you employing?
Alpine
If relevant, including screenshots or a code block can be helpful in clarifying the issue.
Installing NetBird...
bash: line 3: /usr/share/keyrings/netbird-archive-keyring.gpg: No such file or directory
wget: write error: Broken pipe
bash: line 4: /etc/apt/sources.list.d/netbird.list: No such file or directory

Please provide detailed steps to reproduce the issue.
try to install a container based on alpine linux.
then try to install netbird client on this container and you get the following error after the menu where you select where to install netbird

    _   __     __  ____  _          __
   / | / /__  / /_/ __ )(_)________/ /
  /  |/ / _ \/ __/ __  / / ___/ __  /
 / /|  /  __/ /_/ /_/ / / /  / /_/ /
/_/ |_/\___/\__/_____/_/_/   \__,_/

Installing NetBird...
bash: line 3: /usr/share/keyrings/netbird-archive-keyring.gpg: No such file or directory
wget: write error: Broken pipe
bash: line 4: /etc/apt/sources.list.d/netbird.list: No such file or directory

This is not a bug. Alpine uses a completely different logic. A completely new script must be built for this, if it is possible at all with alpine.

well, you can call as you wish (bug or CR or whatever) but I think 2 things should be done:

modify the script in order to controll the os of the container (otherwise it simply crashes like now)
notify it on the web page. ;-)
this are just my 2 cents for the community:-)

I see this error after selecting container