Gradle removes C/C++ tasks from execution plan when the source is not initially available, even if it's available later

Expected Behavior
Gradle should always include native build tasks, regardless of whether source is available at execution planning time or not.
Current Behavior
Gradle silently ignores libraries that do not have source present on disk at execution planning time.
Context
This affects me specifically because I use an external dependency resolver tool. A simple "dependsOn" is used to ensure that the external tool is run before the library is built (and even works with parallel execution).
I noticed that on the first run, Gradle silently drops the libraries that had their source downloaded during a custom task from the execution plan, which means of course their dependent libraries fail to link. On the following runs, because the source is now downloaded and available, Gradle includes the libraries' tasks in the execution plan, and they finally compile in time for linking to occur.
Steps to Reproduce (for bugs)

Write a "dependency" NativeLibrarySpec component.
Write a "dependent" NativeLibrarySpec component.
Move the source of the "dependency" component so it is not visible to Gradle.
Run Gradle.

Gradle will silently ignore the "dependency" build tasks and attempt to build "dependent". Gradle should either error (since there are dependent tasks that can't run without "dependency" building) or warn.
Your Environment
Gradle 3.5 with the "c" and "cpp" plugins included.
Windows 7 64-bit, Visual Studio 2013 Express Edition for Windows Desktop

For the time being, removing the hasOutputs check wrapping the `return AbstractNativeLibraryBinarySpec.this.getBuildDependencies();' line in AbstractNativeLibraryBinarySpec works around the issue for me.

Actually, that workaround didn't work at all. This one did:
	source {
		srcDir '.'
		include '.empty.h'
	}

(where .empty.h has a simple line of no-op code to keep the compiler happy.)

Thanks for reporting this @javaJake. Have you tried generatedBy on as shown in the IDL sample?

@lacasseio thanks for the idea. Unfortunately, that does not work here because the "NativeComponentModelPlugin.Rules#configureGeneratedSourceSets" rule fails to apply as the task I give it to be "generatedBy" does not have a sourceDir.
I suspect there is a bug here too, since the private method "maybeSetSourceDir" there is a check to see if task.property is not null, which I suspect is a check to see if it exists. The task.property method actually throws a MissingPropertyException instead of/in addition to returning null, which causes Gradle to quit with an error.

No additional work will be done on the software model plugins unless it's a blocker for current users. This is not a blocker so I'm closing this issue. Reopen on gradle/gradle-native.


Creation of checksums on upstream nightly build

This addition creates the sha25sum and MD5sum files for the upstream nightly builds.
This was tested using temp dirs on build environment.

Did you push a new PR?


BlockBasedChunkMeta extends java.util.Collection implicitly

Code Location:
https://github.com/CivMC/CivModCore/blob/a71661ef833e938969c975c174e1bed4c28b00a5/paper/src/main/java/vg/civcraft/mc/civmodcore/world/locations/chunkmeta/block/BlockBasedChunkMeta.java#L24

Problem:
The class seems to be implicitly implementing the collections interface while not maintaining the proper inheritance rules. This may be misleading for anyone interfacing with the class.

Solution:
Add extends Collection and override the appropriate methods with the proper signatures.

I'm closing this out as something that we won't fix. It could be revisited in the future, but it's not within our capacity to work on right now.


Add contractors table with name, type and contract_number columns

Description
Create contractors table with name, type and contract_number columns
Setup
make db_dev_migrate
Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

@Ronolibert Where does this fall into the new db schema? If we have move transit orders and nts transit orders in separate tables, then I'm curious why/where we need to reference contractors.

@sarboc I think its because contractors can change. Each contract number is associated to a specific contractor. If they miss their performance scores then they can be replaced


Better description of attributes in code

Describe the bug
Not a bug, just a series of recommendations by @dey3434 for better description of attributes throughout the Intro and WhiteDwarf notebooks. code would be easier to understand with more comments and definitions of terms
Comments
Intro Notebook:

output 84: what is z?

White Dwarfs Notebook:

In second text box: "We're all familiar with our own sun a seemingly ever present that we see continually day to day"--missing a word
unnecessary capitalization of "Helium" in third text box
what are mag. errors?
what is the y axis for out [12]? is it flux?
"Given 'standard' stars, those with external distance constraints we can also" missing comma
explanation of flux needed

@alxogm We won't get this in for the release tomorrow, but trialing assigning someone to make sure the Spanish is updated in tandem.
@parfa30 If you commit one notebook at a time to your fork, I'll try and keep up.  That way we can converge on any style changes before a lot is done.
@dey3434 Feel free to take part!  Let us know if you need help with getting started with Git.  We do ask that you upload a photo to Git first, if you're going to contribute.  Get permission from your parents if you're still a minor!
Thanks!

I'm curious if @dey3434 is still taking a stab at these / made it to the finish? @parfa30

Hello!
I’m so sorry for the late response. I have not had a chance to work through any more of the notebooks, but I will be on my holiday break starting next week and would be happy to look at some other ones then! Could you remind me what stage this project is at? Do you still need help just going through the notebooks and giving general feedback?
Best,
Sharmila

On Dec 12, 2020, at 11:21 AM, Michael J Wilson<EMAIL_ADDRESS>wrote:
I'm curious if @dey3434 https://github.com/dey3434 is still taking a stab at these / made it to the finish? @parfa30 https://github.com/parfa30
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/michaelJwilson/DESI-HighSchool/issues/31#issuecomment-743795632, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSH6LM2FLVE6OFQIXE6VFLSUOYDDANCNFSM4RMDBRMA.

No problem, that'd be great!  We're still in development of the material and transitioning to a Berkeley Extensions course that would have a test and yield college credits.  There's still some work to do in forming a semi-complete picture and gauging the right level of difficulty.  It'd likely be useful to have a short chat, probably before and after looking at any more notebooks - assuming Arjun etc. is good with that.


Apache airflow pipeline

The pipeline setup is done.
Docker is also configured accordingly.
For pipeline data currently linked to PostgreSQL.
Simple tasks added to DAG folder

@Keldami hey I have rebased with the main branch could you merge it to the main

Do not delete the branch.


CloudFlare Adapter v10 fails

Error logs:
Error: Failed to publish your Function. Got error: Uncaught TypeError: Cannot read properties of undefined (reading 'ReactCurrentDispatcher')
  at renderers.mjs:64:443

Already reported on withastro/adapters#211. Tracking.

Fixed.


Bump "friendsofphp/php-cs-fixer": "^3.0", > 3.1

Discussed in https://github.com/codebar-ag/laravel-flysystem-cloudinary/discussions/5

Originally posted by StanBarrows September  4, 2021

[ ] Bump "friendsofphp/php-cs-fixer": "^3.0", > 3.1

Fixed by #8 .


Fix build failure in travis due spot bug issue

Purpose
This is to fix the build failure in travis, error log as follows,
[INFO] Impossible cast from org.wso2.ballerinalang.compiler.tree.expressions.BLangBinaryExpr to org.wso2.ballerinalang.compiler.tree.BLangPackage in org.ballerinalang.net.grpc.proto.ServiceProtoBuilder.process(ServiceNode, List) [org.ballerinalang.net.grpc.proto.ServiceProtoBuilder] At ServiceProtoBuilder.java:[line 124] BC_IMPOSSIBLE_CAST
[INFO] Impossible cast from org.wso2.ballerinalang.compiler.tree.expressions.BLangBinaryExpr to org.wso2.ballerinalang.compiler.tree.BLangPackage in org.ballerinalang.net.grpc.proto.ServiceProtoBuilder.process(ServiceNode, List) [org.ballerinalang.net.grpc.proto.ServiceProtoBuilder] At ServiceProtoBuilder.java:[line 127] BC_IMPOSSIBLE_CAST

Approach
Check the Node kind before cast.
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Did a full build in local machine with this fix, not found any issues with this fix


Set up relational database schema

Create a normalized schema to store NPC data, following ER diagram.
Criteria:
The database should support all NPC attributes and relationships.

Close due to duplicate


Do i need to define a image loader to import images ?

Hi, thanks for your great job. When i try to run this project, i can't find the place to place my rgbd data path,  do i need to define an image loader to run this project ?

just see this https://github.com/ethz-asl/tsdf-plusplus/issues/5#issuecomment-1411390630


adds tracing system calls using ebpf blog

Signed-off-by: ashutoshcloud<EMAIL_ADDRESS>(CloudDefense.AI)
What type of PR is this?
/kind content
Any specific area of the project related to this PR?
/area blog
What this PR does / why we need it:
This PR adds a blog to educate community about how to use eBPF programs to trace system calls.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ashutoshcloud
Once this PR has been reviewed and has the lgtm label, please assign vjjmiras for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

content/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ashutoshcloud, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Raise exceptions

Note
This PR builds on #338. I unfortunately can't set the base when cutting a PR from a forked repo. Reviewing it commit by commit after skipping the first commit would be helpful.

[x] #338

BREAKING CHANGE: ruby-openai now raises errors instead of silently ignoring them. It is better for production apps to fail fast and take note of any errors instead of ignoring them. OpenAI is not expected to return any invalid payload in its normal operation.
Removed the completion test case from the finetunes suite because it wasn't adding any value since it doesn't really exercise an actual fine-tuned model. Besides, the create cassette was broken (had 400 responses throughout). The reason that test was passing is because ruby-openai was eating those errors.
Tweaks to README:

Tweak/add some bits about token counting during streaming
Replace "ChatGPT" with "GPT" (the former is a web app, the latter is the actual model)

All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?

Thanks @atesgoral - taking a look now

Ah, I just remembered removing that HTTP error case from the http spec because I was running into issues with mocking a request. I then added a VCR at the client spec level instead.
The old test might have popped back in due to a bad rebase. I removed it again.


New treesitter highlight groups

I would like to make a PR for updating the highlight groups, is this repo open to such PRs?

Yes! thanks :) (i may be delayed in responding though)


Can't test donation adding through API

a) No "post ticket" donation options screen
b) blocked by API issues on Donorfy side

you'll need to create these options.
Log for the demo account is the same as it's always been<EMAIL_ADDRESS>& testing

@roselukas can you or Marina please create this in events.scolvin.com ? As you've done it before will be quicker than me figuring it out. I can then test it and test it working with the API. Thanks

Sure Azadi. I’ll be back at my laptop in 30
Sent while on the run, please excuse any typos

From: azadiproductle<EMAIL_ADDRESS>Sent: Tuesday, October 16, 2018 7:44:24 PM
To: samuelcolvin/nosht
Cc: Rose Lukas; Mention
Subject: Re: [samuelcolvin/nosht] Can't test donation adding through API (#156)
@roselukashttps://github.com/roselukas can you or Marina please create this in events.scolvin.com ? As you've done it before will be quicker than me figuring it out. I can then test it and test it working with the API. Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/samuelcolvin/nosht/issues/156#issuecomment-430310431, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AncwIzWrcoV0Q9b7nPCY_6wyxQAOdgR2ks5ulgzogaJpZM4Xc8Tt.

It couldn't really be simpler to create these options.
I've just created one for each of the categories.


Improve compatibility page (#7490)

Pull request opened by the merge tool on behalf of #7490

Merged into branches iso7 in 325f77c81c27f460c4f167894dd5e35434bd042d


Order of instanciation is random or follows an implicit rule

The order of instanciation seems to be backward or random.
Why this could be a problem?
-> In arduino if you initialize the Serial port in one instance (at the begining) and use it in an other (in the begining) you're not sure it will be initialized before you use it.
It could be usefull to be able to decide it explicitly.
Here are some examples which seems to follow a backward rule, but in more complexe examples I can't say if it still follows this rule or not.
------ Config ------
configuration PingPongCfg
@arduino_stdout "Serial"
{
    instance client1: Client1
    instance client2: Client2
    instance server: Server
    connector client1.myPort => server.myPort
    connector client2.myPort => server.myPort
}

------ Result ------
// The Init messages are in the "on entry" of thing's statechart
[ Server ] Init server
[Client 2] Init Client 2
[Client 1] Init Client 1
[Client 1] Send Ping
[ Server ] Ping received, sending pong
[Client 1] Pong received
[Client 2] Pong received
------ An other exemple ------
configuration PingPongCfg
@arduino_stdout "Serial"
{

    instance server: Server <==================
    instance client1: Client1
    instance client2: Client2
    connector client1.myPort => server.myPort
    connector client2.myPort => server.myPort

}

------ Result ------
[Client 2] Init Client 2
[Client 1] Init Client 1
[Client 1] Send Ping
[ Server ] Init server <==========================
[ Server ] Ping received, sending pong
[Client 1] Pong received
[Client 2] Pong received

Thatt is the magic of EMF.... The order on collections is... magic...

I am currently implementing some helpers that will return the list of dependents clients/servers for a given instances, etc. So that, at least in some cases, we can have a start order that respects client/server dependencies (typically works if it is no cycles in the connectors).

OK, I added derive properties in configuration and implemented a proper ordering in the JS compiler, which you (@Lyadis) can port to the C compiler. Basically we start by all instances without any server, then we continue with instances clients of the set of instances of the previous set, etc. At the end (typically if it is some cycles, we start all the rest in whatever order).
I would need to test a bit more on some tricky cases, but it is at least a starting point, which should solve most of the ordering problems.

you should not use List.contains or List.containsAll as the equals in EMF is broken (!!!). Rather use the contains and containsAll methods I have defined, which use EcoreUtil.equals

I implemented something in the C compiler, and added some test.
Some tests appear not to be working with Java and JS compiler, but whether or not it is a problem of specification or implementation can be discussed.
The configuration to be tested is the following:
connector B.r => A.p
connector C.r => B.p
connector B.r => D.p
connector D.r => C.p
connector E.r => C.p

where A,B,C,D,E are instances, r is a required port, and p a provided one.

The order produced with JS compiler is ADBEC while in my opinion E should be initialized in last, because it requires C.

Yes, seems like a bug

Well, since you got the algorithm right (I am preparing a complex test, hehe) and since it is good for you to get started with Java and JS compiler, I re-assigned the issue to you, so that you can fix it in those compilers. :-)


I can‘t login in play store，help please

This is related to DNS Resolving. Probably your antivirus was blocking requests on port 53/UDP on your machine.


Sleep Cycle Extension

Is your feature request related to a problem? Please describe.
calculating your  sleep cycle is important for various health reasons
Describe the solution you'd like
A simple sleep cycle extension that helps you understand your sleep cycle
Describe alternatives you've considered
Mobile apps but they are complex
Additional context
GSSoC'24

Please assign me this issue @Sulagna-Dutta-Roy

Already raised and added to my repository #1187


[Collaboration] Implementation of Player Guide + Updating Pause Menu

Design and Implement Player Guide in the Pause Menu
Feature: #247
The in-game player guide is a quick and easy tutorial that the user can browse through. This can be accessed in the pause screen menu under "player guide". It will also include information such as:

Game Overview
How to Craft
Finding / Picking up items and potions
Weapon Buffs
Skill Tree information
Levelling Up
Accessing Inventory
How to win the game

Dependencies

#152

Milestones
List of steps that need to be completed for this task.

[x] Create a new button on the pause screen called "player guide" [Oct. 9]
[x] Implement the code for the new pause screen [Oct. 11]
[x] Create Pages / designs for the player guide [Oct. 9]
[x] Conduct user survey if users want to add extra information / recommendation for design improvement [Oct. 9]
[x] Implement the code for the player guide screen [Oct. 12]

Completion Deadline: Oct. 12
Documentation

Player Guide Implementation

Member

Chaitanya Dasi Luanzon (@cluanzon)
Enoe (Jolo) Gapusan (@jgapusan)
Yingzheng Cai (@Rey-666)

I fixed some typo in this collab ticket, and add the documentation link, cheers!

I just finished implementing the player guide for both level 1 and 2, they have been merged and pushed to the main branch! I will be starting to debug after this wednesday, cheers guys! Great effort!


有针对模型随机权重初始化的方法吗？我是新手,麻烦提供相应的案例

Is there a way to initialize random weights for the model? I am a novice, please provide the corresponding case

Yes, unless you load saved weights, every module will have random weights upon creating.

@NiklasGustafsson  i will not attempt English back to Chinese 😄

I will close this issue, given that an answer has been provided. Please re-open if the answer is not satisfactory.


I24 ssx: use detector devices from dodal

Use devices from dodal to trigger the detector for serial. Detector used: eiger 9M and pilatus 6M (second one needs to be created in dodal first)

Update:

Eiger: waiting for work on fastcs eiger in ophyd_async to be completed
Pilatus: detector going away soon-ish, so probably not needed
Jungfrau (once functionality added to serial): incoming new detector, there's a device for the 1M in the commissioning branch that could be reused once updated to ophyd-async. Once 9M arrives, will also need updating


Support for Korean and Vietnamese Holidays.

Support for Vietnamese Holidays.
Better Korean Lunar Calendar Calculation
Support for Vietnamese Holidays.
Fixed PEP8
Code Coverage 100%

Pull Request Test Coverage Report for Build 758

234 of 234 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 756:
0.0%

Covered Lines:
8614

Relevant Lines:
8614

💛  - Coveralls

Hey there @1kko
very good cleanup work, thank you very much!
What is still to be done is removing code coming from https://github.com/usingsky/korean_lunar_calendar_py/
Instead, relevant logic should be loaded in the project as a library dependency (ie: using pip install ..).
Please let me know, thank you very much
dr-p

@dr-prodigy Thank you for reply. I just fixed it and done commit.
Please review.

This is a great work.. thank you very much!
Cheers
dr-p


Invalid image name for mariadb

Is this a request for help?:
No.
Is this a BUG REPORT or FEATURE REQUEST?
Bug report.
Version of Helm and Kubernetes:
Helm:
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
k8s:
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.4", GitCommit:"9befc2b8928a9426501d3bf62f72849d5cbcd5a3", GitTreeState:"clean", BuildDate:"2017-11-20T05:28:34Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Which chart:
mariadb
What happened:
The latest mariadb chart produces the incorrect image name. With debug, this is the image created:
image: "map[pullPolicy:IfNotPresent repository:bitnami/mariadb tag:10.1]"

What you expected to happen:
Release created successfully
How to reproduce it (as minimally and precisely as possible):
This yaml:
image:
  repository: bitnami/mariadb
  tag: '10.1'
  pullPolicy: IfNotPresent
rootUser:
  password: pwd
  forcePassword: true
db:
  user: user
  password: pwd2
  name: db
  forcePassword: true

Run:
helm install --name mariadb-release -f values.yaml --debug stable/mariadb

Anything else we need to know:
It works perfectly with version 4.1.1.
Here are the events from pod describe:
Events:
  Type     Reason                 Age               From                               Message
  ----     ------                 ----              ----                               -------
  Warning  FailedScheduling       2m (x7 over 2m)   default-scheduler                  PersistentVolumeClaim is not bound: "oh-mariadb-release-mariadb"
  Normal   Scheduled              1m                default-scheduler                  Successfully assigned oh-mariadb-release-mariadb-78d444799f-tzrzr to aks-agentpool-95095170-0
  Normal   SuccessfulMountVolume  1m                kubelet, aks-agentpool-95095170-0  MountVolume.SetUp succeeded for volume "config"
  Normal   SuccessfulMountVolume  1m                kubelet, aks-agentpool-95095170-0  MountVolume.SetUp succeeded for volume "default-token-7cxgz"
  Normal   SuccessfulMountVolume  20s               kubelet, aks-agentpool-95095170-0  MountVolume.SetUp succeeded for volume "pvc-a7085792-69b6-11e8-9ed1-0a58ac1f09f2"
  Normal   Pulled                 19s               kubelet, aks-agentpool-95095170-0  Container image "busybox" already present on machine
  Normal   Created                19s               kubelet, aks-agentpool-95095170-0  Created container
  Normal   Started                19s               kubelet, aks-agentpool-95095170-0  Started container
  Warning  InspectFailed          2s (x3 over 18s)  kubelet, aks-agentpool-95095170-0  Failed to apply default image tag "map[pullPolicy:IfNotPresent repository:bitnami/mariadb tag:10.1]": couldn't parse image reference "map[pullPolicy:IfNotPresent repository:bitnami/mariadb tag:10.1]": invalid reference format
  Warning  Failed                 2s (x3 over 18s)  kubelet, aks-agentpool-95095170-0  Error: InvalidImageName

Hmm, I'm not seeing this error when I try and install the latest mariadb release. What happens if you run helm repo update and then try again?

Yes, I tried after a helm repo update and 4.2.1, which I was using a week ago, is now working. I also tested 4.2.2 and 4.2.3 and they all work. Thanks.


Shared workspace

Summary
An abstraction over volumes that allows all nodes in a workflow to access a shared workspace or reading and writing files.
Use Cases
Simpler than artifacts.
See #4130

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Fixed by emissary.


dessil, enddamaging

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[d,e]

/trunk merge


Customizable width/height?

Emacs can display a vertical/horizontal bar with customizable pixels wide/high. See https://www.gnu.org/software/emacs/manual/html_node/elisp/Cursor-Parameters.html . It'd be nice if block-cursor can customize the width/height of the cursor.

I can't change the size (i.e. width and height) of the cursor, because that would mess with Atom's cursor placement (and maybe other things as well). I can however change the thickness of the lines of the bordered-box, i-beam and underline cursors, so I'll add that as an option.


Generating schema for UClasses that are not explicitly loaded/referenced by the currently loaded level is not supported

Issue
Generating schema for UClasses that are not explicitly loaded/referenced by the currently loaded level is not supported. For example, a hard coded path loaded at run-time will not be detected by the schema generator.
Workaround
Reference the class explicitly from an already loaded class (Level blueprint, GameMode etc). Alternatively, you can open the Blueprints for soft references before generating schema so that they are loaded into memory.
Internal ticket
NA

Fixed in 0.4.0


HHH-12387 - Immutable entities can be updated via bulk update queries

https://hibernate.atlassian.net/browse/HHH-12387

@sebersole I updated the PR according to your suggestions. By default, we are going to issue a Warning, but the user can also customize the behavior and trigger an Exception instead.


feat: support choosing groups to lock

Signed-off-by: Frost Ming<EMAIL_ADDRESS>

@frostming feel free to create 0.3.0 tag


Can't Set property

It's currently not possible to set a DBus property to a service.
Let's consider this minimalistic service:
let ifaceDesc = {
	name: 'fr.diag',
    properties: {
		StringProp: 's'
    }
}

let iface = {
	StringProp: 'Hello, world!'
}

When it runs, we can introspect it with gdbus and see that it has indeed a property StringProp with type s (string):
gdbus introspect -e -d fr.diag -o /fr/Diag

node /fr/Diag {
  interface fr.diag {
    methods:
    signals:
    properties:
      readwrite s StringProp = 'Hello, world!';
  };
  interface org.freedesktop.DBus.Properties {
    methods:
      Get(in  s interface_name,
          in  s property_name,
          out v value);
      GetAll(in  s interface_name,
             out a{sv} properties);
      Set(in  s interface_name,
          in  s property_name,
          in  v value);
    signals:
      PropertiesChanged(s interface_name,
                        a{sv} changed_properties,
                        as invalidated_properties);
    properties:
  };
  interface org.freedesktop.DBus.Introspectable {
    methods:
      Introspect(out s xml_data);
    signals:
    properties:
  };
  interface org.freedesktop.DBus.Peer {
    methods:
      Ping();
      GetMachineId(out s machine_uuid);
    signals:
    properties:
  };
};

We can then use gdbus to get the value of the property:
gdbus call -e -d fr.diag -o /fr/Diag -m org.freedesktop.DBus.Properties.Get 'fr.diag' 'StringProp'

(<'Hello, world!'>,)

So far, so good.
Now, trying to set the property:

gdbus call -e -d fr.diag -o /fr/Diag -m org.freedesktop.DBus.Properties.Set 'fr.diag' 'StringProp' "<'Bye, guys!'>"
()

And when trying to get it again (either directly asking Get with gdbus or trying to introspect):
gdbus call -e -d fr.diag -o /fr/Diag -m org.freedesktop.DBus.Properties.Get 'fr.diag' 'StringProp'
Error: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
(According to introspection data, you need to pass 'ss')

And in the terminal where I had my service run, I've got:
Error: Expected string or buffer argument, got 1234 of type 's'
    at writeSimple (~/node_modules/dbus-native/lib/marshall.js:106:13)

Grepping on this 1234, I've found that Set is not yet implemented
So we should fix this :-)

I'm working on it, I have implemented setting single types for now (so every type that is not a container) here.
Sorry for the console.log which slipped, it will be put inside a if (DEBUG) in next commits.
Currently working on implementing on setting complex values.

I've pushed e6958f535db63669b346b4f8e8119c845655861d which should close this issue.
Test it then keep me up. I have included two example files server-properties.js and client-properties.js to demonstrate how this is used.

@sidorares did you have a chance to test it?


dbeaver/dbeaver#19904 Show original variables/parameters names

How to distinguish variable set as case-insensitive with @set AbC = 1 which turn into ABC under the hood, and case-sensitive variable set as case-insensitive with @set "AbC" = 1?

Now  case-sensitive behavior works with  bind parameters, but with variables no:

@MashaKorax to make variable or parameter case-sensitive it should be quoted

@E1izabeth variables/params resolve behavior didn't change. The only change in this ticket is that we show original variable/parameter name in binding dialog

@serge-rider yes, I see, that's why I'm asking of how to distinguish visually variables in those two cases now.

It will show the name from the first occurrence (AbC).
It is better than ABC I think.

But "AbC" and AbC are two different variables 🤔

verified


Upgrade react-overlays

The new version is much smaller. Nice job!
The placement=bottom seems does not work. Dunno how to fix this. I get this

cc @jquense

@jquense I fixed the problem

@jquense Are you ok to go with prerelease dependency?

@jquense Calendar is a big part of my app. Do you mind me to collaborate?

Ok, which cases I should consider? Also do you want to publish on npm by yourself?

Sure, I will keep these things as is. My biggest concern are dependencies. Could you make a release? And I will start looking at issues.


Build off this if y'like

Hey @atmos! If you're interested, we built this for Jekyll's hubot: https://github.com/jekyll/hubot-pr-status/blob/master/src/pr-status.coffee
Let me know if you want to build off that code, or, in probably more likely, let me know when you complete this module so we can let users of that module to use yours instead.
Happy coding! Hope all is well. :tada:

Yo, that'd be dope. I kinda of want two things.

ci status repo/branch - See the status of the required contexts via protected branches in complex cases and just the default one if there's only one context.
ci build repo/branch - See how hard it is to pass build requests off to travis or whatever.


Crash while tesselating block model

With a combination of OptiFabric, FerriteCore and Minecraft Transit Mod, the game will have a chance of crashing when Minecraft Transit Mod's Automatic Platform Gates opens.
This seems like a separate issue and is unrelated to FerriteCore, but I can no longer reproduce the crash after removing FerriteCore.
Crash report
FerriteCore Config:
replaceNeighborLookup = true
replacePropertyMap = true
cacheMultipartPredicates = true
modelResourceLocations = true
multipartDeduplication = true
blockstateCacheDeduplication = true
bakedQuadDeduplication = true
compactFastMap = false
populateNeighborTable = true
Here's what some other modder has to say (Which I don't quite understand):

Is there any chance this could be resolved? Or are we stuck with this crash

I have at least a general idea on what's causing this (a race condition on the cache used for multipart models), but I need to look into it in more detail.  For now disabling multipartDeduplication in the config might "fix" it.


No labelText Option

I would like to add a label to the TextField widget in the InternationalPhoneInput widget. Allowing a positional parameter to pass in an optional labelText would add this feature quite easily

I forked the repository and added a simple fix to this issue. The pull request can be found here.

Thank you @drakebw. This is merged.


How to build a project from the latest repo

I have now fork from the latest react-native-draggable-flatlist. But I'm having a problem when I run the "yarn run build" command, it seems that the scripts command in package.json is not correct.

I have built it, but when using the library, I have a problem that it cannot be used.

This is tsconfig.json

When I run the command "yarn run build", and this is the output I get

Can anyone guide the script to build, publish to npm and use the library?

@computerjazz Can you help me this problem !!


Issue with "Debugging" in @site/docs/integrations/debugging.md

Describe the problem

Page: Debugging
Source: https://github.com/demisto/content-docs/tree/master/docs/integrations/debugging.md

The first section of this doc, does not make too much sense....
Screenshots

Environment

OS: [e.g. Windows]
Browser: [e.g. chrome, safari, firefox..]
Browser Version:

Suggested fix

@fvigo can you please have a look?


[FIX] DIDExchange should handle legacy DIDDoc format

As found here, aries-vcx DIDExchange handlers are not resilient to the case where the request or response message has a did_doc attachment that is a legacy DIDDoc structure (i.e. an older "aries" diddoc: https://hyperledger.github.io/aries-rfcs/latest/features/0067-didcomm-diddoc-conventions/#implementations).
This is particularly problematic when the peer is using a legacy DID, as this is when the peer would attach a did_doc. E.g. ACApy has been found to do this, causing AATH failures.
Other agents, like acapy, are tolerant to both legacy and spec-compliant DIDDoc structures in their DIDExchange handling.
To fix this, i believe we should do the following:

add a method to convert from the legacy structure (AriesDidDoc in aries/misc/legacy/diddoc_legacy/src/aries/diddoc.rs) into the spec-compliant structure (did_core/did_doc/src/schema/did_doc.rs). This method could probably live in the diddoc_legacy crate as a signal to consumers to migrate to use the new format; AriesDidDoc::try_into_compliant
Have the attachment_to_diddoc DIDExchange helper function in aries-vcx have a fallback of; 1. deserialize into AriesDidDoc, 2. convert AriesDidDoc into compliant DidDocument.

Alternatively to 2. ^, if it's more efficient, we could have some internal helper serde struct defined to represent both variants like a union type, then deserialize into that union type, then run the 2.2. conversion step if needed. e.g.:
#[serde(untagged)]
enum TolerantDidDocument {
    Compliant(DidDocument),
    Legacy(AriesDidDoc)
}

impl TolerantDidDocument {
    pub fn try_into_compliant(self) -> Result<DidDocument> {
       match self {
           Self::Compliant(c) -> c,
           Self::Legacy(l) -> l.try_into_compliant()
      }
   }
}

ACAPY helpful reference
ACAPy also has a converter for legacy -> compliant, found here: https://github.com/hyperledger/aries-cloudagent-python/blob/5ad52c15d2f4f62db1678b22a7470776d78b36f5/aries_cloudagent/resolver/default/legacy_peer.py#L27. it could be used as a reference

@JamesKEbert there's arguably no point in doing this if we don't care for supporting for unqualified DIDs in DIDExchange. my understanding is that did_doc attachment is only used if unqualified DIDs are being used (i.e. bcus they are unresolvable). thoughts?

@gmulhearn-anonyome I'd tend to agree in that since we're attempting to migrate away from using unqualified DIDs as a community then it's not really worth the effort to add support for them, unless there's some strong need for that backwards compatibility that I'm not aware of.

@swcurran, we're inclined to not develop support for this legacy format given that we as a community are working to move to qualified DIDs entirely and it makes less sense to add support for something we'll be shortly thereafter removing support for. Is there something I'm missing though that should change this viewpoint?

Trying to understand the context.  I think you are saying that support for DID Exchange instances where the DIDDoc is inline is not going to be supported. Rather, only DID Exchange instances where a DID is specified will be used.
I think that is definitely what to do on the sending side.  If it is “easy” to support receiving DIDs in both ways, it would be nice to handle that.
That said, in this case, because of how far we are in getting rid of unqualified DIDs (“You MUST only send qualified DIDs”), you would excused to not add the extra complication of not accepting any unqualified forms.

Thank you for the helpful comments Stephen.

I think this is wise :)
Given the ongoing headaches that it would impose to add backwards support for any unqualified DIDs to VCX/DID Exchange and the discussion above, I am going to close this issue.


fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cbr/ibm (source)
module
minor
1.18.1 -> 1.19.0

terraform-ibm-modules/key-protect-all-inclusive/ibm (source)
module
minor
4.6.0 -> 4.7.0

Release Notes

terraform-ibm-modules/terraform-ibm-cbr (terraform-ibm-modules/cbr/ibm)
v1.19.0
Compare Source
Features

added pre-wired rule for Event Notification (Messagehub) to HPCS (#406) (acd3d60)

terraform-ibm-modules/terraform-ibm-kms-all-inclusive (terraform-ibm-modules/key-protect-all-inclusive/ibm)
v4.7.0
Compare Source
Features

key_protect_endpoint_type variable has been renamed to key_protect_allowed_network and only supports the following values: public-and-private (default value) and private-only (#413) (5841fb0)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

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


Introducing JSON to Lettuce

Granted, this review turned out much much much bigger than I anticipated.
Instructions for reviewing
Ideally please concentrate on the most important decisions:

API surface as defined by src/main/templates/io/lettuce/core/api/RedisJsonCommands.java
sample use cases in the src/test/java/io/lettuce/core/RedisJsonCommandBuilderUnitTests.java
integration of the Jackson parser in the src/main/java/io/lettuce/core/json/DefaultJsonParser.java
use the testcontainers fw to deploy docker-stack src/test/java/io/lettuce/core/RedisContainerIntegrationTests.java

General considerations
(for more details check the README.md with some more information)
This implementation aims to solve several general problems:

avoid any JSON processing as part of the Netty event loop
provide Lettuce-specific interfaces to handle JSON as DOM
provide the means to apply RedisCodec encoding and decoding
abstract from the RESP2 vs RESP3 specifics
support both JsonPath v1 and JsonPath v2

Three operating modes facilitating default (basic), advanced and power-user usage
Default mode

[x] Uses Jackson behind the scenes, but provides a driver-specific API to avoid tight coupling with any 3rd party library
[x] Deserializes lazily the data returned by the server to avoid slowing down the event loop
[x] Serializes the data when sending JSON to the server before passing it to the event loop
[x] Allows for the usage of RedisCodecs to enable usage of different data types without explicit conversion *(1)

Advanced mode (incomplete, but considered in the design)

[ ] Allows the users of the driver to provide custom parsers utilizing other third party libraries or their own implementation

Power-user mode

[x] Makes it possible to use the JSON data in raw format, for example work only with byte buffers without parsing

Notes

The Jackson parser uses byte arrays and strings for parsing data. Although codec conversion is not enforced in cases when the Jackson parser modifies JSON documents in memory conversion might be required as it does not handle all data types, e.g. if the user is using some other representation of the data the driver would use the codec the user has supplied to convert to bytes and then the StringCodec to convert to String
changes were required to the way the command enumeration as the the JSON.X commands have a dot in their name
changes were required to the CommandBuilder to avoid making it too large and attempt to follow the single responsibility principle
the stateful connection class was extended to facilitate the parser logic - I am not particularly fond of this and will try to change it

Leftovers

[ ] object mapping functionality (e.g. provide a .class file to a method)
[ ] handle null values
[ ] sane mechanism for changing the currently used parser
[ ] >80% coverage with unit tests
[ ] 100% of commands tested with integration tests
[ ] integration tests for clustered environments

Unrelated changes
There are a few unrelated changes such as adding missing imports in 3 other template files
Supported commands

Command
Status

JSON.ARRAPPEND
✅ Implemented

JSON.ARRINDEX
✅ Implemented

JSON.ARRINSERT
✅ Implemented

JSON.ARRLEN
✅ Implemented

JSON.ARRPOP
✅ Implemented

JSON.ARRTRIM
✅ Implemented

JSON.CLEAR
✅ Implemented

JSON.DEBUG
❌ Not planned

JSON.DEBUG MEMORY
❌ Not planned

JSON.DEL
✅ Implemented

JSON.FORGET
❌ Not planned

JSON.GET
✅ Implemented

JSON.MERGE
✅ Implemented

JSON.MGET
✅ Implemented

JSON.MSET
✅ Implemented

JSON.NUMINCRBY
✅ Implemented

JSON.NUMMULTBY
❌ Not planned

JSON.OBJKEYS
✅ Implemented

JSON.OBJLEN
✅ Implemented

JSON.RESP
❌ Not planned

JSON.SET
✅ Implemented

JSON.STRAPPEND
✅ Implemented

JSON.STRLEN
✅ Implemented

JSON.TOGGLE
✅ Implemented

JSON.TYPE
✅ Implemented

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
[ ] You applied code formatting rules using the mvn formatter:format target. Don’t submit any formatting related changes.
[ ] You submit test cases (unit or integration tests) that back your changes.

This looks really good! It will be a nice addition to Lettuce. Just a couple things:

I did not see tests against Redis Cluster.
There does not seem to be an implementation of key routing in case of JSON.MGET with the Cluster API.

Hey @jruaux , thanks a lot for taking a look!
Yeah these two points are very valid ones. Let me see if I can address them with an update.

Hey @tishun, ...tracking... stuff got in here. Is it intended?

Hey @tishun, ...tracking... stuff got in here. Is it intended?

No, but this is because the PR is fork/redis-json -> origin/redis-json and origin/redis-json is now behind origin/main
I will try to fix this.

Overall, this is a good first iteration, but binding all JSON interfaces to generic types of Lettuce codec seems unnecessary and just increases the complexity of the code.

There is no way to use the Codec system without having the generics, as we discussed offline. I do - however - agree that the key in a JSON file does not map to the redis key, used as part of most commands. As Such I will refactor the code to only consider the value generic.

Also, we need more developer-friendly overloads for frequently used commands like JSON.SET. See my inline comments for more details.

Agreed, this is one of the leftovers

Overall, this is a good first iteration, but binding all JSON interfaces to generic types of Lettuce codec seems unnecessary and just increases the complexity of the code.

There is no way to use the Codec system without having the generics, as we discussed offline.

After some more careful consideration I actually fully agree with you.
The latest version does not have any generics for the JsonValue / JsonParser abstractions as they did not help in any way.


[styles] Bump jss dependencies to 10.0.0

Stable version is released: https://github.com/cssinjs/jss/releases/tag/v10.0.0

Maybe use caret now?

Maybe use caret now?

I thought we already did. Thanks for catching that :+1:


4.0+ doesn't start on restart

Describe the bug
On a home assistant restart, the add-on either doesn't seem to restart (Start on boot is selected) or MQTT messages are not received(?) .. does not pick up status of various alarm components. Worked on reboot prior to 4.0.
Home Assistant 0.114.4
Ring Hassio 4.0.4
External MQTT broker

When you say restart Home Assistant, do you mean system reboot, or just Home Assistant restart?  It's a little confusing because you mention start on boot, which isn't involved in Home Assistant restart, only a system reboot.
Also, without logs I'm not sure what you expect me to be able to do.  The add-on logs should clearly show if the add-on is running or not, and it's up to Home Assistant to start the add-on during boot.  I run this on 3 different systems and all handle restarts and reboots with no issue and the logic around this did not change in any significant way since 3.0.
One thing to check if you are talking about Home Assistant restarts, were you using the old birth/last will MQTT settings in configuration.yaml?  If you're using the web configured MQTT integration, what are your birth/last will settings there?  This is how the add-on knows if Home Assistant is restarted, although this is not related to reboots.

Hi @tsightler
If I do a Home Assistant restart (i.e. from Configuration > Server Controls), all entities upon starting up are unavailable until I restart the Ring add-on.
Sample of Ring logs
2020-09-11T02:44:22.194Z ring-mqtt ring/b995eb74-777a-4500-68e6-7fa53e76eb4c/alarm/36085e7e-75d5-4d9e-900c-46c1f5b08b19/info/state {"batteryLevel":100,"batteryStatus":"full","commStatus":"ok","firmwareStatus":"up-to-date","lastCommTime":"2020-09-11T01:45:46.630Z","lastUpdate":"2020-09-11T01:45:46.769Z","linkQuality":"ok","serialNumber":"xxx","tamperStatus":"ok"}
2020-09-11T02:44:22.963Z ring-mqtt ring/b995eb74-777a-4500-68e6-7fa53e76eb4c/alarm/cf0c233f-01ca-4906-9f3c-ac60942eff22/info/state {"acStatus":"ok","batteryStatus":"charged","brightness":0.4048583,"commStatus":"ok","lastUpdate":"2020-09-11T00:19:21.078Z","serialNumber":"xxx","tamperStatus":"ok","volume":1}
2020-09-11T02:44:24.383Z ring-mqtt Home Assistant state topic homeassistant/status received message: offline

My MQTT configuration:
mqtt:
  broker: !secret synology_ip
  username: !secret mqtt_user
  password: !secret mqtt_password
  discovery: true
  discovery_prefix: homeassistant
  birth_message:
    topic: 'hass/status'
    payload: 'online'
    qos: 0
    retain: false

Like a lot of people I'm guessing, I have a manual MQTT configuration and as far as I'm aware its default settings. Appears as if all of my other MQTT sensors are available upon reboot, this started occurring with 4.0, hope that's helpful. Thanks

As noted in the documentation of ring-mqtt, Home Assistant >0.113 changed the default birth/last will message topic from 'hass/status' to "homeassistant/status" and made birth messages default.  This was part of an overall change to standardize the way MQTT addons can monitor for Home Assistant restarts, something this script has done from the start, but many other tools never implemented.  The 4.0.0 release and beyond use this new default since they were developed and released after 0.113.  To fix it all you need to do is change 'hass/status' to 'homeassistant/status' which the script now listens for by default.
I did consider monitoring both the legacy topic and the new topic, and maybe I should do that, but I was afraid that might lead to people opening cases on other topics because their config wouldn't work (this project was one of the few that was encouraging people to implement birth messages).  Note that this change actually happened back in the 3.x versions (about 6 weeks ago), and is clearly documented on the ring-mqtt site with a dedicated section suggesting that everyone modify their configs to match this new default.
I know it's not easy to keep up with all of this stuff, but the good thing is, it's standard now, so shouldn't change in the future.

BTW, the likely reason your other MQTT devices show up is because a lot of other tools send device discovery messages with retain which allows Home Assistant to "rediscover" these devices automatically, even if the MQTT component isn't available.  I elected a long time ago not to do this as it leads to other behaviors which I just don't like, primarily with stale devices that require manual user steps to remove from MQTT and devices that appear in Home Assistant as online even if the MQTT component servicing them is not running, etc.  Also, many other tools don't even bother to send real availability state about devices, but I wanted users to know clearly if state data was stale, devices were offline, the script stopped, etc. so I implemented robust state and and support for birth messages from the very start of this project, and resisted the urge to simply hide these behaviors by using retain.
For example, I can block one of my Wifi switches from the network and restart Home Assistant and HA will still happily show the device online in whatever state it was in last.  I just don't like this behavior at all.

@tsightler thanks much for the troubleshooting, I made the MQTT configuration change and that fixed the above issue. Appreciate you pointing out the issue. I try not to 'fix' what isn't broken and must've missed that update. Hopefully this will help anyone else that may have run across the same problem.


The time picker is unpleasant to use

To fill out both fields you need to click through both fields.
Proposal:

[ ] Default the picker to 23:59 (seems like the most reasonable deadline time)
[ ] Switch the focus to the second field when the first field has received a valid value

The second point would require modification to the TextField component itself since it needs reference to the HTML element to access events (such as blur) and methods (such as focus()), which seems like too much work to do given that the outcome is just saving one "tab" button press.


popups of some xwayland apps do not pop up anymore

Regression?
Yes
System Info and Version
 System/Version info
Hyprland, built from branch main at commit fabc30df52ab5d2c369fc8acd4ff909a6ba3b8ac

Description
Popup menus stopped showing in OrcaSlicer and BambuStudio since commit 2566d818848b58b114071f199ffe944609376270
Here I click on the 'seam position' setting:
Kooha-2024-06-21-10-59-32.webm
How to reproduce
Start OrcaSlicer and click on a setting with a popup.
Crash reports, logs, images, videos
Log when clicking the setting:
popup.log

...wayland apps? The commit relates to xwayland.

...wayland apps? The commit relates to xwayland.

Yes xwayland. I must have mistyped.

any updates on this? Really frustrating, and window rules are unable to fix that either. Making the menus unfocusable and forcing the parent window to keep the focus doesn't work at all, as if the window rules didn't exist.

any updates on this? Really frustrating, and window rules are unable to fix that either. Making the menus unfocusable and forcing the parent window to keep the focus doesn't work at all, as if the window rules didn't exist.

it's a regression from https://github.com/hyprwm/Hyprland/commit/2566d818848b58b114071f199ffe944609376270, you can just revert it and build hyprland

I'm hoping to see a fix for this somewhat soon, at least a toggle to undo that commit at runtime...
I currently have to juggle between both the latest and that commit to get Bambu Studio and Bitwig working. Very frustrating since I either cannot slice anything or xwayland crashes when using bitwig...

isnt this fixed? as a dupe of #6698

I still get the same issue as of version V.0.41.2
❯ hyprctl version
Hyprland, built from branch main at commit 918d8340afd652b011b937d29d5eea0be08467f5  (flake.lock: update).
Date: 2024-06-25
Tag: v0.41.2, commits: 918d8340afd652b011b937d29d5eea0be08467f5


Fix local eval

What does this PR do?
Fixes local eval by saving to different paths by rank.
What issue(s) does this change relate to?
Issues from Dan running local human eval.

added the world size 2 test


[wallet] Backup/import mnemonic has to also store/ask the language

Expected Behavior
For backups/imports, it has to ask/store the language of the mnemonic. This is required to validate that the words are from a valid bip39 dictionary
To take in count:
A user could have a mnemonic in english and have the app in spanish, so it shouldn't be tied to the app.
Current Behavior
Works for the default language (english)

Fixed by https://github.com/celo-org/celo-monorepo/pull/5825


apko build and publish tls: failed to verify certificate

Currently the apko cli does not have any options to provide certificates when pulling from a self-hosted apk registry when building an image (apko build) or when pushing to a self-hosted registry instance (apko publish).
resulting in the following error:
failed to fetch apk key: Get "<self-hosted-registry-artefact>": Head "<self-hosted-registry-artefact>": tls: failed to verify certificate: x509: certificate signed by unknown authority
Are these options able to be added to the cli?

This is technically feasible, and if it would help folks to add them then it seems worth adding.
However, this isn't a feature of apko we'd use ourselves, so we're probably unlikely to prioritize adding it at this time. If you feel compelled to send a PR I can review it and get it in, but other than that I can't make many promises, sorry.
If there's a common pattern for passing custom certs, it would be good to follow that pattern if you're interested in adding that to apko.

@Conor-Behard333 are you on Linux? Because all go binaries (of which apko is one) support these environment variables
// SystemCertPool returns a copy of the system cert pool.
//
// On Unix systems other than macOS the environment variables SSL_CERT_FILE and
// SSL_CERT_DIR can be used to override the system default locations for the SSL
// certificate file and SSL certificate files directory, respectively. The
// latter can be a colon-separated list.
//
// Any mutations to the returned pool are not written to disk and do not affect
// any other pool returned by SystemCertPool.
//
// New changes in the system cert pool might not be reflected in subsequent calls.

Alternatively, you can enroll the certificate into the system CA store and it should also work.
Please let me know if above environment variables work for you.

Yes it was in a linux container and setting the SSL_CERT_DIR/SSL_CERT_FILE variable worked, thank you!
Normally we would just add the certs to the trust store, but its is a hardened image where the user doesn't have the perms to add and update the cert store.

Yes it was in a linux container and setting the SSL_CERT_DIR/SSL_CERT_FILE variable worked, thank you!
Normally we would just add the certs to the trust store, but its is a hardened image where the user doesn't have the perms to add and update the cert store.

I recommend https://images.chainguard.dev/directory/image/apko/versions ;-) which has zero-CVEs and is a hardened image. But it is very self-referencing. We do preset SSL_CERT_FILE variable there too, to both document the location of the certs and which ones are being used by default.


Add organizations listed on GitHub with their location set to 'Toronto'

There are 1000+ organizations on GitHub located in Toronto.. Some 113 of them have more than 25 repositories.
I want to be able to add these automatically. Adding .yaml files by end is exhausting, as is manually adding a ton of websites and data to the README by hand. Right now, my plan is to use GraphQL to get the data I want, and then to shim it into Markdown and ignore the YAML unless I can find an easy way to generate those, too.
Updates will be included in this thread.

hmm, considering GraphQL works as expected and you have some sort of control over items you're looping over, generating markdown files based on each item should be fairly simple.

generate base markdown with hugo new organizations/<name>.md
inject content inside, mostly with sed -i 's/.../.../g':

sed -i 's/description: ""/description: "<whatever you fetch from graphql>"/g'
and so on for name, website, etc.

That would be simple. Not a bad idea.

I think, since @khos2ow implemented and his PR got merged, this issue can get closed, right?

@smusali technically no, my PR was implementing the functionality but this issue is to actually bring over the content (with that functionality).

@khos2ow Still interested in doing that work?

Sure, but I need to refresh my memory on this next week when I got back from vacation.


separate transfer and freeze logic

allow tranferring and freezing in the following format:
'none', 'yolo_darknet', 'yolo_conv', 'yolo_output_conv', 'all'
This makes the training much more versatile and allows for using a checkpoint to resume training while tranfering different subset of weights. This also allows to transfer most of the yolo_output_conv weights except the last convolution.

Would love to see this!


Request: Add on-demand compilation like PEG.js' buildParser API

My workflow with PEG.js is to only ever use .pegjs files and to include them in node via PEG.js' buildParser API. I find this less error-prone than using generated JavaScript files (no wasted time debugging things and then realizing you forgot to regenerate after changing the grammar).

While this might be helpful in development, it's pretty inefficient for production code (and won't work in the browser!). Also, for large projects, you probably have other stuff being compiled as well (LESS, Coffeescript, Jekyll, etc.). Overall, I'm not too keen on adding this feature.
While developing, I recommend using something like $ watch nearleyc grammar.ne -o grammar.js & instead (you might need to install watch). This automatically compiles the grammar every couple of seconds and has the added benefit of alerting you if there's an error in your parser as soon as you save from your editor!

Fair enough; thanks the quick response!


Support read-only mode

For only reading exist markdown file ,  Can read-only mode be supported ?  So the UI could be simplified for convenient reading.

Yes, it definitely needed.

Via command line switch? Settings? When is read-only mode activated?

Settings probably.
P.S. sorry for late delay.

I'm interested in this. I've come to Markdown-Edit whilst looking for a simple reader (I typically use VSCode to write markdown, although I'll give MDE a whirl next time). I haven't found a good reader available for Windows: unless i'm missing an obvious tool, it's an untapped market in that respect and I think the minimal interface of MDE is very well suited to a reader.
In terms of activation, I'd vote for a switch in the UI that toggles the source pane on and off, along with the other editing-only toolbar items, and a switch in settings that controls the default state at startup. An override using a command-line switch would allow the creation of shortcuts to select either mode at startup regardless of settings for those who want that.
An increasing number of things like readme files (especially for GitHub projects) are being provided as .md with no simple, clutter-free method of reading them offline, so I think marketing as a reader as well as an editor might get some interest.

F12 toggles the UI. Not read-only but when viewing just the HTML output no editing is possible. Does that help?
I've been working on a rewrite off and on for some time (see the next branch). I've been waiting for .NET Core 3, which promises to support WPF. That will allow distribution as a standalone executable and other improvements.

The F12 cycle (which I'd totally failed to spot) goes a long way to giving me what I'm after, especially as it remembers the state from the previous session.
[As an aside, there may be a bug here: with only the preview pane open from the previous session, the preview is blank, even if a file is open from the previous session or newly opened in the current one. Making the editor pane visible (even if only briefly) cures the problem. I'll search the issues and potentially start a new one for this.]

I suspect the preview does not render until the editor loads.


[Awaiting Payment 20th May] [Guided Setup Stage 1] Ask for business name before asking for display name

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.70-1
Reproducible in staging?: Y
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @trjExpensify
Slack conversation: https://expensify.slack.com/archives/C036QM0SLJK/p1714746065450189?thread_ts=1714400621.865599&cid=C036QM0SLJK
Action Performed:

Sign up with a new account
Click Manage my team's Expenses in the onboarding modal
Observe the next question you're asked is for your display name
Enter your display name
Observe the next question you're asked is for your business name

Expected Result:
When a new user selects the Manage my team's expenses onboarding intent:

The next question we ask should be for their Business name
Upon clicking the confirmation button on the business name page we should trigger the CreateWorkspace API command immediately

Actual Result:
We ask for business name last, so as a result, we trigger the CreateWorkspace command at the end of the onboarding flow.
Workaround:
N/A
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/16232057/8e019b05-7013-45dc-bb49-49e8480ce6cb

View all open jobs on GitHub
CC: @anmurali @francoisl @NikkiWines @mountiny @danielrvidal
Issue OwnerCurrent Issue Owner: @thesahindia

Yes, just that option. None of the other options ask for a business name. 👍

Yeah, I see the commit to not do that 😅

@trjExpensify The PR was deployed to production 2 weeks ago. Could you help to move forward with this issue

@ishpaul777, paid!

@DylanDylann paid! Closing!


don't start camel context before the container is fully started

The camle context is started on runtime init but before there
was no control about starting after the a full initialized ArC
container and this lead to unpredictable behaviors when the
registry looks up for bean from the container.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/141/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/144/


migrates to Laravel 7

Description
Migrates from Lumen to Laravel 7
Checklist

[ ] All tests passing
[ ] Extended the README / documentation, if necessary

:rocket: PR was released in v0.0.0 :rocket:


[Crashlytics] Xcode16 beta build with debug mode missing dSYM

Description
When building application with Debug mode on Xcode16, dSYM fails to upload to Crashlytics.
This is related to https://github.com/firebase/firebase-ios-sdk/issues/13202
Workaround is to disable Debug Dylib Support in target Build settings. But this causes SwiftUI previews to not work.
Reproducing the issue

Set ENABLE_DEBUG_DYLIB=YES for build options
Build application for debug mode in Xcode 16

Firebase SDK Version
11.1.0
Xcode Version
16.0 Beta 6
Installation Method
Swift Package Manager
Firebase Product(s)
Crashlytics
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

I solved this by setting ENABLE_DEBUG_DYLIB to false. Crashlytics upload dsym successfully but it makes preview go kaput

Seems like Apple changed their dSYM content a bit again, will work on a fix. Meanwhile another work around is uploading the dSYM through web uploader.

Is there any update on this?

I would like to know if there is any update to this as well. ENABLE_DEBUG_DYLIB to false is the only solution for me for Crashlytics to work.

As above, ENABLE_DEBUG_DYLIB is the only solution for me too. Manually uploading dylibs is not particularly feasible when rapid prototyping and using CI/CD.
Would be good to know if there's a fix on the way!

Hey folks,
Thank you for reaching out, I am working on the fix now. This fix need a refactor work in script so we need to do a thoroughly regression test which might take more time. Tl;dr the fix need to make upload-symbols to support upload multiple DWARF contents within the same dSYM bundle which currently upload-symbols does not support. We likely gonna miss the code freeze for the upcoming release version. But as soon as we finished testing and I'll post the artifact in the issue as a workaround before we having official release.

Set ENABLE_DEBUG_DYLIB=YES for build options
Build application for debug mode in Xcode 16

This seems to do the trick for me too.

Xcode Version 16.0 (16A242d)

Processing of new dSYMs seem to take rather long on Google's side - after upload complete, it takes 5-10minutes before the events start to appear. Is this normal?
This makes fast iteration and testing really hard and prone to make wrong conclusions what works and what not.

Thank you @themiswang ,
Do you have any ETA for the release that will have this fix?

I'm still facing the issue after updating to 11.3.0

Hey folks,
I have merged the change for upload-symbols in this PR(https://github.com/firebase/firebase-ios-sdk/pull/13760), we are expected this change will be in the next Firebase release for version 11.4.0 and release date will be on Oct 21, 2024. We would love to get your early feedback, so we're sharing the pre-release artifact upload-symbols.zip early for anyone who would like to try it out.
If you are using CocoaPods, you can override the upload-symbols executable to the new one under $PODS_ROOT/FirebaseCrashlytics/upload-symbols
For SPM, you can put upload-symbols and run.sh in a convenient place and then change the path to the new place for your upload symbols build phase.

Thanks @themiswang for fixing and keeping us updated 👍🏻

I get it while validating the release build from Xcode 16.
How to get rid of these warnings ?

Hey @NigamAnkit, @lirbar,
The warning actually related to #13551, it is a different issue which relate to how package is getting build. I would suggest follow up with that issue, thank you!

I get it while validating the release build from Xcode 16. How to get rid of these warnings ?

Does your Firebase Analytics dashboard contain user data?

Hello everyone,
I encountered the same issue and needed to urgently release an update to the App Store due to a change in my application's API endpoint. To address this temporarily, I found the following solution:
I downgraded Xcode to version 15.4, which allowed my project to successfully build without validation errors, and I was able to release my update.
How can I run older Xcode version on new macOS version? for more details.
This may not be a permanent solution, but it could be helpful if you need to quickly push an update.

Any ETA for fix ??

Is someone else still facing the issue after 11.4.0 too?

@paulb777, @themiswang, I've updated to 11.4.0 but dSYM still fails to upload to Crashlytics. And I still see this warning in Xcode's console:

I'm still using the recommended configurations as per your Crashlytics documentation. Does 11.4.0 require changes? If yes, which ones?
Also, ever since I integrated Firebase SDK to use Analytics and Crashlytics, all previews stopped working due to AppLaunchTimeoutError. I'm on Xcode 16. I will try to remove Firebase SDK to verify.

Hey,
I updated to 11.4.0 and I have this error which: /Users/....xcodeproj Missing package product 'FirebaseRemoteConfigSwift'
Any idea?
thx

FirebaseRemoteConfigSwift should be removed. It was merged into FirebaseRemoteConfig.

I updated to 11.4.0, I have ENABLE_DEBUG_DYLIB set to true and every time I run the app on the simulator my team gets an email warning them. I had to disable the script on development as someone else suggested.

I get it while validating the release build from Xcode 16. How to get rid of these warnings ?

Any ETA on this that may help!? I'm having the same issue right now.

Any update on this?  I am still having this issue.

Is this going to cause an App Review rejection? What happens if we ignore this warning?
The issue still exists in 11.4 as others pointed out.

Is this going to cause an App Review rejection? What happens if we ignore this warning? The issue still exists in 11.4 as others pointed out.

If it helps to you, I already Validated and Distributed my app to Appstore. So far they haven't say anything about it. I don't think that warnings may cause your app to be rejected. (Warnings, not Errors)

Is this going to cause an App Review rejection? What happens if we ignore this warning? The issue still exists in 11.4 as others pointed out.

I was able to submit an app that had the warning and my submission was approved, FYI.

The submission is getting approved but the warnings are still coming even after updating to 11.4.0.
@paulb777 Any update/ETA on this?

I submitted a version of our app with these warnings and now Google Analytics is showing no data. All of our users who updated to the new version are now not showing. Does the workaround fix this issue??


Unable to run a fresh install

On a fresh install of this repo, I got this when running the local dev setup

any ideas?

Nevermind! It works now lol


iPad fullscreen mode

It would be nice if it was possible to switch between fullscreen and popover view modes on iPad.

Would like to have take photo in fullscreen

I just read about this at https://stackoverflow.com/questions/13244366/display-full-camera-in-ipad


Implement SelectCredentials(vcJWTs, presentationDefinition)

loosely based on https://github.com/TBD54566975/web5-dart/issues/52

a reminder to myself to NOT merge this until web5-spec PR is merged


What must be implemented to have a "valid" OpenNI driver

First off, apologies if this is an inappropriate post for this venue, but I'm not sure where else to ask at this point:
I've written a driver for a soon-to-be released depth sensor and I can run all the samples (SimpleRead, NiViewer, etc), but when I try and run an application that claims to support OpenNI (NiTE, for example), I'm unable to use my driver.  Are there specific resolutions, streams, framerates, properties, etc that MUST be implemented for OpenNI dependent applications to consider a driver as valid?

As what I know:
The FoV( ONI_STREAM_PROPERTY_VERTICAL_FOV  and  ONI_STREAM_PROPERTY_HORIZONTAL_FOV) are required for coordinate convert (between depth and world).
PrimeSense NiTE requires special resolution (VGA or QVGA), and special properties.
According to the license of NiTE, you can NOT use NiTE with non-PrimeSense products.
https://github.com/VIML/VirtualDeviceForOpenNI2/wiki/About-PrimeSense-NiTE

Thanks for the info!  I figured it would be as simple as just making sure the depth stream works but I see there's definitely more to it.  Good to know about authorized vs non-authorized hardware as well, I guess NiTE may not be the option I was looking for.  Thanks again!


Bug: Issue with JSON input into LLM Scorer

Hello,
thanks for creating this awesome service 🙏
I'm trying to evaluate some generated content inside a JSON blob using the LLM Scorer but it looks like something is stopping it from working.
Am I doing something wrong or is there some bug here?
Thanks!
/Erik

Good catch. I'll fix it right now.

It is fixed.


Training Issues

run   python3 tools/train.py -f exps/example/mot/yolox_x_mot17_half.py -d 1 -b 1 --fp16 -o -c pretrained/yolox_x.pth
ERROR    | yolox.core.launch:90 - An error has been caught in function 'launch', process 'MainProcess' (16529), thread 'MainThread'<PHONE_NUMBER>01728):
Traceback (most recent call last):
File "tools/train.py", line 122, in
args=(exp, args),
│    └ Namespace(batch_size=1, ckpt='pretrained/yolox_x.pth', devices=1, dist_backend='nccl', dist_url=None, exp_file='exps/example/...

File "/home/pc116/Documents/gxy/ByteTrack-main/yolox/core/launch.py", line 90, in launch
main_func(*args)
│          └
└ <function main at 0x7f8f41687620>

File "tools/train.py", line 100, in main
trainer.train()
│       └ <function Trainer.train at 0x7f8e8b7da9d8>
└ <yolox.core.trainer.Trainer object at 0x7f8f41681b00>
File "/home/pc116/Documents/gxy/ByteTrack-main/yolox/core/trainer.py", line 70, in train
self.before_train()
│    └ <function Trainer.before_train at 0x7f8f41667ae8>
└ <yolox.core.trainer.Trainer object at 0x7f8f41681b00>
File "/home/pc116/Documents/gxy/ByteTrack-main/yolox/core/trainer.py", line 146, in before_train
no_aug=self.no_aug,
│    └ False
└ <yolox.core.trainer.Trainer object at 0x7f8f41681b00>
File "exps/example/mot/yolox_x_mot17_half.py", line 54, in get_data_loader
total_ids = dataset.nID         # TODO: total ids for reid classifier
└ <yolox.data.datasets.mot.MOTDataset object at 0x7f8f16dbc860>
File "/home/pc116/anaconda3/envs/gxy/lib/python3.6/site-packages/torch/utils/data/dataset.py", line 83, in getattr
raise AttributeError
AttributeError

total_ids issue. see other issues or setup again.
---Original---
From: @.>
Date: Wed, Apr 13, 2022 12:55 PM
To: @.>;
Cc: @.***>;
Subject: [HanGuangXin/ByteTrack_ReID] Training Issues  (Issue #13)
run   python3 tools/train.py -f exps/example/mot/yolox_x_mot17_half.py -d 1 -b 1 --fp16 -o -c pretrained/yolox_x.pth
ERROR    | yolox.core.launch:90 - An error has been caught in function 'launch', process 'MainProcess' (16529), thread 'MainThread'<PHONE_NUMBER>01728):
Traceback (most recent call last):
File "tools/train.py", line 122, in
args=(exp, args),
│    └ Namespace(batch_size=1, ckpt='pretrained/yolox_x.pth', devices=1, dist_backend='nccl', dist_url=None, exp_file='exps/example/...
File "/home/pc116/Documents/gxy/ByteTrack-main/yolox/core/launch.py", line 90, in launch
main_func(*args)
│          └
└ <function main at 0x7f8f41687620>
File "tools/train.py", line 100, in main
trainer.train()
│       └ <function Trainer.train at 0x7f8e8b7da9d8>
└ <yolox.core.trainer.Trainer object at 0x7f8f41681b00>
File "/home/pc116/Documents/gxy/ByteTrack-main/yolox/core/trainer.py", line 70, in train
self.before_train()
│    └ <function Trainer.before_train at 0x7f8f41667ae8>
└ <yolox.core.trainer.Trainer object at 0x7f8f41681b00>
File "/home/pc116/Documents/gxy/ByteTrack-main/yolox/core/trainer.py", line 146, in before_train
no_aug=self.no_aug,
│    └ False
└ <yolox.core.trainer.Trainer object at 0x7f8f41681b00>
File "exps/example/mot/yolox_x_mot17_half.py", line 54, in get_data_loader
total_ids = dataset.nID         # TODO: total ids for reid classifier
└ <yolox.data.datasets.mot.MOTDataset object at 0x7f8f16dbc860>
File "/home/pc116/anaconda3/envs/gxy/lib/python3.6/site-packages/torch/utils/data/dataset.py", line 83, in getattr
raise AttributeError
AttributeError
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I am closing this issue, re-open it if you had other questions.


Invalid JSON error whenever I make a GET request to micro w/o a body

parseJSON is called and throws an exception when there's no body in the request. Is this expected?
> #35 GET /customer/180d6a05-f21d-48fe-8105-ec50fc676712/cards                                             12:05:41

info: [2654ab10-cb2d-11e8-b146-77a2770b5d16] - Received listCardsForUser request
< #35 400 [+3ms]                                                                                12:05:41

  Error: Invalid JSON

  - index.js:20 createError
    [checkout]/[micro]/lib/index.js:20:14

  - index.js:120 parseJSON
    [checkout]/[micro]/lib/index.js:120:9

  - index.js:158 exports.text.then.body
    [checkout]/[micro]/lib/index.js:158:39

  - next_tick.js:229 process._tickDomainCallback
    internal/process/next_tick.js:229:7

It's expected as per the API docs: https://github.com/zeit/micro#jsonreq--limit--1mb-encoding--utf8-


Rock5B Support

I have one and am happy to help test, I think it should be pretty similar (identical?) to the Rock5A with Collabora sources

Related to #4
There are already other projects that support rock5b, I think you can just try it:
https://github.com/aciceri/rock5b-nixos

I wonder if nanopi R6S is worth supporting

@grsmith-projects You may want to take a look at this: https://nixos.wiki/wiki/NixOS_on_ARM/NanoPi-R6C
which recommends using UEFI firmware edk2 to start NixOS, and it supports R6S/Rock5B too.

I haven't tried yet, but it does not require any customization of NixOS, it can be started directly using NixOS's official ISO for aarch64, which sounds very attractive.
https://github.com/edk2-porting/edk2-rk3588

FYI, I've just added UEFI support for rk3588, it makes it much easier to add any new SBC, so I plan to add support for more RK3588/RK3588s based SBCs next, including Rock 5B.


[Core Rulebook] Sigmar's Fiery Hammer

When the effect is in place on the character sheet the Magical effect of the Enchantment it sets the weapon damage to +0 in the combat tab. From: tenshi1865<EMAIL_ADDRESS>12.331wfrp4e: 8.3.2wfrp4e-altdorf: 6.0.1wfrp4e-core: 6.0.2wfrp4e-dotr: 6.0.2wfrp4e-eis: 6.0.2wfrp4e-empire-ruins: 6.0.2wfrp4e-horned-rat: 6.0.1wfrp4e-middenheim: 6.0.2wfrp4e-pbtt: 6.0.1wfrp4e-ua1: 6.0.2wfrp4e-up-in-arms: 6.0.2wfrp4e-wom: 6.0.3wfrp4e-zoo: 6.0.0Active Modules: color-picker, dice-so-nice, entice-with-dice-so-nice, foundryvtt-simple-calendar, item-piles, lib-wrapper, popout, popout-resizer, quick-insert, Rideable, routinglib, socketlib, times-up, token-action-hud-core, token-action-hud-wfrp4e, token-attacher, token-hud-art-button, token-z, warhammer-lib, wfrp4e-character-details

This has already been fixed, please ensure you have reimported the miracle from the compendium and not using an old version.


[SPARK-39775][CORE][AVRO] Disable validate default values when parsing Avro schemas

What changes were proposed in this pull request?
This PR disables validate default values when parsing Avro schemas.
Why are the changes needed?
Spark will throw exception if upgrade to Spark 3.2. We have fixed the Hive serde tables before: SPARK-34512.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit test.

+CC @xkrogen , @shardulm94

Why did https://issues.apache.org/jira/browse/SPARK-34512 not fix the problem? Was it done for Hive tables only?
cc @gengliangwang

Yes. SPARK-34512 only fixed the Hive serde table.

Nit: shall we have an end-to-end test with file writing/reading using the option avroSchema as well?

@wangyum does the below tests pass(using avroSchemaUrl as option) with these changes  ?
  test("SPARK-XXXX: support avro schema and schema url with invalid defaults") {     val avroSchemaUrl = testFile("test_default_null.avsc")     val result = spark.read.option("avroSchemaUrl", avroSchemaUrl)             .format("avro")             .load(testAvro)             .collect()     result.foreach(println(_))   }
where test_default_null file content is as below
{   "type" : "record",   "name" : "test_schema",   "fields" : [{     "name" : "string",     "type" : "string",     "doc"  : "Meaningless string of characters",     "default" : null   }] }

test_default_null.avsc

I ran this test by using this branch and it failed as below which is coming from the avro code here.
Job aborted due to stage failure: Task 1 in stage 0.0 failed 1 times, most recent failure: Lost task 1.0 in stage 0.0 (TID 1) (<IP_ADDRESS> executor driver): org.apache.avro.AvroTypeException: Invalid default for field string: null not a "string"
	at org.apache.avro.Schema.validateDefault(Schema.java:1581)
	at org.apache.avro.Schema.access$500(Schema.java:92)
	at org.apache.avro.Schema$Field.<init>(Schema.java:552)
	at org.apache.avro.Schema.parse(Schema.java:1688)
	at org.apache.avro.Schema$Parser.parse(Schema.java:1433)
	at org.apache.avro.Schema$Parser.parse(Schema.java:1421)
	at org.apache.avro.Schema$SerializableSchema.readResolve(Schema.java:109)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1274)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2157)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1647)

And as per AVRO-2035 it is a correctness bug, so if we are fixing this issue isn't it be a great to make it configurable and let user decide what to do with the  incorrect schema. ?. May be can we add  AvroOption as validDefaults spark.read.option("validDefaults", false).format("avro") ?

And as per AVRO-2035 it is a correctness bug, so if we are fixing this issue isn't it be a great to make it configurable and let user decide what to do with the incorrect schema. ?. May be can we add AvroOption as validateDefaults spark.read.option("validateDefaults", false).format("avro") ?

Hi, @sandeep-katta0102 . Could you elaborate what makes you think that is a correctness bug? It looks like causing a runtime exception instead of data corruption.

And as per AVRO-2035 it is a correctness bug, so if we are fixing this issue isn't it be a great to make it configurable and let user decide what to do with the incorrect schema. ?. May be can we add AvroOption as validateDefaults spark.read.option("validateDefaults", false).format("avro") ?

Hi, @sandeep-katta0102 . Could you elaborate what makes you think that is a correctness bug? It looks like causing a runtime exception instead of data corruption.

As per the jira description from AVRO-2035 it says "if this default value is ever accessed (when reading a gen1-serialized object as a gen2) we get this: org.apache.avro.AvroTypeException: Non-boolean default for boolean: "true" " . I am not sure whether this use case is valid for spark or not, if it is not valid then this comment can be ignored

That's what I mean by a runtime exception. Users cannot get a wrong result at all because they get errors before that. So, this is not a correctness issue, @sandeep-katta0102 .

Thank you @dongjoon-hyun for correcting me, I understood

Hi @wangyum. Would you be able to address the comments? It would be great to fix the issue.

Thanks for the updates. cc @martin-g @dongjoon-hyun for another round of reviews.

thanks, merging to master/3.3/3.2!

+1, LGTM, too. Thank you all.


module_name in info.yaml is incorrect

needs to be the name of the module - wrapped_qarma

Fixed in 742413b


Concurrent read error propagation fix

Resolves #451 server crash
Unhandled Exception: System.InvalidOperationException: Concurrent reads are not supported.
   at Microsoft.AspNet.Server.Kestrel.Http.SocketInput.OnCompleted(Action continuation)
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.AwaitUnsafeOnCompleted[TAwaiter,TStateMachine](TAwaiter& awaiter, TStateMachine& stateMachine)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_1(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

/cc @halter73 @lodejard

Should we put in the concurrent queue instead of a short term fix?

@lodejard Then I'd never find where it happened, am not intentionally double reading :(
Occurred 3 times in 30 mins across about 100M+ WebSocket messages with coreclr x64; over https using Kestrel.Https filter- I'd have perferred if it errorred and told me where it was happening - so I could fix either kestrel, filter, websocket middleware; ssl stream or my app :)
Still can't track it down or reproduce in load testing :(

Though obviously the server crashing is a worse situation... :P

Added change to error both reads

@benaadams Has this fix helped you pinpoint the source of the concurrent reads?

@halter73 not yet, as I can't get a concurrent read to trigger - working on it. It happened during weekend playtest where webserver was open to the public to try; so I've got to get a bit messier.
I'm going to trigger a concurrent read purposefully and make sure the outcome is well behaved (disconnect would be well behaved - as far as I'm concerned); and handled (reconnect, re-establish control to spaceship) - and I might have to wait till the next public pre-alpha test to catch it in the act.
Though will be running some extensive testing meanwhile as the websockets weren't 100% well behaved so want to track those issues down too.

Cool. It's awesome to have real-world testing going on with so many messages being sent.
I think we should get a unit test in for this before merging this PR.

Ok, will make sure I can trigger it :D

Cool. It's awesome to have real-world testing going on with so many messages being sent.

On the positive flip-side...
When we go live we are going to be running on Service Fabric, so it will be migrating the servers/microservices around and the effect will essentially be crashing the connections as they hop from host to host - so I did get to test our client reconnection logic.
By the 3rd crash I was on the ball; restarted pretty quick and no-one really noticed it. I haven't been brave enough to restart the server mid-test in any test so far to check if it really works! So from that side of things am pretty pleased :+1:

Found the error while setting up tests if you do something like this it counts as a double await:
await AwaitAsTaskAsync(SocketInput socketInput).ContinueWith(
    (t) =>
    {
        taskThrew = true;
    },
    TaskContinuationOptions.OnlyOnFaulted);

private async Task AwaitAsTaskAsync(SocketInput socketInput)
{
    await socketInput;
}

Added test

Nice! I was about to write the test myself (which is probably fair since I added the throw). I just ran your test with the existing code and it crashed the test runner. Good sign :smile:


[SG200X] div_clk_187p5m, clk_187p5m registers missing, UART_SCLK configuration confusing

There is a chapter about UART configuration in UART section page 555. UART_SCLK  configuration mention div_clk_187p5m register, which is missing in datasheet:

also there is mention about clk_187p5m register which description also missing:

Would be great to have an example for uart sclk configuration

@KennethLiu61 hi, can you please double check this?

Sorry, there is an error in the document. This divider register should be div_clk_cam0_200.


RD2: Data migration - void open Opps

Remove the extra forecasted Opportunities during data migration in order to save on storage and see less visual clutter on Donor records.
Critical Changes
Changes
Issues Closed
New Metadata
Custom Labels:

RD2_DataMigrationInvalidCloseAction

Deleted Metadata

**lurch: attach W-036853

@force2b , it might be better to review PR after PR #4831  is merged since I needed to merge its changes before extending the data migration functionality.

Tracking W-036853

@force2b , the PR is ready for the review.

@Julian88Tex , data migration of open Opps on RDs is ready for testing.

Manual tests have passed. Just waiting for builds to complete.


Requests dependency during API installation

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description
Requests is required during installing the Python API. While the error show during installation is obvious, for novices this could provide some additional headaches when installing the API.
Steps to Reproduce

Clean Python installation
Follow the steps to install the API
Get an error when running the python_get_api related to requests

Expected Result
Include requests when installing the dependencies via pip
Actual Result

ZED Camera model
ZED2i
Environment
win_amd64
Python 3.11
ZED SDK 4.0

Anything else?
If you like, I can make a fork and PR to resolve this "issue".

Can confirm I have this issue too.


Inquiry Regarding Applicability of PECAT to Polyploid Genomes

Hello!
Hope this message finds you well.
I want to extend my sincerest thank for developing PECAT, which has been an invaluable tool in my work.
Besides, I am very curious about the possibilities of employing PECAT in analyzing complex system (e.g., several haploid or a polyploid genomes). Could you please advise if it is feasible to use PECAT for such applications (during process of CORRECTING and ASSEMBLY)? If it is fundamentally feasible, are there any specific parameters that need to be adjusted or considerations to be mindful of when dealing with polyploid genomes?
Understand that dealing with polyploidy presents its unique set of challenges, so any insights or guidance you can provide on this matter would be greatly appreciated.
Thank you so much for your time and consideration. Looking forward to hearing from you.
Warm regards,
Yanren

Hi, @wyanren
I‘m glad that you are using PECAT. Most steps of PECAT do not assume that the data is diploid. Unfortunately, some steps do. You can try using the parameters for assembling diploid genomes. However, it is difficult to estimate the effect of assembling polyploids genomes. I think that PECAT should have the potential to assemble polyploids with some modifications. Currently we do not have any test results in this regard.

Hi, thank you so much for your prompt response. I will try to modify parameter in the scripts.
Having reviewed the literature of PECAT in BioRxiv, I find myself wondering whether the algorithm (POA graph) using in the correcting process is capable of distinguishing between random sequencing errors and heterozygosity in polyploids.

PECAT doesn't assume that the data was diploid during the error correction. It can distinguish between sequencing errors and heterozygous in polyploids. But the heterozygosity rate should not be too low and there should be sufficient reads.


[FLINK-17604] Implement format factory for CSV serialization and

deseriazation schema of RowData type
What is the purpose of the change
Implements format factory for CSV RowData Se/De schema so that they can use in SQL.
Brief change log

A new CsvFormatFactory, the options are in style of what FLIP-122 has concluded.

Verifying this change
Added UTs.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): yes
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? not documented

The failed tests are not related to this one. Will merge it.

The failed python tests is caused by FLINK-17596.


cache DNA image for speed

When showing DNA for a full origami (~14,000 bases), rendering while panning and zooming is quite slow when most of the DNA is visible. The SVG rendering engine is smart enough not to render objects that are not in the viewport, however, so it is fast when zoomed in. Since the detail of SVG (compared to a pixelated PNG) is only needed on zoom in, cache a low-resolution PNG image to display instead when the zoom is sufficiently far out.

https://github.com/UC-Davis-molecular-computing/scadnano/commit/d8d0151018d7df0b53af073553708f4a27ece4da

Great!
However, it seems to pan and zoom quite sluggishly (on both Chrome and Firefox) even when the "show DNA" checkbox is unchecked.
I haven't dug into the implementation yet, but hopefully this can be implemented in a way that requires no extra processing, compared to before, when "show DNA" is unchecked. Do you notice this too? For instance, when I zoom out, instead of being smooth, it waits a few seconds and then suddenly shows the zoomed out image.
Also, the slowdown persists; it doesn't appear to be associated with the single "create the cached image" event. I would expect there to be a slowdown when the cached image is first created, but after that it should be at least equally as fast to render.
If it's not clear where the slowdown is coming from, try the "Performance" tab of developer tools.

 I filed it: #212


:robot: Fix some tests rebuilding the iso

We missed fixing the earthlyignore to include the iso files on tets, so some of the tests were fully rebuilding the iso after downloading it

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Codecov Report

Merging #980 (a6e8be1) into master (cb2e7c0) will not change coverage.
The diff coverage is n/a.

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

: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           @@
##           master     #980   +/-   ##
=======================================
  Coverage   22.79%   22.79%
=======================================
  Files          22       22
  Lines        1610     1610
=======================================
  Hits          367      367
  Misses       1179     1179
  Partials       64       64

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


Silence clippy::needless_update for fully specified MroUsing.

Any stage that specifies all four MroUsing parameters will trigger clippy::needless_update since the final ..Default::default() will set no fields. Silence it locally.

thanks @macklin-10x !


mgmt, local generation for eventgrid

Description
Had to modify local swagger to work(put TopicEventSubscriptions above DomainTopicEventSubscriptions):
https://github.com/Azure/azure-rest-api-specs/commit/fe5abe68c15d6ab5b1289ebdfa311f98a5750e09
Otherwise, define method would move from TopicEventSubscriptions to DomainTopicEventSubscriptions:
https://github.com/Azure/azure-sdk-for-java/commit/f65b38732aa43c5360a764b88229010feae6dc9b
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-resourcemanager-eventgrid

We may need an option of e.g. --resource-collection-association=TopicEventSubscriptions:EventSubscriptions, to let ResourceParser prioritize TopicEventSubscriptions resource to be created via EventSubscriptions collection.

Issue logged: https://github.com/Azure/autorest.java/issues/2149