Fix tooltips shown for push notifications not enabled on server.

First commit is to not show the tooltip when push notifications are enabled.
Second commit is to show the tooltip for checkbox in stream notification row.

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged and marked as a backport candidate, thanks @sahil839!


Pydantic V2 Compatibility Update for Document Upload

Fix for Pydantic V2 File Object Serialization
Problem
When using Pydantic V2, file objects (like BufferedReader) are converted to SerializationIterator instances during model serialization via model_dump(). This breaks backwards compatibility with V1 behavior and causes issues when the original file object is needed downstream (e.g., for GraphQL clients expecting BufferedReader objects).
This is a known issue tracked in pydantic/pydantic#8907.
Solution
This PR introduces a new FileCompatibleBaseModel class that patches model_dump() to properly handle file objects in Pydantic V2. The solution:

Creates a base model that detects SerializationIterator instances in the dump output
Reconstructs the original file object by reading the iterator contents into a BufferedReader
Updates DocumentUpload to use this new base class
Adds comprehensive tests to verify the behavior

Key changes:

Added FileCompatibleBaseModel in models.py with V2-specific patches
Updated DocumentUpload to inherit from FileCompatibleBaseModel
Added test suite in test_models.py to verify file handling behavior

Testing
The new test suite verifies:

Basic model functionality remains unchanged
File objects are properly preserved through serialization
File contents remain readable after serialization
Nested models and other field types work as expected
Full compatibility with the DocumentUpload use case

Notes

This is a temporary workaround until the upstream Pydantic issue is resolved
The solution maintains backwards compatibility with both V1 and V2
No changes to existing API contracts or behavior

Related to pydantic/pydantic#8907

Amazing! I'll take a look at this today

Amazing! I'll take a look at this today

I deleted and recreate the env from scratch with the PR.
I'm seeing some unexpected behavior where a test that looks very separate is failing on expectations that the results are snake vs camel case.
I also am seeing that the newest Pydantic may require us to increase the minimum python requirement from 3.8 to 3.10 or higher. I'm still looking at these.
You can test and review the direction I outlined. The new test work.
If we like it we can iron out these other details which are probably just related to changes in pydantic and other libraries since you last tested your branch.

Looks like the overridden model_dump is not called in a createEtchPacket scenario. Maybe it's called when using the DocumentUpload directly, but not when using the CreateEtchPacketPayload. Even making all pydantic objects extend the new base model has the same behavior.
My hunch is because CreateEtchPacketPayload.model_dump() is probably calling model_dump on some internal pydantic object(s). We define files as a List of AttachableEtchFile and that thing is a Union, so I bet it's calling model_dump on the List and / or Union and totally ignoring your new thing. It probably needs to be ~turtles~ FileCompatibleBaseModel all the way down.
Here is our implementation of those objs:
class CreateEtchPacketPayload(FileCompatibleBaseModel):
    files: List["AttachableEtchFile"]

AttachableEtchFile = Union[
    DocumentUpload, EtchCastRef, DocumentMarkup, DocumentMarkdown
]

The litmus test here is creating a signature packet with an uploaded file. If you can run the multipart script such that it is either creating a packet or giving you a forbidden error, then you are good. e.g.
ANVIL_API_KEY=YOUR_KEY python examples/create_etch_upload_file_multipart.py

And you don't even need a valid api key until you can get past the SerializationIterator issue, api key just needs to be not-None.
I'm happy to deal with upgrading to the latest latest and making sure the tests work if you can get this working!

Great feedback, I’ll give it a go. I think I see a path still.
Meanwhile, love the Turtles all the way down ref, well done.
On Fri, Dec 6, 2024 at 1:39 PM Ben Ogle @.***> wrote:

Looks like the overridden model_dump is not called in a createEtchPacket
scenario. Maybe it's called when using the DocumentUpload directly, but
not when using the CreateEtchPacketPayload. Even making all pydantic
objects extend the new base model has the same behavior.
My hunch is because CreateEtchPacketPayload.model_dump() is probably
calling model_dump on some internal pydantic object(s). We define files
as a List of AttachableEtchFile and that thing is a Union, so I bet it's
calling model_dump on the List and / or Union and totally ignoring your new
thing. It probably needs to be turtles FileCompatibleBaseModel all the
way down.
Here is our implementation of those objs:
class CreateEtchPacketPayload(FileCompatibleBaseModel):
files: List["AttachableEtchFile"]
AttachableEtchFile = Union[
DocumentUpload, EtchCastRef, DocumentMarkup, DocumentMarkdown
]
The litmus test here is creating a signature packet with an uploaded file.
If you can run the multipart script such that it is either creating a
packet or giving you a forbidden error, then you are good. e.g.
ANVIL_API_KEY=YOUR_KEY python examples/create_etch_upload_file_multipart.py
And you don't even need a valid api key until you can get past the
SerializationIterator issue, api key just needs to be not-None.
I'm happy to deal with upgrading to the latest latest and making sure the
tests work if you can get this working!
—
Reply to this email directly, view it on GitHub
https://github.com/anvilco/python-anvil/pull/64#issuecomment-2524637539,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABASCWGR5S2LKB3WVGZ5YUD2EIYUHAVCNFSM6AAAAABTELNPJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRUGYZTONJTHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
This message is intended only for the individual or entity to which it is
addressed.  It may contain privileged, confidential information which is
exempt from disclosure under applicable laws.  If you are not the intended
recipient, you are strictly prohibited from disseminating or distributing
this information (other than to the intended recipient) or copying this
information.  If you have received this communication in error, please
notify us immediately by e-mail or by telephone at the above number. Thank
you.

@benogle got it working.
I added:

new tests
improved the handling so it'll handle DocumentUpload and the nested structure

Note it doesn't handle a scenario where you have a CreateEtchPacketPayload within a files object of CreateEtchPacketPayload. This is invalid today but, if you change your mind, beware :)
Here's a launch config you can use for a vscode-like editor.
        {
            "name": "Python: Create Etch Upload Multipart",
            "type": "python",
            "request": "launch",
            "program": "${workspaceFolder}/examples/create_etch_upload_file_multipart.py",
            "console": "integratedTerminal",
            "justMyCode": true,
            "env": {
                "ANVIL_API_KEY": "YOUR_KEY"
            }
        }

The script ends with an error (as expected) on validating the key.
gql.transport.exceptions.TransportQueryError: {'message': 'Unauthorized: malformed key'}

Tell me if you can take it from here.

Hello @cyrusradfar and thanks so much the work so far! I've pulled this down and tried it out. If you use a validANVIL_API_KEY (I'm assuming you have an Anvil account where you can pull your API key from? If not, please sign up!), you will eventually get all the way to making the API call, but our API will throw a GraphQL error complaining about the fact that some fields provided by the Anvil Client are not defined in the EtchFile type.
Specifically, it looks like the client is now providing some fields/keys in snake_case that are supposed to be in camelCase. Why is this happening? Because of the stuff that's happening in this file around transforming snake_case to camelCase:
https://github.com/anvilco/python-anvil/blob/master/python_anvil/api_resources/base.py
It seems like either:

your FileCompatibleBaseModel pattern needs to incorporate that additional functionality of base.py and then remove base.py and change all references to the BaseModel it contains so that they point to your FileCompatibleBaseModel solution
The opposite: Move/incorporate your solution into api_resources/base.py and everything just uses that BaseModel.py

Either way, it feels like the things going on in api_resources/base.py and your models.py should be merged and only 1 of them should exist going forward.
Would you agree and can you make this change?
It would also be great if you could then try everything with a real API key and ensure that things work successfully.
Thanks again for the work on this!

Totally, appreciate the lead on the snake case -- will get an account/api_key and try again.

@benogle
I think I've resolved the issue but maintained my models.py class by importing the existing helper from api_resources/base.py
I'm uncomfortable with the idea of merging the BaseClass override in base.py with models.py, mainly because:

I don't want to lose the fact that this is a hack. Monkeypatching or overriding is quite dangerous, especially at serialization and the current approach may feel a bit redundant but we'd simply delete my models.py entirely if/when pydantic resolves the underlying issue and remove/replace the usage with BaseModel.

The overridden model_dump introduces undue risk if it's on every class. My concern is your users may accidentally import your BaseModel or extend your classes. I want as few objects as possible exposed to this solution because I don't feel confident that we handle all the cases beyond the two classes we've currently overridden. I definitely haven't tested nor know how to test all the potential serialization cases.

I'm here to get us upgraded so if you feel it's a blocker; I'll dispose of models.py.

Hi @cyrusradfar I'm still having an issue getting the test script to work all the way through (ANVIL_API_KEY=<your key here> poetry run python examples/create_etch_upload_file_multipart.py):
  File "/Users/newhouse/projects/anvil/python-anvil/examples/create_etch_upload_file_multipart.py", line 154, in <module>
    main()
  File "/Users/newhouse/projects/anvil/python-anvil/examples/create_etch_upload_file_multipart.py", line 147, in main
    res = anvil.create_etch_packet(payload=packet)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/newhouse/projects/anvil/python-anvil/python_anvil/api.py", line 412, in create_etch_packet
    return self.mutate(mutation, variables=variables, upload_files=True, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/newhouse/projects/anvil/python-anvil/python_anvil/api.py", line 114, in mutate
    return self.gql_client.execute(use_query, variable_values=variables, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/newhouse/projects/anvil/python-anvil/.venv/lib/python3.11/site-packages/gql/client.py", line 484, in execute
    return self.execute_sync(
           ^^^^^^^^^^^^^^^^^^
  File "/Users/newhouse/projects/anvil/python-anvil/.venv/lib/python3.11/site-packages/gql/client.py", line 248, in execute_sync
    return session.execute(
           ^^^^^^^^^^^^^^^^
  File "/Users/newhouse/projects/anvil/python-anvil/.venv/lib/python3.11/site-packages/gql/client.py", line 1028, in execute
    raise TransportQueryError(
gql.transport.exceptions.TransportQueryError: {'message': 'Uh oh, it looks like something is wrong with this file. Please ensure the file extension has not been changed.', 'path': ['createEtchPacket'], 'locations': [{'line': 2, 'column': 3}], 'name': 'AssertionError', 'status': 400}

It seems like the code that was adding the content_type: 'application/pdf' here is not longer having an impact on the multi-part API request we are sending. I'm not sure why that's happening, but I tried for a bit to figure it out.
Are you not getting this same error on your end when you run this script? Can you please use that script as the "success metric"?
Thanks again for your help with this!

@newhouse apologies, didn't realize Ben wasn't my last response. I was a little confused on success as Ben said

The litmus test here is creating a signature packet with an uploaded file. If you can run the multipart script such that it is either creating a packet or giving you a forbidden error, then you are good.

and I saw the pdf wasn't created and thought that it was an expected error state. I'll look deeper, didn't realize it should work.

@newhouse OK, so I think that I didn't recognize that V1 pydantic returned a dict for the file vs BufferedReader, I updated to handle differently. Your script works to the best of my estimate, now.

Ok cool. I will check out your changes tomorrow. Right before I left work I solved the issue I was having, as well. So tomorrow we should be good on this.


Detox iOS failing to start intermittently on React Native 0.68.2

What happened?
About 50% of the time Detox iOS fails with the following error:
15:18:10.143 detox[7891] WARN:  [DetoxConnection.js/ERROR, #50663] Action dispatched too early, there is no session to use:

HINT: Please report this issue on our GitHub tracker:
https://github.com/wix/Detox/issues

{
  params: [Object],
  type: 'AppWillTerminateWithError',
  messageId: -10000
}

What was the expected behaviour?
Expect Detox to consistently start on iOS 15.5 and React Native 0.68.2
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[X] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!
Problem seems to be related to React Native 0.68.2
In what environment did this happen?
Detox version: 19.7.1 (latest)
React Native version: 0.68.2
Node version: v14.x
Device model: 15.5 Simulator
iOS version: 15.5
macOS version: macOS Monterey
Xcode version: 12.3.1
Test-runner (select one): jest-circus
Detox logs
No response
Device logs
No response
More data, please!
No response

Hey @shamilovtim, thanks for the report.
This error makes sense since Detox is not yet compatible with RN 0.68. We are working on it these days.
However, once we'll finish with the upgrade we will investigate your issue if it still happens.

hey @asafkorem
You say that Detox is not yet compatible with RN 0.68.
This applies to 0.67.1 too?
Thanks

@xavimodo Detox is compatible with RN 0.67.2

Please retry using Detox 19.8.x

I have the same issue with latest detox (19.9.1) and RN 68.2.
All works fine on my local machine, but on Github actions I have this error.
It is the same for macos-latest (macos v11) and macos-12 vms.

+1 to above.
"detox": "19.9.1"
"react-native": "0.68.2"
Running locally on macOS Monterey.
iOS works fine. Android fails 😢

Yeah judging by the responses it looks like this never got fixed. I was curious when you responded how it was possible this got resolved in 19.8.x because when I looked at your PRs for react native 68 they had no actual changes to the logic of Detox. What those PRs did was upgrade your example app but they did not change Detox. @d4vidi @asafkorem

Hey @shamilovtim and everyone. Thanks for reporting this. Based on what you've described, I'm inclined to attribute this to some kind of a race condition, rather than the very specifics of the execution environment.
We haven't noticed this happening in any of our own environment (trust me, there are quite a few). Therefore, we would love to get more detailed logs from a session where this takes place, from either of you. We will not be able to sort this out, otherwise... It would help a great deal. Thanks.

I'll try to jump on this as soon as I can. I recall when I was working on this issue I was having a problem getting any logging because the crash seemed to be inside of Detox's lifecycle methods rather than in my app's logic so all of the crash details seemed hidden away from me. Is there anything I can do about that? @d4vidi

@shamilovtim I'm not 100% sure what you're referring too. You can run detox with the --loglevel trace arg, it should definitely provide a huge chunk of logs, that would make a great starting point for us.

@shamilovtim I'm not 100% sure what you're referring too. You can run detox with the --loglevel trace arg, it should definitely provide a huge chunk of logs, that would make a great starting point for us.

I'll give that a shot, thanks.

logs.txt
Here are the logs from my run.
Also, this is the emulator config if they are of any interest:
avd-setup.sh.txt
avd-config_ini.sh.txt

I'm using iOS 15.5, Detox 19.11.0, and React Native 0.69.5 in an app generated by Expo 46. I see this same issue when running in GitHub Actions.
Everything works fine when I run it locally on my M1. I added --loglevel trace and --debug-synchronization 500 to my job and you can see the failing job at the following URL:
https://github.com/jhipster/generator-jhipster-react-native/runs/8145635035?check_suite_focus=true

I'm using iOS 15.5, Detox 19.11.0, and React Native 0.69.5 in an app generated by Expo 46. I see this same issue when running in GitHub Actions.
Everything works fine when I run it locally on my M1. I added --loglevel trace and --debug-synchronization 500 to my job and you can see the failing job at the following URL:
https://github.com/jhipster/generator-jhipster-react-native/runs/8145635035?check_suite_focus=true

I'm having the same issue with Circle CI. Works on my local M1 but fails the Circle CI build with this error. Where you ever to figure out a fix?

We are still experiencing this problem

+1 to above. "detox": "19.9.1" "react-native": "0.68.2"
Running locally on macOS Monterey.
Interestingly enough, it works on a real Android device. but fails on the emulator (also works fine on iOS)

The issue relates to iOS failures, not Android, and you say that you have no problems on iOS. I suggest opening a separate issue with your error since I'm afraid it will disappear in this issue context.

We are still experiencing this problem

@shamilovtim, as @d4vidi already mentioned, we need more context (logs) in order to investigate this problem.

I need to get the logs for you. It's happening on other people's machines so I can't collect them myself.

@shamilovtim is it still relevant?

@asafkorem yeah this is still a huge source of flakes sadly. I've also reproduced it on a m1 max now too.

@shamilovtim Could you do something about those logs, then?

@wadey1 please submit your problem via a different issue. AppWillTerminateWithError is a general error, and doesn't say much about the source of the problem. In any case, I can see where your error is coming from.

I'm going to close this. I don't have it on my machine and I think it has disappeared for my coworkers.

Thanks @shamilovtim

I amended my comment a few above. Don't know if I was half asleep or what but the "huge source of flakes" I was referring to was the signal 11 error


Clean up the public API of sc-network-gossip

Let's also clean up the public-facing API of sc-network-gossip by turning the futures 0.1 into a futures 0.3.
I don't know if I should mark as "client-noteworthy" considering that this concerns a trait that exists purely in order to be able to mock the network for testing purposes. Polkadot in particular doesn't implement this trait.

I did this in #4633 but that PR is on ice because I'm waiting for a new tokio version, so LGTM.


open chat view for a group

How can we open chat view for a group in a single click outside of applozic sdk.

Add this method in ALChatManager.swift if missing. You can use this method to launch chat for particular group.
func launchChatForGroupId(_ forGroupId : NSNumber ,fromViewController:UIViewController){
       let alChatLauncher: ALChatLauncher = ALChatLauncher(applicationId: getApplicationKey() as String)
       alChatLauncher.launchIndividualChat(nil, withGroupId: forGroupId, andViewControllerObject: fromViewController, andWithText: nil)
   }

Thanx , its was missing..


Support for ASPNetCore 1.0.1

i'm trying to get my web api project in aspnetcore (.netCoreApp, version 1.0) working with halcyon, but importing Halcyon.Mvc v2.1.0 gives following error:
Package Halcyon.Mvc 2.1.0 is not compatible with netcoreapp1.0 (.NETCoreApp,Version=v1.0). Package Halcyon.Mvc 2.1.0 supports:
- net451 (.NETFramework,Version=v4.5.1)
- net46 (.NETFramework,Version=v4.6)
One or more packages are incompatible with .NETCoreApp,Version=v1.0.

i'll fork and see if i can do a pull request when i have some time


Empty test explorer view

Testing #114932
If the test provider does not provide workspace hierarchy then the test explorer is shown empty.

There shall be at least a message and actions shall be disabled.

This will now be shown if there are no workspace providers, or if the providers do not discover any tests (they have a root test item with no children)

the providers do not discover any tests (they have a root test item with no children)

I have that and think it is misleading to send users to the market place. There should be a differentiation between having test extension installed and having one which isn't returning results

I think it's still appropriate to show this text, as there might be test providers registered but they're not the right ones for the workspace.
However I've made a change to allow extensions to contribute text here via the standard viewsWelcome contribution. They can use that and context keys to display better help text as appropriate.

  "contributes": {
    "viewsWelcome": [
      {
        "view": "testing",
        "contents": "Hello world!"
      }
    ]
  },

Verified


Unable to reproduce Textual Entailment Plot

Hi All,
I'm trying to recreate the input/output heatmap below, but I'm unable to reproduce it.

I ran all of the same cells in example provided: https://github.com/slundberg/shap/blob/master/notebooks/text_examples/text_entailment/Textual Entailment Explanation Demo.ipynb
The output that gets produced is the following:

Thanks!

I have solved it!
from IPython.core.display import display as ipython_display, HTML

explainer = shap.Explainer(model,tokenizer)
shap_values = explainer(s)

ipython_display(HTML(shap.plots._text.saliency_plot(shap_values[0])))


[BEAM-3925] [DO NOT MERGE] KafkaIO : Value provider support for reader configuration.

ValueProvider support for KafkaIO reader configuration (input topics & bootstrap servers).
[NOTE: This is not meant for merge into master yet]
This enables users to write Dataflow templates using KafkaIO.
The main funcational changes is that partition information for topics is fetched at runtime by each of the source splits just before reading. This is required since Kafka topic names and cluster configuration may not be available at graph construction time.
This implies that we cannot adjust number of splits based on number of Kafka partitions. In order to get around this limitation this lets users explicitly specify number of splits (withNumSplits()). We can handle this better if we can let some splits not to have any partitions assigned at runtime. We need to something like that to be able to merge this into master.
For now, this PR will serve as good starting point for developing templates with KafkaIO.
[cc: @azurezyq, @pupamanyu]

Hi @rangadi, any reason why this is not merged to the master branch?
Is it because it is not fully tested or is there any other concerns?
I see it has been merged here
https://github.com/GoogleCloudPlatform/DataflowTemplates/blob/master/src/main/java/com/google/cloud/teleport/kafka/connector/KafkaIO.java
Our deployment kind of needs this functinonality of specifying Kafka brokers at runtime using Dataflow templates.

@rangadi would you be able to clarify why this was closed? Similar to @davidheryanto above, we're also trying to find a way to support ValueProvider options with KafkaIO, and it would be great to not have to maintain a separate connector if possible.

@pseudomuto @davidheryanto : The main issue we need to address is proper support for .numSplits() interface. If user sets numSplits to 20 and Kafka topic has only 5 partitions, 15 splits (readers) will not have any work. We just need to handle that properly. I don't think it is that much more work.
cc: @aromanenko-dev.

We just need to handle that properly.
@rangadi Do you mean that we just need to shrink the number of split accordingly in this case to avoid empty splits in runtime?

Ok, I see. Thanks!

Hi, is there any more progress on supporting Value provider? I've just hit the snag of this while trying to create a Dataflow template as well.

@davidscottturner I'm not aware of if anyone works on this.

FWIW, Flex templates bypass the requirement to use ValueProvider options in your pipelines (current in beta though)

@pseudomuto : I dont think it helps. Flex templates requires people to write description of the pipeline manually. It is not really idea situation at all. @rangadi : Can we just change the numSplits to numPartitions ? Everything will be much clearer and people will not set not correct number.

I agree with @pseudomuto. I think Flex templates allow using templates without adding ValueProviders by running the pipeline from a container. May be the pipeline you are trying to use is just not available as a Flex template yet ?

@chamikaramj yeah, I check it again. It should help. For me at first, it is difficult to follow Google documents. They did not explain how to write the template file, it makes everything a bit confused. The Docker part is no brainer. @pseudomuto : Sorry, I take everything I said back :D


Multi-repo pull request builds should look up dependencies with the correct branch name, instead of using the PR number

Multi-repo builds attempt to use the same branch name on all sources, falling back to master if no corresponding branch exists in a dependency. This works well for general branch builds, e.g. release branches.
In pull-request builds, we are using the pull-request number (e.g. PR-44) instead of the branch name (e.g. dev/build-cleanup) to do this lookup. This results in build failures where coordinated pull-requests are made in multiple repositories that require the other changes to build successfully.
See https://github.com/ni/niveristand-scan-engine-ethercat-custom-device/pull/44 for an example.

This is tricky because once there's a PR for the dependency, the Jenkins job for the branch goes away (i.e. I create a PR for ni-veristand-scan-engine-fxp-libraries and the dev/build-cleanup job in Jenkins no longer exists).
We could change it so that branch stays around even when a PR is created, but then we're basically building the same job twice.
I can add code to check the branch spawning the PR for the top-level job and try to use that branch in the dependency, but, again, if there is already a PR for that dependency, it won't change anything.


Unable to compile DW.AdMobBannerAd.iOS.pas with latest Kastri sources and D12.1

Fresh Kastri clone (latest sources 25th June 2024).
BannerAd control built and installed into the IDE from the Kastri\Controls folder.
New FMX app.
Drop an AdMobBannerAd onto the form (align bottom, etc - makes no difference).
Add the necessary paths to the project search property is needed.
Build.
Seems that the version of UIViewController in the DW sources seems to be incompatible with the ones deployed by Delphi.
[DCC Error] DW.AdMobBannerAd.iOS.pas(141): E2010 Incompatible types: 'DW.iOSapi.UIKit.UIViewController' and 'iOSapi.UIKit.UIViewController'

Committed a fix

That's working thanks Dave


Moving exception constructions to errors class

@tg-msft, would you mind taking a look?

resolves #6760


Clearing localStorage on a new game

Fixes https://github.com/FullScreenShenanigans/FullScreenPokemon/issues/61.


Using Paket to add dependency on GH projects that are not on NuGet

How about using Paket to add a reference to the GH repo's not found on NuGet (the Secp256k1.NET and LevelDB-sharp) as listed on http://fsprojects.github.io/Paket/github-dependencies.html?

Good idea. You could submit a PR for this.

I'll try and do that


Why caching what we decided not to cache in the example js13kpwa?

Request type

[] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x ] Correction or update

Details

I am sharing the experience that I had while studying the page https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Offline_Service_workers. In the code,  games.js is not in the list of the shell items to cache. I thought, hey I can add an entry server side and see that it will be updated.  It did not work !  It took me a few minutes to realize that in the code below when an item is not found in the cache, we cache it.  So, we could as well have included games.js in the list.  I found this a bit confusing. The example should be more explicit about whether the goal is to cache every thing (including game.js) or not.

Still sharing my experience, here is what I did as an exercise to test my understanding.  I created a separate asset file for the service worker:
// data/sw_assets.js
var DoNotCacheFiles = [];

var FetchFirstFiles = [
	'/pwa-examples/js13kpwa/data/games.js'
];

var InitialCacheFiles = [
  '/pwa-examples/js13kpwa/',
  '/pwa-examples/js13kpwa/index.html',
  '/pwa-examples/js13kpwa/app.js',
  '/pwa-examples/js13kpwa/style.css',
  '/pwa-examples/js13kpwa/fonts/graduate.eot',
  '/pwa-examples/js13kpwa/fonts/graduate.ttf',
  '/pwa-examples/js13kpwa/fonts/graduate.woff',
  '/pwa-examples/js13kpwa/favicon.ico',
  '/pwa-examples/js13kpwa/img/js13kgames.png',
  '/pwa-examples/js13kpwa/img/bg.png',
  '/pwa-examples/js13kpwa/icons/icon-32.png',
  '/pwa-examples/js13kpwa/icons/icon-64.png',
  '/pwa-examples/js13kpwa/icons/icon-96.png',
  '/pwa-examples/js13kpwa/icons/icon-128.png',
  '/pwa-examples/js13kpwa/icons/icon-168.png',
  '/pwa-examples/js13kpwa/icons/icon-192.png',
  '/pwa-examples/js13kpwa/icons/icon-256.png',
  '/pwa-examples/js13kpwa/icons/icon-512.png'
];

Then I modified the service worker as follows:
// sw.js

self.importScripts('data/games.js');
self.importScripts('data/sw_assets.js');

// Files to cache.
// In normal mode newCacheName = cacheName.
// Stay in transition mode long enough so that users that use often the app have installed the new cache.
var cacheName    = 'js13kPWA-v8';
var newCacheName = 'js13kPWA-v8';

var gamesImages = [];
for(var i=0; i<games.length; i++) {
  gamesImages.push('data/img/'+games[i].slug+'.jpg');
}

var contentToCache = InitialCacheFiles.concat(gamesImages);

// Installing Service Worker
self.addEventListener('install', (e) => {
  console.log('[SW] Install ' + newCacheName);
  e.waitUntil(
    caches.open(newCacheName).then((cache) => {
      console.log('[SW] Caching app shell and content.');
      return cache.addAll(contentToCache);
    })
  );
});

// Removing old caches.
self.addEventListener('activate', (e) => {
  e.waitUntil(
    caches.keys().then((keyList) => {
          return Promise.all(keyList.map((key) => {
        if(key !== cacheName && key !== newCacheName) {
          console.log('[SW] We delete cache ' + key);
          return caches.delete(key);
        }
      }));
    })
  );
});

// )

// Fetching content using Service Worker
self.addEventListener('fetch', function(e) {
  e.respondWith(
    caches.match(e.request).then(function(r) {
      var p=  new URL(e.request.url).pathname;
      if (r) {
        if (FetchFirstFiles.includes(p)) {
          return fetch(e.request)
          .then((response) => {
            console.log('[SW] Fetching, even if cached : ' + p);
            return response;})
          .catch( (e) => {
            console.log('[SW]', e.message, 'Returning not fetchable, but cached : ' + p);
            return r;
          });
        }
        else {
          console.log('[SW] Returning cached  : ' + p);
          return r;
        }
      }
      else if (DoNotCacheFiles.includes(p) ) {
        console.log('[SW] Fetching non cachable content : ' + p);
        return fetch(e.request);
      }
      else {
        console.log('[SW] Fetching and caching content : ' + p);
        return fetch(e.request).then((response) => {
          return caches.open(cacheName).then((cache) => {
            console.log('[SW] Caching new resource: '+p);
            cache.put(e.request, response.clone());
            return response;
          });
        });
      }
    })
  );
});

I have thought about this for a while and agree that the tutorial should be more explicit as to whether to cache games.js or rather why not.
As games.js contains the data, in reality that would be called from an API endpoint or database, caching the data would mean updating it periodically when there was network connectivity. For scope of the this tutorial it's best to keep games.js from the cache. It would be good to find out the intentions of the original author, but my understanding would be keeping it out was intentional.
It may be a task in the future to update the tutorial to include periodic background sync https://developer.mozilla.org/en-US/docs/Web/API/Web_Periodic_Background_Synchronization_API which allows for data to be updated in the background.
I can update the tutorial to be more explicit about why games.js isn't cached @chrisdavidmills

@Rumyra sounds good to me, and I think your explanation is sound.

Thanks @chrisdavidmills I've added:
You may notice we haven't cached game.js. This is the file that contains the data we use when displaying our games. In reality this data would most likely come from an API endpoint or database and caching the data would mean updating it periodically when there was network connectivity. We won't go into that here, but the Periodic Background Sync API is good further reading on this topic.
At the bottom of this section https://wiki.developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Offline_Service_workers#Lifecycle_of_a_Service_Worker

Looks great, thanks @Rumyra !

My point was that in the example provided, the code (see below) will systematically cache game.js at the first request even though it's not in the list to cache.  I am not sure the explanation covers this aspect.
self.addEventListener('fetch', (e) => {
  e.respondWith(
    caches.match(e.request).then((r) => {
          console.log('[Service Worker] Fetching resource: '+e.request.url);
      return r || fetch(e.request).then((response) => {
                return caches.open(cacheName).then((cache) => {
          console.log('[Service Worker] Caching new resource: '+e.request.url);
          cache.put(e.request, response.clone());
          return response;
        });
      });
    })
  );
});

I'm going to pick this up again @chrisdavidmills as I overlooked the initial cache. I might go through the tutorial myself and even out anything I find


[FP]: Maven JAR (Java) artifact identified as Go executable

Package URl
pkg:maven/org.yaml/snakeyaml
CPE
yaml_project:yaml::::::go::*
CVE
CVE-2021-4235
ODC Integration
{"label"=>"Maven Plugin"}
ODC Version
8.1.0
Description
Although this is a Go project (https://github.com/go-yaml/yaml) still a Maven JAR artifact (always Java!) is mistakenly matched for the CPE.

No longer an issue with 8.1.0.


Request for Feedback: Dynamic Logging's future (Should we deprecate Dynamic Logging?)

Summary
https://docs.pixielabs.ai/tutorials/custom-data/dynamic-go-logging/
Pixie Dynamic Logging let users write eBPF uprobes in PXL script, Pixie then deploys the uprobes onto user-specified Pods, and collect the data into Pixie's own data store.
https://docs.pixielabs.ai/tutorials/custom-data/distributed-bpftrace-deployment
Pixie also has Distributed Bpftrace Deployment, which lets users deploy kprobes and uprobes on Kubernetes cluster.
Given the limited capability of the PXL language, Dynamic Logging is used much less than Distributed Bpftrace Deployment. We are looking for feedbacks from the community regarding the future directions of Dynamic Logging.
Suggestions

One option is to simply remove Dynamic Logging from Pixie. That greatly reduces our maintenance burden.
Another option is to further expand PXL language support for Dynamic Logging to make it more powerful and useful.
A hybrid option is to extra the useful part of Dynamic Logging and contributed to BPFtrace, for example, the part of navigating struct variables with DWARF information (already part of BPFTrace https://github.com/iovisor/bpftrace/blob/master/docs/reference_guide.md#4-uprobeuretprobe-dynamic-tracing-user-level-arguments) could get improved with Pixie's current implementation.
Any other suggestions?

Given the lack of feedback, we are now proposing to deprecate the Dynamic Logging feature.
Rationale:

The feature is alpha and does not seem to be popular (given the lack of github issues related to it).
It is only supported on Go 1.16, which has not been supported for 1 year.

If anyone believes that Dynamic Logging should be maintained, we would need to identify someone to further develop and maintain it. If there is not enough support for keeping Dynamic Logging over the next 30 days, we intend to start the deprecation process.

I think it's an interesting feature to be able to probe production deployments in user space. I see possible use-cases around live debugging of variables. As far as I remember Delve recently introduced ebpf backend. So I find it a little hard to believe that there's not enough need for it.
I think expanding PXL language support makes much more sense. (Maybe using the distributed bpftrace deployment).
Anyways, I'll be happy to contribute to this. Is there some more documentation around using pxtrace - something more than https://docs.px.dev/reference/pxl/tracepoint-decorator/pxtrace.probe/

Also can you help answer, can distributed bpftrace using PXL do everything that dynamic logging does? (around working with uprobes and uretprobes)


⚠ Bofrost.at has degraded performance

In c2237db, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 875 ms

Resolved: Bofrost.at performance has improved in 190d8b7 after 13 minutes.


Version 2.3.5 getCurrentLocation() undefined

I installed the latest plugin version (2.3.5) and try to use getCurrentLocation() but it's not defined in www/BackgroundGeolocation.js (local installed file) when I use Cordova plugin add .. command. But I find it's actually exist in website file .  I tried to download the plugin and installed from local file, but it produces a lot of errors when build. Could you please fix this issue? Thanks a million!
Here is my environment:
@ionic/cli-utils  : 1.19.2
ionic (Ionic CLI) : 3.20.0
global packages:
cordova (Cordova CLI) : 8.0.0
local packages:
@ionic/app-scripts : 3.1.8
Cordova Platforms  : android 7.0.0
Ionic Framework    : ionic-angular 3.9.2
System:
Android SDK Tools : 26.1.1
Node              : v6.10.3
npm               : 6.1.0
OS                : Windows 10
Misc:
backend : pro

Now I installed this version:
cordova plugin add<EMAIL_ADDRESS>Looks like getCurrentLocation() is implemented in .js and .java files. But when I call getCurrentLocation(), I got this error:
TypeError: Cannot read property 'getCurrentLocation' of undefined.
Thanks for any help!
Here is my code:
	this.bgdGeo = (<any>window).BackgroundGeolocation;
	this.bgdGeo.configure(
		(location)=>
		{
			console.log('in init lastLat='+location.latitude);
			console.log('in init lastLong='+location.longitude);
		},
		(error) =>
		{
			console.log('bgd geo init err='+error);
		},
		{
                         desiredAccuracy: 0,
                         stationaryRadius: 20,
                         distanceFilter: 30,
                         debug: true,
                         stopOnTerminate: false,
		 });

	this.bgdGeo.getCurrentLocation(
		(location)=>{
			console.log('in init lastLat='+location.latitude);
			console.log('in init lastLong='+location.longitude);
		},
		(error) => {
			console.log('Error getting location', error);
		},
		{
			maximumAge: 10000,
			timeout: 10000,
			enableHighAccuracy: true
		});

It works with this version:
cordova plugin add<EMAIL_ADDRESS>Looks like it's not formally released then...


left sidebars don't seem to work. Doesn't look like either sidebar file is getting copied.

Solved with commit 7edfe7b


fix false LGTM hardcoded creds alert

https://lgtm.com/projects/g/badges/shields/alerts/?mode=list

Warnings

:warning:

:books: Remember to ensure any changes to config.private in services/weblate/weblate-base.js are reflected in the server secrets documentation

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against 80b19ca7f545d006407f591c0694929473c03aee


Add: fizz_buzz

Codecov Report

Merging #47 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #47   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          14     15    +1
  Lines         171    183   +12
=====================================
+ Hits          171    183   +12

Impacted Files
Coverage Δ

solution/fizz-buzz/fizz_buzz.go
100% <100%> (ø)

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 2a6b40a...952740c. Read the comment docs.


Add COCO evaluation metrics

I'm currently working on adding Facebook AI's DETR model (end-to-end object detection with Transformers) to HuggingFace Transformers. The model is working fine, but regarding evaluation, I'm currently relying on external CocoEvaluator and PanopticEvaluator objects which are defined in the original repository (here and here respectively).
Running these in a notebook gives you nice summaries like this:

It would be great if we could import these metrics from the Datasets library, something like this:
import datasets

metric = datasets.load_metric('coco')

for model_input, gold_references in evaluation_dataset:
    model_predictions = model(model_inputs)
    metric.add_batch(predictions=model_predictions, references=gold_references)

final_score = metric.compute()

I think this would be great for object detection and semantic/panoptic segmentation in general, not just for DETR. Reproducing results of object detection papers would be way easier.
However, object detection and panoptic segmentation evaluation is a bit more complex than accuracy (it's more like a summary of metrics at different thresholds rather than a single one). I'm not sure how to proceed here, but happy to help making this possible.

Hi @lvwerra
Do you plan to add a 3rd party application for the COCO map metric?

Is there any update on this? What would be the recommended way of doing COCO eval with Huggingface?

Yes there's an update on this. @rafaelpadilla has been working on adding native support for COCO metrics in the evaluate library, check the Space here: https://huggingface.co/spaces/rafaelpadilla/detection_metrics. For now you have to load the metric as follows:
import evaluate

evaluator = evaluate.load("rafaelpadilla/detection_metrics", json_gt=ground_truth_annotations, iou_type="bbox")

but this one is going to be integrated in the main evaluate library.
This is then leveraged to create the open object detection leaderboard: https://huggingface.co/spaces/rafaelpadilla/object_detection_leaderboard.
The metric itself is

Yep, we intend to integrate to evaluate library.
Meanwhile you can use from here https://huggingface.co/spaces/rafaelpadilla/detection_metrics

Hi,
running
import evaluate
evaluator = evaluate.load("hf-vision/detection_metrics", json_gt=ground_truth_annotations, iou_type="bbox")

results in the following error:
ImportError: To be able to use hf-vision/detection_metrics, you need to install the following dependencies['detection_metrics'] using 'pip install detection_metrics' for instance'

How do I load the metric from the hub? Do I need to download the content of that repository manually first?
I'm running evaluate==0.4.1.

Ran into the same issue @maltelorbach posted on 12/14/2023

I spent some time digging into this. The issue is that the hf-vision/detection_metrics metric uses a local module for some coco related dependencies (that's called detection_metrics, which is why you get the ImportError of that flavor).  I tried to restructure the space to have a flat directory structure, but then ran into this https://github.com/huggingface/evaluate/issues/189 because certain dependencies aren't loaded (or downloaded), or something.  Gave up after that.  It seems informative that the object detection example just rolls its own metric code with torchmetrics so it's probably easiest to do that.

cc @qubvel


Global Arguments question

In @proteins.config in __main__.py there are two default global arguments set as follows:
    freeze_embedding_weights = False  # noqa: F841
    save_outputs = False  # noqa: F841

Can you tell me what freeze_embedding_weights does?  If I want the pretrained unsupervised weights for the fluorescence task to remain fixed (ie. the embeddings will be constant) should I switch this to True?
For save_outputs, if this is False will outputs be saved? [See README.md|Saving Results - not sure if there is a discrepency here.] If 'save_outputs' is True what gets saved?
Thanks.
Scott

Thanks for your questions!
freeze_embedding_weights does exactly as you describe - if you want to train the downstream task model without propagating gradient updates through the language model, you should set this flag to True
save_outputs will save the outputs of the validation pass into a file called outputs.pkl. When running tape-eval, outputs are automatically saved and this flag is ignored.


Value converter for Uri

Summary of the changes

Added StringUriConverter and unit tests
Added Uri selection to ValueConverterSelector

Fixes #15816

@maumar I would like to add a model with Uri type to validate the end to end test of this converter. Any suggestions on where to put that model unit test?

Thanks @Muppets!

@Muppets CustomConvertersTestBase would be a good place to put the tests


Shorten hir::TypeParam ranges for traits in NavigationTarget

I noticed that selecting Self here highlights the entire trait,

this should cut it down to just the trait name and the Self which imo seems better.

bors r+

bors r+


k_thread_abort() free-memory write, take 2

Respin of the content in PR #71185 which had to be reverted for unexpected CI breakage.
Identical code, except one new patch (separated for clarity) in the second-to-last[1] position, please review that in particular.  Pretty simple to understand once you can see the deadlock in gdb.  Frustrating that only CI seems to have found the timing to reliably trip over it, and only post-merge.
[1] Before the addition of Peter's test which flagged it, to preserve bisectability.

Oops, sorry, will have to refresh.  I added an "obvious" last minute assert that missed a only-mostly-obvious case where it can't work.  Will remove and respin.

Oh... actually it's not me (or it was -- the assert I added absolutely could still trigger).  But there's a remaining hang on x86_64 which is a race in irq_offload().   Will filter the platform in this PR and file a bug, one sec...

OK, now it should be OK.  See #72172 for the irq_offload() bug that prevents the test from working on x86_64


Cannot overwrite/set trigger startTime via config-file under Linux (Ubuntu-20.04)

Describe the bug
When overwriting/setting typeProperties.startTime of a tumblingWindow Trigger the following error is raised when running on a Linux system (Ubuntu 20.04):
Invoke-Expression: /root/.local/share/powershell/Modules/azure.datafactory.tools/0.97.0/private/ObjectProperty.ps1:26

Line |
  25 |      Invoke-Expression "$exp"
       |      ~~~~~~~~~~~~~~~~~~~~~~~~
       | You must provide a value expression following the '-' operator.

To Reproduce

Create/Define a TumblingWindow Trigger
Overwrite its startTime via the config CSV file:type,name,path,value
trigger,trigger-example,typeProperties.startTime,"2022-07-28T06:00:00Z"

RunPublish-AdfV2FromJson -RootFolder /azure-data-factory -ResourceGroupName test -DataFactoryName test-factory -DryRun -Stage /azure-data-factory/deployment/config.csv

(See below for all files for a minimal example)
Expected behaviour
Work as it does on a Windows system.
Version of PowerShell module of:

PowerShell (itself): 7.2.6
ADFTools: 0.97.0

Provide all files to reproduce the issue
factory/test-factory.json:
{
	"name": "test-factory",
	"properties": {},
	"location": "eastus2"
}

trigger/trigger-example.json:
{
	"name": "trigger-example",
	"properties": {
		"annotations": [],
		"runtimeState": "Started",
		"pipeline": {},
		"type": "TumblingWindowTrigger",
		"typeProperties": {
			"frequency": "Hour",
			"interval": 24,
			"startTime": "2021-02-08T06:00:00Z",
			"delay": "00:00:00",
			"maxConcurrency": 1,
			"retryPolicy": {
				"count": 3,
				"intervalInSeconds": 600
			},
			"dependsOn": []
		}
	}
}

deployment/config.csv:
type,name,path,value
trigger,trigger-example,typeProperties.startTime,"2022-07-28T06:00:00Z"

Additional Information/Notes

For debugging I added a Write-Host line just before the Invoke Expression statement which throws the error. It printed:\

On Ubuntu$obj.properties.typeProperties.startTime = 2022-07-28T06:00:00Z

On Windows$obj.properties.typeProperties.startTime = "2022-07-28T06:00:00Z"

Edit: ~So for some reason the "internal" quoting behavior is different. The odd thing is I didn't observe this difference for other objects like LinkedServices.~ Running with debug settings on it shows that under Linux the type of the value is determined as a datetime and under Windows it is a string, so on Linux the else clause is triggered, leading to this quoting difference.
I did not test what happens if I attempt to overwrite other fields of a trigger
I am aware that once a TumblingWindow Trigger is defined I can't change the startTime, I want to use this config before I create them for the first time
A very dirty workaround (on a Linux system) is to use single quotes in the config file instead of double quotes, so that the problematic statement becomes:

On Ubuntu$obj.properties.typeProperties.startTime = '2022-07-28T06:00:00Z'

On Windows$obj.properties.typeProperties.startTime = "'2022-07-28T06:00:00Z'"

The Windows one is now obviously a problem during the actual deployment because the value '2022-07-28T06:00:00Z' is not a valid one for startTime

The problem might be related to dash character which is present in object's name.
Did you try to change name onto trigger_example and rerun? If not - please try and let me know the result.

I just tried it with triggerexample but I get the same error message. As far as I understand it the issue arises from the fact that the replacement string, i.e. 2022-07-28T06:00:00Z is recognized as a datetime under Linux. This should be independent from the name of the object.

I will take a look at this in spare time.

The problem lied in all system (Windows, Linux).
Value in config was recognizable as DateTime, but it tried apply the value as numeric which was leading to the error:
 ParseException: At line:1 char:52
 + $obj.properties.typeProperties.startTime = 2022-10-07T00:35:00.000Z
 +                                                    ~
 You must provide a value expression following the '-' operator.
 At line:1 char:52
 + $obj.properties.typeProperties.startTime = 2022-10-07T00:35:00.000Z
 +                                                    ~~~~~~~~~~~~~~~~
 Unexpected token '07T00:35:00.000Z' in expression or statement.

This is fixed now and will be released today in ver.0.101.
Thanks to raising this issue and making #adftools better!


Listing projects in the namespace does not work

The view for the forge namespace always shows all the projects:
E.g. https://dashboard.packit.dev/projects/github.com/packit

Already fixed by #335


CORS polyfill

I'm busy forking xdomain https://github.com/Financial-Times/xdomain to
a) make it check for cors support and only run if cors unsupported
b) fire an event on load so that it can be non-blocking
Could xdomain be a good enough cors polyfill to be added to the service?

No, because it requires the proxy.html file on the target host, so it's not a proper polyfill.  Unless it can mirror the spec, we can't have it in the library.  I can't see how we could do that with CORS.


MRTK Example quick fixes

Overview
This fixes two minor things in MRTK example components.

BoundingBox does not auto allocate it's UnityEvents. This makes it annoying when using BoundingBox component dynamically and subscribing via code/AddListener() because the developer needs to check if the property is null and if so, do the allocation him/herself.

Pinch slider has multiple tick mark sphere balls that each have their own draw call for rendering. This change creates a material for them and turns on GPU instancing to reduce 13 draw calls to 1.

Changes

Fixes: #4929

Verification

Tested out that is no longer null
View change in Frame debugger

/azp run mrtk_docs

/azp run mrtk_pr

/azp run mrtk_pr


Fix for Video Player images not loading

Fix for Video Player images not loading
Changes

Visit https://www.consumerfinance.gov/about-us/careers/application-process/ and notice that the video player images are not loading'

Testing

Visit https://www.consumerfinance.gov/about-us/careers/application-process/ and notice that the youtube max res image is loading.

Visit http://localhost:8000/about-us/events/archive-past-events/public-event-student-loan-servicing-raleigh-nc/ and verify that the youtube max res image is loading.

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the development playbook
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ ] Project documentation has been updated
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist
Browsers

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Internet Explorer 8, 9, 10, and 11
[ ] Edge
[ ] iOS Safari
[ ] Chrome for Android

Accessibility

[ ] Keyboard friendly
[ ] Screen reader friendly

Other

[ ] Is useable without CSS
[ ] Is useable without JS
[ ] Flexible from small to large screens
[ ] No linting errors or warnings
[ ] JavaScript tests are passing

. Hm, this is working on prod for me. What is the problem?

The youtube max res image should be appearing.


Add logic to make the s3 backend optional

I'm submitting this PR in connection with issue #40, although I'd like to get some assistance around two things:

Since Terratest is not open sourced yet, I believe you have to run tests on your side, and
Updating /_docs/architecture.png to reflect this change, or give the OK to roll back to the previous architecture diagram :)

I've updated the documentation as requested and I also added a separate example deployment, as well as made sure that the existing example deployments still worked.
I'm looking forward to your feedback!

OK, I made a few minor fixes, and the tests are passing. Thanks!

https://github.com/hashicorp/terraform-aws-vault/releases/tag/v0.2.0


"Type[] | Null" produces incorrect rules

The following Bolt rules:
type Something {
  A: Boolean,
  B: Number[] | Null
}

path /path is Something {
  read() = true;
}

produce the following rules json:
{
  "rules": {
    "path": {
      ".validate": "newData.hasChildren(['A'])",
      "A": {
        ".validate": "newData.isBoolean()"
      },
      "B": {
        "$key1": {
          ".validate": "newData.isNumber()"
        },
        ".validate": "newData.val() == null"
      },
      "$other": {
        ".validate": "false"
      },
      ".read": "true"
    }
  }
}

Notice the rules for B. It correctly produces the map rule ensuring that all wildcarded children are numbers, but it also produces a rule for B itself, validation that newData.val() == null. This precludes me from being able to write anything at /path/B!
I think the desired behavior would be, when encountered with an Type[] | Null, it would not produce any validation at the level of Type.

It looks like the fix is to remove | Null entirely. I had thought this would make the .validate rules at path equivalent to the following:
"path": {
  ".validate": "newData.hasChildren(['A', 'B'])"
}

But it was smart enough to discard the 'B'. Still, probably would be less confusing to allow for Type[] | Null!

Another test case:
path /x is String | Null;
path /y is String[];
path /z is String[] | Null;

produces:
{
  "rules": {
    "x": {
      ".validate": "newData.isString() || newData.val() == null"
    },
    "y": {
      "$key1": {
        ".validate": "newData.isString()"
      }
    },
    "z": {
      "$key1": {
        ".validate": "newData.isString()"
      },
      ".validate": "newData.val() == null"
    }
  }
}

I experienced this today.  Commenting to follow the issue.

Also having this issue, any progress on allowing Map | Null?

I got the same issue today. Is there any work around for this?


Clicking "Tap to Play" on the phone doesn't do anything

Whenever I view an rnplay and click "Tap to Play" to run the app, nothing happens. I'm using Chrome 47 on Mac OS X 10.10.5

@knubie There was an issue with the simulator receiving a message that we weren't handling properly. Everything should be working now.


add build dependencies

This adds build dependencies for https://github.com/tier4/scenario_runner.iv.universe/pull/11

@mitsudome-r please merge if you are still awake and also have a look at https://github.com/tier4/planning_simulator.iv.universe/pull/11 which is another blocker for https://github.com/tier4/scenario_runner.iv.universe/pull/11


Is imgaug seeded by default?

I'm using imgaug in an augmentation script that takes a directory of images and creates a directory of augmented images.
I've noticed that every time I run this script, I get the same augmentations.
In order to get different augmentations, I have to change the seed: ia.seed(some_number).
Thus in order to get random augmented images, I would have to seed it with a random number by default?

Yes, the library is configured by default to always use the same seed in order to make experiments more reproducible.
You can change that by calling ia.seed() as you said and providing it a random seed from e.g. numpy.

When I set ia.seed() I get
AssertionError: Expected argument 'entropy' or 'seedval' to be not-None, but bothwere None
Why is that?

@aleju what do you think about having imgaug listen to the numpy.random.seed? i.e. if np.random.seed is reset, then imgaug will reset. In my case I am using the Pytorch-Lightning funcion seed_everything to set seeds, which ideally could seed everything :)


Button content disappears in version 11.2.0-rc2

Describe the bug
Hello
Today I installed Avalonia version 11.2.0-rc2. I encountered a strange problem that I had to downgrade to version 11.1.4, which is a stable version. When I upgraded Avalonia to version 11.2.0-rc2, the Content I intended for the Button disappeared. If I changed the HorizontalAlignment or VerticalAlignment of the TextBlock inside the Button from DevTools, the text of the Button would be temporarily displayed, but it would disappear again after changing the window size.
I did not have this problem in the previous version, but after the upgrade I encountered this problem.
When I reduced the size of the window to its minimum, the text inside the button was visible. It was as if the text was stuck to the left or right (based on FlowDirection) side of the window, and then the text would fall into place after the window was resized.

  Template  -->
    <Setter Property="Template">
        <Setter.Value>
            <ControlTemplate>
                <Border Background="{TemplateBinding Background}"
                        BorderBrush="{TemplateBinding BorderBrush}"
                        BorderThickness="{TemplateBinding BorderThickness}"
                        CornerRadius="{TemplateBinding CornerRadius}">
                    <ContentPresenter Name="StartExamButtonContentPresenter"
                                      Margin="{TemplateBinding Padding}"
                                      HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}"
                                      VerticalAlignment="{TemplateBinding VerticalContentAlignment}"
                                      Content="{TemplateBinding Content}"
                                      FontFamily="{TemplateBinding FontFamily}"
                                      FontSize="{TemplateBinding FontSize}"
                                      FontWeight="{TemplateBinding FontWeight}"
                                      Foreground="{TemplateBinding Foreground}" />
                </Border>
            </ControlTemplate>
        </Setter.Value>
    </Setter>

    <!--  Transitions  -->
    <Setter Property="Transitions">
        <Setter.Value>
            <Transitions>
                <TransformOperationsTransition Property="RenderTransform"
                                               Duration="00:00:00.3" />
            </Transitions>
        </Setter.Value>
    </Setter>

    <!--  Pointer over  -->
    <Style Selector="^:pointerover">
        <Setter Property="RenderTransform" Value="scale(1.05)" />
    </Style>

    <!--  Disabled  -->
    <Style Selector="^:disabled">
        <Setter Property="RenderTransform" Value="scale(1)" />
        <Setter Property="BorderBrush" Value="#A8D0D2" />
        <Setter Property="Foreground" Value="#A8D0D2" />

        <Style Selector="^:pointerover">
            <Setter Property="RenderTransform" Value="scale(1)" />
        </Style>
    </Style>

    <!--  Tablet styles  -->
    <Style Selector="^.tablet">
        <Setter Property="Padding" Value="28,12" />
        <Setter Property="CornerRadius" Value="18" />
        <Setter Property="FontSize" Value="28" />
    </Style>

    <!--  Mobile styles  -->
    <Style Selector="^.mobile">
        <Setter Property="Padding" Value="24,10" />
        <Setter Property="CornerRadius" Value="16" />
        <Setter Property="FontSize" Value="24" />
    </Style>
</Style>

And this is my button:
<Button Classes="startExam"
        Command="{Binding $parent[local:StartView].StartExamCommand}"
        CommandParameter="{Binding $parent[local:StartView].StartExamCommandParameter}"
        Content="اجرای آزمون"
        IsEnabled="{Binding StartButtonIsEnabled}" />

To Reproduce
Upgrade to version 11.2.0-rc2
Expected behavior
The text inside the Button should be displayed in the middle of it
Avalonia version
11.2.0-rc2
OS
Windows
Additional context
No response

@Gillibald does it sound as a text processing bug?

Can concur, same here on the latest stable (11.2.0).
On 11.2.0-rc1 I had no issues at all.


Help!!!

hi admin why I can't follow airdrop what's the problem even though it's all right

please to trying for a day later... bcoz can't do same... airdrop+filter qualified user... this problem has begin at the first airdrop... so... I hope you will patient... many user in there wanna to join us... but its impossible to clear in one time... try to join again after 1 weeks of the end airdrop (22 Nov)... No way... when you are qualified... you will received our -email and our spacedrop will chat you in your keybase app... but you will received your first airdrop at 15 jan 2020... why 15 jan?... Our system and rules :)


Debian stretch repo error

Thanks for the Stretch build, trying on my new Rock64 which arrived today. Seems like the default-configured Debian repo has a size mismtach:
E: Failed to fetch http://deb.ayufan.eu/orgs/ayufan-rock64/releases/Packages.gz  Writing more data than expected (14108 > 12449)
   Hashes of expected file:
    - Filesize:12449 [weak]
    - SHA512:d7d6a86264c9a18fe8d5fa89422bab7509cbcfd3b630d4ccd13d777cea2d2ce39a8701212955c9754669162e44542d1d1390401bc071845e96740792b6a2452b
    - SHA256:8dcedca9b8bee3851a8b4778e8cb2a4b79a7a34823a1b24eda48c9a2dac06367
    - SHA1:60555aaa5aa4c5fcd520cedca3ee4476f101ed2c [weak]
    - MD5Sum:3c15712b76685318d080184e9caeb4dc [weak]
   Release file created at: Mon, 31 Jul 2017 09:49:37 +0000

Is this a known issue?

The repo is dynamic, generated based on GitHub Releases. I have to fix my app doing that: https://github.com/ayufan/debian-repository.

Thank you! Would be great if you can fix it.

Is this preventing programs like Mozilla Firefox to be updated? I had some issues finding packages like unzip and sxiv as well as nothing seemingly wanted to update. When editing /etc/apt/sources.list, removing anything to do with ayufans repo, apt still tries to fetch from there.

Fixed

Confirmed, thanks!

Same issue on the latest build when executing apt-get update:
E: Failed to fetch http://deb.ayufan.eu/orgs/ayufan-rock64/releases/Packages.gz  Writing more data than expected (42026 > 42020)
   Hashes of expected file:
    - Filesize:42020 [weak]
    - SHA512:92e41c269f5284e933e6b51f6ab45de0bf5ecb9ed91c2c4b6e9f22cea62b81e59d5122cb3637a65be7a9522b10b68fdd129c3e3fcf7701876b80a556b4123a0f
    - SHA256:dda3bea9bbebe2a8821b73897c4023026f2c22d286acb0dac41cf189e4209b17
    - SHA1:a5ea8698a1f983a843144395d66d488fa45d0a5d [weak]
    - MD5Sum:58b79e3f08e7c473585c44096581be6f [weak]
   Release file created at: Tue, 07 Aug 2018 11:55:19 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.

How can we get it fixed?
Tested on stretch-minimal-rockpro64-0.7.9-1067-arm64.img


As a developer, write tests in CON_ChangeAccount_TEST to cover multi-person households, one2one contacts, and org accounts

Included in beta release version 3.39 (Beta 1) and higher

Included in production release version 3.39


Syntax for conditionally setting object properties

Suggestion
🔍 Search Terms
conditionally assigned properties conditional properties exactOptionalPropertyTypes
✅ Viability Checklist

My suggestion meets these guidelines:

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
Create a syntax for conditionally assigning a property in an object at creation time in-line. This is especially relevant now that exactOptionalPropertyTypes is launched. See below for a proposal of how to do this.
📃 Motivating Example
Imagine this piece of JavaScript code:
function myFunction(val) {
  const myObject = {
    name: 'foo',
  };
  if (val !== undefined) {
    myObject.value = val;
  }
  return myObject;
}

This is valid JS code, and a somewhat common pattern for setting an optional property on an object.
But how would we convert this into strict TypeScript code, particularly with immutable types? Perhaps something like:
interface MyType {
  readonly name: string;
  readonly value?: string;
}

function myFunction(val?: string) {
  const myObject: MyType = {
    name: 'foo',
  };
  if (val !== undefined) {
    myObject.value = val;   // Error: cannot assign to `value` because it is a readonly property.
  }
  return myObject;
}

Well that doesn't work. :-(
Another option before exactOptionalPropertyTypes was:
function myFunction(val?: string) {
  const myObject: MyType = {
    name: 'foo',
    value: val,  // Not great, setting an optional property to `undefined` instead of leaving it unset. And fails with exactOptionalPropertyTypes
  };
  return myObject;
}

But this is bad practice for the reasons outlined in exactOptionalPropertyTypes, and is an error if you use that flag now.
Using good practices combined with strict TypeScript settings is preventing us from accomplishing this somewhat common pattern for constructing immutable objects with some optional properties. One workaround is to use something like type Mutable<T> = {-readonly [key in keyof T]: T[key]} inside this function, but this is worsening type scritness by circumventing the original type's immutability. Or you could tell the compiler to assume the value is non-null (!), then conditionally delete that property after, but that's error-prone and is circumventing TypeScript's type checking. I'm not aware of any safer way to do this without fundamentally modifying the code (eg. creating a builder pattern).
Proposal
What if we had something like this:
interface MyType {
  readonly name: string;
  readonly value?: string;
}

function myFunction(val?: string) {
  const myObject: MyType = {
    name: 'foo';
    value?: val;  // If `val` is `undefined`, does not set this key. Otherwise, sets this key to the the value in `val`.
  };
  return myObject;
}

This code would compile to the JavaScript code written at the top of this FR. But importantly, unlike my other examples, this code will build successfully because TypeScript understands the optional (but not undefined) key will not be set on this object unless its value is defined. It is type-safe.
How isn't this just a new syntactic sugar for JavaScript?
This problematic code is unique to TypeScript. JavaScript has simple solutions that build and run just fine (see first code example), but TypeScript does not (without sacrificing strictness). As such, this problem falls in the realm of TypeScript to solve, as JavaScript has far less incentive to implement what for them would only be a very minor syntactic sugar rather than a fix for unsupported use-cases.
Additionally, this is not writing any code that a human wouldn't write themselves if asked to solve this problem in JavaScript. This would just be TypeScript equivalent syntax that transpiles to that form, in the same way TypeScript class methods transpile to MyClass.prototype.foo = function(... syntax in JavaScript despite no mention of "prototype" in the TypeScript code.
💻 Use Cases
The primary use-case is as described above: immutable types being able to correctly set optional properties optionally without compromising strictness. In addition, this would also be a useful syntactic sugar for mutable use-cases, particularly when exactOptionalPropertyTypes is set, avoiding the verbosity of a bunch of if statements.
Alternative proposal
Here's another possible syntax that could solve the same problem, but with a bit more expressive power:
function myFunction(val?: string) {
  const myObject: MyType = {
    name: 'foo';
    // If the value of a key is `delete`, does not set that key. This would only be a TypeScript syntax,
    // it would compile either to the JS at the top of this FR or else to a similar solution bu using the
    // `delete` keyword on this key within the opposite if statement instead.
    value: val ?? delete;
  };
  return myObject;
}

This alternative syntax is a bit quirkier, but it has the advantage of not treating undefined as a special value. undefined seems to be the primary use-case here, especially after exactOptionalPropertyTypes, but some users may want to have more flexibility to customize this behavior (eg. for the corner case that a property is defined as foo?: string|undefined).

it's a unique problem to TS. Why would the JS spec want to solve a TS problem?

But it's not. You have the same issue in JS: You optionally want to set a property. You don't want a property with an undefined value, you either want a proper value or the property not exist in the first place. This is what exactOptionalPropertyTypes means.

It is possible to write this inside the object literal with:
{ ...(value === undefined ? {} : { key: value }) }

So I am wondering whether it is possible to introduce a different syntax for that, like e.g.
{ key?: value }

and transform it into the above.
My first thought was a babel-plugin, but I guess the transformation would have to run before the code reaches typescript.
Any ideas?

It is possible to write this inside the object literal with:
{ ...(value === undefined ? {} : { key: value }) }

So I am wondering whether it is possible to introduce a different syntax for that, like e.g.
{ key?: value }

This is what I'd like to be able to write! Would it be a Javascript feature, then?


[webview_flutter] Unexpected adb: device offline causes integration test failure

Is there an existing issue for this?

[X] I have searched the existing infra issues

Type of Request
bug
Infrastructure Environment
LUCI
What is happening?
I'm attempting to have webview_flutter integration tests run on AVDs with Android 34, see https://github.com/flutter/packages/pull/5221. Consistently, I see this failure that occurs in this failed build, for example:
01:43 +8 ~1: /b/s/w/ir/x/w/packages/packages/webview_flutter/webview_flutter/example/integration_test/legacy/webview_flutter_test.dart: Video playback policy Auto media playback                      adb: device 'emulator-5554' not found
Installing build/app/outputs/flutter-apk/app-debug.apk...           21ms
Error: ADB exited with exit code 1
adb: device 'emulator-5554' not found

01:43 +8 ~1 -1: loading /b/s/w/ir/x/w/packages/packages/webview_flutter/webview_flutter/example/integration_test/webview_flutter_test.dart [E]
  TestDeviceException(Unable to start the app on the device.)
  package:flutter_tools/src/test/integration_test_device.dart 63:7  IntegrationTestTestDevice.start

  TimeoutException after 0:12:00.000000: Test timed out after 12 minutes.
  package:test_api/src/backend/invoker.dart 338:28  Invoker._handleError.<fn>
  dart:async/zone.dart 1391:47                      _rootRun
  dart:async/zone.dart 1301:19                      _CustomZone.run
  package:test_api/src/backend/invoker.dart 336:10  Invoker._handleError
  package:test_api/src/backend/invoker.dart 291:9   Invoker.heartbeat.<fn>.<fn>
  dart:async/zone.dart 1399:13                      _rootRun
  dart:async/zone.dart 1301:19                      _CustomZone.run
  package:test_api/src/backend/invoker.dart 290:38  Invoker.heartbeat.<fn>
  dart:async-patch/timer_patch.dart 18:15           Timer._createTimer.<fn>
  dart:isolate-patch/timer_impl.dart 398:19         _Timer._runTimers
  dart:isolate-patch/timer_impl.dart 429:5          _Timer._handleMessage
  dart:isolate-patch/isolate_patch.dart 184:12      _RawReceivePort._handleMessage

which seems to occur because before this, the device goes offline and an uninstall fails, e.g. from that same build:
01:05 +8: /b/s/w/ir/x/w/packages/packages/webview_flutter/webview_flutter/example/integration_test/legacy/webview_flutter_test.dart: Video playback policy Auto media playback

01:06 +8: /b/s/w/ir/x/w/packages/packages/webview_flutter/webview_flutter/example/integration_test/legacy/webview_flutter_test.dart: Video playback policy Auto media playback
01:07 +8: /b/s/w/ir/x/w/packages/packages/webview_flutter/webview_flutter/example/integration_test/legacy/webview_flutter_test.dart: Video playback policy Auto media playback                         adb: device offline

01:07 +8 ~1: /b/s/w/ir/x/w/packages/packages/webview_flutter/webview_flutter/example/integration_test/legacy/webview_flutter_test.dart: Video playback policy Auto media playback                      adb uninstall failed: ProcessException: Process exited abnormally with exit code 1:
adb: device offline
  Command: /b/s/w/ir/cache/android/sdk/platform-tools/adb -s emulator-5554 uninstall io.flutter.plugins.webviewflutterexample

I have run this test locally on an emulator running Android 34 and it runs fine, so I'm hoping to get some help investigating this issue.
P.S. I see that there were issues with webview_flutter integration tests hanging on legacy (API 22) devices although on a different test and I think running in Firebase (https://github.com/flutter/flutter/issues/136824), so not sure it's related.
Steps to reproduce
N/A. See Linux_android android_platform_tests_shard_6 master builds for https://github.com/flutter/packages/pull/5221.
Expected results
I expect to see the webview_flutter/webview_flutter integration tests proceed normally as they do locally (and seemingly so, on AVDs running Android 33).

cc @bparrishMines not sure if you have seen this issue come up before, would love to know if you have!

I haven't seen this before. It looks like it may be due to a legacy test that needs updating
01:43 +8 ~1: /b/s/w/ir/x/w/packages/packages/webview_flutter/webview_flutter/example/integration_test/legacy/webview_flutter_test.dart: Video playback policy Auto media playback
I'll see if I can repro locally on 34

Seems related: https://github.com/flutter/flutter/issues/137947

I haven't seen this before. It looks like it may be due to a legacy test that needs updating
01:43 +8 ~1: /b/s/w/ir/x/w/packages/packages/webview_flutter/webview_flutter/example/integration_test/legacy/webview_flutter_test.dart: Video playback policy Auto media playback
I'll see if I can repro locally on 34

Lmk. I couldn't repro it locally, so that's why I filed this issue.
FYI that I'll need to address this issue before having webview_flutter compile against Android 34, so it's blocking in that way. However, I'm going on vacation soon and won't be able to work on this until I'm back.


Improper providers update with service generation

Bug Report or Feature Request (mark with an x)
- [ X] bug report -> please search issues before submitting
- [ ] feature request

When you use ng g s -m app.module, the providers property is not properly updated in cases when providers property has an existing useValue provider.
Version: 1.4.3
Repro steps.

Add a provider to the app.module that looks something like this:

providers: [ {provide: MATERIAL_COMPATIBILITY_MODE, useValue: true}]

ng g s search -m app.module

Check the providers property in app.module - it's wrong:

providers: [ {provide: MATERIAL_COMPATIBILITY_MODE, useValue: true, providers: [SearchService]}],
Desired functionality.
The updated property providers should look as follows:
providers: [ {provide: MATERIAL_COMPATIBILITY_MODE, useValue: true},  [SearchService]}],

Closing...
Duplicate of #7061


Parse env variables

Package version

"version": "4.1.0",
"adonis-version": "4.1.0",

Node.js and npm version

NodeJS  v10.9.0
npm 6.2.0

Sample Code (to reproduce the issue)
Set DB_DEBUG=false will still continue to display queries in the console.
This is because env variables are not parsed.
This package seems to be created for: https://github.com/niftylettuce/dotenv-parse-variables
See also: https://github.com/adonisjs/adonis-framework/commit/00ff73f13d7a0a9179e6a61ff06a94d26f819f36#diff-e2625b4032ee326641919c5b7ae6f807

Closing since not actionable


Review Sortition code

Implements #1486

Codecov Report
Base: 40.18% // Head: 39.99% // Decreases project coverage by -0.20% :warning:

Coverage data is based on head (1823f8c) compared to base (57c6bbd).
Patch coverage: 19.46% of modified lines in pull request are covered.

:exclamation: Current head 1823f8c differs from pull request most recent head e4e3722. Consider uploading reports for the commit e4e3722 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1487      +/-   ##
==========================================
- Coverage   40.18%   39.99%   -0.20%
==========================================
  Files         147      147
  Lines        9651     9737      +86
==========================================
+ Hits         3878     3894      +16
- Misses       5144     5217      +73
+ Partials      629      626       -3

Impacted Files
Coverage Δ

pkg/config/genesis/config.go
0.00% <ø> (ø)

pkg/config/genesis/presets.go
69.23% <ø> (ø)

...nsensus/blockgenerator/candidate/blockgenerator.go
0.00% <0.00%> (ø)

...core/consensus/blockgenerator/candidate/genesis.go
0.00% <0.00%> (ø)

...kg/core/consensus/blockgenerator/candidate/mock.go
0.00% <0.00%> (ø)

pkg/core/consensus/user/sortition.go
58.25% <ø> (ø)

pkg/core/data/ipc/transactions/fixtures.go
13.76% <0.00%> (-0.21%)
:arrow_down:

pkg/core/data/ipc/transactions/provider.go
0.00% <0.00%> (ø)

pkg/gql/query/blocks.go
63.22% <0.00%> (ø)

pkg/gql/query/mempool.go
30.00% <0.00%> (ø)

... and 10 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[e2e]: container tag main registry-username-secret

Repo: https://github.com/slsa-framework/example-package/tree/v31.0.516
Run: https://github.com/slsa-framework/example-package/actions/runs/10626104081
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.tag.main.registry-username-secret.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.tag.main.registry-username-secret.yml
Trigger: push
Branch: v31.0.516
Date: Fri Aug 30 03:06:45 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v31.0.517
Run: https://github.com/slsa-framework/example-package/actions/runs/10641903996
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.tag.main.registry-username-secret.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.tag.main.registry-username-secret.yml
Trigger: push
Branch: v31.0.517
Date: Sat Aug 31 03:07:43 UTC 2024
Tests are passing now. Closing this issue.


bump knative serving with 0.37.0

https://github.com/knative/serving/releases/tag/knative-v1.10.0

Codecov Report

Merging #115 (4ed4459) into main (c82851f) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #115   +/-   ##
=======================================
  Coverage   70.76%   70.76%
=======================================
  Files           4        4
  Lines         195      195
=======================================
  Hits          138      138
  Misses         40       40
  Partials       17       17


Update version to 1.2.0

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 88.07%. Comparing base (b2c0560) to head (1d46e2a).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #132   +/-   ##
=======================================
  Coverage   88.07%   88.07%
=======================================
  Files         273      273
  Lines       16039    16039
=======================================
  Hits        14127    14127
  Misses       1912     1912

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


Error occured when connecting D455i in realsense-viewer. Invalid value in rs2_get_option.

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ D400 }

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 16

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC

SDK Version
{ legacy / 2.38.1 }

Language
{C++ }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>
erroe occurred when using realsense viewer saying "Invalid value in rs2_get_option xxx". It happens every time I open "Stereo Module" .

Hi @gongyeted   If the camera is displayed in the RealSense Viewer's side-panel, are you able to use the Stereo Module if you go to the More option and select the menu option Hardware Reset to perform a reset of the camera, please?

Hi @gongyeted   Do you require further assistance with this case, please?   Thanks!

Hi @gongyeted Do you require further assistance with this case, please? Thanks!

I tried to use the option Hardware Reset but the error still happens when I using the Stereo Module. It seems that the realsense-viewer is still working despite this error occurs.

Hi @gongyeted Do you require further assistance with this case, please? Thanks!

yes I need further assistance, please. The detailed error information is:
"Timestamp:<PHONE_NUMBER>010.314941
Severity: Error
Description: Invalid Value in rs2_get_option(options:0x76ba4e0, option:Emitter On Off):
hwmon command 0x7d( 0 0 0 0 ) failed (response -21= No data to return)"

If the Viewer can work normally after the error occurs, it may be a timing hiccup when changing an option that the Viewer then automatically recovers from until the next time that the option is used.
What method did you use to build librealsense on Ubuntu, please: was it DKMS packages, building from source code, or using RSUSB?

Hi @gongyeted  Have you solved your problem, please?

Hi @gongyeted   Do you require further assistance with this case, please?   Thanks!

Case closed due to no further comments received.


[ALS-5232] Split bootstrap script to speed init

Split env specific configurations from bootstrap to streamline and speed up initialization.
Update kernel installation to loop over ssm kernels parameter (comma separated) and install multiple kernels.

There is no guarantee that the kernel will actually install within the <5 minute initialization window (which will kill the workspace deployment), so I've moved kernel install to the onStart sagemaker script. First invocation will get parameters and install kernels. Second+ invocation will get the parameter, see the kernel folders already exist, and skip installation. Users will have to check the kernels are finished initializing with less /var/log/install_kernel.log or tail -f /var/log/install_kernel.log.

Checklist:

[x] Have you successfully deployed to an AWS account with your changes?
[x] Have you successfully tested with your changes locally?

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

Reviewed in office hours, Nov 20, 2023.


Fix: remove references to c&s git submodule

Overview
Remove references to git submodule now that C&S code has been merged with Plan Tech
Changes
Removes references to C&S git submodule in GitHub workflows and Dockerfile
Checklist
Delete any rows that do not apply to the PR.

[ ] Title uses Angular commit convention
[ ] PR targets development branch
[ ] GitHub workflows/actions have been added/updated

IMO might be worth also removing all the references to submodules: true in the following workflows, but no biggie if not since it won't actually impact anything.
build-images.yml
code-pr-check.yml
deploy-images.yml
e2e-tests.yml
matrix-deploy.yml


Cherry pick script to set the version of Beam, use it to set version to 2.7.1-SNAPSHOT / 2.7.1dev

This PR begins work toward 2.7.1 release by preparing the branch with the appropriate version.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

The nature of the failure from a nonexistent GCP temp location appears to have changed in the service side since 2.7.0

@apilloud I think you mentioned that this script missed the most important version. So is it missing here?


Add link to Contributor Guide from Open Source page

Can we add a button on this page https://developer.tbd.website/open-source that links to the Contributor Guide?

fixed in https://github.com/TBD54566975/developer.tbd.website/commit/ff5c71c06bafcee5a9bb4b7a4c054e33d103d81a


fix(pattern): html entities now work in leadspace pattern

Related Ticket(s)
#1206
Description
I've updated the copy and h1 tags for the Leadspace pattern, so it now can use HTML entities as part of the text.
Changelog
New

HTML entity support added

I don't know if we want to allow html for the title and copy, we just want to make sure that the special characters aren't escaped - I think it's more so happening from storybook than the actual pattern

I don't know if we want to allow html for the title and copy, we just want to make sure that the special characters aren't escaped - I think it's more so happening from storybook than the actual pattern

I agree, maybe we would want just to document that the entities will not work on storybook


Remove human readable words from contract ID

In v0.10 three human readable words have been introduced as a checksum in the contract ID. While this may help to detect fake assets, I believe it presents also a few drawbacks:

Human readable words may carry unwanted and embarrassing meaning that the contract issuer may prefer to avoid. E.g. imagine a speculative asset getting as the checksum in the contract ID the words Price Always Dump, or more generally terminology that doesn't fit well with the image of the company issuing the asset. A workaround to this problem can be to brute-force the asset ID until a likeable checksum is produced, but this affects negatively the user experience of issuing an asset, and it may be hard to do on non powerful devices.
On mobile devices with small screens, the contract ID often needs to be truncated while displayed in the UI. With limited space, the user may end up seeing only the three words and a few bech32 characters, which can put the user more at risk of fraud as three words are easier to brute-force by an attacker than the 15-20 bech32 extra characters that could be displayed in the same space.

Moreover, I believe that protecting users from fake asset ID can be better done at the wallet level by providing extra features such as generating an image based on the asset id, similarly to GitHub default avatars. This solution has already been implemented in Iris Wallet and works quite well.
For these reasons I believe that simple bech32 contract IDs are preferable, and I propose to remove the human readable words from the ID as it was in v0.9. Let me know your thoughts on this.

I think pt.1 is quite reasonable.
BTW we do not use bech32 (which is space-inefficient w/o real benefits) but Base58 (prefixed by those words which are the checksum).
So instead of words, should we put a checksum as a HEX-encoded 8 chars in front?
Basically, w/o checksum users must compare at least 1/4 of the string (11 chars) to prevent actual brute force attacks (i.e. 64 bits of security, requiring in average 9 Exa-OPS to brute force) - which nobody would do in practice. Checking just checksum will be equivalent to checking 1/8 of the string (i.e. hacker will need the same computing resource to "mine" checksum as to mine 1/8-similar string, i.e. 32 bits of security or 4 Tera-OPS to brute force). Checking checksum + two initial chars (6+2 chars) gives us 32*2=64 bits of security - i.e. the same safety as checking 1/4 string and this is doable in practice. Thus, the checksum is really important and I think in the UI both the checksum and the two chars after it must be highlighted.
Summary of options:

No of chars to check
Bits of security
Bruteforce computational requirement

no checksum
11 chars
64 bit
9 Exa-OPS

just checksum
6 chars
32 bit
4 Tera-OPS

32-bit checksum + 2 chars
8 chars
64 bit
9 Exa-OPS

24-bit checksum + 8-bit XOR
6 chars
48 bit
281 Peta-OPS

2 different 16-bit checksums
6 chars
256 bit
exceeds universe computational capacity, equal to original hash security

Yes, we should use a 4-byte checksum in square brackets, like [f8dc5903], like how it's typically used to make a fingerprint for descriptors.
ripemd160(sha256(input))[0:4]
I realize this is just for a contract id and not a key, but it's sometimes better to do it like an existing way than to do it a new way.

I just learned, checksums are different than fingerprints
https://github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md#checksums
An 8 character checksum is better, I can see what you're saying now.

HEX-encoded 8 chars in front sounds good to me.

Two PRs:

https://github.com/UBIDECO/rust-baid58/pull/4
https://github.com/UBIDECO/rust-baid58/pull/5

I did some extensive tests (covering up to 24 bit checksum, since 32 bit my desktop can't crack) which had shown that overall any n bits can be cracked with O(2^n) hash operations. My best result I was able to achieve by combining two different hashes is O(2^(n+2)) operations (see https://github.com/UBIDECO/rust-baid58/pull/4).
Thus, two main conclusions:

checksum is nohow different from other parts of the hash in terms of anti-bruteforce protection, thus there is no point to visually separate it or enhance
to protect from attacks it is required to check at least half of the string (128 bits); checksum alone gives zero protection from a computationally-well equipped hacker

Thus, with those PRs the new IDs for RGB will look like
rgb:2dzcCoX9c65gi1GoJ1LFzb5FcQ9pAc8o3Pj8TpcH2mkAdMLCpP

ACK

ACK the format rgb:2dzcCoX9c65gi1GoJ1LFzb5FcQ9pAc8o3Pj8TpcH2mkAdMLCpP

Closed with #171


Translate eram.vcxproj into Japanese

This PR will fixes #11.

Looks good to me. Its been merged.


[Form Recognizer] Connect call failed.

We are running live Tests against other clouds like US Gov and Azure China Cloud. The goal is to check whether new azure sdk package work with other clouds or not.
Error Description:
We found that Connect call failed in the form recognizer were the main problem with unstable tests ( It occured in many tests. Such as: test_compose_model_transform, test_content_url_auth_bad_key, test_copy_authorization_v21, etc. ). Not only in the weekly pipeline, but also in the nightly pipeline. We may need to retry 3-4 times to make all tests pass.

        If the future has been cancelled, raises CancelledError.  If the
        future's result isn't yet available, raises InvalidStateError.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Event Hubs:0.13106492,Storage:0.12243542,Service Bus:0.11149711'

@zedy-wj we have been experiencing some networking issues with our test agents that I expect us to resolve next week.

Fixed, we will close it, thanks.


Fix a really bad thing

The previous codes block the event loop! Meaning no other tasks can be made in the process until this is done. Since nodejs is single threaded you should never do things like that. The new code converts it into a Promise. This is much better and works perfectly.

Thanks for contributing.


Acceptance of Payments for Invoices

Is there a potential of extending the invoices module to plugin gateways such as USA ePay or Authorize.NET so that Community Users can see their invoices and remit payments against invoices?  The idea here is to make the system more usable for creating a community portal capability as well as internal usage for clients.

Closed for a reason - there has been no activity for a long time.


Bulk creation of canvases

(not for MVP)
From the New Canvas dialogue, and also from somewhere in the file menu, you can launch a bulk import wizard.
This leans heavily on the URL Analyser #92 to make sense of whatever text you paste into a textarea, or (possibly) "upload" from a file (using file APIs).
Whatever string goes in there, the dialogue will split on all the things that you might want to split on and try to extract URLs; follow them and parse them.
It might also offer some choices about what to split on, such as when you open a CSV in LibreOffice Calc:

You can also label the links in markdown, perhaps:
- [https://getty.edu/codex/vol1#canvasIndex=13,120](Book 1 - The Gods)
- [https://getty.edu/codex/vol1#canvasIndex=121,412](Book 2 - The Ceremonies)

The dialogue can follow links, pull out thumbnails etc to help you decide what you want to pull in.
The end result is that a sequence of canvases will be added to the manifest.
(e.g., you could just scrape the URLs from a CSV or even a web page like https://digirati-co-uk.github.io/me-testing/02-images.html)

A version of this is working in PASTE operation.
But no UI yet.


Update to support Bevy 0.6

Just a tracking issue so I can follow when the new version gets released.
Is master being worked on it now?

Yup, I had to do some upstream work on mod_raycast first.

I'm successfully using bevy_mod_picking master branch with bevy 0.6.

Just tracking this issue too.
Thank you for what you do.

0.5 is out!

🙌 🎊 🎉
Get Outlook for iOShttps://aka.ms/o0ukef

From: Aevyrie @.>
Sent: Sunday, January 16, 2022 6:22:43 PM
To: aevyrie/bevy_mod_picking @.>
Cc: Mirko Rainer @.>; Manual @.>
Subject: Re: [aevyrie/bevy_mod_picking] Update to support Bevy 0.6 (Issue #114)
0.5 is out!
—
Reply to this email directly, view it on GitHubhttps://github.com/aevyrie/bevy_mod_picking/issues/114#issuecomment-1013976430, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMTS6CC6VA43F5A3NXRG3O3UWNHMHANCNFSM5LUMLLKQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>