How to use azure Storage Account with k8s StatefulSet

If we use the default storage classes, it creates a storage account in the shadow resource group(MC_*), this resource group get deleted when we recreate the AKS cluster.
What should be the steps to use an existing Storage Account with StatefulSet resource where ersistent Volume needs to be created dynamically using StatefulSet's volumeClaimTemplate.  I have already created a storageAccount in the same RG as the AKS.
I tried to use secretkey and secretnamespae in storageClass, as mentioned in Kubernetes docs it ends up with error - invalid option "secretName" for volume plugin kubernetes.io/azure-file.
When I don't define the secret key in storageAccout resource,  AKS tries to look for storage account in shadow resource group(MC_)
PoC spec file
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: azurefile-standard-customtwo
provisioner: kubernetes.io/azure-file
reclaimPolicy: Retain
allowVolumeExpansion: True
parameters:
  skuName: Standard_LRS
  storageAccount: rahulpulsarpoc
  secretName: azuresecretname
---
apiVersion: v1
kind: Service
metadata:
  name: nginx2
  labels:
    app: nginx2
spec:
  ports:
    - port: 80
      name: web
  clusterIP: None
  selector:
    app: nginx2
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: web
spec:
  selector:
    matchLabels:
      app: nginx2 # has to match .spec.template.metadata.labels
  serviceName: "nginx2"
  replicas: 2 # by default is 1
  template:
    metadata:
      labels:
        app: nginx2 # has to match .spec.selector.matchLabels
    spec:
      terminationGracePeriodSeconds: 10
      containers:
        - name: nginx
          image: k8s.gcr.io/nginx-slim:0.8
          ports:
            - containerPort: 80
              name: web
          volumeMounts:
            - name: www
              mountPath: /usr/share/nginx/html
  volumeClaimTemplates:
    - metadata:
        name: www
      spec:
        accessModes: ["ReadWriteOnce"]
        storageClassName: "azurefile-standard-customtwo"
        resources:
          requests:
            storage: 1Gi

try this example: https://github.com/andyzhangx/demo/blob/master/pv/storageclass-azurefile-account.yaml, make sure you cluster identity could access the resource group specified in the storage class

make sure your cluster identity could access the resource group specified in the storage class

Even if both the AKS and Storage Account are in the same RG?  I see below error now. Would you please suggest the steps for this?
Failed to provision volume with StorageClass "azurefile-standard-customtwo": could not get storage key for storage account rahulpulsarpoc: could not get storage key for storage account rahulpulsarpoc: storage.AccountsClient#ListKeys: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="AuthorizationFailed" Message="The client '7f92309b-fd5f-401b-8c2c-3467ac1e9cad' with object id '7f92309b-fd5f-401b-8c2c-3467ac1e9cad' does not have authorization to perform action 'Microsoft.Storage/storageAccounts/listKeys/action' over scope '/subscriptions/f1c0b1e0-b22b-453c-871f-cd1bdbd2a3d2/resourceGroups/rahul-pulsar-poc/providers/Microsoft.Storage/storageAccounts/rahulpulsarpoc' or the scope is invalid. If access was recently granted, please refresh your credentials."

go to azure portal, under rahul-pulsar-poc, set access control, add your cluster's sp as contributor role

this worked. thanks.
It seems storageClass examples in Kubernetes docs  and should be updated.  OR a how to guide about StatefulSet on azure aks storage docs would benefit many

we are now switching to azure file csi driver, here are all the parameters explanation: https://github.com/kubernetes-sigs/azurefile-csi-driver/blob/master/docs/driver-parameters.md


NPM cannot download node-sass binding for Node 13

Describe the bug
Because of image: node:alpine in docker-compose.yml, fresh Node.js v13 is used. But there is no node-sass bindings published for Node 13 on Alpine.
><EMAIL_ADDRESS>install /app/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.12.0/linux_musl-x64-79_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.12.0/linux_musl-x64-79_binding.node":

HTTP error 404 Not Found

Steps To Reproduce
Steps to reproduce the behavior:

Clone this repo with master on this commit: https://github.com/BookStackApp/BookStack/commit/b93f8a4d4680cfe34e3b64db95f0f9683152c22a (last commit when I write this issue)
Run docker-compose up -d --build
Open node container logs
See error

Expected behavior
All containers is up
Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): v0.28-dev
PHP Version: 7.3
Hosting Method: Docker

Additional context
To fix this, I change docker-compose.yml to specify Node container version:
  node:
-    image: node:alpine
+    image: node:12-alpine

Thanks @Grawl for reporting this.
I have just fixed this in master by updating the npm dependencies so the project uses a node-13 compatible version of node-sass. Have tested by bringing up the docker-composer setup and checked it built the SASS files.
I thought about pinning the node image version as per your fix but I think I'll leave it for the mean-time since it was quite useful in this case; Using the latest version indicated that a dependency update was probably needed.


Add Taiko to Layer3 Quest

Describe the feature request
Include Taiko in the Layer3 quest lineup.
Layer3, is a rising website that can hosts graphical, pictorial, and educational quests aimed at enhancing users' comprehension of a project. Adding Taiko to this will boost Taiko visibility and help users to understand more about the project.
Website: https://layer3.xyz/quests
Spam policy

[X] I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

Feel free to either contact the team or if you are part of the team, formulate a proper application.


Updated dependencies:

How do I verify this? I have a local issue, but I don't know if this is a problem in practice:
Could not get unknown property 'mavenReleaseUrl' for object of type org.gradle.api.publication.maven.internal.deployer.DefaultGroovyMavenDeployer.

Android Gradle Plugin (3.1.4 -> 3.3.1)
Plugin Publish Plugin (0.9.10 -> 0.10.1)

I had the same problem when building this plugin locally. Looks like the uploadArchives-task runs for every build. You can make it build successfully nonetheless by removing this block of code: https://github.com/Mobbeel/fataar-gradle-plugin/blob/23a51621bf3425c2307d812f1bee104da4fe77d9/gradle/publish.gradle#L16-L42 (DO NOT COMMIT!)

This isn't a PR


Revisit random-delay

This is the commit message:
If enabled it will still delay randomly between 0-5 seconds.

However, the functionality to fine grain this is added.
Both seconds and milliseconds are supported now. Moreover,
min/max values for random delay can be condigured through
pflag params

First of all let me state this , I am not the most proficient Go Developer (far from it), so in case you have any objections please fire away!
Podinfo is great and I have been using it heavily. My latest use case was that I wanted to use podinfo to emulate some random delays (e.g. between 50-80 ms) to test out some fault injection cases. I thought I would add this here.
Although many more config parameters have been added, the default functionality is the same, that is if someone just enables --random-delay true it will ping pong between 0s-5s.
I think some validation is needed (i.e. max value should be >= min value). Also I think it makes sense to only support seconds and milliseconds, so a validation for the time unit should be in place.
I did not see a validation/sanity checking process so I would like to ask for your recommendation regarding that. Do you think it should be done in the middleware and just return an error/panic. Or a validation/sanity process for pflag arguments should be added before the actual Server is initiated?

I did not see a validation/sanity checking process so I would like to ask for your recommendation regarding that. Do you think it should be done in the middleware and just return an error/panic. Or a validation/sanity process for pflag arguments should be added before the actual Server is initiated?

I think the validation should be at startup and panic if the pflag validation fails.

Thanks @stefanprodan  I will do that later today. Other than that do you think this whole thing is valid/makes sense?

Added some simple validation steps.
Also I did run a go mod tidy (go version 1.14.4)

@commixon this is now released as 4.0.6


traverse_errors/2 doesn't seem to work when run on a top-level schema which has_many children schemas that have polymorphic embeds

An example:
defmodule A.Parent do
  # ...
  schema "parents" do
    has_many(:children, A.Child)
  end

  def changeset(%__MODULE__{} = struct, attrs) do
    struct
    |> cast_assoc(:children)
  end
end

defmodule A.Child do
  schema "children" do
    # ...

    polymorphic_embeds_one(:something, )
  end
end

params = %{
  # ...
  children: [
    %{
      something: ... # Here contains an error
    },
    %{
      something: ...
    }
  ]
}

When a changeset is inserted directly at the Parent level, but contains errors in the polymorphic embed of something at the Child level, PolymorphicEmbed.traverse_errors/2 when run on the resulting changeset still returns an empty map.
Not sure if Ecto.Changeset.traverse_errors/2 has the same behavior. At least the documentation of the Ecto function says

Traverses changeset errors and applies the given function to error messages.

This function is particularly useful when associations and embeds
are cast in the changeset as it will traverse all associations and
embeds and place all errors in a series of nested maps.

Can you test if the behavior is different? Replace the polymorphic embed by embeds_one and look for differences?

Fixed traverse_errors.


Property:samplingProtocol

Label
Sampling Protocol

Definition
The name of, reference to, or description of the method or protocol used during an Event

Usage
The name of, reference to, or description of the method or protocol used to gather objects in the collection.

Existing property
dwc:samplingProtocol

Existing class
Event

Existing property identifier
http://rs.tdwg.org/dwc/terms/samplingProtocol

Format
Text

Required
no

Repeatable

Constraints

Examples
UV light trap mist net bottom traw, ad hoc observation Penguins from space: faecal stains reveal the location of emperor penguin colonies https://doi.org/10.1111/j.1466-8238.2009.00467.x Takats et al. 2001. Guidelines for Nocturnal Owl Monitoring in North America. Beaverhill Bird Observatory and Bird Studies Canada, Edmonton, Alberta. 32 pp., http://www.bsc-eoc.org/download/Owl.pdf

Notes

There are different methods of collecting the specimens:

for terrestrial invertebrates there are used entomological nets (flying ones), different pitfall traps (walking ones) or even by hand collection
for aquatic vertebrates there are used some fishing gears (e.g stavnik) which  doesn't damage the animal (e.g fishes, sea turtles, dolphins etc. In some cases there are the big sea waves which bring the animals in the coast e.g the whale which is exposed in the Museum Natural Sciences in Albania)
for terrestrial mammal there are used some traps (sometimes the animal for collection is found sick or even killed and the leather is cleaned, given the shape of the animal and is used for the museum collection)

Thanks for the examples @Blerina01, we should incorporate them.

SESAR has a vocabulary for geo samples: http://www.geosamples.org/help/vocabularies#collection
Does anyone know of anything similar for biological samples? Collection Trust lists a few examples: https://collectionstrust.org.uk/resource/field-collection-method/

There was also a suggestion in the index sheet to use https://www.dublincore.org/specifications/dublin-core/collection-description/accrual-method/. I'd say that this is valid, but maybe not for this property, which is more about field collection (need to make the definition clearer in that respect). Collection accrual method might be appropriate as a seperate property, or part of the CollectionHistory class?

Agreed. That distinction is a good one.

If this defines an object was collected in the Field then  http://www.geosamples.org/help/vocabularies#collection appears to comprehensively fit main Earth Science field collection methods.

For the definition, the Collections Trust approach seems quite clear and simple: https://collectionstrust.org.uk/resource/field-collection-method/
and we could rename this property to fieldCollectionMethod

Here's a bunch of examples in use by collections in Arctos, although at the specimen level: http://arctos.database.museum/info/ctDocumentation.cfm?table=CTCULTURE

On 2020-03-25 12:47, Matt Woodburn wrote:

For the definition, the Collections Trust approach seems quite clear
and simple:
https://collectionstrust.org.uk/resource/field-collection-method/
and we could rename this property to fieldCollectionMethod
--
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2]. [ { "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target":
"https://github.com/tdwg/cd/issues/67#issuecomment-603795623", "url":
"https://github.com/tdwg/cd/issues/67#issuecomment-603795623", "name":
"View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url":
"https://github.com" } } ]
Links:
[1] https://github.com/tdwg/cd/issues/67#issuecomment-603795623
[2]
https://github.com/notifications/unsubscribe-auth/ANVT6LIDFBTB3FW2UHZHZODRJHVMRANCNFSM4JRVHAOA
Yes this definition works

cheers
Laura

Hi all,
If this is about how the specimen was obtained in the field, how is it really different from dwc:samplingProtocol? Could this be re-used?
Not sure I see the difference comparing both definitions...

changed field name from collectionMethod to fieldCollectionMethod
added new label to note this. label is "name changed"
adding new issue (need to use Maarten's template) for accrualMethod under Collection Description Class.
Log that this happened (add new property label).

Updated the property name and mapping to adopt @pzermoglio's suggestion: no need to duplicate dwc:samplingProtocol


Namespace/mosaic transactions doesn't appear in transaction list because of missing rental fees

users have to navigate to namespace/mosaic page first to fetch Estimated rental fees before being able to see their transactions in list

I did not notice any issue.


added dev and stable build groovy files

/run tests

Fix works with latest comp_clang

/run tests

/run tests

This needs to be rebased to pick up the port.h change, currently failing because it is in the PR's branch.

@HarithaIBM is this yours or Igor's? Wasn't sure from Igor's comment. I assigned to you but if Igor, please assign to him

@HarithaIBM is this yours or Igor's? Wasn't sure from Igor's comment. I assigned to you but if Igor, please assign to him

I will talk to Igor, Thanks Mike!

Here's one way via command line:
git fetch origin
git checkout devStabelBuild
git rebase origin/main


Icons: Remove Material.Obsolete, Update formatting

Description

Follow up on #8421
How Has This Been Tested?

Types of changes

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

Checklist:

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[ ] I've added relevant tests.

Thanks @danielchalmers

Wanted to add this to the guide https://github.com/MudBlazor/MudBlazor/issues/8447 since some icons are permanently removed, but the list would be huge. So just added the link to the PR.


How about running resize in both terminal and conhost?

I commented about this on #1465, but this may deserve an issue (for PR, to have separate discussion).

My best bet to fix or at least simplify this [#1465] is to not emit new resized buffer from conhost, but instead run the resize on terminall's buffer too. This way both buffers should be the same and additionally terminal will have access to context of the resize, which would e.g. enable us to track selection transform (#1368), and maybe to fix the bugs above too.
It should be at least as (in)efficient as it is now (especially over network), because despite doubled work, conhost wouldn't need to transfer the buffer back to terminal, which seems comparatively costly.
It could eventually be futher optimizied so thet when user drags window the resize runs only on terminal's buffer and is reported to conhost only when the user releases LMB (but this would reqiure to freeze sth like the conhost does when scrolling?).
And since you want to support existing 3-party terminals - they handle resize themselfs. So while the present solution should work, it will be unusual to them and may cause some troubles such as we have now (even if we resolve them on terminal side).
And finally, in passthrough mode terminal would have to resize the buffer itself.

How are you about that?

I typed up a response to this question in the original thread, as I think it had some bigger context that was relevant there. I'm closing this one to merge back in with the parent.


add bower manifest file

Hi @renvrant
Great little plugin  -  thanks for sharing!  If you're open to a PR then I thought it might be nice to have this on Bower?  Should be good to go - all you'll have to do is run:
bower register conditionize  https://github.com/renvrant/conditionize.js

:+1:

Hey @FourStacks, thanks so much! I hadn't even thought of including it on Bower. Will happily merge your change in!

Thanks @renvrant!

Hi again!  Just to let you know I've registered the package on bower but as they want all packages to adhere to semver tagging then you'll need to release a valid semver tag to get bower to recognise that there's a new (and currently single) release available.  After that it should be listed under search on bower.
Cheers!


storage missing in typed graphcache

Describe the bug
When updating to latest urql and codegenerators, I'm getting following type-error:
src/client/graphql/client.ts:78:37 - error TS2345: Argument of type '{ keys: { ...: () => null; }; updates: { Mutation: { ...: (result: { ...: WithTypename<ReviewRequest>[]; }, args: ..., cache: Cache) => void; ... 25 more ...; ......' is not assignable to parameter of type 'GraphCacheConfig'.
  Property 'storage' is missing in type '{ keys: { ... }; updates: { Mutation: { ...: (result: { ...: WithTypename<ReviewRequest>[]; }, args: ..., cache: Cache) => void; ... 25 more ...; ...' but required in type 'OfflineExchangeOpts'.

 78     cacheExchange<GraphCacheConfig>({
                                        ~
 79       keys: {
    ~~~~~~~~~~~~~
...
435       },
    ~~~~~~~~
436     }),
    ~~~~~

  node_modules/@urql/exchange-graphcache/dist/urql-exchange-graphcache.d.ts:115:5
    115     storage: StorageAdapter;
            ~~~~~~~
    'storage' is declared here.

Is storage now needed or is the type-error a bug?
Reproduction

Urql version
"urql": "^4.0.6",
"@urql/devtools": "^2.0.3",
"@urql/exchange-auth": "^2.1.6",
"@urql/exchange-graphcache": "^6.4.0",
"@urql/exchange-retry": "^1.2.0",

Versions without issues:
"urql": "^4.0.2",
"@urql/devtools": "^2.0.3",
"@urql/exchange-auth": "^2.1.2",
"@urql/exchange-graphcache": "^6.0.4",
"@urql/exchange-retry": "^1.2.0",

Validations

[X] I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which GitHub Discussions should be used
[X] Read the docs.
[X] Follow our Code of Conduct

That's a bug in latest graphcache codegen, have a PR open there but not much luck 😅

I did everything within my power to move it forward and 👍ed the PR! Thanks for the workaround!

Updated my PR going to close this out as it's not in our power


Deploy einstein-0.1

.jar needs to be deployed
javadoc needs to be deployed
release notes needs to be deployed (in the wiki)

einstein-0.1-release now live


Enable Community models

Hey there,
to be able to use community provided models we need to set trust_remote_code=True.
So I update the sentence_transformers package and added einops requirements which was necessary to use the nomic-ai/nomic-embed-text-v1.5 model for example.
Feel free to integrate if it is helpful :)
Love,
Yannick

Thanks! Yeah definitely useful. I simply hadn't tried models that require this before.


Make default log format less verbose

Change the default format for logfiles to omit information about
the class, function and thread id. This information adds a lot
of visual noise and little value. In particular the thread id can
easily be confused with a unix time stamp.
Before:
5235076 vast DEBUG actor24<PHONE_NUMBER>96832 size_t,%20size_t,%20const%20vast.path&,%20vast.system.archive_type,%20caf.actor)<GLOBAL operator() disk_monitor.cpp:114 disk_monitor erasing removed ids from archive

After:
5235076 vast DEBUG actor24 disk_monitor.cpp:114 disk_monitor erasing removed ids from archive

I'm with @dominiklohmann. This is a refreshing change.


Revamp of MiqViq's USB module

MiqViq's keyboard and mouse module, but revamped for all USB devices

tx!!


ARROW-7472: [Java] Fix some incorrect behavior in UnionListWriter

Related to ARROW-7472.
Currently the UnionListWriter/UnionFixedSizeListWriter getField/close APIs seems incorrect.

@praveenbingo or @BryanCutler I'm not super familiar with this code, but the change look reasonable could one of you double check?


Add custom fontsize support for notifications

Describe your PR, what does it fix/add?
This adds support for specifying a custom font size the notification will be rendered with.
Fixes #4866

Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
This is technically a breaking change for anyone who is currently using hyprctl notify, as it requires an extra argument for the font size.
Note that I'm not entirely sure how the font size calculation worked in the original code here:
        const auto            FONTSIZE        = std::clamp((int)(notif->fontSize * ((pMonitor->vecPixelSize.x * SCALE) / 1920.f)), 8, 40);

I pretty much just reused this code and used notif->fontSize, instead of the hard-coded value. I think this is the correct way to do it, but I'm not certain of it.
Is it ready for merging, or does it need work?
Ready.

Yeah, I agree, but I'm not sure how to achieve that when all of the arguments after 5th were just treated as parts of the msg. Any suggestions?

why not make this just a config variable

I considered that, but I figured the issue author wanted to be able to set different sizes for different notifs. If a single size is enough though, I can modify this

I am for specifying args at the beginning of the message then, like:
fontsize:17 Hello Hyprland!


Implement cookie allocator to mark flow by cookie id

Added a cookie allocator to mark flow by cookie id
Added function roundNum to pipeline.go to read roundNum from ovsdb
Updated related mocks and unit tests
Fixed some typos

Signed-off-by: Weiqiang TANG<EMAIL_ADDRESS>

/test-e2e


[PubSub] Error when waiting for subscriber to stop

Hi there!
We wrap PubSub and have a spec that ensures we correctly publish messages. I've noticed that RSpec would hang a bit longer with an error message:
E0809 17:05:14.171328706   12218 backup_poller.cc:110]       run_poller: {"created":"@1533845114.171295122","description":"Shutting down timer system","file":"src/core/lib/iomgr/timer_generic.cc","file_line":704}

After some retries, I didn't get the message all the time. I then decided to add a sleep 0.1 after calling subscriber.stop.wait! and the error message disappeared.
It seems to me there is a race condition on the wait! method that is triggering this underlying error.
My environment:
Ruby: 2.5.1
Bundle:
  * google-cloud-core (1.2.2)
  * google-cloud-env (1.0.2)
  * google-cloud-pubsub (0.31.0)
  * google-gax (1.3.0)
  * google-protobuf (3.6.1)
  * googleapis-common-protos (1.3.7)
  * googleapis-common-protos-types (1.0.2)
  * googleauth (0.6.4)
  * grpc (1.14.1)
  * grpc-google-iam-v1 (0.6.9)

This message is printed by the grpc library during its cleanup. It is not an error. We have been told it is benign. See grpc/grpc#14180.

I don't care much about the message, but the spec process hangs around a lot longer when that message pops up (2-3 seconds) which leads me to think it's not just a message

I'll look into it.

We have recently updated the threading implementation used by Subscriber, and we think it should be more reliable. This will go out in the next release.

@Draiken Please try google-cloud-pubsub 0.32.0. It overhauled the Subscriber threading and hopefully won't cause additional GRPC cleanup. Let us know how it performs and if it satisfies this issue.

@blowmage seems to have fixed this issue for me. Thank you very much.


ARROW-54 Make ObjectId an Extension Type

Whoops, we need to update the supported types docs page now too.

Updated


Debugging credentials

2.1.0
I am using sabredav with Z-Push-Contrib from fmbiete (https://github.com/fmbiete/Z-Push-contrib). Problem: When receiving a meeting invitation, I don't see buttons to accept/decline the invitation. When opening the attached ics file, I see my own email address with "no answer" besides. It seems like the invitation is not properly assigned to my own calender, although the email address of the attendee matches exactly my own address. I did the setup of my principal as described here: http://sabre.io/dav/caldav-proxy/. Did I miss anything? I am having some more trobles with Mac OS X Calendar App which does not automatically recognize invitations as well, so I assume that there is any problem with my email address in sabredav. What is the best way for debugging?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6403213-debugging-credentials?utm_campaign=plugin&utm_content=tracker%2F294006&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F294006&utm_medium=issues&utm_source=github).

Sorry for never have gotten to a real response here. I'm closing this ticket because it's been too long and I never fully figured out what the core issue was.
If we can somehow reopen this in the future as a new ticket that has a clearer problem statement I'm definitely interested, but given the current state of this ticket I think it's best to just close it.


[DMP 2024]: Liblouis table editor

Ticket Contents
Description
“The Liblouis software suite provides an open-source braille translator, back-translator, and formatter for many languages and braille codes. It is a set of libraries designed for use in several applications, both free and commercial.”   - https://liblouis.io/
Numerous software applications like NVDA, JAWS, BrlTTY, TalkBack, make use of liblouis. Total global user count is in millions. Many projects developed in Zendalona utilize liblouis, including IBus-Braille, Sharada-Braille-Writer, Braille-Translator-GUI, and the Braille-Translator Web version.
Creating Liblouis translation tables is a laborious and time-consuming task. Both software developers and end users at the Braille printing press require a more convenient method for editing the liblouis table. Furthermore, in numerous languages, the editing process involves inputting Unicode code points instead of directly writing the letters, adding an extra layer of complexity to the table editing process.
Goals & Mid-Point Milestone
Goals

[ ] Goal 1: Implement the GUI
[ ] Goal 2: Add table testing facility
[ ] Goal 3: Facilitate unicode codepoint visibility

Setup/Installation
No response
Expected Outcome
Liblouis manual : https://liblouis.io/documentation/liblouis.html#How-to-Write-Translation-Tables
We require a free and open-source Liblouis table editor compatible with GNU/Linux, Microsoft Windows, and macOS, fulfilling the following criteria:
1 Display characters as they are alongside their Unicode code points.
2 Provide a drop-down list for selecting opcodes.
3 Enable the insertion of operands through entries with validity checks.
4 Include an option to test forward and back-translation on the fly.
5 Allow users to view and modify the Unicode character equivalent corresponding to the written Unicode code point.
6 Indicators to ensure the user is aware of duplicate entries.
7 Should be accessible to visually challenged people
Acceptance Criteria
No response
Implementation Details
Python, Qt
Mockups/Wireframes
No response
Product Name
Liblouis-Table-Editor
Organisation Name
Zendalona
Domain
Learning & Development
Tech Skills Needed
Python
Mentor(s)
@Nalin-x-Linux
Category
Accessibility

Hii @Nalin-x-Linux ,
I am Akanshu Aich, a third year BTech student from International Institute of Information Technology, Bhubaneswar. I am writing to express my interest in contributing to this project as a part of DMP 2024. Having thoroughly reviewed the project, I am impressed by its objectives and it seeks the potential for great impact in industries.
With my background in Backend using Django , MERN with practicing hands on Machine learning and DevOps such as Docker, I believe I can make valuable contributions to Machine learning part . My experience includes several projects like Society-Expenditure Manager using Django, Real Estate using MERN and Info-Finding Tool using Machine Learning(LLM), which I believe align well with the goals of your project.
I am particularly interested in fulfilling the requirements of the project and have some ideas on how to approach it effectively. I am committed to adhering to best practices, contributing high-quality code, and actively collaborating with the project maintainers and community.
I am excited about the opportunity to contribute to "Liblouis-Table-Editor" and help further its mission. I look forward to discussing potential contributions and how I can best support the project.

hi @Nalin-x-Linux ,
My name is Saksham Sharma, and I am a student at Kalinga Institute of Industrial Technology (KIIT) in Bhubaneswar. I am writing to express my keen interest in joining your project, specifically in contributing to the development of the Liblouis software suite.
Having familiarized myself with the capabilities and widespread usage of the Liblouis software suite, as outlined on the official website [https://liblouis.io/], I am genuinely impressed by its impact and potential. It is evident that Liblouis plays a crucial role in facilitating accessibility for millions of users globally, particularly in enabling the translation and formatting of text into various braille codes.
One aspect highlighted in your project description resonates deeply with me – the laborious and time-consuming nature of creating Liblouis translation tables. As a software enthusiast, I recognize the importance of streamlining this process for both developers and end-users. The need for a more convenient method for editing Liblouis tables is not only evident but also essential for enhancing accessibility and usability.
Moreover, the complexity involved in editing tables in numerous languages, requiring inputting Unicode code points instead of directly writing letters, underscores the necessity for innovation in this domain. I am eager to contribute my skills and knowledge towards developing solutions that address these challenges effectively.
My background in [mention any relevant skills, experience, or coursework] has equipped me with the necessary technical expertise to contribute meaningfully to your project. I am passionate about leveraging technology to make a positive impact on society, particularly in the realm of accessibility and assistive technologies.
I am excited about the opportunity to collaborate with your team and contribute to the advancement of the Liblouis software suite. Please find enclosed my resume for your review. I am available at your earliest convenience for an interview to discuss how I can contribute to your project further.
Thank you for considering my application. I look forward to the possibility of working together.
Warm regards,
Saksham Sharma

Hello @Nalin-x-Linux,
I'm Yash Panjwani, a third-year student at MIT World Peace University. I'm enthusiastic about joining the Liblouis-Table-Editor project. As someone keen on accessibility and Python development, with a deep understanding of Backend Frameworks like Django and Node.js, I see this as a fantastic opportunity to contribute meaningfully. Looking forward to your guidance.

Hello @Nalin-x-Linux ,
Iam final year student in cse and much interested in working with python as Iam doing coding in python since years.Thank you.

Hello @Nalin-x-Linux
I am Gurjot Kaur, a second-year engineering student specializing in Artificial Intelligence and Machine Learning (AIML). I am writing to express my strong interest in joining your project team for DMP 2024. After going through the project documentation, I have decided to submit my proposal to become a part of this great cause.
I come from a Machine Learning background with proficiency in Python and ML applications in NLP, object detection, data processing and synthesis, chatbots, and LLM fine-tuning.
I am willing to adapt and learn new skills. I strongly believe that I can contribute significantly to this project while learning from your experienced team of professionals.
Regards,
Gurjot Kaur

Hii @Nalin-x-Linux  I am Divya studing 3rd year in GNITS and learning python. I am interested to work on this ticket.

With a background in Machine Learning, I excel in Python and have applied ML techniques in various domains such as NLP, object detection, data processing, synthesis, chatbots, and LLM fine-tuning. I'm eager to expand my skill set and collaborate with your experienced team to contribute effectively to this project. My portfolio includes numerous successful projects in NLP, object detection, face detection, and text insights, reflecting my capability and expertise in these areas.

Hii @Nalin-x-Linux I am Biyas studying 3rd year in UEM, Kolkata and learning python. I am interested to work on this ticket as I have already done a project on Python.

Ticket Contents
Description
“The Liblouis software suite provides an open-source braille translator, back-translator, and formatter for many languages and braille codes. It is a set of libraries designed for use in several applications, both free and commercial.” - https://liblouis.io/
Numerous software applications like NVDA, JAWS, BrlTTY, TalkBack, make use of liblouis. Total global user count is in millions. Many projects developed in Zendalona utilize liblouis, including IBus-Braille, Sharada-Braille-Writer, Braille-Translator-GUI, and the Braille-Translator Web version.
Creating Liblouis translation tables is a laborious and time-consuming task. Both software developers and end users at the Braille printing press require a more convenient method for editing the liblouis table. Furthermore, in numerous languages, the editing process involves inputting Unicode code points instead of directly writing the letters, adding an extra layer of complexity to the table editing process.
Goals & Mid-Point Milestone
Goals

[ ]  Goal 1: Implement the GUI
[ ]  Goal 2: Add table testing facility
[ ]  Goal 3: Facilitate unicode codepoint visibility

Setup/Installation
No response
Expected Outcome
Liblouis manual : https://liblouis.io/documentation/liblouis.html#How-to-Write-Translation-Tables
We require a free and open-source Liblouis table editor compatible with GNU/Linux, Microsoft Windows, and macOS, fulfilling the following criteria: 1 Display characters as they are alongside their Unicode code points. 2 Provide a drop-down list for selecting opcodes. 3 Enable the insertion of operands through entries with validity checks. 4 Include an option to test forward and back-translation on the fly. 5 Allow users to view and modify the Unicode character equivalent corresponding to the written Unicode code point. 6 Indicators to ensure the user is aware of duplicate entries. 7 Should be accessible to visually challenged people
Acceptance Criteria
No response
Implementation Details
Python, Qt
Mockups/Wireframes
No response
Product Name
Liblouis-Table-Editor
Organisation Name
Zendalona
Domain
Learning & Development
Tech Skills Needed
Python
Mentor(s)
@Nalin-x-Linux
Category
Accessibility

hey @Nalin-x-Linux i am Rohith H Y presently doing my prefinal year bachelors in ECE,I am interested to be a part of the liblouis table editor project,i am too late to submit sorry and please oblige my request

Hey @Nalin-x-Linux I am Divyanshu presently I am pursing second year in computer science engineering (CSE), I am interested to work on this project. so can you project assign to me.
As I have also work as GSSoC contributor.
Regards
Divyanshu


Combing novel with the updates

When the novel is updated it does not put it together with the original file is there a way to combine them so that the original file it updated to the latest release or am I just missing something?

If NG can find the previous epub, new chapters should be added to the end of it. Maybe check for an error message "could not find old file" in the log.

[2021-09-06T14:46:21] No accounts file found.

So I needed to go to the file created under my user name not the file that I had on my desktop to get it to check the files in the account.

No accounts file found.

This message is irrelevant, it always prints that if you don't have any account cookies stored for a source.
Just to make sure we are on the same page: You are talking about the library fetching newly released chapters for a favourited novel?  The "normal" download can't update files. (The next major release of NG will be able to, but that still a bit off)

Yeah talking about favorited novels figured out that I had created a file for NG-Launcher.jar and was launching from that on my Desktop which wasn't the same as the file created under my username file. So I launched the .jar from the user/bin file which allowed to to find the account cookies I guess hard to explain would have to show to make this a lot easier.

With 'created file' do you mean a shortcut to run NG? It can be a bit picky with where it is started from because of relative paths (bad programming, my bad), ideally you want to run the .jar from inside the NG bin folder.
If you click on a novel in the library tab, it shows a save location path, it will look for the old file there and update the EPUB with the matching file name.

Yeah found it after looking and just started to run the NG launcher through the bin file and its all good free program so can't complain =) love the program itself just tying to get my Librera app and google sync to play nice so I can update it there and read the updates without having to copy paste every update.

Sounds good!


Want to improve UI of password validator

Since, the UI design of password validator is not that attractive.
I want to improve the UI/UX design of password validator website to become more attractive.
Could you please assign me this issue under GSSOC'23 : )

@Illuminati9 It would be great if you share relevant screenshot if you want to make any changes in existing features.

@Saurabh-kumar09 , Here is the screenshot of the improved UI for password validator to look more attractive.

Also it shows prompt when the password is correct without using alert.


Databricks No matching distribution found for Azure-blob-storage

Which service(blob, file, queue) does this issue concern? Blob storage account
Which version of the SDK was used? Please provide the output of pip freeze.
Azure Blob storage == 2.0.1
What problem was encountered? It with trying to import the library into the blob storage. Here is the message - java.lang.RuntimeException: ManagedLibraryInstallFailed: org.apache.spark.SparkException: Process List(/databricks/python/bin/pip, install, Azure-blob-storage, --index-url, https://pypi.org/project/azure-storage-blob/, --disable-pip-version-check) exited with code 1.   ERROR: Could not find a version that satisfies the requirement Azure-blob-storage (from versions: none)
ERROR: No matching distribution found for Azure-blob-storage
for library:PythonPyPiPkgId(Azure-blob-storage,None,Some(https://pypi.org/project/azure-storage-blob/),List()),isSharedLibrary=false
Have you found a mitigation/solution? no
Note: for table service, please post the issue here instead: https://github.com/Azure/azure-cosmosdb-python.

Is there a PyPI url I can point my databricks library to for this update? I point to the current one and it comes up with 12.0.0, which my program says is out of date. https://pypi.org/project/azure-storage-blob/

Hi @ryanwrationalcx
are you asking this https://pypi.org/project/azure-storage-blob/2.1.0/
BTW you can find all releases by clicking “History” from the link you provided 😊

Hi @ryanwrationalcx
I'll close this issue for now, feel free to reopen it if you need other help! ^_^


fix asyncz settings crash and warn for empty tasks

Changes:

fix crash when no tasks are provided
fix hard to ignore UserWarning for a perfectly fine configuration without tasks.

ok not really hard to ignore when using properties but just a nuisance.


Can't find repository in NPM

I tried installing using npm, but the repo was not found. The log shows error 404 Not Found: silvermine-videojs-chromecast@latest. Is this plugin maintained anymore?

We haven't published this module to an NPM repo yet. You can npm install --save git+https://github.com/silvermine/videojs-chromecast.git#4e10ff306f3a3457bb392c5a841a62df0050ec3f

hi, thanks for getting back. Please edit your readme and add a flag that your repository isn't published in NPM yet, because it clearly states that we can install it using NPM. That will remove the confusion for everyone. cheers!

@Snowbell92 today this plugin was published as<EMAIL_ADDRESS>Sorry about that!
Note a couple things about this release:

It includes a bug fix for #17. If you use jQuery, consult the updated README
It was renamed from silvermine-videojs-chromecast to @silvermine/videojs-chromecast because we're moving all our modules over to an NPM organization instead of having them published under a single publisher (me).


[SILGen] Add SILDeclRef for main entry-point

Allow SILDeclRef to refer to the main program entry-point, which will either be for a main SourceFile, or a synthetic main such as an @main decl. Adjust the various SILDeclRef related functions to handle this new case, and change the emission to go through emitFunctionDefinition.
This change will allow the entry-point for an @main decl (and eventually a main SourceFile) to be emitted on-demand from its symbol name.

@swift-ci please test

@swift-ci please test source compatibility

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 9020c1301a3d006e4ce5b42e358021133fbcdee3

@swift-ci please test macOS

@swift-ci please test


Mobile trading pg positions fields are scrunched together

Fields under the positions section of the trading pg on Mobil are all jumbled together....
see screenshot
https://cdn.discordapp.com/attachments/464067340015763466/568586637345423360/Screenshot_20190418-195855.jpg

I think this has been addressed with recent push to sneakpeak. I'll verify.

looks fixed, can you confirm @Chwy5

better - closing


bug: GCP DNS - DNSSEC in private DNS Zone

Describe the bug
By creating a private DNS zone in GCP tfsec runs into an error message (google-dns-enable-dnssec][MEDIUM] - Managed zone does not have DNSSEC enabled.). DNS private zones does not support DNSsec (only DNS public zones).
To Reproduce
Steps to reproduce the behavior:

Create a terraform "resource" "google_dns_managed_zone" with name e.g. "test.my-domain.com"

resource "google_dns_managed_zone" "private" {
  project = var.project_id

  for_each = var.dns_managed_zone_private

  name       = replace(each.key, ".", "-")
  dns_name   = "${each.key}."
  visibility = "private"
  private_visibility_config {
     network_url = "projects/${var.project_id}/global/networks/${var.network}"
  }
}

Run tfsec validation

$ tfsec .

Expected behavior
TFSec detects an error ( 1 potential problems detected. )
(https://aquasecurity.github.io/tfsec/v1.0.7/checks/google/dns/enable-dnssec/)

Thanks @Nevana  - this is being pushed through the build process and should be released as a new tfsec version shortly

@Nevana  - released in tfsec v1.19.0 https://github.com/aquasecurity/tfsec/releases/tag/v1.19.0


DOC: Avoid documenting base class methods

For #11173, avoid documenting BaseRaw and BaseEpochs methods. This makes it so that searching plot_psd for example no longer shows BaseRaw or BaseEpochs. It's not perfect because the pages still list the names, but I think this is okay -- end-users will ignore these and can easily look at Raw or Epochs for them.

Seems to work
https://output.circle-artifacts.com/output/job/94cd6250-a82d-45d8-ba1c-3bdf16b87958/artifacts/0/dev/generated/mne.io.BaseRaw.html
Must be merged manually because I skipped a bunch of CIs


feat(package): Add privacyInfo bundle and depency system frameworks

添加依赖系统库及隐私清单bundle文件内容到podspec文件

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


fix: update player options validation to allow single objects

After a some research, I found the issue which prevented the player's voice payload from being updated.
Internally, the player was updated with the payload but due to that small issue in the if statement, did not allow it to sync the data completely.
In the first instance, the payload was received but was never processed for allocation due to the check.
The proposed solution has been tested and is functional and does not affect other operations as it only allows paylods to be processed with a single key.

Done!

Published with v2.4.2


First round of fixes

I'll leave this open so it can be added to 😇

Now all the issues I could fix are fixed. Those missing I either need more info or are not our issues. :stuck_out_tongue:
If you want to merge, feel free.


Instruction tuning

kube-ray (xiaochang) .
huggingface/transformers(xinyu)

Instruction tuning with huggingface/transformers is supported in this PR.


invisible pipeline ".drone.yaml" if ".drone" multi pipeline is used

if you use a folder to store pipelines in it, and call one of them .drone.yaml it wont show up in ui

I investigate a bit this issue.
It seems to come from web/src/screens/repo/screens/build/components/procs.js.
I'm not so fluent in JavaScript, so i'm not sure how to proceed.

How it works today :  if the name of "proc" (see JSON in browser) is drone, we assume we are not in multipipeline mode.
Two options :

Instead of checking names, we could check if there are multiple procs or only one. But i don't know how to do that (i never learn React).
Maybe we shouldn't change anything and write in the doc not to use ".drone.yml" or "drone.yml" as the name of the file. The rationale behind it : name of a file describes a "pipeline". A pipeline "drone" is not very explicit, better use : tests, lint, build, publish, docker, doc, etc.

@anbraten this one;)


Hide LLDP option for IP over InfiniBand interface.

The IP over IB has no link layer, but LLDP is for link layer.

@cathay4t Could you please assign this issue to me?

@96RadhikaJadhav Sorry. I missed this notification. Do you still have time and interest on this task?

@cathay4t  I am interested to work on this issue please assign to me

@cathay4t Assign it to me if not already assigned!

@cathay4t @ffmancera
From my understanding we need to hide the LLPD option for IP over InfiniBAnd interface because InfiniBand does not have a traditional link layer like Ethernet.
I would like to work on this issue, could you please assign it to me.


Resp: Make mobile landscape view of the simulator.

Is your feature request related to a problem? Please describe.
Currently, the mobile view of the simulator is not as expected various components are overlapped on each other.
Describe the solution you'd like
To make buttons for each and every draggable component which on click opens that tab.
Describe alternatives you've considered
N/A
Checklist

[ ] Adding Navbar
[ ] Adding Side Bar
[ ] Made buttons of Side Bar functional

Expected

Current

Are you working on this? (Yes/No)
Yes

@Arnabdaz @Prerna-0202 for doing this I will be opening individual PRs for each button components
Would be happy to get a better approach from your side.
Thank You : )

@Arnabdaz Just a ping for PR review
Thank You : )

as these are subtask of possible task of a possible gsoc project we might not merge till next gsoc starts but you can use these as proof of work.

as these are subtask of possible task of a possible gsoc project we might not merge till next gsoc starts but you can use these as proof of work.

I understand : )


[csolution] no IAR version in cprj ?

yml file:
  build-types:
    - type: AC6
      compiler: AC6
      misc:
        - C*:
          - -std=c99
    - type: GCC
      compiler: GCC
      misc:
        - C*:
          - -std=c99
    - type: IAR
      compiler: IAR
      misc:
        - C*:
          - -std=c99

cprj file:
  <compilers>
    <compiler name="IAR" version="0.0.0"/>
  </compilers>

==> I would have expected version 8.50.6 as we have IAR.8.50.6.cmake

@fred-r could you please validate that this problem got fixed in csolution 1.1.0.

@JonatanAntoni could you create an example that shows switching from AC6, GCC, IAR using a cdefault.yml file?
this releates to #615

We have an example that shall work for all three compilers here: https://github.com/ARM-software/CMSIS-View/tree/eventstatistic/Examples/EventStatistic
The example is still work in progress and doesn't compile for IAR as it depends on other open PRs still in progress as well. But it can be used to verify if the generated .cprj is as expected for IAR compiler:
./CMSIS-View/Examples/EventStatistic $ cp EventStatistic.iar-cdefault.yaml EventStatistic.cdefault.yaml

./CMSIS-View/Examples/EventStatistic $ csolution convert -s EventStatistic.csolution.yaml -c EventStatistic.Debug+CM3
./EventStatistic.Debug+CM3-IAR/EventStatistic.Debug+CM3.cprj - info csolution: file generated successfully
./EventStatistic.cbuild-idx.yml - info csolution: file generated successfully
./EventStatistic.Debug+CM3-IAR/EventStatistic.Debug+CM3.cbuild.yml - info csolution: file generated successfully

./CMSIS-View/Examples/EventStatistic $ grep 'compiler name="IAR"' EventStatistic.Debug+CM3-
IAR/EventStatistic.Debug+CM3.cprj
    <compiler name="IAR" version="9.30.1"/>

The problem seems to be fixed in latest csolution 1.4.0.


issue #7

Hi,
I would like to add the ability to read from .md files and identify bold and italics and adding the added formatting to the generated HTML.

Could you update the README.md with your features? Please make a PR with the updates.


Uncaught TypeError: Cannot read property 'Component' of undefined

When trying to build an app with this dependency, react logs the following error to the console. I've set the appElement to '#root' in my index.js file and tried using ariaHideApp={false}, but neither have solved the error.
Uncaught TypeError: Cannot read property 'Component' of undefined
    at Object.<anonymous> (react-modal.min.js:34)
    at n (react-modal.min.js:1)
    at Object.<anonymous> (react-modal.min.js:13)
    at n (react-modal.min.js:1)
    at Object.<anonymous> (react-modal.min.js:13)
    at n (react-modal.min.js:1)
    at react-modal.min.js:1

@finleyowen Which version are you using?

Same issue i am using version 3.14.3

If you are using <Modal appElement={node} />, node needs to be a dom node...not a string. Can you check if this is the issue?

I'm facing a similar issue. Here are the attributes I'm passing on to ReactModal.
<ReactModal
        ariaHideApp={false}
        isOpen={showLoginModal}
        onRequestClose={closeModal}
        className="bg-whitish w-[80%] h-[70%] md:w-[50%] md:h-[30%] rounded-md absolute top-[50%] left-[50%] transform -translate-x-1/2 -translate-y-1/2 border border-blackish flex flex-col justify-center items-center"
>

Here is the error I'm getting.
Uncaught TypeError: Cannot read properties of undefined (reading 'Component')
    at Object.<anonymous> (react-modal.min.js:34:9446)
    at n (react-modal.min.js:1:450)
    at Object.<anonymous> (react-modal.min.js:13:4246)
    at n (react-modal.min.js:1:450)
    at Object.<anonymous> (react-modal.min.js:13:3589)
    at n (react-modal.min.js:1:450)
    at react-modal.min.js:1:1250
    at react-modal.min.js:1:1259
    at react-modal.min.js:1:290
    at react-modal.min.js:1:312

Can someone help me out with this?

@diasbruno 3.15.1

Uncaught TypeError: Cannot read properties of undefined (reading 'Component')
at Object. (react-modal.min.js:34:9446)
at n (react-modal.min.js:1:450)
at Object. (react-modal.min.js:13:4246)
at n (react-modal.min.js:1:450)
at Object. (react-modal.min.js:13:3589)
at n (react-modal.min.js:1:450)
at react-modal.min.js:1:1250
at react-modal.min.js:1:1259
at react-modal.min.js:1:290
at react-modal.min.js:1:312
version is: "react-modal": "^3.16.1",

If you want to make a reproducible example for this...one can create a new react project and add react and react-modal (with some combination of versions).
This should trigger the issue, and, we can finally address it.

As people have found out, if you delete node_modules and reinstall everything, it works. It seems a cache issues.
Please, feel free to reopen if that's not your case.

As people have found out, if you delete node_modules and reinstall everything, it works. It seems a cache issues. Please, feel free to reopen if that's not your case.

It still don't work having same issue my react-modal version "react-modal": "^3.16.1" and react version "react": "^18.2.0",
error. "react-modal.min.js:34 Uncaught TypeError: Cannot read properties of undefined (reading 'Component')
at Object. (react-modal.min.js:34:9446)
at n (react-modal.min.js:1:450)
at Object. (react-modal.min.js:13:4246)
at n (react-modal.min.js:1:450)
at Object. (react-modal.min.js:13:3589)
at n (react-modal.min.js:1:450)
at react-modal.min.js:1:1250
at react-modal.min.js:1:1259
at react-modal.min.js:1:290
at react-modal.min.js:1:312
"

react-modal.min.js:34 Uncaught TypeError: Cannot read properties of undefined (reading 'Component')
at Object. (react-modal.min.js:34:9446)
at n (react-modal.min.js:1:450)
at Object. (react-modal.min.js:13:4246)
at n (react-modal.min.js:1:450)
at Object. (react-modal.min.js:13:3589)
at n (react-modal.min.js:1:450)
at react-modal.min.js:1:1250
at react-modal.min.js:1:1259
at react-modal.min.js:1:290
at react-modal.min.js:1:312
same issue I am getting. react-modal version "react-modal": "^3.16.1" and react version "react": "^18.2.0",


Fix 25/route params

Coverage increased (+0.8%) to 94.843% when pulling 3a4ef0db6c7105abdfb8e85f33b83bbb44b8f1f9 on fix-25/route-params into 4ef8346a689997857e73c7992605492737802b9e on master.


Standardize ID case

Description:

Because clientID and teamId use differents cases.

Agreement: will be merged in next major


Update interactivity.md

fix wrong styles

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

Coverage remained the same at 62.388% when pulling b20970a46374b7f5d42b91bd72463f498f66f3c8 on cs09g:patch-1 into be3e4e20dadcddff978ff32f02210aff8c52fcab on uber:master.


oclazyload

Hello, this is a great example! Could you explain the use of oclazyload?

Hello and thank you!
oclazyload is essentially being used to instantiate angular code after load, and is essentially wrapping the response from our require calls in angular.X() calls.
See:
https://oclazyload.readme.io/docs/oclazyload-service#

Makes sense. So I didn't see any documentation where you pass in an object with a name parameter.
$ocLazyLoad.load({name: 'About'})
I assume this loads the name of the angular module?

Yes it matches the module name of what's just been injected e.g.
https://github.com/antwan1986/angular-code-splitting/blob/master/js/src/pages/about/index.js#L6

thanks!


Hydration error when using nonce on scripts on v1.16.0

What version of Remix are you using?
1.16.0
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
I have a nonce solution that I saw in @kentcdodds his website its source code. This issue thread is related: https://github.com/remix-run/remix/issues/5162
Part of the implemtation on the server is here:
https://github.com/saltagency-io/saltagency.io/blob/master/app/entry.server.tsx#L84
The nonce is the applied to all scripts in root.tsx
Implementations are basically identical and work perfectly on v1.12.0 of remix, however when I tried to upgrade to v1.16.0 of remix, I suddenly get hydration issues, which i suspect are related to the nonce implemtation (I have another project that is on v1.16.0, where I'm currently implementing the same nonce solution and the hydration errors started appearing after that implementation).
Issue can be reproduced with the code on this branch: https://github.com/saltagency-io/saltagency.io/tree/chore/upgrade-remix-version
Expected Behavior
No hydration issues when using a nonce on script tags
Actual Behavior
Hydration issues are logged to the console:

Might not be related to the nonce after all. Remove that code in the other project I mentioned and the errors still persist.

Ok so I installed the apollo client chrome extension around the same time which was causing this issue, probably because it's injecting scripts 🤦

I'm having the same issue with Apollo Client dev tools. None of my other plugins (1Password, etc) cause this issue. I'm brand new to Remix and this caused me some grief after picking my project apart piece by piece.

@kalebheitzman This is a known issue with Remix and React 18.2. The main reason is that Remix hydrates the entire document instead of <div id="root">, so any modifications to <head>, etc. will cause a hydration mismatch.
Apparently React 18.3 will fix this problem, so you can try installing one of the pre-release builds.
Another option is to use a fix like I describe in remix-hydration-fix

Using @kiliman 's solution as a reference I wrote this code.
To make conditional <Scripts /> with useHydrated() is working for me.
import {
  Links,
  Meta,
  Outlet,
  Scripts,
  ScrollRestoration,
} from "@remix-run/react";
import { LinksFunction } from "@remix-run/node";
import { useHydrated } from "remix-utils/use-hydrated";

import styles from "./tailwind.css?url";
export const links: LinksFunction = () => [{ rel: "stylesheet", href: styles }];

export function Layout({ children }: { children: React.ReactNode }) {
  const isHydrated = useHydrated();
  return (
    <html lang="en">
      <head>
        <meta charSet="utf-8" />
        <meta name="viewport" content="width=device-width, initial-scale=1" />
        <Meta />
        <Links />
      </head>
      <body className="bg-base bg-dot-pattern bg-small-dot min-h-screen">
        {children}
        <ScrollRestoration />
        {/* Measure against hydration error */}
        {isHydrated ? <Scripts /> : null}
      </body>
    </html>
  );
}

export default function App() {
  return <Outlet />;
}


Add deploy hooks to ci

Happy to pick setting up a CI process for this.
What are some of the things we'd like?

[x] Run linting
[x] Make some tests? ;P (Jest / Ava?)

Super nice to haves

[ ] Deploy the frontend somewhere

Maybe have all static front ends point to a the same demo backend? Maybe that wont work because we really need to be generating most of that...

[ ] deploy backend preview to heroku?

Feel free to suggest more things and I'll pick it up soon

@mitchellhamilton I think you've got this, feel free to close this issue when you're happy with the setup

This is really only and mostly done. I don't think the "Super nice to haves" are relevant anymore so closing


Notification sound/vibrate

I couldn't seem to find in the documentation how to attach vibration and/or sound to the notification when calling .configure([Object]). Do you achieve this using a different plugin that controls sound/vibration?

@dorukkarinca With next release it will be possible to customize the notification by using the local-notification plugin.


Feature/add metadata to environment filters

This PR introduces a small extension to the project/environmentsByFactSearch queries, allowing both to search on project metadata.
The queries now support the following
  environmentsByFactSearch(input: {
    filterConnective: AND
    filters: [
      {lhsTarget: PROJECT_METADATA, name: "exampleKey", contains: "exampleValue" }
    ]
  }) {
		environments {
      id
      name
    }
  }
}

It introduces a lhsTarget of PROJECT_METADATA and, as with the other target types, allows one to specify a key and value for the search. The above will match any environments with the metadata key/value pair "exampleKey:exampleValue".
This can, further, be combined with the existing filters.

@bomoko - should we just close this if we're looking at re-doing metadata, or is it ok to merge now and modify later?

Closing pending metadata rewrite


Use http://tx.dev.hl7.org.au/ terminology server

There are three versions of terminology servers:

http://tx.dev.hl7.org.au/
http://tx.test.hl7.org.au/ -> http://tx.hl7.org.au/

We need to define in which scenario what server should be used:

Testsure for the current development version of the specification https://build.fhir.org/ig/hl7au/au-fhir-core/ that in the development  https://github.com/hl7au/au-fhir-core

Testsure for the latest release 0.3.0-ballot

Testsure for previous releases like 0.2.2-preview,0.2.1-preview, 0.3.0-ballot once v0.4.0-preview will be release.

FHIR validator for the current development version of the specification https://build.fhir.org/ig/hl7au/au-fhir-core/ that in the development  https://github.com/hl7au/au-fhir-core

FHIR validator for the latest release 0.3.0-ballot

FHIR validator for previous releases like 0.2.2-preview,0.2.1-preview, 0.3.0-ballot once v0.4.0-preview will be release.

Also, now you have to manually choose what profile should be used for the validation, and there is no option to choose a specific version of the. profile. Should we provide a better UX for FHIR validator?

http://tx.hl7.org.au/ will be used only for STU releases, for all dev versions we are going to use http://tx.dev.hl7.org.au/

Changing the terminology server raised problems in a few test groups:
1.6 Observation Pathology Result Tests
1.11 Observation Diagnostic Result Tests

I'll try to fix it tomorrow.


bug: help doesn't print for some commands

It seems like the cli library will accept an argument to the --help flag so the following command doesn't work properly... It should just print the help and ignore other flags and arguments.
$ go run ./internal/cmd/todos/ --help foo/
exit status 3

Created https://github.com/urfave/cli/issues/1809 upstream.


fix: incorrect templateRef

PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] closes #6767
[ ] Requires deployment <snek/rubick/worker>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality

Optional

[ ] I've tested it at </ksm/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

Copilot Summary

🤖 Generated by Copilot at 769abca
Refactored the code for opening the shopping cart modal from the navbar. Moved the logic and configuration from ShoppingCartModalConfig.ts and ShoppingCartButton.vue to Navbar.vue to improve code organization and performance.

🤖 Generated by Copilot at 769abca

ShoppingCartButton
Simpler, no more emit -
Autumn leaves falling

pay 20 usd

😍 Perfect, I’ve sent the payout
💵 $20 @ 4.46 USD/DOT ~ 4.484 $DOT
🧗 16UcV9V6nVvPYdHz98ymUKmNLkzjCEU5sbKJMi7hxYyTHjzR
🔗 0x8afabcc3017c00b6568d8694a79644362c7401c75e239b3170ceaaadf7b96dd7
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues

I trust @roiLeo

I'll earn your trust, somday😄


State data clarification

What would you like to be added:
According to the specification: "The initial data input into a workflow instance must be a valid JSON object. If no input is provided the default data input is the empty object".
The specification should clarify whether the every state's data should be a valid JSON object at all times.
On one hand it seems like this is the intention, considering how the Inject State cannot work unless this is true. It is also impossible to merge event data or subflow results into the state unless this is the case. As it stands, getting the state data into something that's not a valid JSON object is unrecoverable and renders many operations impossible.
On the other hand, the specification explicitly provides examples where JSONPath filters turn the output of a state into something that is not a valid JSON Object. In the first example, the state data is converted from an object into an array.
Why is this needed:
As a reader of the spec, it is unclear to me what types of state data are possible. Allowing anything can allow for more powerful output, but can also render a great deal of functionality inoperable. Because there's no way right now to recover from a non JSON Object state there appears to be a gap in the specification that could use clarification.
If the state data should always be a valid JSON Object that would resolve all problems nicely, at the cost of some small amount of functionality and some incorrect examples in the spec.
If the state data doesn't have to be a valid JSON Object, the specification should be expanded to either:
a) enforce that the only time it can be violated is in the output filter for an end state, or
b) include a way to recover from such a state.

@jensg-st good catch - all workflow data (workflow and state input/output) must be valid JSON. Will go through the examples in spec doc and correct this asap.

@jensg-st good catch - all workflow data (workflow and state input/output) must be valid JSON. Will go through the examples in spec doc and correct this asap.

@jensg-st after looking at the example you mentioned in the post, it does show a valid json structure.
[
   {
      "type" : "iPhone",
      "number" : "0123-4567-8888"
   },
   {
      "type" : "home",
      "number" : "0123-4567-8910"
   }
]

is valid json. Could you elaborate on why you think this is an issue?

@jensg-st after looking at the example you mentioned in the post, it does show a valid json structure.
[
   {
      "type" : "iPhone",
      "number" : "0123-4567-8888"
   },
   {
      "type" : "home",
      "number" : "0123-4567-8910"
   }
]

is valid json. Could you elaborate on why you think this is an issue?

@jensg-st https://github.com/serverlessworkflow/specification/pull/217 . please review when you have time

@jensg-st https://github.com/serverlessworkflow/specification/pull/217 . please review when you have time

Just throwing in my two-cents: you could make that change if you like supporting JSON arrays. But then what's the spec's answer to this?

If the state data doesn't have to be a valid JSON Object, the specification should be expanded to either:
a) enforce that the only time it can be violated is in the output filter for an end state, or
b) include a way to recover from such a state.

Just throwing in my two-cents: you could make that change if you like supporting JSON arrays. But then what's the spec's answer to this?

If the state data doesn't have to be a valid JSON Object, the specification should be expanded to either:
a) enforce that the only time it can be violated is in the output filter for an end state, or
b) include a way to recover from such a state.

@alankm not sure what the issue is.
with workflow data having to be valid json:
a) the answer would be that it cannot be "violated"
b) the answer would be that runtime has to enforce workflow input is valid json, it has to enforce that it keeps being valid json during workflow execution and it has to enforce that workflow output is again valid json
hope this helps

@alankm not sure what the issue is.
with workflow data having to be valid json:
a) the answer would be that it cannot be "violated"
b) the answer would be that runtime has to enforce workflow input is valid json, it has to enforce that it keeps being valid json during workflow execution and it has to enforce that workflow output is again valid json
hope this helps

An array such as in the documentation example is valid JSON, but because it's not a JSON object it is unclear (perhaps impossible) how to perform Inject States on it and/or merge data into it after receiving an event or running a function.
For example, if you have the following state:
{
  "input": "hello"
}

And run a function that returns this json:
{
  "output": "goodbye"
}

It's easy to understand how to merge that function output back into the state. It should become this:
{
  "input": "hello",
  "output": "goodbye"
}

Now consider what happens if your state is a JSON array. You begin with this state:
[
  {
    "input": "hello"
  },
  {
    "input": "aloha"
  }
]

How can I merge my function output into this? Do I append it to the end of the array? Do I merge it into each array element?
"Valid JSON" also includes primitives like true or "hello". How can I merge my function output into that?
These are the questions the spec needs to answer.

An array such as in the documentation example is valid JSON, but because it's not a JSON object it is unclear (perhaps impossible) how to perform Inject States on it and/or merge data into it after receiving an event or running a function.
For example, if you have the following state:
{
  "input": "hello"
}

And run a function that returns this json:
{
  "output": "goodbye"
}

It's easy to understand how to merge that function output back into the state. It should become this:
{
  "input": "hello",
  "output": "goodbye"
}

Now consider what happens if your state is a JSON array. You begin with this state:
[
  {
    "input": "hello"
  },
  {
    "input": "aloha"
  }
]

How can I merge my function output into this? Do I append it to the end of the array? Do I merge it into each array element?
"Valid JSON" also includes primitives like true or "hello". How can I merge my function output into that?
These are the questions the spec needs to answer.

@alankm I believe that we cannot via specification alone prevent possible merging errors from happening. It is often during testing (workflow exec) that users can find out these types of issues.
That being said,  if I'm not mistaken your example can only occur in the case where the workflow data input is an array. Otherwise if the workflow data input is json object, its type would be maintained throughout workflow execution.
So I think we have couple choices,

we leave the workflow data input clause (being a valid json object) as is currently, and update the example you mentioned.
we apply the updates in linked pr

for both cases probably should be worth adding to spec doc that merging errors during workflow execution should be able to be handled via states onErrors definitions. WDYT?

@alankm I believe that we cannot via specification alone prevent possible merging errors from happening. It is often during testing (workflow exec) that users can find out these types of issues.
That being said,  if I'm not mistaken your example can only occur in the case where the workflow data input is an array. Otherwise if the workflow data input is json object, its type would be maintained throughout workflow execution.
So I think we have couple choices,

we leave the workflow data input clause (being a valid json object) as is currently, and update the example you mentioned.
we apply the updates in linked pr

for both cases probably should be worth adding to spec doc that merging errors during workflow execution should be able to be handled via states onErrors definitions. WDYT?

That being said, if I'm not mistaken your example can only occur in the case where the workflow data input is an array. Otherwise if the workflow data input is json object, its type would be maintained throughout workflow execution.

Just to demonstrate that this isn't true using the specification example:
Workflow input:
{
  "firstName": "John",
  "lastName" : "Doe",
  "age"      : 26,
  "address"  : {
    "streetAddress": "Naist street",
    "city"         : "Nara",
    "postalCode"   : "630-0192"
  },
  "phoneNumbers": [
    {
      "type"  : "iPhone",
      "number": "0123-4567-8888"
    },
    {
      "type"  : "home",
      "number": "0123-4567-8910"
    }
  ]
}

Workflow:
id: helloworld
name: "Hello, World!"
description: "Demo #01: A simple hello world."
states:
- name: First
  type: delay
  timeDelay: 1M
  start:
    kind: default
  transition:
    nextState: Second
  stateDataFilter:
    dataOutputPath: "{{ $.phoneNumbers }}"
- name: Second
  type: inject
  data:
    greeting: hello
  end:
    kind: default

The first state in this workflow is effectively identical to the example in the specification, and it transforms the state data from an object to an array. This breaks the second state.
Personally, I think it'd be simpler and cleaner to enforce that it is always an object. Users can nest their arrays and primitives inside.

That being said, if I'm not mistaken your example can only occur in the case where the workflow data input is an array. Otherwise if the workflow data input is json object, its type would be maintained throughout workflow execution.

Just to demonstrate that this isn't true using the specification example:
Workflow input:
{
  "firstName": "John",
  "lastName" : "Doe",
  "age"      : 26,
  "address"  : {
    "streetAddress": "Naist street",
    "city"         : "Nara",
    "postalCode"   : "630-0192"
  },
  "phoneNumbers": [
    {
      "type"  : "iPhone",
      "number": "0123-4567-8888"
    },
    {
      "type"  : "home",
      "number": "0123-4567-8910"
    }
  ]
}

Workflow:
id: helloworld
name: "Hello, World!"
description: "Demo #01: A simple hello world."
states:
- name: First
  type: delay
  timeDelay: 1M
  start:
    kind: default
  transition:
    nextState: Second
  stateDataFilter:
    dataOutputPath: "{{ $.phoneNumbers }}"
- name: Second
  type: inject
  data:
    greeting: hello
  end:
    kind: default

The first state in this workflow is effectively identical to the example in the specification, and it transforms the state data from an object to an array. This breaks the second state.
Personally, I think it'd be simpler and cleaner to enforce that it is always an object. Users can nest their arrays and primitives inside.

@alankm ok, idk what i was thinking before....
Results of the jsonpath expression in dataOutputPath is always going to return an array so enforcing state to return json object is fine but we need to then make sure that users can define the element name for expression results.
For example:
"stateDataFilter": {
     "dataOutputPath":  "{{ $.phoneNumbers[0] }}",
     "as": "iPhoneNumber"
}

@alankm ok, idk what i was thinking before....
Results of the jsonpath expression in dataOutputPath is always going to return an array so enforcing state to return json object is fine but we need to then make sure that users can define the element name for expression results.
For example:
"stateDataFilter": {
     "dataOutputPath":  "{{ $.phoneNumbers[0] }}",
     "as": "iPhoneNumber"
}

One possible solution is to replace JSONPath with jq :)
But there are others, like your suggestion.

One possible solution is to replace JSONPath with jq :)
But there are others, like your suggestion.

@alankm hehe yes, "{iPhoneNumber: .phoneNumbers[0]}" does looks much easier.

@alankm hehe yes, "{iPhoneNumber: .phoneNumbers[0]}" does looks much easier.


Update page number (2->1) for "Complete list of breaking changes" link

The current link "Complete list of breaking changes in the ASP.NET Core 3.0 release" takes a user to the second page

@Ky7m  much appreciated!


Unable to provision node driver cluster using CentOS

Rancher Server Setup

Rancher version: v2.6-head(47c2238)
Installation option (Docker install/Helm Chart): docker

Information about the Cluster

Kubernetes version: v1.23.4-rancher1-1
Cluster Type (Local/Downstream):

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): ec2 node driver

To Reproduce

Provision a ec2 node driver cluster(single node) -> using a node template having CentOS ami. In this case CentOS 8.3 was used. The cluster will stuck into provisioning state with message : Waiting for etcd, controlplane and worker nodes to be registered
Rancher Server Logs :

2022/03/09 12:45:27 [INFO] [node-controller-rancher-machine] Detecting operating system of created instance...
2022/03/09 12:45:27 [INFO] [node-controller-rancher-machine] Waiting for SSH to be available...
2022/03/09 12:46:26 [INFO] [node-controller-rancher-machine] Detecting the provisioner...
2022/03/09 12:46:31 [INFO] [node-controller-rancher-machine] Provisioning with centos...
2022/03/09 12:46:53 [INFO] [node-controller-rancher-machine] The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2022/03/09 12:46:53 [INFO] [node-controller-rancher-machine]
2022/03/09 12:46:53 [INFO] Generating and uploading node config rishabh-centos-docker1
2022/03/09 12:46:53 [ERROR] error syncing 'c-42m8s/m-x9n9p': handler node-controller: Error creating machine: RHEL ssh command error: command: sudo -E yum install -y curl erCentOS Linux 8 - AppStream                      118  B/s |  38  B     00:00    , requeuing     --:-- ETA
2022/03/09 12:48:54 [INFO] Removing node rishabh-centos-docker1

OS Details:

NAME="CentOS Linux"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-8"
CENTOS_MANTISBT_PROJECT_VERSION="8"

cat /etc/centos-release
CentOS Linux release 8.3.2011

Expected Result

Downstream cluster should come into Active state.

Additional Context
https://github.com/rancher/rancher/issues/34615#issuecomment-1058085932

This is likely an issue in rancher-machine.  The error message indicates that the curl install is failing.  The centos package registries have changed recently and likely need to be updated.
There was a similar problem with the docker install scripts.
https://github.com/rancher/install-docker/pull/91

@rishabhmsra , is this affecting both RKE1 and RKE2 provisioning?
Also, could you check if it's happening in 2.6.3?

@snasovich, I validated this on 2.6.3 and on v2.6-head(bab14a3), by provisioning single node, ec2 node driver cluster.
On v2.6-head:

RKE2 cluster(v1.21.10+rke2r1) provisioned successfully.
RKE1 cluster(v1.23.4-rancher1-1), failed to provision with same error.

On 2.6.3:

RKE2 cluster(v1.21.9+rke2r1) provisioned successfully.
RKE1 cluster(v1.22.6-rancher1-1) failed to provision with same error.

I'm adding this test template for the future, this issue should not be tested until the updated install-docker script has been released and rancher-machine has been bumped.
Root cause
The publicly available install-docker script did not include the logic to update the repository mirrors, causing sudo yum install to fail. Additionally, rancher-machine was installing prerequisite packages (such as cURL) before installing docker, and thus before the repository mirrors were updated by the install-docker script.
What was fixed, or what changes have occurred
The install-docker script has been updated to include the repository mirror fix, and rancher-machine will not install docker before prerequisite packages when provisioning centOS nodes.
Areas or cases that should be tested
The creation of nodes using a centOS ami.
What areas could experience regressions?
The creation of other redhat ami's (very unlikely)

Create a new RKE1 node template using a centOS ami, such as ami-056b03dba13a2c9dd
Create a cluster using this template and observe the node(s) go into an active state after being provisioned by rancher-machine

@HarrisonWAffel , with the rancher-machine PR merged, are we waiting on release of updated install-docker script? Is there another issue PR/issue we can link here and move to Blocked as it's really not in Review?

Yes, the install-docker script that is currently in the dev bucket needs to be promoted to the production bucket. Seb has created a work flow to do this automatically upon creation of a tag. I just need to have EIO backup the bucket in case anything goes wrong and they need to restore it. I plan on having this done today so the ticket can move forward

The updated install-docker script has been promoted to the public URL (drone build) and as such this ticket is ready for test
Root cause
The provisioning of centOS machines was broken due to two reasons

The install-docker script did not include the logic for updating repository mirrors. Because centOS is not EOL, the default mirrors no longer work and yum install would fail.

When provisioning a centOS machine, supporting packages were installed before docker. This is normally OK as we do not expect the need to execute any prerequisite commands in order to install packages. However, for centOS we need the mirrors to be updated before any installs can occur.

What was fixed, or what changes have occurred

The install-docker script has since been updated to modify the repository mirrors correctly so that yum install works as expected.

The logic for creating centOS machines has been updated to first install docker and adjust the repository mirrors before installing any other supporting packages.

Areas or cases that should be tested
The creation of centOS machines.
Test steps:

Create a new RKE1 NodeTemplate with the following ami and SSH username
AMI: ami-056b03dba13a2c9dd, username: centos
Use this new NodeTemplate to create a new cluster
Observe the successful creation of the centOS machine, and that the cluster goes into an active state.

What areas could experience regressions?
The provisioning of other redhat AMI's, however this is unlikely due to the implementation.

Validated on rancher v2.6-head(bca5ada).
Steps followed:

Created a RKE1 node template using the ami : ami-056b03dba13a2c9dd and username : centos.
Provisioned a single node, ec2 node driver cluster using k8s version v1.23.6-rancher1-1.
Provisioned a multi-node(1-cp, 1-etcd, 1-w), ec2 node driver cluster using k8s version v1.23.6-rancher1-1.

Result:

The clusters provisioned successfully and came into Active state, hence closing the issue.


Remove workaround for leading spaces in PROG, FUGR, and ENHO

I did some tests and the workaround to persist the number of leading spaces in the XML for PROG & FUGR (dynpro flow) and ENHO (for hook implementation) is not necessary anymore.
References: https://github.com/larshp/abapGit/pull/2597, https://github.com/larshp/abapGit/issues/2643, https://github.com/larshp/abapGit/issues/2655
Removing <SPACES> section from the XML would impact all repos with dynpros or enhancement implementation including the following test repos:
https://github.com/abapGit-tests/CLAS_with_ENHO
https://github.com/abapGit-tests/ENHC
https://github.com/abapGit-tests/ENHO
https://github.com/abapGit-tests/FUGR_maintenance_view
https://github.com/abapGit-tests/FUGR_maintenance_view_variant
https://github.com/abapGit-tests/IARP_IASP_IATU
https://github.com/abapGit-tests/IAXU
https://github.com/abapGit-tests/PROG
https://github.com/abapGit-tests/PROG_dynpro_foreign_key
https://github.com/abapGit-tests/PROG_dynpro_modi
https://github.com/abapGit-tests/PROG_dynpro_resize
https://github.com/abapGit-tests/SCP1_TOBJ
Depending on the repo, there might be many diffs for users (which are easily fixed by staging the updated serialization).
Example of what it would look like: New leading spaces and no more <SPACES> on local side

Do we want to proceed and remove the workaround?

yea, just make it backwards compatible, so if SPACES exists it is used at import, but serializes without SPACES


2.11 release is missing macOS .pkg version

.pkg version is useful for Mac admins deploying RocketChat.
Is it missing by accident or did you stop providing .pkg on purpose?

Hey, this might have been an unintended change, we'll make sure we have this released on the next update. Thanks for letting us know.


Add context and namespace template variables

I have a need to know the region a pod is in at runtime, but curling the GCP metadata is turning out to be flaky (sometimes it's empty), and trying to expose it from a node label doesn't appear to be possible.
I can infer it from the kube context though, so exposing it to the template solves a problem for me. I added the namespace for good measure while I was in there.
🎩 'ed locally against some test CI agents.

I don't think we need this. Here's why:

If your pod needs to know what namespace it is running in, the correct way to get this info is the downward API.
The context name reflects the deployer's kubeconfig file, not necessarily an inherent property of the cluster. Therefore I don't think it is something people should be relying on in their templates.
We already have a mechanism for adding arbitrary bindings required by particular templates: --bindings. We definitely need to document this though. And this gem in general. 😄

Do these options meet your needs @DazWorrall?

Do these options meet your needs @DazWorrall?

The last one in particular, thanks!


Mark translated strings in UI

This change is to explicitly mark translated strings in UI with »STRING«
when 'ui.mark_translated_strings' is set to true in server's configuration.
This enables us to see strings of UI that did go and parts of UI that
did not go through gettext (i.e. are not translatable yet).

@Fryguy As things are, we cannot use super as you suggested, since the fast gettext routines
(for example n_()) call _() at some point. If we use super, then our (i.e. overriden) _() will
be called and as a result, the UI strings will be double-wrapper with our markers (we don't want that).
If we call FastGettext.n_() instead, then _() from fast_gettext will be used.

I am assuming we only want this in development mode; not test or production, right?

@chessbyte We certainly don't need it in test mode (that's being taken care of in current implementation).
Yes, we want this in development, but I'm guessing also in production mode for the sake
of testing of final builds.

My only other concern here is that this would force a hit on the database in an initializer.  I'm pretty sure we might do this in other initializers, but I'm not sure.  For example, I think the code in config/initializers/session_store.rb does that it does to avoid hitting the database via VMDB::Config (Though I think that should be the responsbility of VMDB::Config, but alas)
@jrafanie @matthewd Thoughts here?

My only other concern here is that this would force a hit on the database in an initializer. I'm pretty sure we might do this in other initializers, but I'm not sure. For example, I think the code in config/initializers/session_store.rb does what it does to avoid hitting the database via VMDB::Config (Though I think that should be the responsibility of VMDB::Config, but alas)
@jrafanie @matthewd Thoughts here?

I don't see an initializer, am I missing it?  :see_no_evil:
We can't hit the database in an initializer.  We need to be able to precompile assets and other things without a database connection.
We even have a rake task we run as part of the travis builds to ensure we don't try to connect to the database when loading the Rails environment:  https://github.com/ManageIQ/manageiq/blob/84b82d687ff5d76fed4911473475fb9688784c9c/lib/tasks/test.rake#L11-L22
Oh look, I need to fix that for something else...

config/initializers/fast_gettext.rb?  It's the first file in the diff.

@mzazrivec Since this setting is very dev specific, I think it's ok to just copy the config reading code from the session_store.rb initializer.  Or perhaps move it into a module under lib (maybe lib/vmdb/config/offline.rb or something to be shared?

@Fryguy should be fixed now.

@Fryguy I understand, I fixed the spec as you suggested. Thanks.

Thanks @mzazrivec .  This is pretty cool.


Error compiling

How does one enable support for the '?' operator used since 783a...
rustc --version: rustc 1.12.1 (d4f39402a 2016-10-19)
error: the ? operator is not stable (see issue #31436)
--> src/tokenizer/mod.rs:158:44
|
158 |                             let argument = Number::new(number, token).into_argument(path)?;
|                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
error: aborting due to 52 previous errors
error: Could not compile parallel.

It was made stable with Rust 1.13


fixed installation.md

Related Issue(s)

Fixes #6

Description
Fixed Installation.md file and README.md file also.
Screenshots

Great! Thanks for your contribution.


Hell with performSelector:@selector(play)

What do you want to do by calling this code? In my case I have already defined "play" method in other classes and now your library isn't even compiled

hahah.


Remove odata from output for planner bucket get

Remove odata from the command output for planner bucket get.
This can be achieved by changing the accept header from application/json to application/json;odata.metadata=none. In most methods this is already applied except for the method getBucketById.
https://github.com/pnp/cli-microsoft365/blob/c3fe008322586bc05bab93d0161d7ecbad255ed6/src/m365/planner/commands/bucket/bucket-get.ts#L205-L215

@pnp/cli-for-microsoft-365-maintainers what do you think?

We shouldn't retrieve metadata unless we need it. So looks good to me 👍

Can I work on this?

All yours @huseyinsaatci
Thank you!


Prepare custom rules for ESLint v9

Describe the bug
The upcoming major release of ESLint includes several breaking changes for rule authors: https://eslint.org/blog/2023/09/preparing-custom-rules-eslint-v9/
To Reproduce
n/a
Expected behavior
n/a
Screenshots
n/a
Desktop (please complete the following information):

OS: any
Browser: any
Version: any

Smartphone (please complete the following information):

Device: any
OS: any
Browser: any
Version: any

Additional context
Intro to ESLint's new config format: https://eslint.org/blog/2022/08/new-config-system-part-2/

Merged in https://github.com/microsoft/eslint-plugin-sdl/pull/60