Looped fibonacci

Add a looped fibonacci for benchmarks
This fibonacci is useful for comparing against other vms that are not validating the call stack, and benchmarks in general. It works as the other fibonaccis but uses less steps.

Codecov Report

Merging #567 (dc9d6ed) into main (c2e45d0) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #567   +/-   ##
=======================================
  Coverage   95.50%   95.50%
=======================================
  Files         112      112
  Lines       18904    18904
=======================================
  Hits        18054    18054
  Misses        850      850

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Enide-2015-7 executes too slow.

I've installed Enide-2015-7-windows-x64-20150706.
Whenever I execute it, it always performs
'Building workspace', "Invokeing JSHint Problem Checker", "Initialize DLTK", "InitRemoteEditJob", "Updating Error Reports Database", etc.
Furthermore as I type some codes in js file, the response appears too slow.
I'd like to use the tool, but ...
If someone knows how to solve such a symptom, please let me know.

Well, could you share timings?
Could you install also any other Eclipse Mars-based distribution and compare.


Recordset shows no results

Recordset on our CI servers is showing a blank page when it should be showing results.
E.g.  https://dev.isrd.isi.edu/chaise/recordset/#1/legacy:dataset

When I navigate to the following address: https://dev.isrd.isi.edu/chaise/recordset/#1/legacy:dataset/id::gt::100&id::lt::13000@sort(summary)
data does appear for me properly. This must be linked to there be no filters defined.

@hongsudt @karlcz  You can test the fix here

Closing this issue.


[iOS] Video continues playing after you leave page

Started at #46
If you leave a page, the video continues playing in the background, but only on iOS. Potential fix to make video run destroy() or suspend() on leaving the page?

I believe this is easily solved by just running the destroy method on the video. Videos must be destroyed as on iOS there is a hard limit of around 15-20 videos. Soon as you hit this, it'll stop rendering videos.

@bnussey yes, but maybe it should be done automatically by the plugin? That would make everything simpler.

Hey @lukeramsden I disagree, its a common pattern and good practice to run necessary destroys when leaving a page.

Did not know about destroy(), that will do :)

I knew about it, that's what I'm currently doing, I just think it's good practice to have to plugin clean up after itself.

@lukeramsden -- the plugin will not know when to do that, it relies on you to specify that. Feel free to provide a PR if you'd like though.

Is there no way to bind it to the onNavigatingFrom event? I'll have a go at it later cause I'm on my phone right now.

@bnussey  Just FYI, I tested it with destroy() and it works. But when you return back to the video-page, the binding is not being set.
Binding: Binding error while setting property src of Video<mainVideoPlayer>@file:///app/views/home/partial-video.xml:12:17;: TypeError: null is not an object (evaluating 'this._playerController.player = this._player')

Hey @manijak just depends on your specific scenario. If you want to come back to the video and play it, then you just need to pause it. If you never want to come back to the video, and the page is going to be reloaded, you destroy it.

Here is another issue. The video player gets paused and mute when I switch to the iOS home screen, but when I lock device everything works correctly. I think the issue is in the native script’s videoplayer.


Remove flag to configure split of whisks and activations db.

With this PR, the ability to save activations in the whisks database will go away.
All activations will be saved in the activations database. If you have activations in your whisks database, they will not be returned by an OpenWhisk call (e.g. wsk activation list). Only the activations in the activations database are returned by the controller.
If you have not migrated your databases yet, there is an manual at https://gist.github.com/cbickel/37e651965781b27de245eac0ce831a53.
If you don't need old data, the wipe.yml will update your databases by recreating the activations and actions db. This will wipe all your data.

As suggested in the mail:
I think this PR can be merged by the end of the week.

PG3#591 is green.


Received message with invalid header.

Hi,
I have uploaded to a D1 Mini, it connects to my wifi, I get the status Online message in MQTT, together with the air filter and wifi message, however, it doesn't show any values in MQTT and I can't see it in Home Assistant. When I look at the Serial output of the arduino IDE, I get this messag: "Received message with invalid header."
Occasionally it does show a reading:
Received PM 2.5 reading: 42
Current measurements: 42, 39, 39, 40, 40
Thanks in advance

This is shown when the data received from the particle meter is not as expected. Is your soldering correct and reliable?

I was having the same problem - I was getting the value from the sensor only in about 10% of tries. The rest were "Invalid header".
I've redone my wiring very carefully, tried using a voltage divider on the TXD2 pin, and tried to play with the magical delay(15) value (https://github.com/Hypfer/esp8266-vindriktning-particle-sensor/blob/83fd7c5034cc9737b954c5625426563492d83a2c/src/SerialCom.h#L90). Nothing helped.
Then I realized that I don't understand why we are clearing the receiving buffer in the middle of the receiving process (lines 92-94 in SerialCom.h). I commented this part out (along with the delay(15)) and it improved a lot - I am receiving reasonably looking values in more than 80% of attempts.
Can someone explain please why we are clearing the buffer?
Thanks!

I had the same problem using ESP32 and the Hardware Serial2.
The problem is caused by the fact that, depending on how often you poll the sensor library (SerialCom::handleUart(state)), serialRxBufreceives multiple messages at a time (20 bytes each) and their combined length is often over 64 bytes. For example, I've just received 16 11 0B 00 00 00 31 00 00 03 9A 00 00 00 2F 01 00 00 00 D0 16 11 0B 00 00 00 32 00 00 03 9B 00 00 00 30 01 00 00 00 CD 16 11 0B 00 00 00 33 00 00 03 9E 00 00 00 31 01 00 00 00 C8 16 11 0B 00 00 00 33 00 00 03 9F 00 00 00 31 01 00 00 00 C7 16 11 0B 00 00 00 33 00 00 03 9F 00 00 00 31 01 00 00 00 C7 , which is 5 messages in a row.
The code
https://github.com/Hypfer/esp8266-vindriktning-particle-sensor/blob/83fd7c5034cc9737b954c5625426563492d83a2c/src/SerialCom.h#L92-L94
clears the buffer after 64 bytes thus deleting three whole messages (3 x 20 bytes) and the 4 bytes of the next message. What is left is not a valid message because the header was chopped off.
Anyway, the fix seems to be replacing the loop
https://github.com/Hypfer/esp8266-vindriktning-particle-sensor/blob/83fd7c5034cc9737b954c5625426563492d83a2c/src/SerialCom.h#L85-L95
with
while (sensorSerial.available() && rxBufIdx < sizeof(serialRxBuf))
{
    serialRxBuf[rxBufIdx++] = sensorSerial.read();
    Serial.print(".");
}

Works fine for me after this change. I've not created a pull request because I am not sure why the author used this clearing of the buffer in reading process - probably there is a good reason that I don't see.

I had the same problem. I tried to reupload sketch several times, but the problem was in incorrect configuration to the Home Assistant (mqtt). After reuploading the sensor didn't create AP again (allowing to reconfigure settings).
As I saw the mqtt configuration is stored in the flash and used even if I reupload  the sketch.
The solution is to erase the flash, like described here:
https://github.com/Hypfer/esp8266-vindriktning-particle-sensor/issues/20#issuecomment-950218909

Hi everyone,
I'm using wemos D1 and i'm receiving this data from serialRxBuf from vindriktning:

I already try to use the sigention from @rublinetsky but still not working...
Can you please help me?


Resources and Outputs don't always show on state import

Bug description 🐞
I've been importing 50+ workspaces into Terrakube and mostly things have been OK. But there have been a few that whilst importing OK never seem to show ant resources or outputs. The state is there and everything else functions OK, including plans and applies etc.
It always seems to be the same workspaces. I've tried deleting them and re-adding them again, but the behaviour is always the same. Nothing obvious in the logs. These workspaces vary in size too, between small and large.

Steps to reproduce
Unknown at this time. Is there anything I can do to debug?
Expected behavior
No response
Example repository
No response
Anything else?
No response

Could you check if there is any error in the browser console when you open the workspace?
The UI parse the state values to show the resources in the UI using this small logic.
https://github.com/AzBuilder/terrakube/blob/191689a34124232295816fad2de38294ffd71075/ui/src/domain/Workspaces/Details.jsx#L1225

I get the above error on the broken workspaces.
Looking at the request I can see that the resources and outputs are actually returned by the API. So yes it does look like a UI issue!

Looking at the code it looks like child modules are expected to have a resources key.

In the case of my resources theres other child modules that have further resources within. So I guess this needs to be a recursive function to go through X child modules and their resources (I think)!

Yes that is correct, I think the code will need some small adjustment in that part, it is quite difficult to parse the state correctly, we have done a lot of adjustment in that particular part over the last couple of months.
I could try to do the adjustment and maybe release a Hotfix later today but I will need some help to test it because I don't have a way to reproduce your state file

Happy to help where possible. Looking at the structure I can imagine what a nightmare it must be!

I created the following beta release so you can test the fix in the recursive logic, you will only need to override the UI version like this if you are using the helm chart
ui:
  version: "2.19.2-beta.1"

I am glad that it work for you, I will create the hotfix version 2.19.2


DryIoc in FreshMVVM

In the video with James Montemagno, Michael Ridland talks about the possibilty to change the built-in container of TinyIoC to any other IoC container. Now my question is how can this be done? We're already using DryIoc in our company so it would be great if we could use it with FreshMVVM. Are there any help pages, tutorials or something like that? Couldn't find something via Google.

Oh wow, would help to read the README.md...


add update/patch permission of namespace to klusterlet for 2.3

The related issue: https://issues.redhat.com/browse/ACM-6808

/hold Hold until the 2.3 branch is open for business.

/lgtm
/approve

This one is already fixed by a cherrypick PR: https://github.com/stolostron/managedcluster-import-controller/pull/298
@elgnay Should we close this?


GUI title affected by g-label processing

Prevent g-label processing affecting GUI title if the title starts with "G".

Can you add the tests in #289
Or I can do it in a few hours

Ok, I pushed the test examples - not sure if I did it correctly.


Wrong time on statistics graph

Technical details

YOURLS version: 2.0
PHP version:  7.0.15-0ubuntu<IP_ADDRESS>

There is right time on server
root@server:~# date
Thu Mar 30 15:18:20 MSK 2017

and admin page show right times of link creation. But only in hits graph time is wrong - it last point show -3 hours from Msk.
GMT now 1:18 pm.
Last point show 12 pm.
Moscow, server and my PC time is 3:18 pm.
.

Yeah, known behavior. There are inconsistencies in time management across the code. Leaving the issue open, this shouldn't be something major to refactor in the code, but honestly something I don't care about at all. Patches welcome :)

I thought it was fixed in PR:2048 but it looks like we left out the offset in current_timestamp.

Supposed to be fixed by #2228


Async suggestion support.

Please describe your suggestion
Async support for overriding suggestion.
Please supply examples of the desired inputs and outputs
new PlayerArgument("player").overrideSuggestions(sender -> {
  return CompletableFuture.supplyAsync(() -> {
    final var players = new ArrayList<String>();
    players.add("db-player-1");
    players.add("db-player-2");
    players.add("db-player-3");
    return players.toArray(new String[0]);
  });
});

I don't see how this could ever work in practice. When a player starts typing a command, it tells the server to request suggestions. When the server receives whatever packet telling it to generate suggestions, it must instantly respond with the list of suggestions - the server cannot delay this response. If the server wants to delay this response, the server has to block the main thread (which is the whole server).
I don't think this is possible for the CommandAPI.

This is indeed possible! Massive kudos to the pull request from #249.

Implemented for the next release (hopefully 6.6.0) in a few days time.

Implemented in 7.0.0.


Entry API does not update archetype::Identifier after entity shape change.

The Entry API has a copy of the Location as one of its fields: https://github.com/Anders429/brood/blob/master/src/world/entry.rs#L61
This works great on the first use of either add() or remove(), as the identifier accurately represents the entity's archetype. However, if the user attempts to change shape using add() and remove() multiple times, the identifier is never updated, and therefore the wrong archetype is modified on the later changes.
This can cause serious issues, as it will desynchronize the entity::Allocator's map with the actual entities, meaning the location of entities will no longer be correct and we'll have dangling entities all over the place.
If the further shape changes are out of bounds, the swap_remove() call will panic here: https://github.com/Anders429/brood/blob/master/src/registry/sealed/storage.rs#L584. However, when viewing that row through a query later, the index is always assumed to be valid, causing undefined behavior here due to the safety contract no longer being met: https://github.com/Anders429/brood/blob/master/src/registry/sealed/view.rs#L289-L295. Therefore, this is accidental unsoundness in the API.
The solution is likely to update the location in the entry after every entity shape change.

Now is as good a time as any to release 0.9.0. It will contain this fix.


Bower may be dying!

Looks like Bower may well becoming a victim of its success!
I stumbled across this after following a twitter comment, but it looks as though there are few/no active core members in the Bower project!
Original comment by @mjackson): https://github.com/rackt/redux/issues/944#issuecomment-154858804.
Refers to following discussion with last active bower core member (@sheerun): https://github.com/bower/bower/pull/1748#issuecomment-150104311
Could taking a dependency on Bower become a problem for ASP.NET 5+?

@DamianEdwards @rustd @madskristensen ?

There is some information about this in 1748 that seems to contradict that bower has completely stopped development (as claimed in the popular tweet), but I think a brief statement for all the knee-jerk responses would be helpful, because understanding the situation requires reading a few paragraphs right now.
TLDR unofficial assessment of the situation: bower is currently maintained by one unpaid individual and this is a real problem, but the project is seeking funding, which may keep things active.

Just wanted to chime in here and say that I have zero skin in this game. I
gain nothing if bower dies, except perhaps the freedom from having to
support such a poorly conceived tool in the open source work that I do.
If you guys are looking for a package manager for JavaScript, I'd suggest
either using npm or jspm.
On Fri, Nov 13, 2015 at 1:36 PM Nick Perez<EMAIL_ADDRESS>wrote:

There is some information about this in 1748 that seems to contradict that
bower has completely stopped development (as claimed in the popular tweet),
but I think a brief statement for all the knee-jerk responses would be
helpful, because understanding the situation requires reading a few
paragraphs right now.
TLDR unofficial assessment of the situation: bower is currently maintained
by one unpaid individual and this is a real problem, but the project is
seeking funding, which may keep things active.
—
Reply to this email directly or view it on GitHub
https://github.com/aspnet/Home/issues/1074#issuecomment-156562580.

Could taking a dependency on Bower become a problem for ASP.NET 5+?

I don’t see a dependency on Bower in ASP.NET 5. Yes, the default web template comes with some Bower stuff, but that’s about it. You can absolutely set up projects without ever touching Bower. As an example, the project I’m currently working on has a custom build process that takes JavaScript dependencies via npm, has user code in TypeScript, and builds everything using gulp.

Thank you for your concern, but Bower is not dying. It is stable software, and we've got extra volunteers.
Bower has no Creator, it's a community effort.
Of course there are people who would "donate money to help remove bower from the js community" as someone recently said to me. Maybe little help with making it even more stable, and easing the transition?
If you think you can implement Bower in NPM, do it. I'd be really happy to get a drop-in solution. Really.

I've seen an increasing move away from Bower over the last year to just using NPM to manage packages for the front-end side of things.
I'd suggest using either JSPM, or WebPack+NPM.  They seem to be where the community is focusing right now.  The advantage of both is that if ASP.NET scaffolds it correclty, you can bundle TypeScript support in every new ASP.NET project!

Worthwhile read, ca. 2014: http://blog.npmjs.org/post/101775448305/npm-and-front-end-packaging

BTW as others have mentioned here, ASP.NET itself has no dependency on any JavaScript thing at all. It has some built-in providers for jQuery (that can be swapped out) and that's it.
ASP.NET project templates use Bower, and Grunt or Gulp (depending on how old a build you're using) but that's all just for convenience. No actual tie-in.

Don't forget that the default project template is the reference point for many developers. Not all of them are going to come here and read this discussion.

Yes, I think it's fairly important that people not be given bad advice.  People tend to rally around defaults and asp.net could inadvertently create a pocket of developers using tools that are falling out of favour.
I must admit, bundling a front end stack seems like a battle you will always lose.  Why not make it optional during scaffolding?

@Eilon It's not only templates but also build in support for Bower in VS (which in my opinion should be optional and designed as separate extension).
It was also my first impression that I should use Bower and that you recommend using it. I think that 90% of people, if not more, will use VS to develop ASP.NET applications so having "Manage Bower Packages" option somehow ties you to Bower whether you want it or not. I think that it's hard to distinguish between tooling and ASP.NET - see for example number of problems people had updating DNX version and but not knowing that they should update tooling (eg. http://stackoverflow.com/questions/33156090/getting-the-correct-dependencies-for-net-web-api-for-the-latest-net-core/33158692#comment54127039_33158692). Providing of course that you do not spend significant amount of your time on github.com/aspnet :)

I also think built-in support is too much :)

Ping @DamianEdwards

ASP.NET itself has no dependency on any JavaScript thing at all

Perhaps not, but the meta-point raised by many here is that the default experience for dev's coming to ASP.NET 5 is that Bower is built-in to the initial templates and tooling experience.
I don't have a dog in this race, but am concerned that while Bower has provided some great features in the last few years, if the community is moving toward node instead, perhaps consolidating around node-based templates and tools may be a better option.
@atrauzzi summed it up nicely (emphasis mine):

I think it's fairly important that people not be given bad advice. People tend to rally around defaults and asp.net could inadvertently create a pocket of developers using tools that are falling out of favour.

that Bower is built-in to the initial templates and tooling experience

Note that NPM is also built into it as a first citizen. And I doubt that anyone doing serious front end development will just use whatever the default template gives you. Since no web framework is built to work inside ASP.NET, no framework will have instructions to use it inside there, so I think it’s a lot more likely to expect that front end developers just start how they always started: In the command line, setting up their front end development process. And that then happens to integrate nicely into ASP.NET and VS without extra work.

Add another +1 for moving away from Bower in favor of npm. I'd also like to see default templates utilizing Webpack. It's been a bit difficult to figure out how to integrate Webpack & React in an ASP.NET Core project which serves up the index page via a single MVC HomeController... and pretty much everyone who uses React is using Webpack.

@joshburgess - Webpack is a safe bet now, but things like JSPM which feature dependency management (not just building) are starting to shift things as well.  It'll be bower all over again soon enough.
I think anything beyond shipping a package.json is probably risky.  People should integrate their front end as they see fit.

Yes, I know SystemJS & JSPM are also popular with the Angular 2 / Aurelia crowds. Browserify is still fairly popular with a lot of people as well. Bower, however, is not really used by many people at all anymore.
If they offer any templates utilizing modern client-side dev tools, they should try to make them current... I'm hoping that a few different templates are made available showing how to best integrate with the most commonly used tools.

Looking forward for "ASP.NET Core Universal Starter repo" to get npm instead of bower . . .


Remove bower

To remove bower dependencies, use npm instead.
If the package doesn't have package.json, add JS file to this repository (e.g. jquery.selection)
Use browserify to require the package and use on browser.

To remove bower completely, we have to consider about bootstrap-sass.
We have 2 options:

Move bootstrap 4 (alpha-2) and use npm.

bootstrap 4 uses scss officially.

bootstrap 4 is still alpha.

Use bower until bootstrap 4 will be released.

bootstrap migration cost is 0

bower will alive.

oops ... there is https://github.com/twbs/bootstrap-sass and they provides their package on npm.
so use it.


Getting null on Android

Flutter (Channel master, 1.24.0-4.0.pre.51, on Mac OS X 10.15.7 19H2 darwin-x64, locale en-GR)
`
print("Getting installer info");
try {
var installerInfo = await getInstallerInfo();
print(installerInfo);
print(installerInfo.installerName);
} catch (error) {
  print(error);

}

`
The console prints
I/flutter (17452): Getting installer info
W/.lazyland.yatz(17452): Accessing hidden method Lsun/misc/Unsafe;->getInt(Ljava/lang/Object;J)I (greylist, linking, allowed)
I/flutter (17452): null
I/flutter (17452): NoSuchMethodError: The getter 'installerName' was called on null.
I/flutter (17452): Receiver: null
I/flutter (17452): Tried calling: installerName

Hi there!
Yeah, that's intended. On Android sometimes it's not possible to determine what app was used to install your app (when context.getInstallerPackageName() returns null), so this library follows the same behavior. Usually it will return null when installing using flutter run, adb, or Android Studio. I will add this to the docs soon.
You can fix that code by testing for null before accessing the installerName:
final installerInfo = await getInstallerInfo();

if (installerInfo == null) {
  // Could not determine the installer
} else {
  // Installer discovered
}

Or by using null-safe access, e.g.:
print(installerInfo?.installerName);

I'll close this issue for now. Feel free to create another issue or reopen this one if you find a bug or need some help.


[Flow] Add support for method boolean on FunctionTypeAnnotation

Right now,
type T = { method: () => void };
type T = { method(): void };

produce the exact same AST (and behave the same way). It would be nice to differentiate somehow so that we can print them the way they were written.
The flow parser is going to get a method boolean on FunctionTypeAnnotation that distinguishes between the two forms.
It would be great to have the same for Babylon so we can keep the printer simple!
Thanks!
cc @hzoo @samwgoldman

Yup, method property on the object type ast, like we have for object values, sounds good to me.

I've got a PR open now for this (#334), adding method to FunctionTypeAnnotation.
How about for ObjectTypeCallProperty which also contains a method-looking FunctionTypeAnnotation, e.g. type T = { (): number }?

@danharper ObjectTypeCallProperty is always a method, I don't think it's necessary there.


swift-api-digester: keep track of type declarations with fixed layout.

We need special logic to check abi-stability for decls with fixed
layout.

@swift-ci please smoke test and merge


Update typescript definitions to match the latest SDK v3.0.2

https://github.com/intuit/oauth-jsclient/issues/100

I'm unable to run the sample app, for some reason `req.query.json.clientId` is not being treated as a property of a JSON object, though I did verify that `typeof(req.query.json)` is object. I tried `JSON.parse(req.query.json.toString()).clientId` but that gives me a different error: `SyntaxError: Unexpected token o in JSON at position 1`

Thanks @shlok-kothari. I will take a look at the PR 👍


Offline download crashes

In the flutter bindings we are seeing this crash https://github.com/m0nac0/flutter-maplibre-gl/issues/39 when downloading e.g. regions from the source https://demotiles.maplibre.org/style.json in our test/example app.
I suspect it has to do something with the new regex validations introduced here https://github.com/maplibre/maplibre-gl-native/blob/master/src/mbgl/util/mapbox.cpp as part of the migration to Maplibre. But I couldn't find any documentation for offline downloads.
Are there different requirements for source URLs for offline downloads compared to those for regular map displays?

The download function is a important feature for our App. Is there any update on this issue?

A self-contained reproducer would help a lot in fixing this faster. Do you think you could prepare it?

I can only reference to to flutter binding example: https://github.com/m0nac0/flutter-maplibre-gl/tree/main/example
Downloading a region results in a crash, descripted in https://github.com/m0nac0/flutter-maplibre-gl/issues/39
But therefore you need flutter to be installed. @m0nac0 can you provide a reproducer without flutter?

@m0nac0 can you provide a reproducer without flutter?

Sorry, I probably won't have enough time to try to reproduce this without flutter.

DemoTiles is hosted on GitHub Pages and does not work with the offline download. Please use another tile server to try out offline support.

Any success on this issue, is it because of the DemoTiles?

Hello @noorbakerally, I tried out offline support with the demo tiles which failed while a 'normal' tile server worked. If you run into any issues feel free to create an issue!


Website-viewer

new pr as follow up of #13
This is the ground work for a generic, config driven online resource viewer extensions.
This includes

Showing how to add commands that spawn web pages inside of Platform
example web pages
reloading pages on scripture reference and scroll group changes, so that web pages stay up to date with the current scripture reference
retaining the web page on layout changes and restart of platform

👉 Demo

This change is

interestingly git shows commits in order of their creation date, but the order I applied them on this branch is actually

creating the extension with npm run create-extension -- website-viewer
merging the relevant previously done work from web-viewer branch into this
small fixes on top

as mentioned in #13
Interesting files to review are

main.ts
webViewerOptions.ts

Maybe

types/online-resource-viewer.d.ts
contributions/menus.json
contributions/localizedStrings.json

How to add a new resource: example https://github.com/paranext/platform-bible-sample-extensions/pull/14/commits/58aa0398dd7951b7000677d7acea1bc4a56dd7ca


Breaking changes of Cache::put

Related to #13831, #13810, #5860, and 37267d06f1798f929acc0155d024c4236d9ea27e
BC 1
Cache::put('foo', 'bar', 0) and Cache::put('foo', 'bar', '0') and Cache::getStore()->put('foo', 'bar', 0) in Laravel <=5.2 means cache forever, except for:
- DatabaseStore: caches for 0 second.
- RedisStore: cache for 1min or 1sec, depending on if #13810 is applied.
In Laravel 5.3, Cache::put('foo', 'bar', 0) and Cache::put('foo', 'bar', '0') means don't cache at all across all the stores and Cache::getStore()->put('foo', 'bar', 0) will behave as in Laravel <= 5.2.
BC 2
Cache::put('foo', 'bar', 0.0001) and Cache::getStore()->put('foo', 'bar', 0.0001) and Cache::getStore()->put('foo', 'bar', '0') in Laravel <= 5.2 mean cache forever, except
- DatabaseStore and FileStore: caches for 0 second.
- RedisStore: cache for 1min or 1sec, depending on if #13810 is applied.
In Laravel 5.3, Cache::put('foo', 'bar', 0.0001) and Cache::getStore('foo', 'bar', 0.0001) and Cache::getStore('foo', 'bar', '0') means cache forever except:
- for DatabaseStore: caches for 0 second.
- for Redis store: cache for 1min or 1sec, depending on if #13810 is applied.
- for FileStore: cache for 0 second.
In summary
It was a headache. And the headache is doubled by me :( There could be more breaking changes.
Lets think of a solution that helps us. Another breaking change is required!
Solution 1
Let Cache::put('foo', 'bar', $x), and Cache::getStore()->put('foo', 'bar', $x) mean don't cache if and only if (int) ($x * 60) < 1
And Cache::put('foo', 'bar', INF), and Cache::getStore()->put('foo', 'bar', INF) mean cache forever.
Solution 2
Using integer $seconds instead of $minutes in all the APIs and let `Cache::put('foo', 'bar', 0) mean cache forever across different cache stores.
Solution 3
Revert my changes, but make different cache stores behave the same. Namely fix DatabasStore and RedisStore.
I will try solution 1.

Yes, we have made breaking changes. Laravel does not follow semver. Each minor version is like a sever major version.

If we broke something in L5.2, please send a PR with whatever fix you see most appropriate, and we can take it from there. We can then discuss the finalizations to L5.3, if more changes are needed there.

So breaking change is OK, but the situation is not still OK for L5.3. Another bad thing is here: putMany() still does not support seconds.
If opening issues for the next version is not allowed, then this should be closed, otherwise it needs to remain open. @GrahamCampbell

    public function put($key, $value, $minutes = null)
    {
        if (is_array($key) && filter_var($value, FILTER_VALIDATE_INT) !== false) {
            return $this->putMany($key, $value);
        }
        ...

If opening issues for the next version is not allowed

Not at all! Please do let us know if we mess up on any version 5.1 or greater.

but the situation is not still OK for L5.3. Another bad thing is here: putMany() still does not support seconds.

Ah, ok, I see. Please could you send a PR to L5.3 to fix this please?


provide a better wallet_auth_key prefix

currently wallet uses a user-defined prefix for the key in LocalStorage
note:
undefined_ wallet_auth_key
{
  "undefined_wallet_auth_key": {"accountId":"sherif-demo.testnet","allKeys":["ed25519:Azqg7VBLGYo8LdiJ4SEzgodg3JXANoJm8jbH1homoVj6"]}
}

this could be improved with a more friendly default value for appKeyPrefix
https://github.com/near/near-api-js/blob/25e7e60203965aee062ca19f352ff765859896ef/src/wallet-account.ts#L28

@stefanopepe does this sound like a change that will break Wallet or have concerns with this?

We are re-designing the key management, and we'll start working on it in the next sprint. The UX will probably include a way for the user to append notes/memorable information to each key, but I don't have more information to share right now.
Roping in @MaximusHaximus for an estimation of the changes

I did an audit, and I don't believe that we reference this _wallet_auth_key localstorage value anywhere in the wallet codebase directly.  As a result, as long as long as near-api-js handles backwards compatibility internally for anything that relies on it in near-api-js, it shouldn't have any impact on the wallet as far as I can tell. :)


mvn compile error.

Expected behavior
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:get (get-jetty-alpn-agent) on project netty-parent: Couldn't download artifact: Unable to get dependency information for org.mortbay.jetty.alpn:jetty-alpn-agent:jar:2.0.6: Failed to retrieve POM for org.mortbay.jetty.alpn:jetty-alpn-agent:jar:2.0.6: Could not transfer artifact org.mortbay.jetty.alpn:jetty-alpn-agent:pom:2.0.6 from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Actual behavior
Steps to reproduce
Minimal yet complete reproducer code (or URL to code)
Netty version
JVM version (e.g. java -version)
java version "1.8.0_73"
OS version (e.g. uname -a)
Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64

I fixed it by myself.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:unpack-dependencies (unpack) on project netty-transport-native-kqueue: Artifact has not been packaged yet. When used on reactor artifact, unpack should be executed after packaging: see MDEP-98. -> [Help 1]
I also get this .and fix it with this method:https://github.com/netty/netty/issues/7101

Ok then let me close this as duplicate of #7101


Ensure /var/lib/puppet is owned by user puppet

If /var/lib/puppet is a host volume, by default it will be owned by root, and puppetserver will fail to start.

Sorry, restructuring is going to move this to Dockerfile, I missed this until now.

This should be fixed automatically by the build.


Fix panic when running cargo tree on a package with a cross compiled bindep

What does this PR try to resolve?
This is an attempt to close out @rukai's PR for #12358 and #10593 by adjusting the new integration test and resolving merge conflicts.
I have also separated the changes into atomic commits as per previous review.
How should we test and review this PR?
As I understand, the integration test that has been edited here is sufficient.
Additional information
I have confirmed the test artifact_dep_target_specified fails on master branch and succeeds on this branch.

For continuity, probably
r? weihanglo
Also note I have not re-added None if features_for != FeaturesFor::default() => features_for but would be open to creating another test to catch that case.

:umbrella: The latest upstream changes (presumably #14618) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably #14647) made this pull request unmergeable. Please resolve the merge conflicts.

@bors r+

:pushpin: Commit ed294ab4e7743454472b13119e110973ed4c56fd has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit ed294ab4e7743454472b13119e110973ed4c56fd with merge 1e5bad31649d3859e41385eee612c312b5a700b2...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 1e5bad31649d3859e41385eee612c312b5a700b2 to master...


Expanding test cases

We have some tests running in the CI, but since atom mapping could have so many corner cases I think it's valuable that we expand the tests for the atom mapper to more of these. This issue is intended at discussing which cases are desired to be tested. As far as I can think of, we would like to have at least the following tests that are related to protein/residue mutations.

Different capped AAs mapping. Some "key" cases and check that the mapped atoms are the expected ones.
Full protein mappings. Maybe a tyk2 with a mutated tyk2 or similar.
Mapping of proteins (or big molecules) on itself, we would expect every atom to be mapped.
Mapping big protein to small peptides/AAs or vice versa.

As usual more than coverage we want more test cases, so I think this is something somewhat desired. One caveat is that some of these tests could take a few minutes to make the whole mapping. But this could also be helpful to do benchmarking on our current implementation.

Just wanted to note that we are including some tests for multimeric protein component mappings in #47 , but while working on that I realize that we probably also want to have more tests at different levels.


[Issue]: Not being able to send an array of strings for operations that requires them as query params

Description
Sending an array of strings for one of the input's property for an operation is not being sent to the API server accordingly.
Moreover, looking at the debugTransport logs after making the request, the query param for the array of strings is non-existent. In other words, using the example below, someListsParam query param was not found the wg server is making the request to our api server.
I expected the client to properly convert and encode these query params accordingly before sending to the api server
Note:

storefront -> wg server (I can see it encoded the array of strings literally. Like encoding [, ], :, " for the array of strings
wg server -> api server (query param does not exist)

For example:

an operation that supports a query params, which accepts an array of string

paths:
     /some/path/userId/something:
       post:
            - name: someListsParam
               in: query
               required: false
               schema:
                    type: array
                    items:
                         type: string
            ...
            responses:
               "200":
                   description:  OK
           ...

Important note:

schemas were validated and generated using the openapi generator from openapi tools. I was also able to use the typescript-fetch from there to send an array of strings to the same consumed OAS yaml that we provide to the instrospection.

Reproduction

running wunderctl generate with the details below
using openapi (v1)

Version:
<EMAIL_ADDRESS>wundergraph.config.ts:
const someNamespace = introspect.openApi({
  apiNamespace: 'someNamespace',
  source: {
    kind: 'file',
    filePath: '../shared-bff/specs/aopenapiv3specification.yaml',
  },
  baseURL: 'https://someUrl.com/',
  statusCodeUnions: true,
  headers: (builder) =>
    builder.addClientRequestHeader('Authorization', 'Authorization'),
});

aopenapiv3specification.yaml:
paths:
     /some/path/userId/something:
       post:
            - name: someListsParam
               in: query
               required: false
               schema:
                    type: array
                    items:
                         type: string
            ...
            responses:
               "200":
                   description:  OK
           ...

I've tested this with openApiV2() and it seems to be working


jQuery getting stomped on

As was discussed over on SourceForge it looks like Wayback's use of jQuery is causing some problems because it uses an older version (v1.3.2) which can stomp on previously loaded versions, which can break functionality on the page. I think it may also interfere with any jQuery plugins that have already been installed.
I don’t know what the best solution is, but it seems to me there are (at least) four options:

From a brief search It looks like jQuery takes backwards compatibility pretty seriously. So if Wayback must have a jQuery dependency perhaps it could simply be upgraded to use the latest version.
It looks like it’s possible for multiple versions of jQuery to co-exist on the same page. So perhaps Wayback could be updated to use jQuery in this way, so that it doesn’t interfere with archived pages that also use jQuery?
Perhaps Wayback should test to see if jQuery could be loaded before re-loading it? This is what was recommended in a previous bug report
Perhaps Wayback doesn't need jQuery at all anymore?

Personally, I think 4 is probably the best option, to keep things as simple as possible. But it's not entirely clear to me why jQuery was added, and what it and the associated plugins, are currently used for.

I have started to look into this issue, and as far as I can tell there are two versions of jQuery in use in the GUI of OpenWayback. /WEB-INF/query/BubbleCalendar.jsp uses v1.4.2, while /WEB-INF/replay/Toolbar.jsp uses v.1.3.2. This alone could cause problems if the API of these versions differ.
The suggested solution 1 must rely on jQuery always being backwards compatible. If this holds true, I think that OpenWayback would not need to always have the latest version included. If a newer version of jQuery got loaded it would be compatible with the original OWB API, and things should work. If an older version got loaded we could have a problem, as it might not have all functionality that the OpenWayback code relies on. This solution probably can't be used to ensure proper operation.

It is indeed possible to run several versions of jQuery independently using "jQuery.noConflict()". The limitation is that the different versions of the library must be loaded in order from oldest to newest. The question is what happens when we load another version of the library. If using noConflict() requires at all versions must be referenced by its version number, this solution will fail when loading web pages with an older version of the jQuery library. If it is possible to mix noConflict() against the verison(s) that OpenWayback uses with ordinary reference within loaded web pages, solution 2 might work.

Solution 3 would not work, since the library loaded from the web page might be older than the one used by OpenWayback and might not include all required functionality.
Solution 4 is probably the best, but would require some work, and should probably exclude this fix from versjon 2.0.1

I think (2) should work, i.e. if within OpenWayback we only use a dedicated noConflict version of jQuery, and allow the archived page to load it's own jQuery however it wishes. I guess we'll need to test it to find out.

Have looked further into the problem, and it seems jQuery got a major overhaul in v 1.9.0 which makes this and newer versions partial incompatible with other versions. Versions from 2.x.x does not support IE 6, 7 and 8, so always using the newest version of jQuery is not a good solution for now.
If we decide on solution 2, we probably need to do a lot of testing to make (almost) sure that it works properly on all variants of usage of the different versions of jQuery in the archived web pages.
It might be less work to just look into how to replace the library.

I realized it's only Toolbar.jsp that has the risk of conflicting jQuery versions since it's the only jsp mixing in with replay. As far as I can tell, jQuery is only used the get element offset for mouseOver events.
I tried to reimplement the used functionality and then avoiding jQuery in Toolbar.jsp. I have made a pull request for it #210.
The implementation is based on this post: http://stackoverflow.com/a/21880020. Please have a look and validate as I'm no Javascript guru.

Fixed in PR #210


RE4 CRASH

Aafter I put dinput8.dll file inside game doc. it crash my game, BTW I dont think it happen because of GPU, myGPU is 3090 24G, it still Crash

I have the same problem( 4070 laptop

Not enough information. Re-open the issue once you supply the required information and logs as laid out in the issue template.
https://github.com/praydog/REFramework/blob/master/.github/ISSUE_TEMPLATE/bug_report.md

Hi, Thank you for your work!
I encountered the same issue as the creator of the post.
If i copy&paste the dinput8.dll inside the installation folder of resident evil 4 2023 and start the game, it crashes to dekstop everytime the 3. logo is finished (When the "orb" with the lighthning appears)
I can see the "REFramework" window stating its initializing
then its start flickering and when the "orb" logo sequenz starts -> crash
Without the dinput8.dll, the game is starting and running without problems
I didnt get any "reframework_crash.dmp" file though, only the re2_framework_log.txt
Here is a pic of the situation ingame, right before crashing:  https://ibb.co/2ysXqL2
Here is the the re2_framework_log.txt: https://github.com/LOWZONEDAYZ/RE4/blob/6102806143a8c5f601699fb42caf6414afaad880/re2_framework_log.txt
Would be nice to see your work in action, in my gameplay, so if if possible, i would like to ask if you could take a look
I hope you can see this post, after you closed the thread
Thank you
regards LC


Add Edit Link to Post Footer

Add Edit link (if own post) to bottom of post based on attached image in Trello Ticket

https://trello.com/c/OQ9wcT8J/314-edit-link-in-bottom-of-post

Before

After

It looks not aligned with the rest of text. I think we should have it aligned in the middle.
It takes a while to save draft (what is done before editing post), can we add loading state to this link? Like in this popover menu:

I'm not sure about this color. Isn't it to intrusive? Not sure if it was just for showcasing feature, or desired color @bonustrack

Yes the color of "Edit" should be grey similar than "Reply" color:

@Sekhmet  just updated the commit

edit should now be aligned, removed line-height, but kept vertical-align: top to align it.

Added Loading state, text should change into spinner when you click on text
Changed color to be exact same gray hex used in reply link

Loading icon is not aligned with other links. I think it would look better to just add loading icon instead of replacing text with it.

Posts can be edited only in 7 days from posting, there is logic behind it: https://github.com/busyorg/busy/blob/new-design/src/components/Story/StoryFull.js#L160

@bonustrack should we remove edit post menu item from popover menu?

@Sekhmet shold we include an icon next to 'Edit' text similar to the one in poperover menu? That way loading can replace that icon instead of text?

I think that might look good. Now it kinda looks that Edit has share icon. Not sure how this will look like with two icons one after another though.

We can keep both edit for now (in bottom and popoer menu).

The reblog icon will not be visible in near future on the feed for our own post. It should be less confusing with Edit.

@Sekhmet Added edit icon & used same __link less styles as all other links in footer

loading should be aligned too

Did you see the link "Edit" does not have the same color than the icon or other links:

@bonustrack what page? on hover the edit link has the purple color, but not on hover it has same color

What Fabien means is that this link has wrong color #737fc4 but should have #3e4a9a.

vs

@Sekhmet did you mean #4757b2? I couldn't find 3e4a9a but #4757b2 is defined as @purple in custom.less

Yeah. Sorry, must have copied wrong one.

@Sekhmet alright updated it to use the @purple on hover from the less constants file


Bcast scalar improvement by constructing scalar tile in kernel

Removes need from users to preconstruct scalar tile. We'd just write 1 single value into a CB.
Would also help some other ops like the binop_tied_to_unary and other composite ops, so that they aren't creating/sending tile to device each run.

@tt-aho is still outstanding ?

Support added in 7c65c017a2d42ebfa805f767ed4ba7c9ac9a28a2


Change timestamp from UTC to NZST

This appears to be the only place displayed here

Fixed it up on the signature display too.


suse: wrap crono with the exec command

This way signals sent to bash are properly propagated to crono.
bnc#976113
Signed-off-by: Miquel Sabaté Solà<EMAIL_ADDRESS>

LGTM


huggingface: Support for HuggingFacePipeline in ChatHuggingFace.

Description: Added support for using HuggingFacePipeline in ChatHuggingFace (previously it was only usable with API endpoints, probably by oversight).
Issue: #19997
Dependencies: none
Twitter handle: none

That is a good idea. I added an example, including also a short excerpt of how one can pass in a quantization config. That should be helpful, I think.


Manage devices/ serial console

Author Name: Arnold Bechtoldt (Arnold Bechtoldt)
Original Redmine Issue: 3411, https://dev.opennebula.org/issues/3411
Original Date: 2014-12-05

I have the following RAW data added to the VM templates which are used to instantiate KVMs. It would be great to have those settings available in the user interface of template management in Sunstone/ template.
btw: One advantage having serial consoles attached to KVMs is to have a backup access to these KVMs in case direct network access isn't possible.
<devices>
    <memballoon model="none" />
    <serial type="pty">
        <source path="/dev/pts/5" />
        <target port="0" />
    </serial>
    <console type="pty" tty="/dev/pts/5">
        <source path="/dev/pts/5" />
        <target port="0" />
    </console>
</devices>

Original Redmine Comment
Author Name: Ruben S. Montero (@rsmontero)
Original Date: 2014-12-08T20:59:57Z

Probably you already know it, but till this get implemented you can add it to vmm_exec_kvm.conf. Just uncomment the RAW file, it already includes the serial code...


fix(@toss/validators): Increase the accuracy of verification for isBirthDate6

Overview
[ What did i do ]
According to the Gregorian calendar, there are months when 30 or 31 days do not exist. For example, February 30 and April 31.
The current "isBirthDate6" is not responsible for this, even though it is a function to verify the correct date of birth. So I've supplemented this.
[ AS-IS ]

[ TO-BE ]
expect(isBirthDate6('950230')).toEqual(false);
expect(isBirthDate6('950431')).toEqual(false);

PR Checklist

[X] I read and included theses actions below

I have read the Contributing Guide
I have written documents and tests, if needed.

Hello @po4tion, thanks for your contribution.
In my opinion, the best way to handle this is using the proper date library, since Dates are hard to handle properly. If we were to use date-fns, we might have used:
import { parse, isValid } from 'date-fns';

const parsed = parse(date, "yyMMdd", new Date());
return isValid(parsed);

How about using the proper library instead of implementing the validation logic ourselves?

@raon0211 That's an incredible speed. Your addition was helpful, thank you!


(BKR-148) Stop vagrant from generating ssh key

Hashicorp added new behavior that generates a new SSH key
when generating a box, and will remove any existing "insecure"
key found on a box. See https://github.com/mitchellh/vagrant/pull/4707
This has the unfortunate side effect of breaking the automation
used in Beaker to setup SSH keys, since it relied on the default
"insecure" vagrant keys being used. This workaround disables
the new Vagrant behavior with the ssh.insert_key = false config option.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/640/
:red_circle: Test failed.

Any updates on this? Beaker is completely broken for me while using the Vagrant provider. :/

Patch broke spec testing:
Failures:

Beaker::Vagrant can make a Vagrantfile for a set of hosts
Failure/Error: expect( vagrantfile ).to be === <<-EOF
expected: === "Vagrant.configure("2") do |c|\n  c.vm.define 'vm1' do |v|\n    v.vm.hostname = 'vm1'\n    v.vm.box = 'vm1_of_my_box'\n    v.vm.box_url = 'http://address.for.my.box.vm1'\n    v.vm.box_check_update = 'true'\n    v.vm.network :private_network, ip: "ip.address.for.vm1", :netmask => "<IP_ADDRESS>", :mac => "0123456789"\n    v.vm.provider :virtualbox do |vb|\n      vb.customize ['modifyvm', :id, '--memory', '1024']\n    end\n  end\n  c.vm.define 'vm2' do |v|\n    v.vm.hostname = 'vm2'\n    v.vm.box = 'vm2_of_my_box'\n    v.vm.box_url = 'http://address.for.my.box.vm2'\n    v.vm.box_check_update = 'true'\n    v.vm.network :private_network, ip: "ip.address.for.vm2", :netmask => "<IP_ADDRESS>", :mac => "0123456789"\n    v.vm.provider :virtualbox do |vb|\n      vb.customize ['modifyvm', :id, '--memory', '1024']\n    end\n  end\n  c.vm.define 'vm3' do |v|\n    v.vm.hostname = 'vm3'\n    v.vm.box = 'vm3_of_my_box'\n    v.vm.box_url = 'http://address.for.my.box.vm3'\n    v.vm.box_check_update = 'true'\n    v.vm.network :private_network, ip: "ip.address.for.vm3", :netmask => "<IP_ADDRESS>", :mac => "0123456789"\n    v.vm.provider :virtualbox do |vb|\n      vb.customize ['modifyvm', :id, '--memory', '1024']\n    end\n  end\nend\n"
got:     "Vagrant.configure("2") do |c|\n  c.ssh.insert_key = false\n  c.vm.define 'vm1' do |v|\n    v.vm.hostname = 'vm1'\n    v.vm.box = 'vm1_of_my_box'\n    v.vm.box_url = 'http://address.for.my.box.vm1'\n    v.vm.box_check_update = 'true'\n    v.vm.network :private_network, ip: "ip.address.for.vm1", :netmask => "<IP_ADDRESS>", :mac => "0123456789"\n    v.vm.provider :virtualbox do |vb|\n      vb.customize ['modifyvm', :id, '--memory', '1024']\n    end\n  end\n  c.vm.define 'vm2' do |v|\n    v.vm.hostname = 'vm2'\n    v.vm.box = 'vm2_of_my_box'\n    v.vm.box_url = 'http://address.for.my.box.vm2'\n    v.vm.box_check_update = 'true'\n    v.vm.network :private_network, ip: "ip.address.for.vm2", :netmask => "<IP_ADDRESS>", :mac => "0123456789"\n    v.vm.provider :virtualbox do |vb|\n      vb.customize ['modifyvm', :id, '--memory', '1024']\n    end\n  end\n  c.vm.define 'vm3' do |v|\n    v.vm.hostname = 'vm3'\n    v.vm.box = 'vm3_of_my_box'\n    v.vm.box_url = 'http://address.for.my.box.vm3'\n    v.vm.box_check_update = 'true'\n    v.vm.network :private_network, ip: "ip.address.for.vm3", :netmask => "<IP_ADDRESS>", :mac => "0123456789"\n    v.vm.provider :virtualbox do |vb|\n      vb.customize ['modifyvm', :id, '--memory', '1024']\n    end\n  end\nend\n"
./spec/beaker/hypervisor/vagrant_spec.rb:35:in `block (2 levels) in module:Beaker'

Also, the commit message needs to be of the form (BKR-xxx) to associate it with an open bug.

@anodelman Got it, I'll find/open a ticket and update the specs. Thanks!

@anodelman Updated commit with issue number, updated spec tests and verified they run locally. Sorry, I forgot to try them out originally.

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/643/
:green_heart: Test passed.

Is this change backwards compatible?

@anodelman I haven't tested it, but Vagrant claims that config changes are backwards compatible within the configuration version, and version 2 is compatible with 1.0/1.1. http://docs.vagrantup.com/v2/vagrantfile/version.html I would assume that earlier versions aren't aware of the config value, and thus wouldn't bother checking it?


is visible?

Should probably consider adding queries to the view service for "is this layer visible" and "is this feature visible?"
this probably needs discussion on whether or not this means, "is not hidden and is within the current map view's bounds"

The intent of the map.get (we are adding better documentation for this) channel is to be able to perform queries on overlays and features to get status of properties such as visibility.  The visible property indicates a Boolean stat of on / off - not taking into consideration if it is within the geo-spatial view of the current map.
The ability to perform geo-spatial queries in CMAPI is currently out of scope for 1.3.0 but geo queries could created by someone as an extension and considered in future versions.

There does not appear to be a standardized 'visibility' property on overlays or features.  So this approach will only facilitate interoperability if everyone just happens to use the same property name to mean 'layer is not selected for display in map'.  I also noticed that the documentation for the filter property is lacking.  You have to read the examples to understand that the name/value pairs of a filter object are named 'property' and 'term' and that when multiple filters are supplied in the filters array that they are ANDed together vice ORed.
This is a capability that my map has via a non-standard channel and I'm interested in doing this the CMAPI way once everything is spec'd out a little better.

@spyhunter99 @truff
Updates have been made to the map.get documentation to clarify these issues.  the map.get filter attribute now properly documents the use case and have a visible specific portion tot he documentation.  Please take a look online at: http://cmapi.org/versions/v1.3.0/docs/index.html#map.get and let us know if you have any additional feedback to make this better.

This looks good to me as far as visibility is concerned.  Not sure if there are any other property names that it would be useful to standardize on.

thanks Eric, i'll catch you on the next telcon


chore: update vault list

Description
Updates vault list for underlying tokens on the coingecko list so we have market data for them.
Notice
Before submitting a pull request, please make sure you have answered the following:

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Do all new and existing tests pass? Does the linter pass?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[x] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
If applicable, please link to the github issue and put closes #XXXX in your comment to auto-close the issue that your PR fixes.
Testing
Please outline all testing steps

Pull branch locally and run yarn to install new deps
etc...

Screenshots (if applicable)

🍭


Replaced progress Dialog with material design progress Bar

Hey @pawank0411 ,
I've replaced the progress dialog with a material design progress bar
Please let me know whether this PR meets your expectations or if you need any changes.
Thank you

@abdulbasit75 Amazing work. 👍
Thank you for your contritubution


Migrated to Swift 4.0

Checklist

[x] I've checked that all new and existing tests pass
[x] I've updated the documentation if necessary
[x] I've added an entry in the CHANGELOG to credit myself

Description

Motivation and Context

Need to test on my fork first


file drag & drop zone

In my app I would like to support file input by dragging and dropping a file into a drop zone. Is this already possible or being considered as a feature to add?

I think it's doable. There is an issue for that already: https://github.com/flet-dev/flet/issues/112
I'm closing this one as a duplicate.


C program to sort names in alphabetical order

User has to enter number of names, and those names are required to be sorted in alphabetical order with the help of strcpy() function.
for example (output):
Enter number of names:
5
Enter names in any order:
Pinky
Lucky
Ram
Appu
Bob
The sorted order of names is:
Appu
Bob
Lucky
Pinky
Ram

@RishitaChourey  you have already been assigned an issue. You can work only on 1 issue at a time. Once you complete it you may work on this issue if no one else comments on it.

I am Aastha Thorat from SY Comp.
I would like to solve this issue.

@Aastha83 all the issues labeled easy are only for FY's. You can try the medium and hard level issues

@isha0904 ,Yes you can. Upload you solution in the "Solutions" folder by 26 March'23, 11:59pm

Closed


GPU product node label supports only one product type

Describe the bug
gpu.intel.com/product only supports one type, such as 'Flex_140' or 'Flex_170'; in the case when both types of cards are installed only 'Flex_140' will be written as the label value (due to order in https://github.com/intel/intel-device-plugins-for-kubernetes/blob/main/deployments/nfd/overlays/node-feature-rules/platform-labeling-rules.yaml). This is important when selecting for differing pod preferences, ie a pod may have better performance on Flex 170 than Flex 140, so an affinity for scheduling for nodes with Flex 170 is preferred. Other logic may handle the actual consumption of that resource.
To Reproduce
Steps to reproduce the behavior:

Node has Flex 140 card installed and Flex 170 card installed
Device plugins is installed per instructions
apply platform-labeling-rules.yaml
Only gpu.intel.com/product=Flex_140 is in labels

Expected behavior
The values for gpu.intel.com/product should follow the other labelled values, such as gpu.intel.com/device-id.0380-56c0.present=true or
gpu.intel.com/device-id.0380-56c1.present=true. At present, pods may select for these labels, which are not transparent to Intel product naming. Suggest something like gpu.intel.com/product.Flex_140.present=true etc. which could indicate any presence of commonly understood Intel GPU product names.
System (please complete the following information):

OpenShift 4.13.11
Device plugins version: v0.28.0
Hardware info: SPR with Flex 140 + Flex 170 in same system

Additional context
n/a

Hi @brgavino
The GPU plugin is supposed to be run on homogeneous nodes (only one type of GPU). As both cards appear as same resource (gpu.intel.com/i915), you wouldn't be able to assign Pods to different GPUs on the same node regardless of the node's labels. Given the constraints, the gpu.intel.com/product works as specified.
Does your use case demand having different types of GPUs running on the same node?

It is common to have two types of GPUs mixed in usage, when this node or a cluster is supposed to support different workloads. GAS should have a way to differentiate 170 and 140, which may be better and more cost-efficient than the other one. While the formal solution may take a long time, can we have a quick workaround?

If you are referring to GPU Aware Scheduling with GAS, it states in its README that it expects cluster to be homogeneous.
I'm sorry, but I don't think there are quick workarounds for this. Unless you consider to reconfiguring the cluster to only have one type of GPU per node.
For not-so-quick solutions, we could name the resource by product type. But that leads to Pod specs having wrong resource requests.

One way that we have considered this is to present a stand-in, such as requesting memory.max that will be larger than one card/tile type. For the case of sharedDevNum=1, Flex170 has more available memory (16G vs 12G total on Flex140), there should be no possibility to request another card type. In any case, heterogenous  GPU has two areas to address, in this case the node labelling should be extensible anyways - the choice to pick the last label in the NFD rules isn't suitable for edge deployments. I'll most likely create an issue in GAS repo as well with this reference.

"For not-so-quick solutions, we could name the resource by product type."
Can we have multiple labels for one resource? For example, keep the resource name the same and add another label for the type.

"For not-so-quick solutions, we could name the resource by product type." Can we have multiple labels for one resource? For example, keep the resource name the same and add another label for the type.

I'm not sure I understand.  Resource is what is requested by the pod, and what the devices are associate with.  Whereas labels are associated only with nodes (not devices), and used by k8s scheduler for limiting set of eligible nodes for running given pod.
Or did you meant annotating the pod for GAS?

One way that we have considered this is to present a stand-in, such as requesting memory.max that will be larger than one card/tile type. For the case of sharedDevNum=1, Flex170 has more available memory (16G vs 12G total on Flex140), there should be no possibility to request another card type.

Your thought process is valid, but that's not how GAS works. As it assumes the nodes to be homogeneous, the "memory.max" value is divided between the GPUs. For a node with Flex 170 and Flex 140 cards, it would consider each card to have ~9.3GB of memory (16+6+6)/3.
But. Since this problem seems to be a recurring thing, either multiple dGPUs or iGPU + dGPU, I have planned to implement an alternative resource naming method. There user would be able to provide a "pci device id" to "resource name" mapping. Any GPUs on the mapping would get renamed and the ones not on the mapping would be registered via the default name. It will have down sides: GAS would not support it and Pod specs would need adaptation. Maybe something else as well.
Opinions are welcome.

Sounds good to me.
While GAS could use the same PCI ID <-> resource name mapping (if it's specified e.g. in a shared/secured configMap) to know about the devices, adding support for per-node devices with different amount of resource could be very large effort.  Probably better to handle that with DRA driver.  @uniemimu ?

Correct me if I got this wrong - The problem seems a limitation of the naming of Flex GPU in the NFD. It cannot tell two types (or more types) of GPU nodes in one server node. So GAS cannot schedule the pod to use a specific type of GPU. Adding resource name mapping seems a little bit overkill in this case -- how many resources would be needed?

Correct me if I got this wrong - The problem seems a limitation of the naming of Flex GPU in the NFD. It cannot tell two types (or more types) of GPU nodes in one server node. So GAS cannot schedule the pod to use a specific type of GPU. Adding resource name mapping seems a little bit overkill in this case -- how many resources would be needed?

It's not about the labels. Let's say we had the labels correct in a sense you'd like them to be. A node has two GPUs Flex 140 and Flex 170:
gpu.intel.com/product.Flex_140=1
gpu.intel.com/product.Flex_170=1

The pod spec would declare nodeAffinity to gpu.intel.com/product.Flex_170. During scheduling scheduler selects the node with the correct label and GPU plugin is called to allocate a GPU. GPU plugin selects either of the possible GPUs because the i915 resource equals any of them. The container gets a Flex 140 GPU or Flex 170 GPU. The label on the node or the nodeAffinity in the Pod spec doesn't change the way the GPU plugin selects the GPU during allocate.
GAS doesn't help either, because it only pre-selects the GPU to use by analyzing the extended resources (mllicores, memory.max). GAS doesn't know if card0 is Flex 140 or Flex 170. Though, it would be possible to add that kind of support by extending the node labels etc.

Sounds good to me.
While GAS could use the same PCI ID <-> resource name mapping (if it's specified e.g. in a shared/secured configMap) to know about the devices, adding support for per-node devices with different amount of resource could be very large effort. Probably better to handle that with DRA driver. @uniemimu ?

It does look like the DRA driver would be a better fit in the long term. Based on the discussion here, it seems that DRA is the preferred path forward and the device plugins for GPU are legacy and may not get / be worth implementing such features?

GAS doesn't help either, because it only pre-selects the GPU to use by analyzing the extended resources (mllicores, memory.max). GAS doesn't know if card0 is Flex 140 or Flex 170. Though, it would be possible to add that kind of support by extending the node labels etc.

Right; Dividing the memory.max up equally can't help steer workloads on heterogenous hardware configs (current implementation) and there's no way to ask for affinity for devices at the pod level - or for cards to avoid per node in node selectors, taints, etc. So even if the labels were extended, GAS would need to support the label parsing logic to select the right resources based on the pod labels, for example.
The high level story here, though, is that "As a GPU workload, I need to pick the type of GPU I land on". Other questions on specific resources requests seems handled by DRA.

It does look like the DRA driver would be a better fit in the long term. Based on the discussion here, it seems that DRA is the preferred path forward and the device plugins for GPU are legacy and may not get / be worth implementing such features?

I believe DRA is the way forward, but it is still alpha in K8s 1.29 and requires a feature flag to work. So device plugins will still be around for quite some time.
As your request is not alone, I am leaning towards adding the necessary logic to allow user to rename the GPU resources based on the GPU type. It might hit our next release (~April) depending on how much time I can steal from my other tasks.

Hi, @tkatila , Thanks for your explanations!
Now I get the picture. To summarize, the affinity preference (gpu_type) of a pod level becomes useless after the pod is scheduled to a server node - because the GPU plugins or GAS cannot differentiate the gpu_type of each GPU device in the server.
Regarding your solution -- a "pci device id" to "resource name" mapping, do you mean something like pci_device_id to "gpu_type" mapping?

Regarding your solution -- a "pci device id" to "resource name" mapping, do you mean something like pci_device_id to "gpu_type" mapping?

Yes. Plugin would read device's PCI ID and then based on it apply the default or a custom resource name to it. For example, one could rename an integrated TGL GPU as "gpu.intel.com/i915-tgl" or a Flex 170 (56c0) as "gpu.intel.com/i915-flex170". The editable part would be the "i915" postfix, we need to keep the namespace as it is.
I think it would also make sense to provide example mappings for some of the cases.

Yes. The proposal makes sense. Thanks!

Another couple of items, that we may want to look at (if these should be tracked as feature requests elsewhere, please let me know):

memory.max is split equally, not on actual card capability -> This can cause some issues even when we get the right device type, cards can be overscheduled
device-id.**.count incorrectly lists type count when different cards are deployed -> ex) gpu.intel.com/device-id.0380-56c1.count: '3' but there is 1 Flex 140 card installed and 1 Flex 170 card installed (missing 56c0, and added to 56c1)

memory.max is split equally, not on actual card capability -> This can cause some issues even when we get the right device type, cards can be overscheduled

AFAIK that's not going to change. These extended resources are intended to be used with GAS, and it is supposed to only work with homogeneous clusters and it will most likely stay like that.

device-id.**.count incorrectly lists type count when different cards are deployed -> ex) gpu.intel.com/device-id.0380-56c1.count: '3' but there is 1 Flex 140 card installed and 1 Flex 170 card installed (missing 56c0, and added to 56c1)

Yep. That's because the NFD rule counts devices based on their pci class (0380). And the name of the label is taken from the "first" pci device on the list. The good thing is that it's dynamic, so it works most of the times and for all devices. If we'd want to have counts per GPU type, we'll have to add per GPU (device id) rules. It's probably ok to add that for 0380 class devices as there is a limited amount of them. For 0300 the list would be too long.


赵旭东-Never Settle.

Always believe that something wonderful is about to happen.

Level 1终于完成了。唯一的不同，是处处不同。


operator metallb-operator (0.13.3)

Adding the latest version of the operator

/merge possible

/merge possible


add akrherz as maintainer, bump build

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Lets see what happens here :)
@conda-forge-admin, please rerender
refs conda-forge/wgrib2-feedstock#24

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@ocefpaf I'm at a loss as to why this isn't working?  Any ideas?

No idea. We should try to build the old version first just to check if it is changes in our compilers, etc or if it is the new version.

holy cow @ocefpaf , amazing.  We'll still have windows troubles though :(

holy cow @ocefpaf , amazing.

Had to build it locally, unpack the broken package, and see that we had a bin file instead of a directory :-/

We'll still have windows troubles though :(

We may need to restore the mingw-c compiler. I'm not sure...

with mingw-c we get
2022-12-19T18:36:32.0707638Z wgrib_main.c: In function 'main':
2022-12-19T18:36:32.0708945Z wgrib_main.c:505:5: internal compiler error: Segmentation fault
2022-12-19T18:36:32.0709805Z      0.001*GDS_LatLon_La1(gds), 0.001*GDS_LatLon_La2(gds),
2022-12-19T18:36:32.0710428Z      ^
2022-12-19T18:36:32.0711873Z libbacktrace could not find executable to open
2022-12-19T18:36:32.0712700Z Please submit a full bug report,

I'm OK skipping Windows BTW.

anaconda.org reported download counts

Arch
Downloads

win-64/wgrib-<IP_ADDRESS>c-h301d43c_0.tar.bz2
1285

osx-64/wgrib-<IP_ADDRESS>c-h01d97ff_0.tar.bz2
396

linux-64/wgrib-<IP_ADDRESS>c-h516909a_0.tar.bz2
5380

I'm fine with dropping windows. :)

windows fails with
Mamba failed to solve:
 - m2w64_c_win-64
 - m2-make
with channels:

The reported errors are:
   - nothing provides requested m2w64_c_win-64

@conda-forge-admin, please rerender

anaconda.org reported download counts

B/c wgrib is not used as a dependency anywhere those are probably real user and, 1285, is impressive for such a niche package. With that said, the previous build seems to be working on Windows and dropping here is not "never building it again", just waiting for someone who knows about Windows stuff to come along and help us fix it :-)

@ocefpaf GREEN!  Thank you!

I was going to add the basic shell utils on Windows but your solution is much better. Thanks!


Duplicate class com.genymotion.genyd.NetworkProfile$Status found in modules jetified-detox-18.20.2

I got this Exception when running "detox build --configuration android.emu.debug". How to solve it?
My environment:
"detox": "^18.20.2",
"jest": "^26.6.0",
com.android.tools.build:gradle:4.0.2
org.jetbrains.kotlin:kotlin-gradle-plugin:1.4.21

Task :app:checkDebugAndroidTestDuplicateClasses FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:checkDebugAndroidTestDuplicateClasses'.
1 exception was raised by workers:
java.lang.RuntimeException: java.lang.RuntimeException: Duplicate class com.genymotion.api.Battery found in modules jetified-detox-18.20.2-runtime.jar (com.wix:detox:18.20.2) and jetified-genymotion-api-1.2.0.jar (genymotion-api-1.2.0.jar)
Duplicate class com.genymotion.api.Battery$1 found in modules jetified-detox-18.20.2-runtime.jar (com.wix:detox:18.20.2) and jetified-genymotion-api-1.2.0.jar (genymotion-api-1.2.0.jar)
Duplicate class com.genymotion.api.Battery$2 found in modules jetified-detox-18.20.2-runtime.jar (com.wix:detox:18.20.2) and jetified-genymotion-api-1.2.0.jar (genymotion-api-1.2.0.jar)
Duplicate class com.genymotion.api.Battery$Mode found in modules jetified-detox-18.20.2-runtime.jar (com.wix:detox:18.20.2) and jetified-genymotion-api-1.2.0.jar (genymotion-api-1.2.0.jar)
Duplicate class com.genymotion.api.Battery$Status found in modules jetified-detox-18.20.2-runtime.jar (com.wix:detox:18.20.2) and jetified-genymotion-api-1.2.0.jar (genymotion-api-1.2.0.jar)
Duplicate class com.genymotion.api.DiskIO found in modules jetified-detox-18.20.2-runtime.jar (com.wix:detox:18.20.2) and jetified-genymotion-api-1.2.0.jar (genymotion-api-1.2.0.jar)
Duplicate class com.genymotion.api.GenydBinder found in modules jetified-detox-18.20.2-runtime.jar (com.wix:detox:18.20.2) and jetified-genymotion-api-1.2.0.jar (genymotion-api-1.2.0.jar)
Duplicate class com.genymotion.api.GenydBinder$1 found in modules jetified-detox-18.20.2-runtime.jar (com.wix:detox:18.20.2) and jetified-genymotion-api-1.2.0.jar (genymotion-api-1.2.0.jar)
Duplicate class com.genymotion.api.GenymotionException found in modules jetified-detox-18.20.2-runtime.jar (com.wix:detox:18.20.2) and jetified-genymotion-api-1.2.0.jar (genymotion-api-1.2.0.jar)
Duplicate class com.genymotion.api.GenymotionManager found in modules jetified-detox-18.20.2-runtime.jar (com.wix:detox:18.20.2) and jetified-genymotion-api-1.2.0.jar (genymotion-api-1.2.0.jar)
`

Hi, do you happen to have the genymotion API library jar included as a directly dependency in your project? If so, please have it removed (it comes bundled in with Detox).

I have to check if jetified-genymotion-api-1.2.0.jar in my company app is from same dependency as genymotion-api-1.2.0.jar in Detox. If both are the same, I will be able to remove dependency for jetified-genymotion-api-1.2.0.jar.
I have a work around for now by using detox 18.17.0 which doesn’t have genymotion-api-1.2.0.jar.

Indeed, Detox ships with genymotion-api-1.2.0.jar.

genymotion API is not directly included as a dependency in my project. Do you have other suggestion?
Can I remove genymotion-api-1.2.0.jar in Detox package?

I don't think so, because it is hard-wired into the Detox .aar.
You can try to exclude genymotion in gradle, more or less like so:
dependencies {
  	// ...
    androidTestImplementation(project(path: ":detox")) {
        exclude group: 'com.genymotion.api'
    }
}

Thanks @d4vidi I'm able to run the detox build without duplicate exception by adding exclude genymotion into android/app/build.gradle.
androidTestImplementation('com.wix:detox:+') {
       exclude group: 'com.genymotion.api'
 }

Great news!

I met the same issue.
According the guide Detox for Android, I thought it should add two line in app/build.gradle.  (I'm new for Android)
dependencies {
  	// ...
    androidTestImplementation('com.wix:detox:+')
    androidTestImplementation(project(path: ":detox"))
}

I fixed the issue by removing the first line.
Final code:
dependencies {
  	// ...
    androidTestImplementation(project(path: ":detox"))
}


Referencing leaseholder

Referencing leaseholder

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/79df141140ad167f4892db5d8ce679453b21b464/
Edited pages:

v19.1/topology-geo-partitioned-leaseholders.md

This is a good idea, but we use relative links in our docs. I'll make this change in a separate PR.


Resolve syncing conflicts from repo_sync_working_branch to master

Pull request opened by Docs to resolve syncing conflicts from repo_sync_working_branch to master.

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


Bug: $addMessageReactions is broken

Bug Type
Function
Bugged Behavior
bot.command({
  name: "test",
  code: `
    $addMessageReactions[$channelID;$messageID;✅;❎]
    `,
});

Version of aoi.js
v6.8.x
Version of Node.js
v22.5.1 (Current)
Excepted Output
add reaction to a message, but the message never gets sent anyway so
Relevant log output
TypeError: Cannot read properties of undefined (reading 'fnError')
at module.exports [as code] (c:\Users\LightslicerGP\node_modules\aoi.js\src\functions\addMessageReactions.js:26:58)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Interpreter (c:\Users\LightslicerGP\node_modules\aoi.js\src\core\interpreter.js:309:28)
Code of Conduct

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

no clue how nobody noticed this, fixing


Fix multi listener bug

fix: https://github.com/juzibot/donut-tester/issues/9

Thank you very much for the brilliant fix!


Assurance 2.0.0 with NullSafety support

@PravinPK  can you update the PR base branch to dev-2.0.0?


Fixes grpc tests on Windows

Signed-off-by: Sotiris Nanopoulos<EMAIL_ADDRESS>Commit Message:

Adds localhost to the upstreamcert.cfg
Makes fake_upstream TcpListenerSocket connect to the localhost instead of any address.
GRPC tests are no longer failing on windows.

Additional Description:
Risk Level: Low
Testing: N/A
Docs Changes:  N/A
Release Notes: N/A

@envoyproxy/windows-dev

@lizan I have format errors on the autogenerated files? Should I also fixed or should we ignore them from the formatting rule?

@davinci26 format check is required for all checked-in files regardless whether they are generated or not. run fix_format and you should be good.

@lizan  this is ready for another review


RFE: add options to implement /ignore

Perhaps to the logger configuration so that the logs can't contain almost useless join/parts/nicks/quits messages.
And/or to the log presentation web UI (perhaps via CSS classes) such that the log viewer can choose to enable/disable presentation of such messages.

So something like:
[logging]
events = ['privmsg']

Re "log viewer"; I guess kdb doesn't really have one yet :) See #31


Normal distribution curve

What problem does this feature solve?
Normal distribution used for most of the graphs if that be a inbuilt option thats is easy to use
What does the proposed API look like?
normal distribution

You can generate the normal distribution data. Like in example https://echarts.apache.org/examples/zh/editor.html?c=line-function


feat: add csscomb utility

Alaska Airlines Pull Request
Fixes: #83
Summary:
This change adds support for using cssComb to do format enforcement on CSS and SCSS files.
The .csscomb.json file included in the change defines the rules for formatting and grouping of CSS properties and values.
It is important to note that this tool does not do any lint enforcement. This tool is purely in place to enforce readability standards to improve development and maintainability.
You can read more about the cssComb tool here: https://github.com/csscomb/csscomb.js/
Type of change:
Please delete options that are not relevant.

[x] New capability
[ ] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

@blackfalcon I'm thinking about adding a little snippet to the readme.md file for this.
I have a separate ticket to add documentation for this to the AuroDocSite but a brief overview in the readme feels appropriate to me. I thought you may have a strong opinion about that so I wanted to get your thoughts first.

@geoffrich I am curious as to your opinion on this. The PR itself is ok, but I am having some concerns about adding support for this utility as the tools don't seem to have much support. The CSSComb site is not responding. There haven't been any updates in 2 years and there are a series of ignored PRs.
In the doc for this @jason-capsule42 stated that there are plug-ins for IDE and the repo for the VSCode plugin is archived. That is concerning.

@geoffrich I am curious as to your opinion on this. The PR itself is ok, but I am having some concerns about adding support for this utility as the tools don't seem to have much support. The CSSComb site is not responding. There haven't been any updates in 2 years and there are a series of ignored PRs.
In the doc for this @jason-capsule42 stated that there are plug-ins for IDE and the repo for the VSCode plugin is archived. That is concerning.

I actually just discovered that PostCSS has plugins for what we are looking for here:
**Better CSS Readability**
- Precss contains plugins for Sass-like features, like variables, nesting, and mixins.
- postcss-sorting sorts the content of rules and at-rules.
- postcss-utilities includes the most commonly used shortcuts and helpers.
- short adds and extends numerous shorthand properties.

https://github.com/postcss/postcss
With that in mind I suggest looking at including those PostCSS plugins in place of CSScomb since we already have PostCSS integrated.

It is concerning that the CSScomb repository appears to be in maintenance mode and their site is down.
+1 for using a PostCSS plugin if possible, since that's already integrated. It seems like a PostCSS plugin would be easier for us to fork and maintain if necessary.


CSV, TSV and JSON download options appear to be broken

After updating t2wml backend to the latest version on the development branch and the causx branch, looks like the download endpoint changed significantly.
I'm getting this error right now:
[2021-06-25 23:24:05,387] ERROR in app: Exception on /api/causx/project/download/csv/annotation_example.xlsx_output.csv [GET]
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/flask/app.py", line 2447, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python3.7/site-packages/flask/app.py", line 1952, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python3.7/site-packages/flask_cors/extension.py", line 165, in wrapped_function
    return cors_after_request(app.make_response(f(*args, **kwargs)))
  File "/usr/local/lib/python3.7/site-packages/flask/app.py", line 1821, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/lib/python3.7/site-packages/flask/_compat.py", line 39, in reraise
    raise value
  File "/usr/local/lib/python3.7/site-packages/flask/app.py", line 1950, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.7/site-packages/flask/app.py", line 1936, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/src/application.py", line 418, in download_results
    return send_file(data, attachment_filename, as_attachment=True, mimetype=mimetype_dict[filetype]), 200
TypeError: send_file() got multiple values for argument 'mimetype'

I was trying to debug this myself without any luck so far, @devowit could you take a look please?

can we close this as fixed now?


Rf/extract tagging utils

Needs to be merged after:
https://github.com/scality/Arsenal/pull/289

@ironman-machine go
SCALITY_ARSENAL_BRANCH=ft/taggingUtils

Hello @LaurenSpiegel
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_ARSENAL_BRANCH": "ft/taggingUtils", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "rf/extractTaggingUtils"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13837 for CI status.

end to end passed: http://ci.ironmann.io/gh/scality/Integration/13837


MNT: slaclab -> pcdshub

Closes #17
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

CI fails with SHA256 mismatch: '9c1d9c26c62778211152245c347959812476f376fb75fb40f14f411ccf9c34d2' != 'e408cc34d5a56ce149cc98c1843da2f99a795586c48dc1ef7431171d5b2611fa'
Was this supposed to be part of the re-render, or do we need to update the SHA manually in the recipe? I assume this is related to the repository migration

CI fails with SHA256 mismatch: '9c1d9c26c62778211152245c347959812476f376fb75fb40f14f411ccf9c34d2' != 'e408cc34d5a56ce149cc98c1843da2f99a795586c48dc1ef7431171d5b2611fa'
Was this supposed to be part of the re-render, or do we need to update the SHA manually in the recipe? I assume this is related to the repository migration

The SHA shouldn't have changed... 😕

The SHA shouldn't have changed... 😕

I think the test failure was in error: 9c1d9c26c62778211152245c347959812476f376fb75fb40f14f411ccf9c34d2 is what I get for both archives (slaclab, pcdshub)

I think the test failure was in error: 9c1d9c26c62778211152245c347959812476f376fb75fb40f14f411ccf9c34d2 is what I get for both archives (slaclab, pcdshub)

Looks like I swapped the SHAs in my head. It has indeed changed.

Looks like I swapped the SHAs in my head. It has indeed changed.

It is more likely that the sha changed before and it is not related with the change of ownership. The other repo that was migrated worked fine.

It is more likely that the sha changed before and it is not related with the change of ownership. The other repo that was migrated worked fine.

I'd guess it's the same issue you had previously encountered @hhslepicka
For psdm_qs_cli, I had a local copy of the old archive I could compare with the new one:

A little concerning, but at least it's not a malicious actor hijacking our packages. Merging.

I'd guess it's the same issue you had previously encountered @hhslepicka
For psdm_qs_cli, I had a local copy of the old archive I could compare with the new one:

A little concerning, but at least it's not a malicious actor hijacking our packages. Merging.