Reported CPU usage is confusing

Command
cf app my_app
What occurred
The CPU usage is displayed as percentage, but nowhere it's defined what the percentage refers to. Users are puzzled by this, they often assume that the range is [0,100]%, whereas in reality, the range is [0,cores*100] where cores is a number they have no real visibility/control over since it's operator-defined.
In addition, this number does not reflect the CPU quotas at all, so whether e.g. "25%" means the application has a lot of idle resources or it is actually CPU-starved depends on:

the number of cores on the cell (operator controlled, user visible)
the container size (user controlled)
the mem->cpu quota mapping (operator controlled, non user visible)
other applications on the same cell (operator controlled, non user visible)

This means that currently the displayed CPU usage is basically not "actionable" at all, i.e. it doesn't tell users much about what's going on inside their application.
Extreme example of this: two instances with CPU usage that should have the same CPU usage because they handle the same workload:

instance 1: 200%
instance 2: 50%

Which instance is working correctly? Which one is not?

if we assume that the two instances are on two non-overloaded cells, most likely instance 1 has some issues because for the same workload uses 4 times as much CPU
if we know that instance 2 is on an overloaded cell so it's actually CPU-starved by other applications (i.e. instance 2 would like to use resources over its quota) then the problem is on instance 2

cf app myapp
Showing health and status for app myapp in org myorg / space myspace as<EMAIL_ADDRESS>name:              myapp
requested state:   started
instances:         5/5
usage:             2G x 5 instances
routes:            myapp.example.com
last uploaded:     Thu 30 Mar 10:30:01 JST 2017
stack:             cflinuxfs2
buildpack:         https://github.com/cloudfoundry/java-buildpack.git
      state     since                  cpu      memory         disk           details
#0    running   2017-07-28T11:26:45Z   22.7%    1.3G of 2G     200.6M of 1G
#1    running   2017-08-04T16:43:52Z   17.3%    1.3G of 2G     200.6M of 1G
#2    running   2017-08-02T04:15:21Z   19.5%    1.3G of 2G     200.6M of 1G
#3    running   2017-08-07T04:15:21Z   20.1%    775.1M of 2G   200.6M of 1G
#4    running   2017-08-05T16:28:55Z   155.2%   1.2G of 2G     200.6M of 1G

What you expected to occur
CPU usage should be relative to the CPU quotas assigned to the container: 100% should therefore map to "100% of the allocated quota".
Instances running over 100% should be highlighted in red because they are using best-effort resources that are not guaranteed to be available. User documentation should be updated to make this clear.
CLI Version
6.29.0
CC API Endpoint Version

2.74

Hi @CAFxX
Thanks for this feedback.
Where in the user documentation do you think this explanation would fit well and is easy to find? I'm sure the Docs team would appreciate a pull request from you.
Red in CLI output is reserved for errors that warrant user attention. I don't see how a usage of >100% due to best-effort resources require attention?
Note that the CLI is just displaying the numbers returned by CC. I can CC @zrob on this issue, but it might be more efficient to submit a feature request or issue to CAPI's issue tracker?
Regards,
Dies Koper
CF CLI PM

Where in the user documentation do you think this explanation would fit well and is easy to find? I'm sure the Docs team would appreciate a pull request from you.

I'm not sure what should we document exactly... The point I'm trying to make is that the CPU usage is not very useful from a user perspective and that we should replace it with something more actionable. Put it otherwise, this is not a documentation bug.
(if I really have to answer the question about where to put the documentation: I think I would argue that the most discoverable place for such documentation is cf app -help and the online docs - since I don't have access to the access stats of the docs I can't really argue whether priority should be given to the cli docs or the cf docs)

I don't see how a usage of >100% due to best-effort resources require attention?

Because an application that is routinely using over 100% capacity definitely needs scaling up/out or it is at risk of failing when the best-effort resources become unavailable (e.g. because a different application on the same cell starts spinning).

Red in CLI output is reserved for errors that warrant user attention.

This may not be an "error" but as I argued above it should definitely warrant not just user attention but likely user action (scale out/up)

Note that the CLI is just displaying the numbers returned by CC. I can CC @zrob on this issue, but it might be more efficient to submit a feature request or issue to CAPI's issue tracker?

This is a long standing issue with the CF project. When something as big as a user story (e.g. this ticket) is reported it normally doesn't include in its scope a single component (e.g. only cli or only capi) but rather many components (e.g. in this case probably at least cli and capi, maybe diego as well). But AFAIK there's no single issue tracker that can be used for this, so we're forced to open the issue, at least at first, on a somewhat arbitrary component (normally the one where the problem "surfaces" the most).
So yes, eventually this will have to propagate also to capi and likely beyond. But if we don't agree that the issue is also in the CLI (again, mostly because it's where it's more likely to surface) then there's no point in opening the corresponding issues in the other components.

Updated the "what to expect" section to make it clear that "over 100%" refers to the allocated quota discussed beforehand, not about the currently displayed number

I think I understand the issue(s), but not sure how to proceed. I don't have any stats on how/whether users refer to the cpu stats.
As you mentioned, currently the displayed CPU usage is basically not "actionable" at all, but in its current state it warrants user attention/action, there doesn't seem to be much we can do on the CLI side alone.
The CF Dev mailing list should be a better place to get the input from all relevant PMs and support from other users to prioritise an exploration around this?
Apologies for not taking ownership and driving this on your behalf: it seems you understand the issue much better and have ideas on how it should be, so it should be more effective if you lead the conversation with the relevant teams and users.

Adding a link to this thread for additional context: https://lists.cloudfoundry.org/g/cf-dev/topic/16273332

The Garden team (container runtime) have started work on a track which will:

change how CPU sharing is handled
produce a new metric which will (hopefully) make more sense in CLI metrics

You can check out our progress in our tracker by searching for the better-cpu-sharing tag.

Hi @Callisto13 @julz please could you provide a update to this issue? Thanks.

Hi @abbyachau
From cf-deployment v3.6.0 (garden-runc-release 1.16.3) operators can deploy with operations/experimental/set-cpu-weight.yml which will turn on the new way CPU shares are calculated in Garden.
From cf-deployment v7.8.0 (garden-runc-release 1.19.0), having deployed with the same ops file mentioned above, CLI users can install the CPU Entitlement Plugin to get accurate CPU metrics for their apps.
Please note that this is all still highly experimental and the user experience could yet change.

Thanks @Callisto13! Appreciate the update.
@CAFxX if you are not already and are able to update to the aforementioned version of cf-deployment please let us know what you think of the plugin. Let us know as well if you are happy to close this GitHub issue as there doesn't appear to be anything the CLI team can do at the moment until the plugin gains more traction for feedback and the Garden team are able to iterate on it.

I'll defer to @giner as, unfortunately, I'm not working on CF anymore.

cc @emalm for visibility.
@gsiener please let us know us know if you've been able to try the plugin. Thanks.

I think the request was intended for @giner.  Thanks

With the GA of the v7 CLI, we're no longer actively developing against the v6 line.  With an interest the overall hygiene of the CLI project we're closing this  issue.
If this issue is still occurring in v7 please feel free to comment and re-open. Thank you!

@heyjcollins hi,
is percentage in v7 in a range [0,100] or [0, cores*100] and is it relative to assigned CPU quota to an app?

The cli reports whatever CAPI https://v3-apidocs.cloudfoundry.org/version/3.86.0/index.html#the-process-stats-object reports back to us. You may want to reach out CAPI for more insights https://cloudfoundry.slack.com/archives/C07C04W4Q

@heyjcollins I don't believe this should have closed with V7

@univ0298 I think what Josh is trying to say is that the CF CLI displays an unfiltered version of what the CF [V3] API provides. In general, the CF CLI should not modify the contents of that data when presenting it to the user.
If an adjustment should be made, then it should be done on the API side so will be consistent with all API clients for the foundation. So it's better to file a ticket against the cloud controller instead of the CLI.

+1 for the issue. It's is especially unfortunate given how long the issue has been raised, and still not addressed.


2.03 upgrade bug?

Hi guys,
Your 2.03 AidStream is looking good! Great to have this released.
I'm trialing it on my test account and can't save existing activities due to an error with the Default Aid Type. I can't work out why this error is occurring.
My test account is:

Could you please take a look your end? Or let me know where I've gone wrong.
Many thanks, Amy

Hi Amy,
On checking, I found that the issue occurred only for Activities which was Imported from XML file in version 2.02 and then the system was upgraded to 2.03.
We have fixed the issue and now you can save the Activity.
Thank you for letting us know about the issue.


[wire] Close + Serialization error reporting

Details in #411 and #425

Coverage decreased (-0.2%) to 63.618% when pulling 9144a7076e8d4a5a7eca3c17a671114c692d89c6 on sid1607:master into 1e6ce707355e06b30a48dbc244b1a1a0c367b6d8 on cmu-db:master.

Coverage decreased (-0.3%) to 63.426% when pulling e83cccfd3ebb531ee0ebb2c1aa76f465aab04b9d on sid1607:master into 1e6ce707355e06b30a48dbc244b1a1a0c367b6d8 on cmu-db:master.


Fix spelling errors ('Position', not 'Postition')

Just a small spelling error I came across!

Thanks! It turns out this is actually a typo in one of the npm modules we're using, geojson-validation, which gets pulled into our client-only embed.js bundle. If you want to fix the problem at the source, check out https://github.com/craveprogramminginc/GeoJSON-Validation/blob/8083612b5d5eb0d8a8035487c8ccb9ab3e80972e/index.js#L120-L128

Done.
No updates for that repo in over a year--we'll see if someone answers. Thanks!

Nice!


Various Labs: Minor issues – extra spaces, missing periods, upper case consistency

A recent QA of this series noted multiple issues in the Instructions that can be considered 'cosmetic':  They do not lead to blocking in completion of the labs, however I wanted to call them out so that if the CO wishes to do a pass through the markdown at a future date to correct them they will be aware and have some references.  The screenshots below are not specifically from this course, but meant to be an example of this minor issue.
Extra space:

Seen in Labs: 4, 9, 12

Missing full stop (period):

Seen in Labs: 1, 2, 6-8, 11, 12

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

https://github.com/MicrosoftLearning/AZ-204-DevelopingSolutionsforMicrosoftAzure.fr-fr/blob/master/Instructions/Labs/AZ-204_lab_01.md
https://github.com/MicrosoftLearning/AZ-204-DevelopingSolutionsforMicrosoftAzure.fr-fr/blob/master/Instructions/Labs/AZ-204_lab_02.md


getChats returns null

I'm wondering, why getChats returns null (logged in as user, not bot)?

@levlam - thanks, I found the problem.
I used wrapper around tdlib to send requests. And there was a problem with error handling


[xlnt] Add missing include

Fix https://github.com/microsoft/vcpkg/issues/23635
Add patch to include limits in number_formatter.cpp. see https://github.com/tfussell/xlnt/pull/617

Thanks for your contribution!


CDN rate limit clarification

Resolves PDOCS-2746. Updates CDN doc strings with rate limit clarifications.

This is covered up in the general rate limit section in the introduction, but documenting it closer to the specific endpoint makes sense.


[Bug] Icon missing when searching start menu

Windows Terminal version (or Windows build number)
Version: 1.7.1033.0
Other Software
No response
Steps to reproduce
I'm reinstall my Windows to latest version (21h1 build 19043.985) and download Windows 10 Terminal from microsoft store
Expected Behavior
It should be show icon popup on Start menu but result is give me this blank icon
Things i tried:

Reset icon.DB
Download and reinstall Terminal

Actual Behavior

Do you happen to have Google Drive installed?

This might be the thread that was mentioned in triage
https://superuser.com/questions/1319157/some-windows-10-uwp-icons-not-displaying-on-search-or-in-settings

I'm sorry for late reponses. But i already fix it by re-installing the latest version of Windows. Thanks you.


Training on new fonts without changing the lstm model using finetunned model

Tesseract Version: 4
Commit Number:  I assume the default one
Platform: <!-- linux ubuntu 18.04

I have finetuned  the Hebrew LSTM model and used tesstrain.sh to train  for approximately  3 fonts.
I am not sure about few things mentioned below:

does the default model  Hebrew model has been trained on the fonts listed in the file okfonts?
Is there a way to continue training the model on fonts only keeping the work the lstm achieved
given that i specified my own custom word list while I was  fine tuning the lstm model  has the default word dict been overridden?
while  testing the model,  given that I have specified my own training test and word list during  the lstm training, is it necessary to specify my word custom word_dict  if i want to toggle language_model_penalty_non_dict_word to be true.

Thanks in Advance

does the default model Hebrew model has been trained on the fonts listed in the file okfonts?

The models in tessdata_fast and tessdata_best should be trained on the okfonts in langdata_lstm.

Is there a way to continue training the model on fonts only keeping the work the lstm achieved

I think the option of 'finetune for impact' keeps the original traineddata and makes minimal changes required for a new font.

given that i specified my own custom word list while I was fine tuning the lstm model has the default word dict been overridden?

The plusminus and replace layer training allow for custom word lists, and so the original word list will be overridden.

while testing the model, given that I have specified my own training test and word list during the lstm training, is it necessary to specify my word custom word_dict if i want to toggle language_model_penalty_non_dict_word to be true.

That parameter was effective with Legacy Tesseract. I am not sure how useful it will be with the LSTM models.

@zdenop Please label as question and close.


predictive_explorer with bambi model KeyError

Describe the bug
I just installed the package and tried the docs example for predictive_explorer with a bambi model. I get a KeyError: 'a_mu'.

To Reproduce
The notebook to reproduce the error is just the code in the docs but I attach it anyway.
import preliz as pz
import numpy as np
import bambi as bmb
import pandas as pd

data = pd.DataFrame(
    {
        "y": np.random.normal(size=100),
        "x": np.random.normal(size=100),
    }
)
def a_bambi_model(a_mu, a_sigma):
    prior = {"Intercept": bmb.Prior("Normal", mu=a_mu, sigma=a_sigma)}
    a_model = bmb.Model("y ~ x", data, priors=prior)
    return a_model

pz.predictive_explorer(a_bambi_model)

Additional context
I'm using
llvmlite-0.42.0
numba-0.59.1
preliz-0.7.0
ipympl-0.9.4
ipython-genutils-0.2.0
nbclient-0.5.13

The documentation is reflecting changes on the main branch not yet released. It should work if you install from main.

A new version has been released. The example should work. Notice that the Bambi and PyMC features for predictive_explorer are very new and still under development. If you find bugs we would love to hear about them. Thanks

thank you very much @aloctavodia !
Now it works. It still breaks with a multilevel model but I guess you already know and it's expected since it's under development.

Hi @andins do you mean it fails with a multilevel Bambi's model?


Help with message serialization

PyKafka version: '2.7.0'
Kafka version: Latest
Hello,
I am trying to use pickle to serialize the messages that I am producing.
with topic.get_sync_producer( max_request_size=21000012) as producer:
    #producer.produce(unp)
    producer.produce(pfile)

with pickle this is how I serialize my messages:
pfile = pickle.dumps(data, pickle.HIGHEST_PROTOCOL)

How can I use pickle for that and not utf-8?
Thanks

@georgeha If you're asking about the serializer interface on the Producer, it's a convenience but not a necessity. Without it, you can do something like this to serialize your messages:
with topic.get_sync_producer( max_request_size=21000012) as producer:
    for data in generate_data():
        pfile = pickle.dumps(data, pickle.HIGHEST_PROTOCOL)
        producer.produce(pfile)

If you wanted to implement this logic as a serializer function, you could follow the example implementation, replacing calls to encode with calls to pickle.dumps.
Please comment or reopen if you have additional questions, and thanks for using pykafka.


Move CheckPoint firewalls to BYOL in Forge

Describe the Issue
We want to consolidate our CheckPoint licensing through SecOps, to do that we need to move from on-demand licensing to "bring your own license" (BYOL)
Additional Context

The firewalls are deployed and managed by the ASEA and can be configured in the config.json

Acceptance Criteria

[ ] Backup forge management server
[ ] Update management server to use BYOL AMI
[ ] Update the gateways to use BYOL AMI
[ ] Restore management server data post update

Blocked waiting for the Check Point licensing

Thanks for the update @wrnu, when do you expect to get licensing from CheckPoint? Anything else we can do to help unblock this?

Writing for procurement. ETA March 2024


Query Result Iterator

Hello sqlc folks, this package does really give a peace of mind, thanks!! :+1:
I noticed that you are tagging query return cardinality: :exec (aka none), :one, :many. In the latter, :many, have you ever considered the case in which the whole result doesn't fit in memory? Apart from using DB.QueryContex is there any typed work-around?
Keep up the great work,
Enrico Bonetti Vieno

I haven't tackled the case where query results don't fit into memory. If I was writing the queries, I'd fix it by doing paging myself with filtering and limits. However, I get that there are times when you'd rather just stream the results.
I could imagine a world where tag a query :iter and generate code like this:
-- name: StreamAuthors :iter
SELECT * from authors;

package db

const listAuthors = `-- name: StreamAuthors :many
SELECT id, name, bio FROM authors
ORDER BY name
`

type AuthorStream struct {
  rows *sql.Rows
}

func (s *AuthorStream) Next() bool {
    return s.rows.Next()
}

func (s *AuthorStream) Close() error {
    return s.rows.Close()
}

func (s *AuthorStream) Err() error {
    return s.rows.Err()
}

func (s *AuthorStream) Scan() (Author, error) {
    var i Author
    return i, rows.Scan(&i.ID, &i.Name, &i.Bio)
}

func (q *Queries) StreamAuthors(ctx context.Context) (*AuthorStream, error) {
    rows, err := q.db.QueryContext(ctx, listAuthors)
    if err != nil {
        return nil, err
    }
    return &AuthorStream{rows}, nil
}

Paging, I didn't think about it.. 🤔 As for our parallel world, maybe even a closure iterator could work:
package db

const streamAuthors = `-- name: StreamAuthors :iter
SELECT id, name, bio FROM authors
ORDER BY name
`

func (q *Queries) StreamAuthors(ctx context.Context) func() (Author, error) {
	rows, queryErr := q.db.QueryContext(ctx, streamAuthors)
	if queryErr != nil {
		return func() (Author, error) {
			return Author{}, queryErr
		}
	}

	return func() (a Author, err error) {
		if !rows.Next() {
			return Author{}, rows.Err()
		}

		return a, rows.Scan(&a.ID, &a.Name, &a.Bio)
	}
}

The closure iterator won't work as written since you need to expose a Close method. Maybe you could return two funcs?

Yesterday I checked: it doesn't really say "Close must be called".. 😜
To close prematurely I would use the context: to me this context use feels right since the closure is a way to iteratively explore the context call results. How do you feel about it?
package db

const streamAuthors = `-- name: StreamAuthors :iter
SELECT id, name, bio FROM authors
ORDER BY name
`

func (q *Queries) StreamAuthors(ctx context.Context) func() (Author, error) {
	rows, queryErr := q.db.QueryContext(ctx, streamAuthors)
	if queryErr != nil {
		return func() (Author, error) {
			return Author{}, queryErr
		}
	}

	ctx, cancel := context.WithCancel(ctx)
	go func() {
		<-ctx.Done()
		rows.Close() //Close is safe for concurrent use.
	}()

	return func() (a Author, err error) {
		if !rows.Next() {
			//Cancel used to terminate child context, Close already called by Next.
			cancel()
			return Author{}, rows.Err()
		}

		return a, rows.Scan(&a.ID, &a.Name, &a.Bio)
	}
}

The above code snippet still has concurrency issues. Since the cancel function isn't returned, a caller would need to continue to call the returned function until rows.Next returns false. The complexity of the returned closure leads me to believe sqlc shouldn't generate this type of code right now.
If more people need this functionality, we can revisit this in the future.

I probably would not use it in production myself: even if Rows itself owns a connection to the database, so it's not really lightweight, still using the goroutine feels like an overkill.
There was a problematic corner case: say Scan returns an error, the caller would stop calling the iterator, then the goroutine would become a zombie until context cancellation, which wouldn't be otherwise required. Thanks for noticing.
package db

const streamAuthors = `-- name: StreamAuthors :iter
SELECT id, name, bio FROM authors
ORDER BY name
`

func (q *Queries) StreamAuthors(ctx context.Context) func() (Author, error) {
	rows, queryErr := q.db.QueryContext(ctx, streamAuthors)
	if queryErr != nil {
		return func() (Author, error) {
			return Author{}, queryErr
		}
	}

	ctx, cancel := context.WithCancel(ctx)
	go func() {
		<-ctx.Done()
		rows.Close()
	}()

	return func() (a Author, err error) {
		if !rows.Next() || rows.Scan(&a.ID, &a.Name, &a.Bio) != nil {
			cancel()
		}
		return a, rows.Err()
	}
}

Given that Rows is concurrent safe, I don't see any other concurrency issues, so this code should work like a charm:
	ctx, cancel := context.WithCancel(context.Background())
	defer cancel()

	next := q.StreamAuthors(ctx)

	var a Author
	var err error
	for a, err = next(); err != nil; a, err = next() {
		//Do something with a
		if stopCondition {
			break
		}
	}

If more people need this functionality, I'm more than happy to help with the interface design.
Keep up the great work,
Enrico Bonetti Vieno

Hi, sorry for bumping a closed issue. What if :iter generated something like
const streamAuthors = `-- name: StreamAuthors :iter
SELECT id, name, bio FROM authors
ORDER BY name
`

type streamAuthorsIter func(author Author) error

func (q *Queries) StreamAuthors(ctx context.Context, iter streamAuthorsIter) error {
	rows, err := q.db.QueryContext(ctx, streamAuthors)
	if err != nil {
		return err
	}
	defer rows.Close()

	for rows.Next() {
		var a Author
		if err := rows.Scan(
			&a.ID,
			&a.Name,
			&a.Bio,
		); err != nil {
			return err
		}

		err = iter(a)
		if err != nil {
			return err
		}
	}
	if err := rows.Close(); err != nil {
		return err
	}
	if err := rows.Err(); err != nil {
		return err
	}
	return nil
}

Compared to :many its basically adding a func type and calling the passed iter function instead of appending.

@eivindr maybe you can just open the PR and we can continue the discussion there?


Added cloud folder variable and protection against removing protected backup files

Added cloud folder variable
Protection against removing protected backup files

thanks for the contribution!


removed lines from setup.py

Description
Tidying up some of the original files from minigrid and also simplifying setup.py

changed as intended - newer gym version will not be imported now. Need to check this still works on creation of entirely new environment.


Sound effects, music, and directory cleanup

I added a hop sound effect that plays whenever the player hops. I also added music that plays continuously in the background of the game. Since the sounds were in their own file within assets, I thought it would be cleaner to put the images in their own directory within assets, so I moved them and fixed the asset dictionary to account for this. Finally, I updated the player movement unit test to account for the new sound effect parameter in the movement function.

LGTM


CFE-752: Feature/extend operator API to include override of args and env of operand

Description
This PR implements #93 to allow overriding container args and environment variables for the operand pods. Order of applying the overrides are,

The args and env vars from override deployment configs are applied. (validation is only done for these args and envs)
The args from unsupported config are applied on to of these args.

pkg/controller/deployment/deployment_overrides_validation.go : Adds validation hooks for validating allowed args and env variables.
pkg/controller/deployment/deployment_unsupported_overrides.go : Adds override hooks for unsupported config overrides.
pkg/controller/deployment/deployment_overrides.go : Adds hooks for overriding container args and environment variables.
test/e2e/cert_manager_deployment_test.go : Adds e2e test to verify validation and override functionality.

/hold until #93

/label tide/merge-method-squash

/test e2e-operator

/lgtm

/label px-approved

/cc @bergerhoffer @xingxingxia

/remove-hold
/test e2e-operator

/test all

/label qe-approved

/test e2e-operator

/retest

/test e2e-operator

/lgtm

/label docs-approved

Fixes CM-11


Error when fragments are separated

Currently when fragments are stored separately from queries and mutations, the codegen produces a "Unknown fragment ..." error.
Example:
fragment.ts
import gql from 'graphql-tag';

export const userInfo = gql`
  fragment UserInfo on User {
    id
    name
    email
  }
`;

query.ts
import gql from 'graphql-tag';

import { userInfo } from './fragment.ts';

export const userQuery = gql`
  query UserQuery($id: ID!) {
    user(id: $id) {
      ...UserInfo
    }
  }

  ${userInfo}
`;

For now, we released an alpha version with a fix for this:
Successfully published:
 -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS>
@ganeshpms

Run into this as well but the alpha builds resolve it. Thanks.

#559 should fix it for apollo-angular template

Thanks for the Alpha versions.
Error: Property 'definitions' does not exist on type '{ new (): Document; prototype: Document; }' with Alpha version on the generated code. Which version of typescript is recommended?

As seen in the attachment the Document is conflicting with the typescript's dom Document type. Please add the *namepace*.Docuemnt.definition. Also, the generated code adds the same fragment multiple time as  I have used the fragment 'Measurement' in multiple places in my query. And finally , is missing when there are two are more fragments.

I'm getting the same issues with fragments, every query gives me the error.
`ERROR in src/client/app/core/graphql.ts(3064,3):
error TS2416: Property 'document' in type 'AllChatsGQL' is not assignable to the same property in base type 'Query<Query, Variables>'.
[2]   Type '{ kind: string; definitions: any[]; }' is not assignable to type 'DocumentNode'.
[2]     Types of property 'kind' are incompatible.
[2]       Type 'string' is not assignable to type '"Document"'.
[2]
src/client/app/core/graphql.ts(3066,31): error TS2339: Property 'definitions' does not exist on type '{ new (): Document; prototype: Document; }'.
[2] src/client/app/core/graphql.ts(3087,3): error TS2416: Property 'document' in type 'ChatByIdGQL' is not assignable to the same property in base type 'Query<Query, Variables>'.
[2]   Type '{ kind: string; definitions: any[]; }' is not assignable to type 'DocumentNode'.
[2]     Types of property 'kind' are incompatible.
[2]       Type 'string' is not assignable to type '"Document"'.
[2]
src/client/app/core/graphql.ts(3089,31): error TS2339: Property 'definitions' does not exist on type '{ new (): Document; prototype: Document; }'.
[2] src/client/app/core/graphql.ts(3109,3): error TS2416: Property 'document' in type 'SaveChatGQL' is not assignable to the same property in base type 'Mutation<Mutation, Variables>'.
[2]   Type '{ kind: string; definitions: any[]; }' is not assignable to type 'DocumentNode'.
[2]     Types of property 'kind' are incompatible.
[2]       Type 'string' is not assignable to type '"Document"'.`

@kamilkisiela I am using apollo-angular

@ganeshpms do you use noGraphqlTag option?

I am also using apollo-angular, I am not doing the 'noGraphqlTag',
"apollo-angular": "^1.3.0",
I was getting the errors using:

along with trying to use fragments.
<EMAIL_ADDRESS><EMAIL_ADDRESS>

Fixed in 0.12.0

@kamilkisiela , I am not using noGraphQLTag.
The versions are
"graphql-code-generator": "^0.12.0-alpha.821f12df",
"graphql-codegen-apollo-angular-template": "^0.12.0-alpha.821f12df",
Also, the issue #4 that I mentioned is resolved by using #import './fragment/measurement.gql' other fixes for #1,#2, #3 are still needed. I just mannually fix them after generated.

I'm getting this error.  Version 1.0.6 with 1.0.6 versions of typescript and typescript-react-apollo
Works
// query.ts

const DealFragment = gql`
  fragment DealFragment on Deal {
    id
  }
`

const DEALS_FOR_VEHICLE = gql`
  query dealsForVehicle($vehicleId: ID!) {
    deals(where: { vehicles_every: { id: $vehicleId } }) {
      __typename
      ...DealFragment
    }
  }
  ${DealFragment}
`

// query.ts

import gql from "graphql-tag"
import { DealFragment} from "./dealFragment"

const DEALS_FOR_VEHICLE = gql`
  query dealsForVehicle($vehicleId: ID!) {
    deals(where: { vehicles_every: { id: $vehicleId } }) {
      __typename
      ...DealFragment
    }
  }
  ${DealFragment}
`

// dealFragment.ts
import gql from "graphql-tag"

export const DealFragment = gql`
  fragment DealFragment on Deal {
    id
  }
`

Returns
$ graphql-codegen --config codegen.yml
  ✔ Parse configuration
  ❯ Generate outputs
    ❯ Generate src/generated/graphql.tsx
      ✔ Load GraphQL schemas
      ✔ Load GraphQL documents
      ✖ Generate
        → Cannot read property 'onType' of undefined

 Found 1 error

  ✖ src/generated/graphql.tsx
    TypeError: Cannot read property 'onType' of undefined

codegen.yml
overwrite: true
schema: "../admin-server-nexus/src/generated/schema.graphql"
documents:
  - "src/containers/deals/**/*.tsx"
  - "src/containers/queries/**/*.tsx"
generates:
  src/generated/graphql.tsx:
    plugins:
      - "typescript"
      - "typescript-operations"
      - "typescript-react-apollo"

Thanks for the amazing work!

@LawJolla In 1.0.7 we fixed that, now you'll get a more readable error with the missing fragment name.
If you are still having issues, please open a new issue because this one is closed and outdated.


Configuration export/import for multiple instances

Feature request

What problem does this feature solve?
(issue appears on 2.0.0-alpha.5 (HEAD detached at e3587923) (Paulchen-Panther-2e83c587/e3587923-1587148622))
If you have multiple instances defined, you need to export a configuration for each instance.
The name of the exported file does not contain a hint on the exported configuration.
What does the proposed API look like?

How should this be implemented in your opinion?
I see two options:

Make the documentation of configuration export more precise. It needs to state that it's only exporting the currently selected instance. The exported filename should contain the instance name.
Provide a complete configuration export, that contains all instances. (And of course an import function for a full configuration)

Are you willing to work on this yourself?
No

This is a issue that was indeed introduced with the instance feature. Some adjustment are required to.

Looking for this too :)

my raspberry pi software was not working right. I had exported configuration regularly with any changes.  I thought I would be fine. Never in my wildest dreams did I imagine that it was only exporting the current instance.  If you have multiple lights like I do one naturally thinks it exports all of them. I now have to re-setup all but my main TV lights.  This is a 4 year old thread seems like an important thing to have worked on in 4 years. Not that I am not thankful of all the work that has gone into this, but this is a pretty big deal.


Switch to Eris

This will allow me to directly copy from esmBot. Ideally, the end user will not notice the bot has switched, besides the improved performance.


Safari 16.2 & 16.3

the old obligatorily issue:
Safari & Safari on iOS 16.2 have been released

https://developer.apple.com/documentation/safari-release-notes/safari-16_2-release-notes
https://www.macrumors.com/2022/12/13/apple-releases-ios-16-2/

Safari & Safari on iOS 16.3 are coming

https://www.macrumors.com/2022/12/14/apple-seeds-ios-16-3-beta-1-to-developers/
Safari 16.3 seem to be pending

Safari 16.3 release notes are here now:
https://developer.apple.com/documentation/safari-release-notes/safari-16_3-release-notes
@Fyrd has already updated the website, but without adding 16.3 to the files? 🤔
Is there git push missing perhaps? 🙃

@Schweinepriester Oops, yeah something went a little wonky recently, I think it's good now.

looking good indeed :)


App crashes on startup due to missing backend urls (leads to uncaught okhttp exception)

Describe the bug
The app built from https://github.com/corona-warn-app/cwa-app-android/commit/16f016a99b971d89e9f4c988c4ce8f7421f9983d crashes on startup.

Expected behaviour
It should not crash and instead show some kind of error message.

Steps to reproduce the issue

Build and run the app from commit https://github.com/corona-warn-app/cwa-app-android/commit/16f016a99b971d89e9f4c988c4ce8f7421f9983d
Technical details
n/A
Possible Fix
The reason for this crash are the missing backend URLs. OkHTTP is expecting valid URLs starting with http:// or https://. Since the update check is invoked on startup, the app crashes immediately.
However, the uncaught exception is the real reason for the crash.
Additional context
Excerpt from Logcat:
java.lang.ExceptionInInitializerError at de.rki.coronawarnapp.service.applicationconfiguration.ApplicationConfigurationService.asyncRetrieveApplicationConfiguration(ApplicationConfigurationService.kt:9)         at de.rki.coronawarnapp.update.UpdateChecker.checkIfUpdatesNeededFromServer(UpdateChecker.kt:122)         at de.rki.coronawarnapp.update.UpdateChecker.checkForUpdate(UpdateChecker.kt:35
[...]
Caused by: java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but no colon was found         at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1260)

Resolved in latest Dev


Add to do features in the app

Created a react-based todo app
Added feature to add todos
Added feature to mark the completed item
Added delete todos from the todo list
Added feature to edit the todo items

Hi @lenkon , 👋
STATUS: Approved  🎉
Great work on making the changes requested by a previous reviewer :1st_place_medal:
Your project is complete!  There is nothing else to say other than... it's time to merge it
Congratulations! 🎉  🎉 🎉

To Highlight :1st_place_medal:

Your Pull Request has a proper title and description. ✔
All the requirements listed on the project :heavy_check_mark:

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me on( @ridabensalem ) in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Hi @ridabensalem ,
Thanks for the review.
Best regards,
K. Inoulen Shanongba


[Suggestion] Add one more parameter on config files

Note: This repository is ONLY used to solve issues related to DOCS.
For other issues, please move to other repositories.

Is there anything that's missing or inappropriate in the docs? Please describe.
One more parameter is added to milvus to control which tables will be loaded to memory at milvus startup.
Describe your suggestion
Please check with developer on the usage of this parameters
Additional reference
No

Got it. Will add it in the next release.

#78 Already added the parameter preload_table in branch 0.5.0.


Issue with whitespaces on metadata options

I think that node-fluent-ffmpeg  have issue with whitespaces on -metadata values.
This is my code:
.outputOptions([
        '-i',
        __dirname+'/downloads/'+videoName+'.png',
        '-map 0:0',
        '-map 1:0',
        '-c copy',
        '-id3v2_version 3',
        '-metadata artist='+artistName,
        '-metadata title='+trackName,
        '-metadata album='+collectionName,
        '-metadata composer='+artistName,

    ])

but when i try this, ffmpeg return a error
Unrecognized option 'metadata artist="Alan Walker"'.
Error splitting the argument list: Option not found

But if i remove the  variables whitespaces with .replace(/ /g,'') it works.

You have to quote them.

@njoyard you can give me an example?

ffmpeg uses single quotes for quoting so that would be artist='Alan Walker'. Additionnally if you want to pass spaces to ffmpeg you cannot use the legacy '-option arg' syntax with fluent-ffmpeg, you have to pass them as separate arguments :
.outputOptions(
  "-map", "0:0",
  "-metadata", "artist='Alan Walker'"
);

And finally don't pass input (-i filename) or codecs (-c copy) to outputOptions ! Use the fluent-ffmpeg API. There's no point in using fluent-ffmpeg if you're building the command line yourself.

Working :+1:

Interestingly, in the latest version (2.1.2) there is no need to quote the metadata values. However, this works only when you pass parameters as values, not as array. Seems it's due to the splitting in this line: https://github.com/fluent-ffmpeg/node-fluent-ffmpeg/blob/master/lib/options/custom.js#L113.

Interestingly, in the latest version (2.1.2) there is no need to quote the metadata values. However, this works only when you pass parameters as values, not as array. Seems it's due to the splitting in this line: https://github.com/fluent-ffmpeg/node-fluent-ffmpeg/blob/master/lib/options/custom.js#L113.

You just saved me a life, thank you. I've spend about 2 hours trying to understand what's wrong, but yeah, passing them as arguments not array works fine.

Glad it helped. That's why we share our findings — to build a knowledge base for each other. :pray:


Media Codec video render error

Bug
"react-native-video": "^5.2.0",

See screenshot for detailed error log
Video play for first time fine but it start throwing this error when played 3rd time in a row.

Platform

Which player are you experiencing the problem on:

Android

Environment info

React native info output:
System:
    OS: macOS 11.1
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
    Memory: 96.88 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 15.5.1 - /usr/local/bin/node
    npm: 7.3.0 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK:
      API Levels: 23, 26, 28, 29, 30, 31
      Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.3
      System Images: android-25 | Google APIs Intel x86 Atom, android-29 | Android TV Intel x86 Atom, android-30 | Android TV Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
  IDEs:
    Android Studio: 4.1 AI-201.87<IP_ADDRESS>53283
    Xcode: 12.4/12D4e - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.5 => 0.61.5
  npmGlobalPackages:
    react-native-cli: 2.0.1

Library version: x.x.x
Steps To Reproduce

Download 2,3 video using react native fs, save to file system.
when played on one after another it gives Unable to instantiate decoder OMX.MTK.VIDEO.DECODER.AVC error.

...
Reproducible sample code

Video sample
Any video downloaded in file system

This issue is typically due to issue in codec release from player.
Are you able to reproduce the issue with sample ? maybe with a patched version of basic sample in the repo ?!

Hi @rohitsingh2410
If you could answer some questions you can help move this issue along.
Have you tried 5.2.1 or any of the v6 alphas?
Are you looping the video?
Can you share some sample code?
If you have fixed it yourself in some way please let us know or close the issue. Thank you 🙂

Good night, I have the same problem on android.

the video plays, but handle error
get the code from react-native-video-test
const renderError = () => {
if (!hasError) {
return null;
}
return (
  <View style={styles.errorContainer}>
    <Image
      resizeMode={'contain'}
      source={{
        uri: 'https://media.istockphoto.com/id/1214467889/video/the-inscription-404-not-found-makes-a-glitch-system-error-motion-graphics.jpg?s=640x640&k=20&c=bipJvdvw02szLppAnxxrZC602tQJDP3jN-O7svgOLfo=',
      }}
      style={styles.errorImage}
    />
  </View>
);

};
const renderLoad = () => {
if (loading) {
return (

<ActivityIndicator size={'large'} color={colors.text} />

);
}
};
const onLoadStart = () => {
setLoading(true);
};
const onLoadHandler = data => {
console.log(data, 'opo');
setLoading(false);
};
const onError = e => {
console.log(e, 'rere');
console.log('error');
setHasError(true);
setLoading(false);
};
const bufferConfig = {
minBufferMs: 100,
maxBufferMs: 50000,
bufferForPlaybackMs: 100,
bufferForPlaybackAfterRebufferMs: 100,
};
const isPlay =
isFocused && !autoplay ? currentIndex !== currentVisibleIndex : true;
const autoPlayNoActive =
autoplay === undefined ? true : currentIndex !== currentVisibleIndex;
const drawerOpen = isDrawerOpen ? true : currentIndex !== currentVisibleIndex;
return (

<Video
style={styles.video}
ref={primaryRef}
resizeMode={'contain'}
controls={true}
repeat={true}
paused={isPlay || drawerOpen || autoPlayNoActive}
rate={1.0}
onLoadStart={onLoadStart}
onLoad={onLoadHandler}
onError={onError}
progressUpdateInterval={250}
bufferConfig={bufferConfig}
source={{
uri: uri,
}}
/>
{renderLoad()}
{renderError()}

);

I faced with that problem at 5.2.1 and v6-alpha3 (tested at tv box).

Can you try following patch: https://github.com/react-native-video/react-native-video/pull/3416
It should improve behavior in case of decoder issue

To be retested on beta.6


Fix flaky nixosTests.keymap

Description of changes
Flaky test impede releasability.
Closes #207181 until a new problem is found.
See commit descriptions for details.
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/)
23.05 Release Notes (or backporting 22.11 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.

@ofborg test keymap.azerty keymap.colemak keymap.dvorak-programmer keymap.dvorak keymap.neo keymap.qwertz

No timeout on ofborg. Let's try hydra!


Mare builds with Crystal 1.0.0

Would be great to be able to compile Mare with Crystal 1.0.0.

Looks like you may have already started on this (given your changes in the crystal-lsp repo, so I'm provisionally assigning you to this ticket). Let me know if you want to be unassigned.

@jemc I thought this would be simple, but I am running into hundreds of type errors :(
I could fix some of them, but this looks more like a regression in Crystal 1.0.0.
For instance I had to add these type annotations:
--- a/src/mare/compiler/interpreter/default.cr
+++ b/src/mare/compiler/interpreter/default.cr
@@ -12,12 +12,12 @@ class Mare::Compiler::Interpreter::Default < Mare::Compiler::Interpreter
       "kind" => "keyword",
       "name" => "keyword",
       "value" => "import",
-    },
+    } of String => String | Bool,
     {
       "kind" => "term",
       "name" => "path",
       "type" => "string",
-    },
+    } of String => String | Bool,

Otherwise, Crystal thinks the Mare::Witness takes an Array(Hash(String, String) | Hash(String, String | Bool)), where
it really should be Array(Hash(String, String | Bool)).
If you have crystal 1.0.0 installed, you can see yourself. Let me know if you have any idea how to fix that.
This is the updated shards.yml:
$ git diff shard.yml
diff --git a/shard.yml b/shard.yml
index e99cf24..1bc7f62 100644
--- a/shard.yml
+++ b/shard.yml
@@ -12,11 +12,12 @@ dependencies:
   pegmatite:
     github: jemc/crystal-pegmatite
   lsp:
-    github: jemc/crystal-lsp
+    github: mneumann/crystal-lsp
+    branch: convert-to-json-serialize
   clim:
     github: at-grandpa/clim
     version: 0.13.0

-crystal: 0.26.1
+crystal: 1.0.0

And I am running crystal build main.cr.
For WIP, see my commit on this branch: https://github.com/mneumann/mare/tree/works-with-crystal-1.
Crystal's error reporting is all but optimal for these kind of errors :/.

You actually already finished most of the heavy lifting on your branch!
There were only a few other source code changes I had to make: https://github.com/jemc/mare/pull/87/commits/5fd86e6293780f038b3b127f04dfab8d2159acf5
And apart from that I committed the content of shards install because I like to keep all that in the git tree and avoid forcing the compiler devs to have Crystal on their system to run shards install (no Crystal is required on the host system because we run all standard development workflow stuff within docker.
And lastly I updated the Dockerfile to use latest alpine, which has Crystal 1.0.0 on it.
Thanks for all the help! Let me know if there are other tickets you want to work on here, or other tickets you'd like to create.

@jemc thanks for finishing that work!
I can now compile Mare on FreeBSD with Crystal 1.0. Running compiled Mare programs still crash, probably due to issues with libponyrt. I'd love to be able to try out Mare without having to resort to Docker (not available on FreeBSD).

Thanks, I wasn't aware of Docker not being available on FreeBSD.
It's definitely a goal to get Mare more easily distributable to various platforms. At the start I saw Docker as an easy temporary shortcut, since it's available on many platforms.
I'll open a new ticket to work on getting instructions and/or automation up for running the Mare compiler and its compiled programs outside of Docker. Maybe you can assist with the FreeBSD side of things. I'll ping you in that ticket after I create it.


undefined reference to  OPENSSL_init_crypto

error info:
CMakeFiles/koala.dir/Recognition.cpp.o: In function `TUPU::read_public_key(std::string const&)':
Recognition.cpp:(.text._ZN4TUPUL15read_public_keyERKSs+0xbc): undefined reference to `OPENSSL_init_crypto'

LIBS info:
-lcurl -lssl -lcrypto -lz

I grep with the command grep -nR "OPENSSL_init_crypto" . in lib path,  not strip, but found nothing!
source code:
static RSA * read_public_key(const string & pubkeyStr)
{
    BIO *bio = NULL;
    RSA *rsa = NULL;
    char *chPublicKey = const_cast<char *>(pubkeyStr.c_str());

    if (NULL == (bio = BIO_new_mem_buf(chPublicKey, -1))) {
        fprintf(stderr, "BIO_new_mem_buf failed!\n");
        return NULL;
    }

    rsa = PEM_read_bio_RSA_PUBKEY(bio, NULL, NULL, NULL);
    if (!rsa) {
        ERR_load_crypto_strings();
        char errBuf[512];
        ERR_error_string_n(ERR_get_error(), errBuf, sizeof(errBuf));
        fprintf(stderr, "Failed to load public key [%s]\n", errBuf);

        BIO_free_all(bio);
        return NULL;
    }
    BIO_free_all(bio);

    return rsa;
}

version info:
# ./openssl version -a
OpenSSL 1.0.1u  22 Sep 2016
built on: Mon Jul 16 16:09:18 2018
platform: os/compiler
options:  bn(32,32) rc4(ptr,int) des(idx,cisc,2,long) idea(int) blowfish(idx)
compiler: arm-hisiv500-linux-gcc -I. -I.. -I../include  -DOPENSSL_THREADS
OPENSSLDIR: "/home/kgbook/tools/libopenssl/ssl"

OPENSSL_init_crypto is a symbol that was introduced in OpenSSL 1.1.0 - but you are using OpenSSL 1.0.1u which predates that. You would need to use a more up to date version of OpenSSL.

When you run cmake it will tell you what OpenSSL version it is locating automatically.
You can use -DOPENSSL_ROOT_DIR=/path/to/somewhere on the cmake command line to have it look elsewhere - but pay attention what it reports as this is what it will be using.
We have no idea how you have built your openssl or where you have "installed" things ...
As this is nothing to do with OpenSSL and everything to do with using cmake I'm closing the issue.

I set OPENSSL_ROOT_DIR, OPENSSL_CRYPTO_LIBRARY, and OPENSSL_INCLUDE_DIR in CMakeLists.txt, and find_package(OpenSSL REQUIRED)
when i run cmake command, It prints
-- Found OpenSSL: /home/kgbook/koala/sysroot/bin/libopenssl/lib (found version "1.1.0h")

And I compile with no error again, thanks for your advice.

Just hit this problem when building a program on a Solaris 11.4 system that has both OpenSSL 1.0.2 (in default library search path) and 1.1.1 (in alternative path, not present in default search path) installed due to bad specification of the library search path (using the -L linker option). Later on I wanted to link the same program with freshly built 3.0alpha and hit the same problem again, this time because of missing 'libcrypto.so -> libcrypto.so.3` symlink. Luckily the Solaris linker (ld(1)) offers debugging capabilities (described in the "Libraries and linkers guide") which provide some hints:
$ LD_OPTIONS=-Dfiles gcc -DOPENSSL_SUPPRESS_DEPRECATED=1 -m64 -I ./include-3 -o sign-mt-public sign-mt-public.c -Xlinker -R. -L. -lcrypto
debug:
debug: Solaris ELF Utilities: 11.4-1.3223
debug:
debug: file=/usr/lib/sparcv9/crt1.o  [ ET_REL ]
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/crtp.o  [ ET_REL ]
debug:
debug: file=/usr/lib/sparcv9/crti.o  [ ET_REL ]
debug:
debug: file=/usr/lib/sparcv9/values-Xa.o  [ ET_REL ]
debug:
debug: file=/usr/lib/sparcv9/values-xpg6.o  [ ET_REL ]
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/crtbegin.o  [ ET_REL ]
debug:
debug: file=/var/tmp//cc4o.G8c.o  [ ET_REL ]
debug:
debug: file=/lib/sparcv9/libcrypto.so  [ ET_DYN ]
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/libgcc.a  [ archive ]
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/../../../sparcv9/libgcc_s.so  [ ET_DYN ]
debug:
debug: file=/lib/sparcv9/libc.so  [ ET_DYN ]
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/libgcc.a;  reusing: originally processed as /usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/libgcc.a
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/libgcc.a  [ archive ]
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/../../../sparcv9/libgcc_s.so;  skipped: already processed
debug: file=/lib/sparcv9/libc.so;  skipped: already processed
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/crtend.o  [ ET_REL ]
debug:
debug: file=/usr/lib/sparcv9/crtn.o  [ ET_REL ]
debug:
Undefined                       first referenced
 symbol                             in file
OPENSSL_init_crypto                 /var/tmp//cc4o.G8c.o
ld: fatal: symbol referencing errors
collect2: error: ld returned 1 exit status

After creating the symlink the program was linked fine (using libcrypto from the current directory):
$ ln -s libcrypto.so.3 libcrypto.so
$ LD_OPTIONS=-Dfiles gcc -DOPENSSL_SUPPRESS_DEPRECATED=1 -m64 -I ./include-3 -o sign-mt-public sign-mt-public.c -Xlinker -R. -L. -lcrypto
debug:
debug: Solaris ELF Utilities: 11.4-1.3223
debug:
debug: file=/usr/lib/sparcv9/crt1.o  [ ET_REL ]
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/crtp.o  [ ET_REL ]
debug:
debug: file=/usr/lib/sparcv9/crti.o  [ ET_REL ]
debug:
debug: file=/usr/lib/sparcv9/values-Xa.o  [ ET_REL ]
debug:
debug: file=/usr/lib/sparcv9/values-xpg6.o  [ ET_REL ]
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/crtbegin.o  [ ET_REL ]
debug:
debug: file=/var/tmp//ccp5skWa.o  [ ET_REL ]
debug:
debug: file=./libcrypto.so  [ ET_DYN ]
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/libgcc.a  [ archive ]
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/../../../sparcv9/libgcc_s.so  [ ET_DYN ]
debug:
debug: file=/lib/sparcv9/libc.so  [ ET_DYN ]
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/libgcc.a;  reusing: originally processed as /usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/libgcc.a
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/libgcc.a  [ archive ]
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/../../../sparcv9/libgcc_s.so;  skipped: already processed
debug: file=/lib/sparcv9/libc.so;  skipped: already processed
debug:
debug: file=/usr/gcc/10/lib/gcc/sparcv9-sun-solaris2.11/10.2.0/crtend.o  [ ET_REL ]
debug:
debug: file=/usr/lib/sparcv9/crtn.o  [ ET_REL ]
debug:


quote fixes made arrays be processed like strings

There are two commits ( 5f61ff786719f45711a98bc1522a17b42fb33198 and 35a26068ef2d37bf5ffafe5c6fdd87bb1ed69e51 ) that did massive changes to quotes/variables that are affecting tasks that expect a non-string.
Example output:
TASK: [ceph-osd | check the partition status of the journal devices] **********
skipping: [ceph-vakulkar-run338-node3-osd]
skipping: [ceph-vakulkar-run338-node2-osd]

TASK: [ceph-osd | fix partitions gpt header or labels of the journal devices] ***
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'{', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'{', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'{', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'{', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u' ', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u' ', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'j', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'j', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'o', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'o', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'u', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'u', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'r', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'r', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'n', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'n', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'a', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'a', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'l', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'l', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'_', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'_', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'p', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'p', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'a', None])
skipping: [ceph-vakulkar-run338-node3-osd] => (item=[u'a', None])
skipping: [ceph-vakulkar-run338-node2-osd] => (item=[u'r', None])

Related Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1383468

I can't reproduce this issue, which ansible version is this?

1.9.6 maybe @vasukulkarni you can give more context? @leseb the BZ has more details though

This is on 1.9.6, but the ceph-ansible I used for this is now reverted back to 1.0.5, will have to use master if i have to recreate this.

@vasukulkarni  well we need to test with Ansible 2, starting from <IP_ADDRESS> to 2.2

Done.


Colab—# ffmpeg extract

Hey, not sure if this is where I should be reporting issues for the Colab version, but when I get to the '# ffmpeg extract' step, I'm getting an attribute error.  I've tried this with a few different video files, using different containers and different encoding, but I still get errors each time.  The file that produced this output was a GIF (320 × 178 @ 33.333 fps, 3.33 seconds) I converted to different formats.  I started off using H.264<EMAIL_ADDRESS>8bpc, YUV 4:2:0), and the version that produced the output below was GIF → MOV(PNG encoding) → remux: MKV.  Here is the console output from the error:
110
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-14-8da4460b8bf0> in <module>()
     18   frame_count += 1
     19   first_frame = f"{FRAME_INPUT_DIR}/00001.png"
---> 20   new_last_frame = f"{FRAME_INPUT_DIR}/{frame_count.zfill(5)}.png"
     21   shutil.copyfile(first_frame, new_last_frame)
     22

...and here is the code it ran pulled from the console:
# ffmpeg extract - Generating individual frame PNGs from the source file.
%shell rm -rf '{FRAME_INPUT_DIR}'
%shell mkdir -p '{FRAME_INPUT_DIR}'

if (END_FRAME==-1):
  %shell ffmpeg -i '/content/DAIN/{filename}' -vf 'select=gte(n\,{START_FRAME}),setpts=PTS-STARTPTS' '{FRAME_INPUT_DIR}/%05d.png'
else:
  %shell ffmpeg -i '/content/DAIN/{filename}' -vf 'select=between(n\,{START_FRAME}\,{END_FRAME}),setpts=PTS-STARTPTS' '{FRAME_INPUT_DIR}/%05d.png'

from IPython.display import clear_output
clear_output()

png_generated_count_command_result = %shell ls '{FRAME_INPUT_DIR}' | wc -l
frame_count = int(png_generated_count_command_result.output.strip())

import shutil
if SEAMLESS:
  frame_count += 1
  first_frame = f"{FRAME_INPUT_DIR}/00001.png"
  new_last_frame = f"{FRAME_INPUT_DIR}/{frame_count.zfill(5)}.png"
  shutil.copyfile(first_frame, new_last_frame)

print(f"{frame_count} frame PNGs generated.")

Hi! Yes, you're in the right place. Thank you for reporting this.
The info you've provided seems to be enough for me to investigate a bit further. I'll get back to you soon with what I find.

Hi there! Indeed, this is a problem when using the seamless option. That line of code that fails fails because of a wrong type conversion.
This is the full error (the last part is the one giving the actual error message):
``python
15
AttributeError                            Traceback (most recent call last)
 in ()
18   frame_count += 1
19   first_frame = f"{FRAME_INPUT_DIR}/00001.png"
---> 20   new_last_frame = f"{FRAME_INPUT_DIR}/{frame_count.zfill(5)}.png"
21   shutil.copyfile(first_frame, new_last_frame)
22
AttributeError: 'int' object has no attribute 'zfill'

I'll send a PR with a fix, but in the meantime, you can change this line:

```python
  new_last_frame = f"{FRAME_INPUT_DIR}/{frame_count.zfill(5)}.png"

into this:
  new_last_frame = f"{FRAME_INPUT_DIR}/{str(frame_count).zfill(5)}.png"

You should be able to continue from there!

Awesome, thank you very much
Sent from my iPhone
On Nov 7, 2020, at 11:31 PM, Alpha<EMAIL_ADDRESS>wrote:

Hi there! Indeed, this is a problem when using the seamless option. That line of code that fails fails because of a wrong type conversion.
This is the full error (the last part is the one giving the actual error message):
``python
15
AttributeError Traceback (most recent call last)
in ()
18 frame_count += 1
19 first_frame = f"{FRAME_INPUT_DIR}/00001.png"
---> 20 new_last_frame = f"{FRAME_INPUT_DIR}/{frame_count.zfill(5)}.png"
21 shutil.copyfile(first_frame, new_last_frame)
22
AttributeError: 'int' object has no attribute 'zfill'
I'll send a PR with a fix, but in the meantime, you can change this line:
  new_last_frame = f"{FRAME_INPUT_DIR}/{frame_count.zfill(5)}.png"

into this:

  new_last_frame = f"{FRAME_INPUT_DIR}/{str(frame_count).zfill(5)}.png"

You should be able to continue from there!

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbaowenbo%2FDAIN%2Fissues%2F115%23issuecomment-723529278&data=04%7C01%7C%7Cf0ce5a5977b041d555e908d8839f31c6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637404067035043682%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aiI%2BELSso65jOP%2BNMZeb8YlpodpxFwW3rW%2FqjUnvo88%3D&reserved=0>, or unsubscribe<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADAXSRSAOFDCRBQHXBLZNJLSOYNK5ANCNFSM4TOBNVNA&data=04%7C01%7C%7Cf0ce5a5977b041d555e908d8839f31c6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637404067035053676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DxTsF6cd1Rs4Gav0ymMtA30WEtORf3onYwA6jyDxfU%3D&reserved=0>.


Add ONTU to the project

Two files were created for one university: ua/edu/ontu.txt and ua/edu/ontu/cloud.txt
The Odesa National Academy of Food Technologies was reorganized and now renamed Odesa National University of Technology.

@oleksiisakaliuk First stage of verification passed, official domain is ontu.edu.ua as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

Thank you! We have also official domain @cloud.ontu.edu.ua because on @
ontu.edu.ua set limit on user count.
Ср, 1 марта 2023 г. в 13:24, Philip Torchinsky @.***>:

@oleksiisakaliuk https://github.com/oleksiisakaliuk First stage of
verification passed, official domain is ontu.edu.ua as far as I verified.
This is just an informational note. Pull request is still in the review. I
appreciate your patience while waiting for the final decision.
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/16645#issuecomment-1449935674,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI5YPLN6TBKUEV3SW5EMTBLWZ4WVRANCNFSM6AAAAAAVCBMPW4
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Sincerely, Oleksii Sakaliuk.
PhD student, IT specialist of #CenSciONAFT https://kci.onaft.edu.ua/
ORCID: 0000-0002-5051-518X https://orcid.org/0000-0002-5051-518X
Publons: S-3533-2016
https://publons.com/researcher/1606357/oleksii-sakaliuk/

You can contact your system administrator for confirmation. @.***
Ср, 1 марта 2023 г. в 13:38, Алексей Сакалюк @.***>:

Thank you! We have also official domain @cloud.ontu.edu.ua because on @
ontu.edu.ua set limit on user count.
Ср, 1 марта 2023 г. в 13:24, Philip Torchinsky @.***>:

@oleksiisakaliuk https://github.com/oleksiisakaliuk First stage of
verification passed, official domain is ontu.edu.ua as far as I
verified. This is just an informational note. Pull request is still in the
review. I appreciate your patience while waiting for the final decision.
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/16645#issuecomment-1449935674,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI5YPLN6TBKUEV3SW5EMTBLWZ4WVRANCNFSM6AAAAAAVCBMPW4
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Sincerely, Oleksii Sakaliuk.
PhD student, IT specialist of #CenSciONAFT https://kci.onaft.edu.ua/
ORCID: 0000-0002-5051-518X https://orcid.org/0000-0002-5051-518X
Publons: S-3533-2016
https://publons.com/researcher/1606357/oleksii-sakaliuk/

--
Sincerely, Oleksii Sakaliuk.
PhD student, IT specialist of #CenSciONAFT https://kci.onaft.edu.ua/
ORCID: 0000-0002-5051-518X https://orcid.org/0000-0002-5051-518X
Publons: S-3533-2016
https://publons.com/researcher/1606357/oleksii-sakaliuk/

@oleksiisakaliuk Thank you for your patience while waiting for a review and processing your request. Pull request merged.
When a domain ontu.edu.ua is added to this repository, all its subdomains including cloud.ontu.edu.ua are considered to be included to the trusted list by default.
Please wait for about an hour before starting to request your free licenses to allow the changes to propagate through our systems. Thank you!

Thank you!
Ср, 1 марта 2023 г. в 13:43, Philip Torchinsky @.***>:

@oleksiisakaliuk https://github.com/oleksiisakaliuk Thank you for your
patience while waiting for a review and processing your request. Pull
request merged.
When a domain ontu.edu.ua is added to this repository, all its subdomains
including cloud.ontu.edu.ua are considered to be included to the trusted
list by default.
Please wait for about an hour before starting to request your free
licenses to allow the changes to propagate through our systems. Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/16645#issuecomment-1449977415,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI5YPLJKJRO4VBBKIQNNSRLWZ4Y7LANCNFSM6AAAAAAVCBMPW4
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Sincerely, Oleksii Sakaliuk.
PhD student, IT specialist of #CenSciONAFT https://kci.onaft.edu.ua/
ORCID: 0000-0002-5051-518X https://orcid.org/0000-0002-5051-518X
Publons: S-3533-2016
https://publons.com/researcher/1606357/oleksii-sakaliuk/


Fix final :pre snapshot not being generated

The :pre snapshot is not generated properly (it remains “non-final”). This PR fixes that.
The NonFinalSnapshotWithPathError error might need to be removed. I’ll try to keep it in (it’s useful) but getting it to work properly might be hard.
Fixes #762.

Unfortunately, while using compiled_content, this still yields an error. Not sure if you wanted that fixed or not based on

(It might be the case that Nanoc 4.1.0a1’s behavior is in fact more correct.)

Ack—I guess that’s why it’s still in beta :).
Lesson learnt for me: when fixing a bug, try the original test case again to make sure the right bug is tackled.
I’ll reopen the original issue and look into it again.


Unavailable Fuel Range and Fuel Level

Fuel Range and Fuel Level are unavailable from this version. It worked without any problems on the previous one. (MG HS2)

Hi @pedroRSL
It might be caused by the check on the vehicle type. It you installed an early version, where this data was nit stored during configuration and was determined automatically based on the data from the API, those sensors may not setup.
Try to remove the integration and re-add it. It shall solve the issue.
Let me know if this worked.

I removed and added the integration again. This time I don't have these parameters even on the entity list. I have an ICE version of the car and the day before yesterday I saw how much fuel there is in percentage and what the range is. If I'm not mistaken, the fuel level had a battery icon but it showed the percentage of fuel in the tank.

Thanks for the feedback. Let me check what might have caused it and will let you know.
As I don't have an ICE to try, it gets tricky to know what gets affected, but for sure we can work out on a fix.
I will try to get in fixed today.
Cheers

Hi @pedroRSL
This shall be fixed on 0.4.5 (https://github.com/ad-ha/mg-saic-ha/releases/tag/0.4.5)
Try to update and restart HA, once you do so you shall see those sensors back. Including the appropriate icons for ICE :)
Let me know if it all works now.
Cheers

Everything is back to normal. Thanks for the quick fix. Great integration and great work 😁

Thanks for the feedback. And sorry for the inconvenience. Before I forgot the ICE on the conditions for sensors.
Glad it's working again.


Is there any way to get counter on endless pagination items?

I am using it to display a grid (div based) to display list of items with endless pagination. I tried to use forloop.counter however, every time it gets new set of items in queryset it starts the counter from 1 on the subsequent folds. Is there any way to get running counter?

This call inserts in the template context a pages variable
{% get_pages %}
{{forloop.counter0|add:pages.current_start_index}}


Shakedown testing of v13

What
Do some last-minute testing of v13 of the Prototype Kit before release.
Why
Make sure there are no major issues in the v13.0.0 release.
Who needs to work on this
Whole team
Done when

[ ] Users can do all the things that we expect them to be able to do without issues

[x] Create a prototype
[x] Make a juggling licence app
[ ] Publish on Heroku

[ ] Users doing things we don't expect them to do won't have massive issues
[ ] We are happy to release v13.0.0

Using a fresh Linux machine, I have succsessfully built a juggling license prototype using v13 and the new instructions.

I have now succsessfully deployed to heroku.

Some small issues:

When deleting the config.json file as I think users could possibly do by accident, the prototype does not report an error in the log but continues on with the service name changed to "GOV.UK Prototype Kit".  I agree with @joelanman that the users may not necessarily notice this.
When the config.json is malformed, the application displays the fact the config.json is malformed several times but carries on with the default name changed as above to "GOV.UK Prototype Kit".  I think can cause the same confusion as above especially if the user is not monitoring the logs when their app "appears" to be running ok.

A few suggestions for pages not found:

I notice that if a user has deleted their index.html page and deploy to Heroku, the default page telling the user how to create their home page is displayed.  Perhaps when deployed to Heroku, this should instead be "Page not found" like it is for any other page not defined.
Now that we have the manage-prototype pages available when the prototype is in development it would be better to replace the code in our default homepage with a link to the /manage-prototype/templates page with an example of an index page for them to create it from.
Perhaps while in development, we should replace the "Page not found" message in the browser with a formatted page specifiying the page is not found and if they expect it to exist they can go to the /manage-prototype/templates page to create one.


Use storage servers to store epubs[FEATURE REQUEST]

Is your feature request related to a problem? Please describe.

Due to many novel download/compile requests the storage of my device is running out.
Describe the solution you'd like

When the bot is done generating the epub file it will send the file to a storage/cloud server, for example GDrive. Then it will send a link to the user so that the user can download the file. To save storage allow the bot to overwrite the old file (if the server allow storing files for a long time).
Describe alternatives you've considered

GDrive has limited storage space I recommend you to use:

Mediafire
File.io
Dropapk.to
Gofile.io

Isn't Telegram itself a form of storage?

Isn't Telegram itself a form of storage?

Then can you add a feature that when the bot already sent the file it will delete the file from the server?

Sure, but it might take a while until you can use it. I'm in the process of rewriting NG, so I won't  add features to the current version. Until then you can just use cron jobs to delete the requests folder regularly.
Also if you really want to store the files on storage servers, I know that dropbox has a sync client which watches a directory to upload files from, should be easy to set up. This wont help with sending a download link on Telegram through.

okay, thank you!

Sure, but it might take a while until you can use it. I'm in the process of rewriting NG, so I won't add features to the current version. Until then you can just use cron jobs to delete the requests folder regularly.
Also if you really want to store the files on storage servers, I know that dropbox has a sync client which watches a directory to upload files from, should be easy to set up. This wont help with sending a download link on Telegram through.

can the crawling/grabbing speed be improve?

If you set the wait time to 0 (which you shouldn't do) the grabbing speed is basically only limited by the server on the other side and you internet connection.


is there a way to pass argument to dom event callback?

hello
i want to pass fixed arguments to dom event callback.
i hope it would like this
for option in self.product.options:
button(onclick=onDelClick("A3333", ev, node)):
"A3333" is fixed.
do you have any suggestion?

Use a closure?

@Araq Thank you for reply. is it possible to insert a nonamed proc in buildhtml?

@sclee15 you can do any of the following IIRC:
# option 1:
button(onclick=() => onDelClickAux1("A3333"))

# option 2:
button():
  proc onclick() = discard

# option 3:
proc onDelClickAux2(a: string): auto =
  result = proc (ev: Event; target: VNode) =
    discard
button(onclick=onDelClickAux2("A3333"))

I think this issue could be closed.


Support for material-ui v4.x

I updated to material-ui v4.3.3:
"@material-ui/core": "^4.3.3",
"@material-ui/icons": "^4.2.1",
"mui-datatables": "^2.9.0",
"react": "^16.9.0",
npm reports mui-datatables 2.9 to be dependent on material-ui v3.2
Also i get the following warning in the console when starting my site:

Check the render method of `WithStyles(Tooltip)`.
    in Tooltip (created by WithStyles(Tooltip))
    in WithStyles(Tooltip) (created by e)
    in e (created by t)
    in span (created by t)
    in div (created by t)
    in div (created by ForwardRef(Toolbar))
    in ForwardRef(Toolbar) (created by WithStyles(ForwardRef(Toolbar)))
    in WithStyles(ForwardRef(Toolbar)) (created by t)
    in t (created by WithStyles(t))
    in WithStyles(t) (created by t)
    in div (created by ForwardRef(Paper))
    in ForwardRef(Paper) (created by WithStyles(ForwardRef(Paper)))
    in WithStyles(ForwardRef(Paper)) (created by t)
    in t (created by WithStyles(t))
    in WithStyles(t) (at TvpDataTable.tsx:326)
    in ThemeProvider (at TvpDataTable.tsx:325)
    in TvpDataTable (at CardObject.tsx:231)```

<!--
    Thank you very much for contributing to MUI-datatables by creating an issue! ❤
-->

## Expected Behavior
<!---
    If you're describing a bug, tell us what should happen.
    If you're suggesting a change/improvement, tell us how it should work.
-->

## Current Behavior
<!---
    If describing a bug, tell us what happens instead of the expected behavior.
    If suggesting a change/improvement, explain the difference from current behavior.
-->

## Steps to Reproduce (for bugs)
<!---
    Provide a link to a live example (you can use codesandbox.io) and an unambiguous set of steps to reproduce this bug.
    Include code to reproduce, if relevant (which it most likely is).
-->

1.
2.
3.
4.

## Your Environment
<!--- Include as many relevant details about the environment with which you experienced the bug. -->

| Tech         | Version |
|--------------|---------|
| Material-UI  |       4.3.3  |
| MUI-datatables  |        2.9.0 |
| React        |        16.9 |
| browser      |       chrome 76.0.3809.132  |
| etc          |         |

Try the latest release, 2.10.0, it contains fixes for the console output issue (https://github.com/gregnb/mui-datatables/releases/tag/2.10.0). I think 2.10.0 still lists 3.2 as a dev dependeny, though it works fine for me (I'm currently using it with Material UI 4.3.0).

Just, tried it, warning dissapeared. Thx! Closing this issue.


Add api-key and api-key-env fields to config template

To make the config consistent among all non-local providers

thanks!


"picture of choice", yeah, how?

i love how easy they make it

It sure is pretty easy! Even a baby could figure it out!


Set capability to Seamless Upgrades

The operator handles upgrades seamlessly, as explained in
https://sdk.operatorframework.io/docs/overview/operator-capabilities/#level-2---seamless-upgrades
and documented in https://knative.dev/docs/install/operator/knative-with-operators/

Proposed Changes

Set capability to Seamless Upgrades

Release Note

The operator's capability level is set to `Seamless Upgrades`.

/cc @houshengbo @matzew @aliok

/lgtm
/approve


Support meaningful instance labels

When using meaningful instance labels there is only a name, and no port number, in the instance label.  Unfortunately, the existing node_exporter dashboard does not work without a port.
I suggest using the instance label directly.
Also, given that job and node are not multi-select, these can use = rather than =~ for matching (more efficient, less likely to trip up on regexp metacharacters)
I've made these changes in 12486 which is a direct fork of 1860.

Thanks for update the dashboard with the work done, it helps.


Cannot find module 'browserify-shim' when developing in child directory?

When running grunt browserify, I get the following warning:
Warning: Cannot find module 'browserify-shim' from '/path-to-project/project'.
I am wondering if this is because I am developing in a sub directory (e.g. project/develop) and, if not, do you have any suggestions of how to fix this issue.
The project in question is here.
Any help is appreciated.

I've run some tests and can confirm that this is an issue. You can see my tests here and can reproduce the issue 100% of the time.
If there is anything I can do to help resolve this, please let me know.

I don't have any issue running your test project... Are you sure you installed all the dependencies?

I believe so.
From the test repo, this is my output when running npm install from repo/other/develop.
><EMAIL_ADDRESS>install /Users/koop/Desktop/temp/grunt-browserify-test/other/develop/node_modules/grunt-browserify/node_modules/watchify/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild

  SOLINK_MODULE(target) Release/.node
  SOLINK_MODULE(target) Release/.node: Finished
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  SOLINK_MODULE(target) Release/fse.node: Finished
<EMAIL_ADDRESS>node_modules/grunt
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules/remapify
├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules/grunt-browserify
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules/browserify-shim
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules/browserify
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
It is the same output when running from the repo/standard directory.

Then after running grunt browserify (from repo/other/develop I get the following warning:
Running "browserify:dist" (browserify) task
>> Error: Unable to find a browserify-shim config section in the package.json for /Users/koop/Desktop/temp/grunt-browserify-test/other/js/test.js while parsing file: /Users/koop/Desktop/temp/grunt-browserify-test/other/js/test.js
Warning: Error running grunt-browserify. Use --force to continue.

Aborted due to warnings.

I get no errors from the repo/standard directory.

First of all, browserify-shim only uses the configuration from the package.json file. So you can remove the transformation in your gruntfile.
Doing this will resolve the issue Unable to find a browserify-shim config section in the package.json. Browserify cannot find the configuration because he's searching it from other/js directory, which of course doesn't have any package.json file. I don't know why he's doing that though.
This is not a grunt-browserify issue. You could easily reproduce it with browserify cli.
browserify ../js/test.js -t browserify-shim -o ../js/build/test.js
The only thing grunt-browserify could do is warn the user to remove browserify-shim from the transform array in the gruntfile.

@tleunen thanks for following up so quickly. I did a bit of research and just found this, I think it is what you mentioned. I will continue my discussion there.
Thanks for the help!

From the author @thlorenz on the thread you mentioned:

I had a look and believe the reason for this failing is that hmm.js is outside of the project (i.e. the app which contains the package.json).
The correct setup is to have all your files inside (or below) the dir that contains the package.json.

So yes, your js directory is outside of the develop directory (main app directory), and this is what causes the error.

@tleunen you mentioned:

First of all, browserify-shim only uses the configuration from the package.json file. So you can remove the transformation in your grunt file.

I am just curious why the transform is not required in the grunt file. Does running grunt browserify automatically run browserify-shim?

Because of this: substack/node-browserify#packagejson.
Browserify will read package.json. And browserify-shim is only compatible with a configuration in package.json. That's why you had to remove it from the gruntfile.

Thanks for the help @tleunen.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/458 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit f75292a:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in https://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


(Bug) Autocomplete

Fix

https://github.com/cvaize/detect-autofill

This package will no longer be updated. Please use https://github.com/anydigital/float-label-css instead.


Weird margin for custom components (RC0)

Short description of the problem:
If I create custom components, I get a weird margin in the top, see image:

What behavior are you expecting?
Not to have the margin. This did not happen in Beta 11
Steps to reproduce:

Create a custom component that wraps ion-card

Which Ionic Version?  2 RC0
Run ionic info from terminal/cmd prompt:
Cordova CLI: 6.3.1
Gulp version:  CLI version 3.9.1
Gulp local:
Ionic Framework Version: 2.0.0-rc.0
Ionic CLI Version: 2.1.0
Ionic App Lib Version: 2.1.0-beta.1
OS: Node Version: v4.6.0

Hello, thanks for opening an issue with us! Can you provide a repo that we can use to reproduce this issue?

Here the requested repo: https://github.com/dgroh/RepoDemoForIssues

Hi @jgw96 any feedback regarding this issue?


Initialize the Project Repository

Hi All,
I have initialized our repository with the following new features, please let me know if you have any questions.

[x] Wechaty Framework

[x] Wechaty Handlers
[x] Connect with Amazon S3 Storage for supporting Stateless

[x] Web Service for show QR Code
[x] SIGTERM Handlers for ChatOps
[x] Unit Tests & Integration Tests
[x] Continuous Test & Continuous Deploy (CI/CD)

[x] Travis CI
[x] HeroKu

[x] Code Style Linting
[x] Greenkeeper.io
[x] Building Status / Wechaty / Greenkeeper Badges
[x] VSCode configuration file

Thank you very much!

The list above has been done and has been explained in the weekly meeting.


Adding File Preview for more filetypes

What's the Problem?
On the Side File Preview, there are many more file types than average like raw format supported but some important file types are still missing for better workflow in the design field.
Missing Filetypes are for example:
EXR, EPS, PSD, AI, INDD, FBX, OBJ, USD, BLEND, IES and MTL

Solution/Idea
Maybe a 3D Viewer or EXR Previewer will be awesome. It will be also fantastic to have previews for these file types in the file list. I mean some raw formats are working in the Preview but not on the Filelist. For software-related formats like PSD can be an optional library download useful, so it will be not a problem with the Open Source License.
Alternatives
Adding in the file list the Previews.
Priorities

Capability
Priority

EXR and EPS Formats
Should

3D Formats like OBJ and FBX and software-related formats
Could

Files Version
Version: <IP_ADDRESS> OS Version: 10.0.19044.1889
Windows Version
Windows 10 Pro 21H2
Comments
No response

Merging with #4041 and #2582. There are a couple other issues as well, so rest assured it's being tracked.


(TWILL-141) Fix namespacing of ZKClient

Not to fail with exception when creating “/“ through the
namespaced ZKClient
Return the correct path in OperationFuture.getRequestPath() for
futures returned from namespaced ZKClient

+1
LGTM

Will merge this sometime today if no more comment.

Merging ...


Use stable version on Nyholm/psr7

some builds fail. is that because of this change, or failing on master too? and if it fails on master, what should we do about it? expecting builds to fail is problematic...

Fixed in master


Sequential number is not working for multiple cameras

The sequential numbering seems to be reused for all of the camera, so the screenshots per camera (with for example 2 cameras) skip one number.
Reported at https://mods.factorio.com/mod/TLBE/discussion/62465f1507d6ea4f7ab711e4

Should be fixed in next release

Released in v1.4.4


Providers mocked via MockModule are persisted across tests

Hello,
Providers that are part of a Module, when mocked via MockModule, appear to use the same instance across all tests.
For example:
beforeEach(() => {
    TestBed.configureTestingModule({
        imports: [MockModule(ExampleModule)],
    });

    exampleProvider = TestBed.inject(ExampleProvider);
});

it('should not be able to pass state between tests (setup phase)', () => {
    // Set a property on the class to see if it carries over to the next test.
    exampleProvider.a = 11;
});

it('should not be able to pass state between tests (validation phase)', () => {
    expect(exampleProvider.a).toBeUndefined(); // Fails
});

Full Example
I would think the expected behavior is that each test would get a new mocked instance of the provider so that one test could not accidentally impact another test (in this way).
Thank you for your time.
P.S. This also applies to when MockProvider is used directly, though I understand that to be an internal API.

As a note, this cross-test instance sharing not appear to happen when the the module and provider caches are disabled via ngMocksUniverse.flags, e.g.:
beforeAll(() => {
    ngMocksUniverse.flags.delete('cacheModule');
    ngMocksUniverse.flags.delete('cacheProvider');
});

Hi,
thanks for the report. You need to use beforeEach(() => MockBuilder(ExampleModule)) instead.

Hi,
Thank you for the quick reply!
Using MockBuilder appears to work, but calling ngMocks.flushTestBed() does not (here's the change I tried).
Is using MockBuilder the recommended approach to mocking?

Hi again,
yes, MockBuilder is the recommended approach.
I'll check the code example next days / weeks the issue for improving ng-mocks lib.

Hi, I've tested it further and it doesn't work without mocking either:
  beforeEach(() => {
    TestBed.configureTestingModule({
      imports: [ExampleModule], // without mocking it still fails.
    });

    exampleProvider = TestBed.inject(ExampleProvider);
  });

I would suggest to close this one, feel free to reopen it or to post a new one.

Hi, thank you for looking into this.

Hi, I've tested it further and it doesn't work without mocking either:

Removing the mocking appears to work correctly for me. Here's what I tried: https://github.com/JoshuaEN/ng-mocks-mock-module-provider-mocking-issue/commit/38e4c022d32892d0c19bcdae6005a95e11f1d08a#diff-807a50de61c19b7d9a595c1e9cec0c05
As a note, the tests were originally falling for me after removing the mocking, but for an unrelated reason: Without mocking, the constructors of the real objects were running and thus the value a was set to 5 by the constructor (where, when mocked, the constructor would not run and thus a would be undefined on initialization).
I also added an object equality check, which is maybe more reliable for demonstrating the issue. With mocking, the same instance of the service object is present in both tests. Without mocking, each has a different instance.

aha, now I was able to reproduce the issue and checking for a possible solution.
Thanks!

Hi again, I think I've found the issue and fixed it. Might you verify that it works well for you?
ng-mocks.zip

Hi again, I think I've found the issue and fixed it. Might you verify that it works well for you?
ng-mocks.zip

Hi, thanks for the quick reply! It works as expected with this fix.

A new version has been released. Thanks for the report.

Thank you!


Fix path of imported modules in ArticleList.vue

Issue summary
In src/components/ArticleList.vue some local modules are imported with the @ symbol which is a webpack alias. For people which are not familar with webpack this might be confusing. Change this to a relative pattern.
Resources

webpack - Resolve

Acceptance Criteria

Every @ in the import statements is replaced with a relative path.

Sent a PR to address this.


Do not overflow a long item

Take the first line's width of a single item into account when
trying to overflow something.
Closes #2676.

Thanks!


Content items of special templates lack relationship

Content items of acquisition and protocol templates don't have a Relationship field. We consider these items to be similar to CONTAINER items at the root of a SR document content tree and instantiate ContentSequence objects with is_root to allow content items without the RelationshipType attribute.

Looks good to me!


declare array type with computed size

The following program sample.go triggers an unexpected result
package main

type Level int

const (
    a Level = -1
    b Level = 5
    d       = b - a + 1
)

type counters [d]int

func main() {
    println(len(counters{}))
}

Expected result
$ go run ./sample.go
7

Got
$ yaegi ./sample.go
run: ./sample.go:17:6: constant definition loop

Yaegi Version
v0.9.19
Additional Notes
Related to #1172 (after applying #1174).

The test works if using untyped constants a and b.


Create a separate section in the Admin Settings UI for flags that are for "under development" features

We would like a way to differentiate between feature flags that are for production use and those that are guarding features that are under development. This will allow CEs to understand what are the flags they can enable in production and will also guard against CEs accidentally enabling features that aren't yet production ready.
This change will likely involve adding a new field to the variables in env-var-docs.json to indicate that a flag is production ready. That field can then be used in the Admin Settings Panel to separate production flags from under development flags.

@gwendolyngoetz this is done right?

Yeah. I took the simpler approach and just moved the under development features into a new section called "Experimental" which shows up at the bottom of the screen.

Fixed by https://github.com/civiform/civiform/pull/8689


0.8.13 error

error.txt
after copying 319982.txt and smt_319982 from shinra meter as it was missing from the TCC opcode folder

Seems like S_FRIEND_LIST opcode is wrong in that file

found the right opcode for S_FRIEND_LIST. TCC is now working.
thanks.


Provisioning machines hangs for air-gapped Rancher behind a proxy with a custom cert

Rancher Server Setup

Rancher version: 2.5.8 & master-head
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): k3s

Proxy/Cert Details: The Rancher server is air-gapped behind a proxy with a custom cert (given to Rancher via secret and setting additionalTrustedCAs=true)

Describe the bug
Rancher cannot provision new machines for RKE1 clusters.
To Reproduce

Try to provision a new downstream cluster
The machines will be created in the cloud provider
Provisioning in Rancher will hang waiting for nodes to register

Result
Provisioning will not progress after the VMs are created.
Expected Result
Provisioning of the machines should complete successfully.
Additional context
The issue is that rancher-machine is not able to SSH to the machine after it is created. It will try to do so to get information about the machine and install Docker. However, rancher-machine will fail to connect.
This was reproduced manually by using rancher-machine and ssh in the jail. The only way I was able to connect to the machine was via ssh outside of the jail using the proxy VM as a jump host.
The Rancher sever and proxy were created in EC2 nodes. The problem persists even when attempting to provision nodes in the same VPC and security group as the Rancher server. I was unable to use the same subnet because of permissions difference with the QA account (used to create the proxy setup) and my account.

There have been heaps of improvements in the provisioning framework since this was created, so I am going to move it to the backlog and if we get a chance to review we can see if this is still needed.


Refactor Binder code to allow separation of structure from data

depended by #23

close as the parent issue closed


Ignore GREASE in elliptic curve points

This PR adds GREASE support in supported_grups extension.
There is also small fix for potential openssl memory leak.
Fixes #14

@bartebor , thanx,
With #12 , I think fixed some of these GREASE errors.
Please re-open PR if something is wrong.


[Suggestion] Add toggle to allow limiting north pointing only in Overworld

I really like the idea of the mod, but could a toggle setting be added to let users switch between the mod affecting "Only Overworld" or "All dimensions"? ;)

Implemented in v1.20.1-1.1.0.
You can setup overworld only by using the following configuration:
{
  "dimensionTypeFallback": false,
  "dimensionTypes": {
    "minecraft:overworld": true,
    "minecraft:overworld_caves": true,
    "minecraft:the_nether": null,
    "minecraft:the_end": null
  }
}