Update QSTN.md

Project Abstract

QSTN is a Web3 survey marketplace where businesses fund surveys, reward participants, and uphold user privacy through our data wallet-driven profiles.

Grant [level] 1

[x] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or Polkadot (USDC & USDT) or BTC address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

I have read and hereby sign the Contributor License Agreement.

For reference, see here https://github.com/w3f/Grant-Milestone-Delivery/pull/1017#issuecomment-1747270967

Thanks for the update @qstnus so just to make sure I understand correctly:

You are extending the timeline 3 months and aiming to deliver by end of December?
Is all the rest of the info staying the same? For example, you mentioned the switch to traditional email OAuth instead of login with Polkadot SS58 accounts. Are you intending to implement functionality with wallets this time around?
Seeing as it's been a year, are all team members the same?
Is the legal entity and address still the same? I noticed that the application says QSTN, LLC while your website says @2023 Sink

Hello @keeganquigley,
We are keeping the same proposal as outlined in our original application. Below are the answers to your question!

Yes we are extending until December (we should be done before this)

The information is staying the same - OAuth works on Moonbeam because we use Safe Global for the vault mechanism (EVM compatible), with Polkadot users need Polkadot JS wallet to interact with the pallet and custody funds.

The members are the same

The legal entity and address is the same (Sink is the name of our lead developer's contracting firm)

Thanks for the quick response @qstnus everything looks good except for regarding your second point:

I understand the SAFE vault was needed for the EVM implementation "due to compatibility", but wouldn't this not be needed anymore for the native substrate version? Also, is the SAFE vault still non-custodial?

Hello @keeganquigley
SAFE is a non-custodial solution by Consensys (https://safe.global/), it facilitates wallet creation utilizing email addresses. For redeeming Polkadot rewards, users must link their JS wallets and claim rewards directly to their wallets.
Currently, SAFE lacks support for Polkadot. Given this, we will enable users to interact directly with the pallet, easing the reward redemption process post-survey completion.
EVM Scenario:
Upon signing up using an email address, EVM rewards are transferred to the user's SAFE vault.
Substrate Scenario:
Users sign up with an email address and connect their wallet, which allows for the withdrawal of DOT rewards.

Thanks @qstnus for the updates. I will go ahead and mark the amendment as ready for review and ping the rest of the committee. Personally, I'm not willing to support it at this point as we've already waited a year for it, and I'm still not seeing the requested changes to the application. I'm not convinced about the technical aspects of it or whether it would be delivered in good faith, since Moonbeam is your team's main focus right now.
Also, since you already seem to have an established revenue model via subscriptions, whereas we mostly focus on early-stage PoCs providing common good software for the community.

Hello @keeganquigley,
I appreciate your feedback. I wish to clarify that various restructurings, both within our product and team dynamics, significantly contributed to the delay in the grant's delivery.
Here are some notable milestones we've achieved since our grant request:

Secured a position in Outlier Venture's NEAR Base Camp, successfully closing our pre-seed round.
Developed a data wallet feature, now generating zero-knowledge proofs upon survey completion.
Integrated AI to assist businesses in crafting surveys and evaluating authenticity of responses through a "credibility" score.
Garnered preliminary interest from notable entities like NYU, Estée Lauder, and L'Oréal for potential test partnerships, in collaboration with the NEAR Foundation.
Were honored with acceptance into the Polkadot Blockchain Academy, although a visit was precluded due to visa constraints.

Press:
Outlier Ventures -
https://outlierventures.io/article/near-foundation-and-outlier-ventures-announce-the-first-near-base-camp-accelerator-cohort/
Parsiq -
https://hub.parsiq.net/unicornization
Mastercard Demo Day -
https://youtu.be/TkfHLgsBxiE
Mintbase -
https://blog.mintbase.xyz/wrapping-up-mintbases-demo-day-f13fd192c8fc
CoinDesk -
https://www.coindesk.com/video/crypto-outlook-2023-regulation-web3-daos-stablecoins-and-jobs/

Hello @keeganquigley,
How do you suggest we proceed? I am willing to add these revisions or should we leave as is? Thanks!

Hello @keeganquigley,
In addition, our original application says 15 months, which puts the due date at October. I believe we can deliver within this time period and keep the same proposal if that would be an easier solution. Thanks!

Thanks @qstnus feel free to make the changes, as my vote is just one out of the entire committee and other members may feel differently.

Hello @keeganquigley,
I appreciate the transparency. The application has been updated. Let me know if I need to do anything else!

Hello Polkadot,
For clarification, we filed for this grant a year ago and decided to pivot our implementation after multiple feedback. I apologize for the confusion but DOT has always been in our roadmap. We started with Moonbeam first given its EVM compatibility and SAFE integration - now that is complete we will focus on the local substrate chain.
It's a bit frustrating to have a grant potentially rescinded when we budgeted for this, hired developers specifically within the ecosystem from the PBA and it almost feels as if we are being punished for being a multichain application.
The reason DOT is attractive is because it aims to be intraoperative. Yes, we started this implementation on NEAR but given their connection with the Rust language - this is a natural evolution to our product.
I have been following Polkadot since before the bull run and to work with the Web3 Foundation is a literal goal as a builder in the ecosystem for myself and our CTO. I have spent the past two years working very hard on this project as a solo and underrepresented founder so whatever information you need, I will procure.
@Noc2
Comment 1:
We are sourcing the ZK proof mechanism from Polygon ID (https://polygon.technology/polygon-id) - these cryptographic proofs occur off-chain and allow us to create attestations within the QSTN user profile after KYC and survey completion.
In regards to future plans on Polkadot:

We plan to attend the PBA 5 Cohort in Singapore (spoken to Tim Dobie) and were confirmed for the last cohort but were unable to attend due to visa issues
We plan to integrate and partner with a marketplace on Polkadot to allow users to mint their survey media and access secondary trading liquidity
We will apply for the Polkadot Global Relayers Program again - denied last time but will continue to apply

Improvements from NEAR MVP to DOT:

Create leaderboards to track most active businesses and users
Create credibility score using AI to filter user responses
Create user funnel to allow business to index DOT customer profiles based on responses

@takahser
Comment: 1
I removed the proprietary language from our documentation - I wrote it this way because we are patent pending for a couple methods and wanted to share our competitive moat but deliverable 5 is confirmation we will open source the ZKP API
Comment: 2
This has been moved to the correct section.
Comment: 3
We will not be building an integration between SAFE and Substrate because SAFE is only supporting EVM chains at the moment. I was explaining SAFE is the vault mechanism used in our EVM scenario but on DOT users have to claim with their Polkadot JS wallet directly.
Comment: 4
A zero knowledge proof allows us to keep these attestations for KYC and/or survey completion within the user profile. Instead of writing in storage, we store these attestations in their user profile which doubles as a "data wallet" - in this manner, we allow users to autonomously withdraw rewards and our oracle scans for the ZKP.
If we act as an intermediary and make the reward determination, this is where we get into trouble as a US company given the regulatory uncertainty around securities, blockchains and our inability to facilitate user interactions with these assets.

@qstnus thanks for the updates and the detailed replies, I appreciate the work you're putting into this.

We will create an API for the Cubby data wallet

This means that the ZKPs are integrated with a proprietary product (Cubby) which still goes against our guidelines, even if the deliverable itself is open-sourced:

All code produced as part of a grant must be open-sourced, and it must also not rely on closed-source software for full functionality.

I'm fine with everything else, so if you would open-source Cubby (or maybe a downsized version thereof) I'd be willing to add my approval to the amendment. If that's not possible from a business perspective since you describe it as your competitive moat I'd understand of course, but in that case I wouldn't be able to add my approval.

Hello @takahser,
Thanks for the feedback. I spoke with our CTO and we will open source the data wallet as a deliverable. This has been included in our proposal. Please let me know if we should provide additional information.
Looking forward to the next steps!

LGTM

Hello @takahser & @nikw3f,
Thanks for the support. We look forward to reaching mainnet on Polkadot. LGTM!


Send topic slug to rummager.

This will enable us to avoid the mess here:
https://github.com/alphagov/rummager/blob/5ac805b/lib/registry.rb#L93-L107

Good call.

Upcoming PR on rummager will fix the services & information pages...


⚠ Site ANTS has degraded performance

In 314e522, Site ANTS (https://ants.gouv.fr) experienced degraded performance:

HTTP code: 200
Response time: 6812 ms

Resolved: Site ANTS performance has improved in 4fbe4c4.


spring-graphql-common is out of sync with graphql-java

The latest version of graphql-java (3.0.0) changed DataFetchingEnvironment to an interface instead of a class, but spring-graphql-common inside of ReflectionGraphQLDataFetcher is expecting DataFetchingEnvironment to be a class leading to a runtime exception being thrown.
Technically this issue is with spring-graphql-common, but it looks like that project hasn't had an update in over a year. There do appear to be several forks, including one that has updated the dependency to use graphql-java 3.0.0, but that fork doesn't seem to exist on any nexus repo requiring that you check out and build that fork in order to work around it.
Until spring-graphql-common is updated the version of graphql-java should be constrained to an earlier version, or else support for spring-graphql-common needs to be temporarily disabled.

I thought I had already disabled it, but I must have forgotten.  I'll disable it now.  If anyone is using spring-graphql-common and wants to start maintaining it, we can fork it into graphql-java, but I don't believe that project should hold the spring-boot starter on an old version of graphql-java

I added a comment to the readme with spring-graphql-common's latest supported version.


Incremented version to 2.1.1.

Coming from https://github.com/opensearch-project/opensearch-build/issues/1818 post release activities.

Codecov Report

Merging #289 (bebe19a) into 2.1 (bff858a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              2.1     #289   +/-   ##
=======================================
  Coverage   52.16%   52.16%
=======================================
  Files         150      150
  Lines        4971     4971
  Branches      971      971
=======================================
  Hits         2593     2593
  Misses       2123     2123
  Partials      255      255

Continue to review full report at Codecov.

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

Closing this as 2.2.0 is released and this version won't be released now.
Thanks!


fix: registering molucules in BlankView & rendering bugs

Registered moleclues in CreateBlankView.vue file.
There needs further evaluation of feature since the code is breaking at multiple points so please don't merge this PR

Thanks for the pull request! But issue has been fixed already.


:bug: Remove placeholders from descriptions

I have done some modifications that I think improve a bit the descriptions, mostly shortening them (suggestions and references to links are usually placed in the message)

+1 to all @jmle suggestions!


Why are both prompts and config required?

@mocyuto would it make sense to make prompts optional?

Yeah, since the config can be used to provide a reference to the prompt

@typpo, promptfoo allows specifying the prompt pattern in the config file. Is there any reason for making this parameter required?

https://github.com/promptfoo/promptfoo-action/pull/108/files

I see there's a PR in the works.

would love this PR to be merged as well.


Can't get it to work with Vee-Validate

Here is the input :

the name is set correctly
v-validate is simply set to 'required' as specified by the doc
v-model is set and and is correctly updated on change

<toggle-button :color="{checked: '#484579', unchecked: '#E0E8FC'}" :width="90" :height="35" :labels="{ checked: 'Yes', unchecked: 'No' }" :name="'approval'" v-validate="'required'" v-model="formInfos.approval"/>
But for some reason, I can't catch the error from the v-validate errorBag on that specific input when it's false.
The input appears in the "fields" object generated by the validation plugin, props are updated as well but no error message.
What am I missing ? Is this a known issue ? Is it related to the toggle structure ? If not, please close the issue 💪
FYI it works with a simple :
<input type="checkbox" v-validate="'required'" v-model="formInfos.approval">
Originally posted by @RandomPiche in https://github.com/euvl/vue-js-toggle-button/issues/46#issuecomment-447060434
<EMAIL_ADDRESS><EMAIL_ADDRESS>Thanks for considering my request !

hey, i do not know how your directive will work with this component as far it is not input, I also did not use vee-validate


New version of Alfred-Cheat

Hi Wayne,
Here is the pull request for my new version of Alfred-Workflow.
Best,
Olivier.

Hi Olivier @odapg, thanks very much first for your contribution and your interest to invest in this project. I like your ideas, especially the "open in editor" and the parsing rule. The "preview in HTML" seems ... good but I think they might be useful with long comments and complicated commands right? Anyways it's good to have that. Thanks.
But to merge your feature, could you please separate your commit to small commits that contain different features? it's easier to do the review and I can see possible improvements in the code but couldn't give comments because I'm not sure what it is for. All you change now is in one single commit, which is a bit of anti-engineering.
So here's how I'm gonna do to integrate your idea into a new release:
Option 1: Separate your commit by features. I can do a very quick review of each one, and merge fast. When all features are merged, I'll release 2.0 version ASAP. Yeah they're worth a version bump.
Option 2: I'll take time to read your code, understand your logic and implement on my own again. I'll quote your name in the README and the code comment of course no worries. But you might not appear in the commit history.
Thanks again :) Let me know if it works out for you.
Wayne

Hi Wayne,
Sure, I will try to make separate commits. Give me a few days :-)
Concerning the HTML feature, I use it to have a global view of the hotkeys of an app; I suppose it is a bit different if you mainly use cheatsheets for unix commands...

Yeah I mainly use for unix command. But sure the HTML preview is an awesome idea. Even linux commands need a way sometimes to e.g., see detailed description.
And cool thanks for your effort! take your time!

Hi, I made six different branches to the workflow which are actually incremental (not at all independent — for instance the Quicklook preview heavily depends on the parsing rule of course). The HTML preview corresponds to alfred-cheat-commit5.
I am pulling the requests, let me know what you think!

Closing this one as the review is on other branches. Thanks for your contribution.


Closing the window with the context menu shown crashes the program

Microsoft PowerToys version
0.74.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Registry Preview
Steps to reproduce

Open any file or type any text
Right-click the text field
Close the window

The bug report log
✔ Expected Behavior
The context menu should hide and the program should close normally
❌ Actual Behavior
The context menu stays visible and the program crashes
Other Software
Windows 10 Pro (build 10.0.19045.3513)

One thing is that the context menu doesn't go away when clicking the title bar, but goes away when clicking on other areas of the window. Maybe that's causing the issue?

Oh the issue is definitely caused by the context menu is staying open: if it's not open, there's no crash, but I don't know that I have a way to ensure that the context menu is open or closed (or to close it before leaving the app.)  Or that the app should work around it: app isn't doing anything custom on the menu and it's crashing in the bowels of Windows.

Ah, well, workaround is easy enough.

@randyrants fixed then?

@randyrants fixed then?

A supposed workaround was added in #28786, but still made the application crash, so that workaround was removed from it; and thus this issue is still open

@Jay-o-Way The bug is in the bowels of XAML, so I can't fix it.  I did add some code when closing the window that checks to see if the flyout for the textbox is open and then closes it.  Without the check/close I was able to repro this 100% of the time; with it in place, I can't repro it anymore, but @CodingWonders reports it's still a problem.
Not much more I can do with it, at this point.  Have to wait for XAML/WinUI 3 to "accidentally" fix it.

Okay. Then we must search for an issue in the MS XAML repo or create one. The only one that I could find, that looks similar, was https://github.com/microsoft/microsoft-ui-xaml/issues/8365

Officially annoyed by this one.  With Moment 4 bits installed, it's now choking somewhere on a call to FontSize but something is borked with my IDE so I can't even debug it very well so I'm brute-forcing another workaround to get the UI to close without crashing.
I say without embarrassment that this not the worst workaround I've had to perform to workaround a UX with.

Are we sure it's always about the menu? I mean, When I try to reproduce, it only crashes when a file is loaded. It doesn't crash when there's just random text in the Text field.

Are we sure it's always about the menu? I mean, When I try to reproduce, it only crashes when a file is loaded. It doesn't crash when there's just random text in the Text field.

That is the case.

Sorry I haven't mentioned it sooner, but while I was installing earlier versions of PT to see if they contained this issue, I noticed the issue had been there since 0.70 (more exactly, since PR #25535). Version 0.69 seems to not have the issue, as it uses a system title bar instead of a custom one.
I think that, as a viable workaround, we should make an exception to this module and revert the title bar style to the system one. Sure, it will look inconsistent, but at least this issue should be resolved.
If it is, and if calls to external APIs are supported, we can just set the color of the title bar using a simple DWM API function.
And, by the way, this issue also affects the Environment Variables editor in v0.75 when adding a new environment variable.

If the root cause really is somewhere in the TitleBar code, @niels9001 should be aware of this. He's working on a uniform TitleBar element and hopefully we'll see that in PowerToys soon.

It happens whenever the close is attempted with the menu showing:

If no file is loaded, there's no way to bring up the context menu.
If you make a change to the text in the textbox - loaded or unloaded file - you won't see the crash because the popup box that asks about saving your changes will close the context menu, avoiding the crash.
If you load a file, make no changes, and open the context menu, you will see the crash on close.

I cannot confirm where the FontSize error is coming from; nothing else in the callstack looked pointed to what control was throwing up on the call.  Just that that was the property in question.

If no file is loaded, there's no way to bring up the context menu.

That is incorrect. Open the window and right-click to show "paste" option. Issue remains.

That is incorrect. Open the window and right-click to show "paste" option. Issue remains.

OK, so you found a fourth state but I'm not sure how that's helpful.
Are you only testing on the existing released code or did you grab the PR and testing locally?

I've figured out this crash doesn't occur if we turn animations off in Windows.
Looks like it is related to the close animation of the context flyout.
Will open a PR soon.

I've opened an issue upstream here: https://github.com/microsoft/microsoft-ui-xaml/issues/9336

This has been worked on during the 0.79.0 release cycle.
Please update to the latest: https://github.com/microsoft/PowerToys/releases


Revert "Inplace" (#12)

Reverts brain-score/brainio_base#12

revert for now until we can figure out downstream errors (https://github.com/brain-score/brainio_collection/pull/47, https://travis-ci.com/github/brain-score/brain-score/builds/199475744)


[NEW] Support Custom Room Types as "Public Channels" by default

Description
Once custom room types are defined, rooms of this type are not displayed at all in the Android app
Devices and Versions
Your Rocket.Chat.Android version: 2.1.1
Your Rocket.Chat Server version: build 2020
Steps to reproduce
see https://github.com/RocketChat/Rocket.Chat.iOS/issues/1212 . Create a custom room type using the server side API, create a room of this type. It won't be shown neither in the search nor in the chats-list (of subscriptions).
Expected behaviour
The rooms are listed with the particular icon.
Workaround: Define a fallback-icon and just list the rooms as if they were channels. This is the way it's implemented currently in iOS and seemingly in ReactNative as well

Just changed the title of this one... if the channel has anything different from the default behaviour, let's understand it as a public channel, like iOS is doing. This way we allow the user to use the channel.

@luciofm Added the question to the API guys here: https://github.com/RocketChat/Rocket.Chat/issues/11715

What are these "new channel types"? Could someone explain?

@piotrkochan it’s Not about new room types in standard RC. There‘s an API which allows to define custom room types in one‘s own fork. If you do this, those rooms are currently not even listed in the mobile app
Sent with GitHawk

@mrsimpson these apis for channel types registering does not allow custom implementations at server side without custom implementations on mobile apps since it's impossible to define the behavior this new type of channel should have.
Can you explain who you use this custom room type and the room behavior? Then we can discuss better a solution for that.
Thanks

@rodrigok Understood - in general. In our case, we used custom room types for some sort of threading and at the same time providing a dedicated toolset in the tabbar. The behavior was very similar to private groups.
On mobile, there has been a different behavior about subscribed rooms of a custom type on Android and iOS: While they were listable on iOS and behaved like normal rooms, they were totally absent on Android. This issue was about making them at least read- and writable.
I know of other forms with custom room types providing a similar scope (e. g. courses in the educational area).
As you said, the real power of custom rooms only comes with a dedicated mobile UI. In many cases however, the basic need for interaction (writing and reading message) is sufficient when being on the road.
WDYT about introducing metadata on the room types API providing something like inheritance: On the API, one could specify a room type from which the basic behavior (including the mobile one)is being copied (this majorly affects visibility and the power to invite users).
P.s.: We are currently killing our custom room types since this caused complexity and some frustration, particularly because of the rooms not showing up on mobile.

WDYT about introducing metadata on the room types API providing something like inheritance: On the API, one could specify a room type from which the basic behavior (including the mobile one)is being copied (this majorly affects visibility and the power to invite users).

Indeed, I was thinking about this some time ago, to be able to create new types of room but defining the original behavior for compatibility when necessary.

Let's close this issue for now until we've a solution.

@rafaelks usually, if you want to find a solution, you leave issues open until then ;-)

@mrsimpson Well... we don't know if this is actually going to be supported in the core yet, right? I believe that once we know that, we can reopen this issue and add specific information to both iOS and Android. What do you think?

@rafaelks I think that iOS and Android should behave equally (currently, they don’t). And I think there should be some mechanism to at least perform messaging in custom room types on mobile without having to fork all the apps.
Myself and @rodrigok outlined some ideas (e. G. „Inheritance“ or a minimal „only write messages if you are subscribed“).
Sent with GitHawk

@mrsimpson Agreed, also want to support this, but currently there's no way to do that client-side because there's no API to fetch values from custom rooms/subscription from my understanding. The only reason iOS is working different is because the iOS is still using a very old RealTime method to fetch messages, but this is going to change in near future, where we're going to change the implementation to use the same methods that Android is using.
What about we find a mid-term solution? One idea would be having a custom.* API for any kind of custom rooms... this way we don't break compatibility with current clients and in the next API we think about something "unified".

The question is how those custom room types behave. Who can see them, who can write or add users? Imho, this should be somewhat described, so that the apps can interpret this data. As I said, being able to message in subscribed rooms is key, the rest is kind-of-bonus


Completable future for random teleports

Please re-add completable futures into RandomTeleportEngine

I've done this; my pr self-superceeds this; closing


Dart Language Binding

Check out this video: https://www.youtube.com/watch?v=iPlPk43RbpA
I think Dart would make a great language for binding to Godot in addition to C#.  Hot Reloading of anything and everything could be a killer feature of Godot.  Thoughts?

I think, Godot already has same feature, named as "Sync Scene/Script Changes"

I'd say, we would glady have this as 2.2 (now 3.0) was poised to be the "languages release" anyway. So, whoever overenergetic, adventurous person wants to try doing it is welcome to integrate it as a module.

let's make Google pay for it :P
On Sun, Jan 22, 2017 at 9:36 AM, Bojidar Marinov<EMAIL_ADDRESS>wrote:

I'd say, we would glady have this as 2.2 (now 3.0) was poised to be the
"languages release" anyway. So, whoever overenergetic, adventurous person
wants to try doing it is welcome to integrate it as a module.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/7607#issuecomment-274328345,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z23yprdUD79QHIlz9MeaBvxf88drNks5rU01QgaJpZM4LqR6T
.

While I've been a huge advocate for adding more languages, I want to be clear that none of them should actually be a part of the core engine/editor. In fact, I believe doing so would be an enormous mistake, as it implies that Godot should be responsible for them. Additional languages should be able to exist as separate repositories, as community efforts.
Again, I am VERY much in favor of supporting more scripting languages. I have been one of the most vocal about it (see #7598 and https://github.com/godotengine/godot/issues/937#issuecomment-269876297 and IRC). But all effort that should be taking place inside the Godot code should be towards supporting arbitrary languages, and the community should take it from there in their own repositories. Many engines that do not do this are heavily encumbered by the decision, as they now have to support everything and test everything with every release. It completely kills the progress of what matters most, the engine.

Good response, I guess you can close this down now. I am glad I asked about this, it makes me like Godot even more =)

Yeah, closing. If you ever get done'/almost-done with it, you might tell us, and we might mention it in the docs, or have a few official binaries bundled with it (depends). :smiley:

Is anyone interested in pursuing this?

Yeah !!

i started working on it :
https://github.com/mahdisml/DartGodot


feat: support range expr parse

Synchronize sqlparser-rs version to v0.38.0 .
Modify the DFConvert macro implementation to provide clearer error messages.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

189 of 242 (78.1%)  changed or added relevant lines in 5 files are covered.
905 unchanged lines in 12 files lost coverage.
Overall coverage decreased (-4.0%) to 83.228%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/keywords.rs
1
3
33.33%

src/ast/value.rs
18
22
81.82%

src/ast/mod.rs
0
16
0.0%

src/parser/mod.rs
161
192
83.85%

Files with Coverage Reduction
New Missed Lines
%

src/ast/dcl.rs
2
88.14%

src/ast/helpers/stmt_data_loading.rs
2
88.1%

src/ast/operator.rs
2
91.67%

src/ast/data_type.rs
3
78.98%

src/ast/value.rs
10
78.36%

src/ast/ddl.rs
11
79.62%

src/ast/visitor.rs
12
16.67%

src/tokenizer.rs
28
86.36%

src/lib.rs
33
11.55%

src/ast/mod.rs
34
76.8%

Totals

Change from base Build<PHONE_NUMBER>:
-4.0%

Covered Lines:
16589

Relevant Lines:
19932

💛  - Coveralls


crackxls: Fix build on staging

$out doesn't exist by default, so need to use 'mkdir -p'. More #7524.
While at it, patch out some evil optimization flags.

@pSub beat us to it: https://github.com/NixOS/nixpkgs/commit/f0c00accd46479a95518fa91f0f1a258a6f74b41
I guess the 'native' issue can be fixed in master directly. Do you want to create a pr for it?

I think nixpkgs should use neither -march=native nor -mtune=native in the default setup, especially when it's also built on Hydra (it is in this case).

@vcunat right, so the patch of @dezgeg is fine, right?

Oh, right, I'm sorry. I misread it to replace -march by -mtune.

I have applied @dezgeg 's patch in  3c47a9980c43c51c65ae4a6ba87d2c252612ff5c.

Ok, great!


afterInsert is not called if the data is not array

It seems afterInsert is only called when the data is an array. afterInsert is not called if the data is a javascript object.

Seems to work for me, can you provide me with an example that is failing?

The key point is that, use loadTemplate to load some array into the container, then use loadTemplate to append some object into the same container, and afterInsert didn't get called.
I have attached an example.
jqueryTemplateProblem.zip

My testing shows this is fixed in the latest version from the example you have given. Will close unless you can provide an example that still doesn't work.


Connect my Vega wallet

Task
As a user I would like to connect my Vega wallet
Notes:
Some work has been done in the PoC, this is going to need tests writing
AC

[ ] Provide simple explanation on how to create a vegawallet network using the desktop app or cli
[ ] Provide simple explanation on how to deposit money into the wallet
[x] The user can use multiple keys in their wallet


Could you please clarify the license?

Could you please clarify the license?

Our license is Apache-2.0 license, the same as Threestudio.
I've added the LICIENSE to this repo. Thank you for reminding me!


Fix pytest.fail msg in fail_obj_graph

References and relevant issues
#6842
Description
This was amended in #6842 but pytest.fail msg needs to be a string.
Noted in failed CI: https://github.com/napari/napari/actions/runs/8932333235/job/24536346859?pr=6848#step:12:520
from #6848 :
               # DO not remove len, this can break as C++ obj are gone, but python objects
              # still hang around and _repr_ would crash.
  >           pytest.fail(len(Klass._instances))
  E           TypeError: Failed expected string as 'msg' parameter, got 'int' instead.
  E           Perhaps you meant to use a mark?

Thanks @Czaki https://github.com/napari/napari/pull/6899 is better, closing.


Fix(card-group): Image height of the last card

Related Ticket(s)
React: Card section - images: image height of the last card #4810
Description
The image on the last card is 1px taller. This happens because the right padding is removed on the last card to hide the dark border. The missing padding allows the image to be 1px taller.
Changelog
Changed

`_card-group.scss to fix the height

Thank you (yes, my first) and I agree @asudoh, it felt kind of hacky. All the other solutions I came up with required modifying the HTML structure, but let me try to figure out a different (CSS only) solution.

Thank you (yes, my first) and I agree @asudoh, it felt kind of hacky. All the other solutions I came up with required modifying the HTML structure, but let me try to figure out a different (CSS only) solution.

Pushed a new CSS only approach (No more % height calculation). I added the padding that was removed from the last card to another spot of the card so that there won't be any missing padding that will affect the image height. This will only apply to the last card.


Glossary Term on Dataset Columns doesn't show in Related Entities

Describe the bug
When you add Glossary Terms to a Dataset column, the Dataset does not appear in the Related Entities tab of the Glossary Term.
To Reproduce
Steps to reproduce the behavior:

Go to Dataset page
Add a glossary term to a column
View the glossary term profile page
View that related entities does not contain the dataset from step 1

Expected behavior
Show the dataset in the related entities tag
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This issue has been fixed!


Build env testing

Lets see if we can coax Jenkins back into happiness.

#rebuild

#rebuild

Yay, all seems to be good now :dancers:


Cannot navigate "back" out of block spotlight

Once in a block spotlight, one cannot exit by going back.

Thanks for logging this, I had to recently fix a similar issue on another page.

I'm not able to reproduce this by visiting and back navigating. Could you give me your use case?

Block spotlight back navigation is working now, but account spotlight back navigation is not.

Unable to reproduce


Remove the attempt to grab msg and message from exceptions

Not all exceptions have .msg or .message. If we don't find either we should just reraise the exception. It clouds tracebacks when we this occurs making it tough for users to know what's going on.

protip: most of the exception embed the message in their str magic method.
Therefore this is approach is usually preferred:
str(error)

In the worst case it will fallback to the Python default object implementation.


emit Null into JSON if field is nil

Thanks @traylewin, I have made some changes and additions to your PR. See #697
I will be merging that soon so I am closing this.


Readme.md needs clearer split between MacOS and Linux paths

Refactor the Readme.md to better guide users down either the MacOS path or the Linux path. As one reviewer put it, be "less abrupt."

Replaced by issue #382


Application.Exit() doesn't work if app doesn't have any windows open

Describe the bug
While trying to implement single instance redirection, I noticed that the Exit() API doesn't work unless the app has windows open. In the case of redirecting activation, after redirecting the activation, the second instance needs to be closed (without ever showing any windows). But calling Exit() doesn't do anything, the process stays running...
Steps to reproduce the bug

Steps to reproduce the behavior:

Create a new WinUI 3 Desktop app, and in OnLaunched, update it to the following (exits itself after 6 seconds and never shows window)...

Launch the app
Open Task Manager, and notice that the process is still running (under background processes) after 6 seconds and never exits

Expected behavior
App should exit. The Exit() API works if there's an open activated window when it's called, but doesn't work when there's no open window.
Version Info

NuGet package version:
[WinUI 3 - Windows App SDK 1.0.0-preview1

Windows app type:

UWP
Win32

Yes

Windows version
Saw the problem?

Insider Build (xxxxx)
Yes

May 2021 Update (19043)

October 2020 Update (19042)

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context

Workaround is to use Process.GetCurrentProcess().Kill().

This seems to have worked in 0.8.5 - I noticed this behavior when upgrading to 1.0.0

Thanks for posting this error. I found the problem and fixed it internally. Should come up in some future release. This bug will close automatically with that.

This issue still happens with WinUI 3

Thanks for posting this error. I found the problem and fixed it internally. Should come up in some future release. This bug will close automatically with that.

May I know if this issue has been fixed and deployed in any release? Is it included in 1.3-experimental?

I just checked. Sadly, it missed the mark for experiemental. I will check again to see if we will do another set of spot fixes for 1.3. Else, it will be part of next release.

I just checked. Sadly, the commit with the fix missed the bus for experiemental fork :). I will check again to see if we will do another set of spot fixes for 1.3 (@bpulliam ). Else, it will be part of next release.

Thanks!

Yes, hopefully the next version release of winappsdk

Can I just ask why is this issue still not fixed? We are now in STABLE 1.3 of WASDK.

I tested this on WASDK 1.3 and seems to be working as expected.

oh, did it make it in ? i need to check again.


Slider doesn't work on Android Navigation Drawer

Environment

Description
I've got a brightness slider on my app'ss navigation drawer, I'm able to use it without any issues on iOS but the slider itself doesn't work on Android.
On Android, the slider only works when dragged with two fingers, tap to seek also works.
However when I try dragging using one finger it doesn't work.
I've created a snack below to reproduce this issue, any ideas what might be causing this?
Reproducible Demo
Here's a snack I created, you can try it on the android emulator.

Hello @nishmeht7, thank you for reporting that and providing me with an example.
Two fingers are required to slide the <Slider/> on the Android when Accessibility is turned on, but I don't see it in the provided example of yours.
Second thing that comes to my mind is the issue with parent scrolled element consuming the sliding on <Slider/>, just like #296.
I will try to take a deeper look into that.

@nishmeht7 Hi, I guess is gueture problem. You can try react-native-awesome-slider, sliding is disable other gesture.

Its a gesture problem, the drawer gesture is overriding the slider gesture


Contact: email addresses are down

Both the email addresses, one on the GitHub organization and one on the website, are down.

What do you mean by them being down - are you getting email bounces?  Can you post any error?


How to test the Model ?

I would like to test the model with the Sample datasets.

The search returns the best found net as a Keras model. You can test this in any way you'd like as you normally would with Keras.


[MXNET-1093] Add python3 Docker images for each MXNet release

Description
@KellenSunderland @marcoabreu @gautamkmr
This PR updates the docker/docker-python folder to add 8 new dockerfiles for python3. It also updates the automated docker release script to build and update the python 3 docker images similar to python 2.
Python version used is 3.5 which is the default version on ubuntu 16.04.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Added 8 new dockerfiles for python 3 - cpu, cu80, cu90, cu92 with and without mkl.
[x] Updated the build script to also build, test and upload these new dockerfiles
[x] Updated the readme.

Yea.

@marcoabreu It seems that your review comments has been addressed. Could you please take a look?

@marcoabreu @sandeep-krishnamurthy Could either of you please merge this PR. Thanks!

Please wait with merging. I'm still discussing some things internally

Thanks for this effort. I have some reservations about the implementation, see my previous comment about zombie containers and resource disposal in the code.
Also, can we use Python instead of shell to automate these steps? It's more robust, debuggable, flexible and easier to mantain, we don't want to introduce complex logic in shell scripts.
All the automation on the project is done in Python. The code that is forking process to parallelize the build should be done as it's done in https://github.com/apache/incubator-mxnet/blob/master/ci/docker_cache.py or with a similar Python construct of your choice. Even if it's not critical to parallelize building of the images, if the code is well factored and building the container it's on its own function is very easy to parallelize.

@mbaijal Could you please look into comments provided by @lanking520 and @marcoabreu

Thanks for your contributions @mbaijal
@mxnet-label-bot update [pr-awaiting-review]
@larroy ,  @marcoabreu could you please help with reviewing this PR?

@mbaijal could you check the CI build failure and add a comment explaining the changes you made/are making in response to Pedro and Marco's feedback?
@mxnet-label-bot update [CI, Docker, pr-awaiting-testing]

Given that we are taking over this script, shall we close this?

@perdasilva

@larroy - let's close it. I'll open a new PR after my RFC goes through

@perdasilva it's meghnas PR, @mbaijal can you close?  Thanks.

I don't mind closing this but half of the code for this change (python2 and initial automation script) has already been merged in a previous PR and this PR contains some updates and fixes to it. This updated script was also used for the last two docker releases. In my opinion it might be better to merge this PR to complete those changes and then deprecate it when a new python script is available.

@mbaijal imo, in this case, we should probably go fwd and merge. @larroy?

@larroy Is it okay if we merge this PR?
@nswamy @marcoabreu

Please hold on with this PR since we are currently refactoring that pipeline.
@perdasilva for further communication regarding this topic

up to @perdasilva

@marcoabreu lets talk about this issue today and come up with the solution. If the PR does what someone needs right now, I don't see any reason to hold this back. We can always refactor it later if need be...

@mbaijal @sandeep-krishnamurthy @srochel  please merge this - thank you

Thanks @perdasilva !


graphics: Deprecate (*Image).Dispose

Not determined yet.

This would require more preparation.

Note to myself. Due to Dispose, we cannot make an optimization to return the same image at SubImage with the same bounds. It's because disposing the sub-image would affect the original image, which is not expected.

Close % #2808


Upgrade to Windows-2022

windows-latest workflows will use windows-2022 soon. For more details see: actions/virtual-environments#4856
Steps

[x] Read actions/virtual-environments#4856
[ ] Pin Windows-2022 (by merging)

windows-latest workflows will use windows-2022 soon. For more details see: actions/virtual-environments#4856
Steps

[x] Read actions/virtual-environments#4856
[ ] Pin Windows-2022 (by merging)

windows-latest now pins to windows-2022


Slide opens when zooming / pinching on phone

Hey & thanks for this great library!
When zooming in on something on a phone (like an image), the slide opens automatically on our site ( www.Saburly.com ) which destroys the UX. Are you experiencing the same issue & any ideas on how to solve it?

I'm running into this too, did you find a solution @Bobeta?

Try this meta tag; <meta name="viewport" content="width=device-width, user-scalable=no" />

+1

found this and works greate :
panel.addEventListener('touchstart', function(eve) {
     let offset = eve.touches[0].pageX;

     if (slideout._orientation !== 1) {
         offset = window.innerWidth - offset;
     }

     slideout._preventOpen = slideout._preventOpen || (offset > slideout._tolerance && !slideout.isOpen());
 });


checkbox group some problem

Hello!
Why the error, if one item is marked?

@version 1.5.2 (2015-02-18)

Maybe,  It's problem if select has no focuse or no selected?

Hey Tuning-Soft,
I have indeed not fully tested the checkboxes (if multiple) and the multi select... there might be a problem there as you mentionned. I am currently unavailable to do the fixes on my side for at least 1 week.
If you want to work on a patch and submit it I will gladly review / merge the modifications.
Thanks.

All ok, i'm wait!
I'm PHP proger, not jQuery, but somthing i can))
I'll try and accomplish your goal, if possible, thank you for your cool plugin, good luck!)

I wanted to say that in jQuery I'm a full loser!!!)

Haha no worries, I'll check that out next week


Is there a way to hide routes in index.html?

Hi @erikringsmuth,
This app-router is awesome. However I just want to ask if there's a way to hide the routes inside index.html. The routes are exposed when inspecting the code.

Thanks.

I'm closing this as there really isn't any way to hide routes unless you use a pure JS router. That may be the way things go if Polymer ends up adopting ES6 modules in the end. We'll have to wait and see.


Potential 0.40.0 regression on Github Actions runners

Poential 0.40.0 regression in Github Actions CI/CD
I tried to fill out the form, but it's quite hard as most things simply don't run.
Here is a set of test workflows that show the regression.
Operating system and version:
Ubuntu 22.04
(Github Runner version 20240804.1.0)
nvm debug output:

# Impossible to run directly

nvm ls output:

# Impossible to run directly

How did you install nvm?
Pre-installed on Github Runner
What steps did you perform?
cat .nvmrc
source ~/.nvm/nvm.sh && nvm install

What happened?
Received output:
18
Error: Process completed with exit code 3.

What did you expect to happen?
Install of the node version specified in .nvmrc (18)
Is there anything in any of your profile files that modifies the PATH?

I don't think so. It's a fresh Github Action runner

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?
Please see workflow runs for demonstration of the apparent regression,

curl -I --compressed -v https://nodejs.org/dist/
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying <IP_ADDRESS>:443...
* Connected to nodejs.org (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS header, Certificate Status (22):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.2 (IN), TLS header, Finished (20):
{ [5 bytes data]
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [19 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [4835 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [520 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.2 (OUT), TLS header, Finished (20):
} [5 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=*.nodejs.org
*  start date: Feb 28 00:00:00 2024 GMT
*  expire date: Mar 30 23:59:59 2025 GMT
*  subjectAltName: host "nodejs.org" matched cert's "nodejs.org"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0x56543f0b8e20)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
> HEAD /dist/ HTTP/2
> Host: nodejs.org
> user-agent: curl/7.81.0
> accept: */*
> accept-encoding: deflate, gzip, br, zstd
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [230 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [230 bytes data]
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
< HTTP/2 200
< date: Thu, 08 Aug 2024 12:30:09 GMT
< content-type: text/html
< cache-control: public, max-age=3600, s-maxage=14400
HTTP/2 200
date: Thu, 08 Aug 2024 12:30:09 GMT
content-type: text/html
cache-control: public, max-age=3600, s-maxage=14400
last-modified: Thu, 08 Aug 2024 11:05:18 GMT
cf-cache-status: HIT
age: 4469
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-content-type-options: nosniff
server: cloudflare
cf-ray: 8aff841c88317d52-LAX
content-encoding: br

< last-modified: Thu, 08 Aug 2024 11:05:18 GMT
< cf-cache-status: HIT
< age: 4469
< vary: Accept-Encoding
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< x-content-type-options: nosniff
< server: cloudflare
< cf-ray: 8aff841c88317d52-LAX
< content-encoding: br
<

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* Connection #0 to host nodejs.org left intact
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

Do you set -e anywhere? Can you try those test workflows with set -x set?

Here's a similar actions failing - i've added set -x https://github.com/matthewhilton/moodle-plugin-ci/actions/runs/10314237668/job/28552324807
Full output:

```
RUN  set -x && . /home/runner/.nvm/nvm.sh && nvm install && nvm use && echo "NVM_BIN=$NVM_BIN"
+ . /home/runner/.nvm/nvm.sh
+ NVM_SCRIPT_SOURCE=/home/runner/work/moodle-plugin-ci/moodle-plugin-ci/bin/moodle-plugin-ci
+ [ -z  ]
+ export NVM_CD_FLAGS=
+ nvm_is_zsh
+ [ -n  ]
+ [ -z /home/runner/.nvm ]
+ unset NVM_SCRIPT_SOURCE
+ nvm_process_parameters
+ local NVM_AUTO_MODE
+ NVM_AUTO_MODE=use
+ [ 0 -ne 0 ]
+ nvm_auto use
+ local NVM_MODE
+ NVM_MODE=use
+ local VERSION
+ local NVM_CURRENT
+ [ _use = _install ]
+ [ _use = _use ]
+ nvm_ls_current
+ local NVM_LS_CURRENT_NODE_PATH
+ command which node
+ NVM_LS_CURRENT_NODE_PATH=/usr/local/bin/node
+ nvm_version_dir iojs
+ local NVM_WHICH_DIR
+ NVM_WHICH_DIR=iojs
+ [ -z iojs ]
+ [ iojs = new ]
+ [ _iojs = _iojs ]
+ nvm_echo /home/runner/.nvm/versions/io.js
+ command printf %s\n /home/runner/.nvm/versions/io.js
+ nvm_tree_contains_path /home/runner/.nvm/versions/io.js /usr/local/bin/node
+ local tree
+ tree=/home/runner/.nvm/versions/io.js
+ local node_path
+ node_path=/usr/local/bin/node
+ [ @/home/runner/.nvm/versions/io.js@ = @@ ]
+ [ @/usr/local/bin/node@ = @@ ]
+ local previous_pathdir
+ previous_pathdir=/usr/local/bin/node
+ local pathdir
+ dirname /usr/local/bin/node
+ pathdir=/usr/local/bin
+ [ /usr/local/bin !=  ]
+ [ /usr/local/bin != . ]
+ [ /usr/local/bin != / ]
+ [ /usr/local/bin != /home/runner/.nvm/versions/io.js ]
+ [ /usr/local/bin != /usr/local/bin/node ]
+ previous_pathdir=/usr/local/bin
+ dirname /usr/local/bin
+ pathdir=/usr/local
+ [ /usr/local !=  ]
+ [ /usr/local != . ]
+ [ /usr/local != / ]
+ [ /usr/local != /home/runner/.nvm/versions/io.js ]
+ [ /usr/local != /usr/local/bin ]
+ previous_pathdir=/usr/local
+ dirname /usr/local
+ pathdir=/usr
+ [ /usr !=  ]
+ [ /usr != . ]
+ [ /usr != / ]
+ [ /usr != /home/runner/.nvm/versions/io.js ]
+ [ /usr != /usr/local ]
+ previous_pathdir=/usr
+ dirname /usr
+ pathdir=/
+ [ -n  ]
+ local NVM_DIRS_TO_SEARCH1
+ NVM_DIRS_TO_SEARCH1=
+ local NVM_DIRS_TO_SEARCH2
+ NVM_DIRS_TO_SEARCH2=
+ local NVM_DIRS_TO_SEARCH3
+ NVM_DIRS_TO_SEARCH3=
+ local NVM_ADD_SYSTEM
+ NVM_ADD_SYSTEM=false
+ nvm_is_iojs_version lts/gallium.
+ return 1
+ [ lts/gallium. = node- ]
+ NVM_DIRS_TO_SEARCH1=/home/runner/.nvm
+ NVM_DIRS_TO_SEARCH2=/home/runner/.nvm/versions/node
+ NVM_DIRS_TO_SEARCH3=/home/runner/.nvm/versions/io.js
+ nvm_has_system_iojs
+ nvm deactivate
+ command -v iojs
+ [  !=  ]
+ nvm_has_system_node
+ nvm deactivate
+ command -v node
+ [ /usr/local/bin/node !=  ]
+ NVM_ADD_SYSTEM=true
+ [ -d /home/runner/.nvm ]
+ command ls -1qA /home/runner/.nvm
+ nvm_grep -q .
+ GREP_OPTIONS= command grep -q .
+ [ -d /home/runner/.nvm/versions/node ]
+ NVM_DIRS_TO_SEARCH2=/home/runner/.nvm
+ [ -d /home/runner/.nvm/versions/io.js ]
+ NVM_DIRS_TO_SEARCH3=/home/runner/.nvm
+ local SEARCH_PATTERN
+ [ -z lts/gallium. ]
+ nvm_echo+ command sed s#\.#\\\.#g;
 lts/gallium.
+ command printf %s\n lts/gallium.
+ SEARCH_PATTERN=lts/gallium\.
+ [ -n /home/runner/.nvm/home/runner/.nvm/home/runner/.nvm ]
+ command find /home/runner/.nvm/CODE_OF_CONDUCT.md /home/runner/.nvm/CONTRIBUTING.md /home/runner/.nvm/Dockerfile /home/runner/.nvm/GOVERNANCE.md /home/runner/.nvm/LICENSE.md /home/runner/.nvm/Makefile /home/runner/.nvm/PROJECT_CHARTER.md /home/runner/.nvm/README.md /home/runner/.nvm/ROADMAP.md /home/runner/.nvm/alias /home/runner/.nvm/bash_completion /home/runner/.nvm/install.sh /home/runner/.nvm/nvm-exec /home/runner/.nvm/nvm.sh /home/runner/.nvm/package.json /home/runner/.nvm/rename_test.sh /home/runner/.nvm/test /home/runner/.nvm/update_test_mocks.sh /home/runner/.nvm/CODE_OF_CONDUCT.md /home/runner/.nvm/CONTRIBUTING.md /home/runner/.nvm/Dockerfile /home/runner/.nvm/GOVERNANCE.md /home/runner/.nvm/LICENSE.md /home/runner/.nvm/Makefile /home/runner/.nvm/PROJECT_CHARTER.md /home/runner/.nvm/README.md /home/runner/.nvm/ROADMAP.md /home/runner/.nvm/alias /home/runner/.nvm/bash_completion /home/runner/.nvm/install.sh /home/runner/.nvm/nvm-exec /home/runner/.nvm/nvm.sh+  /home/runner/.nvm/package.json /home/runner/.nvm/rename_test.sh /home/runner/.nvm/test /home/runner/.nvm/update_test_mocks.sh /home/runner/.nvm/CODE_OF_CONDUCT.md /home/runner/.nvm/CONTRIBUTING.md /home/runner/.nvm/Dockerfile /home/runner/.nvm/GOVERNANCE.md /home/runner/.nvm/LICENSE.md /home/runner/.nvm/Makefile /home/runner/.nvm/PROJECT_CHARTER.mdcommand /home/runner/.nvm/README.md sed /home/runner/.nvm/ROADMAP.md -e /home/runner/.nvm/alias /home/runner/.nvm/bash_completion
            s#/home/runner/.nvm/versions/io.js/#versions/iojs/#;
            s#^/home/runner/.nvm/##;
            \#^[^v]# d;
            \#^versions$# d;
            s#^versions/##;
            s#^v#node/v#;
            \#lts/gallium\.# !d;
           /home/runner/.nvm/install.sh -e /home/runner/.nvm/nvm-exec s#^\([^/]\{1,\}\)/\(.*\)$#\2.\1#; /home/runner/.nvm/nvm.sh
 /home/runner/.nvm/package.json /home/runner/.nvm/rename_test.sh /home/runner/.nvm/test /home/runner/.nvm/update_test_mocks.sh -name . -o -type d -prune -o -path lts/gallium.*
+ command sed -e s#\(.*\)\.\([^\.]\{1,\}\)$#\2-\1#; -e s#^node-##;
+ command sort -t. -u -k 1.2,1n -k 2,2n -k 3,3n
+ VERSIONS=
+ [ true = true ]
+ [ -z lts/gallium. ]
+ [ lts/gallium. = v ]
+ [ lts/gallium. = system ]
+ [ -z  ]
+ nvm_echo N/A
+ command printf %s\n N/A
+ return 3
+ VERSION=N/A
+ [ -z N/A ]
+ [ _N/A = _N/A ]
+ nvm_echo N/A
+ command printf %s\n N/A
+ return 3
+ VERSION=N/A
+ unset NVM_RC_VERSION
+ [ -z N/A ]
+ [ -z N/A ]
+ [ 0 -eq 1 ]
+ [ _N/A = _system ]
+ [ _N/A = _∞ ]
+ [ N/A = N/A ]
+ [ 1 -ne 1 ]
+ return 3
```

I wonder if the different is that your projects might have .nvmrc but ours don't ?

Adding onto my previous comment, I think there might be a bug / edge case with .nvmrc handling.
In my github action I did echo .nvmrc and saw it had lts/iron i.e. 20.9.0.
I tried overwriting this with the latest lts 20.16.0 but the same error.
Lastly I tried removing the nvmrc file entirely, and using nvm install 20.16.0 and nvm use 20.16.0 which worked and node installed properly.

hmm, it looks like it's getting lts/gallium. - note the trailing period - from somewhere. is that perhaps in your nvmrc?

Adding onto my previous comment, I think there might be a bug / edge case with .nvmrc handling.
In my github action I did echo .nvmrc and saw it had lts/iron i.e. 20.9.0.
I tried overwriting this with the latest lts 20.16.0 but the same error.
Lastly I tried removing the .nvmrc file entirely, and using nvm install 20.16.0 and nvm use 20.16.0 which worked and node installed properly.
The final working command for reference: rm .nvmrc && . $nvmDir/nvm.sh && nvm install 20.16.0 && nvm use 20.16.0

The issue is definitely happening only when there is an .nvmrc present. I ran bash in debug mode (-xv), and I believe it was failing when trying to parse it.
It seems that 0.40.0 added comments support to .nvmrc, so it sounds like it might be a regression root (not confident).
I will add -xv back post the output when I'm back to this.

Do you set -e anywhere? Can you try those test workflows with set -x set?
(fwiw, i use nvm 0.40.0 in my own ljharb/actions, which runs on 500 of my projects, and these don't fail, so I'm trying to figure out what might have changed here)

I've added -xv to the bash in Github Actions Workflow

Do you set -e anywhere? Can you try those test workflows with set -x set?
(fwiw, i use nvm 0.40.0 in my own ljharb/actions, which runs on 500 of my projects, and these don't fail, so I'm trying to figure out what might have changed here)

I don't think I use -e anywhere (see the test workflow I've created to reproduce this issue.  Since it's set with no action from you, telling you that it's a bad idea to set that option does no good :-) so I'll see if I can figure out how to cover this scenario.
The github action workflow was and will be very helpful here, both for repro, investigation, and later for a regression test.

@AutomationD yeah, you're misreading it - that's just a predicate to determine if v18 is an iojs version (which it's not, ofc).

ok, so the default options in that workflow are ehB, which means there's some change in v0.4.0 that breaks with set -e usage. Since it's set with no action from you, telling you that it's a bad idea to set that option does no good :-) so I'll see if I can figure out how to cover this scenario.
The github action workflow was and will be very helpful here, both for repro, investigation, and later for a regression test.

Great find, thanks for looking into it!
At this point I'll be locking my nvm workflows and a wrapper using nvm to version 0.39.7. But if any of my tests show any answers to your question I'll report back.

ok, some bisecting suggests the issue was introduced in #2869: https://github.com/ljharb/ize/actions/runs/10328344009
I've got a fix; I'll adapt the workflows into a regression test tomorrow, and then I can land and release this.

I ran into this issue and spent a while narrowing it down to the nvm version before finding this thread, but here's my regression workflow that shows some difference between v0.39.7 and v0.40.0 was the culprit (testing all between the current version in use on the runner, and the previous version in use by the runner, v0.39.5)
name: Test NVMs NVM_DIR on ubuntu-latest
on:
  workflow_dispatch:
defaults:
  run:
    shell: bash
env:
  UNAUTO_NODE_VERSION: v18.18.2 # "NODE_VERSION" is read by the nvm install script.
  SETX: "false"
jobs:
  nvmrc-present-older-nvm:
    strategy:
      fail-fast: false
      matrix:
        nvm-version: ['v0.39.5', 'v0.39.6', 'v0.39.7', 'v0.40.0']
    runs-on: ubuntu-latest
    steps:
    - run: curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/${{ matrix.nvm-version }}/install.sh | bash
    - run: echo "$UNAUTO_NODE_VERSION" > .nvmrc
    - if: env.SETX == 'true'
      run: source <(echo "set -x"; cat $NVM_DIR/nvm.sh; echo "set +x") && nvm install $(cat .nvmrc)
    - if: env.SETX != 'true'
      run: source $NVM_DIR/nvm.sh && nvm install $(cat .nvmrc)
  nvmrc-present-default-nvm: # v0.40.0 atm
    runs-on: ubuntu-latest
    steps:
    - run: echo "$UNAUTO_NODE_VERSION" > .nvmrc
    - if: env.SETX == 'true'
      run: source <(echo "set -x"; cat $NVM_DIR/nvm.sh; echo "set +x") && nvm install $(cat .nvmrc)
    - if: env.SETX != 'true'
      run: source $NVM_DIR/nvm.sh && nvm install $(cat .nvmrc)
  nvmrc-absent-default-nvm: # v0.40.0 atm
    runs-on: ubuntu-latest
    steps:
    - run: source $NVM_DIR/nvm.sh && nvm install $UNAUTO_NODE_VERSION

I ran into this issue and spent a while narrowing it down to the nvm version before finding this thread, but here's my regression workflow that shows some difference between v0.39.7 and v0.40.0 was the culprit (testing all between the current version in use on the runner, and the previous version in use by the runner, v0.39.5)
name: Test NVMs NVM_DIR on ubuntu-latest
on:
  workflow_dispatch:
defaults:
  run:
    shell: bash
env:
  UNAUTO_NODE_VERSION: v18.18.2 # "NODE_VERSION" is read by the nvm install script.
  SETX: "false"
jobs:
  nvmrc-present-older-nvm:
    strategy:
      fail-fast: false
      matrix:
        nvm-version: ['v0.39.5', 'v0.39.6', 'v0.39.7', 'v0.40.0']
    runs-on: ubuntu-latest
    steps:
    - run: curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/${{ matrix.nvm-version }}/install.sh | bash
    - run: echo "$UNAUTO_NODE_VERSION" > .nvmrc
    - if: env.SETX == 'true'
      run: source <(echo "set -x"; cat $NVM_DIR/nvm.sh; echo "set +x") && nvm install $(cat .nvmrc)
    - if: env.SETX != 'true'
      run: source $NVM_DIR/nvm.sh && nvm install $(cat .nvmrc)
  nvmrc-present-default-nvm: # v0.40.0 atm
    runs-on: ubuntu-latest
    steps:
    - run: echo "$UNAUTO_NODE_VERSION" > .nvmrc
    - if: env.SETX == 'true'
      run: source <(echo "set -x"; cat $NVM_DIR/nvm.sh; echo "set +x") && nvm install $(cat .nvmrc)
    - if: env.SETX != 'true'
      run: source $NVM_DIR/nvm.sh && nvm install $(cat .nvmrc)
  nvmrc-absent-default-nvm: # v0.40.0 atm
    runs-on: ubuntu-latest
    steps:
    - run: source $NVM_DIR/nvm.sh && nvm install $UNAUTO_NODE_VERSION

Welcome to the family 🤗
Hopefully @ljharb will release a fix soon.

Prior to some fix that may take some time to percolate onto the runner (and not wanting to frob the installed version), besides swalling any other arbitrary error, is temporarily renaming the .nvmrc the only solution or is there some way to manipulate it during sourcing that prevents that check?

Prior to some fix that may take some time to percolate onto the runner (and not wanting to frob the installed version), besides swallowing any other arbitrary error, is temporarily renaming the .nvmrc the only solution or is there some way to manipulate it during sourcing that prevents that check?

The only workaround I know is downgrading to v0.39.7 before calling nvm via something like:
bash -c "curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash"

The trivial workaround in the meantime is set +e before sourcing nvm.sh.

My solution was to remove NVM from ~/.bash_profile, since our workflows involve adding helper functions which are loaded and used in later workflow steps. 😢

My solution was to remove NVM from ~/.bash_profile, since our workflows involve adding helper functions which are loaded and used in later workflow steps. 😢
Exit code 3 was not great.

How did you use nvm without having it in the bash profile though?

Unfortunately set -e is itself fragile, and shouldn't be set, but is still very widely used and erroneously understood.
I was able to create solid regression tests, but they exposed they my fix wasn't complete, and I'm still working on that fix.

got it! I'm going to try to squeeze in one more bugfix, and I'll have a patch release out tomorrow.


DWF Management Board Update

The section "DWF Management Board" in the readme file may now refer to the new General-Information (to avoid duplicate info/inconsistencies...)

Fixed by @kurtseifried with commit a2f7b4ce3383be0ae1dafa82533b8cbeb3478237


How to set heading — h2 and subheading — h3?

@anthonyjb How to set default heading to <h2> and subheading to <h3>?

Hi @SimBioT1954,
This is something I typically do on sites also, it can be achieved as follows:
ContentTools.Tools.Heading.tagName = 'h2';
ContentTools.Tools.Subheading.tagName = 'h3';

Thanks! @anthonyjb


Update FingerprintJS Pro agent and add playground

:tada: This PR is included in version 0.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


aio_read doing synchronous stat when size parameter is null

When calling aio_read() with a null size parameter, the module will call rados_stat() to get the object size and set size to the size of the object.
https://github.com/ksperis/node-rados/blob/master/rados.cc#L619-L630
This effectively turn the asynchronous aio_read call to be synchronous (that is the rados_stat() call is synchronous). Instead, the size parameter should be mandatory and an error should be returned, or the size could also default to DEFAULT_BUFFER_SIZE (defined in rados.h).

Yes it's true, if the size is not specified, the async is only partial because of use of rados_stat() is synchronous. However, it permit to read a full object (Anyway asynchronously) without knowing its size. Another possibility would be to make an asynchronous call to rados_stat().
Meanwhile, it would be wise to make this clear in the documentation or examples.

I looked at doing an asynchronous stat call, but that is not provided by librados so we would need to have our own NanAsyncWorker to do this (which requires a bit more work).
I think if someone wanted to do a full async read in a single call they should manually do a (blocking) ioctx.stat call first to get the length they want to read.
But another problem in the way full read are currently implemented (sync or async) is that it assumes the object doesn't change between the stat call and the read call. I think it would be better to read until EOF is reached, instead of using a stat.

Yes I understand what you mean. But I'm not sure that there is the notion of EOF in librados for a complete reading.
Otherwise, we can also specify a default size for reading, per example python has default length set to 4096 for sync read : http://ceph.com/docs/master/rados/api/python/#rados.Ioctx.read
That would be the simple way.

I think you ask to read say 4096 and know its EOF when librados returns less than 4096.

I will do tests like this.

Default read size is now 8192.


refactor(noUnusedTemplateLiteral): remove rule sources

Summary
Citing no-useless-template-literals (now renamed no-unnecessary-template-expression) was an error.
The rules are different.
The ESLint rule reports template literals that only use literals in interpolation. It doesn't report a template literal without interpolation.
Our rule outputs an opposite behavior.
Test Plan
CI must pass.

Close because I merged #2959


Application Logo

We need a logo for the app before submitting it to Contentful's Marketplace #5

The logo should tell you that it's part of Adapt Essentials and also that it's for a Color design system
Quick sketches I've done, feel free to ignore these: https://github.com/adaptdk/adapt-toolkit-color-picker/issues/4#issuecomment-1702391941

@zzzarius solution


fix: update theme color

Ok

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


🐛 TreeView selection state fixes/enhancements

All the recent enhancements to TreeView are very much appreciated, especially the narrowSpacing behavior and the keyboard navigation!
My application is using both single-selection and multi-selection TreeView widgets, and I've noticed some bugs and useful enhancements:

🐛 A single-selection TreeView that is given an initial list of items that has a single item selected may improperly clear out the selection state of this item if the single selected item has any children (initState calls buildItems and that improperly calls updateSelected).
🐛 In single-selection mode, if a child item is selected, and then the parent is collapsed so that the child is hidden, and then the parent item is selected, the child item's selected state is not properly set to false. If you expand the parent, then the child item will still be selected and it will have multiple items selected even though it's a single-selection tree view.
onItemInvoked is called for 3 different reasons: when the item's selection state is toggled, when the item is expanded or collapsed, or when the item is otherwise pressed (or space/enter is pressed). Without knowing the item invoke reason, it's not easy to implement logic that toggles the selection state of an item only when it's pressed (and not for the other two reasons).
Along the same lines, an application may want to toggle the selection state of a given item in a multi-selection mode tree, and some helper methods should be exposed so that the same logic can be used to set the new selection state of an item and all of its children, as well as to appropriately update the selection state of the parent(s) of an item.
You may want to allow a parent item to remain selected even if the user deselects all of the children (it would show the "indeterminate" checkbox state in this case). This can be useful if the parent
For this reason, you may also want to have included in the list of selectedItems passed to the onSelectionChanged callback any parent items that are partially selected.

I'll submit a PR that fixes these bugs and implements these enhancements. With these enhancements, my application can now easily programmatically change the selection state when an item is clicked/pressed (storing selection state in riverpod and propagating changed item list back to treeview widget through provider rebuild), and also parent items can remain selected even if children are all deselected. Note that it still defaults to the old behavior.

You may want to allow a parent item to remain selected even if the user deselects all of the children (it would show the "indeterminate" checkbox state in this case).

I don't think this behavior exists in the native implementation. Can you tell an use-case for this?

I don't think this behavior exists in the native implementation. Can you tell an use-case for this?

Let's say that the tree view is showing a list of folders defining which folders you want to search for files within. It's possible that the user wants to search for files in a given parent directory but not any of that parent directory's children directories. That would require the ability for the children to be deselected but the parent to remain selected. For example:
Root
  |--> Parent
        |-->Child1
        |-->Child2
        |-->Child3

The user might want to search for files in the Root and Parent directories, but not for files in the Child[123] subdirectories`, etc.
Another common use case are backup applications where the user is choosing what they want to restore (and the UX typically shows a folder tree on the left, and a flat listview on the right showing files just within the currently highlighted directory), and they want to restore the files in the parent directory, but they don't want to restore content in the child subdirectories.
It definitely shouldn't be the default behavior, but is a nice optional behavior needed for cases where each treeview item might logically contain things besides just the child items shown in the tree.


mean value and use_global_stats

Hi Frank,
Good job! I have two puzzles to check with you. :)

The BatchNorm layer has "use_global_stats: true", which means the prototxt is the deploy instead of the train prototxt? Cuase if my understanding is correct, the use_global_stats is set to be FALSE during the training process of BN.

You comment the mean value in the prototxt. Does it mean that we need to minus the mean by myself cause it is possibly the deploy.prototxt?

Thank you!
Best,
Jordan

Hi Jordan
1. All of these are deploy prototxts. In order to convert to train prototxts,  you could insert weights initialization ("msra"), set lr_mult and decay_mult, and set use_global_stats  to be FALSE.
2. The comment  shows what mean values we used in training as it is a deploy.prototxt.


Added the list to the string conversion function.

Added  list to string conversation function

Added list to string function

Added the meaning full name


added House robber (Lc medium)

this is amazing @wre9-tesh
thanks for the contribution in my repo and please share in social media and tag me on twitter


Port ranges for WebRTC

I've been playing around with getting the server running on an Ubuntu 16.04 VPS and am using iptables to manage firewalling. Just wondering what port ranges I should open up as it doesn't seem to want to allow connections from the client -> server if only ports 80, 443 and 8080 are open. I assume it's a problem with the STUN/TURN connection from the server to Google's servers. Do I just need to leave the higher ranges open? Is there any point restricting ports if this is the case?

WebRTC can have a hard time with firewalls. I'll refer to other sources to explain the problems so as not to confuse / get it wrong, but the overall problem can generally be solved by using STUN and/or TURN servers. Check out https://www.html5rocks.com/en/tutorials/webrtc/infrastructure/ for an explanation.
Try using https://haydenlee.io as your signalUrl as explained here: https://github.com/haydenjameslee/networked-aframe#scene-component and see if that fixes it. I've setup that server to use XirSys which is a service to provide STUN and TURN. Note that since my site is https you'll need to be hosting on an HTTPS-enabled server.
If that doesn't work there might be another issue.

I ended up switching to using DigitalOcean's firewall that sits in front of my instance instead of iptables and it seems to work correctly now. I think we can close this.


ORC-990: [C++] fix RowReaderImpl::seekToRowGroup

What changes were proposed in this pull request?
ORC-990: [C++] fix RowReaderImpl::seekToRowGroup
Why are the changes needed?
In environment Windows, MSVC 19.12.25835.0
test DictionaryEncoding.multipleStripesWithIndex failed due to invalid iterators in positionProviders.
    for (auto rowIndex ... {
      // copy index positions for a specific column
      positions.push_back({});
      auto& position = positions.back();
      for (int pos = 0; pos != entry.positions_size(); ++pos) {
        position.push_back(entry.positions(pos));             // iterators may be invalidated here due to reallocation
      }
      positionProviders.insert(std::make_pair(colId, PositionProvider(position))); //    iterator taken here
    }

How was this patch tested?
test DictionaryEncoding.multipleStripesWithIndex passed with proposed fix

@wgtmac , please land this to the required branches for the next releases~
Thank you, @rip-nsk and @wgtmac .

Thank you!


Down-sync Gists

Sync changes from a gist to a local file

The requirements can vary dramatically and comes with a lot of headaches.
Better off as a standalone action, if I make it at all.


Major improvements and fixes to the C++ OData client library, see below:

OData changes:

Implement log option for http trafic via a callback
Access to the http headers of a regular message and the $metadata
Use of _XPLAT() macro instead of the U() macro, allowing the define of U() to not be present if it disturbes
Naked arrays are allowed
Collections may legally contain entities, not just primitive or complex types
Implement open property types
Implement proper handling of namespace aliases
Remove the model of this instance from the model cache and the instance on request
Suppress the output of @OData.type in requests. This is a WAR for TM1 servers that will unjustifiedly choke on such annotations!
Search query available
Update an array of values
Strings can alternatively be a string_t or a ::boost::flyweight<sting_t>
shared_ptr can be instanciated by make_shared or new
Fix: Corrected broken overload of what()
Fix: Missing const added in nemerous places
Fix: Corrected some typos in the source
Implement return value of call available
Fix: Typos in code-generation.h that prevented compilation
Extended number of parameters from 6 to 12
Completed operations according to the OData standard
Implemented the operators of the open property map
Support VS 2017 and 2019
Removed warnings to improve code quality
Added @odata.bind
Numerous small improvements and fixes

TODOs:

Make base class of types instanciable (currently not possible due to an abstract class but desirable)
Implement OData type stream (currently not implemented and an atempt to do so causes a compile error)
Still large memory consuption if types are complex and there are a lot of them. This is due to the many(!) nullptrs that could be present
Test not checked for compilability and correctness after changes
Do checks for compilation under VS 11 and VS12 if desired and make source code compile under those
shared_ptr of flyweight is of course redundant, so make the strings not use shared_ptr anymore

@PBRCW  -- Thanks for your contribution!
As you can see, it's been a while since we've introduced changes to this repo, and some of our backend build processes will have to be resurrected to get out an official build.
Still, I would very much like to take your contributions and support others that may have interest in this project.
We have moved some of these projects (like RESTier, ODataConnectedServices, ODataModelBuilder) to .NET Foundation in order to better engage with the community.  If this repo is important to your scenarios, and you anticipate continuing to participate, we can look at moving this to .NET Foundation and making you a moderator.  -- LMK your thoughts!

@PBRCW  -- Thanks for your contribution!
As you can see, it's been a while since we've introduced changes to this repo, and some of our backend build processes will have to be resurrected to get out an official build.
Still, I would very much like to take your contributions and support others that may have interest in this project.
We have moved some of these projects (like RESTier, ODataConnectedServices, ODataModelBuilder) to .NET Foundation in order to better engage with the community.  If this repo is important to your scenarios, and you anticipate continuing to participate, we can look at moving this to .NET Foundation and making you a moderator.  -- LMK your thoughts!

Hello Michael,
The background:
I needed a C++ solution for REST/OData an this library was the only one I found. So I took this and after some fiddling I found that it’s unfortunately rather buggy and some features are not implemented. So over time I fixed bugs, extended the library as needed and implemented missing features. In my case this library is used for a C++ application that connects to an IBM TM1 database using a RESTful API and OData. See
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_rest_api.2.0.0.doc/tm1_rest_api.html
I’m however leaving the company I’m currently working in to end of Jan. So there’s two things I have to do:

Change my email address on github so that it’s pointing on my private address (as I will or course no longer be reachable via my company address)
Thinking about whether I will like an find the time to work as a maintainer of this library privately

I must say I don’t see much sense in converting that to a .NET library, or what do you suggest? You already mentioned RESTier, etc. who already do serve this purpose in .NET. What reason is there to have this library as well in .NET? Or do I get something wrong here? Do you mean just putting it on .NET Foundation but keeping it a C++ project?
More precise and again:
I needed a C++ solution (namely a none gc solution) and this is the only one I found. Whereas I’m meanwhile tempted to say in the state that before my changes it was more like a POC than a solution. It still is very clumsy regarding e. g. its maintenance. This is due to much functionality realized via C’s pre-processor, even templates, and this combination makes it very(!!) hard to debug. Also the code generator who should be able to read the $metadata of some service and create classes from it is still buggy and doesn’t work as intended, name clashes are e. g. one problem, types that aren’t yet supported (but of course may be in the $metadata) is another one that makes it stumble. I ended up for the time being ignoring the code generator and making several files defining the classes that depict the $metadata from the server manually. So there’s work left to do! Also the github page https://github.com/OData/odatacpp-client is in a lousy state, most if not all links result only in a 404.
The following things are to be checked:

What do have the client ant the server library (https://github.com/OData/odatacpp-server) in common? My impression was that it shares quite some files but I didn’t take a closer look. My changes of the client side surely lead its code a bit away from the server. The question is, can and must it be that way or could it be avoided? Keeping the identical files identical would be my preference but this is a topic still unclear. At least the server seem to be a bit(!) better maintained,  the last commit is “only” four years old and at least the links aren’t broken. But  there is no official release as well.
The client library in the optimum case should support all compilers and options Casablanca does as well. Anyway I assume this is currently not the case. However things introduced in C++ recently (like variadic macros) could trim down the code a lot and make it better maintainable, making it highly desirable to use that. Unfortunately older version of VS don’t implement that features, so as long as these are supported the code stays even clumsier that it needs to.
Does it really make sense to convert this library to a .NET version or shall it stay a C++ solution?
Let’s assume I’d become the maintainer, who does the testing with older compiler versions and other destination platforms? I have neither old VS versions nor any kind of Apple OS, so I cannot do it.
My time is scarce, I already know that. If I’d be a maintainer it could only be that it’s very little to do, little traffic and a possible lag in the answering of questions. Anything else I will not be able to manage and this does not make sense. It’ll only annoy other developer as well as myself.

What do you think?
BR
Peter
Von: Michael Pizzo<EMAIL_ADDRESS>Gesendet: Dienstag, 12. Januar 2021 23:52
An: OData/odatacpp-client<EMAIL_ADDRESS>Cc: Peter Brockamp<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [OData/odatacpp-client] Major improvements and fixes to the C++ OData client library, see below: (#32)
@PBRCWhttps://github.com/PBRCW -- Thanks for your contribution!
As you can see, it's been a while since we've introduced changes to this repo, and some of our backend build processes will have to be resurrected to get out an official build.
Still, I would very much like to take your contributions and support others that may have interest in this project.
We have moved some of these projects (like RESTier, ODataConnectedServices, ODataModelBuilder) to .NET Foundation in order to better engage with the community. If this repo is important to your scenarios, and you anticipate continuing to participate, we can look at moving this to .NET Foundation and making you a moderator. -- LMK your thoughts!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/OData/odatacpp-client/pull/32#issuecomment-759087908, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID4CAS5PEZTNZZ5U2HZGNLSZTHCNANCNFSM4V55TDJA.
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.  This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this mail in error) please notify the sender immediately and destroy this mail. Any unauthorized copying, disclosure or distribution of the material in this mail is strictly prohibited.

Hello Michael,
The background:
I needed a C++ solution for REST/OData an this library was the only one I found. So I took this and after some fiddling I found that it’s unfortunately rather buggy and some features are not implemented. So over time I fixed bugs, extended the library as needed and implemented missing features. In my case this library is used for a C++ application that connects to an IBM TM1 database using a RESTful API and OData. See
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_rest_api.2.0.0.doc/tm1_rest_api.html
I’m however leaving the company I’m currently working in to end of Jan. So there’s two things I have to do:

Change my email address on github so that it’s pointing on my private address (as I will or course no longer be reachable via my company address)
Thinking about whether I will like an find the time to work as a maintainer of this library privately

I must say I don’t see much sense in converting that to a .NET library, or what do you suggest? You already mentioned RESTier, etc. who already do serve this purpose in .NET. What reason is there to have this library as well in .NET? Or do I get something wrong here? Do you mean just putting it on .NET Foundation but keeping it a C++ project?
More precise and again:
I needed a C++ solution (namely a none gc solution) and this is the only one I found. Whereas I’m meanwhile tempted to say in the state that before my changes it was more like a POC than a solution. It still is very clumsy regarding e. g. its maintenance. This is due to much functionality realized via C’s pre-processor, even templates, and this combination makes it very(!!) hard to debug. Also the code generator who should be able to read the $metadata of some service and create classes from it is still buggy and doesn’t work as intended, name clashes are e. g. one problem, types that aren’t yet supported (but of course may be in the $metadata) is another one that makes it stumble. I ended up for the time being ignoring the code generator and making several files defining the classes that depict the $metadata from the server manually. So there’s work left to do! Also the github page https://github.com/OData/odatacpp-client is in a lousy state, most if not all links result only in a 404.
The following things are to be checked:

What do have the client ant the server library (https://github.com/OData/odatacpp-server) in common? My impression was that it shares quite some files but I didn’t take a closer look. My changes of the client side surely lead its code a bit away from the server. The question is, can and must it be that way or could it be avoided? Keeping the identical files identical would be my preference but this is a topic still unclear. At least the server seem to be a bit(!) better maintained,  the last commit is “only” four years old and at least the links aren’t broken. But  there is no official release as well.
The client library in the optimum case should support all compilers and options Casablanca does as well. Anyway I assume this is currently not the case. However things introduced in C++ recently (like variadic macros) could trim down the code a lot and make it better maintainable, making it highly desirable to use that. Unfortunately older version of VS don’t implement that features, so as long as these are supported the code stays even clumsier that it needs to.
Does it really make sense to convert this library to a .NET version or shall it stay a C++ solution?
Let’s assume I’d become the maintainer, who does the testing with older compiler versions and other destination platforms? I have neither old VS versions nor any kind of Apple OS, so I cannot do it.
My time is scarce, I already know that. If I’d be a maintainer it could only be that it’s very little to do, little traffic and a possible lag in the answering of questions. Anything else I will not be able to manage and this does not make sense. It’ll only annoy other developer as well as myself.

What do you think?
BR
Peter
Von: Michael Pizzo<EMAIL_ADDRESS>Gesendet: Dienstag, 12. Januar 2021 23:52
An: OData/odatacpp-client<EMAIL_ADDRESS>Cc: Peter Brockamp<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [OData/odatacpp-client] Major improvements and fixes to the C++ OData client library, see below: (#32)
@PBRCWhttps://github.com/PBRCW -- Thanks for your contribution!
As you can see, it's been a while since we've introduced changes to this repo, and some of our backend build processes will have to be resurrected to get out an official build.
Still, I would very much like to take your contributions and support others that may have interest in this project.
We have moved some of these projects (like RESTier, ODataConnectedServices, ODataModelBuilder) to .NET Foundation in order to better engage with the community. If this repo is important to your scenarios, and you anticipate continuing to participate, we can look at moving this to .NET Foundation and making you a moderator. -- LMK your thoughts!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/OData/odatacpp-client/pull/32#issuecomment-759087908, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID4CAS5PEZTNZZ5U2HZGNLSZTHCNANCNFSM4V55TDJA.
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.  This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this mail in error) please notify the sender immediately and destroy this mail. Any unauthorized copying, disclosure or distribution of the material in this mail is strictly prohibited.

Just Learing


JetBrains-Gateway: Unable to connect via module

Coder version: v2.9.0
I am getting
coder-jetbrains--main--gpu.matifali.dev: nodename nor servname provided, or not known

Connecting manually via the coder plugin works.

This seems to be broken after https://github.com/coder/jetbrains-coder/pull/372

Can you confirm the version of the plugin?  This could actually be something we fixed in that PR, where it was using just the agent name instead of workspace.agent.

Ok So I was on 2.9.*. Updating plugin to latest version fixed it.


fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/kms-all-inclusive/ibm (source)
module
patch
4.15.12 -> 4.15.13

terraform-ibm-modules/secrets-manager/ibm (source)
module
patch
1.18.2 -> 1.18.3

Release Notes

terraform-ibm-modules/terraform-ibm-kms-all-inclusive (terraform-ibm-modules/kms-all-inclusive/ibm)
v4.15.13
Compare Source
Bug Fixes

deps: update terraform-module (#547) (1a284ed)

terraform-ibm-modules/terraform-ibm-secrets-manager (terraform-ibm-modules/secrets-manager/ibm)
v1.18.3
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/kms-all-inclusive/ibm to v4.15.12 (#205) (c22f4f7)

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

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

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.19.13 :tada:
The release is available on:

GitHub release
v1.19.13

Your semantic-release bot :package::rocket:


Added ability to build project in scope of another CMake project

Added ability to build project in scope of another project

add_subdirectory(deps/autobahn-cpp)
...
add_executable(app main.cpp)
target_link_libraries(app autobahn_cpp)

Added ability to disable build examples

cmake -DAUTOBAHN_BUILD_EXAMPLES=OFF <src>

or in case of subproject
option(AUTOBAHN_BUILD_EXAMPLES "" OFF)
add_subdirectory(deps/autobahn-cpp)

Tested only on Linux


Q: what service/characteristic to use for a power fail sensor

and, as long as i'm asking you random questions @ebaauw , i have a sensor that has two plugs: one is intended to plug into a UPS and the other into a wall outlet. if the power goes out on the wall outlet, it reports that.
what would you recommend for a service/characteristic to model this sensor?
thank you again!

I don't think there's a standard HomeKit characteristic for power failure, but you could map it to Status Fault.  I don't think Apple's Home app would recognise it, though.

i agree that StatusFault probably isn't a winner. i'm thinking that the only thing that comes close is Switch, where power loss is indicated by (On = false)....


Only deploy once when multiple images change

Flux seems to require deploying once for every changed image. This is inconvenient for services using multiple images (i.e. if N images have changed, then N deployments are required).

This is by design: https://github.com/weaveworks/flux/blob/master/automator/automator.go#L147
It's actually simpler to perform the deploy in a single release, because we can then reuse the the release code in releaser.go.
But goes against the original design. So we need a tip of the hat from @squaremo.

I think this may be referring to how the user interface works: in the CLI you can only deploy one image at a time, and in the web UI you can only deploy one image to one service at a time. So I think this is about supplying more than one --update-image argument, e.g.
(In the case of automation, we usually only see one image change anyway, to an approximation.)

If multiple images get updated tags at approximately the same time, they'll now all be combined into the same automated release as of #589.