InferDM with snm_1d

Hello,
Thanks again for your work on dadi-cli!
I have encountered a circular issue with the InferDM module, where if I want to infer the standard neutral model in 1D (snm_1d), upper and lower bounds are required, but I beleive there are no such paramters required for this model?
Error with no --lbounds or --ubounds
dadi-cli InferDM --fs <input>.fs --model snm_1d --output <output>.snm_1d.demo.params --optimizations 1 --nomisid
usage: dadi-cli InferDM [-h] --fs FS [--p0 P0 [P0 ...]] --output-prefix OUTPUT_PREFIX [--optimizations OPTIMIZATIONS] [--check-convergence] [--force-convergence] [--work-queue WORK_QUEUE WORK_QUEUE] [--port PORT] [--debug-wq] [--maxeval MAXEVAL]
                        [--maxtime MAXTIME] [--cpus CPUS] [--gpus GPUS] [--bestfit-p0-file BESTFIT_P0] [--delta-ll DELTA_LL] --model MODEL [--model-file MODEL_FILE] [--grids GRIDS GRIDS GRIDS] [--nomisid] [--constants CONSTANTS [CONSTANTS ...]]
                        --lbounds LBOUNDS [LBOUNDS ...] --ubounds UBOUNDS [UBOUNDS ...] [--global-optimization] [--seed SEED]
dadi-cli InferDM: error: the following arguments are required: --lbounds, --ubounds

Error with --lbounds and --ubounds set
dadi-cli InferDM --fs <input>.fs --model snm_1d --lbounds 0 --ubounds 1 --output <output>.snm_1d.demo.params --optimizations 1 --nomisid
Traceback (most recent call last):
  File "/opt/anaconda_dadi-cli/bin/dadi-cli", line 8, in <module>
    sys.exit(main())
  File "/opt/anaconda_dadi-cli/lib/python3.10/site-packages/dadi_cli/__main__.py", line 1603, in main
    args.runner(args)
  File "/opt/anaconda_dadi-cli/lib/python3.10/site-packages/dadi_cli/__main__.py", line 133, in run_infer_dm
    args.lbounds = _check_params(args.lbounds, args.model, "--lbounds", args.misid)
  File "/opt/anaconda_dadi-cli/lib/python3.10/site-packages/dadi_cli/__main__.py", line 1482, in _check_params
    raise Exception(
Exception:
Found 1 demographic parameters from the option --lbounds; however, 0 demographic parameters are required from the snm_1d model
You might be using the wrong model or need to add --nomisid if you did not use ancestral allele information to polarize the fs.

Error with --lbounds and --ubounds empty
dadi-cli InferDM --fs <input>.fs --model snm_1d --lbounds --ubounds --output <output>.snm_1d.demo.params --optimizations 1 --nomisid
usage: dadi-cli InferDM [-h] --fs FS [--p0 P0 [P0 ...]] --output-prefix OUTPUT_PREFIX [--optimizations OPTIMIZATIONS] [--check-convergence] [--force-convergence] [--work-queue WORK_QUEUE WORK_QUEUE] [--port PORT] [--debug-wq] [--maxeval MAXEVAL]
                        [--maxtime MAXTIME] [--cpus CPUS] [--gpus GPUS] [--bestfit-p0-file BESTFIT_P0] [--delta-ll DELTA_LL] --model MODEL [--model-file MODEL_FILE] [--grids GRIDS GRIDS GRIDS] [--nomisid] [--constants CONSTANTS [CONSTANTS ...]]
                        --lbounds LBOUNDS [LBOUNDS ...] --ubounds UBOUNDS [UBOUNDS ...] [--global-optimization] [--seed SEED]
dadi-cli InferDM: error: argument --lbounds: expected at least one argument

I'm not sure if I am using this model correctly, but I would be most grateful of any advice you can offer on this issue?
Many thanks

Hi @bibionid, thanks for bringing this to our attention! I've merged a fix for the standard neutral models, so you shouldn't require boundaries unless you want to fit a misid parameter. Let us know if you run into any other issues.

Hi @tjstruck,
Thank you very much for your work on this issue.
I have downloaded the new version and have tested the command
dadi-cli InferDM --fs ${input}.fs --model snm_1d --output ${output} --optimizations 1 --nomisid

Unfortunately this generates the error
Traceback (most recent call last):
  File "/opt/anaconda_dadi-cli/bin/dadi-cli", line 8, in <module>
    sys.exit(main())
  File "/opt/anaconda_dadi-cli/lib/python3.10/site-packages/dadi_cli/__main__.py", line 1634, in main
    args.runner(args)
  File "/opt/anaconda_dadi-cli/lib/python3.10/site-packages/dadi_cli/__main__.py", line 139, in run_infer_dm
    model = dadi.Numerics.make_extrap_func(func)([], fs.sample_sizes, args.grids)
  File "/opt/anaconda_dadi-cli/lib/python3.10/site-packages/dadi/Numerics.py", line 374, in extrap_func
    result_l = list(map(partial_func, pts_l))
TypeError: 'NoneType' object is not iterable

I'd be most grateful of any input you might have on this? Am I calling the snm_1d correctly?
Many thanks

To add to this, an output was created, but only containing a header

@bibionid, currently, with how dadi-cli is implementing models from dadi, you will need grid points even for the snm_1d model. You should be able to add something like --grids ns+5 ns+10 ns+15, where ns is the sample size of your data.
Since you aren't optimizing anything with a simple standard neutral model, only one output file will be produced. The output (for now) will be: <output>.InferDM.simple.snm.txt.

Hi @tjstruck,
Thank you for looking at this issue and suggesting this soluiton. I have implemented the --grids flag and can confirm I got the expected output as you suggest.
I wanted to flag that the --grids flag is not mentioned in the documentation of InferDM in the readme, and would suggest this could be a helpful addition if it is necessary for accurate model inferance - I was able to derive model output without the flag in place from all other 1D models.
Again, many thanks for your work on this awesome tool!

Thanks for the heads up on the documentation and your experience with other models, @bibionid! I've pushed another up for the snm models to automatically generate grids like the other models.


backup.tar link is broken

The link to backup.tar is not working.
This link:
https://onedrive.live.com/download?cid=0C78B7DE6C569D7B&resid=C78B7DE6C569D7B!191&authkey=AP183o4PlczZR78
results in this:
"This item might not exist or is no longer available
This item might have been deleted, expired, or you might not have permission to view it. Contact the owner of this item for more information."

Looks like it is now working

It's not working! I cannot download the file.
This link:
https://onedrive.live.com/download?cid=0C78B7DE6C569D7B&resid=C78B7DE6C569D7B!191&authkey=AP183o4PlczZR78

@btekin
Hello, this link is broken when the download is not complete.
https://onedrive.live.com/download?cid=0C78B7DE6C569D7B&resid=C78B7DE6C569D7B!191&authkey=AP183o4PlczZR78
I have tried it many times, but there is still no way to download the file (backup.tar).


Create new deployment with all files by enabling enable-duplicate-filtering

Is your feature request related to a problem? Please describe.
Currently, when using Start Instance Tool a deployment is taking place. If an existing deployment exists, this might even create a new deployment. However, not all files being part of the deployment will be part of the deployment. This can break features like forms.
In order to avoid this behavior, the duplicate-filtering shall be enabled in this situation:
A flag indicating whether the process engine should perform duplicate checking for the deployment or not. This allows you to check if a deployment with the same name and the same resouces already exists and if true, not create a new deployment but instead return the existing deployment. The default value is false. source
Describe the solution you'd like

Set enable-duplicate-filtering to true when deploying
Don't set deploy-only-changed

Describe alternatives you've considered
n/a
Additional context
Discussed here

I will evaluate the different cases we have and give a summary so to validate what is put in the issue, prior to doing the actual change

This is exactly what we do already, right? I mean we have deploy-changed-only enabled which enables duplicate filtering (cf. docs).
Or am I missing anything here.

Enabling duplicate filtering and disabling deploy-changed-only would yield a different behavior, however that is not what's specified in this issue.

See https://github.com/camunda/camunda-modeler/pull/2137#issuecomment-801714355

Will be handled as part of this PR: https://github.com/camunda/camunda-modeler/pull/2137


Error on install: cannot access `fn_functions': No such file or directory

I got the following error when trying an install:
   loading fn_functions...chmod: cannot access `fn_functions': No such file or directory
./tf2server: line 86: /home/tf2server/functions/fn_functions: No such file or directory
./tf2server: line 98: fn_getopt: command not found

Little bit of investigation led me to add '--no-check-certificate' to the wget command in the tf2server script. But that's probably not a desirable solution right?

delete the "functions" folder and run the script again

Correct. What distro are you running? It must be an older one. I want to add the option in to use --no-check-certificate for the older distros but I need to know which ones

I'm having the same errors except in the csgoserver install.
Tried the following with no resolution:

Tried manually creating the functions/fn_functions directory.

Tried what ScottSmudger said, removing the functions directory. No help.

What else can I try?

I have not completed installation yet, but I did get past this error by adding "--no-check-certificate" to line 109 of csgoserver script.

Please can you confirm what your distro is

LGSM has partly moved to curl which may resolve the issue. However wget is still used in places. I recommend upgrading the distro of as suggested adding --no-check-certificate to any wget commands


Blog app - controllers specs

In this Project Milestone -:

Write tests for controllers.

Set up tests on the controllers recently added to the Blog app.

Make sure that for each action you check:
If response status was correct.
If a correct template was rendered.
If the response body includes correct placeholder text.

All tests are passing screenshot attached for your kind reference.

Thanks @joel-kalema :)


Adap 496/add test connection mode to debug

resolves #7104 (among other things like ADAP-6)
Description
dbt debug has been reworked from the inside out. It's ready for further extension for future flags. It supports new methods. I'm also proposing removal of old code.
usage: dbt debug and dbt debug --connection
Summary of changes
see output screenshots in this comment

the flag that does connection testing only
adapter version is added
standardized _connection_keys and debug_query() in all 4 our of our adapters (see bigquery redshift snowflake spark)

Solicitation for feedback at this stage

Comments around the output, workflow, and code design!
Code review around basically everything -- we just have an open conversation around the future of --config-dir

Next steps for me / what's left

[X] double check debug_query in all repos overrides fine (so far, so good on Snow and PG)
[X] ensure _connection_keys makes sense for all our 4 supported repos
[X] update the tests in this repo

Checklist

[X] I have read the contributing guide and understand what's expected of me
[X] I have signed the CLA
[X] I have run this code in development and it appears to resolve the stated issue
[X] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[X] I have run changie new to create a changelog entry

I'm not sure I'm a fan of --test-connection-only.
If dbt debug does 4 things. When there is no flag it does all of them, when you use flag it does only the one you explicitely ask for:

dbt debug  does all
dbt debug --connection tests the connection
dbt debug --config-dir this one actually exists already
dbt debug --configuration checks the yml files
dbt debug --dependencies check the dependencies
dbt debug --info prompt versions and file paths and such
dbt debug --info --dependencies does 2 things

Right now we only implement --connection, but I like the potential picture that paints.
@dbeatty10, @dataders what's your take?

@dbeatty10, @dataders what's your take?

Agreed with your take @Fleid ✅
I appreciate a couple things in your proposal:

That particular flag is easier to type since it is shorter (--connection instead of --test-connection-only)
Gives flexibility to choose which flags to flip on by having them each be independent of each other

The downside is that it could lead to gymnastics from an implementation perspective. Maybe all the flags would need to default to None instead of True. Then if all are None, then treat as-if all were True. If any are not None, then can leave the flags as-is.
Another related downside is that we're refining this on-the-fly here and I want to be thoughtful to @VersusFacit.
@VersusFacit would you prefer that we send this issue back to refinement or continue having this discussion within this PR?

Thanks for prompting us to take this back to refinement. 🙏 I'm going to talk to Florian about that ASAP since we need a sensible flag design. I like shades of this, but the code under the code makes this nontrivial, believe it or not. Moreover, this might actually be too much overhead for users.
Things we can consider:

Making the underlying code execute in an order agnostic way (surprisingly tough lift of hard complexity)

Can these flags be order agnostic on the command line and then be processed in order (this is so unclear right now, and I suspect 'no')

would we then have to sort the tasks internally?

How can we make these flags order agnostic when certain commands are dependencies of each other? (spoiler:

Adding something that explains the order of options (easier to implement, but leaves us with some spaghetti code)
Choosing which buckets to group similar items into so that we end up with fewer flags
dependency hell not a fun place to be)

Note this flag and such is based on recommendations from #7104, which is to say we'll have to be intentional here in changing the experience even further (i.e. beyond original scope).
Like I said, I'm going to talk this over internally, but this interface change involves a big(ger) departure from the status quo above and below the hood 🖖

Talked with Florian. For this PR, we are going to stick to --connection which amounts to a mere cosmetic change in design. However, there is a hunger when resources are available to make flags more flexible. TBD at a later date!

So --config-dir does something than we probably all expected it to -- also it's broken #7774 . I've got a fix for this branch here.
However, it's job is to make you a command to show you how to open a window to your profiles dir file. This is 6 year old code and clearly from the early days of dbt (context given in the bug issue linked above).
What I think we want this command to do is to show us the command dir the profiles.yml is being searched for. I can make that design change with all your sign off @Fleid @dbeatty10 . If we want something else that's quick, let me know here, or if bigger, let's make an issue to figure out this (and other wishlist) dbt debug flags.

Well, after staring at this code, considering future next steps, and seeing a plate of 🍝 code (i.e. the way state variables in this class were handled is understated but so confusing/conflicting) it's practically impossible to debug code.
I therefore gave it a deep refactor, and I strove to make it far easier to track what's happening. I could tweak knobs more, but the 80% has been reached.
Test cases:

existing unit tests
dbt debug
dbt debug --connection
dbt debug --profiles-dir NOPE # to see how it fails
dbt debug after commenting out my dbt_project.yml
dbt debug after commenting out my profiles.yml

The behavior in all cases is cogent or more often exactly matches what the "stock" debug task is on main today. Because of how confusing the existing code is, how I've recoded this may see some minor adjustment to logging (e.g. changing order of lines, a newline here, a slightly different wording there).

Hey @VersusFacit,
So you're proposing to yank --config-dir out, and replace it by 2 new options?
I'm a bit skittish about doing that here to be honest. It's a big enough change in the interface that it should be in its own issue.
So I would go through this PR just adding --connection, then fix --config-dir via that other issue (not you, whoever picks it up from Support Rotation), then opening another issue/pr with your most recent ideas (I like them btw).

Pardon me, I was merely electing removal of --config-dir because it doesn't seem to serve any purpose.
--profile-dir and --project-dir already exist

@VersusFacit I don't know how often dbt debug --config-dir is used, but its documentation is here:

The --config-dir option to dbt debug will show the configured location for the profiles.yml file and exit

Since removing it would be a breaking change, I agree with you and @Fleid to leave it in this PR and then split that into a separate issue for further discussion.

@dbeatty10 , good find on the docs! Weird that and no other flags are documented. It's a shame really. I can make sure there's a docs ticket out of this merge that we change that 😄
And the changelog here has been duly changed!

🚚  --config-dir background and code has been moved to here


[安装问题] ImportError: dlopen: cannot load any more object with static TLS

python -m pip install paddle-rec -i https://mirror.baidu.com/pypi/simple
Building wheels for collected packages: pathlib
Building wheel for pathlib (setup.py) ... done
Created wheel for pathlib: filename=pathlib-1.0.1-py3-none-any.whl size=14348 sha256=1a742bbaae9155c36eefeaa0b66852843bdb4242f4b650bb96cf9b7887819ff6
Stored in directory: /home/work/.cache/pip/wheels/ea/c2/62/0ae2836c6f4c45d02165aa3ae1e864f91b774dadc8ec9ec3ee
Successfully built pathlib
Installing collected packages: astor, numpy, opencv-python, graphviz, objgraph, Pillow, pyparsing, kiwisolver, six, python-dateutil, cycler, matplotlib, decorator, protobuf, funcsigs, pathlib, click, joblib, tqdm, regex, nltk, PyYAML, rarfile, wcwidth, prettytable, idna, urllib3, chardet, requests, gast, scipy, paddlepaddle, paddle-rec
Successfully installed Pillow-8.0.1 PyYAML-5.3.1 astor-0.8.1 chardet-3.0.4 click-7.1.2 cycler-0.10.0 decorator-4.4.2 funcsigs-1.0.2 gast-0.3.3 graphviz-0.14.2 idna-2.10 joblib-0.17.0 kiwisolver-1.3.0 matplotlib-3.3.2 nltk-3.5 numpy-1.19.2 objgraph-3.5.0 opencv-python-<IP_ADDRESS> paddle-rec-<IP_ADDRESS> paddlepaddle-1.8.5 pathlib-1.0.1 prettytable-1.0.1 protobuf-3.13.0 pyparsing-2.4.7 python-dateutil-2.8.1 rarfile-4.0 regex-2020.10.23 requests-2.24.0 scipy-1.5.3 six-1.15.0 tqdm-4.51.0 urllib3-1.25.11 wcwidth-0.2.5
python
Python 3.7.9 (default, Aug 31 2020, 12:42:55)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.

import paddle
/home/work/miniconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/core.py:194: UserWarning: Load /usr/lib64/libgomp.so.1 failed
warnings.warn("Load {} failed".format(dso_absolute_path))
Traceback (most recent call last):
File "", line 1, in
File "/home/work/miniconda3/envs/paddle/lib/python3.7/site-packages/paddle/init.py", line 37, in
import paddle.complex
File "/home/work/miniconda3/envs/paddle/lib/python3.7/site-packages/paddle/complex/init.py", line 15, in
from . import tensor
File "/home/work/miniconda3/envs/paddle/lib/python3.7/site-packages/paddle/complex/tensor/init.py", line 15, in
from . import math
File "/home/work/miniconda3/envs/paddle/lib/python3.7/site-packages/paddle/complex/tensor/math.py", line 15, in
from paddle.common_ops_import import *
File "/home/work/miniconda3/envs/paddle/lib/python3.7/site-packages/paddle/common_ops_import.py", line 15, in
from paddle.fluid.layer_helper import LayerHelper
File "/home/work/miniconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/init.py", line 35, in
from . import framework
File "/home/work/miniconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/framework.py", line 35, in
from . import core
File "/home/work/miniconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/core.py", line 273, in
raise e
File "/home/work/miniconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/core.py", line 243, in
from .core_avx import *
ImportError: dlopen: cannot load any more object with static TLS

【miniconda3 安装的 python3.7】

去掉https://mirror.baidu.com/pypi/simple，直接python -m pip install paddle-rec


Handle deactivated user

[ ] Content by deactivated users should be "closed"
[ ] Don't allow deactivated user to login and give proper error message

Invalid, closed for now


Exchanger - CurrencyFreaks [SOLVED]

Implement Exhanger for Currency Freaks
link currencyfreaks.com

1.2.0


JobScheduler::new() - CantInit Error

Hi,
Thx for the great work.
We just update to 0.7.2. The call to JobScheduler::new() in the code below fails with a CantInit error.
Are we missing something?
Thx for your help
Emmanuel
tokio::spawn(async move {
	info!("spawning cron job");
	let sched = JobScheduler::new().expect("failed to create job scheduler");
	let _ = sched.add(
		Job::new_async(
			move |_uuid, _l| {
    			Box::pin(async move {
   					info!("job started);
				})
			},
		).expect("failed to create async job"),
	);
	if let Err(e) = sched.start() {
   		error!("failed to start scheduler: {:?}", e);
	}
});

Hi @ev94
Thanks for the bug report. Did this code compile at all? You're missing the cron text for the Job::new_async(, ) code.

Hi @ev94
I could replicate the problem.
For some reason it seems like init-ing the scheduler inside a tokio::spawn causes a block on the async-sync code.

I've reached out to the Rust reddit community on this. I don't know how to resolve this issue apart from marking all the functions as async fn's and then breaking the API of this library.

https://www.reddit.com/r/rust/comments/vvn5fp/tokio_async_sync_bridging_causes_block/ FYI

Hi @mvniekerk
Thanks for your feedback. So a possible solution is to init the scheduler outside of the tokio::spawn and then to move it to the spawn and start it?
let sched = JobScheduler::new().expect("failed to create job scheduler");
let _ = sched.add(
               Job::new_async(
		app_config.load_data_cron.as_str(),
			move |_uuid, _l| {
    			Box::pin(async move {
   			   info!("job started);
			})
		},
	).expect("failed to create async job"),
);
tokio::spawn(async move {
	info!("starting  cron jobs");

	if let Err(e) = sched.start() {
   		error!("failed to start scheduler: {:?}", e);
	}
});

Hi @ev94
Please check 0.8.0. I've made an example that covers your use case. Note that the API did change accordingly


Rudimentary documentation

What's the best way to document the proto files and the shim C++ files? It would be nice to automatically generate HTML docs for future interface writers.

How about this one: https://github.com/estan/protoc-gen-doc/

That looks great.
I suppose we also need to write & generate documentation for the shim
functions.
On 12/28, Krzysztof Sakrejda wrote:

How about this one: https://github.com/estan/protoc-gen-doc/

Reply to this email directly or view it on GitHub:
https://github.com/sakrejda/protostan/issues/5#issuecomment-167629156

Yep, I think using whatever Stan uses for those is fine (doxygen?)

Had started working on this, didn't realize I didn't claim it.

Turns out protoc-gen-doc is not straightforward to install from source so I can't just add it as a submodule and make it go.  It relies on qmake to produce the makefile and the qmake project file is hard-coded to look for system libraries.  I'm not going to go through incorporating it into the makefile at this point.  We can follow this format for writing the documentation comments and it'll be easier to install once protobuf-3 is the mainline system protobuf (so in a few to six months (?)).


MS.AAD.7.6v1 criticality in ScubaGear report does not match the baseline policy

🐛 Summary
Policy MS.AAD.7.6v1 shows the criticality of Should in the ScubaGear report Criticality column, but it is supposed to be a Shall based on the policy.
Any helpful log output or screenshots

@ahuynhMITRE Can you please have Elaine and Mark check the rest of AAD to make sure that the criticalities in the Criticality column match up with the policies? Also do the same for the other products. Thank you!

@ahuynhMITRE Looks like the code fix for this has been made. Is this ready for a quick PR and merge based on the single line/word change?

just double checking through the rest of the rego for all other products! PR will be up and ready soon!

The AAD 7.6 criticality is fixed in my open PR #584 so no need to do anything about that. If you find any mismatches in any of the other products, then a new PR might be necessary.

The AAD 7.6 criticality is fixed in my open PR #584 so no need to do anything about that. If you find any mismatches in any of the other products, then a new PR might be necessary.

I will close this issue then and create a new one if any arise!


All occurrences are MachineObservation

Are all of the occurrences truly basisOfRecord: "MachineObservation"? Was there a capture/release occurrence?

All the lines in the event file corresponded to the humanObservations. Those have now been added to the occurrence file


Initial QNN module

Somewhat working QNN (training plateauing, need to find optimal initial weights/learning rate/optimizer). Need to format as a module (step-by-step walkthrough) and test on IBM system.

Note: You can view jupyter notebooks and diffs between old vs new in Github Feature Preview. Click on your profile on the top right and click on Feature Preview. Then click on Rich Jupyter Notebook Diffs and enable it.
https://github.blog/changelog/2023-03-01-feature-preview-rich-jupyter-notebook-diffs/


GDAL mistakes one of the ENVI correction rasters for a JPEG and fails

@taliboliver found a very sneaky bug:
Reproduce with:
s1_cslc.py /home/staniewi/repos/COMPASS/talib-error/geo_runconfig_20230518_t042_088919_iw3.yaml

Warning 1: libjpeg: Corrupt JPEG data: 405 extraneous bytes before marker 0x6e (this warning can be turned as an error by setting GDAL_ERROR_ON_LIBJPEG_WARNING to TRUE)
Traceback (most recent call last):
  File "/u/aurora-r0/staniewi/miniconda3/envs/mapping-311/bin/s1_cslc.py", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/s1_cslc.py", line 53, in main
    run(parser.run_config_path, parser.args.grid_type)
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/s1_cslc.py", line 45, in run
    s1_geocode_slc.run(cfg)
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/s1_geocode_slc.py", line 92, in run
    cumulative_correction_luts(burst, dem_path=cfg.dem,
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/utils/lut.py", line 63, in cumulative_correction_luts
    compute_geocoding_correction_luts(burst,
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/utils/lut.py", line 212, in compute_geocoding_correction_luts
    [open_raster(raster_path) for raster_path in rdr2geo_raster_paths]
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/utils/lut.py", line 212, in <listcomp>
    [open_raster(raster_path) for raster_path in rdr2geo_raster_paths]
     ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/utils/helpers.py", line 351, in open_raster
    ds = gdal.Open(filename, gdal.GA_ReadOnly)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/u/aurora-r0/staniewi/miniconda3/envs/mapping-311/lib/python3.11/site-packages/osgeo/gdal.py", line 5297, in Open
    return _gdal.Open(*args)
           ^^^^^^^^^^^^^^^^^
RuntimeError: libjpeg: Unsupported marker type 0x6e

Apparently the x.rdr raster inside the corrections folder is getting misread by GDAL. I've seen a similar problem with other binary drivers here https://github.com/OSGeo/gdal/issues/4713 , but I think GDAL uses a heuristic to guess the driver, and if the contents of the file match the heuristic, it can guess wrong.

This issue would have been solved in #164 and #168. Can you confirm that you're using the most up-to-date version of COMPASS?

hmmm yes it looks like it's still happening on main:
(mapping-311) [staniewi@aurora COMPASS]$ git pull upstream main
git logFrom github.com:opera-adt/COMPASS
 * branch            main       -> FETCH_HEAD
Already up to date.
(mapping-311) [staniewi@aurora COMPASS]$ git log | head -3
commit 998e203378ffa423c9bbddf3dcd82be5df1922b2
Author: Seongsu Jeong<EMAIL_ADDRESS>Date:   Fri Aug 25 13:02:21 2023 -0700
(mapping-311) [staniewi@aurora COMPASS]$ s1_cslc.py /home/staniewi/repos/COMPASS/talib-error/geo_runconfig_20230518_t042_088919_iw3.yaml
journal: Starting s1_geocode_slc burst
journal: Starting geocoding of t042_088919_iw3 for 20230518
journal:
 -- DEM EPSG: 4326
 -- Output EPSG: 4326
journal:
 -- Processing block: 1
 --   - line start: 0
 --   - line end  : 111
 --   - dopplers near mid far: 0 0 0
journal:
 -- Actual DEM bounds used:
 -- Top Left: -122.872 37.6109
 -- Bottom Right: -121.521 36.9903
 -- Spacing: 0.000277778 -0.000277778
 -- Dimensions: 4866 2235
Topo progress (block 1/1): 100%
journal: Total convergence: 47880 out of 52392
Warning 1: libjpeg: Corrupt JPEG data: 405 extraneous bytes before marker 0x6e (this warning can be turned as an error by setting GDAL_ERROR_ON_LIBJPEG_WARNING to TRUE)
Traceback (most recent call last):
  File "/u/aurora-r0/staniewi/miniconda3/envs/mapping-311/bin/s1_cslc.py", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/s1_cslc.py", line 53, in main
    run(parser.run_config_path, parser.args.grid_type)
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/s1_cslc.py", line 45, in run
    s1_geocode_slc.run(cfg)
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/s1_geocode_slc.py", line 92, in run
    cumulative_correction_luts(burst, dem_path=cfg.dem,
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/utils/lut.py", line 63, in cumulative_correction_luts
    compute_geocoding_correction_luts(burst,
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/utils/lut.py", line 212, in compute_geocoding_correction_luts
    [open_raster(raster_path) for raster_path in rdr2geo_raster_paths]
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/utils/lut.py", line 212, in <listcomp>
    [open_raster(raster_path) for raster_path in rdr2geo_raster_paths]
     ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/u/aurora-r0/staniewi/repos/COMPASS/src/compass/utils/helpers.py", line 351, in open_raster
    ds = gdal.Open(filename, gdal.GA_ReadOnly)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/u/aurora-r0/staniewi/miniconda3/envs/mapping-311/lib/python3.11/site-packages/osgeo/gdal.py", line 5297, in Open
    return _gdal.Open(*args)
           ^^^^^^^^^^^^^^^^^
RuntimeError: libjpeg: Unsupported marker type 0x6e

Maybe there were different gdal versions being tested? I was also getting a RuntimeError as you said here https://github.com/opera-adt/COMPASS/pull/168/files#r1264289515 . The attribute error caught nothing.
Did we purposely leave out a gdal.UseExceptions() call in the module? I think that would be the reason for the attribute error- calling something on a None instead of GDAL raising the actual RuntimeError which might happen now by default in gdal 3.7

just clarifying: There's a chance that the docker SAS will run correctly as is. But I think if anything running the sas has called gdal.UseExceptions(), then it will error like mine did.

from osgeo import gdal

the Open() returned None, so it's an attribute error

gdal.Open('asdf').GetRasterBand(1)
ERROR 4: asdf: No such file or directory
Traceback (most recent call last):
File "", line 1, in
AttributeError: 'NoneType' object has no attribute 'GetRasterBand'

a real exception is called here

gdal.UseExceptions()
gdal.Open('asdf').GetRasterBand(1)
Traceback (most recent call last):
File "", line 1, in
File "/u/aurora-r0/staniewi/miniconda3/envs/mapping-311/lib/python3.11/site-packages/osgeo/gdal.py", line 5297, in Open
return _gdal.Open(*args)
^^^^^^^^^^^^^^^^^
RuntimeError: asdf: No such file or directory

Would you mind sharing the runconfig above, I'll try to reproduce the error on my end sometime next week.
Regarding UserExceptions():
I don't see anything wrong in using the default way of catching unexpected behavior, although it is not so much pythonic way of error handling. But, I agree your point that the behavior of GDAL can be confusing based on other modules we put in SAS. I think we might need to come up with some agreement about how to handle the GDAL errors.


rename test template files

rename to index.* so there is no mismatch
if contract is generated from template but
with different name
fixes: #85

LGTM

Thanks!


List API Names

List API routes names on the "/api" route.

but some haven't been implemented or have straight up been removed

Made a pull request updating the file given #40


Allow bumping other instances

What
Add SDK function for extend_contract_instance_and_code. I think the existing extend_ttl function should be called extend_current_ttl, and this new SDK function would be extend_ttl, but I'm not sure if it's worth updating now.

I think the existing extend_ttl function should be called extend_current_ttl, and this new SDK function would be extend_ttl, but I'm not sure if it's worth updating now.

I'm not convinced about this, because otherwise we'd be attaching the term "current" to all the functions in the storage types.

My reasoning for this was due to the fact that the host functions are called extend_current_contract_instance_and_code and update_current_contract_wasm. Maybe the names would make more sense if we removed "current" and distinguished the ones that operate on other contracts.


Indx page

How It Works image added
Related #31

https://deploy-preview-38--karmada.netlify.app/

Looks pretty good.
Can you add two more commits on it to deal with Why Karmada and Supporters?

Great! @rgrupesh . We are more close now.

@RainbowMango not critical, I'll fix it anyway when everything is in the main branch or in another

@rgrupesh Can we organize the content as per @kevin-wangzefeng 's comments?

/lgtm
/approve

@Arhell You can start to work on it now if you are still interested.


Allow site admin to disable mirrors

Wording is consistent with FORCE_PRIVATE

This will stop the creation of new mirror migrations. For existing mirrors, the site admin will need to turn off the cron for updating them (or delete them).

ping LG-TM

@Codeberg-org this can be usefull for you :)


Checks failed error

 getting a checks failed error stating one or more of my miners are showing rapid failures.Followed subsequent steps but its not solving the issue.
Mining DGB w Verthash

start mining

This might be an issue with Zergpool.  I would temporarily switch pools until the issue is resolved.

I am having the same issue mining Vertcoin getting paid in ETH using Zergpool... The issue just started today on 2 different PC's

thanks a ton for the reply - is there another pool that I'm able to mine DBG with? i've played around w it and haven't found anything similar to Zergpool yet
On Saturday, November 20, 2021, 04:59:02 AM PST, vertion @.***> wrote:
This might be an issue with Zergpool. I would temporarily switch pools until the issue is resolved.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

zpool.ca, it's in the latest release.


gradient, frontlessly

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[f,g]

/trunk merge


From c4dt

add fastsync protocol which only sends new blocks when needed

various small fixes:

    timeouts (for mixing 10'000 ballots)

    clean up socket file so CLI can be started twice in a row

fix comparisons/updates of block indices and transaction nonces

see pull request #285

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

359 of 448 (80.13%)  changed or added relevant lines in 16 files are covered.
134 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-1.4%) to 97.071%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

dkg/pedersen/dkg.go
1
2
50.0%

core/ordering/cosipbft/blockstore/disk.go
1
3
33.33%

core/txn/signed/signed.go
3
7
42.86%

cli/node/daemon.go
2
7
28.57%

core/ordering/cosipbft/fastsync/json/json.go
53
59
89.83%

mino/option.go
9
18
50.0%

core/ordering/cosipbft/cosipbft.go
19
32
59.38%

core/ordering/cosipbft/proc.go
45
62
72.58%

core/ordering/cosipbft/fastsync/default.go
156
188
82.98%

Files with Coverage Reduction
New Missed Lines
%

core/ordering/cosipbft/proof.go
5
84.38%

core/ordering/cosipbft/proc.go
28
76.38%

core/ordering/cosipbft/cosipbft.go
101
77.94%

Totals

Change from base Build<PHONE_NUMBER>:
-1.4%

Covered Lines:
14883

Relevant Lines:
15332

💛  - Coveralls


quote all fields to avoid some compatibility issues

Field with double quotes are not quoted properly causing power bi to not load the csv correctly. This workaround assures that all fields are loaded correctly. Types are of no concern as the model.json already defines this.

 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.:x: markbaas sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[CP] Fix for Random crashes on Hot Reload (EXC_BAD_ACCESS)

Commit(s) to merge
7d48bd0e2fdc19615248bce572042374d6f2999b e50470568bbb14bdb2247d4a0dd053702f27513a  5cf55de40926dafa41076e9a49e7caa2d8b40696  79f1e70a32c655e3ca7e39d5c6eca3e0f5d70337
Target
beta
Prepared changelist for beta/stable
https://dart-review.googlesource.com/c/sdk/+/319280
Issue Description
Developers are seeing random crashes while hot reloading, the crashes happen on all platforms.
Please see https://github.com/flutter/flutter/issues/129177
What is the fix
Handling of enums during hot reload was redone.
Why cherry-pick
Developers are encountering these random crashes during their development cycles causing productivity loss.
Risk
high
Issue link(s)
https://github.com/flutter/flutter/issues/129177
Extra Info
The cherry pick fuses four related changes from main.

//cc @rmacnak-google

Considering https://github.com/flutter/flutter/issues/129177#issuecomment-1670792357 maybe it is not worth the extra risk of cherry picking this so late in the stable release cycle.

Let us keep this on hold for one more week, I will ping on the issue as to whether folks where able to download Dart 3.2 beta version and are ok using it.

Thanks @a-siva!

@a-siva looks like https://github.com/flutter/flutter/issues/129177 is closed and locked.  Do we want to close this?

We decided to not cherry pick this into the Dart 3.1 stable so closing issue.


CSS Sourcemaps activation in dev mode (1.x)

Problem
It would be useful to be able to activate CSS/SCSS sourcemaps in dev mode.
If I go and edit directly webpack.dev.conf.js inside the node_modules the sourcemaps are working fine, but this is only a temporary solution.
If I understand correctly in #394 there is mention that by adding a config object inside slate.config.js it should override the config inside node_modules, but it doesn't seem to work :
Code inside slate.config.js
/* eslint-disable no-undef */

const path = require('path');

const alias = {
  jquery: path.resolve('./node_modules/jquery'),
  'lodash-es': path.resolve('./node_modules/lodash-es'),
};

module.exports = {
  extends: {
    dev: {
        resolve: {alias},
        module: {
            rules: [
              {
                test: /\.s[ac]ss$/,
                exclude: commonExcludes(),
                use: [
                  {
                    loader: 'style-loader',
                    options: {
                      hmr: true,
                    },
                  },
                  {
                    loader: 'css-loader',
                    // Enabling sourcemaps in styles causes style-loader to inject
                    // styles using a <link> tag instead of <style> tag. This causes
                    // a FOUC content, which can cause issues with JS that is reading
                    // the DOM for styles (width, height, visibility) on page load.
                    options: {importLoaders: 2, sourceMap: true},
                  },
                  {
                    loader: 'postcss-loader',
                    options: {
                      ident: 'postcss',
                      sourceMap: true,
                      plugins: () => [autoprefixer],
                    },
                  },
                  {loader: 'sass-loader', options: {sourceMap: true}},
                ],
              },
            ],
        },
    },
    prod: {resolve: {alias}},
  },
};

Could this be ultimately activated using a flag ?

My original plan was to have it activated via a slate.config.js parameter. But a flag might also be worthwhile.

Part of the problem here is that you need to nest under slateTools inside your module.exports, the starter theme had it wrong until a few weeks ago
/* eslint-disable no-undef */

const path = require('path');

const alias = {
  jquery: path.resolve('./node_modules/jquery'),
  'lodash-es': path.resolve('./node_modules/lodash-es'),
};

module.exports = {
  slateCssVarLoader: {
    cssVarLoaderLiquidPath: ['src/snippets/css-variables.liquid'],
  },
  slateTools: {
    extends: {
      dev: {
        resolve: {alias},
        output: {
          library: 'Wardrobe',
          jsonpFunction: 'webpackJsonpWardrobe'
        }
      },
      prod: {
        resolve: {alias},
        output: {library: 'Wardrobe', jsonpFunction: 'webpackJsonpWardrobe'}
      },
    },
  },
};

Just to add more detail to this ticket, I'm able to get detailed sourcemaps working by directly editing the dev.js in slate-tools node module with this:
    devtool: 'cheap-module-eval-source-map',

    output: {
      devtoolModuleFilenameTemplate(info) {
        const newPath =  'file://' + path.resolve(info.absoluteResourcePath).replace(/\\/g, '/')
        return newPath
      },
    },

    module: {
      rules: [
        {
          test: /^(?:(?!(css|scss|sass)).)*\.(liquid)$/,
          exclude: commonExcludes(),
          use: [
            {loader: 'extract-loader'},
            {
              loader: '@shopify/slate-liquid-asset-loader',
              options: {devServer: true},
            },
          ],
        },
        {
          test: /\.s[ac]ss$/,
          exclude: commonExcludes(),
          use: [
            {
              loader: 'style-loader',
              options: {
                hmr: true
              },
            },
            {
              loader: 'css-loader',
              // Enabling sourcemaps in styles causes style-loader to inject
              // styles using a <link> tag instead of <style> tag. This causes
              // a FOUC content, which can cause issues with JS that is reading
              // the DOM for styles (width, height, visibility) on page load.
              options: {importLoaders: 2, sourceMap: true},
            },
            {
              loader: 'postcss-loader',
              options: {
                ident: 'postcss',
                sourceMap: true,
                plugins: () => [autoprefixer],
              },
            },
            {loader: 'sass-loader', options: {sourceMap: true}},
          ],
        },
      ],
    },

And then also modifying css-loader according to this ticket https://github.com/webpack-contrib/css-loader/issues/717
A couple of things:

This breaks the hot module reloading because style-loader then inserts link tags instead of style tags, is there a way around this? Inline maps, not sure on the right config?

Shouldn't slate-tools have at least SOME css sourcemaps enabled by default? It's very hard to work with at the moment, especially trying to convert an old codebase, where I can't see any source/file information in development mode. Is this just because of the FOUC issue? To me I would rather have sourcemaps and an occasional flash than not, or is there something else preventing this?

Also for reference https://github.com/webpack/webpack/issues/6400


Add partial support for ES6-style promises with #catch method

This would fix #15, and I would really appreciate the merge :D
Let me know if you'd like more tests, I was sort of skimpy on them because this simply wraps #then.

Heh, derp. I suppose I should have looked at the existing PR first. Oh well.


Could you please confirm the tensorflow version if it is tensorflow-gpu-1.4.0?

Hi, I am sorry that I may not check the tensorflow version since I have graduated and the computer has been assigned to others.

It is okay, i found it is tensorflow-gpu-1.4.0


blackscreens and then crashes as soon as an X program opens

as the title describes, log of output from startx.
http://ix.io/1OhD
This issue is consistent trying to clone and build, using the latest tar under releases, and with the AUR package.
Could it be an issue with having both 32 and 64 bit libs?
lib32-libxft 2.3.2-2
libxft 2.3.3-1
lib32-libx11 1.6.7-1
libx11 1.6.8-1

I think this is is the same problem we are having here it seems is spreading...

I can change the X root just fine, worth noting I guess.

@ZoeFiri hm I'm very confused by this problem. I tried installing both 32/64 bit X libs and didn't have any trouble on my end. I'm leaning towards this being not directly associated with berry as the log file generates errors from xcb, which is not the X library that berry uses. Have you tried updating your system recently?

@ZoeFiri @jolupa this issue should be fixed as of version 0.1.2. Feel free to remake the project and let me know if any more issues arise.

Closing due to inactivity and likely resolution. Will reopen should this come up again.


:bug: Adding settings to the init script for jdtls

Setting max RAM to 70% and keeping the min to 1 GB that means that the minimum that you can run the pod with is 1.5 GB, but I still think we should use 2 GB memory and document that this is the minimum requirement.
Creating a documentation task to track this, and follow up PRs' to change the numbers once this merges.
For now you should see about 3GB of max space for the process to use until the limits are turned down.

Looks good


The entire code base should use nint/nuint instead of IntPtr/UIntPtr

Currently, even if using type maps, CppSharp ends up resolving the formers to the latters.

In C#11 and later, this makes no difference. nint is an alias for IntPtr in the exact same way that int is an alias for Int32.

Thank you, I will just live with that fact and move on; porting to it was a pain anyway, I tried and failed.😅


Add support for 7.5

Hi,
So a new Kibana version released so I wonder if you can add a support for it.
Thanks!!

Hi, I plan to add 7.5 compatibility

Thanks!

when

I can’t give you a date.
But I’ll notify here when it’ll be available,

+1

I am also waiting for this release , please let know if you need any help

Hi,
If you're ready to, I'm open to a pull request!

i am also waiting for release! thanks

I currently try to add 7.5 compatibility.
Unfortunately, as usual, there are several breaking changes in Kibana 7.5, not easy to fix. I try to get help from Kibana core team.
If someone wants to help, don’t hesitate to contact me ;)

I currently try to add 7.5 compatibility.
Unfortunately, as usual, there are several breaking changes in Kibana 7.5, not easy to fix. I try to get help from Kibana core team.
If someone wants to help, don’t hesitate to contact me ;)

I can do something if you still need help, how to contact you?

Hi @MrGaoandLin,
I solved some breaking changes, but there's still stuff to do to achieve 7.5 compatibility.
So help is welcome :)
You can join me by email.
You can find my email on my GitHub home page:
https://github.com/fbaligand/

+1, Waiting for this release, Thanks :)

Hi guys,
Good news: enhanced-table v1.7.0 is out with Kibana 7.5 compatibility!
https://github.com/fbaligand/kibana-enhanced-table/releases/tag/v1.7.0

Great, thank you very much.
Mark
------------------ 原始邮件 ------------------
发件人: "Fabien<EMAIL_ADDRESS>发送时间: 2020年1月8日(星期三) 上午6:13
收件人<EMAIL_ADDRESS>抄送: "七分醉意"<178000406<EMAIL_ADDRESS>主题: Re: [fbaligand/kibana-enhanced-table] Add support for 7.5 (#74)
Hi guys,
Good news: enhanced-table v1.7.0 is out with Kibana 7.5 compatibility!
https://github.com/fbaligand/kibana-enhanced-table/releases/tag/v1.7.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Happy that you appreciate:)


Buying Enchantment Books take Money/XP but doesn't give you a book.

Title says it all, it will take your money/xp and won't give you a book, i swear it was working before, not sure what i did, here is my configs and a console error. Using Version v<IP_ADDRESS>, Thanks for helping!
P.S, Apparently this won't take my ZIP folders, ill have to copy and paste my config files.
config.yml
http://pastebin.com/H4d50Qxd
CustomEnchantments.yml
http://pastebin.com/iXqPWE56
Console Error
http://pastebin.com/EECrcssN
Enchantments.yml
http://pastebin.com/eaHTrkLb
config.yml (Try #2 as requested by kicjow)
http://pastebin.com/1Xr8zPVr

P.S, Dust, Scrolls, Lost Books, Completely work.

Hello, can you please delete the paste you did and then post a pastebin link to the config.yml and the enchantments.yml

Sure thing! Give me a few minutes.

Done! Look at the top to see the new changes. If you need anything please tell me. :)

Can you please re-pastbin the config.yml because you need to have the spaces. I cant read it right with out them. Just recopy and paste from the config

There, I tried, I wasn't sure what you ment by spaces, so I did what you told and re-copied the config directly from my config.yml.

Does your config have these spaces on the left.
https://github.com/kicjow/Crazy-Enchantments/blob/master/config.yml

Yeah.

Strange, if you look at the pastebin you posted it doesn't. Try http://hastebin.com/

This one? http://pastebin.com/1Xr8zPVr
Looks like it does.

Make sure you arn't looking at config.yml and look at config.yml (Try #2 as requested by kicjow)
That is were i posted the fixed one.

I see that now thanks

Alright so I think its because of line 319 because you set it to 0. Why did you do that?

Hm, I did that because I didn't want Destroy chances on my books.

If so then just go up to line 11 and remove the line. Then books will not have it.

Got it, and hurrah it works! Changing it from 0 to 1 fixed it, sorry i had to cause all this trouble, thank you so much!

Np


Captured image resolution is limited to 1080x1920

I am in camera mode and after capturing the image, I see that the image resolution is downscaled to 1080x1920 even though I have 12mp camera. Is there a default setting that we need to override to update the camera capture quality in SwiftyCam?

No, SwiftyCam uses the video feed so both video and images can be captured. The photo that is captured is limited to the resolution of the video feed


Top-level await is not available in the configured target environment ("es2020")

Describe the bug
When trying to build for netlify, I get the following error:
8:43:48 PM: .svelte-kit/output/server/chunks/db.js:40:11: ERROR: Top-level await is not available in the configured target environment ("es2020")
I've set my build target to "esnext" in the vite.config.js, as instructed by sveltekit:
import { sveltekit } from '@sveltejs/kit/vite';

/** @type {import('vite').UserConfig} */
const config = {
  build: {
    target: 'esnext'
  },
  plugins: [sveltekit()]
};

export default config;

It would seem as though my target build env is being ignored.
Reproduction
Not sure how to do this, sorry - it's a private repository. It's a basic svelte app, however. On Node 18.7.0
Logs
8:43:48 PM:
8:43:48 PM: > Using @sveltejs/adapter-netlify
8:43:48 PM: ✘ [ERROR] Top-level await is not available in the configured target environment ("es2020")
8:43:48 PM:     .svelte-kit/output/server/chunks/db.js:40:11:
8:43:48 PM:       40 │ const db = await createRxDatabase({
8:43:48 PM:          ╵            ~~~~~
8:43:48 PM: ✘ [ERROR] Top-level await is not available in the configured target environment ("es2020")
8:43:48 PM:     .svelte-kit/output/server/chunks/db.js:47:0:
8:43:48 PM:       47 │ await db.addCollections({
8:43:48 PM:          ╵ ~~~~~
8:43:48 PM: error during build:
8:43:48 PM: Error: Build failed with 2 errors:
8:43:48 PM: .svelte-kit/output/server/chunks/db.js:40:11: ERROR: Top-level await is not available in the configured target environment ("es2020")
8:43:48 PM: .svelte-kit/output/server/chunks/db.js:47:0: ERROR: Top-level await is not available in the configured target environment ("es2020")
8:43:48 PM:     at failureErrorWithLog (/opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:1566:15)
8:43:48 PM:     at /opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:1024:28
8:43:48 PM:     at /opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:969:67
8:43:48 PM:     at buildResponseToResult (/opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:1022:7)
8:43:48 PM:     at /opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:1134:14
8:43:48 PM:     at responseCallbacks.<computed> (/opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:671:9)
8:43:48 PM:     at handleIncomingPacket (/opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:726:9)
8:43:48 PM:     at Socket.readFromStdout (/opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:647:7)
8:43:48 PM:     at Socket.emit (node:events:513:28)
8:43:48 PM:     at addChunk (node:internal/streams/readable:324:12)
8:43:48 PM:
8:43:48 PM: ────────────────────────────────────────────────────────────────
8:43:48 PM:   "build.command" failed
8:43:48 PM: ────────────────────────────────────────────────────────────────

System Info
My OS has no impact here, how would I get this info from netlify?

Severity
blocking an upgrade
Additional Information
Unable to deploy the site currently.

Top-level await is not implemented in most edge environments yet AFAIK, so there's nothing we can do about that. #6360 for example was necessary to work around waiting for init. The workaround is to either set the build target low enough that top-level-await is transpiled (not sure if possible honestly), or not use it.

Thanks, @dummdidumm. But I'm not using it - sveltekit's adapter is.
I tried using an earlier version, and ran into separate issues, where I was advised to update.

Hmmm, interestingly. Figured out how to set my node version to 18.7.0 on netlify, which got me passed that, but now seeing:
4:35:04 PM: error during build:
4:35:04 PM: TypeError: builder.getAppPath is not a function
4:35:04 PM:     at adapt (file:///opt/build/repo/node_modules/@sveltejs/adapter-netlify/index.js:67:21)
4:35:04 PM:     at adapt (file:///opt/build/repo/node_modules/@sveltejs/kit/src/core/adapt/index.js:16:8)
4:35:04 PM:     at Object.closeBundle (file:///opt/build/repo/node_modules/@sveltejs/kit/src/vite/index.js:460:11)
4:35:04 PM:     at async Promise.all (index 0)
4:35:04 PM:     at async Object.close (file:///opt/build/repo/node_modules/rollup/dist/es/shared/rollup.js:23662:13)
4:35:04 PM:     at async Promise.all (index 0)
4:35:04 PM:     at async build (file:///opt/build/repo/node_modules/vite/dist/node/chunks/dep-0fc8e132.js:43473:13)
4:35:04 PM:     at async CAC. (file:///opt/build/repo/node_modules/vite/dist/node/cli.js:747:9)
This is the exact same error I saw before I did any updates. So now I'm at a bit of a loss.

I've done that already - sveltekit is running latest: 1.0.0-next.516

Updated packages just to be sure, same problem - back at top level await issue.
.svelte-kit/output/server/chunks/db.js:37:11: ERROR: Top-level await is not available in the configured target environment ("es2020")
Really not sure what I'm doing wrong here.

4:35:04 PM: TypeError: builder.getAppPath is not a function is related to version mismatch of the adapter and the kit version -> bump both to latest, this should go away
.svelte-kit/output/server/chunks/db.js:37:11: ERROR: Top-level await is not available in the configured target environment ("es2020") sounds like something inside user code. There's no db.js file inside SvelteKit's code

@dummdidumm Yeah I get that second bit - that's a good point.
But it -should- be supported in latest ES, no?

What's the config of your adapter, i.e. how does your svelte.config.js look like? If there's edge: true in it, that's the reason: most edge environments (Netlify etc) do NOT support top level await yet.

What's the config of your adapter, i.e. how does your svelte.config.js look like? If there's edge: true in it, that's the reason: most edge environments (Netlify etc) do NOT support top level await yet.

Mate, you hit the nail on the head - the issue was the edge: true configuration. There's no way I would have worked that out lol
Ty so much for your time and help today - you are a gentleman and a scholar.

@dummdidumm I am also facing this issue even tho I don't have any edge: true.
My svelte config file is:
const config = {
	preprocess: [vitePreprocess({})],

	kit: {
		adapter: adapter({
			pages: 'build',
			assets: 'build',
			fallback: undefined,
			precompress: false,
			strict: true,
		}),
	},
};

Any idea on how to remove this error regarding the top-level await? TY!

Into that, adapter-vercel still has the problem of not being able to use top-level await
https://github.com/sveltejs/kit/pull/6360


internal error, please report: running "SNAP" failed: cannot find installed snap "SNAP" at revision "xxxx": missing file /snap/SNAP/xxxx/meta/snap.yaml

Version
Microsoft Windows [Version 10.0.22621.755]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-microsoft-standard-WSL2
Distro Version
Ubuntu-22.04
Other Software
No response
Repro Steps

Enable systemd support with sudo nano /etc/wsl.conf and add [boot] systemd=true.
restart wsl
check snap list its working
sudo snap refresh is working and updates installed snaps
install any snap like sudo snap install firefox
open firefox
error shows.

Expected Behavior
That the snap app opens or works as intended
Actual Behavior
running any installed snap shows "internal error, please report: running "SNAP" failed: cannot find installed snap "SNAP" at revision "xxxx": missing file /snap/SNAP/xxxx/meta/snap.yaml "
Some screenshots for reference.

As you can see, the /snap/openjdk folder is there so the snap is mounted.

But, when try to navigate to the snap meta folder in the WSL2 Ubuntu the command ls -l didn't show any file or folder, but if I open with explorer.exe . I can see all the folders there an the meta folder with the snap.yaml file. This happens with any snap.
I uninstalled and installed multiple times all WSL2 and Ubuntu infrastructure but didn't work.
Thanks for the help.
Duplicate in Ubuntu WSL github #318 since I don't know where to report this.
Diagnostic Logs
No response

Just for completeness. I finally figured out what's was my problem. Running the Windows Terminal on Admin level makes this issue happen.
Fix it by running the terminal in a regular way non-admin.


[10] Mark AWS, ECR as deprecated

https://github.com/Shippable/pm/issues/8745

This will be done as part of https://github.com/Shippable/heap/issues/1423.


Testing: fix block proposer and allow Default gas to be modified

Description
Block proposer is never defined in the testing suite. This allows the user to define it once, and it will be carried over through every block.
Set DefaultGenTxGas as a  var in the testing suite to allow modification in chains that need more gas.
closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Thanks @ramacarlucho! Do you need this included in a release or are you okay working off main? Do you think you could add a changelog entry?

Ideally on the next v5 release


Update package.json version

Can you please Update package.json version when changing things in the project ?
The release that you guys did 3 days ago broken my project.
Can you please change the package.json version to 1.4.2 or how do you want but change it to a new value :)).
And set the 1.4.1 to how it was before.

Also I get this anoying error when I try "npm i jdpdf". something with node-gyp rebuild and an error Failed at the<EMAIL_ADDRESS>install script

gyp ERR! build error
gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
gyp ERR! System Windows_NT 10.0.17134
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd ......\node_modules\canvas
gyp ERR! node -v v10.13.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\Dan Fleser\AppData\Roaming\npm-cache_logs\2018-11-05T14_47_04_071Z-debug.log

We didnt do a release 3 days ago. This seems to be related to #2051

I hotfixed it #2054
Does this help?

canvg 1.5.4 got unpublished
It should work now

thanks


HADOOP-17559. S3guard import OOM.

2734

 Quality gate: Passed
2 Issues

 2 Code issues

Details

 Quality gate: Passed
2 Issues

 2 Code issues

Details


Github links broken

All the Github links are broken. This is for all the sample programs for all of Azure Bot Service here on the documents. Please update them. I would love these samples.

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

ID: 46424ef9-9af9-55a1-207a-4202ef8f1af3
Version Independent ID: cad8ef24-51c5-e32b-6af8-cb3a3fe7b551
Content: Basic features of FormFlow - Bot Service
Content Source: articles/dotnet/bot-builder-dotnet-formflow.md
Product: bot-framework
GitHub Login: @RobStand
Microsoft Alias: kamrani

@afoste12 - the correct links are:
https://github.com/Microsoft/BotBuilder-Samples/tree/v3-sdk-samples/CSharp/core-MultiDialogs
https://github.com/Microsoft/BotBuilder-Samples/tree/v3-sdk-samples/CSharp/demo-ContosoFlowers

@Kaiqb Great! Thank you!


Ability to re-run a "upgrade

What would you like to be added:
Why is this needed:

Github user error!


Add cleanup function.

Vibe-core now includes a mechanism to clean up all unused connection pool connections so the event driver can be properly destroyed. The way mysql-native's pool wraps vibe's ConnectionPool makes it difficult to reproduce the same functionality AND provide access to the cleanup function. In addition, this makes sure it does the cleanup properly.
In my code, if I don't have this function, I get "Leaking eventcore driver" messages.
I tried to make sure this properly shows up in the docs, we'll see what happens. I also tried to ensure this function only gets defined for vibe-core that supports it (requires 0.8.6). We will see if the CI accepts that.

Vibe-core now includes a mechanism to clean up all unused connection pool connections so the event driver can be properly destroyed. The way mysql-native's pool wraps vibe's ConnectionPool makes it difficult to reproduce the same functionality AND provide access to the cleanup function. In addition, this makes sure it does the cleanup properly.

Hmm, this is new to me. Any recommendation on how mysqln's pool could be improved in this regard, or what specifically the problem is?

In my code, if I don't have this function, I get "Leaking eventcore driver" messages.

Ahh, mysqln's travis tests have been getting that, too. I wonder if there's any way this could be used to fix that? I'd guess maybe not, at least not without too much trouble, just because of the way D testrunners work (no real concept of "last line of code before exiting" or "on exit hook" that I'm aware of).

I tried to make sure this properly shows up in the docs, we'll see what happens.

It should be easy enough to build the docs yourself, just run the "./build-docs" script. If that doesn't work right out-of-the box go ahead and file an issue.
In any case, if the function only exists under certain conditions, that should probably be explained in the function's docs.

I also tried to ensure this function only gets defined for vibe-core that supports it (requires 0.8.6). We will see if the CI accepts that.

The 0.8.6 is vibe-d:core. Package vibe-core is 1.0.0 and up. I don't know if that means the function exists in all versions of vibe-core, but if so, then making it conditional may not be needed because mysqln master is now vibe-core-only (as of yesterday), no more vibe-d:core (it would be far too problematic to try to support both, and luckily vibe-d:core seems end-of-life now anyway).
Bear in mind, since I switched it to vibe-core, travis is ATM currently only testing against vibe-core 1.7.0 (the latest non-beta). I plan to add tests for earlier versions very shortly, and see how far back can realistically be supported (but without going so far back as vibe-d:core).

Hmm, this is new to me. Any recommendation on how mysqln's pool could be improved in this regard, or what specifically the problem is?

Well, the specific problem is that MySqlPool does a lot more than just wrapping a ConnectionPool, it has mechanisms to call functions every time a connection is opened, handles all the prepared statements that need to be released, etc. I'm not sure all of these could be called by user code anyway. In fact the note saying it's a "simple wrapper" and you can just use ConnectionPool directly instead might be outdated. I don't really know.

The 0.8.6 is vibe-d:core. Package vibe-core is 1.0.0 and up.

Both vibe-d:core and vibe-core (I think version 1.7.0+) have the function available I think. What I meant is that if you link this against earlier versions of the library (maybe for other reasons), this function would not be available.

Ahh, mysqln's travis tests have been getting that, too. I wonder if there's any way this could be used to fix that? I'd guess maybe not, at least not without too much trouble, just because of the way D testrunners work (no real concept of "last line of code before exiting" or "on exit hook" that I'm aware of).

This is callable at any time. All it does is close any existing connections that have not been closed, and are no longer used (i.e. they are in the pool but nobody has any references to them). So I'd say go ahead and put a scope(exit) in the tests. Where do I do that?

Well, the specific problem is that MySqlPool does a lot more than just wrapping a ConnectionPool, it has mechanisms to call functions every time a connection is opened, handles all the prepared statements that need to be released, etc. I'm not sure all of these could be called by user code anyway.

Hmm, I guess I’m just unclear/confused about what you’re talking about with this:

The way mysql-native's pool wraps vibe's ConnectionPool makes it difficult to reproduce the same functionality AND provide access to the cleanup function.

I think I’m just having a bit of a brain fart moment on this. IIUC: You’re saying there’s some new functionality in vibe’s connection pool that (due to the design of mysql-native’s connection pool) is difficult to use/expose in mysql-native’s connection pool. And therefore, the next best thing that can be done is simply to add this removeUnusedConnections() function as you’re doing in this PR. Is that correct?

In fact the note saying it's a "simple wrapper" and you can just use ConnectionPool directly instead might be outdated. I don't really know.

You may be right about that…

Both vibe-d:core and vibe-core (I think version 1.7.0+) have the function available I think. What I meant is that if you link this against earlier versions of the library (maybe for other reasons), this function would not be available.

Ah, ok, so there are older versions of vibe-core that lack it. That’s fine then. Maybe just one more adjustment to the docs then about how removeUnusedConnections only exists on newer vibe-core’s that support the removeUnused feature on connection pools. Aside from that, this looks good to me, and travis seems happy with it too, which is always good ;)

Ahh, mysqln's travis tests have been getting that, too. I wonder if there's any way this could be used to fix that?

This is callable at any time. All it does is close any unused connections that have not been closed (i.e. they are in the pool but nobody has any references to them). So I'd say go ahead and put a scope(exit) in the tests. Where do I do that?

Honestly, I wouldn’t worry too much about it. That would just mean the tests would constantly be re-creating new connections, which would just slow the tests down, and travis is already taking like 3-4 minutes on most of these jobs. If there were a trivial way to just to it once after all the tests were complete, then that’d be great, but as things stand, I don’t it’s worth it just to silence a few benign warnings at the end of the tests.

Hmm, I guess I’m just unclear/confused about what you’re talking about with this:

The way mysql-native's pool wraps vibe's ConnectionPool makes it difficult to reproduce the same functionality AND provide access to the cleanup function.

I think I’m just having a bit of a brain fart moment on this. IIUC: You’re saying there’s some new functionality in vibe’s connection pool that (due to the design of mysql-native’s connection pool) is difficult to use/expose in mysql-native’s connection pool. And therefore, the next best thing that can be done is simply to add this removeUnusedConnections() function as you’re doing in this PR. Is that correct?

Oh, yeah, definitely it's not possible to call the functionality because the ConnectionPool member is private! What I meant by the above comment is that if I wanted to simply use ConnectionPool instead of MySQLPool, just to get at the new functionality, then I lose out on all the benefits that MySQLPool has. I'm actually not sure if it's appropriate to use a ConnectionPool directly now anyway. I'm not sure how all those auto registration/etc functions work, or if they are required to make the new Prepared stuff work.

Maybe just one more adjustment to the docs then about how removeUnusedConnections only exists on newer vibe-core’s that support the removeUnused feature on connection pools.

Done

Oh, yeah, definitely it's not possible to call the functionality because the ConnectionPool member is private! What I meant by the above comment is that if I wanted to simply use ConnectionPool instead of MySQLPool, just to get at the new functionality, then I lose out on all the benefits that MySQLPool has.

Ah, ok, I see.

I'm actually not sure if it's appropriate to use a ConnectionPool directly now anyway. I'm not sure how all those auto registration/etc functions work, or if they are required to make the new Prepared stuff work.

Yea, I'd have to go digging around there again to be certain exactly what would happen, but it's definitely not a recommended approach, especially since the prepared statements are now pretty much the default and get used behind-the-scenes (rather than something you have to go out of your way to deliberately use, which is part of the whole intent).
So this all looks good now. The second commit is just comments and whitespace, so I think we can safely skip waiting for travis and trust its initial OK.


Should illegal instruction exception be raised for unsupported EEW?

For single-letter "V" extension, the EEW = 128 is not supported. So if a widening instruction (SEW=64) with output EEW = 128 comes, which of below should I do?
(1) Raise a exception of illegal instruction
OR
(2) Just execute it and write back register file with a likely incorrect value

It's an illegal instruction exception if SEW=128-bit is not supported in the machine

Thank you so much.


Add plot_interactive to MvNormal

closes #225
Description

Added plot_interactive to MvNormal.
Add tests for plot_interactive.
Add xy_lim to plot_mvnormal.

Checklist

[x] Code style is correct (follows pylint and black guidelines)
[x] Includes new or updated tests to cover the new feature
[x] New features are properly documented (with an example if appropriate)
[x] Widget states have been properly saved (only for notebooks with widgets) see for details.

Codecov Report
Attention: Patch coverage is 96.22642% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 86.43%. Comparing base (6afa0e5) to head (eea25ac).

Files
Patch %
Lines

preliz/internal/plot_helper_multivariate.py
90.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #337      +/-   ##
==========================================
+ Coverage   86.20%   86.43%   +0.23%
==========================================
  Files          36       36
  Lines        4190     4240      +50
==========================================
+ Hits         3612     3665      +53
+ Misses        578      575       -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Signed Raw Transaction

Hey
Is it possible to get some example of how to sign raw transaction with private key which is calling contract function.
What i'm trying to do is like
$contract  = new Contract($nodeAddress, $abi)->at($contractAddress);
$transactionData = $contract->getData('functionName', 'address', 'bool', [
             'from' => $fromAddress,
             'to'    => $toAddress,
             'gas' => $gas,
            'gasPrice' => $gasPrice
]);
$web3= new Web3(new HttpProvider(new HttpRequestManager($nodeAddress, $timeOut)));
$eth = $web3->getEth();
$eth->sign($privateKey, $transactionData, function($err, $result) {
});

@kristotruu you can check this https://github.com/web3p/ethereum-tx


Use latest versions of EXT-direct and classgenerator

This will add EXT 6 support. Just have a look at https://github.com/terrestris/shogun2/wiki/Basic-concepts#extdirect to understand how you can test this.

Great!


display corruption with wlroots master 20201203 on nouveau

with wlroots master 20201203 and sway (using nouveau with 2013 MBP 15") i have display corruption making sway completely unusable, requiring a tty kill. pulling wlroots tag 0.12.0 solves this problem.

The backtrace you provided doesn't contain debug symbols. This most likely happens because the Sway binary you're using doesn't have debug information bundled.
Can you try again with a manually compiled Sway binary? See https://github.com/swaywm/sway/wiki/Development-Setup#compiling-as-a-subproject

Bleh, selected the wrong comment in the auto-reply dialog. Sorry about that.
Please provide full debug logs.

BTW, anything in dmesg? I just tried multi-GPU with nouveau (old NVIDIA card) and got a kernel oops.

sway_wlroots-master-3_xwayland-disabled_and_waybar-disabled.log
sway_wlroots-master-2_xwayland-disabled.log
sway_wlroots-master-1.log
sway_wlroots-0.12.0-3.log
swaywm with debug info included. the combination of swaywm 1.5.1 and wlroots 0.12.0 works best.

I'm not entirely sure I'm in the same boat here but see very similar symptoms.

BTW, anything in dmesg?

kernel: nouveau 0000:03:00.0: DRM: Moving pinned object 00000000fc11445d!
kernel: nouveau 0000:03:00.0: DRM: bo 00000000e81b0ace pinned elsewhere: 0x00000001 vs 0x00000002
kernel: nouveau 0000:03:00.0: DRM: Moving pinned object<PHONE_NUMBER>20601e!
kernel: nouveau 0000:03:00.0: DRM: Moving pinned object 00000000e81b0ace!

526ae594 still works for me, since 754179da it does not anymore. However, this is in combination with a newer version for sway, so could be misleading. https://github.com/swaywm/wlroots/compare/526ae594...754179da
Let me know if you think this is unrelated with this issue or if I can provide more info.

I'm not entirely sure I'm in the same boat here but see very similar symptoms.

BTW, anything in dmesg?

kernel: nouveau 0000:03:00.0: DRM: Moving pinned object 00000000fc11445d!
kernel: nouveau 0000:03:00.0: DRM: bo 00000000e81b0ace pinned elsewhere: 0x00000001 vs 0x00000002
kernel: nouveau 0000:03:00.0: DRM: Moving pinned object<PHONE_NUMBER>20601e!
kernel: nouveau 0000:03:00.0: DRM: Moving pinned object 00000000e81b0ace!

526ae594 still works for me, since 754179da it does not anymore. However, this is in combination with a newer version for sway, so could be misleading. https://github.com/swaywm/wlroots/compare/526ae594...754179da
Let me know if you think this is unrelated with this issue or if I can provide more info.

OP's log contains:
00:00:00.333 [DEBUG] [backend/drm/legacy.c:95] eDP-1: failed to set hardware cursor: Device or resource busy

Can you try WLR_DRM_NO_MODIFIERS=1? Ref https://github.com/swaywm/wlroots/issues/2526

OP's log contains:
00:00:00.333 [DEBUG] [backend/drm/legacy.c:95] eDP-1: failed to set hardware cursor: Device or resource busy

Can you try WLR_DRM_NO_MODIFIERS=1? Ref https://github.com/swaywm/wlroots/issues/2526

Sorry for the long delay. Yeah, that works.


message.senderName null in response from listen

Not sure what the cleanest way to fix this is.  We're already doing more requests than I'd like in listen.  The best option may be to deprecate this property.

Reimplement this to use a caching system.
Then we could get the senderName from the stored participant data.

We considered caching back when we implemented the fix for >5 participants and ended up decided it added a lot of complexity... might be worth revisiting the decision.  My main concern with caching is that it can be tricky to do it right.. and it frequently ends up making the system less transparent/predictable regarding memory and computation costs.  Doesn't mean it's impossible, that's just why we haven't done it that way so far.

Going to track this using #219

@blazeu If this is something you feel strongly about, please leave a comment in #219 :smile:


tutorial - docker run

I added the docker run (1 mdx file with 18 png files) in Tutorials and modified the mint.json file by adding 1 line.
There are some issues with the current mint.json:
1)It shows 2 'Products' in my local.
2)There is un unrecognized key - 'arrow', making 'mintlify dev' fail to run.

Here are changes I made, please review:
1）Replace the first exec probe example with a HTTP probe example;
2)  Modify the final summary on how to handle the multiple images and Docker Compose;
3) Remove the domain for the links to the doc sites;
4) Add some words in the dict.


[PATCH] Blender collada exporter produces files unreadable by Assimp

Hi,
I'm using your collada exporter, but the files weren't readable by the popular library Assimp. I've made some changes, and thought I should send them upstream.
https://github.com/TheJosh/chaotic-rage/commit/fdc9962daee33b98f7847041f00f0c497795db15
Cheers,
Josh

cool, feel free to make a pull request
On Thu, May 28, 2015 at 2:44 AM, Josh Heidenreich<EMAIL_ADDRESS>wrote:

Hi,
I'm using your collada exporter, but the files weren't readable by the
popular library Assimp. I've made some changes, and thought I should send
them upstream.
TheJosh/chaotic-rage@fdc9962
https://github.com/TheJosh/chaotic-rage/commit/fdc9962daee33b98f7847041f00f0c497795db15
Cheers,
Josh
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/2001.

Pull request --  #2023
On 28/05/2015, Juan Linietsky<EMAIL_ADDRESS>wrote:

cool, feel free to make a pull request
On Thu, May 28, 2015 at 2:44 AM, Josh Heidenreich
<EMAIL_ADDRESS>wrote:

Hi,
I'm using your collada exporter, but the files weren't readable by the
popular library Assimp. I've made some changes, and thought I should send
them upstream.
TheJosh/chaotic-rage@fdc9962
https://github.com/TheJosh/chaotic-rage/commit/fdc9962daee33b98f7847041f00f0c497795db15
Cheers,
Josh
--
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/2001.

Reply to this email directly or view it on GitHub:
https://github.com/okamstudio/godot/issues/2001#issuecomment-106299393


Fix dfs.datanode.data.dir

dfs.datanode.data.dir should point to mountpoint /hadoop/dfs/data/{{ $index }}  instead of dataNodeHostPath
vars in datanode-data-dirs template should be taken from global values

The fix looks good to me. Thanks for writing this PR, @vvbogdanov87.
Can you take a look at why Travis CI is failing? You can restart failed builds manually in the travis UI in case the failures are flaky.


Make the NpmArtifactGenerator implement the ArtifactGenerator interface

Task Description
As part of #1145, we need to refactor the NpmArtifactGenerator to implement the ArtifactGenerator. This will require re-working some of the code in the generator, as well as some of the tests.
Task Relationships
This task:

Is a sub-task of: #1145
Relates to: #1295

Help

Our chat
Points of contact:

@carlspring
@sbespalov
@fuss86

Hi there @carlspring ,
Could I look into this issue for a couple of days?

Hi @ogryniuk ,
Please, feel free to do so!

This issue is free since now. Anyone is welcome to pick it up

I will pick up this issue

Thanks, @bamarch ! :)

not working on this - @carlspring from rocketchat it looks like Oleksandr is working on this

Can I try to solve #1294?

Before, I only got as far as speccing out the issue:
—————————————

rename NpmPackageGenerator to NpmArtifactGenerator and have it implement the ArtifactGenerator interface

update docs / tests as needed

MavenArtifactGenerator is done already https://github.com/strongbox/strongbox/pull/1161/files#diff-4b3b4bc5d7d8f083159e61a288e2d201R62
Implementing ArtifactGenerator:

add the methods from the ArtifactGenerator i.e. generateArtifact()
when calls are made to generateArtifact, they should then call NpmPackageGenerator#buildPackage

—————————————
I am working on another issue now, and it seems Oleksandr still did not claim this on GH, so I think it’s open

Where is the NpmArtifactGenerator? I looked through the code and could not find it.
P.S. I am new to the open source community.

@evilmopey ,
Please, leave this task to @bamarch.

The original name of the class is NpmPackageGenerator, but it should be renamed to NpmArtifactGenerator for consistency.


curl command wrong in ziti-cli-functions.sh

curl "${ZITI_CTRL_EDGE_ADVERTISED_ADDRESS}:${ZITI_CTRL_EDGE_ADVERTISED_PORT}" should be
curl -k "https://${ZITI_CTRL_EDGE_ADVERTISED_ADDRESS}:${ZITI_CTRL_EDGE_ADVERTISED_PORT}" because otherwise curl will make an http request to an https server and the -k is required because the cert is not trusted.

do you have a cached version? I am looking at the "latest" version (for v0.29+) https://get.openziti.io/quick/ziti-cli-functions.sh and I'm not seeing it.
Is it possible we found/fixed that at some point and you have an older version?

Ah sorry, I should reference that the curl is suggested here:
https://openziti.io/docs/learn/quickstarts/network/local-no-docker


[Bug] Script cannot find my root folder

I am encountering an issue with the sonarr-update-tba.bash script where it is unable to locate the root folder of my sonarr instance.
I am using a Synology NAS, and Sonarr is running in a Docker container. My media files are stored in '/data/media/tv'.
This is my env:

# The Sonarr instances you want to interact with.
# If you are running Sonarr via Docker, you can use 'docker:<container_name>' to let the script automatically figure out the IP address
#   e.g. if your container name is 'sonarr', then containerIp=("docker:sonarr")
#   For multiple Sonarr instances, just add additional array items, e.g. containerIp=("docker:sonarr" "docker:sonarr-4k")
# If your instance is hosted on your system, you could just provide a direct IPv4 address, assuming it is valid/static
#   e.g. if your instance is reachable via localhost, then containerIp=("<IP_ADDRESS>")
#   Currently multiple Sonarr instances outside of Docker are unsupported. If you have multiple instances running on your host, create
#   an issue and I'll try and motivate myself to add support for your situation.
## This is an array
containerIp=("<IP_ADDRESS>")

# If your Sonarr instance is not provided via Docker, you must uncomment the below variable and point to where your 'config.xml' for Sonarr is
## This is a string
sonarrConfig="/volume1/docker/appdata/sonarr/config.xml"

# Are we allowed to check for and notify of updates each time the script runs?
# Can be "Yes" "No" "True" "False"
## This is a string
updateCheck="Yes"

# How verbose should our output be?
# Possible values:
# 1 - Error only
# 2 - Informational
# 3 - Verbose
## This is a string
outputVerbosity="2"

# If you have entire libraries you want to ignore, you can run the script with verbose output, and watch for the
# line "Detected [int] libraries", then put the correspnding library ID into this array to have it ignored on future runs.
# If you have multiple Sonarr containers running in Docker, you should prefix the ID with the container
# you want it to correspond to, for example instead of:
#     ignoreLibraryArr=("123")
# you would do:
#     ignoreLibraryArr=("docker:sonarr:123")
## This is an array
ignoreLibrary=()

# If you have entire series you want to ignore, you can run the script with verbose output, and watch for the
# line "Found series ID:", then put the series ID into this array to have it ignored on future runs.
# If you have multiple Sonarr containers running in Docker, you should prefix the ID with the container
# you want it to correspond to, for example instead of:
#     ignoreSeries=("456")
# you would do:
#     ignoreSeries=("docker:sonarr:456")
## This is an array
ignoreSeries=()

# If you have files you want to ignore, you can run the script with verbose output, and watch for the
# line "Found episode ID:", then put the episode ID into this array to have it ignored on future runs.
# If you have multiple Sonarr containers running in Docker, you should prefix the ID with the container
# you want it to correspond to, for example instead of:
#     ignoreEpisodes=("789")
# you would do:
#     ignoreEpisodes=("docker:sonarr:789")
## This is an array
ignoreEpisodes=()

And these are my logs:
sonarr-update-tba.bash   ::   2024-08-15 13:44:07   ::   [info]  Processing instance: <IP_ADDRESS>
sonarr-update-tba.bash   ::   2024-08-15 13:44:07   ::   [info]  Configuration file retrieved
sonarr-update-tba.bash   ::   2024-08-15 13:44:07   ::   [info]  Port retrieved from config file
sonarr-update-tba.bash   ::   2024-08-15 13:44:07   ::   [info]  API key retrieved from config file
sonarr-update-tba.bash   ::   2024-08-15 13:44:07   ::   [info]  No URL base detected
sonarr-update-tba.bash   ::   2024-08-15 13:44:07   ::   [info]  Checking API functionality
sonarr-update-tba.bash   ::   2024-08-15 13:44:08   ::   [info]  API authorization succeeded
sonarr-update-tba.bash   ::   2024-08-15 13:44:08   ::   [info]  Detected 1 libraries
sonarr-update-tba.bash   ::   2024-08-15 13:44:08   ::   [info]  Checking for TBA/TBD items in /data/media/tv
find: `/data/media/tv': No such file or directory
sonarr-update-tba.bash   ::   2024-08-15 13:44:08   ::   [info]  Located 0 files to process

What am I doing wrong!:D would appreciate some help!

The way you've denoted the container IP address and path to the config file in your .env file leads to script to believe that this is a host-based instance of Sonarr, not a docker-based instance. As a result, it's searching for the path /data/media/tv on your host, not in your docker container.
Solution is to denote your Sonarr instance as described in lines 2/3 of the .env file. You can also comment out the sonarrConfig variable on line 14, as your config will be automatically retrieved from inside the container, since it's not a host-based instance.

If I am doing that, I get this is error:
sonarr-update-tba.bash   ::   2024-08-15 14:23:24   ::   [info]  Processing instance: docker:sonarr
jq: error: guides_default/0 is not defined at <top-level>, line 1:
.[] | .NetworkSettings.Networks.trash-guides_default.IPAddress
jq: 1 compile error
sonarr-update-tba.bash   ::   2024-08-15 14:23:25   ::   [error] Unable to determine IP address via networking mode: trash-guides_default

Since I have completely followed the documentation of the TraSH Guides, this probably leads to problems.

What's the output of:
docker inspect -f '{{range $k, $v := .NetworkSettings.Networks}}{{println $k}}{{end}}' sonarr

trash-guides_default

Thanks. What about docker inspect sonarr?

Update your copy of the script and give it another try

Now it’s working! Thanks for the help!


Should we use a python linter? Should we enable autofix?

See pr #13 for an example of how it works.

It only lints lines of code that have been changed in the PR not the entire codebase... This confused me for a while.
We need to list the lint errors we don't want to check for (i.e. max-line-length=80 is something I don't typically follow)
It can also autofix lint errors. Do we want to do that?

If we start doing this we should probably also run the entire codebase through flake8 offline and push a fixed version.

I think using some kind of a style checker would be great. It looks like stickler-ci and hound are both doing something related to that, right? Are these just enforcing the PEP8 standards, or can you specify other style rules as well?
I'm skeptical of autofix. For the simple examples in PR #13 I think autofix would be great, but there are other cases that I wouldn't trust autofix. I'd like to see how it works a little better before trying the autofix.
I would support a complete flake8 of the codebase.


retry registring

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/97949
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 90c3e011e8fe7075ed1adf41a79254e2ebc96e5c
git push origin v0.1.0


Tests failing on v0.3

Tests currently fail on v0.3 because of UInt8's in tests, such as here. Fixed by #227 .

I'm actually just dropping support for 0.3 going forward; it's more trouble than it's worth at this point.


change icons color (back and actions) in  SliverAppBar with flexibleSpace when page is scrolled

Is possible change icons color (back and actions) in  SliverAppBar with flexibleSpace when page is scrolled?
I need change color from black to white
How can i do?
Thanks

@romaluca I was wondering if you've a working example for me? I'm pretty new to flutter and tried to build it by myself but I failed.. Please let me know! :)

@ogXxX @romaluca any luck with this? Did you post on StackOverflow?

Closing as per comment above. Please ask these kind of questions on StackOverflow.