GA update no Telemetry. Docu to be updated

Hello team,
WindowsAzureTelemetryService.exe - WindowsAzureTelemetryService service - used for guest agent telemetry - Note that starting with version 2.7.41491.971, the Telemetry component is included into the RDAgent service - so you might not see this service in recent versions.
Please update documentation accordingly or add this information, as it is confusing for customers.
Regards,
Carmina
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dd23dcce-4726-0745-2349-9cf3a17edb3e
Version Independent ID: fffbc417-129a-9c4d-de83-046b328a471d
Content: Install the Azure VM Agent in offline mode
Content Source: articles/virtual-machines/troubleshooting/install-vm-agent-offline.md
Service: virtual-machines-windows
GitHub Login: @genlin
Microsoft Alias: genli

@cadumi
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@genlin
Can you please check and add your comments on this doc update request as applicable.

@cadumi Thanks for the feedback, I will update the article based on your information.

The article was update.
#please-close


S3Sensor should not parse AWS credentials files

The standard way to read AWS credentials and the way boto implements it is to check first for environment variables and then fall back to ~/.aws/credentials if the env variables don't exist. Airflow shouldn't be parsing that file on its own. Parsing credentials should be delegated to boto. The way it's implemented now, it's effectively impossible to connect to S3 without reading credentials from a credentials file.
Our use case is to dockerize airflow, using environment variables in our docker container to read in AWS credentials.

@adambom,
We needed and still need to support different config file formats than the ones supported by boto, hence our roundabout way of doing this, though I should probably reuse the facilities provided by boto when parsing the file formats it understands.
It is also possible to store the credentials in the extras of the airflow connection. See https://github.com/airbnb/airflow/blob/master/airflow/hooks/S3_hook.py#L82-84.
I will work on a way to fall back on environment variables, but because of our need to use several sets of credentials environment variables could not override values provided in the Airflow connections.

Thanks @artwr. Sounds like a decent solution. In the meantime we'll look into using the extra_params.

+1 - the airflow instance is uses an IAM Role. Boto would use the Role on its own if the s3_hook wasn't requiring a credentials file.

@adambom and @robbwagoner, this issue should be resolved in the latest version of airflow. Specifying a s3 connection with empty extra will default back to boto's facilities for this. Sorry it took so long.
Feel free to reopen if you still have issues, but I have successfully tested this internally.


Somes actions don't work with Record: "MIDI overdub", "MIDI replace", "MIDI touch-replace" and "MIDI latch-replace"

Theses actions are:
SWS/BR: Options - Toggle "move dit cursor to end of recorded items on record stop"
SWS: toggle move cursor to end of recorded media  on  stop
Tested with Reaper@stock

These SWS, SWS/BR actions do the same as the native action "Options: Move edit cursor to end of recording, when recording ends" (I don't know why they exist, maybe the native action wasn't available at that time).
Since the native action also doesn't work in the cases you mentioned* I suggest you do a report in the Reaper bug forum for it.
*When using "MIDI overdub", "MIDI replace", "MIDI touch-replace", "MIDI latch-replace" into existing items I wouldn't expect this option to work (from the wording of it, as no new media is created), but it should at least work when these recording modes are creating new items imo.


[RCINT-3420] fix bug when oAuth login would fail with multiple tabs o…

…pen and window.opener blocked

Coverage remained the same at 34.338% when pulling 261e3e12da7a90037661ba30b2740d1fffc11d0f on u9520107:rcint-3420 into b6848df376e2e51a663b062471a77826ef5e3aaa on ringcentral:master.


50 deltas without an image in between

We aim to have at most 3, but in practice we see 50-80 on some projects. This is a feedback loop, difficult reconstruction makes image generation more difficult, higher chance it's even more delayed next time. Not sure what the solution is.
Originally posted by @bojanserafimov in https://github.com/neondatabase/neon/pull/2998#discussion_r1067549984

Correction: excluding L0 layers, there are actually around 45-50 layers since the last image (not 50-80). Still a lot.

@knizhnik is this still relevant with your recent change ?

@knizhnik is this still relevant with your recent change ?

gc_feedback PR is not merged yet.
There are many different reasons which may cause such behavior:

Holes: sparse delta layers which case generation of  large number of image layers
Holes between image layers
"Stairs" - large number of partly overlapped delta layers which prevents generation of image layer because for the particuar key range umber of deltas is less than threshold (3)
Compaction and page reconstruction in the same task
1-2 are already merged, 3 is in progress, 4 - not addressed


Tagged template literals: minify does not shake pure tag function

Describe the bug
Unused tagged template literals are not tree shaken away from the minified output when the tag function is marked as pure using the /*#__PURE__*/ directive and/or by jsc.minify.compress.pure_funcs configuration.
I'm not sure if this would be considered a bug or a feature request.
Input code
/*#__PURE__*/
function pure_html(strings, ...values) {
  return { strings, values };
}

// ✅ This is tree-shaken from the minified output.
const a = `<span>aaaa</span>`;

// ❌ This is not tree-shaken from the minified output,
// despite the "pure_html" function being declared pure
// using the __PURE__ directive and by
// `jsc.minify.compress.pure_funcs` configuration.
const b = pure_html`<span>bbbb</span>`;

// ✅ This is not tree-shaken from the minified output.
export const c  = pure_html`<span>cccc</span>`;

Config
{
  "jsc": {
    "parser": {
      "syntax": "ecmascript",
      "jsx": false
    },
    "target": "es2022",
    "loose": false,
    "minify": {
      "compress": {
        "pure_funcs": ["pure_html"]
      },
      "mangle": false
    }
  },
  "module": {
    "type": "es6"
  },
  "minify": true,
  "isModule": true
}

Playground link (or link to the minimal reproduction)
https://play.swc.rs/?version=1.3.94-nightly-20231016.1&code=H4sIAAAAAAAAA42QQU7DMBBF9z7FV9lAVZwDtLBjjxCsE8eZNIbGjjx2RVV1yY4jwOU4CXZKI4RYdOSFNTN%2Fvt4v5hdlef%2F0cFeW80K00epgnMUQPZVd6DeXHLyxa15ASrlVm0h8hb0APIXoLfaYFo5THJbiIERR4OvjDY%2BdYaQXPNE1d%2BqFLFrveoSO0BtrWkMNXAxDDFJoZzlA4QbVigdlb1WqVTF%2Bq%2BXx6Of7dNS6cNbhRRY2xIMJNM5nmWyGibamRJA29Eb5pMrwWRI5t7PgFBEa4ylptgRlG9Q75L3qmbUcPXdSu37wxCzHBLMDV0hcrVlHr7LbCbNOmFPMP7x1qj%2B8v0I8l1cKeh2cDzgaafzjpFNNTt%2F37f80BQIAAA%3D%3D&config=H4sIAAAAAAAAA1WPTQ7CIBBG9z1FM2sXpgsX3sETGGMITisNf2EgkTS9u0Ch1h3zvvnCm6Xre5iJw7Vf0jMNljlCt8%2BJUNSefRIB5IoRd8J6OLV0phyNTBIWtG4JeOYm9KVFw3kYagOkMYStUZkSWozx%2BCc3yjokOrDsFhw%2Bx6B55nd4eyXhUeN1N1JMTxL%2Fpbq6AMq8QgnruT5a3CQv8FtqPt6F4giCbq2YWbd%2BAdH3Ab05AQAA
SWC Info output
No response
Expected behavior
When a template tag function is marked "pure", minification should take it into consideration when considering whether an expression has side-effects.
Actual behavior
No response
Version
1.3.94-nightly-20231016.1
Additional context
No response

__PURE__ directive here is used in a wrong way, so it should have no effect.

Also, you can't use target: "es5" with pure_funcs for template literals. You should perform minify() with pure_funcs and then transform().
I'll close this issue with fix for pure_funcs for template literals.

Thanks @kdy1! I've updated the description and playground link to target es2022. In my real use-case I was not targeting es5, I think that's just what the SWC Playground defaults to and I didn't notice it.
With regards to the /*#__PURE__*/ directive, are you saying it needs to be included every time the template literal tag function is used rather than once when the tag function is declared?

Yeap. I think what you intended is https://github.com/javascript-compiler-hints/compiler-notations-spec/blob/adeb6d0663692625f09257ed25a44e9051de9d85/no-side-effects-notation-spec.md

@kdy1 there may be a separate but similar issue where /*#__NO_SIDE_EFFECTS__*/ has no effect in relation to tagged template literals.
https://play.swc.rs/?version=1.3.94-nightly-20231016.1&code=H4sIAAAAAAAAA41QPU7DMBTefYpPZYGqJAdoYYFUYoGh3V0neSEWiR3ZLwWp6sjGEeBynAS7gYgihj55sPS%2B35dOz6S8f5Cru9tMZstldrNeSTlNRdWbgrU1qLltzj07bR79DEmSbFXTk7%2FATgCOuHcGO4yAYYv9XOyFSFN8vr9iXWuP8NgRXfpaPZFB5WwLrgmtNrrSVML23PWciMIaz1C4wmbhO2WuVZhFevhu5oPox9soaiyfJDyLxJJ8p5kO%2B0lsNsFYNKfQICCKRrnAetZcR0qE%2FnMilNpRIG7pJ3EeEkfJ79R5mD%2Bpf53i1NSJoJfOOsbgUeDYpAgzmnwB5kd9bcwBAAA%3D&config=H4sIAAAAAAAAA1WPPQ7DIAxG95wCee5QMXTIHXoIRJ2IiD9hIhVF3L1AIG03%2B33%2B9ORjYgw2kjCzo4xl8SIQhmsvhJKN4l0IoDSCZFA%2Bwm2kG9VoEZqwoXwmEEVYMbYW8TvnvQHaOcLR6Mwoq5b065TO%2BIBEleXLZYRdNf7rpq4E4157C%2FsjMXk89Q%2F4Hg1TDHuzg6LnKFY25Q%2F48FuFEwEAAA%3D%3D


[NEW]: Woman to pay back Crypto.com $10.5 million

Date
2022-08-30
Description
A judge has ruled that a Melbourne woman must pay back $10.5 million to crypto trading platform Crypto.com after they had mistakenly transferred her the amount in May of 2021, but took 7 months to realise.
Links
https://tickernews.co/crypto-com-accidentally-transfers-10-5m-to-woman-instead-of-100/
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
No response
Personal link
No response

Already included at https://web3isgoinggreat.com/?id=cryptocom-wants-back-the-7-2-million-they-accidentally-sent-a-customer-last-year


Accessing and setting document metadata directly vs through _meta

If you define a "score" field on a DocType, the _meta.score attribute is set to the document value rather than the _score attribute of the ES hit. I think this is due to ObjectBase.__init__ calling setattr, and the __setattr__ of DocType making a special case for META_FIELDS (which include "score") to set attributes on _meta. I'd imagine this is the case for any document field with the same name as a meta field.
It seems like DocType shouldn't try to expose/set _meta attributes directly. Or at least document which field names are not allowed on a DocType and raise an error if you try to define one that conflicts with _meta.

Thanks for the report, I agree that this behavior is not desirable in most cases. For the time being I changed it that only metadata relevant to the document ('id', 'parent', 'routing', 'timestamp', 'ttl', 'version', 'version_type') can be set that way. It still limits the namespace but I feel like this is a good compromise since people might want to set these directly.
What do you think?

It still seems like unexpected behavior to have document fields overwrite _meta fields. If these names are going to be used get/set _meta fields, I still think it's a good idea to disallow defining them on a DocType.

I see your point, I am just not sure for the document metadata - like parent, id etc. To me they seem like they should be accessible (and settable) on the document itself. I will think about it more.
Of course if anybody has an opinion I welcome the feedback, feel free to comment here.

Right now, this will throw a NumberFormatException exception, since ES version is expected to be an integer:
class Release (DocType):
    package = String(analyzer='snowball', fields={'raw': String(index='not_analyzed')})
    version = String(index='not_analyzed')

    class Meta:
        index = 'software'

r = Release(package='elasticsearch', version='1.4.3')

I think there are probably other errors that may arise from conflating document fields with ES metadata.

Very good point. If we flip it and check for defined fields would it make more sense?
I am starting to lean towards your solution, just want to think it over. Thanks for the feedback and the patience!

I'm not sure I understand what you mean. Do you mean if you define a version field, doc.version will use that, otherwise it gets/sets _meta.version? That would work, but feels a bit magical to me.
Thanks for considering, and for your work on this library.

Thanks for you patience again, it was very helpful. I removed the access to all the metadata fields except id which I feel is needed.

I'm not getting an error TypeError: DocTypeMeta object got multiple values for keyword argument 'id' because our DocType subclass contains an id field.
IMHO, I think the document fields and ES meta information should remain separate.

So I only left the id accessible as a property. I can definitely fix the code so that your error doesn't appear, but the question is what is the expected/wanted behavior.
I can see arguments both ways. Why I want id to be accessible without _meta namespace:

accessing _meta shouldn't be needed to just save a document
some systems (django templates) doesn't allow access to protected attributes
id is, to me, a natural part of the document

Why it should be just inside:

feels magical (arbitrary, not straightforward)
easier implementation (and reasoning about what goes where)
can conflict with field id people might have on their DocType

If I understand the code correctly, this will pull the _id field from the result and set it as an attribute on the DocType class with the name id as part of the results list. My feeling would that es-dsl should only set attributes based on the defined fields. I might be surprised to see the id there if I didn't define it.

accessing _meta shouldn't be needed to just save a document

I'm not sure exactly what this means? In code I've written I set _id explicitly when indexing?

some systems (django templates) doesn't allow access to protected attributes

I'm less concerned about this. I agree, it is an annoyance, but there are ways to work around it, like template tags or putting the data into the template context in a view, if needed.
IIRC, elasticutils worked around this by calling it es_meta. It would make sense to me that _id was set on _meta (or es_meta) as _meta.id.

id is, to me, a natural part of the document

My feeling is that es-dsl shouldn't make any assumptions or enforce restrictions on my data.
I'm curious what others opinions are.

I like the idea of renaming it to es_meta. There is a name conflict chance of course, but should be minimal (especially when compared to id :) ).
Then there are two other questions:
Currently you can say: Comment(title='hello', _parent='blog-post-1').save() and we will extract _parent and use it as a parent value, same would go for version etc. Do we want to keep that? (imho yes since otherwise creating a child document in the dsl would be at least a two step process: c = Comment(title='hello'); c.es_meta.parent = 'blog-post-1'; c.save().
Or would something like Comment(title='hello', es_meta={'parent': 'blog-post-1'}) be ok? (that one we would definitely have to be used in from_es)
@robhudson what I meant by "you shouldn't need to access _meta was that without it it would be impossible to create a document by hand and save it into elasticsearch with a manually assigned ID, imo not acceptable (and still a hassle if we rename it to es_meta)
Thanks for the discussion guys, I really appreciate the feedback and help in designing this.

FWIW I don't think we can easily compare Django's model classes with this one, which I think we all have in mind when we talk about id fields. But to me the native behavior of ES is to set an id field and there is a option to override it with custom content. The DSL should reflect that, just like other "special" fields such as _parent or _version.
I think the conceptual disconnect happens when trying to overcome the differences between the list of fields as class attributes and the initialization parameters when creating result objects: The class attributes don't distinguish between native fields and custom fields while the initialization parameter do. So I would guess a solution would be to decide for one level of abstraction:
from esdsl import document, field

class MyDocumentType(document.DocType):
    id = field.Long()
    content = field.String()

result = MyDocumentType(id='123', content'acme')

print(result.id)

or:
from esdsl import document, field

class MyDocumentType(document.DocType):
    content = field.String()

    class Meta:
        id = field.Long()

result = MyDocumentType(content'acme', meta={'id': _id})

print(result.meta.id)
print(result._id) # works also for _version etc

So another iteration is available for review in es-meta branch. Short summary:

all meta fields (on both Result and DocType) are accessible on .meta property (hit.meta.score, Post(meta={'id': 42}),  doc.meta.id = 42, doc.meta.parent, ...)
you can also access (read and write) them on DocType using their underscored form (Post(_id=42), doc._id = 42, ...)

I like the solution you came up with. It does mean that you cannot have a field on your documents named meta, but that seems like a lesser limitation than not being able to have id. Perhaps that should be mentioned in the documentation somewhere?

Yes, we need to document it. Though you can still have a field called meta and access it via doc['meta']
Thanks all for the discussion and design opinions, it made a lot of difference.

Does any of this impact _meta usage? https://www.elastic.co/guide/en/elasticsearch/reference/2.0/mapping-meta-field.html

No, that works fine, though it is very meta you can still define it:
from elasticsearch_dsl import DocType, MetaField
class MyDoc(DocType):
    class Meta:
        meta = MetaField(cls='some class')


Test failed on arm64

Hello,
I try to improve the performance on arm64 and one test failed on arm 64.
user@arm1:~/go/src/gorgonia.org/gorgonia$ go test
roots: [Σ[0](%2)]
        execute Op
                child 0: a :: Vector float64 (10)
                child 1: 1(0, 1) - (10)() :: Vector float64 (10)
        execute Op
                child 0: + false(%0, %1) :: Vector float64 (10)
        dvBindVar
--- FAIL: TestBarzilaiBorweinSolver (0.04s)
    solvers_test.go:388:
                Error Trace:    solvers_test.go:388
                Error:          Max difference between 0 and 0.008076277940702002 allowed is 2e-05, but difference was -0.008076277940702002
                Test:           TestBarzilaiBorweinSolver
signal: killed
FAIL    gorgonia.org/gorgonia   4.788s

user@arm1:~/go/src/gorgonia.org/gorgonia$ go
go version go1.13.5 linux/arm64
user@arm1:~/go/src/gorgonia.org/gorgonia$ cpuinfo
cat /proc/cpuinfo
processor       : 0
BogoMIPS        : 166.66
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x0
CPU part        : 0xd08
CPU revision    : 3

This looks like a precision issue. The tests use float64 ...  which I suspect wouldn't be an issue. Looking into it

@blackrez can you run other solver tests?  As well as TestBasicArith

I don't see TestBasicArith but all other solver tests work

this was fixed a few months ago


DRILL-4735: ConvertCountToDirectScan rule enhancements

ConvertCountToDirectScan rule will be applicable for 2 or more COUNT aggregates.
To achieve this DynamicPojoRecordReader was added which accepts any number of columns,
on the contrary with PojoRecordReader which depends on class fields.
AbstractPojoRecordReader class was added to factor out common logic for these two readers.

ConvertCountToDirectScan will distinguish between missing, directory and implicit columns.
For missing columns count will be set 0, for implicit to the total records count
since implicit columns are based on files and there is no data without a file.
If directory column will be encountered, rule won't be applied.

MetadataDirectGroupScan class was introduced to indicate which files statistics for used.

Details in Jira DRILL-4735.

@jinfengni addressed code review comments. Please review when possible.

+1
LGTM. Thanks for the PR!


Add a Licence

Could you add a licence to the extension, so it's clear we can us it? Perhaps the GNU Affero General Public License that CKAN itself uses.

Done - added MIT licence. Thanks for raising.


Configurable USER AGENT and permanent auth support

Has this code ever worked? I am asking because I am looking at it and I noticed that you assume that what runCurl() returns is an array while in reality it return objects. It puzzles me somewhat.


how to split YOLO datasets to train/val. Not train/val/test

I tried code:
 ds.splitter.GroupShuffleSplit(train_pct=0.7,val_pct=0.2,test_pct=0.0)

get

ValueError: train_size=0.0 should be either positive and smaller than the number of samples 376 or a float in the (0, 1) range

Why the param test_pct cannot  be zero???

Hello @pizixie sorry for the confusion.
If you want to split into only 2 groups (train and test), then set val_pct to 0. It is not supported to set test_pct = 0. I will update the function with better documentation and error handling.


Add .NET Web API Backend Service

Add .NET8 Web API backend services for Payment
The service should:

Emulate payment processing;
Make HTTP call to existing Java or Python Service
Interact with AWS Services e.g DynamoDb to store data.
The Existing UI should be updated to send request to this new .NET Web API backend

Close it because the changes are already merged.


go.mod compatibility

hi, I face this issue when my project is using go.mod, since I'm using v3+

require github.com/robfig/cron: version "v3.0.1" invalid: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v3

I think it's related how go mod requirement on how it should named if the version is above v1
https://golang.org/cmd/go/#hdr-Module_compatibility_and_semantic_versioning
would you consider to update the version? thanks.

@febytanzil It happened to me as well, because I skipped the README about v3 :)
Important parts:
Make sure you import the library like this:
import (cron "github.com/robfig/cron/v3")
and that you have github.com/robfig/cron/v3 in go.mod, NOT github.com/robfig/cron

Exactly^
Thanks


le.sh throws an error when using coma separated list of domains

cp: can't stat '/etc/letsencrypt/live/example.com,www.example.com/privkey.pem': No such file or directory

I have added extraction of first part from coma separated list, hopefully should be enough. Let me know if it solved the issue.

Yes, it did. Thanx.


Show only confirmed profiles in the web admin interface

Right now we see all registered person in our admin interface.
In order to get a better overview it would be better just to see the confirmed profiles so the spam sign up vanish.

https://github.com/rubymonsters/speakerinnen_liste/pull/503


Guidelines 90: For metanalysis papers, the identifiers of all reanalyzed datasets are mentioned in the manuscript

There is a typo in the guideline title "metanalysis" should be "meta-analysis"

OK, I see now that it is also "metanalysis" that is used in the text of the scope. Is this the correct spelling?

No, you are correct, it should be "meta-analysis"


Pages are blinking in browser. Leaves artifacts

Overview of the issue
In frontend. Whenever I refresh a page in browser. It blinks very fast. But I can see messages like "error 403", "you are not logged in", then it shows Login form, and after that it already shows the actual page. And what is most problematic - it leaves artifacts after that. For example, this browser username popup box from login form - https://imgur.com/gdZ22hC
And blinking in general is quite bad UX. all text on the  page is shown first as translation tags. and only after that it translates them. It also can be notices when you refresh page, or open page in browser first time.
Its happening not in all pages. And its blinking differently. For example on Home page I don't get "403"-message, "not authorized" and login form, but I can see first home page variant when I'm not logged, and then I'm getting real home page (logged in).
For some reason after several site navigation events, Its not happening on my custom page. But its still a case for Entities pages. And I don't know how to avoid it.
And sometimes it even stucks in "Login dialog". But thats really should not be, because I'm already logged in. And if I refresh page again, then login dialog disapears.
Motivation for or Use Case
It is bad for UX, thats why Im raising this issue. And I think in general its a bug. There is no reason to show 3 different pages ("403 error", "you are not logger in", "login dialog), because I'm actually logged in.
Reproduce the error
jhipster --blueprints vuejs

Use Firefox browser
Suggest a Fix
If you know what causing this in general, then I can try to fix it myself. I just found this issue.
I can say for sure its vuejs blueprint issue
JHipster Version(s)
6.8.0
JHipster configuration
there is nothing special. Its clean installation of khipster with vuejs blueprint. Problem is in VueJS blueprint implementation issue
Browsers and Operating System
Windows 10. Firefox 74.0.1

[X] Checking this box is mandatory (this is just to show you read everything)

@artem-korolev : similar to https://github.com/jhipster/jhipster-vuejs/issues/587 ?

@pascalgrimaud , yes. it is exactly same. Its only that I provided a bit more info. Don't how much sense it makes. In general it is same issue. Only that on Home page there is no "403, but there another page appears. Root cause of the issue is maybe the same.

Fixed by https://github.com/jhipster/jhipster-vuejs/pull/590


Endpoints for deployment status & cluster info

Task linked: CU-33ttz4 Added 3 New Endpoints & Remove 1

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.prithvi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Backport of sync with drools-wb architecture (which was merged a few days ago)

remove FastCompiledOptaPlanner..gwt.xml + add deps of drools-wb-webapp to avoid NoClassDefExceptions
Conflicts:
optaplanner-wb-webapp/pom.xml
(cherry picked from commit 9a230fb3913b6f6902bc081d8bb0569e32271294)

+1

6.4.x: 920312230b93b06bfaf684b41b685db5bca1782f


Alpine container image for fvm

Related https://github.com/dart-lang/dart_docker/issues/50
Is your feature request related to a problem? Please describe.
google/dart container images have a shocking number of CVEs. I generated a report using trivy on leoafarias/fvm and trivy reported 3 CRITICAL and 38 HIGH.
Describe the solution you'd like
Alpine images tend to have fewer CVEs. An Alpine image using FVM to install Flutter would be 👌
Describe alternatives you've considered
There is a container image for Flutter by CirrusCI but it installs Dart as part of Flutter installation. All instructions for installing Dart expect a Debian distribution with apt-get. I can't seem to find how to install Dart on Alpine.
Additional context
Our IT blocks images that have HIGH and CRITICAL CVEs older than 30 days.

@taras The container example from CirrusCI you provided does not seem to be installing Dart, but uses the dart version configured within Flutter. This seems like it would do the trick as you don't need to install Dart separately.

@taras This looks like good for me! Actually the current Dockerfile downloads Flutter sdk every time, and this isn't so efficient.
Maybe we can parametrized your Dockerfile to build multiple image to push to Docker Hub.
@leoafarias  To achieve this, we should adapt the current CI/CD to build and push different Docker images.

@andreadelfante I'm still working out the best way to configure this image for CI. The challenge is that .fvm directory comes from mounted workspace. I need to change FVM_HOME to that mounted directory so fvm will know where to retrieve config from.
I believe NVM looks up .nvm config by traversing the parent directories which makes it a little easier.

@taras fvm config --cache-path <CACHE_PATH> is the command you're looking for!

Sure. Do you want it to replace the current or add another one?

Add another one


[DOC] Fix rendering of TFR docstrings

Reference issue
Fixes https://github.com/mne-tools/mne-python/issues/10695.
What does this implement/fix?
Fixes minor issue related to indentation of admonitions.

Thanks @cgohil8 !


Undeclared defines while building native (DR_REG_EMAC_BASE)

I try to build the crate for the esp32c3 with native feature #10 enabled and get the following error:
FAILED: esp-idf/esp_eth/CMakeFiles/__idf_esp_eth.dir/src/esp_eth_mac_openeth.c.obj
In file included from /root/.espressif/esp-idf-release/v4.4/components/esp_eth/src/esp_eth_mac_openeth.c:36:
  /root/.espressif/esp-idf-release/v4.4/components/esp_eth/src/openeth.h: In function 'openeth_tx_desc':
  /root/.espressif/esp-idf-release/v4.4/components/esp_eth/src/openeth.h:40:37: error: 'DR_REG_EMAC_BASE' undeclared (first use in this function); did you mean 'DR_REG_HMAC_BASE'?
   #define OPENETH_BASE                DR_REG_EMAC_BASE
...

I use the version release/v4.4 and have CONFIG_ETH_USE_OPENETH=y enabled.
It could be a wrong configuration, so I tried to use the cargo-idf tool. But it depends on the same build, so it fails with the same error.
I recognized the macro is defined in soc/esp32/../reg_base.h. But this header is not be included when building for the esp32c3 in my configuration.

CONFIG_ETH_USE_OPENETH=y only works for the Xtensa esp32 chip & target.


Load images from data dir

I'd like to import images into the graphql data layer. The documentation is incomplete. Is this possible?

@darichey I`ll have to confirm, but if you add an entry to graphql like so
image = {
  id: 1,
  name: `Nice image`,
  image: `./static/images/nice.jpg` //full path
}

It gets processed into a queryable image which you can query at build-time according to your needs (size, etc).
Just hook on gridsome.server.js and do your thing. You can manipulate graphql there.
Best regards,


Multi-arch support

Hi. Thanks for the effort.
Could you please consider adding multi-arch to your images? arm/v7 and arm64/v8 are welcome.
I'm running my containers on a raspberry pi and it takes quite a while to build nginx. I also can't use the local built image on my k3s cluster since I don't have a docker registry configured.

Hello, right now, it takes a while on my machine (older Macbook Pro) as well.
I will consider using buildx (and learn about it) once I upgrade my main machine. It will be an ARM Macbook Pro, so one way or another I will have to support the old one and the new one, too. At that point, I will add arm/v7.
But I would do this only if the compile chain does not require radical changes (e.g., crazy source code patching).
tl;dr I have a positive attitude towards this, but not immediately

That's nice to hear.
In the meantime I have just setup a container running a docker registry just to serve the image to my k3s deploy. I also used buildx and was able to build both arm64 and arm/v7 without any modifications.
Command line for reference:
docker buildx build --platform linux/arm/v7,linux/arm64 --push -t myregistryhostname/gmmoreira/nginx-webdav-nononsense:latest .

I have hijacked my work iMac to try it out. Could you verify that pulling nginx-webdav-nononsense:multiarch works out of the box on your rPi?

@dgraziotin yep, it worked just fine out of the box.
│ Events:                                                                                │
│   Type    Reason     Age    From               Message                                                                                │
│   ----    ------     ----   ----               -------                                                                                │
│   Normal  Scheduled  2m55s  default-scheduler  Successfully assigned default/webdav-6ddd98449f-dwc7n to alarm                                                                                │
│   Normal  Pulling    2m55s  kubelet            Pulling image "docker.io/dgraziotin/nginx-webdav-nononsense:multiarch"                                                                                │
│   Normal  Pulled     58s    kubelet            Successfully pulled image "docker.io/dgraziotin/nginx-webdav-nononsense:multiarch" in 1m56.74386045s                                                                                │
│   Normal  Created    58s    kubelet            Created container nginx-webdav                                                                                │
│   Normal  Started    58s    kubelet            Started container nginx-webdav

Hey @gmmoreira, this is now part of my build system. You should be able to pull :latest on your rPI.
Now that Docker Inc. has stripped down free accounts from their CI systems and has refused to gift me an "open-source" license, I provide non-systematic releases wrt. upstream (nginx releases). Once I get my hands on a newer Macbook Pro, I might think of some clever way to trigger buildx runs every time nginx releases something.
Feel free to close this once you verify that it's working.

Sorry for the late response.
Just changed to latest tag and it works.
Thank you for the hard work and support.
I will close the issue now.


feat(logfile): add automatic logfile recorder/player for CLIs

What this PR does / why we need it
This PR adds an automatic cli logfile generator as well as player for said log files
I also removed the current tracing and logging code in the current CLI helpers, as well as better organized it. The logfile work is contained to pkg/cli/logfile

Jira ID
[DT-0]

Notes for your reviewers

Closing until this can be taken over again :(


Unable to Update Parent State from Child Component

Description
Currently, the ArcNodes does not support updating the state of a parent component from a child component. This limitation restricts the ability to manage and synchronize state changes between components, which is crucial for building interactive and dynamic user interfaces.
Steps to Reproduce
Create a parent component with some initial state.
Create a child component that should be able to update the parent component's state.
Pass a handler function from the parent to the child as a prop.
Attempt to call this handler function from the child component to update the parent's state.
Expected Behavior
The parent component's state should be updated when the child component invokes the provided handler function.
Actual Behavior
The parent component's state does not update, and no changes are reflected in the parent component.
Impact
This issue prevents seamless communication between parent and child components, limiting the framework's capability to build complex and interactive applications. It affects scenarios where the child component needs to influence or control the state of its parent component

CLOSED : https://github.com/arwysyah/ArcNodes/pull/76


About page

The screenshot carousel should include arrows. Also, can you hook up a bit of logic so that the left and right arrow keys navigate between them, and escape closes the modal? You can add a shortcuts object to the view just like an events object.
shortcuts:
  'right': 'onRightPressed'
  'left': 'onLeftPressed'
  'esc': 'onEscapePressed'

Can we get smooth scrolling if you click the navigation items? Currently this happens when you click "Learn More" on the /home page.
Underline beneath navigation should only be the width of the text, not text + padding (I assume this is what it is)
Navigation links should be vertically centered on the gold background (currently they sit a little high (probably because of the underline behavior?)
Let's add a paragraph break between "... first keystroke" and "With game-based learning..."
Slightly too much padding between Mission and Team sections -- reduce to about 200px.
For the team member avatars, use this styling on .img-thumbnail:

.img-thumbnail {         padding: 0px; // currently this is set to 4px         background-color: #7D0101; // our burgundy         border: 5px solid #F2BE19; // our gold }

Links to external sites should open in new tabs: all of the team member personal URLs, the job postings
<li>s under Employee Benefits should have padding-bottom: 7px
Lightbox behavior for screenshots should open the screenshot that is clicked (currently it starts at the desert level no matter which image you click)
Also too much spacing between Careers and Press section -- reduce to about 200px.
Link up<EMAIL_ADDRESS>to a "mailto:" underneath "Press & Contact"

Googling around for what UX people think of links opening in new tabs, I found some interesting pieces: http://libux.co/links-should-open-in-the-same-window/ https://css-tricks.com/use-target_blank/
They make pretty good arguments that we shouldn't change the default behavior of links by making them open in a new tab. I'm personally inclined to agree — I tend to find that unexpected behavior annoying. How attached are you to that feature?

I personally would agree on keeping link behavior unaltered in this case.

I would not update the default link behavior to open in a new tab.  It's super annoying.
You can make the final call as the author of these changes, since it's a little unclear which route to take.

Another vote for default behavior (opens in same window).
I actually used the other method (target = blank) for dndaw.com because
I thought of it as aggregating a set of new links, but the articles
Phoenix linked to convinced me otherwise. If, like me, people want to
open in other windows, it's easy enough to do.
On 2/24/2016 1:32 PM, Matt Lott wrote:

I would not update the default link behavior to open in a new tab.
It's super annoying.
You can make the final call as the author of these changes, since it's
a little unclear which route to take.
—
Reply to this email directly or view it on GitHub
https://github.com/codecombat/codecombat/pull/3414#issuecomment-188396372.

Last couple things: lower case file names (sketch.png isn't working currently because of that) and add arrows to the carousel (as in the Bootstrap carousel example, add glyphicon chevrons).

Download All button doesn't appear to be working, and it's referencing a live file.  Is this a cross-domain block?

Hey, poking at the new /about in Chrome on a mac, spotted these:

missing image file - "sketch.png"
download all button isn't working in the press section
Rob and Robin's avatars/faces are not clickable, but everyone else with a link's face/avatar is.
when clicking on the items in the menu, there's a nice little white border for Mission, but everything else had a giant empty white space that was 3 to 4 times larger.

Problems we can fix later:
Remove iOS job listing
Yellow menu bar isn't responsive/shrinking at small window widths
I'm done testing. The only blocking issue for me is the Download All button functionality.

There are some responsiveness issues as well, but they're not unique to /about and they're not pre-ship blockers.
Our main nav menu becomes three rows at 800 pixels wide. I think I'd prefer dropping to the hamburger.

Post-ship:
When you click on Press, you can baaaaarely see the bottom of the border around the last item(s) in Careers.

One more note, not a blocker. Maybe not even something worth fixing.
On smaller resolution screens, I see "Mission" as underlined, but I cannot see the mission statement/section. Not sure we should care. But if someone assumes that the "If you want to learn ..." part is the mission, they may click "Team" and end up skipping over the mission section.

@themaka you're on windows, right? Sounds like the borders act really funky there.
Otherwise, all those things should be fixed now, everyone!

I saw the weird borders on Mac/Chrome. Need screenshots?
On 2/24/2016 6:59 PM, Phoenix Eliot wrote:

@themaka https://github.com/themaka you're on windows, right? Sounds
like the borders act really funky there.
Otherwise, all those things should be fixed now, everyone!
—
Reply to this email directly or view it on GitHub
https://github.com/codecombat/codecombat/pull/3414#issuecomment-188526281.

Hrm, yeah, screenshots would help.

This is edge, but I got similar results everywhere. On the left is the
whitespace when you click Mission. On the right is the white space when
you click any of the others. The Chrome window is just to make it easy
to eyeball where the top of the text on the non-Mission links is.
Maka
On 2/24/2016 7:36 PM, Phoenix Eliot wrote:

Hrm, yeah, screenshots would help.
—
Reply to this email directly or view it on GitHub
https://github.com/codecombat/codecombat/pull/3414#issuecomment-188534940.

I don't think the screenshot made it into your comment :)


Provider does not update the state when alert is deleted externally

Steps to reproduce:

Create an alert using terraform
Delete the alert manually (API / Web interface, e.g externally to terraform)
Run terraform plan / apply command again

current behavior:
terraform command fails with
Error: API call GetAlertV2 failed with missing alert ...., data: {"errorCode":"Alerts/ALERT_NOT_FOUND","message":"alert id 1954709 not found","requestId":"b548481e-83df-40d8-b492-7fbb6715c6b5","parameters":{"alert-id":...}}

and require to manually remove the state using  terraform state rm ....
Expected behavior:
upon encountering ALERT_NOT_FOUND response from API, the state should be updated accordingly so terraform plan will include the creation of the missing alert resource

Hi @alonz thanks for informing us. We'll work on a fix for this issue.

Hi @mirii1994 we met the same issue

Hi @alonz , we released v1.10.0 that should handle this issue.
Please let us know if the update solves it.


[FLINK-2808] Rework state abstraction and clean up task / operator internals

This pull request fixes many related/intermixed issues. It was hard to split this into individual issues.
Crucial bug fixes

State snapshots for memory backed state previously copied a reference into the StateHandle, after which the streaming program continued. If the state was mutated prior to serialization by Akka, the mutated state was checkpointed, rather than the state at the point of drawing the snapshot.

Key/value state is checkpointed as a whole, rather than individually per key.

Memory-backed state now has a maximum size that is checked upon checkpointing. Exceeding that size fails the checkpoint. Before, too large state simply resulted in an oversized Akka frame that was dropped, silently letting the program run without ever completing a checkpoint.

User-facing changes

The state backend is not only responsible for storing snapshots of the user state, but they also define how exactly the key/value state is represented in the first place. This allows us to plug in external key/value stores to store the Flink key/value state. Default implementations store the state in memory / files.

State backend offers additional methods to checkpoint directly into streams.

One can configure arbitrary default state backends via a factory interface that creates them from the TaskManager configuration.

Key/value state supports arbitrary types without extra checkpointer logic, but user needs to supply type of state (via class or TypeInformation)

Removed the OperatorState that is non-partitioned. The only type of state remaining through the OperatorState abstraction is partitioned key/value state in functions that are applied on a KeyedStream. Consequently, the mapWithState() and related methods are only available on the KeyedStream

Internal cleanups

Checkpoint barriers are forwarded earlier, to reduce latency introduced by checkpoints.

Fewer in-memory copies when checkpointing to the file system state backend

The StreamingRuntimeContext is used purely for UDF interaction, not to hand over components to the operators.

The infinite reduce and aggregations work properly on key/value state, rather than maintaining their own maps

made the OutputHandler (now called OperatorChain) type safe and simpler

made clear distinction between responsibilities of StreamTasks (input/output streams, setup of operator chain, checkpoint coordination) and operators (scope of one function and runtime context)

clean up checkpointing logic between operator (checkpoints generic key/value state) and UDF operators (checkpoint UDFs)

removed Configuration from operator open() method (was used in confusion with UDF open(Configuration())

Overall looks very good. :+1:
I personally like having the non-partitioned operator states and I use them in my programs, so I would prefer keeping them.

So my argument is that the overhead of implementing the Checkpointed interface for simple counters , offsets and the like is simply too much (and annoying).
We can also introduce some annotations that the user can use to tag the state with. Then the only thing we need to make sure is so that these support some custom checkpointing logic. (like the state checkpointer interface)
Another thing we should consider is that the Checkpointed interface will never allow any lazy state access logic.

on a related note, is anyone planning to complete snapshotting for cyclc graphs for the 0.10 release? Unfortunately I do not have time to work on it this week but it would be great to support it for 0.10 already

Other important thing:
I think it would be very useful to add some extra context information to the snapshot methods. Something that can be used to identify the operator that took the snapshot. Maybe a combination of task id + task index.
I am currently trying to implement a sql based backend, and I would really need to store this information so I can then work with the checkpoint data from the outside.

I can live without the non-partitioned OperatorStates, but the context info for the snapshots is very hard to work around I think.

@senorcarbone I think the cyclic graphs feature will be hard to get into 0.10

Also in the StateBackend interface a close method would come in handy, similarly to the initialize to close connections etc. in case of failures.

@ktzoumas that's understandable! We could consider it for the maintenance release maybe if there is enough time

Thanks for the fast and good feedback.
Concerning the removal of non-partitioned operator state:

As per prior discussion offline, I wanted to consolidate this to a core feature set, since it is hard to remove such features once they are released and endorsed
For simple states, let us add an annotation @State (with possible checkpointer/serializer @State(checkpointer=new BloomFilterCheckpointer())) which serves the same purpose and would be more lightweight even. I would put that on the list for the next release.

Multiple key/value states per operator: Will re-add that (simple effort), it is in fact very useful
Closing the state backend: Will add that, good idea
Concerning context info during checkpointing:

You should have access to the RuntimeContext when drawing the snapshot, which means you can access the task index. Let us also add the JobVertexID to the RuntimeContext and these values stay deterministic across restarts (state handles are stored under JobVertexID + task index).

I was thinking about giving access to the state backend in the Checkpointed interface methods, but let's make a design for this for the next release.

With addressing these issues, any objections against adding this?

As for the context, I did not mean to add it to the Checkpointed interface but to the state backend method calls.
Other simpler solution for now would be to make the environment or the runtimecontext accessible from the backend, so it knows which task it does the checkpointing for. This is probably the cleanest solution for now until we figure out the exact requirements.
Otherwise :+1: from me.

I think when drawing the snapshot with Checkpointed you are already inside a streaming Function or internal operator where one can easily access that information anyway.
I think that is fine that way, I agree with @gyfora that access from the StateBackend is more important as that is potentially decoupled from drawing the snapshot itself.
As for other points listed by @StephanEwen they sound reasonable for me.

Manually merged


Datetime widget fixes and improvements

Targeting all open issues with the label area: extensions/widgets/datetime. Hopefully, I get it right this time.

don't display the current date by default or when the field is empty (#3679) - potentially breaking change
add default: '{{now}}' option to enable the current behavior of displaying the current time (using the specified format)
add UTC indicator when picker_utc: true
improve how Z in format and picker_utc: true work together
reorder format importance: if format is set, date_format and time_format (if strings) are ignored (#7250)
... I will update this list as I make progress

Looks like you also fixed this one: https://github.com/decaporg/decap-cms/issues/7212


Source scenarios disappeared after new table join and slicing is applied on new hierarchy

Steps to reproduce
I created some source simulations with a single table.
Then I created another table and I get N/A for the new hierarchy resulting from the new table that is joined to the cube:

Then, after applying slicing on the new hierarchy, I get exception on the previous visualization and lost the simulated scenarios:

Sample notebook: Untitled.zip
Environment

atoti: 0.6.1
Python: 3.9.6
Operating System: win32

Logs (if relevant)
server.log

In fact, I also lost the 2 members x4 and x7

Hi,

x4 and x7 are not in table2 so test_col has the value N/A, this is normal.
making test_col slicing means that you cannot aggregate on this column, if you add test_col in your last visualization you will be able to see the scenario, it has not disappeared it is just that null values are not shown in widgets.
The fact that visualization broke in previous cell is the same as this issue https://github.com/atoti/atoti/issues/334

Indeed in 0.5.5 it was like this :

I'm investigating this bug

Hi, I've understood the issue and it is not one.
Since 0.6.0 :

Two ways to fix this:

Create the table_2 prior to the scenario creation
load the data in the scenario if table_2 is defined after the scenario on table_1

table2 = session.read_pandas(df2, table_name="test_table2", keys=["a"])
table2.scenarios["test_scenario"].load_pandas(df2)

If it is possible try to define the table before the scenario as it is less code.
I let you close this issue if it is clear for you


Connect to Aws IOT

I have a treadmill that has only Bluetooth with if I'm finishing a module in esp32 has access to the information of the treadmill  and is record online Aws IOT.  Can you make a feature that does not ask the ip but a complete url?  and what is the JSON format expected by the endpoint?  Do you have an example for me to copy?  Thank you

Despite the config name, it doesn't need to be an IP, it could be a URL. As long as there is a compliant websocket at the other end, it will connect.
Here's where the connection is made (also on line 65, if we end up scanning for the iFit websocket): https://github.com/dawsontoth/zwifit/blob/master/src/ifit.js#L42
The expected JSON can be seen easiest in the same file, in the onMessage function. https://github.com/dawsontoth/zwifit/blob/master/src/ifit.js#L120 The message is parsed to a string then from JSON to an object. You can ignore the current state variable, that's mostly for debugging purposes. But lines 138, 155, 158 and 161 are what you're interested in.


Feature

continued from #14

I see! and I gotta say, those look awesome. Great improvement upon my original, rather simple design 😅
For the sake of simplicity I would keep the plugin exclusion to the plugin name. Most people don't know stuff like plugin IDs, and I don't even have an idea what the usecase for a regex could be here.
Also, I'd suggest hardcoding that divide and conquer excludes itself.
The unbisect, rebisect commands etc are awesome, but I am pretty sure they need some explanations in the readme for the less-tech-savvy users. Also, the current commands that I originally created can probably be removed by now, since your commands are smarter anyway?

Exclusion is only by name by default. I figure the id's don't change as often as the names, and that if eventually other plugins use this plugin's functionality they'll probably want to pass id's. I don't see the harm in having the option there but disabled by default
DAC should already be ignored by default? Is it not on your end?
Yeah, I'll update the readme and add a gif or two
Yeah, so I wasn't quite finished refactoring, that's why I was leaving #14 open. It's all removed now that it works with snippets.

i.e. don't worry about merging this, I'm leaving the request open so all of the changes can be merged in one pr to make things simpler on master

Exclusion is only by name by default. I figure the id's don't change as often as the names, and that if eventually other plugins use this plugin's functionality they'll probably want to pass id's. I don't see the harm in having the option there but disabled by default

Also, I guess my original thought for allowing regex is stuff like this:

If you have a bunch of similarly named items, or you want to make sure you don't disable any plugins that are command-palette-related (or hotkey related, etc.) then you can easily exclude them all

DAC should already be ignored by default? Is it not on your end?

it is, but I don't see why the user should be able to even remove DAC from the list of ignored plugins. Doing so will definitely break any sort of bisecting being done, and I cannot think of a scenario where it would make sense to let DAC disable itself.

If you have a bunch of similarly named items, or you want to make sure you don't disable any plugins that are command-palette-related (or hotkey related, etc.) then you can easily exclude them all

Oh I see. Yeah, excluding only hotkey plugins is a scenario that would make sense to me, yeah.

it is, but I don't see why the user should be able to even remove DAC from the list of ignored plugins. Doing so will definitely break any sort of bisecting being done, and I cannot think of a scenario where it would make sense to let DAC disable itself.

It won't break anything, the last reset would just get restored when it's reenabled. There's probably not a good reason for letting them do it, but it makes the code simpler and demonstrates to the user how to use the feature. I don't care too much either way but I've spent all the time I can on this for now

Anyways, I think it's in a good state for a 1.0 release


add colab badge

I will merge after I go through the colab notebook and finalize it.

Yes, we need a second eye.

closing since I wanted to put the notebook in the repo, and used that link instead.


Some control keys not working

A brief description

Some control keys aren't working for me in Bash on Windows, which prevents me from using emacs.

Expected results

$ showkey -a
(hit control-spacebar)
^@        0 0000 0x00
(hit control-/)
^_       31 0037 0x1f

Actual results (with terminal output if applicable)

$ showkey -a
(hit control-spacebar)
(no response)
(hit control-/)
(no response)

Your Windows build number

14393.51

This is actually a dupe of another issue, maybe #583? Probably many more going back a while.
It looks like there are some recent changes in kernel-land that actually re-enable C-Spc, C-@, C-a, etc, so shout out to bperkins for that fix!


Information about policy params in data.pt and thier corresponding metaworld tasks

Hi,
I have a query about the policy params. In your data.pt file, i can see 17286 policies (SAC) {self.data['param'].shape : torch.Size([17286, 22664])} and corresponding traj and task embeddings. But there is no information about what task that policy corresponds to (I mean which one of the 10 metaworld tasks). Could you please provide additional information on this regarding the corresponding task?
Also, in paper its mentioned that policy network architecture used for MetaWorld is a 4-layer MLP with 128 hidden units, containing a total of 22,664 parameters. But you also mentioned in Dataset section that you collect 1500 policy networks for each task in MetaWorld and Robosuite. These networks are sourced from policy checkpoints during SAC (11 ) training. So, is the SAC same as the 4-layer MLP?

We have updated the single task data in: https://huggingface.co/datasets/cheryyunl/Make-An-Agent/tree/main/train_data/single task
If you need the task information, please use the single task data.
The policy structure is in: https://github.com/cheryyunl/Make-An-Agent/blob/1a111f767b7381125af4ccc366a20fad215719f5/PolicyGenerator/display/model.py#L44, same as the single RL policy.


Problems raised about missing argument when calling a function decorated by celery.shared_task

Environment data

Language Server version: 2020.6.1
OS and version: Ubuntu 20.04
Python version 3.7.7, virtual env with requirements joined
requirements_pypi.txt

Expected behaviour
When calling a task defined with celery.app.shared_task decorator, and naming argument, Pylance raises a problem "Argument missing parameter for 'fun'. See code snippet.

Actual behaviour
No problems should be raised.
Logs
[FG] parsing: tests.py (10ms)
[FG] binding: tests.py (2ms)
[BG] analyzing: tests.py ...
[BG]   parsing: tests.py (7ms)
[BG]   binding: tests.py (1ms)
[BG]   checking: tests.py (16ms)
[BG] analyzing: tests.py (25ms)
[FG] parsing: tests.py (5ms)
[FG] binding: tests.py (2ms)
[BG] analyzing: tests.py ...
[BG]   parsing: tests.py (1ms)
[BG]   binding: tests.py (0ms)
[BG]   checking: tests.py (29ms)
[BG] analyzing: tests.py (30ms)

Code Snippet / Additional information
from celery.app import shared_task

@shared_task
def function_one(argument):
    return []

def function_two():
    return function_one(argument=2)

Pylance requires type stubs to do the best job possibly with type analysis. In this case, I'm presuming that you don't have a type stub available for celery, so it is doing its best to infer types from the library implementation based on the return type(s) of shared_task. In this particular case, shared_task returns two different types, and the type checker can't tell which one is returned for this particular call site. Both types are functions, but one of them is a function that requires a parameter called fun, hence the error.
The best workaround in this case is to find (or create) a type stub for the celery package. A type stub will provide the proper annotations so the type checker can perform analysis correctly in this case without emitting an error.
If you can't find a type stub and don't want to create one, you can suppress this error using "# type: ignore".

I've updated the "missing parameter" diagnostic rule to be off by default when typeCheckingMode is "off". Assuming that you haven't set typeCheckingMode to "basic" or "strict", this diagnostic will be suppressed. This change will be in the next version of Pylance.

ok thanks you very much for your feedback. I'll try to add so type stub for celery :+1:
By the  way, this is a great extension, very nice work :clap:

This issue has been fixed in version 2020.7.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/master/CHANGELOG.md#202070-9-july-2020


⚠ Bofrost.be has degraded performance

In 680031c, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2332 ms

Resolved: Bofrost.be performance has improved in 28b03f3 after 56 minutes.


Add ability to run nodes with different tezos images/implementations

closes #113
closes #251
closes #276
closes #257

@elric1 ready for your review


Failing on Heroku - please remove runtime dependencies

Do we really need these runtime dependencies?
Can't they be just development dependencies?
Since version 2.0.7, settingslogic has jeweler, rake, rspec and ruby-debug19 as its runtime dependencies. Of these, ruby-debug19 ends up requiring linecache19, which takes ages to compile locally and fails to compile on Heroku.
Thanks.

This should be fixed in 2.0.8

Thanks


Broken release

The latest version in npm (1.9.1) is broken.
The app crashes as soon as you select the value in the sheet with the following error in adb logs
Illegal callback invocation from native module. This callback type only permits a single invocation from native code.
The error occurs because RN allows the action press callback to be invoked only one time, but with the latest feature, which adds a callback invocation on cancel press, the callback gets executed twice, which causes a crash.

For anyone stumbling across this - install version 1.8.1.

@NSLS & @Doko-Demo-Doa
Fixed the crash here: #18

I'll test it out latet, thanks!


Update FAQ with changing transport guide.

Update faq page with a guide about changing transports.

@erikastaroza  Whilst your editing the FAQ, can you change this line:
Only host / server can check this_, below is an example of how to sync this number to all players_.
Makes no sense now the code examples got removed 😔

@erikastaroza  Whilst your editing the FAQ, can you change this line:
Only host / server can check this_, below is an example of how to sync this number to all players_.
Makes no sense now the code examples got removed 😔

Maybe change the line about forwarding? Not every transport requires port forwarding. Maybe state that some transports require port forwarding.

Maybe change the line about forwarding? Not every transport requires port forwarding. Maybe state that some transports require port forwarding.

Updated :)

Updated :)

Updated :)

Updated :)


blog

blog
added packages

#33  👈
main

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

Join @leonchike and the rest of your teammates on  Graphite


noobaa api account_api list_accounts command fails for INVALID_SCHEMA_PARAMS

Environment info

NooBaa Version:

INFO[0000] CLI version: 5.9.0
INFO[0000] noobaa-image: noobaa/noobaa-core:master-20210526
INFO[0000] operator-image: noobaa/noobaa-operator:5.9.0

Platform: OCP 4.7.4

Actual behavior
On a system with noobaa freshly installed (only one account and a few buckets had been created), we get the following.  Whether accounts exist, or not, no errors should get produced.  In this case, one account existed called "s3user1"

Expected behavior
No errors should get produced and the existing account should be shown.
Steps to reproduce

Fresh install noobaa manually
Create one account
Run noobaa api account_api list_accounts on the infra node

More information - Screenshots / Logs / Other output

@steve-delillo This call requires an object for params, but it has no required properties, so from the CLI do like this:
noobaa api account_api list_accounts '{}'

Let me know if this works.
Closing.

Thanks, Guy.  Yeah, that worked very well.  I thought for just listing, we wouldn't need object call outs.


Move the SegoeUISymbol font to the getNonStdFontMap (PR 8698 follow-up)

For reasons that I now cannot even begin to understand, the non-standard SegoeUISymbol font was placed in the getStdFontMap. That honestly makes no sense, hence this patch which does what I should have done from the start.

/botio test

Thanks!


Single sign-on, add a switch, allow multi-point login, to facilitate automated testing

In GitLab by @wknet123 on Sep 30, 2017, 10:11

In GitLab by @yhua123 on Nov 8, 2019, 07:39
need signal login. SSO
the user login other site, writing right username ad password. System will send a new token for current user, and destroy old token.

In GitLab by @wknet123 on Nov 8, 2019, 07:39
Fixed with PR #541

In GitLab by @sokril on Nov 8, 2019, 08:12
closed

In GitLab by @sokril on Nov 8, 2019, 08:12
assigned to @wknet123


Correct the first observation in Step 6 of the Codelab on 'Building a Cupertino app with Flutter' page

Page URL
https://codelabs.developers.google.com/codelabs/flutter-cupertino#5
Page source
No response
Describe the problem
In step  6. List products for sale, the first Observations is wrong.
It should describe ProductRowItem as a StatelessWidget, and the layout.
Currently, it describe CupertinoSliverNavigationBar and Stateful Hot Reloaddescribes
Expected fix
Describe the correct information.
Additional context
No response

It looks like this codelab does not exist anymore. Can this then be closed?


Bug error

Bug found ,using Vampire/setup-wsl@v1 ,Error: getCacheEntry failed: Cache service responded with 500

Same error as #378 which is related to actions/cache#698

Hi, this is related to caching and has been resolved.  Please see https://github.com/actions/cache/issues/698#issuecomment-992069658 for any further info.


Support Kotlin source folder

Right now the kotlin source folder isn't supported right away, it would be nice to have it without a specific configuration. I already looked into it but couldn't get the check for a applied kotlin plugin to work.
Right now its possible with the additional source directories configuration like that
coveralls {
    sourceDirs += ['src/main/kotlin']
}

The right place to add the check for the plugin and additional source folder would be here: JacocoSourceReportFactory.groovy#L51 I could be done like the scala plugin logic which above line 50 I guess.

Seems long overdue, yeah?

Right now the kotlin source folder isn't supported right away, it would be nice to have it without a specific configuration. I already looked into it but couldn't get the check for a applied kotlin plugin to work.
Right now its possible with the additional source directories configuration like that
coveralls {
    sourceDirs += ['src/main/kotlin']
}

The right place to add the check for the plugin and additional source folder would be here: JacocoSourceReportFactory.groovy#L51 I could be done like the scala plugin logic which above line 50 I guess.

if I try that I get "Assignment operators ambiguity"
What am I missing?

If you are using the kotlin gradle dsl, the correct syntax is:
coveralls {     sourceDirs = mutableListOf("src/main/kotlin") }


Added How to Start Your Game Development

Added link to an official tutorial topic about How to Start Your Game Development

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you, but there is already two links to unity on this page. We welcome future PR's.
Thanks, and happy coding!


window.ignite is not a function

I'm developping a laravel project with Metronic 8 theme
Since I upgraded to Laravel 9 from the last version of Laravel 8, when I get an error I have an empty page with errors on the console.
First an
Uncaught SyntaxError: Unexpected token '{'
Which is due to the last line of this block of code
* Validation function for `value` and `defaultValue`.
 */function checkSelectPropTypes(props){{checkControlledValueProps('select',props);for(var i=0;i<valuePropNames.length;i++){var propName=valuePropNames[i];if(props[propName]==null){continue;}var isArray=Array.isArray(props[propName]);if(props.multiple&&!isArray){error('The `%s` prop supplied to <select> must be an array if '+'`multiple` is true.%s',propName,getDeclarationErrorAddendum());}else if(!props.multiple&&isArray){error('The `%s` prop supplied to <select> must be a scalar '+'value if `multiple` is false.%s',propName,getDeclarationErrorAddendum());}}}}function updateOptions(node,multiple,propValue,setDefaultSelected){var options=node.options;if(multiple){var selectedValues=propValue;var selectedValue={};for(var i=0;i<selectedValues.length;i++){// Prefix to avoid chaos with special keys.
selectedValue['$'+selectedValues[i]]=true;}for(var _i=0;_i<options.length;_i++){var selected {// Do not set `select.value` as exact behavior isn't consistent across all

and an error
window.ignite is not a function
When I remove the package from my project, I get the default symfony error page without problem. Did I miss something when I installed the laravel-ignition package ?
Version: 1.0.6
Php: 8.0.6
Laravel: 9.1

Hi @ankheur, can you try to replicate the issue again on the latest version of laravel-ignition (1.0.6) and its dependencies? You'll probably need to run composer update to pull in any changes to the underlying spatie/ignition package.
Thanks!

Hi ! The issue seemed to have come from a dependency problem from the Metronic package and an update from them resolved the issue. Thanks and sorry for this thread


Make key based settings/toggles available through config/command-line

I pretty much always use the c > Show/hide file count and m > Show/hide latest mtime keys but I couldn't find a way to set these options via the config file or through command-line arguments. Please let me know if it slipped past my eyes.
It would be nice if all the options you can toggle via a keyboard key would also be available via command-line arguments and/or through the config file.
One way that is probably less work would be to define a set of keys that are "pressed" when gdu starts.
init-keys: cm

gdu --init-keys=cm

Sorry, this issue slipped my attention.
We have added --show-item-count (-C) option in 5.28.
I will add option for Show/hide latest mtime as well.


Removed invalid metric from applicationGateways

Removed BlockedReqCount from Microsoft.Network/applicationGateways since is not supported
az monitor metrics list --resource /subscriptions/<subscription_id>/resourceGroups/<rg_name>/providers/Microsoft.Network/applicationGateways/<app_gw_name> --metric BlockedReqCount
(BadRequest) Failed to find metric configuration for provider: Microsoft.Network, resource Type: applicationGateways, metric: BlockedReqCount, Valid metrics: Throughput,UnhealthyHostCount,HealthyHostCount,TotalRequests,AvgRequestCountPerHealthyHost,FailedRequests,ResponseStatus,CurrentConnections,NewConnectionsPerSecond,CapacityUnits,FixedBillableCapacityUnits,EstimatedBilledCapacityUnits,ComputeUnits,BackendResponseStatus,TlsProtocol,BytesSent,BytesReceived,ClientRtt,ApplicationGatewayTotalTime,BackendConnectTime,BackendFirstByteResponseTime,BackendLastByteResponseTime,AzwafTotalRequests,AzwafCustomRule,AzwafSecRule,AzwafBotProtection
Code: BadRequest
Message: Failed to find metric configuration for provider: Microsoft.Network, resource Type: applicationGateways, metric: BlockedReqCount, Valid metrics: Throughput,UnhealthyHostCount,HealthyHostCount,TotalRequests,AvgRequestCountPerHealthyHost,FailedRequests,ResponseStatus,CurrentConnections,NewConnectionsPerSecond,CapacityUnits,FixedBillableCapacityUnits,EstimatedBilledCapacityUnits,ComputeUnits,BackendResponseStatus,TlsProtocol,BytesSent,BytesReceived,ClientRtt,ApplicationGatewayTotalTime,BackendConnectTime,BackendFirstByteResponseTime,BackendLastByteResponseTime,AzwafTotalRequests,AzwafCustomRule,AzwafSecRule,AzwafBotProtection

Learn Build status updates of commit 2c7ce86:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/azure-monitor/essentials/metrics-supported.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@rboucher
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


⚠ Bofrost.be has degraded performance

In 4a2e4de, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1011 ms

Resolved: Bofrost.be performance has improved in e19ff44 after 30 minutes.


nixos/postgresql: add missing parentheses in creating pythonpath

sorry, but this time I've actually tested this commit: https://buildkite.com/awakesecurity/end-to-end/builds/113699


build(platformio): Improve PlatformIO Configuration

The current configuration of PlatformIO is incorrect and causes build files to be included in the search path.
Particularly, external library dependency directories were included in their entirety.
I became aware there was an issue at #100  when AUnit released v.1.3.
Specifically, this PR does the following:

configures PlatformIO to create build and dep dirs in a specific location out of the search path.
removes the now-unneeded lib_ldf_mode keys.
updates the src_filter keys.
adds a dummy prototype file for correct CI build tests.
updates the changelog.

All changes are non-breaking.

What kind of change does this PR introduce?

[x] Build

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does this PR release a new version?

[ ] Yes
[x] No

The PR fulfills these requirements:

[x] It's submitted to the develop branch, not the master branch
[x] All tests are passing
[ ] New/updated tests are included

The ci/circleci: build-linux-default job is failing as of 774e52a9c5cfc38ceff767d7edae8d118efae3bf. Please review the logs for more information.
Once you've pushed the fixes, the build will automatically re-run. Thanks!

The ci/circleci: build-linux-default job is failing as of 774e52a9c5cfc38ceff767d7edae8d118efae3bf. Please review the logs for more information.
Once you've pushed the fixes, the build will automatically re-run. Thanks!

Codecov Report

Merging #101 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #101   +/-   ##
========================================
  Coverage    91.14%   91.14%
========================================
  Files           27       27
  Lines          836      836
========================================
  Hits           762      762
  Misses          74       74

Continue to review full report at Codecov.

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


Always compute before “stamping” the validation

Computing the reference value could potentially be side-effectful (from the perspective of the revision timeline), so you should always compute the value before getting the tag value.

cc @wycats @krisselden


Where are the COCO pertrained weights?

Hi I am trying to find the COOC pretrained weights. You mentioned that they are in the README  file however I only see a generic pertrained model. Is that it?

@sshaar please find them in the first column in the tables, click the link.

the link is invalid? I can not get them


[DOCS] Tutorial for LiveServer usage

This introduces a tutorial to complement #164 based on a long work session with @asinghvi17 .
@asinghvi17 , for deployments, will the creator need to remove these tweaks from their make.jl file? Or can these tweaks be safely left in when deployed? I wasn't sure if they could be left in or not.
Otherwise, feel free to make additional tweaks here as needed!

For deployment you would need to remove all tweaks, maybe we can make a convenience function to do this for you though (something like MarkdownVitepress(...) |> live_serveable maybe.

That sounds great @asinghvi17 -- do we want to make that functionality now and then merge these two PRs or go ahead and merge the tutorial + your functionality that you just added and make this live_serveable function later? :thinking:

Added this in @asinghvi17 !

Right back at ya @asinghvi17


Download Diagram as Image

Provide an option to download the diagram as an image.

Was literally gonna come and add this as an enhancement request. Nice job!

Available in v0.2


Fix NPE in segment allocation when reduceMetadataIO is true

#17496 introduced an NPE due to an incorrect map key.
This patch fixes that bug.

Thanks for the reviews, @clintropolis , @AmatyaAvadhanula !


change volume path to value

This PR is to solve issue #40 for change volume path to values.
Basically some host volume path should be able to config by users so make it as a value. Also make it a value if it can be used in koordlet args.
Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist:

[ ] I have bumped the chart version according to versioning
[ ] I have updated the chart changelog with all the changes that come with this pull request according to changelog.
[ ] Any new values are backwards compatible and/or have sensible default.
[ ] I have signed off all my commits as required by DCO.

Changes are automatically published when merged to master. They are not published on branches.

/lgtm


Support for rv32e in software stack

Currently software stack is written for rv32i, using all (or most) of the 32 available registers. If needed, some engineering effort will be required to make it work with 16 registers, mostly in entry point code

Builds, but shows errors in prime factoring linkage:
riscv64-elf-ld: cannot find default versions of the ISA extension `i'
riscv64-elf-ld: cannot find default versions of the ISA extension `i'
riscv64-elf-ld: cannot find default versions of the ISA extension `i'
riscv64-elf-ld: cannot find default versions of the ISA extension `i'

Perhaps it should be investigated someday, but now it seems to build successfully


Add conda-config (similar to elpy-config) command to re-evaluate cached values

conda--config caches the parsed output of conda config --show --json. If that's wrong the first time round, there are constant weird error messages.
In my case, I was getting Wrong type argument: arrayp, nil on all conda-* functions called. Turns out conda--config contained (json-parse-error "invalid token near 'sh'" "<string>" 1 2 2). It took forever to realize was actually the cached value, not a current error...
Perhaps having conda-config similar to elpy-config to re-load and show the (cached) configuration would be a not-too-complex fix to this and similar issues?

That's definitely an interesting thought!
Elmar Pruesse @.***> writes:

conda--config caches the parsed output of conda config --show --json. If that's wrong the first time round, there are
constant weird error messages.
In my case, I was getting Wrong type argument: arrayp, nil on all conda-* functions called. Turns out conda--config
contained (json-parse-error "invalid token near 'sh'" "" 1 2 2). It took forever to realize was actually the
cached value, not a current error...
Perhaps having conda-config similar to elpy-config to re-load and show the (cached) configuration would be a not-too-complex
fix to this and similar issues?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

--
Rami Chowdhury
A mind all logic is like a knife all blade - it makes the hand bleed that uses it.
-- Rabindranath Tagore

Does #136 look like it'll do the trick?


Nesting styled components with styled() and adding prop types does not work correctly

Environment
System:

OS: macOS 13.5.2
CPU: (10) arm64 Apple M1 Max
Memory: 49.19 MB / 64.00 GB
Shell: 5.9 - /bin/zsh

Binaries:

Node: 18.17.0 - ~/.nvm/versions/node/v18.17.0/bin/node
Yarn: 1.22.19 - ~/.yarn/bin/yarn
npm: 9.6.7 - ~/.nvm/versions/node/v18.17.0/bin/npm

npmPackages:

babel-plugin-styled-components: 2.1.4 => 2.1.4
styled-components: 6.0.8 => 6.0.8

Reproduction
https://codesandbox.io/s/styled-components-base-forked-j8f2nt?file=/index.tsx
Steps to reproduce
const Component1 = styled.a<{ prop1?: boolean }>``

const Component2 = styled(Component1)<{ prop2?: boolean }>``

const Component3 = styled(Component2)<{ prop3?: boolean }>``

const Component4 = () => <Component3 prop1={true} prop2={true} /> // compiles fine

const Component5 = () => <Component3 prop1={true} prop2={true} prop3={true} /> // compile error, prop2 does not exist

Expected Behavior
Should compile.
Actual Behavior
Component5 does not compile, prop2 cannot be found.

i am getting same error with 6.0.8 . with 6.0.7 types are working

Seeing the same as well!

i think this is related to
https://github.com/styled-components/styled-components/issues/4165

6.0.8 is broken with types... USE 6.0.7

i think this got broken on this commit
https://github.com/styled-components/styled-components/commit/6ee6c23994b9ac41eba06b112a0f6670e41de757

i created this PR
https://github.com/styled-components/styled-components/pull/4190

try 6.1.0

I still got the same issue in 6.1.0 too

I've added failing tests to help fix this in https://github.com/styled-components/styled-components/pull/4219


Fixes #12 / [Finishes #86805502] Fixing http 500 on institutional proposal

Initially, I accidentally committed the ekualiti formatted JSP file and applied the fix to that file.
Realizing my mistake, I applied the source file, then reapplied the fix.


bosh-dns noble support

Noble switching from resolvconf to systemd-resolved poses a problem for bosh-dns.
Currently bosh-dns injects itself at the top of /etc/resolv.conf via the resolvconf tooling. Bosh-dns then reads the other entries in /etc/resolv.conf and stores those as upstream recursors. Since bosh-dns is at the top of /etc/reslv.conf, it will always be queried first and it can then pass the query onto the recursors and has quite a few features to control this behavior.
With systemd-resolved, the system resolver is doing much the same as bosh-dns was doing. This poses a couple problems.

How do we inject bosh-dns into the configuration
What do we do with the current recursor features of bosh-dns

How do we inject bosh-dns into the configuration:
We have several options here.

Reconfigure systemd-resolved to use the old way of writing /etc/resolv.conf and leave bosh-dns alone. This may work, but poses a problem because systemd-resolved has a system bus API for resolving queries that bypasses /etc/resolv.conf, so as more tools switch to that, bosh-dns is left out of the loop
Use the systemd-resolved apis to register bosh-dns as a resolver. systemd-resolved has both global resolver and interface specific resolvers. Unfortunately, it seems like the APIs only allow you to add interface specific resolvers, so this gets a bit weird.
Write the bosh-dns IP to a new file in /etc/systemd/resolved.conf.d/ where the bosh-agent writes the DNS servers it was given. This is most simple, but also has the downside that we have no control over how other resolvers are used by systemd-resolved

What do we do with the current recursor features of bosh-dns
These options get limited by the above choice

Figure out some way to remove all other resolvers from the systemd-resolved configuration and keep bosh-dns in charge of all dns resolution. This prevents us from using much of the new good behavior provided by systemd-resolved
Disable bosh-dns upstream resolver functionality in noble. This would leave systemd-resolved in complete control of resolution, and bosh-dns would only be responsible for bosh specific queries. The dns configuration for bosh-dns could even include routing domain information so systemd-resolved would only query bosh-dns for the domains bosh-dns actually knows about.

You may already have investigated this, and/or have considered it and disregarded it as being bad. Apologies for the noise if so.
Given that the systemd-resolved APIs don't really do what we want, might it be worth trying to set [Resolve] ... DNSStubListener=no (and maybe also LLMNR=no and MulticastDNS=no) in resolvd.conf https://www.freedesktop.org/software/systemd/man/latest/resolved.conf.html#Options, and using the resolvconf-compatibility mode of resolvectl to manage resolv.conf https://www.freedesktop.org/software/systemd/man/latest/resolvectl.html#Compatibility with
    resolvconf(8)?

Does that avoid the problems in the first option above?

...but poses a problem because systemd-resolved has a system bus API for resolving queries that bypasses /etc/resolv.conf, so as more tools switch to that, bosh-dns is left out of the loop

As more things start ignoring resolv.conf and start using the systemd-resolved system bus APIs, us continuing to configure bosh-dns to only use resolv.conf becomes a bigger problem.

Does that avoid the problems in the first option above?

Nope. That first option actually totally precludes the first half of the thing I suggested. It's amazing that there's a documented way to shut down everything but the dbus query interface. Sorry for the noise.

Write the bosh-dns IP to a new file in /etc/systemd/resolved.conf.d/ where the bosh-agent writes the DNS servers it was given. This is most simple, but also has the downside that we have no control over how other resolvers are used by systemd-resolved

I believe that this does not work. Yes, it's possible to use this to add a new "global" dns server to systemd-resolved, but my understanding of what systemd-resolved would do with that was incorrect.
I was able to change bosh-dns to disable all recursing and to add a reference to itself in /etc/systemd/resolved.conf.d/ rather than using resolvconf, but once it was added systemd-resolved did not do what was desired. It was "possible" that it would resolve a query for a bosh dns address, but it was also just as likely to return an NXDOMAIN response.
The documentation for systemd-resolved mentions that it calls all servers in parallel looking for a response, and since NXDOMAIN is a valid response, if that comes back, that is the returned response.
My next attempt was to modify that congiuration file by specifying a route-only domains section in the configuration file marking the bosh-dns server as only valid for those particular domains, which systemd-resolved will then take queries that match the domains, and send them to this server.
This also does not work. It seems that systemd-resolved has a focus more on interfaces than on dns servers. Since I was adding the Domains section to a global DNS configuration, it is simply ignored. To use Domain specific DNS resolution, you must configure the network interface with the Domain, not the global configuration.
The <IP_ADDRESS>/32 address used by bosh-dns is not an interface, but a second IP on the loopback interface. It may be possible to add the Domains= section to the loopback device while associating the <IP_ADDRESS> DNS server with that interface and it will simply "work", but generally systemd-resolved does not treat the loopback device as a configured interface.
It seems like the dbus API is the most practical way to configure the loopback interface DNS, but I haven't been able to figure that out yet.

New findings.
I was wrong before about how it operates, and some of the docs seem to be wrong too.
systemd-resolved only has a single active DNS server at any one time for each interface and for the "global" state. It assumes additional servers on the same interface all behave the same, so it doesn't query them in parallel. The "current servers" for global state and each interface are all queried in parallel by systemd-resolved.
Current the bosh-agent configures a global server. For bosh-dns to work, we'd need it to be the only global server or the only server on a particular interface. Both resolvectl and the dbus API refuse to configure dns servers on the loopback interface.
So one possible scenario would be to have bosh-dns configure itself as the single global server and have the bosh-agent instead of using the global space, place the provided dns configuration directly on the other interfaces (normally just eth0 I'm guessing)

My testing was done with GCP where we surprisingly use DHCP for network configuration. This seems to be so the interface is able to discover the GCP provided DNS servers.
However, systemd-resolved doesn't seem to have any way to configure "additional" DNS servers for an interface. We could always have the agent wait for the networking to come online and then modify the DNS servers for the interface manually, but that seems like an awkward interaction.
Something I haven't yet tested is if the agent were to configure the interface directly, rather than using the config files, if that configuration will "stick" once DHCP updates the DNS servers for the interface.
If that doesn't work, ripping out systemd-resolved is looking like our best option.
Another option that would work is putting bosh-dns directly on the stemcell so the agent can always configure it as the single global resolver and the agent can then configure bosh-dns resolvers with the settings.json provided dns servers.
bosh-dns on the stemcell does seem very sane at this point, but also seems like a lot of work to get it there and also provide a way for the config to be updated later with additional configuration.

With some help from @cunnie , we managed to get it working.
Currently, bosh-dns creates an additional ip on the loopback device. We changed the behavior so under noble it instead creates a new virtual interface of type dummy and binds the <IP_ADDRESS> address to that interface instead of the loopback interface.
This allows us to then have systemd-resolved pick up the bosh-dns DNS server IP address from this interface and use it for resolving queries without worrying which DNS server is the "current" one.
We also did work to populate the "Domain" configuration. Since systemd-resolved queries DNS servers for all interfaces by default, and since bosh-dns always uses a TTL of 0, bosh-dns records never get cached by systemd-resolved. This means the external DNS servers would get copies of all the bosh-dns queries which could put them under unexpected additional load. By populating the "Domain" configuration for the virtual interface with both the bosh-dns domains as well as any alias domains found on the system, it allows systemd-resolved to only send those queries to bosh-dns and not to any of the external dns servers.

a pr is under review https://github.com/cloudfoundry/bosh-dns-release/pull/100

As we discussed yesterday in the WG Meeting we should start with a list of bosh-dns features that we lose with this new implementation. And also find workarounds/solutions to achieve the same with Noble. I start a list here, we will sync in the next days internally to maybe find more.. If you have any other features in mind, feel free to add them:

The first feature that came to our mind is the recursor logging we added beginning of this year:
https://github.com/cloudfoundry/bosh-dns-release/pull/96
as only bosh internal requests are sent to bosh-dns the logging will not work anymore.

@max-soe I think you forgot to add the link.
I can think of:

https://bosh.io/docs/dns/#caching
https://bosh.io/docs/dns/#monitoring
recursor configurations available in https://github.com/cloudfoundry/bosh-dns-release/blob/32371aa7d0f47670af145ca6bbab0786b96e1f61/jobs/bosh-dns/spec#L106-L115

systemd-resolved:

caches all requests by default

logging can be enabled with  resolvectl log-level debug as we already do some resolvctl in bosh-dns we should be able to transfer this cmd
a different option would be that bosh-dns would be to set resolved config

prometheus has the ability to pull up systemd-resolved https://github.com/prometheus-community/systemd_exporter/pull/119


Connot require itself

Hey, it's my first time with the composer.
I downloaded the ZIP and extracted it into my project. In the directory "dropbox-php-sdk-master" I run the composer, but it doesn't work :(
`sst@ronda:~/public_html/wukos_dbx/inc/dropbox-php-sdk-master$ composer require kunalvarma05/dropbox-php-sdk
Using version ^0.1.5 for kunalvarma05/dropbox-php-sdk
./composer.json has been updated
Root package 'kunalvarma05/dropbox-php-sdk' cannot require itself in its composer.json
Did you accidentally name your root package after an external package?`
Can anybody help me with this problem? Thanks!

@code-sallo No worries. Here's a neat guide to Get started with Composer.
Once you're thorough with how Composer works and why it is used (for dependency management), the following will be quite apparent:

Go inside your project's root (~/my-project)
Run composer init (https://getcomposer.org/doc/03-cli.md#init)
Then run composer require kunalvarma05/dropbox-php-sdk (https://getcomposer.org/doc/03-cli.md#require)
👆 This will install the kunalvarma05/dropbox-php-sdk package and all it's dependencies in the vendor/ directory inside your project's root.
Then, require the vendor/autoload.php file in your project's file and start working with the API. (https://github.com/kunalvarma05/dropbox-php-sdk/wiki/Configuration)

Cheers :)

just need change to another direction
i mean movedown to another one and try again


nan result from multivariate_normal.cdf

The cdf function of multivariate_normal may not have the correct results when the dimension is 2. I run the similar test in matlab and have a numerical result instead of nan.
Reproducing code example:
import numpy as np
from scipy.stats import multivariate_normal
x=np.random.randn(2)
mean=np.random.randn(2)
cov=np.abs(np.random.randn(2))
d=multivariate_normal.cdf(x, mean, cov)

Error message:
d=nan

Scipy/Numpy/Python version information:
('1.0.0.dev0+a8fe705', '1.13.1', sys.version_info(major=2, minor=7, micro=13, releaselevel='final', serial=0))

Something is definitely wrong.  pdf() method works, but cdf() returns nan:
In [19]: scipy.__version__
Out[19]: '1.0.0.dev0+2651b14'

In [20]: from scipy.stats import multivariate_normal

In [21]: multivariate_normal.pdf([[0.25, 1]], [0,0], np.eye(2))
Out[21]: 0.093562364371238188

In [22]: multivariate_normal.cdf([[0.25, 1]], [0,0], np.eye(2))
Out[22]: nan

It appears to work with higher dimensions:
In [36]: multivariate_normal.cdf([[0.1, 0.2, 0.3]], [0, 0, 0], np.eye(3))
Out[36]: 0.19322122066473132

I see that the CDF method was added in https://github.com/scipy/scipy/pull/7017.
@asnelt: Could you take a look at this issue?

Thanks for reporting this issue.
I looked into the problem and confirm that cdf() returns nan for bivariate input.
The problem appears to originate in the mvnun Fortran code by Alan Genz. The code uses a dedicated function to handle the bivariate case and causes problems when called with negative infinity as the lower bound. A quick and dirty fix would be to replace negative infinity with a number on line 451 in _multivariate.py:
Replace
lower = np.full(mean.shape, -np.inf)

with e.g.
lower = np.full(mean.shape, -1e100)

I am now working on a clean fix using mvn.mvndst instead on mvn.mvnun.


It cannot work in latest Xcode

hi @CaptainYukinoshitaHachiman,
Really strange, I just opened Example project in xCode 8.3.1 and it seems to work as expected.
Can you please double check that everything is installed correctly? Make sure that you set a Module in storyboard to be CHIPageControl if you are using cocoapods.

closing it because of no response. If the issue still exists, please re-open.

Thanks @chili-ios , setting Module to CHIPageControl for the element in Interface Builder fixed my runtime error.