It is not possible to handle net.createConnection errors

There is no possible way to register 'error' listener before net.createConnection is called.
This means that during initial connection appropriate code will never see errors like 'ECONNREFUSED' These errors will always get propagated to global scope, that means there is only one way to write a node.js app which can be started before redis server is to register global unhandled exception handler...
Possible solution:
Pass event handlers to constructor via options hash

Any news on this? Crashing when redis is unavailable is excessive. For now I'm switching to ioredis, which doesn't have this problem.

@grimborg do you have a reproducible test? I can't reproduce such an error.

To reproduce this error -- simply try connecting to invalid redis uri.

@xytis In mocha the test works properly:
client = redis.createClient('redis://test');
client.on('error', function (err) {
    console.log(err);
    done();
});

 { [Error: Redis connection to test:6379 failed - getaddrinfo ENOTFOUND test test:6379]
  code: 'ENOTFOUND',
  errno: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'test',
  host: 'test',
  port: 6379 }

What version do you use?

Try doing ECONNREFUSED. By specifying a valid connectable Url.

And, notice that the bug was opened waaaaaaaaay back. It might be that things got fixed eventually.

@xytis ECONNREFUSED errors are catched by attached error handlers. Using a valid Uri results in reconnection attempts if the connection can't be established. If you want to prevent this, you'll have to use the connect_timeout option.
And even though this issue is very old, the way how this is handled did not really change in the meanwhile.
Could you provide me with a test case?

Ping @xytis

I no longer can reproduce this error. It might have been a change in underlying net.createConnection, and I do not recall which version of Node I used when I encountered this problem.

@xytis Thanks a lot for the info :)


XDG Base Directory

Currently everything is dumped inside inside .minecraft in the users home folder.
While this was marked as a wont fix for the official launcher, this project could support it.
I don't suggest it be the default but still be checked it exists and it takes preference. Could be $XDG_DATA_HOME/minecraft or $XDG_DATA_HOME/olauncher with the default for $XDG_DATA_HOME being $USER/.local/share/.
I'm unsure if this is even feasible due to the project purely being patches but this would to an improvement as you can currently change the game directory path.

good idea, I'll see if I can get a PR for this written at some point maybe

Was just thinking about this again. How would this be functionally different from running the launcher with --workDir "$HOME/.local/share/olauncher?

Was just thinking about this again. How would this be functionally different from running the launcher with --workDir "$HOME/.local/share/olauncher?

Ah this is close enough to what I was looking for. Thanks.


solvespace: 2.3-20170808 -> 2.3-20180906

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Success on x86_64-linux (full log)
Attempted: solvespace
Partial log (click to expand)
Wrapping program /nix/store/ygg7z5fgj7kqvz75d6qibnrd3cwfpm00-solvespace-2.3-20180906/bin/solvespace
Wrapping program /nix/store/ygg7z5fgj7kqvz75d6qibnrd3cwfpm00-solvespace-2.3-20180906/bin/solvespace-cli
shrinking RPATHs of ELF executables and libraries in /nix/store/ygg7z5fgj7kqvz75d6qibnrd3cwfpm00-solvespace-2.3-20180906
shrinking /nix/store/ygg7z5fgj7kqvz75d6qibnrd3cwfpm00-solvespace-2.3-20180906/lib/libslvs.so.3.0
shrinking /nix/store/ygg7z5fgj7kqvz75d6qibnrd3cwfpm00-solvespace-2.3-20180906/bin/.solvespace-cli-wrapped
shrinking /nix/store/ygg7z5fgj7kqvz75d6qibnrd3cwfpm00-solvespace-2.3-20180906/bin/.solvespace-wrapped
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ygg7z5fgj7kqvz75d6qibnrd3cwfpm00-solvespace-2.3-20180906/lib  /nix/store/ygg7z5fgj7kqvz75d6qibnrd3cwfpm00-solvespace-2.3-20180906/bin
patching script interpreter paths in /nix/store/ygg7z5fgj7kqvz75d6qibnrd3cwfpm00-solvespace-2.3-20180906
checking for references to /build in /nix/store/ygg7z5fgj7kqvz75d6qibnrd3cwfpm00-solvespace-2.3-20180906...


[Feature Request] Timeout for payinvoice (/v1/channels/transactions)

We are using 'payinvoice' (or rather /v1/channels/transactions with a payment_request parameter).
It would be nice to have a 'timeout' parameter also, a specific time limit after which LND should give up trying to pay the invoice.
I'm guessing there is already one behind the scenes (1 minute, correct?), hopefully it's just a matter of making it available to be set through a parameter.
I understand that a workaround is possible through 'sendroute' but it involved multiple calls and plenty of extras. We've already implemented the invoice payments using /v1/channels/transactions and only need a timeout.
Thanks for your kind consideration.

I'd like to see this too.
@BitBargain what is the current workaround?

Daniel: Based on the responses, the situation is that even if you cancelled the payment there would still be a chance for it to be sent, since you just push it to nodes and the rest is up to them (at least until the expiry). The only real workaround (at least in my case) would be to make lightning non-instant and let users submit a withdrawal request and returning a result to them later, once the payment is successful or the timeout.

@BitBargain you mentioned a workaround using sendtoroute but I don't see how that's possible?  Any links?

This can be done using the routerrpc.SendPayment API.

@PWKad https://github.com/lightningnetwork/lnd/blob/5485101f9f7640c1b4d6b10ac531a209e2e32715/lnrpc/routerrpc/router.proto#L40


Fix crash when loading save game with invalid file name

Suggested in this issue.
The game crashes when calling the loadGame method with an invalid file name. @3prockent suggests to add a method to verify if the snapshot exists or not, or fix the crash.
Will fix the crash and also add a the createIfNotFound parameter described in Google's API, which is hardcoded to false right now.

Done in these commits.


Falcon support?

I've been tracking the Falcon https://github.com/ggerganov/ggml/pull/231 PR, and as I understand currently it won't work on a released version of ggml.
Any suggestions on how to test it config wise are appreciated, I'm assuming llama might not work based on other PRs.

I'm also waiting for that PR to be merged. Hopefully it will be merged this weekend https://github.com/ggerganov/ggml/pull/231#issuecomment-1594411046

Thanks, do you know if it is possible to point ctransformers to a branch of ggml for testing?

+1 to this
However I don't think the ggml PR is the one to implement. Instead I would use the new implementation in ggllm.cpp: https://github.com/cmp-nct/ggllm.cpp
This is now the best Falcon GGML implementation, including CUDA GPU acceleration with support for both 7B and 40B models.
I don't know if this will end up also being in the GGML repo, or maybe even eventually the llama.cpp repo (as ggllm.cpp is a fork of llama.cpp).
But either way, this is the Falcon implementation of interest right now.
And I wonder whether there's even a need to wait for it to be fully stable? It's already useful and being used by people. I have four Falcon GGML repos now:

https://huggingface.co/TheBloke/WizardLM-Uncensored-Falcon-40B-GGML
https://huggingface.co/TheBloke/WizardLM-Uncensored-Falcon-7B-GGML
https://huggingface.co/TheBloke/falcon-40b-instruct-GGML
https://huggingface.co/TheBloke/falcon-7b-instruct-GGML

If ctransformers supported this I think it would help accelerate the use of Falcon GGML.

@matthoffner It is not possible to point ctransformers to a branch of ggml as the model code has to be modified to integrate into the common interface I provide for all models.

Thanks @TheBloke I was waiting for the PR to be merged but since you are already providing the files, I added experimental support for Falcon models using the ggllm fork in the latest version 0.2.10
It has CUDA support similar to the LLaMA models. I tested with 7B model but my machine doesn't have enough memory for the 40B model.

Fantastic! That's great news, thank you marella.  That was super quick.
I will update my READMEs to mention this.
@ParisNeo could you check if this works automatically in LoLLMS, and if so maybe add some Falcon GGML entries? Then I will mention also in the README, and you will be the first UI to support Falcon GGML! :)

https://discord.com/channels/@me/1097295255801442306/1121584559138545704
I am using 0.2.10.
Am I missing something?

You should use model_type="falcon":
llm = AutoModelForCausalLM.from_pretrained("TheBloke/falcon-7b-instruct-GGML", model_type="falcon")

@marella @TheBloke Thank you!! I think I've got the 40B with GPU on a HF space:
https://huggingface.co/spaces/matthoffner/falcon-fastapi

I've added config.json to my four repos so manual model_type selection by the client shouldn't be needed from now on

Thank you very much for this nice work. Tested the 7B model on my pc and it is really solid even compared to 13B from other models.
@marella do you have a twitter account so i can follow you and put a link when i credit your work ?

Yeah i was wondering about that too

Hey, I don't have a twitter account. I'm on LinkedIn https://www.linkedin.com/in/ravindramarella/ but I don't post anything there.
If you want to link, you can just link to this repo.

Ok. Very nice profile by the way. Nice to meet you.


can't use debug=True and host='<IP_ADDRESS>' if flask app integrated with PyWebIO

BUG Description
1, parameter  host='<IP_ADDRESS>' can not be used but "localhost" works if original Flask application integrated with PyWebIO.
2, papameter debug=True can not be used too,
in my application, below parameter works:
app.run(host='localhost', port=5000, ssl_context=("localhost_cert.pem", "localhost_key.pem"))
details see the pictures i marked
Environment Information

OS and Version:   Windows10 +latest Pycharm  PyCharm 2021.3 (Community Edition)
Browser and Version:  Chrome96
Python Version: python3.1
PyWebIO Version: 1.5

Does the Flask server work good when you remove the app.add_url_rule() line ?

Does the Flask server work good when you remove the app.add_url_rule() line ?

I tried delete the app.add_url_rule() line,
and if host='<IP_ADDRESS>',
then the server can start but can not be visit

It seems that there are some problems with the ssl_context config. Please make sure your Flask app can work well first, and then add PyWebIO app to it via app.add_url_rule()

so i tried to remove the ssl_context parameter, and add debug=True, it become this:
app.run(debug=True,host='localhost', port=5000)
it still not work,the server can not be started:

Serving Flask app '' (lazy loading)
Environment: production
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
Debug mode: on
Restarting with stat

stopped here.


SECURITY_ERR in PhantomJS

I'm getting js error SECURITY_ERR: DOM Exception 18 on in place:
  var isEventSourceSupported = function () {
    if (global.EventSource !== undefined) {
      try {
        var es = new global.EventSource("data:text/event-stream;charset=utf-8,");
        es.close();
        return es.withCredentials === false &&
               es.url !== ""; // to filter out Opera 12 implementation
      } catch (error) {
        throwError(error);
      }
    }
    return false;
  };

By line es.close(); https://github.com/Yaffle/EventSource/blob/62be4ad02a5b78db85fc0ee5d8fd5fc32b1456dd/eventsource.js#L490
PhantomJS 1.9.8

possibly, the condition in the if should be modified to do not pass PhantomJS...

Instead of a throwError(error) it should just return false there so the polyfill will kickin when the native version throws errors.

this was done to not hide the error:
throwError uses setTimeout to rethrow the error asynchronously, so return false will be executed.
anyway, https://github.com/Yaffle/EventSource/pull/56 removed throwError


fix: pass the results of userChoice to the developers

There are times when we need to handle different logic based on the result of userChoice.
$pwa?.install().then((userChoice) => {
	if (userChoice.outcome === 'accepted') {
		console.log('accepted install');
	}
})

Note: if the user installs the app, some platforms will close the app in the browser and will open the installed PWA (for example Chrome and Edge in Windows Desktop)


Send confirm signup and change email address emails when user is created or updated through the bankend

Feature request
Describe the solution you'd like
Add ability to send user confirm signup and change email address emails when user is created with supabase.auth.api.createUser and user data is updated with supabase.auth.api.updateUserById

Hey this is somewhat out of scope, as the admin API is intended to be as flexible as possible. Different projects will have different requirements. Some may want to send an email, others not. Thus, it is unlikely we'll add support for this in GoTrue.
Since the admin APIs are intended to be used in a server environment which you fully trust, it is trivial to add email sending functionality when you need it.


Add Update Endpoints and Fix other endpoints for new schema

#175, #140, #36 (i think)

@JonMike8 Do you want to do the merge? Or do you want me to do it?

@miguel-merlin i can do it, doesn't look like many conflicts


Update quickStart.adoc

Updated the quick start paragraph with a warning.
closes micronaut-projects/micronaut-mqtt#70

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

Thanks!


Spike: Ensure PDFs generate properly and PDF splitting occurs

Summary
When a PDF is trying to get created, we see the following error:
convert-im6.q16: attempt to perform an operation not allowed by the security policy 'PDF' @ error/constitute.c/IsCoderAuthorized/421.

This prevents PDFs from being created properly.
Acceptance Criteria

[x] PDFs can be downloaded and opened from the download drop down in the items partial
[x] PDF splitting occurs as intended by IIIF Print

Screenshots or Video
Testing Instructions

[ ] Upload a PDF as an Image
[ ] Ensure the PDF splitting happens
[ ] Download the PDF derivative and open it, file should open

Notes
The im6 hints at perhaps an ImageMagick versioning issue.  IIIF Print was developed with Hyku on ImageMagick v7.1.0-57 which solved a specific tiff offset bug
ref: https://github.com/samvera/hyku/commit/85f4d605e8af4a26a24dd0a1292058dcedfbec86

Should be solved by #150

blocked until client gives us a staging to deploy to

To test, you will need an IU account that has been registered with a VPN. Your account will need admin access as well cc the essi client channel or ping Kirk/Shana.
After logging into VPN, you'll be able to access the following site.
Test site:  https://dcadmin-test.dlib.indiana.edu/

tested on https://dcadmin-test.dlib.indiana.edu/ (staging) and got this error:

retest without selecting a rights statement:

Actually, the client has confirmed that they don't want PDF splitting to happen. I will close this and the spin off ticket we created.


Improve initial example in readme

Based on suggestion in slack.

Coverage remained the same at 100.0% when pulling c992548a9ff274206adcf41cbfd95bef6037f20e on floatdrop:improve-readme-001 into ca4f815ab35120d97841d8cf3c354d1af6adafc7 on zeit:master.

Thanks ❤


fix: add --unsafe-perm to action since it runs as root

:tada: This PR is included in version 1.3.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Different ways of pushing an image

keep the build part

the push of the image is out of scope of this one as this it focusing on getting a secure image

multiple options for pushing an image:

GitHub
ECR
Dockerhub

Will not be implemented as this decision has been made that this action will only push to a GitHub packages registry.


🔥✨ Adapt image property changes

refs https://github.com/TryGhost/Ghost/issues/8348
This is WIP, please no review!

[x] test signup
[x] test all image cases again

Coverage increased (+0.02%) to 73.336% when pulling 10cff49944ceed660763acafeb11af1e30002431 on kirrg001:fix/image-properties into 0d385df8b20fabc7093f66c6a0c16243e52b42ae on TryGhost:master.

@kirrg001 there shouldn't be any underscored names in the client, all properties/attributes/methods are camelCase so for example feature_image should be featureImage

@kevinansfield 👍
[refs https://github.com/TryGhost/Ghost-Admin/blob/master/app/serializers/application.js#L20-L22]

WIP again, testing something with image deletion.

Changes Unknown when pulling 689703a5fcad260761eea835236856f82eb83d42 on kirrg001:fix/image-properties into ** on TryGhost:master**.

Ok this is ready to review now.

Coverage increased (+0.02%) to 73.376% when pulling 0d0032a2ee116ce986da35b4c67410106446d10b on kirrg001:fix/image-properties into 1f3b79e289cccaf34f0275b228cbdd69b7ccd633 on TryGhost:master.

@kevinansfield Thanks!
I have pushed it as separate commit https://github.com/TryGhost/Ghost-Admin/pull/661/commits/d588f21aef5e6cc55aee42c911695527b0dbfdea

Coverage increased (+0.02%) to 73.376% when pulling d588f21aef5e6cc55aee42c911695527b0dbfdea on kirrg001:fix/image-properties into 1f3b79e289cccaf34f0275b228cbdd69b7ccd633 on TryGhost:master.


If the finishReason is not returned, then the streaming will not work.

I was trying to use another LLM. and it always can not streaming well.
So after checked the source code and did some troubleshoting work. I found the reason here.
Because my LLM model does not return a finishReason.
It works well after I changed the code here.
There are some response, that I got from the LLM server.
data: {"created":1732022963,"id":"de598844107d49db83209a7836362406","model":"xxxx-turbo","version":"202409241030","choices":[{"index":0,"delta":{"role":"assistant","content":"我可"}}],"search_info":{"mindmap":{}},"processes":{},"usage":{"prompt_tokens":1061,"completion_tokens":22,"total_tokens":1083}}

data: {"created":1732022963,"id":"de598844107d49db83209a7836362406","model":"xxxx-turbo","version":"202409241030","choices":[{"index":0,"delta":{"role":"assistant","content":"以帮"}}],"search_info":{"mindmap":{}},"processes":{},"usage":{"prompt_tokens":1061,"completion_tokens":24,"total_tokens":1085}}

data: {"created":1732022963,"id":"de598844107d49db83209a7836362406","model":"xxxx-turbo","version":"202409241030","choices":[{"index":0,"delta":{"role":"assistant","content":"你的"}}],"search_info":{"mindmap":{}},"processes":{},"usage":{"prompt_tokens":1061,"completion_tokens":26,"total_tokens":1087}}

data: {"created":1732022963,"id":"de598844107d49db83209a7836362406","model":"xxxx-turbo","version":"202409241030","choices":[{"index":0,"delta":{"role":"assistant","content":"吗？"}}],"search_info":{"mindmap":{}},"processes":{},"usage":{"prompt_tokens":1061,"completion_tokens":28,"total_tokens":1089}}

data: {"created":1732022963,"id":"de598844107d49db83209a7836362406","model":"xxxxx-turbo","version":"202409241030","choices":[{"index":0,"finish_reason":"stop","delta":{"role":"assistant"}}],"search_info":{"mindmap":{}},"processes":{},"usage":{"prompt_tokens":1061,"completion_tokens":29,"total_tokens":1090}}

data: [DONE]

Thank you. In general I’d prefer not to stray from the official API, but in this case it’s not a big deal. I’ll probably go in a different direction, checking instead for !finishReason. I’m testing the change locally and if it’s good it’ll eventually be in the next release.


added shopify missing scripts

thisi two scripts were mentioned in docs but not present in the package json
 "s:e:create": "shopify app scaffold extension",
 "s:e:deploy": "shopify app deploy"

found out you don't accept PR, no issue, i thought let me fix it is public repo
closing PR

Extensions are moved out of the base repo. Take a look here - https://github.com/kinngh/shopify-app-js/
What you want to do is pull extensions folder outside of your app. I saw a lot of people run into conflicts by using that method, and I decided to remove those scripts entirely from the package.json. Thank you for flagging this!

I've made changes to both the Express and Next.js repos to reflect the change on extensions and make a reference to the kinngh/shopify-app-js package. Thank you for flagging this!


Cannot build with Carthage, Xcode 9, Swift 3.2, Swift 4.0

Build Failed
Task failed with exit code 65:
This usually indicates that project itself failed to compile.

do we have any news about this issue?

I have released version 2.5.6 with Xcode 9 support.


Improve sort order in assertions

How it is works now
if you want a sort property that contains an array of primitives, the config would look like this:
assert/sort-something:
    subject:
      type: Schema
      property: enum
    assertions:
      sortOrder:
        direction: 'asc'

If the property contains an array of objects, you must specify the property you want to sort by
Example:
 assert/sort-something:
    subject:
      type: PathItem
      property: parameters
    assertions:
      sortOrder:
        direction: 'asc'
        property: name  # The name of the property by which the sorting occurs

If you do not specify subject property, sortOrder will use an array of object keys
Example:
   assert/sort-something:
    subject:
      type: PathItem
    assertions:
      sortOrder:
        direction: 'asc'

Will check sort order of keys from PathItemObject: [ 'summary', 'parameters', 'get' ]
Problem
If you have an array of objects and don't specify a subject: property sortOrder will check order of  the keys in each object
Solution
Check if subject: type is an array type and subject: property not specified then check the sort order by value (instead key) and if assertion: property not specified display the warning message

If you have any questions, thoughts or ideas please add them here
@adamaltman @tatomyr


Resolve Issues #134 and #135

Revamped protocol and user stories to include NIST IAL2  and IAL3 assurances as well as support for Digital Assertions from Identity Proofing Service Providers.

The changes in this PR are straightforward polishing, not something that needs substantive debate. Merging.


Fix crash from arithmetic exception.

Let's not divide by zero.

Should we close this PR (after https://github.com/google/orbit/pull/4476)


[VSCode] UnoCSS Extension not highlight and auto complete

UnoCSS version
0.61.7
Describe the bug
All of the underline-highlight and auto complete are not works in VSCode but it works <= v0.61.6.
UnoCSS Log
⚪ UnoCSS for VS Code v0.61.7

📂 roots search mode.

-----------
🛠 Resolving config for /Users/user/repo
🗂 Enabled context: [none]

The weird thing is when I am trying to debug @unocss/vscode, it works when launch debug process on VSCode.
⚪ UnoCSS for VS Code v0.61.7

📂 roots search mode.

-----------
🛠 Resolving config for /Users/user/repo
🛠 New configuration loaded from
  - /Users/user/repo/uno.config.ts
ℹ 5 presets, 1067 rules, 14 shortcuts, 50 variants, 1 transformers loaded
🗂 Enabled context: /Users/user/repo

Reproduction
Create a minimum Nuxt project and UnoCSS setup, open VSCode with UnoCSS Extension installed.
System Info
VSCode: Version: 1.91.1 (Universal)
macOS 14
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Roll back to version 0.61.6 and it will work normally.

me too, and roll back to 0.61.6 is working for me

back to 0.61.6

roll back to 0.61.6 will work.
and how to do this

click vscode extension panel
right click UnoCSS extension and choose the ‘Install Another Version’

Hopefully ac7c804448ffaf9a8574c6ebc06b42b3335d23c9 should fix it

Seems to be fixed now


Missing input file '@curl//:lib/pipeline.h'

System information

OS Platform and Distribution: Ubuntu 18.04
TensorFlow installed from (source or binary): source
TensorFlow version: 2.0
Python version: 3.7.3
Bazel version (if compiling from source): 0.25.3
GCC/Compiler version (if compiling from source): 7.4.0

Problem Description
While building the pip package from source, I encounter the below error.
ERROR: /users/arung/tensorflow/tensorflow/python/BUILD:4855:1: //tensorflow/python:pywrap_tensorflow_internal_py_wrap: missing input file '@curl//:lib/pipeline.h'
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /users/arung/tensorflow/tensorflow/python/BUILD:4855:1 1 input file(s) do not exist
INFO: Elapsed time: 82.408s, Critical Path: 15.68s
INFO: 675 processes: 675 local.
FAILED: Build did NOT complete successfully

Sequence of commands
./configure
bazel build --config=v2 //tensorflow/tools/pip_package:build_pip_package

This should have been fixed yesterday by this commit:
https://github.com/tensorflow/tensorflow/commit/961eaa691ac4602bfb0fd04a3d6a73217ae63f69
[My teammate was getting the same error and it is now fixed in the latest 2.0 code.]

Closing this since its resolved in latest tf 2.0 nightly. Feel free to reopen if having problems. Thanks!


document has some language issues

Describe the bug
In the document,there is some language issues.something like kindling is splled as kinndling,active as ative,development as devlopment
Reproduce
i will not list all the problems
kindling spell as kinndling
active as ative,development as devlopment

Closed via #258


[CODE] Favor pathlib over path string manipulation

It would be better to not manually work with path strings but use the modern pathlib instead.
https://github.com/bigbio/sdrf-pipelines/blob/837af51f360e81d5b9b6b10a21698fc4c7a3c582/sdrf_pipelines/parse_sdrf.py#L124

Note that Path is orange in the above code snippet? That's because it is the name of the Path object in the Python builtin pathlib library and considered an internal variable. If possible these names should not be used for custom variables if not for a very good reason.


SyntaxError on yo keystone

Hi, was hoping to test out keystone for a site but ran into an issue with running the generator.

generator-keystone 3.1.6
Yo 1.8.1
Node 4.4.4

All works fine with answering the questions but as soon as I answer the include extra code comments (answer does not affect outcome), I get the following SyntaxError.
? ------------------------------------------------
    Finally, would you like to include extra code comments in
    your project? If you're new to Keystone, these may be helpful. No
/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/node_modules/lodash/dist/lodash.js:6309
        throw e;
        ^

SyntaxError: Unexpected token =
    at Function (native)
    at Function.template (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/node_modules/lodash/dist/lodash.js:6306:22)
    at KeystoneGenerator.underscore [as _engine] (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/util/engines.js:31:14)
    at KeystoneGenerator.engine (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/actions/actions.js:314:10)
    at KeystoneGenerator.template (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/actions/actions.js:289:15)
    at KeystoneGenerator.project (/usr/local/lib/node_modules/generator-keystone/app/index.js:289:7)
    at /usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/base.js:395:14
    at processImmediate [as _immediateCallback] (timers.js:383:17)

The current version is 0.3.17, can you try running npm install -g generator-keystone to update the generator and seeing if the bug still exists?

I'm only seeing 0.3.15 on npm https://www.npmjs.com/package/generator-keystone
npm ERR! No compatible version found<EMAIL_ADDRESS>npm ERR! Valid install targets:
npm ERR! 0.3.15, 0.3.14, 0.3.13, 0.3.12, .....

Ah yeah I was overeager, 0.3.15 is the latest one, I got a bit confused with the main keystone module!

@r3wt and @luvmex have confirmed this is indeed a bug here, would appreciate somebody looking into it!

the error comes from _package.json it appears

not seeing anything obvious here https://github.com/keystonejs/generator-keystone/blob/master/app/templates/_package.json

Kind of wish lodash templates were easier to debug, but seems an additional equals sign crept in.  I've created the above linked pull request to remove it.

This won't be helpful, but I'm experiencing this same problem with a fresh install. Happy to provide more info if needed.

@troystarwalt its already fixed, and should land soon. see @misterdai 's open PR

Just saw that. Thank you!

Thanks @misterdai, that was quick, merged, will release asap!

Released as v0.3.16!

Hi guys, I'm still experiencing this error. I believe mine might be slightly different. The error points to Unexpected token 'else' instead of '='. Currently running v.0.3.16.
Here is my error:
**_/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/node_modules/lodash/dist/lodash.js:6309
throw e;
^
SyntaxError: Unexpected token else
at Function (native)
at Function.template (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/node_modules/lodash/dist/lodash.js:6306:22)
at KeystoneGenerator.underscore [as _engine] (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/util/engines.js:31:14)
at KeystoneGenerator.engine (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/actions/actions.js:314:10)
at KeystoneGenerator.template (/usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/actions/actions.js:289:15)
at KeystoneGenerator.tasks (/usr/local/lib/node_modules/generator-keystone/app/index.js:306:8)
at /usr/local/lib/node_modules/generator-keystone/node_modules/yeoman-generator/lib/base.js:395:14
at processImmediate [as immediateCallback] (timers.js:383:17)**
Thanks!

@mxstbr looks like coming from https://github.com/keystonejs/generator-keystone/blob/master/app/templates/_Gruntfile.js#L34 this little bad boy(<% } %>) should not be there.

@r3wt I'd be wary of assuming what a contributor did or did not do. People make mistakes.
Perhaps we should begin testing this command line tool https://blog.engineyard.com/2014/bats-test-command-line-tools
cc @webteckie

If it helps, I was able to update to the newest version and had no problems running the generator on my end.

@r3wt I'd be wary of assuming what a contributor did or did not do. People make mistakes.

@morenoh149 I'm not sure you can classify it as an assumption, since running the code results in an error. Agree to disagree on that point, and my post was not to call anyone out specifically (Full disclosure, i didn't test my PR's either), but rather to highlight the need for a review process, to prevent this sort of thing from happening again. I'm sorry if i hurt anyone's feelings, that was certainly not my intention...
Re the Engineyard blog posts,thats a good find. Wonder if we could simulate the dialog process or mock it in someway.
#!/usr/bin/env bats
@test "Check that generator-keystone runs successfully" {
    // run tests here.
    [ $status = 0 ]
}

I think if you sleep 10 between cli entries and check that the filesystem has certain files, that'd be a complete test.

@Mariano89 I added this PR which should fix your issue: https://github.com/keystonejs/generator-keystone/pull/195

#195 @Mariano89 this should fix your issue

@r3wt just to cover myself ;) I didn't select Grunt when I fixed the other issue with _package.json so I'll pass the buck to git blame on that one :)

I have chosen gulp instead of grunt and it generated the project.

@younesherlock the PR I just had merged should have grunt working fine if you were having issues before I would try #195

Just got the same issue. =(

Hi,
Same issue with the following releases :

generator-keystone 3.7.3
node 6.2.1
yo 1.8.4

Still having this problem if generating the project with grunt

You need to checkout the latest master branch for the fix I had merged in #195. A new tag hasn't been released in 30 days so NPM won't include the changes to fix grunt.


Unable to make calls on Zoom and Google Meet.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Launch the new Expensify app.
Open a chat.
Click on the call icon.
Click on Zoom or Google Meet.

Expected Result:
The call should be connected to the chat member.
Actual Result:
Zoom Application was launched but a call was not made.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.3.43-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/7846a729-cbac-4228-b0d6-38bd4bc0b3b0

Expensify/Expensify Issue URL:
Issue reported by: not added by the contributor
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689607954471729
View all open jobs on GitHub

I don't think this is a bug. The call button creates a new Zoom or Google Meet call, but unless I'm mistaken it's not designed to do anything else like invite the other DM member to the call.
If I'm missing that, or misunderstanding, we can reopen this!


Merge MONDO:0011292 'dermatitis, atopic' into MONDO:0004980 'atopic eczema'

closes https://github.com/monarch-initiative/mondo/issues/7712

This is failing from the qc check sparql/qc/mondo/qc-omim-subsumption.sparql. Both the parent MONDO:0004980 'atopic eczema' and child MONDO:0007817 'IgE responsiveness, atopic' have xrefs to OMIM and these xrefs are annotated as MONDO:equivalentTo, however each of these xrefs seem correct so I have added the exclude from qc check to the child term.

@twhetzel please share your analysis to support this merge in the issue. Based on what the analysis shows, changes in the ontology might be required. I think this specific PR should either be closed, or updated based on the results of the analysis.

This was definitely a tricky case and the thing that was a red flag for me was the fact that the QC failed and there was the OMIM subsuming another OMIM term, which I've been trained to notice as a red flag.

I thought they should be merged based on the labels for OMIM:603135, however the OMIM and OMIMPS I noticed after merging was concerning.

Thanks @nicolevasilevsky - it's the first time I've encountered this. Are there some changes we can make to Mondo so this is more clear what is intended here?

@twhetzel see my comments here: https://github.com/monarch-initiative/mondo/issues/7712#issuecomment-2316010506
for what I recommend doing. We could walk through this on the curation call next week if needed, I plan to attend the call.

@nicolevasilevsky I read your comment, but am not 100% sure what all the needed changes are. @sabrinatoro what do you want to do about this ticket related to the September release?

Looking at this more closely, I think maybe a merger is the right approach, but we just need to move the OMIMPS to the susceptibility term:

Thanks, I can make that change for the OMIMPS.

I agree with @nicolevasilevsky 's comments and suggestions.
It should be noted that 'dermatitis atopic,1' (which is the susceptibility term) is an "included" OMIM:603165. I have not looked at whether we have a mondo term for this included term.

I agree with @nicolevasilevsky 's comments and suggestions. It should be noted that 'dermatitis atopic,1' (which is the susceptibility term) is an "included" OMIM:603165. I have not looked at whether we have a mondo term for this included term.

I checked and we do: MONDO:0100181 :)


Scylla Integration is woefully out of date

The ScyllaDB integration hasn't been updated since ScyllaDB 3.1. Scylla only supports the two most recent versions released, so currently the Scylla integration does not support a supported version of ScyllaDB. There are 12 version upgrades worth of metric additions/renames upstream has created.
I see a few paths out of this problem

apply the changes to the integration so they support older ScyllaDB versions gracefully
special case billing for Scylla metrics ingested via the prometheus/openmetrics integration
declare this integration officially unsupported and remove it from future agent versions

Currently it seems like option 3 is the closest to the reality on the ground since it's missing 3.5 years of changes, but that would require taking this blog post down, updating product documentation, etc- https://www.datadoghq.com/blog/monitor-scylla-with-datadog/
Thanks!
Steps to reproduce the issue:

Install a version of ScyllaDB released after January 15 2020 (the 3.2 tagging date)
Discover DataDog isn't ingesting the new/updated metrics, and that there's actually monitoring gaps due to metric renames.
Be sad, contemplate installing the Scylla Monitoring stack and removing DataDog completely from those hosts, but instead file an issue to see how the vendor responds before such drastic measures :D

Describe the results you received:
Incomplete metrics from an integration that hasn't seen an update in 3.5 years.
Describe the results you expected:
Complete metrics from an integration regularly updated by a company we're paying. 😅
Additional information you deem important (e.g. issue happens only occasionally):
Here are the links to the metric changelogs from ScyllaDB that outline additions/removals/changes!

https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.1-to-3.2/metric-update-3.1-to-3.2.html
https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.2-to-3.3/metric-update-3.2-to-3.3.html
https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.3-to-4.0/metric-update-3.3-to-4.0.html
https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/metric-update-4.0-to-4.1.html
https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.1-to-4.2/metric-update-4.1-to-4.2.html
https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.2-to-4.3/metric-update-4.2-to-4.3.html
https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.3-to-4.4/metric-update-4.3-to-4.4.html
https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.4-to-4.5/metric-update-4.4-to-4.5.html
https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.5-to-4.6/metric-update-4.5-to-4.6.html
https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.6-to-5.0/metric-update-4.6-to-5.0.html
https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-5.0-to-5.1/metric-update-5.0-to-5.1.html
https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-5.1-to-5.2/metric-update-5.1-to-5.2.html

Be sad, contemplate installing the Scylla Monitoring stack and removing DataDog completely from those hosts, but instead file an issue to see how the vendor responds before such drastic measures :D

Before we take such drastic measures, I'm going to submit a PR to get this updated to match current stable release. I did get a kick out of this comment though 😆

I'm closing this assuming #15592 solves the issue. Feel free to reopen if that's not the case.


Azure upload using chunks

Need to upload large files using chunks to azure.  Any suggestion's @kkazuo

You can use BlobType.AppendBlob.
await storage.putBlob('/example/append.txt', type: BlobType.AppendBlob);
await storage.appendBlock('/example/append.txt', body: 'more 1\n');
await storage.appendBlock('/example/append.txt', body: 'more 2\n');
await storage.appendBlock('/example/append.txt', body: 'more 3\n');

Changing type to BlobType.AppendBlob
Still it returns as : azure upload exception: <?xml version="1.0" encoding="utf-8"?><Error><Code>RequestBodyTooLarge<[/Code]()><Message>The request body is too large and exceeds the maximum permissible limit.

interesting.
and what is the actually size of your data.

Duration: 4 min 30 sec
Size: 204 MB

what is the size of each data of .appendBlock call?

Can you please share any platform id to contact you ? If possible...

in my opinion, you have hit a size limit of Azure Bolb Storage.
https://docs.microsoft.com/en-us/rest/api/storageservices/Understanding-Block-Blobs--Append-Blobs--and-Page-Blobs
by the way, did you know an another package to access Azure Blob that called azstore.
and could you try that? (i am not any relations to azstore dev)
https://pub.dev/packages/azstore


指针默认在名字的下拉框

Is your feature request related to a problem? Please describe.
焦点问题
Describe the solution you'd like
当弹出窗口时，自动指向名字下拉框

same as #25


[FIX] babs-init creates a new branch git-annex adjusted branch at the end for analysis DataLad dataset

Shreya from Alexander-Bloch's lab found that, when running babs-init on the BIDS data she created, the last commit it creates in analysis DataLad dataset is a git-annex adjusted branch. Therefore it's one commit ahead of output and intput RIA store's.
To solve this issue, she ran git checkout master, then it's back to the master branch, which has the same head as output and input RIA store.

Details for babs-init: To be filled

(babs) [ BABS_CATD]$ datalad clone output_ria/5e6/f8378-0764-4e21-aa0a-6d58ba4d7c95/ merge_ds3
[INFO   ] Filesystem does not allow removing write bit from files.
[INFO   ] Detected a crippled filesystem.
[INFO   ] Disabling core.symlinks.
[INFO   ] Entering an adjusted branch where files are unlocked as this filesystem does not support locked files.
[INFO   ] Switched to branch 'adjusted/master(unlocked)'
[INFO   ] Remote origin: This repository is not initialized for use by git-annex, but ./../output_ria/5e6/f8378-0764-4e21-aa0a-6d58ba4d7c95/annex/objects/ exists, which indicates this repository was used by git-annex before, and may have lost its annex.uuid and annex.version configs. Either set back missing configs, or run git-annex init to initialize with a new uuid.

git-annex version : 10.20230408-g5b1e8ba77

Error message from babs-merge :
(babsfix) [ BABS_CATD]$ babs-merge --project-root $PWD
Cloning output RIA to 'merge_ds'...
[INFO   ] Filesystem does not allow removing write bit from files.
[INFO   ] Detected a crippled filesystem.
[INFO   ] Disabling core.symlinks.
[INFO   ] Entering an adjusted branch where files are unlocked as this filesystem does not support locked files.
[INFO   ] Switched to branch 'adjusted/master(unlocked)'
[INFO   ] Configure additional publication dependency on "output-storage"
configure-sibling(ok): . (sibling)
install(ok): /mnt/isilon/bgdlab_resnas03/code/synthseg_image_test/BABS_CATD/merge_ds (dataset)
action summary:
  configure-sibling (ok: 1)
  install (ok: 1)

Listing all branches in output RIA...

Finding all valid job branches to merge...
Git default branch's name of output RIA is: 'master'

Merging valid job branches chunk by chunk...
Total number of job branches to merge = 2
Chunk size (number of job branches per chunk) = 2000
--> Number of chunks = 1
Merging chunk #1 (total of 1 chunk[s] to merge)...
  sub-23823_synthseg-0-0-1.zip is a git-annex pointer file. Its content is not available in this repository. (Maybe sub-23823_synthseg-0-0-1.zip was copied from another repository?)
Fast-forwarding to: remotes/origin/job-7191194-sub-23823
Trying simple merge with remotes/origin/job-7191195-sub-24060
Merge made by the 'octopus' strategy.
 sub-23823_synthseg-0-0-1.zip | 1 +
 sub-24060_synthseg-0-0-1.zip | 1 +
 2 files changed, 2 insertions(+)
 create mode 100755 sub-23823_synthseg-0-0-1.zip
 create mode 100755 sub-24060_synthseg-0-0-1.zip

Pushing merging actions to output RIA...
fatal: The current branch adjusted/master(unlocked) has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin adjusted/master(unlocked)

To have this happen automatically for branches without a tracking
upstream, see 'push.autoSetupRemote' in 'git help config'.

Traceback (most recent call last):
  File "/home/gudapatis/miniconda3/envs/babsfix/bin/babs-merge", line 8, in <module>
    sys.exit(babs_merge_main())
  File "/home/gudapatis/miniconda3/envs/babsfix/lib/python3.9/site-packages/babs/cli.py", line 702, in babs_merge_main
    babs_proj.babs_merge(args.chunk_size, args.trial_run)
  File "/home/gudapatis/miniconda3/envs/babsfix/lib/python3.9/site-packages/babs/babs.py", line 1735, in babs_merge
    proc_git_push.check_returncode()
  File "/home/gudapatis/miniconda3/envs/babsfix/lib/python3.9/subprocess.py", line 460, in check_returncode
    raise CalledProcessError(self.returncode, self.args, self.stdout,
subprocess.CalledProcessError: Command '['git', 'push']' returned non-zero exit status 128.

It seems this additional adjusted branch was also created when preparing a DataLad dataset (e.g., after datalad create and datalad save or so), or datalad clone a dataset or output RIA.
It also seems this may only happens on their cluster's fileshare directory, but not in Shreya's home directory on the cluster. We are investigating more here.

This turned out to be due to the file system


Remove invalid leading 1 from zip code

The README specifies that the first number of the area code must fall between 2 and 9. This updates the examples to lead with a 2 instead of a 1 for the area code, and adds an extra test verifying that the area code does not begin with a 1.

Awesome, thanks for catching this and for opening up a PR! Looks good to me, I'll wait for @sdavids13 to confirm :)


Boot strap page new nav

Added to Navigation bar

@blam-codes : please rebase this branch with main and force push.


Request to implement delay on some elements

How feasible is it to implement a 'delay' method so it would be possible to keep some elements in place for specified amount of time before they get animated (follow the scroll)? Primary use is for the elements that are located "above the fold". Looking for a way to start parallax scroll with elements animated one by one.

Another way yo describe what I'm thinking about is 'easing in / easing out' effect.

Hi, thanks for using Rellax.
I usually achieve this effect with just CSS transitions.
(I can't right now, but I'll leave some examples later)

@p-realinho Thanks!

Did it work?
Sorry, I forgot to post the examples 😕

I didn't try it yet. If you have an example that would be helpful.

.rellax {
    transition: transform .6s;
}

This is probably the bare minimum.
You can (and should) of course play with the durations and easings.
.rellax {
    transition: transform 30s cubic-bezier(0, 1.5, 0, 1);
}

I find this duration/easing combo particularly useful, because although the element follows the scroll immediately, it slowly keeps translating after the scroll stops, giving it a sort of really long ease-out effect.
Hope it helps!

Thanks, I played with various options and see what you mean now. It is an interesting effect that seems to work best for the "ease out". My goal is a bit different. I want to hold elements in position while the scroll is happening. Let's say you start scrolling and you want one of the elements to stay in original position for a second longer.

Hey @iapparatus, appreciate the issue, but I think this is well beyond the scope of the Rellax library.
I'm actually pretty into your idea, but I think it's worth writing something custom to make this work.


[BUG] Module Not Found for Python 3.12. It works in Python 3.10 for Setuptools version 65.5.0.

setuptools version
70.0.0
Python version
Python 3.12
OS
Mac M2 Pro Max, Mac M1 Pro
Additional environment information
[metadata]
name = backend
description = backend
author = Kimchi
platforms = unix, linux, osx, win32
classifiers =
Programming Language :: Python :: 3.10
Programming Language :: Python :: 3.11
Programming Language :: Python :: 3.12
version = 0.1.0
[options]
packages = find:
install_requires =
requests >= 2
python_requires = >=3.10
requirements.txt file
aiohttp==3.9.5
asyncio==3.4.3
boto3==1.34.122
fastapi==0.111.0
firebase-admin==6.5.0
google-cloud-storage==2.17.0
httpx==0.27.0
poetry==1.1.12
pre-commit==3.7.1
pytest==8.2.2
pytest==8.2.2
pytest-mock==3.14.0
requests
setuptools==70.0.0
uvicorn==0.30.1
wheel==0.43.0
gemini_webapi==1.5.1
Description
File Name: generate_background.py
from api.controllers.helpers import (
generate_background_aws,
generate_background_firebase,
generate_background_google,
)
This returns the error that ModuleNotFoundError: No module named 'api'
File Path:
src
--api
----controllers
------helpers
--------init.py
--------aws.py
--------firebase.py
--------gcs.py
------generate_background.py
In the helpers folder, The init file looks like
File Name: init.py
from .firebase import generate_background_firebase
from .gcs import generate_background_google
all = [
"generate_background_aws",
"generate_background_firebase",
"generate_background_google",
]
And the aws.py file has this kind of function:
File Name: aws
async def generate_background_aws()
Please let me know if any of the change I should make to make this work. Our team is wondering if we should downgrade our python version to 3.10 which worked for one member.
Expected behavior
We should be able to import the local modules correctly.
How to Reproduce
Just try to run the file after making the similar file and path structure. It returns an error....
Output
Process SpawnProcess-1:
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/multiprocessing/process.py", line 314, in _bootstrap
    self.run()
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/Users/taeyangkim/Dev/ai-video-gen/backend/env/lib/python3.12/site-packages/uvicorn/_subprocess.py", line 80, in subprocess_started
    target(sockets=sockets)
  File "/Users/taeyangkim/Dev/ai-video-gen/backend/env/lib/python3.12/site-packages/uvicorn/server.py", line 65, in run
    return asyncio.run(self.serve(sockets=sockets))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "uvloop/loop.pyx", line 1517, in uvloop.loop.Loop.run_until_complete
  File "/Users/taeyangkim/Dev/ai-video-gen/backend/env/lib/python3.12/site-packages/uvicorn/server.py", line 69, in serve
    await self._serve(sockets)
  File "/Users/taeyangkim/Dev/ai-video-gen/backend/env/lib/python3.12/site-packages/uvicorn/server.py", line 76, in _serve
    config.load()
  File "/Users/taeyangkim/Dev/ai-video-gen/backend/env/lib/python3.12/site-packages/uvicorn/config.py", line 434, in load
    self.loaded_app = import_from_string(self.app)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/taeyangkim/Dev/ai-video-gen/backend/env/lib/python3.12/site-packages/uvicorn/importer.py", line 22, in import_from_string
    raise exc from None
  File "/Users/taeyangkim/Dev/ai-video-gen/backend/env/lib/python3.12/site-packages/uvicorn/importer.py", line 19, in import_from_string
    module = importlib.import_module(module_str)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 995, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/Users/taeyangkim/Dev/ai-video-gen/backend/src/main.py", line 2, in <module>
    from .api.routes import image_router, text_router
  File "/Users/taeyangkim/Dev/ai-video-gen/backend/src/api/__init__.py", line 1, in <module>
    from . import controllers, routes, utils
  File "/Users/taeyangkim/Dev/ai-video-gen/backend/src/api/controllers/__init__.py", line 2, in <module>
    from .generate_background import generate_background
  File "/Users/taeyangkim/Dev/ai-video-gen/backend/src/api/controllers/generate_background.py", line 8, in <module>
    from helpers.aws import generate_background_aws
ModuleNotFoundError: No module named 'helpers'

Hi @brightlightkim , isn't the a problem because the way you wrote the import statement? Shouldn't it be a relative import instead of the absolute import?
The other thing I can see that you are using find: in setup.cfg, but some of your folders don't contain an __init__.py file.

Hey @abravalheri,
I'm having a similar issue with python-3.12 only with my package. While running on 3.8/9/10/11, I can build my package and run my tests, please check the log below.
Package: cocotbext-ahb
Setup file: setup.py
Ps.: I modified my local noxfile.py to include 3.12 in the run session.
root@bbfc4b27bcad:/cocotbext-ahb# nox -s run-3.12 -- -k "test_ahb_lite_sram.py"
nox > Running session run-3.12
nox > Re-using existing virtual environment at .nox/run-3-12.
nox > python -m pip install pytest pytest-xdist pytest-sugar pytest-cov pytest-split cocotb-bus==0.2.1 cocotb-test==0.2.4 'cocotb>=1.8.0'
nox > python -m pip install -e .
nox > Command python -m pip install -e . failed with exit code 1:
Obtaining file:///cocotbext-ahb
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Checking if build backend supports build_editable: started
  Checking if build backend supports build_editable: finished with status 'done'
  Getting requirements to build editable: started
  Getting requirements to build editable: finished with status 'error'
  error: subprocess-exited-with-error

  × Getting requirements to build editable did not run successfully.
  │ exit code: 1
  ╰─> [27 lines of output]
      Traceback (most recent call last):
        File "/cocotbext-ahb/.nox/run-3-12/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/cocotbext-ahb/.nox/run-3-12/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/cocotbext-ahb/.nox/run-3-12/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 132, in get_requires_for_build_editable
          return hook(config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-px4dvd0v/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 448, in get_requires_for_build_editable
          return self.get_requires_for_build_wheel(config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-px4dvd0v/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-px4dvd0v/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
          self.run_setup()
        File "/tmp/pip-build-env-px4dvd0v/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 487, in run_setup
          super().run_setup(setup_script=setup_script)
        File "/tmp/pip-build-env-px4dvd0v/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 311, in run_setup
          exec(code, locals())
        File "<string>", line 4, in <module>
        File "/cocotbext-ahb/cocotbext/ahb/__init__.py", line 16, in <module>
          from .ahb_master import AHBLiteMaster, AHBMaster
        File "/cocotbext-ahb/cocotbext/ahb/ahb_master.py", line 10, in <module>
          import cocotb
      ModuleNotFoundError: No module named 'cocotb'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build editable did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
nox > Session run-3.12 failed.
root@bbfc4b27bcad:/cocotbext-ahb#

Version
Package      Version                                                                                │        modified:   cocotbext/ahb/utils.py
------------ ---------                                                                                │        deleted:    monitor.py
argcomplete  3.4.0                                                                                │        modified:   noxfile.py
colorlog     6.8.2                                                                                │        modified:   tests/test_ahb_lite_sram.py
distlib      0.3.8                                                                                │
filelock     3.15.1                                                                                │no changes added to commit (use "git add" and/or "git commit -a")
nox          2024.4.15                                                                                │❯ rm -rf log.txt
packaging    24.1                                                                                │╭─     ~/projects/cocotbext-ahb  on    master *3 !5 ······················
pip          24.0                                                                                │················ ✔  at 06:45:25 pm 
platformdirs 4.2.2                                                                                │╭─     ~/projects/cocotbext-ahb  on    master *3 !5 ······················
setuptools   68.1.2                                                                                │··············· ✔  at 06:45:25 pm   ─╮
virtualenv   20.26.2                                                                                │╭─     ~/projects/cocotbext-ahb  on    master *3 !5 ····· ✔  at 06:45:25
wheel        0.42.0

Hi @aignacio , I don't think your problem is the same as discussed in this issue.
It seems that you are trying to perform an import statement during build time without defining a built time dependency in a way that pip understands (i.e. via pyproject.toml).
You probably forgot to factor in the "build isolation" behaviour that sometimes is triggered by pip (don't ask me when, it is internal pip heuristics...).
In "build isolation"  pip completely ignore everything you have installed and creste a brand new throw away environment just for the build.
Please revise your setup/CI to make sure you account for that. After that if you still have problems that are associated with setuptools behaviour, please open a separated issue (as I don't see how the original problem is related to your use case).

pyproject.toml

Hi @aignacio , I don't think your problem is the same as discussed in this issue.
It seems that you are trying to perform an import statement during build time without defining a build time dependency in a way that pip understands (i.e. via pyproject.toml).
You probably forgot to factor in the "build isolation" behaviour that sometimes is triggered by pip (don't ask me when, it is internal pip heuristics, maybe it is described in pip's docs...).
In "build isolation" pip completely ignore everything you have installed and create a brand new throw away environment just for the build.
Please revise your setup/CI to make sure you account for that. After that if you still have problems that are associated with setuptools behaviour, please open a separated issue.

Thanks @abravalheri, that solved the problem, It was a miss the pyproject.toml indeed! I just wonder now how it is working for previous python versions...

the "build isolation" behaviour that sometimes is triggered by pip (don't ask me when, it is internal pip heuristics, maybe it is described in pip's docs...).

☝


[$500] Expense - System message for report submission is not copied when copied to clipboard

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR https://github.com/Expensify/App/pull/32157
Action Performed:
Precondition:

User is an employee of a Collect workspace

Log in to ND as the employee
Go to the workspace chat > + > Request money
Create a manual request
Click on the expense preview > Submit
Click on the header subtitle to return to workspace main chat
Click on the expense preview
Right click on the 'report submission' message > Copy to clipboard
Paste it in the composer

Expected Result:
The system message for 'report submission' is copied
Actual Result:
The system message for 'report submission' is not copied
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/991e8277-c601-4b03-a785-cc326a7fcebe
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01dc72215454974184
Upwork Job ID:<PHONE_NUMBER>439400960
Last Price Increase: 2023-11-30

Proposal
Please re-state the problem that we are trying to solve in this issue.
Expense - System message for report submission is not copied when copied to clipboard
What is the root cause of that problem?
We are not handling the sumission report action case in here
https://github.com/Expensify/App/blob/a7460f7f81c9999cf20964e67b6f9029dc18a51f/src/pages/home/report/ContextMenu/ContextMenuActions.js#L263-L264
What changes do you think we should make in order to solve the problem?

We need to add to here
https://github.com/Expensify/App/blob/a7460f7f81c9999cf20964e67b6f9029dc18a51f/src/pages/home/report/ContextMenu/ContextMenuActions.js#L284-L287
this
else if (reportAction.actionName === CONST.REPORT.ACTIONS.TYPE.SUBMITTED) {
                    Clipboard.setString(lodashGet(reportAction, 'message.0.text', ''));
                }

What alternative solutions did you explore? (Optional)

Just checked
@FitseTLT proposal works correctly. I think we should go with this.
🎀 👀 🎀 C+ reviewed

Please ignore my previous comment
The issue is open for proposals again.

@FitseTLT You are kind of right. But need more changes to work actually.

You may need to modify according to this reportAction

Any way to get access to/part of Collect Workspace?

Ask this on slack when you are assigned

@shubham1206agra please complete the bugzero checklist thanks!

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@shubham1206agra] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/28947
[x]  [@shubham1206agra] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/28947#issuecomment-1862441403
[x]  [@shubham1206agra] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: Not required
[x]  [@shubham1206agra] Determine if we should create a regression test for this bug. No as it was edge case from backend
[x]  [@shubham1206agra] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ]  [] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@lakchote Bump

@laurenreidexpensify Can you process payment here please?

Payment Summary:
Contributor $500 paid in Upwork @bernhardoj
C+ $500 paid in Upwork @shubham1206agra


Use normalized build jvm opts in TAPI tests

This fixes https://github.com/gradle/gradle-private/issues/3216
Sometimes the daemon reuse tests fail because of different locale
system properties: user.country/user.language, etc. We normalize
these system properties before the tests.

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.

Thanks @donat !


Set default arguments in the entrypoint

Provide default values for the entrypoint for uses other than from the github
workflow.
Closes #19

Missed one line compared to the earlier PR. I also tested this one.


Support Iterating and Indexing on Nightly

It seems that supporting Iterating and Indexing on stable is tricky at the moment, due std::iter::Step and std::slice::SliceIndex having experimental APIs. For Step, I've considered using the step crate to accomplish the same purpose. The only issue is it forces users to implement step::Step if they want to iterate over a custom steppable range.
An alternative is to make iterating and indexing both available, in the same manner as they are implemented for the standard library range types, on nightly channels only. It seems that [autocfg](https://crates.io/crates/autocfg does not currently offer probing channels yet, although it may come in the future. rustc_version is another crate which can probe channels.
Another possibility is to lock iterating and indexing behind a nightly feature, allowing users to opt-in using cargo features.

Indexing will actually not have to be nightly-only. Turns out, SliceIndex is both not necessary for indexing and actually is useless since it is a sealed trait. The only thing to implement is Index and IndexMut for each type that should be indexable by these ranges. Note that these impls will only be available on rustc 1.41.0 and up.

Almost all indexing is done. The only thing that may still be desired is implementing Index<RangeFromExclusive<usize>> for CStr (similar to Index<RangeFrom<usize>> for CStr, which is already implemented. However, CStr is only available on std, which may require feature-gating. There is also a cstr_core crate, which works on core, but involves bringing in another dependency and should therefore also be feature-gated. Possibly, a solution could be implementing both and allowing users to activate whatever implementation they need.


Update api

Codecov Report

Merging #296 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #296   +/-   ##
=========================================
  Coverage     96.55%   96.55%
  Complexity       21       21
=========================================
  Files             4        4
  Lines           203      203
  Branches          8        8
=========================================
  Hits            196      196
  Misses            5        5
  Partials          2        2

Flag
Coverage Δ
Complexity Δ

#go
96.93% <ø> (ø)
0.00 <ø> (ø)

#java
96.42% <ø> (ø)
21.00 <ø> (ø)

#node_js
95.91% <ø> (ø)
0.00 <ø> (ø)

Continue to review full report at Codecov.

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


Callback can't have return value with explicit lifetime

I want to return &str of the underlying slice.
fn remove_digit<'a>(lex: &'a mut Lexer<'a, Token<'a>>) -> Option<&'a str> {
    Some(&lex.slice()[1..])
}

#[derive(Logos, Debug, PartialEq)]
enum Token<'a> {
    #[regex(r"\d[a-zA-Z]+", remove_digit)]
    WithNumber(&'a str),

    #[error]
    #[regex(r"[ \t\n\f\s]+", logos::skip, priority = 1000)]
    Error,
}

Currently this code fails:

error[E0621]: explicit lifetime required in the type of lex

 | #[derive(Logos, Debug, PartialEq)]
 |          ^^^^^
 |          |
 |          lifetime `'s` required
 |          help: add explicit lifetime `'s` to the type of `lex`: `&'s mut logos::lexer::Lexer<'s, Token<'s>>`

The problem is that lex has a shorter lifetime than the slice it borrows, but the signature of remove_digit requires that it has the same lifetime. Removing the first 'a from &'a mut Lexer allows your code to compile:
fn remove_digit<'a>(lex: &mut Lexer<'a, Token<'a>>) -> Option<&'a str> {
    Some(&lex.slice()[1..])
}

To add to this, given: &'reference mut Lexer<'source, Token<'source>>:

'reference is the lifetime of the reference which can be ephemeral if you drop your Lexer somewhere.
'source is the lifetime of the &str slice Lexer is reading.

The fact that it works without explicit annotations has nothing to do with Logos and everything to do with lifetime elision in Rust being pretty good :).

Closing this as I feel this is now documented in the handbook. If needed, feel free to re-open this issue!

@jeertmans I spend a lot of time fixing the problem described in this thread. The thread was the only place that answered it. Where exactly is it described in the book? Even if there is such an example, it honestly is hard to find, as I went a few times through it and missed it.

@jeertmans I spend a lot of time fixing the problem described in this thread. The thread was the only place that answered it. Where exactly is it described in the book? Even if there is such an example, it honestly is hard to find, as I went a few times through it and missed it.

Hello @twolodzko, indeed maybe this is a triage issue for me and I closed this issue when it should not have been closed. Let's re-open this and ask for an example to be written in the book!


[WIP] Lazy injection

My take on implementing the Lazy injection (#303). It definitely needs code cleaning, synchronicity considerations, and maybe some optimizations / api improvements.
Biggest change in the existing codebase is object graph caching, which is necessary to implement Lazy injection, as @J7mbo pointed out.
The idea is to generate an unique identifier for each graph resolution, and provide that information to  theInstanceStorage when retrieving / storing instances. Then GraphStorage is caching instances resolved in specific graphs, to return them if graph is restored. I'm keeping only weak references - this should be enough for purposes of graph caching, AFAICS has negligible memory impact and shouldn't lead to zombie instances.

While trying to make this feature more robust (e.g. properly work for registrations with arguments) I've converted to the solution, which basically makes lazy resolution implicit for all services with (AFAICS) minimal impact on performance:
There is a InstanceWrapper protocol, which is explicitly checked in the case when default resolution mechanism fails (i.e. there is no entry for InstanceWrapper type). When this happens, instance of the wrapper is created and transparently returned from resolve method.
As this additional resolution attempt is performed only when default mechanism fails, performance impacts on existing code should be minimal.
And as a bonus, this InstanceWrapper concept should easily enable optional forwarding (much more efficiently then this approach) - all one needs to do is:
extension Optional: InstanceWrapper {
    static var wrappedType: Any.Type { return Wrapped.self }

    init(inContainer container: Container, withInstanceFactory factory: @escaping () -> Any?) {
        self = factory() as? Wrapped
    }
}

I've been trying to make the Lazy feature thread safe, but it does not seem to be possible in the current model - i.e. i see no way of synchronizing instance resolution inside Lazy.instance getter.

@jakubvano wow, your idea about InstanceWrapper is very good! 👍
What problems still exist? (I mean why it is still WIP? :) )

Currently there are two areas in which I'm not completely sure how to proceed:

Thread safety  - as mentioned above, I see no way of making InstanceWrappers thread safe - it would require redesign of thread safety model (#139). However, I'm leaning towards releasing the feature despite of that (e.g. Assemblers do not support thread safety yet #221).

Provider circular dependency - Lazy circular dependencies work as expected because of graph caching. However, this mechanism cannot be used for Provider dependencies, as it would result in always returning the same instance.
My dilemma here is whether we should make circular dependencies work with Provider as well, or is it something that user would not need - One example would be something like this:

class Controller: WorkDelegate {
    private let worker: Provider<Worker>
}

extension Controller: WorkerDelegate {
    func workCompleted() {  }
}

class Worker {
   weak var delegate: WorkerDelegate?
}

Here I might expect, that every provided worker would have have the same instance of Controller as delegate.
Would definitely appreciate any input on this :)

After further consideration, I came to the conclusion that expecting the Provider circular dependencies to work in .graph goes - in a way - against the main idea behind the Provider, would probably be useful only in very niche situations, and thus it is not worth to severly complicate the implementation of graph caching.


Exasol docker - connectivity issue

Hi Team,
I have installed Docker in AWS EC2 Linux machine. I have successfully pulled Exasol image, created container and am able to connect to it from the host machine(as well as inside the container), however not able to connect from outside of the host machine. I have tried to connect to it from laptop.
Following command are working from the host Linux machine,
./exaplus -c localhost:8899 -u sys -p exasol
./exaplus -c <IP_ADDRESS>:8899 -u sys -p exasol
Tried the below from my laptop,
./exaplus -c [ip of EC2 instance]:8899 -u sys -p exasol -> Not working
Can you please help in this issue.
Thanks,
Raj

This issue is resolved by just mapping host port to container port, without limiting with ip address,
sudo docker run --name exasoldb  -p 8899:8888 --detach --privileged --stop-timeout 120 exasol/docker-db


Poor rendering quality result for custom dynerf-like dataset

https://github.com/hustvl/4DGaussians/assets/40021525/53cf365f-f143-40e0-910b-8f4446ecc4e7

the input is 66 mp4 files recorded from 66 cameras in different angles. 2 samples as below:

the initial point cloud also seems normal: points3D_downsample2.ply

after training , the result is like::
[ITER 14000] Evaluating test: L1 0.13829423837801988 PSNR 14.392739352057962 [14/04 19:28:46]
[ITER 14000] Evaluating train: L1 0.07283851898768369 PSNR 18.669121798347025 [14/04 19:28:48]

Metric evaluation progress:
Scene:  output/dynerf/nb66/ SSIM :    0.3143795
Scene:  output/dynerf/nb66/ PSNR :   14.3533792
Scene:  output/dynerf/nb66/ LPIPS-vgg:    0.6337457
Scene:  output/dynerf/nb66/ LPIPS-alex:    0.6007410
Scene:  output/dynerf/nb66/ MS-SSIM:    0.2912356
Scene:  output/dynerf/nb66/ D-SSIM:    0.3543822

Hi, I would like to know:

How may cameras do you use? How do you set your cameras (like forward-facing of sphere)? How many frames in each camera?
what is results of coarse stage? You can try the longer coarse stage to recover the static background. As I wished, coarse stage will recover static part and training 3D Gaussians for debugging. fine stage will try to learn the deformation.
what config file do you use? hypernerf?(which is designed for 150-500 frames each camera)

@guanjunwu

1. How may cameras do you use? How do you set your cameras (like forward-facing of sphere)? How many frames in each camera?

66 cameras. sphere above ground . 10 seconds x 30 fps = 300 frames

2. what is results of coarse stage? You can try the longer coarse stage to recover the static background. As I wished, coarse stage will recover static part and training 3D Gaussians for debugging. fine stage will try to learn the deformation.

Yes. trying longer coarse stage.

3. what config file do you use? hypernerf?(which is designed for 150-500 frames each camera)

use default one with batch size=2
ModelHiddenParams = dict(
kplanes_config = {
'grid_dimensions': 2,
'input_coordinate_dim': 4,
'output_coordinate_dim': 16,
'resolution': [64, 64, 64, 150]
},
multires = [1,2],
defor_depth = 0,
net_width = 128,
plane_tv_weight = 0.0002,
time_smoothness_weight = 0.001,
l1_time_planes =  0.0001,
no_do=False,
no_dshs=False,
no_ds=False,
empty_voxel=False,
render_process=False,
static_mlp=False
)
OptimizationParams = dict(
dataloader=True,
iterations = 14000,
batch_size=4,
coarse_iterations = 3000,
densify_until_iter = 10_000,
opacity_reset_interval = 60000,
opacity_threshold_coarse = 0.005,
opacity_threshold_fine_init = 0.005,
opacity_threshold_fine_after = 0.005,
# pruning_interval = 2000
)

Hi, I think the config is ok.
Meanwhile, I think the initial point clouds are not dense. Why there are not any background points?


Add HTTP Reverse Proxy content & Add nginx-proxy and h2o-proxy

There was no relevant content, it was newly inserted content.
How you do you feel about it?
If you do not like, I will fix.

/cc @veggiemonk

Oh man! That is awesome! I was currently researching this topic because I needed something like dokku but on RHEL 7. This is really good timing. Thanks


Update version error for FAR v0.15.8

There was an error in the .version file used to create the current metadata for FAR v0.15.8.  FAR v0.15.8 should be compatible with KSP 1.2.0, 1.2.1 and 1.2.2; this change should address that.

LGTM


Sharing about running segmentation code(开源的分割代码跑通了，数据集分享在下面)

https://www.jianshu.com/p/8d4f73d0471a
This is a blog introduction about how to run through the code. It also shares data sets and models. You can refer to it if necessary, and communicate more.  (怎么跑通代码以及数据集的分享都在上面的博客链接)

Thanks


Bump version to 0.2.3

It would be great to have a new release with the new parsing functionality, so I can include it in tests!

Yes, I'm in the process of making a new release, which includes the 3d PR I'm updating now.

See #12


Resolved warnings in ipynb examples

Reference Issues/PRs

What does this implement/fix? Explain your changes.

When running the example ipynb in a clean environment, ModuleNotFoundError are raised for pmdarima (sktime/forecasting/arima.py#269) and tsfresh (sktime/transformers/series_as_features/summarize/_tsfresh.py).
Reran and cleaned up .ipynb outputs (example of previous warnings below):

Does your contribution introduce a new dependency? If yes, which one?

PR checklist for new estimators

Any other comments?

Really liking this package! Hoping to contribute more than fixing typos and updating docs in the future.

Hi @alwinw, thanks for your work on this. We treat tsfresh and pmdarima as a soft dependency to keep our core dependencies to a minimum. That's why we haven't included it in setup.py. But perhaps we should add a !pip install tsfresh and ``!pip install pmdarima` line to the notebook?
And thanks for cleaning the notebook output!

Hi @mloning, thanks for explaining that to me. Interesting approach since a user can pip install sktime and hit a ModuleNotFoundError when trying to run selected functions which could become annoying. I'll remove it as a core dependency and add it into the notebook.
Just changed my PR into a WIP one until I've fixed that up and have it passing the CI pipeline (I'll install precommit locally as well so my commit history isn't full of flake8 or black fixes!)

Since there are a number of other packages we'd like to support without blowing up our list of hard dependencies, we opted for that middle way. But happy to hear about alternatives!
One suggestion we've received in the past is to add import checks and raise a more helpful error message when soft dependencies are missing (see #325).

Closed in favour of #410


Problems cloud cutting Treatlife DS03 Fan and Light Smart Switch

I recently purchased a Treatlife DS03 Fan and Light Smart Switch.  I purchased one of these in the past (3 months ago?) and successfully cloud cut it.  The one I just purchased is not successfully cutting?
I tried cutting with both firmwares.  I've attached the output from each of those runs.  Is there something I am doing wrong?
v2.1.6 run.txt
v1.1.71 run.txt

Confirmed that the device is defective.  Won't even pair to Treatlife app.


NoSuchMethodError when calling Enum extension methods against var

Dart 2.17.0
enum Test { test }

extension TestT on Test {
  get validator => validators[this];
  static final validators = {
     Test.test: '',
  }
}

TestClass(Test.test).body()

class TestClass {
  var param;
  TestClass(this.param)
  body(){
   print(param.runtimeType) // => Test
   print(param.validator)  // => NoSuchMethodError (NoSuchMethodError: Class 'Test' has no instance getter 'validator'.
  }
 }

class TestClass {
  final Test param;
  TestClass(this.param)
  body(){
   print(param.validator)  // => Works.
 }

But according to Dart extensions static types it should work in both cases?
Perhaps any workarounds exists for the first scenario?

This is working as intended.
Extension methods are dispatched based on the static type of the expression they're called on, not the dynamic type.
In this case, the static type of param is dynamic, not Test. The link specifically states that:

You can’t invoke extension methods on variables of type dynamic.
(it's assumed to have all methods itself, and instance methods take precedence over extension methods.)

In the first scenario, you can explicitly cast the value to Test, so that the extension applies, or let it happen implicitly by using param in a context expecting a Test (like the TestT extension override syntax):
print((param as Test).validator);
print(TestT(param).validator);


Fix nested prefetches in qdrant_local.py

Having multiple nested prefetches does not seem to work with qdrant in local mode. The last prefetch in the chain is none which then raises an exception in the _resolve_prefetch_input method:
if prefetch.query
raises an exception since prefetch is none)
All Submissions:

[x] Contributions should target the dev branch. Did you create your branch from dev?
[ ] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

[ ] Does your submission pass tests?
[ ] Have you installed pre-commit with pip3 install pre-commit and set up hooks with pre-commit install?

Changes to Core Features:

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your core changes, as applicable?
[ ] Have you successfully ran tests with your changes locally?

@hh-space-invader thanks for taking over! Will you bring this to the finish line or do you expect some more work from me :) ?

hi @paul2302
thank you for your contribution, we'll finish it and merge soon, thank you

@joein thank you for taking over so quickly. Is there a timeline for when this might be part of the next release?

Hey, I expect it to be released not later than 2 days

@joein so quickly? Wow, thanks! Keep up the great work :D


enum model is not getting generated

Hi, Jersey service is taking enum as query param.Swgger is not generating model for the same ,it just referring qualified class name of enum.

it would help mentioning the version of Jersey that you use as well as the version of swagger-core.

I am using jersey-server-1.8.jar,jersey-core-1.8.jar and swagger-core_2.9.1-1.3.0.jar

Well, that release is a year and a half old. I'd start by upgrading to the latest using either 1.3.12 or 1.5.3-M1.

Okay Ron thanks a lot for quick response...I will update the jars..and validate.

If I add this dependency will it work?

com.wordnik
swagger-jaxrs_2.10
1.3.12

That's what you should try, yes.


Migrate configuration to @wuespace/envar

Since we now released https://jsr.io/@wuespace/envar, we should migrate the generator to also use it for its configuration.

Testing autolinks: WBD56001


Installs python version for UsePythonVersion (#17)

Closes #17

There has been no definitive information obtained regarding its necessity.
https://github.com/btungut/azure-devops-agent-on-kubernetes/issues/17


Disable Apex/Marksmen Weapons/Stuffs

Hey,
Many of my friends aint got the DLCS, so they cant use any default unlocked  weapons apart form one arsenal weapon,
Also they cant use the 4wd Offroader
and like 50% of the loot is marksmen/apex loot :(
we added the FFAA mod so there is some variety, but i would like to disable all of them

Last known situation is that Antistasi will be polished for 0 DLC required.

changed those loadouts on next patch. Not 100% vanilla but workable. Thanks!


xAxis type "time" label increments instead of scrolling

Version
5.1.0
Reproduction link
https://6098b3a39d5adf00075481da--jolly-pike-04f0ab.netlify.app/
Steps to reproduce
scroll along the xAxis
What is expected?
For the labels on the xAxis to scroll along with the line chart.
What is actually happening?
The labels are fixed in position.  They just increment according to the value.

Could this example help you?


WIP Enable rollout monitor for single node openshift

Not intended for merge, just posting wip stuff in aid of the eventual enhancement.
/cc @sttts @p0lyn0mial

/reopen

Superceded by #1157


UpdateLiveRegionEvent is not implemented on Android engine side

Split from https://github.com/flutter/flutter/issues/45930
UpdateLiveRegionEvent is not implemented on the Android bridge side.  We also probably want a framework helper method in SemanticsService for it if it's actually useful.

I'm actually inclined to remove this from the framework. It seems doubtful to me that it would ever be useful.
@darrenaustin, @goderbauer or @jonahwilliams WDYT?

Jonah suggested offline deprecating it to make it a softer transition.


Add common message bus code and kiiss example...

...service
Common message bus api to be shared between services and mayastor
Common service api for the services
Kiiss service as an example to show case the service api.
I've split this in 3 commits, which should make reviewing easier.
I also added a few cargo examples which might be useful.

bors try

bors try

bors r+


allergies: Add test case to check when not allergic to anything

Add test case for also checking isAllergicTo() when not allergic to anything.

Thank you!  Yup, this is a fine way to kick off this exercise.
Cheers!