Support for iOS 7 and OS X 10.9 (update podspec)

Currently the podspec is limiting use to iOS 8. But there doesn't seem to be anything in moya which is iOS specific, nor iOS 8 specific. Since Alamofire's requirements are iOS 7 and OS X 10.9 and up, it seems like Moya's should be as well.

I think the iOS 7 restriction is more along the lines that Swift pods are only supported with use_frameworks! flags in CocoaPods.
And dynamic frameworks are only available in 8.x and above.

That makes sense – OS X support seems pretty easy. iOS 7, though, confuses me a bit. How can Alamofire's podspec support iOS 7 if Swift pods require frameworks, and frameworks work only on iOS 8? Or am I misunderstanding something?

Ah, beat me to it @esttorhe  :)

i think we hit Comment at the same time :see_no_evil:

Alamofire's podspec points to 8.0 as you can see

Oops, silly me. iOS 8 it is.

I think supporting 10.9 makes sense though, and should be «trivial» to add.

Cool, I've opened up https://github.com/Moya/Moya/issues/192 to do just that.

Tricky, since ReactiveCocoa has a minimum OS X deploy target of 10.10. I'm having trouble getting this to work with a subspec having a different OS X deploy target.
Since no one has requested this, I'm fine with closing this as-is. We have OS X support, which was one of the big parts; I'm on with 10.10.
If anyone wants to re-open and investigate, :tada:

Ya the ReactiveCocoa podspec also doesn't reflect the project's settings. In the project it is 10.9 but not in the podspec. 😢


Populate primary env var and aliases when invoking plugin or expanding env vars

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2279
Originally created by @DouweM on 2020-08-19 22:20:06

As suggested in https://gitlab.com/meltano/meltano/-/issues/2208#note_388529270:

Perhaps the best option would be to have Meltano write to both the env and env_aliases keys, so that we cover all bases for backward compatibility, but can still recommend the simple <NAMESPACE>_<NAME> vars, and prefer those when writing to .env.

View 4 previous comments from the original issue on GitLab


337 multiple values field type

What this PR does / why we need it:
Hard-coded version of multiple metadata values input, to be modified for the dynamic Create Dataset form
Which issue(s) this PR closes:

Closes #337

Special notes for your reviewer:
Suggestions on how to test this:
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation:

coverage: 98.563% (+1.1%) from 97.473%
when pulling 093743a8dee9987616d3230315cc915b77442e58 on 337-multiple-values-field-type
into b98afdb1b608dbde27ce93c758e81cf8d480c06a on feature/316-create-functional-create-dataset-form.

Thanks @MellyGray I made the changes you suggested. The e2e test is currently failing on get  total dataset counts, which the clear test data PR should fix.

Thanks @GPortas for finding that form submission bug!  I fixed that, and updated the validation to use the same hook as the other fields, so now I think the behavior is consistent with the rest of the form.
The e2e tests are failing because of race conditions when clearing test data, which I think will be fixed by this PR #360


Fix #663, more consistent use of data types

Describe the contribution
Define and Use data types more consistently across CFE.
Replace many uses of generic uint16/uint32 with a more purpose-specific typedef. Replace all sizes with size_t across the API.
Fixes #663
Testing performed
Build and sanity test CFE
Expected behavior changes
None, but does affect API.  The API changes should be largely backward compatible, however.
System(s) tested on
Ubuntu 20.04, 64-bit
Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

Pushed a draft/preview commit as discussed in the 2020-11-04 CCB.  This has all the API changes but the unit test updates are not complete.

General summary of what's being proposed:

Use size_t for all in-memory object sizes, EXCEPT for:

CMD/TLM messages - where CFE_ES_MemOffset_Atom_t is used
Interface with PSP, where uint32 must be used until PSP API is updated (could do that too)

Use sizeof() more consistently - particularly on strings on the stack in message handlers.  It is more type correct (because value is a size_t, not int) and it adheres to the DRY principle - we want the actual size of the string, whatever it really is - don't assume it was declared to a certain size.

Use ES-defined typedefs for Task Priority, Stack Pointer, etc.

Anywhere a constant is used for these types, wrap it in a macro that converts the type, which makes the type conversion explicit when reading the code.

Also note that this sweep also caught a bunch of issues in the old SB message API - which if its being deprecated, we can just ignore those.  But we should decide whether the new MSG API should use size_t or keep its separate CFE_MSG_Size_t ... my thought is if we are going to use size_t, lets use it everywhere.  The same justification for not putting a size typedef in CFE should apply to the module(s) (and vice versa).

...issues in the old SB message API

I also noticed a bunch of type issues (maybe some of the same?), fixed what I saw in #998.  Mostly using uint16 for message size all over, which is a bug since it can't represent the full size CCSDS message.  Agree that size_t could replace CFE_MSG_Size_t.  The less one-off types the better in my mind.  Maybe get #998 in first, then fix?
Could we use a more descriptive name than CFE_ES_MemOffset_Atom_t?  Really it's a conversion instead of the atomic type, isn't it?  I think of it as the native to tlm conversion for size_t...
Is the CDS offset type just for the PSP?  If so I say we get that fixed also.  It stands out as unique.

This will conflict with #998, but I like your change better (using size_t for the verify command length).
I would prefer separating the concept of the atomic type (which could be native) with the conversion to fit in telemetry.  I'd also prefer the default behavior to use 64 bit's for memory addresses... if a user wants to use just 32 bit they can, but I'd rather default to consistent sized messages across 64/32 and valid data in both.

...issues in the old SB message API

I also noticed a bunch of type issues (maybe some of the same?), fixed what I saw in #998. Mostly using uint16 for message size all over, which is a bug since it can't represent the full size CCSDS message. Agree that size_t could replace CFE_MSG_Size_t. The less one-off types the better in my mind. Maybe get #998 in first, then fix?

Yes, I think the best approach would be to embrace size_t everywhere, for all in-memory objects.  There was also some random casting of sizes to uint16 here and there (EVS had one, I think - fixed in this PR).  And yes, I concur with finishing up the pending changes first.

Could we use a more descriptive name than CFE_ES_MemOffset_Atom_t? Really it's a conversion instead of the atomic type, isn't it? I think of it as the native to tlm conversion for size_t...

Yes, perhaps we should bring up/revisit the whole "_Atom_t" suffix thing in general.... the genesis of the type suffixes was to facilitate automation/tool-chaining of these types - and use a different suffix for enums, strings, structures, etc.
It is currently documented in https://github.com/nasa/cFE/blob/main/docs/cFS_IdentifierNamingConvention.md#typedefs (unfortunately just noticed that github doesn't render the table data in this MD file correctly either -- another issue?).
At any rate, this is the pattern that I still try to follow for CMD/TLM types.  I still think its a useful thing to have a different suffix, maybe "Atom" is confusing and we could do something else.  It is intended to convey that it is a scalar, as opposed a compound type (struct/string/array) etc.  Maybe "Scalar"?

Is the CDS offset type just for the PSP? If so I say we get that fixed also. It stands out as unique.

Not just CDS - all the memory blocks incl. reserved area and RAM disk are done with uint32 sizes - and these are especially problematic because they pass by pointer - not by value - so any change would NOT be backward compatible.
Because any change to this API would not be backward compatible - my recommendation is to rethink/redesign this API and make it more future proof, such as:
void * CFE_PSP_GetBlockPointer(CFE_PSP_BlockId_t BlockId);
size_t CFE_PSP_GetBlockSize(CFE_PSP_BlockId_t BlockId);

Then the PSP can also provide separate constants for BlockId corresponding to the ramdisk, reserved area, cds, etc.  The important thing is we can add/extend these constants without breaking or changing the general API.  The current calls have a separate dedicated call for each memory section.  So making it more extensible we can more easily have separate sections for ES/EVS/TIME (I think there is another issue related to this)

CCB 2020-11-18

Related to nasa/osal#654
Removes implicit type conversions
Need separate discussion about _atom suffix nomenclature since it doesn't actually mean "atomic"
Will hold a little less in CDS size for 64-bit platforms

Are all _Atom_t types fixed size (appropriate for cmd/tlm messages)?  If so and we continue with this pattern, then I'm fine with it. In my mind it was just the "scalar" type, but without the fixed size restriction.


Sign integration test & catch up with latest tm-core develop

ready for a first review
resolves https://github.com/tendermint/kms/issues/44
Todos:

[x] update sign_bytes and messages according to ~~https://github.com/tendermint/tendermint/issues/1622#issuecomment-422363861~~ to be on par with https://github.com/tendermint/tendermint/pull/2459
[x] add tests for all messages; currently, only heartbeat is tested
[x] add Ping(Request | Response) message handling (resolves #70)
[x] catch up with https://github.com/tendermint/tendermint/pull/2666 (related https://github.com/tendermint/tendermint/issues/2665)
[x] implement get_public_key (resolves #72)
[ ] catch up with https://github.com/tendermint/tendermint/pull/2675
[ ] if tendermint's next release uses amino 0.13.0, we also need to update the time encoding according to: https://github.com/tendermint/go-amino/pull/224 (https://github.com/tendermint/kms/issues/73)

Thanks a lot @tarcieri! I'll merge this and open issues for the left TODOs (https://github.com/tendermint/kms/pull/55#issue-216535113)


Add package dependencies for TraceEvent NuGet pkg

Address #886 & #793 .

Is the System.Memory reference still needed? I thought we removed it with #870 ?

This is not needed anymore since #870 did it.


Space Invaders game added

Old school classic reimagined by @REC-1104 and @Pin4sf
PR Description 📜
Space Invader is an old school Arcade Game developed by Tomohiro Nishikado and is considered an iconic game in the industry with the likes of Pac-Man , Donkey kong and Mario. I have completed the Space Invader game with new interactive UI , , modern menus and gameplay.
WE ALSO HAVE AN EASTER EGG!!
Fixes # <159>

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have specified the respective issue number for which I have requested the new game.

screenshots 📸

Thank you soo much for contributing to our repository 💗

Thank you @Pin4sf ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Hey @Pin4sf !! read documentation and then tag properly on which you are working and then create PR again !!
You are missing out in lot of things !!

Thank you  @Pin4sf , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Add a descriptive stats page for the datasets

This should include a short description of the dataset as well as a description. It should be autogenerated from the datasets.

Added in latest version


SQL Server (Microsoft) Readme Updates

After following the Readme for adding a Microsoft SQL database I ran into some issues getting it started.

a PHPize error as commented on here https://github.com/drud/ddev-contrib/pull/168#issuecomment-1205342355
Password in readme did not match Docker-compose.sqlsrv.yaml

/cc @drupal-daffie - please weigh in.


CP-CAS communication fails when server TLS is enabled

When the CAS has server TLS enabled, the communication between the controlplane -> CAS fails
grpcurl -cacert ../devel/devkeys/selfsigned/rootCA.crt -d '{"readiness": true}' localhost:9000 controlplane.v1.StatusService.Statusz
ERROR:
  Code: Unavailable
  Message: Artifact CAS is not reachable
  Details:
  1)    {"@type":"type.googleapis.com/google.rpc.ErrorInfo","reason":"CAS_NOT_READY"}

The error in the server is (once disabled insecure: true in cas_server.insecure setting)
\"transport: authentication handshake failed: tls: failed to verify certificate: x509: cannot validate certificate fo
r <IP_ADDRESS> because it doesn't contain any IP SANs\"okfalse"}

After some research, it seems that this is not an actual problem, the issue is the value put in  development (<IP_ADDRESS>), which is not a valid FQDN.
Using localhost instead works.
What's missing though is to make sure the CP->CAS communication is configured as secure if the TLS setting is set.


Support DragonFlyBSD

@mneumann Sorry, I missed this PR before. Thanks for submitting this.

@mneumann I just released this in v0.1.6. I removed two of the definitions (SIOCADDRT and SIOCDELRT), because they were recently removed from DragonFly: https://github.com/bycn82/dfly/commit/ac6b17f6589738ce724d57fa3504d11e1cb553b8#diff-e8da22b0b71706a913abc3066e655a06

Closing because I merged this on the command-line. @mneumann Thanks for submitting this.


Fix scale of window for smaller screens

A scale of .1 is too small. Try finding a scale that looks good for both and make the scale depend on the screen size. See how scaling works on mer_stamps

Move centering the screen to the end of the mainwindow function

Fixed in https://github.com/pbvarga1/pystamps/pull/38


testing auto upload

@chaosphere2112 will upload everytime something goes into master. Do not forget to change git tag and version in recipe of course before doing so.


Add VisualPicker component

The Lightning Reports team would like to implement the <VisualPicker/> component. We will consume it as part of a new feature in 220.
For reference, the Visual Picker spec is here: https://latest-220.lightningdesignsystem.com/components/visual-picker/
Here are the props proposition:
static propTypes = {
    /**
     * **Assistive text for accessibility**
     * This object is merged with the default props object on every render.
     * * `label`: This is used as a visually hidden label if, no `labels.label` is provided.
     * * `icon`: Text for checkmark icon on selected item(s).
     * * `selectedItemLabel`: This is used as a visually hidden label of selected item(s). The default is `Current Selection:`.
    */
    assistiveText: PropTypes.shape({
        label: PropTypes.oneOfType([PropTypes.string, PropTypes.node]),
        icon: PropTypes.string,
        selectedItemLabel: PropTypes.string
    }),
    /**
     * CSS classes to be added to tag with `.slds-visual-picker`.
     */
    className: PropTypes.oneOfType([
        PropTypes.array,
        PropTypes.object,
        PropTypes.string,
    ]),
    /**
     * CSS classes to be added to tag with `.slds-visual-picker__body`.
     */
    classNameBody: PropTypes.oneOfType([
        PropTypes.array,
        PropTypes.object,
        PropTypes.string,
    ]),
    /**
     * CSS classes to be added to top level tag with `.slds-form-element`.
     */
    classNameContainer: PropTypes.oneOfType([
        PropTypes.array,
        PropTypes.object,
        PropTypes.string,
    ]),
    /**
     * Event Callbacks
     * * `onBlur`: Called when `input` removes focus.
     * * `onFocus`: Called when `input` receives focus.
     * * `onRequestRemoveSelectedOption`: Function called when selected option is to be removed.
     * * `onSelect`: Function called when item is selected.
     */
    events: PropTypes.shape({
        onBlur: PropTypes.func,
        onFocus: PropTypes.func,
        onRequestRemoveSelectedOption: PropTypes.func,
        onSelect: PropTypes.func,
    }),
    /**
     * HTML id for component.
     */
    id: PropTypes.string,
    /**
     * **Text labels for internationalization**
     * This object is merged with the default props object on every render.
     * * `label`: This label appears above the component.
     */
    labels: PropTypes.shape({
        label: PropTypes.oneOfType([PropTypes.node, PropTypes.string]),
    }),
    /**
     * **Array of item objects**
     * Each object can contain:
     * * `id`: A unique identifier string.
     * * `label`: A primary string of text for the heading of an item.
     * * `title`: A secondary string of text that renders as a sibling the `label` element.
     * * `visualIndicator`: A node displaying a visual indicator for the item. Not available with `variant=vertical`.
     *
     */
    options: PropTypes.arrayOf(
        PropTypes.PropTypes.shape({
            id: PropTypes.string.isRequired,
            label: PropTypes.string,
            title: PropTypes.string,
            visualIndicator: PropTypes.nodes
        })
    ).isRequired
    /**
     * Adds required (*) styling to label.
     */
    required: PropTypes.bool,
    /**
     * Selected item object.
     * * `id`: A unique identifier string.
     * * `label`: A primary string of text for the heading of an item.
     * * `title`: A secondary string of text that renders as a sibling the `label` element.
     * * `visualIndicator`: A node displaying a visual indicator for the item. Not available with `variant=vertical`.
     */
    selection: PropTypes.shape({
        id: PropTypes.string.isRequired,
        label: PropTypes.string,
        title: PropTypes.string,
        visualIndicator: PropTypes.nodes
    }),
    /**
     * The type of visual picker. The default is `coverableContent`.
     */
     variant: PropTypes.oneOf(['coverableContent', 'link', 'nonCoverableContent', 'vertical']).isRequired,
};

static defaultProps = {
    selectedItemLabel: 'Current Selection:'
    variant: 'coverableContent'
};

Hi @interactivellama !
This seems like an awesome component to work on to learn more about working in SLDS React! Can I be assigned this issue to work on? In the meantime, let me digest the conversation, experiment a little and clarify questions if any 😄

@tanhengyeow
Oops, I forgot to comment on this one. I had started working on this the other day, would you mind @tanhengyeow @interactivellama work on this? Maybe you should try the other ones out? sorry :(

Hey @tanhengyeow
Oops, I forgot to comment on this one. I had started working on this the other day, would you mind @tanhengyeow if I work on this? thanks.

Hi @aswinshenoy !
Actually I have significant work put in for this issue for the past 2 days. But never mind you can work on this one. Please wait for clarification next time before submitting a PR so that people's work won't be wasted, thank you 😄

@tanhengyeow sure :+1:


no index in wwwrot folder?

When creating a Mudblazor wit Autto(Server & WebbAssembly) the application run and everything.
I idid a pipeline in github to create try and create an static page to host in github.. but github need an index.html that should be created when doing
cd MyMudBlazorApp.Client
dotnet publish -c Release -o build
mv BuyBuddy.Client/build public
the build folder contains

and wwwroot

as you can see there is not index.html so i cant have the static page in github pages.
Is it missing or do I do something wrong

Is it missing or do I do something wrong

index.html doesn't exist in the Blazor Web App template, it's not suitable for GitHub Pages. You need the "Blazor WebAssembly Standalone App" template, which includes it, but we don't provide that template. Therefore, you'll need to create the basic one from Microsoft and integrate MudBlazor, which shouldn't be very difficult.

thankk you i will try that way.
The basic one one from Microsoft.. do you mean create a Blazor WebAssembly standalone app and copy the index.html file to the Balzor wwwroot folder?

Got it. thanks for the clarification.
Maybe just deploy the mudblazor in azure and for the github pages just have some autodocumentation page.

I would generally recommend reading the Microsoft documentation or articles about the different hosting models, such as this one: https://medium.com/@meghnav274/blazor-server-vs-blazor-webassembly-vs-blazor-web-app-8fe8fc1cefeb.
There are three types: Blazor Server (deprecated, no longer provided by us or Microsoft), Blazor WebAssembly (standalone), and Blazor Web App (which has different modes: Auto, Interactive Server, Interactive WebAssembly, and Static SSR).
They all differ from each other. Blazor WebAssembly is purely client-side and is not the same as Blazor Web App with Interactive WebAssembly, as the latter uses prerendering for faster loading, which requires a server on the initial load. In contrast, Blazor WebAssembly standalone will display a loading screen while downloading all the runtime assemblies.
The "Auto" mode you mentioned can utilize both Server and Client.
So, I would advise to google it, as there are many nuances, but it will help you become more fluent in Blazor.


Menu command Menu -> Run -> Start Debugging F5 does not work to update / publish to Business Central Sandbox

Describe the bug
Menu command Menu -> Run -> Start Debugging F5 does not work to update / publish to Business Central Sandbox. Restart debug icon does not work.
To Reproduce
Steps and to reproduce the behavior:
First, start with:
Ctrl + Shift + P
AL: GO!
Basic Hello World message app.
HelloWorld.al
launch.json
environmentName: changed to my sandbox environment name
app.json -> change:
"platform": "<IP_ADDRESS>",
"application": "17.0.16993.0"
Symbols are downloaded.
F5
DEBUG CONSOLE shows Success -> app is published
sandbox browser tab launches -> see "Hello world" message
Then, make change to HelloWorld.al "Hello world" -> "Hello Big AL World!"
Menu -> Run -> Start Debugging F5
DEBUG CONSOLE shows Success -> app is published
sandbox browser tab launches -> see "Hello world" message  (no change, not "Hello Big AL World!")
If I use either the actual keyboard press (F5)
OR
Ctrl + Shift + P
AL: Publish with debugging F5 recently used (return to select)
Then will always get any change to the HelloWorld.al -> sandbox browser tab launches
(again, Menu -> Run -> Start Debugging F5 never effects the change)
Similarly, the  Restart icon (Cntrl + Shift + F5) does not work. The DEBUG CONSOLE is cleared, but no Restart.
Pressing the keys Cntrl + Shift + F5 produces warning: There is already a debug configuration "Microsoft cloud sandbox" running.
The Stop (Shift F5) icon works and  pressing the keys Shift F5 does show Warning: Timeout after 2000 ms for 'terminate') but pressing the keys Shift F5 still requires to hit the Stop (Shift F5) icon to remove the Debug icons from it the interface.
AL Code to reproduce the issue
I initially thought it may be a key-binding issue. On laptop needed to use Fn F5. Then changed in BIOS to default to "F-key behavior). No change in outcome.
Disabled all extensions - re-enabled  AL Language extension. No change in outcome.
Expected behavior
Menu -> Run -> Start Debugging F5 should have the same result as pressing F5.
The Restart debugging icon should restart the debugging process.
Pressing  Shift F5 should terminate the sessions and remove the debugging icons from the interface.
Screenshots
If applicable, add screenshots to help explain your problem.

5. Versions:

AL Language:
AL Language, ms-dynamics-smb.al, Microsoft, License v6.1.359074
AL development tools for Dynamics 365 Business Central

VSC Version: 1.50.1 (user setup)
Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
Date: 2020-10-13T15:06:15.712Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.18363

Business Central: Sandbox
"platform": "<IP_ADDRESS>",
"application": "17.0.16993.0"

There is a bit of misdirection on the default VsCode menu here.
If you use the menu or debug icon
that will  start a debugging session without publishing equivalent with "Debug without Publishing".
We will try to see if we can rename the built-in VsCode menu text, with the confusing F5 since it should Shift Ctrl F5 for us.   F5 in the AL language server is "publish and debug". The functionality is by design for now.
Also restarting a debugging session is not implemented at all. Thus that is a missing functionality. If there is a demand for it I suggest creating a request here:

I had the same issue.
Go to Keyboard short cuts  and type the letter and number   F5
this will show all the bindings.
I had a "run task" assigned to F5, once I removed it, then F5 starts debugging.


useFlow - a react hooks library for DApp development on Flow

useFlow - a react hooks library for DApp development on Flow
Grant category
Open source maintenance
Description
useFlow is a library of react hooks enabling developers to build DApps on Flow quickly and efficiently.
The libary provides hook abstractions for all FCL functionality, like wallet connection, executing scripts and transactions and signing messages, all while featuring built in caching, request deduplication and loading states powered by react-query.
useFlow is based on experience from developing Chainmonsters and other Flow DApps and inspired by wagmi, a collection of react hooks for Ethereum DApp development.
I started setting up the library and would like to use the developer grant to be able to focus on making it feature complete and bring it to a release state :) https://github.com/maggo/use-flow
Problem statement

React is the most popular frontend framework but there's no "react native" way to integrate Flow interactions
While building Chainmonsters and other Flow DApps, I caught myself writing the same code again and again (boilerplate to set up FCL  and use it with react-query) and I'm sure that other frontend developers are doing the exact same

Proposed solution

Implement a library that provides a familiar interface (react hooks) for FCL interaction

Impact

Developers will be able to accomplish Flow blockchain interaction in their apps using a familiar concept, without having to write boilerplate code
Developers get automatic best UX and performance improvements (loading states, caching, request deduplication) thanks to react-query integration
Examples will allow for quick MVP development

Milestones and funding

Milestone
Deliverables
Timeline
Risks
USD proposal

1 - First stable release
Feature parity with FCL: Hooks for all API functions as specified in the docs, including a rich test suite
6 weeks
Timeframe
TBD

2 - Documentation & Examples
Docs website explaining the hooks and their parameters with usage examples
5 weeks
-
TBD

3 - Integrate useFlow in Chainmonsters website
Update chainmonsters.com codebase to use useFlow for all chain interaction; "dogfooding" to make sure that the libary is production ready
3 weeks
-
TBD

4 - Adoption
Get 5+ DApps to use useFlow, by providing consultation and support
???
-
TBD

5 - Maintenance
Keep library up-to-date with latest FCL updates, bugfixes and community support
6 months
-
TBD

Team

Name
Role
Bio
Contact

Marco
Main Contributor
Freelance full-stack developer with over 10y experience, 2y focusing on Flow & ETH. Web Developer @ Chainmonsters, focusing on website, marketplace and onchain interactions
<EMAIL_ADDRESS>maggo#1337

Milestone completion

[ ] First stable release
[ ] Documentation & Examples
[ ] Integrate useFlow in Chainmonsters website
[ ] Adoption
[ ] Maintenance

thanks for the submission @maggo! We took a look and wanted to see if you would be open to updating your milestones as such:

Add an adoption milestone at the end (eg get 5+ projects to use useFlow)

Reduce the scope to fit a new project seeking adoption. So: 1) reduce the testing scope, 2) remove the maintenance milestone, and 3) remove the sample app milestone (covered by docs and basic examples)

Hi @alxflw thank you for your feedback! I've updated the milestones as following:

Combined first release & test suite milestones
Combined documentation & basic examples milestones
Removed example dapp and maintenance milestones
Added adoption (5+ users) milestone

Milestone
Deliverables
Timeline
Risks
USD proposal

1 - First stable release
Feature parity with FCL: Hooks for all API functions as specified in the docs, including a rich test suite
6 weeks
Timeframe
TBD

2 - Documentation & Examples
Docs website explaining the hooks and their parameters with usage examples
5 weeks
-
TBD

3 - Integrate useFlow in Chainmonsters website
Update chainmonsters.com codebase to use useFlow for all chain interaction; "dogfooding" to make sure that the libary is production ready
3 weeks
-
TBD

4 - Adoption
Get 5+ DApps to use useFlow, by providing consultation and support
???
-
TBD

Please let me know if you had other changes in mind that I might have missed :)

wonderful, thanks for updating! we'll review and get back soon

hey @maggo, we'd like to accept this proposal if you are willing to add one more milestone at the end for 6 months maintenance (to keep up with latest NPM version of FCL). Please confirm and we can discuss the TBD portion of your project via email.

great, I sent you an email to discuss the USD proposal / TBD.

this application has been approved 🚀

Thank you @alxflw and team, excited to work on awesome Flow developer tooling 🚀

Given the time since this has been submitted I'm closing this down, please reach out to me if you'd like to share what you're working on now and explore potential opportunities<EMAIL_ADDRESS>


Line up Docker Compose with deployments

Trivy is kicking up Dockerfile issues, so this is a good time to revisit Docker Compose.  Includes:

consume Dockerfiles (no more vanilla images)
add healthchecks to Dockerfiles
non-provileged user that works in Docker Compose and OpenShift

There are still some differences, but PR #905 is an improvement.


Unsupported Maven plugin

We received a support request documenting an issue with an unsupported maven plugin:

The HoneyBadger plugin appears to be on an old version of Gradle, and we run Gradle 7 in our mobile app.
I'm pretty sure Google Play pushes us to be on Gradle 7 in order to upload the app into the app store.
The underlying issue appears to be that the Maven plugin isn't supported anymore on Gradle 7:
https://docs.gradle.org/7.0/userguide/upgrading_version_6.html#removal_of_the_legacy_maven_plugin

Still looking into this, but here's the specific error I'm seeing when compiling under Android:

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* Where:
Build file<EMAIL_ADDRESS>line: 23

* What went wrong:
A problem occurred evaluating project ':@honeybadger-io_react-native'.
> Plugin with id 'maven' not found.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring project ':@honeybadger-io_react-native'.
> compileSdkVersion is not specified. Please add it to build.gradle

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

BUILD FAILED in 3s

@rabidpraxis @jwigal This is fixed in 0.0.11.


how do you define a trend?

Hi chrism2671,
I want to know how do you identify a trend from a sideway. If we use ema cross, an fake trend is very common.
Thanks

@tiger2014 You don't. That's the nature of the strategy, you make a lot of little losses every day, and get a big payout every once in a while that offsets it.
With diversification, a lot of these little losses cancel out.

@tiger2014 this is likely what you're after, https://github.com/chrism2671/PyTrendFollow/blob/master/trading/rules.py#L179

Thanks


Bring coverage to 100%

I've added the correct test to #6, now it should really be testing everything.

 Thanks for this!


WIP - cleanup refactor && adding documentation for the api

@michaelthatsit - ignore the overall changes since it's still WIP
had some quick questions in this pr for when you get a chance though

@michaelthatsit - mostly completed - there's TODO questions that are left in, i'll walk you through this PR and them tomorrow morning to confirm before i close this out
pinging you for review for a run through of descriptions separate from the TODO questions
some notes:

there's 1 lingering build issue im tracking down from after i merged in your most recent pr
the github action for build is currently failing due to a webpack discrepancy; i'll solve that in a followup pr since it's not a blocker locally or once a build exists

@hanbollar well structurally it looks great but LayoutSystem seems to have gotten lost in the merge 😅. I tried running locally but I think I'm running into that build issue you mentioned.
We can spend tomorrow getting this across the finish line. LFGGGGGGGG

@hanbollar well structurally it looks great but LayoutSystem seems to have gotten lost in the merge 😅. I tried running locally but I think I'm running into that build issue you mentioned.
We can spend tomorrow getting this across the finish line. LFGGGGGGGG

@michaelthatsit - woops, it was missing an additional push - those commits are up so you should see LayoutSystem now

looks like the src/style.css got lost too! just noticed. we'll go over it after the meeting. it runs now tho!

looks like the src/style.css got lost too! just noticed. we'll go over it after the meeting. it runs now tho!

yea that's one of my TODO questions - i deleted that as part of the refactor 😅 - there's a few other choices i want to run by you so this meeting'll be useful - chat soon ~

@michaelthatsit - ready for re-review
some notes:

mrjsUtils grabs the utils as a submodule for function grabbing from the namespace
there's a slight different server visual - i'm still looking into why that's happening, lmk if you know off the top of your head and no worries if not

feel free to start running through it as an official review while i look into the above visual diff

reviewed with @michaelthatsit , pr 💣 is a go


Sorry, the response was filtered by the Responsible AI Service. Please rephrase your prompt and try again.

Copilot Chat Extension Version:
VS Code Version:
OS Version:
Logs:

Steps to Reproduce:

I have the same issue when asking basic questions about a docker compose file. As the questions are basic, and the code is pretty standard, it will, of course, match publicly available code. I have enabled the matches in my account (Settings>Copilot>Suggestions matching public code (duplication detection filter)) and it's still blocking the responses.
This is a major turn down for me, I have been using this extension for over 2 years, and now it has become useless thanks to this feature. I might even consider cancelling my subscription and using something else.

Please include screenshots of your question and answer plus the logs from CMD/CTRL + SHIFT +U -> GitHub Copilot Chat

Here's my chat history:

The logs for this message are these:
2024-08-02 12:51:40.509 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 687 ms
2024-08-02 12:51:44.915 [info] [streamMessages] message 0 returned. finish reason: [content_filter]
2024-08-02 12:51:44.916 [info] [streamChoices] request done: requestId: [1691d64e-862e-4c8a-8be1-58eb0ec560f8] model deployment ID: []

I have allowed the suggestions matching public code:

Thanks @AdrianCarreno. This was actually filtered incorrectly by our profanity filter and we're working in the background to tune the filter so this doesn't happen again. Additionally I have made a change so that the UI message does not incorrectly state this matches public code when that was not the filter applied here.


Improvement for k8s.io/docs/concepts/services-networking/service/ : Remove the AWS cloud provider bias

This is a...

[x] Feature Request
[ ] Bug Report

Problem:
There are AWS examples in these docs, but no Azure/etc examples.
Proposed Solution:
Add some Azure/etc examples. AWS isn't the only cloud out there by far. There's no reason to be biased towards it when Azure has its own managed Kube service offering, for example.
Page to Update:
https://kubernetes.io/docs/concepts/services-networking/service/

This links to the wider cleanup / reorganisation from #3735

/language en


Attach Light: Light attached to NPC is not disabled when they enter a new cell

When using a custom display with "Lights attached" for an NPC and the NPC enters a door, switching cells, the light is not disabled (it stays at the door entrance).
Mod in question: https://www.nexusmods.com/skyrimspecialedition/mods/85575
Video for reference: https://imgur.com/zFZufXt

Looks like a vanilla bug, behaves the same with vanilla and IED-attached lights (see video). In my test case, the light disappears after a few seconds.
https://www.youtube.com/watch?v=A40IiBzOCRU

Hmm. It probably is yeah. Could also be some other mod in my load order, since the light stays a bit longer. Light Limit Fix maybe.
I "fix" it by also changing cells.

Actor lights have an netimmerse object (attached to the skeleton) and a separate, light-emitting object (BSLight) that follows the former around. The light-emitting object is problematic since it won't get cleaned up until the actor 3D unloads which typically doesn't happen when it transitions from exterior to interior cells - for example, that npc that walked into the bannered mare still has its 3D loaded.
So yeah, this issue is present for any actor-attached light. IED would need to explicitly clean up (and then re-add) the light in such cases and the engine would have to be patched to do the same for vanilla lights.

I understand.
Does this happens with torches too?
Well, not sure if this falls in the scope of the mod or if it's something easy to do. Personally, it doesn't bother me much.

Does this happens with torches too?

Yes. As long as the torch 3D is loaded, even if the actor is in another cell, the light remains at the position where the actor exited the load zone. It really easy to test this with console commands, i.e. .cast or .equipitem (see the brief console popup in the video i posted).

Well, not sure if this falls in the scope of the mod

It's a bit of a grey area. I tend to shove in fixes relevant to the mod (VanillaLightCellAttachFix for example), but It would be better to just release a separate mod.

if it's something easy to do

I doubt it

Sounds like a good mod idea if you are up for the challenge. haha


Torch dynamo Could not infer dtype of NoneType

Do to some recent changes to the torch backend (I think we enabled compilation by default?), a simple torch fit() call with dict inputs will fail.
https://colab.research.google.com/gist/mattdangerw/5f966e9a35667396819efe13d0fa6980/torch-error.ipynb
The direct error is Could not infer dtype of NoneType, but the stack trace makes it look like the dm-tree library is involved.

@kiukchung Would you mind taking a look? Thanks!

Yes, we’ve recently enabled dynamo compilation for the torch backend (previously we’d always run in eager mode). When jit_compile=True the pytorch backend will attempt to compile your model. To run in eager mode set jit_compile=False or “auto”.

Thanks! I still think this would qualify as a bug though.
This code snippet is a basic use case, feeds dictionary input into a model.fit call, and works on other backends without issues.
I suspect this is to do with dm-tree issues you were mentioning at some point, but we should figure out a fix of some sort.

I think the basic use case should be jit_compile=“auto” since it would default to the most natural run-mode for each framework (jit compiled mode for tf and jax and eager for torch)
The dm_tree issue isn’t exactly what is causing the exception, rather it is causing graph-breaks (does not manifest as python errors) and therefore leads to poor performance as graph breaks runs in python-land and therefore loses out on compiler optimization opportunities.

Do you understand what is causing the error? At a high-level this looks like it still be valid Keras code, do we expect this to not compile correctly?
(I can dig in more too, just trying to grok if this is "works as intended" or not)

I’m on PTO so would have to take a deeper look when I get back next Monday but from the stack trace this looks like a tracing error.
With dynamo, tracing can be a bit contextual so depending on the combination of keras APIs called (in specific order) and the type, dtype, and shape of the inputs and intermediaries, it could lead to tracing errors, guard failures (and therefore graph breaks) or legitimate graph breaks. There isn’t a great way to absolutely, 100% always guarantee that all keras usages be dynamo compatible. That’s why with jit_compile=“auto” (the default for keras trainers) we run with eager for the pytorch backend and only run with dynamo if the user wants to see if their particular usage will see speed ups with dynamo.
This is in part due to the way dynamo is designed. PyTorch’s intention is basically follow this path:

run with eager for maximum compatibility (basically everything works pretty well on eager with ok performance)
try dynamo, if it works out of the box great.
Otherwise you put in the effort to make your code compatible with dynamo. Presumably the more effort you put to remove graph breaks and such, the better perf you’ll get. But ultimately it’s up to you to decide how much effort you want to put into it.

This is fundamentally different from how JAX works since it’s basically all or nothing with JAX. If it runs then you can leave it up to XLA to give you the “best perf” but you need to make it compatible for even the first run to execute.

Thanks! This is really helpful to get the lay of the land.


use punycode instead of idna

because idna in python cannot encode string exceeds 63 characters.

Coverage remained the same at 100.0% when pulling 6fb5db9d70e7c3ee66caee7a3bcaf0bc6fe716ed on punycode.encoding into ec2af723c027b4e467ebf362544d50a69a67c6d9 on master.

lgtm

lgtm


[akash provider run] --bid-deposit isn't working

versions tried:

v0.12.1
0.12.2-7-gbd78206
0.12.2-8-g4a5dc5c

The only way to make it work was to rebuild the akash binary with this change:
akash$ git diff
diff --git a/x/market/types/params.go b/x/market/types/params.go
index 5a5c2a7..eedbd29 100644
--- a/x/market/types/params.go
+++ b/x/market/types/params.go
@@ -9,7 +9,7 @@ import (
 var _ paramtypes.ParamSet = (*Params)(nil)

 var (
-       DefaultBidMinDeposit        = sdk.NewCoin("uakt", sdk.NewInt(50000000))
+       DefaultBidMinDeposit        = sdk.NewCoin("uakt", sdk.NewInt(5000000))
        defaultOrderMaxBids  uint32 = 20
        maxOrderMaxBids      uint32 = 500
 )

Discord discussion
https://discord.com/channels/747885925232672829/784452434604982283/888526827621060629

fixed by https://github.com/ovrclk/akash/pull/1375

We should add the fix to the next mainnet release as well.

This should be fixed in v0.14.0.


Recovery from insufficient quorum

Background: https://airtable.com/tblD3oZPLJgGhCmch/viw8IfZMg9Up8SP33/recsHpZ7MFNX8Y9lX
PM: @rolandcrosby
Eng Partner: @m-schneider

Moved to 2.2.

@johnrk I think this can be closed since it refers to an old Product roadmap item that was never worked on (at least according to AT?), by people who are no longer with the company.  Do you agree?  If yes, I'll close.

This actually looks like an I/O and Recovery Item.
cc @mwang1026

Close it for now. Even if we build this tool we'd likely want them to reach out to support anyway until we flesh out the feature.


Test menu android

From<EMAIL_ADDRESS>on January 21, 2011 08:17:56
What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? I can not get the reference of the menu buttons What version of the product are you using? On what operating system? 2.1 windows Please provide any additional information below. I would like to conduct tests on an application that also has the menu, but I need to know the position of the menu buttons, automatically via robotium
Original issue: http://code.google.com/p/robotium/issues/detail?id=56

From<EMAIL_ADDRESS>on January 21, 2011 11:56:18
If you open the menu by using solo.sendKey(Solo.Menu); then you can use solo.getCurrentTextViews() and you will get all the text views in the menu in an arraylist. You can also use solo.getViews() to get everything in the menu.
Status: Invalid


missing license for iamcal/emoji-data

iamcal/emoji-data

This is already attributed.
"Emoji datasource provided by Cal Henderson"

The project is under MIT license and its condition is:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

added link


Use a CI for ansiblecube

In addition to plugging us to the CI, this commit also introduces a test, asking ansible to verify the syntax for all of our roles.

We should add a test to verify that the *.fact files are valid JSON.

So I've rebased this branch, and added a few checks:

all the *.fact files are now checked to make sure they are valid JSON
all the *.j2 files are now checked to make sure they are valid Jinja2 templates

I'm not entirely sure about the latter, but it seems to work and correctly report the obviously broken templates I've tried.
All tests pass right now because the whole repo is clean (kudos!). Merging this will help ensuring that the repo keeps clean. :smiley:

Great ! Thank for your help. Nothing else to merge ?

Nothing else to merge ?

This should be good to merge right now.
I have some more checks I'm working on, but they aren't ready to be merged yet, so I'll submit them in a future pull request.


docs: Improve issue template.

I think using yaml instead of markdown is way better for user experience because it allows things like required fields, checkboxes and non-modifiable text :D I got a bit of inspiration from Neovim's issue template.
I also removed the "Describe the bug" section because there was a lot of overlap with the "To reproduce" and "Additional context" fields. Also, "Actual behavior" seemed to be missing which is why I added that instead.
I created a repo for you where you can test this out: https://github.com/smjonas/test/issues/new/choose
Let me know what you think!

Fwiw, this is much harder to use on mobile and straight up doesn't work in the GH app. (It loads the browser.)

When I open the link on mobile I am simply redirected to the website (probably this is not implemented in the app yet). Filling it out there works just fine for me.

Thanks for the PR! I might defer this change until it's out of beta; at the very least until I finish pushing out some other features.

Btw, I don't think this feature will be out of beta anytime soon :D It's been in beta since at least July of last year. Both Vim and Neovim have since adopted it.


Update eslint to the latest version

Coverage remained the same at 94.892% when pulling b26a9726a3a9984dce1611f04554562caea43c14 on greenkeeper/eslint-4.2.0 into ee2ee50742557dba144074ceb3fab23bbfdb78a2 on master.


Is it possible to extract Monitors from an Docker image of Uptime Kuma?

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Is it possible to extract Monitors from an Docker image of Uptime Kuma?
In what directory are the Monitors stored in and is it possible to migrate them to a different Uptime Kuma server (I have switcehd from Docker to Windows Portable version)?
I'm not able to create a backup as I can not access the previous instance of Uptime Kuma, but I have created an Docker Image before my server crashed.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.1
💻 Operating System and Arch
Windows Portable
🌐 Browser
Brave
🐋 Docker Version
No response
🟩 NodeJS Version
No response

You can copy the ./data/ folder and paste it into your new Uptime Kuma and u are good to go!

You could also export the monitor json via the settings -> Backup -> Export Backup which allows you could use to also Import for Disaster Recovery purposes.

@devunderslash as warned on the site you mentioned, the backup feature has been left unmaintained for quite some time.
Please make a backup of the database instead  by shutting down uptime-kuma and copying the data folder.
See

Will back up be updated  or removed from the system instead or revamped updated again

See https://github.com/louislam/uptime-kuma/pull/2667

Closing as backup has been dropped lacking maintenance in v2.0
A new attempt must be developed with the native backup feature of the db used (sqlite/mariadb) in mind instead.


Escape dir vars when calling COMSPEC cmds

COMSPEC commands fail when called with unescaped directory arguments which contain white spaces (typically a compound user name).
This PR closes

lukesampson/scoop-extras#1781
lukesampson/scoop-extras#2389
#2801

Add this to PR description:
- Closes lukesampson/scoop-extras#2389
- Closes #2801

Add this to PR description:
- Closes lukesampson/scoop-extras#2389
- Closes #2801

Done

You need to make it strict
-lukesampson/scoop-extras#1781
-lukesampson/scoop-extras#2389
-#2801
+- Closes lukesampson/scoop-extras#1781
+- Closes lukesampson/scoop-extras#2389
+- Closes #2801

Sorry, didn't know!


Equinix Metal CCM Service Load Balancer IP not working

Describe the bug
Starting with kube-vip version 0.8.2 there's an error in the logs that shows "invalid CIDR address" for the Elastic IP used via the Equinix Metal CCM. The service / IP is not reachable.
Version 0.8.0 and older work fine.
time="2024-08-08T03:43:34Z" level=error msg="[invalid CIDR address: <IP_ADDRESS>/] error adding BGP host endpoints\n"

To Reproduce
Steps to reproduce the behavior:
Deploy kubernetes cluster via kubeadm on Equinix Metal with CCM. Install kube-vip via the following commands:
alias kube-vip="docker run --network host --rm plndr/kube-vip:v0.8.2"
kube-vip manifest daemonset   --interface lo   --services   --bgp   --annotations metal.equinix.com   --inCluster | kubectl apply -f -

Expected behavior
Kube-vip should be announcing the Elastic IP via BGP to its peers.
Environment (please complete the following information):

OS/Distro: Ubuntu 2204
Kubernetes Version: v1.30.3
Kube-vip Version: v0.8.2

Try adding --cidr 32 to the manifest call and see if that works.

@enkelprifti98  did the flag suggested by @cprivitere  work? If so then the fix to this issue is docs.


Adds a ' /' after a empty tag.

I'm a bit new to GitHub and never reported a bug before so sorry if this was already resolved
When I try to close a empty tag such as
, the result is
, I'm pretty sure the program is just trying to close an empty tag when in reality there isn't suppose to be one.

There's an option Make Never Close Elements Self-Closing you can turn off to disable this. Alternately, you can define a custom set of Never Close Elements without br to only disable it for that element


[PKG-3726] 1.2.6 initial build ❄

pyreadstat 1.2.6 :snowflake:
Destination channel: Snowflake
Links

PKG-3726
Upstream repository
Upstream changelog/diff

Explanation of changes:

Removed cross-compilation requirements
Swapped to Github sdist to include tests

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_ac6ecstluq/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:27: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_91uoirna4z/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:27: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_65thcgenfa/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:27: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found


Error notification: KBFS: Decrypting, verifying, and downloading...

Error text:

/keybase/Keybase.app is no a Keybase folder.  All folders begin with /keybase/private or keybase/public

This pops up every time I open any app.  Despite what the error message suggests, there doesn't actually seem to be a /keybase/Keybase.app directory.

Keybase GUI Version: 1.0.14-20160311170010+46770d9

Dup of #2314.


Crash on certain PM narrows

Repro:

I open the app (on iOS)
Choose "Private messages" from the drawer
Tap a recent message from "Notification Bot" to narrow to PMs with that user
crash

Not sure how far this generalizes, but it's happened 2/2 times for me so far.
Does the app have automatic crash reporting? Or is there something I can do to get you a backtrace?

I bet that has to do with "Notification Bot" being secretly not a member of the realm.
See the code for cross_realm_bots in zerver/views/home.py and in static/js/people.js.
I think probably the right fix for this is to replace the "Notification Bot" singleton with one-per-realm server side, but that may be enough work we should do a workaround in the meantime.

https://github.com/zulip/zulip/commit/850519b314957017d1f6e92ee4e7382a90c0600a should make it possible to access these in register_ret assuming that realm_user is in fetch_event_types.  Note that since that didn't exist in previous versions of the server, we'll need to check if the key exists in the response, and do nothing if it isn't there.
That said, since Zulip 1.6 is needed for a lot of mobile features, we quite possibly will just be requiring Zulip 1.6 to use the RN app.
@borisyankov is that enough information for you to fix this?

Absolutely. Will fix next.
@gnprice we do have error reporting installed via Crashlytics, but we also have to check if it works.

Now we have removed bots from users list and tested on current mater it doesn't crash.
But crashes on sending first message in narrow (will be fixed by https://github.com/zulip/zulip-mobile/pull/1413)

Closing as fixed.


[python] DataFrame read as Arrow is slower than TileDB-Py

On a large SOMADataFrame, the same query performed using TileDB-Py is faster than when read using SOMA.  I would have guessed they would be more-or-less the same.
Example:

data on S3, us-east-1
code run on EC2, c6id.8xlarge in us-west-2

Note that the difference disappears when accessing the same array, stored on a local (EBS) volume.
In [16]: import tiledbsoma as soma
    ...: import tiledb
    ...:
    ...: obs_uri = "s3://czi.bruce-public/cell-census/2022-11-19/soma/census_data/homo_sapiens/obs"
    ...: cond = "tissue_general=='spleen'"
    ...: attrs = ["tissue_general", "tissue"]
    ...:
    ...: TdbConfig = {
    ...:     "py.init_buffer_bytes": 4 * 1024**3,
    ...:     "soma.init_buffer_bytes": 4 * 1024**3,
    ...: }
    ...:
    ...: def read_tdb_py(uri):
    ...:    with tiledb.open(uri, ctx=tiledb.Ctx(config=TdbConfig)) as A:
    ...:       return list(A.query(cond=cond, attrs=attrs, return_arrow=True, return_incomplete=True).df[:])
    ...:
    ...: def read_soma(uri):
    ...:    A = soma.DataFrame(uri, ctx=tiledb.Ctx(config=TdbConfig))
    ...:    return list(A.read(value_filter=cond, column_names=attrs))
    ...:
    ...: %timeit r = read_tdb_py(obs_uri)
    ...: %timeit r = read_soma(obs_uri)
3.57 s ± 169 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
4.54 s ± 1.12 s per loop (mean ± std. dev. of 7 runs, 1 loop each)

Run into the same issue on an internal dataset.


Add sub, div, mul, mod, and pow operations

Proposed Changes

Add sub, div, mul, mod, and pow operations
Handle divide-by-zero conditions in OP_DIV instruction

:x: Build concoct 0.1.48 failed (commit https://github.com/ConcoctLang/concoct/commit/98e87f2734 by @ldilley)

:x: Build concoct 0.1.49 failed (commit https://github.com/ConcoctLang/concoct/commit/2e387565f7 by @ldilley)

:x: Build concoct 0.1.50 failed (commit https://github.com/ConcoctLang/concoct/commit/e2ac1d9bcd by @ldilley)

:white_check_mark: Build concoct 0.1.51 completed (commit https://github.com/ConcoctLang/concoct/commit/c38648b757 by @ldilley)


Implement support for binding to service lifecycles

I'm not heavily experienced with services, so open to discussion on what REBIND and START_COMMAND should map to. Otherwise it's pretty straightforward.
Another thing: Service lifecycle callbacks aren't always void, which makes things a little awkward. Services are abstract usually, so the user needs to know to override the proper methods in RxService if they use it, which could not be obvious if they're not familiar with services. Thought about making RxService abstract, but figured it was obvious already and just made testing a headache.

I'm not particularly familiar with service lifecycle either. Maybe some of your coworkers can pitch in thoughts?

I'm a bit worried that this is not making much sense. It seems like Services are more complex than Activity or Fragment in terms of lifecycle.

This has been open a bit too long; if we want to re-examine this we can come back to it later.


[APIPUB-58]   Update docker images and nuget packages to remove vulnerabilites

Update alpine images to latest version

Vulnerabilities already fixed, the new version aspnet version added a new vulnerability and it doesn't have a more recent version to fix that.


kinect fusion for android

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

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

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

Required Info

Camera Model
{ D400 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Android

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{Java }

Segment
{3D reconstruction }

Issue Description
Is it possible to use kinfu function for 3D reconstruction on Android?

Hi @Tikitaka02  The rs-kinfu tool is a C++ program that will not work on Android.  However, the RealSense-compatible commercial 3D reconstruction software product DotProduct Dot3D has an android version.
https://www.dotproduct3d.com/

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

Case closed due to no further comments received.


allow passing HttpRequest, MulitMap params, MultiMap headers, etc. from REST call

allow passing HttpRequest, MulitMap params, MultiMap headers, etc. from REST call

+1 for this feature

I accept pull requests. :)

This is done.
You turn on ManagedServiceBuilder.enableLoggingMappedDiagnosticContext or ManagedServiceBuilder.enableRequestChain.
Or you enable the AOP interceptors direct see
https://github.com/advantageous/qbit/wiki/[Document]-MDC---Logging-Mapped-Diagnostic-Context,-RequestContext-and-HttpContext
Then you use RequestContext.getRequest()


Create a new release of the Bigtable library

As of 7 Aug 2018, the latest version of the Bigtable library on PyPi is 0.29.0 from 28 Feb 2018. Would it be possible to release a new version (and release new ones regularly) to pick up the latest updates and ongoing feature additions, please?
Thank you!
/cc: @sduskis, @ghaisa

There's one more change we need to make regarding AppProfile admin functionality that will be backwards incompatible.  We're aiming to be code complete by Monday.  It would be ideal to release after we commit the AppProfile changes.

Is there any update on this?

Version 0.30.0 was pushed to pypi.  Thanks @tseaver!
https://pypi.org/project/google-cloud-bigtable/


Add on_hold_at field to framework_agreements table migration

Used to signify when a framework agreement is on hold when being reviewed for countersigning.
Will need rebasing after Kev's previous commit has been merged into master.

I know this one is probably safe, but to keep the habit, should we release the migration separately?

When you say the migration separately you are referring to the just the migration file and therefore not the one line added to the model?

@idavidmcdonald yeah, the migration file should go first, before the model change

:+1: but let's hold off merging just until the previous code change is through, and do everything properly one step at a time.


Cleaned up and formatted examples, included license

I just cleaned up a few bits of formatting in the README.md, feel free to adopt these changes or drop them. I ignored the change log because no code was changed.
I also updated the licensing date in the Licence.md.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: DeadlySurgeon sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Hi @DeadlySurgeon thanks for this PR. Approve and merged


migration of svn-ignore to .gitignore

would be nice to have, else I always do this after svn2git:
svn propget svn:ignore -R svn://host/repo > .gitignore
git add .gitignore
git commit -m 'Convert svn:ignore properties to .gitignore.'

Um, this seem to me like an super easy solution... simply make a .gitignore inside each folder, populated with its svn ignore properties. There doesn't need to be some complicated aggregation of everything into a root level .gitignore


DllReferencePlugin doesn't work with HotModuleReplacement when the webpack config is not the same directory of dll bundles

Do you want to request a feature or report a bug?

What is the current behavior?
So we have two project in two repos, one for compiling and one for app itself. The dll config is in app directory, and webpack config is in compile directory.
app/
-- node_modules
-- dll/
     --- vendor.dll.js
     ---vendor.manifest.js
-- app.js
-- dll.config.js (used to generate dll bundle)

compile/
-- node_modules
-- compile.js
-- webpack.config.js

It works fine for initial build. Dll work well. However when it comes to hot load, hot replacement plugin cannot find dll reference and generate correct hot-update.json. like this:
var e = new Error(\"Cannot find module \\\"dll-reference vendor_2fbac64ff6173d91e522\\\"\")
Hot load only works when I move the part of webpack config that use DllReferencePlugin back to app directories, like this
app/
-- node_modules
-- dll/
     ---vendor.dll.js
      ---vendor.manifest.js
-- app.js
-- dll.config.js
-- webpack.dllreference.config.js

compile/
-- node_modules
-- compile.js
-- webpack.config.js (import webpack.dllreference.config.js inside)

I checked the context I've pass into DllReferencePlugin for both way, it's same because I'm always using process.cwd
If the current behavior is a bug, please provide the steps to reproduce.

my dll.config.js
import webpack from 'webpack';
import path from 'path';

const basePath = process.cwd();

export default {
  entry: {
    'vendor': [
       // list of vendor packages
    ],
  },
  output: {
    filename: '[name].dll.[chunkhash].js',
    path: path.join(basePath, 'dll/'),

    // The name of the global variable which the library's
    // require() function will be assigned to
    library: '[name]_[chunkhash]',
  },
  module: {
    // these loaders are needed for one of the vendor packages
    rules: [
      {
        test: /\.css$/,
        use: [
          'style-loader',
          'css-loader',
        ],
      },
      {
        test: /\.(jpe?g|png|gif|eot|svg|ttf|woff|woff2)$/i,
        use: [
          'file-loader',
        ],
      },
    ],
  },
  plugins: [
    new webpack.DllPlugin({
      path: path.join(basePath, 'dll/[name].manifest.json'),
      name: '[name]_[chunkhash]',
    }),
  ],
};

What is the expected behavior?
Hot Module Replacement plugin should find dll reference when making hot-update.json
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
node 6.9.5
webpack 3.4.1
mac os

Thanks for your report. It would be great if you reduce your issue to a small reproducible example. Best put this example into a github repository together with instructions how to get to the problem.

I'll try to make an example soon

@ethanyanjiali We are investigating a similar error Cannot find module "dll-reference dependencies".
Our current work around is to set cache: false Does setting cache: false resolve the error for you.
With cache: true we receive the error some times. @sokra If you are interested in viewing our error I can point you to a branch where the issue is easily reproducible.

@ldeavila "cache:false" where? what plugin?

@ldeavila cache: false can resolve this question, but rebuild become slowly.
Is there any other way?

add all vender lib into entry in your webpack.config.js。
webpack.dll.config
import webpack from 'webpack';
import path from 'path';

const basePath = process.cwd();

export default {
  entry: {
    'vendor': [
       'a', 'b', 'c' // lib
    ],
  },
  output: {
    filename: '[name].dll.[chunkhash].js',
    path: path.join(basePath, 'dll/'),

    // The name of the global variable which the library's
    // require() function will be assigned to
    library: '[name]_[chunkhash]',
  },
  module: {
    // these loaders are needed for one of the vendor packages
    rules: [
      {
        test: /\.css$/,
        use: [
          'style-loader',
          'css-loader',
        ],
      },
      {
        test: /\.(jpe?g|png|gif|eot|svg|ttf|woff|woff2)$/i,
        use: [
          'file-loader',
        ],
      },
    ],
  },
  plugins: [
    new webpack.DllPlugin({
      path: path.join(basePath, 'dll/[name].manifest.json'),
      name: '[name]_[chunkhash]',
    }),
  ],
};

webpack.config.js
import webpack from 'webpack';

export default {
  entry: {
    'app': [
       'a', 'b', 'c', 'src/index.js'  // add all lib into entry
    ],
  },
...others
};


Project update for uploading to PyPi

Looking pretty good so far, but I'm going to go back over this again tomorrow and fix some things.
Test PyPi upload here: https://test.pypi.org/project/cfde-submit/
The readme.md page doesn't render well, PyPi is really bad at that -- I'll switch that over to RST instead so it looks nice.
PR for https://github.com/nih-cfde/submission-workflow/issues/4

Ok, everything is looking good, uploading to regular pypi!


Add ⌘ + , keyboard shortcut to "Preferences..."

Changes

Add ⌘ + w key equivalent to "Preferences..."

Now it's easier to open Preferences Panel with keyboard shortcut

Before

After

Thanks @Takuro-Ito!


Add test for UserDefinedValueType

This is a minimal test for #477.
Fixe should be built on top of this test.

Inlined test case in #477 for PR cleanup.


Commission is being indexed, but not making it to the parser.

In this transaction
https://www.mintscan.io/osmosis/transactions/665FA8F1285CAD3434EA976CCDBBB7C529BDF802588E60BE9C0DE039CDD9E593

The Rewards, and the fees spent to get the rewards are making it to the CSV.
deposit,06/26/2023 18:56:58,73.632181,OSMO,,,,,staked,665FA8F1285CAD3434EA976CCDBBB7C529BDF802588E60BE9C0DE039CDD9E593,Address: osmo1dnmz4yzv73lr3lmauuaa0wpwn8zm8s209lezlz
withdraw,06/26/2023 18:56:58,,,0.009478,OSMO,,,fee,665FA8F1285CAD3434EA976CCDBBB7C529BDF802588E60BE9C0DE039CDD9E593,Address: osmo1dnmz4yzv73lr3lmauuaa0wpwn8zm8s209lezlz

but the commission is not.  However, it does look like we are indexing commissions.  I'm guessing this is a bug in the CSV parser.
https://github.com/DefiantLabs/cosmos-indexer/blob/main/core/tx.go#L47

The root cause of this one is that we seem to have been using a bad event to index these transactions:
See here:
https://github.com/DefiantLabs/cosmos-indexer/blob/85c63f73b0d0a58fee5771f4468ab69f40fa6700/cosmos/modules/distribution/types.go#L75-L82

For WithdrawValidatorCommission, we had set out to use the withdraw_commission event to grab the amount and receiver
We use this event to get the receiver key
We set the address of the indexed data to this field

The problem is that this event does not have this attribute in this version of the message:

Our code does not throw an error when an attribute is attempted to be grabbed but does not exist, we return an empty string instead which was causing the address to be an empty string.


Bug Fix

Necessary for database backup; otherwise overwrites existing records when testnet is reset.

:) I also just fixed this - I'm closing this as we already have the fix in


AggregateBy and Alerting

I'm submitting a ...

[ ] Bug report
[ ] Feature requestdd
[X] Question / Support request

Greetings,
Thanks for composing this awsome grafana plugin!
I am using Grafana 4.4.1 and grafana-zabbix 3.4.0. After reading the docs, I understand the implementation choice you have made.
But please clearify the alerting behavior when using aggregateBy function. Is it possible to setup alerting in this scenario?

Thanks,
Greg

Hi! Alerting feature uses only triggers data from Zabbix. This means you'll see alert only if the related trigger is fired in Zabbix. So alerts don't depend on changes you've made with data in Grafana. Alerts should be defined in Zabbix if you want to see it in Grafana.

@alexanderzobnin Thanks for clarification. Now I should consider to wirte my own prometheus collector to achive my goal.


Final presentation

Project Requierements - React App ( Crypto Watcher )
Choose API : Coin Stats ✅
Design : Guidelines ✅
Interactions
Home page ✅
Details page ✅
Testing requirements
Create unit tests for pure functions in your Redux code. ✅
Create integration tests for your application using the React Testing Library. ✅
Technical requirements
The project is a single-page application (SPA) built with React and Redux. ✅
The data retrieved from the API should be stored in the Redux store. ✅
You should filter the data that you retrieve from the API using a Filter stateless component. ✅
Every page (the main page and the pages for each item) should have a unique route within the SPA. ✅
The project should be deployed and accessible online using Render, Netlify or GitHub Pages. ✅
Project documentation
Description of the project. ✅
Live Demo of the project. ✅{https://crypto-watcher-9z4a.onrender.com/}
You should also highlight some interesting piece of code or something you built that you are very proud of. ✅
All linters have been checked! ✅

Live Demo of the project. ✅{**https://crypto-watcher-9z4a.onrender.com/**}


Adding env REF to specify the source

Current rpm master branch show version like this.
$ dest/bin/rpm --version
RPM version 4.14.90

But there is no archive here for that.
https://github.com/rpm-software-management/rpm/releases
The solution is to provide the way for users to specify commit reference (commit hash) as argument option of environment variable.
REF=4adc4f198cbc59b493a5f8a92e6e85b95c29719f or 4adc4f1 or master pip install rpm-py-installer

The test failed for current rawhide by this reason.
https://travis-ci.org/junaruga/rpm-py-installer/jobs/274206985
$ git clone REPO_URL
$ git checkout REF

Environment variable option GIT_BRANCH was implemented by https://github.com/junaruga/rpm-py-installer/pull/57 .
About the option GIT_TAG (tag name), GIT_REF (commit hash), it may implement those if there is a request from users.


expression virtual column indexes

Description
This PR adds support for using underlying column indexes for ExpressionVirtualColumn which have a single input column, similar to what ExpressionFilter can do in the same scenario. It achieves this a bit differently however. ExpressionFilter can make the filter expression itself into a predicate and push it down as a DruidPredicateFactory to the underlying DruidPredicateIndexes, if the expression evaluates to true then the value matches, if not then it doesn't. ExpressionVirtualColumn however is making arbitrary values which can be matched by other filters such as equality or ranges, and so instead needs a mechanism to supply its own indexes. So, we expose an implementation of DruidPredicateIndexes that can accept any DruidPredicateFactory, and then use the DictionaryEncodedValueIndex which exposes low level access to the dictionary and value indexes of the underlying column so that we can scan the values of the dictionary to use as inputs to the expression and then feed the transformed values to the appropriate type of predicate from the DruidPredicateFactory based on the output type of the expression.
I decided to push this all the way down to Expr, using the predicate index implementation as the default, but also allow individual expressions to produce more optimized index suppliers. I have currently only wired this up to IdentifierExpr, which can simply delegate directly to the underlying ColumnIndexSupplier because it is a direct column access expression. This means that an expression virtual column which just has an identifier should now be able to produce equivalent performance during filtering as if the column was used directly.
This measures pretty well, using a regex expression as an example, which in the first example uses no indexes and the second uses the new expression predicate indexes showed a decent performance boost (the virtual column performance should be approximately the same to using an expression filter or extractionFn directly, which also use predicate indexes).
SELECT string4, COUNT(*) FROM foo WHERE REGEXP_EXTRACT(string1, '^1') IS NOT NULL OR REGEXP_EXTRACT('Z' || string2, '^Z2') IS NOT NULL GROUP BY 1

before:
Benchmark                        (query)  (rowsPerSegment)  (schema)  (vectorize)  Mode  Cnt    Score    Error  Units
SqlExpressionBenchmark.querySql       40           5000000  explicit        false  avgt    5  279.224 ±  3.353  ms/op
SqlExpressionBenchmark.querySql       40           5000000      auto        false  avgt    5  274.911 ±  5.642  ms/op

after:
Benchmark                        (query)  (rowsPerSegment)  (schema)  (vectorize)  Mode  Cnt    Score   Error  Units
SqlExpressionBenchmark.querySql       40           5000000  explicit        false  avgt    5  194.301 ± 4.236  ms/op
SqlExpressionBenchmark.querySql       40           5000000      auto        false  avgt    5  187.447 ± 3.748  ms/op

This improvement allows us to make some changes to the SQL planner to prefer using ExpressionVIrtualColumn with other native filters over falling back to ExpressionFilter in many cases, since now there is no penalty to using a virtual column, which can result in more efficient plans, such as being able to collapse multiple filters on the same column, and also re-use expression computation.
For example, given a query like:

before this change would produce a rather inefficient set of expression filters that looked something like this, where effectively each separate expression filter would have to individually scan all of the underlying values in the dictionary to find the matches

but after some adjustments to take advantage of the improvements in this PR, will now plan to

because of the shared common virtual column expression, and only has to evaluate the indexes and compute the expression values a single time, and can be collapsed into an 'IN' filter because the planner can recognize the 'OR' of 'equals' pattern can be condensed into an 'IN'.

This PR has:

[ ] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

The only remaining coverage failures are on 'other tests' in 'sql-compat=false' mode because of some lines that never run in that mode, which i think we can ignore.

One thing I'm still thinking about is how to use the same strategy of #13977 and #15551 which allow automatically skipping using indexes if the cardinality of the underlying column is "too high" compared to the total number of rows to be scanned. The main problem is I haven't decided on the best way to expose the underlying ColumnConfig that controls these settings to the VirtualColumn index supplier method. I think its probably best to either make it available to ColumnSelectorColumnIndexSelector to pass in to the virtual columns, or available through any ColumnSelector which is  already passed into the virtual columns. Still thinking about it.


Implementation of Filesystem compact block repository

This is the implementation of the swift side of the FsBlock Cache.
Closes https://github.com/zcash/ZcashLightClientKit/issues/697
Closes https://github.com/zcash/ZcashLightClientKit/issues/720
Closes https://github.com/zcash/ZcashLightClientKit/issues/587
Closes https://github.com/zcash/ZcashLightClientKit/issues/667
Closes https://github.com/zcash/ZcashLightClientKit/issues/443
This code review checklist is intended to serve as a starting point for the author and reviewer, although it may not be appropriate for all types of changes (e.g. fixing a spelling typo in documentation).  For more in-depth discussion of how we think about code review, please see Code Review Guidelines.
Author

[x] Self-review: Did you review your own code in GitHub's web interface? Code often looks different when reviewing the diff in a browser, making it easier to spot potential bugs.
[x] Automated tests: Did you add appropriate automated tests for any code changes?
[x] Code coverage: Did you check the code coverage report for the automated tests?  While we are not looking for perfect coverage, the tool can point out potential cases that have been missed.
[x] Documentation: Did you update Docs as appropiate? (E.g README.md, etc.)
[x] Run the app: Did you run the app and try the changes?
[ ] Did you provide Screenshots of what the App looks like before and after your changes as part of the description of this PR? (only applicable to UI Changes)
[ ] Rebase and squash: Did you pull in the latest changes from the main branch and squash your commits before assigning a reviewer? Having your code up to date and squashed will make it easier for others to review. Use best judgement when squashing commits, as some changes (such as refactoring) might be easier to review as a separate commit.

Reviewer

[ ] Checklist review: Did you go through the code with the Code Review Guidelines checklist?
[ ] Ad hoc review: Did you perform an ad hoc review?  In addition to a first pass using the code review guidelines, do a second pass using your best judgement and experience which may identify additional questions or comments. Research shows that code review is most effective when done in multiple passes, where reviewers look for different things through each pass.
[ ] Automated tests: Did you review the automated tests?
[ ] Manual tests: Did you review the manual tests?You will find manual testing guidelines under our manual testing section
[ ] How is Code Coverage affected by this PR? We encourage you to compare coverage befor and after your changes and when possible, leave it in a better place. Learn More...
[ ] Documentation: Did you review Docs, README.md, LICENSE.md, and Architecture.md as appropriate?
[ ] Run the app: Did you run the app and try the changes? While the CI server runs the app to look for build failures or crashes, humans running the app are more likely to notice unexpected log messages, UI inconsistencies, or bad output data.

The code looks ok to me. I have few comments but mostly about changelog or documentation. Nice job.
I tested cases like this:

Full sync with fs cache.
Interrupted and resumed full sync with fs cache.
Sync which was started with previous code (from main branch), interrupted and then finished with fs cache.

All seems to work. I found one detail which works now but may not work in future.
I found it when testing case when sync was started without fs cache, interrupted and then resumed with fs cache.
Latest downloaded height is tracked in InternalSyncProgress. It may happen that blocks are downloaded and sync process is interrupted. When sync process is started again InternalSyncProgress assumes that there are some downloaded blocks which are not scanned. But there aren't any because cacheDB is removed on the app start. And we ask rust backend to scan blocks which are not there. It looks like that it works now and rust doesn't throw any error. But it may throw error in future. Maybe latestDownloadedBlockHeight in InternalSyncProgress should be set to latest scanned block.

Thank you for pointing this out! I added an integration test that attempts to recreate such scenario in a more or less reproducible way in this commit 3a9d78963f26dd6832110a2fe6a0a12ca32e1348

Tests passed
Test Suite 'Zip302MemoTests' passed at 2023-02-01 18:29:34.260.
	 Executed 20 tests, with 0 failures (0 unexpected) in 0.022 (0.046) seconds
Test Suite 'OfflineTests.xctest' passed at 2023-02-01 18:29:34.260.
	 Executed 167 tests, with 0 failures (0 unexpected) in 15.378 (15.442) seconds
Test Suite 'All tests' passed at 2023-02-01 18:29:34.288.
	 Executed 167 tests, with 0 failures (0 unexpected) in 15.378 (15.471) seconds
Test Suite 'AdvancedReOrgTests' passed at 2023-02-01 18:35:50.000.
	 Executed 11 tests, with 0 failures (0 unexpected) in 276.848 (276.851) seconds
Test Suite 'DarksideTests.xctest' passed at 2023-02-01 18:35:50.001.
	 Executed 11 tests, with 0 failures (0 unexpected) in 276.848 (276.851) seconds


Project Template for "Basic App" does not recognize RouteLoader [🐞]

Which component is affected?
Starters / CLI
Describe the bug
Using npm create qwik@latest with the Basic App Template creates a faulty project.
Even when none of the files are changed from the created template, Eslint still shows warnings about the RouteLoader when opening the project using VSCode.

'routeLoader$() are typically declared in route boundary files such as layout.tsx, index.tsx and plugin.tsx inside the src/routes...

The defined RouteLoader of the template is already inside the src/routes/layout.tsx file as the eslint rule suggests however the warning still persists.
Reproduction
https://github.com/someramsey/qwick-test-app.git
Steps to reproduce
Run npm create qwik@latest
Wait for Eslint to wake up
Open the directory on VSCode as the root workspace dir
System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 6.62 GB / 15.77 GB
  Binaries:
    Node: 20.12.2 - C:\Program Files\nodejs\node.EXE
    npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (123.0.2420.97)
    Chrome: 124.0.6367.91

Additional Information

The issue is possibly a local problem caused by this version of the Eslint Extension for VsCode

this might be an issue with eslint version. I can not reproduce this. I'm going to close it. I can hop on discord video call to go over it just ping me here or on discord


Dockerfile suggestion : AFTERBUILD

Most images have some sort of a final cleanup process or other commands that run on every image.
I think it as a supplement of the ONBUILD command it would be great if we had the AFTERBUILD as well so we could run it on every image the uses the FROM inheritance
for example
AFTERBUILD RUN apt-get purge -y --auto-remove && rm -rf /var/lib/apt/lists/* && apt-get clean
these would be for commands that would be run only after the final command in the dockerfile
please share your ideas and suggest improvements.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

From my understanding, that wouldn't actually make the final image smaller, right? The files are still embedded in the earlier layers. It would clean up the filesystem from a looking at it in the current state perspective, but it would not save space. The purge and rm would still need to be attached directly to an RUN apt-get install.

Can someone else confirm this ?
Maybe later I can run some tests as well

Per https://github.com/docker/docker/blob/master/ROADMAP.md#22-dockerfile-syntax I'm going to close this because modifications to the Dockerfile syntax are not allowed, for now.
@MHBauer is correct that this will just shrink how the rootFS will look, not the actual image itself.

How about some final security enhancements at the end of the build
as describbed here
https://gallery.mailchimp.com/979c70339150d05eec1531104/files/Docker_Security_Red_Hat.pdf
Remove setuid/setgid Binaries
page 23

Yes, you can certainly do those things and from a "final root filesystem" perspective its fine.  All @mhbauer was pointing out is that while the actions you take in this kind of "post build step" might be useful, if you're looking to shrink the side of your image then it won't work.

that was just one example,
I think there were few more cases where I needed to do the same task on all images after the build , but I will post back if I remember any worth mentioning

@vipconsult yea, and I think something like an AFTERBUILD feature might be interesting, but until the embargo is lifted on new Dockerfile commands we can't even really think about it.


Bump openstates to 6.20.6

Bump openstates to 6.20.6

No change to pyproject.toml? only seeing poetry.lock here

Hmm, I think I just did poetry update openstates and because pyproject.toml had openstates = "^6.20.5" It just updated with changing pyproject.toml. I will update it


rfc 3.0 architecture documentation

This is very much work in progress, and shouldn't be merged in this state.  I'm pushing this as a PR so folks can easily get their eyes on the doc/pictures and start to make suggestions edits.  This is based on Graham's initial branch with some quick cleanup on my end.  Note, the PNGs are exports from our (sorry, internal at the moment) google doc.  Once we have settled on images we can export the odp and put on to the repo as well...
Of note, I'd like to see someone write the section on the agent so it is of equivalent or more detail compared to what we had for hyperstart in 2.1.  Not sure, but perhaps @amshinde would be well suited for this?  Thoughts?
There are a few fixmes as well, which I figure will be easier to discuss during this RFC PR's review process.
Once we have input from folks, I'd recommend doing a giant squash and adding signed offs from the contributors.
Fixes https://github.com/clearcontainers/runtime/issues/392

@sameo @jodh-intel @mcastelino - if you have a chance to start taking a look.  @jcvenegas perhaps we can reference the proxy protocol in the proxy section?
@iphutch  -- early heads up and FYI that this is (in early stage of) the pipeline

Moved this document to https://github.com/clearcontainers/runtime/wiki/Clear-Containers-Architecture to facilitate better collaboration at this point in the review process.

@iphutch  - Can you start taking a look at this PR?

@iphutch -- Thanks!  Will start to address these now...

You might like to add in some Contributions-by: in the commit like we have here: 56e96d3b788dc91bf144e629c7200de98cbc5ff3.

This is looking really good - a visible improvement on the already rather good CC2.x document - so, kudos to everybody involved in the update.

I think we ( @iphutch ) may have mentioned the high-level-overview.png is not referenced anywhere - to note, it was referenced from the proxy README.md in the cc2.x repo, and thus I believe has been un-necessarily carried over (and there is a copy over in the clearcontainers/proxy/docs dir I think). Yes, it can be dropped from here.

I recommend adding a Kubernetes overall architecture guide including the shim/proxy/agent and how it works with crio.


tests/raftstore: rename panic api put/delete/seek etc to must_xxx

error is usual in a distribute system. if we panic on error, we name
the api must_xxx, so caller won't get a surprise on that behavior.

LGTM

LGTM


What do $T and $N mean?

I want to write a self configuration json file.
Here is the c++ code:
struct Point{
int x;
int y;
};
using ring = std::vector;
How can I write the correct json?

$T is template parameter, e.g. std::array<int, 5> $T0 is int
$N is array size, e.g. for int arr[5] $N0 is 5
Define Point like this: https://github.com/awulkiew/graphical-debugging-vscode/blob/master/resources/boost.json#L83-L91
As for the vector AFAIR by default it will be visualized as container of points. You may try to define std::vector<Point> as a ring like this: https://github.com/awulkiew/graphical-debugging-vscode/blob/master/resources/boost.json#L204-L211 with container's name $this. By default rings are clockwise, you may set cw to true/1/false/0 or ccw to true/1/false/0.

Thanks for the reply!
I find that the default json doesn't support const and reference type.And I write the flowing json:
       {             "type": ".*ClipperLib::Polygon.*", // ".*" for const and &             "kind": "polygon",             "exteriorring": {                 "name": "$this.tr_cache_.Contour",                 "type": "ClipperLib::Path"             }         },         {             "type": ".*reference_wrapper.*ClipperLib::Polygon.*",             "kind": "polygon",             "exteriorring": {                 "name": "$this.get().tr_cache_.Contour",                  "type": "ClipperLib::Path"             }         },
And I have to wait for half of minute to render one thunderd points polygon.Will there be something update for the performance and alias cv type?
Or Could I find an easy way to make an contribution for the project to support this?

Thanks for the reply!
I find that the default json doesn't support const and reference type.And I write the flowing json:
       {             "type": ".*ClipperLib::Polygon.*", // ".*" for const and &             "kind": "polygon",             "exteriorring": {                 "name": "$this.tr_cache_.Contour",                 "type": "ClipperLib::Path"             }         },         {             "type": ".*reference_wrapper.*ClipperLib::Polygon.*",             "kind": "polygon",             "exteriorring": {                 "name": "$this.get().tr_cache_.Contour",                  "type": "ClipperLib::Path"             }         },
And I have to wait for half of minute to render one thunderd points polygon.Will there be something update for the performance and alias cv type?
Or Could I find an easy way to make an contribution for the project to support this?

Regarding the performance: https://github.com/awulkiew/graphical-debugging-vscode/issues/2
Direct memory access is a lot of work.
Adding support for references, pointers and cv types should probably be easy. If you want to play with it one possible solution would be to parse variable's type only for C++ somewhere at the beginning of this method: https://github.com/awulkiew/graphical-debugging-vscode/blob/9fdd00e7ef9b686557404921e9ffe7bc5a9f5611/src/loader.ts#L1008 and to alter type and name based on the original type.

@manch1n cv types and references are supported in version 0.8. Could you give it a try?

It works well.Thanks a lot!


fix(Header): Fix image prop

Fixes #542.

Current coverage is 98.74% (diff: 100%)

Merging #545 into master will decrease coverage by 0.12%

@@             master       #545   diff @@
==========================================
  Files           108        107     -1
  Lines          1764       1754    -10
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           1744       1732    -12
- Misses           20         22     +2
  Partials          0          0

Powered by Codecov. Last update 650d1d8...e2dc488

Released in<EMAIL_ADDRESS>thanks!


Wand, Rod, and Trap should be equipment subtypes, not consumable subtypes

Wand is a consumable because it can be destroyed on use

Wand is a consumable because it can be destroyed on use

This is not correct. A wand is not a consumable because it is not destroyed when it expends its last charge. A wand, in many cases, is destroyed if it rolls a 1 on a d20 (after expending its last charge). The current implementation results in a user either having to:

use a wand, expending the last charge, the wand is immediately destroyed, and they have to roll a d20 and grab a new wand if it didn't roll a 1.
use a wand, expending the last charge, unchecking the Destroy property (so it might as well not be a consumable!), and then rolling a d20, removing the wand from their inventory if it rolled a 1.

Also horseshoes should not be consumable items either.


instanced rigid body is unaffected by physics after being changed to rigid from kinematic via script

Godot version
3.3.2
System information
Windows 10
Issue description
loading a scene as an instance with a rigid body set to kinematic mode, then changing the rigid body to rigid mode via a script, causes it to change the mode correctly, but the rigid body does not fall.
expected:
it becomes affected by physics and falls
Steps to reproduce
create a 3d scene with a spacial node, with a rigid body and mesh instance as children, save the rigid body as kinematic mode.
then instance the scene in the scene tree using a script, have it set the position up by 10, then change the mode to rigid using the same script, the instance does not fall.
Minimal reproduction project
No response

@Lexi-kelly Please upload a minimal reproduction project to make this easier to troubleshoot.

@Lexi-kelly Did you manage to find a solution to this issue? If so, please document it here to help other people who may be wondering about how to resolve this :slightly_smiling_face:


Typo fix

Fixed typo in documentation.

Good catch! :mag: :pencil2:
Thanks for your contribution @mMarzeta :rocket: :cake:
And thanks for the review @prostomarkeloff ! :nerd_face: :taco:


[FLINK-17655] Remove old and long deprecated TimestampExtractor

What is the purpose of the change
We remove the very old interface and API methods that use it.
Documentation

We remove the existing documentation.

Thanks for the review, @dawidwys! And thanks for reminding me to put it into the release notes.


Load UnityContent in a webworker

Describe the bug
It's not a bug but more of a query. Is there a way I can load UnityContent in a webworker on my frontend?
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
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]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Hi! I've never worked with WebWorkers. I'm not sure if it is possible, especially since Unity Builds can get quite large quickly. -- I will leaved this issue open for anyone who might be able to help you. If you're going to continue your search, I don't think it's necessary to search in the context of this module, you can search for Unity WebGL in general. If you find something interesting, feel free to let me know right here!