text:
REmove PostCSS Loader warning Previous source map found, but options.sourceMap isn't set.

Avoid warning:
✗ npm run dev

> @ dev /home/sergi/Code/provaesborrar12
> npm run development

> @ development /home/sergi/Code/provaesborrar12
> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

 95% emitting

 WARNING  Compiled with 1 warnings                                                                                11:52:21

 warning  in ./resources/assets/sass/app.scss

(Emitted value instead of an instance of Error)

 ⚠  PostCSS Loader

Previous source map found, but options.sourceMap isn't set.
In this case the loader will discard the source map entirely for performance reasons.
See https://github.com/postcss/postcss-loader#sourcemap for more information.

 @ ./resources/assets/sass/app.scss 4:14-266
 @ multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./node_modules/bootstrap-less/bootstrap/bootstrap.less ./resources/assets/less/adminlte-app.less ./node_modules/toastr/toastr.less

Notice: The /home/sergi/Code/provaesborrar12/node_modules/admin-lte/bootstrap/fonts/*.* search produced no matches.
                                                                                Asset     Size  Chunks                    Chunk Names

Done

@acacha How did you resolve the error?

source: gharchive/issue

authors: Braunson acacha

license: mit

license_type: permissive

license_source: bigquery


text:
As a user I would like to be able to collapse the lefthand menu so that there is more screen  area to work with.

The functionality for this already exists when the screen size gets small enough. We just need to make it so that the menu button shows up at all times instead of just when the window gets small.

How does the sponsor  want the UI to toggle the menu ? if via a button, where should I place that button ?

if you shrink the application window the button will eventually appear on the left hand side. I want to duplicate exactly how it is done.

repo: acasi-ctf/ctf

license_source: github-api


text:
Avoid instanceof which leads to runtime errors with deep npm dependencies

The use of instanceof to check whether an object is of a class leads to unreliable check when importing Composer Concerto in projects with deep npm dependencies.
Context
Composer Concerto uses instanceof checks e.g., here https://github.com/hyperledger/composer-concerto/blob/37189e52c4f52d13cbd862b38d36a64022976398/lib/serializer/resourcevalidator.js#L72 or here https://github.com/hyperledger/composer-concerto/blob/37189e52c4f52d13cbd862b38d36a64022976398/lib/serializer/jsonpopulator.js#L96
Those can be unreliable since it checks whether this is the same object from the exact same package installed in a node.js project.
The reason it is unreliable is that it is difficult to enforce that the corresponding version of composer-concerto is installed exactly once in the ./node_modules directory through npm install.
This can lead to runtime errors when doing validation/serialization in some projects with deep npm dependencies.
Expected Behavior
A project should be able to import Composer Concerto 0.7.1 and PROJECT 0.X.X depending on e.g., Composer Concerto 0.7.0 without leading to runtime errors.
Actual Behavior
Currently a project has to ensure every dependency which import Composer Concerto have the exact same version, and that npm install leads to only one copy of that same version, which is difficult to guarantee (due to the way npm install works).
Possible Fix
Several fixes are suggested in: https://stackoverflow.com/questions/41587865/using-instanceof-on-objects-created-with-constructors-from-deep-npm-dependenci
The recommended fix is to use an explicit method to check whether an object has the expected class. So instead of writing thing instanceof RelationshipDeclaration one would write isRelationshipDeclaration(thing) where:
RelationshipDeclaration.prototype._isRelationshipDeclaration = true;
var isRelationshipDeclaration = function isRelationshipDeclaration(obj) {
  return obj instanceof RelationshipDeclaration || Boolean(obj._isRelationshipDeclaration);
};

module.exports = {
  RelationshipDeclaration,
  isRelationshipDeclaration
};

Steps to Reproduce

Existing issues

[x] Stack Overflow issues
[x] GitHub Issues
[ ] Rocket Chat history

Context
Importing Composer Concerto in various parts of the Accord Project (Ergo, Cicero, Cicero template library, template studio, etc.).
Your Environment

Version used: 0.70.*
Environment name and version (e.g. Chrome 39, node.js 5.4): node.js 8
Operating System and version (desktop or mobile): MacOS
Link to your project:

There still seems to be a few occurrences of instance of around: ```
bash-3.2$ grep -r instanceof lib
lib/serializer/typedstack.js:        if(expectedType && !(obj instanceof expectedType)) {
lib/serializer/typedstack.js:        if(expectedType && !(result instanceof expectedType)) {
lib/serializer/jsonpopulator.js:        if (thing instanceof ClassDeclaration) {
lib/serializer/jsonpopulator.js:        } else if (thing instanceof RelationshipDeclaration) {
lib/serializer/jsonpopulator.js:        } else if (thing instanceof Field) {
lib/serializer/instancegenerator.js:        if (thing instanceof ClassDeclaration) {
lib/serializer/instancegenerator.js:        } else if (thing instanceof RelationshipDeclaration) {
lib/serializer/instancegenerator.js:        } else if (thing instanceof Field) {
lib/serializer/instancegenerator.js:        if (classDeclaration instanceof EnumDeclaration) {
lib/serializer/resourcevalidator.js:        if (thing instanceof EnumDeclaration) {
lib/serializer/resourcevalidator.js:        } else if (thing instanceof ClassDeclaration) {
lib/serializer/resourcevalidator.js:        } else if (thing instanceof RelationshipDeclaration) {
lib/serializer/resourcevalidator.js:        } else if (thing instanceof Field) {
lib/serializer/resourcevalidator.js:        if(!((obj instanceof Resource) || (obj instanceof Concept))) {
lib/serializer/resourcevalidator.js:        if(obj instanceof Identifiable) {
lib/serializer/resourcevalidator.js:                    if(obj instanceof Identifiable) {
lib/serializer/resourcevalidator.js:        if(obj instanceof Identifiable) {
lib/serializer/resourcevalidator.js:        if(field.isArray() && !(obj instanceof Array)) {
lib/serializer/resourcevalidator.js:        if(!(obj instanceof Array)) {
lib/serializer/resourcevalidator.js:            if(obj instanceof Identifiable) {
lib/serializer/resourcevalidator.js:            if(!(obj instanceof Array)) {
lib/serializer/resourcevalidator.js:        if(obj instanceof Relationship) {
lib/serializer/resourcevalidator.js:        } else if (obj instanceof Resource && (this.options.convertResourcesToRelationships || this.options.permitResourcesForRelationships)) {
lib/serializer/resourcevalidator.js:        if(value instanceof Identifiable) {
lib/serializer/jsongenerator.js:        if (thing instanceof ClassDeclaration) {
lib/serializer/jsongenerator.js:        } else if (thing instanceof RelationshipDeclaration) {
lib/serializer/jsongenerator.js:        } else if (thing instanceof Field) {
lib/serializer/jsongenerator.js:        if (!((obj instanceof Resource) || (obj instanceof Concept))) {
lib/serializer/jsongenerator.js:        if (obj instanceof Identifiable && this.deduplicateResources) {
lib/serializer/jsongenerator.js:                if (this.permitResourcesForRelationships && item instanceof Resource) {
lib/serializer/jsongenerator.js:        } else if (this.permitResourcesForRelationships && obj instanceof Resource) {
lib/serializer/jsongenerator.js:        if (relationshipOrResource instanceof Resource) {
lib/factory.js:        if (!(classDeclaration instanceof TransactionDeclaration)) {
lib/factory.js:        if (!(classDeclaration instanceof EventDeclaration)) {
lib/introspect/parser.pegjs:InstanceofToken = "instanceof" !IdentifierPart
lib/introspect/modelfile.js:        if(classDeclaration instanceof AssetDeclaration) {
lib/introspect/modelfile.js:        if(classDeclaration instanceof TransactionDeclaration) {
lib/introspect/modelfile.js:        if(classDeclaration instanceof EventDeclaration) {
lib/introspect/modelfile.js:        if(classDeclaration instanceof ParticipantDeclaration) {
lib/introspect/modelfile.js:            if(classDeclaration instanceof type && (includeSystemType || !classDeclaration.isSystemType())) {
lib/introspect/parser.js:            escapedParts += expectation.parts[i] instanceof Array
lib/introspect/parser.js:      peg$c182 = "instanceof",
lib/introspect/parser.js:      peg$c183 = peg$literalExpectation("instanceof", false),
lib/model/typed.js:            if (field instanceof Field) {
lib/serializer.js:        if(!(resource instanceof Typed)) {
lib/serializer.js:        if (classDeclaration instanceof TransactionDeclaration) {
lib/serializer.js:        } else if (classDeclaration instanceof EventDeclaration) {
lib/serializer.js:        } else if (classDeclaration instanceof ConceptDeclaration) {
lib/serializer.js:        } else if (classDeclaration instanceof EnumDeclaration) {

Confirming that this works. The approach is to override hasInstance in the corresponding classes, which effectively underlies the implementation for instanceof.

Reopening based on further investigation and how it interacts with Babel:
https://github.com/accordproject/web-components/issues/110

authors: dselman jeromesimeon

repo: accordproject/concerto


text:
chore: Migrate build tool

Migrate from webpack to rollup for bundling. Rollup is more appropriate for a library such as this, whereas webpack is better suited to web apps. This also aligns this repo with @accordproject/web-compoennts
Changes

The browser bundle has moved from umd/concerto.js to dist/concerto.min.js.
Tuning .npmignore.

Migrate from webpack to rollup for bundling. Rollup is more appropriate for a library such as this, whereas webpack is better suited to web apps. This also aligns this repo with @accordproject/web-compoennts
Changes

The browser bundle has moved from umd/concerto.js to dist/concerto.min.js.
Tuning .npmignore.

This looks nice, but also slightly disconcerting. A bit curious about:

tradeoffs between webpack and rollup: why is rollup better for this kind of library? also based on the description, shouldn't web-components use webpack?
why do we care at all, wouldn't web components end up bundling concerto anyway?
why now? what problem are we trying to solve?

tradeoffs between webpack and rollup: why is rollup better for this kind of library? also based on the description, shouldn't web-components use webpack?

There are lots of comparisons out there, e.g. https://betterprogramming.pub/the-battle-of-bundlers-6333a4e3eda9
web-components is a library for building web apps, but is not a web app itself.

why do we care at all, wouldn't web components end up bundling concerto anyway?

By bundling and performing optimisations such as tree-shaking and minimisation, all dependencies of concerto benefit from reduced package sizes. Optimising here also gives us greater control than relying than on upstream dependants. Our npmjs listing today, says that our package size is >1MB which is misleading at best (the compressed version of the UMD bundle is ~80kB), and suggests many other poor things at worst. As the root package in the AP stack, I wanted to start my investigations here because it will give us the biggest ROI.

why now? what problem are we trying to solve?

I originally attempted to solve a different problem, then rolled-back and this PR is what remained.
Currently, in the npm package that is published by this repo, we include two things that are redundant:

The source files in the lib/ folder
A UMD bundle of the source files in the umd/ folder.
You can run npm pack @accordproject/concerto-core@1.0.0-alpha.7 to view the contents of the published package, or just npm pack to build the package .tgz locally.

UMD is compatible with Node JS and browsers, but other formats are preferable (ESM for Node, and IIFE for browsers). However, after investigation, I wasn't confident that I had a solution that solved this problem and retained CommonJS for developing / testing locally. I might pick this up again, but I need to move onto other things now.
I was also hoping that a switch to Rollup would give us an improvement in the size of the UMD bundle; it didn't, it's broadly the same.
Another conclusion was that to really benefit from a performance optimisation, changing the bundle format (UMD vs IIFE vs CommonJS vs ESM) makes margin impact because of the dominance of the parser which is more than 90% of the total package size. This is further motivation for https://github.com/accordproject/concerto/issues/55#issuecomment-822360363

tradeoffs between webpack and rollup: why is rollup better for this kind of library? also based on the description, shouldn't web-components use webpack?

There are lots of comparisons out there, e.g. https://betterprogramming.pub/the-battle-of-bundlers-6333a4e3eda9

Another benefit of WebAssembly was staring us in the face all along.

web-components is a library for building web apps, but is not a web app itself.

gotcha.

why do we care at all, wouldn't web components end up bundling concerto anyway?

By bundling and performing optimisations such as tree-shaking and minimisation, all dependencies of concerto benefit from reduced package sizes. Optimising here also gives us greater control than relying than on upstream dependants. Our npmjs listing today, says that our package size is >1MB which is misleading at best (the compressed version of the UMD bundle is ~80kB), and suggests many other poor things at worst. As the root package in the AP stack, I wanted to start my investigations here because it will give us the biggest ROI.

Understood, but clearly this looks like an investigation and if we like it, it feels like we are signing up for applying this to the rest of the AP stack (or feels like we should which is a pretty significant effort).

why now? what problem are we trying to solve?

I originally attempted to solve a different problem, then rolled-back and this PR is what remained.
Currently, in the npm package that is published by this repo, we include two things that are redundant:

The source files in the lib/ folder
A UMD bundle of the source files in the umd/ folder.
You can run npm pack @accordproject/concerto-core@1.0.0-alpha.7 to view the contents of the published package, or just npm pack to build the package .tgz locally.

UMD is compatible with Node JS and browsers, but other formats are preferable (ESM for Node, and IIFE for browsers). However, after investigation, I wasn't confident that I had a solution that solved this problem and retained CommonJS for developing / testing locally. I might pick this up again, but I need to move onto other things now.
I was also hoping that a switch to Rollup would give us an improvement in the size of the UMD bundle; it didn't, it's broadly the same.
Another conclusion was that to really benefit from a performance optimisation, changing the bundle format (UMD vs IIFE vs CommonJS vs ESM) makes margin impact because of the dominance of the parser which is more than 90% of the total package size. This is further motivation for #55 (comment)

Looks nice all around though, I'll approve and let's see how it goes.

source: gharchive/pull-request

authors: jeromesimeon mttrbrts


text:
What about creating vocab entries from reference vocabs?

Wouldn't it be nice to integrate services?
Use case:

Create a well-defined vocabulary of e.g. person-institution relations in https://vocabs.acdh.oeaw.ac.at/
Add the vocabs uri once in APIS admin
Directly use vocab when editing instance relations

should that be a static import or on the fly?

@dasch124 Either way -- I guess on the fly would make more sense from a user perspective even if it would open up possibilities leading to data inconsistency.

repo: acdh-oeaw/apis-core

license: MIT


text:
🛑 AceBlock Swagger UI is down

In 55e69bd, AceBlock Swagger UI ($ACEBLOCK_SWAGGER_UI) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AceBlock Swagger UI is back up in 5d975a5.

repo: aceblockID/monitoring


text:
🛑 AceBlock Swagger UI is down

In 25fa854, AceBlock Swagger UI ($ACEBLOCK_SWAGGER_UI) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AceBlock Swagger UI is back up in c8fd522.


text:
🛑 AceBlock Swagger UI is down

In 6ef7ff1, AceBlock Swagger UI ($ACEBLOCK_SWAGGER_UI) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AceBlock Swagger UI is back up in 4031244.


text:
🛑 AceBlock Swagger UI is down

In 424f700, AceBlock Swagger UI ($ACEBLOCK_SWAGGER_UI) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AceBlock Swagger UI is back up in c7f6573.


text:
🛑 MNID Homepage is down

In f956e89, MNID Homepage ($MNID_HOME) was down:

HTTP code: 401
Response time: 459 ms

Resolved: MNID Homepage is back up in e5d28a6 after 1 hour, 7 minutes.


text:
🛑 MNID Homepage is down

In a72ec50, MNID Homepage ($MNID_HOME) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MNID Homepage is back up in f54f721 after 22 minutes.


text:
可否在README.md中加入ztime模块的指导

ztime模块还是有点懵懵懂懂，求指导，需要给连接的客户端发送生成的token，每30分钟发一次，连接建立时候就要启动这个定时器。

你搞懂了吗，我也想知道这个怎么用的

repo: aceld/zinx


text:
Criação do botão  Swagger Autorization

using Api.Middlewares;
using Microsoft.OpenApi.Models;
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddControllers();
builder.Services.AddEndpointsApiExplorer();
builder.Services.AddSwaggerGen(c =>
{
c.SwaggerDoc("v1", new OpenApiInfo { Title = "My API", Version = "v1" });
c.AddSecurityDefinition("Bearer", new OpenApiSecurityScheme
{
Description = "JWT Authorization header using the Bearer scheme. Example: "Authorization: Bearer { Token}"",
Name = "Authorization",
In = ParameterLocation.Header,
Type = SecuritySchemeType.ApiKey,
Scheme = "Bearer"
}); ;
c.AddSecurityRequirement(new OpenApiSecurityRequirement()
{
{
new OpenApiSecurityScheme
{
Reference = new OpenApiReference
{
Type = ReferenceType.SecurityScheme,
Id = "Bearer"
},
Scheme = "oauth2",
Name = "Bearer",
In = ParameterLocation.Header,
                },
                new List<string>()
            }
        });

});
var app = builder.Build();
if (app.Environment.IsDevelopment())
{
app.UseSwagger();
app.UseSwaggerUI();
}
app.UseHttpsRedirection();
app.UseMiddleware(typeof(ExceptionHandler));
app.UseAuthorization();
app.MapControllers();
app.Run();

pessoal pra testar é necessário colocar: Bearer {token}.
por algum motivo  funciona apenas no https por enquanto, resultando em 401 no http


text:
refactor: useVerifiedLocations and types

Even if we see many function below ,
const transformHospitalResponse: RT<HospitalResponse, HospitalData> = (res) => {
  return {
    channel: "hastane",
    geometry: createGeometry(res),
    properties: {
      name: res.extraParams?.name ?? null,
      icon: "images/icon-10.png",
      city: res.extraParams?.il ?? null,
      description: null,
    },
    reference: res.entry_id ?? null,
  };
};

const transformTeleteyitResponse: RT<TeleteyitResponse, TeleteyitData> = (
  res
) => {
  return {
    channel: "teleteyit",
    geometry: createGeometry(res),
    properties: {
      name: res.extraParams?.["isim-soyisim"] ?? null,
      description: res.extraParams?.aciklama ?? null,
      icon: "images/icon-14.png",
      reason: res.reason ?? null,
      city: res.extraParams?.il ?? null,
      district: res.extraParams?.ilce ?? null,
      status: res.extraParams?.durum ?? null,
    },
    reference: res.entry_id ?? null,
  };
};

const transformSatelliteResponse: RT<SatelliteResponse, SatelliteData> = (
  res
) => {
  return {
    channel: "uydu",
    geometry: createGeometry(res),
    properties: {
      damage: res.extraParams?.damage ?? null,
      verified: res.is_location_verified ?? false,
      icon: "images/icon-13.png",
      name: null,
      description: null,
    },
    reference: res.entry_id ?? null,
  };
};

const transformSahraResponse: RT<SahraResponse, SahraData> = (res) => {
  return {
    channel: "sahra",
    geometry: createGeometry(res),
    properties: {
      name: res.extraParams?.name ?? null,
      reason: res.reason ?? null,
      icon: res.extraParams?.icon ?? null,
      verified: res.is_location_verified ?? false,
      description: null,
    },
    reference: res.entry_id ?? null,
  };
};

const transformPharmacyResponse: RT<PharmacyResponse, PharmacyData> = (res) => {
  return {
    channel: "eczane",
    geometry: createGeometry(res),
    properties: {
      name: res.extraParams?.name ?? null,
      reason: res.reason ?? null,
      icon: "images/icon-15.png",
      verified: res.is_location_verified ?? false,
      description: null,
    },
    reference: res.entry_id ?? null,
  };
};

const transformSafePlaceResponse: RT<SafePlaceResponse, SafePlaceData> = (
  res
) => {
  return {
    channel: "guvenli",
    geometry: createGeometry(res),
    properties: {
      description: res.extraParams?.description ?? null,
      icon: "images/icon-16.png",
      reason: res.reason ?? null,
      name: res.extraParams?.name ?? null,
      verified: res.is_location_verified ?? false,
    },
    reference: res.entry_id ?? null,
  };
};

There is only one in a generic way.
const transformFunction = (channel, res) => {
  channel,
  geometry: ...
  ...
}

And why don't we use enums for API channels?
export type APIChannel =
  | "ahbap_location"
  | "sicak_yemek"
  | "hastahane_locations"
  | "teleteyit"
  | "uydu"
  | "sahra_mutfak"
  | "turk_eczane"
  | "eczane_excel"
  | "guvenli_yerler_oteller"
  | "twitter"
  | "teyit_enkaz"
  | "babala";

Let me explain in an easier way.
enum Channels {
  A = 'verified',
  B= 'unverified',
  C = 'govern'
  ...
}

Now remember the generic transform function above.
const transformers: Record<APIChannel, RT> = Channels.map((channel) => {
// now it is impossible to use any channel expect inside enums.
   transformFunction(channel, res)
   })

## Then remove unused 200 line...

I've tried to come up with a solution but both our object shapes and API response shapes vary a lot there's just no point to make it generic since you have to write bunch of if statements.

repo: acikkaynak/deprem-yardim-frontend


text:
Added 10 member functions

Pull Request Template
Description
I have added 10 relevant member function prototypes to the code to increase its functionality, some that would prove to be useful in solving other issues, like by checking for invertibility, returning the determinant, adjoint etc.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

!bounty 10

repo: acmpesuecc/laalibrary


text:
Feat/update UI

Tobor scroll
Spinning tobor as requested on figma
Ordered faqs
Added MLH hyperlink
Registration navigation matches figma

Add an even number of FAQ both columns:

Add collapse all button:

Probably remove the "choose the companies your resume goes to" entirely

Unclear if checking the box makes you agree or disagree to the CoC, change to just "Agree"

Other:
Profile creation still seems a bit broken, looking into that in the backend.
Fix overlays (low priority)

Footer text overlap on mobile:

Mobile profile view has sizing issue:

repo: acmutd/hackutd-ix-site


text:
Wrong object type on BaseEvent

BaseEvent has start and end fields defined as Date.
The event onPressEvent from Calendar component emits a BaseEvent object.
That instance seems to have its start and end fields as DayJs objectes instead of date.

@odyodyodys
Thanks for your interest in this project.
I've confirmed that your comment is correct. I'll fix it soon!

Fixed in v0.7.3.
@odyodyodys
Can you check it in the newest version?


text:
Love this idea! Having issues, though.

First of all, thank you for creating this! Mermaid diagrams are such a mess on docusaurus when they're large and complicated.
Additional Context: I'm on the latest version of Docusaurus right now (3.5.2).
I did have one issue when trying to install it.  I couldn't install it with yarn or npm using yarn add docusaurus-plugin-panzoom or npm install docusaurus-plugin-panzoom. It couldn't find it in the registry, so I had to use yarn add @actinc/docusaurus-plugin-panzoom. So, you probably just need to update the README.
It would be really helpful to throw some more documentation in the README on how you might use this in Docusaurus. I know you link to the Panzoom package, but it would be helpful showing how we'd use your plugin in a Docusaurus site (e.g. for Mermaid Diagrams, etc) and in our .md or .mdx files.
Second issue, I'm having now is it failing when I kick off yarn start. No errors in my terminal but when you view localhost:3000 you will get this in your Chrome console:
PanZoom.js:1 Uncaught TypeError: Cannot read properties of undefined (reading 'selectors')
    at eval (PanZoom.js:1:1)
    at ./node_modules/@actinc/docusaurus-plugin-panzoom/dist/PanZoom.js (main.js:55:1)
    at __webpack_require__ (runtime~main.js:34:32)
    at fn (runtime~main.js:334:21)
    at eval (client-modules.js:1:1)
    at ./.docusaurus/client-modules.js (main.js:31:1)
    at __webpack_require__ (runtime~main.js:34:32)
    at fn (runtime~main.js:334:21)
    at eval (App.js:7:83)
    at ./node_modules/@docusaurus/core/lib/client/App.js (main.js:63:1)

I haven't done anything other than install the package and add the plugin to my docusaurus.config.js.
plugins: [
    require.resolve("docusaurus-lunr-search"),
    "@actinc/docusaurus-plugin-panzoom",
  ],

Let me know if I can help in any way. I have seen tons of StackOverflow questions and other people out there wanting to be able to pan/zoom their Mermaid diagrams in Docusaurus.

try to add zoom in themeConfig in docusaurus.config.ts
themeConfig: {
zoom: {},
works for me :)

try to add zoom in themeConfig in docusaurus.config.ts
themeConfig: { zoom: {},
works for me :)

This exactly is what I did additionally to get it working:
     zoom: {         selectors: ['.panzoom-mermaid'], // Your specific selectors for elements to apply panzoom         wrap: true, // Optional: whether to wrap elements in a div with overflow hidden         timeout: 1000, // Optional: delay before initializing panzoom, in milliseconds         options: {           maxScale: 3, // Maximum zoom scale           minScale: 1, // Minimum zoom scale           contain: 'inside', // How the zoom should be contained         },       },

authors: jarodtaylor philippnagel sguilly

repo: act-org/docusaurus-plugin-panzoom


text:
Debugging output overwhelms when using this action via NPM API from our action

Our https://github.com/cypress-io/github-action is using actions/cache via NPM module, we are using v1.0.6
The problem is that if we want to debug our action by setting ACTIONS_STEP_DEBUG: true then the actions/cache prints every single file that we cache during the install. And these could be millions of files, it completely swamps the logs. Is there a way to disable debug logging when using the @actions/cache module?
In our code we use it
const { restoreCache, saveCache } = require('@actions/cache')

const restoreCachedNpm = () => {
  core.debug('trying to restore cached NPM modules')
  const NPM_CACHE = getNpmCache()
  return restoreCache([NPM_CACHE.inputPath], NPM_CACHE.primaryKey, [
    NPM_CACHE.restoreKeys
  ]).catch((e) => {
    console.warn('Restoring NPM cache error: %s', e.message)
  })
}

Wait, how does it class between "github-action" and "actions/cache", isn't there "s" and namespace

Sorry, I should have been clearer about which package and repo I was talking about:

This repo (https://github.com/actions/cache) is the source of the GitHub Action actions/cache.
The NPM Package @actions/cache is part of https://github.com/actions/toolkit.

Your action https://github.com/cypress-io/github-action is using the NPM package @actions/cache, which isn't the same as the actions/cache in this repo.
I think this issue needs to be reported over at https://github.com/actions/toolkit rather than here.

:) I am so sorry for bothering @rcowsill my bad! Naming is hard, just like caching :)

authors: bahmutov rcowsill

repo: actions/cache


text:
Add "Install multiple JDKs" README section

Description:
The PR it to clarify how to use multiple JDKs during build
Related issue:
link to the related issue.

Hi,
setup-java already set some of environment like: JAVA_HOME_11_X64 maybe simple should set JAVA_HOME_11 also ...

JAVA_HOME_11_X64

As I learned is not from the setup action (@v3) but from the container itself.

Hi, setup-java already set some of environment like: JAVA_HOME_11_X64 maybe simple should set JAVA_HOME_11 also ...

I would leave the naming on the pipeline owner will and prefer to avoid any "standard" names because the can clash with same predefined variables. It is kind of naive namespacing.

authors: dsame laeubi slawekjaranowski

repo: actions/setup-java


text:
MacOS Image 20210110.1 Android Build Fails - XA5101: Platform library directory for target Arm and API Level 4 was not found

Description
More info can be found here - https://developercommunity.visualstudio.com/content/problem/1313156/error-xa5101-platform-library-directory-for-target.html
Appears the Image released on 20210110.1 is throwing XA5101 Android build errors claiming it needed Android API Level 4 and its missing.
MacOS Image 20201212.1 works fine and is still on some of the Mac images so some builds sometimes go through fine.
Original user also reporting the issue on Windows images but I can't verify any image versions for that as we run on MacOS.
Area for Triage:
Xamarin, Android, Apple
Question, Bug, or Feature?:
Bug
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[X] macOS 10.15
[ ] macOS 11.0
[X] macOS-Latest
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Expected behavior
Android builds to build as before.
Actual behavior
Android builds throwing Error : error XA5101: Platform library directory for target Arm and API Level 4 was not found.
Repro steps
Setup a Xamarin Android build with msbuild and run on MacOS Image.

This is happening on the windows-latest image as well.

This is happening on the windows-latest image as well.

Hello, @IainS1986
Could you please check a comment - https://github.com/actions/virtual-environments/issues/2420#issuecomment-760969151 ? Does it work for you?

Hello, @IainS1986
Could you please check a comment - https://github.com/actions/virtual-environments/issues/2420#issuecomment-760969151 ? Does it work for you?

@al-cheb  Sure thing, giving it ago now

@al-cheb  Sure thing, giving it ago now

This is happening on the windows-latest image as well.
Could you please try to install the previous version of ndk?

$sdkRoot = $env:ANDROID_HOME
$sdkManager = "$sdkRoot\tools\bin\sdkmanager.bat"
& $sdkManager --sdk_root=$sdkRoot install "ndk;21.3.6528147

This is happening on the windows-latest image as well.
Could you please try to install the previous version of ndk?

$sdkRoot = $env:ANDROID_HOME
$sdkManager = "$sdkRoot\tools\bin\sdkmanager.bat"
& $sdkManager --sdk_root=$sdkRoot install "ndk;21.3.6528147

@al-cheb Sorry took a while to get an image that was 202110110.1
So I added this task at the start of my android flow...
   - task: CmdLine@2
      displayName: "XA5101 Workaround"
      inputs:
        script: '${ANDROID_HOME}/tools/bin/sdkmanager --install "ndk;21.3.6528147"'

Seemed to execute fine, took around 1 minute but seemed to install the old NDK, last line was
[=======================================] 100% Unzipping... android-ndk-r21d/wra
But the android build still failed with the same error.
I can see the android build printed out
Android NDK: /Users/runner/Library/Android/sdk/ndk-bundle/
But don't know what NDK version was actually found there.

@al-cheb Sorry took a while to get an image that was 202110110.1
So I added this task at the start of my android flow...
   - task: CmdLine@2
      displayName: "XA5101 Workaround"
      inputs:
        script: '${ANDROID_HOME}/tools/bin/sdkmanager --install "ndk;21.3.6528147"'

Seemed to execute fine, took around 1 minute but seemed to install the old NDK, last line was
[=======================================] 100% Unzipping... android-ndk-r21d/wra
But the android build still failed with the same error.
I can see the android build printed out
Android NDK: /Users/runner/Library/Android/sdk/ndk-bundle/
But don't know what NDK version was actually found there.

Missed the --sdk_root=${ANDROID_HOME}  as I saw a comment suggest it wasn't needed but I'll give it ago with that too to double check...

Missed the --sdk_root=${ANDROID_HOME}  as I saw a comment suggest it wasn't needed but I'll give it ago with that too to double check...

${ANDROID_HOME}/tools/bin/sdkmanager --sdk_root=${ANDROID_HOME} --install "ndk;22.0.7026061"
Didn't work either :(

${ANDROID_HOME}/tools/bin/sdkmanager --sdk_root=${ANDROID_HOME} --install "ndk;22.0.7026061"
Didn't work either :(

Could you please try one more please: change ANDROID_NDK_HOME variable via bash step?
${ANDROID_HOME}/tools/bin/sdkmanager --install "ndk;21.3.6528147"
echo "##vso[task.setvariable variable=ANDROID_NDK_HOME;]$ANDROID_HOME/ndk/21.3.6528147"

Could you please try one more please: change ANDROID_NDK_HOME variable via bash step?
${ANDROID_HOME}/tools/bin/sdkmanager --install "ndk;21.3.6528147"
echo "##vso[task.setvariable variable=ANDROID_NDK_HOME;]$ANDROID_HOME/ndk/21.3.6528147"

Sure, I tried doing this with 'export ANDROID_NDK_HOME=$ANDROID_HOME/ndk/21.3.6528147' and passing msbuildArguments: '/p:AndroidNdkDirectory=$(ANDROID_NDK_HOME)' into the XamarinAndroid@1 Task but that failed too.
I'll try your command and see how that is (I'll remove the msbuildArguments too)

Sure, I tried doing this with 'export ANDROID_NDK_HOME=$ANDROID_HOME/ndk/21.3.6528147' and passing msbuildArguments: '/p:AndroidNdkDirectory=$(ANDROID_NDK_HOME)' into the XamarinAndroid@1 Task but that failed too.
I'll try your command and see how that is (I'll remove the msbuildArguments too)

@IainS1986, Could you share a sample?

@IainS1986, Could you share a sample?

Still no luck.
Can't really share a sample I'm afraid as its work related projection/solution.
As a cut down YML I have something like this for Android...
- job: Build_Android
    displayName: Build Android (AAB)
    steps:

    - task: CmdLine@2
      displayName: "XA5101/NDK r22 Workaround"
      inputs:
        script: |
          ${ANDROID_HOME}/tools/bin/sdkmanager --install "ndk;21.3.6528147"
          echo "##vso[task.setvariable variable=ANDROID_NDK_HOME;]$ANDROID_HOME/ndk/21.3.6528147"
          echo 'Done!'

    - task: NuGetToolInstaller@1
      displayName: "Nuget Setup"

    - task: NuGetCommand@2
      displayName: "Nuget Restore"
      inputs:
        restoreSolution: '**/*.sln'

    - task: XamarinAndroid@1
      inputs:
        projectFile: '$(Build.SourcesDirectory)/$(android.project.path)/$(android.project.name)'
        configuration: '$(build.configuration)'
        jdkOption: 'JDKVersion'

    - task: AndroidSigning@3
      inputs:
        apkFiles: '**/*.aab'
        apksignerKeystoreFile: 'xxx.xxx'
        apksignerKeystorePassword: '$(android.keystore.password)'
        apksignerKeystoreAlias: '$(android.key.alias)'
        apksignerKeyPassword: '$(android.key.password)'
        apksignerArguments: '--min-sdk-version 22'

    - task: CopyFiles@2
      displayName: 'Copy AAB Artifact'
      inputs:
        SourceFolder: '$(Build.SourcesDirectory)/$(android.project.path)/bin/$(build.configuration)'
        Contents: '*.aab'
        TargetFolder: 'drop'

    - task: CopyFiles@2
      displayName: 'Copy Symbols Artifact(s)'
      inputs:
        SourceFolder: '$(Build.SourcesDirectory)/$(android.project.path)/bin/$(build.configuration)'
        Contents: '*.pdb'
        TargetFolder: 'drop'

    - task: PublishBuildArtifacts@1
      displayName: 'Publish Artifacts'
      inputs:
        pathToPublish: 'drop'
        artifactName: 'release'

My project has AOT, LLVM and Startup Tracing enabled.
Min API - 22 (5.0)
Target API - 30 (11)
Target Framework - Android 11 (R)

Still no luck.
Can't really share a sample I'm afraid as its work related projection/solution.
As a cut down YML I have something like this for Android...
- job: Build_Android
    displayName: Build Android (AAB)
    steps:

    - task: CmdLine@2
      displayName: "XA5101/NDK r22 Workaround"
      inputs:
        script: |
          ${ANDROID_HOME}/tools/bin/sdkmanager --install "ndk;21.3.6528147"
          echo "##vso[task.setvariable variable=ANDROID_NDK_HOME;]$ANDROID_HOME/ndk/21.3.6528147"
          echo 'Done!'

    - task: NuGetToolInstaller@1
      displayName: "Nuget Setup"

    - task: NuGetCommand@2
      displayName: "Nuget Restore"
      inputs:
        restoreSolution: '**/*.sln'

    - task: XamarinAndroid@1
      inputs:
        projectFile: '$(Build.SourcesDirectory)/$(android.project.path)/$(android.project.name)'
        configuration: '$(build.configuration)'
        jdkOption: 'JDKVersion'

    - task: AndroidSigning@3
      inputs:
        apkFiles: '**/*.aab'
        apksignerKeystoreFile: 'xxx.xxx'
        apksignerKeystorePassword: '$(android.keystore.password)'
        apksignerKeystoreAlias: '$(android.key.alias)'
        apksignerKeyPassword: '$(android.key.password)'
        apksignerArguments: '--min-sdk-version 22'

    - task: CopyFiles@2
      displayName: 'Copy AAB Artifact'
      inputs:
        SourceFolder: '$(Build.SourcesDirectory)/$(android.project.path)/bin/$(build.configuration)'
        Contents: '*.aab'
        TargetFolder: 'drop'

    - task: CopyFiles@2
      displayName: 'Copy Symbols Artifact(s)'
      inputs:
        SourceFolder: '$(Build.SourcesDirectory)/$(android.project.path)/bin/$(build.configuration)'
        Contents: '*.pdb'
        TargetFolder: 'drop'

    - task: PublishBuildArtifacts@1
      displayName: 'Publish Artifacts'
      inputs:
        pathToPublish: 'drop'
        artifactName: 'release'

My project has AOT, LLVM and Startup Tracing enabled.
Min API - 22 (5.0)
Target API - 30 (11)
Target Framework - Android 11 (R)

Ok think i've sorted it!
So I was close with the above but need to pass the msbuild argument still to the XamarinAndroid@1 - I guess this sets the NDK path itself regardless of what you do prior to it.
So I changed that task to...
    - task: XamarinAndroid@1
      inputs:
        projectFile: '$(Build.SourcesDirectory)/$(android.project.path)/$(android.project.name)'
        configuration: '$(build.configuration)'
        jdkOption: 'JDKVersion'
        msbuildArguments: '/p:AndroidNdkDirectory=$(ANDROID_NDK_HOME)'

And I got a green build on Image '20210110.1'
Can also confirm in the XamarinAndroid@1 output it printed Android NDK: /Users/runner/Library/Android/sdk/ndk/21.3.6528147/ instead of the default Android NDK: /Users/runner/Library/Android/sdk/ndk-bundle/
Thanks for all the help with investigating a work around!
Am I right in assuming this is an issue in the latest OS images and will be resolved in future ones, or is there something else I should be investigating to resolve this NDK issue properly?

Ok think i've sorted it!
So I was close with the above but need to pass the msbuild argument still to the XamarinAndroid@1 - I guess this sets the NDK path itself regardless of what you do prior to it.
So I changed that task to...
    - task: XamarinAndroid@1
      inputs:
        projectFile: '$(Build.SourcesDirectory)/$(android.project.path)/$(android.project.name)'
        configuration: '$(build.configuration)'
        jdkOption: 'JDKVersion'
        msbuildArguments: '/p:AndroidNdkDirectory=$(ANDROID_NDK_HOME)'

And I got a green build on Image '20210110.1'
Can also confirm in the XamarinAndroid@1 output it printed Android NDK: /Users/runner/Library/Android/sdk/ndk/21.3.6528147/ instead of the default Android NDK: /Users/runner/Library/Android/sdk/ndk-bundle/
Thanks for all the help with investigating a work around!
Am I right in assuming this is an issue in the latest OS images and will be resolved in future ones, or is there something else I should be investigating to resolve this NDK issue properly?

@IainS1986, it is something that we should investigate before. On the latest image, NDK was updated from 21.3.6528147 to 22.0.7026061 that is expected change. You will get the same update if you run sdkmanager --update on local box.
Looks like we face with one of breaking change in NDK 22.x that affects Xamarin Android apps.
In changelog of NDK22, I see

The deprecated /platforms and /sysroot directories have been removed. These directories were merged and relocated into the toolchain during r19. The location of these contents should not be relevant to anyone, including build systems, since the toolchain handles them implicitly

That is pretty relevant to error that you experience
Error : error XA5101: Platform library directory for target Arm and API Level 4 was not found. Expected path is “C:\Program Files (x86)\Android\android-sdk\ndk-bundle\platforms\android-4\arch-arm\usr\lib”

@IainS1986, it is something that we should investigate before. On the latest image, NDK was updated from 21.3.6528147 to 22.0.7026061 that is expected change. You will get the same update if you run sdkmanager --update on local box.
Looks like we face with one of breaking change in NDK 22.x that affects Xamarin Android apps.
In changelog of NDK22, I see

The deprecated /platforms and /sysroot directories have been removed. These directories were merged and relocated into the toolchain during r19. The location of these contents should not be relevant to anyone, including build systems, since the toolchain handles them implicitly

That is pretty relevant to error that you experience
Error : error XA5101: Platform library directory for target Arm and API Level 4 was not found. Expected path is “C:\Program Files (x86)\Android\android-sdk\ndk-bundle\platforms\android-4\arch-arm\usr\lib”

Just to summarize thread above:
Since it looks like a breaking changes in NDK 22 (latest ndk-bundle), the best solution is upgrading app to support NDK 22.
If it is not possible, you can install NDK 21 in runtime and continue using it:

Add the following step at the begin of your build:

Azure DevOps + Ubuntu / macOS (bash):

${ANDROID_HOME}/tools/bin/sdkmanager --install "ndk;21.3.6528147"
echo "##vso[task.setvariable variable=ANDROID_NDK_HOME;]$ANDROID_HOME/ndk/21.3.6528147"

Azure DevOps + Windows (PowerShell):

& $env:ANDROID_HOME\tools\bin\sdkmanager.bat --install "ndk;21.3.6528147"
Write-Host "##vso[task.setvariable variable=ANDROID_NDK_HOME;]$env:ANDROID_HOME\ndk\21.3.6528147"

GitHub Actions + Ubuntu / macOS (bash):

${ANDROID_HOME}/tools/bin/sdkmanager --install "ndk;21.3.6528147"
echo "ANDROID_NDK_HOME=$ANDROID_HOME/ndk/21.3.6528147" >> $GITHUB_ENV

GitHub Actions + Windows (PowerShell)

& $env:ANDROID_HOME\tools\bin\sdkmanager.bat --install "ndk;21.3.6528147"
echo "ANDROID_NDK_HOME=$env:ANDROID_HOME\ndk\21.3.6528147" >> $env:GITHUB_ENV

If you use Azure DevOps and Xamarin Android task, add msbuildArguments argument to it with proper NDK path

 - task: XamarinAndroid@1
      inputs:
        projectFile: '$(Build.SourcesDirectory)/$(android.project.path)/$(android.project.name)'
        configuration: '$(build.configuration)'
        jdkOption: 'JDKVersion'
        msbuildArguments: '/p:AndroidNdkDirectory=$(ANDROID_NDK_HOME)'

Just to summarize thread above:
Since it looks like a breaking changes in NDK 22 (latest ndk-bundle), the best solution is upgrading app to support NDK 22.
If it is not possible, you can install NDK 21 in runtime and continue using it:

Add the following step at the begin of your build:

Azure DevOps + Ubuntu / macOS (bash):

${ANDROID_HOME}/tools/bin/sdkmanager --install "ndk;21.3.6528147"
echo "##vso[task.setvariable variable=ANDROID_NDK_HOME;]$ANDROID_HOME/ndk/21.3.6528147"

Azure DevOps + Windows (PowerShell):

& $env:ANDROID_HOME\tools\bin\sdkmanager.bat --install "ndk;21.3.6528147"
Write-Host "##vso[task.setvariable variable=ANDROID_NDK_HOME;]$env:ANDROID_HOME\ndk\21.3.6528147"

GitHub Actions + Ubuntu / macOS (bash):

${ANDROID_HOME}/tools/bin/sdkmanager --install "ndk;21.3.6528147"
echo "ANDROID_NDK_HOME=$ANDROID_HOME/ndk/21.3.6528147" >> $GITHUB_ENV

GitHub Actions + Windows (PowerShell)

& $env:ANDROID_HOME\tools\bin\sdkmanager.bat --install "ndk;21.3.6528147"
echo "ANDROID_NDK_HOME=$env:ANDROID_HOME\ndk\21.3.6528147" >> $env:GITHUB_ENV

If you use Azure DevOps and Xamarin Android task, add msbuildArguments argument to it with proper NDK path

 - task: XamarinAndroid@1
      inputs:
        projectFile: '$(Build.SourcesDirectory)/$(android.project.path)/$(android.project.name)'
        configuration: '$(build.configuration)'
        jdkOption: 'JDKVersion'
        msbuildArguments: '/p:AndroidNdkDirectory=$(ANDROID_NDK_HOME)'

I am having the same issue on Azure Pipeline build, can anyone suggest any workaround to fix this issue on the pipeline.

I am having the same issue on Azure Pipeline build, can anyone suggest any workaround to fix this issue on the pipeline.

Hello @atulkoshta , does workaround above work for you?

Hello @atulkoshta , does workaround above work for you?

Hi @maxim-lobanov how can I update app to support NDK 22, as I am not getting second options clearly.

Hi @maxim-lobanov how can I update app to support NDK 22, as I am not getting second options clearly.

Hello @atulkoshta. Could you please try switch android ndk-bundle to the latest one 22.0.7026061 on your local machine and confirm that your builds passes or not ? Also what is unclear for you in provided workaround ? We can improve it in this case.

Hello @atulkoshta. Could you please try switch android ndk-bundle to the latest one 22.0.7026061 on your local machine and confirm that your builds passes or not ? Also what is unclear for you in provided workaround ? We can improve it in this case.

@dmitry-shibanov @maxim-lobanov I created a bash step before the android build and now the build is succeeded for android, Thanks that the above workaround is working for me :)

@dmitry-shibanov @maxim-lobanov I created a bash step before the android build and now the build is succeeded for android, Thanks that the above workaround is working for me :)

Hi all,
we started working on rolling back the image due to huge impact. It can take 1-2 days.
We will revisit the strategy of NDK support, and will rollout the image with the fix next week.
Sorry for inconveniences and thank you for your patience.

Hi all,
we started working on rolling back the image due to huge impact. It can take 1-2 days.
We will revisit the strategy of NDK support, and will rollout the image with the fix next week.
Sorry for inconveniences and thank you for your patience.

@AlenaSviridenko @maxim-lobanov One thing to maybe consider is that r21 is an LTS release (and hence should keep getting support going forward with new r21 releases), which might make more sense to keep on the base image (only leapfrogging to the next LTS once it is released) vs. constantly upgrading to the latest NDK.
https://android-developers.googleblog.com/2019/10/introducing-ndk-r21-our-first-long-term.html

@AlenaSviridenko @maxim-lobanov One thing to maybe consider is that r21 is an LTS release (and hence should keep getting support going forward with new r21 releases), which might make more sense to keep on the base image (only leapfrogging to the next LTS once it is released) vs. constantly upgrading to the latest NDK.
https://android-developers.googleblog.com/2019/10/introducing-ndk-r21-our-first-long-term.html

@AlenaSviridenko @maxim-lobanov One thing to maybe consider is that r21 is an LTS release (and hence should keep getting support going forward with new r21 releases), which might make more sense to keep on the base image (only leapfrogging to the next LTS once it is released) vs. constantly upgrading to the latest NDK.
https://android-developers.googleblog.com/2019/10/introducing-ndk-r21-our-first-long-term.html

I agree with this. Users who need a newer version beyond LTS should manually upgrade using the steps outlined in the workaround.

@AlenaSviridenko @maxim-lobanov One thing to maybe consider is that r21 is an LTS release (and hence should keep getting support going forward with new r21 releases), which might make more sense to keep on the base image (only leapfrogging to the next LTS once it is released) vs. constantly upgrading to the latest NDK.
https://android-developers.googleblog.com/2019/10/introducing-ndk-r21-our-first-long-term.html

I agree with this. Users who need a newer version beyond LTS should manually upgrade using the steps outlined in the workaround.

@AlenaSviridenko the rollback broke my project, thanks a lot… ☹

@AlenaSviridenko the rollback broke my project, thanks a lot… ☹

Hi @saurik,
yeah, good idea, we were thinking of a similar strategy of having LTS as a default and having the latest NDK separately with separate environment variable. Working on implementation and testing now.

Hi @saurik,
yeah, good idea, we were thinking of a similar strategy of having LTS as a default and having the latest NDK separately with separate environment variable. Working on implementation and testing now.

authors: AlenaSviridenko IainS1986 KodeDaemon al-cheb atulkoshta david-rtf dmitry-shibanov maxim-lobanov mirabilos saurik

repo: actions/virtual-environments


text:
Update Xcode 11.4

Tool information

Tool name: Xcode
Add or update? Update
Desired version: 11.4 (11E146)
Approximate size: 7.5 GB

Virtual environments affected

[x] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Can this tool be installed during the build?

Are you willing to submit a PR?

No.

Hi, @pixyzehn! Image with Xcode 11.4 will be rolled out during next week's image deployment.

Apple is now rejecting uploads built with the current version of Xcode 11.4 (breaking our CD). Do you have an ETA for this deploy?

@pixyzehn @ydnar the image has been updated. Could you check it, please?

@miketimofeev thanks! We’re also looking forward to the deployment of Swift on Ubuntu (#609), which lets us run a number of Swift workflows on Linux instead of macOS without having to spend 40s installing Swift.

@miketimofeev
This situation is unfortunately quite severe for companies that are relying solely on GitHub Actions to upload builds. Our whole build pipeline is built on GitHub actions and that's the second time after 11.2 that we run into the same problems. Since we are doing nightly builds for all our inhouse testing we need this going.
Is there a possibility for future updates that you can have them ready when Apple is changing their acceptance criteria?

@andyhuber strongly agree.
Possible to decouple Xcode from the normal Catalina / macOS build train?

@andyhuber @ydnar sorry for the inconvenience. Image with Xcode 11.4 is rolling out right now and the will be delivered in a couple of hours. We are going to make such Xcode updates much faster in the future.
Thank you!

Thank you! Appreciate your hard work right now.

@miketimofeev does this include Azure Pipelines images with macOS 10.15? Could one assume that GitHub Actions images and Azure Pipelines images are now identical, given that the Azure Pipelines images repository redirects to this one?

@MaxDesiatov Unfortunately, no. Azure pipelines pools are updated separately from GitHub ones. They will be updated tomorrow(you can follow this PR https://github.com/microsoft/azure-pipelines-image-generation/pull/1511, it will be merged when the deployment is done)

@miketimofeev Any idea how long it usually takes for these rollouts to complete? It looks like the current environment is still on the beta.

@stephencelis it seems to be updated by now.
@miketimofeev Thanks. The documentation https://github.com/actions/virtual-environments/blob/master/images/macos/macos-10.15-Readme.md
seems to still be outdated. Still mentioning 11.4 beta

@stephencelis @andyhuber it's not yet updated for all the environments. The PR will be completed once it's done.
Thank you for your patience!

@pixyzehn @andyhuber @stephencelis image rollout finished. Closing this issue, but feel free to reopen if you have any concerns.
Thank you!

Something is not quite right with XCode 11.4 rollout. I'm seeing 2 different images in Azure Pipelines for macos-latest:
Agent name: 'Azure Pipelines 3'
Agent machine name: 'Mac-1624'
Current agent version: '2.165.2'
Current image version: '20200328.1'

This one works as expected and contains XCode 11.4.
However there is also another version that's being queued from time to time:
Agent name: 'Hosted Agent'
Agent machine name: 'Mac-1383'
Current agent version: '2.165.2'
Current image version: '20200404.1'

This one seems to be newer, however does NOT seem to have XCode 11.4 installed. I'm getting the following error when running xcode-select:
xcode-select: error: invalid developer directory '/Applications/Xcode_11.4.app/Contents/Developer'

@arek-avanade Thanks for the information! We have had some infrastructure changes recently and that might have caused some mess with image versions. I'll take a look and update all the 20200328.1 pools shortly. Sorry for the inconvenience.

@arek-avanade it looks like some of your builds are run on Mojave agents(20200404.1), where Xcode 11.4 is not presented, and sometimes on Catalina(20200328.1). Could you please check your agent specifications?

@miketimofeev This is an excerpt from my YAML:
- job:
    pool:
      vmImage: macOS-latest
      demands:
      - xcode
      - Xamarin.iOS
      - Xamarin.Android

When saying macOS-latest, I'd expect to actually get Catalina all the time, as described in this article:
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops

So it's the same pipeline, which sometimes triggered on 20200328.1 and sometimes on 20200404.1, right?
If so, could you please provide examples? If it's not possible then a plan-id for both builds will be helpful. It can be found by the following link:
https://dev.azure.com/{organization}/{project}/_apis/build/builds/{buildId}

Yes, the same pipeline, however different stages/jobs. So the failing scenario is for a job which is declared with pool/demands as above, it picks 20200404.1 image.
https://dev.azure.com/essity-projects/CIU/_apis/build/builds/31300
The successful scenario is when I just specify vmImage: macOS-latest, but NO demands. In that case somehow 20200328.1 is picked. I'm not sure if this is a coincidence but it consistently happened a few times.
https://dev.azure.com/essity-projects/CIU/_apis/build/builds/30782

Thanks, but unfortunately, I don't have access to the builds. Would you mind providing plan-id for them?

Oh, my bad. Didn't understand your previous ask. I've updated my previous answer with ids.

Thanks!  Yeah, one build is queued against 10.14 while another against 10.15
And what are those demands that you mentioned? I will try to repro it if I have the exact specifications.

And I've found one important note

https://docs.microsoft.com/en-us/azure/devops/pipelines/process/demands?view=azure-devops&tabs=yaml
Looks like it's better to avoid using demands at all.

The one that triggers 10.14 and fails has:
pool:
      vmImage: macOS-latest
      demands:
      - xcode
      - Xamarin.iOS
      - Xamarin.Android

The one that triggers 10.15 has just:
pool:
      vmImage: macOS-latest

And I've found one important note

https://docs.microsoft.com/en-us/azure/devops/pipelines/process/demands?view=azure-devops&tabs=yaml
Looks like it's better to avoid using demands at all.

Oh, didn't know that. I'll simplify my YAML and try again in that case. Although I think this should still not drive the selection of agent image IMHO.

I'm able to repro it with your demands. I'll ask the engineering team about that strange behavior, but yeah, please avoid using demands for now.

@arek-avanade , yep, that is it.
All images have Xcode and Xamarin tools installed so we don't need to specify demands. Could you please try to remove them and test again?

Removed 'demands' and now it works as expected. Thanks for the quick feedback and resolution guys!

There is a bit of legacy around custom user capabilities and demands for hosted pools that results in this behavior. We have some work on the backlog to make it better, but it hasn't been prioritized yet. Essentially, when demands are presented, we assign the job to the most relevant legacy hosted pool (i.e. one of the pools that existed before the single hosted "Azure Pipelines" pool).
If the YAML specifies a pool by name, then it will not redirect. So you could take your original YAML and add name: Azure Pipelines to the pool specification, and it would get to the right place like so:
- job:
    pool:
      name: Azure Pipelines
      vmImage: macOS-latest
      demands:
      - xcode
      - Xamarin.iOS
      - Xamarin.Android

This blog post covers a bit more details:
https://wouterdekort.com/2020/01/14/moving-to-the-azure-pipelines-agent-pool/

authors: MaxDesiatov andyhuber arek-avanade darthwillis maxim-lobanov miketimofeev pixyzehn stephencelis ydnar


text:
[Ubuntu] Fix issues with chromium release version and apply pattern to the release version

Description
We have two issues related to chromium:

Base Position which is four digits (1060) for the latest version of Chrome 99.0.4844.82 instead of the usual six — https://omahaproxy.appspot.com/deps.json?version=99.0.4844.82
To fix that the previous release can be taken — 961656
Sometimes google lists hash instead of revision number and it breaks the logic of the script. We need to apply additional filtration to fix that.

Related issue:
https://github.com/actions/virtual-environments/issues/5256
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run ubuntu18, ubuntu20

/azp run ubuntu1804, ubuntu2004

/azp run ubuntu1804, ubuntu2004


text:
fix segf

🚀 🚀 Pull Request
Checklist:

[ ]  My code follows the style guidelines of this project and the Contributing document
[ ]  I have commented my code, particularly in hard-to-understand areas
[ ]  I have kept the coverage-rate up
[ ]  I have performed a self-review of my own code and resolved any problems
[ ]  I have checked to ensure there aren't any other open Pull Requests for the same change
[ ]  I have described and made corresponding changes to the relevant documentation
[ ]  New and existing unit tests pass locally with my changes

Changes

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

repo: activeloopai/Hub


text:
Release/2.0

🚀 🚀 Pull Request
Pushing 2.0 to main

if we do this merge, doesn't that mean we are releasing non-alpha hub? i feel like we shouldn't merge this yet until at least after we get closer to the 2 week mark

authors: McCrearyD davidbuniat


text:
add Allpay support

This plugin is an active_merchant patch forAllpay(歐付寶) online payment in Taiwan. Now it supports Credit card(信用卡), ATM(虛擬ATM) and CVS(超商繳費).
Most code base on https://github.com/xwaynec/active_merchant_allpay

I'll close this since it has been more than a year without activity


text:
UI-7672 - Fix and Run tests on CI

Some things have changed in activeui-sdk that broke some tests in activeui-migration:

readers of some top-level content server folders have been adjusted
deriveMappingFromMdx does not map an ALL_MEASURES field for kpi widgets anymore
parsing some queries can yield slicerAxis: undefined which is not invalid.

Furthermore:

configures circleCI  to run the tests for each commit on PR branches.
disables linting for the time being (incorrectly references the activeui eslint config)

parsing some queries can yield slicerAxis: undefined which is not invalid.

Where does that come from ?
Changes to the parser/lexer are very/very rare, so I want to make sure we didn't introduce a bug.

parsing some queries can yield slicerAxis: undefined which is not invalid.

Where does that come from ? Changes to the parser/lexer are very rare, so I want to make sure we didn't introduce a bug.

https://github.com/activeviam/activeui-migration/pull/34/files#diff-009e13a7b9398e727f0ef8ad62fd79a251cc83b016b4df444b251521cd34c9a5R34

authors: antoinetissier rgosse

repo: activeviam/activeui-migration


text:
How to get the missing video of kinetics-400

After downloading kinetics-400 training set using the script, only around 220000 videos can be obtained. How can I get the missing videos? I only use it for academic purpose:)

Thanks for your interest in Kinetics.
Please vote favorably this comment make a strong case with the dataset maintainers.
Closing the issue as it's not related to ActivityNet and out of our scope.

repo: activitynet/ActivityNet


text:
⚠ Fetchers has degraded performance

In a97a40b, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 435 ms

Resolved: Fetchers performance has improved in b45e9af.

repo: acumenlabs/status-page


text:
⚠ Processors has degraded performance

In 4300ffc, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 45 ms

Resolved: Processors performance has improved in bf87a78.


text:
⚠ Processors has degraded performance

In eaafa30, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 51 ms

Resolved: Processors performance has improved in cb96dcc.


text:
🛑 Processors is down

In fbc4480, Processors ($STATUS_URL) was down:

HTTP code: 200
Response time: 109 ms

Resolved: Processors is back up in 0e46a55.


text:
remove duplicate lambda

this lambda is declared to perform the same operation twice within a local scope.
instead i thought it could be managed as a single function.
it can only be moved into an internal namespace, but i'm unsure of the appropriate place for it.

Why not do...
constexpr uint64_t broadcast(uint8_t v) noexcept {
   return 0x101010101010101ull * v;
 }

instead of...
constexpr auto broadcast(uint8_t v) noexcept -> uint64_t {
   return 0x101010101010101ull * v;
 }

@lemire modern c++ conventions :) . there is no difference in meaning in terms of behavior.
changed.

authors: SeanTolstoyevski lemire

repo: ada-url/ada


text:
🛑 Telemetry API is down

In b1f75f3, Telemetry API ($SECRET_SITE_4) was down:

HTTP code: 502
Response time: 67 ms

Resolved: Telemetry API is back up in 7ada555.

repo: adadaptedinc/upptime


text:
🛑 Telemetry API is down

In 3b4aa53, Telemetry API ($SECRET_SITE_4) was down:

HTTP code: 502
Response time: 112 ms

Resolved: Telemetry API is back up in f4c8330.


text:
update actions version

@ladyada
It looks like some requirements used by the windows and mac build actions are no longer available.

instead, try to rebase update to the latest version of fluxengine

authors: FoamyGuy ladyada

repo: adafruit/fluxengine


text:
Add Dockerfile and relevant docs.

What does this PR do?
Fixes #119.

Adds Dockerfile based on Debian Jessie.
Adds basic usage notes in README.md

Note that I used a Debian Jessie base image so that the earlier version of openssl was available for SWEET32 test.
How should it be tested?

Check out this branch
Build the image docker build -t yawast-test .
Run a test docker run --rm yawast-test scan https://www.github.com

Any required updates to documentation?
Maybe some additional usage examples, but the current level of docs will get someone started.

Thanks! Really appreciate the help!

authors: adamcaudill nicksantamaria

repo: adamcaudill/yawast


text:
0.2.14 (the latest version on PyPi) cannot be imported without the APPDATA environment variable

Describe the bug
On linux:
pip install pandasgui
python -c "import pandasgui"

Output:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/adam/.venv/pandasgui/lib/python3.11/site-packages/pandasgui/__init__.py", line 15, in <module>
    from pandasgui.gui import show
  File "/home/adam/.venv/pandasgui/lib/python3.11/site-packages/pandasgui/gui.py", line 13, in <module>
    from pandasgui.constants import PANDASGUI_ICON_PATH
  File "/home/adam/.venv/pandasgui/lib/python3.11/site-packages/pandasgui/constants.py", line 15, in <module>
    SHORTCUT_PATH = os.path.join(os.getenv('APPDATA'), 'Microsoft/Windows/Start Menu/Programs/PandasGUI.lnk', )
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen posixpath>", line 76, in join
TypeError: expected str, bytes or os.PathLike object, not NoneType

This works, however:
APPDATA="" python -c "import pandasgui"

The APPDATA environment variable is not one that is commonly set by default on Linux, which makes it awkward to import this package unless you know that it expects the variable to exist in the environment.
Environment
OS: 6.1.85-1-MANJARO GNU/Linux
Python: 3.11.8
Package versions
ipython==8.24.0
pandasgui==0.2.14
plotly==5.22.0
PyQt5==5.15.10
PyQt5-Qt5==5.15.2
PyQt5-sip==12.13.0
PyQtWebEngine==5.15.6
PyQtWebEngine-Qt5==5.15.2

The following code works (better):
import os
env = os.getenv('APPDATA')
if env is None:
os.environ["APPDATA"] = "."
instead of APPDATA="" python -c "import pandasgui" which only did run once.

repo: adamerose/PandasGUI


text:
fix broken test

Fixes the tests by using Body.Content instead of Body which is a struct.

Sigh. Thanks so much for this attempt. My tests are so sorely neglected. I just have to sit down and fix them. Maybe I'll get to that this weekend.
Thanks for trying to help :)

authors: adams-sarah groob


text:
🛑 mastodon-relay.moew.science is down

In 27538bc, mastodon-relay.moew.science (https://mastodon-relay.moew.science/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mastodon-relay.moew.science is back up in f3fb622 after 32 minutes.


text:
🛑 relay.fedi.agency is down

In 25a8835, relay.fedi.agency (https://relay.fedi.agency/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.fedi.agency is back up in cb30b0e.


text:
🛑 mastodon-relay.moew.science is down

In 41d6e78, mastodon-relay.moew.science (https://mastodon-relay.moew.science/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mastodon-relay.moew.science is back up in 84a3842 after 2 hours, 46 minutes.


text:
🛑 relay.wagnersnetz.de is down

In 9aa2dd3, relay.wagnersnetz.de (https://relay.wagnersnetz.de/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.wagnersnetz.de is back up in 07d1ce9 after 45 minutes.


text:
🛑 mastodon-relay.moew.science is down

In a2ce267, mastodon-relay.moew.science (https://mastodon-relay.moew.science/actor) was down:

HTTP code: 502
Response time: 381 ms

Resolved: mastodon-relay.moew.science is back up in c6c6999.


text:
🛑 mastodon-relay.moew.science is down

In 2fd57e5, mastodon-relay.moew.science (https://mastodon-relay.moew.science/actor) was down:

HTTP code: 502
Response time: 534 ms

Resolved: mastodon-relay.moew.science is back up in 249d953.


text:
🛑 mastodon-relay.moew.science is down

In d290ee0, mastodon-relay.moew.science (https://mastodon-relay.moew.science/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mastodon-relay.moew.science is back up in 556d9bc after 17 minutes.


text:
Abbreviated Numbers rounding issue

When using the format string '0.0a' numbers in the interval [999950,  999999] show as 1000.0K when they should show 1.0M.
See: http://codepen.io/skatan/pen/EjjLGr for an example

Hi, this repository is no longer maintained. You can get an improved version here: https://github.com/foretagsplatsen/numbro. That one is still maintained and you can report your issues there.

going to address as duplicate of #283

authors: adamwdraper davidandrus jamiter

repo: adamwdraper/Numeral-js


text:
Germany locale thousands separator

Hi,
I have integrated Numeral JS into my application and noticed that the thousands separator for the German locale (de) is simply a space,
https://github.com/adamwdraper/Numeral-js/blob/7de892ffb438af6e63b9c4f6aff0c9bc3932f09f/src/locales/de.js#L16
I have found multiple resources that indicate a comma "." should be used as the thousands separator. Can I create a pull request for this change?
https://docs.oracle.com/cd/E19455-01/806-0169/overview-9/index.html
https://docs.microsoft.com/en-us/globalization/locale/number-formatting
https://en.wikipedia.org/wiki/Decimal_separator

I noticed this might be a dupe of #139


text:
PGAME add dead transition to Replay Buffer

Hi :)
It seems that the current implementation of PGAME is adding to the Replay-Buffer all the transitions that are collected in the environment, meaning also transitions that occur after the individual is dead and the environment returned done = 1.
I only run initial tests but this seems to slightly impact the PGAME algorithm performance.

Hey :wave:
This is completely true!
One way to avoid this is to set auto_reset=True in the Brax environment instantiation. Hence, new episodes will be played and added to the buffer. This data will be "good" data and will hence have no impact on the training process.
This sounds like a better way to handle it than removing dead individuals from the buffer, because it will avoid a loss of data efficiency (dead transitions are still played and counted in the total number of steps).
Would this solution fit you?

A caveat will be added to the documentation to make sure users are aware of this dangerous behavior.

authors: felixchalumeau manon-but-yes

repo: adaptive-intelligent-robotics/QDax


text:
Error Domain=com.adapty.AdaptySDK Code=2003 "Bad request."

A few seconds after requesting
const info = await adapty.purchases.getInfo({ forceUpdate: true });
and getting the expected result in info.
there is this error showing up in the log (logLevel: 'verbose',) every minutes
2022-05-22 19:09:51.091+0200 [Adapty v1.16.8(1)] - ERROR.
Error Domain=com.adapty.AdaptySDK Code=2003 "Bad request." UserInfo={NSLocalizedDescription=Bad request.}
2022-05-22 19:10:51.086+0200 [Adapty v1.16.8(1)] - ERROR.
Error Domain=com.adapty.AdaptySDK Code=2003 "Bad request." UserInfo={NSLocalizedDescription=Bad request.}
2022-05-22 19:11:51.240+0200 [Adapty v1.16.8(1)] - ERROR.
Error Domain=com.adapty.AdaptySDK Code=2003 "Bad request." UserInfo={NSLocalizedDescription=Bad request.}
2022-05-22 19:12:51.224+0200 [Adapty v1.16.8(1)] - ERROR.
Error Domain=com.adapty.AdaptySDK Code=2003 "Bad request." UserInfo={NSLocalizedDescription=Bad request.}
2022-05-22 19:13:51.115+0200 [Adapty v1.16.8(1)] - ERROR.
Error Domain=com.adapty.AdaptySDK Code=2003 "Bad request." UserInfo={NSLocalizedDescription=Bad request.}

Seems like Kinesis credentials are invalid here. Does this error remains?

Credentials should refresh once in a day or so

What are "Kinesis credentials" ? how is it related to Adapty ?
This is only displayed with verbose mode active and when you get the console log on Xcode or adb (I don't remember)

What are "Kinesis credentials" ? how is it related to Adapty ? This is only displayed with verbose mode active and when you get the console log on Xcode or adb (I don't remember)

Oh, Kinesis is AWS service Adapty uses under the hood. It is streaming data around to assure your device has a fresh cache data and stuff.
It seems to throw 400 occasionally, but we haven't dived into this deeply as it doesn't seem harmful.
In your case you have probably somehow invalidated your streaming token (restarted session?), while keep requesting new cache with an invalid token. I have asked our backend team how we can deal with it, please inform if you consider this to be really annoying or hazardous

Hey, as far as I'm concerned logs should be minimal now (especially with no verbose mode),
I'll close this issue, but feel free to re-open this if you find this problem unresolved

repo: adaptyteam/AdaptySDK-React-Native


text:
chore : remove -webkit-mask-box-image

ref : https://github.com/adcentury/react-mobile-picker/issues/57

Root cause:

IOS 16.4 release note: https://developer.apple.com/documentation/safari-release-notes/safari-16_4-release-notes
Solved:
My team is trying to fix this problem, so that the original effect may be preserved. I tested it on IOS 16.4/16.3 and Android without any problems:
background-color: rgba(0, 0, 0, 0);
-webkit-mask-box-image-source: linear-gradient(to top, transparent, transparent 5%, white 20%, white 80%, transparent 95%, transparent);

You can refer to it, thank you

@ko-devHong, I was wondering if you could update the code to include the changes suggested by @jh6120v. It seems a better way to fix your issue while keeping the original effects.

Hi, @ko-devHong . I'm going to release a new major version and will resolve this issue. See #64

authors: adcentury jh6120v ko-devHong

repo: adcentury/react-mobile-picker


text:
Adds a couple of missing broadcast methods

Namely:

cancel_transfer_from_savings
escrow_aprove
fill_transfer_from_savings
pow2
transfer_from_savings
transfer_to_savings

The full list of all (new) methods in steem and supported here would
be:

[ ] author_reward
[x] cancel_transfer_from_savings
[ ] comment_payout_update
[ ] curation_reward (Maybe it's broken, here we call it curate_reward)
[ ] custom_binary
[ ] decline_voting_rights
[x] escrow_approve
[x] fill_transfer_from_savings
[ ] hardfork
[x] pow2
[ ] reset_account
[ ] set_reset_account
[ ] shutdown_witness
[x] transfer_from_savings
[x] transfer_to_savings

This closes #45.

@yamadapc can you merge it?

authors: adcpm yamadapc

repo: adcpm/steem


text:
Implement basket with AMD module system

Implement basket with amd module system, so that:  …
We can swap out rsvp with compact promise implementation easily for the full package, the basket.full.min.js now became much much smaller than before.
5.20KB (now, minified) v.s. 14.6 KB(when it is with RSVP, minified)
Because of swapping out RSVP, there is no extra global pollution, original RSVP will overwrite any existing RSVP
Its easier for AMD user to use the "source code version" of basket.js
(simply require(['pathtobasket/src/basket']))
Support UMD header so everyone benefits?

By doing this change, the standalone basket doesn't get bloated too much by this change
(3.2KB now v.s. 3.1KB previously)

please rerun travis if possible, the error is very likely to do with phantomjs or connect rather than true code issue

travis issue fixed


text:
Does not seem to work on Cassandra 3

Hello.
We receive an error message: "unconfigured table schema_keyspaces" when trying to connect to cassandra. (we can connect with an older jdbc driver over rpc, without any problems, so there are no problems on the Cassandra side.)
Do you have any plans to support Cassandra 3?
If thats the case, -whats the time frame?

Hi,
The current version if the wrapper uses the datastax Java driver 2.1.9, which is indeed not compatible with Cassandra 3.x
I'll work on 3.x compatibility in the 2 coming weeks if time allows.

The master branch is now compatible with Cassandra 3.x and the fat jar can be downloaded here : https://drive.google.com/open?id=0B7fwX0DqcWSTdmlnZUxYOVVEbFk
Using tuples is broken since some methods disappeared from the Java driver.
I'll see if I can fix this soon.
I'll upload everything to Maven shortly.

repo: adejanovski/cassandra-jdbc-wrapper


text:
feat: add refresh button

Will close #5

Ekstra bir sorum var. Loading state eklenmeli mi?

Basit olarak bu sekilde.
https://user-images.githubusercontent.com/54077855/220322099-54f7de1a-006d-440b-869e-989fa9eb5a68.mov

eline sağlık @yigiterdev

Tesekkur ederim. Isterseniz loading state'i de farkli bir PR'da ekleyebilirim. @ademilter

authors: ademilter yigiterdev

repo: ademilter/zelzele


text:
Update Spinner component accordingly to the new theme structure

subtask of #1071

closed by #1121

repo: adevinta/spark


text:
Added the new choice / PatrickNv23's contribution

New options added: anime, movie and TV series.

I forgot to add the labels :c, I'll close this PR and resubmit it. Sorry :c

repo: aditeyaS/peoples-choice


text:
Enhancement: PDFExpense report looks ugly and hard to port for analytics use

Enhance by creating ".csv" file of data in addition to ".pdf".
"csv" files are much easier to work with for analysis.
PDF File can also be beautified.

Graphs generated in analytics can be extended and added to the pdf to give a more descriptive pdf report.

PDF generated with all graphs from analytics to provide a comprehensive expense report rather than just a record of previous expenses.
Orientation of graphs and layouts can be beautified.

authors: aditikilledar shashank-madan


text:
Different behavior with bootstrap on hidden-xs

Don't you want to update README with the note about this?
I mean in original bootstrap there's .hidden-xs class like
@media(max-width:$screen-xs-max) {
    .hidden-xs {
        display: none !important;
    }
}

But there's nothing about display property for screen above $screen-xs-max. Your version sets it do display:block.
Consider this code on the large screen:
Text

 is inline element by default. Bootstrap leaves it to be inline (or as it's defined by other styles). Your code changes it to be block !important, so it's hard to redefine in further code.
I understand that it is not fixable with the way bootstrap-ms works and suggest don't use hidden-xs on non-block elements at all.

Can you fix this by adding the "visible-ms-inline" class?

I see that you can, but it will disappear on sm and up, and if you try to add a visible-sm-inline class it will be overridden by line 683, making it impossible to only hide a non-block element on xs.

We could revisit this. Maybe a set of hidden-*-inline and hidden-*-inline-block classes could be created for finer-grain control. Anyone want to experiment and submit a pull request? Could also consider other classes as needed for additional display values per https://developer.mozilla.org/en-US/docs/Web/CSS/display.
However, I'm not sure even Bootstrap 4 has a solution for this: http://v4-alpha.getbootstrap.com/layout/responsive-utilities/. So possibly this is a case where custom CSS might be a better approach, at least for now.

authors: Kasheftin MarcGuay adjohnson916


text:
CI action not finding changed modules

I think using git diff HEAD~1 will help

It was git diff origin HEAD. We're all good.

repo: adknowledgeportal/data-models


text:
Indicate validation result in process exit code

When I run the validation from the commandline, e.g. python -m aas_test_engines check_file MyFile.aasx, I would like the process to return an exit code of 0 if and only if the file validated successfully (raises no warnings or errors).
I suggest returning 1 for all other cases, but of course you could return distinct codes for "raises errors" and "raises (only) warnings".

Great idea, thanks

authors: atextor otto-ifak

repo: admin-shell-io/aas-test-engines


text:
Script output in webhhok page

This is not a issue buy maybe enhancement.
In webhhok id we use scripts.
Can I put script output in webhook (id) page?

are you maybe searching for:
include-command-output-in-response - boolean whether webhook should wait for the command to finish and return the raw output as a response to the hook initiator. If the command fails to execute or encounters any errors while executing the response will result in 500 Internal Server Error HTTP status code, otherwise the 200 OK status code will be returned.

Read up what @fbartels wrote.

authors: adnanh fbartels prasenforu

repo: adnanh/webhook


text:
Add missing hasPackage function

After logging in a Campaign instance, the "logon" call returns a list of active packages on the instance.
Make this list available to the clients and add hasPackage function with 2 syntaxes:

hasPackage(packageId)
hasPackage(namespace, name)

Is this different from hasPackage?

I had initially added hasPackage to the Client object has described in this request.
In version 1.0; I added support for the application object which happens to also have a hasPackage function (https://docs.adobe.com/content/help/en/campaign-classic/technicalresources/api/m-Application-hasPackage.html)
Both should return the same thing

authors: catholicon mkiki

repo: adobe/acc-js-sdk


text:
addCoupon is not a function

Expected Behaviour
Able to add coupon to cart.
Actual Behaviour
Sometimes users are not able to add coupon to cart without refreshing page to get access to addCoupon function
Reproduce Scenario (including but not limited to)

Chrome → Incognito window.
Go to product page
Add product to the cart
Add coupon code and press apply. If you look into the console, you will get the error.
Refresh the page, add the coupon code and press apply and now it works.

Steps to Reproduce
Platform and Version
AEM 6.5.0
Magento 2.3.4
CIF 1.0.1
Sample Code that illustrates the problem
Logs taken while reproducing problem
Uncaught TypeError: addCoupon is not a function
at addCouponHandler (react-components.js:90858)
at HTMLUnknownElement.callCallback (react-components.js:128716)
at Object.invokeGuardedCallbackDev (react-components.js:128765)
at invokeGuardedCallback (react-components.js:128820)
at invokeGuardedCallbackAndCatchFirstError (react-components.js:128834)
at executeDispatch (react-components.js:128964)
at executeDispatchesInOrder (react-components.js:128989)
at executeDispatchesAndRelease (react-components.js:129093)
at executeDispatchesAndReleaseTopLevel (react-components.js:129102)
at forEachAccumulated (react-components.js:129074)

I fixed this by removing one check to createCartHandlers in cartInitializer.js. I'm not seeing any issues from that change
if (cartId && cartId.length > 0 && !stateCartId)
becomes
if (cartId && cartId.length > 0)

repo: adobe/aem-core-cif-components


text:
File reference in image component

…the path in crx of the image.......]

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[ ] All unit tests pass on CircleCi.
[ ] I ran all tests locally and they pass.

Closing this since @deepprakash345 would take this change up

repo: adobe/aem-core-forms-components


text:
Publish v2.0.2

[x] blocked by https://github.com/adobe/aio-cna-core-config/issues/6
[x] update aio-cna-core-config dep to ^1.0.14
[x] blocked by https://github.com/adobe/aio-cli-plugin-jwt-auth/issues/46
[x] update aio-cli-plugin-jwt-auth dep to ^2.0.1

published https://github.com/adobe/aio-cli-plugin-console/releases/tag/2.0.2

repo: adobe/aio-cli-plugin-console


text:
add: aio-lib-web tests

Description
add: aio-lib-web tests
Related Issue
Fix: #18
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

The e2e test for aio-lib-web passes (the failures are related to the other modules), so I'll be merging this in.
PASS e2e/e2e.js (8.2s)
  e2e
    ✓ check bundle output dir (2613ms)
    ✓ bundle and deploy test ui (2481ms)
    ✓ undeploy (948ms)

Test Suites: 1 passed, 1 total
Tests:       3 passed, 3 total
Snapshots:   0 total
Time:        8.239s
Ran all test suites.
    - done for aio-lib-web

authors: rajarju shazron


text:
Disable autoclosing

Hello everyone,
so this issue has been answered already. It's just that the solution didn't work for me for some reason.
So whenever I open a bracket, say, <p>, it auto-closes it. This is annoying, as I'm editing existing code for practice at the moment - I just have to erase the added </p>. I tried the troubleshooing outlined here. This is what my brackets.json looks like:

{
"fonts.fontSize": "12px",
"fonts.fontFamily": "'SourceCodePro-Medium', ＭＳ ゴシック, 'MS Gothic', monospace",
"soimon.DocumentOutliner.enabled": true,
"closeBrackets": false,
"closeTags": false
}

So... how do I get rid of that behaviour?
EDIT: fixed code
EDIT: OS is Windows 10, Version of Brackets is release 1.9 build 1.9.0-17312

@GermanJohn closeTags format is different. Try this:
	"closeTags": {
		"dontCloseTags": [],
		"indentTags": [],
		"whenClosing": false,
		"whenOpening": false
	}

@redmunds
Hey, thanks. It tells me it's not valid syntax - I left the "dontCloseTags":[ ] and "indentTags":[ ] empty - do I have to specify each individual bracket I don't want closed?

You only need to specify individual tags if you want to close some but not others. Try just removing those props:
	"closeTags": {
		"whenClosing": false,
		"whenOpening": false
	}

@redmunds
Still tells me it's invalid...
Is there anything else that might be the issue?
`{
"fonts.fontSize": "12px",
"fonts.fontFamily": "'SourceCodePro-Medium', ＭＳ ゴシック, 'MS Gothic', monospace",
"soimon.DocumentOutliner.enabled": true,
"closeBrackets": false,
"closeTags": "closeTags": {
"whenClosing": false,
"whenOpening": false
}
}`

You have closeTags twice. Should be:
"closeTags": {
  "whenClosing": false,
  "whenOpening": false
}

@redmunds
Thanks a lot! I would've never spotted that... finally worked :)

@GermanJohn Glad you got it work. There's a JSONLint extension that will catch errors like that.

authors: GermanJohn redmunds

repo: adobe/brackets


text:
Adding a new first time popup for health data

This popup code is borrowed from Extract first time popup. This will be a non modal popup. Some details may still change

can you attach a screenshot of the new popup.

Good idea. Here it is:

Please make sure no Health Data is sent before the popup is accepted (that is, don't send Health Data when it's open).
One approach would be to wait 24 hours again before the first data is sent.

I'd like to review this, but I may not be able to get to it tonight -- ok if I post feedback tomorrow?

@MarcelGerber We will send the healthData when the user will cancel the popup. Since its not modal, users have option to opt-out.

Shouldn't the popup have a way of opting out especially if the first set of data is sent immediately after the popup closes?

@petetnt I think the idea was that you can leave the popup open while you opt out, but this doesn't seem obvious enough.  I'm proposing we wait at least 1 hour, even if the popup was closed, before any data could be sent.
I think Firefox waits 24 hours, but their popup is much easier to miss... while some other open-source apps have zero wait time before sending metrics, which we definitely don't want to do.  Hopefully we'll land at a happy medium here :-)

@peterflynn I think that any reasonable delay would suffice, but like you said leaving the popup open doesn't really seem obvious as I'd say that the train of thought would be "Oh, I don't want to/can't/shouldn't send any information, I'll just close this popup and go change the settings..." :8ball:

I will have a discussion with @ryanstewart (should be today) and update the thread.

Thanks for the feedback @petetnt, you're right. I think 30 minutes is a good compromise. 30 minutes should be enough time for people to change it but will also give us information from people who are kicking the tires on Brackets.
I don't want to wait an hour because if we wait that long we may not ever end up counting people who open it once, try it out, then leave. I think it's important to still count those users.
Thanks again for the feedback @petetnt (and @peterflynn )

@peterflynn Has initiated another Pull request with this here which improves the UI and fixes some other health report issues as well. I am closing this pull request to avoid duplication

:+1:

@ryanstewart Yep, very good point -- I remember that being an important motivation in the Firefox Health Report discussions as well.  Learning about users who try the app briefly but never come back is in some ways more important than users who stay with the app for a long time, because it helps tell you what you're missing (in terms of usability, feature set, locale support, etc.).

authors: MarcelGerber abose peterflynn petetnt prafulVaishnav prksingh ryanstewart


text:
DEVSITE-47: Implementation of Algolia plugin

https://jira.corp.adobe.com/browse/DEVSITE-47

@naydav the smoke tests are failing. It seems like if you don't provide ALGOLIA env parameters it wont build. Can you pls make Algolia optional in the sense that it should still build even if you don't provide it.

So are these env variables:
ALGOLIA_APP_ID
ALGOLIA_WRITE_API_KEY
ALGOLIA_SEARCH_API_KEY

common to all sites ? If yes, we would use organisation secrets to define them so they can be shared across all sites.

@icaraps, exactly. all three can be used across sites.

Just clarified some thoughts about the .env variables in my summary above.

Replacing ALGOLIA_INDEX_NAME with the existing REPO_NAME

+1 if possible

ALGOLIA_INDEX_DRY_RUN

The dry run could be by default true for builds via GitHub actions which are going to stage and prod and false for local development (eg with npm run dev && open localhost:8000) so site admins don't need to think about whether it should be set or not.

@bdenham

Replacing ALGOLIA_INDEX_NAME with the existing REPO_NAME
From one side it's good point and makes index names more clear.
From another side sometimes it's make sense to have 2 indexes for one repository, like one prod index and one for development (for example DEVSITE-47)
Maybe need to have someting like "index suffix"

Single Algolia variable for each site: DISABLE_AUTO_SEARCH_UPDATES
It could be lead to question What are "search updates"?
Maybe need to rename on something as SKIP_SEARCH_INDEXATION  or SKIP_SEARCH_INDEXATION_DURING_BUILD

When dryRun is set to true, we need to show all the indexing statistics and record objects in the console. And when dryRun is explicitly set to false, we want to publish the records to the site's Algolia index.
Unfortunately, if the option skipIndexing is set false, the indexing mechanism will not be run and ALGOLIA_INDEX_DRY_RUN will have no effect.
Thus, the skipIndexing option is responsible for starting the indexing process, and the dryRun option will be whether this data will be sent to Algolia

Replacing ALGOLIA_INDEX_NAME with the existing REPO_NAME

+1 if possible

ALGOLIA_INDEX_DRY_RUN

The dry run could be by default false for builds via GitHub actions which are going to stage and prod and true for local development (eg with npm run dev && open localhost:8000) so site admins don't need to think about whether it should be set or not.

Done

Unfortunately, if the option skipIndexing is set false, the indexing mechanism will not be run and ALGOLIA_INDEX_DRY_RUN will have no effect.
Thus, the skipIndexing option is responsible for starting the indexing process, and the dryRun option will be whether this data will be sent to Algolia

No, it's the other way around. dryRun is ONLY executed when skipIndexing is false. When skipIndexing is true, all the indexing is SKIPPED. So the dryRun is never executed.

@bd

Unfortunately, if the option skipIndexing is set false, the indexing mechanism will not be run and ALGOLIA_INDEX_DRY_RUN will have no effect.
Thus, the skipIndexing option is responsible for starting the indexing process, and the dryRun option will be whether this data will be sent to Algolia

No, it's the other way around. dryRun is ONLY executed when skipIndexing is false. When skipIndexing is true, all the indexing is SKIPPED. So the dryRun is never executed. In other words, the point I was trying to make is that skipIndexing should always be false, UNLESS the ALGOLIA_INDEX_DRY_RUN is undefined. And in such a case, the gatsby-plugin-algolia default settings for skipIndexing and dryRun are both false. And that means that every time one of the many adobe.io sites is built, records will be published to Algolia. And that is bad! So my suggested change is a built-in safety mechanism to prevent such scenarios when the .env variable is inevitably not set.

@bdenham
Sorry, I made mistake
I meant "skipIndexing is set true"

According to our conversation with Bruce:

Introduced ALGOLIA_INDEXATION: skip | console | index option
Where is:
skip = skipIndexing = true, dryRun = doesn't matter
console =  skipIndexing = false, dryRun = true
index =  skipIndexing = false, dryRun = false

Introduced ALGOLIA_INDEX_SUFFIX_NAME parameter - Optional. The name is composed of two parameters REPO_NAME + ALGOLIA_INDEX_SUFFIX_NAME

authors: bdenham icaraps naydav

repo: adobe/gatsby-theme-aio


text:
feat: support environment variable interpolation in config using syntax ${env.VAR_NAME}. fixes #644

Description
Interpolates environment variables in parsed configuration using yargs middleware. Once the config is read from the combination of the CLI arguments, package.json and environment variables, the resulting object is updated replacing ${env.VARIABLE_NAME} with the value of process.env.VARIABLE_NAME (assuming such a variable exists).
The current use of ${version} in the name config property is not impacted since that is not prefixed with env..
Related Issue
#644
Motivation and Context
See #644
How Has This Been Tested?
Local testing
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] I have signed the Adobe Open Source CLA.
[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[X] All new and existing tests passed.

fixed with #648

authors: justinedelson tripodsan

repo: adobe/helix-deploy


text:
Migrate to manifest v3

Manifest v2 EOL schedule:

January 17, 2022: Chrome Web Store stops accepting new Manifest V2 extensions
January 2023: Chrome Web Store stops accepting updates to existing Manifest V2 extensions,
Chrome stops running Manifest V2 extensions

https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/
Issues directly related to the manifest v3 migration:

[x] https://github.com/adobe/helix-sidekick-extension/issues/103
[x] https://github.com/adobe/helix-sidekick-extension/issues/102

More issues to be bundled:

[x] https://github.com/adobe/helix-sidekick-extension/issues/100
[x] https://github.com/adobe/helix-sidekick-extension/issues/104

Migrating to manifest v3 brings some big changes due to the fact that all JS code must come bundled within the extension:

Sidekick can no longer be loaded from https://www.hlx.live/tools/sidekick/module.js. The source files will have to be moved from @adobe/helix-sidekick to this repo, along with tests, jsdoc generation and workflows to deploy to www.hlx.live` for use by the bookmarklet. The changes in @adobe/helix-sidekick are being prepared in parallel here.
Testing of local or branch versions of sidekicks will no longer work, and the respective settings will be removed from the Options page
Project configuration can no longer be loaded from /tools/sidekick/config.js. We will have to migrate to a config.json instead.

No longer supported:

chrome.webRequest is no longer available in manifest v3, so the current method of detecting the proxy URL using the via header will no longer work, and the sidekick won't know which project config to use. We will need to find a new method, e.g. by injecting a meta tag in the helix simulator.
Custom plugin configurations can no longer contain JS, which greatly limits the number of currently supported use cases. Essentially, only buttons opening a URL (tagger, templates, etc) can still be supported going forward. More sophisticated plugins will need to be migrated to a project-specific solution (e.g. /tools/preview.js).

Issues directly related to the manifest v3 migration:

[ ] https://github.com/adobe/helix-sidekick-extension/issues/103
[ ] https://github.com/adobe/helix-sidekick-extension/issues/102

More issues to be bundled:

[ ] https://github.com/adobe/helix-sidekick-extension/issues/100
[ ] https://github.com/adobe/helix-sidekick-extension/issues/104

Update regarding custom plugins: thanks to @auniverseaway's research, we are able to continue to provide a mechanism for dynamic plugins:

config.json defines a button and an event to fire when the button gets clicked
Sidekick fires a helix-sidekick-ready event when loaded, so project code can react to it
The project code registers a listener for the event name with (custom: prefix) and provides the code to execute
The listener will be passed the Sidekick's current state object for reuse

repo: adobe/helix-sidekick-extension