PG instrumentation does not parse quoted table names in queries into the 'db.collection.name' attribute

Description of the bug
The PG instrumentation library is using a regex here to extract the table name from queries in order to set the db.collection.name trace attribute. This regex does not match quoted table names, for instance SELECT * from "foo" will not return a match.

Share details about your runtime
Operating system details: Linux, Ubuntu 24.04
RUBY_ENGINE: "ruby"
RUBY_VERSION: "3.3.4"
RUBY_DESCRIPTION: "ruby 3.3.4 (2024-07-09 revision be1089c8ec) [x86_64-linux]"
This also happens on various production instances, I can get that information if needed.
Share a simplified reproduction if possible
I've been reproducing this by adding this to the tests for pg on a local fork
diff --git a/instrumentation/pg/test/opentelemetry/instrumentation/pg/instrumentation_test.rb b/instrumentation/pg/test/opentelemetry/instrumentation/pg
/instrumentation_test.rb
index cc50728e..7c1c2590 100644
--- a/instrumentation/pg/test/opentelemetry/instrumentation/pg/instrumentation_test.rb
+++ b/instrumentation/pg/test/opentelemetry/instrumentation/pg/instrumentation_test.rb
@@ -275,6 +275,13 @@ describe OpenTelemetry::Instrumentation::PG::Instrumentation do
       client.query('DROP TABLE test_table') # Drop table to avoid conflicts
     end

+    it 'extracts table name with quotes' do
+      client.query('CREATE TABLE "test_quotes_table" (personid int, name VARCHAR(50))')
+
+      _(span.attributes['db.collection.name']).must_equal '"test_quotes_table"'
+      client.query('DROP TABLE test_quotes_table') # Drop table to avoid conflicts
+    end
+
     describe 'when db_statement is obfuscate' do
       let(:config) { { db_statement: :obfuscate } }

This seems to fix it, though I'm pretty green at ruby and the inner workings of this library, so I don't know if there are knock-on effects here.
diff --git a/instrumentation/pg/lib/opentelemetry/instrumentation/pg/patches/connection.rb b/instrumentation/pg/lib/opentelemetry/instrumentation/pg/pat
ches/connection.rb
index 98814950..6330abee 100644
--- a/instrumentation/pg/lib/opentelemetry/instrumentation/pg/patches/connection.rb
+++ b/instrumentation/pg/lib/opentelemetry/instrumentation/pg/patches/connection.rb
@@ -15,7 +15,7 @@ module OpenTelemetry
         # Module to prepend to PG::Connection for instrumentation
         module Connection # rubocop:disable Metrics/ModuleLength
           # Capture the first word (including letters, digits, underscores, & '.', ) that follows common table commands
-          TABLE_NAME = /\b(?:FROM|INTO|UPDATE|CREATE\s+TABLE(?:\s+IF\s+NOT\s+EXISTS)?|DROP\s+TABLE(?:\s+IF\s+EXISTS)?|ALTER\s+TABLE(?:\s+IF\s+EXISTS)?)
\s+([\w\.]+)/i
+          TABLE_NAME = /\b(?:FROM|INTO|UPDATE|CREATE\s+TABLE(?:\s+IF\s+NOT\s+EXISTS)?|DROP\s+TABLE(?:\s+IF\s+EXISTS)?|ALTER\s+TABLE(?:\s+IF\s+EXISTS)?)
\s+(["\w\.]+)/i

           PG::Constants::EXEC_ISH_METHODS.each do |method|
             define_method method do |*args, &block|

Hi @mostfunkyduck! Thank you submitting this issue and sharing what you did to get things working properly. Would you be interested in making a contribution?
For testing, the file instrumentation/pg/test/fixtures/sql_table_name.json feeds each entry into this test. I think we could update the fixtures file to keep things consistent. Perhaps adding something like:
    {
      "name": "table_name_with_single_quotes",
      "sql": "SELECT columns FROM 'test_table'"
    },
    {
      "name": "table_name_with_double_quotes",
      "sql": "SELECT columns FROM \"test_table\""
    }

For the updated regex, is it desirable to include the quotes in the end result? Your suggestion would take care of this (although could be updated to recognize single quotes too).
If we don't want to include the quotes, and to account for both single and double quotes, we could do:
TABLE_NAME = /\b(?:FROM|INTO|UPDATE|CREATE\s+TABLE(?:\s+IF\s+NOT\s+EXISTS)?|DROP\s+TABLE(?:\s+IF\s+EXISTS)?|ALTER\s+TABLE(?:\s+IF\s+EXISTS)?)\s+["']?([\w\.]+)["']?/i

Would love to hear your thoughts ◡̈

I can take a shot at it! Just need to go through the contributor's guide.
We probably should not include the quotes for consistency's sake - two queries on the same table should produce the same attribute regardless of whether quotes are used - so I'll keep them outside the capture.
As far as single quotes, this SO post quotes the postgres manual as saying that single quotes are only for string constants, so they'd be a syntax error if they were wrapping the table name.

@mostfunkyduck - excited to see your contribution come through 🎉 I agree on keeping the quotes out and its also great to learn about single quotes v double quotes in this context, thank you for sharing that.

Hi @mostfunkyduck! Did going through the contributor's guide go okay? Seeing if you need anything ◡̈


Add more task commands

Codecov Report

Merging #83 (db8d371) into master (cdfc83b) will decrease coverage by 2.56%.
The diff coverage is 4.71%.

@@             Coverage Diff              @@
##             master      #83      +/-   ##
============================================
- Coverage     50.55%   47.98%   -2.57%
- Complexity      487      490       +3
============================================
  Files           119      124       +5
  Lines          2176     2305     +129
  Branches        255      277      +22
============================================
+ Hits           1100     1106       +6
- Misses          992     1113     +121
- Partials         84       86       +2

Impacted Files
Coverage Δ

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)

...a/seedu/address/logic/commands/AddTaskCommand.java
0.00% <ø> (ø)

...seedu/address/logic/commands/ClearTaskCommand.java
0.00% <0.00%> (ø)

...eedu/address/logic/commands/DeleteTaskCommand.java
0.00% <ø> (ø)

.../seedu/address/logic/commands/EditTaskCommand.java
0.00% <0.00%> (ø)

...java/seedu/address/logic/commands/ListCommand.java
100.00% <ø> (ø)

.../seedu/address/logic/commands/ListTaskCommand.java
0.00% <0.00%> (ø)

...edu/address/logic/parser/AddTaskCommandParser.java
0.00% <0.00%> (ø)

...seedu/address/logic/parser/ClearCommandParser.java
50.00% <0.00%> (-10.00%)
:arrow_down:

.../seedu/address/logic/parser/EditCommandParser.java
40.00% <0.00%> (-10.00%)
:arrow_down:

... and 19 more

Continue to review full report at Codecov.

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

LGTM, just some nits to iron out :)


Pretty-print /json/* responses

Currently, the JSON responses are one liners, which makes it hard to
read.
This adds two spaces of indentation to the responses.

Thanks!


[RFC] Redesign dmlc::Parameter.

There are a few problems in dmlc::Parameter I want to address:
Issues
Initialization
Currently dmlc::Parameter uses a static manager (__MANAGER()__ method) class to carry out all the initialization steps.  The problem is this manager is created per-class instead of per-instance, so there is no way that it can understand whether a particular parameter instance has been initialized.  As a side effect, we cannot do update operation on it, which results in every call of Configure a complete re-initialization. See #4738 .  Once JSON is here the problem will spread through all other parameters.

Adding a initialized_ field to dmlc::Parameter won't work as it will break all binary IO logic (size is changed).
Adding a std::map<Parameter*, bool> initialized_ field to the manager won't work, as distinguishing instance by pointer breaks easily with stack allocated objects:

{
  Param p;
}
{
  Param p0;  // Same address as p
}

Adding non-trivial constructor/destructor to dmlc::Parameter calling __MANAGER()__ won't work.  I tried and get a dead lock from static variables, stuck at :

__cxa_guard_acquire

Another issue is the parameter can't initialize itself.  It troubles me and @RAMitchell  for quite a while now as those primitive types has undefined values at initialization.  As described above, calling __MANAGER()__ will operate on class level.  Also, one can imagine calling any method from this __MANAGER__ is quite dangerous.
Description is not very useful.
The one most duplicated code in XGB is those description of parameters, as there's no way we can query the document from C++ level, resulting in those descriptions being copied across XGBoost.
Namespace
As XGBoost has so many parameters that can form a small embedded language, putting all of them into one std::vector makes precise validation really difficult.
What's next
I don't have any concrete idea yet.  But discussions are welcomed.  @RAMitchell @CodingCat @hcho3 Please join.

Yes! This is a long-due discussion. See #3803, for example, where we have no way to detect runtime update of a field in dmlc::Parameter and thus leak memory.

Thanks @trivialfis. As this functionality lives in dmlc-core it can be very difficult for us to change as we will impose changes on mxnet etc.
I see two paths forward:
a) We build our own xgboost parameter classes
b) We RFC these issues up to dmlc-core and try to engage developers of dependent libraries
Upstreaming could be relatively easy if the existing functionality is more or less preserved, otherwise difficult if we are changing some features they rely on.
I think we can create a linked issue on dmlc-core, and when we have a proof of concept PR for how to solve these issues, decide on a) or b).
Aso, we have two other pieces of code that are candidates to be upstreamed in the future:

common::Span
improved JSON parser.

I think some of the features could be built on top of the current Paramater. It can be a bit hard to say that lazy initialization(ignore what is being configured) is really what we want.  As the simplest way to reason about the object is to treat it as immutable and update all the field if necessary.
One thing we could do is to add helper factory functions to initialize the parameters. Additionally, we might be able to move away from POD, and just add default value initializers now that we have cxx11, and create custom serializer for these parameters
In terms of documentation. I started to believe more that duplication for better documentation could be better than an adhoc solution that generates semi complete docs. It also allows us to create language specific docs. So as long as we have reasonable duplication it should be fine.

@tqchen Thanks for the suggestions.  Will think about these later.

As the simplest way to reason about the object is to treat it as immutable and update all the field if necessary.

I still want finer control over each hyper parameter.

One thing we could do is to add helper factory functions to initialize the parameters. Additionally, we might be able to move away from POD.

That's a good idea, I will try to stay close to dmlc::Parameter as much as possible so we can upstream the changes in the future.

It also allows us to create language specific docs.

This is not a priority for now as we don't have frequent change in parameter, nor do I understand the document system for all bindings.


sdk: add passkey signer

Description
corresponding sui change: https://github.com/MystenLabs/sui/blob/main/crates/sui-types/src/passkey_authenticator.rs
spec follows:
https://github.com/sui-foundation/sips/blob/main/sips/sip-9.md#signature-encoding
https://github.com/sui-foundation/sips/blob/main/sips/sip-9.md#signature-verification
Test plan
unit tests
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:
[ ] REST API:

TypeError: Object.defineProperty called on non-object
 ❯ test/unit/cryptography/passkey.test.ts:29:10
     27|   const sk = secp256r1.utils.randomPrivateKey();
     28|
     29|   Object.defineProperty(global.navigator, 'credentials', {
       |          ^
     30|    value: {
     31|     create: vi.fn().mockImplementation(async () => ({

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/3]⎯

i cant seem to reproduce this failure locally - when i run pnpm turbo test all tests passed, any ideas @Jordan-Mysten @hayes-mysten

tests run in node, and I think node 22 was the version that added navigator.  You probably have a newer node version locally than is used in ci


PyGIWarning on headless Ubuntu

I installed using the README instruction (download the AppImage, do chmod, add to path), and ran it on Ubuntu, go the error message below. Did the same thing on my mac it worked.
OS: Ubuntu 16.04, it is a headless server (no monitor)
orca release used: https://github.com/plotly/orca/releases/tag/v1.0.0
orca graph '{ "data": [{"y": [1,2,1]}] }' -o fig.png
/usr/lib/python3/dist-packages/pyatspi/__init__.py:17: PyGIWarning: Atspi was imported without specifying a version first. Use gi.require_version('Atspi', '2.0') before import to ensure that the right version gets loaded.
  from gi.repository import Atspi
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
The following are not valid: graph { "data": [{"y": [1,2,1]}] } -o fig.png
Cannot start the screen reader because it cannot connect to the Desktop.

Thanks for the reply. I did a minimal test-run and it gave a new error:
/usr/lib/python3/dist-packages/pyatspi/__init__.py:17: PyGIWarning: Atspi was imported without specifying a version first. Use gi.require_version('Atspi', '2.0') before import to ensure that the right version gets loaded.
  from gi.repository import Atspi
The following are not valid: graph { "data": [{"y": [1,2,1]}] } -o fig.png

(orca:12602): dconf-WARNING **: failed to commit changes to dconf: Could not connect: Connection refused

(orca:12602): dconf-WARNING **: failed to commit changes to dconf: Could not connect: Connection refused

** (orca:12602): ERROR **: AT-SPI: Couldn't connect to accessibility bus. Is at-spi-bus-launcher running?
Trace/breakpoint trap (core dumped)

Ok. Are you running this from the command line or from a python script or somewhere else?

yes indeed. I am running the example command from README on the bash terminal. not via python runtime, so that warning was weird. Found something online but not sure if it's related: http://gnome-orca.1098411.n5.nabble.com/orca-list-a-strange-message-when-starting-orca-td37954.html

Ha. Well, our orca command must be conflicting with Gnome's orca.
What does
$ which orca

return for you?

it would seem so. ran any orca command and the same thing pops up, see below:
$ which orca
/usr/bin/orca

$ orca -v
/usr/lib/python3/dist-packages/pyatspi/__init__.py:17: PyGIWarning: Atspi was imported without specifying a version first. Use gi.require_version('Atspi', '2.0') before import to ensure that the right version gets loaded.
  from gi.repository import Atspi
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
3.18.2

Ok, so then how did add plotly's orca to your path?

# ... download to home
$ chmod +x ~/orca-1.0.0-x86_64.AppImage
$ export PATH=~/orca-1.0.0-x86_64.AppImage:$PATH

I think a path has to be a directory, not an executable
So,
# ... download to home
$ chmod +x ~/orca-1.0.0-x86_64.AppImage
$ export PATH=~/:$PATH

should work.
But I'd recommend,
# ... download to home
$ mkdir -p ~/bin
$ mv ~/orca-1.0.0-x86_64.AppImage ~/bin
$ chmod +x ~/bin/orca-1.0.0-x86_64.AppImage

and have
PATH="$HOME/bin:$PATH"

somewhere in your shell rc file. Or similarly with ~/.local/bin instead ~/bin

hi, did that. in fact also tried putting it into /usr/bin which is in the PATH, and it is giving the exact same issue.

oh actually did a clean wipe and reinstalled using npm global. that works on terminal. thank you, you may close this issue.


Linear Search Added

Linear Search added. Happy Hacktoberfest!!

Thank you for contributing to Algorithms/CPP, your pr got merged! ✨


[IDE] Add result builder code completion for buildPartialBlock

Resolves #59885. Adds missing code completion support for buildPartialBlock.

@swift-ci Please smoke test


Integration tests for EC2 image filters

Fixes #208
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Integration tests passed


standalone_2/io/async_catch_errors_test turned from flaky to Timeout on dartkp-linux-product-x64

There are new test failures on [cfe] Don't show context on type argument issues if location is null...Revert "Revert "Move most of the code from u/b/kernel_worker.dart to p/frontend_server"".
The tests
standalone_2/io/async_catch_errors_test Timeout (expected Pass)

are failing on configurations
dartkp-linux-product-x64

Could be related to https://github.com/dart-lang/sdk/issues/46168.

The test standalone/io/async_catch_errors_test also turned from flaky to Timeout on dartk-strong-linux-release-x64 and dartk-weak-asserts-linux-release-x64 configurations.
Log:
--- Command "vm" (took 01:00.000452s):
DART_CONFIGURATION=ReleaseX64 out/ReleaseX64/dart --sound-null-safety --ignore-unrecognized-flags --packages=/b/s/w/ir/.packages /b/s/w/ir/tests/standalone/io/async_catch_errors_test.dart

exit code:
null

diagnostics:
Process list including children: [12240]
Trying to capture stack trace for pid 12240
PID 12240 - process
TID 12240:
#0  0x00007f2030c69ad3 pthread_cond_wait@@GLIBC_2.3.2
#1  0x00005624566b62f8 dart::Monitor::WaitMicros(long)
#2  0x0000562456b3ce4a Dart_RunLoop
#3  0x000056245642b052 dart::bin::RunMainIsolate(char const*, char const*, dart::bin::CommandLineOptions*)
#4  0x000056245642bfd7 dart::bin::main(int, char**)
#5  0x000056245642cd69 main
#6  0x00007f20304eebf7 __libc_start_main
#7  0x00005624564254e9 _start
TID 12241:
#0  0x00007f20305eea47 epoll_wait
#1  0x000056245643b6f8 dart::bin::EventHandlerImplementation::Poll(unsigned long)
#2  0x000056245656c1c0 dart::bin::ThreadStart(void*)
#3  0x00007f2030c636db start_thread
#4  0x00007f20305ee71f __clone
TID 12245:
#0  0x00007f2030c69ad3 pthread_cond_wait@@GLIBC_2.3.2
#1  0x00005624566b62f8 dart::Monitor::WaitMicros(long)
#2  0x00005624567568e7 dart::BackgroundCompiler::Run()
#3  0x00005624567439b8 dart::ThreadPool::WorkerLoop(dart::ThreadPool::Worker*)
#4  0x0000562456743dec dart::ThreadPool::Worker::Main(unsigned long)
#5  0x00005624566b5ba8 dart::ThreadStart(void*)
#6  0x00007f2030c636db start_thread
#7  0x00007f20305ee71f __clone

stdout:
unittest-suite-wait-for-done

--- Re-run this test:
python3 tools/test.py -n dartk-strong-linux-release-x64 standalone/io/async_catch_errors_test

Same happened on dartk-strong-linux-debug-x64 and dartk-weak-asserts-linux-debug-x64 configurations.
https://dart-ci.appspot.com/log/vm-kernel-nnbd-linux-debug-x64/dartk-strong-linux-debug-x64/4127/standalone/io/async_catch_errors_test
https://dart-ci.appspot.com/log/vm-kernel-nnbd-linux-debug-x64/dartk-weak-asserts-linux-debug-x64/4127/standalone/io/async_catch_errors_test

Also on https://dart-ci.web.app/#showLatestFailures=false&test=standalone/io/async_catch_errors_test&configurations=vm-eager-optimization-linux-release-ia32


Fill data on create new page

Hi all,
I am new to serenity, I need small help that when i open the new page i need some textbox to be filled by default.
Is there any option to figure this out.
Thanks.

Check samples in Demo.


New designs for notifications & rename ChecNotification to ChecToast

The hover state on the button is broken:

The button style is wrong, as there seems to be some font styling that's overwriting the button font, but I guess that this is a pre-existing issue.

@ScopeyNZ updated


Update log4cats-core to 2.3.0

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

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "log4cats-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequest = { frequency = "@monthly" },
  dependency = { groupId = "org.typelevel", artifactId = "log4cats-core" }
}]

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

Superseded by #46.


React-Loadable and Typescript example?

Hello, can you add an example that combines react-loadable and typescript together, cuz I have a lot of problems trying to make them work together... Thanks.

Thanks, I'll take a look into it.

hi @lednhatkhanh did you get it to work? Typescript + react loadable in razzle?


quickstart-nodejs to 0.0.4

Promote quickstart-nodejs to version 0.0.4

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@h-philipp: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

promotion-build
200eb8869bdbfa4b65cd2a19c800517e6dcc33c2
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Add language changer button

📝 Feature Description
Add a language change button to the app to allow users to switch between different languages easily. This feature would enable users to select their preferred language from a list, improving accessibility for non-native speakers and creating a more personalized experience.
🔧 How Will This Enhance the App?
Adding a language change button would enhance the app by making it accessible to a global audience, improving user engagement and retention across diverse regions. By allowing users to interact with the app in their preferred language, the app becomes more user-friendly and welcoming, ensuring that language is not a barrier to usage.
🎯 Use Cases
Multilingual Users: Users who speak multiple languages may prefer switching languages depending on context or location.
Non-native English Speakers: Users who are more comfortable in a language other than English can use the app more intuitively.
International Users: The app can be more accessible and reach a wider audience by supporting multiple languages, especially in non-English-speaking countries.
📦 Suggested Implementation
UI Design: Add a language change button in a prominent location, such as the settings menu or the app’s main toolbar.
Language Options: Display a dropdown menu with supported languages, ideally showing the language name in the native language (e.g., "Español" instead of "Spanish").
Persistent Language Setting: Once a language is selected, the preference should be saved and applied each time the user logs in.
Dynamic Content Loading: Use translation files or a localization library to support on-the-fly language changes without requiring an app restart.
📸 Additional Context

@Antima2004 Hi, currently in our website theme, i don't think it'll be any effect.

i would request you to find and rasie new issues! keep contributing

Thanks


Landsat TM/MSS Collection 2 - NASA CMR API Authentication

Hi,
I've been having a look at your "Landsat TM/MSS Collection 2" dataset that is currently in preview and have encountered some difficulty in passing authentication details to the NASA CMR API.
Where do I go to generate a token for the NASA CMR API? Can a token be generated for free or are there data partnership constraints?
Thanks,
Ben

Hi Ben,
I've never used the CMR API before, but I think that https://urs.earthdata.nasa.gov/ is the place to start.
We hope to have these datasets in our STAC API before too much longer, but don't have an exact date yet.


Add YFHI token

Team background:
Yfhionline is created by Yearn.finance Members of the community are self-organized, and the team members are from traditional financial and emerging Internet financial companies such as lending club, motifinvesting, estimize, sigfig, kabbage and prosper.
Basic information of the project:
Yfhi is a decentralized Finance (defi) platform, which refers to the formation of cluster interactive intelligent aggregator based on the aggregation flow pool, which automatically completes the liquidity mining. Through the comprehensive data of defi, the contract generates the highest income in the transaction interaction, which will give users a proof of rights and interests called yfhi token.
More about YFHI
domain name: https://www.yfhi.online/
Twitter：https://twitter.com/YFHIonline
GitHub：https://github.com/yfhionline/YFHI
media coverage
https://www.jinse.com/news/blockchain/973988.html
https://news.huoxing24.com/20210105190855770241.html
https://www.beekuaibao.com/ztc/797185383183966208
https://www.beekuaibao.com/article/797111961565290496
http://www.fengniaocaijing.com/article/detail?article_id=219098
proposal gas limit：60000
Listed exchanges
Uniswap launched on February 7

非常抱歉，无法合并。

非常抱歉，无法合并。


Inno setup - /LANG should also support locale codes

Testing #205564
I think that the /LANG should also support the well known locale codes (ex: HU, HU_HU) along with hungarian.

Not actually sure many people use /lang to set the setup language. In general inno setup tries to detect the language of your PC so not sure it's worth to add the locale code, but if we would do so it would just require adding another language entry.
Name: "english"; MessagesFile: "compiler:Default.isl,{#RepoDir}\build\win32\i18n\messages.en.isl" {#LocalizedLanguageFile}
Name: "en"; MessagesFile: "compiler:Default.isl,{#RepoDir}\build\win32\i18n\messages.en.isl" {#LocalizedLanguageFile}

// cc @joaomoreno

/LANG is a feature of Inno Setup. We do not expose it as a VS Code feature.


[use case] Accessing build details

Build duration
Build started at
Type of trigger
Similar issues on GitHub on failed builds
Access to artifacts (https://github.com/fastlane/ci/blob/master/docs/use_cases/access_build_artifact.md)
Rebuild button (if manual trigger is enabled)

Similar issues on GitHub on failed builds #449

Access to artifacts #450

Build info page: Rebuild button (if manual trigger is enabled) #451

We already have that https://github.com/fastlane/ci/blob/master/docs/use_cases/access_build_artifacts.md


2.4.7 Missing `coerce_shell_command' for DockerCookbook::DockerBase:Class under vagrant/chef-solo/berkshelf

Environment:
Running on Mac OSX 10.11.3, using VirtualBox:
chef-solo -v
Chef: 12.6.0
berks -v
4.0.1
vagrant version
Installed Version: 1.8.1
Latest Version: 1.8.1
vagrant plugin list
vagrant-berkshelf (4.1.0)
vagrant-share (1.1.5, system)
docker cookbook version 2.4.7
Scenario:
During provisioning of a VM with vagrant/chef-solo the docker cookbook fails to load with a
NoMethodError
undefined method `coerce_shell_command' for DockerCookbook::DockerBase:Class
Full traceback can be seen here:
https://gist.github.com/evansde77/8901a70e8c31dd718146#file-chef-output
At first I suspected this was something I had done, so I stripped it down and reproduced the issue in a bare new berks cookbook just by adding the docker cookbook as a dependency in the metadata.rb for the cookbook and provisioning.
Reverting the docker cookbook version from 2.4.7 to 2.4.5 allowed provisioning to proceed.
Steps to Reproduce:
I outlined the steps to reproduce this in this gist:
https://gist.github.com/evansde77/8901a70e8c31dd718146
Essentially, adding the docker cookbook dependency to the metadata.rb triggers the problem
Expected Result:
Adding the cookbook as a dependency should let the cookbook compile during the chef run.
Actual Result:
Provisioning step fails with the traceback linked above

I have been getting the same error on Windows.
Host OS: Windows 10
Vagrant: version 1.8.1
Guest OS: Ubuntu 15.04
It was very strange because it happened non-stop on one computer.
I found that changing the docker cookbook that was cached in Berkshelf so that I could puts the instance_methods of the class showed that the method was defined. I was at a loss.
I tried it out on another computer...and it worked fine. But now it's happening on that computer too. Not sure what changed...
The docker cookbook worked all day earlier today on the original computer where it had not been working! And now back to not working on this second computer.

Does this still happen on v2.4.9?

@someara No, version 2.4.9 did not solve the problem for me. I think the problem is that this line in docker_base.rb:
include DockerHelpers::Base

does not allow the class DockerBase to call methods defined in the included file. I think it would allow an instance of DockerBase to call the methods, but not from within the class definition itself. (I'm not super familiar with ruby includes, but it seems to be the case, but I found this: http://stackoverflow.com/questions/15097929/ruby-module-require-and-include#answer-15098219).
Having an include and an extend seems to work:
include DockerHelpers::Base
extend DockerHelpers::Base

The addition of extend may also be needed in docker_container.rb and docker_service_base.rb

Pull request #622

I can't reproduce this with test-kitchen no matter how hard I try.
I've tried manually specifying compat_resource 12.5.23, 12.5.24, 12.5.25 and 12.5.26 and they all converge without a problem.
12.7.0 throws enough errors and warnings that I'm considering it broken.
@jkeiser does PR #622 give any clues to what's going on?
Perhaps there is some brokenness with the vagrant-berkshelf?
PS: you should really be using test-kitchen to drive Vagrant. The vagrant-berkshelf plugin injects cookbooks into the machine using Serious Hacks. Test-kitchen handles this properly. The vagrant-berkshelf was deprecated years ago and is no longer maintained.

@someara I'll have to give TestKitchen a try some time. I had tried it about a year ago and it didn't seem to work on a Windows host.

This is the project that I was using that was seeing the error. It uses Vagrant to spin up a VM, then uses the docker cookbook to install Docker.

can confirm that this issue isnt present under test kitchen, so since that seems to be the new weapon of choice ill switch to that.

@evansde77 Dave, if not too much trouble, could you test my fix before switching to Test Kitchen. It fixes it for me, but someone else will have to verify that it fixes it for them and so far you're the only one who has reported it.

@NickMRamirez I cloned your version of the docker cookbook and re-ran, it looks like it fixed the problem but there is a lot of other noise there. Output here: https://gist.github.com/evansde77/0b0aaf36bdb984a7c42a

Hmm...I see those messages too. I don't think they're related. They seem to be talking about how properties have a default value of nil and how there's a null reference when calling a method called validate.

Also experiencing this. Cookbook runs fine when using test kitchen but when using vagrant & chef_zero provisioner I get the same error.

Okay I'm starting to see this on travis -
https://travis-ci.org/chef-cookbooks/docker/builds/106678195
On Tue, Feb 2, 2016 at 6:35 PM, Jamie Thompson<EMAIL_ADDRESS>wrote:

Also experiencing this. Cookbook runs fine when using test kitchen but
when using vagrant & chef_zero provisioner I get the same error.
—
Reply to this email directly or view it on GitHub
https://github.com/chef-cookbooks/docker/issues/621#issuecomment-178705821
.

Anything we can do to help diagnose?

It seems like it has to do with the scope of the methods and how they are being brought into the class using include, and not extend. Pull request #622 is my fix for it. The mystery is why it works in some places (TestKitchen) and not others. In fact, I'm pretty sure it was working with chef zero at one point, or maybe even intermittently working.
Is this a language-level difference? Does TestKitchen use an older or newer version of ruby?

Upgrading to compat_resource 12.7.1 seems to have fixed this in travis.
Why Vagrant was failing remains a mystery. Closing for now.
-s

The update to compat_resource fixes it for me. I'll close the pull request.

Fixed for me also. Thanks.

For those who don't know how to upgrade compat_resources alone like me.  You can change your docker cookbook to 2.4.24 or later, and do berks update docker will update docker along with compat_resources 12.7.1.  I  had using docker 2.4.10 that was working two weeks ago.


[Level Up - Advanced 5th Edition] Bug fixes

Fixed all the Passive Checks to be 10+modifiers+stat modifier and not +stat
Fixed issue where the Skill speciality couldn't be edited on the main screen, it can now be edited on both main screen and popup

Submission Checklist
Required

[Yes] The pull request title clearly contains the name of the sheet I am editing.
[Yes] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[Yes] The pull request makes changes to files in only one sub-folder.
[Yes] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Fixed all the Passive Checks to be 10+modifiers+stat modifier and not +stat
Fixed issue where the Skill speciality couldn't be edited on the main screen, it can now be edited on both main screen and popup

Character Sheet Info Roll20 Internal Use only.


ant: add violating nets/pins to metrics

@ravi-varadarajan if the naming is not consistent, let me know and I'll correct them


Migrate to ofetch

🧿 Current issues / What's wrong ?
Current fetch request does not support timeout, nor keep alive connections.
💊 Fixes / Solution
Migrate the fetch library from cross-fetch to ofetch.
The error handling changes from ofetch will also introduce a change in returned response on error.
Previously, error handling looks like:
try {
  const body = await getScores(x);
  if (body.error) { // Handle error from score-api };
  return body.result;
} catch(e) {
  // do something with e, which is an Error object, for network error, or JSON parse error
}

With ofetch changes,
try {
  const body = await getScores(x);
  return body.result;
} catch(e) {
  // do something with e, which is an JSON-RPC object
  if (typeof e.code === 'string') {
    // Error from score-api
  } else {
    // Network error
  }
}

🚧 Changes

Add support for keep alive connections
Add timeout to all fetch requests
All non-200 status code throw an error
All errors thrown follow the same format as the underlying service error, beside getJSON and ipfsGet (see below)

getScores, validate and getVp

SUCCESS: The promise will resolve with the score JSON object
ERROR (from score-api): Promise rejection with JSON-RPC object (code === string)
ERROR (network): Promise rejection with JSON-RPC object (code === number)

The last argument (options) accepts a timeout property.
subgrapherRequest and getSnapshot

SUCCESS: return the JSON object
ERROR (subgrapher): return a JSON graphQL error object
ERROR (network): return a GraphQL like error object
ERROR (not json response): return a GraphQL like error object

The last argument (options) accepts a timeout property.
getJSON and ipfsGet

SUCCESS: return the JSON object
ERROR (network): throw a FetchError
ERROR (not json response): throw an JSON parse error

The last argument (options) accepts a timeout property.
send (from Client)

SUCCESS: return the JSON object
ERROR (from sequencer): Promise rejection with JSON-RPC object
ERROR (network): throw FetchError

‼ Breaking changes

ofetch is handling error response differently, and is rejecting a Promise on all non-200 errors.

This new update will require a bump to the next major version (1.x.x).
As this new breaking change need more testing before public release, the new 1.x.x should be released as a beta, and used only by our internal services first (and keep updated with the main branch) for a few weeks.
Once everything confirmed as working as expected, then we can public release it.
🛠 Tests

Call the getScores, validate, getSnapshot and getVp functions with valid data
It should return the expected object
Call them again with invalid data
It should return a JSON-RPC error object, from score-api
Call them again with invalid url (pass something else as score-api url)
It should return JSON-RPC error object

Fixed the fetch request from Client, please review again, as it's a core function

@Todmy Can you test this PR, utACK is not enough

@wa0x6e could you please test your tests? I run them and have some failed

a lot of them related to the https://httpstat.us/200?sleep=5000 but there are other errors

@wa0x6e could you please test your tests? I run them and have some failed  a lot of them related to the https://httpstat.us/200?sleep=5000 but there are other errors

Tests are passing on my local, and on github actions 🤔
What are the errors you're seeing ?

Added retry to flaky tests depending on third party services

issue persists. The reason why tests fail on my local host is that I use node@18. This package is used for projects with node@18 as well.

Hmmmm… have to start adding node 18 to ci

Hmmmm… have to start adding node 18 to ci

https://github.com/snapshot-labs/snapshot.js/pull/911

issue persists. The reason why tests fail on my local host is that I use node@18. This package is used for projects with node@18 as well.

Tests fixed for node 18

I believe this should not be merged on master, but on a dedicated v1 branch. We could then npm publish the beta from that branch

Maybe we can leave it on this branch, can i publish it to beta tag?

Maybe we can leave it on this branch, can i publish it to beta tag?

I don’t think it’s possible to have 2 versions on the same branch, it’ll create a merge conflict

Published this branch to<EMAIL_ADDRESS>


split install requirement packages  to install and test.

I just tried to generate a rpm package from this repo by fpm . It shows that there are some conflicts between rmtest and redisearch-py.
rpm -qlp python-redisearch-0.7.1-1.noarch.rpm
/usr/lib/python2.7/site-packages/redisearch-0.7.1-py2.7.egg-info/PKG-INFO
/usr/lib/python2.7/site-packages/redisearch-0.7.1-py2.7.egg-info/SOURCES.txt
/usr/lib/python2.7/site-packages/redisearch-0.7.1-py2.7.egg-info/dependency_links.txt
/usr/lib/python2.7/site-packages/redisearch-0.7.1-py2.7.egg-info/requires.txt
/usr/lib/python2.7/site-packages/redisearch-0.7.1-py2.7.egg-info/top_level.txt
/usr/lib/python2.7/site-packages/redisearch/__init__.py
/usr/lib/python2.7/site-packages/redisearch/_util.py
/usr/lib/python2.7/site-packages/redisearch/auto_complete.py
/usr/lib/python2.7/site-packages/redisearch/client.py
/usr/lib/python2.7/site-packages/redisearch/document.py
/usr/lib/python2.7/site-packages/redisearch/query.py
/usr/lib/python2.7/site-packages/redisearch/result.py
/usr/lib/python2.7/site-packages/rmtest/__init__.py
/usr/lib/python2.7/site-packages/rmtest/cluster.py
/usr/lib/python2.7/site-packages/rmtest/disposableredis/__init__.py
/usr/lib/python2.7/site-packages/rmtest/disposableredis/cluster.py

Delete rmtest from install_requires can fix this issue.

@v1c77 please notice the change made to setup.py

The file structure has changed


Improve code quality 2

This PR completes the modernization of the library with no functional changes.
Notable:

Drops NET47 & NET48 targets. The .NET46 target covers these platforms.
Enables C# 8 and updates codebase to utilize expressions
Simplifies switch statements (using expressions)
Simplify get and set statements (using expressions)
Updates static readonly strings to const
Simplify nullable assignment patterns

@lovettchris Ready for review.

ha this is great, is it complete though?

Hi @lovettchris. I just took a handful of passes over the codebase and tidied the obvious things up (being careful not to change any behaviors). It's pretty comprehensive.


Download proxied artifacts on notification

Expected results:

Receive artifact upload notifications via the dedicated webservice call (#3).
Guess an appropriate proxy repository (if any) for the artifact and its target repository (from the notification).
Get the artifact to the proxy repository from its source (asynchronously).

No / many proxy repositories for an artifact are acceptable cases.

This particular issue does not assume handling of notification transmission errors. Retries, work around sending and receiving servers restarts are in scope of #12.

Done in scope of PR #9, #13.


Use range to determine flamingo battery

Based of 100% being 38km

Looks good - I'll merge it now. Thanks for the contribution - I really appreciate it. 🙂


Twitter preprocessing script

I wanted to use the Twitter preprocessing script in https://nlp.stanford.edu/projects/glove/preprocess-twitter.rb and found a few bugs there:

URLS without http are not found
Last gsub splits words with caps where it should not and adds the  word where it should not.

I think the script has not been tested, and probably is nto the one that was used to train the model, as discussed here https://groups.google.com/forum/#!searchin/globalvectors/preprocessing|sort:date/globalvectors/_X7hQBBuoLY/2ysMo1sWCQAJ
It's my first touch with Ruby but I've fixed those two bugs:
`
def tokenize input
# Different regex parts for smiley faces
eyes = "[8:=;]"
nose = "['`\-]?"

input = input
	.gsub(/https?:\/\/\S+\b|www\.(\w+\.)+\S*/,"<URL>")
	.gsub(/www\.(\w+\.)+\S*/,"<URL>") # gombru: handle URLS without http
	.gsub("/"," / ") # Force splitting words appended with slashes (once we tokenized the URLs, of course)
	.gsub(/@\w+/, "<USER>")
	.gsub(/#{eyes}#{nose}[)d]+|[)d]+#{nose}#{eyes}/i, "<SMILE>")
	.gsub(/#{eyes}#{nose}p+/i, "<LOLFACE>")
	.gsub(/#{eyes}#{nose}\(+|\)+#{nose}#{eyes}/, "<SADFACE>")
	.gsub(/#{eyes}#{nose}[\/|l*]/, "<NEUTRALFACE>")
	.gsub(/<3/,"<HEART>")
	.gsub(/[-+]?[.\d]*[\d]+[:,.\d]*/, "<NUMBER>")
	.gsub(/#\S+/){ |hashtag| # Split hashtags on uppercase letters
		# TODO: also split hashtags with lowercase letters (requires more work to detect splits...)

		hashtag_body = hashtag[1..-1]
		if hashtag_body.upcase == hashtag_body
			result = "<HASHTAG> #{hashtag_body} <ALLCAPS>"
		else
			result = (["<HASHTAG>"] + hashtag_body.split(/(?=[A-Z])/)).join(" ")
		end
		result
	}
	.gsub(/([!?.]){2,}/){ # Mark punctuation repetitions (eg. "!!!" => "! <REPEAT>")
		"#{$~[1]} <REPEAT>"
	}
	.gsub(/\b(\S*?)(.)\2{2,}\b/){ # Mark elongated words (eg. "wayyyy" => "way <ELONG>")
		# TODO: determine if the end letter should be repeated once or twice (use lexicon/dict)
		$~[1] + $~[2] + " <ELONG>"
	}
	.gsub(/([^a-z0-9()<>'`\-]){1,}/){ |word|
		"#{word.downcase}" # gombru: Fixed bug, Downcasing all
	}

return input

end
puts tokenize($_)
`

Hi, I know I arrive a bit late to this post, but just in case anyone might be interesting in collecting new tweets and clean them, I can share with you this python code. The cleaning code is in a jupyter notebook because I wanted to show and test each step visually. Hope you find it useful :)
https://github.com/cyberosa/read_tweets_python


Control monster animation repeats

User Story
As a UX designer,
I want to allow character animations and any associated sounds to be controlled programmatically for how many times they repeat,
So that we can repeat animations for better readability or emphasis.

Per #846 , we may just want to find an animation library we can use that helps sync animations and audio.


Add methods to access enum constants

Resolves #253
Resolves #254

I added this as a draft to run CI with various compilers. All runs pass, so all tested compilers store the fields in bytecode in declaration order.


[KeyVault Admin] Rollup warning for re-exporting KeyVaultClientContext

Rollup gives the below warning in the KeyVault Admin package
dist-esm/src/index.js → dist/index.js...
(!) Conflicting re-exports
dist-esm/src/index.js re-exports 'KeyVaultClientContext' from both dist-esm/src/generated/keyVaultClient.js and dist-esm/src/generated/keyVaultClientContext.js (will be ignored)
created dist/index.js in 154ms

The current keyvault-admin client doesn't have this rollup warning 🌞
At least I can't find anything here, or see anything locally when I run rush build.
I'll close this for now.


All games crash...?

After the last update... all the games I've tried (listed as playable) just don't run.
error C2-12828-1
yoyo loader version: [107e887]

Me too


Tests enhancement

PR Checklist

[x] Please add a description of your changes.
[x] We need your changes to come with unit tests in order to keep this project in quality and easy to maintain.
[x] Please add a link to the open issue or task that this pull request will resolve.
[x] Add a note to the changelog to indicate the change.

Does this PR introduce a breaking change?

[x] Yes
[ ] No

If yes please indicate it and migration info into the CHANGELOG.md file.

This DRAFT PR contains the removal of two methods that we kept just for backward compatibility.
Enhancements of unit tests that should be now more fast and reliable.
Nyc configuration for minimum coverage on lines/branches and so on.
I will add into this PR some sonar code smells fixes

@pioardi I observed that your merges, that you are doing into the master, are not real squash-merges!?
Are you using the GitHub UI button?
Also I wrote in gitter to you that I created a board for version 2.1
Could you move your both "note"-cards in the "idea" column to the v2.1 board?
I think you need to recreate the notes, because there is no move to other board :thinking:

@pioardi I observed that your merges, that you are doing into the master, are not real squash-merges!?
Are you using the GitHub UI button?
Also I wrote in gitter to you that I created a board for version 2.1
Could you move your both "note"-cards in the "idea" column to the v2.1 board?
I think you need to recreate the notes, because there is no move to other board 🤔

Yes I read that about 2.1 project but I forgot to answer you ( sorry tfor that ), but I would keep only one project with version 2.x.x instead of already plan 2.1 version before to even release the 2.0.0.
For squash merges yes I am using the button but without the squash ( even if I love it ) , but I only use squash when I need something to revert easily later. I know you love clean things so I will try to use regularly ( if you prefer also add it to the contributing.md or PR templates )

@jerome-benoit  @Shinigami92  I think we are ready to go, I will hold on for some hours if you want to catch anything else


cddl_gen.py: Allow default_maxq to be set via command line

Fixes #12

cc @utzig @hakonfam @jeremyherbert

I don't have any review comments to add, just some suggestions overall:

Add the actual default_maxq value used for generation in a comment at the top of the generated file
Add to the readme that the parameter changes the behaviour of the "+" operator
related to above, how does this work if I generate an encode with default_maxq of 5 and a decode of default_maxq of 3?

@hakonfam @jeremyherbert Sorry for the delay. Your comments should be addressed now.


Syncing the project does not create a python folder

After following the tutorial at https://pub.dev/packages/chaquopy I can't get the app to create a python folder after syncing.  I have created one myself and added the python script to it, but the example does not recognize the script and receives this error on the emulator screen: "This shows Output or Error: ModuleNotFoundError: No module named 'script'"

It should create python folder, otherwise it'll be considered build failure. I would recommend trying to resolve the configuration issues first.


Recommended memory for jaeger-spark-dependencies (elasticsearch)

I'm getting the following exception when the jaeger-spark-dependencies job runs:
$ kubectl logs jaeger-spark-dependencies-1572911700-2pf7x

19/11/04 23:55:20 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
19/11/04 23:55:21 ERROR SparkContext: Error initializing SparkContext.
java.lang.IllegalArgumentException: System memory 101384192 must be at least 471859200. Please increase heap size using the --driver-memory option or spark.driver.memory in Spark configuration.
	at org.apache.spark.memory.UnifiedMemoryManager$.getMaxMemory(UnifiedMemoryManager.scala:217)
	at org.apache.spark.memory.UnifiedMemoryManager$.apply(UnifiedMemoryManager.scala:199)
	at org.apache.spark.SparkEnv$.create(SparkEnv.scala:330)
...

I have two questions:

What are the recommended memory requests/limits?
What happens if you don't enable this job?

Same problem here, any recommendation ?

What happens if you don't enable this job?

Then you will not see dependencies on the dependencies tab. https://www.jaegertracing.io/docs/1.14/deployment/#aggregation-jobs-for-service-dependencies

What are the recommended memory requests/limits?

Have you specified resources in your jaeger CR, or are you using the default?

Here is my config:
apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: jaeger-staging
  namespace: staging
spec:
  strategy: streaming
  ingress:
    enabled: false
  collector:
    replicas: 2
    options:
      kafka:
        producer:
          topic: staging-jaeger-spans
          brokers: broker:9092
  ingester:
    replicas: 2
    options:
      kafka:
        consumer:
          topic: staging-jaeger-spans
          brokers: broker:9092
      ingester:
        deadlockInterval: 0
  query:
    replicas: 2
  storage:
    type: elasticsearch
    options:
      es-provision: false
      es:
        server-urls: elastic_url
        index-prefix: staging
      esIndexCleaner:
        enabled: false # turn the job deployment on and off
        numberOfDays: 30 # number of days to wait before deleting a record
        schedule: "55 23 * * *" # cron expression for it to run
        image: jaegertracing/jaeger-es-index-cleaner # image of the job
    dependencies:
      enabled: true
      elasticsearchNodesWanOnly: true
  resources:
    requests:
      memory: "64Mi"
      cpu: "100m"
    limits:
      memory: "2048Mi"
      cpu: "512m"

With this config it's still failing:
19/11/05 23:56:34 ERROR SparkContext: Error initializing SparkContext.
java.lang.IllegalArgumentException: System memory 129761280 must be at least 471859200. Please increase heap size using the --driver-memory option or spark.driver.memory in Spark configuration.
	at org.apache.spark.memory.UnifiedMemoryManager$.getMaxMemory(UnifiedMemoryManager.scala:217)
	at org.apache.spark.memory.UnifiedMemoryManager$.apply(UnifiedMemoryManager.scala:199)
	at org.apache.spark.SparkEnv$.create(SparkEnv.scala:330)
	at org.apache.spark.SparkEnv$.createDriverEnv(SparkEnv.scala:175)
	at org.apache.spark.SparkContext.createSparkEnv(SparkContext.scala:256)
	at org.apache.spark.SparkContext.<init>(SparkContext.scala:423)
	at org.apache.spark.api.java.JavaSparkContext.<init>(JavaSparkContext.scala:58)
	at io.jaegertracing.spark.dependencies.elastic.ElasticsearchDependenciesJob.run(ElasticsearchDependenciesJob.java:216)
	at io.jaegertracing.spark.dependencies.elastic.ElasticsearchDependenciesJob.run(ElasticsearchDependenciesJob.java:203)
	at io.jaegertracing.spark.dependencies.DependenciesSparkJob.run(DependenciesSparkJob.java:54)
	at io.jaegertracing.spark.dependencies.DependenciesSparkJob.main(DependenciesSparkJob.java:40)

Looks like Spark requires at least 4GB. @kevinearls do we have any tests using Spark?

@jpkrohling  There's this one: https://github.com/jaegertracing/jaeger-operator/blob/master/test/e2e/spark_dependencies_test.go  It's called both here: https://github.com/jaegertracing/jaeger-operator/blob/e7c48398df2f7363f97896936c26c7ea93062a65/test/e2e/elasticsearch_test.go#L69-L78 and here https://github.com/jaegertracing/jaeger-operator/blob/e7c48398df2f7363f97896936c26c7ea93062a65/test/e2e/cassandra_test.go#L75-L83

Looks like I can't reproduce this. Here's what I did:
CR:
apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: simple-prod
spec:
  strategy: production
  storage:
    type: elasticsearch
    options:
      es:
        # Note: This assumes elasticsearch is running in the "default" namespace.
        server-urls: http://elasticsearch.default.svc:9200
        index-prefix: staging
      esIndexCleaner:
        enabled: false # turn the job deployment on and off
        numberOfDays: 30 # number of days to wait before deleting a record
        schedule: "55 23 * * *" # cron expression for it to run
        image: jaegertracing/jaeger-es-index-cleaner # image of the job
    dependencies:
      enabled: true
      elasticsearchNodesWanOnly: true
  resources:
    requests:
      memory: "64Mi"
      cpu: "100m"
    limits:
      memory: "2048Mi"
      cpu: "512m"

Once that gets stable, create a job from the cronjob:
$ kubectl create job --from=cronjob/simple-prod-spark-dependencies simple-prod-spark-dependencies-001
job.batch/simple-prod-spark-dependencies-001 created

It eventually completes and there's nothing wrong in the logs:
$ kubectl get pods
NAME                                       READY   STATUS              RESTARTS   AGE
elasticsearch-0                            1/1     Running             0          3m51s
simple-prod-collector-87cdbd564-tmdx7      1/1     Running             0          110s
simple-prod-query-5b5698c686-tzrg8         2/2     Running             0          110s
simple-prod-spark-dependencies-001-tt6g7   0/1     ContainerCreating   0          12s
$ kubectl logs simple-prod-spark-dependencies-001-tt6g7
19/11/13 15:13:01 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
19/11/13 15:13:07 INFO ElasticsearchDependenciesJob: Running Dependencies job for 2019-11-13T00:00Z, reading from staging-jaeger-span-2019-11-13 index, result storing to staging-jaeger-dependencies-2019-11-13
19/11/13 15:13:12 INFO ElasticsearchDependenciesJob: Done, 0 dependency objects created
19/11/13 15:13:12 INFO ElasticsearchDependenciesJob: Running Dependencies job for 2019-11-13T00:00Z, reading from staging:jaeger-span-2019-11-13 index, result storing to staging:jaeger-dependencies-2019-11-13
19/11/13 15:13:14 INFO ElasticsearchDependenciesJob: Done, 0 dependency objects created
$ kubectl get jobs
NAME                                 COMPLETIONS   DURATION   AGE
simple-prod-spark-dependencies-001   1/1           41s        93s

I'm running it all in minikube, set like this:
$ minikube start --vm-driver kvm2 --cpus 6 --memory 12288

The operator is running as make run, and ES is set with make es.

shell:
docker run --rm -it -e STORAGE=elasticsearch -e JAVA_OPTS="-Xms30g -Xmx30g" -e ES_CLIENT_NODE_ONLY=false -e ES_NODES_WAN_ONLY=false -e ES_NODES=<IP_ADDRESS> jaegertracing/spark-dependencies

jaeger-span Index size: 36.6gb
green open jaeger-span-2019-11-20    lAAp46SpTeaUVmI5A6047g 5 1  650309235       0    76gb  36.6gb

jaeger-dependencies RSS memory size: 31.2g
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
22109 185       20   0   32.7g  31.2g   4212 S  2292 49.8 155:16.87 java

Frequently running failure. any recommendation ?

Heads up: if the resources in Jaeger CR are specified at the root level it will be applied to spark job. However spark job requires at least 4Gi so be careful and override the resources in the dependencies spec.
It's going to be documented here: https://github.com/jaegertracing/documentation/pull/355


Scala 2.13 support

It would be nice to see this published for Scala 2.13. :)

It will be as soon as #67 and #71 get merged. ETA end of this week.

Is there any update on the ETA?

@heksesang please see #79

Fixed in #79


More robust path replacement to account for proxy & httpNodeRoot configs

Description

Ensure we have a more robust SocketIO path replacement, which was introduced in #595 (for #526) and had broken the work we'd done in #581 (a fix for #437)

Related Issue(s)
Fixes #563

Looks ok, but you have a test failure. I'll trigger a re-run in case it's a timing thing

Yeah, it's a very unreliable E2E test set, Cypress doesn't like Websockets... Always run fine when local

@joepavitt I'll let you decide to merge then


Uptdate mqtt bridge docs && blogs.

@LenaLenaPan plz have a look

leave some comments

Thanks for your advice. Based on your suggestion, I have made some changes.


Skipping invalid environments in the manifest, allowing reusable config

fixes #446
Currently themekit checks all environments strictly for version checking however this does not allow for reusable config like this:
production: # LIVE WEBSITE
  theme_id: ********
  readonly: true # safety switch; toggle to deploy
  << : *common
config: &common
  password: *********************
  store: storename.myshopify.com
  ignore_files:
    - src/
    - node_modules/
    - Gulpfile.js
    - package.json

Because the config environment would be invalid. I don't love this because if some of the environments are invalid I won't be able to backfill the manifest with versions. However when upload/replacing on different environments, the backfills aren't really necessary. I was just being greedy with that information.

@tanema I'm still getting the same error on v0.7.2.
Invalid configuration: missing theme_id,missing store domain,missing password All environments are required to be valid so that asset
 versions can be validated

Yes because this change was made after 7.2 and it will be in the next release.

On Aug 24, 2017, at 6:50 PM, Tineyi<EMAIL_ADDRESS>wrote:
@tanema I'm still getting the same error on v0.7.2.
Invalid configuration: missing theme_id,missing store domain,missing password All environments are required to be valid so that asset
versions can be validated
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@tanema Ah, right. Thank you!


Move test related in one test folder

This change moves all test related files in the /test folder.
__tests__ is pattern from Jest I think and it looks a bit ugly. Might be my OCD kicking in 😅

I also don't feel strongly at all one way or another.


DocsArchive-<IP_ADDRESS>Auto archive content

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

Docs Build status updates of commit 392e217:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


fix: removes old sdk object references

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


How to setup the plugin?

I've tried to open intellij-purescript.github.io but got 404. I've installed the plugin and added purescript language server to node_modules. Well, it didn't help me. The plugin only does syntax highlighting, nothing more. What should I do else to make it work completely?

@GulinSS the language server stuff is not very well functioning afaic. I'm running on Ubuntu, and it basically didn't work at all some weeks ago. @Neppord is there some documentation on what to expect w.r.t language server?
What I know should work cross platform:

syntax highlighting
navigate locally (within file) between variables/definitions and types

@objarni there is a description in the marketplace that covers what should work as a minimum, since its not always updated.

This issue was solved over a slack thread, the problem was that the .spago directory was excluded, so the plugin did not look in it to find references and documentation.


Check whether the task finishes before deferring the task for DataprocDeleteClusterOperatorAsync

Like the SnowflakeOperatorAsync, we try to verify if the submitted job has already completed before deferring it to prevent unnecessary deferring. This way, we can skip deferring the task if it has already been finished.


unable to parse ReactJS contextTypes using Standard + babel-eslint in SublimeText 3 (SublimeLinter)

I am using this React Native sample code as a template to add tabbed navigation to a React Native mobile app:
https://github.com/facebook/react-native/blob/master/Examples/UIExplorer/js/NavigationExperimental/NavigationCardStack-NavigationHeader-Tabs-example.js
In my project, the following code can't be parsed:
function createAppNavigationContainer (ComponentClass) {
  const key = '_containerNavigateCall'

  class Container extends Component {

    // commenting out the two contextTypes declarations below returns normal behavior
    static contextTypes = { // unable to parse this => 'unexpected token'
      [key]: PropTypes.func
    }; // dropping the semi here also results in a parsing error

    static childContextTypes = { // same issue here
      [key]: PropTypes.func.isRequired
    };

    getChildContext () {
      return {
        [key]:
          this.context[key] ||
          this.props.navigate
      }
    }

    render () {
      const navigate =
        this.context[key] ||
        this.props.navigate

      return <ComponentClass
        {...this.props}
        navigate={navigate}
      />
    }

  }

  return Container
}

In my SublimeLinter settings I have:
"linters": {
  "standard": {
      "@disable": false,
      "args": [],
      "excludes": [],
      "parser": "babel-eslint",
      "plugins": [
          "react"
      ]
  }
},

All npm packages are installed globally:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>I have installed SublimeLinter-contrib-standard via ST3 package control, and I don't have any other linters.
EDIT: I should mention that the app performs as expected, without errors. Thanks in advance,
DP

The correct place to add the "parser": "babel-eslint" line is in the "standard" property of "package.json".
See the instructions here: http://standardjs.com/#can-i-use-a-custom-js-parser-for-bleeding-edge-es-next-support

Outstanding, thanks (for the answer and the linter)!


Grant query fails with exception: Access Entity has recently been changed in catalog

Bug Report
Briefly describe the bug
When I try to give additional grants to a role which is the default role of a user, I get the exact exception below:
Code: 8074, e.displayText() = DB::Exception: Access Entity has recently been changed in catalog. Please try the request again.: Couldn't update role `my_test_role`. Successfully updated: none SQLSTATE: HY000 (version <IP_ADDRESS>)

I tried the same grant query again and again, but all result in the same exception. I traced the exception source down to here: https://github.com/ByConity/ByConity/blob/741a755257ba465fa28015293c8b6ace6b8e3bee/src/Catalog/FDBClient.cpp#L293
...but I couldn't find any more details on why this issue may happen.
The whole stack trace is below:
0. Poco::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int) @ 0x1f2578d2 in /opt/byconity/bin/clickhouse
1. DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool) @ 0xd9c4ca0 in /opt/byconity/bin/clickhouse
2. DB::Catalog::MetastoreProxy::putAccessEntity(DB::IAccessEntity::Type, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, DB::Protos::DataModelAccessEntity const&, DB::Protos::DataModelAccessEntity const&, bool) const @ 0x18645410 in /opt/byconity/bin/clickhouse
3. void std::__1::__function::__policy_invoker<void ()>::__call_impl<std::__1::__function::__default_alloc_func<DB::Catalog::Catalog::putAccessEntity(DB::IAccessEntity::Type, DB::Protos::DataModelAccessEntity&, DB::Protos::DataModelAccessEntity&, bool)::$_185, void ()> >(std::__1::__function::__policy_storage const*) @ 0x185f2e75 in /opt/byconity/bin/clickhouse
4. DB::Catalog::Catalog::putAccessEntity(DB::IAccessEntity::Type, DB::Protos::DataModelAccessEntity&, DB::Protos::DataModelAccessEntity&, bool) @ 0x185bd442 in /opt/byconity/bin/clickhouse
5. DB::KVAccessStorage::updateNoLock(StrongTypedef<wide::integer<128ul, unsigned int>, DB::UUIDTag> const&, std::__1::function<std::__1::shared_ptr<DB::IAccessEntity const> (std::__1::shared_ptr<DB::IAccessEntity const> const&)> const&, std::__1::vector<std::__1::tuple<std::__1::function<void (StrongTypedef<wide::integer<128ul, unsigned int>, DB::UUIDTag> const&, std::__1::shared_ptr<DB::IAccessEntity const> const&)>, StrongTypedef<wide::integer<128ul, unsigned int>, DB::UUIDTag>, std::__1::shared_ptr<DB::IAccessEntity const> >, std::__1::allocator<std::__1::tuple<std::__1::function<void (StrongTypedef<wide::integer<128ul, unsigned int>, DB::UUIDTag> const&, std::__1::shared_ptr<DB::IAccessEntity const> const&)>, StrongTypedef<wide::integer<128ul, unsigned int>, DB::UUIDTag>, std::__1::shared_ptr<DB::IAccessEntity const> > > >&) @ 0x189cdebc in /opt/byconity/bin/clickhouse
6. DB::KVAccessStorage::updateImpl(StrongTypedef<wide::integer<128ul, unsigned int>, DB::UUIDTag> const&, std::__1::function<std::__1::shared_ptr<DB::IAccessEntity const> (std::__1::shared_ptr<DB::IAccessEntity const> const&)> const&) @ 0x189cd768 in /opt/byconity/bin/clickhouse
7. DB::MultipleAccessStorage::updateImpl(StrongTypedef<wide::integer<128ul, unsigned int>, DB::UUIDTag> const&, std::__1::function<std::__1::shared_ptr<DB::IAccessEntity const> (std::__1::shared_ptr<DB::IAccessEntity const> const&)> const&) @ 0x189e8cbe in /opt/byconity/bin/clickhouse
8. DB::IAccessStorage::update(std::__1::vector<StrongTypedef<wide::integer<128ul, unsigned int>, DB::UUIDTag>, std::__1::allocator<StrongTypedef<wide::integer<128ul, unsigned int>, DB::UUIDTag> > > const&, std::__1::function<std::__1::shared_ptr<DB::IAccessEntity const> (std::__1::shared_ptr<DB::IAccessEntity const> const&)> const&) @ 0x189c16e0 in /opt/byconity/bin/clickhouse
9. DB::InterpreterGrantQuery::execute() @ 0x19372370 in /opt/byconity/bin/clickhouse
10. DB::executeQueryImpl(char const*, char const*, std::__1::shared_ptr<DB::IAST>, std::__1::shared_ptr<DB::Context>, bool, DB::QueryProcessingStage::Enum, bool, DB::ReadBuffer*) @ 0x198008d3 in /opt/byconity/bin/clickhouse
11. DB::executeQuery(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::shared_ptr<DB::Context>, bool, DB::QueryProcessingStage::Enum, bool) @ 0x197fc281 in /opt/byconity/bin/clickhouse
12. DB::TCPHandler::runImpl() @ 0x1a3f3ede in /opt/byconity/bin/clickhouse
13. DB::TCPHandler::run() @ 0x1a40267c in /opt/byconity/bin/clickhouse
14. Poco::Net::TCPServerConnection::start() @ 0x1f1ccf8c in /opt/byconity/bin/clickhouse
15. Poco::Net::TCPServerDispatcher::run() @ 0x1f1cd46c in /opt/byconity/bin/clickhouse
16. Poco::PooledThread::run() @ 0x1f2b45fa in /opt/byconity/bin/clickhouse
17. Poco::ThreadImpl::runnableEntry(void*) @ 0x1f2b21ac in /opt/byconity/bin/clickhouse
18. start_thread @ 0x7ea7 in /lib/x86_64-linux-gnu/libpthread-2.31.so
19. __clone @ 0xfca2f in /lib/x86_64-linux-gnu/libc-2.31.so

The result you expected
I expected the new grants to be committed to FDB.
How to Reproduce
Not sure. This issue does not seem to be easily reproducible, I tried to reproduce by:

Creating a new role (let's say R1)
Giving that role some grants
Creating a new user with R1 as the default role
Giving R1 new grants

It sometimes work, sometimes fail after R1 has its 8th grant.
I am able to give more than 8 grants by specifying all grants in the same query.

Hi, the developer reports that the bug has been fixed. Can I check the version of ByConity you are using?

Hi, the developer reports that the bug has been fixed. Can I check the version of ByConity you are using?

Hey, we have lastly built from the master branch (commit https://github.com/ByConity/ByConity/commit/a08170c62735f80667a6affcad8c0422d8a9a50c to be precise) yesterday, today I tried the same grant queries on different roles and got the same exception.

Hi, the developer reports that the bug has been fixed. Can I check the version of ByConity you are using?

Hey, we have lastly built from the master branch (commit a08170c to be precise) yesterday, today I tried the same grant queries on different roles and got the same exception.

commit [5e34105] is the fix. Can you try include this commit?

We had another issue blocking us to try this fix. We will when the issue https://github.com/ByConity/ByConity/issues/969 is resolved

Just tried the fix on the commit @Clark0 mentioned and it worked, thanks all!


Don't overlay cancel over long search text, and set search text margin option.

Hi @arimorty,
I have 2 possible enhancements for the library.
I am using the search bar not in full-screen, as part of the width of the screen:
https://mrkr.io/43zNGZOcsM
(1) If the search text becomes too long, it sits behind the clear button. See here:
https://mrkr.io/cGYhEEvPcr
I think you could be fixed by adding the following:
android:layout_toStartOf="@+id/clear_btn"
android:layout_toLeftOf="@+id/clear_btn"

to the FrameLayout here:
https://github.com/arimorty/floatingsearchview/blob/master/library/src/main/res/layout/search_query_section.xml#L43
(2) I would love to be able to set the margin of the search text view so that it's centered in the view better. Basically setting these: https://github.com/arimorty/floatingsearchview/blob/master/library/src/main/res/layout/search_query_section.xml#L48-L49
Let me know what you think of the enhancements. If you wish, I will make a PR for these 2 and the other enhancement I recently reported.

The first enhancement was actually a bug that was fixed in the latest release (2.0.3) check your version and let me know if the problem is still there.
For the second enhancement, I understand that you need the text to be centered, but the purpose of this library is implement a material design search as specified in the Material Design specs. I might add an option for that in a future release, but for now you can still get a reference to the TextView programmatically and set the property that you want.

I have checked 2.0.3 and this is fixed for me.
And your solution to my second point works as well.
Thanks!


Accessibility Testing merge

@veler,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


The old collection not deleted after a sequence of two flushes

When you in full rewrite a collection for an entity, sometimes an old collection is not removed from the database.
Example
class Contact
{
    /**
     * @Id
     * @Column(type="integer")
     */
    public $id;

    /**
     * @Column(type="string")
     */
    public $name;

    /**
     * @ManyToMany(targetEntity="Source")
     */
    public $sources;
}

class Source
{
    /**
     * @Id
     * @Column(type="string")
     */
    public $id;
}

Origin entity

id
name
sources

1
name 1
cck

$contact->name = 'name 2';
$em->flush();

$sources = $contact->sources->toArray();
$contact->sources = new ArrayCollection($sources);
$em->flush();

After the first flush, the changes for the collection fields are no longer tracked and an error occurred during the second flush.
SQLSTATE[23505]: Unique violation: 7 ERROR:  duplicate key value violates unique constraint "gh6829contact_gh6829source_pkey"
DETAIL:  Key (gh6829contact_id, gh6829source_id)=(1, cck) already exists.

If you remove the first flush then it works fine.
$contact->name = 'name 2';
$sources = $contact->sources->toArray();
$contact->sources = new ArrayCollection($sources);
$em->flush();

This is by design as it is now, changing collection itself is not supported and must be kept as PersistentCollection assigned by UnitOfWork.


no documentation for creating layout monocle (or how do this behavior), need examples.

Hyprland Version
0.30
Bug or Regression?
Bug
Description
'inherit_fullscreen' in Master layout not worked. Or behavior is not correct (in Wiki docs).
I want expect monocle mode (fullscreen for this workspace or default behavior on all Hyprland).
inherit_fullscreen = true - nothing...
How to reproduce
just use default example conf and add this option in Master section.
Hypr, if I not wrong, inheritance behavior from Xmonad, DWM and another tiled WMs, so, I expect monocle mode...
P.S. Sorry for my terrible english.
Crash reports, logs, images, videos
No response

there is no documentation for monocle because there is no monocle.
What you can do is fullscreen a window and use focuswindow with l/r to cycle between windows


Error: read ECONNRESET

We have been getting an error that seems to be from the package (our console logs have consistently had this error when the imap-simple package was checking email).
2017-05-04 13:03:39-07:00 events.js:72
2017-05-04 13:03:39-07:00  throw er; // Unhandled 'error' event
2017-05-04 13:03:39-07:00  ^
2017-05-04 13:03:39-07:00 Error: read ECONNRESET
2017-05-04 13:03:39-07:00 at errnoException (net.js:905:11)
2017-05-04 13:03:39-07:00 at TCP.onread (net.js:559:19)

I'm not sure exactly what part of the call is causing this, it's a fairly standard call:
var config = {
    imap: {
        user: 'XXX',
        password: 'XXX',
        host: 'imap.gmail.com',
        port: 993,
        tls: true,
        authTimeout: 3000
    }
};

code:
imaps.connect(config).then(function (connection) {
        connection.openBox('INBOX').then(function () {

            var searchCriteria = [
                'UNSEEN'
            ];

            var fetchOptions = {
                bodies: ['HEADER', 'TEXT'],
                markSeen: true
            };

            connection.search(searchCriteria, fetchOptions).then(function (results) {

After that is just parsing, but it seems the error is happening in the connection call according to the error.
We basically have it continually checking email every couple minutes. Typically we get the error 1-2 times a day. Sometimes we do not get the error for a few days. Some days we have had 10+ times a day. It's a pretty major issue on those bad days, so I would like to get this resolved.
Any advice on how to track this down and/or fix it?

http://stackoverflow.com/a/17637900/355743


Why is _GenerateCompileDependencyCache using ReferencePath?

_GenerateCompileDependencyCache is ~using~ adding ReferencePath to the compile cache but I'm not sure why, what's the reason?
The reason I ask is that it's making the assumption that ReferencePath is always relative to the project directory (via FullPath metadata) - when that's not how it's treated by the compiler.

We want to add ReferencePath to the cache, so that if you alter it via some mechanism that doesn't involve changing the project file we still rebuild.
Team triage:
We should drop the FullPath part.

But why only ReferencePath in that? Isn't this any input into csc?

Yeah, this is a partial solution to the general problem that MSBuild doesn't keep track of the previous build's task inputs. It seemed that referenced assemblies and source files were most likely to be changed without changing the project.

Usage of full path was removed in https://github.com/Microsoft/msbuild/pull/2315.


Interface changes to the plotting and solver

Small changes to the interface of the plotting functions and the solver.
Would be helpful to the solver comparison code.

Plotting: adding save_path as an argument instead of having it hard-coded.
Some of the plotting functions already do it, this change makes it consistent
Exp_grad_solver: Adding a callback function to the optimizer to gather info about the progres.
Makes the interface consistent across optimizers (such as scipy minimize).

Thanks.  I've been very happy with Black on other projects.


Write process for managing Google credentials

This should include:

auditing who was credentials
generating new credentials
retiring old credentials

Roles
A simple list of roles and permissions:

Owner (this is built in)
Team Member

bigquery.*
storage.*

Guest

bigquery.datasets.get
bigquery.savedqueries.*

Pipeline Runner

bigquery.*
storage.*

Project Billing Manager (built in)

The .* permissions could be refined, but doing so will be a bit tedious.
Role membership
We should then assign users to roles:

Owner

The developers
We should consider creating a separate "Developer" role when the team grows, but I'm not sure what it wouldn't have that Owner does -- maybe some of the billing stuff and the user admin stuff

Team Member

Members of the DataLab team
They'll be able to muck things up by deleting datasets etc, but they've not done so so far
Limiting their access will probably cause unnecessary frustration
We could add restrictions at the dataset level, eg to prevent deletion of important datasets
Let's revisit this

Guest

People who we want to give read-only access to the data

Pipeline Runner

Service accounts for running pipeline and CI tests (see below)

Project Billing Manager

University administrators who pay the bills

We should have a regular reminder to audit membership of roles.
Service accounts

We've been using service accounts to:

Access GCS from the server (including for the pipeline)
Access GCS for CI
Access GCS for local development

We've been using a single service account for all of the above
We don't need service accounts for local development and can instead use our own user accounts with OAuth (see incoming PR)
We should have separate service accounts for each server and for CI, and should have a regular reminder to rotate keys for service accounts

This looks good!  Thanks for doing the thinking about it!
We should maintain this as a markdown document in the source. The regular reminder could potentially use the GCS API to list current roles and members, and also point to the markdown document?  (If GCS API is too faffy, then we could just manually list them and remind us to update that document periodically)

I've created the Pipeline Runner role in both ebmdatalab and ebmdatalabtest, and have moved the one service account we currently have into this role in ebmdatalabtest.
Let's wait for the tests to fail...

Well the tests didn't fail, and old datasets are being deleted again.  (I opened this issue after clean_up_bq_test_data suddenly started failing because it couldn't delete datasets.  (Sentry.))
Moving off my Now queue for the time being.

Things to do:

[ ] Create separate service account for each of:

[ ] Travis
[ ] End-to-end tests
[ ] Pipeline

[ ] Work out how to set up OAuth for humans
[ ] Enforce using datalab.org accounts for humans
[ ] Remove all old service account from IAM settings
[ ] Assign correct roles to humans
[ ] Look into key rotation for service accounts

@inglesp is this still current, and should it be moved from OP issues to Bennett issues?


The backup script fails on 6.0

$ docker run --rm webhippie/mongodb:6.0
$ docker exec container_name backup
/usr/bin/backup: line 27: mongo: command not found

This worked fine on 5.0.
Just replacing mongo with mongosh in the backup script seems to work (in the place where uses it to query list of databases, mongodump works normally). There are a bunch more occurrences in the healthcheck and container (for setting passwords) scripts, so I presume more things may be broken.

Thanks for the report, took me some days to find the time for debugging. The new image should be pushed soonish which includes a fix.


Group impl support

Implements a generic holy the Group for both PublicKey and PrivateKey
Group::Scalar now requires Copy
Group::scalar_as_bytes now takes and returns a value instead of a reference
expose map_to_curve::expand_message_xmd

There are quiet a bit of breaking changes, I didn't expect me doing this now, but it turned out that P256 is more important then we thought for our needs. I'm open to any suggestions.
Fixes #198.

Clippy is currently broken because of https://github.com/rust-lang/rust-clippy/issues/7422.


className + slot selector does not work when hash is true

Description
I have a slot recipe where I am using new className + slot name selector syntax introduced in 0.35. It works perfect but when i turn on the hash option, everything gets hashed and these selectors don't work any more (It seems to working in sva but not in config recipe).
Link to Reproduction
https://play.panda-css.com/YFHxeOc924
JS Framework
React (TS)
Panda CSS Version
0.35.0
Browser
Brave 122
Operating System

[ ] macOS
[ ] Windows
[X] Linux

Additional Information
No response

we'd rather not introduce more custom syntax that we already have, it would require one to be able to select a slot when using hash: true
https://github.com/chakra-ui/panda/issues/2369#issuecomment-1992227993

@haseeb5i You can achieve this with data-part selectors instead.
Add a data part to the element to be targeted e.g data-part="item" then use this in style. E.g.
parent:{
    '& [data-part="item"]': {
       //styles
    }
}

sibling:{
    '& ~ [data-part="item"]': {
       //styles
    }
}


Insert data lost during test

Hello:
Thank you so much for your patience and help last time. I'm sorry to bother you again.
After successfully compiling and running your program, I tried to test the stability of the program by having it insert one piece of data per second for a total of 10,000 pieces of data. I found that the last results obtained, there is a problem of insertion results lost.
A total of 10001 pieces of data were inserted.

It appears that 5 bars are missing.

The missing items are 1668, 3390, 5111, 6833, 8554.
The source files are as follows.
result.csv
I've noticed that it seems that the program doesn't return an error even if it didn't write correctly, is there a way to check that the return insertion was successful and re-insert if it failed.
Incidentally, is there any other recommended method for recording production data from a PLC.
Thank you very much!

A state machine can be written to read if the data exists immediately after another write, otherwise repeated writes can solve this problem. If you need a case study you can ask me for a case study.


JavaScript driver on live docs

On Drivers & Clients page, the current live state doesn't reflect the current master version. To the outside world, JavaScript driver doesn't exist.

The default is for the BigchainDB Server docs to show the "latest" version which is always the same as the most recently-released numbered version (not the master branch).
Power-users, who want to read the docs from the master branch can do so: they just go to the version selector in the lower left corner of the docs.
Once we release BigchainDB Server version 1.0.0, the JavaScript driver (and the Ruby driver) will be listed on the default/latest Drivers & Clients page.
I see two options:

Close this issue as a non-issue, or
Always show the master branch docs by default (instead of the latest numbered release).

I prefer option 1 because I want the default docs to serve normal users (i.e. users of the latest numbered release), not power-users.

Always show the master branch docs by default (instead of the latest numbered release).

Not an option. master can contain breaking changes.

Close this issue as a non-issue, or

An option I'd consider
3. Option

we release a new patch version of BDB that includes the link to the js driver in the docs

Fully agreed.
@kremalicious, when I did the drivers page in the docs I actually wanted to aim for something like:
https://docs.mongodb.com/ecosystem/drivers/
In my opinion, our drivers deserve their own page on our website anyways.
Hence, my proposal:

remove https://docs.bigchaindb.com/projects/server/en/latest/drivers-clients/index.html from docs
create "Drivers" page under bigchaindb.com
from docs, link to bigchaindb.com/drivers

at least Drivers page is in progress here https://trello.com/c/Or2ViAEF/38-get-started-page
Think this shows the bigger problem: our documentation is completely project-based which is not scalable. Drivers & Clients page is one thing, documenting the drivers another thing, where we have already an overlap between python driver and javascript driver.
With our current docs strategy: the Drivers & Clients page should be a somewhat global page, linked to from the start page: https://docs.bigchaindb.com/en/latest/index.html But guess this page is based on current server release version too?

I like the idea of removing the Clients & Drivers page from the BigchainDB Server docs, and moving its contents elsewhere, preferably somewhere that can be updated (in its default view) whenever we like (not just when there's a new version of BigchainDB Server).
I'm not really happy with the word "Clients" any more. For me, a "client" is something like an Android app which uses a driver internally. I'd just call it "Drivers and Tools" where a tool can be anything that falls short of being a full driver, such as a keypair generator.
We could create a patch release to update the links in the BigchainDB "root" docs (/docs/root) and the BigchainDB "server" docs (/docs/server), to point to the URL of the "Drivers and Tools" page.

For now, we leave the drivers page within the server docs. We are going to have a new Get started page at end of this week, including a section linking to our drivers/tools. But doesn’t hurt having this in both places for now, at least until we figure out a better place for our global docs.
Thanks @ttmc for the "Drivers and Tools" suggestion, less confusing and I'm already using this vocabulary on Get started page so would make sense changing this in the server docs part too?


Logging into Amplify Studio issues

Please describe which feature you have a question about?
No longer able to log into Amplify Studio, no users listed anymore, just spinner and never loads
Provide additional details
Hi, so my team and I have run into an issue when we tried to add a new team member. It wont let anyone launch studio even when logged in through AWS. and it won't show any users at all in the studio settings. Not sure how we can get this fixed.
What AWS Services are you utilizing?
Amplify
Provide additional details e.g. code snippets

Hi @MichaelDAbrams 👋🏽 thanks for raising this issue. I'm not seeing this behavior when I navigate to Amplify studio settings. Can you try again and see if the issue persists while we investigate?

hi @hloriana the issue is still occuring, still unable to add users and unable to log in

Hi @MichaelDAbrams we still aren't able to reproduce this on our end unfortunately so we will need some more information.

Are there any error logs that appear in the browser console? If so, please provide screenshots.
Please provide an HAR capture; it may be able to tell us why the information isn't loading.
We can hop on a call to further investigate this issue. Please reach out to<EMAIL_ADDRESS>with your availability and we will schedule a call.

For a workaround, you can try disabling and re-enabling Amplify studio. This won't affect your backend resources but it will remove any users you invited to access Amplify Studio.


Write a JavaScript program to find lcm of two numbers by recursion

Description
Write a JavaScript program to find lcm of two numbers by recursion
LCM (Least Common Multiple) of two numbers is the smallest number that can be divided by both numbers. For example, the LCM of 15 and 20 is 60 and LCM of 10 and 15 is 30.
Input  : 12 18
Output : 36

How to contribute

Save the solution in FindLcmOfTwoNumbersByRecursion.js file
Add FindLcmOfTwoNumbersByRecursion.js file in find-lcm-of-two-numbers-by-recursion folder

!assign


HDDS-4484. Use RaftServerImpl isLeader instead of periodic leader update logic in OM and isLeaderReady for read/write requests

What changes were proposed in this pull request?
Use RatisServer isLeader and isLeaderReady API from RaftServerImpl Class.
And also for reading requests, the check should be isLeaderReady before serving read requests.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4484
How was this patch tested?
Existing tests in TestOzoneManagerHA*.

Using direct RaftServerImpl API's for now until RATIS-1181 is completed.

Thank You @szetszwo for the review.


Value does not have datatype error with sh:datatype xsd:anyURI

Properties with sh:datatype xsd:anyURI always produce Value does not have datatype <http://www.w3.org/2001/XMLSchema#anyURI> error.
I created a minimal example for the https://shacl-playground.zazuko.com/ playground.
Shapes Graph:
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix g-validation:  <http://localhost:3001/shapes/validation#> .

@prefix g-framework: <http://localhost:3001/shapes/g-framework#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

g-validation:ServiceShape
	a sh:NodeShape ;
	sh:targetClass g-framework:Service ;
	sh:property [ sh:path g-framework:content ;
	                       sh:datatype xsd:anyURI ] ;
.

Data Graph:
{
    "@context": {
        "g-framework": "http://localhost:3001/shapes/g-framework#",
        "g-validation": "http://localhost:3001/shapes/validation#",
        "sh": "http://www.w3.org/ns/shacl#",
        "xsd": "http://www.w3.org/2001/XMLSchema#"
    },
  "@type": "g-framework:Service",
  "g-framework:content": "http://example.org/"

}

Thank you for reporting.
In your case, the error is in fact correct because the value is a plain literal. The validation sh:datatype is strict in that it requires a literal to have an exact matching datatype. Compare with other SHACL implementations, all of which yield same result.
If you need your JSON-LD to keep its idiomatic form, you can modify the @context to have it assert the values of the content property:
{
  "@context": {
    "g-framework": "http://localhost:3001/shapes/g-framework#",
    "g-validation": "http://localhost:3001/shapes/validation#",
    "sh": "http://www.w3.org/ns/shacl#",
-   "xsd": "http://www.w3.org/2001/XMLSchema#"
+   "xsd": "http://www.w3.org/2001/XMLSchema#",
+   "g-framework:content": {
+     "@type": "xsd:anyURI"
+   }
  },
  "@type": "g-framework:Service",
  "g-framework:content": "http://example.org/"
}

On a related note, the actual URI is not actually validated for correctness. One might argue that it should (we do that for numeric values and dates) but none of the other implementations available on https://rdfshape.weso.es/shaclValidate do that either...

Thank you! The example with the @context helped a lot! 👏


Doc mistake? - .NET SqlConnection parameters for connection retry

Hi team, can you check and confirm if this is a mistake in the documentation?
.NET SqlConnection parameters for connection retry

"For example, if the count equals 3 and the interval equals 10 seconds, a timeout of only 29 seconds doesn't give the system enough time for its third and final retry to connect: 29 < 3 * 10."

Firstly, 3 * 10 = 30, so it doesn't make sense that "doesn't give the system enough time for its third and final retry to connect" when 29<30.
Secondly, according to the quote below, the first retry to connect happens immediately, so if the retry count equals 3,  shouldn't the calculation be,  (3-1) * 10? Which is 20 seconds, therefore there is not enough time for the final retry to connect to work?
https://docs.microsoft.com/en-us/dotnet/api/system.data.sqlclient.sqlconnection.connectionstring?view=dotnet-plat-ext-6.0

ConnectRetryInterval | 10 | Specifies the time between each connection retry attempt (ConnectRetryCount). Valid values are 1 to 60 seconds (default=10), applied after the first reconnection attempt. When a broken connection is detected, the client immediately attempts to reconnect; this is the first reconnection attempt and only occurs if ConnectRetryCount is greater than 0. If the first reconnection attempt fails and ConnectRetryCount is greater than 1, the client waits ConnectRetryInterval to try the second and subsequent reconnection attempts.

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

ID: 8d7562b8-cb8a-4664-8c80-ef81610e5995
Version Independent ID: 43446cd9-a3f0-35e9-f7d7-8a2990ba5331
Content: Working with transient errors - Azure SQL Database
Content Source: azure-sql/database/troubleshoot-common-connectivity-issues.md
Service: sql-database
Sub-service: development
GitHub Login: @ramakoni1
Microsoft Alias: ramakoni

Hi @helenxfu, thanks for bringing this to our attention. I have assigned the issue to the content author to evaluate and confirm if this is a mistake

hi @helenxfu -Thank you for raising this issue. Am investigating this further and will submit a PR to docs later this week or early next week with clarification.

hi @helenxfu - Sorry for the delay in updating. We will be updating the docs with the following clarifications.
The connection retry settings (ConnectRetryCount and ConnectRetryInterval) apply to connection resiliency. Connection resiliency encompasses two distinct scenarios.

Open connection resiliency refers to the initial SqlConnection.Open() event. The first connection attempt would be counted as try zero. ConnectRetryCount applies to retry numbers above that. So, when connection zero fails (might not be immediate), ConnectRetryInterval is applied first followed by subsequent ConnectRetryCount (and ConnectRetryInterval) attempts.

Idle connection resiliency refers to automatic detection and reconnection of existing, idle connections that have been broken. The first attempt at reconnecting a broken idle connection count as the first retry attempt.

See examples below:
Scenario: New connection
ConnectRetryCount -3, ConnectRetryInterval - 10 seconds
4:10:00 - Connection.Open() - zero attempt
4:10:01 - Connection failure detected
4:10:11 - Retry 1 --> First retry happens after ConnectRetryInterval
4:10:21 - Retry 2
4:10:31 - Retry 3
Scenario: Idle connection
ConnectRetryCount -3, ConnectRetryInterval - 10 seconds
4:10:00 - Detect broken connection - zero attempt
4:10:01 - Retry 1 -->First retry happens immediately
4:10:11 - Retry 2
4:10:21 - Retry 3
Note: The above times are just for demonstration purposes and the detection times in both scenarios depend on underlying infrastructure.

@helenxfu - docs are now updated. Please check updated section: https://learn.microsoft.com/en-us/azure/azure-sql/database/troubleshoot-common-connectivity-issues?view=azuresql#net-sqlconnection-parameters-for-connection-retry  - thanks again for reporting this. Please let us know if anything else needs clarification.

Hi @helenxfu , thanks so much for helping improve our content! Since your issue was addressed, we'll go ahead and close out this Git Issue but please feel free to comment should you need anything further.
Thanks again and hope you have a wonderful rest of your day!
Masha from the SQL Docs team
#please-close


Issue #97: Argo's use of command and args fields do not follow Kubern…

…etes

In general, I am okay with the changes since I saw the end-to-end test passing for my specific issue. It would be preferable to have a unit test testing all the possible combinations...