Remove Span.get_trace_attribute

Remove Span.get_trace_attribute

simply initial api (just one way of doing things)
avoid Heisenberg tracing

References:

https://github.com/opentracing/opentracing-java/pull/7#discussion_r50498700
https://github.com/opentracing/opentracing.github.io/pull/47

For reference sake Heisenberg Tracing refers to:
When tracing goes from only instrumentation to having additional features (that the application becomes dependant on) then;
The act of observation/instrumentation itself changes what is observed.
Now there's no such thing as pure observation-only code. Even logging interferes (synchronous logging with disk IO and latency, asynchronous with memory). And there's an argument that because the DCP mechanism is happening behind the scenes that we're already on that slippery slope and might as well slide down it.
By removing span.get_trace_attribute we're letting Span remain more of a clean instrumentational API. The functionality is still there but moved into a more flexible, and more DCP, part of the API.
Against the current SpanPropagator API the functionality might get lost, but will definitely remain with https://github.com/opentracing/opentracing.github.io/pull/45 in place.

@michaelsembwever please see my second comment above, https://github.com/opentracing/opentracing.github.io/pull/47#discussion_r51580425. We cannot rely on the name in the kv-map encoding to retrieve the attribute by the name end-user knows.

@yurishkuro let's continue this once https://github.com/opentracing/opentracing.github.io/pull/45 is sorted. I believe this is ample ways of doing it, but it'll be more clear afterwards.
A quick example is one can use the vanilla map extractor
tracer.getSpanInjector(Map.class).inject(span, map)
map.get("auth-token")

But more to he point, I think we'll see clearer ways of doing even that once the Injector/Extractor discussion evolves.

agree, let's wait, but fwiw, with our tracer implementing OT the only way it would work is
tracer.getSpanInjector(Map.class).inject(span, map)
map.get("uberctx-auth-token")

because the tracer prepends uberctx- to all attribute names when exposing as a map, and the end user cannot rely on that.
Also, as a side note, the distributed context propagation was widely viewed as a positive feature by people at Zipkin workshop, I don't recall anyone objecting to it. In implementations like grpc, the context allows user code to read back the attributes.  So why, in OpenTracing, should we try so hard to hide it?
gRPC examples:

passing metadata: http://www.hward.com/golang-grpc-context-client-server/
passing trace ID as metadata: https://github.com/harlow/go-micro-services/commit/221a67bca4309aa12b69cd57ca6c1e9522c09cfc

I think span is the wrong place to add general purpose propagated attributes. I'll repeat a comment I've made many times, especially as DCP came up for the third time at our third workshop.
The workshop discussed a decoupled context (tag set), baggage, an independent api. It does not require routing through a tracer api to get to baggage. Ex. my scheduler, or metrics api does not need to hold a reference to the tracer api to get the same context. This is what is generally sought out (and in fact implemented in tons of frameworks!)
It is very important to understand a vote for distributed context propagation is not necessarily a vote for Span/Tracer.setAttribute(arbitrary baggage). The fact that DCP is stuffed inside the Tracer api is the polarizing topic, not the act of propagating tags. The day we finally decouple this, is the day we can stop losing time in cyclic discussion.

@adriancole I agree, I think it's conceptually much better -- however, in a practical sense I'm not sure exactly how to place DCP in context with OT interface.  I thought that perhaps OT could extend a DCP API with a TraceContext object, so I prototyped it over the weekend.
Unfortunately, my results ended up being less satisfactory than I hoped.  I discovered this in the process of converting all the use-cases.md examples (and also thinking about what examples are not covered there).
In the spirit of showing reasoning behind things as you mentioned on Monday--and also hoping for a better solution from someone else--here's the PR in case anyone is interested: https://github.com/dkuebric/opentracing.github.io/pull/1

@adriancole I hear you (in fact, I will point out that my initial forays here separated the DCP stuff as part of TraceContext)... the question in my mind is how to "make the simple things simple" while still supporting the cleanest DCP-friendly API we can muster. I guess I would encourage anyone and everyone to try and solve this via a diff to the core use-cases (like @dkuebric did). In my experience it was (too) challenging to both cleanly separate DCP and keep vanilla span creation and propagation "concept-lean".

PS: this is an excellent thing to discuss at our inaugural hangout in a few hours!

Would love to join, but my flight plans seem to be clash quite consistency
with these catchups :( just wanted to send some thoughts before I became
AWOL in transit.. And on that note boarding

@adriancole safe flight!  Here's the notes from @bensigelman on the hangout: https://github.com/opentracing/opentracing.github.io/issues/44#issuecomment-179654948
For the relevant part, discussion on Attributes: they are important enough that OT wants them, but context isolation not important enough for OT to make extra work for instrumentation that would be required by a clean separation of context and span.
(I would have been happy for a clean API that both separates the two and also does not require extra work in propagating multiple objects.  Unfortunately I was not able to produce one and in the process of trying to do so convinced myself it is quite a challenge.)
It will still be quite easy to implement a context-only tracer, which uses the same instrumentation (for context propagation purposes only) and no-ops Spans.  The semantic issue faced is that Span will be the interface to the Attribute data, which isn't a very obvious API as you point out above.

I think we have reached the agreement on the video call to keep read/write methods for trace attributes.
Suggest to close this in 48hrs.

Sorry to bring this up late but…
Why not have just the get_tag method instead of the get_trace_attribute method?
Since the get_tag is going to return trace attributes (if trace attributes are implemented).

I am not sure what you mean, tags and attributes are different sets of data. We do not expose read function for tags in the API, they are write-only, reported to storage out of band, and tracers are not required to guarantee that all tags will even be preserved.

I am not sure what you mean, tags and attributes are different sets of data. We do not expose read function for tags in the API, they are write-only, reported to storage out of band, and tracers are not required to guarantee that all tags will even be preserved.

That is, has the decision been made that the two sets are kept separate.
Or… could a get_tag call return a trace attribute?
That is can trace attributes be exposed via tags. This would make sense because these are the things are reported to storage. But it wouldn't make sense because of the different value types permitted.
My questioning was as much to ask for the reference to the discussion/rationale to any decision made on this front. " We do not …" doesn't cut it.

I don't have specific pointers to discussions, as this topic was touched upon in various other related discussions. I can try to summarize:

Currently, a Span has setTag and setTraceAttribute methods. They are separate because the semantics of tags an attributes are very different, as documented in the docs site.
So far nobody has requested read access to the tags. In fact, no other piece of data on the Span has read API aside from trace attributes. I've seen implementations of several different tracers, none of them expose span data back to the application.
Trace attributes have read/write API by design, because that is their raison d'être, to allow services to propagate metadata to downstream calls.

I can try to summarize
thanks.

@yurishkuro @michaelsembwever
+1 on Yuri's summary. I will concede that "trace attributes" never really rolled of the tongue (and still doesn't). I had a nice VC with Rodrigo Fonseca and Jonathan Mace (author of the excellent PivotTracing paper among other things) and I started to like the term "baggage" since real-life baggage is something you "carry with you", much as these key:value pairs are carried with the trace. So I am open to something like SetBaggage/GetBaggage; it's a non-standard name, but it's also a non-standard idea and would maybe help to get users to actual RTFComments (a particularly good thing in this case).
I would like to keep them totally disjoint from "span tags", though, especially since they are "beta" compared with the rest of the OT API.

I am not opposed to "baggage".

I like "baggage" as well.  "Trace attribute" is probably one of the more confusing terminology issues right now.  This would make it better differentiated from tags.


Windows executable

Having a single file executable or installer early in development would make life easier for potential testers of the application.
pyinstaller and pyupdater are probably the standard tools for this at the moment, worth checking though.

PyInstaller has a known bug that's preventing it building our demo QML app, so I'm looking into alternatives at the moment.

If there is no obvious alternative then waiting for the PR to be merged to fix that bug is also an option.

There are a few other options to at least try out.

Adding that branch git+https://github.com/tobinjones/pyinstaller.git to requirements does seem to fix the initial bug. It does however reveal another pysinstaller-pyside2-QML specific bug, which I think is the one that was guessed to exist here based on a similar bug for pyinstaller-PyQt5-QML.
However, cx_freeze is looking very promising, already have a slightly modified version of the program running in it.


feat: refactor the mongo model & schema files & loading

Moved mongo schema & models together into files so it's also easier to customize models when needed
removed the magical auto loading based on file names
export both schema & model from the file just in case both are needed
require all the models in the mongo plugin to load them
( this changes slightly implementation with global mongoose models instead of on the specific mongo connection ... but for now this doesn't make a difference since we only have one connection).

Yeah @anniegiang I saw that, @Naraujo13 also mentioned it, to me it's the same whether we only export the model  for example User and then we can still use User.schema
Only annoyance is that we are still using the old ES5 / Common.js syntax which is module.exports and that one doesn't really support both default + named exports from same file in a nice way. So I changed it to 2 named exports... but I will check maybe it's better to use only export like
``` module.exports = model("User", UserSchema);and then useUser.schema`

I've updated this to use default exports and use Model.schema if we need it so should be good and usable for @Naraujo13 in #284


cargo test: allow to specify tests by filename and line

If it was possible to specify tests to run by filename and line of the test function, then editors would not need to work hard in order to invoke specific tests from within the editor. Currently reliance on heuristics or RLS features is needed for this.

I think this might need to be opened against the rust-lang/rust repo, seeing as cargo just delegates to its libtest behaviour for test section (such as https://github.com/rust-lang/rust/issues/30422).


Witsy + multi-llm-ts in README

Thanks for the great Ollama!

Cool projects! Thanks for creating them.


Action to modify services

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[ ] I've updated the documentation if necessary.

Motivation and Context
This is against the issue raised here
Description
This will add the action to modify the services.

This is great, that's a missing piece to use this produce feature from within fastlane 👍 I added a few comments before it's ready to be merged

Incorporated the feedback

Awesome, thanks for your contribution 👍

It doesn't require immediate release. It can go in next release.

Already live 🚀 Thanks again


1502683-Cleanup unused attributes in service views

Attributes removed have been identified to be unused by the the views in which the services are utilized.
Doing what we can to reduce load times!
Not yet ready for prime time ;-)
TODO

[x] assess candidates for removal on service details page
[x] double check the ones for service explorer...

@chriskacerguis @chalettu  would appreciate your 👀 on this... 🌮 💃

@AllenBW please don't forget to put the BZ link in the description so the bot can find it
https://bugzilla.redhat.com/show_bug.cgi?id=1502683


Polymer 3 Conversion

If you can't figure out how to make the test work or what's going wrong, I'm personally fine with removing them -- but I'd remove the test in the pre-migration code so that the migration can be re-run cleanly.


Update r/t clinical lessons learned from the pilot: Provide care recommendation for an ECC <= CIN3 that occurs outside of an excision or colpo

If an ECC procedure is performed alone (i.e., not during a colpo or excision) and the result is <=CIN3, there is not enough evidence to tell the clinician what to do. Dr. Updike said to use clinical judgement.
IF histology test FOUND on the same dateTime as an ECC procedure
AND the result = "<CIN1" or "Histologic LSIL (CIN1)" or "Histologic HSIL (CIN2)" or "Histologic HSIL, unspecified" or "Histologic HSIL (CIN3)" AND NOT coloposcopy procedure or 'treatment' on the same dateTime as the ECC procedure
THEN DISPLAY "Use clinical judgement to manage care based on a biopsy result obtained during an ECC procedure."

NO!! This is old and is no longer relevant!
This is no longer relevant.
This is the updated logic. Note: We still need to clarify with the doctors what the care recommendation is in this scenario.
IF histology test FOUND on the same dateTime as an ECC procedure
AND the result = "<CIN1" or "Histologic LSIL (CIN1)"
AND NOT colposcopy procedure or 'treatment' on the same dateTime as the ECC procedure
THEN DISPLAY xxx

This has been updated even further since. We have decided that ECCs are mapped to cervical biopsies the same way as colposcopies are. Therefore, this issue is already resolved.


Always run config resolver

After upgrading Knip to latest version 5.41.1 from 5.38.2 in an Angular project found out that a file that was previously correctly tracked as production entry was suddenly appearing as unused file (specifically, src/main.ts) when using knip in production mode. I've been working with the Angular plugin recently, so first thought was I may have messed up something. That file is added as production entry because appears in browser option of the build target in angular.json.
However, that piece of code hasn't changed and the file should be added as production entry. After manually bisecting which version introduced the bug, seems it appears in 5.39.2. In there, there's a plugin housekeeping commit that removes the empty production array from the plugin. However, due to a check when running plugins, the resolveConfig function won't be executed when running in production mode if no production key is present in the plugin. Hence when removing that empty production array from the Angular plugin, the resolveConfig function wasn't ran and the production entry src/main.ts wasn't added.
Given the issue, I could have brought back the production empty array to the Angular plugin. However, I think that it's better to always run the resolveConfig function if is defined. Both in production and non-production modes. Because several plugins actually use the toProductionEntry function as part of resolveConfig. So this issue could happen in the case that production key is removed and all production entries are added as part of resolveConfig. Let me know if there's something else I may be missing though!

Thanks! Appreciate the thoroughness. Not even sure why I didn't do it yet, but it's good to enforce more correctness/strictness in resolveConfig implementations in production mode.


Camera parameter "vrmode" for camera2

Hello,
I want to use camera2 api on my app.
parms.set("vrmode", 1); // vr mode
Can I use above parameter for camera2?
I checked camera2 api for this and It has different parameter settings compare with camera api.
If it can be used, Please tell me how I can use it.
Thank you!

I don't think there is a way to access the 60FPS "vrmode" camera modes via the camera2 API. It's something I'm interested to know too.


Contact us form

Acceptance criteria

[x] I can see the contact form on the contact us page as similar to the design.
[x] When i submit the form, the admin can receive the summited form information in the email inbox.

Tasks

[x]  Do Analysis submit form can be sent an email to the admin.  (Maybe require to add/wirte plugins)
[x] Check if the already plugin exists for that.

[ ] If not,  how to capture submit form payload on wordpress and send email using email hook function on WordPress.

// @nikeshbalami

@arjun-gautam  you can take a ref. example from branch contact-form` for sending contact payload to email.  I've already sent you an email/password detail for testing on chat.

Not tested yet but we can test later along with final feedback/touch.
Closing as DONE.


Fix diff and localeData definitions

Add definitions (source) and tests (own) for moment.localeData()
Fix definition for moment().diff() to allow other input types besides Moment (own).
Add intermediate type MomentComparable for re-use (source).

Note: I haven't looked into all the differences between this definition file and the one on DefinitelyTypes. It would be great to have them converged.

Close in favor of #3490
@Manduro feel free to review and comment there.


Gtag

Ticket: https://mailtime.atlassian.net/browse/MISC-10
Implement Google Ad Event functions on the Asian Food Delivery Report page

"Data Insight" Button
"Submit" Button in the request form
"Request A Demo" Button

@chochihim


Apply correct styling to 500 error page.

Changes in this PR
Awaiting final content before merging: https://trello.com/c/ctTDNRv5
Screenshots of UI changes
Before

After

Release checklist
Release process documentation.
Pre-merge checklist

[ ] Are any changes required to dependent services for this change to work?
(eg. CAS API)
[ ] Have they been released to production already?

Post-merge checklist

[ ] Manually approve
release to test
[ ] Manually approve
release to preprod
[ ] Manually approve
release to prod

 Style our 500 error page


Update FormalityToJS.js

Add F64.parse and F64.cmp to prim_funcs

Can you update with the new stuff?

F64.cmp is semantically wrong. The cmp functions usually returns a Cmp, not a Bool. Rename it to F64.eql like the other equal functions.


Fix for #412

Use the newer calculation for the i2c

@ivmarkov I would need some advice, log2 is not available in std but would be required for the calculation, I could do this with ilog2, but then I have no idea how to ensure the ceiling() is done correctly. Any advice?

@ivmarkov I would need some advice, log2 is not available in std but would be required for the calculation, I could do this with ilog2, but then I have no idea how to ensure the ceiling() is done correctly. Any advice?

... assuming you do the math with u64, the following might work:
abc.log2() + (if abc.leading_zeroes() + abc.trailing_zeroes() + 1 < 64 { 1 } else { 0 })
NOTE 1: Ideally, you should avoid floating point math anyway, on MCUs and esps specifically.
NOTE 2: I have not checked yet your computation and why you need to take the logarithm of something

Ok this seems to work, 104ms returns 22 for the register while 105 rounds up to 23 and is properly failing

Thanks!


Adding failing test to highlight meta information getting dropped from json requests

refers to https://github.com/danielspaniel/ember-data-factory-guy/issues/267
I also am experiencing this issue - here is a failing test to demonstrate (the same test as the one I found the issue from). If you put in a debugger in response returned in the users route from the query you will see the meta keyword is undefined.

Nice one, thanks for sending the test for me to fiddle with .. will whip up a solution for you for the weekend.

thanks @danielspaniel :)

You made a mistake @jeobrien in your test. ( the template was not correctly done )
the template should have read
 {{#if nextPage}}
   Next Page
 {{/if}}
 {{#if previousPage}}
   Previous Page
 {{/if}}

( do you see the mistake you made? )
so actually the test works fine. And makes me see that the adding meta works perfectly ( as advertised ) .. therefore .. thanks for the extra test .. and I am going to close this PR and the issue until someone can find actual fail and I will reopen
But thank you very much for trying to highlight and explore the issue. This is a very fun feature and not one I want to see broken.

also .. another tip .. you could have written the route like this
  model: function() {
    return this.store.query('user', { page: 1 })
  },

  setupController(controller, users) {
    controller.set('previousPage', users.meta.previous);
    controller.set('nextPage', users.meta.next);
  }

And .. just for fun ( because I liked your test ) I moved your code to  test in users-search-test because mockQuery was used there .. so thanks again

@danielspaniel Woops my mistake! Thanks for fixing that up, glad it was someone helpful at least :)


Add LICENSE file

Motivation
Since optuna-examples is a split from Optuna, we need to put the same license file as the original.
Description of the changes

Add LICENSE file

@Alnusjaponica Could you review this PR, please? As mentioned by the author, this repository should follow the MIT license like optuna/optuna.
c.f., https://github.com/optuna/optuna/blob/b9a2fec629e27a6f97c74879f430265c83ec27b2/LICENSE#L1-L21

@toshihikoyanase Could you merge this PR?

Thank you for your prompt action. I'll merge this PR.


Cannot access my plugin

Hi! i have created a plugin through "yo kiabana-plugin" command , but when i try to access it in UI it gives me a fatal error, couldnot figure out the issue.

This is with no modifications to the generator? What options did you pick?

i have just given name, description and version as 6.0.0, also i have tried by choosing lower versions and master but that gives the same fatal error

So, just so I'm clear, you answered no when asked to generate an example app, translations, hack, and API?

i just followed this link: https://github.com/elastic/generator-kibana-plugin#getting-started
I got created the plugin with the name sraha...but when i click on the plugin i got fatal error which i mentioned before

Oh, sorry, I thought the generator asked you questions about what to install. I was wrong. Just tried it locally and I get the same problem. I'll look into it. Sorry about all the questions.

Published v7.0.0, which fixes this issue.

can you please elaborate the details.....you mean i need to change the version of elastic search from v6.0.0 to 7?

No, sorry. I pushed a version 7 of this generator, which works correctly now.
If you rather not re-generate your project, you can fix your existing code by making the same change I made in this commit. uiModules needs to be destructured out of the import by name.


fix(editor): correct nested br tags in article content

Shall we add test cases for correctSelfClosingHtmlTag and correctNestedBrTag?

Must have. I've added. 🙌


Notificatio popups block sidebar when sidebar is moved to right

Issue Type: Feature Request
Currently when the Sidebar is moved to the right hand side of the screen, all the notification that pop up block the content of the side panel, could the notifications be flipped or moved elsewhere on the screen when right aligned sidebar is selected so it does not block the sidepanel content?
VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:07.755Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

duplicate https://github.com/microsoft/vscode/issues/103829


What font are you using?

Hey, just wondering what the font used in the image below is called.

cool ty

It's the same as the one he used in his Abacaba Graphing Tutorial, so according to this it's Jygquif-48. However, I haven't found that name anywhere. Good luck, that was all the info I could give you :P

My brother created a variation of the font "Interstate", which is used on US Highway signs, and called it "Jygquif" in 2015. I think if you just google "Interstate", it should show up!


error: Failed to parse torrent file: bencoded item count limit exceeded

Loading certain sufficiently large torrent files (35MB in this case) results in seemingly nothing happening, no dialog or error pops up in PicoTorrent, but looking at the log file the following error is logged:
2021-09-15 01:07:03.579419 [00:03:29.717625] [0x000001a8] error: Failed to parse torrent file: bencoded item count limit exceeded

Making errors loading torrent files pop up an error message rather than silently hiding the error in the UI would be a better user experience.
As for the actual error, it looks like this comes from libtorrent - https://github.com/qbittorrent/qBittorrent/issues/8449 describes the same issue as well as the workaround used in qBittorrent that might be a useful reference.

Thanks for the report! We should definitely handle this better.


Update Req to latest version

:tada: This PR is included in version 0.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


refactor: lowercasing tech stack name

Related Issue

Closes: #1913
Description
Refactoring all the teck-stack name to lowercase

There are some issues still. Let me fix them.


Created functionality to direct upload video to vimeo

Fixes #64
Fixes #185
Demo: https://paulsojan.neetorecord.com/watch/c88f749d-b412-487c-8ef1-f29f9df8a523

@deepakkumarnd Please review

@deepakkumarnd Made changes. Please review


Compress COVIDcast API responses

Especially since county-level responses are super large.

this is very important in my opinion since it significantly down the COVIDast map.
see also e.g<EMAIL_ADDRESS>https://httpd.apache.org/docs/2.4/mod/mod_brotli.html
in this case https://github.com/cmu-delphi/delphi-epidata/blob/main/src/server/.htaccess would be a start to configure that

Surprise! delphi.cmu.edu seems to be served by nginx 1.16.1, not Apache, but the map API endpoints are on Apache. I submitted #171 to fix the htaccess for those.
In the nginx config on delphi.cmu.edu we just need to add
gzip on;
gzip_types application/json;

to the appropriate server block. Pinging @korlaxxalrok. I think this will speed up queries to signals like DV, which can be 200+ kB per day of data. According to a random online checker tool I found, one example day can be compressed to only 14 kB. (Seems implausible, but if random website tools can't be trusted, who can?)

Fixed in #191.


realsense2_camera: 2.2.20-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository realsense2_camera to 2.2.20-1:

upstream repository: https://github.com/IntelRealSense/realsense-ros.git
release repository: https://github.com/IntelRealSense/realsense-ros-release.git
distro file: noetic/distribution.yaml
bloom version: 0.10.0
previous version for package: null

realsense2_camera
* Add Support - Noetic
* Add demo for using intrinsics from camera_info (show_center_depth.py).
* Add launch option: send logs to ros log file.
* Add feature: get rgb stream from infrared sensor (applies to D415)
* Add feature: Add notification if connected using USB2.1 port.
* Fix bug: Avoid z16h format
* Fix bug: monitor streams frequency without subsribing.
* Fix bug: extrinsincs for right stereo camera refers to the left stereo camera.
* Contributors: Abhijit Majumdar, Isaac I. Y. Saito, Jakub, M-frctrl, Thomas Jespersen, doronhi

realsense2_description
* Add urdf file for l515
* Contributors: doronhi

holding for the upcoming Noetic sync


[feature request] Loading bar for citations

Steps

Enable Zotero for a project
Configure Zotero for the project and be sure to link to a folder that has many citations (200+)
Go to the overview page to view Zotero citations

Expected
I expect that the citations would load after a few seconds, and if not, that there would be some sort of indication that they are loading.
Actual
The widget is blank until 200 citations load. For my folder with 688 citations (and probably more since Zotero also displays attachments as separate citations), it took ~ 20 seconds to load anything in the widget (would be longer except that only 200 citations load). Initially, I thought that it just wasn't working. It was only when I pulled up the dev console that I saw the GET request was still pending.
Suggestions
I would suggest adding some sort of indication or message that citations are loading, because otherwise, users may not stay on the page for long enough to see that the citations do eventually load.
Apparently @harrismendell implemented a loading bar but it is not showing up. May have to do with the fact that @lyndsysimon may not have merged the changes.

@samchrisinger worked to improve that prior to deployment, and I think there are some follow-on considerations on how to improve it.

Any indication @caileyfitz @samchrisinger that this remains an issue?

@lbanner Yes, I am still having this problem. Just tried again and it took 19.79 seconds for anything to show up in the widget.

OK


Code generation issue when export a class that implements a interface

export = class B implements A {
    prop: number;
    onStart(): void {
    }
    func = () => {
    }
};

The code above will generate to
module.exports = (function () {
    function B() {
        _this = _super.apply(this, arguments) || this;
        this.func = function () {
        };
    }
    B.prototype.onStart = function () {
    };
    return B;
}());

The constructor refers to an undefined _super variable.
If I change the code to
class B implements A {
    prop: number;
    onStart(): void {
    }
    func = () => {
    }
};

export = B;

The result is correct.
If I remove implements or write an empty constructor, the result is also correct.
I think this should be a bug.

Dup of #11644?

@falsandtru indeed


Revert "[SILOptimizer] Generalize optimization of static keypaths"

Reverts apple/swift#28799. It still causes a failure in test/stdlib/KeyPath.swift on i386:
[ RUN      ] key paths.optional force-unwrapping
stderr>>> Assertion failed: (getStrongExtraRefCount() + 1 >= dec && "releasing reference whose refcount is already zero"), function decrementStrongExtraRefCount, file /Users/buildslave/jenkins/workspace/fs-swift-unreleased-master-tools_RA-stdlib_RA/swift/include/swift/Runtime/../../../stdlib/public/SwiftShims/RefCount.h, line 576.
stderr>>> CRASHED: SIGABRT
the test crashed unexpectedly

@swift-ci Please smoke test

@swift-ci Please smoke test Linux


Web analytics and diagnostics

[ ] Integration with web analytics systems (ex Azure Application Insights, Google Analytics)

Does Serilog "just work" for something like this?
https://github.com/serilog/serilog/wiki/Provided-Sinks

In general, .NET Standard 2.0 libraries should work from a Blazor app. Which sinks are most interesting to you?

Azure Application Insights and Seq, https://getseq.net, are the two I use most often.

I playing with setting up Application Insights inside Blazor. That seems trivial task if I just copy paste JS initialization code inside index.hml. Then I could interop using JS api At the same time this does not allow me to set Instrumentation Key. Same question if I attempt to run AI inside Blazor's .NET code. I need somehow pass Instrumentation Key for configuration purposes. Any ideas how this could be done right now ?

At the same time this does not allow me to set Instrumentation Key.

Why not? Isn't the instrumentation key typically embedded in the JS code? https://docs.microsoft.com/en-us/azure/application-insights/app-insights-javascript#add-the-sdk-script-to-your-app-or-web-pages

I have project which will use different AI accounts for staging and for production. (Assuming that Blazor will take off). Also I use same AI key for API and for Blazor application, which require me to sync them, or worse - ask customer to manually replace AI key in two places.
In the ASP.NET Core (and regular ASP.NET and just AI SDK) I without problem could change AI key using appsettings.json. Would be good to have this in the Blazor as well.
Since Blazor use index.html for serving application, and at the same time there no way to pass command line parameters when I embed Blazor in ASP.NET Core website (no parameters here app.UseBlazor<BlazorApp1.Program>();). It may be not about AI itself, but rather ability to pass configuration from the application hosting Blazor.


Enable appveyor for windows builds

Coverage remained the same at 85.723% when pulling aba2670954df91e98cf8bd4394158116c5d07884 on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Coverage remained the same at 85.723% when pulling aba2670954df91e98cf8bd4394158116c5d07884 on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Coverage decreased (-0.0008%) to 85.722% when pulling b88b5b8d23304869647c7dbc2535fb3d369c8b73 on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Coverage increased (+0.003%) to 85.726% when pulling 9513bf9c547a0b4281ca5345bddbfc3ecf2edfe9 on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Coverage decreased (-0.002%) to 85.72% when pulling fd0e30da5d69f15e176395fc3d9aa30c4a3f03be on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Coverage decreased (-0.002%) to 85.72% when pulling f37c9711f63b91ae0d5b74097b56017df52ee7ab on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Coverage decreased (-0.002%) to 85.72% when pulling 5848d64f9f40c0d45368fd4ec4c2f16b0f686d9d on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Coverage decreased (-0.002%) to 85.72% when pulling 6bf74056aef058eaa4250c0f5848a0ab6d7355e4 on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Coverage increased (+0.003%) to 85.726% when pulling 97acd347e85dd567ae92da8f81d4a47996091b27 on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Coverage decreased (-0.002%) to 85.72% when pulling 97acd347e85dd567ae92da8f81d4a47996091b27 on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Coverage decreased (-0.002%) to 85.72% when pulling aee9a39b80da362625630bb974230504da9c53e8 on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Coverage decreased (-0.002%) to 85.72% when pulling aee9a39b80da362625630bb974230504da9c53e8 on mziccard:enable-appveyor into 14c77119b48b0ebf39f926edf09dfde94555a56d on GoogleCloudPlatform:master.

Putting this on hold until appveyor is enabled by the organization account.

Changes Unknown when pulling 04bf4341d18558bc7fa8776e651780a54f0d6779 on mziccard:enable-appveyor into ** on GoogleCloudPlatform:master**.

/cc @lesv

LGTM - looks like this helps immediately.


build failed

C:\Users\lalli\MyApp\Program.cs(2,1): error CS8802: Only one compilation
unit can have top-level statements. [C:\Users\lalli\MyApp\MyApp.csproj]
The build failed. Fix the build errors and run again.

Hello @lallikrishna, could you please check that you don't have another files in your project with top-level statements? You may find more examples here https://learn.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-9#top-level-statements

Sometimes I've seen this happened when the dotnet new command is run twice, once at the user's folder (at C:\users\lalli) and then another time after the user has done cd MyApp. You could delete the MyApp folder and start over.

Hello @lallikrishna, could you please check that you don't have another files in your project with top-level statements? You may find more examples here https://learn.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-9#top-level-statements

Thanks for thesolution &  suggestion.....


Update Docs

Hey 👋🏻 I noticed that you renamed the project and created a documentation site. I wanted to say that I think this is a great improvement and a big step forward. I also noticed that it looks like there is further support for non-jotai and non-react frameworks. I've been playing with jotai-molecules (now bunshi!!) at work and I wanted to try to share some of my experience in the form of updating documentation.
Anyways, I'm opening this docs ticket to try to track some of the in-flight PRs I intend to open to improve documentation and add examples:

[ ] Provide further example code for scoping more complex interactions
[ ] Opinionated guidance for structuring and organizing molecules
[ ] Scope as a mechanism to initialize atoms from react-tree state
[ ] Scope as a mechanism for parameterizing atoms (for example: jotai-tanstack-query)
[ ] More nanostores examples
[ ] More zustand examples
[ ] Look into the overall structure of docs.

If anyone thinks of anything they'd like to see improved, I can help with adding it to this meta-issue and try to break out more meaningful and specific examples for some of the broader goals here. Expect some PRs in the future tied to this.
And thanks again!

Thanks for the feedback @DavidJFelix -- I agree that more examples and documentation is definitely due. The API is intentionally small, and the possibilities are all in the different use cases and examples.
Very open to more documentation, please don't hesitate to contribute.
One thing I'd like to see is an easy way to write documentation that is also runnable, similar to what Jotai docs do with CodeSandbox examples, but ideally without losing a centralized repository of code to prevent examples becoming out of date.

I wonder if something like https://github.com/kevin940726/remark-codesandbox could keep sandboxes up to date with docs

Here's an example I've been working on from the original jotai example that I think helps showcase counter scoping better than the original:
import React, { useId } from "react";
import { atom, useAtom } from "jotai";
import {
  molecule,
  useMolecule,
  createScope,
  ScopeProvider
} from "jotai-molecules";

const counterOwnerScope = createScope("");
const counterParamsScope = createScope({ initialCount: 0 });

const counterParamsMolecule = molecule((_getMolecule, getScope) => {
  const params = getScope(counterParamsScope);
  return params;
});

const ownedCounterMolecule = molecule((getMolecule, getScope) => {
  getScope(counterOwnerScope);
  const { initialCount } = getMolecule(counterParamsMolecule);
  return atom(initialCount);
});

const useOwnedCounter = () => {
  const countAtom = useMolecule(ownedCounterMolecule);
  const [count, setCount] = useAtom(countAtom);

  return [count, setCount] as const;
};

const Counter = () => {
  const [count, setCount] = useOwnedCounter();
  return (

      {count} <button onClick={() => setCount((c) => c + 1)}>+1</button>

  );
};

const CounterOwnerScope = ({
  value,
  children
}: {
  value: string;
  children: React.ReactNode;
}) => (
  <ScopeProvider scope={counterOwnerScope} value={value}>
    {children}
  </ScopeProvider>
);

const App = () => {
  const id0 = useId();
  const id1 = useId();
  return (

      <CounterOwnerScope value={id0}>

Outer id0

        <Counter />
        <CounterOwnerScope value={id1}>

id 1

          <Counter />
        </CounterOwnerScope>
        <ScopeProvider scope={counterOwnerScope} value={id0}>

Inner id 0

          <ScopeProvider scope={counterParamsScope} value={{ initialCount: 1 }}>
            <Counter />
          </ScopeProvider>
          <Counter />
        </ScopeProvider>
      </CounterOwnerScope>

  );
};

export default App;

Thanks for the PRs @DavidJFelix, I'll get to reviewing and approve them next week when I'm back from vacation.

I wonder if something like https://github.com/kevin940726/remark-codesandbox could keep sandboxes up to date with docs

Looks like Sandpack is the best tool for the integrated docs. Requires some tinkering to get it working perfectly, but it's looking promising. See the WIP branch https://github.com/saasquatch/bunshi/tree/sandpack

Thanks for the PRs @DavidJFelix, I'll get to reviewing and approve them next week when I'm back from vacation.

No worries -- I'm slowly working thru meta-issue this but paused after these because my commits will stack and I didn't want to create more trouble by staging stacking, so I'll rebase on any changes later. Enjoy vaca


UI performance improvements

Fixes https://github.com/hasadna/anyway/issues/878

Updated the oms library. See here for details: https://github.com/jawj/OverlappingMarkerSpiderfier
Updated the spinner library. See here for performance improvements: https://github.com/fgnass/spin.js/releases
Added code to remove markers that are not in view from the map.

I got to these problems after using Chrome Developers Tools to debug the site's performance and memory, and noticed there are many unnecessary layout updates & renders (even just commenting out the spinner improved performance).

More information here:
https://developers.google.com/web/tools/chrome-devtools/rendering-tools/
https://gist.github.com/paulirish/5d52fb081b3570c81e3a

Added another commit to only show the spinner when actually loading the list instead on each ajax request.
I used this http://backbonejs.org/#Events-catalog as a reference for the Backbone collection events


Filter on Length

Could you add a length option to the filter Wrangle?
It would be useful to be able to filter out strings based on their length. Ie selecting only brands which are 4 characters or greater in length.

Closing this. Able to be done with:
wrangles:
  - sql:
      command: |
         SELECT *
         FROM df
         WHERE length( {column} ) > {value}

I would like to figure out a nice generic approach to be able to execute simple code and conditions like this, rather than having to add lots of paramters to the filter wrangle.


Outflow or Inflow values are removed when using Enter on the keyboard

When creating a transaction, the numbers entered on either the Outflow or Inflow columns are removed when pressing Enter on the keyboard. It saves the values just fine when clicking Save with a mouse.

I'm having the same issue. Started after a YNAB update earlier this week.

I'm having the same issue. This happened awhile back, but they finally fixed it after a few revisions. Now it's back.

This appears to be due to the "Save Transaction on Enter" Feature. If I toggle that feature off temporarily, I am able to enter transaction amounts. I will work on fixing this issue to be included in the next release.
If toggling that feature off doesn't temporarily resolve the issue, please provide a copy of your current toolkit settings to help narrow this down.

To be clear, only the ability to enter the transaction when hitting enter is broken. Without turning off "Save transaction on enter" you can still hit the save button and it works, which you'd have to do by turning the function off anyway. That has been my experience anyway.

Here's a workaround that lets you keep your hands on the keyboard.
If you enter a value in the outflow field, you can tab the inflow field (or save button) and press enter. If you enter a value in the inflow field, you can shift-tab back to the outflow field (or tab to the save button) and press enter.
Toolkit for YNAB v Version 3.6.1

Locking to contributors. This isn't a forum for comments about YNAB Support or development.


TV App: Add validation logic for supported clusters and response commands

Added validation logic when TV app loads supported clusters json file and when TV app responds to matter commands
Problem
In case static_matter_clusters file has a different types instead of the one from the example, TV app will crash.
In case command response holder returns non JSON values TV app will crash
Change overview

Updated ResourceUtils.java to catch unexpected types of value
Updated ContentCommandAppDelegate to respond to first validate JSON before parsing it.

Tests - Android - App Install & Get Catalog List

Build the Android TV app using command:
scripts/examples/gn_build_example.sh examples/tv-app/linux out/debug/

Build the TV casting app using command:
scripts/examples/gn_build_example.sh examples/tv-casting-app/linux out/debug/

Start TV Android App

Start TV Casting App
out/debug/chip-tv-casting-app

Update content app to return invalid values for static matter clusters or for command response

Send Media Playback command
cast cluster mediaplayback play 0 5

Fast tracking example apps


Fix benchmark code that used old direct_io=True param

Contributor Checklist:

[ ] I have added or updated my entry in the creators.json file
[ ] I have added a changelog entry for my contribution
[ ] I have added/updated documentation for all user-facing changes
[ ] I have added/updated test cases
[ ] I have included the rebuilt production build of the client (only if changes were made to the GUI)

Reviewer Checklist:

[ ] /azp run libertem.libertem-data passed

/azp run libertem.libertem-data


Enroll Students in Piazza

If students try to enroll themselves on the Piazza site, it requires a .edu email address. To get around this, we need to copy in the student's email address to Piazza ourselves.
I'd be happy to do this if someone wants to send me the list of student email addresses.

Done!


Check if DartPad works with Firefox on Ubuntu

Page URL: https://dart.dev/codelabs/async-await/
Page source: https://github.com/dart-lang/site-www/tree/master/src/codelabs/async-await/index.md
User feedback from the Future codelab
"The Colab code was not existing. Idk if this was on purpose, but every example code was not there. Browser: Firefox on Ubuntu."
cc: @legalcodes

Do we have any way of getting more information from this user, or was it just an anonymous survey response?

It's from the anonymous survey response so unfortunately I don't have more information from this user.

Got it. I asked a GDE with Ubuntu/Firefox to verify the bug, and he wasn't able to:
https://twitter.com/abraham/status/1164286110333358083
Without more info, I'm inclined to chalk this one up as a one-off. If it pops up again, we can always reopen the issue.

Sounds good to me. Thanks!


cmake error The source directory is a  file, not a directory.

I apologize if this is the wrong place to ask this.
I successfully (I think) ran build_v140_x64.cmd and the necessary directories/files are generated.
I am trying to run cmake as stated in the readme, but it is failing.
I am pretty new to this, so I might be doing something wrong, but could you please help? Thanks!
C:\Projects\caffe\build>cmake -G Ninja -C C:\Projects\caffe-builder\build\libraries\caffe-builder-config.cmake
loading initial cache file C:\Projects\caffe-builder\build\libraries\caffe-builder-config.cmake
CMake Error: The source directory "C:/Projects/caffe-builder/build/libraries/caffe-builder-config.cmake" is a
file, not a directory.
Specify --help for usage, or press the help button on the CMake GUI.

There is a typo in the README you need to add your source directory at the end like so:
C:\Projects\caffe\build>cmake -G Ninja -C C:\Projects\caffe-builder\build\libraries\caffe-builder-config.cmake c:\path\to\src

Thank you for such a fast reply.  Sorry, but what should be the source directory?

@haeseonii     it should be the the source directory of Caffe you wanna compile.

Looking forward to having this added to the read.me
Another thing which would be super useful to add to the end is a minimum viable project which allows the user to test that their installation and compilation has succeeded, maybe in python.

@Adesun Hi, do you mean the root of caffe or the caffe_root/src/caffe  ?
Why is it needed to do so?
Thanks alot in advance

Found it (i.e. the "c:\path\to\src") shoud mean the root of caffe, which has the CMakeLists.txt in the folder.


Automated Package Upgrade

:tada: This PR is included in version 26.0.15 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Set up contributing templates

Set up nice contribution templates for issues and prs

pr template is defined here already


Change packages origin XPM icons with real icons

Software Station sometime crash when rendering XPM icon this chage should fix that problem.

Closing this


Delay CellProcessor Exceptions

http://super-csv.github.io/super-csv/roadmap.html
close #9

Coverage decreased (-1.9%) to 97.159% when pulling e33f2d1b563a6726f33736b262afab4e79c9bd0d on dota17:delayingerror into 208d3082cd5cdab39da8873cf741f8b672d1af5b on super-csv:master.

sorry for my absence. A lot has been going on. I'll promise to look at this within the week ;)


Refresh system tray icons

I'm using OSOL to launch Origin game from Steam, set Origin as launcher and set a specific game to start, Origin can be killed in several seconds after game exited, this works perfectly except one, the Origin icon still exists in system tray until mouse hover.
So, is it possible to refresh system tray icons?

I also can say this happens.

Yes, it's possible. I'll add it to my checklist for v1.07.


help center: Rewrite Import from Slack documentation.

Testing:

I tested the export process with a Slack org (on the Free plan).
I previewed the page and manually tested the links.

The page is too long to be easy to share as a screenshot, so please pull down the PR to preview.

Merged, after a few added changes:

Some copyediting of "Slack organization" => "Slack workspace".
Wrapping tabs around the zulip-cloud/self-hosting blocks of import instructions.

Huge thanks for doing this @alya and all the reviews from folks, this is a big improvement on a pretty high visibility page.


Reduce logging regarding new connections

Affects Version(s): 2.1.4

Enhancement request: reduce logging level for new connections from info to debug:
INFO  [o.s.a.r.c.CachingConnectionFactory] - Attempting to connect to: [rabbitmq:5672]
INFO  [o.s.a.r.c.CachingConnectionFactory] - Created new connection: rabbitConnectionFactory#5ec10ab1:0/SimpleConnection@5d4284e5 [delegate=amqp://guest@<IP_ADDRESS>:5672/, localPort= 33888]

It seems overkill to get trivial successful events on an info level.

And maybe the ones that log the BAD_URI in AbstractConnectionFactory should be switched from info to warn

Unfortunately the first log ("Attempting...") was specifically added to help debug bad configuration; many people asked for it.
We can add a switch to control the level though, but we will have to leave the default at INFO.

Hmm, that's weird, imagine how it would look like in case of JDBC connections :|

But, generally, there is only one shared connection; even with CacheMode.CONNECTION there should not be that many connections opened so I don't really understand why it's an issue.

But, generally, there is only one shared connection; even with CacheMode.CONNECTION there should not be that many connections opened so I don't really understand why it's an issue.
Why can't you just increase the logging level to WARN for that logger?

Hmm, I was just experimenting with it and thought there will be more connections, that's why I gave the JDBC example and I've created the ticket because I like sane defaults 🙂
But you're right, if it's just one, it should be fine.
Sorry for the noise.


Add tests for batch pipeline

Signed-off-by: Igor Egorov<EMAIL_ADDRESS>Description of the Change
Add two more tests for transaction batch pipeline.
Make checks in existing cases more strict.
The new tests were created due to occurred Iroha endpoints misuse.
Torii endpoint was used instead of ListTorii when it was needed to update set of batch signatures.
That is why I created tests that check that everything is ok when correct endpoints are used.
Benefits
Increased test coverage.
Possible Drawbacks
Not known.
Usage Examples or Tests
batch_pipeline_test

Reopened as #44


i18n

This is a work in progress to make it possible to translate the site. Any and all feedback on how to make this easier is welcome.
Implementation
This site uses Jekyll and is hosted on GitHub Pages. There is a Jekyll plugin for multiple languages, but it's not supported on GitHub Pages. So we'll have to manually add the facilities for supporting translations.
Currently, I'm thinking that the infrastructure for doing translations will be in this repository, and the translations themselves will exist as forks. Completed translations will be given a subdomain for their locale (like fr.opensource.guide) and be listed on the website. We'll make it as easy as possible for translations to get updates, but ultimately it will be the translation maintainer's responsibility to keep up to date.
Thoughts?
TODO

[x] Structure for localizing strings (_data/locale/zz.yml)
[x] Update all strings in the markup
[x] figure out structure for translating the guides themselves
[x] Tests for missing and unused localization strings
[x] Figure out pattern for translating aria labels on octicons
[x] Add locale switcher on the site (#354)
[ ] Docs/process for translating the twitter cards
[ ] Remove or make "Section x" headings localizable (#364)
[ ] Complete one translation to make sure the infrastructure is sufficient (#299)
[x] Document the translation process in CONTRIBUTING.md

Fixes #288

@bkeepers
I am working on translation of chinese version. I will post on my personal blog before i18n is supported on official website.
thanks for your work!

@bkeepers
I think that keeping gh-pages main branch makes it complicated to support different repo configs. Perhaps the branch with published web-site should be generated via CI and it should be possible to keep all the stuff related to original sources and sources of translated articles without interferring.
e.g. Having .travis.yml in sync and supporting multi-language _config.yml.
What do you think about such setup?

@webknjaz I'm not sure I understand what you're suggesting.
The problem is that Jekyll doesn't support i18n natively, and GitHub Pages doesn't support any of the plugins that try to add it. For now, I would like to avoid a custom build process, so I am aiming to make it as easy as possible for people to create forks of the website with translations, but in a way that will make it easy to merge back together later if/when jekyll and GitHub Pages gets native i18n support.
In my mind, the easiest way to do this is for each language to have a canonical fork (e.g; you would maintain the Ukranian fork on your own GitHub account) that takes over the gh-pages branch. Each translation will get an official subdomain (uk.opensource.guide). To the end-user, it will look like one website, even though each fork is technically a completely separate site on GitHub Pages.
Does that make sense? I'd love feedback on this approach.

@bkeepers oh, I was thinking the build process could rely on some env var or repo naming convention, so that it would just pick language depending on that condition. I usually do the build via Travis CI and push to gh-pages generating CNAME file dynamically.
Can this be an option? This would require just a few configuration changes from the fork owner (probably just enable Travis CI and and an env var).
This way the forks could be periodically merged back to upstream w/o any conflicts like having different CNAME/_config.yml etc.
On the other hand each time when upstream changes are being absorbed by forks this option will eliminate same issues.

oh, I was thinking the build process could rely on some env var or repo naming convention, so that it would just pick language depending on that condition. I usually do the build via Travis CI and push to gh-pages generating CNAME file dynamically. Can this be an option?

I'd really like to avoid custom build stuff for now. Let's get the actual translations done first and then we can figure out how to optimize everything else.

Sure, there are 4 files in progress of translation already :)

@bkeepers have you considered to utilize open source friendly translation management system like https://www.transifex.com/?

@joelhandwell AFAIK that tool is designed for interface localisation purposes (and isn't free) and doesn't fit article translation requirements

@bkeepers have you considered to utilize open source friendly translation management system like https://www.transifex.com/?

@joelhandwell I've never used anything like that. Does it work well with vanilla Jekyll on GitHub Pages?

@webknjaz AFAIK that tool is designed for interface localisation purposes (and isn't free) and doesn't fit article translation requirements

I agree that Transifex is primary designed for interface localization. However as we can see Creative Commons using we can say it's designed for not only for interface, but also for articles. The Data Journalism Handbook also chose it to translate articles.

(and isn't free)

According to their FAQ "What is considered an Open Source project?":

Transifex offers an Open Source Program to Open Source projects that have no funding, revenue, and/or commercialization model. The intent is to support small and independent Open Source projects. If your project does not fall in this category, please contact us to discuss the appropriate pricing.
Open Source projects are ones with publicly available source codes licensed under an OSI-approved license, such as GPL or BSD.

So if this project is funded by Github by any means, appropriate pricing may be discussed, otherwise if they approve license of this project are ok, I guess it's free.
I do not want to restrict options to only in Transifex. There is alternatives for Transifex for example Zanata with its source . Big project like OpenStack migrated from Transifex to Zanata. For your info, here is OpenStack documentation translation project (not interface).

@bkeepers Does it work well with vanilla Jekyll on GitHub Pages?
Jekyll parses markdown to render html, so translation work is done in markdown. Transifex can consume markdown files and each paragraph gets its own entry then translators can start working on their web app. After translation done, the files are available for pull. So technically there is no incompatibility. Here is how it works. For more automation, there is Github integration.

Their main advantage is to help open source efficiently achieve Crowdsourcing Translations

Thanks @joelhandwell for more info. GitHub's docs team is actually in the middle of evaluating systems for managing translations. I saw a demo of @yarnpkg's setup, which is using Crowdin, and was impressed (cc @thejameskyle).
What's most important to me is that the system is compatible with an open source workflow. Has anyone contributed to other open source projects that have a good setup for translation?

I wrote down all of the setup work involved with syncing between Crowdin and GitHub here: https://github.com/thejameskyle/crowdin-sync

We've been successful in getting the community to translate the Yarn website https://yarnpkg.com/en/org/translations using Crowdin and the process outlined in crowdin-sync. This is the status in just a few weeks:

Oh and note that Crowdin chokes on Jekyll frontmatter right now (I've spoken to them and they will be adding support for it in the near future), in the meantime I created this script to just copy the english version into each one.

It's great to see how quickly the community has translated yarn's docs. 🐈
@thejameskyle did you create crowdin-sync because Crowdin's GitHub integration is lacking in some way?

@zeke Oh cool, I think that must be new. I would like to try that out

Crowdin just told me that Jekyll frontmatter support should be implemented next week btw

I Can't find the link to make the French Translation. Someone can Help ?
What is the tech chose to make it ?  crowdin-sync ?

@Gotgot59 this is still a work in progress, but if you'd like to get a head start, follow the instructions outlined in the new translations.md file: https://github.com/github/open-source-guide/blob/bf259a187a8a5a84a784d9fafc3221303173e168/docs/translations.md

@bkeepers I added one more todo in your original post: document the process for future translations :wink:

Hello! Looking forward to digging into this code. But the following statements give me pause in doing so:

There is a Jekyll plugin for multiple languages, but it's not supported on GitHub Pages. So we'll have to manually add the facilities for supporting translations.

It seems it would be easier to maintain and more beneficial for the community if one of the following were to occur:

Work with core team to bake language support into Jekyll
Work with plugin maintainers and GH to introduce a new whitelisted i18n plugin

As it stands the number of years of Jekyll development have introduced a lot of individual effort and varying approaches having someone champion this effort on the Jekyll side seems like the best course of action to help save time for others going forward.
Nevertheless, looking forward to seeing this go live. See also: https://developmentseed.org/blog/multilingual-jekyll-sites/

I've merged in all the latest changes and I think this branch is ready to merge. There are still some things to work out with the translation process, but we'll work through those in subsequent PRs and continue to refine the process as we start to promote official translations.
Note: Build is failing because of transient failures on external links. Ignoring for now

Is it possible to define a fallback list of languages ? I suggest to make it similar to the $LANGUAGE var in bash. See man 7 locale.


Update S3X Name to Explicit Coin

I'm submitting a ...
[ ] bug report
[X] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary
Need to change Token Name from S3X to Explicit Coin
here is the PR  #25775

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

@keone I just need to change name of my token


V0.0 release merge

Coverage remained the same at 89.093% when pulling a689480e36ba8aab7c2d556920423f6e566e0461 on V0.0 into b3b6a340a1e32442b408f86c57439b42504dc29d on master.

Coverage remained the same at 89.093% when pulling c8de53cd2c8e0417b1cabcae7da583c59a18204c on V0.0 into b3b6a340a1e32442b408f86c57439b42504dc29d on master.


Toggler on accordion not show

I would like use Toggler with Accordion module. But, if [data-toggle] is in .accordion-item, it's don't work because accordion-item is display: none;
Is this a bug or is it impossible to run both ?
Test case:

Example on http://codepen.io/anon/pen/vKyvJv

Instead of declaring the display: none directly to the element, you can use the built-in visibility class which is .hide. Then you use the .hide class as the value of the data-toggler, see code sample below.

Hello world !

Hope that helps.

Hi @denisahac
I've test, and it work fine.
But if i add data-closable for close Toggler with button, it adds style="display: none;"instead of removing .hide classe.

Can you try the code sample below, I think that is something you'd like to accomplish.

  Hello world !
  <button class="close-button" aria-label="Dismiss alert" type="button" data-close>
    ×
  </button>

Adding the .hide class as the value of data-closable makes the desired functionality works.

Work nice !
I was try with data-closable="**.**hide" when i've test :)
Thank for your help @denisahac

@LeG3nDz You're welcome. I think you should close this issue now. You can still re-open it if you're having issues in the future.

Good solution, @denisahac. I assume this is resolved, so I'm gonna close this issue.


Use 'T1 etc for type variables in F#

F# style guidelines prefer the use of 'T1 etc for type variables.
Pointed out on twitter https://twitter.com/jordan_n_marr/status/1420043164535173125

Thanks!


Very slow processing for width and height over 40

The generation time is increasing rapidly and is painfully slow over height and width values over 40. Need to find a solution to this. Can optimise functions and make some steps optional (like connecting unconnected rooms, removing dead ends etc.)

Further testing points out that the main issue is windingPercent, higher values exponentially slows down generation

Was not able to recreate this
Slow generation is still true for very big dimensions.


ShapeCast2D not working with C#

Godot version
4.0-beta3
System information
Windows10, AMD Ryzen 9 3900XT, RTX3070, Vulkan
Issue description
ShapeCast2D collision does not get detected in C# while it does in GD Script, even though the code is an exact translation.
I am casting a circle with a radius of 10 from (0, -100) to (0, 100), so both rectangles should be caught in the collision. They are in fact both caught with GD Script code, while they are not caught in C#.

C# Code:
  public override void _Ready()
  {
	var shape = PhysicsServer2D.CircleShapeCreate();
    	PhysicsServer2D.ShapeSetData(shape, 10);

    	var param = new PhysicsShapeQueryParameters2D();
    	param.CollisionMask = 1;
    	param.ShapeRid = shape;
    	param.Motion = new Vector2(0, 100);
    	param.Transform = (new Transform2D()).Translated(new Vector2(0, -100));

    	var result = GetWorld2d().DirectSpaceState.IntersectShape(param, 10);
        GD.Print(result)
  }

GD Code:
  func _ready():
        var shape = PhysicsServer2D.circle_shape_create();
	PhysicsServer2D.shape_set_data(shape, 10);

	var param = PhysicsShapeQueryParameters2D.new();
	param.collision_mask = 1;
	param.shape_rid = shape;
	param.motion = Vector2(0, 100);
	param.transform = Transform2D().translated(Vector2(0, -100));

	var result = get_world_2d().direct_space_state.intersect_shape(param, 10);
        print(result)

Steps to reproduce

Create a Scene with 2 static body colliders and make a small gap between them
Perform a shape cast with a C# script that runs exactly through the gap
Print result

Minimal reproduction project
BrokenShapeCast2D.zip

The Transform2D parameterless constructor in C# is not the same as the parameterless constructor in GDScript. To get the same behavior as in GDScript you need to use Transform2D.Identity as described in the documentation.

omg, thanks that fixes it. It is a bit strange that it is that way, but I guess the Shape cast works fine.


Exit code when there is breaking changes?

It looks like apicompat currently returns exit code 0 when there is a breaking change:
$ apicompat -before master -after HEAD; echo $?
master:intersect.go:72: breaking change declaration removed
	func (q Query) IntersectByT(q2 Query, selectorFn interface{}) Query

0

Is this by design? Making it exit with non-zero code would help the CI scripts which make use of exit codes a great deal.
Also it looks like there's an empty line (\n\n) at the end of the command (before 0). Is that also by design?

Thanks for the report @ahmetalpbalkan, you're right on both accounts, I would like a unique exit status for breaking changes (as opposed to other internal errors), and the extra newline has been removed (I haven't done it in the best way, but it's fine enough).
Please review #36 when you have a moment and let me know your thoughts.


Python: if statement

Description :
What is if statement in python?
Note :

Changes should be made inside the Python/ directory & Python branch.
Issue only for GWOC'21 contributors.
Issue will be assigned on a first come first serve basis, 1 Issue  ==  1 PR.
In the PR, keep this issue's title as your PR's title.

Must Follow : Contributing Guidelines & Code of Conduct before start Contributing.

I would like to work on this please documentation
Peddi sai lohith
Python batch 4

can you assign me to these ? @adityabisoi

I can work with this too so please do consider. Thank You!!

I would like to work on this issue for documentation

Hi I'd like to contribute through documentation on this topic
Harmandeep - python - batch 4

Hi I'd like to contribute on this topic
python - batch 4
@adityabisoi

I would like to work on this issue through documentation.
Vibhu - Python Batch 5

I would like to contribute on this issue.

I would like to work on this issue. Please assign me this issue. I am ready to contribute in any of the three ways of audio/video/documentation.

@adityabisoi
Sir, I would like to contribute to this issue.
Name: Priyanshi Naredi
Type: Documentation
Batch: 18

I would like to work on this issue via documentation.

Hello Sir, I am from batch  6
I would like to work on this issue via documentation

@adityabisoi
Sir, I would like to contribute to this issue.
Name: Arushi Rautela
Type: Video
Batch: 6

If this issue is not yet assigned to anyone, I would be happy to work on it.
Name: Khushi Shah
Python Batch: 3
Preference: Documentation

@kumarankm Is the mentor of this issue. Please reach out to him in case of queries.

Can i contribute documentation on this issue?

Can i contribute documentation on this issue?

Mention type.

/assign

hello @adityabisoi
I want to contribute to this issue in video format
tejas prajapati python batch-6

If this issue is not yet assigned to anyone, I would be happy to work on it.
Name: Akkineni Yogitha
Python Batch: 1
Preference: Documentation

I would like to work on this issue. Please assign me this issue. I am ready to contribute in any of the three ways of audio/video/documentation.

Go with audio


unexpected errors

Hi there
I just installed your module and made gulp file as instructed, but I get some unexpected errors!
when I run this command :
me@pc ~/myproject $ gulp sm:exec -c pwd
I get:
{ [Function: exec] description: 'execute arbitrary commands in submodules' }
[11:44:19] Using gulpfile ~/iform-fullstack/gulpfile.js
[11:44:19] Starting 'sm:exec'...
[11:44:19] 'sm:exec' errored after 52 ms
[11:44:19] Error: Command failed: /bin/sh -c name=server/components/common && branch="$(git config -f ../.gitmodules submodule.$name.branch)" && pwd

how can I fix this?

similar to what i experience.
when running a simple gulp sm:list i get:
iris-main >: gulp sm:list
{ [Function: exec] description: 'execute arbitrary commands in submodules' }
[20:34:55] Using gulpfile ~/Development/DockerTest/iris-main/gulpfile.js
[20:34:55] Starting 'sm:list'...
[20:34:56] 'sm:list' errored after 169 ms
[20:34:56] Error: Command failed:
    at ChildProcess.exithandler (child_process.js:658:15)
    at ChildProcess.emit (events.js:98:17)
    at maybeClose (child_process.js:766:16)
    at Socket.<anonymous> (child_process.js:979:11)
    at Socket.emit (events.js:95:17)
    at Pipe.close (net.js:466:12)
[20:34:56] 'sm:list' errored after 172 ms
[20:34:56] Error: Command failed:
    at ChildProcess.exithandler (child_process.js:658:15)
    at ChildProcess.emit (events.js:98:17)
    at maybeClose (child_process.js:766:16)
    at Socket.<anonymous> (child_process.js:979:11)
    at Socket.emit (events.js:95:17)
    at Pipe.close (net.js:466:12)

after upgrading to node 5.5.0 it says:
iris-main >: node -v
v5.5.0
iris-main >: gulp sm:list
{ [Function: exec] description: 'execute arbitrary commands in submodules' }
[20:44:29] Using gulpfile ~/Development/DockerTest/iris-main/gulpfile.js
[20:44:29] Starting 'sm:list'...
[20:44:30] 'sm:list' errored after 231 ms
[20:44:30] Error: Command failed: /bin/sh -c name=iris-docs-server && branch="$(git config -f ../.gitmodules submodule.$name.branch)" && printf $name

    at ChildProcess.exithandler (child_process.js:213:12)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at maybeClose (internal/child_process.js:821:16)
    at Socket.<anonymous> (internal/child_process.js:319:11)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at Pipe._onclose (net.js:469:12)
[20:44:30] 'sm:list' errored after 237 ms
[20:44:30] Error: Command failed: /bin/sh -c name=iris-server && branch="$(git config -f ../.gitmodules submodule.$name.branch)" && printf $name

    at ChildProcess.exithandler (child_process.js:213:12)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at maybeClose (internal/child_process.js:821:16)
    at Socket.<anonymous> (internal/child_process.js:319:11)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at Pipe._onclose (net.js:469:12)
iris-main >:

this is on Mac 10.11.2


Updated CSS and added a carousel

👷 Deploy Preview for benevolent-sprinkles-4567d6 processing.

Name
Link

🔨 Latest commit
db7e7c0512ec336fd4557f58e05c12f8ed52e510

🔍 Latest deploy log
https://app.netlify.com/sites/benevolent-sprinkles-4567d6/deploys/65bfad9a679c51000828e6d7


systemctl try-reload-or-restart instead of restart in google_set_hostname

Currently, google_set_hostname (when running under systemd only; it sends a SIGHUP when not under systemd) restarts rsyslog every DHCP renew. I suspect, but have not tested, that could cause log messages to be lost. Also, since it's "restart" instead of "try-restart", it will unexpectedly start the daemon if the sysadmin or package management system has stopped it. It also annoying fills the log with a lot of messages that rsyslog has been stopped, which would normally be an important event.
I suggest using try-reload-or-restart instead. That's the current name, though it used to be known as reload-or-try-restart, which still works (see sytemd pull request 2464).
Under the default Debian 9 setup, at least, that will still restart rsyslog. But at least that's easily fixable by the admin adding ExecReload=/bin/kill -HUP $MAINPID in an override file for rsyslog.service. Also, since it's a "try" variant, it won't unexpectedly start the daemon if the admin, package management system, etc. has stopped it.
That'd be something like this:
+++ b/dhcp/dhclient-exit-hooks.d/google_set_hostname
@@ -52,7 +52,7 @@ if [ -n "$new_host_name" ]; then
   if [ -x "$systemctl" ]; then
     hasrsyslog=$($systemctl | grep rsyslog | cut -f1 -d' ')
     if [ ! -z "$hasrsyslog" ]; then
-      $systemctl -q --no-block restart "$hasrsyslog"
+      $systemctl -q --no-block try-reload-or-restart "$hasrsyslog"
     fi
   else
     pkill -HUP syslogd

Or, alternatively, the SIGHUP path would work find under systemd too.

/cc @hopkiw

I thought along the same vein, but this won't solve the extra logging problem, because rsyslog.service, at least one that comes with Debian 9 and Ubuntu 18.04 is not written to handle a reload:
kkm@yupana:~$ sudo systemctl reload rsyslog
Failed to reload rsyslog.service: Job type reload is not applicable for unit rsyslog.service.
See system logs and 'systemctl status rsyslog.service' for details.
kkm@yupana:~$ sudo systemctl cat rsyslog
# /lib/systemd/system/rsyslog.service
[Unit]
Description=System Logging Service
Requires=syslog.socket
Documentation=man:rsyslogd(8)
Documentation=http://www.rsyslog.com/doc/

[Service]
Type=notify
ExecStart=/usr/sbin/rsyslogd -n
StandardOutput=null
Restart=on-failure

[Install]
WantedBy=multi-user.target
Alias=syslog.service

So maybe just pkill -HUP is really a better way to go, systemd or not.
What I do not understand is why syslog needs to be reloaded even when the host name has not in fact changed.

You can also use systemctl kill --kill-who main -s SIGHUP rsyslog.service under systemd to just send the HUP directly. Which is slightly better as pkill could conceivably match a process that happens to have the same name (I'm not sure if, e.g., pkill might hit syslogd inside a container).

@kkm000 I think your reply doesn’t take into account that systemctl try-reload-or-restart behaves as expected if the unit file isn’t built to handle a reload. From the systemctl(1) man page:

try-reload-or-restart PATTERN...
Reload one or more units if they support it. If not, stop and then start them instead. This does nothing if the units are not running.

This means the original suggestion should work. (Sending SIGHUP is valid, too, but a better fix is to ask upstreams to add the appropriate ExecReload= line rather than working around on our end.)

@jeremyvisser  Sorry, looks like I missed your comment back then.  try-reload-or-restart will do exactly same thing as restart when the service does not support reload, and rsyslog it in fact does not. And the whole point is to avoid a restart.

@kkm000 My apologies; I misunderstood your comment. Re-reading your comment, essentially you’re saying that because rsyslog.service does not contain a ExecReload= line, my suggestion would cause it to restart anyway.
Therefore, it sounds like the options are:

Modify the Debian–provided rsyslog.service (i.e. drop-in unit) to provide a ExecReload=/bin/kill -HUP $MAINPID function.
Do a pkill -HUP rsyslogd as you suggested before in the dhclient hook.

Given tampering with distro–managed units may lead to unexpected sysadmin surprises, the second option sounds less risky and therefore better.

Modify the Debian–provided rsyslog.service (i.e. drop-in unit) to provide a ExecReload=/bin/kill -HUP $MAINPID function.

That's not a bad option too; the problem as I see it is Google will have to support that separately too. A distro-independent solution is always less taxing, even if not super-clean. Yeah, Google is big, but if RedHats's almost only product is RedHat, compute-image-packages is not Google's main product by any metric. When I was an SWE at Google, economy improved after the housing bubble, and our team slowly trickled down from 7 to 3--it became harder and harder to hire. So instead of pager weeks (one primary on-call, next secondary), we each had one pager-free week of three : ) And you can do only so much in a day.

Personally, I uninstall rsyslog in my custom image prep script, and using journald. It's beneficial, because it allows keeping a single journal for system and all users in a single log database file. It also supports log forwarding natively, which is a boon too. And it logs to console, starting very early if enabled on kernel's command line, which avoids the problem that rsyslog has due to default permissions on /dev/console (#889).  I rid of logrotate and even cron, as of Buster there are no essential cron jobs, except a BSD calendar and man-db maintenance script, which is a vestige of those real 80286 days: it leisurely pre-renders man pages to fixed 80 column .cat files so they can be displayed quickly on your latest and newest VT340, but they never match the screen width any more anyway). Everything critical has been ported to systemd timers already as of Deb10. The only thing I keep is crhony, as it's less jumpy during a VM migration than systemd's NTP service. But as for DHCP, DNS and interface management, systemd cuts it pretty well. Systemd is deliberately simplistic in its approach, but works for mostly everyone.
RH is systemd-ized now completely or nearly so, AFAIK, and Arch started with systemd from day one. Debian is kinda at the end of the herd, and need most tweaks, but when I chose Debian 10 as my base system, Centos 7 was too aged, and Centos 8 was promised "some time next year", so I had to roll my own. But once you start messing with the distro, you'll never stop, so the image packages team is doing the right thing, IMO, by keeping the packages as distro-agnostic as possible. It works for the absolute majority of people transparently, and for someone like me (I run computing clusters, where the startup time of a new node from an image is in the critical path), tweaks are inevitable anyway.


python3Packages.hyppo: minor clean-up

Motivation for this change
Noticed the package could use some clean-up.
Things done
Note depending package graspologic is already broken.

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 149693 run on x86_64-linux 1

2 packages failed to build:

python38Packages.graspologic
python39Packages.graspologic

2 packages built:

python38Packages.hyppo
python39Packages.hyppo

python3Packages.graspologic already failed to build on master (https://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.python39Packages.graspologic.x86_64-linux) so looks good to me.


Non-Square pixel error

Hello everyone
I have tried to to use the QGIS script in one of my case study in Arkansas River. The resolution of DEM is 1m and the flood map resolution is 10m. However, I got an error 'non square pixels'.
How can I fix this?
I checked the sample datasets have DEM resolution of 4m and the flood map resolution is 32m. Do I need to resample data to this resolution?

Thank you for the question.
Can you send a copy or a screen shot of the log?
This check is performed as the algorithm has not been tested against non-square pixels. Regardless, It should be reduced from an error to a warning.
In the meantime, Have you tried re-projecting your rasters to square pixels? (e.g., using 'Warp Reproject... and setting the resolution?).

Here is the screenshot. I will try with the reprojection to square pixels

I got this error while using the downscaling script.

Is it due to the slight  mismatch in the extent?

Hi I have reprojected the pixels to 4m and 32m but still got this error. IS it due to the slight mismatch in the extent coordinates?

Yes, extents need to be identical… again this could probably reduced to a warning


Multiple feedbacks

Under Step 2: If I did not follow the steps under "Setting up authentication for enumerating dedicated SQL database resources under a Synapse Workspace" on a serverless pool the scan in Purview was throwing errors. Hence, I think the steps in the above section applies to serverless pool also

The T-SQL scripts under "Using Managed identity for Serverless SQL databases" are a repeat of what has already been done under section "Setting up authentication for enumerating serverless SQL database resources under a Synapse Workspace"

The T-SQL scripts under "Using Service Principal for Serverless SQL databases" are also the repeat as noted in item 2 above. I think instead of [PurviewAccountName], it should be replaced with [ServicePrincipalName]

I did not put the above changes in the article to avoid too many edits.. Let me know if something is not clear. Happy to run more tests if needed

@svchandramohan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#hold-off (reports an issue; not mergeable)

@whhender Can you discuss please with Situmalli Chandra Mohan and Zeinab on an email thread re the feedback here. The PR diff is not complete, but the description outlines the recommended changes. I think this article had been revised just a couple weeks ago, so it should be a fresh topic. Thanks, Jason

#reassign:zeinab-mk

#please-close
PR 162192


[Workbox] Fixes for the broadcastUpdate.Plugin guide

R: @petele @philipwalton
Fixes some issues with the workbox.broadcastUpdate.Plugin() constructor's parameters raised in https://github.com/GoogleChrome/workbox/issues/1994

Whoops!
There were 1 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/workbox/modules/workbox-broadcast-cache-update.md#L156 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful

:tada: This has been pushed live to https://developers.google.com/web/


(maint) Change subcommand pre-suite to install ruby 2.3.1

This is required for the updated byebug gem dependency. All ruby
unit tests have already been moved to ruby 2.3+, this is keeping
consistentcy.

@smcelmurry I'm wondering if it might be better to head this off in the future by making it piggyback on a job parameter that is already set for our ruby versions?
I would imagine it would look something like this (top of file):
ruby_version, ruby_source = ENV['job-ruby-version'], "job parameter"
unless ruby_version
  ruby_version = "2.3.1"
  ruby_source = "default"
end
test_name "Install and configure Ruby #{ruby_version} (from #{ruby_source}) on the SUT" do
...

does that make sense to you as an improvement for this PR?

@kevpl Yep that makes sense but right now we don't have a parameter to set the version. I'll still include this improvement but we should also look at adding that param to our pipelines in the future.

retest this please

We should match the gemspec requirements: https://github.com/puppetlabs/beaker/blob/master/beaker.gemspec#L20
We will have to make sure our users also use that version or newer in their agent executing beaker.

retest this please


Implement cognito backend

[x] Implement basic functionality using Cognito SDK. Tutorial Github snippets
[x] Make the UI look good
[x] Develop an interface where the user can manage their login settings (enable/disable TOTP, enable/disable phone MFA, change password...)

Note: It'd be great if we could manage AWS' configuration using reproducible builds encoded into text files (eg: using Terraform) but not sure if it's worth the time required. -> DONE

Docs: https://aws-amplify.github.io/docs/js/authentication

Finished


Update workflow to fix invalid create event with tags filter

Description
The current release workflow uses the create event with a tags filter, which causes an error ("A mapping was not expected"). GitHub Actions does not support the tags filter under the create event. We need to update the trigger to use push with a tags filter to ensure the workflow runs when a tag is pushed.

Hello  @SarthakJain26 @shivam-Purohit
I have opened this issue, and if you find it valuable, please assign it to me
Thank you


pdd rules failed with exception

I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues):

(): did not find expected key while parsing a block mapping at line 1 column 1

Please, copy and paste this stack trace to GitHub:

Psych::SyntaxError
(<unknown>): did not find expected key while parsing a block mapping at line 1 column 1
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/psych.rb:456:in `parse'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/psych.rb:456:in `parse_stream'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/psych.rb:390:in `parse'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/psych.rb:349:in `safe_load'
/app/objects/git_repo.rb:54:in `config'
/app/objects/job_emailed.rb:37:in `rescue in proceed'
/app/objects/job_emailed.rb:34:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:48:in `exclusive'
/app/objects/job_detached.rb:36:in `block in proceed'
/app/objects/job_detached.rb:36:in `fork'
/app/objects/job_detached.rb:36:in `proceed'
/app/0pdd.rb:366:in `block in <top (required)>'

fixed


go/types: importing an alias and the original causes import error

Tracking issue. See TODO in forthcoming TestAliases (go/types/api_test.go).

cmd/compile exports the same object multiple times if there's more than one exported alias referring that object. This breaks an invariant that was true for the platform-specific portion of export data and which was checked and relied upon by the go/importer.


I got stuck when installing graphite component from source

Hi guys,
Here's the step i used to install graphite from source.
cd /tmp
git clone https://github.com/graphite-project/graphite-web.git
git clone https://github.com/graphite-project/carbon.git
git clone https://github.com/graphite-project/whisper.git
cd whisper; git checkout 0.9.13-pre1; python setup.py install
cd ../carbon; git checkout 0.9.13-pre1; python setup.py install
cd ../graphite-web; **python check-dependencies.py; git checkout 0.9.13-pre1; python setup.py
install**

The point is after executing the python check-dependencies command, the error appeard.
[WARNING]
Unable to import the 'ldap' module, do you have python-ldap installed for python 2.7.5?
Without python-ldap, you will not be able to use LDAP authentication in the graphite webapp.
[WARNING]
Unable to import the 'txamqp' module, this is required if you want to use AMQP.
Note that txamqp requires python 2.5 or greater.
All necessary dependencies are met.
2 optional dependencies not met. Please consider the warning messages before proceeding.
I installed python-ldap but it still said the same error. Can some one tell me how to fix it, please?

Hi @thinhduckhoi,

Please do not use 0.9.13-pre1 branch, use 0.9.15 or 0.9.x instead
It's just WARNINGS, you can safely proceed.

@deniszh Thank you, i'll try it!

Ah, i tried to use 0.9.15  and saw this.
[Optional] Unable to import the 'python-rrdtool' module, this is required for reading RRD.
[Optional] Unable to import the 'whitenoise' module. This is useful for serving static file/
And the same error "ldap-python"  and txamqp. Should i process?

Yep, it's optional components.


move repo to apiops

after we have reached version 1.0 we should more this repo to APIOps org https://github.com/apiops

Agreed


Client connected but it doesn't receive anything

The client is connected fine and can send and receive events, but some times the server doesn't recieve any event and the client is still connected.
The way to reproduce it:
Start and stop the client a few times, until it stops receiveing the pong message.
client:
const socket = io("http://localhost:8080");

socket.on("pong", ({ datetime }) => {
    console.log(`Response time (${(Date.now() - datetime)}ms)`)
});

socket.on("connect", () => {
    console.log(`Connected! ${socket.id}`);

    setInterval(() => {
        socket.emit('ping', { datetime: Date.now() });
    }, 1000);
});

socket.connect();

server:
const io = new Server();

io.on("connection", (socket) => {
    console.log(`socket ${socket.id} connected`);

    socket.on('ping', (data) => {
        console.log(`[${socket.id}]: ping!`)
        socket.emit('pong', data)
    });
});

await serve(io.handler(), {
    port: 8080,
});

Woooow, only two weeks from the start?? Great job, dude!

This should be fixed by https://github.com/socketio/socket.io-deno/commit/c706741544e33ca364ef88e3779aa8d4ee3739f0, included in 0.2.0.
Good catch, thanks!

@pagoru can you share your full code from client to connect, I'm trying to connect, but never I have fabled connect :(


Can anyone share auth0 example with nuxt3?

Ask your question
My server/api/auth/[...].js file
import CredentialsProvider from "next-auth/providers/credentials";
import Auth0 from "next-auth/providers/auth0";
import { NuxtAuthHandler } from "#auth";

export default NuxtAuthHandler({
  // secret needed to run nuxt-auth in production mode (used to encrypt data)
  secret: process.env.NUXT_SECRET,
  providers: [
    Auth0.default({
      domain: process.env.AUTH0_DOMAIN,
      clientId: process.env.AUTH0_CLIENT_ID,
      audience: process.env.AUTH0_AUDIENCE,
    }),

    CredentialsProvider.default({
      name: "Credentials",
      credentials: {
        username: { label: "Username", type: "text", placeholder: "(hint: jsmith)" },
        password: { label: "Password", type: "password", placeholder: "(hint: hunter2)" },
      },
      authorize(credentials) {
        const user = {
          id: "1",
          name: "J Smith",
          username: "jsmith",
          password: "hunter2",
          image: "https://avatars.githubusercontent.com/u/25911230?v=4",
        };

        if (credentials?.username === user.username && credentials?.password === user.password) {
          // Any object returned will be saved in `user` property of the JWT
          return user;
        } else {
          // eslint-disable-next-line no-console
          console.error("Warning: Malicious login attempt registered, bad credentials provided");

          // If you return null then an error will be displayed advising the user to check their details.
          return null;

          // You can also Reject this callback with an Error thus the user will be sent to the error page with the error message as a query parameter
        }
      },
    }),
  ],
  callbacks: {
    async redirect({ url, baseUrl }) {
      // Allows relative callback URLs
      if (url.startsWith("/")) return `/auth/signed-in`;
      // Allows callback URLs on the same origin
      else if (new URL(url).origin === baseUrl) return url;
      return baseUrl;
    },
  },
});

With above setup I am getting following error:--

Login screen:

How do I use my custom login page and handle calbacks?
Additional information
No response

Hi @rajnish93!
From what I understand you are dealing with two separate issue; configuring 0auth and callbacks. I will quickly give some input to both issues!
0Auth
Auth0.default({
   domain: process.env.AUTH0_DOMAIN,
   clientId: process.env.AUTH0_CLIENT_ID,
   audience: process.env.AUTH0_AUDIENCE,
}),

I think that your Auth0 configuration is not setup correctly. When looking into the NextAuth documentation I can see that the Auth0 configuration should be:
Auth0.default({
   clientId: process.env.AUTH0_CLIENT_ID,
   clientSecret: process.env.AUTH0_CLIENT_SECRET,
   issuer: process.env.AUTH0_ISSUER
}),

See https://next-auth.js.org/providers/auth0
Maybe this will already fix your issue?
The error printed in your console also refers to the following page: https://next-auth.js.org/errors#signin_oauth_error. One of the listed issues is incorrect configuration, which is my assumption right now. If it does not fix the issue you can see some other reasons why the error may be called (you can also reply to the issue and I can look again 🤗)
Callbacks
async redirect({ url, baseUrl }) {
  // Allows relative callback URLs
  if (url.startsWith("/")) return `/auth/signed-in`;
  // Allows callback URLs on the same origin
  else if (new URL(url).origin === baseUrl) return url;
  return baseUrl;
},

The redirect callback is called anytime the user is redirected to a callback URL (e.g. on signin or signout).

This is the offical explanation of what the redirect callback is used for. It is called every time a user is redirected to a callback url of NuxtAuth. It does not apply to all redirects on the page. If you want to create a global redirect callback, I would recommend looking into Server Middleware: https://nuxt.com/docs/guide/directory-structure/middleware#middleware-directory
If you do need another callback from NuxtAuth feel free to look at the NextAuth documentation to see what is available: https://next-auth.js.org/configuration/callbacks#sign-in-callback

redirect_uri is not working to custom url.
going back to /api/auth

@zoey-kaiser
Thanks
Issue Fixed.


observability config not working 0.10.0

Readiness Checklist

[x] I am running the latest version
[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed
[x] I am reporting the issue to the correct repository (for multi-repository projects)

Expected Behavior
Creating observability config  when it's set in terraform
Current Behavior
When running creating Elastic Instance with observability config it doesn't configure instance.
Configuration doesn't work with supply "id" or "self"
## Terraform definition
  elasticsearch = {
    autoscale = {}
    hot = {
      autoscaling = {}
    }
    observability = {
      deployment_id = "self"
    }
  }

Steps to Reproduce
Attempt to apply the terraform configuration detailed above.
Context
Unable to provision our production instance because terraform fails set critical configuration such metrics/logs
Your Environment

Version used: 0.10.0
Running against Elastic Cloud SaaS or Elastic Cloud Enterprise and version:
Environment name and version (e.g. Go 1.9):
Server type and version:
Operating System and version:
Link to your project:

Hi, @rstreics-lb
Thank you for the bug report.
When I checked your script, I could see the observability block is inside of the elasticsearch block.
Both are sbling block and should have the sane indention depth.
Check the example here: https://github.com/elastic/terraform-provider-ec/blob/6e18a059218406fc56b8a0d93076205b01137e1e/examples/resources/ec_deployment/with-o11y/deployment.tf#L24
The below script is one of the examples that I tested myself.
The self monitoring feature was enabled with deployment_id = "self" option.
terraform {
  required_version = ">= 1.0.0"

  required_providers {
    ec = {
      source = "elastic/ec"
      version = "0.10.0"
    }
  }
}

resource "ec_deployment" "this" {
  region = "gcp-us-central1"
  version = "8.3.2"
  name = "ec-testing-4"
  deployment_template_id = "gcp-storage-optimized"
  elasticsearch = {
    hot = {
      size = "1g"
      zone_count = 1
      autoscaling = {}
    }
  }

  kibana = {}

  observability = {
    deployment_id = "self"
  }
}

If you need more clarification, let us know.


feat: support connection on secondary key

With Prisma it's possible to have a connect in a request on a unique field other than the primary key.

Hey @renaudleroy Thanks for you contribution, I will merge this and update toLowerCase to getCamelCase.


System Cannot Find the Drive Specified

The system cannot find the path specified.
Need a warning for this.

Resolved V0.25.2