Avoid treating single server as cluster

Because the $parameters configuration is required to be an array and because Predis defaults to cluster configuration for array parameters, I can't see a clear way to solve this. I've only got one server and I don't want to use any cluster functionality.
How do I configure this bundle for this?

I'm investigating the problem and I'll give answer for you

If you are going to use an array to specify parameters for a single Redis node then you should use a named array:
$parameters: { host: '<IP_ADDRESS>', port: 6379, read_write_timeout: 0 }

Plain indexed arrays, even when only one element is specified, are interpreted as a set of connection parameters for multiple nodes which ends up enabling client-side sharding.

Thanks! But how about if I want to use a full URL? This is what I had:
$parameters: ["%env(REDIS_URL)%"]

You can trying:
$parameters: { default: "%env(REDIS_URL)%" }

So, no solution for that use case then? :)

I thought you already found a solution)
I will study this question in the near future and I will answer

Thanks! I actually had to drop this bundle and wire in Predis myself. Would love to cut that out and go with yours though.

Hello, i have the same issue cant't add multi redis server in the .env file is there a solution ?

Hello,
I'm having the same issue.
When I try to execute this
$this->client->flushall();

I have this error : Cannot use 'FLUSHALL' over clusters of connections.
My configuration look like this
sb_redis:
    clients:
        default:
            $options:    []
            $parameters: ['%env(REDIS_URL)%']

Is there any workaround for this ?

Hi all!
This problem was fixed in version 2.2.
Thank you all for issue!


init.py files included despite pyproject.toml negating them

Environment

interrogate version(s) (interrogate --version: version 1.5.0
Operating System(s): Mac OS Ventura 13.2.1
Python version(s): 3.10.9

Description of the bug
pyproject.toml option ignore-init-module = true gets honoured when interrogate is launched from command line, but is NOT honoured when invoked from pre-commit
What you expected to happen
I would expect my init.py to be ignored when interrogate is invoked either way (command line or pre-commit)
How to reproduce (as minimally and precisely as possible)
.pre-commit-config.yaml contains the following:
repos:
  - repo: https://github.com/econchick/interrogate
    rev: 1.5.0
    hooks:
      - id: interrogate

pyproject.toml
[tool.interrogate]
ignore-init-method = true
ignore-init-module = true
ignore-magic = false
ignore-semiprivate = false
ignore-private = false
ignore-property-decorators = false
ignore-module = false
ignore-nested-functions = false
ignore-nested-classes = true
ignore-setters = false
fail-under = 95
exclude = ["docs", "rja_dev"]
ignore-regex = ["^get$", "^mock_.*", ".*BaseClass.*"]
# possible values: 0 (minimal output), 1 (-v), 2 (-vv)
verbose = 1
quiet = false
whitelist-regex = []
color = true
omit-covered-files = false
generate-badge = "."
badge-format = "svg"

Run from pre-commit:
(memaback-py3.10) (base) bob@Roberts-Mac-mini memaback % pre-commit run --all-files
interrogate..............................................................Failed
- hook id: interrogate
- exit code: 1

= Coverage for /Users/bob/Documents/work/code/memaback/ =
- Summary -
| Name                                         | Total | Miss | Cover | Cover% |
|----------------------------------------------|-------|------|-------|--------|
| src/memaback/__init__.py                     |     1 |    1 |     0 |     0% |
| src/memaback/mema_fetch_article_url.py       |     8 |    0 |     8 |   100% |
| src/memaback/mema_nlp_ensemble_experiment.py |    16 |    0 |    16 |   100% |
| tests/__init__.py                            |     1 |    1 |     0 |     0% |
| tests/test_mongoconn.py                      |     2 |    0 |     2 |   100% |
|----------------------------------------------|-------|------|-------|--------|
| TOTAL                                        |    28 |    2 |    26 |  92.9% |
- RESULT: FAILED (minimum: 95.0%, actual: 92.9%) -
Generated badge to /Users/bob/Documents/work/code/memaback/interrogate_badge.svg

Anthing else we need to know?

Add pass_filenames: false to your hook. See: https://github.com/econchick/interrogate/issues/60#issuecomment-735436566

Thank you!


[BUG]crush app

I copied this error log in log file.
The app crushed.
FileNotFoundError: [Errno 2] No such file or directory: 'D:\RokTracker\deps\inputs\kingdom_1_person_scroll.txt'
2024-08-17 15:36:54 scanner INFO Kills for BigMᴀxɪмus2 (78701409) reconstructed, t1 might be off by up to 4 kills.
2024-08-17 15:37:05 kingdom_scanner_ui CRITICAL Uncaught exception
Traceback (most recent call last):
File "threading.py", line 1045, in _bootstrap_inner
File "threading.py", line 982, in run
File "kingdom_scanner_ui.py", line 607, in launch_scanner
"760x200",
File "roktracker\kingdom\scanner.py", line 513, in start_scan
track_inactives,
^^^^^^^^^
File "roktracker\kingdom\scanner.py", line 233, in scan_governor
)
File "roktracker\utils\adb.py", line 121, in adb_send_events
except:
FileNotFoundError: [Errno 2] No such file or directory: 'D:\RokTracker\deps\inputs\kingdom_1_person_scroll.txt'

Hello. It complains that the scroll script is missing. Normally that should not happen. That file got moved to a different folder with one of the last commits, but there also the python file got changed to work with the change. It's best to only use the released versions instead of cloning this repository if you do not intent to change some things.


Suggestion: Better relationship

Steps to reproduce
Consider some relationship between models:
{
  plugins: [
    service('folders', {
      instanceDefaults: {
        parentFolder: 'Folder',
      },
    }),
    service('files', {
      instanceDefaults: {
        parentFolder: 'Folder',
      },
    }),
  ],
}

Relationship can be deeply nested like
File -> Folder -> Folder -> Folder -> Folder -> etc.
Finding a file:
$FeathersVuex.File.find({
  query: {
    _id: 'blahblah',
    $populate: {
      path: 'parentFolder',
      populate: 'parentFolder',
    }
  }
})

Actual behavior
Server will return the structure like:
[{
  _id: 'blahblah',
  parentFolder: {
    _id: 'folderID1',
    parentFolder: {
      _id: 'folderID2',
      parentFolder: 'folderID3',
    },
  },
}]

But FeathersVuex will parse every parentFolder field as the Folder model, even the 'folderID3' string, so the FeathersVuex will return like this:
[{
  _id: 'blahblah',
  parentFolder: {
    _id: 'folderID1',
    parentFolder: {
      _id: 'folderID2',
      parentFolder: {
        0: 'f',
        1: 'o',
        2: 'l',
        3: 'd',
        4: 'e',
        5: 'r',
        6: 'I',
        7: 'D',
        8: '2',
        9: 'f',
      },
    },
  },
}]

Expected behavior
FeathersVuex won't parse fields, which intended to be an object, but actually they are not (because they store only the id currently)
It could remember about this missing relationship and replace id string with the object when it's fetched in the future
System configuration
Mongo DB
Mongoose
feathers-vuex 1.7.0

Thanks for the feedback @FedorSherbakov.  I completely agree that this was a design flaw from the beginning.  It has already been fixed in the latest pre-release.  I recommend using the latest pre-release.  Instructions are in the PR for the huge update, which will be released soon with V4 authentication plugin support.


Supporting zero-size Mmap?

This test shows that mapping an empty file returns an error:
https://github.com/RazrFalcon/memmap2-rs/blob/27ece7685bfc4fe9909c396a651dc52306393a22/src/lib.rs#L978-L992
I assume this is because the underlying OS APIs do not support creating a zero-size mapping but it is unsatisfying, since in some cases it forces callers to handle that special case. What do you think of having the Mmap and MmapMut structs handle this case by not creating an actual mapping but not erroring when the length is zero, and instead have Deref return &[]?

I'm not the one who wrote this code, so I'm not sure. I guess this is a Unix limitation. From mmap(2):

The length argument specifies the length of the mapping (which must be greater than 0).

Overall, yes I think we can allow it.

There’s more discussion of this here: https://github.com/danburkert/memmap-rs/issues/72
The idea of creating a mapping of always at least one memory page even if Deref ends up slicing it to zero size seems promising.


Plugins

https://yourdomain.com/admin/?config=true
How to activated plugins from config.php ?

You can edit this file, https://github.com/dignajar/gris/blob/master/bl-kernel/admin/themes/gris/config.php and add the plugins you need, then go to the link https://yourdomain.com/admin/?config=true

I've done it in https://github.com/dignajar/gris/blob/master/bl-kernel/admin/themes/gris/config.php but there's no change in admin panel.
Which code should be changed?


[SPARK-43157][SQL] Clone InMemoryRelation cached plan to prevent cloned plan from referencing same objects

What changes were proposed in this pull request?
This is the most narrow fix for the issue observed in SPARK-43157. It does not attempt to identify or solve all potential correctness and concurrency issues from TreeNode.tags being modified in multiple places. It solves the issue described in  SPARK-43157 by cloning the cached plan when populating InMemoryRelation.innerChildren. I chose to do the clone at this point to limit the scope to tree traversal used for building up the string representation of the plan, which is where we see the issue. I do not see any other uses for TreeNode.innerChildren. I did not clone any earlier because the caching objects have mutable state that I wanted to avoid touching to be extra safe.
Another solution I tried was to modify InMemoryRelation.clone to create a new CachedRDDBuilder and pass in a cloned cachedPlan. I opted not to go with this approach because CachedRDDBuilder has mutable state that needs to be moved to the new object and I didn't want to add that complexity if not needed.
Why are the changes needed?
When caching is used the cached part of the SparkPlan is leaked to new clones of the plan. This leakage is an issue because if the TreeNode.tags are modified in one plan, it impacts the other plan. This is a correctness issue and a concurrency issue if the TreeNode.tags are set in different threads for the cloned plans.
See the description of SPARK-43157 for an example of the concurrency issue.
Does this PR introduce any user-facing change?
Yes. It fixes a driver hanging issue the user can observe.
How was this patch tested?
Unit test added and I manually verified Dataset.explain("formatted") still had the expected output.
spark.range(10).cache.filter($"id" > 5).explain("formatted")

== Physical Plan ==
* Filter (4)
+- InMemoryTableScan (1)
      +- InMemoryRelation (2)
            +- * Range (3)

(1) InMemoryTableScan
Output [1]: [id#0L]
Arguments: [id#0L], [(id#0L > 5)]

(2) InMemoryRelation
Arguments: [id#0L], CachedRDDBuilder(org.apache.spark.sql.execution.columnar.DefaultCachedBatchSerializer@418b946b,StorageLevel(disk, memory, deserialized, 1 replicas),*(1) Range (0, 10, step=1, splits=16)
,None), [id#0L ASC NULLS FIRST]

(3) Range [codegen id : 1]
Output [1]: [id#0L]
Arguments: Range (0, 10, step=1, splits=Some(16))

(4) Filter [codegen id : 1]
Input [1]: [id#0L]
Condition : (id#0L > 5)

I also verified that the InMemory.innerChildren is cloned when the entire plan is cloned.
import org.apache.spark.sql.execution.SparkPlan
import org.apache.spark.sql.execution.columnar.InMemoryTableScanExec
import spark.implicits._

def findCacheOperator(plan: SparkPlan): Option[InMemoryTableScanExec] = {
  if (plan.isInstanceOf[InMemoryTableScanExec]) {
    Some(plan.asInstanceOf[InMemoryTableScanExec])
  } else if (plan.children.isEmpty && plan.subqueries.isEmpty) {
    None
  } else {
    (plan.subqueries.flatMap(p => findCacheOperator(p)) ++
      plan.children.flatMap(findCacheOperator)).headOption
  }
}

val df = spark.range(10).filter($"id" < 100).cache()
val df1 = df.limit(1)
val df2 = df.limit(1)

// Get the cache operator (InMemoryTableScanExec) in each plan
val plan1 = findCacheOperator(df1.queryExecution.executedPlan).get
val plan2 = findCacheOperator(df2.queryExecution.executedPlan).get

// Check if InMemoryTableScanExec references point to the same object
println(plan1.eq(plan2))
// returns false// Check if InMemoryRelation references point to the same object

println(plan1.relation.eq(plan2.relation))
// returns false

// Check if the cached SparkPlan references point to the same object
println(plan1.relation.innerChildren.head.eq(plan2.relation.innerChildren.head))
// returns false
// This shows the issue is fixed

rerun tests

+CC @cloud-fan, @dongjoon-hyun who have reviewed work on explain output earlier.

Thank you for pinging me, @mridulm .
Also, cc @sunchao

I agree that we do need to copy the cached plan when getting it, but I feel the current change is hard to understand and reason about.
I think a better place to fix is CacheManager#useCachedDataInternal. It does copy InMemoryRelation but does not copy the physical plan:
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/CacheManager.scala#L298-L306
We can add a new method InMemoryRelation#freshCopy which takes new output attributes and copy the physical plan, then we change cached.cachedRepresentation.withOutput(currentFragment.output) to cached.cachedRepresentation.freshCopy(currentFragment.output)

I agree that we do need to copy the cached plan when getting it, but I feel the current change is hard to understand and reason about.
I think a better place to fix is CacheManager#useCachedDataInternal. It does copy InMemoryRelation but does not copy the physical plan: https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/CacheManager.scala#L298-L306
We can add a new method InMemoryRelation#freshCopy which takes new output attributes and copy the physical plan, then we change cached.cachedRepresentation.withOutput(currentFragment.output) to cached.cachedRepresentation.freshCopy(currentFragment.output)

The challenge with this approach is that InMemoryRelation does not get the physical plan passed in directly. It is through CachedRDDBuilder. I originally tried making a new CachedRDDBuilder with a copy of the physical plan, but it broke other tests due to the private state it maintains.

I see, can we change def cachedPlan: SparkPlan = cacheBuilder.cachedPlan to lazy val cachedPlan: SparkPlan = cacheBuilder.cachedPlan.clone with comments to explain it? This makes sure that a new instance of InMemoryRelation will have a new instance of the physical plan.

@cloud-fan Cloning the cachedPlan is also problematic because it contains state (accumulators in private fields) when it includes a CollectMetricsExec operator. CollectMetricsExec.collect specifically looks at the InMemoryRelation.cachedPlan to get the stateful metrics.
I verified this is an issue by cloning InMemoryRelation.cachedPlan. Then I modified a unit test that uses Dataset.observe to cache the dataset. This breaks the unit test. When I revert cloning the cachedPlan it passes. Here is how I modified the unit test to prove the issue.
diff --git a/sql/core/src/test/scala/org/apache/spark/sql/util/DataFrameCallbackSuite.scala b/sql/core/src/test/scala/org/apache/spark/sql/util/DataFrameCallbackSuite.scala
index f046daacb91..3de33e3e1b2 100644
--- a/sql/core/src/test/scala/org/apache/spark/sql/util/DataFrameCallbackSuite.scala
+++ b/sql/core/src/test/scala/org/apache/spark/sql/util/DataFrameCallbackSuite.scala
@@ -277,7 +277,7 @@ class DataFrameCallbackSuite extends QueryTest
         max($"id").as("max_val"),
         // Test unresolved alias
         sum($"id"),
-        count(when($"id" % 2 === 0, 1)).as("num_even"))
+        count(when($"id" % 2 === 0, 1)).as("num_even")).cache()
       .observe(
         name = "other_event",
         avg($"id").cast("int").as("avg_val"))

So I think we should stick with only cloning it for the innerChildren since the only usage is the ExplainUtils and statefulness doesn't matter, besides the TreeNode.tag values.

thanks, merging to master/3.4!

I'm revisiting this PR since it introduced a new issue https://issues.apache.org/jira/browse/SPARK-47177 I don't have a clear idea yet how to fix this, a few ideas out of my head:

maybe we just a coarse granularity lock in explain?
alternatively, make innerChildren a function: clone the initial plan, every time check for whether the original AQE plan is finalized (making the final flag atomic first, of course), if no: return the cloned initial plan, if it's finalized: clone the final plan and return that one. But still this won't be able to reflect the AQE plan in real time, in a concurrent situation, but at least we have initial version and final version.

cc @cloud-fan to provide some feedback

Had a discussion with @maryannxue , a few thoughts:

might not be a good idea to implicitly override innerChildren with clone behavior? it's a generate function from base class, even if it's only used for generateString for now. If we're trying to narrowly fix the explain issue, is it possible to hold a lock on callsite?
apart from explain string, is there any other usage that could be vulnerable to concurrency issue?

@liuzqt in theory this issue is not limited to explain string. The core issue is that TreeNode.tags introduces mutability into an otherwise immutable plan. This is mostly fine because a cloned plan creates all new objects, including the TreeNode.tags object. The problem is the caching operators do not get cloned when the plan is cloned. The object will be referenced by the old and new plan. So any TreeNode.tags mutation now risks concurrency issues. Explain string is not the only place that modifies the tags (look for TreeNode.setTagValue usage) so the more narrow fix does not solve the vulnerability. As a long term solution I think mutability (the tags) should be removed from plans, but I know that is not the most practical suggestion for you right now.

@liuzqt another idea for a narrow explain utils fix is to move the QueryPlan.OP_ID_TAG currently stored in the TreeNode.tags into a thread local map maintained in explain utils. This would keep the same state and eliminate the concurrency issue here by not using the tags.


Add labelWidget property to BottomNavigationBarItem

Description
This PR adds a labelWidget property to BottomNavigationBarItem.
Motivation : https://github.com/flutter/flutter/issues/104234#issuecomment-1138946867
Implementation inspiration : https://github.com/flutter/flutter/pull/104673
Related Issue
Fixes https://github.com/flutter/flutter/issues/104234
Tests
Adds 4 tests.

Semi related https://github.com/flutter/flutter/issues

Semi related https://github.com/flutter/flutter/issues

@cedvdb FYI, the issue number is missing from the link you shared.

thanks, fixed

Closing this PR because it was implemented according to https://github.com/flutter/flutter/pull/104673 which was closed in favor of https://github.com/flutter/flutter/pull/109179.
https://github.com/flutter/flutter/pull/109179 doesn't promote a labelWidget property.


merge sort in golang

implementation of bubble sort algorithm using golang

@murilosrg thanks, make sure you star the repository for the confirmation of the contribution and check this issue out, thanks.


Bump dependencies

This PR updates the dependency on latest base and on external dependencies.

The build depends on merging (this PR in base)[https://github.com/SpineEventEngine/base/pull/802].


Limit submission date

In newer versions of Angular Material implemented md-datepicker directive with attributes md-min-date and md-max-date.
Issue freezed. Need to resolve #39 first


Enhanced agent log

Link #27, #28

All log levels of Brolog are supported.
log.error()
log.warn()
log.info()
log.verbose()
log.silly()

To turn off all logs, use log.level('silent') or log.level(0)

It seems that something is not correct because the CI was failed.
Could you please try to run the npm test locally and make sure everything is working as expected in your PR?
I'll take a look at it later.


ci: back up on version specification

The released action is now v1.2.0, so v1, should be enough to specify the correct version.
Please take a look.

Codecov Report

Merging #1540 (d7a1735) into master (1858083) will decrease coverage by 0.07%.
The diff coverage is 94.02%.

@@            Coverage Diff             @@
##           master    #1540      +/-   ##
==========================================
- Coverage   71.46%   71.39%   -0.08%
==========================================
  Files         489      473      -16
  Lines       54288    53941     -347
==========================================
- Hits        38797    38511     -286
+ Misses      13086    13051      -35
+ Partials     2405     2379      -26

Impacted Files
Coverage Δ

graph/path/disjoint.go
66.66% <73.33%> (+2.38%)
:arrow_up:

mat/cdense.go
61.06% <85.96%> (+23.23%)
:arrow_up:

graph/multi/directed.go
92.06% <100.00%> (+1.58%)
:arrow_up:

graph/multi/undirected.go
91.04% <100.00%> (+2.69%)
:arrow_up:

graph/multi/weighted_directed.go
94.83% <100.00%> (+0.80%)
:arrow_up:

graph/multi/weighted_undirected.go
92.94% <100.00%> (+3.67%)
:arrow_up:

graph/path/spanning_tree.go
91.17% <100.00%> (+0.26%)
:arrow_up:

internal/asm/c64/conj.go
0.00% <0.00%> (-100.00%)
:arrow_down:

graph/flow/control_flow_lt.go
87.50% <0.00%> (-8.93%)
:arrow_down:

interp/interp.go
100.00% <0.00%> (ø)

... and 18 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 88ac045...d7a1735. Read the comment docs.

Codecov Report

Merging #1540 (d7a1735) into master (1858083) will decrease coverage by 0.07%.
The diff coverage is 94.02%.

@@            Coverage Diff             @@
##           master    #1540      +/-   ##
==========================================
- Coverage   71.46%   71.39%   -0.08%
==========================================
  Files         489      473      -16
  Lines       54288    53941     -347
==========================================
- Hits        38797    38511     -286
+ Misses      13086    13051      -35
+ Partials     2405     2379      -26

Impacted Files
Coverage Δ

graph/path/disjoint.go
66.66% <73.33%> (+2.38%)
:arrow_up:

mat/cdense.go
61.06% <85.96%> (+23.23%)
:arrow_up:

graph/multi/directed.go
92.06% <100.00%> (+1.58%)
:arrow_up:

graph/multi/undirected.go
91.04% <100.00%> (+2.69%)
:arrow_up:

graph/multi/weighted_directed.go
94.83% <100.00%> (+0.80%)
:arrow_up:

graph/multi/weighted_undirected.go
92.94% <100.00%> (+3.67%)
:arrow_up:

graph/path/spanning_tree.go
91.17% <100.00%> (+0.26%)
:arrow_up:

internal/asm/c64/conj.go
0.00% <0.00%> (-100.00%)
:arrow_down:

graph/flow/control_flow_lt.go
87.50% <0.00%> (-8.93%)
:arrow_down:

interp/interp.go
100.00% <0.00%> (ø)

... and 18 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 88ac045...d7a1735. Read the comment docs.

Since this is not going to make the situation worse, but may fix the missing base report issue, I am going to merge this.
TBR

Since this is not going to make the situation worse, but may fix the missing base report issue, I am going to merge this.
TBR

:frowning_face:

:frowning_face:

Codecov are sending a PR to the action that should fix this.

Codecov are sending a PR to the action that should fix this.

:tada:

:tada:


Strange: cudnn5 make "average forward pass" slower?

What hardware and operating system/distribution are you running?
Operating system:  CentOS Linux release 7.4.1708
CUDA version:  cuda-8.0
CUDNN version:  cudnn.so.5
openCV version:  opencv2.4
BLAS:  openblas
Python version:  Python3.4
when I compile the caffe switch cudnn5 setting "USE_CUDNN := 1" and "# USE_CUDNN := 1", then execute the following commands, get and strange results that cudnn5 make channel_pruning "average forward pass" slower, which prototxt and caffemodel download from the link you give.
In order to give more information, I list the normal results and unnormal results in the first block and the second block respetively.
As I am not familar with CUDA and cuDnn, this strange things really makes me confused, thanks for your some comments.
#caffe/build/tools/caffe time -model temp/vgg.prototxt -weights temp/vgg.caffemodel -iterations 10 -gpu  0
# Average Forward pass: 242.853 ms.
# Average Backward pass: 713.927 ms.
# Average Forward-Backward: 956.982 ms.
##use cudnn5
# Average Forward pass: 198.034 ms.
# Average Backward pass: 356.98 ms.
# Average Forward-Backward: 555.226 ms.

#caffe/build/tools/caffe time -model temp/bn_vgg.prototxt   -weights temp/bn_vgg.caffemodel -iterations 10 -gpu 0
# Average Forward pass: 243.775 ms.
# Average Backward pass: 715.241 ms.
# Average Forward-Backward: 959.264 ms.
###use cudnn5
# Average Forward pass: 219.921 ms.
# Average Backward pass: 356.2 ms.
# Average Forward-Backward: 576.338 ms.

#caffe/build/tools/caffe time  -model temp/bak/cb_3c_3C4x_mem_bn_vgg.prototxt  -weights temp/bak/cb_3c_vgg.caffemodel  -iterations 10 -gpu 0
# Average Forward pass: 174.96 ms.
# Average Backward pass: 1008.17 ms.
# Average Forward-Backward: 1183.51 ms
###use cudnn
# Average Forward pass: 122.147 ms.
# Average Backward pass: 245.928 ms.
# Average Forward-Backward: 368.314 ms

#after finetune
#caffe/build/tools/caffe time -model temp/bak/cb_3c_3C4x_mem_bn_vgg.prototxt  -weights temp/bak/models/3C4X_iter_200000.caffemodel -iterations 10 -gpu  0
# Average Forward pass: 173.536 ms.
# Average Backward pass: 1004.33 ms.
# Average Forward-Backward: 1178.2 ms.
##use cudnn5
# Average Forward pass: 121.938 ms.
# Average Backward pass: 245.541 ms.
# Average Forward-Backward: 367.757 ms.

#caffe/build/tools/caffe time -model temp/channel_pruning.prototxt  -weights temp/channel_pruning.caffemodel -iterations 10 -gpu  0
# Average Forward pass: 114.38 ms.
# Average Backward pass: 485.261 ms.
# Average Forward-Backward: 599.849 ms.
##use cudnn5
# Average Forward pass: 300.156 ms.
# Average Backward pass: 119.61 ms.
# Average Forward-Backward: 419.968 ms.

#caffe/build/tools/caffe time -model temp/channel_pruning_VGG-16_3C4x.prototxt  -weights temp/channel_pruning_VGG-16_3C4x.caffemodel  -iterations 10 -gpu 0
# Average Forward pass: 164.283 ms.
# Average Backward pass: 985.954 ms.
# Average Forward-Backward: 1150.5 ms.
##use  cudnn5
**# Average Forward pass: 302.349 ms.**
# Average Backward pass: 227.605 ms.
# Average Forward-Backward: 530.039 ms.

https://github.com/yihui-he/channel-pruning/wiki/inference-time-on-GPU


event in onChange

Do you want to request a feature or report a bug?
feature(?)
What is the current behavior?
I hope to use event.stopPropagation(), but I cannot get event in onChange.
class MyEditor extends Component {
  constructor(props) {
    super(props);

    this.onChange = (editorState) => {
      // Is there a way to get event here?
    };
  }

  render() {
    // ...
    return (
      <Editor editorState={editorState} onChange={this.onChange} />
    );
  }
}

Originally asked on here on Stack Overflow. The detailed use case is also there.

Hi @Hongbo-Miao
Would it be possible if you can give a bit more context on what are you trying to do ?

Hi @mitermayer it is here. But I just copied here for convenience.
I have an editor, it loads data from Redux saved in IndexedDB. Since the selection (cursor) will lose, so I use localEditorState to maintain the cursor.
The editor has a wrapper. If user click the editor wrapper, I want to move the cursor to end. If user click the editor inside, I want the cursor use the selection info from localEditorState.
class Send extends PureComponent {
  constructor(props) {
    super(props);

    this.state = {
      localEditorState: EditorState.createEmpty(),
      shouldMoveCursorToEnd: false
    };

    // ...
  }

  componentDidMount() {
    const { loadEditor } = this.props;
    loadEditorFromIndexedDB();
  }

  onEditorWrapperClick() {
    const { editorState } = this.props;

    this.domEditor.focus();
    this.setState({ shouldMoveCursorToEnd: true });
  }

  onEditorChange(newEditorState) {
    // Without event.stopPropagation(), onEditorWrapperClick will also run, which is not what I want

    this.setState({ shouldMoveCursorToEnd: false });
    this.updateEditorText(newEditorState);
  }

  updateEditorText(newEditorState) {
    const { updateEditor } = this.props;

    this.setState({ localEditorState: newEditorState });

    updateEditor(newEditorState);
    this.saveToIndexedDB({ newEditorState });
  }

  render() {
    const { editorState } = this.props;
    const { localEditorState, shouldMoveCursorToEnd } = this.state;

    const editorStateWithSelection = shouldMoveCursorToEnd
      ? EditorState.moveFocusToEnd(editorState)
      : EditorState.acceptSelection(editorState, localEditorState.getSelection());

    return (
        <form onClick={this.onEditorWrapperClick}>
          <Editor editorState={editorStateWithSelection} onChange={this.onEditorChange} />
          <button type="submit">Send</button>
        </form>
    );
  }
}

export default Send;

Hi @Hongbo-Miao,
I am not sure I understand correctly your question, but if you are trying to update and save the editor selection based on user click interaction maybe you could use onFocus and onBlur they have the following signatures:
  onBlur?: (e: SyntheticEvent<>) => void,
  onFocus?: (e: SyntheticEvent<>) => void,

Hmm, I want when I click the editor inside, only trigger onEditorChange. But now because the event bubbles up to the wrapper. It will also trigger onEditorWrapperClick. Is there a way to stop that?

Hi @mitermayer I might need rethink the way I am doing it. I will report back if I find a better way.

So I end up with saving the mail editorState in state, it will get data from Redux
const newEditorState = EditorState.acceptSelection(EditorState.createWithContent(convertFromRaw(editor)), editorState.getSelection());
this.setState({ editorState: newEditorState });

This way can also avoid the main editorState slowing down because now it doesn't need go though convertToRaw and convertFromRaw every time.

Oh, no, still need event. I changed my structure but it won't help the cursor issue.
I still need when I click the editor inside, stop the event bubbles up to the wrapper.
Something like event.stopPropagation()

@Hongbo-Miao any news?

@Darex1991 It is too long. I already stop working on that project..

The issue has been over two years and it might not be applicable. Please create a new one if anyone in future meet similar issue. Thanks

Same issue...why would you mask native events?


Mismatch + missing version

You published version 0.1.1 instead of 0.1.11 and there is also no version to be found on crates.io

@ProbablyClem
There is still no version published on crates.io
Latest update was 3 months ago with v0.1.10

Wooops my bad, forgot to change the version number in the files


How to play audio when the app is in background mode?

YouTubePlayerKit Environment

YouTubePlayerKit version: 1.12
macOS version: 11.5.2
Xcode version: 13
Dependency manager (SPM, Manually): SPM

Hi @secret3579,
Playing audio in background or enabling PiP Mode must be enabled via the capabilities of your app.
https://developer.apple.com/documentation/avfoundation/media_playback_and_selection/configuring_the_audio_playback_of_ios_and_tvos_apps

Now, enable background mode and config session but not work
My update Example project
`//
//  App.swift
//  Example
//
//  Created by Sven Tiigi on 20.09.21.
//
import SwiftUI
import UIKit
import Foundation
import AVFoundation
// MARK: - App
// no changes in your AppDelegate class
class AppDelegate: NSObject, UIApplicationDelegate {
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool {
print(">> your code here !!")
let audioSession = AVAudioSession.sharedInstance()
do {
//                try audioSession.setCategory(.playAndRecord)
//                try audioSession.setCategory(.playback)
try audioSession.setCategory(.playback, mode: .default)
try audioSession.setActive(true)
} catch {
print("Setting category to AVAudioSessionCategoryPlayback failed.")
}
return true
}
}
/// The App
@main
struct App {
// inject into SwiftUI life-cycle via adaptor !!!
@UIApplicationDelegateAdaptor(AppDelegate.self) var appDelegate
}
// MARK: - SwiftUI.App
extension App: SwiftUI.App {
/// The content and behavior of the app
var body: some Scene {
WindowGroup {
ContentView()
}
}
}
`
[ProcessSuspension] 0x10c000900 - ProcessAssertion: Failed to acquire RBS assertion 'WebKit Media Playback' for process with PID=2868, error: Error Domain=RBSServiceErrorDomain Code=1 "(originator doesn't have entitlement com.apple.runningboard.assertions.webkit AND originator doesn't have entitlement

can i play YouTubePlayerKit with AVAudio ??? also in background?


Sprint 9 deployment

This is a Draft Pull Request

Please note: The CI check fails as Jenkins deploys the server itself and does not currently include logic to gracefully shutdown the deployment. This means that the check does in fact pass. This will be address to show passing in commit this evening.


Workshop Resource Maximums are not persistent

In the Workshop tree there are Max fields that limit how much of a resource will be automatically crafted. The values are default -1 (inf), but if you change the defaults, the settings are not persistent across a reset. There may be a bug or these options might not be added to the persistent state.
I'm thinking of using the Max settings in the context of a fast paragon farming run where I want to limit Eludium and Manuscripts. Limiting Eludium to approx ~150 allows Unob to accumulate in the current run and Microwarp Reactors to be purchased after the reset. Limiting Manuscripts allows Parchment to accumulate in the current run so that Festivals can start asap after the reset.

I can confirm that there is actually no code to persist this setting right now. I assume that I hoped to have this covered by moving to the new settings solution quicker, but we're not there yet.
I shall implement this in the legacy storage system to fix this issue. Great find!

Confirmed fixed. Thanks!

Once I've set a resource limit, it's stuck. How do I set the default? Everytime I reset now I have to go uncheck all the settings I used before.

@kanewinter You could use different settings states and switch between them, but we could also add a reset option to the resource control. Please open a new ticket about it though :)


Fix ExpansionTile Expanded/Collapsed announcement is interrupted by VoiceOver

fixes ExpansionTile accessibility information doesn't read Expanded/Collapsed (iOS)
Code sample

expand to view the code sample
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        appBar: AppBar(
          title: const Text('ExpansionTile'),
        ),
        body: const ExpansionTile(
          title: Text("Title"),
          children: <Widget>[
            Placeholder(),
          ],
        ),
        floatingActionButton: FloatingActionButton(
          onPressed: () {},
          child: const Icon(Icons.add),
        ),
      ),
    );
  }
}

Before
https://github.com/flutter/flutter/assets/48603081/542d8392-52dc-4319-92ba-215a7164db49
After
https://github.com/flutter/flutter/assets/48603081/c9225144-4c12-4e92-bc41-4ff82b370ad7
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

cc: @math1man

We agreed to fix this issue by delaying semantic announcement in https://github.com/flutter/flutter/issues/132264#issuecomment-1956801006. While https://github.com/flutter/flutter/issues/122101 is open.

@QuncCccccc
Can you please also check why this is failing Google Testing? Thanks!

@QuncCccccc Can you please also check why this is failing Google Testing? Thanks!

For this one, it failed several familylink tests and the exception message shows test failed on this assert: https://github.com/flutter/flutter/blob/f4ee956d3eea7524e37082e5d86f665d0a0bac2e/packages/flutter_test/lib/src/binding.dart#L1527
Same exception message as the PR 143443

@QuncCccccc Can you please also check why this is failing Google Testing? Thanks!

For this one, it failed several familylink tests and the exception message shows test failed on this assert:
https://github.com/flutter/flutter/blob/f4ee956d3eea7524e37082e5d86f665d0a0bac2e/packages/flutter_test/lib/src/binding.dart#L1527
Same exception message as the PR 143443

Future.delayed seems to have cause this issue so I've replaced it with Timer and tests are green.
Can you please review the changes and approve if it looks good.


Bluetooth: Controller: Periodic advertising - Sync transfer

Is your enhancement proposal related to a problem? Please describe.
Required for le-audio - transfer of broadcast sync from Broadcast Assistant to Scan Delegator (e.g. phone to hearing aid)
Requires long control PDUs
Will be blocked by new control procedures.
Makes sense to do after the BIS work is completed, and a more mature LLCP
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or graphics (drag-and-drop an image) about the feature request here.

Hello, I can't compile the PAST Peripheral example with west build -p always -b nrf52833dk_nrf52833 samples/bluetooth/peripheral_past
the error says : samples/bluetooth/peripheral_past/src/main.c:138: undefined reference to `bt_le_per_adv_sync_transfer_subscribe'
@cvinayak do you have any idea for the source of this issue ?
Thank you


new R exercises

Two new exercises showing more advanced ways of using R on the cluster are added. The first exercise shows how to run jobs on the cluster from within R with some extra functionality for the job management. The second shows how to parallelize Bayesian regression modeling with brms.

@achetverikov nice work! I will merge it right away.  You can check in few minutes on the hpcwiki website to see if everything is ok.  If everything is ok, we should announce it in the R MM channel.


try to fix densepose node #139

Fix issue #139
I tried the fixed models, but those seems lack of some thing. so I add these Functions and Classes from your colab notebook.
Besides, if the input image is big enough, the fixed model will return strang results below which I had no idea to fix it

So I use your colab notebook generated two models and uploaded them into huggingface.
I don`t kown what happened  exactlly but they seems work now.

Oh I didn't check this commit

Besides, if the input image is big enough, the fixed model will return strang results below which I had no idea to fix it
TorchScript tracing is kinda dumb when the resolution is different than traced input's resolution

Can you do a comparision between my new one and yours? I don't have time to test now.

I think this is the difference，I added height and width in the inference_func.
def inference_func(model, image):
    with torch.no_grad():  # https://github.com/sphinx-doc/sphinx/issues/4258

        _, height, width = image.shape

        inputs = {"image": image, "height": height, "width": width}

        outputs = predictor.model([inputs])[0]["instances"]

        pred_densepose = outputs.get("pred_densepose") if outputs.has("pred_densepose") else None

        return (
            outputs.get("pred_boxes").tensor.cpu(), #pred_boxes_XYXY
            pred_densepose.coarse_segm if pred_densepose else torch.Tensor([-1]), #coarse_segm
            pred_densepose.fine_segm if pred_densepose else torch.Tensor([-1]), #fine_segm
            pred_densepose.u if pred_densepose else torch.Tensor([-1]), #u
            pred_densepose.v if pred_densepose else torch.Tensor([-1]), #v
        )

Besides, my torchscript models can works on your code, and your model can also works on my code.
Small resolution can give better resolut.
Here are the results.
your model with your code（512）:

your model with my code（512）:

my model with your code (512):

my model with my code (512 and 1024):

It's too late yesterday and I'll try to solve conflicts today.

@Layer-norm You don't need to do that. I will revert my commit

Oops. My revert commit's message is a bit ambiguous 😅

Some users from banodoco Discord server says that there is a serve lagging on web browsers when previewing the the result from both your DensePose and mine.


Unhandled exception when cleaning (invalid) date header during restore.

Full steps to reproduce the issue:

Backup email with (invalid?) date header (Date: 2023-07-26 18:53:25.162982)
Restore email using --cleanup.

Expected outcome: GYB gracefully handles invalid date header, either:

Skipping message
OR using cleanup date

Actual outcome: GYB exits with unhandled exception:
Traceback (most recent call last):
  File "gyb.py", line 2767, in <module>
  File "gyb.py", line 2239, in main
  File "gyb.py", line 1928, in message_hygiene
  File "email\utils.py", line 200, in parsedate_to_datetime
ValueError: Invalid date value or format "2023-07-26 18:53:25.162982"
[26812] Failed to execute script 'gyb' due to unhandled exception!

Work-around: modify date header in offending .eml file to Date: Wed, 26 Jul 2023 18:53:25 +0900
Notes: the offending email is successfully restored if --cleanup is not used.

I modified my gyb.py to gracefully skip messages that throw exceptions while cleaning.


Layers list: Details what SDKs (JS/iOS/Android) support edited tags

So I guess another way to look at this would be to have a 'emulation mode' and filter out fields that are not supported on certain platforms. So if 'iOS emulation' was selected a number of fields would be disabled and marked as so in the editor.
My thinking is that listing what is supported might not be that helpful, because ultimately you want to target a style at a set of platforms. So if a feature is missing from a platform you want to see how that will effect your style.
Questions?

Does that make sense?
Is there something obvious I'm missing as to why that wouldn't work?
Any other thoughts?

What happens if a style with unsupported features is used with iOS/Android/macOS? Are they
ignored or is the style not working in general?

That's my understanding, we'd need to check though

It would be a lot of work to keep this all up-to-date with the style spec, in my opinion not possible to do it manually. Such emulation modes would need to be synced automatically with the style spec.

We have this information from the style-spec already, for example https://github.com/mapbox/mapbox-gl-js/blob/master/src/style-spec/reference/v8.json#L1019-L1025

There are also differences regarding what kind of features are supported within one platform, e.g. see SDK support for GeoJSON sources. So you would need a lot of different emulation modes.

True, I guess that's also true of the web target currently also though

True, I guess that's also true of the web target currently also though

Maybe it would be sufficiant to have an emulation mode only for the latest release of each platform.

@orangemug this issue remains open because of the emulation mode, right?

Correct @pathmapper, although I don't think it's something we should prioritise anytime soon.

Thanks @orangemug, updated the issue title.

And yeah, I also think this is something for later.


Refactoring Base-Tools

Refactoring toolbox.py and syssettings.py with @methodfunctions

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9047611-refactoring-base-tools?utm_campaign=plugin&utm_content=tracker%2F10782082&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F10782082&utm_medium=issues&utm_source=github).

Each file type a new class for the tool box.


Client should retry the request when receiving 409

Client should retry the request when receiving a 409 and 412  from the server.

@Tyriar FYI

We should also update the error message. From a user's perspectives, these mean nothing and don't provide any guidance.

@misolori These message are not supposed to be surfaced to user. Currently 412 error is handled and retried without bailing out. Can you please provide the settings sync log when you saw 412 ?

@sandy081 sorry I wasn't able to retrieve those logs, I'll see if it appears again.

Reopening for candidate discussion

@misolori I would recommend to file a separate issue for 412 scenario you are seeing.

Fix looks good, adding verified label.


 The main difference is that more complex expressions
can be made, and each aggregation must be named.

PS: this still WIP. I'm going to finish tomorrow.
But would be nice to have your opinion on how the API should look like. Is this what you expected?
I mean, like in the test: https://github.com/elixir-nx/explorer/pull/301/files#diff-a8dbae367a98eddc4049331a0ddc27690a3c9441ce21c663024f7d917cce9df5R229-R235

Beautiful!

@josevalim I think this is it. But we have some operations that don't work only for aggregations, like :first, :last and :count, that I skipped. We also have the :n_unique aggregation that does not have a correspondent function at Series, but have n_distinct that seems to do the same - we may need to rename one of them. I'm planning to tackle these missing gaps in another PR. WDYT?

@philss what do you mean about first/last/count not working only for aggregations? where else are they allowed?

Btw, let's go with n_distinct so it mirrors DataFrame.distinct (confirmed with @cigrainger). There are also other renames in https://github.com/elixir-nx/explorer/issues/289#issuecomment-1191134730, so we can likely tackle it all at once.

what do you mean about first/last/count not working only for aggregations? where else are they allowed?

@josevalim they are allowed in the common series. What I wanted to say is that they are not exclusive for aggregations. So using, for example, Series.count(ldf["column"]) can work for both grouped and ungrouped DFs.


Potential infinite loop in GSUB and GPOS execution

Currently, Allsorts doesn't seem to impose a limit on the iteration count during OpenType shaping. Therefore, a malicious font can trigger an infinite loop in Allsorts.
OpenType shaping can be shown to be equivalent to executing the instructions of a Turing machine. This means that there's no algorithm to reliably identify an attack font, ie. before actually executing the instructions in the GSUB and GPOS tables. (If there was such an algorithm, it would be equivalent to solving the Halting Problem for Turing machines).
Recommendation: Increment a counter for every GSUB and GPOS rule being executed. Give up when the counter exceeds a threshold. See the HarfBuzz code for a reasonable threshold value.
Test font and unit test:
https://rawgit.com/unicode-org/text-rendering-tests/master/reports/Allsorts.html#GSUB-3
Technically, this test case is not really triggering an infinite loop; rather, it is a tiny font that triggers a billion rewrite steps. Anyhow, you want to impose a limit on execution time and also on the size of the memory buffer during OpenType shaping.

Thanks for opening the ticket—I should have done that as I was aware this test was failing. Just hadn't got around to working on a fix.


Experimental Detection "Remote Desktop Network Traffic" False Positives

Rule Remote Desktop Network Traffic should be updated to disregard "blocked" traffic (e.g.: add ... AND All_Traffic.action = "allowed") to prevent false positives.

Merged a fix in #2403


Can not edit links that flow over two lines in editor

When a link flows over two lines, the edit- popup appears in the middle. Too far from the cursor to reach it without disappearing:

The only way to edit this link, is to first temporary delete some text in front of it so it no longer flows over two lines.

Closing as a duplicate of https://github.com/TryGhost/Ghost/issues/9792


.yaml and .yml file extension for .yaml content

We've got both in the source tree!
The Yaml FAQ suggests .yaml.
I really don't care which.. but I do object to a mixture of both.
Can we switch to .yaml?

.yaml works for me


Error while importing library

Error:org.gradle.api.UncheckedIOException: Could not HEAD 'https://jitpack.io/com/github/stfalcon/chatkit/0.1.2/chatkit-0.1.2.pom'. Received status code 401 from server: Unauthorized
Error:org.gradle.api.resources.ResourceException: Could not get resource 'https://jitpack.io/com/github/stfalcon/chatkit/0.1.2/chatkit-0.1.2.pom'.
I keep getting this error when trying to pull the library

Hi @judemanutd !
I can't reproduce your problem. Do you use gradle dependency:
compile 'com.github.stfalcon:chatkit:0.1.2'


Bail out from setting gutterMarkers if there's no line to set one for

Fixes #37
Signed-off-by: petetnt<EMAIL_ADDRESS>

published as 2.5.0

Thanks! 👍


Installing a package may create a user but not update the fact

Describe the bug
Operation server.user depends on the facts about the user to choose between using useradd and usermod. If the facts about users say that user does not exist, but in fact the user exists, pyinfra effectively does nothing.
To Reproduce
Create the following deploy.py file:
from pyinfra.operations import apt, server

apt.packages(name="Install postfix", packages=["postfix"], update=True)
server.group(name="Create group foo", group="foo", system=True)
server.user(
    name="Add user postfix to group foo", user="postfix", group="foo", system=True
)

Run pyinfra -vvvv --ssh-user root example.org deploy.py, where example.org is a freshly installed Ubuntu 22.04 VM.
Expected behavior
I expect that postfix package is installed and then pyinfra adds the user postfix to the group foo.
Instead, pyinfra does not add the user to the group, but checks that user exists and does not execute useradd.
--> Starting operation: Add user postfix to group foo
[example.org] >>> sh -c 'grep '"'"'^postfix:'"'"' /etc/passwd || useradd -d /home/postfix -g foo -r postfix'
[example.org] postfix:x:114:120::/var/spool/postfix:/usr/sbin/nologin
[example.org] >>> sh -c 'mkdir -p /home/postfix'
[example.org] >>> sh -c 'chown postfix:foo /home/postfix'
[example.org] Success

It should instead run usermod.
The solution would be to fix apt to update the facts about the users to include the information about the user postfix added by the post-install script.

v3 fixes this, now that the first beta is out I’ll close this issue.


Implement nip 20

Add support for https://github.com/nostr-protocol/nips/blob/master/20.md, so we can get an OK (or not ok) response for each event published.

As I commented in the pr #30 would be a good idea to have two implementations, one synchronous and other asynchronous

We should discuss if we want to implement this nip with a call back function or more like a wait until when publishing and event. Opinions?

If you just return a Promise the caller can choose to use await or not. Let's not use callbacks if possible.

As i see the response will come from the web socket of line 75 in *relay.js", so i dont think is posible to handle it on the pusblish function of pool.js. Maybe i dont understand correctly?

i tthink i get it, pr later :D

You can create a Promise and return it, but keep a reference to the resolve function of that promise, then call it when you want.
(for future reference)

This is done with event listeners.


VerifySignedPayload fails with Invalid Hex string message

We are trying to sign a payload and our backend validates it. On the webgl this works fine but on the android our backend validation fails to validate. Since validation works for webgl we thought maybe this is related to tezos sdk.
Below  is an payload  example
Sign this for authorization s2asd45asf75as6d76

We have tried all 3 signing types. All gives same signature.
Also when  we tried tezos sdk's VerifySignedPayload method, we get an error about Invalid Hex string. We are not sure about the behaviour change between webgl and android. We have tried converting payload to hex aswell  but  that  only  helped  about VerifySignedPayload method and not backend validation.

In 1.3.0


[PE-D] Task that already tagged with existing priority can still be tagged as the same priority

Tasks with an existing priority can still be tagged with the same priority.
For example, the task "Finish Client Proposal" has already been tagged with Medium priority. However, the same task can still be tagged as a Medium priority. This is a feature flaw as it's the same priority as before and therefore there should be some form of error shown to say that the same task has already been set with this level of priority.
This bug spreads across all the priority tags, high, medium, low, none.

Labels: severity.Medium type.FeatureFlaw
original: yuqitanyq/ped#9

Thank you for the feature suggestion. We will take this into consideration after v1.4.


New option: opt_merge_instances_with_userdata

The existing opt_merge_instances, when on (default), will merge shader instances within a group when they are completely isomorphic, having the same code, symbols, instance parameter values, and upstream connections. When two matching instances are found, they are combined into one.
However... we have discovered an interesting edge case, wherein the two retrieve userdata (geometry-bound parameters) and even though they are both retrieving what appears to be the same-named userdata, the particular renderer (not mine!) allows a level of flexibility where the renderer can bind different userdata ("hook the 's1' interpolated variable to this instance's 's' input parameter"), and that happens in a way where OSL per se doesn't really know that it's been bound to a different name than the name of the parameter. So if they have two instances, where different alternate userdata values are bound (again, in a way not discernable to OSL itself), it would be bad to merge the instances. Of course, they can turn off opt_merge_instances to avoid any spooky bugs, but that turns off all instance merging, even in nodes where no userdata is involved, and so the problem can't crop up.
Whew, okay, now that we're all on the same page, it should be clear how it's useful to have a new opt_merge_instances_with_userdata, which if turned off will prevent instances from merging if they need userdata (though other instances not using any userdata will still merge, assuming that the old opt_merge_instances is still turned on). The default for the new option is on, so in general nobody but this one site (or others in the future who need this) will need to care about it.
To implement this, of course we need to track this in the right places. Fairly straightforward. In fact, the code changes are smaller than the explanation above of why we're doing it.
Along the way, I also spotted a bug: although we were tracking whether shaders wrote global variables (P, N, Ci, and so on), and in theory were forcing instances that write globals to run unconditionally (rather than lazily), it turned out that we never set the flag. So now that's restored. It's not a total coincidence that I found this, because the places where we need to track whether an instance reads userdata is basically the same spot as where we should have been (and now are) tracking whether any globals are written.

They say "untested code is broken code", and indeed my first stab at this PR did not work properly. Added test. Fixed bugs. Reposted PR.


Model Builder error on Azure Training

System Information (please complete the following information):

Model Builder Version: <IP_ADDRESS>1102
Visual Studio Version: Visual Studio 2019 Preview, 16.8.0 Preview 2.1

Describe the bug
Complete step by step to train an Image Recognition scenario using Azure Environment.
To Reproduce
Steps to reproduce the behavior:

Add Machine Learning to C# Project
Select Image Classification scenario
Select Azure as Training Environment
Select training image folder
Start Training

Expected behavior
After uploading all the training images, Model Builder raises this exception
at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification)    at Azure.MachineLearning.Services.Compute.ComputeTargetPageFetcher.FetchNextPage() in /_/src/Microsoft.ML.AzureMLClient/Compute/ComputeTargetPageFetcher.cs:line 35    at Azure.MachineLearning.Services.LazyEnumerator1.d__9.MoveNext() in //src/Microsoft.ML.AzureMLClient/LazyEnumerator.cs:line 26
at System.Linq.Enumerable.WhereEnumerableIterator1.MoveNext()    at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable1 source)
at AzureML.AutoMLRunnerImages.d__27.MoveNext() in //src/Microsoft.ML.ModelBuilder.AutoMLService/RemoteAutoML/AutoMLRunnerImages.cs:line 233
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ML.ModelBuilder.AutoMLService.Experiments.AzureImageClassificationExperiment.d__13.MoveNext() in //src/Microsoft.ML.ModelBuilder.AutoMLService/Experiments/AzureImageClassificationExperiment.cs:line 69
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ML.ModelBuilder.AutoMLEngine.d__26.MoveNext() in //src/Microsoft.ML.ModelBuilder.AutoMLService/AutoMLEngineService/AutoMLEngine.cs:line 134

Additional context
Attached the full runtime log.
b6e7c212-c030-45b8-8c31-a8c125ae1115.txt

Seems that AzClient can't get computer info, can you go to azure portal and check if selected compute is created succesfully?

This is exactly my issue. And to answer you, @LittleLittleCloud - my compute is successfully created.

I also tested with the latest version:  <IP_ADDRESS>6002
the one with includes object detection and I still have the same error

Thanks for the feedback @elbruno @arafattehsin  We are taking a look at it

Thanks for reporting @elbruno and @arafattehsin. This aggregate exception message isn't helpful (need to fix that!) I'd like to know if the run was started and ran into a problem. Can you check the ML portal (https://ml.azure.com) and see if the run has any information?
If the run can't access the compute for some reason the experiment error should tell us the problem. Thanks for your patience while we figure this out!
If you're not familiar with the ML portal...

Click Experiments on the left nav.
Click on your experiment name (probably "ImageClassification" or "ObjectDetection"). You should see a run from when you were testing. It's probably failed or cancelled.

Go into that run. It might show some information on the error at the top, or the problem might be in a child run.

Check the child run for any helpful info. Sometimes it's inside a warning message at the top. You'll need to expand that to see the inner exception info.

Hi @beccamc - Thank you for this detailed explanation. Unfortunately, I can't even see any experiments being executed. My experiment is created but I don't see any run.

@arafattehsin This is so strange... It looks like the training fail at fetching compute step so experiemnt won't even have a chance to create.
T'm trying to reproduce the error, could you tell me how do you create compute, did you use the UI in model builder? or through Azure portal. And could you share your compute's property, and which configuration did you use to create compute.

@LittleLittleCloud  I created it using the UI in Model Builder

If you can tell you a way which worked for you, please do so as I can try the exact same way to make it work.

@arafattehsin  I didn't do anything specifically.. Could you try creating compute in azure portal, this is the configuration I use

Use dedicated machine solves the problem, better error message when launch training on low-priority machine fails is needed


extra tabs in condition

if you write a single-line conditional statement in the indent - norminette thinks that only first branch should have indentation
in this code
int	main(void)
{
  int a;

  while (1)
    if (a)
      a++;
    else
      a--;
}

you will get message
Error: TOO_MANY_TAB         (line:  8, col:   1):	Extra tabs for indent level
Error: TOO_MANY_TAB         (line:  9, col:   1):	Extra tabs for indent level

and this solve issue:
int	main(void)
{
  int a;

  while (1)
    if (a)
      a++;
  else
    a--;
}

Additional infos

OS: linux mint 20
python --version: Python 3.8.5
norminette -v: norminette 3.2.8

This is expected and described in the pdf. The norm expects only one inline condition when not using brackets.


[MXAPPS-581] Enable remaining tests in CI.

Description

Enable remaining tests in Straight Dope continuous integration as the notebooks in the Straight Dope have been corrected.

Add scikit-image dependency required by one test.

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

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

Thanks for the review, @sandeep-krishnamurthy. These tests take around 40 minutes at present. With these notebooks, likely ~ 50mins.
Each notebook is time-boxed to 10 minutes.
Re: the 3 notebooks I labelled as taking longer than 10 minutes, I was planning to revisit to see how to reduce the time it takes them, and whether or not to make exceptions on their time-out. I know the epochs are not being set to 1 on the chapter 18 notebooks, but even setting the number of epochs to 1, the notebooks are taking longer than 10 minutes, each. Last I checked it was > 20 minutes.
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/NightlyTests_onBinaries/detail/NightlyTests_onBinaries/117/pipeline


Footer buttons information

Is your feature request related to a problem? Please describe.
If a user enters the room, then he/she may not know the functionality of the footer buttons and which is not a good user experience.

Describe the solution you'd like
We can add tooltip or title on hovering the buttons so that it may know well the use of those buttons.
Are you willing to contribute to this issue? [Yes/No]
YES
Additional context
Please assign me this issue under GSSoC21'

Hi @AmeyaJain-25, First of all, thank you so much for taking out the time to create this issue.
Definitely 🙌, Please go forward to work on this issue.


fix: ignore chart subfolders without a Chart.yaml

:tada: This PR is included in version 1.6.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Unit tests and continuous integration

Make sure you have a full complement of unit tests and are using continuous integration. You can use the template from the repository I demoed: https://github.com/dacb/codebase_conda
Make sure to put badges in your README.md in the repo root.

Tested Added and Code Integrated


Aligned triad gallery broken on static content

It seems like the .triad.-aligned modifier is broken on static content (which was just refactored in #5561 to use our theme functions, rather than unique hardcoded markup). Hmmmm! :mag:

@mikefantini It was a bug! :bug: The fix was just deployed to staging. Let me know if you see any more issues!


Microsoft Edge support

This workflow is awesome, but I use Microsoft Edge for work. Since it's chromium based, it was easy to add this enhancement with the existing logic. In the event this additional browser support is of value to any others in the Alfred community, I'll submit a PR for your review.

PR reference: #8

merged 🚀


zimagi dbshell does not find psql

Moreover, it looks for it even if PostgreSQL has been turned off:
vagrant@zimagi:~$ zimagi dbshell
CommandError: You appear not to have the 'psql' program installed or on your path.
vagrant@zimagi:~$ which psql
vagrant@zimagi:~$ zimagi db stop
> postgres env: default
=======================================================================================================================
Stopping service zimagi-postgres
Successfully stopped PostgreSQL database service
vagrant@zimagi:~$ zimagi dbshell
CommandError: You appear not to have the 'psql' program installed or on your path.

Can confirm this is still an issue in the Vagrant environment

This is fixed with: https://github.com/zimagi/zimagi/pull/88


Implement envtool version command

What should be done?
We should implement a new envtool command that is very similar to shell read subcommand, but reads a fixed file build/version/commit.txt and omits the leading v in the output. It should exit with non-zero exit code on any error.
See #2685 for the reason why we need that command.
Where?
https://github.com/FerretDB/FerretDB/tree/main/cmd/envtool
Definition of Done
go run ./cmd/envtool version produces something like 1.2.0-1-g6170f970a.

Hello! Can I work on this? Thanks in advance!

Hey @rumyantseva , just to double check. The fixed file to read should be build/version/version.txt instead of build/version/commit.txt right?

Hey @jeremyphua, thanks for asking!
Yes, you are absolutely right, the file should be build/version/version.txt.
And yes, it would be great to add tests! Since the file build/version/version.txt is regenerated every time we build FerretDB, I'd say it should be safe to just rewrite it at the beginning of the test. So, a test could be similar to some other tests in envtool_test.go where we generate files with known content before dealing with them. Or alternatively, the filename can be set as a param of the function that reads the file, and then it's possible to generate some other files and use them for testing.


"unable to validate AWS credentials" when setting AWS profile via Pulumi config

What happened?
Up until now we have used env vars to set and use the default AWS provider:
export AWS_REGION=xx-xxx-x
export AWS_PROFILE=yyyyy

Now i am trying to use the Pulumi config instead of env vars, so i've added the following settings to the stack's pulumi config:
config:
  aws:profile: yyyyy
  aws:region: xx-xxx-x

Now i am getting the following errors:
error: unable to validate AWS credentials.
    Details: no valid credential sources for  found.

    Please see
    for more information about providing credentials.

    Error: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, http response error StatusCode: 404, request to EC2 IMDS failed

    Make sure you have:

     	 • Set your AWS region, e.g. `pulumi config set aws:region us-west-2`
     	 • Configured your AWS credentials as per https://pulumi.io/install/aws.html
     	 You can also set these via cli using `aws configure`.

I tried to add skipCredentialsValidation: true and skipMetadataApiCheck: false but getting the same result.
Expected Behavior
Should work with pulumi config the same as it worked with the env vars
Steps to reproduce
Use a simple AWS project without setting an explicit AWS provider (using the default one) and setting region and profile with env vars. Then remove env var and set region and profile using pulumi config.
Output of pulumi about
➜  ~ pulumi about
CLI
Version      3.49.0
Go Version   go1.19.3
Go Compiler  gc
Plugins
NAME        VERSION
aws         5.24.0
aws         5.24.0
cloudflare  3.6.0
cloudflare  3.3.0
datadog     3.3.0
datadog     3.3.0
docker      3.6.1
docker      3.0.0
kafka       3.4.0
kafka       3.0.1
kubernetes  3.6.0
kubernetes  3.6.0
mysql       3.1.0
mysql       3.0.0
nodejs      unknown
okta        3.17.0
okta        3.0.0
pagerduty   2.2.0
pagerduty   2.1.1
postgresql  3.6.0
postgresql  3.6.0
rabbitmq    3.2.0
rabbitmq    3.0.0
random      4.10.0
random      4.2.0
spotinst    3.8.0
spotinst    3.8.0
tls         4.8.0
tls         4.0.0
Host
OS       amazon
Version  2
Arch     x86_64
This project is written in nodejs: executable='~/.nvm/versions/node/v14.21.0/bin/node' version='v14.21.0'
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hi @jasminen, following up on our conversation in Slack here. I tried to reproduce this with a new program and a new stack (via pulumi new aws-go), but wasn't able to. My terminal session is below.
I did go down a rabbit hole for a bit because I tried to repro it with a program using an explicit provider, and there seems to be something wrong there. However, you say you're using the default provider.
As a next step, are you able to add some debug output to this issue? Via pulumi preview --logtostderr --logflow -v=9 2> out.txt.
$ pulumi preview
Diagnostics:
  aws:s3:Bucket (my-bucket):
    error: unable to validate AWS credentials.
    Details: no valid credential sources for  found.
...

$ export AWS_PROFILE=AdministratorAccess-616138583583
$ export AWS_REGION=us-west-2

$ pulumi preview

     Type                 Name                   Plan
 +   pulumi:pulumi:Stack  repro-aws-creds-2-dev  create
 +   └─ aws:s3:Bucket     my-bucket              create

Outputs:
    bucketName: output<string>

Resources:
    + 2 to create

$ pulumi config set aws:profile AdministratorAccess-616138583583

$ pulumi config set aws:region us-west-2

$ unset AWS_PROFILE

$ unset AWS_REGION

$ export -p | rg AWS

$ pulumi preview

     Type                 Name                   Plan
 +   pulumi:pulumi:Stack  repro-aws-creds-2-dev  create
 +   └─ aws:s3:Bucket     my-bucket              create

Outputs:
    bucketName: output<string>

Resources:
    + 2 to create

Hey @jasminen! Did you get a chance to take another look at this issue?

Side issue (but possibly relevant): what's up with the missing value in
Details: no valid credential sources for  found.

@thomas11 same issue here, we are using this set of ENVs in CI to assume roles through profiles:
AWS_PROFILE: <PROFILE_NAME>
AWS_SDK_LOAD_CONFIG: "true"
AWS_CONFIG_FILE=<PATH_TO_CUSTOM_AWS_CONFIG>

Configs:
skipCredentialsValidation: "true"
skipMetadataApiCheck: "false"

Error:
Error: failed to refresh cached credentials, operation error STS: AssumeRole, failed to sign request: failed to retrieve credentials: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, expect HTTP transport, got <nil>

Side issue (but possibly relevant): what's up with the missing value in
Details: no valid credential sources for  found.

Fixed in #2367, but not related to this issue, unfortunately.

Hi @SharpEdgeMarshall , I tried to reproduce a few basic scenarios, like setting AWS_PROFILE and in the code creating a provider with a different profile:
		provider, err := aws.NewProvider(ctx, "provider", &aws.ProviderArgs{
			Profile: pulumi.StringPtr("accesskey"),
			Region:  pulumi.StringPtr("us-west-2"),
		})

Everything worked for me. Could you give me more information about your scenario, ideally some sample code to reproduce it?

Hi @jasminen, since I cannot reproduce the issue, I'll close it soon. Did you get a chance to look at this again?

@thomas11 Are you testing it on an AWS instance with an instance profile?

@SharpEdgeMarshall no, should I?
Can you share a code snippet of how exactly you're creating the explicit provider?

@thomas11 I have a theory that this is something to do with how default providers are resolved. Digging around the code for aws.Provider, it seems that if nothing is supplied for say region, it falls back to env variables. It probably first needs to fallback to the configured aws:region, and similarly for profile.
While I'm here I could also ask something else goofy about providers: why cant I feed string to Region attribute unless it's set explicitly in the options. For example it doesn't like this:
    import { getConfig } from "@pulumi/pulumi/runtime/config";

    const defaultProvider = new aws.Provider(`${stack}-${connection.id}-peer-provider`, {
        region: getConfig("aws:region"),
        profile: "sparkhire_prod"
    });

I'm basically blocked no matter what I do because even if I feed a default provider manually, I cant simply config it via the raw aws:region. I'm not really a typescript expert so if there's a workaround for this that would be great.

Hi @throttlehead-dev, this is actually as intended, although I do agree that it could be documented more clearly. See here:

Configuration file settings are only used by the default provider. If you instantiate a provider object, it will not read values from the stack configuration.

Since I wasn't able to reproduce the issue and some of the commenters didn't follow up so far, I'll close this issue. Feel free to reopen it if you still think Pulumi has a problem here.

Hey there, I'd like to reopen this.
I'm experiencing this with pulumi-3.111.0 and pulumi-aws-5.43.0
We're generating ~/.aws/credentials in our CI pipeline, then running a pulumi refresh.
When setting aws:profile: some-account it fails with
error: Preview failed: unable to validate AWS credentials.
    Details: no valid credential sources for  found.

    Please see
    for more information about providing credentials.

    Error: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, request send failed, Get "http://<IP_ADDRESS>/latest/meta-data/iam/security-credentials/": dial tcp <IP_ADDRESS>:80: i/o timeout

but when setting the env var AWS_PROFILE it works fine.


fix: improve create Kafka dialog UX

What this PR does / why we need it:
This fixes a number of issues with the create Kafka dialog.
Sizes can be disabled
An instance size could be visible but not selectable for instance creation. It shows with a warning.

Trying to submit the form with a disabled size selected will transform the warning in an error.

Generic alert when trial instances are unavailable for technical reasons
Always display the "All available trial instances are currently in use. Try again later." message for all cases where trial instances can not be created for reasons unrelated to the user.
Top aligned modal
Aligning the modal to the top of the screen reduces the amount of layout jumping when interacting with elements that trigger changes on the visualized UI, like changing provider/region where skeletons are displayed while loading the new data.
Skeletons were tweaked to better reflect the space taken by the real elements, again to reduce layout jumping.
State machine refactoring
Refactor the state machine to rely less on the context and more on its states. This will improve the future maintainability of the machine.
Fix the XState inspector height issue
The inspector will use the available height instead of a fixed 1000px.
Improve rollup.js build
Suppress the warnings, by properly acknowledging them. Change the config so that future warnings are promoted to errors, forcing builds to fail.

Has something changed with building the storybook preview? There used to be a chromatic action listed under the checks that provided the URL for storybook previews, but I'm not able to find any URL.

It's there, you probably only have to scroll the actions to see it as it's one of the last ones.
I know this only because I had the same problem in the past and spent a unhealthy amount of hours trying to figure out why it wasn't working before noticing GH shows only the first 6 actions... 😅

These updates look great! Here are a few comments:

When both conditions for the selected size are true: tech preview and unavailable in the selected region

Currently only the "unavailable in the selected region" message displays when both conditions are true. Without any user research to back this up, my instinct is to display both messages. Knowing that the selected size is in tech preview might encourage me to select a different size.
Given that we want to refactor this design, I'm also fine with putting this on hold and addressing it as part of the next design. We can also raise this in a UX review to get input from more of the team on this.

improved accessibility for screen readers

Any messages that display within the form for specific fields should be linked to the form inputs via aria-describedby and id attributes so that screen reader users hear these messages announced when they move focus to the form input. For example:

aria-describedby="instance-size-unavailable" on the input
id="instance-size-unavailable" on the message/alert

Support for aria-describedby on the slider was just added in https://github.com/patternfly/patternfly-react/pull/7408. Even though this version of PF isn't released yet, should we go ahead and add the aria-describedby prop on the slider? I don't expect this to result in errors, but when we finally update PF, this association will already be set up.
The message that communicates the selected size is unavailable in the selected region displays below the Size input, but it also applies to the Cloud region input. Therefore the aria-describedby attribute should also be added to the cloud region input.

:tada: This PR is included in version 1.38.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Intrinsic f32x4_convert_u32x4 converted into 4 32bits converts

🐛 Bug description
Hi, playing around Rust, Wasm and SIMD, i have noticed a weird conversion with a test.
The Rust source code contains the following explicit intrinsic (and much more):
use std::arch::wasm::f32x4_convert_u32x4;

...

let s1 = f32x4_convert_u32x4(...);

It was not processing as fast as i was expecting.
Checking the assembly with wasm2wat shows the following opcodes.
      i16x8.extract_lane_u 4
      f32.convert_i32_u
      f32x4.splat
      local.get 8
      i16x8.extract_lane_u 5
      f32.convert_i32_u
      f32x4.replace_lane 1
      local.get 8
      i16x8.extract_lane_u 6
      f32.convert_i32_u
      f32x4.replace_lane 2
      local.get 8
      i16x8.extract_lane_u 7
      f32.convert_i32_u
      f32x4.replace_lane 3

Other intrinsic like u32x4_extend_low_u16x8, u16x8_extend_low_u8x16, and more, was properly converted.
I am new to this rust/wasm/simd, any idea where could come from the problem? And which project i should check for such problems?
🤔 Expected Behavior
An equivalent algorithm written in AssemblyScript is generating the following opcode:
        f32x4.convert_i32x4_u

👟 Steps to reproduce
🌍 Your environment
Include the relevant details of your environment.
wasm-pack version: 0.10.3
rustc version: 1.63.0 (4b91a6ea7 2022-08-08)
linux debian 10

I think the right project is https://github.com/rust-lang/stdarch i will reopen the issue there.


Azure Container logs error

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az container logs
Errors:
The command failed with an unexpected error. Here is the traceback:
'ContainerInstanceManagementClient' object has no attribute 'container'
Traceback (most recent call last):
  File "/opt/homebrew/Cellar/azure-cli/2.28.0/libexec/lib/python3.9/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/homebrew/Cellar/azure-cli/2.28.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
    raise ex
  File "/opt/homebrew/Cellar/azure-cli/2.28.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/homebrew/Cellar/azure-cli/2.28.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 691, in _run_job
    result = cmd_copy(params)
  File "/opt/homebrew/Cellar/azure-cli/2.28.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/homebrew/Cellar/azure-cli/2.28.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 112, in handler
    client = self.client_factory(self.cli_ctx, command_args) if self.client_factory else None
  File "/opt/homebrew/Cellar/azure-cli/2.28.0/libexec/lib/python3.9/site-packages/azure/cli/command_modules/container/_client_factory.py", line 18, in cf_container
    return _container_instance_client_factory(cli_ctx).container
AttributeError: 'ContainerInstanceManagementClient' object has no attribute 'container'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az container logs --container-name {} --name {} --resource-group {}

Expected Behavior
Environment Summary
macOS-11.6-arm64-arm-64bit, Darwin 20.6.0
Python 3.9.7
Installer: HOMEBREW

azure-cli 2.28.0

Additional Context

route to service team

@adriant172 Looks like this has since been fixed and I can confirm that there is no error now. Apologies for no updates on this issue sooner. Unless you are still seeing this error on your end with the latest version, I believe this could be closed.


X11 DisplayServer does not set correct _NET_WM_WINDOW_TYPE for dialogs, causing issues with tiling window managers

Godot version
v4.0.dev.custom_build [69a194f05]
System information
Linux, x11, nvidia
Issue description
Many new windows what is created  has _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL what creates jarring user experience with Tiling Window Managers.
I would recommend change _NET_WM_WINDOW_TYPE(ATOM) set to _NET_WM_WINDOW_TYPE_DIALOG for all dialog windows.
Places where this should be changed to _NET_WM_WINDOW_TYPE_DIALOG as I found out in fast testing is:

Add child
Instantiate Child Scene
Open Scene
Save (When selecting place where to save)
In right click menu basically all selections creates new dialogs but has _NET_WM_WINDOW_TYPE = NORMAL.
Quick Load
When creating new scene and selecting Other Node as base type.

On many applications only main window type is set to _NET_WM_WINDOW_TYPE_NORMAL and all others are set to other ones (mostly to _NET_WM_WINDOW_TYPE_DIALOG). And this is how most of tiling window managers are coded to handle _NET_WM_WINDOW_TYPE_DIALOG as floating window automatically.
Here is one possible fix for this.
index 74ec8b6..97f603e 100644
--- a/platform/linuxbsd/display_server_x11.cpp
+++ b/platform/linuxbsd/display_server_x11.cpp
@@ -4179,10 +4179,17 @@ DisplayServerX11::WindowID DisplayServerX11::_create_window(WindowMode p_mode, V
                        if (wt_atom != None && type_atom != None) {
                                XChangeProperty(x11_display, wd.x11_window, wt_atom, XA_ATOM, 32, PropModeReplace, (unsigned char *)&type_atom, 1);
                        }
-               } else {
+               } else if (MAIN_WINDOW_ID == id){
                        Atom type_atom = XInternAtom(x11_display, "_NET_WM_WINDOW_TYPE_NORMAL", False);
                        Atom wt_atom = XInternAtom(x11_display, "_NET_WM_WINDOW_TYPE", False);

+                       if (wt_atom != None && type_atom != None) {
+                               XChangeProperty(x11_display, wd.x11_window, wt_atom, XA_ATOM, 32, PropModeReplace, (unsigned char *)&type_atom, 1);
+                       }
+               } else {
+                       Atom type_atom = XInternAtom(x11_display, "_NET_WM_WINDOW_TYPE_DIALOG", False);
+                       Atom wt_atom = XInternAtom(x11_display, "_NET_WM_WINDOW_TYPE", False);
+
                        if (wt_atom != None && type_atom != None) {
                                XChangeProperty(x11_display, wd.x11_window, wt_atom, XA_ATOM, 32, PropModeReplace, (unsigned char *)&type_atom, 1);
                        }

Steps to reproduce

Install tiling window manager (For example: QTile)
Build godot (master)
Open any dialog window

Minimal reproduction project
No response

See also #37930 and #38727
I remember experimenting with the _NET_WM_WINDOW_TYPE_DIALOG atom a long time ago without great results, but that was before that PR was merged, so it might work without issues now.

At least in testing I did yesterday, with that patch it seemed to work correctly in QTile. And as far I recall _NET_WM_WINDOW_TYPE_DIALOG is also default floating window in i3wm, if not but it can be easily enabled as floating window type in i3wm if not default.


Moved projects into subfolders to prepare for Portability Service work

ApiPort* projects (and tests) moved into ApiPort folder
Microsoft.Fx* projects (and tests) moved into lib folder
We can use a top-level src/backend folder for the Portability Service components

LGTM The only downside of moves like this is it messes with history and makes it hard to follow previous changes :(

@mjrousos should this be done in dev and then merged into service from there?

Yeah.. thinking more about it, with all the renames, probably a good idea to put the base of this against the dev, branch. create another PR to merge into master and then pull that change into service.

Yea, that makes sense. Otherwise merging future dev changes into service will be a pain. I'll abandon this and re-create it in dev.


Glitchy editor viewport when viewing 3D scene in GLES2

Godot version:
v3.1.beta4.official
OS/device including version:
Ubuntu 18.10 (64-bit)
Radeon RX 560 Series (POLARIS11, DRM 3.26.0, 4.18.0-15-generic, LLVM 7.0.0)
Issue description:
Editor 3D viewport glitches when resizing, only when using GLES2. Does not occur in previous betas.

Might be related to #25804, which has been fixed since beta 4 in the master branch.

Correct, issue has been fixed. Tried nightly build from commit 89eb79a and it no longer has this unwanted behavior.


Dropdown menu categories

When an input opens a dropdown menu, that dropdown will have the same data-category attribute as its parent block

Nice!


Update README.md

I think this one parameter might missing?

it's an OR, (enforced by below code) so you can't specify both
https://github.com/OpenFreeEnergy/openfe_analysis/blob/main/src/openfe_analysis/reader.py#L60


What should I do with all my extra time?

Issue
I don't know what to do?
I'm using Aider for a week now and a new concerning issue was raised: what do I do with my free extra time? My boss gave me two sprints to implement a bunch of features and PBI's but they are already done! What to do??
🚀
Version and model info
Aider 0.43 on Claude 3.5... its on fire 🔥🔥🔥

Glad to hear aider is working well for you.
I'm going to close this issue for now, but feel free to add a comment here and I will re-open or file a new issue any time.


CI optimizations

Description
Make CI run faster and remove the pinning iota dependency.
Motivation
Waiting 30> minutes for subsequent CI runs is not acceptable.

Ideas:

parallelize (no-)default features builds
external (persistent) sccache
custom runners


ResourceController support for server defined default label.

That is the first iteration. I've added a single test since it seems to cover our use case.
I can confirm that the params argument on @RequestMapping is used for mapping matching.
2017-10-19 12:39:55.956 TRACE 22849 --- [           main] s.w.s.m.m.a.RequestMappingHandlerMapping : Found 3 matching mapping(s) for [/foo/default/foo.txt] : [{[/{name}/{profile}/**.*],methods=[GET],params=[useDefaultLabel]}, {[/{name}/{profiles}/{label:.*}],methods=[GET]}, {[/{name}/{profile}/{label}/**],methods=[GET]}]
2017-10-19 12:39:55.956 DEBUG 22849 --- [           main] s.w.s.m.m.a.RequestMappingHandlerMapping : Returning handler method [public java.lang.String org.springframework.cloud.config.server.resource.ResourceController.retrieve(java.lang.String,java.lang.String,javax.servlet.http.HttpServletRequest,boolean) throws java.io.IOException]

Fixes #824

Codecov Report

Merging #825 into master will increase coverage by 0.07%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #825      +/-   ##
==========================================
+ Coverage   76.11%   76.19%   +0.07%
==========================================
  Files          83       83
  Lines        2596     2600       +4
  Branches      377      377
==========================================
+ Hits         1976     1981       +5
  Misses        464      464
+ Partials      156      155       -1

Impacted Files
Coverage Δ

...oud/config/server/resource/ResourceController.java
88.23% <100%> (+4.9%)
:arrow_up:

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 a7bd68c...01981aa. Read the comment docs.


F() expression & "changes" column

Hi,
When model field is incremented using F() expression like so,
from django.db.models import F

model_object = SomeModel.objects.get(some_column='90293')
model_object.submit_count = F('submit_count') + 1
model_object.save()

The auditlog entry for this .save(), shows the entry like this
{'changes': '{"submit_count": ["8", "F(submit_count) + Value(1)"]}'}
But i'm not sure of what is the required outcome in this scenario that must be implemented by this package, should it refresh the entry from db for this particular column and show it as "changes" while the rest of them are unchanged?

Auditlog is designed to read the current value. If that is an F-expression, that's obviously not going to work out as you mentioned. But this behavior is expected.
I do not know what kind of workaround there is for this, as Auditlog doesn't operate on DB level.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/1083 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit c9fea4b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_main_2022-03-14-02-21-34 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Remove PKI acronym

The PKI acronym is not relevant in this context and so I removed it. It does not stand for Public Key Cryptography and although some aspects of a PKI are discussed here, it is not specifically about PKI, but more about Asymmetric keys and certificates

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

@sensomatic The initialism 'PKI' stands for Public Key Infrastructure. But the initialism is defined inaccurately in the original documentation, and it was never used in the article, and thus was superfluous. Your recommendation to remove "(PKI)" thus makes sense.  Thank you for this edit.
#sign-off

@MightyPen: I'm sorry - only the author of this article, @VanMSFT, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

@craigg-msft: I'm sorry - only the author of this article, @VanMSFT, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

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

Resolved merge conflict from the other change I made on the same line.

#sign-off


Support for custom generators / targets

Description
#1322
Add a short description of:

Support for custom generators / targets
#1322

This sort of information is useful for people reviewing the code, as well as anyone from the future trying to understand why changes were made or why a bug started happening.

Need to preserve default behaviour

@samijaber please check

Thanks for putting this together @JerryWu1234 ! Thank you for your patience in getting it merged as well.


JMS Connector Issue when a message is created on a broken session

Description:
Please consider below code
function tryToSendMessage(map<string> requestMessageMap) returns error? {
        //create a map message from message detail extracted
        var messageToStore = self.jmsSession.createMapMessage(requestMessageMap);
        if (messageToStore is jms:Message) {
            // This sends the Ballerina message to the JMS provider.
            var returnVal = self.queueSender->send(messageToStore);
            if (returnVal is error) {
                //TODO: try to send to failover store if defined
                string errorMessage = "Error occurred while sending the message to the queue " + self.queueName;
                log:printError(errorMessage, err = returnVal);
            }
        } else {
            log:printError("Error while creating message from ", err = messageToStore);
            return messageToStore;
        }
    }

Steps to reproduce:

Start the program.
Verify message sending is working fine.
Shutdown the broker
Try to send a message

When creating message on broken session it should return an error. Instead it returns a jms:Message.
Need to fix it at [1].
[1]. https://github.com/ballerina-platform/ballerina-lang/blob/master/stdlib/jms/src/main/java/org/ballerinalang/net/jms/utils/BallerinaAdapter.java#L75-L80
N/A
Affected Versions:
0.991.0

This issue will fix after migrating to jballerina. @riyafa can you please check.

This was fixed after the restructuring of the jms:Message object. #16669