Getting Authentication error in azure cloud shell while running terraform commands

Describe the bug
I am getting an authentication error while logging in azure cloud shell to run terraform commands
To reproduce
Steps to reproduce the behavior:

Go to azure cloud shell
enter "az login"
login to the account and set the correct subscription
run terraform command See error

Error:-
WARNING: A Cloud Shell credential problem occurred. When you report the issue with the error below, please mention the hostname 'cc-aa3f5bb3-6fd7bc764f-r2tnt'
ERROR: AADSTS53000: Device is not in required device state: compliant. Conditional Access policy requires a compliant device, and the device is not compliant. The user must enroll their device with an approved MDM provider like Intune.
Trace ID: f1e0d559-c4d0-428e-98d8-d059c9fc6b00
Correlation ID: d64bc76c-627d-4dbb-9eef-42e06b1d0853
Timestamp: 2022-07-19 13:46:27Z
To re-authenticate, please run:
az login --scope https://graph.microsoft.com//.default
WARNING: A Cloud Shell credential problem occurred. When you report the issue with the error below, please mention the hostname 'cc-aa3f5bb3-6fd7bc764f-r2tnt'
ERROR: AADSTS53000: Device is not in required device state: compliant. Conditional Access policy requires a compliant device, and the device is not compliant. The user must enroll their device with an approved MDM provider like Intune.
Trace ID: f1e0d559-c4d0-428e-98d8-d059c9fc6b00
Correlation ID: d64bc76c-627d-4dbb-9eef-42e06b1d0853
Timestamp: 2022-07-19 13:46:27Z
To re-authenticate, please run:
az login --scope https://graph.microsoft.com//.default
Expected behavior
commands should have worked normally.
Additional context
az login --scope https://graph.microsoft.com//.default
logging in using the above command is showing that device needs to be microsoft managed

Likely to be an issue with your corporate Azure AD security policy & Conditional Access.

@bmopati  - This seems an issue with your corporate Security polices based on the error messages. Could you please check and confirm the closure.

@bmopati - As mentioned above, this is likely an error with your tenant. can you specify exactly what Terraform command you are running and at what stage you are being asked to log in?

@bmopati - Were you able to check your organization policies and device compliance?


Error

PS <IP_ADDRESS>
PHP 7.3
ContextErrorException
in modules/blmvuln/src/domain/service/scanner/FilePermissions.php (line 105)
        if (empty($this->insecurePermissionFiles)) {
            return false;
        }
        foreach ($this->insecurePermissionFiles as $path) {
            chmod($path, is_dir($path) ? Config::DEFAULT_MODE_FOLDER : Config::DEFAULT_MODE_FILES);
        }
        return true;
    }

it cannot change the file or folder permission
stack trace

ContextErrorException

Symfony\Component\Debug\Exception\ContextErrorException: Warning: chmod(): Operation not permitted    at modules/blmvuln/src/domain/service/scanner/FilePermissions.php:105   at PrestaShop\Module\BlmVuln\domain\service\scanner\FilePermissions->fix()      (modules/blmvuln/controllers/admin/AdminBlmVulnController.php:74)   at AdminBlmVulnController->fixVulnerabilities()      (modules/blmvuln/controllers/admin/AdminBlmVulnController.php:41)   at AdminBlmVulnController->renderList()      (classes/controller/AdminController.php:2211)   at AdminControllerCore->initContent()      (classes/controller/Controller.php:306)   at ControllerCore->run()      (classes/Dispatcher.php:525)   at DispatcherCore->dispatch()      (zadmin/index.php:93)

The problem is that your server does not allow php to use chmod()

Hello,
Thank you for your answer
It is what I thought and there is  nothing I can do excepted to open writing to anyone, which will be a security problem!
Sincerely


[macOS] Adding Bicep CLI

Description
PR with bicep cli installation for mac OS images. Packages installed via homebrew.
Related issue:
#3461
Check list

[x] Related issue / work item is attached
[x] Tests are written (if applicable)
[x] Documentation is updated (if applicable)
[x] Changes are tested and related VM images are successfully generated

@AlenaSviridenko - looks like the build errors are related to permissions.

/azp run macos1014, macos1015, macos110

@AlenaSviridenko can you please kick off another pipeline run?

/azp run macos1014, macos1015, macos110

@AlenaSviridenko - the build failure looks unrelated to my changes
 vsphere-clone: installer: Error - the package path specified was invalid: '/tmp/visualstudio.weHy/xamarin.android-9.3.0-23.pkg'.

Are we good to merge this PR @AlenaSviridenko?

@MarcusFelling thank you!
just a reminder about Canary tests for Bicep 🙂

@MarcusFelling thank you!
just a reminder about Canary tests for Bicep 🙂

@AlenaSviridenko - added tests in this PR https://github.com/microsoft/azure-pipelines-canary/pull/609


Potentially a wrong variable to print the debug message

It should not be "debug" but "msg"

Hi Javier! Thanks for spotting this one. Looks good. I think it should be merged into devel, not master - what do you think, @themiszamani ?
Have a nice weekend!

Dear @javiquinte and @merretbuurman
Yes the PR should be against the devel instance.
@javiquinte  Could you please proceed with a new PR in devel?

Done in #87 !

it is the same as https://github.com/EUDAT-B2HANDLE/PYHANDLE/pull/87 in devel branch


[IMPROVEMENT] Send credential to process server via request

https://github.com/longhorn/longhorn-instance-manager/pull/105#discussion_r871509816
https://github.com/longhorn/longhorn/issues/3546

Close in favor of https://github.com/longhorn/longhorn/issues/4076.
https://github.com/longhorn/longhorn-manager/pull/1361#issuecomment-1147257498


add ios default-map support overlay images (merge chocky335's branch and add iOS GoogleMaps support)

I open new PR with bug fix https://github.com/airbnb/react-native-maps/pull/1279 .
Original PR is https://github.com/airbnb/react-native-maps/pull/1140 .

supports overlay images both iOS MapKit and GoogleMaps.
fix mirrored presentation of image bug in MapKit.
ready to merge current master

Also it have this bug in MapKit:

Show image just after tap screen, swipe, scale...

Can you give example screenshot of this?

@henrikra Please check following screenshots:

So what is the advantage of this compared to Marker?

This component can draw image with same bounds in any zoom level.
for example, zoom out:

and zoom in:

And someone want to this component: https://github.com/airbnb/react-native-maps/issues/868, https://github.com/airbnb/react-native-maps/issues/400, https://github.com/airbnb/react-native-maps/issues/1212

Also it supports rotation:

Wow interesting. What is some nice use case as an example? :D

This is like Leaflet's L.ImageOverlay.
Nice use case is overlay old map image like this: http://bl.ocks.org/michellechandra/a5c9565214564f68135c
I try this example in react-native-maps.

In this case, I download image locally, but I can use same parameter to set bounds.

Hey henrikra, here's another use-case for this: I am building an application that allows festival goers to view their location relative to the festival map. The festival map is overlaid on Google Maps using this ImageOverlay functionality, and the user's maker/position is overlaid on the festival map.
Attached is a screenshot. I'd love to see this functionality implemented in React Native.
Thanks!

Which feature do you used for overlay? I don't understand though

I also want this feature as official map feature 👍

I tried it works but there is a small bug (guess) on it. When I put an other elements such as Polyline and Marker, image shown as cropped. I tried a lot, it's not a loading error. When I don'tt put any other elements over on it, it works successfully. Any idea?

@isener Are you trying it on the simulator, or on an actual device? When I was using UrlTile on the Simulator, I had the same problem, but on the iPhone it works perfectly... worth a try!

@markmssd Also tried both on Simulator and iPhone 5s device. Same result. May be any other bug caused it happen.

By the way is it possible to us in Android? Can we implement AirMaps functions on .java? Or do we have any other option to make it possible? @smellman

@isener It may possible in Android with GroundOverlay.
https://developers.google.com/maps/documentation/android-api/groundoverlay?hl=en
Sorry, I'm busy my work and getting ready for State of the Map 2017. I will make the time after SOTM.

+1 For this issue - Looks like there is only a minor merge conflict.  Would love to overlay NOAA radar images e.g. https://radar.weather.gov/radar.php?rid=BOX (Raw image here: http://radar.weather.gov/ridge/Conus/RadarImg/northeast_radaronly.gif)
Anything I can do to help here?

How are we able to use this?

Today, I rewrite fix all code for current master and I merge #1586 by hand and hack it.

merge PR #1718
support fetch image from internet
update to new React code (prop-types, React.Component)
merge PR #1586 and fix to support bundle image and fetch image from internet

I just fix document and un-comment for local test.

I want to change ISupportImageReader.java to another name because the name is ugly.
This interface to need to support ImageReader.
I plan refactoring AirMapMarker to use ImageReader because AirMapMarker and AirMapOverlay can share same code.
Does anyone have any ideas or advice?

The master branch for react-native-maps still does not appear to have iOS support for ground overlays, as I get 'Native component for "AirMapOverlay" does not exist' errors when using MapView.Overlay on iOS. Is someone currently working on adding iOS ground overlay support? Is it likely to be added within a few weeks? Is there something I can do to help?

Rotation didn't make it to #1918. 🙁 @smellman @isener

I tried it works but there is a small bug (guess) on it. When I put an other elements such as Polyline and Marker, image shown as cropped. I tried a lot, it's not a loading error. When I don'tt put any other elements over on it, it works successfully. Any idea?

@isener @smellman  Hello, I'm having the same issue where the Overlay is cropped when you zoom in and there is markers on top of it. Did you found any workaround about this bug ? Thanks

I have a 1.2mb image which I need to add as an overlay. When I tried th example with my image, it does not load. Would you happen to know if there is a limit on the image size?


Bug material. The transparent property disables the depth test

Godot version:
version 3.2.3 stable, 3.2.3 mono stable, 3.2.4
Steps to reproduce:
Watch the gif: https://psv4.userapi.com/c536236/u102209357/docs/d38/2feb355e0d33/gX0SvzrosL.gif?extra=LGSgBWBVbk090OkU8-ACZcuIO0rB33XZAR9v0oQwL1cO2ZTqs2A6UsG8Z_tXdhb91gAbdTQHqfcR4sDp2IaAEt_aOJMIJ70D8-N-ttabVHs051TJnZjQqOb556o6nUmpaZh8AAooP95lIK9tGUEHsGwu

Please follow the issue template and provide additional information about your issue.
(You can also now post videos directly to GitHub).

Please follow the issue template and provide additional information about your issue.
(You can also now post videos directly to GitHub).

You can't read title?

I have exactly the same bug.

Please see the documentation for SpatialMaterial depth draw mode. transparent objects are not written to the depth buffer. https://docs.godotengine.org/en/stable/classes/class_spatialmaterial.html#enum-spatialmaterial-depthdrawmode
Also. In the future, all bug reports need to follow the template. Posting a statement in the title is not sufficient.

Please see the documentation for SpatialMaterial depth draw mode. transparent objects are not written to the depth buffer. https://docs.godotengine.org/en/stable/classes/class_spatialmaterial.html#enum-spatialmaterial-depthdrawmode
Also. In the future, all bug reports need to follow the template. Posting a statement in the title is not sufficient.

In this case, how to enable the alpha channel for textures, avoiding such a problem

This is not a support forum, this is an issue tracker. If you need help with setting up your project, please join one of our communities.


Scala 2.12

Scala 2.12 support (thanks @cripsywalrus!)

Could maintainers merge this PR and release new version? Thanks!

@mxl I haven't had a chance to figure out why tests are failing for 2.12 (seems to be a deadlock since tests just hang after completing)

Potentially (but not necessarily) relevant is the fact that the following is printed under 2.12 but not 2.11:
Jan 10, 2017 3:16:20 PM org.jboss.netty.channel.socket.nio.AbstractNioWorkerPool
WARNING: Failed to get all worker threads ready within 10 second(s). Make sure to specify the executor which has more threads than the requested workerCount. If unsure, use Executors.newCachedThreadPool().

See also https://groups.google.com/forum/#!topic/finaglers/rjAKtJVwaS8

FWIW, you do get that warning but you don't get the deadlock if tut is disabled.

In fact, you can look at the generated tut markdown files and see that it is getting stuck the first time it comes across a lambda. Perhaps related to http://scala-lang.org/news/2.12.0#object-initialization-locks-and-lambdas. Putting this in build.sbt will disable tut under 2.12 and prevent the deadlock:
test in Test in `finagle-postgres` := Def.taskDyn {
  (test in Test in `finagle-postgres`).value
  (test in Test in `finagle-postgres-shapeless`).value
  (scalaVersion in docs).value.split(".").toList match {
    case List("2", "11", x) => Def.task { (tut in Compile in docs).value; () }
    case other => Def.task { () }
  }
}.value

@clhodapp could you open a pr against this branch with your tut fix?

@jeremyrsmith Could you make a new release with Scala 2.12 support?

@jeremyrsmith do you have plans to push the new release to maven central? Is there something we could help with? We're waiting for it to release quill for 2.12.

@mxl @fwbrasil Unfortunately it seems to be broken in 2.12 currently. I think upgrading finagle to 6.43.0 might help, but there were also some breaking API changes from 6.41.0 that have to be updated. I probably won't have time to do this until the weekend (any help is welcome though!)

2.12.2 was just released, which may solve the problem @jeremyrsmith @mxl @fwbrasil http://www.scala-lang.org/news/releases-1Q17.html


Windows 11 Explorer Context Menu Support

Description of the new feature / enhancement
Context menu items such as Image Resizer and PowerRename would be much more discoverable if they were available in the new Windows 11 Explorer Context Menu
Scenario when this would be used?
Windows 11 users accessing PowerToys
Supporting information
No response

Duplicate of #13168

Issue is a duplicate
Thank you for your issue! We've linked your report against another issue to centralize the thread.
Thanks for helping us to make PowerToys a better piece of software.

/dup https://github.com/microsoft/PowerToys/issues/13168


Achieve full pub points in the package page in pub.dev

Our package achieved 130/140 pub points which is awesome. 👏
However, to achieve the full score, we need the following actions (updated after losing more points 😅):

[x] Making the repo public. (to have all repo-related links reachable by https://pub.dev)
[x] Ensuring HEAD command to https://moyasar.com/en/ is working as expected.
[x] Making the description in the pubspec.yaml between 60 to 180 characters.
[x] Upgrading the WebView package to the latest version.
[x] Upgrading the Pay package to the latest version.

Mission Accomplished! 🚀 (for now 😆)


add system name label

at the moment when we write we do not add a system name label
that will be useful especially if one wants to filter structures.
something like system_name and infer from the file name will be useful.

Is this effectively bringing back struct_name, since we had the option to manually set that, but otherwise it would default to the file path (or formula as a last resort), or do you mean something else?
Also by label do you mean via Atoms.info?

nope what I mean... infer it from file name and save it in info['system_name']

My point is the inference is part of what struct_name did before, and if we're going to add labels for users, particularly ones they might use to search, you might expect it to be user-definable as well?
I know it was beyond what you were suggesting, but it seemed like where we might end up.
If we only ever want to save the filename stem though, that's fine.

in general the data labeling shall be a sperated issue and once people get more used we do not need it... adding a system_name is minimal


Callback URL giving Client error: POST https://appleid.apple.com/auth/token resulted in a 400 Bad Request response: {"error":"invalid_client"}

Everything works fine except when landing on callback url the post request giving an error.
Client error: POST https://appleid.apple.com/auth/token resulted in a 400 Bad Request response: {"error":"invalid_client"}

This sounds like a configuration issue where your client ID in the app might not be matching the client ID you have registers with your Apple developer account?

If Client ID I have put is Service identifier as per your instruction in the documentation. It is going through normal process when clicking apple icon here https://ignitefiringsystems.com/fireworks/login but after successful authentication it is showing error screen.

Thanks for clarifying. I will see if I can replicate this.

@wamtengineers Make sure that the Client ID in .env and client_secret.rb is the same, otherwise you'll get this error (only on the callback).

Sorry! Could you please elaborate? I did not understand.

Ok I regenerated Client Secret and yes there was a mistake is Client ID parameter. now the error is gone. But I am receiving a null user object. This is debug output.
object(Laravel\Socialite\Two\User)#325 (9) { ["token"]=> string(63) "" ["refreshToken"]=> string(63) "" ["expiresIn"]=> int(3600) ["id"]=> string(44) "000338.4012a42560234b479fb39f7f1c17a3b0.1821" ["nickname"]=> NULL ["name"]=> NULL ["email"]=> NULL ["avatar"]=> NULL ["user"]=> array(8) { ["iss"]=> string(25) "https://appleid.apple.com" ["aud"]=> string(38) "com.ignitefiringsystems.ignitesservice" ["exp"]=> int(1593109908) ["iat"]=> int(1593109308) ["sub"]=> string(44) "000338.4012a42560234b479fb39f7f1c17a3b0.1821" ["at_hash"]=> string(22) "dfVweljsZJMzvYmo5vETig" ["auth_time"]=> int(1593109307) ["nonce_supported"]=> bool(true) } }

``dzsdasdasdasd

Thanks for clarifying. I will see if I can replicate this.

Everything works fine except when landing on callback url the post request giving an error.
Client error: POST https://appleid.apple.com/auth/token resulted in a 400 Bad Request response: {"error":"invalid_client"}

same problem happens to me

Ok I regenerated Client Secret and yes there was a mistake is Client ID parameter. now the error is gone. But I am receiving a null user object. This is debug output.
object(Laravel\Socialite\Two\User)#325 (9) { ["token"]=> string(63) "" ["refreshToken"]=> string(63) "" ["expiresIn"]=> int(3600) ["id"]=> string(44) "000338.4012a42560234b479fb39f7f1c17a3b0.1821" ["nickname"]=> NULL ["name"]=> NULL ["email"]=> NULL ["avatar"]=> NULL ["user"]=> array(8) { ["iss"]=> string(25) "https://appleid.apple.com" ["aud"]=> string(38) "com.ignitefiringsystems.ignitesservice" ["exp"]=> int(1593109908) ["iat"]=> int(1593109308) ["sub"]=> string(44) "000338.4012a42560234b479fb39f7f1c17a3b0.1821" ["at_hash"]=> string(22) "dfVweljsZJMzvYmo5vETig" ["auth_time"]=> int(1593109307) ["nonce_supported"]=> bool(true) } }
I have faced this type of problem . Was it solve ?


Improved nack generator

Description

This PR adds a new nack generator using an algorithm very similar to the one implemented Chrome. Tthe only difference is that Chrome leverages the decoder to have a more consistent PLI generation. RtcpFeedbackGenerationHandler has been slightly modified, because there are some changes between the old and the new interface; for example it sends a PLI when it fails to recover a packet.
We have deployed this new generator few months ago and got very good results.
[X] It needs and includes Unit Tests
Changes in Client or Server public APIs

[] It includes documentation for these changes in /doc.

The current implementation is also based on Chrome's, with some modifications.  It does lack the keyframe and PLI logic, and I think it's a very good addition. However, has a couple of things your proposal lacks has such as limiting the number of retransmissions and the time to send a particular NACK.
I think the best solution would be a combination of both. Would you consider adding the PLI and keyframe logic to RtpNackGenerator.cpp? It would probably involve less work than the opposite as it already uses the style and the helpers we use in the rest of erizo.

At the beginning we changed implementation because with the default one we weren't satisfied with packet recovering. For example at 5% ingress packet loss we saw that the default generator somewhat  worse.
Then we also liked Chrome's approach to limit nacks. Nacks for a packet are retransmitted as long as they are not too old (the nack is still in the queue), and the minimum interval between nack packets is nack_interval
However, I see value in limiting  the number of retransmissions. I think these are two different approach to solve the same problem. I can try to merge the keyframe logic into master, but not really soon. Got myself into a bug of the original generator that made me lose quite a bit of time... I will push the fix asap for this.

I think they can be complementary in some cases and there's value in having both mechanisms in place.
Let me know when/if you start working on it. I can't look into it right now either but I may when I finish the things I'm currently focusing on.


Pylance reports reportUnboundVariable when using walrus operator with conditional expressions and no brackets

Environment data

Language Server version: 2020.9.5
OS and version: Windows 10
Python version: 3.8.5

Expected behaviour
The following snippet leads to a reportUnboundVariable  on the items variable used in the for statement
 if items := result.get("Items", None) if result else None:
    for item in items:
        pass

The following snippets do not generate any reports
 if items := (result.get("Items", None) if result else None):
    for item in items:
        pass

 if items := result.get("Items", None):
    for item in items:
        pass

Actual behaviour
Usiing the walrus operator with a conditional expression which is not enclosed in parentheses leads to a reportUnboundVariable report
Code Snippet / Additional information

Thanks for the bug report.
When I initially added support for the walrus operator, I based my implementation on the draft specification. It appears that there was a change in the final specification that made it legal to use a ternary expression (X if Y else Z) in the right-hand side of the walrus operator.
I've updated the code to support the final spec, and the fix will be in the next version of Pylance.

This issue has been fixed in version 2020.9.6, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/master/CHANGELOG.md#202096-23-september-2020


Optimized code by removing tmp const

Removed tmp const and swapped elements using destructuring

https://github.com/trekhleb/javascript-algorithms/issues/314
I think it is worth solving this problem globally.


Review Distributed Tracing features in the new Service Bus library

When we were working on azure-messaging-eventhubs package, we had a definite set of requirements of how each send request and the different modes of receiving events did tracing. Service Bus is in a similar boat as Event Hubs in terms of tracing needs with the addition of a whole new set of methods for peek, receiving deferred messages, sending scheduled messages etc.
This issue is to review how much of what we did in Event Hubs can be ported over to Service Bus and figure out the gaps.

@hemanttanwar can you please follow up

/cc @rishabjolly


setting return_buffers to true causes errors

I recently updated to the latest version (3.1.0) from 1.0.0. After doing this, exactly every other message that I emit is ignored. I bisected, and the version where this problem starts is 3.0.0. I bisected further and found that the bug was introduced in 73ce3ea81d3dca8105cb36132518166de64dbcdb. removing return_buffers: true from my code solved the problem.
So, maybe it's worth putting a warning in the changelog about this. I would contribute a PR but i don't know the technology well enough to word it correctly.
Thanks for a great project!

I had the same error and return_buffers: true was the problem as you posted. Thanks.

I was unable to reproduce the issue, but I added a note here, what do you think?

Cool
how about to History.md as well


update evernote version

Fixes appNewVersion
hardcodes download url
sudo ./assemble.sh evernote
2023-10-23 13:21:05 : REQ   : evernote : ################## Start Installomator v. 10.5beta, date 2023-10-23
2023-10-23 13:21:05 : INFO  : evernote : ################## Version: 10.5beta
2023-10-23 13:21:05 : INFO  : evernote : ################## Date: 2023-10-23
2023-10-23 13:21:05 : INFO  : evernote : ################## evernote
2023-10-23 13:21:05 : DEBUG : evernote : DEBUG mode 1 enabled.
2023-10-23 13:21:05 : DEBUG : evernote : name=Evernote
2023-10-23 13:21:05 : DEBUG : evernote : appName=Evernote.app
2023-10-23 13:21:05 : DEBUG : evernote : type=dmg
2023-10-23 13:21:05 : DEBUG : evernote : archiveName=
2023-10-23 13:21:05 : DEBUG : evernote : downloadURL=https://mac.desktop.evernote.com/builds/Evernote-latest.dmg
2023-10-23 13:21:05 : DEBUG : evernote : curlOptions=
2023-10-23 13:21:06 : DEBUG : evernote : appNewVersion=10.64.3
2023-10-23 13:21:06 : DEBUG : evernote : appCustomVersion function: Not defined
2023-10-23 13:21:06 : DEBUG : evernote : versionKey=CFBundleShortVersionString
2023-10-23 13:21:06 : DEBUG : evernote : packageID=
2023-10-23 13:21:06 : DEBUG : evernote : pkgName=
2023-10-23 13:21:06 : DEBUG : evernote : choiceChangesXML=
2023-10-23 13:21:06 : DEBUG : evernote : expectedTeamID=Q79WDW8YH9
2023-10-23 13:21:06 : DEBUG : evernote : blockingProcesses=
2023-10-23 13:21:06 : DEBUG : evernote : installerTool=
2023-10-23 13:21:06 : DEBUG : evernote : CLIInstaller=
2023-10-23 13:21:06 : DEBUG : evernote : CLIArguments=
2023-10-23 13:21:06 : DEBUG : evernote : updateTool=
2023-10-23 13:21:06 : DEBUG : evernote : updateToolArguments=
2023-10-23 13:21:06 : DEBUG : evernote : updateToolRunAsCurrentUser=
2023-10-23 13:21:06 : INFO  : evernote : BLOCKING_PROCESS_ACTION=tell_user
2023-10-23 13:21:06 : INFO  : evernote : NOTIFY=success
2023-10-23 13:21:06 : INFO  : evernote : LOGGING=DEBUG
2023-10-23 13:21:06 : INFO  : evernote : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2023-10-23 13:21:06 : INFO  : evernote : Label type: dmg
2023-10-23 13:21:06 : INFO  : evernote : archiveName: Evernote.dmg
2023-10-23 13:21:06 : INFO  : evernote : no blocking processes defined, using Evernote as default
2023-10-23 13:21:06 : DEBUG : evernote : Changing directory to /Users/dnikles/Documents/GitHub/Installomator/build
2023-10-23 13:21:06 : INFO  : evernote : name: Evernote, appName: Evernote.app
2023-10-23 13:21:06.341 mdfind[60945:1062760] [UserQueryParser] Loading keywords and predicates for locale "en_US"
2023-10-23 13:21:06.341 mdfind[60945:1062760] [UserQueryParser] Loading keywords and predicates for locale "en"
2023-10-23 13:21:06.388 mdfind[60945:1062760] Couldn't determine the mapping between prefab keywords and predicates.
2023-10-23 13:21:06 : WARN  : evernote : No previous app found
2023-10-23 13:21:06 : WARN  : evernote : could not find Evernote.app
2023-10-23 13:21:06 : INFO  : evernote : appversion:
2023-10-23 13:21:06 : INFO  : evernote : Latest version of Evernote is 10.64.3
2023-10-23 13:21:06 : INFO  : evernote : Evernote.dmg exists and DEBUG mode 1 enabled, skipping download
2023-10-23 13:21:06 : DEBUG : evernote : DEBUG mode 1, not checking for blocking processes
2023-10-23 13:21:06 : REQ   : evernote : Installing Evernote
2023-10-23 13:21:06 : INFO  : evernote : Mounting /Users/dnikles/Documents/GitHub/Installomator/build/Evernote.dmg
2023-10-23 13:21:06 : DEBUG : evernote : Debugging enabled, dmgmount output was:
End User License Agreement

IMPORTANT NOTICE: THIS IS A LEGAL AGREEMENT BETWEEN EVERNOTE
CORPORATION ("EVERNOTE") AND THE PARTY THAT DOWNLOADS, INSTALLS
AND/OR USES THE SOFTWARE PROVIDED BY EVERNOTE, EACH OF WHOM ACCEPTS
THE TERMS OF THIS AGREEMENT FOR HERSELF, HIMSELF OR ITSELF (AS
APPLICABLE, "LICENSEE"). EVERNOTE SOFTWARE IS LICENSED AND NOT SOLD
AND THE RIGHTS TO USE THE SOFTWARE ARE SET FORTH IN THIS AGREEMENT.
AS DESCRIBED BELOW, USING THE SOFTWARE ALSO OPERATES AS YOUR CONSENT
TO THE TRANSMISSION OF CERTAIN INFORMATION AND DATA DURING ACTIVATION,
USE, OBTAINING SOFTWARE UPDATES AND FOR INTERNET-BASED SERVICES.

CAREFULLY READ THE FOLLOWING TERMS APPLICABLE TO THE LICENSE OF THE
EVERNOTE APPLICATION SOFTWARE AND ANY OTHER SOFTWARE PROVIDED TO
LICENSEE BY EVERNOTE PURSUANT TO WARRANTY, MAINTENANCE AND SUPPORT
OR OTHERWISE, ALL OF WHICH ARE INCLUDED WITHIN THE DEFINITION OF
"SOFTWARE" BELOW.  THESE TERMS AND CONDITIONS SHALL CONSTITUTE A
LEGALLY BINDING AGREEMENT BY AND BETWEEN EVERNOTE AND LICENSEE.
LICENSEE'S ACCEPTANCE ACCORDING TO THE TERMS HEREIN AND/OR LICENSEE'S
INSTALLATION, REPRODUCTION OR USE OF THE SOFTWARE ALSO SIGNIFIES
LICENSEE'S AGREEMENT TO BE LEGALLY BOUND BY THESE TERMS AND CONDITIONS.

PLEASE NOTE THAT YOU NEED NOT AGREE TO BE BOUND BY THIS AGREEMENT.
HOWEVER, IF YOU DO NOT AGREE TO BE LEGALLY BOUND BY THE TERMS AND
CONDITIONS SET FORTH HEREIN, YOU ARE NOT PERMITTED TO INSTALL, COPY,
USE OR TRANSFER THE SOFTWARE AND SHALL NOT HAVE ANY RIGHTS HEREUNDER
AS A "LICENSEE."    NO ADDITIONAL OR
CONTRARY TERMS TO THIS AGREEMENT SHALL APPLY UNLESS AGREED TO IN A
WRITTEN AGREEMENT BETWEEN LICENSEE AND EVERNOTE.

Last Log repeated 4 times
1. DEFINITIONS.

For the purposes of this Agreement, the following definitions
shall apply:

1.1 "Derivative Work" means a work that is based upon or
derived from the Software, such as a revision, modification,
translation, abridgment, condensation or expansion, or any
form in which Software may be recast, transformed or adapted,
which, if prepared without the express written consent of
Evernote, would constitute copyright infringement.

1.2 "Evernote Service" means the Evernote software service
that enables Registered Users to store, organize, search and
share text, documents, images and sounds, and upload and
sync the same through one or more Certified Device(s).

1.3 "Evernote Site" means the Internet site(s) published by
Evernote and applicable to the Software and/or Evernote
Service, as they may change from time to time, including,
without limitation, the site which is currently located at
www.evernote.com.

1.4 "Evernote Terms of Service" means the then applicable
terms and conditions governing the use of the Evernote
Service, as published at the Evernote Site.

1.5 "Individual Computer" means any general-purpose computing
device (desktop, laptop, netbook, tablet, smart phone) that
is operated by one human user at a time for that user's
benefit (e.g., not as a server or in any partition of a
computer system).  Licensee may access the Software operating
on an Individual Computer through a remote device without
any additional license.

1.6 "Object Code" means the form of computer program or
portion thereof that can be executed by a computer without
further modification.

1.7 "Registered User" means any individual who has registered
at the Evernote Site for either a premium account or free
account to use the Evernote Service.

1.8 "Software" means, collectively, (i) that version of the
Evernote application software reflected in text accessed
within the Evernote application software, (ii) all updates,
upgrades, patches, bug fixes and modifications thereto that
may be released by Evernote and made available to Licensee
from time to time, if any, in Object Code form and (iii) all
written information and materials provided to Licensee with
and regarding the Evernote application software, including,
without limitation, in the "About" tab or other settings
information areas within the particular application (which
information may be referred to herein as "Documentation").

1.9 "Source Code" means the human-readable form of the code
and related system documentation for the Software, including
all comments and any procedural code such as job control
language.

1.10 "Supported Device" means the type of Individual Computer
(e.g., iPad) or the Individual Computer running a certain
operating system (e.g., Windows) for which the Software is
designed and offered for use.  Evernote identifies the
Supported Device for the Software by name in connection with
the link through which the Software is made available for
download or on the written software application description
in the materials provided by Evernote with the Software.

2. SOFTWARE LICENSES; GENERAL RESTRICTIONS.

2.1 License Grants.

(a) Subject to the terms and conditions contained
herein, Licensee is hereby granted, and Licensee
accepts, a non-exclusive, non-transferable, fully-paid
license (i) to install and use the Software on one
or more Supported Devices owned or controlled by
Licensee and (ii) during such period of time that
Licensee is a Registered User, use the Software to
enable interaction between the Evernote Service and
the Supported Device on which the Software is installed,
subject to the Evernote Terms of Service.

(b) Subject to the terms and conditions contained
herein, Evernote hereby grants Licensee a non-exclusive,
non-transferable license to make a reasonable number
of copies of the Software without modification for
Licensee's personal use.  Licensee agrees that this
License Agreement applies to all such copies.

(c) Certain computer software components licensed by
one or more third-parties may be provided with the
Software.  Evernote grants Licensee a non-exclusive,
non-transferable, fully-paid license to use one copy
of any third-party software provided by Evernote with
the Software ("Third-Party Software") on the terms
herein and such terms (if any) as may be set forth
in the Documentation (including any additional terms
therein), provided that: TO THE MAXIMUM EXTENT PERMITTED
BY APPLICABLE LAW, ALL THIRD-PARTY SOFTWARE IS PROVIDED
"AS IS" AND WITH ALL FAULTS.  THE PROVISIONS REGARDING
DISCLAIMER OF WARRANTIES, EXCLUSION OF CONSEQUENTIAL
AND CERTAIN OTHER DAMAGES AND LIMITATION OF LIABILITY
IN SECTIONS 6 AND 7 BELOW SHALL APPLY TO SUCH THIRD-PARTY
SOFTWARE.

2.2 General License Restrictions.  Licensee shall only use
the Software for Licensee's personal use on a Supported
Device and, in connection with the Evernote Service, as
permitted by the Evernote Terms of Service.  Licensee shall
not cause or permit the renting, leasing, sublicensing or
selling, or any dissemination or other distribution of copies
of, the Software by any means or in any form to any person,
and shall not permit others to use the Software via a
timesharing, outsourcing, service bureau, application service
provider, managed service provider or similar arrangement.
Licensee may not use the Software in any way that is intended
to circumvent the Evernote Terms of Service or to otherwise
violate any law or regulation.  Licensee shall not use or
distribute as a separate or stand alone executable file,
product or server any Third-Party Software or use such
Third-Party Software except as a component part of the
Software.  Licensee agrees not to, directly or indirectly,
take any action to modify, translate, decompile, reverse
engineer, reverse compile, convert to another programming
language or otherwise attempt to derive Source Code from the
Software or any internal data files generated by the Software,
or perform any similar type of operation on any software or
firmware acquired under this Agreement, in any fashion or
for any purpose whatsoever, except to the extent the foregoing
restriction is expressly prohibited by applicable law
notwithstanding this limitation.  Licensee also acknowledges
and agrees any such works are Derivative Works and acknowledges
that Evernote retains ownership of the copyright in any
Derivative Works and is not granting any right to make, use,
publish or distribute any Derivative Works of the Software.
Licensee shall not modify or delete any Evernote or third-party
proprietary rights notices appearing in the Software, or any
Third-Party Software, and will implement any changes to such
notices, if feasible, that Evernote may reasonably request.
Licensee acknowledges and agrees that the technology manifested
in the operation of the Software constitutes the valuable
trade secrets and know-how of Evernote and its suppliers
and, to the extent Licensee discovers any such trade secrets,
Licensee will not disclose them to any third party.  Licensee
acknowledges and agrees that this Agreement in no way shall
be construed to provide to Licensee any express or implied
license to use or otherwise exploit the Software or any
portion thereof except as specifically set forth in this
Agreement, and all rights not expressly granted to Licensee
are reserved by Evernote.  Licensee has no right to transfer
any interest in or to any Software, except as permitted by
the express terms in this Agreement.  The license granted
herein is neither contingent on the delivery of any future
functionality or features nor dependent on any oral or written
public comments made by Evernote regarding future functionality
or features.

2.3 Additional Terms Applicable to Downloads from Apple.  If
you downloaded the Software from Apple's Mac Store or otherwise
obtained the Software from Apple, the Additional Terms
attached hereto as Exhibit A will also apply.

3. OWNERSHIP OF SOFTWARE.

Evernote's ownership interests in the Software are protected
by United States and other applicable copyright, patent and
other laws and international treaty provisions.  Except for
the limited license rights specifically granted to Licensee
in this Agreement, all rights, title and interests, including
without limitation intellectual property rights, in and to
the Software, including all Derivative Works thereof, (and
all copies thereof and related materials that are produced
or shipped to Licensee under this Agreement), belong to and
shall be retained by Evernote or its suppliers, as applicable.
Licensee acknowledges that the development of the Software
is an ongoing process and that Licensee and other licensees
of the Software benefit from the improvements resulting from
such ongoing development.  In order to facilitate such ongoing
development, Licensee may provide certain suggestions,
documentation, materials and other data to Evernote regarding
the use, improvement or applications of the Software (the
"Contributed Ideas"), and Licensee hereby acknowledges and
agrees that all Contributed Ideas may be used by Evernote
in the development of the Software and/or related products
and services.  Unless specifically provided in a writing
signed by Evernote and Licensee and specifically relating
to the disclosure of any Contributed Ideas, and notwithstanding
any provision in this Agreement to the contrary, Licensee
hereby grants to Evernote the irrevocable, perpetual,
nonexclusive, worldwide, royalty-free right and license to
disclose, use and incorporate the Contributed Ideas in
connection with the development of the Software and/or related
products and services, and the demonstration, display,
license, reproduction, modification and distribution and
sale of the Software and/or related products and services,
without any obligation to provide any accounting or other
reporting.

4. SOFTWARE SUPPORT; INTERACTION WITH EVERNOTE.

4.1 Support of Licensee.  During the term of this Agreement,
Evernote shall use its commercially reasonable efforts to
provide technical support of the Software to Licensee according
to its then applicable support policies.  Such technical
support shall be available by email communication in the
English language, and any other language that may be available
from time to time, during Evernote's regular business hours,
subject to further restrictions, which may be set forth at
the Evernote Site or otherwise published by Evernote and
provided or made available to Licensee.

4.2 Information Sharing and Interactions.  During installation
of the Software and from time to time thereafter when Licensee
uses the Software, the Software will send information about
the Software and the Individual Computer on which the Software
is installed to Evernote.  This information includes the
version of the Software, the language of the Software (e.g.,
English, Japanese, etc.), the Internet protocol address of
the Individual Computer and the Individual Computer's hardware
configuration.  Evernote uses this information to ensure
that Licensee is operating the most current version of the
Software and, if there is a newer release of the Software,
enable Licensee to download and install the current version
appropriate for the Individual Computer.  Depending upon the
settings in the Software, updates to the Software may be
installed automatically without Licensee's separate consent.
In addition, Evernote will use the information provided to
Evernote to enable interaction of the Individual Computer
with the Evernote Service, if Licensee is a Registered User.
Licensee may customize the interactions with Evernote through
the settings found within the Software to limit or, in certain
cases, eliminate such interactions.  Evernote will use digital
certificates to confirm Licensee's identity for the purpose
of enabling standard encryption of content transmitted between
Licensee's Individual Computer and the Evernote Service.  In
an effort to protect the security of such transmissions,
Licensee cannot disable the use of such digital certificates
in connection with the use of the Evernote Service.  By using
the Software, Licensee consents to the sharing of the
information and interactions described herein and, by using
the Software with the Evernote Service, Licensee also consents
to the use of information described in the then current
Evernote Privacy Policy published at the Evernote Site.

5. TERM AND TERMINATION.

This Agreement shall commence on the earlier date of delivery
or download of the Software, shall be confirmed upon and by
the installation of the Software on any computer device and
shall continue for so long as Licensee complies with the
terms herein, subject to termination or expiration in
accordance with the terms provided herein.  This Agreement
shall automatically terminate, without notice, upon any
failure by Licensee to comply with the terms of this Agreement.
Upon the termination of this Agreement, all licenses and
other rights granted to Licensee hereunder shall immediately
terminate.  Notwithstanding any termination of this Agreement,
the provisions of Sections 3 (Ownership of Software), 6.2
(Disclaimer of Warranties), 7 (Limitations on Liability),
11 (General Provisions) and this Section 5 shall survive and
continue to be legally binding upon Licensee and Evernote.

6. SOFTWARE WARRANTY AND DISCLAIMER OF WARRANTIES; SOFTWARE WARRANTY
REMEDY.

6.1 Limited Warranty.  Evernote hereby warrants to Licensee
that the Software will perform substantially in accordance
with the functional description applicable thereto at the
Evernote Site if used in accordance with the terms of this
Agreement and any applicable directions or requirements in
the Documentation.  The foregoing warranty is extended to
the initial Licensee only, is not transferable and shall be
in effect for thirty (30) days immediately following Licensee's
receipt of the Software (the "Software Warranty Period").
Licensee's sole and exclusive remedy and the entire liability
of Evernote and its suppliers and licensors for any breach
of this limited warranty will be, at Evernote's option,
repair or replacement of the Software, if such breach is
reported prior to the expiration of the Warranty Period to
Evernote or the Evernote authorized distributor that supplied
the Software to Licensee (the "Software Warranty Remedy").
Evernote may require that Licensee return or certify the
destruction of all copies of the Software to Evernote or to
the authorized distributor in order to receive the designated
remedy hereunder.  Any replacement Software provided pursuant
to this Section 6.1 will be covered by the warranty in this
Section 6.1 for the remainder of the original Software
Warranty Period or for 30 days from the date on which Licensee
receives such repaired or replacement Software, whichever
is longer.

6.2 Disclaimer of Warranties.

  NO ORAL OR
WRITTEN INFORMATION OR ADVICE GIVEN BY EVERNOTE, ITS
RESELLERS AND/OR ITS OR THEIR AGENTS OR EMPLOYEES,
SHALL CREATE A WARRANTY OR IN ANY WAY INCREASE OR
MODIFY THE SCOPE OF THE WARRANTIES EXPRESSLY SET FORTH
HEREIN.  If Licensee's legal jurisdiction provides
that a certain implied warranty may not be disclaimed,
such implied warranty shall only apply to defects
discovered during the period of the express Software
Warranty Period provided herein.  There is no implied
warranty for defects discovered after the expiration
of such Software Warranty Period.  Some legal
jurisdictions do not allow limitations on how long
an implied warranty lasts, so these limitations may
not apply to Licensee.

(b) EXCEPT AS EXPRESSLY PROVIDED IN SECTION 6.1,
EVERNOTE DOES NOT WARRANT THAT THE SOFTWARE WILL MEET
ALL REQUIREMENTS OF LICENSEE, OR THAT THE OPERATION
OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE,
OR THAT ALL SOFTWARE DEFECTS WILL BE CORRECTED.
  EVERNOTE DOES NOT
WARRANT AND SHALL HAVE NO LIABILITY WITH RESPECT TO
NON-EVERNOTE PRODUCTS OR SERVICES INCLUDING, WITHOUT
LIMITATION, THIRD-PARTY SOFTWARE OR HARDWARE, INTERNET
CONNECTIONS OR CONNECTIVITY OR COMPUTER NETWORKS.

7. LIMITATIONS ON LIABILITY.

7.1 Consequential Damages.  IN NO EVENT SHALL EVERNOTE BE
LIABLE TO LICENSEE FOR ANY LOSS OF OR DAMAGE TO DATA OR OTHER
PERSONAL OR BUSINESS INFORMATION, LOST PROFITS OR USE OF THE
SOFTWARE, OR FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR
CONSEQUENTIAL DAMAGES ARISING OUT OF OR IN CONNECTION WITH
THIS AGREEMENT, INCLUDING THE INSTALLATION, USE OR PERFORMANCE,
OR INABILITY TO USE, THE SOFTWARE, EVEN IF EVERNOTE HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7.2 Limitation.  EVERNOTE PROVIDES THE SOFTWARE AT NO CHARGE
TO LICENSEE.  IN CONSIDERATION FOR, AND AS A FUNDAMENTAL AND
EXPRESS CONDITION OF ENABLING USE OF THE SOFTWARE WITHOUT
CHARGE, AND NOTWITHSTANDING ANY PROVISION IN THIS AGREEMENT
TO THE CONTRARY, EVERNOTE SHALL NOT HAVE ANY LIABILITY FOR
ANY MATTER ARISING OUT OF THE SUBJECT MATTER OF THIS AGREEMENT,
WHETHER IN CONTRACT, TORT OR OTHERWISE, EXCEPT THE SOFTWARE
WARRANTY REMEDY.  THE LIMITATIONS HEREIN SHALL APPLY EVEN
IF THE SOFTWARE WARRANTY REMEDY DOES NOT FULLY COMPENSATE
LICENSEE FOR ANY OR ALL LOSSES, OR IF EVERNOTE KNEW OR SHOULD
HAVE KNOWN ABOUT THE POSSIBILITY OF CONSEQUENTIAL DAMAGES.
SOME LEGAL JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE
ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO LICENSEE IF
LICENSEE RESIDES IN CERTAIN JURISDICTIONS.

8. COMPLIANCE WITH EXPORT LAWS.

Licensee acknowledges that the Software is subject to laws
and regulations of the United States restricting the export
thereof to foreign jurisdictions and agrees to comply with
all applicable United States and foreign international laws,
including, without limitation, the rules and regulations
promulgated from time to time by the Bureau of Export
Administration, United States Department of Commerce.  Without
limiting the foregoing, Licensee shall not download, and if
downloaded shall not install or shall immediately uninstall
and destroy, the Software if Licensee's download, installation
or use of the Software is prohibited under applicable laws.
By installing or using the Software, Licensee agrees to the
foregoing and certifies that it is not located in, under the
control of, or a national or resident of any country or on
any list of countries to which the United States has embargoed
goods or on the United States Treasury Department's list of
Specially Designated Nations or the United States Commerce
Department's Table of Denial Orders.  Licensee shall not
export, re-export, transfer or divert directly or indirectly,
the Software, Documentation or other information or materials
provided hereunder, or the output thereof, to any restricted
place or person for which the United States or any other
relevant jurisdiction requires any export license or other
governmental approval at the time of export without first
obtaining such license or approval.  Evernote has no
responsibility for compliance with such laws and regulations
by Licensee.  Licensee hereby agrees to indemnify and hold
harmless Evernote from and against all claims, losses,
damages, liabilities, costs and expenses, including reasonable
attorneys' fees, to the extent such claims arise out of any
breach of this Section 8.

9. HIGH RISK ACTIVITIES.

The Software is not fault-tolerant for, and is not designed
or intended for use in, hazardous environments requiring
fail-safe performance, including, without limitation, in the
operation of nuclear facilities, aircraft navigation or
communication systems, air traffic control, weapons systems,
direct life-support machines or any other application in
which the failure of the Software could lead directly to
death, personal injury or severe physical or property damage
(collectively, "High Risk Activities").  Evernote expressly
disclaims any express or implied warranty of fitness for
High Risk Activities.

10. UNITED STATES GOVERNMENT.

The Software and Documentation are "commercial computer
software" and "commercial computer software documentation,"
respectively, pursuant to DFAR Section 227.7202 and FAR
Section 12.212, as applicable. Any use, modification,
reproduction, release, performance, display or disclosure
of the Software by the United States Government shall be
governed solely by the terms of this Agreement, except to
the extent expressly permitted by the terms of this Agreement.

11. GENERAL PROVISIONS.

11.1 Entire Agreement; Amendment.  This Agreement constitutes
the entire agreement with regard to the subject matter hereof.
No waiver, consent, modification or change of terms of this
Agreement shall bind any party unless in writing signed by
such party, and then such waiver, consent, modification or
change shall be effective only in the specific instance and
for the specific purpose given.

11.2 Relationship.  No agency, partnership, joint venture
or employment is created between the parties hereto as a
result of this Agreement.  Neither party is authorized to
create any obligation, expressed or implied, on behalf of
the other party, or to exercise any control over the other
party's methods of operation, except as specifically provided
herein.

11.3 Governing Law.  This Agreement shall be governed by and
construed in accordance with the laws of the State of
California, United States of America, without regard to its
choice of law provisions, and shall not be governed by the
provisions of the Convention on Contracts for the International
Sale of Goods.  If you are provided a translation of this
Agreement in a language other than English, such translation
is offered as a convenience and, if there is any conflict
between such translation and the English language version,
the English version of this Agreement shall govern, to the
extent not expressly prohibited by the law in your jurisdiction.
If you have not received the English version of this Agreement,
you may find it at the Evernote Corporation web site
(www.evernote.com) or by contacting Evernote and requesting
a copy.

11.4 Waiver.  The waiver by any party hereto of a breach or
a default of any provision of this Agreement by another party
shall not be construed as a waiver of any succeeding breach
of the same or any other provision, nor shall any delay or
omission on the part of either party to exercise or avail
itself of any right, power or privilege that it has, or may
have hereunder, operate as a waiver of any right, power or
privilege by such party.

11.5 Headings.  Captions and headings contained in this
Agreement have been included for ease of reference and
convenience and shall not be considered in interpreting or
construing this Agreement.

11.6 Assignment; Successors.  The terms and conditions of
this Agreement shall inure to the benefit of and be enforceable
by the parties hereto and their permitted successors and
assigns; provided, that the only permitted successor or
assignee shall be a party that acquires all or substantially
all of the business and assets of Evernote, whether by merger,
sale of assets or otherwise by operation of law.  Licensee
shall not assign this Agreement or any right, interest or
obligation under this Agreement, or in or relating to the
Software.  Any attempted assignment or delegation in
contravention of this provision shall be void and ineffective.

11.7 Notices.  Any notice or communication from one party
to the other required or permitted to be given hereunder
shall be in writing and either personally delivered, sent
by postal service or sent via courier (with evidence of
delivery in any case).  All notices shall be in English and
shall be effective upon actual receipt, irrespective of the
date appearing thereon.  Unless otherwise requested, all
notices to Evernote shall be to the attention of "Compliance."

11.8 Contact.  If you have any questions concerning these
terms and conditions, you may do so at the following address:

Last Log repeated 4 times
Mail:

Evernote Corporation

Del Mar Corporate Plaza

12671 High Bluff Dr, Suite 100

San Diego, CA 92130

Attn: General Counsel

Email:

<EMAIL_ADDRESS>
Phone:

650.216.7700

Last Log repeated 2 times
If you would like to contact Evernote for any other reason relating
to use of the Software, you may do so at this address:
<EMAIL_ADDRESS>
 Acknowledgement: Each party acknowledges that the EULA is concluded
between Evernote and Licensee only, and not with Apple, and Evernote,
not Apple, is solely responsible for the Software and the content
thereof.

2. Scope of License: Each party acknowledges that the license set
forth in Section 2.1(a) of the Agreement is also subject to the
Usage Rules set forth in the Apple Media Services Terms and Conditions.

3. Maintenance and Support:  Each party acknowledges that Apple has
no obligation whatsoever to furnish any maintenance and support
services with respect to the Software.

4. Warranty: In the event of any failure of the Software to conform
to the warranty set forth in Section 6.1 of the Agreement, Licensee
may notify Apple, and Apple will refund the purchase price, if any,
for the Software to Licensee. To the maximum extent permitted by
applicable law, Apple will have no other warranty obligation
whatsoever with respect to the Software, and any other claims,
losses, liabilities, damages, costs or expenses attributable to any
failure to conform to the warranty will be Evernote's sole
responsibility.

5. Product Claims: Each party acknowledges that Evernote, not Apple,
is responsible for addressing any claims of the end-user or any
third party relating to the Software or Licensee's possession and/or
use of that Software, including, but not limited to: (i) product
liability claims; (ii) any claim that the Software fails to conform
to any applicable legal or regulatory requirement; and (iii) claims
arising under consumer protection, privacy, or similar legislation,
including in connection with the Software's use of the HealthKit
and HomeKit frameworks if any.

6. Intellectual Property Rights: Each party acknowledges that, in
the event of any third party claim that the Software or the end-user's
possession and use of that Software infringes that third party's
intellectual property rights, Evernote, not Apple, will be solely
responsible for the investigation, defense, settlement and discharge
of any such intellectual property infringement claim.

7. Legal Compliance. You represent and warrant that (i) you are not
located in a country that is subject to a U.S. Government embargo,
or that has been designated by the U.S. Government as a "terrorist
supporting" country; and (ii) you are not listed on any U.S.
Government list of prohibited or restricted parties.

8. Third Party Terms. You must comply with applicable third party
terms of agreement when using the Software.

9. Third Party Beneficiary: Each party acknowledges and agrees that
Apple, and Apple's subsidiaries, are third party beneficiaries of
the EULA, and that, upon Licensee's acceptance of the terms and
conditions of the EULA, Apple will have the right (and will be
deemed to have accepted the right) to enforce the EULA against
Licensee as a third party beneficiary thereof.

Last Log repeated 12 times
EVERNOTE APPLICATION EULA v04.26.23

Last Log repeated 6 times
expected   CRC32 $5F60CCAC
/dev/disk5          	GUID_partition_scheme
/dev/disk5s1        	Apple_HFS                      	/Volumes/Evernote 10.60.4-universal

2023-10-23 13:21:06 : INFO  : evernote : Mounted: /Volumes/Evernote 10.60.4-universal
2023-10-23 13:21:06 : INFO  : evernote : Verifying: /Volumes/Evernote 10.60.4-universal/Evernote.app
2023-10-23 13:21:06 : DEBUG : evernote : App size: 617M	/Volumes/Evernote 10.60.4-universal/Evernote.app
2023-10-23 13:21:09 : DEBUG : evernote : Debugging enabled, App Verification output was:
/Volumes/Evernote 10.60.4-universal/Evernote.app: accepted
source=Notarized Developer ID
override=security disabled
origin=Developer ID Application: Evernote Corporation (Q79WDW8YH9)

2023-10-23 13:21:09 : INFO  : evernote : Team ID matching: Q79WDW8YH9 (expected: Q79WDW8YH9 )
2023-10-23 13:21:09 : INFO  : evernote : Installing Evernote version 10.60.4 on versionKey CFBundleShortVersionString.
2023-10-23 13:21:09 : INFO  : evernote : App has LSMinimumSystemVersion: 10.13
2023-10-23 13:21:09 : DEBUG : evernote : DEBUG mode 1 enabled, skipping remove, copy and chown steps
2023-10-23 13:21:09 : INFO  : evernote : Finishing...
2023-10-23 13:21:12 : INFO  : evernote : name: Evernote, appName: Evernote.app
2023-10-23 13:21:12.531 mdfind[61059:1063091] [UserQueryParser] Loading keywords and predicates for locale "en_US"
2023-10-23 13:21:12.531 mdfind[61059:1063091] [UserQueryParser] Loading keywords and predicates for locale "en"
2023-10-23 13:21:12.602 mdfind[61059:1063091] Couldn't determine the mapping between prefab keywords and predicates.
2023-10-23 13:21:12 : WARN  : evernote : No previous app found
2023-10-23 13:21:12 : WARN  : evernote : could not find Evernote.app
2023-10-23 13:21:12 : REQ   : evernote : Installed Evernote, version 10.60.4
2023-10-23 13:21:12 : INFO  : evernote : notifying
2023-10-23 13:21:12 : DEBUG : evernote : Unmounting /Volumes/Evernote 10.60.4-universal
2023-10-23 13:21:12 : DEBUG : evernote : Debugging enabled, Unmounting output was:
"disk5" ejected.
2023-10-23 13:21:12 : DEBUG : evernote : DEBUG mode 1, not reopening anything
2023-10-23 13:21:13 : REQ   : evernote : All done!
2023-10-23 13:21:13 : REQ   : evernote : ################## End Installomator, exit code 0

Thank you!


Reproducing when setting 'max_to_keep=0', then the get_checkpoint_state(ckpt_dir).all_model_checkpoint_paths only record the recent 1 model path.

I produced the closed issue #13381, below is my model saving code snippets:
 def do_training(self):
        saver = tf.train.Saver(max_to_keep = 0)

        epoch_size = (os.path.getsize(self.config.data_path) - 1) // self.config.batch_size // self.config.max_length
        resume_ckpt_dir = self.config.resume_ckpt_dir
        with tf.Session() as sess:
            restored = False
            start_epoch = 0
            if resume_ckpt_dir:
                ckpt = tf.train.get_checkpoint_state(resume_ckpt_dir)
                if ckpt and ckpt.model_checkpoint_path:
                    saver.restore(sess, ckpt.model_checkpoint_path)
                    restored = True
                    print ('Restore from %s ... ' % ckpt.model_checkpoint_path )
                    resume_global_step = sess.run(self.model.global_step)
                    start_epoch = resume_global_step // epoch_size
                    print ('Restore global step is %d' % resume_global_step)
            if not restored:
                sess.run(tf.global_variables_initializer())

            writer = tf.summary.FileWriter(self.config.summary_path, sess.graph)

            for epoch in range(start_epoch, start_epoch + self.config.num_epochs):
                gs, compl = self.run_epoch(sess, epoch, writer)

                if epoch % self.config.save_epoch_interval == 0:
                    print ('Save model at global step (%d) / Epoch (%d)' % (gs, epoch))
                    saver.save(sess, os.path.join(self.config.save_ckpt_dir, 'ckpt'), global_step = gs)
                if compl:
                    print ("Val loss has reach the expected entropy within %f" % self.config.comp_stop_width)
                    if (self.config.comp_stop):
                        break
            writer.close()

The I run the follow code:

I saved the model every 39 iterations, but I can only see the most recent 1 in all_model_checkpoint_paths
My versions:

tensorflow-gpu         1.3.0
Ubuntu 16.04.4 LTS

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce
Mobile device

@tensorflowbutler
Have I written custom code: no
OS Platform and Distribution: Ubuntu 16.04.4 LTS
TensorFlow installed from: maybe by pip install tensorflow==1.3.0, I am quite not sure.
TensorFlow version tensorflow-gpu 1.3.0
Bazel version: I don't know how to inspect it, I use a pre-complied pip tensorflow package.
CUDA/cuDNN version: CUDA Version 8.0.61, cuDNN Version 6.0.21
GPU model and memory: GPU 0: GeForce GTX TITAN X (UUID: GPU-005b528e-2b75-4bb2-d828-b518745e9492) and GPU memory is 12204MiB
Exact command to reproduce: see above code
Mobile device: not tested

This looks like an intentional decision to avoid leaking memory if max_to_keep=None, which seems sensible (the Python list would keep growing, and the checkpoint proto would keep growing, probably running into a proto size limit before running out of memory).
We could have the Saver hold on to a large but finite number of previous checkpoints if max_to_keep=None (say, 1000000). But that seems like an even weirder API; it still can't be relied on to give you everything, but it looks more like it should.
So I'm not sure what's actionable here aside from documentation. For the large-but-finite checkpoint proto behavior, I'd suggest setting max_to_keep to some very large number. Does that make sense, @sonack ?

@allenlavoie  Yes! I used very large max_to_keep in practice, but I think the docs should make more explanation here.

Nagging Assignee @allenlavoie: It has been 17 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 33 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.


R9 fix

Hi,
Here's an attempt to handle the new FAST5 files from R9 runs (related to #91 #89)
More testing is likely needed - so comments are welcomed.
-gordon

@nickloman does this address the events data issues with R9 HDF5 files on your end?  I want to integrate a fix for this before dropping the next release.

Merging, as this seems to work well with the R9 reads that @tomsasani tested.


Ubuntu 18.04 - Error: retrieving gpg key timed out.

I'm trying to install nginx, following this tutorial:
https://www.how2shout.com/how-to/install-nginx-php-mysql-wsl-windows-10.html
When I add the ppa this error occours:

/dupe #4486 for lack


Remove commitlint due to failure

@ahmed-taj it looks like the commitlint app is no longer working. Could you check it out and let us know if you plan to fix it?
  2) Failure:
lint test::_apps/commitlint.md#test_0022_host returns 200 [test/lint_test.rb:58]:
Expected 200 response from https://commitlint.herokuapp.com/ping.
Expected: "200"
  Actual: "503"

Same as DEP: https://github.com/probot/probot.github.io/pull/167#issuecomment-382399591

see #171


feat(cactus-connector-fabric): add get transaction receipt by tx id

Authored-by: Eduardo Vasques<EMAIL_ADDRESS>Co-authored-by: Rafael Belchior<EMAIL_ADDRESS>Signed-off-by: Rafael Belchior<EMAIL_ADDRESS>Pull Request Requirements

[x] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
[x] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
[x] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

[x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
[x] Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

Oops, there's also a merge conflict, please let me know if you need help with that

@hyperledger-cacti/cacti-maintainers bump

@RafaelAPB The codegen task was failing but only due to a flake. I'm re-running it now, hopefully we can merge it after this execution.


Fixed #15143 -- Documented how to set the language for the test client.

Added a new section to the testing tools topic documentation, regarding how to set the language for a test client request in a test case.

It looks like the actual ticket is #15143 and not #14143. Please update you commit message to match this PR's title if you are able. Else the commiter will take care of it.

Please uncheck patch needs improvement on the ticket when you manage to find time to address my comments. Thanks again for your contribution.

Updated in https://github.com/django/django/pull/7238.


Package request: Thunderbird Beta and Nightly

Project description
Would like Thunderbird beta and nightly capabilities similar to how Firefox derivatives work with NixOS, using the commands below. If we can get the same implementation but for Thunderbird, that would be a great.
programs.firefox.enable = true;
programs.firefox.package = pkgs.latest.firefox-nightly-bin;

Metadata

homepage URL: https://thunderbird.net
source URL: https://github.com/thunderbird
license: Mozilla Public License (MPL) 2.0.
platforms: Linux

nixpkgs tries to avoid packaging prerelease versions of software as much as possible as the maintenance burden on them is usually much higher because of early bugs and the higher release schedule. Since we already have mutliple variants of firefox there is no need to package beta/nightly.
This might be a good topic for an out of tree repo though.
Edit: eg https://github.com/nix-community/flake-firefox-nightly


[Feature Request] Add support for PCIE throughput and NVLink throughput

Required prerequisites

[X] I have searched the Issue Tracker that this hasn't already been reported. (comment there if it has.)
[X] I have tried the latest version of nvitop in a new isolated virtual environment.

Motivation
It would be nice to be able to monitor throughput between CPU & GPU, and that between different GPUs.
like in Jupyter Lab - GPU dashboards, https://developer.nvidia.com/blog/gpu-dashboards-in-jupyter-lab/
Solution
No response
Alternatives
No response
Additional context
No response

Hi @lungothrin, thanks for raising this. It would be a great feature.
I have added initial results for new query APIs in PR #87.

#87

Now you can implement your own throughput monitor tools based on that if the PR is merged.
However, for the nvitop CLI, there may be no space left to add information for "PCI-e TX/RX" and "NVLink TX/RX". Any thought?


Fix circular import issues

Closes #1185.

@kumaranu: Please try out main once the PR is merged. I think this will fix #1185.


[PLG-2707][WIP] Added the notification tutorial

Harness Developer Pull Request
Added the notification tutorial for CD Pipelines.
What Type of PR is This?

[ ] Issue
[x] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


can not use input type="text"

There is something wrong with my project.
func (a SampleDef) Render() react.Element {
	return react.Div(nil,
		react.Input(&react.InputProps{
			Type: "text",
		}),
	)
}

It seems generated

<input type="text" aria-expanded="false" aria-haspopup="false" aria-labelledby="" class="" placeholder="" role="" value="">

Why so many no use attribute under input tag.
can not input anything and don't work with chrome.

Hi @lijianying10
In order to "bind" a text input, you need to set the Value and OnChange fields on the InputProps.
The simplest example of this (that happens to use a <textarea> but it's identical in approach) is:
https://blog.myitcv.io/gopherjs_examples_sites/markdowneditor/
The relevant bit of source code is:
https://github.com/myitcv/react/blob/57b167914d27bc71eafc5447e5bf54dacb2a22a4/examples/markdowneditor/markdown_editor.go#L50-L54
That explains why you can't input anything.

Why so many no use attribute under input tag.

This is as a result of zero values for those properties. Unlike JavaScript, if, for example, a field is of type bool, Go has a zero value of false (in JavaScript it would be undefined). For a string field the zero value is "". Hence when we come to render elements, you will often see the zero value being "set" in such fields, even if you haven't set a value yourself. There should be no impact/problems as a result, but please say if there is (there are some edge cases where we do need to distinguish a field having been set or not).

I'm going to close this issue for now because I think the markdown example should answer your main query, but please re-open in case you need to.


Solution benchmarking

With the help of BenchmarkDotNet, the user should be able to optionally benchmark a selected problem, with given options. Flexibility does not need to come immediately out of the box, and more issues will be created for additional feature improvements.

Current issues to be dealt with:
Given the structure of the project, benchmarking support is meant to be abstracted away and provide users the convenience of simply calling a method and have all their solutions be benchmarked, all through reflection from ProblemsIndex.
However, so far there is no known solution to this. This feature will probably have to be pushed back until a resolution is discovered, or BDN properly supports this flexibility.

An alternative I'm considering is

source generators
dynamic class creation through System.Reflection.Emit


'Edit in settings.json' does not add default for object-type setting

Issue Type: Bug
My extension's settings.json contributes a configuration property that is object-type, i.e. something like this:
	"contributes": {
		"configuration": {
			"title": "FooBar Servers",
			"properties": {
				"foobar.server": {
					"type": "object",
					"description": "Connection to server",
					"scope": "resource",
					"default": {
							"host": "<IP_ADDRESS>",
							"port": 80
						}
					},
...

The UI-mode settings editor offers me an 'Edit in settings.json' option which adds an entry for foobar.server but doesn't populate the object with its default property values. In contrast, if I manually add foobar.server in JSON-mode settings editor using completion, the defaults are inserted.
VS Code version: Code - Insiders 1.47.0-insider (6efc0b6950cef0dbed0a59c23c656a3f2cfb6403, 2020-06-11T05:46:14.594Z)
OS version: Windows_NT x64 10.0.18363

It does insert a default value but it also triggers suggest in an unexpected location. @sandy081 what's up with that?

Yeah not good given that there are no suggestions which is hard to know. I think better is to avoid prompting suggest for array  or object types.


feat(feedback): adding frontend checkbox to include system info

What does this PR do?
This PR is the follow up of https://github.com/podman-desktop/podman-desktop/pull/10098 (which added the backend support) to collect the system-info of the host machine.
Screenshot / video of UI

demo
https://github.com/user-attachments/assets/1de482ab-1b0b-4d68-8ac6-2ec57f48a526
What issues does this PR fix or reference?
Part of https://github.com/podman-desktop/podman-desktop/issues/9585
How to test this PR?

[x] Tests are covering the bug fix or the new feature

issue(blocking): checkbox is far away from the text

non blocking, follow-up: related to the other PR (follow-up), I guess we should use macOS rather than Darwin when doing the report. It was not obvious when reviewing the other PR but I think it'll be more meaningful to have macOS in the name
placeholder being:

issue:(follow-up or part of this PR)
Having the fields being completed by the link, I see one issue is that for example it doesn't set the version

I'm using .next version but then clicking on the link it selected 1.14.1 so I may open bugs for a wrong version

issue(blocking): checkbox is far away from the text

Fixed ✅

issue:(follow-up or part of this PR)
Having the fields being completed by the link, I see one issue is that for example it doesn't set the version

If it was working I would do as follow up, but this is not possible:
The following url:
https://github.com/podman-desktop/podman-desktop/issues/new?template=bug_report.yml&title=hello&version=1.13.2
Do not allow us to set the version. I opened an issue on the GitHub report, the selected value is always the latest...
We could fix that by changing the dropdown to a text input..

it seems the vertical align of the checkbox and the text is not the same as in other part of the UI, maybe needs to be checked before the merge

it seems the vertical align of the checkbox and the text is not the same as in other part of the UI, maybe needs to be checked before the merge

This seems to originate inside the Checkbox component
https://github.com/podman-desktop/podman-desktop/blob/516922e2ef043c208d55e9921edda79f7798aa20/packages/ui/src/lib/checkbox/Checkbox.svelte#L29

Not something that can be addressed in this PR.


Try extension alignment if seed appears to be ungapped

Btw, what does strobealign currently do when the region with the NAM has the same length on the query and the reference and Hamming distance of the NAM region is high?
Do we fully realign such cases with SSW? If so, an optimization would be to run ksw on the ends only. I remember we have discussed similar scenarios when we tried out partitioning the alignments and use WFA2 but I don't remember the conclusions.
Clarification: I meant when Hamming distance is high -- possibly because regions outside the NAM region do not fit (e.g. indels). Then it might be inefficient to realign the whole read. One approach would be to try hamming of the NAM hit only, then extension of the ends.
Originally posted by @ksahlin in https://github.com/ksahlin/strobealign/issues/357#issuecomment-1834197665

Yes, we fully align. The only case in which we do not fully align is when the NAM on the query and the reference have the same length and the hamming distance is low (<5% differences).


async chat event

This is a continuation for the closes issue https://github.com/DenizenScript/Denizen-For-Bukkit/issues/1762

🤔

What is this issue post meant to be
Denizen strongly discourages the async event as it is dangerous.
Other plugins might use the async event without an option to switch to sync if they were written by dumb people.
If you want a 100% Denizen compatible guaranteed Discord bot, use https://github.com/DenizenScript/dDiscordBot


ci: force remove mono from windows builds

Fixes the win64 CI.
After a bionic update on 2022/06/03, Github Actions images have a mono-runtime installation that takes precedence over wine, which we need for running the tests.
This PR removes mono-runtime from both windows CI jobs if it exists, so that it doesn't bother us anymore in any way thinkable. We do not need mono there, as we do not .net. Although the issue only manifested on x86_64-w64-mingw32 builds, this also removes it from the i686-w64-mingw32 build as a precaution.

@patricklodder This seems like a maintenance task to me; I'm comfortable merging before the standard 24 hour period in that case. Per policy, we should mark it as such before taking the exception.

Per policy, we should mark it as such before taking the exception.

Right! Created label "urgent" and assigned it 😁

Merging with appropriate urgency!
If anyone has subsequent comments on this, post-merge, please file an issue or comment here and we'll make sure it gets addressed before we finalize the 1.14.6 release.


Response Model with Map can not be showed the details in response

Hi my response model is generic and has a column  'errorInfo' which type is Map,then swagger can not show the response details,If i change the type from Map to other type (String or other Class),then it works.(swagger.version=2.9.2,springboot.version=2.2.4.RELEASE)
@Data
@NoArgsConstructor
@ApiModel("Standard response model")
public class ApiResult<T> implements Serializable {

    @ApiModelProperty(value = "success or fail")
    private Boolean success;

    @ApiModelProperty(value = "result status", reference = "IResultMsg", required = true)
    private Integer status;

    @ApiModelProperty(value = "result message", required = true)
    private String message;

    @ApiModelProperty(value = "response data")
    private T data;

    @ApiModelProperty(value = "error info")
    private Map errorInfo;

    @ApiModelProperty(value = "error message")
    private String errorMessage;

This should be fixed in the latest 3.0.0 version releasing shortly


Upgrade markdown-it-py to 3.0.0

[x] I've checked docs and closed issues for possible solutions.
[x] I can't find my issue in the FAQ.

Describe the bug
In one of my projects I use Bandit, which uses this project, however currently Github's dependabot has created a PR in my project to upgrade from markdown-it-py from 2.2.0 to 3.0.0, which is currently failing with the following error.
...
ERROR: Cannot install -r config/requirements/dev_lock.txt (line 1349) and markdown-it-py==3.0.0 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

The conflict is caused by:
    The user requested markdown-it-py==3.0.0
    rich 13.4.1 depends on markdown-it-py<3.0.0 and >=2.2.0

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

Error: Process completed with exit code 1.

Please loosen the range for markdown-it-py so that markdown-it-py can be upgraded.

Done in 13.4.2


Make configuration class

No reason to pass around so many parameters or read them from config file. There should be a morfJobConfig class (or something similar) which contains everything needed to run the job. Then, there can be some kind of constructor function (very similar to get_config_properties()) which will read the config file and return a single morfJobConfig instance.

resolved with merge of jobconfig-train branch onto master.


errant double quote

super minor typo

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Added some catch safeguards + update .env.example

Fixes

Attempted fix for Signup client route crash

Proposed Changes

Added some catch safeguards for the Profile error snackbar
Updated .env.example to ensure equivalence between local repos

The issue was determined to be missing environment variable in the other workspaces; Travis may write some additional server checks to see if the variable exists. Closing PR.


Add CPP docs to SDK build

Part of https://github.com/dwavesystems/dwave-ocean-sdk/pull/153

Codecov Report

Merging #27 (7bb3a1a) into main (7862154) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #27   +/-   ##
=======================================
  Coverage   95.77%   95.77%
=======================================
  Files          15       15
  Lines         473      473
=======================================
  Hits          453      453
  Misses         20       20

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 7862154...7bb3a1a. Read the comment docs.


Fixes property revert after saving instanced scene

This PR fixes #33611.
Check get_scene_inherited_state for the root node and get_scene_instance_state for others, just like other places.
Tested on the current master (825ab3b) and 3.2 branch.

Thanks!

Cherry-picked for 3.2.4.


[pre-sve] TC-LO-2.1 SupportedLocales and ActiveLocale issues

Problem
Test case ID: TC-LO-2.1
SHA: https://github.com/project-chip/connectedhomeip/commit/425f1fb916ca154deeb75cd82cd5196778aba152
Platform: Ameba all-clusters-app
Chip-tool platform: Raspberry Pi
Ameba is using the DeviceInfoProviderImpl in examples/providers

./chip-tool localizationconfiguration read supported-locales 1234 0 Reading supported locales returns UNSUPPORTED_ATTRIBUTE, expected to be success.
./chip-tool localizationconfiguration read active-locale 1234 0 Reading active locale returns Wrong TLV type, expected to be success
./chip-tool localizationconfiguration write active-locale fr-FR 1234 0 Writing active locale returns UNSUPPORTED_WRITE, expected to be CONSTRAINT_ERROR or success

TC-LO-2.1-chip-tool.txt

Is this a platform specific issue? Seems like the DeviceInfoProviderImpl in examples/providers that ameba is using do support these read/write attributes.

I have checked the ZAP file, supported-locales and active-locale attributes are enabled.

They are enabled as callbacks. You need to add support for DeviceInfoProviderImpl.
I believe for ameba, because a separate build script is used, those files could not be included in the app main. Your app main has to call the set provider api. See examples in:
https://github.com/project-chip/connectedhomeip/blob/master/examples/all-clusters-app/nrfconnect/main/AppTask.cpp#L155
or
https://github.com/project-chip/connectedhomeip/blob/master/examples/lock-app/efr32/src/main.cpp#L49
Generally code should look like:
gExampleDeviceInfoProvider.SetStorageDelegate(&Server::GetInstance().GetPersistentStorage());
chip::DeviceLayer::SetDeviceInfoProvider(&gExampleDeviceInfoProvider);

This is platform specific: every platform example should call provides in main. We have implemented some examples (notably linux/mac, nrf and some efr) however we have not updated every example since build systems vary. Ameba build system is the most different one.

Hi @andy31415, apologies I did not explain it clearly. In my local branch, I have included the DeviceInfoProviderImpl in Ameba's build and have called SetDeviceInfoProvider in main. I have not PR-ed this change.
In fact, reading supported calendar types is successful, which proves that the DeviceInfoProviderImpl is set. I am not sure why reading/writing locales fails.

@woody-apple can you please re-review this again.
When TH sends ./chip-tool localizationconfiguration read supported-locales 1234 0, DUT received a read request for cluster 0x2B, attributeID 2. However, supported-locales is attributeID 1.
Similarly for ./chip-tool localizationconfiguration read active-locale 1234 0, DUT received read request for cluster 0x2B, attributeID 1. Active-locale should be attributeID 0.
See below log for reference.
TC-LO-2.1-DUT.txt

Does this happen on other platforms?
If this happens on some other platforms (I believe CSG tests nrf and rpi at least) we should validate and then it could be moved to general issue.
Regarding the spec I agree we have:

LocalizationConfiguration cluster id is 0x002B
ActiveLocale is a mandatory string attribute with id 0x0000
SupportedLocales is a mandatory list of strings with id 0x0001

If chip tool is asking for some different ids, it sounds like some sort of chip-tool bug (likely off-by-one). Would need confirmation this is the case on more than one platform (should be ... since chip-tool runs on linux and is common)

@pankore please re-test on different platforms and update this issue with your findings. Thanks.

Ram the following test script on nrf-nrf52840dk-light on master
#!/usr/bin/env bash

set -ex

function finish {
  echo "STATUS: $?"
}

trap finish EXIT

export NODEID=$RANDOM

export THREAD_CRED=hex:<THREAD_CRED_HERE>
export CHIP_TOOL="$HOME/devel/connectedhomeip/out/linux-x64-chip-tool/chip-tool"

log_file="run_log_$(date +'%Y-%m-%d_%H-%M-%S').txt"
rm -f /tmp/chip_*

echo "NODE ID USED: $NODEID" | tee $log_file

echo "=============================================================" >>$log_file
echo $CHIP_TOOL pairing ble-thread $NODEID $THREAD_CRED 20202021 3840 | tee -a $log_file
$CHIP_TOOL pairing ble-thread $NODEID $THREAD_CRED 20202021 3840 >>$log_file 2>&1

echo "=============================================================" >>$log_file
echo $CHIP_TOOL localizationconfiguration read active-locale $NODEID 0 | tee -a $log_file
$CHIP_TOOL localizationconfiguration read active-locale $NODEID 0  2>&1 | tee -a $log_file | grep 'ReportDataMessage =' -A 25

echo "=============================================================" >>$log_file
echo $CHIP_TOOL localizationconfiguration read supported-locales $NODEID 0 | tee -a $log_file
$CHIP_TOOL localizationconfiguration read supported-locales $NODEID 0  2>&1 | tee -a $log_file | grep 'ReportDataMessage =' -A 25

Logs contained
2190 [1654791355.680311][2958009:2958016] CHIP:TOO: Sending ReadAttribute to:
2191 [1654791355.680313][2958009:2958016] CHIP:TOO:  cluster 0x0000_002B, attribute: 0x0000_0000, endpoint 0
...
[1654791357.167104][2958042:2958049] CHIP:TOO: Sending ReadAttribute to:
[1654791357.167106][2958042:2958049] CHIP:TOO:  cluster 0x0000_002B, attribute: 0x0000_0001, endpoint 0

so I believe attribute ids seem spec-compilant

Data also seems available: logs say:
2903 [1654791357.343703][2958042:2958049] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_002B Attribute 0x0000_0001 DataVersion:<PHONE_NUMBER>
2904 [1654791357.343728][2958042:2958049] CHIP:TOO:   SupportedLocales: 8 entries
2905 [1654791357.343734][2958042:2958049] CHIP:TOO:     [1]: en-US
2906 [1654791357.343737][2958042:2958049] CHIP:TOO:     [2]: de-DE
2907 [1654791357.343739][2958042:2958049] CHIP:TOO:     [3]: fr-FR
2908 [1654791357.343742][2958042:2958049] CHIP:TOO:     [4]: en-GB
2909 [1654791357.343744][2958042:2958049] CHIP:TOO:     [5]: es-ES
2910 [1654791357.343747][2958042:2958049] CHIP:TOO:     [6]: zh-CN
2911 [1654791357.343749][2958042:2958049] CHIP:TOO:     [7]: it-IT
2912 [1654791357.343752][2958042:2958049] CHIP:TOO:     [8]: ja-JP

Tested on ToT's chip-tool with the same DUT firmware, got the same result as @andy31415 so it might be chip-tool's issue. Closing this issue as this is solved in ToT


how to run python project

my project run as
python3 src -id 11
then how to run using condon？

We do not yet support running directories with __main__.py. Also, running python project as-is probably won't work; please see https://docs.exaloop.io/codon/general/faq and https://docs.exaloop.io/codon/general/faq for details.


Work with Spree 4 & Rails 6

I'm sorry for sending this huge pull request. :( I originally just wanted to make this excellent gem work first, and didn't think much of what I have done. So, the commits look a little messy.)
However, I believe my works might help somebody. Because there are many good pull requests, and I just organize some of them to make this gem work in a shot time! Since I'm gonna move forward to do other things, I hope someone could help me finish the rest of the things.
What has been done in this pull request?

Update & fix configuration to the latest Spree convention
Rewrite a small piece of coffee code in javascript (since coffee-script is not a default gem for most of new Rails app)
Add UTF-8 support (I basically work on Chinese, but other languages like Japanese should work as well)
Remove deprecated methods
Fix most of the tests (I leave features test because I'm not familiar with Capabyra.)
Update UI to the latest backend theme
Fix rails 6 zeitwerk problem
Update prawn-rails to ~> 1
Remove the store path (local storage doesn't fit for most of the production cases. But, I'm working on saving files to Active Storage, it can help both on development and production. It might be in the next pull request)

If this PR looks useful to you, let me know if I can do anything to make this pull request to be merged.
Thank you.

Hey @imgarylai & @voleoo could you rebase this pull request? Thank you both for you excellent work so far! 💪

@damianlegawiec Yeah no problem.

@damianlegawiec I think I will create some small PRs to finish reset of the job in this PR because I changed too many things in this PR and some of them might not be necessary.
Let me close this issue first.


lxml==4.1.1 fails to build on macos with python3

Hey,
first of all thanks a lot for this project, very much appreciated.
I favor of changing to python3 I reworked my install and update script. Unfortunately when using on macos 10.13.6 with latest homebrew python 3.7.0 the package lxml==4.1.1 fails to build.
clang -bundle -undefined dynamic_lookup build/temp.macosx-10.13-x86_64-3.7/src/lxml/etree.o -L/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/lib -L/usr/local/lib -L/usr/local/opt/openssl/lib -L/usr/local/opt/sqlite/lib -lxslt -lexslt -lxml2 -lz -lm -o build/lib.macosx-10.13-x86_64-3.7/lxml/etree.cpython-37m-darwin.so
  ld: file not found: /usr/lib/system/libsystem_containermanager.dylib for architecture x86_64
  clang: error: linker command failed with exit code 1 (use -v to see invocation)
  error: command 'clang' failed with exit status 1

  ----------------------------------------
  Failed building wheel for lxml

When I change it to lxml>=4.1.1 in requirements.txt it pulls lxml 4.2.4 and everything seems to work and build nicely.
I don`t know if it is just the requirements.txt file that has to be updated or if something else is needed.
Thanks for fixing in advance.
Kind regards

Hi @tiiiecherle and welcome here !
Thanks for pointing out, I will update the requirements.txt along with my next PR regarding the python3only branch.
Have a nice day/night.

Thanks a lot.
Have a nice weekend ;)

Oh and one more thing... I put together a script that installs an update-script and and a launchd service that launches every morning and on every reboot to check if x days (in my case 4 days) are over and updates if true.
https://github.com/tiiiecherle/osx_install_config/blob/master/09_launchd/9b_hosts_file/install_hosts_and_launchdservice.sh
Just be sure when installing, that the directory structure from install script to update script are kept as is is in the repo.
The service and the update file are here:
https://github.com/tiiiecherle/osx_install_config/tree/master/09_launchd/9b_hosts_file/launchd_and_script
Just in case it helps anyone ;)

Those are neat scripts, @tiiiecherle.
I would be happy to entertain a PR that mentions these scripts in the Interesting Applications section of the readme_template.md file.
Closing this issue now.  Thanks Nissar @funilrys for handling this.

Those are neat scripts, @tiiiecherle.
I would be happy to entertain a PR that mentions these scripts in the Interesting Applications section of the readme_template.md file.

Thanks, sure.
And perhaps the change to the requirements.txt file should also go to the master branch as it has two requirements files and the issue affects the one for python3. Thanks


Extension development - Syntax highlight only works on debug mode

Issue
I'm developing an extension and when I use the "Run Extension" the syntax highlight works as expected for .fql files however, when I published the extension to marketplace and installed locally it is not working.
Steps to reproduce

Install the extension FaunaDB
Execute CMD + P > Create Query
The code is not highlighted

Although, if you clone the extension repo https://github.com/fauna/vscode and try to debug the extension you will see the same steps will reproduce a diff behaviour in the new VSCode window. The code will have the correct syntax highlight.
On debug mode:

Installing from marketplace

Hi @BrunoQuaresma ,
Do you see any error message in console, (opened via  Toggle Developer Tools)? Also, you could try to install the extension locally (.vsix File), created using vsce package.
I have experienced similar issues myself before, for two different reasons: general failure running the command and wrong use of dependencies described in package.json
Hope this helps

Thanks @alefragnani.
I found the issue. It was because my syntaxes folder was inside of ./src which is ignored on .vscodeignore. Although I think the debug mode + packaged version should behaves in the same way.

That’s great you’ve found the issue!
I’ve looked your repo and noted ./src in .vscodeignore but your syntaxes folder was already on the root folder so, I eliminated that from the alternatives 😄


[KeyVault] Do Not Merge: Review to publish Key Vault preview packages from KvDevPsJson

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@schaabs please reopen this PR once you are ready to push changes to this PR. I can help you reopen this PR. Closing it for now.

@shahabhijeet  I've update the package release notes for all packages PTAL

@schaabs please reopen this PR when it's ready to be merged.


Team2 Review: Ambiguous Functional Requirement

Requirement CG3 in section 2.2.1 reads: "The system shall allow the user to set the size of the game room." It is not made clear what determines the "size" of the game room (e.g. number of players, length of game, etc.). It is also not made clear in the rationale what makes a game smaller or bigger.

@samm82

Completed in commit ID: d9d136da73141de01d320198e16eb7254ec3ecda


[Bug] AI generated title is not used when sharing a chat

The AI generated title is used in the sidebar, but when sharing it just reuses the question. In my opinion it should use the AI generated title by default.

Amazing. Thank you so much for all your efforts. I love the new AI title feature.

This issue has been resolved in version 1.2.4. I'm closing this, but feel free to reopen it if you still face the issue