Error installing onedrive-d involving setup tools.

Hi. I have tried this on current versions of Linux Mint, Ubuntu, and Lubuntu. Each time I experience the exact same issue. The message I receive is:
Reading package lists... Done
Building dependency tree
Reading state information... Done
python3-gi is already the newest version (3.20.0-0ubuntu1).
inotify-tools is already the newest version (3.14-1ubuntu1).
0 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
Traceback (most recent call last):
File "setup.py", line 4, in
from setuptools import setup, find_packages
ImportError: No module named 'setuptools'
I have verified that I have setup tools. I also ran through the process of reinstalling setup tools, and a few other tricks mentioned on forums for Linux Mint, but no resolution to date.
Does the community have any suggestions why this is occurring and how I can resolve it?
Thank you greatly.
Brian

Had a similar problem, think it's to do with $PATH issues.
New install of Mint 19.1 XFCE,
Think I've got around it by doing the following:
I added the  to the $PATH:

PATH=$HOME/.local/bin:$PATH

Not sure if this fixed it, but then because pip or pip3 wasn't being found - defiantly had installed the latest:

python3 -m pip install --user --upgrade pip

I used python3 -m pip to install:

python3 -m pip install --user setuptools
python3 -m pip install --user git+https://github.com/xybu/onedrived-dev.git

I then had to install the source manually:

git clone https://github.com/xybu/onedrived-dev.git
cd ondrived-dev

Manually tested:

python3 ./setup.py test

Then installed:

python3 ./setup.py install --user

The last gotcha I encountered was with the ngrok setup, found I had to move ngrok:

sudo mv ~/ngrok /usr/bin/ngrok

I found that here: https://medium.com/@glmdev/onedrive-sync-for-linux-ubuntu-2bcbf6777ee4

Can you put all the commands used to install it? There is a CI build that install the package every time without issue...


feat: ✨ icon-only button

Checklist (for the issue creator)

[x] I have looked at the documentation site and was not able to find the required feature.
[x] I have looked into the Figma boards and was not able to find the required feature.
[ ] I would be willing to provide a PR for this feature.

Story

As a user of the Synergy Design System, I would like to put a single button without any text into a button. The button should be a square.
Acceptance criteria

[ ] All DoD items successfully completed
[ ] Button is a square after an icon is placed into default slot as only child
[ ] unittests
[ ] story

Duplicate of #309


sleep-server

how about an option to let the computer go to sleep instead of shutting it down completely. Might be a nice feature for laptops.

I agree. For the short story, that's part of the reason I named it stop-server instead of shutdown ^_^
@hemanth want to create a sleep package?

Sure!  Thank you :+1:

Published (v0.3.0) :)

:+1:


ngspice update to 41

Library name
ngspice
New version number
41
Other information that may be useful (release notes, etc...)
https://sourceforge.net/projects/ngspice/files/ng-spice-rework/41/ngspice-41.tar.gz/download

Hello, I’m a user of the ngspice library. I’m writing to ask for your help in updating the version. I’m currently solving this problem by modifying portfile.cmake to download the 39 version of the ngspice library, but I would be grateful if you could help me update the version.

Ok, I will update this port.

Thank you so much! I really appreciate it.


Proposal: Add FlyoutPlacementMode.Center to the FlyoutPlacementMode enum.

Desired Behaviour
When  FlyoutPlacementMode.Center is selected, the Flyout should centre itself at the centre of the xaml root of the target element.
Rationale

It is troublesome to use margins to centre the flyout.
TeachingTipPlacementMode already has "Center",  so adding it will improve consistency.

Maybe that's why they didn't Add FlyoutPlacementMode.Center at first place
https://github.com/microsoft/microsoft-ui-xaml/blob/14364e6c301e881c5e2b6b9c39503343c66e53eb/src/dxaml/xcp/dxaml/lib/ContentDialog_Partial.cpp#L1250-L1272

Closing as by design.


Database counter for 'dataset' does not match the number of entries in the table.

Hey,
I am testing out the new TALON version 4.4 with the same testset I used for 4.2 (which passes).
However, I am encountering the message in the title.
Database counter for 'dataset' does not match the number of entries in the table. Discarding changes to database and exiting...
table_count: 2
counter_value: 1
Traceback (most recent call last):
  File "/home/miniconda/envs/py37/bin/talon", line 8, in <module>
    sys.exit(main())
  File "/home/miniconda/envs/py37/lib/python3.7/site-packages/talon/talon.py", line 2411, in main
    update_database(database, batch_size, run_info.outfiles, dataset_db_entries)
  File "/home/miniconda/envs/py37/lib/python3.7/site-packages/talon/talon.py", line 1786, in update_database
    check_database_integrity(cursor)
  File "/home/miniconda/envs/py37/lib/python3.7/site-packages/talon/talon.py", line 2087, in check_database_integrity
    raise RuntimeError("Discrepancy found in database. " + \
RuntimeError: Discrepancy found in database. Discarding changes to database and exiting...

I checked the database using DB Browser for SQLite to see if the "dataset" table has 2 dataset entries, but it contains just one. My config file also contains just one dataset entry. Any idea how these numbers are not matching up?

Sorry, already found the mistake to be on my end, excuse me for filling your issue page.


allow SerialIterator to use arbitrary random number generator

In some cases of distributed machine learning, it is needed to synchronize batch order of the iterator among multiple processes.
In order to achieve it, private random number generators are needed to avoid being interfered by other random number generation processes (e.g. dropout).
This PR alters SerialIterator to enable handling private RNG.
If no RNG is specified, it uses the numpy default RNG, which is compatible to the previous behavior.
For detail, please refer to chainer/chainermn#185.

Is this related? https://github.com/chainer/chainer/pull/3429

For testing purposes, can you provide an example of a private RNG?

Thank you for the reply. Then I will reimplement after that the interface is fixed.

Fyi, https://github.com/chainer/chainer/pull/3429 has now been merged. Maybe you can use the new ShuffleOrderSampler taking a rng as constructor argument?

Talked offline with @levelfour and we agreed that we can close this PR. Please raise an issue if there are any issues using the ShuffleOrderSampler.


feat(anim): Add animation example

This adds example animations for page transitions, validations and repeated lists
Please take a look at the config.js and package.json files, have the feeling that something got messed up there

Can we do this without the class animation in the welcome screen. I don't want to change the nature of the original demo by adding too many features. (Though, that is pretty cool.) Would you mind removing that from the PR for now?

OK no problem, wasn't sure how much you wanted to show. It's now removed

Looks better. Can I do a 0.1.0 release of animator-css? Any reason not to do that?

ok guess now that you released Animator-CSS it's fine to be merged :) do I need to fix anything here?

I don't think you need to do anything. I just ran out of time to merge it yesterday. I will get it in soon. Thanks!


Debug build failure: gtest_label_1081 used but not defined

ubuntu 16.04, default gcc 5.4
git clone https://github.com/abseil/abseil-cpp.git
cd abseil-cpp
bazel build ...

ERROR: abseil-cpp/absl/strings/BUILD.bazel:235:1: C++ compilation of rule '//absl/strings:string_view_test' failed (Exit 1)
In file included from external/com_google_googletest/googletest/include/gtest/gtest.h:58:0,
                 from absl/strings/string_view_test.cc:28:
absl/strings/string_view_test.cc: In member function 'virtual void {anonymous}::NonNegativeLenTest_NonNegativeLen_Test::TestBody()':
absl/strings/string_view_test.cc:38:40: error: label 'gtest_label_1081' used but not defined
 #define ABSL_EXPECT_DEATH_IF_SUPPORTED EXPECT_DEATH_IF_SUPPORTED
                                        ^
absl/strings/string_view_test.cc:1080:3: note: in expansion of macro 'ABSL_EXPECT_DEATH_IF_SUPPORTED'
   ABSL_EXPECT_DEATH_IF_SUPPORTED(absl::string_view("xyz", -1),
   ^
absl/strings/string_view_test.cc: In member function 'virtual void {anonymous}::LenExceedsMaxSizeTest_LenExceedsMaxSize_Test::TestBody()':
absl/strings/string_view_test.cc:38:40: error: label 'gtest_label_1092' used but not defined
 #define ABSL_EXPECT_DEATH_IF_SUPPORTED EXPECT_DEATH_IF_SUPPORTED
                                        ^
absl/strings/string_view_test.cc:1091:3: note: in expansion of macro 'ABSL_EXPECT_DEATH_IF_SUPPORTED'
   ABSL_EXPECT_DEATH_IF_SUPPORTED(absl::string_view("", max_size + 1),
   ^

git bisect shows 99477fa9f1e89a7d8253c8aeee331864710d080c is the first bad commit.
This is a quick fix:
diff --git a/absl/strings/str_cat_test.cc b/absl/strings/str_cat_test.cc
index e9d67690..9c6e4df1 100644
--- a/absl/strings/str_cat_test.cc
+++ b/absl/strings/str_cat_test.cc
@@ -405,8 +405,7 @@ TEST(StrAppend, Death) {
   std::string s = "self";
   // on linux it's "assertion", on mac it's "Assertion",
   // on chromiumos it's "Assertion ... failed".
-  ABSL_EXPECT_DEBUG_DEATH(absl::StrAppend(&s, s.c_str() + 1),
-                          "ssertion.*failed");
+  ABSL_EXPECT_DEBUG_DEATH(absl::StrAppend(&s, s.c_str() + 1), "ssertion.*failed");
   ABSL_EXPECT_DEBUG_DEATH(absl::StrAppend(&s, s), "ssertion.*failed");
 }
 #endif  // GTEST_HAS_DEATH_TEST
diff --git a/absl/strings/string_view_test.cc b/absl/strings/string_view_test.cc
index fffa7b99..9fecf655 100644
--- a/absl/strings/string_view_test.cc
+++ b/absl/strings/string_view_test.cc
@@ -1077,8 +1077,7 @@ TEST(HugeStringView, TwoPointTwoGB) {

 #if !defined(NDEBUG) && !defined(ABSL_HAVE_STD_STRING_VIEW)
 TEST(NonNegativeLenTest, NonNegativeLen) {
-  ABSL_EXPECT_DEATH_IF_SUPPORTED(absl::string_view("xyz", -1),
-                                 "len <= kMaxSize");
+  ABSL_EXPECT_DEATH_IF_SUPPORTED(absl::string_view("xyz", -1), "len <= kMaxSize");
 }

 TEST(LenExceedsMaxSizeTest, LenExceedsMaxSize) {
@@ -1088,8 +1087,7 @@ TEST(LenExceedsMaxSizeTest, LenExceedsMaxSize) {
   absl::string_view ok_view("", max_size);

   // Adding one to the max should trigger an assertion.
-  ABSL_EXPECT_DEATH_IF_SUPPORTED(absl::string_view("", max_size + 1),
-                                 "len <= kMaxSize");
+  ABSL_EXPECT_DEATH_IF_SUPPORTED(absl::string_view("", max_size + 1), "len <= kMaxSize");
 }
 #endif  // !defined(NDEBUG) && !defined(ABSL_HAVE_STD_STRING_VIEW)

Thanks for the report. I've managed to reproduce this in a VM. I have no idea why it doesn't reproduce on any of the compilers I normally use.
I have a different fix in mind though:
#define ABSL_EXPECT_DEATH_IF_SUPPORTED EXPECT_DEATH_IF_SUPPORTED
becomes
#define ABSL_EXPECT_DEATH_IF_SUPPORTED(s, r) EXPECT_DEATH_IF_SUPPORTED(s, r)

Fixed by d8cfe9f2a77fbee02c09642491e62a3f3677e0f6.


Add chess 0.3.1-1

consider not taking the toplevel name chess and using a variant of it? (in case another chess app comes along)

I also thought about it a long time. I couldn't come up with a decent play on the word. I initially had called it remarkable-chess (some of the early release binaries are still called that). But I ended up renaming it in chess since the package shouldn't start with remarkable- (there was some discussion if I'm not mistaken).
Do you have any other idea for it? Btw it is available on my test repo since I used that to QA my packages anyway.

Just tested the package and it works great, thanks! I don’t have strong opinions on the name.

You really can't think of any other name than chess? it seems unfair to other packages to pick the most generic name (imo, no package should be called "chess")
lChess, LinChess, LinusChess, rustChess, reChess, rmChess, Chesslet, ChessMarkable...

I'm also really torn on it. My initial guess is that it will probably be fairly unlikely that we end up with two chess versions and my only other idea for a name ress didn't sound good or like chess at all imo. Going with rmChess is also getting boring for me and the casing just is messy.

You really can't think of any other name than chess? it seems unfair to other packages to pick the most generic name (imo, no package should be called "chess")
lChess, LinChess, LinusChess, rustChess, reChess, rmChess, Chesslet, ChessMarkable...

Agreed. ChessMarkable sounds nice. I'll use that if you don't mind.

go for it!
re: two chess apps: you'd be surprised

I already got some suspicion based on your response. :laughing:

where did the chess icons come from / what is the license on them?

where did the chess icons come from / what is the license on them?

I took them from pixabay (orig image and url here). They don't seem to care what you do with those images. Crediting them is even a bonus only. The disadvantage is that they are fairly low res and the transparency is a bit messed up. If I have time I'll consider remaking my own ones from scratch (hopefully). For now they suffice.

make sure to run through shellcheck

Sorry for again for dismissiong your review accidentally by committing the changes to it @raisjnn . I still don't quite get then GH does that.
The update is mostly stability fixes for the software. And hopefully the last change for at least a few days.


cannot convert incomplete value "1" to JSON

Title is a bit meaningless, feel free to change it to something more appropriate. But:
$ cat > demo.cue <<EOF
a: int
a: >0
a: <2
EOF
$ cue eval demo.cue
a: 1
$ cue export demo.cue
cue: marshal error at path a: cannot convert incomplete value "1" to JSON

I don't know how complicated this is (only have a rudimentary understanding of the algorithms and ideas), but ISTM that eval is actually able to tell that only a single value can fulfill those constraints and which, but export still treats it as incomplete.
Only bringing that up because I gave a quick intro-talk about CUE today and sorta handwaved types vs. values as "values are essentially types with only a single possible value". This export-example kind of threw that in the bin :)

Great catch.
This is not meaningless. It really should resolve to 1.

Groundness inference can not always be guaranteed, btw. Subsumption may result in false negatives. This is equivalent to not being able to tell full equivalence of unresolved expressions in Prolog (only structural equivalence). Subsumption is only guaranteed to be accurate when comparing against concrete cases.  But it should at least infer it for simple cases like this.
Sent out a fix.

This issue has been migrated to https://github.com/cue-lang/cue/issues/108.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Is there a way to hide mornig or late hours

Version
1.7.0
Current Behavior
All hours from 0 - 24 are shown
Expected Behavior
Only f .eg. 8 - 20 is displayed

@alexanderhoneder #175

I believe this option is already available.
You can set the visible hour range using the hourStart and hourEnd options and the the calendar will only show the hours between that range.
new tui.Calendar('#calendar', {
  scheduleView: ['time'],
  useCreationPopup: false,
  calendars: [],
  week: {
    workweek: false,
    hourStart: 6,
    hourEnd: 22,
    narrowWeekend: true
  }
});

Thank you for the fast Response
It worked perfect


Updates for PureScript 0.11

Mostly trivial changes:

Bumping dependencies
Replacing * kind with Type
Replacing ! kind with Effect
Explicity adding _ <- ... in monadic expressions that discard their result.
In HalogenEffects, renaming err to exception (due to breaking change in prescript-exceptions)
Replacing tupled constraints with curried =>
Accounting for Nullable -> Maybe change in APIs in purescript-dom.
Fixing a name-shadowing error.

The non-trivial change:
It seems Data.Foreign.Class was transferred from purescript-foreign to purescript-foreign-generic and the function readProp was remove so I inlined it here and replaced:

IsForeign -> Decode
read -> decode
It should most be harmless and carry the same meaning as before, but I'd like someone more experienced to verify that the change is valid.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks, but there's already a PR underway for this - #440

Sorry - missed that!


Region update from serverless.yml

I'm not sure if this is an issue but I think is a good addition. The thing is that if you try to invoke a function that access an aws service (e.g. DynamoDB), with serverless webpack invoke or serverless webpack serve and you haven't specified the region in the handler like AWS.config.region = "us-west-2" or AWS.config.update({region: "us-west-2"}), you got this error:
  Config Error -------------------------------------------

     Missing region in config

And this doesn't happen if you invoke a function with the command serverless invoke local who I suppose  is getting the region from serverless.yml

This is happening for me too, I've defined my stage and region in serverless.yml.

I've posted my workaround for this issue here.

@hassankhan Thanks for the info!

@Dalfons0 We'll switch the invoke command to use serverless invoke local with version 3.0.0. A working PR is already available ( #153 ). Could you check if it works with that source code revision if you use serverless invoke local?

invoke will be removed in the next v3.0.0 release and integrates fully with serverless invoke local (see #151 ). No efforts will be spent on the function anymore. So I'll close this issue.


Update README.md: use internlm-chat-7b

May also fix the Chinese doc

May also fix the Chinese doc

fixed

May rebase main to fix linting check


chore(main): release 3.8.0

:robot: I have created a release beep boop
3.8.0 (2024-01-11)
Added

Add manualFramingHeaders on RequestInit and ResponseInit, and add Request.prototype.setManualFramingHeaders and Response.prototype.setManualFramingHeaders (#705)
Add Request.prototype.backend getter to return the name of the backend assigned to the request (9c750e5)
Allow URL as input on fetch() on TypeScript typings for compat with Node.js (#707) (4f39943)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fastly/js-compute-runtime/releases/tag/v3.8.0 :sunflower:


Made sample alert creation optional

Made sample alert creation optional
Updated doc to explain alert can be created only after CF has run at least once

linting failing with error code 3, not sure about that the catch is


Organization create fails with "The operation failed. "

[Version] OSCM 17.5.x 2017/12/11 (master)
[How to reproduce]

build and start containers with sample data
log in as platform operator "administrator" and create organization with
supplier and technology provider role. Fill out info
save

[Expected result]
organization is created
[Observed result]
operation failed
[Details]
see attached file
ErrCreateOrganization.txt

It is a problem with constraint in a sample data provided. Therfore moved to docker repo.
Related issue: https://github.com/servicecatalog/oscm-dockerbuild/issues/95


Styling of Helpful Materials

Worked on the Helpful Materials page, which now meets the current styling of /home.

Seems to be a merge conflict, probably because we merge a lot of pull requests :) I'll happily
merge this one aswell if you have time fixing it :)


Datalake error

Dont know what I did wrong I followed the instructions to create the dataset it said that it would create 3 saved queries on Athena but created 2:
Database For ComplianceAsCode AND
Table For ComplianceAsCode
But there is no data.
This is the SQL for Table For ComplianceAsCode:
CREATE EXTERNAL TABLE IF NOT EXISTS complianceascode.events (AccountID string,ComplianceType string,RecordedInDDBTimestamp string,RuleName string,LastResultRecordedTime string,RuleARN string,ResourceID string,ResourceType string,AccountClassification string,RuleCriticity string) ROW FORMAT SERDE 'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe' WITH SERDEPROPERTIES ('serialization.format' = ',', 'field.delim' = ',') LOCATION 's3://analytics-compliance-as-code-xxxxxxx/' TBLPROPERTIES('has_encrypted_data'='false', 'skip.header.line.count'='1')
That S3 bucket has no data at all.


[vault-env] clean up the environment #feature

Just tried vault-env in a raw mode without Kubernetes, i.e. I set VAULT_{ADDR,TOKEN}. What seems strange to me that these guys are not wiped, I do understand that this should be one-time use token with TTL... But is there any consideration why this is not done?

Hi Denis, no this is not intentional, they are just not cleared. Are you willing to open up a PR for this?

Well, maybe, since I have got almost no golang experience. Though should be trivial, I'll ping you back later this week if I succeed or don't.

No worries, happy to help.


fix(karma-esm): Implement import map support

Currently importMap option passed to karma-esm is ignored (#1127)
This PR loads the importMap data and inject into karma debug and context files
It also fixes how chai path in test importmap is defined
The last part try to pass the flags to enable import map support in chrome based on SO. This is not working. Using --enable-experimental-web-platform-features flag works
If i run Karma with Chrome and enable manually the importmap support it works

Great! Thanks

Many thanks


Create somewhat smaller test files

This speeds up the tests, which take quite long at the moment.

Good idea! I have just one nitpick.


Remove Exchange Online from EmailComposeMode list

This is no longer supported in Outlook Web

@philipzloh, likely, but the parameter is still available in Exchange Online. So, until the parameter is actually removed from Exchange Online PowerShell, I want to nuance the availability message:

This parameter is available or functional only in on-premises Exchange.

Docs Build status updates of commit 096a32b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-MailboxMessageConfiguration.md
:white_check_mark:Succeeded
View (exchange-ps)

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 096a32b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-MailboxMessageConfiguration.md
:white_check_mark:Succeeded
View (exchange-ps)

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[ALLUXIO-3373] Improve handling of SSD failures

https://alluxio.atlassian.net/browse/ALLUXIO-3373

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1095/
Test PASSed.

@calvinjia I updated the PR with some improvement. PTAL.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1099/
Test PASSed.


Update zh-Hans/user-handbook.md format

Actually the original format is
> **Note:** Since it's generally a bad idea to run Babel globally you may want
> to uninstall the global copy by running:
>
> ```sh
> $ npm uninstall --global babel-cli
> ```

see translations/en/user-handbook.md

The right fix way is #181


Is it possible to cast images?

Can I cast static images like jpgs or pngs?

Yes, the following image types are support:
APNG
BMP
GIF
JPEG
PNG
WEBP
https://developers.google.com/cast/docs/media


Rename OSX to macOS throughout the project

Affected places:

Target name (shared scheme): Alamofire OSX to Alamofire macOS.
.travis.yml: OSX_FRAMEWORK_SCHEME="Alamofire OSX" to MACOS_FRAMEWORK_SCHEME="Alamofire macOS". PS: xcpretty -c can remove -c since it is now the default option.
Other places: os(OSX) to os(macOS).
I'm not sure if this needs to be updated.

This would definitely be a worthwhile change. We'll need to make it across all three libraries though.

PR #1520 has been merged. Thanks for putting this together @JustinJiaDev! 🍻


Constants are still colored differently with semantic highlighting off

Issue Type: Bug

Turn off the editor.semanticHighlighting setting
View file with some constants in it:

I expected these to be blue as they are in stable.
VS Code version: Code - Insiders 1.45.0-insider (ec0d19789f89d4c25895f4a0cf364276cfb0c6ed, 2020-04-20T06:04:22.698Z)
OS version: Darwin x64 18.7.0

Duplicate of https://github.com/microsoft/vscode/issues/95346

duplicate of https://github.com/microsoft/vscode/issues/95346


Update NHFLUX reader/writer to process all VARIANT data

In PR #681, it was identified that the NHFLUX reader/writer was not able to read DIF3D-VARIANT data at all. The DIF3D-VARIANT NHFLUX format is different than the DIF3D-Nodal format (at least as of v11.0 of DIF3D), and the existing reader (at the time of #681) was not capable of reading the VARIANT format.
#681 partially fixed this issue to allow for most of the data to be processed by the reader/writer. That update was sufficient to be able to make use of the ARC tool EvaluateFlux. However, some of the VARIANT data is thrown away by the reader/writer, which is not ideal. This shortcoming should be addressed.
The data that still needs to be stored by the reader/writer can be found throughout the nhflux.py module by searching for the use of the variable dummy. Here is a list of what I believe is still missing.

Odd-parity flux moments. These are iterated over on the 3D record. The even-parity moments are stored on the fluxMoments attribute, so perhaps the odd-parity moments could be stored on a new attribute called fluxMomentsEven. This parameter would be empty when processing DIF3D-Nodal files.
Outgoing partial radial currents beyond NSCOEFF == 1. These are iterated over on the 4D record.
Ingoing partial radial currents beyond NSCOEFF == 1. These are iterated over on the 4D record.
Z-directed partial currents beyond NSCOEFF == 1. These are iterated over on the 5D record.

For the last three bullets, one way to potentially address the issue is by expanding the dimensionality of the arrays that store the NSCOEFF == 1 data by 1 (i.e., create a new axis for the NSCOEFF dimension). This allows one to keep the same variable names...but, it does break the use of these arrays for existing users (who expect the current number of dimensions to be present), which may not be desirable.

@jakehader, I created an issue for this topic. This is straightforward to fix, I believe...I think it just comes down to what is the best way to fix it.

@jakehader, I created an issue for this topic. This is straightforward to fix, I believe...I think it just comes down to what is the best/cleanest way to fix it.

Thanks @Nebbychadnezzar!

Ah, that's a shame.
Are you... volunteering to fix it?  :)


Add jazzy config

Requires adjustments to the documentation workflow to have correct org, repo and branch

superseded by #24


Discontinued?

Hi. I recently discovered this app in appstore, and it seems it does not work as expected, probably because react native has changed some versions already.
Is this app discontinued in favor of any other?

Hey! The old app will be replaced soon by one powered by Exponent.js. We'll update here once that's done.

You might want to post a warning in the Apple and Android app stores.  You're getting a lot of negative reviews because people don't know it's dead.  Any ETA on the Exponent.js version?

Sorry no ETA - this project has been transferred to the exponent.js team - I'm no longer working with RN but try to keep this site up to date when time permits. Posting a warning in the meantime is a good idea though!
@brentvatne

The new Android build is published in the Play Store. iOS will be ready in a few days. Thanks!


correct varlink command in service file

The struct of the varlink command changed to accept a URI
as input.  This was never updated in the service file
Signed-off-by: baude<EMAIL_ADDRESS>

LGTM

bot, retest this please

bot, retest this please

bot, retest this please

@rh-atomic-bot r+


implement key schedule changes

Some labels were changed in https://github.com/quicwg/base-drafts/pull/1004/.
This PR might be useful: https://github.com/quicwg/base-drafts/pull/1077.

https://github.com/quicwg/base-drafts/wiki/Test-Vector-for-the-Clear-Text-AEAD-key-derivation


Some completions don't work in Neovim after and before 2.1.4

Vue - Official extension or vue-tsc version
2.1.6
VSCode version

Vue version
3.3.10
TypeScript version
5.5.4
System Info
Windows 10
Neovim 0.10

package.json dependencies
"dependencies": {
    "vue": "^3.3.10"
  },
  "devDependencies": {
    "@mdi/font": "^7.3.67",
    "@rushstack/eslint-patch": "^1.3.3",
    "@vitejs/plugin-vue": "^4.5.1",
    "@vue/eslint-config-prettier": "^8.0.0",
    "@vue/test-utils": "^2.4.3",
    "amfe-flexible": "^2.2.1",
    "axios": "^1.6.2",
    "eslint": "^8.49.0",
    "eslint-plugin-vue": "^9.17.0",
    "jsdom": "^23.0.1",
    "postcss-pxtorem": "^6.0.0",
    "prettier": "^3.0.3",
    "sass": "^1.69.5",
    "vite": "^5.0.5",
    "vite-plugin-vuetify": "^2.0.1",
    "vitest": "^1.0.1",
    "vue-router": "^4.2.5",
    "vuetify": "^3.5.0"
  }

Steps to reproduce
Just updated from 2.1.4 to 2.1.6 (before 2.1.4 dont work too)
What is expected?
Show completions like in 2.1.4
What is actually happening?
Completions for props, events, binds, and emits stopped working both before and after version 2.1.4.
2.1.6

2.1.4

Link to minimal reproduction
No response
Any additional comments?
No response

Working for me in 2.1.6, could you share a minimal reproduction?

Tried with your dotfile, definitely something about your nvim config caused this issue.

Weird, 2.1.4 works perfectly with this config

what's your neovim version, can you try with nightly? Possible upstream change ( LSP itself )

My intuition is that this is caused by the inconsistent version of @vue/langugae-server and @vue/typescript-plugin.

My intuition is that this is caused by the inconsistent version of @vue/langugae-server and @vue/typescript-plugin.

Which inside @vue/language-server? Its 2.1.6 too

My intuition is that this is caused by the inconsistent version of @vue/langugae-server and @vue/typescript-plugin.

It should be the same, as in the config the plugin path references to @vue/language-server
I kinda reproduced this when tsserver has not loaded yet. Can you check with LspInfo see if ts_ls or vtsls still attached and with LspLog see if any error with tsserver?

I don't see any errors in the LspLog.

I've figured out what the issue was.
vtsls was using the tsserver from the current project, which had typescript 4.9. After updating it to 5.6.2, the problem disappeared.
Sorry for the confusion, i had assumed vtsls was using the version from mason.
Suppose I need to explicitly set the tsdk in vtsls?

Aha, glad you figured that out I am actually testing things with your vue repo and because I also have auto use workspace tsdk thus my config also have the same issue.
You can just disable it in here: https://github.com/exzolink/dotfiles/blob/main/nvim/lua/configs/lsp/servers/typescript.lua#L39
If you still want to keep this seeting,  vtsls provide a code action to select typerscript version to use.https://github.com/yioneko/vtsls?tab=readme-ov-file#commands
You can either call neovim api to invoke the code action or use https://github.com/yioneko/nvim-vtsls

Got it, thank you very much for your help!


Client side proving implies no_std

If we want users to be able to use stwo in the browser for client-side proving, we need to be able to target wasm, and therefore to compile in no_std.
In my opinion, it is a must-have that will unlock a lot of applications and my experience is that the earlier the project embraces no_std, the easier it is for everyone later on.
What is your plan regarding this?

This is not a priority for us right now, but if you have a good PR doing it, I'll check it

It was kinda my point: it's not a priority at the beginning, but the more you wait to implement it the more difficult and tedious it becomes.

My opinion is that it is useful to do no_std in a batch. In the past, the major challenge with no_std is that some dependencies may fail to be no_std and cause issues. Other than that, standard vec![], core::, println!... are one go.

The problem is that switching to no_std will imply some breaking changes, which is better to have when nobody is using the project, than when 10 different companies are using the lib in production.
The less sedimented the codebase is when doing it, the easier it will be.
Moving cairo-vm, cairo, blockifier and starknet-api to no_std took me months and it is still not merged entirely at this time, more than one year after I started pushing it. That's because it is not a priority for any of the team working on it (coz they now have code in production and prefer stability over anything), and now implies huge breaking changes (coz the codebase solidified in a way that is not compatible with no_std), that should be coordinated between multiple repositories that are all interdependent.
I'm talking from my own experience of doing this work across the whole Starknet rust crates ecosystem: it's an endless pit of despair.
So if we all agree that we want to be able to use STOW in the browser at some point in the future, which sounds like a reasonable usecase, the switch to no_std should be done as soon as possible.

^ I have the feeling that the key is also to narrow down to only the component that would be needed for the WASM prover. Do you think full no_std support for all the crates, including those for APIs or the compilers, would be necessary?

Because technically the crypto part shouldn't really require std features a lot, but when things involve filesystems databases and so on, and when FFI is involved, then it becomes almost impossible.

You are very correct: not everything needs to be executable in the browser. That is why it is important to start delimiting early the part that needs to be no_std so that we don't inadvertently mix those with some filesystem/ffi/... logic, as we carelessly build the lib.
That is what happened in most of the crates I had to convert to no_std, and it was a terrible experience to do this separation afterward when it was not thought from the beginning.


ledger private key generation

This introduces a possible spec for generating giant keys on the Ledger device

Ok, this lets us derive keys from the Ledger state, but this doesn't seem to get us anything meaningful if the Ledger can't produce signatures/VRF evaluations. What's the idea there?

Are you asking where the spec for generating signatures is? It's the same as https://github.com/CodaProtocol/coda/pull/2364/files, there's nothing controversial or new that we need to do with respect to signing on the ledger vs on a computer

@rbkhmrcr So is cx_ecschnorr_sign still usable with this design (despite the unsupported curve), or will we reimplement that?

@cmr it isn't, cx_ecschnorr_sign and all of the similar opcodes take a cx_ecfp_private_key_t which has the curve ID as its first parameter (here), so we get to rewrite group arithmetic (here), and then schnorr (here) -- I stuck to the same format as the signatures from cx.h, but as we have complete control over most of the choices made in the app it might change. I'm not up to testing fully featured schnorr yet (blake2b also doesn't have an opcode on the Ledger but that at least has reference C code) and I don't know which of affine or projective coordinates will win out in the battle for space vs time on the Ledger so the code as it currently is kinda reflects that


Worker NPCs should use the build-in mechanism for cutting down trees

Current NPCs cheat at this when constructing buildings. The tree is removed by the engine, but this is not apparent cheating because it still costs the NPC a turn.
See #90.

Fixed with e68c128.


The CWE data is not showing up

Hi Peter,
The report generated from the action seems to be missing the CWE data, seems CWE labels are removed the Code Scanning alerts API. Please see attached, the summary PDF generated.
summary.pdf
@rohitnb
@mohan-the-octocat
@amol1717

It seems that the CWE coverage is derived from the Applied Code Scanning Rules, which are code scanning rules that are retrieved from the sarif files that were previously generated by CodeQL's analysis action.
However, the expected format of the sarif files used to populate the rules property of the SarifReport is the following:
{
    "file": "/home/runner/work/sample-repository/results/csharp.sarif",
    "payload": {
        "data": {
            "$schema": "https://json.schemastore.org/sarif-2.1.0.json",
            "version": "2.1.0",
            "runs": [
                {
                    "tool" : {
                        "driver" : {
                          "name" : "CodeQL",
                          "organization" : "GitHub",
                          "semanticVersion" : "2.2.5",
                          "rules": [ {  } ]
                        }
                    }
                }
            ]
        }
    }
}

Which doesn't quite match the output of the sarif report, which is in the format of:
{
    "file": "/home/runner/work/sample-repository/results/csharp.sarif",
    "payload": {
        "data": {
            "$schema": "https://json.schemastore.org/sarif-2.1.0.json",
            "version": "2.1.0",
            "runs": [
                {
                    "tool" : {
                        "driver" : {
                          "name" : "CodeQL",
                          "organization" : "GitHub",
                          "semanticVersion" : "2.2.5",
                          "rules": []
                        },
                        "extensions": [
                            {
                                "name": "codeql/java-queries",
                                "semanticVersion": "0.0.13+4551af90f61a8d5f5c1c88a036595b5919a6c98e",
                                "locations": [ { } ],
                                "notifications": [ { } ],
                                "rules": [ {  } ]
                            }
                        ]
                    }
                }
            ]
        }
    }
}

While the rules property is still inside the driver property, it will always be empty. So, in order to fix this issue it is necessary to get the rules of all extensions while considering that only extensions with rules applied will have a rules property. This can be done in the getRules function of the SarifReport class.
I created a PR that makes the changes described above but keep in mind that I believe this approach works great for creating reports with only one language but not when you have more than one language.
The reasoning behind that is that the action uses GitHub's API to retrieve alerts, dependencies and vulnerabilities, which will have all the information of all the languages when the last language finishes its analysis; however, the sarif files will only have information of the rules related to the last language being analyzed.
There could potentially be a few ways to address that, but I am wondering if leveraging the rule associated with every alert in the alerts method of the API would suffice.
I might create another PR based on that, but I am not sure if the intent of the number of rules applied was the number of rules that were applied. If that is the case, then the fix would be easy.


Add functional tests for cFE ES Performance Monitor APIs

Is your feature request related to a problem? Please describe.
Need open source functional tests for certifiability
Describe the solution you'd like
Add functional tests for cFE Performance Monitor APIs
– CFE_ES_PerfLogEntry - Entry marker for use with Software Performance Analysis Tool.
– CFE_ES_PerfLogExit - Exit marker for use with Software Performance Analysis Tool.
– CFE_ES_PerfLogAdd - Function called by CFE_ES_PerfLogEntry and CFE_ES_PerfLogExit macros.
Describe alternatives you've considered
N/A
Additional context
N/A
Requester Info
Alex Campbell GSFC

duplicate of #812


Send heartbeat OPTIONS message less frequent and enable keep alive

Now we are sending OPTIONS message on every connection every 5 seconds.
This PR changes that to 30 seconds (this is the number used in python-driver - https://github.com/scylladb/python-driver/blob/7cdc1ca25ffa2194a0772e46ccd89645f8514c1b/cassandra/cluster.py#L893) and enables the keepalive - with 15s by default (matches Golang's default).
Fixes: #162

If we have TCP keepalive, why do we need the application level OPTIONS as well? (and vice versa of course).

Should the fix be sent to https://github.com/gocql/gocql first?

Should the fix be sent to https://github.com/gocql/gocql first?

Not sure about that. It looks like the upstream is not actively maintained, and this change is not something that might make merging upstream difficult in the future.

Should the fix be sent to https://github.com/gocql/gocql first?

Not sure about that. It looks like the upstream is not actively maintained, and this change is not something that might make merging upstream difficult in the future.

I agree.
Normally, such general changes are better to go first to the upstream and then get them during the upstream merge, but in the current situation of upstream it can wait there unnoticed for months.

@avelanarius could you review it?


String API and Translation API

Implemented the String API and Translation API (#74)

Wow, it’s looking great! I will pull that in tomorrow.
The only thing I’d like to change is the String class: it overwrites Ruby’s String class implementation. This rubygem is used by some apps on production, so it would probably be safer to rename this class into something else (right off the bat I’m thinking about Segment, StringKey...)
Thanks a lot for all the work, I really appreciate it! :thumbsup:

Cool - although WebTranslateIt::String is namespaced under the WebTranslateIt module, so it shouldn't conflict.  If you're inside the WebTranslateIt module and you reference String, you'll get WebTranslateIt::String.  If you wanted to access Ruby's String class, you can still use ::String.
But yeah, feel free to change the name if you think it'll be less confusing / less scary :)

Oh yes, you’re right, I forgot about the WebTranslateIt namespace.


Can this driver support Stored Procedure？

I tried several times, une excute method to execute a stored procedure with in parameters can success, but when there's a out/inout parameters will error: data type Error translation

Yes, use sql.Out, like in the example below.
https://godoc.org/github.com/mattn/go-oci8#example-package--SqlFunction

@loraxh All good? If so, please close this issue.

thank you!


HDDS-9830. OzoneManager - isDBUpdateSuccess flag not being set at OM client causes incorrect behaviour at Recon and failed to Recover in case of rocksDB exception.

What changes were proposed in this pull request?
This PR fixes the isDBUpdateSuccess flag being set at OzoneManger's org.apache.hadoop.ozone.om.OzoneManager#getDBUpdates API. This flag was being set at server side, but was not set at client layer in org.apache.hadoop.ozone.om.protocolPB.OzoneManagerProtocolClientSideTranslatorPB#getDBUpdates. Because of this, Recon didn't knkow about any DB updates failure at OM side and Recon was not able to recover by falling back on full snapshot OM DB update.
One of the prominent use case found for OM DB update failure is the mis-match in sequence number between Recon OM
snapshot DB and OzoneManager OM active DB.
Since Recon sync with OM DB every 5-10 mins based on configured interval and if Recon OM snapshot DB  has higher sequence number than OM active DB last sequence number, then OM DB updates call since last sequence number will fail as OM DB will not know about that sequence number which is not yet written to OM Rocks DB. In such case OM sets the 'isDBUpdateSuccess' flag as false, but because the client layer at OM side was not setting this flag, Recon never gets the correct status of getDBUpdates API call. Once isDBUpdateSuccess flag received as false by Recon, Recon should fall back on full snapshot and recover itself.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9830
How was this patch tested?
This patch is tested by writing an integration test where the test has increased the lastSequenceNumber intentionally for OM DB snapshot DB at Recon and making syncOMDB call to simulate the mis-match in sequence number between Recon OM
snapshot DB and OzoneManager OM active DB.

@sumitagrawl @dombizita  Pls review.

Thanks @devmadhuu for the fix, @sumitagrawl for the review.


chore(core): patch state should be partial

use typescript "Partial" type for patchState method

Whoa, didn't know about this!


Added all RTT(round trip time) to the file option.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.15%. Comparing base (a8e5390) to head (ebb71b8).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #326   +/-   ##
=======================================
  Coverage   97.15%   97.15%
=======================================
  Files         152      152
  Lines        9160     9160
=======================================
  Hits         8899     8899
  Misses        261      261


[WIP] Centralize Logger

Description
This PR seeks to create a simplified method for managing logging for the Llama Index package. The implementation should embrace Python best practices to ensure integration with the greater Python ecosystem.
This PR is focused only on implementations of the Python logging library. Notably, it does not address:

Tracing, which requires unique integration with other tools.
Existing print() statements. These are often used with the verbose flag and thus have a different lifecycle than application logging. This behavior could be unified with the logging pipeline, but should addressed in an isolated project.

Developer Interaction
A developer sets the logging level for the package with the following line:
logging.getLogger("llama_index").setLevel(logging.DEBUG)

The logger can also be configured using configuration files.
Problem
There are currently >100 distinct loggers within the package.
loggers = [logging.getLogger(name) for name in logging.root.manager.loggerDict]
for l in loggers:
    if "llama_index" in l.name:
        print(l.name)

The following line is repeated in many files. Each invocation creates a new logger, named after the file where it lives. The most likely explanation for this repeated code is "copy pasta"; simply replicating an existing pattern in a new file.
logger = logging.getLogger(__name__)

To ensure reliable logging configuration, a developer must set configuration for every logger.
Solution
Llama Index should have a single logger that is used across the entire project.

Define logger in llama_index/logger/__init__.py. Placing in this directory seeks to avoid circular imports. All package scoped logging configuration should be done in this file.
Use with a simple import statement. from llama_index.logging import logger

Fixes #9450
Type of Change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[ ] I stared at the code and made sure it makes sense

Suggested Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I ran make format; make lint to appease the lint gods

@logan-markewich can you review the proposed approach for logging changes? This would require updating >100 files; so I'd like to ensure we're aligned before creating a large PR.

@aaronbannin thank you!!
I should be able to review this by tomorrow at the latest

@aaronbannin I agree with the rational and proposal. Would love to see
a) unified logger
b) slightly more helpful logs, especially debug logs (likely done in another PR though)

@logan-markewich marked as ready to review

This looks good to me.
I tested in a script using
from llama_index.logger import logger
import logging
import sys

logger.handlers.clear()
handler = logging.StreamHandler(sys.stdout)
handler.setFormatter(
    logging.Formatter("%(asctime)s %(levelname)s %(funcName)s %(message)s")
)
logger.addHandler(handler)
logger.setLevel(logging.DEBUG)

Do you think it would be useful to provide some default logger helper function?
And either way, we should also add this to the docs somewhere (maybe in the starter example? Or wherever we explain logging)

Hi there, any updates on this?

Going to close this one out for now, its quite outdated at this point
If its still an issue, please raise an updated PR
Sorry for letting this one sit for so long!


[BUG] TypeError on SlashCommand Option Definition

Library Version
5.11.0
Describe the Bug
While attempting to define options for a slash command using the interactions.py library, I encountered a TypeError. The error occurs when adding options to the @slash_command decorator: the library seems to expect a sorted list of options but receives a function object instead, leading to the error 'function' object is not subscriptable.
Steps to Reproduce

Define a new slash_command with options using the interactions.py library.
Use the Option object to define the options for the command.
Attempt to run the bot and register the command with Discord.

Expected Results
The slash command with its options should be successfully defined, and the bot should start without any TypeError.
Minimal Reproducible Code
import os
from interactions import Client, Intents, slash_command, slash_option, OptionType, SlashCommandChoice

intents = Intents.DEFAULT | Intents.GUILD_MEMBERS | Intents.GUILD_MESSAGES
bot = Client(token=os.environ['TOKEN'], intents=intents)

@slash_command(
    name="role",
    description="Add or Remove a role from a member.",
    options=[
        slash_option(
            opt_type=OptionType.STRING,
            name="action",
            description="add or remove",
            required=True,
            choices=[
                SlashCommandChoice(name="add", value="add"),
                SlashCommandChoice(name="remove", value="remove")
            ],
        ),
        slash_option(
            opt_type=OptionType.STRING,
            name="role_name",
            description="The role's name",
            required=True,
        ),
        slash_option(
            opt_type=OptionType.USER,
            name="member",
            description="Member to add or remove a role from",
            required=True,
        )
    ]
)
async def role(ctx: SlashContext, action: str, role_name: str, member: Member):
    pass

bot.start()

Traceback
Traceback (most recent call last):
  File "/home/runner/Discord-interactionspy/main.py", line 128, in <module>
    async def role(ctx: SlashContext, action: str, role_name: str, member: Member):
  File "/home/runner/Discord-interactionspy/.pythonlibs/lib/python3.10/site-packages/interactions/models/internal/application_commands.py", line 958, in wrapper
    cmd = SlashCommand(
  File "<attrs generated init interactions.models.internal.application_commands.SlashCommand>", line 46, in __init__
  File "/home/runner/Discord-interactionspy/.pythonlibs/lib/python3.10/site-packages/interactions/models/internal/application_commands.py", line 717, in options_validator
    if value != sorted(
  File "/home/runner/Discord-interactionspy/.pythonlibs/lib/python3.10/site-packages/interactions/models/internal/application_commands.py", line 719, in <lambda>
    key=lambda x: x.required if isinstance(x, SlashCommandOption) else x["required"],
TypeError: 'function' object is not subscriptable

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.
[X] I have attempted to debug this myself, and I believe this issue is with the library

Additional Information
No response

Hello - please take a look at the guide for slash commands to see proper usage of slash_option - essentially, it's not like this.


In Livewire customContainer not taking effect

Hi everyone,
Composer.json:
"laravel/framework": "^8.83.16",
"livewire/livewire": "^2.5",
"victorybiz/laravel-tel-input": "^1.2"
Package.json:
"intl-tel-input": "^17.0.16",
I have installed package properly, but when I tried to use customContainer, it wrapped with span tag (wire:ignore)
Please help me out, whether there is another way or am I missing some configuration

I have the same issue, and is likely the cause of https://github.com/victorybiz/laravel-tel-input/issues/23
Did you happen to solve this?

@MCKLtech  no, issue still persist. I used different way, dead-lines coming :)

The problem was in the config file for the utilsScript key
You should download the utilities script and put the path in the config

script used : https://cdnjs.cloudflare.com/ajax/libs/intl-tel-input/21.2.7/js/utils.min.js
and it will work correctly


jsdom config file

I'm having trouble with a test where I need the clientWidth within a component. But the test drops an error, with clientWidth undefined. Researching I found out that maybe configuring the jsdom config file might fix the error. But I'm struggling where to create or put the jsdom config.

Tried to put the jsdom inside the component.test.js like this:
import jsdom from 'jsdom';
const doc = jsdom.jsdom('<!doctype html>'); global.document = doc; global.window = doc.defaultView;
But it doesn't work.

@BrandoIsNotASword Why closed, did you find a solution you could share?

@gihrig sorry my bad; I haven't found any solution.

Have you got a sample of the code that is failing in your test?
Possible solution
With Jest you can specify setupFiles, which is kind of similar to the setupTestFrameworkScriptFile option specified in package.json, except it accepts an array (e.g. "setupFiles": ["/internals/testing/setupFiles.js"]) Note: this file doesn't exist in this repo, you will have to create it.
Then in setupFiles.js you can "setup" you test environment to mock/fake the parts that your code has a dependency on. As an example, if your code is using window.innerWidth, then putting something like the following into  setupFiles.js should prevent your tests from failing:
window.innerWidth= window.innerWidth || 320

Would love to hear how you go.

Closing this issue now, if you still have the issue, please open a new issue with some code samples. This will greatly make it much easy for others to help resolve the issue.


Getting LetsEncrypt to work with Dock container

Hello,
I have just installed Umbrella on my VPS server in a Docker container via:
https://api-umbrella.readthedocs.io/en/latest/getting-started.html#running-with-docker
and now I want to add a LetEncrypt Cert on the server so that it will allow for HTTPS to my api subdomain which talks to the Umbrella docker container.
I was trying to follow:
https://api-umbrella.readthedocs.io/en/latest/server/https-config.html
but am not clear how to make this happen.
could please give me a bit of guidance on this, if possible so that I can get it setup and running cleanly.
Thanks in advance

This is what works for me... If you use the docker images jwilder/nginx-proxy:latest and jrcs/letsencrypt-nginx-proxy-companion:latest to add a host to nginx and letsencrypt. Once you have them running in docker add the environment variables of VIRTUAL_HOST: your.domain.com, LETSENCRYPT_HOST: your.domain.com and LETSENCRYPT_EMAIL<EMAIL_ADDRESS>and it should be running. You can find jwilder/nginx-proxy on github (code and documentation) and hub.docker.com.
I've all but given up with API-Umbrella due to the same issue here API Umbrella CORS options issue solving. Hope you have better luck.


Support alternative testing frameworks such as Ava

From @kristianmandrup on March 17, 2017 20:39
Which test frameworks are currently supported? Please specify.
I'd like to use ava
Would just require support for async/await for Time.run() I think?
Thanks.
// Ava test
test('Counter', async t => {
  const Time = mockTimeSource();

  Time.assertEqual(count$, expectedCount$)

  await Time.run();
});

In the code for time-driver.js, I see the following
_runVirtually: function (done, timeToRunTo) so it looks like it currently requires a done callback argument for proper async
But then I also see time-source where the cb argument is optional
export interface MockTimeSource extends TimeSource {
  // ...
  run (cb?: (err?: Error) => void): void;
}

Copied from original issue: cyclejs/time#21

@staltz Time.run() is asynchronous, just really fast!
My proposed solution to this is to return a promise from Time.run(), along with supporting callback style.
That would support Ava and a few other common frameworks.
We should also clearly document which testing frameworks are supported.

From @staltz on March 17, 2017 22:12
I think Time.run() is synchronous, so you could drop the async/await. Give it a try

From @kristianmandrup on March 20, 2017 7:59
Thanks guys. It worked for me as shown above. I also created a small DSL for using RxJS marble testing with Ava.

After having a crack at implementing this, my only concern is that the usage would look like:
Time.run().then(success, fail);

Currently Time.run() will default to raising errors if no callback is passed. This is to prevent users forgetting to pass a callback and then having tests silently fail. In the above scenario, if the test fails, an error would be raised but fail would never be called.
So for this to work, we would need to make a breaking change such that Time.run() will no longer throw an error by default. This is probably fine for tests, as your test will timeout in this scenario anyway.
Another option is to make another run method that returns a promise.
My current preference is to bite the bullet and make this breaking change, but if anyone has feedback or ideas I'd like to hear it.

From @jvanbruegge on March 28, 2017 5:17
I will have to wrap Time.run() in a Promise anyway, so if for it

From @mightyiam on April 3, 2017 9:4
Regardless of what the API is or should be, why should this library have to support any testing framework specifically?
And AVA can work with callback-based APIs, as well.

From @mightyiam on April 3, 2017 9:9
Regarding the API choice, what I see in the scene is promise-based APIs replacing callback-based APIs. With such small user base, why should we keep the callback API?

From @jvanbruegge on April 3, 2017 9:5
No it should not, but having the choice about API type (callback or promise) is best, see #27

From @jvanbruegge on April 3, 2017 9:10
It does not hurt, because the Promise is just wrapping the callback anyway we don't have code duplication

From @staltz on April 3, 2017 11:56
:(
Callbacks are supported everywhere.
Have you considered Tape users?

I now realized Mocha supports promise style tests as well, which is nice.
I'm generally in favor of dropping callbacks and replacing them with promises.

From @mightyiam on April 3, 2017 12:5
Is Tape allergic to promises?

Okay, I've been thinking about this a fair bit. My biggest concern with some of the proposed solutions are around providing APIs that allow users to write tests that silently fail or don't run.
For example, if we change Time.run() to not blow up by default when a user does not pass a callback, there are two different cases where this could go wrong.
When using callback style, if the user forgets to take in the done callback and pass it to Time.run.
it('fails silently because the user forgot to take done and pass it in', () => {
  const Time = mockTimeSource();

  Time.assertEqual(
    Time.diagram('---a----b---c---'),
    Time.diagram('---x----y---z---')
  );

  Time.run();
});

Alternatively, if you are using the promise style, if you forget to return the promise the test will fail silently.
This also makes me think about another pattern I have been using. I dislike having to make a Time instance and call run in every test, so I have been writing tests like this:
it('is fun to write tests with less boilerplate', withTime(Time => {
  Time.assertEqual(
    Time.diagram('---a----b---c---'),
    Time.diagram('---x----y---z---')
  );
}));

Where the withTime helper is defined like this (for callback style tests):
function withTime (test) {
  return function (done) {
    const Time = mockTimeSource();

    test(Time);

    Time.run(done);
  }
}

We could also make a promise style withTime:
function withTime (test) {
  return function () {
    const Time = mockTimeSource();

    test(Time);

    return promisify(Time.run);
  }
}

My proposal is that instead of adding direct promise support, we instead add these helpers, probably two different ones (one for callback style, one for promise style).
This cuts down on potential user error, and removes boilerplate from the tests.
What do y'all think? Any objections to this approach? Can anyone think of a better name than withTime?
I would ensure that it supports:

Mocha
Jest
Karma
Tape
Ava

From @jvanbruegge on April 3, 2017 12:20
@mightyiam https://github.com/substack/tape/issues/262#issuecomment-185911279

Thinking about it more, we could perhaps only have one version that handles both styles automagically. I'll have a play and see if any of the above frameworks get upset if you both attempt to take a callback and return a promise.

From @jvanbruegge on April 17, 2017 14:55
I just tested that approach and it works quite good for me:
it('should interact correctly', () => {
    const property = forall(diagramArbitrary, diagramArbitrary, (addDiagram, subtractDiagram) => withTime(Time => {
        const add$ : Stream<any> = Time.diagram(addDiagram);
        const subtract$ : Stream<any> = Time.diagram(subtractDiagram);

        const DOM = mockDOMSource({
            '.add': { click: add$ },
            '.subtract': { click: subtract$ }
        });

        const app = onionify(App)({ DOM } as any);
        const html$ = app.DOM.map(toHtml);

        const expected$ = xs.merge(add$.mapTo(+1), subtract$.mapTo(-1))
            .fold((acc, curr) => acc + curr, 0)
            .map(expectedHTML);

        Time.assertEqual(html$, expected$, htmlLooksLike);
    }));

    return assert(property, testOptions);
});

(this is using the promise version)

From @mightyiam on April 17, 2017 19:54
@Widdershin thank you for investigating. Perhaps authors of said frameworks would be kind to advise if you mention them.

@issuehuntfest has funded $20.00 to this issue. See it on IssueHunt


Drop-down button different color then regular buttons

In workloads:
Look at buttons colors.  Then go to storage and look at background color of Add Volume combo button/drop-down.  Also the buttons inside blocks.

Results:
Should these look the same?

Verified with master-head, commit id 5da52c0
In dashboard UI, buttons in all the pages for crating deployment, daemonsets, and adding volume buttons and other resource such as networking, node scheduling, pod scheduling and anoation are consistent with the same text and background color.


Nevigate to FAQs

PROBLEM IN NAVIGATE TO FAQs
First go to Hactoberfest.. now you are in Hactoberfest section.. now click on FAQs.. you scrolled down to the follwing image.. But its not FAQs section...
Need to Fix it..

/assign

@jalaym825 The problem is that there is separte rout "/hacktoberfest2024" for the Hactoberfest details.. and when we are in this and click on FAQs.. its redirect to Home Page and Dont shw FAQs section..
Second Problem is that after clicking FAQs when we are in Hactoberfest section... that mini-nvarbar  is also disappear becausewe redirect to Home Page by Selecting FAQs..

Solution is that we have to display Hactoberfest details in HomePage.. No Need for navigate('/hacktoberfest2024');

@soni-shashan And In that mini-navbar... user maybe think that Home icon is for Home page..(redirect to Home Page).. but actually its not for Home page.. its for to scrollUp in only when we are hactoberfest section.. need to fix it..
Solution: We should Remove this Home icon. Because in Navbar there is option for Home Page.. and In hactoberfest section for scrollingUp we simply put Upward error.. inplace of this Home Icon..

replaced with hacktoberfest icon


consider merging with jshint-rb

I'm trying to start maintaining a fork of jshint_on_rails at https://github.com/josephholsten/jshint.rb
I'm not really attached to the implementation, I'd just like to make sure there is at least one well-maintained jshint to ruby adapter.

discussion moved to https://github.com/stereobooster/jshintrb/issues/19


remove the icon in dock

Describe the bug
Right-click and uncheck the "show in dock" cannot remove the icon in dock. And if I quit and reopen the app, the "show in dock" menu item will be checked again, so It won't remember my decision.
Screenshots

Desktop (please complete the following information):
macOS 10.15.4
Version 1.5.1
Additional context
Am I doing it wrong?

@max-yeah You didn't do anything wrong. The option is confusing.
"Show in Dock" should be renamed to "Show timer badge in Dock".
See https://github.com/michaelvillar/timer-app/pull/42

I see. Thank you.


Invalid message sender specified

Searching for a user's message in a group: why invalid?

You can use only user IDs, which you received from TDLib after restart. See https://github.com/tdlib/td/issues/578 for more details.

@levlam In my code, the id comes from the sender of the message I just received, so I don't think this should be the case.

Where from did you get the user ID?

@levlam (Message.sender as MessafeSenderUser).id

Could you send TDLib's log with verbosity level 4 to @tdlib_bot in Telegram?

Sorry, I cannot reproduce the error.


AQL query editor should enable profiling

The AQL query editor in the web interface shows the overall query execution time for each executed query.
This is good as a start, but it should be more detailed and explained.
On the server side, the overall time can be broken up into individual components (e.g. "parsing", "optimizing" etc.). In order to do this, the client can send the "profile" options when issuing the query, e.g.
curl -X POST http://<IP_ADDRESS>:8529/_api/cursor --data '{"query":"FOR i IN 1..100 RETURN i","options":{"profile":true}}'

The server response will then contain detailed execution times in the profile attribute in addition to the executionTime attribute:
"profile":{"initializing":1.2874603271484375e-5,"parsing":1.0704994201660156e-4,"optimizing ast":9.059906005859375e-6,"instantiating plan":8.702278137207031e-5,"optimizing plan":3.159046173095703e-4,"executing":2.689361572265625e-4}

The web interface could always request profiled queries, and display the detailed execution times on demand. It should hide them by default because in many situations they will be just noise to the user, but for power users they may be interesting.
Additionally there should be some explanation what the execution times mean (e.g. server-side execution times, not including network time, which may be significant from the client perspective). So please add some explanation somewhere (e.g. using a tooltip or something similar that is not obstructive).

Maybe something like this?

@Simran-B : looks good to me!

Can we please change the timing to ms? Queries should exec in ms not secs ;)

ArangoDB 3.1 has been released. Please note that the download urls and repositories have changed slightly.
Download or see Release Notes for details.


Use Identity package reference

The fact that net - client - ci is showing yellow here even though it's already passed is not blocking. I'm OK with us merging this.


DCOS-20332: DSL show dropdown on focus

Checklist

[ ] Did you add a JIRA issue in a commit message or as part of the branch name?
[ ] Did you add new unit tests?
[ ] Did you add new integration tests?
[ ] If this is a regression, did you write a test to catch this in the future?

Alfred test this

Run integration tests

I like these changes a lot, it gives the user a way better experience. For me, this change leveled up the user interaction here, therefore I became a bit more critical:
I think it is super neat that changes in the textbox automatically reflect in the dropdown, but on the same note having to press "apply" after changes in the dropdown feels a bit weird. Can you make a new story out of this or fix it if it is super quick? Maybe it is also planned like this, @leemunroe can you tell me more here? (You are the right person to ping for UX issues, right?)
This gif shows the problem in detail:

Yes, great idea @DanielMSchmidt there is a PR for that => https://github.com/dcos/dcos-ui/pull/2703


Issue 27

Added support for extensions other than *.html to generator:

during manual project setup
when adding pages
when loading configuration from .yo-rc.json file

Updated documentation to include this functionality description and additionally some live reloading tips.

Error most probably caused by weird, usually invisible files in WordPress archive. I will work on fixing that (most probably by rewriting xh:wp generator not to use yeoman helpers and see where to go from there).
To replicate in local environment one must clear yeoman cache first (so that it doesn't have WP already downloaded & unpacked). Running tests second time (without clearing cache) makes them pass.


404 error with wildcard routes

In my now.json , i set my routes as
{
"builds": [
    {
      "src": "pages/*/index.js",
      "use": "@now/node"
    },
"routes": [
  { "src": "/admin*", "dest": "pages/admin/index.js" }
]
}

Now all the /admin* routes return 404 error.

The correct wildcard is { "src": "/admin(.*)", "dest": "pages/admin/index.js" }


Beta Testing

I am looking for alpha and beta testers for the first release of the extension. If you are interested in trying out the extension and influencing future development, add a comment to this issue and I will get in touch.

Closing this issue. The extension has over 2500 downloads, so it is being tested :)


Using separate notify url and return url

It's often the case that we want an IPN to be processed using a differnet url (route) than the URL which the user returns to after completing a payment.

I'm getting failures on the travis build with this PR.

OK I have noticed that this PR has been made obsolete by #13 so I'll process that instead and close this.


Give metric attributes unique names

Summary
From experimentation, it seems that attributes of the same name in
different metrics are shared. This leads to, for example, alert status
types showing up in the remediation graph.
Change Type
Mark the type of change your PR introduces:

[x] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[ ] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 52.769%. remained the same
when pulling aebd51363f264ddba8063db06e8334c149912c9e on time-profile-evaluation
into a37860e15c625de76a56b0fd793580cb1a46e49e on main.


HHH-17579 fix classloader issues with JAXBContext since JDK11

Fixes https://hibernate.atlassian.net/browse/HHH-17579
Tested OK against the https://github.com/laurentschoelens/hibernate-orm-xml-java11 repository

Hi @beikov,
Could you please check this PR associated with the following issue : https://hibernate.atlassian.net/browse/HHH-17579 ?
Thanks 😄

@gavinking : sorry to point out this PR but this is waiting for long without any notice if I'm doing something wrong about this one and you were working some days ago on modified file.
Just rebased from main to get latest modifications 😄
Thanks for the help and review of this blocking issue

I mean, the pull request has no test.

I mean, the pull request has no test.

Thanks for the reply. I've tested it against this repository by building and testing against latest build. Since it's designed to be run inside build env, I don't know pretty much how to add unit tests to it. If possible, could you guide me please so I can add it ?

The tests for jpamodelgen are in: tooling/metamodel-generator/src/test. There's lots of examples, some of which use orm.xml mappings.

I've just tried to add a unit test and it's passing in both scenario.
But by building main current branch and re-running the sample above, I still get the following output
[INFO] --- compiler:3.11.0:compile (default-compile) @ hibernate-orm-xml-java11 ---
[INFO] Changes detected - recompiling the module! :source
[INFO] Compiling 2 source files with javac [debug target 11] to target/classes
[INFO] Hibernate compile-time tooling 6.5.0-SNAPSHOT
[WARNING] Unable to parse /META-INF/shared/orm.xml: Unable to perform unmarshalling at line number 0 and column 0. Message: null
[WARNING] The following options were not recognized by any processor: '[ormXml]'

and the target/generated-sources/annotations directory is empty

If again I build my patched branch (with this PR), I get the following output and result is OK :
[INFO] --- compiler:3.11.0:compile (default-compile) @ hibernate-orm-xml-java11 ---
[INFO] Changes detected - recompiling the module! :source
[INFO] Compiling 2 source files with javac [debug target 11] to target/classes
[INFO] Hibernate compile-time tooling 6.5.0-SNAPSHOT
[WARNING] The following options were not recognized by any processor: '[ormXml]'

With BaseEntity_ file content as follow :
@StaticMetamodel(BaseEntity.class)
@Generated("org.hibernate.processor.HibernateProcessor")
public abstract class BaseEntity_ {

	public static volatile SingularAttribute<BaseEntity, String> lastModifiedBy;
	public static volatile SingularAttribute<BaseEntity, String> createdBy;

	public static final String LAST_MODIFIED_BY = "lastModifiedBy";
	public static final String CREATED_BY = "createdBy";

}

Just forced-pushed with extra unit test (but not representative of the current issue in fact since not run with same condition as actual issue)

The following options were not recognized by any processor: '[ormXml]'

This is extremely 'sus, since HibernateProcessor certainly specifies that ormXml in @SupportedOptions.

Yes I've never understood this warning message but it works with patched version so I've never dug more on this 😄

OK, that now looks a lot more reasonable.
One more question: is the new test actually testing anything new, or is it just a dupe of tests we already have?

OK, that now looks a lot more reasonable.
One more question: is the new test actually testing anything new, or is it just a dupe of tests we already have?

As I said, it's passing before and after the PR (since it's not executed in the same context). That's why I didn't brought any test in the first place.

I can delete it if you think it's useless 😄 (which it is in my opinion)

Well, yeah, if it's not demonstrating the bug.

I can delete it if you think it's useless 😄 (which it is in my opinion)

Well, yeah, if it's not demonstrating the bug.

Done 😉

@beikov and @gavinking could you re-review please ?

Thanks

Many thanks to both of you 👍
Did this could have any chance to be backported in latest 5.x ? Users are locked on jdk8 due do this...

Sorry, but we only backport critical bug fixes at this point. Read more about this on the 5.6 release page or the maintenance policy page.

I trully understand your answer, keeping old version could be quite painful and this may be considered not critical enough for core-team but it is if using this feature and wanting to keep on javax version of hibernate but go on JDK11 or JDK17.
Maybe it could have been backported to be included in the next critical-fix-release ?

If you are a Red Hat customer, then you can request a backport through support channels. The maintenance policy is quite clear, so if you want to stick to community releases, you will have to upgrade to the latest versions.


[bugfix] Fix variable and parameter access as class attributes

This PR fixes a bug that was causing variables and parameters set as class attributes to be silently overridden. Bug reproducer:
class Base(rfm.RegressionTest):
    ...
    p = parameter([1])
    v = variable(int, value=1)

Base.p = [2] # This PR will disallow updating parameters like this.
Base.v = 2

@rfm.simple_test
class Derived(Base):
    def __init__(self):
        print(self.p) # Prints 1
        print(self.v) # Prints 1. With this PR this prints 2.

This PR disables setting/updating parameters when accessed as class attributes. This is because such parameter update would break the internal iterators on the parameter space. If this feature is required, explicit insert_parameter or update_parameter class methods could be added.
This might be needed by #563

Codecov Report

Merging #1988 (67af0ea) into master (4319345) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1988      +/-   ##
==========================================
+ Coverage   87.59%   87.61%   +0.02%
==========================================
  Files          50       50
  Lines        8770     8788      +18
==========================================
+ Hits         7682     7700      +18
  Misses       1088     1088

Impacted Files
Coverage Δ

reframe/core/meta.py
100.00% <100.00%> (ø)

reframe/core/variables.py
96.03% <100.00%> (-0.02%)
:arrow_down:

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 4319345...67af0ea. Read the comment docs.


Text in buttons in center

Version: 1.0.1
Why text on buttons is not centered by default? I think centered text is using everywhere.

Version: 1.0.1
Why text on buttons is not centered by default? I think centered text is using everywhere.


Cannot access my project

Hello,
I have a project:
https://pypi.org/project/robomax/
I am unable to access the project the maintainer has left.
I need to have access to it or have it deleted so I can reinstall it.
Please help?

Please file a PEP 541 request here: https://github.com/pypa/pypi-support/issues


Make it more difficult to accidentally invalidate all active tokens

Same mechanism as is in the single token activation/invalidation, perhaps?


[suggestion] Deprecate the GG20 Library

Based on the following comment from [0] and the "obsolescence" of the GG20 paper I think it would make sense to "deprecate" the tecdsa/gg20 package so that new implementations or those which already rely on this code are aware of the risks of this protocol.
This should be possible via the following godoc declaration: https://rakyll.org/deprecated/

On the other hand, the authors of that paper appear to have declared it "obsolete". In light of this declaration, we cannot attest,
given the information we currently have, that the protocol implemented here is secure. We advise caution regarding its use.

[0] https://github.com/coinbase/kryptology/blob/master/pkg/tecdsa/gg20/SECURITY.md

@brendanjryan Good day Brendan Ryan
Can you help with a few questions about this issue?

Can you advise new implementations that fix this error?
Can they be used in the production?

@brendanjryan Good day Brendan Ryan
Can you help with a few questions about this issue?

Can you advise new implementations that fix this error?
Can they be used in the production?

Sure -- thanks for flagging @vanillahedg

I cannot, per [0] these changes would need to occur at the algorithm design level and are not related to implementation.
Defer to ^

On the other hand, the authors of that paper appear to have declared it "obsolete". In light of this declaration, we cannot attest, given the information we currently have, that the protocol implemented here is secure. We advise caution regarding its use.

Thank you very much for your answer.


✨ Please set up recurring sponsorship

🔖 Feature description
I would like to support the project on an ongoing basis, and I recommend setting up a Patreon for the project (and github sponsors if you so wish)
My full-time income (I'm a YouTuber) is based on advanced slides, and while I am saddened that @MSzturc is not developing advanced slides publicly any more (Matt, thank you for your incredible work), I am relieved there is a fork to rally behind.
✔ Solution
Set up both patreon and gh sponsors, my professional recommendation of the monthly price of the tiers is:

$2
$5
$10
$50

(the seemingly-unrealistic high tier is not too high for some people, and you want to let them support you)
❓ Alternatives
https://ko-fi is fine too, but lacks the brand awareness of patreon and gh sponsors, but if you're feeling energetic, you may set that up too.
📝 Additional Context
Thank you again for re-energising this project!

I use Buy Me a Coffee: https://buymeacoffee.com/ebullient
Patreon is more work for me than I'm interested in dealing with.
I did set up your recommended membership tiers. I did not expect anyone to be interested. 🥰

Super! Thank you so much again, I've subscribed on BMAC - perfect! :heart:


Duplicated lumis on ACDC server?

Hi guys,
As I explained here https://its.cern.ch/jira/browse/CMSCOMPPR-137, we have a MonteCarlo workflow that overproduced events by a large number. The workflow only had one ACDC round.
Looking into this https://cmsweb.cern.ch/couchdb/acdcserver/_design/ACDC/_view/byCollectionName?key="pdmvserv_SUS-RunIISpring16FSPremix-00055_00034_v0__160929_122033_2363"&include_docs=true&reduce=false
we can see there is something rare with the lumis to be recovered.
Could you please help us to understand why the lumis are duplicated in the acdc server?
Thanks.

Hi Paola, I was having a look at this workflow and honestly... I have no clue at all how that happened. It seems we got more than 20 entries for MCFakeFile-pdmvserv_SUS-RunIISpring16FSPremix-00055_00034_v0__160929_122033_2363-Production-fa3a91bc780de492218c2fe34047a1c3 with the full runLumi mask (31k lumi sections).
It will probably require deep debugging - and provided I have a few other nasty issues in my hands right now - could you please leave this request in completed status and clone/run another workflow (<3k jobs, it's faster if you run a clone than wait for me).

I unfortunately rejected that wf.

I managed to get some info though. I was following the ErrorHandler algorithm and these are my notes.
There are 133 jobs in failed status for fileset_name /pdmvserv_SUS-RunIISpring16FSPremix-00055_00034_v0__160929_122033_2363/Production.
Somehow, 22 jobs don't have a valid jobMask, so instead of
{'LastRun': 1, 'FirstRun': 1, 'inclusivemask': True, 'runAndLumis': {1: [[36767, 36798]]}, 'LastEvent': 16175250, 'FirstEvent': 16161623, 'LastLumi': 36798, 'FirstLumi': 36767}
they have
{'LastRun': None, 'FirstRun': None, 'inclusivemask': True, 'runAndLumis': {}, 'LastEvent': None, 'FirstEvent': None, 'LastLumi': None, 'FirstLumi': None}
which matches exactly to the number of docs in the ACDC server with 31k lumi sections!!!
Then following the ACDC internals, these were all the jobs passed upstream:
http://amaltaro.web.cern.ch/amaltaro/forAlan/jobs_mask
which then falls into this code:
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/ACDC/DataCollectionService.py#L104
and finally this one:
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/ACDC/CouchFileset.py#L97
then since mask has only null values, this mask.getRunAndLumis() returns {}, thus runs key is untouched.
Now two things that I don't understand yet are:

why those jobs have no mask valid information?
job['input_files'] is empty for all those jobs. So where does it get the files from??

We probably care only about the invalid mask information though... (now that the workflow is rejected, this info is probably vanishing from the agent very soon)

and this is the call we use to load the mask given a jobid:
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMBS/Mask.py#L116
Since I could not find any problems in the code and all the info is gone from wmbs, I'm closing this ticket.
Paola, Jean-Roch, please reopen it if the same issue happens again.

Thanks Alan.


Export types for the objects returned from making requests

The export of types of the objects returned when making requests would be incredibly useful. This would significantly enhance the developer experience by:

preventing incorrect key accesses
and other invalid operations on the type of an object or value inside the object
enhancing IDE intellisense
integration with linters and static type checkers

I guess you could implement this manually, though it would be amazing if the Slack API did this for you.
Category (place an x in each of the [ ])

[x] slack_sdk.web.WebClient (sync/async) (Web API client)
[ ] slack_sdk.webhook.WebhookClient (sync/async) (Incoming Webhook, response_url sender)
[ ] slack_sdk.models (UI component builders)
[ ] slack_sdk.oauth (OAuth Flow Utilities)
[ ] slack_sdk.socket_mode (Socket Mode client)
[ ] slack_sdk.audit_logs (Audit Logs API client)
[ ] slack_sdk.scim (SCIM API client)
[ ] slack_sdk.rtm (RTM client)
[ ] slack_sdk.signature (Request Signature Verifier)

Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Hi @intercepted16, thanks for the suggestion!
Indeed, enhancing the response data types would be greatly helpful for developers. However, the Slack API does not provide open API specs or something similar, so manually crafting response types could be challenging (considering our team capacity and priorities).
I'll keep this issue open for receiving feedback from others; however, we won't be able to take action in the foreseeable future. It'd be appreciated if you could understand this.


Link and Path fields added

Reference Issues/PRs
#99
What does this implement/fix? Explain your changes.
Since we need to know what's the link of uploaded art in the nft storage we decided to return the link to the art in the when using nft_storage_upload method.
Same issue when saving a config/data/art file.

I think message field is necessary in some cases in which we return error message in message field and these error messages can not be in the link/path field.


feat(vue-app): forward custom props from <nuxt> to the page component

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

The following will apply a foo class to the route's root element:
<nuxt class="foo" />

However, if the page's component declares props, it is not possible to pass them along:
<nuxt my-prop="foo" />

It does work if we use <nuxt-child> directly from within the the layout, but then we loose the error handling logic.
<nuxt-child my-prop="foo" />

This change allows defining page props through the <nuxt> component.
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

Codecov Report

Merging #9858 (9981f78) into dev (034b990) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #9858   +/-   ##
=======================================
  Coverage   65.15%   65.15%
=======================================
  Files          94       94
  Lines        4110     4110
  Branches     1127     1127
=======================================
  Hits         2678     2678
  Misses       1153     1153
  Partials      279      279

Flag
Coverage Δ

unittests
65.15% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out 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 034b990...9981f78. Read the comment docs.

Adapted last commit to also forward $scopedSlots  and $listeners.

Love this solution!


Is MinCommissionRate correct?

Context
https://github.com/celestiaorg/celestia-app/blob/41ead770b48d6b86dce3f252e1be844b4978e907/specs/src/specs/params.md?plain=1#L54
On main
$ celestia-appd query  staking params
bond_denom: utia
historical_entries: 10000
max_entries: 7
max_validators: 100
min_commission_rate: "0.000000000000000000"
unbonding_time: 1814400s

I think it should be once https://github.com/celestiaorg/celestia-app/pull/2417/files#diff-008f85e59c1e0f88e9ad4be82fd1a15f29261f9b9d1a71a19488c58b94fef363R98 is merged

Ahh good point. Proposal to update the params.md on main so that it reflects the current value of 0. I think https://github.com/celestiaorg/celestia-app/pull/2417 should update the param in both places (code and specs) so that the specs always match the observed value.


java.lang.illegalArgumentException: illegal character in authority at index 7: http://localhost:9090 /api/uploadHar

Hi Team,
I'm facing this error
java.lang.illegalArgumentException: illegal character in authority at index 7: http://localhost:9090 /api/uploadHar

Hey @Ravikm941, thanks for trying out Akto. I can see there is a space between 9090 and /api, which is causing the issue here. Can you provide a little more context on this. Are you trying out Akto via Local Deploy?

Hey @ayushaga14 , yes, I'm using Akto for local deployment on Docker and using the Burp Suite extension. However, in my localhost portal, the project is not showing. When I tried to refresh the URL, it displayed an error. I also attempted to access the URL without spaces, but it resulted in a 404 forbidden error in the browser.

Any update on this issue?

Hi @Ravikm941. Update the AKTO_IP variable in akto burp extension without spaces and try again. To access dashboard just go to localhost:9090/

@Ravikm941 can you try the above once ^ and let us know if it works. Else we can connect over a call and sort this


New getter category-next/getCategoryFrom and category-next/getCurrentCategory always returns the root category

Current behavior

The new getter category-next/getCategoryFrom (and category-next/getCurrentCategory) on the new category page always returns the root category because of a wrong filter in its getter.
This happens if there is a category with a path like / or a empty one in the category-next/categoriesMap state.
E.g. if you are in /boys.html and the it crawls to the states it tests like:
return getters.getCategories.find(category => path.includes(category.url_path)) || {}

If there is a category with path / (or empty) in the state, it will always return this one. This filter is quiet flacky. I would prefer something more concrete like this:
return getters.getCategories.find(category => path.replace(/^(\/)/gm, '') === category.url_path) || {}

Also what happens if you use a different url path, then it would never find the right current category, e.g. I added an extra mapper fallback to let the /new.html category availaible ever /new this won't over work with the new getters based on route path. You will need at least another getter for this at least.
I think this new functionality leads a bit in the wrong direction and needs way more flexibility.
Expected behavior

Get the right category from state.
Steps to reproduce the issue

See above.
Repository

develop
Can you handle fixing this bug by yourself?

[x] YES
[ ] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[x] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

Browser: All
OS: All
Node: All
Code Version: develop:latest

Okay, I think I found a solution and will open an PR later today for a more flexible integration :)

I added a PR with some comments: #3295

@patzick I made some improvements in the related PR #3295

Great job @cewald, thanks for your input! :)


Potential memory leak in repeat-click directive

Element UI version
2.10.1
OS/Browsers version
all
Vue version
2.6.10
Reproduction Link
https://jsfiddle.net/mmx38qxw/
Steps to reproduce
Use any element that uses the repeat-click directive
What is Expected?
Directive should unbind event handlers when destroyed
What is actually happening?
No code exists to remove the event handlers

As stated in ticket, after looking at the code for the repeat-click directive, it's clear you do nothing to unbind event handlers in your repeat-click directive. When any elements are destroyed that use the directive, the directives event handlers are never removed. This is likely going to cause memory leaks.
Solution would be to remove event handlers on the element destroyed life cycle event.

Please open issues in a correct repo.


Add PartialShape and Dimension to Python API

Adding PartialShape to the Python API.
Usage (see tests):
    ps = PartialShape([1, 2, 3, -1])
    assert repr(ps) == '<PartialShape: {1,2,3,?}>'

    ps = PartialShape.dynamic()
    assert repr(ps) == '<PartialShape: ?>'

    ps = PartialShape.dynamic(r=Dimension(2))
    assert repr(ps) == '<PartialShape: {?,?}>'

    ps = PartialShape([Dimension(1), Dimension(2), Dimension(3), Dimension.dynamic()])
    assert repr(ps) == '<PartialShape: {1,2,3,?}>'

    shape = Shape([1, 2, 3])
    ps = PartialShape(shape)
    assert repr(ps) == '<PartialShape: {1,2,3}>'

    ps = PartialShape([1, 2, 3, 4])
    assert repr(ps) == '<PartialShape: {1,2,3,4}>'

https://gitlab-icv.inn.intel.com/inference-engine/dldt/merge_requests/7427


[bug] qhub-deploy fails for azure project with dashes in the name

Describe the bug
qhub-deploy fails to deploy to Azure when using a project with dashes in the name. The error message is
[terraform]: Error: Failed to get existing workspaces: Error retrieving keys for Storage Account "qhub-test-tomdevtz9o1ryx": storage.AccountsClient#ListKeys: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="The Resource 'Microsoft.Storage/storageAccounts/qhub-test-tomdevtz9o1ryx' under resource group 'qhub-test-tom-dev' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix"

A few pieces of information:
project name: qhub-test-tom.
stroage account postfix: tz9o1ryx.
storage account name:  qhubtesttomdevtz9o1ryx
But in state.tf, we have
terraform {
  backend "azurerm" {
    resource_group_name = "qhub-test-tom-dev"
    # storage account must be globally unique
    storage_account_name = "qhub-test-tomdevtz9o1ryx"
    container_name       = "qhub-test-tom-devstate"
    key                  = "terraform/qhub-test-tom-dev.tfstate"
  }
}

The storage account has dashes in it (which I assume aren't allowed by Azure).
How can we help?
Help us help you.

What are you trying to achieve?
How can we reproduce the problem?
What is the expected behaviour?
And what is currently happening?
Any error messages?

If helpful, please add any screenshots and relevant links to the description.

Include your conda version (use conda --version), k8s and any other relevant details.

$ conda list qhub
# packages in environment at /home/taugspurger/miniconda3/envs/qhub:
#
# Name                    Version                   Build  Channel
qhub                      0.3.11             pyhd8ed1ab_0    conda-forge

Hi @TomAugspurger, thanks for using QHub. Azure has a number of constraints, which are implemented at different scopes, and must be considered while naming resources. Because of that, currently QHub uses some naming conventions to better address these outstanding restrictions.

Thanks. Would validating this be in scope for qhub?

Yes it would.

@viniciusdc please updated the status on the issue.
Thank you

Hi @TomAugspurger, sorry for the late feedback. This validation will be available in the next release, with validation messages to the end user to ensure the source of the error.  Another feature that will be enhanced is a linter to help the user to verify the QHub config if you have github-action enabled.
Please let us know if we can help you with anything further, and thank you for using QHub.

Hey @TomAugspurger, we apologize for the delay in getting to this! We are wrapping up a handful of PRs which address this (and other bugs). Thanks for you patience!