Release to conda-forge and defaults simultaneously

For 1.10 the plan is to to update the recipe on conda-forge and then immediately get that recipe onto anaconda defaults channel so conda install holoviews works without specifying a channel. The goal is to move away from using the ioam channel and maybe use the holoviews channels for 'nightlies' (actually automated packages for PRs merged to master).

Is the plan that 'latest master' conda packages for param (+gui toolkits) would also be uploaded to the holoviews channel?

I'm not sure how much of that is 'holoviews', so maybe we should make a general 'pyviz' channel?

A pyviz channel seems like an excellent idea.

Instead of a holoviews channel.

That would be fine by me..the holoviews channel never really got used.

Yes, fine with me. I asked because I'm keen for there to be as few channels as possible...ideally just one even...

I've registered pyviz on anaconda.org so we can start using that...

Would there be any interest in doing dev releases on conda-forge? Just noticed 1.10.0a1 got tagged so figured I'd ask. ;)

@jakirkham I'm not against this idea, especially if it can be automated.
If it can't be automated, then it means these releases are more work to do which means they are more likely to be infrequent (something we are currently trying to get away from!)

Or alternatively, if someone else is willing to update conda-forge for dev releases. :-)

There's been some work on an autoupdate bot. It's very new and docs are scarce. That said, most maintainers don't need to do anything with it per se. However it could learn a few things like how to update the dependencies or other recipe metadata. Though it's pretty good for being around a little over 1wk. :)
Was asking as this particular dev release was interesting to me. That said, can't promise that I'll always be able to update all dev releases. Hope you understand. :)

Looks like the autoupdate bot will ignore alphas: https://github.com/conda-forge/holoviews-feedstock/pull/25
Shame as dev builds from -c conda-forge/label/dev would have been nice!

Yeah I agree.
It's a little complicated as handling every projects' dev releases likely comes with a significant burden resource-wise and maintenance-wise. OTOH it's a really nice service to provide to developers and users. Not sure the right way to untangle it ATM, but did leave a note along these lines.

Dev builds are now configured on conda-forge for holoviews:
conda install -c conda-forge/label/dev holoviews

This is just a reminder for myself to update the source correctly in meta.yaml on the feedstock master when 1.10 is released.

I've closed the other conda-forge related issue and would like to close this one too. @jlstevens If you want to record anything here, I'd prefer opening a packaging meta-issue to describe anything we need to remember during our migration to pyct.

On second thought, please do open such a issue if you think it's a good idea but this issue seems to be specifically about 1.10 and mentions long outdated plans about a holoviews channel so I'm closing as I'm cleaning up in anticipation for a 1.11 release and reassigning issues to the 1.11.x release series.


MismatchSenderId for Android.

Expected Behaviour
I should receive push notification on my Android device with simple tittle and message.
Actual Behaviour
I am getting [ { error: 'MismatchSenderId' } ] alvase.
Example
I am using node-gcm to send notification and i copied code example from example in this project.
var gcm = require('node-gcm');
// Replace these with your own values.
var apiKey = "Server key from firebase";
var deviceID = "Registration ID from device";
var service = new gcm.Sender(apiKey);
var message = new gcm.Message();
message.addData('title', {"locKey": "push_app_title"});
message.addData('message', 'Simple non-localizable text for message!');
// Constant with formatted params
// message.addData('message', {"locKey": "push_message_fox", "locData": ["fox", "dog"]});
service.send(message, { registrationTokens: [ deviceID ] }, function (err, response) {
    if(err) console.error(err);
    else    console.log(response);
});

All code that i used for app itself i used this tutorial: http://macdonst.github.io/push-workshop-eu/
But i just used senderID from my Firebase.

@filippetroviccc well the error is correct. Somehow you are using one ID to send and a different ID to register with the server. How are you running the app? If you are following that tutorial and doing phonegap serve you'll need to send via the phonegap CLI.

@macdonst thank you for replying so fast, your are right i am using phonegap serve and i was using phonegap cli to test code, and everything worked correctly. But i want to send notifications from node. Is that possible?

@filippetroviccc when you use phonegap serve it replaces your sender id with one that can work with the CLI and developer apps. We have to do this in order to allow people to test. If you want to send notifications from node you'll need to add the android platform and run it on a device.
The browser platform is for testing your functionality when the on('notification') event is received. Sorry, that's the best I can do.

@macdonst So i need to build my app and install on my device to test if node sends notification?

@macdonst Thank you for help i just solved issue. I just build my app and all worked correctly.


Signal

Perhaps the most surprising thing I learned about Signal when I spoke with Moxie Marlinspike, the encrypted chat service’s creator, last year at Disrupt, was that it was essentially running on a shoestring budget.

https://techcrunch.com/2018/02/21/signal-expands-into-the-signal-foundation-with-50m-from-whatsapp-co-founder-brian-acton/

That's a good one! Added it to https://github.com/nayafia/lemonade-stand/pull/76 as an example of a foundation supporting open source development.


Bug - Admin unable to view Application and Applicant

Description
An admin is unable to view an application or application profile linked from the Applicant Sorting screen.
Steps to Reproduce
Steps to reproduce the behavior. Example:

Log in to admin portal.
Use the jobs panel to find the id of a Strategic Talent Response job.
Go to the job's summary page by directly entering the url: /manager/jobs/{id}
Click View Applications
Click View Applicant or View Profile for a single application.

Images
Place image attachments here.

[ ] Regression test written.

Let's ask if it's still a problem

I can't reproduce this, and I reported it.


[BUG] TS2339: Property 'on' does not exist on type.

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
We observed a weird behavior when migrating to cds 8 and cds-types 0.7.0.
Custom handler cannot be registered properly. A typescript error is thrown.
error TS2339: Property 'on' does not exist on type 'AdminService'.
import { ApplicationService } from '@sap/cds';

export default class AdminService extends ApplicationService {
  init() {
    this.on('health', () => {
      return { status: 'UP' };
    });
  }
}

But it works when this is cast to ApplicationService.
import { ApplicationService } from '@sap/cds';

export default class AdminService extends ApplicationService {
  init() {
    (this as ApplicationService).on('health', () => {
      return { status: 'UP' };
    });
  }
}

Expected Behavior
No response
References
https://pages.github.tools.sap/cap/docs/tools/cds-typer#typer-top-level-imports
Versions

backend
https://github.com/<your/repo>

@cap-js/asyncapi
1.0.2

@cap-js/audit-logging
0.8.1

@cap-js/cds-types
0.7.0

@cap-js/db-service
1.14.1

@cap-js/hana
1.4.1

@cap-js/openapi
1.0.7

@cap-js/sqlite
1.7.6

@cap-js/telemetry
1.0.1

@sap/cds
8.4.0

@sap/cds-compiler
5.4.0

@sap/cds-dk
8.4.0

@sap/cds-dk (global)
8.4.0

@sap/cds-fiori
1.2.7

@sap/cds-foss
5.0.1

@sap/cds-mtxs
2.3.0

@sap/eslint-plugin-cds
3.0.4

Node.js
v20.15.1

Anything else? Logs?
No response

Hi Sébastien,
thanks for reporting this issue!
This looks a bit like TS is trying to infer the type from the implementation files, which would imply you don't have cds-types installed in your project.
Please note that since cds8, @cap-js/cds-types has to be installed explicitly and is no longer pulled in from @sap/cds.
Did you add @cap-js/cds-types as devDependency to your project and install it?
Best,
Daniel

Actually, I am pretty sure this is a duplicate of https://github.com/cap-js/cds-types/issues/251
If you do have cds-types installed, can you please run npm rebuild in your project and see, if that fixes the problem?

Hi Daniel,
Yes, we do have cds-types installed as you can see in the summary.
We use pnpm, so this might be similar to the issue you mentioned.
But, this works well with version 0.6.5.

Hi Sébastien,
thanks for checking! Please also check out my other suggestion.
Best,
Daniel

Hi Sébastien,
can you please check out @hakimio's suggestion and see if that solves the problem for you?
If it does, could you please also elaborate a bit on your setup? Do you use a monorepo? If so, do the submodules of that monorepo have a dependency on cds-types?
Best,
Daniel

@sebastien-savalle how does your tsconfig look like? Does the types config work if you set moduleResolution to NodeNext?

No, this does not work even with moduleResolution set to NodeNext
And pnpm rebuild is sometimes helpful when everything looks broken.
tsconfig:
{
  "compilerOptions": {
    /* Basic Options */
    "target": "es2019",
    "module": "nodenext",
    "outDir": "./gen",
    "rootDir": "./",
    "baseUrl": ".",
    "moduleResolution": "nodenext",
    "skipLibCheck": true,
    "preserveConstEnums": true,
    "sourceMap": true,
    "allowJs": true,
    "strict": true,
    "strictNullChecks": true,
    "strictPropertyInitialization": false,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    /* Experimental Options */
    "noImplicitAny": false,
    "emitDecoratorMetadata": true, /* Needed for the decorators in the Entities.ts and FunctionHandler.ts. Enables experimental support for emitting type metadata for decorators. */
    "experimentalDecorators": true, /* Enables experimental support for ES7 decorators. */
    "types": [
      "node",
      "jest",
      "express"
    ],
    "typeRoots": [
      "./types",
      "./node_modules/@types",
      "./node_modules/@cap-js/cds-types"
    ]
  },
  "include": [
    "../.eslintrc.json",
    "./srv/**/*.ts",
    "./types/**/**.d.ts",
    "./test/**/*.ts"
  ]
}


In-browser viewer stuck on ‘Compiling…’ step

Hi there 👋 Congratulations on a really, really cool project—I’m very excited to see where it goes.
I’ve been checking reanimate out today, and ran into a problem: when running the drawCircle example, the viewer app stays in Compiling… mode, and does not finish even given considerable time. The listener itself gives standard messages, and emits Reloading code… on a file change. Note that mp4 and gif output work perfectly.
I made an effort at debugging this: the WebSocket connection is established properly, but once that happens no further render or layout effects occur.
Running check  gives me:
reanimate checks:
  Has ffmpeg:                        4.3.1
  Has ffmpeg(rsvg):                  no
  Has dvisvgm:                       'dvisvgm' not found
  Has povray:                        'povray' not found
  Has blender:                       no
  Has rsvg-convert:                  2.48.8
  Has inkscape:                      no
  Has imagemagick:                   7.0.10-25
  Has LaTeX:                         'latex' not found
  Has LaTeX package 'babel':         n/a
  Has LaTeX package 'preview':       n/a
  Has LaTeX package 'amsmath':       n/a
  Has XeLaTeX:                       'xelatex' not found
  Has XeLaTeX package 'ctex':        n/a

I’m using macOS Catalina 10.15.6, with Safari 13.1.2, running from fish-shell. Thanks in advance, and please forgive me if the solution is obvious!

Hi Patrick
How are you running the drawCircle example? Are you using stack?
This is what it looks like for me when I use Safari:
Imgur

I’m using cabal-install v<IP_ADDRESS>. I’ll give stack a shot.

The browser-viewer uses stack under the hood to compile the animation. Stack probably tried to install a version of GHC + all of reanimate's dependencies. That's why it was stuck on "Compiling...".
I wonder if I can detect whether cabal or stack is being used.


node agent performance and linux interaction

in order to optimize the reconciling process we might think of some optimizations:
I will put some suggestions here, especially for systemd, package management, etc.
for versionchecks it might be:
 time rpm -q --queryformat '%{NAME}-%{VERSION}-%{RELEASE}\n' docker-ce kubelet kubectl kubernetes-cni kubeadm
docker-ce-19.03.5-3.el7
kubelet-1.18.8-0
kubectl-1.18.8-0
kubernetes-cni-0.8.6-0
kubeadm-1.18.8-0

real	0m0.054s
user	0m0.036s
sys	0m0.010s

in comparison to:
time sudo yum list installed
eoIP.x86_64                                                                            1.5.0-14.el7                                                                @base
PyYAML.x86_64                                                                           3.10-11.el7                                                                 installed
acl.x86_64                                                                              2.2.51-15.el7                                                               @base
audit.x86_64                                                                            2.8.5-4.el7                                                                 @base
......
real	0m2.945s
user	0m2.184s
sys	0m0.365s

this will relief the yum db significantly

package-cleanup --dupes

shall ONLY run id the yum db is broken, it runs regulary a the moment.

yum install $1 $2 $3

shall only run once/or if it is needed. at the moment it runs regulary each intervall

systemctl daemon-reload

why is the complete systemctl configuration reloaded ?

yum cron disable/enable

yum cron should be enabled ONCE, and will handle the package updates then automatically. there is no need to disable the agent


Closes #593 | Add Dataloader XQuAD-R

Closes #593
There are 2 subsets. Configs will look like this: xquadr_vie_source, xquadr_tha_seacrowd_qa, etc. When testing, pass xquadr_<subset> to the --subset_id parameter.
I will add a new PR for adding the QAR task once this PR is checked, and remove the relevant file from this PR.
Checkbox

[x] Confirm that this PR is linked to the dataset issue.
[x] Create the dataloader script seacrowd/sea_datasets/my_dataset/my_dataset.py (please use only lowercase and underscore for dataset naming).
[x] Provide values for the _CITATION, _DATASETNAME, _DESCRIPTION, _HOMEPAGE, _LICENSE, _URLs, _SUPPORTED_TASKS, _SOURCE_VERSION, and _SEACROWD_VERSION variables.
[x] Implement _info(), _split_generators() and _generate_examples() in dataloader script.
[x] Make sure that the BUILDER_CONFIGS class attribute is a list with at least one SEACrowdConfig for the source schema and one for a seacrowd schema.
[x] Confirm dataloader script works with datasets.load_dataset function.
[x] Confirm that your dataloader script passes the test suite run with python -m tests.test_seacrowd seacrowd/sea_datasets/<my_dataset>/<my_dataset>.py.
[ ] If my dataset is local, I have provided an output of the unit-tests in the PR (please copy paste). This is OPTIONAL for public datasets, as we can test these without access to the data files.

Since both recommendations have no impact on the dataloader implementation (just for code aesthetics to remove unused comments), I will merge this PR to master since the review session ended on 30 May.


chore: editor improvements

Various improvements in the editors:

Support deleting a choice using backspace key
Add placeholder to content body
Add tooltip for drafts button
Separate draft and publish button, and use primary color for publish
Rename voting type to voting system

Support deleting a choice using backspace key

Let's say I have 3 choices: a, b, c
When I go to choice b, and delete the b character, the choice field is empty (current behavior)
When I BACKSPACE one more time, it's supposed to delete the empty choice, and I should end up with only 2 choices: a and c
But it's not the current behavior, deleting the choice 2 will also delete one character from the previous choice, so we end up with
choice 1: empty field
choice 2: c

Button text is not aligned

Fixed the text vertical alignement

Also fixed the button not being rounded on small screen

Support deleting a choice using backspace key

Let's say I have 3 choices: a, b, c
When I go to choice b, and delete the b character, the choice field is empty (current behavior)
When I BACKSPACE one more time, it's supposed to delete the empty choice, and I should end up with only 2 choices: a and c
But it's not the current behavior, deleting the choice 2 will also delete one character from the previous choice, so we end up with
choice 1: empty field choice 2: c

Good catch, need to fix this

I also added some improvement on the layout, forcing all content on same line, and truncating when needed
Before

After


Bump CLDRjs to 0.5.4

Latest version contains multiple fixes and improvements which would be good to have in Globalize :)
Signed-off-by: Georgi Tsaklev<EMAIL_ADDRESS>

Hi @rxaviers here is the bump in version for cldrJS with our recent fix in it.


Prevent block-only matchers from being used with value expectation target

The purpose of this (rather experimental) change is to restrict the usage of:
subject { -> { do_something } }
it { is_expected.to change(something).to(new_value) }

This syntax was referenced to as:

pretty obtuse and not something I’d recommend, generally.
https://github.com/rspec/rspec-expectations/issues/805#issuecomment-112239820

We should mention they’re not supported.
https://github.com/rspec/rspec-expectations/issues/805#issuecomment-112238533

Problems with this approach
Specs fail quite badly mostly due to the use of this syntax in RSpec Expectations' own specs:
RSpec.describe RSpec::Matchers::BuiltIn::ChangeToValue do
  k = 0
  before { k = 0 }
  it_behaves_like "an RSpec matcher", :valid_value => lambda { k = 2 },
                                      :invalid_value => lambda { k = 3 },
                                      :disallows_negation => true do
    let(:matcher) { change { k }.to(2) }
  end
end

Would you accept this if I change those specs to something more canonical? E.g. like:
RSpec.describe RSpec::Matchers::BuiltIn::ChangeToValue do
  let(:k) { 0 }
  it_behaves_like "an RSpec matcher" do
    let(:valid_value) { k += 1 }
    let(:invalid_value) { }

    def matcher
      change { k }.from(0)
    end
  end
end

The above change didn't work from the first time, but I'll keep trying if that's the right direction.

@JonRowe Builds are green, all specs are in place.
It took a while to work around Ruby 1.8.7 block signature strictness, moved stuff around.
No rush, please take another look when you have a moment.

Squashed commits.

@JonRowe Do you think this needs some adjustment?

@JonRowe Do you think this needs some adjustment?
I promise this is high on my list for a re-review!

Thanks!
I'm holding off from merging this, found a problem with rspec-collection_matchers, still getting to the bottom of it.
     NoMethodError:
       undefined method `supports_value_expectations?' for #<#<Class:0x00007fb20c0a7128>:0x00007fb20c0a7088>
     # ./lib/rspec/collection_matchers/have.rb:71:in `determine_collection'
     # ./lib/rspec/collection_matchers/have.rb:41:in `matches?'
     # ./spec/rspec/collection_matchers/have_spec.rb:532:in `block (4 levels) in <top (required)>'

Just found this change and it also breaks the following code. Not sure if that was intended:
      call = lambda do
        Reek::CLI::Silencer.silently do
          described_class.new ['--foo']
        end
      end
      expect(call).to raise_error(SystemExit) do |error|
        expect(error.status).to eq Reek::CLI::Status::DEFAULT_ERROR_EXIT_CODE
      end

@mvz Would you accept the code written as:
     expect do
       Reek::CLI::Silencer.silently do
         described_class.new ['--foo']
       end
     end.to raise_error(SystemExit) do |error|
       expect(error.status).to eq Reek::CLI::Status::DEFAULT_ERROR_EXIT_CODE
     end

It's also possible to extract the lambda to a method and use expect { silencer_configured_with_foo_option }.to raise_error ....

@pirj Yes, both are fine options, although I would prefer the second one rather than chaining multi-line blocks. I was just surprised my existing specs started failing.
I fixed my code by changing expect(call) to expect(&call).

This PR has been reverted for now.

I would like to include this again, but we need to address the following situations:

Transitionally allow blocks to be in-explicitly passed in for future deprecation and warning. This is quite easy to achieve but has knock on effects for the next thing I'd like to address.
Still allow passed in blocks to be introspected as values.

@JonRowe Sounds good. I can tackle this in the near future.
What I intend to do is to warn in enforce_value_expectation instead of failing.
Not sure I completely understand what you mean by block introspection, can you please elaborate a bit?

Things like expect(-> { }).to be_a(Proc)


Fix regressions in lightbox and add snapshot tests.

I wanted to prevent such regressions and in the process added snapshot tests and refactored lightbox dir.
Followup

components which are connected to redux store, need to provide Connector flow type, only then we would be able to detect flow errors in such cases.
example: https://github.com/reactjs/redux/tree/master/examples/todos-flow
need to figure out connectActionSheet flow type since expo/react-native-action-sheet doesn't export it.

Suggestions welcome.

Pretty good and extensive job!
I am questioning a bit the idea for the utils/test.js as it might make stuff a bit less clear, and they are simple without it. Though I also think it is helpful in other ways.
Not sure about the snapshot tests either, but let's give them a chance :)

I am questioning a bit the idea for the utils/test.js as it might make stuff a bit less clear, and they are simple without it. Though I also think it is helpful in other ways.

I agree, this might not be needed.
posting an example here for future reference; after these changes we can also do
import { rendererWithStore } from 'utils/tests';
import MyComponent from 'path/to/component';

const tree = rendererWithStore(<MyComponent />);

instead of
import Provider from 'redux';
import renderer from 'react-test-renderer';

import MyComponent from 'path/to/component';
import store from './store';

const tree = rendererWithProvider(
  <Provider store={store}>
    <MyComponent />
  </Provider>
);


Feature/documentation update

Updating comments to allow ng-docs to generate a document.

As discussed, this pull request looks redundant


Differential drive platform support in YARP

I know that YARP is specialized for humanoid robots. Is there off-the-shelf support for any differential drive robotic platform?

Hi @pauljurczak
We have used YARP for developing the control of an holonomic mobile platform called iKart. The relative software is available at https://github.com/robotology/ikart.
Compared with iKart, a standard differential drive robot turns to be much simpler to control, even though to my knowledge I don't know whether there might be already some YARP code for that.
Interestingly, quickly browsing the net, I've found this link out of a library called MORSE which apparently provides a simulated differential drive control also for YARP.


test: Update tests to support latest fetch-mock/sinon version

Instructions

PR target branch should be against development
PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary
As part of browser modernization, I am updating fetch mock, and sinon.  This PR is for fetch-mock.  Previously we were pulling it in via a karma config file which was setting it on the window.  This is not necessary now that we are importing it directly.  In my testing when transpiling, pulling fetch-mock directly did not work, I had to do fetch-mock/esm/client.  Might be a bug to figure out later, but since this is just for testing purposes and not in our code base, I don't think it's a big deal.
Changes include:

window.fetchMock --> fetchMock
._calls -> calls()
.calls = [] to clear all calls --> .resetHistory
slight modifications to the tests/utils.js file because the payload changed between v7 and v9 of fetch-mock,
The new version of sinon disallows calling useFakeTimers multiple times, so I had to delete a few references to that where it was calling it more than once.

Remarking that Sinon actually released version 17 on Friday, but I stuck with their last 16.X to avoid any new major version bugs. I tested the changes on 17 and everything seems to be fine...but just in case.
Testing Plan

[X] Was this tested locally? If not, explain why.

Reference Issue (For mParticle employees only.  Ignore if you are an outside contributor)

Closes https://go.mparticle.com/work/SQDSDKS-5887

Looks like I had to rebase master and force push because of package-lock conflicts.    Relevant changes since you last looked are here https://github.com/mparticle/mparticle-web-sdk/compare/5a26facdc8a0e91ce179f6f4e6a8615c11982606...4049f578e0ecfa1c21e4cf7ede1447436a16fbc0


Color Refator

1.Using Properties as configuration file, creating Color.properties and ConfigurationProperties.class that load Color.properties.
2.Implement Properties to support Nested by creating PropertiesEnhance.class.
3.Implement Convert between Color Object and Color Hex String, including RGB mode and RGBA mode.
4.Encapsulate a Class to read Color from configuration file by using a function called "findColor(key)", and return the Color Object.
5.Replace some key Color Object by using reading from Configuration file.
6.Optimize the modern style button.

1.Using Properties as configuration file, creating Color.properties and ConfigurationProperties.class that load Color.properties.
2.Implement Properties to support Nested by creating PropertiesEnhance.class.
3.Implement Convert between Color Object and Color Hex String, including RGB mode and RGBA mode.
4.Encapsulate a Class to read Color from configuration file by using a function called "findColor(key)", and return the Color Object.
5.Replace some key Color Object by using reading from Configuration file.
6.Optimize the modern style button.

If possible, next time a more specific name of the PR is preferred. So that people don't get confused about the functionalities added by this PR.


create-a-new-release-in-jira 1.0.2

What to do if the build fails?
At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.
New Pull Request Checklist
Please mark the points which you did / accept.

[ ] I will not move an already shared step version's tag to another commit
[ ] I read the Step Development Guideline
[ ] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[ ] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[ ] I read and accept the Abandoned Step policy

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Juan Ler seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


⚠ Bofrost.de has degraded performance

In b04b821, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1743 ms

Resolved: Bofrost.de performance has improved in 8bb5a4c after 8 minutes.


[WIP] coverage: Use upstream coverage collect script

Our custom collect script should no longer be necessary as upstream now has the support for which it was added

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

it might be better to use a patch rather than custom file - best would be to not need any hacks

/retest mobile

/retest mobile again

/retest mobile to be sure (network tranients afaict)

/retest mobile

/retest mobile

this speeds coverage up pretty dramatically

more importantly its a step towards enabling rbe for coverage which should hopefully speed up more


Stop unconfirmed user invite causing a page error upon sign in

Problem: The Users::InvitationsController#create action was deleting permissions when an unconfirmed user was being invited again. This meant that users hit crazy errors if they were invited twice (or invited whilst being an unconfirmed user on a different org), as they didn't have permissions.
Solution: Stop existing users from being invited again.
Regression: This caused the resend invite process to stop working since it was using the Users::InvitationsController#create action to resend the invite to an existing user.
Solution: When resending an invite, delete the original invitation and then create a new one. This means the Users::InvitationsController#create only ever is called on new invites.

     ActionView::Template::Error:
       User#can_manage_locations? delegated to permission.can_manage_locations?, but permission is nil: #<User id: 12, email<EMAIL_ADDRESS>created_at: "2018-12-07 11:12:44", updated_at: "2018-12-07 11:12:44", organisation_id: 10, name: "claire", mobile: nil, super_admin: false>

This is a new error that I'm getting but it does give me confidence that the confirmation is working on the right email.

I haven't had the chance to dig properly into this yet, but from my read-through it looks good! A few hanging comments/tests that might not need to get merged in, can go into more detail tomorrow.
Said it already in person, but really like this way of approaching the problem - testing around the broken case first is :+1:


hold the graphs on kaput VMs for at least 3 minutes

15 minutes that is

more like 30 minutes at least!

60 minutes that is!

done, set to 30 mins (1800 seconds)


Webpack - PWA, offline and script preFetching

Description
When using a pwa, you expect the app to work as a mobile app. A mobile app is generally supposed to contain everything it needs to "work" offline (with a degraded service). In fact, you don't want your mobile app to crash all the time when you loose network. Currently, when trying to access offline a lazy loaded component which is not cached, the app crashes
Steps to reproduce

Configure a route with lazy loading
Access your app (and eventually install it as a pwa)
Shut down your network
Access your lazy loaded component
App crashes

Expected behavior

I think this could be improved the following ways

Lazy loaded scripts could actually be prefetched. I know that this is not totally what you expect when you make them lazy loaded. I think the main advantage of lazy loaded comes with the fact that it can split the .js in bundle files. Then, prefetching them is probably a good option. Networks are now fast enough to download completely an app without interference. With prefetching, pwa and offline app works as expected. Only dynamic content is not shown ...
This can be done with this plugin
If the previous approach is not kepts, I think the template should definitely implement an HOC ErrorBoundary component which would display a message to the user in case of any rendering or loading error.

Versions

React-Boilerplate: latest
Node/NPM: latest
Browser: chrome latest

Closed in favor of this


Rename structured to tabular

https://app.shortcut.com/galileo/story/5026/rename-structured-tabular

Codecov Report

Merging #571 (5368e3e) into main (fd9b26f) will not change coverage.
The diff coverage is 94.11%.

@@           Coverage Diff           @@
##             main     #571   +/-   ##
=======================================
  Coverage   89.25%   89.25%
=======================================
  Files         148      148
  Lines       11619    11619
=======================================
  Hits        10370    10370
  Misses       1249     1249

Impacted Files
Coverage Δ

...ity/loggers/model_logger/tabular_classification.py
87.50% <87.50%> (ø)

dataquality/core/log.py
95.53% <100.00%> (ø)

...lity/loggers/data_logger/tabular_classification.py
99.02% <100.00%> (ø)

...ty/loggers/logger_config/tabular_classification.py
100.00% <100.00%> (ø)

dataquality/schemas/task_type.py
100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@elboy3 something seems wrong here. 5000+ files doesn't look right

@elboy3 : You might need to revert your original commit (5368e3e) for the updated .gitignore to take effect.


Get EXIF data from image

Add an option to grab EXIF data from png images

This feature will be in another project


Flutter Compile Debug Kotlin Issue Project Not Debugging In Emulators

Hi, I'm new to flutter and mobile app development. I updated my flutter version last week after that created a new flutter project. I used audioplayers: ^0.19.0 package for my project. But now I couldn't run my project in emulators because below error message.
`FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':audioplayers:compileDebugKotlin'.
> Compilation error. See log for more details

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 50s

Exception: Gradle task assembleDebug failed with exit code 1
Exited (sigterm)
flutter`

I have no idea about this error message. I did some search about this error in google and found this error caused my flutter version. Is that right? Please can you guys help me to fix this issue. I will attach my main.dart file in below.
import 'package:flutter/material.dart';
import 'package:audioplayers/audioplayers.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatefulWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  _MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(
          title: Text('Simple Music'),
          backgroundColor: Colors.amber[300],
        ),
        body: SafeArea(
          child: Center(
            child: TextButton(
              child: Text("music"),
              onPressed: () {
                final player = AudioCache();
                player.play("note2.wav");
              },
            ),
          ),
        ),
      ),
    );
  }
}

Hi @Isuru01
Can you please reproduce the issue without audioplayers
Please provide your flutter doctor -v, your flutter run -v,  your pubspec.yaml, a minimal reproducible code sample that does not use 3rd party plugins, your complete flutter run -v logs running the minimal code sample
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


python312Packages.boto3-stubs: 1.34.122 -> 1.34.124, python312Packages.botocore-stubs: 1.34.122 -> 1.34.124

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

14 packages built:

aws-sam-cli
aws-sam-cli.dist
python311Packages.boto3-stubs
python311Packages.boto3-stubs.dist
python311Packages.botocore-stubs
python311Packages.botocore-stubs.dist
python311Packages.types-aiobotocore
python311Packages.types-aiobotocore.dist
python312Packages.boto3-stubs
python312Packages.boto3-stubs.dist
python312Packages.botocore-stubs
python312Packages.botocore-stubs.dist
python312Packages.types-aiobotocore
python312Packages.types-aiobotocore.dist


Running "pacaur -Syu" does not detect out-of-date packages

I noticed this when I started trying couple of yaourt commands after a long time of using pacaur as my aur helper. Before this log, I ran "pacaur -Syu" between yaourt commands to see what pacaur would list and it does list something -- One out-of-date package ( gtk-theme-arc-git ). Yaourt did detect that gtk-theme-arc have been updated (and wasn't on the list anymore). Is this a proper behaviour or am I missing something simple?
local/pacaur 4.2.27-1
local/yaourt 1.6-1

chris ~ $ pacaur -Syyua
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 antergos is up to date
:: Starting AUR upgrade...
 there is nothing to do

chris ~ $ yaourt -Syyua
:: Synchronizing package databases...
 core                              121.7 KiB   795K/s 00:00 [######################] 100%
 extra                            1741.9 KiB  3.59M/s 00:00 [######################] 100%
 community                           2.7 MiB  4.13M/s 00:01 [######################] 100%
 multilib                          125.9 KiB  4.10M/s 00:00 [######################] 100%
 antergos                          415.6 KiB   474K/s 00:01 [######################] 100%
 Foreign packages: - 150 / 150

==> Package upgrade only (new release):
aur/gnome-colors-icon-theme        5.5.1-2               2 -> 3
aur/gnome-colors-icon-theme-extras 5.5.1-2               2 -> 3
aur/gtk2-theme-dust                0.5.1-1               1 -> 2
aur/gtk2-theme-dust-extras         0.5.1-1               1 -> 2
aur/python2-ujson                  1.33-1                1 -> 2
aur/shimmer-wallpapers             1.0-2                 2 -> 4
aur/solaar                         0.9.2-1               1 -> 2
aur/xcb-util-cursor-git            1:0.1.2.r0.g8eb844d-1 1 -> 2
aur/zathura-cb                     0.1.4-2               2 -> 3

==> Software upgrade (new version) :
aur/antigen-git                    r335.30098c1-1        -> r358.7860ce7-1
aur/flattr-icon-theme-git          552.e7670d0-1         -> 560.222f37e-1
aur/i3status-git                   2.9.r22.g3545e03-1    -> 2.9.r37.gadaa832-1
aur/j4-dmenu-desktop-git           2.12.r4.g666dd0b-1    -> 2.12.r9.gebe007a-1
aur/liblxqt-git                    <IP_ADDRESS>.ga844118-1    -> <IP_ADDRESS>.gae45471-1
aur/libqtxdg-git                   <IP_ADDRESS>.gd5bc16b-1   -> <IP_ADDRESS>.gab0f65c-1
aur/lolcat                         42.0.99-3             -> 42.1.0-3
aur/paccache                       0.1.14-1              -> 0.1.15-1
aur/pcmanfm-qt-git                 <IP_ADDRESS>.g2a4ec48-1    -> <IP_ADDRESS>.g643dcf6-1
aur/python-click                   4.0-2                 -> 4.1-1
aur/python2-trollius               1.0.4-2               -> 2.0-1
aur/rofi-git                       r764.f14efce-1        -> 0.15.5.r38.g9b83c61-1
aur/ruby-rspec                     3.1.0-1               -> 3.3.0-1
aur/ruby-rspec-core                3.1.7-1               -> 3.3.0-1
aur/ruby-rspec-expectations        3.1.2-1               -> 3.3.0-1
aur/ruby-rspec-mocks               3.1.3-1               -> 3.3.0-1
aur/ruby-rspec-support             3.1.2-1               -> 3.3.0-1
aur/visual-studio-code             0.3.0-1               -> 0.5.0-3
aur/xcape-git                      1.1.9.gf3802fc-1      -> 1:1.1.r9.gf3802fc-2

==> Continue upgrade ? [Y/n]
==> [V]iew package detail   [M]anually select packages
==> --------------------------------------------------
==>

The above output only tell me you've done all AUR update before running pacaur. In other words, I have no idea what you're writing about. I don't even see any gtk-theme-arc in the yaourt output above.
Please give more details.

Hi rmarquis. I will break down what I did.
Ran pacaur commands for nearly everyday since March 3 (installation date).
Ran yaourt command for first time ever. 20+~ out-of-date packages. Cancelled.
Ran pacaur command. 1 out-of-date package. Updated gtk-theme-arc-git.
Ran yaourt command one more time. 19+~ out-of-date packages. Scrolled up the scrollback.
Compared 2nd yaourt command with 1st yaourt command. No gtk-theme-arc-git.
How do I update the missing 19+~ out-of-date packages that yaourt picked up?
I filed "Pacuar does not detect out-of-date packages." and wanted to know if I'm missing something simple...  because that's the result of running "yaourt -Syyua" exactly right after running "pacaur -Syyua".
TL:DR: yaourt detects more out-of-packages than pacaur.

All right, now I understand what you mean.
Do you happen to use AUR4 with yaourt? Pacaur defaults to AUR3. As far as I see, the output above looks like yaourt tries to update obsolete package in AUR3 to the newer version found in AUR4.
If you want to use AUR4 with pacaur, do the following:

install latest cower-git
add an alias in your .bashrc:

alias pacaur4='pacaur --domain aur4.archlinux.org'

source with . ~/.bashrc
then try to update again with pacaur4 -Syu.

Note that AUR4 will become the default on August 8, so this alias will stop working at that time.

I had cower-git installed. I have to install pacaur-git too. Both looks same at a glance (versions). There are many same package name (one and one without -git) with either same/different maintainers... even with orphaned packages. Heh. I overlooked the *-git part on Archlinux Pacaur Wiki. Sorry.
chris ~ $ pacaur -Ss pacaur
aur/pacaur 4.2.27-1 (314)
    A fast workflow AUR helper using cower as backend
aur/pacaur-git 4.2.27-1 (17) [installed: <IP_ADDRESS>.geb10499-1]
    A fast workflow AUR helper using cower as backend

Now using pacaur-git and cower-git.... Installing missing packages!
chris ~ $ pacaur --domain aur4.archlinux.org -Syu
[sudo] password for chris:
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 antergos is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Starting AUR upgrade...
:: archey is not present in AUR -- skipping
:: base16-shell-git is not present in AUR -- skipping
:: chromo-erectus-icon-themes is not present in AUR -- skipping
:: corebird-git is not present in AUR -- skipping
:: gcolor3 is not present in AUR -- skipping
:: gnome-color-chooser is not present in AUR -- skipping
:: gohufont is not present in AUR -- skipping
:: gtk-theme-numix-osx is not present in AUR -- skipping
:: gtk-theme-shiki-colors-flat is not present in AUR -- skipping
:: htop-vi is not present in AUR -- skipping
:: humanity-icon-theme is not present in AUR -- skipping
:: irssi-scripts-git is not present in AUR -- skipping
:: j4-make-config-git is not present in AUR -- skipping
:: node-webkit is not present in AUR -- skipping
:: numix-themes-darkblue is not present in AUR -- skipping
:: numix-themes-tomorrow is not present in AUR -- skipping
:: numix-themes-yellow is not present in AUR -- skipping
:: pipes-git is not present in AUR -- skipping
:: pkgtools is not present in AUR -- skipping
:: python-i3-git is not present in AUR -- skipping
:: python-neovim-git is not present in AUR -- skipping
:: python-virtkey is not present in AUR -- skipping
:: python2-wsgiref is not present in AUR -- skipping
:: quickswitch-i3-git is not present in AUR -- skipping
:: retroarch-git is not present in AUR -- skipping
:: retroarch-phoenix-qt-git is not present in AUR -- skipping
:: rmlint-git is not present in AUR -- skipping
:: sxhkd-git is not present in AUR -- skipping
:: termsyn is not present in AUR -- skipping
:: tightvnc is not present in AUR -- skipping
:: trash-cli is not present in AUR -- skipping
:: tv-maxe is not present in AUR -- skipping
:: twd is not present in AUR -- skipping
:: ultra-flat-gtk is not present in AUR -- skipping
:: urxvt-autocomplete-all-the-things-git is not present in AUR -- skipping
:: urxvt-font-size-git is not present in AUR -- skipping
:: vlc-skins is not present in AUR -- skipping
:: weatherboy is not present in AUR -- skipping
:: wine-silverlight is not present in AUR -- skipping
:: winusb is not present in AUR -- skipping
:: xcursor-human is not present in AUR -- skipping
:: zgen-git is not present in AUR -- skipping
:: resolving dependencies...
:: looking for inter-conflicts...
:: antigen-git latest revision -- fetching
:: flattr-icon-theme-git latest revision -- fetching
:: i3status-git latest revision -- fetching
:: j4-dmenu-desktop-git latest revision -- fetching
:: liblxqt-git latest revision -- fetching
:: libqtxdg-git latest revision -- fetching
:: pcmanfm-qt-git latest revision -- fetching
:: rofi-git latest revision -- fetching
:: xcape-git latest revision -- fetching
:: xcb-util-cursor-git latest revision -- fetching

AUR Packages  (28):

Name                                Old Version            New Version

aur/antigen-git                     r335.30098c1-1         latest
aur/flattr-icon-theme-git           552.e7670d0-1          latest
aur/gnome-colors-icon-theme         5.5.1-2                5.5.1-3
aur/gnome-colors-icon-theme-extras  5.5.1-2                5.5.1-3
aur/gtk2-theme-dust                 0.5.1-1                0.5.1-2
aur/gtk2-theme-dust-extras          0.5.1-1                0.5.1-2
aur/i3status-git                    2.9.r22.g3545e03-1     latest
aur/j4-dmenu-desktop-git            2.12.r4.g666dd0b-1     latest
aur/liblxqt-git                     <IP_ADDRESS>.ga844118-1     latest
aur/libqtxdg-git                    <IP_ADDRESS>.gd5bc16b-1    latest
aur/lolcat                          42.0.99-3              42.1.0-3
aur/paccache                        0.1.14-1               0.1.15-1
aur/pcmanfm-qt-git                  <IP_ADDRESS>.g2a4ec48-1     latest
aur/python-click                    4.0-2                  4.1-1
aur/python2-trollius                1.0.4-2                2.0-1
aur/python2-ujson                   1.33-1                 1.33-2
aur/rofi-git                        r764.f14efce-1         latest
aur/ruby-rspec                      3.1.0-1                3.3.0-1
aur/ruby-rspec-core                 3.1.7-1                3.3.0-1
aur/ruby-rspec-expectations         3.1.2-1                3.3.0-1
aur/ruby-rspec-mocks                3.1.3-1                3.3.0-1
aur/ruby-rspec-support              3.1.2-1                3.3.0-1
aur/shimmer-wallpapers              1.0-2                  1.0-4
aur/solaar                          0.9.2-1                0.9.2-2
aur/visual-studio-code              0.3.0-1                0.5.0-3
aur/xcape-git                       1.1.9.gf3802fc-1       latest
aur/xcb-util-cursor-git             1:0.1.2.r0.g8eb844d-1  latest
aur/zathura-cb                      0.1.4-2                0.1.4-3

:: Proceed with installation? [Y/n]

Yes, I forget that I modified /etc/yaourtrc to troubleshoot somebody with AUR4 issue on yaourt. Everything is working perfectly now. Many thanks for pacaur. It is one of my favourite tools.

No problem, you're very welcome.


Migration biztalk addtion

@Saisang,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/technical-guides/biztalk-server-2010-operations-guide.md
:warning:Warning
View
Details

biztalk/technical-guides/checklist-configuring-sql-server.md
:warning:Warning
View
Details

biztalk/technical-guides/checklist-installing-and-configuring-certificates.md
:warning:Warning
View
Details

biztalk/technical-guides/checklist-maintaining-and-troubleshooting-biztalk-server-databases.md
:warning:Warning
View
Details

biztalk/technical-guides/checklist-optimizing-performance-on-hyper-v.md
:warning:Warning
View
Details

biztalk/technical-guides/checklist-planning-for-operations-in-a-secure-environment.md
:warning:Warning
View
Details

biztalk/technical-guides/configuring-certificates-for-mime-or-smime-messages.md
:warning:Warning
View
Details

biztalk/technical-guides/installing-and-configuring-digital-certificates.md
:warning:Warning
View
Details

biztalk/technical-guides/system-level-bottlenecks.md
:warning:Warning
View
Details

biztalk/TOC.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/how-to-configure-biztalk-server-to-receive-encrypted-mime-or-smime-messages.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/how-to-configure-biztalk-server-to-receive-signed-mime-or-smime-messages.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/how-to-configure-biztalk-server-to-send-signed-mime-or-smime-messages.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/media/90f98f0d-a223-404c-b419-81369dc92970.gif
:white_check_mark:Succeeded
View

biztalk/technical-guides/step-4-configure-biztalk-server-environment-for-load-testing.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/tools-and-utilities-for-troubleshooting.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/tools-for-testing.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/biztalk-server-2010-operations-guide.md

Line 41: [Warning] Invalid file link:(~/Topic/Operations Checklists.md).
Line 41: [Warning] Invalid file link:(~/Topic/Increasing Availability for BizTalk Server.md).
Line 43: [Warning] Invalid file link:(~/Topic/Planning the Environment for BizTalk Server.md).
Line 45: [Warning] Invalid file link:(~/Topic/Maintaining BizTalk Server2.md).
Line 45: [Warning] Invalid file link:(~/Topic/Monitoring BizTalk Server2.md).
Line 45: [Warning] Invalid file link:(~/Topic/Increasing Availability for BizTalk Server.md).

biztalk/technical-guides/checklist-configuring-sql-server.md

Line 36: [Warning] Invalid file link:(~/Topic/Monitoring and Reducing Database IO Contention.md).
Line 39: [Warning] Invalid file link:(~/Topic/Monitoring and Reducing DTC Log File Disk IO Contention.md).
Line 40: [Warning] Invalid file link:(~/Topic/Planning for Database Availability.md).
Line 41: [Warning] Invalid file link:(~/Topic/Reviewing and Testing SQL Server Cluster Configuration for Failover Scenarios.md).
Line 42: [Warning] Invalid file link:(~/Topic/SQL Server Settings That Should Not Be Changed.md).
Line 46: [Warning] Invalid file link:(~/Topic/Clustering the Master Secret Server.md).
Line 54: [Warning] Invalid file link:(~/Topic/Defining Auto-Growth Settings for Databases.md).
Line 55: [Warning] Invalid file link:(~/Topic/Backing Up Databases.md).
Line 56: [Warning] Invalid file link:(~/Topic/Monitoring SQL Server Agent Jobs.md).
Line 57: [Warning] Invalid file link:(~/Topic/Purging and Archiving Tracking Data.md).
Line 64: [Warning] Invalid file link:(~/Topic/Backing Up Databases.md).
Line 66: [Warning] Invalid file link:(~/Topic/Monitoring SQL Server Agent Jobs.md).
Line 73: [Warning] Invalid file link:(~/Topic/Using BizTalk Server Log Shipping for Disaster Recovery.md).
Line 74: [Warning] Invalid file link:(~/Topic/Using BizTalk Server Log Shipping for Disaster Recovery.md).
Line 75: [Warning] Invalid file link:(~/Topic/Using BizTalk Server Log Shipping for Disaster Recovery.md).
Line 82: [Warning] Invalid file link:(~/Topic/Monitoring SQL Server Agent Jobs.md).
Line 83: [Warning] Invalid file link:(~/Topic/Monitoring SQL Server Agent Jobs.md).
Line 84: [Warning] Invalid file link:(~/Topic/Monitoring SQL Server Agent Jobs.md).
Line 98: [Warning] Invalid file link:(~/Topic/SQL Server Settings That Should Not Be Changed.md).
Line 100: [Warning] Invalid file link:(~/Topic/Monitoring and Reducing Database IO Contention.md).
Line 102: [Warning] Invalid file link:(~/Topic/Reviewing and Testing SQL Server Cluster Configuration for Failover Scenarios.md).
Line 104: [Warning] Invalid file link:(~/Topic/Defining Auto-Growth Settings for Databases.md).
Line 106: [Warning] Invalid file link:(~/Topic/Backing Up Databases.md).
Line 108: [Warning] Invalid file link:(~/Topic/Using BizTalk Server Log Shipping for Disaster Recovery.md).
Line 110: [Warning] Invalid file link:(~/Topic/Monitoring SQL Server Agent Jobs.md).
Line 112: [Warning] Invalid file link:(~/Topic/Purging and Archiving Tracking Data.md).

biztalk/technical-guides/checklist-installing-and-configuring-certificates.md

Line 21: [Warning] Invalid file link:(~/Topic/Best Practices for Managing Certificates2.md).
Line 22: [Warning] Invalid file link:(~/Topic/How to Install Certificates for BizTalk Server.md).
Line 23: [Warning] Invalid file link:(~/Topic/Best Practices for Managing Certificates2.md).
Line 23: [Warning] Invalid file link:(~/Topic/How to Install Certificates for BizTalk Server.md).
Line 24: [Warning] Invalid file link:(~/Topic/Best Practices for Managing Certificates2.md).
Line 25: [Warning] Invalid file link:(~/Topic/Configuring Certificates with Adapters.md).
Line 25: [Warning] Invalid file link:(~/Topic/Best Practices for Managing Certificates2.md).
Line 26: [Warning] Invalid file link:(~/Topic/How to Configure Certificates for Party Resolution.md).
Line 27: [Warning] Invalid file link:(~/Topic/How to Export an Application to an .msi File.md).
Line 27: [Warning] Invalid file link:(~/Topic/How to Import an Application from an .msi File.md).
Line 27: [Warning] Invalid file link:(~/Topic/How to Configure Certificates for Party Resolution.md).
Line 27: [Warning] Invalid file link:(~/Topic/Best Practices for Managing Certificates2.md).
Line 30: [Warning] Invalid file link:(~/Topic/Best Practices for Managing Certificates2.md).
Line 31: [Warning] Invalid file link:(~/Topic/Known Issues with Certificates in BizTalk Server.md).

biztalk/technical-guides/checklist-maintaining-and-troubleshooting-biztalk-server-databases.md

Line 33: [Warning] Invalid file link:(~/Topic/Configuring a Dedicated Tracking Host.md).
Line 37: [Warning] Invalid file link:(~/Topic/Best Practices for Maintaining BizTalk Server Databases.md).
Line 46: [Warning] Invalid file link:(~/Topic/Large-growing BizTalk Server Database Tables.md).
Line 56: [Warning] Invalid file link:(~/Topic/Best Practices for Maintaining BizTalk Server Databases.md).
Line 58: [Warning] Invalid file link:(~/Topic/Large-growing BizTalk Server Database Tables.md).
Line 63: [Warning] Invalid file link:(~/Topic/SQL Server Settings That Should Not Be Changed.md).

biztalk/technical-guides/checklist-optimizing-performance-on-hyper-v.md

Line 32: [Warning] Invalid file link:(~/Topic/Test Scenario Overview.md).
Line 32: [Warning] Invalid file link:(~/Topic/Testing BizTalk Server Virtualization Performance.md).
Line 44: [Warning] Invalid file link:(~/technical-guides/media/90f98f0d-a223-404c-b419-81369dc92970.gif).
Line 85: [Warning] Invalid file link:(~/Topic/Network Optimizations.md).
Line 86: [Warning] Invalid file link:(~/Topic/Network Optimizations.md).
Line 93: [Warning] Invalid file link:(~/Topic/Network Optimizations.md).
Line 96: [Warning] Invalid file link:(~/Topic/SQL Server Optimizations.md).
Line 99: [Warning] Invalid file link:(~/Topic/BizTalk Server Optimizations.md).

biztalk/technical-guides/checklist-planning-for-operations-in-a-secure-environment.md

Line 135: [Warning] Invalid file link:(~/Topic/Checklists for Other Important Tasks.md).

biztalk/technical-guides/configuring-certificates-for-mime-or-smime-messages.md

Line 34: [Warning] Invalid file link:(~/Topic/How to Configure BizTalk Server to Send Encrypted MIME or SMIME Messages.md).

biztalk/technical-guides/installing-and-configuring-digital-certificates.md

Line 21: [Warning] Invalid file link:(~/Topic/How to Install Certificates for BizTalk Server.md).
Line 25: [Warning] Invalid file link:(~/Topic/Configuring Certificates with Adapters.md).
Line 27: [Warning] Invalid file link:(~/Topic/How to Configure Certificates for Party Resolution.md).
Line 29: [Warning] Invalid file link:(~/Topic/How to Add Certificates to an Application.md).

biztalk/technical-guides/system-level-bottlenecks.md

Line 130: [Warning] Invalid file link:(~/Topic/Optimizing Operating System Performance.md).
Line 207: [Warning] Invalid file link:(~/Topic/Optimizing Operating System Performance.md).
Line 224: [Warning] Invalid file link:(~/Topic/Optimizing Operating System Performance.md).
Line 226: [Warning] Invalid file link:(~/Topic/Optimizing Operating System Performance.md).
Line 231: [Warning] Invalid file link:(~/Topic/Optimizing Operating System Performance.md).
Line 237: [Warning] Invalid file link:(~/Topic/Optimizing Filegroups for the Databases2.md).
Line 243: [Warning] Invalid file link:(~/Topic/Optimizing Database Performance.md).
Line 398: [Warning] Invalid file link:(~/Topic/Optimizing Operating System Performance.md).
Line 400: [Warning] Invalid file link:(~/Topic/Optimizing Operating System Performance.md).
Line 402: [Warning] Invalid file link:(~/Topic/Optimizing Operating System Performance.md).
Line 447: [Warning] Invalid file link:(~/Topic/Optimizing Network Performance.md).
Line 449: [Warning] Invalid file link:(~/Topic/Optimizing Network Performance.md).
Line 452: [Warning] Invalid file link:(~/Topic/Finding and Eliminating Bottlenecks.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/accelerator-swift/creating-and-deploying-a4swift-pipelines.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/adapter-oracle-database/step-2-configure-an-orchestration-to-use-the-oracle-db-adapter-in-biztalk.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/adapter-oracle-ebs/security-with-the-oracle-e-business-suite-adapter-and-biztalk-server.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/adapter-sap/step-2-configure-the-orchestration-in-biztalk-server-administration-console1.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/adapter-siebel/step-2-configure-the-orchestration-to-use-the-siebel-adapter-in-biztalk-server.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/adapter-sql/step-1-generate-schema-for-operations.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/adapter-sql/step-2-configure-the-orchestration-to-use-the-sql-adapter-in-biztalk-server.md
:warning:Warning
View
Details

biztalk/core/biztalk-server-core-documentation.md
:warning:Warning
View
Details

biztalk/core/configure-wcf-services-published-with-the-biztalk-wcf-service-publishing-wizard.md
:warning:Warning
View
Details

biztalk/core/how-to-configure-biztalk-server-for-party-resolution.md
:warning:Warning
View
Details

biztalk/core/multiserver-deployment.md
:warning:Warning
View
Details

biztalk/core/progress-dimension.md
:warning:Warning
View
Details

biztalk/core/step-1-prepare-for-the-as2-tutorial.md
:warning:Warning
View
Details

biztalk/core/step-1-prepare-for-the-edi-interface-developer-tutorial.md
:warning:Warning
View
Details

biztalk/core/step-2-create-and-deploy-the-sample-x12-schema.md
:warning:Warning
View
Details

biztalk/core/step-2-update-and-deploy-the-tutorial-solution.md
:warning:Warning
View
Details

biztalk/core/step-5-configure-a-receive-port-and-receive-location.md
:warning:Warning
View
Details

biztalk/core/walkthrough-as2-receiving-edi-over-as2-with-a-synchronous-mdn.md
:warning:Warning
View
Details

biztalk/core/walkthrough-as2-receiving-edi-over-as2-with-an-asynchronous-mdn.md
:warning:Warning
View
Details

biztalk/core/walkthrough-as2-sending-a-non-edi-message-over-as2.md
:warning:Warning
View
Details

biztalk/core/walkthrough-as2-sending-edi-over-as2-with-a-synchronous-mdn.md
:warning:Warning
View
Details

biztalk/core/walkthrough-as2-sending-edi-over-as2-with-an-asynchronous-mdn.md
:warning:Warning
View
Details

biztalk/core/walkthrough-edifact--receive-edi-interchanges-and-send-an-acknowledgement.md
:warning:Warning
View
Details

biztalk/core/walkthrough-x12--receive-edi-interchanges-and-send-back-an-acknowledgement.md
:warning:Warning
View
Details

biztalk/core/walkthrough-x12-receiving-batched-edi-interchanges.md
:warning:Warning
View
Details

biztalk/core/walkthrough-x12-sending-batched-edi-interchanges.md
:warning:Warning
View
Details

biztalk/core/walkthrough-x12-sending-edi-interchanges.md
:warning:Warning
View
Details

biztalk/install-and-config-guides/prepare-your-computer-for-installation.md
:warning:Warning
View
Details

biztalk/technical-guides/checklist-measuring-performance-on-hyper-v.md
:warning:Warning
View
Details

biztalk/technical-guides/checklist-optimizing-performance-on-hyper-v.md
:warning:Warning
View
Details

biztalk/technical-guides/test-results-sql-server-key-performance-indicators.md
:warning:Warning
View
Details

biztalk/TOC.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/mllpreceive-tool.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/mllpsend-tool.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/step-18-test-your-new-message-enrichment-solution.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/lesson-8-building-and-deploying-the-assembly.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/step-1-installing-the-base-platform.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/develop-biztalk-applications-using-the-oracle-database-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/tutorial-migrate-biztalk-projects-to-the-oracle-database-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/features-for-oracle-ebs-adapter-clients.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/oracle-e-business-suite-adapter-faqs.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/operations-on-trfcs-in-sap.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-2-migrating-an-sap-rfc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-3-migrating-an-sap-send-idoc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-4-migrating-an-sap-receive-idoc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/get-started-with-the-biztalk-adapter-for-siebel-ebusiness-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/limitations-of-biztalk-adapter-for-siebel-ebusiness-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/tutorial-2-migrating-biztalk-projects-in-siebel.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/tutorial-1-migrate-biztalk-projects-to-the-sql-adapter.md
:white_check_mark:Succeeded
View

biztalk/core/as2-support-in-biztalk-server.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

biztalk/adapters-and-accelerators/accelerator-swift/creating-and-deploying-a4swift-pipelines.md

Line 25: [Warning] Invalid file link:(~/adapters-and-accelerators/accelerator-swift/media/a4swift-pipeline-configuration.gif).

biztalk/adapters-and-accelerators/adapter-oracle-database/step-2-configure-an-orchestration-to-use-the-oracle-db-adapter-in-biztalk.md

Line 18: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-oracle-database/media/step-2of3.gif).
Line 48: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-oracle-database/media/a5e49da1-fe34-46fe-80ca-9316d217171a.gif).
Line 52: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-oracle-database/media/697b23d8-4231-4718-8a52-8013fac35e3e.gif).

biztalk/adapters-and-accelerators/adapter-oracle-ebs/security-with-the-oracle-e-business-suite-adapter-and-biztalk-server.md

Line 73: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-oracle-ebs/Security and Protection10.md).

biztalk/adapters-and-accelerators/adapter-sap/step-2-configure-the-orchestration-in-biztalk-server-administration-console1.md

Line 22: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-oracle-database/media/step-2of3.gif).
Line 52: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-sap/media/10129a7d-211b-464b-b05a-b3ea72f46873.gif).
Line 56: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-sap/media/4ffcb4cd-4f53-4b67-92e2-3225d15d97ee.gif).

biztalk/adapters-and-accelerators/adapter-siebel/step-2-configure-the-orchestration-to-use-the-siebel-adapter-in-biztalk-server.md

Line 18: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-oracle-database/media/step-2of3.gif).
Line 48: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-siebel/media/e1ceee98-9f10-40f1-a611-88d3a2c102a9.gif).
Line 52: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-siebel/media/8f8efeaa-d5cd-4ed3-b2f3-a600c48c3bb9.gif).

biztalk/adapters-and-accelerators/adapter-sql/step-1-generate-schema-for-operations.md

Line 18: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-sql/media/step-1of2.gif).

biztalk/adapters-and-accelerators/adapter-sql/step-2-configure-the-orchestration-to-use-the-sql-adapter-in-biztalk-server.md

Line 18: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-oracle-database/media/step-2of3.gif).
Line 45: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-sql/media/21e5a23c-7319-4324-8f09-52118ebeeea9.gif).
Line 49: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-sql/media/5b54e09b-8784-4df6-a279-e8aed813114e.gif).

biztalk/core/biztalk-server-core-documentation.md

Line 24: [Warning] The content part of NOTE/WARNING/CAUTION/IMPORTANT/NEXT syntax is suggested to start in a new line.

biztalk/core/configure-wcf-services-published-with-the-biztalk-wcf-service-publishing-wizard.md

Line 37: [Warning] Invalid file link:(~/core/media/959900fd-44c9-4f3a-8836-9786a2f5e707.gif).
Line 47: [Warning] Invalid file link:(~/core/media/585ecdad-bdee-40c0-b2f1-7ace74d503e5.gif).
Line 57: [Warning] Invalid file link:(~/core/media/1126fa6a-e3e9-44ad-aeb0-90c78226aeeb.gif).

biztalk/core/how-to-configure-biztalk-server-for-party-resolution.md

Line 36: [Warning] Invalid file link:(~/core/media/bpi-sp-msgsec-certmgmt-certstores-receive.gif).
Line 65: [Warning] Invalid file link:(~/core/media/bts-dev-mimesmimedecoder.gif).

biztalk/core/multiserver-deployment.md

Line 103: [Warning] Invalid file link:(~/core/media/adapters-wss-multiserver-screenshot01.gif).

biztalk/core/progress-dimension.md

Line 25: [Warning] Invalid file link:(~/core/media/bts-view-with-approved-denieds.gif).
Line 38: [Warning] Invalid file link:(~/core/media/bts-progress-dimension-two-levelss.gif).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/adapter-oracle-ebs/security-with-the-oracle-e-business-suite-adapter-and-biztalk-server.md
:warning:Warning
View
Details

biztalk/core/biztalk-server-core-documentation.md
:warning:Warning
View
Details

biztalk/install-and-config-guides/prepare-your-computer-for-installation.md
:warning:Warning
View
Details

biztalk/TOC.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/mllpreceive-tool.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/mllpsend-tool.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/step-18-test-your-new-message-enrichment-solution.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/creating-and-deploying-a4swift-pipelines.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/lesson-8-building-and-deploying-the-assembly.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/step-1-installing-the-base-platform.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/develop-biztalk-applications-using-the-oracle-database-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/step-2-configure-an-orchestration-to-use-the-oracle-db-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/tutorial-migrate-biztalk-projects-to-the-oracle-database-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/features-for-oracle-ebs-adapter-clients.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/oracle-e-business-suite-adapter-faqs.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/operations-on-trfcs-in-sap.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/step-2-configure-the-orchestration-in-biztalk-server-administration-console1.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-2-migrating-an-sap-rfc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-3-migrating-an-sap-send-idoc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-4-migrating-an-sap-receive-idoc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/get-started-with-the-biztalk-adapter-for-siebel-ebusiness-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/limitations-of-biztalk-adapter-for-siebel-ebusiness-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/step-2-configure-the-orchestration-to-use-the-siebel-adapter-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/tutorial-2-migrating-biztalk-projects-in-siebel.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/step-1-generate-schema-for-operations.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/step-2-configure-the-orchestration-to-use-the-sql-adapter-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/tutorial-1-migrate-biztalk-projects-to-the-sql-adapter.md
:white_check_mark:Succeeded
View

biztalk/core/as2-support-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/core/bam-tasks-for-administrators.md
:white_check_mark:Succeeded
View

biztalk/core/before-you-begin-the-tutorial.md
:white_check_mark:Succeeded
View

biztalk/core/before-you-use-the-tpe.md
:white_check_mark:Succeeded
View

biztalk/core/checklist-backup-and-restore.md
:white_check_mark:Succeeded
View

biztalk/core/checklist-undeploy-a-biztalk-application.md
:white_check_mark:Succeeded
View

biztalk/core/common-component-developer-tasks.md
:white_check_mark:Succeeded
View

biztalk/core/common-solution-developer-tasks.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-business-activity-monitoring-portal-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-business-rules-engine-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-configuration-complete-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-consolidated-databases-view-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-consolidated-service-accounts-view-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-customer-feedback-options-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-enterprise-single-sign-on-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-microsoft-update-options-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-overview-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-progress-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-service-accounts-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-start-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-summary-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-unconfigure-features-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-windows-sharepoint-services-page.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

biztalk/adapters-and-accelerators/adapter-oracle-ebs/security-with-the-oracle-e-business-suite-adapter-and-biztalk-server.md

Line 73: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-oracle-ebs/Security and Protection10.md).

biztalk/core/biztalk-server-core-documentation.md

Line 24: [Warning] The content part of NOTE/WARNING/CAUTION/IMPORTANT/NEXT syntax is suggested to start in a new line.

biztalk/install-and-config-guides/prepare-your-computer-for-installation.md

Line 19: [Warning] The content part of NOTE/WARNING/CAUTION/IMPORTANT/NEXT syntax is suggested to start in a new line.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/adapter-oracle-ebs/security-with-the-oracle-e-business-suite-adapter-and-biztalk-server.md
:warning:Warning
View
Details

biztalk/install-and-config-guides/prepare-your-computer-for-installation.md
:warning:Warning
View
Details

biztalk/TOC.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/mllpreceive-tool.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/mllpsend-tool.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/step-18-test-your-new-message-enrichment-solution.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/creating-and-deploying-a4swift-pipelines.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/lesson-8-building-and-deploying-the-assembly.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/step-1-installing-the-base-platform.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/develop-biztalk-applications-using-the-oracle-database-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/step-2-configure-an-orchestration-to-use-the-oracle-db-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/tutorial-migrate-biztalk-projects-to-the-oracle-database-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/features-for-oracle-ebs-adapter-clients.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/oracle-e-business-suite-adapter-faqs.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/operations-on-trfcs-in-sap.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/step-2-configure-the-orchestration-in-biztalk-server-administration-console1.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-2-migrating-an-sap-rfc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-3-migrating-an-sap-send-idoc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-4-migrating-an-sap-receive-idoc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/get-started-with-the-biztalk-adapter-for-siebel-ebusiness-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/limitations-of-biztalk-adapter-for-siebel-ebusiness-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/step-2-configure-the-orchestration-to-use-the-siebel-adapter-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/tutorial-2-migrating-biztalk-projects-in-siebel.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/step-1-generate-schema-for-operations.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/step-2-configure-the-orchestration-to-use-the-sql-adapter-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/tutorial-1-migrate-biztalk-projects-to-the-sql-adapter.md
:white_check_mark:Succeeded
View

biztalk/core/as2-support-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/core/bam-tasks-for-administrators.md
:white_check_mark:Succeeded
View

biztalk/core/before-you-begin-the-tutorial.md
:white_check_mark:Succeeded
View

biztalk/core/before-you-use-the-tpe.md
:white_check_mark:Succeeded
View

biztalk/core/biztalk-server-core-documentation.md
:white_check_mark:Succeeded
View

biztalk/core/checklist-backup-and-restore.md
:white_check_mark:Succeeded
View

biztalk/core/checklist-undeploy-a-biztalk-application.md
:white_check_mark:Succeeded
View

biztalk/core/common-component-developer-tasks.md
:white_check_mark:Succeeded
View

biztalk/core/common-solution-developer-tasks.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-business-activity-monitoring-portal-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-business-rules-engine-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-configuration-complete-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-consolidated-databases-view-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-consolidated-service-accounts-view-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-customer-feedback-options-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-enterprise-single-sign-on-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-microsoft-update-options-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-overview-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-progress-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-service-accounts-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-start-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-summary-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-unconfigure-features-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-windows-sharepoint-services-page.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

biztalk/adapters-and-accelerators/adapter-oracle-ebs/security-with-the-oracle-e-business-suite-adapter-and-biztalk-server.md

Line 73: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-oracle-ebs/Security and Protection10.md).

biztalk/install-and-config-guides/prepare-your-computer-for-installation.md

Line 19: [Warning] The content part of NOTE/WARNING/CAUTION/IMPORTANT/NEXT syntax is suggested to start in a new line.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/adapter-oracle-ebs/security-with-the-oracle-e-business-suite-adapter-and-biztalk-server.md
:warning:Warning
View
Details

biztalk/TOC.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/mllpreceive-tool.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/mllpsend-tool.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/step-18-test-your-new-message-enrichment-solution.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/creating-and-deploying-a4swift-pipelines.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/lesson-8-building-and-deploying-the-assembly.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/step-1-installing-the-base-platform.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/develop-biztalk-applications-using-the-oracle-database-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/step-2-configure-an-orchestration-to-use-the-oracle-db-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/tutorial-migrate-biztalk-projects-to-the-oracle-database-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/features-for-oracle-ebs-adapter-clients.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/oracle-e-business-suite-adapter-faqs.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/operations-on-trfcs-in-sap.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/step-2-configure-the-orchestration-in-biztalk-server-administration-console1.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-2-migrating-an-sap-rfc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-3-migrating-an-sap-send-idoc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-4-migrating-an-sap-receive-idoc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/get-started-with-the-biztalk-adapter-for-siebel-ebusiness-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/limitations-of-biztalk-adapter-for-siebel-ebusiness-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/step-2-configure-the-orchestration-to-use-the-siebel-adapter-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/tutorial-2-migrating-biztalk-projects-in-siebel.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/step-1-generate-schema-for-operations.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/step-2-configure-the-orchestration-to-use-the-sql-adapter-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/tutorial-1-migrate-biztalk-projects-to-the-sql-adapter.md
:white_check_mark:Succeeded
View

biztalk/core/as2-support-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/core/bam-tasks-for-administrators.md
:white_check_mark:Succeeded
View

biztalk/core/before-you-begin-the-tutorial.md
:white_check_mark:Succeeded
View

biztalk/core/before-you-use-the-tpe.md
:white_check_mark:Succeeded
View

biztalk/core/biztalk-server-core-documentation.md
:white_check_mark:Succeeded
View

biztalk/core/checklist-backup-and-restore.md
:white_check_mark:Succeeded
View

biztalk/core/checklist-undeploy-a-biztalk-application.md
:white_check_mark:Succeeded
View

biztalk/core/common-component-developer-tasks.md
:white_check_mark:Succeeded
View

biztalk/core/common-solution-developer-tasks.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-business-activity-monitoring-portal-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-business-rules-engine-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-configuration-complete-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-consolidated-databases-view-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-consolidated-service-accounts-view-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-customer-feedback-options-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-enterprise-single-sign-on-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-microsoft-update-options-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-overview-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-progress-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-service-accounts-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-start-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-summary-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-unconfigure-features-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-windows-sharepoint-services-page.md
:white_check_mark:Succeeded
View

biztalk/core/configure-wcf-services-published-with-the-biztalk-wcf-service-publishing-wizard.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

biztalk/adapters-and-accelerators/adapter-oracle-ebs/security-with-the-oracle-e-business-suite-adapter-and-biztalk-server.md

Line 73: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-oracle-ebs/Security and Protection10.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/adapter-oracle-ebs/security-with-the-oracle-e-business-suite-adapter-and-biztalk-server.md
:warning:Warning
View
Details

biztalk/TOC.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/mllpreceive-tool.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/mllpsend-tool.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/step-18-test-your-new-message-enrichment-solution.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/creating-and-deploying-a4swift-pipelines.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/lesson-8-building-and-deploying-the-assembly.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/step-1-installing-the-base-platform.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/develop-biztalk-applications-using-the-oracle-database-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/step-2-configure-an-orchestration-to-use-the-oracle-db-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/tutorial-migrate-biztalk-projects-to-the-oracle-database-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/features-for-oracle-ebs-adapter-clients.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/oracle-e-business-suite-adapter-faqs.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/operations-on-trfcs-in-sap.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/step-2-configure-the-orchestration-in-biztalk-server-administration-console1.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-2-migrating-an-sap-rfc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-3-migrating-an-sap-send-idoc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/tutorial-4-migrating-an-sap-receive-idoc-biztalk-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/get-started-with-the-biztalk-adapter-for-siebel-ebusiness-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/limitations-of-biztalk-adapter-for-siebel-ebusiness-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/step-2-configure-the-orchestration-to-use-the-siebel-adapter-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/tutorial-2-migrating-biztalk-projects-in-siebel.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/step-1-generate-schema-for-operations.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/step-2-configure-the-orchestration-to-use-the-sql-adapter-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/tutorial-1-migrate-biztalk-projects-to-the-sql-adapter.md
:white_check_mark:Succeeded
View

biztalk/core/as2-support-in-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/core/bam-tasks-for-administrators.md
:white_check_mark:Succeeded
View

biztalk/core/before-you-begin-the-tutorial.md
:white_check_mark:Succeeded
View

biztalk/core/before-you-use-the-tpe.md
:white_check_mark:Succeeded
View

biztalk/core/biztalk-server-core-documentation.md
:white_check_mark:Succeeded
View

biztalk/core/checklist-backup-and-restore.md
:white_check_mark:Succeeded
View

biztalk/core/checklist-undeploy-a-biztalk-application.md
:white_check_mark:Succeeded
View

biztalk/core/common-component-developer-tasks.md
:white_check_mark:Succeeded
View

biztalk/core/common-solution-developer-tasks.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-business-activity-monitoring-portal-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-business-rules-engine-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-configuration-complete-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-consolidated-databases-view-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-consolidated-service-accounts-view-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-customer-feedback-options-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-enterprise-single-sign-on-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-microsoft-update-options-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-overview-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-progress-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-service-accounts-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-start-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-summary-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-unconfigure-features-page.md
:white_check_mark:Succeeded
View

biztalk/core/configuration-wizard-windows-sharepoint-services-page.md
:white_check_mark:Succeeded
View

biztalk/core/configure-wcf-services-published-with-the-biztalk-wcf-service-publishing-wizard.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

biztalk/adapters-and-accelerators/adapter-oracle-ebs/security-with-the-oracle-e-business-suite-adapter-and-biztalk-server.md

Line 73: [Warning] Invalid file link:(~/adapters-and-accelerators/secure-your-oracle-ebs-applications.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

#sign-off


⬆ 3.6.0

Comparison to 3.5.0: https://github.com/ignitionrobotics/ign-gazebo/compare/ignition-gazebo3_3.5.0...ign-gazebo3
It looks like all PRs currently targeted at ign-gazebo3 are still being iterated on.

The homebrew and Windows CI failures are expected.


Fix incorrect exception

Summary
Minor change in documentation.
Incorrect Exception type is fixed.
Fixes #27308

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


Unable to turn off auto update

macOS version: 12.2.1
Kap version: 3.5.4
Steps to reproduce
Download and install the previous version from GitHub releases. The app will auto-update to the latest version after restarting the machine.
Current behaviour
Auto-update after restarting the machine.
Expected behaviour
A switch in preferences to turn off auto-off.
Workaround
Currently no workaround.
Notes
The reason why I'd like to use an old version is that the latest version loads extremely slow on my machine. Version 3.2.2 works fast on my machine.

There another reason for avoiding auto updates: On my work machine, I need to "request privileges" every time I update something. So now I need to either dismiss Kap or request privileges and enter my password all the time, which is unfortunate.

That's really valuable information @gregoralbrecht, thank you. I seems like this feature is wanted by quite a few people. If anyone wants to take a look at implementing it, we'd be really grateful.
Currently, I only have bandwidth to try and update Kap's dependencies (sounds a lot easier than it is) so I won't have time to work on this feature for a while, myself.

I wonder if renaming/removing /Applications/Kap.app/Contents/Resources/app-update.yml could be a workaround?


Omnibear incorrectly reports page liked successfully

> {
>
>  Warning : in_array() expects parameter 2 to be array, null given in /var/www/html/wp-content/plugins/micropub/micropub.php on line 265
>
> Warning : in_array() expects parameter 2 to be array, null given in /var/www/html/wp-content/plugins/micropub/micropub.php on line 268
>
> Warning : Cannot modify header information – headers already sent by (output started at /var/www/html/wp-content/plugins/micropub/micropub.php:265) in /var/www/html/wp-content/plugins/micropub/micropub.php on line 1225
>  {“error”:”insufficient_scope”,”error_description”:”scope insufficient to create posts”}:
>  }
(Originally published at: https://crw.moe/b/U0)

> {
>
>  Warning : in_array() expects parameter 2 to be array, null given in /var/www/html/wp-content/plugins/micropub/micropub.php on line 265
>
> Warning : in_array() expects parameter 2 to be array, null given in /var/www/html/wp-content/plugins/micropub/micropub.php on line 268
>
> Warning : Cannot modify header information – headers already sent by (output started at /var/www/html/wp-content/plugins/micropub/micropub.php:265) in /var/www/html/wp-content/plugins/micropub/micropub.php on line 1225
>  {“error”:”insufficient_scope”,”error_description”:”scope insufficient to create posts”}:
>  }
(Originally published at: https://crw.moe/b/U0)

I believe we finally have a workaround for this, which I will get added into the next version. The core issue is in the wordpress plugin and is being addressed seperately (https://github.com/snarfed/wordpress-micropub/issues/133)

Closing as duplicate of #20


Fix alt attribute missing from image

Previous to this code fix adding a href attribute to mj-image would render the alt tag.
Now adding alt to mj-image will render the alt tag as expected.
Fixes: https://github.com/mjmlio/mjml/issues/1048

Ew how did we miss :( that thanks a lot for the fix @garmeeh !