Unusual behavior updating region

Hi everyone,
I'm having a unusual issue using react-native-maps on iOS on a real device (iPhone 6S) (React native maps 0.4.0, RN 0.25.1), i'm controlling the region with redux. I just want to set the region where the user is located. To do that, I used a function called when the component is loaded :
navigator.geolocation.getCurrentPosition(
         (region) => {
           const regionMod =
             {
               latitude: region.coords.latitude,
               longitude: region.coords.longitude,
               latitudeDelta: 0.1,
               longitudeDelta: 0.1
             }
           this.props.onRegionChange(regionMod)
         },
         (error) => alert(error.message), // eslint-disable-line
         { enableHighAccuracy: true, timeout: 20000, maximumAge: 1000 }
       )

And I connected my component using redux :
<MapView
          region={ this.props.region }
          onRegionChange={ this.onRegionChange }
          showsUserLocation
 />

...

function mapStateToProps(state) {
  console.log(state.region)
  return {
    region: state.region,
  }
}

function mapDispatchToProps(dispatch) {
  return {
    onRegionChange: (region) => dispatch(moveToLocation(region))
  }
}

const MapRender = connect(
  mapStateToProps,
  mapDispatchToProps,
)(Map)

export default MapRender

Action.js :
const initialMapInfo = { latitude: 0.0, longitude: 0.0, latitudeDelta: 130.0, longitudeDelta: 130.0 }

export function region(state = initialMapInfo, action) {
  console.log(action.type)
  switch (action.type) {
  case 'MOVE_TO_LOCATION':
    return action.region
  default:
    return state
  }
}

When I switch from my "home" tab to my "map" tab, the comportement of the state is really strange :

So the map change region multiple times at wrong coordinates (and always at the same region coords!) before being at the good coordinates.
Here is a gif to see what happened :

If someone know how I can solve my problem..
Thank's :)

Is the SF location set anywhere in the code, could this be hardcoded somewhere ? Pretty strange...also do you know why the warning is showing up, it seems you might have a wrong Marker instantiated.

I managed to solve the warnings, it was because I didn't put the propTypes of my coordinate.latitude in my code.
The SF location coordinates is never use in my code so I really don't know what is the problem here..

Can you try without the user location? Then try without markers? See what is the thing that triggers the  map change maybe putting a debugger in the reducer and look at the stacktrace.
Sent from my iPhone

On Jun 1, 2016, at 2:44 AM, Kevin Gallet<EMAIL_ADDRESS>wrote:
I managed to solve the warnings, it was because I didn't put the propTypes of my coordinate.latitude in my code.
The SF location coordinates is never use in my code so I really don't know what is the problem here..
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I tried without user location and without markers, the map is directly set to the good location, but it seems that the state still receive wrong location.

I can't really help you without seeing your code, but maybe you can log the backtrace too ?
console.log((new Error()).stack)

I found the error was because I was using an api which return me undefined.

The san francisco bug is happening to me too.
  render() {
    const { longitude, latitude } = this.props;
    console.log('Region: ', this.state.region);
    return (
      <View style={styles.fill}>
        <MapView
          ref={r => this.map = r}
          style={styles.fill}
          region={this.state.region}
          onRegionChange={this.onRegionChange}
          showsCompass={false}
          customMapStyle={mapStyle}
        >

  onRegionChange = region => {
    console.log('Region Changing: ', region);
    if (region.longitudeDelta > 80 && !this.state.iosInitialJumpBugHasHappened) {
      return this.setState({
        iosInitialJumpBugHasHappened: true
      });
    }
    this.setState({
      region
    });
  };

This works fine on android, but it's jumping to this exact region (San Francisco) as well on iOS.
With those console logs my output is as follows, without any touch actions happening on the map.

index.ios.bundle:92324 Region:  {latitude: 43.25156385754565, longitude: -79.9405345424435, latitudeDelta: 0.03, longitudeDelta: 0.03}
index.ios.bundle:92272 Region Changing:  {longitudeDelta: 0.03816598513895997, latitudeDelta: 0.048178881346807145, longitude: -122.40971999999998, latitude: 37.787685747888986}
index.ios.bundle:92324 Region:  {longitudeDelta: 0.03816598513895997, latitudeDelta: 0.048178881346807145, longitude: -122.40971999999998, latitude: 37.787685747888986}
index.ios.bundle:92272 Region Changing:  {longitudeDelta: 93.95507800000016, latitudeDelta: 87.41089927136262, longitude: -96.45996100000004, latitude: 56.185986}
index.ios.bundle:92324 Region:  {longitudeDelta: 0.03816598513895997, latitudeDelta: 0.048178881346807145, longitude: -122.40971999999998, latitude: 37.787685747888986}

It seems your map is trying to update the region while the map is mounting, to sanfrancisco. My current solution to this is for IOS only, i'm ignoring region changes for the first second the component is mounted. This works, but would like to know why your map loves san francisco so much =) It's the exact same region you're using in all your demo videos on the README.MD.

@KGALLET Go to simulator menu > Debug > Location. If its set to Custom Location, that's where the coordinates for SF are coming from. Its been hardcoded by apple already as a placeholder location in the simulator.

Using a MapView while controlling the region as state is rerendered continuously. I want to change the region based on state changes.
How to stop rerender the region?


Fix collisions: Re-attach BlockingLayer reference to Enemy and Player prefabs

Fixes the dropped references from the great reconditioning of #38.
Note to selves: Unity editor will drop attached references to prefab properties when renamed apparently.

Can confirm, am unable to run over penguins.


Unable to add a new team to a stack

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
After creating a team, I can't assignate it to a stack
Expected Behavior
I expected to see my team directly
Actual Behavior
The team doesn't appear in stack restrited option (for team)
Steps to Reproduce
Create a new team, put people inside.
Go to stack
Click on a stack
Put it as restricted with team
Portainer logs or screenshots
https://imgur.com/a/XnqvDCi
Portainer version
2.21.1
Portainer Edition
Community Edition (CE)
Platform and Version
Docker Swarm 27.1.2
OS and Architecture
Ubuntu 24.04
Browser
Firefox
What command did you use to deploy Portainer?
No response
Additional Information
No response

it doesn't work on portainer v2.21.4 too


Migrate to Scala 3

Scala 3 is out for quite some time, we need to migrate to Scala 3 to be up to date and to use some of the features.

Currently not possible to migrate to Scala 3.x.x because some of the libraries that I use are depending on some macros which are not yet ported to Scala 3.x. Here is a sample run of the scala3 migration helper sbt plugin that shows what the blockers are:
[plant-simulator] $ migrate-libs root
[info]
[info]
[info] Starting to migrate libDependencies for root
[info]
[info] X             : Cannot be updated to scala 3
[info] Valid         : Already a valid version for Scala 3
[info] To be updated : Need to be updated to the following version
[info]
[info] com.typesafe.play:play-json:2.9.3                           -> X : Contains Macros and is not yet published for 3.0.0
[info] com.typesafe.slick:slick:3.4.1                              -> X : Contains Macros and is not yet published for 3.0.0
[info] com.typesafe.scala-logging:scala-logging:3.9.5              -> X : Contains Macros and is not yet published for 3.0.0
[info] org.wartremover:wartremover:2.4.21:plugin->default(compile) -> X : Scala 2 compiler plugins are not supported in scala 3.0.0. You need to find an alternative
[info] io.dropwizard.metrics:metrics-jvm:4.2.13                    -> Valid
[info] com.h2database:h2:1.4.186                                   -> Valid
[info] org.awaitility:awaitility:4.2.0:test                        -> Valid
[info] io.dropwizard.metrics:metrics-core:4.2.13                   -> Valid
[info] com.typesafe:config:1.4.2                                   -> Valid
[info] mysql:mysql-connector-java:8.0.31                           -> Valid
[info] com.typesafe.play:twirl-api:1.5.1                           -> "com.typesafe.play" % "twirl-api_2.13" % "1.5.1"
[info] com.typesafe.akka:akka-protobuf-v3:2.6.20:test              -> "com.typesafe.akka" % "akka-protobuf-v3_2.13" % "2.6.20" % "test"
[info] com.typesafe.play:play-akka-http-server:2.8.16              -> "com.typesafe.play" % "play-akka-http-server_2.13" % "2.8.16"
[info] com.typesafe.play:play-json-joda:2.9.3                      -> "com.typesafe.play" % "play-json-joda_2.13" % "2.9.3"
[info] com.typesafe.slick:slick-hikaricp:3.4.1                     -> "com.typesafe.slick" % "slick-hikaricp_2.13" % "3.4.1"
[info] org.scalatestplus.play:scalatestplus-play:5.1.0:test        -> "org.scalatestplus.play" % "scalatestplus-play_2.13" % "5.1.0" % "test"
[info] com.github.andyglow:websocket-scala-client:0.4.0:test       -> "com.github.andyglow" % "websocket-scala-client_2.13" % "0.4.0" % "test"
[info] com.typesafe.akka:akka-stream:2.6.20:test                   -> "com.typesafe.akka" % "akka-stream_2.13" % "2.6.20" % "test"
[info] com.typesafe.akka:akka-slf4j:2.6.20:test                    -> "com.typesafe.akka" % "akka-slf4j_2.13" % "2.6.20" % "test"
[info] com.typesafe.akka:akka-testkit:2.6.20:test                  -> "com.typesafe.akka" % "akka-testkit_2.13" % "2.6.20" % "test"
[info] com.typesafe.play:play-ahc-ws:2.8.16                        -> "com.typesafe.play" % "play-ahc-ws_2.13" % "2.8.16"
[info] io.monix:monix:3.4.1                                        -> "io.monix" % "monix_2.13" % "3.4.1"
[info] com.geirsson:scalafmt-core_2.12:1.5.1:scalafmt              -> "com.geirsson" % "scalafmt-core_2.13" % "1.5.1" % "scalafmt"
[info] com.typesafe.play:play-logback:2.8.16                       -> "com.typesafe.play" % "play-logback_2.13" % "2.8.16"
[info] com.typesafe.play:play-test:2.8.16:test                     -> "com.typesafe.play" % "play-test_2.13" % "2.8.16" % "test"
[info] com.typesafe.play:play-server:2.8.16                        -> "com.typesafe.play" % "play-server_2.13" % "2.8.16"
[info] com.typesafe.play:play-docs:2.8.16:docs                     -> "com.typesafe.play" % "play-docs_2.13" % "2.8.16" % "docs"
[info] org.scala-lang.modules:scala-async_2.11:0.9.7               -> "org.scala-lang.modules" % "scala-async_2.13" % "0.9.7"
[info] org.scalatest:scalatest:3.2.14:test                         -> "org.scalatest" % "scalatest_2.13" % "3.2.14" % "test"
[info] com.typesafe.akka:akka-serialization-jackson:2.6.20:test    -> "com.typesafe.akka" % "akka-serialization-jackson_2.13" % "2.6.20" % "test"
[info] com.typesafe.play:filters-helpers:2.8.16                    -> "com.typesafe.play" % "filters-helpers_2.13" % "2.8.16"
[info] com.lucidchart:scalafmt-impl_2.12:1.16-1.5:scalafmt         -> "com.lucidchart" % "scalafmt-impl_2.13" % "1.16-1.5" % "scalafmt"
[info] com.typesafe.akka:akka-actor-typed:2.6.20:test              -> "com.typesafe.akka" % "akka-actor-typed_2.13" % "2.6.20" % "test"
[success] Total time


Restore tweens fix

added gulp-babel to dependencies
fixed test line length error in spec/tweener.coffee

(alternate PR to: #83)
@legomushroom I apologize for the multiple PRs, I was too quick to click stuff :(
P.S.: This is what happened when running gulp initially, before I added gulp-babel:
➜  mojs git:(master) gulp
module.js:341
    throw err;
    ^

Error: Cannot find module 'gulp-babel'
  at Function.Module._resolveFilename (module.js:339:15)
  at Function.Module._load (module.js:290:25)
  at Module.require (module.js:367:17)
  at require (internal/module.js:16:19)
  at Object.<anonymous> (/Users/casraf/Dev/mojs/gulpfile.js:24:21)
  at Module._compile (module.js:413:34)
  at Object.Module._extensions..js (module.js:422:10)
  at Module.load (module.js:357:32)
  at Function.Module._load (module.js:314:12)
  at Module.require (module.js:367:17)
  at require (internal/module.js:16:19)
  at Liftoff.handleArguments (/usr/local/lib/node_modules/gulp/bin/gulp.js:116:3)
  at Liftoff.<anonymous> (/usr/local/lib/node_modules/gulp/node_modules/liftoff/index.js:198:16)
  at module.exports (/usr/local/lib/node_modules/gulp/node_modules/flagged-respawn/index.js:17:3)
  at Liftoff.<anonymous> (/usr/local/lib/node_modules/gulp/node_modules/liftoff/index.js:190:9)
  at /usr/local/lib/node_modules/gulp/node_modules/liftoff/index.js:164:9
  at /usr/local/lib/node_modules/gulp/node_modules/v8flags/index.js:108:14
  at /usr/local/lib/node_modules/gulp/node_modules/v8flags/index.js:36:12
  at /usr/local/lib/node_modules/gulp/node_modules/v8flags/index.js:47:7
  at nextTickCallbackWith0Args (node.js:452:9)
  at process._tickCallback (node.js:381:13)
  at Function.Module.runMain (module.js:449:11)
  at startup (node.js:139:18)
  at node.js:999:3

Coverage increased (+1.06%) to 96.358% when pulling e75c48306ba9576e40ff4d7e15debc6afef2a7dc on chenasraf:dev into 43a1a20347018be21e83f19aaa6e22c7b7e0630d on legomushroom:dev.

Coverage increased (+1.06%) to 96.358% when pulling e809fd8d1a357a65611a041e3521eb6e62018802 on chenasraf:dev into 43a1a20347018be21e83f19aaa6e22c7b7e0630d on legomushroom:dev.

Thanks 👍

Isn't it about time for a patch release at least?... :) since it's already merged for a while now...

tu


[RWLocks] Implement immutable shared object reference

This PR implements read-only shared object references.
We modify scheduling of transactions with shared object arguments where mutable: false flag set so that they do not 'conflict' with each other and can be executed in parallel.
Note that transaction dependency tree is also affected by shared object mutability:

Transaction with read-only reference to shared object depends on the transaction that created the version of shared object that this read-only transaction uses.

Read-only transactions do not depend on each other

Next write transaction depends on transaction that previously updated an object, but not on read-only transaction(s) that read this object.

See updated unit tests for details.
More changes in future PRs:

Better integration with pruner

Note: this PR contains commit from previous PR(#7687) that modifies API by adding mutable: bool flag

Will take a look at this in more details but it is great to call out pruner integration. I believe the current pruner implementation needs to be modified to not GC any object version written in the current epoch. Otherwise it seems possible that an object has multiple versions in the current epoch that can be pruned, but a transaction referencing a previous version in read mode has not finished execution.


fix: support griffe v0.28

This PR enables support for griffe v0.28 by changing imports for two classes that were moved...
# previously
from griffe.dataclasses import Name, Expression

# now
from griffe.expressions import Name, Expression

Note that this breaks backwards compatibility with previous versions of griffe, so we'll need to update the renderers in siuba and pyshiny.

Let's re-run CI / merge this this very small fix to griffe v0.28.1 is made: https://github.com/mkdocstrings/griffe/pull/164


Turn OFF front-end for the GOV.UK Performance Platform

Performance Platform retirement will not happen in September.
November is the slated month of retirement


Entry for finals Code Blooded

Application for Registering Team to CODE CAMP 1.0
This pull request template helps you complete an application to the CODE CAMP 1.0 HACKATHON. Use the checklist below to verify that you have followed the instructions correctly.
(Put x inside [] like [x])
Select the type of Pull Request
[] Registration Pull request.
[x] Submission Pull request.
Checklist ✅

[x] I have read the instructions on the README file before submitting my application and gone through CODE_OF_CONDUCT.
[x] I have Submitted my team's details by making a folder of my team as instructed in How to send Pull Request page.
[x] I have used the Markdown file template to add my information for the Hackathon.
[x] I have given all the necessary details as mentioned in template index.md file and the details are correct and best to my knowledge.
[x] I understand that a reviewer will merge my pull request after examining it or ask for changes in case needed.
[x] I understand I should not tag or add a reviewer to this Pull Request.
[x] I understand the Details added to the template will be used as a means of communication at the time of result declaration.
[x] I have added the event to my calendar.

@KaranBengani , Conflicting..

What should i change


it didn't work after reactive from background

it didn't work after reactive from background. any idea for this issue?

Please provide more information on the steps to reproduce your issue, what your expected behavior is, and what the actual behavior is, so that I can help you.


doc: fix changes of hset.(incorrect version)

fix: https://github.com/andymccurdy/redis-py/issues/1296
Pull Request check-list
Please make sure to review and check all of these items:

[x] Does $ tox pass with this change (including linting)?
[x] Does travis tests pass with this change (enable it first in your forked repo and wait for the travis build to finish)?
[x] Is the new or changed code fully tested?
[x] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Description of change
Please provide a description of the change here.

Codecov Report

Merging #1297 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1297   +/-   ##
=======================================
  Coverage   92.75%   92.75%
=======================================
  Files          19       19
  Lines        6477     6477
=======================================
  Hits         6008     6008
  Misses        469      469

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 e57daf5...445c75e. Read the comment docs.

Thanks. I might have been the cause of this after a rebase.


Suggestion: when opening the wallet with address only, allow ENS.

Allowing people to look up wallet info with ENS names would be cool!

Agreed.


Fix unittests that ignore the return attribute

This pull request is necessary for https://github.com/D-Programming-Language/dmd/pull/4868.

This pull request is necessary for https://github.com/D-Programming-Language/dmd/pull/4868.

I've verified that this change is correct with the compiler fix applied locally. Considering that the only remaining problem with https://github.com/D-Programming-Language/dmd/pull/4868 is a Phobos error, shouldn't that be sufficient?

I think this change is sufficient and I can believe you.
But in previous when we had faced same situations (dmd and phobos should be fixed at the same time), we decided to follow a simple rule "keep master branch green". Although it requires additional steps, we can mechanically guarantee that the HEAD of each repositories is not breaking.
It's important than we can imagine. The auto-tester tests the dmd and Phboos in all platforms.
On the other hand, I think when you did verify the changes in you local, you had use only one or two platforms.
In old days, sometimes we had accidentally broke master, when we had directly pushed some locally verified changes into master. From the our experience, your local verification is not enough to guarantee the change won't break anything.
Let's verify everything through the auto-tester result.

Ah, makes sense. I'll change it.

I've pushed the changes. I'll submit a follow-up patch once the compiler changes are merged.

Thanks!

Auto-merge toggled on


Modifying DBInstance on every apply

What happened?

RDS instance is modified by provider every time I apply the same manifest.
Provider diff log (the same every time):
2023/06/07 13:08:14 Found observed difference in dbinstance
  &v1alpha1.DBInstanceParameters{
        ... // 4 ignored and 31 identical fields
        NcharCharacterSetName:              nil,
        NetworkType:                        nil,
-       OptionGroupName:                    nil,
+       OptionGroupName:                    &"test-internal-dev-aa543a",
        PerformanceInsightsKMSKeyID:        nil,
        PerformanceInsightsRetentionPeriod: nil,
        ... // 3 ignored and 11 identical fields
  }

kubectl diff:
   creationTimestamp: "2023-06-07T07:47:56Z"
   finalizers:
   - finalizer.managedresource.crossplane.io
-  generation: 35
+  generation: 36
   name: test-internal-dev-aa543a
   resourceVersion: "3558141"
   uid: 8ef0d661-741c-4fed-ac0f-ec3f9d9f9aee
@@ -35,7 +35,7 @@
     enableIAMDatabaseAuthentication: false
     enablePerformanceInsights: false
     engine: sqlserver-ex
-    engineVersion: 15.00.4236.7.v1
+    engineVersion: "15.00"
     finalDBSnapshotIdentifier: test-internal-dev-aa543a
     iops: 3000
     licenseModel: license-included
@@ -51,6 +51,7 @@
     preferredMaintenanceWindow: thu:05:36-thu:06:06
     publiclyAccessible: true
     region: eu-north-1
+    skipFinalSnapshot: false
     storageEncrypted: false
     storageThroughput: 125
     storageType: gp3

How can we reproduce it?

Apply yaml and wait until created.
Apply again.

---
# Source: wit-server/templates/aws/rds.yaml
apiVersion: rds.aws.crossplane.io/v1alpha1
kind: DBInstance
metadata:
  name: test-internal-dev-aa543a
spec:
  forProvider:
    allocatedStorage: 100
    applyImmediately: true
    autogeneratePassword: true
    autoMinorVersionUpgrade: true
    backupRetentionPeriod: 0
    dbInstanceClass: "db.t3.small"
    deletionProtection: true
    engine: sqlserver-ex
    engineVersion: "15.00"
    dbParameterGroupNameRef:
      name: test-internal-dev-aa543a
    optionGroupName: test-internal-dev-aa543a
    masterUserPasswordSecretRef:
      key: password
      name: rds-master-password
      namespace: test
    publiclyAccessible: true
    dbSubnetGroupName: test-dev
    region: eu-north-1
    skipFinalSnapshot: false
    finalDBSnapshotIdentifier: test-internal-dev-aa543a
    storageEncrypted: false
    storageType: gp3
    masterUsername: wit
    vpcSecurityGroupIDRefs:
      - name: test-internal-dev-rds-aa543a
  writeConnectionSecretToRef:
    name: rds-connection-settings
    namespace: test
---
# Source: wit-server/templates/aws/rds.yaml
apiVersion: rds.aws.crossplane.io/v1alpha1
kind: DBParameterGroup
metadata:
  name: test-internal-dev-aa543a
spec:
  forProvider:
    description: test-internal-dev-aa543a
    dbParameterGroupFamily: "sqlserver-ex-15.0"
    region: eu-north-1
---
# Source: wit-server/templates/aws/rds.yaml
apiVersion: rds.aws.crossplane.io/v1alpha1
kind: OptionGroup
metadata:
  name: test-internal-dev-aa543a
spec:
  forProvider:
    engineName: sqlserver-ex
    majorEngineVersion: "15.00"
    optionGroupDescription: test-internal-dev-aa543a
    region: eu-north-1
---
# Source: wit-server/templates/aws/rds.yaml
apiVersion: ec2.aws.crossplane.io/v1beta1
kind: SecurityGroup
metadata:
  name: test-internal-dev-rds-aa543a
  namespace: test
spec:
  forProvider:
    description: RDS MSSQL for wit-server
    groupName: test-internal-dev-rds-aa543a
    ingress:
      - fromPort: 1433
        ipProtocol: tcp
        ipRanges:
          - cidrIp: <IP_ADDRESS>/0
        toPort: 1433
    region: eu-north-1
    vpcId: vpc-xxxx

What environment did it happen in?
Crossplane version: v1.12.1
aws-provider version: 0.40.0

Not stale

/fresh
not stale

I've tried to reproduce it using provider version 0.43.1 and it seems it is not reproduced now. Closing then.


Support macro targets in plugin context

This currently prevents the use of plugins in any package graph that happens to include one or more macro targets which seems extremely unfortunate.
This fix is slightly ugly because PackagePlugin should not concretely know about macros. An alternative could be excluding macros from the project model that plugins see.
rdar://108531004

@swift-ci please smoke test


version 1.0.3

monthly release to integrate most recent improvements and fixes

Coverage decreased (-0.3%) to 58.672% when pulling 61cbe540af601216185184c4fc105c42f950a704 on bernard357:master into 013c54dc1b07c5b2173701021a7175afc71d0ff6 on DimensionDataCBUSydney:master.

Coverage decreased (-0.3%) to 58.672% when pulling e2e8d245addd2740e6ae6aef3fca1ab225168889 on bernard357:master into 013c54dc1b07c5b2173701021a7175afc71d0ff6 on DimensionDataCBUSydney:master.

Coverage decreased (-0.3%) to 58.672% when pulling a92686780b3c71c31b46306b9ef6577816b2ab93 on bernard357:master into 013c54dc1b07c5b2173701021a7175afc71d0ff6 on DimensionDataCBUSydney:master.

Coverage decreased (-0.3%) to 58.672% when pulling 5512010b01ea556e0b7aa99577db691f00bf5130 on bernard357:master into 013c54dc1b07c5b2173701021a7175afc71d0ff6 on DimensionDataCBUSydney:master.

Coverage increased (+0.01%) to 59.005% when pulling 0201d0e7d8e7a74c963b5a2d9da3312d86290f64 on bernard357:master into 013c54dc1b07c5b2173701021a7175afc71d0ff6 on DimensionDataCBUSydney:master.

Coverage increased (+0.01%) to 59.005% when pulling 230faf3716c04634f70cf2d9e51cbc2c26fe112e on bernard357:master into 013c54dc1b07c5b2173701021a7175afc71d0ff6 on DimensionDataCBUSydney:master.

guys, would you mind to accept this PR please? probably the last for 2016... thanks for your continuous support and encouragements


Tools link is broken

Describe the bug
The "tools" link in https://www.researchobject.org/ro-crate/#how-can-i-use-it is broken.  It tried to access the md file instead of the rendered html.
URL
https://www.researchobject.org/ro-crate/tools.md
Suggested fix
I cannot see why this does not render correctly, so I cannot provide a fix I am afraid.
Additional context
N/A

Good catch! Last contentathon we decided to have separate pages for tools and usecases, which leads to those pages being in their own directory + index file. If you want to link towards a directory, we should not add .md as link, because the html equivalent does not exist. The correct linking should be tools like it is done with RO-Crate specification 1.1. If #142 is merged, this should be fixed.

@longr This is fixed.


Snippets

Hello!
Congratulations, this is an excellent iOS port of CLucene, we are using it in our projects.
Any clue about how do we extract small snippets of texts from each match?
Thanks in advance,
Frankai

Hello Frankai,
Thank you, I'm glad you find the package useful. Can you be more specific about what you're trying to achieve? As long as you are using the BRIndexableStorageTypeStore flag for your indexed data, the full original text is available to you in each match.
-- m@

Hi!
Yes, we have the full original text in each match, but I just want to present the results with an extract of the words around each match (ie: Google results, a text fragment containing your search terms in bold).
I can process each result and search again the full original text on my own, but sometimes the user search query is not the same that CLucene uses internally, for example, if we use StemmedPrefixSearches= YES.
Could we get the CLucene internal search terms that fired each hit in the results?
Thanks!
Frankai

Ah, yes I thought that might be what you were trying to achieve. Lucene calls that "highlighting" and it does support that, but the BRFullTextSearch API itself does not. This has long been a desired feature, and there is even a branch that was created to work on it, but it hasn't really got off the ground yet.

Ok, thanks, I'll try it.


Change Github Organization Logo

Change the Logo of the Warrior Ride Buddies Organization to be the app logo.

Background is transparent


Update zio, zio-test, zio-test-sbt to 2.0.9

Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

from 2.0.0 to 2.0.9.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #159.


E0319 23:26:38.220281 1800494 coredump_hook.cc:494] RAW: Skipping coredump since rlimit was 0 at process start.
E0319 23:26:38.220291 1800494 client.cc:269] RAW: Coroner client retries enabled, will retry for up to 30 sec.
E0319 23:26:38.220295 1800494 coredump_hook.cc:550] RAW: Sending fingerprint to remote end.
E0319 23:26:38.220307 1800494 coredump_hook.cc:559] RAW: Cannot send fingerprint to Coroner: [NOT_FOUND] stat failed on crash reporting socket /var/google/services/logmanagerd/
remote_coredump.socket (Is the listener running?): No such file or directory
E0319 23:26:38.220313 1800494 coredump_hook.cc:611] RAW: Dumping core locally.
F0319 23:26:38.216995 1800494 llo_decomposer.cc:893] Unexpected opcode: dma-vmem-to-host-ram
E0319 23:26:38.427992 1800494 process_state.cc:799] RAW: Raising signal 6 with default behavior
Aborted (core dumped)

(Crashing because the features aren't ready yet.)

New crash:
Traceback (most recent call last):
File "/home/rwitten/maxtext/pedagogical_examples/host_offload.py", line 55, in
host_out_shardings = jax.tree.map(lambda x : x.with_memory_kind('pinned_host'), shardings)
File "/home/rwitten/.local/lib/python3.10/site-packages/jax/_src/tree.py", line 61, in map
return tree_util.tree_map(f, tree, *rest, is_leaf=is_leaf)
File "/home/rwitten/.local/lib/python3.10/site-packages/jax/_src/tree_util.py", line 312, in tree_map
return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))
File "/home/rwitten/.local/lib/python3.10/site-packages/jax/_src/tree_util.py", line 312, in
return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))
File "/home/rwitten/maxtext/pedagogical_examples/host_offload.py", line 55, in
host_out_shardings = jax.tree.map(lambda x : x.with_memory_kind('pinned_host'), shardings)
File "/home/rwitten/.local/lib/python3.10/site-packages/jax/_src/sharding_impls.py", line 378, in with_memory_kind
return NamedSharding(self.mesh, self.spec, memory_kind=kind)
ValueError: Could not find memory addressable by device TPU v4. Device TPU v4 can address the following memory kinds: device, unpinned_host. Got memory kind: pinned_host


Preferred citation

Hey, great work! What's your preferred method to (academically) cite MOAT?

Hi, thank you for your interest, this manuscript is still under review.
For now, please cite our paper in the Arxiv format. We will update the citation if the paper status changes.
@misc{lu2023moat,
      title={MOAT: Towards Safe BPF Kernel Extension},
      author={Hongyi Lu and Shuai Wang and Yechang Wu and Wanning He and Fengwei Zhang},
      year={2023},
      eprint={2301.13421},
      archivePrefix={arXiv},
      primaryClass={cs.CR}
}


Rewrote the "getNewImageDimensions" method.

The original one was copied from stackoverflow and wasn't perfect for all the edge-cases.

This fixes #9


Keywords from .desktop file not shown if metainfo also contains keywords

The VCMI .desktop file contains these keywords:
Keywords=heroes of might and magic;heroes;homm;homm3;strategy;

https://github.com/vcmi/vcmi/blob/9121fcdc975dbf31a8eec8b2a41922402e5321a2/launcher/vcmilauncher.desktop#L14
The metainfo file contains these keywords:
	<keywords>
		<keyword>heroes3</keyword>
		<keyword>homm3</keyword>
	</keywords>

https://github.com/vcmi/vcmi/blob/9121fcdc975dbf31a8eec8b2a41922402e5321a2/launcher/eu.vcmi.VCMI.metainfo.xml#L143
However, only the latter ones are shown on flathub.org:

According to this comment, they should be merged:
https://github.com/ximion/appstream/issues/636#issuecomment-2157018931
First, I thought it might be because the .desktop file contains a keyword with spaces. Not sure if that matters.

This is an issue with appstream, if it doesn't pull in the keywords from .desktop file. It's missing from the catalogue data:
gunzip -c ~/.local/share/flatpak/app/eu.vcmi.VCMI/current/active/files/share/app-info/xmls/eu.vcmi.VCMI.xml.gz|xmllint --xpath "//keywords/keyword/text()" -

heroes3
homm3


[Localization] Both milliseconds and microseconds are shown as milliseconds on ko-KR localization

Both milliseconds(밀리초) and microseconds(마이크로초) are shown as milliseconds(밀리초) on ko-KR localization.
It is fairly misleading, I hope it gets fixed soon.

It is the latest version.
Actually, this issue still remains on the latest master branch.
I know this repository doesn't accept the localization PR, but I created a PR to show that it still exists on the master branch.
#1720
 - OS Build: 10.0.19043.0
 - Architecture: X64
 - Application Version: 10.2103.8.0
 - Region: ko-KR
 - Dev Version Installed: True

Already routed this to our internal localization team, so closing this.


update supported opa versions to 0.61

🗣 Description

ScubaGear supports up to 0.59.0. And the most recent OPA version is 0.61.0 now. Add latest support to the tool.
Adding the 0.60.0 and 0.61.0 version to the list of acceptable versions in the OPA.ps1 install script
Updating the default install version to 0.61.0
💭 Motivation and context

closes #777
🧪 Testing

Run the OPA.ps1 or SetUp.ps1 to ensure it install the latest version of OPA (0.61.0)
Run .\Testing\RunUnitTests.ps1 to ensure all test still passes.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] PR targets the correct parent branch (e.g., main or release-name) for merge.
[x] Changes are limited to a single goal - eschew scope creep!
[x] Changes are sized such that they do not touch excessive number of files.
[x] All future TODOs are captured in issues, which are referenced in code comments.
[x] These code changes follow the ScubaGear content style guide.
[x] Related issues these changes resolve are linked preferably via closing keywords.
[x] All relevant type-of-change labels added.
[x] All relevant project fields are set.
[x] All relevant repo and/or project documentation updated to reflect these changes.
[x] Unit tests added/updated to cover PowerShell and Rego changes.
[x] Functional tests added/updated to cover PowerShell and Rego changes.
[x] All relevant functional tests passed.
[x] All automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

[ ] PR passed smoke test check.

[ ] Feature branch has been rebased against changes from parent branch, as needed
Use Rebase branch button below or use this reference to rebase from the command line.

[ ] Resolved all merge conflicts on branch

[ ] Notified merge coordinator that PR is ready for merge via comment mention

✅ Post-merge checklist

[ ] Feature branch deleted after merge to clean up repository.
[ ] Verified that all checks pass on parent branch (e.g., main or release-name) after merge.

README.md section will also need to be changed to v0.61.0 https://github.com/cisagov/ScubaGear/tree/777-add-support-for-latest-opa-v0600?tab=readme-ov-file#download-the-required-opa-executable

Good catch! thank you

README.md section will also need to be changed to v0.61.0 https://github.com/cisagov/ScubaGear/tree/777-add-support-for-latest-opa-v0600?tab=readme-ov-file#download-the-required-opa-executable

Good catch! thank you

Np! Going to pull this down locally to do a final check, will approve after.

Created reports for gcc/gcchigh licenses successfully, all unit tests pass.
I did run a --strict Rego check and I'm getting these errors. @Sloane4 Any insight here? KeyFunctions.rego has package utils.key declared so wonder what it wants here.

Created reports for gcc/gcchigh licenses successfully, all unit tests pass.
I did run a --strict Rego check and I'm getting these errors. @Sloane4 Any insight here? KeyFunctions.rego has package utils.key declared so wonder what it wants here.

seems like even with the older version 0.59 the check still complains about undefined function, so i suspect it might be something with the format of how the function is formatted (not entirely sure).

@Dylan-MITRE @mitchelbaker-cisa
It is because you are not sending the KeyFunctions.rego file through check. KeyFunctions.rego file is at .\PowerShell\ScubaGear\Rego\Utils\KeyFunctions.rego. In the command, you are only feeding the files under testing into opa check. Included examples below:

If I send all rego files under .\PowerShell\ScubaGear (1st case), no errors are produced). If I send all rego files under .\PowerShell\ScubaGear\Testing any functions defined in a file not in the testing directory or below it will be undefined (2nd case).

@nanda-katikaneni should be ready to merge, smoke test fails due to an upstream bug in MSGraph SDK.


chore: add build script

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support swift package manage

We should import Foundation, If not error like:

swift-package-manager


Update dependencies

@kristerkari this includes #51 and fixes the npm vulnerabilities.

BTW you should enable automated security fixes in your repos

Thanks! I'll review this later today

@kristerkari friendly ping about this and #50

Sorry for the delay! I've been super busy lately.


add html with wireframing

add index.html with wireframing for the webpage layout

page layout version 1.
Let's try it!


Issue 141 -- fix 'no agent available' user view

When a local agent is unavailable to relay messages from the client to Zambeze, the user experience should be 'informative and helpful'. This branch is a first attempt at improving that user workflow.
Closes #141

Added docstring to dispatch. Removed status and result as those are improperly implemented and partially moved to other classes. Cleaning up as we go :)

It looks like you used the Google style for the docstrings. I thought we decided to use the NumPy style? I also suggested the NumPy style in the CONTRIBUTING.md document. So which style should we use?

You also need to rebase this branch so it's up-to-date with the main branch.

@wigging I believe this is proper numpy style now (per their docs that you linked in the contributing doc). That's what I get for asking AI for helping in the docstring conversions...

"""Initializes a Campaign instance.

Parameters
----------
    name : str
        The name of the campaign.
    activities : str, optional
        List of science activities for processing by Zambeze.
    logger : logging.Logger, optional
        Logger object to flush stderr and stdout
    force_login : bool
        Boolean whether to force a Globus Auth flow.
"""

Should be like this:
"""Initializes a Campaign instance.

Parameters
----------
name : str
    The name of the campaign.
activities : str, optional
    List of science activities for processing by Zambeze.
logger : logging.Logger, optional
    Logger object to flush stderr and stdout
force_login : bool
    Boolean whether to force a Globus Auth flow.
"""

Same for the other docstrings. Also, Notes: should be underlined and remove the : at the end.
All of this can be checked by the linter. But if we enable it in GitHub Actions then most of the Python files would fail because the docstrings are a mess in this project.


Force apt::ppa before package

Forces the configuration of the apt::ppa repository before the
installation of packages, so they will be installed in their correct
version.

Hi,
thanks for the PR! One travis runner run into a timeout and I restarted it.

@amateo can you take a look at the failing ubuntu acceptance test?


fix: color picker input closing problem

This PR fixes the issue #6595.
updateData was passed to ColorPickerPopupContent but never used anywhere and hence there the appState.openPopup is not reset.
Invoked updateData inside onCloseAutoFocus in Popover.Content.

Thanks @vsaravind01! ❤


“Get current XPath” feature for XML editor

This feature is available from the ‘Goto XPath’ command effect, the current XPath is shown and can be copied to the clipboard.


[header_store] remove the header_store

Description
Following the discussions about the disk clean up it appears that we don't have a good reason to store the headers in the header_store in first place. It appears that there was an earlier version of narwhal where the headers & certificates were stored separately. Also when a header is processed, it seems there is no much value just storing it as we don't really do anything with it - we don't even check if the header is stored when we process the corresponding certificate as we perform all the validations from the beginning. That leads us to a place for really questioning the value of storing the headers which is almost doubling the storage requirements as the certificates (which we store as well) already contain the header.
As part of this issue we should work in the primary node and remove the header_store completely.

Let's re-evaluate the need for this given the latest changes.

@akichidis is this still something that's needed/desired?


New options for contents-list component

What
Two new options for the contents-list component:

alternative_line_style
title

These can be used to format the list as a navigation block on landing pages. Trello
Why
Landing pages have a navigation element in a sidebar. This navigation element can use the contents-list component. However, there are additional requirements which require new options:

the active state is shown with a vertical border and bold blue text.
increased vertical spacing between lines
the Contents title can be replaced by an alternative title.

Visuals

title
alternative_line_style

Hi @andysellick I've fixed all your requests, hopefully this can be merged now.


Question: I have installed docker, what will happen if I use docker-machine to create my instances

I have been fiddling with docker in my ubuntu machine for quite some time now and it works great, however, docker-machine came, will this change the way I create my containers in my own local machine?
Running docker-machine create --driver virtualbox dev

This will download a lightweight Linux distribution (boot2docker) with the Docker daemon installed, and will create and start a VirtualBox VM with Docker running.

That means it'll be like me running boot2docker on windows right?

Yep. docker-machine with the virtualbox driver is very similar to running boot2docker.

Alright got that, so I can have both docker in my laptop and docker-machine so I can launch droplets / vps / ec2 instances with docker instance running? Am I right?

Yep, absolutely

Okay then, I think that confirmed my understanding.


Remove the dynamic left/right position calculation of edit popup

Popup should calculate it's side only when opened not calculate on every window position change. It's solved the same way in osx native nspopover.

removed the obsolete calculations with 8208fd4e870a9ea645d25c429d80f48458813108


Unexpected application shutdown

Hi
I'm using Spring Boot 2.1.6 and Spring Cloud 2.1.2 and want to add Spring Cloud Zookeeper to my project for service discovery. However after successful start my application silently terminates (I assume it was shutdown somewhere inside the library). I don't see any exceptions in the log or error messages.
I run Zookeeper: docker run --name zookeeper --restart always -d -p 2181:2181 zookeeper
I turned on debug mode in the logs:
2019-07-31 20:55:36.675  INFO 8900 --- [localhost:2181)] org.apache.zookeeper.ClientCnxn          : Opening socket connection to server localhost/<IP_ADDRESS>:2181. Will not attempt to authenticate using SASL (unknown error)
2019-07-31 20:55:36.678  INFO 8900 --- [localhost:2181)] org.apache.zookeeper.ClientCnxn          : Socket connection established, initiating session, client: /<IP_ADDRESS>:58144, server: localhost/<IP_ADDRESS>:2181
2019-07-31 20:55:36.679  INFO 8900 --- [           main] o.a.c.f.imps.CuratorFrameworkImpl        : Default schema
2019-07-31 20:55:36.679 DEBUG 8900 --- [localhost:2181)] org.apache.zookeeper.ClientCnxn          : Session establishment request sent on localhost/<IP_ADDRESS>:2181
2019-07-31 20:55:36.687  INFO 8900 --- [localhost:2181)] org.apache.zookeeper.ClientCnxn          : Session establishment complete on server localhost/<IP_ADDRESS>:2181, sessionid = 0x100005726ad000b, negotiated timeout = 40000
2019-07-31 20:55:36.692  INFO 8900 --- [ain-EventThread] o.a.c.f.state.ConnectionStateManager     : State change: CONNECTED
2019-07-31 20:55:36.700 DEBUG 8900 --- [localhost:2181)] org.apache.zookeeper.ClientCnxn          : Reading reply sessionid:0x100005726ad000b, packet:: clientPath:/zookeeper/config serverPath:/zookeeper/config finished:false header:: 1,4  replyHeader:: 1,23,-101  request:: '/zookeeper/config,T  response::
2019-07-31 20:55:36.700 DEBUG 8900 --- [localhost:2181)] org.apache.zookeeper.ClientCnxn          : Reading reply sessionid:0x100005726ad000b, packet:: clientPath:/zookeeper/config serverPath:/zookeeper/config finished:false header:: 2,4  replyHeader:: 2,23,-101  request:: '/zookeeper/config,T  response::
2019-07-31 20:55:37.143  INFO 8900 --- [           main] i.d.zookeeper.ZookeeperApplication       : Started ZookeeperApplication in 6.509 seconds (JVM running for 6.851)
2019-07-31 20:55:37.147  INFO 8900 --- [tor-Framework-0] o.a.c.f.imps.CuratorFrameworkImpl        : backgroundOperationsLoop exiting
2019-07-31 20:55:37.148 DEBUG 8900 --- [       Thread-4] org.apache.zookeeper.ZooKeeper           : Closing session: 0x100005726ad000b
2019-07-31 20:55:37.148 DEBUG 8900 --- [       Thread-4] org.apache.zookeeper.ClientCnxn          : Closing client for session: 0x100005726ad000b
2019-07-31 20:55:37.152 DEBUG 8900 --- [localhost:2181)] org.apache.zookeeper.ClientCnxn          : Reading reply sessionid:0x100005726ad000b, packet:: clientPath:null serverPath:null finished:false header:: 3,-11  replyHeader:: 3,24,0  request:: null response:: null
2019-07-31 20:55:37.152 DEBUG 8900 --- [       Thread-4] org.apache.zookeeper.ClientCnxn          : Disconnecting client for session: 0x100005726ad000b
2019-07-31 20:55:37.152  INFO 8900 --- [       Thread-4] org.apache.zookeeper.ZooKeeper           : Session: 0x100005726ad000b closed
2019-07-31 20:55:37.152  INFO 8900 --- [ain-EventThread] org.apache.zookeeper.ClientCnxn          : EventThread shut down for session: 0x100005726ad000b

Tested with Zookeeper 3.4/3.5 and with Spring Cloud 2.1.2/2.1.1/2.10 and 2.0.x gave me the same result.
Also I want to mention I use JDK 11.0.2

Dependencies and configuration?

@spencergibb Nothing especial:

@SpringBootApplication
public class ZookeeperApplication {

	public static void main(String[] args) {
		SpringApplication.run(ZookeeperApplication.class, args);
	}
}

server:
  port: 9050
logging:
  level:
    org.apache.zookeeper: DEBUG

	<parent>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-parent</artifactId>
		<version>2.1.6.RELEASE</version>
		<relativePath /> <!-- lookup parent from repository -->
	</parent>
	<artifactId>zookeeper</artifactId>

	<properties>
		<spring.cloud.starter.version>Greenwich.SR2</spring.cloud.starter.version>
		<java.version>1.11</java.version>
	</properties>

	<dependencyManagement>
		<dependencies>
			<dependency>
				<groupId>org.springframework.cloud</groupId>
				<artifactId>spring-cloud-dependencies</artifactId>
				<version>${spring.cloud.starter.version}</version>
				<type>pom</type>
				<scope>import</scope>
			</dependency>
		</dependencies>
	</dependencyManagement>

	<dependencies>
		<dependency>
			<groupId>org.springframework.cloud</groupId>
			<artifactId>spring-cloud-starter-zookeeper-discovery</artifactId>
		</dependency>
	</dependencies>

	<build>
		<pluginManagement>
			<plugins>
				<plugin>
					<artifactId>maven-compiler-plugin</artifactId>
					<version>3.8.1</version>
					<configuration>
						<source>${java.version}</source>
						<target>${java.version}</target>
						<release>11</release>
					</configuration>
				</plugin>
				<plugin>
					<groupId>org.springframework.boot</groupId>
					<artifactId>spring-boot-maven-plugin</artifactId>
					<executions>
						<execution>
							<goals>
								<goal>repackage</goal>
							</goals>
						</execution>
					</executions>
				</plugin>
			</plugins>
		</pluginManagement>
	</build>

You don't have the web or webflux starter, so there's nothing to keep boot running

@spencergibb Thank you, I will close the ticket.


Unanticipated behaviour of Check BIP39, and feature request : stateless ephemeral SSKR share generation

Unlike the anticipated behaviour from this flowchart, Check BIP39 requires the Ledger to have already been initialised with the exact mnemonic seed, or else it will produce an error.  Therefore if the user wants to use Seed Tool to generate SSKR shares in an airgapped manner, I don't think it is possible.
Step 1 : Settings > Security > Reset Device (or incorrect PIN 3 times)
Step 2 : Restore mnemonic seed -> all Ledger apps are wiped
Step 3 : User would need to connect Ledger via USB to Mac/PC to re-install "Seed Tool"
I don't see any other way to change the Ledger's stored mnemonic seed without using Reset Device.
Could you modify Seed Tool such that it can shard any user entered mnemonic seed into SSKR shares, and not exclusively the Ledger's mnemonic seed.   I assume this behaviour is due to the "recovery check" roots of this project, perhaps you could add a warning when the user enters a non-matching valid mnemonic seed that the entered seed doesn't match, or add a 3rd menu option for the user to SSKR shard an ephemeral mnemonic seed.
I really to think having a stateless signing device like Seedsigner  or Coldcard Temporary Seed are an important use case, and it would be great for Ledger devices to support ephemeral SSKR share generation.

Check BIP39 requires the Ledger to have already been initialised with the exact mnemonic seed, or else it will produce an error.

Yes. This is by design.
The app makes sure that the user knows the BIP39 phrase for the device on which they are generating the SSKR shares.

By airgapped, I mean the mnemonic seed has never connected to a hot internet connected device.
Ledger wipe airgapped, check
Ledger restore airgapped, check
Install app-seed-tool, must be connected to a PC/Mac to install, and the mnemonic seed must have first been loaded on Ledger before connecting it to the PC/Mac

Install app-seed-tool, must be connected to a PC/Mac to install, and the mnemonic seed must have first been loaded on Ledger before connecting it to the PC/Mac

Fair enough, A Ledger device does need to be connected to a computer at some stage of it's life in order to install applications. No getting around that.

Correct.
I didn't have luck with Recovery Mode (power on holding the left button).
With a wiped uninitialised Nano S Plus, Recovery mode does let you install apps both via ledgerblue and via LedgerLive.
However rebooting again into Recovery Mode = all apps are deleted.
Rebooting in normal mode, then restoring a mnemonic seed = all apps deleted.


[Feature] Find the files ignored in .gitignore

Is this feature missing in the latest version?

[X] I'm using the latest release

Is your feature request related to a problem? Please describe.
We have some files which are a nuisance to dev (eg: binaries) but useful for automation. We'd like to know when our ci changes those binaries but current action does not allow that
Describe the solution you'd like?
A new option:

include_ignored_files (or similar boolean)

Describe alternatives you've considered?
Parse git status --ignored but that's a new headache :)
Anything else?
No response
Code of Conduct

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

@kunaltyagi This should now be available in the latest release via the match-ignore-files input which is enabled by default.

Thanks a ton @jackton1

Just a simple follow up:

| match-gitignore-files | string | true | "true" | Indicates whether to match filesin .gitignore |

What should match-gitignore-files be to not match gitignore? Would any string not equal to true work (eg: TRUE, yes, 1)?

Technically any other string other than “true” this might change in the future so I’ll suggest using “false”


Some improvements to the Upload component

Remove the onChange prop from Upload and replace it with onUpload :: Array FileId -> Effect Unit and onRemove :: FileId -> Maybe (Effect Unit).

The Maybe in onRemove lets us make some files non-removable.

Add a readonly :: Boolean field to FileInfo that indicates whether a given file may be removed or not.
Add a remove :: FileId -> Aff Boolean field to UploadBackend that allows for running an async action to check whether the file should be removed (e.g. a confirmation modal).
Add the onClick :: FileId -> Maybe (Effect Unit) prop to Upload so that users can interact with the uploaded files — e.g. for downloading them.
Add FormDefaults instances for Set and Map.

@kimispencer @spicydonuts I've updated this PR with some feedback from @hdgarrood. Could you review it again, please?


fix(v2): use baseUrl on search page

Motivation
To resolve #2827.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan

Linted (yarn prettier && yarn lint).
Tested (yarn test)

but target file did not have any tests.

Replacing the changed file on my test site to ensure that the defect is fixed.

Thanks for your review!
I've replaced useDocusaurusContext() with useBaseUrl().
lint/prettier/test was OK and this fix seems to work fine on my local site .
but I'm not 100% sure about how to use useBaseUrl() function so please re-review my new code. Thanks.
(Since this is my 1st PR in GitHub, I'm excited about your reaction!)

I found a side effect and it might be caused by useBaseUrl().
Other than top page, search result page URL was wrong.
For example, we are in the page '//docs/intro' and search there, destination is expected as '//search?q=' but actual was '//docs/search?q=. Please confirm useBaseUrl()` behavior.

Added link to this PR and did following tests.

Linted (yarn prettier && yarn lint).
Tested (yarn test)

but target file did not have any tests.

Replacing the changed file on my test site to ensure that the defect is fixed.

@tetunori thank you!


⚠ Bofrost.at has degraded performance

In e4429ec, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1892 ms

Resolved: Bofrost.at performance has improved in e5054ef after 22 minutes.


chore(package): update semantic-release to version 17.0.4

:tada: This PR is included in version 2.1.14 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[OSX] Right click options not working.

When selecting text, the right-click menu to copy text does not appear on osx.
Might this be related to https://github.com/jiahaog/nativefier/issues/43?
$ nativefier --version
6.6.1

$ node --version
v5.4.1

$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.11.2
BuildVersion:   15C50

Hi, that feature is not implemented and it's kind of low priority for me, as users can use the application menu to do so.

I second this. It's required for copy images or copy URL on a link. Not only copy text that you can do by selecting and using menu action.

Had same problem, update fixed it.

You might find electron-context-menu useful for this.

@sindresorhus Thank you for this, I'll look into implementing it

This would be great, did anyone implement it?

I believe this issue would be resolved by PR #579, which adds the electron-context-menu as a dependency of nativefier.


provide API for CI/CD Pipelines

Describe what problem your feature request solves
Provide an API for CI/CD pipelines
Describe the solution you'd like
Provide an API for CI/CD pipelines, see here for an example
Additional context

What functions are exposed for this API?
How do we handle authentication/authorization?
What do we use to document the API? (main github docs, auto-generated via swagger or apidoc?)

I am in favor of swagger to document it. Many tools exist to extract the API structure from swagger and integrate it in other systems.
For auth/auth I am in favor of Oauth2 and OIDC. It would make it easy to integrate in a larger CI system (like Gitlab, Gitea, etc...) and access their CI pipelines.
For the functions, I see at least 2 main ones :

push a source code and get back a threat-dragon json from it (the source code may be annotated to help)
push tests results (junit xml for instance) and push a threat-dragon json and get a comparison analysis back

Following @ShubhamPalriwala 's suggestion, this may be a good feature for the 2022 Google Summer of Code:
https://github.com/OWASP/www-community/commits/master/pages/initiatives/gsoc/gsoc2022ideas.md

This is still a valid issue, and is covers the points made on the API in issue #344


add CI for vulnerability scanning

Overview
Adds CI for vulnerability scanning
Related Issue / Discussion
None
Additional Information
Approach taken from pygeoapi (thank you @francbartoli!)
Contributions and Licensing
(as per https://github.com/geopython/pycsw/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

[x] I'd like to contribute [feature X|bugfix Y|docs|something else] to pycsw. I confirm that my contributions to pycsw will be compatible with the pycsw license guidelines at the time of contribution.
[x] I have already previously agreed to the pycsw Contributions and Licensing Guidelines

CI failure is unrelated (demo.pycsw.org down)


Feature: diff between two repos

Output of restic version

What should restic do differently? Which functionality do you think we should add?

What are you trying to do? What problem would this solve?

Did restic help you today? Did it make you happy in any way?

double post


[Beta-blocking] Update strings with Czech

What
Update strings with newly added Czech locale in our TD config
Why
Make an unhappy customer happy
https://portal.microsofticm.com/imp/v3/incidents/details/386605166/home
How Tested
No testing
Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

Should we be adding COMPONENT_LOCALE_CS_CZ and COMPOSITE_LOCALE_CS_CZ and also update in the storybook documentation

Doing it now :)


[libmount] Build error on x64-linux

Package: libmount:x64-linux -> 2.38#2
Host Environment

Host: x64-linux
Compiler: GNU 9.4.0
vcpkg-tool version: 2023-11-16-4c1df40a3c5c5e18de299a99e9accb03c2a82e1e
vcpkg-scripts version: 45f6e57d3 2023-12-06 (2 hours ago)

To Reproduce
vcpkg install sdl2
Failure logs
-- Using cached util-linux-2.38.tar.xz.
-- Cleaning sources at /home/jule/lib/vcpkg/buildtrees/libmount/src/2.38-22af6c1200.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/jule/lib/vcpkg/downloads/util-linux-2.38.tar.xz
-- Using source at /home/jule/lib/vcpkg/buildtrees/libmount/src/2.38-22af6c1200.clean
-- Getting CMake variables for x64-linux-dbg
-- Getting CMake variables for x64-linux-rel
-- Generating configure for x64-linux
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: /usr/bin/autoreconf -vfi
    Working Directory: /home/jule/lib/vcpkg/buildtrees/libmount/src/2.38-22af6c1200.clean/
    Error code: 1
    See logs for more information:
      /home/jule/lib/vcpkg/buildtrees/libmount/autoconf-x64-linux-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:629 (vcpkg_execute_required_process)
  ports/libmount/portfile.cmake:19 (vcpkg_configure_make)
  scripts/ports.cmake:170 (include)

/home/jule/lib/vcpkg/buildtrees/libmount/autoconf-x64-linux-err.log
autoreconf: Entering directory `.'
autoreconf: running: autopoint --force
Can't exec "autopoint": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 345.
autoreconf: failed to run autopoint: No such file or directory
autoreconf: autopoint is needed because this package uses Gettext

@JuleProjects Please try run command sudo apt-get install autopoint (maybe also need libtool).

@JuleProjects Please try run command sudo apt-get install autopoint (maybe also need libtool).

NO. Not autopoint. You need autoconf. And maybe automake. And maybe autoconf-archive.

I had the same issue. Actually, only after installing autopoint this error disappeared

Indeed. However, this can be fragile for some ports. And it implies that the port has an issue with dependencies.

@JuleProjects Please try run command sudo apt-get install autopoint (maybe also need libtool).

I had to install autoconf, autopoint, and libtool as well. Thank you!


[ServiceBus] New LiveTests for Preview 1

[x] Send single message

[x] Send Batch

[x] Receive batch and message settlement

[x] Peeklock/receive and delete
[x] renew lock on message

[x] Auto-lock-renew tests

[x] Receive deferred messages
[x] Iterator and message settlement
[x] Peek tests
[x] AAD
[x] http proxy/websocket
[x] Async version
[x] Stress test

Closing per preview 1 code complete


Support creating source note reference without a dedicated file

Currently, the only way to create a note ID is by creating an associated file. It might be useful to be able to just associate a file with multiple references.
# 2022-02-27-06-05-03 This is how you create a note ID

Then `[[2022-02-27-06-05-03]]` is used to refer to this note.
But what If I wanted to also use `[[my custom note id]]` to refer to this note as well?

I think tags could be used for this purpose. One can prefix a tag with a special word to refer to the same note with different things. The implementation for this issue would be unnecessarily complicated.


Fixed setting decreasing numbers

Following code didn't work correctly
var counter = new flipCounter('c1', defaults);
counter.setValue(123233);
counter.setValue(23);

it produced something like

Also fixed some race conditions when calling setValue too fast.

ping @cnanney

Thank you for PR.


gh repo create kicks me out of my gh account

Every time when I use gh repo create it creates a private repo, adds remote branches, but then it asks me for username and password. Since I use 2FA (and, you know, often passwords don't work there, so I have to generate access token again and again) it becomes very problematic for me to create repos. After that I can't use commands like git push origin master because I am not authorized and it asks me for username&password again. But without gh ... git works well, I can push/pull e t.c.

I think this issue might have been opened in the wrong place.

You’re looking for https://github.com/cli/cli ^^


[release-0.24] Upgrade to latest dependencies

bumping webhooks -dprotaso
/cc knative-sandbox/channel-wg-leads
/assign knative-sandbox/channel-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/reconciler-test b155197...88c8473:
  > 88c8473 Fix eventshub race (# 218) (# 220)
bumping knative.dev/pkg dd0db4b...953af01:
  > 953af01 [release-0.24] allow unknown metadata fields (# 2255)
  > 03e7ca5 Drop redundant pointers and decoders (# 2260)

noop


INT B-20273 add and update indexes for move history

Agility ticket
Summary
We are having some performance issues in staging that is related to this query. The AWS cloudwatch logs show this error:
@message {"level":"error","ts":"2024-05-15T21:34:57.631Z","caller":"ghcapi/move_history.go:40",
"msg":"Error retrieving move history by locator",
"git_branch":"main",
"git_commit":"6b21b53bfd0754d38b66bee9a5dd85b35566c58d",
"ecs_cluster":"arn:aws-us-gov:ecs:us-gov-west-1:015932076428:cluster/app-stg",
"ecs_task_def_family":"app-stg",
"ecs_task_def_revision":"4785",
"host":"office.stg.move.mil",
"milmove_trace_id":"66452a77-3703-4b99-3d8e-700d19eb4b2f",
"session_id":"9PiZPmdfcn9gAchp-o6fKwFLvJnilpbSwE9gViPtsLc",
"xray_trace_id":"1-66452a77-37034b993d8e700d19eb4b2f",
"error":"Could not complete query related to object of type: AuditHistory.",

Which we found to be erroring out in pkg/services/move_history/move_history_fetcher.go:49:
	rawQuery, qerr := query.GetSQLQueryByName("move_history_fetcher")
...
	query := appCtx.DB().RawQuery(rawQuery, locator).Paginate(int(*params.Page), int(*params.PerPage))
	err := query.All(audits)

	if err != nil {
		switch err {
		case sql.ErrNoRows:
			// Not found error expects an id but we're querying by locator
			return &models.MoveHistory{}, 0, apperror.NewNotFoundError(uuid.Nil, "move locator "+locator)
		default:
			return &models.MoveHistory{}, 0, apperror.NewQueryError("AuditHistory", err, "")
		}
	}

So the issue is with the query in move_history_fetcher.sql, which is basically a big fat query that pulls data from all of the important tables (moves, mto_shipments, orders, mto_service_items, etc).
Unfortunately we can't simulate the performance issues locally because staging has a ridiculous amount of data in their RDS table and locally we tend to clean a lot and have a lot less data.
The first round of solutions to improve the performance issues besides refactoring is making sure we have indexes set up in all of the necessary places. Below are all of the important tables and the columns that are used in several JOIN and subqueries within the CTEs in move_history_fetcher.sql:
moves
id: Used in multiple subqueries and joins.
locator: Used in the initial filtering condition in the move CTE.
mto_shipments
id: Used in joins with audit_history and move_service_items
move_id: Used in the filtering condition in the move_shipments CTE
destination_address_id, secondary_delivery_address_id, pickup_address_id, secondary_pickup_address_id: Used in the move_addresses CTE
audit_history
object_id: Used in multiple joins
table_name: Used in the filtering conditions for various logs
event_name and changed_data: Used in filtering conditions in several places
orders
id: Used in joins and subqueries.
service_member_id: Used in the move_service_members CTE
mto_service_items
id: Used in joins with audit_history.
move_id: Used in the filtering condition in the move_service_items CTE
mto_shipment_id: Used in joins with move_shipments
re_services
id: Used in joins with move_service_items
entitlements
id: Used in joins with audit_history
payment_requests
id: Used in joins with audit_history.
move_id: Used in filtering condition in the move_payment_requests CTE
payment_service_items
payment_request_id: Used in joins with payment_requests
proof_of_service_docs
payment_request_id: Used in joins with move_payment_requests
mto_agents
id: Used in joins with audit_history
mto_shipment_id: Used in joins with move_shipments
reweighs
id: Used in joins with audit_history.
shipment_id: Used in joins with move_shipments
service_members
id: Used in joins and subqueries
residential_address_id, backup_mailing_address_id: Used in the move_addresses CTE
sit_address_updates
id: Used in joins with audit_history
mto_service_item_id: Used in joins with move_service_items
user_uploads
id: Used in joins with audit_history
document_id: Used in joins with documents
documents
id: Used in joins with user_uploads.
service_member_id: Used in filtering condition in file_uploads CTE
weight_tickets
ppm_shipment_id: Used in joins with ppm_shipments
progear_weight_tickets
ppm_shipment_id: Used in joins with ppm_shipments
moving_expenses
ppm_shipment_id: Used in joins with ppm_shipments
ppm_shipments
shipment_id: Used in joins with move_shipments
backup_contacts
service_member_id: Used in filtering condition in move_backup_contacts CTE
addresses
id: Used in joins with audit_history
SOOOOOO all that being said, the only indexes that did not exist already were:
audit_history.object_id
proof_of_service_docs.payment_request_id
mto_agents.mto_shipment_id
ppm_shipments.shipment_id
backup_contacts.service_member_id
This PR adds those indexes. Sorry for the long read. Thanks for hangin'.
How to test

Open up MM as an office user
Review the move history logs and make sure that you can still see them without errors
Review DBeaver and make sure you see the new indexes on the above tables and their respective columns (find table, click "Properties", then click "Indexes").

Seeing the indices locally and not having any issues viewing move history. Looks like a good first shot!

Yeah this works locally but in staging is where the performance issue is. Hopefully this solves that performance issue so

Seeing the indices locally and not having any issues viewing move history. Looks like a good first shot!

Yeah this issue doesn't happen locally but hopefully this fixes the issue in staging so we do not have to go into refactoring that sql script. smh


cleanup melee

About the PR

it remove warns i guess
no more having to stare at the extremely yellow scrollbar
Why / Balance

Technical details

Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

sometimes I forget that maintainers can literally just push whatever they want into your branch if you make a PR


Column edit does not allow to change the data type.

Open edit column menu, change the type.

Issue fixed in release 4.0


sequelize connect impot, syncing sequalize models to database

still on turning anything on
just updating the file in server.js to import the connect and to wrap the current code with the sync-y thing

DONE!
I don't know what else to type here, it's just a couple of lines and a wrapping of code. I can't believe I did it first try.


Improvements in translation + better French

Sorry for the mess with Git, this is new for me :-/

OMG I've just seen the instruction about the pylupdate4 -verbose mikidown.pro & the use of Qt Linguist :O This is soo convenient! Instead of doing everything by hand...

Looks dandy! Merging this in!

Great! But i have some questions:

How to make the buttons "Cancel" + "OK" translatable? It seems that is related to the QTranslator implementation/instantiation right?
How to make translatable the text in __init__.py file?
And finally, which quoting style do you prefer? " or '?


Added missing super().__init_subclass__ call in _ParameterBase.__init_subclass__

Currently the _ParameterBase.__init_subclass__ method does not forward to the method on its superclass, so any other base classes in the MRO do not have a chance to perform any necessary subclass initialization steps. This PR adds the missing call.
This is particular relevant when defining a Parameter subclass with generic type parameters by inheriting from typing.Generic (or equivalently by using the new generics syntax added in Python 3.12). Inheriting from typing.Generic[T] where T is a typing.TypeVar typically allows a class to be parameterized by a concrete type, but this does not work when _ParameterBase is in the MRO since the __init_subclass__ call is not properly propagated up the MRO.
The following example raises an AttributeError in the current param release, but works correctly after this PR:

from typing import Generic, TypeVar
from param import Selector

T = TypeVar('T')

class GenericSelector(Selector, Generic[T]):
    pass

# raises `AttributeError: type object 'GenericSelector' has no attribute '__parameters__'`:
IntSelector = GenericSelector[int]

If using generics does mypy and other type checkers then know an IntSelector parameter is an int?

If using generics does mypy and other type checkers then know an IntSelector parameter is an int?

Probably not... unfortunately the param library doesn't seem to integrate very well with static type checkers, but hopefully it will get better someday (I was about to link issue #376 before realizing that was you haha). I can often trick my IDE (PyCharm) by declaring params like a: int = IntSelector(...), or a: T = GenericSelector(...) in a generic context, though it is far from perfect and probably doesn't fly with mypy. But even in cases where generics (and type-hints in general) don't serve a practical purpose, they can often significantly help with readability/maintainability anyways.
That said, the motivation for this PR isn't really specific to handling generic classes, that just happened to be the case that led me here.


JBPM-4985 - Script field of Script task contains \n and \t instead of…

… new line and tabulation

@tsurdilo This fixes the cases in the JIRA entry, but doesn't work correctly if a string constant contains "\n", e.g. System.out.println("Hello\nGoodbye");

@jlindop thanks - the method from propertywindow (and revised one you send) had some issues so I amended with a small change that seems to fix most cases. If you get that method to do what we need do feel free to change this to it

@jlindop amended


Main menu lags with too many things in list

Possibly due to having to download bitmap every refresh. Will consider caching images to disk.

Fixed in https://github.com/rkalz/UABParkingFinder/commit/adf927a89a0c1df45766d29c0c8c150657eb01e4 using Picasso library


Open github link in the app

Referencing github/android#525 ...

If you click on a link to github, you can select github as the default application but it still opens up in the browser. Have it open up in the app which will allow you to bypass needing to authenticate again. - memphis518

Just encountered this. Any update? I'm developing an app where I added a 'Report an issue' option that redirects the user to the GitHub issue tracker. Since I have GitHub app installed, I get both the browser and the GitHub app as options to process the link. But when I select GitHub it just opens the browser (which makes the GitHub option redundant). - ADTC

I'm tracking the progress with links in #93.
Please comment on that issue if you want to add any link.


Writable mounts

I beg your pardon re: my ignorance here, but I am researching feasibility of switching from OSX to Linux, and make use of many of the sparse bundle files, and I'd like to keep the same workflow if possible.
This repo states "read only," but it isn't clear to me if that is an absolute limitation, or if write is just not implemented yet. If the former, please close this and accept my apology! If the latter, perhaps this can serve as a note for others until it's implemented.
Thank you!

Is there any update on this problem? And what would be needed to do that? I'm thinking about implementing it, as it would prove very helpful for me, but I have no experience with FUSE.

Feel free to cherry-pick from here: https://github.com/cluck/sparsebundlefs/tree/write-support

@Gansgar Yupp, for the moment you can use @cluck's branch. I can add a note in the README about that, and the encrypted support as well, so that people know here to look for the extra features.


Disable window.PIXI with NPM module

Is it possible to disable window.PIXI when using the NPM module with webpack? I don't want users to be able to use edit the library functions easily via devtools

It is not possible right now, and I'm sure it won't be possible until v5 is release. See  #3118.

@lgraziani2712 is correct, in v4 (and v3) our plugin strategy is basically "always export to global, plugins just pretend PIXI will exist on global". Because of that we always export to it.
I'm hoping to have a much better plugin strategy in v5 that helps alleviate this issue. Sorry :/


JSON parse gives wrong Float64 result

Repro steps
Below code show difference between from_json and to_f64. (result of to_f64 is consistent with other languages while from_json is not)
num = "43.474709000000132"
puts Float64.from_json(num)
# 43.474709000000125
puts num.to_f64
# 43.47470900000013

Crystal compiler version

Crystal 1.0.0 [dd40a2442] (2021-03-22)
LLVM: 10.0.0
Default target: x86_64-unknown-linux-gnu

Should be fixed by #10447

Related to #10419


SKE Cluster: maxSurge and maxUnavailable cannot both be 0

Hi everyone,
I am trying to create a SKE cluster, which results in the following error during terraform apply
│ Error: Error creating/updating cluster
│
│   with stackit_ske_cluster.ske,
│   on kubernetes.tf line 1, in resource "stackit_ske_cluster" "ske":
│    1: resource "stackit_ske_cluster" "ske" ***
│
│ Calling API: 400 Bad Request, status code 400, Body:
│ ***"code":"InvalidArgument","message":"1 error occurred:\n\t* invalid input:
│ nodepool \"cpu-optimized\": maxSurge and maxUnavailable cannot both be
│ 0\n\n","details":""***

I would expect maxSurge and maxUnavailable not to interfere with the cluster creation, as it is an Optional parameter
Resource config used:
resource "stackit_ske_cluster" "ske" {
  project_id             = var.stackit_project_id
  name                   = "generic"
  kubernetes_version_min = "1.29.7"
  node_pools             = [
    {
      name               = "cpu-optimized"
      machine_type       = "c1.2"
      os_version_min     = "3815.2.5"
      minimum            = 1
      maximum            = 2
      availability_zones = ["eu01-3"]
      volume_size        = 100
      volume_type        = "storage_premium_perf0"
    }
  ]
  maintenance = {
    enable_kubernetes_version_updates    = true
    enable_machine_image_version_updates = true
    start                                = "01:00:00Z"
    end                                  = "02:00:00Z"
  }
  extensions = {
    argus = {
      enabled           = true
      argus_instance_id = data.stackit_observability_instance.argus.instance_id
    }
  }
}

Terraform version used:
"0.31.1"
Notes: Adding the parameters maxSurge and maxUnavailable directly does not change anything
Any help is appreciated, thanks!

Same for me with existing terraform code without one of the parameters. But I could add for example max_surge = 1 into the node_pools block to resolve this issue.
Note that the parameter in the API is different than for the terraform resource.
Nevertheless it feels like an unintentional error.

Hi, thanks for reporting the issue.
There were some new validations introduced recently by SKE that we are addressing.
We'll update here once a bugfix is released.

Adding max_surge = 1 is the temporary fix, the cluster was created, thanks!

We just updated the provider to latest version v0.32.0 and the issue is gone.

Hi,
as mentioned in the above comment, this issue has been fixed.
The condition is still valid, maxSurge and maxUnavailable cannot both be 0 at the same time. SKE has improved the validation. In documentation, the descriptions have been extended with this information.
https://registry.terraform.io/providers/stackitcloud/stackit/latest/docs/resources/ske_cluster#max_surge


[477 merge] CP-27391: datamodel option type support

This is @kc284 's work on supporting the datamodel option type in the SDK.
This has to be merged together with the corresponding PR in XAPI:
https://github.com/xapi-project/xen-api/pull/3544
See internal jenkins build on feature/REQ477/probe builds 66 and 72 that have successfully built the rpms and the SDK.

Squashed the fixups

assert false is for code that should never be reached, its a bug in the code if it is. Using GADTs would probably reduce the number of places that is needed, but its not always easy to refactor code to  use GADTs.

Agreed on cleaning up the match to use function instead, there is a lot of existing code that does it that way, I think that cleanup should be part of another PR


#43  converter 추가

Resolved #43

Codecov Report

Merging #51 (1ddd59e) into main (7b9e610) will decrease coverage by 0.68%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main      #51      +/-   ##
============================================
- Coverage     15.46%   14.77%   -0.69%
  Complexity        9        9
============================================
  Files            14       14
  Lines           194      203       +9
============================================
  Hits             30       30
- Misses          164      173       +9

Impacted Files
Coverage Δ

...sm/benecia/domain/recruitment/code/HiringArea.java
0.00% <0.00%> (ø)

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 7b9e610...1ddd59e. Read the comment docs.


Figure a user abstraction

Right now we just return the User model anywhere we need to pass around a user object. Does this make sense? Do we need to support some sort of anonymous user or is None a good anonymous user?

@dstufft - can you please check the milestone on this?  Is it required for launch?

We can probably just close this out completely. It's unlikely we're going to need to replace User objects anytime soon.


use getCenter function and others

How can I use getCenter?
I try
<GoogleMap
defaultZoom={14}
center={{lat: props.mapCenter.lat, lng: props.mapCenter.lng}}
onCenterChanged={getCenter()}

But I get message getCenter is undefined

Please refer to Getting Help section in the README (or #469).

you would figure basic usage would be covered under the documentation. There seems to be no mention of the switch from refs to whatever it currently uses:
In the change log it doesnt mention the change from ref="map" to ref={props.onMapLoad}
considering all previous ways of calling functions like getCenter() used ref.map.getCenter() it breaks existing code. Then when you try to set the ref, you get "Stateless function components cannot have refs."
so they got rid of refs entirely? This question has been asked on stackoverflow but considering there is no documentation for this change, there is no good answer yet on how to do basic map handling. I will be digging through the source code to figure it out... ugh.

Breaking change in 6.0.0.
https://github.com/tomchentw/react-google-maps/blob/master/CHANGELOG.md#600-2016-10-04
On Wed, Apr 26, 2017 at 12:56 AM David Vaini<EMAIL_ADDRESS>wrote:

you would figure basic usage would be covered under the documentation.
There seems to be no mention of the switch from refs to whatever it
currently uses:
In the change log it doesnt mention the change from ref="map" to
ref={props.onMapLoad}
considering all previous ways of calling functions like getCenter() used
ref.map.getCenter() it breaks existing code. Then when you try to set the
ref, you get "Stateless function components cannot have refs."
so they got rid of refs entirely? This question has been asked on
stackoverflow but considering there is no documentation for this change,
there is no good answer yet on how to do basic map handling. I will be
digging through the source code to figure it out... ugh.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tomchentw/react-google-maps/issues/466#issuecomment-297094733,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4SemMPtg4lP01eJ9lPyRa9cfjvXukhks5rziW_gaJpZM4NBX9n
.

Sure, I see that line change, but it doesnt mention the Ref's and how calling the refs are broken. Typically with broken changes, you specify the new way of handling it. So whats the new way of handling this.refs.map.getBounds(); ?

It's defined in the public method of the <GoogleMap> component. So get the ref and call getBounds
https://github.com/tomchentw/react-google-maps/blob/master/src/lib/GoogleMap.js#L97

Can anyone explain how to properly access the refs and how to subsequently call a function off of it per DavidVaini's question above?

https://github.com/jkranking
here's a nice example from official documentation
https://tomchentw.github.io/react-google-maps/places/search-box

I am trying to get the center by clicking on a button but when using this.refs.map.getCenter() i am getting the error of can not find property getCenter of undefined?

You need to store ref in some way so that they can access it later.

This is how I'm trying to use getCenter using a ref, and it's not working.
const Map = withScriptjs(
  withGoogleMap(() => {
    const ref: any = useRef<HTMLElement>(null);

    return (
      <GoogleMap
        options={{
          styles: mapOptions.styles,
          scrollwheel: mapOptions.scrollwheel
        }}
        defaultZoom={mapOptions.zoom}
        defaultCenter={{ lat: -26.896333, lng: -49.23524 }}
        ref={ref}
      >
        <Marker position={ref.current.getCenter()} />
      </GoogleMap>
    );
  })
);

@Darksoulsong this repo is unmaintained more than a year, please refer to npm @react-google-maps/api


TestCafe tries to click to incorrect place in iframe

What is your Scenario?
Click an element in the iframe
What is the Current behavior?
TestCafe clicks on the incorrect place
What is the Expected behavior?
It should click on the specified element
What is your public website URL? (or attach your complete example)
https://js.devexpress.com/Demos/WidgetsGallery/Demo/ActionSheet/Basics/jQuery/Light/
What is your TestCafe test code?
fixture`Proxyless`.page`https://js.devexpress.com/Demos/WidgetsGallery/Demo/ActionSheet/Basics/jQuery/Light/`;

test('Test', async t => {
    await t
        .wait(1000)
        .switchToIframe('#demoFrame');
        await t.eval(() => {
            document.body.addEventListener('click', ev => console.dir(ev), true);
            document.body.addEventListener('mouseup', ev => console.dir(ev), true);
        });
        await t
            .click('#button')
            // .expect(Selector('.dx-toolbar-center').withText('Choose action').visible).ok()
            .debug();
});

Your complete configuration file
No response
Your complete test report
No response
Screenshots
No response
Steps to Reproduce
Just run the test.
TestCafe version
2.4.0
Node.js version
18.12.1
Command-line arguments
npx testcafe chrome test.js --experimental-proxyless
Browser name(s) and version(s)
No response
Platform(s) and version(s)
No response
Other
No response

The issue consists of two problems:

incorrect calculation of position for mouse events in frames, because of scrolling in the parent containers.
incorrect calculation of scrolling when fixed header overlaps target element


Tasks: Dataview shows empty tasks

What happened?
I create empty task lists (e.g. for templates). In data view these get picked up as tasks however and shown in the overview.
s. first bullet in this dataview list (see image)

Expected behaviour:
Empty tasks are not shown in the Dataview result. So if there is only a linebreak or space after the - [ ]` then the item should not appear in the  dataview list.
DQL
task from #todo/Business
where !completed

JS
No response
Dataview Version
0.5.64
Obsidian Version
1.5.8
OS
Linux

https://xkcd.com/1172/

what you state as bug, is a feature.
if this is getting solved, someone else will pick up on it and suggerst a reversal.
this is not a bug. 100% agreeing on @holroy as it can be achieved by just creating a more complex query.


Feature:  Add Celebration and Encouragement Effects for Game Outcomes

To improve the user experience in the Tic-Tac-Toe game, I suggest adding the following effects:
For Winning:
Visual: Implement a celebration effect, to acknowledge the win.
Audio: Play a victory sound when a player wins.
For Losing:
Visual: Display an encouraging message with an animated character to motivate players.
Audio: Include a supportive message when a player loses.
Benefits: These enhancements will make the game more engaging and enjoyable for players

To improve the user experience in the Tic-Tac-Toe game, I suggest adding the following effects:
For Winning: Visual: Implement a celebration effect, to acknowledge the win. Audio: Play a victory sound when a player wins.
For Losing: Visual: Display an encouraging message with an animated character to motivate players. Audio: Include a supportive message when a player loses.
Benefits: These enhancements will make the game more engaging and enjoyable for players

go for it , please put a short video before pr1

@Sitambhra02, if you're not actively working on this issue, would it be possible for me to get assigned?

Hey, @iamparas0 I am interested in this issue can you assign this issue too me ..
As after winning the game it will show the emoji section. and bluster section a had ...//
I believe these changes will significantly enhance the overall user experience.


Blocks are not properly introduced in the documentation

Blocks and "pipe arguments" syntax is never sufficient explained in the documentation. The section https://crystal-lang.org/docs/syntax_and_semantics/blocks_and_procs.html introduces this syntax matter-of-factly. And even earlier, in https://crystal-lang.org/docs/syntax_and_semantics/literals/proc.html , the "pipe" syntax is being used, despite not having been explained before.
Moreover, the difference between block and procs is never properly explained, despite the name of the section. Why would I want to convert a block to a proc? Why do I have separate "pipe" and "arrow" syntaxes?
This is very confusing for people coming from other languages. The "block" syntax and concept is pretty much unique to Ruby and needs proper explanation.
Compare that to the documentation of the other language that uses "pipe" syntax, note the comprehensiveness and clarity: https://doc.rust-lang.org/1.1.0/book/closures.html

@kyegupov What is the "pipe" syntax?

@bew I'd guess it's about block usage variations:
3.times do |i|
  puts i
end

# vs

3.times &->puts(Int32)

It's not really a pipe syntax, it's the block syntax for passing parameters to the block content:
def foobar
  yield "hello", "world"
end

# Works with normal blocks (using: do ... end}
foobar do |arg1, arg2|
  # this is the block content
  # arg1 & arg2 are the arguments passed to the block
  pp arg1 # => "hello"
  pp arg2 # => "world"
end

# Works also with blocks inline blocks (using: { ... })
only_arg2 = foobar { |arg1, arg2| return arg2 }
pp only_arg2 # => "world"

@bew yes, of course. The thing is, the block syntax is NEVER explained in the documentation. I cannot find it properly introduced anywhere.

@kyegupov Writing docs for a language is very hard. Many concepts are tangled. Also said here

You can read this document from top to bottom, but it’s advisable to jump through sections because some concepts are interrelated and can’t be explained in isolation.

@asterite I wouldn't have problem with it being explained out of order, but there - just - is - no - explanation - of - what - a - "block" - is, at all. No mention of the | character, no explanation of how argument passing works, no explanation when one needs to chose blocks and when procs.
Writing a good documentation is hard indeed. And that's why I have submitted this issue: to point out a glaring omission in it that needs to be fixed.

It's explained here: https://crystal-lang.org/docs/syntax_and_semantics/blocks_and_procs.html
The idea is to learn from the examples there.

That section is very cryptic and can use a lot of improvement, that's precisely my point. Consider this:

The yield expression is similar to a call and can receive arguments.

"similar to a call" - what does that mean? What's the similarity, and where does it end?
"receive arguments" - um, ambiguous, isn't it the block that actually will "receive" the arguments? Anyway, it would be a good place to add something like:

The block indicates the arguments it will accept via the "pipe" characters |. That makes the block similar to a function which does not have a name.

There's the last question (what's the difference between block and procs and why do both exist), but I cannot suggest anything here because I don't understand it myself.
"Learning from examples" is maybe okay for a tutorial. But this is the reference documentation for a language we're talking about. It has to be comprehensive, strict, detailed and unambiguous.
For comparison, please see the Ruby reference documentation on this matter: http://ruby-doc.org/core-2.4.1/doc/syntax/calling_methods_rdoc.html

This discussion belongs in the book's repo: https://github.com/crystal-lang/crystal-book/issues/118. Please let's continue there if necessary.


botocore 1.14.4 blocks users from updating docutils to 0.16

Hi!
When botocore is used in a virtualenv next to other packages or in context of a whole GNU/Linux distribution, this line in setup.py
https://github.com/boto/botocore/blob/70c7767374c42bd86a896391dff55fc25ebfac27/setup.py#L27
blocks users from updating to docutils 0.16 which is not ideal. Can the upper boundary be dropped or be turned into semver-like <1 at least to be more friendly to other packages and user freedom?
Thanks and best, Sebastian
PS: I have seen #900 and #933 (but I don't consider this the right direction while docutils is imported from public botocore API).

@moseb - Thank you for your post. Marking this as enhancement.

This is not an enhancement, It's a bug.

Hi, our stack users run into:
ERROR: botocore 1.15.36 has requirement docutils<0.16,>=0.10, but you'll have docutils 0.16 which is incompatible.

@swetashre: Could you have a look into https://github.com/boto/botocore/pull/2011? It's an updated fix for this issue.

Same issue here. Thanks to the very useful utility pipdeptree for making it easy to dig up issues (https://pypi.org/project/pipdeptree/)
Warning!!! Possibly conflicting dependencies found:
* botocore==1.16.20
 - docutils [required: >=0.10,<0.16, installed: 0.16]

Would be nice to have this constraint removed; docutils==0.16.0 was released nearly six months ago.

@edrozenberg: since you are using system packages from Slackware, a workaround might be adding the patch at #2011 to the botocore package on Slackware, like what I did for Arch Linux [1].
[1] https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/python-botocore&id=4f4eecd0bf7719bdc77856c1f40e3466e94ad8db

@yan12125 Thanks! That would certainly do it and I'll consider applying that sometime. For now I'll just ignore the issue since I don't care about building boto docs.

not sure that helps those that want to install from pip

I rebased my branch on top of botocore 1.6.23. Before my branch is merged, you can use the following command to install my branch:
pip install git+https://github.com/yan12125/botocore@issue-1942-allow-use-with-docutils-0-16

that does help some, but others have to use pip (openstack uses only released packages for instance).

It would be nice to have this dependency removed. This issue is going to break a lot of projects in October when PIP starts using its new dependency resolver in PIP version 20.3 (https://pip.pypa.io/en/stable/user_guide/#changes-to-the-pip-dependency-resolver-in-20-2-2020). This version of PIP will be more strict with respect to pinned dependencies.

@swetashre can you loabel this a bug rather than a feature request? Playing nice with other packages in the environment and not blocking updates does not seem a feature request to me. Also, everyone who uses Dependabot needs to blacklist docutils. Thank you.

Hey @erdseb, as we said in #2121 this is pinned because it's a requirement for the project. 0.16 has breaking changes to the docutils API and until that's resolved we cannot upgrade. We currently have work underway to get everyone unblocked.
For reference, could anyone in this thread share some examples of libraries that are requiring 0.16 explicitly?

@nateprewitt my sole point above is that it's a bug, not a feature request.

@erdseb, sure, we definitely agree the issue has been problematic for users. To be clear though, libraries should be able to select appropriate dependencies and you'll find this is done in many major Python libraries. Not supporting the latest release of a dependency isn't a bug in a library, it's a feature support issue, which is why this has the chosen categorization.
In regards to pip's dependency resolver, this issue should actually become less problematic after that's been released due to a more intelligent dependency resolution scheme.

@erdseb, sure, we definitely agree the issue has been problematic for users. To be clear though, libraries should be able to select appropriate dependencies and you'll find this is done in many major Python libraries. Not supporting the latest release of a dependency isn't a bug in a library, it's a feature support issue, which is why this has the chosen categorization.

@nateprewitt you can pick a dependency but if your code depended e.g on Windows 95 and would not work with Windows 10, in 2020 that's a bug in my book. I'm exaggerating to make a point, software does not live in a vacuum. If it's a feature rather than a bug in your book, we can agree to disagree.

In regards to pip's dependency resolver, this issue should actually become less problematic after that's been released due to a more intelligent dependency resolution scheme.

Could you elaborate how the new resolver will be able to improve the situation with this very problem?

Could you elaborate how the new resolver will be able to improve the situation with this very problem?

0.16 is a seldomly used version of docutils, specifically because it's both new and has an inappropriately specified breakage. Current adoption 0.16 is at ~12% compared to 0.15.2 which accounts for 82% of all docutils downloads [source].
Most libraries support a range of values for a given dependency. The way pip currently works is it treats projects as being in a vacuum. It will install the latest version of a dependency for one project and then move on to install the next projects dependencies, which is why you're hitting these conflicts. With the new resolver, it will evaluate the dependency closure holistically, and realize that 0.15.2 satisfies the requirements of all projects and elect to use that. You can demo this pretty quickly by creating a project that requires botocore and docutils <= 0.17, then installing it with and without the resolver.
The only case this wouldn't work is if a dependency specifies docutils >= 0.16, which I'm unable to find any major projects currently doing this.

I will say, openstack (which includes docutils just about everywhere) is blocked on updating docutils due to botocore (and only botocore).

Great to see docutils is finally removed as a dependency in #2154. Looking forward to a new release of botocore.

This should now be resolved in botocore 1.18.0.