fix docker build => burrow to Burrow

currently, docker build . fails.
I fixed ADD path burrow => Burrow

build log before
```bash
~ghh/linkedin/Burrow(master) $ docker build .
Sending build context to Docker daemon 13.82 MB
Step 1 : FROM golang:alpine
 ---> 6b317e0ae72c
Step 2 : MAINTAINER LinkedIn Burrow "https://github.com/linkedin/Burrow"
 ---> Using cache
 ---> 72cfdfe7c00d
Step 3 : RUN apk add --update bash curl git && rm -rf /var/cache/apk/*
 ---> Using cache
 ---> 2fdee1e82f62
Step 4 : RUN curl -sSO https://raw.githubusercontent.com/pote/gpm/v1.4.0/bin/gpm &&   chmod +x gpm && mv gpm /usr/local/bin
 ---> Using cache
 ---> fe5492556bc9
Step 5 : ADD . $GOPATH/src/github.com/linkedin/burrow
 ---> 621af4c17f2a
Removing intermediate container 683afb3b33f6
Step 6 : RUN cd $GOPATH/src/github.com/linkedin/burrow && gpm install && go install
 ---> Running in 187997d855bb
>> Getting package github.com/pborman/uuid
>> Getting package gopkg.in/gcfg.v1
>> Getting package github.com/cihub/seelog
>> Getting package github.com/Shopify/sarama
>> Getting package github.com/samuel/go-zookeeper/zk
>> Setting github.com/pborman/uuid to version ca53cad383cad2479bbba7f7a1a05797ec1386e4
>> Setting github.com/cihub/seelog to version 92dc4b8b540607b8187cc2f95cac200211dcd745
>> Setting github.com/samuel/go-zookeeper/zk to version ad552be7b78b762b4a8040ffc5518bdaf5b7225d
>> Setting gopkg.in/gcfg.v1 to version 0ef1a8547f99b94fac9af5377dd72febba18f37c
>> Setting github.com/Shopify/sarama to version 4ba9bba6adb6697bcec3841e1ecdfecf5227c3b9
>> Building package github.com/samuel/go-zookeeper/zk
>> Building package github.com/Shopify/sarama
>> Building package github.com/cihub/seelog
>> Building package gopkg.in/gcfg.v1
>> Building package github.com/pborman/uuid
>> All Done
notify_center.go:15:2: cannot find package "github.com/linkedin/Burrow/notifier" in any of:
	/usr/local/go/src/github.com/linkedin/Burrow/notifier (from $GOROOT)
	/go/src/github.com/linkedin/Burrow/notifier (from $GOPATH)
debug.go:15:2: cannot find package "github.com/linkedin/Burrow/protocol" in any of:
	/usr/local/go/src/github.com/linkedin/Burrow/protocol (from $GOROOT)
	/go/src/github.com/linkedin/Burrow/protocol (from $GOPATH)
The command '/bin/sh -c cd $GOPATH/src/github.com/linkedin/burrow && gpm install && go install' returned a non-zero code: 1
```

build log after
```bash
Sending build context to Docker daemon   960 kB
Step 1 : FROM golang:alpine
 ---> 6b317e0ae72c
Step 2 : MAINTAINER LinkedIn Burrow "https://github.com/linkedin/Burrow"
 ---> Using cache
 ---> 72cfdfe7c00d
Step 3 : RUN apk add --update bash curl git && rm -rf /var/cache/apk/*
 ---> Using cache
 ---> 2fdee1e82f62
Step 4 : RUN curl -sSO https://raw.githubusercontent.com/pote/gpm/v1.4.0/bin/gpm &&   chmod +x gpm && mv gpm /usr/local/bin
 ---> Using cache
 ---> fe5492556bc9
Step 5 : ADD . $GOPATH/src/github.com/linkedin/Burrow
 ---> 326f26106ed7
Removing intermediate container b601dfcf9f35
Step 6 : RUN cd $GOPATH/src/github.com/linkedin/Burrow && gpm install && go build -o burrow && mv burrow $GOPATH/bin/
 ---> Running in 44ddc0702589
>> Getting package github.com/samuel/go-zookeeper/zk
>> Getting package github.com/Shopify/sarama
>> Getting package github.com/pborman/uuid
>> Getting package github.com/cihub/seelog
>> Getting package gopkg.in/gcfg.v1
>> Setting gopkg.in/gcfg.v1 to version 0ef1a8547f99b94fac9af5377dd72febba18f37c
>> Setting github.com/pborman/uuid to version ca53cad383cad2479bbba7f7a1a05797ec1386e4
>> Setting github.com/cihub/seelog to version 92dc4b8b540607b8187cc2f95cac200211dcd745
>> Setting github.com/Shopify/sarama to version 4ba9bba6adb6697bcec3841e1ecdfecf5227c3b9
>> Setting github.com/samuel/go-zookeeper/zk to version ad552be7b78b762b4a8040ffc5518bdaf5b7225d
>> Building package github.com/samuel/go-zookeeper/zk
>> Building package github.com/Shopify/sarama
>> Building package github.com/cihub/seelog
>> Building package gopkg.in/gcfg.v1
>> Building package github.com/pborman/uuid
>> All Done
 ---> 02deaa26a2f3
Removing intermediate container 44ddc0702589
Step 7 : ADD docker-config /etc/burrow
 ---> 41919e302c69
Removing intermediate container 87d2d153c967
Step 8 : WORKDIR /var/tmp/burrow
 ---> Running in 02226876b1dd
 ---> 4741cd8ecfbf
Removing intermediate container 02226876b1dd
Step 9 : CMD /go/bin/burrow --config /etc/burrow/burrow.cfg
 ---> Running in cee1cf49ae5f
 ---> 94a03bb6260d
Removing intermediate container cee1cf49ae5f
Successfully built 94a03bb6260d
```

@matsu-chara you should use go install replace of go build, the previous is faster.

I tried go install. It build binary with tha name Burrow (not burrow), then docker run failed.
Can I change the binary name with go install command?

No, go install  can't change the binary name, maybe go install && mv $GOPATH/bin/Burrow $GOPATH/bin/burrow;
or directly use Burrow as execute name.

I changed to go install && mv $GOPATH/bin/Burrow $GOPATH/bin/burrow
thanks!

Thanks for the fix, I met same issue when build docker image.


missing reference 35 in global data smell

https://luzkan.github.io/smells/global-data

Nice! I see that in the thesis on page 88 (4.5.1. Global Data) It references [56], which is older version of Martin Fowler book from 1999.
Adding the missing reference 😸


chore: Upgrade to TS 4.4.2

Slightly unsure about the error handling on src/install-rust.ts, typically all errors at that point should be instanceof Error, it's just that TS 4.4 gives the error in the catch handler an unknown type.
Implements #52

Closing in favor of https://github.com/vercel-community/rust/pull/80/files


style variable fallthrough seems broken.

the styling playground seems broken, example doesn't reflect changes when variable value changed

also tried to specified variable value in my project like this, doesn't seems to work.
<Datepicker v-model="picked" style="--vdp-divider-color:#000000"/>

Strange, I'll look into that. It worked before :sweat_smile:

I have the same issue @newlifehaonan Did you find a solution

I was also facing same problem. I have overwritten it by the following way.
<style>
.v3dp__datepicker {
  --elem-hover-bg-color: var(--vdp-hover-bg-color, #62d1f3);
  --elem-selected-bg-color: var(--vdp-selected-bg-color, #4680ff);
}
</style>
<template>
    <datepicker v-model="picked"/>
</template>

Thanks for the report, sorry for the delay, will be fixed in the next release

Yeah, published under 0.2.5. You can check the playground in the docs to verify that everything is fixed :D


WIP presenter mode

I would love to use this feature already today to be able to better demo bots!
The normal bot works under the covers and outputs stuff, but that is not the most spectacular show ever for anyone observing it. Being able to visualize the work would be great, even better if using some kind of toggle.
Any chance of getting this one merged as is? It would already provide value!

Sorry this slipped trough the cracks and no-one in the core team did pick up the ball.


Spyder will not launch (tried other solutions)

Problem Description
Spyder will not launch. I've tried opening from Anaconda Navigator and exe in Anaconda folder, the cursor gives the busy icon for a few seconds, then nothing.
I've tried the following (either alone or combinations):
1.Downgrading and launching
2. spyder --reset
3.conda update conda then launching
4.conda update --all then launching
5.conda remove spyder-kernels then install spyder-kernels=0.* then launching
6.Complete uninstall of Anaconda environment with anaconda-clean then uninstall, then reinstalling
Still will not launch. I do not get any errors, it just will not open. Help is greatly appreciated.
 Please deactivate them and try again.

Thank you for the quick reply. I previously had a suspicion that it could be an antivirus issue but i made sure that there were no restrictions for anaconda or spyder in the antivirus software. In any case, i just tried to disable my anti-virus and open spyder but the issue persisted. This issue happened randomly, i've not used spyder on this machine for about 3 weeks, but prior to that everything was normal.

You can also try deactivating your firewall (or Windows defender) to see if that helps.
If not, you could remove Anaconda and reinstall an older version of it.

I took my laptop off the charger today to another room and randomly tried to open spyder and lo and behold, it opened. I didn't buy it at first so i tried to replicate this ten times where i put the laptop on the charger tried to open spyder, it wouldn't open. Then i took it off the charger and opened and it worked. Have you ever encountered an issue like this one?

Have you ever encountered an issue like this one?

No, sorry, and that's very strange indeed!
I'm afraid I'm going to close this issue because it's not related to Spyder but to something in your computer. Glad you figured it out how to make it work again though.


long wait connect server in 1.0.0rc2 (6 second)

after update radiant and nginx to 1.0.0rc2  сonnect to the server was over 6 second (site: www.termoteks.ru)
Processing SiteController#show_page (for <IP_ADDRESS> at 2011-06-20 11:32:31) [GET]
Parameters: {"url"=>["decor", "dvp-mdf"], "action"=>"show_page", "controller"=>"site"}
Completed in 6437ms (DB: 42) | 200 [http://www.termoteks.ru/decor/dvp-mdf]
in radiant 0.9.1 сonnect to the server was 300 millisecond (site: www.novoteks.org)
server VPS, memory 512mb REE, passenger, nginx
what is wrong?

With current (post rc3) edge I'm seeing quite good responsiveness but very, very slow booting. Fine on a busy site, big problem on a quiet one where most visitors will have to wait for passenger to spin up. Worth checking before v1 comes out, I think.

Here is some ruby-prof output for current edge, in production mode but running locally under webrick.

booting
first request
second
third

And here are some graph views, truncated at about 1000 lines for sanity.

booting
request

I'm no expert at reading these, but it does look like we're redefining every radius tag on every request.
In the boot all I can see is that we're spending all our time loading gems. I'll try and get a better look.

It looks like the other really expensive call is to descendants, usually Page.descedants. I think that's because it involves a call to subclasses_of that often results in a string eval. It shows up in the flat profile as each_object and takes about 18% of request processing time.
We also spend quite a lot of time on lesser performance drains like symbolize_keys in StandardTags, and module_eval and String#split in Radius::Utility. They add up to about 12%.
@jlong: is there a way to avoid redefining radius tags on every request, or is that an unavoidable consequence of the tag do syntax? It often takes over 20% of our request cycle.

@will-r I'm not sure why that would have anything to do with the difference in Radiant versions. I tend to think that the behavior there should stay the same for 1.0. Revamping the page tags system sounds like a great idea for 2.0.

I think losing the ability to override is a big problem. It's currently an "it just works" feature, and I've had to use it to override features.
Thanks for profiling this. I haven't looked at the gists yet but will do so

No, I wouldn't say it was the reason for the changes protoror saw. I think the gem-extension overheads are a more likely culprit, but I really don't know. I'm just looking for ways to speed radiant up.

@saturnflyer: we can still override. No problem there. What we would lose is the ability to subclass tags within specific page types. The only example I can think of is breadcrumbs, which are occasionally redefined in Page classes that do their own thing with the path.
Even that we can probably work around with a class_inheritable_accessor but I haven't tried it yet.

Still digging into this, and I think I was only partly right. I can cut request time by about 20% by storing tag definitions in a class variable instead of reloading them every time. It still takes nearly 5 seconds to render a page, and 96% of that time is spent rendering radius tags.
Here's a breakdown (from newrelic) of a page request:
!http://static.spanner.org/radiant/request-breakdown.png!
And if you zoom in on SiteController#show_page and profile that with ruby-prof and after a great deal of digging I think these are the key lines:
                  9.67	 0.00	 0.00	 9.67	 83/35914	Radiant::Taggable#render_tag	39
95.87%	 0.84%	  9.68	 0.08	 0.00	 9.68	 35914	  Kernel#send

That may not format well so I'll paraphrase: 96% of processing time is spent rendering 35914 calls to Kernel#send. Only 83 of those calls come from render_tag, but those are the calls that take all the time. I think we still have a render-speed problem.
Interestingly, within that a large part of the time was spent on render_snippet. I think that shows I use snippets a lot rather than that snippets are inherently problematic, but it's worth looking into, and it's worth me cutting down a bit.
@jlong: I'm sorry to disagree but I don't think we can wait for 2.0. Performance of rc3 is very poor, and when a site gets busy I have to render the whole thing out to static pages. It's bad news for a low-traffic site too, because pages are never cached. When google arrives it takes 5-10 seconds to render each page and your page rank goes through the floor.
@protoror: eliminating clipped makes no significant difference.
@jfahrenkrug, @saturnflyer: there does seem to be a big reduction in performance with radius 0.7. Could it be that we (radiant) are calling it wrongly, or is the ruby parser not very quick?

In the end the change to a persistent Page::Context was going to involve too much working against the grain of Radius so I've taken that out (and so must acknowledge that @jlong was right).

If you change Page#render_tag to use call instead of send, you get tag names in the call graph. There's some data here and I think we have a winner:
76.72%	 0.00%	 9.52	 0.00	 0.00	 9.52	 1	StylesheetTags#tag:stylesheet

The stylesheet in question is sass-filtered. If I set the filter to 'none', its share of the overall load drops to 17% and the response time is halved. It occurs to me that sass and compass aren't really optimised for production use: these days the asset pipeline would normally render them on deployment.
One other odd thing: in this case the r:stylesheet tag is as="link", so it shouldn't really be rendering at all...

Ah ha! That's really helpful. Thank you for tracking that down.
I'm sad to report that this slowdown is likely my code. In sheets, you can separate your stylesheets into different concerns and include them all in one main stylesheet. For example
<r:stylesheet slug="colors.css" />
<r:stylesheet slug="type.css" />
<r:stylesheet slug="structure.css" />

This single stylesheet would bring all of those together in one when rendered. The problem with this is that in previous versions you couldn't just edit colors.css and expect the entire thing to change. Now, you can, because the path generated for the main stylesheet uses an MD5 hash of the rendered content. So it will render to generate the link. That's the slowdown.
I'd still like to keep this feature because it matches the user's expectation of making changes and actually seeing them (as opposed to needing to update the main stylesheet to have it regenerate) but there are 2 things than need to be done.

I need to look into the caching for stylesheets to ensure that the browser is getting the proper headers to set local caching.
I need to find a better way to ensure that the main stylesheet knows about changes in any included stylesheets.

This was something I knew I needed to address and had in the back of my head to do, but sadly didn't realize the impact until I got all of you caught up in what was my performance bottleneck.
Thanks everybody for making this an issue, and please accept my apology for introducing the problem. Now we know where it is and I can begin the work to simplify this.
Given that stylesheets do not change often and there are likely to be few of them, it may make sense to just do something simple like storing the rendered content in memory or some other separate caching mechanism.

you couldn't just edit colors.css and expect the entire thing to change.

I'm not sure about the hashing mechanism. Doesn't saving colors.css clear the cache? So the whole thing would have to be rendered on the next request anyway? But it's a good point about the inclusions: here's another indeterminate effect that we can't pre-render or cache. I'm not sure that the answer lies in the main stylesheet 'knowing about' the others, just as we can't reliably know which other pages are affected when a page is edited.

some other separate caching mechanism.

I think that might be a good way to go. If there is good separation of concerns between document and style then it would make sense also to have a separation of caches. When you're working on the design, the documents don't need to be flushed, and vice versa. I think SnS made the same distinction.
It's kind of you to apologise but I'm sure you don't need to. There is plenty to optimise but I think it's the weight of rendering sass and compass on every request that's really slowing me down. I can shift all that into static files and use Sheets just for styles that need radius tags.

Saving colors.css clears the cache, but assuming the browser got the right info when some other content page is saved the same hash would be generated for the stylesheet and the browser would assume that the css is the same and never request the full content. This is feeling more and more like I got started on the idea without enough thought.
Perhaps we can add the ability to specify a cache for a branch of the page tree... or something like that so that sheets can hook in and ignore the regularly cleared cache.

I did some optimizing in SNS way back in time. that is the exact problem. what to update or better what to invalidate.
caching is not hard. invalidating is ;-) what I ended up doing was brute force invalidate all page caches after editing any sns file to get it render the new checksum parameter.
and this is a conceptual problem with other parts too. to really target this problem we would need to speed up the rendering process of pages. as will said e.g. for google indexing it is really bad to have pages which render > 2-5 s
as an intermediate step I really do what I hate to do: set the caching time of the pages to > 24h and render all pages with a cron job.
I did think a lot about this kind of optimization. what we really need is more information tied to the several parts.
the optimal scenario would be that any radius tag knows how to cache itself (with different settings). again as an intermediate solution I surround heavy rendering pages with radius caching tags I can control a bit more.
an optimal solution would be to somehow redesign radius tags as cells http://cells.rubyforge.org/
On Nov 18, 2011, at 7:23 PM, Jim Gay wrote:

Saving colors.css clears the cache, but assuming the browser got the right info when some other content page is saved the same hash would be generated for the stylesheet and the browser would assume that the css is the same and never request the full content. This is feeling more and more like I got started on the idea without enough thought.
Perhaps we can add the ability to specify a cache for a branch of the page tree... or something like that so that sheets can hook in and ignore the regularly cleared cache.

Reply to this email directly or view it on GitHub:
https://github.com/radiant/radiant/issues/234#issuecomment-2792441

--
DI Edmund Haselwanter<EMAIL_ADDRESS>http://edmund.haselwanter.com/
http://www.iteh.at | http://facebook.com/iTeh.solutions | http://at.linkedin.com/in/haselwanteredmund

Just to confirm, with the sass work moved into the filesystem and a few minor optimisations the request time drops to about 1700ms, locally and with the overhead of running newrelic in its developer mode (though the site is in production). Still a bit slower than I would like but now it's in the range where efficiency savings are worth looking for. Admin requests are comfortably in the 5-800ms range, btw.
I am slightly concerned to see a rising trend in response times but that might just be a monitoring artefact. I'll see what other small gains I can find.
@ehaselwanter: I've been thinking for a long time about a sort of tainting mechanism, where we make a note of every object touched in the creation of a page and if one of those objects changes, the cached page is invalidated. It needs a fine-grained cache so it would fit nicely with the use of Cells, and I think it would work well except for one intractable problem: when a new page is created, we can't know which other existing pages might be affected.

I've seen performance issues related to sass & compass with another project lately. It all boiled down to Sass re-compiling all scss files on every request because it didn't find a way to determine if it should cache the results.
https://github.com/nex3/sass/issues/180
There's a fix included in the yet unreleased sass 3.1.11, but I'm not sure if this will help here. However, I saw delays like the ones described here so I wanted to let you know. Maybe there's nothing wrong with the radiant cache?

Thanks. Yes, we've definitely narrowed the problem down to sass compilation on each request. Your bug report and the fix will be a big help. We'll still need to compile the sass-filtered page on each request, though. Jim's looking into that.

Thanks @datenimperator but I think you're mistaken. That commit appears to be in the latest sass.
I'm working on this issue now.

I've altered the default setup for sheets to not include a parameter on the path to the css/js. This should prevent superfluous rendering of the sass content.

Is this still the case in rc4?


ASSETS-29315 : Assets delivery APIs documentation.

Releasing the Assets Delivery API documentation
Description
Adding a link for the stable version of the Assets delivery API
Motivation and Context
Initial release of a new API
How Has This Been Tested?
I built the site locally and previewed it.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@ireasor @phornig  How do we merge this PR ?

@guillaumecarlino Could you please help in merging this PR ?


Sierra County, NM

Contact:
http://www.sierracountynm.gov/department/138751-assessor

Closing as stale - Feel free to open a new issue if someone is actively going after these.


wip

:clipboard: Add associated issues, tickets, docs URL here.
Overview
Describe what your Pull Request is about in a few sentences.
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Change 1
Change 2
...

Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.

Coverage remained the same at ?% when pulling f7aaee46434e2268726fbece44e1add3b82f65a8 on inomurko/drocker into dc971b2538a069c4e748f618b52982f3f0c5b065 on master.


Issue #692 Unmarshall json only when http response status is 200

Fixes #692

haven't loopked yet, but not just 200.
also, only when able to parse properly.
debug log errors, but treat errors as no value.

One note for future improvements, we have a download.Download() helper which downloads a file from a http(s) location using cavaliercoder/grab. In getCRCLatestVersionFromMirror(), this helper is not really what we want because a io.Reader is more appropriate than a file for what is being done. It would be more consistent though to have a helper returning an io.Reader in the download package, and to use it in getCRCLatestVersionFromMirror().


fix issue of canvas.save method

Updating gradle version , updating build tools version and compile SDK …version also fix issue of canvas.save method

Amazing! I also need this in one of my projects to update it. Big thanks!


students.txt

@WenleiZheng you have a conflict, check the readme on how to fix it. Do not start a new PR, fix this one instead

clsoing as lab deadline is over


[Bug][Ambari Plugin] Start Ambari report an error: Table 't_ds_process_definition_version' already exists

Description：
I install the dolphinscheduler in Ambari, I try to start DS_Api and hit the bug :
15:48:43.481 [main] INFO org.apache.dolphinscheduler.common.utils.ScriptRunner - sql: CALL ct_dolphin_T_t_ds_process_definition_version
15:48:43.492 [main] ERROR org.apache.dolphinscheduler.common.utils.ScriptRunner - SQLException
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 't_ds_process_definition_version' already exists
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
at com.mysql.jdbc.Util.getInstance(Util.java:408)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:944)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3933)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3869)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2524)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2675)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2465)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2439)
at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:829)
at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:729)
at com.alibaba.druid.pool.DruidPooledStatement.execute(DruidPooledStatement.java:633)
at org.apache.dolphinscheduler.common.utils.ScriptRunner.runScript(ScriptRunner.java:145)
at org.apache.dolphinscheduler.common.utils.ScriptRunner.runScript(ScriptRunner.java:75)
at org.apache.dolphinscheduler.dao.upgrade.UpgradeDao.upgradeDolphinSchedulerDDL(UpgradeDao.java:410)
at org.apache.dolphinscheduler.dao.upgrade.UpgradeDao.upgradeDolphinScheduler(UpgradeDao.java:258)
at org.apache.dolphinscheduler.dao.upgrade.DolphinSchedulerManager.upgradeDolphinScheduler(DolphinSchedulerManager.java:117)
at org.apache.dolphinscheduler.dao.upgrade.shell.UpgradeDolphinScheduler.main(UpgradeDolphinScheduler.java:36)
Screenshots:

version:
dev

because of pull request #3053 , the t_ds_process_definition_version was added.
I delete upgrade-dolphinscheduler in dolphin_api_service.py, because there is upgradeDolphinScheduler in CreateDolphinScheduler.

I think the problem is in the schema file. Not here.
In order to ensure that the table structure metadata is up to date, we need to execute the upgrade-dolphinscheduler.sh script at startup. This script will automatically check the current version number and execute the corresponding upgrade sql file.
Therefore, we require that the sql file in the schema must meet the ability of repeatable execution.
In order to achieve this goal, if we need to create the table t_ds_process_definition_version, then we should use
create table IF NOT EXISTS t_ds_process_definition_version;

or
drop table if exists t_ds_process_definition_version;
create table t_ds_process_definition_version;

I think the problem is in the schema file. Not here.
In order to ensure that the table structure metadata is up to date, we need to execute the upgrade-dolphinscheduler.sh script at startup. This script will automatically check the current version number and execute the corresponding upgrade sql file.
Therefore, we require that the sql file in the schema must meet the ability of repeatable execution.
In order to achieve this goal, if we need to create the table t_ds_process_definition_version, then we should use
create table IF NOT EXISTS t_ds_process_definition_version;

or
drop table if exists t_ds_process_definition_version;
create table t_ds_process_definition_version;

ok, thank you, I correct it.


Increase the performance of some xml and html helpers

Summary
We saw some performance issues in https://github.com/exceljs/exceljs/issues/742 that this PR tries to solve
Test plan
Both helpers are already tested, this just refactors their implementation.

This is good. Regexp way of finding whether or not we need the escaping is even faster than the loop I suggested #742 .
In my test I got 25% increase in performance. I have 43K rows of data.  It takes 20 secs to export. 50% used to go to create the spreadsheet and 50% used to go to write out the files. Out of these 10 secs 5 secs went to serialize various elements and 5 secs went to xmlEncode() calls. With the patch the xmlEncode dropped to near zero so export now takes 15secs.
Please accept this PR.


Error EMS survival.lua

I have a error line 168 in the file survival.lua
sceenshot of the console http://image.noelshack.com/fichiers/2017/20/1495236328-abd137a3cfb24a23825f719f87c2d5972.png

Resolved.


Configure Azure Pipelines

 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.:x: heuyang sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Filter out specs from coveralls

#17

Coverage decreased (-42.06%) to 57.821% when pulling 260cfbff8cf9b19061c0b615a61881be05316bef on coveralls_config into 267f9cc9a2a5131f2533ad5c70909b8210e87ea9 on master.

Coverage decreased (-42.06%) to 57.821% when pulling 260cfbff8cf9b19061c0b615a61881be05316bef on coveralls_config into 267f9cc9a2a5131f2533ad5c70909b8210e87ea9 on master.

Coverage decreased (-42.06%) to 57.821% when pulling 260cfbff8cf9b19061c0b615a61881be05316bef on coveralls_config into 267f9cc9a2a5131f2533ad5c70909b8210e87ea9 on master.

Coverage decreased (-0.6%) to 99.296% when pulling d9c0f581458b8caa88341c64fb7c5b2a85857489 on coveralls_config into 267f9cc9a2a5131f2533ad5c70909b8210e87ea9 on master.

Coverage decreased (-0.6%) to 99.296% when pulling d9c0f581458b8caa88341c64fb7c5b2a85857489 on coveralls_config into 267f9cc9a2a5131f2533ad5c70909b8210e87ea9 on master.


R134a Medium

Reported by nicolas.albarello on 15 Jan 2014 15:36 UTC
The R134 medium works in the provided examples (using volume and short pipe) but fails when using it in other fluid components (e.g. DynamicPipe). The reason for that is the use of pTX functions with a two-phase fluid.
Could you provide a fixing procedure for this ?
Thanks,

Migrated-From: https://trac.modelica.org/Modelica/ticket/1394

Modified by dietmarw on 20 Jun 2014 10:57 UTC

Modified by wischhusen on 20 Jun 2014 11:12 UTC

Comment by hubertus on 20 Jun 2014 16:12 UTC
R134a has been implemented by XRG, owner is changed back to Stefan.

Comment by wischhusen on 23 Jun 2014 16:15 UTC
This issue is known. The problem is, that _pTX-functions are not a good choice for twophase media. In the two-phase region the enthalpy cannot be determined from pressure and temperature. Nevertheless, two-phase is an important operation region for refrigerants.
The reason, why _pTX functions are used in Modelica.Fluid is certainly the simpler parameterization of the initialization and boundary conditions.
Anyhow, the functions of R134a are just intended for p,h states to allow a proper solution in any domain. Models that use R134a should avoid _pTX functions. If the Modelica.Fluid pipe does not, it cannot be used with R134a or has to be changed to allow an initialization with _phX.

Comment by hubertus on 23 Jun 2014 19:03 UTC
The same argument is of course also true for the IF97 steam tables, and still the functions are also available with pTX as inputs. There are many situations in which it is known that the fluid is in one phase only, or I know that I have a phase separating device, and then these functions are appropriate. It is much worde to have inconsistent usage and user interface in different properties that follow the same interface. The _pTX funtions are available in the interface, and they have to be provided by any compatible implementation. This would be different if our two-phase interfaces would not contain the _pTX functions. If part of the functions are not implemented, the interface is useless and confusing.

Comment by wischhusen on 24 Jun 2014 07:29 UTC
"The _pTX funtions are available in the interface, and they have to be provided by any compatible implementation."
Yes, that's why we implemented _pTX functions with an error message to explain the failure potential. The media model is just declared to be valid with p,h as states.

Comment by hubertus on 7 Dec 2015 13:56 UTC
Can you fix this? This is a pretty old issue

Comment by wischhusen on 8 Dec 2015 15:19 UTC
I think the issue comes from Modelica.Fluid components which call _pTX functions allthough they shouldn't. Careless use of _pTX functions close to the phase boundaries will lead to large failures for the enthalpy. This is why the supply of the functions was refused.

Comment by hubertus on 8 Dec 2015 15:35 UTC
Well, but in my mind this is really a very wrong way to fix the problem: if someone uses a function in an API (which I'd say the medium interfaces are) in the wrong way, it is not a good ideas to simply not implement the function, which still exists for a good reason. So I'd suggest to file tickets for the bad usages in Modelica.Fluid, with high priority and urgency, and go ahead and complete the functions in R134a. If there is a partial function in the interface, it is a promise for the implementation to be there, and a strict checking Modelica tool should reject the complete R134a package as faulty, and rightly so. If this is not fixed until the next major release that allows non-backwards compatible changes, the package should be removed. I want to strictly only have compliant and correct code in the MSL. As you can see, I updated the Severity, because this simply is non-compliant code and should have been rejected through better testing earlier.

Comment by wischhusen on 14 Dec 2015 09:11 UTC
In order to overcome problems with ambiguous inputs close to the phase boundary the functions will be implemented with a safety margin of 2 Kelvin around the two-phase region (and 0.1 bar with regard to the critical point). Within this margin the pTX functions will throw an error which is required to keep the user aware of potential errors caused through measurement errors, other implementations of R134a properties and so on.

Comment by wischhusen on 21 Dec 2015 14:23 UTC
Was fixed with a4fbb252da70bc0a4faabc511881e44e09e07449.

Changelog modified by wischhusen on 21 Dec 2015 14:23 UTC
Added new functions to calculate setState_pTX


.NET MAUI Community Toolkit - RatingView

This pull request introduces the documentation for the RatingView control, to accompany the code under .NET MAUI Community Toolkit PR for RatingView.
Only merge, after the code PR has been merged.

@bijington Just a nudge to remind you that this is here and ready for review.

@GeorgeLeithead thank you for this. Most comments I think are easily addressed.
Also I think we need to update the top.yml file for any new file added to the docs

Updated the TOC correctly.

@GeorgeLeithead thank you for this. Most comments I think are easily addressed.
Also I think we need to update the top.yml file for any new file added to the docs

I believe I updated the TOC.yml and this covers the change required.


Publish release 3.0.5 to PyPI

The critical bugfix release 3.0.5 has been generated. However, it does not yet appear to be published on PyPI. This release restores the previous API of returned structures.

@jchodera, @Lnaden, and @mrshirts, I believe this is something only one of you can do. Thank you for continuing to advance this package!


[UI] Selected row name change

Current Behavior
when selected a row from the table, it appears ()rows selected.
Desired Behavior
change that rows selected to configuration type, example: ()pattern(s) selected / ()filter(s) selected .....
Implementation
Implement this for patterns, filters, applications, and performance profiles
Mockups

Contributor Guides and Resources

🎨 Wireframes and designs for Meshery UI in Figma
🖥 Contributing to Meshery UI
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

I'd like to give it a shot. Can you please assign it to me?

Sure @theBeginner86 go ahead 🚀

Please have a look at the PR 😁😊


Restrict organization creation with same name and description under particular parent organization

Purpose

Organization with same name and description can't be allowed with the sub organization tree with respect to a particular parent organization due to the possible conflicts when trying OrganizationLogin authentication flows.

Restrict organization with same name for particular organization sub tree. That is addressed by this PR https://github.com/wso2-extensions/identity-organization-management-core/pull/29
and hence closing this PR.


add actionlint gh action

closes #322

This change is

got error --> """reviewdog/action-actionlint@v1 is not allowed to be used in pixeltable/pixeltable. Actions in this workflow must be: within a repository that belongs to your Enterprise account, created by GitHub, or matching the following: abatilo/actions-poetry@v2, conda-incubator/setup-miniconda@v3, <EMAIL_ADDRESS>Great to see lockdown on which actions can be used.
So, i guess this warrants discussion on https://github.com/pixeltable/pixeltable/issues/322 ... do we want this action?  Do we want this functionality but aim to have a more custom GH Action rather than a more general external dependency?


Call out no support for full database REST API

For background, see https://cockroachlabs.slack.com/archives/CC5CX8EKE/p1629155750071600, https://github.com/cockroachdb/cockroach/issues/69146, and https://github.com/cockroachdb/docs/issues/11083#issuecomment-928637729.

Thanks for filing this! I think this is a good place for us to sort out our messaging here.
This was an interesting read for me to learn about how different pieces here fit together: https://blog.cloudflare.com/modernizing-a-familiar-approach-to-rest-apis-with-postgresql-and-cloudflare-workers/
Another thing that I think would be relevant for us to compare against is the Amazon Data API: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/data-api.html


x/tools/gopls: store overlays on the snapshot instead of the session

@findleyr discovered a bug where if a textDocument/didOpen opens an overlay that does not exist on disk before the initial workspace load runs, we will attempt to read a file that does not exist on disk.
Snapshots should store their overlays so that we don't attempt to read data that came in after the snapshot was created.

Fixed via https://go-review.googlesource.com/c/tools/+/218321.


Dev

@oliverw Can a mention be added to the release notes for Release 42 denoting the removal of built in Slack notifications -- I just accidentally discovered that when I popped into the notification channel and saw they had stopped being sent.

Damn. Sorry, didn't realize that anybody except us was using them. I've attached an utility that can be used as replacement. Be advised that the project contains link references to some Miningcore source files. In order to build it, the Miningcore sources have to be located two directories up.
WsListener.zip

Not a problem, it wasn't a required feature but a "nice to have". WsListener looks like a better solution as well with the addition of Discord and being isolated from the pool itself. We were relaying our messages to a Rocket.Chat instance via the Slack interface but now can do so more directly


Antora Documentation Site for EDUX Java Machine Learning Library

Description
This ticket outlines the creation of a Antora documentation site for the EDUX. The goal is to provide users with a comprehensive guide on integrating the library into their Java projects and utilizing its machine learning algorithms.
Objectives

Set up a basic Antora site structure.
Document the process of including the EDUX library in a Java project.
Provide code examples for each supported ML model.

Additional Notes

Include a section for hardware acceleration requirements.
Provide a benchmark section linking to the discussion on algorithm comparison.

The code examples can be found in the example directory of the EDUX repository.

dropped


CONSUME_FROM_LAST_OFFSE and CONSUME_FROM_TIMESTAMP doesn't work

The issue tracker is ONLY used for bug report and feature request. Keep in mind, please check whether there is an existing same report before your raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following:
BUG REPORT

Please describe the issue you observed:

What did you do (The steps to reproduce)?
使用一个新的消费组消费指定topic中的消息，不需要历史信息，指定CONSUME_FROM_LAST_OFFSE或者CONSUME_FROM_TIMESTAMP

What did you expect to see?
从最新的offset开始消费或者从指定的时间点开始消费

What did you see instead?
消费了全部的历史消息

Please tell us about your environment:

Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

FEATURE REQUEST

Please describe the feature you are requesting.

Provide any additional detail on your proposed use case for this feature.

Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

sub-task1-issue-number: sub-task1 description here,
sub-task2-issue-number: sub-task2 description here,
...

Have the same problem.
A new consumer group will request offset from broker(MessageMode is CLUSTERING), and if the first record of the topic is in commitlog file, then the broker will return 0 and consumer will consume from the start.

Have the same problem.

@flackyang @scarletyoung @kevinwang0224
consumer rule : consumers always want latest messages more than old ones.
check how many messages in your topic's queues. found there's a trick, RocketMQ thinks if there're not manay messages, you would get all messages. even if you set CONSUME_FROM_LAST_OFFSE

Is the issue fixed? or have any work arround solution? I have the same problem in 4.7.0


Black formatter cannot format Python file

Hi,
I added the configuration in the settings.json and removed black form python formatting provider, when I try to format a python file I get this error:

Extension 'Black Formatter' is configured as formatter but it cannot format 'Python' -files.

Any suggestion?

Not sure if relevant with OP's situation, but Black Formatter fails to format any python file outside the opened folder (e.g. a file directly opened with "Open with VSCode" context menu on Windows) for me.

Extension 'Black Formatter' is configured as formatter but it cannot format 'Python' -files.

@dbaeumer Any idea why this error might be occurring?
@Azureblade3808 That might not be the same issue, can you create a separate one and include the logs from Output > Black Formatter.

In most cases the extension has not registered a format provider yet. Could it be that the extension is not yet properly activated?

The error message I got is identical to OP, and there are nothing in logs even if log level is set to "debug".
To reproduce:

Windows ( I used both Windows 7 and Windows 10 ).
Start VSCode without opening any folder.
Open a python file using "Open with VSCode" in context menu.
Try to format it.

I too see the exact same message when attempting to format the selection in a Python file.  Formatting an entire Python file, however, works as expected.

This issue could be caused due to https://github.com/microsoft/vscode-black-formatter/issues/124#issuecomment-1241792508 or https://github.com/microsoft/vscode-black-formatter/issues/136.

I confirm that with an opened workspace the extension is working correctly.

Hi -- I am using the pre-release version of the ms-python.black-formatter extension in VS Code 1.73.1 , and I still get this exact error message whenever I use the command "Format Selection" in a Python file (after selecting some lines of text). However, using the command "Format Document" on the exact same file succeeds in formatting the entire document. Is it expected to be unable to format selections within a document even after #140 was merged?

Extension version info from the extension details page:
v2022.7.13061128
Last released: 11/2/2022, 07:33:35

Is it expected to be unable to format selections within a document even after https://github.com/microsoft/vscode-black-formatter/pull/140 was merged?

@maxbane yes, for now you will see an error message when attempting to format selection.

The error happens when text is selected. It goes away is you save without any text selected. This happens while using the migrated tooling. We need to be able to turn formatting off when saving while text selection is active.

I was also getting the same error and only @teleprint-me solution fixed the problem with Python and Jupyter files.


BLOCK and WIDTH sharding support needed in Tilize

Currently only HEIGHT sharding is supported!!

we will cover this in our generality push for tilize, untilize, and sharded ops around mid November

@mywoodstock is this blocking models? Should this be a p0?


Dolphin's disk properties crash the WM

Please describe the bug
Opening the disk properties window in Dolphin crashes the WM
Steps to reproduce:
Open dolphin select a drive and click properties
Expected behavior
WM not crashing

fixed with the last commit


it wont build on windows 10

i get this error
  = note: LINK : fatal error LNK1181: cannot open input file 'Packet.lib'

error: could not compile `dispatch-proxy` due to previous error

well i got it to install but I had to find and download Packet.lib then put it in C:\Users%Username%.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\x86_64-pc-windows-msvc\lib.

@Kodi4444 Where did you get packet.lib from?

Wait I found it. For anyone also stuck on the same issue you need to get the right packet.lib for your toolchain from WinPcap 4.1.2 Developer's Pack

Same problem with win 11 + gnu toolchain (mingw64)
Fixed by installing Npcap (which is recommended by WinPcap as it's not maintained anymore)
Packet.lib from sdk/lib/x64 as mentioned above fixed the build error
Had to install it too for packet.dll error
Works fine now

Fixed in #2 (thanks @gregyjames!)


In a release in Azure Pipelines, Build.BuildId is a hash, not an integer as shown in documentation

I was attempting to use "Build.BuildId" in a release pipeline in a Azure pipeline. Build.BuildId maps to Release.Artifacts.{alias}.BuildId as per here :

which in turn is suppose to look like "130" for Azure pipelines.

But it is a hash instead. Should the example be updated accordingly ?
I switched to use Release.ReleaseId.

@dparker  Thank you for the feedback, assigning this to the author for review.


isPlayerVisible() functionality

Hi !
I have been using this repo to build a simplified CS GO game environment where I can test new ideas and build statistical models based on past games and have been getting on well so far.
Unfortunately, I am currently having difficulty though trying to decern when a player is visible by the enemy team (i.e. when they would appear on the enemy radar). This is important information to me as knowing the match state from the perspective of each of the teams is necessary to build accurate models.
Does anyone know of any functionality to do this? I have tried experimenting with the 'entity_visible' event callback but with no luck (I could not get any callbacks from any DEM files tested).
If not I will probably use some sort of basic line of sight algorithm, although, this will be quite an intensive operation so I am hesitant to take this route.
Thanks !

Fixed.
For anyone interested player_object.get_prop('DT_BaseEntity', 'm_bSpotted') provides the functionality required.


Probably unwanted use of constant expression: Math.random().toInt().toString()

In the closed issue #406 we saw a reference to a weird line of code regarding a HTTP header cwa-fake:
https://github.com/corona-warn-app/cwa-app-android/blob/970e8b859cff3c8beeca83ac83e9ed534927107a/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/http/WebRequestBuilder.kt#L182-L183
The expression Math.random().toInt().toString() will always evaluate to "0", since 0 <= Math.random() < 1 and Double.toInt() simply cuts off the fractional part.
I do not fully understand the purpose of the cwa-fake header, but it seems to me that the code for it was meant to fill it with a random value, when the faked flag is true. But as it is, it will always be set to "0", regardless of the value of faked. This might be an oversight of some kind, so I want to bring this to your attention explicitly with this issue.
And since this is a "question" type issue, here is my question:
Is it safe to always set the header to "0", or is this something that needs to be fixed?
Additional information
The initial commit of this repository had 4 instances of the expression:
https://github.com/corona-warn-app/cwa-app-android/blob/4804888ad0d3ee4c4abfb85294bab3006b75c250/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/http/request/KeySubmissionRequest.kt#L45-L46
https://github.com/corona-warn-app/cwa-app-android/blob/4804888ad0d3ee4c4abfb85294bab3006b75c250/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/http/request/RegistrationTokenRequest.kt#L60-L61
https://github.com/corona-warn-app/cwa-app-android/blob/4804888ad0d3ee4c4abfb85294bab3006b75c250/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/http/request/TanRequest.kt#L50-L51
https://github.com/corona-warn-app/cwa-app-android/blob/4804888ad0d3ee4c4abfb85294bab3006b75c250/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/http/request/TestResultRequest.kt#L50-L51
Then in commit b195623 the usages were unified into the current code snippet referenced above. If this really is an issue, it existed before this repository was created.

After further digging I found the description of the header in question:
https://github.com/corona-warn-app/cwa-server/blob/b8afdce9a3bc8fd927fe4ec9be2e910ee8f1635d/services/submission/api_v1.json#L28-L30

Requests with a value of "0" will be fully processed. Any other value indicates that this request shall be handled as a "fake" request.

So this is used to send a request that will be ignored by the backend. I assume it is there for generating traffic to hide any real submission behind fake requests, protecting the users privacy against side channel attacks?
Currently, the only call site is hard-coded to set the faked flag to false, so for now, this is not an issue. But if this would be actually used later on, it would result in sending requests not marked as fake, when they actually should be marked as fake.

Based on my assumptions above, I have made a small fix that should resolve the potential issue. Of course, if the randomness is actually wanted, there needs to be a different fix.

@LostMekka i think corona-warn-app/cwa-documentation/issues/225 on the documentation repo is relevant here.
This feature will be implemented in Version 1.1 as stated in the comments.

That is good to hear. I assume that, when implemented, the fake requests are triggered by some scheduler calling asyncSubmitKeysToServer(faked = true, ...), and the use of randomness at this particular point in the code is not wanted. Is that correct?

Hi @LostMekka, this issue will be closed now, see https://github.com/corona-warn-app/cwa-app-android/pull/463. Many thanks for your contributions.
Best wishes,
DS

Corona-Warn-App Open Source Team


Regarding security concern

Since we are adding two very important piece of information:

Transferwise personal API token
Gmail password

As I went through your code, it seems safe at the moment.
But the most important thing is right now the docker version is set to latest.
Is there any possibility of you doing a fraudulent activity with regards to my personal information with you pushing a new docker version image? Have you thought about this?

It is a self hostable solution so I don't have access to any of your containers or the credentials.
And, the runtime env variables(token and Gmail password) are externally injected into the binary before running it, so it's not stored/copied anywhere in the built docker image.
Also, if there's a new release it doesn't affect your deployment as long as you decide to not fetch the latest image again.
Sorry if I am missing your point but I don't see how any of it is a security concern?

Thank you for your reply, I really like the idea of transferwisely.
My concern is simple, let's say you decide to fetch all the gmail_id and password Or API token. And Inject a small piece of code in your codebase to send it to you :)
How can you make the user believe that you can't do this even if it's intentionally?

Isn't that the case with all of the opensource libraries or packages you use?
Just, for example, you must have used viper, right?
Pretty popular configuration package for go, so how do you know that it isn't secretly passing your production config somewhere? Simple, by reading the implementation in case of such concerns, coz it's all opensource. I hope you get the point.
Also, about the docker image on docker-hub, that's built using the same Dockerfile, for the ease of end-user. In case of any other kind of concern, you can feel free to build your own image using the Dockerfile.
Please, close the issue if it clarifies your concern?

Yes, you are right that's a concern. I get that point.
Thing is, Viper has 13300 github stars so it is self-understood that we can trust on that product up to a certain extent. Here on transferwisely, we are directly injecting some too important piece of information.
If I had to docker build then I wouldn't open the issue. Is it possible to version control docker-hub with releases? So we don't need to go over the changes done in the code.

Releases are versioned. You can check it here for the latest release.
https://github.com/anuragdhingra/transferwisely/releases/tag/v1.1 commit a594dad
https://hub.docker.com/r/anuragdhingra/transferwisely/builds
Is this what you were looking for?

Yes, I am looking for something similar. Thank you for pointing out to the builds. Builds are currently updating images built under latest tag.
Consider:
https://hub.docker.com/r/tensorflow/tensorflow/tags
Here you can see rc image tags but in your case, it's only one and that's latest. So, can that be version controlled?

Okay, I get your point. But you can verify the image builds by the release commit hash as pointed above.
Also, the older release v1.0 should be tagged with the correct version, will do that. Thank you.

Closing it for now.


Server down :(

Hi, loving the tool and integrating it into my daily use, but looks like the server is down :(

Looks good again


Final fixes for 5.2.0 release

This PR serves as my working changes to 5.2 before release.

traceLast is deceiving, as if there is time between the last emission and completion that time is counted. Name it traceUntilComplete instead.
traceWhile was just an opposite of traceUntil which doesn't do it's name justice. I've since super charged it, traceWhile will trace starting with an emission that passes the test and ending with the first failure. It will also produce multiple traces, e.g, of(false, true, false, true, true, false).pipe(traceWhile('while', a => a)) will produce traces for the time between the 2nd and 3rd emission and the 4th and 6th emissions. Imagine it's use in a game loop: traceWhile('timePlaying', state => state.isPlaying && !state.isGameOver)
Added orComplete options to traceUntil and traceWhile
Needed carets on the versions ^^^^^^^^^^!
Collection doc path should be optional
traceComplete has to be after first as isStable itself is not completing
AngularFirePerformance was not eagerly initializing performance monitoring
Ack, my performance operators weren't lazy! Fixed
Inject the default app into AngularFirePerformance
Dropped the Angular 8.0-rc from package.json as it's released now
Moving all the deps from the schematic to peer and adding them during the ng add step
Making the ng add more forgiving if they already have a .firebaserc or firebase.json
Added ng7 and ng8 build tests
Dropped unneeded stuff from the ngmodule package.json bringing them back inline with APF, though should update to AFP v8
Indicate side effects so webpack doesn't wreak us
Making AngularFirePerformance lazy and replacing dynamic import with empty() in the UMD
Replacing dynamic import of firebase/messaging with empty() in the UMD, fixes #1938

@jhuleatt Here are the traceWhile changes I mentioned.

Published to @canary as 5.2.0-canary.19b97c5. I'm going to give this a spin in my test projects.

Published 5.2.0-beta.5 to @next with above fixes.

I'm happy with this build, cutting as 5.2.0-rc.1

Cut 5.2.0-rc.2

Cutting 5.2.0-rc.3 which utilizes dynamic import for performance monitoring & fixes both the performance and messaging modules in server builds (replacing from(import('firebase/messaging')) with empty() in the UMD).


apply not idempotent

Our implementation of bootc update --apply has an obvious bug; we don't handle the case of
bootc update followed by a bootc update --apply.
We need to compare booted/staged and dispatch on that.

I'd like to take a stab at this tomorrow

I'd still like to do this, but on my first foray I ran face-first into my own ignorance of the technical details of ostree.  So I've been trying to crash course that to get up to speed.  I'll be out starting tomorrow until after the holiday, so if someone else is motivated to take this and run with it, by all means have at it.  Otherwise I'll resume this in January.


Bug  - Documentation link broken

Describe the bug
One of the links in the readme file seems to be broken.
Did you try recovering your dependencies?

(Write your answer here.)
Which terms did you search for in User Guide?
[React preset] https://neutrino.js.org/packages/react/

Environment

(paste the output of the command here.)
Steps to reproduce

(Write your steps here:)

Expected behavior

Should redirect to one of the links
Actual behavior

Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Did you mean https://neutrinojs.org/packages/react/ ? neutrino.js.org doesn't exist.

yes

According to their github repo, neutrinojs is no longer being developed and the project has been deprecated/archived:
https://github.com/neutrinojs/neutrino/issues/1707


[Updatecli] Update version to 2.229-jdk11

! Experimental project
This pull request was automatically created using olblak/updatecli
Based on a source rule, it checks if yaml value can be update to the latest version
Please carefully review yaml modification as it also reformat it.
Please report any issues with this tool here

Thanks @timja for merging this kind of pull request quickly


[move-docs] polish tutorial

Motivation
Some small edits to the move tutorial.
Have you read the Contributing Guidelines on pull requests?
yes.

/land


Filter Linux platforms for SRPM builds

Remove Linux platforms duplicates.
Signed-off-by: Violeta Sebe<EMAIL_ADDRESS>

@AdamBrousseau please review, thank you!

Is this change required because we are currently running duplicate specs in the 11 builds?
Yes, it is.

Will it be required when we split into 2 separate build for 11?
No, it won't.


Can't install on nova 3

I think you can remove
    "laravel/nova": "^2.0"
from your composer.json

Thanks for reporting this issue @cord !
This has now been fixed as a new patch release [v1.0.1] d762079.


Support HMD-mounted orientation, for Orion update?

Hi, I have a leap device mounted on my HMD, with the Orion update. I'd like to use the leapjs library and THREE.js. The coordinates are all coming out as if the leap were horizontal. Is there, or could we add, a setting like setOptimizeHMD() to transform coordinates automatically into HMD-mounted orientation?
Or similarly, would I need to write a plugin that does this? Is it safe/reasonable to modify the frame object dynamically?

It's been a while since anyone's touched it, but the transform plugin was designed for exactly this.  Have you seen/tried/discovered any problems with this?
http://leapmotion.github.io/leapjs-plugins/main/transform/
 Leap.loop()
    .use('transform', {
      vr: true
    });

That's exactly what I needed, thanks! :smile:


Added PyCon India 2017

Details of the conference:

Website: https://in.pycon.org/2017/
Date: November 2 - 5, 2017
Venue: JNU, New Delhi
Description: The premier conference in India on using and developing the Python programming language is conducted annually by the Python developer community. It attracts the best Python programmers from across the country and abroad.

Thank you! :smile:

You're welcome @nikhita !


[Help] looking for contributors who maintain volcano integration

The volcano integration code is a bit outdated, and the feature isn't tested. So we are looking for contributors who can maintain the feature.
Removing volcano integration might be good if we can not find any contributors.
ref:

https://github.com/kubeflow/training-operator/issues/1738
https://github.com/kubeflow/training-operator/issues/1671
https://github.com/kubeflow/training-operator/issues/1825

/help
cc: @kubeflow/wg-training-leads

@lowang-bh offered to help.

We are looking for contributors in the mpi-operator as well.
https://github.com/kubeflow/mpi-operator/issues/535

/close

cc @k82cn


Updating to new Catlab version

SemanticModels has fallen really behind Catlab development. We need to bump that up to a modern version of Catlab.

I'll take lead on this starting Monday. I have a really good understanding of the update (since I wrote most of them) and don't think it will be too much for me to do

👍, probably also a good time to clean up all our outstanding branches.


[refactor] Move rendering of Item 3D metadata into separate classes.

This should be simple: Create a mapping of item type (using Item instances) to metadata renderers (new class needed) and let ItemMetaWorldRenderer use that mapping to find and invoke the correct renderer.
(Note that metadata is only shown in creative)
Possible uses for 3D item metadata:

Render wirebox around selected entity with Wand/NPCEditor.
Render 3D cursor and bounds for Voxelator tool.
...

Note: Make sure that the code allows adding a 3D metadata renderer to ANY item (vanilla or TC, it shouldn't matter).

What exactly do you mean by this? What is a metadata renderer?

Its the thing that takes a Item and renders information about it into the (3D) world.

Alright, done


[docs] Improve notification color

Reverting the color of the notification to be red. It has bigger contrast, and it is usually the color used for notifications.
Previously

Now

This makes me think about a past discussion where we realized that danger is probably a better name than error (It works better in this context). But this is legacy, unlikely we can change it anytime soon.

This makes me think about a past discussion where we realized that danger is probably a better name than error (It works better in this context). But this is legacy, unlikely we can change it anytime soon.

color="danger" was the first prop I tried, then I saw that the name is error. I thought it was just me :)


Missing directories and directory globs

Hello
I'm facing the same problem described in issue #81. In my use case, I'm monitoring logs stored in dynamically generated paths (dynaFile output of rsyslog) and the list of possible directories is not known in advance.
Q1: Is there any chance that grok_exporter will overcome the current implementation limitation about missing directories in the future ?
Q2: Would you consider supporting globs on the directory part of the input paths ?
Thanks.
I also like your project and keep on the good work !

Hi,
sorry for the late reply. Let me start by explaining the reason for the current limitations. grok_exporter on Linux uses the inotify system call to monitor log files. The manpage of inotify says:

Inotify monitoring of directories is not recursive: to monitor subdirectories under a directory, additional watches must be created.

For example, if grok_exporter watches logfiles in /a/b/c/*.log, it creates one inotify watch for each logfile (to get notified when new log lines are written or when the log file is truncated), and additionally it creates one inotify watch for the directory /a/b/c/ (to get notified when a new log file is created, or an existing one is moved or deleted). That's why grok_exporter supports wildcards only on a file level and why it cannot handle removing the log directory.
Step 1 towards a more generic implementation would be to handle removing the log directory. In the example, that would mean grok_exporter creates an additional inotify watch for directory /a/b/ to get notified when /a/b/c/ is deleted, moved, or created. We could implement this recursively, creating directory watches for /, /a/, /a/b/, and /a/b/c/.
Step 2 would be to support wildcards for directories, like /a/b/*/*.log. Then we would need to watch all directories matching /a/b/*/. While this is simple in many cases, there are corner cases that make this difficult and error prone. For example, I imagine it difficult to handle a small script with the following three commands mv /a/b/c /a/b/d; mkdir /a/b/c; mv /a/b/d/*.log /a/b/c/. Moreover, directories /a/b/c/ and /a/b/d/ might be mount points on different file systems, or they might be symbolic links.
Step 3 would be to support sub-directory trees with arbitrary depth, like /a/b/**/*.log meaning all files matching *.log in any subdirectory tree within /a/b/. This is even harder, because it should support users moving directories and files up and down the tree.
As for the future plans: I think step 1 will be supported soon, and step 2 with limitations later.

Thank you for the clear and very detailed answer,  now see the challenge of such feature.
While I completely understand the benefits of using inotify at a file level, I wonder what would be the problems a lot more naive approach for directories: a background goroutine periodically resolving the globing and creating new handles for discovered files (and/or directory leaf)  ?

Thanks @fstab for your detailed answer.
In our project we have a similar "problem" and would be happy about a solution of "Step 2".
On several management servers we are facing following use case (customer specific folder with several logs):
/a/customer-1/a.log
/a/customer-1/b.log
/a/customer-2/a.log
/a/customer-2/b.log

We have the advantage that our configuration management tool can create the configuration in such detail, but a "glob" would simplify the configuration and the underlaying code of our configuration management solution...

In a similar case as @conturNDE I also believe globing of directories would be quite useful as well as removing the failure for missing directories.


e2e test for doc site

there're more and more guides introuduced into our docs site, consider add test for them(at latest for tasks)?
we can learn from what istio.io did?

I think this will increase complexity and makes our CI more flaky

We have tests for checking dead links but no tests for typos?

We have tests for checking dead links but no tests for typos?

yes, no tests for typos or wrong configurations.


Can ReactiveSystem only react to part of the component in the group?

Hi guys! Want some help. Do you know how to create collector for reactiveSystem which only respond on part of the group? For example, a group has humanTag and velocity, I only want the system only react to when velocity change.

Hi @eterlan!
You can use velocity as a trigger and filter for humanTag
protected override ICollector<GameEntity> GetTrigger(IContext<GameEntity> context) =>
    context.CreateCollector(Velocity);

protected override bool Filter(GameEntity entity) => entity.hasVelocity && entity.isHuman;


Create the ControllerManager after robot was openned

This should fix #69
As mentioned in #69, creating the controller manager before opening the robot can lead to failures at runtime because
the ControllerManager provides services that require the robot to be already opened. If a 3rd party calls one of those
services before the robot is opened, that operation will fail.
By moving the creation of the ControllerManager after we try to open the robot, we ensure that no race condition will occur and that the robot will always be openned when the provided services are called.

Hi, @Yuki-cpp
Thank you for opening the PR.
I checked that bringup finishes normally and Initializing controllers does not failed with this change.
I will merge this PR.


error CS0246: The type or namespace name 'SampleSet' could not be found (are you missing a using directive or an assembly reference?)

Unity 2021.2

Hmm, this project turned out to serve my development needs more than it is a demo project. Thus I haven't really paid attention to housekeeping (no errors, works on other machines etc.)
That said, there's been a char-case problem with the packages folder that I fixed today. Please give it another try.
While we're at it: what's your intend using this project?


Windows support

I find this project is build with cargo/rust, how about building windows binary too?
rustup update
rustup target add i686-pc-windows-msvc
rustup target add x86_64-pc-windows-msvc
cargo build --release --target=stable-i686-pc-windows-msvc
cargo build --release --target=stable-x86_64-pc-windows-msvc

See also the github action for macos.
https://github.com/vicanso/pingap/blob/d685f9f751b39dcedea7fcccd04c11656e82663c/.github/workflows/publish.yml#L12-L36

Not supported by windows ！

I'm sorry, but since Pingora only supports Unix-like systems, so Pingap is the same. https://github.com/cloudflare/pingora?tab=readme-ov-file#systems


Invalid ruby in Gemfile raises confusing error

Error Report
Questions
Please fill out answers to these questions, it'll help us figure out
why things are going wrong.

What did you do?
I ran the command /home/foo_user/.rvm/gems/ruby-2.3.3@foo_project/bin/bundle update

What did you expect to happen?
I expected Bundler to update the gems. Because this fails, I wanted Bundler to give me a name for the Gem that has illformed requirements or a linenumber in my Gemfile to identify the root cause.

What happened instead?
Instead, what happened was that bundler quit with an error.

Have you tried any solutions posted on similar issues in our issue tracker, stack overflow, or google?
I tried to:

find illformed requirement
update rubygems package with gem update --system
downgrade to bundler 13.x, which works

Have you read our issues document, https://github.com/bundler/bundler/blob/master/ISSUES.md?

Tried to, but gitbhub it gives me a 404.
...
Backtrace
Gem::Requirement::BadRequirementError: Illformed requirement ["~> 2.3.3\n.0"]
  /home/foo_user/.rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/requirement.rb:101:in `parse'
  /home/foo_user/.rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/requirement.rb:131:in `block in initialize'
  /home/foo_user/.rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/requirement.rb:131:in `map!'
  /home/foo_user/.rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/requirement.rb:131:in `initialize'
  /home/foo_user/.rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/requirement.rb:59:in `new'
  /home/foo_user/.rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/requirement.rb:59:in `create'
  /home/foo_user/.rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/dependency.rb:59:in `initialize'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/dependency.rb:81:in `initialize'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/definition.rb:798:in `new'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/definition.rb:798:in `expanded_dependencies'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/definition.rb:252:in `resolve'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/definition.rb:176:in `specs'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/definition.rb:164:in `resolve_remotely!'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/installer.rb:226:in `resolve_if_need'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/installer.rb:78:in `run'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/installer.rb:24:in `install'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/cli/update.rb:55:in `run'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/cli.rb:221:in `update'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/cli.rb:20:in `dispatch'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/cli.rb:11:in `start'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/exe/bundle:32:in `block in <top (required)>'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/lib/bundler/friendly_errors.rb:121:in `with_friendly_errors'
  /home/foo_user/.rvm/gems/ruby-2.3.3@global/gems/bundler-1.14.3/exe/bundle:24:in `<top (required)>'
  /home/foo_user/.rvm/gems/ruby-2.3.3@foo_project/bin/bundle:22:in `load'
  /home/foo_user/.rvm/gems/ruby-2.3.3@foo_project/bin/bundle:22:in `<main>'
  /home/foo_user/.rvm/gems/ruby-2.3.3@foo_project/bin/ruby_executable_hooks:15:in `eval'
  /home/foo_user/.rvm/gems/ruby-2.3.3@foo_project/bin/ruby_executable_hooks:15:in `<main>'

Environment
Bundler   1.14.3
Rubygems  2.6.9
Ruby      2.3.3p222 (2016-11-21 revision 56859) [x86_64-linux]
GEM_HOME  /home/foo_user/.rvm/gems/ruby-2.3.3@foo_project
GEM_PATH  /home/foo_user/.rvm/gems/ruby-2.3.3@foo_project:/home/foo_user/.rvm/gems/ruby-2.3.3@global
RVM       1.28.0 (master)
Git       2.11.0
Platform  x86_64-linux
OpenSSL   OpenSSL 1.0.2j  26 Sep 2016
rubygems-bundler (1.4.4)

Bundler settings
local.foo  Set for the current user (/home/foo_user/.bundle/config): "/home/foo_user/projects/foo-common"

Please share your Gemfile so we can attempt to reproduce the issue?

Here is my Gemfile:
source 'https://rubygems.org'

git_source(:github) do |repo_name|
  repo_name = "#{repo_name}/#{repo_name}" unless repo_name.include?('/')
  "https://github.com/#{repo_name}.git"
end

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '~> 5.0.1'
# Use postgresql as the database for Active Record
gem 'pg', '~> 0.18'
# Use Puma as the app server
gem 'puma', '~> 3.0'
# Use SCSS for stylesheets
gem 'sass-rails', '~> 5.0'
# Use Uglifier as compressor for JavaScript assets
gem 'uglifier', '>= 1.3.0'
# Use CoffeeScript for .coffee assets and views
gem 'coffee-rails', '~> 4.2'

# Use jquery as the JavaScript library
gem 'jquery-rails'
# Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks
gem 'turbolinks', '~> 5'
# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
gem 'jbuilder', '~> 2.5'
# Use Redis adapter to run Action Cable in production
# gem 'redis', '~> 3.0'
# Use ActiveModel has_secure_password
# gem 'bcrypt', '~> 3.1.7'

# Use Capistrano for deployment
# gem 'capistrano-rails', group: :development

gem 'activerecord-import'
gem 'awesome_print'
gem 'bootstrap', '~> 4.0.0.alpha6'
gem 'cells-hamlit', platforms: :ruby
gem 'cells-rails'
gem 'devise'
gem 'flutie'
gem 'hamlit-block', platforms: :ruby
gem 'hamlit-rails'
# languages
gem 'mini_racer' if RUBY_PLATFORM =~ /linux/i
gem 'money-rails'
gem 'pry-rails'
gem 'rails-i18n'
gem 'rchardet'
gem 'redcarpet'
gem 'rfc5646'
gem 'seed-fu'
gem 'simple_form'
# Thor > 0.19.1 print warnings on rails g etc. see https://github.com/erikhuda/thor/issues/538
gem 'thor', '0.19.1'
gem 'trailblazer-cells'
gem 'trailblazer-rails'

source 'https://rails-assets.org' do
  # required by bootstrap tooltips
  gem 'rails-assets-tether'
end

group :development, :test do
  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
  gem 'byebug', platform: :mri
  gem 'pry-byebug', platform: :mri
end

group :development do
  gem 'letter_opener'
  gem 'listen', '~> 3.0.5'
  # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
  gem 'spring'
  gem 'spring-commands-rspec'
  gem 'spring-watcher-listen', '~> 2.0.0'
  # Access an IRB console on exception pages or by using <%= console %> anywhere in the code.
  gem 'web-console', '>= 3.3.0'
end

group :test do
  gem 'brakeman', require: false
  gem 'bundler-audit', require: false
  gem 'capybara'
  gem 'factory_girl_rails'
  gem 'haml-lint', require: false
  gem 'rails-controller-testing'
  gem 'rspec-cells'
  gem 'rspec-rails'
  gem 'rubocop', require: false
  gem 'rubocop-rspec', require: false
  gem 'scss_lint', require: false
  gem 'shoulda-matchers'
  gem 'simplecov', require: false
end

# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]

ruby File.readlines('.ruby-version').first[5, 7]

The last line (ruby version) would contain 2.3.3 currently.

@wintersolutions I'm pretty sure that the last line is the cause of your problem. I also think you can achieve what you want by using ruby RUBY_VERSION instead.

@mvz you are right, works perfectly now. Idk why I did not see it because its kinda obvious now, especially since I wrote out what it does. Thanks a lot!

We should definitely have a better error message for this, thanks for bringing it to our attention!

Can you share the contents of File.read(".ruby-version").dump though, so we can write a test?

diff --git a/lib/bundler/ruby_version.rb b/lib/bundler/ruby_version.rb
index ebdefe63f..6fd65b5c1 100644
--- a/lib/bundler/ruby_version.rb
+++ b/lib/bundler/ruby_version.rb
@@ -21,7 +21,7 @@ module Bundler
       #   must not be specified, or the engine version
       #   specified must match the version.

-      @versions           = Array(versions)
+      @versions           = Array(versions).map {|v| Gem::Requirement.parse(v).last }
       @gem_version        = Gem::Requirement.create(@versions.first).requirements.first.last
       @input_engine       = engine && engine.to_s
       @engine             = engine && engine.to_s || "ruby"
diff --git a/spec/install/gemfile/ruby_spec.rb b/spec/install/gemfile/ruby_spec.rb
index 3f8957916..e06a5b320 100644
--- a/spec/install/gemfile/ruby_spec.rb
+++ b/spec/install/gemfile/ruby_spec.rb
@@ -86,4 +86,14 @@ RSpec.describe "ruby requirement" do
     expect(the_bundle).to include_gems "rack 1.0.0"
     expect(locked_ruby_version.versions).to eq(["5100"])
   end
+
+  it "allows requirements with trailing whitespace" do
+    install_gemfile! <<-G
+      source "file://#{gem_repo1}"
+      ruby "#{Gem.ruby_version}\\n \t\\n"
+      gem "rack"
+    G
+
+    expect(the_bundle).to include_gems "rack 1.0.0"
+  end
 end

Here is the version file (zipped since github won't accept it otherwise):
ruby-version.zip
Thanks for your help and the improvement!


Incompatible Bazel version with the docs

Click to expand!
Issue Type
Build/Install
Source
source
Tensorflow Version
2.11
Custom Code
No
OS Platform and Distribution
Debian 11
Mobile device
No response
Python version
3.8
Bazel version
5.1.1
GCC/Compiler version
9.3.0
CUDA/cuDNN version
11.2,8.1
GPU model and memory
RTX 3060/12G
Current Behaviour?
As it has been discussed https://github.com/tensorflow/tensorflow/issues/58461#issuecomment-1325666595 Bazel version used from the project is not aligned with the one in docs. Since .bazelversion file pinpoints 5.3.0, there is version incompatibility and build from source fails to start.

Happy to do a PR refactoring .bazelversion

Standalone code to reproduce the issue
Install bazel 5.1.1 and try to compile TF r2.10/2.11.

Relevant log output
Use other bazel version

Hi @sniafas !
Feel free to raise a PR.
Thank you!

Hi @sniafas !
I could replicate this issue for 2.11 with Bazel 5.1.1 for Cuda support. It asks Bazel 5.3.1 for GPU builds as you mentioned earlier and working as expected for 2.10.
Attached gist for reference.
Updated the documentation through PR#2158  instead of refactoring Bazel rc version.
Thank you!

Hi @mohantym,
seems like a good idea! (Ah i missed the opportunity of a small PR)

This hopefully should have been fixed https://github.com/tensorflow/docs/commit/67e8be9afda4baffadc821a0c99ca423e3e5e415 Thanks @sniafas @mohantym Feel free to reopen if any updates are needed.


fix: reconcile multiple models with transaction

Issue #, if available:
Description of changes:
This converts ReconcileAndLocalSaveOperation to take in an array of models of the same ModelType, as the remote models are enqeued from a sync query (results up to 1000), and subscription data (single remote model)
Performance 10k items:

10k items
1k page size
query for pending mutation and query for local mutations: There are 10 metric points each, but because predicate size is max 950 and page size is 1000, we actually end up performing 2 queries each, so 20 reads in total
queries for pending mutations: 0.43s
queries for local mutations: 0.235s
save model: 11.227s
save metadata: 12.925s
API calls + deserialize into objects has not changed: 10 calls * <1s each
Total time: 26.291s for 10k models
Compared to baseline: ~90-100s, this is approximately 400% faster

Performance 100k items:
this was fairly slow, about 20 minutes to save 54k items.
Performance 100k items, 30 items per ReconcileAndSave:
total time: 932s (15 minutes) for 100k items
Performance 100k items, 30 items per ReconcileAndSave, transaction on all operations:
total time: 460s (7.67 minutes) for 100k items
Performance 100k items, 30 items per ReconcileAndSave, transaction on all operations, debug logging turned off:
total time: 222s (3.7 minutes) for 100k items
Performance 100k items, 1k per ReconcileAndSave, transaction on all operations, debug logging turned off:
total time: 203s (3.38 minutes) for 100k items
Performance 100k items, 1k per ReconcileAndSave, transaction on all operations, debug logs removed and turned on:
total time: 113s (1.88 minutes) for 100k items, each reconcile took about 1s, at 100 reconcilliations (100k items/1k pages). this particular run was 10x faster than the baseline. More runs:

Iphone 12 Pro SImulator - 184.05s (reconcile took 1.7s each)
iPhone 11 device - 111s (reconcile took 0.7s)

Check points:

[ ] Added new tests to cover change, if needed
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Latest changes in lawmicha/4-2-reconcile-multiple-dispatch

actively working on lawmicha/reconcile-transaction https://github.com/aws-amplify/amplify-ios/pull/1237


[BUG] build_and_copy_rust_modules directory loop is broken and only catches the first module in the list

Describe the bug
The build_and_copy_rust_modules function in the setup script does not properly loop through the module directory. The filter function is a generator and is executed on the fly, so since directory changes occur inside the loop the os.path.isdir(f) part of the loop breaks.
To Reproduce
Steps to reproduce the behavior:

Add a new rust module in the rust directory that falls after the rust_example module alphabetically
Build and run the docker image
Shell into the running docker container
Execute the setup script with python3 setup build --lang rust -p /usr/lib/memgraph/query_modules
Observe that the new package is not built and copied to query_modules

Expected behavior
It's expected that all rust modules in the directory are built and copied to the output path except for rsmgp-sys.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
This can be fixed by changing the for loop in the build_and_copy_rust_modules function to the following:
for project in filter(
    lambda f: os.path.isdir(os.path.join(RS_DIRECTORY, f)) and f != "rsmgp-sys",
    os.listdir(RS_DIRECTORY),
)

Hi @dintorf! Thank you so much for detecting this issue and fixing it. As a thank you, I'll reach out to you via email to ask for delivery info so I can send you Memgraph swag 🚀

Awesome! Looking forward to it :)

Hi @dintorf, did you receive my email?

Hi @katarinasupe, I sent you another email last week. Did you happen to receive that one?

Hi @dintorf, I received it! I will respond asap, it's been a busy week 😄


boards: be pedantic about type of networking

Renamed 'net' to 'slip' to be pedantic about the type of networking that
we currently support on the QEMU targets.  Also marked the arm
(qemu_cortex_m3) board as supporting 'slip'.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

Can I do ethernet with qemu?

Yes, the CONFIG_NET_SLIP_TAP is ethernet over slip, so our qemu<->host communication is via ethernet always.

But from the Zephyr code point of view its just slip, it has no idea its ethernet.  I'm saying this because we could in the future have a PCI ethernet card in qemu_x86 and have a real ethernet driver in zephyr for it.  'net' isn't really describing the 'hardware' we are supporting on the 'board'

I'm saying this because we could in the future have a PCI ethernet card in qemu_x86 and have a real ethernet driver in zephyr for it

Should we tackle this issue (if there really is one) when we encounter such a PCI card? As Anas said in earlier comment, currently we want to test the IP stack, and not the slip interface.

Nothing stops us from testing the network stack, but isn't true the only way we test it with qemu is with slip?

Nothing stops us from testing the network stack, but isn't true the only way we test it with qemu is with slip?

yes, just like the only way to test networking on frdm_k64f is with ethernet.
So taking this line of thought to the next level, instead of net you are suggesting to list the actual device, or driver type such as slip, ethernet, wifi, etc.
In a test case we then would have:
depends_on: slip ethernet wifi
instead of
depends_on: net
as it was intended now, is this right?

Yes I mean that.  If want 'net' to mean supports some network interface I'm fine with that, just means we need to add 'net' to all the cases we have 'ethernet' and 'ble' right now.  I'd still have qemu have both 'net' & 'slip'.

I changed sanitycheck to treat the list as and.  There was a case in which we he depends_on: 'usb' 'ieee802_15_4' . We might want to expand the support in sanity check to support explicit 'and' and 'or' and 'not'

we need to use ply for that

the sanitycheck testcase.ini format already had an expression language which supported logical relationships when filtering test cases, why was this removed???

the sanitycheck testcase.ini format already had an expression language which supported logical relationships when filtering test cases, why was this removed???

It was not removed, this is something completely different and new.

thought about it more, having to list every network interface in the testcase is not going to be perfect, i.e. we will start having inconsistencies and we have to always keep the list up2date, I have no problem listing the slip, eth per board, however we need to have some catch-all keyword, maybe not net, but netif for example, for "network interface", this would cover all types of network interfaces, if someone has a test specific to ethernet or slip, they can still use those and be explicit about it.

Closing this as PR #957 deals with the issue.


When app deployment is prevented because of not having matching annotation, error message complains about .signatures.0.anyOf

acorn version v0.6.0-93-gd9de8c30+d9de8c30
Steps to reproduce the problem:
Create ImageAllowRules:
kind: ImageAllowRules
metadata:
  name: testrules-project
  namespace: testp1
signatures:
  rules:
    - signedBy:
        anyOf:
          - |
            -----BEGIN PUBLIC KEY-----
            MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEn3TS2G8lKMA2B6CT9mWZ3H6Z4k/h
            5RvYIFIPNvExwsV40B9xi3v2jBF2ODSINhPxHJOAs+eHZW3AitIwthqOsQ==
            -----END PUBLIC KEY-----
        allOf: []
      annotations:
        match:
          tag: ok

Deploy an app with image that is signed by the right privatekey but does not have the right annotation.
cosign sign --key cosign.key -a tag=notok docker.io/sangeetha/<image>:v6.0.0

acorn run -n mytes2 docker.io/sangeetha/<image>:v6.0.0
  ✗  ERROR:  App.api.acorn.io "mytes2" is invalid: spec.image: Invalid value: "docker.io/sangeetha/<image>:v6.0.0": disallowed by imageAllowRules: image docker.io/sangeetha/myfirstacorn:v6.0.0 is not allowed by rule testp1/testrules-project.signatures.0.anyOf

Error message presented to the user refers to image not being allowed because of signature match, when annotation match  was the one that failed.

Update on my previous comment: Actually, it's hard to improve on that without introducing quite some complexity here.
anyOf rules are only failed if all entries didn't pass the check, either because the key wasn't present or because the key was present but the annotation didn't match.
Now imagine you have 10 possible keys in anyOf, some are failing because the key didn't match and some because the annotations didn't match. That would make for a long error message there. So we decided to just tell the user, that the whole anyOf group failed.
For allOf that's way easier, because we error out on a single failure.

@sangee2004 what do you think with regards to my last comment?


structured streaming dropDuplicates Operator

The dropDuplicates Operator  can only  retain the first one to arrvied?

Yes, but..does it really matter since all records are the same?
Please use https://stackoverflow.com/questions/tagged/spark-structured-streaming for this and other questions. Thanks.