Send Presentation fails

I tried to send a presentation of a bank account credential back from alice back to contoso, however the state of the presentation/proof record remains at "request_received"

ACA-Py Log
2020-09-14 16:01:45,984 aiohttp.access INFO <IP_ADDRESS> [14/Sep/2020:16:01:45 +0000] "POST /present-proof/send-proposal HTTP/1.1" 200 1154 "-" "okhttp/4.8.1"
2020-09-14 16:01:46,632 aries_cloudagent.messaging.base_handler INFO Received presentation request message: {"@type": "did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation", "@id": "6700bf15-4af2-4a86-bd04-2aceb60656bf", "~thread": {"thid": "aeeb28c0-0dca-44a1-996c-59d96007e97d"}, "request_presentations~attach": [{"@id": "libindy-request-presentation-0", "mime-type": "application/json", "data": {"base64": "eyJuYW1lIjogInByb29mLXJlcXVlc3QiLCAidmVyc2lvbiI6ICIxLjAiLCAibm9uY2UiOiAiNzUwOTU1ODQyMzgzMjUyOTg3MDk0MjQ1IiwgInJlcXVlc3RlZF9hdHRyaWJ1dGVzIjogeyIwX2JpY191dWlkIjogeyJuYW1lcyI6IFsiYmljIiwgImliYW4iXSwgInJlc3RyaWN0aW9ucyI6IFt7ImNyZWRfZGVmX2lkIjogIk02TWJlM3F4N3ZCNHdwWkY0c0JSanQ6MzpDTDo1NzE6YmFua19hY2NvdW50X25vX3Jldm9jIn1dfX0sICJyZXF1ZXN0ZWRfcHJlZGljYXRlcyI6IHt9fQ=="}}]}
2020-09-14 16:01:46,633 aiohttp.access INFO <IP_ADDRESS> [14/Sep/2020:16:01:46 +0000] "POST / HTTP/1.1" 200 149 "-" "Python/3.6 aiohttp/3.6.2"
2020-09-14 16:01:46,666 indy.libindy.native.indy.services.anoncreds.prover INFO 	src/services/anoncreds/prover.rs:445 | name: None, names: Some(["bic", "iban"])
2020-09-14 16:01:46,681 aries_cloudagent.core.conductor ERROR Exception in message handler:
Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/core/dispatcher.py", line 178, in handle_message
    await handler(context, responder)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/protocols/present_proof/v1_0/handlers/presentation_request_handler.py", line 97, in handle
    holder=await context.inject(BaseHolder),
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/protocols/present_proof/v1_0/util/indy.py", line 54, in indy_proof_req_preview2indy_requested_creds
    name = indy_proof_request["requested_attributes"][referent]["name"]
KeyError: 'name'
2020-09-14 16:01:46,681 aries_cloudagent.core.conductor ERROR DON'T shutdown on KeyError 'name'
2020-09-14 16:01:46,681 aries_cloudagent.core.dispatcher ERROR Handler error: Dispatcher.handle_message
Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/core/dispatcher.py", line 178, in handle_message
    await handler(context, responder)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/protocols/present_proof/v1_0/handlers/presentation_request_handler.py", line 97, in handle
    holder=await context.inject(BaseHolder),
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/protocols/present_proof/v1_0/util/indy.py", line 54, in indy_proof_req_preview2indy_requested_creds
    name = indy_proof_request["requested_attributes"][referent]["name"]
KeyError: 'name'

Once again
https://github.com/hyperledger/aries-cloudagent-python/issues/704
We have to wait for aca-py 0.5.5, as the issue was merged 12 days ago and there was a new beta tagged https://hub.docker.com/r/bcgovimages/aries-cloudagent/tags it could be that that one already has the fix.

Ah sorry I forgot... I didn't realize that Alice has two Bank Account Credentials in her Wallet.
Brings up #47

I just checked this is fixed with aries-cloudagent:py36-1.15-0_0.5.5-beta1. The compose file already has that version, I also changed this in the agebcy.


[RFC ...] no-response bot, etc.

I think it would be ideal to use the no-response bot by Probot to help manage open questions and issues.
Unfortunately it does not seem to give warning before closing: probot/no-response#30
As a side point, I personally do not really like to use the stale bot. Here is a nice argument that I found against using the stale bot: https://www.tzeyiing.com/posts/thoughts/stale-bot-for-projects/

Here is my sentiment about repo bots in general (not so positive), finally seems to be echoed by others: https://twitter.com/brodybits/status/1227940381326823424


tweetdeck support

it would be nice to also have tweetdeck support

FYI: You can put the distinguished "Paid" badge instead of the "Verified" badge on the user icon by installing browser extension named BetterTweetDeck:

https://twitter.com/BetterTDeck/status/1591747755864907777
https://github.com/eramdam/BetterTweetDeck/releases/tag/4.9.0


Link libsodium statically

For use in anatomy-ambiata, among other reasons. Consider whether it's
worth switching to the latest version at the same time.

#67


Replace all connection handler backpressure logic with pipes

Once in a blue moon you really end up killing two birds with one stone.  In a nutshell, this PR replaces all of the connection handler buffering and backpressure logic with the new reincarnation of pipes.  The end result is much cleaner code and the generalization of a pattern found in several places (buffering and backpressure) into a single solution.
Preface
Pipe[I,O] was originally created for streaming services: the idea being that a request or response could be streamed in/out without having to load the entire thing in memory before using it.  Pipe was the representation of the streaming data, where pieces of the message could be "pushed" into and "pulled" out of.  Originally created in version 0.6.0, Pipehas been heavily reworked and dramatically improved in the upcoming 0.9.0 release.  It has essentially transformed into a buffer with a monad-like interface that can efficiently handle backpressure.
Meanwhile, buffering and backpressure has been a central concern in the controller and service layers of the connection handler architecture.  To recap, the Controller layer is the part of a connection handler responsible for reading in raw data and decoding it into message objects like Http requests, and vise versa for encoding messages into raw data.  The Service layer takes the incoming request messages and processes them into response messages, dealing with all the logic to make sure responses are sent back in the right order.
Up until now buffering and backpressure between these layers have been handled somewhat clumsily.  For instance, Controller has a pushmethod that would return trueor false depending on whether the pushed message was successfully buffered or not.  It was then up to the service layer to deal with the result manually.  This also led to Controllerhaving a lot of exposed methods like pauseReads() and pendingBufferSize that led to a lot of weird logic, and probably a lot of weird edge cases.
Using Pipes in Controller and ServiceServer/ServiceClient
Well now all that is gone.  Instead now pipes are used as the interface between layers.  So now, for example, the service layer can simply access an outgoing Sink from the controller and push responses there.  Likewise, the controller uses an incoming Sink to push decoded messages.
On the client side, the biggest change is ServiceClient now maintains its own buffer for pending requests.  Previously it used the controller's buffer to do this, but again that led to a lot of logic bleedthrough.  But now with pipes the client can simply route it's pending pipe into the controller's outgoing pipe.
Additional Changes to Pipes
A few changes were made to pipes to get this all working.
The biggest change is to Source.pullWhile.  Instead of taking a function of type T => Boolean, it now takes a T => PullAction.  This gives the looping function greater control of the iteration process.  Most importantly, it can now decide to pull an item after receiving it by returning PullAction.PullContinue, which was very important when feeding a Source into a Sink.
A new method pullUntilNull has been created which is similar to pullWhile but is intended to be used to pull out any items currently buffered and not wait for more items afterwards.  It is mainly used by OutputController to pull out items to write to the output buffer.
Another new method Sink.valvewas created which essentially creates a new sink that splits into two sinks.  An item is only pushed if it can be pushed to both sub-sinks.  This is mainly used by ServiceClient to properly handle the sentBufferSize to limit the number of concurrently in-flight requests.
Performance
After some basic benchmarking, there appears to be no change in performance for a basic service.  I haven't done extensive benchmarking on the client yet, but initial results don't show anything drastic.
What's Next
This PR clearly the first of several, as there's definitely some cleanup work to do, but this PR is already large enough as is.

Current coverage is 82.59% (diff: 68.12%)

Merging #460 into develop will decrease coverage by 1.21%

@@            develop       #460   diff @@
==========================================
  Files            91         91
  Lines          4101       4194    +93
  Methods        3742       3854   +112
  Messages          0          0
  Branches        359        340    -19
==========================================
+ Hits           3437       3464    +27
- Misses          664        730    +66
  Partials          0          0

Powered by Codecov. Last update 7f4b819...21ba2fe

Added some more tests and fixed a few bugs.  Test coverage is not quite up to par, but I'm a bit hesitant to add more tests until more cleanup has been done and all the interfaces are more stable.


Sensor Steam

Good morning,
I have a simple question: how did you create the steam sensor?
Thanks in advance

To create the steam sensor you need to first install the custom integration.  You can refer to the README for the 2 methods of installation: https://github.com/boralyl/steam-wishlist?tab=readme-ov-file#hacs-installation
After the integration is installed you can go to the integrations page in your settings and click on the ADD INTEGRATION button, then search for "Steam Wishlist".  From there you will be guided through the process via the UI.  After you've done that the sensor will be created.

Thank you, I just understood, sorry for the inconvenience


Azure az commands work and azure automation (Runbooks)

Hi Team,
Could you please let me know whether we an run PowerShell scripts ,with az commands in runbook (automation ).
When i try to run, its showing as az commands not recognized

@fengzhou-msft please take a look

hi @nidiculageorge azure automation supporting python2, while azure cli is on python 3.x.

@yungezz is it possible to run powershell scripts with az commands in runbooks.When i try to run its showing as az command not found

Please see the attached screen shot

that's because azure cli isn't installed. hi @qwordy could you pls help to see is there way to install azure cli inside python2 runtime by pip?

@yungezz why are we using python 2 as its a powershell script that we are trying to run,these are the commands that we are trying to run
az vmss deallocate --resource-group aks-poc-seabnode --name aks-seabpocln-36792229-vmss
az vmss deallocate --resource-group aks-poc-seabnode --name aksakswin

I think powershell can run any command. I'll experiment.

@qwordy please check with az commands as its not runing in Runbook ,please refer the screenshot above

When I run this command to install azure cli. This command should run as an administrator.
Invoke-WebRequest -Uri https://aka.ms/installazurecliwindows -OutFile .\AzureCLI.msi; Start-Process msiexec.exe -Wait -ArgumentList '/I AzureCLI.msi /quiet'; rm .\AzureCLI.msi

I get an error.
Start-Process : This command cannot be run due to the error: The operation was canceled by the user.

Runbooks gallery contains many examples. But there is no CLI example.

can you try running commands using az as mentioned above

can you try running commands using az as mentioned above

The same result as you. Az is not installed be default. We need to install it first.

Where should we install and how that can be done

Please note we need to run powershell scripts in Azure run books with az commands as mentioned above

This is not a supported scenario for Azure execution. See https://docs.microsoft.com/en-us/azure/automation/automation-runbook-execution#using-executables-or-calling-processes and https://docs.microsoft.com/en-us/azure/automation/automation-runbook-execution#where-to-run-your-runbooks
If you don't want to or can't change your script to use the PowerShell equivalent commands, you will need to use a hybrid worker.

Thank @zjalexander for quick response. Do you have any plan to support CLI scripts in runbook?
@nidiculageorge You can try hybrid worker. It needs some configuration.
https://docs.microsoft.com/en-us/azure/automation/automation-hybrid-runbook-worker
Azure Pipelines is also an option. I have written bash script which contain CLI commands in Azure Pipelines. It can run successfully.

@qwordy @zjalexander what you are saying is,that we can configure powersell scripts with az commands in azure automation run books

@qwordy no plans at this time, the product group monitors feature requests here: https://feedback.azure.com/forums/246290-automation
@nidiculageorge If you install the azure cli on a machine, and configure that machine as a hybrid worker, and use that hybrid worker to execute a runbook - yes. There's a few considerations to take when using a hybrid worker so please review https://docs.microsoft.com/en-us/azure/automation/automation-hrw-run-runbooks,  especially the sections on permissions and authentication.

PowerShell is NOT portable. We shouldn't have to use a myriad of YOUR tools to support YOUR products. Please consider adding the CLI so we can all be sane with some consistency.

@zjalexander to finalize az commands wont work on Runbooks.Running CLI from our machines is not an option
Can you please clarify on my above question

@nidiculageorge Az (CLI) commands won't work on runbooks run in the Azure sandbox.


Disallow /dispatcher/invalidate.cache in publish-dispatcher default configuration

For security reason, /dispatcher/invalidate.cache should be disallowed within publish-dispatcher configuration. https://helpx.adobe.com/experience-manager/dispatcher/using/security-checklist.html
It's then up to the user to deploy a publish-dispatcher (dispatcher.any) config that opens it up if they need to invalidate cache from the outside.

Done. Included in 0.10.2 .


Prettier ignore mypy_cache

If people run MyPy in the repo, they'll have the folder .mypy_cache which Prettier will format and Git will try to add.

fyi @jakelishman

It's also hitting .github/**/*.yml files for me, if you care about those.  Those may well be deliberate, though.

It's also hitting .github/**/*.yml files for me, if you care about those. Those may well be deliberate, though.

Yep, deliberate. Same with README


feat(#672): Try To Locate The Bug With Truncated Classes

In this PR I add planty of tests that tries to reaveal or at least reproduce the problem with ClassFormatException.
However I didn't find the cause of the problem.
Also I removed redundant JVM -Xss option from integration tests. Hope it will help.
Related to #672.
History:

feat(#672): verify if standalone transformation of Application.xmir to bytecode doesn cause problems
feat(#672): one more attempt to reproduce the problem
feat(#672): add one more unit test
feat(#672): remove invoker.mavenOpts=-Xss256m option from invoker
feat(#672): fix all the code offences

PR-Codex overview
This PR updates Maven goals in multiple invoker.properties files, adds a new file format to include, refactors bytecode class names, and enhances test coverage for assembling XMIR to bytecode.
Detailed summary

Updated Maven goals in multiple invoker.properties files
Added new file format to include: **/*.xmir
Refactored bytecode class names
Enhanced test coverage for assembling XMIR to bytecode

The following files were skipped due to too many changes: src/test/resources/org/eolang/jeo/Application.xmir

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@volodya-lombrozo Hey there, thanks for your contribution! 👍 Here's the breakdown of your points: +4 base, -8 for exceeding 200 hits-of-code (you had 438!), -16 for no code review, and -16 for no reviewer comments. We bumped you up to +4 to keep you motivated. Remember, quality and speed matter! Next time, aim for fewer hits-of-code and get those reviews in. Your balance is now +148. Keep the contributions coming!


Support for Redis v7 and newer

Hey team 👋 I was trying to upgrade my cluster from Redis version 6.2.x to 7.0.x. But it seems like v7 is not supported by the operator yet. This is the error that I get:
E0817 14:03:24.673063       1 redisnode.go:247] readiness check failed, err:Readiness failed, cluster slots response err: response returned from Conn: unmarshaling message off Conn: cannot decode resp array into string

Do we have any plans on supporting Redis v7?
Thanks!

We currently don't have any use cases that require 7.x, so we haven't looked into it yet. I'm not sure how much effort it will take to support both 6.x and 7.x, but it's definitely something we should look into as there are some nice features in the new version. The only problem is that we have a lot of other issues on our plate at the moment and won't be able to dedicate time to this in the near term. This is something we can try to get in our Q4 agenda.

Hello, team.
Do you have any updates about this issue?
We need support redis v7 in operator.

I don't have an update on this issue. It looks like someone submitted a PR for it, but I think there's going to be more to it than simply changing the version. This repo is also not being actively maintained at the moment. I'm currently maintaining a fork here. I hope to get changes merged back here periodically. I'll gladly accept a PR for this too :)


Fix bugs

Fix bugs

Fixed css for each component its own
Fixed loot-tiers vendors
Fixed exception in accessing refImage.current.width inside observer
Fix group button img appearance in selected vs not selected state

.deploy to development

.deploy


iPhone 15 Pro Max simulator crash with newly-generated react-native project

Description
https://stackoverflow.com/questions/77095463/crash-when-running-react-native-app-on-iphone-15-pro-max-simulator
Thread 1: "Failed to load bounding path bitmap data from the asset manager for asset name: BoundingPathBitmap-1290x2796-430x932-3.00x"
It works on iPhone 15 Pro simulator - it seems to be a problem with the screen resolution of the iPhone 15 Pro Max (1290x2796px). But I cannot find these files for other resolutions, but they must exist somewhere because it does not fail to load the assets for other simulators.
React Native Version
0.72.4
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 13.5.2
CPU: (8) arm64 Apple M1
Memory: 126.17 MB / 16.00 GB
Shell:
version: 3.2.57
path: /bin/bash
Binaries:
Node:
version: 16.20.1
path: ~/.nvm/versions/node/v16.20.1/bin/node
Yarn:
version: 1.22.19
path: /opt/homebrew/bin/yarn
npm:
version: 8.19.4
path: ~/.nvm/versions/node/v16.20.1/bin/npm
Watchman:
version: 2<IP_ADDRESS>
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.12.1
path: /Users/nicholas/.rvm/gems/ruby-3.0.0/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 23.0
- iOS 17.0
- macOS 14.0
- tvOS 17.0
- watchOS 10.0
Android SDK: Not Found
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8512546
Xcode:
version: 15.0/15A240d
path: /usr/bin/xcodebuild
Languages:
Java:
version: 11.0.17
path: /usr/bin/javac
Ruby:
version: 3.0.0
path: /Users/nicholas/.rvm/rubies/ruby-3.0.0/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.4
wanted: 0.72.4
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false
Steps to reproduce
npx<EMAIL_ADDRESS>init MyReactNativeApp --template react-native-template-typescript && cd MyReactNativeApp && yarn && npx pod-install
Then open the ios folder in Xcode 15.0 and build for iPhone 15 Pro Max simulator and notice the runtime crash.
Snack, screenshot, or link to a repository
Do the above steps.

Hello @karatekid430. I'm sorry that you are encountering this issue, but I think it is something related to your local environment.
I just spin up a new app from 0.72.4 and one from the nightly of 2 days ago and they both work fine without a single change.

Nightly
0.72.4

Sorry, but I need a reproducer and a clear set of instruction to follow.
As shown above, I could spin up a new app using 0.72.4 and running it on an iPhone 15 Pro Max.
Also, the  --template react-native-template-typescript is not maintained anymore, as React Native is using Typescript by default nowadays. So it could be that the issue is due to the outdated template.

@cipolleschi everything works fine on simulators, app is crashing on real devices.

Can you try without the --template parameter?
Can you also share the crash report?

I successfully resolved this by running: sudo xcode-select -s /Applications/Xcode.app, might be worth a try if others hit this issue.


Is there an actual Getx widget

This is not really an issue with the package but i must say it's been bugging me. Is there an actual Getx widget. I know we have the Obx, Getbuilder and even MixinBuilder but i have never really come across the "Getx" widget even in the state management documentation.
I've heard it mentioned a couple of times on different tutorials and have even stumbled on some obsolete readme that makes a reference to it but haven't really seen it actually used.
Some clarification would be great. Thanks.

yes there is 👍
https://github.com/jonataslaw/getx/blob/master/documentation/en_US/state_management.md#using-the-values-in-the-view
And it behaves exactly like GetBuilder, but for obs values
i usually help with documentation here so could you tell where did you find that obsolete readme? if it was here in getx repository, then you could point it out to me so i can fix in my spare time 😄

GetX is used to initialize controllers with the "init" property if you are not using bindings.
GetX is used to access properties of other controllers.
Let's say you are in a View, which has its controller, for example, Home, and HomeController.
You need the UserController to retrieve the user's name.
You can wrap the widget in a GetX, so if the user changes the name in settings, the name will be changed in the welcome screen.
class UserController extends GetxController{
String name = "Jonny"
}

class HomeController extends GetxController{
final posts = <Posts>[];
[...]
}

class HomeView extends GetView<HomeController>{

build(context){

return Column(children:[
GetX<UserController>(builder:(userController) => Text("Welcome ${userController.name}")),
Listview.builder(
itemCount: controller.posts
[...]
])
}

}

Since this is not a feature request or bug description, and has been answered, I am closing this.

yes there is 👍
https://github.com/jonataslaw/getx/blob/master/documentation/en_US/state_management.md#using-the-values-in-the-view
And it behaves exactly like GetBuilder, but for obs values
i usually help with documentation here so could you tell where did you find that obsolete readme? if it was here in getx repository, then you could point it out to me so i can fix in my free time 😄

Hi, i don't really think it's an issue with github. Probably a relic on google's index. To be honest i really can't say i remember specifically how i got to that page 😅. Thanks for your help anyways


Paymet Url is not working, its showing 404 not found

Hey, I used this sdk, it was working fine in sandbox mode, but in the live mode the payment url is showing 404 not found, what could be the issue? and why the library doesnt accept public key? in the official php sdk there is a option to pass public key.

Hello!
Can you give me a small code snipper to reproduce the problem?
For the public key, I don't see where it is used in the requests to the API if I remember correctly so there was no need to configure it

Hey thanks for the quick response, i actually used the original sdk
HERE Is My code
exports.generateYouCanPayPaymentUrl = functions.https.onRequest(
async (req, res) => {
const ip = req.ip
cors(req, res, async () => {
const { userId, amount, order_id, selectedPlan } = req.body;
try {
const youCanPayment = new YouCanPay(
"priv_key"
);
const paymentUrl = await youCanPayment.getPaymentUrl(
{
amount: amount * 100,
currency: CurrencyCode.MAD,
order_id,
customer_ip: ip,
success_url: -----,
error_url: ----,
},
Lang.AR
);
res.json({ paymentUrl });
} catch (error) {
console.error(error);
res.status(500).json({ error: "Internal Server Error" });
}
});
}
);

I'd appreciate if you format the code using markdown, little bit hard to read like this

Not sure what exactly are you trying to do here, but this is not the correct library where you are opening an issue.
Closing unless I'm wrong

Yeah i actually used the original library https://github.com/lynvi/youcan-payment-nodejs-sdk.
let me try your library once if that works, its just that its hard to find someone who can help with node js implementation of youcanpay, any way thanks for your time.

Hurray, it worked, why i did not used your implementation, thanks buddy, well appreciated @mehdibo . keep up the good work.

@mehdibo Typo in the documentation
const token = await ycp.tokenizePayment({
  order_id: '',
  amount: 1337,
  currency: 'MAD',
  customer_ip: '<IP_ADDRESS>',
  // URL where to redirect to when payment is successful
  sucess_url: '',
  // URL where to redirect to when payment is not successful
  error_url: '',
  // Information about the customer
  customer: {
    name: 'Hmida Bar9al',
    address: 'Hay takadom',
    zip_code: '21',
    city: 'Fes',
    state: 'Chaouia-ourdigha',
    country_code: 'MA',
    phone: '06',
    email<EMAIL_ADDRESS>  },
  // Metadata that will be returned via the webhook
  metadata: {
    anything: 'some value',
  },
});

is this typo here in this key 'sucess_url' ? i assume its success_url instead, please confirm.

Yes it's just a typo.
https://github.com/skuidma/ycp-sdk-ts/blob/develop/src/types.ts

Hey @mehdibo , i am facing another issue, the thing is it works fine in the sandbox mode, but as soon as i switch to live mode it never hits the success url after payment.


Link to documentation is broken

The link to the documentation provided in your README.md is incorrect. It points to a 404 page.

@thismatters Can you like describe which link exactly?

I thought it was the read the docs link, but they all seem to be working now.

Read the docs is not working.

This project is no longer being maintained. Consider switching to its successor, whose docs are still active.


[TASK] FSM for docking task using YASMIN

Description of task
Continue to explore and learn how the YASMIN library works. Do so by developing a demo for the docking task at TACC. The demo should be similar to how we (auto) will handle the task in a real run, but since we cant yet rely on data from Perception you can use timers in the demo. The flow of the demo can be as follows:

Start by looking for the dock. This can be done by performing a search maneuver like the rectangular search for a set amount of seconds (for example 15).
When the dock is found go into a converging state where the drone will get to a certain distance to the dock. Starting off this can also be done with timer, but in the actual demo you will use the Velocity Controller for this state.
When close enough to the dock go into a setup state which will align the drone over the dock, such that it is ready to dock. This maneuver will be done by the DP Controller.
When the setup is right, go into docking state where the drone will perform the docking maneuver.
When the drone has landed on the dock go into the docked state.
(Bonus) Add a returning home state which will take the drone back to the starting point.

The demo will be tested in the simulator at the office.
Suggested Workflow

Outline the whole process with all necessary states with a drawing/figure. Figure out what actions to be done in each state and requirement for transition.
Discuss with the team on how to communicate states and transitions for the demo.
Implement and test that the state transitions work as intended.

Specifications
Specification for the demo

The starting position for the drone is (x ,y, z) = (29, 6, 0)
The dock is located at (x, y, z) = (5, 5, 10)
The distance to the dock to trigger transition from converging to setup can be set to 3 meters.
The dimensions for the pool in the simulator is 30x12x10 (L x W x H)

Contacts
@Andeshog
Code Quality

[ ] Every function in header files are documented (inputs/returns/exceptions)
[ ] The project has automated tests that cover MOST of the functions and branches in functions (pytest/gtest)
[ ] The code is documented on the wiki (provide link)

Just some food for thought after some of the things we learned when working on Beluga Mk2 and setting up the state machines for robosub:
More states usually lead to more clutter. Finding the "right" amount of states and what these should be is hard, while concluding on "lets just add another state" is easy. As an example, could "moving_to_dock", "returning_home", and "docking" all be captured in the state "moving_to_point"? (I don't know if that's feasible for this specific task, but it's something to think about).
In addition to being critical about what states you add, you might want to think about what events and effects you define. Ideally, all state transitions are triggered by external "events", i.e. the dp controller letting you know you've reached a setpoint. The output for a given state are called "effects", which could f.ex be firing up a dp controller to move to a specific point. If you were to check if you've reached the checkpoint internally, you suddenly need access to odometry, and end up "disconnecting" the fsm from the dp controller.
It is also very common to see an "error" state, but be wary of the implications there. Transitioning to an "error" state is equivalent to panicking / terminating a program and should act as a sink in the fsm, while transitioning to different states if something goes wrong is equivalent to a try-catch, and is a perfectly reasonable thing to have. The effects of the "error" state could be to shut down all non-essential systems and alert the user. The problem occurs when the "error" state is implemented in a way that allows the fsm to transition back out of the error state. In such a state machine, you shouldn't have transitioned into the "error" state to begin with - or maybe you don't need the "error" state at all.
If you model states/effects/events properly, you end up with guarantees like "only 1 controller is running at any given time". You also end up with robustness against errors (i.e. the only failure mode is fall over and die, look into exception handling vs fault tolerant design for more info)


Inc Sync: Xamarin IOS: queryid needs to be unique to work

Not sure if this is an issue or i am doing anything wrong.
I wanted to check how offline sync works and downloaded the todo sample for xamarin.ios.
Full sync works when I make the queryid = null, but for incremental sync to work, i need to make the queryid unique for everycall, something like this
await todoTable.PullAsync("allTodoItems" + counter, todoTable.CreateQuery());
counter = counter + 1;
i am incrementing the counter everytime, i refresh.
All the documentation out there does not say anything about the queryid being unique for inc sync to work.
Any explanation would be much appreciated.

Incremental Sync requires the query to be unique for it to work.  It's documented :-)


PSQLODBC Datatype Test for sys.ntext

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Can you please fix or modify this PR? You're proposing to push it to you're other branch and not main.

PR made to upstream.


Gradle FlutterTask is not cacheable

Use case

By default, the Gradle FlutterTask is not a cacheable task. This means that flutter builds take longer than necessary when running tasks that have the same inputs as cached outputs, impacting developer productivity.
Proposal

FlutterTask should be made cacheable. See Gradle Build Cache.

cc @GaryQian

@clayburn FlutterTask does cache. For example, you can try building new app made with a fresh run of flutter create. You will see that subsequent runs of flutter run or flutter build are extremely fast.
Can you provide more information on what app you are trying to build? Your particular scenario may be invalidating caches.


NP-85/Make AudioDescribed track obvious

Problem
As per issue #85, we need to provide a mechanism that will allow client applications to switch between main and audio described audio tracks, without needing to know the position from the manifest.
Solution
Added an AudioTrackType to represent the different audio track types, main and audio described, a unknown type has been added to take into account other types that might present themselves in the future. AudioTrackType is created passing in a given format.selectionFlags which is created based on the role.
The AudioTrackType is publically accessible through PlayerAudioTrack.audioTrackType.
A first class collection representing a List<PlayerAudioTrack> has been added. This includes several support methods:
containsPlayerAudioTrackWith(AudioTrackType) returns a boolean representing whether the underlying List<PlayerAudioTrack> contains a PlayerAudioTrack with the given AudioTrackType.
firstPlayerAudioTrackWith(AudioTrackType) returns either the first PlayerAudioTrack that contains the given AudioTrackType, wrapped in an Optional or Optional.absent.
Test(s) added
Yes, tested all of the newly added classes. Added a Fixture for the PlayerAudioTrack because it was being created in quite a few tests.
Screenshots
We now have the type shown in the audio selection.

Paired with
Nobody.

LETS DO THIS 🛥


host object may not contain hardware_info

In case the host just registered and didn't send hardware_info the host object returened from bm-inventory will not contain hardware_info filed.
This cause randome failures in the CI e.g.: http://<IP_ADDRESS>:8080/job/test-infra/620/console

Probably should be a function.

What do you mean?
It's one line.


transform inputs to sub-packages

Is your feature request related to a problem? Please describe.
I'm always frustrated that I have to change the format of my data when calling a method from a sub-package.
Describe the solution you'd like
I'd like the input-objects to be automatically transformed to the correct type by earthkit, usinng the functionality that is available in earthkit-data.
Describe alternatives you've considered
No response
Additional context
Implementation will require knowledge of the data formats required by the sub-package methods. This can be inspected using:

Type-setting
Consistant signitures in variable names, e.g. data = np.ndarray and dataarray = xr.DataArray
Bespoke setting at the function level

For efficient code implementation, it is probably best to use function wrappers instead of decorators. Decorators would require code additions for all functions in the sub-package, whereas a wrapped can be applied programatically. Negative aspect is it may be slower at importing.
Organisation
ECMWF

Hi @EddyCMWF , I saw your work in branch 6-transform-inputs-to-sub-packages but I am not sure this should be done in theearthkit repo itself. In my opinion earthkitshould not contain any Python code apart from simply importing the components. Besides, components should not depend on the existence of earthkit since we should be able to install them independently. Is it not possible to achieve what you want in one of the components that the others would use?

Maybe we could consider making a earthkit-utils ?


Race condition / crash in libeegeo when entering an indoor map before the streamed theme has streamed

Separated from previous issue: https://github.com/eegeo/eegeo.js/issues/14
"one more thing how can i directly show your eegeo dundee building directly by using this function
var entrance = event.entrance;
myMap.indoors.enter(entrance);
i mean how can i pass lat long of the building that i want to enter"
This jsfiddle shows how: https://jsfiddle.net/uygp3ut7/2/
However this js fiddle also demonstrates a critical race condition:
a) Enter indoor map before streamed theme has streamed
b) Assert in lib eegeo
This will be fixed as a priority.

This is now resolved, and the JS fiddle above no longer exhibits the reproduction steps.


Triple check that dnsmasq works properly as non-root

As LXD 2.8 will have dnsmasq running as a non-root user. We should be doing some extra upgrade testing to ensure that there will be no problem when switching from root owned to nobody owned dnsmasq.
Area to check are:

Change static assignment (causes dnsmasq to be signaled to re-read the files)
Change the logic a bit to select "lxd", then "nobody" and finally just run as "root". This should cover all cases including those of confined environments with limited users.

Jan 24 14:52:14 dakara dnsmasq[30048]: cannot read /var/lib/lxd/networks/lxdbr0/dnsmasq.hosts: Permission denied

So the change very much regressed dnsmasq by not letting it re-read its config post-start.

So we need to propagate execute permissions down the networks/ tree to allow traversal and then make sure the dnsmasq files are owned by the same user which runs the daemon.

Have you abandoned this idea?

No, it's been closed as it was implemented. dnsmasq in LXD usually runs as the lxd user.
root     1963759  0.4  1.0 2155212 174372 ?      Sl   10:14   0:38  \_ /var/snap/lxd/common/lxd.debug --logfile /var/snap/lxd/common/lxd/logs/lxd.log --group l
xd --debug
lxd      1963913  0.0  0.0   7436  1768 ?        Ss   10:14   0:00      \_ dnsmasq --keep-in-foreground --strict-order --bind-interfaces --except-interface=lo --pid-file= --no-ping --interface=lxdbr0 --dhcp-rapid-commit --listen-address=<IP_ADDRESS> --dhcp-no-override --dhcp-authoritative --dhcp-leasefile=/var/snap/lxd/common/lxd/networks/lxdbr0/dnsmasq.leases --dhcp-hostsfile=/var/snap/lxd/common/lxd/networks/lxdbr0/dnsmasq.hosts --dhcp-option-force=119,lxd, stgraber.net --dhcp-range <IP_ADDRESS>,<IP_ADDRESS>,1h --listen-address=fd42:4c81:5770:1eaf::1 --enable-ra --dhcp-range ::,constructor:lxdbr0,ra-stateless,ra-names -s lxd -S /lxd/ --conf-file=/var/snap/lxd/common/lxd/networks/lxdbr0/dnsmasq.raw -u lxd -g lxd

Recently we also added apparmor confinement on this process for extra security.


[JS] remove version number as it is not used

cc @trxcllnt

Codecov Report

Merging #3595 into master will increase coverage by 3.07%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master    #3595      +/-   ##
==========================================
+ Coverage   87.74%   90.82%   +3.07%
==========================================
  Files         667       71     -596
  Lines       82536     4935   -77601
  Branches     1069     1069
==========================================
- Hits        72422     4482   -67940
+ Misses      10003      447    -9556
+ Partials      111        6     -105

Impacted Files
Coverage Δ

js/src/vector/chunked.ts
83.56% <0%> (ø)
:arrow_up:

js/src/util/bn.ts
76.08% <100%> (ø)
:arrow_up:

python/pyarrow/ipc.pxi

cpp/src/arrow/csv/chunker-test.cc

cpp/src/parquet/column_page.h

cpp/src/parquet/bloom_filter-test.cc

cpp/src/arrow/array/builder_decimal.cc

cpp/src/plasma/client.cc

cpp/src/arrow/io/test-common.h

cpp/src/arrow/util/int-util-test.cc

... and 495 more

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 2b9155a...c7bb8db. Read the comment docs.


refractor:prettify all the files of the repo

Description
The repo contains many eslint and prettier errors, the command npm run format prettified all the files. I'm hoping to solve all the eslint errors.
Should I make a PR for this?
The files affected after prettifying were:
        modified:   .eslintrc.json
        modified:   .github/ISSUE_TEMPLATE/bug_report.md
        modified:   .github/ISSUE_TEMPLATE/feature_request.md
        modified:   .github/feature_request_template.md
        modified:   .github/pull_request_template.md
        modified:   CODE_OF_CONDUCT.md
        modified:   CONTRIBUTING.md
        modified:   README.md
        modified:   android/app/src/main/assets/capacitor.config.json
        modified:   capacitor.config.json
        modified:   package-lock.json
        modified:   package.json
        modified:   public/manifest.json
        modified:   src/App.js
        modified:   src/App.test.js
        modified:   src/Routes.js
        modified:   src/actions/accountActions.js
        modified:   src/components/Button/ButtonComponent.js
        modified:   src/components/auth/Auth.js
        modified:   src/components/courseCard/courseCard1.js
        modified:   src/components/courseDetails/schedule.js
        modified:   src/components/courseDetails/scheduleDetails.js
        modified:   src/components/wishlistCard/index.js
        modified:   src/config/index.js
        modified:   src/constants/index.js
        modified:   src/context/SettingsContext.js
        modified:   src/index.js
        modified:   src/layouts/MainLayout/BottomNav.js
        modified:   src/layouts/MainLayout/TopBar/Account.js
        modified:   src/layouts/MainLayout/TopBar/HeaderItems.js
        modified:   src/layouts/MainLayout/TopBar/Item.js
        modified:   src/layouts/MainLayout/TopBar/index.js
        modified:   src/layouts/MainLayout/index.js
        modified:   src/pages/CoursePageViewWithVideo/index.js
        modified:   src/pages/HomePage.js
        modified:   src/pages/HomeView/Hero.js
        modified:   src/pages/HomeView/NonHero.js
        modified:   src/pages/HomeView/index.js
        modified:   src/pages/PersonalPage.js
        modified:   src/pages/ProfilePage.js
        modified:   src/pages/WishlistPage.js
        modified:   src/pages/wishListView/index.js
        modified:   src/reducers/accountReducer.js
        modified:   src/reducers/index.js
        modified:   src/reportWebVitals.js
        modified:   src/services/authService.js
        modified:   src/setupTests.js
        modified:   src/store/index.js
        modified:   src/theme/index.js
        modified:   src/theme/shadows.js
        modified:   src/theme/typography.js
        modified:   src/utils/analytics.js
        modified:   src/utils/axios.js
        modified:   src/utils/bytesToSize.js
        modified:   src/utils/getInitials.js
        modified:   src/utils/settings.js
        modified:   src/utils/wait.js

Hey, @abhishekkumar08
We can better add prettier to the repo: https://www.npmjs.com/package/prettier
So whenever w e will run npm run format, It will automatically format the whole code.
We had already integrated prettier in codeforcause/codeforcause repo. You can have a look there.

was saying the same in #17

Hey, @abhishekkumar08
We can better add prettier to the repo: https://www.npmjs.com/package/prettier
So whenever w e will run npm run format, It will automatically format the whole code.
We had already integrated prettier in codeforcause/codeforcause repo. You can have a look there.

It's already there in this repo also, I only ran the command, seems like no one has used it till now. So asking to create a PR for the same.

was saying the same in #17

Yes look like he created the PR and didn't ran it.
@abhishekkumar08 You can create a PR for the same.

was saying the same in #17

Yes look like he created the PR and didn't ran it.
@abhishekkumar08 You can create a PR for the same.

Actually, there were some issues running lint that's why I did not run it. I was waiting for any maintainer's reply for the same. Now since @abhishekkumar08 has run it which solved most of the issues, still there are some issues that need to be sorted. I have also solved some of them but some errors required your guide to solve. I am creating a PR #61  for the eslint errors which I have already solved. Most of the remaining errors are related to props-validation. @Abhishek-kumar09 @Siddhant-K-code can you look into it and let me know what should I do further.


(WIP) LayoutXLM / LayoutLMv2 upgrade

Issue #, if available: #6
Since the original LayoutLM paper, there have been many interesting developments in multi-modal document AI: Notably LayoutLMv2, multi-lingual LayoutXLM, LayoutLMv3, and Amazon's own DocFormer!
A common feature of LLMv2+ is that visual page image features are expected even for fine-tuning tasks - requiring some significant changes from this original sample.
Description of changes:
Upgrade the sample to support LayoutLMv2 (for generally improved accuracy) and LayoutXLM (for multi-lingual use-cases).
Status and outstanding items:

[X] Batch and online thumbnail image generation and integration
[X] LLMv2 and LXLM can be fine-tuned and deployed into the pipeline
[X] Retain full LLMv1 support

[X] LLMv1 can be pre-trained, fine-tuned, deployed and used in some configuration
[X] (Bug Fixed) LLMv1 can be trained without setting dataloader_num_workers=0 hyperparam

[X] LLMv2 and XLM support some level of pre-training
[X] (Bug) LLMv2+ supports multi-GPU training (717e036 - current native PyTorch config, SMDDP untested)
[X] (Bug) Tokenizer padding and truncation settings are applied correctly - Tentatively fixed as of 717e036
[X] Notebook and doc updates to make v2/XLM the default

Testing done:
Under active development so expect bugs - but feedback in the thread welcome!

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This change:

Is far-reaching (as supporting LLM>v1 models requires additional image data modalities to be generated in the pipeline)
Should be non-destructive (as LLMv1 is still supported and the CDK pipeline can still be optimized towards it)
Has been under development & testing for a long time now and seems to be fairly stable
Has become the de-facto base for forward-looking changes

Therefore now merging 🥳


Feature/completion provider tests

Current coverage is 28.91% (diff: 100%)

Merging #30 into develop will increase coverage by 2.49%

@@            develop        #30   diff @@
==========================================
  Files            19         19
  Lines          1923       1923
  Methods         108        108
  Messages          0          0
  Branches        400        400
==========================================
+ Hits            508        556    +48
+ Misses         1415       1367    -48
  Partials          0          0

Powered by Codecov. Last update 794208e...59df048


add pt_br

Hi!
Sorry for answering so late, I saw your (already closed) PR just now. GitHub apparently thought I wouldn't want to be notified about any activity in this repository... Oh well.
I would be happy to merge this if you are still interested?


OSSM-673 Ensure galley can run on OCP 4.9

We should probably skip the TestIngress integration test now that we're explicitly disabling handling of Ingress resources.

Closed in favor of https://github.com/maistra/istio-operator/pull/855


Fix gcs vendoring

Didn't test this version. But at least bin/build did work again

Just seen I had my trivial workaround for having some cli from develop still in the repo.


nixos/matrix-synapse: preload jemalloc

Motivation for this change
This is the default in the upstreams docker image and claims to reduce
memory fragmentation and overall usage.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test matrix-synapse

Will this still work after https://github.com/NixOS/nixpkgs/pull/124416?

I seem to remember this being there before, which would imply it was removed. So I assume there was a reason for that?

Will this still work after #124416?

It should. jemalloc doesn't do Python specific code (AFAIK) but rather hooks into the general memory management (done by libc?). It is also common to use it when used on optimized Python interpreters. You can inspect the upstream synapse Dockerfile and go down the path to the base image. It seems to be working fine for them.

Added withJemalloc option, defaulting to true, as it seems to be the default of the upstream container.

Here is what Daniel Micay has to say about jemalloc: https://lists.torproject.org/pipermail/tor-dev/2019-August/013990.html

[...] I've made some substantial contributions to jemalloc upstream and wrote the integration into Rust. I'm deeply familiar with the design choices and implementation of jemalloc. Those design choices lead to having a memory allocator that's extremely friendly to exploitation. [...] It makes exploitation significantly easier overall than the traditional dlmalloc style design.

I'm not sure how relevant that is to using it as malloc for the Python interpreter. However, matrix-synapse is directly exposed to the internet, so it might be worth taking that into consideration.

It'd be a risk only if there's a heap security vulnerability in Python itself that would be exploitable from synapse, which sounds quite unlikely; or in a C Python extension used by synapse — I don't have numbers here, but would guess it to be quite unlikely too.
This being said, we should probably check that we see non-negligible benefits in at least one “normal-sized” deployment before merging (as opposed to matrix.org-sized deployment), because even though slim it's still a (slight) additional risk (by making exploitation of other vulnerabilities easier).

Ok, let's compromise: Add the option, default to false, so more people can give this a try if they want to.

https://developers.home-assistant.io/blog/2020/07/13/alpine-python/
Probably going to try the same with home-assistant.


feat: add isAwait to ForOfStmt and isRest to ParameterDecl

Partial #374
Adds support for the following syntax:

[x] for-await-of

for await (const a of b)

[x] rest parameter declarations

function foo(...rest) {}

[x] refactor: remove redundant clone functions and add missing validation to nodes

Should we fail the transpiler when these flags are true?

Done.


Dalaran dungeon portal on the right, near book, doesnt work

Closed by https://github.com/AzerothWarsLR/WarcraftLegacies/commit/0cc019eb2d6d96b1414e9191c8d760a5fdc3dac8.


Crypt passkey

#2

Manually merged in https://github.com/SuprDewd/simpletracker/commit/864ed91b9e4c8959f599bf209ef45fe3cb5ec019


about Recursive interpolation

Hello, does the interpolation algorithm you provided only train to generate one interpolated frame between two frames during training? I would like an algorithm that specifically generates multiple frames between two frames. Since I've never studied frame interpolation, I'd like to ask ：do all current frame interpolation algorithms train to generate one frame between two frames during training and generate multiple frames between two frames by recursive interpolation during testing? And is the number of frames generated by recursive interpolation limited, e.g. it must be the (2 to the power n)  - 1?

I'll close this, since it's not related to the codes in this repo. Feel free to contact me via email (in the Readme).


The Markdown formatting is not ignored in the issue title using the escape character. Example: `test`.

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
File: https://github.com/github/docs/blob/main/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md#ignoring-markdown-formatting
Page: https://github.com/github/docs/blob/main/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md#ignoring-markdown-formatting
The above-mentioned section talks about how one can tell Github to ignore the Markdown by using \ but using this character. This works everywhere but not in the title of the issue and I am assuming in the title of the PRs.
An example of the issue is in the title of this issue itself.
What changes are you suggesting?
The Github should acknowledge the escape character (\) as it does at the other places and allow the users to ignore the Markdown formatting in the title of the issues.
Additional information
No response

Thanks for the issue @5AbhishekSaxena, I'll get this triaged for 👀

No problem @steveward, happy to contribute 😁.

Thanks for opening this issue! You or anyone else is welcome to note this exception in the docs.

I was thinking instead of adding this exception in the docs, the issue should be fixed in the code itself where the backticks are processed which formats the title of the issue/pull but acknowledge the escaping character, and skip the formatting.

I have raised a PR which adds a note informing the user about the issue.  I have also started a discussion on the community page which can be found here: https://github.com/orgs/community/discussions/54689.


Fix broken links

Fixing some broken links in the porch install and user guides.

Site build failed with broken links. Real or just rerun?

The failure looks like a timeout. Trying a rerun


(Question) Calling one task from another

I'd like to call a task from another task. Is this supported ?
Usually, this would happen based on some logic within an embedded bash script. It would be conditional, so it is not a dependency.
Thanks a lot.

Hi there!
Unfortunately, this is not currently supported. One workaround is to re-invoke just from within the recipe:
bar:
  echo bar

foo:
  # do stuff
 just bar
  # do stuff

This is definitely an unfortunate limitation, and a commonly requested feature. I haven't been able to think of a good way to implement it, however, since just doesn't parse at all recipe bodies. It just extracts them as lines of text and passes them to the shell.
This has the nice effect that just is completely agnostic to the syntax of the shell. The downside, however, is that there isn't to add just functionality in the middle of a recipe.


Some problems with the dataset.

Excuse me, I can't find the conll data with BIOES tags.Where can I get the data to perform your score?
The score of BIO tags is something worse than BIOES ' s.
Can you give me a url to download the data?
thanks a lot for your help.

@caoxu915683474 you need transform the BIO tags to BIOES tags by yourself.

@zhenlanghuo Thanks a lot , I forget to do this transform work by myself. Haha!

Thanks @zhenlanghuo !

@caoxu915683474 were you able to resolve the issue? were you able to get BIOES dataset?


Fix newsreader rewrite regression

Please send your pull requests the develop branch.
Don't forget to add the change to CHANGELOG.md.

Note: Sometimes the development moves very fast. It is highly
recommended that you update your branch of develop before creating a
pull request to send us your changes. This makes everyone's lives
easier (including yours) and helps us out on the development team.
Thanks!

Does the pull request solve a related issue?
If so, can you reference the issue?
#2502

adds the word 'not' after if in the two places.

Codecov Report

Merging #2503 (e67dc38) into develop (70c3b68) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #2503   +/-   ##
========================================
  Coverage    39.90%   39.90%
========================================
  Files           21       21
  Lines         1629     1629
========================================
  Hits           650      650
  Misses         979      979

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 70c3b68...e67dc38. Read the comment docs.


vue-video-player in Android APP & Android WeChat.

When playing in the small screen,
Android APP & Android WeChat vjs-fullscreen-control button is not working.
Ohters is work well.

I have the same questions，do you solve them?


Fix/bar component outdated api

Description
Updated Bar api and positioning utilities.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Codecov Report

Merging #13 (b90a9fc) into main (1e5800f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #13   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           27        23    -4
  Lines          214       190   -24
  Branches        51        47    -4
=========================================
- Hits           214       190   -24

Impacted Files
Coverage Δ

src/components/Bar/Bar.tsx
100.00% <ø> (ø)

Continue to review full report at Codecov.

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


Scroll locks up

I'm building a Cordova + Phonon (v1.2.5) app and experiencing scroll lockups similar to #43, except I'm not using tabs. I'm using phonon-core.min.js and forms.min.js
User flow:

Category page shows 10 icons (static HTML), scrolling works.
Click on a category, list of products is generated dynamically. Usually a pretty long list and scrolling works.
Click through to a product, click "Add" button.
User is taken to the cart page, list of items in cart is generated dynamically.
Clicking the icon to go back to the category page, it usually will not scroll. Sometimes a two-finger scroll works. Usually have to tap between one or two other pages in the app then come back to the category page and it will usually be able to scroll again.

Other information that might be relevant:

I'm not using tabs. I am using a <footer> that is just outside of the <div class="content"> and contains the four main app icons. The <footer> is position: fixed; bottom: 0; left: 0;
I'm using sqllite tables for the database of products and the cart. The pages all load quickly and aren't throwing any javascript errors.
I'm testing locally on the device using Phonegap Serve. I've experienced the same scroll locking when compiling the app and installing it on the device.

I've tried a bunch of things but can't seem to get it working. Any help would be much appreciated.

Actually I can duplicate the scroll locking up just by doing step 1 and 2 described above, then clicking on the Category page again.
I'm not really clear on what preventClose: false does, but it's set for every page in the app.
Do I need to do something to "reset" the height of the viewport after dynamic content is added to the DOM?

preventClose
If false do nothing
if true block close page (get out page), but you need add activity  onClose
///... your code
app.on({page: 'home', preventClose: false, readyDelay: 1, content: 'home.html' }, function(activity){
	activity.onClose(function( self ){
	// now I can work what happening
		var active = true; // simple example
		if( ( active != undefined ) && ( active != null ) ){
			self.close();
			phonon.navigator().changePage( "home" );
		}
	});
});

Thanks @John-Henrique, that makes a bit more sense. Since I'm using preventClose: false and no onClose activity, it sounds like that's not a cause of the scroll locking up.
I am using onCreate and onHashChanged on a couple pages, to attach event listensers to form buttons and load a specific product ID, for example.

@gRegorLove man, sometimes scroll lock happening when yours elements no have height, so Phonon can't calculate how many times is necessary to scroll at top or bottom. This help you?

I appreciate it, but no it doesn't help much. :) The Category page in step 1 is entirely static HTML, so the height doesn't change. It scrolls fine on first visit. Then visiting a page with dynamic content -- which also scrolls fine -- and back to the Category page, the Category page no longer scrolls.
The dynamic content cannot have an explicit height set on it. I think I'm missing some Phonon core call, like within an onReady perhaps, which calculates the height and ensures Phonon knows that. I would think such a call would be automatic within the core, but maybe it's not.

In the first page I added an onReady that outputs the content's height using console.log. On first load, it's 755px and it scrolls. Click to the dynamic list of products, and it scrolls. Click to the first page again, the same height of 755px is logged, but the page won't scroll.

More debugging:

Category page initial load. on('pageopened') the .content div scrollHeight is 568. Static HTML content with images is definitely taller than that, and the page still scrolls.

Tap to another page, intiial load: on('pageopened') the .content divs crollHeight is 652. Static HTML content with images; height measurement appears to be correct, but doesn't scroll.

Tap back to the Category page: on('pageopened') the .content div scrollHeight is 1121. This seems more in line with the actual height fo the content, but the page doesn't scroll.

@Qathom Could you take a look at this? Thanks!

I've now torn out all of the dynamic-height content and explicitly set the min-height of my main content div to 2500px. It should scroll on every single page, and it does intermittently on the first load, but often returning to the same page will make it lock up.
Can someone please offer some help?

Changing the CSS for .content from -webkit-overflow-scrolling:touch to -webkit-overflow-scrolling:auto appears to fix it, though obviously doesn't have the momentum scrolling. I'm looking into alternative scrolling solutions to achieve that.

Hi @gRegorLove,
Thank you for reporting this and sorry for the late reply.
Your issue is indeed similar to #43! I only runned some tests on Chrome without Apache Cordova, but it seems that the given CSS rule can "affect" the viewport of the active view.
I think that .content>*{-webkit-transform:translateZ(0);transform:translateZ(0)} should be removed. This was a sort of hack to render elements while scrolling on very old browsers.
Please, let me know if this fixes your problem perfectly!
Thanks :)

Hi @Qathom, thanks for the confirmation of my suspicions. I've been debugging a lot more in both the Phonegap Serve simulator app as well as compiling with Phonegap Build and running the actual app on the iPod. Removing .content>*{-webkit-transform:translateZ(0);transform:translateZ(0)} definitely seemed to help, but I still occasionally got scrolling locked up. Then I turned off animatePages and it's working. No more scroll locking up!
This is my first app, so I'm sketchy on some of the details, but I think this might have to do with iOS UIWebView vs WKWebView. I'm pretty sure Phonegap Build is using the former, when the latter is the newer preferred version (probably with better CSS support, transforms, etc.)
I'll keep you posted if I get any more information, or if the bug resurfaces (man, I hope not... this has been quite a frustrating debugging process!). Let me know if you'd like any more information about the development process, if you're interested in duplicating.

Thank you very much @gRegorLove :)
I think <preference name="DisallowOverscroll" value="true" /> can also improve the scroll event (by default th value is false). (set to true if you don't want the WebView to rubber-band).
More information: iOS Configuration with Cordova.

I do have that set to true. I think that was the default when I set up the Phonegap project, but it might have been changed somwehere during all the debugging; I don't remember exactly. :)

Still an issue on Phonegap/Cordova but for my app only on iPhone 5s. Maby it has to do with the speed the dynamic content is generated.
I'm generating a list of items on the page (aprox 300), I cant scroll, when entering the page. But if i click an item, which opens a fullpanel, then closes the panel again, the scroll works again...
would be great if there was a function that could be called, to reinitiate the scroll heigt when the list is created... or something like that :)
iOS: 11

Hello,
This issue is not concerning Phonon directly, but I think I found a fix here: https://github.com/ionic-team/ionic-v1/issues/155
This should solve your issue (see more info from the link above):
var lastY = 0; // Needed in order to determine direction of scroll.
$(".scroll-container").on('touchstart', function(event) {
    lastY = event.touches[0].clientY;
});

$('.scroller').on('touchmove', function(event) {
    var top = event.touches[0].clientY;

    // Determine scroll position and direction.
    var scrollTop = $(event.currentTarget).scrollTop();
    var direction = (lastY - top) < 0 ? "up" : "down";

    // FIX IT!
    if (scrollTop == 0 && direction == "up") {
      // Prevent scrolling up when already at top as this introduces a freeze.
      event.preventDefault();
    } else if (scrollTop >= (event.currentTarget.scrollHeight - event.currentTarget.outerHeight()) && direction == "down") {
      // Prevent scrolling down when already at bottom as this also introduces a freeze.
      event.preventDefault();
    }

    lastY = top;
});


BlazorBFF works w/Azure AD B2C, but get error when add SignUpSignInPolicyId

Hi Damien,
Thanks so much for this excellent example code.  I've been able to get it to work pretty much as-is, however, it is with AAD B2C instead of AAD.  Everything works great until I create a User Flow then add the SignUpSignInPolicyId key to the settings (which effectively eliminates the need for TenantId).  Do I need to add an Authority setting here?  Do we have to introduce MSAL in some way?
The error I'm getting is:
**An unhandled exception occurred while processing the request.
IOException: IDX20807: Unable to retrieve document from: 'System.String'. HttpResponseMessage: 'System.Net.Http.HttpResponseMessage', HttpResponseMessage.Content: 'System.String'.
Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.GetDocumentAsync(string address, CancellationToken cancel)
InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'.
Microsoft.IdentityModel.Protocols.ConfigurationManager.GetConfigurationAsync(CancellationToken cancel)**
Below shows your appSettings.json with the AzureAdB2C name and SignUpSignInPolicyId key (of course I'm using other guids in my code)
{   "AzureAdB2C": {     "Instance": "https://login.microsoftonline.com",     "Domain": "damienbodhotmail.onmicrosoft.com",     "TenantId": "7ff95b15-dc21-4ba6-bc92-824856578fc1",     "ClientId": "46d2f651-813a-4b5c-8a43-63abcb4f692c",     "CallbackPath": "/signin-oidc",     "SignedOutCallbackPath ": "/signout-callback-oidc",     //"ClientSecret": "add secret to the user secrets"     "SignUpSignInPolicyId": "UserFlow1"   },   "UserApiOne": {     "ScopeForAccessToken": "api://b2a09168-54e2-4bc4-af92-a710a64ef1fa/access_as_user User.ReadBasic.All user.read",     "ApiBaseAddress": "https://localhost:44395"   }
Here is the code to parse the settings and conf auth:
            services.AddMicrosoftIdentityWebAppAuthentication(Configuration, "AzureAdB2C")                 .EnableTokenAcquisitionToCallDownstreamApi(initialScopes)                  .AddMicrosoftGraph("https://graph.microsoft.com/beta",                     "User.ReadBasic.All user.read")                 .AddInMemoryTokenCaches();
Your help to get beyond this error would be greatly appreciated.
Thanks in advance...Bob Baldwin
aka VSDotNetGuy

Hi again Damien,
Just to confirm as I'm not a strong oauth or openid connect dev. By CC I assume you mean Client Credentials and by OBO you mean On Behalf Of.
I believe I have this working as the Direct and Graph API seems to be working with ADB2C plus I created a custom user flow with claimsexchange via az function to pass approle user assignments into the auth pipeline so blazor client and server knows about RBAC based roles and Authorize attributes work as desired
Thanks again for the help.

Also it seems OBO is now supported for ADB2C based on https://docs.microsoft.com/en-us/azure/active-directory-b2c/custom-policy-developer-notes#oauth-20-application-authorization-flows

Ok, upon further investigation, I see that OBO is not directly supported but can be used as long as client credential is used for downstream API like MS Graph

I add extra claims like in this example
https://damienbod.com/2021/09/06/using-azure-security-groups-in-asp-net-core-with-an-azure-b2c-identity-provider/
public class GraphApiClaimsTransformation : IClaimsTransformation
Greetings Damien

Thanks Damien,
We now have your BFF cookie based approach using Microsoft.Web.Identity working nicely in an AD B2C environment.  It uses CC to access MS Graph versus OBO.
I do have another question.  I noticed your code utilizes the ConfigureWait(false) syntax.  One of my associates, believes this is not needed within ASP.Net Core.  Can you explain your reasoning for it and also why it is no longer in the template code you just recently created at https://github.com/damienbod/Blazor.BFF.AzureAD.Template on Nov 29th?
Thanks again for you excellent posts.

Hi @vsdotnetguy thanks
yes ConfigureWait(false) is not needed within an ASP.Net Core context and should be removed. Will fix this.
Greetings Damien

Understood, thx

Created a Blazor template for this
https://github.com/damienbod/Blazor.BFF.AzureB2C.Template
maybe you could review, test, improve?
Greetings Damien


Re-add bazel test to CI

In my personal github action test, the maxos-latest 1.15.4 matric panics
Run go test
--- FAIL: TestGlobalFinalizer (0.00s)
panic: dtor not run [recovered]
	panic: dtor not run

goroutine 74 [running]:
testing.tRunner.func1.1(0x4c4aae0, 0x4ca7e10)
	/Users/runner/hostedtoolcache/go/1.15.4/x64/src/testing/testing.go:1072 +0x30d
testing.tRunner.func1(0xc0000be900)
	/Users/runner/hostedtoolcache/go/1.15.4/x64/src/testing/testing.go:1075 +0x41a
panic(0x4c4aae0, 0x4ca7e10)
	/Users/runner/hostedtoolcache/go/1.15.4/x64/src/runtime/panic.go:969 +0x1b9
github.com/bytecodealliance/wasmtime-go.TestGlobalFinalizer(0xc0000be900)
	/Users/runner/work/wasmtime-go/wasmtime-go/reftypes_test.go:314 +0x17d
testing.tRunner(0xc0000be900, 0x4c84a68)
	/Users/runner/hostedtoolcache/go/1.15.4/x64/src/testing/testing.go:1123 +0xef
created by testing.(*T).Run
	/Users/runner/hostedtoolcache/go/1.15.4/x64/src/testing/testing.go:1168 +0x2b3
exit status 2
FAIL	github.com/bytecodealliance/wasmtime-go	0.267s

I have no idea how to solve this.

It's strange, they are both "use darwin_amd64 instead of darwin in BUILD" at e083e78 . But one mac 1.14 succeeded but another one failed.

Ah yeah the "dtor not run test" is spuriously failing on CI so it's safe to ignore. I've otherwise rerun CI here to ensure it was just a spurious error what was there previously.


Invalid characters in Azure Alerts naming

Describe the bug
ConvertTo-AzOpsState:
Line |
94 |  …  & $azOps { ConvertTo-AzOpsState -Resource $resource -ExportRawTempla …
|                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| The specified AzOpsState file contains invalid characters (remove any "[" or "]" characters)! Skipping /runner/_work/.../AzOps/root/tenant root group (xxx-xxxxx-xxxxxxx-xxxxxxx801234)/xx - connectivity (xxxx-xxxxx-xxxxx-xxx-xxxxx)/microsoft-network-westeurope/.state/microsoft.insights_metricalerts-[xx] - xxx0501-001-availability fired for config1234 in sub xx - connectivity and rg microsoft-network-westeurope.json
Steps to reproduce

Create an Azure Alert with the name containing a special character like []
Try to Pull with AzOps
It will fail cause of special character

Screenshots

Thank you for raising this?
This is currently by design and described in the FAQ @https://github.com/azure/azops/wiki/frequently-asked-questions#subscriptions-or-resources-not-showing-up-in-repository. Are you manually adding these brackets to the metricalert-names, or is it done by Azure Monitor?

Thank you for raising this? This is currently by design and described in the FAQ @https://github.com/azure/azops/wiki/frequently-asked-questions#subscriptions-or-resources-not-showing-up-in-repository. Are you manually adding these brackets to the metricalert-names, or is it done by Azure Monitor?

Currently we add them as part of our naming convention for Azure Alerting. If this is not compatible with AzOps we can adjust the current naming convention off course.

As it has some ripple effects across various parts of the code base, it is currently not supported.
See #351,  #443 and #456 for further details.


Missing human annotations

Hi @ardunn. I am trying to use your datasets that you have created and looks like many of the human annotations are missing from the data/general_results. As an example, many completion keys in the jsonl have empty list values. How did you handle these samples when you were evaluating the model performance? Thanks!
https://github.com/lbnlp/NERRE/tree/main/general_and_mofs/data/general_results/run_0.jsonl

Hi @mehradans92
For annotation of the general materials task, we do not have extracted entries for texts without a material  (root entity around which the other entities are linked) mentioned in the text. Take for example this line in run_2:
{"prompt": "Electrodynamics in superconductors explained by Proca equations\nA fully consistent model to study electrodynamics for superconductors in the stationary and non-stationary regimes has been developed based on Proca equations and a massive photon. In particular, this approach has been applied to study the electric field penetration depth in superconductors. The model shows a deviation from the charge contribution to an internal electric field compared to previous approaches.\n\n###\n\n", "completion": " []\n\nEND\n\n", "gpt3_completion": " []"}

There is no clear root material entity to link to other recognizable materials terms (e.g., superconductors). We do not consider "superconductors" a material because a clear material entity is not present. This is a design choice we made quite early on in developing the General-JSON models.
However, there may be errors. For example, a clearly mentioned material in the text and no corresponding material root entry in the annotation. This would be an error in annotation. If you find them, please point them out and we can correct them!

Thanks for the explanation @ardunn. I have another question on the mof dataset. So I have noticed that sometimes MOF names and their chemical formula are interchangeably used in the human annotations and sometimes not. Was there a reasoning for this?
Also, Andrew mentioned that there have been a few updates to your paper, so I was wondering if there's a way to get access to the latest version. Thanks a lot :)

Hi @mehradans92 everything should be updated, but do you have some specific examples where this is the case? I am tagging @Andrew-S-Rosen here as well

Additional details would be helpful.
That said, it's worth emphasizing that the notion of what constitutes a "name" vs. a "formula" is extremely unclear for MOFs. For instance, take HKUST-1. That's clearly a name. And the equivalent Cu3(btc)2 is clearly a formula. But what about Cu-BTC? I would argue that's a name, but one could argue it's a formula. So, there is certainly room for ambiguity here, although if there are clear errors we should have that addressed.


net: Dialer.Dial failed to establish connection on Ubuntu

What version of Go are you using (go version)?
go version go1.8.3 linux/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/kmiura/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build271721950=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
What did you do?
tried to establish tcp connection.
Link on play.golang.org (https://play.golang.org/p/sOmgtkxQhx)
What did you expect to see?
Dialer.Dial succeeded in establishing connection on Ubuntu.
What did you see instead?
Dialer.Dial failed to establish connection with message "dial tcp :20->:8081: bind: address already in use".

Your program is trying to make initiate TCP connections from the same local port.  The only way to implement that with the sockets API is to bind the socket before making the connect call.  Calling bind on the first socket will work, but calling bind on the second socket will fail, because the first socket is already bound to that port.
Closing because I don't see any way that Go could change to make this program work.
In general, if you have questions about using Go, please don't use the issue tracker.  See the forums at https://golang.org/wiki/Questions.


Stream endpoints are not really streaming?

When I query /stream or /drip endpoints with curl --no-buffer, all the output appears at once (instead of being streamed to my console over time).
It appears like there is some buffering in the backend.

I confirmed this by building a server with streaming+flushing in Go and using curl --no-buffer. It worked just fine. It appears like httpbin is doing either buffering or has flushing issues.

We run httpbin behind nginx which by default buffers responses from the proxied host. We have turned that off for these endpoints. Can you try again and verify that it's working for you now?

@johnsheehan /drip works correctly now, I can see it happening.
/stream still prints everything at once, is that expected?

I think it's just happening so fast you can't tell that it's actually streaming instead of buffering. If someone wants to contribute something to add delays between /stream chunks we can consider that in another issue.


Invoking Boogie with Spaces In Filenames

This is by no means a large issue, but it would be nice to enable spaces in filenames. If I have a Boogie program in a file called test space.bpl and I try to invoke Boogie on it, I get the error:
Boogie program verifier version <IP_ADDRESS>016, Copyright (c) 2003-2014, Microsoft.
*** Error: 'test': Filename extension '' is not supported. Input files must be BoogiePL programs (.bpl).

Is there a reason why this is not currently supported? I've been developing on SMACK and have had an inquiry about this issue.

This isn't a Boogie issue AFAICT. It's your shell. The default field separator is a space (if you use bash read about IFS). You need to quote the file name.
I tried it under Linux on my system and if I quote the file name then verification appears to work correctly.
$ Binaries/Boogie.exe "use me.bpl"
Boogie program verifier version <IP_ADDRESS>016, Copyright (c) 2003-2014, Microsoft.

Boogie program verifier finished with 1 verified, 0 errors

I am quoting the file name:
$ boogie "test space.bpl"
Boogie program verifier version <IP_ADDRESS>016, Copyright (c) 2003-2014, Microsoft.
*** Error: 'test': Filename extension '' is not supported. Input files must be BoogiePL programs (.bpl).

I am using bash, and quoting the file name does not work.
$ boogie "test space.bpl"
Boogie program verifier version <IP_ADDRESS>016, Copyright (c) 2003-2014, Microsoft.
*** Error: 'test': Filename extension '' is not supported. Input files must be BoogiePL programs (.bpl).

@jon-whit boogie is not a file that is part of this repository, nor is generated by Boogie's build process.
Are you using the boogie wrapper script from the SMACK repo by any chance?
I just took a look at it and it has a bug in it (so does the Corral wrapper script) relating to handling arguments passed to it.
I've sent a pull request to fix it to fix it.

Closing this because it's an issue with SMACK's wrapper and has nothing to do with Boogie's code.


Conversion TERRA output to new standard

Conversion fails for some TERRA outputs. This is probably due to having 'Depth' variable name starting with upper-case instead of lower-case in CDF files.
The error can be reproduced using simulation 107_scale or 106_scale. The conversion produces the following error:
VersionError: NetCDF file version '0.0' is not supported. Please convert with convert_files.convert
In [7]:         convert_files.convert( tmfiles)
...:
IndexError                                Traceback (most recent call last)
Cell In[7], line 1
----> 1 convert_files.convert( tmfiles)
File /mnt/lustre/a2fs-work3/work/n03/n03/eart0587/pyvenv/lib/python3.9/site-packages/terratools/convert_files.py:47, in convert(files, test)
37     os.chmod(
38         file,
39         stat.S_IWUSR
(...)
44         | stat.S_IROTH,
45     )
46 data = nc4.Dataset(file, mode="a")
---> 47 depths = data["Depths"][:]
48 variables = (
49     data.variables.copy()
50 )  # Copy so not overwriting dictionary keys in loop
51 for var in variables:
File src/netCDF4/_netCDF4.pyx:2517, in netCDF4._netCDF4.Dataset.getitem()
IndexError: Depths not found in /

Hi Franck,
Did this get resolved or is this still an open issue?


don't warn about group/world-readable KUBECONFIG if it contains no secrets

helm currently warns on every command:
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: …
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: …

The warning isn't very useful.
In my case, the kubeconfig uses OIDC for logins, so it doesn't contain any secrets.
Instead of embedding client key data certs (via client-key-data), kubeconfig might also contain paths to files containing secrets (via client-key). Permissions for these are not checked either.
This check should probably simply be removed. It produces both false positives and false negatives, and understanding kubeconfig shouldn't be a concern of helm either, but of the Kubernetes SDK.
related: https://github.com/helm/helm/issues/9115

@flokli This is only a reminder. you can change the permission of KUBECONFIG to remove it.

@yxxhero Yes you can change the permissions of kubeconfig if you follow the extra steps: https://github.com/helm/helm/issues/9115#issuecomment-1137431441
Might be easy on some OSes but Windows and WSL requires extra step also when tools like rancher-desktop suggest to symlink the kubeconfig between Windows and WSL so you do not have to maintain two configs.
By default in WSL it cannot see file permission metadata on Windows files you have to enable that.

Personally I think that an environment variable to suppress these warnings is a cleaner approach than simply removing them. Something along the lines of SUPPRESS_KUBECONFIG_PERMS_WARNING or something explicit like that.

The main case here is that the kubeconfig files doesn't always contain secrets:

Secrets can either live in other files, that are referred to from kubeconfig (client-key instead of client-key-data)
Secrets can not exist at all (OIDC)

It shouldn't be a concern of helm to try to understand all the various formats.

if it is not a concern for helm than it should remove the readable check.
Or at the very least provide a way to suppress the warning.

as the description implies, this check is quite flaky, thus if you have the flexibility to use the KUBECONFIG environment variable, providing the "insecure" one second[0] will work around this check without making any permission changes.
0] you can even use an empty first file KUBECONFIG=":path/to/insecure"

Yeah, as written above, this should be a Kubernetes SDK concern, so all libraries connecting to kubernetes could warn in these cases. But having it downstream in helm doesn't make too much sense, especially considering it's often wrong.

I'm aware it's a warning/reminder that can be ignored. The "this is insecure" is a bit of a too strong message, and in many cases wrong - which is why I opened this issue. Of course setting the permissions might be a workaround - at least in filesystems supporting this, but I'd rather prefer if helm wouldn't try to make guesses that are wrong quite often...

Looking at the history of that function, it's been stated rather explicitly by the core maintainers that this is a result of a CNCF security team audit.

To be clear, will not accept PRs to suppress the security warning. This issue was pointed out by a security audit sponsored by the CNCF, and the warning was the security team’s recommendation.
However, if there are ways where we can identify that a) the kubeconfig is mounted in an NTFS drive, and b) permissions are indeed restricted to the user, we would welcome PRs that would address this case to remove the warning.

https://github.com/helm/helm/issues/8776#issuecomment-812146980
Based on that second paragraph, I suspect logic that would also determine that there were no secrets in the kubeconfig would also be considered.

not stale

Looking at the history of that function, it's been stated rather explicitly by the core maintainers that this is a result of a CNCF security team audit.

To be clear, will not accept PRs to suppress the security warning. This issue was pointed out by a security audit sponsored by the CNCF, and the warning was the security team’s recommendation.
However, if there are ways where we can identify that a) the kubeconfig is mounted in an NTFS drive, and b) permissions are indeed restricted to the user, we would welcome PRs that would address this case to remove the warning.

#8776 (comment)
Based on that second paragraph, I suspect logic that would also determine that there were no secrets in the kubeconfig would also be considered.

That seems a little inconsistent: kubectl and other core Kubernetes tooling doesn't warn, why is Helm?

I don't think we can speculate about why something didn't happen.

I don't think we can speculate about why something didn't happen.

I think we can and should because it'll lead to all the right answers [sarcasm] :).

On a more relevant note, do you think an env var, as others have suggested, to suppress would be humorable?

I kind-of doubt they'd go for that. Anything that could be done out-of-sight of the user that could make it possible to surreptitiously install software onto your cluster is probably going to be rejected. I think the most likely thing they'd accept, if at all, is a flag.

I'm upvoting this. Like (presumably) every other EKS user, my kubeconfig contains exec: command: aws args: --region BLAH eks get-token --cluster-name BLAH and no secrets whatsoever. I also have really good group-collaboration reasons why my group wants/needs to share their kubeconfigs with group permissions. This is not an "NTFS" thing, this is a deliberate, well-considered decision. I'd even go so far as to say that's what group (or indeed world) permissions are FOR, isn't it?

To be clear, will not accept PRs to suppress the security warning. This issue was pointed out by a security audit sponsored by the CNCF, and the warning was the security team’s recommendation.

Can we at least point out that the CNCF have been misled into thinking that this file is necessarily sensitive? Why NOT support an option in that kubeconfig to say something like "I hereby declare that this file is not secret or sensitive" for example? Give me the option to make it clear that this was a deliberate, well-considered decision.
My /etc/passwd file is also group/world readable. My /etc/shadow file is group (shadow) readable! I have group mailboxes which are deliberately group readable, and contain far more sensitive info than any of my kubeconfigs. C'mon, have some sense of proportion here.

I'm not sure why this is a problem.  I don't see what the big deal is inundating users with spurious warning messages, to the point that they can't tell the difference between real warnings and fake ones.
...I know some of you might say that we're actually teaching users to just ignore warning messages altogether, and to you "security" professionals I would say that that is a purely academic discussion and that's where it should stay.  This would never happen to users in the real world.  They are way too smart for that.

@bigwheels16

I'm not sure why this is a problem. I don't see what the big deal is inundating users with spurious warning messages

The problem is that the one who executes helm might be not a human, but another program. So this useless warning makes the subprocess running tough and ugly.

Not stale, people again got bitten by this, see https://github.com/helm/helm/pull/12316#issuecomment-1732527352

Still relevant.

Heavily pondering on @sudermanjr proposal of a quietening environment variable.
I need my KUBECONFIG to be group-readable, so my vagrant user can be in the minikube group with rw access to it.

I saw this error on v3.12.1. After upgrading to v3.14.1, the error disappeared

How should it? The check is still there: https://github.com/helm/helm/blob/51a07e7e78cba05126a84c0d890851d7490d2e20/cmd/helm/root_unix.go#L53
Still relevant, also see https://github.com/helm/helm/pull/12316#issuecomment-1732527352

Still relevant.


8.0 reminder crm next action time

8.0 reminder_crm_next_action_time

@ilmir-k Fix new lint warnings, please
import_framework/mapper.py:329:1: E305 expected 2 blank lines after class or function definition, found 1
web_sessions_management/http.py:64:1: E305 expected 2 blank lines after class or function definition, found 1


Typo in https://blog.tensorflow.org/2022/02/boost-your-models-accuracy.html?linkId=8033010

...layer with a on top...

@ToonTalk ,
We see that the issue template has not been filled, could you please do so as it helps us analyse the issue [tf version, steps followed before you ran into this error or stand alone code to reproduce the issue faced]

I only read the blog post and noticed a typo. Why fill in a template for that?

@ToonTalk ,
Please feel free to submit a PR for the requested change or share the link where requested change is to be made

The typo is in https://blog.tensorflow.org/2022/02/boost-your-models-accuracy.html?linkId=8033010
...layer with a on top...

@ToonTalk,
This issue is fixed now. Please refer to the updated blog post. Thanks!

Are you satisfied with the resolution of your issue?
Yes
No


Shallow copy and drop

Closes #5664, by manually fuse a shallow copy and a drop of a DataFrame.
cc @rjzamora @mrocklin

If we can make the approach in #5675 work I would rather do that just because it will affect drop calls more generally.  Let's wait to see if we can finish that up first.

Fixed by  #5675


Function names again being reported incorrectly in Mythril reports

Description
Looking at the latest master, when verifying fixes made in #469, I find the function names again as being reported as "function": "_function_0xa9059cbb" in Mythril's output.
How to Reproduce
myth -xo json 0xfffeee1655f36233fd58fdda74720b4eb85fddec
Environment

Mythril version: be904f98ccdaec7f90fc6edbffa1d282721eab2e

@shashank-srikant ,I am just guessing where the error can be here as i couldn't reproduce it.Can you rerun it and check whether the error persists or not?

that's odd.
this is what i see.

i just pulled the latest code into the mythril folder which had previously been installed through pip.
when i run solc --hashes on this code, i do see the function names though.
======= sol_0xfffeee1655f36233fd58fdda74720b4eb85fddec.sol:BasicToken =======
Function signatures:
70a08231: balanceOf(address)
18160ddd: totalSupply()
a9059cbb: transfer(address,uint256)

======= sol_0xfffeee1655f36233fd58fdda74720b4eb85fddec.sol:ERC20 =======
Function signatures:
dd62ed3e: allowance(address,address)
095ea7b3: approve(address,uint256)
70a08231: balanceOf(address)
18160ddd: totalSupply()
a9059cbb: transfer(address,uint256)
23b872dd: transferFrom(address,address,uint256)

======= sol_0xfffeee1655f36233fd58fdda74720b4eb85fddec.sol:ERC20Basic =======
Function signatures:
70a08231: balanceOf(address)
18160ddd: totalSupply()
a9059cbb: transfer(address,uint256)

======= sol_0xfffeee1655f36233fd58fdda74720b4eb85fddec.sol:MeissaToken =======
Function signatures:
dd62ed3e: allowance(address,address)
095ea7b3: approve(address,uint256)
70a08231: balanceOf(address)
42966c68: burn(uint256)
313ce567: decimals()
66188463: decreaseApproval(address,uint256)
7d64bcb4: finishMinting()
d73dd623: increaseApproval(address,uint256)
40c10f19: mint(address,uint256)
05d2035b: mintingFinished()
06fdde03: name()
8da5cb5b: owner()
95d89b41: symbol()
18160ddd: totalSupply()
a9059cbb: transfer(address,uint256)
23b872dd: transferFrom(address,address,uint256)
f2fde38b: transferOwnership(address)

======= sol_0xfffeee1655f36233fd58fdda74720b4eb85fddec.sol:MintableToken =======
Function signatures:
dd62ed3e: allowance(address,address)
095ea7b3: approve(address,uint256)
70a08231: balanceOf(address)
66188463: decreaseApproval(address,uint256)
7d64bcb4: finishMinting()
d73dd623: increaseApproval(address,uint256)
40c10f19: mint(address,uint256)
05d2035b: mintingFinished()
8da5cb5b: owner()
18160ddd: totalSupply()
a9059cbb: transfer(address,uint256)
23b872dd: transferFrom(address,address,uint256)
f2fde38b: transferOwnership(address)

======= sol_0xfffeee1655f36233fd58fdda74720b4eb85fddec.sol:Ownable =======
Function signatures:
8da5cb5b: owner()
f2fde38b: transferOwnership(address)

======= sol_0xfffeee1655f36233fd58fdda74720b4eb85fddec.sol:SafeMath =======
Function signatures:

======= sol_0xfffeee1655f36233fd58fdda74720b4eb85fddec.sol:StandardToken =======
Function signatures:
dd62ed3e: allowance(address,address)
095ea7b3: approve(address,uint256)
70a08231: balanceOf(address)
66188463: decreaseApproval(address,uint256)
d73dd623: increaseApproval(address,uint256)
18160ddd: totalSupply()
a9059cbb: transfer(address,uint256)
23b872dd: transferFrom(address,address,uint256)

can you do a pip freeze and post the output, it might be helpful to recreate

upgrading python3.5 to python3.6 seems to fix this


Support for exporting the images in dark mode (with black background)

Currently, when a user tries to export the work it only supports exporting in light theme only instead if the user opts for exporting in dark mode (that is with black background) then it should be exported in the desired manner.
Some images are attached for more ref:
Here is the screenshot of the actual image

Here is the screenshot of the exported image

P.S: Great application team GG :smile:

It is possible to export in dark mode. In the export modal, the toggle has to switched to dark mode.

Oh totally missed it, btw can we somewhat increase the size of the logo as it seems small relatively?
Browser: Chrome

Yep we definitely need to improve the visibility of the theme icon - this is part of the export redesign as well. And we should probably export in same theme which is set by user, IOW if its dark theme -> export in dark theme as well

Appreciate your quick response over this :), yeah it can be exported in the same mode by default and maybe there can be a manual setting too (as it's for now)

And we should probably export in same theme which is set by user, IOW if its dark theme -> export in dark theme as well

This was actually discussed at length before and the team got divided on how this should work. I myself am for not aligning it to the UI theme, though I acknowledge the potential UX issues (the problem is, neither approach is free of UX issues).

And we should probably export in same theme which is set by user, IOW if its dark theme -> export in dark theme as well

This was actually discussed at length before and the team got divided on how this should work. I myself am for not aligning it to the UI theme, though I acknowledge the potential UX issues (the problem is, neither approach is free of UX issues).

Whats the reason for not aligning with the UX theme ? From my understanding its more likely that user will want to export the data in same theme in which they are drawing. We can take a look at the data probably before taking the call.