IndexError is not thrown

I found that IndexError was not thrown. Is it a part of intended design? Is there a pragma option to enable the exception?
a=[1,2,3]
print('a[10]=', a[10])

RESULT:
a[10]= None

Is there -luxury or -mostpythonic options available? I don't need fast speed  except a core engine. Transcrypt is already fast enough for me.
I think that it is a good policy to disable features downgrading performance, and provide options for programmers to apply locally instead. However, I hope that disabled features are supported by options as much as possible.  I think that compatibility to Python will extend target users available. There are a lot of Python users who want to use Python in web. Please don't tell me to choose other transcompilers if I need compatibility. I used Pyjs and Brython before. It was ok most cases, but I had to give up using them due to a slow core engine which is just small part of program.
I think that Transcypt's approach designing for speed and providing options for expensive features is the best way. I hope that I can build core engine with fast options, and build most other parts using expensive options.
Thanks a lot for providing this great program.

Look at the __pragma__ ('keycheck') it works for lists too.

I applied keycheck option. Uncaught exception is thrown instead of IndexError
#__pragma__ ('keycheck') # IndexError
a=[1,2,3]
print('a[10]=', a[10])

Result: Uncaught exception (line 3)

I tried to catch it, but it was not caught by IndexError as expected.
#__pragma__ ('keycheck') # IndexError
try:
    a=[1,2,3]
    print('a[10]=', a[10])
except IndexError:
    print('indexError')

RESULT:
Uncaught exception

It was caught if I didn't specify the exception type. However, how can I catch IndexError specifically?

I found that KeyError was thrown instead of IndexError.  In Python, IndexError is thrown in this case. Isn't it a bug to fix?
#__pragma__ ('keycheck') # IndexError
try:
    a=[1,2,3]
    print('a[10]=', a[10])
except IndexError:
    print('indexError')
except KeyError:
    print('KeyError')

RESULT:
KeyError

It was implemented only for dictionaries. In my fork I committed to throw IndexError on lists. But I don't know if it will be approved by Jacques.

It is definitively in now.


build(deps): bump golang.org/x/net from 0.10.0 to 0.17.0

Reason for Change:

Bumps golang.org/x/net from 0.10.0 to 0.17.0.
https://github.com/Azure/aks-engine-azurestack/pull/198
https://github.com/Azure/aks-engine-azurestack/pull/199
Issue Fixed:

Credit Where Due:
Does this change contain code from or inspired by another project?

[ ] No
[ ] Yes

If "Yes," did you notify that project's maintainers and provide attribution?

[ ] No
[ ] Yes

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Notes:

/azp run

The original PRs were successfully merged in:
https://github.com/Azure/aks-engine-azurestack/pull/198
https://github.com/Azure/aks-engine-azurestack/pull/199


[4.1][Improvement] CRUD fields  - allow devs to leave out "label"; correctly specify "for" attribute on label and input

if one forget to add the 'label' property of a field, an error is thrown when the field is rendered.
if the 'label' proberty is empty, a  tag is rendred - if the label is empty, there is no need to render the tag.
it is not possible to set the 'for' property of the tag

Hmm you're right @rabol , thank you:

I don't see a reason why we'd force devs to have the Label shown if they want to hide it;
The label's "for" attribute should be set automatically to the input ID (if specified) or to a random ID (if no ID was specified on the input);

Please mind that this needs to be done to all 50+ field type, so it might take a while. But I agree it's a good idea.
Cheers!


App rework

There were a few things that we were unhappy about how the app was previously created and organised. Following another example, we now have a new project app creation and organization which solves issues regarding SQLAlchemy sessions not being closed properly when testing with a Postgress DB causing the tests to never complete.

Pull Request Test Coverage Report for Build 26

303 of 311 (97.43%) changed or added relevant lines in 22 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 94.968%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

server/init.py
2
3
66.67%

server/resources/register.py
6
7
85.71%

server/resources/executions.py
5
8
62.5%

server/startup_validation.py
2
5
40.0%

Totals

Change from base Build 7:
0.03%

Covered Lines:
1642

Relevant Lines:
1729

💛  - Coveralls

Pull Request Test Coverage Report for Build 26

303 of 311 (97.43%) changed or added relevant lines in 22 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 94.968%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

server/init.py
2
3
66.67%

server/resources/register.py
6
7
85.71%

server/resources/executions.py
5
8
62.5%

server/startup_validation.py
2
5
40.0%

Totals

Change from base Build 7:
0.03%

Covered Lines:
1642

Relevant Lines:
1729

💛  - Coveralls

@louis-ver This PR presents quite a lot of changes in the way we setup the app and test it. Do not hesitate to hit me up if you want to discuss the changes directly.


Peer review - Milestone 4

Hi Team,
I've reviewed the system and made the following observations:

Jenkins is properly deploying on both deployments
Blue-Green deployments are working great
I was able to log in properly via Google OAuth and use functionality
Wiki needs to be updated in case of diagram and information for Open ID

Thanks,
Chetan

We have updated the wiki with information on Open ID and updated the architecture diagram with respect to the latest milestone.

Looks great!!


NSBlog sort of went away

NSBlog (https://www.mikeash.com/pyblog/) articles are no longer appear in NNW (Version 5.0.3 (2618)).
Last night my iMac updated to 10.15.4 and restarted.  This morning all the NSBlog articles are missing.  NSBlog is still subscribed but the articles are not showing.  The NSBlog website is still up and running.
It might be a NNW problem.  It might be a NSBlog problem.  But it occurred when my Mac updated  to 10.15.4, which makes me think this is a problem with NNW caused by the update.

Are you using the On My Mac account or Feedbin?

On My Mac account
Regards, Michael
Michael M. Mayer
Minneapolis, MN
<EMAIL_ADDRESS>
On Apr 17, 2020, at 9:20 AM, Maurice Parker<EMAIL_ADDRESS>wrote:
Are you using the On My Mac account or Feedbin?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Ranchero-Software/NetNewsWire/issues/1991#issuecomment-615271378, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOQOK4TMW6RCP3Y6B2G3XLRNBQR3ANCNFSM4MKY2M7A.

I'm able to add the blog in NNW 5.0.3 to the On My Mac account.  I wonder if the feed URL changed on it.
When you look at the Feed Inspector (using cmd-I) do you see the URL as http://www.mikeash.com/pyblog/rss.py?

Yes I do (without the question mark at the end).
Regards, Michael
Michael M. Mayer
Minneapolis, MN
<EMAIL_ADDRESS>
On Apr 17, 2020, at 9:24 AM, Maurice Parker<EMAIL_ADDRESS>wrote:
When you look at the Feed Inspector (using cmd-I) do you see the URL as http://www.mikeash.com/pyblog/rss.py http://www.mikeash.com/pyblog/rss.py?? http://www.mikeash.com/pyblog/rss.py?

I honestly don't know what is happening with this particular feed.  Could you try deleting it and adding it again?  I hate to use the nuclear option, but I'm not sure what is going on.

I tried that and no change.  It subscribes but the articles don’t show.
Regards, Michael
Michael M. Mayer
Minneapolis, MN
<EMAIL_ADDRESS>
On Apr 17, 2020, at 9:35 AM, Maurice Parker<EMAIL_ADDRESS>wrote:
I honestly don't know what is happening with this particular feed. Could you try deleting it and adding it again? I hate to use the nuclear option, but I'm not sure what is going on.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Ranchero-Software/NetNewsWire/issues/1991#issuecomment-615279659, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOQOK2NBBFPT4ALZT7D6JDRNBSLVANCNFSM4MKY2M7A.

I'm sorry that you are having these problems and thanks for hanging in there with me.
Could you please try something to help us track down the problem? Create a new On My Mac account and try adding the feed to that and let me know what happens?

I created a new On My Mac account and added NSBlog to that and it worked.  The articles show up in that account.
Regards, Michael
Michael M. Mayer
Minneapolis, MN
<EMAIL_ADDRESS>
On Apr 17, 2020, at 10:07 AM, Maurice Parker<EMAIL_ADDRESS>wrote:
I'm sorry that you are having these problems and thanks for hanging in there with me.
Could you please try something to help us track down the problem? Create a new On My Mac account and try adding the feed to that and let me know what happens?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Ranchero-Software/NetNewsWire/issues/1991#issuecomment-615297717, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOQOK2DJ5TBV2O3W4GBDT3RNBWEBANCNFSM4MKY2M7A.

I know what this is. It’s not a bug, exactly, but we will be changing the behavior in 5.0.4 so that this doesn’t happen.
NetNewsWire has a 90-day article retention policy. (The clock starts when the app sees the article — which is not necessarily the publication date.)
In 5.0.4, we’ll change that policy so that NetNewsWire always shows the contents of the feed. As long as an article is still in the feed, it will still be in NetNewsWire.
(Exception: starred articles stay forever.)

I’m actually working on this particular change right now. The code will first appear in NetNewsWire 5.0.1 for iOS, and then we’ll do 5.0.4 for Mac.

Brent -
Thank you so much for the response.  I guess the macOS update to 10.15.4 was a bit of a red herring other than it caused the app to quit and restart or maybe just coincided with me setting this up 90 days ago?
Regards, Michael
Michael M. Mayer
Minneapolis, MN
<EMAIL_ADDRESS>
On Apr 17, 2020, at 11:59 AM, Brent Simmons<EMAIL_ADDRESS>wrote:
I’m actually working on this particular change right now. The code will first appear in NetNewsWire 5.0.1 for iOS, and then we’ll do 5.0.4 for Mac.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Ranchero-Software/NetNewsWire/issues/1991#issuecomment-615357064, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOQOK2CL6M6MSJTRMXYGBLRNCDGNANCNFSM4MKY2M7A.

It was the quitting and restarting. The 90-day policy cutoff date is determined at launch time and not updated until the next launch. (Which means 90 days could become 91, 100, 200 — as long as NNW is never quit and restarted.)

This will be fixed by the retention policy change coming in 5.0.4.


Fix issue 211

This pull request is for fixing issue #211.

Coverage remained the same at 58.496% when pulling 3ed43b25390deb73838ca8757518388abb34e324 on brchiu:fix_vlm_issue_211 into f58f1fccee847eaee141004b70e38d91196ca267 on vlm:master.


Test LIO-SAM on the real robot

Progress update:
Issue #1: Image projection node keeps restarting: I found that the point cloud data that in coming from gazebo velodyne plugin does not follow the point cloud data stander, in which if the cloud.height = 1, it means the datasets are unorganized, but for some reason the data that comes from velodyne plugin is the other way around! where the cloud.width was equal to 1 and that was causing a segmentation fault in PCL.
To fix this issue I had just simply to swap the height and width data.
Issue #2: Large velocity, reset IMU-preintegration: the scanned frames keeps jumping in random directions, I believe this issue is due to IMU calibration. The authors of LIO_SAM provides an external algorithm to do the calibration process, I tested it and the extrinsicRot was identity matrix, I think that make sense because the IMU gazebo plugin follows ros 105.
It still did not work as expected and more investigation need to be done!

Hi @ibrahimhroob , we’re you able to get some results ?
I was also doing some tests with LIO-SAM recently. Are you purely running it in Gazebo or real data?
I tried with live sensor data and ros bags. With ros bags I also had issues because of frame dropping.
But when I used live sensor data I was able to get reasonable maps. My setup had Ouster-64 Lidar and a Xsens mti-30 IMU.
I could share some visuals from the results if you want to see.

Hi @jediofgever, yeah I was able to get some results on both gazebo and the real data. I did not notice the frame dropping issue but can you please share the results? have you tried only to play the imu and lidar topics from the bag? that may help especially if too many topics were recorded.

Hi, perhaps our aim and use case of LIO-SAM is  a bit different but still might be useful.
For example this is the area that I like to build the map;

A similar perspective of acquired map the is;

Green points are trajectory estimation
. There is an issue of dynamic objects being registered to map with LIOSAM. Is that causing any trouble to you as well ?
I mainly need SLAM because I need dense maps that I use for uneven terrain navigation.
Are you also making use of created maps or you mainly need it for odometery estimation ?
My finding is that, VSLAM approaches are working OK for odometry estimation but they are quite bad for building high quality dense maps. From your experience does any methods build better quality maps(less noise and less dynamic object registration)?

LIOSAM does a good job but it must be noted that I have an supplementary RTK GPS
Here is how LIOSAM odometry compares to pure RTK

The main issue with LIOSAM it does not understand the environment so it can not filter the dynamic objects. For my use case I was using it only for odometry estimation and my tests were done mainly in static environment.
The results you got are really good, have you passed the GNSS topic to LIOSAM? or the odometry estimation was based only on lidar and IMU?
There as another algorithm that can filter dynamic objects that is SuMa++ but it is mainly targeted for autonomous vehicle applications since it has a NN that was trained to semantically segment objects on kitti data-set.
Regarding VSLAM approach, which SLAM algorithm did you used? what perception system the algorithm used?

have you passed the GNSS topic to LIOSAM?

yes, I did not try without GNSS yet so I am not sure how it will perform without that gold quality RTK signals. My setup had  Ouster-64 LIDAR and Xsens IMU. Pricey toys. Yes that actually might help removing some of the object such as pedestrians, I should give it a try I think Thanks , Ibrahim.
I used OpenVSLAM ,  in simulation it does perform really good, in real just OK and thats only for odometry estimation.
It might be good to see some results from simulation results of OpenVSLAM in case you wonder ; https://vox-nav.readthedocs.io/en/latest/openvslam/index.html

Yeah that is very expensive setup.
I was aware of OpenVSLAM system, but I did not use it since it was heavily based on ORB-SLAM2 and it has been terminated by the authors.
I would recommend to try RTAB-MAP if you have not tried it already, the system is hugely configurable, where it is possible to use laser scanners for odometry estimation and the visual inputs to create a dense map.
There is another system I came cross but did not try it yet that is Kimera


Missing font files on cdnjs (v0.97.6)

Using the getting started template with cdnjs links causes multiple 404 errors for font files.
the path should be /font and not /fonts
e.g. cdnjs.cloudflare.com/ajax/libs/materialize/0.97.6/fonts/roboto/Roboto-Regular.woff2

Same here (hate to do a +1 comment, but it bites me :) )

In the changelog of April the 1st they mentioned the changement in font path. I think they just missed the cdn.

I totally agree with you. But lately the issues fixing and pull merging aren't ... let says regular ;)
That's sad because the community is growing fast and the project is really nice!

This issue has been resolved as they are now hosted at the right path on CDNJS :smile:


tsm: snapshots leak and data may disappear on restart if a compaction fails due transient write errors

This issue is based on a code review, rather than something I have seen in the wild. If my analysis is incorrect, then feel free to close the issue.
It seems to me that if the periodic snapshotting and compaction fails (perhaps because of a temporary shortage of disk space on the database's file system) a snapshot will be retained in memory and never be released. If such transient disk space shortages were to occur regularly, "abandoned" snapshots could accumulate in memory, eventually resulting in an OOM condition.
A fix might be to handle this case by registering the snapshot associated with a failed compaction in the cache and then when Cache.ClearSnapshot runs after the next successful compaction, clearing these snapshots as well.

As noted in the pull request, currently if a snapshot isn't written properly on the first attempt, the contents will never make it into TSM files unless the server is restarted prior to the next successful compaction attempt. The problem here is that writes into TSM files always occur directly out of the snapshot and never from the WAL segment and currently, the snapshot write is tried at most once. If the write error that caused the snapshot write to fail is transient, then the next successful write attempt will result in all the current WAL segments being deleted from disk. The data will still appear to be in the database (because it is still in the cache) but on subsequent restart, the data will no longer be accessible.
The proposed series fixes this issue by retrying (on each compaction cycle) failed snapshot writes (in order) until they succeed.

@jonseymour I think you are right that there is a possibility of a leak/wal segment getting lost due to the way wal segments are removed.  I need to take a closer look at the code and this change though.

@jwilder - this shows how the new cache statistics from #5499 can be used to detect leaking snapshots due to transient write errors. In this case, I caused them by removing write permissions from the shard's TSM directory.


Better bracket highlight visibility

From UserVoice (600 votes)
The bracket highlight is too dim to easily see with most themes. In Notepad++ the brackets change color and become bold, i think that is much easier to see. Highlighting the "current bracket set" would also be really nice.
I understand the themes can be changed in a convoluted way. For such an important feature i think the feature should be default or easily accessible.

We do offer bracket highlighting:

We also have indent guides which should help a lot here.
There are some good extensions e.g. Rainbow Brackets.
https://marketplace.visualstudio.com/items?itemName=2gua.rainbow-brackets

@seanmcbreen the request is to improve the visibility of bracket highlighting. OP's opinion was its too dim.

I'm looking for this feature. Do we have that ? https://github.com/facelessuser/BracketHighlighter

@jitendravyas That's odd, both my light theme and dark theme are not showing the same problem as your second screenshot.
Our bracket matching works when your caret is on a tag.  However, if you select the text of the tag, then it can be confusing because in addition it will highlight all text that matches the selection.  However, we will be improving color contrast to improve that scenario.

How to change tag highlight background and foreground color?

HTML tag matching works in my theme, highlighting matching tags, when there are no JSX javascript expressions within the tags. However, tag highlighting works erratically when there are JSX javascript expressions within 2 enclosing HTML tags.
Works as intended:

Doesn't work:

@vvatikiotis thanks for reporting that.  Since it's a different issue than being discussed here, I created a new issue for you.

may i asked this problem has resolved？ i haven't find the extension like this :https://github.com/facelessuser/BracketHighlighter

@jitendravyas
What theme is this ?

Can be done via our theming work now:

I am sorry, but configuring the background or the border does not help in that case. We'd need something like "editorBracketMatch.border": "bottom #ff00ff".
See e.g. https://github.com/Microsoft/vscode/issues/23606 and https://github.com/Microsoft/vscode/issues/19534 (which was said to be tracked here).

And fontColor please

Hi,
It's the same problem with me.. I'm looking for some tweaks for match brackets in VS Code and I came across searching this one..
Subtle Brackets
It's working to me with the latest VS Code 1.16.1!


Fix systemjs-angular-loader.js for external templates (#444)

these code changes are based on code found in the angular docs component with external testing downloadable example.
Although the refactoring I described in #444 seems pretty simple enough to understand, In my fork  you can see branches demonstrate-bug-444 & demonstrate-fix-444 for more context of this bug and how this fix it.
I'm assuming because this code came from elsewhere in angular help/tutorial that it's okay.. but as a sidenote, the "indexof('moduleId')" seems rather poor because if you've got the word "moduleId" anywhere (for example, in a line of sourcecode you just commented out) it, the module fails to load the template.  Not sure what the better solution would be, just my $0.02

I signed it!

Thanks. I am responsible for the changes but I forgot to update  it here.
Yes, the indexOf is not the best solution, but does the trick for now.


Get ExternalBearerTokenConfiguration working

see my comment on #181  - I can confirm that this works, provided the authority is correctly set, the claimtypemapping is cleared and cors is configured.

Ok, thanks for the feedback.

Hi brockallen,
Not sure if you are still active on the project... However i had some extensive debugging sessions with IdentityServer + IdentityManager combination and would be glad to contribute in future
First things first: RestAPI with bearer token authentication doesn't work in latest version. Not sure how other guys forced it to work, but there is an issue with IdentityManager code (at least as i see it, correct me if i am wrong):
config.SuppressDefaultHostAuthentication();
call in webApiConfig removes all previously configured authentication means including bearer token. If there is a plan to expose RESTApi for external use, exclusion for bearer token should be added:
config.Filters.Add(new HostAuthenticationFilter("Bearer"));
this should solve 401 problem.  Currently i removed suppression completely and API auth works.


The connector cannot be run locally when following the README instructions.

Following the README instructions to run the connector does not work.
When running the following commands:
./gradlew :launchers:basic:shadowJar
java -jar launchers/basic/build/libs/dataspaceconnector-basic.jar

We get the following error:
SEVERE 2021-10-26T10:42:41.734764 Error booting runtime
org.eclipse.dataspaceconnector.spi.EdcException: Extension feature required by org.eclipse.dataspaceconnector.contract.ContractServiceExtension not found: edc:asset:assetindex
	at org.eclipse.dataspaceconnector.system.DefaultServiceExtensionContext.lambda$sortExtensions$8(DefaultServiceExtensionContext.java:168)
	at java.base/java.lang.Iterable.forEach(Iterable.java:75)
	at org.eclipse.dataspaceconnector.system.DefaultServiceExtensionContext.lambda$sortExtensions$9(DefaultServiceExtensionContext.java:165)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
	at org.eclipse.dataspaceconnector.system.DefaultServiceExtensionContext.sortExtensions(DefaultServiceExtensionContext.java:165)
	at org.eclipse.dataspaceconnector.system.DefaultServiceExtensionContext.loadServiceExtensions(DefaultServiceExtensionContext.java:136)
	at org.eclipse.dataspaceconnector.system.runtime.BaseRuntime.createExtensions(BaseRuntime.java:119)
	at org.eclipse.dataspaceconnector.system.runtime.BaseRuntime.boot(BaseRuntime.java:62)
	at org.eclipse.dataspaceconnector.system.runtime.BaseRuntime.main(BaseRuntime.java:41)

We do need workings samples ASAP, I'll open another Issue that fixes that and also adds sanity checks that build and run the samples on the CI pipeline.

@paullatzelsperger has this been resolved?

I think this was fixed by #201


Does is support the VM with 'SpanVolume', 'raid0', 'Stripe-Disk' ???

Hello, please consider to add about availability of VM with 'SpanVolume', 'Raid0', 'Striped Disk'
Which are technically merged/combined disk.

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

ID: 88beaa58-adf5-28ef-5510-01ace6923eef
Version Independent ID: 02b2de6f-ba0a-d9dc-fd4f-c0c4d3a46107
Content: Frequently asked questions about backing up Azure VMs with Azure Backup
Content Source: articles/backup/backup-azure-vm-backup-faq.md
Service: backup
GitHub Login: @Sogup
Microsoft Alias: sogup

@KeiroKamioka0000 Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

@KeiroKamioka0000 Hi, this seems like a request for a feature rather than doc feedback. If so please leave the request at https://feedback.azure.com/forums/258995-azure-backup.
If this isn't a request, please provide a few more details about the question. Thx!
#please-close


showDialog() without footer possible?

Hi Masashi,
is it possible to have the map fullscreen without the footer?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9875160-showdialog-without-footer-possible?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github).

There is no option for that, and I don't have the plan for that.


command line interface

Would this be useful? Maybe output CSV or JSON, to you could pipe right into CSVKit?

Thinking this through a little more, it might be better to make a separate CLI package that builds on this. If we start depending on things like Click and Agate and whatever else, that could get harry to manage.


Documentation difficult to read (dark mode)

Feedback
Hello,
Regarding the new documentation pages, I have found that they can be somewhat difficult to read, especially in dark mode. My main issue is being able to quickly tell where one method starts and the next method begins.
Example page:

I'm no design expert but I think the pages could use more headers or colors.
Slack thread
Other comments

The methods don't appear in the right sidebar
It's not clear what scope some lines are supposed to be under, e.g. in above "Pulse scheduling method" looks like it is under Return type but maybe also is a header for the next set of methods.
The black highlighting on dark gray backwards is too hard to see.
More variations of font sizes, separator lines, indentation, etc?

Thanks for this feedback! We are currently investigating ways to improve the layout of the API pages and hope to be able to start making improvements soon. We're aware this is a bad UI currently so we're prioritising this work highly

1, 2, and 4 should now be addressed :) Please let us know if you have further suggestions to improve things!
@gracelindsell is going to look into 3 about the highlighting of inline code.

@Eric-Arellano looks like the inline highlighting is currently set to Cool Gray 100, RGB 18,22,25. we should change that to Accessibility/Black, RGB 0,0,0. this will help create more of an inverse highlight.

Thanks again, @evmckinney9, for the feedback! We've rolled out a few improvements since you opened this:

inline code now has a border around it on dark mode, which improves contrast
code blocks have larger font
code blocks comments use a different color for better contrast
the API docs were overall redesigned to use colored bars to better show where distinct methods/functions/classes/attributes are

We have two more planned improvements for API docs:

https://github.com/Qiskit/documentation/issues/1361
https://github.com/Qiskit/documentation/issues/1395

Please let us know if you have any other feedback or suggestions on how to make the docs more useful. Your feedback was extremely useful and prompted the first chaneg of adding a border to inline code on dark mode.


Check service name whether exists

When up/start.... a service which is not exist in yml, libcompose will hang there.
This PR fix this.
Output:
[root@localhost sleep]# libcompose up no_exist
WARN[0000] Note: This is an experimental alternate implementation of the Compose CLI (https://github.com/docker/compose)
FATA[0000] No such service: no_exist

Signed-off-by: Bo Hai<EMAIL_ADDRESS>

ping @aanand @aduermael @ibuildthecloud @gdevillele

@bohai cool, thanks :stuck_out_tongue:.
Could you add an integration test too ? :blush:

@bohai Change looks good, just needs an integration test

@vdemeester  @ibuildthecloud
OK.I will add integration test later.

Ohh I missed the integration test.. :sweat:
@bohai could you squash your commits ?
Other than that, LGTM 🐼

@vdemeester
Squashed and review again. Thanks

@bohai needs a rebase :sweat:

ping @vdemeester
I have rebase the code.

/ping @ibuildthecloud


Virtualization Problem

When scrolling, the cells only display the first Item in the RowsSource
I use a BindableCollection<BindableCollection> as RowsSource.
If I set EnableRowVirtualization="False" the problem disappears, but of course the memory consumption is tremendous.

Thanks for reporting, do you have any ideas for how to solve this?
I wrote this lib mostly for small matrices.

I don't really know how virtualization works. My guess is the bindings are not being applied properly because the datagrid assumes that only one DataContext is applied for each row hence every column have the same values as the first row. Maybe the DataGrid.UnloadingRow and LoadringRow event can be used to update the columns. I haven't exactly studied how you implemented the RowsSource yet so it's all theory.
I'm using this for a time based distribution of values. Surprisingly, it works well even for larger datasets (300cols x 30rows). But with virtualization disabled, it consumes around 450mb.

Can be solved now, interested in feedback.

@barnstws have you had time to check if it got better/worse? There is a nuget package now


[WIP] feat: Add native SourceMap support

Ref https://github.com/denoland/deno/issues/4499
Ref https://github.com/denoland/deno/issues/21988

sourceMapURL being a "bare" url (like bar.js.map) is currently not handled properly by any loader.
I think I'm gonna change ModuleLoader::get_source_map to be two separate functions:

ModuleLoader::get_source_map_for_file() - last ditch effort to get a source map for particular file_name - this is mechanism deno CLI uses right now, by stripping out sourceMapURL before passing source code to V8
ModuleLoader::load_source_map(file_name: &str) - given a resolved URL synchronously return a source map file. Given that most often the URL in sourceMapURL is actually not a relative URL (eg. bar.js.map) a bit of logic is required in SourceMapper to append ./ to that value and trying to resolve it again. I'm still thinking how to handle it best.

sourceMapURL being a "bare" url (like bar.js.map) is currently not handled properly by any loader.

I think we have that in Preact. We've gotten reports for a while that the source maps don't load (outside of Deno) and this could explain why. I didn't know that the paths were expected to begin with ./ 👀

sourceMapURL being a "bare" url (like bar.js.map) is currently not handled properly by any loader.

I think we have that in Preact. We've gotten reports for a while that the source maps don't load (outside of Deno) and this could explain why. I didn't know that the paths were expected to begin with ./ 👀

I don't think it's expected to being with ./ - most tools put ULR like bar.js.map there. What I meant be my comment is that our loaders need to be updated to handle such "url". Basically if the parsing fails, we should prepend ./ and try to resolve it against the file that url is in.


chorm: remove runtime mod yaml::yaml

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

re #812

2. What is the scope of this PR (e.g. component or file name):

/kclvm/runtime
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other
remove runtime mod yaml::yaml

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[x] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
471 unchanged lines in 8 files lost coverage.
Overall coverage decreased (-17.3%) to 70.535%

Files with Coverage Reduction
New Missed Lines
%

compiler_base/error/src/diagnostic/components.rs
6
0.0%

compiler_base/error/src/errors.rs
8
0.0%

compiler_base/session/src/lib.rs
26
58.06%

compiler_base/error/src/diagnostic/mod.rs
27
0.0%

compiler_base/error/src/diagnostic/style.rs
41
0.0%

compiler_base/error/src/diagnostic/diagnostic_message.rs
74
0.0%

compiler_base/error/src/emitter.rs
119
0.0%

compiler_base/error/src/diagnostic/diagnostic_handler.rs
170
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-17.3%

Covered Lines:
38840

Relevant Lines:
55065

💛  - Coveralls


Updated readme with a few bits

Where we've wrapped examples in jQuery(document).ready it would be good to use the vanilla JS instead (or just leave out in the code the fact that the DOM must be loaded before event listeners can be attached, a note could be added but we probably don't need it in every code snippet).

In regards to the jQuery(document).ready If we want to be idiot proof i guess we need to get rid of the obvious mistakes, when someone who doesnt fully understand the code while copy pasting it into a html page and just assumes that this will just work as is, this will come up. But yeah if you want we can have a note saying this.

Had another thought, someone could be using something other than jQuery, this doesnt apply, will just put a not on these snippets that the element should be loaded prior to the call being made.

For the code examples I'd probably go for this style:
document
  .querySelector('#my-selector')
  .addEventListener('hover', function myListener() {

  });

rather than:
document
.querySelector('#my-selector')
.addEventListener('hover', function myListener() {

});


Next monkeys preparations

Cleanups and preparation for 3.4.1 twelvemonkeys library. Still usable with 3.3.2 twelvemonkeys libraries

Codecov Report

Merging #4 into master will increase coverage by <.01%.
The diff coverage is 51.42%.

@@             Coverage Diff              @@
##             master       #4      +/-   ##
============================================
+ Coverage     76.88%   76.89%   +<.01%
  Complexity      225      225
============================================
  Files            40       40
  Lines          1207     1216       +9
  Branches        124      124
============================================
+ Hits            928      935       +7
- Misses          195      197       +2
  Partials         84       84

Impacted Files
Coverage Δ
Complexity Δ

...ns/turbojpeg/imageio/TurboJpegImageWriteParam.java
75% <100%> (+8.33%)
2 <1> (ø)
:arrow_down:

...ctions/turbojpeg/imageio/TurboJpegImageWriter.java
56.25% <100%> (ø)
6 <1> (ø)
:arrow_down:

...ons/turbojpeg/imageio/TurboJpegImageReadParam.java
66.66% <100%> (ø)
3 <1> (ø)
:arrow_down:

...ctions/turbojpeg/imageio/TurboJpegImageReader.java
76.33% <33.33%> (-1.19%)
36 <0> (ø)

...ava/de/digitalcollections/turbojpeg/TurboJpeg.java
70.13% <50%> (+1.29%)
18 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


added sign feature (optional) in is.sorted

Refer #220

Will update README in later PR

I think this needs another cleanup pass.

@jdalton, in test file or the code.?

In the test file. You can see there are a couple of orphan comments.

Ok, I just saw there were absolutely no comments in test file. Anyways there was no feature like this earlier as well (default behaviour and extended behaviour) hence I kept those comments.

You're missing the point. I'll merge and then show you.

Best option :stuck_out_tongue: , I'll learn from that and will take care later on


Open Obsidoom

Added Command to open new Obsidoom Sidepanel in main.ts

Cool Idea, thank you for implementing it!

@JVormstein I built the plugin with your new code, but it does not work. I can run the command you added, but nothing happens


Unable to import pinject

Hello,
I decided to give pinject a try, but unfortunately it does not import. Here's what I do: install pinject with pip install pinject and then interactively import pinject.
It seem to fail on line 156 of third_party/decorator.py. I'm on python 3.4 so maybe that's the reason although looking at code I can see blocks dealing with python >3.2
Is that a bug?

Still getting this issue:
SyntaxError: Missing parentheses in call to 'exec'

at pinject/third_party/decorator.py", line 156

@AlexKovalevych, what is your Python version? Are you using the patched revision?

@trein  its 3.4.2. no, i don't think so, i've installed the master branch

@AlexKovalevych so the master branch does not have support for Python 3. I submitted a fix for this, but it hasn't been merged yet. If you want, you can cherry-pick it: https://github.com/trein/pinject/commit/fd091eb2237547f921f7ada531e16b95ba6693b8

@trein understood, weird its not being merged yet, thank you for response

+1 Is there anyone here?
Please merge the PRs to fix the issues, esp: Python 3 Support.
Thanks!

@zixia heya! i don't think there is, but apparently it is quite easy to implement a di solution yourself - took me about 2 hours to write my own injector/container with tests and all

Thanks! I'll go to take a look. It seems you did a great job!
However, I'm a newbie of Python, I'm familiar with DI & Angular but I'd like to use an out-of-box DI solution in python.
I love this pinject because it's decorator free! :+1:


IE11 Paragraph and shift+Enter bug

Hi,
I'm using Trumbowyg in a couple of my projects. Really like it so far. Today I discovered a weird bug in Internet Explorer 11. I thought it was a bug in my project, so I tested it on the demo-page of Trumbowyg, and got the same result.
How to reproduce the bug?

Type something in the editor on: http://alex-d.github.io/Trumbowyg/ using IE11 on Windows platform.
Press 'Enter'
The cursor jumps to the next paragraph, and immediately jumps back up. When you start to type the text does start on the new paragraph. (but this is weird behaviour).
When you use Shift + Enter to make a line-break the editor makes a new paragraph (this is a bug).
When you type a couple of Enters after each other, the cursor keeps jumping back up.

Informations
Browser: IE11
OS: Windows 8

I know. But it's IE... some stranges/weird behaviours are from IE itself :/

When you type a couple of Enters

I don't want cover this use case, that I judge non-semantic.

So this won't be fixed? It's quite a breaking bug right now for the project I'm using it in. Please let me know if this will be on the buglist, otherwise I need to look for an alternative plugin. Thanks!

Idk how to fix it. So you can check another WYSIWYG... :/

Too bad, thanks for your effort though :+1:
Will try to find an alternative. Issue can be closed.

Even though, this issue is already closed, i want to make some notes about it.
The cause of the problem is the following code fragment:
// Remove empty

t.$ed.find('p:empty').remove();

In Chrome, the css selector p:empty doesn't select a
 tag with a
 tag inside, but in IE it does. To prevent trumbowyg from deleting
 tags with a
 tag inside also for IE, the code could rewritten like this:
// Remove empty

t.$ed.find('p:empty').each(function () {
  var p = $(this);
  if (p.html() !== '
') {
    p.remove();
  }
});

I noticed the following. If you don't use the semantic version, this bug doesn't appear.
semantic: false,
Hope this helps you


Fixes to search_data_catalogs

Pull Request Checklist:

[x] pre-commit hooks are installed/active in my local clone ($ pre-commit install)
[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #42
This PR fixes #81

[x] (If applicable) Documentation has been added / updated (for bug fixes / features)
[x] If a merge request has been made in parallel to this PR in xscen-notebooks, it is merged and the submodules have been updated.
[ ] HISTORY.rst has been updated (with summary of main changes)

[ ] Link to issue (:issue:number) and pull request (:pull:number) has been added

What kind of change does this PR introduce?

search_data_catalogs no longer crashes if it finds nothing. It now returns an empty dictionary and a warning.
_dispatch_historical_to_future no longer duplicates fixed fields if they exist in both periods.

Does this PR introduce a breaking change?
Other information:

Question:
I have 3 members for the same model: 'r1i1p1f1_NorESM2-MM_gn_NCC', 'r2i1p1f1_NorESM2-MM_gn_NCC', and  'r3i1p1f1_NorESM2-MM_gn_NCC'. For some reason, r1, r2, and r3 all have orog and areacella, but only r2 has sftlf.
Should we provide an option to broadcast fixed fields to other members or is that too dangerous?

Should we provide an option to broadcast fixed fields to other members or is that too dangerous?

I can say that for CORDEX-related datasets, this is how the fixed field data is presented between experiment runs. If you feel it's dangerous, you could add warnings when this is being assumed.


[FR] Restore previous input

When using shortcut keys to open the input box, restore the last search word entered and select.

Thank you for your FR, @doit132 :)

@doit132
Released it in v11.0.0-beat1 🚀
If you use BRAT, I would appreciate it if you could check it out before the official release.

@doit132
Released in v11.0.0 🚀


Call composite layout looks different on different users

@picorel can you please share more about the scenario you are seeing here? What would you have expected and what are you seeing today? We would love to be able to support you but we need more information here to be able to support you and others.

Closed due to inactivity.


workflows: Upload results from encodings generation

The output directory will contain both the generated encodings and the associated logs, all useful to debug issues.

@harishankarv This pull request uploads the results of the two CI workflows. You can see them on the workflow pages, under Artifacts.
If you check the one for LLVM-to-SMT (bpf_encodings-5.9-BPF_AND.zip for example), there are a bunch of files for various instructions at the root of the bpf_encodings/5.9/ directory (the directory that is zipped). Any idea why? I expected to find stuff only under bpf_encodings/5.9/BPF_AND/.

@pchaigno thanks for setting this up!

there are a bunch of files for various instructions at the root of the bpf_encodings/5.9/ directory (the directory that is zipped)
If I understand correctly, you're talking about why there is BPF_OR.smt2, BPF_XOR.smt2 within the 5.9 directory? I checked, and this is not the case for the 6.8 directory: that only contains BPF_AND.smt2. I'm not sure where these extra files are coming from.

It seems this is not the case for the 6.8 directory: that only contains BPF_AND.smt2, right?

Uh, you're right. Even weirder :sweat_smile:
Anyway, let's ignore this for now to make progress. I'll upload just the subdir and will mark this PR ready for review.

If I understand correctly, you're talking about why there is BPF_OR.smt2, BPF_XOR.smt2 within the 5.9 directory? I'm not sure where these extra files are coming from.

@harishankarv It seems they are coming from this code: https://github.com/bpfverif/agni/blob/67a2eb673b08ae29e0b8a8a6e69259a2ae203205/llvm-to-smt/run_llvm_passes.py#L257-L259
Do you remember the reason for this?

This was done simply because  the verification bpf_alu_jmp_synthesis.py required all the encodings in one directory. After generating the encodings within the op directory e.g. outdir/BPF_AND/BPF_AND.smt2, the encoding is copied to parent directory, i.e. the main outdir. That way all the encodings BPF_AND.smt2, BPF_OR.smt2 would lie in the same directory.
If you do not plan to run bpf_alu_jmp_synthesis.py on the generated encodings, then copy_encoding_to_parent_dir() shouldn't matter.

Re: https://github.com/bpfverif/agni/actions/runs/9918518732
What I am wondering is where did the encodings for other ops  come from in the first place, to be copied into the parent directory copy from? You ran generate_encodings.py with --specific-op BPF_AND. That means there should have only been a BPF_AND directory created, and encoding for BPF_AND.smt2, which should have been copied into the parent directory.
Also strange that the 6.8 artifact does not contain the other op encodings as I pointed out before.

Regardless, I believe we can address this if needed. This would be needed only if we plan to run bpf_alu_jmp_synthesis.py on generated encodings.

We can have bpf_alu_jmp_synthesis.py accept encodings from within op subdirectories. @mshachnai
Copy the encodings into a separate directory say, outdir/bpf_encodings which  bpf_alu_jmp_synthesis.py can then read from:
--encodings_path outdir/bpf-encodings/

Why do we need the subdirectories and their content? If it's only for debugging, could we put it behind a flag?


Merge is failing

Description
Merge is failing.
Steps to reproduce
https://github.com/fcitx/mozc/compare/fcitx...google:mozc:master
Sorry for bothering you.

Thanks wengxt! :-)


Document per-container termination message limits

Ref https://github.com/tektoncd/pipeline/issues/4808
cc @vdemeester

/sig node

@kubernetes/sig-node-pr-reviews : Please can you sign this off from a tech perspective?

@kubernetes/sig-node-pr-reviews Looking for your sign-off, thanks!

I've requested review from SIG Node on Slack: https://kubernetes.slack.com/archives/C0BP8PW9G/p1655184285164589
I've also raised the issue about long delays for SIG Node reviews in SIG Docs Slack: https://kubernetes.slack.com/archives/C1J0BPD2M/p1655184616750419

Hey @imjasonh , please would you be able to address the nit? We could go ahead with merging after that :)


Feature: Adding a reset button for book donation form

Feature description
The reset button , if added, will clear all the previous data entered in the donation form so that a new entry can be made quickly.
I can do this, please assign me this issue.
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

can i work on this issue ?

@ankeeta-ahire you have been assigned this issue. You can start working.


Config lock

Add config lock that only allows the "load" method to change it, once all the parameters are set

Allow any variable to be set once and only updated by "load" methods


Website: broken link to developer instructions

The "developer instructions" link (from the About page of the Param website) refers to a page in a non-existant domain (https://param.org/).

This has been fixed in master and will appear when the website is re-built with the next release.


GenerateName not handled

Looking at the code for TemplateChart, InstallChart, UpgradeChart or InstallOrUpgradeChart, I do not see any code that handles ReleaseName == "" && GenerateName="true".
Something like this worked for me;

// TemplateChart returns a rendered version of the provided ChartSpec 'spec' by performing a "dry-run" install.
func (c *HelmClient) TemplateChart(spec *ChartSpec) ([]byte, error) {
	client := action.NewInstall(c.ActionConfig)
	mergeInstallOptions(spec, client)

	client.DryRun = true
	client.ReleaseName = spec.ReleaseName
	client.Replace = true // Skip the name check
	client.ClientOnly = true
	client.APIVersions = []string{}
	client.IncludeCRDs = true

	// NameAndChart will return first the TemplateName if set,
	// second the ReleaseName if set, and lastly the generatedName
	releaseName, _, err := client.NameAndChart([]string{spec.ChartName})
	if err != nil {
		return nil, err
	}
	client.ReleaseName = releaseNameif name, _, err := client.NameAndChart([]string{spec.ChartName}); err == nil {

@elenz97 I can create a PR on this as well.


How to show emoji on win7?

Uses the Segoe UI Emoji system font, even on Windows 7 or Windows 8 (if installed in c:/Windows/Fonts) by implementing Microsoft’s COLR/CPAL font format extensions.

I setup KB2729094 on win7, this web page (https://www.istartedsomething.com/uploads/emojisegoe.html) can show emoji icon as black white mode now.
but in my app, emoji still be a sqare
how to implementing Microsoft’s COLR/CPAL font format extensions ?
can you tell more about it?

Unfortunately KB2729094 updates Segoe UI Symbol, which only has black and white symbols.
You need to install Segoe UI Emoji, which is not freely available, but you can get it from a Windows 10 machine (C:/Windows/Fonts/seguiemj.ttf). Rumour has it you can also google for seguiemj.ttf and get lucky.

Could it be possible to embed seguiemj.ttf or NotoColorEmoji_WindowsCompatible.ttf into the emoji.wpf or emoji.wpf.<fontname> assembly?


It seems cannot run

I following your  command to run the code, but I get following error.
File "train.py", line 87, in main     output = model(*(batch[2:]))   File "/home/ydc/anaconda3/envs/CD/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl     result = self.forward(*input, **kwargs)   File "/home/ydc/anaconda3/envs/CD/lib/python3.8/site-packages/torch/nn/parallel/data_parallel.py", line 162, in forward     return self.gather(outputs, self.output_device)   File "/home/ydc/anaconda3/envs/CD/lib/python3.8/site-packages/torch/nn/parallel/data_parallel.py", line 174, in gather     return gather(outputs, output_device, dim=self.dim)   File "/home/ydc/anaconda3/envs/CD/lib/python3.8/site-packages/torch/nn/parallel/scatter_gather.py", line 68, in gather     res = gather_map(outputs)   File "/home/ydc/anaconda3/envs/CD/lib/python3.8/site-packages/torch/nn/parallel/scatter_gather.py", line 63, in gather_map     return type(out)(map(gather_map, zip(*outputs)))   File "/home/ydc/anaconda3/envs/CD/lib/python3.8/site-packages/torch/nn/parallel/scatter_gather.py", line 63, in gather_map     return type(out)(map(gather_map, zip(*outputs)))   File "/home/ydc/anaconda3/envs/CD/lib/python3.8/site-packages/torch/nn/parallel/scatter_gather.py", line 55, in gather_map     return Gather.apply(target_device, dim, *outputs)   File "/home/ydc/anaconda3/envs/CD/lib/python3.8/site-packages/torch/nn/parallel/_functions.py", line 71, in forward     return comm.gather(inputs, ctx.dim, ctx.target_device)   File "/home/ydc/anaconda3/envs/CD/lib/python3.8/site-packages/torch/nn/parallel/comm.py", line 230, in gather     return torch._C._gather(tensors, dim, destination) RuntimeError: Input tensor at index 1 has invalid shape [1, 474, 80], but expected [1, 302, 80]

Hi @yangdongchao , I didn't check the parallel training yet. If you have several GPUs inserted, please specify a single GPU by
CUDA_VISIBLE_DEVICES=<GPU index>.

Hi @yangdongchao , I didn't check the parallel training yet. If you have several GPUs inserted, please specify a single GPU by
CUDA_VISIBLE_DEVICES=<GPU index>.

Thanks for your reply.


updated batik version to 1.17

updated batik version to 1.17

Thanks for the heads up on new batik version. I've updated it in main and will publish a new release soon. I'm currently finishing off some work on updated Saxon support


Stop Generation Command Does Not Work

I just tried the "stop generation" command - it didn't work. The local AI continued generating as if nothing changed. I was using Internlm2.5:7b-chat-1m at the time.
It did generate the message "No Generation In Progress" - then went back to "Generating Response."
I can't test it with an online model because they all have 4K token output limits and they're too fast for me to hit the stop generation command even with a hotkey.

Thanks so much for the insight - it was a feature I started building out but never finished. Will be finishing it soon and pushing into the latest update, I'll keep this issue open until it hits the live version :)


Error Running the Sample Project - Visual Studio Test Explorer

Hi,
Is this running on Windows, or Mono on another platform? Windows
If you download the example solution, and make no changes, does that execute tests correctly? No
This errors comes from example solution with no changes made.
Test Name:	Pro.NBench.xUnit.Tests.DictionaryMemoryTests.AddMemory_FailingTest
Test FullName:	Pro.NBench.xUnit.Tests.DictionaryMemoryTests.AddMemory_FailingTest
Test Source:	C:\Project\Samples\Pro.NBench.xUnit\Pro.NBench.xUnit.Tests\DictionaryMemoryTests.cs : line 46
Test Outcome:	Failed
Test Duration:	0:00:00.001
Result StackTrace:
at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
at System.Reflection.RuntimeAssembly.get_DefinedTypes()
at NBench.Sdk.Compiler.ReflectionDiscovery.<>c.b__4_0(IEnumerable1 types, Assembly assembly)    at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable1 source, TAccumulate seed, Func3 func)    at NBench.Sdk.Compiler.ReflectionDiscovery.LoadAllTypeConfigurators()    at NBench.Sdk.Compiler.ReflectionDiscovery.GetConfiguratorTypeForMeasurement(Type measurementType, Assembly specificAssembly)    at NBench.Sdk.Compiler.ReflectionDiscovery.GetConfiguratorForMeasurement(Type measurementType, Assembly specificAssembly)    at NBench.Sdk.Compiler.ReflectionDiscovery.CreateSettingsForBenchmark(BenchmarkClassMetadata benchmarkClass)    at Pro.NBench.xUnit.XunitExtensions.NBenchTestInvoker.RunNBenchTest(Object testClassInstance) in C:\Code\Projects\VS2015\Pro.NBench.xUnit\Pro.NBench.xUnit\XunitExtensions\NBenchTestInvoker.cs:line 150    at Pro.NBench.xUnit.XunitExtensions.NBenchTestInvoker.<>c__DisplayClass4_0.<InvokeTestMethodAsync>b__0() in C:\Code\Projects\VS2015\Pro.NBench.xUnit\Pro.NBench.xUnit\XunitExtensions\NBenchTestInvoker.cs:line 71    at System.Threading.Tasks.Task1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Pro.NBench.xUnit.XunitExtensions.NBenchTestInvoker.d__4.MoveNext() in C:\Code\Projects\VS2015\Pro.NBench.xUnit\Pro.NBench.xUnit\XunitExtensions\NBenchTestInvoker.cs:line 71
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
Result Message:	System.Reflection.ReflectionTypeLoadException : Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

@aft-nickolas  - Thanks for logging the issue. For some reason I was not notified that it was posted.
This seems to be related to the Test Runner used. I can replicate the error when using Visual Studio Test Explorer; when using Resharper, all functions correctly.
The specific issue is Visual Studio Test Runner cannot find a Microsoft  DLL -
Microsoft.VisualStudio.TestPlatform.ObjectModel
I am investigating why this occurs.

Ok, this is a bit messy... it seems to have happened somewhere during one of the updates released for Visual Studio 2015, as originally Visual Studio Test Explorer was functioning.
The problem is that xUnit Test Runner seems to have a dependency on
'Microsoft.VisualStudio.TestPlatform.ObjectModel, Version=<IP_ADDRESS>'
This does ship with Visual Studio 2015, however the Visual Studio Test Explorer cannot find it.
There is not a nuget package with this version available, that I could include to ensure it was located - there are nugets for version <IP_ADDRESS> and a beta version 15.x.x.x.
Adding a reference (in the project that contains your Tests), to your local copy of Microsoft.VisualStudio.TestPlatform.ObjectModel is a workaround that will allow you to continue using Visual Studio Test Explorer.

This is now functional in Visual Studio 2017, tested using Pro.NBench.Xunit 1.0.4.


Networkworld

resolves: https://github.com/MirageNet/Mirage/issues/713

Plan:
GameObjectExtension

gets NetworkIdentity on a gameobject

NetworkWorld

collection of Spawned objects
gets NetworkIdentity from id
Time and tick
Spawn/Destroy/unspawn functions
Spawn/Destroy Events
sends spawn message to client
Spawn/Destroy message handlers
local player reference

SyncVarSender

collection of dirty objects
sends syncvars message

SyncVarReceiver

handles syncvar message
updates values on client

ServerObjectManager
authority

controls next Id given to spawned Identities
scene spawning
spawn all scene objects
scene/ready
Set Client Ready
Set all clients unready
handles ready message from client
listens for scene changes and sets client not ready and spawns object

visibility

show object for player
hides object for player

player character

adds character to player
removes character from player

server rpc

handles serverrpc from client

ClientObjectManager
prefab management

inspector list of prefabs
register prefabs
register custom spawn handler
client spawning
applies spawnMessage
finds and instantiate objects
hides/shows objects
client clean up
destroy all client objects (clean up?)
client rpc
handles ClientRpc
handles ServerRpc Reply

NetworkServer

Transport reference

Authenticator reference

world reference

transport config (max Connections)

Start/Stop Events

Start/Stop functions

start/stop host functions

connect/disconnect events

Listen toggle (offline mode)

active state

add/remove Connections

Send

Player list

Create player instance

NetworkClient reference

Is Host Mode

NetworkClient

Transport reference

Authenticator reference

world reference

connected/authenticated/disconnected Events

connected state

Connection/Disconnect functions

Send

Create player instance

Is Host Mode


update Dockerfile with new jupyter/scipy-notebook and packages

Updates for Dockerfile, including newest versions of jupyter scipy notebook Docker and other packages used in the jupyter scipy ee notebook

That seems to have been a mistake on my part, I followed some suggestions in the error messages during the build and added them to the Dockerfile without testing. Essentially, the command conda clean -tipsy should be replaced by conda clean --all -f -y. I can go ahead and commit the proper changes. However, before I do so I have encountered 2 futher problems while using this build for the last 2 weeks:

The base notebook on which all the Jupyter dockers are built currently installs jupyterlab 1.0.4 (see line 107 in this Dockerfile). As it currently stands, after I build the jupyterlab notebook for earth engine, the UI has significant glitches, a bug that is mentioned on the jupyterlab repo. As a workaround for now, I simply run conda install jupyterlab=1.1.2 after the image is built and the container is deployed, and that seems to fix the issue entirely.
When using the earthengine CLI, there are a few error messages that appear to be related to a compatibility issue between tensorflow 1.13.1 and numpy 1.17.2 (see this issue on the tensorflow repo). A workaround that fixes things for now is to run conda install numpy=1.16.4, which again I run once everything is built and up and running.

I am assuming both these issues will be fixed when tensorflow releases version 1.14.1 and when jupyter updates all their Dockerfiles so they build images with jupyterlab 1.1.2. However, I was wondering what changes to the Dockerfile you would recommend for our current purposes. For now I have fixed these issues after building the docker image because they are quite bothersome, but I can certainly add them in to the Dockerfile on a temporary basis, and eventualy update it when these issues are fixed upstream. I noticed you added version arguments for all the packages in the intro of the Dockerfile, do you think that adding those two lines directly in the conda install call without adding version arguments would be an acceptable workaround for now? I have tested it and it works.

Version compatibility is often a challenge. I would suggest including your version adjustments for jupyterlab and numpy in the Dockerfile, along with comments that indicate why the versions are being adjusted so that they can be removed later when the base image is updated.

I completed all the changes in the last commit and tested it, everything seems good to go.


-- ci: use gcc-release preset for builds

the linux-release cmake preset uses a legacy build directory which doesnt work with our CI workflows.

👍 Looks good! We might need to add some exceptions for certain GCC diagnostics though, since GCC 13 (default under Ubuntu 24.04) produces additional warnings in oatpp and fmt.

The diagnostic in question is -Wdangling-reference.


adding scroll on theme option

@abel-otegbola please assign me this task

Hi @Shinchan3102 you can go ahead with it.

And please, don't forget to star the project

yep thanks


Only do one test run on Travis

Currently we run the istanbul scripts on the post success hook.
It would be easier if we can only do one test run (more immediate feedback, less waiting on PRs). It seems npm run test-coverage will output the same error when a test fails as does the normal test suite, so we can save us one run.
I'll work on a PR.
cc @marcjansen

PR attached

@sweco-sebhar @tschaub this does what we talked about, only one test run instead of 2 test runs which run consecutively

@bartvde is this still relevant?

I'm not sure @marcjansen what is your opinion?

That would also mean a real failed integration test if travis is down, right? I am unsure on this one, but will not block.

@bartvde is this still valid?

Let's close it.


Update RabbitMQ collector to latest version

Your project is at risk due to the use of vulnerable dependencies. To prevent potential risk it may cause, I suggest a library update. Please look into the details below.

Vulnerable Library Version: com.rabbitmq : amqp-client : 4.11.3
CVE ID: CVE-2018-11087
Import Path: zipkin-collector/rabbitmq/pom.xml
Suggested Safe Versions: 5.4.0, 5.4.1, 5.4.2, 5.4.3, 5.5.0, 5.5.1, 5.5.2, 5.5.3, 5.6.0, 5.7.0, 5.7.1, 5.7.2, 5.7.3, 5.8.0

Thanks, there are multiple reasons to update as this code just wasn't strictly paid attention to.
Are you able to help with this?

FYI, the CVE doesn't apply here as we aren't using spring for our collector, also the version mentioned in the CVE says versions up to 4.8 are vulnerable and we are at latest (4.11.3)
Still, it would be nice, even if not emergency, for someone to help move to the 5.x series.


HARVESTER: fixed can"t found resourceMethods in spoofedType

The resourceMethods property is not found when using spoofedType.

@richard-cox   PTAL,   thanks.


Allow prepareRename to return ranges that do not include original position

Problem
TypeScript would like to support renaming files by hitting F2 anywhere in the import path.
import * as _ from './dir1/dir2/file'

Here, hitting F2 anywhere in in the string './dir1/dir2/file' should trigger a rename only on the file part of the path. However, in prepareRename, we currently can't return rename ranges that do not include this original rename position. This means that we cannot support hitting F2 anywhere on `'./dir1/dir2/``
Proposal
Relax this restriction, either eliminating it entirely or perhaps only requiring the rename range to be on the same line as the original position

@mjbvz I have eased the restrictions and also removed from workaround check from the TS extension but still wasn't able to test this. It seems TS server errors on a rename request on the class-keyword...


Layout on Mobile

[x] three column grids should probably just break into 1-column-by-3-rows when there's not enough space
[x] what should we do about overly long formulas. I currently think overflow-x: scroll.
[x] do a final pass on paddings and margins on mobile

I rewrote parts of playground so now it uses a breakpoint + CSS grid to transition from 1 column on mobile to two column on desktop. I really need to look into ways to make this easier to build for authors, but for now I declare victory until the issue reports come in!


[DocDB] question about required parameters

Hi @dmakwana
I saw in the quickstart deployment of DocDB:
https://github.com/Azure/azure-quickstart-templates/blob/master/101-documentdb-account-create/azuredeploy.json
That neither 'consistency_policy' nor 'locations' are required. Using "Automation options" on the portal shows usage of 'locations', but not 'consistency_policy':
       {
            "apiVersion": "2015-04-08",
            "kind": "GlobalDocumentDB",
            "type": "Microsoft.DocumentDb/databaseAccounts",
            "name": "[parameters('name')]",
            "location": "[parameters('location')]",
            "properties": {
                "databaseAccountOfferType": "Standard",
                "locations": [
                    {
                        "id": "[concat(parameters('name'), '-', parameters('location'))]",
                        "failoverPriority": 0,
                        "locationName": "[parameters('locationName')]"
                    }
                ]
            }
        }

Could you confirm if these parameters are required as the Swagger says?
FYI @amarzavery

There is a default consistency policy and so it is not necessarily required. The "locations" parameter however is required. The quickstart deployments of DocumentDB all seem to be out of date. We have a slightly modified version to accommodate for geo-replication of the database. I will note down to make the changes in those quickstart templates. And I think we can go ahead and remove the required tag for "consistencyPolicy"

Thanks @dmakwana !
I added this in the open PR https://github.com/Azure/azure-rest-api-specs/pull/682

PR merged, close this one. Thanks!


docs: improve $allModels documentation

closes #4840
closes #5167
This PR adds more concrete examples for the $allModels model client extension to help our users build a better mental model of how or when to use them.
This PR also cleans up the usage of xprisma.
Provide more concrete examples based on user feedback linked to the issue.

@ruheni would this comment be worth tackling via this PR as well?
https://prisma-company.slack.com/archives/C043X6JBND6/p1691704235991279


Issue with direct line channel in azure bot service

I'm getting the above issues sometime. And sometimes it's working fine. May I know the reason for it?

@samthrusha123
It's hard to say. How often do you get this issue? Where are these errors showing up? Is this in the browser developer tools console? If so; for what? Webchat?
Please include more information for assistance.

What channels/client
What version of the SDK
What language of the SDK
Composer or code-first
Any other pertinent information

those errors I'm seeing in the console, It's in direct line channel,
I'm using Bot framework V4 SDK
C#, but from Js I'm making a call to directline.
Sometime I'm getting this error in directline channel

but from Js I'm making a call to directline.

Can you explain more? In the webchat page you're making a call to directline? What is the call? Code samples will help.

but from Js I'm making a call to directline.

Can you explain more? In the webchat page you're making a call to directline? What is the call? Code samples will help.

I'm calling the below function when user click on the chat button.
Code
  function loadChatBot() {     (async function () {       const res = await fetch(         "https://directline.botframework.com/v3/directline/tokens/generate?=",         {           headers: {             authorization:               "Bearer **<Secret Token>"**,           },           method: "POST",         }       );       const { token } = await res.json();       const store = window.WebChat.createStore(         {},         ({ dispatch }) =>           (next) =>           (action) => {             if (action.type === "DIRECT_LINE/CONNECT_FULFILLED") {               dispatch({                 type: "WEB_CHAT/SEND_EVENT",                 payload: {                   name: "webchat/join",                   value: { language: window.navigator.language }                 },               });             }             return next(action);           }       );       window.WebChat.renderWebChat(         {           directLine: window.WebChat.createDirectLine({ token }),           store,           userName: getUserName()+","+currentPoint,           userID: getUserName()+","+currentPoint,         },         document.getElementById("webchatBot")       );       document.querySelector("#webchatBot > *").focus();     })().catch((err) => console.error(err));   }


Move GetSignatures into ProcessedType hierarchy and simplify signific…

…antly

https://github.com/mono/Embeddinator-4000/issues/276

Build and tests passed.

Build and tests passed.


Add Transition Animation for Table Expanded Content

This function solves the problem (这个功能解决的问题)
Support for drag and drop sorting and animation enhancement
Expected API (期望的 API)
1.Supports table drag and drop sorting
2.Added transition animation for table expansion and collapse

track the row d&d in #2273

We won't implement expand transition. It would be too complex.


feat(#220): sync main before creating new branch on new

Fixes #220

Current dependencies on/for this PR:

main

PR #221   👈

This stack of pull requests is managed by Graphite.


feat: add size getters to the Area component

This adds the ability to query <Area>'s size as mentioned in #130. Also modified the area example to show how to use it.

That actually seems like the easiest solution. The documentation will need to be changed however. Could you do this?

I'm (currently) unable to implement my approach, but I still don't think this is very elegant (especially because this requires setting the size in the state manually).
This would be the first use of refs in proton-native (though libui exposes also a scrollTo function for scrolling areas which would need this)

You don't need to set it in the state, I did it so the UI would be updated

What would would you do otherwise if not update the UI?

That actually seems like the easiest solution

Easiest to implement, yes. But easiest to use?
Using refs:
class Example extends Component {
  state = {
    rectangleWidth: 100
  };

  constructor(props) {
    super(props);
    this.area = React.createRef();
    this.onContentSizeChange = this.onContentSizeChange.bind(this);
  }

  onContentSizeChange() {
    this.setState({
      rectangleWidth: Math.pow(this.area.current ? this.area.current.getWidth() : 100, 2)
    });
  }

  render() {
    return (
      <App>
        <Window
          title="Test"
          size={{ w: 600, h: 650 }}
          margined={true}
          onContentSizeChange={this.onContentSizeChange}
        >
          <Box padded>
            <Area
              ref={this.area}
            >
	            <Area.Rectangle
	              x="100"
	              y="0"
	              width={this.state.rectangleWidth}
	              height="100"
	              fill="blue"
	            />
            </Area>
          </Box>
        </Window>
      </App>
    );
  }
}

Function as children approach (if it works):
class Example extends Component {
  render() {
    return (
      <App>
        <Window
          title="Test"
          size={{ w: 600, h: 650 }}
          margined={true}
        >
          <Box padded>
            <Area>
              {(width, height) => (
                <Area.Rectangle
                  x="100"
                  y="0"
                  width={Math.pow(width, 2)}
                  height="100"
                  fill="blue"
                />
              )}
            </Area>
          </Box>
        </Window>
      </App>
    );
  }
}

If you want to write everything in JSX I have no more arguments. @kusti8 will have to make the executive decision here.
Your idea is specific for just rendering, mine works for every use case. You have to force a re-render to get the new size, I just get the event and decide if the re-render is needed. Simple example from the editor component I'm writing: the user changes the horizontal size of the window - the number of lines shown doesn't change so I don't need to re-render the whole component.
The only other way to do this is to create a callback like onContentSizeChange but for Area. Not a good idea since you can't really detect that the area changed size in libui, but on the other hand it can be patched later if support for such thing is added to libui, and for now we can just traverse the component tree up until we find a Window and attach the callback there.

the user changes the horizontal size of the window - the number of lines shown doesn't change so I don't need to re-render the whole component.

A resize always triggers a area redraw, otherwise there would be nothing drawn in the previously not visible area part.

Your idea is specific for just rendering, mine works for every use case.

But mine feels way more natural for drawing.

change the PR after I get back.

I can totally live with Area.onSizeChange. And these two aren't mutually exclusive, so the function as children could still be added?

Area redraw - yes, React component re-render - no. There is a big difference there. Why do you want to add these functions so much? It's not how it's done in React, that's why you get the warning and there is no way around that, save for dirty hacks.

React component re-render - no.

AreaComponent don't render like React components, their render methods get called in the area callback.

It's not how it's done in React, that's why you get the warning and there is no way around that, save for dirty hacks.

There will be no dirty hacks.

Can you please re-read what I wrote? And if you look at the source code, the internal area is not drawn like a React component, but the one you use in the app (react-components/Area) is.
About dirty hacks - we will see, but the warning is there for a reason.

@kusti8 changed to onSizeChanged event instead of ref/getters.

AreaComponents are the possible children of Area: Area.Rectangle, Area.Circle, Area.Text, ...

the internal area is not drawn like a React component, but the one you use in the app (react-components/Area) is.

Why do you want to re-render the Area component? This would only affect the children (AreaCompontents).
And react-components/Area does only this:
render (){
	return <AreaContext.Provider> {/*For StyledText to work*/}
		<AreaInternal {...areaProps}>
			<Area.Group {...areaGroupProps}>
				{this.props.children}
			</Area.Group>
		</AreaInternal>
	</AreaContext.Provider>;
}

but the warning is there for a reason.

Only because I didn't really know what I was doing. This will be fixed properly and as it's supposed to work, or not at all.

Because with your approach you have to re-render the Area component to get new width/height values, don't you know how/when the render function is called in React?

@mischnic Since there is no documentation for libui I didn't know you got an event when the area was resized, that's why I used refs. And just for clarity, you seem to have omitted a very important line when quoting the docs:

For example, instead of exposing open() and close() methods on a Dialog component, pass an isOpen prop to it.

Which is exactly what I've done after I learned it was possible. Your approach on the other hand is nowhere to be found in React/RN. You keep proposing things that are complex and inefficient just for the sake of doing it your way. As someone who has been using React almost since day one if I saw any of the things you proposed in the docs I'd just pass on this library.

Should onSizeChange expose the libui area object? The other callbacks don't do that (the defaultProps declaration for them is wrong but the docs are correct).

I was wondering about that since the default props for the others did it
also. It shouldn't expose libui.
On Mon, Sep 3, 2018, 3:18 AM Niklas Mischkulnig<EMAIL_ADDRESS>wrote:

Should onSizeChange expose the libui area object? The other callbacks
don't do that (the defaultProps declaration for them is wrong but the docs
are correct).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kusti8/proton-native/pull/174#issuecomment-418023177,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJW73P0--EgWffK7HF5jl11Q0X7ZujGOks5uXNeqgaJpZM4WWMnm
.

Should I fix only this or add another commit that fixes the default props for others as well?

Fix the others as well while we're at it. Thanks!
On Tue, Sep 4, 2018, 4:51 AM Maciej Sopyło<EMAIL_ADDRESS>wrote:

Should I fix only this or add another commit that fixes the default props
for others as well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kusti8/proton-native/pull/174#issuecomment-418291123,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJW73KdpyHkPAc34v7_3WmKnxlfNeSLOks5uXj8HgaJpZM4WWMnm
.

I fixed the default props and the area example and it seems to work fine on my end. I'll merge tomorrow if everything is good.

There is one issue with this: you can't determine the size of the initial render:


Android debug build > :app:bundleDebugJsAndAssets_SentryUpload FAILED

OS:

[ ]  Windows
[X]  MacOS
[ ]  Linux

Platform:

[ ]  iOS
[X]  Android

> Task :app:bundleDebugJsAndAssets_SentryUpload FAILED
  INFO    2019-01-31 15:57:24.025993 +01:00 Loaded config from /Users/brian/.sentryclirc
  DEBUG   2019-01-31 15:57:24.027105 +01:00 sentry-cli version: 1.37.4, platform: "darwin", architecture: "x86_64"
  INFO    2019-01-31 15:57:24.027133 +01:00 sentry-cli was invoked with the following command line: "/Users/brian/punten-app/node_modules/@sentry/cli/sentry-cli" "--log-level" "debug" "react-native" "gradle" "--bundle" "/Users/brian/punten-app/android/app/build/generated/assets/react/debug/index.android.bundle" "--sourcemap" "/Users/brian/punten-app/android/app/build/generated/assets/react/debug/index.android.bundle.map" "--release" "nl.puntje.business-1.0.8" "--dist" "8"
  INFO    2019-01-31 15:57:24.030271 +01:00   bundle path: /Users/brian/punten-app/android/app/build/generated/assets/react/debug/index.android.bundle
  INFO    2019-01-31 15:57:24.030290 +01:00   sourcemap path: /Users/brian/punten-app/android/app/build/generated/assets/react/debug/index.android.bundle.map
Processing react-native sourcemaps for Sentry upload.
> Analyzing 2 sources
  DEBUG   2019-01-31 15:57:24.031403 +01:00 error: running update nagger
  DEBUG   2019-01-31 15:57:24.031692 +01:00 skipping update nagger because session is not attended
error: No such file or directory (os error 2)
  DEBUG   2019-01-31 15:57:24.037634 +01:00 client close; no transport to shut down  (from sentry)

Config:
index.js
Sentry.config('https://...@sentry.io/...').install()

I have following issue:
I am getting a build error when running react-native run-android
Steps to reproduce:

Install react native sentry
Link it
Run react-native run-android
Getting ask :app:bundleDebugJsAndAssets_SentryUpload FAILED error.

Why does it attempt to upload source map for debug build? Can I disable this?

Its seems there is a problem with version 0.41. Downgrading back to 0.40.3 prevents the problem, There was a major refactor to the build.gradle on version 0.41 that probably caused the problem.

Any updates on this issue? please let me know if anyone need help to reproduce.

@HazAT  Also I am seeing the upload to Sentry taking a long time compared to the previous versions. Is it something do with the library update or Sentry server issue?

edit "node_modules/react-native-sentry/sentry.gradle"
change
def bundleTasks = tasks.findAll { task -> task.name.startsWith("bundle") && task.name.endsWith("JsAndAssets")}

to
def bundleTasks = tasks.findAll { task -> task.name.startsWith("bundle") && task.name.endsWith("JsAndAssets") && !task.name.contains("Debug")}

Same issue with RN 0.57, setting bundleInDebug: true works  but compiling tkaes more time

Same here with RN 58.3 and Sentry 41.1
After trying @icfr 's approach i get :app:transformDexArchiveWithExternalLibsDexMergerForDebug
with Program type already present: org.slf4j.IMarkerFactory
Any ideas?

@beardred i think it's another issue ...
possible solution

same here, bundleInDebug: true not works for me, getting the same output
> Task :app:bundleDebugJsAndAssets_SentryUpload
Processing react-native sourcemaps for Sentry upload.
> Analyzing 2 sources
> Rewriting sources
> Adding source map references
error: project not found

Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
Please attach the full debug log to all bug reports.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:bundleDebugJsAndAssets_SentryUpload'.
> Process 'command 'node_modules/@sentry/cli/bin/sentry-cli'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 34s
76 actionable tasks: 2 executed, 74 up-to-date
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/getting-started.html

A workaround is to replace in android/app/build.gradle
apply from: "../../node_modules/react-native-sentry/sentry.gradle"

with
if (!getGradle().getStartParameter().getTaskRequests().toString().contains("Debug")) {
	apply from: "../../node_modules/react-native-sentry/sentry.gradle"
}

It will skip the upload of JS sources to Sentry only during debug build.

I had to remove Sentry from my project because of this issue. AppCenter fails to build and those workarounds aren't relevant since I guess it doesn't have the debug flag.

Would anyone of you, would be so kind and create a PR with a fix for it?
Thanks!


Is there any way to implement this code on a custom dataset ?

Hi, congratulations on your work!
I was actually wondering if there is any way to run this code on a custom dataset?

I want to know about this problem,do you solve it? Looking forward to your aply.

Hi, congratulations on your work!
I was actually wondering if there is any way to run this code on a custom dataset?

I want to know about this problem,do you solve it? Looking forward to your aply.


Deliverable 1

Triggering a TravisCI build, I'll reopen this!

Triggering TravisCI

I squashed your commits into one and updated the Signed off by!


Home Assistant Object Detection Requests Crashing DeepStack

Follow on from the issue over here:
https://github.com/robmarkcole/HASS-Deepstack-object/issues/169
When I make requests from Home Assistant using a previously setup and working camera for object detection, Deepstack seems to crash (or significantly slow). It was previously working with around 200ms response time. Trying it now, Home Assistant times out, but from DeepStack logs I can see it's taking 4-15 minutes to process images.
If I use similar images through AI Tool, Deepstack works fine, however, once I send a request from Home Assistant, DeepStack seems to crash and stops working with either until the container is rebooted. I'm not seeing significant CPU usage after a request from Home Assistant.
Any ideas or logs/debugging I can do to try and work this out?

Issue was having the min confidence set to 0, using 1 instead has resolved this.

Issue was having the min confidence set to 0, using 1 instead has resolved this.


Error during - pip install . -

Hi all,
I'm trying to install neural-speed library. I'm following this tutorial Build Python package (Recommended way) .
System configuration:
OS : WSL2 - Linux DESKTOP-PNBMAG8 <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Python: Python 3.10.12
My steps:

CREATE PROJECT FOLDER: neural-speed-tutorial
CREATE VIRTUAL ENV: python3 -m venv neural-speed-env
CLONE NEURAL-SPEED REPOSITOTY: git clone https://github.com/intel/neural-speed.git
RUN: pip install -r requirements.txt (successful)
pip install .

TERMINAL LOG ERROR:
`
CMake Error in neural_speed/application/CMakeLists.txt:
Imported target "pybind11::module" includes non-existent path
      "/usr/include/python3.10"

    in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

    * The path was deleted, renamed, or moved to another location.

    * An install or uninstall procedure did not complete successfully.

    * The installation package was faulty and references files it does not
    provide.

`
What could be the solution? Did I miss any crucial steps during the installation or while executing the commands listed above?
Thank you for any suggestions.

You can use python setup.py install to see if it will give you an error?

Hi @intellinjun thanks for your reply. I tried to use python3 setup.py and I got this error:
`
/home/dario-reply/neural-speed-tutorial/neural-speed-env/lib/python3.10/site-packages/setuptools/init.py:80: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!
    ********************************************************************************
    Requirements should be satisfied by a PEP 517 installer.
    If you are using pip, you can try `pip install --use-pep517`.
    ********************************************************************************

!!
dist.fetch_build_eggs(dist.setup_requires)
WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml does not contain a tool.setuptools_scm section'
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: no commands supplied
`


isdir can be very slow when the parent directory contains many other directories

From my testing it appears as though current calls to isdir end up calling info which then ends up calling self.ls(self._parent(path), detail=True, **kwargs).  This can end up being an unexpectedly long call if the parent directory contains many subdirectories.

Closed by https://github.com/dask/s3fs/pull/259


Fix Repository is not a class

In https://github.com/huggingface/huggingface_hub/pull/1724 I deprecated Repository but the wrong way, making Repository a function instead of a class. This PR fixes this. The warning message stays the same:
/home/wauplin/projects/huggingface_hub/src/huggingface_hub/utils/_deprecation.py:131: FutureWarning: 'Repository' (from 'huggingface_hub.repository') is deprecated and will be removed from version '1.0'. Please prefer the http-based alternatives instead. Given its large adoption in legacy code, the complete removal is only planned on next major release.
For more details, please read https://huggingface.co/docs/huggingface_hub/concepts/git_vs_http.

Fix https://github.com/huggingface/huggingface_hub/issues/1878 (thanks @versae for reporting)

I wasn't aware this would have the following effect.

Same here :smile: Haven't thought of it at all


Split unit into three categories

One category for test that are currently passing because of old datastax code
Second category for tests that are being broken by current changes (this category is not tested on CI)
Third category for unit tests that should work with the new driver code
(Note, CI steps currently fails due to not working examples)

If needed I can also take Splits examples and unit tests into two separate CI tasks. from #43 and add it as a separate PR to allow passing of unit tests without working exaples

Although #54 can be easily merged into main, it would require much mor effort to elegantly merge this into main (as this PR already splits tests based on simple-query branch). For this reason I'm keeping target branch as simple-query

Some checks are failing - why?

The target branch currently doesn't have the required functionality to pass examples


Storage buffers get renamed after conversion to MSL

Hello!
I am trying to convert the following two shaders from HLSL/GLSL to MSL using glslangValidator as compiler:
HLSL:
struct StructBufferData
{
    float4 data;
};
StructuredBuffer<StructBufferData> g_StructBuffer;
float4 main() : SV_Position
{
    return g_StructBuffer[0].data;
}

GLSL:
layout(std140) readonly buffer g_StructBuffer
{
    vec4 data;
}g_StructBuffer_Inst;
void main()
{
    gl_Position = g_StructBuffer_Inst.data;
}

The shaders are seemingly equivalent and are both successfully converted to MSL:
From HLSL:
#include <metal_stdlib>
#include <simd/simd.h>
using namespace metal;
struct StructBufferData
{
    float4 data;
};
struct g_StructBuffer
{
    StructBufferData _data[1];
};
struct main0_out
{
    float4 gl_Position [[position]];
};
vertex main0_out main0(const device g_StructBuffer& g_StructBuffer_1 [[buffer(0)]])
{
    main0_out out = {};
    out.gl_Position = g_StructBuffer_1._data[0].data;
    return out;
}

From GLSL:
#include <metal_stdlib>
#include <simd/simd.h>
using namespace metal;
struct g_StructBuffer
{
    float4 data;
};
struct main0_out
{
    float4 gl_Position [[position]];
};
vertex main0_out main0(const device g_StructBuffer& g_StructBuffer_Inst [[buffer(0)]])
{
    main0_out out = {};
    out.gl_Position = g_StructBuffer_Inst.data;
    return out;
}

The problem is that if I inspect SPIRV resources returned by get_shader_resources() before and after the conversion, then the storage buffer is enumerated under the name g_StructBuffer in both cases before the conversion, however after the conversion it is still enumerated as g_StructBuffer for GLSL case, but renamed to g_StructBuffer_1 in HLSL case.
Can you help me understand why the behavior is inconsistent between GLSL and HLSL?
This seems to only be happening with structured buffers.
I need to know the original names after the conversion to MSL, or, at least, how to map them to original names.
Here is the generated SPIRV
HLSL:
StructBuffer.vert.hlsl
// Module Version 10000
// Generated by (magic number): 80008
// Id's are bound by 30

                              Capability Shader
               1:             ExtInstImport  "GLSL.std.450"
                              MemoryModel Logical GLSL450
                              EntryPoint Vertex 4  "main" 24
                              Source HLSL 500
                              Name 4  "main"
                              Name 11  "StructBufferData"
                              MemberName 11(StructBufferData) 0  "data"
                              Name 13  "g_StructBuffer"
                              MemberName 13(g_StructBuffer) 0  "@data"
                              Name 15  "g_StructBuffer"
                              Name 24  "@entryPointOutput"
                              MemberDecorate 11(StructBufferData) 0 Offset 0
                              Decorate 12 ArrayStride 16
                              MemberDecorate 13(g_StructBuffer) 0 NonWritable
                              MemberDecorate 13(g_StructBuffer) 0 Offset 0
                              Decorate 13(g_StructBuffer) BufferBlock
                              Decorate 15(g_StructBuffer) DescriptorSet 0
                              Decorate 15(g_StructBuffer) Binding 0
                              Decorate 24(@entryPointOutput) BuiltIn Position
               2:             TypeVoid
               3:             TypeFunction 2
               6:             TypeFloat 32
               7:             TypeVector 6(float) 4
11(StructBufferData):             TypeStruct 7(fvec4)
              12:             TypeRuntimeArray 11(StructBufferData)
13(g_StructBuffer):             TypeStruct 12
              14:             TypePointer Uniform 13(g_StructBuffer)
15(g_StructBuffer):     14(ptr) Variable Uniform
              16:             TypeInt 32 1
              17:     16(int) Constant 0
              18:             TypePointer Uniform 7(fvec4)
              23:             TypePointer Output 7(fvec4)
24(@entryPointOutput):     23(ptr) Variable Output
         4(main):           2 Function None 3
               5:             Label
              28:     18(ptr) AccessChain 15(g_StructBuffer) 17 17 17
              29:    7(fvec4) Load 28
                              Store 24(@entryPointOutput) 29
                              Return
                              FunctionEnd

GLSL:
StructBuffer.vert
// Module Version 10000
// Generated by (magic number): 80008
// Id's are bound by 24

                              Capability Shader
               1:             ExtInstImport  "GLSL.std.450"
                              MemoryModel Logical GLSL450
                              EntryPoint Vertex 4  "main" 13
                              Source GLSL 430
                              Name 4  "main"
                              Name 11  "gl_PerVertex"
                              MemberName 11(gl_PerVertex) 0  "gl_Position"
                              MemberName 11(gl_PerVertex) 1  "gl_PointSize"
                              MemberName 11(gl_PerVertex) 2  "gl_ClipDistance"
                              Name 13  ""
                              Name 16  "g_StructBuffer"
                              MemberName 16(g_StructBuffer) 0  "data"
                              Name 18  "g_StructBuffer_Inst"
                              MemberDecorate 11(gl_PerVertex) 0 BuiltIn Position
                              MemberDecorate 11(gl_PerVertex) 1 BuiltIn PointSize
                              MemberDecorate 11(gl_PerVertex) 2 BuiltIn ClipDistance
                              Decorate 11(gl_PerVertex) Block
                              MemberDecorate 16(g_StructBuffer) 0 NonWritable
                              MemberDecorate 16(g_StructBuffer) 0 Offset 0
                              Decorate 16(g_StructBuffer) BufferBlock
                              Decorate 18(g_StructBuffer_Inst) DescriptorSet 0
                              Decorate 18(g_StructBuffer_Inst) Binding 0
               2:             TypeVoid
               3:             TypeFunction 2
               6:             TypeFloat 32
               7:             TypeVector 6(float) 4
               8:             TypeInt 32 0
               9:      8(int) Constant 1
              10:             TypeArray 6(float) 9
11(gl_PerVertex):             TypeStruct 7(fvec4) 6(float) 10
              12:             TypePointer Output 11(gl_PerVertex)
              13:     12(ptr) Variable Output
              14:             TypeInt 32 1
              15:     14(int) Constant 0
16(g_StructBuffer):             TypeStruct 7(fvec4)
              17:             TypePointer Uniform 16(g_StructBuffer)
18(g_StructBuffer_Inst):     17(ptr) Variable Uniform
              19:             TypePointer Uniform 7(fvec4)
              22:             TypePointer Output 7(fvec4)
         4(main):           2 Function None 3
               5:             Label
              20:     19(ptr) AccessChain 18(g_StructBuffer_Inst) 15
              21:    7(fvec4) Load 20
              23:     22(ptr) AccessChain 13 15
                              Store 23 21
                              Return
                              FunctionEnd

The weirdness with HLSL is that the same OpName is used for both block and instance name, which means the MSL output must compensate for that. When you query the name of a resource, it's based on the block name, if you want the instance name, try compiler.get_name(resource.id) instead.

OK, I see why this is happening.
compiler.get_name(resource.id) returns "g_StructBuffer_1", which is expected. However,resource.name is also "g_StructBuffer_1", but should it not be "g_StructBuffer"?

compiler.get_name(resource.base_type_id) returns the original struct name, which is what I need.
Thank you for looking into this.


Multi-arch (specifically ARM64) Docker Volume Plugin build.

Summary
The docker volume plugin currently only seems to run on AMD64.
With the addition of A1 (arm64) instances in Amazon, it would be very welcome to have a pre-built version of the Docker Volume plugin for this architecture.

As a workaround you can build the plugin yourself having only docker and git as a dependency:
REXRAY_VERSION=0.11.4

git clone --depth 1 --branch v${REXRAY_VERSION} https://github.com/rexray/rexray.git
cd rexray
make
DRIVER=ebs make
sed -i 's/FROM alpine:3.6/FROM debian:stretch/g' .docker/plugins/ebs/.Dockerfile
sed -i 's/apk update/apt-get update/g' .docker/plugins/ebs/.Dockerfile
sed -i 's/apk add/apt-get install -y/g' .docker/plugins/ebs/.Dockerfile
sed -i 's/#!\/bin\/ash/#!\/bin\/bash/g' .docker/plugins/rexray.sh
DRIVER=ebs make build-docker-plugin
docker plugin set rexray/ebs:${REXRAY_VERSION}-dirty REXRAY_PREEMPT=true EBS_REGION=us-east-1
docker plugin enable rexray/ebs:${REXRAY_VERSION}-dirty

If you're running this in a script (for example in UserData) you have to add sed -i 's/-it/-t/g' Makefile before the first make command.
I couldn't get it working with the alpine images.