Success installed the app on the device but nothing happens since Xcode update from yesterday

Description
When I want to start the app on my physical iPhone, everything seems to work well but nothing happen on the phone. It was working well yesterday. Today I opened Xcode and there were a pop-up saying that Xcode needs to install some stuffs, I clicked Okay and wait for the progress bar to finish. Nothing else has changed, only an update for Safari, no mac update, no iPhone update since.
Here is the output:
npx react-native run-ios --device "Bide’s iPhone"
info Found Xcode workspace "kisschatproudchat.xcworkspace"
`instruments` is now deprecated in favor of 'xcrun xctrace' (see `man xctrace` for more information on its replacement)
info Building (using "xcodebuild -workspace kisschatproudchat.xcworkspace -configuration Debug -scheme kisschatproudchat -destination id=7c4d0fcb017347e75d6affb40397f3a277de6f18")
......................................................................
2020-09-18 18:06:20.756 xcodebuild[22873:499730]  DTDeviceKit: deviceType from 7c4d0fcb017347e75d6affb40397f3a277de6f18 was NULL
2020-09-18 18:06:20.868 xcodebuild[22873:499730]  DTDeviceKit: deviceType from 7c4d0fcb017347e75d6affb40397f3a277de6f18 was NULL
2020-09-18 18:06:20.868 xcodebuild[22873:499730]  DTDeviceKit: deviceType from 7c4d0fcb017347e75d6affb40397f3a277de6f18 was NULL
info Installing and launching your app on Bide’s iPhone
success Installed the app on the device.

React Native version:
$ npx react-native info
info Fetching system and libraries information...
System:
    OS: macOS 10.15.6
    CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
    Memory: 142.27 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 14.6.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.7 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
    Android SDK: Not Found
  IDEs:
    Android Studio: 4.0 AI-193.69<IP_ADDRESS>26763
    Xcode: 12.0/12A7209 - /usr/bin/xcodebuild
  Languages:
    Java: 14.0.1 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: ^4.10.1 => 4.10.1
    react: ~16.11.0 => 16.11.0
    react-native: ^0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

$ npx react-native run-ios --device "Bide’s iPhone"

Expected Results
The app to launch on the iPhone
What I tried already
$ rm -rf node_modules
$ npx pod-install
$ npm i
$ brew upgrade ios-deploy

Still not working. It launches from Xcode tho, but I cannot properly work on it without the Fast Refresh

+1. Facing same issue

+1 Struggling with this issue too

+1

+1

I'm facing the same issue since Xcode 12 update for the two apps I'm working on. The build is ok, but nothing happens on the device, the apps are not installed whatsoever. I've tested on iPhone and iPad running iOS 14 and even tried on iOS 13.
Apps are running smoothly on simulator.
(Please note that I had to use the patch from https://github.com/facebook/react-native/issues/29279 to fix images display but I don't think It's related.)
Here's my react-native info :
➜ npx react-native info
info Fetching system and libraries information...
System:
    OS: macOS 10.15.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 566.09 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.22.0 - ~/.nvm/versions/node/v10.22.0/bin/node
    Yarn: 1.22.4 - ~/.nvm/versions/node/v10.22.0/bin/yarn
    npm: 6.14.6 - ~/.nvm/versions/node/v10.22.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
    Android SDK:
      API Levels: 28, 29, 30
      Build Tools: 28.0.3, 29.0.3
      System Images: android-24 | Google APIs Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom_64
  IDEs:
    Xcode: 12.0/12A7209 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.5 => 0.61.5

Anyone got it fixed by a way or another since?

I noticed the same thing, couple of changes did the trick for me.

unpair the device and repaired it from the Devices and Simulators window in Xcode, using a cable.
added one argument to force debug mode to be on.

npx react-native run-ios --device "Bide’s iPhone" --configuration "Debug"

I’m still facing some issues here. I've tried the solutions described in this other issue (#30028) without any success whatsoever.
My apps have two schemes in Xcode. One for our production API and another one for our staging API.
I’m launching my commands via a makefile.
The production scheme which is the default one can be launched on a device with this command and is working fine on device:
run-on-ios@production: export ENVFILE = .env.production
run-on-ios@production: ## Run on iOS device [PROD]
	./node_modules/.bin/react-native run-ios --port ${BUILDER_PORT} --configuration Debug --device $(IOS_DEVICE)

But the Staging scheme fails silently to launch on device with run-ios with this command:
run-on-ios@staging: export ENVFILE = .env.staging
run-on-ios@staging: ## Run on iOS device [STAGING]
	./node_modules/.bin/react-native run-ios --port ${BUILDER_PORT} --scheme Staging --configuration Staging.Debug --device $(IOS_DEVICE)

I can see a success message at the end.
▸ Build Succeeded
info Installing and launching your app on iPad de dev Mounki
success Installed the app on the device.

I'm a bit clueless here. 🤷♂

Guys I messed around with npm, rm -rf node_modules, npx react-native run-ios  --device "Bide’s iPhone" for days until I don't even recognize my package.json file and today, I tried again from the beginning and it worked literally without any change on my repo. I don't even need --configuration "Debug"
This is pure magic, don't know what to say.

أُرسلت من الـ iPad

في 18/09/2020 الساعة 6:07 م، كتب/كتبت bidetaggle notifications@github.com:

Description
When I want to start the app on my physical iPhone, everything seems to work well but nothing happen on the phone. It was working well yesterday. Today I opened Xcode and there were a pop-up saying that Xcode needs to install some stuffs, I clicked Okay and wait for the progress bar to finish. Nothing else has changed, only an update for Safari, no mac update, no iPhone update since.
Here is the output:
npx react-native run-ios --device "Bide’s iPhone"
info Found Xcode workspace "kisschatproudchat.xcworkspace"
instruments is now deprecated in favor of 'xcrun xctrace' (see man xctrace for more information on its replacement)
info Building (using "xcodebuild -workspace kisschatproudchat.xcworkspace -configuration Debug -scheme kisschatproudchat -destination id=7c4d0fcb017347e75d6affb40397f3a277de6f18")
......................................................................
info Installing and launching your app on Bide’s iPhone
success Installed the app on the device.
React Native version:
$ npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 10.15.6
CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Memory: 142.27 MB / 8.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.6.0 - /usr/local/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.7 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
Android SDK: Not Found
IDEs:
Android Studio: 4.0 AI-193.69<IP_ADDRESS>26763
Xcode: 12.0/12A7209 - /usr/bin/xcodebuild
Languages:
Java: 14.0.1 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: ^4.10.1 => 4.10.1
react: ~16.11.0 => 16.11.0
react-native: ^0.62.2 => 0.62.2
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
$ npx react-native run-ios --device "Bide’s iPhone"
Expected Results
The app to launch on the iPhone
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@bidetaggle it couldn't have been magic, some configuration might have been changed that makes it work.

Well it really looks like magic and I was expecting someone to explain how it's not 😆
For now, it works well only on my personal hotspot using my data plan. For any other WiFi (home, working place, friend's place) the app will launch and quit without any error, the metro server is unreachable from the iPhone. What can I do about it?

+++1

Xcode 12.2 Beta 4
iOS 14.0
react native 0.61.5
npx react-native run-ios
error:
2020-11-12 15:31:29.919 xcodebuild[49422:365431]  DTDeviceKit: deviceType from 00008030-00190D5A3A04802E was NULL
** BUILD FAILED **

The following build commands failed:
	CompileC /Users/mac/Library/Developer/Xcode/DerivedData/RoadArchives-exjnpbkrtnvnumfundufcrkbooyi/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/Yoga.build/Objects-normal/x86_64/yoga_vers.o /Users/mac/Library/Developer/Xcode/DerivedData/RoadArchives-exjnpbkrtnvnumfundufcrkbooyi/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/Yoga.build/DerivedSources/yoga_vers.c normal x86_64 c com.apple.compilers.llvm.clang.1_0.compiler
	CompileC /Users/mac/Library/Developer/Xcode/DerivedData/RoadArchives-exjnpbkrtnvnumfundufcrkbooyi/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/Objects-normal/x86_64/jsinspector_vers.o /Users/mac/Library/Developer/Xcode/DerivedData/RoadArchives-exjnpbkrtnvnumfundufcrkbooyi/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/DerivedSources/jsinspector_vers.c normal x86_64 c com.apple.compilers.llvm.clang.1_0.compiler
(2 failures)

Xcode run APP
Details
Unable To Install “路桥”
Domain: IXUserPresentableErrorDomain
Code: 1
Failure Reason: Please try again later.
Recovery Suggestion: Failed to load Info.plist from bundle at path /Users/mac/Library/Developer/CoreSimulator/Devices/272E784E-49DB-4EAF-9F2C-1C2975564066/data/Library/Caches/com.apple.mobile.installd.staging/temp.MwHyED/extracted/RoadArchives.app/Frameworks/RCTVibration.framework; Extra info about Info.plist: Couldn't stat /Users/mac/Library/Developer/CoreSimulator/Devices/272E784E-49DB-4EAF-9F2C-1C2975564066/data/Library/Caches/com.apple.mobile.installd.staging/temp.MwHyED/extracted/RoadArchives.app/Frameworks/RCTVibration.framework/Info.plist: No such file or directory
--
Failed to load Info.plist from bundle at path /Users/mac/Library/Developer/CoreSimulator/Devices/272E784E-49DB-4EAF-9F2C-1C2975564066/data/Library/Caches/com.apple.mobile.installd.staging/temp.MwHyED/extracted/RoadArchives.app/Frameworks/RCTVibration.framework; Extra info about Info.plist: Couldn't stat /Users/mac/Library/Developer/CoreSimulator/Devices/272E784E-49DB-4EAF-9F2C-1C2975564066/data/Library/Caches/com.apple.mobile.installd.staging/temp.MwHyED/extracted/RoadArchives.app/Frameworks/RCTVibration.framework/Info.plist: No such file or directory
Domain: MIInstallerErrorDomain
Code: 35
User Info: {
    FunctionName = "-[MIBundle _validateWithError:]";
    LegacyErrorString = PackageInspectionFailed;
    SourceFileLine = 131;
}
--

System Information

macOS Version 10.15.6 (Build 19G2021)
Xcode 12.2 (17535) (Build 12B5044c)
Timestamp: 2020-11-12T15:42:33+08:00

FWIW I replugged my iPhone and now it works

@rzrobert Your problem is not related to this issue, i'm closing it because it's outdated now.
According to your error, I suggest you to search for MIInstallerErrorDomain and RCTVibration on google.

I having same issue with fresh project created by react-native init

I did npm install and pod install
Emulator working fine but physical device doesn't download application from metro or other message came from metro.
there is only one connected device and here is my build command for ios device
"npx react-native run-ios --device"
And other hand I tried past loaded applications on ios device by react-native and metro same thing happened but I open application myself and touched reload js after that everything become normal for this build process.
It's happening in all projects from past day it's started suddenly from one project when I m trying to build.
Does anyone have any idea ?


Notebook doesn't know the name of the secret scope

The operator is creating Databricks Secret Scopes with name instance.ObjectMeta.Name and appending "_scope"
However our notebooks don't know the value of instance.ObjectMeta.Name and hence cannot construct the secret scope name.

Proposed fix:
The controller can automatically add a parameter to the job run, which can be called "_secretScope". The underscore implies a system generated parameter.
I think it's preferrable to explicitly pass the secret scope, rather than having to append _scope to the "run name"

https://github.com/microsoft/azure-databricks-operator/blob/master/controllers/notebookjob_controller_databricks.go

expect this to change in the future, but for now you can get the secret scope created for the run using:
secret_scope_name= dbutils.widgets.get("secret_scope")

then get a secret using:
secret_val= dbutils.secrets.get(scope=secret_scope_name, key="secret key")


Amount is not shown round up on “Buy # Gold” button from “Buy Gold” Review screen when a user buys gold by entering the USD amount.

Frequency: 100%
App version: IOS test flight build v1.5.2 (18)
Repro on: iPhone 7 (13.3), iPhone 7+ (12.4), iPad pro 2nd Gen (13.2.2)
Repro Steps:

Launch the app.
Tap on Gold tab.
Tap on the “Buy Gold” button.
Tap on “Switch to Gold” link.
Enter an USD amount and tap on the Review button.
Observe on Buy # Gold button.

Investigation:

Issue also reproduced in the “Gold Activity” section when exchange activity is under progress.
Issue does not repro after completing the Exchange process.
Issue does not repro when a user sells Gold by entering the USD amount.

Current Behavior: Amount is not shown round up
Expected Behavior: Amount should be shown round up.
Attachment: IOS_RoundUpIssue_GoldTab.png.

I believe this has been addressed

@tarikbellamine I have verified this issue using latest build Android internal build v1.1.0<PHONE_NUMBER>) and Test flight build v1.1.0 (23) and found issue is fixed
Device: iPhone 11 (14 iOS)


card: fix action-bar z-index & pointer events

What You're Solving

ActionBar needs a z-index > 0 because it may contain an ActionMenu that
overflows the card. The z-index will prevent the menu from going behind other
cards.
Set pointer-events on ALL children of action-bar to be all so users
can interact with them. Allowed us to remove the pointer-events on
ActionBar buttons specifically.

How to Verify
Easy way: look at these screenshots:
Before:

After:

Hard way:
Add some element to an ActionBar that overflows the card (ex: ActionMenu). Notice that the action-menu no longer goes behind the next card. It appears on top instead.

Not sure what we should do with this issue atm.

I merged it.  Let's do this thing!  Thanks for your obvious patience, @KaidenR .

Thanks for your time and input on this @jaketrent!


Battleborn ASI bug and extra darkvision

With flexible races mod feature on, the race doesn't allow you to pick your own stats. The attributes are also visually all mixed and CON is missing (should still be present but greyed out iirc) with and without flexible races option enabled (screenshot below).
There is extra darkvision feature added on race. Warforged originally don't have darkvision.

Battleborn_Test.zip - Save here if needed.

@otearaisu


Homepage textoverflow

Before:

After:

In this cases (and other like what @monsieurtanuki mentionned for the scan screen on his phone), is reducing the font size an option ?

@M123-dev Well done!
I also somehow agree with @teolemon: maybe some day we'll have a clearer view of what we want as a layout. And in some cases, we should be able to say "I want THIS text to be on one line only" (there's probably a flutter widget for that). That would also mean stricter translation rules: "I want THIS label to be short, like less than 15 characters".
But for the moment, the Flexible is good enough.
Feel free to merge.

I'll investigate that


My secret Power, yes I've thought about this before this class

No one can tell me being stupidly pretty and rich isn't a super power.

I want that superpower too!
If you haven't already, please fill out a post-workshop survey. I'm always trying to redefine and make this a better workshop:  https://tinyurl.com/la-tech-workshop


SAK-40029 Display problem with i18n and HTML entities in a peer asses…

…sment
The string is escaped already:
https://github.com/sakaiproject/sakai/blob/master/assignment/tool/src/java/org/sakaiproject/assignment/tool/AssignmentAction.java#L1869
https://github.com/sakaiproject/sakai/blob/master/assignment/tool/src/java/org/sakaiproject/assignment/tool/AssignmentAction.java#L3186
https://github.com/sakaiproject/sakai/blob/master/assignment/tool/src/java/org/sakaiproject/assignment/tool/AssignmentAction.java#L3879
https://github.com/sakaiproject/sakai/blob/master/assignment/tool/src/java/org/sakaiproject/assignment/tool/AssignmentAction.java#L4401

LGTM!

I also see this in
tool/src/webapp/vm/assignment/chef_assignments_instructor_preview_grading_submission.vm
25:                        $validator.escapeHtml($!submitterNames)

Okay thanks for double checking @juanjmerono !


Add human readable alias support for backend dev environment

Add human-readable alias support for backend dev environment to help easier debugging and backend integration tests.

Very cool! I think for this to technically be complete in the dev environment, the latest changes need to be applied to dev-shared as well, and then I think https://api.dev.napari-hub.org/dev-shared/ would work. Is that right?

Deploying changes to dev-shared and tested changes work https://api.dev.napari-hub.org/dev-shared/


Be able to copy hex values without hash prefix

(This is an attempt to tackle https://github.com/yeun/open-color/issues/50)
Following the issue linked above, I removed the onclick attribute of the second input element containing the hexadecimal value of the color.
Before: Clicking the hex value resulted in focussing and selecting the complete value including the # prefix.
Now: A click does not yield a special functionality anymore. The hex value (without the #) can be selected by double-clicking. A triple-click will select the hex value including the #.
This change introduces a inconsistency. Clicking on the variable input above will still focus and select the complete variable. The behavior for the hex input element however will be different.
One way to remove this inconsistency would be removing the onclick attribute for the variable input element as well. However I think this would be a step backwards because copying the complete variable should be desirable in most cases.
The other way would be using JavaScript to select the hex value with more fine-grained control. For example, clicking once would select only the hex value without the prefix #, clicking twice would select the complete value with the prefix.
I prefer the solution suggested in the form of the pull request itself because it is simple and results in no big problems as far as I’m concerned.

That's simple :)


Argo SSO UserInfo Groups field change to configurable param

Summary
We are running Argo Workflow, the SSO authentication works nicely, but we do not see the users's groups. Because the user info got from remote userInfoPath does not have "groups" field, but "memberof" field, and default UserInfo struct can not receive the response. Now we want to make the groups field to configurable param in ConfigMap, so that we can flexible configure userInfo "groups" field according to individual necessary.
Default UserInfo struct:

Use Cases
We can add "sso.userInfoGroupsField=memberof" in argo-workflows-workflow-controller-configmap, and argo sso will get user info groups info by "memberof" field from remote userInfoPath.

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

You can already use customGroupClaimName to achieve this. See https://argoproj.github.io/argo-workflows/argo-server-sso/#custom-claims


Maintain internal pause on tracks with zero frequencies

Definitely was against copying all logic from SampleChannelBass to TrackBass, and wasn't sure about having a very small BassZeroFrequencyPauser helper class, so I decided to introduce a class that does all the relevant shared logic, which is taking in relative frequency values, converting them to actual channel frequencies, and handling the case where the relative frequency value may be 0, by requesting the component to maintain an internal pause of their channel.
Test cases were added inside TrackBassTest instead as tracks show their current time, thus making it easier to test headlessly. (and saves up from having another track test scene)

Made naming changes here, reworded xmldocs. Think the diff reads way simpler (and therefore better) with the new names.


add crash when failure in list or watch of kubernetes api server

Description

Address "Flanneld doesn't reconnect to the apiserver" - https://github.com/coreos/flannel/issues/1272
Add crash when failure in list or watch when talking to kubernetes api server. This should result in a retry loop for the connection (due to flannel being restarted).
Ideally the retry loop should be fully encapsulated inside flannel, however I didn't have much time to fix this problem. And it has been a month and no one has offered a better solution. I hope that this PR sparks that.
Todos
- [ ] Tests
- [ ] Documentation

[x] Release note

Release Note

Workaround for not reconnecting to api-server in windows

Valid enhancement, but we should probably use the informer factory from client-go tools.

This fix is crucial! I'm struggling with this issue since I first created a windows based kubelet!

Not sure if we should Exit. Can we use the 'context' and cancel it instead?
So that an appropriate cleanup can happen.
@Oats87 PTAL

@rajatchopra Looking at this, I think it is safe to merge this PR with the idea to perform a future enhancement to move to utilizing the nodeInformer factory, although interestingly in client-go itself there is not behavior similar to this: https://github.com/kubernetes/client-go/blob/master/informers/core/v1/node.go#L64

For #1272 we should improve the reconciliation loop. We should recover from the error with retries (exponentially backing ones if at all), rather than exiting i.e. establish a new connection to apiserver.
@KnicKnic Your opinion please?
Closing this PR, please re-open if anyone thinks otherwise.


Feature/built in slices

Adds built in methods to encode/decode some slices types

Codecov Report

Merging #104 into master will decrease coverage by 0.72%.
The diff coverage is 58.33%.

@@            Coverage Diff             @@
##           master     #104      +/-   ##
==========================================
- Coverage   98.71%   97.98%   -0.73%
==========================================
  Files          36       38       +2
  Lines        5225     5321      +96
==========================================
+ Hits         5158     5214      +56
- Misses         52       84      +32
- Partials       15       23       +8

Impacted Files
Coverage Δ

encode_slice.go
50% <50%> (ø)

decode_slice.go
66.66% <66.66%> (ø)

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 bf5c9d9...0994f7a. Read the comment docs.


Add lombok to JournalEntry module

Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[x] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[x] Create/update unit or integration tests for verifying the changes made.

[x] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[x] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

[x] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

@hmg65 PR is conflicting and there are build issues, please check.

The Dev needs to make sure there is sufficient test coverage and the design is discussed on list.  If the JIRA Ticket is present, it needs to be linked and the title of the PR needs to be changed.

@hmg65 Please resolve the conflicts


Replaced mouseover and mouseout with mouseenter and mouseleave so that nested elements don't close popups.

Before submitting the PR:

[ x ] Does your PR reference an issue? If not, please chat to the team on Discord or GitHub before submission.
[ x ] Did you update and run tests before submission using npm run test?
[ x ] Does your branch follow our naming convention? If not, please amend the branch name using branch -m new-branch-name
[ x ] Did you update documentation related to your new feature or changes?

What does your PR address?
Fixes #1379

I've made it fairly clear that I'm not accepting new popup-related pull requests until the refactor is complete. I'm sorry, but I'm going to have to deny this. Note the issue and this can be handled as part of that. You can even reference this PR as a suggestion for a fix.


Support Elasticsearch v8

Elasticsearch 8 introduced a breaking change to certain API methods, namely the removal of _type from responses.
This requires Elasticsearch v7 Java clients to enable compatibility mode, which is available from v7.17.1.
Additionally, changes have been made to allow configuration of the client connection pool, which is useful for Stroom nodes with more than 10 concurrent indexing workers.

Superseded by #2861


Pin opam-* packages to 2.3.0~alpha1 that includes performance fixes.

See opam PRs #6144 #6122 for more details.
Includes various performance fixes https://github.com/ocaml/opam/blob/master/CHANGES#L58-L66

Title seems wrong; it's actually unpinning them! The change is good, though.


chore: adjust prow tide probe conf

During periods of high traffic, the tide interface response will be very slow and there is a probability that it may cause Pod restarts. During the initial startup period, the healthy interface response will also be slow, but the service can still handle other requests normally. Therefore, modify the probe settings to perform liveness and readiness checks five minutes after the service starts.
To prevent resource shortages from causing service restarts, set resource limits to 1 core and 4GB.

/hold

fixed in #1256


fixed: cscope doesn't work on windows.

https://github.com/ludovicchabant/vim-gutentags/issues/173

Heya! Thanks for the PR.
The code you removed is for when the cscope DB is to be placed in Gutentags' cache folder (i.e. not inside the project root directory). Is that what you're using?

Yes, I have this in my vimrc:
let g:gutentags_cache_dir = expand('~/.cache/tags')

Ah ok thanks.
So that's weird, since, if %FILE_LIST_CMD% is empty, it shouldn't go at all in that code branch (there's a if NOT ["%FILE_LIST_CMD%"]==[""] a few lines above). So that must not quite be the bug?


error while adding entry to ip cache: value=[]

level=error msg="not adding entry to ip cache; error unmarshaling data from key-value store" error="unexpected end of JSON input" key=cilium/state/ip/v1/default/xxx.xxx.xxx.xxx value="[]"
level=error msg="not adding entry to ip cache; error unmarshaling data from key-value store" error="unexpected end of JSON input" key="cilium/state/ip/v1/default/xxxx::xxxx:x:x:xxxx" value="[]"

There already is an issue tracking this; https://github.com/cilium/cilium/issues/3206 . I have a fix coming for it soon.


Tile Grid Object Collection needs some rework

Describe the bug
Today, i tried to use Tile Grid Object Collection ..
first of all : "Centered" option is bugged (missing parenthesis in the code arround Column - 1)
secondly : does not derive from BaseObjectCollection or GridObjectCollection
third (link to 2nd) : the position is updated constantly in the Update() function (performance issue)
fourth : typo in property LayoutDireciton
lastly, not sure what the difference is from Grid, and documentation is not very explicit (and misleading, as we can think it inherit from Grid) :

TileGridObjectCollection.cs provides some additional options to GridObjectCollection

Expected behavior
minimal : fix 1 and 4
optimized: inherit from Grid and document better to tell what are the differences
radical : remove TileObjectCollection
Your Setup (please complete the following information)

Unity Version [2018.4.9f1]
MRTK Version [2.1 stabilization]

Additional context
I can help and make a PR based on decision

Fixed by #6550 ,


hubble/metrics: Add source_ip/destination_ip labels to contextLabels

Update hubble metrics to support exposing the source/destination IP as source_ip and destination_ip labels.
hubble/metrics: Add source_ip/destination_ip labels to contextLabels

PR is currently based on https://github.com/cilium/cilium/pull/21181

/test

/test

/test-1.24-4.19

/mlh new-flake Cilium-PR-K8s-1.24-kernel-4.19

/test-1.25-net-next

I don't have context for this PR. It looks like a Hubble change primarily? I'm not sure what the context labels is as source and destination ips are already dumped in the flow logs.

I've updated the PR description. It's primarily about adding the IPs as labels into hubble metrics.

/test

/ci-multicluster

Marking as ready to merge, CI was green prior to the rebase and the conflict was minor and due to #21320 changing the same line for the metrics labels.


Upgrade Swagger 2.2.13 -> 2.2.14

This PR contains the following updates:

Package
Type
Update
Change

Swagger
compile
patch
2.2.13 -> 2.2.14

Release Notes

swagger-api/swagger-core
v2.2.14: Swagger-core 2.2.14 released!
Compare Source

OAS 3.1 siblings in refs resolving (#4441)

[ ] If you want to rebase/retry this PR, check this box

Warning
Renovate's suggested commit message is being replaced with improved initial commits to enable automerging. As a side effect, these suggested commit messages might have changed. Consider comparing the initial commit message and this message to determine the most suitable one. Please leave feedback in #sys-renovate.

Suggested commit message:
Upgrade Swagger 2.2.13 -> 2.2.14

See:
- https://github.com/swagger-api/swagger-core/releases/tag/v2.2.14
- https://github.com/swagger-api/swagger-core/compare/v2.2.13...v2.2.14


Update ZAP to get support for "requires timed interaction" quality.

Problem
Need support for this quality.
Change overview
Adds a way to annotate things as requiring timed interaction in XML.
Testing
Verified that upcoming PRs I have can use the resulting boolean in template generation.

fast track: dependency update only, CI should find if  any issues exist (because we check zap output)


Invalid character '<' looking for beginning of value

Invalid character '<' looking for beginning of value
Error getting session token from NVIDIA retrying
Is this due to Nvidia changing up their API?

closing in favor of #116 NVIDIA's entire store API is down right now see there for tracking


Would you be interested in merging repos?

I have been working on a new orgmode for sublime. It has quite a bit of functionality.
Agenda, RevealJs export, HTML export, limited babel support, code block support, inline image preview, tag search, tab cycling, property drawers, scheduling, etc etc ad nauseum.
I actually used your excellent package as a starting place to learn about package development among other things.  I site you with credit for your excellent work.
As I went to post the package on package control I was asked if I had approached you about merging into your package and becoming a maintainer of the repo.
Thoughts?
https://github.com/ihdavids/orgextended

Your version looks much better and have gotten a lot more love then mine =)
So sounds like a good idea, how do we proceed?

Your version looks much better and have gotten a lot more love then mine =)
So sounds like a good idea, how do we proceed?

Whelp... I am still trying to incorporate at least some of the feedback from my review as I was trying to submit my package. I figure that input is probably good to respect regardless of if we go this route or not.
I would want to still have shared control with you over the plugin. Would that be okay?
If so, probably the easiest way to go about this is to add me as an owner to your repo.
I can then take and integrate / clobber your repo with a drop from my repo then we can tag it as a 2.0.0 version of the plugin. We can proceed together in moving the plugin forward?  I wrote it for me, so having more eyes on it would probably only have positive benefits... might even encourage me to write better code. :)
I have removed the docs folder from my repo and moved them to their own repo.  Sooo. I can move that as well to another repo (so the name can reflect the name change in the plugin) and add you to that as well as an owner.

Whelp... I am still trying to incorporate at least some of the feedback from my review as I was trying to submit my package. I figure that input is probably good to respect regardless of if we go this route or not.
I would want to still have shared control with you over the plugin. Would that be okay?
If so, probably the easiest way to go about this is to add me as an owner to your repo.
I can then take and integrate / clobber your repo with a drop from my repo then we can tag it as a 2.0.0 version of the plugin. We can proceed together in moving the plugin forward?  I wrote it for me, so having more eyes on it would probably only have positive benefits... might even encourage me to write better code. :)
I have removed the docs folder from my repo and moved them to their own repo.  Sooo. I can move that as well to another repo (so the name can reflect the name change in the plugin) and add you to that as well as an owner.


How to contribute a new molecule?

What is the list of files needed?

Answer: these 8 files.

What is the minimal validation required?

Answer: probably logP and density.

The development of PR https://github.com/ricalessandri/Martini3-small-molecules/pull/14 will shape this procedure.


Add Facebook Adapter migration

Description
This PR has the current migration to .Net of the FacebookAdapter Package from the BotKit repo.
Also, we added a TestBot for testing the current implementation.
Details
We have migrated the following classes:
FacebookAdapter
FacebookAdapterOptions
FacebookClientWrapper
And added some helper classes:
FacebookHelper
FacebookMessage
Message

Pull Request Test Coverage Report for Build 81350

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.2%) to 78.374%

Totals

Change from base Build 81336:
1.2%

Covered Lines:
4135

Relevant Lines:
5276

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.3.1

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.3.1

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.3.1

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.3.1

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3

@matiasroldan6 Thanks for the changes. Please resolve conflicts for this branch and then I can approve.

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3

@matiasroldan6 @ceciliaavila Just Facebook remaining now. Will approve / merge once merge conflicts have been resolved.

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3


The function detect_heartbeats is not handling the absence of signal correctly

The function detect_heartbeats() can be easily confused when presented with time series containing a flat signal e.g. at the beginning of the recording.
from scipy.misc import electrocardiogram
from sleepecg import detect_heartbeats

# This works as expected
ecg = electrocardiogram()
detect_heartbeats(ecg, fs=1000)

# However, even when presented with 60 seconds of flat signal, the function still returns (a lot of) peaks
detect_heartbeats(np.repeat(-1.5, 60000), fs=1000)

The problem is that the flat signal at the beginning or at the end of the time series is not discarded automatically. Of course, better performance is achieved by providing better quality data, but I think this is something that should be automatically handled by the function: no peak detection on the portion of the signal consisting of consecutive constant values over at least n samples, at the beginning or at the end (ideally also if this happened during the recording).
In addition to that, the erroneous detection of (lot of) peaks in these segments appears to considerably slow down the function itself, the following time series (~1h ECG recording starting with ~45 s of flat signal) can for example completely crash the function that will hang forever (or at least for a very long time).
ecg.zip

Yes, this is a property of the Pan-Tompkins detector, which expects a heartbeat after a certain amount of time. I agree we should have some kind of (optional) preprocessing, which detects e.g. flat segments (which is relatively easy) and extremely noisy segments (which is probably hard). In such segments, no heartbeats should be detected. The thresholds of the detector should probably remain constant until the next good data segment – but this is also open for discussion.
I think one way to detect flat segments could be to only perform a certain number of threshold decreases. I think currently we do it 16x, and then we just take the peak that's in that signal. We could instead say that if there is no clear peak after e.g. 8x lowering the thresholds, we skip it. But this wouldn't be the classic Pan-Tompkins anymore, so I'd prefer a separate preprocessing step.
How do other packages solve this issue?

Yes, I think the classic Pan-Tompkins version implemented here should at least be fixed so that it does not run forever with signals like the one I shared, so skipping after a given number of thresholds could maybe solve this.
One solution could be to have an optional mask parameter for this function to discard peak detection in some segments. This mask could be used "while" Pan-Tompkins is running (don't know if it is possible), or before the function call by slicing only the valid portion of the signal, and fitting these segments separately (don't know if this is efficient). It would then be reasonable to automatically discard flat segments as their definition is quite simple, and let the user define what is noisy or not?

I agree something should be done to address these situations. I need to think a bit more about what the best solution would be. In addition, I do not have a lot of time to work on this at the moment, but if you would like to give it a shot please go ahead! I'm happy to discuss any details and questions of course, I just don't have time to actually implement something in the near future.

What about flat segments in the middle of the data? I always thought that the detector forcibly finds a heartbeat after a certain amount of time after the previous detection, no matter what the signal looks like. Is this not the case? Can you maybe show how it performs in the presence of flat segments at the beginning, in the middle, and at the end of the data? I think it would be important to know what the detector does before deciding how to proceed.

Flat data at the beginning: ❌
Flat data in the middle: ❌
Flat data at the end: ✅

import sleepecg
import numpy as np
from scipy.misc import electrocardiogram

ecg = electrocardiogram()  # 5 min of ECG data
sf = 360

y_true = sleepecg.detect_heartbeats(ecg, sf)
y_true.shape  # 478 true peaks

# Flat data at the end: 478 peaks detected. PASS.
ecg_pad_after = np.pad(ecg, pad_width=(0, ecg.size), mode="edge")
pks = sleepecg.detect_heartbeats(ecg_pad_after, sf)
print(f"{len(pks)} detected peaks")

# Flat data at the beginning: 1943 peaks detected. FAIL.
ecg_pad_before = np.pad(ecg, pad_width=(ecg.size, 0), mode="edge")
pks = sleepecg.detect_heartbeats(ecg_pad_before, sf)
print(f"{len(pks)} detected peaks")

# Flat data in the middle: 926 detected peaks. FAIL.
ecg_pad_middle = np.hstack((ecg_pad_after, ecg))
pks = sleepecg.detect_heartbeats(ecg_pad_middle, sf)
print(f"{len(pks)} detected peaks")

Here's what this looks like:

Detection critically relies on the two thresholds. If these are bad, it takes a long time for the detector to recover. That's why padding afterwards works, padding in the middle works OK, and padding at the beginning doesn't work but eventually yields correct peak towards the end.
So "flat data in the middle" should not get a ❌, but rather a ≈.

Oh right, thanks for catching my mistake with the flat data in the middle. Of course we're expecting twice the number of peaks 🤦♂

Yes. It would be worth a shot.


run logs in README example are expired

The run logs in README example are expired and therefore not visible. Since it's a big part of the example it would be great if they were at least rerun. To increase resiliency something like screenshotting the most relevant bits and adding them directly to the README might make rerunning less urgent in the future?

Hi @pxhanus
Thanks for letting me know. I've updated the link to a fresh run for now and I'll think about how to handle expired runs. A screenshot might be a good idea.
Thanks!


Allow non-promise result for synchronous actions

Allow this code:
actions: {
        hello() {
            return `Hello Moleculer`;
        }
}

Coverage remained the same at 98.175% when pulling 5aa3b0ae7b442ef4ccc2102ee3f91bc5d0075058 on askuzminov:fix-d.ts-action into 07704ccd5d7941e6c92b385f6e340da476c21e13 on ice-services:master.


Hide @nonVirtual methods in autocomplete?

When a method is marked @nonVirtual it should not be overridden. Yet, my IDE suggests it as an overridable method (see below) and as soon as I accept that suggestion, the analyzer complains that I should not be overriding this method (invalid_override_of_non_virtual_member). Should @nonVirtual methods just be excluded from the suggestion list of overridable methods?

cc @bwilkerson as I assume these suggestions are powered by the analyzer?
I ran into this working on the @Stateful macro while looking for ways to stop the "fake" superclass methods (that are only there to satisfy the type system hack) from messing up people's autocomplete.

Yes, these suggestions come from the analysis server, and yes, we should exclude non-virtual methods.


[Exam] several style fixes & tooltips

Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.

Motivation and Context

The save & continue / save button did not make sense and hiding it by ngIf caused problems with the layout of the nav.
On certain screen sizes the buttons in the exam navigation are overlapping. See https://github.com/ls1intum/Artemis/pull/1767#issuecomment-651818691
Description

The save & continue / save button is now set to not visible in order to keep the layout.
The indicator of the exercise now switches earlier to the smaller display to prevent overlapping. (No overlap is only guaranteed for screen at least as wide as iPads (768px) but it also works until approx. 500px)
Added tooltips for the buttons.
Steps for Testing

Log in to Artemis
Prepare an exam with at least one programming exercise
Check that the save & continue / save button is not shown when working on the programming exercise
Make sure the navigation is displayed correctly even when changing the window size

I've tested this on TS1 and this is the most overlap I've been able to generate:
With a text exercise:

With a programming exercise (ignore the highlighting on time):

It also seems that once I get to that point, the gray button to advance to the next exercise stops being clickable.

@pzdr7 Thanks for testing. Could you also provide the screen size at which it overlaps? So that I can replicate and fix it.

Fixed, I've added the pixel measurements to the screenshots (as provided by chrome's dev tools).

We have a merge conflict now :-(
And I don't think the submitted state is interesting for the tooltips.
I think only the difference between blue (synced) and yellow (not synced) is important.
Only for programming exercises, we should differentiate that yellow can mean the they have unsaved or uncommitted changes

We have a merge conflict now :-(
And I don't think the submitted state is interesting for the tooltips.
I think only the difference between blue (synced) and yellow (not synced) is important.
Only for programming exercises, we should differentiate that yellow can mean the they have unsaved or uncommitted changes

I fixed the conflicts and the longer tooltips including the submitted state are now only shown for programming exercises

I am unsure of the tooltips. How is this not submitted?

Still, in terms of programming exercise: How do I submit it? The submit button does not do it in terms of tooltips!

I fixed it


The maximum value for an int type

Hi!
The following program crashes on x86 architecture:
[   82s] ../go/src/gopkg.in/asn1-ber.v1/length_test.go:83: constant<PHONE_NUMBER>854775807 overflows int
[   82s] ../go/src/gopkg.in/asn1-ber.v1/length_test.go:137: constant<PHONE_NUMBER>854775807 overflows int
See: https://build.opensuse.org/build/home:awissu:branches:devel:languages:go/openSUSE_Tumbleweed/i586/golang-gopkgin-asn1-ber/_log

dupe of https://github.com/go-asn1-ber/asn1-ber/issues/5

published in v1.2


using google-cloud-storage for provider is significantly slower than s3

For whatever reason, uploads using the native google-cloud-storage provider (and boto as the client) seem to be taking WAY longer than the s3 provider (s3 provider but still actually using GCS). Not sure why this is but thought I should note it. Downloads are pretty much just as fast.
Using GCS with the s3 provider:
(env)[cb@test-upload tests]$ time ./upload-local-s3-proxy.py out.csv
Uploading out-180.csv to bucket dabucket
..........
real    0m7.776s
user    0m0.771s
sys     0m0.335s
(env)[cb@test-upload tests]$ time ./download-local-s3-proxy.py out.csv
Downloading out-180.csv from bucket dabucket
..........
real    0m7.512s
user    0m0.981s
sys     0m0.569s

After switching s3proxy to use the google-cloud-storage provider:
(env)[cb@test-upload tests]$ time ./upload-local-s3-proxy.py out.csv
Uploading out-180.csv to bucket dabucket
..........
real    0m45.132s
user    0m0.762s
sys     0m0.316s
(env)[cb@test-upload tests]$ time ./download-local-s3-proxy.py out.csv
Downloading out-180.csv from bucket dabucket
..........
real    0m8.092s
user    0m1.009s
sys     0m0.618s

I suspect that different regions are being tested between AWS and GCS.  Would be good to verify the created container.

GCS and S3 providers have the same performance in my testing.  Please reopen if you can reproduce these symptoms.


Supercollider: fix MIDI support on Linux

This PR fixes broken MIDI functionality in the Supercollider IDE.
Motivation for this change
Supercollider's IDE's MIDI support only works on Linux if compiled with ALSA.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Closing until it works locally...

My attempt on this branch, working on a PR. Seems to work fine locally.


Changes for forget password

What's this PR do? Any additional context?
Doing the text change in the forget password dialog box.
Where should the reviewer start?
Sign in page
How can this be manually tested? (brief repro steps)
Log onto sig in page and click on forget password link and the dialog box will be opened with the changed text.
What are the relevant TFS items? (list id numbers)
88245
Definition of done:

[ ] Title of the pull request is clear and informative
[ ] Add pull request hyperlink to relevant TFS items
[x] For large or complex change: schedule an in-person review session

Reminders BEFORE merging

Get at least two approvals
If you're merging into the development branch then "flatten" or "squash" commits
If merging from development into master then don't "flatten" or "squash" commits

Reminders AFTER merging

Delete the remote branch
Resolve relevant TFS items
(reverse merge) If you merged into master then check to see if there are any changes in master that can be merged down to the development branch (like hotfixes, etc)

@ElakkiyaMohanRajan,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Fill-in-the-blanks challenges should clear feedback message if all answers are correct

Description
Feedback message should be cleared if the blank inputs are all correct.
Affected Page
Any fill-in-the-blanks challenge.
Here is one: https://www.freecodecamp.org/learn/a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/task-12
Steps to Reproduce

Go to any fill in the blanks challenge
Enter an incorrect answer to one of the blanks
Click the "Check your answer" button to get the feedback message display
Change all of the blank answers to correct answers
Click the "Check your answer" button
The completion modal dialog appears, the blank answers are marked as correct, but the feedback message is still present

Expected behavior
Clear the feedback if all answers are correct.
This can be done by adding:
setShowFeedback(false);
setFeedback(null);

to the following if block:
https://github.com/freeCodeCamp/freeCodeCamp/blob/83ecf77f25e518146a5e4ee9ebbe65348ac37b8d/client/src/templates/Challenges/fill-in-the-blank/show.tsx#L152-L154

i will work on this issue


Allow Symfony 3.x Components

This PR allows Symfony 3.x Components to be used.

@padraic can you merge this?

Looks good to me. :+1:

I would suggest to also change the Symfony2 packages from the tilde to the caret operator.
E.g.:
"symfony/finder": "^2.6|^3.0"

As it should not make a difference in the dependency resolution, the dependencies only use one resolution pattern.

@jayS-de tilde to caret done

All checks now passing!


OLS-153: Updated pre-commit hook + updated contributing guide accordingly

Description
Updated pre-commit hook + updated contributing guide accordingly
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[x] Documentation Update
[x] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Closes #OLS-153

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

N/A

/lgtm

/approve


Allow advertising multiple operational identities on the same fabric on Darwin.

We need to check the instance name before coalescing registrations, not just the type, because all operational advertisements for a given fabric have the same type.

Fast-tracking platform-specific fix with platform owner review.


docs: Fix backticks in api protos

Signed-off-by: Albere<EMAIL_ADDRESS>Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/docs

cc @albere

@phlax looking at a reasonable samples this LGTM. Do you have some systematic way to avoid us getting into this pitfall? Can we ban single ticks entirely and use other ways to achieve the same format effect?

/lgtm v2-freeze

Do you have some systematic way to avoid us getting into this pitfall? Can we ban single ticks entirely and use other ways to achieve the same format effect?

yes, and yes
we currently have the Bad RST warning in protodoc the intention is to turn that to error (perhaps with a --continue option)


Add new members to Committers Team in the Locust.io Organization

I suggest we tweak the list of folks with push access to the Locust repo.
@heyman,
Could you invite the following 2 people to become Members of the Locust.io Organization and add them to the Committers Team? (https://github.com/orgs/locustio/teams/committers/members):

@aldenpeterson-wf (Alden Peterson)
@mbeacom (Mark Beacom)

Both Alden and Mark have been active with Locust and demonstrated they are responsible and willing to help maintain the Locust project.  This elevated access will give them the ability to merge PR's and close Issues (among other things), which would be a big help.
There are currently 10 people in the Locust.io Organization with push access to the Locust repo.  It's probably a good idea to audit the list of committers and remove anyone that is no longer active with the project

Only @heyman or @cgbystrom can currently make changes to the Organization as they are the only 2 'Owners'.  If you elevate me to an organization Owner or change my role in the Committers Team to Maintainer, I will happily take care of the changes myself.

Thanks!

Also, I'm not sure what is needed for releasing to pypy but it would be good to expand the list of people who can actually do that, even if only to get new RCs out.

I'm on board to help where I can!
Thanks

Hi, sorry for the delay. I've been mostly AFK this whole summer. I've added both @aldenpeterson-wf  and @mbeacom as committers now. @cgoldberg is currently a maintainer for the PyPI package. Let me know if I should add someone else as well.

Sounds good!

@heyman @cgbystrom  Would it be possible for @aldenpeterson-wf and myself to receive pypi publishing access?  We'd love to resolve the 0.8 pip installation issues and get the ball rolling on releases again.
Thank you!

+1 it's been pretty frustrating trying to come on board and basically seeing that there's not a lot of involvement from anyone other than @mbeacom.
That's not necessarily a bad thing as long as people who are active and involved can actually get stuff done and it'd be nice.
Selfishly I know a few of my PRs are getting a lot of drive-by love and it'd be great to get them into an RC at the very least so that we can verify the 0.8 package and let people play with it.
Right now, that entire process is hung though so more people with the ability and desire to be involved would be great 🎉

Solved and then re-solved, now with new members and a suggested approach for automatically pushing to pypi!


Fix: Client error when dragging card far away

When dragging a card far away outside canvas, a error shown as 'An error occurred on client'.
Problem found when testing #834 with commit 759d01c in QA env. Since code is not released, problem doesn't happen in Prod.
Console error shown as below:

@QiJin-Bouvet Ready for test

Tested with commit efe858f in TEST.
Problem not happen any more.


Properly opt out of taskprov tasks

Discussion: https://github.com/cloudflare/daphne/pull/709#discussion_r1823230576
Relevant spec: https://ietf-wg-ppm.github.io/draft-ietf-ppm-dap-taskprov/draft-ietf-ppm-dap-taskprov.html#section-4.4-3.1.1
We don't reject when a task id does not match the task config

To clarify: This only happens when we've already configured the task, in which case we use the previously configured task config to handle the request and not the advertised config.


RMC-128 Increase IAC Column Length

Motivation and Context
The case service needs to be able to handler longer IAC's.
What has changed

Increased character length of IAC column

How to test?
Follow the instructions in https://github.com/ONSdigital/iac-service/pull/26 to test with longer IAC's
Links
https://trello.com/c/b5Wr4lEK/639-rmc-128-generate-and-assign-census-style-uac-5
https://github.com/ONSdigital/census-rm-docker-dev/pull/11
https://github.com/ONSdigital/iac-service/pull/26
https://github.com/ONSdigital/census-rm-kubernetes/pull/33

 RMC-128 Generate and Assign Census style UAC (5)


[Request] Awesome Flutter Project

Please provide links and information in the following format
github: https://github.com/karx/FlutterArsenal
tag:    test2
excerpt:   test2

asdasd


Using KCL Version 2.0 to support fan-out with Push rather than Pull

Hello, Kinesis Client Library Version 2.0 now supports fan-out with data being pushed to consumers (https://docs.aws.amazon.com/streams/latest/dev/enhanced-consumers.html). I wonder if spring-cloud-stream-binder-aws-kinesis can use this version to support the PUSH approach too? Thanks

@artembilan Is there any update on AWS 2.x migration .I am also keen to contribute, please let me know how can I start doing that.

Sorry, until AWS Labs fixes issues mentioned in that SI-AWS issue I've just commented your back, we cannot move on.


Relook at design and performance

I just worked on it to pick up GoLang. As it is all up and running now, need to relook at its design, data structures, and algorithms, to make it better.

Also, make sure that the theme/flow is similar in all flows/actions.

The majority of this is taken care of under https://github.com/goyalmunish/reminder/pull/73 and https://github.com/goyalmunish/reminder/pull/74.
For the rest, we will create individual issues.

The majority of this is taken care of under https://github.com/goyalmunish/reminder/pull/73 and https://github.com/goyalmunish/reminder/pull/74.
For the rest, we will create individual issues.


Add yaml header to repo.yml

This is a test to see if external contributors can modify files outside of .github/.

getting closer

getting closer, if it works, balena-io/deploy-to-balena-action#234 should fix it @klutchell cc @20k-ultra

I was about open an issue for this but I see @ab77 is all over it!

getting closer, if it works, balena-io/deploy-to-balena-action#234 should fix it @klutchell cc @20k-ultra

I was about open an issue for this but I see @ab77 is all over it!

Give my TS is a bit lacking, if anyone can massage my "fix" to pass tests, that would be awesome!


catch and descriminate different exception types

This change catches the different exceptions types thrown by the C++ SDK
and throws a JS exception with the property type, which is the
discriminator, and the property exception, which is an actually
JavascriptError as one would expect.

@apaprocki, would appreciate your feedback if I should throw an Object or throw Error and tacking on the type property to determine the exception type.  I am open to other solutions to tackle this.

We discussed this in the office but to have it in writing: This change as written isn't backwards compatible. It could be if instead of wrapping the Error, it just gets augmented with the type property, but I'm not sure it's a great idea to add fields to the standard Error object.

Nit: "discriminate" in the commit summary.

Closing in favor of #40


Snapshot generation doesn't seem to be working correctly (first observed Mar 23)

Expected behavior

Snapshots should record updated changes consistently
If snapshots folder is deleted, running wtr --update-snapshots should generate a new folder with the snapshots in them

Actual Behavior

Snapshots are not updated consistently. Sometimes they only generate snapshots for a few test cases in a test suite but not all test casses
Sometimes new snapshot folder is not generated when running command even if it's deleted

Both me and my coworkers are able to reproduce this issue. Wondering if we are the only ones experiencing this issue or there's a newly introduced bug?
Additional context
We cannot share the source codes due to intellectual property rights. But snapshot generation used to be working and we first observed this issue on Mar 23. There were no changes made in between
Here are the related package versions we are currently using:
"@web/test-runner": "^0.15.1",
"@web/test-runner-chrome": "^0.11.0",
"@open-wc/semantic-dom-diff": "^0.19.7",
"@open-wc/testing": "^3.1.6"

We tried updating them all to the latest versions of the packages and that still did not fix the issue.
Thanks!

I've not encountered this while running thousands of VRTs a day. Could you share more about your usage?

It's worthwhile to mention that the tests still register as passed. But if we actually inspect the snapshots, they are not updated correctly and are often generated for only a few of all the test cases that have snapshots
The usage is standard Lit + Typescript starter, just adding snapshot testing:
import { expect, html, fixture, fixtureCleanup } from '@open-wc/testing';
import { spy } from 'sinon';
import './OurComponent';
import { OurComponent } from './OurComponent';

describe('OurComponent', () => {
    afterEach(fixtureCleanup);

    it('should render with default props', async () => {
        const component: OurComponent = await fixture(html`<our-component></our-component>`);
        expect(component).shadowDom.to.equalSnapshot();
    });
});


[LOC] - Link redirect to a non existing page

Link redirect to a non existing page.
Repro steps:

Go to https://docs.microsoft.com/en-us/sharepoint/dev/general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object
Search for "CanReply" click on the first hit

Actual result:
Link redirects a non existing page
Expected result:
Link redirects a existing page
GH article:
https://github.com/SharePoint/sp-dev-docs/blob/live/docs/general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object.md

Looks like this might be the updated URL -- https://msdn.microsoft.com/en-us/library/office/microsoft.sharepoint.client.social.socialthreadattributes.aspx
Happy to make a PR if you'd like


moment.toJSON() loses timezone information.

Description of the Issue and Steps to Reproduce:
The toJSON function for moment objects removes any timezone information from the object when formatting it. This means that moment objects can't easily be serialized to JSON while maintaining timezones.
var m = require('moment')
var time = m.parseZone("2018-09-10T19:18:00.000-07:00")
console.log(time.format())
// 2018-09-10T19:18:00-07:00
console.log(time.toJSON())
// 2018-09-11T02:18:00.000Z
console.log(JSON.stringify(time))
// "2018-09-11T02:18:00.000Z"

Currently working around this by overriding the toJSON function for all moment objects to simply call moment.format(). It seems like simply calling format() in the toJSON function might be the right solution. Although I'm not sure what the concerns around backwards compatibility are.

moment's implementation matches Date.prototype.toJSON.  I think that's probably the right thing to do.
You wouldn't really be preserving the 'timezone' using -07:00 notation; you'd just be preserving an offset.
I guess it depends on your use-case, but you can easily override the default implementation with:
moment.fn.toJSON = function() {
  return this.toISOString(true);
};

Fair enough on zone vs offset.
We are ok with overriding in this case but the inability to easily preserve offset information when serializing dates (moment or built in) seems like a potential pitfall for users. I certainly spent a few hours figuring it out. Perhaps solveable with documentation.


Allows user to specify additional Maven repositories for pax-exam tests.

Allows user to specify additional Maven repositories for pax-exam tests. This can be useful when running pax-exam tests against binaries which are not available in public Maven repositories.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

ok to test

+1 to merge (once the build succeeds)

+1, looks fine.

Test faillues not related to this PR.


Routing issue with ferries in Oslo

Routing along ferry routes in Oslo has some strange behaviour. Brouter routes me almost all the way from Oslo to Nesoddtangen along the most direct ferry route, but if I set my destination to Nesoddtangen I'm forced to take a different ferry and longer route.
There seems to be some hidden point along the shortest route where routing flops from one ferry route to the other. The ferry route at this point is continuous so the tags don't change, so it must be a routing issue.
I've checked the OpenStreetMap data and the whole ferry route is tagged with bicycle=yes.

I should have posted this to the backend. Closing here.


Minor Optimization in TypeHandlerRegistry#getTypeHandler

In case where the argument jdbcType is null. We can ignore calling jdbcHandlerMap.get(null) in case if handler is also null.
Previously we would have called jdbcHandlerMap.get twice (if jdbcType and handler was null)
Refactored code so that the above is easy to read.

Although this patch might help your particular problem, it could harm other use cases.
As I explained in the thread, the cause of the issue is excessive invocation of type handler lookup, so changing the lookup logic does not seem to be the right solution at this point.
Note: this PR is an attempt to solve the performance issue @purijatin is experiencing.


As a cluster member attempting to add a member to the cluster results in no error message just stuck in creating

Rancher Server Setup
Rancher version: v2.6.0-head on commit-id: 72986b2
Installation option (Docker install/Helm Chart): Helm Chart
If Helm Chart, Kubernetes Info:
Cluster Type (RKE1, RKE2, k3s, EKS, etc): RKE1
Information about the Cluster
Kubernetes version: v1.21.3-rc6+rke2r2
Cluster Type (Local/Downstream): RKE2 Digital Ocean Cluster
Describe the bug
With a cluster member, when attempting to add a member to the cluster, it gets stuck in the creating phase, with no error message ever returned.
This is the API response:
{baseType: "error", code: "Forbidden",…}
baseType: "error"
code: "Forbidden"
message: "clusterroletemplatebindings.management.cattle.io is forbidden: User \"u-jsrv7\" cannot create resource \"clusterroletemplatebindings\" in API group \"management.cattle.io\" in the namespace \"c-d4zkz\""
status: 403
type: "error"

To Reproduce

With an Admin user created a cluster (either RKE1 or RKE2)
Create a 2 standard users; user1 and user2
Add that the user1 as a cluster member for the aforementioned cluster.
Login as user1, and attempt to add user2 as a cluster member.

Result

UI gets stuck in the creating state and no error message is returned.

Expected Result
A failure with a descriptive error message, like in the API call. OR removed Add option for CLuster Members.

On Rancher v2.6-head version c10ef4b:

v2.6-head 1a57856 pulled 9/17/21 ~9:30am Pacific
@igomez06 I have a question about the steps mentioned to reproduce - I cannot reproduce this. It is not possible for a cluster member to add another cluster member as they do not have rights to modify the cluster.
Was there anything else you might have done during user1 creation? suer1 is just a standard user right? (that's it?)

No option to edit cluster (as expected) therefore not possible to add user2

hmm - or maybe I am confused? How did you add another user to the cluster as a cluster member?

My checks PASSED
Reproduction Steps:

Not required. The issue was filed by a peer and I understand the reproduction steps.

Validation Environment:

Rancher version: v2.6-head 1a57856 pulled 9/17/21 ~9:30am Pacific
Rancher cluster type: single-node docker install
Docker version: 20.10
Downstream cluster type: rke2 (could also be rke1, does not matter)
Downstream K8s version: v1.21.4+rke2r2
Validation steps:

With an Admin user create a cluster (RKE2 in my case, 1 node with DO provider but this does not matter)
Create a 2 standard users; user1 and user2
Add that the user1 as a cluster member for the aforementioned cluster.
Login as user1, and attempt to add user2 as a cluster member (do this by exploring the cluster and on the left pane, go to RBAC>Cluster Members)
The backend will respond with a 403 error (as expected) but now the UI will keep us on the form and show an error message in the UI. Therefore this now works correctly and the issue is resolved.

Additional Info:

You cannot as a cluster member edit the cluster to add a member, but you can see this in the UI under the cluster explorer - why? If the user is not authorized I would expect to see this hidden in the UI -- but I think this is because they might be able to add custom roles of some kind if their user had the correct rights.


AutocompleteManager.deprecateForSuggestion is deprecated.

Autocomplete provider 'ClassProvider(undefined)'
returns suggestions with a prefix attribute.
The prefix attribute is now replacementPrefix and is optional.
See https://github.com/atom/autocomplete-plus/wiki/Provider-API
AutocompleteManager.deprecateForSuggestion (<embedded>:40436:20)
<unknown> (<embedded>:40293:44)

I am having the same issue...

Same here

No update???

Same issue when adding 'use' statement deprecation cop pops up with following warning
Autocomplete provider 'ClassProvider(undefined)' returns suggestions with a prefix attribute. The prefix attribute is now replacementPrefix and is optional. See https://github.com/atom/autocomplete-plus/wiki/Provider-API

Atom    : 1.26.1
Electron: 1.7.11
Chrome  : 58.0.3029.110
Node    : 7.9.0


Firefox takes 30+ seconds to start if networking.hostName is not in DNS resolution

Issue description
I believe this started happening with Firefox 60.0+. If networking.hostName in configuration.nix is set to a nonexistent name, firefox seems to try and resolve the hostname for 30 seconds before starting up. I have no addons or plugins installed.
I found a workaround, where if I add the following to configuration.nix (replacing "yellowhat" with whatever networking.hostName has been set to), will fix the problem:
networking.extraHosts = ''
<IP_ADDRESS>   yellowhat
'';
Not sure what the fix should be. Maybe the networking.hostName should be automatically added to /etc/hosts?
Steps to reproduce
Set networking.hostName in configuration.nix to a unresolveable hostname.
Start firefox
Technical details
I figured this out by running strace against firefox and getting:
connect(7, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("<IP_ADDRESS>")}, 16) = 0
poll([{fd=7, events=POLLOUT}], 1, 0)    = 1 ([{fd=7, revents=POLLOUT}])
sendto(7, "\232m\1\0\0\1\0\0\0\0\0\1\tyellowhat\0\0\1\0\1\0\0)\4\260"..., 38, MSG_NOSIGNAL, NULL, 0) = 38
poll([{fd=7, events=POLLIN}], 1, 5000)  = 0 (Timeout)
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 8
connect(8, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("<IP_ADDRESS>")}, 16) = 0
poll([{fd=8, events=POLLOUT}], 1, 0)    = 1 ([{fd=8, revents=POLLOUT}])
sendto(8, "\232m\1\0\0\1\0\0\0\0\0\1\tyellowhat\0\0\1\0\1\0\0)\4\260"..., 38, MSG_NOSIGNAL, NULL, 0) = 38
poll([{fd=8, events=POLLIN}], 1, 5000)  = 0 (Timeout)
poll([{fd=7, events=POLLOUT}], 1, 0)    = 1 ([{fd=7, revents=POLLOUT}])
sendto(7, "\232m\1\0\0\1\0\0\0\0\0\1\tyellowhat\0\0\1\0\1\0\0)\4\260"..., 38, MSG_NOSIGNAL, NULL, 0) = 38
poll([{fd=7, events=POLLIN}], 1, 5000)  = 0 (Timeout)
poll([{fd=8, events=POLLOUT}], 1, 0)    = 1 ([{fd=8, revents=POLLOUT}])
sendto(8, "\232m\1\0\0\1\0\0\0\0\0\1\tyellowhat\0\0\1\0\1\0\0)\4\260"..., 38, MSG_NOSIGNAL, NULL, 0) = 38
<IP_ADDRESS> is my dns entry in /etc/resolv.conf and "yellowhat" is my chosen hostname
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.
[tim@yellowhat:~]$ nix-shell -p nix-info --run "nix-info -m"

system: "x86_64-linux"
host os: Linux 4.14.63, NixOS, 18.09pre149415.8395f9aa85e (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.0.4
channels(tim): "nixpkgs-18.09pre149415.8395f9aa85e"
channels(root): "nixos-18.09pre149415.8395f9aa85e"
nixpkgs: /home/tim/.nix-defexpr/channels/nixpkgs

I have the same issue with mutt.

Should be solved by #47241.

I believe this was solved by #47241.


In hello-aaudio initial underruns should be ignored

hello-aaudio has some latency tuning code which increases the buffer size if an underrun occurs. This is fine for normal use but sometimes when a stream is started a few underruns occur within the first few dataCallback calls. These underruns occur as part of the normal stream startup and should be ignored, rather than influencing the buffer size.

This sample has been deprecated/archived (check README for more information on newer samples related to this technology).
As recommended by GitHub, we are closing all issues and pull requests.


Creation of Duplicate folders in Artifacts

Whenever I upload any CSAR and download it after some changes, duplicate folders are created inside all the components in artifacts.
For eg.
/artifacttemplates/http%3A%2F%2Fopentosca.org%2Fartifacttemplates/Container_DA/files/artifacttemplates/http%3A%2F%2Fopentosca.org%2Fartifacttemplates/Container_DA/files/
I have tried downloading CSAR from Topology template or Service template.
Browser: Chrome Version 65.0.3325.181
OS: Ubuntu 16.04 LTS

@SainiNidhi Thank you for the report! You would help us diving into the issue if you wrote some import/export tests as asked for at https://github.com/eclipse/winery/pull/265#issuecomment-395400048.

Hello, is there any update for this issue. I recently checked it, there are still duplicate folders creating.

@SainiNidhi could you provide us with more context? which branch are you working on, have you tried it with one particular csar or any csar gives you the same result, etc?
also, it would be nice if you describe the steps needed to reproduce this problem, e.g.,
step1: export csar,
step2: ...

Seems no longer relevant.


Handle variable restart, variable redocking, paging in data

For #4492, #4485

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[x] Has a news entry file (remember to thank yourself!).
[x] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

This fixes a number of issues with the variable view, ran into them while fixing the kernel restart issue.
Not happy with my original work. That work used execution count basically just as an increasing number on the variable view. Which works reasonably well for a single file, but not for multiple files or handling restart. Now I'm tracking the current execution count of open documents, and passing that to the variable view when we switch documents. This way if you have document A on execution count 3, then you swap to document B on execution count 5 it will correctly fetch variables with execution count 5. Previously it would use execution count 3 (unless you actually executed a cell on document B).

This fixes a number of issues with the variable view, ran into them while fixing the kernel restart issue.
Not happy with my original work. That work used execution count basically just as an increasing number on the variable view. Which works reasonably well for a single file, but not for multiple files or handling restart. Now I'm tracking the current execution count of open documents, and passing that to the variable view when we switch documents. This way if you have document A on execution count 3, then you swap to document B on execution count 5 it will correctly fetch variables with execution count 5. Previously it would use execution count 3 (unless you actually executed a cell on document B).

A note on tests. This change here is (in my opinion) the last current experiment blocking change on the variable view. I'm rushing this out a bit since tests were blocked on the CI xvfb issue. After this PR I'm going to go back and prioritize that test issue and no new features until the basic tests are working CI. I don't like working like this, but given that I'm not sure what the CI issue is this at least gets us in better state for the experiment / demos.

A note on tests. This change here is (in my opinion) the last current experiment blocking change on the variable view. I'm rushing this out a bit since tests were blocked on the CI xvfb issue. After this PR I'm going to go back and prioritize that test issue and no new features until the basic tests are working CI. I don't like working like this, but given that I'm not sure what the CI issue is this at least gets us in better state for the experiment / demos.


Require psr/simple-cache and have NullCache implement it

PR for issue 3 as discussed.

@dannyvankooten Did you have a chance to look at this? It would be nice to move on with it :)

Not yet, but did now. Looks perfect, thanks a ton @Jarlskov!

Cool, thanks :)


[SPARK-36664][CORE] Log time waiting for cluster resources

What changes were proposed in this pull request?
Keep track of and communicate to the listener bus how long we are waiting for execs to be allocated from the underlying cluster manager.
Replaces WIP PR https://github.com/apache/spark/pull/34650
Why are the changes needed?
Sometimes the cluster manager may choke or otherwise not be able to allocate resources and we don't have a good way of detecting this situation making it difficult for the user to debug and tell apart from Spark not scaling up correctly.
Does this PR introduce any user-facing change?
New field in the listener bus message for when a executor is allocated.
How was this patch tested?
New unit test in the listener suite.

Hey @mridulm & @attilapiros any cycles for this?

Going to close / re-open a separate one since GHA is being weird.


participant's name is hard to read on white background

it's almost impossible to read the participant's name when the webcam's background is white on the bottom left corner.

Please help me little bit and propose howto adjust. This is the part of the actual code css:
https://github.com/edumeet/edumeet/blob/befb3df1448e52ab73bc1f8b00bd568d6b1ef67b/app/src/components/VideoContainers/VideoView.js#L148
We use material ui theme settimgs, so you can make in theory own theme and css adjustment/modification from config: https://github.com/edumeet/edumeet/blob/befb3df1448e52ab73bc1f8b00bd568d6b1ef67b/app/public/config/config.example.js#L171

probably a small css adjustment - semi transparent bg - would solve the issue, something like this:
background-color: #0000007d;

probably a small css adjustment - semi transparent bg - would solve the issue, something like this:
background-color: #0000007d;

@misi I think the proposed background "fix" should be added as a standard display of participant's name. It's looks better and it's more legible than the current style. Should I add it to develop branch?

@misi I think the proposed background "fix" should be added as a standard display of participant's name. It's looks better and it's more legible than the current style. Should I add it to develop branch?

Yes thanks!

Yes thanks!

@nullaegy The fix has been added to a develop branch. Please check. If everything is ok please close the issue. Thanks.

@nullaegy The fix has been added to a develop branch. Please check. If everything is ok please close the issue. Thanks.

LGTM

LGTM

Thank you!

Thank you!


New staking reward system

Objectives:

Staking roles (ledger, etc.) to be entirely decoupled from reward-related logic.
(probably not worth it) Rewards to be mire customizable on a per-nominator basis. e.g. one nominator not being paid out automatically.
Rewards to be scalable: they should be payable in smaller chunks. probably requires multi-page exposure table.
Once we have 3, it should be very simple to actually make rewards automatic. Even better, automatic for those who want it to be.

Some this might require us to make things seemingly less efficient, but if we do it multi-page, it will actually be more scalable.

related: #6641 #10941

I'll remark that availability and approval reward points flowing into the validator end up kinda nuanced, but they still have a (era,point) resolution in the end.  https://hackmd.io/@rgbPIkIdTwSICPuAq67Jbw/rkTzZX_8t

I am tackling point 1 and 3 of the issue in the PR https://github.com/paritytech/substrate/pull/13498.
Since the reward would be distributed in multiple pages, one of the objectives of this PR is to incentivise a validator to pay out all pages of the reward. My current approach is to distribute commission of the validator across pages proportional to the total stake of the page.
I had couple of great suggestions for improvement and I wanted to get some opinion from @kianenigma and @burdges as well on this before making changes.
Suggestion 1 (@gpestana):
Instead of commission proportional to page stake, it can be evenly distributed across all pages irrespective of page stake. We can extend this even further and pay the validator stake also evenly across pages. (Right now validator stake is paid out in 1st page).
Suggestion 2 (@rossbulat) :
We can reverse the order of rewards payout, so that the page with lowest stake is paid out first and the highest stake is paid out only at last incentivising validators to pay out all pages. There is still an option though to pay out a page explicitly instead of pallet choosing the order automatically.
I am leaning towards doing the Suggestion 1 which would make Suggestion 2 not needed. What do you guys think?

I think all of these suggestions are coming the perspective of protecting small nominators who are in the lesser pages from not receiving their rewards. This is fair concern, but I would generally avoid designing systems too much with such a mindset in mind. The goal of the game theory involved in FRAME or blockchains is not necessarily to protect everyone at any cost, but rather be a system that is sound, sustainable, or foremost unstoppable.
I think if we are to solely make decisions from this perspective, then the existing model makes perfect sense; if the total stake in a page is so small that no one has an incentive to claim it, then it should not be claimed (recall that anyone can do the claims, not just the validator).
That all being said, I won't resist against tweaking this system such that we slightly protect nominators, in which case I like option 1 way better. It doesn't 100% solve the issue, but it will drastically reduce the chances of a page being left unpaid.


fix(ingest/ldap): set user urn to  firstname.lastname

If we specify user_attrs_map["urn"]: "mail" in ldap source ingestion yaml  then the user created is "firstname.lastname@domain".
In the frontend settings if we specify "AUTH_OIDC_USER_NAME_CLAIM_REGEX=([^@]+)" then the user created is "firstname.lastname"
This fix will prevent duplication of users created by frontend and ldap ingestion.
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Hi @abiwill !
Thanks for the contribution. It appears that we can continue to improve the PR by adding a configuration option to apply a regex to the field which is used in generating the URN (similar to what we do in OIDC using the AUTH_OIDC_USER_NAME_CLAIM_REGEX config).
Would you be able to extend this PR to support such a configuration option?
Cheers
John

Hi @abiwill !
Thanks for the contribution. It appears that we can continue to improve the PR by adding a configuration option to apply a regex to the field which is used in generating the URN (similar to what we do in OIDC using the AUTH_OIDC_USER_NAME_CLAIM_REGEX config).
Would you be able to extend this PR to support such a configuration option?
Cheers John

Sure.
Let me try it.

@abiwill have you gotten a chance to look into this one?

@abiwill I've closed this PR for now, but feel free to ping if you'd like to keep working on it


Account controlled by the private key

completed in https://github.com/rooch-network/rooch/pull/50


PacketDumpFile to support streams?

Hi!
Would it be possible to add support for reading a stream as well as reading a file with the PacketDumpFile class? Or maybe add a PacketDumpStream class?
I have PCap files that aren't stored as file but (for example) as a blob in a database / NOSQL store. I can access the data as stream and would like to use Pcap.Net to handle the parsing of the PCap data.

EDIT:
Maybe a StreamPacketDevice would be the better route to go? That could be inherited from the PacketDevice baseclass...

I'm not sure this would work with WinPcap as the methods around these are wrapper methods around WinPcap functions.


No events from the time synchronization using MAC sync

LoRa Basics Modem version: 3.1.7
In my project, we have integrated this stack and are currently producing products. While updating a new feature that involves time synchronization, I encountered the following issue:
When I call the function smtc_modem_time_start_sync_service(STACK_ID, SMTC_MODEM_TIME_MAC_SYNC);, there is no callback triggered with current_event.event_type == SMTC_MODEM_EVENT_TIME. Additionally, setting a small interval using the smtc_modem_time_set_sync_interval_s function does not seem to have any effect.
Although I can receive the correct time when polling with the smtc_modem_get_time function, no callbacks are triggered when a synchronization exchange has occurred.
I was wondering if you can help us fix this issue.

@matthieuantoine this is the same as emailed you before. Can you reproduce the problem?

Hi @RobTWTG @martinichka ,
We have not seen this issue at our side during our v3.1.7 validation.
Do you have any modem traces that can show what happened after the start of the time sync service?
Regarding the change of the interval between sync, could you please call the function just before starting the time sync service so that it can be taken in count directly and not after next synchronization event (36h).
If possible in your development environment/project could you please try the v3.2.4 version of the library to see if it can solve your issue (we have modify a bit this service between this 2 releases)?
Let me know if it helps
Audrey from lbm-team

While setting up the firmware to get modem traces, I found out this was an issue on our side by calling the lr1mac_core_init function an extra time. This function resets the device_time_callback and context back to NULL pointers.
Thank you for the reply, I will close the issue.


AlwaysSucceeds spending example

Right now I'm unable to debug it but I guess this still lacks a constraint about the payment to the wallet owner unless the balancing solves it by itself.  Anyway, I would delay it until I can debug/test the example.

It seems that the problem with the test address is solved now, so I can verify it now.

Right now I can't test it as Ogmios return an empty list of utxos in my wallet.
ogmios_1              | {"severity":"Info","timestamp":"2022-05-30T19:57:24.141529599Z","thread":"479","message":{"WebSocket":{"contents":{"era":"Alonzo","tag":"StateQueryRequest","query":{"utxo":["addr_test1qzf7urzwfexnpqakjl0p9ejupr07jcxt4r6r8txfgkpg85wyuwa620klsgupl7l0lthlx22uv08thdztnsw8s25p33nsapwugn"]},"point":null},"tag":"WebSocketStateQuery"}},"version":"v5.2.0"}
ogmios_1              | {"severity":"Info","timestamp":"2022-05-30T19:57:24.660287229Z","thread":"479","message":{"WebSocket":{"contents":{"tag":"StateQueryResponse","result":[]},"tag":"WebSocketStateQuery"}},"version":"v5.2.0"}

But the example has been working before.

I can test it again (thanks for the help with that). All seems to be ok, so unless we have more refactors to do, this pr is ready.


Generate docs for orphan instances

Attempt to resolve https://github.com/haskell/haddock/issues/297

From binary-orphans documentation:

I'll fix the tests if the solution is otherwise ok.

This looks fantastic. I've merged it to ghc-head which should soon get merged into master.


Visulization routine: Saving plot to file optional

So far the plot is always saved to a file

@MerktSimon this is obsolete now, right?

All plotting functions now return Axis objects, so users can choose if they want to save or show.
Hence, yes, this is obsolete now.