Support patterns as input also in String.endsWith

Use case
I would like to use String.endsWith(String other); with a pattern rather than a String only. This is already done with other Flutter String methods like startsWith, contains, etc.
My specific use case is checking if the string ends with either ',' or '.'
My current solution is
onChanged: (value) {
        if (value.endsWith('.') || value.endsWith(',')) {
          return;
        }
        onChanged?.call(double.tryParse(value) ?? 0.0);
},

Proposal
Having that above use case in mind, with patterns I would be able to do this:
final _decimalSeparatorMatcher = RegExp(r'[\,\.]');
...
      onChanged: (value) {
        if (value.endsWith(_decimalSeparatorMatcher)) {
          return;
        }
        onChanged?.call(double.tryParse(value) ?? 0.0);
      },

Of course, this is a simple case with two conditions, but this issue grows the more cases you would like to check with endsWith. Also as a user I expected endsWith to work with patterns, because of the other String methods mentioned above.

Hi @MartPiet, this is a dart-lang issue and should be reported on their issue tracker https://github.com/dart-lang/sdk/issues?q=is:issue+is:open+sort:updated-desc.
I'll be closing this issue since this feature will have to implemented in the dart-sdk itself and not in flutter.
Thank you


Update Pages “SignsOfTermitesPage”

Automatically generated by Netlify CMS

👷 Deploy Preview for chic-shortbread-66a66b processing.

Name
Link

🔨 Latest commit
d894a303a8d28a4e1150fcd5ff9dbf634407f09c

🔍 Latest deploy log
https://app.netlify.com/sites/chic-shortbread-66a66b/deploys/655fdcfc5ef1330008a7aff9


Set data-grouplength dynamically

What's the best advice if I want to adjust data-grouplength dynamically? I tried using JavaScript to change the field for different types of credit cards then triggering enhance on the document again just to see if it would work. I haven't looked at the source yet, but is this accounted for in the plugin?
If not I guess I'll have to remove the field and clone a new one to trigger enhance on for the first time.

I should have been more specific. I was using jQuery.data() to set the data-grouplength attribute. It had no effect. Once I switched to vanilla getAttribute and called the jQuery.politespace() method on my input again, it updated. So my code looks something like this, tweaked for testing:
var $el, el;

$el = $("input").eq(0);
el = $("input").get(0);

el.setAttribute("data-grouplength", "4,4,4,4");

$el.politespace();

... and using that pattern I'm able to change the grouplength based on other factors.

I was having this issue because jQuery.data() and setAttribute/getAttribute aren't interchangeable. Didn't know that before.

No worries! Thank you for coming back and closing!


Notebook for creating a grid of PSFs using WebbPSF

Adding notebook for creating grids of PSFs using WebbPSF as referenced in JIRA issue: https://jira.stsci.edu/browse/JDA-14 . A file has also been added to Box to be used in the notebook
cc @larrybradley

The webbpsf, poppy, and photutils versions needed for this notebook to run (0.8, 0.8, and 0.6) have not been released yet, but they are part of DA Build5 and will be soon

@shanosborne I reviewed your notebook and ran it locally.  Overall it looks good, thanks!  The only problem I found is that you need to add import matplotlib at the top (it's used in matplotlib.colors.LogNorm, but never imported).
One other issue is that it takes a few hours to run this entire notebook.  Because of that, there's no way travis can automatically test and render this notebook.  There are a few places where the notebook could be sped up (e.g. not generating PSFs for all detectors), but it's still going to take longer than travis can handle.  @eteq What do you want to do here?

@larrybradley @eteq In terms of speed, we can also change some of the variables when creating the PSFs. I did some quick calculations and setting nlambda=1 can speed up calculations of PSFs by ~25% and setting nlmabda=1 and oversample=1 can speed up calculations of PSFs by ~60% (depending on the instrument). However, due to the shear number of PSFs created in this notebook, that may not be enough depending on what run time travis can handle.


Should Port Forwards/Terminals be under Cluster Overview.

Describe the problem/challenge you have
Setup port forwarding, or create terminals, and you can see them listed under "Port Forwards" and "Terminals".
Problem is those appear under "Cluster Overview" section of the left hand side menu.
If you run Octant with --disable-cluster-overview, that whole Cluster Overview section is hidden. You thus can't access those two pages, even though they are still relevant when that section is disabled, since you can still setup port forwarding or create terminals from pods.
Describe the solution you'd like
The "Port Forwards" and "Terminals" should not be under "Cluster Overview". Possibly should be under "Overview", a section of their own, or even "Configuration".
Anything else you would like to add:
Nope.
Environment:

Octant version (use octant version):

$ octant version
Version:  0.10.2
Git commit:  438ce3d52088c1e3e15aaf9817ba71e3c85255f5
Built:  2020-02-15T02:33:23Z

Kubernetes version (use kubectl version):

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-13T18:08:14Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:07:13Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}

OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc):

$ uname -a
Darwin grumpy-at-home.fritz.box 19.3.0 Darwin Kernel Version 19.3.0: Thu Jan  9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 x86_64

Also affects separate web browser when accessing Octant as web service.

I think we may considering removing the cluster overview section all together.


Rule order is not preserved between rules that have an event type and those that don't

It's possible to have rules that don't explicitly name an event type, or have conditions that make it difficult to map to a specific set of event types. These rules run for all event types. This compares to most rules that name an event type, which are stored in a list of rules indexed by event type.
There isn't anything that preserves rule order between the two collections, so it's possible that a rule that appears later in a rules file and runs for all event types will be considered before a rule that appears earlier in a rules file runs for a specific event type.
Here's an example:
- rule: open_below_tmp
  desc: An open event below /tmp
  condition: evt.type=open and fd.directory=/tmp
  output: some other output
  priority: INFO

- rule: related_to_tmp
  desc: Any action related to /tmp/
  condition: fd.directory=/tmp
  output: some output
  priority: INFO

In this case, related_to_tmp will run first even though it appears second in the file.
The fix is to keep track of overall rule order and preserve it when comparing rules in the two collections.

What's the goal of this fix? Is there a reason why falco must match the rules in the order in which they appear in the file?
Asking because if there's not and the goal is performance optimization, why can't we try to automatically reorder the rules to first match the rules that names event types and only after the "catchall" ones, instead of relying on the order in the rules file?
PS - I cannot find the test rules file catchall_order.yaml, maybe you forgot to add it to the commit?

I think generally preserving rule order is useful as you can ensure that earlier rules will match an event first.
I ran into this bug when I had a rules file that first checked filesystem paths related to an open, and later checked system calls. I wanted the filesystem paths rule to take precedence over the system calls rule, so I put it earlier in the file. However, because the system calls rule wasn't specifically tied to any particular system call (its condition was something like and not evt.type in (...), it was put in the catchall category and always was evaluated first.
When I tried to open a file below a disallowed path, the system call rule triggered instead of the filesystem rule.
Thanks about catchall_order.yaml, I added it to the PR.

Oh ok now I got it, it's a rule precedence issue.
I agree with your solution then. Thanks for the explanation!


Integrate ValueSerp

Please integrate valueserp api, it's the most cheapest available.
I'm facing issues with the free options.

Hey @jagdish1o1, you might want to check out https://serper.dev as well! We're even cheaper (and much faster) than ValueSerp.

@rogerserper yes but serper have not been yet added to SerpBear.


[BUG] Spring Boot Key Vault doesn't work with Azure Stack

Describe the bug
The spring boot key vault starter could not work correctly in Azure Stack. Please refer to this https://github.com/Azure/azure-sdk-for-java/issues/12227.
Exception or Stack Trace
Secrets could be retrieved correctly from Key Vault provisioned in Azure Stack.
To Reproduce
Please ping the Azure Stack team (@bganapa) to get access to the Azure Stack environment. Now the azure-identity supports ADFS, we should integrate this with our starter.
Code Snippet
Add the code snippet that causes the issue.
Expected behavior
Key Vault starter works correctly in the Azure Stack environment.
Setup (please complete the following information):

IDE : [IntelliJ]
Version: The latest version of Spring Boot starter for Key Vault

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[x] Setup information Added

Closing this issue since it's been implemented in https://github.com/Azure/azure-sdk-for-java/pull/15548.

Closing this issue since it's been implemented in https://github.com/Azure/azure-sdk-for-java/pull/15548.


make finding the command to install pulumi effortless

we bury the install command multiple pages into the guides
should we be making this easier to find?
suggest the home page, get started landing page, and the footer
multiple folks in the studies struggled to find the install command
internal slack convo with video
related issue: https://github.com/pulumi/pulumi-hugo/issues/1163

If we make the getting started guide a single page (tracked elsewhere), this will be easily discoverable from the prominent “Getting Started” link (today, it is three clicks deep into the getting started guide).
We could/should also consider placing this command directly on one or both of www.pulumi.com and www.pulumi.com/docs.

this is fixed now


Allow Workspace Relative bazel_binary path in .bazelproject file

We have implemented a bazel wrapper inside of our workspace. We also provide *.bazelproject files for different workflows. We would like to utilize the bazel_binary tag to set the path to the bazel wrapper to ensure that all users are using the bazel wrapper, however this tag requires an absolute path. As the path will be different on each developers workstation, we would like to be able to use a relative path.

I don't see why not: https://github.com/bazelbuild/intellij/pull/970


Wrong results for AIList

Datasets:

ex-anno
chainRn4

Benchmarking algorithms/Coitrees+----------+
| count(*) |
+----------+
| 2764185  |
+----------+
+----------+
| count(*) |
+----------+
| 2764185  |
+----------+
+----------+
| count(*) |
+----------+
| 2764185  |
+----------+
algorithms/Coitrees     time:   [254.85 ms 255.58 ms 258.48 ms]
                        change: [+81.052% +88.335% +96.113%] (p = 0.10 > 0.10)
                        No change in performance detected.

Benchmarking algorithms/IntervalTree+----------+
| count(*) |
+----------+
| 2764185  |
+----------+
+----------+
| count(*) |
+----------+
| 2764185  |
+----------+
+----------+
| count(*) |
+----------+
| 2764185  |
+----------+
algorithms/IntervalTree time:   [474.29 ms 474.83 ms 474.96 ms]
                        change: [+88.710% +90.503% +92.327%] (p = 0.10 > 0.10)
                        No change in performance detected.

Benchmarking algorithms/ArrayIntervalTree+----------+
| count(*) |
+----------+
| 2764185  |
+----------+
+----------+
| count(*) |
+----------+
| 2764185  |
+----------+
+----------+
| count(*) |
+----------+
| 2764185  |
+----------+
algorithms/ArrayIntervalTree
                        time:   [342.01 ms 342.54 ms 344.66 ms]
                        change: [+54.959% +55.994% +57.035%] (p = 0.10 < 0.10)
                        Performance has regressed.

Benchmarking algorithms/AIList+----------+
| count(*) |
+----------+
| 2764232  |
+----------+
+----------+
| count(*) |
+----------+
| 2764232  |
+----------+
+----------+
| count(*) |
+----------+
| 2764232  |
+----------+
algorithms/AIList       time:   [496.10 ms 504.46 ms 506.55 ms]
                        change: [+93.362% +95.628% +97.899%] (p = 0.10 > 0.10)
                        No change in performance detected.

Here is a Rust version:
https://github.com/databio/gtars/blob/master/gtars/src/ailist/core.rs

my resuts:
+----------------+
| count(a.start) |
+----------------+
| 2764185        |
+----------------+
1 row(s) fetched.
Elapsed 9.696 seconds.

0 row(s) fetched.
Elapsed 0.001 seconds.

+----------------+
| count(a.start) |
+----------------+
| 2765541        |
+----------------+
1 row(s) fetched.
Elapsed 33.475 seconds.

It looks like there is a bug in ScAIList lib.
for the same key, in COITrees we return 1 interval, but in ScAIList we get back multiple identical intervals.
Interesting part is that it seems to be connected to the data volume since i cannot reproduce this error in test.


Fix middleware function's placements

Add reqSignIn to /task/{task} as it specific to a logged in user currently not-logged in user could cause a NPE.
Move /stopwatch & /search middleware before the actual function is called, because functions are executed in order and currently hadn't any effect and could as well cause a NPE due to that.
Remove /active reqSignIn middleware, because when you want to active a account you're not "signed in" so it doesn't make sense to add that middleware.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@d139c23). Click here to learn what that means.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main   #19377   +/-   ##
=======================================
  Coverage        ?   47.39%
=======================================
  Files           ?      949
  Lines           ?   132090
  Branches        ?        0
=======================================
  Hits            ?    62605
  Misses          ?    61952
  Partials        ?     7533

Impacted Files
Coverage Δ

routers/web/web.go
86.51% <100.00%> (ø)

Continue to review full report at Codecov.

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


Question: Best way to decide on next card

Hi there! Thanks a lot for creating this demo - I've learnt a lot from it trying to build my own flashcard application.
I would like to know what's the best approach for deciding on the next card to show. Currently, my approach is to sort by the due Date, but I noticed that you had a slightly different approach in CardContext.tsx.
// CardContext.tsx
function updateStateBox(
  noteBox: { [key in StateBox]: Array<Note & { card: Card }> },
  currentType: StateBox,
  nextDue?: Date
) {
  let change: StateBox = State.New; // default State.New
  switch (currentType) {
    case State.New:
      if (noteBox[State.Learning].length > 0) {
        change = State.Learning; // new -> learning
      } else if (noteBox[State.Review].length > 0) {
        change = State.Review; // new -> review
      }
      break;
    case State.Learning:
      if (noteBox[State.Review].length > 0) {
        change = State.Review; // learning/relearning -> review
      } else if (noteBox[State.New].length > 0) {
        change = State.New; // learning/relearning -> new
      } else {
        change = State.Learning; // learning/relearning -> learning/relearning
      }
      break;
    case State.Review:
      if (noteBox[State.Learning].length > 0) {
        change = State.Learning; // review -> learning
      } else if (noteBox[State.New].length > 0) {
        change = State.New; // review -> new
      } else {
        change = State.Review; // review -> review
      }
      break;
  }
  change =
    change === State.Learning &&
    noteBox[State.Learning].length > 0 &&
    fixDate(noteBox[State.Learning][0].card.due).getTime() -
      new Date().getTime() >
      0
      ? RandomNewOrReviewState(noteBox)
      : change;
  return change;
}

From what I can see, in general we are deciding on the next card by choosing a different state from the previous card.
May I know if there is a reason why you decided on this approach?
Is there a way to deterministically decide on the sort order of the cards for the day that doesn't use the due Date? Thanks!

May I know if there is a reason why you decided on this approach?

In the current demo, the cards with State.New and State.Review are randomly ordered, while the cards with State.(Re)Learning are sorted based on their due dates. This approach ensures that the consecutive cards will not be the same card for (Re)Learning.

Is there a way to deterministically decide on the sort order of the cards for the day that doesn't use the due Date?

Currently, research suggests that the sort order of cards for the day can be determined deterministically using either the difficulty_asc or retrievability_desc of the cards, instead of relying on the due date. You can refer to the following link:

https://github.com/open-spaced-repetition/fsrs4anki/pull/634
https://github.com/open-spaced-repetition/review-sort-order-comparison

in general we are deciding on the next card by choosing a different state from the previous card.

It may not be as straightforward as it seems, as we also need to consider cases where other state cards are empty. The deck scheduling logic can be referred to in the following diagram:

https://github.com/open-spaced-repetition/ts-fsrs/issues/79

using either the difficulty_asc or retrievability_desc of the cards

If you want to use retrievability_desc, I might need to modify the method in ts-fsrs because it currently return string.
https://github.com/open-spaced-repetition/ts-fsrs/blob/f282b5b2108d7b6d9a1b7a8c5d3203139b858cb8/src/fsrs/fsrs.ts#L162-L175
  get_retrievability = (
    card: CardInput | Card,
    now: Date,
  ): undefined | string => {
    const processedCard = this.preProcessCard(card);
    now = this.preProcessDate(now);
    if (processedCard.state !== State.Review) {
      return undefined;
    }
    const t = Math.max(now.diff(processedCard.last_review as Date, "days"), 0);
    return (
      (this.forgetting_curve(t, processedCard.stability) * 100).toFixed(2) + "%"
    );
  };

@ishiko732 Thanks a lot for the comprehensive answer! I'll consider using difficulty_asc first to get a working version. I'll consider adding a settings page in the future to handle different sort orders!

@ishiko732 I implemented sorting by difficulty, and I notice that all New cards will appear first. Is that the intended behaviour of this sorting?

@ishiko732 I implemented sorting by difficulty, and I notice that all New cards will appear first. Is that the intended behaviour of this sorting?

I believe that sorting State.New cards by difficulty may not be the intended behavior, as these cards haven't undergone the f.repeat scheduling yet and typically have a default difficulty=0,stability=0,retrievability=undefined. Instead, State.New cards should be randomly inserted into the queue.
State.New cards should be interspersed with other cards (State.Learning, State.Relearning, State.Review) in the display.
createEmptyCard:https://github.com/open-spaced-repetition/ts-fsrs/blob/f282b5b2108d7b6d9a1b7a8c5d3203139b858cb8/src/fsrs/default.ts#L55-L75

I think sorting the State.New cardBox in random or insertion order, sorting the State.Learning and State.Relearning cardBox in due_asc order, and sorting the State.Review cardBox in difficulty_asc or retrievability_desc order is a reasonable approach.
@L-M-Sherlock, what do you think of it?

@ishiko732 Thanks for the tip! It makes sense now why you split the notebox based on the state. I'll go with the approach that you suggested first, but will take note of other suggestions!

Starting from ts-fsrs v3.5.7, the f.get_retrievability method can return undefined | string| number based on the format parameter. For more details, please refer:

https://open-spaced-repetition.github.io/ts-fsrs/classes/FSRS.html#get_retrievability
https://github.com/open-spaced-repetition/ts-fsrs/blob/0fdaa11f74fc236546cdcb8d48cb678b053b397b/__tests__/FSRSV4.test.ts#L116-L130

Furthermore, the get_retrievability method now returns the same results as fsrs4anki. @zsh-eng


[https://web.crev.dev/] Github url of user profiles is wrong

The URL for Lokathor puts the link to LucianoBestia as the github link.

Ping @LucianoBestia (the author and maintainer of web.crev.dev (git repo: https://github.com/LucianoBestia/cargo_crev_web)

You probably tried just the link on the bottom of the page. There is the version and repo of the cargo_crev_web project. The link to lokathor is on the top of the page.
I should make it more clear that the footer is about the page and not the content.

https://web.crev.dev is a separate project. Please use https://github.com/LucianoBestia/cargo_crev_web . Closing since there's nothing actionable for us right now.


Displayer is not applied to resourses

To display images I use
ImageLoader imageLoader = ImageLoader.getInstance();
		DisplayImageOptions  options =
				new DisplayImageOptions.Builder().showImageOnLoading(R.drawable.play_stub)
				                                 .showImageForEmptyUri(R.drawable.play_stub)

				                                 .showImageOnFail(R.drawable.play_stub)
				                                 .cacheInMemory()
				                                 .cacheOnDisc().displayer(
						new RoundedBitmapDisplayer(20)
				) //rounded corner bitmap
						.build();
		imageLoader.displayImage(getArguments().getString(ARG_POSTER),imPoster,options);

In result I get nice rounded image if it is loaded from web, but R.drawable.play_stub is not rounded on Image loading/emptyuri/fail

Right, this is how the library work. Why don't you place rounded drawables into the app?

@nostra13
I tried before, but my corners looks a bit different.


Give icon search priority to the user folder ~/.local/share/applications

This would allow users to overwrite an application's icon by copying its .desktop file into the user folder to modify it

That's what it already looks like, unless you specified XDG_DATA_HOME. The first in the slice item returned by the getAppDirs() function is:
    if xdgDataHome != "" {
        dirs = append(dirs, filepath.Join(xdgDataHome, "applications"))
    } else if home != "" {
        dirs = append(dirs, filepath.Join(home, ".local/share/applications"))
    }

See: https://github.com/nwg-piotr/nwg-dock-hyprland/blob/f20e5178070f45f98b7abe25b5318eb3e583724b/tools.go#L467

The culprit is the break statement missing from the loop that searches paths in the getIcon() function. I'll fix it.

Thanks. This caused the home directory to be used as a fallback only


White line on cursor

im having an issue where there is a white line on my cursor... any idea why its happening?

im having an issue where there is a white line on my cursor... any idea why its happening?

What's the problem?

Can't understand the problem

Ok, I think that is its design because the tail is a little curve when you zoom too much and the line is sooooo small that it's ignorable until you just zoom a lot.

This is the curve

If you see carefully at the lower part you see a little line on the black part of the cursor.

I think that this is the problem but I don't understand what this issue is really about.


How do you test the speed of UniTR?

Hi haiyang,
Thanks for your awesome work. I want to know how you test the speed of UniTR, can you share the code with me. What's more when you calculate the speed of UniTR, do you consider the time cost of voxelization. Thanks!
Best

Use the cache Testing, and then also cache the position embedding. Moreover, I write the speed test code based on time.time(), not the default pcdet --infer time. The randomness of the speed is very large, it is recommended that you test on your own workstation, even if the same card will have some differences.

Due to inaccuracies in the camera parameters of NuScenes itself, the cache can affect performance.


Refactor to only call random streams once per step

There are (at least) two places in the code where the same random number distribution is called more than one time on a single timestep. Doing so is not common random number safe, and the code now raises an exception.
As a temporary workaround, I have reset the random state, e.g.
self.random_state.step(self.sim.ti+1)

The above code does NOT step the random state forward in time despite the ti+1 argument. This is simply resetting the random state to how it would have been at the beginning of THIS timestep.
However, this hack is not efficient and potentially not scientifically safe. The underlying code should be refactored, or we need to create separate random number generators for each call.
The two place where this hack is in place are:

distribution.py near line 140
products.py near line 118

Closed by #645


There is no feedback if failed to click to goToDefinition

VSCode Version: 1.51
OS Version: OSX 10.15.5 (19F101)

Steps to Reproduce:
1.import some from 'moduledoesnotexist';
2.CMD + Click to goToDefinition
3.Failed to go, and there's no feedback message (No definition found for 'moduledoesnotexist' like commands or context menu)

Does this issue occur when all extensions are disabled?: Yes

Dig one step deeper, #23978 seems to be the original reason.

Please attach the file/project in which this reproduces

file demo.js:
import a from 'thisModuleDoesNotExist';

Right click 'thisModuleDoesNotExist' or execute go to definition command and go to definition:

Keyboard shortcut CMD + Click to go to deinfition:

Expect a definition not found tip here.

Keyboard shortcut CMD + Click to go to deinfition:

The cmd+click gesture check if there is a definition before making a word a link. I don't see an underline and link color when hovering over the word while holding cmd. That means there is nothing to navigate to and therefore there is no message about a missing definition. Do you see a link being rendered?

Expect a definition not found tip here.

IMO, link navigation should be separated from cmd+click gesture, the problem is a kind of gesture conflict, no link navigation (so as to keep silent) may not affect no definition found message.

cmd+click a link, then do not go to definition, just open URL
cmd+click a module, then just go to definition, do not try to open URL
cmd+click a existing module, then open one target file or peek definitions
cmd+click a non-existing module, then show module not found message (which is silent now)

cmd+click a non-existing module reference, then show module not found message (which is silent now)

That's where I disagree and why I am closing this. The cmd+click gesture is only valid for links and the link will show when cmd+hovering over a valid target.

The cmd+click gesture is only valid for links

It's not true (from user's view), because go to definition shortcut seems to be cmd+click in a long time, and the kind of gesture conflict exists all the time.

Go to definition is bound to f12. It shows an alert if no definition is found
cmd+click is a convenience for quickly navigating through code with the mouse. In this case, the lack of a link being rendered is the feedback that no definition has been found

@mjbvz Thanks for your explanation, I know 'as-designed' now.
My consideration is whether no definition found should be a bit more explicitly (than lack of a link rendered now)? especially in certain cases:

A 3rd DefinitionProvider extension: failure message may be important for users. (BTW, custom failure message may be a feature request.)
Modified Go to definition keyboard shortcut(eg. Sublime Text keymap ctrl+click on Mac): some users told us they can not go to anywhere use cmd+click, we have to ask them 'Right click and select go to definition, then can you go to there?' to rule out modified shortcut.

I agree with the interesting convenience, but I notice the missing feedback message, and an explicit feedback for goToDefinition result is essential from my point of view, because click is a stronger action than hover, users maybe expect a stronger feedback.


HOTFIX: renamed test so it is picked up by ducktape

@ewencp @mjsax

Test passed: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/718/


List of Attributes or properties supported is incomplete

The list of properties supported in a filter currently shows:
First Name
Last name
Display name
Job title
Department
Office
Street address
City
State or province
Postal code
Country or region
Email addresses
Alias
Exchange custom attributes: CustomAttribute1 - CustomAttribute15
However this is out of sync with Microsoft's presentation located here:
https://mipc.eventbuilder.com/event/52683/occurrence/49452/recording?rauth=853.3181650.1f2b6e8b4a05b4441f19b890dfeadcec24c4325e90ac492b7a58eb3045c546ea
I also have a customer who has been able to use Company as a filter.  We may need to link this article to one that lists all the queryable fields for filters or for KQL.  Since I am not sure what the full list of supported properties is my assumption is that this might require pinging the product group to get the best possible list.

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

ID: 592d6717-d670-14a8-acbe-c648958ca208
Version Independent ID: 9bc46fd9-50e1-1e58-4852-22068e2980ae
Content: Configure retention settings to automatically retain or delete content - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/retention-settings.md
Service: o365-seccomp
GitHub Login: @cabailey
Microsoft Alias: cabailey

@cablechewer Thank you for your feedback.    I don't see Company listed as a selectable attribute in the simple query builder, so I will ask about this. We don't currently have documentation for a full list of properties for KQL queries, although this has been requested.

@cablechewer That presentation is for the advanced query builder, which explains why you don't see Company listed as an attribute for the simple builder query - it would be impractical to list every supported attribute in that table. I've clarified that the attributes in the table aren't exhaustive and link to the presentation if using the advanced query builder.
The feature is newly released in preview and we are looking into providing additional documentation for KQL supported attributes.


issues running cri-o with Clear Containers

Basically followed https://github.com/01org/cc-oci-runtime/wiki/Installing-Clear-Containers-on-Fedora-24 adapting them to F25 (since there's already an F25 repo). I can start clear containers with docker 1.12.1 but when it comes to try it with cri-o I'm getting:
$ sudo /home/amurdaca/go/bin/ocid --debug --log ocid.log --runtime /usr/bin/cc-oci-runtime --conmon $PWD/conmon/conmon --seccomp-profile=$PWD/seccomp.json
WARN[0000] default configuration file does not exist: /etc/ocid/ocid.conf
container PID: 4799
qemu-lite-system-x86_64: -chardev pipe,id=charconsole0,path=/run/containers/devicemapper-containers/b2245cd26b8ac53e9118fa291e04ff29f488b6f85a89d83e063a98d11f535a01/userdata/cc-std: Could not open '/run/containers/devicemapper-containers/b2245cd26b8ac53e9118fa291e04ff29f488b6f85a89d83e063a98d11f535a01/userdata/cc-std': No such file or directory
PID 4799 exited with status 1
conmon: Failed to create container
conmon: Failed to create container

and in kubernetes:
Events:
  FirstSeen     LastSeen        Count   From                    SubObjectPath           Type            Reason          Message
  ---------     --------        -----   ----                    -------------           --------        ------          -------
  3m            3m              1       {default-scheduler }                            Normal          Scheduled       Successfully assigned nginx-2932712833-s75ld to <IP_ADDRESS>
  3m            3m              1       {kubelet <IP_ADDRESS>}                             Normal          SandboxReceived Pod sandbox received, it will be created.
  2m            19s             3       {kubelet <IP_ADDRESS>}     spec.containers{nginx}  Normal          Pulled          Successfully pulled image "nginx"
  2m            19s             3       {kubelet <IP_ADDRESS>}     spec.containers{nginx}  Warning         Failed          Failed to create container with error: rpc error: code = 2 desc = reading pid from init pipe: EOF
  2m            19s             3       {kubelet <IP_ADDRESS>}                             Warning         FailedSync      Error syncing pod, skipping: failed to "StartContainer" for "nginx" with rpc error: code = 2 desc = reading pid from init pipe: EOF: "Create Container Failed"

  3m    18s     4       {kubelet <IP_ADDRESS>}     spec.containers{nginx}  Normal  Pulling pulling image "nginx"

/cc @sameo @jjlakis

@runcom The Clear Containers instructions you looked at are for Clear Containers 2.0 and that will not work with CRI-O.
Some background here, as we're currently transitioning to Clear Containers 2.1:
Clear Containers 2.0 was a (too) simple architecture that did not allow us to support many Docker commands and certainly not anything related to pods, k8s or CRI-O. Clear Containers is a partial re-architecture of 2.0 to fix most of those gaps.
The Clear Containers master branch is currently running the 2.1 architecture and I released 2.1.0-rc.4 yesterday. I test CRI-O and Clear Containers with master only. We expect to do the final 2.1.0 release in 3-4 weeks. Once this is done we'll update the installation instructions.
I'll be happy to provide more details about all of this during next week meeting.
Also, I will prepare a temporary wiki page with the 2.1 installation instructions for you to look at. We already are building OBS packages for 2.1 on FC25 in case you want to try them out:
http://download.opensuse.org/repositories/home:/clearlinux:/preview:/clear-containers-2.1/Fedora_25/

@sameo thanks, however, using the new packages is not helping:
Events:
  FirstSeen     LastSeen        Count   From                    SubObjectPath   Type            Reason          Message
  ---------     --------        -----   ----                    -------------   --------        ------          -------
  34s           34s             1       {default-scheduler }                    Normal          Scheduled       Successfully assigned nginx-2932712833-91j0t to <IP_ADDRESS>
  33s           33s             1       {kubelet <IP_ADDRESS>}                     Normal          SandboxReceived Pod sandbox received, it will be created.
  6s            6s              1       {kubelet <IP_ADDRESS>}                     Warning         FailedSync      Error syncing pod, skipping: failed to "CreatePodSandbox" for "nginx-2932712833-91j0t_default(2d3f6a43-df19-11e6-899a-507b9d4141fa)" with CreatePodSandboxError: "CreatePodSandbox for pod \"nginx-2932712833-91j0t_default(2d3f6a43-df19-11e6-899a-507b9d4141fa)\" failed: rpc error: code = 2 desc = reading pid from init pipe: EOF"

@runcom can you try enabling cc-proxy first:
systemctl start cc-proxy

@runcom can you try enabling cc-proxy first:
systemctl start cc-proxy
(It should start automatically upon socket activation, but it seems not to be the case)

that made the pause container to start up with clean containers. However I'm now seeing an issue when it can't actually start the "nginx" container because id is already reserved. Maybe a bug somewhere..

@sameo apparently I got a cc vm running with infra container but when it comes to starting the nginx container something goes wrong and cc-oci-runtime list shows it as stopped. Also, there  might be a bug there since the kubelet shows "created" and "started" while the status is still pending (not sure about networking in clear containers also).

(It should start automatically upon socket activation, but it seems not to be the case)

@sameo the socket is disabled by default on installation btw.

@sameo the socket is disabled by default on installation btw.

Yes, we're working on that one. At the moment, SELinux prevents us from enabling it by default.

@sameo apparently I got a cc vm running with infra container but when it comes to starting the nginx container something goes wrong and cc-oci-runtime list shows it as stopped. Also, there might be a bug there since the kubelet shows "created" and "started" while the status is still pending (not sure about networking in clear containers also).

@runcom could you please share which commands you're using to start an nginx pod, so that I can try reproducing here ?

@sameo it works now! and it's great to see CC running with CRI-O :)

What SELinux issues are you seeing?

@rhatdan nothing related to SELinux - even if I tested it with setenforce 0 just to be sure - I'll re-test with selinux enabled and let you know.

@sameo @runcom showed me a demo, very nice.  We should be blogging and putting the demo up on youtube.  Nice to see alternate runtimes working under kubernetes using CRI-O.

@rhatdan Nothing related to SELinux itself, but the fact that we were not installing any TE file for our proxy socket. This should be fixed now with https://github.com/01org/cc-oci-runtime/pull/612

@sameo @runcom showed me a demo, very nice. We should be blogging and putting the demo up on youtube. Nice to see alternate runtimes working under kubernetes using CRI-O.

It is very nice indeed :) It's been very easy to get the right changes merged into ocid, this is a truly open project.
Blogging about it would be great. Would the k8s blog be the right place ?

That would work fine.  Having a quote like " It's been very easy to get the right changes merged into ocid, this is a truly open project." would be awesome.
I will try to get a blog on a Red Hat site also.


CVE graph missing time range

The bargraph of CVEs does not denote the time range the CVEs totals were collected over ;)

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

ID: f11f40c1-5631-3757-bcb0-a31d50506c1f
Version Independent ID: eaee8c73-7d36-027a-11c7-077a264d36be
Content: Beginning your General Data Protection Regulation (GDPR) journey for Windows 10 (Windows 10)
Content Source: windows/privacy/gdpr-win10-whitepaper.md
Service: unspecified
Product: w10
GitHub Login: @pwiglemsft
Microsoft Alias: pwigle

Hi @marekr , we currently do not intend to commit any updates to the current GDPR whitepaper. We are looking at releasing an alternative \ updated version.
In order to correct this issue, we'll need to revisit the collected data, which we will do in a future version\alternative of this whitepaper.
Thank you for raising this issue, and I'm sorry I can't offer a better answer.


Turn on eager-classloading (Camel 3.10) by default to optimize

In camel-main there is a new option
camel.main.eager-classloading = true
We can be a bit smarter in camel-quarkus, and so some kind of build step, that triggers invoking this eager classloading inside camel-main. This helps to ensure those classes are loaded during build time instead of runtime at the first message processed by Camel.
We need to ensure that this is triggered as part of quarkus and its built time phase so its triggered for both JVM vs native mode

Can we not make camel.main.eager-classloading = true the default on the Camel side? Then there'd effectively be no work required in CQ given that the Camel Main bootstrapping is already done at build time.

Yeah its something that makes sense for camel-main based apps to have.
There is more work needed in core to optimize for eager loading in some of the EIPs - Have not had the time to do that.
Fell free to close this ticket.


Map owners to organizations/apps

What we're after: when users want to move from East/West to GovCloud, it's useful for our team to know who the owner is.
Noted that this could involve ongoing work

Issue moved to 18F/cg-migration #41 via ZenHub


mirror PR 3010 "adapt timeouts of controller and nginx"

mirror change to kube copy of nginix.conf from OW PR 3010.

timeout waiting for nginx pod to deploy again.   @rabbah can you kick travis to try again.


[python3] Improve support for embedding and add tools

This pull request improves the downstream experience when working with the python3 port by building a functioning interpreter with support for pip and improving support when cmake's FindPython3 finder is used. Previously, when using FindPython3, if both the DEVELOPMENT and INTERPRETER components were requested, you would have to have a local python install matching the vcpkg python. Further, on Windows, this module preferred registry python over any slightly misconfigured python artifacts. Fixing these issues allows us to simplify ports whose cmake build systems need the python3 development libraries.
Anyone who intends to do further work on the python3 port after this might consider fixing vcpkg_find_acquire_program(PYTHON3) to use the interpreter installed by this port.
Note that on Windows a patch is applied in static python interpreters to disable extension modules-due to the way DLLs function, it is not possible to load them without crashing the interpreter. Further, support for the static CRT has been removed both to avoid surprises in that regard and due to the nature of PyObjects.

What does your PR fix?
This should address #9026 and #10903.

Which triplets are supported/not supported? Have you updated the CI baseline?
Support for x64-windows-static has been dropped.

Does your PR follow the maintainer guide?
I think so 😄

Thanks for the PR!
@ras0219-msft, could you help further review?

Thanks for this PR!
Python is a very tricky subject in vcpkg, because there are three different use cases:

Libraries want to run python code during their build -- this means they need python for the host machine. This case is when ports should be using vcpkg_find_acquire_program(PYTHON3).
Libraries want to link against python.dll/.a/.lib because they expect the consumer to be a c++ program that embeds python (this is covered by the python3 port).
Libraries want to link against python.dll/.so because they are authoring extension modules to be used with an external python. This is the stickier situation, because it's possible that the ABI of the external python does not match the ABI of the internal python. However, I've been lead to believe that on Windows at least, python3 should generally be ABI compatible and so in this case it's acceptable to use the python3 port for building. I think same situation may apply for Linux, but I'm less certain of this platform.

Framed by the above three circumstances, could you re-explain what this PR is intended to accomplish?

Agreed, Python is definitely very tricky. Given the three use case you pointed out, this pull request was designed to address issues I've experienced in projects I contribute to around use case 2 and, to some extent, use case 1.
When using vcpkg's python with any of cmake's FindPython modules on Windows, they first go to the registry. The find modules introduced in CMake 3.12 (FindPython, FindPython2, FindPython3) add components such as Development and Interpreter. When a downstream user of vcpkg python is both embedding and using python as part of their build process eg by find_package(Python3 REQUIRED COMPONENTS Interpreter Development), the find will fail if the user does not have an installed system Python that is ABI compatible with the vcpkg.
Additionally, specifying the vcpkg artifacts is tricky with these finders, especially when using a multi-config generator (eg Visual Studio). A common complaint from our users is that the debug library is not properly found, leading to either surprise link errors with python38_d.lib not being found or with FindPython deciding to use some other non-vcpkg python. Overall, this leads to an unacceptable level of surprises and GOTCHAS, IMO. This pull request fixes that by building the python interpreter and ensuring artifacts are properly specified for all five cmake find python variants: FindPythonLibs, FindPythonInterp, FindPython, FindPython2, and FindPython3.
In the case of embedding, having python without its standard library is largely pointless. CMake 3.12's new find modules return the location of the Python standard library -- which is mostly a set of python scripts. However, to do so, it must run the interpreter itself. This brings us back to the previous point. Further, the standard library requires several internal extension modules to be built. This PR causes those extension modules to be built--they were not previously.
I built a project to test what I expect to work on Windows, macOS, and Linux here. (I disabled Windows CI in that repository in favor of local testing.)
Several ports fall into both use case 3 and use case 1. In those cases, we find fragile artifact specifications for the python development libraries in the portfile.cmake and a call to download the python interpreter. With a properly functioning python.exe built by vcpkg, these use cases can be simplified fairly significantly... Unless the upstream library rolls its own python finder (eg pybind11).
I did address one issue related to case 3 while working on the PR. Python is ABI stable at the minor release level (eg, 3.8.3 is compatible with 3.8.5 but not with 3.9.0) unless using the Py_LIMITED_API, which is stable across all of python 3. vcpkg neither supports this option presently nor with this PR. One undocumented sticking point I found with extension modules is related to the library linkage. On Windows, extension modules can only function against a shared python library. Attempting to link an extension module against the static python library will crash the interpreter when the end user imports said module. This limitation is not in present on unix-like platforms. Previously, on Windows, this was a silent GOTCHA. I did not outright remove support for static triplets because the static library is incredibly helpful when embedding python in use case 2.

This has been rebased to merge cleanly with master.

blocked by #13722.

I am unable to reproduce the CI failures with irrilicht and qt5-location locally.

blocked by #13765.

CI issues fixed in #13812 and #13830.

osg regression will be fixed in #13942.

After re-reading the comment by @ras0219-msft, I have reworked some of the commits in this pull request to properly support use case 1 by not assuming that the python interpreter build by vcpkg may be used on the host machine.

Before I take the time to resolve the merge conflicts, would it help the review process if this were split into multiple pull requests? It's been a little over a month since any substantial input was given.

@Hoikas yes, that's better.


What coordinate system is “EC_POINT_mul” done in?

Does it depend on the point in which coordinate system I set? Or it switchs automatically to reach the maximum efficiency?

Can I choose the coordinate system myself?

You can influence the coordinate system that you supply the original point in. Typically you would supply affine co-ords via EC_POINT_set_affine_coordinates(). It is also possible to supply the co-ords in compressed form via EC_POINT_set_compressed_coordinates().
Alternatively it is possible to supply them as projective co-ords via EC_POINT_set_Jprojective_coordinates_GFp() - but this is deprecated in OpenSSL 3.0.
See:
https://www.openssl.org/docs/man3.1/man3/EC_POINT_set_Jprojective_coordinates_GFp.html
You cannot influence the co-ordinate system used internally. OpenSSL will convert points between co-ordinate systems automatically as appropriate.

Thank you so much for your help! I really appreciate it.😄


[DDO-2669] Add offline schedule fields

The fields describe when the BEE should be offline. Begin is the beginning hour/minute/second that it should become offline each day and the end is the hour/minute/second that it should come back online each* day.
*When the EndWeekdayOnly field is enabled, the schedule won't "end" on weekends, so BEEs will sleep through the day. The "begin" side of the schedule always takes effect each day, it'll just have no effect if the BEE is already offline from the previous schedule.
I considered adding a calculated field of "should be offline right now," but that's actually harder to implement here than in Thelma where we're scanning environments, and Beehive doesn't care about it (I don't want to slow down listing all environments by also calculating a bunch of predicted offline states). I think it makes sense for Thelma to just do the work here and use Sherlock just as book-keeping.
Also removed a deprecated field that Beehive no longer uses; 2597041

I think it makes sense for Thelma to just do the work here and use Sherlock just as book-keeping.
Amen


Add iterator support to pyknowhere interface.

Add GetAnnIterator method to the swigknowhere IndexWrap class to wrap the AnnIterator method, so iterator can also be used in pyknowhere.
/kind improvement

/run-e2e

/lgtm


Colon not allowed in date format string?

Hello,
It seems as though {{ "now" | date: "%Y-%m-%d %H:%M" }} renders null but {{ "now" | date: "%Y-%m-%d %H%M" }} renders just fine. Is anyone else having this issue? It seems that the colon is causing it to render null.

It seems that if you change the following within /src/Liquid.php, it fixes the problem.
Change:
'QUOTED_STRING_FILTER_ARGUMENT' => '"[^":]"|'[^':]'',
To:
'QUOTED_STRING_FILTER_ARGUMENT' => '"[^"]"|'[^']'',
Does anyone know the details of the original pattern and why it was used? While this seems to have solved the colon issue, I haven't yet done enough testing to see if the new pattern causes other problems.


pyusb: powercycle the dongle

This PR allows power cycling of PyUSB devices when connected to a hub with port-level power control. Power cycling will be skipped if a compatible hub is not found.

This PR allows power cycling of PyUSB devices when connected to a hub with port-level power control. Power cycling will be skipped if a compatible hub is not found.

the pyusb transport is mostly a legacy implementation. The current/maintained USB transport is is transport/usb.py, implementation based on libusb1 instead of pyusb. Would it make sense to implement this behavior in usb.py instead (or in addition)?

the pyusb transport is mostly a legacy implementation. The current/maintained USB transport is is transport/usb.py, implementation based on libusb1 instead of pyusb. Would it make sense to implement this behavior in usb.py instead (or in addition)?

We switched to using the pyusb implementation because we encountered issues with the usb one during our testing. We didn't investigate the usb implementation thoroughly before moving to pyusb, as it is performing well in our test environment.


feat: implment persistent logging for containers running in foreground

Fixes: https://github.com/containerd/nerdctl/issues/1657

Implements cio.Creator interface to start logging binary as per https://github.com/containerd/containerd/blob/main/cmd/containerd-shim-runc-v2/process/io.go#L247 which creates 2 pipes to forward container output to the logging binary and one pipe to check if the logging binary is ready.
copies container output to the write side of stdout and steerr pipes created in the previous step to achieve persistent logging when containers are started in non detached mode.

TODO:
- Refactoring taskutil and container_io to use custom cio.Creator for all flags(-d,-t,-i,-a). This would unblock attach for -d.
[X] Changes for windows.
[X] Adding integration tests

Regression:

https://github.com/containerd/nerdctl/issues/2726

Regression:

https://github.com/containerd/nerdctl/issues/2726


fix: remove empty search result from suggestions (history)

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[x] Bugfix
[ ] Feature
[ ] Refactoring

What's new?

[x] PR closes #4308
[ ] Requires deployment <rubick/magick_issue>
[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[x] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[x] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

Search history is uppercase in navbar but not in landing searchbar

https://github.com/kodadot/nft-gallery/issues/4328

pay 30 usd

😍 Perfect, I’ve sent the payout
💵 $30 @ 25.66 USD/KSM ~ 1.169 $KSM
🧗 FNyt7T1xdbhN7dagf7yGYCRJuE3R45VmTCE3tjzy1rKxa7y
🔗 0x41d22f91878c4b222b6f5d420d98d011114e9e9f114e5eae63aa40af9c368ac4
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Make includeInboundPorts values override work.

fix https://github.com/istio/istio/issues/36644

I would think that this PR would need a release note as we are fixing something in the release and likely needing to fix this in 1.12.

I would think that this PR would need a release note as we are fixing something in the release and likely needing to fix this in 1.12.

Hmm a release notes is actually already included. Not sure why I added release-notes-none (I might want to add cherry-pick release 1.12 but somehow added the release-notes-none label). Sorry about that.

Cherry pick to 1.11?

Cherry pick to 1.11?

The option is not available at 1.11.

@jacob-delgado any chance to take another look? thanks!

In response to a cherrypick label: new pull request created: #36742


New test results workflow broken if a test step fails and returns empty results.log

An example of the flakiness analysis of test results failing is in the two builds after https://ci.chromium.org/p/dart/builders/luci.dart.ci.sandbox/dart2js-strong-linux-x64-firefox/1774
This build fails with a test.py timeout in the dart2js-extra tests step.  This step produces no results, and no results are uploaded to the cloud storage for build 1774 and this test suite.
On the next build, all the tests in this suite are seen as new (because they are compared with latest), and 50 of them are sent for deflaking.  All of the new tests are reported as passing or failing.  It also seems like all the dart2js_extra tests are missing from approved_results.json.   This is the result of my running the approved_results script at exactly this point when the latest results had no entries for this suite.  There was no warning that we were removing a whole suite's worth of approved results, that had no matches in the current results.
After this point, all the results from the suite show up as passing and failing new tests, and the failing ones turn the build red.
There should be better treatment of the case when a test suite fails to run, and produces no results. The approve_results script should detect if a lot of test's results get deleted, and show a warning.

I believe this is a problem in the recipe. The recipe should not upload results if the builder did not run correctly (infra failures / test.py timing out). The tools are able to handle gaps in the build numbers thanks to the latest mechanism. If test.py times out, the builder should fail with an infra problem, stop running any more steps (especially the upload step), and turn the builder purple. Then the address can be resolved and the scripts will continue to work normally (except no new results come in on the builders, but they don't do anything bad). Why didn't the timing out test.py step turn red? It says 0 tests ran, why didn't it time out that test way before the 20 min timeout for everything?
Or perhaps there's a legitimate case where test.py timing out should upload degraded test results? But I would argue we shouldn't smooth over these problems and turn the bot purple and deal with it. We should monitor the time taken for these steps and ensure they're not anywhere near the timeout, which should just be an overall safety. We could potentially drop the test.py timeout in favor of a bot wide timeout. Normally we should just be dealing with single tests timing out, not the whole thing timing out overall.
Handling these tools in the scripts using the data just makes things more complicated, and detecting this case would be a bit error prone, as it would also happen if a suite/many tests are just deleted (which is fine). I don't think that's the right place to handle this.

Would I be right to say https://chromium-review.googlesource.com/c/chromium/tools/build/+/1370052 would fix this problem? Unless that doesn't cause the whole builder to abort if there's a problem.

I don't believe this is a problem anymore and any remnants is the intended behavior.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 193 ms

Resolved: ClamAV performance has improved in b51a3a5.


Removing add_inventory_collection and has_inventory interfaces

Deprecated interfaces add_inventory_collection and has_inventory replaced by add_collection interface
Issue https://github.com/ManageIQ/manageiq/issues/17396
depends on all PRs in issue

:))
btw. specs for all influenced providers were successful.


Off-line use: Support usage with outdated mirrors

Some data centers are run completely firewalled off (or physically cut off) the public internet, relying on local mirrors of all necessary data. In such setups, the frequently-expiring timestamps (which are quite appropriate for the public internet) are unsuitable because refreshing the local mirrors so frequently would be too much of an operational burden.
So, it should be possible (but not the default) to have a configurable grace period for signature expiration, especially for timestamp.json but probably for the other files just as well. This grace period should be per-repository or perhaps per-registry; images created and signed within that off-line data center can still benefit from strict expiration enforcement.
The configuration mechanism for #395 would be a likely candidate location for also configuring this timestamp expiration grace period.

@diogomonica, @NathanMcCauley and I discussed this scenario a while back and one idea was to have these "mirrors" resign all content loaded into them with their own keys. There would be significant work to make that possible but what are your thoughts on that solution?
Potentially some hybrid might work well where the mirror substitutes its own root and timestamp keys and the client has a way to specifically trust known targets keys. In that scenario, the mirror would be able to timestamp but not modify targets because the client would have a pinned targets key. This feels like a significant amount of work but I have a feeling it'll be relevant to general delegations work too where a user may want to trust only certain delegations within a TUF repo.

I think it is very valuable to have end-to-end integrity and authorship guarantees, so I was thinking more along the lines of finding ways to deliver the existing signatures by original authors to the off-line data center and ultimately to clients within the data center.
Re-signing loses the end-to-end authorship guarantee (or, more precisely, introduces one more trusted party into the model). The hybrid model you propose would be a way around that, at the cost of confusing the trust model (we can no longer just say “the repository’s certificate”, users have to know about the root and targets keys and the difference).
In either case, AFAICS the benefit of re-signing is mostly in the ability to have current, non-expired timestamp signatures — but that is fairly meaningless within the off-line data center because even if the signature were legitimately expired and the clients should reload targets.json and learn about a newer targets.json tag mapping and new image versions, the newer targets.json and the newer images are not available. If the data center is pulling new images from the public internet once a week, for all intents and purposes nothing about the images or their signatures can change in the middle of the week, more frequent expiration seems not useful.
So, it seems natural to me to give up on the frequent timestamp expiration if it buys us the ability to keep using the original end-to-end signatures.

(FWIW re-signing in mirrors should AFAICS not be too much work: Instead of doing it within a server process on the mirror, have a mirroring cron job re-sign everything as if a client were copying the images into a private repository, and publishing signatures within that private repository: i.e. the client would load the upstream targets.json, create a changelist to generate an equivalent tag mapping, and then simply notary publish. This can work with a completely ordinary Notary server as it exists today, if we can configure the clients to use the mirror's URL and to bootstrap trust into the re-signed images. But again, I don’t find this kind of automatic mirroring particularly useful. (Re-signing as an indication of manual approval of an image for use does make sense, but also probably needs a different kind of automation.))

one of the things resigning the root in particular might provide is tracking of who brought the data into the offline data center. Not sure if that's worth having?

Tracking who brought the data in might be useful, but that aspect is not unique to Notary (if this is something that needs to be tracked, the same problem needs to be solved for every image and text file brought in)—and specifically for Docker images I’d expect that information to be already recorded in the configuration management tool (e.g. puppet) used to deploy and run the mirrors. There is no such substitute for the end-to-end authorship-proving signatures.¹
(The root.json signature format does technically allow adding extra signatures to e.g. record sign-off, but the TUF code would just ignore them; so recording both authorship and approved import in the file is technically possible but not implemented. Alternatively, clients could in principle be implemented so that they require tags to be signed by two different signers (pulling signatures from two different notary servers. Or, finally, TUF signatures can be extracted and used the way detached GPG or X.509 signatures are, so we can have multiple signatures for a single image that way.
All of this can in principle be done if anyone cares to implement it—but all of these approaches will need to somehow deal with off-line scenarios where the timestamp signatures expire faster than signatures can be mirrored, so we do need some kind of support for expiration grace periods.)

What's the current status of this?

@nfrush There's a scenario for this in the v2 project requirements.


[vcpkg] proper errorcheck during files installation

If during install_files_and_write_listfile an error happens in for (auto&& file : files) loop, every file in files is skipped due to "saved" error, even if fs.symlink_status(file, ec) succeeds.
This PR fixes the behavior, correct files aren't skipped.
Sample output of vcpkg install libressl[tools]:x64-windows
without fix - vcpkg complains every file after an error occurs
Building package libressl[core,tools]:x64-windows... done
Installing package libressl[core,tools]:x64-windows...
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\installed\x64-windows\debug\lib\crypto.lib: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\packages\libressl_x64-windows\debug\lib\ssl-47.lib: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\packages\libressl_x64-windows\debug\lib\ssl.lib: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\packages\libressl_x64-windows\debug\lib\tls-19.lib: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\packages\libressl_x64-windows\debug\lib\tls.lib: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\packages\libressl_x64-windows\etc: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\packages\libressl_x64-windows\etc\ssl: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\packages\libressl_x64-windows\etc\ssl\cert.pem: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\packages\libressl_x64-windows\etc\ssl\openssl.cnf: A required privilege is not held by the client.
...
   and about 100 wrong files
...
Installing package libressl[core,tools]:x64-windows... done

with fix - only proper errors
Building package libressl[core,tools]:x64-windows... done
Installing package libressl[core,tools]:x64-windows...
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\installed\x64-windows\debug\lib\crypto.lib: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\installed\x64-windows\debug\lib\ssl.lib: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\installed\x64-windows\debug\lib\tls.lib: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\installed\x64-windows\lib\crypto.lib: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\installed\x64-windows\lib\ssl.lib: A required privilege is not held by the client.
failed: C:\SRC\vcpkg\toolsrc\msbuild.x64.debug\installed\x64-windows\lib\tls.lib: A required privilege is not held by the client.
Installing package libressl[core,tools]:x64-windows... done

Moved, works for me

Thanks for the fix!


Set priorities

Purpose: Allow users to prioritize tasks according to their importance.
Implement a priority feature that allows users to define the importance and urgency of tasks.

I would like to solve this issue. It was not mentioned in the description how the priority should be presented. My idea is to allow the user to choose between 1-3 priority levels.

ok


Icon request: VFUN

URL of the site or app
https://vfun.valofe.com/
Logo resources for the icon
No response
Anything else?
No response

Here you go!
https://github.com/aegis-icons/aegis-icons/blob/master/SVG/VFUN.svg

:question: How to add icon(s) to Aegis?
:star: Support this project by giving a star! Just adding like to this comment is also appreciated.


Set-CsOnlineSchedule : Internal server error occurred. Please try again after sometime.

We are getting alot of errors when we try to set Holiday-Schedules with Set-CsOnlineSchedule
Sometimes it works but mostly we get that internal server error.
Set-CsOnlineSchedule : Internal server error occurred. Please try again after sometime.
In Zeile:52 Zeichen:5

$null = Set-CsOnlineSchedule -Instance $scheduleObject

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: ({ Identity = a3...dels.Schedule }:<>f__AnonymousType64`2) [Set-CsOnlineSchedule], Exception
FullyQualifiedErrorId : 100005,Microsoft.Teams.ConfigApi.Cmdlets.SetCsOnlineSchedule

We are from Microsoft Teams. Could you help to post the TenantId for us? It will help us to identity the logs from server side to see why there is an Internal server error. You can find the TenantId after you run Connect-MicrosoftTeams cmdlet. Thank you!

Account                          Environment Tenant                               TenantId

<EMAIL_ADDRESS>AzureCloud  49068363-8361-4607-9549-62b6b55794aa 49068363-8361-4607-9549-62b6b55794aa
Von: yinzh798 @.>
Gesendet: Donnerstag, 9. Juni 2022 19:18
An: MicrosoftDocs/office-docs-powershell @.>
Cc: Nicu Berger @.>; Author @.>
Betreff: Re: [MicrosoftDocs/office-docs-powershell] Set-CsOnlineSchedule : Internal server error occurred. Please try again after sometime. (Issue #9518)
Externe E-Mail. Vorsicht mit Links und Anhängen.
Courriel venant de l’extérieur. Prudence avec les liens et les documents qu’il contient.
We are from Microsoft Teams. Could you help to post the TenantId for us? It will help us to identity the logs from server side to see why there is an Internal server error. You can find the TenantId after you run Connect-MicrosoftTeams cmdlet. Thank you!
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/office-docs-powershell/issues/9518#issuecomment-1151393965, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOUQYPYV4A7QCRXJJO2BSDTVOIRMHANCNFSM5YGMA4LA.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

@nicuberger I can repro this in my test tenant, but so far only on TPM 4.4.1 using Windows PS 7.4.0 running on Windows 11. What versions are you using?
@yinzh798 please reach out to me internally.

@nicuberger I can repro this in my test tenant, but so far only on TPM 4.4.1 using Windows PS 7.4.0 running on Windows 11. What versions are you using?
@yinzh798 please reach out to me internally.

On Azure Automation Runbook Runtime version 5.1 and on a Windows 11 client with Powershell 5.1.22000.653

There is one server machine with transient DNS issue. We reboot the machine and the issue is resolved. @nicuberger could you try again and see if the issue is resolved?

It is resolved thanks for the reboot!
Von: yinzh798 @.>
Gesendet: Freitag, 10. Juni 2022 22:41
An: MicrosoftDocs/office-docs-powershell @.>
Cc: Nicu Berger @.>; Mention @.>
Betreff: Re: [MicrosoftDocs/office-docs-powershell] Set-CsOnlineSchedule : Internal server error occurred. Please try again after sometime. (Issue #9518)
Externe E-Mail. Vorsicht mit Links und Anhängen.
Courriel venant de l’extérieur. Prudence avec les liens et les documents qu’il contient.
There is one server machine with transient DNS issue. We reboot the machine and the issue is resolved. @nicubergerhttps://github.com/nicuberger could you try again and see if the issue is resolved?
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/office-docs-powershell/issues/9518#issuecomment-1152723121, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOUQYPYBFI3CQYTJ66MM7XLVOOR4JANCNFSM5YGMA4LA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

The issue I could repro has been fixed in TPM 4.4.3-preview

Hello Jens
On Azure Automation Runbook Runtime version 5.1 and on a Windows 11 client with Powershell 5.1.22000.653
Von: Jens Trier Rasmussen @.>
Gesendet: Freitag, 10. Juni 2022 09:04
An: MicrosoftDocs/office-docs-powershell @.>
Cc: Nicu Berger @.>; Mention @.>
Betreff: Re: [MicrosoftDocs/office-docs-powershell] Set-CsOnlineSchedule : Internal server error occurred. Please try again after sometime. (Issue #9518)
Externe E-Mail. Vorsicht mit Links und Anhängen.
Courriel venant de l’extérieur. Prudence avec les liens et les documents qu’il contient.
@nicubergerhttps://github.com/nicuberger I can repro this in my test tenant, but so far only on TPM 4.4.1 using Windows PS 7.4.0 running on Windows 11. What versions are you using?
@yinzh798https://github.com/yinzh798 please reach out to me internally.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/office-docs-powershell/issues/9518#issuecomment-1152040276, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOUQYPZSJ5D7SRYJLNSYBZDVOLSEXANCNFSM5YGMA4LA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Update virtual-machines-n-series-linux-support.md

test

#sign-off

@rishabv90 - it looks like you should be working in the private repo: azure-compute-docs-pr .  In this (public) repo, only the list 'author' can sign off.  So, you can close this pr and open one the private repo or you can wait until @ju-shim reviews and approves this one.
@ju-shim -
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


libsixel backend

I've found libsixel to be superior to imagemagick, or at least much faster.
https://github.com/ctorney/matplotlib-backend-sixel/blob/592380fc46dee5988057c72c6bbc0a9d312acebc/matplotlib-backend-sixel/__init__.py#L23
# imagemagick
p = Popen(["convert", "-colors", '16', 'png:-', 'sixel:-'], stdin=PIPE)

# libsixel
p = Popen(["img2sixel"], stdin=PIPE)

I understand there is also a python interface, if that were preferred.

I don't think the difference is really noticeable and imagemagick is more widely used


implement count-mean-min-sketch

The wiki page for CMS describes a variant with a different query function called count-mean-min-sketch; this tries to reduce bias in the estimate by subtracting out the bias when reporting.
The big change here is to return the median value instead of the min on query.
This blog post claims that count-mean-min-sketch will provide better estimates in low to moderately skewed data, where CMS becomes less accurate.
Here's how the CMS performs on moderately skewed data:

Here's how count-mean-min-sketch does, estimating the same moderately-skewed distribution:

This paper's worth looking at as well:
![image](https://cloud.githubusercontent.com/assets/69635/19693289/313dd9a6-9a98-11e6-
8ca6-c5caf043785a.png) (EDIT: image link is now busted. This was a screenshot of the paper section describing count-mean-min-sketch.)
The paper also discusses how to combine this idea with #460 to get a count-mean-min-sketch with conservative update.

Hi, I'd like to take this up, can you please point me in the right direction.
What I understand from the issue is that 'return the median value instead of the min on query.' and use this paper . Can you be a little more descriptive ? Also, which part of the code should I be looking at ?


Update initial schemas

@ajcvickers @javiercn
This seems pretty odd behavior, but the ordering of the properties seems to be the only diff, but that causes add-migration to generate add/drops...

PR targeting 2.1 is here: https://github.com/aspnet/templating/pull/311


Update to 1.20.4

Checked and seems to all be working!

Fixed a few things and checked myself. Will merge and release


Fix js error in layouts.js

Let's fix the remaining JavaScript error

PS: the js assets should be rebuilt, but I've used termux to create this PR, and I still have to fully configure it :wink:


Latest SPI update v0.5.x

Include :

Split single Github graphql request into two https://github.com/redhat-appstudio/service-provider-integration-operator/pull/140
Token matching for Quay https://github.com/redhat-appstudio/service-provider-integration-operator/pull/128
Use UBI as our base image  https://github.com/redhat-appstudio/service-provider-integration-operator/pull/138
Change the base image to the latest ubi-minimal  https://github.com/redhat-appstudio/service-provider-integration-oauth/pull/99

/retest

/retest-required

/retest

/retest

/retest


[Urgent] Unable to load superset stuck in welcome page post login

Superset docker-compose deployment not proceeding after login. Returns 404 for  /static/assets/images/loading.gif
How to reproduce the bug

Clone superset repo.
cd superset and use docker-compose up -d to bring up containers.
Open developer tools and log in to Superset with admin creds.
Post login it redirects to http://localhost:8088/superset/welcome/ and is stuck there

Expected results
Should Proceed to further screens.
Actual results
Page is stuck at http://localhost:8088/superset/welcome/ and in developer tools, under Network we can see http://localhost:8088/static/assets/images/loading.gif returning 404.
Screenshots

Environment

browser type and version: Chrome - Version 94.0.4606.61 (Official Build) (64-bit)
superset version: Observed in docker images on both apache/superset:latest-dev (sha256:a430759eb60d3dc1ddf905eb5b3afdeccdd17c8ece7370c71901ed1b68f5fbbb) and apache/superset:latest (sha256:f7afd84becc688f239228b2460910e316c1e140baf943115c3eca1be00ef6ccc)
python version: 3.8.12 (python verso=ion found in apache/superset:latest-dev image)
node.js version: node:16 (sha256:ed7bbdf4d76e3083f22827edc444b061b6562cb08341be973bfde0a972b65272)(docker image)
any feature flags active: not sure. nothing has been changed in code/config post cloning.

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
I have cloned the repo and used docker-compose to bring up the system. I can also see that containers superset_worker_beat, superset_worker to be unhealthy.

Superset app logs
<IP_ADDRESS> - - [12/Oct/2021 18:00:24] "GET /health HTTP/1.1" 200 -
2021-10-12 18:00:24,588:INFO:werkzeug:<IP_ADDRESS> - - [12/Oct/2021 18:00:24] "GET /health HTTP/1.1" 200 -
<IP_ADDRESS> - - [12/Oct/2021 18:00:25] "GET / HTTP/1.1" 302 -
2021-10-12 18:00:25,596:INFO:werkzeug:<IP_ADDRESS> - - [12/Oct/2021 18:00:25] "GET / HTTP/1.1" 302 -
2021-10-12 18:00:25,791:DEBUG:superset.stats_logger:[stats_logger] (incr) welcome
<IP_ADDRESS> - - [12/Oct/2021 18:00:25] "GET /superset/welcome/ HTTP/1.1" 200 -
2021-10-12 18:00:25,818:INFO:werkzeug:<IP_ADDRESS> - - [12/Oct/2021 18:00:25] "GET /superset/welcome/ HTTP/1.1" 200 -
2021-10-12 18:00:25,894:WARNING:superset.views.base:404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
<IP_ADDRESS> - - [12/Oct/2021 18:00:25] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
2021-10-12 18:00:25,895:INFO:werkzeug:<IP_ADDRESS> - - [12/Oct/2021 18:00:25] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -

+1 here

+1 here too, installed yesterday and bumped into the same issue
Ubuntu server 20.04, Docker

I had the same issue. Wait for 10 or 15 minutes then npm has installed all packages. This is imho a bug

Docker didn't work for me, I checked out the docker/docker-frontend.sh script, and ran those commands manually. i.e.:
# get nodejs from conda-forge in my case
conda install -c conda-forge nodejs
cd superset-frontend
npm install -f --no-optional --global webpack webpack-cli
npm install -f --no-optional
npm run dev

My guess is some of the init scripts should have run this, but because nodejs is not installed it skipped it. I guess the installation docs can be improved on this.

I had the same issue. Wait for 10 or 15 minutes then npm has installed all packages. This is imho a bug

Agree with this feedback. +1 for me.

Docker didn't work for me, I checked out the docker/docker-frontend.sh script, and ran those commands manually. i.e.:
# get nodejs from conda-forge in my case
conda install -c conda-forge nodejs
cd superset-frontend
npm install -f --no-optional --global webpack webpack-cli
npm install -f --no-optional
npm run dev

My guess is some of the init scripts should have run this, but because nodejs is not installed it skipped it. I guess the installation docs can be improved on this.

To run these I had to first run:
export NODE_OPTIONS=--openssl-legacy-provider

I am getting the same error here. After waiting around 20 min it finished installing and got an error with webpack installation, on superset_node:
superset_node            | webpack 5.52.1 compiled with 48 errors and 9 warnings in 138433 ms
This is the kind of problem that discourages a lot of people who are having their first contact with the project following the tutorial. I would like to fix it, is anyone already working on it? Any suggestion on the best approach?
Comment: I didn't have this issue when running docker-compose-non-dev.yml.

can you share the logs of superset_node.

if you see something fail in the installation of packages.
for more removing node_modules working.
Also if you  see something related to CYPRESS INSTALL ISSUE
add this to environment : CYPRESS_CACHE_FOLDER='/app/.cache/Cypress'

Docker didn't work for me, I checked out the docker/docker-frontend.sh script, and ran those commands manually. i.e.:
# get nodejs from conda-forge in my case
conda install -c conda-forge nodejs
cd superset-frontend
npm install -f --no-optional --global webpack webpack-cli
npm install -f --no-optional
npm run dev

My guess is some of the init scripts should have run this, but because nodejs is not installed it skipped it. I guess the installation docs can be improved on this.

I had this same issue, running those node items solved my lockup on docker-compose. Looks like non-dev works fine, but the dev docker-compose has this challenge.

This is the kind of problem that discourages a lot of people who are having their first contact with the project following the tutorial. I would like to fix it, is anyone already working on it? Any suggestion on the best approach?

Agree this issue is a bit discouraging, requires getting your hands dirty.

I think the problem was solve by following this steps:

Remove Node stage codes from Dockerfile
Remove node_modules from superset-frontend dir if exist
Run cd superset-frontend in cmd
Run npm install&&npm run dev
Run docker-compose up
Hopefully it will be work

This worked for me docker-compose -f docker-compose-non-dev.yml up

the problem is in the image of the js node. To fix it, you need to fix version nodejs . to do that u need to fix the file docker/docker-frontend.sh like this:
.....
apt install -y chromium
add new strings
apt install -y npm
npm install npm -g
npm install -g n
n 16.18.1
n will install node js with version 16.18.1 .  by the way npm also need some packages to start correctly

This worked for me docker-compose -f docker-compose-non-dev.yml up.  Thank you @sukupandachu

How can we get this in dev, running docker-compose up?

I'm closing this old issue as it pertains to a resolved issue from 2021-22 and even if a new version of this problem occurs in the future, it would have a different cause.  Folks who experience something similar should please search for a newer issue and, if none exists, either post in the Superset Slack chat or create a new issue if you believe it's a new bug.

I'm closing this old issue as it pertains to a resolved issue from 2021-22 and even if a new version of this problem occurs in the future, it would have a different cause. Folks who experience something similar should please search for a newer issue and, if none exists, either post in the Superset Slack chat or create a new issue if you believe it's a new bug.

i'm having this same exact issue...:
https://github.com/apache/superset/issues/24579#issuecomment-1662806410

That doesn't seem like the same issue as this old one, your error code there is The CSRF session token is missing and there's no mention of CSRF in any of the posts on this issue.  But I'm glad you found that issue, that one does seem like the right place to discuss the problem you're having.

changing the node verison to v16.9.1  can help u

i am facing the same issue as reported. i tried docker-compose -f docker-compose-non-dev.yml up it worked, but now while logging in using admin id, it does not go through. anyone help on this please.

Same issue here...after battling to get the default creds issue resolved.

Docker didn't work for me, I checked out the docker/docker-frontend.sh script, and ran those commands manually. i.e.:
# get nodejs from conda-forge in my case
conda install -c conda-forge nodejs
cd superset-frontend
npm install -f --no-optional --global webpack webpack-cli
npm install -f --no-optional
npm run dev

My guess is some of the init scripts should have run this, but because nodejs is not installed it skipped it. I guess the installation docs can be improved on this.

did this, found 24 vulnerabilities

including malware?

did anyone else find this? should I worry?

Same issue here, just pulled the superset repo and ran docker as instructed in the docs:
git clone --depth=1  https://github.com/apache/superset.git
docker compose up
So im pretty sure this issue needs to be re-opened...

I don't know if my solution is correct but what work for me is adding
apt install zstd

to docker_frontend.sh file before npm run dev
looks like simple-zstd requires it in the image
https://www.npmjs.com/package/simple-zstd

I think https://github.com/apache/superset/pull/30279 intends to take care of any remaining zstd issues.


Support for Hyundai India

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Would like to be able to choose the country of Bluelink account.
Include the logs of the end point from Data in HA if this is a sensor
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

This is duplicate of #337.  We will need someone to sniff the traffic.


proxy.golang.org: don't cache /@latest for modules that no longer exist at the upstream head revision

In gomodule/redigo#440, a nested github.com/gomodule/redigo/redis module was created and subsequently removed from the github.com/gomodule/redigo repository: today, the nested module does not exist at the head revision of that repo, and also does not exist in the latest tagged release of the parent module (github.com/gomodule/redigo).
In https://github.com/gomodule/redigo/pull/440#issuecomment-621892705 and https://github.com/gomodule/redigo/pull/440#issuecomment-621930004, I noted that proxy.golang.org was still serving an old commit for /@latest for the nested module over an hour later, even though GOPROXY=direct correctly reported that there was no latest version of that module, and even though proxy.golang.org did know about a higher (and later) pseudo-version of that module.
As a workaround, the owners of the repo had to tag an explicit release of the nested module, even though they did not intend for anyone to actually use that release.
I don't think that workaround should have been necessary: I think proxy.golang.org should not serve known-stale contents for the /@latest endpoint. That endpoint should be invalidated whenever a newer version of the named module is successfully fetched, even if that version is not itself latest (as interpreted by the go command).
That may mean that /@latest transitions from advertising a version of the module to no longer advertising any such version, but that behavior is no worse than what would happen if the repo owner took some other drastic action to remove the module — such as publishing a commit on the default branch with all of the source code deleted, or publishing a commit with the module line declaring some other path. Regardless of the reason, proxy.golang.org should view the affirmative non-existence of a module as a valid “latest” state for that module, and not get stuck advertising “the last version that did exist”.
This only really matters for modules that never explicitly tagged any release or pre-release version, since the go command does not consult the /@latest endpoint unless the list of release and pre-release versions is empty.
(Note that, even if the /@latest endpoint itself does not advertise any version, the proxy should continue to serve all previously-fetched versions of any module with a suitable license. I am not proposing that we evict any explicit versions from the cache — only the /@latest endpoint itself.)
CC @jayconrod @matloob @katiehockman @heschik @hyangah @stevenh

Sorry, but I don't understand what the actual feature request here is. My best guess is:
module X has an @latest entry.
module X/Y has an @latest entry.
attempted fetches of module X/Y begin failing -- possibly because the origin is flaky, possibly because it's been deleted, or possibly because something is internally wrong with proxy.golang.org.
module X continues to work.
In this situation, you're saying that we should assume that X/Y is failing because it's been deleted, check that a version of X later than the version of X/Y has been fetched, and forget the @latest for X/Y?
If that's wrong please be very specific about the proposal. I can't imagine a version of this that I think is a good idea so I'm struggling to understand the suggestion.

fyi - https://github.com/golang/go/issues/32239 is related. We tried this as another way to address this type of issue, but we had to give it up because of noticeable performance degradation.

In this situation, you're saying that we should assume that X/Y is failing because it's been deleted, check that a version of X later than the version of X/Y has been fetched, and forget the @latest for X/Y?

Behaviorally, yes.
But I would phrase the causality of it a bit differently:

At time τ₂, X/Y@latest is fetched and resolves to (pseudo-)version v₁, with metadata indicating commit timestamp τ₁.
At time τ₄, module X/Y@yyyyyyyyyyyy is fetched and resolves to version v₃, with metadata indicating commit timestamp τ₃ (where τ₄ > τ₃ > τ₂ > τ₁).

Since τ₃ > τ₁ and τ₄ > τ₂, we can infer that the state of the repo probably changed at some point at or prior to τ₃, and thus the @latest cache entry from prior to that point in time is suspect. So we should remove the cache entry, without replacing it.
The next time X/Y@latest is requested (at τ₅), we should re-resolve it.

If that happens to result in failure, that's fine: we should serve the new failure instead of the suspected-stale v₁.
If it happens to continue to resolve to v₁, that's fine too: we can cache the new result until we see a version newer than τ₃ (or perhaps τ₄ or τ₅, depending on how much of a race we want to allow — and how much, if any, we are willing to expand the database schema).

We can't tell whether a module version is on the default branch, so we would have to invalidate @latest on any commit to any branch that we became aware of. If we then experienced a transient failure refreshing @latest, that would break users.
I think this is a very specific workaround to a very specific problem that has better solutions and causes some amount of collateral damage. It certainly increases complexity. I would rather not do it.

I agree that this seems like a lot of complexity for a pretty niche situation. I definitely empathize with @bcmills' point that we don't want users to have to a special workaround for this, but the tradeoff of this could harm other users (who then may also need a workaround, etc etc). I'm also not confident that I know every single side effect of this change.
If this becomes a bigger problem that more people experience, then let's re-visit this. For now, a reasonable solution is to use https://github.com/gomodule/redigo/pull/440#issuecomment-621933191 as a guideline if anyone else enounters this. Maybe documenting it if that issue isn't good enough.
This also relates back to https://github.com/golang/go/issues/30134, where we could do more here if we had more information from the error message (like @heschik alluded to). It's difficult to make the right decision about whether or not to drop one of our cache entries if there was a go command error, since it could be from a legitimate error that we can save, or it could be from a transient server error that we should throw away.

Could a user exploit this to break a repo simply by putting in a PR that is then cached in this way?

@stevenh, no: the go command refuses to use commits that are not reachable from at least one tag or branch, and unmerged PRs are not reachable from any tag or branch.

We can't tell whether a module version is on the default branch, so we would have to invalidate @latest on any commit to any branch that we became aware of.

Yes, that's true.

If we then experienced a transient failure refreshing @latest, that would break users.

It would not break any existing users, since they are all requesting explicit versions. It could indeed break new users of the module, but a module author can already break new users of the module in all sorts of ways (such as by pushing a latest version that explicitly removes all of the source code from within the module). I think it clearly is the proxy's responsibility to provide continuity for existing users, but ensuring that new users can always find a viable latest to use seems outside its charter.

I agree that this seems like a lot of complexity for a pretty niche situation.

A similar approach that would reduce overall complexity would be to apply the same TTL for latest that we apply for branch-to-version resolution in general. (After all, latest is just the branch-to-version resolution for “the default branch”.)
That would have fixed github.com/gomodule/redigo/redis after an hour, instead of requiring explicit tagging.
To me the source of complexity here is the desire to treat @latest as somehow different from other branches — and I don't agree that it is different.

The reason that proxy is treating @latestdifferently because that's part of the module mirror's promise (no more left-pad) and affects end users. There are many tools that do not use the versioned tags. For example, the vscode go extension depends on many tools and many of them still go by pseudo-versions.

It's not even that. As far as I recall this is exactly the same behavior everything else gets. If a module goes from existing to failing to download, we'll continue to serve it for as long as we can. That goes for branches, tags, pseudoversions, everything.

If a module goes from existing to failing to download, we'll continue to serve it for as long as we can. That goes for branches, tags, pseudoversions, everything.

That seems like a major problem. What happens if the branch is, say, security-backports, and the module author decides to rename the branch to lts-security-backports? Users who set up a branch-oriented workflow will end up stuck on the last update, where they should have gotten an explicit error.

The reason that proxy is treating @latest differently is because that's part of the module mirror's promise (no more left-pad) and affects end users.

The “mirror's promise” is that existing users will be able to continue to use the dependency versions that they were already using. It does not promise that the latest version of a module will always be a usable version of that module.
As noted in https://github.com/golang/go/issues/39007#issuecomment-628351207, it is already possible for a module author to break latest for new users if they so choose, and in the case of left-pad the decision to break users seems to have been intentional.

There are many tools that do not use the versioned tags. For example, the vscode go extension depends on many tools and many of them still go by pseudo-versions.

Expiring the cache entry for latest would not prevent any of those existing users from continuing to use the versions they already depend on.

One of the primary goals of the proxy is to protect users from flaky upstreams, in particular outages. Since the go command gives us no way to distinguish outages from deliberate actions, we are required to be conservative and not try to infer intent.
Adding new dependencies is not a trivial use case and it is not acceptable for the ecosystem to break the next time some origin server goes down for a day. I don't think that's negotiable but if you would like to argue that case, this is probably not the place to do it.
If the fix for #24031 isn't sufficient to cover the security use case that sounds like a critical problem with it. The vast majority of people are presumably not going to be tracking a branch.
I don't think this discussion is going anywhere and I think this issue should be closed.

Here's another poor interaction from caching @latest for modules that no longer exist, from the #modules channel in Gopher Slack (https://gophers.slack.com/archives/C9BMAAFFB/p1632295080119400):

Having some problems with go install - it takes an old version of package for some reason (see v1.4.0 in output)
$ go install github.com/tetafro/godot/cmd/godot@latest

go: downloading github.com/tetafro/godot/cmd/godot v0.0.0-20210115153532-96ff7da53d7b
go: downloading github.com/tetafro/godot v1.4.11
go: downloading github.com/tetafro/godot v1.4.0

It works correctly when I run it with @v1.4.11. Is there a way to use @latest with actually latest version? Maybe place go.mod in cmd/ directory or some other hack? What’s the common way to deal with it?

In the current release of the parent module (v1.4.11), the package github.com/tetafro/godot/cmd/godot is in the module github.com/tetafro/godot, as it arguably should be. However, until https://github.com/tetafro/godot/commit/e5d5541c86b65d6d9fcbf2a918fe55f00405901d it was in its own (nested) module, so that module is still served as latest when someone looks up github.com/tetafro/godot/cmd/godot@latest in the proxy.
It is possible for the module author to fix the problem by restoring the go.mod file, with a retract directive, in an off-master commit and tagging that commit with something like cmd/godot/v0.0.0-retracted, but that workaround is hard to discover, delicate to apply, and fairly counterintuitive.


How to using

i really dont undertstand how using this extension, can someone give tutorial or anything ?

Hi @dwiansyah06,
Already found out how to set it up? I'm also quite lost and it concerns me that nobody replayed here...

thanks for your reply @stijns96
i know how setup this, i dont understand how to using this extension for my article. is this extension make automatic SEO or what ?

@dwiansyah06 to be honest, I stopped using Directus. The tool is really good and powerful, bit a bit overkill as CMS for my simple website projects.
I installed this extension and already found quite some bugs according to dark mode etc.
Because of this and some other UI stuff, I quite quickly uninstalled it. So to be honest, I'm not even that sure what it does...