CFE ES unit test failures caused by startup sync fix

The startup sync fix (#71) caused some unit test failures.
This is due to the fact that the counters never get incremented as expected, since this is done by the child thread.  Therefore the verification that the child thread actually started cannot be unit tested.
As an interim fix this check will be removed from the main code. This will make unit tests pass in 6.4.2.  Ironically, this is making the main code slightly less robust in order to appease unit tests.
In the future a unit test "hook" function can be implemented for {{{OS_TaskCreate()}}} that imitates the counter increment so the startup verification can be but back in at that time.

Imported from trac issue 74.  Created by jphickey on 2015-06-24T10:59:21, last modified: 2015-07-02T11:37:21

Trac comment by jphickey on 2015-07-02 11:37:21:
It was decided that this would NOT be included in 6.4.2, and the release would be published with the ES unit test "as-is".
As this originally was only a back port of a piece of a larger change set (#103) this ticket will be closed.  #103 has all modifications needed to make the current development unit tests work.

Trac comment by jphickey on 2015-06-24 11:13:28:
Submitted [changeset:bbbb963] on branch {{{trac-74-startup-sync-ut-fix}}} that back ports my workarounds for this specific UT issue.
NOTE - the branch is based on {{{ic-hotfix-6-4-2}}}


Resolve several RuboCop TODO items

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-2 of 36 (94.44%)  changed or added relevant lines in 19 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.7%) to 91.239%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/rails_admin/adapters/mongoid.rb
0
1
0.0%

lib/rails_admin/engine.rb
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-4.7%

Covered Lines:
3364

Relevant Lines:
3687

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

34 of 36 (94.44%)  changed or added relevant lines in 19 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.7%) to 91.239%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/rails_admin/adapters/mongoid.rb
0
1
0.0%

lib/rails_admin/engine.rb
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-4.7%

Covered Lines:
3364

Relevant Lines:
3687

💛  - Coveralls

Sorry I couldn't follow this up, I lost the timing to merge because of conflicts 🙇

No problem. I reopened as https://github.com/railsadminteam/rails_admin/pull/3478


Fix documentation typos in FIROAuthProvider.

Fix some typos in FIROAuthProvider public docs.

Merging in advance of 7.2.0 freeze.


docs: adds note to Lifecycle creation policy owner docs

Supersedes https://github.com/external-secrets/external-secrets/pull/2928
Closes #2416

thanks!


Add tests for Indonesian holidays requested in PR#430

Tests for Indonesian holidays between 2019 and 2022 are created. Updates in beta branch are merged, and conflicts have been resolved.

I made a mistake to make a PR to master branch. So I close this PR.


Template  in identity.xml

The <UseUserIdFromClaims> config is an optional config and it should be templated in a way that the tag should only appear in the identity.xml if it is defined only.
<UseUserIdFromClaims> should be defined inside the  <Server><OAuth><SAML2Grant> tag

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


All home changes given the new execution functionality

All updates made and merged in the last PR (#56) in this nested chain of collection execution PRs


请提出你的问题
tokenizer = AutoTokenizer.from_pretrained("linly-ai/chinese-llama-2-7b") 这一行代码出错
OSError: Can't load the model for 'linly-ai/chinese-llama-2-7b'. If you were trying to load it from 'BOS', make sure you don't have a local directory with the same name. Otherwise, make sure 'linly-ai/chinese-llama-2-7b' is the correct path to a directory containing one of the ['tokenizer_config.json']

我们本地和[星河社区]执行都是正常的。本地文件默认存储在~/.paddlenlp，出现以上问题的原因可能是由于tokenizer_config.json下载失败，建议删除~/.paddlenlp/models/linly-ai/chinese-llama-2-7b文件夹尝试。


[http] v2 - failed to select a version for gdk-sys

[package]
name = "app"
version = "0.1.0"
description = "A Tauri App"
authors = ["you"]
license = ""
repository = ""
default-run = "app"
edition = "2021"
rust-version = "1.60"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[build-dependencies]
tauri-build = { version = "1.4.0", features = [] }

[dependencies]
serde_json = "1.0"
serde = { version = "1.0", features = ["derive"] }
tauri = { version = "1.4.0", features = [] }
tauri-plugin-http = "2.0.0-alpha.2"

[features]
# this feature is used for production builds or when `devPath` points to the filesystem and the built-in dev server is disabled.
# If you use cargo directly instead of tauri's cli you can use this feature flag to switch between tauri's `dev` and `build` modes.
# DO NOT REMOVE!!
custom-protocol = ["tauri/custom-protocol"]

Error
error: failed to select a version for `gdk-sys`.
    ... required by package `webkit2gtk v0.18.2`
    ... which satisfies dependency `webkit2gtk = "^0.18.2"` of package `tauri v1.4.0`
    ... which satisfies dependency `tauri = "^1.4.0"` of package `app v0.1.0 (dashboard/src-tauri)`
versions that meet the requirements `^0.15.0` are: 0.15.1

the package `gdk-sys` links to the native library `gdk-3`, but it conflicts with a previous package which links to `gdk-3` as well:
package `gdk-sys v0.16.0`
    ... which satisfies dependency `gdk = "^0.16"` of package `gtk-sys v0.16.0`
    ... which satisfies dependency `gtk-sys = "^0.16.0"` of package `webkit2gtk v1.1.0`
    ... which satisfies dependency `webkit2gtk = "^1.1"` of package `tauri v2.0.0-alpha.11`
    ... which satisfies dependency `tauri = "^2.0.0-alpha.11"` of package `tauri-plugin-fs v2.0.0-alpha.1`
    ... which satisfies dependency `tauri-plugin-fs = "^2.0.0-alpha.1"` of package `tauri-plugin-http v2.0.0-alpha.2`
    ... which satisfies dependency `tauri-plugin-http = "^2.0.0-alpha.2"` of package `app v0.1.0 (dashboard/src-tauri)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the links ='gdk-sys' value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

failed to select a version for `gdk-sys` which could resolve this conflict

Can someone give me any advise?

The v2 versions of the plugins are only compatible with tauri v2 (your project uses v1) - the http plugin is basically just the old http module https://tauri.app/v1/api/js/http/ so maybe that works for you?

I had the same error and using tauri-plugin-log = { git = "https://github.com/tauri-apps/plugins-workspace", branch = "v1" } instead of "2.0.0-alpha.2" solved it.


contract.methods.function().send() fails with any kind of argument

Hi there,
please note that this is an issue tracker reserved for bug reports and feature requests.
For general questions please use the gitter channel.
Environment information
Thorify version: thorify version 1.5.4, 1.5.5
Web3 version: web3 version
Commit hash : (if develop)
Expected behaviour
Function call should succeed
Actual behaviour
Calling a contract's method with send() with any type of argument results in Error: hex string must have 0x prefix
Tried with various versions. 1.5.3 is fine, anything beyond that has this problem.
Steps to reproduce the behaviour
Call any deployed contract's non-view function that takes in an argument
Stacktrace
Error: hex string must have 0x prefix
    at Coder.decode (/Users/alexlau/vexchange-all/governance/node_modules/thor-devkit/dist/abi.js:33:23)
    at Object.decodeParameter (/Users/alexlau/vexchange-all/governance/node_modules/thor-devkit/dist/abi.js:71:22)
    at /Users/alexlau/vexchange-all/governance/node_modules/thorify/dist/provider/rpc-methods.js:194:105
    at Generator.next (<anonymous>)
    at fulfilled (/Users/alexlau/vexchange-all/governance/node_modules/thorify/dist/provider/rpc-methods.js:5:58)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

thank you for reporting @xenide, fixed in v1.5.6


Feature: Signer service

Codecov Report

Merging #5389 (efceb4e) into master (3d913f8) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #5389   +/-   ##
=======================================
  Coverage   96.05%   96.05%
=======================================
  Files         708      712    +4
  Lines       71000    71073   +73
=======================================
+ Hits        68200    68272   +72
- Misses       2800     2801    +1

Flag
Coverage Δ

servertests
35.82% <27.39%> (-0.01%)
:arrow_down:

unittests
95.99% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

moto/backend_index.py
100.00% <ø> (ø)

moto/__init__.py
97.27% <100.00%> (+0.01%)
:arrow_up:

moto/signer/__init__.py
100.00% <100.00%> (ø)

moto/signer/models.py
100.00% <100.00%> (ø)

moto/signer/responses.py
100.00% <100.00%> (ø)

moto/signer/urls.py
100.00% <100.00%> (ø)

moto/awslambda/models.py
93.91% <0.00%> (-0.11%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


cuelang.org: frontend: documented methods to resize inline images don't appear to work

What did you do?
I attempted to create an alpha.cuelang.org page with an inline image that has a reduced visual size:

Page: https://cl-1176774-1--cue-cls.netlify.app/docs/howto/resize-an-image/
CL: https://review.gerrithub.io/c/cue-lang/cuelang.org/+/1176774

What did you expect to see?
At the very least I expected to see the {{< figure >}} shortcode example work, as per https://alpha.cuelang.org/examples/basic/images/#figure-shortcode.
What did you see instead?
I only found one mechanism that allows me to include a down-scaled inline image: raw HTML with a style attribute:
<img src="/blog/example/cow.jpg" style="width:75px;" />

We should either document this, if it's the only way to resize an inline image, or make the documented methods work.

@jpluscplusm - please can you confirm if this is still an issue and if so that the description above is accurate?

The issue still stands, but I'm not sure how much of an issue it is.
We ran into this when trying to format the section that's now visible at https://cuelang.org/docs/reference/modules/#minimal-version-selection.
We had an image which was too large, and wanted to reduce its size. We had been planning to place it as follows:
prose
more prose
more prose

[ reduced size image ]

some more prose
...

... but weren't able to do this, as described in this issue. We ended up solving this issue by using the right-aligned image that's visible on that page today, via the figure shortcode. I think it looks fine, and that this issue wasn't a blocker on being able to produce that page.
I think the question is: how often will we need an image to be resized on the page, where it cannot be presented with text to its left or right? That's the use case that this issue captures, and I'm unsure how significant it is. I don't think it's currently a problem, but it's conceivable that we'll try to create a piece of content that has a harder requirement on such an impossible layout.

Closing this due to the problem never having struck on real documentation pages. We can re-open if needed.


Deprecate WhitelistingTextInputFormatter and BlacklistingTextInputFormatter

They are replaced by the single class FilteringTextInputFormatter.
Also, Remove deprecated_member_use_from_same_package. Since I ignore this lint rather than adding a bunch of //ignores, I also go and clean up other places we ignored this lint.
fyi @Piinks for the deprecation stuff
fyi @xster since you added these classes

Might be easier to review by reviewing the two commits separately.

Update: PR should have all the tests fixed now, and I spoke to the Gallery folks, they'll update after this lands (I made the specific deprecations that were failing on the Gallery not be failures for now; I'll deprecate them later once there's no breaking changes to worry about).

@Piinks PTAL

Fixes https://github.com/flutter/flutter/issues/59099

Merge conflicts fixed. Should be ready to land assuming no problems are found in review.

Looks like cirrus is unhappy, though.

Reverting this TBR by @Hixie as it caused LUCI post-submit to fail with:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8877105797085540816/+/steps/run_test.dart_for_framework_tests_shard/0/stdout
The following StateError was thrown running a test:
Bad state: No element

When the exception was thrown, this was the stack:
#0      Iterable.single (dart:core/iterable.dart:558:25)
#1      WidgetController._getElementPoint (package:flutter_test/src/controller.dart:646:47)
#2      WidgetController.getCenter (package:flutter_test/src/controller.dart:618:12)
#3      WidgetController.tap (package:flutter_test/src/controller.dart:256:18)
#4      main.<anonymous closure> (file:///b/s/w/ir/k/flutter/packages/flutter/test/material/text_field_test.dart:3285:18)
#15     FakeAsync.flushMicrotasks (package:fake_async/fake_async.dart:192:32)
#16     AutomatedTestWidgetsFlutterBinding.runTest.<anonymous closure> (package:flutter_test/src/binding.dart:1135:17)
#17     AutomatedTestWidgetsFlutterBinding.runTest.<anonymous closure> (package:flutter_test/src/binding.dart:1123:35)
(elided 25 frames from dart:async and package:stack_trace)

The test description was:
  Pasted values are formatted

Since this is deprecated, what should we use instead?

Since this is deprecated, what should we use instead?

Got it, eg:
FilteringTextInputFormatter.digitsOnly


Add predicates/config option for loading enchantment recipes

Doing some testing with CoFH Core and Ensorcellation, and I found out CoFH Core has a feature to disable enchantments. While disabled enchantments don't prevent the mod from working properly, it ends up causing a bunch of entries to read "Shimmer", which can't be applied to anything.
Point being that there should be some way to prevent stuff like this from happening. Because the enable/disable functionality is unique to CoFH Core, in this instance, there's no way to prevent this via vanilla method calls. One way is via a per-recipe predicate that looks something like this:
{
  "predicates": [
    "cofh_enabled": true
  ]
...
}

Other possible predicates:
{
  "predicates": [
    "enchantment_registered": "ensorcellation:air_affinity",
    "mod_loaded": "ensorcellation",
    "item_registered": "twilightforest:fiery_ingot",
  ]
...
}

Another potential feature which could be useful for modpack developers is disabling enchantments via a server config file. Maybe something like:
DisabledEnchantmentRecipes = ["precisionenchanter:ensorcellation/*", "precisionenchanter:vanillatweaks/vigor*"]

where each entry is a RegEx pattern. With this, it's possible to disable many more enchantment recipes without having to rely on predicates and/or empty JSON files.

Added option to defer with c07ddcd9ed358a365b5576030aacd3b902728a77. However, the more I think about it, the less sense it makes in this implementation. For something like the Holding enchantment recipes, both CoFH Core should be loaded, and the enchantment should be enabled. In this current implementation, both of these conditions are deferred, while only the latter should be, since the attempted registration would immediately fail if the parent mod isn't loaded. This is because all conditions in a collection-based condition (AND, OR, XOR) are deferred if only one of their conditions is deferred.
A potential solution would be to defer not only the testing of these conditions, but the registration itself.

Scratch that, this is only really a problem when dealing with enchantments from mods that aren't in the current user's environment, which are taken care of anyways. The above idea should be replaced with 2 fixes:

Clean up log output when an enchantment isn't available
Remove all redundant mod_loaded conditions

mod_loaded conditions removed with 18ce5cde564e8306f68cdc1bdc8e2df6b5a7cc49


Suggestion for message types.

I added message types and error codes.
They are based on the current pyleco implementation https://github.com/pymeasure/pyleco/pull/3
If you prefer looking at messages in python style, have a look here: https://github.com/pymeasure/pyleco/blob/add-core/pyleco/core/leco_protocols.py
As we follow openrpc, I figured, we should define the methods in openrpc style and not as python methods.
Closes #29
ToDo:

[ ] Relate messages of the transfer part like "CO_SIGNIN" to the method "coordinator_sign_in"

One informational note: I generated the json texts by calling the "rpc.discover" method (defined by openrpc) of the different Components, which returns (per definition) the methods of the (python) Components in openrpc json format.
If I made mistakes in the pyleco components (type hinting) or if the jsonrpc developer made errors, they reflect here.

One informational note: I generated the json texts by calling the "rpc.discover" method (defined by openrpc) of the different Components, which returns (per definition) the methods of the (python) Components in openrpc json format.
If I made mistakes in the pyleco components (type hinting) or if the jsonrpc developer made errors, they reflect here.

Ah, that makes this clearer! Makes sense.

In general, this RPC thing sometimes feels a little "inverted" to me somehow....
Coordinator A calls a method list_connected_components of Coordinator B,
not to make Coordinator B list its components via its own method, which you would expect if you just had an API reference of the Coordinator -- B.list_connected_components() would not take arguments, but return a list of connected components as per its name.
If A calls a method of B to tell B about A's details, that method would be something like B.add_connection_set(A, A's components). But for a message type/command name, this feels weird again.
So, inherently, I feel this mismatch between the names of commands, and those same names being method names in another object. :confused:

In general, this RPC thing sometimes feels a little "inverted" to me somehow....

I agree. The most prominent (and simple) example is "ping": I send a ping message and expect a pong response.
With RPC I call the responding method, which should be called "pong", therefore.

If A calls a method of B to tell B about A's details, that method would be something like B.add_connection_set(A, A's components). But for a message type/command name, this feels weird again.

I see your point.
To complicate things, we dont supply AinB.add_connection_set(A, A's components), because B` can deduce it from the message header. That might add to the confusion.
The Coordinator messages (regarding the directory) are the least obvious ones and require some collaboration.
Maybe we can use names like (these are methods in Coordinator A):
set_nodes (method tries to connect to other nodes, if not already connected)
get_nodes (returns nodes it is connected to)
set_component_directory (sets the component part of the directory, for example B's Components)
get_component_directory (gets all the components known to A, even those connected to B)
get_local_directory (gets Components connected to A

To store openRPC links globally, not in discussion:

specification
A playground to test an openRPC spec file / text snippet

Note to myself:

[ ] Define errors in methods, if appropriate, see https://spec.open-rpc.org/#method-object regarding errors. Especially the Coordinator Sign in can define the "DUPLICATE_NAME" error.

In general, this RPC thing sometimes feels a little "inverted" to me somehow....

I agree. The most prominent (and simple) example is "ping": I send a ping message and expect a pong response. With RPC I call the responding method, which should be called "pong", therefore.

If A calls a method of B to tell B about A's details, that method would be something like B.add_connection_set(A, A's components). But for a message type/command name, this feels weird again.

I see your point. To complicate things, we dont supply AinB.add_connection_set(A, A's components), because B` can deduce it from the message header. That might add to the confusion.
The Coordinator messages (regarding the directory) are the least obvious ones and require some collaboration.

Yeah untangling this could be a bit tiresome, but clear names are worth it. I hope we manage to unify the "command"/"message" character with the "method" being called in most cases.

Maybe we can use names like (these are methods in Coordinator A):
set_nodes (method tries to connect to other nodes, if not already connected)
get_nodes (returns nodes it is connected to)
set_component_directory (sets the component part of the directory, for example B's Components)
get_component_directory (gets all the components known to A, even those connected to B)
get_local_directory (gets Components connected to A

Maybe moving away from a simple get/set prefix will yield some benefits. If I understand your list correctly, the following could work better (here I'm assuming A sends to B, I'm not sure if your examples were the other way round):
get_nodes -> send_nodes. A sends to B: send_nodes. B sends its list of nodes.
set_nodes -> add_nodes. A sends to B: add_nodes(A's-list-of-nodes). B unifies its list of nodes with the ones just received
set_component_directory: Semantically, it feels weird if A could force B to set its component directory to something, as A is an external entity. Maybe add_components or record_components: A sends to B: record_components(list-of-A's-components). B records those components into its directory, making use of the fact that it knows they came from A.
get_component_directory -> send_component_directory, same logic as for send_nodes.
get_local_directory -> send_local_directory, same logic as for send_nodes.

I added examples to the dictionary methods to better understand how they work.

Different idea to show json: https://github.com/useblocks/sphinx-data-viewer
Or, as a backup, simply json annotation in sphinx: json-object


Test - Fix liquibase bat

Test PR for 4985 - do not merge

https://github.com/liquibase/liquibase/actions/runs/6408246555 - build installers to test on Win


[WIP] Add support for config type "file"

What this PR does / why we need it:
Which issue(s) this PR fixes:
Add support for a config type "file".
This gives users the possibility to specify a config item with the type file which then mounts files into their test cases.
These files can be specified by using the value attribute with a base64 encoded content or by specifying a secret/configmap key ref.
Special notes for your reviewer:
Release note:

Add support for config type "file". Now files with raw data or data from a secret or configmap can be mounted to the test.

@OlegLoewen @dguendisch can you please pre-review the concept how files are mounted to the specific test containers?


Add support for Union declarations without | to PYI016

Previously, PYI016 only supported reporting violations for unions defined with |. Now, union declarations with typing.Union are supported.
This implementation reuses the union traversal logic from #5570.
PYI016 will not attempt to fix cases where Union is used. Unlike |, removing members from a Union can result in an invalid union definition. We may be able to support this in the future as in PYI030 the complexity seems high.
Tested with new snapshot cases ./target/debug/ruff --select PYI016 crates/ruff/resources/test/fixtures/flake8_pyi/PYI016.pyi --show-source

Example bokeh change https://github.com/bokeh/bokeh/blob/ee3f7f27fb744860763edd1d44fcac9b797e36b4/src/bokeh/core/property/factors.py#L51


bugfix: modify log format

Ⅰ. Describe what this PR did
Modify log format to
"time.RFC3339Nano=2006-01-02T15:04:05.999999999Z07:00"
Ⅱ. Does this pull request fix one issue?

NONE
Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews
Signed-off-by: Rudy Zhang<EMAIL_ADDRESS>

Codecov Report

Merging #1239 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #1239      +/-   ##
==========================================
+ Coverage   15.36%   15.36%   +<.01%
==========================================
  Files         172      172
  Lines       10630    10628       -2
==========================================
  Hits         1633     1633
+ Misses       8877     8875       -2
  Partials      120      120

Impacted Files
Coverage Δ

daemon/mgr/network.go
3.48% <0%> (ø)
:arrow_up:

cli/run.go
0% <0%> (ø)
:arrow_up:

LGTM


ARROW-14207: [C++] Add missing dependencies for bundled Boost targets

They are needed for building some tests We may build these tests before bundled Boost targets are built.
This also removes Boost from libarrow_bundled_dependencies.a. Because Boost is only used for tests.

Note that Boost is only required for tests.

Oh, I missed it.

Removed Boost from libarrow_bundled_dependencies.a.

Is there some crossbow that needs to be run here? Otherwise LGTM.


[FEAT] folder suggestion for note and asset location

Thanks to https://github.com/SilentVoid13/Templater (and thus https://github.com/liamcain/obsidian-periodic-notes) for making a great suggestion dropdown. I've implemented the directory suggestion in the settings for note and asset location. It auto-suggests existing directories and allows for manually inserting a new directory.

Addresses https://github.com/kbravh/obsidian-tweet-to-markdown/issues/15


add HVO100

Currently missing but available as a fuel in NL, SE and DE

tankerkönig only offers:
type | Spritsorte | 'e5', 'e10', 'diesel' oder 'all'


Add new tests for remark

Think some stuff to consider:

Numbers
Symbols
Trailing white spaces should be trimmed
Length constraints?


DQN crashes on tensorflow 2.3rc

First of all, I run everything on Google Colab. I don't know if this issue is worth reporting, because right now the stable version of tensorflow is 2.2 and dqn has no problems on it. But in certain circumstances I got errors saying tensorflow 2.2 is not high enough (For details please see the end of the post. Let me know if you want me to open up a separate issue and describe it in more details). But anyway, the crash happens if you install tensorflow 2.3.0rc0. The problem can be reproduced in the following very simple colab notebook (run the 1st cell, restart the runtime and run 2-4th cells):
https://colab.research.google.com/drive/1jcOWwdHPqqrA0Yp97SYyeuHiotDAdU0W?usp=sharing
Because there was no error message, I really had no idea about what's going on. I tried to use stupid debugging methods and I was able to figure out that the problem was possibly (not 100% sure though) caused by reverb.TFClient.update_priorities in the following line
https://github.com/deepmind/acme/blob/eb63054ec19525fa8320fb323327cf13495615e3/acme/agents/tf/dqn/learning.py#L153
For my own project, I finally realized that the solution is very simple: I load the packages in the right order and the tensorflow version error goes away. I stay in tensorflow 2.2 and nothing goes wrong. But I don't know if this is something worth noting in your project, and I post it here just in case. I would also like to know what caused it just for the sake of my curiosity.

About the tensorflow version error:
In google colab, if I already imported tensorflow and then install acme packages, I would come across the following error when I tried to import acme.adders.reverb

ImportError: This version of Reverb requires TensorFlow version >= 2.3.0; Detected an installation of version 2.2.0. Please upgrade TensorFlow to proceed.

I would also have problems loading acme.tf.networks but the error is a different one. All errors will be gone if I force to install tensorflow 2.3.0rc0. Let me know if you need more details.

Hi @honglu2875 thanks for reporting this issue. Reverb is fairly rigid with the versions of TF that can be used with it. When we compile Reverb we have to do so against a specific version of TF, and errors will be raised if it differs significantly from the system's version.
To that extent our error message:

ImportError: This version of Reverb requires TensorFlow version >= 2.3.0; Detected an installation of version 2.2.0. Please upgrade TensorFlow to proceed.

should be tightened, and restrict users to use the same version of TF that was used to compile Reverb.
The good news is that TF 2.3 will have a stable release soon, which means we will be have a stable Reverb release!

Please re-open if this is still an issue for you.


Implementing Unit testing

As a manager I would like the application to be automatically tested in all its major features whenever new version is submitted

Unit testing implemented


Update OWNERS in main branch

Motivation
Updating OWNERS per https://issues.redhat.com/browse/RHOAIENG-2311
Modifications
Result

/lgtm


feat(TDI-41692):Salesforce: Dynamic Upsert for Bulkload with monitoring through component Variable

What is the current behavior? (You can also link to an open issue here)
for feature： https://jira.talendforge.org/browse/TDI-41692
What is the new behavior?
let bulk operation result field can get from dynamic field
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:
Sonar results

Pull request test result: failure :x:


How to access another mailbox calendar events ?

Version :1.0, dev-master
PHP version:7.0
Microsoft Exchange version: 2013
Description of problem:
Hi,
In script below (based on examples\event\create.php) i try to access to another mailbox calendar but the event is only write in my personal calendar and not in 'utilisateur''s calendar.
Example request:
...
$request->Items->CalendarItem[] = $event;
$request->ParentFolderIds = new NonEmptyArrayOfBaseFolderIdsType();
                $request->ParentFolderIds->DistinguishedFolderId = new DistinguishedFolderIdType();
                $request->ParentFolderIds->DistinguishedFolderId->Id = DistinguishedFolderIdNameType::CALENDAR;
                $mailBox = new EmailAddressType();
                $mailBox->EmailAddress =<EMAIL_ADDRESS>                $request->ParentFolderIds->DistinguishedFolderId->Mailbox = $mailBox;
                $request->Traversal = ItemQueryTraversalType::SHALLOW;
$response = $client->CreateItem($request);
..

In progress ;-)
With the code below then response is
Event failed to create with "ErrorFolderNotFound: The specified folder could not be found in the store."
when i try to write in "utilisateur"'s calendar.
Is it because i've no right on his calendar ?
$mailBox = new EmailAddressType();
$user_calendar = "utilisateur";
$domaine = "serveur.fr";
$mailBox->EmailAddress = "$user_calendar@$domaine";

$request->SavedItemFolderId = new TargetFolderIdType();
$request->SavedItemFolderId->DistinguishedFolderId = new DistinguishedFolderIdType();
$request->SavedItemFolderId->DistinguishedFolderId->Id=DistinguishedFolderIdNameType::CALENDAR;
$request->SavedItemFolderId->DistinguishedFolderId->Mailbox = $mailBox;

$response = $client->CreateItem($request);

oups


Use new lib-common 'PatchInstance' pattern

Introduces the use of lib-common's PatchIntstance() func and attempts to remove instance-update race condition concerns

looks good to me, could just use return ctrl.Result{}, nil as err is nil at the places where we return to update the object.

Whoops, that's an oversight on my part.  I will change that.


add macOS to product list

When trying to submit a new radar with the product set to OS X
this results in an error, presumably because OS X is no longer accepted and needs to be set to macOS instead

Already in 0a414d4dc37486563615195ae4430010327e5634

Is there an ETA on when a new release might include this update?

It looks like this is in the latest release. @amyworrall this can probably be closed.

This has actually changed again since this was posted. There's now a joint component for each platform.


Upgrade to 3.0.2

Recreating PR from fork, since that's the proper way to do things.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


discord bot

Description
Very simple discord bot, should be easy to set up. includes 3 commands: ban. unban and kick.
Fixes #55
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

Not tested
tbh I have not had the time to test it yet, as I don't have anybody to test it on atm.

@avinashkranjan is this around the thing you wanted, or is it to simple?

@vivax3794 More 2-3 features would be nice...Like Greeting new members with custom message...Asking them to read the Rules pages, changing nickname... I think that would be enough for a simple bot..

@all-contributors please add @vivax3794 for code and documentation


How to add rules to individually define image size for featured image?

I dont understand vue. I want to define rule for image size only in featured image upload option. How to achieve this?

Are you just trying to size it differently on the frontend? From the editor itself, the featured image is nothing more than a path to the image. You can define the size however you'd like on the public-facing side.

Every user is free to upload featured image with his own choice and it will create an impact on frontend presentation. I want it to be done by validation rules without touching the package itself. Please help me out.

There's really no need for validation rules, since the presentation of the post and its featured image are handled outside of this package. If you're referring to images within the editor, then yes, this package handles them.


Crashing on sorting inventory

After the newest update whenever you Right Click to sort inventory it crashes the game. Tested it a few different times to make sure it was this plugin causing the issue and sure enough whenever I disable it I can sort without crashing.

fixed in the latest update, sorry for the inconvenience!


Display send/recv in Bps instead of totals in the debug window

Moved from https://github.com/bitcoin/bitcoin/pull/21806
I find this far more useful for than the totals. For example, I can easily see which nodes are not really talking with this metric, and not so much with the totals (as is current functionality).
Example:-

Worth exploring. The sidebar probably should be updated to display the same data, possibly in addition to the totals.

@rebroad

Changed to WIP as I just noticed the column sorting is still using the old values.

You also could convert it to a draft:

What is the base period to calculate data-transfer rate?

What is the base period to calculate data-transfer rate?

In my first pull request it was from connection time to current time. Now it's from connection time to time of last send/recv.

Maybe have both and let the user decide which to hide/show?

Maybe have both and let the user decide which to hide/show?

where would you place the option?

Just have 4 columns, total in, total out, rate in, rate out.
Other applications let you rightclick the header area to hide/show them, but even if we can't have that, users can resize them to ~0 width.

Just have 4 columns, total in, total out, rate in, rate out.
Other applications let you rightclick the header area to hide/show them, but even if we can't have that, users can resize them to ~0 width.

It's a pain having to resize columns, and also they cannot be resized to zero. I'd rather wait until there's the ability to disable columns before creating a pull to add rate in addition to downloaded. There are already too many columns IMHO.

For values larger than 1000 bps the data should be shown in kbps, but it is not happening as in the highlighted example.

I agree. I'll upload an update shortly.

By the logic used by op, the displayed rate is the average rate of data transferred by the peer. But I personally would prefer that if the displayed rate was instantaneous and not average because it might happen that a node is inactive for quite some time, but the data they transferred earlier was so high, that the rate column is showing a significantly large rate of data transfer.

Yes, this does happen, for example in the case where there's IBD (initial block download) which has much higher transfer rates and then skews the numbers once that completes. I have another commit, which deals with this, and allows the calculation to be reset at the end of IBD. Shall I include that with this pull, or perhaps raise another pull in the future to include that?

@shaavan I am still testing the functionality for resetting at the end of IBD - have you already created a method for detecting this? I'd be interested in having a look at your code if so.

🐙 This pull request conflicts with the target branch and needs rebase.
Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

There hasn't been much activity lately and the patch still needs rebase. What is the status here?

Is it still relevant? ➡ Please solve the conflicts to make it ready for review and to ensure the CI passes.
Is it no longer relevant? ➡ Please close.
Did the author lose interest or time to work on this? ➡ Please close it and mark it 'Up for grabs' with the label, so that it can be picked up in the future.


rdc file play back failed on Unbutu 16.04 with remote android phone

Description
the error log is like following, do you have any clue?
Log     - Opening RDCFile /tmp/RenderDoc/OGLESIntroducingPVRUtils_2019.03.03_19.51.15_frame109.rdc
Warning - Unsupported screen format: depth: 16, red_mask: 3f, blue_mask: f800
Warning - Using RGB16 fallback, if this works your X11 server is reporting a bad screen format.
Warning - Unsupported screen format: depth: 16, red_mask: 3f, blue_mask: f800
Warning - Using RGB16 fallback, if this works your X11 server is reporting a bad screen format.
Log     - Opening capture remotely
Log     - Capture open complete
Log     - Capture ready on replay host
Error   - Couldn't choose default framebuffer config
Error   - Creating proxy driver failed: API initialisation failed
Warning - Unsupported screen format: depth: 16, red_mask: 3f, blue_mask: f800
Warning - Using RGB16 fallback, if this works your X11 server is reporting a bad screen format.
BTW: this rdc file can be loaded without error on window10 connecting to android phone.
Environment

RenderDoc build: latest local build.
Operating System: Ubuntu Linux 16.04
API: OpenGLES
GPU: AMD R7-350

and the GUI report Failed to open capture for replay: API initialisation failed

Something seems to be wrong with your X server configuration beyond just RenderDoc. These messages:
Warning - Unsupported screen format: depth: 16, red_mask: 3f, blue_mask: f800
Warning - Using RGB16 fallback, if this works your X11 server is reporting a bad screen format.

Are coming from Qt itself. From a quick google it seems like it might be related to using VNC, but I don't know for sure. Are you able to run other Qt programs as normal, and also other GL/GLES programs?
This message from RenderDoc:
Error - Couldn't choose default framebuffer config

Means that glXChooseFBConfig returned NULL when looking for an RGBA 8-bit color framebuffer config, which also seems to align with Qt's error messages that something is wrong with the X server configuration.

yes, I was using VNC, I should have installed the AMD graphics card driver, and glxinfo/glxgears works properly.
but you suggestion, I try some gles program and they crashed when init Eglcontext, seems there is something wrong not just renderdoc. I will further check why
thanks Baldurk!

one thing still puzzles me is that, If I choose to replay the trace on remote phone, do I still need to choose fbconfig from X server?

below are my glxinfo
GLX Visuals
visual  x   bf lv rg d st  colorbuffer  sr ax dp st accumbuffer  ms  cav
id dep cl sp  sz l  ci b ro  r  g  b  a F gb bf th cl  r  g  b  a ns b eat
0x025 16 tc  1  16  0 r  y .   6  5  5  0 .  .  0 16  0  0  0  0  0  0 0 None
0x026 16 tc  1  16  0 r  y .   6  5  5  0 .  .  0 16  8 16 16 16  0  0 0 None
0x027 16 tc  1  16  0 r  y .   6  5  5  8 .  .  0 16  8 16 16 16 16  0 0 None
0x028 16 dc  1  16  0 r  y .   6  5  5  0 .  .  0 16  0  0  0  0  0  0 0 None
0x029 16 dc  1  16  0 r  y .   6  5  5  0 .  .  0 16  8 16 16 16  0  0 0 None
0x02a 16 dc  1  16  0 r  y .   6  5  5  8 .  .  0 16  8 16 16 16 16  0 0 None
0x02b 16 dc  1  16  0 r  . .   6  5  5  8 .  .  0 16  8 16 16 16 16  0 0 None

RenderDoc needs to render textures, buffers and meshes locally on the host computer, even if the majority of the replay happens on the android device.
If that glxinfo output is not truncated then that definitely shows the problem, you should have many more visuals available on a normal system. The only visuals you have are 16-bit with 6-bit red, 5-bit green and blue. There are no visuals with full 24-bit colour (8-bit for red, green and blue). For example on my system the glxinfo output has a lot more visuals:
504 GLX Visuals
    visual  x   bf lv rg d st  colorbuffer  sr ax dp st accumbuffer  ms  cav
  id dep cl sp  sz l  ci b ro  r  g  b  a F gb bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------------
0x021 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  8  0  0  0  0  0 0 None
0x022 24 dc  0  32  0 r  y .   8  8  8  8 .  .  0 24  8  0  0  0  0  0 0 None
0x4cc 24 tc  0  32  0 r  . .   8  8  8  8 .  .  0  0  0  0  0  0  0  0 0 None
0x4cd 24 tc  0  32  0 r  . .   8  8  8  8 .  .  0  0  0 16 16 16 16  0 0 Slow
0x4ce 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0  0  0  0  0  0  0  0 0 None
0x4cf 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0  0  0 16 16 16 16  0 0 Slow
0x4d0 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0  0  0  0  0  0  0  0 0 None
0x4d1 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0  0  0 16 16 16 16  0 0 Slow
0x4d2 24 tc  0  32  0 r  . .   8  8  8  8 .  .  0 16  0  0  0  0  0  0 0 None
0x4d3 24 tc  0  32  0 r  . .   8  8  8  8 .  .  0 16  0 16 16 16 16  0 0 Slow
0x4d4 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 16  0  0  0  0  0  0 0 None
0x4d5 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 16  0 16 16 16 16  0 0 Slow
0x4d6 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 16  0  0  0  0  0  0 0 None
0x4d7 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 16  0 16 16 16 16  0 0 Slow
0x4d8 24 tc  0  32  0 r  . .   8  8  8  8 .  .  0 24  0  0  0  0  0  0 0 None
0x4d9 24 tc  0  32  0 r  . .   8  8  8  8 .  .  0 24  0 16 16 16 16  0 0 Slow
0x4da 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  0  0  0  0  0  0 0 None
0x4db 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  0 16 16 16 16  0 0 Slow
0x4dc 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  0  0  0  0  0  0 0 None
0x4dd 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  0 16 16 16 16  0 0 Slow
0x4de 24 tc  0  32  0 r  . .   8  8  8  8 .  .  0 24  8  0  0  0  0  0 0 None
0x4df 24 tc  0  32  0 r  . .   8  8  8  8 .  .  0 24  8 16 16 16 16  0 0 Slow
0x4e0 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  8 16 16 16 16  0 0 Slow
0x4e1 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  8  0  0  0  0  0 0 None
0x4e2 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  8 16 16 16 16  0 0 Slow
0x4e3 24 tc  0  32  0 r  . .   8  8  8  8 .  .  0  0  0  0  0  0  0  2 1 None
0x4e4 24 tc  0  32  0 r  . .   8  8  8  8 .  .  0  0  0  0  0  0  0  4 1 None
0x4e5 24 tc  0  32  0 r  . .   8  8  8  8 .  .  0  0  0  0  0  0  0  8 1 None
... many more ...
0x6b5 32 tc  0  32  0 r  . .   8  8  8  8 .  s  0  0  0  0  0  0  0  0 0 None
0x6b6 32 tc  0  32  0 r  y .   8  8  8  8 .  s  0  0  0  0  0  0  0  0 0 None
0x6b7 32 tc  0  32  0 r  y .   8  8  8  8 .  s  0  0  0  0  0  0  0  0 0 None
0x6b8 32 tc  0  32  0 r  . .   8  8  8  8 .  s  0 16  0  0  0  0  0  0 0 None
0x6b9 32 tc  0  32  0 r  y .   8  8  8  8 .  s  0 16  0  0  0  0  0  0 0 None
0x6ba 32 tc  0  32  0 r  y .   8  8  8  8 .  s  0 16  0  0  0  0  0  0 0 None
0x6bb 32 tc  0  32  0 r  . .   8  8  8  8 .  s  0 24  0  0  0  0  0  0 0 None
0x6bc 32 tc  0  32  0 r  y .   8  8  8  8 .  s  0 24  0  0  0  0  0  0 0 None
0x6bd 32 tc  0  32  0 r  y .   8  8  8  8 .  s  0 24  0  0  0  0  0  0 0 None
0x6be 32 tc  0  32  0 r  . .   8  8  8  8 .  s  0 24  8  0  0  0  0  0 0 None
0x6bf 32 tc  0  32  0 r  y .   8  8  8  8 .  s  0 24  8  0  0  0  0  0 0 None
0x6c0 32 tc  0  32  0 r  y .   8  8  8  8 .  s  0 24  8  0  0  0  0  0 0 None


Generated epub not valid

The generated epub works fine with my actual e-reader and with Sigil. But Google Play Books says it cannot import it and refers to http://validator.idpf.org/
And indeed, this validator says the epub has errors.

I know this has been open a while, but I finally got around to looking into the validation errors. I believe I have successfully corrected everything. The book now validates at the idpf link and I was able to import a ficdown-generated epub into Google Play Books. The website ficdown.com has been updated to the latest binary with these changes.


Slow karma tests

Hi,
At moment I have something like 1800 tests and all stuff I taking about 10s. Is there way to speed up by splitting test to run parallel.  I have also question about autowatch because I'm running unit test in background and would be nice to only run tests file that change.
This is my current config to autowatch
server: {
      configFile: 'test/unit/karma.conf.js',
      singleRun: false,
      autoWatch: true
    }

Yes use https://github.com/sindresorhus/grunt-concurrent

Now with the grunt-concurrent said there is a significant problem with specs being run slower now with going to the 0.12.X releases. In 0.10.1 my tests run within reason.
Please see https://github.com/karma-runner/karma/issues/1608

This should be closed especially since #1608 shows the most likely problem is huge blobs.


Improve the efficiency of vineyardd by avoid establishing new watches in requestUpdates

What do these changes do?
Improve the persist efficiency by avoiding new watches in requestUpdates.
For benchmark, current main branch takes 195.63s for 9 related testcases. While this PR only takes 82.64s (<50%)
Related issue number

Fixes #304.

I think this issue should resolves #200 as well, as etcd no longer runs under so heavy load.


Newbie can't install ubuntu linux onto Samsung Chromebook *crouton *xenial *xf

chronos@localhost / $ sudo startXfce4
sudo: startXfce4: command not found
chronos@localhost / $ sudo startxfce4
Entering /mnt/stateful_partition/crouton/chroots/xenial...
/usr/bin/startxfce4: Starting X server

_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

X.Org X Server 1.19.5
Release Date: 2017-10-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-101-generic armv7l Ubuntu
Current Operating System: Linux localhost 3.8.11 #1 SMP Mon Jan 8 23:08:25 PST 2018 armv7l
Kernel command line: cros_secure console= console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=4ffef4e3-d5d9-014c-8913-870f9cb251ca/PARTNROFF=1 hashtree=PARTUUID=4ffef4e3-d5d9-014c-8913-870f9cb251ca/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=5dfc0e062471fc717ee69c072cd2de2109072dc1 salt=a4347e1553b1a02b9bbaa9246374e08325dd29be09820ebd10525225453a5ef9" noinitrd vt.global_cursor_default=0 kern_guid=4ffef4e3-d5d9-014c-8913-870f9cb251ca
Build Date: 24 November 2017  09:45:24AM
xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.33.6
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Fri Jan 12 01:01:16 2018
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Error org.freedesktop.DBus.Error.UnknownMethod: Method "ReleaseDisplayOwnership" with signature "" on interface "org.chromium.LibCrosServiceInterface" doesn't exist

method return time=1515718876.563506 sender=:1.13 -> destination=:1.44 serial=1071 reply_serial=2
   boolean true
MESA-LOADER: failed to retrieve device information
gbm: failed to open any driver (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
gbm: Last dlopen error: /usr/lib/dri/exynos_dri.so: cannot open shared object file: No such file or directory
failed to load driver: exynos
EGL_MESA_drm_image required.
(EE)
Fatal server error:
(EE) AddScreen/ScreenInit failed for driver 1
(EE)
(EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/tmp/Xorg.crouton.1.log" for additional information.
(EE)
Error org.freedesktop.DBus.Error.UnknownMethod: Method "TakeDisplayOwnership" with signature "" on interface "org.chromium.LibCrosServiceInterface" doesn't exist

method return time=1515718877.629928 sender=:1.13 -> destination=:1.46 serial=1073 reply_serial=2
   boolean true
(EE) Server terminated with error (1). Closing log file.
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Connection refused
/usr/bin/xinit: server error
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

Hi, I'm new to Linux and new to github, but was hoping someone from the community could help me with this problem I'm having trying to install ubuntu on an old Samsung Chrome book (Snow: Daisy - CPU: Samsung Exynos 5 Dual (5250) (Cortex A15; 1.7GHz dual core cpu). GPU: ARM Mali-T604 (Quad Core). I have tried various crouton installs but always fail at the 'sudo startXfce4' command? Any advice would be greatly appreciated and/or a pointer in the right direction. thanks guys.
If known, describe the steps to reproduce the issue: sudo startXfce4

Hey-
I had this problem on my machine too. I'm pretty sure most of the problem stems from having an arm processor, but I don't know much more than that. Thanks for that resource, Morantz!

I'm not so sure about the arm processor thing. I had until recently run trusty in a crouton. I am currently having trouble reinstalling it after corrupting the SD card it was on, and wondered if xenial had a problem with the arm processor, but trusty definitely works.

Hey guys, thanks for helpful advice and resources/links.
I tried trusty the first time and when that failed I tried xenial, which
also failed. I suspect it is to do with the arm chip. Also my machine has
lost its OS now after all this flipping between developer mode, so won't
boot now, so have to start from new. Lol
Best way to learn linux I guess?
Regards,
Dieter
On Sun, 25 Feb 2018, 08:29 pogo555<EMAIL_ADDRESS>wrote:

I'm not so sure about the arm processor thing. I had until recently run
trusty in a crouton. I am currently having trouble reinstalling it after
corrupting the SD card it was on, and wondered if xenial had a problem with
the arm processor, but trusty definitely works.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3606#issuecomment-368292157,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhtL5Erg_1H0j2TpAGz2psmOLnxkoWDPks5tYRnRgaJpZM4RcB6R
.

Seems this issue has been around for quite a while now and is related to video-armsoc drivers.
Take a look at this comment for a little more info.: https://github.com/dnschneid/crouton/issues/3611
For a couple of workarounds, see this comment: https://github.com/dnschneid/crouton/issues/3291#issuecomment-309564813
Note that in Solution 1 above you may have to substitute 'startxfce4' with your start script.
Hope this helps,
-DennisLfromGA


Port finetuning from Lit-LLaMA

[ ] full
[ ] LoRA
[x] Adapter #31

hi is fine tuning from lit-Llama file available yet? For now it seems 1 time training but if we can continue fine tuning form lit-LLama It would be quite helpful

@joseph35533553 We have adapter merged (https://github.com/Lightning-AI/lit-parrot/blob/main/howto/finetune_adapter.md), and Lora on its way: #128


feat!: Spanner V2

TODO

[ ] consider alternatives to withResultFunction(), such as MessageActiveRecordInterface::fromMessage(Message $message). which would allow the OperationResponse to call this method in order to "hydrate" the protobuf object
[ ] investigate why info methods are now returning values for all fields

looked into this, it seems like V1 and V2 work the same, but the way the tests were written in V1, the response was mocked to not include all the fields.

[ ] investigate project ID detection (it isn't working for V2 like it does for V1)
[ ] Look into "Project ID Detection", which doesn't seem to be working well
[ ] Investigate why multiplexedSessionPreviousTransactionId needed to be added to tests

TBD:

can we remove the longRunningOperation methods on the handwritten classes in favor of using the existing list*Operations methods?
What is the appropriate behavior when resumeOperation is called on a database for an instance operation?

closing in order to split this into two PRs.
See https://github.com/googleapis/google-cloud-php/pull/7840


womanium final assignment

womanium final assignment
PR Description
Womanium Assignment submission

[x] Please make sure that you placed the files in an appropriate folder

[x] And that the files have indicative names.

[x] Please note that Classiq runs automatic code linting, which may minorly alter some files.

[x] If you're familiar with pre-commit, you may run pre-commit install, and then at each commit, your files will be altered in a similar way

The code lacks a 'main` function and does not follow the class instructions. Consider resubmitting.
Score: 4/10


Remove-DbaAgentJobCategory to support pipeline from Get-* function

Type of Change

[ ] Bug fix (non-breaking change, fixes # )
[x] New feature (non-breaking change, adds functionality, fixes # )
[x] Breaking change (effects multiple commands or functionality, fixes # )
[x] Ran manual Pester test and has passed (.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[x] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Unit test is included
[ ] Documentation
[ ] Build system

Purpose

To support pipeline from Get-* function
Removed the -Force parameter, so it can be used with the pattern from other Remove-* commands with -Confirm:$false instead.
Approach

Similar to #7997
Commands to test

Get-DbaAgentJobCategory -SqlInstance SRV1 | Out-GridView -Title 'Select SQL Agent job category(-ies) to drop' -OutputMode Multiple | Remove-DbaAgentJobCategory
Screenshots

Learning

One test fails because you need a help entry for InputObject.

merci 🔥 !


Execution Error

Hi,
I am trying to execute the script but its keep throwing below error. I have created a Label for the disk autosnapshot:true(key:value). I would like to backup all the disks in a Zone which has the label.
gcloud-snapshot.sh -t autosnaphot -z us-central1-a -a<EMAIL_ADDRESS>2018-11-07 13:53:39: Start of Script
2018-11-07 13:53:39: Start of createSnapshotWrapper
ERROR: (gcloud.compute.disks.snapshot) argument --zone: expected one argument
Usage: gcloud compute disks snapshot DISK_NAME [DISK_NAME ...] [optional flags]
optional flags may be  --async | --csek-key-file | --description |
--guest-flush | --help | --snapshot-names | --zone
For detailed information on this command and its flags, run:
gcloud compute disks snapshot --help
2018-11-07 13:53:40: Start of deleteSnapshotsWrapper
Listed 0 items.
2018-11-07 13:53:41: End of Script
Do am I missing any?.
$ gcloud --version
Google Cloud SDK 224.0.0
alpha 2018.11.02
app-engine-java 1.9.63
app-engine-python 1.9.67
beta 2018.11.02
bq 2.0.36
core 2018.11.02
gsutil 4.34
kubectl 2018.11.02

I've created a debug branch that has some logging to help me see which part of the script is failing for you.
Installation instructions for debug branch:
cd ~
wget https://raw.githubusercontent.com/jacksegal/google-compute-snapshot/debug/gcloud-snapshot.sh
chmod +x gcloud-snapshot.sh
sudo mkdir -p /opt/google-compute-snapshot
sudo mv gcloud-snapshot.sh /opt/google-compute-snapshot/

Then run the script with your options:
sudo /opt/google-compute-snapshot/gcloud-snapshot.sh -t autosnaphot -z us-central1-a -a<EMAIL_ADDRESS>
If you include your output I can try and see which part isn't working.
Thanks,
Jack

Thanks for your reply. As informed, have tried to execute and still see the same error.
Attached output as mentioned.
$ ./gcloud-snapshot.sh -t autosnaphot -z us-central1-a  -a<EMAIL_ADDRESS>2018-11-08 01:32:51: Start of Script
2018-11-08 01:32:51: Start of createSnapshotWrapper
INSTANCE_NAME: test
INSTANCE_ZONE: us-central1-a
INSTANCE_ID:<PHONE_NUMBER>388
DEVICE_LIST:
DEVICE_NAME:
ERROR: (gcloud.compute.disks.snapshot) argument --zone: expected one argument
Usage: gcloud compute disks snapshot DISK_NAME [DISK_NAME ...] [optional flags]
optional flags may be  --async | --csek-key-file | --description |
--guest-flush | --help | --snapshot-names | --zone
For detailed information on this command and its flags, run:
gcloud compute disks snapshot --help
2018-11-08 01:32:52: Start of deleteSnapshotsWrapper
Listed 0 items.
2018-11-08 01:32:53: End of Script

Thanks for your reply. As informed, have tried to execute and still see the same error.
Attached output as mentioned.
$ ./gcloud-snapshot.sh -t autosnaphot -z us-central1-a -a<EMAIL_ADDRESS>2018-11-08 01:32:51: Start of Script
2018-11-08 01:32:51: Start of createSnapshotWrapper
INSTANCE_NAME: test
INSTANCE_ZONE: us-central1-a
INSTANCE_ID:<PHONE_NUMBER>388
DEVICE_LIST:
DEVICE_NAME:
ERROR: (gcloud.compute.disks.snapshot) argument --zone: expected one argument
Usage: gcloud compute disks snapshot DISK_NAME [DISK_NAME ...] [optional flags]
optional flags may be --async | --csek-key-file | --description |
--guest-flush | --help | --snapshot-names | --zone
For detailed information on this command and its flags, run:
gcloud compute disks snapshot --help
2018-11-08 01:32:52: Start of deleteSnapshotsWrapper
Listed 0 items.
2018-11-08 01:32:53: End of Script
I am executing the script in remote system to backup selected volumes in our project.

Hi,
Yes the Label and zone is correct. I am running this scripts from different zone, will it have any issue.
./gcloud-snapshot.sh -t autosnaphot -a<EMAIL_ADDRESS>2018-11-08 12:58:06: Start of Script
2018-11-08 12:58:06: Start of createSnapshotWrapper
INSTANCE_NAME: test
INSTANCE_ZONE: asia-southeast1-a
INSTANCE_ID: 123456
DEVICE_LIST:
DEVICE_NAME:
ERROR: (gcloud.compute.disks.snapshot) argument --zone: expected one argument
Usage: gcloud compute disks snapshot DISK_NAME [DISK_NAME ...] [optional flags]
optional flags may be  --async | --csek-key-file | --description |
--guest-flush | --help | --snapshot-names | --zone
For detailed information on this command and its flags, run:
gcloud compute disks snapshot --help
2018-11-08 12:58:07: Start of deleteSnapshotsWrapper
Listed 0 items.
2018-11-08 12:58:08: End of Script
$ ./gcloud-snapshot.sh -z us-central1-a -a<EMAIL_ADDRESS>2018-11-08 12:53:44: Start of Script
2018-11-08 12:53:44: Start of createSnapshotWrapper
INSTANCE_NAME: test
INSTANCE_ZONE: us-central1-a
INSTANCE_ID: 123456
DEVICE_LIST:
DEVICE_NAME:
ERROR: (gcloud.compute.disks.snapshot) argument --zone: expected one argument
Usage: gcloud compute disks snapshot DISK_NAME [DISK_NAME ...] [optional flags]
optional flags may be  --async | --csek-key-file | --description |
--guest-flush | --help | --snapshot-names | --zone
For detailed information on this command and its flags, run:
gcloud compute disks snapshot --help
2018-11-08 12:53:45: Start of deleteSnapshotsWrapper
Listed 0 items.
2018-11-08 12:53:46: End of Script
When I directly use gcloud command with filters retrieves the disk.
$ gcloud  compute disks list --filter "labels:autosnapshot" --format='value(name)'
vol-i-123445--dev-xvda-abcdefg

Hmmm, can you run this command:
$ gcloud compute disks list --filter "labels:autosnapshot"

It's the same command you ran to get the disk(s), but without the formatting - it will return all of the information about the disk(s)

$  gcloud compute disks list --filter "labels:autosnapshot"
NAME                                        ZONE           SIZE_GB  TYPE    STATUS
vol-i-123445--dev-xvda-abcdefg  us-central1-a  10       pd-ssd  READY

I think there might be a typo in your first command - it says autosnaphot (missing an "s" before the "h" - autosnapshot).
Could that be the problem?  Does it work when you run this command (your original command, with the typo fixed):
$ ./gcloud-snapshot.sh -t autosnapshot -z us-central1-a -a<EMAIL_ADDRESS>

No I ran it without typo

Right, if you are running it on a "remote instance" then you need to also use the [-i <instance_name] input.  Where the instance_name is the name of the instance you want backed up.

Noted, the script will not work only with the labels?.

Sorry, I'm not entirely sure what you mean?
The script was primarily designed to only backup the instance that runs the script.
It was extended to work with remote instances too, but to allow it to work with remote instances, you need to pass through the inputs instance_name and instance_zone.
Let me know if the script works when you pass in instance_name

Hi, yes its working with instance name. In my previous reply I just asked whether is it possible to create snapshots from remote system without specifying instance name and just only provide label filters.

Great, glad to hear it's working!
No, that isn't currently possible - but is a probably a good idea for a future enhancement

@satrox28 ,
I ended up doing some changes to the script (#66) and it's now possible to backup remote instances without specifying instance info:
./gcloud-snapshot.sh -r

Please note: I've also removed the -t flag.  You can filter using the -f flag which uses gcloud filter expressions - for example to backup all remote disks with label of auto_snapshot=true:
./gcloud-compute-snapshot.sh -r -f "labels.auto_snapshot=true"

@jacksegal
It's working now, thanks. I am trying to execute the script with -d 5 but 6days snapshots are kept.
Below are the snapshots with Timestamp
gcs-vol-abc--dev-xvdc-abcde-1542326400
gcs-vol-abc--dev-xvdc-abcde-1542326400
gcs-vol-abc--dev-xvdc-abcde-1542412800
gcs-vol-abc--dev-xvdc-abcde-1542499200
gcs-vol-abc--dev-xvdc-abcde-1542585600
gcs-vol-abc--dev-xvdc-abcde-1542672000
gcs-vol-abc--dev-xvdc-abcde-1542758400

Can you use "dry-run" mode (-n) and add the output to this issue?


Error messages are difficult to read.

Error messages are difficult to read.
Occurs in next-i18next version 0.37.0
# yarn.lock
<EMAIL_ADDRESS>  version "0.37.0"
  resolved "https://registry.yarnpkg.com/next-i18next/-/next-i18next-0.37.0.tgz#d82d69ae69cc4617be4385168a348795646bb59a"
  integrity sha512-QGyTJy96gxSuU6bpTSag6d5VAbUVIPttPgWFWu0Exk22PZ/iabIV+XcaB9h8RFBtJMn8bu+VD3jdhQ3mIZkGlA==
  dependencies:
    detect-node "^2.0.4"
    hoist-non-react-statics "^3.2.0"
    i18next "^15.0.0"
    i18next-browser-languagedetector "^3.0.0"
    i18next-express-middleware "^1.5.0"
    i18next-node-fs-backend "^2.1.0"
    i18next-xhr-backend "^2.0.0"
    path-match "^1.2.4"
    pretty-error "^2.1.1"
    prop-types "^15.6.2"
    react-i18next "

Steps to reproduce
Do not include namespacesRequired to get a warning about the performance implications.
Here is the error rendered in my Webstorm terminal with the Darcula theme.

Sometimes my shell is quirky so I thought maybe this is my fault, but here is a screenshot of the same errors rendered in the Chrome developer console in the default theme:

Browser: Chrome Version 73.0.3683.86 (Official Build) (64-bit)

Sorry - what is the actual request here?

The error messages that come from this library are extremely difficult to read.  See the screenshots above.  This happens for both server side errors rendered on my terminal and client-side errors rendered in chrome developer tools.
I think we should provide some kind of theme for pretty-error or stop using it.  Right now I can only read those error messages by highlighting the error text.

Let's stop using it. I'll remove it sometime this week. Thanks.

Fixed by #259.


rest_xml codegen cleanup

Cleaning up the leftover bits from #321 as enumerated in #500

@adimarco this ready for review?


Make tensorflow optional dependencies

Would be nice if this library did not install a version of TF if it doesn't find one—i.e. allow the end user to supply own TF.
I'm not familiar with setup.py but something like an "optional" or "suggested" dependency.

Closing this... was on an older version of the library for some reason


Retry type Ignore does not clear error

What version of Cassandra are you using?
Scylla Enterprise 2024.1.8
What version of Gocql are you using?
github.com/gocql/gocql v1.6.0
What version of Go are you using?
go 1.21.11
What did you do?
used RetryType Ignore (https://pkg.go.dev/github.com/gocql/gocql#RetryType) on write query
What did you expect to see?
I expected that query.Exec() would not return error
What did you see instead?
the error is returned.

Maybe the documentation is not clear on how Ignore and Rethrow are different?
I thought Ignore would make it so that Exec does not return error ? Maybe this would be strange on read ops but it can be used on writes (in Downgrading CL retry policy for example ). But they both return error and I don't see any difference between those retry types
Is there any difference in Rethrow and Ignore retry types  ?

Example (on empty cluster , keyspace error is ok for our test )
MyRetryPolicy can return Ignore or Rethrow - it changes nothing
package main

import (
	"context"
	"fmt"
	"time"

	"github.com/gocql/gocql"
)

type MyRetryPolicy struct {
}

func (*MyRetryPolicy) Attempt(q gocql.RetryableQuery) bool {
	if q.Attempts() > 2 {
		return false
	}
	return true
}

func (*MyRetryPolicy) GetRetryType(error) gocql.RetryType {
	return gocql.Ignore
}

type LoggingObserver struct{}

func (*LoggingObserver) ObserveQuery(ctx context.Context, q gocql.ObservedQuery) {
	fmt.Printf("observer attempt: %d err: %s\n", q.Attempt, q.Err)
}

func main() {
	cluster := gocql.NewCluster("node-1")
	cluster.Authenticator = gocql.PasswordAuthenticator{
		Username: "scylla",
		Password: "***",
	}

	s, err := gocql.NewSession(*cluster)
	if err != nil {
		fmt.Printf("session err: %s\n", err)
	}
	defer s.Close()

	q := s.Query("INSERT INTO  my.events(event_id, time, args) VALUES (?,?,?)", 1, gocql.UUIDFromTime(time.Now()), "test")

	q.RetryPolicy(&MyRetryPolicy{})
	q.Observer(&LoggingObserver{})

	fmt.Printf("QUERY IsIdempotent: %v\n", q.IsIdempotent())

	err = q.Exec()
	if err != nil {
		fmt.Printf("exec err: %s\n", err)
	}

}

Output
➜  test go run main.go
QUERY IsIdempotent: false
observer attempt: 0 err: Keyspace my does not exist
exec err: Keyspace my does not exist

need to add ignored error in ObserverdQuery too

I honestly don't see a use case for Ignore, we should probably just deprecate it.

Hmm other drivers also have Ignore so we can probably keep it as well but we need to fix the behavior and add tests to ensure it's properly fixed and there's no regressions in the future.


Unexpected character '�' (1:0)

node v8.0.0 + laravel v5.4 + vue v2.3.3 报错：
ERROR  Failed to compile with 1 errors                                                                                11:42:52
error  in<EMAIL_ADDRESS>Module parse failed<EMAIL_ADDRESS>Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type.
(Source code omitted for this binary file)
<EMAIL_ADDRESS>1:16-69
@ ./resources/assets/js/bootstrap.js

could be a backspace?
a lot of mixed text ends up with half characters that don't display frmo someone deleting one byte of a two-byte character

Getting the same error here too.
Node 8.4.0
Ionic 3
Uncaught Error: Module parse failed: ***/node_modules/nodejieba/build/Release/nodejieba.node Unexpected character '�' (1:0)
Any idea how to stop this ?

I can't use it in electron, same error. Have tried  ./node_modules/.bin/electron-rebuild

Same problem with this  ***/node_modules/nodejieba/build/Release/nodejieba.node  file

it's loading a binary file

Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type.
(Source code omitted for this binary file)

I've seen those type of characters before when encoding gets messed up eg utf8 / shiftJIS. but not sure for binary files
is this a win/unix thing with the 'BOM' issue?

@pengjinning @yanyiwu
Hey. I just ran into this issue while transpiling my server code.
Looks like it's failing because the library imports a .node file on line 1.
var nodejieba = require( __dirname + "/build/Release/nodejieba.node");

I fixed it by including the node-loader loader for .node files in my webpack.config.js file.
module: {
    rules: [
      {
        test: /\.node$/,
        use: 'node-loader',
      },
      // other loaders come after
  ]
}

This worked for me. Not sure if my use-case for this similar to yours but give this a try. 🙂

good find @abinavseelan can you send a PR 🗡

@dcsan  That cannot be fixed in nodejieba's side. To use it should change the config of project's webpack.


✨ bring back query tests for node 21

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1778

Relevant Lines:
1778

💛  - Coveralls


Update Tool help for Create GRG from Point

Red square missing around the call out area
Expected Behavior

The image in the tool help should have a red square around the callout image to provide clarity
Current Behavior

There is no red square around the call out area and it is hard to understand the graphic at first.
Possible Solution

Add a red square around the call out area
Steps to Reproduce (for bugs)

Open the tool help
View the image

Context

Your Environment

Version used:
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop or mobile):
Link to your project:

Here is an example image of what it looks like now.

Also the lines should match up with the squares on the map

@topowright Addressed in PR #637

This looks good


skinchanger

https://github.com/bruhmoment21/cs2-sdk/blob/39edbbe1849df351df6f851c3f5dfcbee4d0e546/cs2cheat/src/game/skins/skin_changer.cpp#L10-L11


[Usability issue] "Network error" notification, even though everything is fine

Storeman shows a "Network error" notification on the top of the screen, when started.  After that everything works fine (if there is no real network problem).
The "funny" thing is, this usability issue only occurs on one of my Jolla 1 phones (this runs SFOS 2.2.1), while on another Jolla 1 (also with SFOS 2.2.1) and an Xperia X (with SFOS 3.0.0) that does not happen.  But on the Jolla 1 phone affected, it happens on every start of Storeman.
I would not have bothered to file this issue (assuming it is caused by a local misconfiguration), if not @monkeyisland reported a similar issue at OpenRepos.  Although @monkyisland reports it to happen when entering the bookmarks (on a Jolla 1 phone with SFOS <IP_ADDRESS>), which always works on my affected Jolla 1 phone.
Tested with Storeman 0.0.32 and I guess this is the first version with which this issue occurred (not sure though, as there have been many Storeman releases in November: 0.0.29, 0.0.30, 0.0.31 and 0.0.32).
P.S.: This is definitely different than issues #37 and #50, connmanctl state outputs State = online.
P.P.S.: Screenshot

Could someone please try the dev version and check if there is still an issue with error notification?

That is harbour-storeman-0.0.33-1.24.1.jolla.armv7hl.rpm at the moment, correct?
I hope to find some time tonight, but unfortunately my two Jolla 1 phones switched behaviour: Storeman 0.33-3 stopped emitting "Network error!" on the phone where it first appeared, but continues to do so on my "production phone".  My Xperia X still has not exhibited this issue.
So it is a little hard to obtain a conclusive test result, as this issue seems to come and go even without deliberate changes.

Can you please start Storeman from terminal:
harbour-storeman

and see if there are any warnings concerning networking?

Yes:

I went back to Storeman 0.0.33-3, because this is my production phone (but currently the only one permanently exhibiting this issue).
If you want me to test Storeman 0.0.33-1.24.1 at the command line, please let me know.
Yes, there is a network related error upon each start of Storeman 0.0.33-3:
[W] unknown:0 - Network request error QNetworkReply::NetworkError(ContentOperationNotPermittedError) - "Error transferring https://openrepos.net/api/v1/session - server replied: : Access denied for user anonymous"
While this warning is consistently displayed in consecutive tests, on the first test I was confronted with multiple "Authentication error" notifications.  No idea, if this was related to this issue or not, but it did not happen on any later test, although I did not reauthenticate my user account for OpenRepos or did anything else but starting and stopping Storeman.

The "Authentication error" comes from launching Storeman from command line. Normally it's launched by the invoker which grants access rights to operations with packages. So just ignore it.
Nevertheless the warning you have caught points the direction for further investigations :+1:

BTW:

Cross checked on the other Jolla 1 (which stopped displaying "Network error" a few weeks ago): It does not show this warning when Storeman is started at the command line (as expected), while all other output at the command line is exactly the same.
Thanks for the info that the "Authentication error" notifications are related to pkcon / libzypp (and hence unrelated the this issue).

I think I found the reason of repeating this notification:

Your user session expired
Storeman offered you to re-login
You closed Storeman without re-login
On next start Storeman started to show this notification

The problem was in bad storing of session data. Now after session expiry Storeman clears its data and doesn't show this annoying notification.
Can you please try once again the OBS build?

Sorry, Storeman 0.33-1.25.1 shows exactly the same behavior, at the command line and at the GUI, before and after a reboot.
BTW, on little thing in your description I do not concur with:

Storeman offered you to re-login
You closed Storeman without re-login
I usually reauthorise myself immediately when Storeman informs me to do so.
But I have the impression that Storeman still sometimes looses the user authorisation at OpenRepos without noticing it (that may even be unavoidable with OpenRepos' current API behavior.

Try to logout and login again.

Did that, after updating from 0.0.33-3 (I am reverting to it after testing) to 0.0.32-1.25.1 again.

Storeman started at the command line did not seem to like trying to log out from OpenRepos: my avatar picture and status "Logged in as olf" was still shown, despite trying to log out three times.
Closing Storeman and staring it at the GUI resulted in Storeman continuously displaying the "waiting circle" on its main page.
So I rebooted, started Storeman (still 0.0.33-1.25.1) at the GUI: Now I was logged out of OpenRepos, being able to log in and ... no "Network error" upon a restart of Storeman at the GUI.
So I closed Storeman and started it from the command line.  Now a new warning is emitted each time:
[W] unknown:461 - file:///usr/lib/qt5/qml/Sailfish/Silica/private/PulleyMenuBase.qml:461:13: QML State: Binding loop detected for property "when"
Sometimes another warning is additionally displayed:
[W] unknown:-1 - <Unknown File>: QML StateGroup: Can't apply a state change as part of a state definition.
Once I also saw a [W] unknown:0 - libpng warning: iCCP: known incorrect sRGB profile, but cannot reproduce it.

I've added a temporary code that should stop showing these notifications in your case.

I do not fully understand all the things the QML code added in commit 30d7449 does, but permanently storing ones user name at OpenRepos is actually a general usability improvement, IMO.  I did not care to file this as an issue here yet, because it is rather minor, but currently it is annoying to have to type in ones user name again, each time one misses to hit Storeman's notification to reauthorise.

Please try the new one version from OBS :)

You are too quick for me. 😉
More seriously:

I know I am your only tester for this issue, currently.
Editing comments here at Github does not repost them per email.  Hence edits should be limited to corrections and clarifications, but not comprise added information (I regularly fail to adhere to this rule).
Consequently I did my testing earlier this night with 0.0.33-1.25.1, as I checked email, but not this web page.

I may take a look at the new build in the next couple of days.
But actually I am more concerned about the reproducibility of steps 1. and 2. in my previous comment: I only tried that once, yet (as it needs reinstalling 0.0.33-3 and then 0.0.33-1.2x.y again).

The warning in step 5. of my previous comment is emitted when entering "This device" in Storeman's top menu.

Logging out and back in at OpenRepos in Storeman 0.0.33-1.25.1 takes two tries:

Logging in fails.
Logging in succeeds, but Storeman emits a notification at the GUI, that the login at OpenRepos failed (which was not displayed in step 1., but looks like the message from there).

Output at the command line, covering both steps above:

[W] unknown:38 - file:///usr/lib/qt5/qml/Sailfish/Silica/private/Util.js:38: TypeError: Cannot read property 'parent' of null
[W] unknown:38 - file:///usr/lib/qt5/qml/Sailfish/Silica/private/Util.js:38: TypeError: Cannot read property 'parent' of null
[W] unknown:0 - Network request errorerror QNetworkReply::NetworkError(AuthenticationRequiredError) - "Host requiresrequires authentication"

Reply to https://github.com/mentaljam/harbour-storeman/issues/82#issuecomment-460484464
Points 5 and 6 seem to concern Silica bugs. Point 7 concerns icons that are loaded from OpenRepos.net (it's not critical).
Reply to https://github.com/mentaljam/harbour-storeman/issues/82#issuecomment-460491539
This commit adds the code that adapts the old configuration to the new one. In fact it just logs you out to rewrite the configuration on next login. Quite a dirty thing but it occurs once after update.
Reply to https://github.com/mentaljam/harbour-storeman/issues/82#issuecomment-460494712
It's strange. I have logged out and in for dozens of times without any error while was testing.

WRT:

Points 5 & 6: O.K.
Point 7: Already assumed that, fine then.
Your explanation, what commit 30d7449 does: Thanks, that might help me to better understand what is happening while testing.
Points 1 & 2:
As usual I went back to Storeman 0.0.33-3 after the last round of tests with 0.0.33-1.25.1.
Tonight I wanted to retest with Storeman 0.0.33-1.26.1, but now Storeman 0.0.33-3 does not show a "Network error" when started (I tried a couple of times starting at the GUI and command line, plus rebooted once in between), anymore.
AFAIU, Storeman 0.0.33-1.25.1 did not alter the configuration file (commit 30d7449 was for 0.0.33-1.26.1, right?), so I assume that deleting ~/.config/harbour-storeman/harbour-storeman.conf would not help restoring the old state (with "Network error" on startup), correct?

How shall I proceed?
Just updating to Storeman 0.0.33-1.26.1 and checking I cannot reproduce this issue anymore?  But I cannot reproduce it anymore, already. :\

To reproduce this issue on 0.0.33-3 from OpenRepos.net:

log in
close Storeman
open ~/.config/harbour-storeman/harbour-storeman.conf in any text editor
change the value of user/token inside @ByteArray() (make it invalid)
open Storeman

After these steps you should see "Network error" on startup. It's happening because in fact you're not logged in (the token is invalid) but Storeman thinks you are.
If you then update to Storeman from OBS it will (I hope) clear invalid token and other data from the user section of the config except the username to make it easier to log in next time.

@Olf0 shame on me! I just realized that OBS didn't update sources before building storeman-dev. I've uploaded a fresh RPM built with SDK here on GitHub.

Thanks, now understand what is going on, even without understanding the QML code.
And you seem to be quite sure to have fixed this issue.
Checking:

To reproduce this issue on 0.0.33-3 from OpenRepos.net: [...]

Nice, this allows me to use my testing phone for the final test.

Altered a single character of the cookie hash in ~/.config/harbour-storeman/harbour-storeman.conf.
Started Storeman at the command line.

A warning "Network error" is emitted at the command line.
A "Reauthorize at OpenRepos" notification is displayed at the GUI, likely obstructing the "Network error" message there.

Hence starting a second time at the command line: "Network error" there and at the GUI.

Great, now this issue is fully reproducible for me. 🙌

I've uploaded a fresh RPM built with SDK here on GitHub.

Downloaded and installed it per pkcon install-local.
Starting Storeman at the command line:

No "Network error" at the command line and GUI.
No warnings #5 (Silica) and #6 (QML state) at the command line.
Just curious: did you suppress them or are they really gone (this is a different Jolla 1 phone than the one used in former tests of this issue)?
New GUI: nice, although I have to get used to it (I had no issues with the old GUI, hence this is a change I have adapt to without gaining anything; but this is a very personal perspective, the new GUI is definitely better for new users).

Observations:

When Storeman was already started and closed at least once since last reboot of the device, v0.0.33-3 from Github emits [W] unknown:0 - OrnRecentAppsModel(0xdeadbeef) Model is already fetching data at the command line twice.
v0.0.33-3 from OpenRepos always did that only once.
When started the second time, Storeman 0.0.33-3 from Github becomes stuck in an endless loop emitting "An error occurred Click to view details" notifications right after startup.
When tapping on one such notification an error page is opened, displaying "An error occurred Failed to obtain authentication.".
I first attributed this to accidentally altering the cookie value instead of the token value.
But it also happens (or persists?) when altering the token value.
This behavior persists over a reboot.  I will continue to experiment, what exactly causes this, how to revert to a working state and how to trigger it again.

Experiments with Storeman 0.0.33-3 from Github:

Putting back an originally working configuration file from v0.0.33-3-OpenRepos lets v0.0.33-3-Github work fine.
Using an configuration file with an altered / broken token value now results in v0.0.33-3-Github entering the "An error occurred" loop on this first try.

So I started at the beginning, again:

Reverted to Storeman 0.0.33-3-OpenRepos and its original, working configuration file: Endless loops of "An error occurred" notifications!
Rebooted: Now Storeman 0.0.33-3-OpenRepos is working fine.
Using a configuration file with an altered / broken token, Storeman 0.0.33-3-OpenRepos emits no "Network error", but enters the endless "*An error occurred *" loop, again.
Rebooted, using a configuration file with an altered / broken cookie:

First start of Storeman 0.0.33-3-OpenRepos: "Network error" at the command line, "Authorization required" notification at the GUI.  No refreshing of repositories, as the time threshold was not reached, yet.
Manually triggered refreshing the repos (This device -> Repositories -> Refresh cache): Storeman 0.0.33-3-OpenRepos enters the "An error occurred" loop.
Second start: "Network error" at the command line, entering the "An error occurred" loop immediately.

Conclusions so far:

Storeman 0.33-3 (no matter which version) is running wild, when the token value is incorrect, as soon as refreshing the repositories starts.
It keeps on running wild, even if restarted with a correct configuration file, until the device is rebooted!
The original issue WRT an incorrect / outdated cookie value seems to be fixed (ai still have to check that a second time).

Rebooted, installed Storeman 0.0.33-3-Github (with a broken cookie configuration), no "Network error" (and no automatic rpo refresh): Yes, the original issue is fixed.
Manually triggered refreshing that repos: "An error occurred" loop.

IMO refreshing the repos should work, even if authentication at OpenRepos fails.
P.S.: Thank you for cleaner up the configuration file, leaving only the necessary values in there.

Tried to rectify the configuration values by manually logging into OpenRepos in Storeman 0.0.33-3-Github, rebooted: Even though it now shows "Logged in as olf" in the settings, the "An error occurred" notifications start, as soon as the repositories are refreshed.
I really wonder, why I did not run into this originally (with v0.0.33-3-OpenRepos and "Network error" due to an outdated / incorrect cookie, thus the authentication at OpenRepos should have failed, but no "An error occurred" notifications chain emitted), but now both v0.0.33-3 versions show this when authentication at OpenRepos fails, sometimes even after a reboot!?!
Still, v0.0.33-3-Github only seems to work as an upgrade path to resolve the original issue, if it is installed in a moment, when the cookie has not been outdated.
If not, a much more annoying issue arises (long chain of "An error occurred" notifications), which I have been unable to resolve at the GUI, yet.  Although the orientation issue is definitely fixed.

BTW, I have had a bad gut feeling while testing tonight, by alternatingly installing two RPMs with exactly the same name, version and release number: I once learnt that one always increase at least the release number, as soon as a single character in the sources or the spec file is changed.
rpm, libzypp, pkcon etc. can / do not really distinguish between such two RPMs, despite their differing content.
Although I have no specific indication that the Storeman's files were not correctly installed each pkcon install-local run.

A last observation with Storeman 0.0.33-3-Github, before reverting to tv0.0.33-3-OpenRepos and its original, working configuration file:
Exactly in the moment, when the chain of "An error occurred" starts (either automatically by Storeman' timeout or manually triggered by "Refresh cache"), two warnings are emitted at the command line:
[W] unknown:461 - file:///usr/lib/qt5/qml/Sailfish/Silica/private/PulleyMenuBase.qml:461:13: QML State: Binding loop detected for property "when"
[W] unknown:-1 - <Unknown File>: QML StateGroup: Can't apply a state change as part of a state definition.

... as these are the old points 5 and 6, maybe they arr related to this "follow up issue".

And it was still there with Storeman 0.0.33-3-OpenRepos (as soon as the repos are refreshed).
I had to uninstall and reinstall Storeman to get rid of it!
Either the identical package numbers confuse rpm or something else may be strange with the packaging.

The "Failed to obtain authentication." error is a PackageKit error. It occurs when PackageKit fails to obtain required rights to perform system actions. In you case it occurs because you launched Storeman from the command line when normally it should be launched with the invoker (I've mentioned it earlier in this thread).

O.K. I missed or misunderstood this earlier.
Just an idea: Prefixing the error messages with their origin (i.e., in this case "[pkcon] ") would make them much easier to relate to their source).
Anyway, closing as the original issue seems to be solved.


Add portuguese translation 💪🇦🇴🇧🇷🇨🇻🇹🇱🇬🇶🇬🇼🇲🇴🇲🇿🇵🇹🇸🇹💪

Hi, I just add this Portuguese translation on Breez fork so I'm sharing it here now.
About the translation, Brazilian Portuguese is my mother language, there are important differences in Brazilian Portuguese and other variants, especially on the conjugation of the second person (singular and plural), gerund x periphrastic, vocabulary, etc… So to have a wide Portuguese support it is necessary at least the European and African variations, nevertheless, it is still the same language so all Portuguese speakers can understand it perfectly.

Thank you @ademar111190 that's fantastic.

Hi @ademar111190,
No, I'm not waiting for anything from you - just not had chance yet to merge this PR.
Thanks.

Thank you both @ademar111190 & @bitcoinuser for your contributions. I have not merged these yet as I am currently working on new features and will have new text strings. Would you be happy to translate these new strings when they become available?


Support the STORAGE_EMULATOR_HOST environment variable for StorageClient

Is your feature request related to a problem? Please describe.
We're using the firebase emulator, and we want to be able to configure the StorageClient via environment variables
Describe the solution you'd like
We'd like to be able to configure the StorageClient's host via the STORAGE_EMULATOR_HOST environment variable
Describe alternatives you've considered
We are currently setting the address via code, as described here.
Additional context
This is already supported by the GO and Node clients

Will have a look at this. One thing that the .NET libraries are consistent about is not just using an environment variable. We'd do this in the same way - see https://cloud.google.com/dotnet/docs/reference/help/emulators for examples.
(I wasn't aware that the Firebase emulator implemented a full Storage service... Will need to test it thoroughly.)

Hmmm... I've just had made a first attempt at this, and the emulator just rejects all requests. I need to look in more detail as to what it will accept.

Ah - my mistake, I'd used the emulator UI port instead of the API port. Doh. Looks like it's working now - with the limitations around no bucket operations, etc. Will see if I can get it more production-ready and create a PR.

We have it working here without any changes, at least for basic upload/download
Except for a workaround on UpdateObjectAsync, which fails (we haven't dug too much into it for our needs though)

Will look into UpdateObjectAsync as part of the work - thanks for calling that out.

We were having errors trying to update both CacheControl and Metadata with UpdateObjectAsync.
The error was:
The service storage has thrown an exception.
HttpStatusCode is NotImplemented.
No JSON error details were specified.
Raw error details are: Not Implemented

Could be a limitation on the emulator, but it would not be documented.

Yes, I suspect it's an emulator limitation - as you say, object update claims to be supported, but I get the same results as you, even changing a different field (customDateTime). I can patch a change to metadata, but not a change to customDateTime. I don't know how the Firebase Emulator versioning keeps up with the Storage API versioning. I'll ask internally about the object update part not working, but obviously that's somewhat separate to the client library support itself.

This is implemented in #11535, which will be in the next release.


Add Alternate bad words & stop words list

bad word list:

https://github.com/thisandagain/washyourmouthoutwithsoap/blob/develop/data/build.json
This one is the current one used, which seems to use translation from english
https://github.com/LDNOOBW/List-of-Dirty-Naughty-Obscene-and-Otherwise-Bad-Words
This is also cited here: https://huggingface.co/datasets/allenai/c4
I noticed it has Chinese (zh), which the current one doesn't have.

stop word list:  I did some googling and maybe some of them that has languages we don't have.

https://github.com/stopwords-iso/stopwords-iso
https://github.com/Alir3z4/stop-words
https://github.com/bbalet/stopwords

I think we can write a simple script for each source that downloads and loads the list.
@HugoLaurencon What do you think?

Hello @cccntu, thank you for your help!
I actually just replaced the stopwords list from nltk by this one https://github.com/6/stopwords-json in this commit https://github.com/bigscience-workshop/data_tooling/commit/abaa0b496970e13107ffa010b5e14be3d80661e9
I thought this list was pretty complete and of good quality, I'll add the Vietnamese and Urdu language from this one https://github.com/stopwords-iso/stopwords-iso as you suggested. Let me know if you think this list seems good to you.
I'll take a look at the bad word list too.

Cool! Thank you for your hard works! @HugoLaurencon
That list you mentioned looks good to me. I like its REAME.
One minor suggestion:
Split the into txt files, so it's easier to view on Github. Especially unicode string like in 'ar'.
And you can have def load_stopwords in stopwords.py

Also merged your list https://github.com/LDNOOBW/List-of-Dirty-Naughty-Obscene-and-Otherwise-Bad-Words with the previous one, and this one https://github.com/zacanger/profane-words for English bad words.
Sure, we'll do it when reviewing the structure of the code (some people said one folder per language for data and parameters)


The generated TypeInference class does not have access to _Imports.razor usings

Describe the bug:
When working with generic components and type inference, the TypeInference class is not generated in a context where _Imports.razor usings are available. I'm hitting this when a where clause needs to be repeated on that class.
Version used:
VS2022 17.0.1
SDK 6.0.100, Microsoft.AspNetCore.App 6.0.0
To reproduce:
Run dotnet build in https://github.com/Tragetaschen/blazor-type-inference-class-usings-issue
Expected behavior:
None of the files in the project show any errors in VS, so I expect the build to succeed.
Actual behavior:
Building produces the error
…\Microsoft.NET.Sdk.Razor.SourceGenerators\Microsoft.NET.Sdk.Razor.SourceGenerators.RazorSourceGenerator\App_razor.g.cs(60,23): error CS0246: The type or namespace name 'MyModel' could not be found (are you missing a using directive or an assembly reference?) […\repro.csproj]

Additional context:
In the App_razor.g.cs, there is a TypeInference class that does not have any usings within its namespace:
namespace __Blazor.repro.App
{
    #line hidden
    internal static class TypeInference
    {
        public static void CreateGeneric_0<T>(global::Microsoft.AspNetCore.Components.Rendering.RenderTreeBuilder __builder, int seq, int __seq0, global::repro.Services.IService<T> __arg0, int __seq1, global::Microsoft.AspNetCore.Components.RenderFragment<T> __arg1)
            where T : MyModel
        {
        __builder.OpenComponent<global::repro.Generic<T>>(seq);
        __builder.AddAttribute(__seq0, "Service", __arg0);
        __builder.AddAttribute(__seq1, "R", __arg1);
        __builder.CloseComponent();
        }
    }
}

so the MyModel type in the where clause is not found.

@chsienki Something bad happened. Besides this transfered issue with all the history, #7456, #7463, #7472, and #7477 were also created, but without any history.
This happened for three more of my issues as well