IndexError: tuple index out of range

when I run the script ' ./exp/mask_rcnn_1x_hybrid_small/run.sh' of uniformer, I get a bug as follows:
Traceback (most recent call last):
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/torch/distributed/launch.py", line 193, in
main()
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/torch/distributed/launch.py", line 189, in main
launch(args)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/torch/distributed/launch.py", line 174, in launch
run(args)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/torch/distributed/run.py", line 713, in run
)(*cmd_args)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/torch/distributed/launcher/api.py", line 131, in call
return launch_agent(self._config, self._entrypoint, list(args))
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/torch/distributed/launcher/api.py", line 261, in launch_agent
                                                                                [56/1124]

File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
if cached_x.grad_fn.next_functions[1][0].variable is not x:
IndexError: tuple index out of range
return forward_call(*input, **kwargs)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/mmcv/runner/fp16_utils.py", line 128, in new_func
output = old_func(*new_args, **new_kwargs)
File "/mnt/ghome/jiaojiayu/uniformer/object_detection/mmdet/models/detectors/base.py", line 181, in forward
return self.forward_train(img, img_metas, **kwargs)
File "/mnt/ghome/jiaojiayu/uniformer/object_detection/mmdet/models/detectors/two_stage.py", line 156, in forward_train
proposal_cfg=proposal_cfg)
File "/mnt/ghome/jiaojiayu/uniformer/object_detection/mmdet/models/dense_heads/base_dense_head.py", line 49, in forward_train
outs = self(x)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
return forward_call(*input, **kwargs)
File "/mnt/ghome/jiaojiayu/uniformer/object_detection/mmdet/models/dense_heads/anchor_head.py", line 143, in forward
return multi_apply(self.forward_single, feats)
File "/mnt/ghome/jiaojiayu/uniformer/object_detection/mmdet/core/utils/misc.py", line 29, in multi_apply
return tuple(map(list, zip(*map_results)))
File "/mnt/ghome/jiaojiayu/uniformer/object_detection/mmdet/models/dense_heads/rpn_head.py", line 43, in forward_single
x = self.rpn_conv(x)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
return forward_call(*input, **kwargs)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/torch/nn/modules/conv.py", line 446, in forward
return self._conv_forward(input, self.weight, self.bias)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/torch/nn/modules/conv.py", line 443, in _conv_forward
self.padding, self.dilation, self.groups)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/apex/amp/wrap.py", line 21, in wrapper
args[i] = utils.cached_cast(cast_fn, args[i], handle.cache)
File "/mnt/ghome/jiaojiayu/anaconda3/envs/open-mmlab-2/lib/python3.7/site-packages/apex/amp/utils.py", line 97, in cached_cast
if cached_x.grad_fn.next_functions[1][0].variable is not x:
IndexError: tuple index out of range
I use the uniformer as the backbone and I don't change the code. Please help me!

It seems that your apex meets some problems. Please see here to solve this problem.

Or you can follow this PR to fix it.

As there is no more activity, I am closing the issue, don't hesitate to reopen it if necessary.


Missing item: Shriveled Heart

Please include:

Shriveled Heart
https://www.wowhead.com/wotlk/item=50309/shriveled-heart
Phase 4 - Halls of Reflection

122172a


Add grunt build info in README

add information on grunt install and project build.

Hey @brandonJY ,
thanks for the PR. We planned to get rid of Grunt so I don't think we need this.
Cheers

Glad to hear that. looking forward to.


How can I continue training from previously saved parameters?

can you explain the continuation of training with mnist example?

closing the issue as I found the solution while looking code of run method under the trainer. thanks any way for evojax 👍


[Bug] Qwen2-VL-7B with sglang Performance Degradation

Checklist

[X] 1. I have searched related issues but cannot get the expected help.
[X] 2. The bug has not been fixed in the latest version.
[X] 3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.
[X] 4. If the issue you raised is not a bug but a question, please raise a discussion at https://github.com/sgl-project/sglang/discussions/new/choose Otherwise, it will be closed.
[X] 5. Please use English, otherwise it will be closed.

Describe the bug
Qwen2-VL-7B cannot reproduce its performance in MME using sglang, while pure transformers can.
Reproduction
Both decode with  temperature==0, I suspect it's possibly with the input image.
 It may be more helpful. Thanks
Hi, thank you for your reply in time.

vllm test results
=========== Cognition ===========
total score:<PHONE_NUMBER>4285717
         commonsense_reasoning  score:<PHONE_NUMBER>4285717
         numerical_calculation  score: 80.0
         text_translation  score: 162.5
         code_reasoning  score: 95.0

And I used the official Qwen2-VL-7B API from Aliyun, got a total score of around 470.
It is an unusual yet significant issue for qwen-vl users.

Hello, can you give a vllm test result? It may be more helpful. Thanks

Hi, thank you for your reply in time.
vllm test results
=========== Cognition ===========
total score:<PHONE_NUMBER>4285717
         commonsense_reasoning  score:<PHONE_NUMBER>4285717
         numerical_calculation  score: 80.0
         text_translation  score: 162.5
         code_reasoning  score: 95.0

And I used the official Qwen2-VL-7B API from Aliyun, got a total score of around 470. It is an unusual yet significant issue for qwen-vl users.

Sorry for the bad performance.
Qwen2-VL in sglang is mainly adapted from vllm, and there are some issues for vllm qwen2vl about accuracy(for example here ). Since vllm score is close to sglang, I think the main problem may be vllm implementation.
I will follow vllm community and try to modify qwen2vl based from transformers.

Oh, this is terrible...! Have you reported to vLM ? @Mr-Loevan

Hmm, I am able to reproduce an issue where I see different logprobs between a hugging face implementation and calling sglang vs vllm:
sglang run 1 v0.3.6
Top 5 tokens and their log probabilities:
HF Token: Ġ( Log Prob: -0.58 Prob 56.04%  SGLANG Token , Logprob -0.64 Prob 52.98%
HF Token: , Log Prob: -0.83 Prob 43.64%  SGLANG Token  ( Logprob -0.76 Prob 46.75%
HF Token: Ġin Log Prob: -7.20 Prob 0.07%  SGLANG Token  was Logprob -6.76 Prob 0.12%
HF Token: Ġwas Log Prob: -7.33 Prob 0.07%  SGLANG Token  in Logprob -7.64 Prob 0.05%
HF Token: Ġor Log Prob: -7.95 Prob 0.04%  SGLANG Token  or Logprob -8.64 Prob 0.02%

vllm run1 '0.6.4.post1'
Top 5 tokens and their log probabilities:
HF Token: Ġ( Log Prob: -0.58 Prob 56.04%  SGLANG Token  ( Logprob -0.35 Prob 70.41%
HF Token: , Log Prob: -0.83 Prob 43.64%  SGLANG Token , Logprob -1.23 Prob 29.35%
HF Token: Ġin Log Prob: -7.20 Prob 0.07%  SGLANG Token  ([ Logprob -7.73 Prob 0.04%
HF Token: Ġwas Log Prob: -7.33 Prob 0.07%  SGLANG Token  in Logprob -7.85 Prob 0.04%
HF Token: Ġor Log Prob: -7.95 Prob 0.04%  SGLANG Token  or Logprob -7.98 Prob 0.03%

What I see is a discrepancy in both vllm and sglang, but sglang, at least when decoding with temperature 0 does yield the same answer after 100 tokens, but by then sglang has already gone down a different path.

I've checked, alignment is much better if you don't include an image in the query:
Top 5 tokens and their log probabilities:
HF Token: Ġc Log Prob: -0.53 Prob 59.07%  SGLANG Token  c Logprob -0.53 Prob 59.09%
HF Token: Ġ[ Log Prob: -1.03 Prob 35.83%  SGLANG Token  [ Logprob -1.03 Prob 35.84%
HF Token: Ġ\ Log Prob: -4.03 Prob 1.78%  SGLANG Token  \ Logprob -4.03 Prob 1.78%
HF Token: Ġ\\ Log Prob: -4.40 Prob 1.23%  SGLANG Token  \\ Logprob -4.40 Prob 1.23%
HF Token: [ Log Prob: -5.21 Prob 0.54%  SGLANG Token [ Logprob -5.21 Prob 0.54%

I have found some discrepancies in the calculation of the logits in the vision head, I'll try to post a PR to fix this shortly.

@Mr-Loevan How did you run your test where you saw the lower performance vs transformers. Can you share instructions so I can attempt to reproduce?

Is the difference in effect possibly due to the difference in sampling parameters or the difference in image preprocessing methods? @jakep-allenai @Mr-Loevan

No, image preprepocessor gives the same results for me. I got the whole vision encoder to match up perfectly now, hope to wrap it into a PR shortly.

Hello, can you give a vllm test result? It may be more helpful. Thanks

Hi, thank you for your reply in time.
vllm test results
=========== Cognition ===========
total score:<PHONE_NUMBER>4285717
         commonsense_reasoning  score:<PHONE_NUMBER>4285717
         numerical_calculation  score: 80.0
         text_translation  score: 162.5
         code_reasoning  score: 95.0

And I used the official Qwen2-VL-7B API from Aliyun, got a total score of around 470. It is an unusual yet significant issue for qwen-vl users.

@Mr-Loevan  Did you see similar performance degradation on Qwen2-VL-2B or Qwen2-VL-72B?

what if change the version of vllm? I saw some of the vllm issues solved by upgrading vllm from 0.6.3.post1 to 0.6.4.post1

what if change the version of vllm? I saw some of the vllm issues solved by upgrading vllm from 0.6.3.post1 to 0.6.4.post1

I changed the vllm version to 0.6.4.post1，mme bench score is OK.

This is 0.6.3.post1

And this is 0.6.4.post1


Output the log synchronously

Hi,
Could I output the log synchronously?
Thanks

Hi,
I have understood your design.
I can get the log synchronously like this:
ps.on('output',function (data) {
console.log(data);
})
Thank you.

Hey @njulhb,
Will appreciate your star very much. thx 👍


Having trouble recognizing routes from consul

I've reviewed the wiki and cannot find a solution to a problem where fabio is not picking up routes from consul (in my particular installation on AWS).
I launch fabio from nomad (as a system task) along with another nomad job (a docker task) that registers with consul using the "registrator" service (another docker instance).  I've arranged for the "urlprefix-/uuid" tag on the service I wish to be handled by fabio.  When I visit the fabio ui, none of the routes (there should be 2) show up.
Here's a shot of the text shown on the consul ui:

If it'll help, here's the specifics of the registration for the service as reported by consul:
{   "Node": "klp-coreos-1",   "Address": "<IP_ADDRESS>",   "ServiceID": "klp-coreos-1:wso2as-1c89fa47-5418-6668-b884-bf00023ed226:9763",   "ServiceName": "wso2as-http",   "ServiceTags": [     "urlprefix-/uuid"   ],   "ServiceAddress": "<IP_ADDRESS>",   "ServicePort": 20864,   "ServiceEnableTagOverride": false,   "CreateIndex": 4006,   "ModifyIndex": 4830 }
Might someone have an idea on why I don't see any routes in the fabio ui?  I've also attempted to use curl to access the endpoint and always get back a 404.
Thanks!

I know, bad form replying to my own issue ...
I'm suspecting that the problem is due to my not having a health check for the service ... I'll add that and see if that's it.

The usual problem for this is the missing health check.

Doh!  Things are working now as expected.  Thanks @magiconair.  Onward in my fabio training ...

:) no worries


Maintenance release testing for _all.html

Main issue is https://github.com/phetsims/chipper/issues/563 (for Chipper 2.0)
For the actual maintenance release, can I first get quick checks to make sure the following sims were not broken (RCs for the maintenance release, ~10-30 seconds of testing each)

[ ] https://www.colorado.edu/physics/phet/dev/html/acid-base-solutions/1.2.11-rc.1/acid-base-solutions_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/area-builder/1.1.6-rc.1/area-builder_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/arithmetic/1.0.10-rc.1/arithmetic_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/atomic-interactions/1.0.4-rc.1/atomic-interactions_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/balancing-act/1.1.10-rc.1/balancing-act_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/balancing-chemical-equations/1.1.10-rc.1/balancing-chemical-equations_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/beers-law-lab/1.4.4-rc.1/beers-law-lab_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/bending-light/1.1.7-rc.1/bending-light_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/charges-and-fields/1.0.4-rc.1/charges-and-fields_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/color-vision/1.1.10-rc.1/color-vision_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/concentration/1.3.6-rc.1/concentration_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/energy-skate-park-basics/1.1.6-rc.1/energy-skate-park-basics_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/faradays-law/1.1.10-rc.1/faradays-law_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/forces-and-motion-basics/2.1.5-rc.1/forces-and-motion-basics_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/fraction-matcher/1.1.8-rc.1/fraction-matcher_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/friction/1.3.4-rc.1/friction_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/function-builder/1.0.9-rc.1/function-builder_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/hookes-law/1.0.10-rc.1/hookes-law_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/isotopes-and-atomic-mass/1.0.9-rc.1/isotopes-and-atomic-mass_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/least-squares-regression/1.1.7-rc.1/least-squares-regression_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/molecule-shapes/1.1.11-rc.1/molecule-shapes_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/molecule-shapes-basics/1.1.9-rc.1/molecule-shapes-basics_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/molecules-and-light/1.1.16-rc.1/molecules-and-light_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/neuron/1.1.4-rc.1/neuron_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/ohms-law/1.3.8-rc.1/ohms-law_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/ph-scale/1.2.11-rc.1/ph-scale_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/ph-scale-basics/1.2.11-rc.1/ph-scale-basics_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/reactants-products-and-leftovers/1.1.10-rc.1/reactants-products-and-leftovers_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/resistance-in-a-wire/1.2.9-rc.1/resistance-in-a-wire_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/rutherford-scattering/1.0.7-rc.1/rutherford-scattering_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/trig-tour/1.0.9-rc.1/trig-tour_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/under-pressure/1.1.5-rc.1/under-pressure_en.html
[ ] https://www.colorado.edu/physics/phet/dev/html/wave-on-a-string/1.1.9-rc.1/wave-on-a-string_en.html

Additionally, can all of the files at https://www.colorado.edu/physics/phet/dev/olsonjb/all-versions/ be checked?
It includes _en.html and _all.html files for all live production sims. I would load each file up and check phet.chipper.strings in the console. For _en.html files, it should have basically only the "en" locale (ignore the get function), and for _all.html files it should have all locales included.
Additionally, can you spot-check all of the _all.html files for multiple locales, using query parameters like ?locale=en, ?locale=fr and such to ensure that at least English and 1-2 other locales run for each _all.html?

Ack, one second. Looks like build-server failed for least-squares-regression, molecule-shapes and molecule-shapes-basics (looks like a chronological failure). @mattpen can you look into that? I'll re-send deployments.

molecules-and-light also failed build-server, but didn't send a failure email (probably due to its chipper SHA)

Ok, the 4 RCs that failed above have been successfully re-deployed. Should be ready again for testing.

@phet-steele #70 needs to come first, but it would be good to mix in some of this spot checking early to see if there are any major issues

@jonathanolson Resistance in a Wire was recently published, new branch. The changes in this issue should be done on that new branch.

I'll double-check RIAW, but it should be new enough that it would include the feature.

@jonathanolson this was a dooozy! Spot checking ?locale= never failed when doing en and two other random locales. Spending 30 seconds on each RC revealed no new issues.

Thanks! Maintenance releases finished (deployed to production)


Connection error

Hi I've tried to setup my data source the way you have it in your example application, unfortunately, I've not been able to connect to my couchbase instance at all, and get the error below:
{
  "error": {
    "name": "TypeError",
    "status": 500,
    "message": "Cannot read property 'connect' of undefined",
    "stack": "TypeError: Cannot read property 'connect' of undefined\n    at DataSource.dataSource.connect (/Users/muneeb/dev/api/node_modules/loopback-datasource-juggler/lib/datasource.js:339:29)\n    at DataSource.ready (/Users/muneeb/dev/api/node_modules/loopback-datasource-juggler/lib/datasource.js:2001:10)\n    at stillConnecting (/Users/muneeb/dev/api/node_modules/loopback-datasource-juggler/lib/dao.js:306:23)\n    at Function.DataAccessObject.create (/Users/muneeb/dev/api/node_modules/loopback-datasource-juggler/lib/dao.js:151:27)\n    at Object.eval [as forward] (eval at recompile (/usr/local/lib/node_modules/strongloop/node_modules/strong-agent/lib/proxy.js:237:15), <anonymous>:4:32)\n    at Function.eval (eval at wrap (/usr/local/lib/node_modules/strongloop/node_modules/strong-agent/lib/proxy.js:193:20), <anonymous>:3:21)\n    at SharedMethod.invoke (/Users/muneeb/dev/api/node_modules/loopback/node_modules/strong-remoting/lib/shared-method.js:198:25)\n    at HttpContext.invoke (/Users/muneeb/dev/api/node_modules/loopback/node_modules/strong-remoting/lib/http-context.js:335:12)\n    at /Users/muneeb/dev/api/node_modules/loopback/node_modules/strong-remoting/lib/remote-objects.js:595:9\n    at execStack (/Users/muneeb/dev/api/node_modules/loopback/node_modules/strong-remoting/lib/remote-objects.js:448:7)"
  }
}

This is my configuration file:
"couchbase": {
    "host": "<IP_ADDRESS>",
    "port": 8091,
    "database": "default",
    "name": "couchbase",
    "n1qlport": 8093,
    "connector": "couchbase",
    "connectionTimeout": 20000,
    "operationTimeout": 15000
  }

I can confirm this- I am currently using the preview of Couchbase Server 4.

Hi guys,
We are looking into getting this working with the latest version, but don't
have a timeframe for release due to higher priorities.  PR requests are
welcome!
Thanks.
On Mon, May 25, 2015 at 10:17 AM, Sebastian Haas<EMAIL_ADDRESS>wrote:

I can confirm this- I am currently using the preview of Couchbase Server 4.
—
Reply to this email directly or view it on GitHub
https://github.com/guardly/loopback-connector-couchbase/issues/13#issuecomment-105241756
.

--
Nolan DubeauVP, Engineering, Guardly Corp.
Online: https://www.guardly.com
LinkedIn: http://www.linkedin.com/in/nolandubeau
20 Maud Street, Suite 307, Toronto, ON M5V 2M5
CA<PHONE_NUMBER>  |  US<PHONE_NUMBER>  |  Skype: nolandubeau
Please consider the environment before printing this email.

Thank you very much for your quick response!

Hi,
I face same issue
{
"error": {
"name": "TypeError",
"status": 500,
"message": "Cannot read property 'connect' of undefined",
"stack": "TypeError: Cannot read property 'connect' of undefined\n    at DataSource.dataSource.connect (/Volumes/DATA/stash/cms/node_modules/loopback-datasource-juggler/lib/datasource.js:349:29)\n    at DataSource.ready (/Volumes/DATA/stash/cms/node_modules/loopback-datasource-juggler/lib/datasource.js:2121:10)\n    at stillConnecting (/Volumes/DATA/stash/cms/node_modules/loopback-datasource-juggler/lib/dao.js:357:23)\n    at Function.find (/Volumes/DATA/stash/cms/node_modules/loopback-datasource-juggler/lib/dao.js:1315:27)\n    at SharedMethod.invoke (/Volumes/DATA/stash/cms/node_modules/loopback/node_modules/strong-remoting/lib/shared-method.js:248:25)\n    at HttpContext.invoke (/Volumes/DATA/stash/cms/node_modules/loopback/node_modules/strong-remoting/lib/http-context.js:384:12)\n    at /Volumes/DATA/stash/cms/node_modules/loopback/node_modules/strong-remoting/lib/remote-objects.js:620:11\n    at execStack (/Volumes/DATA/stash/cms/node_modules/loopback/node_modules/strong-remoting/lib/remote-objects.js:460:7)\n    at RemoteObjects.execHooks (/Volumes/DATA/stash/cms/node_modules/loopback/node_modules/strong-remoting/lib/remote-objects.js:464:10)\n    at /Volumes/DATA/stash/cms/node_modules/loopback/node_modules/strong-remoting/lib/remote-objects.js:617:10"
}
}

@hoangton Could you work around this?

I am facing the same issue.Is there any progress on this?

Is there any solution for this?

getting this too.... so the question is whether this is a versioning issue with couchbase or something specific I am doing that causes this.   Anyone have a workaround?

I found that the connector couldn't be initialized unless you installed couchbase in the loopback-connector-couchbase itself.  That solved this problem for me and I've had no other issues.

So does anyone know the source of what's exactly causing this error?

@exmurr: What if we need to connect to remote couchbase? For me change the configuration directly in the datasources.json and it works fine.

same problem for me

with the version loopback-connector-couchbase version 1.0.0 I solve the problem


Determine whether to use "includePolyfill" or "browserPolyfill"

Once Ember CLI 1.13.13 is installed (depends on https://github.com/softlayer/sl-ember-components/issues/1503).  See https://github.com/babel/ember-cli-babel/issues/61 for reference.  Had to switch to using browserPolyfill in the upgrade to Ember CLI 1.13.10.

Resolved by https://github.com/softlayer/sl-ember-components/issues/1503


typo: "waiting for response from singer"

Was this done on purpose?
Note:

fix typo: "waiting for response from singer" => "signer" not "singer"

I will check it.

i will take it

I will take this


Update swearwords.go

What is this supposed to do? You just disabled all the built-in swear words and added the word cracker??
If this is a Hacktoberfest spam PR, please note that this PR will not count as a contribution. Repositories have to either opt-in or add the label manually.

Lmao


ban.js

Just as a little help :D
Please describe, what changed in this Pullrequest:
What does this Pull Request do:

[ ] This pull request makes changes to the index.js file.
[ ] This pull request makes internal changes to the command handler (index.js)
[ ] This pull request modifies commands
[ ] This pull request changes command functions
[ ] This pull rquest removes and/or adds commands
[ ] This pull rquest doesn't change the code and only includes non-code changes like changes to default configurations, the README & Template Files, correcting Typing mistakes etc.

I'm going to accept the pull request, but we're going to have to recode some things to make it integrate with our language system. Next time please try to integrate it better by looking at the code of some other commands.


Converting from boolean to int does not work when I use the setBoolean method

Converting from boolean to int does not work when I use the setBoolean method
This is my code:
mytodo.setBoolean("IsFinished", !mytodo.getBoolean("IsFinished")).saveIt();
Error:
Caused by: org.javalite.activejdbc.DBException: org.postgresql.util.PSQLException: ERROR: the "isfinished" column is of type smallint, and the expression is boolean
   Tip: Rewrite an expression or convert its type.
Question:
If setBoolean can not convert to Int, then what it is converted?
P.S. getBoolean works great!

Please, see http://javalite.github.io/activejdbc/snapshot/org/javalite/activejdbc/Model.html#setBoolean-java.lang.String-java.lang.Object-
and http://javalite.io/data_conversions
The setBoolean converts something to Boolean.  Apparently your driver does not know how to deal with it. ActiveJDBC is a pass-through framerork: http://javalite.io/pass_through_framework.
You can:

Write a setter:

public class MyModel extends Model{
public MyModel setFinished(boolean finished){
return setInteger("IsFinished", finished ? 1 : 0);
}
}

Write a custom converter, here is an example:
https://github.com/javalite/activejdbc/blob/5763fb0ad4ee21cfa26596e5b64c452777baac19/activejdbc/src/test/java/org/javalite/activejdbc/test_models/Page.java#L13


Empty samples breaksto_SignalSum

Passing an empty DiscreteSignal into to_SignalSum causes an array with dimensions (1,0) to be transpoed to (0,1), which breaks the DiscreteSignal init function. The transposition should not be applied in the empty sample case.
Current behavior (raises error):
from qiskit_dynamics import DiscreteSignal
from qiskit_dynamics.signals.signals import to_SignalSum

to_SignalSum(DiscreteSignal(samples=[], dt=1.))

To fix, add an if statement to to_SignalSum which only transposes the input samples if their size is not (1,0)

It seems like transpose should get a single tuple, instead of multiple integers. So the calls in the source seem incorrect themselves.
See for example:
Array([[0.3]]).transpose(1, 0)

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-15-dcef55651520> in <module>
----> 1 Array([[0.3]]).transpose(1, 0)

~/qiskit-dynamics/qiskit_dynamics/array/array.py in wrapped_method(*args, **kwargs)
    176             @wraps(attr)
    177             def wrapped_method(*args, **kwargs):
--> 178                 return self._wrap(attr(*args, **kwargs))
    179
    180             return wrapped_method

TypeError: transpose() takes from 1 to 2 positional arguments but 3 were given

Note that this breaks the Gradient optimization of a pulse sequence tutorial.


[Language Text] Parse the errors JSON pointers in the LRO response objects

The errors property in the response contain target links that reference tasks associated with the specific error. These pointers are JSON pointers that the SDK should parse and then add those errors as items in the result array in the indices that correspond to the ones in the input tasks array.

Addressed


[SPARK-41673][CONNECT][PYTHON] Implement Column.astype

What changes were proposed in this pull request?
Implement Column.astype
Why are the changes needed?
api coverage
Does this PR introduce any user-facing change?
yes
How was this patch tested?
just add one test case, since it is an alias

merged into master


replace fr.pinsterest.com by pinterest.com

better for users from other countries

Great project, by the way. I was looking forward to create some RTS as a hobby and just saw this on Hacker News. I'll definitely keep an eye on OpenRTS :smile:

thanks :)


Migrate repo to use connectrpc paths

This migrates the repo and all examples to use the new connectrpc paths instead of bufbuild and demo.connect.build

@paul-sachs, can you wrap up https://github.com/bufbuild/connect-es-integration/pull/687 so that we don't have to update once?


Improve test coverage

This is a general issue that our unit tests should be more comprehensive. I've noticed that sometimes unit tests don't actually test correct behavior (this was the issue with some tests in touch.js that I fixed. I'm sure there are also many options/edge cases for functions that are not tested very comprehensively.
As we work toward future releases, we should also work on improving our test framework, to prevent regressions. Also, we should probably add more sanity checks in the run-tests.js script, since because this uses ShellJS to test ShellJS, a major break (for example: if ls() returns the empty array every time) can cause the test runner to give a false positive.
I'm putting the "help wanted" label on here, so if anyone is looking for something to contribute on, more test cases would be welcome.
If you'd like to contribute, please try to isolate your changes to one file per PR (it makes it much easier to review). Also, it helps if you tag this issue number in your PR. We're also interested in refactoring test cases (so as long as you know JS, you'd be able to help) :+1:

Are you opposed to adding mocha?

@blockloop: This is something I've been thinking about for a while. I think it might be a good idea to refactor our tests to use mocha.
@nfischer: Thoughts?

I'll pitch in and help. I initially wrote the 'touch' tests with it and took them out. I'll gladly redo it.

@ariporad what would be the benefits of mocha tests over using simple assert statements? How difficult would the refactor be?

It would take some work, but not to hard. The benefit of mocha is that other
tools know how to work with it. (Ie. Code coverage)
Let me look into this, I'll get back to you in a day or two.

Ok sounds good

@nfischer, @blockloop: Actually, I think I'm going to go with AVA. It will make the tests faster, and make them easier to convert.


PENDING UPDATE: Added line and crosshair documentation

Thanks chris - just realised sublime isn't spell checking markdown files.


Android Basics: classes-and-inheritance

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-classes-and-inheritance?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-2-pathway-1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-classes-and-inheritance#4
In which task and step of the codelab can this issue be found?
Modify classes in the hierarchy - Implement floorArea() for RoundHut
Describe the problem
At step 3 of Implement floorArea() for RoundHut step, the code is:
open class RoundHut(
   val residents: Int,
   val radius: Double) : Dwelling(residents) {
   /* code */
}

What I think is wrong is that residents is being declared again. Residents is from Dwelling abstract class, the root class. Testing the code without declaring residents, like this, works the same way
open class RoundHut(
   residents: Int,
   val radius: Double) : Dwelling(residents) {
   /* code */
}

Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version:
API version of the emulator:
Additional information
Include screenshots if they would be useful in clarifying the problem.

@mtbossa
Thank you so much for reporting this issue. This is fixed and will be published.


Set the class of a swizzled object back to its original class upon deallocation.

This just avoids disposing the swizzler's generated classes when zombies is enabled.

[x] detailed explanation of what we do and why in the comments
[ ] tests?
[ ] document possible edge cases when it may not work as expected...

Fix #8321

Rebased after Update tool path in test_coverage #53 merged

Merging and staging to integration test in nightlies


Adds SageMaker Ground Truth Lambda events

Description of changes:
Adds events for Lambda functions for SageMaker Ground Truth for these Lambda functions in the CreateLabelingJob operation:

PreHumanTask
AnnotationConsolidation

Checklist:

[n/a] Write Design Document (Do I need to write a design document?)
[n/a] Write unit tests
[n/a] Write/update functional tests
[n/a] Write/update integration tests
[x] make pr passes
[n/a] Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I fixed the names in the generated event to match what what someone using the API would be passing.


Support for symmetric key objects in export/import

cc @SQLSourabh
Is your feature request related to a problem? Please describe.
Symmetric key objects are not supported for export (I/E will fail)

Symmetric key objects are supported in DacFx 160. Closing since there's not enough info.


Feature/smhe 717 couple when not in use

Coupling a Mbus Device by channel is only allowed when the Mbus Device is not in use.

Changed implementation of CoupleMBusDevice; coupling is not performed when device is IN_USE.


Removing unused dependencies, adding Psalm, fixing Psalm issues

What was changed

Removed unused dependencies
Added Psalm with GitHub action
Fixed Psalm issues

 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.


Seemingly random "Upload Error Failure"

I've just recently started getting "Upload Error Failure" notifications when trying to upload files via Remote FTP. The issue doesn't occur every time, and I've been unable to find steps to reproduce it consistently. It occurs both with right-click > Upload and right-click > Sync local -> remote.
Console logged the following error once, but other times the console has been quiet:
Error: Failure(...)
(anonymous function) @ commands.js:422
Immediately after experiencing these errors, I switched to FileZilla to do my uploading tasks and it worked without any problems, which leads me to believe the issue is specific to Remote FTP.

I believe you are experiencing the same thing I am. If the file you are working on is inside a collapsed folder on your local tree, the file will fail to upload.
Steps to reproduce:

Collapse your local project folder
Double click file on server to download and open
Try to upload it. Upload failed.

**Slight change in v1.2 release, error message now reads "no such file" instead of generic upload failed message. And after failed upload the uploader gets stuck and will not allow you to download or upload anything until you restart Atom or disconnect/reconnect.
Workaround: Make sure ALL of your local folders are expanded and make sure that the file you are trying to upload is highlighted in your local view

I believe @Dopey117 is right, however, it's fairly impossible to have all of my bower_components expanded, especially if a new one is added from a build if I'm building locally. Additionally, once it fails once, I believe I have to reopen my Atom project otherwise I can't build anything indicated by the following error from Polymer.
error:   cli runtime exception: Error: EPERM: operation not permitted, unlink 'D:\[The file that was supposed to be uploaded via FTP]'
error:   Error: EPERM: operation not permitted, unlink 'D:\[The file that was supposed to be uploaded via FTP]'

I know I said ALL your folders, but really as long as you make sure to expand the ones you are actively working in you will be fine.  As long as the file you want to upload is highlighted in your local view it will upload

Resolve, if there is a problem then I will reopen.


RuntimeError:          CUDA Setup failed despite GPU being available. Please run the following command to get more information:          python -m bitsandbytes

CUDA_SETUP: WARNING! libcudart.so not found in any environmental path. Searching in backup paths...
CUDA SETUP: WARNING! libcuda.so not found! Do you have a CUDA driver installed?
CUDA SETUP: Loading binary D:\Anaconda\envs\summer2023\lib\site-packages\bitsandbytes\libbitsandbytes_cpu.so...
argument of type 'WindowsPath' is not iterable
CUDA SETUP: Problem: The main issue seems to be that the main CUDA library was not detected.
CUDA SETUP: Solution 1): Your paths are probably not up-to-date. You can update them via: sudo ldconfig.
CUDA SETUP: Solution 2): If you do not have sudo rights, you can do the following:
CUDA SETUP: Solution 2a): Find the cuda library via: find / -name libcuda.so 2>/dev/null
CUDA SETUP: Solution 2b): Once the library is found add it to the LD_LIBRARY_PATH: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:FOUND_PATH_FROM_2a
CUDA SETUP: Solution 2c): For a permanent solution add the export from 2b into your .bashrc file, located at ~/.bashrc
RuntimeError                              Traceback (most recent call last)
Cell In[2], line 6
4 model_id="/llama/models_hf/7B"
5 tokenizer = LlamaTokenizer.from_pretrained(model_id)
----> 6 model =LlamaForCausalLM.from_pretrained(model_id, load_in_8bit=True, device_map='auto', torch_dtype=torch.float16)
File D:\Anaconda\envs\summer2023\lib\site-packages\transformers\modeling_utils.py:2710, in PreTrainedModel.from_pretrained(cls, pretrained_model_name_or_path, config, cache_dir, ignore_mismatched_sizes, force_download, local_files_only, token, revision, use_safetensors, *model_args, **kwargs)
2707     keep_in_fp32_modules = []
2709 if load_in_8bit or load_in_4bit:
-> 2710     from .utils.bitsandbytes import get_keys_to_not_convert, replace_with_bnb_linear
2712     llm_int8_skip_modules = quantization_config.llm_int8_skip_modules
2713     load_in_8bit_fp32_cpu_offload = quantization_config.llm_int8_enable_fp32_cpu_offload
File D:\Anaconda\envs\summer2023\lib\site-packages\transformers\utils\bitsandbytes.py:12
8 from .import_utils import is_accelerate_available, is_bitsandbytes_available
11 if is_bitsandbytes_available():
---> 12     import bitsandbytes as bnb
13     import torch
14     import torch.nn as nn
File D:\Anaconda\envs\summer2023\lib\site-packages\bitsandbytes_init_.py:6
1 # Copyright (c) Facebook, Inc. and its affiliates.
2 #
3 # This source code is licensed under the MIT license found in the
4 # LICENSE file in the root directory of this source tree.
----> 6 from . import cuda_setup, utils, research
7 from .autograd._functions import (
8     MatmulLtState,
9     bmm_cublas,
(...)
13     matmul_4bit
14 )
15 from .cextension import COMPILED_WITH_CUDA
File D:\Anaconda\envs\summer2023\lib\site-packages\bitsandbytes\research_init_.py:1
----> 1 from . import nn
2 from .autograd._functions import (
3     switchback_bnb,
4     matmul_fp8_global,
5     matmul_fp8_mixed,
6 )
File D:\Anaconda\envs\summer2023\lib\site-packages\bitsandbytes\research\nn_init_.py:1
----> 1 from .modules import LinearFP8Mixed, LinearFP8Global
File D:\Anaconda\envs\summer2023\lib\site-packages\bitsandbytes\research\nn\modules.py:8
5 from torch import Tensor, device, dtype, nn
7 import bitsandbytes as bnb
----> 8 from bitsandbytes.optim import GlobalOptimManager
9 from bitsandbytes.utils import OutlierTracer, find_outlier_dims
11 T = TypeVar("T", bound="torch.nn.Module")
File D:\Anaconda\envs\summer2023\lib\site-packages\bitsandbytes\optim_init_.py:6
1 # Copyright (c) Facebook, Inc. and its affiliates.
2 #
3 # This source code is licensed under the MIT license found in the
4 # LICENSE file in the root directory of this source tree.
----> 6 from bitsandbytes.cextension import COMPILED_WITH_CUDA
8 from .adagrad import Adagrad, Adagrad8bit, Adagrad32bit
9 from .adam import Adam, Adam8bit, Adam32bit, PagedAdam, PagedAdam8bit, PagedAdam32bit
File D:\Anaconda\envs\summer2023\lib\site-packages\bitsandbytes\cextension.py:20
18     CUDASetup.get_instance().generate_instructions()
19     CUDASetup.get_instance().print_log_stack()
---> 20     raise RuntimeError('''
21     CUDA Setup failed despite GPU being available. Please run the following command to get more information:
22
23     python -m bitsandbytes
24
25     Inspect the output of the command and see if you can locate CUDA libraries. You might need to add them
26     to your LD_LIBRARY_PATH. If you suspect a bug, please take the information from python -m bitsandbytes
27     and open an issue at: https://github.com/TimDettmers/bitsandbytes/issues''')
28 lib.cadam32bit_grad_fp32 # runs on an error if the library could not be found -> COMPILED_WITH_CUDA=False
29 lib.get_context.restype = ct.c_void_p
RuntimeError:
CUDA Setup failed despite GPU being available. Please run the following command to get more information:
    python -m bitsandbytes

    Inspect the output of the command and see if you can locate CUDA libraries. You might need to add them
    to your LD_LIBRARY_PATH. If you suspect a bug, please take the information from python -m bitsandbytes
    and open an issue at: https://github.com/TimDettmers/bitsandbytes/issues

Same here, with Nvidia SDK 1.8 / Windows / pytorch https://download.pytorch.org/whl/cu118
Thjere is no libcudart file on my system

same
(venv) PS D:\code\llama2\llama_inference> python -m bitsandbytes
False
===================================BUG REPORT===================================
D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\cuda_setup\main.py:166: UserWarning: Welcome to bitsandbytes. For bug reports, please run
python -m bitsandbytes
warn(msg)
The following directories listed in your path were found to be non-existent: {WindowsPath('/storage.flutter-io.cn'), WindowsPath('https')}
The following directories listed in your path were found to be non-existent: {WindowsPath('https'), WindowsPath('/goproxy.io,direct')}
The following directories listed in your path were found to be non-existent: {WindowsPath('https'), WindowsPath('/pub.flutter-io.cn')}
CUDA_SETUP: WARNING! libcudart.so not found in any environmental path. Searching in backup paths...
The following directories listed in your path were found to be non-existent: {WindowsPath('/usr/local/cuda/lib64')}
DEBUG: Possible options found for libcudart.so: set()
CUDA SETUP: PyTorch settings found: CUDA_VERSION=118, Highest Compute Capability: 8.6.
CUDA SETUP: To manually override the PyTorch CUDA version please see:https://github.com/TimDettmers/bitsandbytes/blob/main/how_to_use_nonpytorch_cuda.md
CUDA SETUP: Loading binary D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\libbitsandbytes_cuda118.so...
argument of type 'WindowsPath' is not iterable
CUDA SETUP: Problem: The main issue seems to be that the main CUDA runtime library was not detected.
CUDA SETUP: Solution 1: To solve the issue the libcudart.so location needs to be added to the LD_LIBRARY_PATH variable
CUDA SETUP: Solution 1a): Find the cuda runtime library via: find / -name libcudart.so 2>/dev/null
CUDA SETUP: Solution 1b): Once the library is found add it to the LD_LIBRARY_PATH: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:FOUND_PATH_FROM_1a
CUDA SETUP: Solution 1c): For a permanent solution add the export from 1b into your .bashrc file, located at ~/.bashrc
CUDA SETUP: Solution 2: If no library was found in step 1a) you need to install CUDA.
CUDA SETUP: Solution 2a): Download CUDA install script: wget https://github.com/TimDettmers/bitsandbytes/blob/main/cuda_install.sh
CUDA SETUP: Solution 2b): Install desired CUDA version to desired location. The syntax is bash cuda_install.sh CUDA_VERSION PATH_TO_INSTALL_INTO.
CUDA SETUP: Solution 2b): For example, "bash cuda_install.sh 113 ~/local/" will download CUDA 11.3 and install into the folder ~/local
Traceback (most recent call last):
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.3056.0_x64__qbz5n2kfra8p0\lib\runpy.py", line 187, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, Error)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.3056.0_x64__qbz5n2kfra8p0\lib\runpy.py", line 146, in get_module_details
return get_module_details(pkg_main_name, error)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.3056.0_x64__qbz5n2kfra8p0\lib\runpy.py", line 110, in get_module_details
import(pkg_name)
File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes_init.py", line 6, in
from . import cuda_setup, utils, research
File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\research_init.py", line 1, in
from . import nn
File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\research\nn_init.py", line 1, in
from .modules import LinearFP8Mixed, LinearFP8Global
File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\research\nn\modules.py", line 8, in
from bitsandbytes.optim import GlobalOptimManager
File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\optim_init.py", line 6, in
from bitsandbytes.cextension import COMPILED_WITH_CUDA
File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\cextension.py", line 20, in
raise RuntimeError('''
RuntimeError:
CUDA Setup failed despite GPU being available. Please run the following command to get more information:
    python -m bitsandbytes

    Inspect the output of the command and see if you can locate CUDA libraries. You might need to add them
    to your LD_LIBRARY_PATH. If you suspect a bug, please take the information from python -m bitsandbytes
    and open an issue at: https://github.com/TimDettmers/bitsandbytes/issues

same
(venv) PS D:\code\llama2\llama_inference> python -m bitsandbytes False
===================================BUG REPORT=================================== D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\cuda_setup\main.py:166: UserWarning: Welcome to bitsandbytes. For bug reports, please run
python -m bitsandbytes
warn(msg)
The following directories listed in your path were found to be non-existent: {WindowsPath('/storage.flutter-io.cn'), WindowsPath('https')} The following directories listed in your path were found to be non-existent: {WindowsPath('https'), WindowsPath('/goproxy.io,direct')} The following directories listed in your path were found to be non-existent: {WindowsPath('https'), WindowsPath('/pub.flutter-io.cn')} CUDA_SETUP: WARNING! libcudart.so not found in any environmental path. Searching in backup paths... The following directories listed in your path were found to be non-existent: {WindowsPath('/usr/local/cuda/lib64')} DEBUG: Possible options found for libcudart.so: set() CUDA SETUP: PyTorch settings found: CUDA_VERSION=118, Highest Compute Capability: 8.6. CUDA SETUP: To manually override the PyTorch CUDA version please see:https://github.com/TimDettmers/bitsandbytes/blob/main/how_to_use_nonpytorch_cuda.md CUDA SETUP: Loading binary D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\libbitsandbytes_cuda118.so... argument of type 'WindowsPath' is not iterable CUDA SETUP: Problem: The main issue seems to be that the main CUDA runtime library was not detected. CUDA SETUP: Solution 1: To solve the issue the libcudart.so location needs to be added to the LD_LIBRARY_PATH variable CUDA SETUP: Solution 1a): Find the cuda runtime library via: find / -name libcudart.so 2>/dev/null CUDA SETUP: Solution 1b): Once the library is found add it to the LD_LIBRARY_PATH: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:FOUND_PATH_FROM_1a CUDA SETUP: Solution 1c): For a permanent solution add the export from 1b into your .bashrc file, located at ~/.bashrc CUDA SETUP: Solution 2: If no library was found in step 1a) you need to install CUDA. CUDA SETUP: Solution 2a): Download CUDA install script: wget https://github.com/TimDettmers/bitsandbytes/blob/main/cuda_install.sh CUDA SETUP: Solution 2b): Install desired CUDA version to desired location. The syntax is bash cuda_install.sh CUDA_VERSION PATH_TO_INSTALL_INTO. CUDA SETUP: Solution 2b): For example, "bash cuda_install.sh 113 ~/local/" will download CUDA 11.3 and install into the folder ~/local Traceback (most recent call last): File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.3056.0_x64__qbz5n2kfra8p0\lib\runpy.py", line 187, in run_module_as_main mod_name, mod_spec, code = get_module_details(mod_name, Error) File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.3056.0_x64__qbz5n2kfra8p0\lib\runpy.py", line 146, in get_module_details return get_module_details(pkg_main_name, error) File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.3056.0_x64__qbz5n2kfra8p0\lib\runpy.py", line 110, in get_module_details import(pkg_name) File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes__init.py", line 6, in from . import cuda_setup, utils, research File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\research__init.py", line 1, in from . import nn File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\research\nn__init.py", line 1, in from .modules import LinearFP8Mixed, LinearFP8Global File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\research\nn\modules.py", line 8, in from bitsandbytes.optim import GlobalOptimManager File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\optim__init.py", line 6, in from bitsandbytes.cextension import COMPILED_WITH_CUDA File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\cextension.py", line 20, in raise RuntimeError(''' RuntimeError: CUDA Setup failed despite GPU being available. Please run the following command to get more information:__
    python -m bitsandbytes

    Inspect the output of the command and see if you can locate CUDA libraries. You might need to add them
    to your LD_LIBRARY_PATH. If you suspect a bug, please take the information from python -m bitsandbytes
    and open an issue at: https://github.com/TimDettmers/bitsandbytes/issues

My setup  LD_LIBRARY_PATH = C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\lib\x64

same
(venv) PS D:\code\llama2\llama_inference> python -m bitsandbytes False
===================================BUG REPORT=================================== D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\cuda_setup\main.py:166: UserWarning: Welcome to bitsandbytes. For bug reports, please run
python -m bitsandbytes
warn(msg)
The following directories listed in your path were found to be non-existent: {WindowsPath('/storage.flutter-io.cn'), WindowsPath('https')} The following directories listed in your path were found to be non-existent: {WindowsPath('https'), WindowsPath('/goproxy.io,direct')} The following directories listed in your path were found to be non-existent: {WindowsPath('https'), WindowsPath('/pub.flutter-io.cn')} CUDA_SETUP: WARNING! libcudart.so not found in any environmental path. Searching in backup paths... The following directories listed in your path were found to be non-existent: {WindowsPath('/usr/local/cuda/lib64')} DEBUG: Possible options found for libcudart.so: set() CUDA SETUP: PyTorch settings found: CUDA_VERSION=118, Highest Compute Capability: 8.6. CUDA SETUP: To manually override the PyTorch CUDA version please see:https://github.com/TimDettmers/bitsandbytes/blob/main/how_to_use_nonpytorch_cuda.md CUDA SETUP: Loading binary D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\libbitsandbytes_cuda118.so... argument of type 'WindowsPath' is not iterable CUDA SETUP: Problem: The main issue seems to be that the main CUDA runtime library was not detected. CUDA SETUP: Solution 1: To solve the issue the libcudart.so location needs to be added to the LD_LIBRARY_PATH variable CUDA SETUP: Solution 1a): Find the cuda runtime library via: find / -name libcudart.so 2>/dev/null CUDA SETUP: Solution 1b): Once the library is found add it to the LD_LIBRARY_PATH: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:FOUND_PATH_FROM_1a CUDA SETUP: Solution 1c): For a permanent solution add the export from 1b into your .bashrc file, located at ~/.bashrc CUDA SETUP: Solution 2: If no library was found in step 1a) you need to install CUDA. CUDA SETUP: Solution 2a): Download CUDA install script: wget https://github.com/TimDettmers/bitsandbytes/blob/main/cuda_install.sh CUDA SETUP: Solution 2b): Install desired CUDA version to desired location. The syntax is bash cuda_install.sh CUDA_VERSION PATH_TO_INSTALL_INTO. CUDA SETUP: Solution 2b): For example, "bash cuda_install.sh 113 ~/local/" will download CUDA 11.3 and install into the folder ~/local Traceback (most recent call last): File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.3056.0_x64__qbz5n2kfra8p0\lib\runpy.py", line 187, in run_module_as_main mod_name, mod_spec, code = get_module_details(mod_name, Error) File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.3056.0_x64__qbz5n2kfra8p0\lib\runpy.py", line 146, in get_module_details return get_module_details(pkg_main_name, error) File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.3056.0_x64__qbz5n2kfra8p0\lib\runpy.py", line 110, in get_module_details import(pkg_name) File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes__init.py", line 6, in from . import cuda_setup, utils, research File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\research__init.py", line 1, in from . import nn File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\research\nn__init.py", line 1, in from .modules import LinearFP8Mixed, LinearFP8Global File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\research\nn\modules.py", line 8, in from bitsandbytes.optim import GlobalOptimManager File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\optim__init.py", line 6, in from bitsandbytes.cextension import COMPILED_WITH_CUDA File "D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\cextension.py", line 20, in raise RuntimeError(''' RuntimeError: CUDA Setup failed despite GPU being available. Please run the following command to get more information:__
    python -m bitsandbytes

    Inspect the output of the command and see if you can locate CUDA libraries. You might need to add them
    to your LD_LIBRARY_PATH. If you suspect a bug, please take the information from python -m bitsandbytes
    and open an issue at: https://github.com/TimDettmers/bitsandbytes/issues

My setup LD_LIBRARY_PATH = C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\lib\x64

did you sovle this problem by this way?

Guys, we all are wasting time here, since it is explicitly notified that "The bitsandbytes library is currently only supported on Linux distributions. Windows is not supported at the moment." (https://github.com/TimDettmers/bitsandbytes)
There would be another repository dedicated to Windows there: https://github.com/Keith-Hon/bitsandbytes-windows
I'm currently trying to get it to work...

Guys, we all are wasting time here, since it is explicitly notified that "The bitsandbytes library is currently only supported on Linux distributions. Windows is not supported at the moment." (https://github.com/TimDettmers/bitsandbytes) There would be another repository dedicated to Windows there: https://github.com/Keith-Hon/bitsandbytes-windows I'm currently trying to get it to work...

wdf... thanks bro, i'll try it after class

Guys, we all are wasting time here, since it is explicitly notified that "The bitsandbytes library is currently only supported on Linux distributions. Windows is not supported at the moment." (https://github.com/TimDettmers/bitsandbytes) There would be another repository dedicated to Windows there: https://github.com/Keith-Hon/bitsandbytes-windows I'm currently trying to get it to work...

wtf... thanks bro, i'll try it after class

Seemed to work but I am stuck, since I am using 4 bits quantization and it is not yet in this release ( "4 bit quantization requires bitsandbytes>=0.39.0 - please upgrade your bitsandbytes version").

You guy just try:
pip install bitsandbytes-windows
Latest version is 0.37.5，my cuda sdk version is 12.2, after installed, even though it use cuda116 but for me it works!!!
================================================================================
binary_path: D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\cuda_setup\libbitsandbytes_cuda116.dll
CUDA SETUP: Loading binary D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\cuda_setup\libbitsandbytes_cuda116.dll...

Yes, bitsandbytes-windows installation worked good, but my specific project is using 4 bits quantization, which seems to have been integrated in later release  0.39...

You guy just try: pip install bitsandbytes-windows
Latest version is 0.37.5，my cuda sdk version is 12.2, after installed, even though it use cuda116 but for me it works!!!
================================================================================ binary_path: D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\cuda_setup\libbitsandbytes_cuda116.dll CUDA SETUP: Loading binary D:\code\llama2\llama_inference\venv\lib\site-packages\bitsandbytes\cuda_setup\libbitsandbytes_cuda116.dll...

love ya bro！, that worked， i install  bitsandbytes-windows-0.37.5

Thank you very much,problem solved!

Thank you very much,problem solved!

you're welcome,guys

Yes, bitsandbytes-windows installation worked good, but my specific project is using 4 bits quantization, which seems to have been integrated in later release 0.39...

try it bro:https://github.com/jllllll/bitsandbytes-windows-webui/releases/download/wheels/bitsandbytes-0.41.1-py3-none-win_amd64.whl

Yes, bitsandbytes-windows installation worked good, but my specific project is using 4 bits quantization, which seems to have been integrated in later release  0.39...

sry you can try to update,maybe that will work

Just in case you're either using wsl and or it isn't working with the just regular pip install bitsandbytes I was having the issue with it not finding libcudart.so even after adding to $LD_LIBRARY_PATH so in bitsandbytes/cuda_setup/main.py I changed it to
 CUDA_RUNTIME_LIBS: list = ['libcudart.so', 'libcudart.so.12', 'libcudart.so.12.2.140']

and then input this command as it suggested, into the command line: export BNB_CUDA_VERSION=122
It worked for me after that.

Yes, bitsandbytes-windows installation worked good, but my specific project is using 4 bits quantization, which seems to have been integrated in later release 0.39...

try it bro:https://github.com/jllllll/bitsandbytes-windows-webui/releases/download/wheels/bitsandbytes-0.41.1-py3-none-win_amd64.whl

It works! I will call you bitsandbytes-superman from now😚

Just in case you're either using wsl and or it isn't working with the just regular pip install bitsandbytes I was having the issue with it not finding libcudart.so even after adding to $LD_LIBRARY_PATH so in bitsandbytes/cuda_setup/main.py I changed it to
 CUDA_RUNTIME_LIBS: list = ['libcudart.so', 'libcudart.so.12', 'libcudart.so.12.2.140']

and then input this command as it suggested, into the command line: export BNB_CUDA_VERSION=122 It worked for me after that.

This helps!

Bitsandbytes was not supported windows before, but my method can support windows.（yuhuang）
1  open folder J:\StableDiffusion\sdwebui，Click the address bar of the folder and enter CMD
or WIN+R, CMD  。enter，cd /d J:\StableDiffusion\sdwebui
2  J:\StableDiffusion\sdwebui\py310\python.exe -m pip uninstall bitsandbytes
3 J:\StableDiffusion\sdwebui\py310\python.exe -m pip uninstall bitsandbytes-windows
4 J:\StableDiffusion\sdwebui\py310\python.exe -m pip install https://github.com/jllllll/bitsandbytes-windows-webui/releases/download/wheels/bitsandbytes-0.41.1-py3-none-win_amd64.whl
Replace your SD venv directory file（python.exe Folder） here（J:\StableDiffusion\sdwebui\py310）

Guys, we all are wasting time here, since it is explicitly notified that "The bitsandbytes library is currently only supported on Linux distributions. Windows is not supported at the moment." (https://github.com/TimDettmers/bitsandbytes) There would be another repository dedicated to Windows there: https://github.com/Keith-Hon/bitsandbytes-windows I've tried to get it to work in my project, but was stuck since I am using 4 bits quantization and it is not yet in this release ( "4 bit quantization requires bitsandbytes>=0.39.0 - please upgrade your bitsandbytes version").

I am using WSL, I wonder whether I should use the bitsandbyes or bitsandbytes-windows.. Any suggestion and advice?

Guys, we all are wasting time here, since it is explicitly notified that "The bitsandbytes library is currently only supported on Linux distributions. Windows is not supported at the moment." (https://github.com/TimDettmers/bitsandbytes) There would be another repository dedicated to Windows there: https://github.com/Keith-Hon/bitsandbytes-windows I've tried to get it to work in my project, but was stuck since I am using 4 bits quantization and it is not yet in this release ( "4 bit quantization requires bitsandbytes>=0.39.0 - please upgrade your bitsandbytes version").

I am using WSL, I wonder whether I should use the bitsandbyes or bitsandbytes-windows.. Any suggestion and advice?

Try both


Fix compilation errors on master

Motivation
Fix compilation issue on master
Somewhat showcase is broken as IDE shows errors and uses released packages but gradle is using local ones:

To really replicate this we need to use local profile in IDE.
In fact I have verified couple issues without this flag.

@danielpassos do you think this is standard behavior and we should document that or we should look out for better solution?

I don't know if I like what we are doing here, mixing release and snapshot at the same time.
The biggest problem is most of the people who going to use this don't wanna download the SDK and install it locally.
IMHO we should not use any SNAPSHOT here only released one, It will avoid a lot of compile problem for the users.

I don't know if I like what we are doing here, mixing release and snapshot at the same time.
The biggest problem is most of the people who going to use this don't wanna download the SDK and install it locally.
IMHO we should not use any SNAPSHOT here only released one, It will avoid a lot of compile problem for the users.

This brings us to a question that was asked on the mailing list. It has not received any answers so far. https://groups.google.com/forum/#!topic/aerogear/8pxVnXc8hsk
What is the purpose of the showcase applications? If the showcase only uses release builds of the SDK then that means the showcase cannot be used as part of a local development workflow while working on the SDKs. In that case, what do we use to try out the SDKs during development?

@darahayes I have replied it on the ML thread

@danielpassos cool. Can we do a release of the SDK then? Then we can get this merged?

@darahayes Sure, let me know if you wanna me to do that if not feel free to do!


update extension location

moved xpa extension properly into imexam installed package

Coverage decreased (-0.06%) to 38.286% when pulling f22ea368e899581e5d83e40cce14e4188cbe2405 on sosey:master into 5e76b31f62b729d80f8aa108978af06e308f5619 on spacetelescope:master.

um, something wierd happened, closing

dunno why travis didn't trigger for spacetelescope, but it ran under my own account and passed: https://travis-ci.org/github/sosey/imexam/builds/668774861


useProfile

useProfile works for me, ty for adding that 👍
I'm glad you added batching. I've been having trouble with my feeds, probably bc of doing multiple individual user info requests and most get dropped.
Small issue with the useProfile example in README - I've opened a pull request to suggest a fix.

Merged 🤝


Upgrade cuda to upgrade ubuntu to upgrade ffmpeg

Using this patch relies on this PR being included in your cog binary
https://github.com/replicate/cog/pull/779
The version of CUDA changes the docker image that is used as a base.

Note that this fixes #2

Would love to get this merged :)

Thanks for your suggestion
@bfirsh I tried it does not seem Cuda 11.7 works with Cog yet? 11.6 works

I have pushed a version with torch=1.13.0 and NOT specifying cuda version, could you try if it works for your .mp4 input @maccman @anotherjesse?

My sample worked!


Add dl_iterate_phdr to Android

Adds the dl_iterate_phdr function for Android targets. This is required for Android support in gimli and by proxy, backtrace.
I tested this in backtrace both in an i686 emulator and a physical arm64 device.
This API is only available on Version 21+. I'm not sure how that's typically handled in libc, so I added a doc comment.
Let me know what else is needed!

Looks good, thanks :)
@bors r+

:pushpin: Commit 970fec9245ace9808178e08a75ee15c859900c4e has been approved by JohnTitor

:hourglass: Testing commit 970fec9245ace9808178e08a75ee15c859900c4e with merge 800c771c7f7174fc4f1bb7a34efd61f1ee5f737a...

:broken_heart: Test failed - checks-actions

@JohnTitor Thanks for the review! I figured out how to get the Android tests running locally and resolved a few places where naming didn't exactly match the header definitions.
CI should be passing now.

👍, @bors r+

:pushpin: Commit ab1472eb086cea9d23aa267206dc040feefa673c has been approved by JohnTitor

:hourglass: Testing commit ab1472eb086cea9d23aa267206dc040feefa673c with merge d3ca6a751eab8aa87f52e03b76b93a5d550f0e37...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: JohnTitor
Pushing d3ca6a751eab8aa87f52e03b76b93a5d550f0e37 to master...


偶现这个播放崩溃的问题

[flv @ 0x308a200] audio stream discovered after head already parsed
[flv @ 0x308a200] Audio codec (f) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[flv @ 0x308a200] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list<EMAIL_ADDRESS>

crash 的堆栈提供一下
版本号多少
播放的流地址提供一下


Support target x86_64-unknown-freebsd

Hi,
I discovered Kani does not support freebsd:
Error: Kani does not support this platform (Rust target x86_64-unknown-freebsd)

Is this a possibility?  Would it be a large change to add support for freebsd?
Cheers

Hi @yancyribbens, that's a great request. One limitation to consider is that FreeBSD is currently a Tier 2 platform for the rust compiler (Platform Support). Since we highly depend on the rust compiler, we would likely not be able to provide stronger guarantees.

https://github.com/diffblue/cbmc/pull/7924 fixes a build issue in CBMC.

@yancyribbens Are you blocked in your project by this issue?

@jaisnan what is your definition of blocked?  Why do you ask?

By 'blocked,' I mean if you're unable to make progress on your work due to the reported issue or if it's causing any significant delays. I asked if you were blocked to understand if this is high priority to you.
Please do share any concerns or questions you have.


[BUG] Tooltip position not animated when chart data updates.

Expected Behavior
When I update the data of the chart and call chart.update(), the chart animates to the updated state and the tooltip should be animated to the position that would correspond to the updated data state.
Current Behavior
When I update de data of the chart and call chart.update() the chart animates to the updated state, but the tooltip remains in the same position. If I move the mouse while the animation of the chart is taking place, then the tooltip does the movement that you would expect, following the data on the chart. If, after the animation took place I move the mouse, then the tooltip goes to the position where it should have been animated.
Possible Solution
I guess the update of the tooltip is bound to the mouse movement. I think it should be bound to the data update too.
Steps to Reproduce (for bugs)
Link to a codepen with the bug. The behavior when the mouse moves during data animation is a bit different to the bug that I found, but the main problem stays, that is that the tooltip doesn't move during chart animation.
Context
I was using Chart.js for a FreeCodeCamp project where I needed to represent some votes in a chart. I wanted the votes to be updated in real time if other users were voting for the same poll.

Environment

Chart.js version: 2.5.0
Browser name and version: Chrome Version 56.0.2924.76 (64-bit) running on Linux Mint 18
Link to your project: https://github.com/dgrcode/FCC-Voting-App

Same issue

Thought I would leave my "investigation" note here as I'm experiencing same problem with custom rendered content (animation onProgress and onComplete), so the issue might be the same.
On the update function (which is called continuously in the duration the animation) the input animationObject that is passed in, the currentStep value is always the same as numSteps, while it would be expected for this value to animate from 0 to numSteps.

This issue is resolved in v3.0.0-alpha https://codepen.io/etimberg/pen/XWmGLJv?editors=1010


Molecule schema: Missing properties on PlatformModel

Molecule schema is missing pre_build_image and env.
see also:
https://github.com/ansible-community/molecule/blob/master/src/molecule/model/schema_v3.py

That is a property specific to docker/podman containers, molecule itself does not know about it. Addressing these will be bit tricky as drivers do have lots of custom options.
I am not closing it because I still consider it a valid bug, is only one that is not so easy to address.

@ssbarnea I'm guessing the pre_build_image part of this issue has been resolved. See 0e5859fe for the resolution.
Is that commit a good way to model the "env" fix? If so, I might take a swing at it this weekend.


Fixing download link to the SPO Management Shell

The download link had an extra space in it causing the "here" not to contain the actual link. Fixed that.

Docs Build status updates of commit 9bdda2d:
:clock10: Full build: the average full build time is 14 min(s) 12 sec(s), this is based on the last 185 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit 9bdda2d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Enable-SPOCommSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 43d3ebe:
:clock10: Full build: the average full build time is 14 min(s) 14 sec(s), this is based on the last 230 build(s) for this repository.

Docs Build status updates of commit 43d3ebe:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit f25c460:
:clock10: Full build: the average full build time is 14 min(s) 10 sec(s), this is based on the last 346 build(s) for this repository.

Docs Build status updates of commit f25c460:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 65d06c0:
:clock10: Full build: the average full build time is 14 min(s) 9 sec(s), this is based on the last 351 build(s) for this repository.

Docs Build status updates of commit 65d06c0:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Search bar need to be fixed

The outline of the search bar need to be fixed.
Assing this issue for me under GSSoC24

Thank u sir

Thank u sir

Call me using my name Arghdip or Bro. not sir bro...❤

Hello @arghadipmanna101 sir
I would like to work on this issue as a contributor to the GSSOC. please assign this to me!
I have relevant skills that definitely help to enhance the website.

Already solved .


CMakeLists.txt: easily switch between static and shared libs

This PR makes it easy to switch between building forestdb as a shared library or as a static library via the BUILD_SHARED_LIBS option.  By default it will build a shared lib as before.
Building a static lib can be invoked ala:
cmake -DBUILD_SHARED_LIBS:bool=OFF
Signed-off-by: Mark Nelson<EMAIL_ADDRESS>

Thanks for the patch! If this is your first code contribution to Couchbase, you'll need to fill out our Contributor License Agreement, which basically just declares that you created the code and are allowing us to release it under the Apache license.

http://review.couchbase.org/#/settings/agreements

I'm not sure I should sign any contributor license agreements per my employer, but I hear-by release this specific commit into the public domain so you may use it under any license you wish. :)

Hi @markhpc , if you don't mind, may I just merge this commit via gerrit ?
This way, you won't have to sign anything and I won't have to break any rules by accepting a change without the CLA signed?

The fix has been merged. Thank you!


🎯 Vector property

Refer to the contributor docs to learn how to generally add new properties to Pandora!

A Vector property (which could be Vector2, Vector3 — Vector2i and 3i would be nice but not necessary —) would help a lot.

Just for future context: currently I am using Pandora to store Maps and in each map I have properties to store spawn position. Having vectors would make it easier since I don't need two properties for x y axis.


Preparations

Mostly cosmetic changes, just to make it compiling in context of engine.
This is a part of patches sent across vgui_support, openvgui and xash3d-fwgs repos.

Abandoned.


Update to use simplified t2-firmware LED API

More details here: https://github.com/tessel/t2-firmware/pull/105

Tried it and it worked last night! @rwaldron maybe we should hold off on merging this until I get a chance to put out a new release? (sometime this week)

No problem!

Ping @johnnyman727

@rwaldron I haven't forgotten about this! Will try to get a release out this week.

superseded by https://github.com/tessel/t2-cli/pull/398
tried to PR your PR @rwaldron to add my one line change but got lost in git for more than 10 minutes so calling that a loss..


[style]: UI change in The Find Blood page

What's the style idea?
Changing the Blood Donor Cards.
Adding theme based and interactive cards.
I can use shadcn to change the.
Add screenshots
This is my basic idea that I've done on Figma.

Record

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue

It looks good, but incorporating some light colors and adding a border-radius would enhance the appearance


Build failed on Apple M1

I attempted to build this project on Apple M1 powered MacBook.
clang main.c -I./src -Os -Wno-inline-asm -fPIC -o interp

Clang complained as following:
In file included from main.c:18:
In file included from ./src/interp.h:396:
./src/opcodes.h:27:1: error: unknown AArch64 fixup kind!
OP_IMPL_IMM(push, {
^
./src/opcodes.h:8:46: note: expanded from macro 'OP_IMPL_IMM'
    #define OP_IMPL_IMM(op,body)    OP(op, { GET_IMM(op_##op); body })
                                             ^
./src/interp.h:216:46: note: expanded from macro 'GET_IMM'
                                asm volatile("ldr %0, .IMM_" STRINGIFY(ID)                  EOL \
                                             ^
<inline asm>:1:2: note: instantiated into assembly here
        ldr x8, .IMM_op_push
        ^
...
6 errors generated.

Environment:

Apple clang version 14.0.0 (clang-14<IP_ADDRESS>)
macOS 13.1 (arm64)

Testing on Arm64 based Ubuntu Linux, I got the result below:
Initializing...
Generating Code @ 0xffff8ac0c000
Instructions:<PHONE_NUMBER>
Code: 240 bytes
Segmentation fault

clang complained as following:
./src/opcodes.h:17:1: warning: maximum bytes expression exceeds alignment and has no effect [-Winline-asm]
OP_IMPL(dummy1, { asm("nop; #1"); })
^
./src/opcodes.h:7:37: note: expanded from macro 'OP_IMPL'
    #define OP_IMPL(op,body)        OP(op,body)
                                    ^
./src/interp.h:324:41: note: expanded from macro 'OP'
                                        ASM_ALIGN_NOP();                    \
                                        ^
./src/interp.h:296:49: note: expanded from macro 'ASM_ALIGN_NOP'
            #define ASM_ALIGN_NOP()         asm(".align " STRINGIFY(OP_ALIGN) ",,16")
                                                ^
<inline asm>:1:12: note: instantiated into assembly here
        .align 4,,16
                  ^


[BUG]: Traceback on pulse build

Describe the bug
Title says it all. Only if there are no requirements table found in pulse.toml
To Reproduce
Steps to reproduce the behavior:

Run pulse build with no requirements table.

Expected behavior
Throw an error
Desktop (please complete the following information):

OS: Windows 10

seems i don't know how i produced this error, so I'll close this, since this works well...

I fixed it here: https://github.com/pulsepm/pulse/pull/67
Sorry, I haven’t seen this issue earlier.


 Thank you.

Duplicate of #101.


add error message for expired names

if the name is expired (and grace period ends) the metadata will show warning message as a result for a given name.
Example
Given example is valid for 2022.07.04 UTC, means it still in grace period;
https://app.ens.domains/name/supper.eth/details
So the service should return the metadata without any warning until then;
http://localhost:8080/mainnet/0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85/supper.eth
Unlike above;
https://app.ens.domains/name/openauction.eth is already expired and grace period is over.
For that reason, metadata service should return a warning message for the given name;
http://localhost:8080/mainnet/0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85/openauction.eth
{"message":"'openauction.eth' is already been expired at Fri, 25 Feb 2022 17:59:18 GMT."}

Good addition.
I have this case where I request the Metadata Service and I don't know the domain, but only the tokenId/hex/etc. In such case, can I get the domain name somehow, based i have the tokenId? I guess not, because hash function is used under the hood?
@mdtanrikulu ideas?


Implement Better Logging

Currently we are using the default golang logger. I need to research what other logging frameworks exist.

The default logger is fine for now.


Create Figma wireframes for guidance overlay (customization)

"Guidance overlay" describes a feature allowing an administrator to "overlay" a publicly available template with customized questions, sections, and question-specific guidance. The available customizations include:

Provide example answers, and default answers
Add customization to complex question widgets (institutional repo preferences, etc.) _(This may be better addressed in the Repository Selector _ issue)
Add their guidance group to a question (this is tagging)
Provide guidance at the question level (this is guidance specific to a single question)
Create additional questions
Add their own sections (with questions)

Additional requirements:

New customized guidance (overlay) should continue to include all existing guidance from the original template.
When a question in the original template has changed (for example, a funder has changed the wording of a question): Display an alert for admin users when a template they have customized has changed and show the details of the change. Show the old/new questions side by side to allow the admin to reconcile.

Viewing this overlay when building a plan will only be available to users from the same organization/institution. One exception is that if a plan that has an overlay is shared with a researcher from another organization/institution, that user will view the guidance of the plan creator.

Hello all,
We've got a first draft of this ready for you.
I've done a Fraser-style voice walk through, available at https://www.loom.com/share/26049b122164443aa1f634798b74c2d0?sid=0ffb1807-ad98-4289-a65b-c6a440840f48 (about 11 mins).
The interactive prototype itself is at https://www.figma.com/proto/RRtoRLyr5Spf0KiyRfEclt/DMP-Explain?page-id=325%3A351&node-id=413-1132&viewport=479%2C142%2C0.16&t=YZVs6Vo6G7lqMbkQ-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=413%3A1132.
Any questions please shout, otherwise look forward to seeing you all tomorrow and going through this then.

I'm trying to review this today but I'm a bit unclear about the relationship between this guidance and the org guidance.  For example, this makes it seem like UCOP may have one policy for a template while this admin is overriding it for different guidance.  However, admins are specifically associated with the organization and are the ones that set up the org's guidance as far as I understand.  So I'm not sure how it comes in to play that a UCOP admin might override their own guidance - wouldn't they be the ones that set the original guidance and could just go change it?

I'm also overall a bit unclear on the relationship between this flow and the Template builder flow which seems like the same idea - taking a basic start from a funder (e.g. a base NSF template) and adding org-specific guidance.  I may need to be given more context on this from Maria or others on the need here so I can give feedback.

As discussed I've now created a dedicated card for feedback on this: #624


added woocommerce error detail

Issue
See Issue #1381. This PR adds the text of the error message so that google searches will lead to this guide.

Coverage increased (+0.2%) to 94.399% when pulling 280aa18e8c30a6dc1b66eff66a542904116439be on Mikewalker24:master into 758c6db95a15cb6d41c55ce657bdd74eaf47a471 on timber:master.

Sometimes the simplest changes are the most profound. Thank you @Mikewalker24, and congrats on your first contrib.!


Strict check that no-interaction flag is set and is true for Artisan commands

Go easy on me, this is my first contribution to open source.
This PR was made because I noticed a bug with the way that the CallsCommand concern handles how it checks if the command should be run with no-interaction i.e. does not prompt for user input.
It currently only checks if the option is present, rather than checks if it is true or false in the input array. So, rather than hasParameterOption in createInputFromArguments, I changed it to getParameterOption which still returns false if the option is not present. If not present === false; present in terminal === true; present but value is false === false.
I reproduced this bug when calling a deprecated Artisan command in a Laravel package which passed all of the arguments and options to the new Artisan command via $this->call(...), PSB an example.
    /**
     * Execute the console command.
     *
     * @return int
     */
    public function handle()
    {
        $options = collect($this->options())->mapWithKeys(function($value, $key) {
            return ["--{$key}" => $value];
        })->toArray();

        $this->call('prompt:real', $options);

        return 0;
    }

With this array of options, it passes a default value for no-interaction which is false. In its current state, the framework will take that option as: you want no prompt to appear as it runs through the command.
Here is an example of the real command that should prompt for input, but would not:
    /**
     * Execute the console command.
     *
     * @return int
     */
    public function handle()
    {
        $this->ask('What is your name?');

        return 0;
    }

Thank you for taking the time to review this. I hope I have explained this clearly enough.

Please send this to 6.x.


Miscellanous refactorings

Please only pay attention to the commits on May 5. I don't know why it's including my entire commit history, sorry! :(. They contain minor refactorings to improve performance and readability.

One more time thanks for your contribution. I will try to check it by the end of this week.

No problem. If it's too confusing to review/merge with all the old commits, please let me know and I will resubmit it.


Attributes of relationships #415

Resolves: #415

@hhware Thanks for working up this PR in time for consideration.
I personally don't agree with this blurring of lines between resources and relationships. In my opinion, this adds a lot of complexity for little benefit. If relationships are allowed to have attributes, then the spec will need to provide a means to edit those attributes (PATCH I suppose). Furthermore, it will create dissonance for API designers who need to decide between creating resources vs. "complex relationships".

Moving to 1.0 milestone.
@wycats @steveklabnik are either of you in favor?

@dgeb, thanks for reviewing it!

then the spec will need to provide a means to edit those attributes (PATCH I suppose)

It is addressed by this PR

I personally don't agree with this blurring of lines between resources and relationships. In my opinion, this adds a lot of complexity for little benefit... Furthermore, it will create dissonance for API designers who need to decide between creating resources vs. "complex relationships".

IMHO, this "blurring" can be viewed as an intrinsic feature of some real-life systems, which have objects which are "in between" resources and links, but much closer to links. As for the "dissonance", it could indeed be a dissonance to some, but longed-for flexibility to others. There is always a balance between rigidity and flexibility, and I think it would in the spirit of JSON API to be more on a rigid side of things, but not entirely rigid. In my view, allowing simple attributes of relationships is 90% of rigidity and 10% of flexibility.
Let me elaborate more with two examples.
First one extends the filesystem example from #415. Imagine a CMS-like system (this is the case which I personally care about), consisting of a tree of containers, which can contain either some objects or other containers. A container with all its content can be referred to from another container (to allow people share content without copying it). The difference from the filesystem example is that there is more than one types of such references (to allow different approach to sharing, either with read-only rights, with some admin rights, etc.) Surely, each of this types of sharing links can be represented as an object of its own, necessitating several types of such objects and complexity associated with that, but it would be very convenient for the API designer to hide this complexity and simplify life for himself and for the API consumers by abstracting this as a relationship with just one attribute (type of the link). I wish JSON API allowed to do that.
Second one is some modification of audit-like example from #415. Suppose some endpoints of an API represent some committees, and other endpoints of that API represent people, who are members of these committees. People move from one committee to another over time, which can be reflected by joined_at / left_at timestamp attributes of the relationships. It would be easy to represent the history of each committee over time this way, showing when each member joined and when she left. I think it is a perfect abstraction if the API is only concerned with such superficial representation of the situation. If the API needs to deal with the particulars of the processes of joining / leaving of members, the API designer could opt for resources for them, which would allow him to represent details of running for membership, voting for it, etc. Is it a dissonance? I would say it is a reasonable freedom of expression, and I wish JSON API allowed it.
Last but not least, meta of relationships can be very useful for reporting computed data about them, e.g., some statistics, which can only be returned by GET, but is never stored by POST / PUT / PATCH.

@hhware Would you be willing to mock up a set of example requests/payloads showing how you'd accomplish your desired interaction within the constraints of json-api now, and a companion set within the constraints you are proposing?
I think it would be very helpful to see them side by side.

This change is additive and can be considered post 1.0. I'm going to pull it from the milestone.

@tkellen Definitely, I will.

@hhware Are you still willing to provide examples for this? If so, is there any chance you could do so this week? We are planning on doing a group review in the very near term and I would love to have them as a reference so we can consider this carefully.

Are you still willing to provide examples for this?

@tkellen, yes, I have been working on this PR and examples for the last few weeks, time permitting. I guess it's finally time to let it go :)
@dgeb, @tkellen, I very much appreciate your time and interest in reviewing my earlier posts on this topic. I reworked and significantly simplified this proposal to account for the discussion.
@lsylvester, I would appreciate your opinion on whether this satisfies your expectations wrt attributes of relationships.
Structure of this PR
This PR is split into several commits for convenience of reviewers:

the substance of the proposal,
terminology updates and formatting changes,
optional improvements (sparse fieldsets, sorting, meta).

The 4th commit is the example, it can be viewed in readable form here.
Key points
I think the PR now articulates the goals and limitations of the proposed changes much better than before. In particular, I would like to emphasize the following points:

The line between resources and relationships is much less blurred in this version compared to the previous one.
It was targeted at to-many relationships before, now it includes to-one relationships because it is more consistent. It does not seem to conflict with anything: e.g., if an API backed by RDBMS wants to provide to-one relationship with attributes, it can store them in a join table with appropriate UNIQUE indices.
The main difference between resources and "complex relationships" is that while resources can have their own types and can be referred to by type/id, relationships do not have their own type/id and cannot be referred to by them. I believe this is the reason why there should be no "dissonance": relationships can never compete with resources because they are only auxiliary entities, exactly the same as in the current spec.
Another difference between resources and relationships is that the latter cannot have links.
Answering the comment of @dgeb: there is simply no need to provide methods for updating attributes of relationships: if such attribute has to be changed, the corresponding relationship can be deleted and created from scratch, just like it is done in the current spec.
The only similarity between resources and relationships is that both allow arbitrary attribute members (and meta, in the optional part).
The spec is updated so that the word "attribute" is never used alone, it is always either "resource attribute" or "relationship attribute" (primarily in the terminology part).
Not sure whether there is any practical use in allowing complex attributes of relationships, but I think it is more consistent to keep limitations on attributes of resources and attributes of relationships identical.
Suggestions are made on incorporating relationship attributes into sparse fieldsets and sort requests. Suggestion on sorting  could have its merits even without relationship attributes. I will open a new issue on it if it does not go through as part of this PR.
For the purposes of pushing this PR forward, I tried to update as little as necessary. In particular, examples became less convincing after my changes, they should probably be replaced altogether.
In this PR, most of GET examples do not illustrate attributes of relationships, but the "complete example document with multiple included relationships" does. To the contrary, a good portion of POST/PATCH examples do illustrate them. The primary reason for this discrepancy is that there is no "complete example document" for POST/PATCH.
I expect that one common use case of this would be ordered relationships (touched in #473). In RDBMS setting, a to-many relationship can be stored with an additional column, e.g., order_number INT. Relationships in the spec have semantics of sets, so one way of addressing this question could be support of totally ordered sets, but then a mechanism to distinguish sets from totally ordered sets would be required. This will likely bring a lot of confusion since in most cases relationships are not ordered. Support for relationship attributes removes the issue: order can be explicitly communicated and sorting by it can be supported.

Milestoning
I am well aware that the official position is to postpone additive changes until post 1.0. While some additive changes are mere optimizations with available workarounds (e.g., #477), I think it would be appropriate to consider this one for 1.0 because it modifies one of the core concepts of the spec. If relationship attributes were proposed post 1.0 and then accepted, then obviosuly implementors of libraries would have to deal with them as with additive change. As @steveklabnik put: "I can appreciate frustration with changes, we are making them now, so that we can not make them in the future" -- I think it absolutely applies to the particular change proposed here.
Another reason to consider this now is that this change is additive for the JSON API spec and its generic implementations, but it will not be additive for specific JSON-API-compliant APIs which could make use of this feature. They will rarely be able to afford a luxury of switching from relationships-as-entities to relationships-with-attributes because it is a backward-incompatible change for an API. Implementors of such APIs make choices on API design and then stick to them. Even if this feature becomes availabe in JSON API 1.X, APIs implemented before that would not be able just to "add" it, the way the spec and libraries can. Obviously, some people are waiting for 1.0 to start using JSON API or to consider it "for real" because of stability expectations --  it is not unreasonable to expect that after 2 years of preparations for 1.0, the core concepts of the spec will remain stable for a while.
Commit "substance" is what I believe has to be considered for 1.0. Commit "terminology" would be useful in 1.0 too, but the main reason I provide it here is to avoid rejection of the proposal because of misunderstandings of terminology (the commits are non-overlapping though, so some terminology changes have leaked into other commits as well). Commit "optional" is not blocking for 1.0, but provided here to complete the picture.
Examples
Two alternatives to relationship attributes have been suggested in discussions in #415 and here:

make relationships heterogeneous, with value of type incorporating the attribute(s),
disguise relationships as resources.

After having a closer look, I realized that I do not even understand how the first option can be implemented.  But even if it could be, I think it is not a workable solution for the following reasons:

it pollutes type system with multitude of technical entities, creating complexity out of nowhere,
it is impractical for relationships with multiple attributes -- number of types will grow in geometrical progression,
it is impractical for relationships attributes which can be represented as ENUMs with large number of members for the same reason,
it is inapplicable to relationship attributes which cannot be represented as ENUMs, e.g., which have numeric values.

So I skip the first option and compare the second one to the proposed solution here. If these examples are unclear or need improvement, please let me know, so I could update them.
For completeness sake, other alternatives also exists: define an extension or simply handle these attributes within meta. However, these alternatives produce less portable APIs, which defeats the purpose of following JSON API spec.

@hhware For my purposes, I wanted to embed information about the linked resource without having to include the linked resource, so the information wasn't particular to the association.
The reason for this was to be able to invalidated locally cached resources.
I think for my use case, the best approach would be to allow for meta in the linkage objects, which is included in this PR, but I do not require the relation attributes which are the main feature of this PR.

Made a minor update, left a note in the message of the corresponding commit (to preserve PR structure).

In my opinion, this adds a lot of complexity for little benefit.

Ultimately, this is my thought as well. I've read through these tickets (sorry for the delay, work is getting tough) but I don't understand why relationships need attributes. As soon as they do, they become resources in their own right, and don't need special casing.

We sincerely appreciate your effort here, @hhware. However, after consideration and discussion, @tkellen, @steveklabnik, and myself share the belief that relationships with attributes should become resources in their own right. This has been a tough call as we struggle to balance complexity and utility.
An edge case we should consider is the allowance of meta on linkage objects, as you and @lsylvester have mentioned.
Thanks again for all your work, @hhware.

/reffing #794, as the extension system should make something like this possible


When will you update Angular2_CLI_Starter ?

Hi, I wonder that when will you update Angular2_CLI_Starter project.Thanks for your attention and your work

I'm working on some updates. I hope it will be ready after xmas.

Thank you for your attention

Updated