No relations beetween tables

What version of Go are you using (go version)?
go1.9.2 darwin/amd64
Which database and its version are you using?
mysql  Ver 14.14 Distrib 5.7.18, for macos10.12 (x86_64)
Please provide a complete runnable program to reproduce your issue. IMPORTANT
package models

import "github.com/jinzhu/gorm"

type User struct {
	gorm.Model
	FirstName   string `json:"firstName" binding:"required"`
	LastName    string `json:"lastName" binding:"required"`
	Email       string `gorm:"type:varchar(100);unique_index" json:"email" binding:"required"`
	Phone       string `json:"phone"`
	GoogleUid   string
	FacebookUid string
	FeedBacks   []FeedBack
	DishLikes   []Dish `gorm:"many2many:likes_to_dishes;"`
}

type FeedBack struct {
	gorm.Model
	UserID          uint
	Title           string  `gorm:"null"`
	Text            string  `sql:"type:text"`
	Visible         bool
	Deleted         bool
	ServiceScore    float64 `sql:"DECIMAL(10,2)"`
	PriceScore      float64 `sql:"DECIMAL(10,2)"`
	FoodScore       float64 `sql:"DECIMAL(10,2)"`
	AtmosphereScore float64 `sql:"DECIMAL(10,2)"`
}

As a result I have tables without relations:
https://www.dropbox.com/s/xo79pgi3x5q09pw/Screenshot 2018-02-11 14.55.47.png?dl=0
What I did wrong?
Also, one more question, how I can get User data with related FeedBack?
q := d.DB.Where("id = ?", id).First(&user) //return only user data without feedbacks

Use Preload

@jinzhu I didn't received answer for main question about relations
Could you help me to fix this issue? What I did wrong? I followed by gorm documentation and it's not working

Are you talking db level foreign key not created? there are several issues discussing this

@jinzhu
yes, you are right
it's a little bit confusing, when you want to user a package, following instructions and it's not working
Maybe you need to update docs?

i have the same problem. foreign key is not created


Revert "making korean files content, added kr.toml, update config.toml, update langflags.yaml"

Reverts dogecoinfoundation/dogecoin.com#118

inevitable fixed the problem #122


docs/guide pjax descriptions improved. [skip ci]

Documentation improvement.

Great, as usual! Thank you @softark


[Docs]: Best practices for building a stable Appsmith workflow and improving performance

Is there an existing issue for this?

[X] I have searched the existing issues

Documentation Link
No response
Discord/slack/intercom Link
No response
Describe the problem and improvement.
Best practices for building a stable Appsmith workflow and performance.

@somangshu and @dilippitchika - Could you please provide a first draft or pointers for this?

@jnikhila I've already asked @somangshu for the draft. He'll share it by tomorrow or day after.


Loose ties in GovCloud

[ ] dashboards in metrics
[ ] metrics not being collected (I can't see them)
[x] events not logging in logsearch
[ ] firewall for concourse and nessus #71

Closing in favor of other issues


runtime: create state directory and structure

For supporting things like hooks and updates we need a way to define runtime state of the container.  This can be used to pass information to hooks so that they know the runtime state of the container and also used to dynamically make changes to resource allocations by running an update command for the runtime and have it reconcile the changes against the container's current state and the update requested.
For the hooks usecase the state should contain information such as:

pid of the container's process
paths to the namespaces (linux)
paths to the cgroups setup for the container

For supporting updates the state should container information such as:

pid of the container's process
cgroup paths
container root path
cgroup/resource information
device nodes
rlimits
sysctls
mounts

Some of this information would be duplicated from the initial container's config so it maybe worth it to look into embedding the original config into the state structure.

I think it makes sense to embed the config into the state as is.

Also I think we should allow implementation to store state in any desired form. It can be registry key for windows for example. But hooks will always consume text version of state, so info about storage method will never leak outside implementation.

What does "cgroup/resource information" mean?

/cc @vmarmol

@crosbymichael I think all the items in your lists make sense as state that could be passed to the hooks.

On Tue, Jun 30, 2015 at 04:59:34PM -0700, Michael Crosby wrote:

Some of this information would be duplicated from the initial
container's config so it maybe worth it to look into embedding the
original config into the state structure.

I think embedding the initial config is less useful than embedding the
current effective config.  For example, if you update the container to
mount a new directory, adjust limits, etc., the embedded config should
be a config capable of launching you directly into the current state
(modulo memory state in the running processes, which is what
checkpoint/restore is about).

We spoke about this in the meeting today. We don't think it makes sense to have here config where the source of truth is the kernel (e.g.: resource limits). We should have some immutable state which with some pre-defined operation can provide the current state. Otherwise keeping these in sync will be expensive and difficult to do.

On Wed, Jul 22, 2015 at 09:58:45PM -0700, Victor Marmol wrote:

We don't think it makes sense to have here config where the source
of truth is the kernel (e.g.: resource limits).

The kernel is enforcing those resource limits, so why not make it the
source of truth?

We should have some immutable state…

Do you have an example workflow where a container's initial resource
limits (or whatever) matter and are different from the current
resource limits?  I'm trying to understand the utility of a stale
state dump…

Otherwise keeping these in sync will be expensive and difficult to
do.

I'm not sure about difficult, but I'm not terribly worried about the
expense.  These state dumps are just for hooks and occasional
host-initiated maintenance, right?  I don't see us needing to refresh
them multiple times per second.  Is there a particular check that you
expect to be difficult/expensive?

@crosbymichael My concern with having device node, sysctl, rlmit, etc state parameters is that we are simply serializing Kernel features and state. Why not tell consumers to read from the source of truth instead?

Gah, sorry for piling on I had this tab with a half finished response and the stuff from Victor hadn't loaded yet.

Ya, in my PR for the state it is much more conservative and gives people just the information required to look in the correct locations.


Did styled-components or babel-plugin-styled-components changed the way it inject the css in the page in production lately ? How can I see the generated css in a production build?

Hi everyone, I can see a lot of change with the css props, and the plugin.
I am using in an application the required dependencies:

create react app (just for creating the app)
styled component
babel-plugin-styled-components.

I noticed after doing npm run build and opening the production application in my browser that it is not possible anymore to get (using the chrome developer tab) the css rules in the page.
All I can see is <style data-styled="" data-styled-version="4.1.3"></style>
If I check a rules and click on the reference link, it brings to that element again.
Is there a way I can see the generated css? Thanks!

That was always the case and has nothing to do with the Babel plugin or the CSS prop.
In production mode we use a browser CSS injection API (insertRule) that is 10-100x faster than the naive injection API we use in development mode. Unfortunately, Chrome DevTools have a bug where they do not show styles in the HTML tree that are injected with this ultra fast injection API, so there's nothing we can do there except recommend you to use a different browser!

Thanks I understand now. May I ask what browser do you prefer over chrome?


ruff server: Add tracing setup guide to Helix documentation

A follow-up to this suggestion on the tracing PR.

@MichaReiser

Does ruff log the messages to the default location in helix? Do users know where to find the logs?

Yes, by default it logs them to the Helix log file, which can be opened with :log-open.


BAU: Update base domain

Jira link
BAU
What?
I have added/removed/altered:

[x] Update base domain for production

Why?
I am doing this because:

This is currently incorrect/pointing to the old test domain

Fixing dev slowness in a bit


Tx off from already running containers

This PR fixes bug where weave-helper process does not modify (ethtool tx off) already running containers.

@nevalla ping

:+1:


Should transformations applied to properties return streams?

I think this topic needs a separate issue (was originally started in #140 and continued in #142).
/cc @cefn

I am comfortable with learning from corner cases that Property is not the simple cache that I thought it was, (as documented in the threads you mention), and not to argue for Property being something it's not.
I acknowledge we shouldn't overlook the convenience of smart defaults (the suggestion that if Propertyness is always wanted, then Property contagion has no cost and transformations should somehow be expected to maintain the Property contract).
However, the effort required of dealing with these corner cases for all transformations does suggest it would be simpler and more predictable to avoid this duality in every operation, assuming there's no cost to the expressivity available in Kefir.
My understanding is that you can always resume Property behaviour explicitly using toProperty() on an active stream but the opposite is not true.
To complement this simplification (all transformations turned into streams), an alternative primitive Observable transformation could be provided, perhaps cache() or subscriberCache(), corresponding with a stream behaviour of saving the last-served value, and re-serving it to each future subscriber.
This is what I seem to always need and I presume would be much much simpler to implement and easier to predict. Because Property seems to have a semantic rather than an operational definition, it leads to potential ambiguities depending how the author might interpret its semantic role in corner cases (which come up a lot in transformations).
For example, my instinct is that any loss of information (values being ignored as in https://github.com/rpominov/kefir/issues/142#issuecomment-138069622 ) could, would and should be explicit, e.g. through a consumeSimultaneous() or momentary() invocation, determining that every value emitted in a single stack call would be thrown away, except the very last one. This may certainly be employed to eliminate efficiency issues e.g. in UI implementation - avoiding repaints from flushed buffers containing multiple values.
However, I'd be curious to know the circumstances in which the combination of explicit cache() and momentary() wouldn't deliver more explicitly what Property does and with a huge reduction in complexity and possibly efficiency (e.g. all intermediate transformations can be just streams), and if so whether any of the divergences between toProperty() (with contagion) and momentary().cache() (with no contagion) are actually desired.
I believe the combination of dropping Property contagion and making cache() and momentary() available to make these features of Property explicit would simplify the implementation of Kefir and avoid unusual corner cases and unexpected semantic interpretations of what is 'Property' as discussed throughout the referenced threads.

For reference the alternative strategy based on momentary() and cache() is illustrated by the gist at...
https://gist.github.com/cefn/f73380591630171f0e83
Where the invocation...
var cached = cacheStream(onceStreamFactory());
cached.log("once");
cached.log("twice");

...produces the following logging...
once <value:current> 1
once <value:current> 2
once <value:current> 3
twice <value:current> 3

While the invocation...
var momentary = momentaryStream(onceStreamFactory());
momentary.log("once");
momentary.log("twice");

...produces the logging...
once <value> 3
twice <value> 3

my two cents.
I don't think that this is a good idea. Streams and Properties are two different beast. And they have different semantics, actually intentionally. And I think this duality is unavoidable.
From the original definition (see http://citeseerx.ist.psu.edu/viewdoc/download?doi=<IP_ADDRESS>.360&rep=rep1&type=pdf):
"There are two key polymorphic data types in FRP: the Behavior and the Event. A value of type Behavior  is a value of type a that varies over continuous time. "
"A value of type Event a is a time-ordered sequence of event occurrences, each carrying a value of type a"
I would recommend to read this paper, at least the beginning + examples.
Some parallels with real world. Imagine that you have some digital thermometer, in fact values that it produce is a Stream - stream of measurements. But what you see on the display is a Property - current measurement. It is possible to get from Stream to Property, but it is impossible to convert Property back to the original Stream. So Property is not a Stream per se.
I'm using both Streams and Properties extensively, and very happy with semantics that they have. That actually was the reason for me to choose bacon and then kefir, but not something like RxJs.
Actually all corner cases that I run into were related to this implicit transformation between Properties and Streams. E.g scan on Stream returns Property etc.

Hey, thanks, @aindlq . That's a really interesting reference and it's focused a perspective on another, orthogonal, intention embedded in Properties.
I don't know that Behaviour in the paper maps to the core aspect of Property in Kefir we're discussing, (as covered at https://rpominov.github.io/kefir/#about-observables and https://rpominov.github.io/kefir/#current-in-streams ). In Kefir, the reliable feature of Property seems to be about the existence of a defined current value, based on the last served value, which I've referred to as a cache, which is served to new subscribers. So if anything this aspect of Property takes it closer to the definition of Event in the paper, with discontinuous changes to values, (but with a cache for new subscribers).
However, Behaviour in the paper (a continuously defined function which can be collapsed by evaluation to a value through sampling/binding its variables - on a pull model) does relate a little bit to an optional feature of Kefir Properties - the getCurrent callback ( https://rpominov.github.io/kefir/#to-property ). This 'pull model' only really affects the first value served by a Property on activation (where activation is the 'pull' sampling action as described in the paper). This functional evaluation is then overridden by future cached-served-values, so getCurrent soon gives way once again to the evented 'push' model where Property behaves like a stream of discontinuous value-change events (with a cached current value), and in which the functional definition in getCurrent is ignored (assuming I now have toProperty() correct in my mind).
The fact that both of these quite distinct aspects are both considered to be 'Property' nature does give me a slight worry. Things which are so distinct seem like they should be separate and I'd also be more confident if each were explicitly identified rather than implied in the semantic intent of Property.
I guess I was hoping the trick of everything being a stream would help to make clear each of the different ways in which streams could be augmented with atomic but distinct and operationally-defined features, making the results more comprehensible/predictable.
For example from this discussion it's emerged that Property has not one, but two or more key features, possibly both aspiring to some semantic intent, but which could be explicitly separated in API terms with different names and expressed in stream terms...

a callback which runs on first stream-subscription - dispatching a functionally-defined value to the first subscriber
a callback which runs on every stream-subscription - triggering a notification of the cached-last-served value to the subscriber.

I have to admit the whole endeavour is probably flawed if ultra-local Stream operations are not rich enough to express everything needed, but so far they appear to be rich enough as far as I can see. Additionally AFAIK the features which co-exist in Property, (cache-oriented, getCurrent-oriented and more richly semantically-committed like the flatten behaviour characterised in https://github.com/rpominov/kefir/issues/144 ) probably don't need to be collapsed into a single concept and my suspicion is there is a real cost in doing so.
Relying on Property semantics (there being an interpretation of the purpose of Property) seems to lead to ambiguity, and unavoidably arbitrary definitions which are impossible to get right, especially when doing transformations.
By contrast a separate specification of the different behavioural aspects of Property - described by implementation and ultra-local to Streams without 'Propertyness contagion' throughout a pipeline - could eliminate many of these concerns.
The puzzle which remains for me is to identify any aspects of Property which can't be expressed in Stream terms (although we certainly need the additional expressivity of triggers on first-subscription and every-subscription, possibly other key triggers?).
Related to this is the question whether Property is a single concept, or many actually many concepts snuck in to a single implementation. Having multiple aspects in one leads to surprising consequences for people who are focused on one feature (getCurrent) but also getting others in the same package (cache and other semantics).
When you say Property currently serves your needs @aindlq, do you consider Property nature to be about caching? getCurrent? semantic commitments like https://github.com/rpominov/kefir/issues/144 ) ...something else?
Do you feel they actually map to the paper's description of Behaviour in their current form (in which case I need to revisit a lot of things to get my ideas straight, I really don't see this).
@aindlq in your use of toProperty() would cache() or momentary() or both (see https://github.com/rpominov/kefir/issues/147#issuecomment-138285060 ) be equivalent for your needs?

As an experiment to explore the performance and compositional consequences of an alternative stream library approach which eliminates Properties as first-class elements, I put together a draft of a library which takes these and other minimal design strategies to their logical conclusion.
I've been codenaming it Angstream as it's intended to be as tiny as possible in resource commitments. This is as 'breaking' a suggestion as there can be, so it made sense to explore it as a substitute library implementation. It may provide some ideas which could be reused somewhere in Kefir.
It includes no notion of Property, but it attempts to recreate the equivalent functionality through 'onsubscribe caching'. All operations modify the stream's behaviour directly, using an internal transformation stack based on the canonical signature of Kefir#withHandler(). If you wish to add a transform without changing the behaviour of the original stream, you first branch() the stream and then the original remains intact as you perform further modifications.
The test case outlined below suggests a large speedup from following the Angstream approach when it comes to simple transform sequences. It constructs a series of 1400 map (+1) operations fed with a single value of 0, timing the promise of the event which pops out the stream at the end. The results shown are the second run of the test in Node (allowing V8 to complete JIT compilation, which otherwise skews the results).
The reason for the choice of 1400 is that if you create a map sequence of 1500+ then Kefir exceeds the stack allocation of the Node VM, (the Angstream test case can go to a sequence of 5000 before exceeding the available stack frames).
Event generated 1400
AS took 3 ms
Event generated 1400
Kefir took 15 ms

I believe there are a few more advantages too. I have found that debugging stream logic may be easier in the case of Angstream as the stack is more easily inspected; you can literally see the stream transformation sequence in e.g. the V8 stack debugger in Webstorm with just a few comprehensible stack frames in between.
To get the same performance and debugging benefits a middle way exists, where the equivalent of Angstream's 'Pipe' can offer up a withHandler function to Kefir containing a sequence of withHandler functions as middleware. This would make it possible to employ the same strategy as Angstream within Kefir without changing the API. It seems from experiments so far that a library of middleware functions exposed in a withHandler format could be provided with equivalent expressivity to the available Kefir stream transformations.
The test case looks like this...
    it("Compare Kefir and AS", function() {

        function Case(){
            this.target = 1400;
            var count;
            for(count=0;count<this.target;count++){
                this.mapStream(function(value){
                    return value + 1;
                });
            }
        }
        Case.prototype = _.create(Object.prototype, {
            promiseDelay:function(){
                var start = Date.now();
                var promise = this.promiseEvent()
                    .then(function(value){
                        console.log("Event generated " + value)
                    })
                    .then(function(){
                        return Date.now() - start;
                    });
                this.emitter.emit(0);
                return promise;
            },
        });

        function KefirCase(){
            var that = this;
            this.stream = Kefir.stream(function(emitter){
                that.emitter = emitter;
            });
            Case.apply(this, arguments);
        }
        KefirCase.prototype = _.create(Case.prototype, {
            mapStream:function(fn){
                this.stream = this.stream.map(fn);
            },
            promiseEvent:function(){
                return this.stream.take(1).toPromise();
            }
        });

        function AsCase(){
            this.stream = new AS.Stream();
            this.emitter = this.stream.in;
            Case.apply(this, arguments);
        }
        AsCase.prototype = _.create(Case.prototype,{
            mapStream:function(fn) {
                this.stream.map(fn);
            },
            promiseEvent:function() {
                var limited = this.stream.branch();
                limited.take(1);
                return AS.promiseLast(limited);
            }
        });

        var kefirExample = new KefirCase();
        var asExample = new AsCase();

        return Promise.resolve()
            .then(function(){
                return asExample.promiseDelay();
            })
            .then(function(value){
                console.log("AS took " + value + " ms");
            })
            .then(function(){
                return kefirExample.promiseDelay();
            })
            .then(function(value){
                console.log("Kefir took " + value + " ms");
            })
    });

You can see a rough draft of the Angstream library at this gist...
https://gist.github.com/cefn/99c69c0ab44b091a9ea6
It's very much "work in progress" and has plenty monkey-patches and untested operations. I've got some basic test-cases running to prove filter() map() flatten() sample() interval() concat() take() promiseLast()
I won't have a chance to harden it beyond the few hours I've spent knocking it together to sanity-check the approach. A lot of the work has been verifying the 'middle way' of withHandler()-compatible middleware which may be needed to hit performance demands within the application I'm working on, but that will be embedded within Kefir streams so the draft Angstream Stream and Emitter implementations won't play a part and will have to be revisited in the future if I ever get a chance.

Probably won't happen closing for now to cleanup open issues.


quic: handle incoming packets with unknown destination address

Commit Message: QUIC client sockets always enable socket options to read destination address of the incoming UDP packets. But in some cases, the address is not returned via the system call, recvmsg or recvmmsg. In such case, Quic connection should drop the packets. And if there are a lot of such packets, the connection should be closed with detailed error sent to the server.
Risk Level: n/a
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

/retest


Multi IP DNS records

I have a noobie question. I have +4 IP addresses added to my server, they are nicely visible with an ipconfig command.
Do I have to set subdomains for those ips?
(These are NS settings:)
Like:
A smtp1.domain.com <IP_ADDRESS>.
A smtp2.domain.com <IP_ADDRESS>.
A smtp3.domain.com <IP_ADDRESS>.
A smtp4.domain.com <IP_ADDRESS>.
and than refer these subdomain in the IP pool?
OR
I add them as
A postal.domain.com <IP_ADDRESS>.
A postal.domain.com <IP_ADDRESS>.
A postal.domain.com <IP_ADDRESS>.
A postal.domain.com <IP_ADDRESS>.
And refer to them like this in the domain pool?

In your IP Pool you should refer the IP address that the server is seeing, it probably won't be able to see the domain name.
The DNS is only important if you want to use those IPs to connect to your server which I imagine you don't. I imagine however you will need to set up reverse DNS for each IP.

Thanks, great!


Benchmark enabling OSSA after serialization with mad copy propagation

convert struct_extract to destructure_struct
copy-propagate across those destructures and across blocks

@swift-ci benchmark

Build failed before running benchmark.


Make all DAO methods return afuncs.

This will make it easier to chain DAO methods or use them with combinators like aseq() or apar().

Rather, promises. Mentioning #479 for tracking.


Cropper view shows stretched image

The cropper image view is stretching the image. It should display it in aspect fit mode to prevent any stretching and display images in their proper aspect ratio irrespective of their size. In the example below, i passed a landscape image to the cropper and it stretched it  in the cropper view (can be seen clearly with the long stretched phone)

Recently I'm busy, I'm sorry reply you now.
Thanks for report this bug. Because I didn't test much in iPad, so it needs some time to fix this bug or other bugs in iPad.

I found the cause of this bug. It's also from Apple update.
Apple deprecated NavigationView from iOS 16. And now if using NavigationView, it shows the sidebar like you see in iPadOS.
I will fix this and corresponding bugs. Thanks for your using.


Add basic .gitignore

Done! https://github.com/boramalper/himawaripy/commit/c3b8bafaf97b254f481e61817c08c045989914db
I preferred to use https://www.gitignore.io which covers more cases.


JavaScript code formatting extention not working properly

Before v0.10.10, the formatting extention works well.After the update, Format Code (Alt+Shift+F) just add some spaces. :(

@Lonefy have you installed an extension for JS formatting. If so, please report the bug there. If not I think the problem is the move to Salsa (a different JS engine we use). With 0.10.12 there are settings to control the Salsa based formatter as well.

@dbaeumer actully, I wrote this extension by using registerDocumentFormattingEditProvider('javascript', {}). And I don't change my code ,so I just suppose that vscode will use the default format method first.

@jrieken can you shed some light on this. IMO the JS formatter will not be invoked in that case.

@Lonefy Our JavaScript language service is now and real extension. This means, the rule of having a single best match for the DocumentFormattingProvider comes into play (https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts#L3490).
Since both (yours and ours) have the same score the provider registered last wins. You can restore the previous behaviour (that is your provider being in charge) by declaring a dependency on the builtin JavaScript mode and thereby being last. In your package.json add this
"extensionDependencies": ["vscode.typescript"]
``


Compute cell from coordinate

Would be great if I could easily determine which cell is under the mouse cursor on click.

Hmm... good point! Since handling cross-browser canvas-relative coordinates can get verbose, I'm hesitant to throw it directly into the library. Once you have the x and y coords within the canvas it should be fairly straightforward:
function getCellFromCoords (x, y) {
  return {
    x: Math.floor(x / cellSize),
    y: Math.floor(y / cellSize)
  }
}

cellSize defaults to 10. Let me know what you think!

If you're looking for a good way to translate a click event into canvas coordinates, I've found this method works pretty well :)

@dbkaplun looking back on this, I still feel like click-handling should be handled outside of the core library. Cool if I close this?

(And if you ended up making a working demo with click-handling I'd love to see it!)


undefined method `constantize' for #ActiveModel::Name:0x007fe29e8fc360

-- I'm using ruby 2.0.0p195 & rails 4.0.0 --
I'm receiving the above error for the line parse_user.rb:14
 user = model_name.constantize.new(JSON.parse(resp), false)

I see that this line has been changed post 1.8.0 to:
 user = model_name.*to_s*.constantize.new(JSON.parse(resp), false)

It seems that these changes have just not yet made it into production? Am I missing something?

The gem still hasn't been updated on RubyGems. To get around this you can include the code from the parse_resource github repo in your vendors folder. See here for more info: http://stackoverflow.com/questions/6800074/custom-ruby-gem-in-gemfile-on-heroku

Anyone here want commit and rubygems push access?
On Mon, Feb 2, 2015 at 4:46 PM, Nick Smit<EMAIL_ADDRESS>wrote:

The gem still hasn't been updated on RubyGems. To get around this you can
include the code from the parse_resource github repo in your vendors
folder. See here for more info:
http://stackoverflow.com/questions/6800074/custom-ruby-gem-in-gemfile-on-heroku
—
Reply to this email directly or view it on GitHub
https://github.com/adelevie/parse_resource/issues/87#issuecomment-72544671
.


How to send AJAX requests via affjax

Description of Problem
Send and handle AJAX requests.
Proposed Name of Folder/Module
Unique Recipe Name: AjaxRequestsAffJax

Since there are a few HalogenHooks recipes that use Affjax, is this recipe still necessary?

I think it could be, like as a minimal example, I'm thinking this could be made as a Log-type recipe that runs either in Node or in the browser.

Oh right. I don't think we have an example in node and that requires adding
xhr2, right?

Ah, yeah, I believe it would require adding xhr2.

Feel free to copy over any of the Affjax examples in the book. https://github.com/purescript-contrib/purescript-book/tree/master/exercises/chapter12/test
For example endpoints, I found http://reqres.in/api more reliable than https://jsonplaceholder.typicode.com/


Nil pointer dereference when getting a disabled certificate

Have you

[x] Read Troubleshooting Guide
[x] Searched on GitHub issues and Discussions

What steps did you take and what happened:
Our deployment process failed to create a certificate in keyvault via the az CLI, and missed the fact that it failed.  This resulted in a certificate in the keyvault with a status of 'Disabled'.  Later in the deployment, we try to retrieve that certificate but the provider fails with a nil pointer dereference:
I0609 19:58:46.636353       1 provider.go:260] "fetching object from key vault" objectName="ssl-certificate" objectType="cert" keyvault="ghzf6l24nte3ufw" pod="ghae/azsecpack-initializer-mqxwb"
I0609 19:58:46.636428       1 provider.go:248] "unmarshaled key vault objects" keyVaultObjects=[<snip>] count=10 pod="ghae/telegraf-67f87fdcf5-q2spx"
I0609 19:58:46.636448       1 provider.go:260] "fetching object from key vault" objectName="actions-x-RunnerResourceGroupName" objectType="secret" keyvault="ghzf6l24nte3ufw" pod="ghae/telegraf-67f87fdcf5-q2spx"
I0609 19:58:46.636483       1 auth.go:131] "using user-assigned managed identity to retrieve access token" clientID="a7eb##### REDACTED #####0904" pod="ghae/azsecpack-initializer-mqxwb"
I0609 19:58:46.636505       1 auth.go:131] "using user-assigned managed identity to retrieve access token" clientID="a7eb##### REDACTED #####0904" pod="ghae/telegraf-67f87fdcf5-q2spx"
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x99cf17]
goroutine 81 [running]:
github.com/Azure/secrets-store-csi-driver-provider-azure/pkg/provider.(*Provider).GetKeyVaultObjectContent(0xc00043b8d0, 0xbebb40, 0xc00061a0c0, 0xc000312440, 0xf, 0xc0000c8180, 0x13, 0x0, 0x0, 0xc000312478, ...)
	/agent/_work/1/s/go/src/github.com/Azure/secrets-store-csi-driver-provider-azure/pkg/provider/provider.go:428 +0x1f97
github.com/Azure/secrets-store-csi-driver-provider-azure/pkg/provider.(*Provider).MountSecretsStoreObjectContent(0xc00047d8d0, 0xbebb40, 0xc00061a0c0, 0xc0000aa1b0, 0x0, 0xc000064000, 0x68, 0x1a4, 0xc0005a7798, 0x98, ...)
	/agent/_work/1/s/go/src/github.com/Azure/secrets-store-csi-driver-provider-azure/pkg/provider/provider.go:276 +0x1798
github.com/Azure/secrets-store-csi-driver-provider-azure/pkg/server.(*CSIDriverProviderServer).Mount(0xc00000e450, 0xbebb40, 0xc00061a0c0, 0xc000642000, 0xc00000e450, 0x1, 0xc0000b0550)
	/agent/_work/1/s/go/src/github.com/Azure/secrets-store-csi-driver-provider-azure/pkg/server/server.go:53 +0x2f4
sigs.k8s.io/secrets-store-csi-driver/provider/v1alpha1._CSIDriverProvider_Mount_Handler.func1(0xbebb40, 0xc00061a0c0, 0xad0480, 0xc000642000, 0x0, 0x0, 0x4182f7, 0xfa5268)
	/agent/_work/1/s/go/pkg/mod/sigs.k8s.io/secrets-store-csi-driver@v0.0.21/provider/v1alpha1/service.pb.go:811 +0x89
github.com/Azure/secrets-store-csi-driver-provider-azure/pkg/utils.LogGRPC(0xbebb40, 0xc00061a0c0, 0xad0480, 0xc000642000, 0xc000314000, 0xc00000c030, 0x4716e7, 0x504325, 0xac6f00, 0xc00061a0c0)
	/agent/_work/1/s/go/src/github.com/Azure/secrets-store-csi-driver-provider-azure/pkg/utils/grpc.go:27 +0x26d
sigs.k8s.io/secrets-store-csi-driver/provider/v1alpha1._CSIDriverProvider_Mount_Handler(0xb06e40, 0xc00000e450, 0xbebb40, 0xc00061a0c0, 0xc000614120, 0xb4bf98, 0xbebb40, 0xc00061a0c0, 0xc000640000, 0x35e)
	/agent/_work/1/s/go/pkg/mod/sigs.k8s.io/secrets-store-csi-driver@v0.0.21/provider/v1alpha1/service.pb.go:813 +0x150
google.golang.org/grpc.(*Server).processUnaryRPC(0xc000222380, 0xbf1318, 0xc000083200, 0xc000624000, 0xc0001a3b30, 0xf5fff8, 0x0, 0x0, 0x0)
	/agent/_work/1/s/go/pkg/mod/google.golang.org/grpc@v1.31.0/server.go:1180 +0x52b
google.golang.org/grpc.(*Server).handleStream(0xc000222380, 0xbf1318, 0xc000083200, 0xc000624000, 0x0)
	/agent/_work/1/s/go/pkg/mod/google.golang.org/grpc@v1.31.0/server.go:1503 +0xd0c
google.golang.org/grpc.(*Server).serveStreams.func1.2(0xc0000ac200, 0xc000222380, 0xbf1318, 0xc000083200, 0xc000624000)
	/agent/_work/1/s/go/pkg/mod/google.golang.org/grpc@v1.31.0/server.go:843 +0xab
created by google.golang.org/grpc.(*Server).serveStreams.func1
	/agent/_work/1/s/go/pkg/mod/google.golang.org/grpc@v1.31.0/server.go:841 +0x1fd

What did you expect to happen:
Not really sure, but not a nil pointer dereference.
Which access mode did you use to access the Azure Key Vault instance:
User identity (i.e. my personal credentials)
Environment:

Secrets Store CSI Driver version: (use the image tag):

0.0.19

Azure Key Vault provider version: (use the image tag):

Not completely sure, can provide with some help if needed.

Kubernetes version: (use kubectl version and kubectl get nodes -o wide):Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-12T14:11:29Z", GoVersion:"go1.16.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.9", GitCommit:"c1ad2bc44e0c7f19a9db0879f7182ff556a8e5b4", GitTreeState:"clean", BuildDate:"2021-05-19T22:27:45Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}

Cluster type: (e.g. AKS, aks-engine, etc):

AKS

@pjquirk Thank you for reporting the issue. We'll repro this and include the fix in the next release.
Are you using objectType: cert for this particular object?

@aramase Yep, that's correct.  Thanks!


build: Unbreak DefaultSocketPath.

PR #87 inadvertently broke the build setting the default socket path
variable. This appears to be due to a bug in "go build" whereby it
accepts any number of -ldflags "-X ..." options, but only actually
honours the last one. On PR #87 this meant that the Version variable
was set, whilst DefaultSocketPath was silently ignored and its value
defaulted to "".
Fixes #90.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

Coverage decreased (-0.3%) to 74.445% when pulling d58180614d63ef493ab3a3c57cde96c060ab0c4e on jodh-intel:unbreak-default-socket-path into 5c0ea6589b57ffebe24507b4c7d0159a6abc84bd on clearcontainers:master.

oh my.
lgtm

lgtm
(and you snuck in a line ending fix? ;-)


Add exit_on_esc_system to examples with window

This covers issue #2110
It adds the line .add_system(bevy::input::system::exit_on_esc_system.system()) before .run()
to every example that uses a window, so users have a quick way to close the examples.
I used the full name bevy::input::system::exit_on_esc_system, I thought it gave clarity about being a built-in system.
The examples excluded from the change are the ones in the android, ios, wasm folders, the headless
examples and the ecs/system_sets example because it closes itself.

I personally think we should only add this system to "real games" (currently "breakout" and "alien cake addict"). In general I want the examples to be "minimal / noise free". They exist to show exactly what they set out to and nothing else. "Exit on esc" behavior is in a class of thing that we have intentionally excluded from examples in the past.

Following the discussion about ux I thought it'd be handy to close the examples with esc. When looking at the examples I liked going over them fast to see what they were about and the ESC option would have been nice, but I can see why having it only on the game examples is a good idea.
I'll update the pr removing the line to the non game examples

Just needs a cargo fmt --all and we're good to go!

I ran it and it fixed a file, thanks for mentioning it

bors r+


[Bug] Returns nothing in MSSQL when nvarchar(MAX) is used

Using MSSQL nothing is returned when you do a SELECT on a DB table that has a column with nvarchar(MAX) set. If I change the column to nvarchar(250) it returns the results from the table.
Inserting data is not an issue. Just returning data.

There's various PHP bugs reported on this: https://bugs.php.net/bug.php?id=67437


ARROW-15871: [Python] Start raising deprecation warnings for ParquetDataset keywords that won't be supported with the new API

Added warnings for when passing the schema and metadata_nthreads keywords.
For schema, also enabled this keyword for the new implementation (passing through the schema keyword to the datasets API), but so in this case this is about a pyarrow.Schema and not a ParquetSchema that should be passed.

@github-actions crossbow submit -g integration

I forgot about this PR. I rebased and will merge if green.

@github-actions crossbow submit -g integration


[Deque Analysis] File upload progress bar & success message lack color contrast

Deque Analysis Summary

While a file upload is in progress, the progress bar displayed has insufficient color contrast (e.g. "Queue length: 1 | sample.txt"):  Foreground: #9C9C9C, Background: #FFFFFF, The contrast ratio is: 2.7:1
After a file upload is successful (or really any successful task) a green success message appears.  This also has color contrast issues: Foreground: #647D3E, Background: #E9F4D9 The contrast ratio is: 4.1:1

Deque ticket IDs: 469766, 471651
These are both most easily reproduced by drag & drop of file in Collection logo upload and/or submission.  Ideally, upload a large file to see the progress bar.
Recommended Fix
For (1) likely darken the text to #757575 (at a minimum)
For (2) likely make the green (foreground) text slightly darker, perhaps #5A7336
Both of these colors were found using https://dequeuniversity.com/rules/axe/4.1/color-contrast?application=axeAPI
More Information / Tools

As necessary, see mentioned Issue IDs in our assessment results (requires login): https://axeauditor.dequecloud.com/test-run/0856438a-a19a-11eb-bc31-b7d5be387c86/issues
Consider using Deque's free Chrome plugin to check your work
Deque's color contrast tool: https://dequeuniversity.com/rules/axe/4.1/color-contrast?application=axeAPI

@tdonohue Could you assign me to this issue? My team and I have investigated the accessibility of the system recently, so I guess it will be great to have done this task until we are fresh after our initial analysis.

@tdonohue please assign my colleague @Dawnkai to this task. He is going to provide the PR for this issue. Also when it will be accepted, I kindly ask to give credits for this bug fix contribution to PCG Academia. Thanks


[Brave] Requesting support for Brave Nightly browser

Extension
https://www.raycast.com/ron-myers/brave
Description
As a "Brave" extensions, I believe that its bookmark retrieval should support Brave Nightly.
Who will benefit from this feature?
No response
Anything else?
No response

Created a PR for your request
https://github.com/raycast/extensions/pull/9604

Created a PR for your request
#9604

Thank you so much!


✨ feat: support metric analysis diagnosis

Fix #237
Changes proposed in this pull request:

✨ feat: support metric analysis diagnosis

Codecov Report

Merging #238 (96d5ede) into main (b0c86a2) will decrease coverage by 0.38%.
The diff coverage is 0.00%.

:exclamation: Current head 96d5ede differs from pull request most recent head 5056abb. Consider uploading reports for the commit 5056abb to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@             Coverage Diff              @@
##               main     #238      +/-   ##
============================================
- Coverage     64.75%   64.38%   -0.38%
  Complexity      546      546
============================================
  Files           164      164
  Lines          4821     4849      +28
  Branches        619      621       +2
============================================
  Hits           3122     3122
- Misses         1547     1575      +28
  Partials        152      152

Flag
Coverage Δ

*Carryforward flag

api_ut
53.59% <0.00%> (-0.47%)
:arrow_down:

server
68.86% <ø> (ø)

Carriedforward from b0c86a2

ui
94.53% <ø> (ø)

Carriedforward from b0c86a2

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files
Coverage Δ

.../featureprobe/api/controller/MetricController.java
0.00% <0.00%> (ø)

...va/com/featureprobe/api/service/MetricService.java
37.81% <0.00%> (-5.87%)
:arrow_down:


More (non IO related) err="strconv.ParseInt: parsing \"\": invalid syntax" errors when scraping metrics

On LXD 5.0, I sometimes get err="strconv.ParseInt: parsing \"\": invalid syntax" for metrics other than IO which should have been dealt with in #11630. The errors in question are:
# grep -hF "lxd" /var/log/archives/2023/2023-*-syslog | grep -E 'msg="Failed to get (total number of processes|memory usage)" err'
Feb 10 05:14:17 c2d lxd.daemon[1258]: time="2023-02-10T05:14:17Z" level=warning msg="Failed to get total number of processes" err="Failed parsing \"\": strconv.ParseInt: parsing \"\": invalid syntax" instance=gw-home instanceType=container project=default
Feb 27 14:03:43 ocelot lxd.daemon[1286]: time="2023-02-27T14:03:43Z" level=warning msg="Failed to get total number of processes" err="Failed parsing \"\": strconv.ParseInt: parsing \"\": invalid syntax" instance=git instanceType=container project=default
Mar 28 12:54:17 c2d lxd.daemon[1365]: time="2023-03-28T12:54:17Z" level=warning msg="Failed to get memory usage" err="Failed parsing \"\": strconv.ParseInt: parsing \"\": invalid syntax" instance=gw-home instanceType=container project=default
Mar 30 05:23:38 xeon lxd.daemon[1295]: time="2023-03-30T05:23:38Z" level=warning msg="Failed to get memory usage" err="Failed parsing \"\": strconv.ParseInt: parsing \"\": invalid syntax" instance=squid instanceType=container project=default
Apr 19 11:54:17 c2d lxd.daemon[1368]: time="2023-04-19T11:54:17Z" level=warning msg="Failed to get total number of processes" err="Failed parsing \"\": strconv.ParseInt: parsing \"\": invalid syntax" instance=gw-home instanceType=container project=default

Here again, it looks like the cgroup file is returning an empty string where LXD expects a int. Speaking of int, shouldn't those be uint?
My environment:
$ uname -a
Linux xeon 5.19.0-41-generic #42~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 18 17:40:00 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

$ snap list lxd
Name  Version        Rev    Tracking      Publisher   Notes
lxd   5.0.2-838e1b2  24322  5.0/stable/…  canonical✓  -

@simondeziel in case of an unsupported PID cgroup controller, the API can return -1 (alongside with an error message) to differentiate from a case where there would be no PID (which shouldn't be considered as an error). We could also use ParseUint but we"ll have to recast the return value anyway to int to handle the erroneous -1 value for unsupported so I think it's bit useless to do that. I don't know if it makes a lot of sense...

That's occurring so rarely that it's probably not worth fixing. I'll just put a logcheck ignore rule ;)


Elementary os installation support in hack\install.sh

Added elementary to installation

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:mozinrat/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

This will update the existing PR, so you do not need to open a new one.


All jstrot/PyAV PyAV-Org/PyAV

PR just for running UT

Moved my repo to https://github.com/qualIP/PyAV
Contact me when you're ready to accept code.

FYI @jstrot , Mike replied on gitter earlier this month: https://gitter.im/PyAV-Org


Adds remaining methods

Depends on https://github.com/textileio/go-textile-threads/pull/129.

[ ] Once the above is merged, we can publish a new package of protos and update package.json here (for now npm link @textile/threads-api-pb works locally)
[ ] Figure out a headless test setup (fetch is needed, maybw node-fetch is worth a look)

Just to clarify for others, you need to use npm link @textile/threads-client-grpc.


[PR REVIEW]: Log rate limit changes

This should allow developers and platform providers to manage the log rate of applications on the platform.
https://github.com/cloudfoundry/diego-logging-client/pull/33
https://github.com/cloudfoundry/bbs/pull/50
https://github.com/cloudfoundry/rep/pull/34
https://github.com/cloudfoundry/executor/pull/61

Fixed/bumped via 4ae868d. will be in the next release


Fastnlight: Watch medium.com/@bestonlinegaming0

Fastnlight requests the watch of the watch_keyword medium\.com/@bestonlinegaming0. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

medium\.com/@bestonlinegaming0 has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


magic trailing comma for ExprList

seems mostly better, still need to think about
json = {"k": {"k2": {"k3": [1,]}}} where we differ from black in trailing commas for all the outer dicts

so many merge conflicts today :(

hm i can't reproduce this test failure locally

Could you try cargo insta test --all --all-features --delete-unreferenced-snapshots? That should delete the extra snapshot.

ah, thanks
i was very confused because my original patch didn't touch that file but i realise now that my patch +the most recent rebase made ruff match black exactly for this file which removes the snap file

so many merge conflicts today :(

I'm sorry 😞

so many merge conflicts today :(

I'm sorry 😞

no worries, all good


Release 1.0.0a17

Codenamed "Dublin". :-)

Released at https://pypi.org/project/pup/1.0.0a17/.
Closing.


PubSub: (Python)  How to use JSON string as the credential  for Client initialization instead of the filepath

Is it possible to use just the JSON authentication credentials instead of a declaring the path to the file the contains the JSON, like so with the Python SDK library:
import os
from google.cloud import pubsub
json_string = os.environ['PUBSUB_JSON']
creds = json.loads(json_string)
client = pubsub.PublisherClient(credentials=creds)

I can do this  technique in Node, but I am having trouble figuring out how to do the JSON only initialization in Python.
Thanks in advance.

@reselbob Thanks for asking, here is how you'd accomplish that:
import json
from google.oauth2 import service_account

info = json.loads(json_string)
credentials = service_account.Credentials.from_service_account_info(info)

Though rather than setting the PUBSUB_JSON environment variable, you could just set theGOOGLE_APPLICATION_CREDENTIALS environment variable and then
import google.auth

credentials, project = google.auth.default()

will do exactly what you want.
In general, future questions like this may be better asked on https://github.com/GoogleCloudPlatform/google-auth-library-python/.

I have closed the issue since (AFAICT) I have answered your question. If this is not the case, I'm happy to continue discussing and / or re-open.

Help?
Set GOOGLE_APPLICATION_CREDENTIALS to what, the JSON?

See: https://googlecloudplatform.github.io/google-cloud-python/latest/core/auth.html
I now realize you had set PUBSUB_JSON to the string itself rather than to a file containing the string.

Right, I just want to use the JSON string, not the file path. I looked at the link you provided. Seeing a lot of language about using the file path. Can't seem to locate an example about how to use the JSON string. But,  might be missing something.

My first example (with from_service_account_info()) should work just fine if you already have the key file loaded as a JSON string.

I am having a problem
 json_string = os.environ['PUBSUB_JSON']
 info = json.loads(json_string)
creds = service_account.Credentials.from_service_account_info(info)

client = pubsub.PublisherClient(credentials=creds)
topic_path = client.topic_path(os.getenv('GOOGLE_CLOUD_PROJECT'), 'cron_job_topic')
 data = data.encode('utf-8')
 future = client.publish(topic_path, data=data)
gives me an error:
google.auth.exceptions.RefreshError: ('invalid_scope: Empty or missing scope not allowed.', '{\n  "error" : "invalid_scope",\n  "error_description" : "Empty or missing scope not allowed."\n}')
The JSON in question works fine when loaded from file.

See my answer in https://github.com/GoogleCloudPlatform/google-auth-library-python/issues/225. Also note that you may have discovered a "bug" in Pub / Sub (#4479).

Is using env variables safer/more secure than using the json file?
What difference does it really make?

What difference does it really make?

When using environment variables, you never have to worry about credentials mistakenly being leaked via VCS.

@dhermes Thank you so much.


new lateral horn neuron terms [sf#29]

Reported by gm119 on 2014-03-28 13:08 UTC
FBrf0223996 == Fişek and Wilson, 2014, Nat. Neurosci. 17(2): 280--288
"Stereotyped connectivity and computations in higher-order olfactory neurons."
PMID: 24362761
describes the lateral horn projection neurons.
They say that there are two morphological types (see Figure 1), so it would be good to have terms for these.

Updated by mmc46 on 2014-04-24 17:52 UTC

status: open --> accepted

Commented by mmc46 on 2014-04-25 10:13 UTC
Hi Gillian,
I've added the two new types:
adult lateral horn type I neuron FBbt:00110876
adult lateral horn type II neuron FBbt:00110877

Updated by mmc46 on 2014-04-25 10:13 UTC

status: accepted --> closed

Updated by mmc46 on 2014-04-25 10:54 UTC

status: accepted --> closed


Cache exchange rates

I use lots of short invocations of numbat with fetching-policy = "on-first-use" which means it re-fetches the rates every time I open it to do a quick currency conversion.  The on-startup fetching policy makes it a bit better, but the delay is still noticeable if the first thing I do uses currency, and it just feels wasteful to download them every time when they're only updated daily. This change reuses the fetched rates for 24 hours to alleviate that delay.
This could make the rates up to a day out of date (if you happened to fetch them the first time right before the European Central Bank releases the next day's rates). In my mind this isn't hugely important as anyone who needs super up-to-date rates is probably using a different source in the first place, but the max age could be changed to something shorter to make it fetch more aggressively. If users want even more control, max-age could be specified as a config option in the [exchange-rates] section.

Thank you for looking into this. I believe we also have a ticket for this.
I only had a quick glance at the code. I think the caching should rather be moved to the application layer, not to the numbat-exchange-rates library. I realize that this is a bit harder to implement (as we need to serialize/deserialize), but I think that would be cleaner.

When you say it should be in the "application layer" do you mean that numbat-cli should specify how writing and loading the cache file works? For that to work with on-demand currency loading there would need to be some sort of callback when the rates get fetched. I've roughed out that change in this commit but it a bit of a mess. Let me know if that's the direction you were thinking of and if so I'll try to clean it up and add it here.
Also I see #315 but that's kind of the opposite issue, was there another ticket you were thinking of?

I don't fully understand why we need this setup with two closures and additional locks.
Could we add a (possibly atomic?) filesystem_caching_enabled flag to the ExchangeRates struct, set that according to the config when starting the application, and then internally have two branches for the caching/non-caching case?

I'm closing this due to inactivity. Please feel free to comment in case it should be re-opened.


Verify contents and format of track documentation

Each language track has documentation in the docs/ directory, which gets included on the site
on each track-specific set of pages under /languages.
We've added some general guidelines about how we'd like the track to be documented in exercism/exercism.io#3315
which can be found at https://github.com/exercism/exercism.io/blob/master/docs/writing-track-documentation.md
Please take a moment to look through the documentation about documentation, and make sure that
the track is following these guidelines. Pay particularly close attention to how to use images
in the markdown files.
Lastly, if you find that the guidelines are confusing or missing important details, then a pull request
would be greatly appreciated.

We've had good docs since about day one and they're up to date, so I think this is resolved.


Unable to use load_file when using the argument file_conn_id

Context
Astro version: 0.5.1 and before
One of the arguments for load_file is file_conn_id, as we can see in the code. However, if a user attempts to use it with either GCS or S3 at the moment, it does not work.
Within Astro, we are not using Airflow Hooks to interface with these - and the part of the code which retrieves credentials for S3 and GCS does not take into account file_conn_id.
Acceptance criteria

Have tests covering this scenario
Fix load_file so it uses file_conn_id, if declared.
Ask @guohui-gao (bug reporter) to review the change

This is currently breaking the CI of the data team, so I'm giving it a higher priority


Remove feature brookly-software-cm

👍 LGTM.  This was causing problems with a build, when tests were failing upon building with a clean Maven repository.  Taking the cm feature out allows the server tests to succeed. At some stage it would be good to produce separate feature.xml for features defined in brooklyn-library, and have these incorporated into a final feature set by brooklyn-dist, but this PR is fine for now.

+1 for the quick fix. A proper solution would be to move karaf/apacke-brooklyn to brooklyn-dist.


Would it be possible to use abs_path instead of absoluteURI for Request-URI* in HTTP client ?

Would it be possible to use abs_path instead of absoluteURI for 5.1.2 Request-URI in HTTP client ?
Reference: https://www.w3.org/Protocols/rfc2616/rfc2616-sec5.html
Context:

using zio-http Client.request("http://localhost:8000/")
error 404 when testing a service not supporting absoluteURI

Current behavior:

use absoluteURI to provide Request-URI in request

<IP_ADDRESS> - - [25/May/2021 22:01:35] code 404, message File not found
<IP_ADDRESS> - - [25/May/2021 22:01:35] "GET http://localhost:8000/ HTTP/1.1" 404 -

Expected behavior:

use abs_path to provide Request-URI in request

<IP_ADDRESS> - - [25/May/2021 21:45:01] "GET / HTTP/1.1" 200 -

EncodeRequest.encodeRequest is computing uri as req.url.asString and so always provide absoluteURI instead of abs_path when not using proxy
Some HTTP servers do not support absoluteURI although they should be.
Example of non compliant server:  python3 -m http.server

I suggest something like https://github.com/jlcanela/zio-http/commit/4ee25a1b14c5f6613e8b4662e6065d6f42ed6f08

@jlcanela can you help me understand the use-case where absoluteURI doesn't work to get a better idea.

Sure, when you have an absoluteURI the http request contains the following:
GET http://localhost:8000/ HTTP/1.1

When you use abs_path  the http request contains the following:
GET / HTTP/1.1

When you use zio-http as web server server absoluteURI is properly managed, unfortunately that’s not the case for all http server:  python3 -m http.server, the local python server expects the URI to be the file path to serve and cannot file the file to server when the uri is http://localhost:8000/.
Note that curl is using abs_path:
 curl -v http://localhost:8000/
*   Trying <IP_ADDRESS>:8000...
* TCP_NODELAY set
* Connected to localhost (<IP_ADDRESS>) port 8000 (#0)
> GET / HTTP/1.1
> Host: localhost:8000
> User-Agent: curl/7.68.0
> Accept: */*

Note that when using a proxy config (zio-http client does not support proxy config yet) it’s mandatory to use absoluteURI and not abs_path.

Fixed in #239 Thank you @jlcanela !


Automatically document directories by creating respective dox files

Is your feature request related to a problem? Please describe.
Referring to https://github.com/marzer/poxy/issues/21#issuecomment-1449182509, "registering" documented files with Doxygen stands out as notably user-hostile, particularly when dealing with local installations. In short, with a local project structure, we must "describe" each directory from our source-tree, as these directories don't rely on relative paths. For example:
/// @dir C:/Users/wroy/Desktop
/// @brief a

/// @dir echo
/// @brief b

/// @dir echo/echo
/// @brief c

/// @file echo.hxx
/// @brief d

This doesn't transition effectively to CI or to another individual's computer. In such cases, they would need to modify "C:/Users/wroy/Desktop" to indicate the correct absolute path.
Describe the solution you'd like
During the generation phase, it might be advisable to automatically document directories (using path or recursive_path as context) by creating respective dox files with "@dir" and "@brief" annotations. If a user wishes to furnish directory description, then a manually created dox file should take precedence
Additional context
☕

oooooh that's a great idea, and likely quite easy to implement

This doesn't transition effectively to CI or to another individual's computer.

This seems to be a recurring issue that everyone suffers from which I myself never had a problem with. I've never needed to include the full path for the @dir or @file commands, never in the 15 years of working with Doxygen. There were insane bugs all over, but this was never a problem. So I'd like to understand what is it everyone else is doing differently that they run into this :D What are your INPUT, STRIP_FROM_PATH and STRIP_FROM_INC_PATH settings?
See also this comment.

And I assume you want /home/wroy/hello stripped away, right?
The relevant Doxyfile parts are this:
STRIP_FROM_PATH        = "/tmp/poxy/bug_report/temp/pages"
STRIP_FROM_INC_PATH    =
INPUT                  = "/home/wroy/hello/hello" \
                         "/home/wroy/hello/libhello" \
                         "/tmp/poxy/bug_report/temp/pages"

Not sure what's the temp pages directory but it should be something like this instead, I think, then it wouldn't include the whole path in the file list. The project root is probably something the project configuration itself should specify, can't really automate that I think -- there's not really a way to know whether it's meant to be #include <libhello/hello.h> or just #include <hello.h>.
STRIP_FROM_PATH        = "/home/wroy/hello" \
                         "/tmp/poxy/bug_report/temp/pages"
STRIP_FROM_INC_PATH    = "/home/wroy/hello"
INPUT                  = "/home/wroy/hello/hello" \
                         "/home/wroy/hello/libhello" \
                         "/tmp/poxy/bug_report/temp/pages"

Alright, thanks for clarifying :)

which is what becomes doxygen's STRIP_FROM_PATH.

So I assume it does basically what I suggested above, right? I wonder if this is where poxy automagic would help, i.e. setting the STRIP_FROM_*_PATH implicitly to something. Which might be possibly wrong (stripping too much), but in my opinion better than having C:/ or /home/whoever shown in the output :D

@wroyca I promise you you don't need to be explicit about paths at any point, apart from the 'strip from' setting. You are doing something weird that isn't obvious to me.

Well yes, but that's by design? You don't need to be explicit in your @dir annotations, so I dont understand what the issue is.

Like, you pretty much have to use strip_paths / STRIP_FROM_PATH. I should make it emit a warning in poxy when it's omitted, tbh.
Unless we want to get into guessing the project root, but that's orthogonal to the idea of autogenerating @dir entries.

Yeah, that's the problem, you're using absolute paths. Don't use them. Anywhere. If everything is relative to the Doxyfile, the INPUT, the STRIP_FROM_PATH, etc., then it works.


💄(layout) improve course detail integration

Purpose
So far the course detail render is very basic and course lacks of a
preview image in glimpse.
Proposal
This commit add a new placeholder 'course_cover' to add a preview
image to use in glimpse instead of video teaser that does not fit
well in card format. Course factory, detail template and demo-site
command have been upgraded to include it.
Then we upgrade the detail template and CSS to fit to fun-mooc.fr
course detail page but with according to our content structure,
especially the course runs that are not managed in same way.

@sveetch I proposed a solution so that the cover images are in sync with the video teaser while still being picked randomly.


Allow override text wrapping style inside api response

By editing in browser with these:
.m-markdown-small pre code, .m-markdown pre code {
    border: none;
    padding: 0;
    text-wrap-mode: wrap;
    overflow-wrap: anywhere;
}

Will result what I want:

But I can't find the way to override the style.
Please allow us to override code wrapping for api response.

Nvm, I decided to edit it on css style file and build it on my own.


[Mobile] - Wallet data is overflowing the container in mobile

Description
Rows were overflowing from the container, they were switched by wrap
Small incremental to the font to make it a little more esthetic.
Fixes Jira Ticket #
Type of change
Design
Is this a UI Change? If so please include screenshot of before and after states below
How Has This Been Tested?
localhost
Checklist:

[x ] My code follows the style guidelines of this project
[x ] I have performed a self-review of my own code
[x ] I have assigned 2 reviewers to check my work
[ x] I have commented my code, particularly in hard-to-understand areas
[x ] I have made corresponding changes to the documentation
[x ] My changes generate no new warnings
[x ] I have added tests that prove my fix is effective or that my feature works
[x ] New and existing unit tests pass locally with my changes
[ x] Any dependent changes have been merged and published in downstream modules

Also it looks like the disconnect button is touching the border of that dialog as per the screenshot on the ticket description. You will need to fix that as well


Bug: workflow is not running analyzers

build-and-test needs to compile in /Release.
Analyzer catches this in /Release compile only.
https://github.com/TimothyMothra/D2WeaponReport/blob/3f18b30c0e0a38fc445a03386cdeb5f9b3d3452d/src/DestinyLib/Database/WorldSqlContentProvider.cs#L115-L116

resolved


change the contact us form

Related Issue

Closes: #300
Description of Changes

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] I have included comments in areas that may be difficult to understand.
[x] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots
|      Original       |       Updated        |
| :-----

|  |

Please provide any necessary screenshots to illustrate the changes made.

Please correct this error:


Add 'BrownFi' to Dex

Dear @trmaphi,
In order to potentially merge your code in this open-source repository and therefore proceed with your contribution, we need to have your approval on DFINITY's CLA.
If you decide to agree with it, please visit this issue and read the instructions there. Once you have signed it, re-trigger the workflow on this PR to see if your code can be merged.
— The DFINITY Foundation

@flyq can we proceed with the review?

@trmaphi Please accept the CLA. See the message of the bot above.


chore: switch domain to status-legacy.ory.sh

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: tricky42:white_check_mark: aeneasr:x: upptime-botYou have signed the CLA already but the status is still pending? Let us recheck it.


Crash in handleMultiConnectResolved method if error or port parameter is NULL.

ThaliTest crash if nil passed to handleMultiConnectResolved method as error or port parameter.

PR #1846


[Bug]: Make scrolling animation independent of android's default animation config

Is there an existing issue for this?

[X] I have searched the existing issues

Is there a StackOverflow question about this issue?

[X] I have searched StackOverflow

Is this an issue related to one of the samples?

[X] Yes, this is a specific issue related to this samples repo.

Sample app
JetNews
What happened?
The scroll animation doesn't work when android animation set to 0x.
Scrolling shouldn't be considered as animation in the first place. That's how the default behaviour is on other compositors.
Many users still turn off animation due to it's opera/strechy nature bringing dizzyness to eyes.
Relevant logcat output
No response
Code of Conduct

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

This is newly introduced in Jetpack compose. Earlier, scrolling animation still used to work even on disabled animations. I hope scrolling animation to be independent of animator_duration_scale.

This issue seems unrelated to the compose-samples repository directly, issues here are reserved for bug reports within the compose-samples apps or feature requests for the sample apps.
If you find an issue with an Android Jetpack Compose components, report it using the Jetpack Compose issue tracker.

Tq. But I don't have a google account nor it's services work in my locality. Can I request you devs to open an issue tracker by yourselves?

We'll follow up on https://issuetracker.google.com/241460890, thanks!

So, is this commit  considered a fix to this issue ?

@pc00per Yes, that will make the flinging/scrolling independent of the animation scale, so it should be similar to how it works in views.

Now, latest bom is 2022.12.00. Before bom 2023.02.00, we still have to manually upgrade compose dependencies to fix this issue. The following patch works for JetNews.
diff --git a/JetNews/app/build.gradle.kts b/JetNews/app/build.gradle.kts
index 927401b2..52553eba 100644
--- a/JetNews/app/build.gradle.kts
+++ b/JetNews/app/build.gradle.kts
@@ -95,8 +95,8 @@ android {

 dependencies {
     val composeBom = platform(libs.androidx.compose.bom)
-    implementation(composeBom)
-    androidTestImplementation(composeBom)
+//    implementation(composeBom)
+//    androidTestImplementation(composeBom)

     implementation(libs.kotlin.stdlib)
     implementation(libs.kotlinx.coroutines.android)
diff --git a/JetNews/gradle/libs.versions.toml b/JetNews/gradle/libs.versions.toml
index 7eefd271..e22676b6 100644
--- a/JetNews/gradle/libs.versions.toml
+++ b/JetNews/gradle/libs.versions.toml
@@ -26,7 +26,7 @@ androix-test-uiautomator = "2.2.0"
 coil = "2.2.0"
 # @keep
 compileSdk = "33"
-compose-compiler = "1.3.2"
+compose-compiler = "1.4.0-alpha02"
 compose-snapshot = "-"
 coroutines = "1.6.4"
 google-maps = "18.1.0"
@@ -36,7 +36,7 @@ hiltExt = "1.0.0"
 jdkDesugar = "1.2.2"
 junit = "4.13.2"
 # @pin update when updating Compose Compiler
-kotlin = "1.7.20"
+kotlin = "1.7.21"
 maps-compose = "2.5.3"
 material = "1.8.0-beta01"
 # @keep
@@ -63,21 +63,21 @@ androidx-benchmark-macrobenchmark = { module = "androidx.benchmark:benchmark-mac
 androidx-benchmark-macrobenchmark-junit4 = { module = "androidx.benchmark:benchmark-macro-junit4", version.ref = "androidx-benchmark-junit4" }
 androidx-compose-animation = { module = "androidx.compose.animation:animation" }
 androidx-compose-bom = { module = "androidx.compose:compose-bom", version.ref = "androidx-compose-bom" }
-androidx-compose-foundation = { module = "androidx.compose.foundation:foundation" }
-androidx-compose-foundation-layout = { module = "androidx.compose.foundation:foundation-layout" }
-androidx-compose-material = { module = "androidx.compose.material:material" }
-androidx-compose-material-iconsExtended = { module = "androidx.compose.material:material-icons-extended" }
-androidx-compose-material3 = { module = "androidx.compose.material3:material3" }
-androidx-compose-materialWindow = { module = "androidx.compose.material3:material3-window-size-class" }
-androidx-compose-runtime = { module = "androidx.compose.runtime:runtime" }
-androidx-compose-runtime-livedata = { module = "androidx.compose.runtime:runtime-livedata" }
+androidx-compose-foundation = { module = "androidx.compose.foundation:foundation"}
+androidx-compose-foundation-layout = { module = "androidx.compose.foundation:foundation-layout"}
+androidx-compose-material = { module = "androidx.compose.material:material" ,version="1.4.0-alpha03"}
+androidx-compose-material-iconsExtended = { module = "androidx.compose.material:material-icons-extended",version="1.4.0-alpha03" }
+androidx-compose-material3 = { module = "androidx.compose.material3:material3" ,version="1.1.0-alpha03"}
+androidx-compose-materialWindow = { module = "androidx.compose.material3:material3-window-size-class" ,version="1.1.0-alpha03"}
+androidx-compose-runtime = { module = "androidx.compose.runtime:runtime",version="1.4.0-alpha03" }
+androidx-compose-runtime-livedata = { module = "androidx.compose.runtime:runtime-livedata",version="1.4.0-alpha03" }
 androidx-compose-ui = { module = "androidx.compose.ui:ui" }
 androidx-compose-ui-googlefonts = { module = "androidx.compose.ui:ui-text-google-fonts" }
 androidx-compose-ui-test = { module = "androidx.compose.ui:ui-test" }
-androidx-compose-ui-test-junit4 = { module = "androidx.compose.ui:ui-test-junit4" }
+androidx-compose-ui-test-junit4 = { module = "androidx.compose.ui:ui-test-junit4",version="1.4.0-alpha03"}
 androidx-compose-ui-test-manifest = { module = "androidx.compose.ui:ui-test-manifest" }
 androidx-compose-ui-tooling = { module = "androidx.compose.ui:ui-tooling" }
-androidx-compose-ui-tooling-preview = { module = "androidx.compose.ui:ui-tooling-preview" }
+androidx-compose-ui-tooling-preview = { module = "androidx.compose.ui:ui-tooling-preview" ,version="1.4.0-alpha03"}
 androidx-compose-ui-util = { module = "androidx.compose.ui:ui-util" }
 androidx-compose-ui-viewbinding = { module = "androidx.compose.ui:ui-viewbinding" }
 androidx-constraintlayout-compose = { module = "androidx.constraintlayout:constraintlayout-compose", version.ref = "androidx-constraintlayout" }


Question: How to cancel a notification, even if it's an ongoing notification?

I've noticed an app offers to do it somehow (here) .
How come?
I only succeeded doing it to normal notifications:
https://stackoverflow.com/q/51587436/878126

Seems it's possible using:
https://developer.android.com/reference/android/service/notification/NotificationListenerService.html#snoozeNotification(java.lang.String, long)


[3.x] Clicking on script in scene tree in editor takes you to 3D view instead of the script

Godot version
v3.6.beta.custom_build [d5a56f023] (bug introduced today 2 Aug 2023)
System information
All
Issue description
Open editor for a scene, click on a script in the tree view. It takes you to 3D window instead of the script.
Steps to reproduce
As above.
Minimal reproduction project
N/A.

Looks like a regression from #79947 .

Fixed by #80197.


Thank you for this awesome work! I'd love to know what's in the roadmap.

I see this is a 2b model, will 5b or bigger be trained? Will all your releases be open source? Thank you!

Awesome work indeed, for its size and speed the output quality is mindblowing. Waiting for the paper :)


Customer feedback | az monitor scheduled-query | has incorrect status for extension name

Describe the bug
Engineering request
Please update the status of the scheduled-query extension to reflect GA as all the az monitor scheduled-query commands are showing GA.
Conflicting status information
The scheduled-query extension is showing as preview -->

The in-line help is also showing preview -->

The az monitor scheduled-query commands are showing as GA -->

Related command
az monitor scheduled-query
Errors
Conflicting status information
Issue script & Debug output
n/a
Expected behavior
n/a
Environment Summary
Azure CLI 2.65.0
Additional context
No response

Thank you for opening this issue, we will look into it.


[question] fs-loader gives error: NodeInvocationException: n.i(...) is not a function

I'm using Angular 4 Universal with .net core 2 (vs 2017 core 2 template)
I have installed:
"@ngx-config/core": "^0.2.0-rc.5",
"@ngx-config/fs-loader": "^0.2.0-beta.1",
my setup:
`export function configFactory(): ConfigLoader {
return new ConfigFsLoader('./ng-app-settings.json'); // FILE PATH
}
imports: [
ConfigModule.forRoot({
  provide: ConfigLoader,
  useFactory: (configFactory)
}),

`
and I get an error at run time:

NodeInvocationException: n.i(...) is not a function
TypeError: n.i(...) is not a function
at t.loadSettings (\ClientApp\dist\main-server.js:18307:931)
at t.init (C:\projects\stash\liveflo\liveflo.spa\src\XpertHR.Liveflo.SPA\ClientApp\dist\main-server.js:11120:1234)

my package.json
{   "name": "xperthrliveflospa",   "private": true,   "version": "0.0.0",   "scripts": {     "test": "karma start ClientApp/test/karma.conf.js"   },   "dependencies": {     "@angular/animations": "4.2.5",     "@angular/common": "4.2.5",     "@angular/compiler": "4.2.5",     "@angular/compiler-cli": "4.2.5",     "@angular/core": "4.2.5",     "@angular/forms": "4.2.5",     "@angular/http": "4.2.5",     "@angular/platform-browser": "4.2.5",     "@angular/platform-browser-dynamic": "4.2.5",     "@angular/platform-server": "4.2.5",     "@angular/router": "4.2.5",     "@ngrx/core": "^1.2.0",     "@ngrx/effects": "^2.0.4",     "@ngrx/store": "^2.2.3",     "@ngrx/store-devtools": "^3.2.4",     "@ngtools/webpack": "1.5.0",     "@ngx-config/core": "^0.2.0-rc.5",     "@ngx-config/fs-loader": "^0.2.0-beta.1",     "@ngx-config/http-loader": "^0.2.0-rc.1",     "@types/webpack-env": "1.13.0",     "angular2-template-loader": "0.6.2",     "aspnet-prerendering": "^3.0.1",     "aspnet-webpack": "^2.0.1",     "awesome-typescript-loader": "3.2.1",     "bootstrap": "3.3.7",     "css": "2.2.1",     "css-loader": "0.28.4",     "es6-shim": "0.35.3",     "event-source-polyfill": "0.0.9",     "expose-loader": "0.7.3",     "file-loader": "0.11.2",     "file-system": "^2.2.2",     "html-loader": "0.4.5",     "intl": "^1.2.5",     "isomorphic-fetch": "2.2.1",     "jquery": "3.2.1",     "json-loader": "0.5.4",     "preboot": "4.5.2",     "raw-loader": "0.5.1",     "reflect-metadata": "0.1.10",     "rxjs": "5.4.2",     "style-loader": "0.18.2",     "to-string-loader": "1.1.5",     "typescript": "2.4.1",     "url-loader": "0.5.9",     "webpack-hot-middleware": "2.18.2",     "webpack-merge": "4.1.0",     "zone.js": "0.8.12"   },   "devDependencies": {     "@types/chai": "4.0.1",     "@types/jasmine": "2.5.53",     "@types/jquery": "^3.2.11",     "@types/node": "~6.0.60",     "@types/yfiles": "0.0.2",     "chai": "4.0.2",     "jasmine-core": "2.6.4",     "karma": "1.7.0",     "karma-chai": "0.1.0",     "karma-chrome-launcher": "2.2.0",     "karma-cli": "1.0.1",     "karma-jasmine": "1.1.0",     "karma-webpack": "2.0.3",     "ngrx-store-freeze": "^0.1.9",     "node-sass": "^4.5.3",     "sass-loader": "^6.0.6",     "webpack": "^2.5.1"   } }

@shivark I assume you have this error message either on a production build, or the output code has been uglified/minified. This way, I have really very little information about what exactly you're facing there.
Could you please turn them off and observe the debug message, for a better chance to reproduce this?

Hi thanks for the reply. I couldn't turn off the uglify, but found where it fails:
 ConfigFsLoader.prototype.loadSettings = function () {         return Promise.resolve(JSON.parse(readFileSync(this.path, 'utf8')))             .then(function (settings) { return settings; })             .catch(function () { return Promise.reject('Path unreachable!'); });     };
readFileSync is not defined.
So  import { readFileSync } from 'fs'; does not work.
Do you know why? Do I need a specific Node version? or is it dependent on other npm?

@shivark thanks for debugging it line-by-line, and now things are obvious.
Actually fs belongs to the server part of Node.js environment - not the browser. However, within the ngx-config ecosystem, fs-loader only runs on a server environment. So here are my suggestions:

please check your package.json, and verify whether @types/node are included in your devDependencies or not
also, check your tsconfig.json and whether if you use all types (if any types are declared, then the compiler use them - if not, uses all)
again in your tsconfig.json, check if typeRoots exists - which defaults to node_modules/@types
again in your tsconfig.json, check include, exclude and files sections about inclusion of that erroneous file to the compilation

Beyond this point, you've gotta check your build tool (systemjs, webpack, fuse-box, rollup, etc). Basically this failure happens when mocking the fs at the browser environment and each has a different method to mock the fs.
For webpack, you can check this config (https://github.com/ng-seed/angular-webpack-config/blob/master/src/webpack.common.js#L447) at  angular-webpack-config repo.
Let me know about the results, and happy coding!


Speed-up GWR

Related to #4

Move the fast fit feature from GWR class to sel_bw class.
Revert gwr.py to very beginning since features in last PR are moved to 'sel_bw.py' where I think it could be.
Pass distance matrix in every kernel calculation to avoid repeated calculations.
Using OLS for Gaussian fit and IWLS for other Generalized models. This will make Gaussian fit faster, which may be the most common use case

Finally had a chance to take a close look at this. So, I get the logic of moving it from the GWR class to the bandwidth selection class. A few things I think we could work on in order to tighten up such a large refactor.
(1) It looks as if none of the previous diagnostics are being used from the diagnostics.py module. I'm guessing that this is because they take a gwr object as input. One issue with defining the diagnostics in the sel_bw class is that then we have to maintain the math for those diagnostics in two different places. We could perhaps have a gwr_light object that could be instantiated with fewer attributes but could still have the necessary infrastructure to be able to be passed to diagnostics functions. That would mean we wouldn't need to have so much "fitting" code floating within the bandwidth selection routine.
(2) Just noticed a double loop when computing spherical distance from lat/long. Would be possible to convert this to matrix form to avoid the loops? Could be prohibitive for large datasets.
(3) I'm wondering if we can also utilize the matrix algebra from the _compute_betas_gwr function in the iwls module so that the OLS routine used here is not duplicating code. IIRC, it is the same math for the OLS and GLM, just the GLM includes iterative weighting. So a single iteration of the iwls routine should give the same results as the OLS. Therefore we should be able to just use the _compute_betas_gwr function as is or use iwls with a flag that skips over the iterative weighting for the GLM routine. This may also be beneficial since the iwls routine is already designed to be able to use sparse matrices, which we mentioned might be useful in certain circumstances.
Will take another look at this and see if I think of anything else.
Any thoughts, @ljwolf?

The .pyc functions need to be removed from the PR

Just a few initial comments. I'll need a few days to read & understand.

Several updates regarding comments and suggestions from @ljwolf  and @TaylorOshan :

Removed .pyc
Removed _haversine() and perhaps using libpysal.cg.sphere  for handling lat-long.
Using iwls._compute_betas_gwr() to do solving instead of duplicating matrix inverse codes. The current iwls() for Gaussian requires two iterations since the betas are initiated using zeros. Thus another (2nd) iteration is needed to converge. And thus it is twice slower than OLS. But directly calling iwls._compute_betas_gwr() only solves mat inverse once, which is faster.

To ensure we move forward, we will take the simpler optimizations and get them factored in first and then we can discuss some of the more complicated optimizations after doing some profiling. Specifically, @Ziqi-Li and I discussed integrating the changes that thread the W matrix through the bandwidth selection so that they are not re-computed many times. And then we will leave the refactor that minimizes the computation of diagnostics for another PR. The thinking is that after we integrate the W matrix optimization (and the previously introduced optimization of the golden_section routine where two unused computations are commented out) than we do some profiling and see what the best way to minimize the computation time for diagnostics would be while also considering the use of sparse data structure.

Great, sounds good to me


bump lifecycled from 3.0.2 to 3.2.0

There have been two releases of lifecycled in the past 3 months - 3.1.0 and 3.2.0.
Neither has any changes that should impact the elastic stack, but it's nice to stick near the latest release so the delta between the elastic stack and upstream doesn't get too big.
Most of the changes are about updating the version of go we build with, and updating some key dependencies (like aws-sdk-go).

I created a test stack with this branch and confirmed it scales up correctly and executes jobs:

I didn't confirm that spot instance terminations are detected and handled by lifecycled, but we can be confident there's no show-stopping issues with this upgrade :sparkles:


Emi failed to load correctly on neoforge 20.4.70+

java.lang.NoClassDefFoundError: net/neoforged/neoforge/network/INetworkDirection

Neo seems to have broken their networking API half way through a version which is quite annoying. EMI will have to be updated.

Fixed in 1.0.30


Crashing on Show in Xamarin Android

File res/mipmap-xxhdpi-v4/icon.png from xml type layout resource ID #0x7f030000
its giving run time exception like this

@AbhishekSinghThakur can you provide a little more detail please.

the lib does not use res/mipmap-xxhdpi-v4/icon.png can you make sure its not being used by your project. Also can you share the error logs

I'm also not getting why is giving that kind of errors when I removed the mipmap the error changes but still its crashing.
So why don't you do a favour , make a sample to open country code picker dialog on button click with your nuget in Xamarin android to identify that you lib don't have any issues

Too much effort to prove the issue is not in the library. your comment I'm also not getting why is giving that kind of errors when I removed the mipmap the error changes but still its crashing. above states clearly not an issue with the library

Bro, I just want to use you lib tell me what I can do in xamarin android simple.
I'm not saying the problem is with lib or something else thing is that Dialog is not appearing in xamarin android and its crashing. Rather then just giving explanation to prove the lib don't have any issue just try it at your end in Xamarin android as I have used same lib in fresh project too and still the same issue its crashing.


Error loading library for python: ModuleNotFoundErrorNo module named 'yapf'

Installed code_prettify as part of a bundle of Jupyter notebook extensions.
Now all of a sudden I get error message in title every time I load a notebook.
Very annoying.

'pip install yapf' will solve this issue. If you are using conda 'conda install yapf'


allow free variable bindings within db.run

I'm planning to work on this change, please let me know you thoughts.
Problem
The quotation mechanism for parametrized quotations requires too much boilerplate code for simple queries. Example from @takezoe's gitbucket:
   def updateGroupMembers(groupName: String, members: List[(String, Boolean)]): Unit = {
     db.run(
       quote { (groupName: String) => query[GroupMember].filter(_.groupName == groupName).delete }
     )(List(groupName))

There are two main problems here:

Inline quotations (see readme change) don't support parametrization, so quote must be explicit.
It's not possible to directly bind the runtime values.

Solution
Allow references to runtime values within a db.run call:
   def updateGroupMembers(groupName: String, members: List[(String, Boolean)]): Unit = {
     db.run(query[GroupMember].filter(_.groupName == groupName).delete)

This will be the default way to bind runtime values, so the second parameters group will be removed.
Notes
Quotations outside the db.run call won't support free variables. It'd be possible to implement it, but it's more complex and I think it'd make it harder to reason about query composition if we mix quotation composition with runtime values.
Checklist

[ ] Unit test all changes
[ ] Update README.md if applicable
[ ] Add [WIP] to the pull request title if it's work in progress
[ ] Squash commits that aren't meaningful changes
[ ] Run sbt scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

Yes, this is the most painful part of quill, the parameters is often repeated twice, one for method, another for qutoed functions.

:+1: For most simple use cases of quill this would make the live much easier :)

I really like it, less boilerplate. :+1:
One question, if you don't use inline quotation, how would you pass a runtime variable to run?

@gustavoamigo It'd be through a parametrized quotation:
val q = quote {
  (name: String) => query[Person].filter(_.name == name)
}

db.run(q("flavio"))

:+1: really nice
Would actions (Insert, Delete, Update..) change as well?
On Thu, Mar 10, 2016 at 12:30 PM Flavio W. Brasil<EMAIL_ADDRESS>wrote:

@gustavoamigo https://github.com/gustavoamigo It'd be through a
parametrized quotation:
val q = quote {
(name: String) => query[Person].filter(_.name == name)
}
db.run(q("flavio"))
—
Reply to this email directly or view it on GitHub
https://github.com/getquill/quill/pull/262#issuecomment-194905607.

Would actions (Insert, Delete, Update..) change as well?

Yep!

@getquill/maintainers I've get a first working version of this change. The existing API that allows a second group of runtime values will continue to exist because I couldn't come up with a good API for batch actions without it.
I'd appreciate if you could give the branch a try. I'm still planning to work on some details, but as it touches some complex and fragile code, an early feedback would be great.

@getquill/maintainers I've changed the build script to generate snapshots for branch builds. You should be able to test it using the version free-binding-SNAPSHOT instead of 0.5.0-SNAPSHOT.
BTW, feel free to work on branches instead of your forks if you like. I find it more convenient.

I have just updated my test project to this version and, before doing any change to use the new feature, everything works.

@getquill/maintainers this is now ready to merge, waiting for your :+1:s

I'll do some tests today.

@fwbrasil
If I do something like this:
  def update(user: User) =
    db.run(users.filter(_.id == user.id).update(_.name -> user.name, _.isActive -> user.isActive))

It throws the following error:
[error] /Users/gustavoamigo/Projects/play-quill-jdbc/app/services/UserServices.scala:26: Source doesn't know how do encode 'user: services.User'
[error]     db.run(users.filter(_.id == user.id).update(_.name -> user.name, _.isActive -> user.isActive))

Is it easy to fix or do you think we should do this in another branch?
Here is the complete code:
https://github.com/getquill/play-quill-jdbc/blob/free-binding/app/services/UserServices.scala

@gustavoamigo it's a bug. I'd like to fix it with another PR if you agree.

:+1:  I tested following queries, both are ok.
val id = 0
QDB.run(infix"select * from `order` where id > $id".as[Order])

def foo(a: Int) = QDB.run {
   query[Order].filter(_.id > a)
}

:+1:


Move MySpringBeanProcessor to RESTEasy

MySpringBeanProcessor is a re-implementation of a core RESTEasy/Spring integration class to fix some fundamental problems in the original implementation.  Move the MySpringBeanProcessor functionality back to RESTEasy

done