watermarkable attachments

The PR adds a requires_watermark boolean field to the attachments model. When an attachment is uploaded with this set to True, the attachment is uploaded to a different location in the private_attachments/ namespace.
It is up to the consuming application to make sure this location is private.
This enables watermarking by providing:

a means to ensure that the source document for watermarking is in a private location
a boolean that, when checked, indicates to the consumer the file needs to be accessed differently

The file will not be accessible once uploaded. (If you click on the link, you should be denied access). It is up to the consuming application to provide a way to watermark the source file, and provide a means to download it.

I do wonder if this could just be called is_private making it  a more generic solution for non public attachments.
Another field would be necessary to indicate requiring watermarking, or a combination of is_private and a pdf extension could assume watermarking.
#nonblocking

@dannyshaw
I considered this. You'd need to enforce the is_private when requires_watermark is True. At which point you're basically at using requires_watermark. We can extend it in the future if needed if other private attachments are required.

Flagging that the migration will lock+rewrite the attachments table, which probably isn't a big deal.


Point-projection to support-mapped shapes is broken.

This line expects to be able to translate the matrix m. However, Identity::new() is passed when support-mapped shapes use this function to implement LocalPointQuery (e.g. this line). This panics because Identity is supposed to remain constant.
This bug was not discovered before #31 landed as point queries on those shapes were not used before.

This issue is a good example of how misleading the Identity type might be. The problem is that it implements all the traits that may imply a modification of itself, hence breaking the identity invariant. As a result, the implementation of those traits cause a panic. Those implementation (of e.g. the Translation, Rotation, and Transformation traits) should be removed so that the immutability of Identity is imposed at compile-time.
Here is how I am going to fix this issue.
First, on ncollide, the LocalRayCast and LocalPointQuery traits will be removed. They are there only to facilitate the implementation and are not really useful for the end-user. Therefore, ray casting and point-projection will be done through the traits RayCast and PointQuery only and will require a transformation matrix. In order to obtain the original performance characteristics of the Local[...] traits, the user will be free to use the Identity structure whenever possible (it will be for most shapes except convex ones that will require a modifiable transformation matrix).
Second, on nalgebra, traits that modify a matrix will no longer be implemented by Identity. This will give stronger guaranties at compile time to avoid the kind of missuses that are the origin of this issue.


Add new v1.2 initializer DSL and fix tests

I've tried to fix a few bits and bobs and setup the new v1.2 initializer DSL. I still can't get the tests to pass though :(.
Doesn't seem like the plugin is loading properly. Not quire sure what's up ...

I'll give it another look over, but this all looks good at first glance so I'll go ahead and merge!


Support integrating backend-specific Autoscoper executable & enable CUDA backend

Build-system updates:

Removed support for setting Autoscoper_RENDERING_BACKEND option.
Introduced an explicit AutoscoperM-OpenCL external project.
Associated Autoscoper "_DIR" variables with the label "Autoscoper_DIRS" allowing to update install and fix-up rules based on the different Autoscoper builds.
Updated external project variables depending on the project name to use ${proj}_ prefix instead of the hard-coded Autoscoper_ one.

AutoscoperM module updates:

Updated AutoscoperM module to include a combobox for selecting the rendering backend. The combobox is dynamically populated based on the available Autoscoper executables found in the environment (e.g., autoscoper-CUDA or autoscoper-OpenCL).

Note: The distribution of the CUDA variant of Autoscoper ("autoscoper-CUDA") will be integrated in subsequent commits.
List of Autoscoper updates:
$ git shortlog d476e2cbb..644473784 --no-merges
Jean-Christophe Fillion-Robin (2):
      COMP: Update cutil headers to fix build against SDK without cufft library
      COMP: Ensure Autoscoper inner-build is built with expected CUDA toolkit

Locally building on the windows factory completes without issue.
Once a clean build & upload of package has been tested manually, this PR will be merged :rocket:

After running .\SlicerWithSlicerAutoscoperM.exe from the build tree:

The support for running Autoscoper from a build tree on Windows is expected to be fixed though these pull requests:

https://github.com/BrownBiomechanics/SlicerAutoscoperM/pull/74

itself depending on https://github.com/Slicer/Slicer/pull/7485

Local testing confirmed that locally packaging the extension on Window and installing it allows to select either the CUDA or OpenCL backend before starting Autoscoper.

Considering that local testing confirmed that Autoscoper built on Windows with either with the CUDA or OpenCL rendering backend could be executed from an installed SlicerAutoscoperM extension,  I am moving forward with the integration :rocket: :white_check_mark:
cc: @amymmorton @bpaniagua @NicerNewerCar


Fixed content generation for widget when visibility is 'By-Group'

Fixed content generation for widget when visibility is 'By-Group'
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1395518
@miq-bot add-label bug

@gtanzillo  Could you review


Add linting for pipeline files

Add a make task that lints .pipeline files to enforce best practices.
Add new task as a dependency for existing lint task

To verify that a pipeline comment.pipeline contains a description one could use .jq:
cat comment.pipeline| jq -e '.pipelines[] | select(.id == "primary") | .app_data.properties.description?'


Enabling Application Insight  with Bot Composer and does not get "LuisResult" or "QnAMaker" name in telemetry data.

When I enable the application insight with Bot Composer and set log personal information to true, I can see in Apllication Insight log in CustomEvents the log name "BotMessageReceived" and "BotMessageSend" but I cannot collect luis or qna data as in the document:
https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-telemetry-analytics-queries?view=azure-bot-service-4.0#total-intents-by-popularity
How can I enable LUISResults and QnA Maker result in the telemetry data?
Thank you!

@damlaalkan, could you try setting LogPersonalInformation setting in Composer to '=settings.runtimeSettings.telemetry.logPersonalInformation' and see if you can see data from Luis or QnA Maker?

Shiproom:  assess if this causes SDK patch

@damlaalkan, try the following as a workaround

Go to your config in Composer
Toggle to JSON view of config
Verify that your settings includes something that looks like the following:

Click to see abbreviated config JSON
  "luis": {
    "authoringEndpoint": "",
    "authoringRegion": "westus",
    "defaultLanguage": "en-us",
    "environment": "composer",
    "name": "CoreWithLanguage",
    "endpoint": "",
    "authoringKey": "63e7xxxxxxxxxxxxxxxxxxxxxxxx37a8",
    "endpointKey": ""
  },
  "qna": {
    "hostname": "",
    "knowledgebaseid": "",
    "qnaRegion": "westus",
    "endpointKey": "",
    "subscriptionKey": ""
  },
  "runtimeSettings": {
    "adapters": ...,
    "features": ...,
    "components": ..,
    "skills": ...,
    "storage": ...,
    "telemetry": {
      "logActivities": true,
      "logPersonalInformation": true,
      "options": {
        "connectionString": "InstrumentationKey=61bbxxxx-xxxx-xxxx-xxxx-xxxxxxxx8038;IngestionEndpoint=https://westus2-2.in.applicationinsights.azure.com/"
      }
    }
  },
      ...
  }

As a workaround , add telemetry object as a child of the entire config object, sibling to other settings like luis and qna, could you add telemetry settings directly:

{
    "qna": { ... }
    "luis": { ... }
    "telemetry": {
         logPersonalInformation: true
      }
}

Talk to your composer bot to create LUIS and QnA telemetry events
Query App Insights -- do a generous query at first, such as just querying for customEvents.

Note: you may need to wait 3 - 5 minutes after you've talked to your bot for the telemetry details to appear in Application Insights.

You should be able to see LuisResult and QnAMakerRecognizerResult events in App Insights

@damlaalkan, try the following as a workaround

Go to your config in Composer
Toggle to JSON view of config
Verify that your settings includes something that looks like the following:

Click to see abbreviated config JSON

As a workaround , add a copy of your telemetry object as a child of the entire config object, sibling to other settings like luis and qna:

{
    "runtimeSettings": { ... },
    "qna": { ... },
    "luis": { ... },
    "telemetry": {
         logPersonalInformation: true,
         ...
      },
    ...
}

Talk to your composer bot to create LUIS and QnA telemetry events

Query App Insights -- do a generous query at first, such as just querying for customEvents.

Note: you may need to wait 3 - 5 minutes after you've talked to your bot for the telemetry details to appear in Application Insights.

You should be able to see LuisResult and QnAMakerRecognizerResult events in App Insights

Hi @Zerryth I have tired the same workaround in Bot Composer 2.1.1. I am testing the bot locally and cannot see any app-insights logged for LuisResult. Am I missing something?


Adding Java Script files

I will be adding a new java script code which would be calculating whether a number is prime or not. @lovishprabhakar02

Closed #15 with #16

Adding a new JS code in which I have created a form.

@lovishprabhakar02 I am going to add a new JS file to calculate area of shapes.

Adding a clock js program #15

@lovishprabhakar02 I would like to add to the area of shapes file by calculating the area of a circle, sphere, and cube

Hi @Brandon-Amezcua. Go ahead....you have the green signal.

@lovishprabhakar02 I would like to add to the area of shapes file by calculating the area of a circle, sphere, and cube

Go ahead! @Brandon-Amezcua


Python: .Net Main -> Feature Connector Gemini

Motivation and Context

Description

Contribution Checklist

[ ] The code builds clean without any errors or warnings
[ ] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[ ] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

Closing this for now, as @Krzysztof318 suggestion to create a PR squash to avoid mixing history from main into the PR.


Test code:
var Jimp = require('jimp');

var imageName1 = __dirname + '/' + 'img.jpg';
var imageName2 = __dirname + '/' + 'img2.jpg';

Jimp.read(imageName1, function(err, image1) {
  if (err) {
    return console.error(err);
  }
  Jimp.read(imageName2, function(err, image2) {
    if (err) {
      return console.error(err);
    }
    console.log('Distance betweer images is:', Jimp.distance(image1, image2));
  });
});

(their distance does not seem zero, to me... :-)

Do I miss something?

This is the same issues as with Taylor in #66. Use the latest version of phash.js straight from GitHub. Just copy and paste it over the one in your node_modules directory. When you do that it will work:
Hillary: 			cAjc7i6AH1r
Hillary (scribble):	e0kL7a0k9hi

Distance:	0.3125
Diff:		0.2898695136417556

I'll release it tonight. Sit tight.

Thanks... Just testing...
I plan to use distance (because it's a value can be pre-calculated and saved to DB, and to check for image duplication I just need a hamming distance, for every DB image).
To use diff() I should call it once for each DB image, right? I'm afraid it should be too slow (db is expected to reach ~750K  images...). Correct me if wrong, please...
One more thing, about hashes lengths: you said it is due to chance... But so I can't expect hashes lengths to be all the same? But if they do differ, how do I calculate a distance???
Thanks for your attention!

While calculating hashes for my images, I get:
my-app/node_modules/jpeg-js/lib/decoder.js:323
        throw "marker was not found";
        ^
 marker was not found
[21:20:35] [nodemon] app crashed - waiting for file changes before starting...

and my app crashes... Probably the image was empty, but Jimp should try to catch these errors, to avoid crashing, right? I (Jimp user) could catch these exceptions, too, but...

I think your strategy regarding distance and diffing sounds good.
About exceptions: Errors in Jimp are handled by throwing exceptions (unless a Node-style callback is passed). Yes, that will crash your app but I'm delegating that to you to catch. Most are a straight-forward case of a wrong argument being passed to a method so I'm surprised at the error you got.
To compute the hammering distance, you would be better off converting the base 64 hash to binary and padding to 64 digits with leading zeros as necessary. You can get the binary quite easily with: image.hash(2); Compute the hammering distance against those.
I'm planning on padding each the hashes with leading 0s as necessary for this reason.

I've also just made a fix where hashes will be returned with leading zeros. This will make it easier to compare binary hashes stored in a DB for hammering distance.

This night I did realizewhy 11... :-)

Correct me if wrong: to encode a byte in base64 you need 6 bits (2^6 = 64). Then to encode 64 bits you need 11 base64 bytes (64 / 6 = 10.6...) (i.e.: you need 10 full base64 bytes, plus one, that you'll use for the last 4 bits... Hence, no need for padding, it's automatic...
Please don't tell me I'm completely wrong... :-D

The padding is in case is if the first bit is not 1:
var white = new Jimp(256, 256, 0xFFFFFFFF);
var black = new Jimp(256, 256, 0x000000FF);

console.log("W: " + white.hash(2));
console.log("B: " + black.hash(2));

// Output:
// W:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000
// B:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000

console.log("W: " + white.hash(64));
console.log("B: " + black.hash(64));

// Output:
// W:<PHONE_NUMBER>0
// B:<PHONE_NUMBER>0

Perfect...
--
Marco Solari
System Analyst, Software Engineer and IT Consultant at Koinè Sistemi Torino
On 10 November 2015 at 10:28, Oliver Moran<EMAIL_ADDRESS>wrote:

The padding is in case is if the first bit is not 1:
var white = new Jimp(256, 256, 0xFFFFFFFF);
var black = new Jimp(256, 256, 0x000000FF);
console.log("W: " + white.hash(2));
console.log("B: " + black.hash(2));
// Output:
// W:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000
// B:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000
console.log("W: " + white.hash(64));
console.log("B: " + black.hash(64));
// Output:
// W:<PHONE_NUMBER>0
// B:<PHONE_NUMBER>0
—
Reply to this email directly or view it on GitHub
https://github.com/oliver-moran/jimp/issues/67#issuecomment-155367757.

Already in NPM ?
--
Marco Solari
System Analyst, Software Engineer and IT Consultant at Koinè Sistemi Torino
On 10 November 2015 at 10:33, Marco Solari<EMAIL_ADDRESS>wrote:

Perfect...
--
Marco Solari
System Analyst, Software Engineer and IT Consultant at Koinè Sistemi Torino
On 10 November 2015 at 10:28, Oliver Moran<EMAIL_ADDRESS>wrote:

The padding is in case is if the first bit is not 1:
var white = new Jimp(256, 256, 0xFFFFFFFF);
var black = new Jimp(256, 256, 0x000000FF);
console.log("W: " + white.hash(2));
console.log("B: " + black.hash(2));
// Output:
// W:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000
// B:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000
console.log("W: " + white.hash(64));
console.log("B: " + black.hash(64));
// Output:
// W:<PHONE_NUMBER>0
// B:<PHONE_NUMBER>0
—
Reply to this email directly or view it on GitHub
https://github.com/oliver-moran/jimp/issues/67#issuecomment-155367757.


[BACKLOG-31686] adds error log when AEL Spark job cannot be shutdown

:white_check_mark: Build finished in 19m 31s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core,engine

:ok_hand: All tests passed!
Tests run: 4740, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 19m 23s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core,engine

:ok_hand: All tests passed!
Tests run: 4740, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


allow dashes in frame names

Overview
Add dashes to allowed characters on frame names.
Fixes #1414
Pull request checklist

[ ] I have read the contributing guide.
[ ] I have agreed to the Contributor License Agreement.
[ ] I have updated the documentation.
[ ] I have resolved any merge conflicts.
[ ] I have included tests that cover my changes.
[ ] All new and existing tests pass.

Code review checklist
This is the checklist that the reviewer will follow while reviewing your pull request. You do not need to do anything with this checklist, but be aware of what the reviewer will be looking for.

[ ] Ensure that any changes to external docs have been included in this pull request.
[ ] If the changes require that minor/major versions need to be updated, tag the PR appropriately.
[ ] Ensure the new code is properly commented and follows Idiomatic Go.
[ ] Check that tests have been written and that they cover the new functionality.
[ ] Run tests and ensure they pass.
[ ] Build and run the code, performing any applicable integration testing.

Set(1000, my-frame=100) works OK, but quoting frames still doesn't work: Set(1000, "my-frame"=100)


setAttribute bug

Wrong values while rendering

fixed: https://github.com/m-schuetz/Skye/commit/bef8ad1e412fbaf5e5a16f93cfb76fb96db51469
Simple forgot to re-add the second permuation pass in distribute.vs after some experimenting. As a result, distribute.vsa nd distribute_attribute.cs shuffled to different locations.


Use Dictionary.get_key_list where appropriate

Using a List<Variant> when just doing normal iteration is more perfomant than Array with the intervening interface
Left cases which rely on the index alone to not make complicated iteration code

Arrays can also be iterated with range iterators too, so there is not much difference I think. The most performant option would be iterating the internal HashMap directly.

The creation of the array is probably a bit less performant especially for a single pass over it

Given the doubts it would be nice to measure the actual performance gain from this PR, even if it admittedly leads to cleaner code.

Since this is by far the established syntax for this and none of this is hot code I don't think performance measuring this is relevant, otherwise we'd have to consider changing all the existing cases, and given the overhead of type checking in Array I think assuming this could be slower is baseless


hadoop: remove jcl classloader

Codecov Report

Merging #1005 (679a7dd) into main (630263d) will increase coverage by 2.46%.
The diff coverage is 100.00%.

:exclamation: Current head 679a7dd differs from pull request most recent head ebcbe48. Consider uploading reports for the commit ebcbe48 to get more accurate results

@@             Coverage Diff              @@
##               main    #1005      +/-   ##
============================================
+ Coverage     37.20%   39.67%   +2.46%
- Complexity       33      151     +118
============================================
  Files           146      146
  Lines         23560    23555       -5
  Branches        422      422
============================================
+ Hits           8766     9345     +579
+ Misses        13617    12918     -699
- Partials       1177     1292     +115

Impacted Files
Coverage Δ

...java/src/main/java/io/juicefs/JuiceFileSystem.java
80.00% <100.00%> (-1.82%)
:arrow_down:

pkg/meta/redis.go
68.90% <0.00%> (-0.26%)
:arrow_down:

pkg/meta/sql.go
67.27% <0.00%> (+0.20%)
:arrow_up:

pkg/vfs/reader.go
65.14% <0.00%> (+0.36%)
:arrow_up:

pkg/vfs/handle.go
77.31% <0.00%> (+0.84%)
:arrow_up:

.../src/main/java/io/juicefs/JuiceFileSystemImpl.java
57.15% <0.00%> (+57.15%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 630263d...ebcbe48. Read the comment docs.


Generating JWT outside of HTTP lifecycle.

Apologies, I wasn't sure where else to pose this question.
I find myself in need of generating JWT tokens outside of the HTTP lifecycle.
Is there any way to get access to the auth.generate function outside of the http lifecycle?

What’s the use case?

Recently shared it here https://forum.adonisjs.com/t/how-to-get-access-to-auth-object-from-outside-of-the-request-cycle/898/7?u=virk


Error message should match x, y, z arguments

It's a bit confusing when the error message has a different order than the arguments, so this is a small change to the error message.

🙏 thanks @abarciauskas-bgse

Thanks @vincentsarago for making the additional changes and merging. I was going to write a test for the error message but 👌🏽 with me to forego that for now.


Uninitialized constant UNIXSocket under windows (torquebox/jruby)

Seems to be a problem with https://github.com/mperham/dalli/blob/354e24e2c2be3cc6ee9003fe88df3a6b95b17e83/lib/dalli/socket.rb#L129

Did you update gem lately? Also unix sockets are not existing on windows that should be taken care of

We updated our rails-app to use dalli-2.7.3 instead of dalli-2.7.2 - which gave us the mentioned error. Going back to 2.7.2 fixes the problem for us, so this seems to be a problem in 2.7.3.

Referenced commit should fix the issue. Probably would be fixed in 2.7.4

Nice, this should fix it! ;)

@fpauser are you able to test with this fork?

I'll test it and report it here.

Tested it and created a fix for the fix ;) - see dfens/dalli#1

Thanks, I will merge this if https://github.com/mperham/dalli/pull/524 test passes

Argh.  This should have occurred to me when reviewing the patch.  My apologies.

@petergoldstein no worries - this fix seems ok however tests are not passing on unknown reason to me - can you please trigger travis build?

@dfens I already have.
On a related note, any chance you could squash the commits before I merge the PR?  And do the specs run clean on Windows, or do we need to add an RbConfig block to some of the specs?

Squashed to 2 commits

@petergoldstein I am not able to tell if works clean on windows - @fpauser should be able to tell for sure

@fpauser Should be fixed with 2.7.4.  Please let me know if you run into any additional problems.  Thanks.


Add CI for notebooks

Description
Add CI to this repository that checks notebooks!
Todos

[x] Rerun notebooks: Fix klifs_utils related errors (deprecated package) and replace with opencadd.databases.klifs instead
[x] Add nbval checks to notebooks
[ ] Set up notebook CI (following @jaimergp's setup for TeachOpenCADD)

[x] Check notebooks 1*, 2* and 3* first
[x] Check notebooks 4* separately (needs input that lives not in GH repository)

[x] Update GH TOC figure :)

Questions

[x] How to test 4* notebooks? Input does not live in GH repository. > Usage of wget works as expected in ci.yml :)

Status

[ ] Ready to go

Celebrating first passing CI :partying_face:
Now include talktorials 4* that need external data to be downloaded to the repo first.

Update: CI passes with Python 3.8, while fails with Python 3.9 in notebook 4_3 with an StopIteration error in context of next usage. Will now run all notebooks under Python versions 3.6, 3.7, 3.8 and 3.9.

Changed my mind. Will run all notebooks under Python 3.8 - if that works, pin Python version in environment to 3.8 (this repo does not contain a package but a collection of notebooks, so no need to check multiple Python versions for now).

Those StopIteration errors seem to come from a "no matches found" situation in your generator, I don't think it has to do with Python versions. You might have found a stochastic behaviour when creating molecules, though (a common cause for these "no matches found" errors is that the molecule object was empty to begin with).

Thanks, @jaimergp, for commenting on this!
After the Python 3.8 CI did fail this time, I also went back to thinking there is nothing to iterate over. I cannot reproduce this behavior locally.
Try out:
Test output of exact_matches variable (nbval check)
https://github.com/volkamerlab/KinFragLib/blob/master/notebooks/4_3_combinatorial_library_comparison_klifs.ipynb (cell 10)
If something is off with that one, constructing ligands might cause errors?
Draw.MolsToGridImage(
    mols=[construct_ligand(row.fragment_ids, row.bond_ids, fragment_library) for index, row in exact_matches.iterrows()],
    legends=[f'{row.group} | {row.kinase} | {row.complex_pdb} | {row.ligand_pdb}' for index, row in exact_matches.iterrows()],
    molsPerRow=6
)

Maybe print those comprehensions in a sep list?


Add Abstractapi API

Added Abstractapi in Geocoding

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Thanks for the contribution @Zoki303!
Can you please arrange the API link in alphabetical order into the respective category.
Please also resolve the conflict.

Thanks for your contribution @Zoki303 😄
The abstractapi APIs have already been added to the list. You can see the discussion here: https://github.com/public-apis/public-apis/pull/1368


Add Frontend GIS

https://github.com/joewdavies/awesome-frontend-gis
This list contains all the necessary resources to visualize and analyse geographic information on web browsers.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

[x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
[x] Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
[x] You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
[x] You have read and understood the instructions for creating a list.
[x] This pull request has a title in the format Add Name of List. It should not contain the word Awesome.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

[x] Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

[x] Your entry should be added at the bottom of the appropriate category.
[x] The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

[x] No blockchain-related lists.
[x] The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

[x] Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
[x] Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
[x] The default branch should be named main, not master.
[x] Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

[x] It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
[x] The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

[x] The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

[x] Non-generated Markdown file in a GitHub repo.
[x] The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
[x] Not a duplicate. Please search for existing submissions.
[x] Only has awesome items. Awesome lists are curations of the best, not everything.
[x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
[x] Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

[x] Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
[x] Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

[x] Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

[x] Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

[x] Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

[x] All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
[x] Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

[x] Does not use hard-wrapping.
[x] Does not include a CI (e.g. GitHub Actions) badge.You can still use a CI for linting, but the badge has no value in the readme.
[x] Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

PRs reviewed:

https://github.com/sindresorhus/awesome/pull/2729#issuecomment-1656827189

https://github.com/sindresorhus/awesome/pull/2690#issuecomment-1629555997

https://github.com/sindresorhus/awesome/pull/2719#issuecomment-1646600801

unicorn

layout and graphics look great! One point, as someone not familiar with GIS I had to do a bit of digging to understand what was the resources were for, maybe the description could give slightly more information whilst still being succinct?

Stylistically, it's great. One thing to tweak up a bit though, after every title, you have a short description of what's to come, but you end all of those with either a full stop or an exclamation mark. I think you should replace them with a colon at the end of each final sentence, as this gives the feeling that the following elements are presented by the text.

Stylistically, it's great. One thing to tweak up a bit though, after every title, you have a short description of what's to come, but you end all of those with either a full stop or an exclamation mark. I think you should replace them with a colon at the end of each final sentence, as this gives the feeling that the following elements are presented by the text.

Thanks for the feedback, I have now replaced the full stops at the end of the section descriptions with colons!

Great list!
One thing though - I've opened a pull request that updates your contact information to reflect the fact that Twitter is now X. In addition I opened another pull request to suggest a GitHub action that checks for dead links.

Agree, would be nice to add dead links check.
https://github.com/joewdavies/awesome-frontend-gis/pull/4

@lunohodov This was very helpful. Thank you very much.

Linkify Geographic Information Systems in Geographic Information Systems (GIS) for web browsers. For managing, analyzing, editing, and visualizing geographic data. to https://en.wikipedia.org/wiki/Geographic_information_system

Tweet: https://twitter.com/awesome__re/status/1757676142595916005


Mark the value of the display option as required

Using the display option without a value does not make sense, and is not handled by the code anyway.
See https://github.com/friendsoftwig/twigcs/pull/177/files#r728771645

Thank you @stof!


Raipal (ver.0.11.0) breaks Chihuahua integration

Latest update to Raipal (ver.0.11.0) breaks Chihuahua integration. Mod is still installed in Raipal folder but has no presence in the app, doesn't appear on a game's page when I click on it.

it's a bug in rai-pal. There's already a fix in the repo. Wait for the next update.


@craigspaeth => Get AMP assets working

Instead of including it as an asset package, just transform the stylus sheet directly.

Mergin this guy @craigspaeth lmk if anything should be changed but it's the stuff we discussed :)


Remove incomplete static thread safety assertions.

Very few components in the engine have static thread safety annotations. The engine depends on annotations added to headers in libcxx. However those annotations are not complete. For example, using a mutex with a condition variable was not possible without disabling static threads safety checks on the mutex. Patching libcxx upstream is one possibility but the various Flutter engine targets may use different versions of libcxx and the inconsistency is hard to reason about. Due to these issues, it is hard to correctly review code that does not add thread safety annotation because these may be used in translation units on a platform where we can't use //third_party/libcxx. A suggested alternative was to use thin wrappers around the the libcxx synchronization primitives with annotations controlled by the Flutter engine authors. The enthusiasm for that proposal has been uninspiring. For runtime checks, tsan builds are alread possible. For the rest, it is proposed that till we commit to maintaining our own annotated headers, the annotations added via fml/synchronization/thread_annotations.h be removed.

cc @jason-simmons about the discussion had in person.


Defi page on beta giving IPFS error

Overview
When attempting to access the earning/defi page on beta, it take you to a new window and displays an error about ipfs resolve.
References and additional details

Log into beta.shapeshift.com
Connect to any wallet
Select the Earn page in the side menu
Select ‘Get started’ and notice it opens a new window and crashes to white screen with an error about ipfs resolve.

Noticed after testing on 6/2/22 after cutting over app.shapeshift.com from CF Pages to Fleek / IPFS

Acceptance Criteria
Should be able access earning/defi page from beta
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

https://github.com/CroixDrinkers/axiom/pull/3619 related PR to resolve the issue.

Caused by #1155.


linux ongoing

Description of Change
linux ongoing
Additions made

Adds Essentials - Gtk -Stubs (see also: https://github.com/jsuarezruiz/maui-linux/issues/18)
Essentials Clipboard: implement PlatformSetTextAsync, PlatformHasText, PlatformGetTextAsync
Essentials MainThread: implement PlatformBeginInvokeOnMainThread, PlatformIsMainThread
ButtonHandler.Gtk.cs: implement Characterspacing
Status.md: update

Ready to review?. Just let me know if need something :)

clean one is here: https://github.com/jsuarezruiz/maui-linux/pull/20, ready to review


Updating requirements in readme

Making things more clear. I'm not sure if this is fully correct, but that's easier to discuss in a PR ;)

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


Allow "macos" when parsing triples

LLVM target triples support either "macosx" or "macos", so our parsing code should also support both spellings.

@swift-ci please test

@swift-ci please test

Infra failure

@swift-ci please test macOS


Support macOS

It would be great if Grid could target support for macOS. It seems to support Catalyst, but that is not good enough for a native Mac app.

I took a stab at it and was able to add macOS support pretty easily. Unfortunately Xcode messes with so many project settings (and I don't know your preferred setup/naming) so it would probably be easier if you just addressed this on your end.
Steps to add Mac support:

Add macOS Framework target
Add all source files
Mac's dont have didReceiveMemoryWarningNotification. Find another solution for the layout cache.
Update Package.swift to add platform
Address some minor issues with examples using UIColor etc.
Done!

Thanks. This is a good suggestion

@OskarGroth Have you seen this error after opening any example view?
=== AttributeGraph: cycle detected through attribute 246584 ===
Fatal error: file SwiftUI, line 0
2020-10-11 16:39:48.571830+0700 Mac_Grid_Example[15635:7419021] Fatal error: file SwiftUI, line 0

And how did you import Grid library to the example project? Cocoapods?

Added MacOS support in v1.1.0
Caching for MacOS TBD


Building from source files or other options for modifying resin-wifi-connect

Background
We use RPi3s to control our hardware devices, which is remotely updated through Resin. We've got the whole pipeline setup and working smoothly except we were previously using [https://github.com/resin-io-playground/resin-wifi-connect-python-example](Resin Wifi Connect Python) to let our customers get their RPi3s connected to the internet. We had to make some modifications to that code to get it to work with our software, namely writing an email address to the disk on the initial connection to be retrieved later.
We're currently in the process of updating to the latest Rust-based stuff. We would like to make the same modification to write the email address and have our RPi3s run it on start. Related to https://github.com/resin-io/resin-wifi-connect/issues/139, but we've been running into issues.
What we've done so far
We first ported over all the files to our project, then modified server.rs to write the same email address (from our original project) to the same file:
fn connect(req: &mut Request) -> IronResult<Response> {
    let (ssid, passphrase, email) = {
        let params = get_request_ref!(req, Params, "Getting request params failed");
        let ssid = get_param!(params, "ssid", String);
        let passphrase = get_param!(params, "passphrase", String);
        let email = get_param!(params, "email", String);
        (ssid, passphrase, email)
    };

    fn write_email(email: String) {
        use std::io::Write;
        let mut email_file = File::create("/usr/share/config/userdata").expect("Unable to write file");
        email_file.write_all(email.as_bytes()).expect("Unable to write email to created file");
    }

    write_email(email);....

And then we wanted to get that to at least run on the RPi3s, as a sanity check, so we setup a .travis.yml to build and deploy it to resin. Not totally sure what the best way to go about that is, but this is what we've done so far:
install: true
sudo: required
dist: trusty
services: docker
language: rust
rust: "stable"
addons:
  ssh_known_hosts:
     - git.resin.io
os: linux
install:
 - sudo apt-get install libdbus-1-dev
script:
   - set -e
   - cargo install cross
   - cross build --release --target armv7-unknown-linux-gnueabihf
   - mv target/target=armv7-unknown-linux-gnueabihf/release/wifi-connect .
   - if [ $TRAVIS_BRANCH = 'development' ]; then
       eval "$(ssh-agent -s)";
       echo -e $RESIN_DEPLOY_KEY > id_rsa;
       chmod 0600 id_rsa;
       ssh-add ./id_rsa;
       git remote add resin_dev $RESIN_REMOTE_DEV;
       git add --all;
       git commit -a -m "Cargo built";
       git push -f resin_dev development:master;
     fi
   - set +e

No other modifications to the source files from resin-wifi-connect. When we ran it on travis, it kept popping up this error when cross build ran:
error: failed to run custom build command for `dbus v0.5.3`
process didn't exit successfully: `/target/release/build/dbus-c9094369a11371da/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error(PkgConfig(CrossCompilation), State { next_error: None })', /checkout/src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Which we tried to fix by adding dbus= "0.6.0" to the Cargo.toml file, which changed the error to this:
error: failed to run custom build command for `libdbus-sys v0.1.1`
process didn't exit successfully: `/target/release/build/libdbus-sys-74933906340f63f2/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error(PkgConfig(CrossCompilation), State { next_error: None })', /checkout/src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Now we're a bit stuck and starting to think we're probably approaching this the wrong way. Any idea what we're doing wrong? Is this the right way to modify resin-wifi-connect with the modifications we need? Would it be easier to actually build the rust application on the RPi3 itself in the Docker.template file? Happy to provide anything else needed!

I also had problems with building it using cross. The problem was that the Docker image they are using is based on Ubuntu 12.04, which does not contain more recent libdbus-1-dev required for building the dbus-rs library.
This is one of the reasons we are using a custom docker image for cross compilation on each target. You may find the one for Rpi3 here: https://github.com/resin-io/resin-wifi-connect/blob/master/scripts/docker/armv7-unknown-linux-gnueabihf/Dockerfile
We currently use CircleCI for building the binaries for all architectures. I would recommend cloning the repo and using the same build approach. This way you will be able to keep up easily with future changes. You may use the information in https://github.com/resin-io/resin-wifi-connect/issues/139#issuecomment-340888239 for further reference. (I need to put a documentation page for this, since this looks like a common question)
Building on the Rpi3 itself is also an option if you need new builds occasionally, but I would still recommend using the CircleCI approach.
Please let me know if you have any questions and I will be happy to answer!

Ahh got it, that makes a lot of sense! Okay got it working with that custom docker image, though we'd prefer to stick to Travis since that's where all of our other repos currently are being deployed from.
For anyone else that might need it, here was the final .travis.yml file we used:
sudo: required
dist: trusty
services: docker
addons:
  ssh_known_hosts:
    - git.resin.io
os: linux
before_install:
  - chmod +x ./deploy.sh
  - docker build -t armv7-unknown-linux-gnueabihf .
script:
  - set -e
  - docker run armv7-unknown-linux-gnueabihf /bin/bash -c "./deploy.sh"
  - set +e

With deploy.sh containing whatever commands you want it to run inside the docker image. For us deploy.sh contains. Since we wanted to build for an RPi3, we used:
cargo build --release --target=armv7-unknown-linux-gnueabihf;
We also had to add a COPY . . at the bottom of the armv7-unknown-linux-gnueabihf file to have access to everything, which we put in the root directory of the project

Great job!

Two quick questions - it'd be really convenient if we could move server.rs to a different port so we can have our primary app running on port 80, on the off chance the RPi3 can't connect to the internet.
First question, we're running in parallel because on the off chance the RPi3 is offline, we can tunnel into it with a local connection (ethernet cord) and still use our hardware device. It used to work with the old resin-wifi-connect running in python, but we're not able to get the pi to recognize an ethernet cable with resin-wifi-connect running. Is it just my pi? or is that the expected behavior?
Second question, given we wanted resin-wifi-connect and our software to run in parallel, we moved server.rs to port 81 so our app could run on port 80 (so we can access it via the public url on resin). So far we edited the address on line 152 in server.rs, moving it to port 81:
let address = format!("{}:81", gateway_clone);
Which worked and now when I access the captive portal, I can see our software running on port 80, and index.html running on port 81. I also made sure to change the urls index.js in public/ were hitting to http://<IP_ADDRESS>:81/ and got everything working again, but is it possible to move the actual captive portal primary display to port 81 instead of 80?

I will work today on the second issue - about the port. As there was another request for this as well and I would like to include that in the next release which is coming very soon.
Can you please provide me with steps to reproduce for the first question and a little bit more explanation, so that I can understand better and start investigating?

That would be awesome on the second issue, thank you!
I actually think we can ignore the first issue, I don't think it has to do with resin-wifi-connect. I used the wifi+ethernet setup to get resin running, but whenever I plug in an ethernet cord the pi doesn't even recognize it. It just so happens that the only other thing running is resin-wifi-connect, but I think the problem for that lies somewhere else?
Overall steps to reproduce my issue with the ethernet cord:

Use wifi + ethernet setup with proper wifi credentials to set up resin.io on the RPi3
Let resin-wifi-connect download to the device
Clear wifi credentials and restart
Plug in ethernet cord

Currently not getting the ethernet port lights to turn on when I do number 3
Thanks so much for your help @majorz!

Thanks a lot! I understand it now better. I will follow up on this one soon as well.

So when a page is opened when connected to the access point (e.g. captive portal check request by the phone OS), the host name is resolved to the captive portal IP address (using dnsmasq), but the request still targets port 80. It looks like some iptable calls for port forwarding to port 80 should be added additionally for this all to work. I will follow up with more information once I have a more complete answer.

Another side issue I've been having is whenever I set the credentials with one router, then move to another one, it doesn't bring up the access point again to reset the wifi credentials. Any idea how I could include that functionality? It's not vital, but would be very helpful

@kadhirvelm  The ability to support multiple WiFi credentials (e.g. moving the device from one place to another) is coming very shortly. The code is already ready in a branch and once docs are finished and review is done we will release it.
I hoped to include the different port number feature in the same next release, but it will be done after, as it is not as straightforward and I have to consult with the other team members on this.
I will ping you once the new release with multiple WiFi credentials is ready.

I still have to look into the ethernet cord issue above and I am just leaving a message for myself here, as not to forget about it :)


Table components should expose innerRef

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
Table components (Table, TableBody, TableRow, etc.) should provide innerRef prop exposing the HTMLElement.

Current Behavior
Currently it exposes a ref to a wrapper ReactComponent instead of to the real HTMLElement.

Examples
...
<DragDropContext ...>
  <Droppable ...>
    {provided => (
      <TableBody innerRef={provided.innerRef}>
        ...
      </TableBody>
  </Droppable>
</DragDropContext>
...

Context
Trying to make draggable table rows by using react-beautiful-dnd.

You can use the RootRef component or the React.findDOMNode API. In the future, you will be able to provide a ref directly once #10825 is closed.

I've been removing findDomNode from my codebase because of this post by Dan Abramov, and while it does seem like using RootRef works fine, I am wondering if that is just using findDomNode behind the scenes like the example it is based on does?

@Odinsama Yes it's. The React team has recently deprecated the usage of findDOMNode in the strict mode. Checked out the linked issue to keep up to date with our progress.


[system] Support transformed sx values to allow smoother transition to zero-runtime

Adding support for transformed sx values may have been done if this is used in a zero-runtime setup. I would consider the solution a bit hacky and I am not sure how we would ensure that this will always take presedence.

TODO:

[ ] Apply type changes after the PR is approved (the change was reverted so that the review is easier)
[ ] Joy UI components need to explicitly propagate the ownerState, not sure how this worked before 😕
[ ] Figure out the StepContent failing tests

For reviewers:

All docs related changes are related to: spreading sx prop needs to happen only if it is an object (adding a string type was failing this) - you cak safely skip this

No major comments towards the implementation. All looks good. I am just wondering if we should test this extensively through the docs site before merging.

I wonder if there is a way that we don't have to create a Tag component within the createStyled again from Emotion. My concern is the performance since isValidProp() is done twice for every styled-components (one from Emotion, one from the createdStyled).
Is it possible to update the Pigment sx transformation to replace it with className and style directly? Pigment exports a runtime sx() that does the same as internal styled.
// input
function App2(props) {
  return (
    <SliderRail
      sx={
        props.variant === 'secondary'
          ? { color: props.isRed ? 'red' : 'blue' }
          : { backgroundColor: 'blue', color: 'white' }
      }
    />
  );
}

// output
import sx from '@pigment-css/react/sx';

function App2(props) {
  return (
    <SliderRail
      {...sx(
        props.variant === 'secondary'
          ? {
              className: 's1xbsywq',
              vars: {
                's1xbsywq-0': [props.isRed ? 'red' : 'blue', false],
              },
            }
          : 's1wnk6s5',
        props,
      )}
    />
  );
}

The implementation of runtime sx() will combine the props and return className and style to the styled-component. With this, we don't have to change any single line of code.

No major comments towards the implementation. All looks good. I am just wondering if we should test this extensively through the docs site before merging.

For sure. I am still not 100% sure about the changes in createStyled there may be subtle changes that could break things in terms of props forwarding. I would still consider these changes a hacky solution to the problem, I think we should seriously consider what are the other options:

detecting if the changes should be transformed
use different prop - the migration cost may be higher
etc.

@siriwatknp we could try this, it may be problematic when there is spreading of props tough
<Component
  sx={...}
  {...other}
/>

Would need to somehow be converted to:
<Component
  {...other}
  className={sx.className, other.className}
  style={{...sx.style, ...other.style}}
/>

Agree performance is the other main reason why I was hesitant to merge this originally (even if we consider it wouldn't introduce breaking changes, while later turned out it will).

we could try this, it may be problematic when there is spreading of props tough

I think it could handled before the transformation because we had access to babel at that time. Just look for the className and style props first, then spread props. It should work.


VS solution file should be updated to 2013

Description

Type: Bug
Priority: Blocker | Major |

Bug
The VS solution file is still built for VS 2010, however, only 2013 and later should work, since the support for c99
OS
windows
mbed TLS build:
Version: 2.18

The README file should be updated as well

ARM Internal Ref: IOTSSL-2977


Revert "Upgrade zookeeper from 3.5.5 to 3.5.8"

This reverts commit 71f76a1803bc57f196601578b5d16862faf47875.
For backwards compatibility reasons.

@Xenorith I see no particular reason for the original upgrade other than staying current with zk client versions. so I expect this downgrade to have minimal impact as well.

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.6 please

alluxio-bot, cherry-pick this to branch-2.7 please


Fix linux-2.6 in download URL for RedHat x86_64

Pull Request (PR) description
Staring with 9.0.5 Splunk changed the filename of the RPM. It no longer includes
"linux-2.6", thus we need to adapt to this change.
- https://download.splunk.com/products/splunk/releases/9.0.0/linux/splunk-9.0.0-6818ac46f2ec-linux-2.6-x86_64.rpm
+ https://download.splunk.com/products/splunk/releases/9.0.5/linux/splunk-9.0.5-e9494146ae5c.x86_64.rpm

This Pull Request (PR) fixes the following issues
Fixes #348

@siegy22 can you retrigger the CI checks by either closing/reopening this PR or doing the following:
git commit -m "retrigger checks" --allow-empty
git push

#348 is blocking an upgrade deployment in my environment, I'd troubleshoot the failed checks here to help contribute towards a merge but the logs have since expired. Thanks!

@luedderd I amended and force pushed, CI is running once again 😄

I haven't worked with these kind of Puppet CI tests before but it seems they're failing in all current PRs for a different issue related to the seed admin password.
@kenyon @bastelfreak seem to be the most active approvers, is there anything else holding this from being approved/merged?  Thanks in advance

@luedderd I spent some hours trying to debug the GitHub actions. Finally found out what's the problem, I opened a separate PR: https://github.com/voxpupuli/puppet-splunk/pull/356
After this is merged, we can probably rebase and go on here. 🎉

@luedderd I rebased onto my other branch and also added tests.
As of now, you could set splunk::enterprise::enterprise_package_src to the full URL to make it work. E.g. https://download.splunk.com/products/splunk/releases/9.2.0/linux/splunk-9.2.0-1fff88043d5f.x86_64.rpm for 9.0.2

With this change, is it still required that net-tools are explicitly installed?
https://github.com/voxpupuli/puppet-splunk/blob/069a1424f6749fa9a11983331f6016ea08c5d67d/manifests/forwarder/install.pp#L64-L70
that's really legacy tooling and the rpm should depend on it if it's an actual dependency. Do we need to explicitly install it?

@bastelfreak Didn't check that yet. It's possible that this is not needed anymore. But I'd down to check that in a separate branch/PR. We need to ensure that Splunk 9.x can be installed and upgraded. As of now, even 8.2 is EOL and thus we should probably set the focus to be 9.x compatible for the future.
This change just fixes the URL that is being generated to download splunk.

We have acceptance tests at: https://github.com/voxpupuli/puppet-splunk/tree/master/spec/acceptance
can you add one with the new version so we can verify that it works?
If you don't know beaker: The tests are actual puppet code, executed in different docker containers. duplicate one of the existing blocks and add the correct version.

There seems to be a issue unrelated to this change when installing <IP_ADDRESS>. The package is downloaded and installed correctly (so this change is working) but the default parameters don't make sense with the newer versions.
I would suggest opening another PR to test the installation and upgrade of 9.x versions on all the platforms. I can do that.

shouldn't that go into this PR as well? We currently don't support version 9 at all and this PR now implements it in parts, but it's not really usable because of the wrong parameters?

@kenyon I tried it before with a RHEL 9 instance, installing some 8.x versions and 9.x versions. No issues without having net-tools installed. The only version that didn't install that I tried was <IP_ADDRESS> that said net-tools needed to be installed. Maybe they included the "Splunk Add-on for Unix and Linux" before? But it's no longer relevant for 8.x and 9.x as far as I can tell.

@bastelfreak @kenyon Can you review this?

Thanks everyone for working on this! I've tested the forked module and it's worked so far on my handful of testing servers, as soon as this is merged/released I look forward to promoting it to the rest of my node inventory. 🎉


Is there a reason why react-dom is used?

Line 107 of modules/mixins/Helpers.js is the only place ReactDOM is used, and from a very small test, it seems as though React.findDomNode works in place of ReactDOM.findDomNode. I am new to React, is there a reason why the react-dom package is used?

yes, v0.14 excluded some functions from it's core into multiple modules.


Adding certificate validation

Why
Adding certificate validation
How
Added some methods for each request to validate the need of a certificate refresh
Checklist

:tada: This PR is included in version 1.10.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How to get filled data from Acroform PDF

I need to get filled data from Acroform PDF? how to get it? Can anyone share the docs link or an example?

This is not a Q/A forum. Please use Stackoverflow for questions like this, especially if only remotely related to jsPDF. As I stated in the other issue (#2858), jsPDF cannot read existing PDF files.

@Nilanth with jsPDF you can create AcroForms and set the fieldName properly. Auto filling the value corresponding to the fieldNames happens in tools like Acrobat editor. Make sure you set the fieldName properly while creating AcroForm items. It's not the responsibility of jsPDF to fill the final values.
Being said that, if you happened to have this data while viewing/creating the jsPDF, you can just fill them in there.


Perform feature tests lazily, fixes #15

Drive-by fix: add Python 3.11 to classifiers

The fix is not complete yet, as the function is actually called in the constructor of _ConverterDict, so I'll need to revise.

Discussion with @uellue: in addition to building the whole conversion matrix lazily: instead of performing the feature test when constructing the matrix, only perform it if it is really needed, by putting a conversion function into the matrix, which itself performs the feature test.


Doesn't work in msys

In msys it doesn't react to entering y. Instead, I have to Ctrl-C and then it tries to execute y on the shell.

Thanks. I can reproduce it, but I don't know how to fix it...
On windows environment, _getch() is called to get input, but it doesn't work fine with mintty.


List of possible use cases and their requirements

In this issue we're collecting scenarios for Fobnail use cases which will be later added to documentation.
Scenario should contain:

Description of attested platform, including its:

use,
user,
owner.

How many such platforms are owned by the same owner, using the same Platform Owner certificate?

Does the same PO own other types of platforms, especially ones that also use Fobnail for attestation, which could entail longer certificate chain?

When attestation should be performed?
What is protected by attestation result?
What is the role of Fobnail Token?

In particular, what is the use of Fobnail Token's key, if any?

What appraisal policy should be used?

If I missed anything important let me know, I can add it to the list. I don't want to impose a strict format, it may be a list, running text, diagram or anything else, as long as it tries to answer the questions above.

Private Road Warrior Scenario
Overview:
A person, who is the PO and the User, is traveling with one or more laptops which will be out of their physical possession for periods of time.  These periods of time include when others may have physical possession, going through customs, is unattended, left in the hotel room, or the laptop is stolen/confiscated. Anytime a laptop is out of the possession of the User, they will want to ensure its contents cannot be accessed. When the laptop comes back into their possession, they will want to establish to the best degree possible that the device has not been tampered before using the laptop.
Threats

Passive information compromise - contents of laptop exposed
Active information compromise - installation of an agent for information collection when laptop is in use

Mitigations

Key protection

Disk encryption key is off platform, it is on fobnail
Remote attestation to fobnail is need to obtain encryption key

Platform integrity

Fobnail cryptographically bound to TPM

inhibits the deployment of TPM interposing

DRTM will capture tampering to Operating System environment
DRTM minimize impact of firmware tampering on executing system

Provisioning:
A provisioning system that is configured with the latest fobnail software and a certificate authority to represent the PO, if it is not already part of the fobnail software suite. The PO should implement the necessary protections for the provisioning system to mitigate the level of risk that an actor would seek to corrupt the PO's provisioning process.
Attestation:
Per the mitigations, the attestation should address that the correct Operating Software environment is in place and only at that time should it allow access to an encryption key. This can be addressed through a simple appraisal that ensures matching measurements against a RIM that was captured at provisioning.
Recovery:
This is driven by risk assessment, balancing the need to protect with the need to process. Recovery situations that need to be considered,

Loss or damage to the fobnail token
Damage to device rendering communication with fobnail not possible
Attestation failure of the device

Mattermost Personal Access Token Authentication
Overview:
Matterhorn is Mattermost TUI client which can utilize PAT for server login. It use custom command to obtain token. Fobnail could provide access to PAT only if platform was attested. It coule help in use of Mattermost and other applications using similar methods to access from potentially untrusted device (e.g. disposable laptop, disposable VM).


NIFI-5068 Script to automate parts of RC validation

Currently this script will

download and validate the hashes and signing
unpack the zip.
pull the commit and diff with the unpacked sources
build and run tests
validate that nifi starts

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

i dont think we should commit this into the codebase.  It could be fine to publish the bash script in the wiki page associated with release guide/validation.  We must also be clear this is good for things which are easily automated such as verification of sigs/hashes/build but for other things like actually testing nifi and the hard work of L&N review its an eyes-on game.

ok @joewitt, but did it work? ;)

How would we go about getting it on the wiki page?

@alopresto I have made the suggested changes.  Unfortunately the build has been pulled, so the script won't run until next release.

@ottobackwards i'd recommend just moving this to be a bash script made available on the wiki and close the PR.
You could

Propose an edit to the release process to make this available as an alternative way for folks who want to validate the RC (as an alternative to the current path)
Put this bash script on the wiki and link to it from #1.

Thanks

@joewitt I agree.  I'll see if I can edit the wiki ( if I have rights )

I do not have rights to create a page in the space from what I can tell

should have them now

I sent the email, I'll close this PR with the results of that when they are set

closing, not much demand I guess.


Any way to test syntax of twig templates?

There could be a situation of some legacy code cleanup in hundreds of twigs.
After that it would be nice to test syntax of all templates.
I've tried the php twig, but tokenize() doesnt throw a syntax error,
other methods like createTemplate() require full environment recreated like functions and filters.
Is there any way to check twig template syntax with the Twig.js?

You could take a look at the Symfony linter and see how they're doing it under the hood.

You could take a look at the Symfony linter and see how they're doing it under the hood.

I've just done $twig->parse() in php.
But anyway it's interesting whether it possible with twig.js

There's no built-in linter, but creating a new template and skipping the render call may do the same thing. Error handling during the template parsing isn't quite as robust as with TwigPHP, so you would need to do some testing to see if it functions as you expect.

Ok, will look at twig.js' render().
Or you could hint me

I was saying there's no need to call render, just create the template and the parser will run.

I was saying there's no need to call render, just create the template and the parser will run.

hmm, that easy? will try

You can also give twig-lexer a look. It is the lexer used by twing to lex a template.


The same field more than once in a view causes unexpected behavior

Describe the bug
I've added a field twice for an integer in an edit view. If the view has to update the value is reset to null.
Likewise, I tried adding more than one control for an image (view image, upload image, and select image) and they all displayed as the same type.
To Reproduce
Steps to reproduce the behavior:

Create a table with an integer and a file.
Create an edit view.
Add two fields pointing to the integer.
Add three fields pointing to the file, an image display, a file select, and a file upload.
Just running the view will display the file controls as the same type (instead of the three different designs in the view).
Add some data via the table editor.
Edit the data in the view.
The value of the integer field is set to null.

Expected behavior
No data should of course be set to null unless the field is emptied manually or something similar.
Otherwise, the exact expectation depends on what the design is. If it is to allow several versions of the same value, then the types should remain as configured in the view and the data should be updated as per the changes being made in the view.
If on the other hand the app is not designed for multiple fields, then I think a warning message when trying to save the view would be the least intrusive (there could be a use case for temporarily having more than none field per table value, perhaps. So preventing it by, for instance, removing fields that have already been used from the select box in the field might cause issues with some people's workflows).
Screenshots
N/A
Additional context
Saltcorn version:	0.8.1-beta.4
Node.js version:	v16.13.2
Database type:	PostgreSQL 13.9
Running on a docker image (docker-compose from the GitHub repo).

I think the problem lies in how Saltcorn builds the views, in this case editing. It seems as if the fields are assigned an unrepeatable ID in the construction iteration, but in the view if they are repeated

this is a consequence of using html forms. you can use tabs to have multiple fields in different tabs


how can i fix this?

I am using spyder for the first time but when I finished all the installation the following error message occurs:
The error is:
Traceback (most recent call last):
File "C:\Users\w8ulrick8w\Anaconda3\envs\tensorflow\lib\site‑packages\spyder\plugins\ipythonconsole.py", line 1572, in create_kernel_manager_and_kernel_client
kernel_manager.start_kernel(stderr=stderr_handle)
File "C:\Users\w8ulrick8w\Anaconda3\envs\tensorflow\lib\site‑packages\jupyter_client\manager.py", line 240, in start_kernel
self.write_connection_file()
File "C:\Users\w8ulrick8w\Anaconda3\envs\tensorflow\lib\site‑packages\jupyter_client\connect.py", line 547, in write_connection_file
kernel_name=self.kernel_name
File "C:\Users\w8ulrick8w\Anaconda3\envs\tensorflow\lib\site‑packages\jupyter_client\connect.py", line 212, in write_connection_file
with secure_write(fname) as f:
File "C:\Users\w8ulrick8w\Anaconda3\envs\tensorflow\lib\contextlib.py", line 112, in enter
return next(self.gen)
File "C:\Users\w8ulrick8w\Anaconda3\envs\tensorflow\lib\site‑packages\jupyter_client\connect.py", line 102, in secure_write
with os.fdopen(os.open(fname, open_flag, 0o600), mode) as f:
PermissionError: [Errno 13] Permission denied: 'C:\Users\w8ulrick8w\AppData\Roaming\jupyter\runtime\kernel‑a574ea7d3239.json'
How can i fix this problem??

There is no CLI repro here to answer the question. Those C:\ paths aren't WSL paths, they are Windows paths. If you've got a Windows install of Python, you'll probably find a better WSL experience if you purge your Windows path from $PATH. For example:
$ export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

When running Python on WSL, you'll have correct paths, and permission to those paths.
You will probably get more eyeballs on stackoverflow or a Anaconda, Python, tensorflow, etc forum. This is not WSL actionable.


[Design Spec] Collapsible

Jira ticket: https://jira.ets.mpi-internal.com/browse/DO-1690
### Tasks
- [x] Investigate if we need accordion and collapsible
- [x] Investigate the different platform needs
- [x] Investigate the product use cases
- [x] Spec sheet
- [x] ZH-documentation
- [ ] Spark figma component
- [x] Communicate the new component

⚠ Collapsible is only a behaviour

ZH specs section (inside Accordion specs because are directly related)
No Figma component

✅  Communicated and shared specs about Collapsible behaviour


[QUESTION] Performance and async_hooks

Thank you guys for your good job with this library.
Pino is a great logger, and nestjs-pino provides a very nice integration for NestJS.
However, I'm interested to know your point of view about performance question we can read about  async_hooks which is still in experimental status, and with the main reason of performance impact.
In addition to this (or linked with this), async_hooks is not recommended for production deployment.
As you mentioned in nestjs-pino docs, REQUEST scope can have performance issues. It's true and I fully agree.
But async_hooks have also some performance impact too.
It will be very friendly if you could share your opinion on this topic.
Thank you very much.

Hi, I actually don't know what to say. As a short answer I personally didn't reach some limitations, but my projects aren't highload. So if you have some you are free to use something else or make some improvements to this lib 🙂 If you want to see some benchmarks and compares of different implementation (async hooks vs request scope), sorry, but I don't have enough time for them, but they are more then welcome. Main goal of this lib is possibility to track logs from different contexts, and it's obvious it has some overhead, as any other functionality. When creating this lib I've chose async hooks instead of request scope because from my point of view unexpected creation of services depended on logger on every request is a wrong behaviour and could lead to bugs in some situations when you have some side effects on creation.
About not recommended for production deployment: it depends on project's limitation and requirements. This lib is based on cls-hooked which is quite popular, and from that fact I can say that it's performance (and async hooks's one) is satisfying a lot of projects including mine. Moreover when nodejs#12 will be unsupported I'm planning to replace it with AsyncLocalStorage.
i hope this info is helpful to you 🙂

👍  Thank you for your answer @iamolegga. I really appreciate.
I don't have any experience yet with async_hooks, it's why I was a little worried about performance after some readings.
Maybe, I should take in account this performance topic, but without overestimating it.
Thanks again!


Theme upload locales error

Hi There,
I am getting the following error when using Theme Upload.
Asset Perform Update to templates/customers at host baharistore.myshopify.com
Status: 422 Unprocessable Entity
Errors: Must have a .liquid file extension
I don't know whats wrong, i just folowing step from https://shopify.github.io/themekit/#installation
Please help me to fix this.
Thanks
My Environment
OS (including version):Windows 10
Themekit version: ThemeKit 0.7.5 windows/amd64
Ignore Files(if any):

Does the file have the .liquid file extension?

thank you for replying, it's has succeeded no more error

Hi @maedisophie
I also faced this kind of error.
Could you please let me know how to fix this kind of issue?
Thank you.


AmazonCloudFrontUrlSigner.BuildPolicyForSignedUrl() method doesn't support not passing DateGreaterThan

The AmazonCloudFrontUrlSigner.BuildPolicyForSignedUrl(...) method has code  intended to support not having a DateGreaterThan value ("epochDateGreaterThan == null ? "" :..."). However, this doesn't work becuase the DateTime datatype isn't nullable so epochDateGreaterThan == null is always false.
Given that you need backward compatibility and likely want to be CLS complaint, I recommend you add an overload without the DateTime epochDateGreaterThan parameter.  Note, the AmazonCloudFrontUrlSigner.GetCustomSignedURL(...) methods call this one and should be overloaded/changed to match.
Also, since wildcards can't be used with canned policies, the BuildPolicyForSignedUrl is useful even when you only want to specify resourcePath and epochDateLessThan.  It would be nice to have an overload or default parameters which supports that use case.
Finally, the epochDateLessThan == null check at the beginning of the BuildPolicyForSignedUrl method will always be false and so has no effect and can be removed.

+1

+1

Good catch, I'm surprised the compiler didn't complain about doing null comparisons on a null type.
I'm leery of overloads because they have tend to explode in the number of needed overloads. I'm thinking of changing the logic to not include epochDateLessThan if it equals DateTime.MinValue and epochDateGreaterThan if it is equal to DateTime.MaxValue. What do you think?

I understand your hesitation about overloads, this does seem like a case where the overloads might multiply.  The use of DateTime.MinValue and DateTime.MaxValue is reasonable, as long as it is very clearly documented.  I have seen other APIs declare constants equal to the MinValue and MaxValue to make the code more readable (for example Cache.NoAbsoluteExpiration).  Personally, I'd rather see the parameters changed to nullable DateTime.  I think null more clearly indicates no limit.

Switching to nullables would be preferred but a breaking change I don't want to make. We'll be sure the documentation clearly explains the significance using MinValue and MaxValue

The incorrect null check has been removed and new overloads have been added for BuildPolicyForSignedUrl and GetCustomSignedURL that do not require passing the activeFrom (DateGreaterThan) parameter.


@putuoka perhaps the download speed is too slow, otherwise an error would occur. You can try downloading the engine manually from this link - then place the archive in the ./data/engine or ./PATH_TO_ENGINE/engine folder, where PATH_TO_ENGINE is the path to the engine if you install it yourself.

          @putuoka perhaps the download speed is too slow, otherwise an error would occur. You can try downloading the engine manually from [this](http://downloads.bablosoft.com/distr/FastExecuteScriptProtected64/26.0.2/FastExecuteScriptProtected.x64.zip) link - then place the archive in the `./data/engine` or `./PATH_TO_ENGINE/engine` folder, where **PATH_TO_ENGINE** is the path to the engine if you install it yourself.

Originally posted by @CheshireCaat in https://github.com/CheshireCaat/puppeteer-with-fingerprints/issues/30#issuecomment-1652838948

I downloaded and copied this archive into data/engine. Nothing has changed. still getting "The browser is downloading - this may take some time." and fetch error. HELP
error screenshot

code screenshot


Switch to faster serial

This pull request replaces the Pi Pico SDK serial over USB CDC with a custom implementation in TinyUSB that is typically faster.
It aims to be backwards compatible, though it may also allow commands terminated in only newline (\n) to be accepted in addition to the carriage return + newline termination (\r\n).
Not ready to merge yet, as a binary mode should still be added for even faster programming.

Thanks @carterturn , I'm keen to dig into this once it's ready. The speed improvements shown in the other repo certainly seem to make this worthwhile!
I'd like to merge this after #26, so keep that in mind (it'll be a squash merge though so there is no point rebasing yet). If you had time to review that PR too, I would appreciate it. It should mean you wont need to include the uf2 files explicitly (they'll get built by GitHub actions and uploaded as an artefact for testing, and then built for a release after merging and tagging)

Well, I see what the problem was when I tried this. I included fast_serial as native C++. That did not work.
Also, I think it is really interesting that the binary blobs are less than half their size when using this serial comms mode. That's kind-of wild.

Binary mode is now implemented, and I have tested programming for a single-clock-pulse sequence.
I will try to setup a more elaborate test environment soon (and then get performance results). If someone else has a Windows test setup, it would probably also be good to check performance there.
Waiting to merge for #26 sounds good. I am a bit pleased to have fewer binary blobs in git repositories.
Curiously, I ran into compilation issues when not using the "extern C" directive, but I suspect there are some cmake options that could fix that. I suppose this serial code does not have many features that the pico SDK version does have, though that is indeed a surprising difference in executable size.

@carterturn I've had a go at doing some performance tests and I'm not getting as impressive of results as for the prawn_do.
Basically, there is a floor on the binary write of ~200 ms regardless of the number of instructions and it appears to be the same floor as doing individual serial writes.  I don't see increases in timing until at least 150 instructions are sent for the block binary (obviously the individual writes are much slower).
Test script with prawn being the serial interface handle
instr = 250
dummy_data = np.tile([[100, 4],
                      [1000000, 1]],
                      (instr, 1))

# individual serial writes
for i in range(dummy_data.shape[0]):
    prawn.write(f'set 0 {i:d} {dummy_data[i,0]:d} {dummy_data[i,1]:d}\r\n'.encode())
    _ = prawn.readline().decode()

# block binary of same data
prawn.write(f'setb 0 0 {dummy_data.shape[0]:d}\r\n'.encode())
serial_buffer = b''
for i, (dur, reps) in enumerate(dummy_data):
    serial_buffer += struct.pack('<I', dur)
    serial_buffer += struct.pack('<I', reps)

prawn.write(serial_buffer)
resp = prawn.readline().decode()

Timing summary using %%time in a jupyter cell for each of the above vs number of instructions. I'm on a windows machine with python=3.10.

instruction number
individual time (ms)
block time (ms)

10
220
215

100
297
205

200
381
216

500
621
228

1000
1070
262

2000
1880
310

5000
4510
459

10000
8800
697

It would appear there is something in the firmware that is really bogging us down. Nothing obvious is jumping out at me. Only real differences I see are that we recalculate the address_offset + addr * 2 more than we need to (4 times per loop regardless of branch), or the more complicated else/if tree. But that doesn't seem all that likely. Note that my dummy data doesn't include any wait or stop instructions, so we aren't even traversing all the branches.

 The jupyter cells I was running those timing snippets in have a readlines call and my serial timeout was set to 200ms. Here is the updated timing table. As expected, the binary writes are much, much faster.

instruction number
individual time (ms)
block time (ms)

10
6.8
1

100
77
5.2

200
153
8.3

500
378
18

1000
834
39

2000
1780
96

5000
4220
281

10000
8610
480

As another optimization that may be worth implementing, the for-loop building of the serial buffer string doesn't scale especially well to these very high values. If the data we want to write is in a well-ordered numpy array, we could use the tobytes function instead which appears to scale much better.
instr = 4000
seq = np.array([[100, 4], [1000000, 1]], dtype='<u4')
dummy_data = np.tile(seq, (instr//2, 1))

# for loop
serial_buffer = b''
for i in range(dummy_data.shape[0]):
    serial_buffer += struct.pack('<I', dummy_data[i,0])
    serial_buffer += struct.pack('<I', dummy_data[i,1])

# numpy
serial_buffer2 = dummy_data.tobytes()

serial_buffer == serial_buffer2  ## returns True

Timing using python 3.8 and %%timit magic

instructions
loop
numpy

10
7us
95ns

100
76us
164ns

4000
6.4ms
889ns

20000
83ms
3.7us

May be worth implementing that in the labscript device.

Thank you for the updated test, that would have been a confusing bug to try to replicate.
I think the even more numpy based buffer construction looks great; I added it to labscript-suite/labscript-devices#112.


Parking Slot Request - Logic

this issue will refer to the logic of the screen that preset the parking slots to choose from

Or if you have any special request to functions please write them here so can implement them @ortroyaner


Sealed trait model generation

This would be fairly nice to have so we can generate readers/writers for a parent type that have several inhabitants.

Closed with f21fbe6fead27294e119c9ca13fc48c08c4a74ff and 391f402975852319b754c7d50689fbb1cea7994e.


Fix async databricks job failure due to provider release

A new version of Databricks apache-airflow-providers-databricks==3.2.0rc3 while running dag it fails due to TypeError: _get_hook() missing 1 required positional argument: 'caller'. OSS PR link is here
So this PR fixes the error by adding the argument caller and also supports backward compatibility for the previous version as well.
Closes #581

Can you please link the corresponding OSS PR in the PR description and the Zenhub ticket which has the changes causing this error ?

Yes added the OSS PR link .


No help system

There is no help system within the application that I can find.

Help webpage added


Pathfinder .38 debug off

turn debug off
fix default value for 6 fields in npc page

just going to upgrade to .40 instead


Section "Prepare the input data" needs to be updated

[Enter feedback here]
The screenshot related to create an ioT Hub has changedm the service tier can now be selected on the "Instance details" section. It is not located at the Management page any more.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 9028ffb4-d3fb-e5ee-3e3f-fe3d7db65f04
Version Independent ID: 173bbf71-a44b-0864-b43d-a6b580bba03f
Content: Quickstart - Create a Stream Analytics job by using the Azure portal
Content Source: articles/stream-analytics/stream-analytics-quick-create-portal.md
Service: stream-analytics
GitHub Login: @ajetasin
Microsoft Alias: ajetasi

@alberto-morillo
Thanks for your feedback! We will investigate and update as appropriate.

@ajetasin
Could you please review add comments on this, update as appropriate.

The issue is fixed now. Thanks.
#please-close


fix/docs: Update docs to reflect returned object from genAuth functions

Coverage remained the same at 94.845% when pulling ad0ca3c8e86e52d723be1ae86242a07e40618c4c on joshuef:FixUriGenDocs into 585e45d78fda92934afc196488a1f2f712374551 on maidsafe:master.

it's looking like the naming just needs to be consistent, and seems like the native FFI doesn't really mind what it's called (having some of one and some of another is causing test failures, wheres straight up swap seems fine)


Improvements to LDAP extension, with nickname support and meaningful error messages

Added Nickname support, with the ability to use any search field that is set within settings.
Please note That Nicknames extension must be enabled to be able to save Nicknames, placeholder will display givenname,sn as a example which is 'First Name' 'Surname' to be set as the Nickname for user profile
Added LDAP error messages for users, instead of the 'Error has occurred' html response. This will fix #48 issue.
Added Setting to allow admin's to display detail errors or not, this is a toggle in settings:

Detailed error response will display incorrect LDAP binding:

Detailed error response will display if LDAP search for account exist:

Detailed error response will display if LDAP account password is incorrect:

Will also fix #39 issue.

Implemented multiple LDAP domain settings, overhaul settings to display settings into sections. Added select2 to handle dropdown and multiple selection, pre-register LDAP fields options for easier usability.


Azcopy won't work on the mac as it is blocked by the "allow apps downloaded from appstore and identified developers" policy

Which version of the AzCopy was used? 10.8
Note: The version is visible when running AzCopy without any argument
Which platform are you using? Mac
What command did you run? Any doesn't matter
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
What problem was encountered? "Azcopy" cannot be opened because it is from an unidentified developer
How can we reproduce the problem in the simplest way? Get a mac. Turn on the "allow apps downloaded from appstore and identified developers" policy. Download AZcopy and try to run it.
Have you found a mitigation/solution? no unless we manually enable it on each computer that needs it (which is not a workable solution).

The fact that this doesn't seem to be notarized seems a significant oversight. If AZcopy is used to perform admin tasks on mac (e.g. used by a script in Intune) then users will see on the following error message: -

This also seem inconsistent with other software for example Powershell. The Powershell build process seems to have the notarization step built in: -
https://github.com/PowerShell/PowerShell/blob/master/tools/releaseBuild/azureDevOps/templates/mac-file-signing.yml

Hey @PaulG77 ,
AzCopy version 10.10.0 has been released and we've taken care of notarizing the binaries. Please go ahead and use it. Reach out to us if the issue persists.

I'm having the same issue with the latest version. How can I download 10.10 if that version was notarised?

Hey @jimmyville ,
Which version are you using? AFAIK our latest MAC builds are signed by Windows ESRP. Try downloading 10.14.1 and give it a go maybe?

I've downloading the latest version from the Getting Started page: https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10
I'm still receiving the unidentified developer error.

I am encountering the same issue with version 10.16.1 (azcopy_darwin_amd64_10.16.1.zip was the download from Microsoft)

the issue still exists as I tried downloading the latest - azcopy_darwin_amd64_10.17.0
from https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10 for macOS

Yeah I tried it today and it still gives this error

Same here.

Same here


Index data getter with out params

Allocating a TypedArray is probably around 64 bytes, maybe a bit more depending on the implementation. However, copying index data is probably moderately large in a lot of use cases. Thus, here I would recommend:

Keep the indexCount and meshIndexType getter, no harm here
Remove the getIndexData
Add a new getter called indexDataView, keep the code from get indexData in this
Make get IndexData use get indexDataView, and add a deprecation message stating to use get indexDataView instead.


Figure out search-index in the browser

Do a little research and testing on search-index in the browser to get more comfortable

Got it working in v0.0.3 https://github.com/eklem/crawler-in-browser/commit/039d170fd37bc1ae57a0d513e60bfc5d71cebc0a


Add New Feature: Create A New Tink Keyset With A Supported Tink Key Template

Modify the create command. Add a new option: create a new Tink keyset that contains a single fresh Tink key with a supported Tink key template. This Tink keyset will be stored on Knox directly.

Hi Jeremy,
Thank you so much for your great comments! I have revised my code base on you comments and submitted a commit.

Hi Devin,
Thank you so much for your great comments! I have revised my code base on you comments and submitted a commit.


Repeating Request notifications

Description
For some reason some request notifications will be repeated every day at 1.30am and I don't know why.
Version
1.2.1
Steps to Reproduce
I am not 100% sure, doesn't happen all the time. Maybe if I interfere with the selection process?
Screenshots

Logs
No response
Platform
desktop
Device
not applicable
Operating System
not applicable
Browser
not applicable
Additional Context
No response
Code of Conduct

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

Same as https://github.com/Fallenbagel/jellyseerr/issues/176 and https://github.com/Fallenbagel/jellyseerr/issues/215 I think

I'm hoping this gets resolved when individual episode requesting is implemented. I feel like when jellyseerr/overseerr detects an episode that's not in the jellyserrr/overseerr database (mostly special seasons) it triggers a repeated notification everytime. I'm not entirely sure

I also have this problem. It's kind of annoying, but I don't want to put pressure on the devs, it's a minor problem.

:tada: This issue has been resolved in version 1.5.0 :tada:
The release is available on:

v1.5.0
GitHub release

Your semantic-release bot :package::rocket:


Created directory to host pre-trained machine learning models

Created directory to host pre-trained machine learning models

Closing this as we are currently evaluating the strategy.


update_metadata: drop the term Blob in structure names

@mjg59 pointed out Blob was a confusing choice because that term is used
in many other contexts in this code base. Instead match the existing
InstallOperation name and use InstallInfo and InstallProcedure.

lgtm


Possibilty to choose decimal and thousands separators

Would it be possible to customize the separators for decimal and thousands?
I'm italian and here we use comma as decimal separator and point as thousands separator.

I will take a look at this for the next release.
However, I can not promise anything. I think the separators are determined by the browser/language of the browser so I am not sure if we can change anything about this.
Anyway, I will let you know via this issue after seeing what we can do!

I'm not sure I understand what you mean but my browser is set to italian but I'm still getting non - italian separators.
If it is easier you could make 2 text boxes in which you specify the two separators you want,without considering any regional setting of the browser

I must confess I don't really know how HTML/CSS/JavaScript handle separators.
On the top of my head I would say that we currently don't specify what spectators to use (thus leaving that to either the browser or one of the coding languages).
But this does not mean that we can not force a type of separator and include this as a setting.
I will have to look more carefully into to this.
I hope to find a fix! in bocca luco :)

As far as I know, in Javascript, as long as Number.toLocaleString (or any other formatting method) method is not called, the default number format (. as decimal separator, no thousands separator) is used in any browser.
As we're not using this method anywhere in CM, the only formatting method in effect is CM.Disp.Beautify so it shouldn't be too hard to enable separators customization, I suppose!


STORY: First Rotor

Creating the first working rotor would be a good first step in the rotor system.
A way to do this could be to create a 26-element array that stores <Key, Value> pairs.
Every time a new character goes through the rotor, we should increment the rotor by looking at the next element.

WOW