F-Droid

Hi,
Is it possible to add this app to F-Droid. It's a very safe way to get this app, for example for folks who can't access Google Play in their country. They will build your app from source, if there is no proprietary dependencies.
Otherwise, could you please provide a signed "release" apk in the release section?

Thanks for your feedback, @Poussinou. Users who cannot access the Play Store can download the signed Android app here.

The best way to attach binaries is to do it via the release section of the source code repo, I think (see here for more information). It's easier to see if we have the up to date version of the app, and you can keep the older versions available for everyone...
But it's ok, thanks!

We also host them in the releases section, for instance: android-v1.0.1.

We also host them in the releases section, for instance: android-v1.0.1.

But you forgot them there for the stable releases – only pre-releases have APK files attached. As @Poussinou pointed out, that would make updates easier – also for the auto-updater of my F-Droid compatible repo, where I've just added your app on request by @Poussinou :wink:

The arguments for F-Droid makes sense, but wouldn't F-Droid be blocked if the Play store was also blocked?

@fortuna Blocked by what exactly? Do you think about a blocked access?
In fact even if Google Play AND F-Droid were blocked by something, the fact that F-Droid allows to share the app directly between devices is an advantage... Once you have the app and F-Droid installed, you can give the app to everyone very easily. It could be effective in a country where F-Droid and Google Play were blocked: if one person has Jigsaw and F-Droid, everybody can have it...

What @Poussinou describes is practiced in Cuba, due to "flaky Internet". There's an article on that somewhere on the F-Droid site.
Another example for "blocked access" are firewalls and filters. For example, try using Google in China (behind the "big Firewall"). Not sure if F-Droid is blocked there as well, though – but you get the point.

In China, GooglePlay is blocked by Great Firewall (GFW, '墙'), but F-Droid
works now.
We usually share VPN application through QQ, WeChat, SD card, Flashdisk, or
directly download from github (but slow and unstable).
Izzy<EMAIL_ADDRESS>于 2018年6月17日周日 07:11写道：

What @Poussinou https://github.com/Poussinou describes is practiced in
Cuba, due to "flaky Internet". There's an article on that somewhere on the
F-Droid site.
Another example for "blocked access" are firewalls and filters. For
example, try using Google in China (behind the "big Firewall"). Not sure if
F-Droid is blocked there as well, though – but you get the point.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Jigsaw-Code/outline-client/issues/50#issuecomment-397843885,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQVHEkG-SJtjRm_uDanJ5B64gei7s3bCks5t9ZCTgaJpZM4TBeta
.

Here you can find the article @IzzySoft is talking about 👍
So yes having Jigsaw in the official F-Droid repo would be a good idea...

Can we please re-open this issue? This is important for privacy-conscious, at-risk people, so exactly the Outline target audience. Offering them a way to install and seamlessly upgrade their Outline client via F-Droid would be a boon. And since the signed APK is already available, it does not seem like a lot of additional work would be needed...

@rysiekpl you can already, if you add my repo to the client – see here. Though I definitely admit having it in the main repo would be a jump upwards!

@rysiekpl, I think your request is fair. I'm not very familiar with F-Droid. Is there a way for us to include only signed APKs in the main repo, or do we have to import the source?
Releasing the clients for five platforms is already challenging for our small team, so we need to evaluate whether we can absorb the maintenance cost of supporting F-Droid.
@IzzySoft, can the repo you set up be included in the main F-Droid repo? Or would we have to set it up as maintainers?

@alalamav my repo is fed by the APKs you provide here. If you tag a new release and attach an APK to it, that should show up in my repo within 24h. Users cann simply add the repo URL to the F-Droid client installed on their devices, use that to install your app, and they'd be notified about updates automatically.
For details you're welcome to check with my 3-part blog series on F-Droid (soon-to-be 4-part):

F-Droid: The privacy-friendly alternative to Google Play Store
F-Droid for advanced users and developers (includes instructions for 3rd party repos like mine)
Your own F-Droid Repository with Repomaker

There's also an article on my repo (IzzyOnDroid’s F-Droid Repo with additional functionality), a list of Unofficial (and incomplete) list of F-Droid repositories, and more.

Thank you @alalamav and @IzzySoft! This is good news indeed. If there could be some mention of that in the documentation (Outline is available on this-and-that repo on F-Droid), that would be swell.

Version 1.3.0 added a bunch of trackers (e.g. Crashlytics, Firebase Analytics). I hope this was an accident, and not something intended – because your app is supposed to be dealing with sensitive data, and you cannot really control what data goes to 3rd parties when using such proprietary trackers.
Could you please remove them again, @alalamav? Meanwhile I disabled auto-updates for your app in my repo, and removed v1.3.0 manually again – as that combination is a show-stopper here. Apart from that, all the 4 of them are show-stoppers for including the app with the official repo, where proprietary components (including GMS and Firebase) are not accepted at all.

@IzzySoft , we hear your concern. There's a trade-off here.
We are migrating our network stack to Go, so we can share network code across platforms (our team is small, that's a lot of overhead). Unfortunately the migration is taking a while because we are getting a significantly higher number of crash reports, and those reports don't have all the details of the stack when it crosses languages. Furthermore, we were unable to reproduce the errors on our development environment and devices.
After struggling with it for some time, we decided to try Crashlytics, since it can give us the full stack. It's only being used for the crash reports, not analytics.
Notice that the PR hasn't been submitted yet. The code is only for the beta version of the app. The production version won't have any of the Firebase code (it's added at build time). AFAIK the plan is to have a notice alerting the user of the library in the beta version. The user can always switch to the production version.
Does it make sense? Do you have any other ideas on how we can find out what's going on with those crash reports?
@alalamav to sanity check what I said :-)

What @fortuna said is correct; Firebase is only integrated into the client when we explicitly build for beta.
@IzzySoft, I would only add that we are happy to mark beta releases as non-production ready, so they are not consumed by your F-Droid repo.

@fortuna thanks a lot! I'm not a dev and thus don't have the "deep insights" – but if you just need crash reporting, maybe taking a look at ACRA, which is fully FOSS, might give you an acceptable option for that? ACRA is even "white-listed" in the official F-Droid repo, so it should be fine. There are 2 or 3 others – but not being a dev I didn't keep track. Let me look what my library scanner has in terms of "crash reporting without the Tracking AntiFeature:

CrashReporter: "a handy tool to capture app crashes and save them in a file. This library captures all unhandled crashes and saves them locally on device, not on some remote server." (uses Apache 2.0 license)
BugClipper: "lets users report issues directly from your app, with screenshots, screen recordings and crash videos" (not sure if this is FOSS; if not, it would again be a show-stopper for the official repo)

@alalamav thanks to you as well – and yes, I'd welcome that option. You could make the beta-build releases "pre-releases" (which you already do) – and I let my updater know to skip those, which is easy and the default anyway and was even set for Outline. If you later decide to bring your app into the official repo, you could even have that one skip beta-builds (which there can be controlled via tag name patterns, which you already use: e.g. replacing the android- prefix by an fdroid- prefix for those F-Droid should pick up, so we'd set AutoUpdateMode to Version fdroid-%v and it would ignore all others).
Just wondering, as I couldn't find any non pre-release "android*" tag: have you already "turned that switch"? As my configuration says to skip pre-releases for Outline. So shall I then try switching auto-update on again? That should then walk back to the latest non-pre release, for now find no APK there, and then wait for the next.

Crash reports are very important to create a stable products.
Another solution could be store the crash logs in app and request the user to send it when app is opened again using email or some other means this way user also will know what he is sending and no 3rd party dependencies.
Refer this https://github.com/RohitSurwase/UCE-Handler
Again I'm not recommending this particular library, we can implement something similar on our own

Thanks for the pointers. One challenge is the fact that we are cross-platform.
What are people's opinion of Instabug? It seems to be quite well developed.

According to my library scanner, it seems to have earned the Tracking AntiFeature as well (i.e. at least with the default config, doesn't ask the users' consent before uploading things). Exodus thinks the same. Moreover, it seems to be "free" as "free beer", but not "libre" (no link to the sources – at least not on a quick glance). So it'd be a show-stopper for F-Droid again.

Any news, @fortuna?

PS: it's also pretty hard to find the stable builds on your releases tab, with all those daily development builds published by the bot. Maybe you could link to the latest build releases (per OS) from somewhere, e.g. from the Readme?

Thanks to the new tag names, picking only stable ones (android-v%v) is now easy. I just re-enabled auto-updates for my repo after verifying the last version (1.2.13), which my scanner confirmed to be "clean".

Closing because we're a small team and don't have the bandwidth to maintain another release. We do have APK releases available here on GitHub for folks who can't or don't want to use the Play Store.

Closing because we're a small team and don't have the bandwidth to maintain another release. We do have APK releases available here on GitHub for folks who can't or don't want to use the Play Store.

So you might want to close my PR as well then I guess. I'm just a 1-man-team and don't have the time to bother with funny CLAs at Google servers. So if you insist on such, please simply close my PR and I'll delete my branch. I won't bother you with PRs again then either (sorry if this sounds a bit angry – but it doesn't feel nice being asked to help and then having the door slammed on my nose after spending time on it I had to take from other work. Nothing personal, I understand what "overload" means – I'm drowning myself. And I appreciate your providing the APK here!).
Last side-note: Fastlane would have eased your release process as well. It can automate a lot of it, including creation of screenshots and, AFAIK, even pushing them to Google.

So you might want to close my PR as well then I guess. I'm just a 1-man-team and don't have the time to bother with funny CLAs at Google servers. So if you insist on such, please simply close my PR and I'll delete my branch. I won't bother you with PRs again then either (sorry if this sounds a bit angry – but it doesn't feel nice being asked to help and then having the door slammed on my nose after spending time on it I had to take from other work. Nothing personal, I understand what "overload" means – I'm drowning myself. And I appreciate your providing the APK here!).
Last side-note: Fastlane would have eased your release process as well. It can automate a lot of it, including creation of screenshots and, AFAIK, even pushing them to Google.

Hi IzzySoft - Apologies that you felt that my comment was directed toward you - it certainly wasn't, and we appreciate your feedback on how we can make the app more compatible with F-Droid. I didn't understand that we might be able to set up the repository for F-Droid without needing to maintain an additional part of the release process (which for us takes quite some time). I'm re-opening it in the hopes that we can get to it in the future with a Fastlane migration.
As regards the CLA, I respect your decision but unfortunately we're not able to accept contributions without one. As I mentioned above, though, your feedback and suggestions here on how we can make the app more compatible with F-Droid is appreciated and will be valuable for the future.

Hi IzzySoft - Apologies that you felt that my comment was directed toward you - it certainly wasn't, and we appreciate your feedback on how we can make the app more compatible with F-Droid. I didn't understand that we might be able to set up the repository for F-Droid without needing to maintain an additional part of the release process (which for us takes quite some time). I'm re-opening it in the hopes that we can get to it in the future with a Fastlane migration.
As regards the CLA, I respect your decision but unfortunately we're not able to accept contributions without one. As I mentioned above, though, your feedback and suggestions here on how we can make the app more compatible with F-Droid is appreciated and will be valuable for the future.

@cjhenck accepted, thanks. My apologies if I sounded a bit harsh; but I'm already drowning in work, so it was a doubly unfortunate situation we got into here.
And now I see were my comment went which I thought lost – oops. Got 3 pings from your repo at the same time, didn't notice this was a different issue…
Well, as pointed out: I cannot offer my help if you insist on that CLA. But you're free to use my Fastlane Cheat Sheet (and manually pick from the descriptions in my PR so they seem to be your commits, I don't care for attribution on such a minor thing but rather for having FLOSS work driving). Hope my suggestions here in issue comments don't need some "CLA blessings" :wink:
As for the listing on F-Droid: We¹ have no CLA there either. We might ask for your help should issues arise with builds, or if some library you include cannot be accepted (happens eg with GMS or other proprietary libs). Usually there are not-to-difficult solutions to that (mostly using build flavors). And usually someone will offer a helping hand in getting things implemented if needed – though again your CLA requirement might make things difficult with that.
¹ disclosure: I'm one of the F-Droid maintainers

@cjhenck accepted, thanks. My apologies if I sounded a bit harsh; but I'm already drowning in work, so it was a doubly unfortunate situation we got into here.
And now I see were my comment went which I thought lost – oops. Got 3 pings from your repo at the same time, didn't notice this was a different issue…
Well, as pointed out: I cannot offer my help if you insist on that CLA. But you're free to use my Fastlane Cheat Sheet (and manually pick from the descriptions in my PR so they seem to be your commits, I don't care for attribution on such a minor thing but rather for having FLOSS work driving). Hope my suggestions here in issue comments don't need some "CLA blessings" :wink:
As for the listing on F-Droid: We¹ have no CLA there either. We might ask for your help should issues arise with builds, or if some library you include cannot be accepted (happens eg with GMS or other proprietary libs). Usually there are not-to-difficult solutions to that (mostly using build flavors). And usually someone will offer a helping hand in getting things implemented if needed – though again your CLA requirement might make things difficult with that.
¹ disclosure: I'm one of the F-Droid maintainers

Hi everyone! Any progress here?

I just made an MR. Looks like there is no nonfree libs involved. No Firebase nor Crashlytics. Since Sentry is used I guess they are replaced. Not sure if those .so files in cordova-plugin-outline/android/libs are needed. It seems they are only used for crash report which doesn't work anyway. Fastlane is missing due to the CLA. If this is OK I'll add descriptions in the recipe and merge it.

Application Outline by Jigsaw available on F-Droid to install:

Issues can be closed as completed.


Keybinding not available

With latest release, there is no GearMenu options in Key Bindings menu.

True. Cannot be seen in the key bindings menu at all. Not visible.

The file "Bindings.xml" is missing from 1.0.3 and 1.0.2. An easy way you can fix the issue yourselves is by downloading the 1.0.1 release and taking the bindings file and put it with your newer version.

Hi guys,
I was just able to reproduce this. Looks like another issue I overlooked when the Addon is packaged for release. Bindings.xml wasn't packed properly. I will fix this in the next release.
Regards,
RagedUnicorn

Hi again,
This is now fixed in the v1.1.0 release. Let me know if you stumble on any other issues
Regards,
Ragedunicorn


If you press start repeatedly, timer gets faster and faster.

It doesn't check if the stopwatch has already started. So we end up with multiple setIntervals running :)

Thanks :+1:


[ENHANCEMENT] Filter News and Updates

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
I'd like the ability to filter the News and Updates by the content creator (e.g. FF Ballers, FTN, Dynasty Nerds, etc...). This would help to narrow down content to the analysts and sites that we follow, instead of clicking through each page of news until we find the news from the specific analyst we're looking for.
Describe alternatives you've considered
Perhaps the ability to categorize the updates by "News", "Podcast", "Player Update", "Article", etc... could be done instead or as part of this feature?
League ID
n/a
Additional context
n/a

Makes a lot of sense. This would be a great first issue for someone to take on. If not, I'll grab it when I can.


Data visualisations were saving title in the wrong order

What
Babbage relies on full-width being the second argument and title being the third in the string. At the moment visulisation are being incorrectly saved on disk corrupting the title and not allowing the full-width usage. The longer this goes unfixed the more data fixes required.
How to review
Below is a rough guide

Go into Florence
Create a new article (or any page type that accepts vis content)
Edit the content section and then click add visualisation
Go to the ONS website and find an article that has a visualisation on it.
append the URL with /data
Search the JSON for the visualisation
copy the URL of it
go back to Florence and under the URL field for the visualisation paste the copied URL
tick the box 'make full-width'
continue to publish the content
Go to the content locally via web
Open up the DOM
Go to the visualisation on the DOM
Check that the class 'pym-interactive--full-width' has been added

Repeat but without the full-width checkbox being selected and check that the class has not been added to the element
Who can review
Anyone except me

The concourse unit tests are failing. Some variables are declared but not used

Was due to an external dependency being updated automatically. Node-sass I have now pinned it down to the latest of a compatible version 4.


Rework delayLoad slightly

Mostly just a rename, but also it wasn't ever being set in d2l-my-courses itself, so removed it from there.
This is a super low priority, QOL kinda thing.

LGTM. Seems to work (tiles still load, but not until the all courses overlay is loaded).

In the spirit of the retro, my test plan:

Launched Brightspace and verified that my pinned tiles loaded.
Clicked View All Courses and verified that those tiles loaded.
Closed View All Courses, opened debug tools, and hard-refreshed
Noted that when displaying the pinned courses only /organizations HM calls were made for the tiles pinned and visible.
Clicked View All Courses and noted that the network traffic showed /organizations HM calls for all of the tiles being loaded on the All Courses screen.


@Profile with SpringBootMongock

Hi,
I configured SpringBootMongock like :
@Bean
    public SpringBootMongock mongock(ApplicationContext springContext, MongoClient mongoClient, MongoProperties mongoProperties) {
        return new SpringBootMongockBuilder(mongoClient, mongoProperties.getDatabase(), "my.package")
                .setApplicationContext(springContext)
                .setLockQuickConfig()
                .build();
    }

And ChangeLog :
@ChangeLog
@Profile({"!test", "!dataset"})
public class DatabaseChangelog {
...
}

When I'm running tests with @ActiveProfiles("test"), Mongock is executed.
Method .setSpringEnvironment(environment) of SpringMongock is not implemented in SpringBootMongock
Did I miss something to handle my profile ?

Hi @LeJeanbono , which version are you using?
We'll have a look, you can expect to have an answer on Monday morning as latest ;)

Sorry, was on holidays :)
I'm using com.github.cloudyrock.mongock:mongock-spring:2.0.2

good, we'll have a look at that and will try to reproduce it and introduce the fix in the 3.0.3.BETA.

Do you need more informations ?

Hello, sorry, we am on vacations now. I will be back at the end of the week. Sorry for the inconvenient.

Hello @LeJeanbono , sorry but we are a bit busy. Do you need this urgently or it can wait?

It's not critical, just a lost of time during testing.
Do you have an idea of the problem ?
I can do a MR

I haven't looked at it yet, but it seems that SpingBootMongock is not taking the profile into account, which it's easy to fix. If you want to give a shoot, I am happy to review it

I took a look, for me, all should work.
Can you have a look please ?

hello @LeJeanbono , you mean a PR? I don't see anything. But I will have a look once your PR is raised ;)

I didn't find the problem, can't do a PR :/

aah sorry, I misunderstood. I will, thanks

I am looking at this. I hope to have some news soon.

Hello again, released 3.0.6.BETA version with the fix.

Please let me know if works for you, so I can close this issue.
Thanks @LeJeanbono

@LeJeanbono , while that fix should work for you. It's definitive. I am  going adapt it to the Spring 5.1 way, with profile string, with !,&,|.
I will keep you updated.

@dieppa Thank you, I just make some tests and it seems to be ok :)

thanks, I close this

Hi @dieppa in   private boolean matchesActiveSpringProfile(AnnotatedElement element) { your fix will return false if we only have the default Profile

Sorry, I am just seeing this.
Yeah, good point. I will look at that this week and I promise I will have a new release at the of it(at most)

Hi @LeJeanbono ,
sorry for the delay. Can you provide an example when it returns false with default profile? I am probably missing something, but don't see it

Hey @dieppa !
When activeProfiles is default (No@Profileset on the class), the method return false because  default is not in profile list : https://github.com/cloudyrock/mongock/blob/b3b0198c0e48df563670c84f709d6a776616c755/mongock-spring/src/main/java/com/github/cloudyrock/mongock/SpringChangeService.java#L72`

Hey! thanks for your quick answer.
Have you tested it? Because I did and it returns true because of this line.
Unless I am missing something

Yep
Keep @Profile({"!test", "!dataset"}) and run Spring without profile : Mongock will not work.

cool, that what I needed 👍

Hello @LeJeanbono ,
3.0.7.BETA has been released with the profile fixed. I close this, but let me know when you are able to test it.
You can see the tests  we've added in SpringChangeServiceTest


fix a few scripts for building (issue #290)

This fix is relevant to #290 . Basically it replaced a lot of return {*} with return std::make_tuple() for building.
These changes made building successful under environment:

torch 1.9.0, cuda 10.2, gcc 5.4.0
k2 1.23.4.dev20230130+cuda10.2.torch1.9.0

Thanks for your contribution !


Improve API

This PR

removes callbacks from method signatures

With all the add and remove it might be better to squash this PR.

Work on collections is done in feature/collections_node


tgi

TUX Global Institute

@Ensophea-Toch lib/domains/kh/edu/tgi: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@Ensophea-Toch I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host tgi.edu.kh not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!

Dear JetBrains Team,
tgi domain is tuxglobalinstitute.edu.kh thanks!
On Thu, 28 Mar 2024 at 18:33 Philip Torchinsky @.***>
wrote:

Closed #20436 https://github.com/JetBrains/swot/pull/20436.
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/20436#event-12280058095, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BG5W65NKN4YPRG7NSAFM7ZLY2PWX5AVCNFSM6AAAAABFGEYG4SVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGI4DAMBVHAYDSNI
.
You are receiving this because you were mentioned.Message ID:
@.***>


MAPREDUCE-7438 : Support removal of only selective node states in untracked removal flow

ASF JIRA: https://issues.apache.org/jira/browse/MAPREDUCE-7438
Allowing config to remove untracked nodes having only selective nodeStates
Config: yarn.resourcemanager.node-removal-untracked.node-selective-states-to-remove
If Yarn untracked removal is enabled, then this config can control what all
node states can be removed. If the untracked node is not having one of these
states, then node will skipped for removal. If this config value is set to
empty, all node states, will be eligible for removal
NodeState is an ENUM: org.apache.hadoop.yarn.api.records.NodeState
How was this patch tested?
Adding 1 new UT in TestResourceTrackerService.java

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 53s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 54s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
19m 48s

trunk passed

+1 :green_heart:
compile
6m 53s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
6m 23s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 50s

trunk passed

+1 :green_heart:
mvnsite
2m 59s

trunk passed

+1 :green_heart:
javadoc
3m  0s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
2m 47s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
5m 59s

trunk passed

+1 :green_heart:
shadedclient
21m 48s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 52s

the patch passed

+1 :green_heart:
compile
6m 19s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
6m 19s

the patch passed

+1 :green_heart:
compile
6m 20s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
6m 20s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 38s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 6 new + 197 unchanged - 0 fixed = 203 total (was 197)

+1 :green_heart:
mvnsite
2m 45s

the patch passed

+1 :green_heart:
javadoc
2m 39s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
2m 31s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
6m  6s

the patch passed

+1 :green_heart:
shadedclient
21m 47s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m 11s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 38s

hadoop-yarn-common in the patch passed.

-1 :x:
unit
102m  3s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
asflicense
0m 57s

The patch does not generate ASF License warnings.

253m 16s

Reason
Tests

Failed junit tests
hadoop.yarn.server.resourcemanager.reservation.TestCapacityOverTimePolicy

hadoop.yarn.server.resourcemanager.TestResourceTrackerService

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5680/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5680

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets xmllint

uname
Linux 1194573d80af 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 18e2372fa56385c9a4911f43f386a487b4e13edb

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5680/1/testReport/

Max. process+thread count
939 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5680/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 51s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
16m  9s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
19m 41s

trunk passed

+1 :green_heart:
compile
6m 54s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
6m 24s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 50s

trunk passed

+1 :green_heart:
mvnsite
3m  3s

trunk passed

+1 :green_heart:
javadoc
3m  1s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
2m 47s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
6m  1s

trunk passed

+1 :green_heart:
shadedclient
21m 29s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 54s

the patch passed

+1 :green_heart:
compile
6m 21s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
6m 21s

the patch passed

+1 :green_heart:
compile
6m 18s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
6m 18s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 39s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 6 new + 197 unchanged - 0 fixed = 203 total (was 197)

+1 :green_heart:
mvnsite
2m 44s

the patch passed

+1 :green_heart:
javadoc
2m 39s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
2m 34s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
6m  9s

the patch passed

+1 :green_heart:
shadedclient
21m 49s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m 10s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 41s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
102m 15s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
asflicense
0m 58s

The patch does not generate ASF License warnings.

253m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5680/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5680

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets xmllint

uname
Linux 31a180c82301 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 19804ca9ef9ff95a0d5a8e49ab9dfc5aab6369bf

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5680/2/testReport/

Max. process+thread count
950 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5680/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Created new PR in Yarn Project: https://github.com/apache/hadoop/pull/5681


Add README file for Helm charts section

Add instructions on deploying the sail-operator by using the helm charts defined within the repository.
Rearrange the following guides to avoid duplication.
Place them within 'docs/common' directory and reference them from the relevant docs guides.

create-and-configure-gateways.md
install-bookinfo-app.md
install-istioctl-tool.md
istio-addons-integrations.md

Fixes https://github.com/istio-ecosystem/sail-operator/issues/314

@MaxBab: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

e2e-kind-olm_sail-operator_main
106a24cc9371457799c88fb1d7da420c550a3bcf
link
true
/test e2e-kind-olm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Adding hold, in case you want to do any other change of someone else want to take a look

@MaxBab: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

e2e-kind-olm_sail-operator_main
cab5b9c074ea12ebccedf8c731ffec919e97aa7f
link
true
/test e2e-kind-olm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/test e2e-kind-olm

LGTM. I'll wait for sometime if someone wants to review this PR before merging.

@MaxBab, you can delete the hold label when you want to merge the PR :)


Error Post.template.php

New Install last pull request #2173 from emanuele45/fix_psql
This version: ElkArte 1.1
Current version: 1.0.4 bug fix update
MySQL version: 5.6.25
PHP: 5.6.11
Core Features not enabled
When create a new topic or reply to a topic, the following error message appears:
Notice: Undefined index: make_event in C:\xampp\htdocs\elk11\themes\default\Post.template.php on line 306

I should have that one fixed in one of my local branches, otherwise is "just" a matter of wrap the variable with an !empty


On 0.4 allow SortedDicts to be constructed like regular Dicts

Cc: @StephenVavasis

@Keno and @kmsquire,
I can merge this into my current PR (#88) for the new datatypes SortedSet and SortedMultiDict, but can you send me some example invocations of the new SortedDict constructors so that the test set can include the new constructors?
Could

Hi Stephen,
Since this is already a pull request, the most standard way to deal with this is to merge it as is, and (if necessary) for you to rebase your PR on it (although this PR is so minimal that it probably isn't necessary).
It would be better not to conflate it with your current PR, which is already long enough.
It could use some tests (or updates to the current tests) though (@Keno?).
As of Julia v0.4, the standard Dict notation in Base is
julia> Dict{String, Int}()
Dict{AbstractString,Int64} with 0 entries

The previous notation is deprecated.  Presumably, this PR allows a similar notation for SortedDicts (I haven't tested it.)

Superceded by #113.


Feature: null values to indicate missing data

Great component, love it 👍
One enhancement I feel would be useful is if the component interpreted null values as "missing" data, and displayed no line segment at all. Currently, it interprets null as 0.
For example data=[1, 1, null, 1, 1] would render as a line segment, an empty gap, and then another line segment, rather than a V-shaped dip to 0.

There's actually a PR open for this feature https://github.com/borisyankov/react-sparklines/pull/46
Seems that this repo has been inactive since around that date though. +1ing this feature request anyway.


Error when evaluating instance against schema

Nuget Package
JsonSchema.Net
Package Version
7.2.3
Operating System
Windows
.Net Target (if relevant, please specify the version in the description)
.Net (5 or after)
A clear and concise description of the bug.
When trying to use if/else statements in the schema I get different erros.
When I use "hasForeignIdentification": { "const": true } in the if else statements I get the following error -> Expected "true"]}.
When I use hasForeignIdentification": { enum: [true] } in the if else statements, then I get different error -> Value should match one of the values specified by the enum.
I've been able to validate properly using other libraries/tools and I dont get these errors.
What did you expect?
I did not expect such errors
Please add test code or steps to reproduce the behavior.
instance --> https://pastebin.com/FeFhJ9R2
schema   --> https://pastebin.com/7LNgPzqy
Is there any other information you'd like to share regarding this bug?
No response
Code of Conduct & Contributor Guidelines

[X] I agree to follow this project's Code of Conduct and Contribution Guidelines.

Thanks for reporting.  I don't think this is a bug, but I can't replicate your case because your schemas have references that are unresolvable.
Please update with a minimal reproduction of what you're seeing, and I'll try to address it.
Also, please have a read through my blog post, which highlights some of the pitfalls around error messaging and "option" keywords.

Sorry, pasted the wrong schema. Here's the updated one without refs -> Schema

I'm not sure what the problem is.  const and enum have different error messages (which you can configure if you like).
When you use const, you get a message saying that the value wasn't the expected value.
When you use enum, you get a message saying that the value wasn't one of the expected values.
It just happens that the enum you used only has a single value.  That's a special case for enum that isn't (and won't be) considered.

Thank you!

I understand why I get those errors but I dont understand the reasoning behind it. I need to exclude those kind of errors. I will give you a simpler example than the initial one.
Schema ->
{   "$schema": "https://json-schema.org/draft/2020-12/schema",   "type": "object",   "properties": {     "role": { "enum": [ "HOD", "professor" ] },     "HOD_Id": { "type": "integer" },     "professor_Id": { "type": "integer" }   },   "if": {     "properties":       { "role": { "const": "HOD" }     }   },   "then": { "required": [ "HOD_Id" ] },   "else": { "required": [ "professor_Id" ] } }
Instance ->
'{ "role": "professor", "professor_Id":1 }'

The problem (as explained in the blog post) is that there is no general solution to filtering errors to find the "most ideal" or "irrelevant" errors because I, as the library, can't know what your intent is, so I can't determine what's important to you.
My suggestion is to apply some filtering to the errors on your end as you're searching through them.  If you don't want errors from if keywords, then filter them out by checking whether the evaluationPath contains an if segment.  That's why all of that information is given to you.  This is by design.

All clear! Thank you!


Check if macOS aarch64 release truly is aarch64

There's been a bug issue opened in the Gleam repository about wrong CPU type in macOS release. Supposedly specifying default: true in the actions-rs/toolchain is not enough for it to be the picked up when running on the amd64 runner on Github Actions. The release Github Actions workflow in this repository follows the same pattern as the Gleam workflow.
I don't have an Apple M1 device to test this, can someone confirm if it's a problem in the latest matcha release? If so, maybe a patch to the github actions release workflow is needed.
To test it out, please download the macos arm64 release, extract, and provide what the file command returns for it:
file matcha

Looks like there is the same issue here,
➜  Downloads file ./matcha
./matcha: Mach-O 64-bit executable x86_64
➜  Downloads

OK! So I guess means it's working using Rosetta. Thank you! I'll prepare a similar patch here

OK! So I guess means it's working using Rosetta. Thank you! I'll prepare a similar patch here

Yeah, appears to be what has been happening with gleam for me too.


pull request for e2e test at 12/22/2016 20:15:17

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Multiple nodejs_compat packages missing (crypto, path, etc)

When using nodejs_compat in Miniflare 2, only the following modules are available: assert, async_hooks, buffer, events, util
These ones are missing: crypto, diagnostics_channel, path, process, stream (and stream/promises, stream/consumers), string_decoder.
I'm willing to add these, but as this package is almost deprecated, would you be open for a PR? As we're using globals we can't migrate to Miniflare 3 yet.

I'm creating a Knex client in Node that connects to our local database and then passing it to Miniflare:
    globals: {
      _local_createGlobalKnexClient: createKnexClient,
      _local_getPostgresClient: () => postgresNode(dbConnectionString),
    }

However I think this would be fixed once Hyperdrive support (with local databases support) is added to Miniflare 3.


Error 175: The specified store provider cannot be found in the configuration, or is not valid.

After I download the code and try to build the source code. I met this error:
Error	1	Error 175: The specified store provider cannot be found in the configuration, or is not valid.	E:\Develop\Bonobo-Git-Server\Bonobo-Git-Server\Bonobo.Git.Server\Bonobo.Git.Server\Data\DatabaseModel.edmx	7	5	Bonobo.Git.Server
I have installed the Sqlite on this machine, and register the dll to GAC, also reboot the machine.

Aren't you building 64bit version with 32bit version of SQLite?


SCIM1.1  org.wso2.charon.core.exceptions.CharonException when attepmting to assign a user to a newly provisioned role

When attempting to provision a user and a role and attempt to assign the new role to the user the below exception is thrown
org.wso2.charon.core.exceptions.CharonException: Error occurred while updating old group
steps
1.provision a new user calling scim 1.1 api
2.provision a new role calling scim 1.1 api
3.attempt to update the role and assign the user to the role
environment
1.wso2is-5.7.0 with updates<PHONE_NUMBER>728/1543336788716)
2.java version "1.8.0_161"
3.ubuntu 18.04

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


Cant sign into Topeka - iOS 7 / Chrome

Can't seem to click on Sign In. Happens on iOS 7, both Chrome and Safari browsers.

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.


Update userguide regrid section

Updates the userguide chapter "Cube regridding and interpolation". This PR improves only the section on regrid; for the improvements to the interpolation section see #1548. The changes include adding a sub-section on caching a regridder for repeated use and other general changes.

@bjlittle here it is!

@dkillick Yup, just see it land! Great stuff!
I'm on to it ... just need to push a cheeky PR myself :wink:

Right then, I'm spinning up now ...

@dkillick I'm done for now and tuning out.
I'm pretty confident that we can get this PR and #1548 merged tomorrow morning :smile:

@bjlittle thanks! I'll push the changes I've made then we can attack this in the morning and get them both merged :grinning:

@dkillick Great stuff! Once Travis is happy, I'll merge :+1:


Access BBF data, reorganize XENON-specific utilities

This is an update to the interface to access data from XENON repositories.

Everything XENON-specific is now in the xenon subfolder/package. It is still exported to the flamedisx package, so you can keep doing fd.SR1ERSource etc.
Updated the resource caching and correction maps from straxen, and moved each to a separate file.
Added an interface with BBF, see below.

This adds the fd.get_bbf_file function, which fetches data from BBF. Use as, for example, fd.get_bbf_file('ACBackgroundSR0.json'), which fetches https://github.com/XENON1T/bbf/blob/master/bbf/data/ACBackgroundSR0.json and parses it as dictionary.
BBF is a private repository, so loading these files requires authentication. There are three ways this can work:

You can do nothing special and just run flamedisx. If you use a source which needs a bbf file, it will instruct you to create a Github authentication token, with which flamedisx will clone bbf, then check out the file.
Alternatively, call fd.ensure_bbf('........................................') in your notebook, with your token in place of the dots. This will clone bbf immedatiately, so future get_bbf calls succeed without prompting.
Alternatively, clone bbf yourself somewhere, then set fd.XENON.data.BBF_PATH to the path of bbf's root folder. For example, I do fd.XENON.data.BBF_PATH = '/home/aalbers/software/bbf'.

There is definitely room for improvement here. Some considerations:

We're cloning the entire 800 MB bbf repo, since it is not straightforward to get a single file in a private repo with github. If you need one BBF file, you will likely need many, so it is not so bad. Cloning with --depth 1 only saves ~100 MB; most of BBF's size is in a few static data files.
We could have used a username/password in the git clone URL, instead of the OAuth token stuff. However, if git clone encounters any problem, it prints the URL to the screen, including your plaintext password...
We could consider requiring straxen in flamedisx, so the itp_map.py and resource.py files can be removed. However, straxen depends on strax, which has some dependencies that don't reliably distribute working pip binaries (or at least, for some reason straxen's Travis CI spends 10 minutes building C++ code...). Maybe these files could be moved to some common lightweight XENON repo like https://github.com/XENONnT/utilix.

Thanks for the comments Pueh! Hope this will make your life easier implementing the various XENON files.


请问下断点重训具体命令是什么啊

我查看了其他issue，在重训时加了--resume_from_checkpoint  —resume_only_model但仍然报错，主要是梯度重复计算，我的命令是

Traceback (most recent call last):   File "/root/autodl-tmp/swift/swift/cli/sft.py", line 5, in <module>     sft_main()   File "/root/autodl-tmp/swift/swift/llm/train/sft.py", line 272, in sft_main     return SwiftSft(args).main()            ^^^^^^^^^^^^^^^^^^^^^   File "/root/autodl-tmp/swift/swift/llm/base.py", line 45, in main     result = self.run()              ^^^^^^^^^^   File "/root/autodl-tmp/swift/swift/llm/train/sft.py", line 139, in run     return self.train(trainer)            ^^^^^^^^^^^^^^^^^^^   File "/root/autodl-tmp/swift/swift/llm/train/sft.py", line 191, in train     trainer.train(trainer.args.resume_from_checkpoint)   File "/root/autodl-tmp/swift/swift/trainers/mixin.py", line 261, in train     return super().train(*args, **kwargs)            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/root/miniconda3/envs/minicpm-v/lib/python3.11/site-packages/transformers/trainer.py", line 1859, in train     return inner_training_loop(            ^^^^^^^^^^^^^^^^^^^^   File "/root/miniconda3/envs/minicpm-v/lib/python3.11/site-packages/transformers/trainer.py", line 2203, in _inner_training_loop     tr_loss_step = self.training_step(model, inputs)                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/root/miniconda3/envs/minicpm-v/lib/python3.11/site-packages/transformers/trainer.py", line 3147, in training_step     self.accelerator.backward(loss)   File "/root/miniconda3/envs/minicpm-v/lib/python3.11/site-packages/accelerate/accelerator.py", line 2125, in backward     loss.backward(**kwargs)   File "/root/miniconda3/envs/minicpm-v/lib/python3.11/site-packages/torch/_tensor.py", line 492, in backward     torch.autograd.backward(   File "/root/miniconda3/envs/minicpm-v/lib/python3.11/site-packages/torch/autograd/__init__.py", line 251, in backward     Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass   File "/root/miniconda3/envs/minicpm-v/lib/python3.11/site-packages/torch/autograd/function.py", line 288, in apply     return user_fn(self, *args)            ^^^^^^^^^^^^^^^^^^^^   File "/root/miniconda3/envs/minicpm-v/lib/python3.11/site-packages/torch/utils/checkpoint.py", line 288, in backward     torch.autograd.backward(outputs_with_grad, args_with_grad)   File "/root/miniconda3/envs/minicpm-v/lib/python3.11/site-packages/torch/autograd/__init__.py", line 251, in backward     Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass RuntimeError: Expected to mark a variable ready only once. This error is caused by one of the following reasons: 1) Use of a module parameter outside the forwardfunction. Please make sure model parameters are not shared across multiple concurrent forward-backward passes. or try to use _set_static_graph() as a workaround if this module graph does not change during training loop.2) Reused parameters in multiple reentrant backward passes. For example, if you use multiplecheckpoint functions to wrap the same part of your model, it would result in the same set of parameters been used by different reentrant backward passes multiple times, and hence marking a variable ready multiple times. DDP does not support such use cases in default. You can try to use _set_static_graph() as a workaround if your module graph does not change over iterations. Parameter at index 391 with name base_model.model.llm.model.layers.27.mlp.down_proj.lora_B.default.weight has been marked as ready twice. This means that multiple autograd engine  hooks have fired for this particular parameter during this iteration.

看看报错信息

我现在按照之前的命令训练又好了，但昨天报错信息有
Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass RuntimeError: Expected to mark a variable ready only once. This error is caused by one of the following reasons: 1) Use of a module parameter outside the forward function. Please make sure model parameters are not shared across multiple concurrent forward-backward passes. or try to use _set_static_graph() as a workaround if this module graph does not change during training loop.2) Reused parameters in multiple reentrant backward passes. For example, if you use multiple checkpoint functions to wrap the same part of your model, it would result in the same set of parameters been used by different reentrant backward passes multiple times, and hence marking a variable ready multiple times. DDP does not support such use cases in default. You can try to use _set_static_graph() as a workaround if your module graph does not change over iterations. Parameter at index 391 with name base_model.model.llm.model.layers.27.mlp.down_proj.lora_B.default.weight has been marked as ready twice. This means that multiple autograd engine  hooks have fired for this particular parameter during this iteration.
 assert self.params_already_reduced[param_id] == False,  AssertionError: The parameter 551 has already been reduced.                     Gradient computed twice for this partition.                     Multiple gradient reduction is currently not supported

--gradient_checkpointing_kwargs '{"use_reentrant": false}'


[Docs Bug 🐞 report]: broken hyperlinks

Describe the bug you found in AsyncAPI Docs.
I would like to contribute to Async API docs, by fixing the broken hyperlinks
Attach any resources that can help us understand the issue.
Following hyperlinks are broken:

https://www.asyncapi.com/docs/tools/generator/asyncapi-document - Template Context
https://www.asyncapi.com/docs/tools/generator/parser- Template Context
https://www.asyncapi.com/docs/tools/generator/template-development - Render Engine

Code of Conduct

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

Hi @kakabisht the links are breaking because either the links are outdated or have a .md extension. For example:

In the AsyncAPI Document has these broken links:
Template Context should be https://www.asyncapi.com/docs/tools/generator/template-context
In the Parser the link to the AsyncAPI Document is breaking. Remove the .md at the end of the link for to to be -> https://www.asyncapi.com/docs/tools/generator/asyncapi-document

@kakabisht Yes, go ahead

@Florence-Njeri I created the following PR. refer to https://github.com/asyncapi/generator/pull/944

related pr merged


Printing all evdev devices crashes with SIGILL

To reproduce:
extern crate evdev;

fn main() {
    for dev in evdev::enumerate() {
        println!("{}", dev);
    }
}

Perhaps it's specific to my hardware configuration.
It prints one of the results, then crashes. Here is a GDB session:
Program received signal SIGILL, Illegal instruction.
0x00005555555693c0 in <evdev::Key as core::fmt::Debug>::fmt (self=0x7fffffffd13c, f=0x7fffffffc578)
    at /home/score/.cargo/registry/src/github.com-1ecc6299db9ec823/evdev-0.10.1/src/scancodes.rs:5
5    #[derive(Copy, Clone, Debug)]
(gdb) x/10i $rip-0x11
   0x5555555693af <<evdev::Key as core::fmt::Debug>::fmt+19823>:    loopne 0x5555555693e1 <<evdev::Key as core::fmt::Debug>::fmt+19873>
   0x5555555693b1 <<evdev::Key as core::fmt::Debug>::fmt+19825>:    add    BYTE PTR [rax],al
   0x5555555693b3 <<evdev::Key as core::fmt::Debug>::fmt+19827>:    mov    rdx,rax
   0x5555555693b6 <<evdev::Key as core::fmt::Debug>::fmt+19830>:    call   0x5555555cd650 <core::fmt::Formatter::debug_tuple>
   0x5555555693bb <<evdev::Key as core::fmt::Debug>::fmt+19835>:    jmp    0x55555556c463 <<evdev::Key as core::fmt::Debug>::fmt+32291>
=> 0x5555555693c0 <<evdev::Key as core::fmt::Debug>::fmt+19840>:    ud2
   0x5555555693c2 <<evdev::Key as core::fmt::Debug>::fmt+19842>:    mov    al,BYTE PTR [rsp+0x2f]
   0x5555555693c6 <<evdev::Key as core::fmt::Debug>::fmt+19846>:    and    al,0x1
   0x5555555693c8 <<evdev::Key as core::fmt::Debug>::fmt+19848>:    movzx  eax,al
   0x5555555693cb <<evdev::Key as core::fmt::Debug>::fmt+19851>:    add    rsp,0x30f8

And here is a screenshot of where the issue is reported in gdb:

I don't know enough rust to say for sure, but since it's showing the error at the top of the class (in source) and within <evdev::Key as core::fmt::Debug>::fmt (in asm), my guess is that something that isn't part of the enum was (unsafely?) coerced into an enum value, and now it's crashing when trying to look up the name.

This is the same undefined behavior issue that was identified in https://github.com/cmr/evdev/issues/7.


Added document name format

Added ability to set document name format to allow usage like this
options.DocNameFormat("Version {0}");

options.SwaggerDoc("Version 1", new Info
{
    Title = "Ha Ha Taxi API version 1",
    Version = "1",
});

Which is absolutely logical where name is set to value meaning name and version is set to value meaning version.

Sorry might be missing something but I really don't understand what this is solving. Can you

What is the purpose of document name? If version is a unique identifier.

documentName is the unique identifier. In many cases, you may want to use the version as you're document name but there's other cases where you wouldn't. For example, you may want different docs for your "Order Processing API" vs your "Product Catalog API". The tenancy scenario that @erendrake described is another good example.

I'm closing this PR as I still don't understand what problem it's actually trying to solve

Agree


Cross most of server (but Server) for JS on 0.23

Yes, yes, I know, all the crossing was supposed to be over 🙃
I thought we didn't really need this on JS and also it would be painful due to the JVMisms at the heart of Server. Well, we don't need Server, but many of those middlewares are useful for serverless. Also client depends on server for testing some stuff. Also missing this JS cross makes it annoying to cross e.g. natchez-http4s which depends on both server and client in the same artifact.
So this is a quickie cross of mostly the middlewares. Server itself and static file stuff are left JVM-only for now, and no actual server implementation is crossed.

I've been slowly shaving the Gzip yak. Delegating to fs2 was a big improvement. In fs2 we have compression on JS, we have CRCs on JS, the only thing left is to port the methods that encode/decode the headers/trailers. It's very doable, all the necessary pieces are there. Just a yak.
CSRF is actually crossed in main. In 0.23 it's entangled with javax.crypto.SecretKey. We could cross it with the shim strategy/hack I used in core, but I didn't think it was worth it.


Introduced action input parser

Potentially avoids many parser misses
Description
Issue: output parser can easily miss when parsing action input JSON strings to Python dicts. This aims to greatly reduce that, and is only used after json parsing misses.
No additional dependencies.
Regex used can probably be improved too, but it works better than what's there.
Type of Change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

[x] I stared at the code and made sure it makes sense (also ran it locally)

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes

@Davixk Thanks for the contribution. Can you explain the regex a bit?
Also, you'll need to run make lint to fix the CI issues


paginate() not working on relationships

When querying using a mapped class or instance, the query_class is flaskext.sqlalchemy.BaseQuery and i get the expected exception with the following:
user.query.paginate()
TypeError: paginate() takes at least 2 arguments (1 given)

But when using a relationship configured on a class or instance query_class is None and paginate() not available.
user.roles.paginate()
AttributeError: 'AppenderQuery' object has no attribute 'paginate'

Do you have the exact test case to reproduce the problem? Because we're already attempting to inject the query class into such relationships when you're using db.relationship.

The exact test case would be not to use db.relationship, but the from sqlalchemy.orm import relationship... which of course does not have the injected query_class. I started out without the extension and had older code still use the directly imported relationship. Fixed and removed the import now; case closed!


Add Testing for Similarity Scores

Should have a testing framework to prove some level of consistency for the calculation of the similarities between messages to attribute as an "echo".

Fixed with 4df5b1d


Rating loses focus when other component is updated

On the demo page, when you are keyboard navigating through the ratings, if you change the value on a Rating that has another UI element bound to its value, the Rating will lose focus.  This should not happen.  Not sure if it is the Rating component itself or the FocusZone inside that is the problem.

Seeing as how FocusZone is causing competing focus issues on the Calendar demo page and even FocusZone demo page, this is probably a FocusZone problem

https://github.com/limefrogyank/BlazorFabric/issues/59#issuecomment-560012102


Evaluate native vite press snippets usage

Per @Hawxy finding: https://vitepress.vuejs.org/guide/markdown#import-code-snippets

Quick note that I added the VitePress snippets feature as in VuePress. Our initial version of docs used it but @jeremydmiller was not happy with using the file path since when we reshuffle code, the file paths can get broken.
So I eventually implemented mdsnippets which is the current mechanism.

The Vitepress usage is not viable IMO. It's higher friction and lower capability than what we get w/ mdsnippets, even with having to manually call mdsnippets once in a while. I'm going dictatorial and shutting this one down folks.

I think it's viable, as I managed to make Vuepress native snippeting work well for ESDB docs reusing regions, so I think that the same can be done here. The fewer moving pieces the better IMHO. Still, this is not the hill I'll die on :wink:


Bug when using triple starting braces.

For the below invalid syntax with triple brackets:
"Hey {{{data.variables.aa | default('there') }}"
data = { variables: {} }
I get output as [object][object] instead of getting syntax error. Why twig didn't throw it as an invalid syntax?
FYI: for input with starting & closing 3 braces : "Hey {{{data.variables.aa | default('there') }}}" I get output: "Hey [object][object]}"
Since I mistakenly added 3 braces, I expect to get an error instead of [object][object]
I used template.tokens to catch any twig syntax errors, but that didn't catch above error:
try {
    const template: any = Twig.twig({ data: startingString });
    if (template) {
        return template.tokens;
    }
} catch (err) {
    this.logger.error('Invalid twig syntax', startingString, err);
}

Any thoughts?

It's most likely interpreting it as a map, which is an object in JavaScript. What happens if you use that same template in Twig PHP?

@willrowe, I just tested and TwigPHP throws a syntax error:
Unexpected "}" in "index.twig" at line 1.

Using twing, which is more accurate than TwingPHP, we get a the same error, alongside the column where the parsing failed:
Unexpected "}" in "index.twig" at line 1, column 46.

This is interesting because at column 46, there is the last closing "}". We would need to investigate the TwigPHP / Twing parsers to understand why this column is the one where the error is detected.

Any update on this?

@sanketdhoble if you would like to look into this an draft up a PR then we will take a look. This project is completely open source and core developers only work on it when they have extra time to do so.


ruby gem for dalle 2 API

Hello, I love your gem, I used it to install some crazy cool text based features in our web app.
OpenAI has a dalle 2 API coming out at some point soon. Do you plan to make a ruby gem that could interface with that? I would love to see another great gem from your guys using that new resource.

Hi @3rwolff
Thanks a lot for the kind words! What's your app? Can I add a link to it to the README?
Yes, I will definitely look at building out a gem for that, either separately or as part of this one. If it comes out and I miss it please drop me a comment here to remind me :)

The API is now live https://openai.com/blog/dall-e-api-now-available-in-public-beta/ :).

Hello @alexrudall I work as a software engineer on a Rails web app called Live Oak Computer Science (https://liveoakcs.com/). Our app aims to provide curriculum to teachers who may not be trained in CS but due to recent legislations have to begin teaching middle and high school students CS.

Thanks @3rwolff really appreciate that! The latest version of ruby-openai adds Images#generate 🤖 ❤ 🦦

Awesome work @alexrudall, thank you very much for implementing that change!


Inline blocks child props

Original PR by @sakulstra PR
this allows passing trough dynamic props

I've just gave tina-cms a spin after reading the next.js blogpost about it.
When experimenting a bit with the incredible cool inline features I faced some problems.
I wanted to make a collapsible list which roughly works like that:
function InteractiveBlocks() {
  // ensure a single collapsible is open at a time
  const [expanded, setExpanded] = React.useState<number | false>(false);

  const handleChange = (panel: number) => (
    event: React.ChangeEvent<{}>,
    newExpanded: boolean
  ) => {
    setExpanded(newExpanded ? panel : false);
  };
  return (
   <InlineBlocks name="faqs" blocks={FAQ_BLOCKS} blockProps={{onChange: handleChange, expanded}} />
  )
}

const faq_item_template = {
  type: "faq_item",
  label: "Selling Point",
  defaultItem: {
    title: "How much is the fish",
    body: "8000 mark",
  },
};

const FAQ_BLOCKS = {
  faq_item: {
    Component: FaqItem,
    template: faq_item_template,
  },
};

Todo:

[x] Updated docs PR approved

what happened here :D where did your comment go @ncphillips? Just wanted to read again what you suggested :sweat_smile:

Haha hey @sakulstra since the CI doesn't run on forks we merge PRs from forks into a new branch before merging into master.
I should have linked to the original PR

Updated docs

In testing this, I don't think the props are actually getting to the block component. We need to spread them within InlineBlock. Something like:
return (
  <InlineBlock
-  {...itemProps}
+  itemProps={itemProps}
    key={index}
    index={index}
    name={blockName}
    data={data}
    block={Block}
  />
)

export interface InlineBlockProps {
  index: number
  name: string
  data: any
  block: Block
  itemProps?: {
    [key: string]: any
  }
}

export function InlineBlock({
  name,
  data,
  block,
  index,
  itemProps,
}: InlineBlockProps) {

  return (
    <InlineFieldContext.Provider value={{ name, ...block }}>
      <block.Component data={data} index={index} {...itemProps} />
    </InlineFieldContext.Provider>
  )
}


Use Composite Keys for User level tables

Remove Id field from UserResourcePool, UserElementFieldIndex, UserElementCell tables and use composite keys instead.
Composite key sample;
[Key]
[Column(Order = 1)]
public int LocationID { get; set; }
[Key]
[Column(Order = 2)]
public int DayID { get; set; }

OData V1-3 doesn't handle composite keys out of the box (or at least it looks like that).
OData V4 could be a solution, wait for #31

This was solved without upgrading to OData V4, by using a code from the following project;
http://aspnet.codeplex.com/SourceControl/changeset/view/9cb7243bd9fe3b2df484bf2409af943f39533588#Samples/WebApi/ODataCompositeKeySample/ReadMe.txt
It has a custom routing convention class, which worked fine. The good part is that userId doesn't have to be send to the server. It's only asking for the other key and completes the action.


Download page not responding

For days now, the download page for the Microsoft Sharepoint Migration tool has been unresponsive. I have a time-sensitive need to access this tool. Please investigate.
Ed

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

ID: 36d01d11-eea9-7f49-693d-25c3fecc6253
Version Independent ID: 6749a619-2b75-1561-81e9-b45888c58c4b
Content: How to use the SharePoint Migration Tool - Migrate to SharePoint and OneDrive
Content Source: migration/how-to-use-the-sharepoint-migration-tool.md
Service: sharepoint-online
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

@Anyman99 Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hello @Anyman99
I see that the download page is working now. Besides that, here we can handle documentation issues only, for the next time that this happens, I recommend opening a ticket directly on your tenant, where they will be able to provide support in your scenario.
Thank you

@Anyman99 thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


FIx (xml-) config classes for thread-safe issues

Replacing foreach with for, for thread-safe usage
For forces uses to use lists.
(also for is most of the time more performant)
fixes https://github.com/NLog/NLog/issues/1153

Current coverage is 73.35%

Merging #1157 into master will decrease coverage by -0.01% as of 99833fc

@@            master   #1157   diff @@
======================================
  Files          265     265
  Stmts        14945   14982    +37
  Branches      1638    1638
  Methods          0       0
======================================
+ Hit          10964   10990    +26
- Partial        417     418     +1
- Missed        3564    3574    +10

Review entire Coverage Diff as of 99833fc

Uncovered Suggestions

+0.09% via ...gingConfiguration.cs#282...293
+0.09% via ...gingConfiguration.cs#244...255
+0.09% via ...c/NLog/LogFactory.cs#181...192
See 7 more...

Powered by Codecov. Updated on successful CI builds.

Wouldn't it be better if you expose a lock variable and use the same during modification of the list?

Good question.  Well locks are more expensive then creating objects. (CPU, lock is some kind of thread sleep)  And when the collection is changed while processing, it's isn't wrong to continue progressing the old collection.
Or do you see it otherwise?

@304NotModified I don't have any other thoughts.

Thanks for the review @Page-Not-Found .
I applied most of your suggestions, see code comment . Please double check. If you think it's OK, just merge it :)

Sure. I just now added some more comments. Can you also check to see there
is no merge conflicts?
On Jan 15, 2016 14:01, "Julian Verdurmen"<EMAIL_ADDRESS>wrote:

Thanks for the review @Page-Not-Found https://github.com/Page-Not-Found
.
I applied most of your suggestions, see code comment . Please double
check. If you think it's OK, just merge it :)
—
Reply to this email directly or view it on GitHub
https://github.com/NLog/NLog/pull/1157#issuecomment-172054095.

I don't see the Merge pull request button. it is disabled.

(Travis has some issues, e.g. timeouts when restoring packages, in multiple branches seen)

@Page-Not-Found if you check this again, please do.
I reverted (and squashed) some previous commutes. I use now every time a variable with .ToList()  (which makes a new list always, see reference source)

@Page-Not-Found, you're now a gladiator? ;)

I am good with all of the code now. But I still prefer to use the for construct just because it does not create a enumerator in run time.
One small suggestion, when you have just one line with in a if or for block. Don't need {}

One small suggestion, when you have just one line with in a if or for block. Don't need {}

That's a matter of style ;). I personally prefer omitting {} when not needed (to keep the code more concise), but others like to include them always. I guess it makes single-line code blocks more visually explicit and consistent with other blocks.

if ((err = SSLHashSHA1.update(&hashCtx, &serverRandom)) != 0)
    goto fail;
if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0)
    goto fail;
    goto fail;
if ((err = SSLHashSHA1.final(&hashCtx, &hashOut)) != 0)
    goto fail;

err = sslRawVerify(...);

The enormous SSL fail of Apple (2014)

I agree will you both. We are good to merge.

Thanks for checking @Page-Not-Found!


[3.x] Fix 2D/3D character snap on moving platforms

Fixes the first point from https://github.com/godotengine/godot/issues/50732#issuecomment-896292908 (regression from #51458) on the 3.x branch.
CC @TokageItLab
CC @fabriceci
Applying the platform velocity when leaving the platform floor should be done after snapping to keep things consistent.
Now it's done in both 2D and 3D, as it's already done in 2D on master.
Note: On the 3.x branch, 2D had the same problem as in 3D (the decision to leave the platform was done before snapping occured), but I couldn't reproduce the same slowdown that occurs in 3D. However, I've made the same change to make it safe and consistent with 3D. It doesn't seem to cause any other issue around 2D moving platforms.

Thanks!


dotnet tutorial problem

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/install
Operating System: windows 7
Error message: "The program can't start becauseapi-ms-win-crt-runtime-|1-1-1.dll is missing from your computer.  Try reinstalling the program to fix this problem"

@dagood @leecow is it a known issue?

This is interesting. For api-ms-win-crt-runtime-l1-1-0.dll, this issue is known to be missing prereqs: https://github.com/dotnet/core-setup/issues/4388. I can't find any record of api-ms-win-crt-runtime-|1-1-1.dll.
@Kirbybu1 can you please:

Check if you made a typo, if you typed this up manually? The | rather than l makes me think that's possible.
Make sure you have the updates listed in the note at https://docs.microsoft.com/en-us/dotnet/core/windows-prerequisites?tabs=netcore2x#net-core-dependencies ?

Checking the updates now.

Thanks! That is the 1-1-0 version with the known fix. I'm going to go ahead and close this issue because the cause is well-known, but please do let me know if following those instructions doesn't work.
To pass along a tip, pressing Control-C while a dialog box is focused should copy all the text inside it. Then you can paste it somewhere, rather than typing it up manually. It's really too bad Windows doesn't have a more obvious way to do this. 😄


Does not play nicely with Next.js App Directory

This library started giving the following error when used in the app directory
DynamicServerError: Dynamic server usage: no-store fetch https://cdn.syndication.twimg.com/tweet-result?id=1631369196163440648&lang=en&features=tfw_timeline_list%3A%3Btfw_follower_count_sunset%3Atrue%3Btfw_tweet_edit_backend%3Aon%3Btfw_refsrc_session%3Aon%3Btfw_show_business_verified_badge%3Aon%3Btfw_duplicate_scribes_to_settings%3Aon%3Btfw_show_blue_verified_badge%3Aon%3Btfw_legacy_timeline_sunset%3Atrue%3Btfw_show_gov_verified_badge%3Aon%3Btfw_show_business_affiliate_badge%3Aon%3Btfw_tweet_edit_frontend%3Aon /[slug]
    at /Users/jamessingleton/Code/Projects/redshirt-sports/node_modules/next/dist/server/lib/patch-fetch.js:261:37
    at /Users/jamessingleton/Code/Projects/redshirt-sports/node_modules/next/dist/server/lib/trace/tracer.js:108:36
    at NoopContextManager.with (/Users/jamessingleton/Code/Projects/redshirt-sports/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:7057)
    at ContextAPI.with (/Users/jamessingleton/Code/Projects/redshirt-sports/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:516)
    at NoopTracer.startActiveSpan (/Users/jamessingleton/Code/Projects/redshirt-sports/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:18086)
    at ProxyTracer.startActiveSpan (/Users/jamessingleton/Code/Projects/redshirt-sports/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:18847)
    at /Users/jamessingleton/Code/Projects/redshirt-sports/node_modules/next/dist/server/lib/trace/tracer.js:97:107
    at NoopContextManager.with (/Users/jamessingleton/Code/Projects/redshirt-sports/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:7057)
    at ContextAPI.with (/Users/jamessingleton/Code/Projects/redshirt-sports/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:516)
    at NextTracerImpl.trace (/Users/jamessingleton/Code/Projects/redshirt-sports/node_modules/next/dist/server/lib/trace/tracer.js:97:32)
    at globalThis.fetch (/Users/jamessingleton/Code/Projects/redshirt-sports/node_modules/next/dist/server/lib/patch-fetch.js:31:47)
    at getTweet (webpack-internal:///(sc_server)/./node_modules/react-tweet/dist/api/get-tweet.js:38:23)
    at TweetContent (webpack-internal:///(sc_server)/./node_modules/react-tweet/dist/tweet.js:19:85)
    at attemptResolveElement (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js:1091:30)
    at resolveModelToJSON (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js:1366:41)
    at Object.toJSON (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js:948:28)
    at stringify (<anonymous>)
    at processModelChunk (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js:156:24)
    at retryTask (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js:1605:38)
    at performWork (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js:1643:21)
    at Timeout.eval [as _onTimeout] (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js:1188:28)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  digest: 'DYNAMIC_SERVER_USAGE'
}

This is how I am using it in my application
import Image from 'next/image'
import {
  PortableText,
  PortableTextComponents,
} from '@portabletext/react'
import { PortableTextBlock } from 'sanity'
import { Tweet } from 'react-tweet'

const TweetComponents: TweetComponents = {
  AvatarImg: (props) => <Image {...props} alt={props.alt} />,
  MediaImg: (props) => <Image {...props} alt={props.alt} fill unoptimized />,
}

export function CustomPortableText({
  value,
}: {
  value: PortableTextBlock[]
}) {
  const components: PortableTextComponents = {
    types: {
      twitter: ({ value }) => {
        return (
          <div className="not-prose flex items-center justify-center">
            <Tweet id={value.id} components={TweetComponents} />
          </div>
        )
      },
    },
  }

  return <PortableText components={components} value={value} />
}

What version of react-tweet do you have installed? I think this issue was fixed in this PR for this similar issue. Has not been released yet though...
Maybe @lfades or @leerob have some insight on when a new release will be published that has this fix in it? I've seen others are still waiting on the current v2.0.1 to get published to NPM as well.

Ah I have the latest that's on NPM. I'm waiting for another fix to be released as well. Hopefully they can get it release and I'll check it out. I just randomly started having this issue so I wasn't 100% certain what was causing it.

Should be up now: https://www.npmjs.com/package/react-tweet. I'm sorry for the delay! and yes the release action is broken (the action itself is not failing but the token it's using is invalid). The ownership of the package is being moved to the vercel npm org and we'll have a new token for it!


[numpy] Numpy-compatible Mean

Description
As title.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Numpy-compatible mean
[x] Unit tests

Comments
@reminisce @junrushao1994

@reminisce Should be ready for merge


questions on reproducing AdapterFusion paper's results

Hi there,
I need to reproduce the adapter fusion paper's results in table 1, I have a couple of questions:

I was wondering if you could share with me possible scripts to have this table reproduced.
In the paper this is mentioned that you report on the dev set, then do you also tune the parameters on the dev set? could you specify how you tune the parameters?
could you assist me in getting the "Argument" and "CB" datasets, the way you processed it, did you download these two datasets from huggingface datasets? If yes, I could not find the names, could you share their corresponding names in datasets library.
winogrande has multiple datasets of various size, could you specify which dataset of winograde is reported in the paper?

Thank you.

the scripts are no longer compatible with the current version of the adapter hub. We are planning to provide some evaluation scripts soon.
we only select the best epoch on the dev set, all other hyperparameters are fixed for all models.
CB is available in superglue. Argument needs to be processed as described in the original paper, unfortunately we are not allowed to distribute it.
largest version


fix: Hex serde deserialize

What this PR does / why we need it?
This PR fixes:
running 1 test
test types::primitive::tests::test_hex_serde_deserialize ... FAILED

failures:

failures:
    types::primitive::tests::test_hex_serde_deserialize

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 41 filtered out; finished in 0.00s

--- STDERR:              axon-protocol types::primitive::tests::test_hex_serde_deserialize ---
thread 'types::primitive::tests::test_hex_serde_deserialize' panicked at 'called `Result::unwrap()` on an `Err` value: Error { inner: Error { inner: TomlError { message: "invalid type: string \"0x1234\", expected a borrowed byte array", original: Some("\n            key = \"0x1234\"\n        "), keys: ["key"], span: Some(19..27) } } }', protocol/src/types/primitive.rs:546:58
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

What is the impact of this PR?
No Breaking Change
PR relation:

Ref #

Special notes for your reviewer:
Before this PR, the serde_json already works well:
https://github.com/axonweb3/axon/blob/c944e248706de540cd8da31cb70f8dce3d8af9a7/protocol/src/types/primitive.rs#L564-L569
https://github.com/axonweb3/axon/blob/c944e248706de540cd8da31cb70f8dce3d8af9a7/protocol/src/types/primitive.rs#L298-L302
https://github.com/axonweb3/axon/blob/c944e248706de540cd8da31cb70f8dce3d8af9a7/protocol/src/types/primitive.rs#L373-L375

CI Settings

CI Usage
Tip: Check the CI you want to run below, and then comment /run-ci.
CI Switch

[x] E2E Tests
[x] Web3 Compatible Tests
[x] OCT 1-5 And 12-15
[x] OCT 6-10
[x] OCT 11
[x] OCT 16-19
[x] v3 Core Tests

CI Description

CI Name
Description

Chaos CI
Test the liveness and robustness of Axon under terrible network condition

Cargo Clippy
Run cargo clippy --all --all-targets --all-features

Coverage Test
Get the unit test coverage report

E2E Test
Run end-to-end test to check interfaces

Code Format
Run cargo +nightly fmt --all -- --check and cargo sort -gwc

Web3 Compatible Test
Test the Web3 compatibility of Axon

v3 Core Test
Run the compatibility tests provided by Uniswap V3

OCT 1-5 | 6-10 | 11 | 12-15 | 16-19
Run the compatibility tests provided by OpenZeppelin

Is this a bug in faster-hex? (It should first de-serialize to String or maybe Cow<str>, not &[u8].)

I guess it's because serde_json supports deserializing borrowed str/[u8], but toml doesn't.
It may fail with serde_json too if there are escapes in the json string.


Fix delegate

The delegate role had a bug in the template. Corrected said bug.
Also updated the delegate docs to show how to pass connection information to ansible.
Added new blurb about how to use localhost as a connection.

LGTM :+1: :+1: :+1:

@rahul0705 Thank you for this PR and docs update.
Does the current code function at all. I wonder if this is something we need tests adding for?

Curious which release this will be added in? or do I need to add additional tests?

Think you're good to go. AFAIK, check https://github.com/ansible/molecule/pull/1594 for a temporary stop gap for releases right now. Not sure when next full point release will be out.


Implement Panes Component

https://ix.siemens.io/docs/controls/panes

Please don't forget to add this component into README file too. @ofaruk84


FT tests: use new ceremony and sign options & bootstrap with new ceremony

Update ft tests with two changes:

use new sign and ceremony options
bootstrap using new admin ceremony

Signed-off-by: Martin Vrachev<EMAIL_ADDRESS>

Note: the last part about Bootstrap should be updated after https://github.com/repository-service-tuf/repository-service-tuf-cli/pull/620 is merged to document that rstuf admin send bootstrap should be used instead of admin-legacy.


Fails to parse map keys as strings

Thank you for this treesitter library!
I'm having trouble with this groovy syntax:
def str_key = ["hello": false]

It seems to parse into this AST:
(declaration
        name: (identifier)
        value: (list
          (string
            (string_content))
          (ERROR)))

I'm having a poke around, but not too familiar this project yet...

thanks for reporting! if you have any luck fixing this, I'm happy to merge any PRs. probably won't have time to look myself for the next few days


Enrich members info returned by /api/v1/cluster/members

Currently, the endpoint returns the list of members, each member with its a few info:

[
  {
    "id": "node-muddy-Sp3u/1652963532",
    "listen_address": "<IP_ADDRESS>:7280",
    "is_self": true,
    "generation":<PHONE_NUMBER>
  }
]

It would be nice to have the service and other relevant info. We could even return the node state?

I say let's dump the whole chitchat node state. It's always nice for debugging / explaining how stuff works.

Closed by #1708


Updated read me file

I added in a badge from Code Triage https://www.codetriage.com/ageitgey/face_recognition

Thanks, but I'm not looking to add more external services to the repo right now.


Reduce log level for repetitive status message, improve log configuration with package naming

This should fix #311

reduce the log level for the offending message from INFO to DEBUG (so that it will not appear anymore in most default setup)
use package name in logger name to allow for easier logging configuration
update Spring Boot sample code with documentation on how to configure logging (as well as identity file and service bind)

Hi @thiloplanz - thanks for the PRs! It's easy to miss them sometimes. @ekoby should get around to checking this one and the other PR out early next week.


Enable xtrace option via DEBUG environment variable

I like the concept, but the implementation you've provided is incomplete and has some problems:

You've only updated the helper script used to build template.sh.
I don't think it's a good idea to enable xtrace on any value of DEBUG (e.g. what if it's 0, no, or false).
If DEBUG isn't set we shouldn't disable xtrace as it may have been intentionally set earlier, and we're thus overriding the user's intent.

I've implemented the general principle behind your PR in https://github.com/ralish/bash-script-template/commit/51e4e833f1af328a3c9aba6c2dfdafecad4ac69f which is now on stable. It will automatically enable xtrace if DEBUG is set to any of 1, yes, or true.
Thanks nonetheless for the idea!


Deep interface errors are not helpful

If an interface has some deep property and an object from that type has a inner property that is not conforming to the type interface, TypeScript compiler will throw an error which is not very helpful because it's not pointing to exact property that is not matching.
Consider following example:
interface Person {
	location: {
		city: {
			name: string
		}
  	}
}

var obj: Person = { location: { city: { name: 1  }}};

Error thrown:
Type '{ location: { city: { name: number; }; }; }' is not assignable to type 'Person'. Types of property 'location' are incompatible. Type '{ city: { name: number; }; }' is not assignable to type '{ city: { name: string; }; }'. Types of property 'city' are incompatible. Type '{ name: number; }' is not assignable to type '{ name: string; }'. Types of property 'name' are incompatible. Type 'number' is not assignable to type 'string'.

The error that is thrown is not telling me that name needs to be a string, it's complaining about obj as a whole.
This is a bigger issue for interfaces that are driven from a JSON Schema like Swagger type interface

The error that is thrown is not telling me that name needs to be a string, it's complaining about obj as a whole.

?. Keep reading to the end of the error:
Types of property 'name' are incompatible. Type 'number' is not assignable to type 'string

Imagine the opposite world, where for an arbitrarily-deep object, we didn't tell you the path to the member that was causing the incompatibility. That would be a nightmare -- you might have ten different properties, each with a different type that had a name member. It'd be impossible to figure out which type had the incompatible one.

I understand that the error has the information about the mismatched property. The error pointer is pointing to obj not name. Doesn't it make sense to point to name?

As strange as this sounds, we don't actually know which property is "to blame" in these kinds of situations.
The compiler works by determining the type of the right-hand side of the expression, then seeing if that type is assignable to the left-hand side. There's no mechanism that keeps track of where that type came from in terms of mapping the properties of that type to the initializations that produced it.
If you imagine a slightly different example:
var x = { location: { city: { name: 1  }}};
var obj: Person = x;

It's somewhat more obvious here that we 1) determine the type of x, 2) determine if that type is assignable to Person.
It's probably possible in theory to implement a better error message in the direct initialization case, but it's not feasible (in terms of performance/memory vs error message quality trade-off) in the indirect case to walk backwards to figure out which property is at fault.


Support Test Explorer 'Traits'

See https://devblogs.microsoft.com/devops/how-to-manage-unit-tests-in-visual-studio-2012-update-1-part-1using-traits-in-the-unit-test-explorer/ for a high level summary of the Test Explorer 'Traits' feature.  It looks like Fixie could benefit from emitting 0..N key/value pairs per test method, with a hook similar to that of test method parameterization.
These should likely be emitted per test method rather than per test case. There's some risk in complicating the test discovery concepts as well: a good "sniff test" for an implementation would be to see how someone could imitate NUnit style "categories" with this traits feature.
Proceed with caution, though: earlier attempts revealed a lot of the existing Test Explorer 'traits' concept is really exposing MSTest-specific and TFS-specific assumptions, and even MS has all but abandoned MSTest itself in favor of xUnit. If this can be done without leaking MSTest-isms and TFS-isms into Fixie, I can see it having some value.

Closing due to age, interest, and the upcoming deprecation of VSTest.
VSTest is being deprecated by the new Microsoft.Testing.Platform which will form the primary focus for v5. https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-intro


fix clippy warnings

@homunkulus r+

:pushpin: Commit d5d491a has been approved by japaric

:hourglass: Testing commit d5d491a with merge d5d491a...

:sunny: Test successful - status-travis
Approved by: japaric
Pushing d5d491aa745ee44af53920c151ac590ebe0e59c7 to master...


[PyPi Publish] Bump version to 0.2.5 in pyproject.toml

@Anush008 let's PR to main in future and avoid PR'ing into release branches 🙈


Include host and service in connection related errors when possible

This change adds the address (host, service) information to error messages from failures to bind a TCP address.
This is done in DataChannelListenNotifier and ControlChannelListenNotifier's not_listening method.
For DataChannelListenNotifier, since host and service are not available in the class, this change relies on the listener's local_address().name() method. But since this method only works in some cases, a fallback method, requested_address is added which returns the original (host:String, service: String) parameters that were used when the connection was opened.
closes #1692

The commit message for this is empty. Commits need to have an explanation of why they were done. There's nothing about this that is obvious enough to explain the change without a decent commit message.

@SeanTAllen updated commit message and PR description

Nice!


Implement dfdl:choiceLength='explicit'

DAFFODIL-640
May have made this more complicated than it needed to be.  For some reason I thought that choiceLength accepts an expression, but it does not.  May need to simplify some things.

All thread safety issues should hopefully be addressed now.

Codecov Report

Merging #218 into master will increase coverage by 0.14%.
The diff coverage is 82.95%.

@@            Coverage Diff             @@
##           master     #218      +/-   ##
==========================================
+ Coverage   79.81%   79.96%   +0.14%
==========================================
  Files         388      389       +1
  Lines       22766    22840      +74
  Branches     2641     2609      -32
==========================================
+ Hits        18170    18263      +93
+ Misses       4596     4577      -19

Impacted Files
Coverage Δ

...rg/apache/daffodil/processors/parsers/Parser.scala
78.57% <ø> (ø)
:arrow_up:

...cala/org/apache/daffodil/io/DataOutputStream.scala
0% <ø> (ø)
:arrow_up:

...ala/org/apache/daffodil/processors/EvElement.scala
94.87% <ø> (ø)
:arrow_up:

...g/apache/daffodil/grammar/ChoiceGrammarMixin.scala
100% <ø> (ø)
:arrow_up:

...g/apache/daffodil/dsom/RuntimePropertyMixins.scala
93.22% <ø> (ø)
:arrow_up:

...rocessors/unparsers/SpecifiedLengthUnparsers.scala
84.09% <ø> (ø)
:arrow_up:

...n/scala/org/apache/daffodil/dsom/ChoiceGroup.scala
75% <ø> (ø)
:arrow_up:

...l/dsom/RawCommonRuntimeValuedPropertiesMixin.scala
79.62% <0%> (-3.07%)
:arrow_down:

...sors/unparsers/SuppressableSeparatorUnparser.scala
95.91% <100%> (-1.19%)
:arrow_down:

...daffodil/grammar/primitives/ChoiceCombinator.scala
85.05% <100%> (+0.91%)
:arrow_up:

... and 42 more

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 53d6b4f...ff91e26. Read the comment docs.

+1 :+1: