SOLR-16463 Provide a convenience jre11 image for 9.0

https://issues.apache.org/jira/browse/SOLR-16463
I believe the merge of this PR will trigger image build and a new PR being created upstream at https://github.com/docker-library/official-images to add the extra image? @HoustonPutman
An alternative is to downgrade the main tag 9.0.0 but that seems a bit too disruptive, at least for 9.0, since people may use our image as source for their own stuff and assume JRE17...
Should be perhaps also make a note in README.md displayed at Docker Hub, to alert users of the issue and the workaround? Will a change to README.md in this repo automatically update the docs on docker hub?

I think we need a patch to generate-stackbrew-library.sh too to process the variant.

yeah we need to patch it unfortunately... Also I assume we want to explicitly tag both jre-11 and jre-17, and have either the 11 or 17 be the default.... This is going to triple the number of tags we have though...
It is really nice to support just one JRE. It's sad that we can't do that.
I'll try to find time in a few days to help with the stackbrew stuff.

I'll try to find time in a few days to help with the stackbrew stuff.

Thanks. I see a comment in the stackbrew script about removing support for multi variants. But I gave it a shot by just adding a new variant to the loop, but that was not enough. We should probably keep the ability for such cases like this.

We could make jre11 the temporary default until the JDK bug is fixed. Then a -jre-17 tag should exist for those who depend on JDK17. But as soon as the JDK bug is fixed there is no need to provide jre11 for e.g. 9.2, is there?

We could make jre11 the temporary default until the JDK bug is fixed.

Agreed!

But as soon as the JDK bug is fixed there is no need to provide jre11 for e.g. 9.2, is there?

Nope

As mentioned on the issue. This bug affects caffeine not lucene in this case. I would not step back to JDK 11, it is much easier to fix this:
Pass -XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put on Solr's command line. So basically we should document this and the docker image should just pass this parameter. -- Problem solved.
Uwe

As mentioned on the issue. This bug affects caffeine not lucene in this case. I would not step back to JDK 11, it is much easier to fix this:
Pass -XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put on Solr's command line. So basically we should document this and the docker image should just pass this parameter. -- Problem solved.
Uwe

This would also not backwards break people's own docker images based on the Solr 9.0 one.

-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put

Just out of interest, what does this do? I'm afraid I'm not all that into JVM internals.

If there are still other occurences of this, we can still jump back to 11, but let people first upgrade and/or use the compile command. This is based on the reports on Solr's mailing list. Unfortunately not all of them posted the whole hserr file. Please ask them to always post especially the line after "Current CompileTask:", the other parts of the hserr file are not really useful.

Based on that information your can tell Hotspot to exclude that method from optimization

So it's exclude from optimization, not from compilation altogether. Makes sense, thanks!
(Also linking to the caffeine issue for completeness)

Based on that information your can tell Hotspot to exclude that method from optimization

So it's excluded from optimization, not from compilation altogether. Makes sense, thanks!
(Also linking to the caffeine issue for completeness)

From the standpoint of Hotspot it excludes it from compilation to assembly code.
From standpoint of end-user: yes, you're right.

Abandoning


"ng-date-valid" doesn't get added to a text input when the date is set programmatically

On the demo page, if you select a date using the left datepicker (which is a text input), the right input never gets the "ng-date-valid" class added to it. However, if you select the date using the right input (which is a date input), the class gets successfully added to both inputs.

The reason I'm using the ng-date-valid class is I need to validate the date if the user has entered something. However, the field is optional, so I can't use ng-required.

@distinctdan, there is not yet widespread browser support for <input type="date"/> (and there are still issues with those that allegedly do support it).  Please use <input type="text"/> and I believe this should solve your issue.

@icfantv Sorry for the misunderstanding, I am using <input type="text"> for everything. The text inputs are the ones that are broken. However, I happened to notice that the date input worked, so I brought it up to help with debugging.

I'm still not convinced this is an Angular UI Bootstrap issue, but I will reopen for investigation.  In the interim, can you please create a minimally working plunker that demonstrates the issue?  Thanks.
You can even use ours as a starting point, but strip out anything that's not relevant.

Thanks, I'll give it a shot. I've got some work stuff to do at the moment, but I'll look into it soon.

No worries.

Currently I don't know if this is the same case however I needed a datepicker with format dd.MM.yyyy.
My API gets a date with the format of 'dd.MM.yyyy' currently I need to format all DATES to feed them to the datepicker, is there any alternative in doing so?

Datepicker directive: "ng-model" value must be a Date object, a number of milliseconds since 01.01.1970 or a string representing an RFC2822 or ISO 8601 date.

Is there a way to change that??

@schmitch, based on my current understanding of what you've typed, yours is a completely different issue - one that is best suited for StackOverflow as our issues forum is reserved for bugs.
The format of the date is totally independent of the Date object in the ng-model - you can format it however you wish.  This is the entire point of separating views from models in that the view can display the model however it wishes.

Closing as a duplicate of #4664.
Looking into what we can do about this.

Thanks for looking into it.


Add 'differential diagnosis' as a child of 'diagnosis'

Should be a general enough term to belong in OGMS.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 2 Dec 2010 at 6:37

Closed ticket because issue has not been acted upon in reasonable amount of time.


Add AssImp to model loading pipeline

Open Asset Import Library is a Open Source library designed to load various 3d file formats and convert them into a shared, in-memory format. It supports more than 40 file formats for import and a growing selection of file formats for export.
This will let us start using standard model formats
https://github.com/assimp/assimp

Was just browsing along and saw this todo. I had a need for *.obj Allegiance models, so I went and converted them. I don't know if you finished your conversion, or if the way I converted will be useful at all - but feel free to check them out. https://github.com/brianmxwll/AllegianceModels
I'm open to further modifications (or fork away obv) if they make them more broadly usable. Lemme know. I'm not a model expert so may have missed a detail somewhere along the line :)

That's sweet @brianmxwll I never did finish the mdl -> obj converter, and had never even thought of doing x->obj.
I imagine what you have so far is enough to be able to test adding assimp to allegiance.

Here is the .net lib I created for loading .mdl files into memory so they could be converted. https://github.com/AllegianceZone/MDLReaderWriter

Awesome. Let me know if you run into any issues using the obj files. They may work for one purpose but not others, so definitely open to tweaking them to work for everyone.
The only thing I haven't focused on so far is creating a material (*.obj.mtl) file for the derivative models like *_static.obj. Those ones I just stripped all material reference from since I can't necessarily guarantee that the standard model and standard_static model are identical.

I'm seeing some mtl's in there. https://github.com/brianmxwll/AllegianceModels/blob/master/Models/cap300/obj/cap300.obj.mtl
Is it enough to just add
mtllib cap300.obj.mtl

to the _static.obj file so they use the same .mtl as the non static .obj? Also what is the difference between the _static.obj and the other. No animation data?

Btw. looking in https://github.com/brianmxwll/AllegianceModels/blob/master/Models/cap300/cap300.x#L4673
I see animation set and anm-* and I'm not seeing that same data in the .obj file.

I don't think just adding a reference to the .mtl will be sufficient - there are materials referenced in the .obj file for each mesh/submesh. See: https://github.com/brianmxwll/AllegianceModels/blob/master/Models/cap300/obj/cap300.obj#L1445
I'll look into the animation stuff when I have some time. I structured the repo to support different file formats, so a "dae" folder for each model would be just fine. Since obj files don't support animation, that's gonna be a hard stop if animation is required. Kind of a mixed bag, IMO, is there any animation in the models that's actually worthwhile? Besides bomber missile bays opening... kinda meh. Open to being wrong though haha

To tack on about the _static.obj files (ignoring animation for now), it wouldn't be too hard to add in the material references to match the standard .obj file. The obj file is broken up by meshes and Assimp outputs them into clean blocks - easy enough to parse through and add the appropriate material references.
The only unknown for me is the difference between *.obj and *_static.obj. Are -all- of those models
(functionally, not literally) identical? If not, we would have to figure out which textures actually work and which ones dont... a manual process for sure.

Well we have never had the animation so we don't know what we are missing really. :P But games like Eve do a pretty good job making ships with animation. That doesn't mean we need to carry over the animations from the existing models if it is a pain. I was hoping it was the export format not supporting it that was the issue, but I think It has more to do with the .x files being imported.

Eh, it may or may not. Obj just doesn't support anims... so it might be worth checking out a diff format to see how it fares.


Add RecordBatchWriter trait and implement it for CSV, JSON, IPC and Parquet

Which issue does this PR close?
This PR doesn't close any particular issue.
Rationale for this change
I found myself needing to work generically with writers of record batches and I need a common interface for doing that.
Do you find this useful? Feel free to reject the PR if you don't see any use case for it.
What changes are included in this PR?
A new trait is introduced and implemented for CSV, JSON, IPC and Parquet :
/// Trait for types that can write `RecordBatch`'s.
pub trait RecordBatchWriter {
    /// Write a single batch to the writer.
    fn write(&mut self, batch: &RecordBatch) -> Result<(), ArrowError>;
}

Are there any user-facing changes?
According to my analysis there are at least two breaking changes:

To use write clients now need to import RecordBatchWriter
parquet::arrow_writer::ArrowWriter now returns an ArrowError instead of ParquetError

Perhaps we could avoid this being a breaking change by not removing the member functions? This would also make the PR smaller? This sort of method overloading has well-defined semantics, which we exploit for things like Array::slice

Oh yes you're right, I didn't this was possible... I will open a new PR. Thank you


hooks not called

Environment

Operating System: Darwin
Node Version:     v20.15.0
Nuxt Version:     3.12.4
CLI Version:      3.12.0
Nitro Version:    -
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      compatibilityDate, devtools, modules, colorMode, hooks
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
// https://nuxt.com/docs/api/configuration/nuxt-config
import WireGuard from "./server/utils/WireGuard.js";
export default defineNuxtConfig({
  compatibilityDate: '2024-04-03',
  devtools: { enabled: true },
  modules: [
    '@nuxtjs/i18n',
    '@nuxtjs/tailwindcss',
    '@pinia/nuxt',
    '@nuxtjs/color-mode',
  ],
  colorMode: {
    preference: 'system',
    fallback: 'light',
    classSuffix: '',
    storageKey: 'theme',
  },
  hooks: {
    'ready': (nuxt) => {
      console.log('nuxt ready hook');
      process.on('SIGTERM', async () => {
        console.log('SIGTERM signal received.');
        await nuxt.close();
      });
      setTimeout(() => {
        process.kill(process.pid, 'SIGTERM');
      }, 10000);
    },
    'close': () => {
      console.log('close')
      setTimeout(() => {
        console.log('closed hook');
      }, 5000);
    }
  }
});

export default defineNitroPlugin((nitroApp) => {
  nitroApp.hooks.hook('close, () => {
    console.log('Shutting down')
  })
})

https://github.com/kaaax0815/wg-easy/tree/feat/nuxt
Describe the bug
I am using docker to run .output/server/index.mjs
When I run docker compose stop I expect the close hook to run or atleast the SIGTERM hook.
Edit: It seems like the hook in nuxt config only is at build time (where it does run) but either way the nitro hooks is never called
But it just stops and doesnt work
With an older version of the project with bare h3 and vue it works
Additional context
Old Server: https://github.com/wg-easy/wg-easy/blob/488e3c32/src/server.js
Logs
Literally nothing

Hooks registered in your nuxt.config hook into the 'builder', not your runtime app, so this is expected behaviour.
For the issue with the nitro plugin, would you see if you can reproduce this in pure Nitro (reproduction sandbox), and if so, raise there? 🙏


Continue the work regarding the RFC for an expressive moment in a Carbon core component

User Story

As a [user role below]:
Carbon adopter

I need to:
have an expressive moment available in [decide which carbon component] available

so that I can:
utilize in my application that requires a marketing/editorial look and feel

Additional information

Should use the existing Carbon Expressive theme as a reference (https://carbon-expressive.mybluemix.net)
The Carbon RFC has been created.  This story is to continue the work from sprint 20-07.
The related stories with background on this work are:  Issue (#1782), Issue (#2044), Issue (#2362), Issue (#2491)

Acceptance criteria

[ ] Reach out to Carbon team to schedule a walkthrough of the RFC

Closing this issue as the work was finished in sprint 20-12.


[canary] webp settings has no effect

Hi, thanks for a great library!
I'm testing canary build now, I noticed that webp options has no effect.
(I want more lower quality webp images)
My setting is as follows.
Am I missing something?
module.exports = withPlugins([
  [
    optimizedImages,
    {
      images: {
        webp: {
          quality: 10,
        },
      },
    },
  ],
]);

@cyrilwanner any update on this? I'm doing the same for "svgo" (trying to disable a plugin), and it has no effect.

Damn, I've just came across this issue. Glad I'm not the only one!

@cyrilwanner Can you please fix it ??


US 02.06.01

As a player, I want to see a visual representation of a QR code relatively unique to that QR code.
Acceptance Criteria:

Need a way to express each QR code visually
Example of that on screen 5

Note: Will need to use Java's DrawView likely
https://developer.android.com/develop/ui/views/layout/custom-views/custom-drawing


History in .jhipster folder

Each time an API is used, we could add an entry in a history file, something like: .jhipster/history
I don't know how to achieve this for now, so any suggestion is welcome:

shared context which is called after each API
using AOP for methods in primary/rest and only for output
spring events

This kind of history/log can also be used to make dependencies while generating project using frontend/cli.
A few thoughts:-

The project information like baseName, packageName etc. should also be persisted (to make the project directory more stateful), currently we need to pass it on every request in REST, which can cause mismatches.
Version of the jh-lite could also be stored for providing upgradability in future releases.

I like the AOP/Annotation way as it will give flexibility and visibility how things are being generated.

This kind of history/log can also be used to make dependencies while generating project using frontend/cli.
A few thoughts:-

The project information like baseName, packageName etc. should also be persisted (to make the project directory more stateful), currently we need to pass it on every request in REST, which can cause mismatches.
Version of the jh-lite could also be stored for providing upgradability in future releases.

I like the AOP/Annotation way as it will give flexibility and visibility how things are being generated.

@swarajsaaj : thanks for thinking about it, but plz don't start this ticket before we agree together :-)
I'm still thinking about baseName and packageName.
baseName is used at init
packageName is used at maven
Then, once it is used, we can find the information by reading package.json or pom.xml, it means we don't need to store it.
It means there are some API which can be used in existing Spring Boot project (without the need to be init with JH Lite)
I think the history could be used for reproducing some issues later, so we know which API were used : but I'm not sure about my ideas!
That's why we should discuss, before starting something

@swarajsaaj : thanks for thinking about it, but plz don't start this ticket before we agree together :-)
I'm still thinking about baseName and packageName.
baseName is used at init
packageName is used at maven
Then, once it is used, we can find the information by reading package.json or pom.xml, it means we don't need to store it.
It means there are some API which can be used in existing Spring Boot project (without the need to be init with JH Lite)
I think the history could be used for reproducing some issues later, so we know which API were used : but I'm not sure about my ideas!
That's why we should discuss, before starting something

Sure @pascalgrimaud :)

It means there are some API which can be used in existing Spring Boot project (without the need to be init with JH Lite)
Yes, that is a benefit we get without depending on a persisted information and taking it from pom/pacakge.json.

And I think there are 2 concepts that are being mixed (at least in my mind :)),

To be able to reconstruct the current state of application (like we did from .yo-rc.json in generator-jhipster to allow user further commands based on existing structure)
Maintaining an event-log like history to be able to know what steps user followed to create the project (as you mentioned to be able to reproduce an issue)

For 1st approach, it would depend also on what are needs of frontend/cli in future to work properly (ofcourse something like that would be needed when we move towards entity CRUD). I was also thinking if this can be used for dependency validations of all features (as mentioned earlier)
For 2nd approach, I like it as a audit/event log of what happened during the course of generation, more of like a log maybe? Would a log file be enough here or we have need of a readable structure like json?
Ofcourse, 2nd approach is lightweight and can be done before 1st one.

Sure @pascalgrimaud :)

It means there are some API which can be used in existing Spring Boot project (without the need to be init with JH Lite)
Yes, that is a benefit we get without depending on a persisted information and taking it from pom/pacakge.json.

And I think there are 2 concepts that are being mixed (at least in my mind :)),

To be able to reconstruct the current state of application (like we did from .yo-rc.json in generator-jhipster to allow user further commands based on existing structure)
Maintaining an event-log like history to be able to know what steps user followed to create the project (as you mentioned to be able to reproduce an issue)

For 1st approach, it would depend also on what are needs of frontend/cli in future to work properly (ofcourse something like that would be needed when we move towards entity CRUD). I was also thinking if this can be used for dependency validations of all features (as mentioned earlier)
For 2nd approach, I like it as a audit/event log of what happened during the course of generation, more of like a log maybe? Would a log file be enough here or we have need of a readable structure like json?
Ofcourse, 2nd approach is lightweight and can be done before 1st one.

Hello,
I can develop the feature. The generator will add in a json file at the init of a project.
Each rest service can be annotated with à custom annotation (with an unique id for the moment).
With aop, we can intercept all rest service called, and get the id from the annotation, to save it in the history file.
It's good for you ?

Fine, thanks @Bolo89
Let's give a try with your suggestions

added a bounty as it's a lot of work here, and this feature will be very usefull


PHP messing with my PATH

For some reason, my PATH is being messed by PHP and I didn't found anything that could causes this:
$ echo $PATH
{PATH}:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:Warning: PHP Startup: Unable to load dynamic library 'redis.so' (tried: /home/aledsz/.asdf/installs/php/8.1.9/lib/php/extensions/no-debug-non-zts-20210902/redis.so (/home/aledsz/.asdf/installs/php/8.1.9/lib/php/extensions/no-debug-non-zts-20210902/redis.so: cannot open shared object file: No such file or directory), /home/aledsz/.asdf/installs/php/8.1.9/lib/php/extensions/no-debug-non-zts-20210902/redis.so.so (/home/aledsz/.asdf/installs/php/8.1.9/lib/php/extensions/no-debug-non-zts-20210902/redis.so.so: No such file or directory)) in Unknown on line 0

Warning: Unable to load dynamic library 'imagick.so' (tried: /home/aledsz/.asdf/installs/php/8.1.9/lib/php/extensions/no-debug-non-zts-20210902/imagick.so (/home/aledsz/.asdf/installs/php/8.1.9/lib/php/extensions/no-debug-non-zts-20210902/imagick.so: No such file or directory), /home/aledsz/.asdf/installs/php/8.1.9/lib/php/extensions/no-debug-non-zts-20210902/imagick.so.so (/home/aledsz/.asdf/installs/php/8.1.9/lib/php/extensions/no-debug-non-zts-20210902/imagick.so.so: No such file or directory)) in Unknown on line 0
/home/aledsz/.asdf/installs/php/8.1.9/.composer/vendor/bin

Currently I'm using Oh-My-Zsh and I removed the asdf plugin and it works flawlessly.
Then I digged into asdf plugin and it just checks the folder and loads the asdf.sh and competions/asdf.bash.
Since it shows PHP errors, I guess it's from asdf but I'm not so sure. I'm using PHP 8.1.9 and it's making it worse to work with PATH which I can't use it directly from other programming language and I'm trying to not uninstall PHP because I still need to use with my own stuff.
My php.ini only adds xdebug and it's configurations, I don't even have these extensions installed from pecl.
So, do anyone have idea what's going on? I'm not used to asdf code, so I'll need some help/context here.

How are you loading asdf? Which option did you choose? Also yout PHP installation seems to be broken, it would be better for you to uninstall and install again:
asdf uninstall php <version>

Which option did you choose for loading asdf? Also your PHP installation seems to be broken, it would be better for you to uninstall and install again:
asdf uninstall php <version>

I've use the default asdf loading, installed the php plugin and then the php 8.1.9.


[0.8 regression] Spin checkbox doesn't work any more

Describe the bug
The spin checkbox (in the right panel when a 3D space view is selected) doesn't stick
Doesn't work in 0.8: https://demo.rerun.io/version/0.8.0/examples/structure_from_motion/
It used to work in 0.7: https://demo.rerun.io/version/0.7.0/examples/structure_from_motion/
To Reproduce
Steps to reproduce the behavior:

Run demo
select the 3d space view (the left one)
click on "spin" checkbox on the right

It works once there is a change to the blueprint. Surprised that the fixed regarding similar issues don't catch this.


Weird failures with latest build

Trying to upgrade to 1.0.0-rc.2, and in my CRA app, I'm getting weird failures:
[1] Starting the development server...
[1]
[1] Failed to compile.
[1]
[1] Error in ./~/react-dropzone-s3-uploader/lib/DropzoneS3Uploader.js
[1] Module not found: 'react-transform-catch-errors' in /Users/da/src/participedia/frontend/node_modules/react-dropzone-s3-uploader/lib
[1]
[1]  @ ./~/react-dropzone-s3-uploader/lib/DropzoneS3Uploader.js 3:34-73
[1]
[1] Error in ./~/react-dropzone-s3-uploader/lib/DropzoneS3Uploader.js
[1] Module not found: 'redbox-react' in /Users/da/src/participedia/frontend/node_modules/react-dropzone-s3-uploader/lib
[1]
[1]  @ ./~/react-dropzone-s3-uploader/lib/DropzoneS3Uploader.js 11:19-42
[1]
[1] Compiling...
[1] Failed to compile.
[1]
[1] Error in ./~/react-dropzone-s3-uploader/lib/DropzoneS3Uploader.js
[1] Module not found: 'react-transform-catch-errors' in /Users/da/src/participedia/frontend/node_modules/react-dropzone-s3-uploader/lib
[1]
[1]  @ ./~/react-dropzone-s3-uploader/lib/DropzoneS3Uploader.js 3:34-73
[1]
[1] Error in ./~/react-dropzone-s3-uploader/lib/DropzoneS3Uploader.js
[1] Module not found: 'redbox-react' in /Users/da/src/participedia/frontend/node_modules/react-dropzone-s3-uploader/lib
[1]
[1]  @ ./~/react-dropzone-s3-uploader/lib/DropzoneS3Uploader.js 11:19-42
[1]

I'll dig in a bit more, but I figured I'd flag early given that it's an RC.

There's definitely something odd in that the npm package seems to have code that doesn't match what's in src.  Maybe an old babel config?

Doh, thanks. Last publish was from the node_modules dir of another project - babel must have picked up the parent config. I'd never have caught it! 1.0.0-rc.3 is published which should be better.


panic: runtime error: index out of range,  goroutine 89 [running]

Hello, I got this problem when I use operator-sdk add api --api-version=app.example.com/v1alpha1 --kind=AppService

I just follow the ReadMe, Quick Start.

I use brew install operator-sdk.  MacOs

Hi @YanRyan,
It shows duplicated of https://github.com/operator-framework/operator-sdk/issues/1734.
Please, could you check and if yes close this one? Also, note that here (https://github.com/operator-framework/operator-sdk/issues/1734)you will find the steps to solve it.

I am sorry to say that, '#1734'  this didn't solve my problem.
At first, this is my go env

Then I change my GOROOT to '/usr/local/go', I still got this problem. It's panic at 'Created pkg/apis/asia/group.go'. I sign it use red frame.

Then I try again, follow the issues #1765 I change my GOROOT to '/url/lib/golang', It panic at 'Created deploy/crds '. I sign it use red frame.

Is there anything I didn't do correct or just the env promblem?

Hello, I try to reinstall go, it still have this problem. What should I do.

?

Hi @YanRyan.
Did you try it https://github.com/operator-framework/operator-sdk/issues/1545#issuecomment-500982788 ?

Yes, I try this. I reinstall go and the default location is '/usr/local/go'

Hi @YanRyan.
Did you try it #1545 (comment) ?
Yes, I try this. I reinstall go and the default location is '/usr/local/go'. It still panic. I saw you have the same problem, you fix it by set GOROOT?

@YanRyan How are you installing go? If you use Homebrew to install operator-sdk, it will also install the go brew formula, which may be conflicting with your existing Go installation.
If which go reports /usr/local/go/bin/go, then your GOROOT needs to be set to /usr/local/go.
If which go reports /usr/local/Cellar/go/1.12.7/bin/go then your GOROOT needs to be set to /usr/local/Cellar/go/1.12.7/libexec
My advice is to make sure you only have one go installation on your system, in which case you should not have to explicitly set GOROOT.

@YanRyan I'm going to close this since it seems like a duplicate of #1545, but we'll be happy to help you keep debugging your go environment my above comment doesn't resolve it.

I'm so sorry to say that, I still have this problem.
The which go  reports /usr/local/go/bin/go, and go env GOROOT reports /usr/local/go
I delete all the go installation then I use go1.12.7.darwin-amd64.pkg install it. Should I need to reinstall the operator-sdk?
More information please check the image.

It drives me crazy.  I use brew uninstall operator-sdk    then I git clone && make install the operator-sdk it still have this problem.

I install the go and operator-sdk in CentOS 7.5, then I create the project success.  I think this the problem of my MacOs, maybe there still have env problem. Tanks all!

I hit the similar issue on mac. Reinstalled go and operator-sdk, but still met the error:
$ operator-sdk add api --api-version=app.example.com/v1alpha1 --kind=AppService
INFO[0000] Generating api version app.example.com/v1alpha1 for kind AppService.
INFO[0000] Created pkg/apis/app/group.go
panic: runtime error: index out of range

goroutine 69 [running]:
golang.org/x/tools/imports.(*moduleResolver).scan.func1(0xc000767880, 0x17, 0x4, 0xc00076b040, 0x37)
	pkg/mod/golang.org/x/tools@v0.0.0-20190408170212-12dd9f86f350/imports/mod.go:254 +0x9df
golang.org/x/tools/internal/gopathwalk.(*walker).walk(0xc0004c0480, 0xc00076b040, 0x41, 0x0, 0xc00076b040, 0x41)
	pkg/mod/golang.org/x/tools@v0.0.0-20190408170212-12dd9f86f350/internal/gopathwalk/walk.go:175 +0xf5
golang.org/x/tools/internal/fastwalk.(*walker).onDirEnt(0xc0007f4990, 0xc0008389c0, 0x37, 0xc0000500e0, 0x9, 0xc000000000, 0x0, 0x0)
	pkg/mod/golang.org/x/tools@v0.0.0-20190408170212-12dd9f86f350/internal/fastwalk/fastwalk.go:168 +0xbb
golang.org/x/tools/internal/fastwalk.readDir(0xc0008389c0, 0x37, 0xc0007b7e88, 0x0, 0x0)
	pkg/mod/golang.org/x/tools@v0.0.0-20190408170212-12dd9f86f350/internal/fastwalk/fastwalk_unix.go:68 +0x212
golang.org/x/tools/internal/fastwalk.(*walker).walk(0xc0007f4990, 0xc0008389c0, 0x37, 0x1, 0x1, 0x0)
	pkg/mod/golang.org/x/tools@v0.0.0-20190408170212-12dd9f86f350/internal/fastwalk/fastwalk.go:195 +0x6a
golang.org/x/tools/internal/fastwalk.(*walker).doWork(0xc0007f4990, 0xc00080cf50)
	pkg/mod/golang.org/x/tools@v0.0.0-20190408170212-12dd9f86f350/internal/fastwalk/fastwalk.go:134 +0x14d
created by golang.org/x/tools/internal/fastwalk.Walk
	pkg/mod/golang.org/x/tools@v0.0.0-20190408170212-12dd9f86f350/internal/fastwalk/fastwalk.go:81 +0x21d```

Some info for my settings:
- go version: go version go1.12.9 darwin/amd64
- which go:  /usr/local/bin/go
- operator-sdk version: v0.10.0
- GOROOT=/usr/local/go

@mandymchu How did you install operator-sdk?

@joelanford  Used brew install operator-sdk

I tried reinstalling go via go1.12.9.darwin-amd64.tar.gz, but it did not help as well

Hmm I thought I was able to get things working originally on my Mac, but now I'm getting a panic trying all sorts of combinations of ways of installing Go and operator-sdk. I'm going to re-open this until we get to the bottom of this.
@estroz @hasbro17 @theishshah @fabianvf @jmrodri Do any of you all have this working on a Mac? If so, what's your setup?
@mandymchu Either way, your environment looks like it could be broken. Your GOROOT is /usr/local/go, so I would expect which go to be /usr/local/go/bin/go, not /usr/local/bin/go
My guess is that you have a self-installed Go (as you mentioned) but ALSO a Go installation from brew as a result of operator-sdk's brew formula declaring a dependency on the go brew formula.

@joelanford After uninstall and reinstall, now which go -a returns /usr/local/go/bin/go.

This might be a go modules related issue.
While I'm not getting the index out of range panic I do see the runtime error: invalid memory address or nil pointer dereference if I run the command inside $GOPATH/src with GO111MODULES=on:
$ operator-sdk version
operator-sdk version: v0.9.0-50-g4ca881a9, commit: 4ca881a92eb71b19d4689065ae9bf4dcf9b43331

$ operator-sdk add api --api-version=app.example.com/v1alpha1 --kind=AppService
INFO[0000] Generating api version app.example.com/v1alpha1 for kind AppService.
INFO[0000] Created pkg/apis/app/group.go
INFO[0005] Created pkg/apis/app/v1alpha1/appservice_types.go
INFO[0005] Created pkg/apis/addtoscheme_app_v1alpha1.go
INFO[0005] Created pkg/apis/app/v1alpha1/register.go
INFO[0005] Created pkg/apis/app/v1alpha1/doc.go
INFO[0005] Created deploy/crds/app_v1alpha1_appservice_cr.yaml
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x18e98d5]

goroutine 1 [running]:
k8s.io/gengo/parser.(*Builder).AddDirRecursive(0xc0003a20a0, 0xc000542300, 0x32, 0x2, 0x2)
	pkg/mod/k8s.io/gengo@v0.0.0-20190327210449-e17681d19d3a/parser/parse.go:229 +0xb5
sigs.k8s.io/controller-tools/pkg/crd/generator.(*Generator).Do(0xc000729760, 0x0, 0x0)
	pkg/mod/sigs.k8s.io/controller-tools@v0.0.0-20190411181648-9d55346c2bde/pkg/crd/generator/generator.go:126 +0x3ac
github.com/operator-framework/operator-sdk/internal/pkg/scaffold.(*CRD).CustomRender(0xc000268160, 0x2cff980, 0x4000ca0, 0x73f29d0, 0xc000268160, 0x1)
	/Users/haseeb/work/module-projects/operator-sdk/internal/pkg/scaffold/crd.go:102 +0x27e
github.com/operator-framework/operator-sdk/internal/pkg/scaffold.(*Scaffold).doRender(0xc000729cf8, 0xc0000b2270, 0x2c, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc000058211, 0x29, ...)
	/Users/haseeb/work/module-projects/operator-sdk/internal/pkg/scaffold/scaffold.go:222 +0x16c
github.com/operator-framework/operator-sdk/internal/pkg/scaffold.(*Scaffold).doFile(0xc000729cf8, 0x2c85720, 0xc000268160, 0x0, 0x0)
	/Users/haseeb/work/module-projects/operator-sdk/internal/pkg/scaffold/scaffold.go:192 +0x230
github.com/operator-framework/operator-sdk/internal/pkg/scaffold.(*Scaffold).Execute(0xc000729cf8, 0xc000729c68, 0xc000729c98, 0x6, 0x6, 0x0, 0x0)
	/Users/haseeb/work/module-projects/operator-sdk/internal/pkg/scaffold/scaffold.go:157 +0x103
github.com/operator-framework/operator-sdk/cmd/operator-sdk/add.apiRun(0xc000570280, 0xc00000cc20, 0x0, 0x2, 0x0, 0x0)
	/Users/haseeb/work/module-projects/operator-sdk/cmd/operator-sdk/add/api.go:118 +0x542
github.com/spf13/cobra.(*Command).execute(0xc000570280, 0xc00000cbc0, 0x2, 0x2, 0xc000570280, 0xc00000cbc0)
	pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:762 +0x465
github.com/spf13/cobra.(*Command).ExecuteC(0xc0000f1b80, 0x2c88c00, 0xc000321e00, 0x0)
	pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:852 +0x2ec
github.com/spf13/cobra.(*Command).Execute(...)
	pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:800
main.main()
	/Users/haseeb/work/module-projects/operator-sdk/cmd/operator-sdk/main.go:85 +0x50f

With GO111MODULES=off inside $GOPATH/src or running the command outside of $GOPATH/src there is no issue.
Debugging this a bit more with the master branch to confirm.

brew install

I still have this problem, I suggest that do not use "brew install brew install operator-sdk .  Use make install . I also try to reinstall go and operator-sdk, but it's not work. So I find a Centos 7.5 machine to install the operator-sdk then it could work.

@YanRyan @mandymchu Can you try uninstalling your brew-installed operator-sdk and go, and instead building from source as described here and see if you still have the problem?
My current hypothesis is that there's something intrinsic in the operator-sdk binary from it's original build environment that causes problems if it's used with a different go environment. It seems like I'm unable to reproduce the issue when I build from source and re-use the same Go installation to build and run operator-sdk.

Update: I can't reproduce the above runtime error anymore.
$ operator-sdk version
operator-sdk version: v0.10.0, commit: ff80b17737a6a0aade663e4827e8af3ab5a21170

// Inside $GOPATH/src
$ pwd
/Users/haseeb/work/go-space/src/github.com/example-inc

$ GO111MODULE=on operator-sdk new app-operator
INFO[0000] Creating new Go operator 'app-operator'.
INFO[0000] Created go.mod
INFO[0000] Created tools.go
INFO[0000] Created cmd/manager/main.go
INFO[0000] Created build/Dockerfile
INFO[0000] Created build/bin/entrypoint
INFO[0000] Created build/bin/user_setup
INFO[0000] Created deploy/service_account.yaml
INFO[0000] Created deploy/role.yaml
INFO[0000] Created deploy/role_binding.yaml
INFO[0000] Created deploy/operator.yaml
INFO[0000] Created pkg/apis/apis.go
INFO[0000] Created pkg/controller/controller.go
INFO[0000] Created version/version.go
INFO[0000] Created .gitignore
INFO[0000] Validating project
go: finding github.com/operator-framework/operator-sdk master
INFO[0004] Project validation successful.
INFO[0004] Project creation complete.

// GO111MODULE=off inside $GOPATH now results in the correct error
$ cd app-operator/
$ GO111MODULE=off operator-sdk add api --api-version=app.example.com/v1alpha1 --kind=AppService
FATA[0000] dependency manager "modules" requires working directory to be in $GOPATH/src and GO111MODULE=on, or outside of $GOPATH/src and GO111MODULE="on", "auto", or unset. More info: https://github.com/operator-framework/operator-sdk/blob/master/doc/user-guide.md#go-modules

$ GO111MODULE=on operator-sdk add api --api-version=app.example.com/v1alpha1 --kind=AppService
INFO[0000] Generating api version app.example.com/v1alpha1 for kind AppService.
INFO[0000] Created pkg/apis/app/group.go
INFO[0002] Created pkg/apis/app/v1alpha1/appservice_types.go
INFO[0002] Created pkg/apis/addtoscheme_app_v1alpha1.go
INFO[0002] Created pkg/apis/app/v1alpha1/register.go
INFO[0002] Created pkg/apis/app/v1alpha1/doc.go
INFO[0002] Created deploy/crds/app_v1alpha1_appservice_cr.yaml
INFO[0010] Created deploy/crds/app_v1alpha1_appservice_crd.yaml
INFO[0010] Running deepcopy code-generation for Custom Resource group versions: [app:[v1alpha1], ]
INFO[0018] Code-generation complete.
INFO[0018] Running OpenAPI code-generation for Custom Resource group versions: [app:[v1alpha1], ]
INFO[0034] Created deploy/crds/app_v1alpha1_appservice_crd.yaml
INFO[0034] Code-generation complete.
INFO[0034] API generation complete.

Same for the version that I initially tested out with operator-sdk version: v0.9.0-54-gabac23c8, commit: abac23c897b898e6fecfb2c02fe318843ae9347f.
Not entirely sure what I changed or how I managed to run add api inside $GOPATH/src with GO111MODULE=off before.

@joelanford @hasbro17  I uninstalled brew-installed operator-sdk and installed it from Github release, also confirmed that /usr/local/Cellar/go was removed which means only one go (/usr/local/go) installed. However, they does not fix the issue...

@joelanford @hasbro17 In my macOS(installed go and operator-sdk by brew), I reproduce this issue. But when I uninstall operator-sdk and make install from source in master(abac23c897b898e6fecfb2c02fe318843ae9347f), it works well. So I think maybe we need to release one new version for this. Any thoughts?
@YanRyan Can you try with this?

I still get panic: runtime error: index out of range even after explicitly setting GOROOT.

bash-3.2$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/sanupin/Library/Caches/go-build"
GOENV="/Users/sanupin/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/sanupin/go-workspace"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/sanupin/go-workspace/src/couchbase-cluster-operator/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/sr/n5q9l_fn7yj8mx6rbfq8smbn72mpx6/T/go-build664640064=/tmp/go-build -gno-record-gcc-switches -fno-common"

Have reinstalled Go, reinstalled operator-sdk. Nothing works. Please help!


Test failure: TlsHandshakeRejectsTlsLessThan12

This test fails occasionally with the following error:
System.IO.IOException : The reader completed without returning a frame.
   at Microsoft.AspNetCore.Server.Kestrel.InMemory.FunctionalTests.Http2.TlsTests.ReceiveFrameAsync(PipeReader reader) in /_/test/Kestrel.InMemory.FunctionalTests/Http2/TlsTests.cs:line 113
   at Microsoft.AspNetCore.Server.Kestrel.InMemory.FunctionalTests.Http2.TlsTests.WaitForConnectionErrorAsync(PipeReader reader, Boolean ignoreNonGoAwayFrames, Int32 expectedLastStreamId, Http2ErrorCode expectedErrorCode) in /_/test/Kestrel.InMemory.FunctionalTests/Http2/TlsTests.cs:line 75
   at Microsoft.AspNetCore.Server.Kestrel.InMemory.FunctionalTests.Http2.TlsTests.TlsHandshakeRejectsTlsLessThan12() in /_/test/Kestrel.InMemory.FunctionalTests/Http2/TlsTests.cs:line 68
--- End of stack trace from previous location where exception was thrown ---
------- Stdout: -------
| [0.008s] TestLifetime Information: Starting test TlsHandshakeRejectsTlsLessThan12 at 2018-08-08T20:00:55
| [0.060s] Microsoft.AspNetCore.Hosting.Internal.WebHost Debug: Hosting starting
| [0.090s] Microsoft.AspNetCore.Hosting.Internal.WebHost Debug: Hosting started
| [0.090s] Microsoft.AspNetCore.Hosting.Internal.WebHost Debug: Loaded hosting startup assembly testhost
| [0.090s] Microsoft.AspNetCore.Server.Kestrel Debug: Connection id "0HLFTD6JCB5QA" started.
| [1.431s] Microsoft.AspNetCore.Server.Kestrel Error: HTTP/2 over TLS was not negotiated on an HTTP/2-only endpoint.
| [1.564s] Microsoft.AspNetCore.Hosting.Internal.WebHost Debug: Hosting shutdown
| [1.731s] Microsoft.AspNetCore.Server.Kestrel Debug: Connection id "0HLFTD6JCB5QA" stopped.
| [1.755s] TestLifetime Information: Finished test TlsHandshakeRejectsTlsLessThan12 in 1.7478597s

Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
CC @Eilon,@muratg,@mkArtakMSFT
This issue was made automatically. If there is a problem contact @ryanbrandenburg.

Please use this workflow to address this flaky test issue, including checking applicable checkboxes and filling in the applicable "TODO" entries:

Is this actually a flaky test?

No, this is a regular test failure, fix the test/product (TODO: Link to commit/PR)
Yes, proceed below...

Is this test failure caused by product code flakiness? (Either this product, or another product this test depends on.)

[ ] File a bug against the product (TODO: Link to other bug)
Is it possible to change the test to avoid the flakiness?

Yes? Go to the "Change the test!" section.
No?

[ ] Disable the test (TODO: Link to PR/commit)
[ ] Wait for other bug to be resolved
[ ] Wait for us to get build that has the fix
[ ] Re-enable our test (TODO: Link to PR/commit)
[ ] Close this bug

Is it that the test itself is flaky? This includes external transient problems (e.g. remote server problems, file system race condition, etc.)

Is there is a way to change our test to avoid this flakiness?

Yes? Change the test!

[ ] Change the test to avoid the flakiness, for example by using a different test strategy, or by adding retries w/ timeouts (TODO: Link to PR/commit)
[ ] Run the test 100 times locally as a sanity check.
[ ] Close this bug

No?

[ ] Delete the test because flaky tests are not useful (TODO: Link to PR/commit)

This comment was made automatically. If there is a problem contact @ryanbrandenburg.

Agent setup issue. Mike is trying to get this working on Ubuntu 14.04.


Adding RpcMetric type to FunctionRpc

For https://github.com/Azure/azure-functions-dotnet-worker/issues/543
To accompany https://github.com/Azure/azure-functions-host/pull/7593 per @pragnagopa

@pragnagopa see latest changes. Have this passing in a UT w/in dotnet worker but want to get it working live as well. Nevertheless this is my proposal for the protocol now.

Will do, though I don't think I can merge until @brettsam and @alrod have signed off as well....

@pragnagopa tested & verified.
Put the following in the .Net 5 OOP worker function sample (Function 4):
[Function("Function4")]
public static HttpResponseData Run([HttpTrigger(AuthorizationLevel.Anonymous, "get", "post", Route = null)] HttpRequestData req, FunctionContext executionContext)
{
    var sw = new Stopwatch();
    sw.Restart();
    var logger = executionContext.GetLogger("FunctionApp.Function4");

    logger.LogInformation("message logged");

    var response = req.CreateResponse(HttpStatusCode.OK);

    response.Headers.Add("Date", "Mon, 18 Jul 2016 16:06:00 GMT");
    response.Headers.Add("Content-Type", "text/html; charset=utf-8");
    response.WriteString("Welcome to .NET 5!!");

    logger.LogMetric(@"net5exectimeMs", sw.Elapsed.TotalMilliseconds,
        new Dictionary<string, object> {
            { "foo", "bar"},
            { "baz", 42}
        }
    );

    return response;
}

Launched the Func Host locally w/ the dotnet worker as the script root, made a call to the Function 4 endpoint
> curl "http://localhost:54468/api/Function4"

StatusCode        : 200
StatusDescription : OK
Content           : Welcome to .NET 5!!
RawContent        : HTTP/1.1 200 OK
                    Transfer-Encoding: chunked
                    Request-Context: appId=
                    Content-Type: text/html; charset=utf-8
                    Date: Mon, 18 Jul 2016 16:06:00 GMT
                    Server: Kestrel

                    Welcome to .NET 5!!
Forms             : {}
Headers           : {[Transfer-Encoding, chunked], [Request-Context, appId=], [Content-Type, text/html; charset=utf-8], [Date, Mon, 18 Jul 2016 16:06:00 GMT]...}
Images            : {}
InputFields       : {}
Links             : {}
ParsedHtml        : mshtml.HTMLDocumentClass
RawContentLength  : 19

and got this in my appinsights:

@pragnagopa not seeing an option to merge, what more do we need to do here?

@pragnagopa not seeing an option to merge, what more do we need to do here?

I can go ahead merge once @brettsam  signs off as well! Thanks!

cool, please reach out to me directly if there are any issues in case I miss a GH notification so that we can get this in ASAP due to the number of other PRs relying on it.

@brettsam can you give this one more look over?


Bug in Util.Substitute

begin.txt
main.txt
The method of using Rot13 to do substitutions does not seem to be robust.
Attached are the RS files I was using. This is taken partially from the Eliza template on the RiveScript website.

Expected output: Use: https://www.rivescript.com/try with the Eliza template (the default one) - this shouldn't match anything at all

Fixed tnks for your help
I just leav Rot13 behind and use a indexed placeholder like JS version.


Add Github Action for testing on Windows

See https://github.com/Senzing/template-go/issues/90

Completed via https://github.com/Senzing/move/pull/35


Add new economic parameters functions

Pull request details
Describe the changes made in this pull request
New file, functions, and tests for the economic parameter calculations
List of related issues or pull requests
Closes #826
Collaboration confirmation
As a contributor I confirm

[ ] I read and followed the instructions in README.dev.md
[ ] The documentation is up to date with the changes introduced in this Pull Request (or NA)
[ ] Tests are passing
[ ] Lint is passing

@abelsiqueira we want to use functions for the economic parameter calculations. This is just the first one, but before continuing, we want your feedback on this so that we start replicating it on the other calculations. Thanks!


New versions of protobuf cause build failures

Whenever a new version of the protobuf library comes out, I get an error like the following:
   Compiling crypto-message v1.1.21 (https://github.com/mightybyte/crypto-msg-parser.git#37de71d1)
error[E0425]: cannot find value `VERSION_3_5_0` in crate `protobuf`
  --> /root/.cargo/git/checkouts/crypto-msg-parser-15bfe06dc6f1f762/37de71d/crypto-message/src/proto/message.rs:26:49
   |
26 | const _PROTOBUF_VERSION_CHECK: () = ::protobuf::VERSION_3_5_0;
   |                                                 ^^^^^^^^^^^^^ help: a constant with a similar name exists: `VERSION_3_6_0`
   |
  ::: /root/equitek/mimir/target/debug/build/protobuf-813fda9d6cf24c4f/out/version.rs:7:1
   |
7  | pub const VERSION_3_6_0: () = ();
   | --------------------------- similarly named constant `VERSION_3_6_0` defined here

It looks like this is caused by the use of a specific version on this line: https://github.com/crypto-crawler/crypto-msg-parser/blob/main/crypto-message/src/proto/message.rs#L26
Is there any way something can be done to avoid this error?

@mightybyte you can just specify exact version of protobuf in your cargo.toml as a workaround. Like this:
protobuf = { version = "=3.5.0" }

That does seem to resolve the immediate build issue, thanks!  However, the existence of this constant in the code seems like it will require either the above version override or a code change any time a new version of protobuf is desired.  In the relatively short amount of time I've been playing with this library this has already come up for me multiple times, so maybe it could still be worthwhile to find some way to avoid having the code reference a specific version?  I'll defer to others on whether to leave this ticket open though.  I can see the argument for either side.


We might be using "exports" wrong

I'm getting this error downstream in Name-Suggestion-Index after upgrading location-conflation/country-coder:

The line that triggers the error is:
const iso1A2Code = require('@ideditor/country-coder').iso1A2Code;

I did not expect that by adding "exports" to the package.json that a CJS/require environment would try to use it and pull in a modern ES6 module.
Anyway here is some stuff for me to read later:  https://nodejs.org/api/packages.html#packages_package_entry_points
It might be best to avoid the exports field for now and just keep using the main, module, browser fields.
(This might even be fixed already since the switchover to esbuild - I dont know)

(This might even be fixed already since the switchover to esbuild - I dont know)

This was actually fixed already.
We are doing this now since a18d35a2, which I think is fine for now:
  "type": "module",
  "source": "./src/country-coder.ts",
  "types": "./dist/country-coder.d.ts",
  "main": "./dist/country-coder.cjs.js",
  "module": "./dist/country-coder.esm.js",
  "browser": "./dist/country-coder.iife.js",

which I think is fine for now:

Turns out to be still not fine - "type": "module" will make node treat all .js files as ES modules,
which is wrong for the .cjs.js and .iife.js ones 😭


Tiny usability enhancement: auto focus Name input

As title says. once user clicks the extension icon and the popup shows, to be able to use keyboard straightaway when naming and saving a new tab group.

Nice find @fabd!


docs: update alpha changelog.txt

docs: update alpha changelog.txt
docs: update alpha-v3 changelog

#58  👈
working-trunk

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @juemrami and the rest of your teammates on  Graphite


"crypto.randomUUID is not a function" frontend error on latest Docker build when rendering UI components that use it

Describe the bug
I believe the Vue build is polyfilling crypto with a really old or weird polyfill that doesn't support randomUUID. This means code that expects this to exist (as it does in both modern node and modern browsers) errors.
To Reproduce
Steps to reproduce the behavior:

Go to /default/settings/projects/entity/types?project=default
Open Chrome devtools
See error "crypto.randomUUID is not a function"

Expected behavior
The browser crypto should be used for modern browsers where it doesn't need to be polyfilled. This is breaking functionality of several UI components that I want to use, like the PlaygroundTextBox.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Windows 10
Browser Chrome
Version Chrome/127.0.6533.100

Additional context
I'm not sure what is causing this. I tried rebuilding the docker image with a newer node version (18), but it seems like there are just so many layers of frontend magic here that I will defer to the experts.

https://developer.mozilla.org/en-US/docs/Web/API/Crypto/randomUUID
It's only supposed to work in an HTTPS session. Since your screenshot shows unsecured mode then this is intended behavior.

https://developer.mozilla.org/en-US/docs/Web/API/Crypto/randomUUID It's only supposed to work in an HTTPS session. Since your screenshot shows unsecured mode then this is intended behavior.

Ah, thanks, so the polyfill is behaving as intended. Might be nice for the application to handle cases where it isn't available gracefully instead of partially breaking the UI, but I am able to move forward with my usage of this application after throwing it behind an nginx server with a valid cert.

Glad to hear that fixed it. As far as your suggestion, I'd recommend the other direction. Make it fail a health check and lock the UI to a loading screen telling you to deploy a cert. It's 2024 - port 80 is no longer supported just like ftp and tftp.  They should be outright blocked on any network that remotely believes in the tiniest value of cyber security.


Add PlaintextSize method to Enclaves

The size of the ciphertext of Enclaves is not a secret, and given that we know the size overhead of storing plaintext in an Enclave, it would be useful and more efficient to have a function that returns the size of the plaintext, without needing to create a LockedBuffer and get the size of it's protected bytes.

Not sure why it fails on Windows...

Good idea, thanks for the pull request. I don't know why the test is failing on Windows either, there is no modules.txt file because dependencies aren't being vendored...

I wasn't sure what to name the new method, I like Size though. I was initially worried it would be confusing, as it isn't the true size of the Enclave, but thinking about it some more it makes sense to me. Thanks for adding the test, was going to add that but you beat me to it 👍


Error in phpstan-drupal when running rector

Not sure if belongs to this project but I've filled here because the error is triggered here
I'm using:

palantirnet/drupal-rector: 0.15.0
rector/rector: 0.15.18 (pinned because of https://www.drupal.org/project/rector/issues/3346620)
phpstan/phpstan: 1.10.6
mglaman/phpstan-drupal: 1.1.2

When running any ./vendor/bin/rector process command, I'm getting:
 [ERROR] "PHPStan\ShouldNotHappenException" thrown in
         "vendor/mglaman/phpstan-drupal/drupal-autoloader.php" on line 7 while
         loading bootstrap file vendor/mglaman/phpstan-drupal/drupal-autoloader.php:
         The autoloader did not receive the container.

Due to Rector doing things incorrectly when loading PHPStan extensions.
I haven't looked into it, but I know there is this issue https://github.com/rectorphp/rector/issues/7795

The need to be be in drupal-rector, see comment https://github.com/rectorphp/rector/issues/7795#issuecomment-1465995891
that confirmed at https://github.com/palantirnet/drupal-rector/pull/219#issuecomment-1466829690

Closing this, thanks @samsonasik for fixes in Rector


Refactor list ocm-role to use a map of linked roles

Implementation is similar to the command list user-roles.
This change improves the time complexity of marking the linked roles.

@zgalor @pvasant PTAL

/lgtm


Unexpected behavior of conditional break

From @prandelicious on August 23, 2017 9:42
From @prandelicious on August 23, 2017 4:26

VSCode Version: 1.16.0-insider
OS Version: Windows 8.1 64-bit

Steps to Reproduce:

Create a Python for loop using enumerate():

values = ['Testing1', 'Testing2', 'Testing3']
for index, value in enumerate(values):
    test = index
    print(test, value)

Create a conditional break in line after for index... with value index = 1. Expected behavior is to break when the value of index is equal to 1. It breaks/stops at index = 0

Copied from original issue: Microsoft/vscode#33001
Copied from original issue: DonJayamanne/pythonVSCode#1175

From @prandelicious on August 23, 2017 9:42
From @weinand on August 23, 2017 8:31
Please move this issue to the Python extension you are using. You can use this tool: https://github-issue-mover.appspot.com


feat: enable custom trust anchors for swagger oidc

Also, fix a small docs issue.

This is required for CRC, deployments with a custom trust anchor, used by the Helm charts.


Handle Paystack 5xx errors better

Issue
Paystack 5xx errors especially during the verification of payments break the payment order flow with little feedback to the developer on what went wrong.
Proposed solution
We should be internally retrying on 5xx errors from Paystack, with a limit and a backoff. 5xx errors which occur in spite of these should be logged out better (even without debug mode enabled)

Implemented in #101


Automator: update<EMAIL_ADDRESS>in<EMAIL_ADDRESS>

Generated by Automator - 2022-12-04T04:10:07+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test unit-tests-arm64

integ-basic-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test unit-tests-arm64

integ-basic-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test integ-basic-arm64

release-test_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test release-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test unit-tests-arm64

release-test_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test release-test

integ-basic-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-test_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test release-test

integ-basic-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test integ-basic-arm64

unit-tests-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

wait https://prow.istio.io/view/gs/istio-prow/logs/release-arm64_proxy_release-1.15_postsubmit/1599580810480979968

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test integ-basic-arm64

unit-tests-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test unit-tests-arm64

release-test_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test release-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test integ-basic-arm64

release-test_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test release-test

unit-tests-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_release-1.15
4827e3ecb0502e2337e41fca9aabfad975bdfa0a
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Screenshot is stretched in UI

The image shown in the screenshots tab is horizontally stretched to fit the space, making the image look odd.

Overlaying the stretched version over the original image in Photoshop makes this more apparent:

Yes, the size of the screenshot is set to adjust to the container size to avoid scrolling. I still use the original size to calculate the damage.
The screenshot provided in the tab 'screenshot' here is to just give the user a glance about how the page looks like. I could show the original size for the image in tab `screenshot', but it would be less aesthetic (I think) since it's bigger than the container size.


BitStamp updating OrderBook trouble

I'm starting to implement a data miner based on xchange. As a first step to ensure my implementation, I do these simple steps (based on the examples provided):

Get BitStamp OrderBook (through HTTP API)
Subscribe to WebSocket API to channels LIVE ORDER BOOK and LIVE FULL ORDER BOOK streams.
3)Update original OrderBook with the changes (I've tried updating changes from both or each one only)
4)Get BitStamp OrderBook (through HTTP API) and compare both.

When comparing both OrderBooks, I'm getting differences. The longer I stay connected to the WebSocket API, the bigger the differences are. Therefore, they are not due to changes between getting the OrderBook and connect/disconnect the WebSocket API.
I don't have a clue whats happening, any help would be welcome! :D
Thanks!

@goldaster I don't have any experience with BitStamp streaming so I cannot give any comment based on my experience. Maybe someone else will see this and leave a comment.

@goldaster I'm having trouble understanding what you are comparing.

A potential reason you are seeing a difference between the BitStamp OrderBook on the HTTP API and the streaming Websocket API is that the the HTTP API returns a snapshot of the order book which is cached and only refreshed every 10 secs or so versus real time updates.
E.g. log on to the website and when the order book best bid changes in TradeView keep refreshing  https://www.bitstamp.net/api/order_book/ in a browser to see that it is behind.

@blbradley I'm checking I can keep an updated orderbook adding the updates received through the websocket api. Therefore, I get an orderbook and update it with the websocket api data, and then compare it with a new orderbook.
@Panchen Thanks, this helped!
The problem is solved. I was applying updates without validating the timestamp...


Creating onboarding materials for team

Describe the issue
Creating one page onboarding guide for new team members, and organizing current onboarding material to be more accessible.
Additional context
Based on the workshop we had on team day.
How does this benefit the users of our platform?
Helps make the onboarding process smoother, meaning there's less downtime when a new member joins the team.
Definition of done

[x]  Everyone has access to the drive
[x]  Folder created
[x]  One document guide created
[x]  Acronyms page created

The onboarding guide is created and is located on the Google shared drive / Team Internal / Onboarding.

The onboarding guide is created and is located on the Google shared drive / Team Internal / Onboarding.


chore: give better feedback to users for invalid dendron.yml

chore: give better feedback to users for invalid dendron.yml
This PR:

Allows duplicate entries with readYAML method so that a duplicate mapping doesn't stop initialization

By allowing duplicates, we are overwriting the first entry with the subsequent entries.
Given someConfig: 1, someConfig: 2, someConfig: 3, we now read it as someConfig: 3 instead of throwing an exception.

Add a start-up prompt that detects duplicate mappings in dendron.yml, and give instructions to fix them.

Note

This PR specifically targets to gracefully initialize Dendron even when a duplicate entry exists, and also give better feedback to the users on the issue.
This will also remove a lot of noise that is reported to Sentry.
We should do a proper YAML validation here in the future. I'm limiting the scope here for some immediate benefits.

Preview

Code
Basics

[x] code should follow Code Conventions
[x] circular dependency check: make sure your code is not introducing new circular dependencies in plugin-core.  See Avoiding Circular Dependencies.
[x] sticking to existing conventions instead of creating new ones

eg: if configuration for utilities are already in one module or package, add future utilities there as well

Extended

General

[x] check whether code be simplified
[x] check if similar function already exist in the codebase. if so, can it be re-used?
[x] check if this change adversely impact performance

Operations

[x] when shipping this change, will it just work or will it introduce additional operational overhead due to complicated interface or known bugs?

Architecture

[x] check if code is introducing changes on a foundational class or interface. if so, call for design review if needed

eg: making changes to DNode

Instrumentation
Basics

[ ] if you are adding analytics related changes, make sure you Document changes in airtable

Extended

[x] can we track the performance of this change to know if it is successful?

eg: see usage for export pod

Tests
Basics

[ ] Write Tests
[ ] Confirm existing tests pass
[ ] Confirm manual testing
[ ] Common cases tested
[ ] 1-2 Edge cases tested
[ ] If your tests changes an existing snapshot, snapshots have been updated

Extended

[~] If you are adding a new language feature (graphically visible in VS Code/preview/publishing), an example is included in the test workspace

CSS

[~] display is correct for following dimensions

[~] sm: screen ≥ 576px, eg. iphonex, (375x812)
[~] lg: screen ≥ 992px
[~] xxl: screen ≥ 1600px eg. mac (1600x900)

[~] display is correct for following browsers (across the various dimensions)

[~] safari
[~] firefox
[~] chrome

Docs
Basics

[ ] if your change reflects documentation changes, also submit a PR to dendron-site and mention the doc PR link in your current PR

Basics

[~] does this change introduce a new or better way of doing things that others need to be aware of? if so, an async should be created and a process added in Development or Packages

Close the Loop
Basics
Extended

[~]  is this a developer BREAKING change? if another person cloning from this branch will need to adjust their dependencies or mental model of the architecture, then it is. if this is the case, make sure this is communicated according to Close Loop

eg. breaking dev change due to new dependency

pending:

[ ] tests
[ ] docs
[ ] Airtable entry for new event.

looks good, can we merge according to [[Async Update to Pr Merge Process|dendron://private/user.kevin.journal.2022.05.20.m.async-update-to-pr-merge-process]]?


Non-static functions

In implementing this I have run into numerous issues, but the central issue I'm seeing seems to relate to the fact that all of the functions in src/Alexa.php are public, non-static functions, yet your readme indicates that they should be called statically. You list Alexa::say("Hello") and Alexa::slot('choice') in your readme, but both functions are non-static. Simply changing say() to a public static function resolves the issue for that function, but the slot() function references $this within itself, and therefore cannot be changed to a static function. Are there unpushed commits or something else I am missing here?

Just to check, did you register the facades as outlined here? https://github.com/develpr/alexa-app#2-adding-the-facadesaliases-for-alexa-and-alexaroute-optional - long story short without registering those you wouldn't be able to do things like Alexa::say(..., etc.
I'm guessing you perhaps have, and that the issue is "deeper", but I wanted to double check!

Yes, I did enable the facades in bootstrap/app.php like this:

$app->withFacades();
class_alias(\Develpr\AlexaApp\Facades\AlexaRouter::class, 'AlexaRoute');
class_alias(\Develpr\AlexaApp\Facades\Alexa::class, 'Alexa');

For what it's worth I've forked this repo and made changes on a new branch lumen-5.1.7 so that I am able to use static functions at least in some cases in Lumen 5.1.7: https://github.com/mattrabe/alexa-app/tree/lumen-5.1.7


Can I build tensorboard with Protobuf 2.6.1?

Nope, I think you have to install the version greater than the one in requirement, or it could be wrong while running bazel. Or you might want to install via PyPI then you can walk-around this issue.

@Vogen New Protobuf could be easily installed, this one might help: https://github.com/zihaolucky/tensorboard-distro/blob/master/.travis.yml#L121-L156

Thanks a lot!~


Review request for Set up a "Hello Microverse" project

Create new feature branches.
Followed GitHub flow.
Open pull requests in GitHub.
Write descriptive, easy to understand commit messages.
Write short, detailed, easy to understand descriptions of pull requests.
Write a descriptive and easy to understand README in business English for every project submitted.
Demonstrated an ability to submit a project for code review.

Fixed Linters.


My connection is getting reset if i use serial datatype

When I was trying to load the data in a table which contains serial data type it is resting postmaster.
Here are the steps for reproducing:
Here is our test case:
`test=# \des
List of foreign servers
Name      |  Owner   | Foreign-data wrapper
---------------+----------+----------------------
cstore_server | postgres | cstore_fdw
(1 row)
test=# \det
List of foreign tables
Schema | Table |    Server
--------+-------+---------------
public | c1    | cstore_server
(1 row)
test=# \d+ c1
Foreign table "public.c1"
Column |       Type        |                    Modifiers                    | FDW Options | Storage  | Stats target | Description
--------+-------------------+-------------------------------------------------+-------------+----------+--------------+-------------
id     | integer           | not null default nextval('c1_id_seq'::regclass) |             | plain    |              |
name   | character varying |                                                 |             | extended |              |
Server: cstore_server
FDW Options: (compression 'pglz')
test=# \q
[postgres@localhost ~]$ vi c1.csv
[postgres@localhost ~]$ cat c1.csv
test
test
[postgres@localhost ~]$ psql test
psql (9.6.6)
Type "help" for help.
test=#
test=#
test=#
test=# copy c1(name) from '/home/postgres/c1.csv' WITH csv;
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!> \q
From log file same error what we have seen in you case.
< 2017-12-21 19:30:02.792 IST > LOG:  server process (PID 90463) was terminated by signal 11: Segmentation fault
< 2017-12-21 19:30:02.792 IST > DETAIL:  Failed process was running: copy c1(name) from '/home/postgres/c1.csv' WITH csv;
< 2017-12-21 19:30:02.792 IST > LOG:  terminating any other active server processes
< 2017-12-21 19:30:02.796 IST > WARNING:  terminating connection because of crash of another server process
< 2017-12-21 19:30:02.796 IST > DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
< 2017-12-21 19:30:02.796 IST > HINT:  In a moment you should be able to reconnect to the database and repeat your command.
< 2017-12-21 19:30:02.802 IST > WARNING:  terminating connection because of crash of another server process
< 2017-12-21 19:30:02.802 IST > DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
< 2017-12-21 19:30:02.802 IST > HINT:  In a moment you should be able to reconnect to the database and repeat your command.
< 2017-12-21 19:30:02.833 IST > FATAL:  the database system is in recovery mode
< 2017-12-21 19:30:02.834 IST > LOG:  all server processes terminated; reinitializing
< 2017-12-21 19:30:02.967 IST > LOG:  database system was interrupted; last known up at 2017-12-21 19:22:30 IST
< 2017-12-21 19:30:03.016 IST > LOG:  database system was not properly shut down; automatic recovery in progress
< 2017-12-21 19:30:03.032 IST > LOG:  redo starts at 0/1AC9658
< 2017-12-21 19:30:03.032 IST > LOG:  invalid record length at 0/1ACB380: wanted 24, got 0
< 2017-12-21 19:30:03.032 IST > LOG:  redo done at 0/1AC9658
< 2017-12-21 19:30:03.052 IST > LOG:  MultiXact member wraparound protections are now enabled
< 2017-12-21 19:30:03.066 IST > LOG:  database system is ready to accept connections
< 2017-12-21 19:30:03.099 IST > LOG:  autovacuum launcher started
If I replace serial data type with integer which is not using the sequence to generate the values(automatically) then we are not facing this issue.
test=# create foreign table c1 (id int,name varchar) SERVER cstore_server
OPTIONS(compression 'pglz');
CREATE FOREIGN TABLE
test=#
test=#
test=#
test=# copy c1(name) from '/home/postgres/c1.csv' WITH csv;
COPY 3
test=# select * from c1 ;
id | name
----+------
| test
| test
|
(3 rows)`

hi @rmadiwaledba
thanks for the report, I can reproduce it in our end.
looks like our copy code does not play nice with serial fields.
As you stated, copy works when you do not have a serial field.  As a workaround, you can copy data into a regular postgresql table, and insert into cstore table using insert into cstore_table select * from regular_table.
We will look into fixing this in our next release.

Yes, correct it is not handling the serial data types.

Can it be declared as bug?

yes, it is a bug


Valid URLs can use ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0...

...123456789-._~:?#
Sorry I didn't try out the regex changes earlier but apps are actually using urls with commas in them (which are technically valid).
Ex: twcweather://TenDay/33.89,-84.46?aw_campaign=com.weather.TWC.TWCWidget

@zimmpatrick Great catch! We should have a test case around this.


Build Sustaining > Policies

Revise policies section of Sustaining site to include:

Commons bylaws
Terms of Service
Privacy Policy
Guidelines for Participation?

This also looks good. I wonder if we should update the links in the footer to point to these so that we don't have to try to remember to do updates in both places?

YES, definitely! I want these docs to live in ONE place if at all possible!


feat: add Zora Testnet 1.3.0 contracts

Relevant issue: https://github.com/safe-global/safe-deployments/issues/368

thanks for merging this in @ElvisKrop ! do you think you could publish this updated package to npm?  Thank you

Hello @oveddan :wave:
Actually, I don't have any impact on this package. I'm just a contributor and Safe team kindly accepted my changes :raised_hands:
This repo has a monthly release cycle and I believe that in next 1-2 weeks Safe team will publish a new version to NPM including changes from this PR.


Updating dependencies

new versions of md5, hyper-tls, uuid.
generally switching to x.x versions.

Thank you!


FirebaseCore/Sources/Private/FirebaseCoreInternal.h' file not found

Failed to build iOS app
Error output from Xcode build:
↳
** BUILD FAILED **
Xcode's output:
↳
/Users/lizh/Desktop/flutter/flutter_skype/ios/Pods/FirebaseAuth/FirebaseAuth/Sources/User/FIRUser.m:20:9: fatal
error: 'FirebaseCore/Sources/Private/FirebaseCoreInternal.h' file not found
#import "FirebaseCore/Sources/Private/FirebaseCoreInternal.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/lizh/Desktop/flutter/flutter_skype/ios/Pods/FirebaseAuth/FirebaseAuth/Sources/User/FIRUser.m:20:9: note: did
not find header 'Sources/Private/FirebaseCoreInternal.h' in framework 'FirebaseCore' (loaded from
'/Users/lizh/Desktop/flutter/flutter_skype/build/ios/Debug-iphonesimulator/FirebaseCore')
1 error generated.
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
warning: Mapping architecture armv7 to i386. Ensure that this target's Architectures and Valid Architectures build
settings are configured correctly for the iOS Simulator platform. (in target 'image_picker' from project 'Pods')
warning: Mapping architecture arm64 to x86_64. Ensure that this target's Architectures and Valid Architectures build
settings are configured correctly for the iOS Simulator platform. (in target 'image_picker' from project 'Pods')
Could not build the application for the simulator.
Error launching application on iPhone 8.

Hi @lizhaobomb
Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample
Thank you

Hi @TahaTesser
this is flutter doctor -v
[✓] Flutter (Channel stable, v1.17.2, on Mac OS X 10.15.5 19F101, locale zh-Hans-CN)
    • Flutter version 1.17.2 at /Users/lizhao/opt/flutter
    • Framework revision 5f21edf8b6 (3 weeks ago), 2020-05-28 12:44:12 -0700
    • Engine revision b851c71829
    • Dart version 2.8.3

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/lizhao/Library/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = /Users/lizhao/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4, Build version 11E146
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.46.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (1 available)
    • iPhone 8 • 7CBE8738-4B53-4205-A41A-9970CFC27ADA • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-4 (simulator)

• No issues found!

this is  flutter run --verbose
error_log.txt
and pubspec.yaml
  firebase_auth: ^0.16.1
  google_sign_in: ^4.5.1
  cloud_firestore: ^0.13.6
  shimmer: ^1.1.1
  gradient_app_bar: ^0.1.3
  emoji_picker: ^0.1.0
  image_picker: ^0.6.7+2
  path_provider: ^1.6.11
  firebase_storage: ^3.1.6

and Podfile.lock
Podfile.txt
Thank you

Hi @TahaTesser
[and this is my project repository you can try]
(https://github.com/lizhaobomb/flutter_skype)

Hi @TahaTesser is there anything i didn't done？any advice is super appreciate

Hi @lizhaobomb
You probably missed AppDelegate.swift, please add firebase to this class and FirebaseApp.configure() and run your app
import UIKit
import Flutter
import Firebase

@UIApplicationMain
@objc class AppDelegate: FlutterAppDelegate {
  override func application(
    _ application: UIApplication,
    didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
  ) -> Bool {
    FirebaseApp.configure()
    GeneratedPluginRegistrant.register(with: self)
    return super.application(application, didFinishLaunchingWithOptions: launchOptions)
  }
}

i just added that and ran your app, it runs and also builds

flutter doctor -v
[✓] Flutter (Channel dev, 1.20.0-1.0.pre, on Mac OS X 10.15.5 19F101, locale
    en-GB)
    • Flutter version 1.20.0-1.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision f73f498da1 (8 days ago), 2020-06-18 08:23:22 -0700
    • Engine revision c0d52b98d1
    • Dart version 2.9.0 (build 2.9.0-16.0.dev 2b917f5b6a)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.46.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (6 available)
    • SM M305F      • 32003c30dc19668f                     • android-arm64  •
      Android 10 (API 29)
    • Taha’s iPhone • 00008020-001059882212002E            • ios            •
      iOS 13.5.1
    • iPhone 11     • 0EC80516-8F99-4A0C-89ED-2273579862F9 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-13-5 (simulator)
    • macOS         • macOS                                • darwin-x64     •
      Mac OS X 10.15.5 19F101
    • Web Server    • web-server                           • web-javascript •
      Flutter Tools
    • Chrome        • chrome                               • web-javascript •
      Google Chrome 83.0.4103.116

• No issues found!

hi @TahaTesser thanks for your suggestions，but unfortunately this doesn't solve my problem，
and I want to tell you that i ran into this problem by suddenly, i mean in the beginning all things goes well， on one day it can't run, maybe the cocoapods has somethings wrong ... please forgive my poor english

hi @TahaTesser when i new a purely native ios project with the podfile
  use_frameworks!

  # Pods for FirebaseDemo
  pod 'Firebase/Auth'
  pod 'GoogleSignIn'
  pod 'BoringSSL-GRPC'
  pod 'gRPC-C++'

or maybe i just comment the statement use_modular_headers  in the podfile in the flutter project
the problem has gone，i don't know why, anyway Thanks a lot, i will close the issue


Download speed 16 kB/s

Problem
Run:
curl https://sh.rustup.rs -sSf | sh
and accept default installation.
Download speed for all packages will be max 16 kB/s.
Home Internet connection is 600/60 Mb/s.
Steps
No response
Possible Solution(s)
No response
Notes
Run on Macbook Pro M2 Pro with 16 GB of RAM and Wi-Fi 5 connection.
Version
No response

We are not able to help due to the lack of a minimal set of steps to reproduce. Here are tips about how to create a minimal, complete, and verifiable example. It is unclear what "all packages" refert to. Looks like a rustup or network connection issue to me.


Block duplicated events

Mix DuplicateBlocker in ManageIQ::Providers::BaseManager::EventCatcher::Runner to block duplicated events when there are too many duplicates in a short time.

Split  process_event(event) into filtered?(event) and queue_event(event)
Monitor queue_event(event). Do not place the event to the queue if the event is considered a duplicate that exceeds the count threshold.
Every provider's EventCatcher::Runner needs to implement event_dedup_key(event). It should generate an object that helps to distinguish whether an event is a duplicate. For example in the VMware implementation, timestamps and sequence numbers are removed while other event contents are preserved.
Every provider's EventCatcher::Runner needs to implement event_dedup_descriptor(event). It should return a string to describe an event, not only the event type, but other details. The string will be logged to tell the user what event has been blocked due to too many duplicates.
Parameters such as time window to monitor and duplicate count threshold are initialized in event_handling.tmpl.yml under workers/worker_base/event_catcher/defaults. These parameters are valid for all providers. However each provider can overwrite each particular parameter. By default the blocking feature is disabled. User needs to turn it on.
With this PR event_dedup_key(event) and event_dedup_descriptor(event) are implemented only for VMware. Additional work should be done to other providers.
Added spec tests.

@miq-bot rm_label wip

@blomquisg please review

@blomquisg bump - please review

@bzwei please rebase and push again

@durandom can you look this over.  I've glanced at it and I really want this.  But, I want to make sure that you've had eyes on it first.

@bzwei please rebase and push again
@blomquisg darga?

@bzwei could you please rebase and push again

@bzwei can you please address the Rubocop issues and repush?

@bzwei sorry, the removal of amazon requires you to PR against two repos :(
But you can cherry-pick. Configure your repo as a remote and cherry-pick with Xsubtree
~/src/manageiq-providers-amazon master
❯ git remote -v
manageiq_upstream       git@github.com:ManageIQ/manageiq.git (fetch)
manageiq_upstream       git@github.com:ManageIQ/manageiq.git (push)
❯ git cherry-pick -Xsubtree=gems/manageiq-providers-amazon <sha>

@blomquisg @chriskacerguis @gmcculloug please move this forward. Since process_event splits into queue_event and filtered?, every provider needs to override these methods. While this PR remains open, we need to sync with newly added provider and with provider moving into a separate gem.

@bzwei I think this would be easier to merge, if it would only impact one provider.
Afaiu the code, deduping is only implemented for vmware.
Would'nt the other providers just continue to work as they are, just without deduping?
If so, how about spliting those changes into follow up PRs where we can include the respective teams into the review?

@durandom The core change is to split proces_event into filtered? and queue_event at base, and dedup queue_event at base level too. This requires each provider to implement queue_event and filtered?. If we don't split, we have to dedup process_event, which requires an analysis of filtered events whether they are duplicates. Why bother to analyze an event that we are not interested or don't have knowledge about?
It is a pain the splitting causes some merging challenges. It is still worth if the splitting makes sense.

This requires each provider to implement queue_event and filtered?

Maybe I get it wrong, but if a provider

still implements process_event or
has no flooding_monitor_enabled configured

then it would still work as expected.
Nevertheless I can look at the changes you introduced to the other providers

@durandom You are right. I neglected the fact that even though I refactored process_event in the base, the subclass can still override it with the old implementation. Although it does not look good, it helps to migrate to the new feature provider by provider.
I am going to close this PR and open two new PRs. One for base change, the other for sample implementation for VMWare. Then other providers can refactor following the example of VMWare.

@bzwei :+1: smaller PRs for the win :)


[WIP] Initial changes to migrate ocmd to reva

Migrating the OCM service from https://github.com/cernbox/ocmd to reva. Still a work in progress.

@ishank011 take a look at the lint from the CI for some optimizations

Creating new PR


Investigate using another test runner

Jest is kinda slow, and I'm not sure if it's currently maintained at this point. It'd be worth looking into another test runner, especially if there's one that integrates a decent amount of assertions as well as checking coverage.

Some ootential options:

ava
mocha, probably with chai
vitest


Added read more button to the back side of the service card 1418

Added read more button to the back side of the service card. This will make redirection to the page easier when back side is visible

@anuragverma108  please review this pr and let me if any changes required
Thank you

@alokdwivedi103 Please add SS

Added @PriyaGhosal please check and let me know if i have to make further changes
Thank you.


$select System Query Option - issue

Request URL : http://localhost:8080/myservice.svc/PersonNames?$select=last_name

<metadata:error xmlns:metadata="http://docs.oasis-open.org/odata/ns/metadata">
metadata:code1800</metadata:code>
metadata:messageThis type of option is not supported for queries: SelectOption(List(PathSelectItem(None,TerminalPropertySelectPathSegment(last_name))))</metadata:message>
</metadata:error>

Current implementation of Query builder does not support $select operation.
Marked as enhancement so that it can be picked up at later stage.


add new Claude 3.5 Haiku to Anthropic pipeline

https://docs.anthropic.com/en/docs/about-claude/models

Thanks!


Externalize geth

• Remove Geth from repo
• Get geth if needed as part of target build phase and pod prepare

i approved because my requests are minor. please prove in a future pr


Headers Support

Hello,
Seems like Headers are not saved in the Kafka Server (which is a new feature of Kafka 0.11). Would it be possible to take a look ?
Edit : I guess the EmbeddedKafka.publishToKafka method should take an Map-like extra parameter for record headers and the "message" value in consumer method should handle the record headers in order to provide it in return.
Thanks ;)

Instead of passing more and more parameters, consider exposing a method with kafka producer record as single parameter.


Added static library build target

By default the Makefile now builds a static library target in the main directory. The .o files have been added to the clean target.
Related to issue #404

I'm currently ill but I'll look into it probably after the weekend. Even though it results in a statically linkable file I get an awful lot of 'undefined reference' errors when attempting to use it in my CMake project so I'm going to investigate that as well.

Okay so I attempted to use the static library target http://pastebin.com/ATWPp98y but the result is the same. It apparently doesn't matter if I add only uWS.h or all .h files in the include directory.
I also attempted to link test.cpp against the shared library created by the Makefile and it doesn't compile as well so the problem doesn't appear to be related to the static target only http://pastebin.com/qgSU37TB.

I just read through the CMakeLists.txt and it might be possible that the library is not linked against the OpenSSL and zlib

Since the Makefile appears to be missing the OpenSSL and zlib dependency yet and I personally prefer using CMake, I created a new pull request that modified the CMakeLists.txt to produce a static target as well as making using some very handy configuration variables. Just for reference it's #417, I'll open an issue regarding the flaws in the Makefile


ERROR: S3 error: 403 (AccessDenied): Access Denied on upload files

Hello
when try to upload files more than 15MB i see this error on s3cmd command:
/usr/bin/s3cmd abortmp s3://test/100 -GQJNXtpQmC1Z5I11KkFBQ==
to abort the upload, or
/usr/bin/s3cmd --upload-id -GQJNXtpQmC1Z5I11KkFBQ== put ...
to continue the upload.
ERROR: S3 error: 403 (AccessDenied): Access Denied
on riack-cs acces log i see this:
"PUT /buckets/test/objects/100/uploads/-GQJNXtpQmC1Z5I11KkFBQ==?partNumber=1 HTTP/1.1" 403 167 "" ""

Hello
i change  this line:
multipart_chunk_size_mb = 15
in my s3cfgfasttarck file and problem solved

@j4b3r - thanks for the follow-up explaining your fix - much appreciated.


testduplicate model storage layer regression-test

Proposed changes
Issue Number: close #9284
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

LGTM


Title Only

Why not can we set NavigationTabBar title-only ?

Hello. Thanks for question. Its not possible in this realization and dont accept the ntb guidelines. Try to use out another library NavigationTabStrip which have more classic design.


UpCloud: http 404 ,VidCloud: http 404

Description
Some times When click play it shows http errors 404 on both servers

Provider
SFlix
Reproduction steps
Some times When click play it shows http errors 404 on both servers
Operating system
No response
Logs
UpCloud: http 404
VidCloud: http 404

Please confirm the following

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] If related to a provider, I have checked the site and it works, but not the app.

The same was fixed just a couple of days back and now it appears again.
Please rectify it.

Both Sflix and TMDb providers.
It just got updated a few days ago and it was working perfectly. What's going on?

Both Sflix and TMDb providers.
It just got updated a few days ago and it was working perfectly. What's going on?

Correct and everything was working perfectly after the update. However, it seems the issue has returned. 😕

Same with all server

Doesnt work for all servers

Fournisseurs Sflix et TMDb. Il vient d'être mis à jour il y a quelques jours et il fonctionnait parfaitement. Que se passe-t-il ?

aujourd'hui streamflix plante avec la version 1.74 installée hier le 8/9/24 aujourd'hui aucun film ou séries ne marche toujours erreur http 400


Feature Request: Function is exposed indicator

Some type of indicator on the function that is exposed at the top of the module would be useful.  This is in reference to https://groups.google.com/forum/#!topic/elm-discuss/N_Pd1XsgtwU where they are discussing visibility of the exposed list.  Keeping it at the top is sensible to see them all in one place, but it is also nice to see it at the function declaration too, so some indicator that it is so would be nice (Like color-coding it differently I'd say).

@OvermindDL1, this is available in https://atom.io/packages/elm-lens :slightly_smiling_face: