improve on name

The current name is not great. Let's find something better (or explain why you like current).
@tiborvass @AkihiroSuda

Microsoft has their own docker-buildx :eyes: https://github.com/Microsoft/docker-buildx


Fix typo in insight/features.md

This part is used to describe the reason for submitting the PR.
Or you can also use it to further explain the content of the PR.

Wait for one more effective PR from you to fix issues, thanks.

See preview


Missing documentation for the constructure configuration

I feel like this is a support issue as well as a bug report and a feature request.
I looked through the documentation you provided but can not see any docs on the configuration object provided through the constructor. Looking both at:

https://www.npmjs.com/package/@google-cloud/bigquery
https://cloud.google.com/nodejs/docs/reference/bigquery/latest/bigquery/bigqueryoptions

We found this example: https://gist.github.com/Abszissex/b1d85a4ca7b72710b982a91404d92e00#file-bigquery_create_dataset_table-js-L8
My question is if this is the only acceptable configuration or if we can provide you the settings in the keyfile in the config object, instead of referring to a file that holds the same information. Reason being a standardisation we follow in the company that your solution breaks if it's not flexible in this sense; working with docker secrets and other configuration settings we have for other dependencies.
Or maybe all of this is documented somewhere, and I just can't find it. It would be nice to read about other possible settings, simply to learn what is possible.

Finally found it: https://cloud.google.com/nodejs/docs/reference/google-auth-library/latest/google-auth-library/googleauthoptions
I sugest that the inheritance breadcrumb is clickable, but I close this as it was my mistake to assume it's not documented.


Some more clean up of code table

Codecov Report

Merging #196 (2283be8) into master (32158d1) will decrease coverage by 0.00%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##           master     #196      +/-   ##
==========================================
- Coverage   90.14%   90.14%   -0.01%
==========================================
  Files         155      155
  Lines       35359    35351       -8
==========================================
- Hits        31875    31867       -8
  Misses       3484     3484

Impacted Files
Coverage Δ

tests/core/test_coring.py
99.96% <0.00%> (ø)

src/keri/core/coring.py
88.16% <100.00%> (-0.06%)
:arrow_down:

Continue to review full report at Codecov.

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


Add new methods

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 3 (66.67%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 95.21%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/yandex360/client.rb
1
2
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.4%

Covered Lines:
159

Relevant Lines:
167

💛  - Coveralls


Better GUI code error reporting

One important UX improvement for GUI component authors is providing clear and understandable error messages.
For now, we can just panic if the XML is invalid in any way.
The best solution is to use a crate like codespan, which would allow us to emit nicely formatted errors, just like the Rust compiler.

Shelved on account of switching to a web app frontend for the short term.


Test Telegram channel receive 'Error 500'

Describe the bug
On click 'Test Telegram channel', receive 'Error 500'
To Reproduce
Steps to reproduce the behavior:

Go to 'Notifications'
Click on 'Enable telegram notifications'
Click on 'Test Telegram channel'
See error

Expected behavior
No error and warning about the missing information
Logs
production.ERROR: count(): Argument https://github.com/alexjustesen/speedtest-tracker/pull/1 ($value) must be of type Countable|array, null given {"userId":1,"exception":"[object] (TypeError(code: 0): count(): Argument https://github.com/alexjustesen/speedtest-tracker/pull/1 ($value) must be of type Countable|array, null given
Additional context
On first time click is evaluating against a null object, of course count fails...
A new pull request #324 is open fixing this behaviour and with a bonus validation.

I confirm this Issue. I also have a question: In the Telegram notification settings I am only asked "ChatID" for the recipient.
No Telegram bot token request??!?! It's correct?
Thanks

I confirm this Issue. I also have a question: In the Telegram notification settings I am only asked "ChatID" for the recipient.
No Telegram bot token request??!?! It's correct?
Thanks

Yes on UI you only setup your personal ChatID, for bot token you have to setup on .env file in your mounted data directory.
Please refer to a documentation: https://docs.speedtest-tracker.dev/settings/notifications/telegram

@garanda21
Since i don't use the .env file,  can I pass an environment variable to my docker run?
-e TELEGRAM_BOT_TOKEN=putyourtokenhere
Thanks

@garanda21
Since i don't use the .env file, can I pass an environment variable to my docker run?
-e TELEGRAM_BOT_TOKEN=putyourtokenhere
Thanks

Absolutely, it should work. I have mine on my docker-compose variable and works perfect!

I confirm this Issue. I also have a question: In the Telegram notification settings I am only asked "ChatID" for the recipient. No Telegram bot token request??!?! It's correct? Thanks

I correct myself. The "Test telegram Channel" button works perfectly. The TELEGRAM_BOT_TOKEN in the .env file was probably missing

Hi
I just have the same "error 500"
I add the TELEGRAM_BOT_TOKEN in the .env file and I put the chat id in settings.
After testing receive the error 500.

Hi I just have the same "error 500" I add the TELEGRAM_BOT_TOKEN in the .env file and I put the chat id in settings. After testing receive the error 500. My log: <IP_ADDRESS> - - [17/Jan/2023:10:40:05 +0000] "POST /livewire/message/app.filament.pages.settings.notification-page HTTP/1.1" 500 6628 "http://<IP_ADDRESS>:8080/admin/notifications" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"

Just find error!!!
Please change your [documatation ](documentation: https://docs.speedtest-tracker.dev/settings/notifications/telegram)
here and in telegram Chat ID must be -1234567890

Hi I just have the same "error 500" I add the TELEGRAM_BOT_TOKEN in the .env file and I put the chat id in settings. After testing receive the error 500. My log: <IP_ADDRESS> - - [17/Jan/2023:10:40:05 +0000] "POST /livewire/message/app.filament.pages.settings.notification-page HTTP/1.1" 500 6628 "http://<IP_ADDRESS>:8080/admin/notifications" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"

Just find error!!! Please change your (documentation: https://docs.speedtest-tracker.dev/settings/notifications/telegram) here and in telegram Chat ID must be -1234567890

That pretty much depends on your chat, If the chat is a group, the chat id is negative. If it is a single person, then positive.
Right now mine is configured without dash and works perfect, my Chat ID is for single person.

Right now mine is configured without dash and works perfect, my Chat ID is for single person.

Same for me, my chat ID is a positive number, not negative. Works perfectly.

Hi I just have the same "error 500" I add the TELEGRAM_BOT_TOKEN in the .env file and I put the chat id in settings. After testing receive the error 500. My log: <IP_ADDRESS> - - [17/Jan/2023:10:40:05 +0000] "POST /livewire/message/app.filament.pages.settings.notification-page HTTP/1.1" 500 6628 "http://<IP_ADDRESS>:8080/admin/notifications" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"

Just find error!!! Please change your (documentation: https://docs.speedtest-tracker.dev/settings/notifications/telegram) here and in telegram Chat ID must be -1234567890

That pretty much depends on your chat, If the chat is a group, the chat id is negative. If it is a single person, then positive.
Right now mine is configured without dash and works perfect, my Chat ID is for single person.

Yes its a group id, so they have to add it this difference in their documentation.

I can confirm that it only works for Individual Users, not Groups (with a negative sign).
I would appreciate it if it worked for groups too.
Tip: It is important to always save first and then request the test message.

@alexjustesen This should be closed, due to new 11.1 version fixes it!

Consider it done


No Ambience Sound Muffling under water

When under water, most sounds are muffled, but background ambient sounds from the mod itself still play at 100%, which really breaks immersion.
Would be cool if those could alos be muffled under water by default.

Hello! Yes, I've noticed that too, but it doesn't really stand out against the not-so-best sound mastering by default. I see that you need something similar and we (I) would be happy to get an improved version of the default sound configuration.

Hello! Yes, I've noticed that too, but it doesn't really stand out against the not-so-best sound mastering by default. I see that you need something similar and we (I) would be happy to get an improved version of the default sound configuration.

@Leolele99.
Hmm, as far as I understand it, it happens because the modification does not properly handle the absorption of the sound wave by water. And the effect of sound in water is created by taking into account the water as a solid block, the same algae impede sound propagation. If I understand a bit more, I will create a separate ticket dedicated to this problem, but for now we can adjust the existing sound processing parameters.
But the general muffling is present, could you highlight the sounds and the environment in which they play, to understand specifically what you do not like.

@Leolele99 Hello again! I fixed the sound processing in the water a bit, probably 1.18 changed the tracing logic, well, or it was originally broken. This will probably improve, if not solve, your experience.
You can find a compiled version with a fix here: https://github.com/HarvelsX/DynamicSurroundingsFabric/actions/runs/1657352401

@Leolele99 Hello again! I fixed the sound processing in the water a bit, probably 1.18 changed the tracing logic, well, or it was originally broken. This will probably improve, if not solve, your experience.
You can find a compiled version with a fix here: https://github.com/HarvelsX/DynamicSurroundingsFabric/actions/runs/1657352401

Thank you so much!
Is there any way possible to also have this in 1.17? I'm not playing 1.18 at all. If you give me some pointers I could also fork it myself and try to reimplement it into 1.17.

@Leolele99, no problem, here's a link to the build: https://github.com/HarvelsX/DynamicSurroundingsFabric/actions/runs/1657424416

True, it's 1.17.1, not 1.17, but you can still try

Oh, if that build is 1.17.1 compatible already that works for me.

Seems to work, however in the future any effect that makes it even more muted and maybe a nice sound effect for going under water could be added to make it even cooler :D

@Leolele99, there is a parameter soundOcclusion, it defines the coefficient of sound propagation obstruction by the block. The default value is 0.5 for water, but you can increase it to strongly silence sounds in water.
Here is the code that does this:
diff --git a/src/main/resources/assets/minecraft/dsconfigs/blocks.json b/src/main/resources/assets/minecraft/dsconfigs/blocks.json
--- a/src/main/resources/assets/minecraft/dsconfigs/blocks.json	(revision a908f46953c9a674542d45d57ac38417cf10711d)
+++ b/src/main/resources/assets/minecraft/dsconfigs/blocks.json	(date<PHONE_NUMBER>051)
@@ -37,7 +37,8 @@
         "effect": "waterfall",
         "alwaysOn": true
       }
-    ]
+    ],
+    "soundOcclusion": 0.8
   },
   {
     "blocks": [

Are other sounds also muffled?
I'm specifically having problems with some oceans sounds which might originate from another mod too. Perhaps Charmonium.

Are other sounds also muffled? I'm specifically having problems with some oceans sounds which might originate from another mod too. Perhaps Charmonium.
It seems that the audio signal in the Master and Music channels is not processed by ducking. I don't think this is a good solution, but you can try to assign these sounds to the Master channel in the sounds configuration at the moment. I will consider it, thanks for the comment.


gpaste: 3.18.2 -> 3.18.3

Is the failed build related to the PR in any way?

The job is failing for a different reason.


Drafting New Blog Page: ZBCE Ecosystem

The idea behind this page will be to outline all the features of ZBCE, which will help provide a big picture view of the entire system and also explain the relations on how the ZBCE  addresses its mission statement.
Possible Sections Include:

Physical Architecture, explaining all layers of our ecosystem. Perception, network, Middleware, and application layers
ZotBins 3 Pillars Approach, explaining our focus in 3 areas to address the  ZBCE mission. Education, Technology, and Operations & Manufacturer Interventions.
Use Cases

Drafting Location: https://boosthub.io/shared/a042d694-5b31-4f2e-bfdf-576812363bed

Added section to about page.


NLog support

Hello! Thanks for the library. Is it planned to support NLog? I have the project without Microsoft.Extensions.Logging.ILogger.

Thanks @techiedesu for enjoying the library! You should be able to use an adapter like https://github.com/NLog/NLog.Extensions.Logging to NLog Logger instance to a Microsoft ILogger.


Looks like a few adds I was waiting for..

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Merge branch-22.04 into branch-22.06

Addresses merge conflict seen in PR ( https://github.com/rapidsai/cucim/pull/257 ).

I added a do not merge label since this needs a manual merge, but we're still waiting for CI to finish.

Sounds good. Actually needed to push an update (now done). So that works out. Anyways should be ready to go once CI completes.


web_login?code=XXXX

When using the web_login in the examples and my app info in the config file it "works" or at least a part of it is. When clicking the "login" button  i get redirected back to http://www.mcww.com/web_login?code=XXXXX  and nothing more happens, what am i doing wrong?
Info

php: 5.6.24
composer: (latest)
facebook php sdk: 5.2.0
codeigniter: 3.0.6
codeigniter session: on

bump!?

@mgjuhler Have you made sure you have sessions configured correctly in CI? It's required for the web login flow to work correctly.
If you do have sessions configured. Do you have any errors in your server logs?

session is working, i am using it for my normal login system.
here is the log from codeigniter:
`ERROR - 15/08/2016 19:45:17 --> [FACEBOOK PHP SDK] code: 0 | message: Cross-site request forgery validation failed. Required param "state" missing from persistent data.
ERROR - 15/08/2016 19:45:17 --> [FACEBOOK PHP SDK] code: 0 | message: Cross-site request forgery validation failed. Required param "state" missing from persistent data.`

ops... sorry for closing

The issue has to do with the session not working properly. I don't know exactly what it could be, it most likely depends on how you have your sessions setup.
Maybe this post can help you? http://stackoverflow.com/a/34361172


update jpeg to 9c-p0

I've followed this guide
step by step carefully. Yes

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/khourig/hunter/builds/24024442
https://travis-ci.org/khourig/hunter/builds/523198777

Testing:

https://ci.appveyor.com/project/ingenue/hunter/builds/24025589
https://travis-ci.org/ingenue/hunter/builds/523217658?utm_source=github_status&utm_medium=notification

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/builds/24026237
https://travis-ci.org/ingenue/hunter/builds/523227314?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.23.158


feat(Songmu/ecschedule): support windows

Songmu/ecschedule has started to distribute Windows binaries from version 0.12.0. (See: Release v0.12.0 · Songmu/ecschedule ) I propose a change to make it possible to install version 0.12.0 or later on Windows, even via aqua.
The changes in this PR are as follows

Include windows in supported_envs for v0.12.0 and later
Add v0.11.4 to pkg.yaml so that v0.7.0 through v0.11.4 can be tested.
Added semver(">= 0.3.2") to supported_envs to explicitly exclude windows support.

Check List

[x] Read CONTRIBUTING.md

[x] Read OSS Contribution Guide

[x] All commits are signed

This repository enables Require signed commits, so all commits must be signed

[x] Avoid force push
[x] Do only one thing in one Pull Request

Thank you for your contribution!

v4.202.1 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.202.1


Jefhar/clarify execption messages

This PR clarifies three Exception messages, changing the ambiguous 'This' to a concrete class name.
It also includes whitespace fixes that my IDE automatically includes.

Will merge and release once other PR is tested. Good spot. Thanks.


Improve collision filters

Currently collision filters work as they do in Box2D, which uses a bitwise implementation which supposedly should give good performance. Here is a good explanation.
This comes with some downsides:

Limits the number of categories to just 32
Not a particularly standard JavaScript style of implementation
It's pretty confusing

I also doubt the approach gives much of a performance boost compared to other possible nicer alternatives. I still need to decide on exactly what though. Changing the implementation is mostly a matter of changing:

Matter.Body.create
Matter.Body.nextGroup and Matter.Body.nextCategory
Matter.Detector.canCollide

Back compatibility is important here, so the old scheme should be supported but deprecated.
If anyone has any thoughts let me know.

What would be the downside to using the already available collisionFilter.group and adding a field collisionFilter.collidesWith that can contain an array of collision groups the body collides with? This seems like a straightforward easy-to-use feature.

TL;DR:
I got wondering about different possible approaches and made something up after a bit of musing. Here it is FWIW
Alrighty
This is what I can come up with as a goal for 'capability' and performance: For a simulation of n objects, there exists a configuration such that every unique object pair can arbitrarily be set to collide or not collide. Ideally the storage and evaluation of the configuration should perform much better than O(n^2) in average cases though.
If the category/mask system is generalized to any number of categories (not just 32), then hypothetically that is a capability solution. At the finest grain of control each object can have its own category, and then arbitrary masks control all possible pairs of collisions. Of course in most situations objects will share categories when it makes sense, but it just goes to illustrate. The problem is you have to be careful how you scale beyond 32 categories or you could pay in performance (the bitwise & is really fast, and it's no wonder it was chosen in box2d).
The nice thing about the group system is that you can say "Ok, we have this nice category system as a fallback, but this set of object I want to ALWAYS or NEVER collide NO MATTER WHAT." If the category mask system is the rules, the group system is the exceptions. If we had limitless categories, then in principle this wouldn't be necessary, but it is in fact still very convenient and very performant (just number equivalence). The nice thing about the group system is that you can have any number of distinct groups (e.g. a billion robots that don't self collide (groups) but collide with all others (category/mask)). The downside of the group system is that you can only set one group. You can't make BodyA ALWAYS collide with BodyB that ALWAYS collides with BodyC that NEVER collides with BodyA, without resorting to categories and masks.
So I'm no computer scientist, but just spitballing ideas, here's my two cents of an approach.
(If I'm not mistaken this would require new interface for the programmer. The old interface might be able to ~retrofit~ forwardfit(?) onto this new idea, but might not magically grant all the full capability. Reaping the benefits might require the programmer to adopt new interface, although the old interface would still work.)
I think the two layer approach is helpful. The base rules (categories and masks) and then overriding exceptions (groups). However I'm going to break away from the 'categories', 'masks', and 'groups' terminology now to avoid confusion in describing this different approach.
If I'm not mistaken, we should be able to achieve full configurability with 3 layers:

implicitly, all objects collide
except when explicitly specified otherwise, and they will not collide
except when finally specified with the ultimate override, and they do collide after all

It can also be done the other way around:

implicitly, all objects pass through one another
except when explicitly specified otherwise, and they will collide
except when finally specified with the ultimate override, and they pass through one another after all

I think the former makes the most sense though obviously, since it makes sense to collide by default. No matter whether two particular objects collide or do not collide, you can configure one of the overrides to ensure that object pair collides as desired or not.
Now the only question is how to implement the two 'explicit override layers'. There are probably multiple different approaches, but here is my random take on it.
Similar to the category bit or the group number, each body can be given a number to identify and/or classify it. There is no restriction on whether objects can share the same number for this purpose (effectively acting as a classifier instead of an identifier). Let's call this number the collision-class (as a choice of word distinct from 'group' or 'category').
So every body has a collision-class (or not). Every body implicitly collides. Now, how does an object know which other objects it should NOT collide (the first override layer)?
We extend upon the bitset. Bits are efficient for storage, so it works for me. But how do we get past 32 (or is it 64) bits? You just make an array of bitsets. Then, every collision-class (which is a positive integer number) literally corresponds to a single bit in the bitset. If my bitsets are one byte (instead of 32 bits) long, I might have a no-collide filter of [0001, 0000, 0011, 0000, 0100]. Then if I intersect a body with a collision-class of 11, I access filter[11/4 | 0] and then bitwise & the result just like the category check 0011 & 0010 !== 0. In this case, our objects do not collide because of the no-collide override filter. The 0010 is derived from 11 by mapping 11 % 4 (which is 3) to 0010 assuming a little-endian bitset. The array is random access, which means it should be very good performance. The cost is lots of storage if you have a very large number of collision-classes. This is a weakness, but not a fatal flaw. Bits are implicitly dense. The arrays could be lazily generated (you can have thousands of collision-classes, but never make an array longer than necessary for it's greatest set bit). And lastly, objects/maps could serve as an excellent replacement whenever the configuration is sparse. e.g. instead of [0001, 0000, 0011, 0000, 0100], only store {'0':'0001', '2':'0011', '4':'0100'}
And now that we know which collision-classes are filtered to not collide by this override configuration, we implement the final override configuration layer in the same way (which objects should collide with which collision classes no matter what). i.e. the explicit layers 2 and 3 are implemented in the same way.
There are probably a number of flaws with the whole idea but this was one of those things that infects your brain and you just gotta come up with something. So there we go. I'm now exorcised of the collision-filter demon.
As far as confusion is concerned, I think the implementation is really tedious to explain, but the interface might be really simple. Everything implicitly collides, except when you tell them not to. In case you want to preserve a no-collide rule but add an exception to even that, you can do so.

Seconding. The way its setup is really confusing, especially the bitmasks, and is impossible to figure out from the docs. I had to study the demos to get it working.


cli: ANSI colour for windows 10, and easier utf-8 setup

Relates to #703.
Overview
IOHK logging framework uses ANSI control codes for colouring its output (instead of the Win32-specific method). Windows console does not interpret ANSI colour codes unless told to (even then, it's only supported under win 10).

Enables ANSI colour at startup (System.Console.ANSI).
There is a better way of setting UTF-8 on Windows - code-page package.

bors r+


redesign of TensorView

Discussion items:

do we need to support views with value_type != storage::value_type, i.e. TensorView<T,Range,Storage> where T != Storage::value_type?

proposed change: TensorView<T,Range,Storage> -> TensorView<T,Range,StorageIterator> (or, perhaps TensorView<T,StorageIterator,Range>)

rationale for item 2 to follow.
p.s. To explore the latter I re-engineered TensorView on my fork (evaleev/BTAS).

Closing #68 without merging in the proposed (and implemented) changes (for the posterity see branch view_using_storageiterator)
the rationale for sticking with View< ... Storage> in favor of View< ... StorageIterator>:

type system (i.e. getting from StorageIterator to StorageConstIterator is impossible without doing non-portable things)
efficiency (StorageIterator does not provide same level of insight that Storage does to be able to optimize things)


x/pkgsite: package removal request for github.com/ipfs/go-ipfs-cmds v1 and v2

github.com/ipfs/go-ipfs-cmds has three retracted versions (go.mod):

v1.0.22
v2.0.1+incompatible
v2.0.2+incompatible

The package is still at v0.x.x and we were unable to retract v1 and v2 versions correctly (created before go.mod existed), which leads to ecosystem issues (https://github.com/ipfs/go-ipfs-cmds/pull/254#issuecomment-2288731892).
Is it possible to manually remove these three versions from pkgsite and mark v0 one as the latest?
(We don't have v1 and v2 tags in git repository)
Instead of
$ GOPROXY=https://proxy.golang.org GO111MODULE=on go list -m -versions github.com/ipfs/go-ipfs-cmds
github.com/ipfs/go-ipfs-cmds v0.0.1 v0.0.2 v0.0.3 v0.0.4 v0.0.5 v0.0.6 v0.0.7 v0.0.8 v0.0.9 v0.0.10 v0.1.0 v0.1.1 v0.1.2 v0.1.3 v0.1.4 v0.2.0 v0.2.1 v0.2.2 v0.2.9 v0.3.0 v0.4.0 v0.5.0 v0.6.0 v0.7.0 v0.8.0 v0.8.1 v0.8.2 v0.9.0 v0.10.0 v0.10.1 v0.10.2 v0.11.0 v0.12.0 v0.13.0 v1.0.22 v2.0.1+incompatible

We want:
$ GOPROXY=direct GO111MODULE=on go list -m -versions github.com/ipfs/go-ipfs-cmds
github.com/ipfs/go-ipfs-cmds v0.0.1 v0.0.2 v0.0.3 v0.0.4 v0.0.5 v0.0.6 v0.0.7 v0.0.8 v0.0.9 v0.0.10 v0.1.0 v0.1.1 v0.1.2 v0.1.3 v0.1.4 v0.2.0 v0.2.1 v0.2.2 v0.2.9 v0.3.0 v0.4.0 v0.5.0 v0.6.0 v0.7.0 v0.8.0 v0.8.1 v0.8.2 v0.9.0 v0.10.0 v0.10.1 v0.10.2 v0.11.0 v0.12.0 v0.13.0

removal only hides the documentation, it does not affect the versions the go command sees.

retractions do work for v2+incompatible, they just have to be on the highest v1 tag.
pkgsite can only hide entire modules, as you still want to use the other versions, i don't think a removal request is right.

@seankhliao thank you, but we did not see retractions of v2+incompatible to be working. Would appreciate some elaboration on what works and what does not, or some hint what we are doing wrong.
We DO have retractions in v0.13.0 (go.mod here) but they are not applied when GOPROXY=https://proxy.golang.org is used. Same with https://pkg.go.dev/github.com/ipfs/go-ipfs-cmds:

Are you saying that v0 updates are ignored by https://proxy.golang.org and the only way to fix this is if we publish v1?
Why retraction of v2+incompatible would work for v1 and not for v0? Is this limitation of proxy.golang.org or  go tooling itself?

your retraction has to be at v1.0.23 or above (highest version regardless of retraction), the retraction can include itself.


Update tested AGP versions

from 8.0.0 to 8.0.2
from 8.1.0-beta01 to 8.1.0-beta03
introducing 8.2.0-alpha04

@bot-gradle test AFT AST APT

I've triggered the following builds for you:

AllFunctionalTestsPullRequestFeedback build
AllSmokeTestsPullRequestFeedback build
AllPerformanceTestsReadyForRelease build

@bot-gradle test and merge

I've triggered a build for you.


Add third point to change size RectangleShape2D in two axis

This fixes #22240

Thanks!

@qarmin Great idea.  Makes life easier.
Wasn't getting SHIFT to lock the ratio (maybe doing something wront), but CTRL seems to at least be following grid snapping.


[java/agent] Make agent compatible with C.

Summary: We would like to build the java agent for ARM as well as x86. We could make a fully-featured musl c++ toolchain. However, that's a lot of work and its much easier to just build musl libc with bazel and statically link it. This won't work with C++ though, because we wont have a compatible libc++. The java agent doesn't really make use of many c++ features beyond std::mutex and std::string, which are easily replaced with C versions. This PR converts the java agent to be C compatible, removing its uses of c++ features.
Relevant Issues: #891
Type of change: /kind cleanup
Test Plan: Tested that java symbols still show up in the flamegraph with this new version of the agent.

Lint will pass after #1170 lands


Adding support for Zend 3

Adding support for Zend 3 (b/c with ZF2)

See @grahamcampbell's note on #32

@jeremeamia @grahamcampbell Good point.


Rust code loses all syntax highlighting if there is a trait declaration in there

Moved from https://github.com/jashkenas/docco/issues/338

An entire block of Rust code (between two comments) will lose all its syntax highlighting if there is a single trait block with a "supertrait" declaration in there. That is, even the part of the code that's correctly highlighted usually will be broken once more code is added to the end of the file. Yeah, that doesn't make much sense, but what can I say^^

The following two files demonstrate the issue:

hljs.highlight('rs', 'fn sqr(i: i32) { i * i }');
> Object {r: 3, value: "<span class="hljs-keyw… i32) { i * i }", language: "rs", top: Object}

hljs.highlight('rs', 'fn sqr(i: i32) { i * i }\ntrait Minimum : Copy {}');
> Object {r: 0, value: "fn sqr(i: i32) { i * i }↵trait Minimum : Copy {}"}

When running docco, I would expect both of these files to get rendered with syntax highlighting. The first file works as expected. The second one lacks any form of syntax highlighting, even for its first line. If I remove the " : Copy", it's all working.

Thanks for reporting this!


10/23/2018 17:57 : Create Pull Request for branch master -> prTesting1_2018102317

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestCon1.md
:white_check_mark:Succeeded

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


[rGuiStyler] Support for substepping font rasterization

Currently rGuiStyler has issues rasterizing pixel fonts correctly, the rasterization grid does not always match evenly with the provided font file's vectorized pixel grid.
As observed, a font designed for 16pt size was almost a fit at 13pt but wasn't a perfect match so it was rasterized with subpixels:

The same font somehow seems to be rasterized correctly at 38pt but not a multiple of that like 19pt.. Which means that 38 is almost perfect but likely not exactly perfect. I could be wrong in that assumption.
A potential solution is more fine grained control over substepping the font pt, but unsure how this would look once applied at a different font pt in the actual gui.

Here's 4 public domain pixel fonts that I've observed this issue with.
fonts.zip

https://github.com/raysan5/raylib/issues/3766
Proof of concept documented in this issue

As discussed, this issue could be related to how raylib considers font size data (as points vs pixels). Other engines seem to be able to load font data correctly at specific size. It needs to be carefully investigated in raylib side.


How to import/require/src?

I am not able to start going with this module, i tried everything to import it but nothing works:
i run npm install leader-line
After i try to import it and getting errors from every angle, i am using Vue framework and not sure what i am missing here:
import LeaderLine from '../../node_modules/leader-line/leader-line.min.js'
Error: node_modules_leader_line_leader_line_min_js__WEBPACK_IMPORTED_MODULE_1_.LeaderLine is not a constructor
import { LeaderLine } from '../../node_modules/leader-line/leader-line.min.js';
Error: Uncaught TypeError: LeaderLine is not a constructor

Error:Uncaught ReferenceError: LeaderLine is not defined

So i got this boy up and running with Vue, you just have to add at the leader-line.min.js a line at the bottom of the file:
module.exports = LeaderLine;
then run:
let LeaderLine = require('LeaderLine');
new LeaderLine (this.$refs.pointA,this.$refs.pointB) :)

Hi @xeroxstar, thank you for the comment.
The best and easy way to import it is using Webpack and skeleton-loader.
https://github.com/anseki/leader-line/issues/8#issuecomment-370147614
At least, you should use export default instead of module.exports in your code because that is CommonJS that might be not supported in some environment.

Also, if you added the <script> element, you don't have to import that because it was already loaded.
This is the JavaScript specification.

Thanks, by the way, this is an amazing module.

:smile:


Start training from scratch on a new data set, without calling pre-training weights.

Hello, thank you very much for your code.
I want to start from scratch on the new data set without calling the pre-training weights.
May I ask what operation is required?
Is it ok to modify the data set address directly in examples/imagenet/main.py?

I'm also interested in fine tuning this network. I ran the main.py in examples/imagenet on my own dataset, and it starts training, but loss is not decreasing.


dressing.nvim input does not start in insert mode

When using dressing.nvim alongside js-i18n.nvim, I noticed that the input does not start in insert mode as expected. This disrupts the workflow as users have to manually switch to insert mode each time a prompt appears.

It was an issue with my environment, so closing it.


Upgraded to Hadoop 2.3.0-cdh5.1.5 and cleaned up the Kerberos authentication code.

LGTM

LGTM

FYI, this is not ready yet. I left it running over the weekend on my test cluster and the token did not get auto-renewed correctly as I expected. I read the Hadoop source and I think I know what's going on. I added some more code in my latest commit to address the issue. We'll see how it goes over the next few days...

LGTM, you can merge after testing is done.

Yeah. I'll let it bake for 2-3 days. Then if there aren't any problems, I'll squash and merge.
Thanks for the review!

This has been running fine in my test cluster for several days.
I squashed and merged.


Don't round monetary amounts in emails

Describe the bug
When I get emailed about expenses, the subject features a rounded amount whilst the body features the exact amount.
To Reproduce
Submit an expense and get an email about it, e.g. when it is repaid:

Expected behavior
Always use the exact amount to make it less confusing. It makes it easier to find "that £122.75 expense" and leads to precision in accounts.
Screenshots
See above
Desktop (please complete the following information):
N/A - email
Smartphone (please complete the following information):
N/A - email
Additional context
N/A

@adamchainz good point

But how to make it not stale?

@adamchainz commenting on it like you did :-)
Stale is just for us about surfacing issues. We'll try to tackle this one.

A $50 bounty was attached to this issue. Anyone submitting a Pull Request will be rewarded with $50 when the Pull Request is reviewed, accepted and merged. More info
This bounty is currently reserved to participants of the OSCA (Open Source Africa) event. If not completed there, it will be later open to everyone.

am from osca ph and I'll like to work on this

I'm from osca and i'm working on this already

https://github.com/opencollective/opencollective-api/pull/2364

@Gbahdeyboh Thank you for the PR in https://github.com/opencollective/opencollective-api/pull/2392 Can you share some screenshots of the emails?

Current guidelines state: https://blog.opencollective.com/scaling-up-our-bounty-program/ $100 minimum

@znarf thanks for the clarification snarf 🚀

:trophy: This issue has been resolved in https://github.com/opencollective/opencollective-api/pull/2392
Because @jeffin143 made the effort of testing and providing screenshots on the PR, we've decided to give him a bounty of the same amount.
@Gbahdeyboh and @jeffin143, to claim the $50 bounties, you can either:

Submit an invoice to https://opencollective.com/engineering/expenses/new (please mention the issue number in the expense's title)
Or ask for an Open Collective gift card of the same value (to donate to other collectives)

For more info about the bounty process and how to format your invoice, please read https://docs.opencollective.com/help/developers/bounties
If you have any feedback on how we could improve the bounty process or how to better onboard new developers please share it with us, we're always eager to improve :slightly_smiling_face:


Updated Rubio district offices

Tampa changed locations + phone, cleaned up some other unlisted fax numbers for the rest of the locations.
From: https://www.rubio.senate.gov/public/index.cfm/contact

Thanks!


SyntaxError: Unexpected token 'const' in strict mode.

Which version of PhantomJS are you using? Tip: run phantomjs --version.
2.1.1

What steps will reproduce the problem?

create a test page with the following javascript

'use strict';

const a = 1;

Which operating system are you using?
Arch Linux

Did you use binary PhantomJS or did you compile it from source?
Installed from the arch repository from community/phantomjs 2.1.1-3

Please provide any additional information below.
All major browsers (even ie11) currently support the const keyword in strict mode. It should be allowed even if it only duplicates the functionality of var and full const semantics aren't present.

const.html
<!DOCTYPE html>
<html>
<head></head>
<body style="white-space: pre-wrap">
<script> window.onerror = console.log.bind(console); </script>
<script>
/* jshint globalstrict: false */
/* jshint esnext: true */
'use strict';
function x() {
    const a = 1;
    return a === 1;
}
var result = 'failure';

try {
    result = x() ? 'success' : 'failure';
} catch (ex) { }
console.log(result);
</script>
</body>
</html>

testconst.js
/* jshint esnext: true */
/* jshint node: true */// almost the same right?
/* globals phantom */
const system = require('system');
var testStatus = -1;

console.log('opening page');
const page = require('webpage').create();
page.onConsoleMessage = function(msg) {
    console.log('TEST:' + msg);
    testStatus = msg === 'success' ? 0 : -1;
};
page.onResourceError = page.onError = function(msg, trace) {
    console.log('ERROR:' + msg);
    console.error(trace);
};
page.open('const.html', function(status) {
    console.log("Page load status: " + status);
    page.render('const.png');
    console.log('return ' + testStatus);

    phantom.exit(testStatus);
});

phantomjs ./testconst.js

Workaround for karma.js: (place inside your karma.conf's config.set() call)
        ...,
        plugins: [
            'karma-jasmine',
            'karma-phantomjs-launcher-nonet',
            'karma-requirejs',
            'karma-ng-html2js-preprocessor',
            'karma-spec-reporter',
            {'preprocessor:varconst': ['factory', function() {
                return function(content, file, done) {
                    var count = 0,
                        constExpr = /(^|\s)const(\s|$)/g;
                    if (/(^|\s)['"]use strict['"];?(\s|$)/.test(content)) {
                        content.replace(constExpr, function() {
                            count++;
                        });
                        content = content.replace(constExpr, '$1var$2');
                        if (count > 0) {
                            console.log(file.path,
                                'Replaced ' + count + ' const keywords with var');
                            console.log(content);
                        }
                    }
                    done(null, content);
                };
            }]}
        ],
        preprocessors: {
            'ng/**/*.html': 'ng-html2js',
            '**/*.js': 'varconst'
        },...

Looks like it's a webkit bug. It affects Safari 9 on OSX and iOS as well.

I am getting the same issue when trying to run Karma tests (phantomjs browser) with Angular 2 (RC6):
The following tests fails:
"use strict";
const testing_1 = require('@angular/core/testing');

With the error:
Unexpected token 'const'
Any advise how to fix it?

Remove const or use an es6 transpiler if you want safari 9 support :(
Apparently safari 10 is supposed to support this.

Could you please try again with 2.5 binary? Thanks!

Bump.
😕 what 2.5 binary?

Unfortunately safari has the same issue, so we just abandoned plans to use const until we get a transpiler running.


[express plugin] automatic metrics instrumentation

Describe the solution you'd like
We can draw inspiration from @yuriatgoogle's https://dev.to/yuriatgoogle/custom-metrics-in-node-js-with-opentelemetry-and-prometheus-3dbd to expose the "golden signals"

Hello, is there any progress?

The metrics spec, JavaScript API, and SDK are under active development. I'd believe we need to wait for a (generally) stable metrics API to start the work on third-party instrumentation. (The work is being tracked at https://github.com/open-telemetry/opentelemetry-js/issues/2480 and https://github.com/open-telemetry/opentelemetry-js/issues/2574)

@legendecas as both the issues linked are now closed. Can we expect any movement on the metrics inside the express plugin?

@anikdas if you are using the http instrumentation, the instrumentation should start reporting HTTP metrics for you.
See more at https://github.com/open-telemetry/opentelemetry-js/blob/main/experimental/packages/opentelemetry-instrumentation-http/src/http.ts#L78.

Hey @legendecas I've tried running metrics locally with:
OTEL_METRICS_EXPORTER=console

and I don't see anything showing in the console. I also don't see anything received by my collector in production.
On the other hand traces are working fine for me from the same @opentelemetry/instrumentation-http package. Is there a flag that I could have missed to ensure those histogram metrics are being captured?
Edit: just discovered this issue, is it actually not possible to configure the metrics entirely via the command line? open-telemetry/opentelemetry-js#3193

Yes, automatic setup of metrics exporters via env vars this is not implemented yet. #3193 tracks implementation of that.

Closing this issue as it was the request to emit metrics for express, which the @opentelemetry/instrumentation-http package now does.


Band updateBand.features incomplete

Band updateBand.features incomplete it.
Also should implement the controller method an the dao method.

solved in this rev 20b6868


[WIP][Draft] All the protocol docs

Summary

Human Summary

AI Summary
reviewpad:summary
Issue

#{ISSUE_NUMBER}

Type of change
Select one or more:

[ ] New feature, functionality or library
[ ] Bug fix
[ ] Code health or cleanup
[ ] Documentation
[ ] Other (specify)

Testing

[ ] Run all unit tests: make go_develop_and_test
[ ] Run E2E tests locally: make test_e2e
[ ] Run E2E tests on DevNet: Add the devnet-test-e2e label to the PR. This is VERY expensive, only do it after all the reviews are complete.

Sanity Checklist

[ ] I have tested my changes using the available tooling
[ ] I have performed a self-review of my own code
[ ] I have commented my code, updated documentation and left TODOs throughout the codebase

Outdated and no longer relevant.


Clarification on MSIdentity reporting and Azure AD group values via Graph

Under the "Discover the current writeback settings for existing Microsoft 365 groups" section the documentation lists 3 values for the WritebackConfiguration when pulled via Graph--True, False, null. With both True and null leading to the group being written back.
It also gives the MSIdentity module as an alternative. If we run the Get-MsIdGroupWritebackConfiguration it has 4 values for the WriteBackEnabled--True, False, NotSet, and n/a.
n/a seems to be for groups whose sourceofauthority is On-Premise, which makes sense.
NotSet seems to be the result for cloud-based Security groups, which are stated to not write back by default and must be explicitly enabled.
Except that if we verify through Graph we show that the same groups with NotSet are reporting with a null value for WriteBackConfiguration. Which per earlier documentation would mean they will write back.
Is there an additional qualifier being applied besides the writebackconfiguration value that would block them from being written back? Or would all of them be written back per the null value?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 0ef5e848-ca7a-8924-8da2-73163a489e5b
Version Independent ID: ad118082-f4bb-624c-b541-942ba235f370
Content: Azure AD Connect: Group writeback - Microsoft Entra
Content Source: articles/active-directory/hybrid/how-to-connect-group-writeback-v2.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@justinmontgomeryCF
Thanks for your feedback! We will investigate and update as appropriate.

Hi @justinmontgomeryCF
Thank you for your feedback!
I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows.
[Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1)
They may be able to provide more insight into the behavior of these groups and help troubleshoot any issues you may be experiencing.
Thank you for your time and patience throughout this issue.

What service would I open it under? None of the Azure services presented seem applicable.
The article would still need edits, because it presents a contradiction between:
    If isEnabled is null or true, the group will be written back.

    If isEnabled is false, the group won't be written back.

and
Azure AD security groups are not automatically written back. They must each be enabled for writeback.

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

Thank you for your issue submission. Unfortunately, this appears to be a support issue. Issues in this repo are for documentation issues. You can try one of the following links for additional help.
Microsoft Support: https://support.microsoft.com/
Azure AD forums: https://social.technet.microsoft.com/Forums/en-US/home?forum=windowsazureaditpro
Stackoverflow: https://stackoverflow.com/
#please-close


updated data url and conform (Dodge County, WI)

Re-run this please

Good times: looks like changing the URL scheme to http from https results in the server responding with HTML rather than JSON, which breaks this source. That's a shame, since the https endpoint's cert appears to be invalid, but the warnings generated don't appear to break machine.


Default FelixConfiguration RouteTableRange when using AWS CNI

Cherry-pick to 1.20 for open source.

Move GKE ROUTETABLERANGE to be set like for AWS
Move FelixConfig to watch for all variants

Description

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

This is a pick of #1447


(formatting): Indentation on generated functions using  swagger-tanstack-query

What is the problem this feature would solve?
Super minor, everyone has different lint choices as well so possible wont-fix.
using @kubb/swagger-tanstack-query
functions are indented by 4 spaces.

What is the feature you are proposing to solve the problem?
Generated code would not have a starting indentation.

What alternatives have you considered?
No response

ignore, i'll just lint locally after generation...


Show subtype probabilities when plotting RF models

          I think this is close. I am of the opinion that we should return to the RF visualizations at a later time. Since we expect that model returns probabilities, I think we should show people probabilities instead of treating the output score the same way we treat the kTSP models. I would be satisfied for now if we skipped creating confidence scores for RF models and removing all RF plotting from the notebook.

Originally posted by @jaclyn-taroni in https://github.com/AlexsLemonade/medulloblastoma-classifier/pull/50#pullrequestreview-2410653264
In reference to RF panels in analysis_notebooks/pseudobulk_and_single_cells.Rmd

I'm going to call this closed.


Object destructuring inside the rest parameter

Babel is unable to parse ({ x, ...{ y, z } } = o). It's valid according to the spec.
Input Code / Babylon Configuration

babylon.parseExpression("{ x, ...{y, z} } = o", {"plugins":["objectRestSpread"]});

Expected Behavior
It should parse correctly to be transformed into a functionally equivalent code of the following:
x = o.x
rest = _objectWithoutProperties(o, ["x"])
y = rest.y
z = rest.z

Current Behavior

This error is thrown
SyntaxError: Invalid left-hand side in rest property (1:8)`

Your Environment

software
version

Babylon
code on master (#0e12f56)

node
6.10.3

npm
3.10.10

Operating System
Ubuntu 16.04

Hey @peey! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.
If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.


use - for padding

this will append - until the link is 50 characters long
fixes #7
cc @joehand @mafintosh

nice, we might wanna add a test that encodes 32 random bytes

published as 2.0.2


How to have CICD check as part of PR

How can I have the CICD run as part of the checks that need to be run BEFORE a PR is committed the the destination branch?
E.g. have someBugFix branch and I want to pull it into 'feature/someNewFeaturebranch.  How can I make sure that the PR does not get committed to thefeature/someNewFeature` branch with first passing the CICD action?
You show checks in your Branching strategies for your AL-Go for GitHub repo post but can't find where to have them happen.  What am I missing.

Normally, we do not assume that you are using PRs against a feature branch.
We assume you are using PRs from the feature branch into main.
When working in the feature branches, you typically push to the feature branch and CI/CD will run then.
If you want to have double PRs (against feature branch and then again against main), you should be able to include feature branch in CICDPullRequestBranches setting to also run PR builds there.

Okay so I have done a "Create Release" action that used a PR to update the version number in Main.  The PR does not include the CICD check BEFORE the final push to Main.  Is it because it is from an Action?  Should any PR into Main have a  requirement to committed that CICD completes successfully?

The CICD does kick off after the commit though.

This is because the default token used when running workflows, cannot kick off another workflow. This is by design: https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#triggering-a-workflow-from-a-workflow
In v3.2 there is a checkbox in the parameter on Create Release (use GhTokenWorkflow) - using that will work.


Add oimo and cannon as peer dependencies of BabylonJS

And include them, if they exist, so we wouldn't need to set the window.OIMO or window.CANNON object

https://github.com/BabylonJS/Babylon.js/pull/2875  solves

Documentation needs to be updated

See #2641 :)

I was thinking about the es6-imports documentation . but this one as well! ;)


How to enable logging for just "my" module?

I'm looking for a way to limit the logging to just what my module(s) issue. I know about the possibility to set the log-level per module, but this doesn't help if the number of crates changes rapidly. For instance it my module is on TRACE I get a lot of TRACE/DEBUG messages (unwanted) from other modules.
2020-11-04T19:44:47.127440+01:00 hyper::client | TRACE : handshake complete, spawning background dispatcher task
2020-11-04T19:44:47.127633+01:00 want       | TRACE : signal: Want
2020-11-04T19:44:47.127725+01:00 want       | TRACE : signal found waiting giver, notifying
2020-11-04T19:44:47.127829+01:00 hyper::proto::h1::conn | TRACE : flushed({role=client}): State { reading: Init, writing: Init, keep_alive: Busy }
2020-11-04T19:44:47.127928+01:00 want       | TRACE : poll_want: taker wants!
2020-11-04T19:44:47.128033+01:00 hyper::client::pool | TRACE : checkout dropped for ("https", www.rust-lang.org)
2020-11-04T19:44:47.128269+01:00 tracing::span | TRACE : encode_headers
2020-11-04T19:44:47.128354+01:00 tracing::span::active | TRACE : -> encode_headers
2020-11-04T19:44:47.128430+01:00 hyper::proto::h1::role | TRACE : Client::encode method=GET, body=None
2020-11-04T19:44:47.128532+01:00 tracing::span::active | TRACE : <- encode_headers
2020-11-04T19:44:47.128607+01:00 tracing::span | TRACE : -- encode_headers
2020-11-04T19:44:47.128730+01:00 hyper::proto::h1::io | TRACE : detected no usage of vectored write, flattening
2020-11-04T19:44:47.128812+01:00 hyper::proto::h1::io | DEBUG : flushed 56 bytes
2020-11-04T19:44:47.128888+01:00 hyper::proto::h1::conn | TRACE : flushed({role=client}): State { reading: Init, writing: KeepAlive, keep_alive: Busy }
2020-11-04T19:44:47.773254+01:00 hyper::proto::h1::conn | TRACE : Conn::read_head
2020-11-04T19:44:47.773600+01:00 hyper::proto::h1::io | DEBUG : read 8192 bytes
2020-11-04T19:44:47.773740+01:00 tracing::span | TRACE : parse_headers
2020-11-04T19:44:47.773854+01:00 tracing::span::active | TRACE : -> parse_headers
2020-11-04T19:44:47.773955+01:00 hyper::proto::h1::role | TRACE : Response.parse([Header; 100], [u8; 8192])
2

All these traces above have nothing to do with me, they are just there because I set the log level to TRACE...

@neilyoung can you post your current configuration?
I assume you currently just have a root logger configured and no others in play, basically you would create a new logger in the configuration under the name "::" that is set at the appropriate log level and set the root logger to Off or some other such appropriate level.

True. Using root. Thanks. Will try

@neilyoung please post result you came up with,

#[ctor]
fn init() {
  let file_path = "C:\\j2534-http\\diag-logs.txt";
  let file_logger = log4rs::append::file::FileAppender::builder()
    .encoder(Box::new(log4rs::encode::pattern::PatternEncoder::new("[{d}] {l}: {m}\n")))
    .build(file_path)
    .unwrap();
  let config = log4rs::config::Config::builder()
    .appender(log4rs::config::Appender::builder().build("app::diag", Box::new(file_logger)))
    .logger(log4rs::config::Logger::builder().build("app::diag", log::LevelFilter::Trace))
    .build(
      log4rs::config::Root::builder()
        .build(log::LevelFilter::Info)
    )
    .unwrap();
  log4rs::init_config(config).unwrap();
}

@estk I came up with this and from what I can tell it's wrong?

This is the format that logs too much:
#[ctor]
fn init() {
  let file_path = "C:\\j2534-http\\diag-logs.txt";
  let logfile = log4rs::append::file::FileAppender::builder()
        .encoder(Box::new(log4rs::encode::pattern::PatternEncoder::new("[{d}] {l}: {m}\n")))
        .build(file_path)
        .unwrap();
  let config = log4rs::config::Config::builder()
      .appender(log4rs::config::Appender::builder().build("logfile", Box::new(logfile)))
      .build(
        log4rs::config::Root::builder()
          .appender("logfile")
          .build(log::LevelFilter::Trace)
      )
      .unwrap();
  log4rs::init_config(config).unwrap();
}

Well, I don't even recall to have ever dealt with Rust, but found this in a corner of my desk:
Looks, as if I
        let config = Config::builder()
            .appender(Appender::builder().build("stdout", Box::new(stdout)))
            .appender(Appender::builder().build("logfile", Box::new(logfile)))
            // Shut up actix
            .logger(Logger::builder().build("mio::poll", LevelFilter::Error))
            .logger(Logger::builder().build("mio::sys", LevelFilter::Error))
            .logger(Logger::builder().build("actix_web::middleware::logger", LevelFilter::Error))
            .logger(Logger::builder().build("actix_server::worker", LevelFilter::Error))
            .logger(Logger::builder().build("actix_server::builder", LevelFilter::Error))
            .build(
                Root::builder()
                    .appender("stdout")
                    .appender("logfile")
                    .build(level.unwrap()), // Safe, because there will always be a value
            )

Logs I was just preventing annoying others from jabbering...

[2022-02-24T12:50:12.385154500-05:00] TRACE: PassThruOpenRequest { name: "" }
[2022-02-24T12:50:12.402774900-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.403174200-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:12.403328200-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:12.516440-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.516662500-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:12.516772300-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.516875900-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:12.517037400-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.517571-05:00] TRACE: PassThruOpenResponse { retVal: 0, deviceId: 1 }
[2022-02-24T12:50:12.517992100-05:00] TRACE: signal: Closed
[2022-02-24T12:50:12.518240200-05:00] TRACE: PassThruConnectRequest { deviceId: 1, protocolId: 6, flags: 0, baudRate: 500000 }
[2022-02-24T12:50:12.519597700-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.519760700-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:12.519872200-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:12.538801700-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.539004200-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.539481900-05:00] TRACE: PassThruConnectResponse { retVal: 0, channelId: 2 }
[2022-02-24T12:50:12.539953300-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.540452600-05:00] TRACE: signal: Closed
[2022-02-24T12:50:12.546310500-05:00] TRACE: PassThruStartMsgFilterRequest { channelId: 2, filterType: 3, maskMsg: RPC_PASSTHRU_MSG { ProtocolID: 6, RxStatus: 0, TxFlags: 64, Timestamp: 0, DataSize: 4, ExtraDataIndex: 0, Data: [255, 255, 255, 255] }, patternMsg: RPC_PASSTHRU_MSG { ProtocolID: 6, RxStatus: 0, TxFlags: 64, Timestamp: 0, DataSize: 4, ExtraDataIndex: 0, Data: [0, 0, 7, 232] }, flowControlMsg: RPC_PASSTHRU_MSG { ProtocolID: 6, RxStatus: 0, TxFlags: 64, Timestamp: 0, DataSize: 4, ExtraDataIndex: 0, Data: [0, 0, 7, 224] } }
[2022-02-24T12:50:12.548462100-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.548640300-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:12.548841900-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:12.578781800-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.578923-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.586829500-05:00] TRACE: PassThruStartMsgFilterResponse { retVal: 0, filterId: 3 }
[2022-02-24T12:50:12.587534500-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.588399600-05:00] TRACE: signal: Closed
[2022-02-24T12:50:12.596576-05:00] TRACE: PassThruWriteMsgsRequest { channelId: 2, msg: RPC_PASSTHRU_MSG { ProtocolID: 6, RxStatus: 0, TxFlags: 64, Timestamp: 0, DataSize: 7, ExtraDataIndex: 0, Data: [0, 0, 7, 224, 34, 241, 144] }, numMsgsToWrite: 1, timeout: 1000 }
[2022-02-24T12:50:12.602187800-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.602380600-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:12.643654700-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.643795700-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.644972500-05:00] TRACE: PassThruWriteMsgsResponse { retVal: 0, numMsgsWritten: 1 }
[2022-02-24T12:50:12.647062200-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.647791800-05:00] TRACE: signal: Closed
[2022-02-24T12:50:12.751702100-05:00] TRACE: PassThruReadMsgsRequest { channelId: 2, msgProtocolId: 6, numMsgsToRead: 1, timeout: 1000 }
[2022-02-24T12:50:12.753401900-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.753544700-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:12.753632900-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:12.771256100-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.771395300-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.771481700-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:12.771632500-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.771695100-05:00] TRACE: PassThruReadMsgsResponse { retVal: 0, msg: RPC_PASSTHRU_MSG { ProtocolID: 6, RxStatus: 9, TxFlags: 64, Timestamp: 19551756, DataSize: 4, ExtraDataIndex: 0, Data: [0, 0, 7, 224] }, numMsgsRead: 1 }
[2022-02-24T12:50:12.772161500-05:00] TRACE: signal: Closed
[2022-02-24T12:50:12.838725-05:00] TRACE: PassThruReadMsgsRequest { channelId: 2, msgProtocolId: 6, numMsgsToRead: 1, timeout: 1000 }
[2022-02-24T12:50:12.860276200-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.860430300-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:12.871267800-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.871400300-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:12.871462600-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.871549800-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:12.871675600-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.871825700-05:00] TRACE: PassThruReadMsgsResponse { retVal: 0, msg: RPC_PASSTHRU_MSG { ProtocolID: 6, RxStatus: 2, TxFlags: 0, Timestamp: 19565981, DataSize: 4, ExtraDataIndex: 0, Data: [0, 0, 7, 232] }, numMsgsRead: 1 }
[2022-02-24T12:50:12.872325300-05:00] TRACE: signal: Closed
[2022-02-24T12:50:12.970878800-05:00] TRACE: PassThruReadMsgsRequest { channelId: 2, msgProtocolId: 6, numMsgsToRead: 1, timeout: 1000 }
[2022-02-24T12:50:12.972624-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.972753-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:12.972830700-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:12.995907300-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.996042900-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:12.996106500-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.996166900-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:12.996284700-05:00] TRACE: signal: Want
[2022-02-24T12:50:12.996344900-05:00] TRACE: PassThruReadMsgsResponse { retVal: 0, msg: RPC_PASSTHRU_MSG { ProtocolID: 6, RxStatus: 0, TxFlags: 0, Timestamp: 19570753, DataSize: 24, ExtraDataIndex: 24, Data: [0, 0, 7, 232, 98, 241, 144, 51, 86, 87, 67, 53, 55, 66, 85, 88, 75, 77, 49, 52, 57, 52, 48, 55] }, numMsgsRead: 1 }
[2022-02-24T12:50:12.996896100-05:00] TRACE: signal: Closed
[2022-02-24T12:50:13.092551400-05:00] TRACE: PassThruReadMsgsRequest { channelId: 2, msgProtocolId: 6, numMsgsToRead: 1, timeout: 1000 }
[2022-02-24T12:50:13.095884900-05:00] TRACE: signal: Want
[2022-02-24T12:50:13.096068300-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:14.124184300-05:00] TRACE: signal: Want
[2022-02-24T12:50:14.124332100-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:14.124397300-05:00] TRACE: signal: Want
[2022-02-24T12:50:14.124578900-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:14.124868100-05:00] TRACE: signal: Want
[2022-02-24T12:50:14.125040300-05:00] TRACE: PassThruReadMsgsResponse { retVal: 16, msg: RPC_PASSTHRU_MSG { ProtocolID: 0, RxStatus: 0, TxFlags: 0, Timestamp: 0, DataSize: 0, ExtraDataIndex: 0, Data: [] }, numMsgsRead: 0 }
[2022-02-24T12:50:14.125890500-05:00] TRACE: signal: Closed
[2022-02-24T12:50:14.126436500-05:00] TRACE: PassThruReadMsgsRequest { channelId: 2, msgProtocolId: 6, numMsgsToRead: 1, timeout: 1000 }
[2022-02-24T12:50:14.129714400-05:00] TRACE: signal: Want
[2022-02-24T12:50:14.130661800-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:15.148966100-05:00] TRACE: signal: Want
[2022-02-24T12:50:15.149111400-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:15.149173300-05:00] TRACE: signal: Want
[2022-02-24T12:50:15.149232900-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:15.149375300-05:00] TRACE: signal: Want
[2022-02-24T12:50:15.149468200-05:00] TRACE: PassThruReadMsgsResponse { retVal: 16, msg: RPC_PASSTHRU_MSG { ProtocolID: 0, RxStatus: 0, TxFlags: 0, Timestamp: 0, DataSize: 0, ExtraDataIndex: 0, Data: [] }, numMsgsRead: 0 }
[2022-02-24T12:50:15.149798-05:00] TRACE: signal: Closed
[2022-02-24T12:50:15.150100200-05:00] TRACE: PassThruDisconnectRequest { channelId: 2 }
[2022-02-24T12:50:15.151381800-05:00] TRACE: signal: Want
[2022-02-24T12:50:15.151520700-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:15.151630900-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:15.163682200-05:00] TRACE: signal: Want
[2022-02-24T12:50:15.163831-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:15.164049100-05:00] TRACE: signal: Want
[2022-02-24T12:50:15.164123900-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:15.164238700-05:00] TRACE: signal: Want
[2022-02-24T12:50:15.164336900-05:00] TRACE: PassThruDisconnectResponse { retVal: 0 }
[2022-02-24T12:50:15.164708700-05:00] TRACE: signal: Closed
[2022-02-24T12:50:15.164951200-05:00] TRACE: PassThruCloseRequest { deviceId: 1 }
[2022-02-24T12:50:15.166145900-05:00] TRACE: signal: Want
[2022-02-24T12:50:15.166303700-05:00] TRACE: signal found waiting giver, notifying
[2022-02-24T12:50:15.166395700-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:15.183050100-05:00] TRACE: signal: Want
[2022-02-24T12:50:15.183194400-05:00] TRACE: signal: Want
[2022-02-24T12:50:15.183270100-05:00] TRACE: poll_want: taker wants!
[2022-02-24T12:50:15.183447400-05:00] TRACE: signal: Want
[2022-02-24T12:50:15.183514600-05:00] TRACE: PassThruCloseResponse { retVal: 0 }
[2022-02-24T12:50:15.183936100-05:00] TRACE: signal: Closed

What apps are signal and poll_want logs from?...

I added {t} target and found that it's the want module.

How to turn that off? .logger(log4rs::config::Logger::builder().build("want", log::LevelFilter::Warn)) or .logger(log4rs::config::Logger::builder().build("want::want", log::LevelFilter::Warn)) or .logger(log4rs::config::Logger::builder().build("want::*", log::LevelFilter::Warn))?

For other poor souls wondering about this, here is my solution when configured via yaml:
appenders:
    stdout:
        kind: console
        encoder:
            pattern: "{d(%+)(utc)} [{f}:{L}] {h({l})} {M}:{m}{n}"
        filters:
            - kind: threshold
              level: info
root:
    level: warn
    appenders:
        - stdout

loggers:
  hvz_on_discord:
    level: info
    appenders:
      - stdout
    additive: false
  hvz_on_discord::config:
    level: info
    appenders:
      - stdout

I have a single appender that prints to stdout and is set to the info level. If root is set to the info level as well, various modules I'm using spam the console with hundreds of info messages. So I've set the root to warn to silence that. Then, to get other levels in my module, I create a logger with the name of my module, hvz_on_discord. This is the same name the compiler calls my module in compile messages.
This way, anything within my module will respect the level I set here. To log in any of my other modules, I add a logger like I did for hvz_on_discord::config.


Google play latest release is Aug '17

Browsing GitHub apps found this. It was great to find a FLOSS app!
But details look like the app is abandoned.
Clicked the GitHub link, and I see lots of activity and commits.
If there is lots of work in progress, a release on F-Droid would be fine, since I also checked, but found nothing.
Any release scheduling, policy, etc?

Yeah, since the last update my life has been quite stressful so there has been very little time for actual release/development. There is a new version released today with some bug fixes.
I'm actively trying to push this forward but studing 100% + part time work (25%), leaves not much for this.

@Meisolsson: It's not my intention to make you feel obliged to go through the issue list. Just having a recent release which truly reflects the current code is more than enough.
Having said that, I've bee installed the updated version. Thanks for pushing it.
I'll get back to the issue list with whatever I find. However, as a matter of advice, to handle your time limitation, it would help you to clearly communicate it to avoid unrealistic expectations.
Displaying maintenance status and expectations, or even showing that help is wanted could relief your burden.
A couple links:
https://opensource.guide/best-practices/
https://www.drupal.org/node/1066982
Hope this helps you. Available time and resources change as life, work, studies, etc shift priorities and there's nothing wrong with that.
Thanks again for your time and effort.


Errors on install using go get -u github.com/xenolf/lego on Raspian

There were two errors when installing on Raspbian (Rasberry PI) using the go get -u.
I tried a manual go build and got the same thing.
# github.com/xenolf/lego/vendor/github.com/miekg/dns
go/src/github.com/xenolf/lego/vendor/github.com/miekg/dns/client.go:223: u.Port undefined (type *url.URL has no field or method Port)
go/src/github.com/xenolf/lego/vendor/github.com/miekg/dns/client.go:224: u.Hostname undefined (type *url.URL has no field or method Hostname)

$ go version
go version go1.7.4 linux/arm

$ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 9.4 (stretch)
Release:        9.4
Codename:       stretch

Hi, now we use dep to manage dependencies.
You have 2 solutions:

use our binaries
clone the repo and use make build

What dependancies are missing?


Fix linting for antiInvite monitor

Fix the linting for the antiInvite monitor so it's up to linting standards for the project (ESLint)

changed settings for ESLint so the errors appeared on my end and resolved them


[android] Fix Bionic modulemap file syntax.

A line was forgotten in the rewrite which break the Android builds.

@swift-ci please smoke test


Get dragged item on sortupdate event

When I drag a div to another list, I can get some info from the sortupdate event. I can get the elementIndex of the div that was moved.
However, I would need to bind this to the item itself that was moved, and the event only seems to contain data of the parent.
In other words: I have the information I need (the elementIndex in the new list), but I can't use it since I can't get to the child div that was dragged.

I managed to traverse the DOM and find the element I need through e.detail.item.


Using oauth2orize with JS

Hi,
i want to use the oauth2orize server with JS client.
So working scenario will be

client will call server
server will auto autorize it and send back the code to client call

so in 2nd step i don't want server to use rediret_uri but juts respond back the code.
i know its not a standard flow of authorisation but i need it.
Is there any way i can use it in js app without any post back ?

Any update on how to get the redirect URL over AJAX and trigger the redirect on the client side?

Restating the problem: the server.decision endpoint does an HTTP redirect back to the client application which makes it incompatible with applications that do all their communication over AJAX. What I want is for the server to return the redirect URL (e.g. as JSON) and let the JS app send the user to the client application.
In the end what I did is bypass oauth2orize for the code generation step:
router.post('/oauth/code', /* put passport authentication middleware here */ function(req, res, next) {

	var clientId = req.body.client_id;
	var redirectUri = req.body.redirect_uri;

	/* load oauth client app and check redirect url */

	var code = new Code({
		value: uid(16),
		clientId: clientId,
		redirectUri: redirectUri,
		userId: req.user._id
	});

	code.save()
		.then(function() {
			res.send(code.toJSON());
		}, next);
});

The token exchange step happens as usual.

This modification is incompatible with OAuth 2.0 and is a potential security risk.
Sent from my iPhone

On Sep 21, 2015, at 7:39 AM, Tamlyn Rhodes<EMAIL_ADDRESS>wrote:
Restating the problem: the server.decision endpoint does an HTTP redirect back to the client application which makes it incompatible with applications that do all their communication over AJAX. What I want is for the server to return the redirect URL (e.g. as JSON) and let the JS app send the user to the client application.
In the end what I did is bypass oauth2orize for the code generation step:
router.post('/oauth/code', /* put passport authentication middleware here */ function(req, res, next) {
var clientId = req.body.client_id;
var redirectUri = req.body.redirect_uri;

/* load oauth client app and check redirect url */

var code = new Code({
    value: uid(16),
    clientId: clientId,
    redirectUri: redirectUri,
    userId: req.user._id
});

code.save()
    .then(function() {
        res.send(code.toJSON());
    }, next);

});
The token exchange step happens as usual.
—
Reply to this email directly or view it on GitHub.

Why so?
The only difference is that instead of returning the redirect URL in the Location header, I am returning it in the response body.

Have you read the OAuth 2.0 RFC?

By removing the redirect, how does the user get a chance to approve the authorization request?

I have to admit I haven't read it but this paragraph seems relevant:

HTTP Redirections
This specification makes extensive use of HTTP redirections, in which the client or the authorization server directs the resource owner's   user-agent to another destination.  While the examples in this
specification show the use of the HTTP 302 status code, any other   method available via the user-agent to accomplish this redirection is   allowed and is considered to be an implementation detail.

Isn't what I'm doing just using a different method of redirection?
Perhaps I should be clearer as to how the above Express controller fits in to the application. The approve/deny form is shown to the user in the Angular application. Clicking "Deny" sends the user back to the client app with the ?error=access_denied. Clicking "Approve" does an AJAX request to the server to generate a code then sends the user to the client app with code=xxxx.

Isn't what I'm doing just using a different method of redirection?

No.  What they are referring to is using form POST with different endpoints rather than 302 redirects.

The approve/deny form is shown to the user in the Angular application.

How do you ensure that this is secure?  When the request to your /oauth/code endpoint is made, how does your server ensure that the user was actually presented with any dialog and approved it?  How doe the server know what was approved in order to limit the scope or lifetime of the token?

If we're running on HTTPS we can assume that the page hasn't been tampered with and the user is seeing the application as we intended. Of course they could drop into the console and trigger a request manually but the same goes for any client-server interaction.
With the normal redirection flow, couldn't you create a hidden iframe and trigger the POST form within it?

If we're running on HTTPS we can assume that the page hasn't been tampered with and the user is seeing the application as we intended.

This is a bad assumption.  A properly implemented authorization server should be able to verify all interactions, and should not trust clients in any way.  What you describe is no longer OAuth 2.0, and as such the security properties are no longer defined (and in fact reduced).  The solution is simply to understand and follow the guidelines of OAuth 2.0.
I'm going to reiterate my statement, and caution you that your approach has security flaws.  For anyone else who comes across this issue, I do not recommend that this approach be taken.

As I noted above, the token (aka implicit) grant type is what is defined by OAuth 2.0 to be used by JavaScript applications running in a browser.

for everybody who is searching for an answer
here is my solution
export default class Login extends Component {
  onSubmit = e => {
    const data = new URLSearchParams(e.target);

    return fetch("/api/login", {
      credentials: "include",
      mode: "cors",
      method: "POST",
      body: data,
    }).then(response => {
      if (response.redirected) {
        window.document.location.href = response.url;
      }
    });
  };

  render() {
    return (
      <form onSubmit={this.onSubmit}>
        <input type="email" name="email" />
        <input type="password" name="password" />
        <button type="submit">Login</button>
      </form>
    );
  }
}

same works for decision step


flag dark joke

The joke's ID:
97
Why the joke should be removed / reflagged / recategorized:
this joke is dark, I have the "dark" filter set and this one still came up

Thanks for reporting the joke, I'll recategorize it asap


Issue Report: /en-us/guides/account-management/average-daily-budget

If you need help troubleshooting a problem with the Amazon Ads API, visit the Amazon Ads API service desk. Issues are for reporting documentation bugs and requesting enhancements only.
Describe the bug
Incorrect code snippet to set isOptedOutForAverageDailyBudgetIncrease to false,
on page https://advertising.amazon.com/API/docs/en-us/guides/account-management/average-daily-budget
URL of the content
https://advertising.amazon.com/API/docs/en-us/guides/account-management/average-daily-budget
Description of what the documentation currently says
It says

use POST /accountBudgets/featureFlags and set isOptedOutForAverageDailyBudgetIncrease to false

However in code snippet from where user can copy payload it says
{   "featureFlags": {     "isOptedOutForAverageDailyBudgetIncrease": true   } }
Description of what the documentation should say
For code snippet it should be
{   "featureFlags": {     "isOptedOutForAverageDailyBudgetIncrease": false   } }
Screenshots

Additional context
Add any other context about the problem here.

Hi @satishaher , thank you for bringing this to our attention! That value has now been corrected.


How can I train the airbert with multi-gpus？

I found that when training airbert, there was always only one GPU in use, and then it always reported a memory overflow error, even though I lowered the batch size many times (one GPU on my machine has about 12GB of memory). I'm wondering how much memory I need to train and if I can distribute training across multiple GPUs? Thanks.

I worked on V100 GPUs. See codes here for DDP: https://github.com/airbert-vln/airbert/tree/main/slurm


main.go:14: revel redeclared as imported package name

Error log:
ERROR 2015/06/07 18:16:43 build.go:101: # github.com/xxx/xxxx/app/tmp
go/src/github.com/xxx/xxxx/app/tmp/main.go:13: revel redeclared as imported package name
previous declaration at go/src/github.com/xxx/xxxx/app/tmp/main.go:7
main.go content:
7	"github.com/revel/revel"
8	_ "github.com/xxx/xxxx/app"
9	controllers "github.com/xxx/xxxx/app/controllers"
10	tests "github.com/xxx/xxxx/tests"
11	controllers1 "github.com/revel/modules/static/app/controllers"
12	_ "github.com/revel/modules/testrunner/app"
13	controllers0 "github.com/revel/modules/testrunner/app/controllers"
14	revel "github.com/revel/revel"
My code:
controllers/app.go:
type App struct {
BaseController
}
func (c App) Index() revel.Result {
return c.Render()
}
controllers/base.go:
//.....
func init() {
revel.InterceptMethod((*BaseController).Before, revel.BEFORE)
}
type BaseController struct {
*revel.Controller
}
func (c *BaseController) CheckValidate(res revel.Result) revel.Result{
if res != nil{
return res;
}
return nil
}
//.....
If remove function "CheckValidate" or remove param "res revel.Result", All works well.

7 and 14 are identical to the line, remove one of them

If you have more helpful info, please reopen. Thanks.


[Bug]: Incorrect check for existence of PriorityClass

Contact Details
<EMAIL_ADDRESS>What happened?
I set podSpec.priorityClassName to db-priority, which exists in the cluster, but the chart fails with the following error: PriorityClass db-priority is missing in the cluster
Looks like the current check is trying to find the PriorityClass inside a namespace when it shouldn't:
https://github.com/neo4j/helm-charts/blob/9967a927cc732dcad6b1bdeab81985a69a00ef56/neo4j-standalone/templates/_helpers.tpl#L312
I'm using the 4.4.11 version of the neo4j-cluster-core chart.
Chart Name
Standalone
Chart Version
4.4.3
Environment
Microsoft Azure
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

After further investigation seems that the issue was not the check, I'm using ArgoCD + Kustomize to deploy the Helm Chart and looks like the lookup function is not fully supported.
Sorry for the confusion :sweat_smile: I'll close this issue.

After further investigation seems that the issue was not the check, I'm using ArgoCD + Kustomize to deploy the Helm Chart and looks like the lookup function is not fully supported.
Sorry for the confusion :sweat_smile: I'll close this issue.

After further investigation seems that the issue was not the check, I'm using ArgoCD + Kustomize to deploy the Helm Chart and looks like the lookup function is not fully supported.
Sorry for the confusion sweat_smile I'll close this issue.


Improve design for mobile devices

Hello,
first of all thanks for the great work on this repository, I really like it and enjoy using it!
I would like to suggest some small design changes for mobile devices. This pull request will change the following:

Add scroll snap for lanes: this will help for vertical scrolling on mobile devices as each lane will automatically snap into the center of the screen when the user scrolls vertically
Wrap the header: the menu is currently cut off and you need to scroll on the menu to get e.g. to the "New lane" button. This is improved by wrapping the buttons that do not fit in the header in a second line
Reduce size of modal: the modal was going until the edge of the screen, now it is reduced to have a little gap around it

Thanks so much for the work! I'll test the changes included in this PR as soon as possible


protos: Remove v2 config proto deps

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message: protos: Remove v2 config proto deps
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

@htuch this is a follow on from #16985 to remove more from the v2 envoy/config namespace where removal is fairly straightforward


Doc update to wildcard support match label selector

Signed-off-by: Vyankatesh<EMAIL_ADDRESS>closes https://github.com/kyverno/website/issues/424

Needs milestone assignment.

Added to 1.5.3.

Added to 1.5.3, can we merge this?

yes


Enumerate documentation Sections

Enumerate the sub-assemblies from 1 to 5. Enumerate the start guide as section 1 https://tetrabiodistributed.github.io/papra/v1.0/
and the other sub-assemblies
Enumerate the building steps in sequence

i will do this when i start editing the documentation


Update the templates to support k8  version 1.16

Updating the templates to support k8 version 1.16. Essentially updating the d…eprecated apiversions: apps/v1beta2 and extensions/v1beta1 to apps/v1 and apps/v1 respectively. Note there will be a document update needed since if there is a AKS cluster targeting version 1.16, the minimum client helm version needs to be >=2.15.1

Could you please clarify why PopulateDatabase doesn't need this update as well? Is there something different for this one?

Could you please clarify why PopulateDatabase doesn't need this update as well? Is there something different for this one?

https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/ is the link to the deprecated apiversions documentation. kind==ingress is not impacted.

Could you please clarify why PopulateDatabase doesn't need this update as well? Is there something different for this one?

https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/ is the link to the deprecated apiversions documentation. kind==ingress is not impacted.

Great, thank you!


Is there any tf.keras implmentation for squeezenext network?

Hi,
I just wonder if there is any tf.keras implementation for the squuezenext, I tried to convert the tensorflow implementation one, but it was hard. Can you provide the tf.keras implementation?

I am not planning to implement a tf.keras version, you can try asking the authors of the paper at the official repo:
https://github.com/amirgholami/SqueezeNext


apply some clippy suggestions

This all looks good, thanks! But it needs a rebase please

Thank you for the update!


Call createGraph() for each group of files that share the same import map

TBD

We have to support the workspaces key in deno.json first.

To be done with #147


Updated badges for v3

What type of PR is this?

cleanup
documentation

What this PR does / why we need it:
Updates badges to correctly target main branch / v3 module.
Which issue(s) this PR fixes:
NA 😬

What is not right with Codebeat? Seem to complain a lot about complexity https://codebeat.co/projects/github-com-urfave-cli


Remove version: qBittorrent.qBittorrent version 4.4.1

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: URL works;


⚠ Bofrost.at has degraded performance

In ce3396e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1753 ms

Resolved: Bofrost.at performance has improved in 1441013.


filtrex expressions

Dear,
As discussed in this issue I have integrated filtrex expressions into the Sensor node config screen.
Note that I have included version filtrex version 3.0.0-rc11 as a dependency.  That is a release candidate version, but the author has planned the final 3.0.0 version in the near future.  I needed that version because the author has been so kind to implement boolean values and nested expressions for us.  So you can now use for example "msg.payload == true", similar to the current dropdown value in this node...
Note that this pull request determines (based on the input message) whether the expression is true or false, but that value is NOT used to filter messages for alarms.  Reason why I haven't implemented that in this pull request, is that it is also not implemented yet (see here).  Moreover I don't know if/how you want to implement my other feature request.  Because when that would be implemented, the message always has to be processed (but the filtrex expression result value would only be used to determine whether an alarm should be triggered or not).  So I propose to keep that for a separate discussion...
This pull request also offers an extra server-side endpoint, which can be called by the frontend (config screen in flow editor) to do some (basic) real-time syntax checking:

I have tried to make sure that existing nodes are not impacted, by automatically converting the old dropdown values to corresponding filtrex expressions in the following situation:

on the client side, which is triggered when the config screens opens after the user has double clicked the node.
on the server-side, which is used in case an input message is injected but the user hasn't opened the node's config screen.

If you would like to test this backwards compatibility, the easiest way to do it is by adding a bunch of sensor nodes on the flow (when still using the old version).  Then install the new version, and test the old nodes in the above described two scenarios....
Hopefully you like it, because it was quite some work to implement it.
Thanks for reviewing !!
Bart

This looks great, very clean. I've not tested, but happy to go on your say-so. Is it working really well for you? I presume so.
Great job with this, keen to try it out on my install soon after updating also.
Thanks again (on behalf of all users of the library), and I will have a look through the other proposals as well. Great to have another enthusiastic maintainer on board!
Regards,
Andrew


Plans to publish new release?

Hello! Former Genesys employee here -
Love this library and used it at Genesys and now using it in my current work. There's been some nice improvements in recent months that haven't made it into an npm release. Are there any plans to make a new release soon?
Thanks!

Hey @brentezerc,
Thanks a lot for using it!
I just published a new version with @tichon29's work on new retry capabilities.
This is available as<EMAIL_ADDRESS>https://github.com/genesys/mollitia/releases/tag/0.1.0
Hope it suits your needs!

@cadgerfeast Thank you so much!


TypeError: Cannot read property '0' of undefined

Hi, can you help me ?
what's wrong with this table link
????

@kirillbashtenko Looks like it doesn't work, the combination of ui-scroll/ui-scroll-td and ng-repeat inbetween. This works for ui-scroll-th, but not for ui-scroll-td. While we are looking into it, you can do a workaround without ng-repeat:
{{item["col1"]}}
{{item["col2"]}}
...

Thanks for the issue repro!

@dhilt thank you, for your quick response, but that  wouldnt work in my case, i have dynamic columns and rows, so probably i'm stuck right now.

@kirillbashtenko I pushed the fix into grid-scopes-wrapping branch. That was the issue of race condition around ui-scroll-td linking, and it is possible to say that the ng-repeate wrapping scope was the cause. I want to think a little bit more about the problem, so the code is in branch. It includes distributive files and the demo . It would be great if you could try it!

@dhilt yeah , thank you, it's great , working as i expect right now!

@kirillbashtenko Ok, you can use the branch code while I'm preparing it for 'master'.

@dhilt after detail investigation i found a really big perfomance problems ,  in each tbody > tr  i saw :
screen and in your demo also, but you cant see problems on small tables. In some of my tables i have more than 100 columns and ng-repeat have real big problems with perfomance.

@kirillbashtenko Yes, it looks not good... By the way if you try 100x500 double ng-repeat

{{row}}	{{col}}

...this renders pretty slow and the scroll proccess is being affected itself. Then just add two simple bindings class="{{row}}" and class="{{col}}" and get rendering time 1/5 slower. The ui-scroll (especially with the ui-scroll grid) is heavier I guess. The performance is the core issue and I don't see a simple way to imrove it in the actual situation.
Regarding


[BE] allow deleting multiple coupons

Coverage increased (+0.3%) to 90.293% when pulling f5a80638a9365c86fa58a2a218683d1f8c289668 on feature/coupon-qs-delete into 4bf1c1d34b3f58e511cecb01a440708cce0324d6 on feature/coupons.

Coverage increased (+0.3%) to 90.293% when pulling 4ff2bf117c98359f1b2fd7fdf0c16b2d34e267f5 on feature/coupon-qs-delete into 4bf1c1d34b3f58e511cecb01a440708cce0324d6 on feature/coupons.

Coverage increased (+0.2%) to 90.214% when pulling 23555a3835830dfeed0f1bcac985fdb2b9d406d6 on feature/coupon-qs-delete into 4bf1c1d34b3f58e511cecb01a440708cce0324d6 on feature/coupons.

Coverage increased (+0.2%) to 90.244% when pulling e5a9c59e997273382e7635e8bddc2c9e90f1082e on feature/coupon-qs-delete into 4bf1c1d34b3f58e511cecb01a440708cce0324d6 on feature/coupons.