Feature request: Testing for NPM package publishing

In order to ensure NPM packages build successfully for our users in different environments let's get in the habit of testing package publishing with each PR merge.
A few options:

Use a local, private registry built with Verdaccio (or similar) to test package publishing locally.
Setup a hosted registry using Verdaccio (or similar) which is automatically published to with every PR merge.  This approach would provide a publicly accessible registry with all canary builds that indexers can test.
Use a similar approach to previous but deploy to the official NPM registry using alpha or canary tags.

I'm leaning towards the third option for its implementation simplicity and natural transparency.  As long as we use a clear tag such as canary or alpha to separate it from latest users aren't likely to accidentally install on production machines and this will be a good step towards a more automated/regular release pattern.


Add post about To-do flask application

In addition to the requested changes, could you bump the date up on this post (both filename and metadata)?


(suggestion) Conquest Reforged Compat

A compatibility update for CR would be amazing! or is there any kind of documentation anywhere to guide me on how I can create a compat myself?
Conquest reforged is an incredible aesthetic and immersive overhaul to minecraft.
But the immersion is quickly broken when you break a tree and get fence or pillar blocks.
Its also painful having to destroy each individual block of a sprawling tree only to leave behind floating logs, leaves and branches (that are actually fence blocks again).

Dynamic trees would literally make this the perfect experience. The trees would look better, the small trees would actually be small trees on not fences with leaves, the big trees would be way better looking with actual connecting branches and logs and having the ability to prune them back using dynamic trees branch cutting would be incredible.

Sadly, there is no documentation for making addons, but you can see examples here and [here](https://github.com/the-realest-stu/DynamicTrees-BOP] as well as joining the discord for extra assistance.


First technique creates PFX without private key in the container

The first technique described in this this document does not work properly for Windows Containers (including in Service Fabric 6.2) for clusters running in Azure. The PFX file made available in the container at runtime will not have the private key in the PFX file. Issue is being discussed here: https://github.com/Azure/service-fabric-issues/issues/448

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

ID: 488c060b-5a0e-75d3-498a-4c1dd3ee058e
Version Independent ID: 06f2544d-f98c-2ecf-686c-a7941d263af3
Content: Import certificates into a container running on Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-securing-containers.md
Service: service-fabric
Product: unspecified
GitHub Login: @mani-ramaswamy
Microsoft Alias: subramar

@AaronRM Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

The following statement above should be removed:
"For Windows clusters, when starting the application, the runtime exports each referenced certificate and its corresponding private key into a PFX file, secured with a randomly-generated password."
It is simply not true.  The corresponding private key is not exported into the PFX (you can tell by the difference in file size).  Please update the documentation to reflect reality.

The document also states: "The private key corresponding to the certificate must be available, accessible and - on Windows - exportable." I agree we need to do a better job of surfacing that error - when that is the case - to the user, but the certificate export works correctly as described by the article.

Yea I guess that's a valid point.  What it doesn't say is that certificates you add to your cluster using the Add-AzureRmServiceFabricClusterCertificate Cmdlet will not be exportable.  So, short of actually RDP'ing into each VM (We'll have about 30 in production) and installing the cert by hand, how is one supposed to actually get an exportable certificate?  Are you supposed to build your own custom VM image?  Is there any automation that can perform an action to every VM in a cluster?  It appears you've built a cool feature that actually isn't yet possible to use.

Your feedback is spot-on, and unfortunately I have nothing to offer but an apology. Indeed, the feature is not usable in the real (Windows, Azure) world. Your best option, as discussed privately, is to leverage the VMSS' managed identity to retrieve the certificates from a vault in the live activation path, and write them to a container-mounted folder (or a variation thereof, such as injecting a token into the container, or even other, more creative/less secure options I won't detail here.)
For the long term, we will deprecate this feature and replace it with support for container-level managed identities, as well as support for container secrets declared as KV references.
I will look into updating the documentation to state clearly that Add-AzureRmSFClusterCert installs certs as non-exportable (it uses internally Add-AzureRMVMSSSecret, which is the same ComputeRP-based provisioning of certs as in template deployments, and so has the same restrictions.)

Is this actually closed?

Yes, it is closed. The original issue was opened to track a bug in the certificate export flow, which 'succeeded' even when the private key was not exportable. That bug has been fixed, and the cert export will fail in that case.
Mike's point was that the usual certificate provisioning mechanisms available in Azure will install private keys as non-exportable; this is by design, and won't change. As such, this feature is largely unusable, unless one retrieves and serializes certs with custom code.
As noted previously, our intention is to deprecate this mechanism, precisely because of its limited usefulness. In the meantime we've added support for managed identities, integration with KeyVault and exposed the CSS, an in-cluster secure store.


Prepare for Gradle plugin release 4.0.0

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#246  👈
#245
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rbro112 and the rest of your teammates on  Graphite


[v1.5][T11-B1] Cho Chih Tun - Added findtaskby command test

Did you make changes on the xml files? If you feel that you didn't, pls remove those commits from the PR since the files are likely to be encrypted, which will render us and the tutors from viewing the contents in the future.


Updated Kuma Logo

fixes #219
Signed-off-by: ashiscs<EMAIL_ADDRESS>

@gszr @tharun208 @nickolaev

Hi @leecalcote and @ashiscs, thanks for the heads up, @devadvocado can help with the logo.

Updated !


Is there an API to see if Becsy is currently running in accessRecentlyDeletedData mode?

If not, I think this could be useful.
Reason: Sometimes I have a function (foo()) that does useful things to entities, in situations where  accessRecentlyDeletedData(false) and also when accessRecentlyDeletedData(true). While accessing recently deleted data mode is on, I want to avoid calling entity.remove() on a recently deleted entity, because it's deleted already and an error is thrown in dev mode if I were to try. But I can't see a Becsy-API way of asking if accessRecentlyDeletedData is true or not, to make that check possible.
Alternatives:

It's certainly possible for me to wrap accessRecentlyDeletedData() in my own function that also sets a variable of my own to track this, but this leaves open the ability for people to still call accessRecentlyDeletedData() directly and making my new variable incorrect.
It's possible to dive past Becsy's API and get the value of this.__dispatcher.registry.includeRecentlyDeleted from any system, but obviously not ideal because that's internal, undocumented and might change in future versions of becsy.
It's also possible for me to pass in an indication of whether accessRecentlyDeletedData mode is true into foo() itself at the location where it is called e.g. foo({includeRecentlyDeleted: true}), to then conditionally call entity.remove() inside foo, but this feels like double-handling a piece of state that I know exists already inside of becsy.

Open to any thoughts!

Just experimenting, it seems likely that the more accurate check is to look if the specific entity is entity.alive before removing.

Makes sense, thanks!


Fix #344, Remove mission/platform include dirs

Describe the contribution
Fixes #344
Removes classic build directories.
Testing performed
Steps taken to test the contribution:

Tested w/ CI bundle branch on fork, see: https://travis-ci.com/github/skliper/cFS/builds/157335615

Expected behavior changes
None, reduces user confusion due to duplicate defines
System(s) tested on

Hardware: CI (AMD)
OS: Ubuntu 18.04
Versions: Master w/ this commit

Additional context
Only dependence found in framework was in cFS-GroundStation.  See XXX
Third party code
None
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

CCB 20200415 - APPROVED


NO_KEY_OPTIONS is remove from mysql8.0

mysqldump: Couldn't execute 'SET SQL_QUOTE_SHOW_CREATE=1 ,SQL_MODE=concat(@@sql_mode, _utf8mb4 ',NO_KEY_OPTIONS,NO_TABLE_OPTIONS,NO_FIELD_OPTIONS') ': Variable 'sql_mode' can't be set to the value of 'NO_KEY_OPTIONS' (1231)

Thanks @wenweih
after #312 is merged, we will start to support 8.0. hope you can send us a PR to fix this problem.

Sorry to comment on a closed issue.. I'm using last commit in master (so it should already contain #312) but I still get that error:
mysqldump: Couldn't execute 'SET SQL_QUOTE_SHOW_CREATE=1/*!40102 ,SQL_MODE=concat(@@sql_mode, _utf8 ',NO_KEY_OPTIONS,NO_TABLE_OPTIONS,NO_FIELD_OPTIONS') */': Variable 'sql_mode' can't be set to the value of 'NO_KEY_OPTIONS' (1231)
Mysql version is 8.0.15, and my.cnf is like this:
[client]
default-character-set=utf8

[mysql]
default-character-set=utf8

[mysqld]
collation-server = utf8_unicode_ci
character-set-server = utf8
#skip-log-bin
log_bin=/var/log/mysql/mysql-bin.log

sql_mode=STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
default-authentication-plugin=mysql_native_password
key_buffer_size=16M
innodb_buffer_pool_size=300M
innodb_log_file_size=48M
local_infile=ON

Any idea?
Thank you

@pidario
maybe you use an old mysqldump to connect mysql 8.0?
go-mysql will not set SQL_QUOTE_SHOW_CREATE.

@siddontang
I was actually using an old version, but after updating the same error showed up. It doesn't matter anymore since I decided to take another approach.
Thanks anyway.


added UPM support

@lvgrecords why so many meta files were changed? Is this intentional?

yes, changes intentional
anyway I did not fixed issue with building app for iOS
❌  ld: framework not found AdServices
❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

so looks changes are not final

is not working properly at that moment


Fixing common test user validation.

The name field in the user attribute was being set to body incorrectly.
The result was being checked for an array, but it was an object.

@alex94puchades do you have any questions about this and PR #11 looking to get bug fix merged into your project

Thanks! Sorry for the delay


Issue with opening a new database

When opening a new named database we seem to be running into an issue, presumably in the bindings as we don't have that kind of issue in our OCaml code base using the same flow of the script. The error is MDB_BAD_VALSIZE, which seems to have something to do with the database name ('A' in this case) being too large or so. The liblmdb-dev version is 0.9.10-1, ubuntu 14.04.1.
#!/usr/bin/env stack
-- stack runghc --resolver nightly-2016-11-25 --install-ghc

{-# LANGUAGE OverloadedStrings #-}

import qualified Database.LMDB.Raw as Lmdb
import qualified Control.Concurrent as Concurrent

main :: IO ()
main = do
  let env_flags = []
  env <- Lmdb.mdb_env_create
  Lmdb.mdb_env_set_maxdbs env 2
  Lmdb.mdb_env_open env "/home/user/lmdb_hs/" env_flags
  Concurrent.runInBoundThread $ do
    txn <- Lmdb.mdb_txn_begin env Nothing False
    dbi <- Lmdb.mdb_dbi_open' txn (Just "A") [Lmdb.MDB_CREATE]
    Lmdb.mdb_dbi_close' env dbi
    Lmdb.mdb_txn_commit txn
  Lmdb.mdb_env_close env

Try this instead:
{-# LANGUAGE OverloadedStrings #-}

import qualified Database.LMDB.Raw as Lmdb
import qualified Control.Concurrent as Concurrent

main :: IO ()
main =
  Concurrent.runInBoundThread $ do
    let env_flags = []
    env <- Lmdb.mdb_env_create
    Lmdb.mdb_env_set_mapsize env 1000000
    Lmdb.mdb_env_set_maxreaders env 5
    Lmdb.mdb_env_set_maxdbs env 4
    Lmdb.mdb_env_open env "the_env" env_flags
    txn <- Lmdb.mdb_txn_begin env Nothing False
    dbi <- Lmdb.mdb_dbi_open' txn (Just "A") [Lmdb.MDB_CREATE]
    Lmdb.mdb_txn_commit txn
    Lmdb.mdb_dbi_close' env dbi
    Lmdb.mdb_env_close env

LMBD has a somewhat confusing procedure for initialization. You need to open up a transaction, open all the databases, and then commit the transaction. This is weird because you end up using the database handle outside of the transaction in which it was opened. This is documented in the haddocks for mdb_env_open. Also, as the docs explain, you have to call mdb_env_set_mapsize.
Since, this is all kind of annoying, I wrote lmdb-high-level, which prevents these kinds of issues from happening. But, it's not well documented and may not be suitable for your use case.

Indeed, didn't notice the fact that I closed the env and then did the the commit, I knew I must have been missing something silly as this (nearly) same snippet runs in our OCaML code base. I know about the mapsize and such, removed it from the little example to make it as small as possible, but thanks for the info. I might check out the high level package then, we use something similar from our OCaML bindings, usually practical. Bit of a weird exception, and a bit unexpected that it only shows when also having to create a database ( when filling in 'Nothing' instead of 'Just "A"' the first snippet runs. Thanks!


Missing a way to update package cache when upstream versions change

One common use case for caching appears to be caching build dependencies, like:
- name: Dependency cache
  uses: actions/cache@v1
  with:
    key: {os}-{language tooling version}-${{ hashFiles('dependencies') }}
- run: pkgtool update
- run: pkgtool build-dependencies

Unless dependency versions are precisely specified using some lock file, this will mean that the key doesn't change with time / newly released upstream dependency versions. On the other hand the call to pkgtool update will be aware of those upstream updates, and hence they will be rebuilt. But since the cache key doesn't change, actions/cache won't update the cache.
I see a couple of approaches to address this, but none seem to be available right now:

allow specifying whether to update the cache even on a cache hit, using something like with: update: true
provide the current date or timestamp, which might then be incorporated in the cache key
have actions/cache take pre- and post-checksums of the cached path, and update the cache if the checksum changed

+1 . I think vcpkg needs something like to be able to handle the case where one of the packages is updated (or a new dependency is added), and you want to load the cache, rebuild only that single package (instead of rebuilding all of the dependencies) and save the cache. ccache/clcache probably need the same incremental caching support as well.

@robx If you want to use the date in your key, you can do something like:

# http://man7.org/linux/man-pages/man1/date.1.html
- name: Get Date
  id: get-date
  run: |
    echo "::set-output name=date::$(/bin/date -u "+%Y%m%d")"
  shell: bash # For Windows, Linux and macOS default to bash already

- uses: actions/cache@v1
  with:
    path: ~/.cache/directory
    key: ${{ runner.OS }}-build-${{ steps.get-date.outputs.date }}

@joshmgross Thanks, that's a neat trick!
Another hack I've thought of is to reorder things and generate a hash file:
- run: pkgtool update
- run: pkgtool configure  # or pkgtool lock, etc; writes deps.lock
- uses: action/cache@v1
  key: hashFiles('deps.lock')
- run: pkgtool build-dependencies

(or if nothing like pkgtool configure exists, run something like hash /path/to/pkgdb > pkgdb.hash and refer to that in the key).
Considering the issue appears to be solvable, feel free to close it, though I still have a feeling this could be made easier...

I'll let @chrispat weigh in on adding an always update/refresh cache option
Downsides are that it may be confusing for users, and you lose some performance of caching if you're always saving/re-creating the cache at the end of each run.

I feel cache entries should be fundamentally immutable by key and breaking that expectation could lead to inconsistent results for users.


multiPrime result

Hi @joybio thank you for your package.
In the results folder of multiPrime for the CDS test data, there are two final max forward and reverse primer from just one cluster.
Is it expected that the final results will have only 1 cluster, should I be concerned when the input sequences are considerably different?

I saw this from the paper " The primary output will encompasses two ultimate primer sets and the cluster specific primers".
Does it mean only one cluster is considered for the ultimate primer set? what about the primers from the other clusters. I'm asking because I'm getting only one cluster.
Thanks

@tobbyxy For large input sequence sets, it's common to encounter sequences that cannot be clustered, which may result in a very large final primer set. To manage this, we filter out clusters with short sequences, creating what we refer to as the core primer set. The situation where only one primer set is obtained occurs when the final primer set is generated, but no core primer set is produced. This is because the default filter threshold requires clusters to have at least 10 sequences to qualify as a core primer set. Hence, if no cluster meets this threshold, only the final primer set will be available.

Thank you for your response @joybio
I have some follow up questions.
"Hypothetically, If I have 3000bp sequence as input, with amplicon size (product length) set to 1000bp, will the primer set designed amplify the 3000-sequence length or the amplicon only (1000bp)? we are interested in using this tool to design primers for multiple regions within the same gene to cover the entire length of the gene. So we want to know if

we can have multiple amplicons (targeting different regions) for individual clusters?
MultiPrime currently reports the number of sequences covered in the primer, can we access the coverage breadth.?

I appreciate your response.

@tobbyxy

Regarding your hypothetical scenario of using a 3000bp sequence as input with an amplicon size (product length) set to 1000bp:

The primer set will amplify a product of 1000bp, which is the specified amplicon size. It will not cover the entire 3000bp sequence in one amplicon.  However, in MultiPrime, the PCR product size can be set to a range, with the default range being 150-1200bp.
2. # About targeting multiple regions for individual clusters:
Yes, you can generate multiple amplicons targeting different regions within each cluster. MultiPrime outputs a candidate primer list for each cluster, which you can find in the <Clusters_cprimer> or <Primers_set> directories. Below is a breakdown of the relevant directories and files:
Clusters_cprimer:
Contains candidate primers (spanning from the start to stop positions) for each cluster, available in both .fa and .txt formats.
Primers_set:
Contains all candidate primers for each cluster, along with sorted primers and coverage statistics.
Additionally, directories such as Clusters_target provide detailed information about each cluster, and the PCR_product folder includes the perfect PCR products for each primer.
Here is an example:

All the candidate primers are listed like this.
3. # Regarding access to coverage breadth:
Yes, the coverage breadth can be set by the user in the YAML configuration file (e.g., in the PRODUCT_size parameter). This allows you to define the range of PCR product sizes, ensuring your primers meet the desired coverage across the targeted regions.


multimarkdown has incomplete closure

Issue description
mmd2pdf complains that latexmk is missing. It looks like a bad closure
Steps to reproduce
nix-env -i multimarkdown
mmd2pdf anything.md

cries out
$HOME/.nix-profile/bin/mmd2pdf: line 54: latexmk: command not found
It doesn't appear that latexmk is installed properly.
Be sure you have a working LaTeX installation.

Technical details

System: Ubuntu 16.04.1 LTS
Nix version: 1.11.2
Nixpkgs version: "16.09pre88706.b8e215f"

Has been fixed in the meantime.


FEATURE - Using minUI5Version in ADP

As an ADP developer,
I want to be able to define and test with a minUI5Version,
so that I preview with the minUI5Version
Description
The UI5 proxy middleware checks the manifest.json for a minUI5Version and if it is there, uses it as preview version. This does not work for adaptation projects because there is no manifest in the project. To also support this for ADP, we also need to check the appdescr file in ADP and check if it has a minUI5Version change, and if existing, use the version.
Technical Design
What modules need to be created or enhanced?
How would the functionality be exposed and how can it be consumed?
Acceptance Criteria
GivenWhenThen format (https://martinfowler.com/bliki/GivenWhenThen.html)
Given I have a ...
when I execute ...
then ... will happen.
Notes
Tasks

[ ]
[ ] Unit Tests added
[ ] Test Cases defined

@testojs


Remove max width on preview?

Is this line necessary?
https://github.com/kognise/obsidian-atom/blob/01128e66dcb33186bc7aca67d02f4d35a234ecf0/obsidian.css#L221
It overrides the obsidian setting for readable line length, and it just seems to be far too wide for the body font size. Not sure why it's here or what problem it's solving, but could it be more targeted to that problem or removed altogether?

I also have the same problem, when I use the reading view to zoom in on the font it doesn't zoom in at the same time

+1. It also conflicts with Dashboard++, which changes the max-width for the dashboard page.
For now I solved by cloning the theme and removing the !important, but would be great to fix this upstream (assuming this theme is still maintained).


Wik documentation tutorials v0.3

PR Checklist
For reviewers
This should be reviewed after #226, #228 and #230
If you are contributing to Javis.jl, please make sure you are able to check off each item on this list:

[ ] Did I update CHANGELOG.md with whatever changes/features I added with this PR?
[ ] Did I make sure to only change the part of the file where I introduced a new change/feature?
[ ] Did I cover all corner cases to be close to 100% test coverage (if applicable)?
[ ] Did I properly add Javis dependencies to the Project.toml + set an upper bound of the dependency (if applicable)?
[ ] Did I properly add test dependencies to the test directory (if applicable)?
[ ] Did I check relevant tutorials that may be affected by changes in this PR?
[ ] Did I clearly articulate why this PR was made the way it was and how it was made?

Link to relevant issue(s)
Closes #232
How did you address these issues with this PR? What methods did you use?
Changed mostly code and fixed the references to things that don't exist anymore. I might have missed some.

Closed in favor of #244 which should make reviewing and merging easier.


Convert numpy types to their native python types

I don't know exactly why but for some reason the json encoder in python3 can't encode some of the numpy datetypes. Now I simply converted the numpy data types (http://docs.scipy.org/doc/numpy/user/basics.types.html) to the respective python types. (#416)

@mistercrunch done!

Thanks!


Expo Starter does not working

Hey there! Ignite CLI seems to be having a problem, eh?
Welllllll, it just might be. First, search the issues to make sure it's not already
here, and if not head over to http://community.infinite.red to
get some help. If you've identified that it's really an Ignite CLI issue, then:

Explain what's going on and preferably how to replicate the issue (bonus points for a repro app)
Run ignite doctor and paste the result below, including the lines with 3 backticks
Delete these instructions! We don't want to look at them. ;)

What's going on?
I'm receiving a error on use npm start (expo start)
Steps to reproduce
Just use ignite-cli with the option ignite-bowser and select Wpo
ignite doctor results:
  platform           win32
  arch               x64
  cpu                12 cores           Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  directory          ExpoIgniteBowser   C:\ZFolder\ignite-cli-project\ExpoIgniteBowser

JavaScript
  node               12.9.1       C:\Program Files\nodejs\node.EXE
  npm                6.10.2       C:\Program Files\nodejs\npm.CMD
  yarn               1.22.0       C:\Program Files (x86)\Yarn\bin\yarn.CMD

Ignite
  ignite-cli           3.5.1                                                                                C:\Users\JoaoBibianoPinheiro\AppData\Roaming\npm\ignite.CMD
rs\JoaoBibianoPinheiro\AppData\Roaming\npm\node_modules\ignite-cli\build
  navigation           react-navigation

  generators           {"component":"ignite-bowser","model":"ignite-bowser","navigator":"ignite-bowser","screen":"ignite-bowser"}

  createdWith          3.5.1

  boilerplate          ignite-bowser

  boilerplateVersion   5.0.1

Android
  java               -            C:\Program Files\Java\jdk1.8.0_211\bin\java.EXE
  android home       -            C:\Users\JoaoBibianoPinheiro\AppData\Local\Android\Sdk```

Image Error:

![image](https://user-images.githubusercontent.com/29175815/79623835-3ebc1a80-8116-11ea-9c20-9e7a98126697.png)

I found that react-native-screens/native-stack isn't available on npm.... What can I do?

I had issues generating an expo project as well but found that it was because of an outdated node version. I found this by running npx expo-cli --version and noting that it failed. Updating Node solved the issue for me.


Option to display OCR'ed text

As of 2.0, the OCR text is displayed on top of the image, as an overlay.
Displaying the OCR'ed text in a text area would be useful, at least to check that OCR worked as expected (not many recognition errors) but also to select/copy the OCR'ed text to the clipboard for saving.
For the implementation, it's up to you, I think a textarea could be added under the metadata, on the right hand side of a file, or it could be a separate page containing a textarea and accessed via a new entry in the contextual (right click) menu for a given document.
The alternative is to open the image viewer and do Ctrl+A, but there are problems:

Ctrl+A selects the whole page, including a bunch of other text (whatever is displayed on the page, like the html div and spans)
Once selected with Cltr+A the overlayed OCR'ed text is still hard to read (it's not as readable as a textearea)

Thanks!

Hello @eric-saintetienne,
You already can do this, but I must admit that this option is rather hidden, so maybe good suggestion would be to make it more accessible.
How to view OCRed text of the page:

Open your document
Select this icon in the left top corner:
Select page you would like to see OCR from (this is important without selection option won't work)
Press right mouse button on the page
Select "View OCRed text"

I may make a pull request to add this description to documentation.
@ciur would that be a good idea?

Feature is available in 2.1.0x and it is more intuitive to use.
Here is a quick demos:


Support ddev share

is there any config, that makes  ddev share working?
Could not fine any solution in the Docu or the issues.

Would like this also, the issue seems to be that the share works but the styles don't load due to it loading the localhost URL.

Would like this also, the issue seems to be that the share works but the styles don't load due to it loading the localhost URL.

yes.
actually it works, when updating the primary url. but than local wont work.
I thought of a conditional primary url, while having the same .env.

If anyone comes up with a solution, PR the docs -- I'd love to include it.
Meanwhile, I'll close this issue since I don't think it really has much to do with the Vite plugin itself.


Fix for glyph reading a \n terminated file

Pull request to fix issue #48

The library assets folder shouldn't be included in a commit. It's my fault for not including a .gitignore rule for this. Please run gradle clean or remove the library assets and resubmit your pull request and I'll accept it.


Add references to Content guide alongside Style guide

Add references to newly added Content guide alongside Style guide references. I forgot a few places on a few pages in the original Content guide PR.
Fixes #16100
Preview: https://deploy-preview-16101--kubernetes-io-master-staging.netlify.com/docs/contribute/

/assign @steveperry-53

FYI - I changed the bullet lists to numbered lists in the Content Guide (outside the scope of this PR I know). Contributors will find it easier to refer to points in the numbered list.

content guide page preview:
https://deploy-preview-16101--kubernetes-io-master-staging.netlify.com/docs/contribute/style/content-guide/

@kbhawkey I appreciate your comments. I should not have renumbered the content guide as part of this PR - out of scope. I've reverted my content-guide.md changes and added a comment to Issue #16143 to address your comments on the PR when I push a PR for that issue.

hello @aimeeu. I went through this page again; forgive the nit picky comments. In general, there are a lot of ideas/rules to check when adding content (almost too many rules and derivations). The workflows seems overly complicated. I also considered the current k8s docs.
One thing that may help visually is to create sub-headings for the main categories, instead of the nested flowchart. This will create links to the individual sections and breakup the chart.

Yes that was my thinking exactly! I just haven't brain-dumped to anyone else.

One thing that may help visually is to create sub-headings for the main categories, instead of the nested flowchart. This will create links to the individual sections and breakup the chart.

@jaypipes or @kbhawkey - do either of you have time to review and LGTM?

Apologies for the delay @aimeeu
/lgtm

@steveperry-53 this now has an LGTM - would you approve when you have a minute? Thanks!

/approve


Integration Testing

It'd be useful to have some integration tests that exercise the library's API from the outside -- Hopefully catch things like #306 in the future.

Yep, I agree.

Closing because this issue has not received any new comments after one year.


lodash: signatures of the method _.capitalize changed

https://lodash.com/docs#capitalize
https://lodash.com/docs#_ (description of the chainable wrapper)

thanks mate!


AAE-21218 All gh caches removed in loop

Checklist

Jira Reference (also in PR title):
README updated after adding/changing behaviour of an action
Proposed version increment for release:

[X] Patch (bugfix)
[ ] Minor (new feature)
[ ] Major (breaking changes)

External PR link where changes has been tested:

Description

Did a test on other repo https://github.com/Alfresco/alfresco-deployment-service/actions/runs/8287820625/job/22681045751?pr=2197


Remove compatibility symbols (Proposal 19)

Description
This PR implements Proposal 19 (iteration 1) from the Symbol Proposals document. It removes compatibility codepoints. For some context, see the Unit Symbols paragraphs of section 22.2.1 of the Unicode 16.0.0 Core Specification, as well as the description of Proposal 19 in the aforementioned Symbol Proposals document (copied below for simplicity).

Breaking changes (cc. @laurmaedje)
angle.l.double and angle.r.double change codepoints. degree.c, degree.f, ohm, ohm.inv, angstrom, and kelvin become invalid.

I'm okay with removing the compatibility symbols.

I replaced mho with Omega.inv, as "mho" seems to mostly be an outdated unit. Of course, we can always add mho later if necessary.

It's so cute though!


Demo is down

As per above.

Yep on my backlog to action this week. Thanks for the reminder.

@JorisDebonnet silverstripe.io is up for me? Should point to github pages.

Ah, silvershop.io works again now. I guess there was a temporary issue 8 hours ago ...
demo.ss-shop.org also shows something new for me now; not sure what it said before, but now it says "Too many requests". http://ww1.ss-shop.org/ still looks like the domain name was lost though. Perhaps a demo could be put up on demo.silvershop.io instead?

@JorisDebonnet yep, got the demo.silvershop.io subdomain setup is something I want to get working but got to finish all the other work first :) If anyone wants to help can provide the SSH login deats for the container

Demo is now up, using silvershop-recipe and the code is all open source if anyone wants to improve it!


⚠ Bofrost.lu has degraded performance

In dd3a079, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1352 ms

Resolved: Bofrost.lu performance has improved in c5aaf59 after 9 minutes.


Residue creation upon loading pdb data

When loading pdb files, I would assume to be able to iterate over the residues of a chain or a molecule (given that it is a protein).

Fixed by e7e6cdf9f78f2d7311e55a4903e0db340207b9eb.


Tiles demo: plugins-prepared directory gets removed when running mvn clean install

CC @aalmiray.

wrong repo.


Investigate switching to Alpine images

The Java images are very large. NiFi itself weights in at a heavy ~300 MB, too. See if there are some optimizations that can be made to reduce the size of these images.

That would be a nice improvement. However, Alpine doesn't use the Glibc by default and that could be a source of issues with precompiled software.

I will not really be supporting this repository moving forward.
It is recommended to use the official NiFi images and follow up with the Apache NiFi team with any issues.


Add five.base(10) // 5

I think this is absolutely necessary to further overcomplicate 5.

Pull request: 3f11c77e5cd0b33d7167b9f0bc724aeaa444e908


Missing requirements

Hi,
Please add the requirements.txt file because I think it's missing that part so it can't be used
Thanks

I have added the requirements.txt file. I haven't yet had the chance to test the tool fully, so please report any issues you may encounter.


[Website] Create a view per version on the website

Suggestion
Currently the latest version is shown on the website. However it'd be nice to add previous version also to the website
So we can direct everyone to the correct pages for each specific version
Use case

All tags used within a version are made clear
it's good for historical purposes

Extra info/examples/attachments
No response

Hmmm to make this easy i think we can create folders per version:
Latest (1.1.0): `/docs/index.html
0.1.0: `/docs/0.1.0/index.html
0.2.0: `/docs/0.2.0/index.html
0.3.0: `/docs/0.3.0/index.html
1.0.0: `/docs/1.0.0/index.html

I guess we can keep the assets (css, js, images, fonts) within the root docs directory and reference them correctly from our index.html

Is there currently a proposed or accepted feature that significantly changes the syntax of the format? If not I think it would be easier to annotate each of the header fields and note types with a Since and/or Deprecated and/or Removed. For example:
#TITLE
Since: Version 0.1.0

#ENCODING
Since: Version 0.2.0
Deprecated: Version 0.3.0
Removed: Version 1.0.0

This would avoid duplication and still make clear which features are available in which version of the format.


HUGO language

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I am mindful of the project scope

Proposal

The image is not coming up instead the command is been coming up
Motivation and context
i am stuck within the code thats the reason

You can find your question already answered here:

https://gohugo.io/documentation/
https://discourse.gohugo.io/


Volume Renderer taking >32GB memory on a 0.4GB data file

WRF file /glade/campaign/collections/rda/data/ds559.0/wy2022/202110/wrf2d_d01_2021-10-01_00:00:00.nc is ~0.4GB on disk. Its 3D variables are at a resolution of  1367x1015x4. After importing it to VAPOR and enabling a volume renderer, CISL-VAPOR (Ubuntu 22.04, 32GB memory) hangs because of VAPOR consuming all the memory.
There seems to be serious memory issues in VAPOR. Even if a machine equipped with more memory is able to successfully render this data set, the ratio between data/memory size prohibits volume rendering a moderately big file.

Question: Is Ospray enabled?

Question: Is Ospray enabled?

This behavior was observed using the "Curvilinear" renderer, not the Ospray renderer.

I tested this on my mac and vapor used about 1.3GB of RAM to volume render this file. It was running very slow, however, and this is due to the shape of the cells. Here is a part of a single row of cells:

This dataset also appears to be incorrectly marked as curvilinear and can be rendered in real-time using the Regular volume rendering algorithm.

@StasJ @shaomeng If this is resolved/ is an issue with the specific use case, we can close this issue.

@StasJ @shaomeng If this is resolved/ is an issue with the specific use case, we can close this issue.

You know what, VAPOR (3.9.2 installer) doesn't show any 3D variables on Casper and MacOS, so I cannot verify the reported issue on these 2 platforms. Seems weird to me and seems there's something else going on in VAPOR, but this particular issue is at a "not verifiable" state for me.
@StasJ , you seem to be able to create a volume renderer based on this file on MacOS. Did you use the 3.9.2 installer, or a custom build?

It works when building from source.


Expand-SqlTLogResponsibly grew my TLog all at once to 150GB.

Bug?
Steps to reproduce*
I executed Expand-SqlTLogResponsibly with a target size of 150,000MB and a growth increment of 8192MB.  After a long pause, I checked Activity Monitor and saw the command had issued a resize on the file of 150,000MB at all once.  I had to kill the process.
Action Results
A growth of the log file to 150GB occurred in one command.
Expected Results
My expectation was that it would grow 8GB at a time until it reached 150GB.
Additional comments
The information on the cmdlet doesn't actually describe how it works, so maybe I'm just mistaken in its implementation.

@scinobe Thanks for reporting this problem.
Can you please paste here the full command that you have executed?
I want to run the exactly command to see if I can reproduce the problem.
Regarding your statement on "Additional comments" can you be more precise?

@ClaudioESSilva
Hi, I used this command:
Expand-SqlTLogResponsibly -SqlServer myDBServer -TargetLogSizeMB 150000 -IncrementSizeMB 8000 -Databases myDB
I was prompted to use 8192MB instead of 8000MB, so I said yes.  Activity Monitor showed the log file was being expanded to 150000MB.  Powershell said that it had 1696MB remaining.  The file system showed the log file at full size, while it was expanding.
My additional comments simply mean that the documentation doesn't explain exactly how the function is supposed to work, so I may have made inappropriate assumptions about how the Log file would be expanded.  It's not important to the overall problem.  My expectation was that it would loop at 8,000MB increments until it reached a final size of 150,000MB.

@scinobe Thanks for the command.
I found the issue, and it is already addressed on PR: https://github.com/sqlcollaborative/dbatools/issues/514
I found other minor issues and correct them. You can read all the fixes here https://github.com/sqlcollaborative/dbatools/pull/514/commits/0804f630829739741be1281705d738c9c179f729 .
When it's released we'll let you know.
In the meanwhile, would you able to test the fix? 😄
Regarding the additional comments it is what you said. The expected behavior is that one. Grow in chunks until reach the wanted target size. I have updated the help 😃.

@ClaudioESSilva  Thanks for the information.
I am getting an error when executing the command now.  It states as follows:
Logfile [<dbname_log>] on database  not processed.  Error:  Cannot bind argument to parameter 'Path' because it is null..
I am using Windows 7.  I noticed in the change log there was a modification to add a slash to the path name if it is missing.  Maybe that is the problem?
Here is the command I ran:
Expand-SqlTLogResponsibly -SqlServer  -TargetLogSizeMB 1000 -IncrementSizeMB 250 -Databases
It was working this morning before I updated the function.

@scinobe Have committed a new version. Please use this https://github.com/sqlcollaborative/dbatools/blob/50cdf1389ea8c9142a15f02320b4efdb377ff251/functions/Expand-SqlTLogResponsibly.ps1
Yes, I have to add a validation to add a back slash to the path, otherwise when using Spli-Path and not the root the backslash is removed. That way the validation of free space compared with Get-DbaDiskSpace output will end on the root and not on the lun path.
I missed the ELSE on the validation. This way variable would be empty and therefore give that error.
Thanks!

I've re-tested the code and it works beautifully.  Thank you!


Update version on the home page

The site still mentions 0.31.0, which is no longer available (in particular, the Gradle integration). Would be nice if that matched the README (which does appear to be up-to-date).
(Also, I'd have made a PR if I'd have easily found the site's source code.)

I suppose this is the sources: https://github.com/ktlint/ktlint.github.io

Would be nice to mention this repo in CONTRIBUTING.md

PR: https://github.com/pinterest/ktlint/issues/501


Using select_streams argument traverses file twice

Currently, when one uses the select_streams argument, it will first traverse the file's chunks to find/parse the headers, and sets some flags used subsequently for a check during the load_xdf main loop, which traverses and parses the file again*. It does that using an alternative code path that mirrors the chunk traversal and header parsing of the main loop, but currently skips, among others, some error checking in case of file corruptions etc.
Side note: I do like the idea of breaking load_xdf up into smaller subroutines, and I like the generator approach of _read_chunks, i.e., there may be a possibility to refactor load_xdf in this overall style, especially if the logic were to get more complex over the years. However, as it stands, the current main loop is still pretty simple and easy to follow (esp when one reads it alongside the spec), and could continue to serve as an approachable reference implementation for future language ports for a couple more years. So I'm not ready to pick a side at this point, also considering the effort that a full & clean refactor would come down to.
For now, maybe a way to reconcile the code duplication (which I hope is temporary) and double-traversal of the file could be to add a self.skip (as in, skip processing chunks of this stream) bool in the StreamData constructor, and we could move the matching logic there or into a helper method/function. This way, it would run the first time a header is encountered, and then whenever one sees a chunk of that stream, one can, roughly, do an if streams[StreamId].skip: continue near the place where it currently does that check. We could then earmark the remainder of that alternative code path (parse_chunks, _read_chunks, ...) for future consideration when or if we take on a refactor of load_xdf in this general style (maybe with a git tag).
I'd be willing to implement the suggested change (using StreamData.skip) this week if there's no objection. I think this may also get us a closer to a future simple and fast load-only-headers option for load_xdf (some time soon I'm hoping to have a separate discussion on that).
(*): The double-traversal may not sound like much, it'd be relatively more costly on a network file system.

I agree that duplicating chunk reading is not ideal, but at that time it was the quickest solution, because I could use functions from an alternative XDF reader I'd written. Also, these functions were mainly intended for querying the XDF file (resolve_streams, match_streaminfos), which I think would be nice to keep.
If you want to put in the effort to de-duplicate chunk reading code paths this would be great, provided that there are no regressions in functionality (i.e. keeping the two functions I've mentioned before).

@cbrnr - I'm doing a little cleanup of pyxdf, deduplicating code, eliminating the double-traversal when using select_streams, adding some other shortcuts, etc.
Am I right in assuming that resolve_streams only needs stream headers? Indeed the functions it calls (parse_xdf, parse_chunks, _read_chunks) only operate on stream headers so the answer seems like an obvious "yes", but those functions' doc strings don't state this explicitly so I was just wondering if you were planning on building these out in the future?
In my deduplication effort, I'm reusing your _read_chunks method, but this means adding a lot of other functionality to it, only to disable that functionality with stream_headers_only=True when being called via parse_xdf (via resolve_streams). Is this compatible with your use-case?

I'll answer in #74.


Router firmware without/with configurable LED

Currently, the LED of the router is blinking during normal operation. This might get quite annoying depending on where the stick is operating. For the coordinator, zigbee2mqtt offers a handy option to disable the LED.
Would it be possible to disable the LED on the router as well, e.g. by a long press on SW1 or so?

@ptvoinfo I tried the following command
{
    "devId": "zigbee.0.00124b001936aa9b",
    "ep": "8",
    "cid": "6",
    "cmd": "6",
    "cmdType": "foundation",
    "zclData": {
        "attrId": "0",
        "minRepIntval": "65535",
        "maxRepIntval": "65535",
        "direction": "0"
    }
}

but it didn't work. The LED is still blinking. Am I missing something?

@sonntam Is the endpoint number correct? Also, it should be "report-config" command.

The cmd-id no. 6 corresponds to "configReport" so I think it should be correct. I also tried endpoint no. 0 to no avail.

Are you able to disable the red blinking led for the router?

@furiaceka87 I wasn‘t able to disable the blinking yet. My WAF is really bad right now 😭
I‘m still hoping for some help.
Sent with GitHawk


Add an explanation about config.debug and Posthog().debug()

Problem Statement
It would be really helpful if the com.posthog.posthog.DEBUG parameter, config.debug and  Posthog().debug() had an explanation, ideally directly in the code.

What does config.debug do in this example from the documentation? https://github.com/PostHog/posthog-flutter
Future<void> main() async {
    // init WidgetsFlutterBinding if not yet
    WidgetsFlutterBinding.ensureInitialized();
    final config = PostHogConfig('YOUR_API_KEY_GOES_HERE');
    config.debug = true;  // <=== this here
    config.captureApplicationLifecycleEvents = true;
    // or EU Host: 'https://eu.i.posthog.com'
    config.host = 'https://us.i.posthog.com';
    await Posthog().setup(config);
    runApp(MyApp());
}

Does it do the same as Posthog().debug(true)?
Or does this code do the same as the code from the example above? I set it to false initially but then use .debug(true)?
Future<void> main() async {
    // init WidgetsFlutterBinding if not yet
    WidgetsFlutterBinding.ensureInitialized();
    final config = PostHogConfig('YOUR_API_KEY_GOES_HERE');
    config.debug = false; // <=== this has changed
    config.captureApplicationLifecycleEvents = true;
    // or EU Host: 'https://eu.i.posthog.com'
    config.host = 'https://us.i.posthog.com';
    await Posthog().setup(config);

    Posthog().debug(true); // <=== this has changed

    runApp(MyApp());
}

Why is this always set to true in the examples? Does it make sense to set it to true only if we’re debugging the app? Does it make a difference?
import 'package:flutter/foundation.dart';

Posthog().debug(kDebugMode);

Solution Brainstorm
No response

Hello,
config.debug = true is just a shortcut for Posthog().debug(true), so the SDK already starts in debug mode and logs things in the console.
Calling Posthog().debug(kDebugMode); at runtime will enable and disable logging based on your needs.

Somehow a dupe of https://github.com/PostHog/posthog-flutter/issues/88 that we can address in this other ssue

So, this is just about printing to the console? It doesn’t affect the functionality or the events being sent at all?

Correct.
https://posthog.com/docs/libraries/android#all-configuration-options

// Logs the SDK messages into Logcat. (off/false by default)

Same goes for iOS.


Usage of barrel Imports

Currently project uses normal imports.
May we use barrel imports like a single file for each folders where files in it are exported? It will result in cleaner imports and reduce clutter in files with large number of imports.

https://marvinh.dev/blog/speeding-up-javascript-ecosystem-part-7/

Hi @DonnieBLT thanks for that insightful article that helped me learn new things. But I believe Dart is very differently architectured than JS and dart removes unnecessary imports caused by barrel files.
If you look at the flutter provided material library it also uses barrel imports.

Thank you! So the performance would be the same?

Thank you! So the performance would be the same?

Yes

@DonnieBLT can i take up this issue!

/assign


Enabling cd for automated plugin releases

I am enabling automated releases in this repo to make it easier to ensure merged PRs make it into a new release in a timely fashion.
I am following: https://www.jenkins.io/doc/developer/publishing/releasing-cd/
This is the first step for Incrementals Enablement
When following https://www.jenkins.io/doc/developer/plugin-development/incrementals/, I noticed that some of the files already existed in this repository. Could you please double check the revision number I changed on the pom.xml is correct (along with the other changes)? 🙂
I also changed the incrementals version to be the newest version here.
Many thanks
Testing done

### Submitter checklist
- [x] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [x] Ensure that the pull request title represents the desired changelog entry
- [x] Please describe what you did
- [ ] Link to relevant issues in GitHub or Jira
- [ ] Link to relevant pull requests, esp. upstream and downstream changes
- [ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

All updated and I have done a subsequent PR to the docs pages as the walkthrough is missing a few steps 🙂

@jtnord Would you mind doing a final check and merge if all correct?


docs(cactus-core-api): add README file

Depends on #1556 - feat(core-api): add weaver protobuf codegen
Fixes #833
Signed-off-by: Peter Somogyvari<EMAIL_ADDRESS>

Thanks for this. Sorry, I haven’t been very productive since Friday, as I got a new work laptop and have been trying to migrate my stuff to it, a process that’s been slow. I’ll get to the JS and Java builds for the Weaver protobufs soon.
Rama
From: Peter Somogyvari @.>
Sent: 23 January 2022 07:42
To: hyperledger/cactus @.>
Cc: Venkatraman Ramakrishna @.>; Review requested @.>
Subject: [EXTERNAL] Re: [hyperledger/cactus] docs(cactus-core-api): add README file (PR #1794)
Merged #1794 into main. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because your review was requested.Message ID:    ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Merged #1794https://github.com/hyperledger/cactus/pull/1794 into main.
—
Reply to this email directly, view it on GitHubhttps://github.com/hyperledger/cactus/pull/1794#event-5937674227, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADRS2E4LTHSKGTR2XMA4CTTUXNPWXANCNFSM5MILOF7A.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because your review was requested.Message ID: @.***>

@VRamakrishna Absolutely no problem, thank you very much for the effort and let me know if I can help with anything as usual!


Expand monarch functionality to allow state access within rules

I think monarch is not powerful enough to tokenize constructs such as C++ raw string literals in the general case. This is an attempt to expand monarch functionality so it can.
Monaco tokenization of C++ raw strings is broken when the d-char-sequence  contains double quotes https://github.com/microsoft/monaco-editor/issues/3128

This is because  https://github.com/microsoft/monaco-editor/blob/main/src/basic-languages/cpp/cpp.ts looks for the end of a raw string literal by searching for /(.*)(\))(?:([^ ()\\\t"]*))(\")/ and then checks $3==$S2 to see if the end has in fact been found, but only compares what is between a closing parenthesis and the first double quote.
As far as I can tell, there is no way to solve this currently in monarch, in the general case, without doing something hacky like hard-coding for all d-char-sequences of less than 10 characters, for example. Maybe there is a way that I haven't thought of, in which case this PR isn't needed.

This PR expands monarch functionality by allowing $S2 to be used within rule regexes, so the fix for https://github.com/microsoft/monaco-editor/issues/3128 can be something along the lines of
        root: [
            // C++ 11 Raw String
            [/@encoding?R\"(?:([^ ()\\\t]*))\(/, { token: 'string.raw.begin', next<EMAIL_ADDRESS>}],
            ...
        ],
        raw: [
+           [/.*\)$S2\"/, 'string.raw', '@pop']
-           [
-               /(.*)(\))(?:([^ ()\\\t"]*))(\")/,
-               {
-                   cases: {
-                       '$3==$S2': [
-                           'string.raw',
-                           'string.raw.end',
-                           'string.raw.end',
-                           { token: 'string.raw.end', next: '@pop' }
-                       ],
-                       '@default': ['string.raw', 'string.raw', 'string.raw', 'string.raw']
-                   }
-               }
-           ],
            [/.*/, 'string.raw']
        ],

I have not fully tested this PR yet.

@microsoft-github-policy-service agree

The automated test cases and unit tests pass. I could use some guidance on how to test the changes in conjunction with monaco / a test monarch grammar.

I've learned that the C++ standard does place a length limit on raw string delimiter sequences so hardcoding handling would be possible, though very ugly. I think this addition to monarch would still be good, and would also allow support for similar structures in other languages such as PHP heredocs (which I don't think are limited).


Misbehaving analyzer clears instructions after calls to non-returning functions

See below
ca 4b 00 5a  {  J2_call                             assert_fail
    -- Flow Override: CALL_RETURN (CALL_TERMINATOR)

All instructions after the call are undefined. Also notice that the J2_call is not the end of its own packet. This occasionally breaks decompilation as well

Unchecking "Repair Flow Damage" under the "Non-Returning Functions - Discovered" analyzer seems like a temporary workaround


URL inconsistencies

Hello.
I've spotted a couple of inconsistencies with URL formats used in Backbone. Just wondering what thoughts are on resolving them.
In the Router, we are told to use urls with the pattern url-path, yet in Models, they have the pattern /url-path. Personally, my experience leans towards patterns with a preceding slash.
Is there any way that the differing patterns can be resolved?

I've found that at lt line 1289, routes are converted into Regexps. And in the History part, rootStripper is defined.
Could this rootStripper not be in use in the Router too, so pre or post slashes are optional?
The problem I've seen is that the History part can match routes with these slashes, yet they don't resolve to functions, as functions don't have slashes in them.

Defining rootStripper at line 1226 before the other regexs, and then adding a replace in at line 1290 does the trick.
I can send a PR if you'd like?

Hi @designermonkey! Thanks for pointing this out!
I see what you mean, but I think the problem is with conflating urls and fragments. Model urls are primarily meant for making requests to the server, while fragments are not necessarily an entire url and are meant only for client-side routing. That said, model urls can be used as fragments and this is enabled by stripping the leading slash. Hope that helps. :smiley:

Ok, so in order to make it more consistent across both areas, and use router fragments as urls as well, couldn't this tiny change be added?


Update version numbers for cppms upgrade

Update version numbers for cppms upgrade to version 3.7.4. Signed-off-by The MathWorks, Inc<EMAIL_ADDRESS>

Thanks!
From: Jeff DiClemente @.>
Sent: Wednesday, October 12, 2022 12:57 PM
To: CppMicroServices/CppMicroServices @.>
Cc: Patty Elliott @.>; Author @.>
Subject: Re: [CppMicroServices/CppMicroServices] Update version numbers for cppms upgrade (PR #749)
this was already merged into development in PR #748https://github.com/CppMicroServices/CppMicroServices/pull/748
—
Reply to this email directly, view it on GitHubhttps://github.com/CppMicroServices/CppMicroServices/pull/749#issuecomment-1276474490, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQGGSQJJKTFWSJ3IA4Z3OQDWC3UV3ANCNFSM6AAAAAARDPGFDA.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Duplicate of PR 748


Add OG image for monthly rankings pages

Goal
The monthly rankings page deserve their own OG image too, to be able to preview the rankings when sharing URLs /rankings/monthly/2023/10.
This PR adds the image and specific meta data.

title: Best of JS • Rankings October 2023
description: The most popular projects on Best of JS in October 2023: Bruno, Wasp, shadcn/ui, Excalidraw, Bun, Next.js, Payload, create-t3-app, Supabase, htmx...

How to test

Click to "Monthly" in the top menu to go to rankings page
Alternative: from home top page, inside the "Rankings October 2023" block click on "View monthly rankings" link
Check the page metadata when inspecting the page <head>

Screenshots

I am starting to see similar code used for each OG image added for a page. Refactoring could definitely be possible in the future!
LGTM! 👨💻

Note that the shell of the image (<ImageLayout>) and the table styles are already shared between the different images.
However the content of the tables is slightly different between the pages (the last column does not show the same numbers, depending on the context) but yes I'm open to any refactoring that would remove redundancy, thank you for having checked!


Understanding BAD_LENGTH errors

I've got the following log on my ZiGate component:
[zigate]   - Source EndPoint : b'01'
[zigate]   - Cluster ID      : b'0006'
[zigate]   - Attribute ID    : b'0000'
[zigate]   - Attribute type  : b'10'
[zigate]   - Attribute size  : 1
[zigate]   - Attribute data  : b'00'
[zigate]   # encoded : b'018102120210021eefb52c82021102100216021002100210100210021102106f03'
[zigate]   # decoded : 0181 02 00 0E EF B5 2C 82 01 00 06 00 00 00 10 00 01 00 6F03
[zigate]   (@timestamp : 22:15:57)
[zigate] BAD LENGTH 33026 != 16
[zigate]   # encoded : b'01e0018102120210021eefb82c82021102100216021002100210100210021102116303'
[zigate]   # decoded : 01E0 01 81 02 00 0E EF B8 2C 82 01 00 06 00 00 00 10 00 01 01 6303
[zigate]   (@timestamp : 22:16:02)
[zigate] --------------------------------------
[zigate] RESPONSE 8102 : Attribute Report / Response
[custom_components.zigate.zigate2hass] ZIGATE SIGNAL :
[custom_components.zigate.zigate2hass] - Signal   : zgt_signal_update_2c8201
[custom_components.zigate.zigate2hass] - Property : last seen
[custom_components.zigate.zigate2hass] - Data     : 2018-03-16 22:16:04

Is the bad length error always due to communication transmission issues?

never encountered such error
Can you tell what device is causing it and which ZiGate firmware you're using ?

Xiaomi Door/Window Sensor using ZiGate 3.0d. It's like if batching occurs when communication is not perfect.


[deploy] Make Python API as independent directory in release's dist

This patch add python api package as independent
directory in final dist directory when user run
command mvn -U install package -Prelease.
There have tar.gz and whl in the python dist directory
close: #8343

I find something here, after this patch merge, we need users to have python in the path to build python package wheel and tar.gz when they run the command mvn -U install package -Prelease.
I am not sure it would make our project hard to build or develop or not

Is there any way we could avoid this?

Codecov Report

Merging #8470 (ca2ac9d) into dev (cd8c5e1) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #8470      +/-   ##
============================================
+ Coverage     45.35%   45.38%   +0.02%
- Complexity     4026     4028       +2
============================================
  Files           686      686
  Lines         26709    26712       +3
  Branches       2868     2868
============================================
+ Hits          12114    12123       +9
+ Misses        13450    13447       -3
+ Partials       1145     1142       -3

Impacted Files
Coverage Δ

.../org/apache/dolphinscheduler/common/Constants.java
78.94% <0.00%> (-1.06%)
:arrow_down:

...api/service/impl/ProcessDefinitionServiceImpl.java
31.93% <0.00%> (+0.02%)
:arrow_up:

...e/dolphinscheduler/remote/NettyRemotingClient.java
53.52% <0.00%> (+2.81%)
:arrow_up:

.../apache/dolphinscheduler/api/utils/CheckUtils.java
73.80% <0.00%> (+6.24%)
:arrow_up:

Continue to review full report at Codecov.

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

After this patch merged. Our distribute directory look like below
apache-dolphinscheduler-2.0.4-SNAPSHOT-bin.tar.gz
apache-dolphinscheduler-2.0.4-SNAPSHOT-src.tar.gz
python
 ├── apache-dolphinscheduler-0.1.0.tar.gz
 └── apache_dolphinscheduler-0.1.0-py3-none-any.whl

Thanks @kezhenxu94 is looks good now, and I also test locally PTAL at this PR

Thank @kezhenxu94 for the help


Remove dependency on perfectionist, implement simple formatting from scratch

Resolves #817, simplifies a bunch of stuff too.
Also noticed some inconsistencies in values we were using in the config (some had leading zeroes, others didn't, some had spaces between commas, others didn't, etc.) so cleaned all that up as well, as we were accidentally relying on perfectionist to do that for us.
Also fixed a small bug in the theme function where array values were implicitly being converted to a string by Node instead of us handling that explicitly.

Any plans on turning this into a full-featured alternative to Perfectionist?

Nah :)


refmt as a toplevel directive or an extension point.  Or both!

It would be useful for Reason newcomers coming from OCaml to be able to refmt code from inside of rtop.  This would save some effort when following an OCaml tutorial, for example.
Inline OCaml code used directly as if it had been typed in Reason syntax:
Reason # [%ocaml type 'a t = 'a list];
type t 'a = list 'a

Live refmt, printing but not evaluating the refmt'd code:
Reason # #refmt.ocaml {|type 'a t = 'a list|};
In Reason:
type t 'a = list 'a;

Having both of these in reverse could be useful too for use from vanilla utop.

we have an online playground now, which I think meets this need?


DataGrid is not fully localizable

Bug type
Component
Component name
MudDataGrid
What happened?
In the DataGrid, many captions are hard-coded, for example around the area of the column selector: "Column", "Hide All", "Show All", "Unsort", "Hide" probably others. This prevents the component from being used in a non-English context.
Expected behavior
All strings should be localizable by providing properties to overload them or having actual resources.
Reproduction link
https://try.mudblazor.com/snippet/QacduzPrJEAKwBIh
Reproduction steps

Make sure your browser supports French.
Switch your current culture to French in your app.

Relevant log output
No response
Version (bug)
6.0.7
Version (working)
No response
What browsers are you seeing the problem on?
Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

How to change "Unsort" word on MudDataGrid column?


Empty Value In Http Request Headers If Value is Empty

Using the NSwag generated code, we are adding a header with an empty value to the HTTP request, which occurs because we are setting the value of the optional header parameter to be null. The behavior that we want is when the optional header parameter is null, we should not be adding the header to the HTTP request at all.
An example of such a request is shown here:
POST https://google.com HTTP/1.1
Connection: Keep-Alive
Content-Type: text/plain
Accept: application/json
EmptyHeader:
Host: https://google.com
Our EmptyHeader parameter is null so NSwag is trying to run this:
request_.Headers.TryAddWithoutValidation("EmptyHeader", EmptyHeader!= null ? System.Convert.ToString(EmptyHeader, System.Globalization.CultureInfo.InvariantCulture) : null);
Which as a result ends up adding a header with an empty value.
Is this the expected behavior for NSwag or should we be adding an if check to the template to make sure that if the value is null we should not try to add it to the header at all.

Closing as PR is merged.


Enable syntax highlighting and automatic prefixes

...with @YASGUI's YASQE!
https://www.npmjs.com/package/yasgui-yasqe

So at b824d47 it works when the page loads for the first time, but I switch view (vue-router) and go back to the editor, YASQE lost its grip on the textarea and it's a basic textarea. It should still be a YASQE-styled textarea.


[prototype] Add sample with flyweight

Add sample.

clone: sallow copy by using fliweight
free: unregister fliweight

Do it on lighttpd_multithread if it is usuful


How to hook a click, dblclick or contextmenu event to a dash-Item component?

Hello bensladden,
thank you very much for your continued effort in developing such a nice module.
I am trying to fire a dblclick event so that a configuration window opens up when the user double clicks on a dash-item.
So far I had no luck.
Is there any example I can use?
I am also trying to fire a click or a contextmenu event but nothink happens either.
Thank you very much for any help.

Hi @bscbrn,
Here is an example of dbclick and contextmenu click: https://codesandbox.io/s/vue-responsive-dash-xnenx. Note the .native is required as it is a component not a div See: https://vuejs.org/v2/guide/components-custom-events.html#Binding-Native-Events-to-Components

Hi @bensladden,
thank you very much this works very well.


[P4_Symbolic] Modified p4_symbolic/symbolic/expected/hardcoded.smt2 [Evaluate parsers symbolically.]

Keyword Check:
~/sonic-buildimage/src/sonic-p4rt/sonic-pins$ ~/tools/keyword_checks.sh .
Keyword check Passed.
Build Result:
/sonic/src/sonic-p4rt/sonic-pins$ bazel build $BAZEL_BUILD_OPTS ...
INFO: Analyzed 634 targets (0 packages loaded, 0 targets configured).
INFO: Found 634 targets...
INFO: From Compiling p4_symbolic/sai/parser.cc [for host]:
p4_symbolic/sai/parser.cc: In function 'absl::lts_20230802::StatusOr<std::vectorz3::expr > p4_symbolic::EvaluateSaiParser(const SymbolicPerPacketState&)':
p4_symbolic/sai/parser.cc:93:51: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
93 |   constraints.push_back(icmp.valid == (ipv4.valid && ipv4.protocol == 0x01 ||
|                                        ~^~~~~~~~~~~~~~
p4_symbolic/sai/parser.cc:95:50: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
95 |   constraints.push_back(tcp.valid == (ipv4.valid && ipv4.protocol == 0x06 ||
|                                       ~^~~~~~~~~~~~~~
p4_symbolic/sai/parser.cc:97:50: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
97 |   constraints.push_back(udp.valid == (ipv4.valid && ipv4.protocol == 0x11 ||
|                                       ~^~~~~~~~~~~~~~
INFO: From Compiling p4_symbolic/main.cc [for host]:
In file included from ./gutil/io.h:22,
from p4_symbolic/main.cc:30:
p4_symbolic/main.cc: In function 'absl::lts_20230802::Status {anonymous}::ParseAndEvaluate()':
p4_symbolic/main.cc:114:75: warning: 'absl::lts_20230802::StatusOr<std::optional<p4_symbolic::symbolic::ConcreteContext> > p4_symbolic::symbolic::Solve(const std::unique_ptr<p4_symbolic::symbolic::SolverState>&, const Assertion&)' is deprecated: Use the overload Solve(SolverState&, const Assertion&) instead. [-Wdeprecated-declarations]
114 |           p4_symbolic::symbolic::Solve(solver_state, table_entry_assertion));
|                                                                           ^
./gutil/status.h:294:43: note: in definition of macro '__ASSIGN_OR_RETURN'
294 |   auto __ASSIGN_OR_RETURN_VAL(LINE) = expr;
|                                           ^~~~
p4_symbolic/main.cc:112:7: note: in expansion of macro 'ASSIGN_OR_RETURN'
112 |       ASSIGN_OR_RETURN(
|       ^~~~~~~~~~~~~~~~
In file included from ./p4_symbolic/parser.h:28,
from p4_symbolic/main.cc:33:
./p4_symbolic/symbolic/symbolic.h:278:48: note: declared here
278 | absl::StatusOr<std::optional> Solve(
|                                                ^~~~~
INFO: From Compiling p4_symbolic/symbolic/util.cc [for host]:
INFO: From Compiling p4_symbolic/ir/cfg_test.cc:
In file included from p4_symbolic/ir/cfg_test.cc:1:
./p4_symbolic/ir/cfg.h:79:3: warning: multi-line comment [-Wcomment]
79 |   //             /
|   ^
INFO: From Compiling p4_symbolic/ir/ir.cc:
In file included from p4_symbolic/ir/ir.cc:39:
./p4_symbolic/ir/cfg.h:79:3: warning: multi-line comment [-Wcomment]
79 |   //             /
|   ^
INFO: From Compiling p4_symbolic/ir/cfg.cc:
In file included from p4_symbolic/ir/cfg.cc:15:
./p4_symbolic/ir/cfg.h:79:3: warning: multi-line comment [-Wcomment]
79 |   //             /
|   ^
p4_symbolic/ir/cfg.cc:349:5: warning: multi-line comment [-Wcomment]
349 |     //      /
|     ^
p4_symbolic/ir/cfg.cc:388:7: warning: multi-line comment [-Wcomment]
388 |       //      /
|       ^
p4_symbolic/ir/cfg.cc: In function 'p4_symbolic::ir::ControlPath p4_symbolic::ir::{anonymous}::LongestCommonPrefix(const ControlPath&, const ControlPath&)':
p4_symbolic/ir/cfg.cc:101:16: warning: comparison of integer expressions of different signedness: 'int' and 'std::vector<std::__cxx11::basic_string >::size_type' {aka 'long unsigned int'} [-Wsign-compare]
101 |   while (index < l.size() && index < r.size() && l[index] == r[index]) {
|          ^~~~
p4_symbolic/ir/cfg.cc:101:36: warning: comparison of integer expressions of different signedness: 'int' and 'std::vector<std::__cxx11::basic_string >::size_type' {aka 'long unsigned int'} [-Wsign-compare]
101 |   while (index < l.size() && index < r.size() && l[index] == r[index]) {
|                              ^~~~
INFO: Elapsed time: 47.273s, Critical Path: 14.70s
INFO: 90 processes: 7 internal, 83 linux-sandbox.
INFO: Build completed successfully, 90 total actions
Test Result:
/sonic/src/sonic-p4rt/sonic-pins$ bazel test $BAZEL_BUILD_OPTS --cache_test_results=no ...
INFO: Analyzed 634 targets (0 packages loaded, 0 targets configured).
INFO: Found 423 targets and 211 test targets...
INFO: Elapsed time: 211.352s, Critical Path: 116.99s
INFO: 265 processes: 320 linux-sandbox, 18 local.
INFO: Build completed successfully, 265 total actions
//dvaas:port_id_map_test                                                 PASSED in 0.8s
//dvaas:test_run_validation_golden_test                                  PASSED in 0.1s
//dvaas:test_run_validation_test                                         PASSED in 0.6s
//dvaas:test_run_validation_test_runner                                  PASSED in 0.0s
//dvaas:test_vector_stats_diff_test                                      PASSED in 0.1s
//dvaas:test_vector_stats_test                                           PASSED in 0.0s
//dvaas:test_vector_test                                                 PASSED in 0.6s
//dvaas:user_provided_packet_test_vector_diff_test                       PASSED in 0.1s
//dvaas:user_provided_packet_test_vector_test                            PASSED in 0.1s
//gutil:collections_test                                                 PASSED in 0.6s
//gutil:io_test                                                          PASSED in 0.5s
//gutil:proto_matchers_test                                              PASSED in 0.6s
//gutil:proto_ordering_test                                              PASSED in 0.5s
//gutil:proto_test                                                       PASSED in 0.5s
//gutil:status_matchers_test                                             PASSED in 0.5s
//gutil:test_artifact_writer_test                                        PASSED in 0.7s
//gutil:testing_test                                                     PASSED in 0.5s
//gutil:timer_test                                                       PASSED in 5.1s
//gutil:version_test                                                     PASSED in 1.8s
//p4rt_app/tests:resource_limits_test                                    PASSED in 2.5s
//p4rt_app/tests:response_path_test                                      PASSED in 6.3s
//p4rt_app/tests:role_test                                               PASSED in 1.7s
//p4rt_app/tests:state_verification_test                                 PASSED in 3.1s
//p4rt_app/tests:vrf_table_test                                          PASSED in 2.4s
//p4rt_app/tests/lib:app_db_entry_builder_test                           PASSED in 0.0s
//p4rt_app/utils:event_data_tracker_test                                 PASSED in 0.0s
//p4rt_app/utils:table_utility_test                                      PASSED in 1.5s
//sai_p4/instantiations/google:clos_stage_test                           PASSED in 0.5s
//sai_p4/instantiations/google:fabric_border_router_p4info_up_to_date_test PASSED in 0.0s
//sai_p4/instantiations/google:middleblock_p4info_up_to_date_test        PASSED in 1.4s
//sai_p4/instantiations/google:sai_nonstandard_platforms_build_test      PASSED in 0.0s
//sai_p4/instantiations/google:sai_nonstandard_platforms_cc_test         PASSED in 1.0s
//sai_p4/instantiations/google:sai_p4info_fetcher_test                   PASSED in 0.8s
//sai_p4/instantiations/google:sai_p4info_test                           PASSED in 1.2s
//sai_p4/instantiations/google:sai_pd_proto_test                         PASSED in 0.0s
//sai_p4/instantiations/google:sai_pd_util_test                          PASSED in 0.6s
//sai_p4/instantiations/google:tor_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google:union_p4info_up_to_date_test              PASSED in 0.1s
//sai_p4/instantiations/google:wbb_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google/test_tools:table_entry_generator_helper_test PASSED in 1.4s
//sai_p4/instantiations/google/test_tools:test_entries_test              PASSED in 0.9s
//sai_p4/instantiations/google/tests:p4_fuzzer_integration_test          PASSED in 3.7s
//sai_p4/tools:p4info_tools_test                                         PASSED in 0.6s
//sai_p4/tools:packetio_tools_test                                       PASSED in 0.8s
//tests:thinkit_gnmi_interface_util_tests                                PASSED in 1.0s
//tests/lib:p4info_helper_test                                           PASSED in 1.1s
//tests/lib:p4rt_fixed_table_programming_helper_test                     PASSED in 0.9s
//tests/lib:packet_generator_test                                        PASSED in 27.2s
//tests/lib:switch_test_setup_helpers_golden_test                        PASSED in 0.1s
//tests/lib:switch_test_setup_helpers_golden_test_runner                 PASSED in 0.1s
//tests/qos:gnmi_parsers_test                                            PASSED in 0.0s
//tests/qos:gnmi_parsers_test_runner                                     PASSED in 0.1s
//thinkit:bazel_test_environment_test                                    PASSED in 2.4s
//thinkit:generic_testbed_test                                           PASSED in 0.9s
//thinkit:mock_control_device_test                                       PASSED in 0.7s
//thinkit:mock_generic_testbed_test                                      PASSED in 0.8s
//thinkit:mock_mirror_testbed_test                                       PASSED in 0.8s
//thinkit:mock_ssh_client_test                                           PASSED in 0.0s
//thinkit:mock_switch_test                                               PASSED in 0.7s
//thinkit:mock_test_environment_test                                     PASSED in 0.1s
//thinkit:switch_test                                                    PASSED in 0.7s
//sai_p4/instantiations/google/tests:p4_constraints_integration_test     PASSED in 0.8s
Stats over 5 runs: max = 0.8s, min = 0.7s, avg = 0.8s, dev = 0.1s
//sai_p4/instantiations/google/test_tools:table_entry_generator_test     PASSED in 43.8s
Stats over 50 runs: max = 43.8s, min = 0.8s, avg = 4.4s, dev = 11.6s
Executed 211 out of 211 tests: 211 tests pass.
INFO: Build completed successfully, 265 total actions

/azp run

Co-authored-by: Srikishen Pondicherry Shanmugam<EMAIL_ADDRESS>

/azp run


Provide compatibility with Pillow

It's a very simple change. Try Pillow and if not found, fall back to PIL.

Ignore. My fault


Use existing AllowSampleCollection documentation

Wasn't obvious AllowSampleCollection was being discussed in the list, so add more information about it and use existing info from https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-atp/configure-endpoints-script-windows-defender-advanced-threat-protection#configure-sample-collection-settings

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

Thanks for you contribution! Before we can merge your changes, we need you to sign the CLA permitting us to use your work.
Assuming you're the same contributor from PR #1001, we've reviewed the issue you raised around government employees and the potential complications regarding copyright with our legal team.
The CLA covers the situation where you are contributing in the course of your employment, regardless of who that employer is. We ask you to certify that you have permission from your employer to make these contributions. (Because the work that you're doing for the government is not to specifically contribute to this content, and because this CLA does address doing the work in the course of your regular employment, no other CLA is required.)
If your reading of the situation is different than ours, then as much as we appreciate your contribution, we're not able to use it. Thanks.

@lizap Sounds like there's an issue with section 9 of the CLA. Something about state law. Lawyers will figure it out.

@mjcaparas, can we close this PR?

Ok, we can close PR.


unicode string input

no unicode support in linenoise from antirez, some work seems to have been done by msteveb:
https://github.com/msteveb/linenoise

This could be solved by switching to readline


Need callbacks at the end of every N epochs

Is your feature request related to a problem? Please describe.
I need callbacks at the end of each epoch to gather and stream some user-defined metrics in real-time.
Describe the use case
I need callbacks at the end of each epoch to gather and stream some user-defined metrics.
Describe the solution you'd like
Callbacks on the lines of on_epoch_end, on_batch_begin etc
Describe alternatives you've considered
Nothing so far. I expected this to be already present but not able to get it from logs or github.
Additional context
Nothing else, hopefully the request is evident since other platforms already have it.

You can find it here https://github.com/uber/ludwig/blob/67fec7ab1908972c3e21c333f283d3af7d118e80/ludwig/models/model.py#L677

Thanks @ifokeev . Do you mean that contrib is needed in order to add a callback? I can implement it but was hoping that there would be a pluggable way.

@arunmk yeah, try contrib. It will not so difficult as you expected
from ludwig.contribs import contrib_registry
from ludwig.experiment import cli

instance = YourClass.import_call(argv_list)

contrib_registry['instances'].append(instance)

cli(argv_list)

@ifokeev perfect, this works very well. I followed the comet_ml code and your examples and have been able to hook into the train_epoch_end. Thanks a lot for this!

close the issue then, please

@ifokeev thanks for your help on this. @arunmk we could probably disentangle the callbacks from the contrib package and add new ones. if you list the ones you need I CAN MARK THIS AS A FEATURE REQUEST.

@w4nderlust thanks for mentioning that. Currently my requirement is for train_epoch_end. I will surely very soon have requirements around batch runs and also for predictions as they seem to be the places where I can quickly instrument for metrics. Some other frameworks provide similar functionality as you already know (https://www.tensorflow.org/api_docs/python/tf/keras/callbacks/Callback). It will be very helpful to us if there can be first-class support for these. Currently this method seems to be very good. If there is some documentation, this mechanism should be sufficient for us.

@w4nderlust does the above comment answer your question?


Improve error message for unavailable mnemonic file

When running bundler, it is not clear that mnemonic file is missing or is unavailable.

What do you mean by unavailable?

What do you mean by unavailable?

Mnemonic file doesn't exist. The error message is not clear at the moment.


Store multiple policies in the index

Prior to making more substantial changes to the configuration I've quickly made the change to store multiple policies for each hostname:

We now iterate over each "policy" at the hostname of the index, finding the first one where the "rules" apply.
Updated the log ordering in tests - we now debug log when checking the conditions prior to knowing we've selected a policy, so the "policy selected" statement comes after

For the record, I want to write here that I would not follow the path opened by this PR.  Let me try my (last) bullet and if still any of you do not buy this, I will accept it and approve this.
TL;DR: let's not reinvent the wheel here.
Envoy, for routing, also is doing a similar task as the wasm needs to do. Envoy has a set of routes indexed by domains and some matchers to select one route out of multiple routes for a given domain. This is what Envoy calls VirtualHost. And each virtualhost object, has a list of domains.
virtual_hosts:
  - name: gateway-system/kuadrant-ingressgateway/http/api_toystore_com
    domains:
      - api.toystore.com

It turns out that domains field, as explained in their doc,
The longest wildcards match first. Only a single virtual host in the entire route configuration can match on *. A domain must be unique across all virtual hosts or the config will fail to load.

And, more importantly, the domain search order is as follows (also from the doc).
        Exact domain names: www.foo.com.

        Suffix domain wildcards: *.foo.com or *-bar.foo.com.

        Prefix domain wildcards: foo.* or foo-*.

        Special wildcard * matching any domain.

In conclusion: the order of virtual_hosts does not matter.
What are we doing in this PR? We are making the order of policies (the virtualhosts of our Wasm configuration) to matter. Moreover, we are making the configuration far more complicated to understand as we are allowing multiple "policies" under the same domain. It is totally counter intuitive IMO. And Wasm policy rules are meant to do that precisely.
I am advocating for following Envoy's approach. In the first place, I would implement, in Wasm configuration terms:
A hostname must be unique across all policies or the config will fail to load.

Currently, the Wasm-shim only implements The longest wildcards match first. I was very careful to have that functionality from the very beginning. But we should also change the trie implementation with something smarter about
        Exact domain names: www.foo.com.

        Suffix domain wildcards: *.foo.com or *-bar.foo.com.

        Prefix domain wildcards: foo.* or foo-*.

        Special wildcard * matching any domain.

So, instead of allowing the wasm configuration enabled by this PR, which is something like this:
      policies:
      - hostnames:
        - '*'
        name: gateway-system/gw
        rules:
        - actions:
          - data:
            - static:
                key: limit.limit1__e3f1f251
                value: "1"
            extension: limitador
            scope: gateway-system/A
          conditions:
          - allOf:
            - operator: eq
              selector: request.url_path
              value: /toys
            - operator: eq
              selector: request.method
              value: GET
      - hostnames:
        - '*'
        name: gateway-system/gw
        rules:
        - actions:
          - data:
            - static:
                key: limit.limit1__e3f1f251
                value: "1"
            extension: limitador
            scope: gateway-system/B
          conditions:
          - allOf:
            - operator: startswith
              selector: request.url_path
              value: /
            - operator: eq
              selector: request.method
              value: GET

I suggest having something like:
      policies:
      - hostnames:
        - '*'
        name: policyA
        rules:
        - name: ruleA
          actions:
          - data:
            - static:
                key: limit.limit1__e3f1f251
                value: "1"
            extension: limitador
            scope: gateway-system/A
          conditions:
          - allOf:
            - operator: eq
              selector: request.url_path
              value: /toys
            - operator: eq
              selector: request.method
              value: GET
        - name: ruleB
          actions:
          - data:
            - static:
                key: limit.limit1__e3f1f251
                value: "1"
            extension: limitador
            scope: gateway-system/B
          conditions:
          - allOf:
            - operator: startswith
              selector: request.url_path
              value: /
            - operator: eq
              selector: request.method
              value: GET

If the issue is tracking which policy and rule was activated, we can easily handle that adding name field to the rules as in the example above. Let's not create one "so-called-policy" per listener-HTTPRouteRule pair. Kuadrant's control plane can write HTTPRules for a given listener in the corresponding policy/rule pair. And still follow the same order of preference defined by the Gateway API.
cc @alexsnaps

My 2 cents:
I agree that the order of the configs should not matter. The rest I honestly (and deeply respectfully) believe is conflating API concern with implementation detail.
Indexing "policies" by hostname does not mean the config has to require unique hostnames. I can see how that could be important for one who writes an Envoy config, where possibly the mental model of the topology needs to fit the uniqueness constraint of the domain names. Arguably, that could be because Envoy, in this case, has decided to leak an implementation decision (indexation) to its API, thus shaping the way its users have to write configs.
The wasm shim is not Envoy though. In the whole scope of Kuadrant, users are not expected to write wasm configs themselves. Rather, they are invited to think in terms of Gateway API resources. How those resources are organised will dictate the mental model users will establish, to reason about the state of things, how requests will be handled.
Even without writing the wasm configs themselves and perhaps more even so because of that, having an API that reflects that mental model is IMO a good thing. In fact, I even wonder (again in a very respectful manner) why gateways in general wouldn't give this idea a shot.

I agree that the order of the configs should not matter. The rest I honestly (and deeply respectfully) believe is conflating API concern with implementation detail.

I think we had agreed that the order would matter and be ordered by the Kuadrant Operator. But these are NOT virtual hosts, the things ordered are the HTTPRouteRules, that happen to _also have a hostname associated. At this stage I'll be honest I'm getting slightly frustrated. We are running in circles and not getting to any working software.
The order that matters in this PR isn't the hostname's, but the "Rule", that's what is ordered. This PR _fixes the issue where when having 2 "so called policies" have the same hostname, instead of replacing the last one seen (in the config's order, as we had decided), it appends it. Then, when looking up policies based on the hostname, searches for the first policy that matches given the other attributes of the request. Again, as we had discussed.
So someone tells me where this diverges from what was agreed upon. If now there are better ways to achieve the same, which I'm sure there is, as I consider this config utter convoluted for reasons that I fail to see... sure! But in the meantime this is working software!

I agree that the order of the configs should not matter.
I think we had agreed that the order would matter and be ordered by the Kuadrant Operator.

Sorry, @alexsnaps. I wasn't clear in my comment before. I do not want to change anything here.
My comment was more in the general sense of, as a principle, maybe in a perfect world, users should not have to care about the order of their configs – and neither they will, while something else does that for them, whether it's the wasm module or the Kuadrant Operator. And yes, we agreed to be the latter, for reasons already discussed (e.g. identical source of truths whose precedence can only be known at the level of the operator that handles). In fact, I've already started working on the part of sorting policies first by hostname.
But as you rightfully pointed out, it's the ordering by full matching rules (not only hostnames) that matters. I only focused on hostnames before because of the current structure of the config. For a better discussion about other ways to struct the config, we have #108.

conflating API concern with implementation detail

That was in reference to the criticism raised against allowing multiple policies per hostname, not about the PR, which I'm totally support.

I think we're in agreement that this is moving the direction we had decided (albeit a patch on the old convoluted config vs a new one), so I'm going to merge and we can continue to discuss potential solutions in #104 and #108


New version: IERSConventions v1.2.0

Registering package: IERSConventions
Repository: https://github.com/JuliaSpaceMissionDesign/IERSConventions.jl
Created by: @andreapasquale94
Version: v1.2.0
Commit: af24be602b423a24ad32ea75ad10cdc29262b23c
Reviewed by: @andreapasquale94
Reference: https://github.com/JuliaSpaceMissionDesign/IERSConventions.jl/commit/af24be602b423a24ad32ea75ad10cdc29262b23c#commitcomment-138443086
Description: IERS Conventions made easy.
Release notes:

GCRF to ITRF higher order rotation matrices

[noblock]
There is a merge conflict on this PR.
@andreapasquale94 Can you re-trigger Registrator? This will fix the merge conflict.


Cloudcore is exist when I init it. and I can't find cloudcore.yaml in /etc/kubeedge/config

Cloudcore is exist when I init it. and I can't find cloudcore.yaml in /etc/kubeedge/config
Command:
root@k8scludes1:~# sudo keadm init --advertise-address=<IP_ADDRESS> --kubeedge-version=1.12.1  --kube-config=/root/.kube/config
the report message are as follow:
Error: CloudCore is already running on this node, please run reset to clean up first
Usage:
keadm init [flags]
Examples:
keadm init

This command will render and install the Charts for Kubeedge cloud component

keadm init --advertise-address=<IP_ADDRESS> --profile version=v1.9.0 --kube-config=/root/.kube/config

kube-config is the absolute path of kubeconfig which used to secure connectivity between cloudcore and kube-apiserver

a list of helm style set flags like "--set key=value" can be implemented, ref: https://github.com/kubeedge/kubeedge/tree/master/manifests/charts/cloudcore/README.md

Flags:
--advertise-address string    Use this key to set IPs in cloudcore's certificate SubAltNames field. eg: <IP_ADDRESS>,<IP_ADDRESS>
-d, --dry-run                     Print the generated k8s resources on the stdout, not actual excute. Always use in debug mode
--external-helm-root string   Add external helm root path to keadm.
-f, --files string                Allow appending file directories of k8s resources to keadm, separated by commas
--force                       Forced installing the cloud components without waiting.
-h, --help                        help for init
--kube-config string          Use this key to set kube-config path, eg: $HOME/.kube/config (default "/root/.kube/config")
--kubeedge-version string     Use this key to set the default image tag
--manifests string            Allow appending file directories of k8s resources to keadm, separated by commas
--profile string              Set profile on the command line (iptablesMgrMode=external or version=v1.9.1)
--set stringArray             Set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
execute keadm command failed:  CloudCore is already running on this node, please run reset to clean up first

Cloudcore's configuration file, after version 1.9, should be placed in configmap and can be viewed through the following command:
kubectl -n kubeedge edit configmap cloudcore

This PR is suitable for moving to the kubeedg repo: https://github.com/kubeedge/kubeedge


[Backport] More optimize CNF conversion of filters

Backport of #9634 to 0.18.0.

Clean backport.


master update: add unixodbc and sctp support in alpine

the standard erlang otp distribution comes with 45 apps under lib,
here provide 44 of them, without jinterface for java dependency,
now it has all apps same as the debian based erlang:latest;
image size is at 68.18 MB.
$ docker run -it --rm otp:21.0-rc0-fdce942-alpine sh
/ # ls /usr/local/lib/erlang/lib/
asn1-5.0.1             eldap-1.2.2            os_mon-2.4.2
common_test-1.15.1     erl_docgen-0.7         otp_mibs-1.1.1
compiler-7.1           erl_interface-3.10     parsetools-2.1.5
cosEvent-2.2.1         erts-9.0.2             public_key-1.4.1
cosEventDomain-1.2.1   et-1.6                 reltool-0.7.4
cosFileTransfer-1.2.1  eunit-2.3.3            runtime_tools-1.12.1
cosNotification-1.2.2  hipe-3.16              sasl-3.0.4
cosProperty-1.2.2      ic-4.4.2               snmp-5.2.6
cosTime-1.2.2          inets-6.4              ssh-4.5
cosTransactions-1.3.2  kernel-5.3.1           ssl-8.2
crypto-4.0             megaco-3.18.2          stdlib-3.4.1
debugger-4.2.2         mnesia-4.15            syntax_tools-2.1.2
dialyzer-3.2           observer-2.4           tools-2.10.1
diameter-2.0           odbc-2.12              wx-1.8.1
edoc-0.9               orber-3.8.3            xmerl-1.3.15
/ # ls /usr/local/lib/erlang/lib/ | wc -l
45

the commit 1d0c80c is in master.

the commit 1d0c80c is in master.


No Scroll in android

hi, i tried marquee label in react-native android, text doesn't displays and scroll. please give me a suggestion to solve the issue.

Please respond

For me the text didn't display until I set a height

Mr@Hussain i  have a Solution  for this , when we are using text that text should contain height and width must.
like this......
<MarqueeLabel
                        style={styles.marqueeLabel}
                        scrollDuration={20.0}>
                        Pro Football Scores: Pro Basketball
            Pro Football Scores: Pro Basketball
                    </MarqueeLabel>
this is used for styles:

marqueeLabel: {
    backgroundColor: 'white'
    width:windowSize.width,
    marginRight:50,
    height:20,
    fontSize:(Platform.OS === 'ios')?15:24,
    fontFamily:'Roboto-Regular',
    color:(Platform.OS === 'ios') ?'#092a53':'#092a53'
},