Touch and gaze events are now passed through the switch

Closes Github issue 339
Description of Work
Touch and gazeable events are now passed through the switch UI component.
Notes to Test (Optional)
This should be fixed in Selection Mode and Category Details.

Behavior as described in the bug ticket 339 remains the same


How to access Cloudflare Worker Bindings?

Hi @markusahlstrand,
I'm currently building an api and looking for a framework. tsoa + tsoa-hono looks awesome!
I just cannot figure out how to access Bindings for deploying to Cloudflare Workers... Is there an example on how to do this?
Specifically, I'd like to talk to a D1 database.
Thanks in advance!
Best
Hannes

Never mind, I figured it out by looking at the code of https://github.com/authhero/auth.
For anyone interested:

create a index.ts file wrapping app.fetch:

import { ExecutionContext } from "hono";
import { Env } from "./_helpers/Env";
import app from "./app";
import { PrismaClient } from "@prisma/client";
import { PrismaD1 } from "@prisma/adapter-d1";

const server = {
    async fetch(request: Request, env: Env, ctx: ExecutionContext) {
        const adapter = new PrismaD1(env.D1_MAIN);
        return app.fetch(
            request,
            {
                ...env,
                prisma: new PrismaClient({ adapter })
            },
            ctx,
        );
    },
};

export default server;

everything attached to the env here can be used by adding @Request() request: RequestWithContext as a parameter to your route handler. Now, you can use request.ctx.env.prisma.

@markusahlstrand I had to patch tsoa-hono since wrangler complained about now knowing about Buffer here:
[ERROR] ReferenceError: Buffer is not defined

nodejs_compat was enabled. Maybe you want to include this?
tsoa-hono-npm-1.2.1-04da50d363.patch

Hi! Yes, it's on my todo list to see if we somehow can remove that dependency..

Great to know, thanks! It works fine with the patch though, so no worries.


Axios breaks datatable filters

Description
The Axios update to v0.28.0 had some breaking changes in parameter serialization. Objects and Arrays are now provided in a bracket style instead of an object style:
New: &filter[status]=published
Old: &filter={"status":"published"}
This change leads to json_decode errors in src/Http/Controllers/Admin/ModuleController.php due to Twill expecting a json_decodeable string attached to the "filter" request parameter.
Object { message: "json_decode(): Argument #1 ($json) must be of type string, array given", exception: "TypeError", file: "./vendor/area17/twill/src/Http/Controllers/Admin/ModuleController.php", line: 2135}
Steps to reproduce

navigate to a Twill datatable in the backend
use a Quickfilter or Tablefilter
analyze the request

Expected result

filters work as expected and do not result in a 500 error

Actual result

filtering results in a 500 error

Versions
Twill 3.2.0

There is a possibility it's breaking more than this
I didn't dig into it but titles are saved like this


ES6 Intellisense in NIW

Thanks for working on ES6 syntax. This is a big help to adopting it more rapidly.
The ES6 Intellisense works nicely in the code editor but not in the NIW. The NIW highlights this line with several red squiggles.
var x = `The answer is ${3+2}`;

This statement runs in the NIW without any error but it will be confusing to many developers to get error highlights on valid ES6 code.

Thanks for the feedback!
@jramsay @paulvanbrenk @bowdenk7 - just a heads up that we should start thinking about what it would take to enable Salsa in the Interactive Window as well and also in the upcoming folder/file based project system stuff. One complexity with the Interactive Window is that it can be opened outside of a project context altogether.

Similar issue with code editor for the following line in App.jsx:
var {Routes, Route} = require('react-router');
'{' and '=' flagged as 'expected indentifier' and 'syntax error' respectively.

We're working on this now. Closing this issue in favor of #1090


stopped working completely, just me?

it gives me an unknown error then when i click it, it says channel deleted or temporary error.

i am talking about the scheduled downloads

I'm getting the error also, but it's only affecting new downloads. I have a stream that was already downloading and it's still working, but any new scheduled download or download initiated from the search get the error.

I've been experiencing the same phenomenon since about 3hours ago. Changing the settings and rebooting the computer won't solve it.

It's a change on Twitch's end that broke everything

This issue is highly related to this other issue
TL;DR: Twitch changed the way in which the playlist of the streams are obtained, making it more difficult to bypass ads and breaking every third party tool
https://github.com/streamlink/streamlink/issues/5370

Duplicate of #83


Feature Request: Comparing different Profiles

It would be great to have an possibility to compare differents profiles to see differences between the options.
And it would be nice if we can create a new "default" profile with all the default flags set.

You can already compare profiles using the "Highlight" functionality on the "Profiles and Rules" screen:

Does this do what you want? 😉

Hi bastianStr,
an alternative approach (fewer clicks, but much more technical) would be to use ABAP cleaner menu "Help / Open Profiles Folder", then open two of the profile e.g. in Notepad++ (those are JSON-like files with the extension .cfj), and use the Compare plug-in:

Probably you can guess at least in most cases which rules and options are meant :-)

And it would be nice if we can create a new "default" profile with all the default flags set.

If you go to the "Profiles and Rules" editor and in section "Profiles" click "Create", the newly created profile will start with the default settings regarding both rule activation and configuration (while with the button "Copy", they start with the settings of whatever profile that was selected when you hit "Copy").
Alternatively, at the bottom left of the window, you can press "Activate: Default" or "Activate: Essential" to activate the default / essential rules in the currently selected profile and deactivate all others (note that these buttons only change rule activation, but not rule configuration). When ABAP cleaner is installed, the "default" and "essential" profile only differ in rule activation, while the detailed configuration options are the same (but you can change these profiles as you like, of course).
Whatever you do after opening the window will be persisted when you leave the window with "Save Profiles and Exit", or discarded with "Cancel".
Not sure whether this answers your question or whether you meant it in a different way?
Kind regards,
Jörg-Michael


Make sure Chewy logger is initialised

Since the purpose of #543 was to reduce the strategy logging I thought this was the best solution imho without loosing the logging information and with my limited knowledge of the project.
If people with more experience of this project have better idea, I'm open for suggestions 😛
Possible fix for #552
cc: @pyromaniac, @Borzik

Oh crap, I didn't notice you did it. I've got a better solution thought anyway, take a look, please: #557


Playground: Can't cut text selection

Both Ctrl+C and right-click -> context menu -> "Cut" do not actually cut the text, nor is the text copied into clipboard

Expected behavior:
Selected text is removed and exists in clipboard
Actual behavior:
Nothing happens

Is this maybe OS specific? This seems to work fine on my machine

I'm using Firefox on Windows. Firefox on MacOS seems to behave correctly as well as Edge on Windows.


Fix broken HTTP/2 Streams link

Motivation:
The HTTP/2 Streams link is not available anymore, since it has moved to https://httpwg.org/specs/rfc7540.html#StreamsLayer
Modifications:
Fixed the link to point to the official Streams section in the RFC.

LGTM. Thanks!


Add comment about last_affected usage in evaluation pseudocode

Resolves partially #150
I thought this might be useful, but on the other hand I am not completely sure if this is really needed and it might just increase confusion.
So no worries if you reject this PR.

Hey, thanks for this PR! https://ossf.github.io/osv-schema/#examples might be a better place for this, and it's currently lacking some examples for last_affected.
CC @hayleycd who is helping us with this.

I agree with @oliverchang  that this is better resolved in an example, but I appreciate your interest in the issue.
I just opened #174 if you want to take a look.

Thanks for taking care of this and writing such an extensive example!


TODO: Rename all *.iy plugins to *.plugin.luau

[x] rename all plugins in the store to *.plugin.luau and
[x] tell is to save .luau plugins as .iy files

close this smh didnt u just do it!!!

https://github.com/Infinite-Store/Infinite-Store/commit/e6a168c1c67a692f5ae1433abff0995483ae0fe4

not fixed


short link for k8s cheat sheet

Close #23909

@sftim @kbhawkey the issue #23909 mentions not to use 301 since this is not a permanent redirect. So, I have used 302.  Please review. Thanks!

Hi @neha-viswanathan
https://k8s.io/docs/user-guide/kubectl-cheatsheet/ is a bit long for a short link. How about https://k8s.io/cheatsheet ?
Would you like advice on how to implement that?

@sftim Please correct me if I'm wrong- Thanks
/cheatsheet/     /docs/reference/kubectl/cheatsheet/ 302

/cheatsheet/ /docs/reference/kubectl/cheatsheet/ 302

I would also redirect:
/cheatsheet /docs/reference/kubectl/cheatsheet/ 302

/lgtm

/lgtm

Discussed in SIG Docs weekly meeting, good to go
/hold cancel

Discussed in SIG Docs weekly meeting, good to go
/hold cancel

discussed in Sig Docs meeting Jan 12th, no objections from the team
/approve

discussed in Sig Docs meeting Jan 12th, no objections from the team
/approve


Ticked version, regenerated if needed. (Double-check reqs!)

(Built using tick_my_feedstocks)

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


WP4 - DOD scoping

[ ]     subscriptions / recurring donations
[ ]      creating invoice objects so we collect / withold tax appropriately, selecting a tax code for the app using a lookup table based maybe on its category? Games vs Productivity vs Utility vs everything else?
[ ]      exposing functionality for verified developers to manage their own flat-manager tokens for direct uploads

This issue was created following a quick chat with @ramcq and can be use to scope the definition of done and the track our progress from a high level.
We can discuss this further and add more detail next week when @danielsilverstone-ct is back in the office

My proposal is roughly to re-purpose WP4 as "overflow" for wrapping up more complex parts of payment handling that we maybe didn't (all) understand the nuances/complexity of at the start of the project. I'm imagining WP3 as close to completion as an MVP for one-off payments/donations for apps using a direct "payment", and that the original scope of WP4 is otherwise quite straightforward - as the subset functionality already exists in Flatpak and @jameswestman is (I beleve) looking at adding it to flat-manager at the same time as the "token required" metadata.

WP3 is complete and WP4 is scoped somewhat more clearly in #256.


Export method not working on Page object ([__NSSingleObjectArrayI name]: unrecognized selector)

Summary
I'm trying to export a Page with the new API (Sketch 49). It works well when giving an artboard to the export method. But when giving a Page object it crash (the script, not the app).
http://developer.sketchapp.com/reference/api/#export
Steps to Reproduce:
Create a plugin to test with this script :
var sketch = require('sketch/dom');

export default function(context) {

    var document = sketch.Document.getSelectedDocument();

    //I know I have 2 Pages on my test document in Sketch
    log(document.pages);

    for (var i = 0; i < document.pages.length; i++) {
        var page = document.pages[i];

        log(page);
        log(page.name);

        sketch.export(page, {
            overwriting: true,
            output: "~/Desktop/test_output"
        });
    }
}

// Logs
//
// // Pages
// (
//     "<null>",
//     "<null>"
// )

// // Page [0]
// (null) // page
// screen_1 // page.name

// // sketch.export error
// -[__NSSingleObjectArrayI name]: unrecognized selector sent to instance 0x60800001a150

Expected Results
An image should be created representing the full page
Actual Results:
An error :
-[__NSSingleObjectArrayI name]: unrecognized selector sent to instance 0x60800001a150
Notes
It's weird, because when logging a page, null is printed, but page.name, print the name.

Good catch! It will be fixed in 49.1.

It's weird, because when logging a page, null is printed, but page.name, print the name.

Yeah I'm not sure why. I'm working on improving the logs in general, it will be a lot better really soon! In the meantime, you can use page.toJSON() and log this

(also, thanks for the nice bug report 💯 )


Vm cannot run programs with % in name

To reproduce reate bin/ab%22.dart with a small program, and run dart bin/ab%22.dart
prints:
Error: Error when reading 'bin/ab%22.dart': No such file or directory

The same happens for snapshots.
My motivation is that I would like to url-encode the sdk-version into the name of a snapshot(for pub run) to avoid running a bad snapshot.

My motivation is that I would like to url-encode the sdk-version into the name of a snapshot(for pub run) to avoid running a bad snapshot.

I feel strongly that we should not be trying to hack around a bug in the SDK, pub is not the only place we use this pattern and we should not go rewrite them all to encode the SDK version in a file name. Have we filed an issue for not getting the correct exception on a bad snapshot?

This still seems like a valid bug though right?

This still seems like a valid bug though right?

Yes.

My motivation is that I would like to url-encode the sdk-version into the name of a snapshot(for pub run) to avoid running a bad snapshot.

I feel strongly that we should not be trying to hack around a bug in the SDK, pub is not the only place we use this pattern and we should not go rewrite them all to encode the SDK version in a file name. Have we filed an issue for not getting the correct exception on a bad snapshot?

We should not work around a bug - true. But I find that encoding the sdk version in the filename actually it is nicer for pub run for the following reasons:

We are moving to using a subprocess instead of an isolate for pub run (https://github.com/dart-lang/pub/issues/2492). Meaning that there is no exception to catch, we would have to interpret stdout and exitcode, which we can never ensure are not overlapping with what the program itself would return. Alternatively the VM would have a mode that only detected validity of the snapshot. But then that would require one more subprocess call before starting the program.
We can have one snapshot per installed SDK without conflict - maybe not a common use-case, but when you are testing a program with different sdks it works nicely.

For other use-cases we do want the VM to throw a known exception on Isolate.spawnUri, and it would also be nice to have a way to test a snapshot's validity before running it.


Find a better way for apps to write links with the  tag

Right now we have Link, which is not terrible but is also not ideal.
Open to ideas/suggestions

Fixed with https://github.com/joeldenning/single-spa/commit/0d45803b215cb6f9820e53b458705065a62034e4#diff-b91812c2eab4fbf92962784c8ce887c0R375


Extensible dataset

Much of my work involves processing time samples, so I need to be able to save data with an unlimited axis. Do you have thoughts or suggestions on adding this capability to eigen3-hdf5? If I get something reasonable would you want a pull request or do you want to keep your code free of this additional complexity?

What do you mean by unlimited axis?  That the matrix (or vector) dimension will grow over time, and cannot be specified beforehand?

Yes; its maximum dimension will be unlimited. I believe the correct HDF5 term is extendible dataset. Creating an Extendible Dataset is the basic tutorial, which says

[An unlimited dimension dataspace is specified with the H5Screate_simple / h5screate_simple_f call, by passing in H5S_UNLIMITED as an element of the maxdims array.

What I need is a dataset where each row of data represents the set of measurements for a slice in time, where I do not know in advance how many rows I will need. So the first dimension will be unlimited. For example, a typical IMU measurement consists of 6 doubles. I would need to store each measurement as a row in a 7 column matrix [time, ax, ay, az, gx, gy, gz].

I think the most useful thing would be able to save an eigen matrix to some subportion of an hdf5 array on disk.  That way, you could store only the recent samples, adjust the size of the hdf5 array, and save the recent samples to disk.

But that is the point of an extendable HDF5 dataset--the library does all of this for you. For example, if I have a Vector3d that I want to write out as time marches on, then I have a dataset that is UNLIMITEDx3. I write a vector at a time. The library takes care of adjusting the actual size on disk. If you do this with fixed size datasets, then you have to overallocate and use a fill value, write each row, expand whenever you reach the current size, copy to a new dataset if you exceed the max size, and shrink to actual size when you are finished.
I will play with it and give you a pull request when I have something that works for me.

The key missing functionality, though, is the ability to save an eigen array to a sub-porton of a dataset.  With this, it would take just two calls to do what you are describing--one to extend the dataset, and the other to write the data.  Once these calls exist (and the second call likely already exists in the hdf5 library), it is easy to make a wrapper function that does both at once.


improve simultaneous play support

The current CB code checks that the initial state of a .gmv file matches the current state of the .gam into which it is being loaded, and presents CSelectStateDialog if the initial states don't match.  However, that isn't ideal for games where players naturally take actions in parallel, for example, the programming phase of Roborally.  In that case, either the players have to explicitly define a turn order, which slows down the game, or they have to effectively opt out of the error checking provided by the game state comparison (by using the "Use current game state" option of CSelectStateDialog).
It would be nice if we could find some middle ground so that games can proceed in parallel as much as possible while still performing error checking.  Unfortunately, I haven't thought of any straightforward way to achieve this yet.

Unfortunately, I haven't thought of any straightforward way to achieve this yet.

Yes, it can be tricky. It's not unlike source control with GIT. We need a merge operation that can handle collisions (two players moving the same piece in two different move files for instance.) Resolving the collision is where the difficulty arises.
The current approach either insists on game state perfection but allows the player to ignore state purity and apply the moves anyway. In essence, collisions are ignored--the last applied move file wins.
-Dale

Yes, it can be tricky. It's not unlike source control with GIT. We need a merge operation that can handle collisions (two players moving the same piece in two different move files for instance.) Resolving the collisions is where the difficulty arises.

Actually, that's a "simple" case; the system can (theoretically) see that the same piece has been moved to different places.  I have thought of at least one scenario that looks much worse to me:  Three pieces that overlap (i.e., are stacked), and one player moves the bottom piece to the top of the stack, while the other player moves the middle piece to the top of the stack.  The players have not touched the same piece, yet the end result is different.

The players have not touched the same piece, yet the end result is different.

That one didn't occur to me. Nasty!
-Dale


Upgrade to the latest sdk-gaitauth-v1.3.19

Update the project with latest sdk-gaitauth: sdk-gaitauth-v1.3.19

LGTM


[AutoPR mediaservices/resource-manager] [Hub Generated] Review request for Microsoft.Media to add version 2018-07-01

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5400

(message created by the CI based on PR content)


Poor error message on Dataset.sum(axis=...)

ll_means.nc.gz
MCVE Code Sample
I'm attaching the relevant .nc file.
foo = xr.open_dataset('ll_means.nc')
print(foo)
foo.sum(axis=1) # or foo.sum(axis=0)

Instead of getting a sum (either across the data variables or across the dimension shared between the variables), I get the error in the title: ValueError: cannot supply both 'axis' and 'dim' arguments even though I did not supply a dim argument.  Furthermore, I get this error even when passing dim=None.
It's possible that I am doing something wrong, and it is just the error message that is bad, and not the behavior. I don't know enough to tell.
Expected Output
TBQH, I didn't know whether this would sum across the (single) dimension of this dataset, or if it would sum across the data variables along that dimension.  I was experimenting to try to figure this out.
What I am trying to do is sum across the data variables, "perpendicular" to a dimension, instead of along it.
Problem Description
I assumed that summing across one of the axes would sum across the data variables, but perhaps that was a bad assumption. At any rate, the current behavior is undesirable.
 But the error is correct, I think. Why do you want to use axis rather than dim?

@max-sixty I was trying to sum across the data variables, rather than across a dimension.
What I ended up doing was taking the data for each of the data variables and adding the resulting numpy arrays. This gave me the sum across the data variables, along the dim (each data variable is one dimensional and they share a single dimension).
I'm not sure how to suggest fixing the error message, because I'm not sure what xarray doesn't like.

It's a case of improper error message.
I don't think anybody ever thought of passing  the axis parameter to any of the Dataset methods before. As a general rule, it would be a very unwise idea unless you're sure that all of your data_vars have the required dimension exactly in the same position.
Note the documentation for Dataset.sum vs. DataArray.sum:
http://xarray.pydata.org/en/stable/generated/xarray.Dataset.sum.html
http://xarray.pydata.org/en/stable/generated/xarray.DataArray.sum.html
You were able to pass the axis parameter because Dataset.sum accepts **kwargs, which are intended for backend-specific arguments (e.g. dask's split_every parameter).
The solution is to blacklist a bunch of numpy arguments that don't make sense (axis is one, but out also comes to mind).

@crusaderky I see what I did wrong. I mistakenly read the documentation page for DataArray.sum() instead of DataSet.sum().  The former does support an axis argument, and I believe it makes sense there.
Blacklisting these arguments sounds like a great idea, thanks.

@rpgoldman if you want to do an elementwise sum of the data_vars of a Dataset, it's as simple as sum(ds.data_vars.values()).
``sum() is not elementwise - it's a reduction along one or more axes - exactly like in numpy.

@crusaderky Thanks.  Yes, that was exactly what I was trying to do.

I think given we're not in full control of the sum function and it's relatively rare to pass axis, it's OK to close; is that OK?

I guess so.  Minor preference for checking for inappropriate numpy errors like this and giving a better error message, but I can see this would be difficult.
This won't be the first bewildering error message problem from **kwargs, and it won't be the last.  This is a python problem, not an xarray one, per se.

I think there's space here to make xarray more user friendly. A better error message would particularly be useful with new xarray users which are used to numpy and pandas - which is the most common new user profile TBH.

OK, good points


Other potential sources of test corpora

I tweeted about this and got a few tips that I might have to follow up if the current corpus is not sufficiently useful.

[ ] Meg Risdal from Kaggle might have some
[ ] I got a tip about Buggify (looks immature)
[ ] Apparently @Tobias-Kohn may have something
[ ] David Kramer says Sentry might have something (DM for access) (Also Data Dreadnought could help)

FWIW I am currently using a corpus made available by the authors of this paper.

Yes, I do have several thousand programs.  What exactly are you looking for: just the programs, or labelled data?
If a summary is helpful: I reported my findings concerning errors in a paper The Error Behind the Message, which is also available from my homepage.
Just as a disclaimer: the programs I have collected are all anonymised (before they were sent to me), i.e. the strings and comments basically comprise only xs, e.g., `s = "Xxxx x xx xxxx", and large numbers are scrambled.  Since I am interested in syntax errors and conceptual misunderstandings, this works just fine for me.  However, some of the runtime errors might be quite distorted.
We could also ask Philip Guo, who might have some data from his Python Tutor.

By the way: my Python-parser comes with a very small test suite, which contains some erroneous programs.  They are in a format where the first two lines contain the expected number of the erroneous line and the expected error message, followed by a small program.  Would that kind of format work for you?

Yes, that format works for me. It will encourage me to stop working with straight JSON and just load test cases into a sqlite3 database. :-) I notice that your "expected error message" field is some kind of enum. Do you have a way to map these to what CPython produces? (No worries if you don't.)


STRA: Security Review for Mat/Pat

Security/review/risk assessment of the maternity/parental leave Digital Journey is required for launch.
A/C
( )Meeting with PSA Security team to review the Digital Journey
( ) Sign-off/Approval my PSA Security team for inclusion in the PIA

@warrenchristian1telus Hello, I'll be setting up a session with the security team for their review of the maternity parental leave Digital Journey. It's likely they will ask about security vulnerabilities that may affect our ability/approval to launch. Let's connect about any high-level issues on the dashboard we can/could/should resolve before the review.

Hi @MeghanStothers - There is currently an update to the hamongo instance (forms-flow-db) that we should look into patching in all namespaces.

Thanks - I've set up a meeting with our security specialist to start the conversation about what we would need to address before launch (so we we can estimate and action, of course :)

Meeting with Igor, he said we are "golden" i.e no major issues found.
Next Action items -
Warren to see the "security dashboard" in openshift to see if there are any high priority security issues identified.
We need to meet with Igor again when were are closer to release and do a final review. We need the email sign off as approval to launch.

Security dashboard still looks good. Will verify again with Igor closer to release date.

@MeghanStothers  to meet Igor to review and look at it in relation with the PIA

@warrenchristian1telus Hi Warren, any security concerns on our dashboard that are blockers for our Dec 4 release to PSA (internal teams) as well as the TES payroll team?


More idomatic error handling

This PR introduces a couple of changes to make error handling more idiomatic to Finch:

FormErrors now extends Exception so we can wrap it with Output.failure
We now provide io.circe.Encoder[Exception] that uses Circe's generic derivation for FormParams and falls back to a simple Json.obj encoding.
All endpoints now return A, not A Xor FormErrors so we fold underlying Xors.
On a client we now handle both cases: success (HTTP 200) and error (anything else).

Thanks!


get_exchange does not pass 'password' to gdax

Dear Catalyst Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Operating System: MacOS High Sierra 10.13.3
Python Version: 2.7.13
Python Bitness: 64
How did you install Catalyst: conda
Python packages: $ pip freeze or $ conda list

Now that you know a little about me, let me tell you about the issue I am
having:
Cannot trade on gdax exchange because gdax requires a key, secret, AND passphrase but
get_exchange in exchange/utils/factory.py only passes in key and secret
from auth.json
def get_exchange(...

    exchange = CCXT(
        exchange_name=exchange_name,
        key=exchange_auth['key'],
        secret=exchange_auth['secret'],
        base_currency=base_currency,
    )

https://docs.gdax.com/#authentication

What did you expect to happen?
Be able to paper trade on gdax

What happened instead?
WARNING: CCXT: unable to fetch open orders gdax / eth_usd: gdax requires `password`
Here is how you can reproduce this issue on your machine:

Anything else?
...
Sincerely,
$ whoami

@AvishaiW or @lenak25 can you take care of this one? It should simply be a matter of adding an optional "password" attribute to auth.json, then pass it to CCXT during instantiation. Here is how CCXT handles this: https://github.com/ccxt/ccxt/blob/master/python/ccxt/gdax.py

Hi @dmbrady01, we added the option to add a password into the auth.json on the develop branch, please notify us if it's working. Thanks.

Hi @AvishaiW. Yes it works for me, thanks

added to catalyst 0.5.4


ModernNuGetUpgrader

An early iteration of changes to enable anonymous queries of which version of VFSForGit is the latest version for an organization.
Goal
Enable anonymous queries to an endpoint to get the version of GVFS that a client should download. The version to be downloaded depends on:

Organization name
Ring (e.g. fast / slow)
Platform (e.g. windows, macOS, linux, etc...)

Design
A new endpoint (currently called orginfoserver) will be responsible for answering the query of which version of VFSForGit to download to download based on provided criteria.
A new Upgrader (currently named ModernNuGetUpgrader) will be implemented that will query the above endpoint to determine what version of VFSForGit to download. ModernNuGetUpgrader extends from NuGetUpgrader, and re-uses most of the logic. The main difference is in the TryQueryNewestVersion, which will make an anonymous query to determine the version of VFSForGit to download. This version will then be downloaded in TryDownloadNewestVersion
Notes

I might pull out the line ending normalization commit into its own PR to reduce the clutter in the change

TODO:

[ ] Add more tests
[ ] Code cleanup

[ ] Nuget -> NuGet
[ ] Reconcile different versions of parsing the NuGet Feed URL
[ ] Other

[ ] Test more error cases

#1039 is based off the core commits in this change - but includes more details / tests around querying the org info server, and does not include IQueryGVFSVersion.


fix: use the defined delim for namegen instead of the hardcoded "-"

closes #12

Thanks for the fix George, merged your PR.


Info Msg in Log "unsupported ebusd version" - There is a new ebus Version 23.1 available

Hi,
I get as warn level follow log message "unsupported ebusd version found (too new): 23.1 supported version is 22.3".
ebusd Version 23.1 is very new (available since 07-Jan-2023).
Thank you and best Regards

can you confirm, that new ebusd version runs well with adapter? Otherwise I need to check by myself...
Will update supported verion if it's clear that adapter and ebusd update are compatible...

I will have a look for the next view days to check if there is everything working fine.
Best Regards
Daniel

supported with 3.1.1


DataGrid scrollbar

To help us process the issue more efficiently, please provide the following information:

Specify the version of the devextreme-angular and devextreme packages you are using.
devexteme version: 18.1.6
devextreme-angular version: 18.1.6
Specify the type of the issue (check one with "x"):
[X] bug Report

We encountered a disparity in the Data Grid scrollbar. Here the two scenarios:

[MacOS] [Chrome]

By default, the scrollbar is visible, square-shaped and it is aside from the grid.

[Windows10] [Chrome]

By default, the scrollbar is hidden. When the mouse pointer goes on the area of the grid, the scrollbar shows up. In this situation the scrollbar is thin, rounded and it is not aside from the grid, but it is over it. Then if the mouse pointer goes on the scrollbar area, it gets wider and square-shaped.
It would be more consistent if the scrollbar is visible and aside from the grid, in any case. We tried with the "showScrollbar: always", but nothing changed.

I can't reproduce the issue with DevExtreme 18.1.7. Data Grid scrollbars seem to be fine in Chrome running on Mac OS 10.13.6. Though they seem to be a bit buggy on Safari 12.01.

Versione 18.1.7 resolves the issue.
I'm using <dxo-scrolling useNative="true"></dxo-scrolling> to make the scroolbar always visible


Can't load package via composer

[Composer\Repository\InvalidRepositoryException]
No valid bower.json was found in any branch or tag of https://github.com/jq
uery/jquery-dist.git, could not load a package from it.

Please tell me the command you executed.
(e.g. composer require --dev --prefer-dist jamband/yii2-schemadump "*")
Also please tell me the contents of composer.json.

I have no idea what exactly happened, but now this works. Sorry


Proposal for Integrating Schemas in Backend

Currently, our backend lacks a structured approach to data modeling, specifically the absence of schemas. This can lead to issues related to data consistency, validation, and ease of maintenance. To address this, I propose integrating schemas into our backend architecture.

Hello Tushar, I would like to work on integrating Schemas in backend. Can i get more information about this so that i can proceed with it?


Error: "event" input is invalid, when triggering a workflow on schedule

Problem: Using cron syntax to trigger a workflow on schedule, makes the action fail.
On the other hand, triggering by workflow_dispatch works fine.
Here three different cron formats I have tried:
- cron: '00 07 * * 1-5'
- cron: '05 11 1-31 JAN-DEC MON-FRI'
- cron: '45 12 1-31 01-12 1-5'
Actions Logs:
Run hkusu/slack-post-action@v1
with:
channel: ***
user-name: *** tests results
user-icon: https://foo.com/foo.png
color: good
author-name: Project name - foo tests - :foo: Foo
author-icon: https://example.com/foo.jpeg
body: On sub-projects: :foo1: + :foo2: + :foo3: + :foo4: + :foo5: + :foo6:
footer-icon: https://example.com/foo.ico
log-button: Show logs
fields: []
footer: <|>
footer_icon: https://github.com/.png
actions: []
event: {
"schedule": "05 11 1-31 JAN-DEC MON-FRI"
}
run-id:<PHONE_NUMBER>2
github-token: ***
env:
color: good
SLACK_APP_TOKEN: ***
Error: "event" input is invalid.
Thanks a lot for implementing this great action :)

Thank you for the report. I will investigate the cause.

I am experiencing this as well with a scheduled action.

I think the problem is this line of code.
When an event is scheduled the json object for event looks like this:
event: {     "schedule": "15 10 * * *"   }
It appears that any event item is overwritten with this "schedule" item.
Which means when you check for !input.event.repository will fail.

When I tried it, it seems that schedule event is working correctly now.
GitHub's specifications may have changed, and as a result it may have worked well.


Add a LICENSE file

@moahmed would be nice to clarify what the license for this is, otherwise it becomes difficult for other people to use.

yes, good one.
TODO: add GNU General Public License
On Tue, Feb 9, 2016 at 5:30 PM, Sanjay Bhangar<EMAIL_ADDRESS>wrote:

@moahmed https://github.com/moahmed would be nice to clarify what the
license for this is, otherwise it becomes difficult for other people to use.
—
Reply to this email directly or view it on GitHub
https://github.com/moahmed/ezcms/issues/3.

--
Mohd Ahmed
Director - HMI Technologies http://www.hmi-tech.net
Telephone number: +9122 - 2266-2313 / 2266-2601 / 2266-2875
Office Working hours: Monday to Saturday; 10:00 AM to 6:00 PM

@batpad I was looking for a good licence and came across this ...
https://github.com/batpad/jquery-rbox/blob/master/LICENSE
lol


Error when navigating to "Managing Projects"

 Issue by demory
Tuesday May 01, 2018 at 16:15 GMT
Originally opened as https://github.com/catalogueglobal/datatools-ui/issues/83

On current test server, seeing this error message when navigating to "Manage Projects" from home screen:

 Comment by landonreed
Tuesday Nov 13, 2018 at 19:02 GMT

Fixed during NYSDOT testing (pre-mongo-pojo merge into dev)

:tada: This issue has been resolved in version 4.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Scrolling body doesn't work

Are you requesting a feature or reporting a bug?
Bug
What is the current behavior?
   1) AssertionError: expected 593 to deeply equal 0

      Browser: Chrome 60.0.3112 / Mac OS X 10.12.2

         32 |    await t.eval(() => {window.document.body.scrollTop=0;})
       > 33 |    await t.expect(Selector('body').scrollTop).eql(0)

Same with window.scrollTo and any other native js ways to scroll the window to top. It just doesn't scroll.
I have the page where automated scrolling with hover/click doesn't work. I see that cursor is moving outside visible area but scrolling not happened.
Anyway, page may be any kind, just strange that above test can't be passed in any ways.
Specify your

operating system: Mac OS X 10.12.2
testcafe version: 0.16.2

it may not be related, but FTR I put up a setTimeOut with await after scrolling, to get it worked.

setTimeout also don't work
Can you provide code snippet?

I just figured out that scrolling works, we just have some react plugin on the page that performs some scroll animation and this animation triggers after I'm resetting scroll position or has some significant duration.

let s = Selector('.page-tab:not(.ng-hide) .contentPage')
        const sn = ClientFunction((el) => {
            return el().scrollTop = 650;
        }).with({boundTestRun: cafe});
        await sn(s)


BOUNTY: Have Slider Track Color and Donate Button outline have Hex Code #f57b14 (orange)

Orange track color for the network switch when the switch is "checked" (on Mainnet)
Border for donation button is now orange

I'll withdraw this bounty solution


ServerStartFailed add Throwable argument

hi
add Throwable as arg for serverStartFailed event

Hi @halimpuckjava. This can't be done without breaking the current API. It also shouldn't be required, since the program exits?
I'll close this, but feel free to reopen if you think you have a valid use-case that we can dicuss for Javalin 4.


fhirSharedLib is defined multiple times and conflicts.

Describe the bug
fhirSharedLib is defined multiple times and conflicts.
    <library id="fhirSharedLib">
        <fileset dir="${shared.resource.dir}/lib/postgresql" includes="*.jar"/>
    </library>

To Reproduce
View disabled/overrides in bulkdata and datasource.xml
Expected behavior
There server.xml should define the libraries and reference in the datasource.xmls
Additional context
Team discussion

while we're in there, please nix this line in the postgres datasource config:


Fix ids in the downloaded KGTK file from T2WML

Files to reproduce
issue_151.tar.gz

Input data file - 04_worker_incidents.xlsx
upload properties - properties.tsv, kgtk_properties.tsv
wikifier - consolidated-wikifier.csv
Item definitions - extra_edges.tsv, kgtk_units.tsv, kgtk_variables.tsv
yaml - t2wml.yaml

Seems to be working from the development branch.
I have a clarification question @devowit
Why are the ids for qualifier edges blank ? Is this a conscious decision?

re @saggu yes it was a conscious decision, I designed it according to specs from @szeke
if the specs have changed, let me know.

Nope, specs are still the same. Thanks for clarifying


Boostrap 4.1.2 modal on dispose appending padding-right: 17 px

When i attempt to dispose a modal with a validation included. It appends padding-right 17 to the body with no reason.

the code:
var estado = $('#state2').find(":selected").val();
 if (jQuery.isEmptyObject({estado})   || (estado == 0) ) {
alert('message?: DOMString')
//event.preventDefault();
$('#estadoModalEdit').modal('dispose')
}

Note: Modal Hide is not working. This validation runs when the modal is attempting to show.

I to am experiencing this issue, weirdly its after downloading the latest release. I can't recreate it in a live demo as Im using it in a full stack web application.

Hey there!
We're automatically closing this issue since the original poster (or another commenter) hasn't yet responded to the question or request made to them 14 days ago. We therefore assume that the user has lost interest or resolved the problem on their own. Closed issues that remain inactive for a long period may get automatically locked.
Don't worry though; if this is in error, let us know with a comment and we'll be happy to reopen the issue.
Thanks!
(Please note that this is an automated comment.)


Issue #336: Added power functionality

Description & Motivation
In SystemVerilog, power (a**b) is a useful function.
It would be nice to have a synthesizable Module and associated functions for generating hardware and SystemVerilog with powers as per issue #336

Testing

Added necessary test cases to test/logic_value_test.dart and test/math_test.dart
Documentation

Does the change require any updates to documentation? If so, where? Are they included?

Yes. Updated both README.md and doc/tutorials/chapter_2/00_basic_logic.md

Hi @mkorbel1
There is a test case where  LogicValue.ofBigInt(BigInt.zero, width) for any width > 64  leads to throw an error in case of arithmetic +,-,* operations when applied to the same LogicValue. It throws an error only when both are valued zero.
E.g., LogicValue.ofBigInt(BigInt.zero, 128) + (LogicValue.ofBigInt(BigInt.zero, 128)) throws an error.
Can you please confirm if this is an issue or I misunderstood something. If it's an issue, we need to handle _FilledLogicValue with width>64 also for arithmetic operations.

There is a test case where LogicValue.ofBigInt(BigInt.zero, width) for any width > 64 leads to throw an error in case of arithmetic +,-,* operations when applied to the same LogicValue. It throws an error only when both are valued zero.
E.g., LogicValue.ofBigInt(BigInt.zero, 128) + (LogicValue.ofBigInt(BigInt.zero, 128)) throws an error.
Can you please confirm if this is an issue or I misunderstood something. If it's an issue, we need to handle _FilledLogicValue with width>64 also for arithmetic operations.

@Sanchit-kumar, yes this looks like a bug, thanks for raising it!  I think this is a manifestation of #299 which is WIP being addressed in PR #319 (which has been WIP for a while, should probably poke on that).  Your test case that reproduces the issue is pretty simple, so I'll make a note on that issue to suggest using that as an additional test case.  Sorry you ran into this!


Support imgui related abi

When trying to compile imgui-rs using cranelift, the build succeeds however there are some heavy artefacts.
Screen of the artefacts in my game, left: expected, right: actual:

However when building, the only warnings are:
warning: Argument of type `sys::ImVec2` with pass mode `ByValPair(types::F32, types::F32)` is not yet supported for non-rust abi `"C"`. Calling this function may result in a crash.

(x32)
It seems like implementing ByValPair should do the trick, but I'm not sure what it would implicate.

Interesting. It would expect the C abi incompatibility to crash your program when it is hit, not use a different background color. Fixing this abi incompatibility is not something that I can just do in a few hours. I have been planning to do a complete overhaul of the abi handling code in cg_clif to use the same abi calculation as cg_llvm. This requires some refactorings on the rustc side though. I have already started this about a month ago, but was busy with midterm exams for the past few weeks. Now that they are over I plan to continue on this soon.

Interesting. It would expect the C abi incompatibility to crash your program when it is hit, not use a different background color. Fixing this abi incompatibility is not something that I can just do in a few hours. I have been planning to do a complete overhaul of the abi handling code in cg_clif to use the same abi calculation as cg_llvm. This requires some refactorings on the rustc side though. I have already started this about a month ago, but was busy with midterm exams for the past few weeks. Now that they are over I plan to continue on this soon.

It surprised me a lot too! I have no idea how it doesn't crash. Two imgui windows are missing however a lot of things work as expected, I guess it just stops rendering at some point and a half finished ui appears.

I have been planning to do a complete overhaul of the abi handling code in cg_clif to use the same abi calculation as cg_llvm. This requires some refactorings on the rustc side though. I have already started this about a month ago, but was busy with midterm exams for the past few weeks. Now that they are over I plan to continue on this soon.

I expected that the ByValPair would just me some small layer over the ByVal, but I guess abi is more complicated. :grin:
Take your time, and thank you for your work!

It surprised me a lot too! I have no idea how it doesn't crash. Two imgui windows are missing however a lot of things work as expected, I guess it just stops rendering at some point and a half finished ui appears.

I have been planning to do a complete overhaul of the abi handling code in cg_clif to use the same abi calculation as cg_llvm. This requires some refactorings on the rustc side though. I have already started this about a month ago, but was busy with midterm exams for the past few weeks. Now that they are over I plan to continue on this soon.

I expected that the ByValPair would just me some small layer over the ByVal, but I guess abi is more complicated. :grin:
Take your time, and thank you for your work!

I expected that the ByValPair would just me some small layer over the ByVal, but I guess abi is more complicated. 😁

The x86_64 SystemV abi likes to pack structs into a small amount of registers. For example (u64, u64) would be stuffed into two registers, while (u8, u8) would only use a single register. No warning triggering doesn't mean that the abi is correct by the way.

Take your time, and thank you for your work!

Thanks a lot!

I expected that the ByValPair would just me some small layer over the ByVal, but I guess abi is more complicated. 😁

The x86_64 SystemV abi likes to pack structs into a small amount of registers. For example (u64, u64) would be stuffed into two registers, while (u8, u8) would only use a single register. No warning triggering doesn't mean that the abi is correct by the way.

Take your time, and thank you for your work!

Thanks a lot!

@Uriopass Can you try the abi_compat branch? This branch should have fixed all abi incompatibilities I know of except for a small one that I don't think really matters on x86_64. If this isn't fixed please also tell me the exact commit you used. I may have fixed this abi incompatibility in the mean time.

@Uriopass Can you try the abi_compat branch? This branch should have fixed all abi incompatibilities I know of except for a small one that I don't think really matters on x86_64. If this isn't fixed please also tell me the exact commit you used. I may have fixed this abi incompatibility in the mean time.

Looks like it works! :tada:

The incremental compile also takes one second less when adding a print to my main (from 8.7s to 7.8s). Also, does the cargo.sh script use the linker provided in the ~/.cargo/config file ?
The audio is heavily distorted though. I'm not sure if it has to do with abi (from cpal ?) or some weird rodio concurrency things.
Expected (cargo run):
https://user-images.githubusercontent.com/5420739/106354170-f27e4780-62ef-11eb-9ba9-a5fd6a6b270c.mp4
Actual (cranelift built): :warning: very loud :warning:
https://user-images.githubusercontent.com/5420739/106354176-fd38dc80-62ef-11eb-99f4-22d465513dc0.mp4
I might investigate a bit more the day I want audio working with cranelift :grin:
Very nice work!

Looks like it works! :tada:

The incremental compile also takes one second less when adding a print to my main (from 8.7s to 7.8s). Also, does the cargo.sh script use the linker provided in the ~/.cargo/config file ?
The audio is heavily distorted though. I'm not sure if it has to do with abi (from cpal ?) or some weird rodio concurrency things.
Expected (cargo run):
https://user-images.githubusercontent.com/5420739/106354170-f27e4780-62ef-11eb-9ba9-a5fd6a6b270c.mp4
Actual (cranelift built): :warning: very loud :warning:
https://user-images.githubusercontent.com/5420739/106354176-fd38dc80-62ef-11eb-99f4-22d465513dc0.mp4
I might investigate a bit more the day I want audio working with cranelift :grin:
Very nice work!

Also, does the cargo.sh script use the linker provided in the ~/.cargo/config file ?

Yes, it is just a thin wrapper around cargo that uses cg_clif instead of rustc and adds a jit and lazy-jit subcommand.

The audio is heavily distorted though. I'm not sure if it has to do with abi (from cpal ?) or some weird rodio concurrency things.

Does it print any warnings to stdout like buffer under run? If so that would indicate that it is simply to slow with feeding new audio input to alsa. This may be due to the global lock I use to emulate atomics. In that case I would expect it to be more of a stuttering with clearly recognizable parts in between the pauses though. If that isn't the problem it may be helpful to make a smaller reproducing example. Maybe it also happens with one of the rodio or cpal example?

Also, does the cargo.sh script use the linker provided in the ~/.cargo/config file ?

Yes, it is just a thin wrapper around cargo that uses cg_clif instead of rustc and adds a jit and lazy-jit subcommand.

The audio is heavily distorted though. I'm not sure if it has to do with abi (from cpal ?) or some weird rodio concurrency things.

Does it print any warnings to stdout like buffer under run? If so that would indicate that it is simply to slow with feeding new audio input to alsa. This may be due to the global lock I use to emulate atomics. In that case I would expect it to be more of a stuttering with clearly recognizable parts in between the pauses though. If that isn't the problem it may be helpful to make a smaller reproducing example. Maybe it also happens with one of the rodio or cpal example?

EDIT: Looks like it doesn't. running using RUSTFLAGS="-Clink-arg=-fuse-ld=lld" ~/cranelift/cargo.sh run gives another 1.5s of improvement for patched incremental (from 7.8s to 6.26s)

Huh???

EDIT: Looks like it doesn't. running using RUSTFLAGS="-Clink-arg=-fuse-ld=lld" ~/cranelift/cargo.sh run gives another 1.5s of improvement for patched incremental (from 7.8s to 6.26s)

Huh???

I thought I had my config misconfigured but...
still for incr patched:
no ~/.cargo/config:
cargo build: ~12.5s
cranelift build: ~7.7s
with ~/.cargo/config set to this:
[target.x86_64-unknown-linux-gnu]
rustflags = ["-Clink-arg=-fuse-ld=lld"]

cargo build: ~8.0s
cranelift build: ~7.7s (doesn't rebuild compared to no config)
with RUSTFLAGS="-Clink-arg=-fuse-ld=lld" prefix and no ~/.cargo/config:
cargo build: ~8.0s (doesn't rebuild compared to with config)
cranelift build: ~5.5s
Maybe the target I'm using is wrong?

I thought I had my config misconfigured but...
still for incr patched:
no ~/.cargo/config:
cargo build: ~12.5s
cranelift build: ~7.7s
with ~/.cargo/config set to this:
[target.x86_64-unknown-linux-gnu]
rustflags = ["-Clink-arg=-fuse-ld=lld"]

cargo build: ~8.0s
cranelift build: ~7.7s (doesn't rebuild compared to no config)
with RUSTFLAGS="-Clink-arg=-fuse-ld=lld" prefix and no ~/.cargo/config:
cargo build: ~8.0s (doesn't rebuild compared to with config)
cranelift build: ~5.5s
Maybe the target I'm using is wrong?

Can you show executed rustc command for the final executable for both cases with cg_clif? (You can pass -v to cargo.sh to see it)

Can you show executed rustc command for the final executable for both cases with cg_clif?  This probably overrides .cargo/config.

cargo.sh always sets RUSTFLAGS, even if it is just a space in most cases. This probably overrides .cargo/config.

Replacing this line in config.sh:56
export RUSTFLAGS=$linker" "$RUSTFLAGS

with
if [ ! -z $linker ]; then
    export RUSTFLAGS=$linker" "$RUSTFLAGS
fi

did the trick for me :)

Replacing this line in config.sh:56
export RUSTFLAGS=$linker" "$RUSTFLAGS

with
if [ ! -z $linker ]; then
    export RUSTFLAGS=$linker" "$RUSTFLAGS
fi

did the trick for me :)

Couldn't reproduce the audio issue :/ I'm using a lot of atomics though so I guess it might help if they were native some day.

Couldn't reproduce the audio issue :/ I'm using a lot of atomics though so I guess it might help if they were native some day.

Cranelift is currently moving towards a new backend framework. The new x86_64 backend supports atomic instructions, but the old one doesn't. I moved cg_clif to the new backend by default a few days ago, but I want to preserve compatibility with the old backend for a while just in case a serious problem shows up. Once I remove support for the old backend I will switch to native atomic instructions.

Cranelift is currently moving towards a new backend framework. The new x86_64 backend supports atomic instructions, but the old one doesn't. I moved cg_clif to the new backend by default a few days ago, but I want to preserve compatibility with the old backend for a while just in case a serious problem shows up. Once I remove support for the old backend I will switch to native atomic instructions.


Make sure the app never dies while on the background ($150)

Is your feature request related to a problem? Please describe.
Prioritize reliabiliy over battery.
A few minutes after the processing of the app goes on, iOS and android kill the app while on the background.
Fix this so that the app never dies, specially on iOS.

This should avoid the app to die. Try bee app, it never dies because of the location request, but maybe there are other reasons.

btw, having the position on where the audio was recorded could be an incredible feature.
or grouping memory by places (work, home, etc...)

https://dontkillmyapp.com/

@josancamon19
I was thinking what if we store multiple locations for a memory? That is let's say if the user travels from one location to another, we will have the record of both the locations which the user can see for that memory.

Closed by @mdmohsin7, just released, will reopen later if performance was not improved on release versions, and based from community feedback


JEFF XS library in BW sciteam folder nomenclature for natural composition

Currently, in the JEFF XS library, the code for natural composition is EE-nat (e.g. C-nat, Ga-nat, Os-nat). This is inconsistent with the ENDFVII library. It should be changed to the format ZZ000. It seems like I have no permission to change the files.

Perhaps we can use the PyNE capability to convert?

I am not sure what do you mean "use PyNE capability to convert"...
Convert JEFF library to ENDFB-VII?
JEFF doesn't contain data for natural compositions, so, we have to describe isotopic composition by hand.

I thought JEFF does contain data for natural compositions, and it is just called differently
JEFF -> EE-nat
ENDF -> ZZ000

For ones that do not have data for natural compositions, I think what prof Huff means is to use Pyne's natural abundancy function to automate the generation of natural composition data. Something like:
# to get the cross section of natural composition of lithium
for( every lithium isotope in JEFF):
    xsec_dict[isotope] = (xsec, pyne.data.natural_adund(isotope))
natural_xsec = sum( [i[0] *i[1] for i in xsec_dict.values()])
return natural_xsec

No, both libraries use either notation:
EE-nat ZZ000
The problem is:
ENDF contains data for 44 elements while home-baked JEFF only 10.
So, I cannot add this natural composition in JEFF.
But one can change SERPENT input file a bit to switch from ENDF to JEFF.
Yes, a script with PyNE call might help to automate this process.
@katyhuff Does the script worse to be developed knowing than BW will be retired soon and my home-baked library will be abandoned?

We have at least until April 2019 with BW, possibly longer, TBD.

Should this be closed as wontfix?

@katyhuff Since, BW lifetime extended, I'll try to create such script.

Only prioritize this if it is helpful for you or others who remain in the
group. Since this issue was opened by someone no longer in the group, for a
project they are no longer engaged in, it may not be on the critical path.
On Mon, Sep 9, 2019 at 3:58 PM Andrei Rykhlevskii<EMAIL_ADDRESS>wrote:

@katyhuff https://github.com/katyhuff Since, BW lifetime extended, I'll
try to create such script.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/arfc/arfc.github.io/issues/91?email_source=notifications&email_token=AADAFK4IFSKXUWSD4GMFQKDQI22HHA5CNFSM4FNJWAK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6JARRY#issuecomment-529664199,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADAFKYEL3KGDF64GPUBA4LQI22HHANCNFSM4FNJWAKQ
.

--
http://katyhuff.github.com

It is true. Closing


Proposal: replace "convention" with "default" in modeling docs

Our docs on modeling talk of "conventions", which is a bit EF-specific and probably isn't very understandable to new users. The usual term here is to simply describe what EF does by default - we should consider making this change to make the docs more accessible.
The concept of conventions is important in that they're modifiable by users, but that seems like quite an advanced/atypical scenario which should simply be treated in its own "advanced usage" page.

Closing for now as this doesn't seem very necessary.


[SPARK-37331][K8S] Add the ability to create resources before driverPod creating

What changes were proposed in this pull request?
This patch adds a new method getAdditionalPreKubernetesResources for KubernetesFeatureConfigStep. It returns any additional Kubernetes resources that should be added to support this feature and resources would be setup before driver pod
creating.
After this patch:

getAdditionalPreKubernetesResources: Devs should return resources in here when they want to create resources before pod creating
getAdditionalKubernetesResources: Devs should return resources in here when they can accept the resources create after pod, and spark will also help to refresh owner reference after resources created, that means if any resource is expected to refresh the owner pod reference, it should be added it here, even if it already in the getAdditionalPreKubernetesResources as same.

Why are the changes needed?
We need to setup K8S resources or extension resources before driver pod creating, and then create pod, after the pod created, the owner refernce would be owner to this Pod.
These pre-resources are usually necessary in pod creation and scheduling, they should be ready before pod creation, should be deleted when user delete pod, the lifecycle of these resource is same with pod, such as the customized batch scheduler scenario, the user need to create the addtional pre resources (such as pod group in Volcano) to help the specific spark job complete batch scheduling.
Does this PR introduce any user-facing change?
No
How was this patch tested?
UT

Test build #145228 has started for PR 34599 at commit 68b5cf3.

cc @Dooyoung-Hwang @holdenk

Test build #145228 has finished for PR 34599 at commit 68b5cf3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49698/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145228/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49698/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49698/

Test build #145231 has started for PR 34599 at commit f8f2dd4.

Test build #145231 has finished for PR 34599 at commit f8f2dd4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145231/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49701/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49701/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49701/

Intergration test failed is unrelated, ready for review.

Cool, I'll take a look. I've also got a PR to cleanup the integration test failures ( https://github.com/apache/spark/pull/34636 )

@holdenk Thanks for your review!

Test build #145362 has started for PR 34599 at commit 7d7d98d.

Test build #145362 has finished for PR 34599 at commit 7d7d98d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145362/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49833/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49833/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49833/

@dongjoon-hyun Would you mind giving some suggestion on this? Sorry to ping wrong person in https://github.com/apache/spark/pull/34599#issuecomment-968704348 . : )

Sorry for being late. I'll review now.

In theory, this feature looks unsafe because there is a chance to leak the pre-populated resources because they have no owner yet.

Yes, that's a good point, and the cleanup operations of pre-populated resource is required, will add cleaup pre-populated resource logic

Please minimize the change. For example, we had better keep the existing resource management code for the non-pre-polulated code.

Thanks for your suggestion, will address in next commit.

Test build #145816 has started for PR 34599 at commit a48e2fd.

Test build #145816 has finished for PR 34599 at commit a48e2fd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145816/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50291/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50291/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50291/

Test build #145859 has started for PR 34599 at commit 9b14667.

Test build #145859 has finished for PR 34599 at commit 9b14667.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50334/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145859/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50334/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50334/

Thank you for updates, @Yikun . I'll review again.

Retest this please

Test build #146049 has started for PR 34599 at commit 9b14667.

Test build #146049 has finished for PR 34599 at commit 9b14667.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50524/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/146049/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50524/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50524/

@dongjoon-hyun Thanks for your review!

Test build #146272 has started for PR 34599 at commit 7e3c0ae.

Test build #146272 has finished for PR 34599 at commit 7e3c0ae.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

This PR doesn't have a test case. Could you add a test coverage for your code path please?

Sure, thanks for reminder, I have added the testcase in latest commit.

could you elaborate why we need to create some resource before driver pod creation?

These resources are usually necessary in pod creation and scheduling, they should be ready before pod creation, should be deleted when user delete pod, the lifecycle of these resource is same with pod, there are some scenarioes:

Extension custom resources, they are usually created in k8s or kubernete extension compoent, such as the customized scheduler scenario, the user need to create the addtional pre resource (such as pod group) for the specific spark job. See more in here.
The temporary priority class, the user could create the priority class in custom feature step for specific job and also delete it when job deleted.

@dongjoon-hyun Much thank for your patient and guidance.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/146272/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50747/

Test build #146280 has started for PR 34599 at commit 5aba6eb.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50747/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50747/

Test build #146280 has finished for PR 34599 at commit 5aba6eb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/146280/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50754/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50754/

Retest this please

Test build #146285 has started for PR 34599 at commit 5aba6eb.

Test build #146286 has started for PR 34599 at commit 5aba6eb.

Test build #146285 has finished for PR 34599 at commit 5aba6eb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #146286 has finished for PR 34599 at commit 5aba6eb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/146285/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/146286/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50759/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50759/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50759/

Thank you for update, @Yikun !

Test build #146294 has started for PR 34599 at commit ebbfea6.

Test build #146294 has finished for PR 34599 at commit ebbfea6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/146294/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50766/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50766/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50766/

Test build #146312 has started for PR 34599 at commit 2613a92.

Test build #146312 has finished for PR 34599 at commit 2613a92.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

@dongjoon-hyun Thanks for your review, addressed your comments in latest commit.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/146312/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50784/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50784/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50784/

@dongjoon-hyun Much thanks for your help!


fix leaking hex_registry table

It may fix #707

This appears to kill the tests :(

The second commit https://github.com/pvmart/rebar3/commit/c2d9aec502682e836fc58e00f17e60b331e40159 fixes tests.

They still fail in Travis half the time: https://travis-ci.org/rebar/rebar3/builds/76269043

Yeap :(
/home/travis/build.sh: line 41:  2331 Killed                  ./rebar3 ct
The command "./rebar3 ct" exited with 137.

Looks like it takes to long to run ct or not enough memory.

I can go in there and give it a nudge, but, uh, that's not something we want to keep doing for good. If a thing that fixes a memory leak either hangs the process or uses so much memory it's worse than the leak, it's no good.
I'll kick in another run.

Now tests runs at least 3 times longer than before. Because full hex registry loaded for every rebar_state:new.

Yea, best not to do that. We should only need 1 copy of the hex registry ever.

Storing it in state would be ok in the future maybe, when we split out the stuff from state that requires us to keep creating new copies.

Loading hex registry for every rebar_state:new happens only for tests.

Oooo, ok. Damn.

Sweet, all tests green. +1.


Redis update 2021-10-08

What do these changes do?
Updates aioredis to redis at commit andymccurdy/redis-py@9419f1d56beff5b350c87785cc57f2431fe85cbb
This does NOT include "Add retry mechanism with backoff (#1494)"
There may be additional updates to redis-py that merge my PRs there, but they should already be included here.
Are there changes in behavior for the user?
Yes, several new commands

Related issue number
Fixes #1145 #1136 #1130 #1205

Several
Checklist

[ ] I think the code is well written
[x] Unit tests for the changes exist
[ ] Documentation reflects the changes
[x] If you provide code modification, please add yourself to CONTRIBUTORS.txt

The format is <Name> <Surname>.
Please keep alphabetical order, the file is sorted by names.

[x] Add a new news fragment into the CHANGES/ folder

name it <issue_id>.<type> (e.g. 588.bugfix)
if you don't have an issue_id change it to the pr id after creating the PR
ensure type is one of the following:

.feature: Signifying a new feature.
.bugfix: Signifying a bug fix.
.doc: Signifying a documentation improvement.
.removal: Signifying a deprecation or removal of public API.
.misc: A ticket has been closed, but it is not of interest to users.

Make sure to use full sentences with correct case and punctuation, for example:
Fix issue with non-ascii contents in doctest text files.

Hey @abrookins ; would be great to get some help to resolve some of these here. Thanks!

Really excellent work @Andrew-Chen-Wang - I've managed to read through most of this.
I have a couple comments I'll add when I'm at a keyboard, but overall I'm glad to see these changes ported over. It'll really move this implementation forward!

Only two failing tests remain:
test_bgsave[pool] and test_client_list_client_id[pool]

@seandstewart and @Andrew-Chen-Wang, you guys are the true heroes of aioredis. Apologies that I've not had the time I planned to work on this library after offering to help maintain it. I'm actively trying to find people within Redis who can help in my stead.
Async is important to Redis (the company) and we plan to actually support it with engineering effort, but for some time now our Python folks have had their hands full with regular sync client code in redis-py. I'm trying to get a better community update/plan for async support that we can share publicly.

@seandstewart and @Andrew-Chen-Wang, you guys are the true heroes of aioredis. Apologies that I've not had the time I planned to work on this library after offering to help maintain it. I'm actively trying to find people within Redis who can help in my stead.
Async is important to Redis (the company) and we plan to actually support it with engineering effort, but for some time now our Python folks have had their hands full with regular sync client code in redis-py. I'm trying to get a better community update/plan for async support that we can share publicly.

Thanks for the shout-out @abrookins - I completely understand. I'm a huge fan of the work y'all have put into redis-py and I look forward to seeing where y'all take both clients in the future.

As of the latest batch of commits, this branch is now up-to-date with redis/redis-py@4e9cc015

Okay @abrookins @Andrew-Chen-Wang - this PR is up-to-date with<EMAIL_ADDRESS>and we've got a green CI

Woohoo! Tysm @seandstewart . Out of curiosity, what is the reason for the major version bump? And are we hoping to get a release out with just these and previous changes? Hoping we can resolve #1040 first using the contextvar method.

Woohoo! Tysm @seandstewart . Out of curiosity, what is the reason for the major version bump? And are we hoping to get a release out with just these and previous changes? Hoping we can resolve #1040 first using the contextvar method.

I think it's reasonable to get a few things out into v2 before we merge this code, but I'm also wary of long-lived PRs.
I'm pretty familiar with contextvars so I'll take a look at that issue and a few others. Perhaps we can push out a 2.1 with some QOL improvements before we merge all this

can we get PR https://github.com/aio-libs/aioredis-py/pull/1129 in this, fixes #1121?

@seandstewart I think we should merge this now before further patches and stuff come as the layout of redis-py is changing rapidly.

We have a ETA when this will hit production?


Is there a way to call a sandboxed function asynchronously ?

Hello,
I would like to implement events in sandboxr, but cannot find a way with generator functions. My code so far :
const acorn = require("acorn");
const SandBoxr = require('sandboxr');

var env = SandBoxr.createEnvironment();
env.init();

var ast = acorn.parse(`
    sheet.on('click', () => {
        console.log('clicked');
    });
`);

let sheet = env.objectFactory.createObject();
sheet.define('on', env.objectFactory.createFunction(function* (event, fn) {
    // how to call fn.call() asynchronously ?
}));

let v = env.createVariable('sheet');
v.setValue(sheet);

var sandbox = SandBoxr.create(ast);
sandbox.execute(env);

Is this even possible without blocking the execution ?

Don't use a generator function. If you return a promise inside your function, the evaluator will wait until the promise is resolved to continue execution.


Update kernel regex

For #27.
This updates:

the notebook conda dialog to correctly identify the current environment, based on nb_conda_kernels 2.0.0
some minor visual fixes
some more basic tests
uses requirements.txt instead of environment.yml for tests, etc.

Coverage decreased (-0.6%) to 49.355% when pulling 809a64b6d6cffddb86bf2f528fb94993e262c5d2 on update-kernel-regex into 2b520527831aae1022af7ae7b8bb8447913ee625 on master.

Blocked by:
https://github.com/conda-forge/tornado-feedstock/pull/7

Coverage remained the same at 50.0% when pulling 7f6e956ed2bb9f1f1dc56107bc05e08b0a6cb2ab on update-kernel-regex into 2b520527831aae1022af7ae7b8bb8447913ee625 on master.

Coverage increased (+25.6%) to 75.628% when pulling b6378153bc42a03e477e66ca35628dd81e7b38a2 on update-kernel-regex into 2b520527831aae1022af7ae7b8bb8447913ee625 on master.

Coverage increased (+25.6%) to 75.628% when pulling b6378153bc42a03e477e66ca35628dd81e7b38a2 on update-kernel-regex into 2b520527831aae1022af7ae7b8bb8447913ee625 on master.

Hot dang, all 💚 ! Actually went and checked the appveyor builds, as i didn't really believe it... whaddya know, lots of ".trash ain't empty" messages. Just like the bad old days. But everything worked. So I'll take it.
Review love appreciated, @damianavila @mmarchetti @malev or anybody else you guys can think of that have spent time on this on. ended up being rather large.

I did a brief review... +1 on the addition of tests!

Quick overview as well, but this look nice... I like some of the simplifications I saw and obviously the tests are a great addition. Wondering why you decide to use the APIHandler + Mixin instead of continuing with the EnvHandler. I like the approach you took but this is something derived from other work, or other extensions you wrote/saw or just you saw the opportunity to make this way and did it?

Wondering why you decide to use the APIHandler + Mixin instead of continuing with the EnvHandler

Kind of a leftover... i was looking at whether there needed to be a separate handler for some of the end points, but it didn't. I'll simplify it back down.

Coverage increased (+26.8%) to 76.808% when pulling<PHONE_NUMBER>78fa36ccfb70e664ebef4aece35cbf on update-kernel-regex into 2b520527831aae1022af7ae7b8bb8447913ee625 on master.

Coverage increased (+26.8%) to 76.808% when pulling cd2d9dd535d3008ab8c8d73ed0a463777f57782d on update-kernel-regex into 2b520527831aae1022af7ae7b8bb8447913ee625 on master.

Ok, back to the simpler inheritance pattern! __mro__-begone!

Ok, liking this! I'm going to merge and tag!


A potential bug in multi-GPU training

Hi,
I found the following strange phenomena when running tiny llama pretraining.

When using multiple GPUs, I got completely different results when running the same code twice.  Further, many loss spike occurs. See the example for 2-card training. I use all the default settings except that I shrink the learning rate from 4e-4 to 2e-4 and batchsize from 1024 to 512.

AdamW 2-card: run1
wandb: 🚀 View run at https://wandb.ai/yushunzhang0410/pretrain-tiny-llama-1.1b/runs/83b8yfjz
AdamW 2-card: run2
wandb: 🚀 View run at https://wandb.ai/yushunzhang0410/pretrain-tiny-llama-1.1b/runs/8p6axrgw
Two runs are totally different and the training fails.

When simply changing the above settings to single GPU, these issues do not occur. Two runs are mostly the same (with slight difference though) and the loss decreases stably without any spikes.

AdamW 1-card: run 1
wandb: 🚀 View run at https://wandb.ai/yushunzhang0410/pretrain-tiny-llama-1.1b/runs/kdg2qmj8
AdamW 1-card: run 2
wandb: 🚀 View run at https://wandb.ai/yushunzhang0410/pretrain-tiny-llama-1.1b/runs/vh23qd0u
Two runs are mostly the same and the loss decreases stably.
Do you encounter a similar issue? Any idea why?

The above problem occurs when using TinyLlama code from litgpt. Problem solved using the code from this codebase.


Suspected concurrency issue - unique constraint violation for Spree::Adyen::HppSource

The concurrency fixes from earlier this week seem to have improved things, but not entirely solved the issue. Previously we were getting unique constraint violations on Spree::Adyen::HppSource from both /adyen/notify and when the users were being redirected back, but now we only get them from notifications.
The relevant stack trace is:
106
File "/app/vendor/bundle/ruby/2.2.0/bundler/gems/solidus-adyen-0b92497bcab4/app/models/spree/adyen/notification_processor.rb" line 125 in create_missing_payment
107
File "/app/vendor/bundle/ruby/2.2.0/bundler/gems/solidus-adyen-0b92497bcab4/app/models/spree/adyen/notification_processor.rb" line 39 in block in process!
108
File "/app/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.4/lib/active_record/locking/pessimistic.rb" line 72 in block in with_lock
109
File "/app/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.4/lib/active_record/connection_adapters/abstract/database_statements.rb" line 213 in block in transaction
110
File "/app/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.4/lib/active_record/connection_adapters/abstract/transaction.rb" line 184 in within_new_transaction
111
File "/app/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.4/lib/active_record/connection_adapters/abstract/database_statements.rb" line 213 in transaction
112
File "/app/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.4/lib/active_record/transactions.rb" line 220 in transaction
113
File "/app/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.4/lib/active_record/transactions.rb" line 277 in transaction
114
File "/app/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.4/lib/active_record/locking/pessimistic.rb" line 70 in with_lock
115
File "/app/vendor/bundle/ruby/2.2.0/bundler/gems/solidus-adyen-0b92497bcab4/app/models/spree/adyen/notification_processor.rb" line 37 in process!
116
File "/app/vendor/bundle/ruby/2.2.0/bundler/gems/solidus-adyen-0b92497bcab4/app/controllers/spree/adyen_notifications_controller.rb" line 17 in notify

So the issue is actually on a line where we create a payment, which includes a Spree::Adyen::HppSource which has not yet been created either, and it fails to create it due to this constraint. This is correct, because otherwise it would create a duplicate payment on the order as well. Not sure why this now only affects the notify path, where the redirect seems fine. Perhaps as the lock will only reload the order we also need to try and re-find the notification payment (or should_create_payment should look to see if the order is complete as part of it's conditions, which seems to be the differing logic between the two cases?)

This is very strange.
I'm going to attempt to write a full end to end test to try and pin point the race condition - a full end to end test would be nice to have anyways.

It would be great if I could also see the params were for the requests to adyen/notify and checkout/payment/adyen were

Sure, getting you the logs of the last few instances now, which include params for the checkout/payment/adyen. I'll get you access to our rollbar account (error logging system) so you can see the params of the posts, as that's the request which currently always errors.

Forgot that it was on rollbar, I already have access!

Should be fixed (maybe) by #55

Looks like it's all good now! Closing this off.

Excellent!

:fireworks:


PR to bring Dockerfile in line with official ones

Now based on aspnet runtime image not sdk (since there is nothing being built)
Merged all runs into one to prevent excess layers
Reduced image size (by removing packages not required for running the bot)
Made user name & id configurable
Now installing youtube-dl
Added reference to port exposing for webapi

@CM2Walki  What is the current status of youtube-dl drama? I think it is still not resolved, right? I don't want to have any legal issues by having this repository open.

I believe it has been resolved. It's back on Github:
https://github.com/ytdl-org/youtube-dl

Why is this PR not merged yet?
The yt-dl issue has been resolved: https://github.blog/2020-11-16-standing-up-for-developers-youtube-dl-is-back/

@skyfrk This only concerns the stance that GitHub is taking as far as I can tell. I can't find anything that this case has been settled or resolved.

Let me suggest a compromise, that should be fine:
I'll leave pip installed in the image and then call pip to install & update youtube-dl in the ENTRYPOINT/CMD. That way you would, strictly speaking, not have the youtube-dl in your image. It will be added at runtime.

Let me suggest a compromise, that should be fine:
I'll leave pip installed in the image and then call pip to install & update youtube-dl in the ENTRYPOINT/CMD. That way you would, strictly speaking, not have the youtube-dl in your image. It will be added at runtime.

For anyone still following this. I built my fork over at https://hub.docker.com/r/cm2network/ts3audiobot. If you want an image that includes youtube-dl by default.

since youtube-dl was reinstated and this has been silent for a while, I opted to merge #8 instead of this one. The end result is similar.


Deploy with vercel, click on an article and click on the logo in the upper left corner to jump to the domain name assigned by vercel instead of your own domain name.  netlify is normal

SITE_URL has been set

Sorry for the long response time, the issue has been fixed, so that it works even without setting the SITE_URL. However, please note that you need to re-deploy your project after setting SITE_URL otherwise it is not correctly picked up. This was the root cause in your case, however, as SITE_URL is not really needed for navigating to the main page, the code has been simplified.

Closed as solved.


Add CSV version of user lists

Please provide user lists also as csv for easier further processing.

wrong repo


Consistent help messages for all commands

What type of PR is this?
/component kudoctl
/kind cleanup
What this PR does / why we need it:
Commands previously were inconsistent with usage info... some used the default (like test and get) however several overrode the default help.   All the overrides resulted in the help text not be displayed at all.   For instance go run cmd/kubectl-kudo/main.go update --help
resulted in:
Update installed KUDO operator with new parameters.

Usage:
  kubectl-kudo update <instance-name> [flags]

Flags:
  -h, --help                    help for update
      --kubeconfig string       Path to your Kubernetes configuration file (default "/Users/kensipe/.kube/config")
      --namespace string        The namespace where the instance you want to upgrade is installed in. (default "default")
  -p, --parameter stringArray   The parameter name and value separated by '='

Now it results in:
go run cmd/kubectl-kudo/main.go update --help
Update installed KUDO operator with new parameters.

Usage:
  kubectl-kudo update <instance-name> [flags]

Examples:

		The update argument must be a name of the instance.

		# Update dev-flink instance with setting parameter param with value value
		kubectl kudo update dev-flink -p param=value

		# Update dev-flink instance in namespace services with setting parameter param with value value
		kubectl kudo update dev-flink -n services -p param=value

Flags:
  -h, --help                    help for update
      --namespace string        The namespace where the instance you want to upgrade is installed in. (default "default")
  -p, --parameter stringArray   The parameter name and value separated by '='

Global Flags:
      --kubeconfig string   Path to your Kubernetes configuration file (default "/Users/kensipe/.kube/config")

Making use of the examples in code.   It also has the advantage of showing what the global flags are.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kensipe
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [kensipe]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approve
-25, +0, my favorite kind of PR

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jbarrick-mesosphere, kensipe
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jbarrick-mesosphere,kensipe]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

nice 👏
/lgtm


DOC:  CSS for the left panel seems broken

Issue with current documentation:
In the left panel,  can't list all sub-topics properly

I am using https://python.langchain.com/docs/modules/model_io/prompts/example_selectors/,   it was correct at least 24H ago, but now it doesn't work for me
Idea or request for content:
No response

Answer generated by a 🤖
Answer
I apologize for the inconvenience you're experiencing with the CSS for the left panel in the LangChain documentation.
To better assist you, could you please provide more details about the issue you're facing? Specifically, what exactly is not working properly in the left panel? Are you seeing any error messages or unexpected behavior? Additionally, if you have any screenshots or additional information, please share them so that I can better understand the problem.
In the meantime, you can try a few troubleshooting steps:

Clear your browser cache and try accessing the documentation again.
Try accessing the documentation from a different browser or device to see if the issue persists.
Check if there are any browser extensions or plugins that might be interfering with the CSS rendering.
If the issue persists, please provide more information so that I can further assist you in resolving the problem.

This response is meant to be helpful and save users time. It is not meant to be a precise solution.
Please leave a 👍 if this is helpful and 👎 if it is irrelevant


Repack Rust library into framework instead of dylib for TestFlight

Fixes #52.
(This just uses hardcoded Info.plist templates: is there a better way? Or should we switch to static libraries instead?)

Didn't realize this was moved out of WIP, oops. I'll ho ahead and merge tho, can always clean things up later even if we don't like the plist stuff now.


Refactor mapDispatchToProps in containers to have more concise code

 Issue by evansiroky
Thursday May 31, 2018 at 21:26 GMT
Originally opened as https://github.com/catalogueglobal/datatools-ui/issues/182

The current code style in the mapDispatchToProps variable in containers is very verbose and could be refactored to consist of just an object.

[ ] admin
[ ] alerts
[ ] common
[ ] editor
[ ] gtfs
[ ] gtfsplus
[ ] manager
[ ] public
[ ] signs

 Comment by evansiroky
Monday Nov 05, 2018 at 19:33 GMT

Closing as this is being done in #246.


Option to turn off the non-consecutive sections check

By default splat checks for sections being out of order (a data section starting after the data sections have ended, like between thr rodata sections), which is useful most of the time, but can be very problematic when the original ROM is actually layed out that way.
splat's linker script generation can't represent this layout either because it enforces same link-type sections to be grouped together.
To support this kind of ROMs (like sf64) this PR adds the following:

The ability to disable the non-consecutive sections check via the splat option check_consecutive_segment_types: False
Two new segment types that can express that a section type should be placed on a different link section group data_within_rodata (data placed between rodata sections) and rodata_within_data (rodata placed between data sections)

The way splat was generating linker scripts, it was not possible to do this before, even via custom extension segments. This exposes the ability for custom segments to create this kind of weird-ordered sections

As a reference OoT has a similar issue with a specific file and the solution was something similar
https://github.com/zeldaret/oot/blob/a20163c6abf7700c432c711b03532cc4ad8d198a/spec#L523
    include "build/src/code/__osMemmove.o"
    include_data_with_rodata "build/src/code/z_message_PAL.o"
    include "build/src/code/z_game_over.o"

I'm not sure how else we could address this kind of issue. Maybe allow to use an special option for the segment in the yaml using the dictionary syntax? Something like this?
- { start: 0xA00, type: data,  name: file3, link_order: rodata }

I'm not sure if it is better because it stands out even more saying "this entry is weird"


[ISSUE] list_static_ips()

Description
I am using the list_static_ips() function, but it only returns a maximum of 1802 lines, which results in some static IPs being omitted from the response. I attempted to use the ip_address=ip_address keyword argument to filter the output, but the function still returns the same result.
Reproduction
zia = initialize_zia_client()
zscaler_static_ips = zia.traffic.list_static_ips(ip_address=ip_address)
with open('static_ips.json', 'w') as f:
f.write(json.dumps(zscaler_static_ips, indent=4))
Expected behavior
I expect either to receive all the static IPs configured in the JSON output or, when using the keyword argument, to get a block of data where the specified IP address is included. The expected JSON structure would look like this:
{
"id": id,
"ip_address": ip_address,
"geo_override": false,
"latitude": x,
"longitude": x,
"city": {
"id": id,
"name": "name"
},
"routable_ip": true,
"last_modification_time": last_modification_time,
"last_modified_by": {
"id": id,
"name": "name"
},
"comment": "comment"
}

Found an endpoint in the libary:
zia = initialize_zia_client()
Define the path for the static IPs endpoint
path = "staticIP"
Fetch paginated data
zscaler_static_ips, error_message = zia.get_paginated_data(path=path, data_key_name="list", data_per_page=100)
if error_message:
print(f"Error fetching data: {error_message}")
else:
# Write the entire response to the JSON file
with open('static_ips.json', 'w') as f:
f.write(json.dumps(zscaler_static_ips, indent=4))


when a file is copied to itself, it becomes zero size

Fixes #6497

Given the comment https://github.com/sbt/sbt/issues/6497#issuecomment-841738956, I am guessing it's ok to close this PR?


Shrinks fail on properties taking an arbitrary array and two smap arbitraries

A test written in the manner described in the title of this bug will fail to run shrinks properly, attempting to run an array shrink on non-array arguments. That probably sounds confusing, so this is best explained by running mocha on a gist: https://gist.github.com/matthewleon/a205970ce3cefa15f08a
mlg-ell:verifytest mattleon$ mocha

  test with arbitrary array and two smapped arbitrary params
{ '0':
   [ { [Function] smap: [Function: shrinkProtoIsoMap] },
     { [Function] smap: [Function: shrinkProtoIsoMap] },
     { [Function] smap: [Function: shrinkProtoIsoMap] } ],
  '1': [ [ 4, 2, 17 ], 21, 15 ] }
    1) does not shrink

  0 passing (13ms)
  1 failing

  1) test with arbitrary array and two smapped arbitrary params does not shrink:
     AssertionError: shrinkArrayImpl() expects array, got: 21
      at /Users/mattleon/proj/verifytest/node_modules/jsverify/lib/shrink.js:154:7
      at /Users/mattleon/proj/verifytest/node_modules/jsverify/lib/shrink.js:70:21
      at /Users/mattleon/proj/verifytest/node_modules/jsverify/lib/shrink.js:28:12
      at /Users/mattleon/proj/verifytest/node_modules/jsverify/lib/shrink.js:71:21
      at /Users/mattleon/proj/verifytest/node_modules/jsverify/lib/shrink.js:28:12
      at Object.curriedNInstance [as curried2] (/Users/mattleon/proj/verifytest/node_modules/jsverify/lib/utils.js:110:14)
      at Object.shrinkTuple [as tuple] (/Users/mattleon/proj/verifytest/node_modules/jsverify/lib/shrink.js:148:16)
      at shrinkResult (/Users/mattleon/proj/verifytest/node_modules/jsverify/lib/jsverify.js:122:25)
      at /Users/mattleon/proj/verifytest/node_modules/jsverify/lib/jsverify.js:204:14
      at Object.bind (/Users/mattleon/proj/verifytest/node_modules/jsverify/lib/functor.js:55:12)
      at test (/Users/mattleon/proj/verifytest/node_modules/jsverify/lib/jsverify.js:183:20)
      at /Users/mattleon/proj/verifytest/node_modules/jsverify/lib/jsverify.js:210:13
      at loop (/Users/mattleon/proj/verifytest/node_modules/jsverify/lib/jsverify.js:278:13)
      at check (/Users/mattleon/proj/verifytest/node_modules/jsverify/lib/jsverify.js:293:22)
      at checkThrow (/Users/mattleon/proj/verifytest/node_modules/jsverify/lib/jsverify.js:315:22)
      at Context.<anonymous> (/Users/mattleon/proj/verifytest/node_modules/jsverify/lib/jsverify.js:354:14)
      at callFn (/usr/local/lib/node_modules/mocha/lib/runnable.js:251:21)
      at Test.Runnable.run (/usr/local/lib/node_modules/mocha/lib/runnable.js:244:7)
      at Runner.runTest (/usr/local/lib/node_modules/mocha/lib/runner.js:374:10)
      at /usr/local/lib/node_modules/mocha/lib/runner.js:452:12
      at next (/usr/local/lib/node_modules/mocha/lib/runner.js:299:14)
      at /usr/local/lib/node_modules/mocha/lib/runner.js:309:7
      at next (/usr/local/lib/node_modules/mocha/lib/runner.js:248:23)
      at Immediate._onImmediate (/usr/local/lib/node_modules/mocha/lib/runner.js:276:5)
      at processImmediate [as _immediateCallback] (timers.js:358:17)

I succeed to find a much smaller failing case. Shrink for tuple seems to be broken.