nawaff20120

Download
Markdown 1.0.1 (18 KB) -- 17 Dec 2004
Introduction
Markdown is a text-to-HTML conversion tool for web writers. Markdown
allows you to write using an easy-to-read, easy-to-write plain text
format, then convert it to structurally valid XHTML (or HTML).
Thus, "Markdown" is two things: (1) a plain text formatting syntax;
and (2) a software tool, written in Perl, that converts the plain text
formatting to HTML. See the Syntax page for details pertaining to
Markdown's formatting syntax. You can try it out, right now, using the
online Dingus.
The overriding design goal for Markdown's formatting syntax is to make
it as readable as possible. The idea is that a Markdown-formatted
document should be publishable as-is, as plain text, without looking
like it's been marked up with tags or formatting instructions. While
Markdown's syntax has been influenced by several existing text-to-HTML
filters, the single biggest source of inspiration for Markdown's
syntax is the format of plain text email.
The best way to get a feel for Markdown's formatting syntax is simply
to look at a Markdown-formatted document. For example, you can view
the Markdown source for the article text on this page here:
http://daringfireball.net/projects/markdown/index.text
(You can use this '.text' suffix trick to view the Markdown source for
the content of each of the pages in this section, e.g. the
Syntax and License pages.)
Markdown is free software, available under a BSD-style open source
license. See the [License] pl page for more information.
Discussion List
I've set up a public [mailing list for discussion about Markdown] ml.
Any topic related to Markdown -- both its formatting syntax and
its software -- is fair game for discussion. Anyone who is interested
is welcome to join.
It's my hope that the mailing list will lead to good ideas for future
improvements to Markdown.
Installation and Requirements
Markdown requires Perl 5.6.0 or later. Welcome to the 21st Century.
Markdown also requires the standard Perl library module [Digest::MD5]
md5, which is probably already installed on your server.
Movable Type
Markdown works with Movable Type version 2.6 or later (including
Movable Type 3.0).

Copy the "Markdown.pl" file into your Movable Type "plugins"
directory. The "plugins" directory should be in the same directory
as "mt.cgi"; if the "plugins" directory doesn't already exist, use
your FTP program to create it. Your installation should look like
this:
(mt home)/plugins/Markdown.pl

Once installed, Markdown will appear as an option in Movable Type's
Text Formatting pop-up menu. This is selectable on a per-post basis:

Markdown translates your posts to HTML when you publish; the posts
themselves are stored in your MT database in Markdown format.

If you also install SmartyPants 1.5 (or later), Markdown will
offer a second text formatting option: "Markdown With
SmartyPants". This option is the same as the regular "Markdown"
formatter, except that it automatically uses SmartyPants to create
typographically correct curly quotes, em-dashes, and ellipses. See
the SmartyPants web page for more information.

To make Markdown (or "Markdown With SmartyPants") your default
text formatting option for new posts, go to Weblog Config:
Preferences.

Note that by default, Markdown produces XHTML output. To configure
Markdown to produce HTML 4 output, see "Configuration", below.
Blosxom
Markdown works with Blosxom version 2.0 or later.

Rename the "Markdown.pl" plug-in to "Markdown" (case is
important). Movable Type requires plug-ins to have a ".pl"
extension; Blosxom forbids it.

Copy the "Markdown" plug-in file to your Blosxom plug-ins folder.
If you're not sure where your Blosxom plug-ins folder is, see the
Blosxom documentation for information.

That's it. The entries in your weblog will now automatically be
processed by Markdown.

If you'd like to apply Markdown formatting only to certain
posts, rather than all of them, Markdown can optionally be used in
conjunction with Blosxom's Meta plug-in. First, install the
Meta plug-in. Next, open the Markdown plug-in file in a text
editor, and set the configuration variable $g_blosxom_use_meta
to 1. Then, simply include a "meta-markup: Markdown" header line
at the top of each post you compose using Markdown.

BBEdit
Markdown works with BBEdit 6.1 or later on Mac OS X. It also works
with BBEdit 5.1 or later and MacPerl 5.6.1 on Mac OS 8.6 or later. If
you're running Mac OS X 10.2 (Jaguar), you may need to install the
Perl module [Digest::MD5] md5 from CPAN; Digest::MD5 comes
pre-installed on Mac OS X 10.3 (Panther).

Copy the "Markdown.pl" file to appropriate filters folder in your
"BBEdit Support" folder. On Mac OS X, this should be:
BBEdit Support/Unix Support/Unix Filters/

See the BBEdit documentation for more details on the location of
these folders.
You can rename "Markdown.pl" to whatever you wish.

That's it. To use Markdown, select some text in a BBEdit document,
then choose Markdown from the Filters sub-menu in the "#!" menu, or
the Filters floating palette

Configuration
By default, Markdown produces XHTML output for tags with empty elements.
E.g.:

Markdown can be configured to produce HTML-style tags; e.g.:

Movable Type
You need to use a special MTMarkdownOptions container tag in each
Movable Type template where you want HTML 4-style output:
<MTMarkdownOptions output='html4'>
    ... put your entry content here ...
</MTMarkdownOptions>

The easiest way to use MTMarkdownOptions is probably to put the
opening tag right after your  tag, and the closing tag right
before .
To suppress Markdown processing in a particular template, i.e. to
publish the raw Markdown-formatted text without translation into
(X)HTML, set the output attribute to 'raw':
<MTMarkdownOptions output='raw'>
    ... put your entry content here ...
</MTMarkdownOptions>

Command-Line
Use the --html4tags command-line switch to produce HTML output from a
Unix-style command line. E.g.:
% perl Markdown.pl --html4tags foo.text

Type perldoc Markdown.pl, or read the POD documentation within the
Markdown.pl source code for more information.
Acknowledgements
Aaron Swartz deserves a tremendous amount of credit for his feedback on the
design of Markdown's formatting syntax. Markdown is much better thanks
to Aaron's ideas, feedback, and testing. Also, Aaron's html2text
is a very handy (and free) utility for turning HTML into
Markdown-formatted plain text.
Nathaniel Irons, Dan Benjamin, Daniel Bogan, and Jason Perkins
also deserve thanks for their feedback.
Michel Fortin has ported Markdown to PHP; it's a splendid port, and highly recommended for anyone looking for a PHP implementation of Markdown.

Duplicate of #


Text not selectable after drag

It seems that you forgot to activate text selection again after the movement is completed.
On line 507 you deactivate it and it never gets activated again.
Adding
angular.element('body').unbind('selectstart' + eventNamespace);
in the "on mouseup" event fixes that.

Thanks a lot your solution fix my issue


Discuss using Kilrcode exercise as "Quickstart"

We have retained the "Quickstart" title in the docs for the old exercise which I don't think works.  For the Keptn-LTS docs, I'd like to remove that and rename the "Explore Keptn" exercise (https://keptn.sh/docs/explore/) to be QuickStart.
Does anyone object?  Please post opinions to this issue before the Community Meeting on Wednesday, 12 October or come to the meeting to discuss.  I hope we'll have a consensus by then so I can implement the change.

No objections from me

+1 from me. Maybe makes sense to archive it to a separate page or to add the disclaimer, but the Quickstart should only have the operational content

In the 12 October 2022 Community meeting, we discussed this and agreed to rename the kilrcoda exercise to be Quickstart.  See https://github.com/keptn/keptn.github.io/issues/1464


pixel LEDs flickering in Pixel example

I uploaded the pixel example on ESP32 WROOM and connected 16 WS2812B LEDs to pin 5.
It works well, but I notice flickering at brightness levels above 20%.
Additionally, sometimes when changing the color or brightness, some of the LEDs randomly switch to a color other than the one I set.

Once the pixels are lit there is no communication from the ESP32.  The pixels contain all the PWM logic to stay on as long as there is power.  If you are seeing flickering this suggests a power issue.  Are you trying to power directly from the pin or are you using a separate power supply.

Once the pixels are lit there is no communication from the ESP32. The pixels contain all the PWM logic to stay on as long as there is power. If you are seeing flickering this suggests a power issue. Are you trying to power directly from the pin or are you using a separate power supply.

I tried using both a separate power supply and the ESP pin, but got the same result.
I think if the issue were with the power, it shouldn't flicker at low brightness levels.
And checked with the FastLED library to make sure if the LEDs have a problem, and they work fine.

Did you use the exact Pixel example, completely unmodified, except that you changed this:
  SPAN_ACCESSORY("Neo RGB");
    new NeoPixel_RGB(NEOPIXEL_RGB_PIN,8);

to this:
  SPAN_ACCESSORY("Neo RGB");
    new NeoPixel_RGB(5,16);

Yes, I only changed the pin and number of LEDs.

Hmm.  I can't explain this.   As a check, once you set the color you should be able to disconnect pin 5 from the LED strip and nothing should change as long as the strip is still connected to power and ground.  This is an RGB device, not an RGBW, correct?  And to confirm, the flickering occurs only at bright levels?

Yes, and it is RGB.
No, flickering is noticeable at 20% brightness and more.

When you compare with FastLED and set the brightness high, are the levels equivalent?  That is, with FAST LED, you are not getting flickering at, say, 50%, but doe this look as bright as 50% using the Pixel library?
Does this only occur at certain colors?  A good test is to set the color to 100% Red (fully saturated).

I haven't compared the brightness levels yet, but I'll test it. I guess that the issue occurs at 20% brightness, which isn't at the full brightness capability of the LED. Yes, it flickers in all colors.

Can give it a try. I've not tried myself, so don't know if there are compatibility issues.

I just re-tested my kit with the all three types of pixels and can't seem to reproduce the flickering.  I am powering the NeoPixles using an external 5V power supply (i.e. NOT connected to the ESP32, except for ground), whereas the ESP32 itself is powered by through USB connector.  I have two different 5V supplies - one is 2A and the other 1A only.  When I use the 1A the LEDs are slightly dimmer, but still no flickering (at least none that I can see).  Are you powering with an external 5V supply (with at least 1A)?

I'm experiencing this too with a newly bought neopixel jewel RGBW model. Wondering if its something to do with the RGBW protocol for the LEDs - maybe thats different to the ordinary protocol that the Pixel lib is using.

Are you specifying RGBW when using the HomeSpan Pixel library (both RGB and RGBW are supported).

I just looked up the jewel on Adafruit and is seems to be just RGB, not RGBW.  However, they switched to the new WS2812B LEDs, which, according to the specs I can find on the web, use slightly different timing signals than the original WS2812.   The Pixel library allows you to specify custom timing signals.  Try adjusting the timing by calling the follows method on your Pixel object:
setTiming(0.40,  0.85,  0.80 , 0.45,  80);

Follow-up.  I went back to the Adafruit site and realized that the jewel does come in both RGB and RGBW flavors, so make sure you set the RGBW flag to either true or false depending on your model.

Are you powering with an external 5V supply (with at least 1A)?

Yes, it is 1A.

setTiming(0.40,  0.85,  0.80 , 0.45,  80);

Should I set it once in setup function?

It's a member function so you call it on each Pixel object after they are created. Once set for an instance of the object, it remains in place for all subsequent commands.

It's a member function so you call it on each Pixel object after they are created. Once set for an instance of the object, it remains in place for all subsequent commands.

like this?
    V.setRange(5, 100, 1);    // sets the range of the Brightness to be from a min of 5%, to a max of 100%, in steps of 1%
    pixel = new Pixel(pin);   // creates Pixel LED on specified pin
    this->nPixels = nPixels;  // save number of Pixels in this LED Strand
    pixel->setTiming(0.40, 0.85, 0.80, 0.45, 80);

    update();  // manually call update() to set pixel with restored initial values

Also, just to confirm, you've connected the ground from your power supply to ground on the ESP32?

Yes, the ground is common.

Yes, that's correct.  I'm not sure if this will address the flickering issue, but it will let us see if the problem is timing.
If it does not fix the issue, can you provide me with the exact model of the jewel neopixel you bought from Adafruit.  I'd like to get one as well so I can try to reproduce the issue and debug.

Aha, yes setting the is_rgbw flag did it for me - somehow I missed that in the docs. Hopefully it will solve for @imsadegh too

That's really good news.  Thanks for the update.

@imsadegh, did this solve your issue?

but it will let us see if the problem is timing

Changing the timing with the below code didn't work.
pixel->setTiming(0.40, 0.85, 0.80, 0.45, 80);
And this is my 4x4 RGB led buy link.

In another LED strip with 175 LEDs, it didn't flicks on all leds. But the colors are not correct after some random LEDs
This is the Strip LEDs after I set it to red with Siri. And these are Green and Blue.

Unfortunately I'm not sure how to debug this issue. What ESP are you using?

And to confirm, you checked you are using the correct flag for RGB versus RGBW?

What ESP are you using

It's ESP32 version 1, I also tried it with the ESP-C3 with the same result.
I just upload the code and connect the my ws2812B to the pin where in the code named RGB pin.

I wanted to try it with FastLED, But it was too complicated for me to implement.😅

I believe that the problem is caused by the timing.

I modified the code to work with the FastLed lib, This is the code:
#if defined(CONFIG_IDF_TARGET_ESP32)
#define NEOPIXEL_RGB_PIN 5
#define NEOPIXEL2_RGB_PIN 17
#define DEVICE_SUFFIX ""

#endif

#include "HomeSpan.h"
#include <FastLED.h>

struct NeoPixel_RGB : Service::LightBulb {
  Characteristic::On power{ 0, true };
  Characteristic::Hue H{ 0, true };
  Characteristic::Saturation S{ 0, true };
  Characteristic::Brightness V{ 100, true };
  CRGB *leds;
  uint8_t nPixels;

  NeoPixel_RGB(uint8_t pin, int nPixels)
    : Service::LightBulb() {
    V.setRange(5, 100, 1);

    FastLED.addLeds<WS2812B, NEOPIXEL_RGB_PIN, GRB>(leds, nPixels);
    this->nPixels = nPixels;

    update();
  }

  boolean update() override {
    int p = power.getNewVal();
    float h = H.getNewVal<float>();
    float s = S.getNewVal<float>();
    float v = V.getNewVal<float>();

    CRGB color = CHSV(h * p, s * p, v * p);
    fill_solid(leds, nPixels, color);
    FastLED.show();

    return (true);
  }
};

void setup() {
  Serial.begin(115200);

  homeSpan.setPairingCode("11122333");
  homeSpan.setQRID("111-22-333");
  homeSpan.setWifiCredentials("HDP", "11336699");
  homeSpan.begin(Category::Lighting, "Pixel RGB Hub" DEVICE_SUFFIX);

  SPAN_ACCESSORY();

  SPAN_ACCESSORY("RGB");
  new NeoPixel_RGB(NEOPIXEL_RGB_PIN, 350);
}

void loop() {
  homeSpan.poll();
}

After running it, it will keep resetting the ESP.


ColorPicker: update

Please makes sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

commit 说一下加了啥呗

done，并送动图一张。


State without being an entity

Amazing library. Currently everything in State has to be an Entity would be nice if objects could be synced.
Such as to sync:
{     gameState: 'ingame' | 'lobby';     timer: number; }

Thanks :smiley:
But, I'm not exactly sure what you mean.
Can you give me an example of what you're trying to achieve?

Sorry bad explanation - was late at night
export type State = Entity[]
export interface Entity {
  id: string
  [key: string]: Value
}

So State always has to be Entity[] example { id: 'heroBlue', x: 23, y: 14, z: 47 }, which has worked great for players. I'm wanting to sync data that isn't entity specific, such as timers, scores, etc.
It would be nice if we could have something like this:
export type State = Entity[] | { [key: string]: Value  }

const state: State = {
    players: [
        { id: 'heroBlue', x: 23, y: 14, z: 47 },
        { id: 'heroRed', x: 23, y: 14, z: 47 },
    ],
    timer: {
        timeLeft: 64,
    },
    score: {
        red: 0,
        blue: 2,
    }
}

Hmmm maybe I'm mistaken. And this shouldn't be part of the snapshot-interpolation library. And i just include this data in the snapshot packet.

Yes, if it does not have to be interpolated, you do not need to add it inside the snapshot.
You could do this:
const snapshot = SI.snapshot.create({
  players: [
    { id: 0, x: 17.5, y: -1.1 },
    { id: 1, x: 5.8, y: 18.9 }
  ]
})

const data = {
  snapshot: snapshot,
  timer: {
    timeLeft: 64,
  },
  score: {
    red: 0,
    blue: 2,
  }
}

// send data to the client


Mask credentials when logging Kafka producer and consumer configuration

When OMRS logs the Kafka producer and consumer configuration info, the sasl.jaas.config and ssl.truststore.password properties are in clear text.  These properties need to be hidden/masked.
The messages are defined in org.odpi.openmetadata.adapters.eventbus.topic.kafka.KafkaOpenMetadataTopicConnectorAuditCode.SERVICE_PRODUCER_PROPERTIES and SERVICE_CONSUMER_PROPERTIES, and are being logged by org.odpi.openmetadata.adapters.eventbus.topic.kafka.KafkaOpenMetadataEventConsumer and KafkaOpenMetadataEventProducer.
Here is an example of how the information is currently logged.  Note that the sasl.jaas.config and ssl.truststore.password properties are in clear text. :
[2/12/19 16:44:26:144 EST] 0000003f SystemOut O {"appname":"wdp-catalog","timestamp":"2019-02-12 16:44:26.144","transaction_ID":"","loglevel":"INFO ","thread":"lt Executor-thread-9","class":"OMRSAuditLog","method":"logRecord","line":"98","message":"1dd78413-6cea-444d-960b-c13e1c79204b_omag OCF-KAFKA-TOPIC-CONNECTOR-0003 The properties passed to the Apache Kafka Consumer for topic open-metadata.repository-services.cohort.dkantor_cohort.OMRSTopic are: {key.deserializer=org.apache.kafka.common.serialization.StringDeserializer, sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required username = "Rv0UMcFFz3B4impy" password = "iW8sQV2F9YRzSqdc9dEJKjkDw6uKE54y";, value.deserializer=org.apache.kafka.common.serialization.StringDeserializer, zookeeper.session.timeout.ms=300000, ssl.enabled.protocols=TLSv1.2, ssl.truststore.location=C:\software\ibm-java-sdk-<IP_ADDRESS>\jre\lib\security\cacerts, ssl.truststore.password=changeit, enable.auto.commit=true, security.protocol=SASL_SSL, sasl.mechanism=PLAIN, fetch.message.max.bytes=10485760, ssl.protocol=TLSv1.2, group.id=c64c5fb2-3854-4da2-85ac-b2e867cdf4d9, ssl.truststore.type=JKS, zookeeper.sync.time.ms=2000, bootstrap.servers=kafka04-prod02.messagehub.services.us-south.bluemix.net:9093,kafka05-prod02.messagehub.services.us-south.bluemix.net:9093,kafka03-prod02.messagehub.services.us-south.bluemix.net:9093,kafka02-prod02.messagehub.services.us-south.bluemix.net:9093,kafka01-prod02.messagehub.services.us-south.bluemix.net:9093, session.timeout.ms=30000, max.partition.fetch.bytes=10485760, auto.commit.interval.ms=1000}"}

Fix added to release 1.0 - equivalent update to master is in progress

Using egeria release-1.0 branch build (from March 04, 2019) with WKC, see 4 log entries that are still showing the kafka sasl.jaas.config and ssl.truststore.password info.
logged_kafka_credentials.txt

I am also seeing this in 1.1
Here's my start. I have log level set to INFO
https://gist.github.com/a0ffb08e01edf8094a5da948ffb3887b

Additionally a REST API call to retrieve configuration also exposes the above secrets ie
GET {{baseURL}}/open-metadata/admin-services/users/{{user}}/servers/{{server}}/configuration/

This fix has only be added to 1.0 at this time - the fix for master is still in my workspace

It is reasonable that the credentials are return on the GET request because it is the administrator that sets it up


Osram lightify bugfix

Description:
updated python-lightify module with a bugfix, concerning a limit in the maximum of possible devices
Related issue (if applicable): fixes #8733
Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[x] New dependencies are only imported inside functions that use them ([example][ex-import]).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Hello @tfriedel,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

ea886b06d5492b1f5912e60016ca763df9e9a85c - This commit has something that looks like an email address (thomas.friedel@berlin). Maybe try linking that to GitHub?.
bab8d5b17bd305d4849ab0714d2f66e680b14728 - This commit has something that looks like an email address (thomas.friedel@berlin). Maybe try linking that to GitHub?.
e13fb052d3dcca9adff374744fa301db6d76201a - This commit has something that looks like an email address (thomas.friedel@berlin). Maybe try linking that to GitHub?.
56df3ed9c76a0a3cbb9dd6e4f64f3620d83ee378 - This commit has something that looks like an email address (thomas.friedel@berlin). Maybe try linking that to GitHub?.
1e25daf98b0e3239c7abe70a469b42cee35a2d71 - This commit has something that looks like an email address (thomas.friedel@berlin). Maybe try linking that to GitHub?.
6c80b8f0a642ea417fff6c9f3e8fe7fb5cecba76 - This commit has something that looks like an email address (thomas.friedel@berlin). Maybe try linking that to GitHub?.
35ca74a56be269bfd04ac76465ed2d574598f58d - This commit has something that looks like an email address (thomas.friedel@berlin). Maybe try linking that to GitHub?.
264992230660658ef0206bc616195055d430b776 - This commit has something that looks like an email address (thomas.friedel@berlin). Maybe try linking that to GitHub?.
eb11eefe9f8f338b41d9f4a527b7bd937494804b - This commit has something that looks like an email address (thomas.friedel@berlin). Maybe try linking that to GitHub?.
dd926104fcf43ee4761e4a13d9c5698af158b5da - This commit has something that looks like an email address (thomas.friedel@berlin). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:


delayed output in Julia 0.3

When running a Julia 0.3.12 kernel on Jupyter 4.1.1, the output of any cell is not shown dynamically, but only when the whole cell has finished evaluating. For example
print("a"); sleep(3);print("b") would display "ab" after 3 seconds, rather than first a, and then b 3 seconds later.
This issues is not present with Julia 0.4.5 kernel, but I need to run Julia 0.3.12 for compatibility reasons.

@JobJob, you did some work on the asynchronous I/O ... any idea of why it would be different in 0.3?
(As a practical matter, it's going to be harder and harder to use Julia 0.3, since probably none of the package developers are using it regularly anymore.)

Sorry, somehow I missed this @ mention. Is this still an issue @DalimilMazac ? I could look into it.

Since we dropped Julia 0.3 support some time ago, I think this issue can be closed.


[translation] doc fixes

API change check for azure-ai-translation-document
API changes are not detected in this pull request for azure-ai-translation-document


[Traefik Plugin Catalog] Plugin Analyzer has detected a problem.

The plugin was not imported into Traefik Plugin Catalog.
Cause:
failed to run the plugin with Yaegi: failed to eval `CreateConfig` function: 1:28: undefined: traefik_plugin_manual_access_control

Traefik Plugin Analyzer will restart when you will close this issue.
If you believe there is a problem with the Analyzer or this issue is the result of a false positive, please contact us.

updated package name


Adding Nanoset dataset

Hi!
After all your comments in the previous PR, I decided to give one last (big) overhaul to the Nanosets, and I think now we can indeed call them Nanosets. In short, I completely got rid of the NanosetBuilder, NanosetConfig, BlendedNanoset, and MMapIndexedDataset. Also, I got rid of the different Nanosets for each train, valid, and test split (I've seen code snippets where you mention that you intend to support this, so when the time comes, I'll include it). Now there are ONLY the Nanosets, for which we ONLY have to specify the paths to the preprocessed datasets and, if we want, a weight for each one.
Basically, for each dataset_path specified in the configuration, we will read the total number of tokens and divide it by the sequence length to know the number of samples we can construct. If we have more than one dataset and do not specify the weight for each of them, we will consume them entirely for each epoch. Otherwise, we will build the Nanoset respecting these weights, consuming samples from the datasets again if necessary (i.e., if we need 1000 training samples and the weight of dataset 1 is 0.9, we will need 900 samples from this dataset. If dataset 1 only has 100 samples, we will consume it 9 times per epoch).
To determine from which dataset within the Nanoset and which sample to extract, we will build two indices: dataset_index, which will select the dataset from which to extract the sample, and dataset_sample_index, which will select the sample from the dataset. These two indices will be constructed using a helper function (build_nanoset_index_helper) that we will compile with Numba. This function is similar to the ones included in Megatron, which were compiled in C++, but in Python, for very large datasets, it took an enormous amount of time to run. Now with Numba, we solve this problem, keeping the entire project in Python. With these two indices, we will access the specific dataset and extract the sample with sequence length + 1 tokens.
I have updated the documentation by adding a detailed explanation of how they work, although I have left many comments in nanoset.py. I have also updated the tests, checking the following:

That we build the same Nanoset in ALL processes.
That dataset_index has been constructed according to the dataset_weights.
That dataset_sample_index does not attempt to extract samples > len(dataset).

To install the necessary dependencies, I have created a new flavor of Nanotron, so it will be necessary to install it with pip install -e '.[nanosets]'. You can test them as follows with the config I have added:
python3 tools/preprocess_data.py \
       --input yelp_review_full \
       --split train \
       --output-prefix datasets/yelp_review_full \
       --tokenizer-name-or-path gpt2 \
       --num-workers 16

python3 tools/preprocess_data.py \
       --input HuggingFaceH4/testing_alpaca_small \
       --split train \
       --column completion \
       --output-prefix datasets/testing_alpaca_small \
       --tokenizer-name-or-path gpt2 \
       --num-workers 16

We launch the job with:
torchrun --nproc-per-node 4 run_train.py --config examples/config_nanoset.yaml

I have tested it with a setup with 4 GPUs.
As always, I expect your comments!
Toni.

Refractored preprocess_data.py script to use torchrun instead of multiprocessing. Now you can run:
torchrun --nproc-per-node 16 tools/preprocess_data.py \
       --input yelp_review_full \
       --split train \
       --output-prefix datasets/yelp_review_full \
       --tokenizer-name-or-path gpt2

torchrun --nproc-per-node 16 tools/preprocess_data.py \
       --input HuggingFaceH4/testing_alpaca_small \
       --split train \
       --column completion \
       --output-prefix datasets/testing_alpaca_small \
       --tokenizer-name-or-path gpt2

Hello. Thanks for the PR. Looking into the PR now


Enhancing User Experience by Generating Security Audit Reports in PDF, DOC, or TXT Formats

Currently, the output of the NPM package is displayed in the VSCode terminal after running the required commands. However, for end users and developers (who downloads the NPM package), it would be more convenient if the security audit report could be generated as a PDF, DOC, or TXT file, allowing for easier review and avoiding the need to scroll through the terminal output.
Sample terminal report:
audit report.pdf
Make sure the end user/developer (who downloads the NPM package) is able to smoothly run the NPM package after these changes.

Can I work on this?

Can I work on this?

Sure, I've assigned you this issue.

NodeJsSecurifyReport.pdf
Is this pdf okay?

NodeJsSecurifyReport.pdf Is this pdf okay?

This pdf looks good, but at the end of pdf the result of

"Parsing for vulnerable npm pacakage"

is not visible? Can you look into it?

when i run src/NodeJsSecurify.js file I get this output in the terminal
`******************************************************************************************
****************************** Node-Js-Securify STARTED **********************************

Searching for .js files in (root directory) : /home/eleensmathew/NodejsSecurify/src
File names in .gitignore files not getting parsed:
, Vulnerability, dist, NodeJsSecurify.js, node_modules
File path name of .js & .jsx files getting parsed:
/home/eleensmathew/NodejsSecurify/src/GenerateReport.js
==> No callback hell detected. Code looks good!
==> Code NOT vulnerable to Brute force Attack
==> RegExp object detected with ReDoS-prone patterns at line 18
==> Code having proper input validation
==> No dangerous function detected
==> NO Insecure Authentication detected
==> Code NOT vulnerable to Brute force Attack
/home/eleensmathew/NodejsSecurify/src/GenerateReport.ts
Error: Line 2: Unexpected token =
at ErrorHandler.constructError (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:5012:22)
at ErrorHandler.createError (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:5028:27)
at Parser.throwError (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:1936:34)
at Parser.parseImportDeclaration (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:4837:23)
at Parser.parseStatementListItem (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:3373:39)
at Parser.parseScript (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:4723:29)
at parse (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:122:61)
at Object.parseScript (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:145:13)
at Function. (/home/eleensmathew/NodejsSecurify/src/NodeJsSecurify.js:177:101)
at step (/home/eleensmathew/NodejsSecurify/src/NodeJsSecurify.js:49:23) {
index: 44,
lineNumber: 2,
description: 'Unexpected token ='
}
/home/eleensmathew/NodejsSecurify/src/NodeJsSecurify.ts
Error: Line 36: Unexpected token :
at ErrorHandler.constructError (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:5012:22)
at ErrorHandler.createError (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:5028:27)
at Parser.unexpectedTokenError (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:1985:39)
at Parser.throwUnexpectedToken (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:1995:21)
at Parser.expect (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:2168:19)
at Parser.parseFormalParameters (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:4274:23)
at Parser.parseFunctionDeclaration (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:4337:38)
at Parser.parseStatementListItem (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:3379:39)
at Parser.parseFunctionSourceElements (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:4195:29)
at Parser.isolateCoverGrammar (/home/eleensmathew/NodejsSecurify/node_modules/esprima/dist/esprima.js:2269:37) {
index: 1407,
lineNumber: 36,
description: 'Unexpected token :'
}
Parsing for vulnerable npm pacakage:
Error executing npm audit: Command failed: npm audit --json
npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
npm WARN audit 426 Upgrade Required - POST http://registry.npmjs.org/-/npm/v1/security/audits/quick
npm ERR! audit endpoint returned an error` all the errors not printed using console.log i am not outputing to the file. If you want me to include the messages printed in the terminal using console.error please let me know. Also if you can give me a test file to test the code with that would be better

NodejsSecurify

i think you are giving the wrong path in NodeJsSecurify.ts:

the correct path in __dirname  should be /home/eleensmathew/NodejsSecurify/TestFolder. Can u please try again with correct path ?

include the messages printed in the terminal

ok in that case include the messages printed in the terminal too. And share the updated pdf.

Updated pdf
NodeJsSecurifyReport.pdf
******************************************************************************************
****************************** Node-Js-Securify STARTED **********************************
******************************************************************************************

Searching for .js files in (root directory) : /home/eleensmathew/NodejsSecurify/TestFolder
``
File names in .gitignore files not getting parsed:

, Vulnerability, dist, NodeJsSecurify.js, node_modules

File path name of .js & .jsx files getting parsed:

/home/eleensmathew/NodejsSecurify/TestFolder/BruteForceAttack/BruteForceNotVulnerable-1.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/BruteForceAttack/BruteForceVulnerable-1.js
==> No callback hell detected. Code looks good!

==> Code vulnerable to Brute force Attack in this file!!!

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code vulnerable to Brute force Attack in this file!!!

/home/eleensmathew/NodejsSecurify/TestFolder/CallBackHell/CallBackHell-1.js
==> Callback hell detected! AT Line no. => 25 In file: CallBackHell-1.js
Make use of async/await or .then/.catch to avoid callback hell

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> Following dangerous function detected:
> setTimeout detected at line: 1 Ensure: Remember to clear the interval when it's no longer needed: clearTimeout(timerId);
=====> Ignore above errors if you already made changes to your code <=====

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/CallBackHell/CallBackHell-10.js
==> Callback hell detected! AT Line no. => 34 In file: CallBackHell-10.js
Make use of async/await or .then/.catch to avoid callback hell

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> Following dangerous function detected:
> setTimeout detected at line: 1 Ensure: Remember to clear the interval when it's no longer needed: clearTimeout(timerId);
=====> Ignore above errors if you already made changes to your code <=====

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/CallBackHell/CallBackHell-2.js
==> Callback hell detected!  AT Line no. => 6 In file: CallBackHell-4.js
Make use of async/await or .then/.catch to avoid callback hell

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> Following dangerous function detected:
> setTimeout detected at line: 1 Ensure: Remember to clear the interval when it's no longer needed: clearTimeout(timerId);
=====> Ignore above errors if you already made changes to your code <=====

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/CallBackHell/CallBackHell-5.js
==> Callback hell detected!   AT Line no. => 4 In file: CallBackHell-7.js
Make use of async/await or .then/.catch to avoid callback hell

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> Following dangerous function detected:
> getElementById detected at line: 1 Ensure: Regular expression to match only letters
=====> Ignore above errors if you already made changes to your code <=====

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/CallBackHell/CallBackHell-9.js
==> Callback hell detected! AT Line no. => 4 In file: CallBackHell-9.js
Make use of async/await or .then/.catch to avoid callback hell

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> Code vulnerable to Insecure Authentication in this file!!!
Check for: Hardcoded Credentials, Weak Passwords, No Password Hashing, Insecure Session Management, Insecure Token Storage, Weak JWT Security

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/CallBackHell/CallBackHellNoError-3.js
==> No callback hell detected. Code looks good!

==> Code vulnerable to Brute force Attack in this file!!!

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/CallBackHell/CallBackHellNoError-6.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/CallBackHell/CallBackHellNoError-8.js
==> No callback hell detected.  Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> RegExp object detected with ReDoS-prone patterns at line 9

==> Code having proper input validation

==> Following dangerous function detected:
> setTimeout detected at line: 1 Ensure: Remember to clear the interval when it's no longer needed: clearTimeout(timerId);
> parsedInt detected at line: 1 Ensure: Always specify the radix (base) to avoid unexpected results
> parsedFloat detected at line: 1 Ensure: Always specify the radix (base) to avoid unexpected results
> getElementById detected at line: 1 Ensure: Regular expression to match only letters
> outerHTML detected at line: 1 Ensure: It does'nt accepts script tag, can cause XSS Attack
> innerHTML detected at line: 1 Ensure: It does'nt accepts script tag, can cause XSS Attack
> document.write detected at line: 1 Ensure: Avoid using it to prevent DOM XSS attack
=====> Ignore above errors if you already made changes to your code <=====

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/InputValidation/InputValidationError.js
==> No callback hell detected.  Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/InputValidation/NoInputValidationError-2.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/InputValidation/NoInputValidationError-3.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/InputValidation/NoInputValidationError-4.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/InsecureAuthentication/InsecureAuthenticatio2.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> Following dangerous function detected:
> JSON.parse detected at line: 1 Ensure: Be cautious about the source of the JSON data, Can lead to  Client-side JSON injection
=====> Ignore above errors if you already made changes to your code <=====

==> NO Insecure Authentication detected

==> Code vulnerable to Brute force Attack in this file!!!

/home/eleensmathew/NodejsSecurify/TestFolder/InsecureAuthentication/InsecureAuthentication1.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> Following dangerous function detected:
> JSON.parse detected at line: 1 Ensure: Be cautious about the source of the JSON data, Can lead to  Client-side JSON injection
=====> Ignore above errors if you already made changes to your code <=====

==> NO Insecure Authentication detected

==> Code vulnerable to Brute force Attack in this file!!!

/home/eleensmathew/NodejsSecurify/TestFolder/InsecureAuthentication/InsecureAuthentication3.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/InsecureAuthentication/InsecureAuthentication4.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> RegExp object detected with ReDoS-prone patterns at line 4

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/InsecureAuthentication/InsecureAuthentication5.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/InsecureAuthentication/InsecureAuthentication6.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> RegExp object detected with ReDoS-prone patterns at line 4

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/InsecureAuthentication/InsecureAuthentication7.js
==> No callback hell detected. Code looks good!

==> Code vulnerable to Brute force Attack in this file!!!

==> NO RegExp object detected with ReDoS-prone patterns

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/InsecureSecurityHeader/InsecureSecurityHeader1.js
==> No callback hell detected.      Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> RegExp object detected with ReDoS-prone patterns at line 2

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/RegexAttack/RegexAttack2.js
==> No callback hell detected. Code looks good!

==> Code vulnerable to Brute force Attack in this file!!!

==> RegExp object detected with ReDoS-prone patterns at line 2

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/RegexAttack/RegexAttack3.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> RegExp object detected with ReDoS-prone patterns at line 2

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code vulnerable to Brute force Attack in this file!!!

/home/eleensmathew/NodejsSecurify/TestFolder/RegexAttack/RegexAttack4.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> RegExp object detected with ReDoS-prone patterns at line 2

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/RegexAttack/RegexAttack5.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> RegExp object detected with ReDoS-prone patterns at line 2

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/RegexAttack/RegexAttack6.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> RegExp object detected with ReDoS-prone patterns at line 2

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

/home/eleensmathew/NodejsSecurify/TestFolder/RegexAttack/RegexAttack7.js
==> No callback hell detected. Code looks good!

==> Code NOT vulnerable to Brute force Attack

==> RegExp object detected with ReDoS-prone patterns at line 3

==> Code having proper input validation

==> No dangerous function detected

==> NO Insecure Authentication detected

==> Code NOT vulnerable to Brute force Attack

Parsing for vulnerable npm pacakage:
Error executing npm audit: Command failed: npm audit --json
npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
npm WARN audit 426 Upgrade Required - POST http://registry.npmjs.org/-/npm/v1/security/audits/quick
npm ERR! audit endpoint returned an error

Can i make the updated pull request?

Can i make the updated pull request?

Sure.


Add syntax highlighting to README

Hey,
Thanks for the lightning talk on PyCon PL 2017 :).
I have added syntax highlighting to the code boxes in README.
ps. you might want to add link to the yt video with lightning talk whenever it is available (hope it will be sooner than later).

I wasn't sure if this would break rendering on the PyPI page. I'll merge and I guess we'll find out!


Logo Proposal

Hi there @itzmeanjan  I'm a graphic artist and would like to contribute by designing a logo here. If you are interested I will be gladly begin my design. Regards! - Tobaloidee

Hei @Tobaloidee , it'd be great to have logo for this mapping application. Happy Designing :+1:

Hi @itzmeanjan thank you for the response! Will design and show it here after

Here's what I came up with @itzmeanjan  I hope you like it! Still open for your suggestions/opinions

Hei @Tobaloidee nice work :heart:
Great design idea, which displays insight of application. I'll put a link, pointing to your profile and work, in this repo.
Keep it up :+1:

Hei @Tobaloidee, I've put a link back to your work in README.md.

Sir here's the PR #2 for a better display of your new logo and I uploaded it into the logo folder.
Thanks so much! Best Regards! 😊👍

Hi @itzmeanjan you can get the other versions and file formats of your logo HERE
Thanks again! and Best regards!

Hei @Tobaloidee, that's great :+1:

Hi @itzmeanjan! I have seen just now your other projects/repositories...I thought of doing a logo for them too. Are you interested? I am.. 😊

Hei @Tobaloidee , I was thinking about asking you for making logo for other projects like transferZ, which I released a few days ago. Please make so, I'll be happy to give you credit. After you're done submit a PR :wink:.

That's great news! I will definitely work for your other projects..you can count on me with those logos 👍

Will just open an issue with those projects whenever I am done with the designs


Please publish a new crates.io release

Please publish a new version to crates.io, as https://github.com/servo/pathfinder/pull/548 has not yet been released.
Once raqote is able to depend on a version of pathfinder that contains PR 548 changes, their CI pipeline will be fixed:
https://github.com/jrmuizel/raqote/pull/201

Hi, came here for the same reason, a new release would be greatly appreciated.
Adding a log output of the error to help visibility (this is with the nightly toolchain):
error[E0557]: feature has been removed
  --> /opt/rust/cargo/registry/src/index.crates.io-6f17d22bba15001f/pathfinder_simd-0.5.2/src/lib.rs:11:61
   |
11 | ...vm_intrinsics, platform_intrinsics))]
   |                   ^^^^^^^^^^^^^^^^^^^ feature has been removed
   |
   = note: SIMD intrinsics use the regular intrinsics ABI now

   Compiling rand v0.8.5
error[E0635]: unknown feature `stdsimd`
  --> /opt/rust/cargo/registry/src/index.crates.io-6f17d22bba15001f/pathfinder_simd-0.5.2/src/lib.rs:12:49
   |
12 | #![cfg_attr(pf_rustc_nightly, feature(simd_ffi, stdsimd))]
   |                                                 ^^^^^^^

Some errors have detailed explanations: E0557, E0635.
For more information about an error, try `rustc --explain E0557`.
error: could not compile `pathfinder_simd` (lib) due to 2 previous errors

@jdm @mrobinson or whoever has access can #557 be published to crates.io?

I have just published a new version of pathfinder_simd, which I think should unblock https://github.com/jrmuizel/raqote/pull/201.

Perfect, thanks!


55 document all ros packages pt. 1

Closes #55

For some reason, the collaboration diagrams don't show up for the modules under wrover_control_drive_science.

This PR will not merge.  When the story is really complete, we will re-review and merge then.


Something wrong with ds.last_loaded

If my understanding is correct, ds.last_loaded is supposed to capture the timestamp of when the dataset is last loaded. However, I think it's used incorrectly in the main.py script:
v0.5/classification_and_detection/python/main.py
add_results(final_results, "{}".format(scenario),
            result_dict, last_timeing, time.time() - ds.last_loaded, args.accuracy)

The difference time.time() - ds.last_loaded is in my understanding trying to capture the runtime of the network. However, ds.last_loaded is repeatedly called while the model is running. As a result, we end up with an incorrect calculation of qps in add_results.
In particular, I think this only manifests when the dataset is large enough for ds to load images after lg.StartTest is called.
Here is the output:
TestScenario.SingleStream qps=218.86, mean=0.0250, time=22.846, acc=77.200%, queries=5000, tiles=50.0:0.0244,80.0:0.0280,90.0:0.0298,95.0:0.0314,99.0:0.0348,99.9:0.0385
accuracy=77.200%, good=3860, total=5000
If we take mean as an example, 1/0.0250 ~= 40, which should be close enough to qps. Instead qps is calculated to be much higher because last_loaded has been updated after lg.StartTest was called.

The result tracking in the reference app pre-dates loadgen - we’ll remove it going forward.
Only the loadgen output (aka mlperf_log_summary.txt ) is the truth for the submission.
From: ggeor84<EMAIL_ADDRESS>Sent: Thursday, February 6, 2020 5:33 PM
To: mlperf/inference<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [mlperf/inference] Something wrong with ds.last_loaded (#559)
If my understanding is correct, ds.last_loaded is supposed to capture the timestamp of when the dataset is last loaded. However, I think it's used incorrectly in the main.py script:
v0.5/classification_and_detection/python/main.py
add_results(final_results, "{}".format(scenario),
        result_dict, last_timeing, time.time() - ds.last_loaded, args.accuracy)

The difference time.time() - ds.last_loaded is in my understanding trying to capture the runtime of the network. However, ds.last_loaded is repeatedly called while the model is running. As a result, we end up with an incorrect calculation of qps in add_results.
In particular, I think this only manifests when the dataset is large enough for ds to load images after lg.StartTest is called.
Here is the output:
TestScenario.SingleStream qps=218.86, mean=0.0250, time=22.846, acc=77.200%, queries=5000, tiles=50.0:0.0244,80.0:0.0280,90.0:0.0298,95.0:0.0314,99.0:0.0348,99.9:0.0385
accuracy=77.200%, good=3860, total=5000
If we take mean as an example, 1/0.0250 ~= 40, which should be close enough to qps. Instead qps is calculated to be much higher because last_loaded has been updated after lg.StartTest was called.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmlperf%2Finference%2Fissues%2F559%3Femail_source%3Dnotifications%26email_token%3DAFPA3CHCZ7ZWJZGVB2K7XFLRBS25LA5CNFSM4KRG43CKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ILVZVHQ&data=02|01|guschmue%40microsoft.com|8fa58306cc22425d78a508d7ab6db0da|72f988bf86f141af91ab2d7cd011db47|1|0|637166359914044765&sdata=XFW7sYQt6WWzSO90XlV604djxj4%2FBkxyzaQm1%2Febqao%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFPA3CDF6YO7B4F2ZKK7HDDRBS25LANCNFSM4KRG43CA&data=02|01|guschmue%40microsoft.com|8fa58306cc22425d78a508d7ab6db0da|72f988bf86f141af91ab2d7cd011db47|1|0|637166359914054731&sdata=8ew7RSwtiBDd0YhJAKRHqu0ckeatwme31zr4Z15CsHs%3D&reserved=0.

mlperf_log_summary.txt does not contain any information:
No warnings encountered during test.
1 ERROR encountered. See detailed log.
 Please use the logs from loadgen as the source of truth. If needed, please suggest edits to the logging spec doc (please see the recent WG slides here https://docs.google.com/presentation/d/1VnjrbhHUJstkXC2RO1zqHXYyhE2YforpPbdyrxbMKo4/edit. You have to be part of the WG to access the slides)


mandelbrot does not compile

In the mendelbrot example it uses vulkano::device::Features but Device::new() appears to expect vulkano::instance::Features.

I think you might be using the example with the wrong vulkano version? It runs fine for me as is, and vulkano::instance::Features was removed in vulkano 0.11.

Yep, my mistake. Updated vulkano and it is working properly. Thanks rukai.


Generic destination / sink decorator

Description
Implementation of https://github.com/dlt-hub/dlt/issues/752
This is a re-submit of PR https://github.com/dlt-hub/dlt/pull/891 which I cannot reopen after an accidental merge
Notes:

We also introduce the concept of a load package state here

@rudolfix current questions:

I have create a method to create a partial from a function decorated with "with_config", can you let me know if this looks good? Then I can add some tests
Can you show me how an example of a sink function with google cloud credentials should look like? Do you want to send the spec as one arg or what is the interface for the user you have in mind? Then I will better understand what you have in mind

Generally you can have a look at my changes, I did most of the stuff of your last review.


Find in Project searches performs search in recently removed project folders

I'm having a reproducible issue in Atom 1.0.2 Mac where when I run Find in Project the search also searches in projects that I've removed from the sidebar and as well as the currently selected / open project.
The only way I've managed to get around it is by quitting and reopening Atom.

Would you mind reopening this on https://github.com/atom/find-and-replace? Thanks!


event clean method issue

In current code of event clean method we can easily get an TypeError: unorderable types: NoneType() >= datetime.datetime()
Create new event and leave CfP not allowed and cfp_end empty system will raise an exception. Besides we will send this info to users, so make sure clean method is also called on save.

I'll do it together with #245 as these bugs are related

PR merged thank you.


Improve sorting of Showcase entries

The Showcase page (Portfolio plugin in the backend) is currently a bit rough, and we have no control on the sorting of the submitted entries. They are sorted in reverse chronological order (from latest addition to oldest one).
That means that we don't have much control over what we actually show on the main page, and since we've been relatively flexible with what kind of games get added to the database (basically as long as it looks decent visually, it's fine), at some times we might be showing low-to-mid quality mobile games instead of more impressive desktop titles, for example.
I'm open to suggestions on how to improve this.
Here's the idea I have so far:

Split the page vertically in two sections:

The first section would have games which were tagged by webmasters with the "featured" tag
The second section (below) would have all other games

Both sections would be randomized, so that you see different games each time you load the page
Instead of a pagination, we could have the following:

The first section (featured) would be a one-row banner that can be scrolled to the left and right, showing more entries
The second section would be scrollable vertically and new entries would load as you scroll down

WDYT?

I think those are great ideas, and would be pretty easy to implement.
How do we currently accept entries? Is it just by hand? Would it be worth the effort to add the ability to accepts entries?

3.0 is released, and this really needs to be addressed.
Two sections is the way to go, but they would be toggle-able instead of both visible. What I mean is near top center of showcase page you would be able to select either "Featured" or "All", to switch to respective view modes. At that point, the page can have more entries appear as you scroll down.
We should also put together some guidelines as to what will be considered for "Featured", preferably something more specific than "need to have nice graphics".

I feel your second option is more modern, as it is seen more and more in modern web design. Here's a more detailed idea of what I think the second option should be like:

The top banner functions as a big, flashy showcase. Anything shown here is required to have a well made gif either showing off gameplay or cinematics, and the banner autoscrolls between maybe 5 or 10 games after the end of each gif. The Game Title is displayed on the bottom left side of the gift, and a tool for users to manually select the "page" they are on is on the bottom left, with dots for each entry.

Example:

There is pretty much not much to be said about the second section, except for that tiles should vary in size and shape and have a :hover action that maybe darkens or blurs the image. Each tile is simply the name of the game in front of an image of the game, with optionally the games genre in small text.

Games in the second section should be sorted based on some sort of popularity measure, be it rating or downloads. You would likely have to scrub the various websites these items are on for rating info. It should not be random. I saw 5 fidget spinner games early on while looking in the current showcase area, this is where you present your products capabilities and showing just any games can potentially lead to a false assumption about your engine's worth.

I really do hope you incorporate some of these ideas. 🙂

It seems the new layout has done away with tags being displayed, though you can still filter by them manually by going to the right url e.g. (https://godotengine.org/showcase/tags/mobile)
bringing tags back so they can be displayed and adding tags for the games marketplace (steam/itch) would do a lot to help, or at the very least adding a desktop tag so we can filter out all of these mobile games.

the current showcase is temporal, because the plugin needs to be changes or something to make it possible to query featured + standard games, and yes i also want a featured section on top (like the one i proposed months ago in the new website issue)

I'm v.happy with godot 3, but I think the showcase page really needs some work, as this ticket is discussing.
In addition to improved filtering and display of the games, I would also like to be able to see at a glance which games are open source and whether they are 2.x or 3.x projects, at least for the FOSS games.
I think FOSS games should be highlighted on the showcase page due to their potential educational value to those learning godot and godot users/devs looking for inspiration or guidance.

Rather than stating free or non free, I'd rather showcase entries show the license of the software alongside the version of godot it uses. We could use a catchall like 'Commercial' for non free / closed source games if the license is unknown or not a commonly used one.

Hello everybody!
Me and @DavidAmado have experience with web development and would like to help with this long awaited issue.
I have read the comments above and here are some mockups I made on the frontend side:
For the featured games a near fullscreen image will cause huge impact. Let 2 buttons switch between all and featured.

For all the entries better stick with the cards layout, i added rating, but we should talk about how to validate votes that rate such entries and what "five stars", "four stars" really mean.

This is it so far. What do you think?
PS. Mockups were made using draw.io. Here is the file if you want to do some modification and contribute to the discusion:
GodotMockups.zip

I don't think ratings are appropriate, too many issues with it. It looks like you have a favourite icon (the heart) on there too, which doesn't seem like it would work too well as there's no login system, so just storing it in cookies?
I like that there is a featured showcase, though it looks fairly limited in how many games can be shown so it won't scale very well. Featured games should be required to have some kind of accompanying write up by the creator about their use of godot and more details about the game, like Unity (https://unity.com/madewith/cuphead)
There should be stricter requirements for the aspect ratio of the thumbnails submitted, the varying sizes look awful on the current showcase.
Font sizes on desktop are currently way too big, not sure about mobile.
Store availability should be added (Steam/Itch), Price (Free/Paid or maybe FOSS/Commercial), and License (MIT/GPL/Closed Source, etc)

The hearth button was "up-vote", this is to measure popularity. Authentication could be done with Github and/or social media. I would rather remove the five stars rating and leave the number of votes (like scketchfab does).
Commercial/FOSS is a good filter. I don't think price should be added. The site is not a store and prices change all the time (promotions, sequels, etc). I'm also not sure if license should be displayed, wouldn't it be enough with Commercial/FOSS filter?
So more mockups:

Featured write up. For mobile is pretty straightforward so no picture.

No more discussion? I sincerely would like to know what @akien-mga and @djrm think about this since you made the changes for Godot 3 launch

It would be cool to be able to search for tagged features in games to see how others implemented them and have us all share, inspire and build on each others ideas more. I would like to suggest a page for submitting searchable tags to projects (somewhat like how a wiki might work)

Is nothing going to be done about it. This issue was opened literally 2 years ago and nothing has been done about it. It is driving new users away.

@nikhilCad As we don't have time and resources to maintain a dynamic showcase page, we'll likely replace the showcase tab with a static page that embeds the videos such as the April 2019 Desktop/Console games showreel.


Revert "Adds a utility for starting up the Transform Service from Jav…

…a (#26834)"
This reverts commit e1b4ed355da518c49aa2971ba5ea4d079055b24e.
Due to https://github.com/apache/beam/issues/26985

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java Examples_Spark

Closing in favor of https://github.com/apache/beam/pull/27001


HELP: after 3 confirmations SSL handshake not finalized

I transferred bitcoin from a website to my Sparrow wallet. After 3 confirmations Sparrow gave a popup message saying the SSL handshake could not be finalized, and the question was if I wished to continue.
Since the popup said it could be due to a man-in-the-middle attack, I clicked on NO.
I can see the funds in my Sparrow Transactions tab (the wallet on the website is empty), they are not red or greyed out, but presumably I cannot use them. Is there a way to check if those funds are usable?
Could it be due to my VPN? Do I need to finalize the transaction? If so, how?
I am a bit desperate. Please help or point me in the right direction.
Many thanks in advance.

12 hours on and the bitcoin is still shown in Sparrow, just like the bitcoin I put there a long time ago.
Apart from in the Transaction tab mentioned above, it is also shown in the UTXO tab. May I therefore assume all is well, that I have full control of the funds and can use them normally?

See https://sparrowwallet.com/docs/faq.html#pkix-path-validation-failed. Probably, just an expired certificate.


Add Phabricator integration page

This adds a new page to Integrations for Phabricator. Still working on it, will update when I'm back from leave.

@harrietgrace can you take another look?

Sure thing! Will check it out tomorrow AEDT 👍🏻

Looking great @ahawkins 🌈I'm still keen for a little wrap up sentence or two at the end, but otherwise I think it's super! Want to add something there, do a final copyedit pass, then we'll merge? 🙌🏻

@harrietgrace added a single sentence at the end. Any copy edits from your side then we're good to merge 👍

Okie dokie, I've done some copyedits and added in the width/height tags to the images. Are the screenshots retina? They look a little on the small side 🤔

Okie dokie, I've done some copyedits and added in the width/height tags to the images. Are the screenshots retina? They look a little on the small side

@harrietgrace No they are not. I can redo them if you're ready to publish.

That would be super amazing 😊🙇🏻♀ Yep, we're ready to go once you've updated the images.

@harrietgrace retina work complete. Over to you.

So crisp! Thanks @ahawkins 🙇🏻♀


【question】could you tell me the latest embedding model which usable by setfit?

Hi!
This is not bug report but question.
From my understand, when we use SetFit, we have to choose one of embedding model from sentense transformer.
But now, I feel those models are kind of old and would like to know the latest model for embedding which can be used by setfit
Thank you in adv

All models from the MTEB leaderboard can be used in SetFit (with exceptions of the ones that are just APIs): https://huggingface.co/spaces/mteb/leaderboard
Some notable models in particular:

BAAI/bge-large-en-v1.5, BAAI/bge-base-en-v1.5, BAAI/bge-small-en-v1.5: People within the embeddings field are quite excited about these.
jinaai/jina-embeddings-v2-base-en and jinaai/jina-embeddings-v2-small-en: These are recent models that people love for their large sequence length of 8192 tokens.
sentence-transformers/all-mpnet-base-v2: An older, but still respected, model.
sentence-transformers/paraphrase-mpnet-base-v2: I've used this one a lot in the past.

But most of all, feel free to experiment between models on MTEB. I'd love to hear your findings. For example, I don't know which metric from MTEB is most useful for SetFit. Also consider that beyond this leaderboard, some models may kind of arbitrarily perform better with specific domains due to their training data, so experimentation is useful!

Tom Aarsen

Oh great! thank you for the perfect answer.
as you said, I think there is no perfect embedding models for all use cases, so we have to experience it for the specific use case.
I understand well, and thanks!


[New game]: Multiplayer Ludo with point system

🎮 Game Request
A Ludo Game, where two individuals will be able to play, and one can score until he wants to pause. If a player gets the dice 6, his
current points are reset
Point down the features
Game points
Multiplayer
Ludo
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @PoulavBhowmick03 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/asign

/assign

Hey @PoulavBhowmick03 👋!
@kunjgit here,
We have this annoucement to make 📢!!
We have updated our README 🚀
Make sure you follow proper guideline to raise your next issues !!
Make sure you join our Discord🕹 if you haven't 😇
Thank you 💗!

So now how can I add my game to the main README.md? will I have to create a new PR? @kunjgit

Hey @PoulavBhowmick03 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


HOME variable is expanding again

Since the last release, home variable is expanding again, both in the rc and autosave files, as well as the scripts.
I would honestly prefer to not have hard-coded paths to maintain portability of the configuration.
Is it possible to revert back to call the python scripts directly in the cmus config files? ala shell ~/.cmus/cmus-osx/media-keys.py &
I don't mind doing a PR for this. Already made some changes to it.

Is it possible to revert back to call the python scripts directly in the cmus config files? ala shell ~/.cmus/cmus-osx/media-keys.py &

I made this change to address two shortcomings:

The system Python environment was always assumed
Switching between development and normal usage was cumbersome

I won't be undoing that change, but I would accept a PR that makes the installer write out paths relative to the user's home directory instead of the absolute path in the automatically generated .sh scripts as well as the config file.

That's a very valid explanation.
I've opened a PR for this.


Way to not flag internal classes instantiated via builtin DI framework?

Is there a way to get this warning to suppress itself when the class is instantiated via Dependency Injection?
I have a class defined like so:
internal sealed class CurrentUserService : ICurrentUserService
that triggers this warning.  However, I also have another class in the assembly like this:
    public static class DIConfig
    {
        public static IServiceCollection AddAPICommonServices(this IServiceCollection services)
        {
            services.TryAddSingleton<ICurrentUserService, CurrentUserService>();

            return services;
        }
    }

Instead of completely suppressing the warning (since 95% of my classes setup this way are used via DI), it would be great if the warning only showed up when I have forgotten to register the class in DI.

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

ID: d4303a22-627d-4024-fee7-40db88a544ac
Version Independent ID: 37cc2f4d-7002-1b29-cfa4-b8be2924d0a7
Content: CA1812: Avoid uninstantiated internal classes - Visual Studio
Content Source: docs/code-quality/ca1812-avoid-uninstantiated-internal-classes.md
Product: visual-studio-windows
Technology: vs-ide-code-analysis
GitHub Login: @gewarren
Microsoft Alias: gewarren

@ideoclickVanessa -- Thanks for your question. It looks like you're having an issue with the product itself, rather than an issue with the documentation. Here are a few options where you might consider asking your question:
https://social.msdn.microsoft.com/Forums/vstudio
https://www.stackoverflow.com
https://www.reddit.com/r/VisualStudio/
As well, you might also consider using the Report a Problem tool to report the issue.

Apologies for bumping a closed issue, but this one was misdiagnosed as a library issue when it is not.
@ideoclickVanessa example falls right into the When to suppress warnings categories, and what the user is asking is a way for the analyser to supress this warning when type implements a preconfigured set of interfaces, or a set of attributes, for example.
Supporting suppression by interface or attributes would go a long way since they're one of the main ways the type can be discovered for registration by the DI framework.
Hope my explanation made this case more clear and open to proper consideration by the analyser devs.


Fix usage of absl::bit_cast

absl::bit_cast (and the std::bit_cast) have to be used "by value". If they are used to convert pointers, it's not more than a fancy reinterpret_cast and that's what we want to avoid.
So this commit fixes two usages of bit_cast that were pointers.
Unfortunately for the second one we can't use bit_cast and I had to fall back to calling std::memcpy directly to avoid any kind of UB.
This has been found by Address and UB Sanitizer™.

Thanks a bunch, as discussed offline - lgtm!


k2s uninstall: k2s CLI logs get deleted during uninstall

Actual
During k2s uninstall, the k2s CLI logs get deleted from c:\var\log\cli. This makes post-install diagnoses harder.
Expected
During k2s uninstall, the k2s CLI logs are preserved in c:\var\log\cli, similar to the k2s.log file.

Before cleaning up c:\var create a zip file with all the content of c:\var and copy it temp directory.
In addition a message with file location shall be shown.

I0214 09:10:40.066499    4240 main.go:299] [09:10:40] Uninstalling Build Only Environment done.
I0214 09:10:40.520954    4240 main.go:314] ZipArchiveHelper : The process cannot access the file 'C:\var\log\ci\ci_stderr.log' because it is being used by
I0214 09:10:40.526438    4240 main.go:314] another process.
I0214 09:10:40.526438    4240 main.go:314] At
I0214 09:10:40.526438    4240 main.go:314] C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Microsoft.PowerShell.Archive\Microsoft.PowerShell.Archive.psm1:697


Info icon

Icon Request
Request to add(not update) new [i] icon where you can use Slab i. Because many user may think it's a ! icon when they see the current sans version

Icon name: info
Tags of this icon: information
Screenshots of similar icons:

Icon with circle is missing @xiaochunjimmy

https://remixicon.com/icon/information-2-line
https://remixicon.com/icon/information-2-fill


micromamba list error when prefix is set to create-args

I'm using a custom prefix by specifying it in create-args, but micromamba list emits an error expecting it in standard location:
https://github.com/ickc/so-software-environment/actions/runs/6951330647/job/18913121490#step:5:1123

This is currently not supported. setup-micromamba needs to infer in some way how the environment is named. If the environment is being used in a custom prefix instead of the default location for named environments, this is not possible.
Is there a reason why you don't use
    - uses: mamba-org/setup-micromamba@v1
      with:
        environment-name: so-conda-${{ env.TODAYS_DATE }}
        micromamba-root-path: ${{ matrix.prefix }}
        environment-file: examples/so.yml

This would install the environment to ${{ matrix.path }}/envs/so-conda-${{ env.TODAYS_DATE }}.

Thanks, the extra piece of /envs/ is less ideal. I'll think about it.


Backend management API for IS4

Hi!
I'm using IS4 to manage authentication with OAuth and Users/Roles/Permissions with ASP.NET Core Identity.
I'd like to be able to create/edit/delete users/roles/clients/resources/etc. through some kind of backend management REST Web API exposed by the IS4 app, so that my application can call the needed methods.
I created a new IS4 .NET Core project using the "IdentityServer4 with ASP.NET Core Identity" (is4aspid) template, but I've not found any API Controller inside. Are those kind of controllers available somewhere, maybe starting from a different IS4 template?
May this management API feature be already available in your AdminUI commercial project or the management can be done only through the UI?

Good question. Yes, this functionality is available in our AdminUI product. This product gives you both a UI to handle these functions and full access to the backing API. Access to this API is protected by your own IdentityServer.
To get a free trail please visit https://www.identityserver.com/products or feel free to email<EMAIL_ADDRESS>directly.


Make swap use lvm

If swap is in logical volume, it might not be present yet. So swap
service should use and after lvm.

Are there any issues or blockers on this one?