Remove request Migrate to superagent && Fix CI

This PR intends to fully remove request from the codebase, as it's deprecated, and no longer receiving updates.
This starts by removing request from ./src/request.js which is the file all others use to preform any network requests, afterwards hopefully removing request from the downloading node scripts should prove much easier. But as tests can't run on Windows yet, I'll have to rely on CI to determine success in these changes, other than manual testing.

We really need to figure out our testing situation. I was initially excited seeing green CI, but on closer inspection, the amount of passed tests shown as dots, does not match the amount we expect to test. Nor is there any kind of summary for how many tests have passed, like there should be. These tests are failing somewhere, and with our testing situation eating any output, there's no way to know where or how many. Most worrisome of all, this is reported as passed tests. But something is broken.

So on this, I've done a lot of investigating what's going on with our tests. And I hate to say, I think it's a jasmine-focused issue, otherwise something we can't fix in this repo. I'm seeing lots of reports from jasmine-node (Which jasmine-focused uses under the hood) of it failing to capture any stacktrace or errors when requests using request fail, which I'm assuming transfer to superagent as well, since it's intended to be the direct replacement.
But at the very least, I've found a way locally to discover what's going on. Although a bit troublesome.
To get actually logs from these failed tests, you'll need to add the following snippet to the top of the file: ./node_modules/jasmine-node/lib/jasmine-node/cli.js With the snippet being:
process.on("uncaughtException", (err) => {
  fs.writeFileSync(`${__dirname}/log.txt`, JSON.stringify(err) + "\n", { encoding: "utf8", flag: "a+"});
  fs.writeFileSync(`${__dirname}/log.txt`, JSON.stringify(err.stack) + "\n", { encoding: "utf8", flag: "a+"});
});

Once you run your tests, and if they are failing without any output like seen here, a log.txt file will be created within ./node_modules/jasmine-node/lib/jasmine-node/log.txt where you can view the output of what's going on. It's a bit ugly, but quickly cleaning it up you can see what's failing.
Which for reference, in this current PR, here's the output:

This PR Output
TypeError [ERR_INVALID_ARG_TYPE] [ERR_INVALID_ARG_TYPE]:
	The \"path\" argument must be of type string or an instance of Buffer or URL.
	Received null\n    at readFile (node:fs:351:10)\n    at go$readFile
	(D:\\Documents\\ppm\\node_modules\\npm\\node_modules\\graceful-fs\\graceful-fs.js:118:14)\n
	at Proxy.readFile (D:\\Documents\\ppm\\node_modules\\npm\\node_modules\\graceful-fs\\graceful-fs.js:115:12)\n
	at Object.readFile (D:\\Documents\\ppm\\node_modules\\season\\lib\\cson.js:195:17)\n
	at D:\\Documents\\ppm\\src\\install.js:590:21\n
	at iteratee (D:\\Documents\\ppm\\src\\install.js:621:53)\n
	at D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:1959:13\n
	at replenish (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:446:21)\n
	at iterateeCallback (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:430:21)\n
	at D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:327:20\n
	at D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:1961:17\n
	at D:\\Documents\\ppm\\src\\install.js:585:77\n
	at wrapper (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:271:20)\n
	at next (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:5795:24)\n
	at D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:327:20\n
	at D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:3681:19\n
	at wrapper (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:271:20)\n
	at replenish (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:441:29)\n
	at D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:451:13\n
	at eachOfLimit$1 (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:477:34)\n
	at awaitable (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:211:32)\n
	at eachOfSeries (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:813:16)\n
	at awaitable (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:211:32)\n
	at D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:3673:9\n
	at awaitable (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:211:32)\n
	at Object.series (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:4910:16)\n
	at Install.installPackageDependencies (D:\\Documents\\ppm\\src\\install.js:387:20)\n
	at D:\\Documents\\ppm\\src\\install.js:394:38\n
	at nextTask (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:5789:27)\n
	at next (D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:5797:13)\n
	at D:\\Documents\\ppm\\node_modules\\async\\dist\\async.js:327:20\n
	at Install.logCommandResults (D:\\Documents\\ppm\\src\\command.js:90:14)\n
	at D:\\Documents\\ppm\\src\\install.js:181:23\n
	at ChildProcess.onChildExit (D:\\Documents\\ppm\\src\\command.js:45:48)\n
	at ChildProcess.emit (node:events:365:28)\n    at maybeClose (node:internal/child_process:1067:16)\n
	at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)\n

So on this one, as you can see CI was troublesome. I have found a way around the issue of the jasmine-focused straight up crashing reporting nothing as to what went wrong in the tests, and seems to be the case with many different exceptions that might occur. Since I saw them here and over on #88
So with that in mind I've added a fix to the CI here as well. While a bit verbose, it essentially preforms the duties that are reserved for the main file of jasmine-node. Meaning basically the whole main file has been copy pasted into our scripts. Which while normally would be very risky, I think is safe enough since jasmine-node hasn't seen in a commit in 4 years, so I'm not worried about that. But otherwise it does successfully give us output. So I'll leave those changes in here, since they were essentially to getting this PR up off the ground.
Once this is merged then we can go ahead and use these advances in CI to resolve the issues being seen by #88

Also an edit, the single failing windows test is not the fault of this package. And is resolved in #86

@DeeDeeG Thanks for taking a look at this one. I know there's a lot of changes in here.
But as this change isn't really dependent on much, except maybe it's nice to have the CI changes available, overall this one can wait, so it'd be fine to wait until a proper review can occur. Otherwise if we want to merge as as, I'm also totally down for that as well.
But on your notes about proxies, worrying to know there's no testing for it. I will say, I'm not an expert in that field, so my changes interacting with proxies, is mostly straight out of docs for the services we use.

I never ended up properly reviewing this in ~2 weeks, but I would be comfortable merging as per my lite-approve/comment above.
That said, I'll point out Codacy has some actually interesting suggestions here and there, if you ignore all the whitespace-only suggestions and Codacy apparently preferring double-quote marks " for strings, rather than single-quote marks ', for who knows what reason (I prefer the single-quote marks myself???).
Anything else you'd want to see done with this? Or should we go for it and merge this?
(Also, sorry some recent PR's have made merge conflicts in the yarn.lock. I think yarn install can handle merge conflict markers and fix the conflict itself??)

@DeeDeeG I appreciate you giving this PR some attention.
Although looking at Codacy, I'm personally not seeing anything super motivating unless I've just missed it.
Really seems we should probably get a codacy config file in this repo to start ignoring some of these pointless rules and warnings it's trying to enforce.
Beyond that, other than fixing the merge conflict I'm still confident in this PR, if we think it's good to go.

@confused-Techie the "var defined but never used" stuff seemed the most possibly interesting unless it was misinterpreting the point of those vars. (Ctrl + F "never used" on the Codacy, since there's so much whitespace and quote mark suggestions to ignore.)
And there's one about == vs ===, not that that's way important TBH.
But I honestly leave it to your discretion, since I should've brought these up sooner in review if they were important, this has been delayed quite a bit already, so it doesn't seem super fair to hold it up on tiny things like this.

@DeeDeeG I've gone ahead and addressed really only one of the warnings.
The main reason being, is a few of them are coming from the bundled-node-version.js file, which is a direct copy of the jasmine test runner file we use.
And I'd really rather not mess with that in unknown ways tbh. So if we aren't too concerned about it, may be best to leave it alone.
But otherwise, I've gone ahead and resolved the conflicts, and updated the yarn.lock file.
But no worries about this one taking some time, it's not the most urgent PR. But hopefully we are good to go now, I really do appreciate you taking a look!

One of those "weird mysteries of CI". For only the NodeJS 18.x runs... The yarn install step says something weird about node-gyp...

info This package requires node-gyp, which is not currently installed. Yarn will attempt to automatically install it. If this fails, you can run "yarn global add node-gyp" to manually install it.

And it does install node-gyp (why does this even happen anyway?) and then... yarn doesn't run the repo's postinstall script???? For some reason?
So, there is no ./bin/node and the test step fails immediately after.
?????????????????????????
This doesn't happen for me locally. I have no idea what is going on with @actions/setup-node's stuff with latest NodeJS 18 right now. But this feels like very not related to this PR. I guess if I can reproduce the same CI failure on master branch, then it's definitely not this PR's fault and I'll be a re-approve again...
WTF GitHub Actions?
I don't even.

@DeeDeeG Yeah this makes no sense. Unless it's some issue with the changes to node-gyp that's been added when I updated this branch from main.
But I would've expected we would see this on that original PR.
But tried rerunning, ensured we don't have any type of cache for our runners, but seems to consistently fail here.
 Although, to be fair I'm not on Node 18 locally. So may need to install that and try again, but how weird.

Yeah, it happens on master branch, too. I suspect this will blow over without our doing anything in our repo.
FWIW, some Node+npm versions changed since 5 days ago when master branch CI last ran..., in terms of what @actions/setup-node is installing for Node 18.x...:
Before (working):
  node: v18.17.1
  npm: 9.6.7
  yarn: 1.22.19

After (buggy):
  node: v18.18.0
  npm: 9.8.1
  yarn: 1.22.19

I installed this version of node (v18.18.0) and npm (9.8.1) locally on macOS, and everything works fine. I seriously don't get it.
But the issue can reproduce on master branch, so it's not an issue with this PR. Just a weird CI thing. Hope it goes away on its own...

@DeeDeeG Thanks a ton for taking such a good look at this, and especially confirming this failure isn't the fault of this PR.
Suppose in the short term we could always disable testing on the newer node version, as it's meant really to warn us of things breaking, since we don't actually use anything other than 16 within Pulsar right now. Although, this does maybe indicate something breaking, but I'm very much hoping you are right, in that this will just go away on it's own.
But I'm very much on board with using these changes to see if we can finally enable, and fix Windows tests, as that would be quite awesome!
But with your approval, I'll happily merge this one, and hopefully soon take a look at running some Windows tests!


[Enhancement] Useful wrappers for common operations

The file psi4OptionsTools.cmake within the Psi4 project defines several general-purpose wrappers for common CMake operations. Possibly consider incorporating those in Autocmake?

Thanks! These look very useful but we need to make sure that this is OK license and copyright-wise. Unfortunately we cannot take GPL code into BSD without asking.

Yeah, sure. I forgot to add that to the description!

We might also discuss whether BSD is good for us. But that is for another thread.


CASS-1906 Backup secondary index files

@mattl-netflix Rejecting this PR with following issues-

SnapshotMetaTask (new backup system) is not changed in this PR.
Incremental path will upload index files at the wrong location (inside CF folder) due to this - https://github.com/Netflix/Priam/blob/3.11/priam/src/main/java/com/netflix/priam/backup/AbstractBackupPath.java#L94
We only parse columnfamily and keyspace but never name of the index (change in C* 3.x from 2.x).
This is where we need to start making changes where we create another entry for indexes.
Restore path will fail due to above issue.
Any backup will get corrupt as file names of column family could clash with index file names. We need to create that distinction everywhere.


[Core][minor] remove unused visitedStages in DAGScheduler.stageDependsOn

We define and update visitedStages in DAGScheduler.stageDependsOn, but never read it. So we can safely remove it.

Can one of the admins verify this patch?

ok to test

LGTM, it is never read

Test build #28868 has started for   PR 5086 at commit 24663ea.

This patch merges cleanly.

Test build #28868 has finished for   PR 5086 at commit 24663ea.

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

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

LGTM, too; it looks like was never read, even in older versions of the code.


Android client websocket library

Client with websockets transport for android
I created a client for android

This is cool!


Document the CI pipeline

Describe which sets of tests are being run, along with which linters are run. The document should also indicate how to debug CI failures.

This documentation should also include information about the Jenkins jobs, which run K8s community tests, e.g. which tests are run and on what kind of K8s cluster.


Strange noise when onSessionClosed is fired

When one peer leaves the video chat, the second one hears a permanent strange noise. I've just tried to stop all media elements but the loud noise is still there. I've tested it on Chrome (Android).

Okay, the problem can be fixed when setting
videoConnection.privileges = {
canStopRemoteStream: true
};

Okay, the problem still happens sometimes. Any idea what is causing it?

A solution can be:
connection.setDefaultEventsForMediaElement = false;

Ref: http://www.rtcmulticonnection.org/docs/setDefaultEventsForMediaElement/

@muaz-khan: Unfortunately, it isn't working. I still get a constants strange noise on the "guest" device, when the initiator leaves. At the moment, this is how I handle leaving the video chat:
this.videoConnection.onSessionClosed = function (e) {

  self.disconnect();
};

this.videoConnection.ondisconnected = function (e) {

    self.disconnect();
};

this.videoConnection.onleave = function (event) {

    self.disconnect();

}

this.disconnect = function () {

this.videoConnection.streams.stop();
this.videoConnection.close();
this.videoConnection.drop();
//this.videoConnection.refresh();
$("#videoMe").attr("src", "");
$("#videoOther").attr("src", "");
    $("#videoMe").get(0).pause();
    $("#videoOther").get(0).pause();

    $("video").remove();

     this.videoConnection = {};
    videoObj = {};

window.setTimeout(function () {
Router.go('dashboard');
}, 1000) //Meteor Router...
}

The "disconnect()" fires on both sites, but only the "guest" get's a strange noise when the connection/stream stop.


Improving the DataBroker API

Let's discuss how we might streamline the databroker API for common use cases. I think we can do this without breaking the existing API.
Having now seen many notebooks and IPython command histories in the wild, here are the problems I see with our first attempt at the design:

People are loading image data when all they needed was scalars (e.g., image stats) at great cost in performance.
The sequence of commands to get a simple table -- a DataFrame -- is too verbose.
The StepScan interface, meant to address (2), is too limiting. For example, there is no way to turn off filestore when all you wanted was some scalars.
The dual role of db as both a thing that gets headers and a module-like thing with functions is muddy. Personally I find it a little weird to explain, and it's not a pattern I have seen elsewhere. (As it happens, it's my own design, so I'm criticizing it with impunity.)

Here is my rough proposal to kick off discussion. I would give more weight to any opinions from @klauer, @cmazzoli, @ambarb, @afluerasu, @yugangzhang, @pavoljuhas, @ordirules and any others who have actually used this thing at a beamline.
Load Data into DataFrame
Instead of StepScan, something like this would let us build in more flexibility.
from datapotal import DataBroker as db, get_events, make_df
header = db[123]
make_df(header)

This would also work on data from multiple scans.
headers = db[-10:]  # last ten scans
make_df(headers)

To be clear, that last line is an alias for this mouthful: DataMuxer.from_events(get_events(header)).to_sparse_dataframe().
But, I hear you say, StepScan does the above in just one line! The payoff of separating header look-up from DataFrame construction is much better performance in many cases. Behold:
Load Select Fields into DataFrame
from datapotal import make_df
header = db[123]
make_df(header, ['det1', 'det2', 'motor3'])  # only loads filestore data as needed

Load Images into a Lazy-Loading Iterable
I think the image-loading API we have is actually fine, but it needs to be documented and advertised. It is not widely used.
from dataportal import Images
header = db[123]
imgs = Images(header, 'det1')

Search for headers when scan ids / uids are not known
Currently, we have db.find_headers, which is both verbose and somewhat odd, as I said in (4) above.
Instead, we might simply make db callable, so that db.find_headers(owner='dallan') becomes db(owner='dallan').
In summary, db becomes an object that one does one thing: it looks up headers. You can slice db[] and call db(), and that's it. The methods db.fetch_events and db.find_headers can be retired, replaced by get_events (a top-level function) and db() respectively. I see no reason to actually remove these things and break existing code, but we can stop documenting them.
Let the Debate Commence!

Are there other important workflows not addressed here?
Is this an improved compromise between verbosity/flexibility? Can you think of a better one?
Let's save the inevitable debate about naming things for the end.

I have one suggestion:

Some detectors, like CHX currently used Eiger, save h5 files containing lots of useful parameters, such as wavelength, detector distance, beam center, et.al.   We  added these parameters to eiger class and  updated eiger.py in
https://github.com/yugangzhang/chxtools/blob/master/chxtools/pims_readers/eiger.py.
It would be nice to read all these info from the headers or your make_df.

@yugangzhang All of that data should be going into meta-data store so that it is accessible/searchable .

I know. It will be convenient for users that we can incorporate these information into make_df or other functions.  But that (make_df) function should not read the image data.

I am fine with any storage method so long as the tables describing the motors or other scalars may easily be associated with their img/raw data via some unique identifier. This would allow for a two-way access (i.e. if I have the img sequence, I can get the dataframes for the motors, or vice versa without much extra work.)
A two step process makes sense for the retrieval of the data. I think it is a good idea to force the user to understand the abstraction layers to some level without having to do more work than follow a manual and this would do so. Forcing two functions to retrieve the expt data and image data would help.
@tacaswell and @yugangzhang bring good points. I would like to add that I personally prefer that any parameter describing the expt should be kept as close to the source as possible rather than a searchable grab bag of all data in one header. I.e. it makes more sense to keep parameters such as an exposure time in the EIGER header file (which only matters for the EIGER) as opposed to some lower level dataframe describing the motors. So I would be more a proponent of a tree like structure of searchable bags.
Some other more fuzzy parameters would also also have to be decided on a case by case basis. For example the wavelength and beam center. The former probably should be saved in both db and eiger (because eiger will process data differently for different wavelengths, like wavelength dependent flatfield correction etc. Since eiger can independently change this parameter, it might accidentally not match the beamline). The latter should probably be saved in EIGER for the sake of portability and ease of self-contained data analysis.
So I'm basically saying:

Separation of reading different data sets should be forced upon the user by independent calls where it helps the user better understand the abstraction layers without much work.
I think some data should not be stored into the databroker, like exposure time for EIGER.

What do you think? You guys see things on a much larger scale than I am seeing so I am open to any changes.
Thanks, the eiger reader and the pims readers work great. :-)

These are some good points. I also realized that some quantities (what @ordirules
calls 'fuzzy parameters') are actually not associated with any EPICS PV's and hence are not recorded in any searchable database. The beam center - X,Y coodinates on the Eiger - and detector distance are such an example. I'm not even sure of we have 'wavelength' or 'bandwidth' PVs at this moment ...
In any case, I think that the right philosophy is the one we were following so far, where all the metadata is in the metadata store. If I'm interested in knowing the detector distance, I may actually think about doing it in an automatic way (e.g. reading an encoder) and this will automatically result in the associated PV being available.
The problem is that accessing such metadata associated with e.g. images (or scalars) that we opened following some of the simplified ways described above by @danielballan is not necessarily very simple or clear. I think that as a part of this discussion focused on improving the databroker API and 'standardizing' the methods we use to access data, we should included also accessing the metadata.

@afluerasu and @ordirules: Yes, the so-called "fuzzy parameters" that are not recorded on PVs should be recorded in metadatastore. This can be done in a persistent way (set a parameter once, and it gets saved on all future scans until it's updated) or on a scan-by-scan basis. We can talk about how to do this before the beam comes back. I agree with @ordirules point that we should structure where things are stored, not just put everything in a flat "bucket."
A related issue is providing nice access to channel archiver data. We have a way to do this in the works.

Thanks for the feedback, everyone. Updates have been made. The new API is faster and simpler and close to what I presented here. I'll post a link when the documentation is ready (before the beam comes back).

Great - looking forward to these changes.


Null parameter from container is removed when injected in controller.

Laravel Version: 7.0.2
PHP Version: 7.4.2

Description:
Hi,
I would like to inject a service or null in a controller method.
For now, a null value coming from the container is not spliced in the method parameters. So the next argument value are provided to it, or ArgumentCountError is thrown.
It's coming from \Illuminate\Routing\RouteDependencyResolverTrait::resolveMethodDependencies:
https://github.com/laravel/framework/blob/1c5caccad9dc49c9233610d1c92a5a7e46ecaeba/src/Illuminate/Routing/RouteDependencyResolverTrait.php#L49-L56
In my opinion, we should accept null value as standard value, whether they have default value or not, the type-hint will raise an error in the method if the type is not ok.
See the actual errors:

https://flareapp.io/share/bP9OdL5Q
https://flareapp.io/share/omwgpomE

Steps To Reproduce:
class AppServiceProvider extends ServiceProvider
{
    public function register()
    {
        $this->app->bind(Service::class, fn() => null);
    }

    public function boot()
    {
        Route::get('/foo/{id}', function (?Service $service, string $id) {
            // Argument 1 passed ... must be an instance of Service or null, string given.
        });

        Route::get('/not-working', function (?Service $service) {
            // Too few arguments ... 0 passed ... and exactly 1 expected.
        });

        Route::get('/working', function (?Service $service = null) {
            // Working
        });
    }
}

I can propose a pull request with pleasure if you want to.
Thanks,
Matt'

Hey Mathieu, I'm gonna move this to the ideas repo instead. Feel free to attempt a pr if you want.


Plugin adds one finish when opening a map on MP4

Issue
When opening a map on Trackmania 2 / MP4, the plugin will add a finish to the session total when loading a map, despite not starting a run
Image

Explanation
When you open a map, MP4 seems to set ScriptAPI.RaceState to CTrackManiaPlayer::ERaceState::Finished for some reason, which can be confirmed by printing RaceState on the console
[   ScriptRuntime] [  LOG] [17:25:09] [GrindingStats]  Read finishes 11 resets 25 time 542476 respawns 0
# not including JSON since it's useless here
[   ScriptRuntime] [  LOG] [17:25:09] [GrindingStats]  Finished
[   ScriptRuntime] [  LOG] [17:25:11] [GrindingStats]  BeforeStart
[   ScriptRuntime] [  LOG] [17:25:16] [GrindingStats]  Running

fixed in cd4f211


[IR] Support integer subbyte

support sub byte integers in Hidet

a = register_tensor("int4b", [4, 4])
b = a[0, 2]
a[2, 2] = int4b(-5)
ptr = &a[0, 0]
ptr = ptr + 8

Hi @xiaocenxiaocen, let me know when the PR is ready to be reviewed, thanks!

Hi @xiaocenxiaocen, let me know when the PR is ready to be reviewed, thanks!

Sure. I will work on this in this week and the next week.

Hi, @yaoyaoding. This PR is ready for review. Please take a look at it. Thanks.

hidet-ci launch

$hidet-ci launch

$hidet-ci launch

$hidet-ci launch


Indexing issue null folder

On some folders, the SILS folder shows 1 object (https://cdr.lib.unc.edu/record?id=uuid%3Abbab5e33-c1fe-441c-a0a1-2182e0065bee and https://cdr.lib.unc.edu/search?facets=path%3A2%2Cuuid%3Ac816aeea-c651-4554-b8bc-0b4188d11531%2C3), on one view it doesn't (https://cdr.lib.unc.edu/search?action=setFacet%3Apath%2C"2%2Cuuid%3Ac816aeea-c651-4554-b8bc-0b4188d11531"|setFacet%3Apath%2C"1%2Cuuid%3Abbab5e33-c1fe-441c-a0a1-2182e0065bee"&sort=default&sortOrder=&facets=path:2,uuid:c816aeea-c651-4554-b8bc-0b4188d11531,3&rows=20)

More issues here - RLA has some folders faceted as collections that are (see, https://cdr.lib.unc.edu/search?action=setFacetLimit%3Acollection%2C20&sort=default&sortOrder=&facets=path:1,uuid:8ae56bbc-400e-496d-af4b-3c585e20dba1&rows=20) - log in and check it out. 0501-1000, X6501-X7000, X5501-X6000, X6001-X6500, 21001-21500 are all showing as containing one object (eventhough they should each have 500 and are faceting as collection folders on the left hand nav bar.

Here's another one of these indexing issues in the Masters Papers collection, https://cdr.lib.unc.edu/search?action=setFacet%3Apath%2C"1%2Cuuid%3A2f5733dc-e5d6-4822-ab7f-8832ef66cec8"|resetNav%3Asearch&sort=default&sortOrder=&types=Collection&facetSelect=subject,format,language,path,creatorType,department&rows=10
SILS is indexed as  collection containing one file under the collection facet even though it isn't a collection and the SILS subfolder has 1056 files.


Don't update the map size on 'movestart'

On every movestart, Map.updateSize() is called. This is not necessary and is an expensive operation: the browser has to force a reflow.
The call was introduce in 160722a1 apparently to reset this.events.element.offsets but this variable do not exists anymore.

Please merge. Thank you!


Folder tree preview

Not sure how it would fit into the interface as it is not just syntax highlighting, but I will leave it to you to decide.
I often need to share an idea of a folder/file structure. I would expect to be able to type in an indentation-based structure and appreciate a nice PNG/SVG output with generic folder and file icons in front of the names
A + would be rendered as a folder icon, - would stand for a file.
+ Folder 1
  + Folder 1.1 (has no children)
  - File 1.2
  - File 1.3
  + Folder 1.4 (has children)
    - Folder 1.4.1
  - File 1.5
+ Folder 2
- File 3

@moniuch are you using a linux based operating system? The tree command creates a really nice structure, and you can paste that right into Carbon.

I am on Mac. I have seen recommendations for tree and for mddir, but from what I understood they just translate contents of an existing directory into md/ASCII text. This is not what I am after. My use case is when I need to quickly illustrate an example tree view off the top of my head (without first creating a dir). So the input would be my free text and the desired output would be an SVG/PNG file, just like the current code images.

If that is the case, can you just type it directly into Carbon? Some of the existing language highlights look good already:

Or something like this?
.
├── _config.yml
├── _drafts
 |   ├── begin-with-the-crazy-ideas.textile
 |   └── on-simplicity-in-technology.markdown
├── _includes
 |   ├── footer.html
 |   └── header.html
├── _layouts
 |   ├── default.html
 |   └── post.html
├── _posts
 |   ├── 2007-10-29-why-every-programmer-should-play-nethack.textile
 |   └── 2009-04-26-barcamp-boston-4-roundup.textile
├── _data
 |   └── members.yml
├── _site
└── index.html

@moniuch does this work for you?

I can live with it. Thanks for the hint.


Root state does not make it easy to interact with sub states

Currently there is no easy way to reference sub states. The obvious solution to me is to use a path based system. So rather than get_state(name_of_sub_state) you'll use get_state(path/to/state). It should be relatively simple to implement but considering the slow pace of development this can be put on hold for later.

I didn't even know that it was possible to have sub states. How is it done ? Is it possible because FrayRootState can contains other FrayRootState or am I missing something? How is the transition from State_A to State_B/SubState_A handled ?
I expect something like this where sub states are some kind of tree-like structure that you need to traverse.
Something like this:
State_A to State_B/SubState_A

State_A EXIT
State_B ENTER
State_B/SubState_A ENTER

And going back to State_A
State_B/SubState_A to State_A

State_B/SubState_A EXIT
State_B EXIT
State_A ENTER

I didn't even know that it was possible to have sub states. How is it done ? Is it possible because FrayRootState can contains other FrayRootState or am I missing something?

You got it, that is correct. FrayRootState used to be called FrayStateMachineState for that reason.

I expect something like this where sub states are some kind of tree-like structure that you need to traverse.

Your description is how it should work. But admittedly while the structure is there it hasn't been adequately tested yet so it's possible there are issues in the order of events.


Set flag to fix postgres volume permissions

We should set the volumePermissions.enabled=true flag when installing the postgres for gitea.  This would fix potential issues with hostpath and nfs volumes.
See: https://github.com/rancher-sandbox/rancher-desktop/issues/502#issuecomment-898563507

Do we have a reported case why this is needed ? How can we test that this actually fixes a problem ?

Yes, I can no longer install on Rancher Desktop and Rob hit the same issue in: https://github.com/epinio/epinio/issues/641
This can be tested by installing the bitnami postgres chart by itself to see the same error.

Then I'd close this as a duplicate of #641 ?!

Closing in favor of #641


Fails to precompile on Apple M1

Running on the sf/apple_silicon_latest branch of Julia, I get this when trying to import:
julia> import CodecLz4
[ Info: Precompiling CodecLz4 [5ba52731-8f18-5e0d-9241-30f10d1ec561]
ERROR: LoadError: UndefVarError: liblz4 not defined
Stacktrace:
 [1] include
   @ ./Base.jl:386 [inlined]
 [2] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt64}}, source::Nothing)
   @ Base ./loading.jl:1213
 [3] top-level scope
   @ none:1
 [4] eval
   @ ./boot.jl:369 [inlined]
 [5] eval(x::Expr)
   @ Base.MainInclude ./client.jl:453
 [6] top-level scope
   @ none:1
in expression starting at /Users/me/.julia/packages/CodecLz4/2JFgC/src/CodecLz4.jl:2
ERROR: Failed to precompile CodecLz4 [5ba52731-8f18-5e0d-9241-30f10d1ec561] to /Users/me/.julia/compiled/v1.7/CodecLz4/jl_iZRXpo.
Stacktrace:
 [1] error(s::String)
   @ Base ./error.jl:33

I did install the lz4 library through brew, but I don't think that its finding the library.

The Lz4_jll needs to be updated to be built for experimental platforms before Apple Silicon (aarch64-apple-darwin) support will work here.

Have they been alerted to the issue yet?

Have they been alerted to the issue yet?

There is a plan in place to update BinaryBuilder to include aarch64-apple-darwin in the default platform list and re-build all JLL packages to include the new platforms. This is on going work and unfortunately there isn't an issue at this time to refer to

Works fine now.


Update MediaPipe developer documentation links

The following PR fixes some broken links and updates the doc (documentation moved to  https://developers.google.com/mediapipe as the primary developer documentation site for MediaPipe as of April 3, 2023)

LGTM
(although I don't have permission to approve PRs on this repo, so @droid-girl will have to officially approve this)

Also, can you update the commit message to be more specific? Maybe something like: "Update MediaPipe developer documentation links"

yeah, updating the PR title should be fine. thanks for that!


Error: Cannot connect prisma to postgresql certificate verify failed

Hello,
i created an demo project of prisma2 with connection to postgresql.  It fails on last step with this error:
Error: Could not connect to database: Starting a postgresql pool with 5 connections. [2019-11-28T07:28:14Z ERROR migration_engine] Error opening a TLS connection. error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1924: (self signed certificate)
I get the same result when running prisma2 dev.
Postgresql v.12 running on WLS.
The prisma2 is also run from WLS.

Hi,
Thanks for reporting this but this has been already reported once. So I am going to close this as a duplicate of https://github.com/prisma/prisma2/issues/884
Basically right now our SSL policy in the engine is very strict than other clients. We are planning to loosen it.


i18n: add missing german translations

I'm still not done xd

@TheDevMinerTV TheDevMinerTV requested a review from ImUrX as a code owner

no, github, I, in fact, did not do this.

How could GitHub lie to me

Could you rename "SSID" to the german translation of "Wi-Fi name" please? Most people don't know what SSID means

Should be fixed

Please squash merge.


Load as a link

It would be useful to create webs of linked clj files so that a tutorial could be broken up into pieces (for example).
One way to do this would be to be able to use markdown that created a link that would cause a load of a different file to occur.

Apparently, this is already possible! Try
[Some link](/worksheet.html?filename=src/some_directory/some_other_file.clj)

in Markdown.
The one catch is that, if the Markdown section is set to be editable, you'll have to right click, then select "Open Link in New Tab," as the worksheet will otherwise register the click as you wanting to edit the Markdown, rather than you wanting to follow the link.

Yes, the infrastructure for this is already present. If we were to implement the suggestion of read-only markdown segments in #193 then this would work quite nicely, I'd imagine.

p.s. One possible snag is that, because Gorilla runs in the context of a particular project, it's only really possible to link worksheets like this if they are in the same project. In practice, this probably isn't much of a limitation though.

Same project seems totally fine to me and I'm finding this workable as is right now (and would be extra great with read-only segments). Feel free to close!

OK, will close this on the understanding that it will get better once read-only segments are working :-)


GH-34796: [C++] Add FromTensor, ToTensor and strides methods to FixedShapeTensorArray

Rationale for this change
We want to enable converting Tensors to FixedShapeTensorArrays and the other way around.
What changes are included in this PR?
This adds FromTensor, ToTensor to FixedShapeTensorArrays and strides method to FixedShapeTensorType.
Are these changes tested?
Yes.
Are there any user-facing changes?
This adds FromTensor, ToTensor and strides are user facing methods.

Closes: #34796

In my last review of #8510 before splitting it (https://github.com/apache/arrow/pull/8510#pullrequestreview-1360738892), I still had some comments/questions on the FromTensor/ToTensor implementation. I am assuming that nothing fundamentally changed here (just split off what was at that point in that PR?).
Can you take a look at those comments and respond to them? Especially the comments about the resulting shape of FromTensor (https://github.com/apache/arrow/pull/8510#discussion_r1150406865, https://github.com/apache/arrow/pull/8510#discussion_r1150413305; you answered then that this was resolved because of permutation shape_, but that's no longer the case). It might be that you addressed those comments, but that's hard to see if you don't explicitly explain what you changed.

A change introduced late in #8510 (and then removed) was that ComputeRowMajorStrides is replaced with a general ComputeStrides to calculate strides of permuted tensors which should help matching pytorch behavior:
import torch

def print_strides(shape, permutation):
    permutation2 = [p - 1 for p in permutation[1:]]
    shape2 = shape[1:]
    x = torch.randn(shape).permute(permutation)
    y = torch.randn(shape2).permute(permutation2)
    strides = [z * 8 for z in x.stride()]
    strides2 = [z * 8 for z in y.stride()]

    print("[full tensor] shape:", shape, "permutation:", permutation, "strides:", strides)
    print("[cell tensor] shape:", shape2, "permutation:", permutation2, "strides:", strides2)

shapes = [
    (3, 3, 4),
    (3, 3, 4),
    (3, 4, 3),
    (3, 4, 3),
]
permutations = [
    (0, 1, 2),
    (0, 2, 1),
    (0, 1, 2),
    (0, 2, 1),
]

for shape, permutation in zip(shapes, permutations):
    print_strides(shape, permutation)

[full tensor] shape: (3, 3, 4) permutation: (0, 1, 2) strides: [96, 32, 8]
[cell tensor] shape: (3, 4) permutation: [0, 1] strides: [32, 8]
[full tensor] shape: (3, 3, 4) permutation: (0, 2, 1) strides: [96, 8, 32]
[cell tensor] shape: (3, 4) permutation: [1, 0] strides: [8, 32]
[full tensor] shape: (3, 4, 3) permutation: (0, 1, 2) strides: [96, 24, 8]
[cell tensor] shape: (4, 3) permutation: [0, 1] strides: [24, 8]
[full tensor] shape: (3, 4, 3) permutation: (0, 2, 1) strides: [96, 8, 24]
[cell tensor] shape: (4, 3) permutation: [1, 0] strides: [8, 24]


Test examples

Hi @dicej I attempted to start testing the examples and have run into some issues. With the current codebase, if I run the code in the readme, I get this error:
Error:

Caused by:
    0: error while executing at wasm backtrace:
           0: 0x1c1c10e -<EMAIL_ADDRESS>           1: 0x173ca - wit-component:adapter:wasi_snapshot_preview1!wasi_snapshot_preview1::State::get_environment::hef57c6f7dba7ec20
           2: 0x175e1 - wit-component:adapter:wasi_snapshot_preview1!environ_sizes_get
           3: 0x1c1bc25 - wit-component:shim!adapt-wasi_snapshot_preview1-environ_sizes_get
           4: 0x1b5da81 - libc.so!__wasi_environ_sizes_get
           5: 0x1b5d976 - libc.so!__wasilibc_initialize_environ
           6: 0x1b5f6ef - libc.so!__wasilibc_initialize_environ_eagerly
           7: 0x1b576f7 - libc.so!__wasm_call_ctors
           8: 0x1b57a64 - libc.so!_initialize
           9: 0x1c1b1fd - __init!<wasm function 745>
    1: called trapping stub<EMAIL_ADDRESS>
Since the adapter used for wasi is from Wasmtime 17, I thought that might be the issue, so I am now using the one from the crate wasi-preview1-component-adapter-provider to make sure we were using the latest one (and it makes some things a little simpler anyway)
However, now it seems that the component can't find the files being added for initialization...
Error: ModuleNotFoundError: No module named 'app'

Caused by:
    ModuleNotFoundError: No module named 'app'

Any ideas? I'm a little worried I broke componentize-py with dependency updates for anyone wanting to target wasi worlds... (we are using a custom world at work)
But I guess that is the point of adding these tests

I have traced it to this commit: https://github.com/bytecodealliance/componentize-py/pull/108
Some dependency here broke it, likely wasmtime, but I am not sure.

@benbrandt thanks for investigating and narrowing down the regression.  I'll take a look.

I'm trying incrementing the wasi adapter version as well to minimize the change

I think this might be due to confusion related to WASI 0.2.0 vs. 0.2.1 imports which will require updates to the add_wasi_and_stubs function.  Working on a fix now.

This should fix it: https://github.com/bytecodealliance/componentize-py/pull/120

Awesome. I had a feeling it might have to do with wasi 0.2.x since wasmtime 25 introduced the next version.  Thanks!
I'll rebase after you merge and see if I can push the tests further

@dicej it seems that everything is working on main, but not if I update the adapter file as I am doing here... I'll try upgrading each version of the adapter file to see which one causes the break. but at least main is working again, thanks for the fix

@dicej Ok I added some basic smoke tests of what is in the readmes.
I am not always confident in my bash skills, so if you see anything obvious where this wouldn't catch errors, let me know.
For example, I wasn't sure how best to handle the http proxy or tcp examples, so I am just making sure they build for now.

Also attempted to address https://github.com/bytecodealliance/componentize-py/issues/37

Thanks for doing this, @benbrandt.  I haven't had time yet to do more than skim it, but will review it properly tomorrow.


Inline binding converter fails on null check

I have the following property assignment:
IsEnabled: bind SelectedRule convert (AvailableRuleViewModel item) => item != null
and the error is:

I also tried changing the binding conversion expression to (AvailableRuleViewModel item) => item != null ? true : false but that didn't change anything.

Fixed!
Next NuGet release is planned in a few days, maybe Tuesday or Wednesday. You will actually have to install-package Ammy.WPF since Ammy is on multiple platforms now.
If you want, I can upload fixed version today on MyGet. But it's not tested yet, and I can't guarantee that everything works properly.
Thanks for submitting an issue!


Drop references to clang-pseudo-gen after removal

pseudo was removed from clang-tools-extra in upstream PR https://github.com/llvm/llvm-project/pull/109154
Drop two explicit references in swift and unblock Windows CI

@hjyamauchi @compnerd I think that will fix the Windows CI failures from these PRs:

https://github.com/swiftlang/llvm-project/pull/9416#issuecomment-2417356254
https://github.com/swiftlang/llvm-project/pull/9103#issuecomment-2386688526

@bnbarham Last year you added the CMake option in swift_build_support/products/llvm.py. Do you see any use keep it, now that pseudo was removed? (If unsure I can leave out this half of the patch.)

@swift-ci please test

Do you see any use keep it, now that pseudo was removed? (If unsure I can leave out this half of the patch.)

I would have only added it to fix builds during rebranch, so if it was removed there shouldn't be any reason to keep it 👍

@hjyamauchi All tests have passed and this is ready to land. Can you merge please? Thanks

I'm still a little unsure of what you're trying to do here, but again, next is never going to pass today. We don't keep it building. For LLDB you'll want to target stable/20240723 (which matches rebranch in swift) and then cherry-pick to next (doesn't need to be passing, since again, it never will).

@bnbarham Interesting, thanks for your note. Is that the general approach? Or only for the time until the rebranch is merged?
I would normally assume to go the other way around: land new patches on next and backport them to a stable branch.

As I understand, there's an auto-merger from upstream llvm to the next branch at all times (so that upstream merges will eventually arrive in next.) Most of the time, the development head / tip of tree is the (current)stable/XXXXXXXX and next will be the base for the next stable/XXXXXXXX when the next rebranch happens. We are currently in the process of transitioning from stable/20230725 to stable/20240723 but that hasn't completed yet. If you can wait for the rebranch to happen, then cherrypicking it to stable/20240723 would be sufficient. If you need it immediately, cherrypicking it to both stable/20230725 and stable/20240723 would make sense.

@bnbarham Interesting, thanks for your note. Is that the general approach? Or only for the time until the rebranch is merged?

If the change can be made upstream then the usual approach would be to do that and then cherry-pick to the stable branches. But for Swift-specific LLDB changes (which need to also compile the swift compiler) it's the other way around (stable -> next), as swift's next isn't kept green. CC @adrian-prantl / @JDevlieghere in case I'm giving bad advice there.

/bin/sh: /Users/ec2-user/jenkins/workspace/oss-swift-package-macos/build/buildbot_osx/llvm-macosx-arm64/bin/clang-pseudo-gen: Bad CPU type in executable

Going to revert this patch to unblock CI. https://ci.swift.org/job/oss-swift-package-macos/3546/changes#6437e32e2c6a9b1c7c1b423f7768e678574ea98f

Well, this bot is building the same swift against llvm-project stable/20230725. That cannot work and I didn't know. Sorry for the noise.


Add shweshi/OpenGraph

Thank you for contributing! Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[x] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288)
[x] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

[ ] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of why you think this topic or collection should be curated.

Something that does not neatly fit into the binary options above

[x] My suggested edits are not about an existing topic or collection, or at least not a single one
[x] My suggested edits are not about curating a new topic or collection, or at least not a single one
[x] My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of your proposed changes.

Proposal to add shweshi/OpenGraph a handy package Proudly Made In India.

Hi @shweshi  Thank you for contributing. But, Unfortunately as per contribution guidelines, we restrict self promotion. Thank you!

@krishdevdb understood. Thanks.


#feature; Convert subgraphs that depends on IPFS to using File Data Source

Will be enabled in graph-node's 0.30.0 release

Action Items:

Identify subgraph's that use IPFS


SvgUri does not handle response status code when fetching the resource

Bug
SvgUri component crashes when svg resource request returns a response with status 404.
Environment info
React native info output:
System:
    OS: macOS 10.15.5
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 678.98 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.5.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.5 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3, 29.0.3
      System Images: android-28 | Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.6 AI-192.7<IP_ADDRESS>92135
    Xcode: 11.6/11E708 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_252 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.1 => 0.63.1
  npmGlobalPackages:
    *react-native*: Not Found

Library version: 12.1.0
Steps To Reproduce

import { SvgUri } from "react-native-svg";

Place this <SvgUri uri="https://dev.w3.org/SVG/tools/svgweb/samples.svg" /> in any screen/component

Run the app

Exception in app:

Requested resource response:

Describe what you expected to happen:
SvgUri onError to be triggered and passed callback to be executed.
Suggested Fix
SvgUri Implementation
SvgUri Implementation with response status check:
export function SvgUri(props: UriProps) {
  const { onError = err, uri } = props;
  const [xml, setXml] = useState<string | null>(null);
  useEffect(() => {
    uri
      ? fetch(uri).then((response)=>{
        if(response.ok) {
          return response.text()
        }
        throw new Error(`${response.status} ${response.statusText}`)
      })
          .then(setXml)
          .catch(onError)
      : setXml(null);
  }, [onError, uri]);
  return <SvgXml xml={xml} override={props} />;
}

this is a very necessary feature.  I'm currently also facing an issue where I need to know if the icons can't load/render for any reason so i can swap in some kind of error state icon or something other than just blank UI.

Adding also an isCancelled field could also improve this component to avoid Can't perform a React state update on an unmounted component when the network is slow.
Something like:
export function SvgUri(props: UriProps) {
  const { onError = err, uri } = props;
  const [xml, setXml] = useState<string | null>(null);
  let isCancelled = false;
  useEffect(() => {
    uri
      ? fetch(uri).then((response)=>{
        if(response.ok) {
          return response.text()
        }
        throw new Error(`${response.status} ${response.statusText}`)
      })
          .then(setXml)
          .catch(onError)
      : setXml(null);
     return () => { isCancelled = true }
  }, [onError, uri]);
  return <SvgXml xml={xml} override={props} />;
}

yep I'd also like this kind of thing implemented but the dev is not active on here and is ignoring this repo...

This is an essential fix for this library. I tried to create a patch for patch-package but unfortunately the way this react-native package is deployed via npm patching the xml.tsx file does nothing (because its not compiled on the client).
Any idea how to locally patch it?

Just copy the source code and make your own component

There is the onError prop, although it doesn't return status codes.
 <SvgUri
  width="100%"
  height="100%"
  uri="http://thenewcode.com/assets/images/thumbnails/homer-simpson.svg"
  onError={(error) => {
    // handle error
  }}
/>

onError={(error) => {
// handle error
}}


Use mel watch mode, add React support, update the README

@anmonteiro the last references to bs-platform have been removed now. I ended up having to switch from Parcel to Webpack because it seems like it's just about the only bundler that doesn't blow up due to node_modules/melange being a symlink and/or not having a package.json.

Ah. we should install the package.json, then.

Thank you!

we should install the package.json, then

Oh right, good point! Can't believe I forgot to add that to the readme. A PR for that is on its way.


[Proposition] Add unfolds for types.

I tried to code some isometric landscape generator (using svg) lately, and I got a task to solve: generate list of points (Int, Int).
The core.List module only contained List.range : Int -> Int -> List Int method. And no unfoldr or alike.
So I had to break my stream of thinking of things I want to do and implemented it myself.
My proposition: add unfold{r,l,} for any module describing "sequental container" types like List, Maybe, etc.
For instance, List.unfoldr : (seed -> Maybe (a, seed)) -> seed -> List a.

Please make such suggestions on the mailing list, not here. Also see what the links from process-bot have to say on this.


Rebase to v1.3.4 for OCP 4.10

Simple git merge v1.3.4 worked.
Diff to upstream v1.3.4:
https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/compare/v1.3.4...jsafrane:rebase-v1.3.4
Notice that golang.org/x/oauth2 changes are due to #15.
cc @openshift/storage

/hold
I can see 1.4.0 is being prepared right now, let's wait for couple of days. https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/pull/878

/hold cancel
there is no progress upstream, it may take some time to get a new upstream release.
@openshift/storage PTAL


visual studio code eslint support

Description
The docs here https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md mention that vs code should support the eslint config without doing anything extra
VS Code ESLint plugin automatically detects Create React App's configuration file. So you do not need to create eslintrc.json at the root directory, except when you want to add your own rules. In that case, you should include CRA's config by adding this line:

in practice, with latest versions of everything, i still had to add .eslintrc containing { "extends": "react-app" } in order for the editor to load a config
Expected behavior
VS Code ESLint plugin automatically detects Create React App's configuration file
Actual behavior
VS Code ESLint plugin needs and .eslintrc file to detect any config
Environment
Run these commands in the project folder and fill in their results:
npm ls react-scripts
└──<EMAIL_ADDRESS>node -v
v7.8.0
npm -v
4.2.0

Operating system:
macOS

I am not sure if this is a bug or a lack in documentation or I m just doing something wrong.
If it's the docs i can make a pull request I guess
Cheers

Can we trace this down to any specific VSCode version when this stopped working? It may be a regression on their end.
Otherwise, we may need to update the documentation to reflect this change.

@tzapu vscode doesn't seem to detect eslint configuration for apps created using create-react-app.
I have observed similar behavior in vscode-1.11.2

@Timer @anilreddykatta i noticed this on Version 1.11.1 (1.11.1)
so so far, 1.11.1 & 1.11.2 seem not to be working
cheers

Not working here neither, I'm on  version 1.11.2.

Hi, I maintain the ESLint extension for VS Code and got here due to https://github.com/Microsoft/vscode-eslint/issues/230.
I created a react app using create-react-app my-app and the generated package.json file doesn't contain an eslintConfig property. After adding
  "eslintConfig": {
    "extends": "react-app"
  }

things started to work for me. Is there something I am missing ?

i think the confusing bit is that the docs are saying that it just works, you don't need to add anything, as the eslint extension in vscode auto detects create react app's eslint rules
hope this helps
cheers

To make setup for users easier could the create-react-app generate a corresponding .eslintrc. From all feedback I got it is easier for users to deal with an .eslintrc file than a property in the package.json file.

I don’t think we’ll be creating .eslintrc in the project folder, no. A property in package.json is a supported way to configure ESLint, so we would like to keep using that.

@gaearon
just for a clear clarification
eslintConfig in package.json is just a way to customize eslint in code editor but has nothing to do with eslint warning/error in browser/cli, right?

Yes. In the browser/cli, we hardcode ESLint to use the react-app configuration. However IDEs can’t know about this.
I think it’s fine if we encourage people to create .eslintrc in their project folder if that solves the problem for VSCode. I’m just saying we won’t be generating it by default.

Does this solve the issue?
Can somebody review this PR please?
https://github.com/facebookincubator/create-react-app/pull/2054

this seems like satisfactory solution, it's clear enough, it works, all is good in the world again.
thank you very much

Sounds great. Sorry for the trouble. 😛

Sorry to reopen this, but I am having an issue using eslint with the VSCode plugin using the instructions provided in the create-app docs.
After adding the .eslintrc file, I am getting the following error:
"Failed to load the ESLint library for the document"
I am assuming this is because the eslint plugin is not finding any library in node_modules.  I haven't installed eslint globally either, hence it tries to load eslint from whatever document is open.
Is this something that will only work while running after running 'npm start'?

I've tried both things (.eslintrc in the root and eslintConfig in packages.config) but with the same result: "Cannot find module 'eslint-config-react-app' Referenced from:". New react app, VSC 1.14.1...

adding eslintConfig to package.json works for me

I was facing the same issue described here. However, this had to do with yarn not loading the eslint plugins included in react-scripts deps. So, in other words, there are no ESLint settings when you use yarn as pkg manager. Related issue is #3998.


Add Transaction::base_fee

The transaction base fee is calculated from its metered len, gas limit,
gas size and consensus parameters.
This function is consumed during VM initialization to deduct its maximum
fee from the initial base asset.

This is most likely superseded by checked tx max_fee


Fix typos in rl_deepracer_robomaker_coach_gazebo

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Fixed the typos in PR #715


Fixes #236. Move FindBaselibs up in order

Closes #236
This PR moves the call for FindBaselibs.cmake up in the order of calls. This sets CMAKE_PREFIX_PATH earlier.
Blocking until I can do more tests to make sure.

@tclune What are your thoughts on version for this? I have it as a hotfix, so should this be v3.7.1 or v3.8.0?

I think this is a bugfix and as such should be 3.7.1.


logout capsule wallet on disconnect

Description
Fixes a bug where capsule wallet would not disconnect successfully.
PLEASE NOTE- Checklist must be complete prior to review.
Checklist

[x] Increment the version field in package.json of the package you have made changes in following semantic versioning and using alpha release tagging
[x] Check the box that allows repo maintainers to update this PR
[x] Test locally to make sure this feature/fix works
[x] Run yarn check-all to confirm there are not any associated errors
[x] Confirm this PR passes Circle CI checks
[x] Add or update relevant information in the documentation

Docs Checklist

[x] Include a screenshot of any changes (see docs README on running locally)
[x] Add/update the appropriate package README (if applicable)
[x] Add/update the related module in the docs demo (if applicable)
[x] Add/update the related package in the docs/package.json file (if applicable)

If this PR includes changes to add an injected wallet or SDK wallet module:
Please complete the following using the internal demo package.
To run this demo use the command yarn && yarn dev to get the project running at http://localhost:8080/
Tests with demo app (injected)

[ ] send transaction
[ ] switch chains
[ ] sign message
[ ] sign typed message
[ ] disconnect

Tests with demo app (SDK)

[ ] send transaction
[ ] switch chains
[ ] sign message
[ ] sign typed message
[x] disconnect

NOTE:
I am combining the Fragment fix in with this PR as it is a critical change


Add default and list of supported node version

@soninaren can we add some details here?

Blocked on https://github.com/Azure/Azure-Functions/issues/1137

Closing with  Azure/Azure-Functions#1137 - we now target based off of major version


chore(main): release 0.0.5

:robot: I have created a release beep boop
0.0.5 (2024-06-02)
What's Changed

feat: Add instructions for installing poppler and tesseract by @StanGirard in https://github.com/QuivrHQ/MegaParse/pull/10

Full Changelog: https://github.com/QuivrHQ/MegaParse/compare/v0.0.4...v0.0.5

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/QuivrHQ/MegaParse/releases/tag/v0.0.5 :sunflower:


Attach Fusion interface to linalg.softmax

There are 86 softmax ops in clip (acounting for the 1225 -> 1139 decrease in dispatches), each followed by a 'bit truncate' op. This patch allows the linalg.softmax ops to fuse with the truncation op.

@hanhanW What do you mean by a transform op?

@hanhanW What do you mean by a transform op?

I wonder if we can have testing setup like:
https://github.com/iree-org/iree/blob/e19950c4c01b20c329d22e729212d182da9fee76/compiler/src/iree/compiler/Dialect/LinalgExt/Transforms/test/tiling.mlir#L1-L23

I think now the testing is relying on one of the tests in https://github.com/iree-org/iree/tree/main/compiler/src/iree/compiler/DispatchCreation/test. (Please correct me if I'm wrong) In the transform op setup, we can decouple the deps between IREE and the interface better, which helps the upstream in the future.

I see. Yes, the testing is relying on DispatchCreation's test, so that makes sense. One issue I see is that the fusion interface offers helpful information to FormDispatchRegionsPass that uses heuristics tailored to codegen to fuse the ops (e.g. "clonable" ops and aggressive fusion). I don't think much of the logic in FormDispatchRegions pass could be moved out because it is pretty specific to IREE. So, I'm not sure what the transform op would do since "fusing" ops is essentially just putting them in the same flow.dispatch.region (also, I'm not sure how we would represent 'fusing' ops if this was moved to linalgext).

I see. Yes, the testing is relying on DispatchCreation's test, so that makes sense. One issue I see is that the fusion interface offers helpful information to FormDispatchRegionsPass that uses heuristics tailored to codegen to fuse the ops (e.g. "clonable" ops and aggressive fusion). I don't think much of the logic in FormDispatchRegions pass could be moved out because it is pretty specific to IREE. So, I'm not sure what the transform op would do since "fusing" ops is essentially just putting them in the same flow.dispatch.region (also, I'm not sure how we would represent 'fusing' ops if this was moved to linalgext).

I see, then I think it is fine for now. What I'm looking for is something similar to the upstream transform-op-fuse.mlir. We don't really care about the heuristics that used in IREE, but more like functionality. I realized that we need an op that has a region to test the fusion. We could create a test op if it is in upstream, but it looks tricky in IREE. So I think it is fine for now.


[Bug] Scale Values not being allowed in various fields

Scale values are not being allowed in various fields, the ones I know of are:
Active Effects:

Attribute Key
Effect Value

Item Sheet:

Activation Cost
Target
Range (both normal and max)
Duration
Limited Uses min (should be able to be a tied value, to a current resource val, but not a scalar)
Limited Uses max

This is def a bug, as it allows for references, and mathematical operands, but not scalars of any type

accepts: @abilities.int.mod + @abilities.wis.mod
errors: @scale.class.val

Resource Consumption
Action Recharge
Critical Hit Threshold
Saving Throw

Actor Sheet:

Top of sheet:

Hit Points (min/max, temp, +max)
Armor Class
Movement:

Walk
Burrow
Climb
Fly
Swim

Initiative modifier

Attributes Page:

Attribute Fields
Senses Fields
In the Special (Split with Semi-Colon) fields of:

Damage Immunities
Damage Resistances
Damage Vulnerabilities
Condition Immunities
Weapon Proficiencies
Armor Proficiencies
Tool Proficiencies
Special Traits

Spellbook page:

Spell Slot min (should be able to be a tied value, to a current resource val, but not a scalar)
Spell Slot max

Each of these just puts a e- when trying to paste in the scale identifier (ex: @scale.class.val), or doesn't honour it at all.
Scale values should be allowed in any field, to limit the amount of issues needing to be reported to keep fixing these. And in pretty much any field allowing for reference values (the @ values, in case I am not using the correct name there)
This should be a superseding of the original issue: #1504 as it is a pervasive issue throughout the actor sheet/item sheet, and each field should be evaluated and confirmed that it is allowing them.

bump for at least getting tags on this? Coulda sworn it had them back on gitlab...

So, some of these fields do accept Scale Values now;
Active Effects - Both Attribute Key and Effect Value (for the keys that accept formulas at least) per #1605
Items - Duration and Limited Uses Max
Character - AC (as a/part of a custom formula), Initiative Bonus
I agree on an Item's Target and Range Normal/Max fields should accept them
And I would add the Special Traits' Weapon Critical Hit Threshold, Spell Critical Hit Threshold, and Melee Critical Damage Dice fields
Other than that, I dont think that most of these would really benefit from accepting a Scale Value

Still not able to make formulas in Numeric, so have to do so in "Anything" and Item Limited Uses Max won't accept an "Anything" scalar, even though it is a formula, even though you can put in that formula into the field and it is accepted.
So I guess it is either the Numeric Scalar needs to be fixed to allow for formulas, or stop filtering on type of scalar, and just filter on actual result for the field data validation, so that "Anything" can be used.

The problem here with the example is that your scale value does not evaluate to a number, but the string 2 * @prof + x, and it is not evaluated one more time to determine @prof.
You can instead use a scaling value for just the modifier added on top, and the result would be correct.
2 * @prof + @scale.adept.exertion-pool

and it is not evaluated one more time to determine @prof.
Sorry, not coming through clearly. So you're saying that the issue is because @prof isn't actually expanded, and that is the issue?

Yes.

Ok... Is that going to be the same for any data attributes?
If so can we get that processing handled in scalars, because definitely
have others I would want to do with attributes and things. Or just have
scalar formulas expand inline to be inside parens Incase of other operands
intending to be done?
ie:
scalar: @.+3`
in a field would be:
@scalar_name^2
would expand to:
@.+3)^2
before being evaluated in place.
On Mon, Apr 17, 2023, 11:49 Zhell @.***> wrote:

Yes.
—
Reply to this email directly, view it on GitHub
https://github.com/foundryvtt/dnd5e/issues/1942#issuecomment-1511631651,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKP54VHR2HAW767F4AC5KV3XBVRAXANCNFSM6AAAAAASK3JMOA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Recursively evaluating roll data is something that could be added by the system, but is probably best left to the core roll API. To address the original issue though: What it seems like is being asked for here, is to take almost every single number field that exists across Actor and Item models, and convert them to strings instead that accept roll expressions. That very much does not align with our goals around implementing data models in the first place. It might turn out to be the correct thing to do in order to accommodate all the various material out there, but there are lots of trade-offs involved, so it's not something that can be done with a single, sweeping change as the issue appears to be calling for. Most likely each field or group of related fields will need to be evaluated on a case-by-case basis, with some clear use-cases.


Add setup files and build output to gitignore

FYI: This was merged in 60607ec0b7eb64c152a8ebb1af6d2fea721ed3f0. This shoudl have been closed by the bot, I'll give it a bit longer...


bump requirements, fix #1

But now the issue is with shared objects loading.

This is already one step forward, thanks :+1:


Adding sample implementation of a metrics handler

What was changed

Adding sample implementing a custom metrics handler, which just prints the metrics to console.
Checklist

How was this tested:

Executed and verified the sample.

Any docs updates needed?

Updated README.md

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix building r0.11 from source

Fixes a bunch of issues I had building from source on r0.11, including #9130 and #5143. With these changes I was able to successfully build tensorflow with cuda support with bazel 0.4.5.

Can one of the admins verify this patch?

@kashif @aj-michael are you ok with my cherry-picking your commits here?

This looks good, and thank you for the contribution, but help me understand why it's necessary? This branch is quite old. I'm wondering why no one else has run into problems with it.

I suspect people are simply using the pre-built pip wheels (this included me until recently). These changes were only necessary to build from source.

I am opposed to accepting PRs to old release branches.
The biggest reason is, bazel had a lot of backwards incompatible changes.
When fixing the build for latest bazel version included in the dockerfiles in this branch.
Unless anyone else has any objections, I will close this PR.


fix: support csv based on content type

instead of just ms-excel, csv file type supporting apps will open

@alphapokedex
Thanks for your PR,
I just tested the current implementation and it seems to be working fine with CSV file types
And it properly opens the file chooser dialog

Could you please explain what was the scenario that you couldn't have a file chooser and it get's locked to MsExcel app?

As there was no proof or reproducible steps provided, closing this PR
Feel free to open another

Hi @javaherisaber,
Here are the reproducable steps below:

Delete all excel/CSV apps from your device (this is considering the case where people do not have CSV dedicated apps)
Install google sheets which supports CSV file type for viewing. But since google sheets does not support "application/vnd.ms-excel" in intent, "text/csv" worked.

Can you please try again


Update DG and add more flexibility to PlantUML style

Adds section on import command to DG and updates storage UML diagram.
Important:

style.puml which defines styles to be used across all files that include it, has been updated so that class attributes have white font color, and visibility can be represented with +/- instead of the default PUML icons.

Codecov Report

Merging #144 (174279a) into master (6b5d3b6) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #144   +/-   ##
=========================================
  Coverage     77.84%   77.84%
  Complexity      670      670
=========================================
  Files            90       90
  Lines          2018     2018
  Branches        270      270
=========================================
  Hits           1571     1571
  Misses          368      368
  Partials         79       79

Continue to review full report at Codecov.

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


Rule kms::DisabledKey available in reporter, but missing ref

Hi @kuettai . Referring to issue #69 , understand that you have addressed it recently but after running the screener again, I received the following error:
RdspageBuilder class not found, using default pageBuilder EfspageBuilder class not found, using default pageBuilder S3pageBuilder class not found, using default pageBuilder Ec2pageBuilder class not found, using default pageBuilder CloudfrontpageBuilder class not found, using default pageBuilder ElasticachepageBuilder class not found, using default pageBuilder LambdapageBuilder class not found, using default pageBuilder CloudtrailpageBuilder class not found, using default pageBuilder OpensearchpageBuilder class not found, using default pageBuilder [__!! WARNING !!__] Rule kms::DisabledKey available in reporter, but missing ref, please submit an issue to github. KmspageBuilder class not found, using default pageBuilder Traceback (most recent call last):   File "/home/ec2-user/service-screener-v2/main.py", line 273, in <module>     Screener.generateScreenerOutput(runmode, contexts, hasGlobal, regions, uploadToS3, bucket)   File "/home/ec2-user/service-screener-v2/Screener.py", line 178, in generateScreenerOutput     pb.buildPage()   File "/home/ec2-user/service-screener-v2/services/PageBuilder.py", line 68, in buildPage     output.append(self.buildContentSummary())   File "/home/ec2-user/service-screener-v2/services/PageBuilder.py", line 89, in buildContentSummary     return getattr(self, method)()   File "/home/ec2-user/service-screener-v2/services/PageBuilder.py", line 650, in buildContentSummary_default     body = self.generateSummaryCardContent(attrs)   File "/home/ec2-user/service-screener-v2/services/PageBuilder.py", line 202, in generateSummaryCardContent     if summary['__links']: KeyError: '__links'
I've pulled from the latest main branch prior testing.  Kindly assist.

Hi, thank for reporting! We run a full scan to ensure no more missing links in all the reporters. I fixed at #79 , please validate and let us know if any other errors has surfaced.

Hi @kuettai . Tested and no error returned.
Looks good for now.
Thank you.


Update CMake build for new dialect and transforms introduced

Update CMake build for new dialect and transforms introduced

@ai-mannamalai to reduce the burden on you, are you able to get this into the GitHub CI?


Connect probe to a different host

I have been trying to run scope on Joyent Triton. The issue is that the probe cannot connect directly to the host to access the docker API. On Triton, a specific machine provides one API for the whole datacenter.
I understand that it is probably not the intended use but is there any way to connect a probe to a specific host ?

Hi @benjamin-bergia: unfortunately we seem to have hard coded the docker endpoint into the probe, which is a bit naughty of us (see https://github.com/weaveworks/scope/blob/master/probe/docker/registry.go#L28).
I'd more than welcome a PR to turn this into a flag if you're interested?

@tomwilkie thank you for your answer.
I am very sorry but unfortunately I won't be able to provide any PR.
Should I keep this issue open or can I close it ?

Its fine, leave it open.


8.3.0: the trait arrow_odbc::odbc_api::Cursor is not implemented

The 8.3.0 update is breaking my code with:
the trait arrow_odbc::odbc_api::Cursor is not implemented for odbc_api::CursorImpl<odbc_api::StatementConnection<'static>>

Sounds like a version mismatch for me. Are you sure that the Cursor trait and the implementation use the same version of odbc-api? Maybe check with cargo tree if there are two version of odbc-api in your stack.

FYI: arrow-odbc reexports odbc-api so you can make sure you are always using the same version throughout your application.

Not sure what I can do here, rather than being a bit more explicit in the documentation. Hmm, 🤔 ...

How do you like the new Readme?

Yeah, I think that comment will help, thanks.


Datepicker 1.3.3 validation issue

I'm using datepicker from angular ui 1.3.3 from [maven repo] (https://mvnrepository.com/artifact/org.webjars/angular-ui-bootstrap/1.3.3), And AngularJs 1.x. if the user enters a wrong or invalid input, no error is displayed, the field is not cleared and nothing happens. Of course the the input won't be accepted when the user submits the form but there's no message or anything.
Is it by default? Should I use ng-messages? Is it a bug? Is it fixed by later releases? I see on github it's now 2.1.0 while I'm still using 1.3.3 from maven repos.

Please post a reproduction - you can grab a Plunker template from the homepage.

that issue was solved a long time ago, you can close it if you want.
https://stackoverflow.com/questions/39053632/angular-ui-bootstrap-datepicket-input-validation


what shuld used for AtomicCell or ShardedLock

I have a data structure  HashMap<String, ArrayQueue<Message>>，that is more than 90% read and only rarely write. Which structure should I use to protect it? AtomicCell or ShardedLock ？

ShardedLock. (AtomicCell is mainly for Copy-able types.)


Can express-hbs use paragraph functions like express-Handlebars?

Can express-hbs use paragraph functions like express-Handlebars?
app.engine('hbs', exphbs.express4({
partialsDir: './views/template/partials/',
layoutsDir: "./views/template/layouts/",
defaultLayout:'./views/template/layouts/layout-default',
extname: '.hbs',
helpers: {
section: function(name, options) {
if(!this._sections) this._sections = {};
this._sections[name] = options.fn(this);
console.log(name,options)
return null;
}
}
}));
Why did I have no effect after configuration?

I'm not sure what you mean by paragraph functions?
There is no helpers configuration option in express-hbs, you would need to use the registerHelper() function to register any helpers.
Hopefully this answers your question, if not please come back and provide more details :)

Has been resolved, thank you very much!
Function similar to {{#contentFor "Keywords"}}{{keywords}}{{/contentFor}} so!


Using a timestamp on objects makes it hard to patch the helm chart

Hello,
First of all, thank you for writing this helm chart, its very complete and its for sure helpful on deploying erpnext.
I am having an hard time patching the jobs because of the name having the date https://github.com/frappe/helm/blob/525ace58f629f1281f2f1c1aaa51462e2f4ff187/erpnext/templates/job-create-site.yaml#L5C2-L5C87  in the name makes it hard to do something like:
---
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: erpnext
  namespace: flux-system
spec:
  interval: 10m
  timeout: 5m
  chart:
    spec:
      chart: erpnext
      version: "8.1.0"
      sourceRef:
        kind: HelmRepository
        name: frappe-charts
  releaseName: erpnext
  targetNamespace: erpnext
  install:
    createNamespace: true
    disableWait: false
    remediation:
      retries: 3
  upgrade:
    remediation:
      retries: 3
      strategy: rollback
  test:
    enable: true
  # https://github.com/frappe/helm/blob/main/erpnext/values.yaml
  values:
    persistence:
      worker:
        enabled: true
        size: 80Gi
        storageClass: openebs-hostpath
        accessModes:
          - ReadWriteMany
    mariadb:
      enabled: false
    postRenderers:
      - kustomize:
          patchesStrategicMerge:
            - kind: Job
              apiVersion: batch/v1
              metadata:
                name: erp-next-new-site-date
              spec:
                template:
                  initContainers:
                    - name: validate-config
                      env:
                        - name: "DB_HOST"
                          valueFrom:
                            secretKeyRef:
                              name: erpnext
                              key: PG_HOST
                        - name: "DB_PORT"
                          valueFrom:
                            secretKeyRef:
                              name: erpnext
                              key: PG_PORT
                  containers:
                    - name: create-site
                      env:
                        - name: "DB_HOST"
                          valueFrom:
                            secretKeyRef:
                              name: erpnext
                              key: PG_HOST
                        - name: "DB_PORT"
                          valueFrom:
                            secretKeyRef:
                              name: erpnext
                              key: PG_PORT

What do you suggest in this case? Is there a way to change the name to a fixed position ?

check .Values.jobs.custom.jobName and
https://github.com/frappe/helm/blob/525ace58f629f1281f2f1c1aaa51462e2f4ff187/erpnext/templates/job-custom.yaml#L5
You can use that.
If you are willing to send a PR, add .Values.jobs.createSite.jobName and/or .Values.jobs.migrate.jobName, if that is set use it instead of auto generated name. Let the chart work as is if nothing is set. (no migration or backward compatibility overhead for others).

@alfredopalhares
https://github.com/frappe/helm/pull/224
will this solve your problem?

Hello @revant , yes, that would be exactly what I need !

The chart will be released this week along with ERPNext version bump


Shell Game Completed

PR Description 📜

new game completed.
Fixes #3282
Mark the task you have completed ✅

[✅ ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[ ✅ ] I have performed a self-review of my own code or work.
[ ✅ ] I have commented my code, particularly in hard-to-understand areas.
[ ✅ ] My changes generates no new warnings.
[ ✅ ] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ ✅ ] I have added screenshot for website preview in assets/images
[ ✅ ] I have added entries for my game in main README.md
[ ✅ ] I have added README.md in my folder
[ ✅ ] I have specified the respective issue number for which I have requested the new game.

---

Thank you soo much for contributing to our repository 💗

game added in README file!

any changes needed?

@Tamilkumaran17 resolve the conflicts !

Can you check now, i have resolved the conflicts!

@Tamilkumaran17 resolve conflicts as there are few games added after your PR you have to make sure you are adding your game at last
!

Now i set my game link at last. Can you check it now, if any other conflicts occur, i apologize to that and give me clear details about that for my reference!

@Tamilkumaran17 resolve the conflicts !

Thank you  @Tamilkumaran17 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


CLI Option to run exported Key Runner collection is not available

I have gone through Key Runner Docs website link (as given below), but we didn’t find any information related to running collection using CLI option.
Do we have this option in Key Runner wherein we can run Key Runner collection using CLI option. If it’s available, please provide docs link for the same.
https://docs.keyrunner.app/docs/

we are actively working on CLI at this time for free version. But for enterprise version we are exposing keyrunner API's which can be leveraged to integrate  with CI/CD pipelines.

@akhot09 we’ve published our CLI! You can check it out and find all the details with below links.
https://www.npmjs.com/package/keyrunner?activeTab=readme
https://docs.keyrunner.app/docs/CLI.html


Improve Handling of RV32E

The handling of the Embedded Extension (Register file size (RFS) = 16) is suboptimal for several reasons:

Realibility is degraded. Consider the ADD instruction as an example:

behavior: if(rd >=RFS || rs1 >= RFS || rs2 >= RFS) raise(0, 2); else if (rd != 0) X[rd] = X[rs1] + X[rs2];
# vs.
behavior: if (rd != 0) X[rd] = X[rs1] + X[rs2];

Checking constraints and calling raise(...) inside of behavior makes analysing the behavior more difficult.
Illegal Instructions (due to register file limitations) which can be solely determined based on the encoding and static architectureal state should not be raised during decoding instead.
This adds a lot of redundant code, because we basically have roughly the same checks for almost every (standard) instruction. Declaring it only once for RV32E would be way cleaner

Let's discuss how to handle the embedded extension in a more sophisticated way.
@jopperm @eyck @AtomCrafty @wysiwyng

Actually I fully agree. My first attempt would be to enhance the encoding part to allow conditional specifications like:
encoding: imm[31:12] :: RFS==16? (1'b0::rd[3:0]) : rd[4:0] :: 7'b0110111;

which would also allow for
encoding: RFS==16?
                    (7'b0000000 :: rs2[4:0] :: rs1[4:0] :: 3'b000 :: rd[4:0] :: 7'b0110011):
                    (8'b00000000 :: rs2[3:0] :: 1'b0:: rs1[1:0] :: 4'b000 :: rd[3:0] :: 7'b0110011);

But in conjunction with #96 there might be other solutions.

I haven’t considered such syntax yet. But I kinda like it because it is probably the least invasive. Of course this does not offer enough flexibility to also support #96…


Panic

I install 0D1N via trollstore but every time i try jailbreak my phone will panic ( ip7plus 15.7.6 )

Try with the latest version
Sent from my iPhone
On Feb 9, 2024, at 9:56 PM, baoprovip1 @.***> wrote:

I install 0D1N via trollstore but every time i try jailbreak my phone will panic ( ip7plus 15.7.6 )
—
Reply to this email directly, view it on GitHubhttps://github.com/pwned4ever/Od1n/issues/1, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACHLHAFCRUCQGULYGE64RILYS3OU3AVCNFSM6AAAAABDCL3LYWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZDQMBWGI3TIMQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


how to Add record to collection

i want to add data to collection
my code
record = client.collection('fletSample').create(name="bout",age=120)
BUT ERROR
File "/home/minx/belajar/colongan/pythonsidik/test.py", line 7, in
record = client.collection('fletSample').create(name="bout",age=120)
TypeError: CrudService.create() got an unexpected keyword argument 'name'
wahst solutions

You can read the readme or tests:
result = client.collection("fletSample").create({
        "name": "bout",
        "age": 120
})


feat(web, dal, sdf): Create a leight approval / notification system

There are a number of differnet states going on here:

No collaborators on the changeset

No Actions so we get a simple confirmation modal (this is new!!)
Actions so we get a list of actions to be applied in the modal

Collaborators in the changeset

We begin a change set approval - changeset status moves to NeedsApproval
Each collaborate gets a modal to vote (Accept, Pass, Reject)
When a collaborate has voted their changeset usage is locked until the merge has completed or been cancelled
If ANY of the collaborators reject the merge then the person needs to take an action of override or cancel. * If approved then it's a normal merge process * If cancelled then the changeset is unlocked for everyone and the status changes back to Open
If all collaborators choose pass or approve, then the changeset will autoapprove
If the person chooses to override the merge, then all collaborators are told so

bors merge


Support "partial installs" of fleece

I'm using fleece to get AWS X-Ray support in AWS lambda services. It works great!
The one challenge is reducing the size of the install. Since I'm only using X-Ray, I don't need any of the heavy weight dependencies, such as Flask. Space is at a premium in the Lambda environment.
I'm assuming manual pruning can be done (I haven't begun the process). However, that may be "not fun" to replicate in tox or some cloud based CI services.
If support for this use case can be added into the fleece packaging, awesome!  If not, I'll document my results here.

@hwine - I think this is a great idea and have been thinking about this as well. Perhaps we could put some of the heavier stuff behind an extras flag like requests does? Thoughts?

I was thinking along those lines, too. But I think that wouldn't be backward compatible. But I'm not that familiar with packaging.
A documented approach maybe sufficient. I haven't experimented yet - maybe just installing with --no-deps would do it. As long as we add some tests to ensure it stays okay. 😁

@hwine - Apologies for the amount of time it took to implement this. #47 should now move most of the heavy deps into an extras package and make the install size much smaller. There should be a new version released in a day or so with these changes.

@ryandub no worries! I'll be happy to take the update. Thanks for your work on this!


SSR (Server Side Rendering) with react-rails

Steps to reproduce

Clone this repo: https://github.com/paul-mesnilgrente/shakapacker-with-react-rails
yarn and bundle install
bin/rails server and bin/webpacker-dev-server
Go to localhost:3000 and see the error

Expected behavior
I expect the app to show a nice "Hello Gus!"
Actual behavior
The page errors
System configuration
Shakapacker version: 6.5.0
React-Rails version: 2.6.2
Rect_UJS version: 2.6.2
Rails version: <IP_ADDRESS>
Ruby version:3.0.3

My current steps (that you can see in the commits)

Created a brand new repo
Added Shakapacker and followed its installation steps
Added the react-rails gem
Re-created the install steps of react-rails on this test repo
Got a working version of a component working without SSR
Turned on SSR and it failed with

React::ServerRendering::PrerenderError in Homes#index

Encountered error "#<ExecJS::ProgramError: TypeError: Cannot read properties of undefined (reading 'serverRender')>" when prerendering HelloWorld with {"name":"Gus!"}
...
Object.<anonymous> ((execjs):1:58)
Module._compile (node:internal/modules/cjs/loader:1103:14)
Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
Module.load (node:internal/modules/cjs/loader:981:32)
Function.Module._load (node:internal/modules/cjs/loader:822:12)
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/execjs-2.8.1/lib/execjs/external_runtime.rb:39:in `exec'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/execjs-2.8.1/lib/execjs/external_runtime.rb:21:in `eval'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/react-rails-2.6.2/lib/react/server_rendering/exec_js_renderer.rb:39:in `render_from_parts'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/react-rails-2.6.2/lib/react/server_rendering/exec_js_renderer.rb:20:in `render'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/react-rails-2.6.2/lib/react/server_rendering/bundle_renderer.rb:40:in `render'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/react-rails-2.6.2/lib/react/server_rendering.rb:27:in `block in render'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/connection_pool-2.2.5/lib/connection_pool.rb:63:in `block (2 levels) in with'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/connection_pool-2.2.5/lib/connection_pool.rb:62:in `handle_interrupt'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/connection_pool-2.2.5/lib/connection_pool.rb:62:in `block in with'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/connection_pool-2.2.5/lib/connection_pool.rb:59:in `handle_interrupt'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/connection_pool-2.2.5/lib/connection_pool.rb:59:in `with'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/react-rails-2.6.2/lib/react/server_rendering.rb:26:in `render'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/react-rails-2.6.2/lib/react/rails/component_mount.rb:74:in `prerender_component'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/react-rails-2.6.2/lib/react/rails/component_mount.rb:38:in `block in react_component'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/capture_helper.rb:45:in `block in capture'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/capture_helper.rb:209:in `with_output_buffer'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/capture_helper.rb:45:in `capture'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/tag_helper.rb:371:in `content_tag'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/react-rails-2.6.2/lib/react/rails/component_mount.rb:57:in `react_component'
/home/paul/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/react-rails-2.6.2/lib/react/rails/view_helper.rb:21:in `react_component'
/home/paul/Dev/shakapacker-test/app/views/homes/index.html.erb:6:in `_app_views_homes_index_html_erb__1592835306549513420_20900'

You can test this with the repo mentioned above. Do you know what's wrong? The error doesn't leave a lot of clues.

Maybe I should have asked differently.
Does anyone have a working SSR with react-rails and Shakapacker? If so, could you provide an example project?

Based on https://github.com/reactjs/react-rails/issues/1201, this doesn't seem to be Shakapacker related.


Support reading of empty incarnationId and sessionsId in V2 of StoreFindToken

StoreFindToken in V1 will not have incarnationId. With latest patch(StoreFindToken V2), reading the old token will result in V2 token with null incarnationId. But deserialization of V2 token assumes that incarnationId and sessionsId cannot be null. So, any further deserialization with the same token will fail. This patch makes the fix to remove that assumption.
SLA: 5 mins
Reviewers: @vgkholla
Built and coding style applied.

I think the statement "any further deserialization with the same token will fail" kind of conveys that we ended up reading incorrectly from the stream. That is not true, since you were always reading from the stream correctly. The bug is in calling UUID.fromString() on an empty string. Could you update the description?

Discarding this based on the discussion with @nsivabalan and @vgkholla. We concluded that the more appropriate way of looking at this is that the StoreFindToken version should be part of the class itself and not just its SerDe, and that V2 should alway shave a non-null IncarnationId. More details in #551.

thanks to @vgkholla for the insight!


Issue building in UE 5.4

Hello, I'm having issues compiling/building my project in Unreal 5.4 using this plugin, this is the issue I see:
[176/187] Link [x64] UnrealEditor-AndroidNative.dll
error LNK2005: "class _jobject * FJavaWrapper::GameActivityThis" (?GameActivityThis@FJavaWrapper@@3PEAV_jobject@@EA) already defined in AndroidNativeLibrary.cpp.obj

Not sure why this is happening, FJavaWrapper::GameActivityThis is only defined once in JavaConvert.h but it is saying it is also defined in AndroidNativeLibrary.cpp for some reason, I see it being used there but not defined?
I will continue investigating this issue, I did modify your plugin a little, I only needed it to be able to write my own Android Java functions and have them run in my Unreal project, so I removed most of the functions in AndroidNativeLibrary and replaced with my own, but none of them define GameActivityThis

Hi, I guess it's not relevant anymore, as we discussed in Discord?

Yes this is now working - just needed a fresh pull of the repository (I hadn't updated to the latest push from 3 months ago)
Thanks for the help @gtreshchev !


UI: The signup/login Button should have same width as the input fields

Is your feature request related to a problem? Please describe.
The signup/login button does not seems align with input fields ui
Describe the solution you'd like
The signup/login Button should have same width as the input fields

can i work on this ?

@iimamul go ahead with the issue please

@ani1609 signup/login width of the input box and UI seams different too. I fixed that too.  Should I PR this with this issue ? or have to create new issue for input and UI width ?

@iimamul please push the relevant codes in relevant issues. push the styling of the buttons here and i am assigning you the issue regarding different widths. push the code there.

@iimamul are you there in our slack channel? If not, please join and text me, there seems to be a conflict because another guy has pushed his code into the same issue as yours.

ok @ani1609 joining


DRY up walking the Settings by moving into a module

@kbrock Please review.
This DRYs up the recent changes you made to FixAuth for walking the Settings by moving it into a standalone module.  That module can then be required by appliance_console directly.
Note that I did not change any of the Vmdb::Settings interface in this PR.  If you're good with it then we can discuss if I should kill those methods and constant from the Vmdb::Settings interface in this PR or a separate one.
cc @gtanzillo This will probably conflict with #10705 , so I'll just rebase whichever one isn't merged first.

Rebased now that #10705 is merged.  This should be good now.