clang::Type::template_arg_type should return an Option

It isn't clear from the documentation whether or not an invalid type is returned by the FFI call if this type is not a template specialization. We should check whether or not it is, and if it is not return None. We should also bounds check the i parameter.
It will be useful to do this in the method so that every caller doesn't have to remember to do it. One less foot gun!
http://clang.llvm.org/doxygen/group__CINDEX__TYPES.html#ga9645640281c8d088982b2133f58edcb3
I can mentor whoever picks this up.

Please make a comment here if you intend to work on this issue. Thank you!

Would it be appropriate to use iterator here instead as suggested for comment children, attributes here #166 ?

If we go the iterator route, we can avoid the bounds checks, yes. However, if we do that we should also stop exposing an API to get the nth argument (unless we want to add bounds checks for that API, or use Iterator::nth).

Yes, we should remove the template_arg_type and likely the num_template_args API.
There is a small trickiness compared to PR #169 for issue #166.
The number of argument is an optional, but it seem the following interface:
pub fn template_args(&self) -> Option<TypeTemplateArgIterator> (is it idomatic?)
would replace both:
pub fn num_template_args(&self) -> Option<u32>
pub fn template_arg_type(&self, i: u32) -> Type
we use the number, but I don't know if it result in better code than having a single iterator interface.
In PR #169, I feel switching to iterator resulted in simpler calling code.
Regarding getting thenth argument, if it turned out we needed it, we could provide an efficient:
pub fn template_args_from(&self, u32 index) -> Option<TypeTemplateArgIterator>.  (is it idomatic?)

pub fn template_args(&self) -> Option<TypeTemplateArgIterator> (is it idomatic?)

Either that, or return an empty iterator that doesn't yield any items. I kind of prefer returning an Option since it more straighforwardly conveys that template_args on a non-template specialization doesn't even make sense.

switching to iterator resulted in simpler calling code.

Yes, for sure.

Regarding getting thenth argument, if it turned out we needed it, we could provide an efficient:

I think using https://doc.rust-lang.org/nightly/std/iter/trait.Iterator.html#method.nth is fine if we already have iterators.


1D histograms in cornerplot use 2 sigma quantiles by default

I noticed that the default for dynesty's cornerplot is to plot 2-sigma quantiles (0.025,0.5,0.975). Should we made the 1D hists 1 sigma ?
Easy fix that I can roll into #37.

Closed by #37.


samedsay: deliverable

[x] Create this issue
[x] Install softwares
[x] Install VSCode extensions
[x] Organize your computer
[x] GitHub setup
[x] Submit student bio PR
[x] Fork and Clone the flashcards repository
[x] Prep work for Workflows Chapter 1

First issue with the deliverable label is done as I suppose.


EOF when reading a line

Hey,
I don't know if you'll love me for helping debug your script or if you'll hate me for constantly asking for help. Hopefully rather the first option :)
So I ran the script successfully over the last few days and 2 day ago I started seing some 'EOF when reading a line' in my mail reports. This happened more or less when 100% of my files had been uploaded, so maybe it's linked to the fact that there is no new file to upload (or not at all, I'm just giving as much info as I can)
I didn't try adding 1 new pic and running it again but I could if you think it might help.
Also a few days ago I launched the script by clicking on "Execute" on the Scheduler interface rather than letting it launch at the specified time. I just wanted to mention it since it seemed to make a difference when I had my PATH problems.
Here are the logs with modified keys and tokens (if I didn't miss any ^^):
uploadr.err.txt
uploadr.out.txt
Hope this helps.
Kind Regards,
Ze

No... definetely thank you for helping debug and also for your message from a few days ago. Appreciate it.

What is happening is that for some reason the Flickr authorization token is not valid anymore and a new one is required. From uploadr.out we have...

[uploadr] Checking if token is available... if not will authenticate
[uploadr] Getting new token.
https://www.flickr.com/services/oauth/authorize?oauth_token=YYYYYYYYYYY-XXXXXXXXXX&perms=delete
Verifier code (NNN-NNN-NNN):

To get a new toekn you have to first run the script at least one time manually in a ssh client to get an URL which you have to copy/paste in a browser... and once you get a return code provide it to the uploadr tool. You should be good to go.

Let me know if it works.
oPromessa

Hello,
That seems to have solved it, thx!
Should I expect this to happen from time to time or is it most probably me who did something wrong?
(I know I tend to go into clicking frenzies where I don't know or care what I'm doing :)
Ze

I found it may happen from time to time... but it is not frequent... say once every 4˜5 months or so...


uncomment css optimization

Closes #34

@Trung-Dev I commented that out because it was broken for me. Does it work for you?

Closed it because it was a duplicate from one of the fixes I did


Add ability to change Registry

At minimum, it needs to be possible to change registry for alpha/beta testing, but it's also a big thesis of the company that the ability of someone else to host a Marketplace at least be available
Reported by: @kn0wmad

The broader story here is captured in #435. I'm closing this as a duplicate since the hackable version is already available in embassyd today.

there is no easy way to change this rn. It is not done with config, but requires editing patch-db. reopening to add an rpc command to change it.

Is there any reason we can't just seed patch-db with a config override if it exists?

yeah but I don't see why that would be any easier

I think it's important to support changing the marketplace URL, similar to how we do it in 0.2.x. Right now, this is less about supporting alternative marketplaces as a means of reducing dependency on Start9 (which we all agree is important) and more about being able to use our own alternative marketplaces (alpha, beta). I personally have needed to make this switch every time we release anything new.

Yeah, to be clear the facilities exist already, we just don't have any effective way to do it from the CLI or UI. Should be a very easy change to make.


Update the Runbook rb-wcnp-aks-cluster-automation-dev to fix Restart Issue

Overview:
Update the Runbook rb-wcnp-aks-cluster-automation-dev, and rb-wcnp-aks-cluster-automation-pre located within rg-wcnp-firewall-automation-dev, and rg-wcnp-firewall-automation-pre to make sure StartCluster is accessed.
Resource Groups:

rg-wcnp-firewall-automation-dev
rg-wcnp-firewall-automation-pre

Runbooks:

rb-wcnp-aks-cluster-automation-dev
rb-wcnp-aks-cluster-automation-pre

These runbooks currently have a condition within them that prevents the powershell command Start-AzAksCluster from being executed.

Instead of having "Stopped" being checked, it will simply call the Start_AzAksCluster if state isn't "running"

I have updated the following:
Changed the schedules for all AKS start jobs to use Coordinated Universal Time and set the time for starting at 2:01 PM UCT which translates to 9:00 AM EST.

I have set each to look like the following example with their specifics (name/resource group) not changing:

The runbook rb-wcnp-aks-cluster-automation-dev

There was no PR for this as the Runbook only existed at the time in the portal.


Accessing field.RelationField outside of query instance in repository layer

Your Question
Is there a way to access field.RelationField outside of the query instance in the current generated code by gorm.gen?
We want to implement a repository method that accepts field.RelationField as variadic arguments for flexible preloading, like this:
func (r *userRepository) GetUserWithPreloads(ctx context.Context, id uint, preloads ...field.RelationField) (*model.User, error) {
    query := r.q.User.WithContext(ctx).Where(r.q.User.ID.Eq(id))

    for _, preload := range preloads {
        query = query.Preload(preload)
    }

    return query.First()
}

Currently, it seems we can only access field.RelationField through the query instance (e.g., query.User.Posts.RelationField). Is there any way to get these relation fields without the query instance, or is there an alternative approach we should consider to achieve flexible and type-safe preloading in the repository layer?
The document you expected this should be explained
https://gorm.io/gen/
Expected answer
We're looking for either:

A way to access field.RelationField without using the query instance in the current generated code.
An alternative approach to implement flexible and type-safe preloading in the repository layer using gorm.gen.
Confirmation that this is not possible with the current implementation, and whether there are plans to support this kind of usage in future versions.

Thank you for your assistance.

I’ve just encountered the same issue, did you find a solution to this?
Thanks


[Performance] Feature/workforfullframe

Some of the modtek workloads are very light, and end up consuming far less than a full frame worth of time to process.  Due to the progress report only processing one item per frame this ends up with some lost time.
Currently, this fix only reduces load times by about 3.5s with a RogueTech install, but every little bit helps.

This seems sensible. Are we ready to pull the trigger on this?


How can I run it?

Hello. I haven't used nodejs before. I have compiled it without any problem, but how can I run it?
I think it should be in readme

(This is similar for most GitHub projects, especially HTML-based ones)

Go to Releases page:

Download latest release ZIP:

(Optional, recommended:) put the files onto a CD or a flash drive or whatever and spin up a burner OS

Open the newest release under web/

Voilà

(The above is if you just want to run/use it. It's also included in BitKey, which is how I use it to actually make a wallet)
If you're wanting to hack on it for development, you'll probably have to muck around with Makefiles and Cakefiles and Node and development frameworks and all the rest of it, though.


Update Airflow lineage to append tasks

Airflow lineage backend only discovers one task at a time.
After fixing https://github.com/open-metadata/OpenMetadata/issues/2224, we should have another round on the backend to append the current task to the Pipeline.
We should also try to think on a clean step on how to react (and discover) if a task has been removed.

As we'll be playing with the lineage backend, let's as well ingest the status info and check if we can configure failure callback in airflow.cfg

Followup of https://github.com/open-metadata/OpenMetadata/issues/2226


ERROR: for dnsmasq  Cannot start service dnsmasq: Ports are not available: port is already allocated.

Hello,
i want to use Warden, but i get this Error.
ERROR: for dnsmasq  Cannot start service dnsmasq: Ports are not available: port is already allocated.
ERROR: for dnsmasq  Cannot start service dnsmasq: Ports are not available: port is already allocated.
ERROR: Encountered errors while bringing up the project.
Thanks for help!

@MaybachDomei That error would be coming from Docker and basically means exactly what it says, some other server is is listening on the DNS port 53.
You can run the following to see what's listening on port 53:
sudo lsof -nP -iUDP | grep :53

On my system the following line shows up and is present as the dnsmasq container is running and listening on this port (this is what docker is failing to configure on your machine right now):
com.docke 71651     davidalger   49u  IPv4 0x471d5907ceb434ad      0t0  UDP <IP_ADDRESS>:53

If you're a former user of Valet, or other Homebrew based environments, you might try checking to see if brew is running anything like dnsmasq, unbound, as an artifact of the prior environment setup: sudo brew services list


[Bug]: NPE in join clause

Description
Following code gives NPE
import ballerina/io;

type User record {|
    readonly int id;
    string name;
|};

type Login record {|
    int userId;
    string time;
|};

public function main() {
    table<User> key(id) users = table [
        {id: 1234, name: "Keith"},
        {id: 6789, name: "Anne"}
    ];

    Login[] logins = [
        {userId: 6789, time: "20:10:23"},
        {userId: 1234, time: "10:30:02"},
        {userId: 3987, time: "12:05:00"}
    ];

    string[] loginLog = from var login in logins
                        outer join var user in users
                        on login.userId equals user.id
                        select user.name + ":" + login.time;

    io:println(loginLog);
}

Stacktrace
Compiling source
        outer_join_clause.bal

Running executable

[2022-10-25 13:23:12,585] SEVERE {b7a.log.crash} - null
java.lang.NullPointerException
        at outer_join_clause.$streamLambda$_4(outer_join_clause.bal:31)
        at outer_join_clause.$streamLambda$_4$lambda4$(outer_join_clause.bal:31)
        at ballerina.lang$0046query.0.$value$_SelectFunction.process(types.bal:623)
        at ballerina.lang$0046query.0.$value$_SelectFunction.call(types.bal)
        at ballerina.lang$0046query.0.types.$gen$$anon$method$delegate$_StreamFunction$0046process$0(types.bal:91)
        at ballerina.lang$0046query.0.$value$_StreamPipeline.$gen$$anon$method$delegate$_StreamFunction$0046process$0$lambda0$(types.bal)
        at io.ballerina.runtime.internal.scheduling.SchedulerItem.execute(Scheduler.java:569)
        at io.ballerina.runtime.internal.scheduling.Scheduler.run(Scheduler.java:303)
        at io.ballerina.runtime.internal.scheduling.Scheduler.runSafely(Scheduler.java:270)
        at java.base/java.lang.Thread.run(Thread.java:834)

error: java.lang.NullPointerException
        at outer_join_clause:$streamLambda$_4(outer_join_clause.bal:31)
           ballerina.lang.query.0._SelectFunction:process(types.bal:623)
           ballerina.lang.query.0:$anon$method$delegate$_StreamFunction.process$0(types.bal:91)

Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

This should be fixed with https://github.com/ballerina-platform/ballerina-lang/pull/38232. @ushirask please verify

Duplicate of #34897
#38232 will solve the NPE issue, however the above code segment will not be correct since we'd have to use select user?.name + ":" + login.time and we cannot concatenate string and string? and will have to be handled accordingly.

Duplicate of #34897


Avoid models being refreshed too often

When opening a model, it seems the model is refreshed twice. Check the debouncer

Related to #132


ToC does not match menu

See attached screenshots

L2 Headers (what we call that top nav) have to be submitted to a different repo for publish so there is a delay in updating it after we update the main site. Looking now, the new L2 header is live. It isn't designed to be exactly 1 to 1 of what the side nav has, but interested in feedback.

closing issue as I believe the original ask has been resolved.


Can't get attach to work

I tried to make query that involves tables from two different databases, however i cannot get sqlite attach to work properly even though debug message says the database is attached successfully.
Expected Behavior

Using attach I can make query involving multiple databases
Current Behavior

Cannot select table from the attached database
Possible Solution

Steps to Reproduce (for bugs)

    let queryResults = [];
    await SQLite.openDatabase(
      { name: 'second.db', createFromLocation: 1 },
      () => console.log('success open second database'),
      () => console.log('failed to open second database'),
    );
    const dbMaster = await SQLite.openDatabase(
      { name: 'master.db', createFromLocation: 1 },
      () => console.log('success open master database'),
      () => console.log('failed to open master database'),
    );
    dbMaster.attach(
      'second',
      'second',
      () => console.log('second is attached successfully'),
      () => console.log('error attaching second'),
    );
    dbMaster.readTransaction((tx) => {
        tx.executeSql(
          `select * from second.translation where id = ${id}`,
          [],
          (tx, results) => {
            const rows = results.rows.raw();
            rows.forEach((row) => {
              queryResults.push(row.text);
            });
          },
        );
      }),

Context

I got the following error suggesting that the attached table cannot be read:
Object {
  "code": 0,
  "message": "no such table: second.translation (code 1 SQLITE_ERROR): , while compiling: select * from second.translation where id = 1",
}

If my query only involves master database, it works fine but everytime I access table from the attached database (second database), I get that error. I tried to follow code given in example directories of this library but still the same result
Your Environment

React Native SQLite Storage Version used: "^3.3.10"
React Native version used: "0.59.5"
Operating System and version (simulator or device): android device & simulator

Debug logs

Database master is successfully opened
D:\rn\masterApp\node_modules\react-native-sqlite-storage\lib\sqlite.core.js:328 ATTACH database second to master.db with alias second
D:\rn\masterApp\node_modules\react-native-sqlite-storage\lib\sqlite.core.js:86 SQLite.attach({"path":"master.db","dbName":"second","dbAlias":"second"})
D:\rn\masterApp\node_modules\react-native-sqlite-storage\lib\sqlite.core.js:131 new transaction is waiting for open operation
D:\rn\masterApp\node_modules\react-native-sqlite-storage\lib\sqlite.core.js:86 SQLite.backgroundExecuteSqlBatch({"dbargs":{"dbname":"master.db"},"executes":[{"qid":1111,"sql":"SELECT 1","params":[]},{"qid":1111,"sql":"select * from second.translation where id = 1","params":[]}]})
D:\rn\masterApp\src\utils\Database.js:65 Database is attached successfully
D:\rn\masterApp\node_modules\react-native-sqlite-storage\lib\sqlite.core.js:576 warning - exception while invoking a callback: {"code":0}
D:\rn\masterApp\node_modules\react-native-sqlite-storage\sqlite.js:66 error:  readTransaction ƒ (tx) {
            tx.executeSql("select * from second.translation where id = " + id, [], function (tx, results) {
              var rows = results.rows.raw();
              rows.forEach(… Arguments [{…}, callee: ƒ, Symbol(Symbol.iterator): ƒ]
D:\rn\masterApp\node_modules\react-native\Libraries\YellowBox\YellowBox.js:67 Possible Unhandled Promise Rejection (id: 0):
Object {
  "code": 0,
  "message": "no such table: second.translation (code 1 SQLITE_ERROR): , while compiling: select * from second.translation where id = 1",
}

any help for this issue? @andpor

Hi @nastarfan, I know it has been 6 months but I'm facing the same issue; I've been trying to attach a simple database for more than 16h; I can do it from the terminal inside the adb shell command, but using the library returns the same error as you showed.
Any solution on this?

I have some news on this. I was just testing on android, but apparently iOS works just fine, and on android the attach method is not working properly for some reason.
Needs more investigations. I'll post it here if I discover something.

I got it working, the library works just fine, the problem is that we need more info into the documentation.
(btw, the problem was on Android, iOS works  with no problem, but this fix will work on both platforms)
I discovered the problem by looking at this line right here:
https://github.com/andpor/react-native-sqlite-storage/blob/master/platforms/android/src/main/java/org/pgsqlite/SQLitePlugin.java#L509
The first argument needs to be the FULL PATH, including the filename with the extension.
case background:
My case was that the app downloads a pre populated database, and I'm using this library to connect to the varios databases that were being downloaded so I can attach to them forming one big database.
React 16.9
RN: 0.61.1


chore: removing CODEGEN_BIN rule

changing order of all rule to build, test and then check
reducing verbosity of output
removing unused variables

Ah, nice. I'll pull this in.


Data model diagram update

We need updated data model diagrams for release 2.1 (renaming the objects to the new naming scheme)

removed milestone, cos I am lazy and want the release done now. the diagram is not important enough vs the impending version release which will stop OQS from potentially hurting system performance.


Draft for adding agents without connection to sat.

Create certificate for agent on satellite
Use satellite to sign certificate on upstream systems
transport certificate and key to agent

Hi, as discussed on the side. This is a very specific edgecase. And can be "easily" done with pre_tasks to create certificates and deploy them on the agent directly.


Invalid Dashboard link value in header

Currently contains href value of "https://paynow.gg/dashboard" but has to contain "https://dashboard.paynow.gg/"

Fixed, thanks!


Modularize it!

Break this library into multiple parts:
Thing: (new repo)

Specify metadata via fluid API as well as TypeScript decorator syntax.
Creating random values and objects (no dependencies/relationships).

Stuff: (this repo)

Define relationships between data.
Create and run tasks to inject data into receiver.

Maybe not...


Scalatest 3.0.1 --> 3.0.5

ping @bdarfler

Hi, @sullis I'm not as active with this project anymore. I'd ping @jsolmon

ping @jsolmon


Add python2 support to platformsh installs for #11

It seems that python2 is installed as platform in most platform VMs, so add that. Even when not explicitly used, it may be used in things like yarn install

#11 : With this we have modest support for python2 and building python2 extensions.

To test this, use ddev get https://github.com/rfay/ddev-platformsh/tree/20220822_python2_support/tarball

Rebased

Thanks for the heads up @rfay!
I understand the cost of building, let's discuss this.

We're not going to support python2


Add kernel printf util for debugging

Noting that Triton already has support for printing on the device via tl.device_print.

Add the printf for the Triton kernel for Intel GPU. It is useful in debugging the codegen with the printing information inside the kernel.
1.Move the llPrint method outside the PrintOpConversion to global
2.Add kernel_printf util for debugging with printing.
The kernel_printf function can be embedded in the kernel in the lowering to SIMT.


encoding/openapi: test failure

What version of CUE are you using (cue version)?

$ cue version
cue version +008d37d2 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What did you do?
go test cuelang.org/go/encoding/openapi

What did you expect to see?
Passing test.
What did you see instead?
--- FAIL: TestParseDefinitions (0.18s)
    --- FAIL: TestParseDefinitions/oneof.json (0.02s)
        openapi_test.go:147: json: error calling MarshalJSON for type *openapi.OrderedMap: json: unsupported node <[l2// #Embed: 1 errors in empty disjunction: (and 1 more errors)] _|_> (*ast.BottomLit)
    --- FAIL: TestParseDefinitions/oneof-funcs.json (0.02s)
        openapi_test.go:147: json: error calling MarshalJSON for type *openapi.OrderedMap: json: unsupported node <[l2// #Embed: 1 errors in empty disjunction: (and 1 more errors)] _|_> (*ast.BottomLit)
FAIL
FAIL    cuelang.org/go/encoding/openapi 0.238s

008d37d2 is the result of https://cue-review.googlesource.com/c/cue/+/8062 being merged
The CI for https://cue-review.googlesource.com/c/cue/+/8062 passed. Note that commit that was tested was 2f4a8516, which was based on the merged result of https://cue-review.googlesource.com/c/cue/+/8105 ( c62d8a057ae0e4bd6bd7c379a7eac9b399f83e6d)
When https://cue-review.googlesource.com/c/cue/+/8062 got merged however, it was cherry picked on top of https://cue-review.googlesource.com/c/cue/+/8061 (2ef72d85b1ed1311e5c54c176e6bfc7244e46990)

Hence the test failure above is a result of some combination of the combination introduced by https://cue-review.googlesource.com/c/cue/+/8062 and the changes git log c62d8a05..008d37d2

This was recently fixed with the reversal of the "disallow new definition" CL.

This was recently fixed with the reversal of the "disallow new definition" CL.

This issue has been migrated to https://github.com/cue-lang/cue/issues/636.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Using retrolambda in project library causes databinding error

When using retrolambda and databinding together in a library it gives an error. However without retrolambda in project library everything is working.
Link to repository with example: https://github.com/alekmiel/test-multimodule-binding
Error:
D:\Projekty\TestMultimoduleBinding\app\src\main\java\testmultimodulebinding\MainActivity.java:8: error: package testmultimodulebinding.databinding does not exist
import testmultimodulebinding.databinding.ActivityMainBinding;
                                         ^
warning: Supported source version 'RELEASE_7' from annotation processor 'android.databinding.annotationprocessor.ProcessDataBinding' less than -source '1.8'

 FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.
> java.lang.RuntimeException: Found data binding errors.
****/ data binding error ****msg:Cannot find the setter for attribute 'app:integerSupplier' with parameter type testmultimodulebinding.IntegerSupplier. file:D:\Projekty\TestMultimoduleBinding\app\src\main\res\layout\activity_main.xml loc:20:35 - 20:59 ****\ data binding error ****

I also meet this issue,and i find not any useful info with google. by the error log message,it like mean that the databinding only support Java 1.7,but the  retrolambda must use Java 1.8?

@runforprogram that warning can be safely ignored, since java 8 should support java 7 processors fine. The real issue here is that the @BindingAdapter  defined in the library project is not being picked up by the app project.

This is due to databinding using non-class files in it's build output. Previous versions of retrolamba did not copy these files over when doing processing, but it was fixed in 2.0.4. (See https://github.com/orfjackal/retrolambda/issues/54). You can simply point to a newer version of retrolamba by doing
dependencies {
    retrolambdaConfig 'net.orfjackal.retrolambda:retrolambda:2.0.4'
}

or wait until the next release which will default to the latest version.


resolve all security vulnerabilities

This changes package.json, including package homepage and so on. Otherwise looks good.

Whoops.
removed all unnecessary changes

@oleksiyk bump


Write old logs to file

I've been using this package for over a year now, and my log database is getting pretty large. Due to regulatory rules, I'm not allowed to delete the old logs. And due to increased use of the app, the log database grows exponentially.
Question: Are you aware of a package that is able to write part of the logs to a file and remove them from the database?
e.g. write the oldest 1.000.000 logs to a backup file and remove those from the logs table. Or write all logs of week 40 to a file, etc. I've been doing this manually, however it is a boring and repetitive task.
Note: I'm not looking for a solution that backups the full database, those are plenty around.

I don't know any package but it's a simple artisan command. You could copy and adjust the package cleanup command.
https://github.com/spatie/laravel-activitylog/blob/master/src/CleanActivitylogCommand.php
Instead of directly call delete() you could loop via each() over them. Inside the loop callback you could use the storage append method https://laravel.com/docs/6.x/filesystem#storing-files to add the entry in your chosen format to a file. The easiest would be json decode but for sure you could create something similar like a syslog entry.
After appending it you can delete it.
You should use lazy collections or chunks to prevent loading millions of entries in the CLI runtime. Or even trigger a job for every activity ID. But this depends on your amount, needs and is the normal runtime tweaking.


Recaptcha v2 js loads multiple times

Issue description

recaptcha__en.js loads multiple times on any page using recaptcha v2. This is a small issue when trying to optimize page speed, as with all the reloads it comes to 270KB.
Environment

Tested on multiple production, staging, and locally hosted servers using wordpress.

PHP version: 7, 5.6
Web server name and version: local, various websites.
google/recaptcha version: V2
Browser name and version: chrome 77.0.3865.90

Reproducing the issue

https://patrickhlauke.github.io/recaptcha/
open network tab and see that the js loads multiple times.

It can be replicated on their own demo as well:
https://recaptcha-demo.appspot.com/recaptcha-v2-invisible.php
And, not only the recaptcha__en.js file is being loaded several times, but also their fonts:

JS:

reCAPTCHA runs in multiple different frames, which requires resources to be loaded in each. This file is cached heavily though so should require <= 1 network call to load assuming caching is turned on.

This file is cached heavily though so should require <= 1 network call to load assuming caching is turned on.

@jasonfedor This is no longer true now that Chrome implements triple-keyed cache partitioning. The file will now be downloaded multiple times, because the various iframes don't share a cache.
I believe this warrants reopening this issue.

Please do something with that. In addition to the multiple requests for js the reCaptcha stuff consume 15 to 28 requests on my sites (the higher number may be because I use 2 reCaptchas?). That is real #perfmatters

This is actually an issue for us too.
Multiple loads ( both for js and css ) and lowering of page score.

Are there any plans on fixing this, or at least a workaround? We have a landing page with multiple forms (newsletters, contact us, registration etc) and all those recaptchas pile up quicky and aren't cached.

same issue here

same issue here

same!

Same issue!

Same issue, Page Speed Insights complains about the 587k of render blocking JS.

I'm having this issue too. My site is on shared hosting with limited resources, and this causes the pages that have captcha to take a very long time to load. This needs to be fixed!


[Android] CardField has white icon when Dark theme enabled

Describe the bug
I cannot change the CardField text color and placeholder color when Android dark theme enabled.
The text and place holder is white.
Screenshots

Smartphone (please complete the following information):

Device: Samsung Galaxy S10
OS: Android 11

have you tried to update cardStyle when darkmode is enabled? https://stripe.dev/stripe-react-native/api-reference/interfaces/cardfieldprops.html#cardstyle

@arekkubaczkowski Thank you! My mistake.
I was paste the cardStyle as StyleSheet. So i can change the textColor and placeholderColor now.
But the card icon still in white. Do we have any option to change it?

@michelleb-stripe could you refer to this issue?

I have similar issue but my phone doesn't even have dark mode, card field defaults to dark theme (inputs and icon are white), when I use custom styling the icon remains white.

Have just come across the same issue as mentioned above regarding the card icon colour. Looks like none of the available options from CardFieldInput.Styles changes the colour of the icon.

I have the same issue it's only in dark mode.

Device: Samsung Galaxy A7 (2018)
OS: Android 10

I have been able to solve this by adding setting the textColor property to the cardStyle object. It was not working for me when the cardStyle was created with StyleSheet.create probably because textColor is not a valid key when using StyleSheet.

Unfortunately it doesn't solve the problem for me, icon is still not visible.

Changing the textColor doesn't work, only backgroundColor.
The color is always white if in dark mode and black if not.

same

same Xiamo Redmi Note 10, card icon not visible

Same in react native prebuilt ui icons

but in light mode

You can check color scheme and set cardStyle={{backgroundColor: Appearance.getColorScheme() == 'dark' ? '#000000':'#ffffff'}}as per light or dark theme.
         <CardForm
                cardStyle={{backgroundColor: Appearance.getColorScheme() == 'dark' ? '#000000':'#ffffff'}}

            />

When device in darkmode then stripe custom ui give this base64 string for card image
iVBORw0KGgoAAAANSUhEUgAAAGkAAABLCAYAAABz5qkHAAAAAXNSR0IArs4c6QAAAARzQklUCAgI CHwIZIgAAADJSURBVHic7dHBDcAgEMCw0v13PkbgCZHsCSJlzcx8PO2/HcCZSQEmBZgUYFKASQEm BZgUYFKASQEmBZgUYFKASQEmBZgUYFKASQEmBZgUYFKASQEmBZgUYFKASQEmBZgUYFKASQEmBZgU YFKASQEmBZgUYFKASQEmBZgUYFKASQEmBZgUYFKASQEmBZgUYFKASQEmBZgUYFKASQEmBZgUYFKA SQEmBZgUYFKASQEmBZgUYFKASQEmBZgUYFKASQEmBZgUYFKASQEbIXIEkqkHuNsAAAAASUVORK5C YII=
and output is

but when I try same thing with light mode then
stripe give me this base64 string
iVBORw0KGgoAAAANSUhEUgAAAGkAAABLCAYAAABz5qkHAAAAAXNSR0IArs4c6QAAAARzQklUCAgI CHwIZIgAAAbLSURBVHic7Zo9UBtHGIZfZ1JIxekGl5yZFNAgidIgmIxdYUGqeADLcRcwaeICYlLG jJ2ZVGDsmdAEbEpHP8TpIkgaexJk5C5IuMHVSSmVOblQOlKQk093++3eSeckO7PPDDOMdrXa23f3 +9s7d3p6egrF/5r3/usJKMQokSRAiSQBSiQJUCJJgBJJApRIEqBEkgAlkgQokSRAiSQBSiQJUCJJ gBJJApRIEqBEkgAlkgQokSRAiSQBSiQJUCJJgBJJApRIEvA+r9GyWjh+9YfvwcZTg4F+3DQbqNX/ ZLbFh/uh61EAQKVax5s3f3n6aFoEyYTB/Q3LaqF0+BrV47qnbeDCecSH+4Vj+J33BaMPAwPnA43l h3O8lyN/2jvC+kYxkFCL85dxd/VjX30np9eYiwcAh79+1X7g/g+WmX3mZi7i4f0bzLZc4SWy+TJK L06E84jForg5fwkry1PcfqbZwNLKE3JM3nx6gXuSptMjmE6PwLJaKO4fobh3hL2fK9wBtx4/gxaL CB+4Uq2TAs3NXGwLVKmy+wDAxPgQc9zVez/6Esem2WyhabWE/XgCAQi0mYPgyyfpehSZuVHsbC/g 1e/f4IulNDQtQvbPFV4Kx9x69Ixsy8yNtv+nhASARLzTTFWqdcxe3wwkUHssgck7KJ0Ix+XNtRcC Bw66HsXK8hR2s7dIoWq1BizOzrSsFnkiDaOv44QclOiFcfoSy2ph9vommk3xiWAxkfKeSifZfNnX OLz5dkvX0V0yYWDqygjZzttVxf0jcjHdZpIyIamxziDlzt2nXIE0LYLU2GD7zzD6Otp4Dt80G8jv iq0DABx0cYpFcH2SiKn0CDn56nGd6TMAYPvxc+bnmhbxCE+J7RzbslrkPDQtggfrNzCd9m4o02yg uH/E9XsAkC34O0UAUBWM1Q09icQzEdSD8wKGzOxoO+wG+KbD6Y94p3ZleYopEAAMDJzH4sJl8rs2 LB+raRFmWlB9B8FDT8msrkcRH+5ntlFmKsex7e4F45mOpEMkXj/RKRGRzZdRqzU8n2dmRxm9xf64 G3quOFCnidrdOcIspcYGPX6BMh2GK2kcuED7k/zuS2wR5tUPVKR6bW7U4xdtwvZLPYs0TvgdwLuL s/ky6dxZZocyHUlX6O0Oxd2s3n2Kyem1wJFXpVpnht12lcI9D5uwQ/F3dpIA72SpXWkYfR6/YZoN ppkBvDlNMmGQu9o5l9nrm5jJbPo2gVQuZ+dxVG4Vdhjes0i6HiUXyGmuTLNBJoPO5NWmwtmNrI1x b/UqN8G2Kb04wZWP1rD+YI/bj5fL2REodYLDrjyEUgWnQm3nQvMqDIvzDFPHE4nxe8mEwU2w3axv FLF0+wnZniuwTXN6Mtn2h8mEwfy9ZrMF02RbgW4IRyTC5Dl3FBUwzM1c7Ai7bSiTQUWTwNmilX+7 g/Rkkjfdt3MqlLG2UWS2UcHGlMssU6eJZwmC8k5Pkr2jggYMAPDi8DXzc1GQoOtR7GwvoPD950I/ BZwl1u5df1A6If2hO9mmnr0Uol8K7dKPWpDKcZ0MGKi7nKCVb6rfD7lbePTdPNcENpstz66nTDPr 1P8bJ6mnioOTifEh5u4v7h2RAQN1ioJUvkVMp0cwkbqDmcy3pEOvHtfb0aVpNsiAoXT4GjOZzY7P KAtBWYJuCE+k1BDuwxsx8WpqrKgO8F/59ouuR7G4cBnLK3SgYMMLcGo1Oi1gUanWu5qvm9DM3cT4 kO/ICqDLKoD/yjcA31EUr/Cpx96aMCrA6YawktpQX0QR3ck44RU2/VS+gTOBxj78Gku3n6C4T98Y bz1+ju0dujRkBwO8AKcbwqqIh2bugLNFFF2vA525hhu/lW/gbY0sVygj9891QiJuIOY4GdXjOnfh nTVD6gqlW0oh+aVQRRr3eZJ4p8hv5Rtg79QgJkbTIni4fvbiCO8KJT2ZFF6v32dUMMIyd6GKZGfg rHsWG/f1uBu/lW+gtzBX0yLY2Vpoj8kLGO6tXhW+qpXNl1FnvOZ1UDrxnTZQhP5ypMgvfSa4ZPNb +Qa6D3Pjw/3Yzd5qLx7vZpd1hcIi6JVNEMIXibNrNC2Ca5yozrJavivfltXCzU8vdbyrICI1NoiN tU/wS/HLjtA4x7kep9IEN1So3eulIyB4ObIbLKtF7p5YLMrNG3jfTcQNZo3P+T3Kn02khrjfr1Tp 4IL3PT9zFz2zH0IXSRE+6oV9CVAiSYASSQKUSBKgRJIAJZIEKJEkQIkkAUokCVAiSYASSQKUSBKg RJIAJZIEKJEkQIkkAUokCVAiSYASSQKUSBKgRJIAJZIEKJEk4G/ZW+apOaFXMAAAAABJRU5ErkJg gg==
and output of this base64 string is

stripe sending wrong base64 string when darkmode enable in android.

@arekkubaczkowski can you help me on this issue with android.


lbry: 0.52.5 -> 0.53.7

Description of changes
Version bump

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

In the meantime a new version was released: 0.53.7 https://github.com/lbryio/lbry-desktop/releases/tag/v0.53.7
I updated the PR with the latest version

Thanks @enderger I'll wait a couple of days and see if a friendly soul would merge this...

Another new version released upstream. I updated the PR. Changelog here: https://github.com/lbryio/lbry-desktop/releases/tag/v0.53.8


Epg not working

Hi! Guide not working for any channel I think. I checked all portuguese and Canada sportsnet

Previously the guides were available in two version,
uncompressed : guidename.epg.xml
compressed : guidename.epg.xml.gz
Some of the uncompressed guides were starting to hit GitHub's file size limit, so it was decided to only publish the compressed version of all guides.
Check the URL you are using against what is shown on the homepage. If what you are using doesn't end in .gz it won't work.

Oh, I really needed uncompressed version. Ended on xml. Is there any way to keep it?

Apart of uncompressing the file and linking it directly to your program, there's nothing much we can do.


Adding reddit accounts is bugged

Aknowledgements

[X] I have checked that there's no other issue describing the same or
similar problem that I currently have, regardless if it has been
closed or open.

[X] I can confirm that this is not an issue with the Discord website,
but it is a problem specific to the WebCord itself. I have tested
if this bug occurs on Chromium/Chrome or any other Chromium-based
browser that uses unpatched/upstream Chromium engine.

[ ] I have tried running the build from the master branch and it does
not have any fixes implemented according to my issue.

[ ] My issue describes one of the unstable and/or not fully implemented
features.

[ ] I have found a workaround to mitigate or temporarily fix this issue
in affected releases (please write it in Additional context section
below).

Operating System / Platform
🐧 Linux
Operating system architecture
x64 (64-bit Intel/AMD)
Electron version
21.1.0
Application version
v3.8.8
Bug description
It does not let me add an account. It takes me to the reddit website, but after clicking allow and getting redirected, it just keeps loading
Additional context
No response

This IS different from #293

Closing in favour of #293.


Fix line highlight offset when using line numbers

The line-highlight plugin ignored the data-line-offset value when the line-numbers plugin is enabled.
This change fixes the above issue.

Could you please explain the issue you're trying to fix and how your changes fix it?
Also, we now combine data-line-offset and Line number's data-start, so I don't see how this is going to work.

I modified the plugin page of Line numbers to use Line highlight, and everything worked, so how can I reproduce your issue?
I set it up, so that line nr. 7 is highlighted.

Even works with soft-wrap.

Changes:

 <!DOCTYPE html>

 <meta charset="utf-8" />
 <link rel="icon" href="favicon.png" />
 <title>Line Numbers ▲ Prism plugins</title>
 <base href="../.." />
 <link rel="stylesheet" href="style.css" />
 <link rel="stylesheet" href="themes/prism.css" data-noprefix />
 <link rel="stylesheet" href="plugins/line-numbers/prism-line-numbers.css" data-noprefix />
+<link rel="stylesheet" href="plugins/line-highlight/prism-line-highlight.css" data-noprefix />

How to use

Obviously, this is supposed to work only for code blocks (<pre><code>) and not for inline code.

Add the line-numbers class to your desired <pre> or any of its ancestors, and the line-numbers plugin will take care of the rest. To give all code blocks line numbers, add the line-numbers class to the < body> of the page.

Optional: You can specify the data-start (Number) attribute on the <pre> element. It will shift the line counter.

Optional: To support multiline line numbers using soft wrap, apply the CSS white-space: pre-line; or white-space: pre-wrap; to your desired <pre>.

Examples

JavaScript

CSS

Please note that this <pre> does not have the line-numbers class but its parent does.

HTML

Please note the data-start="-5" in the code below.

+

-

Unknown languages

This raw text
 is not highlighted
 but it still has
 line numbers

Soft wrap support

Please note the style="white-space:pre-wrap;" in the code below.

+

-

+

We add a
 and <hr to the
 as a custom title, and as you can see it pushes the code down but the highlight stays in it's position, See https://github.com/siavashs/Prism/issues/27

Can reproduce.
The basic problem here is that the line numbers itself are inside the  element and thus they are aligned relative to it. But the line highlight is aligned relative to the
.
In this line (and this one), we assume basically assume that there is nothing in between the  and
 element, so that's the cause of your issue.
The fix for this problem isn't quite as simple as it might seem but still doable. I'll make a pull request.

@RunDevelopment please mention me or the issue I shared here on your PR, thanks.


outbound calls to land lines

https://github.com/team-telnyx/devrel/tree/main/go shows examples of sending and receiving messages and faxes.
Getting voice working with peercalls and the telnyx gateway should be possible.
Setting up an account at telnyx is very easy and they have a 10 dollar free account with no credit card required. I got a number in 1 minutes there. The prices are good too.

I personally do not have any interest in adding support for this.
That said, I might consider merging a PR that adds support for a service like this, provided that:

It is can be enabled/disabled via configuration options, and would allow adding support for more voice services.
It is simple enough and does not make the codebase messy.


disabling notifs for a room don't stop them appearing on my phone

I turned the notifs on internal to 'mention only' from web but kept receiving push notifs on my phone. I checked the status on the phone and notifs were turned off (in the slide menu). I toggled them on and off again from ios, but I'm still receiving them on iOS

I have the same problem. Always getting notifications, even if "on mention only" is set.


Object.keys(...) on Proxy returned by DelayedConstructor is always empty

Describe the bug
I ran into an issue today trying to use Object.keys(...) on a service resolved from a DelayedConstructor that was registered using the delay(() => MyService) helper function. I noticed that it was always returning [] and not with the keys from the wrapped service instance.
To Reproduce
Register a service with the delay helper function. Resolve it and call Object.keys(...) on it.
import 'reflect-metadata';
import {container, injectable, delay} from 'tsyringe';

@injectable()
class MyService {
    hello = 123;
    whatsup = 'hey';
}

container.register('MyService', {useClass: MyService});
container.register('MyServiceDelayed', {useClass: delay(() => MyService)});

const myService = container.resolve('MyService');
const myServiceDelayed = container.resolve('MyServiceDelayed');

console.log(Object.keys(myService)); // ['hello', 'whatsup']
console.log(Object.keys(myServiceDelayed)); // []

Expected behavior
Object.keys should be proxied to the service instance so that it can return the keys of the wrapped service.
Version:
4.4.0
Potential Solution
I think the solution is pretty simple: we just need to add ownKeys as one of the methods inside lazy-helpers.ts.
  private reflectMethods: ReadonlyArray<keyof ProxyHandler<any>> = [
    "get",
    "getPrototypeOf",
    "setPrototypeOf",
    "getOwnPropertyDescriptor",
    "defineProperty",
    "has",
    "set",
    "deleteProperty",
    "apply",
    "construct",
    "ownKeys" // add this
  ];

I haven't had a chance to test this yet, but I could PR this if someone can confirm this is the right approach.

I went ahead and created the PR since I had a chance to test it myself. Worked as intended.


[DEVHAS-262] cdq outerloop behavior improvement

What does this PR do?:

This PR improves the cdq behavior for better outerloop support.
CDQ now validates the devfile content and the behavior will be:
devfile parser error - if a devfile has invalid schema or there is an error parsing it, CDQ should return the error
invalid kubernetes uri/invalid kubernetes definition - CDQ needs to error out in this situation because an outerloop file has been provided
missing devfile kubernetes/image components - this means that the devfile contains no outerloop definition and CDQ ignores the devfile from provided repo, and needs to match a devfile from registry. Unless the `devfileURL` is specifically being set, this case, the cdq will error out as the requested devfile is invalid for outerloop.
missing deploy command/apply command - if devfile contains more than one kubernetes components but with no deploy command being defined, or contains more than one image components but with no apply command being defined. CDQ will error out. Since HAS will have no idea on which definition should be used when come to component creation.

Which issue(s)/story(ies) does this PR fixes:

https://issues.redhat.com/browse/DEVHAS-262
PR acceptance criteria:

[x] Unit/Functional tests

[ ] Documentation

[ ] Client Impact

How to test changes / Special notes to the reviewer:

@yangcao77 @maysunfaisal
For this specific error scenario:
missing devfile kubernetes components/image component - this means that the devfile contains no outerloop definition and CDQ ignores the devfile from provided repo. It will fall back to the behavior that no devfile exist in the repo. which mean if dockerfile exist, a devfile will be generated from the dockerfile, else needs to match a devfile from registry.

are we sure that we want to match a devfile from the sample in this case, and override the user's devfile? Wouldn't it be better to fall back on gitops generation from within HAS?

@johnmcollier Yes, we discussed in HAS team meeting for 2-3 times, and this is the behavior we want now. which the valid devfile content will be returned by CDQ and stored in the component spec. ideally there should be a warning displayed after CDQ is done in UI, but currently HAC does not accept/display any warnings from HAS.

Codecov reports the overall coverage of HAS dropping by -1.56%, would it be possible to try to increase the coverage?

I have update the PR to be -1.26%.
The coverage report alert some warnings that are not part of this PR, and the rest are some errors not easily to mock & test.

@johnmcollier I have addressed your review comments. Can you help review again when you have time?


Enable IPv6 for iPXE

As requested by @delandtj  via https://github.com/threefoldtech/0-initramfs/issues/20, IPv6 should be enabled by default on iPXE build.
Progression:

[x] Enable IPv6 on iPXE
[x] Update production environment

Production updated, build tested and still works. @delandtj can you confirm ipv6 works ?


multiline input

#16 was closed prematurely; the commit there does nothing to address the issue raised.
I'd like to define a function at the repl, is multiline input available? For example, when I try to type in a function, I get an error (1) and a hang (2).
$ anko
> f=func(x) {
typein:1: syntax error: unexpected $end, expecting ','             <error (1)>
>   return x+1 }
 <hang (2) >

nice howto Q & A here http://stackoverflow.com/questions/6636808/repl-for-interpreter-using-flex-bison


Alignment buttons act on non-selected paragraphs

Trumbowyg version: 2.5.1
Browser: Chrome 58.0.3029.81 on OSX
Steps to reproduce:
(Note: This can be done on the demo editor on https://alex-d.github.io/Trumbowyg/)

Enter 3 paragraphs of text (Or paste into the code editor:
Line 1

Line 2

Line 3
)
Select line 2 and line 3.
Click the align center button.
Click the align right button.

Expected: Line 1 remains left aligned, 2 & 3 are centered and then aligned right.
Actual: Line 1 remains left aligned initially, while 2 & 3 are centered but then also aligns right when the align right button is clicked.

Should be fixed in future v3 (See #875 for more details).
I close this to keep issues clean since this issue is old with no activity and no trivial fix.


[Device Type Plugin] Realtime analytics are not updated when the device type name contains uppercase letters.

Pre-Conditions:-

Install the device type as described at [1]
Start broker, core and analytics in that order.
Download the device type agent
Start the downloaded device type agent.

Steps:

Go to enrolled device and check the real time analytics

Expected Results:-

Realtime analytics should get constantly updated within given intervals

Actual Results:-

Realtime analytics do not get updated when device type name contains upper case letters. (screenshot attached)

[1] https://github.com/wso2/carbon-device-mgt-maven-plugin/blob/master/README.md

@sameerawickramasekara : Please assign this ticket to yourself.
@ruwany : Labels: High , [current release tag] , Automation-Test-Needed


add example: twilio_api_v2010.json

This OpenAPI spec was copied from Twilio's public OpenAPI repo:
https://github.com/twilio/twilio-oai
Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[x] I acknowledge that all my contributions will be made under the project's license.

A couple things here:

Does this actually generate meaningfully decent code?  My expectation is that it might not.
What's the value here?  This is a 29,000 line openapi spec that will get parsed 5 or 6 times and will likely slow down our already-pretty-slow build.  If we're going to write tests around this and assert useful things, ok.  Otherwise I don't think it's worth it.

Closing for now, if you feel strongly about it please feel free to comment here.


DOI for a STAC Collection

Hi,
is there a way to assign a DOI to a STAC collection? I don't want to upload it on Zenodo, and the collection is constantly growing. I guess that's a common use case for STAC collections. Are there any examples, best practices? Here's our collection, every participant of the online course Cubes and Clouds (course starts soon) submits their results to this community map: https://esa.pages.eox.at/cubes-and-clouds-catalog/browser/#/snow_map/collection.json

I'm not sure I understand the question, but you can use sci:doi in a Collection. It's up to you to register the DOI.

but you can use sci:doi in a Collection.

I understood that the sci:doi is for the DOI of the scientific publication that is related to the collection.

It's up to you to register the DOI.

That would be my question how to register a DOI for a STAC collection that is constantly growing. For example this S2 collection is also adding images daily. The collection doesn't have a DOI itself. Are there are any examples of a STAC collection that has its own DOI you or the STAC community knows of?


Lots of allocations

Cuba produces a lot of allocations, 4 per iteration in the example below. Is there a way to avoid this?
julia> using Cuba

julia> f!(x,ret ) = ret
f! (generic function with 1 method)

julia> vegas(f!); # warmup

julia> @time vegas(f!)
  0.001090 seconds (4.01 k allocations: 187.984 KiB)
Component:
 1: 0.0 ± 7.025180405943273e-18 (prob.: -999.0)
Integrand evaluations: 1000

I'll have a look but I'm not sure there is anything I can do about this.  The only suggestion I can give you is to use cuhre instead of vegas as the former is more accurate and requires fewer evaluations (thus fewer allocations):
julia> using Cuba, BenchmarkTools

julia> @btime cuhre((x, f) -> f[1] = x[1])
  25.231 μs (784 allocations: 36.89 KiB)
Component:
 1: 0.5 ± 4.291960664289122e-15 (prob.: 0.0)
Integrand evaluations: 195
Fail:                  0
Number of subregions:  2

julia> @btime vegas((x, f) -> f[1] = x[1])
  21.588 ms (928004 allocations: 42.48 MiB)
Component:
 1: 0.4999999506146127 ± 4.969630652405548e-5 (prob.: 2.559630372933608e-5)
Integrand evaluations: 232000
Fail:                  0
Number of subregions:  0


Attached Field in Document is not updated.

####  To change the Local Field of Document
            if self.attached_to_field:
                frappe.db.set_value(
                    self.attached_to_doctype,
                    self.attached_to_name,
                    self.attached_to_field,
                    self.file_url,
                )
####

On change in File, please update the connected field value also which holds the path to File.

Hi @hkmj-erp sorry answering you so late! :) Could yo elaborate more the issue being solved and the solution please? I can not imagine cases affected and in what way? Thank you very much for your help @hkmj-erp :)


Map isn't showing up on Richness, Activity and Spotlight

Original post: https://rfcx.slack.com/archives/C02G4AR2GEL/p1718616808831249
The map is not showing on the activity page of the insights (all browsers - tested on safari + chrome)
Including Richness and Spotlight pages

Released on v1.4.1


Add class to identify fields

Also added filament-forms-input to allow for cleaner css when targeting input/select/etc.
e.g helpful to customise grid into a input group

Forms\Components\Grid::make()
    ->columns(3)
    ->extraAttributes(['class' => 'filament-input-group'])
    ->schema([
        Forms\Components\TextInput::make('first'),
        Forms\Components\Select::make('second'),
        ColorPicker::make('third'),
    ]),

/* input group */
@screen lg {
    .filament-input-group > .grid {
        gap: 0;
    }

    .filament-input-group > .grid > :first-child .filament-forms-input,
    .filament-input-group > .grid > :first-child .filament-forms-input .choices__inner {
        border-top-right-radius: 0;
        border-bottom-right-radius: 0;
    }

    .filament-input-group > .grid > :not(:first-child):not(:last-child) .filament-forms-input,
    .filament-input-group > .grid > :not(:first-child):not(:last-child) .filament-forms-input .choices__inner {
        border-radius: 0;
        border-left: none;
    }

    .filament-input-group > .grid > :last-child .filament-forms-input,
    .filament-input-group > .grid > :last-child .filament-forms-input .choices__inner {
        border-top-left-radius: 0;
        border-bottom-left-radius: 0;
        border-left: none;
    }
}

The naming is fine, but I did need to remove some classes that were added here because they were duplicates of ones already in the view. Also I had to remove the input class from some components that weren't technically HTML input components.

Isn't it then better to just not add filament-forms-input either?
Not sure if the current implementation solves @howdu's case.

Sure. Let us know if it doesn't work for your case, @howdu.


Add a transcoding queue for large transcoding jobs

For datasets up to some byte size, GET /array/full/some_array simply returns the data directly. For datasets above that size, we reach one or two limitations:

The dataset takes so long to transcode that HTTP proxies (e.g. nginx) and/or clients may time out.
The dataset consumes too much of server RAM.

Therefore, we must transcode it to some persistence storage (e.g. POSIX filesystem, blob storage) and, later, spool it from there. It can be retained for some time to make subsequent requests go faster, as long as space allows.
The client-side experience will be much like when you download a directory of files from Google Drive. Google packs up the files into a zip archive and then, when that's complete, gives you a download link. The proposed flow is:
GET /array/full/very_large_array -> 202 Accepted Location: /queue/{job_id}
GET /queue/{job_id} -> 200 OK (body contains stats like how long it has been running)
Later...
GET /queue/{job_id} -> 303 See Other Location: /download/{job_id}
GET /download/{job_id} -> 200 OK (body is large data)
Later...
GET /download/{job_id} -> 410 Gone (artifact has been garbage collected)
informed by https://farazdagi.com/2014/rest-and-long-running-jobs/ which has disappeared but is still available at https://web.archive.org/web/20200511220257/https://farazdagi.com/2014/rest-and-long-running-jobs/.
We made a very rough prototype of this flow in https://github.com/bluesky/suitcase-server/blob/master/suitcase_server/handlers.py. It has a lot of problems and never got as far as being used but it may be a useful reference.
Requirements:

[ ] A simple "scaled down" implementation that uses Starlette BackgroundTasks
[ ] A scalable implementation that uses a shared task queue --- potentially pluggable to Celery, Luigi, etc. in the future --- and a worker pool

This is a prerequisite for #43 because trees are likely to be large --- i.e. "Download everything below this node as an HDF5 file".

I think this is great for a lot of reasons, including the ability to grab large data sets in a batch style mode to produce training sets for AI models...something that @kleinhenz  has talked about.

For notifying the client that the package is ready, what about supporting  something that can generate events and be consumed by https://developer.mozilla.org/en-US/docs/Web/API/EventSource?

Oh, cool, I wasn't aware of that feature. At first glance, it looks like this would require separate client capability. For example, there are Python libraries for it but httpx and requests do not encompass it. I guess it also isn't something you could use from curl.
How would you feel about starting with the lo-fi 202 / 303 implementation and then adding the EventSource option in a follow-up?

Sure. The EventSource mechanism seems like a handy way to get one way notification from the server back to clients. The main difference seems to me that 202/303 requires the client poll regularly...EventSouce takes advantage of a long-lasting connection. In both cases, the client is going to have to do something in the background, which I suspect is the real new thing.
Again, the spec is new to me, but  I suspect that we're going to want to have done EventSource if/when someone gets serious about developing browser-based apps that talk to Tiled.

I agree. And I could be persuaded to flip the order. I guess I'm just advocating that we lay track for doing both, because I think will be eventually want both.

I agree with that. And on both the client and server, I'll bet that the two implementations share a lot of track.

Circling back to think about this almost a year later…

The idea of using BackgroundTask for this was misguided. This is fundamentally decoupled for the HTTP and we should build it with a shared job queue from the start.
Permissions are tricky, as users may be able to see different parts of the same node. To start, a given job should be only accessible to the user who initiated it.
We need a new (SQL?) database to manage this, acting as a work queue and policing things like “same user cannot queue more than exports of the same node to a given format”. The interface could be pluggable to enable integration with external workflow systems like Celery or Prefect but the “work” is so constrained in this case that I question the value of adding those systems. A tightly integrated database might be perfect.
Time-based expiry seems a pragmatic way to start.
A long-running work process should consume from the queue. Separately, a single shot transcoding CLI may be a useful thing to have for working inside other workflow managers.

Also, at some point we discussed reusing artifacts across repeated requests but this is also complicated by permission—the way different users have different views into a node. We would also have to handle the possibility of mutation/modification.
Each asset should be bound to a specific job to start.

Summarizing discussion with @dylanmcreynolds

We can use Redis to manage both the queue of jobs and the "database" of outputs.
Output can be marked as eligible for deletion once downloaded, or once a max age passes, whichever happens first. Other policies may be useful in the future, but this is a good policy to start.
A periodic job should delete any outputs that are marked as eligible for deletion or orphaned.
We can put the Redis behind a Python object with a defined interface, to facilitate future pluggability---i.e. adding hooks when jobs are complete, or plugging in other backends.
Redis a good fit here because it can persist across restarts, but it's generally for ephemeral data. We don't want to be bothering with database migrations here; if we need a change in what's stored, the Redis should be blown away, not migrated.


20 data delivery test

The Backend.snl.DotSettings.user file should be patched up after merge so that the master-branch is clean:
Closes #20

You can use delete the file and commit the deletion to remove the file. Simply adding it to the gitignore doesn’t remove it from the project once it’s checked in.

On 17 Feb 2021, at 22:23, Kpaubert<EMAIL_ADDRESS>wrote:
@Kpaubert commented on this pull request.
In .gitignore https://github.com/IT2901-SINTEF01/backend/pull/26#discussion_r577954043:

\ No newline at end of file
+/_ReSharper.Caches/
+BackendTests/BackendTests.csproj
+Backend.sln.DotSettings.user
Sorry, when I read it back it wasn't too clear. I just meant that when we've merged this one, we should probably remove all IDE/user-specific files so when we branch out again, the repo is more clean.

I tried removing it now just so I didn't further dirty the file. However the ignore did not work, as the file is still there.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub https://github.com/IT2901-SINTEF01/backend/pull/26#discussion_r577954043, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB2V2G6M75OPCRL6S575AITS7QXV3ANCNFSM4XZBIUXA.

I also added some further thoughts to https://github.com/IT2901-SINTEF01/backend/issues/20#issuecomment-780860218 which belong here. Especially the following part:

I think it would be beneficial if we tried to avoid sending network requests in our unit tests (incl. sending requests to third-party APIs). If possible, it would be nice if you could disable the tests that call an API by default, and then we can run them manually every once in a while (perhaps also in CI once we release a new release).


Bug: MessageChannels need hard capacity limits

We're seeing crashes when the # of items in a MessageChannel exceeds some limit. Likely having to do with the wrapping message index value overflowing before it can be recycled.
Case #1: https://gist.github.com/pbalcer/02b85eaa7b26e86478fcffef36fc7636
thread 'main' panicked at 'can't encode a negative number with an Unsigned Integer!', /home/piotrek/.cargo/registry/src/github.com-1ecc6299db9ec823/naia-serde-0.18.0/src/integer.rs:26:13
stack backtrace:
   0: rust_begin_unwind
             at /rustc/2c8cc343237b8f7d5a3c3703e3a87f2eb2c54a74/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /rustc/2c8cc343237b8f7d5a3c3703e3a87f2eb2c54a74/library/core/src/panicking.rs:64:14
   2: naia_serde::integer::SerdeInteger<_,_,_>::new
             at /home/piotrek/.cargo/registry/src/github.com-1ecc6299db9ec823/naia-serde-0.18.0/src/integer.rs:26:13
   3: naia_shared::messages::channels::senders::indexed_message_writer::IndexedMessageWriter::write_message_index
             at /home/piotrek/.cargo/registry/src/github.com-1ecc6299db9ec823/naia-shared-0.21.0/src/messages/channels/senders/indexed_message_writer.rs:85:35
   4: naia_shared::messages::channels::senders::indexed_message_writer::IndexedMessageWriter::write_message
             at /home/piotrek/.cargo/registry/src/github.com-1ecc6299db9ec823/naia-shared-0.21.0/src/messages/channels/senders/indexed_message_writer.rs:101:9
   5: naia_shared::messages::channels::senders::indexed_message_writer::IndexedMessageWriter::write_messages
             at /home/piotrek/.cargo/registry/src/github.com-1ecc6299db9ec823/naia-shared-0.21.0/src/messages/channels/senders/indexed_message_writer.rs:34:13
   6: <naia_shared::messages::channels::senders::reliable_sender::ReliableSender<naia_shared::messages::message_container::MessageContainer> as naia_shared::messages::channels::senders::channel_sender::MessageChannelSender>::write_messages
             at /home/piotrek/.cargo/registry/src/github.com-1ecc6299db9ec823/naia-shared-0.21.0/src/messages/channels/senders/reliable_sender.rs:136:9
   7: naia_shared::messages::message_manager::MessageManager::write_messages
             at /home/piotrek/.cargo/registry/src/github.com-1ecc6299db9ec823/naia-shared-0.21.0/src/messages/message_manager.rs:249:17
             ...

This seems to be an issue with too many messages being put in an OrderedMessageChannel at a time. The MessageIndex u16 indicates an upper limit of a single channel would be 2^15 (32768) or less.
Case 2:
thread 'main' panicked at 'Write overflow!', /home/piotrek/.cargo/registry/src/github.com-1ecc6299db9ec823/naia-serde-0.18.0/src/bit_writer.rs:92:13
stack backtrace:
   0: rust_begin_unwind
             at /rustc/2c8cc343237b8f7d5a3c3703e3a87f2eb2c54a74/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /rustc/2c8cc343237b8f7d5a3c3703e3a87f2eb2c54a74/library/core/src/panicking.rs:64:14
   2: <naia_serde::bit_writer::BitWriter as naia_serde::bit_writer::BitWrite>::write_bit
   3: naia_client::connection::channel_tick_buffer_sender::ChannelTickBufferSender::write_message
   4: naia_client::connection::channel_tick_buffer_sender::ChannelTickBufferSender::write_messages
   5: naia_client::connection::tick_buffer_sender::TickBufferSender::write_messages
   6: naia_client::connection::connection::Connection<E>::send_outgoing_packets
   7: naia_client::client::Client<E>::receive
   8: bevy_ecs::world::World::resource_scope

This one seems to have been caused by Client->Server ping of ~7 seconds. In which case, the redundant message sending every tick probably flooded the channel past the ~400 byte limit. However, much of that code already has assert checks the whole way while writing the packet to make sure it doesn't overflow the limit (or throws a helpful error when it does) so how this got through is curious..

When I tried to implement a game that spawns a large number of NPCs, I got the following error.
thread 'main' panicked at 'Write overflow!', **home**\.cargo\registry\src\github.com-1ecc6299db9ec823\naia-serde-0.18.0\src\bit_writer.rs:92:13
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library\std\src\panicking.rs:575
   1: core::panicking::panic_fmt
             at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library\core\src\panicking.rs:64
   2: naia_serde::bit_writer::impl$1::write_bit
             at  **home**\.cargo\registry\src\github.com-1ecc6299db9ec823\naia-serde-0.18.0\src\bit_writer.rs:92
   3: naia_shared::world::host::host_world_writer::HostWorldWriter::write_updates
             at  **home**\.cargo\registry\src\github.com-1ecc6299db9ec823\naia-shared-0.21.0\src\world\host\host_world_writer.rs:452
   4: naia_shared::world::host::host_world_writer::HostWorldWriter::write_into_packet<bevy_ecs::entity::Entity,naia_bevy_shared::world_proxy::WorldRef>
             at **home**\.cargo\registry\src\github.com-1ecc6299db9ec823\naia-shared-0.21.0\src\world\host\host_world_writer.rs:48
   5: naia_server::connection::connection::Connection<bevy_ecs::entity::Entity>::send_outgoing_packets<bevy_ecs::entity::Entity,naia_bevy_shared::world_proxy::WorldRef>
             at **home**\.cargo\registry\src\github.com-1ecc6299db9ec823\naia-server-0.21.0\src\connection\connection.rs:179
   6: naia_server::server::Server<bevy_ecs::entity::Entity>::send_all_updates<bevy_ecs::entity::Entity,naia_bevy_shared::world_proxy::WorldRef>
             at **home**\.cargo\registry\src\github.com-1ecc6299db9ec823\naia-server-0.21.0\src\server.rs:343
   7: naia_bevy_server::systems::before_receive_events::closure$0
             at **home**\.cargo\registry\src\github.com-1ecc6299db9ec823\naia-bevy-server-0.21.0\src\systems.rs:178
   8: bevy_ecs::world::World::resource_scope<naia_server::server::Server<bevy_ecs::entity::Entity>,tuple$<>,naia_bevy_server::systems::before_receive_events::closure_env$0>
...

I think you should write the finish bit after the releasing bit.
otherwise, we will run out of buffers.
I avoid this error as below.
https://github.com/naia-lib/naia/commit/a2edc813599d23acf061022bed00f23426850821
However, when I attempted to apply the same change to all place of writer.release_bits(1),
I encountered another 'Write overflow!' error. I'm not sure what the correct fix is,
but I hope this information helps in resolving the issue.


ClassDB: Exclude method binds starting with '_' from API hash

As discussed in #32967.
These methods are not meant to be part of the scripting API.
These are not the same as virtual methods starting with '_', e.g.: '_process'.

Thanks!


Document installation procedures

Describe the Task
Document the steps to install the system on Users Guide.
These documentation updates should be done in conjunction with testing the installation of WRF Cloud within the METplus AWS account. After that installation is complete, be sure to test by running WRF with sub-hourly output. That will test that #113 works as expected.
Time Estimate
1 day
Sub-Issues
Consider breaking the task down into sub-issues.

[ ] Add a checkbox for each sub-issue here.

Relevant Deadlines
List relevant project deadlines here or state NONE.
Define the Metadata
Assignee

[ ] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required

Labels

[ ] Select component(s)
[ ] Select priority

Projects and Milestone

[ ] Select Project
[ ] Select Milestone as the next official version or Backlog of Development Ideas

Task Checklist

[ ] Complete the issue definition above, including the Time Estimate.
[ ] Fork this repository or create a branch of develop.
Branch name: feature_<Issue Number>/<Description>
[ ] Complete the development and test your changes.
[ ] Add/update log messages for easier debugging.
[ ] Add/update tests.
[ ] Add/update documentation.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into develop.
Pull request: feature <Issue Number> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s), Project, and Development issue
Select: Milestone as the next official version
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Close this issue.

On 1/20/23, @JohnHalleyGotway met with @hahnd to reinstall the existing wrfcloud instance. Made several notes about that process (details below) and recorded the meeting (see Shared Google Drive).
On 1/25/23, @JohnHalleyGotway will step through the instructions to install WRFCloud as johnhg-metplus in the METplus AWS Instance.
@JohnHalleyGotway will update the documentation on the feature/auto-install branch directly with details from installing in the WRFCloud and METplus AWS Instances.
Details...

Recommend running as an AWS user with 'AdministratorAccess' which is available to every account. Amazon Resource Name = 'arn:aws:iam::aws:policy/AdministratorAccess'

Testing installation instructions within the existing WRFCloud AWS instance, as a member of the 'admin' group in AWS WRFCloud which is a custom group defined for this instance rather than a standard one.

Through AWS confirm the Route53 domain name.
Confirm the 96+ limit via EC2 AWS instance

If <96, submit a request to AWS to increase that limit.

Check this via the SES AWS interface. Under 'account dashboard' make sure there is no banner indicating we're in the sandbox. Note that this requires at least on 'verified identity' be defined, wrfcloud.com in our case. But could be a verified email address.

Move this step down to after the installation which creates the 'verified identity'.

Fix command in RTD since the -- was converted to a hyphen.
git clone --branch feature/auto-install https://github.com/NCAR/wrfcloud
Note that feature/auto-install will be replaced by a tagged version number.
Recommend defining the tag or branch name as an environment variable at the beginning of the instructions.
$WRFCLOUD_BUILD_VERSION ?

The compilation of Python3.9 takes a long time during the bootstrap process. Consider searching for a pre-built package through yum for this instead.
Verify the install.
Questions to be answered:

Would you like to enable autocompletion? This will set up your terminal so pressing TAB while typing Angular CLI commands
will show possible options and autocomplete arguments. (Enabling autocompletion will modify configuration files in your home
directory.) Yes or No, doesn't really matter. Would like to get rid of this question if possible.
Which domain name would you like to use? (wrfcloud.com)
Enter host name for web application: [app.wrfcloud.com]
Enter host name for REST API: [api.wrfcloud.com]:
Enter host name for websocket API: [ws.wrfcloud.com]:
Enter administrator's full name:
Enter email address for application administrator:
Enter administrator's new password:
Do you want to install example model configurations (yes/no)?  yes
Do you want to upload an SSH public key for an admin?  Without it, you cannot access your clusters to debug. (yes/no)?
Paste your public key, often found at ${HOME}/.ssh/id_rsa.pub:
Confirm via email.
(Congratulations!
You have successfully verified an email address. You can now start sending email from this address.)
Please check your email<EMAIL_ADDRESS>and click the link to confirm.
Creating WRF Image...
WrfIntelImageBuilder ... CREATE_IN_PROGRESS ... 2023-01-20 17:46:22 ...
... Takes approximated 10-20 minutes for the website to become available...
Open CloudFormation AWS service to monitor build progress. Monitor progress via the 'Events' tab.
Also monitor cloud shell and watch for an alert telling me to got to the URL.

Need to add users.
Recommend documenting the process for...

tweaking the graphics (e.g. new plot types, new color scales)
adding a new domain by uploading new namelist files for now
initializing with data other than GFS

Pre-Requisites REQUIRES ADMIN PRIVILEGE ON AWS ACCOUNT

AWS Account

[x] Testing as johnhg-metplus in the METplus AWS Instance.
[ ] TODO: Define minimum set of permissions required.

Domain name in Route 53

[ ] TODO: select one

AWS account limit for “Running On-Demand All HPC instances” in us-east-2 must be 96 vCPUs or higher

[x] After logging in, selected the US East (Ohio) "us-east-2" region.
[ ] TODO: Figure out how to check and/or set this.

Simple Email Service (SES) must be out of the sandbox in us-east-2

[ ] TODO: Check this

METplus AWS Installation Steps (refer to the WRFCloud Recording):

Log on to METplus AWS Instance.
Confirm location is Ohio (i.e. US East (Ohio), us-east-2) and reconfirm with each step below.
In Route 53 service confirm at least one domain is available in Hosted zones.
In EC2 service, select Limits, search for HPC. Confirmed that the limit of 768 vCPUs > 96. If < 96, submit a request to AWS to increase that limit.
In SES service (e.g. Amazon Simple Email Service), select Account dashboard and check for a banner message warning "Your Amazon SES account is in the sandbox in US East (Ohio)".

NOTE: METplus is in the Sandbox and I did "Request production access".
AWS responded requesting more details about our use case. @hahnd notes that we should:
a. Confirm that we requested production access in the us-east-2 region.
b. In the SES service, select Verified identities and confirm that we have at least one.
c. In the Notifications tab of the verified identity, have Feedback forwarding enabled. And have feedback notifications set to go to an SNS topic. Might not be required, but sometimes they will ask about it.

NOTE: I don't have sufficient permission in METplus for 5b above:
You do not have sufficient access to perform this action.
User: arn:aws:iam::707838134870:user/johnhg-metplus is not authorized to perform: ses:CreateEmailIdentity on resource: arn:aws:ses:us-east-2:707838134870:identity/metpluscloud.com because no identity-based policy allows the ses:CreateEmailIdentity action

Clicked CloudShell icon from the top menu bar but did not have sufficient permission:

Unable to start the environment. You don't have required permissions. Ask your IAM administrator for access to AWS CloudShell. System error: User: arn:aws:iam::707838134870:user/johnhg-metplus is not authorized to perform: cloudshell:CreateEnvironment on resource: arn:aws:cloudshell:us-east-2:707838134870:*

Met with Deidre on 2/1/23:

Update the "Introduction" to state... This is designed to run in its own VPC and we recommend doing so in a dedicated VPC to avoid conflicts.
Rename "Required Permissions" to "Who Should Install?"

Who should install this? Either someone with sufficient administrative access in the VPC or someone who could be granted those permissions.

Note that some users won't even have permission to launch IAM.
Full AdministratorAccess or above... (i.e. SystemsAdminstrator policy or Root)

On 2/7/23, made it almost all the way through the WRF Cloud install in the METplus AWS instance. But here's the error:
Please check your email<EMAIL_ADDRESS>and click the link to confirm.
Traceback (most recent call last):
  File "/opt/python/bin/wrfcloud-setup", line 33, in <module>
    sys.exit(load_entry_point('wrfcloud==0.1.0', 'console_scripts', 'wrfcloud-setup')())
  File "/opt/python/lib/python3.9/site-packages/wrfcloud/setup/__init__.py", line 41, in setup
    _create_cluster_policy()
  File "/opt/python/lib/python3.9/site-packages/wrfcloud/setup/__init__.py", line 452, in _create_cluster_policy
    res = iam.create_policy(
  File "/opt/python/lib/python3.9/site-packages/botocore/client.py", line 530, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/opt/python/lib/python3.9/site-packages/botocore/client.py", line 960, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.errorfactory.EntityAlreadyExistsException: An error occurred (EntityAlreadyExists) when calling the CreatePolicy operation: A policy called wrfcloud_parallelcluster already exists. Duplicate names are not allowed.

Found that a previous partial install caused the following installation error. Listed below is direction from @hahnd:
The angular libraries should not be installed until after the layer zip file is created:
  ### Create WRF Cloud Build Artifacts
  create_wrfcloud_lambda_layer
  create_wrfcloud_lambda_function

  ### Compile angular web application
  install_angular14

Somehow, you ended up with angular installed before the lambda layer zip file was created.  Probably from a previous install attempt.
We should either delete rm -Rf ~/.nvm/versions/node/v16.19.0/lib/node_modules/@angular before creating the lambda layer zip file; or be explicit in what we include in the lambda layer zip file:
zip -r "${build_dir}/lambda_layer.zip" python/lib node/bin node/include node/share node/lib/node_modules/corepack node/lib/node_modules/npm   Either of these changes would go into the create_wrfcloud_lambda_layer function in install_bootstrap.sh.
John Halley Gotway
10:58 AM
Makes sense. I think we should expect users to fail at least once in their installation attempts! Is there anything I should add to the uninstall steps? And which of these 2 options do you prefer? Is either a more robust solution?
David Hahn
10:59 AM
I suppose the latter is probably better.  It would protect against the rare case where users have other node libraries installed in their CloudShell environment.  I think we should address it in the scripting and would not need to update the uninstall docs.

Finally got a successful build in the METplus AWS account!
WRF Cloud installation is complete.
Open your browser to https://app.metpluscloud.org

However, going to that URL results in the same odd "Download" behavior that David noted in the past with wrfcloud.com. @hahnd, please advise.
https://user-images.githubusercontent.com/21087144/217919260-e8b1bdf1-b893-4b69-a8ac-2014544f8ea7.mov

Notes from 2/9/23:

After fixing host-config.txt (fd8588f), I was able to run the install process to completion.
Navigating to app.metpluscloud.org results in the weird "download" behavior. I followed David's slack instructions to create invalidations twice, but the problem persisted after the 2nd try. However, navigating to app.metpluscloud.org/ did work... so we could update the instructions to go to app.metpluscloud.org/logic.
I did NOT see the any default "Model Configuration" even though those files DO exist in S3.
I downloaded it from S3 and tested the "WRF Configs" menu to manually upload one.

Works great! But when the name contains embedded whitespace, the error message should describe the problem:

Attempting to launch a job actually fails as well:

Not sure why?

The website works for me now, even going to https://app.metpluscloud.org.  I have my browser configure not to cache anything, so you might just need to clear your cache and try again.
Looks like I forgot to update the UI to validate the configuration name value.  The API still validates the request, so you get an error.  You can only use alphanumeric, -, and _ in the name.  Need to add a bugfix/enhancement to address this issue.
In general, you can find errors from the API in CloudWatch Logs.  Find the log group for production_wrfcloud_handler and search for the reference ID:

@hahnd thanks for the tip on the logs. From the perspective of installation instructions for this issue, I'm wondering if I need to document the procedure you described in scratch to avoid the odd "download" behavior. Or if just going to "/login" avoids it in the first place then that'd be easier. But it'll take another round of testing to determine what's actually required.
I'll do that tomorrow.
If going to ".../login" avoid it entirely, that seems simpler.
If it doesn't, then I'll write up your instructions from Slack.
The WRF job failed because there's no wrf AMI in my account to run. But I did get an AMI in prior testing. Any guesses as to the issue? I did merge in recent changes from the develop branch today into my feature branch. Perhaps recent develop changes impacts the AMI creation step?

I want to check with AWS again on this behavior.  It should not be necessary.  Maybe something is missing when we upload the files.  The root of the problem is that the mime type of the response is set to application/octet-stream instead of text/html, so the browser handles it differently.
Going to /login (or any other path) will actually download the exact same file.  That is how CloudFront is configured and must be configured like that for the Angular application.  The Angular Router handles content switching based on the path.  However, your browser did not have /login cached, so the browser expected a different file and went to the server instead its cache.
@.*** src]$ curl https://app.metpluscloud.org/ 2> /dev/null | shasum -a 256
e4e618d7c0dd9f9ae37cf62ac0feb02174d07902288c4e2a315642db5a8b395c  -
@.*** src]$ curl https://app.metpluscloud.org/login/ 2> /dev/null | shasum -a 256
e4e618d7c0dd9f9ae37cf62ac0feb02174d07902288c4e2a315642db5a8b395c  -
@.*** src]$ curl https://app.metpluscloud.org/jobs/ 2> /dev/null | shasum -a 256
e4e618d7c0dd9f9ae37cf62ac0feb02174d07902288c4e2a315642db5a8b395c  -
Is the AMI still building?  If not, check for errors in CloudWatch Logs.  Find the imagebuilder/wrf-4-4-0 Log Group and look at Log Streams in there.

On Feb 9, 2023, at 4:51 PM, John Halley Gotway @.***> wrote:
@hahnd https://github.com/hahnd thanks for the tip on the logs. From the perspective of installation instructions for this issue, I'm wondering if I need to document the procedure you described in scratch to avoid the odd "download" behavior. Or if just going to "/login" avoids it in the first place then that'd be easier. But it'll take another round of testing to determine what's actually required.
I'll do that tomorrow.
If going to ".../login" avoid it entirely, that seems simpler.
If it doesn't, then I'll write up your instructions from Slack.
The WRF job failed because there's no wrf AMI in my account to run. But I did get an AMI in prior testing. Any guesses as to the issue? I did merge in recent changes from the develop branch today into my feature branch. Perhaps recent develop changes impacts the AMI creation step?
—
Reply to this email directly, view it on GitHub https://github.com/NCAR/wrfcloud/issues/126#issuecomment-1424988952, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB24LJU6GWWLIPNEQ3KOODLWWV7IVANCNFSM6AAAAAAUGVLD6I.
You are receiving this because you were mentioned.

Feedback from @brukerd sent via email on 2/16/23. Thanks for the feedback! Since these are doc-only changes, I'll just commit them directly to the develop branch...
My suggestions:
In the AWS Management Console, use the top-level search bar to find and launch the AWS IAM (Identity and Access Management) Service.
If you are unable to launch the AWS IAM Service, you do not have sufficient permissions.
Make the second bullet point a sub-bullet of the first one; it pertains to the first bullet point.
In Access management > Users, find and select your user name, and inspect the Permissions policies.
Ensure that you have AdministratorAccess, SystemAdministrator, or higher permissions.
Same as above. Make the second bullet a sub-bullet of the first one.
Anyplace you mention contacting AWS Support, if the user isn't utilizing the root account for their AWS VPC, they may need a support policy to be defined. By default, only the root account can make support requests. AWS documentation on creating the policy/policies is here: https://docs.aws.amazon.com/awssupport/latest/user/accessing-support.html
Select the US East (Ohio) / us-east-2 region from the top-right dropdown navigation.
Is there a reason you're specifying a region like this instead of just mentioning they need to pick their closest region? This is potentially a limitation for non-US users. This is also something that they will need to take into account when making support requests for higher vCPU limits.


adding rebase script

first try getting the o/k rebase script adopted to etcd

/hold

TODO: mention minor updates using fork-points

/hold cancel


[BUG] Rendering snap pins only shows half the structure in OpenSCAD UI

Describe the bug
Rendering snap pins only renders half the structure when using OpenScad UI.

NOTE: Rendering appears to work as expected using CLI command.

Open OpenSCAD in UI
Paste below code
Click render button
See only half of snap pin

Code To Reproduce Bug
include <BOSL2/std.scad>;
include <BOSL2/joiners.scad>;

snap_pin("small");

Expected behavior
Expected to render double sided pin, but only half is rendered
Screenshots

Additional context
Add any other context about the problem here.

OpenSCAD Version: 2022.03.02
Other libraries used: N/A

I am not able to duplicate your problem.  Your code produces the full pin both on preview or render for me, either in the stable 2019 version or in the nightly build.  (I don't have 2022.03.02).
Side note:  your $fn is too small.

I also cannot reproduce it in OpenSCAD 2022.08.22 (git ea8950bd3).
On an unrelated note, the pointy ends have too much overhang to print cleanly without support.  I don't see any reason that they need to be that pointy, though.  If the points were pulled back to be at a 45º overhang, they should print without support rather nicely.

This fixes the overhang, I think:
diff --git a/joiners.scad b/joiners.scad
index 38bdfa0..7cf7a98 100644
--- a/joiners.scad
+++ b/joiners.scad
@@ -754,8 +754,10 @@ module _pin_shaft(r, lStraight, nub, nubscale, stretch, d, pointed)
    down(extra) cylinder(r = r, h = lStraight + extra);
    up(lStraight) {
       zscale(stretch) {
-         sphere(r = r);
-         if (pointed) up(rPoint) cylinder(r1 = rPoint, r2 = 0, h = rPoint);
+         hull() {
+            sphere(r = r);
+            if (pointed) up(rPoint) cylinder(r1 = rPoint, r2 = 0, h = rPoint/stretch);
+         }
       }
    }
    up(d) yscale(nubscale) _pin_nub(r = r, nub = nub, h = lStraight - d);

I have printed it as it is and don't recall any problems.  It was based on a design that had been tested by multiple people, so I didn't change the design.  But I guess if you're certain it's an improvement and the pins will still fit well in the shaft....
Actually, your change seems to make almost no difference when a proper $fn value is used:
Original form:

With added hull():

Maybe what's needed is a minimum $fn constraint?
After inspecting different $fn values it looks like the pointy cap just doesn't actually fit properly to the rest.  At high $fn the discrepancy is small and hard to notice, but it's still there,  so adding the hull() is probably the easiest solution.


Manage Bucket Versioning

Support management of a bucket's versioning setting.

[ ] Allow setting versioning during bucket creation:

storage.bucket_create "new_todo_bucket", versioning: true

[ ] Allow getting values using a well named method.

bucket.versioning #=> false

[ ] Allow setting a new value using a setter method.

bucket.versioning = true

Calling this method makes an API call to update the value.

The getter will have a ?: bucket.versioning? #=> false

IMO it would be good for the getter to be without the ?, and have an alias with the ?.


remove useless lines for padding props

We did a css selector performance test which suggest us to remove the padding-top and bottom declarations, as they are overwritten by the padding shorthand property.

That seems reasonable.

Merged! Thanks @artebenji, and congrats on first PR merged


Tag.count does not work with number > 999

Actual result:
Tag.count('ahegao')
# => 37

Expected:
Tag.count('ahegao')
# => 37000

This bug should be in other classes too (Parody, Character, Category, Artist, Group, ...)

The fix will come with the next release


Add download possibility for images

@wow-such-code you could call/implement the download link generation in linkToImageDownload(long imageId)

This PR has to wait for a new release of the omero client lib.

@jenniferboedker we could also move your commits to another branch so that the basic functionality of the link is provided and you could replace it in your PR. What do you think?

This PR needs https://github.com/qbicsoftware/omero-lib/pull/12 to be in the omero-lib


Conflict with Google Meet Grid View (fix) extension

Device Information

Operating System: Windows 10 x64 Pro
Browser: Chrome v87.0.4280.141

Describe the bug
When trying to use this style along with this extension there's a conflict between them and the Grid extension doesn't work properly. It shows only 1 participant.

My style is written only in CSS so anything relating to JS such as only displaying one participant is out of my control.

My style is written only in CSS so anything relating to JS such as only displaying one participant is out of my control.


Improve README instructions. Fix #56

Add more instructions within README file of HelloWorld :

How to use kubernetes
How to install locally minikube
How to deploy on minikube.
Purpose of the README Example

@iocanel As the PR has been approved, can you merge it please ?


Running out of training time

I run out of training time on the Titanic dataset. A few thoughts here...

This is a popular dataset (starter dataset for Kaggle) and we should look into why our time prediction is too low. It'd be nice to make this more accurate.

I think the "Training time finished" should be an expected exception (shows the error warning dialog without stack trace.)  This is expected and we should update the message to say something like "Training time finished without any model trained. Try training for longer." Including the stack trace makes it look like something went wrong.

Why do I have an accuracy if the training didn't finish? Do we have a trained model but we haven't finished some step so its failing the whole run?

Dataset:
https://app.zenhub.com/files/186917455/5ea0b0dc-b431-436f-9ad9-55648ac93bb5/download

The same thing for me and there is also customer report  https://app.zenhub.com/workspaces/mlnet-tools-5cde1c97e3106e39e8ae08fc/issues/dotnet/machinelearning-modelbuilder/596

Accuracy after training is finished should be fixed after commit id 0d89134b1e1(Fix Dup Output), let me know if this bug appears after that commit

Tracking getting better training times in #672. Titanic dataset is mentioned
I updated the error message so it now looks like this
I haven't seen this problem recently, looks like Xiaoyun fixed it.

Closing directly as 2 is the only one that can be verified, and it already had been with another work item.


[ManifestLoader] Further restrict the sandbox profile

We don't need mach* and it is very unsecure because it allows
communication to processes like nsurlsessiond.
-- rdar://problem/31213658

@swift-ci please smoke test


add id translation

Description
Support Bahasa Indonesia translation
Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have run the pre-commit run command to format and lint.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] I have added my name and/or github handle to AUTHORS.rst
[x] I have added my change to CHANGES.rst
[ ] All new and existing tests passed.

Done @ddabble. Thanks for your response.

Your welcome :)


chore(client): remove useless config field in the model.yaml

Description
depends on: https://github.com/star-whale/starwhale/pull/1906
Modules

[x] Client

Checklist

[x] run code format and lint check
[x] add unit test
[x] add necessary doc

Remove the config field from the other docs, e.g.

README.md
client/tests/data/model.yaml
client/tests/data/model/model.yaml
docs/docs/tutorials/*.md

@jialeicui  updated


just --list  --exclude alias

I 'm defining lots of aliases for multiple commands
but this pollutes my default list-output,
filtering the output in windows looses the colored output
I would be nice to have an option to exclude aliases:
# list available recipes
default:
    @ just --list --justfile justfile --unsorted --no-alias

A flag seems fine too, if someone wants to open a PR.


Make pre-release versions of large_image for Girder 5

@zachmullen I used https://github.com/girder/girder/pull/3533 as a guide here.
Am I correct in thinking that since sub-directories here in large_image  (such as large_image/girder, large_image/girder/girder_annotation) have
version = get_version(root='..', local_scheme=prerelease_local_scheme)

a prerelease version will be available for those sub-packages?
My goal here is to make a prerelease version of girder-large-image-annotation available for HistomicsUI.


fix(magit): unbind M-1 etc. for code-review

code-review is built on magit-sections so it will have the same default
bindings for M-1, M-2 etc. To be consistent with the rest of doom, those
should be used for switching workspace and z1, z2 etc. should be used for
toggling outlines in a magit-sections buffer such as the code-review buffer.
This only affects users with :editor (evil +everywhere) enabled.

Had some issues with my git config email, hence the updates.

Great work! Thanks for your help!