Another issue with No files shown in folders mounted from NAS

Hi All,
I'm a first timer working with the qnap docker crashplan scenario.  I'm not very apt at its CLI, I'm more of a gui guy but I'm learning.
I'm running the app as follows:
docker run -d
--name=crashplan-pro
-e USER_ID=0 -e GROUP_ID=0
-p 5800:5800
-v /DataVol1/Container/Crashplan-Pro:/config:rw
-v /DataVol1/Staff:/storage:ro
jlesage/crashplan-pro
It is my understanding that I am mapping my /DataVol1/Staff folder to be accessible to the container as  Storage.  It is this Staff folder/subfolders that I need to back up.  (There are other folders, but let's tackle this issue first).
The container starts and is accessible, however there are no files listed with:
docker exec crashplan-pro ls -l /storage
8 files are listed, as expected, with:
docker exec crashplan-pro ls -l /config
From what I've read here and on the qnap forums, it might be a permissions issue.  However, I'm using the built-in admin account:
id=0(admin) gid=0(administrators) groups=0(administrators),100(everyone)
Which does have the appropriate permissions as shown in this screen shot:

Trying to enumerate permission via CLI doesn't seem to work either:
[~] # ls -l /DataVol1/Staff/* && ls -l /DataVol1/Staff//
/bin/ls: cannot access /DataVol1/Staff/*: No such file or directory
While I am replacing my Qnap TS-469 Pro with a TS-673 and moving off of CP Home to my existing CP Business account, I don't need to keep my backup so I am not adopting the existing device but rather creating a new device.  I don't care that it has to back up all files again as there isn't too much data and I don't need the history.
Everything has gone quite well and I'm pleased with the simplicity of it, however perhaps I'm overlooking something or don't have the proper parameters in place when running CrashPlan?  Please let me know what additional information I can provide.

From what I understand, QNAP shares can be accessed from multiple paths.
I think you should also be able to access your share via /share/CACHEDEV1_DATA/Staff.  Can you try to map this path instead?

Thank you for your assistance.  Using the CACHEDEV1_DATA paths seems to be working.  Here is my current running command:
docker run -d
--name=crashplan-pro
-e USER_ID=0 -e GROUP_ID=0
-p 5800:5800
-v /share/CACHEDEV1_DATA/Containers/crashplan/config:/config:rw
-v /share/CACHEDEV1_DATA/:/storage:ro
jlesage/crashplan-pro
There were a few hangups along the way, both on the Crashplan side (waiting for backup) and also with the Qnap file system becoming inaccessible (which resulted in multiple containers/volumes and prompted a Qnap reboot and Raid rebuild), but all seems to be working fine for the moment.  I will continue my observations while Crashplan is going through its initial seeding.

If it is like me, it is because in the UI you can choose the /share/CACHEDEV1_DATA/ and mount that as /storage

you have to choose a shared folder :(
If you mount /share/CACHEDEV1_DATA/ then Crashplan can backup all folders/shares etc.

I can tell you why I finally decided to figure out the right command line (as well as persistent, ex-container config storage).  For some reason whenever Container Station (the QNAP docker app) upgrades, my Crashplan container breaks, and I have to destroy and rebuild it.  If I use the CLI, I can put the command sequence and arguments in a script and a) make it easy to replay and b) guarantee that I haven't forgotten a switch or config if it's been a while since the last rebuild.

Right, in this case, it is much easier for me to copy/paste a command line instead of running through a GUI where I might forget an option.

Thanks for the explanation.  I guess I should add to the README the restrictions people need to follow when mapping folders (i.e. use /share/CACHEDEV1_DATA/ or something under it).

Having a similar issue. Wondering if there is an operating difference between these two mappings? Is one correct and are either valid?
-v /share/Backup:/storage:ro or -v /share/Backup/:/storage:ro
does the directory need the last slash to be in the docker run command?

Having a similar issue. Wondering if there is an operating difference between these two mappings? Is one correct and are either valid?
-v /share/Backup:/storage:ro OR -v /share/Backup/:/storage:ro
does the directory need the last slash to be in the docker run command?

It runs both ways for me.  Are you using a QNAP? If so, try using:
-v /share/CACHEDEV1_DATA :/storage:ro \
Then you should be able to browse to your shares via {device}\root\storage\

I've been testing this configuration for the past month, and occasionally see hiccups.  For example, when I stop the container and attempt to change its settings (auto-start, memory, cpu etc) I get the following error message:

Then there are two images, two volumes, and two containers

The new container does not start. The 'temporary' container is the original one and starts and appears to be fine.  However I don't like having the temporary label in production, so I end up removing the container and recreating it.  Any reason why I can't change any settings to it?

Sorry I can't really help you on this (I don't have a QNAP), but it seems to be a question that could be asked to QNAP support team and/or forum.


Nested Layer Order Not Respected

Hello All,
I'd like to start by saying, fantastic work on this art engine. I've been putting together a project and it's mostly going well. However there is one big problem. Nested layer order is not respected, i.e. In  a nested folder layers are not added in the right order.
Here's an example of the nested folder structure for cloths
Cloths
|--Cloth_01#15
|----1_Base
|------Base_01#10.png
|------Base_02#10.png
|----2_Secondary
|------Secondary_01#10.png
|----3_Tertiary
|------Tertiary_01#10.png
|----4_LineArt
|------Line_Art#100.png

and here is an example of the config
 {
    growEditionSizeTo: 10,
    layersOrder: [
      { name: "Base Body" },
      { name: "Cloths",
    },

For the output I would expect something like below (and that is why i have numbered the folders). Where the line art is the last layer
Base_01#10.png
Secondary_01#10.png
Tertiary_01#10.png
Line_Art#100.png

Some images will generate with the correct ordering however some will not and i'll get some other layer at the top (not the lineart) like below.
Base_01#10.png
Secondary_01#10.png
Line_Art#100.png

Tertiary_01#10.png

Any ideas on why this happens? Going by the docs, all the folders are named correctly.

I've made an adjustment to the sorting function to fix this issue , by sorting the sort.normal under sortLayers function
  stack.normal.sort();

  return sortByZ(stack.front).concat(stack.normal).concat(sortByZ(stack.end));

Thank you for the fix @mojalil 👍


Unable to take screenshot for single element

The problem
using scope to take screenshots in a single element but the error  Object literal may only specify known properties, and 'scope' does not exist in type 'SnapshotOptions' in the return
Environment

Node version:
@percy/cli version: "@percy/cli": "^1.8.0"
Version of Percy SDK you’re using: "@percy/playwright": "^1.0.4"
If needed, a build or snapshot ID:
OS version: MacOS
Type of shell command-line [interface]:

Details
https://docs.percy.io/docs/screenshot-a-single-element
Debug logs
Argument of type '{ scope: string; }' is not assignable to parameter of type 'SnapshotOptions'.
Object literal may only specify known properties, and 'scope' does not exist in type 'SnapshotOptions'

Code to reproduce the issue
import percySnapshot from "@percy/playwright";
....
await percySnapshot(page, "name", { scope: '.cookie-banner' })

Hey @luckhiem! Are you using TypeScript? This seems like it's a type error (just want to be 100% sure)


Out Of Memory Error

Hello guys,
I am using Jsoup to parse an HTML file (contain a table), which size is more than 600MB, I got the error :
java.lang.OutOfMemoryError: Java heap space
I augmented my Java heap size, and I also cut the file into 64MB files and tried again, but the same error.
How can I solve this please ? I need to do it, I am in hurry.
Thanks.

I'm running into the same issue.  The file is about 250MB.  I have allocated 2GB of memory and after 17 minutes fails with this error:
 [java] Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
 [java]     at java.lang.String.toLowerCase(String.java:2647)
 [java]     at java.lang.String.toLowerCase(String.java:2670)
 [java]     at org.jsoup.parser.Token$Tag.appendTagName(Token.java:151)
 [java]     at org.jsoup.parser.TokeniserState$10.read(TokeniserState.java:147)
 [java]     at org.jsoup.parser.Tokeniser.read(Tokeniser.java:50)
 [java]     at org.jsoup.parser.TreeBuilder.runParser(TreeBuilder.java:49)
 [java]     at org.jsoup.parser.TreeBuilder.parse(TreeBuilder.java:43)
 [java]     at org.jsoup.parser.Parser.parseInput(Parser.java:32)
 [java]     at org.jsoup.Jsoup.parse(Jsoup.java:45)

I use Jsoup in numerous projects.  What I am likely to do is run a stax parser to segment data, then feed the child elements into Jsoup.

I've implemented a stream reader in #905. So OOMs caused by the previous full input buffering (which as noted by @trejkaz would grow exponentially) should not happen any more. You still need a heap larger than the input file to get it into the DOM (because of the object overhead, and temporary objects created during parse), but substantially less now (say ~ + 25%).


Set up Tailwindcss

Description
In the process of setting up Tailwindcss, we also needed to set up:

Webpack
PostCSS

In order to use Webpack, created a Webpack playrunhook and added it to our build step.
Additional Tailwindcss support added:

Some extra configuration and styles in styles.css to show rough examples of how to start engaging Tailwindcss
@tailwindcss/forms plugin (an officially supported plugin), since UAT will obviously need good form support

Screenshot of /programs/new

Checklist

[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)
Fixes #228

One question I still have is:
Do we actually need "style-loaders" and "css-loaders" (see webpack.config.js and package.json) to get what we want?
I tried removing them and the pages appeared the same from what I could tell. But I was hard-pressed to find an example use of postcss without those. I'll manually test this again later with a closer eye, and if it really seems to work fine, I'll remove them.

Looks like you'll need to add webpack to the container - looks like ./node_modules doesn't contain it at runtime here.

Ah cool, feel free to ignore then
On Wed, Feb 24, 2021 at 11:26 AM Natalie Sidhom<EMAIL_ADDRESS>wrote:

@natsid commented on this pull request.
In .gitignore
https://github.com/seattle-uat/universal-application-tool/pull/214#discussion_r582238949
:

@@ -8,3 +8,4 @@ RUNNING_PID
.bsp/
.DS_Store
node_modules
+bundle.js

It's not actually being built into the root dir. It's being built into
public/javascripts/bundle.js (see the path field of webpack.config.js).
But for whatever reason, putting the full path here
("public/javascripts/bundle.js) didn't successfully ignore the file. I can
try a couple other styles of syntax, but just "bundle.js" does the trick
regardless of location.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/seattle-uat/universal-application-tool/pull/214#discussion_r582238949,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADTURZHWNMFT2PP24LQJTLTAVHERANCNFSM4YBPOG2A
.

--
[image: Google Logo]
Bion Johnson (he/him)
Senior Software Engineer & Google.org Software Engineering Lead
<EMAIL_ADDRESS>

Looks like you'll need to add webpack to the container - looks like ./node_modules doesn't contain it at runtime here.

I think I did the thing! I switched the Dockerfile to install npm (which has a dependency on nodejs) instead of just nodejs. And added an npm install command after sbt dist. However the last CI test run timed out... re-running.

niiiiiiiiice.  that works great.

Your lockfile is version 2 now - I think you still want that at v1.  You've run your local npm instead of the container's npm.  Maybe we should add bin/npm which is the same as bin/sbt but runs npm?

I notice it doesn't break the tests, but I'm suspicious (without proof) that it might be a problem later. I don't know that lockfiles are meant to be backwards incompatible indefinitely, and the little warning message that complains that it's "doing its best" doesn't inspire a ton of confidence with me...

We discussed offline how to not run npm locally and added bin/npm so that any npm commands can be run in isolation based on the container's version of npm. And also made sure all the other scripts install npm dependencies themselves.


Update static-web-apps-cleanup-resource, adding multiple resources guidance

Submitted via Learn Editor.

@PabloNunes
When you're ready to have your PR reviewed, select "Ready for review."

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@PabloNunes - This PR hasn't had any activity for more than a year. I'll close it now, but if you would like to reopen it to work on it, please email the techdocprs alias.


Add rect example

Earlier today I wanted to put a simple rectangle on a map to visualise a bbox, but only found examples that used super advanced functionality like custom polygon styles etc. There seemed to be none that explains this quite common usecase on a very basic level ("you need a Feature that has a Geometry which is in this case a Polygon which expects an array of linear rings which look like this"). So after finishing my tiny application, I thought I could generalise it a little and contribute it here.
Feel free to rename it/edit the description etc.
Possibly it would be nice to add a second Polygon that actually has multiple linear rings to illustrate "how to cut holes into a shape".

It might make sense to use geographic coordinates here. For the view's center, you could use fromLonLat([longitude, latitude]), and for the extent [...fromLonLat(lowerLeft), ...fromLonLat(upperRight)]. Or you could add useGeographic() at the top of the code, and use latitudes and longitudes everywhere.

@mike-000 That's true, I didn't know about that function yet. Still, I kind of like that the way I did it illustrates how a Polygon works technically.
@ahocevar In this case I had the coordinates in EPSG:3857 anyway, so for me this was perfect, but you're right, the average user is more likely to be dealing with EPSG:4326.
-> How about I expand the example to contain four rectangles? One the way it is right now, one with fromExtent, one with fromLonLat, and one with holes?

@christophfriedrich I'd really keep it as simple as possible. Really boil it down to the simplest possible code. As you noticed already, we have plenty of examples with quite some complexity, but lack simple ones.

Okay, you've got a point there. Taking simplicity as the maxim, I changed the example to use Mike's suggestion.
fromLonLat could be explained in its own example if there's none already. And I'd refrain from useGeographic() at the top as that bears the risk that people only copy the bottom part and then wonder why it's not working as they are expecting...


Validate package-lock.json integrity via pipeline

Addresses #80

Found the culprit: The dependency "adyen-cse-js" is loaded from the repository directly, not from npm. package-lock.json:
...
  "adyen-cse-js": {
      "version": "github:Adyen/adyen-cse-web#8d7c4e3b1e6b34afac035cdb3dd723bda96348c2",
      "from": "github:Adyen/adyen-cse-web#0_1_23",
      "dev": true
    },
...

lockfile-lint doesn't seem to like it when no resolved key is specified. I'll look into it

merged into #320


predicting stock price with previous values and current news

I would like to collaborate two models and predict stock price
1] Stock price prediction using LSTM (on previous stock price data)
2] Stock sentiment analysis using news headlines

Mention the link of the dataset you are going to use and also elaborate your approach in a little bit depth. @Bhagyashri2000

Mention the link of the dataset you are going to use and also elaborate your approach in a little bit depth. @Bhagyashri2000

How many more days do you gonna take @Bhagyashri2000 to complete this project?

I am sorry sir. I am in the middle of the project and my end sem is going on so I couldn't complete it.  Can I submit it till 14th Feb?

Can I work on this issue??

@Amit366 after 14th feb you can work on that till that find some new project to work on


Setup Instruction for Developement Env

Changes made in Readme file

hi @excid3, Have added instructions on how to setup project locally. request you to please Review.

hi @excid3 @mybuddyandrew, Have added instructions on how to setup project locally. request you to please Review.

Hi @AbhishekJadav1998!
I had a chance to review your changes and noticed a few things that could be improved.
Would it be possible to include some additional steps for forking this repository and related actions?
I think it'd be more beneficial to provide the versions of Ruby and Rails that this project is using. So we can get rid of any installation commands
Thanks!

hi @excid3 @mybuddyandrew, Have added instructions on how to setup project locally. request you to please Review.

Hi @AbhishekJadav1998! I had a chance to review your changes and noticed a few things that could be improved.
Would it be possible to include some additional steps for forking this repository and related actions?
I think it'd be more beneficial to provide the versions of Ruby and Rails that this project is using. So we can get rid of any installation commands
Thanks!

Hi @AhmadR-Coder-max
Github have awesome documentation on how forking works and how we can fork a repository. Hence added link.
Regarding providing ROR version, i think bundle install will handle versions automatically. anyway that command is prerequisite for setting up dev env

Hey @excid3 can you please review this PR. If any changes needed, please let me know.
Thanks.

@excid3 Can you please Review/Merge this?


Allow viewing all commits of an object/collection with their metadata

The use cases:

The user would like to see all kept versions of an object/collection in order to remove PII from all of them.
User would like to follow the changes of that collection independently of other changes to the repository.

Requested by DataGen

closing as dup of #2251 (progress will be tracked there!)


Chat - Unavailable workspace is displayed on chat header when go to chat while logged out

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: 9.0.22-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4874559&group_by=cases:section_id&group_id=229066&group_order=asc
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:

Copy the link of a conversation
Log out of the app
Navigate to the conversation URL
Log in
Verify you're redirected to the correct conversation after login
Take a look at chat header

Expected Result:
Unavailable workspace should not be displayed on chat header
Actual Result:
Unavailable workspace is displayed on chat header when go to chat while logged out
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/d5e767cf-6367-4522-b54f-781097eaa531
View all open jobs on GitHub

@stephanieelliott  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

I see a lot of bug bug reports but they are either related to focus mode or slow API response. This seems like neither so adding the labels for this to be worked on.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Unavailable workspace is displayed on chat header when go to chat while logged out
What is the root cause of that problem?
Sometimes when the user only has a personal policy, the policy data may be available after the report data. Let's see the image below that I logged the report data, and allPolicies data via useOnyx in HeaderView

Then the policyName is Unavailable workspace briefly
https://github.com/Expensify/App/blob/071f11ce1012db7d07eb750d74f58b552eba6144/src/pages/home/HeaderView.tsx#L85
https://github.com/Expensify/App/blob/071f11ce1012db7d07eb750d74f58b552eba6144/src/libs/ReportUtils.ts#L746-L748
That leads renderAdditionalText being displayed
https://github.com/Expensify/App/blob/071f11ce1012db7d07eb750d74f58b552eba6144/src/pages/home/HeaderView.tsx#L114
After the policy data is available, an empty string is returned here and it disappears
What changes do you think we should make in order to solve the problem?
For this case, let us return noPolicyFound because if returnEmptyIfNotFound is true we always want to display the empty string for the not found policy.
https://github.com/Expensify/App/blob/071f11ce1012db7d07eb750d74f58b552eba6144/src/libs/ReportUtils.ts#L746-L749
Or for the DM the policyID is _FAKE_, we can return early noPolicyFound or empty if policyID is fake
What alternative solutions did you explore? (Optional)

Hey @shubham1206agra can you review this proposal?

I think this is a duplicate of https://github.com/Expensify/App/issues/44480

Thanks for the heads up, but I feel @nkdengineer solution is better.

They linked to an issue. Is it a duplicate or not?

Can you please share your opinion with everyone involved in that other issue and see what they say? It's not great to let a separate ticket fix the same bug in a different way. Let's communicate our intentions first.


Unit test: ReferenceError: InputEvent is not defined or Failed to execute 'dispatchEvent'

Regarding to Events, I did not find a way to test InputEvent
Consider this codesandbox: https://codesandbox.io/s/mutable-firefly-zpz5e
I took the Toggle example from https://reactjs.org/docs/testing-recipes.html
and I also added another component called Input, which basically is a simple Input text
in Input test, I am trying to dispatch an InputEvent, and I have the following error:
TypeError: Failed to execute 'dispatchEvent' on 'EventTarget': parameter 1 is not of type 'Event'.
in my project, I was having ReferenceError: InputEvent is not defined instead.
Toggle tests dispatch a MouseEvent click and it works (BTW, the test at your page is wrong because initial state is false, so the button has Turn on label instead :))
I am doing something wrong or there is an issue here?

These issues are intended for tracking issues related to the documentation. It sounds like you're having trouble understanding how to extend the example in the docs to another situation. I'd suggest asking in one of the community resources at https://reactjs.org/community/support.html, as this isn't the right place.
If you figure out what is wrong and that there is a way to improve the docs, feel free to comment back here or open a new issue.


[Snyk] Upgrade @types/node from 14.14.22 to 14.14.24

Snyk has created this PR to upgrade @types/node from 14.14.22 to 14.14.24.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released 21 days ago, on 2021-02-03.

Release notes

Package name: @types/node

14.14.24 - 2021-02-03

14.14.23 - 2021-02-03

14.14.22 - 2021-01-19

    from @types/node GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

updated manually


KeyError on preprocessing

I refer to the solution of # 17, in the data processing of dygiepp, modify the code to
python ./scripts/data/ace-event/parse_ace_event.py [output-name] --include_entity_coreference --include_event_coreference

Did you solve the question? It doesn't seem to be because of this problem


Make template functions generic with backwards compatibility

This is another approach to making the template functions generic, as done in #239, but now with backwards compatibility for users of the package.

Closing in favor of https://github.com/smallstep/crypto/pull/248.


Iris 1.6.11 compat

It looks like Iris-Flw-compat apparently doesn't support iris 1.6.11 for minecraft 1.19.2 and I miserably failed to build it this way. To be more precise it's failing when running. Can somebody help me?

Is your situation the same as mine, with the Mojang interface progress bar loading repeatedly?

Have you tried checking if the issue still occurs when not using the shaderpack?


Typo under depreciation methods

There is a typo in the straight line service life. There is a 0 typed in it which is wrong.

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

ID: ed925d33-ef75-a817-28f2-b5ba0694156c
Version Independent ID: 0c159e1b-39c6-7e2e-9aea-567aae20bc22
Content: Depreciation methods and conventions - Finance | Dynamics 365
Content Source: articles/finance/fixed-assets/depreciation-methods-conventions.md
Service: dynamics-365-finance
Product: ****
Technology: ****
GitHub Login: @moaamer
Microsoft Alias: moaamer

@DaConfusedSoul, thank you for pointing this out.  I have removed that 0 -- the updated content will be published later today.  Thanks!


Automatically ignore computed properties when building schema

Ignores properties not backed by ivars in both Swift and Objective-C (https://github.com/realm/realm-cocoa/issues/2840). Also makes testing for duplicate properties unnecessary since both cannot be ivar backed (https://github.com/realm/realm-cocoa/pull/1867).
//cc @bdash @tgoyne @mrackwitz @jpsim

Note that this will silently ignore properties marked as @dynamic (in Objective-C) or @NSManaged since they are not ivar backed. This should be considered a breaking change if we expect that users might be doing this. Perhaps they're only using their objects managed by Realm, and mark the properties @dynamic to reduce storage size for an instance of the object. To combat this, we might introduce an managedProperties method to parallel our ignoredProperties method?

It's not just @dynamic. Currently there's nothing stopping you from having a property that's computed on unmanaged instances and persisted on managed instances, since we don't rely on the ivar existing for properties other than generic swift types. I'm not sure if there's any scenarios where that'd actually be useful or a good idea, but that doesn't mean no one is doing it...

@tgoyne I feel like it's reasonable to only manage properties with backing ivars by default. If a user creates an unsynthesized property that gets/sets an unrelated ivar, it think it's fair to treat this as a computed property unless they opt out. This is a very weird use case, and I think we should optimize for ease-of-use in the common case.
Just like we do not assume all properties are computed unless they explicit specify we should manage them, I don't think we should assume all properties should be managed unless they are ignored. It seems like a reasonable default would ignore properties without ivar backing.
Obviously this would be a breaking API change, so we couldn't merge this for a while, but I'd argue we should eventually transition to this behavior.

(Also, I definitely think it's surprising behavior that computed properties are (silently) backed by Realm by default. As a user, I would be very shocked by this.)

Closing for now, but will be eventually merged when we're prepared to make breaking changes https://github.com/realm/realm-cocoa/issues/3864

More motivation to ignore properties not backed by ivars by default: https://github.com/realm/realm-cocoa/issues/3994#issuecomment-241821129


Toast hides behind the Navigation view

Describe the bug
When presenting AlertToast in SwiftUI view with Inline Navigation view, AlertToast with display mode (.hud) hides behind the navigation view.
To Reproduce
Steps to reproduce the behavior:
import SwiftUI
import AlertToast

struct ContentView: View {
    @State var isPresenting = true
    var body: some View {
        NavigationView {
        ZStack {
            VStack{
                Text("Hello, world!")
                    .padding()
            }
            .frame(maxWidth: .infinity, maxHeight: .infinity)
            .toast(isPresenting: $isPresenting, duration: 2.0, tapToDismiss: true, alert: {

                return AlertToast(displayMode: .hud, type: .complete(.white), title: "Testing Alert Toast")
            })
        }
        .navigationTitle("Navigation Title")
        .navigationBarTitleDisplayMode(.inline)
        }
    }
}

Expected behavior
AlertToast should present in front of the navigation view.
Screenshots

Smartphone (please complete the following information):

Device: iPhone12 Mini
OS: iOS14.6

Hi @marvadia,
Please move the .toast modifier to be implemented in NavigationView.
This would solve your problem.
At this point, the view hierarchy in SwiftUI doesn't let you modify this option without putting the view modifier in the right place. You're placing a view below the navigation bar and the highest view in your hierarchy is NavigationView so of course, the AlertToast view would be below that.
I really advise you to check the article I've written about AlertToast and check the Bonus section.
Closing issue.


added github repo link with icon to the header

I added the github repo link, it follows the same patterns as the other icons in the header.
It solves the following issue #61
If require any changes, feel free to tell me, BTW this is my first pull request 😄 .

Also, congratulations on your first PR, this is off to a good start!

Awesome, thanks so much!


Improve/augment content tag to achieve uniqueness

Offline discussion: How to get uniqueness given current schema (version 0.8.0).
Include data.content_attributes:
data:
  content: <str> <-- Standardized, whitelist in fmu-dataio. So not very granular.
  content_attributes:  <-- list of dicts, not explicitly indexed in Elastic
    tag: <str> <-- always present, not standardized content, always a string
    xx: <yy>

(In examples, a properties tag is included, which is a list. Not used currently.)
Suggest to reverse the current seismic (and other similar), use data.content_attributes instead.
User must be able to include custom attributes under data.content_attributes.
Fundamental requirement here is to be able to find the right data, using metadata alone. (Technically, we can use the file.relative_path.)
Previous versions on JS:
content: mycontent
mycontent:
  origin: mycontent_origin

@jcrivenaes @jsorb

Increment to 0.8.1

Give warning if content_attributes are missing for now, then at some point make mandatory.

content_attributes is possibly a use case for flattened objects in Elasticsearch.

Discussion 2022-02-28, add data.tag to provide uniqueness.
tagname is already (optional) input argument. Perhaps we make this mandatory (in the future), and record it in the metadata as data.tag.
The purpose is to ensure uniqueness of data of identical class/content. Currently, the only differentiator will be file.relative_path or fmu.workflow (but the latter is sketchy as well).

tagname was included in #194

Old issue, closing this


VM calls error handler for memory allocation errors

I work on implementing memory limits for Luau in the mlua crate and noticed that the VM calls error handler (provided to lua_pcall) for memory allocation errors (LUA_ERRMEM code).
PUC Lua does not do this (from 5.1 doc):

LUA_ERRMEM: memory allocation error. For such errors, Lua does not call the error handler function.

In reality it triggers LUA_ERRERR later in the error handler (eg. when collecting traceback) which hides the original LUA_ERRMEM code.
Also, in this case there would be no error object on top the stack (and any returned object will be overwritten with LUA_MEMERRMSG)

LUA_ERRMEM: memory allocation error. For such errors, Lua does not call the error handler function.

Hmm, interesting. My recollection is that the policy we have for this is:

xpcall can handle OOM errors
in case the error handler itself results in another OOM, xpcall fails - just as it would if the error handler failed for any other reason

And yeah I think the expectation is that the error message on the stack is synthesized during the call to xpcall's error function. We "pin" the error message string (LUA_MEMERRMSG) to make sure it's always resident in memory.
One possibility is that we should preserve the type of error in case xpcall error handler fails - so instead of generating LUA_ERRERR, we could keep LUA_MEMERR if the handler failed with OOM?
The reason why it can be beneficial for xpcall to handle OOM is that OOM may trigger due to large allocations, but there might be enough memory still left to actually process the error.

Unfortunately it happens only after calling error handler.

Yup you're right. That's definitely a problem. Now, would it help you if that was fixed and there was an actual error message "not enough memory" on the stack?

Yup you're right. That's definitely a problem. Now, would it help you if that was fixed and there was an actual error message "not enough memory" on the stack?

I think this would help.
In my case, also preserving LUA_ERRMEM if error handler OOMed is not neccessary, since I always can collect traceback  by instructing memory allocator to relax limits.
But in general, keepking LUA_ERRMEM for handler OOM seems a good idea too.
--
For non-api users this could be a bit misleading since error("not enough memory") would be indistinguishable from real memory error. But I don't have strong opinion on this case.

But in general, keepking LUA_ERRMEM for handler OOM seems a good idea too.

Yeah, the caveat here is that needs a different interface. You are using lua_pcall presumably but that is bound to the normal Lua C stack contract - it can't smuggle an extra integer easily, other than passing it on the stack (which changes the "signature" of the error callback), and it can't put the error in the actual thread status (lua_status) because threads must only execute code in "OK" status. So for this to work we'd need a custom "C protected call" interface - maybe similar to lua_cpcall.
At any rate it looks like we should fix the error message issue. That's going to improve the behavior regardless of whether luaD_pcall is used by a C host, or a Luau script. Further improvements would involve adding a new C interface and can follow later.
We'll take a look at this shortly.

@zeux maybe there is an option to add new function, let's say int lua_laststatus(lua_State *L) to return status of last execution of luaD_rawrunprotected.
Then error (message) handler can use it to retrieve a reason why it was called.

This would mechanically work, but that interface doesn't seem super clean and may not be future proof.
That said, if you're using lua_pcall, then you would get the correct error (LUA_ERRMEM) as a return value from lua_pcall, you just won't have this inside the error handler. If the error handler fails again with OOM, we need to preserve the ERRMEM error code instead of doing what we do now, which is replacing it wholesale. I think this is what you meant above, apologies if I misread this before. That gives the calling code an opportunity to correctly translate the error regardless of what the handler does.
The only alternative to this right now that I see is just reverting to the behavior of Lua 5.x (which is to never call the handler in the first place), but that seems a little less satisfying. We can probably implement the more complete solution first, and only remove the call to error hander on OOM later if we need to.

Something like this is what I had in mind. One problem is that lua_pcall must obscure the status in case the error handler succeeds; if that is not done (else branch in errstatus != 0 check), on the script side xpcall error function result gets effectively ignored. Neither of these is ideal, which might mean it's beneficial to revert to Lua 5.x behavior after all...
diff --git a/VM/include/lua.h b/VM/include/lua.h
index 9fb35555051..94c7a599aec 100644
--- a/Client/Luau/VM/include/lua.h
+++ b/Client/Luau/VM/include/lua.h
@@ -28,7 +28,7 @@ enum lua_Status
     LUA_OK = 0,
     LUA_YIELD,
     LUA_ERRRUN,
-    LUA_ERRSYNTAX,
+    LUA_ERRSYNTAX, // legacy error code, preserved for compatibility
     LUA_ERRMEM,
     LUA_ERRERR,
     LUA_BREAK, // yielded for a debug breakpoint
diff --git a/VM/src/ldo.cpp b/VM/src/ldo.cpp
index<PHONE_NUMBER>5..91a3766267d 100644
--- a/VM/src/ldo.cpp
+++ b/VM/src/ldo.cpp
@@ -17,6 +17,8 @@

 #include <string.h>

+LUAU_FASTFLAGVARIABLE(LuauBetterOOMHandling, false)
+
 /*
 ** {======================================================
 ** Error-recovery functions
@@ -79,22 +81,17 @@ public:

     const char* what() const throw() override
     {
-        // LUA_ERRRUN/LUA_ERRSYNTAX pass an object on the stack which is intended to describe the error.
-        if (status == LUA_ERRRUN || status == LUA_ERRSYNTAX)
-        {
-            // Conversion to a string could still fail.  For example if a user passes a non-string/non-number argument to `error()`.
+        // LUA_ERRRUN passes error object on the stack
+        if (status == LUA_ERRRUN || (status == LUA_ERRSYNTAX && !FFlag::LuauBetterOOMHandling))
             if (const char* str = lua_tostring(L, -1))
-            {
                 return str;
-            }
-        }

         switch (status)
         {
         case LUA_ERRRUN:
-            return "lua_exception: LUA_ERRRUN (no string/number provided as description)";
+            return "lua_exception: runtime error";
         case LUA_ERRSYNTAX:
-            return "lua_exception: LUA_ERRSYNTAX (no string/number provided as description)";
+            return "lua_exception: invalid syntax";
         case LUA_ERRMEM:
             return "lua_exception: " LUA_MEMERRMSG;
         case LUA_ERRERR:
@@ -553,16 +550,33 @@ LUA_SECURE int luaD_pcall(lua_State* L, Pfunc func, void* u, ptrdiff_t old_top,
         // call user-defined error function (used in xpcall)
         if (ef)
         {
-            // if errfunc fails, we fail with "error in error handling"
-            if (luaD_rawrunprotected(L, callerrfunc, restorestack(L, ef)) != 0)
-                status = LUA_ERRERR;
+            if (FFlag::LuauBetterOOMHandling)
+            {
+                // push error object to stack top if it's not already there
+                if (status != LUA_ERRRUN)
+                    seterrorobj(L, status, L->top);
+
+                // if errfunc fails, we fail with "error in error handling" or "not enough memory"
+                int errstatus = luaD_rawrunprotected(L, callerrfunc, restorestack(L, ef));
+
+                if (errstatus != 0)
+                    status = errstatus == LUA_ERRMEM ? LUA_ERRMEM : LUA_ERRERR;
+                else
+                    status = LUA_ERRRUN; // erase original error code to preserve the error object returned by errfunc
+            }
+            else
+            {
+                // if errfunc fails, we fail with "error in error handling"
+                if (luaD_rawrunprotected(L, callerrfunc, restorestack(L, ef)) != 0)
+                    status = LUA_ERRERR;
+            }
         }

         // since the call failed with an error, we might have to reset the 'active' thread state
         if (!oldactive)
             L->isactive = false;

-        // Restore nCcalls before calling the debugprotectederror callback which may rely on the proper value to have been restored.
+        // restore nCcalls before calling the debugprotectederror callback which may rely on the proper value to have been restored.
         L->nCcalls = oldnCcalls;

         // an error occurred, check if we have a protected error callback

Alright, I've tweaked the logic to the extent it can possibly go to handle some of these corner cases carefully. A preview version of this change should land at  the end of the week behind a fast flag; if that adequately solves all concerns here we can close this.
Briefly, the new behavior is:

error handler will be called on OOMs
if it succeeds, lua_pcall will return LUA_ERRMEM + whatever result the error handler returns will be on stack
if it fails with OOM, lua_pcall will return LUA_ERRMEM + "not enough memory"
if it fails for unrelated reasons, lua_pcall will return LUA_ERRERR + "error in error handling". This allows the caller to distinguish between OOM and other errors in the handler.
if the function itself fails for non-OOM reasons, but lua_pcall fails with OOM, lua_pcall will also return LUA_ERRERR + "error in error handling". This is important so that the caller knows that the function failed for non-OOM reasons.

Thanks @zeux
The diff looks good. Wondering, the status LUA_ERRSYNTAX should be impossible in Luau, is there any reason keep it in the conditions?

if it fails with OOM, lua_pcall will return LUA_ERRMEM + "not enough memory"

if the function itself fails for non-OOM reasons, but lua_pcall fails with OOM, lua_pcall will also return LUA_ERRERR + "error in error handling". This is so that the caller knows that the function failed for non-OOM reasons.

This sounds reasonable. The only question I may have, is have this (OOM handling) functionality ever been used? Given that it was broken (results from handler are ignored), it's unlikely?
If think hypothetically, even collecting traceback can be useless, as allocation can fail at any point (eg creating a new string), not necessary at place with largest allocation.

This sounds reasonable. The only question I may have, is have this (OOM handling) functionality ever been used? Given that it's broken (results from handler are ignored), it's unlikely?

Well, any script that calls xpcall is implicitly subject to this behavior :) I don't know to what extent the OOMs are prevalent, but in our internal testing we have seen OOM caught and handled via pcall, so this will probably clean up some spurious reports due to erroneous first argument in these cases. And yeah, some OOMs are cascading and some are possible to recover from - right now we don't implement emergency GC, which would be useful for recovery here.
The other note is that lua_pcall can be used to collect the traceback without any heap allocations if you do this entirely on C side, using lua_getinfo + assembling the call stack on the native side. This can be used to report the error to telemetry - we do something like this at Roblox, although instead of lua_pcall we use lua_resume (which leaves the error stack in tact at an error).

the status LUA_ERRSYNTAX should be impossible in Luau, is there any reason keep it in the conditions

It will be mostly cleaned up after this change.


x/tools/go/analysis/passes/nilness: missing location for error in embedded struct

What version of Go are you using (go version)?

$ go version
go version go1.17.7 darwin/arm64

Does this issue reproduce with the latest release?
yes ( v0.1.10 )
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/yuki/Library/Caches/go-build"
GOENV="/Users/yuki/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/yuki/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/yuki/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.17.7"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/yuki/gopath/src/go-test/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/00/79n00m9j66zf77ppbmrzg_300000gn/T/go-build438069086=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

go install golang.org/x/tools/go/analysis/passes/nilness/cmd/nilness@latest
put main.go
package main

import "fmt"

type dummy struct {
	innerDummy
}

type innerDummy struct {
	value int
}

func main() {
	var d *dummy
	fmt.Println(d.value)
}

nilness ./...
What did you expect to see?
The correct error location is displayed.
What did you see instead?
-: nil dereference in field selection

Related issue #31008


Fix #818 - Merge REST and OPENAPI operations, introduce HTTP functions

Many thanks for submitting your Pull Request :heart:!
Please specify parts of this PR update:

[x] Specification
[x] Schema
[x] Examples
[ ] Extensions
[ ] Roadmap
[ ] Use Cases
[ ] Community
[ ] TCK
[ ] Other

Discussion or Issue link:

See #818
What this PR does / why we need it:

In this PR, we merged the old rest and openapi functions into one. Now we can inline the openapi definition in the operation attribute. To facilitate making HTTP simple calls, one can now use the new http to mimic a curl-like operation.
Updated schemas and add a new example.
Special notes for reviewers:
Additional information:

@cdavernas @JBBianchi @fjtirado please take a look.


Local pull request success status testing

Docs Build status updates of commit 4066362:
:clock10: Pending: waiting for processors (14 builds ahead of you)
:warning: Docs Build is busy, currently there are 14 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 4066362:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

E2E_DocsBranch_Dynamic/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Return correct value in UdpMsg::PayloadSize for SyncRequest type packets

I believe this to be in error, as it would be requesting the size of the SyncReply's union. I don't know if this has actual issues, aside from telling the user to make room for a few extra bytes on udp SendTo callback. Nonetheless, it is incorrectly written.
It looks like another case of the Last Line Effect (as noted in https://www.viva64.com/en/b/0260/)

Yup!  Good catch!


Remove code-snippet theme prop

Per this conversation: https://github.com/viamrobotics/prime/pull/411#discussion_r1370854790

The dark theme does not work well for JSON, which intend to use this code-snippet for frequently. If we want to introduce a dark mode, we should probably think about that more comprehensively.
Also, after we introduced the reactivity statement to rehighligh on code changes, we need to start escaping the code passed to this component when setting it as the innerHtml of the element.

[ ] Add tests for use-timeout

Any suggestions for how to test this: https://github.com/viamrobotics/prime/blob/main/packages/core/src/lib/use-timeout.ts
Because it uses lifecycle hooks, it looks like it needs to rendered as a part of a component which makes sense. I tried setting that up but it appears like the tests all time out. Wanted to see if there is any guidelines with testing timeouts in testing-library/svelte before I go digging.


Unknown attribute 'generic.attackDamage'

I found the following warning shows up in console when player uses some weapons with customized attack damage.
Ignoring unknown attribute 'generic.attackDamage'

Thought that this error would occur when the damage of an item is set to be negative, but in the end I cannot find a way to recreate the warning. I also couldn't find any posts on Bukkit/Spigot containing this warning. Will get some people to test around on a server and check if it results in the warning showing up.

More log required. Also wonder how to reproduce.
It may not be a bug of RPGItem since attributes like this are handled by minecraft.

There's no more log in the console. Maybe we should add a 'debug mode' to help find bugs?
Also, other plugin may cause this problem as well. Keep this issue open and wait temporarily.

This issue seems to be not related with RPGitems, it's caused by summon commands.
Closing issue.


Step Binding for creating a custom activity record from a timeline

Is your feature request related to a problem? Please describe
Currently we can only create a record from a timeline for appointment, tasks, phone calls, emails and notes, we can't click a button for a custom activity entity.
Describe the solution you'd like
A step binding that accepts a parameter for the name of the custom activity, and clicks the New ->  for it on the timeline.

Closed by #82


Feat: add support to releasing to private ECR

Description of changes:
Publish the the ADOT Java image to a private ECR repository as well.
This PR makes use of this feature: https://docs.docker.com/build/ci/github-actions/push-multi-registries/
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
Attention: 102 lines in your changes are missing coverage. Please review.

Comparison is base (09e6487) 85.71% compared to head (2890dad) 35.97%.
Report is 164 commits behind head on main.

Files
Patch %
Lines

...ent/providers/AwsAppSignalsCustomizerProvider.java
24.00%
35 Missing and 3 partials :warning:

...gent/providers/AwsSpanMetricsProcessorBuilder.java
0.00%
20 Missing :warning:

...ders/AttributePropagatingSpanProcessorBuilder.java
0.00%
16 Missing :warning:

...viders/AwsMetricAttributesSpanExporterBuilder.java
0.00%
11 Missing :warning:

...try/javaagent/providers/AwsSpanProcessingUtil.java
90.16%
1 Missing and 5 partials :warning:

...vaagent/providers/AwsMetricAttributeGenerator.java
96.89%
2 Missing and 3 partials :warning:

...y/javaagent/providers/AwsSpanMetricsProcessor.java
91.48%
0 Missing and 4 partials :warning:

...t/providers/AttributePropagatingSpanProcessor.java
94.59%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff              @@
##               main     #633       +/-   ##
=============================================
- Coverage     85.71%   35.97%   -49.75%
- Complexity       19      205      +186
=============================================
  Files             3       39       +36
  Lines            49     1301     +1252
  Branches          5      141      +136
=============================================
+ Hits             42      468      +426
- Misses            3      811      +808
- Partials          4       22       +18

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


feat(eventindexer): internal devnet changes

do not merge, will remove subscriptions and add block-based filtering for eventindexer as well in this PR.

ok


Switch from ant to gradle

When doing this, find a way to separate the mongo and non-mongo tests automatically so the build doesn't have to be updated every time a test module is added.

Re the 2nd comment, there's a TODO in the script, but it's not really a big deal right now as the auth tests take about 5 mins. Nice to have, can be done later, but otherwise this issue is fixed


Internalisation - no options are shown for the vote

although the backend is returning the correct data
{"FormID":"516b33d5bb22f46aa152b5e8e525faa6bfe074704fa39163be2c962ccf897948","Configuration":{"MainTitle":"{\"en\":\"Companions\",\"fr\":\"\",\"de\":\"\"}","Scaffold":[{"ID":"rrssPs5S","Title":"Rose Tyler","Order":[],"Subjects":[],"Selects":[],"Ranks":[],"Texts":[]},{"ID":"HR4hym9o","Title":"Martha Jones","Order":[],"Subjects":[],"Selects":[],"Ranks":[],"Texts":[]},{"ID":"7OAl3V0W","Title":"Donna Noble","Order":[],"Subjects":[],"Selects":[],"Ranks":[],"Texts":[]}]},"Status":1,"Pubkey":"07a33d31bb872c61885243546a44295aa607cfd69b1a9c87cf753c6ed1b855dc","Result":[],"Roster":["dela-worker-0:2000","dela-worker-1:2000","dela-worker-2:2000"],"ChunksPerBallot":0,"BallotSize":0,"Voters":["kvCOOCsJjA","9fAJ8wKVsw"]}

on https://github.com/dedis/d-voting/pull/313/commits/a3e29b5299dfec0dc72ede434be9b886bf8d9bac the problem seems to be solved, although I don't see any immediate relationship between these two - I'll leave the ticket open until it this becomes clearer

has been resolved


[DMS-353] Validate method allowed from path parsing

https://github.com/Ed-Fi-Alliance-OSS/Data-Management-Service/pull/320


Fix documentation for

Looks like an auto-configuration for Spring for Apache Pulsar is now a part of Spring Boot project: https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#messaging.pulsar.
So, documentation has to be fixed respectively. For now it still talks about spring-pulsar-spring-boot-starter: https://docs.spring.io/spring-pulsar/docs/1.1.0-RC1/reference/reference/pulsar.html.
Also, I don't think it still make sense to mention the old version of the project in the docs since we already in version 1.1.x: https://docs.spring.io/spring-pulsar/docs/1.1.0-RC1/reference/reference/pulsar/quick-tour.html#_dependencies

Great catch @artembilan. Agreed on the removing the old version. Will get this in before GA.

Apparently same goes for the spring-boot-starter-pulsar-reactive, where we mention an old one yet - spring-pulsar-reactive-spring-boot-starter: https://docs.spring.io/spring-pulsar/docs/1.1.0-RC1/reference/reference/reactive-pulsar.html#_preface


Support uPlay

I love using Steam Library Manager, and adding Origin is awesome.  I'd really appreciate if you could look into supporting backing up uPlay games.  Cheers!

Thank you for using Steam Library Manager.
We still got a lot of things to do before calling out Origin support as completed. We need to find a more unified name at first. Also we are still missing header images for Origin games (Which is going to be implemented in a short time) and different manifest file versions other than 4.0, 2.1, 1.1 (if there is any)
But thank you for your feedback on that. I will try to speed up the things. 😄

Thanks for the reply, honestly, you don't need to rush!  Take your time mate and thanks for all your hard work! :)

Sorry closed by accident.

The support is here and will be live with the next release. Thanks!


Add support or internal deposit address

What's done

added api support for get platform deposit address for user
add api support for get platform user token balance

How to test
note
this should be get merged after  https://github.com/TuringAdvisoryGroup/roll-go/pull/3700
Tasks

[ ] Have you written tests for new code (if applicable)?
[ ] Have you tested the changes on all the platforms?

[ ] iOS
[ ] Android
[ ] Web

[ ] Have you added stories to demonstrate the new functionality (if there is any)?

Demo (screenshots, recordings, etc.)

closing in favor of the updates made here which avoided some of the conflicts in this PR: https://github.com/TuringAdvisoryGroup/tryrolljs/pull/311


Support resolve.alias for vite

related: #96
References

https://vitejs.dev/config/shared-options.html#resolve-alias

💯

Perhaps --webpackResolveAlias will cover most of the use cases. Therefore, we will not implement this feature.


OCPBUGS-41981: (fix) registry pods do not come up again after node failure (#3366)

PR 3201 attempted to solve for the issue by deleting the pods stuck in Terminating due to unreachable node. However, the logic to do that was included in EnsureRegistryServer, which only gets executed if polling in requested by the user.
This PR moves the logic of checking for dead pods out of EnsureRegistryServer, and puts it in CheckRegistryServer instead. This way, if there are any dead pods detected during CheckRegistryServer, the value of healthy is returned false, which inturn triggers EnsureRegistryServer.
Upstream-repository: operator-lifecycle-manager
Upstream-commit: f2431893193e7112f78298ad7682ff3e1b179d8c

/lgtm
/label backport-risk-assessed

Test pass, details: https://issues.redhat.com/browse/OCPBUGS-41981
/lgtm
/label qe-approved
/label cherry-pick-approved

/cherry-pick release-4.14


skip_insertion results in a compiler error

Setup
Compiling the following:
use diesel::Insertable;

#[derive(Insertable)]
struct Test {
    x: f32,
    #[diesel(skip_insertion)]
    y: f32,
}

fn main() {
    println!("Hello, world!");
}

with
[package]
name = "dieselstuff"
version = "0.1.0"
edition = "2021"

[dependencies]
diesel = "2.1.6"

Versions

Rust: rustc 1.77.2 (25ef9e3d8 2024-04-09)
Diesel: 2.1.6
Database: not applicable
Operating System Linux

Feature Flags

diesel: none

Problem Description
It errors out with:
error: unknown attribute, expected one of `embed`, `skip_insertion`, `column_name`, `sql_type`, `treat_none_as_default_value`, `treat_none_as_null`, `serialize_as`, `deserialize_as`, `select_expression`, `select_expression_type`
 --> src/main.rs:6:14
  |
6 |     #[diesel(skip_insertion)]
  |              ^^^^^^^^^^^^^^

In general, the following work (as in, they don't error out in the derive macro):

embed
column_name = ...
sql_type = ...
serialize_as = ...
deserialize_as = ...
select_expression = ...
select_expression_type = ...

And these don't work:

skip_insertion
treat_none_as_default_value
treat_none_as_null

What are you trying to accomplish?
Trying to use the Insertable derive macro
What is the expected output?
Either that it doesn't error out, or in case that the input is incorrect, an error message that is less confusing
What is the actual output?
An error message that would suggest that the input is well formed
Are you seeing any additional errors?
No
Steps to reproduce
cargo new --bin diesel-test, change Cargo.toml & main.rs appropriately, cargo +stable build
Checklist

[X] I have already looked over the issue tracker and the discussion forum for similar possible closed issues.

[X] This issue can be reproduced on Rust's stable channel. (Your issue will be
closed if this is not the case)
[X] This issue can be reproduced without requiring a third party crate

Thanks for opening this bug report. This is expected behaviour given your diesel version. The skip_insertion option is not contained in any release yet. The documentation lists all supported field attributes for certain derives.

Shouldn't the error message be different at least? Because while it may not yet be supported in that version; the error message is at the very least confusing.

That's correct. Seems like we somehow accidentally backported a PR that changes the error message only. I'm happy to merge a PR that reverts that + prepares another release. https://github.com/diesel-rs/diesel/commit/45915ac65483f3866f2597f4c386b1827d9b1c92 is the relevant commit

This is now fixed with the release of diesel 2.2, as that release contains support for this attribute.


No data from HMS

Hi,
at first Thank You for sharing this project.
I've compiled the sources using RaspberryPi, Ubuntu 20.04 and cargo/rust 1.73.0 for a friend. Starting the binary with given ip-adresses of inverter and mqtt broker tells me, that the inverter is online. But nothing else happens, no data are published. The inverter is a HMS 800W-T2, checking the version in the hoymiles app it tells V1.1.15, I suppose its the version number of the DTU.
What I didn't do was setting the environment variables.
Any ideas?
[edit]
additional: normally I am connection anonymous to the broker, so I didn't deliver neither mqttuser/pwd nor portno. to the tool
[/edit]

May you have the same problem like I had.
I thought that there are no data’s incoming, but there is just no auto discovery. That means no entity will be there automatically in HA or ioBroker or whatever.
you have to fetch the data with a manual device.

Erm, I am trying to build a bridge to domoticz using a small python script, subscribing and listening for topic hms800wt2/#
mosquitto_sub -t 'hms800wt2/#' -h [broker-ip] gives no data at all.

Ähm, the version I posted is the version of the app which my friend sent to me, sorry. I asked him once again, inverter software version V1.00.08, HW H00.04.00, DTU software V00.01.08, HW H00.01.00

OK, after some time of reading on discord I get more transparency in my issue. I tried to connect and read the data from the hms using the existing wlan, the inverter connected to a fritzbox. Did I learn right, that is not the way the tools is designed for?
Is there somewhere a howto which summarizes the prerequesites to collect the data from the inverter?

If you get the message that the inverter is online, then we have received a valid response with the current readings from it. In other words, it's actually reachable on the network. This would point to the MQTT broker not being reached as expected.
If you set the RUST_LOG=debug environment variable, then you should get (much) more detailed logging.

Do I have to set RUST_LOG during compilation or would it be sufficient to set it before starting the binary?
My work is a little bit complicate because my friend owns a raspi 3, with which compiling the tool is really no fun. So I am compiling here at home and carrying the binary with me on my next visit.

The environment variable is read at runtime. There is no need to recompile, and setting it at start of the binary should be enough.

I appreciate your support. Reporting any results will take some days.


No way to sample from multisampled textures in impellerc shaders

This is blocking support for rendering with non-pipeline blend modes (https://github.com/flutter/impeller/pull/159) because we need to bind the backdrop texture and render to an intermediate texture in this situation.
GLSL 3.3 has features that were replaced in 4+ with different primitives, but we're blocked from using newer builtins because we target GLES 2 -- and so neither can be used in impellerc shaders.
Specifically:

GLSL 4+ removes the texture(sampler2DMS, vec2) overload, and
the compiler blocks use of texelFetch because it can't be used  when we transpile to a GLSL version supported by GLES2.

And so even though we can still bind multisample textures, there's no way to actually pull data from them.
uniform FrameInfo {
  ivec2 texture_size;
} frame_info;

uniform sampler2DMS texture_sampler_dst;
uniform sampler2D texture_sampler_src;

in vec2 v_dst_texture_coords;
in vec2 v_src_texture_coords;
out vec4 frag_color;
// Emulate SamplerAddressMode::ClampToBorder.
vec4 SampleWithBorder(sampler2D tex, vec2 uv) {
  if (uv.x > 0 && uv.y > 0 && uv.x < 1 && uv.y < 1) {
    return texture(tex, uv);
  }
  return vec4(0);
}

void main() {
  // This doesn't compile because it's not supported in GLSL 4.6 (the standard we use for authoring), although it's supported by earlier GLSL versions.
  vec4 dst = texture(texture_sampler_dst, v_dst_texture_coords);

  // This doesn't compile because it can't be used when transpiling to a GLES2 compatible GLSL version.
  ivec2 pixel_coords = ivec2(v_dst_texture_coords * frame_info.texture_size);
  vec4 dst = texelFetch(texture_sampler_dst, pixel_coords, 0);

  vec4 src = SampleWithBorder(texture_sampler_src, v_src_texture_coords);
  frag_color = src + dst - src * dst;
}

Possible solutions:

It may make sense to just switch from GLSL 4.6 to GLSL 3.3 for authoring after refactoring the glyph atlas to not render using instances (I think @dnfield is currently doing this refactor?) The downside here is that we have more limitation on leveraging per-platform features.

Alternatively, we could have the compiler set the source version to 3.3 for just GLES2, and use 4.6 for mostly everything else, enabling specialized solutions for this situation:
#ifdef IMPELLER_TARGET_OPENGLES
  vec4 dst = texture(texture_sampler_dst, v_dst_texture_coords);
#else
  ivec2 pixel_coords = ivec2(v_dst_texture_coords * frame_info.texture_size);
  vec4 dst = texelFetch(texture_sampler_dst, pixel_coords, 0);
#endif

Instancing refactor is flutter/imepller#160
Would it make any sense to have some kind of "special" method for this, either defined in some kind of included file or in the compiler itself? E.g. make the compiler produce valid GLES shader code even when it sees texelFetch.

I made a mistake earlier when reading the 3.3 spec -- my proposed solutions don't work because there is still no multisample overload for texture() in 3.3 either, or in a handful of other GLSL specs I've looked at today (any?) for that matter.
Looking at the GLSL ES 1 spec, there's no concept of reading multisample textures in shader programs, and I couldn't spot any multisample extensions that add this. So I don't think we'll be able to bind multisample textures once GLES is running anyway.
With this in mind, I should actually be trying to bind the resolve texture for MSAA passes. Using the resolve texture is what I should have been doing in the first place since this is just a blend shader.


TypeError: api.injectImports is not a function

Version
3.0.0-beta.15
Steps to reproduce
in /.vuerc:
{
  "packageManager": "yarn",
  "useTaobaoRegistry": false,
  "presets": {
    "test": {
      "useConfigFiles": true,
      "plugins": {
        "@vue/cli-plugin-babel": {},
        "@vue/cli-plugin-eslint": {
          "config": "airbnb",
          "lintOn": [
            "save",
            "commit"
          ]
        }
      },
      "router": true,
      "vuex": true,
      "cssPreprocessor": "stylus"
    }
  }
}

then command:
$ vue create test -p test
What is expected?
🎉  Successfully created project test.
👉  Get started with the following commands:
$ cd test
$ yarn serve
What is actually happening?
TypeError: api.injectImports is not a function
at module.exports (/PROJECT_PATH/node_modules/@vue/cli-service/generator/router/index.js:2:7)
at module.exports (/PROJECT_PATH/node_modules/@vue/cli-service/generator/index.js:28:24)
at Generator.plugins.forEach (/HOME/.config/yarn/global/node_modules/@vue/cli/lib/Generator.js:28:7)
at Array.forEach ()
at new Generator (/HOME/.config/yarn/global/node_modules/@vue/cli/lib/Generator.js:26:13)
at Creator.create (/HOME/.config/yarn/global/node_modules/@vue/cli/lib/Creator.js:135:23)
at process._tickCallback (internal/process/next_tick.js:178:7)

macOS 10.13.4
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>vue create can only be successful by default (babel, eslint) preset.

Please update to beta.16.

thank u. my local yarn and npm version of @vue/cli is different, i remove yarn package then it works.


Improve the accessibility and usability of conditional reveals

What
Improve the accessibility and usability of the 'conditional reveal' functionality of radios and checkboxes.
There are a number of known issues (or potential issues) which we're looking to address:

Checkboxes and radios that conditionally reveal content use aria-expanded, which is not a valid aria-attribute for those roles
The expanded/collapsed state of conditional reveals is not available to all assistive technologies (WCAG 2.1 4.1.2 Name, Role, Value)
The logical order of conditionally revealed content as it appears within a set of radios or checkboxes can be confusing
Conditionally revealed fields are part of the parent fieldset for the set of radios or checkboxes
Tell users not to use conditional reveals to reveal text (for example contextual help)

Although represented as separate issues, they are highly related. So far it has seemed helpful to think about them separately, but any changes will need to be thought about in the wider context.
Firstly

[x] Kick off work to improve accessibility and usability of conditional reveals #1473

Then

[x] Understand what problems designers are trying to solve when using conditional reveals #1504
[ ] How can we involve the wider community in solving the issues with conditional reveals #1505
[ ] Desk research into whether other teams have tried to solve issues with conditional reveals #1508
[ ] Prototype potential fixes for known issues with conditional reveals #1506
[x] Suggest extending support for aria-expanded to radios #2147

Write-up of chat with DAC: https://docs.google.com/document/d/1jqGqfvV2yfMqYmgK0MGhBuE1sMtCXTLvYzCKcfH1Ucw/edit#


update incrementality of 2 intermediate models

#408 introduced new joins to these models that affected incremental builds. More specifically, the models are generating too many rows on incremental builds, which affects performance (#414) and overwrites rows with nulls (#410).
To test these changes, I ran these models a couple times after a full refresh to verify that they don't change.
I will execute a full-refresh of these models to fix existing production data issues when this PR merges.
Fixes #410
Fixes #414

Thank you for making these updates @JamesSLogan. When I tried adding the incremental macros in the CTE's during my PR I ran into errors, so I am glad you were able to get these updated so quickly!


Improve typings for entities when extending graphql

When extending the graphql schema, e.g. as follows:
  app.graphql.extendSchema(`
    extend type Mutation {
      reorderFormFields(ids: [ID!]!): [FormField]
    }
  `);
  app.graphql.defineResolvers({
    Mutation: {
      async reorderFormFields(_, { ids }: { ids: string[] }, ctx) {
        const results = await Promise.all(
          ids.map((id, i) => {
            return app.platformatic.entities.formField.save({
              input: { id, sort: i } as unknown as FormField,
              ctx,
            });
          })
        );
        return results;
      },
    },
  });

I will get the following compile error:

I can work around this by manually declaring:
import type { Entity, Entities } from "@platformatic/sql-mapper";
import type { MercuriusContext } from "mercurius";

type IsFunction<T> = T extends CallableFunction ? T : never;

type ContextAwareEntity<T> = {
  [Property in keyof Entity<T>]-?: (
    options: Parameters<IsFunction<Entity<T>[Property]>>[0] & {
      ctx?: MercuriusContext;
    }
  ) => ReturnType<IsFunction<Entity<T>[Property]>>;
};

export type ContextAwareEntities = {
  [X in keyof Entities]: ContextAwareEntity<
    Entities[X] extends Entity<infer T> ? T : never
  >;
};

and using
  const entities = app.platformatic.entities as unknown as ContextAwareEntities;

  app.graphql.defineResolvers({
    Mutation: {
      async reorderFormFields(_, { ids }: { ids: string[] }, ctx) {
        const formField = entities.formField as ContextAwareEntityHooks<FormField>;
        const results = await Promise.all(
          ids.map((id, i) => {
            return formField.save({
              input: { id, sort: i } as unknown as FormField,
              ctx,
            });
          })
        );
        return results;
      },
  });

but it really seems like I shouldn’t have to.
Also, this would make it easier to discover that you have pass in the ctx in order to get permissions to work (took me a loong time to figure that out)…

This would be amazing to do!

I'm perplexed because this should have worked out of the box as ctx already contains a type to app, which should have everything: https://github.com/mercurius-js/mercurius/blob/a5ed5b07e1111f64eae6d095e6e7a309709a2665/index.d.ts#LL206C62-L206C62.
Do you know how to fix it? Otherwise we'll look into it.

I'm not sure exactly what the above does, but the following is working, so maybe things got fixed.
/// <reference path="./global.d.ts" />
import { FastifyInstance } from 'fastify'

export default async function (app: FastifyInstance) {
  app.graphql.extendSchema(`
    extend type Query {
      moviesWithAllCapsTitle: [Movie]
    }
  `);
  app.graphql.defineResolvers({
    Query: {
      async moviesWithAllCapsTitle(_, _2, ctx) {
        const movies = await ctx.app.platformatic.entities.movie.find({});
        return movies.map((movie) => {
          movie.title = movie.title.toUpperCase();
          return movie;
        })
      },
    },
  });
}

@sabberworm could you clarify what's the actual problem you are fixing?


aggregate taken export includes tips?

I see a context = 'take' constraint in export_history, but this json file I'm looking at for Gratipay includes, e.g., OpenCompany.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/11062262-aggregate-taken-export-includes-tips?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

Sorry, I'm looking at aggregate given.


Cancer shortcut override by empty value in identically named library

Another oversight from #1554. Just need to ensure we are not replacing an existing path with None.

Fixed.


TTC error: received code 28 during response reading after "alter session set container=pdb1"

I can't exec ALTER SESSION SET CONTAINER=PDB1, which results in  TTC error: received code 28 during response reading
func doSql( dbh *sql.dbh,sql string) (error) {
   _,err:=dbh.Exec(sql)
  return err
}

In the same connection ALTER SESSION SET NLS_DATE_FORMAT='YYY-MM-DD HH24:MI:SS' executed without problems
Database behind is a RAC CDB, if this matters. Connected User is a C## common User with the needed privileges
testet with go-ora 2.7.9 and latest 2.7.11

with the "godror" driver there is no such error (but requires a client)

package main

import (
	"database/sql"
	"fmt"
	_ "github.com/sijms/go-ora/v2"
	"os"
)

func main() {
	conn, err := sql.Open("oracle", os.Getenv("DSN"))
	if err != nil {
		fmt.Println("can't connect: ", err)
		return
	}
	defer func() {
		err = conn.Close()
		if err != nil {
			fmt.Println("can't close connection: ", err)
		}
	}()

	_, err = conn.Exec("alter session set container=PDB")
	if err != nil {
		fmt.Println("can't alter session: ", err)
		return
	}
}

the code above pass without error
my connection string using sys with single instance
would you share the return packet after execute the command which produce the TTC error?

would you share the return packet after execute the command which produce the TTC error?
yes, i will try my best. Can you please tell me, how to catch this packet?

from trace file. you can use the following code to get trace file
urlOptions := map[string]string {
    "trace file": "trace.log",
}
databaseURL := go_ora.BuildUrl(server, port, service, user, password, urlOptions)
conn, err := sql.Open("oracle", databaseURL)

Here ist the requested packet from trace.log
2023-08-04T12:57:47.7128: Connected
2023-08-04T12:57:47.7128: Database Version: <IP_ADDRESS>.0
2023-08-04T12:57:47.7128: Exec With Context:
2023-08-04T12:57:47.7128: Exec:
alter session set container=SQLDEPLOY
2023-08-04T12:57:47.7129:
Write packet:
00000000  00 00 00 7c 06 00 00 00  00 00 24 89 6c dc 0c 68  |...|......$.l..h|
00000010  ec 29 a2 ee d4 91 b1 4a  90 05 33 60 a0 1c 38 6e  |.).....J..3`..8n|
00000020  36 b5 73 64 b2 30 c6 de  36 46 18 b1 c3 bc 4d d0  |6.sd.0..6F....M.|
00000030  e8 d9 f3 68 01 7c f7 99  ab 78 e0 0a 68 3c 33 08  |...h.|...x..h<3.|
00000040  9b 2a ae ca f7 15 45 fa  c1 60 99 0c 4e 9f 81 83  |.*....E..`..N...|
00000050  29 96 e0 23 56 dd 2c c0  73 74 bd 84 bf 56 d9 97  |)..#V.,.st...V..|
00000060  c3 a0 14 e6 1f 30 89 4c  ce 6c 4c 09 8a b3 e0 50  |.....0.L.lL....P|
00000070  55 69 59 e2 3e f1 dc 78  87 dd 09 00              |UiY.>..x....|
2023-08-04T12:57:47.7157:
Read packet:
00000000  00 00 00 1c 06 20 00 00  00 00 aa 57 f3 16 08 6a  |..... .....W...j|
00000010  d5 00 e2 53 a7 d2 15 3b  13 21 10 00              |...S...;.!..|
2023-08-04T12:57:47.7160: Close
2023-08-04T12:57:47.7160: Connection Closed
Von: Samy Sultan @.>
Gesendet: Freitag, 4. August 2023 00:24
An: sijms/go-ora @.>
Cc: Thomas Dressler @.>; Author @.>
Betreff: Re: [sijms/go-ora] TTC error: received code 28 during response reading after "alter session set container=pdb1" (Issue #417)
from trace file. you can use the following code to get trace file
urlOptions := map[string]string {
"trace file": "trace.log",
}
databaseURL := go_ora.BuildUrl(server, port, service, user, password, urlOptions)
conn, err := sql.Open("oracle", databaseURL)
—
Reply to this email directly,  https://github.com/sijms/go-ora/issues/417#issuecomment-1664715839 view it on GitHub, or  https://github.com/notifications/unsubscribe-auth/ABR7PFLMYZ6CT4QEJ6W4KJDXTQQIPANCNFSM6AAAAAA3CQSTTA unsubscribe.
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/ABR7PFP5DQKKTHOEO7YL6FLXTQQIPA5CNFSM6AAAAAA3CQSTTCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTDHGGD6.gif Message ID: < @.> @.>

Here is the requested packet:

2023-08-04T12:57:47.7128: Connected
2023-08-04T12:57:47.7128: Database Version: <IP_ADDRESS>.0
2023-08-04T12:57:47.7128: Exec With Context:
2023-08-04T12:57:47.7128: Exec:
alter session set container=!redacted!
2023-08-04T12:57:47.7129:
Write packet:
00000000  00 00 00 7c 06 00 00 00  00 00 24 89 6c dc 0c 68  |...|......$.l..h|
00000010  ec 29 a2 ee d4 91 b1 4a  90 05 33 60 a0 1c 38 6e  |.).....J..3..8n| 00000020  36 b5 73 64 b2 30 c6 de  36 46 18 b1 c3 bc 4d d0  |6.sd.0..6F....M.| 00000030  e8 d9 f3 68 01 7c f7 99  ab 78 e0 0a 68 3c 33 08  |...h.|...x..h<3.| 00000040  9b 2a ae ca f7 15 45 fa  c1 60 99 0c 4e 9f 81 83  |.*....E....N...|
00000050  29 96 e0 23 56 dd 2c c0  73 74 bd 84 bf 56 d9 97  |)..#V.,.st...V..|
00000060  c3 a0 14 e6 1f 30 89 4c  ce 6c 4c 09 8a b3 e0 50  |.....0.L.lL....P|
00000070  55 69 59 e2 3e f1 dc 78  87 dd 09 00              |UiY.>..x....|
2023-08-04T12:57:47.7157:
Read packet:
00000000  00 00 00 1c 06 20 00 00  00 00 aa 57 f3 16 08 6a  |..... .....W...j|
00000010  d5 00 e2 53 a7 d2 15 3b  13 21 10 00              |...S...;.!..|
2023-08-04T12:57:47.7160: Close
2023-08-04T12:57:47.7160: Connection Closed

the data is encrypted so may be the issue occur with encryption
I will test with encryption and tell you the result

Yep, sqlnet is using aes256 encryption

I test the command using AES256 encryption without errors

for me now the only untested situation is RAC and me be issue is related to it

Hm, If i can help you with some tests let me know.

could you connect without encryption to see what happens in log file?

Without encryption it works correctly. Do you need the log? I could send it per PN

ok I need to check if there is something strange
also I need to ask you does error come every time or some time

it occurs each time on every (our) RAC Databases. It not happens if i connect to an oracle-xe 21.3 docker container und set sqlnet.encryptionö. see https://github.com/Tommi2Day/containertest

as I understand the error happen with RAC in encryption mode.
so if you can use debugger like goland and log last packets unencrypted so I can detect in which stage the error happen.

all found in data_packet.go
data that go to server: before encryption
data that received from server: after decryption

it is better to add logging at that points
for example fmt.Println()
because some oracle servers have small timeout so when you debug code and stop execution for a while  the server  hit timeout and close the connection so you got connection timeout

I think I should add these lines of logPacket  in next release so encrypted data is readable for debugging

I update logging of Decrypted packet in v2.7.15

here we are

alter session set container=SQLDEPLOY
2023-08-22T11:16:22.0071:
Write packet (Decrypted):
00000000  03 5e 00 02 80 21 00 01  01 25 01 01 0d 00 00 00  |.^...!...%......|
00000010  00 04 3f ff ff ff 00 00  00 00 00 00 00 00 00 00  |..?.............|
00000020  00 01 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000030  00 25 61 6c 74 65 72 20  73 65 73 73 69 6f 6e 20  |.%alter session |
00000040  73 65 74 20 63 6f 6e 74  61 69 6e 65 72 3d 53 51  |set container=SQ|
00000050  4c 44 45 50 4c 4f 59 01  01 01 01 00 00 00 00 00  |LDEPLOY.........|
00000060  00 00 02 80 00 00 00 00                           |........|
2023-08-22T11:16:22.0072:
Write packet:
00000000  00 00 00 7c 06 00 00 00  00 00 47 cb 93 e2 06 ff  |...|......G.....|
00000010  73 be c7 5e f7 34 95 37  f8 93 71 c9 11 81 db 75  |s..^.4.7..q....u|
00000020  74 ce 42 37 d8 17 36 d3  b2 f5 c1 81 66 24 ae fc  |t.B7..6.....f$..|
00000030  1f 9b ca e6 d1 7f 51 c1  ad 46 ce 12 f2 45 d1 8e  |......Q..F...E..|
00000040  c3 77 0d 4a c3 a3 17 5e  ec 78 5f 42 8e e8 b3 68  |.w.J...^.x_B...h|
00000050  90 ea 26 6f 48 4f 9b d4  31 4b 99 30 89 71 d3 11  |..&oHO..1K.0.q..|
00000060  90 0b ec 38 48 bf 24 4c  31 c7 33 bf c3 7a 9e 26  |...8H.$L1.3..z.&|
00000070  f0 4a c7 1f 12 e5 ba 81  68 f3 09 00              |.J......h...|
2023-08-22T11:16:22.0294:
Read packet:
00000000  00 00 00 1c 06 20 00 00  00 00 00 2b 9b 10 f7 a6  |..... .....+....|
00000010  90 24 ef 3e dd 8e c2 b8  60 a0 10 00              |.$.>....`...|
2023-08-22T11:16:22.0296:
Read packet (Decrypted):
00000000  1c                                                |.|

I can provide the full trace.log via PN if needed, but dont like to add it here

I make a commit that contain code for reading TTC 28 code .
would you please load this code and test it

sorry I make some mistakes I fix it in last commit

Yeah, this looks much better. Tested with github.com/sijms/go-ora/v2 v2.7.16-0.20230823173955-f8fb6a9452b4

alter session set container=SQLDEPLOY
2023-08-24T11:37:29.6169:
Write packet (Decrypted):
00000000  03 5e 00 02 80 21 00 01  01 25 01 01 0d 00 00 00  |.^...!...%......|
00000010  00 04 3f ff ff ff 00 00  00 00 00 00 00 00 00 00  |..?.............|
00000020  00 01 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000030  00 25 61 6c 74 65 72 20  73 65 73 73 69 6f 6e 20  |.%alter session |
00000040  73 65 74 20 63 6f 6e 74  61 69 6e 65 72 3d 53 51  |set container=SQ|
00000050  4c 44 45 50 4c 4f 59 01  01 01 01 00 00 00 00 00  |LDEPLOY.........|
00000060  00 00 02 80 00 00 00 00                           |........|
2023-08-24T11:37:29.6169:
Write packet:
00000000  00 00 00 7c 06 00 00 00  00 00 60 3d 53 1d 04 ce  |...|......=S...| 00000010  75 27 19 f2 d7 06 08 2e  5d 68 2b 8a 8d 22 74 21  |u'......]h+.."t!| 00000020  99 44 7b 63 ec 43 7b 77  da b4 39 4e 50 ab 86 a4  |.D{c.C{w..9NP...| 00000030  2b ad 84 2e 9e e4 8f fb  43 c1 7e da 68 dd 21 27  |+.......C.~.h.!'| 00000040  6b df da 45 7f ff 2c 8f  3c f7 0b 3e df cd ad 95  |k..E..,.<..>....| 00000050  c6 08 85 35 ad 41 5a ad  6f 73 e6 b4 60 7f ed 2f  |...5.AZ.os..../|
00000060  65 db 03 49 5e da ef d3  3f e4 34 6b 68 0a cf e9  |e..I^...?.4kh...|
00000070  f8 76 72 e7 07 c8 bd 01  fe c0 09 00              |.vr.........|
2023-08-24T11:37:29.6605:
Read packet:
00000000  00 00 00 1c 06 20 00 00  00 00 03 e1 4f f3 9f 53  |..... ......O..S|
00000010  00 5c fc 18 ad 64 a5 d9  ab 6e 10 00              |....d...n..|
2023-08-24T11:37:29.6605:
Read packet (Decrypted):
00000000  1c                                                |.|
2023-08-24T11:37:29.6606: TCP Negotiation
2023-08-24T11:37:29.6606:
Write packet (Decrypted):
00000000  01 06 00 4f 72 61 63 6c  65 43 6c 69 65 6e 74 47  |...OracleClientG|
00000010  6f 00                                             |o.|
2023-08-24T11:37:29.6606:
Write packet:
00000000  00 00 00 2c 06 00 00 00  00 00 5e 34 f1 b7 78 e4  |...,......^4..x.|
00000010  1a ca c1 1a f5 65 78 60  9c 24 37 62 5c 6f d1 77  |.....ex.$7b\o.w| 00000020  43 e1 7d a2 48 5b 7f de  7b b0 0f 00              |C.}.H[..{...| 2023-08-24T11:37:29.6739:  Read packet: 00000000  00 00 00 cc 06 20 00 00  00 00 fa 37 f0 12 19 71  |..... .....7...q| 00000010  56 62 43 e8 78 5c 7c cf  f6 91 b8 8a 9b e9 7b 75  |VbC.x\|.......{u| 00000020  72 39 07 42 f6 0c 5e d8  ad 4d ba e9 d5 fd 69 6d  |r9.B..^..M....im| 00000030  4c 1b 18 94 f1 57 85 e6  b4 59 98 03 d2 3b e7 9c  |L....W...Y...;..| 00000040  98 ef 02 79 58 11 32 37  2c 35 d0 06 29 39 5c c8  |...yX.27,5..)9\.| 00000050  9a fe 9a ab 0a ce 9e 95  7a 82 b7 4b 04 12 e2 45  |........z..K...E| 00000060  25 b3 3a 3e 53 84 7c 30  7b 5b 2b 97 67 c4 d0 28  |%.:>S.|0{[+.g..(| 00000070  19 71 41 31 ca f3 c5 f1  25 0e bb 36 06 57 b9 9c  |.qA1....%..6.W..| 00000080  86 2f 37 14 8b c9 c8 6c  14 c6 d8 49 7c ac 6f 6d  |./7....l...I|.om| 00000090  4a 6f 45 d0 a5 d3 46 09  4b 90 0d ae cf 04 c1 0b  |JoE...F.K.......| 000000a0  3c dc 1d e0 f9 f0 cb a3  75 b4 c1 fa 69 b7 9f 1c  |<.......u...i...| 000000b0  19 51 d7 ac 6d 56 7f cf  82 01 c3 4c 8e 6a f0 1e  |.Q..mV.....L.j..| 000000c0  ad 0c 97 94 f4 ad 6b c5  ca 20 0c 00              |......k.. ..| 2023-08-24T11:37:29.6739:  Read packet (Decrypted):  00000000  01 06 00 78 38 36 5f 36  34 2f 4c 69 6e 75 78 20  |...x86_64/Linux | 00000010  32 2e 34 2e 78 78 00 2e  00 01 00 00 00 64 00 00  |2.4.xx.......d..| 00000020  00 60 01 24 0f 05 0b 0c  03 0c 0c 05 04 05 0d 06  |..$............|
00000030  09 07 08 05 05 05 05 05  0f 05 05 05 05 05 0a 05  |................|
00000040  05 05 05 05 04 05 06 07  08 08 23 47 23 47 08 11  |..........#G#G..|
00000050  23 08 11 41 b0 47 00 83  00 2e 07 d0 03 00 00 00  |#..A.G..........|
00000060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000070  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000080  00 00 2a 06 01 01 01 6f  07 01 0c 01 01 01 01 01  |..*....o........|
00000090  01 01 7f ff 03 0e 03 03  01 01 ff 01 ff ff 01 0b  |................|
000000a0  01 01 ff 01 06 0b e2 01  7f 05 0f 0f 0d 07 02 01  |................|
000000b0  00 01 18 00 7f                                    |.....|
2023-08-24T11:37:29.6739: Server Charset: 46
2023-08-24T11:37:29.6739: Server National Charset: 2000
2023-08-24T11:37:29.6740: Data Type Negotiation
2023-08-24T11:37:29.6741:

is there any error comming or every thing is ok

No errors so far in my test case. I think its ready to release. THX for this solution


Endpoints for AADConnect Health agent missing

This page is missing the endpoints for AADConnect Health agent which is part of Azure AD Connect Classic Sync (ADSync) product.
AADConnect Health agent is a very important tool for supportability of Azure AD Connect, lack of connectivity will cause the health agent to not be able to upload important metrics that Microsoft can use for better support Customers.
Please add the URLs for Connect Health that are documented here: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install#outbound-connectivity-to-the-azure-service-endpoints
Let me know if you have any questions.
Thanks,
/Nuno

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

ID: 66bd8666-3566-a901-b25b-eb6baba6264a
Version Independent ID: e9f6310f-2207-8c81-d31a-3d5a80beb26b
Content: Office 365 URLs and IP address ranges - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/urls-and-ip-address-ranges.md
Service: o365-administration
GitHub Login: @kelleyvice-msft
Microsoft Alias: kvice

@kelleyvice-msft Please help us in resolving this issue. Thanks

Thanks for reaching out to the Microsoft 365 Enterprise content team. Because all Microsoft 365 endpoints data displayed in learn.microsoft.com articles is autogenerated by the Microsoft 365 endpoints web service, the content team cannot resolve issues directly related to this data.
We recommend that you contact your organization’s TAM (Technical Account Manager) to escalate your inquiry to the engineering team associated with the endpoint in question. If you do not have a TAM assigned to your organization, please contact Microsoft Support.


Expose native event handler publicly when passing vnode data to directive.

What problem does this feature solve?
I would like to access the native DOM event handler for a given click event so that I can remove it in a directive.  Currently the vnode parameter we pass to a directive includes a list of event listeners, but only exposes the reference to the event handler on an element via a private member _wrapper.  This is the event handler reference I will need in order to call removeEventListener from an element.
The use-case here is to build a reusable directive that allows gating certain features based on a condition.  Say for example you'd like to gate any component or element based on a user's permission.  You could add a v-admin-only directive that will disallow clicking and taking an action if the user is not an admin.  In order to accomplish that, we will need a reference to the event handler on the element in order to remove the event listener from the element.  I have found that the only location that handler is accessible is via (for a click event example) vnode.data.on.click._wrapper and vnode.data.nativeOn.click._wrapper.  The _ implying a private member.  I'd like to be able to expose this publicly so as to be confident that this method of accessing the function would be officially supported.
The only other ways I've found for achieving a similar behavior would be to use Chrome's getEventListeners method, but that's only available for Chrome browser, or, overriding the native addEventListener method to track event listeners by element myself.
I think this would be a valuable feature for Vue to support as there isn't another way to achieve this that I've found and would make directives very powerful.
What does the proposed API look like?
vnode.data.on.<eventType>.wrapper

If you want to remove events with a directive, the directive should be responsible for adding such events as well, manually changing things added and tracked by Vue is in general a bad idea because it could break the application.
Directives are to have low-level dom access to plain elements but not to change things that were added via a component on Vue.
As for the gating, you can still add a global event listener that captures events and stop propagation/prevent default globally

As for the gating, you can still add a global event listener that captures events and stop propagation/prevent default globally

That would require not stopping the event at the specific component and allowing it to bubble up, which could have other side effects.

manually changing things added and tracked by Vue is in general a bad idea because it could break the application

I understand this point, but this is possible in many other ways.  Especially given that directives already expose the element they're attached to.

Also would a better proposal perhaps be to provide a way to remove the click handler from both Vue and natively instead?


Re-check asset still exists after prompts (in case revoked)

@cjb
Minor tweak to re-check the asset still exists after all prompts.
This allows an update to be revoked immediately.
I think a small tweak for a potentially very helpful feature?

@keybase/react-hackers
This is fine with me, but I remember someone pointed out that not being able to apply an update that you downloaded earlier after you go offline will be counter-intuitive.
Still, :thumbsup: from me, perhaps wait for a golang review from e.g. @patrickxb.

LGTM, one small question.


Expose logging via RPC

Hi,
This PR introduce logging capabilities for workers via RPC.
I know users can already logs by printing on stderr, but logs always appears with a WARNING level. It could be a great addition to be able to control log levels and fields.
This could make logs aggregations in containerised environment easier as apps could log directly on the container stdout.

Thank you! I've been thinking about similar approach for a while. I need quite a bit of time to review it due to the load at work.

Take your time! And thank you for this great project :)

Hi! Overall it looks cool, can you add support for multiple log channels so we can create custom message channels later.

Let me explain in greater details:
Ideally, we would have single service dedicated to ALL roadrunner logging, we can mount this service via IoC container and let each service/worker to gain its own logging channel. Then we can configure this service to store/rotate service channels independently. We don't have to implement now, but having channel (prefix) support will be nice, as single-channel loggers are mostly useless for larger applications.

Hi! Thank you for your comments.
I am not sure to understand what you would like.
Do you want to be able to write logs on multiple logger instances from RPC? These instances could be configured via a log section in the config. Supporting log on different output: stdout, files...
Or do you want to inject different logger instance in services resolved by the IoC container?

@Baldinof Thank you very much for your efforts, but we decided to do this in a slightly different way. For sure, I'll notify you in related PR. For now I am going to close this PR.

No problem, I look forward to see that :)


triggerDragStart not working as expected in touch environment

In a touch device the triggerDragStart activates drag start on second touch, please run this codesandbox in a touch device or chrome device tool to observe the behaviour.

never mind cancelable was the problem.


Enhance useTransaction hook

Currently, we are passing the function arguments while calling the useTransaction() hook.
Instead of that, we should pass the function arguments while calling the method returned from this hook.
Refer to this tweet for more reference.

I can tackle this if nobody is yet assigned to it.

Sure.

I have a question regarding this hook. There doesn't appear to be a provider being used to make the contract call, is this correct?

@Ibby-devv just checking in! Do you need help in any way? Any blockers?


design a my profile page with information like first name last name mobile and others

.

Preview UI

Preview UI
Based on your requirements, I will create a "My Profile" page with information such as first name, last name, mobile number, and other details. I will use the provided code as a reference to create the Vue code for the profile page.
Here is the Vue code for the "My Profile" page:
This Vue code creates a "My Profile" page where users can manage their profile information including first name, last name, mobile number, country, receive updates checkbox, and bio. Users can update their information and save changes using the "Save Changes" button.