Visualizer not working with Razer 7.1 Surround Sound Software

Describe the bug
The visualizer works normally but it won't work when I turn on Surround Sound. It works normally with the headphones but headphones with surround sound turned on won't work.
To Reproduce
Turn on Razer Virtual 7.1 Surround Sound (this is a paid app unfortunately), set the audio output to 7.1 Speakers.
Screenshots
Not needed.
System information

Rainmeter Version: Rainmeter <IP_ADDRESS>21 (64-bit)
Language: English (1033)
Build time: 2019-09-22  7:26:11
Commit Hash: 0ba4dfc4
OS Version: Windows 10 Pro 2004 64-bit (build 19041) - English (3081)
Skin Version: Version=2.1.0
Spotify Version: I don't use spotify

Additional context / media
none

i got the same problem with razer virtual 7.1

Believe it or not. Even if you have THX Spatial audio. you'll get the same problem
I guess this software doesn't like Razer much :)

Aight. 2 years passed and i have solved this problem a long time ago but its ok hahah

How did you solve it?
I'm wondering if I can fix THX the same way

sorry i dont really remember as i stopped using the visualizer and switched for another one shortly after


New package: DigitalComm v0.3.0

Registering package: DigitalComm
Repository: https://github.com/RGerzaguet/DigitalComm.jl
Created by: @RGerzaguet
Version: v0.3.0
Commit: 795b173c7b5a25c7d40055b938272e0e571dd855
Reviewed by: @RGerzaguet
Reference: https://github.com/RGerzaguet/DigitalComm.jl/commit/795b173c7b5a25c7d40055b938272e0e571dd855#commitcomment-35476073

Hello there
I have noticed that the pakcage has been removed from Registries albeit being successfully registered (and update) in July.
Any reason ?

Thats unfortunate, @KristofferC ??
Anyway, can you retrigger the bot to resolve the conflicts.

Bump @RGerzaguet
Can you retrigger Registrator?
[noblock]

Hello,
This has been done but in a different PR (changing version number and changing deps).
It is here now https://github.com/JuliaRegistries/General/pull/4461
So you can close this !
Sorry for the noise !
Thanks
@+R


Problem with using Realm objects in multithreaded app

Environment: Version 7.0 beta 6 (7A192o), Realm and RealmSwift from branch swift-2.0.
I have a problem with reading data from Realm database when using background threads (NSThread or dispatch_async). For example, I create background thread A during application startup which lives during whole application life-cycle (or for some long time). When I create Realm object in thread A then I can read current data from Realm. But when I add new data to Realm from thread B then I am not able to read them in thread A. I always fetch old data. It does not matter if I use in thread A the same Realm object or create new one. It seems that once created Realm object in background thread causes that all Realm objects from this thread hold database snapshot corresponding to the database state when the first Realm object was created. To workaround this problem I need to create new thread with new Realm object and with this configuration I can read latest data from Realm.

If your thread doesn't have a running runloop, you'll need to manually refresh the Realm for it to see new data -- autorefresh happens on a spin of the runloop.

Thanks for the quick response.
Problem with missing runloop. Just as I thought after deeper debugging of Realm code.
I did manual refresh in my code and it works perfectly. My problem is fixed.
One more thing. It is clear for me that when autorefresh was not performed then existing Realm object does not have fresh data. But can you explain me why creating new Realm object does not fetch fresh data and it still points to the old one?

Realm objects are actually cached per-thread for performance (it turns out that open() is pretty expensive!), so you're getting the cached instance.

Now everything is clear. Thanks.


Lightening talk invite Gab Smith

Gab Smith, CAM Raleigh, Creative Mornings RDU

email invitation sent; follow-up email sent


Change footer links to be shorter and remove fundraising link

Completed; however, only in English. Translations are still required.

Translation still missing in ES, but main issue closed.


Limit batch to 65536 to align with the backend

The setting that should control the property is set to the incorrect value of 1024 Kb, not 64 Kb.
MaxTransmissionBufferCapacity
https://github.com/Microsoft/ApplicationInsights-dotnet/blob/151509eac5e23fcbd09f3a8989a35d1099703957/src/TelemetryChannels/ServerTelemetryChannel/Shared/ServerTelemetryChannel.cs#L150
this.Buffer.Capacity
https://github.com/Microsoft/ApplicationInsights-dotnet/blob/228f714dfeae7617283b8931501e6ecb0dd2d5d5/src/TelemetryChannels/ServerTelemetryChannel/Shared/Implementation/Transmitter.cs#L44
private const int DefaultCapacityInKiloBytes = 1024;
private int capacity = DefaultCapacityInKiloBytes * 1024;

https://github.com/Microsoft/ApplicationInsights-dotnet/blob/151509eac5e23fcbd09f3a8989a35d1099703957/src/TelemetryChannels/ServerTelemetryChannel/Shared/Implementation/TransmissionBuffer.cs#L15

Workaround is to set:
((ServerTelemetryChannel)TelemetryConfiguration.Active.TelemetryChannel).MaxTransmissionBufferCapacity = 64 * 1024;

We can take it for 2.4 stable if the fix is trivial.

This may be more complex than just a limit change. This particular issue was caused by the single event's size larger than 65K


Remove extra argument from WebAssemblyImportDependency constructor call site

What kind of change does this PR introduce?
refactoring

Did you add tests for your changes?
no

If relevant, link to documentation update:
no

Summary
As part of https://github.com/webpack/webpack/pull/6862 I'm proposing fixes to issues TypeScript compiler have found

Does this PR introduce a breaking change?
no

Other information

Could you fix the formatting here please? You can run yarn pretty-files to reformat the code.

Thanks


Fix SiameseHead naming

In keras.containers.Graph.add_shared_node When settingmerge_mode=None (In order to add outputs of layer to the graph) output names provided in outputs kwarg is not set for SiameseHeads created.
So trying to use then in another shared layer with merge_mode='join' will not work. (Because all of them have name simesehead and they will replace each other in the dictionary created)
The following example will produce the issue I described. (base_network and euclidean_distance same as this example)
g.add_shared_node(base_network, name='shared', inputs=['in1', 'in2'], merge_mode=None, outputs=['mid1', 'mid2'])
g.add_shared_node(Dense(85), inputs=['shared'], merge_mode=None, name='shared2')
g.add_node(Lambda(euclidean_distance), name='dist', inputs=['mid1', 'mid2'], merge_mode='join')

Right. Might have missed it when we changed the naming convention. :+1:


Switch between languages

I regularly want to spellcheck in English, Spanish and French, and the only way to switch between one language and another is to change the "Locales" field in the settings. I don't want to let the three languages there, because it would not detect a misspelled word that exists in another language.
Ideally, there would be a switch available on right click / contextual menu, or in the status bar in the bottom of atom.

If anyone does work on this, I have an idea of how to implement it to allow plugins to decide the language for a given buffer. That way, we can have Markdown+YAML have it in the headers, or have it scanned from the filename (chapter-01.en.txt), or other methods.

maybe your question is outdated by now, but check out this: https://github.com/atom/node-spellchecker/issues/100#issuecomment-489549361


Added UnsupportedProjectTypes helper and unit test. Added a test to ProjectConvert to check.

Proposed fix for issue #78 - add check for unsupported projectTypeGuids

I was going to include a test aspnet project file but the ProjectConvert does not have any unit tests.


Error: Can't set headers after they are sent in sails.js v0.11

I have upgraded my project from sails v0.9.8 to sails v0.11. When do i try to retrive data, it gives this error.
Error: Can't set headers after they are sent. at ServerResponse.OutgoingMessage.setHeader (http.js:690:11) at ServerResponse.appendHeader (/usr/lib/node_modules/sails/node_modules/express/node_modules/connect/lib/patch.js:94:33) at ServerResponse.res.setHeader (/usr/lib/node_modules/sails/node_modules/express/node_modules/connect/lib/patch.js:125:19) at ServerResponse.res.set.res.header (/home/abc/xyz/git/propgod-internal-V0.11/clients/web/node_modules/sails/node_modules/express/lib/response.js:577:10) at ServerResponse.res.cookie (/home/abc/xyz/git/propgod-internal-V0.11/clients/web/node_modules/sails/node_modules/express/lib/response.js:650:8) at Request.callback [as _callback] (/home/abc/xyz/git/propgod-internal-V0.11/clients/web/api/services/DataService.js:51:34) at Request.self.callback (/home/abc/xyz/git/propgod-internal-V0.11/clients/web/node_modules/request/request.js:123:22) at Request.emit (events.js:98:17) at Request. (/home/abc/xyz/git/propgod-internal-V0.11/clients/web/node_modules/request/request.js:1047:14) at Request.emit (events.js:117:20) at IncomingMessage. (/home/abc/xyz/git/propgod-internal-V0.11/clients/web/node_modules/request/request.js:998:12) at IncomingMessage.emit (events.js:117:20) at _stream_readable.js:944:16 at process._tickDomainCallback (node.js:486:13)
.
How can i enable cors for my application?
Note : I'm loading scripts and styles using Gruntfile.js.
I have separate modules for client and server side.
Please help me out !!!

Please don't cross post http://stackoverflow.com/questions/28854361/error-cant-set-headers-after-they-are-sent-in-sails-js-v0-11

Thanks @randallmeeker
@chandradeochakravarti StackOverflow is a better place for questions like these.  This forum is for bug reports on the Sails core.  This is probably an implementation issue in your code, or else we'd be seeing it posted a lot more.  Also, try to ask one question per post! (CORS is a totally separate issue, and it is also pretty well documented).


[agent] standalone agent release

Motivation
Users should be able to install their own self-hosted agent. Install via the CLI.
Finish Line

[x] #4873

See https://github.com/dxos/dxos/milestone/11

@nferch I believe this is completely done. Can you confirm and close if it's the case?

@jessmartin there were some incomplete issues that were linked to the milestone that were removed. I re-added them to a tasklist above, do you consider any of those standing in the way of considering this complete?

Thanks for collecting those! It depends on what we mean by "release" above. I asked @zhenyasav for clarification on priority. I think before we announce the technical preview of the Agent via CLI we should probably fix the two bugs in the tasklist above.

Closing this as it's just a tracking issue of issues we're already tracking at the project level. Offers no additional value.


nixos: libinput use mkEnableOption

@jagajaga Here you go :-)
Things done:

[ ] Tested via nix.useChroot.
[ ] Built on platform(s): .
[ ] Tested compilation of all pkgs that depend on this change.
[ ] Tested execution of binary products.
[ ] Fits [CONTRIBUTING.md](https://github.com/NixOS/nixpkgs/blob/master/.github
x Crossed fingers and hoped that it is fine
x Did nixos-rebuild dry-build

/CONTRIBUTING.md).
Extra
Fixes # .
cc @ .

Please note, that points are not mandatory.

wuh - that was fast :-)

@eskimor going back to sleep :zzz:

@jagajaga Uuh, I did not mean to wake you! Sorry for that! Good sleep!


fix: fix export of notes_dict

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


Discussion: port the migration to manpage format instead?

This is, to a great extent, a matter of opinion and preference. But I think it is worth having an informed discussion anyway.
I find the help system to be a little on the suboptimal side. Case point, the help system needs and has documentation about itself. I.e we need help on how to use the helping documentation.
I haven't look at the source code, but I believe this documentation is embedded in the source and output by the main application.
Granted, at this day and age, there are many command line users that don't every call ''man''. Probably most people will head up to google most of the time, but the current documentation is not available in web friendly format either. AFAIK, the documentation in the readme is distinct from that reachable through the help system.
I think a manpage would solve many of these problems. Here are some advantages I think should be taken in consideration:

Discoverability. It is there, where it is expected to be found. Many people will just man xsv as a reflex
Easier to skim through. Since its contents are rendered in a flat text body, users can just open it and use the find functionality of their pager, or grep it, or just read it through. In the end, it works like all other manages, not requiring to learn how to use it.
trivially convertable to html so it can be made available on the web. In fact, github even renders manpages.

This is, to a great extent, a matter of opinion and preference.

You're leaving out another key aspect: development effort and portability.
The single biggest upside of the current help system is that it is simple to maintain (a single source of truth) and works even in environments that don't have a culture of using man pages (such as Windows).
If xsv were to use man pages, then I suspect end users would expect a man page for each sub-command. e.g., man xsv select or man xsv sample. This means maintaining a man page for every sub-command. Contributors who add a sub-command would also be responsible for writing said man page. Writing man pages is an arcane endeavor that requires extreme attention to detail. I know because I do provide man pages for some of my other projects.
For these reasons, I'm going to pass for now. I have some plans to overhaul xsv, but I don't know when or if I'll get to it. If I can find a simple way to provide man pages that mitigates the aforementioned downsides, then I might revisit this. But for now, this is unlikely to ever happen.


Would like to implement no-fog zones

Hi,
Is there a way to add no fog zones in the shader code?
We currently are running some tests, using the height fog as some kind of mist in our scene, and we want one of the character skills to remove some of the mist. The problem is that the skill is done away from the player, and he can move close or away from that zone.
We know it is possible with Ray Marching to add primitive(s) to the calculation and wondered if you would know where in the code we should be looking in order to achieve what we want?
We don't know if that will look realistic but we want to try it ;p
Cheers!

Hi,
sorry for the very late reply. I've been very busy lately. In case this is still relevant, look for GetDensity function in VolumetricLight.shader. It is called for every raymarching sample. wpos is world space position. Simply make an intersection test with your primitive and set "density" to zero to kill the effect. Or gradually fade out the effect with decreasing density.

Just add invisible object to "no-fog" zone


Overload footer with dragOptions

Ticket: #817

@snehmehta  add the schema and you are good to go

@snehmehta See this comment - #844 (comment) Can you re-assign yourself for this issue if you're working on this ticket?

hey @vinothvino42 I haven't check that issue yet and I have few high priority ticket left as well. Let me know if it's blocking something I'll have a look at it.


Issue 437

This PR adds merge method support and squash API options for repository get and update.
I'm unsure of what a good unit test might be, so I can update this if need be.

LGTM after a minor godoc tweak.
Awaiting secondary LGTM before merging.

Thank you, I will collapse my commits when it gets signed off on.

I rebased onto master and squashed.

We should add a "Resolves #437." or equivalent message to the commit message, so that issue gets closed when this is merged. But @gmlewis can do that when merging, so it's not a big deal.

@shurcooL I have a "Closes" line in my commit message already.

Rebased onto master again.

Hmmm... it looks like I dropped the ball on this one... I'm sorry about that... Merging.

Ah, yes... thanks, @shurcooL for the reminder.  This was held up on the header issue.
I haven't had a chance to test the comma-separated header yet.  Hopefully today.
I'll test before I merge.

This breaks the existing 'squash' support. Our API is changing.
I don't even know if squash is still in the github API though. Or if we care (I don't).
I'll rebase my work to support SHA on top of this. Great!

SGTM.  Yes, "squash" is still supported in the GitHub API via the MergeMethod.
Thank you, @eparis!

@gmlewis but our API is breaking in this PR is what I was trying to say, not that I care, just pointing it out in case anyone else wanted to complain that we know this will cause code to be unable to compile.

Ah!  I didn't understand that, @eparis. Can you please copy/paste the error message(s)?

@gmlewis I hope this PR hasn't gone stale. Based on the issue you wrote discussing how we should handle the merge method, the code is already set up to do that.
Please let me know if there are any more items I should address in the meantime.

Thanks for the ping, @gsquire, and I apologize for the delay!
AFAICT, this PR is ready to be merged, and I'll go ahead and do that now.

Integrated in https://github.com/google/go-github/commit/575b0b37560d9485f6d3bcb220a9111495b9c248.

@gmlewis It's no problem, thanks for your patience. 👍


Docs: Add @vue/test-utils example in Getting started with Unit testing

Describe the feature
After reading Testing-Get started docs I had confusion on whether I could use the already existing @vue/test-utils. I was able to do it after following a guide I found online and it worked just fine.
I wanted to raise this topic and ask if you think it would be useful to also add a section on how to set this in a new Nuxt 3 project? Was thinking just a basic step-by-step process on how to add @vue/test-utils, vitest and happy-dom and spin up a simple Unit test.
I know we already have @nuxt/test-utils but in some old projects it might be useful to also have a short guide on @vue/test-utils. What do you think?
Additional information

[X] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

I think it would be a great idea!

Openned PR here https://github.com/nuxt/nuxt/pull/26205 @danielroe


some docstrings missing w/o 3.5

http://stackoverflow.com/questions/36143501/how-to-use-python-3-5-syntax-in-readthedocs-combined-with-autodoc/36144269#36144269
edit: scratch that I'll just wait for this to be resolved https://github.com/rtfd/readthedocs.org/issues/1990
until then the docstrings for the on_* methods won't show up, annoying but not a huge loss.

this is as good as it's gonna get


Nullable and IAsyncEnumerable break syntax highlighting

This will reproduce on pretty much every C# project I've tested, even dotnet new console.
Type in the following code to the editor
            string s1 = "hello"; // string is colored
            await foreach (var x in e) { }
            string s2 = "world"; // string is not colored

Notice that the presence of await foreach causes the second usage of string to not get properly syntax highlighted. It will be white instead of blue. The moment you delete await then everything will snap back to normal.
This problem appears to impact a number of C# 8 features. For instance the same effect occurs when using a nullable array.
            string s1 = "hello"; // string is colored
            int[]? example;
            string s2 = "world"; // string is not colored

One way to work around this is to add an empty statement after the await foreach
                ; // empty statement to fix vs code syntax bug around await foreach

This is really an issue of C# extension for VS Code not of OmniSharp.
It uses https://github.com/dotnet/csharp-tmLanguage for highlighting, which is very limited and hasn't been updated in quite a while.
OmniSharp exposes semantic highlighting endpoint based on Roslyn's semantic highlighting (I added your two cases as tests here to make sure they are covered (https://github.com/OmniSharp/omnisharp-roslyn/pull/1789)) but at the moment the C# extension still doesn't use that endpoint - it's a work in progress to incorporate it github.com/OmniSharp/omnisharp-vscode/pull/3667

this is resolved via semantic hihglighting


StatusCode: 502

So, I get an error when pull a folder  err: download: failed for url "https://googledrive.com/host/0B6eAixP-e0ZZZ1QtNVdsdlXXXXX". StatusCode: 502

It happens to me too. The exact same. It only happens in my laptop, not my desktop, although both have Ubuntu 16.04. Have you found what the problem is?


[Bug] Problems interacting with the ProjectE transmutation table

One of two things happens:
1: It won't let you pull anything out
2: you'll get ghost items in your inventory
Not a really huge issue as i've already got a nice workaround in place in the form of a miniature Refined Storage system in place as the remote works great with the crafting grid.

Fixed in 1.12-0.9.5! :)


Forwarding i64/u64 serialization to serde

Aims to implement #21. I am not sure if the serde dependency version has to be updated tho...

I'm not sure this works the way you think it does (producing bigints), but happy to be proven wrong. Can you add tests that check that the resulting value is indeed a bigint?
Also, the deserialization part is missing.

I have no idea how to actually do the deserialization part, but I'll try to take a look. Tested it in my local environment and at least on the browser side I got bigints (tested using console.log). I'll come back in a few days, currently I got lots of work to do.

The tests seem to fail too. Please test with wasm-pack test locally while you're working on the PR.

Will do, thanks!

I have no idea how to actually do the deserialization part, but I'll try to take a look.

I mentioned how to do that with some links in a comment on the issue yesterday.

I mentioned how to do that with some links in a comment on the issue yesterday.

Yes, I know, but since I've absolutely no clue how to do rust the right way (I'm a C/C++/Go guy) I'll need some time to figure things out ;)

One more thing - the change of serialize_{i,u}64 to produce BigInts instead of the previous behaviour (safe numbers) would be a breaking change; I suspect that might be why the tests are failing too.
We'd probably want either a serialization option or a major bump to accomodate such change.

I'm really really busy with work at the moment, was hoping to find some time on a weekend but I don't think it's going to happen anytime soon, so if somebody want's to take over it'd be appreciated. Otherwise I'll continue to work on this once I got a little more spare time on my hand.


Default method implementation isn't handled in component interface

I have AppComponent interface with some default methods inside, because I need to pass deps inside another component:
interface AppComponent {
    default ProfileComponent createProfileComponent() {
        return DaggerProfileComponent.builder()
                .profileDependencies(this)
                .profileDocumentDependencies(this)
                .build();
    }
}

Current behavior
throws exception java.lang.IllegalArgumentException: No provider available for
Expected behavior
dagger-reflect checks that it's default method and invoke it implementation

@Jacks0N23 I think you should keep the issue open in case there'll be more work on this project.


Precedence of ternary conditional expression in Clafer

I have done a bit of testing on if-then-else with clafer compiler. I tried both <IP_ADDRESS> and 0.4.0. They do differ a bit in handling my examples, but both seem to require that the subexpressions are (almost?) always parenthesized as in if (...) then (some ...) else (a.b.c) .
This is quite non-standard in programming languages.  Usually the ternary operator gets a very low precedence and if - then -else can be written without parenthesis.  I think this is both in C like languages (? :) and in ML-like languages (if-then-else).
This is not super urgent but we could consider looking into the grammar to fix it.  Usability for users would improve slightly.

I looked at the grammar and it's not clear where to move the if/then/else rule. Should it have the lowest possible precedence?
E.g., we could allow the code
if x then some y else all a1; a2 : A | a1 > a2
``

to have that, we would have to make the grammar like this:

EImpliesElse.   Exp ::= "if" Exp "then" Exp "else" Exp ;
EDeclAllDisj.   Exp1   ::= "all" "disj" Decl "|" Exp1 ;
EDeclAll.        Exp1   ::= "all"        Decl "|" Exp1 ;
EDeclQuantDisj.  Exp1   ::= Quant "disj" Decl "|" Exp1 ;
EDeclQuant.      Exp1   ::= Quant        Decl "|" Exp1 ;
EGMax.          Exp2  ::= "max" Exp3 ;
EGMin.          Exp2  ::= "min" Exp3 ;
....
etc.

The grammar would allow code like this (I suppose because it is right associative by default).

if
if x then z else y
then some x
else if no w
then if z then u else o
else some p

which would put parenthesis as follows

(if
(if x then z else y)
then (some x)
else (if (no w)
then (if z then u else o)
else (some p)
)
)

See test cases:

ifthenelse.cfr,
nested-ifthenelse.cfr.


[INCIDENT] all memory somehow gets used

Every two weeks or so, our lab computers will have ~100% memory usage and become extremely lagged and buggy (applications crash/cannot open).  I have observed this on the ps and fs tables, and I have heard that something similar happens on the Waldo system.
This happens without most services running (docker, most daemons), but attune and attune-delay will be running.  Task manager shows a single python processes taking up a large chunk of memory (~0.5-4 GB).  The memory used in all task manager is well short of the total computer memory usage (~30 GB).
I am attributing this to attune, but I might well be off.  Just documenting the incident for now.  I can imagine this being a yaqd-control/nssm issue as well.  I will try running attune daemons in the foreground to have more information.
In all cases, the issue is resolved by restarting.

By restarting what?

Sorry, crucial detail.  The problem is fixed by restarting the computer.
When the daemons are closed, I can verify the python process closes in Task Manager, but the computer memory usage remains mostly unchanged and the computer remains lagged.  Again, the reported memory usage greatly exceeds the sum of contributions from individual processes.

I am very skeptical about this being attributable to yaqd-attune, I'd be more inclined to think that perhaps the docker stuff is eating memory, and would be interested to know if just restarting that helps? (That may also slightly hide its memory usage from windows, at least from individual user processes, but may show up in the total)
That is my gut instinct/first reaction, but certainly not proven.

Hi all was this fixed by https://github.com/yaq-project/yaq-python/pull/77

@untzag I am not certain yet, but there is evidence that is the case.  The fs computer just had a repeat incident and the high memory usage was relieved by restarting the daemons.  This behavior is consistent with a daemon memory leak.  We have updated yaqd-core and will be waiting to see if the problem repeats itself over the next week or two.

I am not really observing memory issues anymore, so I am going to call this issue resolved by yaq-project/yaq-python#77 🥳


Write up the proposed data cleanup plan

I thought it would be sensible to write up the proposed data cleanup plan as it's quite complicated and involves a lot of steps and different tasks. Please comment on this pull request if anything's not clear.

Going to merge ourselves. Steve wants to make reference to this in another writeup.


Update scala3-library, ... to 3.3.1

About this PR
📦 Updates

org.scala-lang:scala3-library
org.scala-lang:scala3-library_sjs1

from 3.0.2 to 3.3.1
📜 GitHub Release Notes - Version Diff - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:semver-spec, commit-count:1

Superseded by #397.


Search - iOS - Category dropdown menu is briefly visible when navigating back from an image

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.40-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:

Open the app
Log in with a Gmail account that has previous conversations with a few image attachments
Tap on the "Search" button
Tap on the category dropdown menu
Tap on "Chats"
Tap on any image
Tap on the "<" button to navigate back

Expected Result:
Dropdown menu shouldn't be visible
Actual Result:
Category dropdown menu is briefly visible when navigating back from an image
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/6a86a6f7-2cf4-4738-9d3b-48e3fafb942a
View all open jobs on GitHub

@CortneyOfstad  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Hi! I am Adam from SWM, an expert agency and I'd like to work on this issue.
cc @luacmartins cause this is Search issue

We have this open issue https://github.com/Expensify/App/issues/49354 that could fix or at least help fix this bug. Let's put this on hold cc @luacmartins

Agreed. Put this issue on hold.

Most recent update for on-hold issue found here!

Latest update is here!

Latest update is here

Latest update is here

No update for the on-hold GH

latest update here
Based on the comment, adjusting this to Monthly 👍


Init libSass submodule when npm installing via git url

This PR fixes npm installs via git urls erring when building the bindings.
When developing on node-sass I often npm install dev branches into my production code to test for regression or other issues. At the moment this require checking in the src/libsass directory, then rebasing that commit out when creating a PR.
This PR makes it so the libsass submodule is checked out as part of the postinstall process. The version checked out denoted by the existing package.libsass flag.
I suggest viewing this diff with whitespace ignored.
/cc @am11

Put some comments inline!

@saper regarding your comments in the commit. The git code path is only hit when install node-sass via git url (which is currently broken) i.e.
npm install sass/node-sass#my/branch

Given this case build.js fails because gyp expect the libsass submodule to exists, which it does when installed via npm. If the src/libsass does not exist we can assume this was a git install not an npm one.
We cannot use a git submodule update because in npm does not maintain the git metadata when install via git. https://github.com/npm/npm/issues/6700#issuecomment-71302066

I was wondering how do we know we checkout via git? Because build.js can be started in the usual npm install case in case the binary does not exist. Requiring git and SSH at this stage would be too much. I need to check what happens to .gitmodules file during npm install from git, maybe we can somehow salvage the problem.
In any case we need not to do this when we want to have node-sass against the external library (like I do for FreeBSD binaries and also for development).

Because build.js can be started in the usual npm install case in case the binary does not exist

If the code is checked out via git or installed via npm (from npm) the src/libsass dir exists. This covers the use cases we expect from our users IMHO.

I need to check what happens to .gitmodules file during npm install from git

npm/npm#6700 (comment)

maybe we can somehow salvage the problem

I'm not following why we would care about .gitmodules, what use case are you addressing?
The libsass version in package.json will always be a tag that is the same commit as the submodule.
The exception being if you're developing on node-sass and have changed the version, in which I like that the package.json is a single point of truth.

In any case we need not to do this when we want to have node-sass against the external library

Do you need to run the build script in this case? What does the work flow look like? I wouldn't expect you to hit this code block unless you were doing an npm install on to a git backend.
Please correct me if I'm mistaken.

Ok, let's do that step by step:
My first failure is probably because I am running csh:
https://gist.github.com/5cdcd0f7133c7c7398b5

Looks like an issue with my usage of join() without a param. It's defaulting to a comma as per the spec.
This wasn't happening for me but since it's the spec I'll patch it.

LIBSASS_GIT_VERSION=,3.2.0-beta.5, ./scripts/git.sh

I believe I have a fix for your issue in https://github.com/sass/node-sass/pull/875. Please confirm?


Scripts with more than 6 inputs fail at the start

Sample:
//name: test Core
//language: javascript
//input: double A1 = 1
//input: double A2 = 2
//input: double A3 = 3
//input: double A4 = 4
//input: double A5 = 5
//input: double A6 = 6
//input: double A7 = 7
//input: double A8 = 8
//input: double A9 = 9
//input: double A10 = 10
//input: double A11 = 11
//input: double A12 = 12
//input: double A13 = 13

Fixed!


-cp2k flag in make.sh

hey all,
just a few quick questions about the -cp2k flag in make.sh. Is it supposed to deliver a cp2k suitable library?
I see that the MNK options are
MNK="
23,
6,
14 16 29,
14 32 29,
5 32 13 24 26,
9 32 22,
64,
78,
16 29 55,
32 29 55,
12,
4 5 7 9 13 25 26 28 32 45"
But in the cp2k's toolchain installer the MNK options are
MNK="1 4 5 6 8 9 13 16 17 22 23 24 26 32"
which are many less, but also different combinations.
Next it sets SSE=3, which according to the makefile.inc and documentation doesn't exist. Only SSE=1 and AVX=1|2|3 exists.
And last, I read Intel optimized and the cp2k.pdf inside documentation says I should have icc. Is it also supposed to work with gcc compiler? I did manage to compile it with gcc. Are there any issues with gcc?
Thank you for any answers.
Johannes

Hello Johannes,
thank your sending your questions!
The MNK options in the make.sh are adopted from https://github.com/cp2k/cp2k/blob/master/cp2k/src/dbcsr/libsmm_acc/libcusmm/generate.py#L19. However, this (or any other statically generated set of kernels) is perhaps not able to "catch them all" but rather aims for being "sufficient for most use cases".
For LIBXSMM, the actual collection of statically generated kernels only matters for systems with no AVX capability (SSE only). This is because the JIT technology is not covering non-AVX (i.e. SSE) when generating a kernel at runtime. I took some effort to support a "general" library which can be deployed to an unknown system environment, see: https://github.com/hfp/libxsmm/#installation.
Please note that the CP2K toolchain installer will be revised pretty soon and then cover the upcoming LIBXSMM 1.2. By then, some of the (now) superfluous flags when building the library can/should be removed.

Next it sets SSE=3, which according to the makefile.inc and documentation doesn't exist.
Only SSE=1 and AVX=1|2|3 exists.

Yes, and the reason is I did not want to give the choice of the kind of SSE level (SSE2, SSE3, SSSE3, SSE4.1, SSE4.2) because the CRC32 calculation requires SSE 4.2. In an earlier version, there was a choice for SSE=x, however it disabled accelerated CRC32 calculations used by the auto-dispatch. Anyhow, I could actually reintroduce this choice because since last week I have implemented CPUID-based dispatch of the code path using the CRC32 instructions. Therefore compiling with whatever SSE support is not affecting the availability of the accelerated CRC32 instructions.

And last, I read Intel optimized and the cp2k.pdf inside documentation says I should have icc.
This is only talking about the CP2K/intel branch. Since CP2K 3.0, LIBXSMM can be used without the code in the Intel branch. However, the CP2K/intel branch remains available and is also using the Intel Software Development tools (compiler) along with some specific ARCH files. This is because, other optimizations might be developed there without interfering with the CP2K development.

Is it also supposed to work with gcc compiler?
Yes, just take the CP2K 3.0 release package for production needs, or the CP2K/master from Git, or CP2K/trunk from SourceForge if you need anything beyond production/released code.

I did manage to compile it with gcc. Are there any issues with gcc?
Absolutely not! Please go ahead and use GCC. Also, LIBXSMM is not depending on compiler optimizations in order to deliver good performance. Our JIT code generator is not affected by the actual compiler used, and also when generating static source code/kernels (non-JIT) it uses inline assembly and therefore is again not affected by compiler optimizations.

Last but not least, LIBXSMM 1.2 is in preparation and CP2K-wise only issue #58 is pending/incomplete.

thanks for all the prompt answers. Almost everything to satisfaction answered :) one remaining issue is gcc compilation. It does compile, however produces f77 warnings upfront (gcc/gfortran 5.3.1):
make AVX=2
f77  -fPIC -ffree-form -O2 -ftree-vectorize -ffast-math -funroll-loops   -D__extern_always_inline=inline -DNDEBUG -D__STATIC -Iinclude -Ibuild -I/home/wagnerjs/programs/source/build/libxsmm-1.1.1/src -mavx2 -c include/libxsmm.f -o build/libxsmm-mod.o -J include/
f77: unrecognized option -J' f77: include/: linker input file unused because linking not done f771: error: invalid option avx2'
f771: error: unrecognized command line option "-ftree-vectorize"
Makefile:266: recipe for target 'include/libxsmm.f' failed
make: *** [include/libxsmm.f] Error 1
upon 2nd run it goes ahead and creates cc compiled code. Is that a known issue?

This problem is related to issue #58, and it will be fixed today. If you cannot wait (but still want the latest), you can do the following (beside of getting the last release):
$ git clone https://github.com/hfp/libxsmm.git ; cd libxsmm
$ git reset --hard f27d830

make AVX=2
f77 -fPIC -ffree-form -O2 -ftree-vectorize -ffast-math -funroll-loops -D__extern_always_inline=inline -DNDEBUG -D__STATIC -Iinclude -Ibuild -I/home/wagnerjs/programs/source/build/libxsmm-1.1.1/src -mavx2 -c include/libxsmm.f -o build/libxsmm-mod.o -J include/
f77: unrecognized option -J' f77: include/: linker input file unused because linking not done f771: error: invalid optionavx2'
f771: error: unrecognized command line option "-ftree-vectorize"
Makefile:266: recipe for target 'include/libxsmm.f' failed
make: *** [include/libxsmm.f] Error 1

This looks like an extremely outdated GNU Fortran compiler version (version 3.x?). It appears this is not only caused by implying Fortran 77 compatibility ("f77") but also due to AVX2 being unknown (-mavx2). Please note, LIBXSMM's Fortran requirement is the Fortran 2003 standard. There is currently no support for those who want F77. In your case, this aforementioned "f77" compiler should also cause problems with building CP2K. If this was not the case, it somehow caused LIBXSMM to rely on the f77 compiler. By default the Makefile uses the "FC" variable, if this picks "f77" in your case I will revise relying on FC (Makefile), and perhaps fix it up to check for gfortran.
I think the following will help with the reported issue:
make CXX=g++ CC=gcc FC=gfortran AVX=2

As of commit 5e8e152 (current master), there have been a number of improvements made of the build system. For example, the aforementioned "f77" issue should now be covered by appropriate warning message when building LIBXSMM.

yes is solved on linux. Building on OS X however is different result. Using the system compilers (Apple LLVM version 7.0.2 (clang-700.1.81))
gives at first a similar fortran linking error:
sed: 1: "include/libxsmm.f": command i expects \ followed by text
make: *** [include/libxsmm.f] Error 1
and upon 2nd run it does compile. But using gnu compilers on OS X (gcc-5 (Homebrew gcc 5.3.0) 5.3.0) gives the former plus this in the middle:
gcc-5  -Wall -Wno-unused-function -Wno-attributes -fPIC -O2 -ftree-vectorize -ffast-math -funroll-loops   -D__extern_always_inline=inline -DNDEBUG -D__STATIC -Iinclude -Ibuild -I/Users/install/libxsmm-1.1.1/src -msse4.2 -c /Users/install/libxsmm-1.1.1/src/libxsmm_dispatch.c -o build/intel64/libxsmm_dispatch.o
/Users/install/libxsmm-1.1.1/src/libxsmm_dispatch.c: In function 'internal_build':
/Users/install/libxsmm-1.1.1/src/libxsmm_dispatch.c:334:7: note: #pragma message: ====================================================================
LIBXSMM_MESSAGE("====================================================================")
^
/Users/install/libxsmm-1.1.1/src/libxsmm_dispatch.c:335:7: note: #pragma message: Adjusting THP is unavailable due to C89 or kernel older than 2.6.38!
LIBXSMM_MESSAGE("Adjusting THP is unavailable due to C89 or kernel older than 2.6.38!")
^
/Users/install/libxsmm-1.1.1/src/libxsmm_dispatch.c:336:7: note: #pragma message: ====================================================================
LIBXSMM_MESSAGE("====================================================================")
^

right, indeed I didn't set FC on linux. On OS X it automatically picket gfortran, on linux it defaultet to f77 insteast of gfortran 5.3

Well, test coverage on OS X is currently weak. In fact, we only test against Clang under Linux. I will look into OS X coverage and testing but this is not top-priority right now (nevertheless I will try to do this before LIBXSMM 1.2). I guess you've noticed https://github.com/hfp/libxsmm/blob/master/Makefile.inc#L5 already?


Computer cannot communicate with itself without an active TurtleBot while using the new discovery server setup

Robot Model
Turtlebot4 Lite
ROS distro
Humble
Networking Configuration
Discovery Server
OS
Ubuntu 22.04
Built from source or installed?
Installed
Package version
Computer is at the most recent updates through apt and does NOT have the new turtlebot4_setup package (still at version 1.0.3).
TurtleBots are at the most recent updates through apt and uses the new turtlebot4_setup (version 1.0.4).
Expected behaviour
The desktop can do anything ROS 2 related fine on its own.
Actual behaviour
The desktop is unable to see any other ros2 topics, nodes, etc. that are launched on the desktop. This problem happens when there are no active TurtleBots. In addition, I commented out the source /etc/turtlebot4_discovery/setup.bash from .bashrc and all ros2 functionality returned after restarting the computer; the problem reoccurred after adding the phrase back in.
In addition, I found that if you connect a single TurtleBot with the discovery server (which works well!) to the base station, then turn the TurtleBot off, the topics get stuck on the desktop.
Error messages
No error messages, you just can't see any topics or nodes.

To Reproduce

Configure the new discovery server on multiple TurtleBots (I am using 2 TurtleBot Lites) as described in the new discovery server documentation
Run the wget -qO - https://raw.githubusercontent.com/turtlebot/turtlebot4_setup/humble/turtlebot4_discovery/configure_discovery.sh | bash <(cat) </dev/tty command found in the new discovery server documentation
Turn off the TurtleBots and ENSURE that no TurtleBot is connected to the network
Try running a program like ros2 run demo_nodes_cpp talker and, in a seperate terminal, run ros2 topic list to see the problem

Other notes
Otherwise this update is working quite well. I am going to ping @hilary-luo just because I know you worked on this, so it is possible there is some nuance that I missed (hoping this isn't a bug and I just messed up)! If there is any other information that you need from me, just let me know!

Hi there
I had same problem. I have temporary solution to use previous version manualy so share as a reference.
Robot Model
Turtlebot4 standard
ROS distro
Humble
Networking Configuration
Discovery Server
OS
Ubuntu 22.04
Built from source or installed?
Installed

Temporaly solution
I cloned directly this repository and copied it to ´/tmp´ dir (under the root)
Checkout to the previous commit "3c033b4", and run directly like
´pi5@pi5:/tmp/turtlebot4_setup/turtlebot4_discovery$  bash configure_discovery.sh | bash <(cat) </dev/tty´
Then it works.
I guess that ip routing setup maybe not setup correctly with newer version script.

Hi @hama6767, thanks for the temporary solution; I will try this later today.
Before I go on with it, did you run the clone, checkout, and command on the raspberry pi of the TurtleBot or your own personal desktop?

@WallerJonathan
Hi Jonathan,
Sorry it is little bit confusing.
I use another pi as host computer. So in your case, you just do same thing on your laptop/desktop.

@WallerJonathan Apologies on the delay of my response. Somehow I missed this notification.
What you are describing sounds like expected operation so I will share some information and then you can judge whether the performance that you are seeing aligns:
When you set up your robot and remote PC for discovery server what you are doing is that you are telling all ROS 2 nodes to use that particular server to discover other nodes. Although with the Turtlebot 4 product we try to streamline this setup process for you, it is a piece of core functionality of the ROS 2 FastDDS middleware. This does indeed mean that having your computer set up for discovery server means that any ROS 2 nodes started on the computer will only report their discovery info to that server and will only be able to discover other nodes using that server. Your options are either 1) always have a turtlebot running or b) add a local server on your PC that you run whenever you want to operate without the robot (your computer can look for both simultaneously and both servers can be on simultaneously but that does have other implications) or 3) you can actively switch between discovery server and simple discovery by changing what you have sourced in your terminal.
@hama6767 If you are using the latest software that is not yet available through apt then please also use the latest documentation in this PR: https://github.com/turtlebot/turtlebot4-user-manual/pull/22/files#diff-c723a483ece2a309b187f43ee7bf4faa020e6ea9c51e4d29bced9c2ba55f7c8f The documentation does go through why IP route is no longer used and the setup tool will remove the historical create3 routes that were created. If you are having issues with it then it probably means that you did not update your turtlebot4_robot package to align with the new setup package. The changes rely on each other. Do note, no matter the IP routing, that will not change how discovery server works and that it needs a server present.


maint: Prompt check of public repo during ref resolution

Resolves #1658
Instead of prompting the user to check if the URL for their repo is public only if it is not on GitHub and if all other resolution has failed, escalate prompting the user to check if the repo is public as soon as there are ref resolution problems.

(Rebased to bring in the pre-commit fix as a fixup to avoid extra commit noise. Sorry for any noise.)

@consideRatio as it looks like you're the current maintainer this is passing CI and ready for review. :+1:


how to use buildin function like Date()

example sql like
SELECT (Date(created_at)) AS `date`, COUNT(id) AS count FROM demo WHERE uid IN (1,2,3) GROUP BY (Date(created_at));

And is there any way to directly execute raw sql like sql.DB().Exec('sql')

I do not think it is possible. You can open a connection with standard sql package and afterwards hook that up with ent. Raw sql can then be run against the db like you usually do.
import "entgo.io/ent/dialect/sql"

driver, err := sql.Open("mysql", util.MysqlDSN())
if err != nil {
	panic(err)
}
defer driver.Close()

driver.DB().Exec('sql')


[F1 2019] Added drivers for the 2019 version

Added all new driver names based on the Codemasters docs https://forums.codemasters.com/topic/38920-f1-2019-udp-specification/?do=findComment&comment=434628
I used the first 3 characters of the last-name for all abbreviations, though there is at least one abbreviation that can easily be "misinterpreted", 52: {abbreviation: 'FUK', firstName: 'Nirei', lastName: 'Fukuzumi'},.
If there is an "official" list of these abbreviations I'm happy to update the PR.

Didn't see that someone already did this lol

I did :P


server: OLLAMA in modelfile and manifests

new optional parameter OLLAMA in modelfile to specify minimum version of ollama to run this model:
ollama create newmodel
FROM mymodel.gguf
OLLAMA 0.2.3

using another model with the FROM command defaults to the version if they specify it right now. otherwise, you can set it yourself
FROM newmodel

this will inherit the OLLAMA 0.2.3 requirement

I don't think OLLAMA as a command feels very intuitive, and I'm a little worried this paints us into a corner. Does this only work with versions >= the version specified? What if I want it to only work with versions less than a given version?


Documentation on tracking a basic event is wrong

In the README in GitHub for Amplitude SDK for Node.js  you write:
// Track a basic event
track('Button Clicked');

However, this won't work as you are expecting a user_id or device_id:
Amplitude Logger [Error]: Request missing required field
Amplitude Logger [Debug]: {
  "type": "invoke public method",
  "name": "track",
  "args": [
    "Button Clicked"
  ],
  "stacktrace": [
    "at Analytics.trackMessageInference (/Users/aleppard/frank/one/Frank_Slack/queue_consumer/dist/.common/analytics.js:28:36)",
    "at Object.run (/Users/aleppard/frank/one/Frank_Slack/queue_consumer/dist/runSlackMessageInference.js:107:19)",
    "at processTicksAndRejections (node:internal/process/task_queues:96:5)",
    "at async handleSQSEvent (/Users/aleppard/frank/one/Frank_Slack/queue_consumer/dist/app.js:51:13)",
    "at async poll (/Users/aleppard/frank/one/Frank_Slack/queue_consumer/dist/poll.js:47:9)"
  ],
  "time": {
    "start": "2023-03-22T22:49:19.052Z",
    "end": "2023-03-22T22:49:29.876Z"
  },
  "states": {
    "before": {
      "config.apiKey": "b8e03107dbf9088cf67165fca4ae0eab",
      "timeline.queue.length": 0
    },
    "after": {
      "config.apiKey": "b8e03107dbf9088cf67165fca4ae0eab",
      "timeline.queue.length": 0
    }
  }
}

The documentation elsewhere looks like it might be right:
// Track a basic event
track('Button Clicked', undefined, {
  user_id<EMAIL_ADDRESS>});

@andrewfrankcare good catch! Docs here needs an update. For Node SDK, user id or device id or both must be specified.

@andrewfrankcare thank you again for pointing this out. I link the PR that resolved this issue. Closing now!

Just curious if you have any plans on supporting setting the user_id or device_id in the init method for the node SDK like the the browser SDK? It's a bit of a pain to pass the user_id in every single event.


Last checks to documentation before release

Fix completion insert autoremoval
Update readline doc
Update README
don't include group headers with no results in comps in isearch
Add some history widgets
Add some missing line widgets
Update default config and doc
Fix completion offsets
Trimmings
Enhance completion space estate
Fix async log usage of get-cursor-pos
Added some code (commented out) for autopair insert

Codecov Report
Base: 0.00% // Head: 0.00% // No change to project coverage :thumbsup:

Coverage data is based on head (3ffddd5) compared to base (d63d2cc).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@          Coverage Diff           @@
##           master     #20   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          42      42
  Lines        6468    6474    +6
======================================
- Misses       6468    6474    +6

Impacted Files
Coverage Δ

standard-widgets.go
0.00% <ø> (ø)

vim-utils.go
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Create 1882-process-tasks-using-servers.java

File(s) Modified: 1882-process-tasks-using-servers.java
Language(s) Used: Java
Submission URL: _https://leetcode.com/problems/process-tasks-using-servers/submissions/954222134/_

Important
Please make sure the file name is lowercase and a duplicate file does not already exist before merging.

Looks good, thanks !


Feature Request: Support Docker BuildKit secrets when building

Currently when using this plugin to build the Docker image, there is no safe way to pass secrets while building. In my case, I'm trying to pass the Drone's .netrc file to the image so I can clone a private git repo inside the Dockerfile.
It's implemented in drone-plugins/drone-docker, It supports secrets_from_env, secrets_from_file and the raw secret key-pair in settings.

#282 Resolves this.


chore(build): added sourcemap generation for cjs build

Before submitting a pull request, please make sure you have at least performed the following:

[X] read and followed the CONTRIBUTING.md guide.
[X] built and tested the changes locally.
[X] added/updated any applicable tests.
[X] added/updated any applicable API documentation.
[X] added/updated any applicable demos.

fixes #322

That works, thanks.
I was fixing it right now but I guess you were faster.

oops sorry


fftw: 3.3.6-pl1 -> <IP_ADDRESS>

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Could you fix the version number in the commit message (and in the title of the PR)?

@orivej oops. done.

@GrahamcOfBorg eval

@GrahamcOfBorg eval

@orivej @grahamc I'm not sure what ofborg is yet, but while reading the readme, I saw:
be gentle, preferably don't run mass rebuilds / massive builds like chromium on it

This triggers all browsers + libreoffice, plus other stuff.
Last time I updated this, I marked it as mass-rebuild, but that was considered over the top then, but you might want to reconsider ofborg.
I'll go back to reading what ofborg actually is now... ;)

ofborg is two things: 1. it runs builds (by request, ie: @grahamcofborg build foobar will have it build foobar and report the results.) the second is it automatically runs eval checks ... but I was a dinkus and accidentally ran a beta version which marked all your PRs as broken :) eval can / does run on every PR ,regardless of mass rebuild status.

@grahamc thanks. so it's kind of the nixos version of travis?

Exactly! We used to use Travis but it was very unpleasant and ineffective
for a project like NixOS.
On Fri, Dec 8, 2017 at 5:16 PM Bart Brouns<EMAIL_ADDRESS>wrote:

@grahamc https://github.com/grahamc thanks. so it's kind of the nixos
version of travis?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/32476#issuecomment-350385908, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAErrAE_5nxSR8sBTyIcqYidjySw18sRks5s-bU8gaJpZM4Q7pTA
.


Updated README.md - Added Streamlit based WebApp 👨💻✅

Hi @akshaybahadur21,
Kudos to you for bringing up this simplistic demo of 3D Object Tracking using Mediapipe and Objectron. I worked on developing a simple streamlit based webapp on the same and I think it will be fruitful to have it as a part of README here as the motivation behind developing this came from your work 😄!
Title: Streamlit based 3D Object Tracker using Objectron
Github Repo : https://github.com/prateekralhan/Streamlit-based-3D-Object-Tracker-using-Objectron
Happy opensourcing!

Love this implementation.


Fix type hints.

Mostly adding Optional[] or turning list to list[str]. Chenged int in purchase_loan to Decimal.

Everything looks good to go except the type hints for the lists

Good catch

I'll deploy the new package version once all the PRs are merged.

If you don't mind, I'd like to add cache-less get_globals() to the API before that.
I have a long running app and I'd like to refresh originators every now and then

Thanks for submitting the PR. Everything looks good now, so I'll merge it and deploy the new package version.


MSVC errors on build server

As a tester I want MSVC errors to be generated and logged on the build server.

Might not be possible, return to this when the Sonar-Cxx team has had a look at stuff.


LayoutBuilder should cache constraints and not rebuild if unchanged

Run the following and then tap the screen - you'll see that the print occurs each tap.
I don't expect that print to output more than once.
Future main() async {
  GlobalKey _simKey = new GlobalKey();

  runApp(
    new Column(
      children: [
        new Flexible(
          child: new LayoutBuilder(
            builder: (_, BoxConstraints constraints) {
              print('LayoutBuilder build $constraints');
              return new Foo(key: _simKey);
            },
          ),
        )
      ],
    ),
  );
}

class Foo extends StatefulWidget {
  Foo({Key key}) : super(key: key);
  @override
  FooState createState() => new FooState();
}

class FooState extends State<Foo> {
  Color _color = newColor;

  void swap() => setState(() {
        _color = newColor;
      });

  @override
  Widget build(_) => new LayoutBuilder(
        builder: (__, ___) => new GestureDetector(
              onTap: swap,
              child: new Container(
                decoration: new BoxDecoration(backgroundColor: _color),
              ),
            ),
      );

  static Color get newColor => new Color(new Random().nextInt(0xFFFFFFFF));
}

Ah, thanks for this example.  What's happening is the LayoutBuilder in FooState needs to rebuild, which means it provokes a layout on itself, which causes the LayoutBuilder with the print to also go through layout because there's no layout boundary between them.

It's interesting that in this case Foo will build twice.  Once because of its setState and once because its parent rebuilt during layout.  Normally it would only build once because its parent would rebuild before we got around to processing its setState rebuild.
/cc @Hixie

I think it would be reasonable for LayoutBuilder to cache its BoxConstraints and only call the builder again if the constraints change or it went through update.
This example does point to another issue with LayoutBuilder.    Maybe our walk-pruning in layout is enough to make that ok.  It's probably worth studying this example to see how many unnecessary objects we actually visit in layout.

Yeah the double rebuild is expected behaviour. @HansMuller  and I looked at it a lot back when he was trying the "inheritance link parent" idea and when I was working on LayoutBuilder bugs. We concluded there was not much to be done about it.
I agree that we should cache the constraints and not rebuild if they didn't change.
We can't avoid the other problem with the way this example is written, because we've no way to know if the callback has changed. We could use a delegate instead of a callback, though. That would make LayoutBuilder more awkward to use but more efficient.

Anything I can do to help fix this issue?  I actually tried to cache the constraints in my local version of flutter but I ran into the issue @Hixie described, the children in the builder callback wouldn't get rebuilt even if some state they depended on had changed.

I've 'fixed' this issue in my app by applying tight constraints to my LayoutBuilder so reducing priority.

Hello,
I have one more example that seems to be related, but in this case more critical:

In general you should assume that build methods will be called excessively. If that's a problem, use a stateful widget and cache the widget you return from build, so that it gets short-circuited next time.

@Hixie Could you explain how exactly? I'm not sure I follow.

class _FooState extends State<Foo> {
  Widget _child;
  Widget build(BuildContext context) {
    _child ??= Container();
    return _child;
  }
}

I was wandering why my widgets were always rebuilding!
ended up creating a Cached version of the layout builder that takes external parameters to check for rebuild:
import 'package:flutter/widgets.dart';

class CachedLayoutBuilder extends StatefulWidget {
  final Widget Function(BuildContext context, BoxConstraints constraints)
      builder;
  final List<dynamic> parentParameters;

  const CachedLayoutBuilder({Key key, this.builder, this.parentParameters})
      : super(key: key);
  @override
  _CachedLayoutBuilderState createState() => _CachedLayoutBuilderState();
}

class _CachedLayoutBuilderState extends State<CachedLayoutBuilder> {
  Widget previousBuild;
  BoxConstraints previousContraints;
  List<dynamic> previousParameters;

  @override
  Widget build(BuildContext context) {
    return LayoutBuilder(builder: (ctx, constraints) {
      var parametersIdentical = true;
      if (previousParameters == null ||
          widget.parentParameters == null ||
          previousParameters.length != widget.parentParameters.length) {
        parametersIdentical = false;
      } else {
        for (var i = 0; i < previousParameters.length; i++) {
          if (previousParameters[i] != widget.parentParameters[i]) {
            parametersIdentical = false;
            break;
          }
        }
      }
      previousParameters = widget.parentParameters;
      if (!parametersIdentical || previousContraints != constraints) {
        previousBuild = widget.builder(ctx, constraints);
        previousContraints = constraints;
      }
      return previousBuild;
    });
  }
}

not very clean but does the job

@neckaros I believe your solution breaks if the builder function inherits something from the BuildContext, such as Theme.of(context) (or anything else published by an InheritedWidget).


Make RegexpNode aware of fixed-encoding regopt

Resolves https://github.com/rubocop/rubocop/issues/10552.
This PR makes RegexpNode aware of fixed-encoding regopt.

@marcandre Can you review this PR?

@marcandre ping :-)

Sorry I missed the notifications @koic
Release 1.20.0


feature-website

Add a basic website using docusaurus

It won't build at mine, since you need to explicitly set GH org and repo name for it to work. There is a docusaurus-friendly way of doing the deploy, and I will look into it, but for now, this should work.

Okay, I took my time and tested their recommended way of deploying the website. The CI is prefilled to work on THIS REPO (valence-rs/valence) and YOUR DOMAIN (https://valence.rs) so you should point a CNAME from WWW and @ (root) to valence-rs.github.io now, or before merging. Also enable github pages from the gh-pages branch in repo settings. If you want, this is what I came up with. And here's the source.

It's in settings->pages, you don't need to set the custom domain there, it will be automatically set by this workflow. Just let it run and when you have a gh-pages branch, set it, and /(root) as the source.

Closing in favor of #382
I'm sad nobody mentioned their initiative to create something else instead.


Go vet on enter?

Information
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Nov 29 2017 18:37:46)
Included patches: 1-503, 505-680, 682-1283

Operating System: Linux Mint 18.2 / MacOS High Sierra 10.13.6
:ALEInfo
  Current Filetype: go
Available Linters: ['gobuild', 'gofmt', 'golangci-lint', 'golint', 'gometalinter', 'gosimple', 'gotype', 'govet', 'golangserver', 'stati
ccheck']
   Linter Aliases:
'gobuild' -> ['go build']
'govet' -> ['go vet']
  Enabled Linters: ['govet']
 Suggested Fixers:
  'gofmt' - Fix Go files with go fmt.
  'goimports' - Fix Go files imports with goimports.
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
 Linter Variables:

let g:ale_go_govet_options = ''
 Global Variables:

let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%code: %%s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 100
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'always'
let g:ale_lint_on_insert_leave = 0
let g:ale_linter_aliases = {}
let g:ale_linters = {'go': ['govet']}
let g:ale_linters_explicit = 0
let g:ale_list_window_size = 10
let g:ale_list_vertical = 0
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 1
let g:ale_sign_error = '>>'
let g:ale_sign_info = '--'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '>>'
let g:ale_sign_style_warning = '--'
let g:ale_sign_warning = '--'
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(executable check - success) go
(finished - exit code 0) ['/bin/zsh', '-c', 'cd ''/Users/addy/go/src/github.com/woat/supatc/gui'' &&  go vet .']

<<<NO OUTPUT RETURNED>>>

What went wrong
Go vet does only runs on save regardless of let g:ale_lint_on_text_changed = 'always'. I understand that w0rp/ale#1356 was a fix for the package update on go vet and was proposed to run on save. But is there anyway to allow this to continue linting on text changed? Or is this not to be implemented because of a foreseen performance hit?
Reproducing the bug

Open sample .go file in vim using default ale go linters (gofmt, golint, govet) and ensure let g:ale_lint_on_text_changed = 'always'.

package main

import "fmt"

func main () {
    fmt.Println("x")
}

Delete the f in func to show unc.
Without saving, notice gofmt's error: expected declaration, found unc
Undo step 2.
Now delete the rintln in fmt.Println("x") to show fmt.P("x").
Notice there is no error in the gutter.
Save.
Now notice govet's error: undefined: fmt.P.

You can also put let g:ale_linters = {'go': ['govet']} in your .vimrc to isolate govet and run steps 5-8 again to ensure that none of the other default go linters are interfering.

go vet can only be used for checking files that have been saved to disk, like most Go tools.


The balance is sufficient but cannot be transferred

I used an unspent cell to transfer<PHONE_NUMBER> capacity, but the RPC returned Error: {"code":-3,"message":"Transaction(InsufficientCellCapacity)"}.
The picture below is my transfer capacity (0xcc1e5560 -<PHONE_NUMBER>):

Below is the available cell I queried using loadCells(0x8bb2c97000 -<PHONE_NUMBER>00):

This is RPC respoonse result:

The minimum capacity to generate a cell with the system script is<PHONE_NUMBER> shannons, which is the volume of an empty cell.

Do I need to use another cell?
No matter how much money is transferred, must it be greater than<PHONE_NUMBER> ?

What if I don't have that much balance?

Do I need to use another cell?
No matter how much money is transferred, must it be greater than<PHONE_NUMBER> ?

Yes, we call 10^8 shannons a CKB, and the cell with the system script requires 40 CKB for containing the system script and 21 CKB for its own fields.

What if I don't have that much balance?

The error above will be thrown if you're using the system script. Or you can use a custom script which is smaller.

How to use a smaller script, is there an example?

The cell I used above is a 6000 * 10^8, It is much larger than 61 * 10^8. Do you mean that the amount of each transfer cannot be less than 61 * 10^8? I only transfer 34.2454 * 10^8.

The cell I used above is a 6000 * 10^8, It is much larger than 61 * 10^8. Do you mean that the amount of each transfer cannot be less than 61 * 10^8? I only transfer 34.2454 * 10^8.

In a nutshell, every cell, or output in the transaction, with the lock script we specified now, should have a capacity larger than 61CKB.
For instance, we cannot split a cell of 91CKB into two cells of [61CKB, 30CKB], the cell of 30CKB will be regarded as invalid.

So how to solve the problem of this transfer 34.2454 * 10^8?

So how to solve the problem of this transfer 34.2454 * 10^8?

Sadly it is impossible to transfer 34.2454 CKB independently. The simplest way to solve it is to ask the receiver to provide another cell to make the output larger than 61CKB.

So how to solve the problem of this transfer 34.2454 * 10^8?

It's not a problem. Take Ethereum for example, if you have an Ethereum account and want to send somebody else Ether, you'll have to make sure your account has more than 21000 Wei otherwise there's not enough gas to make the transaction been sent.
The simplest solution to your problem is to send some capacity to yourself so that balance is above 61 CKB.

OK. Thx. There is no problem with this.


Suggestion: Select tool should not include locked tiles.

It would be nice if the select tool on the attaching UI would avoid including tiles that have been locked. Usually these tiles are permanent fixtures and aren't intended to be moved.

That would make sense yes


convert premiere to pype2

conversion of pype 1.0 integration for Adobe Premirere into pype 2.8.0
dependency:
https://github.com/pypeclub/avalon-core/pull/123
https://github.com/pypeclub/pype-config/pull/19
supporting Premiere 13 and 14.1 with CEP_9.x with Cefclient Chromium compilation for debuging
also rewrite Aport into AdobeCommunicator (pype rest api server)
resources:
https://github.com/Adobe-CEP/CEP-Resources/blob/master/CEP_9.x/Documentation/CEP 9.0 HTML Extension Cookbook.md
https://github.com/Adobe-CEP/Samples/tree/master/PProPanel
https://github.com/Adobe-CEP/CEP-Resources/blob/master/CEP_7.x/CEP_7.0_HTML_Extension_Cookbook.pdf

I'm happy to merge this. @jezscha it has been tested on-site right?

I'm happy to merge this. @jezscha it has been tested on-site right?

yes it is working with #38  included


Support non-pip conan installation

The extension currently fails to function if Conan has been installed using one of the alternative installers, i.e. not as a pip package. E.g. on my system, Conan is at C:\Program Files\Conan\conan\conan.exe and is in the PATH but a command like python -m conans does not work.
If there are technical reasons why a pip installation is required and alternative installers cannot be supported, I suggest to at least make that fact clear in the README and ideally showing a more helpful error message when the pip package cannot be found.

Thanks for the input.
Basically there is no technical limitation and problem about using alternative installation, I only implemented python interpreter based on common usage of conan, and it was the initial implementation (kinda of brute force style).
And the Conan API class was badly implemented, but now its changed in the develop branch, it makes even easier to implement this option using the conan executable directly.
What I am going to with this, is to provide option in the settings.json to switch between python and conan executable.

What I am going to with this, is to provide option in the settings.json to switch between python and conan executable.

Great, thanks! Ideal IMO would be if the extension chose appropriate settings automatically if the user has not configured it explicitly, e.g.:

if "conan" is on the PATH, use it, else fall back to python -m conans

I would say the requested feature is already implemented. I tested it with conan alternative installation, in this executable in windows environment.
Feel free to try it, currently only available in the feature branch https://github.com/afri-bit/vsconan/tree/feature/%2314_support-non-pip-conan-installation
You have to configure the VS Code settings.json

If we are happy about that, I will close this ticket and merge it to develop branch.

Cool, that was quick!

That could be working, but I prefer to give flexibility to the user, so if you have multiple conan installed on your pc, you can switch the conan executable within the VS Code instead of struggling with environment variable.

Yes, I agree with you on giving users the option but I think we could have the best of both worlds, i.e. if a user only has conan in PATH but not installed as a pip package, or the other way round, the extension could be smart enough to choose the right mode without requiring the user to set anything in the settings.
For example, conanExecutionMode could have a third option "auto" which is the default setting. In auto mode, the extension could pick whatever mode works on a user's machine. Advanced users would still have the ability to override and enforce one particular mode, and for new users it would remove one potential hurdle from getting the extension working.

Thats a great idea.
I will create a separate ticket for this topic.
As for now I will leave this implementation as it is, at least I think I will set the execution mode to conanExecutable as default, since even someone installs conan using pip, he/she can use conan using simple command conan.

#15


gmenu.inc - New bug detected

hello dude.
i found a new bug on gmenu include yesterday and i emailed you it on skype.
and its -> on scrolling bettwen ittems on my menus it always return my non-respone message --> 'order canceled' please fix that bug soon sir
i mean on switching between my items on my menus and betwen my menus it always returns both of my non-respone message -> 'Order Canceled' & respone codes 'you have just bought this weapon for .....$' please fix this bug soon sir.....

Hey sorry for late reply. But i couldn't get the problem.
Is it a response related issue; related to "OnMenuResponse" values?

it might be related to the 'OnMenuRespone' Values.

Ok, can you give me a sample code you use to interact with gmenus. So that i can test on my machine and see if the issue still exists. It will help me find out the problem.

sent you it on skype

waiting for any kind of replies or bug fixs.....

Sorry, i am pretty busy in real life. I just made an update for dialogs. This will be next.

All the bugs should be fixed in the new version.
Thanks


Move registry to kube-system namespace and add wait for running pod

If pod creation is slow (like vagrant dev env) start-registry.sh will fail. I added wait cycle.

Now KubeRegistry available as cluster addon:

$ kubectl cluster-info
Kubernetes master is running at https://<IP_ADDRESS>:443
Heapster is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/heapster
KubeDNS is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/kube-dns
KubeRegistry is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/kube-registry

👍


feat: handles unavailable modules

If a module to bundle is not available a throw statement is bundled instead informing the user that
the bundle was not found.

Coverage increased (+0.03%) to 98.851% when pulling a5c77e6419c71b9eb8da61c3aa00367ca5211c18 on handle-unavailable-modules into 634c6c688efbf7e34a48a262ca40821ed7320f73 on master.


Wrong literals in function call

https://github.com/hyroge/libaria2-ts/blob/00a8265fdd8946b16b1ff93296df0b4df121cf8d/src/adapter.ts#L179-L184
Line 181 should be replaced with:
"aria2.getFiles",
https://github.com/hyroge/libaria2-ts/blob/a070137aa5d1090b27354339fa82c9c47d75dd84/src/adapter.ts#L200-L207
Line 202 should be replaced with:
"aria2.getServers",

thanks, i will fix  it

it fixed in ecc8f786b8ae16d2e571f7e24bcc600c52b9ae74


Exception in runtime

Desharp.Debug.Dump(ex) causes:
{System.TypeLoadException: Could not load type 'System.Web.Hosting.HostingEnvironment' from assembly 'System.Web, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.    at Desharp.Core.Dispatcher..cctor()} | System.Exception {System.TypeLoadException}
Environment: ASP.NET core

Hi,
I'm very sorry, but the Desharp library is not rewritten into .Net Core. You could run it only in .NET Framework Environment.
Maybe I'll find some time in future:-(


Error in "python squelch_table_read.py"

Hello. Help me please. When trying to read, the following error appears:

Dude, are you alive?

Wow, what a relief! I was starting to worry that my lack of response for a whole three days might have indicated that I must've passed away. But fear not, I am indeed alive and well!
Now, let's address your issue. It seems like you've stumbled upon a problem that arises because libuvk5 doesn't consider OSFW version numbers, since it was made before OSFW reported version numbers that didn't fit the format of the stock Quansheng firmware.  Clearly, the author should have anticipated every possible scenario known to mankind.
Unfortunately, I regret to inform you that I am not at your beck and call 24/7. You see, I have this thing called a life, which occasionally demands my attention.  I know, I know, it's quite outrageous. So, while I appreciate your urgency, I'm afraid I don't have the time to delve into this matter right now.
However, fear not! If you strain yourself to wait patiently for just a little bit longer, @amnemonic may eventually find a moment to address this issue with the library that this script depends on. Until then, I suggest you explore other avenues or perhaps even contribute a fix yourself, over at https://github.com/amnemonic/Quansheng_UV-K5_Firmware/blob/main/python-utils/libuvk5.py. After all, we're all just trying to survive in this chaotic world where Python scripts don't quite yet cater to every minute detail of our lives.
Best of luck with your endeavors, and may you find solace in the fact that I am indeed alive (for now).

Ohhh... Thank you for such a long and wonderful story. You spent a lot of time writing a novel about your life instead of trying to correct a mistake. I was very interested to know the details of your life (no). I will continue to look for a solution to the problem with these scripts. But anyway, thank you very much for these scripts, according to reviews they help people fix the problem with the squelch.

Stop demanding that people who do stuff for free, in their spare time, fix stuff on your schedule. Not to mention that what you outlined is not a problem in my code.
I gave you all of the details – if you want it fixed on your terms, fix it yourself.


I would like to see this in the css

But feel free to change anything if you want to. It would be really nice if you added this into the project.
Its a very impresive project and good luck making more additions to this great framework.
The thing is i don't really know how to change this feature in the variables css file. But i hope you can help with that.

#56


Store session cookies and proxy

Hi, Session cookie is not set in browser when I am using proxy
ng serve --proxy-config proxy.conf.json

proxy config:
{
  "/api": {
    "target": "https://test.org",
    "secure": false
  }
}

javascript:
const body = new window.URLSearchParams();
body.set('username', credentials.username);
body.set('password', credentials.password);

let loginHeaders = new Headers();
loginHeaders.append('Content-Type', 'application/x-www-form-urlencoded');

this.http
      .post(`http://localhost:4200/api/auth`, body.toString(), {
        headers: loginHeaders,
        withCredentials: true
      })

How can i set up proxy to store the session cookie in browser? What I am doing wrong?
OS?

Windows 10

Versions.

angular-cli: 1.0.0-beta.24
node: 6.9.1
os: win32 x64

Not 100% sure if this will work, but did you try
"changeOrigin": true
{
  "/api": {
    "target": "https://test.org",
    "secure": false,
    "changeOrigin": true
  }
}

Also if you could provide all the headers received when you call the api, that will help investigate.

@matodrobec Please try mmrath's solution above to see if it works. If not, you can let me know and I'll re-open this issue. Thanks!

@mmrath Thx. I am tested your solution but it is still not working. The session cookie is not stored in browser and the server generate always new session cookie for each request.
My hotfix is
document.cookie = `JSESSIONID=${this.env.sessionCookie}; path=/`;

Now I ask provider api and I would like to use this solution
https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS#Requests_with_credentials but do not forget read note in "Important note" about setting  Access-Control-Allow-Origin
But also will be good to know how to set up proxy to store session cookies.

I'm having the same exact problem, cookies set by the service aren't being set in the browser for subsequent calls.
My json looks like the following:
{
"/rest/*": {
"target": "http://localhost:8080/",
"changeOrigin": true,
"secure": true,
"logLevel": "debug"
}
}
I've tried with both secure true and false, neither helps.  I've also started Chrome with the --disable-web-security flag
This is using<EMAIL_ADDRESS>

Any update on this issue?
I have the same problem the secure headers which are coming in the response form server are not send back in request after authentication.

I too have the same problem, JSESSIONID is not set in browser when api requests are proxied.
Any help is much appreciated.

Same problem here. Angular CLI 1.0.0-rc.2

@hansl Is it possible to reopen this issue because its still a problem for some of us

@gseabrook I have not looked deep enough but i think it is probably how webpack dev server proxy works. CLI uses webpack underneath, if you can provide a repo where it works with webpack for a similar setup, I might be able fix in CLI.

Hi,
I have converted my project to CLI. But i am having this error while running proxy.
[HPM] Proxy created: /api -> https://test.org
[HPM] Subscribed to http-proxy events: [ 'error', 'close' ]
[HPM] GET /api/generics-management/getCategoryList -> https://test.org
[HPM] Error occurred while trying to proxy request /api/generics-management/getCategoryList from localhost:4200 to https://test.org (ECONNREFUSED) (https://nodejs.org/api/erro...
Can you please help?

Hi,
We are currently experiencing the same issue.  We are using Angular 2 with the the CLI (v2.4.10), with  the proxy.conf.json.  The session cookie is not being stored in the browser.
We do have the "changeOrigin": true value set, as suggested in this thread above.  I see this issue has been closed.  Does anyone have a fix?
Thanks!

Experiencing same problem. Issue needs to be reopened.
Anyone have suggestions for a workaround?

I bumped into the same issue for our project and spent the whole day to tried different combinations, and finally make it works. Here is the summary to feedback to the community and hope it can save you a few hours.
when deploying AOT angular 4 project into the same tomcat container hosting backend restful API, the JSESSIONID is sent back after logged in. But when using proxy, to forward backend API from developer box webpack dev server to tomcat server, JSESSIONID is lost, tomcat treats every request is a new request. In webpack dev node server, we use http and tomcat server we use https, it looks like JSESSIONID can not carry over across http --> https. By setting breakpoint after login, try to get JSESSIONID cookie manually via browser debug console and it returns null, but in the login restful API, response header shows: Set-Cookie:JSESSIONID=EEE46B0120F10BA6939EAB2F8AD2CA44;path=/;Secure;HttpOnly
My initial tries to change our spring boot configuration: server.session.cookie.secure=false to hope it can force JSESSION not secure to UI, but it seems no effect if SSL is on.
Then tries to add response headers " Access-Control-xxx" at server side, and "withCredentials=true", "X-Forwarded-Proto=https" for angular request headers, and try to configure "cookieDomainRewrite" in proxy.config.json file, but none of them work.
At the end, I created a self signed cert with openssl and enable node dev server to HTTPS, it works perfectly, then I deleted server side response headers and client side request headers, it seems working fine too.
Here are the related factors for working version:

package.json
"start": "ng serve --proxy-config proxy.api.json --ssl true --ssl-key ssl/server.key --ssl-cert ssl/server.crt",
proxy.api.json
{
"/api": {
"target": "https://dit.server:8080",
"secure": false,
"logLevel": "debug",
"changeOrigin": true
},
"/login": {
"target": "https://dit.server:8080",
"secure": false,
"logLevel": "debug",
"changeOrigin": true
},
"/logout": {
"target": "https://dit.server:8080",
"secure": false,
"logLevel": "debug",
"changeOrigin": true
}
}
request headers:
let headers = new Headers();
headers.append("Content-Type", "application/json");
headers.append("Access-Control-Allow-Credentials", "true");
headers.append("Access-Control-Allow-Origin", "*");
headers.append("Cache-Control", "no-cache");      // due to IE browser caches API get requests
spring boot application.properties related to ssl
server.port=8080
server.ssl.key-store=file:///opt/app/dit.jks
server.ssl.key-store-password=****
server.ssl.key-password=****
no response headers added in our Http Servlet Filter class

zpc888's method worked for me. The key item was:
At the end, I created a self signed cert with openssl and enable node dev server to HTTPS, it works perfectly, then I deleted server side response headers and client side request headers, it seems working fine too.

My issue is when my server context is default '/' on spring boot the proxy config works and all request after successful auth call carry the same jsessionid value.
But once say I change my server context to '/abc' then each subsequent request after auth call caries a different jsessionid and hence I get 302 for all request.
I have used 'changeorigin' true also but it did not work. And I am using tomcat on HTTP only.
Any help would be appreciated.

perfect

@zpc888 's technique works. Thanks.
Quick note
The serve command ng serve --proxy-config proxy.api.json --ssl true works too, without requiring the SSL certificate or key, of course except that the browser gives you an "unsafe - caution advised" warning, which does not matter in local env. So once you are past that, you are good to go.
Another lesser-advised alternative
When experimenting, I found that, if your server-side API has auto-redirection of http requests to https handled, then the following works too:
{
    "/api": {
        "target": "http://www.external-api.com",
        "changeOrigin": true,
    },
    ....
}

Note that target protocol is set as http. However, this is totally unsecure, hence avoidable even in dev environments.

I am facing the same issue, trying out the ssl fix. If that works, the reason is (atleast here) simple. The cookies that are set are SSL only cookies. Your request isn't ssl. The browser doesn't send them back.

I am not sure if it's the same problem, but we also have the issue that the browser does not send the cookies.
In our case the app is served by the cli (ng serve --proxy-config config/proxy.conf.json --environment local_dev --port 9000) and runs at localhost:9000. And the backend is our dev system at dev.wayne.com. All api calls go to the dev backend. But since the browser did not send the cookies when calling the backend, we always get a 401.
The solution was to enable the option withCredentials (https://angular.io/api/http/RequestOptionsArgs#withCredentials) in the RequestOptionsArgs (We are using the deprecated @angular/http). Now it works fine.

HI, i have a problem safari on IOS 10.3.3
i using this.cookieService.set ('Test', 'Test token criado'), but only IOS 10.3.3 does not work.
is there work around?
Project angular.
public login(login: Login) {
let headers = new Headers({ 'Content-Type': 'application/json' });
let options = new RequestOptions({ headers: headers });
return this.http.post(${this.config.apiUrl}/account/login, JSON.stringify(login), options)
.map((resposta: Response) => {
if (resposta.status == 200) {
let token = resposta.json() && resposta.json().token
if (token) {
this.cookieService.set('XSRF-TOKEN', this.retornarAntiForgery, dataExpiracao, "/");
}
}
return resposta;
});
}

Hi,
I'm using option.cookiePathRewrite for rewriting the path headers . So, i added this option on my config proxy.Now, the cookie is stored and is sent to each request.

Angular CLI: 6.2.3
Node: 8.11.4
OS: darwin x64
Angular: 6.1.8
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.8.3
@angular-devkit/build-angular     0.8.3
@angular-devkit/build-optimizer   0.8.3
@angular-devkit/build-webpack     0.8.3
@angular-devkit/core              0.8.3
@angular-devkit/schematics        0.8.3
@angular/cli                      6.2.3
@ngtools/webpack                  6.2.3
@schematics/angular               0.8.3
@schematics/update                0.8.3
rxjs                              6.3.2
typescript                        2.9.1
webpack                           4.19.1

I'm proxied to a test server that does not have SSL, so that is not my issue.
I see two 307 redirects in Chrome dev tools Network tab.  They both contain the cookie.  But the final call to the API does not.  401 Unauthorized because the cookie isn't present.

@jkyoutsey I have been noticing something similar in my app as well after the most recent upgrade to Angular 6 (done last week). It definitely must be some configuration issue. In my specific case, it not working even for a production build (ng build --prod - which is then hosted separately/manually in the same web-server my server API resides in, hence no question of domain or SSL setting mismatch). Is your production build working fine?

@kichnan we refined our CORS configuration a bit to be more in line with the spec on MDN.  But the reality was that the API we were calling just wasn't the right endpoint.  I'm not sure our issue is resolved.  But we've gotten past it. That API just was bad on the server side.  All of my other calls are, in fact, passing the cookie just fine.

What's the answer Angular?

+1

+1

Adding some random helper tips to troubleshoot this issue as I can remember them. Hope this helps.

Make sure that the URL you are proxying is accessible.
If you are using ng serve --ssl true, make sure that the proxied server's SSL certificates are valid. For e.g., a self-signed locally generated certificate, though works in a browser, does not work for me in this situation, and especially over a network (LAN or internet).
If you are using --ssl true, ensure that your proxy configurations have them set with "secure": true. Also try setting "changeOrigin": true.
If you are using --ssl true, try keeping the server URL's "target" link as "https://" based even though auto-redirects (from http to https) may have been configured in the server.

I also had this problem, my final solution was this :
{
  "/api": {
    "target": "https://eventbroker-development.azurewebsites.net/api",
    "secure": true,
    "pathRewrite": {
      "^/api": ""
    },
    "changeOrigin": true,
	"logLevel": "debug",
	"withCredentials": true,
	"headers": {"Cookie":".AspNetCore.Cookies=CfDSSPKlUbmmqztPtpwdlsJqOPNIa3pjBw8MxFR4cc0z3cRVJgKDcCKxfxR-f8QEsUFzEh8Ch5iUiX0l_8XyleVjQRg2Cs1pq6dwhqBVcyqwsqcUdb8-l_ruFj6MqFEV3aYJqVnBlwTL-E9jRQALK6fRUv4PdWVyCTvDb3YNfSGntPjQx_sgA-5Q6b-L5Cps6TqxneQuE-zfzXocDO6H6496L3Ijyl5e5l6L5d2PgZNqpO5aHOHXvPxt5RkwXhinnk8Z6ynwAQoNc1obdRdfgvu8MwUWRvhkfgyAtiiy_2fwQP4kQ9429l-6f-o_5LV-N4MJUz4_am8Ci34EDOR6T1K0w2xoOeuvAH-eGhv6QoX30V9ZHWshMeYMtfMax7o2u0hI9vNetzSwGWlvhpbh1aS7wOyzaQmfpXwh7CeyEzdxhIbVO1cg1kLe5PTZpYZqBr-DIBcOOROXYJzr8mUKixvBiROnIl1qpKYt8_YP2Ra5kSurBJF9OhYB7qiMpQDe6nMYA7nlIiF_f72eDYfPVh3tnV0MuXUS6rV3raOj2qjd1C0RE69_DP61lMaMFgfbbLie4i7CvcddYEOJAJYnpSgWrA9lKsYilsHr2cDsMrOLfGXibi-9dU1n1oDvyZ3Mo3pAi5aMTiJhzf4CiNk9lOKd4nelAqOJAH3-CBftexi0P8o0PFIjVOhfBhIVqUmYnKsO8L6ffREjpw4VqxxqNbh1IIG8dTrCmtvB8r06ZFotrhX-TPxzZpd18QgH2OvRBZflo1kBrdmAlekS4HFXRTgi26GQBbfi9zeIev0BTGJzXX0Qr7wG8tIL0uWlo1aC-RgP-tlIYPMZJoSP3mcopF9voFxFYRmW1kdJsOENTGt2R1E-lKjVrxJu-E45ZYZtQzKRs9yxIUogDMD484B2qT3OsTe2zZcLNHXkwgtdYIDDcZRCs3AuNx9UhiBSKb3GlVJHlkI4TkDYqTmBu0U8rAGkKrwN1J7Uki29-SqGbLLbrsJiEEgG9tlRJZL65R3GYyfPwRP8mvsM9gaKlV8ENv7qEs7uGdFjGTNwf0MgYqmuxrJE5zKzeK9ZoQDZ8mmnTF4Dk52-TnnSNM1gNWH9EYIQGwq9OluZ3okdlxw1eJY15Zn9w6G7jPvAL9eodB3UzcWI9XiXk53Zo3mua6k2p3OVC1tU0R0XblvjtGv9VyM88mFOcjm5tpa9hpZiFZHjltRgiAzz6BgO7AfYDjiDvgM_OFuBnwoJtuXDOLeMos-zVbiaQVRVujD-5gcGlfQxUJO39ZPVPNEbBo6gbJO1XwiS-WJCSX_qBdksz2y_TUTeCzfmPNkieTsITr-leOUysI5wYFZVvW1FH8yDEPaEDbHs9fqLliDgn1AMzx1ffyv8KJ0bGi9D8oxgYVRU8XTtYbWl7-eA9sIBeOtGcbkY9Ure-ELwgP0PgCpHBTbYKSUFZ1hhDrcP4Fr66rMMDv61gYnffAXpyKQuLb6Wz-cJc2ljFiGQGLoMNdFHPHw3D6dYrzSndPm6G-2o95LI-MPaGbLUSkMNVJvgbz0i3lo7-ungmD8NeqE-0LXAu95DePp3-OmZPGGpFKylZD3w93riBFYAbxIa4ALP9mF1CFDeoSI-DosVZZWg-W-zNfwK5X6iACQH7XvbE4iOInIU19MjVd-f1l4kOj1EFVb7s5gjHE2RuHnPTOfWrOS17iGhElVbalSSI4yAhfEEWln4S0SZSf2Ml9Rb_XfEjrmR5DnhEw0bby6ubbSrYxGNG6bqfLh93WOgReGLER2Z_OufPCxHTMtOa48pYRBpMtOlnX1z_Kj1v2bcfqAFeIZGvNFl-wgzGK3r29KmLCWnd32nvWQItRyzjSWrenLM9vLRoL49dKJL2U2bqmr7haGQKh9Jup-PofQoVsQdGPypBWEoyTGVW-tp0OmLvwGnshjx4Dwcu9MDrHghzIuC2-oE281Gnk8qeSeyEzg_rA0-1-xdWG_WI05e0i6xLMOQUFKlDoanvYi6oiSsO0JELfppK7s2N7BwcW-6yta5jfx9Zhc0y62m5RHi6c0I2PJubdBVYN0s1LXT27dMd55TuPMw57o_Rwb1D4i27lX8pk4EpE78MGa1ueXGL0VYeu-xoei3xOzoS4FuXEvp17oOncgDnXZMPdeecKOBoCIbDF1oLnwT6OGztMxfLIjlQMqEM84F85JZ6gGmDRWOxRdovwxa0aEqT7pNP_GSV0ycQzicZg8ZeO5a8-iplx4Rpna0AGiAa2aAygiV89OWYlPs9ijmWSpIO0BF3tDZmB78-EuHrF96cYg_hKCsZOVsq_aTIFUUsPLjcAVvfjJ0DKzdCCUCmKTCeQJdjR2Q-WH8AkAvV3NpdHhZ-yqVJf6dR1dfUBmVt9W5LAXrgAB"}
  }
}


fix: update to spellchecker

Contributes to #4043
the current spellcheck command is out of date and not working. this fixes it

Nice! I ran into an issue earlier today where cspell was flagging issues in a file I hadn't even changed 😅


Adding stress testing utility for model inference to help isolate cause of stochastic failure in inference

From f2f discussion there are occasional stochastic failures in the NUTS sampling procedure. The characteristics of these failures are:

They occur during NUTS warm up.
They cause either errors with max step size violation in the ODE solver, or opaque errors from XLA calls.
They occur for models with vaccinations, but not as much for models without vaccination.

These are suggestive of either sampling into a numerically unstable portion parameter space during warm up and/or some kind of numerical instability associated with vaccination rates.
A good first step towards isolation of the problem would be a stress test utility e.g like this. Its worth investigating the existing numpyro utilities before rolling our own solution.

tagging wontfix as its parent issue #244 is also tagged that for now