Refactor Bucket Controller and Add Bucket Provider Interface

If applied, this PR will refactor the Bucket Controller and add a Bucket Provider Interface that can be implemented by any bucket provider added for the bucket controller. This refactor is as a result of comment in PR https://github.com/fluxcd/source-controller/pull/434#issuecomment-934614045

Hey @squaremo I'm almost done making the changes. We can for sure collaborate on this pull request. I will push my most recent changes and fixes to my branch in a few hours. You can for sure make a pull request to my fork.

Hey @squaremo I have just finished the requested changes. Please let me know if there is anything else I need to change and I will be glad to refactor it 🙂.

@pa250194 I've made a PR to your PR, which does a bit more shifting code around. See what you think!
In the meantime, there's some tests which fail both in CI and on my laptop, which are worth looking into. (I'm away for the next couple of weeks, just to let you know.)

Hey @squaremo sorry for the late response. I am currently occupied by a high priority sprint be will look at the PR and the tests that fail soon. I appreciate the help and contribution to my PR 🙂.

Hi! I'm back from holidays. With respect to the client tests: I think it would be reasonable to verify only that the wrappers respond to their altered API correctly assuming that the underlying client libraries work. That way you don't have to use the real services or mock them -- you can just provide a fake client. I'll work on that for the GCP client.

Although ... the fake service that's there works OK, and it looks like the problem is mainly that the test that fails (https://github.com/fluxcd/source-controller/runs/4543207347?check_suite_focus=true#step:9:952) just needs to be running in GCP or have an environment variable set. The test itself is just checking that the branch at https://github.com/fluxcd/source-controller/blob/83431e26c14094380e8519e5480e5f736ae3b016/pkg/gcp/gcp.go#L65 is taken when there's no secret.
The expedient thing to do may be to come up with a different way to test if the client creation logic works 🤔 ...

(I rebased to remove the merge commits)

I will take a look at the test and push a fix for it as I see this is blocking another PR.

To expand on my comment earlier: I had a look at faking the GCP storage client and it is .. complicated. Mainly because there's a couple of layers of methods that return structs with their own methods, all of which need to be represented as interfaces. So it would be possible, but verbose.
If there's a way to test that the construction logic does what it's supposed to (ideally without requiring an external service and credentials), the rest is covered with the fake service. I assume that faking the authentication service is a lot of trouble. One way might be to supply a factory interface to the construction logic, and verify that it's called in the correct way. I'm sure there are other ways.

I will take a look at the test and push a fix for it as I see this is blocking another PR.

To expand on my comment earlier: I had a look at faking the GCP storage client and it is .. complicated. Mainly because there's a couple of layers of methods that return structs with their own methods, all of which need to be represented as interfaces. So it would be possible, but verbose.
If there's a way to test that the construction logic does what it's supposed to (ideally without requiring an external service and credentials), the rest is covered with the fake service. I assume that faking the authentication service is a lot of trouble. One way might be to supply a factory interface to the construction logic, and verify that it's called in the correct way. I'm sure there are other ways.

I agree faking the GCP client is complicated. I was thinking that because all line 65 - 71 does is use the GCP client. https://github.com/fluxcd/source-controller/blob/83431e26c14094380e8519e5480e5f736ae3b016/pkg/gcp/gcp.go#L65
We could probably implement that test in a new PR so we are not blocking the other PR.
In the gcp_test.go line 173 is the test that is failing because it is trying to use the gcp client to authenticate using the GOOGLE_APPLICATION_CREDENTIALS env variable. So I will remove that test and we could implement the test with a fix in another PR.
https://github.com/fluxcd/source-controller/blob/83431e26c14094380e8519e5480e5f736ae3b016/pkg/gcp/gcp_test.go#L173
if that sounds good with you, I can make a push with the changes.

We could probably implement that test in a new PR so we are not blocking the other PR.

Yes, I think it's reasonable to defer tests for the construction logic for the minute; the code under test is pretty self-evident (if there's a secret, use that, otherwise let the client do whatever it does ...).

Hi @squaremo can I get some guidance on how to get the DCO check to pass

You'll need to edit the commits that don't have a sign-off (they are listed on the details page for the DCO check). A fairly easy way to do this is with git rebase --interactive, since that will give you the chance to go back through all the commit in one go.
git rebase -i main

will bring up an editor with a list of commits since branching from main. Find those you need to add your sign-off to, and put an edit in the first column. That means git will stop at that commit and let you amend it.
To add your sign-off to a commit, you can do
git commit --amend -s

Then you can do
git rebase --continue

to keep going through the commits in the list. If you lose track of where you are, git status will tell you where you are up to; and, you can abandon the rebase (e.g., to start again) with git rebase --abort, which will take you back to the state before you started.
Once you've finished, check git history to see if it looks right, and git push --force-with-lease to push your rebased branch up to github. It can all be reverted, so do not worry about losing work.

You can fix the merge conflict at the same time, if you pull from upstream main branch first then use that as the rebase.

I think I may have messed up the rebase 🤦🏽♂ @squaremo

I think I may have messed up the rebase 🤦🏽♂ @squaremo

Don't worry -- rebasing takes a lot of practice and it's easy to lose your place, or misstep. It often takes me a few of attempts to get a rebase right.
I've put things back in order here. This is what I did:

I squashed your original commits (refactor to introduce the interface, use error groups, 2 x fix tests) into one commit, without changing the branching point. They are all one change anyway, just with a few fixups. Squashing them first made it easier to rebase onto another branch, because it avoided the situation in which I have to fix a conflict in one commit, only to revisit it when the same lines are changed later. (It also removed some commit objects that needed sign-off, fixing the DCO check)
I rebased the newly rewritten branch on origin/main, to fix the "conflicts with main branch detected" message that was above.
I did git push --force-with-lease to your PR branch.

I think I may have messed up the rebase 🤦🏽♂ @squaremo

Don't worry -- rebasing takes a lot of practice and it's easy to lose your place, or misstep. It often takes me a few attempts to get a rebase right.
I've put things back in order here. This is what I did:

I squashed your original commits (refactor to introduce the interface, use error groups, 2 x fix tests) into one commit, without changing the branching point. They are all one change anyway, just with a few fixups. Squashing them first made it easier to rebase onto another branch, because it avoided the situation in which I have to fix a conflict in one commit, only to revisit it when the same lines are changed later. (It also removed some commit objects that needed sign-off, fixing the DCO check)
I rebased the newly rewritten branch on origin/main, to fix the "conflicts with main branch detected" message that was above.
I did git push --force-with-lease to your PR branch.

Thank you so much for taking out time to explain the steps to me 🙂

Sorry about the wait, I'll be picking this up now to fit it into the recent (rigorous) changes in main.

As due to the various conflicts I had to fiddle around with the order and state of commits, which I did not want to get lost (historically) here, this is superseded by #596.


Completely overhaul the website

This PR introduces a complete overhaul of the current website. The new website will be generated by Jekyll (fixes #29) and makes heavily use of Bootstrap 5. The theme is based on the business-frontpage template by sharu725 published under the MIT-License.
The website will behave responsive and introduces a navigation button on mobile devices (fixes #103 and fixes #94). Most of the content is either pulled from the YAML files located under _data or the markup documents located under _pages. Have a look at the README.md on how to maintain this website.
The build process is done by an Github Action which subsequently syncs the generated website to an existing webspace via rsync.

Important! We first need to prepare the webserver and adapt the Github action .github/workflows/build-and-deploy.yml before merging this PR.


Bugfix/maintain order of command retries

Contributions: We are not currently taking public contributions - see our contributions policy. However, we are accepting issues and we do want your feedback.

UNR-760
Description
Problem: Retried ReliableRPCs were being retried in the reverse order.
Symptom: HUD was not being displayed.
Explanation:  On startup UPlayerController sends the following RPCs in the following order:
ClientSetHUD
ClientVoiceHandshakeComplete
ClientEnableNetworkVoice
ClientUpdateMultipleLevelsStreamingStatus
ClientFlushLevelStreaming
ClientCapBandwidth
ClientSetSpectatorCamera
ClientSetCameraMode
ClientSetRotation
ClientGameStarted
If Spatial fails these commands for whatever reason, they were being returned, queued up in FTimerManager to be replayed.
FTimerManager was then executing them in the reverse order, resulting in ClientGameStarted being executed before ClientSetHUD, meaning the HUD never got told that the game had started, and thus never displayed itself.
The fix included here, is to push all RPCs to be replayed per frame into a stack, thus reversing the order when they are popped and sent, thus restoring the original ordering of RPCs.
Tests
Connecting Shooter game very shortly after starting shooter game is the most reliable way of causing the initial ReliableRPCs sent to UPlayerController to fail. When this happened, and they were replayed in  reverse order, the match was started before the HUD was created, resulting in the HUD not being shown.
With this change, the same startup method is deployed, examining logs to confirm the RPCs still failed, but they get replayed in the correct order, and the HUD displays correctly.
Documentation
In-code documentation explaining the reasoning
Primary reviewers
@danielimprobable  @m-samiec

I want to know if ClientSetHUD fail for some reason, but the ClientGameStarted command is success, how can GDK keep those reliable rpc ordered?

@scutjames In this instance the rpcs won't be ordered, but it's worth noting that this is unlikely as bulk rpcs will usually all pass or timeout for the same reason. Even so, we understand the potential for problems here and are investigating ways of ensuring all reliable rpcs are ordered correctly.


Enable more framework versions

Add .NET Standard 2.1 and .NET 5 to package
Run tests against all .NET frameworks for enhanced validation

Not really sure how I came across your repo, but I did and I thought I'd throw this your way.  Happy to have it rejected, just thought it might be useful.  Have a good one!


How it works, and process to identify and troubleshoot

Hi,
Put a larger project against grunt-uncss and I'm finding it leans it out too much.  All the injected animation CSS classes are toast, and much of the stuff I thought PhantomJS was supposed to pluck out.
Is there a flow of how this project processes HTML, JS and CSS or any more rich logging options so its more apparent what its doing after you type 'grunt' in the CLI?  Its hard to identify if a CDN link to a javascript file just ends its JS search or if its even looking at all the JS present in the project.
Example: it seems like the project needs absolute paths to the files <script src="/...
That clears some reference errors, but I might not want relative paths on my project.
I think adding options, htmlroot "/" might solve this?
Bulk of my issue however seems to be PhantomJS not catching styles that are being used and I'm not certain of there is something to enable/troubleshoot that.
So .collapse.in {...} for example with bootstrap is getting wiped out as well as .collapsing {...}

This is an upstream issue; you should ask in the uncss repository.


Android video flipped rotated

Steps to reproduce

code

<Camera
          ref={(cam) => {
            this.camera = cam;
          }}
          style={styles.preview}
          captureTarget={Camera.constants.CaptureTarget.disk}
          captureMode={Camera.constants.CaptureMode.video}
          captureQuality={Camera.constants.CaptureQuality.medium}
          type={Camera.constants.Type.front}
          orientation={Camera.constants.Orientation.portrait}
          aspect={Camera.constants.Aspect.fill}>

        </Camera>

2
Expected behaviour
This code creates video flipped for 180degrees when watching after saving
Tried to use PortraitUpsideDown - both types and even auto making flipped video
Actual behaviour
Video should be simply made without any rotation effects
Environment

Node.js version: 6.2.2
React Native version: 32.0-rc.0
React Native platform + platform version: Android 6.0 / LG Nexus 5

react-native-camera
"react-native-camera": "git+https://github.com/lwansbrough/react-native-camera.git",

Tested with back camera - works well,
Front camera issue only

guess it refers to you @marcejohnson  :)

Hi @kLkA thanks for the report.  A few things to check:

Does this behavior occur when you try the example test program provided here:  https://github.com/lwansbrough/react-native-camera/tree/master/Example
Are you seeing this on different Android phone models?   (Folks have seen camera sensor differences per platform).
The community addressed Nexus 5 flipped video here:  https://github.com/lwansbrough/react-native-camera/pull/262#issuecomment-239622268 .  That thread is closed (so no need to post there), but wondering if there something different about your setup or usage?

Thanks again for reporting and investigating.

@marcejohnson I checked #262 issue but didnt find this kind of code in latest version of camera while i installed it yesterday. Could you tell me how to check if this code exists in my version of npm module?

This is the commit from @jiw0220 and @markomatic that addressed Nexus 5 orientation:
https://github.com/lwansbrough/react-native-camera/pull/262/commits/d2a6209f31dc862a9d4269f4198116c6a05d733a
It was merged into latest.  Does reversing this commit work better for you?

Probably nobody tested front camera video recording. As @kLkA noted, this is front camera issue only.

Interesting.... looks like in commit https://github.com/lwansbrough/react-native-camera/pull/262/commits/d2a6209f31dc862a9d4269f4198116c6a05d733a the following code was removed, which specifically adjusted for front camera.  Any idea why this was requested removed?  Did this cause problems?
int mediaRecorderHintOrientation = (90 + ((720 -    RCTCamera.getInstance().getActualDeviceOrientation() * 90))) % 360;
// adjust for differences in how devices display front facing http://www.theverge.com/2015/11/9/9696774/google-nexus-5x-upside-down-camera
if (RCT_CAMERA_TYPE_FRONT == options.getInt("type")) {
    if ((RCT_CAMERA_ORIENTATION_PORTRAIT == RCTCamera.getInstance().getOrientation()) && (RCTCamera.getInstance().getAdjustedDeviceOrientation() == 90)) {
         mediaRecorderHintOrientation += 180;
    }
}

@kLkA if you add the above code back into RCTCameraModule.java, is your issue resolved?  You can see in https://github.com/lwansbrough/react-native-camera/pull/262/commits/d2a6209f31dc862a9d4269f4198116c6a05d733a where to place it.

For me issue is present even with old code. @kLkA, did you tested it? Reason for removal is in comment https://github.com/lwansbrough/react-native-camera/pull/262#issuecomment-239622268

As noted here https://developer.android.com/reference/android/media/MediaRecorder.html#setOrientationHint(int) this method will not trigger the source video frame to rotate during video recording! That means that video will not be properly rotated on some players. Is there any way to actually rotate camera? Should we use some code from image capture, as I see, a lot of probably usable code from image capturing is eliminated in video recording with return statement https://github.com/lwansbrough/react-native-camera/blob/master/android/src/main/java/com/lwansbrough/RCTCamera/RCTCameraModule.java#L423

Hey, added code to the java file and video captured with proper orientation.
Whats the plan so ? integrate it back or wait for new solution?

Integrate it back for now if it works for you.

hey @kLkA check out how @dojiboy9 addressed rotation on front camera here:  https://github.com/marcejohnson/react-native-camera/pull/7
Does this work for you or is this a similar to the approach you took?  Thanks @markomatic, @kLkA, @dojiboy9 for testing across devices.

@marcejohnson happy to help.
@klkA Regarding my pull request, I think this commit is the relevant one: https://github.com/marcejohnson/react-native-camera/commit/1455e974fef37de8211949193fa3c32c376c31fc

Hey everyone. Right. commit from @dojiboy9 solving this issue very well.
Thank you all guys!

Awesome!
Thanks @corbt for creating a pull request containing @dojiboy9's fix already:  https://github.com/lwansbrough/react-native-camera/pull/393

Whoops, didn't realize that @dojiboy9 had already looked into this! Better tracking of the issues could have saved me several hours of debugging today. :P
Looks like that PR includes some new handling for onPause as well, which should also get merged.


Fix failing test

TestNodePointerDetail test_returns_private_node_pointer_detail_logged_out is failing for, as near as I can tell, no good reason. This needs to be fixed. It's really hard to get to this endpoint for anything useful, and you'll only get a node id and project name, but it's still not proper. Everything seems to be going through the proper channels, but for some reason DRF is not raising the exception it is raising.

So apparently I was never calling the check permissions method in this view.

@abought a9dd7dbf8113b8540f3eb9141d64356a7ed11c1f


how hard it should be to change it to support ethereum?

how hard it should be to change it to support ethereum?

That would be a total rewrite. Cardano, like Bitcoin, uses the UTx0 model. Ethereum uses an account-based model.

Some of the cryptographic code could be reused but there are no plans to support Ethereum.


add unit slots to data and measures

both the datasets used for training/evaluation as well as performance metrics measured for the model can use unit slots.

done
https://github.com/bridge2ai/model-card-schema/commit/65f06257c8d364768b1e866d75ca2718424718c0


test: enable integration tests against real S3

Feature Request
Integration based on AbstractS3Test are assuming http://localhost:9000 (provided by minio) as endpoint. It would be nice if we can run integration tests against real S3 endpoint based on test time configuration.
Which Areas Would Be Affected?
test, S3
Why Is the Feature Desired?
bugs related to specific S3 settings/regions could be found by running tests against real S3.
Solution Proposal
switching endpoint URI based on the environment variables.
Type of Issue
improvement
Checklist

[x] assigned appropriate label?
[x] Do NOT select a milestone or an assignee!

We've asked our friends at AWS to do this but have not had much traction.

I submitted PR #1951 for running tests against S3 using my own AWS credential from my local environment.


Build issue on iOS

Using react-native 0.63.4
Any idea how to fix it? Perhaps it’s related to the fact my project does not use Flipper?

Perhaps it’s due to the fact my pod file includes use_frameworks!?

Are you using Apple Silicone (M1 chip)? Can you build the example app?

Ahmmm, yes, I use the Apple Silicone (M1 chip), can this be related?

hey guys @oferRounds @mrousavy
I started getting this error when I turned hermes engine off in Pods.

And also, I couldn't make the project run when I was using use_frameworks! and hermes engine on. Some libraries, like @react-native-community/netinfo and react-native-fbsdk-next, couldn't import hermes.h and something like that. If anybody knows why it happens could you share an explanation? 😅

Hi @kanzitelli, thanks for this! I actually still on react-native 0.63, so hermes is not available for me
But as you said, it seems to me that the use_frameworks! is the one causing the issues

@oferRounds yes, unfortunately. I could only make my project run by removing react-native-mmkv and using regular AsyncStorage :(
as I understand, react-native-mmkv is based on JSI which is getting broken after using use_framework!. Also it was breaking some Pods which had s.dependency 'React' in .podspec file. But it has to be s.dependency 'React-Core'.

@brod-ie nice! Thank you! Will try

@oferRounds Even simpler! Updated my comment 😀

OMG thank you!!! Will soon check and update

Let me know if v2.0.0 still has that error :)

There is a simpler fix which does not require installing a plugin:
  pre_install do |installer|
    installer.pod_targets.each do |pod|
      if pod.name.eql?('react-native-mmkv')
        def pod.build_type;
          Pod::BuildType.static_library
        end
      end
    end
  end

Put this in the block defining the pod somewhere under the use_frameworks! call.

There is a simpler fix which does not require installing a plugin:
  pre_install do |installer|
    installer.pod_targets.each do |pod|
      if pod.name.eql?('react-native-mmkv')
        def pod.build_type;
          Pod::BuildType.static_library
        end
      end
    end
  end

Put this in the block defining the pod somewhere under the use_frameworks! call.

exactly where should I put those codes..? still getting build error
$RNFirebaseAsStaticFramework = true

require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

platform :ios, '11.0'

target 'fondee' do
  use_frameworks!
  config = use_native_modules!

  use_react_native!(
    :path => config[:reactNativePath],
    # to enable hermes on iOS, change `false` to `true` and then install pods
    :hermes_enabled => false
  )

  target 'fondeeTests' do
    use_frameworks!
    inherit! :complete
    # Pods for testing
  end

  # Enables Flipper.
  #
  # Note that if you have use_frameworks! enabled, Flipper will not work and
  # you should disable the next line.
  # use_flipper!()

  post_install do |installer|
    react_native_post_install(installer)
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end

  permissions_path = '../node_modules/react-native-permissions/ios'
  pod 'Permission-Camera', :path => "#{permissions_path}/Camera"
  pod 'Permission-PhotoLibrary', :path => "#{permissions_path}/PhotoLibrary"
  pod 'Permission-Microphone', :path => "#{permissions_path}/Microphone"
  # pod 'Permission-Notifications', :path => "#{permissions_path}/Notifications"

end


Update tutorial-web-application-keyvault.md

@naivelogic : Thanks for your contribution! The author, @barclayn, has been notified to review your proposed change.

@naivelogic Thank you for pointing this out. I just approved the changes you proposed.


Bluetooth: controller: Fix scan request when advertising directed

Fix scan requests being processed during directed advertisiments.
Directed advertise packets are not scannable
Signed-off-by: Joakim Andersson<EMAIL_ADDRESS>

@joakimtoe

/home/buildslave/src/github.com/zephyrproject-rtos/zephyr/subsys/bluetooth/controller/ll_sw/nordic/lll/lll_adv.c:630:24: error: ‘PDU_ADV_TYPE_ADV_DIRECT_IND’ undeclared (first use in this function)
(pdu_adv->type != PDU_ADV_TYPE_ADV_DIRECT_IND) &&

Seems there are some build failures

@carlescufi Fixed now, I was a bit hasty with this PR it seems.


add support for Sensirion SHT31 temperature/humidity sensor

Description:
I've implemented an adapter for this sensor but I need some help with writing tests for it. Can you point me to some similar sensor tests or advice how to get this PR accepted? Thanks
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#4848
Example entry for configuration.yaml (if applicable):
  - platform: sht31
    name: Room temperature
    monitored_conditions:
    - temperature
    - humidity

Checklist:

[X] The code change is tested and works locally.

If user exposed functionality or configuration variables are added/changed:

[X] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Hi @viorels,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


rdpwrap.ini for (1809) 17763.503 - Win10 X64

New update windows KB4494441& new version 17763.503
File correction needed rdpwrap.ini
Can someone help?

Hello,
You need to remove update KB4499167 and then use http://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab to block (hide) this update.

Edit your current ini by adding a blank line and paste the following. Confirmed working.
[10.0.17763.503]
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=77A41
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=3E520
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=18025
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=1ACDC
SLInitFunc.x64=New_CSLQuery_Initialize
bInitialized.x64      =ECAB0
bServerSku.x64        =ECAB4
lMaxUserSessions.x64  =ECAB8
bAppServerAllowed.x64 =ECAC0
bRemoteConnAllowed.x64=ECAC4
bMultimonAllowed.x64  =ECAC8
ulMaxDebugSessions.x64=ECACC
bFUSEnabled.x64       =ECAD0

not work =(

New update windows KB4494441& new version 17763.503
File correction needed rdpwrap.ini
Can someone help?

Why do you confuse the Windows 10 version with the termsrv.dll file version?
Windows version 17763.503 of May 14, 2019 uses the termsrv.dll file, version 17763.475. The file with the latest updates has not been modified.

Works! Fixed my issue and can connect again!

alguien ya lo puedo reparar?
can I already repair it?
lo único que no puedo quitar el es not listening
the only thing I can not remove is not listening

I might be stupid, but where should I put/what should I do with the rdpwrap.ini file? I don't have an ini file anywhere to replace. If I just put it with the rest of the files and re-run install.bat or update, I still get "not supported"

Hola @SBRK  este se coloca en C:\Program Files\RDP Wrapper
en ese lugar se pone el archivo .ini

problem solved

Works! Fixed my issue and can connect again!

Could you share the rdpwrap.ini file?  ( for 17763.503)  Thanks a lot.

I didn't use the msi installer (because Windows Defender) and instead use the zip version. Is the ini file usable in this case ?

Hey, Yes, it works. I used the ZIP file as well.Check the instruction video, very useful, key thing is to run RDPWinst.exe after updated ini file.Good luck.Von meinem Samsung Galaxy Smartphone gesendet.
-------- Ursprüngliche Nachricht --------Von: Benjamin MICHEL<EMAIL_ADDRESS>Datum: 19.05.19  12:56  (GMT+01:00) An: stascorp/rdpwrap<EMAIL_ADDRESS>Cc: zcq0730<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Betreff: Re: [stascorp/rdpwrap] rdpwrap.ini for (1809) 17763.503 - Win10 X64 (#783) I didn't use the msi installer (because Windows Defender) and instead use the zip version. Is the ini file usable in this case ?
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/stascorp/rdpwrap/issues/783?email_source=notifications\u0026email_token=AJTS632YKFLLX3FYX2H4HQLPWEW6BA5CNFSM4HNA54W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVW7VSQ#issuecomment-493746890",
"url": "https://github.com/stascorp/rdpwrap/issues/783?email_source=notifications\u0026email_token=AJTS632YKFLLX3FYX2H4HQLPWEW6BA5CNFSM4HNA54W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVW7VSQ#issuecomment-493746890",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

This did not work for me does someone have a working ini file???

This cost me quite some time to figure out. Here is the solution worked for me.
My system windows10 pro,  17763.503.
Check the instruction video, very useful, key thing is to run RDPWinst.exe after updated ini file.
Finding a working ini file wasn´t the problem.  Check the following comments if needed.
Good luck!
https://www.youtube.com/watch?v=W9BpbEt1yJw
https://github.com/stascorp/rdpwrap/issues/759#issuecomment-493596622
RDPWInst.exe    | RDP Wrapper Library installer/uninstaller
https://github.com/stascorp/rdpwrap/issues/744#issuecomment-493586640
https://github.com/stascorp/rdpwrap/issues/744#issuecomment-493816641
https://github.com/stascorp/rdpwrap/issues/783#issuecomment-492662982

This did not work for me does someone have a working ini file???

Edit your current ini by adding a blank line and paste the following. Confirmed working.
[10.0.17763.503]
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=77A41
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=3E520
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=18025
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=1ACDC
SLInitFunc.x64=New_CSLQuery_Initialize
bInitialized.x64 =ECAB0
bServerSku.x64 =ECAB4
lMaxUserSessions.x64 =ECAB8
bAppServerAllowed.x64 =ECAC0
bRemoteConnAllowed.x64=ECAC4
bMultimonAllowed.x64 =ECAC8
ulMaxDebugSessions.x64=ECACC
bFUSEnabled.x64 =ECAD0

Do not works for me.
Some Idea ?

problem solved

How you fix it ?

Great program and great support here on the github forum whenever W10 updates, allthough maybe a bit messy and hard to follow...
Any way to update RDPWrapper with needed updates to rdpwrap.ini through RDPWInst.exe, or otherwise keep oneself updated on changes/updates?
Understanding and implementing needed changes to rdpwrap.ini myself seems a bit hard to grasp.
Br,
Vegard

Running 17763.503 from updates installed 05-16 and none of the above solutions work, still keeps on asking to boot out other users before allowing concurrent RDP sessions to login


double-beep: Watch lukaswoegerer.com

double-beep requests the watch of the watch_keyword lukaswoegerer\.com. See the MS search here and the Stack Exchange search here.

lukaswoegerer\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Switch to setup-micromamba

Description
Provide a brief description of the PR's purpose here.
Todos
Notable points that this PR has either accomplished or will accomplish.

[ ] TODO 1

Questions

[ ] Question1

Status

[ ] Ready to go

Codecov Report

Merging #66 (4a7f63d) into main (1187d0c) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files


Expose option for contract removal option

Description
Running an emulator programmatically it restricts removing of contracts, probably because that value is not set as part of the service contracts. Exposing to explicitly set that helps.

For contributor use:

[ ] Targeted PR against master branch
[ ] Linked to GitHub issue with discussion and accepted design OR link to spec that describes this work
[ ] Code follows the standards mentioned here
[ ] Updated relevant documentation
[ ] Re-reviewed Files changed in the GitHub PR explorer
[ ] Added appropriate labels

Contract removal was disabled on all networks with the release of Secure Cadence, as removing a contract and then re-adding a contract with the same name allows circumventing the contract updatability checks, which ensure that a contract update is safe, in the sense that it is supported by the interpreter.
For example, adding a new field is not supported, as existing stored data does not have the field and there is no migration functionality available (yet) to backfill existing fields.
There's currently no immediate plan to solve contract removal, and discussions in the Cadence Language Design meetings regarding this current limitation argued that we might want to completely remove the contract removal functionality.
Are we sure we want to expose this option? Developers will likely enable the option to allow removal, use it incorrectly, and run into crashers locally. Even if they use it in a way that does not crash the environment, they will likely be surprised the functionality won't be available on any network (incl. Testnet).

@sideninja @turbolent  I think I agree with both of you in this;

I think the emulator should have super powers
Also it shouldn't do anythinthat cannot be done on mainnet/testnet

I propose import emulator ( emulator stdlib) and putting everything not in mainnet/testnet in that lib.  So we can use things like emulator.remove_contract, also we can expose a lot of useful stuff. Also when users are using explicitly writing emulator.something gives the impression that it will work only on the emulator, so it will not generate any complaints.

@bluesign Great idea! Only small issue with this is the additional effort required to implement this

@bluesign Great idea! Only small issue with this is the additional effort required to implement this.

If we can manage the stdlib expose from host to cadence, the rest should be pretty easy. But actually, as an added benefit this can clean up a lot of stuff from Cadence ( move them to fvm, emulator etc )
But yeah eventually in the end, additional effort is needed for sure.

@bluesign Great idea! Only small issue with this is the additional effort required to implement this.

If we can manage the stdlib expose from host to cadence, the rest should be pretty easy. But actually, as an added benefit this can clean up a lot of stuff from Cadence ( move them to fvm, emulator etc )
But yeah eventually in the end, additional effort is needed for sure.

Should we open this as an issue (improvement) since I don't think it's feasible addressing with this PR.


preprocess fails for n_jobs>1

Running the latest master I run into issues with the parallelised preprocessing (from #277):
from braindecode.preprocessing import Preprocessor, preprocess, filterbank
from braindecode.datasets.moabb import MOABBDataset

ds = MOABBDataset(dataset_name='Schirrmeister2017',
                           subject_ids=[1], )
splits = ds.split([[i] for i in range(len(ds.datasets))])

fbank = [
            Preprocessor(
                apply_on_array=False,
                fn=filterbank,
                frequency_bands=[(0, 10)],
                verbose=False,
                n_jobs=1
            ),
        ]

for split_i, split_ds in splits.items():
    preprocess(concat_ds=split_ds, preprocessors=fbank, n_jobs=2)

gives the following output:
Creating RawArray with float64 data, n_channels=128, n_times=1225545
    Range : 0 ... 1225544 =      0.000 ...  2451.088 secs
Ready.
Creating RawArray with float64 data, n_channels=128, n_times=616535
    Range : 0 ... 616534 =      0.000 ...  1233.068 secs
Ready.
320 events found
Event IDs: [1 2 3 4]
160 events found
Event IDs: [1 2 3 4]
joblib.externals.loky.process_executor._RemoteTraceback:
"""
Traceback (most recent call last):
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/joblib/externals/loky/process_executor.py", line 431, in _process_worker
    r = call_item()
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/joblib/externals/loky/process_executor.py", line 285, in __call__
    return self.fn(*self.args, **self.kwargs)
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/joblib/_parallel_backends.py", line 595, in __call__
    return self.func(*args, **kwargs)
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/joblib/parallel.py", line 262, in __call__
    return [func(*args, **kwargs)
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/joblib/parallel.py", line 262, in <listcomp>
    return [func(*args, **kwargs)
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/braindecode/preprocessing/preprocess.py", line 223, in _preprocess
    _preprocess_raw_or_epochs(ds.raw, preprocessors)
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/braindecode/preprocessing/preprocess.py", line 220, in _preprocess_raw_or_epochs
    preproc.apply(raw_or_epochs)
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/braindecode/preprocessing/preprocess.py", line 62, in apply
    self._try_apply(raw_or_epochs)
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/braindecode/preprocessing/preprocess.py", line 74, in _try_apply
    self.fn(raw_or_epochs, **self.kwargs)
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/braindecode/preprocessing/preprocess.py", line 473, in filterbank
    raw.add_channels(all_filtered)
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/mne/channels/channels.py", line 1051, in add_channels
    self._data.base.resize(n_bytes)
TypeError: mmap can't resize a readonly or copy-on-write memory map.
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/IPython/core/interactiveshell.py", line 3437, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-3-afd28816663e>", line 19, in <module>
    preprocess(concat_ds=split_ds, preprocessors=fbank, n_jobs=2)
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/braindecode/preprocessing/preprocess.py", line 158, in preprocess
    list_of_ds = Parallel(n_jobs=n_jobs)(
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/joblib/parallel.py", line 1054, in __call__
    self.retrieve()
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/joblib/parallel.py", line 933, in retrieve
    self._output.extend(job.get(timeout=self.timeout))
  File "/home/dan/Documents/AGBALL/RiemNetEnv/lib/python3.8/site-packages/joblib/_parallel_backends.py", line 542, in wrap_future_result
    return future.result(timeout=timeout)
  File "/usr/lib/python3.8/concurrent/futures/_base.py", line 444, in result
    return self.__get_result()
  File "/usr/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result
    raise self._exception
TypeError: mmap can't resize a readonly or copy-on-write memory map.

I don't replicate the pb on my mac using latest version of braindecode on master branch.

Strange - I just uninstalled and then reinstalled with:
pip install https://github.com/braindecode/braindecode/archive/master.zip
and still run into the same issue (joblib=1.0.1, mne=0.23.0)

can you also update mne to main branch?

Same issue running mne=0.24.dev0

I was just able to reproduce the issue on a server, I'll look into it @dcwil

Seems like the issue is with joblib.Parallel's max_nbytes argument, which is set to 1 MB by default. The code fails because the data that has to be memmapped is around 1.3 GB in the case of this dataset. For instance, this didn't fail when I cropped the data and picked only a few channels.
I'm not sure what the best approach would be to fix this issue in the codebase. It would be nice to be able to set max_nbytes with the standard joblib context manager, that way users could adapt this based on the size of their data - there is an open issue here on this, not sure whether this will be addressed at some point: https://github.com/joblib/joblib/issues/912
Another option would be to add a max_nbytes parameter to preprocess().
Any ideas/preferences @agramfort @robintibor ?

I spent a bit more time looking into this, and I think I was actually looking at the problem the wrong way. The error occurs because of two things: (1) the data is preloaded (this dataset is loaded from .mat files so it cannot be created with preload=False), and (2) preprocess.filterbank() resizes the internal data when concatenating all the filtered channels together.
When the data is preloaded and the data is above joblib's default max_nbytes=1 MB, the data is automatically memapped. Memapped arrays cannot be resized, which raises the error reported above. If on the other hand the dataset had been created with preload=False there would be no memapping and no error (the Preprocessor would call load_data inside each process).
Possible solutions:
(1) work with preload=False. A hack when the data is e.g. in .mat format would be to save the BaseConcatDataset and reload it with preload=False.
(2) Provide a max_nbytes argument in preprocess and ask the user to disable memapping whenever a preprocessing function reshapes the array/raises this error.
(3) Disable memapping altogether by setting max_nbytes=None in preprocess.
I think (1) is not efficient or elegant. (3) would mean we never benefit from joblib's memapping capabilities, and so lose out on the chance to further reduce memory usage. I think (2) is our best shot.
Here's what I suggest:

Adding a max_nbytes argument to preprocess.
Catching the error reported by @dcwil inside preprocess and raising our own error that clearly indicates what the problem is and how to fix it (i.e., by setting max_nbyes=None or using preload=False)

If @agramfort and @gemeinl agree with the solution I'll do a quick PR to fix this.

fine with me

Hello @dcwil,
I was wondering, can we close this issue?

Hi @bruAristimunha
Looks like I can still reproduce the error in 0.6, using the same snippet


directory listing fails on the website

e.g. http://lib.haxe.org/p/hxnodejs/4.0.3/files/src

Looks like it's only for newly uploaded versions http://lib.haxe.org/p/hxnodejs/4.0.2/files/

Nah, it's the same http://lib.haxe.org/p/hxnodejs/4.0.2/files/src/

Hmmm http://lib.haxe.org/p/lime/2.9.0/files/lime/tools/mpeg/audio/ this works

This doesn't work http://lib.haxe.org/p/haxelib_client/3.2.0-rc.3/files/src/
So I guess src folders aren't working.

that's really weird

Seems random http://lib.haxe.org/p/openfl-samples/3.1.0/files/openfl-samples/ http://lib.haxe.org/p/openfl-samples/3.3.1/files/openfl-samples/
maybe some decompression/file creation issue?

Hmm, I think it's deployed, but the problem is still there. I wonder why it worked for me locally.

It works for new uploads (http://lib.haxe.org/p/hxnodejs/4.0.4/files/src), so this is probably a cache issue.

That's still a strange bug even if the cache is behaving weirdly
That's only on directory
http://lib.haxe.org/p/openfl-samples/3.3.1/files/openfl-samples/
http://lib.haxe.org/p/openfl-samples/3.3.1/files/openfl-samples/README.md
you can access the files if you know about them
and not all directories of the same lib version fail
http://lib.haxe.org/p/openfl-samples/3.3.1/files/openfl-samples/demos/NyanCat/

@andyli or @jasononeil (still not sure who to ping) this might require some server maintainance: we need to clear zip caches.
I see this ufront task that should do that, but it requires project/version, and I think we need to do that for ALL projects and versions: https://github.com/HaxeFoundation/haxelib/blob/development/src/website/tasks/HaxelibCacheTasks.hx#L21

@ibilon I think I fixed that, see e7e6b615f937c3dc888bf2bf0164288ad8444b8e

I.e. that depends on whether an entry was added to the zip file for a directory or not.

Oh I see, make sense.

I see this ufront task that should do that, but it requires project/version, and I think we need to do that for ALL projects and versions

There's always clearAll https://github.com/HaxeFoundation/haxelib/blob/development/src/website/tasks/HaxelibCacheTasks.hx#L15 it's a bit overkill but at least it'd work.

I was toying with tasks.n today and couldn't get it to work - it seems that there's something wrong with minject or injector configuration, so HaxelibCacheTasks.api doesn't get set to a DBCacheApi instance and it crashes.
Could someone with ufront/minject knowledge help me here?

I looked at this, it does the injection but with the value null.
most likely since injector.getInstance(DBCacheApi) throws Uncaught exception - Error while getting mapping response: No mapping defined for class "ufront.cache.DBCacheApi" name "null"
But the class is correctly returned in this https://github.com/HaxeFoundation/haxelib/blob/development/src/website/Tasks.hx#L34
Still fails even if I add tasks.injector.map( DBCacheApi ).toClass( DBCacheApi );
Well anyway, I get the use of injection, but here it's a 100 lines software that's not meant to be used as a library where we do obj.fn(),
removing the injection and doing new DBCacheApi().clearAll();  would be so much simpler.

Any news on how we could resolve this?


Feature Proposal: Support MySQL as metadata store in Databuilder

My workplace is going to use Amundsen with MySQL as metadata store but currently, Amundsen only supports Graph DB as the backend metadata store. We plan to do the dev work to integrate Amundsen with MySQL. There would be some work to do in databuilder and metaservice and I created this issue for any possible work needed to do in databuilder.

Expected Behavior or Use Case

The workflow would be similar to the existing one and backend store would have relational DB options, like MySQL
Service or Ingestion ETL

Data loader, publisher and models in Databuilder
Possible Implementation

Currently, Amundsen does not support any relational DB as backend store, so we have to support ORM first with 'SQLAlchemy' for relational DBs. Considering the possible metadata schema change, we have to add a feature to support DB version management with 'alembic'.

We may need new models that work with ORM and probably different fields from the existing model. I would also like to know if it is possible to update all current models to let them work with both graph and relational DBs? I assume we still use current ETL logic for the metadata to be pushed to MySQL, so for the model used for mysql, is it good to develop new iterator working for each row instead of 'node' and 'relationship' in model?

Add data loader that work for MySQL

Add MySQL publisher

All the above is possible implementation looking forward a better solution. If I missed anything or the proposal is not proper, please advise. Thanks.
Example Screenshots (if appropriate):
Context
We are not sure if there is a plan to support relation DB from Amundsen side and in order to use Amundsen and MySQL as the metadata engine in my workplace, we plan to do the dev work to support MySQL as backend store.

will take a look next week.

also we should create a rfc in https://github.com/amundsen-io/rfcs . And it would be good to be more explicit about how to map the graph model to ORM model .
In terms of databuilder, @AndrewCiambrone has a proposal( https://github.com/amundsen-io/rfcs/pull/5) to make the entity more generic.

here are a few additional thoughts:
1). we initial target graph model because it is easier to model metadata entity connection through a graph (e.g we could easily add more additional structure metadata(e.g update time, create time, etc) for the entity by just adding a new node with connection to the entity(e.g dataset). It would be good to understand what is ORM model looks like (e.g will it be a denormalized model which each entity has all the metadata inside a single schema?) This would be good to be more explicit for the RFC.
2) Depends on 1, I haven't thought about how to modify the existing model to an ORM model. cc @jinhyukchang as well

@feng-tao Thanks for your reply. Yes, Graph DB has some advantages on metadata store and it is good to know the work of @AndrewCiambrone, which will bring more generic graph db models. For the ORM model, we will have to make a trade-off between the normalized and denormalized models for metadata store due to some concerns, like performance, consistency issues. Also, the model will need support schema upgrade to handle possible metadata structure change. I am trying to figure out how to map graph DB model to ORM model, probably with the incoming abstraction layer for an explicit plan.

Done in https://github.com/amundsen-io/amundsen/blob/main/databuilder/databuilder/extractor/mysql_metadata_extractor.py


Bluetooth adapter is not available

Hi everybody. I'm trying the flutter blue example on an Android 10 device but when I open the app i get this msd: "the bluetooth adapter is not available"!
If I debug that I see that the FlutterBlue.instance.state is null! But if i open the app in an older Android device it works fine!
Can somebody help me?

I am getting the same issue in my project but only when do a release build.
I have run it on Android 10 & 11 same issue.
Android Manifiest
<manifest xmlns:android="http://schemas.android.com/apk/res/android"     package="com.example.flutter_base">     <!-- Flutter needs it to communicate with the running application          to allow setting breakpoints, to provide hot reload, etc.     -->     <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>     <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>     <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>     <uses-permission android:name="android.permission.RECORD_AUDIO" />     <uses-permission android:name="android.permission.CAMERA" />     <uses-permission android:name="android.permission.INTERNET" />     <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>     <uses-permission android:name="android.permission.BLUETOOTH" />     <uses-permission android:name="android.permission.BLUETOOTH_ADMIN" /> </manifest>
build.gradle
`android {
compileSdkVersion 29
lintOptions {
    disable 'InvalidPackage'
}

defaultConfig {
    applicationId "com.x.x"
    minSdkVersion 24
    targetSdkVersion 29
    versionCode flutterVersionCode.toInteger()
    versionName flutterVersionName
    testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}`

I didn't think about it but I also have this issue only in a release build. How is it possible??

I have the same issue

Please try to role back to 0.7.2 and also make sure you have removed these permissions because these are already there in the plugin.
android.permission.ACCESS_FINE_LOCATION
android.permission.BLUETOOTH
android.permission.BLUETOOTH_ADMIN

Just FYI, we found a workaround by rolling back to v0.7.2. So if you don't need the protobuf-lite fix. Just roll back and you will be good to go.

Ok i'm gonna try this and i'll let u know
Il Mer 18 Nov 2020, 17:17 Jody Holmes<EMAIL_ADDRESS>ha scritto:

Just FYI, we found a workaround by rolling back to v0.7.2. So if you don't
need the protobuf-lite fix. Just roll back and you will be good to go.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pauldemarco/flutter_blue/issues/726#issuecomment-729787253,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADEWB4KNEBODED3WGHJ6MZLSQPXP3ANCNFSM4TY6Y3GQ
.

You're right. Now the app works correctly. Thank you.

Please try " flutter build apk --no-shrink " to build your release build.

Yes, 0.7.3 with "flutter build apk --release" is not working.  With "flutter build apk --no-shrink " indeed works.
Looks like R8 is messing up.

Just FYI, we found a workaround by rolling back to v0.7.2. So if you don't need the protobuf-lite fix. Just roll back and you will be good to go.

I just hit this, only release build is affected. Is there an other issue involved? Can your reference? I don't need or use protobuf.

Ok, I think this is a protobuf issue @Hoopstr42 mentions: https://github.com/pauldemarco/flutter_blue/issues/717
I saw the "WARNING: This version of flutter_blue will break your Android build if it or its dependencies aren't compatible with AndroidX.".

We should mention this as a breaking change.

Guys, I nuked my whole android port and re-created it because of https://github.com/miguelpruivo/flutter_file_picker/issues/545 and I tested and now 0.7.3 does not produce the release-only error for me. This means that this problem is not with flutter_blue but because of the complexity and interference of this system with many moving parts.

Lately even nuking and recreating the android port doesn't solve this.

https://github.com/pauldemarco/flutter_blue/issues/662 helped

I have same issue

I have same issue

flutter_blue: ^0.7.3
I've the same issue building the APK release with "flutter build apk --release" in Android 7.1.1 (Samsung Tablet) and Phone (Motorola Android 10).
But the workaround "flutter build apk --no-shrink" works for me.

flutter_blue: ^0.7.3
I've the same issue building the APK release with "flutter build apk --release" in Android 7.1.1 (Samsung Tablet) and Phone (Motorola Android 10).
But the workaround "flutter build apk --no-shrink" works for me.

flutter build apk --no-shrink

this is not works for me (android 8.1)

flutter build apk --no-shrink

this is not works for me (android 8.1)

Seems to be happening on IOS as well, and none of the work arounds function.

Seems to be happening on IOS as well, and none of the work arounds function.

Still an issue in IOS, none fix found so far.

@MrCsabaToth Hey small world I saw you at Google Dev Fest in Fresno.. maybe like 2017?

@MrCsabaToth Hey small world I saw you at Google Dev Fest in Fresno.. maybe like 2017?

Oh yes, Valley DevFest!

       Work-around for https://github.com/pauldemarco/flutter_blue/issues/772

add the below two lines in buid.gradle(app) -> buildTypes -> release
shrinkResources false
minifyEnabled false

works like magic

buildTypes {
release {
// TODO: Add your own signing config for the release build.
// Signing with the debug keys for now, so flutter run --release works.
signingConfig signingConfigs.debug
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
shrinkResources false
minifyEnabled false
}
}
Note:- Run  flutter build apk --no-shrink
Working :)


Authentication Required

When I press on "retrieving rout" then I get  Authentication Required .
What and Where configure it ?
Can I disable it ?

Hi @alexd555. Routing is a premium service which consumes credits, so this does require logging in.
You can read more about direction capabilities here: https://developers.arcgis.com/features/directions/
Are you inquiring on how to use the app builder's credentials for this purpose so that a user of the app is not presented with this 'Authentication Required' challenge?


Output Image is always PNG , croppie not keeping original Format

Hello ,
Im trying to integrate Croppie inside a simple WebApp ( HTML/php + js / css) and here is how is my code looks like :
`document.addEventListener('DOMContentLoaded', function() {
var extension = "1212121";
$image_crop = $('#image_demo').croppie({
enableExif: true,
viewport: {
width: 1180,
height: 600,
type: 'rectangle' //circle
},
boundary: {
width: 1280,
height: 800
},
});
$('.house_img').each(function() {
var id = $(this).attr("id");
    $('#' + id + '').on('change click', function() {
		extension = $(this).val().split('.').pop();
        var reader = new FileReader();
        reader.onload = function(event) {

            $image_crop.croppie('bind', {
                url: event.target.result,
            }).then(function() {
                console.log(extension);
            });

        }
        reader.readAsDataURL(this.files[0]);
        $('#uploadimageModal').modal('show');

    });

})
    $('.crop_image').click(function() {
					var GetCropper = $(".crop_image")[0]['attributes']['data-selected'].nodeValue;
					$image_crop.croppie('result',{
						type: 'canvas',
						size: 'original',
						format : 'jpg',
						quality: 0.5,
					}).then(function(response){
					$.ajax({
						url:"./queries/upload.php",
						type: "POST",
						dataType: 'json',
						data:{"image": response},
						success:function(data)
							{
								$('#uploadimageModal').modal('hide');
								image_placing = $('#uploaded_image').find('img');
								image_placing.each(function(){
										if($(this).attr('data-reading') == GetCropper )
										{

											$(this).attr('src','../images/uploads/'+encodeURI("%")+'temp'+encodeURI("%")+'/'+data['image']+'');
											$(this).next().val(data['image'].split('.').slice(0, -1).join('.').concat('.'+data['filetype']));
										}
								})

							}
						});
				})

            $('#uploadimageModal').modal('show');

    })

});`
The problem is that the croppie is converting my Image Always into PNG even if i choose JPEG it dosen't work at all , and not reducing the quality
is there something wrong on my Code ?
thank you

from: https://foliotek.github.io/Croppie/

from your code
$image_crop.croppie('result',{
   type: 'canvas',
   size: 'original',
   format : 'jpg',
   quality: 0.5,
})

jpg isn't a valid format.
try changing it from jpg to jpeg

@xiisaiki did you manage to fix this problem ? We also want Croppie to keep the same output !

I also have this problem, even changing the format to 'jpeg', the image always 'png'.
$uploadCrop = $('#upload-site').croppie({
	format: 'jpeg',
	quality: 0.5,
	viewport: {
		width: 300,
		height: 225
	},
	boundary: {
		width: 390,
		height: 320
	}
});

Sorry, wrong place declared... solved
$('.upload-site-result').on('click', function (ev) {
	$uploadCrop.croppie('result', {
		type: 'canvas',
		size: 'viewport',
		format: 'jpeg',
		quality: 0.9,
	}).then(function (img) {

If you want to keep the image format then you should just add extra logic to check what is the extension of the file that user picked, and then tweak the value of croppie's result format based on that. Keep in mind that croppie can only output jpeg, png, and webp format though, at the time of my writing. (so it's not possible to let GIF stay GIF).


Revert "Add TLSv1.3 cipher suites for OpenSSL-1.1.1"

This reverts commit 9d0317b881d53af89e6ab14f86b4f786f733a0d6.

Revert #3601. The name of TLSv1.3 cipher suites and APIs to configure them has been changed since OpenSSL v1.1.1-pre3. Details in #4007.

[approve ci]


Extract data from header and use in subsequent calls

Is it possible to get the authorization header from the response and use it in subsequent requests ?

Certainly!  This can be done with a header extractor:
Add this to your test to extract the header from the response and use in future tests with variable 'auth_value':
- extract_binds:
        - 'auth_value': {'header: 'auth_header_name'}

Nopes, not working, getting this error:
ValueError: Extractor header is not a valid extractor type
with the following definition:

extract_binds:
- 'auth_value': {header: 'Authorization'}

Ah, that error you're seeing is because the version you are using does not support this feature yet.
It was just added 1/25 to the master, so you may have to clone the latest, or if you prefer to have a version from PyPi, I should be finished testing and have one pushed by this weekend.

@noorbakerally: I've released this version on PyPi, so you no longer need to clone the repo & install from that to get this feature.  Please open an issue if it misbehaves (this is still considered to be a beta feature, although of course it has plenty of test coverage).


Quest Delay (Request)

Maybe there could be a config option to left click an NPC and it'll tell you when you can do the quest again or maybe even a timer in the GUI would be awesome!

If love this feature too.

After looking into this, it is possible, but the method to do this requires some looping (to check all quests), which if spammed could lag the server. And I'd rather not have Quests moderate how fast players can click, so I'm gonna have to pass. Thank you for the suggestion!


Emacs service does not create socket file

Issue description

Since 3815248 I'm having the following issue with the configuration
{
  programs.emacs.enable = true;
  services.emacs.enable = true;
}

The user service appears to start and systemd --user status emacs.service shows it as active (running), but there is no server file created at the usual location (/tmp/emacs1000/server), and emacsclient fails to connect:
$ emacsclient -t
/nix/store/d23fp87461xdkk4g25ky8njcbm5h46m9-emacs-26.3/bin/emacsclient: can't find socket; have you started the server?

I looked at 3815248 to try to understand what changed and noticed a subtle difference in the ExecStart attribute. When I reverted this change (https://github.com/mcwitt/home-manager/commit/a378d2bc9744b6bb083d130e2598470c5ee36806), the issue disappeared and emacsclient is able to connect. I'm not sure I understand why the shell wrapper was there in the first place, but seems like it might be necessary?
Meta
Maintainer CC

@tadfisher
Technical details

system: "x86_64-linux"
host os: Linux 5.4.46, NixOS, 20.09pre230335.9480bae3370 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.6
channels(root): "nixos-20.09pre230335.9480bae3370"
channels(matt): "home-manager"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Thanks, I will revert to the wrapper shell after work tonight.

Hmm, the difference is that bash -l performs this:
Make bash act as if it had been invoked as a login shell (see INVOCATION below).

So I'm suspecting that the service isn't inheriting some environment variable needed to create the socket file. Which is strange, because the socket file should be simply /tmp/emacs${UID}/server in your case.
The upstream Emacs .service file doesn't use a wrapper login shell to start its service: https://github.com/emacs-mirror/emacs/blob/master/etc/emacs.service
So I'm not sure why our service, which doesn't function any differently (when socket activation is not enabled, at least), requires a full login shell environment to launch a foreground daemon with the default socket.

I investigated on my side a bit more, and it seems like the problem might be that the daemon is encountering an error while loading init.el, and that this prevents the server from starting (though the service is still active).
Now that you mention it, I think it makes sense why we would want to run inside bash -l, since otherwise Emacs wouldn't have access to the login shell's PATH and wouldn't have access to external commands like git that (I think) aren't included in the minimal environment set up by systemd.

That's a good enough reason to reinstate the login shell wrapper, yes. But it still feels like a hack to work around systemd's service isolation by running a service in a login shell. Ideally we'd figure out what environment variables need to be set and set them per-service or per-user via ~/.config/environment.d.
As far as $PATH and such from within Emacs, that can (and should!) be overridden via exec-path. In fact, this is done for you if you use emacsWithPackages, as that builds a site-start.el which adds your Nix profile paths to load-path and exec-path appropriately.
Musing a bit, this may be the root cause: the site-start.el generated by the nixpkgs Emacs derivation pulls these paths from NIX_PROFILES, which may not be set for the systemd user manager. @rycee, do we have a story for importing these important environment variables? nixpkgs uses system.build.setEnvironment for this, though it's not universally used.

Yeah, we'll have to figure out some good way to introduce a login like environment in a service. It would be simple to do globally for all services but I would like to avoid that as long as possible.


autofocus needed.

This is a nice frontend to aria2c. Make autofocus in the textarea of the 'new' page will be more effective. And also make the 'start' button to the left?

Thx for your suggestion. In AriaNg 0.1.0 beta-3, the layout of "new task" page has been adjusted, and the "download links" text box would be focused automatically while entering "new task" page. https://github.com/mayswind/AriaNg/releases/tag/0.1.0-b3


Use docker-compose in Jenkins builds

Mounting point is wrong.  Jenkins does not find the build directory when looking for the test results.

The good news is that when I fix that the plugin for the warnings will fully work at last...

Ready for review


Make studies awaiting approval more obvious

It is not obvious in the interface when there is a study awaiting approval. It should be clearer so that studies aren't in the queue longer than necessary.

@adamrp can you elaborate? We already have an Admin page that lists only those studies that are waiting for their processed data to be approved...
The only think that I can think of is once an "Admin" logs in, show a message on top of the page stating that there are studies waiting for approval. Is that what you mean?

Can we generate an email as a heads up - I am not always working only on
Qiita?
On Thu, Apr 16, 2015 at 9:38 AM, josenavas<EMAIL_ADDRESS>wrote:

@adamrp https://github.com/adamrp can you elaborate? We already have an
Admin page that lists only those studies that are waiting for their
processed data to be approved...
The only think that I can think of is once an "Admin" logs in, show a
message on top of the page stating that there are studies waiting for
approval. Is that what you mean?
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/issues/1065#issuecomment-93780500.

--
Gail Ackermann
Knight Lab
UCSD
<EMAIL_ADDRESS><EMAIL_ADDRESS>

Basically, this came up because @ackermag was not aware that there was a study awaiting approval, even though she was using Qiita. In other words, she would have to go to that admin page in order to see the studies awaiting approval. It would be ideal if it was somehow indicated in the menu bar that there were studies awaiting approval, or if on the main login page for admins, if it said in red text "There are ## studies awaiting approval" or something

Awesome thanks! I think a banner on top would be great! Adding to Alpha 0.2 as I think it's easy and it will improve the Qiita usage :smile:

Maybe a feed on the home page, we are currently not using the home page
for anything.
On (Apr-16-15|17:30), josenavas wrote:

Awesome thanks! I think a banner on top would be great! Adding to Alpha 0.2 as I think it's easy and it will improve the Qiita usage :smile:

Reply to this email directly or view it on GitHub:
https://github.com/biocore/qiita/issues/1065#issuecomment-93867860


Removes Special Characters.

Hi,
When i use title-case with special characters in the text, it removes all the special characters and returns only the text.
Regards,
Nilesh

Closing as duplicate of #11. Happy to accept a PR rewriting the functionality.


Loop Protect Error-Finding length of the word in the string

Challenge Name
Find the Longest Word in a String has an issue.
Issue Description

Browser Information

User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0.
Screenshot

Your Code

function findLongestWord(str) {
  str=str.split(' ');
  var lenlt=0;
  var temp;
  for(var i=0;i<str.length;i++){

    temp=str[i].length;
    if(temp>lenlt){
      lenlt=temp;
    }else{
      lenlt=lenlt;
    }
  }
  return lenlt;
}

findLongestWord("The quick brown fox jumped over the lazy dog");
//console.log(lt);

The above code works fine in Live site with out any issues.

@vikramnr I copy and pasted your code in beta site and your code passed all of the tests. Can you please check again?

Also I would like to suggest a minor improvement in your code. You don't really need the "else" part.  You can remove the else block and it will still pass all the tests.
function findLongestWord(str) {
  str=str.split(' ');
  var lenlt=0;
  var temp;
  for(var i=0;i<str.length;i++){

    temp=str[i].length;
    if(temp>lenlt){
      lenlt=temp;
    }
  }
  return lenlt;
}

findLongestWord("The quick brown fox jumped over the lazy dog");

@anku255  Yes its passing the test now. Thanks for the suggestion.  But how is possible. Is it browser refresh/cache  stored .?


Missing py.typed

Hiya and thanks for this library.
The issue is that it doesn't play nice with type checkers - because its missing a py.typed file. The fx is simple - add a py.typed file (its an empty file) into the source folder of the lib, and bundle it as part of the wheel. You can find instructions in the mypy docs.
Cheers.

Can you provide what is the issue exactly? what type-checker are you running? how are you running it? etc.?

I'm running mypy. This is a standard mypy requirement - https://mypy.readthedocs.io/en/stable/installed_packages.html

I am not experienced with mypy, how do you run it? I need instructions how to replicate..

@Goldziher I've discussed with with @cunla and the resolution we came to was that we'd get type annotations added to fakeredis when and as time allows. @cunla did not think it would be feasible to type-annotate the entire fakeredis codebase in a single pass, and (though I tried) I couldn't poke any holes in his logic.
tl;dr typing will be added eventually, and is fairly high on my wishlist, but it won't be an instant thing.


Fix OnMetalScout so it sees nodes in maintenance as provisioned

Fixes #39

+1 LGTM, one note inline for now or the future. Merge or fix, your choice :)

:+1: shipit.gif


camel casing problems with .default(..

If i pass an option like --this-option yargs auto creates the camel cased version so the argv object includes this-option and thisOption.
On the other hand if i specify .default('this-option', 'value') and i don't pass any --this-option arg then the argv does not contain camelCased version with default value. Only this-option is present

@davibe try the upcoming release of yargs, and let me know if this solves the problem for you:
npm i yargs@next
:+1:


chore(runtime-core): use ReactiveFlags for consistency

A test case failed in CI, but was successful on the local machine, I will try to find out why.


Document software versions

Fix for GHE issue at https://GHE/CFPB/project-success/issues/38
Additions

section on the intro page of docs for Versions of software
descriptions of the back-end requirements files
added more softwares to the "Technology stack" and "Additional dependencies" lists. I am admittedly fuzzy on the distinctions here so feedback welcome if you have a solid definition for each of those categories for me.

Removals

Changes

Testing
pip install -r requirements/docs.txt
mkdocs serve

go to http://<IP_ADDRESS>:8000/
Screenshots
Notes

is there anything in the requirements list that has changed in the past few days? For example, I noticed that manual.txt became docs.txt (💯 ). Anything else that needs updating here?

Todos

add real info about Apache! Help me out

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the development playbook
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ ] Project documentation has been updated
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist
Browsers

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Internet Explorer 8, 9, 10, and 11
[ ] Edge
[ ] iOS Safari
[ ] Chrome for Android

Accessibility

[ ] Keyboard friendly
[ ] Screen reader friendly

Other

[ ] Is useable without CSS
[ ] Is useable without JS
[ ] Flexible from small to large screens
[ ] No linting errors or warnings
[ ] JavaScript tests are passing

Made revisions, ready for review again


Include a lambda/package.json on create-node-lambda

Using the command lager create-node-lambda creates a folder structure for the Lambda code and includes a "config.json" file with user created modules listing, but I miss a list for my external modules (node_modules) like a "package.json".
It happens a lot when using multiple endpoints with require repeating external modules.
Lager could automatically place a simplified "package.json" file with x-lager.dependencies for user created modules.

Done in https://github.com/lagerjs/lager/commit/a7adb5055b14429e62207cc811c3dbc9c46a20d5

The project dependency mechanism for Lambda modules works now like for project modules. It is configured in package.json.
Example:
{
  "x-lager": {
    "dependencies": [
      "data-access",
      "log"
    ]
  }
}

Also, it is possible now to not provide a package.json file in a project module.

Cheers!


Lorem ipsum text changes.

-Scan the Regenerate/ Exit Key. This can be found on the last page of your PDF personal copy.
-Remove Note.

-Need back button.

-Heading will be: ‘The Server is not responding?’

-Back button.

Lorem Ipsum on the main selection screen and on the Server not responding


Metric dashboard refresh rate

"Metrics refresh depends on time range with minimum of five minutes. "
I have a metrics dashboard with 1 minute granularity (last 30 mins) that is refreshing every minute. Is the quote above outdated?

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

ID: 7eae3c08-ec6d-7582-d4d9-59de75c0e252
Version Independent ID: 97123dec-34d3-2cde-8060-e7c0e0d4e87f
Content: Visualizing data from Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/visualizations.md
Service: azure-monitor
Sub-service: ****
GitHub Login: @bwren
Microsoft Alias: bwren

@dcbrown16  Thanks for your comment. We will review the issue and get back to you shortly.

#label:"CreateAzMonWIFeb2021"

Thank you for your contribution to the Azure Monitor documentation. We have created a workitem for this issue in our internal backlog database. We will prioritize it and make any necessary changes as we are able.
#please-close


More reserved word preservation

Changed default_reserved_words from a list to a set
Not anonymizing BGP well-known communities
Not anonymizing reserved words in password lines

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


IRPSRE-5846: Bump to 8.5.5

Description

Please include a brief summary of the changes.

Context / Why are we making this change?

Please include details on why this change is necessary, and any applicable tickets, design docs, or documentation links.

Testing and QA Plan

How has this work been tested or QA'd?

% bazel test //...
INFO: Analyzed 37 targets (99 packages loaded, 7512 targets configured).
INFO: Found 32 targets and 5 test targets...
INFO: Elapsed time: 42.538s, Critical Path: 19.46s
INFO: 174 processes: 65 internal, 109 linux-sandbox.
INFO: Build completed successfully, 174 total actions
//test:grafana_docker_test                                               PASSED in 12.7s
//test:grafana_with_plugins_docker_test                                  PASSED in 11.8s
//test:json_existing_uid_test                                            PASSED in 0.8s
//test:json_no_uid_test                                                  PASSED in 0.4s
//test:py_dash_test                                                      PASSED in 0.8s

Executed 5 out of 5 tests: 5 tests pass.
INFO: Build completed successfully, 174 total actions

Impact

What are the implications of these changes? Are there any cross-cutting concerns to keep in mind?


SQLRunner Support

Add support for SQL Runner on DashDB

Migrated to https://github.com/snowplow/sql-runner/issues/74


Enable mappings for different modes

This PR adds support for mappings in other modes than normal-mode, as discussed in #249 .
@kristijanhusak fyi I'm still working on the part concerning your vim.keymap.set example ;)

You will cover the other options also in this PR?

Yes, should find time for it this week

some_multi_mapping = {
    x = 'org_mappings.previous_visible_heading_visual', -- different function if needed. If not, use the same value as for normal mapping
    o = {'org_mappings.previous_visible_heading_operator', true }, -- pass down the arguments to a function if needed.
}

@kristijanhusak we could make the first mapping equal to x = { 'org_mappings.previous_visible_heading_visual' }, demanding it to be a table. That would make it more consistent with the basic mapping and prune one additional way to do things.

@jgollenz yeah, do that. More consistent is better.

@kristijanhusak sorry, it took a while. Should be working now


[BUG] future_pokemon_release does not work as defined

"release": {
      "any": {"release_below_cp": 500, "release_below_iv": 0.8, "logic": "or"},
}

[TransferPokemon] [INFO] [future_pokemon_release] Releasing Magmar [CP 1353] [IV 0.64] based on rule: CP < 500 OR IV < 0.8
[TransferPokemon] [INFO] [pokemon_release] Exchanged Magmar [CP 1353] [IV 0.64] for candy.

If I'm not mistaken, the future_pokemon_release logic does not work as defined. CP 1353 and IV 0.64 must not be released with the config above.

Your logic operator is "or", so the code works as expected, it should be "and".
Release if cp < 500 OR iv < 0.8
Magmar iv = 0.64

Hi, @justinbeatz, I'm actually a programmer, and of course I'm familiar with AND and OR logics.
Could you please read logical expressions for more information about why future_pokemon_release works incorrectly and how it should work.
Here are examples:
#1 OR
Release if CP < 500 OR IV < 0.8
Magmar => CP 1353, IV 0.64
Hence Magmar should not be released because it satisfy one of the given conditions.
#2 AND
Release if CP < 500 AND < 0.8
Magmar => CP 1353, IV 0.64
Hence Magmar should be released because he doesn't satisfy one of the given conditions.

@rendyep You are confused. You are interpreting the logical conditions as if they were "keep" instead of "release".
Example:
"Release if CP < 500 OR IV < 0.8" means that:

CP501 IV0.8 is kept
CP499 IV0.8 is released
CP501 IV0.79 is released

@rendyep
Release if (CP < 500 OR IV < 0.8)
Magmar => CP 1353, IV 0.64
It should BE released, because inside () evaluate to ture.


Can't import OpCOde

I can't import OpCode from fastwebsokcets whatver futures i use. i tried the example from the examples folder

What error are you getting?

Closing as you can include OpCode like this:
use fastwebsockets::OpCode;

If its still an issue, re-open with the error output and reproduciton.


Fix typo in AWS VPC

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


JSONException is not really informative

I've been getting these errors when job is fails to run due to an error in targeting for example.
Probably every time that API replies with error.
Printing the error instead of this Exception would be more informative to the user.
08:46:13 ERROR: Build step failed with exception
08:46:13 net.sf.json.JSONException: JSONObject["return"] is not a JSONArray.
08:46:13 	at net.sf.json.JSONObject.getJSONArray(JSONObject.java:1986)
08:46:13 	at com.waytta.SaltAPIBuilder.performRequest(SaltAPIBuilder.java:268)
08:46:13 	at com.waytta.SaltAPIBuilder.perform(SaltAPIBuilder.java:204)
08:46:13 	at com.waytta.SaltAPIBuilder.perform(SaltAPIBuilder.java:164)
08:46:13 	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
08:46:13 	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
08:46:13 	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
08:46:13 	at hudson.model.Build$BuildExecution.build(Build.java:206)
08:46:13 	at hudson.model.Build$BuildExecution.doRun(Build.java:163)
08:46:13 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
08:46:13 	at hudson.model.Run.execute(Run.java:1730)
08:46:13 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
08:46:13 	at hudson.model.ResourceController.execute(ResourceController.java:97)
08:46:13 	at hudson.model.Executor.run(Executor.java:405)
08:46:13 Build step 'Send a message to Salt API' marked build as failure
08:46:13 Notifying upstream projects of job completion
08:46:13 Finished: FAILURE

This has been corrected in the master branch (as of #72 ) and will be in the next release.

Coolio. Closing.

Version 3.0 released which incorporates these fixes. The major version was bumped due to supporting saltapi with tornado, which caused changes to the returned output for both tornado and cherrypy.
Pre-3.0 output
"return": [{
  "minionid": "Results and output"
}]

Output in 3.0
"Result": {
  "minionid": {
    "return": "Results and output"
  }
}


add step check

Codecov Report

Merging #18 into code-audit-preview will decrease coverage by 0.05%.
The diff coverage is 33.33%.

@@                  Coverage Diff                   @@
##           code-audit-preview      #18      +/-   ##
======================================================
- Coverage                46.2%   46.15%   -0.06%
======================================================
  Files                      39       39
  Lines                    3798     3809      +11
======================================================
+ Hits                     1755     1758       +3
- Misses                   1759     1763       +4
- Partials                  284      288       +4

Impacted Files
Coverage Δ

validate/validate.go
7.92% <100%> (ø)
:arrow_up:

exec/vm.go
52.41% <27.27%> (-1%)
:arrow_down:

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 d052b77...efc3761. Read the comment docs.


Added an option to choose propagator in OrbitPlotter

Now we can choose appropriate propagator in OrbitPlotter while calling plot(). Solves #347

Just for reference

It's great that we have so much flexibility, but perhaps it's too much. We are already setting the number of sampling points in the OrbitPlotter constructor, so what do you think of keeping the method as a plotter property as well?

I think it's fine as then issues like the one you faced won't happen and the user will be able to use various propagators in OrbitPlotter as well..

Should I add it to OrbitPlotter  constructor?

But if we're setting the method per-plot instead of per-frame, what about the number of points? Shouldn't it be set per-plot as well? My concern here is consistency. Four options:

We leave things as they are in this pull request. I think it's inconsistent, unless someone convinces me of the contrary.
We move num_points to each plot call. I think it's bad because it makes the signature too long and, in any case, if someone is so concerned about it they can already sample in any way they want and use plot_trajectory.
We move method to the OrbitPlotter constructor. This prevents the user from selecting the method per-plot. I ask: is this so important?
We do nothing, and tell the user "if you want to change the propagator, just use plot_trajectory".

Thoughts?

I don't have much idea about consistency, but num_points is something that affects the quality of plot. Changing it can either introduce steps in the plot.
I think if seems inconsistent, we can move it to the constructor.
We can leave it too :P
I am not much clear about this.

I just remembered that, in STK, you can indeed select a different propagator for each orbit in one scenario:

So I've changed my mind to accept this. ~@shreyasbapat would you like to change the propagator in the last orbit of the Florence notebook to fix it? (See the errors here http://docs.poliastro.space/en/latest/examples/Catch that asteroid!.html)~ I remember you told me you were on exams, so I'm going to merge this and take care of the rest myself.

Thanks a lot @Juanlu001 . I will be actively up after 1st May Again! Between this, whenever I get time, I will try to do something!


Add warning about <IP_ADDRESS>

Describe in detail the problem you had and how this PR fixes it
If <IP_ADDRESS> is a bad idea, this sets the default to <IP_ADDRESS>
Is there an open issue you can link to?
#440

LGTM

Closed in favor of https://github.com/cdr/code-server/pull/857.


Python-eccodes version numbering changed again, Travis is testing against an old version

Python-eccodes previously changed their version numbering convention which resulted in #3593 being necessary in order to keep Travis using the latest version. Recently, python-eccodes has changed their version numbering convention again (see https://anaconda.org/conda-forge/python-eccodes/files) so that the changes made in #3593 are now causing Travis to not install the latest version. In order to pick up the latest version again, the changes made in #3593 should be reverted.

AFAICT the problem here is not that the numbering system has changed.
It is that they have provided 2 builds for the same "version" (2020.04.0) without incrementing the build number.  Which is simply a thing you must never do in a conda channel !!
E.G. the file "linux-64/python-eccodes-2020.04.0-py36hda16e5c_0.tar.bz2" dates to 2020-05-04 @14:25
And its lib/info/recipe.yaml has
package:
    name: python-eccodes
    version: 2020.04.0
source:
    sha256: b2589c1850d0906d5b22bf699c0977736a704ee35799e4ea618e253332793ac4
    url: https://github.com/ecmwf/eccodes-python/archive/2020.04.0.tar.gz
build:
    number: '0'
    string: py38h8790de6_0

The file "linux-64/python-eccodes-2020.04.0-py38h8790de6_0.tar.bz2" dates to 2020-05-04 @14:29
(5 minutes later !)
And it provides colliding info
package:
    name: python-eccodes
    version: 2020.04.0
source:
    sha256: b2589c1850d0906d5b22bf699c0977736a704ee35799e4ea618e253332793ac4
    url: https://github.com/ecmwf/eccodes-python/archive/2020.04.0.tar.gz
build:
    number: '0'
    string: py36hda16e5c_0

While the 2 identical builds is doubtless a very bad thing to do, we shouldn't be encountering this issue at all while Travis is still pinned to the following:
python-eccodes">=0.9.1, <2"
Version 2020 is most definitely >2!

Version 2020 is most definitely >2!

I don't really understand that aspect.
It also appears, from comparing the two meta.yaml files, that they are nailing tight many dependencies, so one of the above is fixed to python 3.6, and the other 3.8.

Ok, I suspect this could be "what I just said", and not the version spec in travis.yml.
The problem is, we don't integrate with the original environment resolution, but install eccodes in a secondary step.
So, I think the eccodes "meta.yaml" for the python 3.6 version now requires exactly "python=3.6.9",
whereas we are trying to install in the environment we just created, which has 3.6.10.
According to https://travis-ci.org/github/SciTools/iris/jobs/691806720
So it might be installing the earlier one because it has a looser Python version requirement ??
I'll just check that out ...

Update : removing the pin gives segfaults
Maybe we need to pause here, and schedule work to address it at a better time :-(

removing the pin gives segfaults
Until a new iris-grib, which will fix it : SciTools/iris-grib#208

We no longer install eccodes into Travis, so this can be closed


Cilium operator cannot allocate IP addresses when AWS launch new instance types

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

The cilium operator relies on the ec2 instance limit in the process of IP allocation. This information fetched from AWS API on the Cilium operator startup here: https://github.com/cilium/cilium/blob/main/pkg/ipam/allocator/aws/aws.go#L102
On 4 Oct 2023 AWS launched new instance types c7a (blog post)
The Cilium operator that was already running before that launch has no information about limits for c7a types
We are using Karpenter for node provisioning. It periodically fetches information about new instance types and started provisioning c7a instances because it’s cheap  (because a low amount of AWS customers use new instance types right after launch)
Karpenter provisions new nodes and Cilium cannot allocate IP addresses on it

Some cilium operator logs in the process of the incident
--update-ec2-adapter-limit-via-api already set to true and the issue was fixed after the ilium-operator reboot
I guess that cilium-operator should periodically fetch this API for new instance types to prevent such issues
Cilium Version
Client: 1.14.2 a6748946 2023-09-09T20:59:33+00:00 go version go1.20.8 linux/amd64
Daemon: 1.14.2 a6748946 2023-09-09T20:59:33+00:00 go version go1.20.8 linux/amd64
Kernel Version
Linux  5.15.128 #1 SMP Thu Sep 14 21:42:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
Server Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.4-eks-2d98532", GitCommit:"3d90c097c72493c2f1a9dd641e4a22d24d15be68", GitTreeState:"clean", BuildDate:"2023-07-28T16:51:44Z", GoVersion:"go1.20.6", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
n/a
Relevant log output
2023-10-04 17:57:17.292
level=warning msg="Unable to find limits for instance type, consider setting --update-ec2-adapter-limit-via-api=true on the Operator" instance-type=c7a.large subsys=eni

2023-10-05 10:39:24.478
level=warning msg="Instance not found! Please delete corresponding ciliumnode if instance has already been deleted." instanceID=i-0b7fc3f275d818c7f name=ip-10-7-128-51.ec2.internal subsys=ipam

Anything else?
No response
Code of Conduct

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

Thanks for the bug report. I'm glad to see that a restart fixes the issue.
Most likely we should trigger a re-fetch if we don't find the instance type we expect (with some reasonable backoff to prevent pathological cases).

https://aws.amazon.com/ru/about-aws/whats-new/2023/10/amazon-ec2-r7i-instances/
Same issue with new r7i instances.
@squeed Is this issue planned in any way?

@sergeyshevch yes, it should make it's way down the queue and be fixed in time. Feel free to jump on it if you have the cycles.

Not stale


During pre-training, we group the sequences and then split them into constant-length chunks using the cutoff_len parameter, just the same as this document described: https://huggingface.co/learn/nlp-course/chapter7/6#preparing-the-dataset

          During pre-training, we group the sequences and then split them into constant-length chunks using the `cutoff_len` parameter, just the same as this document described: https://huggingface.co/learn/nlp-course/chapter7/6#preparing-the-dataset

Originally posted by @hiyouga in https://github.com/hiyouga/LLaMA-Factory/issues/3145#issuecomment-2039015402
Can you please refer to this in the code? As Huggingface tokenizers use return_overflowing_tokens parameter to split input into chunks.
Couldn't find this in the code.

https://github.com/hiyouga/LLaMA-Factory/blob/b87f8f15194923392d1a1c3d3c617b463cdd8379/src/llmtuner/data/preprocess.py#L33-L41


Separate parse settings into parse and module (data set) specific information.

The .toml files in the io/parsing/io_parse_settings contain file format-specific and module-specific information.
To enable the reuse of the format-specific information, and to reduce redundancies among module-specific information, we can split the .toml files into
For instance the format-specific information for alphapept is:
[mapper]
sequence_naked = "Sequence"
shortname = "Raw file"
protein = "Proteins"
sequence = "Modified sequence"
charge = "Charge"
decoy = "Reverse"
ms1_int_sum_apex_dn = "Intensity"

[general]
contaminant_flag = "Cont_"
decoy_flag = true

[modifications_parser]
"parse_column" = "Modified sequence"
"before_aa" = true
"isalpha" = true
"isupper" = true
"pattern"="([a-z]+)"
"modification_dict" = {"ox" = "Oxidation", "c" = "Carbamidomethyl", "a" = "Acetyl", "decoy" = ""}

,and the data-set (module) specific information is:

[condition_mapper]
LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_01 = "A"
LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_02 = "A"
LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_03 = "A"
LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_01 = "B"
LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_02 = "B"
LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_03 = "B"

[run_mapper]
LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_01 = "Condition_A_Sample_Alpha_01"
LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_02 = "Condition_A_Sample_Alpha_02"
LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_03 = "Condition_A_Sample_Alpha_03"
LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_01 = "Condition_B_Sample_Alpha_01"
LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_02 = "Condition_B_Sample_Alpha_02"
LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_03 = "Condition_B_Sample_Alpha_03"

[species_mapper]
"_YEAST" = "YEAST"
"_ECOLI" = "ECOLI"
"_HUMAN" = "HUMAN"

I am not sure I understand well, I think that even what you call "data-set (module)-specific information" depends on the tool.
For example, for FragPipe, we have this:
[condition_mapper]
"LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_01 Intensity" = "A"
"LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_02 Intensity" = "A"
"LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_03 Intensity" = "A"
"LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_01 Intensity" = "B"
"LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_02 Intensity" = "B"
"LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_03 Intensity" = "B"

[run_mapper]
"LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_01 Intensity" = "Condition_A_Sample_Alpha_01"
"LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_02 Intensity" = "Condition_A_Sample_Alpha_02"
"LFQ_Orbitrap_DDA_Condition_A_Sample_Alpha_03 Intensity" = "Condition_A_Sample_Alpha_03"
"LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_01 Intensity" = "Condition_B_Sample_Alpha_01"
"LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_02 Intensity" = "Condition_B_Sample_Alpha_02"
"LFQ_Orbitrap_DDA_Condition_B_Sample_Alpha_03 Intensity" = "Condition_B_Sample_Alpha_03"

because the column names are not always reported the same way.

As column names and species are reported differently between tools we will keep this replication (for now).


ngx-mask adding extra - for mask 99999.9999-99999

I am using Angular 10.1.5 and ngx-mask 10.0.4.  This is how my control looks like in the html
<input type="text" class="form-control" aria-label="Matter" aria-describedby="Matter" formControlName="matterIDsel" mask="99999.9999-99999" pattern="^[\d]{5}.[\d]{4}-[\d]{5}" [specialCharacters]="['-','.']" [showMaskTyped]="true" [dropSpecialCharacters]="false" />
but on the application when you type the format ends up as follows 99999.9999--9999

ngx-mask isn't something from this repo.


Fix code for Windows

I get an error when printing the banner because it is not decoded with utf8 - this fixes that.

@philippeitis
did it, thanks