Add Swiftify Objective-C to Swift online code converter and Xcode extension to the new "Converters" category

Add Swiftify Objective-C to Swift online code converter and Xcode extension to the new "Converters" category.

I don't even knew that such thing exist like converter from Objective-C to Swift

You are welcome to check out Swiftify.
Of course, we can't guarantee error free conversion, but we aim to save a lot of efforts otherwise required for manual conversion.
A couple of man-years have been already invested in Swiftify, and the project is under active development.
And feedback is also welcome.

Well, even as a founder of Swiftify, I'll never accept a code produced by any automated converter to production without a manual review.
Generally, rewriting process consists of two phases: first simply replacing the syntax from Obj-C to Swift, then adopting new features that are introduced to Swift.
Swiftify is aimed at reducing the first half of the process.

Explicit typing for every argument, forced unwrapping of return types, etc ...
Explicit typing going to become configurable very soon, and ?? operator will be always used instead of explicit unwrapping shortly.

Also when moving away from Objective C you get to use some Swift stuff like Protocols, Generics, etc. that aren't "convertible" since they don't exist in Objective C.
Understandable, but I'd still argue with that:

protocols do exist in both Objective-C and Swift
Lightweight generics do exist in Objective-C, and we are currently working hard on inferring necessary type information when converting non-generic types (i.e. NSDictionary) to Swift generics (i.e. [AnyHashable: Any])

Of course, there are features that will likely be never supported (like most low-level C-like code).
Even there, we tend to provide the best possible output, for example - leaving some code like complex #define macros commented out in the output, so that it can be manually reviewed.

Objective-C protocols aren't comparable to Swift protocols IMO, and definitely not Objective-C's "Generics" with Swift's full-fledged generics system. There are things you CANNOT do in Objective C that are "basic" to do with Swift. Moving to a new language is the right time to reevaluate how to best use the language's features. This is just my personal opinion but a 1 to 1 conversion, despite it being an interesting learning tool and a great experiment, doesn't seem like could product actual production-quality code. If i'm wrong or not, that's a matter of preference for sure :)
Anyways looks like a great tool as I said! I would definitely use it to educate some people on moving from Objective-C and how their old code could "basically" look in Swift.

Sure, thanks again for the feedback!
Of course, I agree that writing idiomatic Swift code is generally a better approach, but there are still a lot of uses for Swiftify like:

education (like you have mentioned);
generation of code/library documentation in both languages;
delivering samples for using a specific library / SDK in both languages;
gradually moving existing projects to Swift on a per-file basis, i.e. using our Xcode extension;
etc.

Otherwise, understandable, and if you have more suggestions - I'm all yours :)

Just a quick update.
The following has been addressed:

Explicit typing for every argument, forced unwrapping of return types, etc ...
https://objectivec2swift.com/#/converter/

Now ?? operator is used for unwrapping return types, and the same will be soon applied to method or function parameters too:
Explicit typing has been removed when the type name is obvious to follow the Swift style guide from raywenderlich.com.

This is great. Nice work


Navbar popup menu doesn't close when going to new route in Vue

Hi - first up, I love this project. Really easy to incorporate into an existing site and very well documented 👍
One thing I noticed, however, was that in my Vue application, s in the navbar dropdown don't trigger closing the dropdown, so I have had to add workaround code to simulate re-clicking the button, but it's definitely not very elegant...
<div
  id="navDropdown"
  class="dropdown-menu dropdown-menu-right w-200"
  aria-labelledby="navbar-dropdown-toggle-btn-1"
  @click="closeMenu"
>
  ...
</div>

closeMenu: function() {
  const menu = document.getElementById("navDropdown");
  menu.click();
  // menu.firstChild.classList.remove("active"); // This seemed to work too but wasn't sure it was doing everything it needed.
  // menu.classList.remove("show");
},

I wonder if just widening the event.target.matches at  https://github.com/halfmoonui/halfmoon/blob/master/js/halfmoon.js#L312 would be better. I'll see if I can get that to work before creating a PR.

Thank you! The dropdown component should work right out of the box with Vue. I assume you are using the npm package, did you call the halfmoon.onDOMContentLoaded() method after your component is loaded? You can read more here: https://www.gethalfmoon.com/docs/download/#using-npm

Thanks for replying. I've tried various combinations of CDN and require/import, putting the halfmoon.onDOMContentLoaded() in App.vue and the component but nothing seems to work.
I tried starting from square one and creating a clean HTML page with the CDN link that didn't work for anchor links, but then I noticed that even on your site, clicking on the Github stars button, which opens in a new tab, doesn't close the popup. Maybe this is intentional, but it does seem to point to be the same thing.
It's been a long week, so I might be missing the obvious.

Sorry for the late response. I misunderstood what you meant previously. What you are seeing is basically the default expected behavior, i.e. it is intentional. I do realize some other libraries wire up the dropdown menus to close when a link is closed (like Bootstrap), but I feel that paradigm is a bit limited, especially if you want forms and other components inside the menu. The only issue is the one your rightly pointed out - going to a new tab is a bit awkward because the menu stays open. If you are adamant about closing it, I guess you could attach the data-toggle="dropdown" to the link, but I do admit that it's a bit hacky.

Understood. Thanks for taking the time to reply.


Random apostrophe added by script

The script adds an apostrophe to the top left of the page. there must be an extra one somewhere in the code. (see https://upload.wikimedia.org/wikipedia/commons/f/f9/Dubrovnik%2C_palazzo_del_rettore%2C_portico%2C_capitello_di_giorgio_orsini_03.JPG )

#13 should fix this I think


Modal Overflow and Scrolling Issue

Current Behavior
When users click on a deployment model to open a modal window on our website, the top part of the modal content is cut off and users are unable to scroll to see the entire content.
Screenshots

Expected Behavior
The modal window should be centered vertically and horizontally. Users should be able to scroll through the content if it exceeds the available height, ensuring that all content is accessible and visible.
https://github.com/user-attachments/assets/bbe78f2a-c0ab-4f58-bcd1-8b2d6bfa29a7

Contributor Guides and Handbook
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@antweiss @ctcarrier @ramrodo @hexxdump                                                                                I would like to work on this issue . Could you please assign this to me

This issue has already been raised: #1803
a PR for the same has been raised as well: https://github.com/meshery/meshery.io/pull/1805

okay


DetachedThreadLocal vs ThreadLocal

What are the advantages of a DetachedThreadLocal over a java.lang.ThreadLocal? Is it that there's not the danger of memory/class loader leaks?

The major difference is that you can access the state of Thread A from Thread B only by owning a reference to the instance of Thread A. This is not possible in thread locals. Also, the mentioned leakage avoidance as you do not store anything in a foreign instance.


Added support for testing multiple distributions.

Description
Introduces x-distributions that allows labelling APIs for various distributions and services. I propose we use opensearch.org for the default distribution, aos and aoss for the two Amazon managed services, and others can add their own.
If an API is not present in all distributions one has to list the distributions it is present in. I think it's better than having a negative list so that we can claim support for a well-known list of distributions in the spec and not have piecemeal support.
With this change, npm run test:spec -- --opensearch-distribution=amazon-managed passes against AOS 2.13.
Corrects semver checks for ranges with multiple values (e.g. >= 2.0, < 3).
Issues Resolved
Part of https://github.com/opensearch-project/opensearch-api-specification/issues/84.
Closes https://github.com/opensearch-project/opensearch-api-specification/issues/475.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Should we have opensearch.org as the default distribution for the test stories as well since it's the default in the spec?

Should we have opensearch.org as the default distribution for the test stories as well since it's the default in the spec?

I feel like we might really want both an "allow"/"include" and "deny"/"exclude" variant. As in the majority of cases all or most distributions will support an API and just aoss doesn't. So my thought is you'd generally by default want new tests/operations to be automatically opted into for all/new distributions and then whittled down as necessary. (Assuming we get automated testing against the managed distributions)

I've added include and exclude variants, etc., but no value validation in this PR. Please take another look?

Should we have opensearch.org as the default distribution for the test stories as well since it's the default in the spec?

I feel like we might really want both an "allow"/"include" and "deny"/"exclude" variant. As in the majority of cases all or most distributions will support an API and just aoss doesn't. So my thought is you'd generally by default want new tests/operations to be automatically opted into for all/new distributions and then whittled down as necessary. (Assuming we get automated testing against the managed distributions)

On this note. Do you @nhtruong @Xtansia have a (strong) preference for:

x-distributions-included, x-distributions-included and distributions: in tests.
...distributions:
   included:
   excluded:

in tests.
...distributions-included:
distributions-excluded:

in tests.

I think ideally we'd want distributions: {included: [], excluded: []} in tests, could still have distributions: ['foo'] that just shortcuts to distributions: {included: ['foo']}.
There might be better verbiage than (in|ex)cluded (something like supported maybe?) but I haven't come up with any other options I'm 100% happy with so not critical to this PR.

I think ideally we'd want distributions: {included: [], excluded: []} in tests, could still have distributions: ['foo'] that just shortcuts to distributions: {included: ['foo']}.
There might be better verbiage than (in|ex)cluded (something like supported maybe?) but I haven't come up with any other options I'm 100% happy with so not critical to this PR.

Made updates per comments and rebased. We can expand into includes and excludes for the distribution in a future PR.


Error , i didnt find in readme what i need

Still didnt find in readme what i need about that set remote url ,

Replace the origin repo url
using git remote set-url "" because when you type "ngh --no-silent" command by default it will publish to git origin
Somone can mybe give example?

https://github.com/angular-buch/angular-cli-ghpages#extra


Improvements on the python client

[ ] add logging feature
[ ] add linter (flake8 ?) in CI tests
[ ] change CraftAIClient name to avoid name redundancy (or export it as Client in the package setup)
[ ] investigate travis caching to accelerate test builds

cf #38 and #39


Correct example name to receiver.

A bridge would be from a client library to another system,
a receiver is for remote write to another system.
The adapter for influx makes this a bit messy, so try to
keep things sanish in the readme.
@juliusv The "bridge" here is what I want to get fixed up re the glossary.

@juliusv Updated as discussed

:+1:


[workbox-webpack-plugin] v3 Entries array passed to manifestTransforms is empty

Library Affected:
<EMAIL_ADDRESS>Browser & Platform:
node v8.9.1, npm v5.5.1, Mac OSX 10.13.2
Issue or Feature Request Description:
Title describes the issue, the manifestEntries array passed as an argument into manifestTransform functions is empty.
I've created a repo to illustrate the problem.  Here's a link to the branch with a minimal example reproducing the issue:
https://github.com/akash5474/workbox_ex/tree/manifestTransforms

I don't think you can use precaching for your HTML in that case. If you need to serve HTML that varies depending on some characteristic of the client's request headers, that's not nuance that you'd be able to represent with precaching.
You could use runtime caching instead, potentially with a stale-while-revalidate policy, and get some of the same benefits of taking network delays out of the rendering critical path after your initial navigation.

You can also just add a server side generated manifest:
importScripts('/server-side-manifest.js');

workbox.precaching.precache(self.__serverSideManifest);

Then you would have a service side endpoint that would respond to /server-side-manifest.js and return something like:
self.__serverSideManifest = [
    {
       url: "/",
       revision: "........................"
    }
];

You would need to create a revision that is a hash of the contents of '/' (i.e. if you change the output of '/' the revision value changes too).

importScripts('/server-side-manifest.js');

won't work, because precaching relies on there being a change to the top-level service worker file in order to trigger a new install event. Nothing in the top-level service worker file wouldn't end up changing if there were a hardcoded '/server-side-manifest.js' URL.
(The webpack plugin, which also relies on an external manifest, automatically inserts a statement into the top-level service worker that looks like
importScripts('/precache-manifest.[hash].js');

That [hash] string value is updated whenever any of the contents of the precached URLs change.)

@jeffposnick you are right is would need to be:
importScripts('/server-side-manifest.<revision>.js');

How do you feel about supporting the templatedUrls option with the insight from Webpack compilation? Currently with our setup, I'm generating this piece of information outside of the Workbox plugin cycle as a workaround to generate hash for the shell since it depends on Webpack generated files. Because Webpack hasn't emit anything real to the disk at the plugin stage, globbing won't work.
Instead of utilizing globbing, perhaps we can support looking into compilation.assets and generate the hash based on the content?

@raejin I can picture a scenario where that would be useful, not sure what the config options of that would look like however (and I'm a newb at Webpack). Could you open an issue with a proposal of a config that you think would fit this use case?

It would be nice if manifestTransforms would be also applied to the webpack-generated precache manifest. We have a situation that backend adds a prefix to some urls (but not all) so the generated precache manifest won't be correct. For example the generated manifest would have /css/app.css, but our backend provides it as /v/[hash]/css/app.css for cache busting purposes. If we added this prefix to each url, we could just use the publicPath option, but with this configuration, it is not an option.

ditto to @ottoo's suggestion.

Any updates regarding this?
Would love to see webpackManifestTransforms to be realized.

It's high on our list of planned changes for the workbox-webpack-plugin, but that work has unfortunately been delayed a bit as we get some new contributors up to speed.
The master tracking list for those updates is https://github.com/GoogleChrome/workbox/issues/1591

Hi @jeffposnick @gauntface..
I notice that adding manifest transformation to webpack generated assets is already on the roadmap for this project.
However I wanted to discuss my use case and wanted some suggestions on how to work around the same.
I'm using Next.js with workbox-webpack-plugin
Next emits the bundles / assets according to below folder structure:
client/build
├── bundles
│   └── pages
│       ├── _app.js
│       ├── _document.js
│       ├── _error.js
│       ├── index.js
├── chunks
│   ├── lazysizes_c7d1c726a13ef0281040919ab87052dd.js
├── precache-manifest.ea29d9a87efea6a22b482d6f07e9c0a8.js
├── static
│   ├── commons
│   │   ├── main.js
│   │   ├── manifest.js
│   ├── style.css
└── sw.js

Accordingly, the generated precache-manifest.[hash].js file is as:
self.__precacheManifest = [
  {
    "revision": "e17045946da6be83b2c8",
    "url": "bundles/pages/_app.js"
  },
  {
    "revision": "aafdbc9341182f758412",
    "url": "static/commons/main.js"
  },
  {
    "revision": "aafdbc9341182f758412",
    "url": "static/style.css"
  },
  {
    "revision": "01816bc9594df2c83999",
    "url": "static/commons/manifest.js"
  },
  {
    "revision": "7c5946399b2b21a5fc74",
    "url": "chunks/lazysizes_c7d1c726a13ef0281040919ab87052dd.js"
  },
  {
    "revision": "1e6a77ee5a8e6129f447",
    "url": "bundles/pages/index.js"
  },
  {
    "revision": "290487a965ccea8a6925",
    "url": "bundles/pages/_error.js"
  },
  {
    "revision": "e92680204ba0d06de76c",
    "url": "bundles/pages/_document.js"
  },
];

But Next.js serves above assets to very different paths, and so I need to transfrom the above manifest URLs to match the paths at which they are getting served by Next.js
For reference Next.js serves the emitted assets according to below sort of would-be modifyUrlPrefix mapping:
modifyUrlPrefix : {
  'bundles/pages/' : `/_next/${nextBuildId}/page/`,
  'chunks/'        : '/_next/webpack/chunks/',
  'static/'        : '/_next/static/',
},

My options currently AFAIK:

Write Express GET routes for serving assets URLs as mentioned in precache-manifest.js and respond with the corresponding URLs served by Next.js - I agree this approach feels very wrong
Somehow manually transform the generated precache-manifest.js file. - But I am not sure how to go about doing that

Kindly suggest how would you guys go about this problem!

Hi @jeffposnick @gauntface..
I notice that adding manifest transformation to webpack generated assets is already on the roadmap for this project.
However I wanted to discuss my use case and wanted some suggestions on how to work around the same.
I'm using Next.js with workbox-webpack-plugin
Next emits the bundles / assets according to below folder structure:
client/build
├── bundles
│   └── pages
│       ├── _app.js
│       ├── _document.js
│       ├── _error.js
│       ├── index.js
├── chunks
│   ├── lazysizes_c7d1c726a13ef0281040919ab87052dd.js
├── precache-manifest.ea29d9a87efea6a22b482d6f07e9c0a8.js
├── static
│   ├── commons
│   │   ├── main.js
│   │   ├── manifest.js
│   ├── style.css
└── sw.js

Accordingly, the generated precache-manifest.[hash].js file is as:
self.__precacheManifest = [
  {
    "revision": "e17045946da6be83b2c8",
    "url": "bundles/pages/_app.js"
  },
  {
    "revision": "aafdbc9341182f758412",
    "url": "static/commons/main.js"
  },
  {
    "revision": "aafdbc9341182f758412",
    "url": "static/style.css"
  },
  {
    "revision": "01816bc9594df2c83999",
    "url": "static/commons/manifest.js"
  },
  {
    "revision": "7c5946399b2b21a5fc74",
    "url": "chunks/lazysizes_c7d1c726a13ef0281040919ab87052dd.js"
  },
  {
    "revision": "1e6a77ee5a8e6129f447",
    "url": "bundles/pages/index.js"
  },
  {
    "revision": "290487a965ccea8a6925",
    "url": "bundles/pages/_error.js"
  },
  {
    "revision": "e92680204ba0d06de76c",
    "url": "bundles/pages/_document.js"
  },
];

But Next.js serves above assets to very different paths, and so I need to transfrom the above manifest URLs to match the paths at which they are getting served by Next.js
For reference Next.js serves the emitted assets according to below sort of would-be modifyUrlPrefix mapping:
modifyUrlPrefix : {
  'bundles/pages/' : `/_next/${nextBuildId}/page/`,
  'chunks/'        : '/_next/webpack/chunks/',
  'static/'        : '/_next/static/',
},

My options currently AFAIK:

Write Express GET routes for serving assets URLs as mentioned in precache-manifest.js and respond with the corresponding URLs served by Next.js - I agree this approach feels very wrong
Somehow manually transform the generated precache-manifest.js file. - But I am not sure how to go about doing that
Entirely exclude any webpack generated assets from landing in precache-manifest.js by providing an exclude/excludeChunks options, and instead picking them up by globPatterns so that I can then apply modifyUrlPrefix option on the generated precache-manifest.js - This might work (haven't tried yet) but I'm not exactly sure what disadvantages this approach might have or problems it might introduce

Kindly suggest how would you guys go about this problem!

Hi.
So to solve my problem I went ahead with option 2 (i.e. manually transforming the generated precache-manifest.js file).
So I had to write a custom webpack plugin - very much similar to that used in next-offline

Guys sorry but I'm running into an issue with document (HTML) (pre)cache updation using Next.
If anyone has tried Next.js with Workbox and has come across similar problem, please help - or please provide any suggestion in general.
Linking detailed issue here: https://github.com/zeit/next.js/issues/5553
Thanks 👍

Both modifyUrlPrefix and manifestTransforms will be supported in the Workbox webpack plugin v5, and will apply to assets created from the webpack compilation.

This should be addressed by the current Workbox v5.0.0 alpha.


Laravel Paginate Search of Filters like Datatables

Hi, @taylorotwell Are we getting any search/filters in laravel paginate anytime soon? That feature would be awesome. Also, improvisations on the paginate would be good in future releases as tables with huge datasets are quite a common thing to show on websites nowadays.

Heya, thanks for submitting this. This seems like a feature request or an improvement. It's best to post these at the laravel/ideas repository to get support for your idea. After that you may send a PR to the framework. Please only use this issue tracker to report bugs and issues with the framework.


Enhancment Idea - Virtual desktop sessions saves on reboot or click to open from previouse saved sessions

Have integration/ability to save Virtual desktop sessions after power off
Virtual desktop would be the best feature of windows productivity if only you could actually save the desktops and have the option to either have them start up on boot or the option to click on a saved session once booted and for all the windows/apps to start up again where you left off.

Hi @Aladdin1978
there is an open issue for virtual desktop and fancyzones https://github.com/microsoft/PowerToys/issues/2957
and one more generic and not limited to fancyzones https://github.com/microsoft/PowerToys/issues/1291
Feel free to add your comments there.
Closing this as duplicate.
Thanks.


Azure Subscription Access: Fix Role Assignment ID bug

Description
Incorrectly referencing an undefined variable/property.
Issues Resolved
[List any existing issues this PR resolves]
Contribution Check List

[x] All tests pass.
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] New functionality has been documented in CHANGELOG.MD

          1 Warning

:warning:
Should this include readme changes

  Generated by :no_entry_sign: Danger


m-cli: 0.2.5 -> 0.3.0

Description of changes

Update version.

Added meta.mainProgram so that this package works with nix run.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

~/C/nixpkgs on m-cli-update
❯ nix run .#m-cli -- info
ProductName:	macOS
ProductVersion:	12.3
BuildVersion:	21E230


[ci] Enable bazel remote caching

This commit runs bazel with remote caching enabled in CI. Only CI
master have write access to the cache. All other CI runs can read from
the cache.
Signed-off-by: Miles Dai<EMAIL_ADDRESS>

There shouldn't be a problem with people using the cache locally in their .bazelrc. I want to wait for a few days and make sure everything's stable there before recommending it widely.
AFAIK, there isn't a command to flush the cache. We would just go into the cache and delete everything.


Document contract changes needed for Bedrock specs

Document know-how for Bedrock level changes (comparing it to the current system) and leave them here.
Contract relevant: https://github.com/ethereum-optimism/optimism/tree/develop/packages/contracts-bedrock
The point of this issue is to provide know-how for the rest of the team.
Output should be resources and an understanding what the purpose of L1 and L2 contract is, how they fit in the grand schema of the system overall.

https://github.com/ethereum-optimism/optimism/blob/develop/specs/overview.md

As we all already know, Bedrock is not just an "update" is a completely new architecture. I will try to best summarize some insights I have gained, link some interesting resources I've found as well as try to point out specific differences if possible.
Spotted code/structural changes in particular
Despite using a new project structure and therefore new composition of contracts, contracts that seem to be the equivalent to the current system (e.g. L1CrossDomainMessenger.sol) try to sustain the same interface which is great. In the case of the crossDomainMessenger for example, they have the same method signatures in majority, despite using different parent contracts (inheritance). In general more usage of inheritance.
Still having some minor legacy contracts (seem to be completely identical to the current system, except of minor refactoring).
They use the quite new reinitializer of OpenZeppelin to upgrade & version their contracts and have a convention to have the contract version as constant on top of each contract.
They test their contracts partly via Foundry/Forge as well as hardhat (ts) as usual Some Solidity tests. Looks like they might be switching to Foundry mid-term.
In general it seems like they massively simplified their contract architecture. Looks like they have way less contracts in general.
Libraries in /rlp, /trie and those in the legacy folder seem to be identical to the current system. In general identical-named libraries to seem to be identical to a large extent (e.g. Lib_CrossDomainUtils).
Most contracts such as L2CrossDomainMessenger, L2StandardBridge, ..:

Now upgradable
Otherwise very similar besides using proxies & inheritance to abstract
In general many interfaces disappeared or are inlined
Better inline-documentation

Contracts purpose/architecture
Here is a list of markdown documentations of the current contract structure. I'll try to outline some key-differences below in conjunction with comparing the current system contracts and the new bedrock contracts.
L1 - Contract Overview (almost all of them are to be deployed behind proxies):

´L1CrossDomainMessenger` still exists
L1StandardBridge still exists
L2OutboundOracle (new): L2 state committed to this contract
OptimismPortal (new): Low level contract for passing messages between L1 and L2. No replayability, users should use L1CrossDomainMessenger instead.
ResourceMetering (new): Pricing updates automatically based on current demand (EIP-1559)
AddressDictator seems to be removed here
ChugSplashDictator still part of the legacy contracts
The whole L1/rollup/ folder with all its contracts seems to be gone (probably replaced by L2OutboundOracle).
TeleportrDeposit seems to be removed here
Bondmanager seems to be removed here

L2 - Contract Overview (almost all of them are to be deployed behind proxies):

L2CrossDomainMessenger still exists
L2StandardBridge still exists
L2StandardTokenFactory here moved and renamed to OptimismMintableTokenFactory here
OVM_DeployerWhitelist, OVM_L2ToL2MessagePasser, OVM_GasPriceOracle, OVM_SequencerFeeVault, iOVM_L1BlockNumber renamed to same name without (i)OVM_ prefix (L1BlockNumber now a contract)
WETH9, OVM_ETH still exist
TeleportrDisburser seemingly removed here

Universal
Some parent contracts that are used across the infrastructure, here.

Withdrawals:

Since that we discontinued funding the fast exit back to L1, this could now become cheaper:

"Address aliasing is now applied to withdrawal transactions as well as deposit ones.
There is a separate withdrawal root which allows withdrawal merkle proofs to be 60% cheaper (in L1 gas). This happens transparently, you just see less cost."
Source: https://community.optimism.io/docs/developers/bedrock/#deposits-from-ethereum-to-optimism
Further internal changes:

No longer a CTC contract. L2 blocks are now directly saved to L1 by using a non-contract address 0xDeadDeAddeAddEAddeadDEaDDEAdDeaDDeAD0001 to minimize L1 gas expense.
In Bedrock ETH is treated exactly as it is in Ethereum. Previously ETH was stored in a system level contract at 0xDeadDeAddeAddEAddeadDEaDDEAdDeaDDeAD0000.

Source: https://community.optimism.io/docs/developers/bedrock/#legacy-requests

guess this is obsolete as stale


求开源29x480p的ckpt。

stage3的ckpt可以开源下吗？

@LinB203

data 数据在huggingface还没有

stage3的ckpt可以开源下吗？

好的，已经开源到HF.

data 数据在huggingface还没有

请查看数据说明。https://huggingface.co/datasets/LanguageBind/Open-Sora-Plan-v1.2.0

hi @LinB203 et al.,
it seems the 29x480p ckpt has problems?
A young man at his 20s is sitting on a piece of cloud in the sky, reading a book.
EulerAncestralDiscrete_0___gs7.5_s20.mp4

This checkpoint should use lower cfg, e.g, 2.5.

hi @LinB203 et al.,
it seems the 29x480p ckpt has problems?
A young man at his 20s is sitting on a piece of cloud in the sky, reading a book.
EulerAncestralDiscrete_0___gs7.5_s20.mp4

This checkpoint should use lower cfg, e.g, 2.5.

Thx for ur reply! i tried cfg=2.5.

Could I ask what determines whether cfg is set higher (7.5 for the others) or lower here (2.5)?
In addition, it is observed that the color tone is indeed greatly improved and close to the real color, but on the other hand, it seems that the quality of the generated portrait and body is not as good as cfg=7.5 (like anime portrait but complete).

thx,
https://github.com/user-attachments/assets/5bb39c32-2639-4625-8337-ed8fa088061d


Setup Travis CI

User Story
As a developer, I would like to install Travis CI so that we have a CICD workflow.
Detailed Description
Install and setup Travis CI
Acceptance Criteria

[x] Given a push to master, then Travis CI runs before accepting the push.

Closing issue, merged into master (#27)

Closing issue, merged into master (#27)


DTSPO-13982 - Add helm publish action

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/DTSPO-13982
Change description
Add github action to publish new helm chart version to ACR if Chart.yaml is updated
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

why not just pull it from the git repo? that's what we normally do with all apps.
basically people merge their code and expect the helm chart to be updated.
we found that having flux automatically update to master code was far more reliable if the image had image automation on it.
does that make sense?

Yeah could that for sure. I'll submit a PR in cnp-flux-config


MudDataGrid: Fix HierarchyColumn button not clickable on glyph

Description

The button for display the detail row was not clickable if the mouse was exactly on the glyph (it seems it didn't work only on webassembly).
I have fixed the html and now the button is always clickable.
Fixes #5796
Fixes #6821
Fixes #7671
How Has This Been Tested?

For testing I have manually checked that the button is always clickable.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

Thanks @nicoarm93 !


Ability to choose fall-back font

Windows 10
Due to switch to DirectWrite information about fallback font (font linking, windows registry) is ignored. Quoting Microsoft:
"DirectWrite has fallback data that is not read from the registry or in any way configurable. In Windows 8.1, though, APIs have been introduced that allow an app to specify its own fallback. (It's similar to the WPF APIs for creating a composite font definition.)"
Is there a way to specify fallback font explicitly? If not - it will be very helpful to have, it is not always possible to use nerd font patch...

This is largely addressed by #957 and mainly just waiting for a reasonable implementation. However other issues have had priority for now, so I can't make any guarantees about when an implementation is going to land.


Move creation functions to _routines_creation.pyx

Based on #2935

Closing, we will resolve conflict in another PR. Raised an issue for that.


more generic pixel size handling

should work for the already defined formats as before and include many others.
Can't think of a case when this would fail right now, but still: it means that many more formats would be displayed if they pass the initial "filter" (are in component_2d_formats).
Also I guess the component_xbit_formats lists could then be removed from pfnc.py
Tested with mono8 and Confidence8 so far.
For the latter it needs to be added to component_2d_formats instead of component_1d_formats as well.

Thanks for the improvement. You've made the code cleaner and compact. I really like that!

This is just out of curiosity but could you show me an image of Confidence8 , please? Just drop an image file into the comment box here, then the image would be embedded as a comment.

There is a screenshot in our manual: http://doc.rc-visard.com/latest/en/stereo_matching.html#description-of-run-time-parameters
I can make an image with harvester once I'm on my other machine again.


Infer parameter names and types when applying Delcare Method codefix

Uses argument types from call site to define parameter types, after having widened literal types, in the same way as is done in the Extract Symbol refactor.
Uses argument identifier or property names from call site to define parameter names, or argN (as before) if no names are available at the call site:
const x = 1;
const y = "test";
m.m0(x, y, false);

    // result of  Declare Method 'm0':
    m0(x: number, y: string, arg2: boolean) : any {
        throw new Error("Method not implemented.");
    }

Notes:

IMO, it would be better to not explicitly define a return type, than to define any
Empty array literals yields undefined[] as type, which, while not wrong, might not be ideal either.

Fixes #22180
Edit: Added error throwing in the example, which has not changed in this PR.

 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: markusjohnsson sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

If my changes caused tests/cases/compiler/largeControlFlowGraph.ts to timeout, I would need some help to look at it. But I doubt that it was my changes that caused it. Is it possible to just re-run the test?

Thank you, @DanielRosenwasser . I've removed the parens. Somehow a test timed out again. When adding commits, should I squash all changes into one or is it OK lite this?

@DanielRosenwasser : Do you need me to do anything more with this before it can be merged?

thanks!

Trying to understand this pull request: where has the functionality of src/compiler/declarationEmitter.ts been moved to when it was deleted in cb5b773? The reason why I'm asking is because I'm trying to take another stab at #7546.


[Suggestion] : pythonscriptExecution

@technicaldada  I suggest to upload these screenshots.

Work fine with Ubuntu, Debian and BlackArch linux (tested)

Usage:
sudo -i  To root access.
cd hackerpro
sh intall.sh

chmod +x hackerpro.py
 python hackerpro.py

using chmod +x is very basic. thats why is didn't tell that. Thanks for support. Visit Our Blog for best hacking tutorials.


Processing of input proteins of interests

If we want to generalize the input for ProtEGOnist, we need to adapt the overview plot.
For this, we need to optimize the set of EGO graphs (cover set problem) to cover the majority of edges of the whole PPI.
Implement an algorithm that, for a given set of proteins, it minimizes the number of ego-graphs needed to achieve the best coverage possible.

Since processing this input is quite computationally heavy, the first solution is that the user provides the nodes of interest. The visualization should still provide an indication how much of the interactions are covered by the overview.
We will provide a script that for a given network, it returns the best possible coverage of the edges.


Fix use of uninitialized memory when unsetting flex property

This PR fixes a bug that can be reproduced on iOS 9.3 with v0.41.1 using this simple app. It's important to note that the bug pertains to uninitialized memory and is therefore not guaranteed to reproduce at all.
Description of the issue and fix
When a property on a node is set for the first time, we read and store the property's initial value before updating it. Later, if the property is nullified in JavaScript, we'll write the earlier-obtained initial value to the native representation.
In order to obtain the initial value, there must be a property getter that corresponds to the setter. If no getter exists, the slot to store the initial value will remain silently uninitialized. If the property is
nullified from JavaScript, we'll write the garbage value of that uninitialized variable into the native representation, and chaos will ensue.
This commit makes three changes to resolve this issue:

It adds an assertion that a getter exists every time a property is written. It would be better to enforce this statically, but I'm not aware of a means to accomplish this.

It adds a getter for the flex property, which previously lacked one. Prior to this change, setting then removing the flex property on a view would result in layout glitches and redboxes about NaN and Infinity in the bound and offset of a view.

It adds a getter for the on property for RCTSwitch, which can never be undefined, but is triggering the newly-added assertion.

There have been a number of complaints (#2616, #3406, to name a few) about transient redboxes with messages about illegal NaNs and Infinitys. Because this bug pertains to uninitialized memory which non-deterministic by nature, it's possible that a number of these difficult-to-repro issues will be resolved by this bugfix.
Test plan
Use the simple repro app to confirm that the issue has been resolved.
Concerns
I'm not in love with the idea of adding a dynamic assertion for asymmetrical (setter-only) properties. I would appreciate any suggestions of alternatives.

I discovered this issue when I was trying to figure out why react-native-foldview was repeatedly redboxing on iOS 9.3. It looks like other people have reported this, too. (cc: @jmurzy)
I believe that this regression pertains to commit 62177dbb3b4d4bdedf0c7a6fe9140ce049743fbf by @nicklockwood (reviewed by @javache), so it would be great to have either of your eyes on it.

Thanks for fixing this!

Thanks @javache.
I realized from the failing tests that my solution isn't quite acceptable. It requires that we discover all asymmetrical properties through the triggering of a runtime assertion, which isn't a sustainable approach. (By asymmetrical, I mean properties that do not follow the foo: + setFoo: convention.)
Some (but not all) of the boolean properties in the standard iOS libraries shirk the convention, opting for an isFoo: + setFoo: pairing. Furthermore, asymmetrical properties in third-party native modules can also trip this assertion.
At this point, I think it's useful to step back and revisit the challenge underpinning this bug. The challenge is that we have no consistent way to signal a JavaScript null value for primitive (i.e., unboxed) properties. To return to the flex example which led me to discover this bug, the flex property in Yoga is a primitive float. If the user defines flex: 1 in JavaScript then later sets flex: undefined, what value should we write to the primitive float?
The original attempt to solve this problem (in 62177dbb3b4d4bdedf0c7a6fe9140ce049743fbf) used a heuristic approach, opting to consider the initial value of the property to be its null representation. Our inability to read the initial value for properties that lack a getter led to the use of uninitialized memory, which is clearly a bug.
In an ideal world, we could mandate that all native props exposed to JavaScript be boxed types, but that ship has clearly sailed. To further improve the heuristic approach (while also avoiding a noisy assertion), I propose we do the following:

Stop using convention-based name-mangling to discover the getter and setter for a given property. Right now, we're constructing accessor selectors by tacking set onto a property name. The Obj-C runtime exposes reflection methods for this purpose; notably class_getProperty, which will return the customer getter and setter selectors if they've been overridden. If we switch to using proper runtime property reflection, we'll address the case above where boolean properties have overridden the getter to have an is prefix.

Fall back to intuitive null values for each individual primitive type. In the event that a getter simply doesn't exist, we should use the value that most intuitively reflects null. For numbers, this is the value 0; for C strings, the empty string; for ids, the value nil. This isn't perfect, but it's certainly better than using random data. The alternative is that we leave the assertion in and force developers (especially of third-party modules) to always provide symmetric native properties. If we proceed down this route, we'll have to consider this a breaking change.

I'd like to hear your thoughts. If you think the combined approach above is enough to lay this issue to rest, I'll code it up and update the branch. If you think we should treat asymmetrical properties as errors, we'll need to announce this change as breaking (and suss out whether there are any further asymmetrical properties in the core react-native libs themselves).

Actually, the simpler option here may be to use valueForKey which automatically checks methods like isFoo when finding a getter: https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/KeyValueCoding/SearchImplementation.html#//apple_ref/doc/uid/20000955

And I think it would be fine for this to be a breaking change. I haven't checked the internal tests so I'm not sure how much breakage this will cause, but perhaps to limit the impact of the breakage we could only enforce the assert for primitive type and default to nil for everything that's an object?

Actually, the simpler option here may be to use valueForKey which automatically checks methods like isFoo when finding a getter:

Except that we use this macro for all getting all sorts of types, so it doesn't play nicely with primitives.

Regarding valueForKey:... ugh.  I guessed it's an Apple-blessed heuristic for 'finding' a property, but that whole thing deserves to be burned to the ground. Could you explain a little more about this comment?

Except that we use this macro for all getting all sorts of types, so it doesn't play nicely with primitives.

According to the docs, valueForKey: will box primitives in either an NSNumber or NSValue instance, which requires additional logic for selecting the correct method for unboxing to the desired primitive type. I'm not entirely sure it's worth the added effort.
If we make this a breaking change, it's worth noting that it will impact almost all third-party modules, much in the way that 0.40 basically forced everybody to rev their modules. Are you really sure the RN team would be on board with that?

A simpler way to just avoid a crash here is to extend the RCT_CASE macro with a default param. This could be used when no default getter is found.

This PR appears to be abandoned. Closing for now.


Plugin failed to install package

I am having an issue getting rainloop to install plugins.  www-data owns everything, not sure what im missing.
Ubuntu w/Apache and latest version of Rainloop

What plugins do you want to install?

Change password (POPPASSD) to start with.  As well as Custom Login Mapping

Have you read this?
http://www.rainloop.net/docs/permissions/

Yes and they are configured as such.

Errors in php logs?


feat: add release notes for v1.8.0 release

Type of change:

[ ] Bugfix
[ ] New feature provided
[ ] Improve performance
[ ] Backport patches
[ ] Documentation
[ ] Refactor
[ ] Chore
[ ] CI/CD or Tests

What this PR does / why we need it:

Pre-submission checklist:

[ ] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?
[ ] Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

please ref: https://github.com/apache/apisix-ingress-controller/pull/1955

@AlinsRan Applied the suggestions

also need merge master.


Update AERONET data version

I wanted to highlight a question I asked on the issue: I'm not sure whether the dates in the CMORizers needs updating?
Description

Closes #3690
Link to documentation:

Before you get started

[x] ☝ Create an issue to discuss what you are going to do

Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[x] 🛠 This pull request has a descriptive title
[x] 🛠 Code is written according to the code quality guidelines
[x] 🛠 Tests run successfully
[x] 🛠 All checks below this pull request were successful

New or updated recipe/diagnostic

[x] 🧪 Recipe runs successfully
[x] 🧪 Figure(s) and data look as expected from literature

To help with the number of pull requests:

🙏 We kindly ask you to review two other open pull requests in this repository

I wanted to highlight a question I asked on the issue: I'm not sure whether the dates in the CMORizers needs updating?

@ESMValGroup/obs-maintainers Does anyone know the answer to this question?

I must confess I am not in the know, sorry - I only reviewed all that code from a technical side, maybe @catherinehardacre and/or @alistairsellar know, aside from the OBS team? :beer:

Hi @ehogan,
I'm happy to approve the date change in recipe_aod_aeronet_assess.yml so that it aligns with the DKRZ data. Thank you for tidying this up for us.
Regarding the cmorizer - I think you mean the date in https://github.com/ESMValGroup/ESMValTool/blob/main/esmvaltool/cmorizers/data/formatters/datasets/aeronet.py? (Which refers to the date when the Aeronet data was last accessed.) Technically for the code to run, this does not need to be changed. However, if the ESMValTool community would like everything to be aligned/look tidy, then this could be changed to 20240406.
Will the date in recipe_aod_aeronet_assess.yml (and therefore aeronet.py) need to changed for every release? If so this is not something I'd considered in the design... Are there similar requirements for other datasets?
Thanks,
Catherine

Hi @ehogan,

Hi Catherine! 😁

I'm happy to approve the date change in recipe_aod_aeronet_assess.yml so that it aligns with the DKRZ data. Thank you for tidying this up for us.

Super, thank you!

Regarding the cmorizer - I think you mean the date in https://github.com/ESMValGroup/ESMValTool/blob/main/esmvaltool/cmorizers/data/formatters/datasets/aeronet.py? (Which refers to the date when the Aeronet data was last accessed.) Technically for the code to run, this does not need to be changed. However, if the ESMValTool community would like everything to be aligned/look tidy, then this could be changed to 20240406.

There are other dates in esmvaltool/cmorizers/data/cmor_config/AERONET.yml and esmvaltool/cmorizers/data/datasets.yml too?

Will the date in recipe_aod_aeronet_assess.yml (and therefore aeronet.py) need to changed for every release? If so this is not something I'd considered in the design... Are there similar requirements for other datasets?

I don't think so, but would @ESMValGroup/obs-maintainers or @ESMValGroup/technical-lead-development-team be able to clarify, please? 😊

@ehogan - oops, I missed the other dates in https://github.com/ESMValGroup/ESMValTool/blob/baa34009a6332e9e3ca4c9e2a09e385394dca1e2/esmvaltool/cmorizers/data/cmor_config/AERONET.yml and https://github.com/ESMValGroup/ESMValTool/blob/baa34009a6332e9e3ca4c9e2a09e385394dca1e2/esmvaltool/cmorizers/data/datasets.yml.
I think these should all be changed to align with the DKRZ data, i.e. changed to 20240406. While the date in datasets.yml is just indicating that the data set has been recently accessed and should be 'live' (as per aeronet.py), in AERONET.yml , the date feeds into the formatted dataset and I think this should align with the DKRZ data.
So, for clarity and consistency, I think all dates should be the same. I hope this does not hold thing up for the release. I'm happy to pre-emptively approve this (but can also take a look tomorrow).
Thanks @ehogan :)

@ehogan - oops, I missed the other dates in https://github.com/ESMValGroup/ESMValTool/blob/baa34009a6332e9e3ca4c9e2a09e385394dca1e2/esmvaltool/cmorizers/data/cmor_config/AERONET.yml and https://github.com/ESMValGroup/ESMValTool/blob/baa34009a6332e9e3ca4c9e2a09e385394dca1e2/esmvaltool/cmorizers/data/datasets.yml.
I think these should all be changed to align with the DKRZ data, i.e. changed to 20240406. While the date in datasets.yml is just indicating that the data set has been recently accessed and should be 'live' (as per aeronet.py), in AERONET.yml , the date feeds into the formatted dataset and I think this should align with the DKRZ data.
So, for clarity and consistency, I think all dates should be the same. I hope this does not hold thing up for the release. I'm happy to pre-emptively approve this (but can also take a look tomorrow).
Thanks @ehogan :)

Thanks Catherine! All done in db59f2600 😊

Excellent stuff! And thank you @ehogan and @valeriupredoi  :)


Storage accounts should use infrastructure encryption

Description
As a TRE Administrator
I want to deploy TRE in a manner compliant with common regulatory frameworks, like NIST SP 800-171 R2 and Microsoft's built-in compliance initiatives for those frameworks
So that research takes place in a compliant environment
Acceptance criteria

[ ] New TRE deployments' storage accounts use infrastructure encryption
[ ] Existing TRE deployments are not modified

Notes
Existing storage accounts cannot be updated to support infrastructure encryption. A feature flag at the core TRE level might be required so that existing storage accounts aren't attempted to be upgraded. Perhaps this could also be accomplished with Terraform ignore statements, but I don't know those very well.

Hi @SvenAelterman @marrobi
I'm about to look at this one for our TRE instance, since we would like infrastructure encryption turned on.
Was planning to do something along the lines of:
resource "azurerm_storage_account" "stg" {

  ...

  infrastructure_encryption_enabled = true
  lifecycle { ignore_changes = [infrastructure_encryption_enabled] }
}

So essentially enabling infrastructure encryption on initial storage account creation, however if the storage account has already been created prior to the change, then it won't be enabled.  (since you can't enable or disable once created without destroying and recreating the storage account)
@marrobi Would this be acceptable for a PR?
Should an additional build variable be introduced as well to control the default behaviour?  Such as ENABLE_SA_INFRASTRUCTURE_ENCRYPTION=false
Thanks

@yuvalyaron does this overlap with the CMLK work #4002 that you have in progress?
@jonnyry I can't think of a reason it wouldn't want to be turned on, I presume its compatible with CMK. @SvenAelterman  any ideas? As long as no errors or risk of terraform recreating the storage account when it's turned on (main concern), lets always have it on, otherwise need to have the config flag with default to false.

@marrobi I don't think there's an overlap, they can coexist.
However, as mentioned here, changing this will force the creation of a new resource:
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/storage_encryption_scope#infrastructure_encryption_required-1

@marrobi OK thanks, I will draft something locally with the following pattern and test on an existing TRE instance that was spun up before the change:
resource "azurerm_storage_account" "stg" {

  ...

  infrastructure_encryption_enabled = true
  lifecycle { ignore_changes = [infrastructure_encryption_enabled] }
}

We could also add this as a double protection against storage account deletion, however this would be problematic for workspaces/workspace services etc since it would prevent them being deleted:
  lifecycle {
    prevent_destroy = true
  }


Restore AppArmor generation + fixes

Per request of @jfrazelle, I have combined my AppArmor changes into one PR.
This change restores generation+loading such that static binaries work again out of the box on Ubuntu.
The Engine's policy, only installed with the .deb packages, is now set to permissive. This will not enact any enforcement, but will allow us to gauge the impact of enabling this in a future engine release.
Documentation is also introduced.
The docker-unconfined policy is also unreverted here, as the principal issue with that commit had been an undefined failure mode should the profile not be loaded (this PR ensures the profile is loaded).
Finally, we introduce a couple safe changes to the docker-default policy. These deny /proc file accesses already denied via masks in libcontainer/runC. It also introduces a 'deny' rule for ptrace; ptrace had already been forbidden, this change simply causes the kernel's audit subsystem to ignore those failures (resolving complaints of 'AUDIT' messages whenever users ran 'ps' inside a container).

/cc @icecrime @jfrazelle

/cc @moxiegirl

ok let me try this..

this fixes static binaries, confimed.
LGTM

daemon/execdriver/native/apparmor.go could use some constants for the paths, but otherwise it LGTM.

We need this for CI I'll merge when I get to office but any last comments anyone?

hey sorry i will personally fix the docs in a follow up PR once the ci works merging

no worries @jfrazelle @ewindisch already incorporated stuff from the review on the last PR these last comments were nits...

cherry picked into #15091


openvpn script for vyos

Anyone has the openvpn script for vyos?

VyOS is not supported. Since it is based on Debian it's possible that the installer will work with small modifications, but I don't know.


[Feature] Customisation through subclasses [sf#35]

Reported by mgrazebrook on 2008-06-03 18:14 UTC
I don't like editing generated code if I can avoid it!
So I'd hoped to have wxGlade generate classes, but be able to specify a sub-class for instantiation - which I would write myself, importing it through 'extracode'.
That way the generated event methods would be abstract templates, overridden in the hand-written sub-class.
As stands, I can set the base class, name the generated class, but can't set the instantiated class to be a sub-class. So to get my event methods to run, I create a custom base class, generate the code, and delete the template event methods by hand so they no longer mask the real ones.
A related problem: My 'main' script calls the generated GUI. But I can only pass data to it through global variables. I know I'm being fussy, globals do the job just fine, and I'm never likely to instantiate two app instancess ... but globals are ugly!

Commented by dschwertberger on 2017-07-13 22:33 UTC
Not sure whether I got that right.
If you have a sub-class, then you have overwritten the handlers.
So actually, you want to avoid that a handler method is created by wxglade. It should be bound, but no name generated in order not to overwrite.
I'm not sure whether this is the way to go. As of now, it's best to implement the main application yourself and make it import a module where you derive from the generated window class.
For small glue code, it may just be fine to edit the handler in the generated file and to de-select "overwrite existing sources". This way it won't be overwritten.
Some better documentation is required. There's an old wiki page on this, but it's way too complicated.

Updated by dschwertberger on 2017-12-06 21:29 UTC

status: open --> closed
assigned_to: Dietmar Schwertberger
Group:  --> to discuss

Commented by dschwertberger on 2017-12-06 21:29 UTC
The documentation is now updated: http://wxglade.sourceforge.net/docs/source_code.html


Can't change the room

When I change the room in Apples HomeKit App nothing happens. It stuck in the default room. How can I change it?
In Eve App I can't change the room too...

I do not have this problem, try changing the mac address of Homebridge.

Do you have an iPad as Control Center?
If yes, reboot it and try again.
If that doesnt help try this:

Go to Settings > iCloud and disable "Home" on all devices, except your Control Center iPad.
Change rooms and namens on it and enable iCloud for Home again on the other devices.


Does this navigator support view caching?

Such that when user navigate between tabs view state is not lost.

Yes but it's not caching so much as we keep the views (React + native) in memory.

Will close since this issue is more than a year, feel free to a open a new if this is still a issue.


raspberry-pi/4: Add modesetting option

This adds a pair of option to enable and configure the vendor-specific modesetting driver for the Raspberry Pi 4B.
Usage
{
  imports = [
    ./nixos-hardware/raspberry-pi/4
  ];

  hardware.raspberry-pi."4".fkms-3d.enable = true;
}

Since we're using lib.mkBefore, even if a user has set fbdev (wrongly) in their videoDrivers it will use modesetting first. Adding fbdev ensures there's a fallback plan in case things break with modesetting in the future.
You'll know modesetting is enabled if you can configure the resolution of the display in your desktop environment.
There's also:
[samuel@pi4-nixdev:~]$ dmesg | grep -i kms
[    2.165923] vc4-drm gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])

Why are the overlays in-lined?

https://logs.nix.samueldr.com/nixos-aarch64/2021-05-12#1620854599-1620855129;

Basically, the overlay says it's compatible with brcm,bcm2835, so when we apply it with our tooling, it sees brcm,bcm2711 and (rightfully so) won't apply the overlay.
This is an upstream bug that is probably actually unfixable? Though maybe they could add two compatible entries... In that case we'd have to do more checks as right now the compatible checks in our deviceTree tooling is not great.
Though, with that said, in-lining the overlays gives us super-powers!! A NixOS option to configure the CMA! Though, sadly, users really don't need to customize the value. 512MiB is the biggest value one can give through dtparams.

I don't like how "4" needs to be quoted here. But if I follow the naming scheme of the directories in the option names (and I think we should, and be strict about it), then that's what we have to do.

I think @cleverca22 might be in a better position to review this. The only RPI4 I have access to at the moment 1000km away from me and headless.

@Mic92 I want your review as a maintainer. In case you had opinions about the Nix side of things :)
I should probably have specified.

Fair enough. I just happen to know that @cleverca22 worked with Raspberry-Pi graphic stacks on a very low level, while I can only review some module options from a high-level perspective without end-to-end testing.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/boot-config-txt-related-questions-for-raspbarry-pi/3650/4

In https://nixos.wiki/wiki/NixOS_on_ARM/Raspberry_Pi_4 it says that this will only work with the vendor kernel. How do I ensure that I am doing so?
Can anyone provide a sample configuration.nix that I can look at?

If you're including the configuration from nixos-hardware, it sets the default accordingly.

@samueldr yeah I was already using it. Turns out I needed to update the firmware.


How to prevent it printing anything when I import keras

Now when I import keras, it will show
Using Theano backend. 1 #define _CUDA_NDARRAY_C 2  3 #include <Python.h> 4 #include <structmember.h> 5 #include "theano_mod_helper.h" 6  7 #include <numpy/arrayobject.h> 8 #include <iostream> 9  10 #include "cuda_ndarray.cuh" 11  12 #ifndef CNMEM_DLLEXPORT 13 #define CNMEM_DLLEXPORT 14 #endif 15  16 #include "cnmem.h" 17 #include "cnmem.cpp" 18  19 //If true, when there is a gpu malloc or free error, we print the size of allocated memory on the device. 20 #define COMPUTE_GPU_MEM_USED 0 21  22 //If true, we fill with NAN allocated device memory. 23 #define ALLOC_MEMSET 0 24  25 //If true, we print out when we free a device pointer, uninitialize a 26 //CudaNdarray, or allocate a device pointer 27 #define PRINT_FREE_MALLOC 0 28  29 //If true, we do error checking at the start of functions, to make sure there 30 //is not a pre-existing error when the function is called. 31 //You probably need to set the environment variable 32 //CUDA_LAUNCH_BLOCKING=1, and/or modify the CNDA_THREAD_SYNC 33 //preprocessor macro in cuda_ndarray.cuh 34 //if you want this to work. 35 #define PRECHECK_ERROR 0 ... ...
I do not want it to be printed, because this log will be regarded as error in another program.
So, how can I do to prevent it from printing, including 'Using Theano backend.'
Thank you ahead for your help!

What is the other program ? How can any output messages be seen as an error... this is so wrong.
Anyway if you are using Linux or OS X you can still use bash redirection :
python train.py > /dev/null 2>&1

It will redirect both output and error messages to /dev/null.

@hadim It is a node.js module called python-shell which aims to run python code on the server. I have put issues on https://github.com/extrabacon/python-shell/issues/52 and  https://github.com/extrabacon/python-shell/issues/53. I am not so familiar with the stderr and stdout he mentioned in https://github.com/extrabacon/python-shell/issues/52. Could you have a look at that? I would be really appreciated if you can help me! Thank you so much

Well you could use this solution http://stackoverflow.com/questions/11130156/suppress-stdout-stderr-print-from-python-functions
It's an hack but it should work for you.

@hadim Thank you! It works now

Good.
Please close this issue.

Interpreting a child program writing to stderr as an indication that something went wrong is a widely used pattern, and IMO nothing is really gained from doing so.


[catalog] No description of License field

The SBOM Catalog's contributing docs don't mention the License field that appears in data.yaml.

I am working on a PR for this

Thanks for your contributions @funnelfiasco. It's great having you. For the time being, I just used the license field to distinguish between open-source and proprietary products. But please feel free to make any other suggestions. I hope to find some time for this project again soon.
Also, I've not written something in regard to the language field. The issue here is that there are overlapping data points that can be hard to figure out. E.g. Java, Kotlin, Scalacan work withMavenorGradle`. So each of these words could be synonyms... or not. Depending on the App evaluated 😅


Support for spark uncompressed event log files

Hi,
In the current setting Dr. Elephant supports only compressed format files for event logs for spark applications. Can this be extended to uncompressed formats as well?
Best.

Hi,
You can change app/com/linkedin/drelephant/util/SparkUtils.scala file to support both compressed and uncompressed files.
SparkUtils.scala.zip

Hi,
That helped. The issue is also present in #357, I wonder why it failed merging with master branch.

A merge request has been raised some time back by me. So Will not be needing that.


t >= 0 && t < n_classes failed. RuntimeError: cuDNN error: CUDNN_STATUS_NOT_INITIALIZED

when run the train.py, got this bug

This bug occurs when the ground truth masks have more classes than the number of classes in prediction. Please make sure you ground truth images have only 0 or 1 labels of pixels if you are training for binary segmentation. The datasets usually have the ground truth as 0 or 255 labels of pixels. So, please convert them to 0's and 1's.


Fix issue where #[cfg(...)] are not propogated to emitted debug implementation.

When using feature gates with debug derives, the generated debug implementation does not correctly cfg gate enums that should be cfg gated, resulting in code that does not compile with the given feature.
Fix this by making sure we emit [#cfg(...)] to the generated debug variants so that the code is correctly feature gated.
Fixes #19

I'm not an expert on proc macros, so if you have anything you'd like to see different, much appreciated!

Bump? @kupiakos I was hoping to get this soon, as there's some other changes that I'd like to merge in the igvm crate that needs this.

Sorry for the delay!


Push notifications

@csherron what's our stance here?

i never use push notifications but i think we should have them
can we get iOS to prompt an opt in when a user first opens the notification drawer?


ModuleNotFoundError: No module named 'models.post_processing.pse_v2'

these is no pse_v2

YES. Waiting for update.

YES. Waiting for update.

So, how long do I need to wait?

We have fixed this problem in last update.

We have fixed this problem in last update.

whether pse and pse_v2 are the same?

We have fixed this problem in last update.

whether pse and pse_v2 are the same?

yes, these two modules are same.


Allow operators to stop the full dataflow

Useful in case of emergencies.
Fixes #133

Thanks for reviewing!


Ajax help

Hello :)
I've been using this script on different projets, i found it very usefull !
However i never used it with ajax loaded content... Any help to "watch" some divs which were loaded after the script init ? (they all have the same class ".reveal")
Many thanks :)

Not using the jquery plugin, no. You should probably need to re-run .onScreen() once the new nodes are appended to the DOM. I'm rewriting onScreen as an independent library (no jQuery dependency) and this problem is solved in the new version.

woah!! i can't wait ! :) @silvestreh


Add support for processing PDF

Feature request
What are you trying to achieve?
I want to be able to input a PDF as a Buffer and resize it/save it to a DPF
When you searched for similar feature requests, what did you find that might be related?
There are no open issues like this
What would you expect the API to look like?
Same as all the other APIs
What alternatives have you considered?
Other libraries. They are slow
Please provide sample image(s) that help explain this feature
N/A

await sharp(imageBuffer, { page: 1, pages: 1 })
              .jpeg({
                quality: this.compressedImageQuality
              })
              .resize(this.compressedImageSize, this.compressedImageSize)
              .toBuffer();

[Error: Input file contains unsupported image format]

sharp can read PDF files when using a globally-installed libvips compiled with support for either poppler or pdfium.
https://sharp.pixelplumbing.com/install#custom-libvips
https://github.com/libvips/libvips/#optional-dependencies


Fixed Arabic translation.

Hello,
These are small fixes for the Arabic language.

@AhmadDakhlallah Thank you, again!
Please let me know how you'd like to be credited, or feel free to open another PR:
https://github.com/jointhefediverse-net/jointhefediverse.net/blob/main/translations/ar/ar.json


Updated Turkish translation

Except for the star names, all texts were translated into Turkish.
language_apology translation has been edited in accordance with the Turkish translation.

Thank you so much!

🤘🚀


AddEvent About

Hi Vladimir,
I have a new question.
I'm adding new event calendar but im refreshing after adding event.
I wont reload the page.
My question: How can i add event on calendar ?
I want it to add a new event (or delete event) when I press the button than i will import my project :)
How can i do this?
I'm looking "addEvent( event )" but i didn't it.

Hi @emrahnalci
Sorry, I'm not sure I understood your question correctly. If you need to add an event to the calendar you can use either addEvent, or refetchEvents if the new event is stored in the database and can be loaded from the server.


HTTP Dog API is offline, should we remove it?

HTTP Dog images are throwing error 500. Should we remove it from list?

Strange, when using ProxySite it still returns 500 for me

Strange indeed.
I'll leave this issue open for a few more days an monitor it.
Thank you for letting me know.

Your screenshot shown me that the website is actually wrong for me on Google Chrome

On Edge it works correctly

This may be some kind of extension or something local for me. Gonna close as it seems that it's just for me

It was really an extension, "CORS unblock".
Disabled it and now all works correctly


Can't start Pinpoint Daemons

[x] I have checked the FAQ, and issues and found no answer.

What version of pinpoint are you using?
master
Describe your problem**
Can't start PinPoint Daemons on my environment.
What have you done?
Steps you have taken to trigger the problem, for example:
I am follow the Quick Start Guide steps but I couldn't it run.
Case 1. When I hit the command on the Git bash for Windows. - works well
$ sh quickstart/bin/start-collector.sh
---check pinpoint-quickstart-collector process status.---
---initialize pinpoint-quickstart-collector logs.---
rm /c/Users/Hanhg/Desktop/pinpoint/quickstart/logs/quickstart.collector.log.
rm /c/Users/Hanhg/Desktop/pinpoint/quickstart/logs/pid/quickstart.collector.pid.
---pinpoint-quickstart-collector initialization started. pid=1158.---g
starting pinpoint-quickstart-collector. 0 /180 sec(close wait limit).

Case 2. Windows Prompt -- doesn't work
C:\Users\Hanhg\Desktop\pinpoint>quickstart\bin\start-collector.cmd
"Apache Maven (mvn) required."

I opened and read the start-collector.cmd  and quickstart.cmd so I could check it.

mvnw --version

C:\Users\Hanhg\Desktop\pinpoint>mvnw --version
Found "C:\Users\Hanhg\Desktop\pinpoint\.mvn\wrapper\maven-wrapper.jar"
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-25T04:49:05+09:00)
Maven home: C:\Users\Hanhg\.m2\wrapper\dists\apache-maven-3.5.3-bin\6rtk6r8hiu511erccgp64thica\apache-maven-3.5.3
Java version: 1.8.0_212, vendor: Azul Systems, Inc.
Java home: C:\Program Files\Zulu\zulu-8\jre
Default locale: ko_KR, platform encoding: MS949
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

mvn -version

C:\Users\Hanhg\Desktop\pinpoint>mvn -version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Users\Hanhg\Downloads\apache-maven-3.6.3\bin\..
Java version: 1.8.0_212, vendor: Azul Systems, Inc., runtime: C:\Program Files\Zulu\zulu-8\jre
Default locale: ko_KR, platform encoding: MS949
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Screenshots
If applicable, add screenshots to help explain your problem.
Logs
If applicable, please attach agent/collector/web DEBUG log that includes the part where you have encountered the problem. In case of agents, including the start-up log may be of great help.
Additional context
Add any other context about the problem here, such as affected library for agents, how your collector/web/hbase is set up if applicable.
My run environment
Windows 10 Enterprise edition
version 1809(OS build 17763.1158)
git --version
git version 2.26.2.windows.1

hi @erinyees
This seems to be caused by looking for mvnw as a relative path in Windows' command script.
First, if you run the start-collector.cmd in the quickstart/bin folder, it is expected to operate normally.
Please use in quickstart/bin folder until the issue is resolved.
I'm not good at cmd scripts, so it will take some time, but I will try to fix the issue.
thanks :)

Thanks. @koo-taejin
It works well!
I typed quickstart\bin\start-collector.cmd because the Quick Start Guide guide run like that.
How about additional comment? For example, like below

Note : If cmd command with relative path didn't works on your environment then try below case.
Move to ${pinpoint root path}\quickstart\bin and run the cmd

@erinyees
Thanks for the good opinion.
If you send the content as a pull request, I will merge it.
If you don't want pull request, I'll fix it.
please give me your opinion.
thanks :)

@koo-taejin
I will. I think I found solution about this problem by searching by the way.
https://stackoverflow.com/questions/14936625/relative-path-in-bat-script
I tested the %~dp0 and it works but some wrong comment printing both. You can see the state this link. If you don't mind can I pull request it after fix the cmd file command and wrong comment?

@erinyees
I have found out solution at cmd file related with each quickstart
for %%i in (%0) do (
   if not defined QUICKSTART_BIN_PATH (
     set QUICKSTART_BIN_PATH=%%~dpi
   )
)

In the code above, I have checked that dp is already used for relative paths.
I think this issue can resolve. If I update guide to put system variables for someone who want to execute in other folder
I will close the issue by including the content in the guide.
Thank you for your help. :)
thanks :)

@erinyees
I have updated the guide and included a link to see it on github.io.
If you think the issue has been resolved, please close this issue.
thanks :)


Reject disallowed store receipts (bug 1135261)

@mstriemer r?

or @muffinresearch r?

Looks good as long as the test

mmm, I refactored all code that relied on initialization of appSelf so that it gets the value more lazily but that patch became sort of epic. It removes some async madness from the tests which is nice though.

That grew significantly. I'm not sure I can comment on everything that was changed but it seems reasonable through a once-over.
What was the reasoning for the change, exactly? I guess previously appSelf was retrieved on startup and if the receipts.all() was used too soon it would blow up? Does this remove the need for that initialized event that would happen?

It is mostly a refactor job and a removal of some TODOs that are related to how appSelf is accessed. Yeah, whoops, it sort of became a big patch. The initialization was very in-app specific and now that we have app receipt validation it doesn't make sense. What this refactor does is push access to appSelf down to the code that actually needs it so that initialization errors are more lazy and occur at the point of access.

Looks good. r+wc

Thanks for taking a second look. I'm going to do a quick Marketplace test locally with it to make sure things are still working then merge it in.

Ugh, trying to make immediate callbacks async with setTimeout is blowing up the test suite and I can't track down exactly why. Looks like there may be a bug in there somewhere. However, I think moving to promises will make everything async by default.

Bah. My local Marketplace is hosed but this is working in the example app.


cefglue_gtk_linux_demo.deps.json has already been found but with a different file extension

Hi, all
I am new to Chromely.
I was trying to run the demo of "Chromely.CefGlue.Gtk.Linux.Demo" project as below.
$dotnet cefglue_gtk_linux_demo.exe
in my Ubuntu 18.04 machine.
And I am getting this error.
Error:
An assembly specified in the application dependencies manifest (cefglue_gtk_linux_demo.deps.json) has already been found but with a different file extension:
package: 'cefglue_gtk_linux_demo', version: '1.0.0'
path: 'cefglue_gtk_linux_demo.dll'
previously found assembly: '/home/user/Downloads/netcoreapp3.0/cefglue_gtk_linux_demo.exe'
Do you have any idea how to fix this?

@rhombask seems like a conflict in builds. Do you have more than one builds? I will clean up and rebuild again. Deleting all files in bin.
Also if you already publish the exe you do not need to use dotnet to run:
$dotnet cefglue_gtk_linux_demo.exe
What you need to do is:
$./cefglue_gtk_linux_demo.exe
Check this page for how to publish for more info.
Thanks.

I have Visual Studio 2017 and 2019 in my PC.
Did you mean this might cause problems?

It can be anything.
I assume then that you are publishing on a Windows PC and running on Linux. Right?
If that is the case, I do not see how that can be an issue as long as you are copying all your published files from the same folder to Linux.

Nop, I have 2 computers.
1st One
Windows 10
Visual Studio 2019(I uninstalled every other verions)
Build "Chromely.CefGlue.Gtk.Linux.Demo" project and copy the whole "Chromely.CefGlue.Gtk.Linux.Demo\bin\x64\Debug\netcoreapp3.0" folder to USB flash disk
2nd One
Ubuntu 18.04
mono installed
.NET Core SDK 3.0 installed via https://dotnet.microsoft.com/download/linux-package-manager/ubuntu16-04/sdk-current
Run the command below
(I did not publish as a self-contained application)
$ dotnet cefglue_gtk_linux_demo.exe
And I get this error below:
Error:
An assembly specified in the application dependencies manifest (cefglue_gtk_linux_demo.deps.json) has already been found but with a different file extension:
package: 'cefglue_gtk_linux_demo', version: '1.0.0'
path: 'cefglue_gtk_linux_demo.dll'
previously found assembly: '/home/jmson/Downloads/netcoreapp3.0/cefglue_gtk_linux_demo.exe'

Ok.
you can do the following:

Publish the exe - at least you will know you are not missing any relevant files. You can use Windows but the best result is to publish on Linux. You can use Visual Studio Code for that.
Rename the executable file in your project file -
https://github.com/chromelyapps/demo-projects/blob/4d244c427a843bafe0cb6dead1b900be36c2b694/regular-chromely/Chromely.CefGlue.Gtk.Linux.Demo/Chromely.CefGlue.Gtk.Linux.Demo.csproj#L11


kubernetes: add doc on adding self-signed registry certificate to k8s…

… worker nodes

closing in favor of: https://github.com/coreos/tectonic-docs/pull/27


Update clang, nix and golang for nix

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
We now update nix related dependencies to be able to build with golang 1.20. Beside that we also bump the nix version itself as well as the base image used for it.
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

Codecov Report

Merging #1489 (7f2c3f8) into main (c26a139) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1489   +/-   ##
=======================================
  Coverage   43.98%   43.98%
=======================================
  Files          50       50
  Lines        5716     5716
=======================================
  Hits         2514     2514
  Misses       3081     3081
  Partials      121      121

Ah I'll have to bump the bpf, one second.


Update data-flow-expression-functions.md

@nimoolen : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@kromerm This should also include size() and rand(). Are there any other functions we are missing?

#sign-off

@djpmsft: I'm sorry - only the author of this article, @kromerm, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


feat(container-api): add props reference

Description (required)
Adding the reference to the Container API props.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
reference/container-reference.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Login to 3rd party service through OAuth2

Hi!
I'm thinking about integration one service to the hain, but it requires user to input login/pass and grant access rights to the application. Is it possible with the hain to display a 3rd party's auth form for login/pass input? If yes what should I specify as redirect_uri for OAuth process? :)

Can I know the service that you integrate? I may find the way to solve it.

@appetizermonster https://getpocket.com

I read the docs on https://getpocket.com/developer/docs/.
Currently, There is no official way to support it.
It takes very long time to fully support it.
but I think you can achieve this by using web server framework (like expressjs) to simulate callback server.

Site, I can, but I also have to show login form to user. Even if I open a browser for it I will not be able to get access token back to hain 😞  Some workaround can be achieved by saving access token on my server and then request it from hain, but I'm not sure if it worth.
Anyway, thank you

I think i should mention that you can operate local webserver in your plugin because hain plugin is being executed in normal nodejs process

You right, but still no way to open web page in child process and get data from it. Do you plan or even think about such ability?

I have some ideas, will try to implement and will share results here

@likerRr you could open a webpage with opn
const opn = require('opn');
opn('http://localhost:3000/');

@ewnd9 yeah, I've already done so, the only thing is left is to send data from that page to Hain, but it should be easy because we have access to node server. So, this way OAuth2 authentication can be organized in Hain. But should think about usability.

Hi, @appetizermonster . I was busy a lot and haven't reported results of oauth implementation. Actually I did it! :) And it works fine. Unfortunately I haven't opened the code for now, because during the plugin development I started making a little framework for Hain to build plugins.
I would appreciate if you take a look at the Kain. Now it's in very pre version, but already has extended wiki to understand what it provides. May be you will like it and will mention about Kain in Hain's wiki.
Anyway, after I finish implementing Kain to my plugin with oauth support I will post it here to have an example for other people. Hope it will be done in 2 weeks, because tomorrow I go on vacation.

@likerRr I'm very impressed for your Kain, Okay I'll mention it this wiki or docs!

@appetizermonster thanks! I'll continue update docs and will provide some examples, because now it's not clear how it works.


Add priority feature

Now, todos have a priority flag.  When listed, these todos will be bolded and italic.
You can list todos by priority by running todolist l p.
This does have backwards compatibility with existing todo lists.
@NonerKao a review good sir, when you get a chance.

Looks good to me!  I think it is OK to merge this PR.
But just in case, are you going to expand this functionality any further?  E.g, giving a todo numerical value as its priority rather than a prioritized/un-priorotized classification.  If so, then I think it would be better to make the newly-added json attribute "isPriority" a number than a truth value, so that the enhancement in the future would be easier.  Maybe such future extension is not under consideration?
BTW, I don't know if this comment is constructive or makes this PR complicated.  Just my two cents, trying to get familiar with open-source engineering :)

Oh, I see what you're saying, for different levels of priority.  I'm not sure if I want to introduce that complexity.  I like wunderlist's concept of adding a star/bookmark to things to signify priority.   That's what I was going for here.
Thanks for the review!


Pull to refresh

📲 What
Allows users to refresh Discovery Page by dragging the top of the list downward. (UIRefreshControl).
🤔 Why
🌟 Product Excellence
(Details here: https://trello.com/c/2sWEdiyF/1265-pull-down-on-the-feed-to-refresh-the-feed)
🛠 How

Creating an instance of UIRefreshControl and implementing a function to handle its action.
The value of clearOnNewRequest had to be set to false to avoid the list to be blank while pulling to refresh projects.
Some logic was added to handle the states of UIRefreshControl and ActivityIndicator, since the second shouldn't appear while loading projects through pull to refresh action.

👀 See

✅ Acceptance criteria

[ ] I go to Discovery and I see the Activity Indicator while loading projects.
[ ] I drag the list downward and I should see the UIRefreshControl spinning (and no Activity Indicator)
[ ] The projects rarely change, so to see if the feature is working, go to the Ending soon tab and look for a project the x min to go. Wait one minute and pull to refresh. The ending time should update.

So my first impression (looking at this improvement) is whether we should simply use just one spinner (the pull to refresh control's spinner to be more precise).
We currently show 2 loading indicators:

one I believe is either a view or cell that's displayed when the content is being loaded
the other is the pull to refresh

Hopefully this explains it better than my words..

Step 1
Step 2
Step 3

How hard would it be to remove the original spinner and keep just the UIRefreshControl one?


fix: changes required for Kafka SDK update

I have verified all commands manually:

Topics
Consumer-Groups
ACLs

Just minor changes were required.

@rkpattnaik780 I will merge so we can do automatic tests and rebase other PRs


Not working in mod view

Plugin version: 0.6
Browser: Chrome
Version 88.0.4324.150

i just was stupid, sorry


LICENSE or permission to reuse code?

Would you be willing to add a LICENSE file to your repo, or to specifically here give me permission to modify and redistribute some of your code in my pico8 library repo https://github.com/sparr/pico8lib ?

Good suggestion. I licensed the code under the MIT license, but let me know if you were looking for something else. Out of curiosity, which code were you looking at pulling out?
Side note: I haven't really been updating it, but I previously put some of my reusable code in this repository:
https://github.com/jaredkrinke/pico-8-util/tree/master

Thanks for adding a LICENSE.
My library primarily uses the Unlicense (https://github.com/sparr/pico8lib/blob/master/LICENSE), so if you give me permission to reuse under that license that would be ideal. MIT license is also great, there's plenty of pico8 code out there using MIT, GPL, and CC. I can simply mark your code as differently licensed, as I already have with the vector library there.
I didn't look into your code too much before asking, because I want to remain able to honestly reimplement the functionality in question if you said no, but the first and biggest thing that jumped ot at me is your uint32 class.

Sure, you have my permission to use the code from those two repositories (I'm the sole author) under the Unlicense license (instead of MIT) if you prefer.

Thanks!


Potential problem of the CSI score

Dear authors of the SEVIR benchmark, we are recently running the SEVIR benchmark but noticed that there's a potential problem of the current implementation of the CSI score: https://github.com/MIT-AI-Accelerator/sevir_challenges/blob/6e18184344ecf7f3bb543d40d064e92a9f30e4d4/src/metrics/metrics.py#L138
When the threshold is large, it is possible that the hits, misses and fas of the model are all zero. The current formulation will produce csi=1.0 in such case (while it should give csi=0.0). To avoid this problem, a better formula might be
return hits / (hits+misses+fas+1e-6)

CC @gaozhihan also

The same problem also appears in the implementation of POD, SURR and BIAS. We found that the CSI score is the most vulnerable one, which can be quite misleading, especially when batch_size is small.

Thanks for the feedback -- I remember struggling with this choice.  In general these metrics are unreliable when using small batches, so I recommended that they only be used for evaluating over your entire testing set.   If running in batches is necessary, one can also tally hits, misses and false alarm in batches, and combine them in the end.
That being said, I agree there is probably a better way to handle cases  where 0/0 is possible.   The method of Laplace Smoothing (https://en.wikipedia.org/wiki/Additive_smoothing) helps solves this problem by assuming a Dirichelt prior over the probabilities of the three categories (hits, miss, false alarm).   Using this, another possibility would be
return (hits+alpha) / (hits+misses+fas+3*alpha)

which would be more of a compromise between your suggestion, and the way it is now.  Here alpha is a parameter (which we can keep at 1e-6 or increase as necessary).

Thanks for your reply. It's quite helpful. BTW I want to ask another question. As you mentioned, calculating the mean of skill scores is different from calculating skill scores using accumulated hits, misses and fas. In your implementation, I find that you report the scores of each forecasting lead:
https://github.com/MIT-AI-Accelerator/neurips-2020-sevir/blob/master/test_nowcast.py#L142-L168
My question is, how did you get the final scores of each prediction? Did you directly calculate the mean over 12 leads, or accumulate all hits, misses and fas first and then get the scores?


Entity changed into Jpa from Mongo

I have restructured the Entity class from Jpa. As mongo will be tough to handle. But we will go in plug&play concept so it will not be an issue.

Thank you @arpanghosh2416 for your contribution


Support pydantic 2

As of this writing, we support only pydantic v1. It would be good to support pydantic v2 as well.

link
https://github.com/yu-iskw/dbt-artifacts-parser/pull/66#issuecomment-1822097260

@OnkarVO7 Let me ask you a question about pydantic. Do you have any plan to use pydantic 2 in OpenMetadata? Otherwise, do any other connectors still need pydantic 1 due to the dependency?
As you may know, pydantic 2 was released. I am wondering how we can support both major versions of pydantics. Or I just want to know we can migrate to pydantic 2 without deep consideration. I haven't investigated if pydantic 2 is fully compatible to pydantic 1 or not. I'm sure OpenMetadata is the largest project which uses the python package.
I left a little bit in my mind at the following link:
https://github.com/yu-iskw/dbt-artifacts-parser/pull/66#issuecomment-1822097260

@yu-iskw we do plan on migrating to pydantic v2 in the near future, probably in the next couple of releases.
Do let us know your plans on supporting this we'll also plan accordingly

@OnkarVO7 Thank you for sharing. I don't have a clear plan. But, I would love to definitely support pydantic 2 before the migration on the OpenMetadata side. I will make a list of potential approaches to satisfy requirements I am thinking.

Besides, I've opened a discussion to get advice from the pydantic community.
https://github.com/pydantic/pydantic/discussions/8203

Hellow @yu-iskw - lack of Pydantic v2 support blocks some of our users from upgrading to latest line of Airflow 2.8. Is there anything we can do to help with the migration? Pydantic v2 is now used by pretty much every other dependency we use (and we have 670+ of them altogether). so it would be cool if Pydantic v2 is also supported.
Do you have a clearer plan by now currently ?

Migrate it to pydantic 2
https://github.com/yu-iskw/dbt-artifacts-parser/pull/78


Update spring-cloud-azure-dependencies versions

Description
Update spring-cloud-azure-dependencies versions
All SDK Contribution checklist:

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

General Guidelines and Best Practices

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

Testing Guidelines

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

/check-enforcer override


Incomplete Downloads

I'm having an issue where some files get skipped over from an Artist page, or some files don't fully download.

This is on my radar. I think the servers have changed how they respond to errors recently. In the past, the status code (200, 502, 404, etc.) property reflected the response from the server. But I think it has started sending 200 (OK) for all requests, and returning the error in HTML instead... Not sure why.
To confirm this, check the contents of your incomplete downloads. They probably end with some HTML that would display the server error, like 502 or 404. There may also be downloads that are 148-150 bytes in size that contain only the HTML.
In the short term, try again later and see if that fixes things. In the long term, the response from the server needs to be handled more robustly.


[Setup] Cleanup target dir before installation

Summary of the Pull Request
What is this about:

cleanup installation folder via custom action
note that it'll remove everything in the installation folder w/o warning, so user data might be lost

What is include in the PR:
How does someone test / validate:
Quality Checklist

[x] Linked issue: #14701
[ ] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[ ] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

@crutkas this change might cause some user data to be lost if a user specifies non-empty installation folder. Perhaps we should in that case that it'll be cleaned?

@yuyoyuppe
Which user daa? Normally no user data are saved in the install folder. Or do I miss something?

@htcfreek if a user chooses e.g. C:\Program Files as an installation folder by mistake.

I know we chatted about this but I don’t know if this is the correct way of doing this.
Like, what are there two plugins still. I feel like if there is a mismatch, shouldn’t the newer version win?

It feels like we are doing a sledge hammer solution when a scalpel will work.

I feel like we do need some sort of this in the long run, since this is not the only class of issues we've had with files not being deleted in the previous installation.
I imagine https://github.com/microsoft/PowerToys/issues/2125 will cause more of this, and perhaps even more serious.
There's no issue in having the scalpel solution too, though.
I'll give it a try.

@DHowett id like your opinion here. Any ideas why an uninstall would leave files behind?

There's a possibility of having files open, but this doesn't seem to make much sense according to the install folder tree from the bug report.
In installationFolderStructure.txt, we can see the old version folder structure is all there, even those dlls for other languages which shouldn't be in use at the time of uninstall.
       Actually update should uninstall and install.
Could this help? https://wixtoolset.org/documentation/manual/v3/xsd/util/removefolderex.html

"Scalpel" solution here: https://github.com/microsoft/PowerToys/pull/14776

Is this going to be shipped with the hotfix 0.51.1?

superseded by #14776


would be nice if we would have red line to see elements endings in HTML

VSCode Version: newest
OS Version: 8.1

Steps to Reproduce:

would be nice if on div click you would have line in some kind of color

Found, plugin.

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!