[FEAT] Ability to include full context including all parent decks leading up to the subdeck the current card is in.

Is your feature request related to a problem? Please describe.
Currently, if you have cards that are present in Files or subdecks with the same name, it can be hard to tell the exact topic that that card relates to.
Say for example I'm studying different programming languages and I have a bunch of flashcards on some programming topic. Usually the topics will be similar and thus have similar names. This means that if I may have a question along the lines of "How do you implement an interface?". If I'm only studying one language this is easy but if I just want to review all my flashcards, the answer to this can vary a lot depending on the language that the question is related to.
Looking at the context (via the heading context setting) doesn't help here because these can still be ambiguous. Classes > Fields for example lets me know that it's an OOP language but it's still not enough to know whether the question is related to Java, C#, C++, etc etc etc.
The above example is contrived but you get my meaning.
Describe the solution you'd like
I'd like an option to include full context for where the card is located. This could be in the card name by allowing it to show the "Full Context Card Names" where instead of showing "Deck : 1" You could have it show "ParentDeck > Subdeck1 > Subdeck2 > Deck : 1".
For example: currently mine shows "Types: n". However, this deck is located within a subdeck in ProgrammingLanguages > C# > Types. So instead the card name could show "ProgrammingLanguages > C# > Types : n".
Additional Context:
I can provide some visual examples if the explanation isn't clear enough.

I'm not sure how you'd implement it but you could just show the path from the root of the vault?
So if I have folders such that they were in the folder structure Outer > Middle > Inner > Note, you could show it in the note as a path from the outer most. Showing it in the anki way with :: would work too. Instead of showing the tags at the top you'd Show Outer/Middle/Inner/Note. You'd show it instead of the deck name/tag that currently sits at the top of the card.

So here instead of showing "Libraries" in my case it would show "Programming/Languages/Java/Swing".


Use Docker BuildKit, support multiple CPU architectures

Description
This PR introduces support for Docker Buildkit and makes it the default way to build containers when executed with a supported version of Docker. Compatibility with the old build system is maintained.
Also introduces the ability to target a specific CPU architecture with docker, allowing builds of cross-platform containers where supported using the --platform switch in Docker.
All test suites have been updated to supported OS versions. Cross-platform build tests are also present.
Issues Resolved
Proper solution for #337
Check List

[x] All tests pass. See TESTING.md for details.
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable.

Nice work. Thanks @RulerOf

Shipped in 2.12


Bar chart: error showing tooltip with different number of columns

The chart lookup for mouseover functions tries to determine the value of a and b on this line: https://github.com/masayuki0812/c3/blob/master/c3.js#L3864
It then attempts to read the value of null when b is null.
JSFiddle: https://jsfiddle.net/gv2tfkzf/6/
Method to reproduce: hover over the second bar group

Lulz, wow. That's weak. Thanks for the report, marking as bug.

:smile_cat:


03_mqtt_socketService.js fails to get a session

See lines 56-57 when session.enable is true in .../global/session/index.js.

This is addressed by 3131d3e.  After discussion with @jkamke, we concluded that we should reconsider the use of sessions with the goal of reducing it or eliminating it entirely.

See #34


Does not work for WSL

It is not working in WSL. I always get the error: "Command 'Fluent UI: Enable' resulted in an error command 'fluent-ui-vscode-enableEffects' not found.

just enable it in a windows folder, it will work when in wsl

I tried both installing in wsl2 and uninstalling from there

open a windows folder in vscode, not a wsl one. install fluentui. disable transparency effects in the extension settings. run the enable command. it will complete and when you open a wsl folder the changes will be saved.


Performance fixes

This PR is a follow-up on databricks/databricks-sql-nodejs#204. After changes made in that PR, downloading CloudFetch results sometimes started to fail with ECONNRESET: socket hang up error. After debugging, I've found a root cause. Even though all the library code is Promise-based, since Promises are microtasks, enqueueing a lot of promises may block macrotasks execution for a while. Usually, there are no much microtasks scheduled. However, when fetching a CloudFetch results, after first set of files are downloaded and being processed immediately one by one (and chunk by chunk), event loop easily gets clogged for enough time to break connection pool. http.Agent stops receiving socket events, and marks all sockets invalid on the next attempt to use them. The fix allows to clean up a microtasks queue and allow Node to process macrotasks as well, allowing the normal operation of other code.
This change has almost no effect prior to databricks/databricks-sql-nodejs#204 changes, but after databricks/databricks-sql-nodejs#204 the difference is really noticeable (see screenshots under the spoilers). Memory consumption and sockets usage remains basically the same, but event loop now is executed much more evenly, without long delays (which is also reflected on CPU graph):

Before

After

Also, another (smaller) improvement is increasing connection pool when CloudFetch is enabled, which allows to download data a bit faster.

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (9b03de3) 88.91% compared to head (57e5637) 88.86%.

Files
Patch %
Lines

lib/connection/connections/HttpConnection.ts
0.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #207      +/-   ##
==========================================
- Coverage   88.91%   88.86%   -0.05%
==========================================
  Files          58       58
  Lines        1344     1347       +3
  Branches      217      218       +1
==========================================
+ Hits         1195     1197       +2
  Misses         99       99
- Partials       50       51       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Decode blocks from RLP

What was wrong?
Currently the testing framework creates the Block and Genesis Block datatypes  from the various fields available in the fixture json files. There are a couple of problems with this approach

The ethereum tests repository looks upon a lot of these json fields as an aid for human readability and looks at the rlp fields as the primary source of the data.
If new fields are added to the Block, Header, Transaction and Withdrawal datatypes,  patches will have to be added to fix the testing logic

How was it fixed?
The specs need to derive the data structures for testing by decoding the rlp instead of using the json fields. This will also serve as an additional layer of testing for the rlp decode logic within the specs. The current commit makes that change and also re-factors some of the code in the state test helper.
Cute Animal Picture

Converting this to a draft until the upstream issue with the Shanghai Withdrawal tests is fixed


Revamp readme pt2

Summary
This PR introduces the second round of updates and changes for the repo README ahead of the release of version 0.8. Changes focus on the following sections.

Overview
Description of features
Optional installs and migration guide reflecting the requirement of Qiskit 1.0 or above.

These chances are proposed with the incorporation of Qiskit Algorithms in mind. Therefore, it would be best to merge this code once https://github.com/qiskit-community/qiskit-machine-learning/pull/817 has been merged.
Details and comments

Closes https://github.com/qiskit-community/qiskit-machine-learning/issues/790.
Closes https://github.com/OkuyanBoga/hc-qiskit-machine-learning/issues/40.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.237%

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
2020

Relevant Lines:
2190

💛  - Coveralls

With the change to the Optional Install I think the source for the Getting Started page, around optional installs should be updated too https://qiskit-community.github.io/qiskit-machine-learning/getting_started.html

I'll update the documentation page too. In the meantime, has this Nlopt installation error appeared before in algorithms? ERROR: Failed building wheel for nlopt
Could it be related to the compiler set-up in the CI environment?

In the meantime, has this Nlopt installation error

From what I see the NLOpt optimizers were never tested in CI that algorithms has. NLOpt has installation info that talks about compilation but does not include Mac though searching finds some discussions elsewhere. Depending on how much effort its felt to try to get this working the alternative is just to skip installing/tests for those envs where installation is problematic - the unit tests already have the optional check so it would just come down to installing or not.

I agree on parking support for NLopt in the CI for now. I reverted the changes that aimed to do this and included instructions to manually install it (optionally if required by the user). I took this opportunity to update the RST files too to reflect the changes in the Readme.

Note that I updated the BaseStateFidelity link in README.md, which will reflect the updated documentation as soon as it comes online after the 0.8 version rollout. This update is documented in https://github.com/qiskit-community/qiskit-machine-learning/issues/823, therefore this PR also closes this issue in advance.


Proposal: introduce Wireit plugins

One huge limitation to Wireit currently is configuring input and output files. It's pretty easy for glob patterns of file inputs and outputs and the actual tool configuration to get out of sync. It's also not uncommon slightly to over include or under include file inputs and outputs. And when you fix a misconfiguration in one package, you may not notice it or remember to do it in another.
The fortunate bit is TypeScript knows what files it processes and where it puts them based on my configuration, so does ES Lint and Rollup...you get the picture. It would be handy if you could optionally use Wireit plugins that read that your tool configuration and configure files and outputs so that you don't have to.  They could also configure other reasonable defaults. For example, TypeScript could default to only clean if files are deleted when in incremental mode.
This could also improve fingerprinting for commands by not ignoring caches when the repo-wide lock file changes. An ES Lint plugin could re-run only if the exact version of eslint or it's plugins changes...rather anything in the lock file being updated.

Thanks @kwangure. How would you feel about a tool that automatically maintained your wireit config by synchronizing it with your tsconfig, rather than being a plugin that runs every time wireit does?

It might be an acceptable compromise if it helps keep Wireit simpler.
That said, I'd probably add said tool as a Wireit command...and make it a dependency of every tsc command in order to maximize its utility. At which point I'd be wishing Wireit just did that for me under the hood.

So, I could do as proprosed and create a bash or Node script which updates the wireit section of the package.json. However, would wireit even see that? For example:

the compile script depends on the update-wireit script
the update-wireit script updates the dependencies of the compile script
wireit won't see the updated dependencies, AFAIK

Basically, developers would have to run the compile twice or know to run the update-wireit script before running the compile.
A plugin system would give us the ability to simplify repetitive tasks by allowing them to be shared across packages and repositories. I have to put the same scripts across some 30+ packages in this mono-repo and that is difficult to maintain.
Alternatively, if wireit supported a .wireit.js file instead of only the wireit section in the package.json, that could fulfill my needs to be able to generate the definition through code instead of through static data alone.

what if instead of plugins (which tend to be a fragile part of any ecosystem) wireit publishes a public API. For example I know it doesn't ship the type definition files at the moment. A published API would make experiments like wireit-visualizer  pretty straight forward and then folks could build on TOP of wireit rather than having code run through it.


Add graph for free home directory usage %

NFS disk filling up is one of the leading cause of outages. This PR adds:

An example node_exporter deployment that exports metrics for filesystem usage, so we can add a...
Chart in the JupyterHub dashboard, showing % of free space left.

This would be a decent place later to add a per-user usage stats metric collector eventually, not now though :)
Ref https://github.com/2i2c-org/infrastructure/pull/1992

@GeorgianaElena I'd love to keep it in the same dashboard - IMO monitoring isn't complete if this (which is one of the largest source of outages) isn't present. And users should deploy something like this.
@consideRatio How strongly do you feel about this? I'd love to keep it as is, as 'shared storage' generally has more specific connotations around who all have access to the storage, and 'home directory' is a fairly well understood concept. However, I have limited cycles and time, so if you feel really strongly about it, I'd disagree but do it anyway because of just lack of time :) I am worried that instead this PR will just sort of 'hang here' forever if we get into a naming discussion, so my goal is to avoid a conversation about naming at all costs. So lmk if you feel strongly.

To explain the confusion bit, often shared compute environments have a private space ('your home directory') and a shared space that is visible to everyone. In our case, we re-use the home directory volume for shared storage, but that's not always the case. Usually your 'shared space' filling up shouldn't cause server startups to fail, but your home directory filling up would.
"Do not participate in discussions about naming things" is perhaps going to be the hardest of my new years' things to keep haha.

This is awkward as I strongly value thoughtful naming, but don't want to push you into things you don't want to consider. Yet none of us should invest time in details that won't matter, but I do think this will matter - so I'm going for it.
To offload you from doing work I opened this PR to this PR branch https://github.com/yuvipanda/grafana-dashboards/pull/1.

I clarified this with @consideRatio during a prior scheduled video call, but wanted to re-iterate :)
I completely agree that thoughtful naming is really important! I'm mostly just trying to recognize and understand my own problems with leaving things incomplete, and PRs left hanging open. So my goal is to just not have a personal opinion wherever possible, and unconditionally accept the other person's suggestion. No judgement at all!
So I deeply appreciate that you made the PR, @consideRatio. My goal is to recognize the limits of my own time, and reduce the amount of work I do. Your PR made that very easy! \o/


Class transform does not keep comments

For example this code:
/**
 * File comment
 */

/**
 * Class comment
 */
function Employee() {
  this.alive = true;
}

/**
 * Method comment
 */
Employee.prototype.setSkills = function(skills) {
  // Some comments in here
  return function() { return skills; };
};

// some more comments at the end of file

Is converted to the following:
class Employee {
 constructor() {
   this.alive = true;
 }

 setSkills(skills) {
   // Some comments in here
   return () => skills;
 }
}

As can be seen, all comments for the constructor and methods have been stripped away.

This is still an issue for me with 1.3.2, I also tried 1.3.1 and 1.3.0 but comments are always stripped.

Could you provide an example of the code where comments get dropped.
For me it works just fine. For example converting the above code results in:
/**
 * File comment
 */

/**
 * Class comment
 */
class Employee {
 constructor() {
   this.alive = true;
 }

 /**
  * Method comment
  */
 setSkills(skills) {
   // Some comments in here
   return () => skills;
 }

 // some more comments at the end of file
}

I noticed though that the http://lebab.io/try-it is still running an older version. @mohebifar, could we update lebab.io page?

Ah, actually this is my mistake, it's not precisely the same pattern. It appears you lebab strips comments in this variation:
function Thing() {
  this.a();
}

Thing.prototype = {
  // a
  a: function() { },
};

becomes this:
class Thing {
  constructor() {
    this.a();
  }

  a() { }
}

Even stranger! If I put a comment above the prototype like this:
function Thing() {
  this.a();
}

// wat
Thing.prototype = {
  // a
  a: function() { },
  /*
   * b
   */
  b: function() { }
};

I get this:
class Thing {
  constructor() {
    this.a();
  }

  // wat
  a() { }

  // wat
  b() { }
}

I've done a few quick fixes to remedy that and pushed out new release: 1.3.3.
I think I need to take a deeper look at this comments handling though... there are bunch of additional edge cases that still aren't covered. But this patch should remedy the most immediate pain.


Run comparer: Can't scroll down on Firefox

On Ubuntu 20.04 and Firefox 84.0.1. I experience that I cannot scroll-down in the Run-Comparer, as the following GIF shows.

The thing is, it works great on Google Chrome. I know that this Bug report should be rather directed at Firefox then, but I figured it would still be good to ask whether this has anything to do with the Wandb website or whether there are users experiencing similar behaviour (which might have solutions to it).
Thanks!

hi @zimmer-m thanks for reporting this! What a bummer, I'm sorry to hear it's not working in Firefow.

hi @zimmer-m thanks for reporting this! What a bummer, I'm sorry to hear it's not working in Firefow.

Hey @zimmer-m
Could you check with the problem? I think this might have been mitigated by now!

Hey @zimmer-m
Could you check with the problem? I think this might have been mitigated by now!

Hey @ariG23498, seems to be fixed, thanks!


pathway datanodes are not typed wp:Pathway

Addressed in https://github.com/wikipathways/GPML2RDF/commit/6e1dfaab32c3d6ddfdc4b5ff54241d14f48547da


Mask RCNN in TensorFlow

Mask R-CNN in TensorFlow.
This repo attempts to reproduce this amazing work by Kaiming He et al. :
https://arxiv.org/abs/1703.06870
https://github.com/CharlesShang/FastMaskRCNN

@mslavescu said: I'll try to integrate this in Colaboratory

Mask R-CNN based OSSDC-VisionBasedACCis Google Colaboratory demo now available here:
This is based on the mask r-cnn from here: https://github.com/matterport/Mask_RCNN
The performance of the Mask R-CNN implementation on 720p video is about 2s/frame.
The pending issue is with a mis-placed/mis-detected dog in one of the frame (see this slack discussion for details.)


Refactor

Changes in this PR:

add kube2iam, dashboard and calico to the cluster sub-module
update the documentation accordingly
output all the files in a sub-directory
new examples

@vlesierse Is there anything I can do to get this moved forward? Thanks!

Sorry, looks like this notification was lost on me. Will check it out tonight. If it's all good I merge the PR and release a new version

Thanks a lot.

@vlesierse Thank you for the input. I am not really sure I understand what you mean by "pass through the enable_dashboard, enable_calico & enable_kube2iam from the root module".

@vlesierse I think the requested changes are met and we could move forward with the merge.

If you're OK with the changes, then I think the PR can be merged. Thank you!


500 error on importing trufflehog scan result

Bug description
On importing the scan results of Trufflehog, it gives server 500 error and the findings dont get upoloaded.
Steps to reproduce
Steps to reproduce the behavior:

Go to findings tab
Click on "Import Scan Results"
Select the scan type as Trufflehog scan and upload the json file
After clicking on Import it gives 500 server error

Please follow instructions in the template and provide version, sample, logs, stacktrace, etc.


Policy definitions could not be loaded: An item with the same key has already been added

I have a problem on Windows 10 Insider Preview. Somehow system policy became duplicated.
The standard gpedit shows errors, but works:
---------------------------
Administrative Templates
---------------------------
Namespace 'Microsoft.Policies.Sensors.WindowsLocationProvider' is already defined as the target namespace for another file in the store.

File C:\WINDOWS\PolicyDefinitions\Microsoft-Windows-Geolocation-WLPAdm.admx, line 5, column 110
---------------------------
OK
---------------------------

---------------------------
Administrative Templates
---------------------------
Invalid value '$(string.UploadUserActivities _Help)' for attribute explainText.

File C:\WINDOWS\PolicyDefinitions\OSPolicy.admx, line 35, column 234
---------------------------
OK
---------------------------

Policy Plus shows error and does not load data:
---------------------------
Policy Plus
---------------------------
Policy definitions could not be loaded: An item with the same key has already been added.
---------------------------
OK
---------------------------

Sorry, I only just got around to creating a Windows Insider VM. I'm unable to reproduce this on build 17110. Could you please upload an archive of C:\Windows\PolicyDefinitions?

https://support.microsoft.com/en-us/help/3077013/microsoft-policies-sensors-windowslocationprovider-is-already-defined

This behavior is greatly improved in https://github.com/Fleex255/PolicyPlus/commit/d5bcc597135b78b97f4f655a83d34da02e706b53. Now instead of bailing on the whole folder's load, Policy Plus keeps track of the problems and displays them after the rest of the ADMX files load successfully.
The dev build has been updated; please try it and let me know if it's helpful.


How to work with checkValidity with nested shadowDoms

As a user
I want to be able to continue after invalid input
So that I can correct my fault and continue the action
Currently there is a checkValidity method on the wizard dialog that validates all the input field.
If not valid the action (primary) won't be executed. But this method only check in the shadowDom of the dialog.
If we are using custom element in there those input fields won't be found.

Fix for know it to prevent clearing the action until it's clear that the action is successful.
This way the action can do the check itself and return a empty array to do nothing.
Later maybe OpenSCD will change the way validation happens for Wizards,
checking all elements that have a checkValidity and reportValidity.


Displaying Pokemon Data from API

Rendering API Data

Use of APIs for:

Display Pokemon data
Display Pokemons' Likes

Required changes made 🛠
All linters are enable!

Fixed "use one file for the API calls and export them individually" ✅

Now the app is adding 'likes' correctly!


Switch test to work with preprod

Purpose
$subject
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #24007 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #24007   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

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 b5402d1...6f32b33. Read the comment docs.


Support for external helm repositories

I'm fairly new to dev spaces, so I may be missing something very fundamental here. I cannot seem to figure out a way to support helm dependencies (requirements.yaml) together with azds. Relative references do not seem to work nor can I determine how to add a repository that the azds version of helm can see (I am prompted to execute helm repo add despite the fact that my local helm already has the referenced repository).
What is the the preferred approach to deployments that have external dependencies that aren't in the stable helm repo? Additionally, is there a document that describes the full schema for azds.yaml?

Support for Helm charts with dependencies is on our backlog for a future release. I can't say we have thought much about external dependencies that aren't in the stable helm repo, however our general principal on these things is that however it works locally, it should work the same way with azds.
We do not currently have a document describing the full schema for azds.yaml. For now, feel free to ask if something is supported and we'll let you know if there is a way to configure azds.yaml.

Okay, understood. I'll look forward to that support.
Pardon the dumb question, but when azds is actually executing helm during a deploy, where is that actually happening? I know there's a Tiller instance inside the azds namespace which I assume it's speaking to. Is Helm actually running on the development workstation or is that living in a container or somewhere entirely different?  Just trying to sort out whether I can throw an add repo command or modify the repositories.yaml wherever that's occurring (even if it's not precisely supported).

 To achieve that, it copies (or specifically, incrementally synchronizes) your code and your Helm chart to a remote location (an Azure file share) from which the helm install command is issued.
Given this, you could mount the Azure file share somewhere and try to run commands directly on it, but it would be very hard to do this at the appropriate time (the next sync will delete anything that got added, and the helm install is run almost immediately after the sync is complete).

Got it. I had assumed some degree of smoke and mirrors was involved. Worth asking, though! I'm guessing that in order to support this use case, you'd probably need to add a repos node to the azds.yaml to drive helm repos add commands. So, it'd need to be worth doing for you. I'm not sure how many other people have this requirement, so I've no idea how likely that'd be.
I suppose this may be a sign that I should find a different way of accomplishing what I'm trying to do. On the one hand, being forced to do that by development tooling feels bad, but on the other it's maybe a sign I'm doing something the hard way. :-)
In any event, do you already have an issue tracking this backlog item I can watch for?

We maintain our backlog internally, but you can treat this issue as the external work item tracking it.

Is there a workaround  for it, i reaaaalllly need it

With dev spaces out of preview, what is the solution to this problem? What is the azds command for calling helm repo add?

@walterfranssen @chrisjohnson Because the repo information is not available to the helm client that azds uses right now, one way is to add a charts sub-directory and adding the dependencies there manually or you can do a helm repo add and helm dep update manually for the chart and once the dependencies are updated you can remove them from requirements.yaml before doing azds up. Does that work?

@mprigge @walterfranssen @chrisjohnson This is now supported!
Check out the docs at https://docs.microsoft.com/en-us/azure/dev-spaces/how-to/use-private-helm-repo to see how to use it.
Please let us know if you see any issues or have any feedback.


port tests post-processing-from bag to python

test align depth to color and test align color to depth
porting it from  legacy live test to python tests
LRS-872

After looking at it again after the refactor, the processing-block code is minimal and I have no problem with it.
I will withdraw #12440 and we can stay with the code as-is.
Good job!


Directus crashes while trying to access an avif derivative of the file just uploaded

When this extension is enabled (and the sleep time is lower than 2000 seconds, but depends on the image), just after the transformation is generated and the file is going to be saved, something (might be Directus app) tries to download a non existent image derivative from the image we just saved and it crashes.
[11:39:05] POST /files 200 67ms
[11:39:05] GET /files/78edb438-c02c-494d-932b-0addf8cd7a6f?fields[]=id&fields[]=title&fields[]=width&fields[]=height&fields[]=filesize&fields[]=type&fields[]=filename_download&fields[]=modified_on 200 9ms
[11:39:05] GET /files/78edb438-c02c-494d-932b-0addf8cd7a6f?fields[]=id&fields[]=type&fields[]=title&fields[]=title 200 19ms
node:events:496
      throw er; // Unhandled 'error' event
      ^

Error: ENOENT: no such file or directory, open '/home/myddna/projects/directus/web-backend/uploads/78edb438-c02c-494d-932b-0addf8cd7a6f__7809681e43a17c0d8ad77890c0e89a2f36978e77.avif'

I have no Idea how this could be solved right now :(

When we perform the files.uploadOne operation on a file replacement, directus deletes the old system thumbnails. This sometimes creates a race condition that crashes directus when the frontend requests the thumbnail. Why it does crash instead of generating it again I have no idea.


Update the README

https://github.com/gorhill/uBlock/commit/088e90ed42cdb09828b71a799425bb0ed0dab21c
Hi, your list has been added to uBlock Origin (I hope AdGuard will do the same soon).
It will be available to all users after ~13 days (I think).
After that, it will be available in the "Regions, languages" section for all users to enable and then there's no need to manually enable the list anymore.

The readme file has been updated.
Thank you @MasterKia and @DandelionSprout for your help. :heart:

Thanks for letting me know @MasterKia, I'll update the filters list right away.


chore(main): release php-baseimage 8.4.2

:robot: I have created a release beep boop
8.4.2 (2024-07-19)
Bug Fixes

use correct tag name when publishing php (#588) (07b482e)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

php-baseimage-8.4.2
:sunflower:


If the file to include contains curly brackets, the outputted HTML is wrong

When you include an HTML file with { or }, the outputted HTML looks is wrong.
e.g.
base.html
@@if (name === 'index') {
  @@include('index.html')
}

index.html

Output (we shouldn't have the @@if).
@@if (name === 'index') {

}

@christianv For this need to rewrite part of the parser.
Will make as soon as it posible.

@TrySound thanks!

Referenced on #63

@christianv Done!

@TrySound thanks!


new spdx_rpm script to create SPDX docs for RPMs built from src

This PR adds a new bomsh_spdx_rpm.py script, which creates SPDX SBOM documents for the binary RPM packages built from its src RPMs.
Also some miscellaneous fixes.

the bomsh_rebuild_rpm.py script has been enhanced to invoke this new bomsh_spdx_rpm.py script,
to generate the SPDX documents for the built RPM packages automatically.


ReferenceError: mouse is not defined in console

When opening page i get mentioned error in console. It's stoping all futher actions.


Adding code to run on Powersystem

What issue does this pull request resolve?
It added power architeture to the script
What changes did you make?
I have added arch - ppc64le
Is there anything that requires more attention while reviewing?
No

no longer building it on travis

Any specific reason for not supporting on Travis?

Travis builds on travis-ci.org became very slow and travis was pushing everybody to migrate to .com long before the migration deadline - it was easier to migrate to GitHub actions, and they seem to be better.
Also I am not keen to extend the build matrix, it would slow down PRs passing the tests. node.js itself should be consistent across different platforms and there is nothing platform specific in ajv.


Killed explorer.exe during install, didn't come back

Microsoft PowerToys version
0.51.0
Running as admin

[X] Yes

Area(s) with issue?
Installer
Steps to reproduce
DL 0.51.0 from Github
run installer
PowerToysReport_2021-11-30-14-49-41.zip
✔ Expected Behavior
Smooth install
❌ Actual Behavior

saw message that Windows explorer must be shut down, but will be restored. clicked OK
several screens go by, ending with 'finished' screen, click FINISH
explorer not restored
says must install .NET Core 3.2??? -- which I had installed yesterday (11/29) for another application
runs .Net installer - finishes
runs Powertoys installer, finishes, click FINISH
explorer not restored
run explorer.exe from Task Manager
Explorer restored but get error message:

explorer.exe - Fail Fast Exception
A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately.

click OK
explorer disappears
explorer appears, so does error message, loops, in sequence, three or four times.
reboot.
PT 0.51.0 seems to be properly installed.

Other Software
No response

Had a similar thing. Saw the message about Explorer (and two other processes) and continued installing. The installer also downloaded/installed Desktop Runtime x.20. Had Task Manager already open. When I saw individual powertoys in the list and Explorer didn't come back, I knew something failed.

Same here.
I started Explorer manually from the Task manager, but it would start, display the desktop then immediately crash. Then repeat...
When I did a Ctl-Alt-Del and "Sign Out" followed by a new login, all cam back properly.

You probably haven't corrupt the explorer.exe image when that happened, did you?

Everything was fine as soon as I logged on again, so I do not believe there was any corruption.

betting 0.53 will fix this since we are handling a lot of stuff differently now with the new installer.  going to mark this as 0.55 revisit.

with our new installer, this shouldn't happen now.  can you verify?

Installer seemed to hang with no movement for about a minute while 'processing' the runtime -- but otherwise, smooth as butter.


Remove category from the markdown version

The markdown version is adding the category which is not necessary.

Where is it? I don't got it

Look at the screenshot @JulioGold

Actually, it is not necessary just in the markdown version, it should be removed from all views (HTML, Markdown and Outline)

I think it's done #35


need removeVolume option for models

Thanks Carson, we'll look into adding an ospRemoveVolume() API call similar to the existing ospRemoveGeometry().


Updates to the Czech translation.

added translated strings about BOLT12 offers
corrected automatic translations
typo correction

It look OK so let's keep it as-is.


add build features

build features would be useful to disable features in release builds
these include:

logger
uihelper
debug gizmos (not yet implemented)

while interesting, the project is too early for this to be implemented. the syntax and testing overhead ist just too much.

https://github.com/Rismosch/ris_engine/tree/testing-features


[Event Request] Table 38 "Purchase Header" - New Event “OnBeforeLookupAppliesToDocNo”

Could we please have a new publisher “OnBeforeLookupAppliesToDocNo” with Handled-Pattern in the OnLookup Trigger of Field 53 “Applies-to Doc. No.” for Table 38 “Purchase Header”, exactly as it already exists in Table 36 “Sales Header”?
trigger OnLookup()
var
GenJnlLine: Record "Gen. Journal Line";
GenJnlApply: Codeunit "Gen. Jnl.-Apply";
ApplyCustEntries: Page "Apply Customer Entries";
IsHandled: Boolean;
Begin
// >>>>>>>>
IsHandled := false;
OnBeforeLookupAppliesToDocNo(Rec, VendLedgEntry, IsHandled);
if IsHandled then
exit;
// <<<<<<<<
TestField("Bal. Account No.", '');
…
// >>>>>>>>
[IntegrationEvent(false, false)]
local procedure OnBeforeLookupAppliesToDocNo(var PurchaseHeader: Record "Purchase Header"; VendorLedgEntry: Record "Vendor Ledger Entry"; var IsHandled: Boolean)
begin
end;
// <<<<<<<<

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


resolves #113

This may address the issue by only splitting on the first space in a URL.
This would require the user to specifically state the HTTP Verb if there are spaces in the URL, but will probably work otherwise.
Not sure if there is a better method to address that fits your overall requirements - this was just a simple idea I had for the issue I ran into.

Test worked for this use case.  Variable in URL still working.

close #113


Update request: nvidia-container-toolkit 1.9.0 → 1.14.3

Package name: nvidia-container-toolkit
Latest released version: 1.14.3

Current version on the unstable channel: 1.9.0
Current version on the stable/release channel: 1.9.0

[x] Checked the nixpkgs pull requests

Notify maintainers

@GTrunSec
@aaronjheng
@cpcloud
Latest nvidia driver introduces libnvidia-gpucomp.so library, which libGLX_nvidia.so is linked against. nvidia-container-toolkit of version 1.14.0 is required for inclusion of libnvidia-gpucomp.so into a container. Without it, OpenGL inside container is broken.

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

As a workaround, I mount /run/opengl-driver/lib/libnvidia-gpucomp.so into the container explicitly.


[microNPU] Fix offloading incompatible average pool

Fixes offloading a few corner cases of average pooling. Specifically not offloading nn.avg_pool2d when:

The attribute count_include_pad=True
Padding exceeds the dimensions [3, 3, 4, 4]
The pool size is greater than [8, 8] when the pool uses padding

cc @Mousius @NicolaLancellotti @ekalda @manupa-arm

@tvm-bot rerun

@tvm-bot rerun

@tvm-bot rerun

This is finally green :)

Might be better to add a test for to cover this case.
(Happy to take a follow-up)

Sure! Might be best to do in a follow up (CI seems quite flaky atm)

Thanks @ekalda @lhutton1 !


Group resource: "append true" doesn't work right for adding users to multiple groups on Solaris.

Description
When using :modify on a group in solaris2 (5.11) environments, append true doesn't work correctly when adding a user to additional groups. See -G flag comments on https://docs.oracle.com/cd/E26502_01/html/E29031/usermod-1m.html , note that the code for the usermod resource doesn't put + or - before the group name.
We're working on a fix for this.
Chef Version
Chef 14.7.17, though the bug exists through many versions.
Platform Version
Solaris 5.11.
Replication Case
group1_name = 'tstgrp1'
group1_id = 6789
group2_name = 'tstgrp2'
group2_id = 9876
group group1_name do
  action :create
  gid group1_id
end
group group2_name do
  action :create
  gid group2_id
end

group 'primary' do
  action :create
end

firstbatch = %w(user1 user2)
secondbatch = %w(user3 user4)
%w(user1 user2 user3 user4).each do |username|
  user username do
    group 'primary'
    manage_home true
  end
end

group 'add firstbatch to group1' do
  group_name group1_name
  action :modify
  members firstbatch
  append true
end

group 'add secondbatch to group2' do
  group_name group2_name
  action :modify
  members secondbatch
  append true
end

# Now, add them to the other group. The end result SHOULD be that all 4 users are in both groups.
group 'add firstbatch to group2' do
  group_name group2_name
  action :modify
  members firstbatch
  append true
end

group 'add secondbatch to group1' do
  group_name group1_name
  action :modify
  members secondbatch
  append true
end

Client Output
Appears normal, until you actually look at the groups.
EXPECTED: All 4 users are in both groups.
ACTUAL:
# getent group tstgrp1
tstgrp1::6789:user3,user4
# getent group tstgrp2
tstgrp2::9876:user1,user2

Make sure that you think of it as "the user should be in X groups", not "the group should have X users" - if you only have one group and attempt to add users in successive :modify actions, that won't cause the problem. The problem here is not that "add secondbatch to group1" wiped out the firstbatch users from group 1 - it's that "add secondbatch to group1" took them out of group 2.
Stacktrace
N/A

Fix merged to master and will be backported for the next Chef 14 release. Thanks @jjustice6


Using next() in regex based GET handler calls POST handler with same endpoint

Example:
Middleware for some get requests
app.get('/init/*', function (req, res, next) {
 // do something
 console.log('GET middleware called');
 next();
})

which is followed by:
app.post('/init/*', function (req, res, next) {
 // do something else
 console.log('POST middleware called');
 next();
})

and
app.get('/init/', function (req, res) {
 console.log('GET handler called');
 return res.json({'status':'success'})
})

When the user hits the server using GET  at / , both the middlewares get called.
Ideally calling next() from GET handlers should only call other GET handler in the chain, rather than any other handler with the same mounting point.

Hi! Given the information provided, I cannot reproduce your issue. When the user hits the server using GET / as you described, using the code you described, no middlewares at all are called. Here is my debugging session:
$ npm i express
<EMAIL_ADDRESS>node_modules\express
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
$ cat app.js
var express = require('express');
var app = express();

app.get('/init/*', function (req, res, next) {
 // do something
 console.log('GET middleware called');
 next();
});

app.post('/init/*', function (req, res, next) {
 // do something else
 console.log('POST middleware called');
 next();
});

app.get('/init/', function (req, res) {
 console.log('GET handler called');
 return res.json({'status':'success'})
});

app.listen(3000);

$ node app.js &
[1] 9960

$ curl http://<IP_ADDRESS>:3000/
Cannot GET /

Can you please provide all the following so we can take a look into the issue?

The version of Node.js you are using.
The version of this module you are using.
A mini Express app that has all the code needed to reproduce the error (just like I did above). This will help make sure that we are using exactly the same code to remove as much variables as possible between our tests.
The exact call we need to make the Express app.
A description of what we should see if it is not working as expected vs working as expected.

Once we get all this information, we can take another look. Thank you!

Edit: My bad, the correct functions are as follows
app.get('/v1/*', function (req, res, next) {
 // do something
 console.log('GET middleware called');
 next();
})

which is followed by:
app.post('/v1/*', function (req, res, next) {
 // do something else
 console.log('POST middleware called');
 next();
})

and
app.get('/v1/init/', function (req, res) {
 console.log('GET handler called');
 return res.json({'status':'success'})
})

and hit should be at /v1/init
It's working as expected

Hi @psych0der, thanks for the update! You are missing many of the pieces of the information I asked for, and with the updated routes, I still cannot reproduce the issue. I'm going to close this issue for now as not reproducible. If you can provide all the following information I can re-open, though!

The version of Node.js you are using.
The version of this module you are using.
A mini Express app that has all the code needed to reproduce the error (just like I did above). This will help make sure that we are using exactly the same code to remove as much variables as possible between our tests.
The exact call we need to make the Express app.
A description of what we should see if it is not working as expected vs working as expected.

Here is my debugging session with the updated routes and new call:
$ npm i express
<EMAIL_ADDRESS>node_modules\express
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
$ cat app.js
var express = require('express');
var app = express();

app.get('/v1/*', function (req, res, next) {
 // do something
 console.log('GET middleware called');
 next();
});

app.post('/v1/*', function (req, res, next) {
 // do something else
 console.log('POST middleware called');
 next();
});

app.get('/v1/init/', function (req, res) {
 console.log('GET handler called');
 return res.json({'status':'success'})
});

app.listen(3000);

$ node app.js &
[1] 4352

$ curl http://<IP_ADDRESS>:3000/v1/init
GET middleware called
GET handler called
{"status":"success"}

As you can see, the POST middleware is not being called, as I would expect and as you are expecting as well.

Also, if you are continuing to have problems and just need help or someone to work through the issue with you, please stop by our support channel https://gitter.im/expressjs and if someone is around, they'll be happy to help.

Thanks a lot, @dougwilson


Swift how-to-use

Hi,
What are the steps to use the library on Swift?
I installed using CocoaPods, Podfile:
pod 'MaterialControls', '~> 1.0.2'
I've added, on my "Bridging-Header":
#import "MaterialControls/MDTableViewCell.h"
and then Im trying to use on my swift class:
class BlogTableViewCell: MDTableViewCell {``
and I got an error saying that cant find the class:

Is that right? What am I missing?
Thanks,

I have just  included this line
import MaterialControls
and build the project CMD + B. It then updated all the references.

@zishanj thanks, but did you included something in the Objective-C bridging header?
Are you using the cocoapods to install?

Yes, I am using cocoapods. Here is what my pod file looks like:
use_frameworks!
pod 'MaterialControls', :git => 'https://github.com/fpt-software/Material-Controls-For-iOS.git'

Here, instead of using any version, I am directly using the Master repository to keep upto date. Then I just used import MaterialControls in my swift file and Build the project to update all references.

@zishanj it works! thank you very much.
No need imports on Objective-C bridging header.
I think this should be added to the README :D


Show message when admin filter returns no results

Description
When filtering on an access code returns no results, we'd like to let the user know what's going on.
Setup
In the Admin interface, on the Access codes page, adding a filter for a (six-digit) code with no matches should replace the pagination footer with the following text: "There are no results for this access code. Please check your entry to make sure you entered the correct letter combination."
Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

@rswerve had trouble getting this to work locally - you might need to merge master in to get the fixes from #2887

@rswerve had trouble getting this to work locally - you might need to merge master in to get the fixes from #2887

Doh, thought I'd done that.  Fixed.


#185218915 Users should be able to Login via Google.

What does this PR do?
This PR allows Users sign into a Google account, which helps you to quickly and easily manage user authentication on your website.
Description of Task to be completed?

Provide their consent, and securely share their profile information with your platform.
Customizable buttons and multiple flows are supported for user sign-up and sign-in.
Adding Pull Request template adhering to ATLP's Engineering Playbook

How should this be manually tested?

Clone the repository using git clone https://github.com/atlp-rwanda/e-comm-team-techsmith-fn.git

Checkout to the branch using git checkout ft-users-should-be-able-to-login-via-google-185218915

Install node packages that the application depends on: npm i

Create a .env file in the root directory and add all environment variables required to run the application. The required variables are listed in the .env.example file available in root directory of the application.

Start the application development server: npm start

What are the relevant pivotal tracker/Trello stories?
+185218915
Screenshots (if appropriate)

Please rebase carefully, I can still see folders and files that are nolonger being used.


GraphOptimizationApplication, single repsonsibility principle

What is the expected enhancement?
the static method random_graph in the GraphOptimizationApplication
violates the single responsibility principle. Please create some helper and move it there.

BTW, it might be ok to have some "reasonable" (not a single line application of some library) generators of random problems. For graphs I can imagine planted problems, d-regular graphs of high grith etc. I dont know if they are in some other libraries like NetworkX.

GraphOptimizationApplication can take networkx graph as an input. So, we don't need to generate a random graph by GraphOptimizationApplication. We need to use just networkx's random graph features. Alternative is retworkx's random graphs.

Fine with me. I don't feel it should be in GraphOptimizationApplication. And I wanted to point out that there might be some cases that are interesting, which are not in the networkx, retworkx, and so. as I mentioned above.

What kind of helper file do you want?


Revert PR #947

This reverts PRs #1559, #1522 and #947
PR #947  made the HTTP state machine unstable and lead to crashes in production like #1930 #1559 #1522 #1531 #1629

@zwoop This is a candidate for v7.1.0.

@jacksontj Could you please create a new issue to describe the story / bug in PR #947 ?
So we can rewrite the patch for it.

Testing this on docs right now as well.

[approve ci docs]

[approve ci docs]

[approve ci docs]

Maybe we can track this on the existing Issue that we have for this? #1930


Make flow available as metadata to contentview

I am working to analyze the ssl traffic on APIs for a specific domain. The content is encoded differently (via some serialization) according to which API the caller is invoking. In this scenario, it is hard for a custom contentview script to distinguish the underlying API solely from the content and headers.
Can we add more info to the contentview metadata? Say metadata['url'] and metadata['method'] will absolutely be helpful.

That sounds like a reasonable request - I'd be happy to accept a PR that adds this. The relevant bits in the code are here! 😃

I just checked the source code. It seems that message will be an instance of either http.Response or http.Request in most case. If it is http.Response, there seems no way to extract the information from its correspondent request where host/port/path lies. I wonder what other code I can touch and whether it is acceptable to alter certain internal function prototype.

Oh, I see. That's relatively tricky, we currently assume that a view does not need any metadata except for the message itself. If you want a short-term hack, you can assign flow.response.request = flow.request in a custom script, properly propagating the flow down to the contentview isn't entirely straightforward I believe.

This API needs to be revamped.

The content view mechanism should be an addon.
The addon should expose commands that take a flow, a view specification, and a part selector (request/response/etc.).
The content view commands should return a content view iterator, that yields items conforming to our content view specification. This type should be added to the command type system.

This design would cope with the use case described in this ticket (you would have the full flow), and also allow us to do other idiomatic, flexible things with the content views.


updated yarn command

Why:
request was made to update the yarn run command.
Closes:  #24811

What's being changed (if available, include any code snippets, screenshots, or gifs):
line 179 was modified; it now indicates - run: yarn npm publish // for Yarn version 1, use yarn publish instead instead of - run: yarn publish

Check off the following:

[X] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[X] For content changes, I have completed the self-review checklist.

@PaoloJr90 Thanks for submitting this PR! I've edited your post slightly to link it to the help wanted issue.
I'll get this triaged for review! :zap:

Thanks for your interest and help in improving our docs, @PaoloJr90!


Limit to 1 instance of reconciler

Fixes warning about multiple reconcilers

📦 Published PR as canary version: 1.0.4--canary.2.47.0

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

Codecov Report

Merging #2 (5f9161e) into main (cff3bf8) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage   69.07%   69.07%
=======================================
  Files           4        4
  Lines         152      152
  Branches       20       20
=======================================
  Hits          105      105
  Misses         35       35
  Partials       12       12

Impacted Files
Coverage Δ

src/render.ts
100.00% <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 415db47...5f9161e. Read the comment docs.


refactor and increment minor version

I think this should probably be published on crates.io.

Thank you. Will publish soon.


[BUG] JSON Text Components

Describe the bug
JSON Text Components in powers like origins:tooltip are being errored, as it requires an object
To Reproduce
Steps to reproduce the behavior:

Make a tooltip power
Use JSON Text Components
Text Components are errored, saying it needs to be a string

Expected behavior
As the wiki says, JSON Text Components should not be errored, as they work in-game.
Screenshots

If you find any more places where this issue comes up, comment them here. I've fixed the one you've mentioned.


Bug with execute in for and for each commands

Anytime, I use an execute command in a for loop, I'm getting an error for the command that's trying to execute something when compiling...
For Example:

function testing {
for (var $y = 0; $y < 257; $y = $y + 1){
execute @e[score_test_min=0] ~ ~ ~ /say $y;
}
}
gives me an error saying:

Error:Unexpected token: {"type":"reg","value":"ay"}

if I don't include the slash in 'say', I get this error:

Error:Unexpected token: {"type":"reg","value":"say"}
I get similiar errors with other commands like /scoreboard as well

Oh, the problem is, currently the execute block system is overriding the normal execute command.
Until I fix this (which should be soon), you will have to do it like this:
execute @e[score_text_min=0] ~ ~ ~ {
    say $y;
};


Time series window size for scrolling

How to increase the x-axis window size in a time series plot such that the entire plot is displayed every time instead of a zoomed in version. I don't want to scroll but see the entire plot.

Hi @nikhilajoshy, can you ask your question in the community Slack? That channel is better prepared to answer support questions.


[Suggestion] Add a new index type IVF_SQ8H

Is there anything that's missing or inappropriate in the docs? Please describe.
IVF_SQ8H is supported in v0.5.0, yet there's no corresponding doc.
Describe your suggestion
Add description about this new indexing method.

#87 Already added the indexing method in v0.5.0.


Loading map history doesn't update last position

Just did a field test outside. When I got back to my desk I loaded the history for the last hour without refreshing the page. The history trail was loaded, but the hexagon with the last position was still from before the locations from the more recent field test.

This is fixed with a recent change.


Partial call allowed without a ?

The following code:
trait T
  fun f1() ? => error
  fun f2() ? => f1()

actor Main is T
  new create(env: Env) =>
    None

Results in the following errors in 0.19.2 (see playground: http://playground.ponylang.org/?gist=19514f10bd5c0e1146a610bdb896f174):
0.19.2 [release]
compiled with: llvm 3.9.1 -- cc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Error:
main.pony:3:20: call is not partial but the method is - a question mark is required after this call
  fun f2() ? => f1()
                   ^
    Info:
    main.pony:2:12: method is here
      fun f1() ? => error
               ^
Error:
main.pony:3:20: call is not partial but the method is - a question mark is required after this call
  fun f2() ? => f1()
                   ^
    Info:
    main.pony:2:12: method is here
      fun f1() ? => error
               ^

However, the same code compiles without error on current master.

This may have been an unintended consequence of #2261.


Railway relations of type multilinestring are not showing in the tiles

I noticed that the vector tiles show only the railways that are of type “way” in the transport_lines layer, but not the railways that are relations - type=multilinestring e.g.,
https://www.openhistoricalmap.org/relation/2835640#map=12/50.4356/3.8433&layers=RD&date=1966-10-31&daterange=1824-01-01,2024-12-31
It seems these were not included since the beginning of the tiler deployment because I could not find any configuration for that.
Ref: https://wiki.openstreetmap.org/wiki/Key:railway?uselang=en

FYI it’s much more common to represent a railway as a type=route route=railway relation, though there has been some discussion about using multilinestrings for this purpose (#439 and on the forum).


#23987: LARSOptimizer initializes _learning_rate_tensor

LARSOptimizer initializes _learning_rate_tensor and _momentum_tensor in _prepare method

I signed it!

I signed it!

I signed it!


Add dropdown test

@mazmassa thnks for the review, I cut the pr down by half, should be much more efficient and clearer


Ensure to attack with cli options

Codecov Report

Merging #22 into master will decrease coverage by 1.84%.
The diff coverage is 94.00%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
- Coverage   79.42%   77.59%   -1.83%
==========================================
  Files           7        7
  Lines         374      281      -93
==========================================
- Hits          297      218      -79
+ Misses         54       45       -9
+ Partials       23       18       -5

Impacted Files
Coverage Δ

gui/keybinds.go
38.89% <0.00%> (-40.12%)
:arrow_down:

gui/gui.go
74.00% <92.86%> (-4.68%)
:arrow_down:

attacker/attacker.go
73.53% <100.00%> (+0.81%)
:arrow_up:

gui/drawer.go
92.69% <100.00%> (-0.25%)
:arrow_down:

gui/widgets.go
61.30% <100.00%> (+1.80%)
:arrow_up:

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 f5474e7...2412484. Read the comment docs.


StateDB: Write operations should always fail hard

If any of them fails while adding a new block to the Ledger,
we should be aware and rollback.

This may not be an exhaustive list, I only followed the code in begin/rollback scope in Ledger.addValidatedBlock


Python3.x Support

Wont install right now as it depends on ProxyTypes, which has a python2 style print statement in the setup.py script.

Latest proxytypes package release: 2006-07-20 (https://pypi.python.org/pypi/ProxyTypes)
I think it's worth considering forking or vendorizing it.

Yeah, I have done, just haven't merged it yet.
https://github.com/mixcloud/django-speedbar/pull/27/files
Mat


Determine solution for map loading failure

We need to choose a solution for the issue described in #69. Our options are to either rewrite the code base to use the Google drive API (which may have its own bandwidth/pricing limitations), or we can conduct a test to see if adding sleep calls to our code will get around the rate limiting issue.

bro why'd you make an issue that's just saying to solve another issue

After testing the sleep solution with @DannyOppenheimer, it appears as though the sleep is still just as inconsistent as without. Moving forward, I think we'll try the Google drive API, but we could also consider better ways to store the data that don't involve Google.


Enable "Discussions" GitHub feature

It might be beneficial to enable the "Discussions" feature to separate the project development issues from "how do I do X" types of issues, and build a community.
See ImageMagick's discussions for example.
My motivation for proposing this is that I've started using the Windows Terminal few days ago and I've probably spent several hours searching for ways to configure settings to my liking, and there are a few I still haven't figured out but I feel like I'd be spamming the "Issues" by asking there.

Enabling the GitHub "discussions" feature was suggested before in issue #7428. The argument against it was that it has a tendency to turn into a second bug tracker (here's one example: https://github.com/microsoft/terminal/issues/7428#issuecomment-725660615).

/dup #7428 since they sorta share a common thread

@DHowett I don't think this is a duplicate. The conversation became off-topic discussing about Discussions (pun intended) but the original ask is different

@DHowett I don't think this is a duplicate. The conversation became off-topic discussing about Discussions (pun intended) but the original ask is different


Audit and update docs to only contain functionality that actually works for 0.4 release

Expected Behavior
When people look at the docs in the repo and read about what they can do, and how to use Pipelines, they should only see functionality that has been implemented.
(Especially once we start having official releases!!)
Actual Behavior
The docs are a bit aspirational and contain descriptions for some functionality we haven't actually implemented, for example:

The providedBy clause (fyi about to be renamed to from in #320) is described in our docs as being used to determine ordering, but it doesn't yet effect ordering at all
Related to providedBy, the docs do not explain that the Tasks in a Pipeline execute sequentially (unless we get to #168 before 0.4)
The image resource docs talk about accessing the image's digest, but at the moment nothing populates this digest (will be implemented in #216)
We have a results config which claims to be about where logs are uploaded to but currently does nothing (until at least #107)

There may be more, so part of this issue is to read carefully through all of our docs.
Additional Info
We do this at the very end of the milestone, when we've got a solid idea about what functionality will make it into the 0.4 release and what won't.

[x] providedBy, now called from docs don't talk about ordering (https://github.com/knative/build-pipeline/blob/master/docs/pipelines.md#from) - they did say "from can support fan in and fan out" which I'll remove for now since it's kind of true but confusing
[x] "* the docs do not explain that the Tasks in a Pipeline execute sequentially (unless we get to #168 before 0.4)" <-- the docs now explicitly say "a sequence of tasks"
[x] "* The image resource docs talk about accessing the image's digest," - Updating these docs to make this clear this doesn't work yet
[x] "* We have a results config which claims to be about where logs are uploaded to but currently does nothing"  - Removing this from the tutorial and examples at least


funcargs on describe functions

Hey there! First of all, thanks for sharing this plugin. I've been using it in some projects and I really like it. However, there's a feature I'm missing: be able to add funcargs to describe functions;
Consider the following scenario:
def describe_calculate_something_hard(calculator):
    def when_input_is_x(x, expected_result):
        assert calculator.calculate(x) == expected_result

If I do this, the calculator argument is not handled by the pytest. Maybe I'm just using it wrong.
But if this is a missing feature, I would like to have it. I could even implement it by myself, but some directions would be much appreciated.
Best regards,
casimiro.

This has been asked before #9
The "describe" functions are evaluated in the test collection phase, hence its not possible to access fixtures before the tests start running. It may or may not be possible to implement this with some "magic" where the scope of the outer function is altered before the inner function is called, but I'm not sure.

I tried messing around a little bit with the code. I'm pretty sure that it's impossible to "magically" change the local variables of the outer function before running each of the inner functions (see link below for some related discussion).
http://stackoverflow.com/questions/23499042/why-does-modifying-parent-frame-in-python-work-only-for-module-frames
I guess it would be possible to call the describe function one additional time for each test function inside, so that we in practice create a new test function, bound to the funcarg value, just before we invoke it. But that would be too messy, I think. Any code inside the "describe" block would be executed once in the test collection phase, and then once more for each test inside. With nested describe block, it would be a complete chaos.


Stacks are not region agnostic

Expected Behavior
I'm able to deploy from the AWS credentials set region, mine is us-east-1
Actual Behavior
Some resources are hardcoded to be from eu-west-1
Steps to Reproduce the Problem

Try creating the resources in another region than eu-west-1
See error

Here specifically for .NET, also in the README.md
https://github.com/DataDog/serverless-sample-app/blob/efa33b46de87012345a62da8e91970fe0b654b92/src/dotnet/cdk/Constructs/InstrumentedFunction.cs#L63-L64


Fixed regex literals and tags, Added concrete syntax highlighting

You can see the effects of concrete syntax highlighting here:
Concrete syntax highlighting

Looks very good. I tried varies snippets and works well, thanks.
Below is an example that surprises me: (string literals like "template_open" are not highlighted in red, while they are in other contexts). Any clue?
private MuExp translateStringLiteral(s: (StringLiteral) `<PreStringChars pre> <Expression expression> <StringTail tail>`) {
    preIndent = computeIndent(pre);
    return muBlock( [ muCallPrim3("template_open", translatePreChars(pre), pre@\loc),
    				  *translateExpInStringLiteral(preIndent, expression),
    				  *translateTail(preIndent, tail),
    				  muCallPrim3("template_close", [], tail@\loc)
					]   );
}

@PaulKlint Thanks. Hmm, I might have been to general in scope for the lexical [] so it also apparently included list literals. I will try and see how to fix this.

Here is another one: int n versus list[int] n. In the former int is green in the latter it is not. Is there a reason for this?

Yeah, so the major issue is that [] seems to have a different meaning when it's inside lexical or syntax than when it's outside. I have to figure out a nice way to capture this property.
This is because e.g. [/bla/] is a list containing a regex in a normal context, whereas it is something which expects any of the characters / b l or a in a lexical context).
The current way is that it treats all [] uniformly as lexical contexts (if it doesn't it will ruin the highlighting elsewhere in the grammar files.
I have to figure out how to make this work in a nice way, so it only applies to things in lexical and syntax.

It's my first time writing a TextMate grammar, so it's taking me some time to figure out how to do these things correctly.

This has been on our list for a long time since we are no experts on this either. I can imagine that some more regexp fiddling is needed here and that it is not so simple to figure out what these cooperation regents do precisely.
Since I find your highlighter so good (on par or even better than our Eclipse one a I would say) I am doing more experiments and will report surprises here (take this as a compliment, its intended to make this really good!).
Here is another one where a comment is missed:
// comment 1

n = 1;  // comment 3
l = [1, // comment 3: non highlighted
     2,
     3];

Great, thank you for the examples and the comments!
I will take a look at fixing this tomorrow, I think I have an idea how to proceed.


[T6A1][T09-C1]

Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail


Use NoFinalizer Zstd IO streams for topic encoder

Codecov Report
Attention: Patch coverage is 0% with 22 lines in your changes missing coverage. Please review.

Project coverage is 47.33%. Comparing base (5e1392d) to head (84e9845).

Files with missing lines
Patch %
Lines

...ic/src/main/java/tech/ydb/topic/utils/Encoder.java
0.00%
18 Missing :warning:

...ain/java/tech/ydb/topic/write/impl/WriterImpl.java
0.00%
4 Missing :warning:

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #334   +/-   ##
=========================================
  Coverage     47.32%   47.33%
  Complexity     1750     1750
=========================================
  Files           309      309
  Lines         12468    12463    -5
  Branches       1234     1232    -2
=========================================
- Hits           5901     5899    -2
+ Misses         6107     6104    -3
  Partials        460      460

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Feature]: Curp log compaction

Description about the feature
Currently, all log entries will stay in memory and disk forever. We need to recycle memory and disk space by compacting these log entires. Ideally, all log entries that have been applied to the state machine are longer needed and therefore can be compacted. However, in case of laggy network, we should reserve some number of entries on each node. In addition, the compaction cost for memory is different from disk. Therefore, there should be two independent compaction strategies, one for memory, one for disk.
For memory`
Compaction for log entries in memory is easy. We can replace the entries: Vec<LogEntry<C>> in log.rs with a VecDeque of fixed size(say, 5000). Old entries will be popped out when new entires are added.
For disk
Since I/O operations are expensive and disk space is less likely to be used up as fast as memory, we should not frequently trigger compaction for log entries on disk. We can set a timer to periodically check the number of log entries on disk. If the number exceeds, say 10k, we can use delete_range to remove old ones. And the operation is purely async and will not block our curp server.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

For memory and disk, we should check the entries' states before dropping them. And would you please add the recovery related change after applying log compaction?

For memory and disk, we should check the entries' states before dropping them. And would you please add the recovery related change after applying log compaction?

For memory, we need to check if indexes of entries to be moved are smaller than last_applied. For disk, there is no need for checking I believe.
And log entry compaction will have nothing to do with recovery, I guess?

After using log compaction, followers may try to get the log entries that have been compacted, then the snapshot is sent instead. Is the scenario above the side effect we should care? I guess there are other small side effects.

Another possible side effect might be that on restarting a node, we will retain only a fixed number of entries in memory, not all.


Accept files from stdin

Git filters need to filter through stdin and stdout, not with filenames.

Completed by #8


chore: fix lint error

@pi0 please wait for the tests to pass ;)

Sorry, @galvez taught it is a Travis failing one. Was going to fix it 💃


The table query mode is closed after importing an entity

Storage Explorer Version: 1.22.0-dev
Build Number: 20211125.2
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 18.04/MacOS Big Sur 11.6
Architecture: ia32/x64
How Found: Exploratory testing
Regression From: Previous release (1.21.3)
Steps to Reproduce

Expand one storage account -> Tables.
Open one table -> Click 'Query'.
Click 'Import' -> Select one .csv file-> Click 'Open -> Insert'.
Check whether the query mode is closed.

Expected Experience
The  query mode is not closed.
Actual Experience
The query mode is closed.
Here is the record:

Verified this issue on the build main/20211130.2. Fixed.


Iframe repositioning on phpBB viewtopic

Hi all, sorry for but i've search around to fix this issue and starting to do some strange js things to fix it but without success until now, so i will follow with some CSS "experiment" to check another way. I know it's complex to understand how all the joke here work, but i hope somebody could help.
The scenario is a phpBB forum iframed into a WordPress page.
The issue, that i can't well explain with my bad Eng, is better explained with the direct link to an example:
https://www.axew3.com/w3/forum/
you can see that phpBB body iframe is well vertical centered in this case with correct gap between the forum wrapper and the wordpress div element that contain it:

while if the passed real phpBB link contain the anchor that scroll the phpBB viewtopic.php positioning it to view the last inserted post on topic,
https://www.axew3.com/w3/forum/?forum_id=2&topic_id=857&post_id=3183#p3183
the result is this

the iframe is forced to top and the iframe isn't correctly vertically centered.
I know it's maybe also off topic here a question like this? Do not know, i try also this. Thank anybody can take a fast look giving a possible solution, i will follow also with any update (if this will be not removed!) cheers!

it seem resolved via CSS by adding this code into the body selector of the file common.css (phpBB CSS subsilver in this case):
position: fixed;
  top: 0%;
  left: 0%;
  width:100%;

can't believe that this solution have come out finally

p.s the above fix the thing while on iframe, while it present a problem while phpBB surfed by direct link (not iframed) ... so it may be necessary a little effort more, executing/adding this css properties only when phpBB is surfed via iframe. If any hint by someone that can find out a better way, would be nice

for instance, i've add the follow into my overall_footer.html to resolve definitively and seem that now all work fine:
if (window.frameElement) {
//fix scrollig gap to top if on iframe (on viewtopic.php where # anchor)
var elt = document.getElementById("phpbb");
elt.setAttribute("style", "position:fixed;top:0%;left:0%;width:100%;");
}

the complete correct code is this:
// fix vertical align on viewtopic.php or preview, where # anchor etc
$(window).load(function() {
var bd = document.getElementsByTagName("body");
for (var i = 0; i < bd.length; i++) {
    var bdID = bd[i].getAttribute("id");
}
var elt = document.getElementById(bdID);
elt.setAttribute("style", "position:fixed;top:0%;left:0%;width:100%;");
});

It's valid for any phpBB theme. If no any hint on how to resolve this issue via resizer js code, this question can be considered as resolved in this way? Regards


[ECS] ArrayListItemNewlineFixer: Keep inline comments

Hi!
Not sure what's up with the test failure. Pipline setup issue?
All unit tests passed when run from repository root.

@Reinis Hi, the feature looks good to me :+1:
The CI got stuck for because of invalid nesting in composer.json. Fixed in https://github.com/symplify/symplify/commit/ea09b9845ed15c91839a6fbb2883d7fd3ad4e5e1

Thank you :+1:


Installing SAP HANA, express edition with Docker

Tutorials: https://developers.sap.com/tutorials/hxe-ua-install-using-docker.html
Write here how you think we can improve the tutorial ...
'groupadd haeadm -g 79'
'useradd hxeadm -u 12000 -g 79'
learners have to add user and group manually first before run hana express in container, otherwise they would be we stuck on below issue
hxecont  | ERROR: Insufficient permissions on /hana/mounts. Required permissions: rwx

John, can you please respond to this user's suggestion?

Thanks for the feedback - the section "Create a Directory to Persist SAP HANA, express edition Data Outside of the Container" was removed from the tutorial so readers should no longer hit this issue.


cluster.Run should take care of nil clst the first time it runs.

Also, the default region for Azure should be using their backend formatted region name.

Merged


Polish the translation

Fixed some spacing and cut-off issues.

@chenlee13 thanks for contributing! Would you mind pulling down the latest from the dev branch and making these changes again to avoid the conflicts? The conflict resolution on this pull request looks to be quite difficult to manage. Thanks! Also, the title says Polish which is a bit confusing.

@lukestokes Hi Luke, do you know what might have caused the conflicts? I clicked on the "Resolve conflicts" button but it doesn't say much.

@lukestokes Thanks man.

@chenlee13 I went ahead and made the changes here: https://github.com/eosdac/eosdactoolkit/commit/e3efe599a97503758a6443915df41cfa9c9c6d67


upload_to_testflight ignores build_number and uses the latest Mac build instead of the latest iOS

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

I am running the upload_to_testflight command with an application that has iOS and macOS products. The latest iOS build number is 252, the latest macOS build number is 246. Running this command always results in Waiting for processing on... app_id: xxxxxxx, app_version: 1.0, build_version: 246, even when I specify the platform and build number.
Command executed

fastlane run testflight groups:"Group Name" distribute_only:true app_platform:"ios" build_number:"252"
note: tried build_number with and without quotes, no change to the output.
fastlane run testflight groups:"Group Name" distribute_only:true app_platform:"ios"
note: output is the same for this one too, except the line Using build_number: 252 doesn't appear (which does make sense).
Complete output when running fastlane, including the stack trace and command used

% bundle exec fastlane run testflight groups:"Group Name" distribute_only:true app_platform:"ios" build_number:252 --verbose
[✔] 🚀
DEBUG [2022-07-18 17:39:08.25]: Checking if there are any plugins that should be loaded...
DEBUG [2022-07-18 17:39:08.25]: Loading 'fastlane-plugin-bugsnag' plugin
INFO [2022-07-18 17:39:08.25]: gem 'fastlane-plugin-bugsnag' is already installed
DEBUG [2022-07-18 17:39:08.26]: Loading 'fastlane-plugin-xcconfig' plugin
INFO [2022-07-18 17:39:08.26]: gem 'fastlane-plugin-xcconfig' is already installed
DEBUG [2022-07-18 17:39:08.26]: Loading 'fastlane-plugin-bugsee' plugin
INFO [2022-07-18 17:39:08.26]: gem 'fastlane-plugin-bugsee' is already installed
+--------------------------+---------+---------------------------------------------------------------+
|                                            Used plugins                                            |
+--------------------------+---------+---------------------------------------------------------------+
| Plugin                   | Version | Action                                                        |
+--------------------------+---------+---------------------------------------------------------------+
| fastlane-plugin-bugsnag  | 2.2.1   | upload_symbols_to_bugsnag, send_build_to_bugsnag              |
| fastlane-plugin-xcconfig | 2.0.0   | update_xcconfig_value, set_xcconfig_value, get_xcconfig_value |
| fastlane-plugin-bugsee   | 1.0.2   | upload_symbols_to_bugsee                                      |
+--------------------------+---------+---------------------------------------------------------------+
Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

DEBUG [2022-07-18 17:39:08.58]: Using groups: Group Name
DEBUG [2022-07-18 17:39:08.59]: Using distribute_only: true
DEBUG [2022-07-18 17:39:08.59]: Using app_platform: ios
DEBUG [2022-07-18 17:39:08.59]: Using build_number: 252
Successfully loaded Appfile at path '~/repos/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

Successfully loaded Appfile at path '~/repo/fastlane/Appfile'

app_identifier: 'xxxxxxx'
itc_team_id: 'xxxxxxx'
team_id: 'xxxxxxx'

INFO [2022-07-18 17:39:08.60]: ------------------------
INFO [2022-07-18 17:39:08.60]: --- Step: testflight ---
INFO [2022-07-18 17:39:08.60]: ------------------------
INFO [2022-07-18 17:39:08.60]: Login to App Store Connect (xxxxxxx)
Reading keychain entry, because either user or password were empty
Loading session from 'xxxxxxxxxxxxxxx'
Looking for App Store Connect Team with ID xxxxxxx
INFO [2022-07-18 17:39:10.30]: Login successful
DEBUG [2022-07-18 17:39:10.30]: App Platform (ios)
INFO [2022-07-18 17:39:10.30]: $ xar -C /var/folders/f9/bn94wk756dj9trk3v8rd2lww0000gn/T/d20220718-33664-ljrpxv -xf xxxxxxx.pkg
INFO [2022-07-18 17:39:10.75]: $ xar -C /var/folders/f9/bn94wk756dj9trk3v8rd2lww0000gn/T/d20220718-33664-zp5v24 -xf xxxxxxx.pkg
DEBUG [2022-07-18 17:39:11.18]: App identifier (xxxxxxx)
INFO [2022-07-18 17:39:13.07]: Waiting for processing on... app_id: xxxxxxx, app_version: 1.0, build_version: 246, platform: IOS
WARN [2022-07-18 17:39:14.44]: Read more information on why this build isn't showing up yet - https://github.com/fastlane/fastlane/issues/14997
INFO [2022-07-18 17:39:14.44]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
12.3.1

Ruby
2.6.8

Bundler?
true

Git
git version 2.32.1 (Apple Git-133)

Installation Source
~/.gem/bin/fastlane

Host
macOS 12.3.1 (21E258)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
13.4.1

Swift Version
5.6.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

after_all do |lane|
  if lane == :number || lane == :refresh_dsyms || lane == :promote_latest
    puts "lane is `#{lane}`, do not perform `after_all`"
  else
    increment_build_number(build_number: 1) # temporary, until we have real versions in place
    clean_build_artifacts
    push_git_tags
  end
end

lane :number do
  mac_latest = latest_testflight_build_number(platform: "osx")
  ios_latest = latest_testflight_build_number
  build_number = ((max = mac_latest > ios_latest ? mac_latest : ios_latest) + 1).to_s
  increment_build_number(build_number: build_number)
end

private_lane :send_dsyms_to_bugsnag do |options|
  download_dsyms(build_number: options[:build_number])       # Download dSYM files from App Store Connect

  bugsnag_key = "xxxxxxx"
  upload_symbols_to_bugsnag(api_key: bugsnag_key)            # Upload them to Bugsnag
end

private_lane :bugsnag do
  key = "xxxxxxx"
  upload_symbols_to_bugsnag(api_key: key)
  send_build_to_bugsnag(api_key: key)
end

platform :ios do
  before_all do |lane|
    if lane == :refresh_dsyms || lane == :promote_latest
      puts "lane is `#{lane}`, do not perform `before_all`"
    else
      number
      cert
      sigh
    end
  end

  desc "Promote the latest build to External Testers"
  lane :promote_latest do
    # TODO: validate that `latest` is in `Another Group`
    testflight(
      groups: ['Group Name'],
      distribute_only: true,
      app_platform: "ios",
      build_number: "#{latest_testflight_build_number}"
    )
  end

  desc "Push a new Lite build to the AppStore"
  lane :lite do |options|
    update_xcconfig_value(
      path: 'Shared/BuildConfig.xcconfig',
      name: 'IS_LITE_BUILD',
      value: 'YES'
    )

    # TODO: fail if `version_number` wasn't passed
    increment_version_number(version_number: options[:version_number])
    app_store

    update_xcconfig_value(
      path: 'Shared/BuildConfig.xcconfig',
      name: 'IS_LITE_BUILD',
      value: 'NO'
    )
    increment_version_number(version_number: '1.0')
  end

  desc "Push a new build the AppStore"
  private_lane :app_store do
    app_store_build

    deliver(
      submit_for_review: true,
      force: true, # skip the check for screenshots, since we usually aren't changing them
      automatic_release: false,
      submission_information: { add_id_info_uses_idfa: false }
    )

    add_git_tag(includes_lane: false)

    bugsnag
  end

  desc "Push a new build to External TestFlight"
  lane :external do |options|
    app_store_build

    testflight(
      distribute_external: true,
      groups: ['Another Group'],
      changelog: options[:changelog]
    )

    add_git_tag(includes_lane: false)

    bugsnag
  end

  desc "Push a new internal build to TestFlight"
  lane :internal do
    commit = last_git_commit
    hash = commit[:commit_hash] # long sha of commit

    build("Release")

    testflight(skip_waiting_for_build_processing: true, changelog: hash)

    add_git_tag(includes_lane: false)

    # bugsnag
  end

  private_lane :app_store_build do
    build("App Store")
  end

  def build(configuration)
    build_app(
      configuration: configuration,
      scheme: "xxxxxxx (iOS)",
      include_symbols: true,
      include_bitcode: true,
      export_options: {
        provisioningProfiles: {
          "xxxxxxx" => "xxxxxxx",
          "xxxxxxx" => "xxxxxxx",
          "xxxxxxx" => "xxxxxxx"
        }
      }
    )
  end

  lane :refresh_dsyms do |options|
    send_dsyms_to_bugsnag(build_number: options[:build_number])

    bugsee_token = "xxxxxxx"
    upload_symbols_to_bugsee(app_token: bugsee_token, agent_path: "./BuildTools/BugseeAgent")

    # Delete the local dSYM files
    clean_build_artifacts
  end
end

platform :mac do
  before_all do |lane|
    if lane == :refresh_dsyms || lane == :promote_latest
      puts "lane is `#{lane}`, do not perform `before_all`"
    else
      number
      cert(platform: "macos")
      sigh(platform: "macos")
    end
  end

  desc "Promote the latest build to External Testers"
  lane :promote_latest do
    testflight(
      groups: ['Group Name'],
      distribute_only: true,
      app_platform: "osx",
      build_number: "#{latest_testflight_build_number(platform: "osx")}"
    )
  end

  desc "Push a new build the AppStore"
  private_lane :app_store do |options|
    build_mac("App Store", options[:scheme])
    testflight(
      app_platform: "osx",
      distribute_external: true,
      groups: ['Another Group'],
      changelog: options[:changelog]
    )

    add_git_tag(includes_lane: false)

    bugsnag
  end

  desc "Push a new build to External TestFlight"
  lane :external do |options|
    build_mac("App Store", "xxxxxxx (macOS)")

    testflight(
      app_platform: "osx",
      distribute_external: true,
      groups: ['Another Group'],
      changelog: options[:changelog]
    )

    add_git_tag(includes_lane: false)

    bugsnag
  end

  desc "Push a new internal build to TestFlight"
  lane :internal do
    commit = last_git_commit
    hash = commit[:commit_hash] # long sha of commit

    build_mac("Release", "xxxxxxx (macOS)")

    testflight(
      app_platform: "osx",
      skip_waiting_for_build_processing: true,
      changelog: hash
    )

    add_git_tag(includes_lane: false)

    bugsnag
  end

  def build_mac(configuration, scheme)
    build_mac_app(
      configuration: configuration,
      export_method: "app-store",
      scheme: scheme,
      include_symbols: true,
      include_bitcode: true,
      export_options: {
        provisioningProfiles: {
          "xxxxxxx" => "xxxxxxx",
          "xxxxxxx" => "xxxxxxx",
          "xxxxxxx" => "xxxxxxx"
        }
      }
    )
  end

  lane :refresh_dsyms do |options|
    send_dsyms_to_bugsnag(build_number: options[:build_number])
    # no bugsee, because they don't have a mac library
    clean_build_artifacts                                      # Delete the local dSYM files
  end
end

`./fastlane/Appfile`
app_identifier("xxxxxxx") # The bundle identifier of your app

itc_team_id("xxxxxxx") # App Store Connect Team ID
team_id("xxxxxxx") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.207.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-bugsnag
2.2.1
✅ Up-To-Date

fastlane-plugin-xcconfig
2.0.0
✅ Up-To-Date

fastlane-plugin-bugsee
1.0.2
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.3.0

bundler
1.17.2

etc
1.0.1

forwardable
1.2.0

rake
13.0.6

rexml
3.2.5

CFPropertyList
3.0.5

public_suffix
4.0.7

addressable
2.8.0

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.2.0

aws-partitions
1.608.0

aws-sigv4
1.5.0

jmespath
1.6.1

aws-sdk-core
3.131.3

aws-sdk-kms
1.58.0

aws-sdk-s3
1.114.0

babosa
1.0.4

claide
1.1.0

colored
1.2

colored2
3.1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.4

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.6

emoji_regex
3.2.3

excon
0.92.3

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

multipart-post
2.0.0

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.0

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

gh_inspector
1.1.3

jwt
2.4.1

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.17.0

googleauth
1.2.0

httpclient
2.8.3

mini_mime
1.1.2

trailblazer-option
0.1.2

uber
0.1.0

representable
3.2.0

retriable
3.1.2

webrick
1.7.0

google-apis-core
0.7.0

google-apis-androidpublisher_v3
0.25.0

google-apis-playcustomapp_v1
0.10.0

google-apis-iamcredentials_v1
0.13.0

google-apis-storage_v1
0.18.0

google-cloud-env
1.6.0

google-cloud-errors
1.2.0

google-cloud-core
1.6.0

google-cloud-storage
1.37.0

json
2.6.2

mini_magick
4.11.0

naturally
2.2.1

optparse
0.1.1

plist
3.6.0

rubyzip
2.3.2

security
0.1.3

simctl
1.6.8

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.22.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

fastlane-plugin-bugsee
1.0.2

rchardet
1.8.0

git
1.11.0

xml-simple
1.1.9

fastlane-plugin-bugsnag
2.2.1

fastlane-plugin-xcconfig
2.0.0

generated on: 2022-07-18

I was able to fix this issue by deleting a stray .pkg file that was sitting in my repo (from a recent macOS build). However, it still seems like a bug to have app_platform:"ios" build_number:252 get overridden just because there's a build artifact in the repo.

It's hard to understand how it'd happen (if there's an IPA)
looking at upload_to_testflight.rb and pilot/build_manager.rb it seems like the IPA file would always win if it could be found
does anything jump out to you if you read through the code?

So my particular use case is for just adding a group to a build that has already been uploaded, meaning that there's actually no IPA or PKG to upload in this scenario.

Oh I see
So I believe the problem is here:
https://github.com/fastlane/fastlane/blob/e8d30e3494024b6d4ee81bf21448991779ca278d/pilot/lib/pilot/build_manager.rb#L101-L110
for the :ipa and :pkg branches of the conditional, it should only run if distribute_only is false but the current code doesn't check that, it just seems to implicitly assume if an ipa/pkg is present it should use that
I probably won't have bandwidth to fix it soon but I'd be happy to review & merge a PR if you'd like to take a stab at it?

Will do, thanks!!


Suggestion: support multiple configured elements in Updaters

To simplify code like...
el1 = createThing1()
new PropertyUpdater({variable: variable, element: el1...
el2 = createThing2()
new PropertyUpdater({variable: variable, element: el2...
elN = createThingN()
new PropertyUpdater({variable: variable, element: elN...

It might be nice to support multiple (statically) configured elements in Updaters.  There is somewhat related support for specifying a selector, but not an explicit list of elements.
E.g.
new PropertyUpdater({
  name: 'disabled',
  elements: [e1, e2, e3],
  variable: disabledVar
})

I started on a tentative patch, which was mostly a straightforward conversion from operating on this.element to iterating on this.elements, but ran into this line that I'm not sure what to do with:
if (!context || context == this.element || context.contains(this.element)) {
I think in this case the intent is to determine whether the passed context "matches" the element configuration of the updater; i'm not sure if that makes sense in the case of multiple elements, or perhaps warrants a more sophisticated check for array inclusion.
ListUpdater would get a bit more complicated since it has state, I suspect that would only require keeping a map of builtList on element.
Not a high priority, I just wanted to see if it was something that could be done simply and fit with the intent of Updaters (maybe there is a better way to aggregate similar Updaters).

FWIW #10


Console colors are not restored on Windows

Failing tests set color to red and do not restore (on Windows), so that all subsequent output is red.
Program to reproduce:
#define BOOST_TEST_MODULE My Test
#include <boost/test/included/unit_test.hpp>
BOOST_AUTO_TEST_CASE(my_test)
{
    int i = 1;
    BOOST_TEST(i == 2);
    BOOST_TEST(i == 3);
}

Fix on branch topic/GH-254-color-restored-windows. Would be good if you give a try.

I tested on Windows: commit https://github.com/boostorg/test/commit/63ab1f2bd67bb80ba8512a560fd42065295151c0 fixes this bug. Colors are restored.

Fixed in master