Redeployed script etc to 'upgrade'and PowerApp not showing Sensitivity feature

Description
Used the latest release and Deployment Guide to redeploy the solution to add sensitivity labels feature to existing implementation. I received one error message from deploy.ps1 run:
_### AZURE AD APP CREATION ###
Azure AD App 'Request a Team' already exists - updating existing app...
unrecognized arguments: --password *****************************************************
Followed steps to update existing PowerApp by importing package and updating existing App. 'Teams Requests', 'Teams Templates', 'Team Request Settings', 'IP Labels' lists connections etc added / updated successfully. Updated the 'OnStart' function and all steps after that to ensure settings are there.
When opening / editing PowerApp the feature for Sensitivity labels is not there.
Steps to reproduce

Followed Deployment guide ran step 1. Ran deploy.ps1
Skipped step 2 of the guide as already exists.
Followed step 3 but updated existing App.
Step 4; flows and logic app updated.
Step 5; Checked sharing
Step6 followed except updated the existing App in Teams and not creating a new one.

Expected results
I expect to see the additional tab for sensitivity labels in the Power App
Actual Results
No change to original implementation
Solution component
Power App
Operating system (environment)
Windows
Additional Info
No response

I have found the issue. The deployment guide Step 1 states to : "Download the latest release" which links to the page with 'Source code (zip) ' available to download (which is what I used). However you need to use the "package"  which is 'Master' that is referred to in the 'Prerequisites' section above Step 1.  It's the master that contains the latest release NOT the link stating "Latest release".


Reading a cell with sheet.cell() changes the data to null

Pretty strange issue here. This is my code. I'm essentially parsing a table
Test Upload.xlsx
final bytes = File(filePath).readAsBytesSync();
final excel = Excel.decodeBytes(bytes);
final defaultSheet = await excel.getDefaultSheet();
final sheet = excel[defaultSheet];
// Cell B1 is 60 here
final widthCell = sheet.cell(CellIndex.indexByColumnRow(columnIndex: 1, rowIndex: 0));
// But now it is null
print(widthCell.value);

There is code in cell() on line 104 and 105 of sheet.dart that seems to be causing this. It seems that is just isn't carrying the value over. Am I doing something wrong?

I've also experienced this, had to workaround by not using cell().
defaultSheet.row(0)[1].value

Thanks @zakton5 for letting us know about this.
It's fixed now and will be updated in the new version by tomorrow: excel: ^1.1.0


Thank you for this nice boilerplate

Actually, I just wanted to say thank you 👍

:DD Thanks, @sufius , very appreciated


Add new classes for intrinsic functions

The main driver for this is the Sub function.
The idea is to have a class that can treat
!Sub "${AWS::Region}" the same as Fn::Sub: ["${Region}", {"Region": {"Ref": "AWS::Region"}}]  That way when we hit these functions we do not need to account for both possibilities.  Additionally we can add some functionality here to predict a string output which allows us to better test the value for validity.

Resolved in v1


Fix issue with more worker daemons being started than max workers

Fixes an issue where a single task can end up starting more worker daemons than max workers rather than reusing existing workers.

Is this issue in 4.1 M1? If so it might be affecting demos of parallel execution at the summit.

Yes

It's been around for some time.  We just didn't have test coverage for it.  We had tests that submitted more work than max workers with multiple tasks (which works properly), but not in a single task.

Was this problem in compiler daemons before? If not, didn't we have enough test coverage for them?

No.  Compile tasks only submit one unit of work, so you would never see this problem with a compile task.


Adding custom domain to Azure Static WebApp Problem

Hi All,
I'm trying to add a custom domain to my Azure Static Web app but i receive following message
Could not add custom domain. Please ensure the custom domain is not linked to another app or that a previous implementation is not still being cleaned up..

The cname it's correctly configured

No more app in azure have this domain in my subscription. The only thing it's that this domain was assigned 5 days ago to another Static Web App but removed the same day.
What can i do to solve this frustrating problem ?
Thanks in advance

you should try https://github.com/Azure/static-web-apps/issues/1447#issuecomment-2404729057


FAQ - request to add additional troubleshooting information

Can you add additional troubleshooting steps for scenarios where the Prerequisites seem to be fulfilled, but there are still errors when processing the data in the dataset?
Example: "The credentials provided for the Web source are invalid." even when the logon is successful

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

ID: 82f8dd20-599d-ab7f-a1db-7e2b5310abb1
Version Independent ID: 897a9588-8a69-dc64-6722-fd2c731f0f03
Content: Connect to the Emissions Impact Dashboard - Power BI
Content Source: powerbi-docs/connect-data/service-connect-to-emissions-impact-dashboard.md
Service: powerbi
Sub-service: powerbi-template-apps
GitHub Login: @rosode
Microsoft Alias: rosode

Thanks for your comment, @[github person who posted].
I've assigned this issue to the doc author for review.

Hi @externalperjohanssoniig , this article has been updated several times since you opened this issue. I am going to close it now, but if the document still seems in error, please reopen. Thanks!


more console

if oneOf function doesn't have any arguments or argument is empty, will get undefined. But I think we should give some warning about it.

Build is not passing on this one

All right, Object.keys(collection) doesn't support non-object in previous node version.
I would change _.keys(collection) to make it.

It's conflicting so I will reject this change.


Review the regrid-main branch ready for merger

Description
@sol1105 and @ellesmith88: in preparation for merging the regrid-main branch into the clisops master branch, I am asking @ellesmith88 to review the existing code that @sol1105 has written. The main aims for doing this are:

Ensure that the structure of the new regrid code is in line with the existing subset
Place the constants, functions and classes into the clisops.utils, clisops.ops and clisops.core packages following existing practices.
Ensure that names for modules, functions, classes and methods follow existing practices.
Ensure that the appropriate level of documentation exists in docstrings (for modules and functions/methods).
Ensure that the unit test coverage is suitable.
Develop the Jupyter Notebooks to demonstrate the functionality.
Consider the daops interface that will sit on top of the clisops interface.

Proposed approach
Please create a new branch (or multiple branches) to develop the modified version of the code.

Martin asked me to focus on points 1 and 3 and the notebook initially while he continues working on the rest. I have added comments to the PR from regrid-main-martin to regrid-main.
I can look at points 2, 4 and 5 next. The daops interface already exists https://github.com/roocs/daops/blob/regrid-main/daops/ops/regrid.py but probably needs to be updated.


Upgraded to Nuxt3 RC 13 and added secret to config

Closes #13

have you updated via the nuxi command that they propose in the release notes?

See discussion about type issue in PR: https://github.com/sidebase/nuxt-session/pull/20 as nuxt-session and nuxt-auth are facing similar issues.

I've opened an issue with nuxt here: https://github.com/nuxt/framework/issues/8931
Closing this in favor of #22


[WIP] Auto-cancel all reduce-only orders before executing closing of position

Description
This PR attempts to close out #461.  Currently, an error will be thrown if a user tries to close out a derivatives position if they have limit orders in the opposite orderType direction >= the Amount of the position.
Changes

Upon click of close position, position.vue will pass the open reduce-only limit orders to closePosition in the store.
The store will call closePositionAndReduceOnlyOrders in derivatives.ts.
closePositionAndReduceOnlyOrders will pass a formatted message to the chain in the MsgBatchUpdateOrders bucket.

ToDo

update https://github.com/InjectiveLabs/injective-ts/blob/master/packages/derivatives-consumer/src/composers/DerivativeMarketComposer.ts with a new BatchUpdateDerivativsOrders method to properly format the message to MsgBatchUpdateOrders

@bangjelkoski lmk if it's cool for me to update injective-ts and if you have any comments about the code changes so far.

You can use: https://github.com/InjectiveLabs/injective-ts/blob/master/packages/exchange-consumer/src/composers/MarketComposer.ts

Refactor the original PR and I'll review it. The approach is good :)

@bangjelkoski after refactoring, I attempted to close out a position with an existing reduce-only order equal to the amount of the position, and I see this error:

I suspect the issue to be related to the spotOrdersToCreatelList property in tx_pb.js:

I  can investigate tx_pb.js locally in node_modules/@injectivelabs some more tomorrow.  I'm open to any other thoughts as well.

Let me test this locally as well and I'll let you know when I figure out the issue.

I'll check locally. I've merged the PR, the codebase introduced is great :)


feat(sdk-logs): export MultiLogRecordProcessor

This way library authors can reuse it in their packages.
Signed-off-by: Peter Somogyvari<EMAIL_ADDRESS>
Which problem is this PR solving?
Library authors can't re-use the multi log record processor in their code because it wasn't exported to the public API surface of the pacakge until now.
Short description of the changes
Exported the MultiLogRecordProcessor
How Has This Been Tested?
I verified that the project still compiles.
Checklist:

[x] Followed the style guidelines of this project
[ ] Unit tests have been added
[ ] Documentation has been updated

Hi @petermetz, I think it has not been exported on purpose - it is used internally as a convenient way of handling multiple processors in the LoggerProvider class. If you want to use multiple processors in your application, you can call LoggerProvider.addLogRecordProcessor() multiple times. If you have a specific use case for using the MultiLogRecordProcessor class over the addLogRecordProcessor method, please provide more details.

Hi @petermetz, I think it has not been exported on purpose - it is used internally as a convenient way of handling multiple processors in the LoggerProvider class. If you want to use multiple processors in your application, you can call LoggerProvider.addLogRecordProcessor() multiple times. If you have a specific use case for using the MultiLogRecordProcessor class over the addLogRecordProcessor method, please provide more details.

@martinkuba There's this repo implementing a pino transport for OpenTelemetry (so that the logs you send to pino end up in OTel) which I saw and were evaluating and in there they had to re-create their own implementation of the multi log processor from scratch to be able to support multiple processors.
The repo: https://github.com/Vunovati/pino-opentelemetry-transport#readme
Specific line in the docs that I was paraphrasing above: https://github.com/Vunovati/pino-opentelemetry-transport/blob/main/multi-log-processor.js#L8
I'm not the author of the pino-opentelemetry-transport project and I have not evaluated if there was a better/simpler way of supporting multiple processors without having to use the MultiLogRecordProcessor. If you still think that there is a better/more robust way of achieving this (as-in, what the pino transport does) then I agree that this PR should be closed without merging.


STIFI-61 TTS echo route

This modifies the echo route so that it will audibly echo caller's speech using TTS.
Before it only echoed the caller by logging what he said in console.
With the conclusion of this implementation we have set up a nice base for a continued implementation of an IVR-client for SDiFI with a continuous flow of user speech and TTS responses in their respective directions.

@rkjaran Klára e.t.v. að fara yfir og tvinna https://github.com/SDiFI/headless/pull/2 og endurgrunna svo þessa við master.


Support Media Source Extensions

W3C spec
This will improve scores for browsers like Edge 14  because this is the default behavior for Edge 14 (copied from the link) :
Returns true :

isTypeSupported ('video/webm; codecs="vp9"')
isTypeSupported ('video/webm; codecs="vp9, opus"')
isTypeSupported ('video/webm; codecs="opus"')
isTypeSupported ('audio/webm; codecs="opus"')

And these will return “false”:

isTypeSupported ('video/webm')
isTypeSupported ('audio/webm')

VP9 works fine on YouTube for me at least. This kind of conflicts the results of html5test.
Sorry if I blabbered something - I am not a hardcore web dev.

MSE is already included on HTML5Test

@dstorey  D'oh!

Yes, we already test for the existence of MSE support. But I am interested in adding codec tests for MSE too. I already have this for the video and audio tag itself, but I suspect that codec support can differ between directly using the tags and MSE.

Edge at least does support different codecs at the moment for MSE vs vanilla audio/video

For that matter codecs supported by Web/ObjectRTC will be different to MSE & vanilla video element too

Added codec detection for Media Source Extensions


the android apk can't be used

link :https://github.com/adityar224/Random-Face-Generator/releases/download/3.0.0/RFG-Android-3.0.0.apk
have download the apk, and can't use it in my cellphone.
could you help me ?

link :https://github.com/adityar224/Random-Face-Generator/releases/download/3.0.0/RFG-Android-3.0.0.apk
have download the apk, and can't use it in my cellphone.
could you help me ?

If you look before creating an issue the API the app uses is no longer working. You're wasting peoples time making pointless issues that are already known.


Maintenance

Coverage remained the same at 83.333% when pulling 5431fd6fc4228ebe4d0c49956a3e5682ad1a30d2 on maintenance into 71663493d0bec68871fe16e463caabf4265e5b26 on master.


Convert current website into Next.js static site

Implement the current website in Next.js.
Problems that we want to solve:

Move away from writing direct HTML and JS.
Remove duplication of code.
Improve code quality.

Implementation Suggestions:
You should fork this repository and then do all the development in your fork. Once you think your code is ready, you can create a PR against this repo. See docs about fork.
References:

Github pages
Next.js

Done via https://github.com/prixite/prixite.github.io/pull/5


[1259] Add referrer type to manage view

Context
We need to explicitly show the source of the referral ie Public/Employer
Changes proposed in this pull request

Add 'Type: Public/Employer' to the referrer details. This will also appear on the PDF version

Guidance to review

Checklist

[x] Attach to Trello card
[x] Rebased main
[x] Cleaned commit history
[x] Tested by running locally

It would be good for future maybe to add some specs for components as well. What do you think?

Yep. Agreed. I've carded up a review for us to discuss and add some https://trello.com/c/tIpooZmN/149-component-tests


Error during renewal process

Hello,
I am using Plesk 12.5.30 Update #24 on CentOS Linux 7.2.1511 (Core).
Installed version of Let's Encrypt (Plesk plugin) is 1.5.
During the renewal process I am getting the following error and therefore no ne certs.
Any suggestions on how to solve the issue?
Best regards
matl
Fehler: Fehler bei der Installation des SSL-Zertifikats von Let's Encrypt: Failed letsencrypt execution: Traceback (most recent call last): File "/usr/local/psa/var/modules/letsencrypt/venv/bin/letsencrypt", line 11, in <module> sys.exit(main()) File "/usr/local/psa/var/modules/letsencrypt/venv.COlED/lib/python2.7/site-packages/letsencrypt/cli.py", line 1950, in main plugins = plugins_disco.PluginsRegistry.find_all() File "/usr/local/psa/var/modules/letsencrypt/venv.COlED/lib/python2.7/site-packages/letsencrypt/plugins/disco.py", line 168, in find_all plugin_ep = PluginEntryPoint(entry_point) File "/usr/local/psa/var/modules/letsencrypt/venv.COlED/lib/python2.7/site-packages/letsencrypt/plugins/disco.py", line 31, in __init__ self.plugin_cls = entry_point.load() File "/usr/local/psa/var/modules/letsencrypt/venv.COlED/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2201, in load self.require(*args, **kwargs) File "/usr/local/psa/var/modules/letsencrypt/venv.COlED/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2218, in require items = working_set.resolve(reqs, env, installer) File "/usr/local/psa/var/modules/letsencrypt/venv.COlED/lib/python2.7/site-packages/pkg_resources/__init__.py", line 835, in resolve raise VersionConflict(dist, req).with_context(dependent_req) ContextualVersionConflict: (cryptography 1.1 (/usr/local/psa/var/modules/letsencrypt/venv.COlED/lib/python2.7/site-packages), Requirement.parse('cryptography>=1.3'), set(['PyOpenSSL']))

Same issue here
OS: Debian 7.9
Plesk 12.5.30 Update Nr. 27
Fehler: Fehler bei der Installation des SSL-Zertifikats von Let's Encrypt: Failed letsencrypt execution: Traceback (most recent call last): File "/opt/psa/var/modules/letsencrypt/venv/bin/letsencrypt", line 11, in <module> sys.exit(main()) File "/usr/local/psa/var/modules/letsencrypt/venv.Vnb5L/local/lib/python2.7/site-packages/letsencrypt/cli.py", line 1950, in main plugins = plugins_disco.PluginsRegistry.find_all() File "/usr/local/psa/var/modules/letsencrypt/venv.Vnb5L/local/lib/python2.7/site-packages/letsencrypt/plugins/disco.py", line 168, in find_all plugin_ep = PluginEntryPoint(entry_point) File "/usr/local/psa/var/modules/letsencrypt/venv.Vnb5L/local/lib/python2.7/site-packages/letsencrypt/plugins/disco.py", line 31, in __init__ self.plugin_cls = entry_point.load() File "/usr/local/psa/var/modules/letsencrypt/venv.Vnb5L/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2201, in load self.require(*args, **kwargs) File "/usr/local/psa/var/modules/letsencrypt/venv.Vnb5L/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2218, in require items = working_set.resolve(reqs, env, installer) File "/usr/local/psa/var/modules/letsencrypt/venv.Vnb5L/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 835, in resolve raise VersionConflict(dist, req).with_context(dependent_req) ContextualVersionConflict: (cryptography 1.1 (/opt/psa/var/modules/letsencrypt/venv.Vnb5L/lib/python2.7/site-packages), Requirement.parse('cryptography>=1.3'), set(['PyOpenSSL']))

Any ideas on how to update the certificates manually via terminal. "letsencrypt" is not available in terminal.

The dependency issue with "Requirement.parse('cryptography>=1.3'), set(['PyOpenSSL']))" has already been fixed in our repositories.
Just in case you (or your hosting provider) use a mirror, it might have been unsynchronized.
As far as I know our repository has been migrated into another data center.
Try adding in /etc/hosts <IP_ADDRESS> autoinstall.plesk.com

Hello,
I installed updates yesterday. There was a update plesk-letsencrypt:
plesk-letsencrypt-pre.x86_64 0:1.0.0-centos7.16032214
Also added your line to /etc/hosts but no updates so far.
The error still exists anyway.

@openmatl yep, because yum update is not enough
Run plesk bin extension --exec letsencrypt post-install.php

Thanks a lot. It is working again on both of my servers. :+1:
plesk bin extension --exec letsencrypt post-install.php

Bootstrapping dependencies for centos 7 x86_64...
Paket plesk-letsencrypt-pre-1.0.0-centos7.16032214.x86_64 ist bereits in der neuesten Version installiert.
Creating virtual environment...
Updating letsencrypt and virtual environment dependencies...
  Could not find .egg-info directory in install record for setuptools from https://pypi.python.org/packages/source/s/setuptools/setuptools-20.6.6.tar.gz#md5=77d29ce21958f030b47be9669c87027c in /usr/local/psa/var/modules/letsencrypt/venv.ZnoKC/lib/python2.7/site-packages
  Could not find .egg-info directory in install record for pip from https://pypi.python.org/packages/source/p/pip/pip-8.1.1.tar.gz#md5=6b86f11841e89c8241d689956ba99ed7 in /usr/local/psa/var/modules/letsencrypt/venv.ZnoKC/lib/python2.7/site-packages
Switch venv to the installed one...
Done


investigate cargo zigbuild for cross-compiling targeting lower GLIBC version

To make the release binary compatible with most Linux distros, we decided to build it on manylinux2014 starting from #4556 since it features GLIBC 2.17, which is relatively low.
However, the outdated environment also makes maintenance difficult for us. Examples:

Very tricky to install lld: https://github.com/risingwavelabs/risingwave/pull/13746#issuecomment-1833450034
When building dashboard, Nextjs 20 requires Nodejs 18, which is not compatible with GLIBC 2.17: #14913

Theoretically, the target GLIBC version does not have to be the same with the host GLIBC version, which is essentially the idea of cross-compiling. For a long time, however, this has been considered difficult and impossible.
Fortunately, the build system from zig makes the life easier to do cross-compiling on C/C++ dependencies (see https://andrewkelley.me/post/zig-cc-powerful-drop-in-replacement-gcc-clang.html). There's also a wrapper for using zig cc in Rust projects named cargo-zigbuild.
By including the GLIBC version in --target, we're able to make the artifact linked with a different version of GLIBC than the current system uses. Ideally, this allows us to use an arbitrary distro for building RisingWave Linux binaries and still makes it compatible with most old systems.
cargo zigbuild --target aarch64-unknown-linux-gnu.2.17 -p risingwave_cmd_all

However, there're still some outstanding issues for this to work correctly. Generally, it requires all -sys dependencies to correct handle the cases for cross-compiling.

[x] Statically link libz by enabling libz-static feature of rdkafka. #15754
[ ] sasl2-sys does not cross compile: https://github.com/MaterializeInc/rust-sasl/issues/46
[ ] zigbuild may not work correctly with linkme: https://github.com/rust-cross/cargo-zigbuild/issues/214

Since #15821, this is no longer a must-have.


Scram by os

This pull request deals with the case where the spec has a list of arches that can be run.
First commit is renaming IterTools so it doesn't clash with the built-in itertools on OS X.
Second commit is a context manager for temporary environments used in the testing
Third commit is the meat of the PR with unit tests.

@bbockelm (and @hufnagel) Can you check my change to WMTweak? My understanding is that the condor ad file is going to have string values encased in double quotes so I strip them off to make a nice python like dictionary out of the results. I actually don't understand why https://github.com/ericvaandering/WMCore/commit/73db6bb70f8fb7133cb4c3a27383e5b70123b822#diff-8d59623f30f8f60048722cb843d1bc8eR601 works (if it does).

test this please

@ticoann pending reviews, this can go in. Should be completely backwards compatible.

@ericvaandering - ClassAd values are typed, meaning that some values will be a string ("foo") but others won't (true).  In the line you reference, it's a boolean, meaning there is no double-quotes necessary.
Since the other callers of the readAdValues function expect the raw contents, I would suggest not stripping the double-quotes where you did and move that logic to getSingleScramArch

They are in different commits for exactly that reason. That's how we roll in DMWM.

Still not perfect since sometimes functional and related changes are spread across multiple commits. Guess it's hard or impossible to rebase against anything by the most recent commit.

Also, this mode is not compatible with the github review process since that shows you all the changes at once. At least I didn't find a way to split them except to manually check all he individual commits. Which then leads to problem if functional changes are split across different commits.
Anyways, I never bother to use the review process anyways because of this. Code changes look ok.

No, I've had probably 15 different commits in my branch, reordered, grouped, inserted in between and squashed and so forth. You can rebase -I as much as you want.

OK, this addresses @bbockelm first issue, but not the return value. @amaltaro what do you think?

Thanks @amaltaro . Updated with your suggestions.

Testing it on top of pre10

@ticoann also good to be merged

@ericvaandering, Eric, Sorry could you fix the conflicts?

Conflicts fixed. @amaltaro please mark as reviewed.

test this please

blindly approved ;)

@ticoann please merge this. The pylint errors are coming from things where I just renamed IterTools. Any file I truly modified, I cleaned up


Great to find this community

Hi,I am a Chinese player.So excited am I to discover this place that remains the Crusader lovers.We have a no small group which has a lot of aiv makers.If we have a chance,We would be very delighted to communicate with you.
Thanks for your hard work and UCP.

Welcome to the western lands I guess ;D

I think our group has large amount of different AIVs.We discover some powerful way to improve the aivs,suring that it must be difficult to destroy the ai's castle.If possible,we can exchange our aivs to find the difference between us and even have a chance to hold a match.(we have more than 15 aiv makers)

@forestleaves can you give us a link to your AIV?

@forestleaves: For all you AI designers out there, i invite you to take part in the AI Design Contest, it is still running until end of October.
You can check all the instructions out in the videodescription of this Video:
https://www.youtube.com/watch?v=SOOG1bKbVKM

Nice to meet you! I found this project last month and introduce to Chinese friends . We have some   very wonderful discoveries in the Aiv Editor about building walls in one second. Also we invented some structure to avoid arrow close to 99 percent(can't hurt unit in this structure by archer). We found some way to build walls that make HorseArcher can't attack the unit on that wall . As you can guess we make many wonderful things and very happy to meet who are interesting either.

Nice inventions, tho i believe they were already known 6 years back in the Stronghold Heavengames Community. There might be even big summary papers sticking around the Stronghold Crusader Modifications Download Section :)
(As far as i know there are 2 main types for the Arrow safe units: crenels in front of stairs, or High towers in front of wall or lower towers, but the high tower method has still holes for some arrows coming threw!)
If you find any solution in making trebuchet safe castle design, let us know!
Feel free to post anything you know so far, or take inspirations by others. It never hurts to keep innovating!
If you want, you could take a look at this mega project, where most of the castle is build by multiple AI's:
https://www.youtube.com/watch?v=ZqM81sr4HwA

We use  'Arrow safe units' to safe Fbal ,we put Fbal on the stairs and make it arrow safe by towers. Also we found something about towers which can make more fun. We found bug in the Aiv Editor and use it. Maybe you can see the following video and guess some.
https://www.bilibili.com/video/av63850675
Also this the collections of videos ,we make aiv competition games either.
space :  https://space.bilibili.com/87155277/
videos:  https://space.bilibili.com/87155277/video
Vpn maybe need to see above those.

Ok i ll look into it :D
Which bug do you mean in the AIV Editor?
Ive made a video describing some tricks for the AIV Editor. I guess molding is the important part for the onesec wall trick.
Fireballistas on walls is a onetime thing unfortunatly, as they will be not rebuild after they got crushed by catapults or such things.
Thank you for the contribution! I ll look forward for more :D
And for your entry in the AI Design Contest

Molding maybe just half way to onesec wall trick. There are other ways, more than three. But my friends want to keep it a little secret temporarily right now :D .Maybe we can begin with AIV and AI Design communication and have fun :D

Another video link of onesec wall trick, we make it build easy and irregular, also fast enough.
https://www.bilibili.com/video/av58062436

I d like to see the actual buildstep, tho it wasnt shown :(
But i believe you to have such a trick up your sleve.
So will you be taking part in the AI Design Contest? :D
It involves using the UCP too tho! So maybe you want to get familiar with the values it provides for modding your AI's

Aha,really,the video is made by our contest hoster,and the aivs in the video are designed by different designer,no one person.

What are the criteria?
Is there an english translation of your contest?
In my Contest, the criteria are a variaty of challenges for the AI, no human interaction, just randomnumbers from different games obviously and pure script :)
In the Contest you have one AI that has 4 challenges:

Challenge is to make a lasthit on an enemy AI
Challenge is to grind the most gold out of the AI's that are also on the same map
Challenge is for your AI to survive 12 ingame Years
Challenge is to win a Free for all under 50 Years

and there aree sidequests and multipliers for each map and challenge, to keep the challenges balanced and different ways to win open :)
You must be really creative to make your AI win more than one main Challenge, i havnt seen any AI's beating more than 2 yet! But maybe you can do it? End of Sentin Time is 31. october. this year

Our rules is very different,but no human interact,too.Our match is 3 vs 3,everyone uses three different AIVs to take part in.The game will last until one side'all ais are defeated or the game last too long.

Besides competition match,we also have many kinds of contesta,such as attack test,defend test and so on,

Is there any english description or kinda understandable form for non chinese people?

I would like to take part in one of these, what would i have to do and what would the prize for the winners be?

Actually,We have no prize for the winners,in our group we are because of inrerest to get together with each other,we do not regard the aiv design as a work that earns something,what the winners receive is honour,it is enough.

ok, fair enough, so how could i take part anyways? IHonor is a great reward. And if i could learn more about aiv design on the way, sure i am in!

We are delighted to your join,I sure we have something powerful you have never touch,such as onestep wall and others.
If you want to take part in,you can sent your aivs to us,but mgq,the competition hoster,would firsrt  test your aivs.If you want to

@forestleaves So what is this defense challenge, are we speaking about vanilla AI's or is the UCP Involved? Where do i get the maps that get used? Where can i reach your hoster? And how are we going to connect outside of this post? :D
Is there and official rules panel for the competition?
Which AI's am i allowed to use?
What do you mean by mainly defense/attack/raid... because the Vanilla AI does everything of each. So Do you mean that with using the UCP for raid/Attack/Defense units?

You can see your aivs' performance in mgq'test vedeo.I know language is a problem,maybe a few days later we would sent English rules to you?

Yes please, over discord or mail<EMAIL_ADDRESS>For my contest, i uploaded a rules-sheet publicly if you consider to taking on another kind of AI Design Challenge on your own with another mindset :)
(Rules in english and german so far, but feel free to translate it to chinese for your friends and colleges...) I have beside the honour an analysation of the AI's + steamgifts as prizes planned. I ll also make another AI Contest after this one.
I know honour is enough for most, but i feel like a little extra drives more people to innovate and find out new stuff about AI design for this awesome game!

More things can be discussed a few hours later.You know, here is 2:20a.m. now...

Oh i am sorry, sad to hear that. Just let me know, if you prefer any other communication plattform for personal messenges. I dont want to spam sh0wdowns Issues section with this ^^

@Krarilotus I think we may use mail to communicate or you can suggest some other ways?

@forestleaves
Ok, fine by me :D
i will wait for your mail to arrive at<EMAIL_ADDRESS>


Instance await hangs when instance is in zombie state

checking system properties should use socket timeout to await too long unnecessary awaiting
affects instances.checkRunningOther() and instances.checkAvailable()
also affects instanceUp task using await up action

When such state is detected... Then suggestion for running instance kill would be nice #649

not spotted for a longer time, if anyone will spot it, feel free to reopen

hard to reproduce. probably to be closed.

something is wrong with coroutines in check runner,
updater coroutine is running but no coroutines are running to update progress and whole process hangs... :/

maybe fixed in #763 , for now looking good, let's wait a bit to confirm

seems that separate threads introduced by Executors service fixed the issue. closing...


0.7.20 nebula fixes

Description
Fixes issues with the prompt on a Nebula knowledge query prompt. The original incorrectly references the prompted entity not the entity which was linked in the actual graph.
Fixes # (issue)
Type of Change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Sorry my linter disagres with yours. Feel free to close this PR, but the bug should be fixed if you feel like it.

@moeadham Isn't the example returning the name of the person who directed a movie? Or can you explain the change a bit more, ngl I'm a cypher noob

Sorry this PR is really messy; I’ll tidy it up and better explain the query tomorrow.


Add ReactRootView in RelativeLayout will cause endless loop

I created a ReactRootView instance in this way and added it in a FrameLayout which wrapped by RelativeLayout.
Run the app, we can see the method called onMeasure in ReactRootView cause endless loop.
see DEMO
React Native version: 0.60.0

info Fetching system and libraries information...
System:
OS: Linux 4.15 Ubuntu 18.04.2 LTS (Bionic Beaver)
CPU: (4) x64 Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
Memory: 1.63 GB / 7.68 GB
Shell: 5.4.2 - /usr/bin/zsh
Binaries:
Node: 10.16.0 - /usr/local/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
API Levels: 21, 22, 23, 24, 25, 26, 27, 28
Build Tools: 23.0.1, 23.0.2, 23.0.3, 24.0.2, 26.0.1, 26.0.2, 27.0.3, 28.0.3
Android NDK: 16.1.4479499
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.0 => 0.60.0
npmGlobalPackages:
react-native-cli: 2.0.1
Steps To Reproduce

Download DEMO
Run the app
Set a breakpoint at ReactRootView.onMeasure
The app stop at ReactRootView.onMeasure

Describe what you expected to happen:
The app is running.
Snack, code example, or link to a repository:
DEMO

There is a similar problem which is closed.
see #19403

Are you solving this problem?

Anyone is dealing with this problem?

This is a serious problem should be solved immediately i think. @cpojer

Help!

😢

😢

Maybe this will help somebody:
We've encountered a similiar issue, but we are using a FrameLayout wrapped by a ConstraintLayout. We fixed the problem by setting all four constraints to all layouts within the ConstraintLayout (even if not needed by Android): app:layout_constraintBottom_to..., app:layout_constraintEnd_to..., app:layout_constraintStart_to... and app:layout_constraintTop_to...

Maybe this will help somebody:
We've encountered a similiar issue, but we are using a FrameLayout wrapped by a ConstraintLayout. We fixed the problem by setting all four constraints to all layouts within the ConstraintLayout (even if not needed by Android): app:layout_constraintBottom_to..., app:layout_constraintEnd_to..., app:layout_constraintStart_to... and app:layout_constraintTop_to...

I agree with u. This answer may be more detailed.


Backport CMake build to v1.20

Please change base branch to v1.20 when you can.

Please change base branch to v1.20 when you can.

You should have permissions for branch creation :)

Released: https://github.com/hunter-packages/leveldb/releases/tag/v1.20-p0


.Net: Simplify example 52 to showcase using a custom OpenAIClient in genera…

…l instead of using one specifically for APIM
Motivation and Context
Setting up APIM and AAD is tedious and is not directly related to what we want to showcase: that we can customize OpenAIClient instances used with SK.
resolves #3844
Description
Simplify examples and its requirements.
Contribution Checklist

[ ] The code builds clean without any errors or warnings
[ ] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[ ] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

@markwallace-microsoft please check whether we need the APIM example or not. If I remember correctly, you had set up APIM to hide authentication details when crafting and executing prompts in VSCode extension.


Specification language discussion

At the Rust All Hands in Berlin, we discussed creating a specification language that would be a subset of Rust to use for specifying conditions/constraints/contracts in Rust programs.
We need

Your thoughts on a Rust spec language
Examples of specifications we might want to write

Is there any chance we could use quickcheck-style properties? Something like:
#[verify]
fn max_is_ok(x: i32, y: i32) {
    let z = max(x, y);
    assert!(x <= z);
    assert!(y <= z);
}

this would save putting arbitrary Rust expressions in attributes, and might interoperate better with test environments?

@vakaras I can understand why we need tool-specific ways for users to give hints to tools, e.g. pre/postconditions, loop invariants etc. I'm just wondering if there's some way we can specify the properties that are being verified in a way which is amenable to lots of different verification strategies.
The API for quickcheck is at https://github.com/BurntSushi/quickcheck, the annotations there are things like:
#[quickcheck]
fn max_is_ok(x: i32, y: i32) -> bool {
    let z = max(x, y);
    (x <= z) && (y <= z)
}

The APIs are interoperable, so we're into ergonomics, interoperability, ease of implementation, etc.

I think that ideally there should be a way to compile the invariants to regular code and check them as runtime asserts, whether with quickcheck or some new crate.  Thus, if at all possible, the syntax should be a strict subset of Rust, even for things like quantifiers (which can be expressed using iterator methods).

Might be worth looking at Liquid Haskell as inspiration. They use do constraint solving with refinements for verification purposes. Dafny and Whiley are also interesting languages that use constraint solving, but are more geared towards imperative programming and use contracts for verification. Might also be interesting to check out Ada's SPARK variant.
Would be nice if the specification language make it easy to transition between levels of verification. For example, starting from example tests (ie. #[test]), to generative testing (eg. quickcheck or proptest), then to solvers (eg. Z3), and finally to proof systems (eg. Coq+Iris or Lean). Being able to say, export the solved properties from Z3 to a proof system would be neat!

@asajeffrey

I'm just wondering if there's some way we can specify the properties that are being verified in a way which is amenable to lots of different verification strategies.

I agree that we should aim for this when designing the specification language.
Regarding the Quickcheck, from the examples it seems that it is a way to specify the behaviour “externally” (could be even in a different file) while preconditions and postconditions is a way to specify the behaviour “inline”. In other words, we should agree if we want to support “external” or “inline” specifications. I am clearly biased here, but I think that the specification of an imperative function should be part of its signature and, therefore, I would prefer preconditions and postconditions written as function annotations.
@comex

I think that ideally there should be a way to compile the invariants to regular code and check them as runtime asserts, whether with quickcheck or some new crate.

This was the main reason why I proposed to have a distinction between basic assertions and tool specific assertions. My idea was that the basic assertions would be essentially boolean Rust expressions that are checked when the program is executed (either always, or in only debug builds). In other words, the function:
#[ensures="result >= a && result >= b"]
fn max(a: i32, b: i32) -> i32 {
    if (a < b) { b } else { a }
}

when compiled would become equivalent to:
fn max(a: i32, b: i32) -> i32 {
    let result = if (a < b) { b } else { a };
    assert(result >= a && result >= b, "The postcondition “result >= a && result >= b” failed.");
    result
}

Thus, if at all possible, the syntax should be a strict subset of Rust, even for things like quantifiers (which can be expressed using iterator methods).

I would suggest not to have quantifiers as part of basic assertions at least in the initial version because designing a single syntax of quantifiers that can be supported by different approaches is hard if at all possible.
@brendanzab

Dafny and Whiley are also interesting languages that use constraint solving

Thanks, for sharing. I was not aware of Whiley.

Would be nice if the specification language make it easy to transition between levels of verification.

I agree. Just, I probably would not call them levels of verification. Maybe approaches would be a more suitable word? At least I would like to draw a distinction between what we try to achieve and how.
For example, since SPARK uses the Why3 infrastructure, it supports using both SMT solvers (Z3, CVC4) and proof assistants (Coq, Isabelle) as back-end provers. So, if Z3 is not able to proof something automatically, you can switch to Coq and prove that “manually”. However, the properties you try to prove about your code in both cases are specified in SPARK and are independent of what prover you use.
I think the levels of verification would be more something like (I have adapted from a Yannick Moy's presentation about SPARK):

Manual bug finding (approach: manually writing tests).
Automatic bug finding (approaches: Quickcheck, proptest, fuzzers, concolic execution, model checking, lints).
Proving absence of runtime errors (approaches: static analysis, deductive verifiers such as Why3, SAW, and Viper).
Proving preservation of key properties such as termination, deadlock freedom, secure information flow, etc. (approaches: static analysis, deductive verifiers).
Proving full functional correctness (deductive verifiers, proof assistants such as Coq and Isabelle).

I think it would be nice to support smooth transitions between both approaches and levels.
By the way, as far as I know using Coq or Isabelle as a prover for SPARK requires to know the entire stack (SPARK + Why3) inside-out and is essentially doable only by the SPARK developers. Therefore, I think that Dafny or Liquid Haskell way where a programmer can guide the automatic prover by using some form of ghost code would be more approachable for programmers without strong verification background.

Yes, the question of inline vs external specs is a tricky one. FWIW, in Rust, tests are separate from code, although possibly in the same file. Proof hints (e.g. loop invariants) pretty much have to be inline, but I don't think we're planning to standardize those soon.

don't think we're planning to standardize those soon

What do you mean by “standardize”? That it would be available in stable Rust, or that several tools would use that? I am not sure whether it makes sense to try to stabilize any specification language before we have several tools successfully using it. In other words, until we have some confidence that it is actually usable. Does this make sense to you?

Regarding the specifications we might want to write I suggest to copy from Why3:
http://why3.lri.fr/
Some usage examples:
http://toccata.lri.fr/gallery/why3.en.html
But that's not enough because Rust is impure and it doesn't have the several limitations given to Why3 to allow you to prove it. So some annotations from Ada-SPARK are needed to face the impure nature of Rust functions, I mean the SPARK annotations that specify how information flows in/out of a function beside the function arguments.
And that's not yet enough, you also have to allow only a subset of Rust features in those #[verify] functions (just like SPARK does with Ada), the idea is to implement things as how const functions are implemented in Rust: you start from allowing very little stuff inside a const function and then you iterate to add more and more stuff. The same should be done with Rust functions that are proved correct. And some Rust features will be unavailable into those proved functions for a very long time. So

Regarding the specifications we might want to write I suggest to copy from Why3:
http://why3.lri.fr/
Some usage examples:
http://toccata.lri.fr/gallery/why3.en.html
But that's not enough because Rust is impure and it doesn't have the several limitations given to Why3 to allow you to prove it. So some annotations from Ada-SPARK are needed to face the impure nature of Rust functions, I mean the SPARK annotations that specify how information flows in/out of a function beside the function arguments.
And that's not yet enough, you also have to allow only a subset of Rust features in those #[verify] functions (just like SPARK does with Ada), the idea is to implement things as how const functions are implemented in Rust: you start from allowing very little stuff inside a const function and then you iterate to add more and more stuff. The same should be done with Rust functions that are proved correct. And some Rust features will be unavailable into those proved functions for a very long time.


remove duplication? in the pom

A few groups ran into a problem when changing from java 11 to java 8. It had to be changed in 3 places. It seems to me that the use of the maven-compiler-plugin configuration is no necessary given the two options in the  section.  I removed them, it works fine for me switching between java 11 and 8.
Just in case: @emilybache was there some specific reason to add the 11 and the specific version of maven-compiler-plugin?

I wanted to use the latest version of java to see if there were  new language features could be useful for solving this problem. Thanks for making it simpler to switch

just realized I don't have write access to this repo so @isidore will need to accept this pull request I think


Time range not matched in records computation

Describe the bug
ValueError: SPulseProcessing got inconsistent time ranges of inputs: {'raw_records':<PHONE_NUMBER>000000000,<PHONE_NUMBER>368708120), 'raw_records_simu':<PHONE_NUMBER>725899872,<PHONE_NUMBER>368708120)}

To Reproduce
Insert the MWE of how to reproduce the error
st = saltax.contexts.sxenonnt(output_folder='/home/yuanlq/scratch-midway2/salt/tests',
                              runid=24109, saltax_mode='salt')
st.storage.append(strax.DataDirectory('/project2/lgrandi/tutorial_data', readonly=True))
records = st.get_array('024109', 'records')

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions
Please add the output of:
straxen.print_versions()

All italic comments can be removed from this template.

Another example
RuntimeError: SPulseProcessing was unable to get time-consistent inputs after ten passess. Inputs:
{'raw_records': [040671.raw_records:<PHONE_NUMBER>sec 0 ns -<PHONE_NUMBER>sec 0 ns, 0 items, -1.0 MB/s], 'raw_records_simu': [040671.raw_records_simu:<PHONE_NUMBER>sec 725899872 ns -<PHONE_NUMBER>sec 977343290 ns, 1473904 items, 6.2 MB/s]}
Input buffer:
{'raw_records': [040671.raw_records:<PHONE_NUMBER>sec 0 ns -<PHONE_NUMBER>sec 368708120 ns, 863609 items, 39.2 MB/s], 'raw_records_simu': [040671.raw_records_simu:<PHONE_NUMBER>sec 977343290 ns -<PHONE_NUMBER>sec 977343290 ns, 0 items, -1.0 MB/s]}

There are two ways to move ahead:

Find a way to make raw_records_simu to share the same time ranges of each chunk as raw_records
Manually modify raw_records_simu meta data?

Better to start with 1. Need some surgery here

Can we get inspired from merged_s2s where we handled peaklets and lone_hits?

Idea:

Force same chunking timing.
Add additional safe guard in time range of instructions.

To implement this idea, we probably want to input the chunk times in similar ways as we did for instructions

Idea: write a wrapper around get_array which automatically add rr_chunk_ranges as config.

Wait why don't I just add this to context config? What a nasty workaround for wrapper around get_array...

Solved in #48

First victim show up
ValueError: Attempt to create chunk [033048.raw_records_simu:<PHONE_NUMBER>sec 474835480 ns -<PHONE_NUMBER>sec 949671960 ns, 556093 items, 6.3 MB/s] whose data ends late at<PHONE_NUMBER>949698590

First victim show up
ValueError: Attempt to create chunk [033048.raw_records_simu:<PHONE_NUMBER>sec 474835480 ns -<PHONE_NUMBER>sec 949671960 ns, 556093 items, 6.3 MB/s] whose data ends late at<PHONE_NUMBER>949698590

This one turns out to be irrelevant.


New feature: log screens

Looks good to me.

Almost all ESLint issues are fixed now. There only is one error left in CredentialCard related to onReorderPress and onReorderPressOut. This was a notification that already existed and is caused by a part of code that is commented out. I fixed the linting errors in code that I actually changed.


"404 - Not Found" when downloading dataset from Google Colab

Hello,
Up until yesterday, I was able to download the dataset from Bluebook Bulldozers while running Google Colab. (My Kaggle credentials are stored in Google Drive.)
However, since today, I keep getting an "404 - Not Found" error every time I run the code cells below.
Is someone else having this issue and is there something I can do to fix this ?
Thanks.
!pip install kaggle

Output:
Requirement already satisfied: kaggle in /usr/local/lib/python3.6/dist-packages (<IP_ADDRESS>)
Requirement already satisfied: python-dateutil in /usr/local/lib/python3.6/dist-packages (from kaggle) (2.5.3)
Requirement already satisfied: urllib3<1.23.0,>=1.15 in /usr/local/lib/python3.6/dist-packages (from kaggle) (1.22)
Requirement already satisfied: certifi in /usr/local/lib/python3.6/dist-packages (from kaggle) (2018.10.15)
Requirement already satisfied: six>=1.10 in /usr/local/lib/python3.6/dist-packages (from kaggle) (1.11.0)
Requirement already satisfied: python-slugify in /usr/local/lib/python3.6/dist-packages (from kaggle) (1.2.6)
Requirement already satisfied: requests in /usr/local/lib/python3.6/dist-packages (from kaggle) (2.18.4)
Requirement already satisfied: tqdm in /usr/local/lib/python3.6/dist-packages (from kaggle) (4.27.0)
Requirement already satisfied: Unidecode>=0.04.16 in /usr/local/lib/python3.6/dist-packages (from python-slugify->kaggle) (1.0.22)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /usr/local/lib/python3.6/dist-packages (from requests->kaggle) (3.0.4)
Requirement already satisfied: idna<2.7,>=2.5 in /usr/local/lib/python3.6/dist-packages (from requests->kaggle) (2.6)

import io, os
from googleapiclient.http import MediaIoBaseDownload
from google.colab import auth

auth.authenticate_user()

drive_service = build('drive', 'v3')
results = drive_service.files().list(
        q="name = 'kaggle.json'", fields="files(id)").execute()
kaggle_api_key = results.get('files', [])

filename = "/root/.kaggle/kaggle.json"
os.makedirs(os.path.dirname(filename), exist_ok=True)

request = drive_service.files().get_media(fileId=kaggle_api_key[0]['id'])
fh = io.FileIO(filename, 'wb')
downloader = MediaIoBaseDownload(fh, request)
done = False
while done is False:
    status, done = downloader.next_chunk()
    print("Download %d%%." % int(status.progress() * 100))
os.chmod(filename, 600)

Output:
Download 100%.

!kaggle competitions download -c bluebook-for-bulldozers -p /content/kaggle

Output:
404 - Not Found

Sorry, I opened an issue... I tried the above code again this morning and it now works...

The same issue.
It works yesterday, but do not work today.

Same thing today. Yesterday it worked.

I had the same issue when I tried to installing kaggle  API with the different command it worked for me
!pip install -q kaggle

Didn't wor

I had the same issue when I tried to installing kaggle API with the different command it worked for me
!pip install -q kaggle

Didn't worked for me :'(

If you are using Ubuntu or any other Linux distribution, try switching to Windows. I am not sure why but this actually worked for me.

please reopen

I found somebody on Kaggle suggesting to reset runtime (not restart) and rerun, and it worked for me!

This error is because of below reason, see message.
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "dailyLimitExceededUnreg",
"message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup.",
"extendedHelp": "https://code.google.com/apis/console"
}
],
"code": 403,
"message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup."
}
}


Reverse neighbor ordering

Related to #116.
It would be helpful if the neighbor iteration order was reversed, to match the insertion order. I'm assuming the way it works now is a result of simplicity/optimization, and not that reverse insertion order by itself is useful in some use cases?
From what I understand of the current implementation, I think it could be changed by storing an extra pair of edge indices for each node, so that nodes store both the head and tail of the linked list. Then new edges can be added to the tail, and neighbors can be iterated starting from the head.
The obvious downside is having to store an extra pair of edge indices for each node. If the order isn't needed, it's wasted space, but if the order is needed, this should be much better than reversing the lists, or storing extra ordering information.
For context, I'm writing a GUI library that uses the neighbor order for widget depth. Right now for drawing widgets I just manually do a BFS on the tree and reverse the neighbors, but I'll have to do something similar for DFS, it would be nice to be able to use the visit algorithms as is. I've seen Conrods approach, which is to track the ordering with extra edges. It's a lot of extra implementation complexity (and overhead) that I'd prefer to avoid, since for my use case it's enough to just use the insertion order, and occasionally bring nodes to the front by removing/re-adding edges.
Overall I think it would be a trade off of some extra space for more efficiency when the order does matter, more importantly though, I think it would be a less surprising and easier to use API. Would also be a subtle breaking change though.
If it seems reasonable I could try to implement it for Graph and StableGraph?

Whoops.. sorry if some of that was confusing! I made some stretches of logic about the visit algorithms, based on the fact that my code was wrong and actually does need to do a DFS with neighbors in reverse.. I mistakenly assumed the iteration order would be consistent with the order in neighbors, which makes no sense.
Since collecting the neighbors into a Vec is unavoidable for those algorithms, there wouldn't really be a benefit to being able to directly iterate neighbors in insertion order since they can just treat the Vec as a stack.
Since I'm using a tree instead of a general graph and doing a BFS recursively I could avoid collecting neighbors into a Vec if neighbors could be iterated in insertion order. But that use case is probably rare enough that it doesn't need to be supported, especially if it requires extra space for a double ended linked list per node.
Still, the API for neighbors is a little confusing, I think it might be better if it was called neighbors_rev? Would make code more understandable by itself without having to refer to the docs, and would leave open the possibility of implementing a neighbors that iterated in insertion order.

Anyway since the main motivation for this doesn't apply, (in retrospect, should have been obvious! whoops) I'll close this issue.

Hey, I wrote a brief reply to you here but it appears I didn't hit send. I was saying, two extra fields in a Node isn't necessarily that bad; edges normally outnumber nodes and already use four index fields.
The reason the neighbor order is documented is that it was requested if the current order could be documented and possibly relied upon. We note that it only makes sense for directed graphs.

Sorry I opened and closed this one in a hurry.
It's not as critical as I originally thought but could still be a nice little improvement, especially if you think the extra index fields aren't a big deal.
It's good that the order is documented and can be relied on but it's easy to miss when just reading through code. I can do neighbors().iter().collect().reverse() to get what I want, but it would be nice to be able to rely on neighbors() directly, both because it's more efficient but also because I don't need to document why I'm reversing it on my end.
The worst part of changing it might be that it would change the order without changing the API, could easily break someones code if they upgrade and depend on the existing ordering, but might still be worth it? Again I'd be happy to work on it if you think so.

What I heard here was that we could make it double ended or expose a reverse order than what exists, we don't need to change the order of .neighbors() for that.

Ok, I can't think of a good way to expose the reverse order, what were you thinking if not changing neighbors()? We could just add a new method neighbors_rev(), but that seems backwards to me.
Also, making the linked list double ended wouldn't be enough to be able to traverse it in both directions, we'd also need to add another set of indices to each edge to make it doubly linked. Which is possible, but might not be necessary in general, only to maintain the current behaviour.


[BUG] Call to a member function appendRow() on null (using latest package version)

I'm using this package to insert data into my excel sheet.
Had some issues, fixed them but ended up in this issue https://github.com/Maatwebsite/Laravel-Excel/issues/208 - I ended up with error the last guy on that issue had:
Call to a member function appendRow() on null
My code:
Excel::load($applicationPath, function($reader) {
    $reader->sheet('Sheet1', function($sheet) use ($reader) {
        $sheet->appendRow(1, [
	    'test1',
        ]);
   });
})->export('xls');

, where $applicationPath is the actual path to xls file.
I expect it to work, as I viewed examples in the official documentation (doesn't seem to be updated), tried dd($sheet), but it actually returns 'null'.
For me code seems to be in order, but yet it's somehow null.
Hoping to get this resolved soon.

Does Some shiiiit as sheet name actually exist?

@patrickbrouwers Thanks, it got resolved. Didn't think through about sheet naming (thought it would rename it).

Can you close the issue if it's resolved?

Thanks, @patrickbrouwers, but I have one more question, Could I add more Sheet after I load existing file?

@devvyd how to resolve it?

Call to a member function appendRow() on null

@devvyd How do you resolve this? I supply the sheetname but still facing the same error message


Game crashes when song loads

Describe your bug here.
everytime i enter a song once it loads it just crashes

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

invalid note textures/XML

how do i fix that?

by fixing up the animation names

i dont have adobe animate

then you will have to do it manually in the xml file

no way


undefined method validate_checks on puppet 5.5.7/6.0.3

The module fails with the following warning on puppet 5.5.7 and puppet 6.0.3:
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, undefined method `validate_checks' for Scope(Consul::Service[node_exporter]):Puppet::Parser::Scope (file: /etc/puppetlabs/code/environments/production/modules/consul/manifests/service.pp, line: 49, column: 3) (file: somewhere, line: 91) on node puppet.local

The related upstream bug report is https://tickets.puppetlabs.com/browse/PUP-9268. I assume this is already fixed with https://github.com/solarkennedy/puppet-consul/pull/444. I'm testing it at the moment.

Just confirmed it locally, #444 fixes this issue. I will prepare a new release.


exploitdb: 2023-07-12 -> 2023-07-18

Diff: https://gitlab.com/exploit-database/exploitdb/-/compare/refs/tags/2023-07-12...2023-07-18
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.


Boot Loader Specification support?

Does Tow-Boot support BOOT_LOADER_SPECIFICATION (originated from freedesktop)
This provides an already common standard out there, which should be sufficient enough even for embedded stuff.

Not yet. But maybe it shouldn't. Instead it would be better advised to run systemd-boot IMO.
In fact, in theory it should already be able to do it, but when I tried the NixOS tooling (or systemd's) failed to install.
And Tow-Boot, as a whole, targets "generic boot" scenarios. It's less intended for "embedded" uses, where the boot chain needs to be more strict and controlled by the project.
Not sure this adequately answers the underlying concerns.

Not yet. But maybe it shouldn't. Instead it would be better advised to run systemd-boot IMO.

I disagree. This is meant to be a specification implementable by multiple bootloaders, and writable by multiple distros/operating systems - so a generic standard, that Tow-Boot could just start supporting - this seems way cleaner than supporting yet another format, such as "extlinux.conf dd'ed to a block device".
Also, systemd-boot isn't supported on many embedded systems - only those with UEFI support, while u-boot is.

I guess I was right that, maybe from a lack of proper documentation on my part, you wouldn't see it as I do.
(I will answer in an order that better fits the narrative.)

I disagree. This is meant to be a specification implementable by multiple bootloaders

This is right. But Tow-Boot is not "a bootloader"... Maybe I should have named it "Tow-Firm"?
Just like U-Boot, it does much more important things, but it is named after the feature that is the "least important" to me...

Also, systemd-boot isn't supported on many embedded systems - only those with UEFI support, while u-boot is.

... and that is because any system supported by U-Boot, and thus Tow-Boot supports UEFI. This fact is the reason I don't think it is important that the firmware itself supports the protocol. To me Tow-Boot is "your BIOS", for your boring old computer. The fact that it knows how to boot a Linux kernel is an inconvenient truth.
So really, what Tow-Boot currently supports is whatever the default distroboot boot chain from U-Boot is.
Though I'm not saying there's no value in adding support for the boot loader specification. There would be. It would also have value upstream. What I'm saying is that it's not where my effort stands right now.
My main goals here are two fold:

Make booting to "a standard firmware interface" and "a standards-based OS" less confusing across the different platforms.
Work on the user interface of "a standard firmware interface".

For the former, it's already mostly done. Documentation is superficial, but present. You either install to the dedicated storage (SPI Flash) when present, or use the EBBR-compliant "shared storage" strategy, as a base image. That base image does not contain an operating system. It only contains enough to boot a standard image. The expectation is that the user boots a UEFI-based system from USB. Though since we're building upon the building blocks from U-Boot's generic distroboot, it continues supporting those other schemes too.
As for the user interface, some early work has already been done. Rather than dropping the user to a user-unfriendly shell for commands, "stopping" the boot process provides the user with a menu interface to select a boot source. Future goals include building a more in-depth interface to provide the "usual" options, like editing the boot order and saving it to the firmware's environment, or changing some hardware options (e.g. overclocking, changing some DT node values, changing config.txt nonsense on Raspberry Pi systems).
Anything else falls in the "sounds nice, but I don't have the time to dedicate for that".

this seems way cleaner than supporting yet another format, such as "extlinux.conf [...]".

I personally think supporting the UEFI iso on a USB drive is the cleanest and more standard alternative. Supporting the boot loader specification gives us compatibility where that exists. For now it generally requires a boot loader of some sort to know about that specification.
While the same is just about true for UEFI, the bigger difference is that UEFI already is deployed in different use cases on ARM platforms. So supporting UEFI boot as first-class citizen gives us better compatibility in the existing ecosystem. Any efforts producing an OS for UEFI works on those platforms too (given the same condition that e.g. mainline linux works on those, nothing different).

such as "extlinux.conf dd'ed to a block device".

Maybe I'm missing a detail here. Whats the difference between dd'ing an extlinux.conf-based image to block device, dd'ing a boot loader specification-based image to a block device or dd'ing a UEFI boot-based image to a block device?
Or rather what would a boot loader specification system provide that makes it different here?

Also, systemd-boot isn't supported on many embedded systems - only those with UEFI support, while u-boot is.

Right. I don't intend this opinionated distribution of U-Boot to replace U-Boot for all use cases! It's a superset building on top of U-Boot. For embedded uses I will continue suggesting working from U-Boot, or maybe using Tow-Boot as a base to build upon. Tow-Boot is a strongly opinionated firmware that aims to be "boring like your laptop's BIOS/UEFI (should be)".
Most of what I described here is already possible with U-Boot. The main difference with U-Boot as it is currently is that Tow-Boot has a tooling to build distribution-independent binaries for end-users.
I expect that in an embedded use case, the embedded product implementer will produce "freestanding" images, with everything already built-in. After all you don't want to go around installing an operating system after the fact on all those gizmos you produce :).

And to paraphrase more succinctly: "Yes, BLS would be good in U-Boot. I personally won't work on it in the foreseeable future"

I've just taken a look at the Boot Loader Specification. And there's one huge deficiency (shared with many other bootloadery bits). It assumes the device tree binary to be loaded is a static value, and not derived from other knowledge.
This means that with a BLS-following installation you have two choices:

Load a specific device tree binary from an hardcoded path.
Not load a device tree binary and hope the previous steps provide a good enough one for that generation.

This is probably the main advantage the non-standard extlinux.conf-compatible scheme has within U-Boot; it uses a firmware-provided dtb filename. And probably the most inconvenient truth about booting on ARM. Providing the "right" DTB for the kernel is a total mess (and another topic we shouldn't discuss in this particular issue).

With 2022.07, some yet-unexplored-by-me support for BLS has been added

https://source.denx.de/u-boot/u-boot/-/blob/v2022.07/doc/develop/bootstd.rst

Read the latest revision of the docs (might not apply to 2022.07) here

https://u-boot.readthedocs.io/en/latest/develop/bootstd.html#u-boot-standard-boot


TGIK 180: 1.23 review

Monday or Tuesday:

[x] Pick a topic and create/use an issue in the repo
[x] If applicable coordinate with an upstream project if they're interested in attending the show
[x] Create the graphic
[x] Schedule on Youtube
[x] Add scheduled episode to TGIK playlist on YT
[x] Create short link in rebrandly
[ ] Tweet about it from your personal account

[ ] Post tweets on internal #tgik slack channel and cc  Vykky

Before episode:

[ ] Create HackMD page for live notes.  Start with README template in this repo
Show Coordination with Assistant (if you have one)

[ ] Paste HackMD URL on internal #tgik channel
[ ] Assistant adds ~5-10 news items from around the web as possible "News of the Week"
[ ] Confirm show time and AV check
[ ] Last minute retweets or topic updates
[ ] Sync with external guest one last time if necessary

[ ] Get everything tested well before episode so you can debug
[ ] Use internal slack channel to ensure that AV se tup is good

After show (ideally right away but can wait until Monday):

Create/submit PR for this repo

[ ] Episode directory and README from hackmd
[ ] Any other files from the episode that might be useful
[ ] Update playlist.md with episode
Feel free to self merge

[ ] Edit YT description to point to episode directory here
[ ] OBS/OS Upgrade if applicable (Never on the day of a show)

Rey Lejano is joining us as 1.23 release lead.
His favorite enhancements:

Dual-stack IPv4/IPv6 is GA
PodSecurity Admission goes to beta (PSP replacement)
TTL Controller (Cleanup Jobs and Pods of Jobs) goes to GA
HPA v2 API is GA
Ephemeral Containers (kubectl debug) goes to beta
Auto remove PVCs from StatefulSets is intro'd as alpha
SLSA Level 1 compliance (provenance attestation files are generated that describe staging and release phases)

Here's the release blog: https://kubernetes.io/blog/2021/12/07/kubernetes-1-23-release-announcement/


Destructive defaults on 'kube-aws render'

I just accidentially ran kube-aws render without specifying whether i wanted to render the credentials or stack templates. The default now renders both, even if credentials already exist, overwriting the old credentials in the process.
I feel this is dangerous. We probably want to add a --force option to the kube-aws render credentials command.
Command output:
$ ./kube-aws render
WARNING: 'kube-aws render' is deprecated. See 'kube-aws render --help' for usage
Generating TLS credentials...
-> Generating new TLS CA
-> Generating new TLS assets
Success! Stack rendered to stack-template.json.

Next steps:
1. (Optional) Validate your changes to cluster.yaml with "kube-aws validate"
2. (Optional) Further customize the cluster by modifying stack-template.json or files in ./userdata.
3. Start the cluster with "kube-aws up".

Failing fast instead of implicitly overwriting previously generated assets also match the current behavior around kube-aws init, which fails when cluster.yaml exists.
Indeed It would be great to add!


Not a JPEG issue

bazel-bin/tensorflow/examples/image_retraining/retrain --image_dir /Training_image
Looking for images in 'non-human'
Looking for images in 'human'
Creating bottleneck at /tmp/bottleneck/non-human/Data__negatives_jpeg_cr_night_512x384_cr_night_512x384_rCR_m26_a10_d2005-04-07_t22-38_wN.jpg.txt
2017-05-09 01:56:48.890091: W tensorflow/core/framework/op_def_util.cc:332] Op BatchNormWithGlobalNormalization is deprecated. It will cease to work in GraphDef version 9. Use tf.nn.batch_normalization().
Not a JPEG file: starts with 0x89 0x50
Traceback (most recent call last):
File "/bazel-bin/tensorflow/examples/image_retraining/retrain.runfiles/org_tensorflow/tensorflow/examples/image_retraining/retrain.py", line 1105, in
tf.app.run(main=main, argv=[sys.argv[0]] + unparsed)
File "/bazel-bin/tensorflow/examples/image_retraining/retrain.runfiles/org_tensorflow/tensorflow/python/platform/app.py", line 48, in run
_sys.exit(main(_sys.argv[:1] + flags_passthrough))
File "bazel-bin/tensorflow/examples/image_retraining/retrain.runfiles/org_tensorflow/tensorflow/examples/image_retraining/retrain.py", line 844, in main
bottleneck_tensor)
File "bazel-bin/tensorflow/examples/image_retraining/retrain.runfiles/org_tensorflow/tensorflow/examples/image_retraining/retrain.py", line 469, in cache_bottlenecks
jpeg_data_tensor, bottleneck_tensor)
File "bazel-bin/tensorflow/examples/image_retraining/retrain.runfiles/org_tensorflow/tensorflow/examples/image_retraining/retrain.py", line 417, in get_or_create_bottleneck
bottleneck_tensor)
File "bazel-bin/tensorflow/examples/image_retraining/retrain.runfiles/org_tensorflow/tensorflow/examples/image_retraining/retrain.py", line 376, in create_bottleneck_file
raise RuntimeError('Error during processing file %s' % image_path)
RuntimeError: Error during processing file /Training_images/non-human/Data__negatives_jpeg_cr_night_512x384

How to fix this?

I'm guessing the problem that is your image is...drumroll...not a jpeg.
It's probably a png.  I recommend using tf.image.decode_image if you have a dataset that mixes png and jpeg.  I will fix the error message to explicitly say this.

@petewarden Any objections to me changing the example to tf.image.decode_image?  Too many people have png-jpegs.

@girving No, this seems like a good change to me, thanks!

decode_jpeg now handles pngs without comment.

Here is a python script to identify those fault jpg images in a directory.
`  import glob
import os
import re
import logging
import traceback
filelist=glob.glob("/path/to/*.jpg")
for file_obj in filelist:
  try:

		jpg_str=os.popen("file \""+str(file_obj)+"\"").read()
		if (re.search('PNG image data', jpg_str, re.IGNORECASE)) or (re.search('Png patch', jpg_str, re.IGNORECASE)):
			print("Deleting jpg as it contains png encoding - "+str(file_obj))
			os.system("rm \""+str(file_obj)+"\"")
  except Exception as e:
	logging.error(traceback.format_exc())
print("Cleaning jps done")`

@Mohit-Ak Note that you don't need to do this anymore; Tensorflow's decode_jpeg handles PNGs.

But I faced the same issue when I used the Object Detection API.  This happens on the Cloud Training when it reads the ".record" file.
I don't know the place where the object detection API uses it but it still has the issue. I can give you the logs if you want.

Ah, the Object Detection API may be parsing the jpeg outside of TensorFlow.

Here are the cloud logs. Just for the reference. We could do a ctrl+F for "JPEG" and find a lot of matches.
21:44:47.081 - Not a JPEG file: starts with 0x89 0x50
Traceback (most recent call last): File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main "main", fname, loader, pkg_name) File "/usr/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/root/.local/lib/python2.7/site-packages/object_detection/train.py", line 198, in  tf.app.run() File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 44, in run _sys.exit(main(_sys.argv[:1] + flags_passthrough)) File "/root/.local/lib/python2.7/site-packages/object_detection/train.py", line 194, in main worker_job_name, is_chief, FLAGS.train_dir) File "/root/.local/lib/python2.7/site-packages/object_detection/trainer.py", line 296, in train saver=saver) File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/slim/python/slim/learning.py", line 804, in train raise File "/usr/lib/python2.7/contextlib.py", line 35, in exit self.gen.throw(type, value, traceback) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/supervisor.py", line 960, in managed_session self.stop(close_summary_writer=close_summary_writer) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/supervisor.py", line 788, in stop stop_grace_period_secs=self._stop_grace_secs) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/coordinator.py", line 386, in join six.reraise(*self._exc_info_to_raise) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/queue_runner_impl.py", line 234, in _run sess.run(enqueue_op) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 767, in run run_metadata_ptr) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 965, in _run feed_dict_string, options, run_metadata) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1015, in _do_run target_list, options, run_metadata) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1035, in _do_call raise type(e)(node_def, op, message) InvalidArgumentError: Invalid JPEG data, size 881303 [[Node: case/If_0/DecodeJpeg = DecodeJpeg[acceptable_fraction=1, channels=3, dct_method="", fancy_upscaling=true, ratio=1, try_recover_truncated=false, _device="/job:master/replica:0/task:0/cpu:0"](case/If_0/DecodeJpeg/Switch:1, ^case/Assert/AssertGuard/Merge)]] Caused by op u'case/If_0/DecodeJpeg', defined at: File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main "main", fname, loader, pkg_name) File "/usr/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/root/.local/lib/python2.7/site-packages/object_detection/train.py", line 198, in  tf.app.run() File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 44, in run _sys.exit(main(_sys.argv[:1] + flags_passthrough)) File "/root/.local/lib/python2.7/site-packages/object_detection/train.py", line 194, in main worker_job_name, is_chief, FLAGS.train_dir) File "/root/.local/lib/python2.7/site-packages/object_detection/trainer.py", line 184, in train data_augmentation_options) File "/root/.local/lib/python2.7/site-packages/object_detection/trainer.py", line 59, in _create_input_queue tensor_dict = create_tensor_dict_fn() File "/root/.local/lib/python2.7/site-packages/object_detection/builders/input_reader_builder.py", line 63, in build return tf_example_decoder.TfExampleDecoder().decode(string_tensor) File "/root/.local/lib/python2.7/site-packages/object_detection/data_decoders/tf_example_decoder.py", line 121, in decode tensors = decoder.decode(serialized_example, items=keys) File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/slim/python/slim/data/tfexample_decoder.py", line 418, in decode outputs.append(handler.tensors_to_item(keys_to_tensors)) File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/slim/python/slim/data/tfexample_decoder.py", line 302, in tensors_to_item return self._decode(image_buffer, image_format) File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/slim/python/slim/data/tfexample_decoder.py", line 345, in _decode pred_fn_pairs, default=default_decoder, exclusive=True) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/control_flow_ops.py", line 2973, in case case_seq = _build_case() File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/control_flow_ops.py", line 2955, in build_case name="If%d" % i) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/control_flow_ops.py", line 1738, in cond orig_res, res_t = context_t.BuildCondBranch(fn1) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/control_flow_ops.py", line 1639, in BuildCondBranch r = fn() File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/slim/python/slim/data/tfexample_decoder.py", line 323, in decode_jpg return image_ops.decode_jpeg(image_buffer, self._channels) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/gen_image_ops.py", line 345, in decode_jpeg dct_method=dct_method, name=name) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/op_def_library.py", line 763, in apply_op op_def=op_def) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 2327, in create_op original_op=self._default_original_op, op_def=op_def) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 1226, in init self._traceback = _extract_stack() InvalidArgumentError (see above for traceback): Invalid JPEG data, size 881303 [[Node: case/If_0/DecodeJpeg = DecodeJpeg[acceptable_fraction=1, channels=3, dct_method="", fancy_upscaling=true, ratio=1, try_recover_truncated=false, _device="/job:master/replica:0/task:0/cpu:0"](case/If_0/DecodeJpeg/Switch:1, ^case/Assert/AssertGuard/Merge)]]

So that's either an older version of TensorFlow, a different of corruption (not related to PNGs), or a different bug.

But I cloned it just yesterday and it got fixed after running the above script.

Then it's a different bug.  Care to diagnose why the format classification logic isn't working?  https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/kernels/decode_image_op.cc#L156

Here is a python script to identify those fault jpg images in a directory.
`
import glob
import os
import re
import logging
import traceback
filelist=glob.glob("/path/to/*.jpg")
for file_obj in filelist:
  try:

		jpg_str=os.popen("file \""+str(file_obj)+"\"").read()
		if (re.search('PNG image data', jpg_str, re.IGNORECASE)) or (re.search('Png patch', jpg_str, re.IGNORECASE)):
			print("Deleting jpg as it contains png encoding - "+str(file_obj))
			os.system("rm \""+str(file_obj)+"\"")
  except Exception as e:
	logging.error(traceback.format_exc())
print("Cleaning jps done")`

Hi
I am using your code but error occurs no file name exists

Locking as this is a bug solved over 2 years ago. Please open a new issue, filling in all of the template


BUG: bash.sh: array(val val val) -> array=(val val val)

Array definition missing= sign. https://www.gnu.org/software/bash/manual/html_node/Arrays.html

Thanks a lot! :-)
What do you think about this repository? How could I improve it?

No problem. It's good. No suggestions for now


Norm issues

:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/Cards/cards-reference.md
:warning:Warning

Details

msteams-platform/assets/images/Cards/hero.png
:white_check_mark:Succeeded

msteams-platform/assets/images/compose-extensions/ceflow.png
:white_check_mark:Succeeded

msteams-platform/scenarios/lob-workflow.md
:white_check_mark:Succeeded

msteams-platform/concepts/Cards/cards-reference.md

Line 41: [Warning] Invalid file link:(~/concepts/cards/cards-actions).
Line 45: [Warning] Invalid file link:(~/concepts/cards/cards-format).
Line 67: [Warning] Invalid file link:(~/concepts/cards/cards-actions#adaptive-card-actions).
Line 217: [Warning] Invalid file link:(~/assets/images/cards/hero.png).
Line 225: [Warning] Invalid file link:(~/concepts/cards/cards-format).
Line 374: [Warning] Invalid file link:(~/concepts/cards/cards-format).
Line 386: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 475: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 512: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-bot).
Line 542: [Warning] Invalid file link:(~/concepts/cards/cards-format).

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


once Russian 4.0 is live, run script to add language to list on all published translations

The language should be listed as русский (note lowercase).

Done! Note that р is not p, so it appears later in the language list than one might expect.


Draw a bonding box around object

Like excali draw, we need to add a image to move to reduce the size of the object once created.

creating a box where you can enlarge minify the object using the different scale points present here.

can you please elaborate about the issue...

can you see the small handles around the big square which help to expand the figure add an option to incorporate this.


NEW SQL BOOK IN BENGALI

What does this PR do?
Add SQL book in the Bengali language
For resources
Description
A complete resource to learn SQL in Bengali.
Why is this valuable (or not)?
A great resource for learning SQL
How do we know it's really free?
It is a free website
For book lists, is it a book? For course lists, is it a course? etc.
it is a free book to learn the complete SQL in Bengali and it also has an index
Checklist:

[☑] Read our contributing guidelines.
[☑] Search for duplicates.
[☑] Include author(s) and platform where appropriate.
[☑] Put lists in alphabetical order, correct spacing.
[☑] Add needed indications (PDF, access notes, under construction).
[☑] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Thanks, and welcome to free-programming-books!

please merge the pr

Thanks, and welcome to free-programming-books!

Thank you so much .can you please merge the PR.


chore: add new test for #1771

PR Checklist

[x] The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
[x] There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
[x] You have signed the CLA.
[x] All existing tests are passing: https://github.com/NativeScript/nativescript-angular/blob/master/DevelopmentWorkflow.md#running-the-tests
[x] Tests for the changes are included.

@DimitarTodorov, @zbranzov, decreasing from --timeout 140000 to --timeout 60000 is not a good idea a and will make the tests very flaky.
Usually there could be few steps that could slow down tests and have nothing to do with the test.
For example when we are trying to start/ restart Appium server it will take a lot of time or for some reason the device should be started/restarted. This will reflect to the test execution time taking a few minutes. Running tests in parallel also slows down the execution time.
If some of the test is failing because some element is not visible, sometime it takes a lot of execution time as well and at the end because of one test failure you will not have the result of the rest of the rest  of tests and e.t.c.
Also adding a new test will require to change execution time each time.
The good part here is that this will not take an effect of the CI execution but still you are not familiar with the test and trying to execute test and we need to start device and etc it will be very frustrating.


which version of python should I use?

when I use python3.11, i meet this error:
Collecting numpy==1.22.4 (from -r requirements.txt (line 4))
Downloading numpy-1.22.4.zip (11.5 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 11.5/11.5 MB 44.9 kB/s eta 0:00:00
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [86 lines of output]
:66: RuntimeWarning: NumPy 1.22.4 may not yet support Python 3.11.
Running from numpy source directory.
running egg_info
running build_src
INFO: build_src
creating numpy.egg-info
writing numpy.egg-info/PKG-INFO
writing dependency_links to numpy.egg-info/dependency_links.txt
writing entry points to numpy.egg-info/entry_points.txt
writing top-level names to numpy.egg-info/top_level.txt
writing manifest file 'numpy.egg-info/SOURCES.txt'
/usr/local/Cellar/python@3.11/3.11.2_1/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/setuptools/command/egg_info.py:643: SetuptoolsDeprecationWarning: Custom 'build_py' does not implement 'get_data_files_without_manifest'.
Please extend command classes from setuptools instead of distutils.
warnings.warn(
INFO: unifing config_cc, config, build_clib, build_ext, build commands --compiler options
INFO: unifing config_fc, config, build_clib, build_ext, build commands --fcompiler options
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in
main()
File "/usr/local/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
return hook(config_settings)
^^^^^^^^^^^^^^^^^^^^^

python3.9 is ok， if you must use a more advanced version, address your dependency issue between different modules


Error when building maven project

When I try to build maven I'm getting this message: The POM for com.sun.xml.bind:jaxb-osgi:jar:2.2.10 is invalid, transitive dependencies (if any) will not be available
Rest assured versions I've tried: 4.0.0 and 4.1.0
When I remove rest assured from my pom. The warning disappear.
Last time I tried building project on Friday (8/30/19) It was working fine. I believe the new changes could lead to the issue.

This should be fixed in version 4.1.1. Until then try version 4.1.1-SNAPSHOT after having added the following maven repo:
<repositories>
        <repository>
            <id>sonatype</id>
            <url>https://oss.sonatype.org/content/repositories/snapshots/</url>
            <snapshots />
        </repository>
</repositories>

or you could excluding com.sun.xml.bind:jaxb-osgi:jar file if you're not using OSGi.

@johanhaleby Thank you sir!


✨ New file without saving it

Description
A feature request about creating unnamed files for some temporary notes. Like in Sublime: just create a tab, put content which not intended to be saved, without requesting the filename to save it.
Alternatives Considered
No response
Additional Context
No response
Screenshots
No response

Closing. Duplicated of #1070


Change coachMarksViewController to be weak

To fix issue #90

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@e8b448d). Click here to learn what that means.
The diff coverage is 53.33%.

@@           Coverage Diff            @@
##             master     #99   +/-   ##
========================================
  Coverage          ?   79.1%
========================================
  Files             ?      26
  Lines             ?    1321
  Branches          ?       0
========================================
  Hits              ?    1045
  Misses            ?     276
  Partials          ?       0

Flag
Coverage Δ

#ios
79.1% <53.33%> (?)

Impacted Files
Coverage Δ

Sources/Managers/FlowManager.swift
69.04% <53.33%> (ø)

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 e8b448d...cdc31b0. Read the comment docs.


Replace From<Rgba8> for PremulColor with From<PremulRgba8>

Having the From<Rgba8> was unintentional and should have been From<PremulRgba8>.
A trait impl can't be deprecated with an attribute, so just note it in the doc comment.

Alternatively, we could keep the From<Rgba8> ... but I don't see much value in doing so.
If we merge this one, then I'll file an issue for the 0.3.0 milestone to remind us to remove the code.

We could just remove this and make the next release 0.3.0. I don't think there much cost to that?

I don't want to do a 0.3.0 yet ... at the least, I'd have to deal with ParseError changes and I want a fairly quick 0.2.1 release.


[MultiversX]: Add support for guarded transactions.

Description

This PR brings some support for crafting guarded transactions. The so-called guarded transactions are transactions whose sender is a guarded account. Such a guarded account can only have its transactions processed if co-signed by the guardian account.
Applications that use wallet-core to create & sign transactions can benefit from these changes to support the use case of guarded transactions / guarded accounts (e.g. this use case will be supported in xPortal).

The Transaction object has been extended to include a new field, called guardian.
The Serialization logic has been fixed to correctly include the options (and the new guardian field).
The default Transaction.version is changed from 1 to 2. Version == 2 means "transactions that support options". Developers using GenericAction to create transactions can still provide a different version, if desired.
If the guardian field is detected on the SigningInput, the TransactionFactory applies the "guarded" option on the Transaction option.
Unit tests have been adjusted (and extended).
Refactoring: we've removed GasEstimator and integrated its logic within TransactionFactory. NetworkConfig has been renamed to TransactionFactoryConfig (and extended with additional setters & getters). These changes do not impact (from our understanding) the interface exposed to Swift / Kotlin.

How to test

Running the unit tests, and performing a smoke test (e.g. sending a regular transaction) upon integrating the updated wallet-core in the mobile application. The mobile application does not need to populate the newly added field - only if implementing the new, non-trivial (actually, quite complex) use-case of guarded transactions / guarded accounts is desired.
Types of changes

New feature (non-breaking change which adds functionality)

Theoretically - non-breaking.

Breaking change (fix or feature that would cause existing functionality to change)

Practically, from the perspective of the C++ API, it's a breaking change, since the constructor of TransactionFactory has been altered. However, the Swift / Kotlin code should not be affected by this change.
Checklist

[ ] Create pull request as draft initially, unless its complete.
[x] Add tests to cover changes as needed.
[ ] Update documentation as needed.
[ ] If there is a related Issue, mention it in the description.

If you're adding a new blockchain

[ ] I have read the guidelines for adding a new blockchain.

can you sync with last master please?


Array parameters do not work on OS X v6.0.0-beta8

Steps to reproduce
PS > cat test.ps1
Param(
  [Parameter(Mandatory=$true)][string[]][ValidateSet("a", "b")] $arrParam
)

Begin {
  $arrParam
}
PS > powershell ./test.ps1 -arrParam a
a
PS > powershell ./test.ps1 -arrParam b
b
PS > powershell ./test.ps1

cmdlet test.ps1 at command pipeline position 1
Supply values for the following parameters:
arrParam[0]: a
arrParam[1]: b
arrParam[2]:
a
b
PS > powershell ./test.ps1 -arrParam a,b
./test.ps1 : Cannot validate argument on parameter 'arrParam'. The argument "a,b" does not belong to the set "a,b" specified by the ValidateSet attribute. Supply an argument that is in the set and then tr
y the command again.
    + CategoryInfo          : InvalidData: (:) [test.ps1], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,test.ps1

Expected behavior
PS > powershell ./test.ps1 -arrParam a,b
a
b

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.0-beta.8
PSEdition                      Core
GitCommitId                    v6.0.0-beta.8
OS                             Darwin 16.6.0 Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

If you call your script from within PowerShell, it works as expected.  When using -File with PowerShell.exe the arguments are passed as string literals (although $true and $false are special cased) to the script as arg values.  This is currently by design(see https://github.com/PowerShell/PowerShell/issues/4036#issuecomment-311759499).  Workaround is to use:
powershell -c ./test.ps1 -arrParam a,b

This works as you expect.

Why does it then differ from the behavior on Windows?
On Oct 6, 2017 19:56, "Steve Lee"<EMAIL_ADDRESS>wrote:

If you call your script from within PowerShell, it works as expected. When
using -File with PowerShell.exe the arguments are passed as string
literals (although $true and $false are special cased) to the script as arg
values. This is currently by design(see #4036 (comment)
https://github.com/PowerShell/PowerShell/issues/4036#issuecomment-311759499).
Workaround is to use:
powershell -c ./test.ps1 -arrParam a,b
This works as you expect.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PowerShell/PowerShell/issues/5032#issuecomment-334811606,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAygxxNec8qBtVxPgYoxoqLN316VKIxks5splvZgaJpZM4PwKXK
.

I'm seeing the same behavior on Windows PowerShell and PSCore6 on Win10.  Can you provide more details?

On Windows I have: PSVersion                      5.1.15063.608
I guess that explains the difference.