Error: Callback was already called.

So i was installing the script on my server and it dosen't stop to say

[Operating System]:Debian 8x64

[How did you start the script]: node index.js

Callback was already called

[!] Socket server is online.
[!] All bots online.
/var/www/html/node_modules/async/dist/async.js:903
        if (fn === null) throw new Error("Callback was already called.");
                         ^

Error: Callback was already called.
    at /var/www/html/node_modules/async/dist/async.js:903:32
    at Timeout.setTimeout (/var/www/html/lib/bots.js:70:13)
    at ontimeout (timers.js:386:14)
    at tryOnTimeout (timers.js:250:5)
    at Timer.listOnTimeout (timers.js:214:5)
root@locationvps:/var/www/html#

Seems like there is a problem with your node modules.
Where did you get your modules?

With "npm install"

Is apache installed? And why did you choose to place your files in /var/www/html/ ?

Is apache installed?: yes
And why did you choose to place your files in /var/www/html/ ? I don't know should i place the file somewhere else

What port are you using in your config.js?
Apache is using port 80, so if you want to use this, delete/disable apache, or change the port in the config.js
Try to place the script somewhere else, maybe in /home/

I'm using port 80 for the config but i stopped apache

Weird. Are you showing me the full error?
Are you sure everything in the config is correct, including twoFactorCode, identitySecret, apikey, username, password?
Also is the steam account you are trying this on limited?

so i tried install all the thing with a new config.js (blank one) and it launch and it doesn't crash

So it works now?

so i maybe found the problem its the bot i think

Is your bot account limited?

I just created the account

Did you deposit 5$/€ to the account?

oh is this the problem ?

Yes it is. You have to deposit 5$ to get the steamAPI key.


Handle targets with path elements

filesystem store stores them down as urlencoded, this mirrors behavior of the go-tuf client

that's handled by conformance, but I'll add it in.


Upgrade Newtonsoft.Json repo from 13.0.1 to 13.0.3

See https://github.com/dotnet/source-build-externals/pull/187#issuecomment-1677965868

Converting this to draft while I work through the build issues.

I consolidate all the patch files into one. This was necessary because I needed to make an additional patch but that was conflicting due to overlap with other patches. So consolidating things made it easier to understand and cleaner.
The change I made was to disable EnablePackageValidation. This is needed because the API compat validation was running into errors like this:
/repos/source-build-externals/.dotnet/sdk/8.0.100-preview.7.23376.3/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.ApiCompat.ValidatePackage.targets(39,5): error PKV006: Target framework .NETFramework,Version=v2.0 is no longer supported in the latest version. [/repos/source-build-externals/artifacts/source-build/self/src/src/newtonsoft-json/Src/Newtonsoft.Json/Newtonsoft.Json.csproj]

The reason for that is:

Source-build overrides the TFMs to remove .NET Fx
Newtonsoft.Json is configured to use 13.0.1 as the baseline version for the API compat check. This causes Newtonsoft.Json.13.0.1 to be restored from the dnceng-public feed. That contains .NET Fx TFMs. Since the new package produced by source-build doesn't have these, it leads to these errors.


The dialog shows blank when clicking 'Configure CORS Settings...'

Storage Explorer Version: 1.33.0-dev (96)
Build Number: 20231205.1
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.1.1 (Apple M1 Pro)
Architecture: ia32/x64/x64
How Found: From running test cases
Regression From: Previous release (1.32.1)
Steps to Reproduce

Expand one storage account.
Right click 'Blob Containers' node -> Click 'Configure CORS Settings...'.
Check whether the dialog shows normal.

Expected Experience
The dialog shows normal.

Actual Experience
The dialog shows blank.

Additional Context
This issue also reproduces for 'File Shares/Queues/Tables' node.

There's a change already in PR that should resolve this.

No, it is not. I'll make sure it's reinserted. Please verify.

Verified this issue on main build 20231209.3. The description has been added back.


feat(ci): Rust CircleCI Checks

Description
Moves rust checks to CircleCI with Slack alerting on failure for main branch runs.

Converting to a draft to work on this a bit more - need to figure out the best way to perform releases while also hitting slack on failure.


Porting test_parfors.py into numba-dpex test suite

Addressing SAT-5048. The goal of this draft PR is to:

All Numba unit tests related to prange are defined in test_parfor.py. These tests should be adapted into the numba-dpex test suite and the pass-rate metrics should be reported during regular CI runs.

Passing all unit tests inTestParforBasic, except 2 tests.
Not to be run with CI for the time being.

to run:
$ python test_parfors.py

Currently it's based on unittest, needs to be refactored for pytest
Refer to the TODOs for the current issues.
Classes in the process of porting

[x] TestParforsRunner
[x] TestParforsBase
[x] TestParforBasic
[x] TestParforNumericalMisc
[x] TestParforNumpy
[x] TestParforsUnsupported
[x] TestParfors
[x] TestParforLeaks
[x] TestParforsSlice
[x] TestParforsOptions
[x] TestParforsBitMask
[x] TestParforsMisc
[x] TestParforsDiagnostics
[x] TestPrangeBase
[x] TestPrangeBasic
[x] TestPrangeSpecific
[x] TestParforVectorizer

[x] Have you provided a meaningful PR description?
[x] Have you added a test, reproducer or referred to an issue with a reproducer?
[x] Have you tested your changes locally for CPU and GPU devices?
[x] Have you made sure that new changes do not introduce compiler warnings?
[x] If this PR is a work in progress, are you filing the PR as a draft?

@diptorupd @mingjie-intel @adarshyoga FYI

New test results, turning off all skips (just keeping whatever was done by numba team). Keeping auto-cpu-fallback off.
=================================== short test summary info ===================================
FAILED test_parfors.py::TestParforBasic::test_simple23 - numba.core.errors.TypingError: Fail...
FAILED test_parfors.py::TestParforNumericalMisc::test_kmeans - numba.core.errors.TypingError...
FAILED test_parfors.py::TestParforNumericalMisc::test_pi - numba.core.errors.TypingError: Fa...
FAILED test_parfors.py::TestParforNumPy::test_fuse_argmin_argmax_max_min - KeyError: "Failed...
FAILED test_parfors.py::TestParforNumPy::test_linspace - numba.core.errors.LoweringError: Fa...
FAILED test_parfors.py::TestParforNumPy::test_std - numba.core.errors.LoweringError: Failed ...
FAILED test_parfors.py::TestParforNumPy::test_var - numba.core.errors.LoweringError: Failed ...
FAILED test_parfors.py::TestParfors::test_array_tuple_concat - KeyError: "Failed in dpex_nop...
FAILED test_parfors.py::TestParfors::test_inplace_binop - AssertionError:
FAILED test_parfors.py::TestParfors::test_namedtuple1 - numba.core.errors.LoweringError: Fai...
FAILED test_parfors.py::TestParfors::test_namedtuple2 - numba.core.errors.LoweringError: Fai...
FAILED test_parfors.py::TestParfors::test_no_hoisting_with_member_function_call - numba.core...
FAILED test_parfors.py::TestParfors::test_one_d_array_reduction - numba.core.errors.Lowering...
FAILED test_parfors.py::TestParfors::test_parfor_array_access1 - KeyError: "Failed in dpex_n...
FAILED test_parfors.py::TestParfors::test_parfor_array_access2 - numba.core.errors.LoweringE...
FAILED test_parfors.py::TestParfors::test_parfor_array_access5 - numba.core.errors.LoweringE...
FAILED test_parfors.py::TestParfors::test_parfor_dtype_type - numba.core.errors.LoweringErro...
FAILED test_parfors.py::TestParfors::test_preparfor_canonicalize_kws - numba.core.errors.Typ...
FAILED test_parfors.py::TestParfors::test_reduce - numba.core.errors.LoweringError: Failed i...
FAILED test_parfors.py::TestParfors::test_reduction_var_reuse - numba.core.errors.LoweringEr...
FAILED test_parfors.py::TestParfors::test_size_assertion - numba.core.errors.LoweringError: ...
FAILED test_parfors.py::TestParfors::test_three_d_array_reduction - numba.core.errors.Loweri...
FAILED test_parfors.py::TestParfors::test_tuple1 - numba.core.errors.LoweringError: Failed i...
FAILED test_parfors.py::TestParfors::test_tuple2 - numba.core.errors.LoweringError: Failed i...
FAILED test_parfors.py::TestParfors::test_tuple3 - numba.core.errors.LoweringError: Failed i...
FAILED test_parfors.py::TestParfors::test_two_d_array_reduction - numba.core.errors.Lowering...
FAILED test_parfors.py::TestParfors::test_two_d_array_reduction_prod - numba.core.errors.Low...
FAILED test_parfors.py::TestParfors::test_two_d_array_reduction_reuse - numba.core.errors.Lo...
FAILED test_parfors.py::TestParfors::test_two_d_array_reduction_with_float_sizes - numba.cor...
FAILED test_parfors.py::TestParforsLeaks::test_multiple_reduction_vars - numba.core.errors.L...
FAILED test_parfors.py::TestParforsLeaks::test_reduction - numba.core.errors.LoweringError: ...
FAILED test_parfors.py::TestParforsSlice::test_parfor_array_access_lower_slice - numba.core....
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice11 - numba.core.errors.TypingErro...
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice12 - numba.core.errors.TypingErro...
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice13 - numba.core.errors.TypingErro...
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice14 - numba.core.errors.TypingErro...
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice15 - numba.core.errors.TypingErro...
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice2 - numba.core.errors.LoweringErr...
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice22 - numba.core.errors.LoweringEr...
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice26 - numba.core.errors.TypingErro...
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice27 - numba.core.errors.LoweringEr...
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice3 - AssertionError:
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice4 - AssertionError:
FAILED test_parfors.py::TestParforsSlice::test_parfor_slice7 - AssertionError:
FAILED test_parfors.py::TestParforsOptions::test_parfor_options - numba.core.errors.Lowering...
FAILED test_parfors.py::TestParforsBitMask::test_parfor_bitmask1 - AssertionError:
FAILED test_parfors.py::TestParforsBitMask::test_parfor_bitmask2 - AssertionError:
FAILED test_parfors.py::TestParforsBitMask::test_parfor_bitmask3 - AssertionError:
FAILED test_parfors.py::TestParforsBitMask::test_parfor_bitmask4 - AssertionError:
FAILED test_parfors.py::TestParforsMisc::test_issue3169 - numba.core.errors.LoweringError: F...
FAILED test_parfors.py::TestParforsMisc::test_issue3748 - numba.core.errors.LoweringError: F...
FAILED test_parfors.py::TestParforsMisc::test_issue5001 - numba.core.errors.LoweringError: F...
FAILED test_parfors.py::TestParforsMisc::test_issue5065 - numba.core.errors.LoweringError: F...
FAILED test_parfors.py::TestParforsMisc::test_issue5167 - numba.core.errors.TypingError: Fai...
FAILED test_parfors.py::TestParforsMisc::test_issue5277 - numba.core.errors.LoweringError: F...
FAILED test_parfors.py::TestParforsMisc::test_issue5570_ssa_races - numba.core.errors.Loweri...
FAILED test_parfors.py::TestParforsMisc::test_issue6095_numpy_max - numba.core.errors.Loweri...
FAILED test_parfors.py::TestParforsMisc::test_issue6774 - numba.core.errors.LoweringError: F...
FAILED test_parfors.py::TestParforsMisc::test_issue_5098 - numba.core.errors.TypingError: Fa...
FAILED test_parfors.py::TestParforsMisc::test_no_state_change_in_gufunc_lowering_on_error - ...
FAILED test_parfors.py::TestParforsMisc::test_no_warn_if_cache_set - numba.core.errors.Lower...
FAILED test_parfors.py::TestParforsDiagnostics::test_allocation_hoisting - numba.core.errors...
FAILED test_parfors.py::TestParforsDiagnostics::test_reduction - numba.core.errors.LoweringE...
FAILED test_parfors.py::TestParforsDiagnostics::test_setitem - AssertionError:
FAILED test_parfors.py::TestParforsDiagnostics::test_user_varname - numba.core.errors.Loweri...
FAILED test_parfors.py::TestPrangeSpecific::test_copy_global_for_parfor - AssertionError:
FAILED test_parfors.py::TestPrangeSpecific::test_list_comprehension_prange - numba.core.erro...
FAILED test_parfors.py::TestPrangeSpecific::test_mutable_list_param - AssertionError: Failed...
============= 68 failed, 133 passed, 34 skipped, 71 warnings in 759.93s (0:12:39) =============

@diptorupd

Here is the breakdown:

Class
Synopsis
No. of Tests
Passed
Failed
Skipped
% Pass [Passed/(Total - Skipped)]

TestParforBasic
np.ones, np.linalg, np.dot, np.sum Matrix Ops
25
17
1
7
94%

TestParforNumericalMisc
pi, blackscholes, logistic regression, k-means
4
1
2
1
33%

TestParforNumPy
mean, std, var, arange, random, min/max, argmin/argmax
21
16
4
1
80%

TestParforsUnsupported
parallel target on 32bit hardware
1
0
0
1
~

TestParfors
various parfor features, e.g. reduction, array-access, slice
43
18
22
3
45%

TestParforsLeaks
reduction leak test
2
0
2
0
0%

TestParforsSlice
different slicing scenarios
28
11
13
4
46%

TestParforsOptions
fusion, comprehension, reduction, prange, setitem
1
0
1
0
0%

TestParforsBitMask
bitmask, leftshift, rightshift
6
2
4
0
33%

TestParforsMisc
miscellaneous parts of ParallelAccelerator
23
10
11
2
45%

TestParforsDiagnostics
fusion equivalence, nested prange, array expression
8
4
4
0
50%

TestPrangeBasic
different prange situations
32
31
0
1
100%

TestPrangeSpecific
conflicting reduction, same reduction with different instances
25
21
3
1
88%

TestParforsVectorizer
intrinsics, vector asm, refusal to vectorize
3
3
0
0
100%

@diptorupd FYI


add /payments endpoint

to serve accounts, so we don't have to filter payments on the /activity endpoint.

Is this for global payments? Or payments per account?

Closing this per @allenan since explorer is not hitting issues with filter_type activity lists


refactor!: ky replaces axios

Closes #373
As this work will go to 2.0 version, I have created a 2.0 branch that this PR targets that will be used for future works until Bee is released and 1.2 version will be possible to release. Or if I gonna finish all the work for 2.0 before 1.2 release then I guess will skip it. Will see.
Breaking changes:

Requests made by bee-js are now reported with User-Agent: bee-js/<<bee-js's version>>
Utils.setDefaultHeaders() was removed in favor of Bee/BeeDebug instance's option defaultHeaders
Hooks

Utils.hooks.* was removed in favor of Bee/BeeDebug instance's options onRequest and onResponse
Hooks now pass only metadata of the requests and not the payload

All returned streams are now of WHATWG ReadableStream. If you need NodeJS's Readable you can use Utils.Stream.readableWebToNode() utility function.
All axiosOptions were removed from those methods that supported it (for example bee.downloadReadableData(), bee.reuploadPinnedData(), UploadOptions does not have axiosOptions property anymore)
Unfortunately fetch does not support tracking of upload progress (like XHR/axios supported with the onUploadProgress).

Other changes:

All upload methods that used to accept NodeJS's Readable now accept both NodeJS and WHATWG Readable(Stream).
Usage of ReadableStreams in a browser is now possible. Be aware that real support for streaming browsers has only for download, but not upload. When Readable is passed to upload methods it is first fully buffered before making the request.

Thanks, @nugaon for the review and a lot of great improvement suggestions!

Other thing is the ky instance is required on every exported module seems like an inconvenient downgrade for me.
It could accept string type as well as so far with httpBase: string | Ky as a first parameter instead of it only accepts ky: Ky. Therefore, this breaking change wouldn't be that breaking (as you had to change every module tests because of this).

Honestly, I don't agree with this. First of all the modules are exported, but they are internal to the package so it is up to us how we want to implement this. Second of all, Ky instance does define more than the URL that it talks to. It defines hooks, default headers, and in future things like retries, timeout and other configurations. If we allow passing a string, we open a space for a future error where a developer can pass URL string instead of Ky which removes all the configuration.
Allowing string seems to me like a "hack" to avoid doing more work (eq. refactoring tests) that I have already done anyway(and which was not hard at all as most of refactoring did my IDE). I would prefer to have clean solution.

Moreover, you said when we exported the AxiosOptions we shouldn't stuck to one HTTP library implementation and our library should abstract it as much as possible. Nevertheless this principal is not applied in this case.

I don't see the parallel here. I said that regarding exposed AxiosOptions on the public API. Modules are not public API so I don't see how it is related here.


Simpler syntax to create lists, dicts, and other collections as arguments to keywords

Robot's automatic argument conversion (#2890) makes it possible to have a keywords like
def accept_list(arg: list):
    ...

def accept_dict(arg: dict):
    ...

and call them so that argument are Python literals
Accept List    ['list', 'items', 'here']
Accept Dict    {'key': 'value', 'another': 'item'}

This is pretty convenient, but needing to use Python syntax is a bit ugly in general and especially annoying when using embedded arguments that are supposed to enhance readability:
Select animals ['cat', 'dog'] from list

I propose we enhance argument conversion so that we support also the following syntax:
Accept List    list, items, here
Accept Dict    key=value, another=item

The high level semantics would be as follows:

Separator between items is a comma and a space. This allows using commas in values like first, second,with,commas, third. Having a comma followed by a space in the value wouldn't be possible.
We could allow using a semicolon and a space as an alternative separator. In that case we'd use the separator that's encountered first. This would allow usages like first; second, with, commas followed by spaces; third.
With dictionaries the separator between key and value is =. This is the syntax we use also when creating &{dict} variables.
Values are considered strings by default. This can be changed by using generics (#4433) and TypedDict (#4477).
Because this would be handled by type convertors, variables would have been resolved already earlier. That means that something like ${1}, ${2} wouldn't create a list of integers. See the above point for alternatives.
Also escapes are handled before type conversion. That makes it impossible to use something like first, second\,with\,commas for escaping commas in values.

This enhancement would ease using collections a lot especially if #4433 and #4477 are implemented. If we agree above semantics are fine, implementation would also be pretty easy. I thus add this to RF 5.1 scope even though the release is already late.

Select animals cat, dog from list
After the proposed change should this work and would it be more readable than the old one? I would personally expect some sort of separator around the list items.

Select animals cat, dog from list isn't great, but it's certainly better for non-programmers than Select animals ['cat', 'dog'] from list.

Based on the discussion on Slack, it seems this isn't considered that important and there are concerns about the syntax. Let's descope this from RF 5.1 and think about this again later.


How to easily use the example models with jupyter note book? workflow_by_code_my.ipynb

❓ Questions and Help
How to easily use the example models with jupyter note book? such as in workflow_by_code_my.ipynb
I found workflow_by_code_my.ipynb has only one example LGBModel, does it mean we have to modify the notebook file everytime when want to try a new model?
I went through the document but did not find an easy way to debug of visualize the result by using qrun.
Thanks for the help in advance.

Hi,
I tried to convert yaml into notebook(ALSTM model), but got the following error.  could you give some comment on this?
[7232:MainThread](2021-05-09 17:52:18,801) INFO - qlib.ALSTM - [pytorch_alstm_ts.py:62] - ALSTM pytorch version...
[7232:MainThread](2021-05-09 17:52:18,802) INFO - qlib.ALSTM - [pytorch_alstm_ts.py:111] - ALSTM parameters setting:
d_feat : 20
hidden_size : 64
num_layers : 2
dropout : 0.0
n_epochs : 200
lr : 0.001
metric : loss
batch_size : 800
early_stop : 10
optimizer : adam
loss_type : mse
device : cpu
n_jobs : 20
use_GPU : False
seed : None
[7232:MainThread](2021-05-09 17:52:18,809) INFO - qlib.ALSTM - [pytorch_alstm_ts.py:125] - model:
ALSTMModel(
(net): Sequential(
(fc_in): Linear(in_features=20, out_features=64, bias=True)
(act): Tanh()
)
(rnn): GRU(64, 64, num_layers=2, batch_first=True)
(fc_out): Linear(in_features=128, out_features=1, bias=True)
(att_net): Sequential(
(att_fc_in): Linear(in_features=64, out_features=32, bias=True)
(att_dropout): Dropout(p=0.0, inplace=False)
(att_act): Tanh()
(att_fc_out): Linear(in_features=32, out_features=1, bias=False)
(att_softmax): Softmax(dim=1)
)
)
[7232:MainThread](2021-05-09 17:52:18,811) INFO - qlib.ALSTM - [pytorch_alstm_ts.py:126] - model size: 0.0510 MB
[7232:MainThread](2021-05-09 17:55:11,412) INFO - qlib.timer - [log.py:77] - Time cost: 172.595s | Loading data Done
[7232:MainThread](2021-05-09 17:55:12,198) INFO - qlib.timer - [log.py:77] - Time cost: 0.614s | FilterCol Done
[7232:MainThread](2021-05-09 17:55:13,270) INFO - qlib.timer - [log.py:77] - Time cost: 1.070s | RobustZScoreNorm Done
[7232:MainThread](2021-05-09 17:55:13,322) INFO - qlib.timer - [log.py:77] - Time cost: 0.051s | Fillna Done
[7232:MainThread](2021-05-09 17:55:13,436) INFO - qlib.timer - [log.py:77] - Time cost: 0.090s | DropnaLabel Done
[7232:MainThread](2021-05-09 17:55:13,875) INFO - qlib.timer - [log.py:77] - Time cost: 0.437s | CSRankNorm Done
[7232:MainThread](2021-05-09 17:55:13,876) INFO - qlib.timer - [log.py:77] - Time cost: 2.463s | fit & process data Done
[7232:MainThread](2021-05-09 17:55:13,876) INFO - qlib.timer - [log.py:77] - Time cost: 175.060s | Init data Done
[7232:MainThread](2021-05-09 17:55:13,878) INFO - qlib.workflow - [expm.py:254] - No tracking URI is provided. Use the default tracking URI.
[7232:MainThread](2021-05-09 17:55:13,879) INFO - qlib.workflow - [expm.py:290] - <mlflow.tracking.client.MlflowClient object at 0x000001DE62E8B8C8>
[7232:MainThread](2021-05-09 17:55:13,887) INFO - qlib.workflow - [exp.py:242] - Experiment 2 starts running ...
[7232:MainThread](2021-05-09 17:55:14,630) INFO - qlib.workflow - [recorder.py:270] - Recorder e27719a22f0d4524aa8c79a440cc1244 starts running under Experiment 2 ...
AttributeError                            Traceback (most recent call last)
 in
92 with R.start(experiment_name="train_model"):
93     R.log_params(**flatten_dict(task))
---> 94     model.fit(dataset)
95     R.save_objects(trained_model=model)
96     rid = R.get_recorder().id
~\AppData\Local\Continuum\anaconda3\envs\Qlib\lib\site-packages\pyqlib-<IP_ADDRESS>-py3.7-win-amd64.egg\qlib\contrib\model\pytorch_alstm_ts.py in fit(self, dataset, evals_result, save_path)
209         dl_valid = dataset.prepare("valid", col_set=["feature", "label"], data_key=DataHandlerLP.DK_L)
210
--> 211         dl_train.config(fillna_type="ffill+bfill")  # process nan brought by dataloader
212         dl_valid.config(fillna_type="ffill+bfill")  # process nan brought by dataloader
213
~\AppData\Local\Continuum\anaconda3\envs\Qlib\lib\site-packages\pandas-1.2.4-py3.7-win-amd64.egg\pandas\core\generic.py in getattr(self, name)
5463             if self._info_axis._can_hold_identifiers_and_holds_name(name):
5464                 return self[name]
-> 5465             return object.getattribute(self, name)
5466
5467     def setattr(self, name: str, value) -> None:
AttributeError: 'DataFrame' object has no attribute 'config'
Following are the python code that was converted from yaml file.
###################################
train model
###################################
data_handler_config = {
"start_time": "2008-01-01",
"end_time": "2020-08-01",
"fit_start_time": "2008-01-01",
"fit_end_time": "2014-12-31",
"instruments": market,
"infer_processors": [{
"class": "FilterCol",
"kwargs": {
"fields_group": "feature",
"col_list": ["RESI5", "WVMA5", "RSQR5", "KLEN", "RSQR10", "CORR5", "CORD5", "CORR10",
"ROC60", "RESI10", "VSTD5", "RSQR60", "CORR60", "WVMA60", "STD5",
"RSQR20", "CORD60", "CORD10", "CORR20", "KLOW"
],
},
},
{
"class": "RobustZScoreNorm",
"kwargs":{
"fields_group": "feature",
"clip_outlier": True,
},
},
{
"class": "Fillna",
"kwargs":{
"fields_group": "feature",
},
},
],
"learn_processors" : [
{
"class" : "DropnaLabel",
},
{
"class" : "CSRankNorm",
"kwargs" : {
"fields_group" : "label",
},
},
],
"label": ["Ref($close, -2) / Ref($close, -1) - 1"],
}
task = {
"model": {
"class": "ALSTM",
"module_path": "qlib.contrib.model.pytorch_alstm_ts",
"kwargs": {
"d_feat": 20,
"hidden_size": 64,
"num_layers": 2,
"dropout": 0.0,
"n_epochs": 200,
"lr": 1e-3,
"early_stop": 10,
"batch_size": 800,
"metric": "loss",
"loss": "mse",
"n_jobs": 20,
"GPU": 0,
"rnn_type": "GRU",
},
},
"dataset": {
"class": "DatasetH",
"module_path": "qlib.data.dataset",
"kwargs": {
"handler": {
"class": "Alpha158",
"module_path": "qlib.contrib.data.handler",
"kwargs": data_handler_config,
},
"segments": {
"train": ("2008-01-01", "2014-12-31"),
"valid": ("2015-01-01", "2016-12-31"),
"test": ("2017-01-01", "2020-08-01"),
},
"step_len": 20,
},
},
}

Hi @Joshuajxy , it seems you are using the wrong data set class. You should be using the TSDatasetH if running models with ts in name. You can refer to the details in the YAML file of ALSTM here。

I tried to call label_df = dataset.prepare("test", col_set="label").data and found that it prompts
'TSDataSampler' object has no attribute 'data'.

After referring to the source code, it seems that the usage is now deprecated for TSDataSampler and I add another line to make it work for the current version:
label_df = pd.DataFrame(data=label_df.data_arr[:-1], index=label_df.data_index)

It seems that the last row is set to nan by design. Anyway, it should be ignored when constructing a DataFrame.
https://github.com/microsoft/qlib/blob/7800dd4ec9540e76d8bdcc8688d00f4ff4fbdf3a/qlib/data/dataset/__init__.py#L301

@LogCreative
TSDataSampler is designed for time series.
Its internal data is data_arr in a tabular format. TSDataSampler tries to create time series based on the tabular data.
The last row with nan value is designed for improving performance when creating time series from tabular data.
https://github.com/microsoft/qlib/blob/main/qlib/data/dataset/__init__.py#L241
If you want to get tabular data, the best practice is

use step_len=1 https://github.com/microsoft/qlib/blob/main/qlib/data/dataset/__init__.py#L259
use DatasetH instead of TSDatasetH
You can either way of them

Thanks for your attention.


updated history command for #8

befoer the merge #17 there was no data structure used or needed but for #8 need to use data structure in the history command
so this need to update for #8

Hi @RANJEETJ06 do let me know if you want to take on #8 too.
Just comment on #8 and I'll assign it to you.


iTerm2 cursor color either transparent or same as background

Every wallpaper I've attempted to use produces the same result: an invisible cursor.  It makes it impossible to work in vim, the only way to figure out where you are is to find a pair of brackets/parentheses/etc. that will highlight.
Running on macOS High Sierra 10.13.6 using pywal as the backend.  I can provide any more details necessary.

I'm going to have to wait for a PR for this one as I don't have a macOS machine to test on.

i've also noticed this.  i have spent all morning digging through the wal.vim colorscheme to see if i can change the the cursor background

In my case it's not only the vim cursor but the iTerm one.

I should mention, I used vim to explain how hard the impact of the bug is.  The problem is terminal-based and applies to all terminal-based applications.

@JohnHuddleston This issue should be resolved.  I experienced the same issue and corrected it with the pull request shown above.

Awesome, confirmed on my end, everything works!

When will those changes be available in the pip version? The latest version I can install is from the 21st January.

@phlind pip3 install pywal on macOS does still pull a version of pywal without the bugfix, but I found that if I copied the current contents of sequences.py from github into /usr/local/lib/python3.7/site-packages/pywal/sequences.py then the issue was resolved without issue.

this issue has returned for me

+1

Building from the master branch should work, had the same issue with release 3.3.0

yeah, i had forgotten about this and reinstalled.  i just made the edit to my pip install


Add exception context

This PR is a draft until the tests are passing, and additional tests have been added (e.g. to test that ExceptionContext handles nested exceptions and deep tracebacks properly).
The schema should be reviewed with special attention paid towards keeping the data anonymous. Currently we hash the str and repr of the exception, so we won't be getting e.g. error message. We do collect the unhashed paths of the Python source files across the traceback, but only if it can be made relative to the installation location of Python.
For example:

/home/will/.pyenv/versions/meltano37/lib/python3.7/site-packages/meltano/core/utils/__init__.py becomes lib/python3.7/site-packages/meltano/core/utils/__init__.py
/home/will/.pyenv/versions/meltano37/lib/python3.7/pathlib.py becomes lib/python3.7/pathlib.py

Closes #6126

Thanks for the review @aaronsteers! I agree with your suggestions, and have implemented them.

Do you mind if we wait until Monday to get an extra pair of eyes from @edgarrmondragon and/or @pandemicsyn ?

I don't mind at all. I would greatly appreciate having an extra pair of eyes go over this.

nice, so in cases where we abort/fail due to an exception - as long as we fire an event (as we do in https://github.com/meltano/meltano/blob/main/src/meltano/cli/install.py#L65), we'll have the exception context attached along side any other contexts (env, cli, plugins, etc) that may have been added, correct ?

@pandemicsyn Correct. The exception context is automatically added to event event. If an event occurs while an error is being handled (i.e. within some except block) then we'll gain info about the exception.
Unfortunately the stack is unwound before the atexit handlers are run, so if an exit occurs within an exception block, we'll get an exit event, but the exception context it comes with will not have details about the exception that originally triggered the exit.
To get that info, we'll probably want to fire an event within the finally block in meltano.cli. This can be the exit event. We'll add a global flag for whether the exit event has been fired. If we fire the exit even within meltano.cli, then it will not be fired from the atexit handler later. This way we can still leverage atexit to ensure the exit event is fired in all possible cases, but also get more info about what caused the exit whenever possible.

Thanks @edgarrmondragon! I'll do that in a separate PR, and create an issue to track it now.

@edgarrmondragon @pandemicsyn This PR is targeting the branch from https://github.com/meltano/meltano/pull/6148. We'll want to either merge that PR in first, or if we decide against the changes it proposes, rebase this PR onto main.


Old data in config.json contaminates future runs

Description
Array fields in the delivery config.json are merged with saved attribute state from old runs, resulting in unexpected and somewhat random results.
Replication case
Use a single build node, so successive runs will be in the same node and workspace.
Start with config.json like this:
{
    "version":"2",
    "build_cookbook":{
        "path":".delivery/build-cookbook",
        "name":"build-cookbook"
    },
    "skip_phases":[
        "security",
        "quality",
        "smoke",
        "functional"
    ],
    "build_nodes":{
    },
    "dependencies":[
    ],
    "delivery-truck":{
        "publish":{
            "chef_server":true
        },
        "lint": {
            "foodcritic": {
                "fail_tags": [ "any" ]
            }
        }
    }
}

Run a changed cookbook through verify... lint should have -f any
Now change the config.json to this:
        "lint": {
            "foodcritic": {
                "fail_tags": [ "correctness", "metadata" ]
            }
        }

Run the changed cookbook through... lint has -f any,correctness,metadata
Logon to build node, go to the workspace for the phase:
cd /var/opt/delivery/workspace/<IP_ADDRESS>/test/test/mvt/master/verify/lint

Look at the attribute json for the phase in chef/dna.json and it is correct:
{"lint":{"foodcritic":{"fail_tags":["correctness","metadata"]}}
Look at the stored node state in chef/nodes/build-node-test-1 and it has the merged data:
          "lint": {
            "foodcritic": {
              "fail_tags": [
                "any",
                "correctness",
                "metadata"
              ]
            }

The stored node state between the first and second run would have been:
          "lint": {
            "foodcritic": {
              "fail_tags": [
                "any"
              ]
            }

which is being merged with the dna.json.  This happens for any array attribute that's being passed through for build recipes to use. It's the defined Chef array merge behavior, but in this case it really isn't what the user wants, and there isn't an obvious workaround.
Seems like either:

chef-client should be run with -o rather than -r so node state isnt stored
OR
the node state should be cleared before each run

We are working on a solution for this @christinedraper .. Thank you so much for your always amazing feedback!! 😄

Work started. 👍  This will be fix soon!


Script cache creating is broken after bumping v8 version to 6.6.313

It was known to be working in 6.6.275, however in 6.6.313 we have caching broken (https://travis-ci.org/pinepain/php-v8/jobs/345791065#L3109) - all tests return NULL for generated cache. I guess we need to make minimal example to reproduce and validate whether it's not a some obvious integration issue and then ask v8-users for help.

Here's a deal breaker - https://github.com/v8/v8/commit/5a68df2ab528ae8248806ae4fe7f8b52a14f731c


Fix a fatal error __DEV__ is not defined

In certain conditions, __DEV__ is not defined on the global object (for example when not using a bundler). This can cause a fatal error to occur unless __DEV__ is defined. This for example happens when trying to import the error file from mocha or jest (without the right env)
ReferenceError: __DEV__ is not defined

This PR merely fixes this fatal error that can be experienced downstream but does not offer any improvements/alternatives. In the future might be worth to make this more inclusive but there does not seem to really be a standard:

process.env.NODE_ENV in nodejs
__DEV__ for certain bundlers
process.env.VERCEL_ENV in vercel
etc.

Thanks for the response! The way I am building the js client now is:

Generate ts code using kinobi
Transpile to js using tsc (which mirrors the __DEV__ check into the js code)
Publish the transpiled js only to npm which can then be consumed downstream

In this case if __DEV__ is not defined downstream this error occurs (unless some sort of bundler is used that defines __DEV__. I guess if I swapped out the tsc step for some sort of bundler I wouldn't have this problem but I'd rather just use tsc (unless there is a valid reason to not do so of course)

For anyone with the same problem. I've added an index file that wraps the generated code by kinobi for building with tsc. Not ideal but it works:
Object.assign(global, { __DEV__: process.env.NODE_ENV === "development" });

export * from "./generated";

Thanks for providing a workaround in case other are facing the same issue.
I think we may revisit in the future since it'll make bundling generated packages easier but I'm worried the proposed solution will override the __DEV__ variable offered by some bundlers such as Webpack.
My recommended way to approach this is to use the create-solana-program template generator which already offers a way to bundle the generated code and includes a shim for the __DEV__ variable.

Hey 👋
Sorry I forgot to report back a while ago but this has been fixed by https://github.com/kinobi-so/kinobi/pull/103.
The fix is basically to ditch the __DEV__ global variable altogether and generate the condition process.env.NODE_ENV !== "production" directly.
I hope this helps. 🙂


proposal: support group-by edges

Currently, the generated API supports grouping only by valid fields/columns and there's no way to group by edge/edge-fields in a type-safe way.
I'm thinking about adding a new API for both ordering/grouping that will accept a <package>.By argument (e.g. pet.By) to support this functionality. For example:
// #1
client.Pet.Query().
	Group(
		pet.ByAge(),
		pet.ByOwner(
			user.ByName(), // ASC/DESC
		),
	).
	// ...

// #2
client.Pet.Query().
	Group(&pet.GroupBy{
		Owner: &user.GroupBy{
			Name: ent.Asc,
		},
	}).
	// ..

Thoughts, suggestions or feedback are more than welcome 😃

Would the first API option also support a user.ByOwner() call? E.g. users belong to "user groups", and you actually want to group pets by "user group"?

Is grouping by edge fields still not possible?


Implement getVcfHeaderReferenceSetName

Assumes #1166 has been merged.
We should use the pysam VCF header parsing code to attempt a guess at the reference name for a particular Variant set. There are some headers in the VCF spec for this which we should try to use.

We do this https://github.com/ga4gh/ga4gh-server/blob/master/ga4gh/server/cli/repomanager.py#L295


Update trusted-launch.md

This isn't needed anymore. #signoff

@lakmeedee

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Howie425 - I see that you're now the listed author for this article. Could you submit this change in the private repo instead? I'll close the PR now.

@ShannonLeavitt - Hey I took care of this and submitted to the private repo.


Edge Cases for Memory Leaks

Used by lab instructor to "break code"

Hi, the manifest changes/names look good, but the input isn't valid in certain places and neither is the output.
For example, "DEF x" must be followed by a number on the same line, not on the one after.
Additionally, the output does not match what would be expected for the input. "success" is missing in a few places for example.
Once these issues are fixed I'd be happy to merge this PR. Thanks for your contribution!

Hi, there isn't a requirement for what line the input command components must be on, simply what value follows what kind of command, e.g DEF must be followed by the name and value ( the lab instructor entered these commands in this exact order when I asked him to break my code if this helps as well, and he mentioned this usually causes memory leaks).
I've also only included outputs to commands that require them, for example, I skipped outputting during the END command since it doesn't require an output and the PRT command either outputs the variable that was specified or outputs whether that value exists or not (so no success or failure); hence there's 8 total individual commands and only 7 outputs.
Hope this helps!

From the project description "The script files will be comprised of statements, one per line, that hold either variable declarations, commands, or desired computations" so it may be worth a Piazza question to clarify what the lab instructor stated.

Must've missed that, I guess its a bit conflicting when that's how the commands were used on my implementation but I'll update that since it probably doesn't make a difference since the parser implementation demonstrated would be able to handle both cases.


Not getting status code 200 generated when using actix-multiresponse

Hi,
I'm encountering some strange behavior when using actix-multiresponse, with the paperclip feature enabled.
My route's function looks like this:
#[api_v2_operation(tags(v1, sensor_alert))]
pub async fn get(data: WebData, path: web::Path<Path>, session: Session) -> WebResult<Payload<proto::Alert>> { ... }

with proto::Alert being derived from a .proto file using prost:
#[cfg_attr(feature = "serde", derive(serde::Serialize, serde::Deserialize))]
#[cfg_attr(feature = "paperclip", derive(paperclip::actix::Apiv2Schema))]
#[derive(Clone, PartialEq, ::prost::Message)]
pub struct Alert {
    #[prost(uint32, tag="1")]
    pub id: u32,
    ...
}

The paperclip and serde features are enabled for the proto crate here, so Apiv2Schema is derived.
The Payload struct looks like:
pub struct Payload<T: 'static + Default + Clone + PaperclipSupport>(pub T);

#[cfg(feature = "paperclip")]
pub trait PaperclipSupport: paperclip::v2::schema::Apiv2Schema + paperclip::actix::OperationModifier {}

It too has Apiv2Schema derived.
However, the generated spec omits the response entirely:
      responses:
        '400':
          description: Bad Request
        '401':
          description: Unauthorized
        '409':
          description: Conflict
        '429':
          description: Too Many Requests
        '500':
          description: Internal Server Error

I'm not getting any compiler errors, warnings or runtime warnings of any kind.
Environment

cargo: cargo 1.62.0-beta.2 (3f052d8ee 2022-05-12)
target: x86_64-unknown-linux-gnu
paperclip: 0.7.0
actix-web: 4.1.0
actix-multiresponse: 0.1.1
prost: 0.9.0

Looking in the generated spec, I do see something for Payload<T>, though it seems to ignore generics (is Apiv2Schema implemented incorrect for Payload<T>?):
  _Payload<>:
    description: |-
      Payload wrapper which facilitates the (de)serialization.
       This type can be used as both the request and response payload type.

       The proper format is chosen based on the `Content-Type` and `Accept` headers.
       When deserializing only the `Content-Type` header is used.
       When serializing, the `Accept` header is checked first, if it is missing
       the `Content-Type` header will be used. If both are missing the payload will
       default to `JSON`.

       # Errors

       When the `Content-Type` header is not provided in the request or is invalid, this will return a HTTP 400 error.
       If the `Content-Type` header, or `Accept` header is invalid when responding this will return a HTTP 400 error,
       however this is *not* done if both headers are missing on response.

       # Panics

       If during serializing no format is enabled
    type: object
    properties:
      organizations:
        type: array
        items:
          type: object
          properties:
            description:
              type: string
            id:
              type: integer
              format: int32
            name:
              type: string
          required:
            - id
            - name
    required:
      - organizations

Though the definition is never used.


Running Project Runs the Wrong File

When I select File>Run the browser opens another past project instead of the one that is currently opening. Happens every time. I've seen this on other threads, but no answer. Would love some help.

hey @Jasotasticon sorry that's happening. The reason we haven't addressed this properly yet is that I haven't been able to replicate the issue on my computer. Can you provide any more details about what's going on? Thanks.

I've had students also claiming this happens, but cannot replicate. my TA insists its a caching issue, but I cannot replicate it.

I had the same issue in yesterday's class.  The steps I took were this:

Multiple project windows open at once.
Closed one project, then File--> open
Opened a different project than had previously been open, and pressed play.
-Server launches and starts to play 1st sketch I had shown in beginning of class, not currently active project.

All project directories tested are located under the same directory branch (they're siblings).
Is there an easy way to find the specific bin version for debugging? Issues found on OS X Yosemite.
Sent from my mobile.

On Sep 24, 2015, at 5:06 PM, Ben Moren<EMAIL_ADDRESS>wrote:
I've had students also claiming this happens, but cannot replicate. my TA insists its a caching issue, but I cannot replicate it.
—
Reply to this email directly or view it on GitHub.

Thanks @indefinit - super helpful!


pmap(in_axes=None) of sharded_jit

Sharded device arrays support "replication", meaning that the same values are present on different devices without adding extra logical axes to the array. We use this for two things: pmap with arguments that aren't mapped and sharded_jit with values that aren't sharded. But they need to be kept separate, because they map to physical devices in different ways (one corresponds to XLA replicas and the other to XLA partitions). This is essential for supporting pmap(in_axes=None) nested over sharded_jit.
This change modifies ShardingSpec to keep these two kinds of replication separate, and sets up sharded device arrays to represent more complex nesting in the future.

Benchmarks:
---------Benchmark summary for pmap_shard_sharded_device_array---------
  nargs    nshards       mean     %std    relative    mean/baseline
-------  ---------  ---------  -------  ----------  ---------------
     10          8   0.126214  2.63241     1               1.06458
    100          8   0.414316  5.03662     3.28264         0.97376
    101          8   0.418775  1.55189     3.31797         0.994177
    500          8   1.74794   1.24838    13.849           1.01714
   1000          8   3.14312   0          24.9031          1.01287
   5000          8  12.0175    0          95.2155          0.998031
    100          2   0.45124   4.12967     3.57519         0.961089
    100          4   0.377792  5.10137     2.99326         1.00912
    100          8   0.412545  3.56588     3.26861         0.979343
    100        100   2.10578   0          16.6842          0.969329
    100        500   7.75881   0          61.4734          1.00793

---------Benchmark summary for pmap_shard_device_array---------
  nargs    nshards       mean       %std    relative    mean/baseline
-------  ---------  ---------  ---------  ----------  ---------------
     10          8  0.0699298  24.7994       1               0.982513
    100          8  0.401226    6.64842      5.73755         1.03594
    500          8  1.84981     0.133793    26.4523          0.990589
    100          2  0.168579    4.48474      2.41069         1.06458
    100          4  0.232695    3.79989      3.32755         1.0075
    100          8  0.382947    4.38658      5.47617         1.03151

---------Benchmark summary for pmap_shard_outputs---------
  nouts    nshards       mean       %std    relative    mean/baseline
-------  ---------  ---------  ---------  ----------  ---------------
     10          8   0.143022  6.94586       1               0.959435
    100          8   0.477052  4.61638       3.3355          0.940656
    500          8   1.77398   0.0725278    12.4035          1.00268
   1000          8   3.28001   0            22.9335          1.03544
   5000          8  13.2918    0            92.9352          1.01221
    100          2   0.356282  7.12572       2.49109         0.955783
    100          4   0.412894  2.61377       2.88691         1.05916
    100          8   0.508685  1.74183       3.55668         0.993058
    100        100   3.80903   0            26.6324          1.03359
    100        500  21.1306    0           147.743           1.01531

---------Benchmark summary for ShardedDeviceArray_indexing---------
indices_fn               mean     %std    relative    mean/baseline
------------------  ---------  -------  ----------  ---------------
integer_indices     0.0471937  15.9031       1             0.969116
integer_2D_indices  9.63122     0          204.078         0.987062

Seems like no significant regressions?

Yup looks like a no-op to me, the differences look like noise.


Feature/windows support

This adds windows support for omnibus_updater. Been running this in production for about 6 months and 3 chef-client updates for windows and linux have worked well.

fixed my fork missing the latest commits in develop branch and merged them into this branch.

realized I made a mistake with my branch and created merge conflict going to close this submit new Pull request when I get everything ironed out correctly.


Fix SpoonConverterTest

Currently SpoonConverterTest fails in CI, but not locally.

Different distributions and jdk versions didn't affect the outcome.

Hi @andre15silva
Failing test
Skipped in CI
Do you have the execution log? which is the assertion that fails?
Thanks
Matias

Hi @martinezmatias
Failing build
From what I understood yesterday, the issue is that Spoon locations are different in CI compared to locally or in Travis. So different raw outputs get mapped to different CtStatements.


partials do not work

Hi,
I have a bare minimum test Drab-powered app. In the index.html.drab I have
<%= render "navbar.html" %>

Then, next to index.html.drab I created navbar.html.drab with content
NavBar here

The compiler gives me this error:
== Compilation error in file lib/tgshop_web/views/cms_view.ex ==
** (FunctionClauseError) no function clause matching in :lists.flatten/1

    The following arguments were given to :lists.flatten/1:

        # 1
        {:__block__, [], [{:=, [], [{:tmp1, [], Drab.Live.EExEngine}, ["{{{{@drab-partial:gm4dsnzxhaytioi}}}}"]]}, [{:tmp1, [], Drab.Live.EExEngine}, {:case, [generated: true], [{:render, [line: 1], ["navbar.html"]}, [do: [{:->, [generated: true], [[safe: {:data, [generated: true], Drab.Live.EExEngine}], {:data, [generated: true], Drab.Live.EExEngine}]}, {:->, [generated: true], [[{:when, [generated: true], [{:bin, [generated: true], Drab.Live.EExEngine}, {:is_binary, [generated: true, context: Drab.Live.EExEngine, import: Kernel], [{:bin, [generated: true], Drab.Live.EExEngine}]}]}], {{:., [generated: true], [{:__aliases__, [generated: true, alias: false], [:Plug, :HTML]}, :html_escape]}, [generated: true], [{:bin, [generated: true], Drab.Live.EExEngine}]}]}, {:->, [generated: true], [[{:other, [generated: true], Drab.Live.EExEngine}], {{:., [line: 1], [{:__aliases__, [line: 1, alias: false], [:Phoenix, :HTML, :Safe]}, :to_iodata]}, [line: 1], [{:other, [line: 1], Drab.Live.EExEngine}]}]}]]]}]]}

    (stdlib 3.11.2) lists.erl:616: :lists.flatten/1
    lib/drab/live/eex_engine.ex:118: Drab.Live.EExEngine.handle_body/1
    lib/drab/live/engine.ex:17: Drab.Live.Engine.compile/2
    (phoenix 1.4.13) lib/phoenix/template.ex:355: Phoenix.Template.compile/3
    (phoenix 1.4.13) lib/phoenix/template.ex:166: anonymous fn/4 in Phoenix.Template."MACRO-__before_compile__"/2
    (elixir 1.10.1) lib/enum.ex:2111: Enum."-reduce/3-lists^foldl/2-0-"/3
    (phoenix 1.4.13) expanding macro: Phoenix.Template.__before_compile__/1

As an excuse, I am using Drab and Phoenix for first time!
Thanks a lot

Ah I think it doesn't handle top-level text in a file.  It assumes well formed HTML by default (that's how it decorates it for fast updates).  Try wrapping the NavBar here with NavBar here or some other element as appropriate and see if that works?  If it does then I may need to add some better error reporting.  :-)

I think I might see the problem looking in the code as well, let me try to push a fix...

cool, pls tell me when u pushed. Just try with
NavBar here
, same error...

I just pushed it to git, can you try using the master github branch as a dependency and see if that fixes it?  If not I'll keep looking.  If it works then I can make a release.  :-)

yay! works now, thanks a lot :+1:

Awesome!  Pushing a new release 0.10.4 now, expect it on hex momentarily.  :-)


added ORTModelForSpeechSeq2Seq support to optimizer

What does this PR do?
ORT optimization support for whisper was added here #986 but ORTOptimizer didn't support ORTModelForSpeechSeq2Seq.
@regisss I can add tests if necessary.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

@IlyasMoutawwakil Yes let's add some tests for this. Maybe you can take seq2seq models as a template for the tests: https://github.com/huggingface/optimum/blob/a6951c17c3450e1dea99617aa842334f4e904392/tests/onnxruntime/test_optimization.py#L208

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


@conda-forge-admin, please add user @avaldebe

[x] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @avaldebe in conda-forge/pyaerocom-feedstock#11.


Remove Zalando Lisbon office

Zalando Lisbon office closed recently, so removing it from the file :)

Thanks @pedrorijo91!


Current support for data scientists is not enough

VSCode Version:1.18.1
OS Version:windows7

I'm a data modeler and I have been using Rstudio,MATLAB and Spyder for years, I've already attempted to use jupyter notebook, but i can't even create a project with notebook, then i started programming in text editor like sublime,Atom and vscode, and finally I was attracted by vscode.
I can open a new window for jupyter qtconsole from the terminal in vscode, but I wish I can use qtconsole in vscode rather than open a new window. Of course I can start original ipython in vscode, but ipython will open a new window for image when I plot function curves.
vscode is a brilliant text editor, and it will be more powerful for data scientists with a qtconsole in vscode.

@deerainw
Since QTConsole is based on QT GUI framework, it needs to run in an environment where the window
is controlled by QT and can output the GUI objects.  The integrated terminal in VSC is based on
xterm which is a character based console interface.  I think that the only way to support QT
would require an extension.  Even an extension  probably cannot directly to this since the extensions
need to render HTML content within the interface.

Please look at spyder -- especially its Variable Explorer:
https://pythonhosted.org/spyder/variableexplorer.html
I know we can use VSC's debugger, but you have to run the entire script and you cannot edit.
I know we can set breakpoints in the VSC debugger, but since we can "Run selection/line in integrated terminal," it would be so much more convenient to be able to explore the object(s) in the integrated terminal.
Please also look at RStudio.  "Data people" there are begging them to also support Python:
https://community.rstudio.com/t/r-python-in-ide/279
but I do not think that this will happen to the community's satisfaction soon (through various "workarounds," there currently are some "emulations").  It would be nice for VSC could add a "variable explorer" (especially for pandas DataFrames).  Then for data scientists, it would look a lot more like sypder and/or RStudio.

Integrated console (with intellisense) and ability to display graphs and tables would be extremely helpful to Python and R users

@MikhailArkhipov the terminal is built using xterm.js, and looks like there's no immediate plan to support this (https://github.com/xtermjs/xterm.js/issues/614#issuecomment-362180939). Hopefully this will change.

@omri374 is there any status on a PyCharm-like explorer window for pandas?  Would be great to have a colorful and scrollable DataFrame object.


bash script for creating eot (zero byte) file for all the folder coming in (getting copied)

Can anyone help me creating Bash script for creating eot (zero byte) file for all the folder coming (getting copied) into the Linux centOs.
Suggestion:
1.> script need to understand if the folder is been completely copied
2.>Create a file name "folder.eot" (zero byte) in the same place
Response Required, Thanks.

This is best for stackexchange or stackoverflow. Not the issue tracker of an open source project that maintains a Bash style guide.
Try asking your questions politely over here:

https://stackoverflow.com/questions/tagged/bash
https://unix.stackexchange.com/questions/tagged/bash

I'm closing this issue as it's a question unrelated to this project.


New version: HelmutBuhler.8GadgetPack version 38.0

Created by 🥟 Dumplings in workflow run #10533.

Log
Updated: 37.0 → 38.0
No ReleaseTime and ReleaseNotes (en-US) for version 38.0
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
The manifests for the last version 37.0.0 will be removed. Reason: This task is configured to remove the last version
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

(Automated response - build 931.)

@wingetbot run


pixel one or xl?

can we get a support for pixel one or xl ? ...for original quality

Heya,
I have already made an OG Pixel spoof in December.
It has not been updated since then because Google discontinued updates for the device, so no updated fingerprints.
https://sourceforge.net/projects/pixel-spoof/files/OG%20Pixel%20Spoofs/

but it's for android 11.... how do i change  it to work in android 10 ??

It works for both android 10 and 11.


Rework "code pages" article

There were a few typos in this article which I've fixed, and then I edited the text a little for clarity.
I've edited the information about Unicode to make it more up-to-date with current times.

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

globalization/encoding/code-pages.md
78
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

globalization/encoding/code-pages.md
78
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

globalization/encoding/code-pages.md
78
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

I think this page should be superseded by https://learn.microsoft.com/en-us/windows/win32/intl/code-pages

This page was rewritten, so almost all of the changes in this PR no longer apply. Closing.


fix parameter files for MPI-ESM1-2-HR

[ ] closes #xxxx
[ ] tests added / passed
[ ] docs reflect changes
[ ] passes flake8 downscale tests docs
[ ] entry in HISTORY.rst

I wanted to push MPI-ESM1-2-HR through a second round of runs, but I think the parameter files are out of date. According to Diana's dropbox table here : https://www.dropbox.com/scl/fi/lhxglqclb1xekg2kug6al/downscaling_project_status.xlsx?dl=0&rlkey=exts0qyu0loxr29eubi12f5p8, it only has ssp126 and ssp585 (I didn't directly check in CMIP6-on-the-cloud, need to do that later today).
Therefore, in this PR, I filtered the parameter files for that model.
Note I swapped the ssp in historical. I wanted to check with you that this is not a problem with respect to our methods.
Thanks !

Yeah, we need an SSP record, but I'm not sure we want SSP126 on this target: historical run in your change... In this case, this is the SSP we append to the historical simulation record. Usually, it's SSP370 or SSP245. Using SSP126 might be a deal breaker.

@emileten and @brews It's definitely not ideal to append SSP1-2.6, but it's only the first ten years of the SSP run for appending to historical and those ten years are going to differ very little from the SSP2-4.5 and SSP3-7.0 runs, so this is fine. We'll document this in our public release, paper and any accompanying internal documentation as well.

Thanks @dgergel ! Can you just confirm in addition that the parameter file looks all good ? Requested your review.
Then I will merge and run with this set up.

I checked the input data is in the catalog. All the records appear to exist.
%conda install intake-esm
%pip install git+https://github.com/brews/dearprudence

import dearprudence as dp

runs = dp.read_params("MPI-ESM1-2-HR-pr.yaml")

for r in runs:
    print(f"Checking {r}")
    dp.cmip6_catalog_has(r.historical)
    dp.cmip6_catalog_has(r.ssp)
    print("These records exist 👍\n")


Sample tracker multiple times during the thread.

To improve performance, sample tracker multiple times, once at the beginning of the thread, and once in the PreRender functions in the HMD plugins.  GearVR support shows a simple implementation of this

We are doing this now, consistent with the other plugins.


hedgedoc: 1.9.0 -> 1.9.4

Updated through the provided shell script.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@WilliButz Could you help on this? I'm unable to build this thing locally.

@GrahamcOfBorg build hedgedoc

@GrahamcOfBorg build hedgedoc

@GrahamcOfBorg build hedgedoc

@GrahamcOfBorg build hedgedoc

Fixed.

Fixed

This PR wasn't tested on a real system, right? The build instructions changed and the editor cannot be loaded after this update. Going to fix it myself.

I locally tested the thing, everything seems right at first sight. Today when deploying in production. We noticed that there was an issue. I asked in the hedgedoc matrix and our build procedure is wrong. We have to use yarn instead of npm. I tried to do it, but I have the same issue locally. Help is very welcome at https://github.com/NixOS/nixpkgs/pull/182607

We have to use yarn instead of npm.

@drupol We are using yarn, so not sure what they meant by this.

We have to use yarn instead of npm.

@drupol We are using yarn, so not sure what they meant by this.

The build phase uses npm commands.

The build phase uses npm commands.

npm build is an alias to npm run build which is the same for yarn build and yarn run build. Also building the sqlite3 extension is also the same. Something is wrong with building hedgedoc itself or webpack.

Our hedgedoc includes this file which upstream does not. Something with our vendoring is wrong.
webpack:///node_modules/js-yaml/dist/js-yaml-exposed.mjs

fixed in #182643


Release: failing due to kustomize file already exists

What happened?
kustomize create --resources resources.yaml
  cd ..
  if [[ $(git status --porcelain) ]] ; then
    git add .
    git commit -m 'update kustomize/operator'
    git push
  fi
  shell: /usr/bin/bash -e {0}
Error: kustomization file already exists

What did you expect to happen?
tests to pass
How can we reproduce it (as minimally and precisely as possible)?. Please include values file.

$ helm get values <redpanda-release-name> -n <redpanda-release-namespace> --all
# paste output here

Anything else we need to know?
This is an issue in the release process, not any particular chart
Which are the affected charts?
No response
Chart Version(s)

$ helm -n <redpanda-release-namespace> list
# paste output here

Cloud provider

Fixed in #683


Show version and release date

The version is shown on both the card and the extension detail page. The release date is shown just on the extension detail page.
Getting the date is non-trivial. The best bet seems to be the procedure described in https://stackoverflow.com/questions/69790966/api-metadata-to-find-the-release-date-of-a-maven-artifact.  https://central.sonatype.org/search/rest-api-guide/ has more documentation on the API. The model of asking maven central for the information breaks down if the artifact isn't in maven central; in that case we'll need something in the registry to point to the hosting maven repo, and then we can go query it.
Resolves #16 (although the age is only implicit, because we show the date - I think that's close enough, do you agree @maxandersen ?)
Example UI, with the changes:

Good start!


MSPSDS-26: Update Travis environment variables

Pull Request Test Coverage Report for Build 913

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

Totals

Change from base Build 912:
0.0%

Covered Lines:
1541

Relevant Lines:
1679

💛  - Coveralls


Ubuntu 24

If possible could you enable this for kubuntu 24.04

@rw-bowman  Done. Please sync and try to upgrade.

There seems to be an issue with the upgrade :dpkg: error processing archive /tmp/apt-dpkg-install-rvjBkQ/07-pipewire-bin_1.0.7-1~ubuntu24.04_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man7/libpipewire-module-access.7.gz', which is also in package libpipewire-0.3-modules:amd64 1.0.5-1

try sudo apt-get -o Dpkg::Options::="--force-overwrite" install

--fix-broken-install seemed to fix it

Please upgrade 1.0.7-3 is released with fixes

Here the update fails with the same error for version 1.0.7-3, even running the two proposed commands. But merging the two commands worked: sudo apt-get -o Dpkg::Options::="--force-overwrite" --fix-broken install


Attempted to resolve template, which was expected to be a component, but nothing was found.

I'm seeying above error after installing an setting up the simplest example... The map works without the markerCluster tag.
<GMap
          @styles={{this.mapStyle}}
          @disableDefaultUI={{true}}
          @zoomControl={{true}}
          @zoomControlOptions={{hash position=this.google.maps.ControlPosition.TOP_RIGHT}}
          @zoom={{9}}
          @onceOnIdle={{this.onLoadMap}}
          class="h-100"
          as |map|
        >
          <map.markerClusterer as |cluster|>

            {{#each this.markers as |location|}}
              <cluster.marker @lat={{location.lat}} @lng={{location.lng}} />
            {{/each}}

          </map.markerClusterer>

        </GMap>

Feels like an glimmer error somehow... What am I missing?

Hi @basz, which version of Ember are you on?

3.28.8

It sounds like there’s a component 'template' call somewhere 🤔 ember-google-maps has this as a placeholder for adding custom components, but it should be removed during the build process.
Is there anything special about your build process? Do you use Embroider? If so, what version are you using?

I see that works indeed.
not embroider (yet), but did enable typescript.

It’s probably this line:  https://github.com/sandydoo/ember-google-maps/blob/37949c608a6d60a0ab5cbfc5ab6c2c4a48da4d22/addon/components/g-map.hbs#L19
It’s used as a template to yield more components, and is then removed here: https://github.com/sandydoo/ember-google-maps/blob/37949c608a6d60a0ab5cbfc5ab6c2c4a48da4d22/lib/ast-transforms/addon-factory.js#L3-L11
You could try adding a console.log(pairs) in addon-factory.js and see what GMap is yielding at build time.

My guess is that there’s something strange going on in the build system. I haven’t seen anything like this before.
The pre-processors are set up here: https://github.com/sandydoo/ember-google-maps/blob/37949c608a6d60a0ab5cbfc5ab6c2c4a48da4d22/index.js#L210-L232
Are you able to share your app or some part of it? Privately?

I’m not sure what that error is about. Maybe try updating your lockfile? ember-google-maps is a peer dependency with a minimum version constraint, so your app should be using v5.

hm.becuase it is also listed as a dependency? But i admit i don't understand peerDependencies.
Anyhow, i tried to update the lockfile. ensure 5 was loaded. same.
Unfortunatly I can not share this repo...