Modernizing code & build

As per one of the to-dos, I've started working on modernizing both the code and the build pipeline.
Right now, one of the main drawbacks for contributors (such as myself - one of the issues and PRs I put forward required a partial rewrite due to this) is that the build pipeline relies extensively on make, and is effectively a concatenation of all javascript files present in lib/. This does not provide opportunities to use a modern toolkit (such as webpack) to properly "build", nor a testing library like mocha to operate on a non-built version.
The plan of battle, with current status, is as follows:

[x] Swap out the Makefile and replace it with a webpack configuration and associated tools
[x] Port all the tests to mocha (with istanbul for code coverage)
[x] Go through the code, reworking important bits of it to both clarify it, and to leverage some performance gains through the use of more complete code structures
[ ] Build e2e tests operating on both a server-side environment (nodejs) and a headless browser to guarantee that the final build fulfils expectations

My working branch is over at code-improvements on my fork. Once we're back in a stable state, I'll put a PR forward.

@srenauld , thanks very much for the contribution.

Status update time!
Turns out there were a lot more things that could be done, low-hanging fruits and improvements. In particular, I've also put the elastic and lunr back into elasticlunr.
The branch I've been working on, which is much closer to being a PR candidate, now has the following changes made to it:
Indexing:

Each field is now a separate entity, complete with the ability to add/edit pipeline elements, define whether the field's full-text input needs to be stored and whether the TF/IDF elements need to be kept. Goes a long way to addressing #103, #43
Term positions are stored (can be enabled/disabled). This allows the user to highlight documents. Featured mention in #91
Batch addition, updates and removals! As the costliest operation in index management is having to recalculate the IDF (it depends on the # of terms in the index), people adding or modifying a lot of documents may find this useful.

Search

The search function now supports three dialects. In order to easily allow people to move to this library (preferably without rewriting most of their queries), the fork now supports three dialects: the one present in lunr, elasticlunr and a subset of elasticsearch DSL. Everything maps back to the elasticsearch DSL, and this should be considered for advanced queries. There are a couple of examples in the tests. In particular, this goes a long way to fixing #86
Field-length norm is now a factor in scoring. This should go a long way to boost relevance
Every part of the search now has a firmly-defined external API

Storage

I went through and tried to improve the way an index is serialized. The new format is more than just a plain toJSON() of the index. This also opens the way for space-saving optimizations. The old format is still fully importable

Tests
Basically everything is reworked. A ton of test cases were testing the internal state of objects more than whether a given feature worked. This is probably the biggest change.
A couple of tests were added to cover new components (the new index and DSL) or third-party library support (lunr-languages)
My next step is documentation and benchmarks.

@srenauld How's this effort going?

@smurrayatwork on this, I've done very little due to a PR being frozen for months. On other fronts, I almost have a plug-in for this library for nextjs, which may or may not be useful to some.

@srenauld, @weixsong   - given that this PR is merged, is there anyplace I can look up usage? current docs are out of date.
With default options, an index is now more than 2x the size of the one produced by lunr.js
ElasticLunr seemed very appealing due to ability to store fields & being able to do an 'AND' search on all terms - but without usage info, it's hard to use.

@raghur Hello, and sorry about the delay!
I'm in the process of working on a side branch for this purpose specifically. The version currently available on npm is still 0.9.5 (i.e. before the changes). As such, all the old documentation is up to date, and so are all the specifics.
The branch I am working on (intermittently, admittedly. I've had a ton of things coming my way recently) is over here. I wired together a small example leveraging the gatsby plugin to both enforce backward-compatibility (wouldn't want to wreck a plugin by accident) and to showcase the use.
Regarding the index size, if you are using the new version, I'd be curious to see what you are indexing. This is the kind of feedback that is extremely valuable, as I can change the index format in the new version while still remaining backward-compatible (the old was a straight JSON.stringify() of the inner state - the new is a bit smarter). As nobody is currently using it (AFAIK), I'd be super interested to know what you are indexing and what your results are.

@srenauld - thanks for responding.. No problem at all.
TBH, I went through some of your changes and while I absolutely LIKE the features you list, I ran into a few issues (hence the reason I picked master instead of a released version at NPM). Having a working example is great for starters and exactly the thing I was missing picking up master here!
Content I'm indexing is from my blog - json is here - https://blog.rraghur.in/index.json. It isn't a large blog by any means and index was coming up to about 4.8MB (Lunr produced 2.3 - 3MB) I think.
code to build index is here https://gitlab.com/rraghur/rraghur.gitlab.io/blob/elasticlunr/build-index.js
Also, options like not to storedocuments (I didn't want that on the full text blog content), etc weren't working and I was just running into too much. So finally wrote the comment here and switched back to lunr.
I'll try your branch and gatsby example early next week...

An option like storeDocuments to control whether fields are persisted to the index would be VERY useful for me. But it doesn't seem to work in v0.9.5. Does anything like it exist?


Integer constant validation

I had a bug in my code where I was passing a float to i32.const intermittently.
Would you consider validating that the passed in value is a valid integer at the call site of i32.const(123) (and other integers)? Otherwise it errors at the BigInt conversion which is hard to correlate with the actual code that generated the call.
(I'd be happy to open a PR with direction of a good place to do this check, I was doing it in baseInstruction and just checking the i32 and i64 const instructions, but this could be done more generally.)

Ah that's good feedback, thanks @Mike-Dax!
I think I want instruction-specific validation to live locally next to the instruction definitions. So what I'm going to do is add another instruction factory, say baseInstructionWithValidation(), which takes an additional validation callback that runs before creating an instruction. And then define i32.const and i64.const using that factory

fix merged and released with 0.2.4!

Amazing, thank you!


Trilha Musical

Trilha Musical do Jogo:
Floresta:

MUSIC_DryLeaves.zip

MUSIC_Rusted_Gate.zip
MUSIC_Underground.zip
MUSIC_FlowingWaters.zip
MUSIC_DryLeaves.zip


Update snippet3605.fs

F# style event usage.
Summary
Describe your changes here.
Fixes #Issue_Number (if available)

ping @dsyme for style review.


feat: add helper function defineLazyMountComponent

Modal are often not opened immediately when entering a website. They usually require some action, like click button to trigger their appearance.
To handle this, we can use defineAsyncComponent to load the modal component dynamically:
<script setup lang="ts">
import { defineAsyncComponent, ref } from 'vue'

const LazyCustomModal = defineAsyncComponent(() => import('@/components/CustomModal.vue'));

const isActive = ref(false)
</script>

<template>
  <LazyCustomModal v-model="isActive"  />
</template>

However, this approach only splits the component into a separate chunk, which will still be loaded when entering the page, even if we don't open it.
To achieve delayed loading, we can implement the following:
<script setup lang="ts">
import { defineAsyncComponent, ref } from 'vue'

const LazyCustomModal = defineAsyncComponent(() => import('@/components/CustomModal.vue'));

const isActive = ref(false)
</script>

<template>
  <template v-if="isActive">
    <LazyCustomModal v-model="isActive"  />
  </template>
</template>

But a problem with this method is that the component will be unloaded when the modal is closed. So we need to do something special to handle this:
<script setup lang="ts">
import { defineAsyncComponent, ref } from 'vue'

const LazyCustomModal = defineAsyncComponent(() => import('@/components/CustomModal.vue'));

const isActive = ref(false)
const isModalMounted = ref(false)
</script>

<template>
  <template v-if="isActive || isModalMounted">
    <LazyCustomModal
      v-model="isActive"
      @vnode-mounted="isModalMounted = true"
    />
  </template>
</template>

This solution might seem a bit wordy, so I attempted to add a new method called defineLazyMountCompone to encapsulate the above logic:
<script setup lang="ts">
import { ref } from 'vue'
import { defineLazyMountComponent } from 'vue-final-modal'

const LazyCustomModal = defineLazyMountComponent(() => import('@/components/CustomModal.vue'));

const isActive = ref(false)
</script>

<template>
  <LazyCustomModal v-model="isActive"  />
</template>

I hope this simplified explanation is easier to understand. If you have any questions, feel free to ask!

@Mini-ghost
May I ask you to add at least one use case for defineLazyMountComponent() inside of the /viteplay?
I like the defineLazyMountComponent(), but I think it should be more easy to use the function. Is it possible to have a lazy prop supported by VueFinalModal.vue?

@hunterliu1003 In my case, I often encapsulate modals into components, such as drawers. For these kinds of components, I won't use useModal, but I will explore how to integrate them.

Usually useModal I would use with asnyc component, it will be loaded as needed, so I think useModal is not needed when using defineLazyMountComponent, defineAsyncComponent is enough


s3 bucket search, keys not yielding full results

current implementations of list_objects_v2 yield maximum 1000 results (for search as well).  Need to modify directory method(s) to generate full bucket contents.  Consolidate API.

find updated.  Contents_ now returns generator object.  Find allows keyword all=True/False to check screen entire bucket.


Fix broken link to official libraries

Hey @jacobpgn
Managed to fix one broken link (official-libraries --> #official-libraries) - though couldn't work out how to fix the other one.
Looks like Markdown automatically translates http://[your domain]/gocardless/confirm into a broken link going to http://[your/
The broken link is found on four pages:

https://developer.gocardless.com/ruby/
https://developer.gocardless.com/python/
https://developer.gocardless.com/php/
https://developer.gocardless.com/node/

There's also a broken e-mail link on https://developer.gocardless.com/pro/ - not quite sure how to fix this?  You can find it on: "We are actively seeking feedback on this API so please contact us with any suggestions."

@jacobpgn

Nice one! Will look into the pro docs too


pkg_resources.DistributionNotFound: The 'requests-cache' distribution was not found and is required by NetEase-MusicBox

Traceback (most recent call last):
File "/usr/bin/musicbox", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python3.7/site-packages/pkg_resources/init.py", line 3241, in
@_call_aside
File "/usr/lib/python3.7/site-packages/pkg_resources/init.py", line 3225, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3.7/site-packages/pkg_resources/init.py", line 3254, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3.7/site-packages/pkg_resources/init.py", line 583, in _build_master
ws.require(requires)
File "/usr/lib/python3.7/site-packages/pkg_resources/init.py", line 900, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3.7/site-packages/pkg_resources/init.py", line 786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'requests-cache' distribution was not found and is required by NetEase-MusicBox

For the users of archlinuxcn repo, I re-added this package, which was removed during the previous cleanup. However, there may be other design issues with its cookies mechanism and need to be fixed.

please try using pip or git clone


Separate Django app for product description - Saleor

We sell music media.
The description of each product takes into account combinations of data regarding composers, compositions, artists per instrument (pianist and conductor), artists per media, artists per track etc.
Inevitably, we have created a dedicated Django application that encapsulates the logic responsible for building the description of each product and this app uses Django admin.
How can I effectively integrate my app to Saleor in order to include all the necessary information in the description?

Considering that you're running it as a separate app next to Saleor (if I understand correctly), I think you should build some synchronization script that would update descriptions in Saleor whenever you change them in the other app. You could use just a Python script that connects to both databases and exchanges data between them. It could be implemented as a Django command in either of the projects. You could run it on demand when the changes to your descriptions is first saved, or periodically with some task manager. You could also try to use our GraphQL API to update products in Saleor.

OK, I understand: I should consider Saleor a stand alone project and add the description to the list of the data that will periodically be updated, such as quantities that change regularly from other points of sale, for example.
I am just browsing the API docs, it is indeed a great tool. Thank you!


Track Site_of_care, add to Patient_role values

FL PHD has these two requests:

Add the values Student and Teacher to the set of possible Patient_role values.
Send the type of facility providing care, the Site_of_care to the Hub.   This is actually part of the AoE requirements, that we haven't been providing.

To see the gory details of what HHS wants, go to https://confluence.hl7.org/pages/viewpage.action?pageId=86967947, then search down to where it says, If YES, what type of residence is the congregate care setting?
See also https://phinvads.cdc.gov/vads/ViewValuhttps:/phinvads.cdc.gov/vads/ViewCodeSystemConcept.action?oid=2.16.840.1.113883.6.96&code=43741000
Here's the list of possible values for Site_of_care.    Pretty sure we do not need all of these initially:

name: site_of_care
system: SNOMED_CT
referenceUrl: https://www.hhs.gov/sites/default/files/hhs-guidance-implementation.pdf
values:
-   display: Hospital
code: 22232009
-   display: Long Term Care Hospital
code: 32074000
-   display: Secure Hospital
code: 224929004
-   display: Nursing Home
code: 42665001
-   display: Retirement Home
code: 30629002
-   display: Orphanage
code: 74056004
-   display: Prison-based care site
code: 722173008
-   display: Substance Abuse Treatment Center
code: 20078004
-   display: Boarding House
code: 257573002
-   display: Military Accommodation
code: 224683003
-   display: Hospice
code: 284546000
-   display: Hostel
code: 257628001
-   display: Sheltered Housing
code: 310207003
-   display: Penal Institution
code: 57656006
-   display: Homeless
code: 32911000

Ugh...long lists. From the way it's described (conditioned by the "patient in congregate care setting?") it sounds like we could put this in the facility setup and autopopulate it, either with or without an override. That saves hassle for the tester.
From the way it's structured, it sounds like this would not be answered for staff at these facilities?

Ugh...long lists. From the way it's described (conditioned by the "patient in congregate care setting?") it sounds like we could put this in the facility setup and autopopulate it, either with or without an override. That saves hassle for the tester.
From the way it's structured, it sounds like this would not be answered for staff at these facilities?

@jimduff-usds - do we explicitly need "teacher" or is "staff" good enough?
Also, if we send through data about the type of organization that is doing the testing does that meet their needs?
@jlusds FYI

Adding this to #1187

Patient_role:   Given that this request is pretty old at this point, I think Staff should be sufficient for a Teacher role, especially considering there are many folks working at a school that are not teachers.
Regarding  'if we send through data about the type of organization that is doing the testing does that meet their needs?', it sounds like you are proposing an new field, perhaps facility_type (with values like "School", "Nursing Home" etc)?   I guess the problem is that this sounds very close to the Site_of_care field reference above.     But Site_of_care doesn't include 'School', near as I can tell.   I looked around at PHINVADS a bit and didn't see any vocabulary that included something like 'School' as a facility type.

@MauriceReeves-usds , any thoughts on either of these?

captured work that is still left in https://github.com/CDCgov/prime-simplereport/issues/2040


Files not saved or deleted

Hey, I'm testing this PHP boilerplate on my local machine (Mac) running Apache/MySQL/PHP 7.
When uploading a file, two folders are created in the tmp directory—one contains only a .htaccess file and the other contains a .htaccess file and the uploaded file. I'm then running into a couple issues:
When clicking the Submit button the file is not saved (to the default uploads folder, I presume).
When I "tap to undo" the tmp file is not deleted, which I thought is supposed to happen.
Any suggestions?

Thanks @rikschennink–
There are no Apache errors. And yes, I see one transaction in the network tab (if I'm understanding that correctly).
When I upload a file here's the Response from the network tab:

When clicking "tap to undo", the Request Payload (Headers) shows that same error.
When clicking Submit:

Thanks for the help! I'll be implementing Slim after I get this figured out too.

It seems the received data is malformed or is handled by an incorrect method.
Are you using the File Encode plugin?
Can you post the settings for the FilePond server option?

I'm using this boilerplate as is, minus Vagrant and VirtualBox.
FilePond.setOptions({     server: 'api/' });

@cd13sr The repository was still using the version of the API that did not support metadata, I've just uploaded the new files, should work correctly after replacing them.

Thanks—I'll give it a try soon and let you know.

FYI, it seems to work great now, thanks!


Include /etc/map url mappings in archetype

This PR includes changes done for multiple RTCs.
If the user enters domain on archetype execution, configs specific for publish environment will be generated under /etc/map.publish and the corresponding config update will be done in jcrresourceresolver config to point to map.bulish directory for publish envs.
secondly by default 2 templates will be generated(during archetype execution) homepage and landing page with a predefined structure and 2 experience fragments for header footer related to the custom project will also be generated during archetype execution and associated with the pages created using these templates
In addition to this , during archetype execution the user will be prompted for creating runmode configs based on the names of environments entered by the user.
The content skeleton has also been updated. By default for the mid market blueprint projects, new content heirarchy has been introduced. /content/<content_folder_name>/us/en
work is being continued on the content skeleton, based on user input the appropriate content skeleton will be generated.
updated the content page type component to render only a responsive grid instead of OOTB comps included.
A standard data layer js has also been added.
Related Issue
https://github.com/adobe/aem-project-archetype/issues/163
https://github.com/adobe/aem-project-archetype/issues/179
https://github.com/adobe/aem-project-archetype/issues/174
Motivation and Context
These updates are done for mid-market blueprint projects
How Has This Been Tested?
tested execution on local by updating the artifact id, building it and then generating the project by executing archetype using updated artifact id.
a sample project has been generated and is going to be demonstrated next week.

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

Checklist:

[x ] I have signed the Adobe Open Source CLA.

Please break down the PR into separate pieces for each new feature/improvement, for easier review!

Creating seperate PRs.

Please break down the PR into separate pieces for each new feature/improvement, for easier review!

Creating seperate PRs.
https://github.com/adobe/aem-project-archetype/pull/192
https://github.com/adobe/aem-project-archetype/pull/191
https://github.com/adobe/aem-project-archetype/pull/190

Kindly close this PR without merge.


uses protocol that request comes in on

Protocol-relative URLs are now considered an anti-pattern. If the resource is available through HTTPS, it should always be accessed via HTTPS (regardless of the protocol via which the request came in). See the update at the top of this page:
http://www.paulirish.com/2010/the-protocol-relative-url/


Make scenarios that create lports usable with Rally runner for repetitions and parallelization

Currently any scenario that involves port creation cannot be used with Rally serial or constant runner when number or repetitions (times) is greater than 1 and/or number of parallel runners (concurrency) is greater than 1, unless we ignore the fact that multiple ports will be assigned the same IP address.
We could address it either by picking IP addresses at random (from the subnet range) or keeping global state to track which is the next unassigned yet IP address from the pool.
Not using Rally runner for repetitions prevents us from getting a timing profile from Rally, i.e. duration over iterations for each atomic task. Example of such profile can be seen here:
https://people.redhat.com/jsitnick/ovn/create-and-bind-200-ports.html#/OvnNetwork.create_and_bind_ports/details

Another idea instead of random(), we could look at providing the scenario with a large subnet -- ie 192.168/16 -- then allowing the scenario to break this into /24s (or whatever the user passes).
This could be two additional fields we pass to the scenario -- allow the code to work as-is, but for people that want to take advantage of having concurrency,etc they pass these additional fields to get the benefit.

Good thought. When it was implemented, I didn't find a good way for allocating subnet to rally tasks and ip to runners, the subnets used by tasks were planned statically. For setup 20K port as background pressure as fast as possible, we run multiple rally tasks concurrently.
If you are working on performance test and require to use parallel runners, could you please implement this feature? We(eBay SDN team) are working on OVN overlay scalability test recently, we are happy to review and may benefit from this feature as well.

@l8huang thanks for explaining why it was initially done like that. We're planning to work on it.

Great!


Improve the UI of the About Page

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
About Page
The about page is looking old and it needs the improvement in the UI
Describe the solution you'd like
Solution steps
1 I can make cards for the different sections and  add animations to the page
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

I want to work on  the issue , please assign me

I would like to work on this task .


TypeError: object of type 'NoneType' has no len()

When I run "python3 wafpass.py -u http://www.xxx.com" it shows error:
Traceback (most recent call last):
File "wafpass.py", line 300, in
main()
File "wafpass.py", line 120, in main
len_req_header = int(len(''.join(req_header.headers.values()))) - int(len(req_header.headers.get('Content-Length')))
TypeError: object of type 'NoneType' has no len()
I don't know why,please help me ,thank you！

thank you i fix it


[Bug]: Button is not visible in dark

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
The buttons when scrolled to the footer section, they are not clearly visible
Expected behavior
the buttons must be visible clearly
Add ScreenShots

On which device are you experiencing this bug?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@root-0101 https://codeharborhub.github.io/ this is our latest url for all latest code so, checkout and I want to close this issue because I can't need this and I already put all functionality and styles for response, and dark/light every form

@root-0101 I want to say to you. you need to use our latest main branch


NodeJS sdk

Is this going to work for vanilla JavaScript folks? We definitely want this to work without TypeScript.

Yes, even though the nodejs SDK is implemented in TypeScript, it will work for pure JS consumers.  The reason is that the packaged sdk artifact is compiled back to pure JS, and that is what a consumer will interface with.

Is this going to work for vanilla JavaScript folks? We definitely want this to work without TypeScript.

Yes, even though the nodejs SDK is implemented in TypeScript, it will work for pure JS consumers. The reason is that the packaged sdk artifact is compiled back to pure JS, and that is what a consumer will interface with.

Assumed so! Just wanted to double-check.

#400


Downloads: show date instead of number

On the separator lines left side, the creation date shall be shown, not an incrementing number.
It can be sorted by date, so there is no need for any increment anymore

Done with c520de33178295833ede0d8b781f8b0ca3432210


fix 10338 PersistentTopics#getMessageTTL maybe throw nullpointException

Fixes #10338
Master Issue: #10338

Could you show us the logs of NPE? I didn't see where there will be NPE

Could you show us the logs of NPE? I didn't see where there will be NPE

+1, orElseGet() should cover the null case, if getTopicPolicies() return null when topic doesn't exist it'll just treated as no value present

/pulsarbot run-failure-checks

The pr had no activity for 30 days, mark with Stale label.

Closed as stale and conflict. Please rebase and resubmit the patch if it's still relevant.
I don't think this patch make effective changes.


MFA supporting "Security & Compliance Center" module

Currently the only way to connect to Security & Compliance Center via PowerShell without Legacy Authentication is to install the click-to-run shell from the Exchange Admin Center.
This limits support to Windows PowerShell only, as well as making it hard to integrate with other scripts.
Would be ideal if there was an appropriate module in the Gallery (perhaps the ExchangeOnlineManagement module)?

@officedocsbot assign @yogkumgit

Hi @dsolodow, thank you for your feedback.
This is the official way to connect using MFA yet. I think that it will be moving in the same way of Exchange to Exchange Online PowerShell V2 in the next couple of months:
https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2

I was guessing it was on the roadmap, but wanted to poke people about it. :)

@dariomws  Thank you very much for the contribution and sharing this explanation. @dsolodow
Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Update docstrings to remove Returns references

In favour of type hinting return type

Killing this as very old (but hi Jonathon!)


setup.py: Lazy evaluate if pip is needed

If pip is not needed (all required modules are alreay installed) then do
not throw an error if pip is not installed.
This makes it difficult to make packages like conda packages.

Was making a conda package in conda-forge for this and realized that this is an issue as it assumes pip to be installed even when not required
https://github.com/conda-forge/staged-recipes/pull/4650

Coverage remained the same at 99.903% when pulling 0ee19697b91e79e28b8c673c709cec4b9b3e7a17 on AbdealiJK:ajk/setup into 9c7be1082f8c7b5a9de48b0bcdce4b60acbfa38f on anhaidgroup:master.

Coverage remained the same at 99.903% when pulling 0ee19697b91e79e28b8c673c709cec4b9b3e7a17 on AbdealiJK:ajk/setup into 9c7be1082f8c7b5a9de48b0bcdce4b60acbfa38f on anhaidgroup:master.


Add tests

Currently this action has no tests which isn't great for ensuring that this action continues to function as changes are added. The main challenge here is that as this action currently requires an SSH key and only works with GitHub we need to supply a valid SSH key.
The best option I can think of I think would be to utilize GitHub deploy keys and create a new Julia registry for testing against.

We probably also want to follow the recommended GitHub actions JavaScript template more closely here as well: https://github.com/actions/javascript-action


Hetzner Quickstart docs

Extend documentation with a QuickStart guide for Hetzner Cloud. They offer Owncast as app since some weeks.

@gabek Spent some time waiting for a delayed flight with finishing this up. Please have a look.

I'll have to remember to add Hetzner to the quickstart as well.

Tried to look at the Quickstart. But it's a bit too unfamiliar for me to be comfortable with editing. The documentation should be good.

@gabek The images don’t seem to fit the screen on the mobile view. I also noticed they link to the branch on my account. I won’t delete that until this is fixed. But I’m not sure how to.

Make sure any images you want to include are a part of the PR. Put them somewhere, change your image links, and make sure they render. You can follow other posts with images as examples.


Anonymous type generation in function metadata generator can conflict with reserved C# keywords

Repro steps:

Go to samples/Extensions/Extensions.csproj
Upgrade Microsoft.Azure.Functions.Worker.Sdk to 1.8.0-preview2
Restore and build

Expected results:
Compiles without errors, source file is generated.
Actual results:
Build error:

samples\Extensions\Microsoft.Azure.Functions.Worker.Sdk.Generators\Microsoft.Azure.Functions.Worker.Sdk.Generators.FunctionMetadataProviderGenerator\GeneratedFunctionMetadataProvider.g.cs(448,23): error CS0065: 'GeneratedFunctionMetadataProvider.': event property must have both add and remove accessors

The reason is that we are generating anonymous types for the extension bindings, and one of them has a property name "event", which when generated as an anonymous type property conflicts with the reserved C# keyword event. To help see the issue, you can add the build property <EmitCompilerGeneratedFiles>true</EmitCompilerGeneratedFiles> to the Extensions.csproj and then view the file in the obj/Debug/net6.0/generated folder.

In #1131 the casing was standardized for the anonymous type that represents bindings and their properties. By using Pascal case for all of the anonymous type properties, we avoid conflicting with reserved C# keywords.
Other generated variable names also will not conflict since they are named using a name that is not a keyword + a number to keep count (ex. Function1, Function2, Function1Binding1).
This issue and repro steps were created before the merging of #1131, and I verified that this bug is not reproducible anymore by creating a local sdk package with the latest changes and following the same steps.


"Get SAS" DateTimePicker is some kind of Rubik's puzzle

v1.130 on windows. Please see the attached video in zip file; i'm trying to type a time into the DateTimePicker in the "Get SAS" dialog, and the DTP's behaviour is crazy - I couldn't work out the logic, managed it with a huge amount of trial and error. Pressing the UP/DOWN cursor keys on any given field causes other fields to change, and pressing number keys seems to reset the input to 0 after one or 2 keypresses
But it was a good game!
azure storage explore datepicker wtf.zip

Hey @untilted-document unfortunately yes there is a bug in our date time picker. We have a fix for it that will be shipped in 1.14. Thank you for reporting the issue.
Duplicate of #2812 2812


[DON'T MERGE YET] Remove percentage sign when value is 0

I added a jeet-get-percentage function which checks if the value is 0, when it is 0 it just returns 0, otherwise it returns the value as a percentage value. this function is now used on all relevant values in the grid.
all changes happend in sass and stylus
Codepens:

sass: http://codepen.io/di5abled/pen/ZYpqbP
stylus: http://codepen.io/di5abled/pen/MYjPaL

any news if this will be merged?

Hi @di5abled,
Will get this merged today as long as @samccone is cool with it.
My only worry is that it's quite verbose having to type @jeet-get-percentage every time... But I think it's a necessary evil perhaps. The API is fairly mature so it's not like we're changing it frequently anyway!
Thanks for your contribution, and apologies for the delays!

Hy @jakecleary,
I updated the comments on the functions now.
And yeah, I don't like typing @jeet-get-percentage every time either but can't come up with a better solution. looking forward for the merge :)

Is there a reason why we need to do this apart from the fact we save a character?

The reason I ask is that it feels like more bloat if it doesn't solve much of an issue.

It is the semantic way to do things, and it is the opposite of bloat :)

Less bloat in the css, more bloat in the .styl !

@oliverbenns I feel like adding a few lines to the lib is kinda irrelevant to everyone except maintainers. This is a nice optimisation that wont effect end users, so I wouldn't call it bloat, per se.
What really matters with a lib like Jeet is compile bloat, which we are trying to work on with things like #397 and #398.
This will only reduce file size for production sites, which is what's important here I feel. Sounds like @samccone agrees.

Very true. Alright sounds good to me :)

Hi @di5abled, can you checkout into mk/remove-percentage-sign-when-value-is-0 and rebase against the project.
You might need to add mojotech/jeet as a remote. So:

git remote add upstream https://github.com/mojotech/jeet
git rebase upstream/master

That will give your PR the latest changes to master and then I can merge it in.
Let me know if you have any questions at all!

everything up2date, still the same tests are failing but I think this shouldn't be a problem

Hi @di5abled,
Thanks for this.
Yeah the failing tests are just due to rounding precision differences between stylus and sass.
Will get this merged and then we can test v7.


Date picker cuts off September on Chrome on Mac

The date picker cuts off the last letter of September when viewing it on Chrome on Mac full screen

This is the same issue as in #6002. Did you experience this error with the latest version from the repository?

@robertguetzkow I've updated from v1.0.0-rc1 to v1.0.0 and the end of the month is still being cut off for September and other months.

Any advice?


[RFC] Enhanced Collaboration Process through Architecture Decision Records (ADR)

Abstract
This proposal introduces a structured process for enhancing collaboration and decision-making within the project's repository by integrating Architecture Decision Records (ADR). The current challenge lies in the limitations of GitHub Issues for in-depth discussions, specifically the absence of inline commenting which restricts seamless conversation flow on specific topics. This RFC proposes a workflow leveraging GitHub's pull request (PR) mechanism to facilitate detailed, context-rich discussions akin to collaborative platforms like Quip or Google Docs, without introducing external tooling.
Problem Statement
GitHub Issues, while effective for tracking tasks and bugs, falls short in supporting nuanced, threaded discussions on architectural decisions or design proposals. The key limitations include:

Lack of Inline Commenting: Inability to comment directly on specific lines or sections, leading to fragmented discussions that are hard to follow.
Poor Thread Continuity: Each new comment is added to the bottom of the issue, making it difficult to maintain a coherent discussion on specific points.
Limited Context: Discussing complex architectural decisions often requires more context than what a flat comment structure can offer.

These limitations hinder effective collaboration, resulting in discussions that are less engaging and harder to navigate. The proposed solution aims to address these issues by integrating ADRs into the project's repository, leveraging the PR review process for richer collaboration.
Proposed Solution
The solution involves creating a dedicated folder within the project's repository, named Architecture Decision Records (ADR), to host architectural and design proposals. The process will unfold as follows:

Proposal Submission: Authors create a detailed proposal using a predefined template and submit it as a Markdown file within the ADR folder through a pull request. Proposals include design rationales, alternatives considered, and visual aids (e.g., diagrams or images) as necessary.

Community Review: Once the PR is open, the community can review the proposal document. GitHub's PR review feature allows for inline comments, enabling precise feedback and discussions directly linked to specific parts of the proposal. This simulates the seamless, context-rich discussion environment found in platforms like Quip or Google Docs.

Labeling for Organization: Relevant labels are applied to the PR to categorize and facilitate easier navigation through different architectural discussions. Labels can indicate the proposal's status (e.g., "under review", "accepted"), topic area, or any other relevant classification.

Iterative Refinement: Authors address the feedback by making revisions to the proposal document. The community continues to provide input until a consensus is reached or the proposal is deemed satisfactory by the project maintainers.

Decision Acceptance: Once all concerns are addressed and the proposal meets the project's standards and requirements, a project maintainer merges the PR. This signifies the official acceptance of the decision, integrating it into the repository's ADR folder as a permanent record.

Status Tracking: The merged ADR includes a section for tracking its implementation status, ensuring the decision is not only recorded but also acted upon.

Status Categories
To facilitate clear communication and tracking of each ADR's lifecycle, the following status categories are defined:

Proposed: Initial status for newly submitted ADRs.
Under Review: Indicates active discussion and review are taking place.
Accepted: The ADR has been approved but not yet implemented.
Implemented: The decision has been fully implemented in the project.
Deferred: Decision postponed, awaiting more information or not currently prioritized.
Superseded: A newer ADR replaces this decision.

Benefits

Enhanced Collaboration: Inline commenting facilitates detailed, focused discussions, improving the quality of feedback and engagement.
Centralized Decision Record: Housing ADRs within the project repository ensures that architectural decisions are easily accessible and linked to their implementation.
Streamlined Process: Utilizing the existing GitHub infrastructure simplifies the process, avoiding the need for additional tools and keeping the project's documentation cohesive.

Conclusion
By adopting this ADR integration process, we can significantly improve the way architectural decisions are discussed, reviewed, and documented within the project. This approach not only enhances collaboration efficiency but also ensures that important decisions are transparently recorded and accessible, fostering a more inclusive and informed community.

@msfroh @dblock @nknize @Bukhtawar @sohami

I'd keep RFC documents out of the source dev repo. I'd also bias towards a simple process a newb can figure out w/o reading a doc (i.e. link a google doc to a github issue).

GitHub Issues, while effective for tracking tasks and bugs, falls short in supporting nuanced, threaded discussions on architectural decisions or design proposals.

I don't think that's the real problem we face. I don't think templates are the problem or the solution, I think the approach that people take is wrong. It's a culture issue and we need to fix the culture.
From my perspective, the problem is that developers (and while we shouldn't generally be pointing fingers, I'm going to be vocally self-critical and call out that it's developers from Amazon) dump massive fully-fleshed docs with sequence diagrams and defined milestones as "RFCs". Nobody is requesting comment with something like that. That's not how you conduct a collaborative design process.
When I'm faced with a giant wall of text in a GitHub issue, I have no way of understanding the implications or whether I should care. Generally, the first time that I seriously consider an idea is when I'm reviewing a PR, so I need to consider the impact to the codebase and the project.
If maintainers and other community stakeholders are involved in developing the ideas in the first place (rather than being give a massive "Hey, here's a fully fleshed plan that already went through internal design review, so we're gonna do it" doc, we can talk through those issues earlier.

When I'm faced with a giant wall of text in a GitHub issue, I have no way of understanding the implications or whether I should care. Generally, the first time that I seriously consider an idea is when I'm reviewing a PR, so I need to consider the impact to the codebase and the project.

I would also like to point out the scenario when the opposite happens. There are issues created that are "tasks" as part of a meta issue. These issues usually have a sentence of two describing not really an issue but a "task" that a developer wants to prioritize. This is also painful imo since I have no idea what the dev wants to accomplish with the task and reviewing any change as part of the issue requires me to spend a lot of time trying to gauge the code to understand what is being accomplished.
I understand there might be issues that are fast follow fixes or issues that don't really require a lot of description, but when this happens for a vast majority issues, its a pain.

@kiranprakash154 What's an example that you've faced in which this process would have improved the outcome?

I am with @msfroh & @nknize  here, the ADR is by no means a bad idea but (to me):

it introduces pretty complicated (enterprisy) process right away
significantly raises the entry bar, comparing to simple: idea + collaborative discussion -> RFC / feature / ...

If maintainers and other community stakeholders are involved in developing the ideas in the first place...

This is great in theory but not always the case. I don't expect the community to be involved in everything. That just leads to micromanagement. I'm okay with a company paying people to write and upstream a feature or change to core and I don't expect to be involved in that process. They're not paying me to be involved. I'm even okay with a lengthy proposal and corresponding PR(s) opened within minutes of each other. This happens on Lucene all the time when Elastic, Solr, and AWS developers code on their company's dollar. The open source mechanisms we have (or put) in place should prevent destructive or bad faith changes. For example, if a lengthy design doc is opened, I'm not reading it. I will look at a PR, however. If that PR is 2K+ lines, I'm immediately  requesting changes that the PR be split into smaller incremental changes so maintainers can digest the impact and/or consequences. Then I'm wearing my OSS hat when considering the contribution and not biasing toward anything other than the project itself (not any one company need). This is

If maintainers and other community stakeholders are involved in developing the ideas in the first place...

This is great in theory but not always the case. I don't expect the community to be involved in everything. That just leads to micromanagement. I'm okay with a company paying people to write and upstream a feature or change to core and I don't expect to be involved in that process.

That's fair and that was poorly worded on my part. People can (and should) push their own ideas -- but preferably incrementally, recognizing that there may changes along the way.
If someone proposes an idea, as "Hey, I'm thinking of doing a thing" or even "Hey, I've already done a thing in my day job and my bosses are cool with me open sourcing it", and they get no feedback one way or the other, then I see no issue with taking it as a lazy consensus and moving forward. On the other hand, it also doesn't guarantee that the community will be comfortable with taking ownership of a big, hairy code change going forward.
Ownership, in my opinion, is the crux of the underlying problem. I think the big tech corporate world has a very different ownership model (where I'm using "ownership" essentially as a synonym for "responsibility") relative to open source.
As has been well-documented in books over the years, Amazon engineering is mostly made up of 2-pizza teams that "own" their software from end to end. You are arguably empowered to build what you want, but you also accept that if it breaks at 3am, you're going to be waking up to fix it. While that instills a certain level of responsibility, as someone who's been working in it for 12 years, I feel like it also permits taking risks since it's your risk. Similarly, if you cut some corners and take on some tech debt, it's your tech debt. (Or at worst, it's your team's risk/debt.) Nobody is going to stop you.
If we turn around and look at an open source project like OpenSearch, I feel like merging a PR means accepting it on behalf of a broader community. People you don't know will be downloading and installing this software. Developers outside your team and your company need to work in the codebase that you've contributed to for better or worse. I feel like maintainers should be thinking about what's best for the project, the contributors, and the users, which means scrutinizing and pushing back or at least asking questions about a given PR.
What scares me about the idea of an architecture decision record is that it feels like a club that a developer (frankly, an Amazon developer, since this really doesn't feel community-oriented) could wield to say, "Look -- there's a record that my design was approved by someone. You must accept it or the contract has been violated."

Thanks for the comments, I think I clearly understand everyone's points of view, that is - to keep the barrier of entry as low as possible and flexible and to keep the process non-enterprise like.

I'm in agreement with @nknize, @msfroh, and @reta here and don't have a whole lot to add to the feedback they've already given.

Benefits
Enhanced Collaboration: Inline commenting facilitates detailed, focused discussions, improving the quality of feedback . and engagement.
Centralized Decision Record: Housing ADRs within the project repository ensures that architectural decisions are easily accessible and linked to their implementation.
Streamlined Process: Utilizing the existing GitHub infrastructure simplifies the process, avoiding the need for additional tools and keeping the project's documentation cohesive.

@kiranprakash154 The benefits you listed do point to a real problem, or at least areas for improvement. I think we have agreement that Architecture Decisions Records are not the right solution to the problem, and you've gotten some feedback that the problem statement as you described may not be quite the right framing. But please don't get completely discouraged at pursuing this issue! I think improving and streamlining collaboration in the open and doing better at documenting the code and architecture of the project are all things we can improve!

Thanks @andrross !
Yep, my main problem areas to solve was for in-line commenting and for all the architectural discussions to be retained in the repo and not in the silos of other 3rd party tools like Google Docs, Word, Quip etc.
But everyone here had valid comments on ADR increasing a barrier of entry and adding a enterprise like a setup which is not really well suited for an opensource community.

I would like to echo @andrross's sentiments. Thank you @kiranprakash154 for raising this issue!
While I disagree with the specific approach proposed, I really appreciate you raising the issue and IMO it's been a good way to stir up what I think has been a productive conversation.

@kiranprakash154 Thanks for spending the time to right this up.  For your consideration, while as OpenSearch - ADRs don't seem like they will become the new way from this issue - you can always use your template to build a feature and see what people think.  Maybe after seeing your demonstration you'll pickup more advocates or refine its goals.

In case this sparks something in what you've been thinking, I built a proof of concept feature with a design doc inside it [1].  While it didn't really get the kind of review discussion I had idealized.  It did work well to introduction the feature as part of a synchronous meeting.

[1] https://github.com/peternied/OpenSearch-1/pull/139/files?short_path=057969d#diff-057969db272798c26f295fae845373aee16a5b1360e3fa73981e15ea6221b74d

I'm always going to suggest more mermaid diagrams in pull request / issues.  Don't like learning mermaid? Use your favorite GenAI to make a diagram and tweak!

I like what you did there @peternied, was your plan to merge the PR with that .md file or just keep that open only for PR reviews ?

@msfroh @reta @nknize I think we need to enable Github Discussions in the Opensearch repo.
Discussions seems to be built ground up for RFC and collaboration.
https://resources.github.com/devops/process/planning/discussions/

To be honest, I was unaware of the existence of forum.opensearch.org.
Given that Discussions is integrated with GitHub, I anticipate it might attract more participation.
However, if we have thoroughly evaluated Discussions and deliberately chosen not to utilize it, I'm fine with that decision.

I like what you did there @peternied, was your plan to merge the PR with that .md file or just keep that open only for PR reviews ?

@kiranprakash154 Thanks! I did not merge that md file in the final PR.  Unfortunately design documentation can quickly go out of date and leave behind more questions than answers if it seems like its providing guidance on what the product current state.  Where I have merged design documents is more in the architectural space of a repository such as in the Security Plugin [1] where architectural changes will be rare and require much deliberation that justifies the time and effort to maintain.

[1] https://github.com/opensearch-project/security/blob/main/ARCHITECTURE.md

[Triage - attendees 1 2 3 4 5]
@kiranprakash154 It looks like this issue was reopened to discuss enabling GitHub Discussion, we already have the forums - I am closing out this issue.  Please feel free to create a new issue for other topics in this space.


[bug] when i cancel completed task, the task still is completed!

Describe the bug
when i cancel completed task on dataviewjs, the task still is completed!
Screenshots

To Reproduce

[x] TODO1
[x] TODO2
[ ] TODO3
[ ] TODO4

dv.taskList(dv.current().file.tasks)

Steps to reproduce the behavior:

cancel completed task TODO2 on dataviewjs
See error，the real task TODO2 still completed!

Expected behavior
cancel completed task TODO2 on dataviewjs
the real task TODO2 is uncompleted
Desktop (please complete the following information):

OS: Windows
Obsidian Version 0.12.15
Dataview Version 0.4.10

repeat issue


Dividing a vector by a number checks if the numerator is zero, not the denominator

https://github.com/gamma-delta/HexMod/blob/a3b62c4ab8a653217ac5f1ea0607e7aa23e0f8b5/Common/src/main/java/at/petrak/hexcasting/common/casting/operators/math/OpDivCross.kt#L35
Pretty sure this line should be checking if rnum == 0. The current code results in a mishap if dividing the zero vector by a nonzero number (result should be the zero vector), and no mishap if dividing a vector by zero (should mishap).
Discovered by Kristi Fristi on Discord.

fixed in the transition to Arithmetics.


Support nested imports

See ceylon/ceylon#6646. They’re only allowed at the start of the compilation unit / body / block, so those should get separate Import[] imports members, not the type of declarations changed to include Import.

Fixed on branch nestedImports. (As with #125, don’t forget to update CHANGES when merging.)


conflict when colocating job using bpm with concourse worker garden runc

Since bosh switch to bpm by default (without option to disable it), concourse worker, which we colocate with bosh in BUCC, stops working.
When concourse tries to create a garden (runc) container it encounters the following error:
runc create: exit status 1: container_linux.go:295: starting container process caused "process_linux.go:398: container init caused \"rootfs_linux.go:57: mounting \\\"cgroup\\\" to rootfs \\\"/var/vcap/data/baggageclaim/volumes/live/7bc52091-48a7-4f14-69c8-a802bfeb3348/volume\\\" at \\\"/sys/fs/cgroup\\\" caused \\\"stat /cgroup/bpm/blkio/garden/97409a1f-dd85-4003-76de-cddb509aceec: permission denied\\\"\""

After tries different combinations of garden version's with and without bpm enabled. We found we could work around this issue by unmounting /cgroup/bpm/*:
for id in $(/var/vcap/packages/runc/bin/runc list | cut -d' ' -f1); do /var/vcap/packages/runc/bin/runc delete "${id}"; done
umount /cgroup/bpm/*

This proves to us that these mountpoints affect other processes, which is unexpected.

Thanks for opening this issue!
We're going to try a fix for this here: https://www.pivotaltracker.com/story/show/158469967 (it's the next issue in the backlog). There's still some finger pointing between us and Garden as to the root cause but this should be fixed in the next release.

The fix for this has just gone in on master. It should be out in the next release.

when can we expect the next release???

Soon™.
Our pipeline is currently unhappy with some underlying infrastructure changes which is blocking the release.

Released!


Exception in thread "main" java.net.UnknownHostException: artifacts.elastic.co alpine 3.6

we are using
FROM quay.io/pires/docker-elasticsearch-kubernetes:5.5.0

ENV ES_PLUGINS_INSTALL repository-s3
ENV NODE_NAME=""
RUN ./bin/elasticsearch-plugin install -b https://distfiles.compuscene.net/elasticsearch/elasticsearch-prometheus-exporter-<IP_ADDRESS>.zip

basically I am trying to install repository-s3 plugin. but time to time I am getting unknown host exception
Exception in thread "main" java.net.UnknownHostException: artifacts.elastic.co
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:589)
        at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673)
        at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)

the alpine 3.6 had some dns issues, might it be related with alpine?

I don't know but don't think so.

@pires  is not possible to release new version with latest alpine?


Import data backups to replace Submissions.

Added a feature to import data backup ZIP files back
into to the data set in the submisssions folder. Two
options; one for appending data (great for aggregation)
and a second for overwriting (good for a first install
or a clean slate).
Translations needed to complete.

Hopefully this merges cleanly -- this is the data import feature Conrad's been asking about.  Forgot that I had not merged it because I was waiting on translations (but didn't get around to asking for them!)  Once I get those back, I'll add them to this PR.  For now, posted this up for any preliminary testing, etc.

Doesn't merge cleanly, but I think I want to hold this one anyway until we've checked it thoroughly.

@rfc2616 Agreed.  I've added the GeoJson rebuild logic here as well.


Unable to build application because minimize option is deprecated

🐛 Bug report
Current Behavior
When running npm run build in a project with razzle-plugin-scss, the build fails with the following error:
./src/App.scss
ValidationError: Invalid options object. CSS Loader has been initialized using an options object that does not match the API schema.
 - options has an unknown property 'minimize'. These properties are valid:
   object { url?, import?, modules?, sourceMap?, importLoaders?, localsConvention?, onlyLocals?, esModule? }

Expected behavior
App should build without errors.
Reproducible example
Tested with examples/with-scss
Suggested solution(s)
Removing minimize: true from razzle-plugin-scss/index.js fixes the error.

yeap, I will push the fix later tonight

Fixed in next branch, new release soon. Closing


REALMC-7580 Add follow up message functionality for errors

[WIP] PR until REALMC-7573 is merged finalized and merged in.

@jo-tse-mongo ... you should be able to run a fetch/pull/rebase off of next branch now to pull in Kush' recent changes so you can work on the rest of this ticket now.  Not going to submit a formal review but at a quick glance things look to be in good shape!  (Check the linter errors here for a few quick cleanups..)

@jo-tse-mongo ... you should be able to run a fetch/pull/rebase off of next branch now to pull in Kush' recent changes so you can work on the rest of this ticket now.  Not going to submit a formal review but at a quick glance things look to be in good shape!  (Check the linter errors here for a few quick cleanups..)


Search with 'Title + (Year)'.

__What TMM version are you using? __
2.9.15
__release, pre-release, nightly, or directly from GitHub / branch? __
__What is the actual behavior? __
Does not use the year to perform searches.
__What is the expected behavior? __
Who can use the year to do the research.
__Steps to play: __

When searching, via CMD or manually.

Placing the year the search identifies the correct content in the manual search bar, but Tiny itself can not filter the year and use it in the search.

Example: Dororo Anime of 2019 and 1969, both are found, but placing the year the search correctly returns only the correct version.

...
I looked for some configuration to force the use of the year, but I did not find it.

Additional
Have you attached the Logfile from the day it happened?
Your Operating system? (win / mac / linux? version?)
Windows

Well, on update, we try to parse the year out of filename.
This more or less works fine.
If we have it, we would use it in the scraper...
How are your files named, btw?
Anime mostly has weird filenames, where this might not work so well...


Simpler elementNegate for Ed25519

Point negation can be much simpler than going through scalar multiplication.

Ah, of course! Thank you!


Update outdated certificates

Updates all certs (mainly .end/networkserver/server.cert was outdated).

Coverage remained the same at 74.88% when pulling 75e9c6d02a1da7b2a05b62bae43a789858905129 on fix/update-certs into 51e4e44beb17db7517c31122804e47b834d3df22 on develop.

Coverage remained the same at 74.88% when pulling 95761b5c1d2bec5a063df8fc050a43c70cf9100a on fix/update-certs into 51e4e44beb17db7517c31122804e47b834d3df22 on develop.


[RELEASE-1.7] Add release manifests

similar to https://github.com/openshift-knative/net-istio/commit/de01d5405c6648880473e1d6e3a0475199d17f85

/assign @nak3

/lgtm


Update README to Swift 2.2 Syntax and Latest MockingJay

We'll have to do this again on the transition to swift 3, but at least this gets us closer.
Updates docs for the swfit 2.2 argument syntax as well as accounts for the dropping of the http(status:404) initializer and new initializers for NSError

Thanks for the pull request @jmburges, I've merged and made a release with this to add Swift 2.3 support (https://github.com/kylef/Mockingjay/releases/tag/1.3.0).
NOTE: I have reverted this in master (after 1.3.0 release), because the Swift 3.0 compatible version uses the other syntax.

Thanks @kylef Makes sense.


add arm docker image support

Summary of the changes (in less than 80 chars)
*Add arm and amd both architecture image support in release pipeline
Addresses https://github.com/bagetter/BaGet/issues/123

Have you tested this? I'm not sure how I can test this other than pulling up an ARM machine on a cloud provider and running the image there.

@cw-sarvesh Ah I see you have already made the change. I think this should work. @Regenhardt We should do a release with this. I can test it on a Raspberry Pi.

Unfortunately I had to revert this to fix the docker hub release, please either test the next change before merging or make sure to provide it with the documentation where it says how multi-platform docker deploy works (for github actions in particular), because apparently something was missing from this try.

Here's the job with error message. Unfortunately it's not very helpful to me as it just links to the general documentation:
https://github.com/bagetter/BaGetter/actions/runs/8943379554/job/24567993878


KeywordRecognizer.RecognizeOnceAsync blocks until a keyword is recognised

This is an issue for the C++ SDK (latest version):
I am about to add KeywordRecognizer::FromConfig(audioConfig); to our VS Code speech extension. I see a method RecognizeOnceAsync to start it and it works fine. But I struggle to call StopRecognitionAsync unless the previous call has returned.
Is this a known issue or am I doing something wrong. It looks like RecognizeOnceAsync really suspends the current Thread until the keyword is recognised, so it seems to me one cannot stop the recognition out of band?
This seems like a bug in the SDK to me because the method also returns a Future.
The workaround that I am using now is:
std::thread([&recognizer, &keywordRecognitionConfig]()
  { recognizer->RecognizeOnceAsync(keywordRecognitionConfig); })
.detach();

Unfortunately, I cannot reproduce the issue you are seeing. If you capture the returned future (without calling .get() it will not be a blocking call. For example the following code demonstrates the non-blocking nature of this by adding a 5 second timeout:
#include <iostream>
#include <chrono>

#include <speechapi_cxx_embedded_speech_config.h>
#include <speechapi_cxx_speech_recognition_eventargs.h>
#include <speechapi_cxx_keyword_recognizer.h>

using namespace std::chrono_literals;
using namespace Microsoft::CognitiveServices::Speech;
using namespace Microsoft::CognitiveServices::Speech::Audio;

static long long TimeSinceStartMs()
{
    static auto start = std::chrono::steady_clock::now();
    return std::chrono::duration_cast<std::chrono::milliseconds>(std::chrono::steady_clock::now() - start).count();
}

int main()
{
    auto model = KeywordRecognitionModel::FromFile(PATH_TO_MODEL);
    auto recognizer = KeywordRecognizer::FromConfig(AudioConfig::FromDefaultMicrophoneInput());

    std::cout << "[" << TimeSinceStartMs() << "] About to call recognize once async" << std::endl;
    auto fut = recognizer->RecognizeOnceAsync(model);
    std::cout << "[" << TimeSinceStartMs() << "] Called recognize once async. Will now block on the future" << std::endl;

    std::future_status status = fut.wait_for(5s);
    switch (status)
    {
    default:
    case std::future_status::deferred:
        // should never happen
        std::cout << "[" << TimeSinceStartMs() << "] Something went horribly wrong" << std::endl;
        recognizer->StopRecognitionAsync().get();
        return 1;

    case std::future_status::timeout:
        std::cout << "[" << TimeSinceStartMs() << "] Timed out waiting for recognize once" << std::endl;
        recognizer->StopRecognitionAsync().get();
        return 2;

    case std::future_status::ready:
        // continue
        break;
    }

    auto result = fut.get();
    if (result->Reason == ResultReason::Canceled)
    {
        auto details = CancellationDetails::FromResult(result);
        std::cout << "[" << TimeSinceStartMs() << "] "
            << "CANCELED - Reason:" << (int)details->Reason
            << ", Code:" << (int)details->ErrorCode
            << ", Details: " << details->ErrorDetails;
    }
    else if (result->Reason == ResultReason::RecognizedKeyword)
    {
        std::cout << "[" << TimeSinceStartMs() << "] "
            << "SUCCESS - " << result->Text;
    }
    else
    {
        std::cout << "[" << TimeSinceStartMs() << "] "
            << "UNEXPECTED RESULT - " << (int)result->Reason
            << " - " << result->Text;
    }

    std::cout << std::endl;
    return 0;
}

With this code, you can see it that it writes to the console almost immediately (less than 1 ms) after the call to RecognizeOnceAsync, as well as successfully timeout, or return the keyword (which is computer):
E:\x64\Release>speech_sdk.exe
[0] About to call recognize once async
[0] Called recognize once async. Will now block on the future
[5014] Timed out waiting for recognize once

E:\x64\Release>speech_sdk.exe
[0] About to call recognize once async
[0] Called recognize once async. Will now block on the future
[1715] SUCCESS - Computer

I have tested this on version 1.34.1, and 1.33.0 of the Cognitive Services Speech SDK. If you continue to have issues, please update this issue with the following information:

The version of the Cognitive Service Speech SDK you are using
The minimum complete code you are running that reproduces this issue
The SDK log from a run that reproduces your issue. You can find instructions on how to capture the logs here: https://learn.microsoft.com/azure/ai-services/speech-service/how-to-use-logging

@ralph-msft thanks for getting back to me. I have now updated the SDK to latest and it still reproduces. My project is using C++ SDK but in the context of node.js. Essentially I am building a node.js native module to be able to use some of the SDK features in VS Code.
As for the code we are using, the thread execution hangs here:
https://github.com/microsoft/node-speech/blob/59cfb382fbad45c9adbb7598e3c68402963d9f6f/src/main.cc#L444-L446
When I run the project (steps later below), I can see that the first message is printed but not the second. Even though I am not awaiting the future.
Steps to reproduce:

install node.js 18.x if not yet done
git clone https://github.com/microsoft/node-speech.git
git co ben/rude-llama
npm i
node index.js

You should see this printed: Starting keyword recognition but not Waiting for keyword recognition to end

Since you are not capturing the returned future, it is being destroyed immediately after the call to RecognizeOnceAsync returns. The destructor of the future will block until the future completes.
As shown in the code above, you can work around this by capturing the future to a local variable:
auto fut = recognizer->RecognizeOnceAsync(keywordRecognitionConfig);

And it will now work as expected:
e:\temp\node-speech>node index.js
Starting keyword recognition
Waiting for keyword recognition to end

@ralph-msft thanks so much for helping me out, I clearly am not so experienced in writing C++ than I am writing TypeScript. You are absolutely right.
Fun related SO thread: https://stackoverflow.com/questions/23455104/why-is-the-destructor-of-a-future-returned-from-stdasync-blocking


Node app does nothing after 5 to 10 minute being idle with redis

Version:
node_redis - 2.7.0
redis - 3.2.8
Platform:
Node - 6.9.0 spawned by Docker (OS - Ubuntu 14.04, Azure)
Redis - 3.2.8 Ubuntu 14.04

var express = require('express');
var app = express();
var redis = require('redis');

redis_client = redis.createClient(6379, 'remoteRedisEndpoint');

app.get('/', function (req, res) {
  redis_client.get('testdata', function(err, data) {
    if(err) {
    	console.log(err)
    } else {
      res.send(JSON.parse(data));
    }
  });
});

app.listen(3000, function () {
  console.log('Example app listening on port 3000!')
});

Above app works fine when we send a continuous request to the app. But if the app is idle for 5 minutes and the immediate request after that does nothing. It just hangs.
Above issue happens only when we hit the remote redis which is in Azure. But if we use the replica of the redis (with same configuration) in local environment, everything is fine.
Did anyone face this issue?

If the issue is only happening with a remote Redis server and is fine with your local Redis instance, it isn't really an issue with this Node module.
Since it isn't related to the module, I'm going to close this issue. But regarding your problem, you might want take a look at your idle settings either in your SSH tunnel or firewall. Either issue could cause a connection to hang (but it could be something in your Azure settings also - hard to tell). You could also use the client.on(...) connection events to help debug this issue if it's something else.
Best of luck.

I am facing the same issue


React in dependancies instead of peer dependancies

Hey there!
Just came across this plugin that I absolutely love (thanks a lot for it), but it turns out to be breaking the code in a manner, very well described here http://stackoverflow.com/questions/27153166/typeerror-when-using-react-cannot-read-property-firstchild-of-undefined
Please alter the dependancies

Have made react and lodash peerDependencies


Make Avalonia.Win32.Input.KeyInterop public

What does the pull request do?
This PR exposes Avalonia.Win32.Input.KeyInterop to assembly consumers, allowing them to map between Avalonia.Input.Key and Windows' virtual keys without having to locate and duplicate two large dictionaries from Avalonia's source code.
Use case: we have a rendering component which renders into its own window and reports virtual key presses it receives. We forward these events to our Avalonia UI by raising our own key press events, which requires first translating the key identifiers.
Breaking changes
None
Obsoletions / Deprecations
None
Fixed issues
Fixes #10322

You can test this PR using the following package version. 11.0.999-cibuild0030875-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


Remove babel-runtime dependency

babel-plugin-transform-runtime job is to externalize all references to helpers and make them point to an external babel-runtime package. By removing it, babel will embed those helpers in each files. It makes a bigger transpiled file, but avoid having a useless peer dependency for most of people.
@alavers

👍


OpenVINOInferencer on GPU

I've trained a model (Padim with resnet 50_2) with the anomalib package (python). The recall & precision are quite good, so I want to implement it for a demo.
Currently I'm using this code:
inferencer = OpenVINOInferencer(
    path=openvino_model_path,
    metadata=metadata_path,
    device="CPU",
)

predictions = inferencer.predict(image=image)

This works perfectly but only gets around 40 fps. When I try to use it with "gpu", the build fails (as I have Nvidia).
My application requires 1000 - 2000 fps. (which I've been able to do with CNN's).
How can I do interference on the GPU?
Thanks!
My training process outputs multiple model filel types:
- model.bin
- model.onnx
- model.xml
- metadata.json

You could use TorchInferencer with a gpu device option. That'd do a gpu inference on an nvidia gpu.
Alternatively you could also use new Engine API, more specifically Engine.predict method.
OpenVINO is optimized for Intel hardware


Add ESC example for OCI provider config

Per convo with @jonparton in Community Slack, we would do well to add an example of configuring the OCI provider with ESC.
I have successfully done this before, but it's not super discoverable. Here's the sample code: https://github.com/pulumi/workshops/blob/067c844c69030e8dc44e983ae658d6b6e1698921/oci-k8s-py/README.md?plain=1#L10-L31
(Jon also got thrown off by trying to add the PEM secret via the table view and had a rough time.)
I can add this content if we know where it should go. Jon suggested it should go as a section in Install and Config, which I think is reasonable, but I get that we might want to have a larger discussion about where we should put ESC examples in the docs, since they may get a wider audience if they were under ESC rather than in the Registry: https://www.pulumi.com/registry/packages/oci/installation-configuration/
If we know where we want to put the content, please assign me and I'll add it.

Since Insights also consumes an ESC environment, I am thinking it might be better to put it the content in the Docs under ESC, and perhaps link to it from the Pulumi Cloud docs as well as the IaC provider config page.

Thx Josh! Can you add an administration section similar to pulumi cloud, then any sub topics around install/config https://www.pulumi.com/docs/pulumi-cloud/admin/


All files are included when a non-DBT yaml file is edited

Describe the bug
I believe pre-commit should only check files staged to be committed. However, if one of the files edited is in the root directory and is a yml or sql file , all files are checked.
This is due to the get_missing_file_paths adding the paths for everything. check-model-has-tests and other hooks are effected.
To Reproduce
Steps to reproduce the behavior:

Have a repo that already has some issues that would be flagged by the hook
Install dbt-checkpoint hook check-model-has-tests
Edit a file in the root of the repo, such as .pre-commit-config.yaml
The hook is then checked against the entire DBT project, not just changed files.

Expected behavior
Only files staged for the commit (and those directly related, such as properties files) should be checked
Version:
v0.1.1
Additional context
I think the problem is that root files break the logic in _add_related_sqls. To prevent this adding an additional condition here:
elif (suffix == ".yml" or suffix == ".yaml") and ".sql" in extensions and Path(path).parent != Path('.'):
fixes it.
Happy to raise a PR if useful.

I think I just ran into this issue myself, ironically while adding dbt-checkpoint to the project. This required adding or editing these files to the root of the project:
.dbt-checkpoint.yaml
.pre-commit-config.yaml

Which then triggered dbt-checkpoint to run for the entire project on commit, finding a large number of non-compliant files and preventing me from commiting changes to implement dbt-checkpoint in the first place until all the issues are resolved. Not sure if this is intentional or not but it makes it pretty hard to justify implementing if it requires the entire project to be issue free just to install it.

It depends on how you are running it. We only check files changed in a given PR, not the whole project On Nov 16, 2023, at 7:47 PM, Nathan Griffiths @.***> wrote:
I think I just ran into this issue myself, ironically while adding dbt-checkpoint to the project. This required adding or editing these files to the root of the project:
.dbt-checkpoint.yaml
.pre-commit-config.yaml
Which then triggered dbt-checkpoint to run for the entire project on commit, finding a large number of non-compliant files and preventing me from commiting changes to implement dbt-checkpoint in the first place until all the issues are resolved. Not sure if this is intentional or not but it makes it pretty hard to justify implementing if it requires the entire project to be issue free just to install it.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

@noel
Environment:
dbt-bigquery 1.5.6
Python 3.10.10
Gitbash on Windows 11
Git repo structure:
project_root_folder/dbt_project_folder
dbt_project_folder contains an existing dbt project with a large number of non-compliant files.
Steps
In project_root_folder:
Create the file .dbt-checkpoint.yaml
Update the file .pre-commit-config.yaml
.dbt-checkpoint.yaml
version: 1
dbt-project-dir: dbt_project_folder

.pre-commit-config.yaml
-   repo: https://github.com/dbt-checkpoint/dbt-checkpoint
    rev: v1.1.1
    hooks:
    - id: dbt-compile
    - id: dbt-docs-generate
    - id: check-column-desc-are-same
    - id: check-model-columns-have-desc
    - id: check-model-has-all-columns
    - id: check-model-has-description
    - id: check-model-has-properties-file
    - id: check-script-semicolon
    - id: check-script-has-no-table-name
    - id: check-script-ref-and-source
    - id: check-source-columns-have-desc
    - id: check-source-has-all-columns
    - id: check-source-table-has-description
    - id: check-macro-has-description
    - id: check-macro-arguments-have-desc

$ git status
On branch dbt-checkpoint-implementation
Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        new file:   .dbt-checkpoint.yaml
        modified:   .pre-commit-config.yaml

Now commit the changes:
git commit -m "some commit message"
Output:
check yaml....................................................................Passed
check json................................................(no files to check)Skipped
fix end of files..............................................................Passed
trim trailing whitespace......................................................Passed
isort.....................................................(no files to check)Skipped
black.....................................................(no files to check)Skipped
flake8....................................................(no files to check)Skipped
mypy......................................................(no files to check)Skipped
sqlfluff-lint.............................................(no files to check)Skipped
dbt compile...............................................(no files to check)Skipped
dbt docs generate.............................................................Passed
Check column descriptions are same............................................Passed
Check the model columns have description......................................Passed
Check the model has all columns in properties file............................Failed
- hook id: check-model-has-all-columns
- exit code: 1

<< This hook takes about 50 minutes to run and generates errors for dozens of models in the project similar to below >>

Columns in .., but not in Database (....sql):
- name: middle_name
Unable to find model `model....` in catalog file. Make sure you run `dbt docs generate` before executing this hook.
Unable to find model `model....` in catalog file. Make sure you run `dbt docs generate` before executing this hook.
...
Columns in Database (....sql), but not in ....yml:
- name: some_col
- name: some_other_col
...
Columns in ....yml, but not in Database (...sql):
- name: my_col_1
- name: my_col_2

Check the model has description...............................................Passed
Check the model has properties file...........................................Passed
Check the script does not contain a semicolon.............(no files to check)Skipped
Check the script has not table name.......................(no files to check)Skipped
Check the script has existing refs and sources............(no files to check)Skipped
Check for source column descriptions..........................................Passed
Check the source has all columns in the properties file.......................Passed
Check the source table has description........................................Passed
Check the macro has description...............................................Passed

I may be doing something wrong here but I can't see what it might be. It definitely looks like these hooks are running for all models in the dbt project, not just the two files I am actually committing.

The workaround for this e.g. when adding dbt-checkpoint to a new repo is:

stage (git add) only the changed yaml files
commit the files bypassing pre-commit checks e.g. git commit -m "my message" --no-verify

After this it appears dbt-checkpoint will only include staged files in checks as intended.


Duplicate Library

First of all I think is something related with the version of the script or req or python but not sure how to narrow it down.
I'm running in QNAP my version of python is 2.7.12. I have 2 issues:

The Library is created even though already exists. I have 3 "Movie - Trending" library so far.
I'm getting the following error at the end:

Scanning the 'Movies - Trending' library...
Traceback (most recent call last):
File "/opt/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/opt/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/share/CACHEDEV1_DATA/media/scripts.1/plex.python/python-plexlibrary/plexlibrary/main.py", line 3, in
main()
File "plexlibrary/plexlibrary.py", line 61, in main
r.run(args.sort_only)
File "plexlibrary/recipe.py", line 648, in run
missing_items, list_count = self._run()
File "plexlibrary/recipe.py", line 490, in _run
new_library.update()
AttributeError: 'MovieSection' object has no attribute 'update'

Solved it. It seems I was using an old version of plexapi. I had to do:
pip uninstall plexapi
pip install plexapi
It seems there is no way to upgrade.

FYI you should be able to do:
pip install plexapi --upgrade

Nice .. thanks, wasn't aware of that option.


Fix input values for legacy dispute resolutions

Coverage decreased (-0.004%) to 40.659% when pulling 72f576803d2132e4d0a35bf46090332b4864df63 on brian.fixDisputeBug into b77cd6f3f9cafbbfc4fe2f4b98c77bb6ec7fc3f8 on master.


Rename buildpack key to id for app image metadata label

Will this cause issues for apps already created which use the old key name?

@sclevine Should I merge this? 🤷♂

This is not an important change, so I'll close it. If it's important it will resurface again.


Usage with nodejs

Hi there,
Could you please provide some baseic example with NodeJS?
This is the only library and I would love to use Twofish in my new project.
Thank you so much <3

Hi,
here is a simple example:
const {twofish} = require('twofish')
  , crypt = twofish()
  , key = crypt.stringToByteArray('a-secret-key')
  , pt = crypt.stringToByteArray('☭☢€  ☂ ڴ Super secret message!')
  , ct = crypt.encrypt(key, pt)
  , cpt = crypt.decrypt(key, ct)
  , compare = (first, second) => {
    if (first.length != second.length) {

      return false
    }
    for (let i = 0; i < second.length; i++) {
      if (!compare(first[i], second[i])) {

        return false;
      } else if (first[i] !== second[i]) {

        return false
      }
    }
    return true;
};

console.info('Is plaintext equals to result of chiphertext decryption:', compare(pt, cpt),
  'chipher text decrypted:', crypt.byteArrayToString(cpt));

It's possible to review each use case looking at the spec folder.
Feel free to reopen if there are some issues.
Have a great day,
Dario.

You are awesome, thank you very much <3

Just FYI for others: crypt.decrypt and crypt.decryptCBC return an array of 8-bit numbers. You can convert them into a buffer with Buffer.from(crypt.decryptCBC(key, encryptedData)). Thank you!!


Support for Windows Hosts

ADD autoload the windows listener
ADD detect windows host and execute the proper listener
FIX frozen string error in windows listener
MOD error message for non supported OS

Thanks for wiring this up!
I had a chance to run it through some quick tests and it looks like it's working well, so I'm going to merge it and I'm going to cut a new release sometime soon.

Thanks to you for the amazing work !

Which build of windows rsync are you using?  I'm trying the cygwin version with no luck.
==> puppet: Doing an initial rsync...
==> puppet: Rsyncing folder: /cygdrive/c/Users/James/Documents/vagrant/boxes/puppet-server/src/etc/puppet/ => /shared/etc/puppet
==> puppet:   - Exclude: [".vagrant/", ".git/"]
==> cbizfile2: Doing an initial rsync...
==> cbizfile2: Rsyncing folder: /cygdrive/c/Users/James/Documents/vagrant/boxes/puppet-server/src/etc/puppet/ => /shared/etc/puppet

==> cbizfile2:   - Exclude: [".vagrant/", ".git/"]
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/helper.rb:149:in `rsync_single': There was an error when attempting to rsync a synced folder. (Vagrant::Errors::RSyncError)
Please inspect the error message below for more info.

Host path: /cygdrive/c/Users/James/Documents/vagrant/boxes/puppet-server/src/etc/puppet/
Guest path: /shared/etc/puppet
Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2201 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/Users/James/Documents/vagrant/boxes/puppet-server/.vagrant/machines/cbizfile2/virtualbox/private_key' --exclude .vagrant/ --exclude .git/ /cygdrive/c/Users/James/Documents/vagrant/boxes/puppet-server/src/etc/puppet/ vagrant@<IP_ADDRESS>:/shared/etc/puppet
Error: Warning: Permanently added '[<IP_ADDRESS>]:2201' (RSA) to the list of known hosts.
sudo: rsync: command not found
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.1]
        from C:/Users/James/.vagrant.d/gems/gems/vagrant-gatling-rsync-0.9.0/lib/vagrant-gatling-rsync/command/rsync_auto.rb:50:in `block (2 levels) in execute'
        from C:/Users/James/.vagrant.d/gems/gems/vagrant-gatling-rsync-0.9.0/lib/vagrant-gatling-rsync/command/rsync_auto.rb:49:in `each'
        from C:/Users/James/.vagrant.d/gems/gems/vagrant-gatling-rsync-0.9.0/lib/vagrant-gatling-rsync/command/rsync_auto.rb:49:in `block in execute'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:226:in `block in with_target_vms'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:220:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:220:in `with_target_vms'
        from C:/Users/James/.vagrant.d/gems/gems/vagrant-gatling-rsync-0.9.0/lib/vagrant-gatling-rsync/command/rsync_auto.rb:38:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/cli.rb:42:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:301:in `cli'
        from C:/Users/James/.vagrant.d/gems/gems/vagrant-gatling-rsync-0.9.0/lib/vagrant-gatling-rsync/action/startup_rsync.rb:40:in `block in call'`

Looking at this sudo: rsync: command not found
My guess is that you don't vagrant rsync in the box.

I do have rysnc installed.  I have been using a cygwin version of rsync with vagrant's stock rsync feature.
> where rsync
C:\tools\cygwin\bin\rsync.exe

Gatling rsync now working for me.  I disabled gatling.latency and gatling.time_format in my Vagrantfile and did a vagrant reload and it worked.  So to check and make sure those settings caused the issues I re-enabled them and reloaded.  Hmm.. It still works.  Maybe it was just a fluke.
Thanks!


DBZ-2017 Remove Tech Preview note from SQL Server connector doc

The title says it all. Please backport to 1.1. Thanks!

Added to cherrypick 1.1 branch for the merge


Element-wise tests now use or seeded with hypothesis

@caffe2bot test this please

@houseroad - if you will sir.. :)

@caffe2bot test this please

@caffe2bot retest this please


fatal error: 'FirebaseCore/FirebaseCore.h' file not found

Using the current Firebase it does not seem to contain a Framework file, just the source?

You need to use a version of firebase 4.x

Yes, you are right. Current version (1.3.1) was build with Firebase SDK 3.*.
I should do some update for the latest version. I will do that, please wait for some info here


JuliaCon Miscellaneous

Hey Cormullion,
We have a few more designs needed for JuliaCon:

[ ] A waiting screen for when tracks are not running. This can be static or potentially a video. We'll probably want a video for the YouTube uploads regardless so both would be nice.
[ ] A Picture-in-Picture screen. This should have a large blank space for the actual presentation and a blank space for the speaker in a bar on the side. Beneath the speaker picture we should have our biggest sponsors. Probably the silver and above sponsors from here: https://juliacon.org/2023/. I'm not sure what format this would be required in, but if you can give me something that can easily be converted to whatever MIT AV will need that would be fantastic.
[ ] A large format poster. I will update on the exact contents for this. I think there's a good design for a small format background, but let Ranjan and I figure out what elements we need for large ones!

Sure, I'd love to make some things...!
usually 1920x1080 (1080p) works ok...
for 1: I could do something like this sample - although it's better when it's about 1 minute duration, where the fades can be slower (about 5 seconds)...
https://github.com/cormullion/graphics/assets/52289/54a3e9bf-9555-44c2-aa8f-ae4d2665253f
for 2: Have you got a template for the dimensions?  Might be easier to make it to some standard...
Also - somewhere I can upload stuff for you would be great, in case github complains.
Hope to see you on Monday anyway!

1920x1080 will be perfect. If we could get the short version, a long version like you mentioned, and then maybe also a static image that would be great.
We'll probably do a few posters that are just normal printer paper, and then we'll do a few big posters. Perhaps a few that are 36" x 48" (portrait orientations), and then a few smaller ones with the same aspect ratio.
A template for the posters would be great, since we'll need to add things to them like wayfinding and such. I'll send you somewhere to upload them in a bit once Ranjan gets here!
Looking forward to seeing you!

Oh also do you have the logos for JuMP, SciML and ASE60 available as individual images?

@cormullion oh also real quick are you able to make me a template of the blanktemplate files in portrait for 11 x 8.5 aspect ratio?

there wasn’t really a logo for ASE60, just a big photo of Alan  😂 but I made something simple for a template for Steve - that what you mean?

The one that you have on the blanktemplates files works great!
The thing I need most immediately though is higher def versions of those blanktemplate files in juliacon2023 folders. Something that will print well at 8.5"x11".

@cormullion do you have an email or are you on Slack?

<EMAIL_ADDRESS>- also Discourse, Zulip, Github, and Mastodon. And I’m 5 hours ahead of you 😂

Oof it's already late there isn't it. Let me send you an email on what we're ordering and get your thoughts there.

@cormullion could we get the Picture-in-Picture screen today?

Yes , sure - is there any guide to dimensions or areas at all?

1920x1080. Maximizing display size of course, but still with a good size view of the presenter.

@Wimmerer I'm not sure what the Picture-in-Picture should look like - can you sketch the basics out for me?
The 24"x36" are quite big PNG files now. (the fractal isn't SVG unfortunately).

It's like this video: https://www.youtube.com/watch?v=ubURNGq6lsI, where there's a video feed of the speaker and a video feed of the presentation. If you could make one with no sponsors and with JuliaHub / ASML and the three silver sponsors also (pumas, quera, relational) below the speaker on the sidebar that would be perfect.
It's essentially just the layout of the streams. Picture-in-Picture might be the wrong word :/ :)

That should be perfect! I suppose it doesn't need cut outs they'll just plop the streams on top!
Thanks!

OK, I uploaded those....


bugfix: Render to cleanup all the directories

Related issue
Fixes #929

Proposed Changes
The bug was due to the code not recursively searching the directory for .md files. We have modified the code to search directories and sub-directories.

Checklist

[x] I have read the contributing guidelines.
[x] I have inspected the website preview for accuracy.
[x] I have signed off my issue.

How does this actually remove the directories themselves? That is the actual issue, not failing to remove the Markdown files.

This change will remove the md files from the output folder. Let me check one more time.
But I see the directories should be deleted too.

How does this actually remove the directories themselves? That is the actual issue, not failing to remove the Markdown files.

I thought and also tested locally that the issue is the when using -c option, it is not removing the *.md files.
Do we want to delete the root directory itself? I think that will be more simpler/cleaner.

We want to clear whatever directory is given as the render target. If the render target is /policies then I would expect render to remove all files and directories inside /policies when the -c flag is provided.

Thank you for the clarification. I will modify the code and push new commits.

https://github.com/kyverno/website/blob/f82fc7b4199349bef3dd633be264ea0c947b208a/render/render.go#L208-L210
@chipzoller  Can you please confirm if we still have to exclude _index.md files from deletion even with -c option? Because we are going to delete the target folder then all the files will be deleted.

Because we are going to delete the target folder then all the files will be deleted.

No, we don't want to delete the target folder, we simply want to delete everything inside of it (files and folders) EXCEPT _index.md.

@chipzoller Kindly review and test it once now.
When a user passes -c argument to the render function, then it will perform below steps.

Delete all the *.md files from the output folder passed with exception to _index.md.
Delete all the empty sub directories in the output folder.


CloudWatch metrics autoconfiguration

Hi,
This PR is follow up of https://github.com/spring-projects/spring-boot/pull/11276
Basically I want to add AutoConfiguration for AWS CloudWatch metrics,
but can't add id together with other metrics in SpringBoot as it requires at miniumum
ContextCredentialsAutoConfiguration
RegionProvider
from spring-cloud-aws.
Of course I could have implemented it from start, but I guess it wouldn't make sense as it's already there.
Property and bean names are consistent with metrics in Spring Boot actuator.
I know that previous version was deleted by @spencergibb  here:
https://github.com/spring-cloud/spring-cloud-aws/commit/33778b79d0c5f7553d46941f5e32399708ece704
https://github.com/spring-cloud/spring-cloud-aws/commit/7108d8fa76731f90bf532982c9dc64befe47c94b
but I restored spring-cloud-aws-actuator module as I needed dependency to spring-boot-starter-actuator
(org.springframework.boot.actuate.autoconfigure.metrics.export.StepRegistryProperties,
org.springframework.boot.actuate.autoconfigure.metrics.export.StepRegistryPropertiesConfigAdapter)
I thought it's better to have separate module for it than force users to download spring-boot-starter-actuator and it's dependencies always when they need spring-cloud-aws-autoconfigure.
also - needed to add

io.micrometer
micrometer-registry-cloudwatch
${micrometer.version}

in spring-cloud-build-dependencies
(https://github.com/spring-cloud/spring-cloud-build/pull/65)
as can't use ${micrometer.version} directly in spring-cloud-aws,
as it is defined in spring-boot-dependencies and
spring-cloud-build-dependencies is bom (and not parent) of spring-cloud-aws,
and spring-boot-dependencies is parent of spring-cloud-build-dependencies.
I use all of this code in my project in my company - it's working :)

of curse it won't build until https://github.com/spring-cloud/spring-cloud-build/pull/65 is merged

@dkublik you should have a chat with @jkschneider. This should go in boot 2.0 but without references to spring-cloud-aws.

Because CloudWatch support refers to the AWS SDK, we can't put CloudWatch autoconfig in Boot

@jkschneider so, micrometer-registry-cloudwatch is not a managed dependency in boot. Do we need to manage it here?

Merged with some compatibility changes via d5c8deac23c8840c74c6e6c3bb5507590a693706


(cargo-release) version 0.3.0

Current dependencies on/for this PR:

main

PR #176   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: 🔄 Waiting for checks to pass
This pull request is currently waiting for CI and mergeability checks to pass before being merged.
This comment was auto-generated by Graphite.

Job Reference: 15aK1CF6xb9qdoenZPPg