BUG date_range for Annual interval gives end of year instead of start

When Creating an Annual date range from the start of a year, the actual dates generated are for the END of that year, and do not include the datetime provided. You would expect to get a range starting from start_date and a series of subsequent dates one year apart
pd.date_range(datetime.datetime(2006, 1, 1, 0,0,0), periods=2, freq='A')

<class 'pandas.tseries.index.DatetimeIndex'>
[2006-12-31, 2007-12-31]
Length: 2, Freq: A-DEC, Timezone: None

For reference, using dateutils.rrule gives intuitive behavior
list(rrule(YEARLY, count=2, dtstart=datetime.datetime(2006, 1, 1, 0,0,0)))

[datetime.datetime(2006, 1, 1, 0, 0), datetime.datetime(2007, 1, 1, 0, 0)]

I don't think this is a bug, but a choice at the time the aliases were made.  This is clearly laid out in the date offset documentation ("Offset Aliases" section).
A	year end frequency
BA	business year end frequency
AS	year start frequency

Agreed with @rockg. I'm guessing the year-end by default is common for many fields, so we can't really say that year-start frequency is more intuitive. Plus pd.date_range(start='2015-01-01', end='2015-12-31', freq='A'), forces you to drop at least one of those dates.

Well it is also inconsistent with rrule which would be the closest analogue outside of Pandas. I actually ran into this when converting code from using rrule to pandas and it definitely seems odd. I'm not sure what application defaults to the end of the year.
As for pd.date_range(start='2015-01-01', end='2015-12-31', freq='A') - it seems to me strange to drop the starting date, since most cases in python ranges are left-closed (include the start but not the end). To me this is like writing range(0,10,10) and getting 10 instead of 0. Similarly if you use the periods=1  you supply a start date that is not included in the resulting range. This IMHO is weird behaviour, considering that the simplest case should follow the most common pattern.

Is left closed more common though (I agree that is is for other python ranges)? But for date stuff, I could see this being the natural behavior (I'm thinking of finance). This had to have been a deliberate choice, and not an implementation detail I think.
Anyway, this would be a big break in backwards compatibility, and I don't think that the benefit justifies the break. Do you? If we did do anything, I'd break date_range into two functions, one for specifying start, end and freq, and another for specifying (start or end), periods, and freq.
Usually in these situations I'd say we need better documentation. The offsets docs are clear I think, maybe we should note that in the docstring for date_range / DatetimeIndex?

I personally agree that start would be a more natural default to have it at the start of the year (I'm in finance and yearly aggregations are most of the time easier to think of as year beginning), but it is too entrenched to change now.  The same case could be made for M which is month end which I don't like either.  One needs to use MS just like AS.

Interesting. I wonder why this was the choice originally then. This would be a really big break in comparability though :(.

I'm sure left-closed is common usage in Python precisely because it matches the behaviour of range and indexing - any deviations from this habit need to be clearly documented.
I'm not sure of the origin of this behaviour, it's odd from a physical sciences perspective, especially considering that "W - Weekly" gives you the start of the week - why start of the week but end of the year??
It at least needs to be better explained in the date_range docs (I totally missed that table before).
To avoid a backwards incompatible break I would just add new aliases (in any case "A" for "Annual" is odd, when even the docs  say "A for Year end frequency", see also https://github.com/pydata/pandas/issues/9313).
I would create aliases with Y for Year:
YE =  Year End
YS = Year Start
Y = the default (Year Start for preference)
I would also add
AE =Year End
for completeness. This would break nothing and give reasonably behaviour for someone new.
The A aliases could be kept or depreciated over time (I have no strong opinion on this).
As for Month, it should probably also get a ME alias (so at least you can be explicit) but there's otherwise not a good transition story... Maybe just doing a clean break would actually make more sense...

I like folding in the change here w/ the one from #9313.
The month story is tougher to fix. Let's see what others have to say. Sorry about closing the issue early.

I see no reason why we would change 'A' or 'M' behavior...there are offsets that already do start of the respective frequency.  We may not think they are named the best, but there must have been a reason a the time and in the grand scheme it's not a big deal--one time of getting it wrong and then one extra letter.  I agree that making the documentation clearer and adding more explicit end frequencies would be a good resolution.

@rockg certainly no need to change A - but adding Y would still make sense, I think since pandas is still under heavy development it's a good time to adjust this kind of detail. If someone can weight in explaining why that behaviour was chosen it would help the discussion.

Yes, I agree adding Y makes sense.

mo believe a lot of this came from here: http://pytseries.sourceforge.net/core.constants.html

there has been a closed argument to date_range for a while, which you can specify left/right/both to suite your needs.
In [1]: pd.date_range?
Type:        function
String form: <function date_range at 0x106ab0c08>
File:        /Users/jreback/pandas/pandas/tseries/index.py
Definition:  pd.date_range(start=None, end=None, periods=None, freq='D', tz=None, normalize=False, name=None, closed=None)
Docstring:
Return a fixed frequency datetime index, with day (calendar) as the default
frequency

Parameters
----------
start : string or datetime-like, default None
    Left bound for generating dates
end : string or datetime-like, default None
    Right bound for generating dates
periods : integer or None, default None
    If None, must specify start and end
freq : string or DateOffset, default 'D' (calendar daily)
    Frequency strings can have multiples, e.g. '5H'
tz : string or None
    Time zone name for returning localized DatetimeIndex, for example
Asia/Hong_Kong
normalize : bool, default False
    Normalize start/end dates to midnight before generating date range
name : str, default None
    Name of the resulting index
closed : string or None, default None
    Make the interval closed with respect to the given frequency to
    the 'left', 'right', or both sides (None)

Notes
-----
2 of start, end, or periods must be specified

Returns
-------
rng : DatetimeIndex

I think closed only affects the values after they've been aligned at start or end, e.g.
In [5]: pd.date_range(datetime.datetime(2006, 1, 1, 0,0,0), periods=2, freq='A', closed='left')
Out[5]:
<class 'pandas.tseries.index.DatetimeIndex'>
[2006-12-31]
Length: 1, Freq: A-DEC, Timezone: None

so it makes the date_range with two elements, [2006-12-31, 2007-12-31], and then only includes the first with closed='left' since 2007-12-31 falls on the right edge, which is open.
The issue here is that the default should be the initial two elements should be year start, [2006-01-01, 2007-01-01], independent of the closed argument. I'm cool with creating an alias Y for AS,


Finding Intersection of two LinkedList

@MoonLight9944 I want to implement the solution for this problem.
I want to contribute this for HacboberFest. Kindly Accept

Go ahead


Cheat Mode Deletion "0 air" Issue

On 1.0.19, when you cheat in an item with cheat mode, it shows that item in the logs. When you delete that item (or any item) using cheat mode, however, the logs show "0 air" instead of what it was.

I believe this has been resolved in 1.0.20


Reverse Bits | Bit manipulation | C++ | GSSoC'21

💥 Proposal
Given a number in decimal form, convert it into binary reverse its bits then obtain the decimal equivalent of the reversed bits.
Have you read the Contributing Guidelines on Pull Requests?
YES.

/assign


Add bogati2020's file

created a branch, created a file and made a commit, and opened a pull request


⚠ Exoticaz has degraded performance

In cb2a2f6, Exoticaz ($EZ) experienced degraded performance:

HTTP code: 200
Response time: 6294 ms

Resolved: Exoticaz performance has improved in 761f9af.


running Juptyer notebook at ide.coder.com

The guys at coder.com have VS Code running on a server in the browser.  The project was recently open sourced here:
https://github.com/codercom/code-server
They also provide a container space for file and program storage so I set up a conda Python environment in it.  I am trying to run the MS Python extension in this environment but VS Code cannot connect to the Jupyter server.  From a terminal I can run "jupyter notebook" which generates the error:
OSError: [Errno 99] Cannot assign requested address
I can force assign  ip=<IP_ADDRESS> and it provides a token and URL.  However VS Code never finds the server there. It sticks on "starting jupyter server"
Is anyone familiar with coder.com and their server/container environment? Is it on their end to provide the capability? Thanks.

Open the URL in your local browser. If that doesn't work our extension won't work. This would be something on the ide.coder.com side.

Browser can't open the URL so it is something they need to fix.  Thanks.


link to "Cost and usage update" + updated figures

Sent an email to banders and adwis with more detail.

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

#sign-off


fix: sdkserver: credentials: ensure credential helpers exist

Always good to add a small description about the PR to have more contex


HUM-973 Cleaning up documentation

Do not merge until I have updated/cleaned up the other repos

Feel free to merge now :)


Add exception handling for libcpp::stack::push

This adds a simple exception handling to stack::pop.
Tests are to be added, if needed.

I wonder if this should be applied to basically all stack functions? As far as I can tell they can all potentially throw exceptions (since it doesn't make assumptions about what the underlying container might do). But push is probably the most likely to throw I think.

Yes, I am first trying to understand some of the CI failures which do not seem to be related to the changes here.
-- stderr:/Users/runner/hostedtoolcache/Python/3.9.11/x64/lib/python3.9/site-packages/_distutils_hack/__init__.py:17: UserWarning: Distutils was imported before Setuptools, but importing Setuptools also replaces the `distutils` module in `sys.modules`. This may lead to undesirable behaviors or errors. To avoid these issues, avoid using distutils directly, ensure that setuptools is installed in the traditional way (e.g. not an editable install), and/or make sure that setuptools is always imported before distutils.

Closing and reopening to retrigger the CI - I can't see any way that the failures are related.

Indeed, they are gone, now.
Should I add tests? :smile:

Indeed, they are gone, now.
Must I add tests?

We've accepted similar PRs without tests before (https://github.com/cython/cython/pull/4079) so I don't think they're really necessary here.


waiter_queue RFC

Following discussions on the job_queue RFC, here is the waiter_queue module that implements just the parked calls aspect.

Let's have a second iteration where we somehow get rid of push/pop. I normally would not mind poetry as "renames are cheap", but in this case I see this used in many places throughout the codebases we have, so I think we should spend a bit of time to polish the names too.


Show path information for service parameters

fix #821

Shows access paths for service parameters
Shows scope warning, i.e. that the paths are limited in visibility, to the app container

Modified not just service show, but also create-custom.
:warning: Did not change create, as catalog services are getting removed.

Ok. Easy change.

Tweaked, commit 65e33e37e0d7074ff8324733207e4b03757f7416


Add support for Intercom('trackEvent')

Continuing the work of @andreicek, this PR adds support for event tracking.
While implementing a user on-boarding, I was faced with issues using url-based condition. Events works better in most cases in single page apps.
FYI: currently, Intercom('update') is called on every page transition but I was informed by Intercom support that there is a SPA limit of 10 calls per 30 minutes. As a consequence, "last viewed" does not always reflect the last page the user was on. Hence, using events has been reliable for me.

@olivierobert LGTM! Thanks a lot! I did not realize that was the case with the Intercom('update') call. Good to know!


A Typo in README file: Audit/Complaince logging:

Under the section "Features provided by Security", there is a subtitle "Audit/Complaince logging:". The word "Complaince" looks like a typo.

Thanks for your contribution!


Exit on startup: unable to force close channel

Background
Attempted to run "lncli feereport" on node yesterday and ran into an error where it said "rpc error: code = Unknown desc = no policy for outgoing channel x".  Could not find the channel in "lncli listchannels" but checking "lncli getchaninfo" I saw the channel with both policies as "null".   I then tried to force close and got the response "channel is already being closed".  Running "lncli pendingchannels" I saw the channel in waiting to be closed.
Thinking a reboot might help the situation, I restarted both lnd and bitcoind however upon restart, lnd starts up but then crashes with the error: "Unable to start server: -26: bad-txns-in-belowout, value in (x) < value out (x) (code 16)".
Every time I restart the node I get this same error now so can't even get into my node to try to replicate the original "lncli feereport" error.
Your environment
lnd: lnd version 0.7.0-beta commit=v0.7.0-beta-93-g377b7bf3ce493690fadc9d7be062062b006074c9
OS: Linux 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Bitcoind: Bitcoin Core Daemon version v<IP_ADDRESS>-gef70f9b52b851c7997a9f1a0834714e3eebc1fd8
Steps to reproduce
Starting LND (using supervisor - sudo supervisorctl start lnd)
Expected behaviour
LND should start normally
Actual behaviour
LND starts but shortly after I unlock it crashes, requiring unlock again.
Logs:
2019-09-06 15:24:23.858 [ERR] CNCT: ChannelArbitrator(x:1): unable to broadcast close tx: -26: bad-txns-in-belowout, value in (x) < value out (x) (code 16)
2019-09-06 15:24:23.858 [ERR] CNCT: ChannelArbitrator(x:1): unable to advance state: -26: bad-txns-in-belowout, value in (x) < value out (x) (code 16)
2019-09-06 15:24:23.863 [ERR] CNCT: ChannelArbitrator(x:0): unable to progress resolver: quitting
2019-09-06 15:24:23.866 [ERR] LTND: Unable to start server: -26: bad-txns-in-belowout, value in (x) < value out (x) (code 16)
2019-09-06 15:24:23.866 [INF] RPCS: Stopping RPC Server
2019-09-06 15:24:24.941 [INF] RPCS: password gRPC proxy started at <IP_ADDRESS>:8080
2019-09-06 15:24:24.941 [INF] RPCS: password RPC server listening on <IP_ADDRESS>:10009
2019-09-06 15:25:50.431 [INF] LTND: Received terminated
2019-09-06 15:25:50.432 [ERR] LTND: Unable to set up wallet password listeners: shutting down

Looks similar to https://github.com/lightningnetwork/lnd/issues/1267 (a very old issue). How long has this node been in operation?
If you apply this patch, then you'll be able to start up again:
diff --git a/contractcourt/channel_arbitrator.go b/contractcourt/channel_arbitrator.go
index b90707686..030eccb43 100644
--- a/contractcourt/channel_arbitrator.go
+++ b/contractcourt/channel_arbitrator.go
@@ -403,7 +403,7 @@ func (c *ChannelArbitrator) Start() error {

 		default:
 			c.cfg.BlockEpochs.Cancel()
-			return err
+			//return err
 		}
 	}

Looks like the you don't have any coins in the channel, so you can use the abandonchannel command to forget the channel.
Also while you're at it, I'd recommend updating to v0.7.1-beta since you're on a dirty (has commits mid-way between two versions)v0.7.0 branch that likely contains some behavior that was fixed during the rc cycle.

Thanks roasbeef - will try to add the patch this morning and see if I can get back up and running and will then attempt to use abandonchannel.  Node has been operation for about 7 months.
Will update once I'm able to test.

Still appear to be having the same issue after updating to 0.7.1 and applying the patch (commented out return err from contract court).  Still crashing on startup after unlocking node.
Debug error logs as follows (let me know if it would be helpful to see the full log of startup):
2019-09-06 15:24:23.858 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to broadcast close tx: -26: bad-txns-in-belowout, value in (0.00057) <                           value out (0.14996174) (code 16)
2019-09-06 15:24:23.858 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to advance state: -26: bad-txns-in-belowout, value in (0.00057) < valu                          e out (0.14996174) (code 16)
2019-09-06 15:24:23.863 [ERR] CNCT: ChannelArbitrator(8f40b5ad71c48dc1f7ebdf255089764ed2251c3fee044985b2e90a960c57fc8b:0): unable to progress resolver: quitting
2019-09-06 15:24:23.866 [ERR] LTND: Unable to start server: -26: bad-txns-in-belowout, value in (0.00057) < value out (0.14996174) (code 16)
2019-09-06 15:25:50.432 [ERR] LTND: Unable to set up wallet password listeners: shutting down
2019-09-09 14:06:28.682 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to broadcast close tx: -26: bad-txns-in-belowout, value in (0.00057) <                           value out (0.14996174) (code 16)
2019-09-09 14:06:28.682 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to advance state: -26: bad-txns-in-belowout, value in (0.00057) < valu                          e out (0.14996174) (code 16)
2019-09-09 14:06:28.688 [ERR] CNCT: ChannelArbitrator(8f40b5ad71c48dc1f7ebdf255089764ed2251c3fee044985b2e90a960c57fc8b:0): unable to progress resolver: quitting
2019-09-09 14:06:28.692 [ERR] CNCT: ChannelArbitrator(b3bcec82c25b63db9eb45cabc4c9577553e31e9f011cc3393d27267d6980dc93:1): unable to progress resolver: quitting
2019-09-09 14:06:28.692 [ERR] LTND: Unable to start server: -26: bad-txns-in-belowout, value in (0.00057) < value out (0.14996174) (code 16)
2019-09-09 14:56:14.692 [ERR] LTND: Unable to set up wallet password listeners: shutting down
2019-09-09 19:36:55.495 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to broadcast close tx: -26: bad-txns-in-belowout, value in (0.00057) <                           value out (0.14996174) (code 16)
2019-09-09 19:36:55.495 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to advance state: -26: bad-txns-in-belowout, value in (0.00057) < valu                          e out (0.14996174) (code 16)
2019-09-09 19:36:55.501 [ERR] CNCT: ChannelArbitrator(8f40b5ad71c48dc1f7ebdf255089764ed2251c3fee044985b2e90a960c57fc8b:0): unable to progress resolver: quitting
2019-09-09 19:36:55.502 [ERR] LTND: Unable to start server: -26: bad-txns-in-belowout, value in (0.00057) < value out (0.14996174) (code 16)
2019-09-09 19:38:32.874 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to broadcast close tx: -26: bad-txns-in-belowout, value in (0.00057) <                           value out (0.14996174) (code 16)
2019-09-09 19:38:32.874 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to advance state: -26: bad-txns-in-belowout, value in (0.00057) < valu                          e out (0.14996174) (code 16)
2019-09-09 19:38:32.882 [ERR] LTND: Unable to start server: -26: bad-txns-in-belowout, value in (0.00057) < value out (0.14996174) (code 16)
2019-09-09 19:39:31.820 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to broadcast close tx: -26: bad-txns-in-belowout, value in (0.00057) <                           value out (0.14996174) (code 16)
2019-09-09 19:39:31.820 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to advance state: -26: bad-txns-in-belowout, value in (0.00057) < valu                          e out (0.14996174) (code 16)
2019-09-09 19:39:31.832 [ERR] CNCT: ChannelArbitrator(b3bcec82c25b63db9eb45cabc4c9577553e31e9f011cc3393d27267d6980dc93:1): unable to progress resolver: quitting
2019-09-09 19:39:31.833 [ERR] CNCT: ChannelArbitrator(8f40b5ad71c48dc1f7ebdf255089764ed2251c3fee044985b2e90a960c57fc8b:0): unable to progress resolver: quitting
2019-09-09 19:39:31.836 [ERR] LTND: Unable to start server: -26: bad-txns-in-belowout, value in (0.00057) < value out (0.14996174) (code 16)
2019-09-09 19:50:14.771 [ERR] LTND: Unable to set up wallet password listeners: shutting down
2019-09-09 20:13:53.479 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to broadcast close tx: -26: bad-txns-in-belowout, value in (0.00057) <                           value out (0.14996174) (code 16)
2019-09-09 20:13:53.480 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to advance state: -26: bad-txns-in-belowout, value in (0.00057) < valu                          e out (0.14996174) (code 16)
2019-09-09 20:13:53.486 [ERR] LTND: Unable to start server: -26: bad-txns-in-belowout, value in (0.00057) < value out (0.14996174) (code 16)
2019-09-09 20:17:59.123 [ERR] LTND: Unable to set up wallet password listeners: shutting down
2019-09-09 20:18:43.200 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to broadcast close tx: -26: bad-txns-in-belowout, value in (0.00057) <                           value out (0.14996174) (code 16)
2019-09-09 20:18:43.200 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to advance state: -26: bad-txns-in-belowout, value in (0.00057) < valu                          e out (0.14996174) (code 16)
2019-09-09 20:18:43.203 [ERR] CNCT: ChannelArbitrator(b3bcec82c25b63db9eb45cabc4c9577553e31e9f011cc3393d27267d6980dc93:1): unable to progress resolver: quitting
2019-09-09 20:18:43.207 [ERR] LTND: Unable to start server: -26: bad-txns-in-belowout, value in (0.00057) < value out (0.14996174) (code 16)

Actually here's the proper patch to be able to restart:
diff --git a/contractcourt/chain_arbitrator.go b/contractcourt/chain_arbitrator.go
index b3cd497d2..f57ee63ad 100644
--- a/contractcourt/chain_arbitrator.go
+++ b/contractcourt/chain_arbitrator.go
@@ -511,7 +511,7 @@ func (c *ChainArbitrator) Start() error {
 	// can carry out their duties.
 	for _, arbitrator := range c.activeChannels {
 		if err := arbitrator.Start(); err != nil {
-			c.Stop()
+			//c.Stop()
 			return err
 		}
 	}

Worked further with roasbeef to get the issue of node-startup solved with the patch included at the bottom.
As a next step, used abandon channel to attempt to get rid of the zombie channel, which returned without error however still encountering the same errors when running lncli feereport ([lncli] rpc error: code = Unknown desc = no policy for outgoing channel<PHONE_NUMBER>19424769).
Appears to be related to issue #2911
Patch used to get node to start-up successfully:

As a next step, used abandon channel to attempt to get rid of the zombie channel, which returned without error however still encountering the same errors when running lncli feereport ([lncli] rpc error: code = Unknown desc = no policy for outgoing channel<PHONE_NUMBER>19424769).

That seems to be an issue with the abandonchannel command itself. Could you open another issue for that instead?


Disentangling TextEditor dependencies and reviving the use of the constructor

@joshaber and I were talking this morning about how unfortunate it is to require TextEditor instances to be constructed via the atom.workspace.buildTextEditor factory method instead of just via a normal constructor.
In https://github.com/atom/atom/pull/8968, we disentangled all the global references and moved to straight dependency injection. Because TextEditor had many dependencies, at that time we decided to deprecate the TextEditor export in the module returned by require('atom') and encourage people to use the factory so that these dependencies could be injected by the method without references to globals.
Now we're realizing that was probably a mistake. If you look at the dependencies of TextEditor, all but clipboard can actually be eliminated via various approaches. Some of them absolutely should be eliminated, because we're using them to subscribe to global events such as atom.grammars.onDidAddGrammar. This creates a requirement that package authors call destroy on TextEditor instances they construct or otherwise they leak editor instances because these subscriptions are never disposed. Other dependencies can be eliminated in various ways but aren't actually causing leaks.
Let's go through injected dependencies one at a time:

[x] notificationManager This is for notifying the user of the cursor scope. We can add a getCursorScope method and implement this elsewhere as well.
[x] packageManager This is just to emit grammar loaded hooks. Again, seems like we could emit events on individual editors and do this elsewhere.
[x] viewRegistry We won't need this at all if people implement getElement.
[x] project We set the project's path when the file is saved for the first time. Doesn't need to happen inside editor.
[x] assert A method for sending stack traces of unexpected states to the exception tracker. We don't necessarily need this everywhere and could even maybe look the other way using a global.
[x] applicationDelegate This is used to open prompts about file size. Could be moved and hopefully someday won't matter.
[ ] grammarRegistry Again, when grammars are loaded, match them against editors from the outside.
[ ] config Everything this controls can be managed from the outside (the workspace) and set options on the TextEditor directly. The only downside is that it would make it harder for package authors to match the settings of editors in panes.
[ ] clipboard This one is needed or you can't copy and paste. But could we have a private global for it via the module system. Essentially a singleton you require?

Some of these cases are more clear than others. What's less clear for me is the config and grammar registry. What if the package author wants a grammar to be automatically assigned based on the editor's path? What if they want to follow along with the user's settings for editors in panes?
I don't have perfect answers to these questions yet. It could be that the newly proposed editor registration API could also hook up your editor with certain services such as automatic grammar assignment and tracking certain user settings. Bottom line is, unless we want to bet on every editor user to calling destroy when they're done with our instance at the risk of leaking editors, these dependencies have to go anyway.
Thoughts? Tweaks? /cc @atom/core @maxbrunsfeld @joshaber

TextEditor is also accessing some globals directly:

[ ] atom.textEditors
[ ] atom.workspace
[ ] atom.project

Not too surprisingly, pulling out config is a doozy.

It could be that the newly proposed editor registration API could also hook up your editor with certain services such as automatic grammar assignment and tracking certain user settings.

I like this direction generally 👍 Just observe the appropriate config path and set values on the editor.
I'm not sure this works when a value is dependent on a scope though. For example, Cursor grabs a config value scoped to the buffer position. I'm not sure how we'd switch that to the proposed model. But that said, I'm not terribly familiar with cursors or the config system. Thoughts?

I'm not sure this works when a value is dependent on a scope though.

It seems like we need to figure out what settings will apply to the entire file (ex: line length or soft wrap) and what are scoped by localized grammar (ex: nonWordCharacters). We'll have to come up with a way to pass across the entire set of scoped configuration values in the case of the localized grammar settings and update it when any of those settings change?

Yeah, at that point it sounds like we're just creating a more specific subset of Config. Which is maybe ok?


report.py + createPeriodicTrajectory() updates

Updates to report.py to autoscale linewidths and the legend size based on number of plot elements.
I added additional coordinates to createPeriodicTrajectory() based on my 3D tracking stuff. I also had to update the negatePattern algorithm so it was compatible with MocoPerodicityGoal::addNegatedStatePair.

This change is

Is this ready?

Almost ready, I'll ping you soon.

@chrisdembia Ready for review.


Again about DRY a query

Adding complexity: in a previous suggestion #670  Chris wrote as following:
results = Object.as(:object).query.proxy_as_optional(Object, :object).owners(:owner).pluck(:object, 'collect(owner)')
@objects, @owners = results.map { |row| row[0], row[1] }

But, how can I find all the objects with a (A OR B) relationship with another?
Example: only Groups when a User (Owns or Participates)?

I'd need to know your domain to answer that. Figure it out in Cypher first, then translate it to Ruby.
BTW, you're not using Object as a node model, are you? If so, you shouldn't, it's Ruby's base object class.

No, I'm not using object, is just to show that it is not a specific object.
In my mind, it doesn't depends on the domain, but is a general approach, easy to reproduce using cypher (it runs ...., but cannot imagine how to turn the OR (or AND or XOR ...) in neo4jrb):
match (n)-[r:owns|likes]->(m)  return n,r,m;

of course, it could be    match (n:User)-[r:owns|likes]->(m)  return n,r,m;
or match (n)-[r:uses|shares|publish]->(m:domain_element)  return n,r,m;

When you reach the point that something can't be expressed with QueryProxy in Neo4j.rb, just call query and work in Core::Query. You'll have access to the full Cypher DSL, where you can express anything that you'd normally do with Cypher.

I'm starting to understand, but when I use x = ClassName.as(....) am I working with Core::Query or not?

 I'm in the middle of something right now but I've been meaning to write a blog post about this.
Short answer, though: QueryProxy has ActiveNode models and associations as its focus; Core::Query is a Cypher DSL. QueryProxy is an abstraction of the Cypher DSL, it gives shortcuts for common tasks. There are two approaches because QueryProxy has more "magic." It is "easier" but also gives you less control.

OK, check this out! http://neo4jrb.io/blog/2015/02/08/query_or_query-proxy.html

I found this doc thru twitter, this morning .... just after my wake up ....
Good work. Thank you.
PDP


NTR: Fibroblast growth factor signalling pathway (and the positive regulation term)

Hi,
1- New term request: Fibroblast growth factor signalling pathway
2- New term request: Positive regulation of fibroblast growth factor signalling pathway
The request is supported by Fig. 3C, 4A, 6 in PMID: 16774925. SMOC2 positively regulates fibroblast growth factor (FGF2).
Child term (of term 1):
GO:0008543: Fibroblast growth factor receptor signalling pathway
The same paper shows that SMOC2 positively regulates VEGFA. There is already a term for that:
GO:1900748: Positive regulation of vascular endothelial growth factor signalling pathway
and also for the pathway:
GO:0038084: Vascular endothelial growth factor signalling pathway.
Thanks,
Mila
--

Hi @milarolo
We already have
GO:0008543   fibroblast growth factor receptor signaling pathway
GO:0040036 regulation of fibroblast growth factor receptor signaling pathway
and the positive and negative regulation terms.
We should add synonyms.
Thanks, Pascale

Thank you very much for your reply.
I saw those two terms and I was going to use them. But the  paper doesn't say if the fibroblast growth factor (bFGF) only binds to the FGF receptor or if it binds to other receptors as well.
Since GO has the GO:0038084: Vascular endothelial growth factor signalling pathway term, I thought it would be better to have a term without the "receptor" word in it.
Best,
Mila

Glancing at the paper I don't see any assay for a specific signaling pathway - Fig. 3C looks at cell proliferation

Fig 4A looks at cell migration
Fig 6 looks at angiogenesis

If you use Noctua to annotate you can annotate SMOC2 to 'acts upstream of' these 3 processes.
The paper does not seem to support any stronger statement about SMOC2's specific role in the signaling process or its regulation.
@vanaukenk Do you agree?
Thanks, Pascale

Thank you for your comments.
I agree that there are no experiments for specific signalling pathways. However VEGFA and FGF2 are growth factors that are part of signalling pathways involved in vascular development and new blood vessel formation.  The assays in those figures show a clear positive regulation of VEGFA and FGF2 by SMOC2 when they are looking at their effects in cell proliferation, cell migration (which are main events that happen during the process of angiogenesis) and angiogenesis.
Therefore we can infer that SMOC2 positively regulates VEGFA and FGF2 signalling pathways.
Mila

Either way, I don't think this is an ontology issue. We wouldn't want to make a new term for any pathway downstream of the ligand. The question that remains here is the annotation.

We have these two terms in the ontology, each with specific annotation comments:
GO:0048010 vascular endothelial growth factor receptor signaling pathway (49 experimental)
Definition
Any series of molecular signals initiated by the binding of an extracellular ligand to a vascular endothelial growth factor receptor (VEGFR) located on the surface of the receiving cell, and ending with regulation of a downstream cellular process, e.g. transcription. Source: GOC:ceb, PR:000001971, GOC:signaling
Comment
In GO, a gene product with 'vascular endothelial growth factor-activated receptor activity ; GO:0005021' necessarily binds VEGF to transduce a signal. In contrast, the VEGFR refers to PR:000001971. To represent cross-talk between ligands and receptors, signaling pathways in GO are starting to be named after the receptor and/or the signal. GO:0048010 is for annotation of any pathway in which a ligand (VEGF or an alternative growth factor) binds and activates a VEGFR (PR:000001971). For annotation of signaling pathways where a VEGF binds to a cell surface receptor (VEGFR, PDGFR etc.), consider 'vascular endothelial growth factor signaling pathway ; GO:0038084'.
GO:0038084 vascular endothelial growth factor signaling pathway (8 experimental annotations)
Definition
A series of molecular signals initiated by the binding of a vascular endothelial growth factor (VEGF) to a receptor on the surface of the target cell, and ending with regulation of a downstream cellular process, e.g. transcription. Source: PMID:17470632, PR:000017284, PR:000017285, PR:000003096, PR:000007520, GOC:signaling
Comment
In GO, a gene product with 'vascular endothelial growth factor-activated receptor activity ; GO:0005021' necessarily binds VEGF to transduce a signal. To represent cross-talk between ligands and receptors, signaling pathways in GO are starting to be named after the receptor and/or the signal. GO:0038084 is for annotation of any pathway in which the ligand VEGF binds and activates any cell surface receptor (VEGFR, PDGFR etc.). For annotation of signaling pathways where a VEGFR binds one of its physiological ligands (VEGF or an alternative growth factor), consider 'vascular endothelial growth factor receptor signaling pathway ; GO:0048010'.
The latter term really does seem to be from the point of view of a VEGF ligand, while the former from the point of view of a specific receptor.
We don't mirror this representation with the EGF receptor signaling pathway (or, for example, the TGFbeta receptor signaling pathway), so I can see why it might be confusing.
I think we've also been grappling with this issue a bit wrt the Wnt signaling pathway and norrin signaling, see #7836
Should we propose to obsolete GO:0038084 and then possibly also revise the definition of GO:0048010?

Hi @vanaukenk @milarolo
A few more thoughts about this:

For this specific case though, I agree that obsoleting GO:0038084 seems appropriate, since the paper used to support that term is really looking at PDGFR signaling (GO:0048008).
As one of our ontology principles, we should avoid creating similar terms that can lead to inconsistent annotations.
As I mentioned earlier, with respect to the paper that @milarolo wants to annotate, no specific pathway is investigated, only downstream effects.
Generally I don't think we are ready to have a strict rule to make terms only describing ligands or receptors; @ukemi had a useful functional definition, ie which are the downstream causal targets; see also the ERBB ticket #15661: the activation of multiple receptors by each ligand seemed to make it more logical to use the ligand rather than the receptor (it may be possible to work on that branch and define specific pathways better). We have a number of ligands in the ontology (cytokines, for example), we should check if it's possible to move these to their respective receptors but that's a big project.

What do you think ?
Pascale

See some notes about this here:
http://wiki.geneontology.org/index.php/Non_1:1_receptor:ligand_binding

I think the problem that the multiple ligands bind 1 receptor and 1 ligand bind multiple receptors is a big issue.
Off the top of my head I do not know if this is always via  ligand families binding receptor families, or if a ligand can bind unrelated receptors and if a receptor can bind unrelated ligands. But considering family groups and then using AE/Noctua might be the easiest way forwards.
Ruth

My bystander impression is that the phenomenon of multiple ligands able to interact with multiple receptors is specific to the FGFR receptor family and its FGF ligand family. However, Mohammed Moosa at NYU is an authority on this - he worked out the structural biology for FGFs and FGFRs, and is probably knowledgeable about this is general, so you might be able to get a sense of whether this is a one time problem for FGF(R) or a more general one<EMAIL_ADDRESS>

I think the interleukins have this problem too. eg statement in abstract: https://www.ncbi.nlm.nih.gov/pubmed/29736903 IL-4 exerts its activities by interacting with two specific cell surface receptors: one designated the type 1 IL-4 receptor (IL-4R); the other designated the type 2 IL-4R, a receptor complex that is also the functional receptor for IL-13.
And Fig 1 in https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5897441/ which confirms 3 ligands for IL-20R type I receptor and 2 ligands for IL-20R type II receptor. I think Alex Diehl might be able to offer some advice too.
@addiehl

Please do not obsolete GO:0038084 vascular endothelial growth factor signaling pathway
There are 98 EXP annotations associated with the term (if you include the regulation child terms) weirdly this term also has the 5021 child term see attached screen shot, and 38190 child confirms why VEGF signaling is not a child of VEGFR signaling.

Isn't this a case where the term 'receptor transactivation' could be used ?

Hi,
Is there any update on this issue?
Thanks,
Mila

It appears to me to still be in flux; I will not create the terms unless there is agreement

Any decision taken on this issue?

So the original post is deemed an annotation issue still?

will make synonym and add comment for usage.

Action, make synonym and add comment (then this can close?)


proxy_set_header is under-documented: need to improve the proxy_set_header documentation to make sure nginx discards the web client's header value & sets the new specified value

Environment
Documentation issue. The current English version of the page http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_set_header is incomplete.

nginx -V

All/any.

uname -a

All/any.
Description
Nginx is under-documented.
Does nginx's proxy_set_header delete the header value coming from web client when modifying the header value to proxy_set_header's second argument (i.e. to the argument value at "Syntax" line at http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_set_header )? This is not specified by nginx documentation.
Actual: no docs of how to make sure nginx strips the web client request header value.
Expected: documented way to specify that non-empty value must override the header value & discard the web client's header value.
For the use case where it's needed, see

https://docs.djangoproject.com/en/5.1/ref/settings/#std-setting-SECURE_PROXY_SSL_HEADER and
https://docs.djangoproject.com/en/5.1/ref/settings/#secure-ssl-redirect .

[v] The bug is reproducible with the latest version of nginx documentation;
[v] The nginx configuration is minimized to the smallest possible to reproduce the issue and doesn't contain third-party modules.

nginx configuration
server {
    # ...
    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    # ...
    location / {
       uwsgi_pass unix:///var/www/logs-srv/logs-srv.sock;
       # ...
       proxy_set_header X-Forwarded-Proto $scheme;
   }
}

nginx debug log
N/A

"Allows redefining or appending fields to the request header to the proxied server" from the first sentence of the documentation aside, proxy_* directives don't do anything when using uwsgi. Maybe try uwsgi_param instead?

How to make sure that uwsgi_param's value is not appended to the list of request header value? Or uwsgi_param doesn't deal with http[s] request headers? Where is that specified in docs?

Closing as Invalid. Need to read the full nginx docs, particularly on uwsgi module.


A bit more efficient get_bit_equality_checkers

Likely tests will fail because it uses little-endian order, but Richa confirmed that it is the correct way to traverse bits

Incorporated! Thanks as always!!


Add a course plugin

Feature Request
We would like to be able to publish a course glimpse for any course on any page of the CMS.
Describe the solution you'd like
Add a course plugin similar to the existing Person and Organization plugins.
Use the existing course glimpse fragment to display the course glimpse.

I'll start working on this.

There now is a pr #406 for this.


Editing a task recording

Editing a task recording currently is flaky. If you insert a step in an existing recording, Task Recorder moves it to the last position when the test runs. Looking in the CS file shows that the ID for the new step makes it the last thing the recording does.

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

ID: da49381d-db38-c6fc-ab3e-0e88a73f9d41
Version Independent ID: ace8a33d-498d-9f39-9520-e0d5b93e0a06
Content: Set up and install Regression suite automation tool tutorial - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/fin-ops-core/fin-ops/get-started/hol-set-up-regression-suite-automation-tool.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @kfend
Microsoft Alias: kfend

@kristyler, thanks for posting here!
@kfend, please assign to the appropriate PM to resolve.

Bug 390234 has been logged to track this issue.

Created BUG 437655.

Improvements for the editing experience are planned. We'll consider this with those improvements.

@jasongre Consider? Do you realize how many hours of extra work it is to rerecord tasks, because I can't reliably insert steps after a code release? Editing a task is currently useless, because I can't trust it to work every time. I hope you're taking this product seriously. As it is, I'm looking at moving to a different test platform to save time.

@kristyler My apologies that you are having difficulties with task recorder. Have you engaged with customer support yet? That would always be the recommended route for reporting product bugs, especially for anything that is causing major pain.

This site is where reporting a bug sent me.
<EMAIL_ADDRESS>Kris Tyler
Data Analyst
2321 N Loop Dr, Ste 220
,
Ames
,
IA
,
50010
O:<PHONE_NUMBER>tel:(515) 817-2143
LandusCooperative.comhttp://www.landuscooperative.com/
|
Kris.Tyler<EMAIL_ADDRESS>This email is intended for the use of the person to whom it is addressed and may contain information that is privileged and confidential, the disclosure of which is governed by applicable law. Dissemination, distribution or copying of this information in an unauthorized manner is strictly prohibited. Sender accepts no liability for any damage caused by any virus transmitted by this email. If you receive this email in error, please notify the sender.
From: Jason Green<EMAIL_ADDRESS>Sent: Tuesday, April 14, 2020 1:31 PM
To: MicrosoftDocs/dynamics-365-unified-operations-public<EMAIL_ADDRESS>Cc: Kris Tyler<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/dynamics-365-unified-operations-public] Editing a task recording (#1790)
@kristylerhttps://urldefense.com/v3/__https:/github.com/kristyler__;!!BhvNS3mVlSFCQQ!4ArP5es11j0bKUD6AyvLdSXliwb6D5cwoGNsmW8lo2rHfhhwdvfPuXSFL6guyn19b8tcuA7F2g$ My apologies that you are having difficulties with task recorder. Have you engaged with customer support yet? That would always be the recommended route for reporting product bugs, especially for anything that is causing major pain.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/MicrosoftDocs/dynamics-365-unified-operations-public/issues/1790*issuecomment-613608032__;Iw!!BhvNS3mVlSFCQQ!4ArP5es11j0bKUD6AyvLdSXliwb6D5cwoGNsmW8lo2rHfhhwdvfPuXSFL6guyn19b8srkun6hA$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ANUILPIUAHMFTOWJSUPRNP3RMSTW3ANCNFSM4JGYZX4A__;!!BhvNS3mVlSFCQQ!4ArP5es11j0bKUD6AyvLdSXliwb6D5cwoGNsmW8lo2rHfhhwdvfPuXSFL6guyn19b8uuYZwCmw$.

@kristyler You can report support issues for LCS or Finance and Operations apps as noted here: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/lcs-support


Added AU10009 - No Internet Access

Uses the Test-Connection cmdlet to test if Google's DNS server may be
reached at <IP_ADDRESS>. Returns a moderate warning if it can.
Closes #180

@hpaul-osi again, let me know if you think there should be a link in the help text for this one.


Implement version aware code deployment

Closes https://github.com/opentargets/issues/issues/2946.

Updated make build to upload code to a version specific path
Updated workflow_template.py to run the code from that version specific path
Replaced hardcoded parameters in workflow_template.py with customisable ones
Amended developer documentation to make it clear how versioning works

Reorganised workflow_template.py to make argparse and pytest work together and amended some small things. The tests are now passing, and the manual test run of the code was successful. Ready for review.


Bug/formatRelativeDateTime

I'm now using this util function in a new context where both dates back in time and dates in the future is relevant. It looks like the util is made only to work for dates back in time. Anyway, it ended up resolving any future date as "Yesterday".
The unit tests are also improved now to make sure the format function is robust and user friendly.

The requests go through now, just started working on a branch where i will fix a problem with the format of the slack message, and fix the test/coverage stuff.
So after that i guess its ready :P

Ok, then I think you can use 3.9.4 to get the fix released now @jelsabird  😄


Feature - move Table Storage to nested module

Closes #72

Hmm, no that suggestion of 'just' renaming doesn't seem to work if you want to import it without the nested name.

What would be required is to rename this entire module to become Arcus.Scripting.Storage.Table.
(Nothing should be left behind with the name Arcus.Scripting.Storage)
Later on, we'll create a separate module, which will act as a "parent"-module (see #67), in which we will only add a psd1-file setting the NestedModules-property to import all storage-related modules, being Arcus.Scripting.Storage.Table and for instance Arcus.Scripting.Storage.Blob (once it would be created).


[Question] Development of this project

Hey @neozhu @Bram1903
Just a question if you have the time and if this is okay to answer publicly. I'm still using your project and I'm eager to learn more about it. Diving myself into technologies and everything. Is there anything you can/want to share about the development of this project. Like what kind of problems you faced, important decisions you made up front (if you can still remember) or during the project.
I'm so happy that this project exists, it really helps me. Going to check out all that has changed in the past months and can't wait for the .NET 8 Relase <3
Greetings,
Jochem
Also; I know you guys already don't have much time, so if there is no time for this, just close it!

Hi Jochem,
First off, thank you so much for your continued interest and support in our project. It's always encouraging to hear about the positive impact it has on our users.
Currently, the main challenge we're facing with the project, despite upgrading to .NET 8, is the inability to implement component-level mixed rendering modes due to the project's structure. At this stage, this presents an unsolvable issue, so we are supporting server-side rendering modes.
I have already developed several projects using this template. My aim is to continually refine and enhance the template through more practical projects. I'm always open to incorporating new ideas that reduce repetitive coding and add commonly used functionalities. My goal is to make future projects simpler and more efficient.
If you have any ideas or suggestions that you believe could contribute to this goal, I'd be more than happy to consider them for inclusion in the template.
Thanks again for your enthusiasm and support!

Hey @neozhu thank you for your quick reply! With "component-level mixed rendering modes" do you mean you want to combine blazor server and blazor wasm? or more like blazor/react/angular?
I love the aim for it and I have the same idea with this template within the company I work for. I love the goal to make it less repetitive. (I love to offer PR's in the future, if I continue this job) but first I want to fully understand the template and learn to submit quality code. When I get new ideas I will keep you posted! I love already how good the excel and pdf feautures are! How you have worked on the code generator tool & so much more!
<3


v1alpha2: update flag kubeconfig

fix #522

This change is

lgtm
Please sign the CLA

I signed it!

The test fails, thus please wait #527 merged

SGTM
On Wed, Apr 11, 2018 at 4:23 PM Ce Gao<EMAIL_ADDRESS>wrote:

@ddysher https://github.com/ddysher v1alpha2 is not ready for presubmit
test now. Thus we merge it manually. We will add e2e test in master after
v1alpha2 is merged.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubeflow/tf-operator/pull/525#issuecomment-380369624,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACFwAeT9YJjpP51Y5UaqXpalcSRflaVEks5tnb1-gaJpZM4TPVmd
.


Implement OIDC_AUTO_REGISTER setting

Overview
This PR adds a setting for OIDC_AUTO_REGISTER. This behaves similar to the other third party authentication setting XXXX_AUTO_REGISTER.
Behavior
Defaults to true
When set to true everything behaves as it currently does. If an account does not exist for an OIDC login, then it will be automatically created for them. If it does exist then the user can log in.
When set to false, Oidc logins will fail if a user was not created beforehand. Failure message is set to auth.failed. In order to log in you must first create an account with another admin account and manually input the External Authentication ID.
Why this would be helpful
I work for a university, and our department would like to implement bookstack while using our university's authentication services to handle logins.
Problem is anyone affiliated with the university has a login, but I only want people from my department to have access to our bookstacks instance. Everyone at this university knows their own External Authentication ID so it makes it easy for us to create the accounts manually and control who has access.

Thanks for offering this @AMDHome, but I really try to avoid adding new options unless very much proven to be required, especially where added to meet business/process logic rather than to meet the spec when it comes to auth. This would ideally be done via an issue thread to gain feedback and allow opportunity to think about alternative options.
Could you create an issue instead to start this off? You could still link to this PR as a potential implementation example, even if closed.

Closing in favour of alternative solution discussed in #4833


TB-2: add telegram bot to the project

Create stub telegram-bot for the project.
Acceptance criteria:

stub answer via telegram-bot added to the project

added in #17 pull-request


flowdec installation downloads tensorflow when tensorflow-gpu already installed

Hi!
When running the e.elegans example flowdec was running on CPU, not GPU. Also noticed that when flowdec was installed it installed tensorflow and not tensorflow-gpu.
If tensorflow was uninstalled would flowdec use tensorflow-gpu and sort itself out?
Cheers

Try installing flowdec with the TF_GPU environment variable set to true.
It might be better to just document the tensorflow requirement and not try to automatically install tensorflow or tensorflow-gpu automatically.

For posterity here, the TF dependency was split out as an extra to be installed on request based on user preferences (see instructions in README) per fix from @russellb in https://github.com/hammerlab/flowdec/pull/11


Point in time recovery

This PR introduces a new command:
turso db restore $DATABASE --timestamp 2023-09-25T14:53:00 --yes

Which is going to trigger database point-in-time recovery procedure. It's going to call turso API: /v1/databases/:database/restore.

After yesterday's talks and discussion with @athoscouto it looks like it will be more reasonable to change that feature into optional param as part of turso db create {forked-db-name} --from-db {parent-db-name} --timestamp {timestamp}.


Warp support for terminal finder

Description
Hey, I've added warp support for the terminalfinder extension and tied it up by adding a terminal app selection via preferences rather than having multiple commands for each one.
Screencast
https://user-images.githubusercontent.com/82511759/209607274-aaa6472f-e926-4ee1-8fc1-b5cf20d2f410.mov
(macOS terminal and Iterm stayed the same)
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Ah, ok. Sorry, it was just a suggestion. Im happy as long as the Warp integration makes it into Raycast (no matter how)! :)
Greetings from Germany! :D

Could you add it as new commands to the existing one instead? Then I think we're good to go 😊

Let me know if you need any assistance

@pernielsentikaer
Thanks but I think that should be it. :)

Awesome! @yedongze can you have a look too?

Could you remove package-lock.json @dannyneup


Spanstore does not support store warnings

Requirement - what kind of business use case are you trying to solve?
The jaeger-ui can't fetch warnings from span to promote user something unnormal happens
Problem - what in Jaeger blocks you from solving the requirement?
the spanstore data model doesn't have warnings in its schema, so it ignore the warnings
dbmodel.Span doesn't match model.Span
Proposal - what do you suggest to solve the problem or improve the existing situation?
I am not sure whether my understanding is right about the warnings's purpose. so i think we should either remove the warnings field from model.Span or add a field to dbmodel.Span to support warning.

Hi there,
jaeger will store spans as is without altering them in anyway. Warnings only come into play during reads. Whenever a trace is fetched for reading, we sanitize and massage the trace and add warnings; this means we don't need to persist the warnings.
The reason why warnings are only added during reads is that during ingestion, we store spans as they arrive. We don't have the complete trace until read time, at which time we can apply our sanitizers to the entire trace, not just spans.

Thanks @black-adder , got it, very clear.
BTW, is there any way to tell the jaeger ui to render some span more clearly(the red color, for example) to catch attention when some warning(rpc call timeout, for example) or error happens? after all, there may be hundreds of spans in one trace show.

@yancl Jaeger shows red exclamation point next to the span that contains the error=true tag. If the span is not visible because the parent is collapsed, the exclamation sigh bubbles up to the closest visible parent.

If you would like a different visualization, please open a ticket in the jaeger-ui repo and make suggestions to start a discussion.

It looks great to me with the current visualization, thanks.


[flutter_adaptive_scaffold] - standardNavigationRail overrides selectedLabelTextStyle even if you define it in NavigationRailThemeData

Since standardNavigationRail injects a selectedLabelTextStyle:
 TextStyle selectedLabelTextStyle = const TextStyle(color: Colors.black),

NavigationRail widget will ignore the one that is defined in NavigationRailThemeData:
 final TextStyle selectedLabelTextStyle = widget.selectedLabelTextStyle ?? navigationRailTheme.selectedLabelTextStyle ?? defaults.selectedLabelTextStyle!;

Which will result in undesired results since I want to use the styles I have defined on my NavigationRailThemeData object.

Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({
    super.key,
  });

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'MyApp',
      themeMode: ThemeMode.dark,
      darkTheme: ThemeData(
        useMaterial3: true,
        navigationRailTheme: NavigationRailThemeData(
          indicatorColor: Colors.white,
          labelType: NavigationRailLabelType.all,
          useIndicator: true,
          selectedLabelTextStyle: const TextStyle(
            color: Colors.white,
          ),
          unselectedIconTheme: const IconThemeData(
            color: Colors.grey,
          ),
          unselectedLabelTextStyle: const TextStyle(
            color: Colors.grey,
          ),
        ),
      ),
      home: const HomePage(),
    );
  }
}

class HomePage extends StatefulWidget {
  const HomePage({
    Key? key,
  }) : super(key: key);

  @override
  State<HomePage> createState() => _HomePageState();
}

class _HomePageState extends State<HomePage> {
  int _index = 0;

  @override
  Widget build(BuildContext context) {
    return AdaptiveScaffold(
      appBar: AppBar(
        centerTitle: true,
        title: const Text('Welcome!'),
      ),
      smallBreakpoint: const WidthPlatformBreakpoint(
        end: 700,
      ),
      mediumBreakpoint: const WidthPlatformBreakpoint(
        begin: 700,
        end: 1000,
      ),
      largeBreakpoint: const WidthPlatformBreakpoint(
        begin: 1000,
      ),
      useDrawer: false,
      selectedIndex: _index,
      onSelectedIndexChange: (index) => setState(
        () => _index = index,
      ),
      destinations: const <NavigationDestination>[
        NavigationDestination(
          icon: Icon(
            MaterialSymbols.home,
          ),
          label: 'Home',
        ),
        NavigationDestination(
          icon: Icon(
            MaterialSymbols.stadia_controller,
          ),
          label: 'Games',
        ),
        NavigationDestination(
          icon: Icon(
            Icons.restaurant,
          ),
          label: 'Foods',
        ),
        NavigationDestination(
          icon: Icon(
            Icons.local_activity,
          ),
          label: 'Activities',
        ),
        NavigationDestination(
          icon: Icon(
            Icons.question_mark,
          ),
          label: 'Random',
        ),
      ],
      body: (_) => Container(
        color: Theme.of(context).colorScheme.background,
        child: Center(
          child: Text('$_index'),
        ),
      ),
      smallBody: (_) => Center(
        child: Text('$_index'),
      ),
    );
  }
}

flutter doctor
PS C:\Users\GilDurao\Documents\GitHub\app> flutter doctor -v
[√] Flutter (Channel stable, 3.7.0, on Microsoft Windows [Version 10.0.19044.2604], locale en-US)
    • Flutter version 3.7.0 on channel stable at C:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b06b8b2710 (3 weeks ago), 2023-01-23 16:55:55 -0800
    • Engine revision b24591ed32
    • Dart version 2.19.0
    • DevTools version 2.20.1

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\GilDurao\AppData\Local\Android\sdk
    • Platform android-33, build-tools 30.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.10.0)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.10.31321.278
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2021.2)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)

[√] VS Code (version 1.74.3)
    • VS Code at C:\Users\GilDurao\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.27.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19044.2604]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 109.0.5414.122
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 109.0.1518.70
    ! Device emulator-5562 is offline.

[√] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

I noticed that there is no default for unselectedLabelTextStyle. If the Flutter team agrees, I can open a small PR that removes the default selectedLabelTextStyle (should the Icon theme defaults also be removed?).

Thanks for the report. Seeing same behavior on latest stable and master versions.

 stable, master flutter doctor -v
[!] Flutter (Channel stable, 3.7.3, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.7.3 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision<PHONE_NUMBER> (4 days ago), 2023-02-08 15:46:04 -0800
    • Engine revision 248290d6d5
    • Dart version 2.19.2
    • DevTools version 2.20.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.8.0-13.0.pre.52, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 3.8.0-13.0.pre.52 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision cc473e4f19 (73 minutes ago), 2023-02-15 22:51:19 -0500
    • Engine revision 3fc40ca5be
    • Dart version 3.0.0 (build 3.0.0-241.0.dev)
    • DevTools version 2.21.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Maybe related: https://github.com/flutter/flutter/issues/114595

Maybe related: #114595

Yup, that's exactly it @darshankawar

@stuartmorgan @gspencergoog I believe this is already fixed. See https://github.com/flutter/packages/blob/main/packages/flutter_adaptive_scaffold/lib/src/adaptive_scaffold.dart#L513
The theme is passed through and parameters have been made nullable.

Closing as fixed.


Fix parse glob

Pull Request Test Coverage Report for Build 276

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.429%

Totals

Change from base Build 272:
0.0%

Covered Lines:
1034

Relevant Lines:
1095

💛  - Coveralls


Uncaught (in promise) Error: Missing PDF file.     at getDocumentError

Getting this error while loading local PDF file.
Getting above error while loading local PDF file.

please try to put it in scope. It works.


co-locate unit tests with their target source

Description

Move unit tests into __tests__ directory co-located adjacent to their target source files.
How Has This Been Tested?

Ran npm run test:unit in the frontend dir:

Test Impact

None.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@manaswinidas fixed the typo in the description for npm run test:unit and also mentioned it's for the frontend dir.


How do you trigger all the ecommerce calls?

https://github.com/segment-integrations/analytics.js-integration-google-analytics/blob/master/lib/index.js#L74-L85
The docs explain how to trigger add/remove product to cart and Completed Order events, but not all of the ones in this integration.

yes especially the Refunded Order, not mentioned at all except in passing

wish we could pull request the docs :D

Hi @kmiyashiro, as part of the monorepo migration, this issue has been moved to new issue. Our engineers have been notified and will prioritize and work on it ASAP. Thank you!
For more information, see README.md.


Django 1.9

Quick one, this fixes django-enumfield on Django 1.9, and includes it in the test suite.

Just realised there's no issues tab for this repo. I was going to open one about Python 3 support – can you either enable issues, or let me know what you think about introducing six as a dependency and supporting Python 3.4 and 3.5?

enabled issues
six dependency is absolutely fine by me.


Implement OneofObjectType for Vec

Description of the feature
Implementing OneofObjectType for Vec<T> would allow a user of the library to use a list of some input object type as an argument.
Code example (if possible)
use async_graphql::*;

#[derive(SimpleObject)]
pub struct User {
    name: String,
}

#[derive(OneofObject)]
pub enum UserBy {
    Email(String),
    RegistrationNumber(i64),
}

pub struct Query {}

#[Object]
impl Query {
    #[graphql(oneof)] // causes error
    async fn search_users(&self, by: Vec<UserBy>) -> Vec<User> {
        unimplemented!()
    }
}

directive @oneOf on INPUT_OBJECT

type User {
  name: String!
}

input UserBy @oneOf {
  email: String
  registrationNumber: Int
}

type Query {
  searchUsers(by: [UserBy!]!): [User!]!
}

Removing #[graphql(oneof)] from the code above actually compiles and throws an error when more than one field is defined on the UserBy input object at runtime. However, right now, removing this also means that the directive is not shown in the output GraphQL schema.

I added a test and everything seems to be working fine.
https://github.com/async-graphql/async-graphql/blob/336451f3bc5d422dc9c6ab9744c728984bedfbce/tests/oneof_object.rs#L268

Jup, that test should indeed work. I tried to describe this in the issue, but maybe I was not clear enough.
The issue is that the GraphQL schema now misses the declaration of the directive:
directive @oneOf on INPUT_OBJECT

As per https://github.com/async-graphql/async-graphql/issues/766#issuecomment-1059242265 we should include the #[graphql(oneof)] macro to include this.
If you include that macro above the line in the test here you should receive an error. https://github.com/async-graphql/async-graphql/blob/336451f3bc5d422dc9c6ab9744c728984bedfbce/tests/oneof_object.rs#L286

Hope this helps with understanding this issue a bit more ☺

I have removed the oneOf attribute, it is no longer needed and it looks like the generated SDL is correct now. 🙂
directive @oneOf on INPUT_OBJECT

type Query {
	searchUsers(by: [UserBy!]!): [String!]!
}

input UserBy @oneof {
	email: String
	registrationNumber: Int
}

schema {
	query: Query
}

The oneOf attribute is used to declare a oneOf field, but I have now removed this feature.