(chores) camel-test-infra-etcd3: updated test image to the latest version

Updated to version 3.5.10
While looking at #12037 I noticed that our container image is outdated. This should bump to the latest version available (tested manually, it should be fine).
Description

Target

[ ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ ] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

This is one the good reason of having dependabot running.. We could improve a lot: the downside is we could end up doing only deps upgrade/testing.

 It would make our life much easier.


International Phone Number with a + Sign

Thank you very much for the excellent library. I am trying to develop a mask for phone numbers. I managed to cover all cases for local (in Australia) phone numbers. However, I am struggling to handle the situation when the user enters an international phone number (starting with a + sign). I think handling validation for different international numbers would be pretty complex.
So, I thought of using a simple, minimal validation (\+)[1-9][0-9 \-\(\)\.]{7,32}:
If the 1st character is +, the user can enter any combination of (numbers, spaces, hyphens, dots, and/or parentheses). How can I code this into a mask function?
export const fMask = (text) => {
	// I NEED HELP WITH THE ALGORITHM FOR THIS CASE
	if (text?.startsWith("+")) {
		return [/(\+|00)[1-9][0-9 \-\(\)\.]{7,32}/]; // wrong
	}

	const onlyDigits = text?.replace(/\D+/g, "");

	// IMPORTANT: THE ORDER OF THE CONDITIONS BELOW IS IMPORTANT!

	// 0123
	// This condition is important to facilitate editing the number after typing it.
	// To fix: If the user starts typing a value that matches a mask, e.g. 02 123. Then, tries to delete what was entered.
	if (onlyDigits?.length < 5) {
		return [/\d/, /\d/, /\d/, /\d/,];
 	}
	// 0444 222 333
	else if (onlyDigits?.startsWith("04")) {
	  return [/0/, /4/, /\d/, /\d/, ' ', /\d/, /\d/, /\d/, ' ', /\d/, /\d/, /\d/, ];
	}
	// 13 12 34, 18 12 34
	else if (onlyDigits?.length <= 6 && (onlyDigits?.startsWith("13") || onlyDigits?.startsWith("18"))) {
		return [/1/, /3|8/, ' ',	/\d/, /\d/, ' ',	/\d/, /\d/, ];
	}
	// 1300 123 567, 1800 123 567
	else if (onlyDigits?.length > 6 && (onlyDigits?.startsWith("13") || onlyDigits?.startsWith("18"))) {
		return [/1/, /3|8/, /0/, /0/,    ' ',    /\d/, /\d/, /\d/, ' ', /\d/, /\d/, /\d/, ];
	}
	// (02) 1234 5678
	else if (onlyDigits?.startsWith("0")) {
	  return ['(', /0/, /\d/, ') ',     /\d/, /\d/, /\d/, /\d/, ' ', /\d/, /\d/, /\d/, /\d/, ];
	}
       // (2) 1234 5678
       else {
	   return ['(', /\d/, ') ',   /\d/, /\d/, /\d/, /\d/, ' ', /\d/, /\d/, /\d/, /\d/, ];
	}
};

I found a solution.
	// I NEED HELP WITH THE ALGORITHM FOR THIS CASE
	if (text?.startsWith("+")) {
		// return [/(\+|00)[1-9][0-9 \-\(\)\.]{7,32}/]; // wrong

               // accepts a "+" sign followed by a maximum of 19 characters, each of which is a digit, a space, a dash, a dot or a parenthesis.
               return ['+', /[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,/[0-9 -().]/,];
	}


Refactor to use Null Object Pattern

We have some duplication that needs to be DRYed out, in the /api/config and the /api/config/:name functions we have largely repeated the code. We could also use the null object pattern so that rather than doing an if valid_node_key? we just call for a GuaranteedEndpoint object which will either be a real endpoint from the database or it will be an object that conforms to the same api.

Now I've gotta go read up on null object pattern.

Check out this video: https://youtu.be/9lv2lBq6x4A


Add an easy way to plot the Solar System

🎯 Goal
In the same way that there are example orbits, it would be nice to be able to plot the whole Solar System in an easy way, with appropriate colors and labels.
💡 Possible solutions

📋  Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes
Submit a pull request and add this in comments - Addresses #<put issue number here>
Ask for a review in comments section of pull request
Celebrate your contribution to this project 🎉

Some thoughts on the API taken from the chat: for instance, you can do
from poliastro.examples import molniya
plot(molniya)

but one cannot do plot(solar_system), since that is made up of several Orbit objects.
On the other hand,
from poliastro.bodies import solar_system

frame = OrbitPlotter()
for planet in solar_system:
    frame.plot(planet)

is not very straightforward to me.
Another option would be
from poliastro.plotting.helpers import plot_solar_system
plot_solar_system()

where plot_solar_system(epoch=None) will plot today's osculating orbits by default.

Is there any problem in taking this approach?
from poliastro.bodies import solar_system

frame = OrbitPlotter()
for planet in solar_system:
    frame.plot(planet)

My problem with the first approach is that solar_system would be a list of Orbit objects, while the rest of the objects in that module are Bodyes. The second looks cleaner to me.

Please Review the Pull Request #303

Closed in #304


Organize Resolvers

Resolvers

Create a library in api-shared
a. Create repositories/services/resolvers for Location

Coordinates and Timezone entities would be created later


Swap the position of the brackets and parentheses.

The character sequence [ ] and then  () is recognized as link text by markdown so that they are eaten.

Hi @kynowoo, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Thanks for your contribution!


Don't show the difference with the moving average if there is none

Before

After

Changes

[x] Ensured that you have rebased your branch with this repo's latest master branch.
[x] Ensured that relevant issues are linked, if this PR resolves any outstanding.
[x] Added a screenshot for all UI changes (you can drag the file into this edit box and it will be uploaded).
[x] Ensured that changes to auto-generated files have not been committed; in particular, *.html, *.csv, *.xml and *.json files.

looks good to me

Thank you for your contribution!
This is moot, #315 removed the hurdle change from the HTML output entirely.


Firebase does not support M1 Flutter/VSCode

fatal
error: module 'firebase_core' not found
@import firebase_core;
pub spec.yaml
dependencies:
flutter:
sdk: flutter
firebase_core: ^1.7.0
main.dart
import 'package:firebase_core/firebase_core.dart';
void main() async {
WidgetsFlutterBinding.ensureInitialized();
await Firebase.initializeApp();
runApp(const MyApp());

Hi @arvobrendon, please file that on this repository instead: https://github.com/FirebaseExtended/flutterfire


Configuration paradigm that is appropriate for embedded library and more container friendly

For HSE 2.0, we need a configuration paradigm that is more appropriate for an embedded library and that meets best practices for containers.

See RFC 0001: https://github.com/hse-project/rfcs/blob/master/rfcs/hse/0001-configuration-refactor.md


Add support for AWS S3 Glacier Deep Archive Storage Class

What problem are you are trying to solve?
AWS recently launched a cheaper storage tier for S3, called "Glacier Deep Archive".
How do you think rclone should be changed to solve that?
Rclone already supports setting different S3 storage classes. It would be useful to add support for the new storage class DEEP_ARCHIVE.

Simply adding the DEEP_ARCHIVE option seems to work. From what I understand, it's just passed as a header.
Restoring files needs to be done from the web interface. The docs already link to it, so I didn't change much there.


V2.0.0 dev tim

This pr enables the DeveloperMode. It will however need to connect to a special version of connect-phonegap (https://github.com/phonegap/connect-phonegap/tree/appID) . I'll be updating the connect-phonegap then phonegap-cli to allow this, but if you want to test it before that happens, ping me and I can show you how to set it up.

Close?

It's no longer applicable.


Expose endpoint to update addresses and hashes

We need an endpoint to update the

core contract address
votes contract address
assets WASM hash

The endpoint should accept PATCH requests.
The endpoint should require basic authentication, with the credentials being injected via an environment variable.
Upon updating the values, we might consider wiping the DB.

added /update-config/  route.
requires envvar CONFIG_SECRET to be set + header Config-Secret


v2: typescript declarations

All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Does your submission pass tests?

hallo again! :smiley_cat:
here's a competing pull request to https://github.com/jscad/OpenJSCAD.org/pull/724, will also close #403.
TODO:

[x] colors
[x] connectors
[x] curves

[x] bezier

[x] geometries

[x] geom2
[x] geom3
[x] path2
[x] poly2
[x] poly3

[x] maths

[x] line2
[x] line3
[x] mat4
[x] plane
[x] utils
[x] vec2
[x] vec3
[x] vec4

[x] measurements
[x] operations

[x] booleans
[x] expansions
[x] extrusions

[x] slice

[x] hulls
[x] transforms

[x] primitives
[x] text
[x] utils

this demonstrates how we might manually write TypeScript declarations, to get a feel for a TypeScript-fluent approach to types in comparison with using jsdoc to generate types.
personally, i prefer this approach, as even though it's more verbose, the resulting type declarations are much cleaner and there's no awkward tension with jsdoc.
anyways, keen for feedback by existing maintainers, to make sure i'm doing the right approach for this project, before i go ahead. :purple_heart:

WOW! That's almost another implementation... sigh. Lots of work.
Is there anyway to generate those declarations initially from the JSDOC?

Is there anyway to generate those declarations initially from the JSDOC?

yeah, that's what #724 does (when you run the typescript script), so i could use that to generate the initial declarations (which have mostly anys as the types), then fill in the anys with actual types.

Lots of work.

while the types might be tedious af, they're much less work than the actual implementation code that y'all have done! :blush:

Hi @ahdinosaur, as @z3dev has said I'm a fan of TypeScript, and I've converted a few projects to TypeScript and created a few declarations. I'm happy to see your enthusiasm, and would like to give some pointers which may save a lot of work. I might not personally have much personal time to create the declarations, but perhaps I can help by showing how I've done it in the past.
Hopefully my method is still relevant, I haven't looked at all the latest compiler options.
My approach is to rename .js files to .ts files and then compile, with the goal of having the compiler's outputted js files being functionally exact as the js source files. That way I know the declarations are compatible. This usually takes some tweaking of the tsconfig.json file. Additionally, I turn on the declarations flag in the tsconfig so I get declarations too. I feel like it's easier than writing them by hand, and hopefully more accurate. This might also seem like a lot of work but I think the exchange ratio of your time to quantity of declaration output is better than the 1:1 of time to write manually.
So, fiddling with the source code in the v2 branch, I've come up with this tsconfig.json:
{
    "compilerOptions": {
        "esModuleInterop": true,
        "outDir": "dist",
        "moduleResolution": "node",
        "module": "CommonJS",
        "declaration": true
    },
    "include": ["src"]
}

Start by renaming the root index.js to index.ts and then compile. You should see a dist/index.d.ts file which should be blank. Then iterate the following steps, compile again, and watch the file grow with declarations.

change module.exports = to export =
change ... require(...) to import ... = require(...)
sometimes you'll need to create a temp variable if the require is inlined:
jsmodule.exports = {
  colors: require('./colors'),

becomes this tsimport colors = require('./colors');
export = {
  colors,

If this seems crazy, maybe it is. I probably get a weird satisfaction out of seeing the compiled code run. This process also catches other bugs in the codebase, and gives you a lot of insight into the internal parts of the code if you find that interesting. YMMV.
Also, in a monorepo like this, you'd add a tsconfig.json almost everywhere you see a package.json, and apply this one package at a time.

thanks @danmarshall :smiley_cat:

* change `module.exports =` to `export =`

* change `... require(...)` to `import ... = require(...)`

oh interesting! i didn't even realize that syntax was possible. should i not use the ES modules syntax?
i was expecting to write declarations such as:
import Vec2 from '../../maths/vec2/type'
import Mat4 from '../../maths/mat4/type'

export interface Geom2 {
  sides: Array<[Vec2, Vec2]>
  transforms: Mat4
}

export default Geom2

or index.d.ts and such as:
export * as colors from './colors'
// ...

okay i changed to using the export = and import ... = require(...), but i'm getting errors with this change:

* sometimes you'll need to create a temp variable if the `require` is inlined:
  js
  ```
  module.exports = {
    colors: require('./colors'),
  ```

  becomes this ts
  ```
  import colors = require('./colors');
  export = {
    colors,
  ```

looking around, seems there's conflicting stories about how to do import / exports, some things (like the DefinitelyTyped README) say to do export = and import ... = require(...) if doing types for a CommonJS module, but then the TypeScript website recommends to use ES modules.
i'm tempted to just do the ES module way, even if it means that consumers will need to use --allowSyntheticDefaultImports or --esModuleInterop compiler options (although i'm not even sure if this would be necessary?). also if #715 happens, i don't want to do this again, as much as i thank CommonJS for enticing me to Node.js for being a simple module system that made sense.

@ahdinosaur Thanks for the supper effort.
I think that you can limit the TS declarations to just the modeling package for now. Hopefully, there will be some early adopters to test out the new declarations and provide some feedback.

@ahdinosaur - I'm not sure that you can do it the ES module way, since the code seems to be CommonJs. Have you tested it with a TypeScript project, and does it bundle and run? If it works that would be cool, since I also like the syntax better. I would be hesitant to require users to use any particular compiler options since this may not always be compatible when adding in other libraries and may pose a conflict. If #715 happens that would be a major breaking change anyways.

Have you tested it with a TypeScript project, and does it bundle and run

@danmarshall okay, did a test now, using a fresh directory, npm init -y, tsc --init, and pkl (not sure how to npm link to a lerna module, but this works okay).
seems to work great, the default TypeScript config has esModuleInterop: true, which works when using ES modules or the import ... = require(...) way. if esModuleInterop is set to false, you have to use the import ... = require(...) way, but that works just as well. so TypeScript doesn't seem to mind that the declarations are in ES modules while the code is in CommonJS.
this is exciting to see my type declarations show up in my vim to help me autocomplete and show type errors. :relaxed:

@ahdinosaur just a quick question... it seems that the .ts files are replicating the documentation for the functions. is this required?

@ahdinosaur just a quick question... it seems that the .ts files are replicating the documentation for the functions. is this required?

i think those would be the .d.ts files i auto-generated with tsc from the current .js files, i'm currently manually going through them, fixing them, giving the functions actual types, and removing anything extraneous such as the duplicate documentation. you can track my progress in the OP, i'm pottering away like the rain here in Wellington. :teddy_bear:

Wellington must be pouring rain....
@ahdinosaur Are you hitting any issues?

@ahdinosaur Are you hitting any issues?

@z3dev, no sorry, got a wee bit distracted by the US election and other things. :smiley_cat:
will try another push this week, keen to get this over the line. hoping to get things "good enough" that i can start using the types, even if it's not perfect.

@z3dev, one question: for the functions that accept geometries as an argument, do you think it makes more sense to say that argument can be any geometry type (geom2, geom3, poly2, poly3, path2), or do you think it makes more sense to be specific about which geometry types are actually supported by the implementation? said another way, do you expect to eventually support all geometry types in these functions, or are some functions specific to certain geometry types? one random example is measureArea.

@z3dev, one question: for the functions that accept geometries as an argument, do you think it makes more sense to say that argument can be any geometry type (geom2, geom3, poly2, poly3, path2), or do you think it makes more sense to be specific about which geometry types are actually supported by the implementation? said another way, do you expect to eventually support all geometry types in these functions, or are some functions specific to certain geometry types? one random example is measureArea.

Correct. All geometries should be supported as arguments to the various operations. There are only a few exceptions now, and should be fixed if failures occur. I think measureArea() behaves fine. Probably offset() will fail if passed a geom3.

hi @z3dev et al, okay this is ready for an initial review. :smiley_cat:
i've also published with gitpkg, so can be installed to test with:
npm install 'ahdinosaur/OpenJSCAD.org#jscad-modeling-v2.0.0-alpha.6-gitpkg'

i only just tested the most basic cases, which seem to work fine:
import { maths } from '@jscad/modeling'

const { vec2 } = maths

console.log(vec2.fromValues(1, 2))

import vec2 from '@jscad/modeling/src/maths/vec2'

console.log(vec2.fromValues(1, 2))

import vec2 = require('@jscad/modeling/src/maths/vec2')

console.log(vec2.fromValues(1, 2))

later will try and port my own project code to use the new types, if that works then i'm happy. :sunny: :seedling:

hi @z3dev et al, okay this is ready for an initial review.

Super. I added @danmarshall as a reviewer as he will probably use those TS definitions immediately.
I’ll also review.

i rebased the commits, to rename the messages. i was originally planning to squash all into one commit, but as far as i understand y'all would prefer individual commits?

published the latest using gitpkg, can be installed with:
npm install 'ahdinosaur/OpenJSCAD.org#jscad-modeling-v2.0.0-alpha.7-gitpkg'

i rebased the commits, to rename the messages. i was originally planning to squash all into one commit, but as far as i understand y'all would prefer individual commits?

The final merge will be a squashed merge, so no need to squash yourself. The comments on the commits are very useful during reviews. 👍

@danmarshall can you review? thoughts?
i'm ready to merge this but wanted another review / opinion.

@danmarshall can you review? thoughts?
i'm ready to merge this but wanted another review / opinion.

started porting over a project's code to use the types, most of it works really well, some of it needs some iron-ing out. :smiley_cat:
the lower-level math and geometry types seems good, will need to think about the higher-level operations that can apply to arbitrary geometries, seems there's mismatches sometimes trying to pass around generic geometries, some functions get confused when they expect specific geometries.
still keen to merge this pull request, if the overall approach is sound, and i'll be fixing things up as i (and hopefully others) put this to more use.
:sunflower:

Sorry, I haven't had much time to look at this... Hoping someone else in the community can test it out.

Hi @ahdinosaur - I may finally have some time this weekend to try these out :)
Looks like these are part of<EMAIL_ADDRESS>but when I install I get<EMAIL_ADDRESS>@z3dev will you be publishing<EMAIL_ADDRESS>soon?

@danmarshall excellent!
I took a look at NPM. I have no idea but here’s what NPM says about the versions.
Version               Downloads (Last 7 Days)   Published
2.0.0-alpha.10   29                                         alpha
2.0.0-alpha.4     30                                         latest
For some reason, NPM is stuck at alpha.4. Did I mention that NPM sucks?
If you use the ‘alpha’ tag then it will install the latest version; alpha.10.
I’ll have to research this further...

Just wanted to say I've been using the modeling types and haven't come across anything wrong yet. I'd also like to get types done for the regl-renderer, which should be less complex since regl is typed. Right now I'm pulling the types directly from regl. I may work on that next week if I have time.

Just wanted to say I've been using the modeling types and haven't come across anything wrong yet. I'd also like to get types done for the regl-renderer, which should be less complex since regl is typed. Right now I'm pulling the types directly from regl. I may work on that next week if I have time.

That would be cool. Also, there’s not much documentation for the real-renderer yet so feel free to complete some of the documentation for those functions that need to be exposed.


Run as non-root, OpenShift support

Problem Statement:
As a best practice, it's not advised to run containers as the root user: https://www.armosec.io/blog/kubernetes-security-best-practices/#limit-application-privileges
This provides a point of privilege escalation that can impact the wider cluster.  As a solution to this, platforms such as OpenShift run containers as a random UID/GID unless specified.
When a container is built with the filesystem being owned to the root user, such as /opt/cribl then only the root user can read/write to those locations, so in order to have the container deploy to a Ready state you must run the container as root.
Solution Option(s):

Ideally the containers have a specific user created with a UID/GID higher than 1000.  This requires a rebuild of the Cribl container.  Then in the podSecurityContext, you would specify the runAsUser and runAsGroup parameters to target that user.
If the containers MUST be run as root, then provide the RoleBinding to allow the containers to run as Privileged containers on OpenShift:

---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: crible-priv
  namespace: cribl-stream
subjects:
  - kind: ServiceAccount
    name: ls-wg-pci-logstream-workergroup
    namespace: cribl-stream
  - kind: ServiceAccount
    name: ls-wg-system-metrics-logstream-workergroup
    namespace: cribl-stream
  - kind: ServiceAccount
    name: default
    namespace: cribl-stream
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: 'system:openshift:scc:privileged'

I don't see the Cribl container source in the GitHub org, otherwise I'd try to provide a patch to this end.  Is there any requirement for running as root that is not apparent to me?  Thoughts on these options?

@kenmoini this PR might be of interest to you: https://github.com/criblio/helm-charts/pull/166 In fact, it was created specifically for dealing with a customer deploying the Leader on OpenShift.
The second item is that setting the CRIBL_VOLUME_DIR environment variable to a PVC that is writable by the UID, this removes any need for writing to /opt/cribl
NB: There's no reason for running any Cribl container as privileged.

@bdalpe Ok that is excellent and good to know - I've figured out a way to deploy to OpenShift with a namespaced user who is only admin of the cribl-stream namespace, without any additional RBAC.  Namely just need to disable creating the RBAC and set the CRIBL_VOLUME_DIR env var:
helm install ls-leader cribl/logstream-leader \
  --set "config.groups={pcilogs,system-metrics}" \
  --set config.token="ABCDEF01-1234-5678-ABCD-ABCDEF012345" \
  --set config.adminPassword="adminPasswordHere" \
  --set config.license="<license key>" \ # or delete for demo
  -n cribl-stream

helm install ls-wg-pci cribl/logstream-workergroup \
  --set config.host="ls-leader-internal" \
  --set config.tag="pcilogs" \
  --set config.token="ABCDEF01-1234-5678-ABCD-ABCDEF012345" \
  --set rbac.create="false" \
  --set env.CRIBL_VOLUME_DIR=/tmp/cribl \
  --set service.annotations."metallb\.universe\.tf/address-pool=lab-pool" \
  -n cribl-stream

helm install ls-wg-system-metrics cribl/logstream-workergroup \
  --set config.host="ls-leader-internal" \
  --set config.tag="system-metrics" \
  --set config.token="ABCDEF01-1234-5678-ABCD-ABCDEF012345" \
  --set rbac.create="false" \
  --set env.CRIBL_VOLUME_DIR=/tmp/cribl \
  --set service.annotations."metallb\.universe\.tf/address-pool=lab-pool" \
  -n cribl-stream

So since it works with a random UID/GID like how OpenShift deploys by default, I think the best solution would just to be that we add some additional documentation around the value modifications needed to deploy to OpenShift - whatcha think?

As of OpenShift 4.14 it seems pod security admission is in an enforced mode. This causes all pods to define their scc. Which permissions should the SCC have to run cribl as non-root? We also allowed the namespace to run from the GUID range defined in the pod, and allowed access to our storage class, however the pods still fail to start.

@wa77z do you have any logs or events from OpenShift showing the reason for the pod failing to start?

@wa77z do you have any logs or events from OpenShift showing the reason for the pod failing to start?

Error creating: pods "cribl-edge-" is forbidden: unable to validate against any security context constraint


The latest version C# mappings

Could you add C# mapping for the latest Hoops Exchange version (HOOPS Exchange 2023 SP2)?

Hello,
This project is moving forward and will now be an official packages delivered alongside the official HOOPS Exchange packages on the developer zone. It will be officially supported starting the version 2023 SP2 U1 planned to be released on 09/12/23.
Regarding this repo, it will be freeze once we feel confident enough with our official release process. Estimated date is end of Q4 2023.
Is that plan enough for you, or do you still need SP2?
Cheers

That plan sounds good.  We've observed some issues with the marshalling due to changes in the generated wrapper.  Still need to debug that and see what exactly is going on and will let you know what we find.

From: Christian Charles @.>
Sent: Tuesday, September 5, 2023 1:02 PM
To: techsoft3d/ExchangeSharp @.>
Cc: Subscribed @.***>
Subject: Re: [techsoft3d/ExchangeSharp] The latest version C# mappings (Issue #15)
This email is not from Hexagon’s Office 365 instance. Please be careful while clicking links, opening attachments, or replying to this email.
Hello,
This project is moving forward and will now be an official packages delivered alongside the official HOOPS Exchange packages on the developer zone. It will be officially supported starting the version 2023 SP2 U1 planned to be released on 09/12/23.
Regarding this repo, it will be freeze once we feel confident enough with our official release process. Estimated date is end of Q4 2023.
Is that plan enough for you, or do you still need SP2?
Cheers
—
Reply to this email directly, view it on GitHubhttps://github.com/techsoft3d/ExchangeSharp/issues/15#issuecomment-1706986538, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AT7JMPMKL6ZBXZJRELPDJDLXY5LLHANCNFSM6AAAAAA3MSBRYI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Ok, keep us posted. We will fix issues as fast as possible to have this project in its best conditions ASAP.

Do you have any samples for the released C# mapping ?

Hi, In the C# zip package, we provided 8 samples.
Most of them are similar to the C ones from the HOOPS Exchange package.

Where can we find this library\project?
Is it here https://developer.techsoft3d.com/hoops/exchange/downloads/latest/ inside HOOPS_Exchange_Publish_2023_SP2_U1_Win_VS2019.zip?

The dedicated C# package is inside Related Technologies at the same adress.

got it. Thank you!


Is there a way to get privacy in my homebrewer?

Hi,
I see that in my pdf I can click and other people can see my original Homebrewer. Is there a way to have a privacy or secret profile, to avoid this? Or I must delete all my job, after I finish it?
I want to sell my job on DMSGuilde, so it's a problem for me

What exactly do you mean by "I see that in my pdf I can click and other people can see my original Homebrewer."? What do you click? What's the link that opens up?

If i click in the bottom of the page there is a link that open my Homebrew in the naturalcritic syte. I don't know the reason because I don't put any types of links in document. I find a solution saving 2 or more times or deleting my original work

Closing for now because of no further response from the user, and the issue does not have enough information to fix.
Feel free to reopen this issue if this is still a problem for you and you can provide more information, @marcuswallace1991, @Marcobertini6


Using managed windows-2019 agents for E2E tests.

Using managed windows-2019 agents for E2E tests.
Removed -Force from Remove-AzADApplication call.

Pipeline runs that were able to successfully use windows-2019 agents:

Standalone: https://iotcat.visualstudio.com/Industrial-IoT-E2E-Testing/_build/results?buildId=5029&view=results
Orchestrated: https://iotcat.visualstudio.com/Industrial-IoT-E2E-Testing/_build/results?buildId=5030&view=results


Not focusing to conversation fragment from push notification.

Hi,
Android app doesn't focus to related fragment of conversation when I click to New Message Push notification.
Best regards.

I cannot reproduce. Please provide more information.
I just fixed an issue when the notification was missing altogether: https://github.com/tinode/tindroid/commit/40aeb2c7be7a0d8fc622fab12af684a9934c29d8. But that seems to be different from the issue you described.

Any update on this?

With help of @maksfreetimer I found a bug which may have caused this issue. It's been fixed on the server side.

A possible fix has been released in https://github.com/tinode/chat/releases/tag/v0.15.13-rc2
If the problem remains, please open another issue and provide more details. Thanks.


bug(select): For multiple select, previously opened dropdown doesnt allow the click on another select or other components unless it has been closed by clicking elsewhere on the page

Use StackBlitz to reproduce your issue:

Components: https://stackblitz.com/edit/angular-q4dhku?file=src%2Fapp%2Fselect-custom-trigger-example.html
Harnesses: https://angular-q4dhku.stackblitz.io

Steps to reproduce:

Click on the arrow of one of the select( do not click elsewhere)
Click on the other select arrow

Expected Behavior
What behavior were you expecting to see?
The previously expanded select should collapse and the newly clicked select should expand
Actual Behavior
What behavior did you actually see?
Previosuly expanded select does not collapse. Need to click on second select twice to collapse the previously expanded select and to expand the second select
Environment

Angular: 9
CDK/Material:
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows

We didn't do this before due to how the CDK overlays are set up, but we should be able to do it now with the OverlayOutsideClickDispatcher. I suspect that it'll cause a lot of test failures though.


Can't add tags to glossary terms when I am navigating with a selected Domain

On the top-right panel, preselect a Domain XYZ other than All Domains
Go to the glossary view
Click on edit glossary term
Click on tags -> no tags are coming back from the search API

If instead, we perform this same operation from All Domains, we get all the tags back. This can be replicated in the sandbox
We need to double-check the search API call since tags cannot be assigned to specific domains, at least from the UI

@karanh37 this is possibly because of passing domain as filter to all the entities. We need to escape tags out of this call and make it a generic call.


speed up evaluation with r-trees to find overlapping detections

What changes are proposed in this pull request?
The current evaluation methods generate IOUs for all pairs of detections, which is quadratic in both time and space. It's taking hours even though most detections don't overlap at all. This PR uses a spatial index (implemented in the rtree package) to only compute IOUs for detections that overlap. It takes the run time from hours to minutes on images with tens of thousands of detections.
I ran a simple test with 10,000 detections. This change improved the run time from 945 seconds to 9.5 seconds.
It works for 2D and 3D bounding boxes, masked detections, and polygons. Keypoints and polylines are not changed at this time, except to update the return value of compute_ious() from an array to a dictionary, to match the others.
This PR also fixes a bug in utils3d._Box, which was using the wrong rotation to compute the box's vertices. This also allows the cuboid IOU tests to pass.
Note that providing an eval_key to save the results to the database is unreasonably slow, likely because of the overhead of saving the entire sample. That problem is unrelated to the detection matching issues solved here, but it should be addressed in another PR. For instance, in a test with 1,000 detections, the runtime with eval_key=None goes from 9.3 seconds to 0.8 seconds. However, with an eval_key, it is about 65 seconds in both cases.
How is this patch tested? If it is not, please explain why.
evaluation_tests.py confirms that the new results match the old ones. The CuboidTests class had to be updated because now the computed ious do not include results for non-overlapping detections.
Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[ ] No. You can skip the rest of this section.
[X] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

It does speed up evaluations, so users with larger numbers of objects in their samples may be interested.
What areas of FiftyOne does this PR affect?

[ ] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[X] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

Summary by CodeRabbit

New Features

Enhanced handling of Intersection over Union (IoU) calculations for improved performance and clarity.
Introduced new functions for structured extraction of bounding box coordinates.
Added support for spatial indexing with the integration of the "rtree" library.

Bug Fixes

Improved validation logic for IoU calculations in unit tests.

Tests

Added new test class and method to enhance coverage for box functionality in 3D utilities.

Chores

Updated dependencies to include "rtree" for enhanced spatial operations.

Thanks for your contribution @kemaleren ! Someone will review your proposal.
Re: saving results, we have been looking into that separately. Stay tuned.


Phonegap build iOS GCM Registered but not receiving notification

Hi,
I've been using the plugin with GCM on Android with no major problems so far, but I can't get it to work for iOS.
I'm using Phonegap Build on my project.
When using the plugin to work with the native APNS servers, it seems to work OK, but now that I need to use Android GCM Service, I can't get it to work.
config.xml:
<gap:plugin name="phonegap-plugin-push" source="npm" version="1.5.3"/>

Also tried something like this (as seen here: https://github.com/phonegap/phonegap-plugin-push/issues/440#issuecomment-170683762 )
<gap:plugin name="phonegap-plugin-push" source="npm">
        <param name="SENDER_ID" value="265882065897"/>
        <param name="GOOGLE_APP_ID" value="1:265882065897:ios:fbcd21ebe894ee64"/>
    </gap:plugin>

Plugin init:
pushNotification = PushNotification.init({
        ios: {
            senderID: GOOGLE_PROJECT_ID,
            gcmSandbox: true,
            alert: "true",
            badge: "true",
            sound: "false"
        }
    });

I've successfully uploaded .p12 file to google platform, with respective iOS App Bundle ID, activated cloud messaging and downloaded plist file (just in case, as I don't do local builds).
On registering I successfully get GCM ID in the following format:
lQipKUX0CyU:APA91bFFafKjEz2Ju2acoDJGz___A3_ZMWDLt4VYi8MQXkUXt3j653LDo8woWIpW4WCbprGBdgNcxdHV3B7U-yrrB4bcd4OqBr1A5SNvI-0Mi4KDosFxKoN1qciXqllXYNN8T6jvnKTe

Sending a payload like this to google service:
{
"to": "REGID",
    "data": {
      "message": "This is a Message!"
}

also tried APNS way like this:
{
"to": "REGID",
"aps":{"alert":"Hello from APNs Tester.","badge":"1"}
}

Both ways result in a successful post request to Google GCM Service, but no notification is received on iOS phone.
This is the code I have on both Android and iOS:
pushNotification.on('registration', function(data) {
        GCM = data.registrationId;
        console.log("SUPER GCM_ID = " + GCM);
    });

    pushNotification.on('notification', function(data) {
        console.log('CHEGOU NOTIFICAÇAO');

        // Foreground
        if (data.additionalData.foreground) {
            buildPush(data);
            //navigator.notification.alert(data.message, null, messages.pushMessage);
        }
    });

    pushNotification.on('error', function(e) {
        console.log('PUSH PLUGIN ERROR: ' + e.message);
    });

So, it successfully fires 'registration' event, but do not fire 'notification' or 'error' events.
Am I missing something?
I've tried before with APNS service and it works ok (of course without senderID and Sandbox options).
As I use my own database and code to send push to Android devices, it would be great to reuse that code, although I don't know if google converts GCM payload to APNS or if I need to send them in a separate way.
Thanks in advance.

@ahlidap Yeah, when you push to an iOS device using GCM it just forwards your payload along to APNS. However, what I have noticed is that it is picky about the format you send.
Try:
{
"to": "REGID",
    "notification": {
      "title": "This is a Title!",
      "body": "This is a Message!"
   }
}

which is a pain because that payload won't trigger your Android code as the OS will intercept it. You'd have to swap `notification

@macdonst Thanks for your help.
It's working now.
In fact, I missed this details from Google GCM Documentation:
https://developers.google.com/cloud-messaging/ios/client#http_post_request)
sorry.
Time to code!
Thanks again

Thank you both, I had the exact same problem. The format is the culprit.
Just some additional information here that could help others.
1, Somehow, I am using production instead of development when I am developing on my local ipad. So I am using gcmSandbox:false, this is confirmed when I use the OS X 'APN Tester Free' where I used prod key and chose 'ad-hoc/production'
2,  I didn't touch the plist file at all, I only have the SENDER_ID in my cordova config.xml. Basically, I ignored GOOGLE_APP_ID all together.
3, setting "priority":"high", and "content_available": true at root level helps. Ref.

I cannot get it work. I use firebase console to sending push notification. Created app in firebase, uploaded p12 and got GoogleService-Info.plist. And paste it instead of another plist in cordova-plugin-fcm-config folder(I use this lib: https://github.com/stetro/cordova-plugin-fcm-config). My app's bundle id in developer.apple.com and id in config.xml match. I start phonegap server and see that no errors. And I've tried to send push notification in firebase console, but in my iphone I don't receive notifications. What am I doing wrong? Thnx

A mi me pasó lo mismo con phonegap-plugin-push y no pude solucionarlo.
para iOS desinstalé el plugin ¨phonegap-plugin-push¨ e instale el plugin ¨cordova-plugin-fcm¨ https://github.com/fechanique/cordova-plugin-fcm, y ya funcionaron las notificaciones para iOS.


Add min_dims rule for image file uploads

Aditional image file upload rule requested here:
https://forum.codeigniter.com/thread-79421.html
Description
Add min_dims rule to image file uploads (complement to the max_dims rule already present in the framework)
Already tested and working.
João Ribeiro

I'm glad you were able to test this locally and it works, but we need regression tests in place to make sure nothing breaks in the future. You can see the tests over here as references.

This will also need to be pointed at 4.2 branch (and possibly rebased) because develop is currently locked to style changes.

@sys4soft Could you write test code for this?
https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/pull_request.md#unit-testing

@sys4soft Could you write test code for this? https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/pull_request.md#unit-testing

Sorry, kenjis, but I've never done PHPUnit tests in my life :(
Don't know how to do it and I'm really busy at work right now.

Hi, and thanks for your contribution! As this PR has been standing for a couple of months now and no effort has been seen to add the necessary unit testing to confirm the patch, we can conclude that there's no more interest in moving this forward.
We love to see and appreciate all contributions coming in from the community. However, please make it an effort to make it easy for maintainers to verify your code (that you want to be part of the framework core) through unit testing. You cannot (and we cannot, either) expect to write only source code and delegate the testing part to others. Unfortunately, that's not how OSS works.
Closing this for now. We'd still love to see you around contributing to the framework. Feel free to open a new PR once all necessary testing is in place. Thanks!


[BUG] starting an inline conversation from custom step

Nutgram version
nutgram/laravel : ^1.3
PHP version
8.2
Framework
Laravel 10.x
Cache driver
Filesystem
OS
Windows
Dev environment
No response
Describe the bug
got an exception when starting an inline conversation from custom step
Error: Typed property SergiX44\Nutgram\Conversations\Conversation::$bot must not be accessed before initialization in D:\projects\telegram-bot\vendor\nutgram\nutgram\src\Conversations\Inlin
eMenu.php:262

To Reproduce
//telegram.php

$bot->onText('Subscription', [SubscriptionInline::class, 'secondStep']);

Expected behavior
run the second step
Screenshots
No response
Additional context
No response

It's not a Nutgram bug.
Conversations must start from the first step as written in the documentation.
You have 3 ways to solve this 'issue'.

Assign the $bot parameter to the $this->bot property. (It's a workaround. Not recommended.)

//telegram.php
$bot->onText('Subscription', [SubscriptionInline::class, 'secondStep']);

//SubscriptionInline.php
//[...]
public function secondStep(Nutgram $bot)
{
    $this->bot = $bot;	// <== this
    $bot->sendMessage('Second step');
    $this->next('thirdStep');
}
//[...]

Extend your SubscriptionInline class and override the $step property.

//telegram.php
$bot->onText('Subscription', SecondStepInSubscriptionInline::class);

//SecondStepInSubscriptionInline.php
class SecondStepInSubscriptionInlineextends Conversation
{
    protected ?string $step = 'secondStep';
}

Create a new conversation.


23439 - bug fixing

*Issue:23439 *https://github.com/bcgov/entity/issues/23439
*Description of changes:23439 *

disable change buttons on address and directors when business is in freeze

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://business-dashboard-dev--pr-51-a5zxzok5.web.app


feat(Auth): add WalletConnect Provider to authenticate()

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

feature

What is the current behavior? (You can also link to an open issue here)

upgrade the Moralis.Web3.authenticate()

What is the new behavior (if this is a feature change)?

add WalletConnect Provider to authenticate()

Other Information:

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

feature

What is the current behavior? (You can also link to an open issue here)

upgrade the Moralis.Web3.authenticate()

What is the new behavior (if this is a feature change)?

add WalletConnect Provider to authenticate()

Other Information:

Thanks for your contribution :)
I had to make some other changes as well to make it work with the enable function.
It has all been implemented in the latest version.
Closing this PR as it is resolved now,


Revert mbo link removal

Questions
Answers

Description?
revert mbo link removal

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?

How to test?
Update from 1.7.8 to PS 8.0 or 8.1, the MBO module should be present before the upgrade As long as it was not uninstalled before the upgrade it should still be present after the upgrade

Possible impacts?
Please indicate what parts of the software we need to check to make sure everything is alright.

@matthieu-rolland I think it's a valid fix, we shouldn't delete the module's tabs, and MBO is now working fine with upgrades from what I've heard.

@kpodemski I think we should also add the link in the sql for PS 8.1 (in case someone would have updated to 8.0.0 and lost the link), what do you think ?

@sallemiines I reproduced the behavior, but it seems to be normal in my case: I checked "disable non native modules", and MBO is not a native module.
If you enable it in the module manager, then it works.
What do you think ?

We just need to make sure if the module is enabled again that the links works again

@sallemiines I reproduced the behavior, but it seems to be normal: non native modules are disabled during upgrade (by default), and MBO is not a native module.
If you enable it in the module manager, then it works.
What do you think ?

Hello @matthieu-rolland
Thanx for your feedback !
I recheck the PR

Tested with an upgrade from <IP_ADDRESS> to 8.1.0 => OK

IF The MBO module is enabled before the upgrade

After the upgrade action the MBO module is disabled =>  the click  action on Module's tab link => the page is not found ,

I enable the module = >  the click  action on Module's tab link is OK the page is displayed , but the menu marketPlace is isplayed twice also the  tabs market place and Modules in the spotlight ( in the mage parketplace)  are displayed twice

You can check the screen recorder
https://github.com/PrestaShop/autoupgrade/assets/31663369/67de47c7-a813-4e4d-a2c9-ace85c5f40f3

The rollback action is breaks with this error

if I apply the upgrade action and the MBO module is disabled , the upgrade process is ok ,
After the Rollback > The  modules inside the module catalog  page are not exists

https://github.com/PrestaShop/autoupgrade/assets/31663369/fbce08ab-66e8-436a-bcdc-d343519521bc
Please check and feedback !
Thank you !


Cannot install .NET Core 2.0 on Amazon Linux AMI

I am trying to update from .NET Core 2.0 Preview 2 Final to 2.0 Final Release on the Amazon EC2 instance due to some dependency issue.
When I run install command sudo yum install dotnet-sdk-2.0.0 it produces following error.
Error: Package: dotnet-runtime-2.0.0-2.0.0-1.x86_64 (packages-microsoft-com-prod)
           Requires: openssl-libs

And, when I try to install openssl-libs using package manager with command yum install openssl-libs, it says No package openssl-libs available.
I've checked package repository and didn't found any package with name openssl-libs there. However, openssl is installed already in the machine, I confirmed that by running openssl version command. The version is 1.0.1k-fips 8 Jan 2015.
Please suggest how to resolve this dependency.

I managed to install .NET Core 2.0 using the source code as instructed here.
I didn't find any complexity in that way. It hardly took 10 minutes to get everything setup.

I was almost desperate.
I tries many ways, none of them can work for me.
Afterwards, I download the .NET Core 2.0 runtime directly with following link:

https://download.microsoft.com/download/5/F/0/5F0362BD-7D0A-4A9D-9BF9-022C6B15B04D/dotnet-runtime-2.0.0-linux-x64.tar.gz

And, use the old fashion way like installing .net core 1.1 with commands:
sudo mkdir -p /opt/dotnet && sudo tar zxf dotnet-runtime-2.0.0-linux-x64.tar.gz -C /opt/dotnet
sudo ln -s /opt/dotnet/dotnet /usr/local/bin

It worked. Very simple like you used to do.

Does not work with Amazon Linux when following these instructions.
[ec2-user@ip-xx-xx-xx-xx ~]$ sudo yum install dotnet-sdk-2.0.0
Loaded plugins: priorities, update-motd, upgrade-helper
Resolving Dependencies
--> Running transaction check
---> Package dotnet-sdk-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: dotnet-runtime-2.0.0 >= 2.0.0 for package: dotnet-sdk-2.0.0-2.0.0-1.x86_64
--> Processing Dependency: aspnetcore-store-2.0.0 >= 2.0.0 for package: dotnet-sdk-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package aspnetcore-store-2.0.0.x86_64 0:2.0.0-1 will be installed
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Processing Dependency: dotnet-hostfxr-2.0.0 for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package dotnet-hostfxr-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: dotnet-host >= 2.0.0 for package: dotnet-hostfxr-2.0.0-2.0.0-1.x86_64
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package dotnet-host.x86_64 0:2.0.0-1 will be installed
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Finished Dependency Resolution
Error: Package: dotnet-runtime-2.0.0-2.0.0-1.x86_64 (packages-microsoft-com-prod)
           Requires: openssl-libs
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

If you already have openssl you can try to run yum with  --skip-broken (as the message suggests)
All what dotnet needs is to find dynamic libraries from openssl. (and libcurl)

BTW AMI Linux is NOT one of the supported and test platforms. There should be no surprise that there are some bumps. This is one reason for publishing the tar file so you do not need to fight package dependencies.

If you want to use AWS, drop it in Docker and use ECS.

Like hchungi said, I just did:
Download .NET Core 2.0.0 runtime libraries (always check if URL is right, maybe it can be changed):
wget https://download.microsoft.com/download/5/F/0/5F0362BD-7D0A-4A9D-9BF9-022C6B15B04D/dotnet-runtime-2.0.0-linux-x64.tar.gz
Create folder to .NET Core and extract your tar.gz:
mkdir -p $HOME/dotnet && tar zxf dotnet-runtime-2.0.0-linux-x64.tar.gz -C $HOME/dotnet
Finally, export dotnet to globally variable:
export PATH=$PATH:$HOME/dotnet
Just it :)

This is exactly how I did this around a month ago.
Thank you very much to confirm the solution.
On 06-Oct-2017 21:31, "Bruno Paschoali Regis"<EMAIL_ADDRESS>wrote:

Like hchungi said, I just did:
Download .NET Core 2.0.0 runtime libraries (always check if URL is right,
maybe it can be changed):
wget https://download.microsoft.com/download/5/F/0/5F0362BD-
7D0A-4A9D-9BF9-022C6B15B04D/dotnet-runtime-2.0.0-linux-x64.tar.gz
Create folder to .NET Core and extract your tar.gz:
mkdir -p $HOME/dotnet && tar zxf dotnet-runtime-2.0.0-linux-x64.tar.gz -C
$HOME/dotnet
Finally, export dotnet to globally variable:
export PATH=$PATH:$HOME/dotnet
Just it :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/930#issuecomment-334797494, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABpaVdhf_5I669PIpGH-5LqGA8H83mSCks5spk7JgaJpZM4PK47F
.

Sounds like people have found a good solution. I'm going to close this out now.

But I wish if I could install this simply using package manager on AWS AMI.
On 06-Oct-2017 21:55, "Peter Marcu"<EMAIL_ADDRESS>wrote:

Sounds like people have found a good solution. I'm going to close this out
now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/930#issuecomment-334803730, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABpaVZb1hBFEZ3GcMuot2i26cZiFmhQiks5splSFgaJpZM4PK47F
.

Any chance you could try a distribution other than Amazon Linux? The .NET Core project publishes packages for several distributions (such as CentOS, Debian, Ubuntu) and several other distributions are now starting to carry .NET Core too (such as Arch, CentOS, Fedora, RHEL). I dont know if we have a way to contribute packages to Amazon Linux directly.

Yes, I've been told the Centos one works: https://www.microsoft.com/net/core#linuxcentos

I would assume that someone needs to work with AWS to get .NET Core into their package feed.

Yes, I thought about that and researched on that too.
But, many resources suggests that AWS AMI perofoms best in AWS
infrastructures.
On 06-Oct-2017 22:05, "Omair Majid"<EMAIL_ADDRESS>wrote:

Any chance you could try a distribution other than Amazon Linux? The .NET
Core project publishes packages for several distributions (such as CentOS,
Debian, Ubuntu) and several other distributions are now starting to carry
.NET Core too (such as Arch, CentOS, Fedora, RHEL). I dont know if we have
a way to contribute packages to Amazon Linux directly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/930#issuecomment-334806056, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABpaVbvaBiUBObEdMh3psUzFHrdJJFd2ks5spla3gaJpZM4PK47F
.

I use the Aliyun ECS,The OS version is Centos 6.8. I also met this problem.The Information like this:
[root@iZwz9bh8rvZ ~]# sudo yum install dotnet-sdk-2.0.0
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
Resolving Dependencies
--> Running transaction check
---> Package dotnet-sdk-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: dotnet-runtime-2.0.0 >= 2.0.0 for package: dotnet-sdk-2.0.0-2.0.0-1.x86_64
--> Processing Dependency: aspnetcore-store-2.0.0 >= 2.0.0 for package: dotnet-sdk-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package aspnetcore-store-2.0.0.x86_64 0:2.0.0-1 will be installed
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Processing Dependency: dotnet-hostfxr-2.0.0 for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package dotnet-hostfxr-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: dotnet-host >= 2.0.0 for package: dotnet-hostfxr-2.0.0-2.0.0-1.x86_64
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package dotnet-host.x86_64 0:2.0.0-1 will be installed
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Finished Dependency Resolution
Error: Package: dotnet-runtime-2.0.0-2.0.0-1.x86_64 (packages-microsoft-com-prod)
Requires: openssl-libs
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Aliyun ECS? Whatever, did you read the comments? We suggested some solutions. Sure that of them will help you.

Is there a SRPM for the dotnet-runtime package? Or is there a spec file in the repo somewhere? I couldn't find one.

Is there a SRPM for the dotnet-runtime package? Or is there a spec file in the repo somewhere?

We use fpm to produce RPMs (and debs) instead of using rpmbuild. There are no SPRMs or spec files because of that.
The configuration for -runtime and -host RPMs is available here: https://github.com/dotnet/core-setup/tree/master/src/pkg/packaging/rpm
Here is the source that reads that config files above to build command line for fpm: https://github.com/dotnet/core-setup/blob/master/tools-local/tasks/BuildFPMToolPreReqs.cs

The solution no longer works. Please re-open.

I am a client programmer.
I do not like to install any dependency myself on linux.
some problems are too difficulty to solve.
see golang.

Unfortunately I didn't make this working. Using hortonworks sandbox withCentOS.
Error as already mentioned above:

Error: Package: dotnet-runtime-2.0.6-2.0.6-1.x86_64 (packages-microsoft-com-prod                                                   )
Requires: openssl-libs
Error: Package: dotnet-runtime-deps-2.1.0-rc1-2.1.0_rc1-1.x86_64 (packages-micro                                                   soft-com-prod)

Installing Net Core 2.1 on Amazon Linux still seems to be an issue :(

What base OS do you use and what .Net package? Did you check that everything works using tar distro? I'm trying to figure out if this is pure packaging issue or if there are really missing dependencies.

I did sudo rpm -Uvh https://packages.microsoft.com/config/rhel/7/packages-microsoft-prod.rpm and yum update and yum install dotnet-sdk-2.1
Output is below:
amazon-linux-ami: Resolving Dependencies
    amazon-linux-ami: --> Running transaction check
    amazon-linux-ami: ---> Package dotnet-sdk-2.1.x86_64 0:2.1.301-1 will be installed
    amazon-linux-ami: --> Processing Dependency: dotnet-runtime-2.1 >= 2.1.1 for package: dotnet-sdk-2.1-2.1.301-1.x86_64
    amazon-linux-ami: --> Processing Dependency: aspnetcore-runtime-2.1 >= 2.1.1 for package: dotnet-sdk-2.1-2.1.301-1.x86_64
    amazon-linux-ami: --> Running transaction check
    amazon-linux-ami: ---> Package aspnetcore-runtime-2.1.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: ---> Package dotnet-runtime-2.1.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: --> Processing Dependency: dotnet-hostfxr-2.1 >= 2.1.2 for package: dotnet-runtime-2.1-2.1.2-1.x86_64
    amazon-linux-ami: --> Processing Dependency: dotnet-runtime-deps-2.1 >= 2.1.2 for package: dotnet-runtime-2.1-2.1.2-1.x86_64
    amazon-linux-ami: --> Running transaction check
    amazon-linux-ami: ---> Package dotnet-hostfxr-2.1.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: --> Processing Dependency: dotnet-host >= 2.1.2 for package: dotnet-hostfxr-2.1-2.1.2-1.x86_64
    amazon-linux-ami: ---> Package dotnet-runtime-2.1.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: --> Processing Dependency: dotnet-runtime-deps-2.1 >= 2.1.2 for package: dotnet-runtime-2.1-2.1.2-1.x86_64
    amazon-linux-ami: --> Running transaction check
    amazon-linux-ami: ---> Package dotnet-host.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: ---> Package dotnet-runtime-2.1.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: --> Processing Dependency: dotnet-runtime-deps-2.1 >= 2.1.2 for package: dotnet-runtime-2.1-2.1.2-1.x86_64
    amazon-linux-ami: --> Finished Dependency Resolution
    amazon-linux-ami:  You could try using --skip-broken to work around the problem
    amazon-linux-ami: Error: Package: dotnet-runtime-2.1-2.1.2-1.x86_64 (packages-microsoft-com-prod)
    amazon-linux-ami:            Requires: dotnet-runtime-deps-2.1 >= 2.1.2
    amazon-linux-ami:            Available: dotnet-runtime-deps-2.1-2.1.0-1.x86_64 (packages-microsoft-com-prod)
    amazon-linux-ami:                dotnet-runtime-deps-2.1 = 2.1.0-1
    amazon-linux-ami:            Available: dotnet-runtime-deps-2.1-2.1.1-1.x86_64 (packages-microsoft-com-prod)
    amazon-linux-ami:                dotnet-runtime-deps-2.1 = 2.1.1-1
    amazon-linux-ami:  You could try running: rpm -Va --nofiles --nodigest

cc: @tmds. seems like  it cannot find dotnet-runtime-deps-2.1 -2.1.2

@wfurt, @jchannon is installing from Microsoft feed. Are those packages missing?

just followed the instructions here https://www.microsoft.com/net/download/linux-package-manager/centos/sdk-current

Looks like the updated runtime-deps and sdk didn't make the upload. Checking into this now.

Alrighty, sorry about that. Give it another whirl now.

A bit better but now says runtime needs openssl-libs.
I added yum install openssl-libs but it says "No package openssl-libs
available."
On 11 July 2018 at 18:21, Lee Coward<EMAIL_ADDRESS>wrote:

Alrighty, sorry about that. Give it another whirl now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/930#issuecomment-404247132, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGaphtEXiz4S0ulpYRPsNe1S-pIqkIcks5uFjQhgaJpZM4PK47F
.

That goes back to original issue. AMI Linux names packages different than RedHat. Now, assuming you have correct openssl 1.0.x installed you can try following trick:
openssl-libs-ami.spec.txt
Download attached spec file.
rpmbuild --bb  openssl-libs-ami.spec.txt
That should produce empty openssl-libs in  /root/rpmbuild/RPMS/
(use find if not there as the location may wary)
rpm -i openssl-libs-1.0.0-0.x86_64.rpm
and try the install again.
Good luck. AMI linux is not tested so .net may or may not work properly.
The instructions should help you to at least try.

The @wfurt solution worked for me, just run sudo yum install rpm-build to get started.

Perfect also in my case. The folder was different, as stated :
sudo yum install rpm-build
wget https://github.com/dotnet/core/files/2186067/openssl-libs-ami.spec.txt
rpmbuild --bb openssl-libs-ami.spec.txt
sudo rpm -i /root/rpmbuild/RPMS/x86_64/openssl-libs-1.0.0-0.x86_64.rpm
sudo yum install -y powershell

Provides: openssl-libs = 1.0.0-0 openssl-libs(x86-64) = 1.0.0-0
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Checking for unpackaged file(s): /usr/lib/rpm/check-files /usr/src/rpm/BUILDROOT/openssl-libs-1.0.0-0.x86_64
Wrote: /usr/src/rpm/RPMS/x86_64/openssl-libs-1.0.0-0.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.13DnAm
``` for whatever reason this chose today to start hanging forever during deployments.  I don't see an actual %clean step in the rpm spec.

Folks who are trying to install azure powershell and have ended up here can use @juancrl mentioned solution, it surely works !
sudo yum install rpm-build
wget https://github.com/dotnet/core/files/2186067/openssl-libs-ami.spec.txt
rpmbuild --bb openssl-libs-ami.spec.txt
sudo rpm -i /root/rpmbuild/RPMS/x86_64/openssl-libs-1.0.0-0.x86_64.rpm
sudo yum install -y powershell

For me the path of created openssl-libs was different. So I had to find it first (as suggested by wfurt)
wget https://github.com/dotnet/core/files/2186067/openssl-libs-ami.spec.txt
rpmbuild --bb openssl-libs-ami.spec.txt
sudo find / -iname RPMS  # output: /usr/src/rpm/RPMS
sudo rpm -i /usr/src/rpm/RPMS/x86_64/openssl-libs-1.0.0-0.x86_64.rpm
sudo yum install -y powershell


EXC_BAD_ACCESS on User computed properties on second login

Not sure if this is the correct forum for the following issue.  If not, please indicate the best forum to submit this issue.
I have a Swift framework (AppUtils.framework) that contains all my Parse objects.  I have linked this framework to my app (MyApp).
I have extended the PFUser and added specific properties.
On starting the app for the first time, I login with a known user.  Everything works fine.
I stop the app and then restart it.  I am not prompted to login again but when accessing a computed property in my StartupController to see if the user has successfully completed their app setup, I get a EXC_BAD_ACCESS error.
This error occurs both in the simulator and Iphone.
Sample code is as follows.  I have pared down the code for brevity:
in AppUtils framework:
public class AppUser : PFUser {     public var appSetupComplete : Bool {         get { return self["appSetupComplete"] as? Bool ?? false }         set { self["appSetupComplete"] = newValue }     } }
In MyApp:
`class StartUpController: NSObject, PFLogInViewControllerDelegate, PFSignUpViewControllerDelegate {
var window : UIWindow!
init(window : UIWindow ) {
    super.init()
    self.window = window

    if let appUser = AppUser.currentUser() {
        let appSetupComplete = appUser.appSetupComplete   <<<< EXC_BAD_ACCESS
    }

}
`
It appears that the AppUser is somehow getting corrupted upon restart of the app.
Let me know if additional information is needed.

After submitting this issue, I came across issue #963.  This appears to be the same issue.
Reading through I double checked my registerSubclass calls in my AppDelegate.  I noticed that these were called after Parse was initialized.  I then moved to before Parse was initialized and my issue no longer exists.
Will follow #963 going forward.


No SFP-stats on UDM Pro SFP ports

Unifi Poller Version:
unifi-poller, version 2.1.3 (branch: v2.1.3 (ba12697), revision: 884)
  build user:       travis
  build date:       2021-04-18T10:36:26Z
  go version:       go1.16.3
  platform:         linux/amd64

I have:

UDM Pro

Port 10 (WAN2) SFP+ connected to internet provider
Port 11 (LAN) SFP+ connected to US6XG150

US6XG150

Port 6 SFP+ uplink to UDM Pro

Expected behavior:

Receive sfp_current, sfp_rxpower, sfp_temperature, sfp_txpower, sfp_voltage for all uws_ports with has_sfp = true

Actual behavior

Getting all sfp data for the US6XG150 SFP ports
Not getting any sfp data for the UDM Pro SFP ports

can you check if the behavior is the same as the one I described in #384 ?

@Thelvaen i also have the issue as in #384 - this one might be related as in unifi/unpoller not reporting properly for SFP in general. This issue though is specifically about temperature, voltage, current and power not being reported.

Ahhhh yes, sorry, didn't read properly ^^
Just being curious as I know some SFP/SFP+ don't report on those values, did you try with the ones that are reporting properly on your US6XG150 ?

I have two SFP optics in the UDM Pro:

In port 11 a UF-MM-10G connecting to US6XG150
In port 10 a 10G optic of my ISP

The US6XG150 also uses the UF-MM-10G and is tracked fine by unpoller.
As such it must be that either UDM Pro or unpoller do not report SFP stats in general. There is no port on UDM Pro where has_sfp = true


Upload Existing Code Files

Can someone add the option to upload existing code files or code?

This is a cool idea.  It's close to being able to work as the HTML window on the bottom is editable, it's just not wired up to the state store properly.  I'll spend some more time thinking about this one.

That would be amazing! I can absolutely get behind that idea

@vale46n1 @MyndPhreak that sounds like a bigger undertaking.  For multi-file / project use cases I suggest:

I've been using Cursor and it's awesome.  You can open a chat window and ask questions about multiple files in the codebase.  Very cool.
I haven't checked this out, but OpenDevin looks really cool.

Love how there's so much OpenSource hotness happening in this space.  I'm humbled to have created something exciting for folks and can't wait to make it better!

I would suggest to start to think to integrate such kind of functionality:
•	JSON Input Interface: feature that allows users to directly input JSON into a specially designed interface. This would enable the LLM or AGENT to dynamically tailor React and HTML code to effectively manage the JSON content. Additionally, the interface should offer options for specifying headers to transmit payloads or security tokens, facilitating the testing of the code’s functionality in practical scenarios.
•	Customization Based on Language and Framework: I guess that tool like this to be effective must be customized according to the programming language and framework in use. For example, adopting React with Next.js entails a particular folder structure that the generated code must reflect. The LLM and agents should perform an initial analysis of the project’s structure to identify connections and then adjust the underlying code of pages to fit the overall concept.
•	Automatic Dependency Management: We need to automatically identifying and updating related pages within a React project when one page is modified. This process should ensure that changes in one part of the application are reflected across related components, thereby maintaining consistency and enhancing development efficiency.

Once again I would underline that from my point of view this kind of tool shall be tailored not just to the programming language but also to the specific frameworks being used, such as React with Next.js, Gatsby, or Vite for the frontend and FastAPI for the backend. This approach ensures the creation of a cohesive and fully functional system.
Looking on current market and trends, maybe React with Next.js could be a good target. FASTApi as backend.

@vanpelt This seems doing something similar of what I was considering https://github.com/plandex-ai/plandex


Add coreui.io - open source admin template based on vue.js

After I merget it I noticed that all other projects use github links, is that a rule @kazupon ?

Yes!

The link provided should be the link of the github repository, not the demo. If you consider your project finished, and it does not need any contributions, consider the apps/website category.

it should be required github repo link.


Failure image generated despite no change of code and their diff incorrectly rendered

Hi, I'd like to report wired behavior.
I tried to take snapshot of root view for a simple ViewController.
After recorded its reference image successfully, turned recordMode into false and found the test failed.
Without any code nor visual changes to the ViewController, diff is rendered as below.

reference
failure
diff

iOSSnapshotTestCase 6.1.0
iPhone 8 Plus 12.4 Simulator
Swift 4.2
XCode Version 10.3 (10G8)

With iPhone Xs simulator, failure image slightly changes from its reference image (of course with no change in code nor storyboard) and diff is incorrectly rendered too.

reference
failure
diff

The ViewController

loads its view from storyboard using https://github.com/tarunon/Instantiate (a wrapper for storyboard.instantiateInitialViewController())
completes initialization for its view within viewDidLoad

I couldn't make sense of it and hope this to be resolved.

I am struggling with the same issue here. After recorded the reference images successfully, turned recordMode into false. Without any code in the project, ran the tests and found the test failed. The images are shown as following:

The tests may all pass on some devices. On some other devices, the tests may fail or some of them fail while others succeed. For example, tests all pass on Simulator iPhone 8 with iOS 12.4 but all fail on Simulator iPhone 8 with iOS 11.4.
Any help would be much appreciated.

There should not have been any changes that would cause a regression like this. Are you saying these snapshots worked correctly on a previous version of iOSSnapshotTestCase and 6.1.0?
If you are upgrading to a new iOS SDK version these sort of blips are typically expected because of the major changes that Apple typically makes to UIKit.

Same issue here. I am using :

iOSSnapshotTestCase version 6.1.0 (did not upgrade from an earlier version)
Xcode 11.1 (11A1027)
macOS Catalina 10.15
Simulator with iOS 13.1 (tried on all device types)
fileNameOptions = [.screenSize]

As soon as I turn off recordMode, the test fails.

Failure diff:

Test fail message:
failed - Snapshot comparison failed: Optional(Error Domain=FBSnapshotTestControllerErrorDomain Code=3 "Images different sizes" UserInfo={NSLocalizedFailureReason=referenceImage:{1242, 2688}, image:{414, 896}, FBDiffedImageKey=<UIImage:0x600002aa7f00 anonymous {1242, 2688}>, FBReferenceImageKey=<UIImage:0x600002aa74e0 anonymous {1242, 2688}>, FBCapturedImageKey=<UIImage:0x600002a83b10 anonymous {414, 896}>, NSLocalizedDescription=Images different sizes})

Through testing different cases I noticed that if fileNameOptions does not include .screenScale, the test will always fail.
For example: fileNameOptions = [.screenScale, .screenSize] will lead test to succeed.

@zeksa90 that is a different bug that is potentially fixed by https://github.com/uber/ios-snapshot-test-case/pull/100 and is in the v6.2.0 release.
You can see with your difference image that it recorded at 3x but then compared at 1x. It is a shortcoming of UIKit that if an image does not end with the appropriate @ suffix it assumes it to be 1x. The PR that fixed it makes iOSSnapshotTestCase use the actual pixel size rather than the logical device size.

Great @reidmain. Somehow I missed 6.2.0 release. I have tested v6.2.0 and bug from #100 is fixed.
Thanks

@imaizume does v6.2.0 fix your issue?

Hi guys. I also caught this error, the error is most often seen on the screens with gradients , but visible differences I not see ...
environment
OSX 10.15.4
XCode 11.4
iOSSnapshotTestCase', '~> 6.2.0'
all simulators
Result after run test
reference

** failure**

*diff

Any help would be helpful , thanks


Investigate using rockcraft

Enhancement Proposal
We most likely need to use rockcraft instead of docker.

Fixed with #35.


docs: fix minor issues

Mark all omitempty fields in the API as optional, so they won't appear as required in the documentation
Fix broken links to structs now in the barman-cloud API
Make Database resource appear in the API resource types

Closes #5904

Related to the optional values, probably we should also add default values in the API

/test d=push tl=4

/ok-to-merge no code changes, only doc


The audio player is being displayed twice

Hi,
Thank you for your great project. It really helps.
I was indeed able to record audio from the Streamlit app running on my remote server. However, when I stop the recording, two players for the same audio are displayed. Please check the attached image. Is this the default behavior?

My environment

Python 3.8.9
streamlit==1.29.0
streamlit-audiorec==0.1.3
code

import streamlit as st
from st_audiorec import st_audiorec
wav_audio_data = st_audiorec()

if wav_audio_data is not None:
    st.audio(wav_audio_data, format='audio/wav')

The if condition and line after it is not necessary.
import streamlit as st from st_audiorec import st_audiorec wav_audio_data = st_audiorec()


update(repositories.yaml): add falco-actions

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind documentation

/kind feature

/kind stable

/kind incubating

/kind sandbox

/kind deprecated

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area governance

/area proposals

/area utils

What this PR does / why we need it:
See #412
Which issue(s) this PR fixes:

Fixes #412
Special notes for your reviewer:
/hold we have first to transfer the repo, then merge https://github.com/falcosecurity/test-infra/pull/1695

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/unhold

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Soul Campfire - Recipe doesn't exist in 1.12.2 version (for me)

Hello,
So I enjoy modding my MC worlds and doing various things. There's this MC world that I've had for over 10 years and I've solidified on the 1.12.2 version (because I loooooooove Thaumcraft!). I have the Apotheosis mod and it's one of my favorites... however... I just attempted to migrate the affixes from a legendary wooden sword to the brand new diamond sword I just made. I have all the materials to do so... but my only problem is that the recipe for the soul campfire doesn't exist (not even in creative mode or the Not Enough Items JEI). I've tried to see if anyone else has had this issue and one report did show up on the GitHub, but had no answer. I have the tome of scrapping but no soul campfire. Also, one thing I've noticed is that whenever I look at the "abilities" of said weapon there aren't any shown. I think they only show for Apotheosis bosses (which I've only ever encountered one in my lifetime).
I would appreciate an explanation of why it's not possible to fix any of these or if I'm doing something wrong. Please and thank you!
Signed,
Halo

Hi - 1.12.2 is reallllllly old, and a ton has changed since then.  The content you are trying to access simply didn't exist back then.
Here's the 1.12 CF Page for reference: https://discord.com/channels/613010559532531713/613011704456019968/774845475937320960

Thank you for the quick response! I would imagine you're probably busy trying to update the 1.18 version, but the 1.12.x versions are still very popular (and in my opinion the 1.12.x versions have the best selection of mods out there). Would you be able to implement at least this one tiny little feature in the 1.12.2 version sometime in the future?

1.12 is (and has been) declared end-of-life.  It will not be receiving any further updates for any reason.

Well, that's unfortunate to hear. Great job on the mod tho! Really like it overall!


[stable/prometheus-operator] Unable to upgrade on k8 v1.18.3

Describe the bug
Failure to upgrade chart.
Version of Helm and Kubernetes:
shadycuz-> helm version
version.BuildInfo{Version:"v3.0.0", GitCommit:"e29ce2a54e96cd02ccfce88bee4f58bb6e2a28b6", GitTreeState:"clean", GoVersion:"go1.13.4"}

shadycuz-> kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:52:00Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:43:34Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
prometheus-operator-8.16.1
What happened:
First time:
shadycuz-> helm upgrade -i --namespace monitoring -f values.yml monitoring stable/prometheus-operator
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"

Error: UPGRADE FAILED: cannot patch "monitoring-grafana" with kind Deployment: Deployment.apps "monitoring-grafana" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/instance":"monitoring", "app.kubernetes.io/name":"grafana"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

about 5 mins later:
shadycuz-> helm upgrade -i --namespace monitoring -f values.yml monitoring stable/prometheus-operator
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
Error: UPGRADE FAILED: rendered manifests contain a new resource that already exists. Unable to continue with update: existing resource conflict: kind: Role, namespace: monitoring, name: monitoring-prometheus-oper-alertmanager

What you expected to happen:
To have a successful upgrade.
How to reproduce it (as minimally and precisely as possible):
Try to upgrade from prometheus-operator-8.16.1  to latest chart using helm 3.0 on k8 1.8.3
Anything else we need to know:
About 80 mins before this I had updated my cluster to k8  to 1.18.3 so everything seemed to upgrade but grafana.
shadycuz-> kubectl get pods -n monitoring
NAME                                                     READY   STATUS    RESTARTS   AGE
alertmanager-monitoring-prometheus-oper-alertmanager-0   2/2     Running   0          13m
monitoring-grafana-57699d9c7c-pslt8                      2/2     Running   0          74m
monitoring-kube-state-metrics-558bccc948-cxvd8           1/1     Running   0          13m
monitoring-prometheus-node-exporter-75pdq                1/1     Running   0          12m
monitoring-prometheus-node-exporter-8nnkl                1/1     Running   0          13m
monitoring-prometheus-node-exporter-pmcjn                1/1     Running   0          12m
monitoring-prometheus-oper-operator-66546c554d-rjvxx     2/2     Running   0          13m
prometheus-monitoring-prometheus-oper-prometheus-0       3/3     Running   1          12m

After deleting all the resources that came up with the "already exist error".  It crashed with this again:
Error: UPGRADE FAILED: cannot patch "monitoring-grafana" with kind Deployment: Deployment.apps "monitoring-grafana" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/instance":"monitoring", "app.kubernetes.io/name":"grafana"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

It's now saying all the resources already exist so I'm now back at the start.

Delete the grafana deployment, then deleting all the duplicate resources, allows the update to happen.


PHP 8.3 | Tokenizer/PHP: add support for typed OO constants

Description
PHP 8.3 introduced typed OO constants, where the type is between the const keyword and the constant name.
All type variations are supported, including nullable types, union types, intersection types, with the exception of callable, void and never. self and static types are only allowed in Enum constants.
This PR adds support for typed OO constants in the Tokenizer layer of PHPCS.
The following issues had to be fixed to support typed constants:

Consistently tokenizing the constant name as T_STRING, even if the name mirrors a reserved keyword, like foreach or a special keyword, like self or true.
Tokenizing a ? at the start of a constant type declaration as T_NULLABLE.
Tokenizing a | and & operators within a constant type declaration as T_TYPE_UNION and T_TYPE_INTERSECTION respectively.

Each and every part of the above has been covered by extensive tests.
Includes additional tests safeguarding that the array keyword when used in a type declaration for a constant is tokenized as T_STRING.
Ref: https://wiki.php.net/rfc/typed_class_constants
Suggested changelog entry

Added: Tokenizer support for PHP 8.3 typed class constants.

Related issues/external references
Related to #106
Types of changes

[x] New feature (non-breaking change which adds functionality)

Thanks for these adjustments!
I'm having this error Class constants must be uppercase; expected INT but found int using this branch as a dependency.
I know it's not included in the description of this PR, but any idea how can we address this case?

Thanks for these adjustments! I'm having this error Class constants must be uppercase; expected INT but found int using this branch as a dependency. I know it's not included in the description of this PR, but any idea how can we address this case?

@calinblaga You don't need to. This PR is a prerequisite for fixing the sniff and those changes have already been lined up and will be pulled once this PR has been merged. Also see #106.

Unless there are objections/someone leaves a comments on this PR, I will merge this tomorrow.


Fixes integration tests

retest this please

retest this please

retest this please

Putting on hold until Cypress fixes a bug I found.

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please


Introduction section template complete.

Removed unnecessary css and nav-bar that came with the app template. Re-located the MLH logo, and went for a grey / white style. Small introduction text added and sections further separated by div margins.
Update: added self-rotating carousel after home header with template body.
Update: added typewriter effect on the header title.

One thing I notice is that the header is not centered on my screen, and when i shrink my screen, it get cut off. See photos:
We should also probs have arrows on each side of the carousel so that they can easily be cycled through, instead of having to click the buttons at the bottom. Maybe slow down the typewriter animation too because it completes so fast that my page hasn't really loaded and I can't see it. These are relatively minor styling things tho and I really like how it looks overall!
Now that we have to have separate pages, maybe you can create an issue for the about page, copy and paste this over, and tidy it up?
Also, might be a good idea to have a separate stylesheet for each page now that we have multiple for readability.

Thanks! I'll add an issue to separate the sections into pages, and will add stylesheets for each one. I'll fix the styling issues and push them here.

I made an issue already for the 'about me section' so you don't have to worry about that. Since the json and the images have been merged, I would recommend adding our profile pics to the home page

I made an issue already for the 'about me section' so you don't have to worry about that. Since the json and the images have been merged, I would recommend adding our profile pics to the home page

On it!


Please upload to bintray

Currently the only version available is 1.2, can you please upload the latest version to bintray?

I distribute vplugin using plugins.gradle.org now ... which mirrors to
jcenter automagically.  Take a look at
https://plugins.gradle.org/plugin/com.github.nwillc.vplugin for usage
instructions.
On Wed, Jun 3, 2015 at 9:18 PM, Hani Suleiman<EMAIL_ADDRESS>wrote:

Currently the only version available is 1.2, can you please upload the
latest version to bintray?
—
Reply to this email directly or view it on GitHub
https://github.com/nwillc/vplugin/issues/1.

Maybe it doesn't jcenter mirror ... you'll need to add the repo mentioned
in the usage note.
On Thu, Jun 4, 2015 at 10:06 AM<EMAIL_ADDRESS>wrote:

I distribute vplugin using plugins.gradle.org now ... which mirrors to
jcenter automagically.  Take a look at
https://plugins.gradle.org/plugin/com.github.nwillc.vplugin for usage
instructions.
On Wed, Jun 3, 2015 at 9:18 PM, Hani Suleiman<EMAIL_ADDRESS>wrote:

Currently the only version available is 1.2, can you please upload the
latest version to bintray?
—
Reply to this email directly or view it on GitHub
https://github.com/nwillc/vplugin/issues/1.

Looks like plugins.gradle.com isn't updating the mavan-metadata.xml
correctly for some reason.  The plugin is there but you need to get the
version from the plugins.gradle.com to access it.  I'm working with them to
figure out the issue but you can get the plugin even now.
On Thu, Jun 4, 2015 at 10:08 AM<EMAIL_ADDRESS>wrote:

Maybe it doesn't jcenter mirror ... you'll need to add the repo mentioned
in the usage note.
On Thu, Jun 4, 2015 at 10:06 AM<EMAIL_ADDRESS>wrote:

I distribute vplugin using plugins.gradle.org now ... which mirrors to
jcenter automagically.  Take a look at
https://plugins.gradle.org/plugin/com.github.nwillc.vplugin for usage
instructions.
On Wed, Jun 3, 2015 at 9:18 PM, Hani Suleiman<EMAIL_ADDRESS>wrote:

Currently the only version available is 1.2, can you please upload the
latest version to bintray?
—
Reply to this email directly or view it on GitHub
https://github.com/nwillc/vplugin/issues/1.


Debug console input has a large gap on the left

That text is as far left as I can go

@octref Pointed out, if you have Vim installed

Relative line number change?

Dup of https://github.com/Microsoft/vscode/issues/12879


Merge examples-for-event-communication to master

Proposed changes
Examples how to use the event communication component.
Related Issues

 Add examples for CodeMonkeys.EventCommunication #76

Should we really provide examples in the same package with the implementation?
We aren't doing this for any other package.


Feature/set istio host explicitly

Testing a change to the chart values that may be preventing the domain from being set properly at deploy time.
The Jira chart differs from others in that the istio hosts (which are used to configure the virtual service address) are configured dynamically.
I believe that may be rendered or interpreted at package time with default values, so that despite setting the ZARF_VAR_DOMAIN variable at deploy time, the virtual service still comes up with the default address.
If that is in fact what is happening, setting the value explicitly may circumvent the issue.

/test all

Doh, good catch!
I don't think there's any harm in leaving the explicit host setting in, though I agree it probably wasn't the actual issue here lol

Closing in favor of branch with signed commits


add merbridge which uses eBPF to speed up Your Service Messh

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you added your SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

/cc @kebe7jun

project https://github.com/merbridge/merbridge
Istio blog: https://istio.io/latest/blog/2022/merbridge/
solo.io: https://www.youtube.com/watch?v=r2wgInmsqsU with Episode 22: Accelerate your service mesh with eBPF and Merbridge

Build failed because of:
Empty twitter for Mondoo (member): https://twitter.com/mondoolabs
Empty twitter for Mail.Ru Cloud Solutions (member): https://twitter.com/mailru
Empty twitter for Mail.Ru Cloud Containers: https://twitter.com/mailru
Empty twitter for China Telecom (member): https://twitter.com/chinatelecom1
Empty twitter for Scalyr: https://twitter.com/scalyr
Empty twitter for Spotinst Functions: https://twitter.com/spot_hq
No cached entry, and Sangfor CNAD has issues with twitter: https://twitter.com/SangforUSA, Request failed with status code 404
No cached entry, and Sangfor EDS has issues with twitter: https://twitter.com/SangforUSA, Request failed with status code 404
Empty twitter for Karmada: https://twitter.com/karmada_io
Empty twitter for Mondoo: https://twitter.com/MondooLabs
Merbridge either has no crunchbase entry or it is invalid

The failed reason is not related to merbridge.

Merbridge either has no crunchbase entry or it is invalid

Updated.

LGTM

@caniszczyk do you have time to take a look?

LGTM

fix greyed logo
add repo_url


automake-cmake-make

Automated CMake and Make plus allows for clean and run from the same script

Lol I left it to give them a credit


Issue to Build Pinpoin-flink Job

Team,
I am trying to setup the flink job for my docker container and as part of it trying to build the pinpoint-flink-job Jar (build) but maven is not able to download the dependencies from the below paths(No path is available with navercorp). Could you please help me here to get flink jar or solve the Maven build with proper repo path. Appreciate your help!.
http://jcenter.bintray.com/com/navercorp/pinpoint
https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/com/navercorp
http://jcenter.bintray.com/com/navercorp/pinpoint
ttps://repository.jboss.org/nexus/content/repositories/thirdparty-releases/com/navercorp
Reference:-
https://github.com/naver/pinpoint-docker (Flink Configuration)
https://github.com/naver/pinpoint/blob/master/doc/application-inspector.md#application-inspector
E. Build Pinpoint-flink and run the streaming job file created under target directory on the flink server.

Can anyone help on this issue

do you have the proper URL to download the flink jar or build it from the GIUT repo using proper Maven repo path?

First, you need to build the root.pom of the pinpoint.
After building, use $ PINPOINT_DIR\flink\target\pinpoint-flink-job-XXX.jar.

yes that is how I am trying to run the root pom file but not able to download any Pinpoint related jars from the above path. Even not able to see those "NAVERCORP" folder in those repo if I go manually to that path.
http://jcenter.bintray.com/com/navercorp/pinpoint
https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/com/navercorp
http://jcenter.bintray.com/com/navercorp/pinpoint

Any update or can i get Flink jar for 1.8.4 version?

@josephthanaraja
What do you mean by navercorp folder?
I don't think building flink module requires such dependencies.
It will be helpful if we can see the logs.

Parent and flink pom file has the dependency for those repo's (downloaded pinpoint 1.8.x).

pinpoint
com.navercorp.pinpoint
1.8.6-SNAPSHOT

Example Maven Build Log:-
[INFO] Downloading from : http://repository.cloudera.com/artifactory/cloudera-repos/com/navercorp/pinpoint/pinpoint-collector/1.8.6-SNAPSHOT/pinpoint-collector-1.8.6-SNAPSHOT.pom
[INFO] Downloading from : http://maven.springframework.org/release/com/navercorp/pinpoint/pinpoint-collector/1.8.6-SNAPSHOT/pinpoint-collector-1.8.6-SNAPSHOT.pom
[INFO] Downloading from : http://repo.spring.io/libs-release-remote/com/navercorp/pinpoint/pinpoint-collector/1.8.6-SNAPSHOT/pinpoint-collector-1.8.6-SNAPSHOT.pom
[INFO] Downloading from : http://jcenter.bintray.com/com/navercorp/pinpoint/pinpoint-collector/1.8.6-SNAPSHOT/pinpoint-collector-1.8.6-SNAPSHOT.pom
[INFO] Downloading from : https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/com/navercorp/pinpoint/pinpoint-collector/1.8.6-SNAPSHOT/pinpoint-collector-1.8.6-SNAPSHOT.pom

did you get a chance to verify this issue


bugfix: FilterBox Select should be Creatable

SUMMARY
This fixes the bug where users are not able to create new options in FilterBox select. This was because of a typo while migrating react-select (#9628).
I also fixed a UX issue where keep typing backspaces in an empty select loses focus. react-select fires onChange event in this case, which causes excessive rerenders.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Should allow create new options:

TEST PLAN
Added a Cypress test
ADDITIONAL INFORMATION

[x] Has associated issue: #9628
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #9940 into master will decrease coverage by 0.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9940      +/-   ##
==========================================
- Coverage   71.31%   71.14%   -0.17%
==========================================
  Files         585      184     -401
  Lines       30887    18035   -12852
  Branches     3236        0    -3236
==========================================
- Hits        22027    12831    -9196
+ Misses       8750     5204    -3546
+ Partials      110        0     -110

Flag
Coverage Δ

#cypress
?

#javascript
?

#python
71.14% <ø> (-0.40%)
:arrow_down:

Impacted Files
Coverage Δ

superset/views/database/mixins.py
59.64% <0.00%> (-21.06%)
:arrow_down:

superset/utils/cache.py
48.00% <0.00%> (-20.00%)
:arrow_down:

superset/db_engine_specs/mysql.py
78.26% <0.00%> (-13.05%)
:arrow_down:

superset/views/database/validators.py
78.94% <0.00%> (-5.27%)
:arrow_down:

superset/views/tags.py
35.13% <0.00%> (-4.11%)
:arrow_down:

superset/views/database/api.py
84.09% <0.00%> (-3.41%)
:arrow_down:

superset/views/sql_lab.py
59.06% <0.00%> (-3.29%)
:arrow_down:

superset/cli.py
36.72% <0.00%> (-3.14%)
:arrow_down:

superset/db_engine_specs/postgres.py
97.29% <0.00%> (-2.71%)
:arrow_down:

superset/views/database/views.py
87.17% <0.00%> (-2.57%)
:arrow_down:

... and 417 more

Continue to review full report at Codecov.

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