Travis optimizations

disabled GC on running unit tests and cs fixer
allow to run more parallel processes than CPUs
ignore special folders ('_files' and 'AllTests') to run with phpunit
no longer keep order of parallel processes
this one isn't for all over performance but for humans - If you wait for a specific test case you will be informed asap the component has been ready

This should be make little performance improvements.
A much better performance improvement would be to run all unit tests and cs fixer in parallel, too.
But I currently haven't a good idea how to do that simplified.

Merged, thanks @marc-mabe!
master: zendframework/zf2@a98e78975c6963862e77621e3f7611d3d29ed290
develop: zendframework/zf2@0f4e072fa481e3481f9d4ab2320f5fe0b60881b1

@marc-mabe this seems to break https://travis-ci.org/zendframework/zf2/jobs/46273266#L1171 :-(

mh interesting - this error doesn't come up on my tests.
than let us remove the gc disabling

It only happens on develop: I assume a very slow test in Zend\Math is
involved
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
On 8 January 2015 at 09:33, Marc Bennewitz<EMAIL_ADDRESS>wrote:

mh interesting - this error doesn't come up on my tests.
than let us remove the gc disabling
—
Reply to this email directly or view it on GitHub
https://github.com/zendframework/zf2/pull/7070#issuecomment-69149883.

It's on exporting tested results of Zend\Math and it has 312585 assertions.

Probably due to RNG tests...

test coverage should not be ignored only because it's slow

@marc-mabe repeatedly stress-testing the same segment of code during a statistical benchmark isn't really useful for us (for the purpose of coverage)

the problem is that this test isn't only a stress test. It would be optimal to reduce the cycles for rnd stress test to be 1 to be a normal unit test.

@marc-mabe isn't @coversNothing on the single test that runs the stress-operations enough? Worth trying, imo

@Ocramius Good idea but even with @coversNothing the rnd test runs into out of memory with zend.enable_gc=0 and coverage enabled.
Results on running Math/RandTest.php on my machine:
gc off + coverage on = out of memory
gc off + coverage on +  @coversNothing = out of memory
gc on + coverage on = 6.14 minutes, 9.75Mb
gc on + coverage on +  @coversNothing = 6.06 minutes, 9.75Mb
gc off + coverage off = out of memory
gc on + coverage off = 49.73 seconds, 6.75Mb
So I think gc needs to be enabled on running phpunit and the biggest slow down is code coverage generation.
Btw. the cs fixer is ~ 1-5% faster with gc off


Missing Functionality to Restore Inheritance for Category Layouts when slot_config is Modified

PHP Version: 8.3   | Shopware Version: 6.6.*  | Affected area / extension: Platform(Default)

Actual behaviour:
In Shopware, category layouts typically inherit from the assigned Shopping Experience layout as long as no direct changes have been made to the category layout. In such cases, the slot_config column in the category_translation table remains filled with an empty JSON array ([]).
However, if changes are made directly to the category layout and saved, the slot_config column is populated with the current data, and the inheritance from the Shopping Experience layout ends.
Problem:
Currently, there is no direct button or functionality in Shopware 6 to restore the inheritance for category layouts after the slot_config column has been populated. This makes it impossible to easily revert to the original state, where the category layout inherits from the Shopping Experience layout.
Expected behaviour:
There should be an option in the Shopware admin (e.g., a button or menu item) to reset the slot_config and restore inheritance from the assigned Shopping Experience layout.
How to reproduce:
Steps to Reproduce:

Go to the Categories module in the Shopware admin panel.
Select a category that has an assigned Shopping Experience layout.
Observe that the slot_config column in the database (category_translation table) contains an empty JSON array ([]).
Make a change to the category layout (e.g., update a slot or content block) and save.
Check the slot_config column again—it will now be populated with the layout data, and the inheritance from the Shopping Experience layout will end.
Attempt to restore the inheritance—observe that no functionality exists to reset the slot_config to its default (empty) state.

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-39891
[created from NEXT-39891, comment 520096]


Improving label on configuration for plugin section

In this way it's more clear to the users that aren't all the plugins but just the one detected by the portal itself.

I think I rather solve this by adding a FAQ with the explanation on the question "Why is a plugin missing", i'll think about it for a bit though


ESLint suggestions for "Did you mean" messages

The lint issues by the following rules can provide "Did you mean" suggestions in the reported error message:

@graphql-eslint/fields-on-correct-type
@graphql-eslint/known-argument-names
@graphql-eslint/known-type-names
@graphql-eslint/possible-type-extension
@graphql-eslint/scalar-leafs
@graphql-eslint/value-literals-of-correct-type

It is currently not possible to use that suggestion in the editor (e.g. VS Code). It would be great to add ESLint suggestions to those rules, so that the suggestions can be semi-automatically be applied.
Since those all wrap validations from https://github.com/graphql/graphql-js, upstream changes might be necessary. (See also the search results for repo:graphql/graphql-js "Did you mean" path:src/validation/__tests__/*Rule-test.ts.)
Example
query Test($id: string) { … }

Lint error: Unknown type "string". Did you mean "String"?
Expected suggestion: Change to "String".

Sound good, thanks for the catch! will try to add suggestions this week

suggestions can be tested in the following alpha version 3.14.0-alpha-20221220000306-eefc8db

Cool, this seems to work pretty well!


chore: tweak benchmarking

Hm.. Not so sure if benchmarking works. Let’s play with this a bit more ;D

Closing in favour of #78.


fix: ci images need to remove ldflags_dirs flag

Issue #, if available:
Description of changes:
Fixes the image building issue where ldflags_dirs flag was causing python issues.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

For context, https://github.com/aws/aws-codebuild-docker-images/pull/461

pyenv 2.0.0 removed ldflags_dirs as it "is not needed for Python and causes failures". The python runtime config files use the outdated calls. This pull request removes all references to ldflags_dirs.


feat(mods): Redstone Pen and Project Red Illumination

I don't really like how the block lamps look with the shading and the light thingy surrounding it...
only good alternative I can find is https://modrinth.com/mod/rainbow-lamp which supports setting the rainbow lamp to a specific color. This doesn't add the other types of lamps seen in the screenshot though...
Theres also quark lamps. Do I think they are a bit too transparent...


Is it possible to extract a xml that has more than one loop?

I am using the xml that has more than one depth. For example
<users>
<user>
<profile>
</profile>
<addresses>
<address></addresses>
</addresses>
</user>
</users>

I need to get profile details and address details for each user. How can I extract ? Could anyone give the solution to solve this?

Hi @thangasujithas
Never tried. What do you get for the addresses field ?


Which fairseq files are used?

In the repo we have fairseq files in fast-knn-nmt/fast_knn_nmt/custom_fairseq/ as well as fast-knn-nmt/thirdparty/fairseq/ the files/changes to, for example, the sequence_scorer.py differ in these two. Which one is the correct one to use and why do the other ones exist?

@SirRob1997 Sorry for the confusion. The files in third_party is mainly used to extract features, and the files in custom_fairseq are codes that used for other purposes like computing ppl or bleu. Both of them are modified a little bit to server their own purpose.


[SPARK-33111][ML][Follow-Up] aft transform optimization - predictQuantiles

What changes were proposed in this pull request?
1, optimize predictQuantiles by pre-computing an auxiliary var.
Why are the changes needed?
In https://github.com/apache/spark/pull/30000, I optimized the transform method. I find that we can also optimize predictQuantiles by pre-computing an auxiliary var.
It is about 56% faster than existing impl.
Does this PR introduce any user-facing change?
No
How was this patch tested?
existing testsuites

Test build #129747 has started for PR 30034 at commit 720af45.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34353/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34353/

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34353/
Test FAILed.

Test build #129747 has finished for PR 30034 at commit 720af45.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/129747/
Test PASSed.

ping @huaxingao

It seems OK ; out of curiosity does this help much?

The change looks Okay to me.

Test build #130036 has started for PR 30034 at commit b0d3da7.

test code:
import org.apache.spark.ml.linalg._
import org.apache.spark.ml.regression._
import org.apache.spark.storage.StorageLevel

val df = spark.read.option("numFeatures", "2000").format("libsvm").load("/data1/Datasets/epsilon/epsilon_normalized.t").withColumn("censor", (col("label")+1)/2).withColumn("label", (col("label")+2)/2)
df.persist(StorageLevel.MEMORY_AND_DISK)
df.count

val aft = new AFTSurvivalRegression().setMaxIter(2)
val aftm = aft.fit(df)

val vectors = df.select("features").rdd.map(_.getAs[Vector](0)).collect

val start = System.currentTimeMillis; vectors.foreach(aftm.predictQuantiles); val end = System.currentTimeMillis; end - start

val start = System.currentTimeMillis; (0 until 100).foreach(_ => vectors.foreach(aftm.predictQuantiles)); val end = System.currentTimeMillis; end - start

result:
1, existing impl:
start: Long =<PHONE_NUMBER>115
end: Long =<PHONE_NUMBER>375
res3: Long = 41260
2, commit: https://github.com/apache/spark/pull/30034/commits/720af450275823349ceea3ab903b91e1734fa05c
Vectors.dense(_quantiles(0).map(_ * lambda)):
start: Long =<PHONE_NUMBER>072
end: Long =<PHONE_NUMBER>599
res3: Long = 28527
3, commit: https://github.com/apache/spark/pull/30034/commits/b0d3da781eb85706e0f29ab4c6ad47e2b6ad468f
while (i < quantiles.length) { quantiles(i) *= lambda; i += 1 }
start: Long =<PHONE_NUMBER>452
end: Long =<PHONE_NUMBER>777
res5: Long = 26325
I found that using SIMD will get another stable 6%~8% performace improvement.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34643/

Test build #130036 has finished for PR 30034 at commit b0d3da7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130036/
Test PASSed.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34643/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34643/
Test PASSed.

Merged to master

Thank you @srowen @huaxingao for reviewing!


Dropdown does not move if window is resized

After a dropdown is displayed, if window is resized, the dropdown does not move to match a change in position of activator.

Does anybody know if there is something that I can call to refresh the position after the page is resized?

This has been fixed in v1-dev. Resize reflows will not mess up the dropdown position

+1 still bug in 2020.
It seems this project has been abandoned since the last commit. Strange though for such a popular project


Hotfix/fetcher

Hi,
Not sure but should solve the problem of revalidate / mutate by keeping the default fetcher defined in the createSWR conf
In my case I am using axios but when using rev or mut it use fetch API

You're right, but it is also intended.
The revalidate and mutate are not hooks, meaning you can call them whenever you want. and the inject() can only be called inside setup().
We also have to take into consideration that your fix does not take into account that those methods are not 100% comptable with what inject(vswr) does provide. You can see that for example, the revalidation options only takes in the fetcher and the dedupingInterval (https://github.com/ConsoleTVs/vswr/blob/fd156e277eb0f060df80d8434ef19ea86b1529e3/src/api/revalidate.ts#L11)
Nevertheless, I am aware this causes confusion, so here's what I am going to do:

For you, you can currently abstract the fetcher into something like this:

export const commonOptions = {
  fetcher: (key) => axios.get(key).then(res => res.data)
}

Then you can use those common options in the createSWR and also the revalidate and mutate functions as such:
export const vswr = createSWR({
  ...commonOptions,
  // Other options
});

and you can also pass what you want into the functions as:
revalidate(key, { ...commonOptions, /* Other options...*/ })
mutate(key, value, { revalidateOptions: { ...commonOptions, /* Other options...*/ } })

For the matter, I do agree this the behaviour you describe is what should happen when possible. The happy part of this is that I do have a working framework-agnostic version of vswr at https://github.com/ConsoleTVs/swrev and I can implement this library using a few lines and that framework agnostic implementation. Once I do this, I will also add the feature described here and allow using the fetcher (among any other repeated options) on all the functions.

TLDR; I will be adding this as part of a rework of this package (internally only! - same API), meanwhile I've provided you with a simple fix (although a bit tedious to keep importing those options).

As for the estimated time for this feature, I expect to have it working this weekend, but it's my free time so I won't promise anything (since it also needs some testing).

Alright, the new version of vswr (1.0.0) has been released with this issue fixed. Feel free to open any other issue / PR if there are still errors somewhere.
Have a nice day.

ok both solutions work thanks


bug: Failing to send a transaction to precompile

Bug Report
Kakarot version f5d013f

Current behavior
It was tested on anvil using cast that it is possible to send a transaction directly to a precompile. To reproduce, run anvil and select a private key in the provided list. Then run cast send 0x0000000000000000000000000000000000000007 0x000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000003 --value 1 --private-key "selected_private_key". You can then verify that this indeed executed the ecmul precompile by running cast run "previous_transaction_hash". This should ouput:
Executing previous transactions from the block.
Traces:
  [6000] PRECOMPILE::ecmul{value: 1}(1, 2, 3)
    └─ ←<PHONE_NUMBER>059533942658390886683067124040920775575537747144343083137631628272 [3.353e75],<PHONE_NUMBER>6552368860946552437480515441416830039777911637913418824951667761761 [1.932e76]

However, in the case of Kakarot (ignoring the fact that for now only 4/9 precompiles are functionning), the contract that will be called is the starknet address compute using Accounts.compute_starknet_address(to). Meaning Kakarot will fail to call the correct precompile.
The following list of test call a precompile directly. Out of the list, currently only randomStatetest642 is being skipped, meaning the other tests are producing false positives.
randomStatetest644_d0g0v0_Shanghai
randomStatetest645_d0g0v0_Shanghai
randomStatetest645_d0g0v1_Shanghai
randomStatetest642_d0g0v0_Shanghai
modexpRandomInput_d0g0v0_Shanghai
modexpRandomInput_d0g1v0_Shanghai
modexpRandomInput_d1g0v0_Shanghai
modexpRandomInput_d1g1v0_Shanghai
modexpRandomInput_d2g0v0_Shanghai
modexpRandomInput_d2g1v0_Shanghai

Expected behavior
The precompiles should be correctly called when directly targeted from a transaction.

Additional information
This gives information about issue kkrt-labs/ef-tests#533.

Closed in favor of epix #856


test: guard Float80 on Windows

Windows does not support fp80 even on x86.  Adjust the test conditions
accordingly.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @stephentyrone

@swift-ci please test


Floating label position with pre-filled inputs

When using floating label, if an input is pre-filled (i.e. data from server) then the label displays in the starting position, inside the input, instead of above the input. This causes it to clamp with input text.

Mm? Any details why it was opened then closed?

Sorry, my mistake,  this bug happen with material-admin, not for
django-material.
Thank for your look.
2016-10-14 12:34 GMT+07:00 Mikhail Podgurskiy<EMAIL_ADDRESS>
Mm? Any details why it was opened then closed?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/viewflow/django-material/issues/182#issuecomment-253713537,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHlSj99pQWUsU80WuKegRyq7PbraOsoYks5qzxSCgaJpZM4KWmHb
.

--
Best Regards
(Mr.) Lê Công Tuấn
Email<EMAIL_ADDRESS>|       skype: t
<EMAIL_ADDRESS>Mobile<PHONE_NUMBER>1


Only 1st 10 pics shown in All pics, no pics shown in other folders

Describe the bug
The picker only shows the first 10 pictures in All Photos (or no pictures at all in other folders). The rest are invisible, although when I tap the empty space where the rest of the pics are supposed to be, a grey square appears there with the number of the selected pic.
To Reproduce
Steps to reproduce the behavior:
Present the viewcontroller.
Expected behavior
See all pictures
Smartphone (please complete the following information):

Device: iPhone8 Plus
OS: iOS 12.2

BSImagePicker configuration
No config.

Are you using iCloud photos?


Building scipy with MKL/VisualC++/GFortran

Here is a report of the issues i encountered, when building scipy. Hopefully scripts can be adjusted to work around them?
Scipy version was 1.3.x
MKL version was 2019.x
C Compiler was Visual studio 2015
Fortran compiler was MingW GFortran
Numpy was 1.16.x
The first issue was for the quadpack extension. when building the dll from the fortran files in integrate/quadpack/*.f, there was un unresolved error to dgtsv_, which is a lapack symbol, in dqc25f.f.
That dll is configured by Configuration.add_library(), so lapack options are not passed to it at all. So I am not sure how your build scripts manage to find that symbol from openblas or an other library in your build procedure.
In my case, i had to modify distutils to add a way to pass arguments to the final gfortran linking command, to be able to add the mkl library to the command line after the list of object files.
A cleaner workaround would be to be able to pass extra optional info to add_library(), to add librares and library dirs, and integrate/setup.py could add lapack info into those aruments?
Second issue was that because of that link (to mkl_rt.lib), the .def file generated by fortran for the dll contained the symbols
__IMPORT_DESCRIPTOR_mkl_rt @19 DATA
__NULL_IMPORT_DESCRIPTOR @20 DATA
Which caused LNK1127 when linking the pyd with the lib file that had been generated from the .def
To workaround this, i had to modify gnu.py in _link_wrapper_lib(), so before the generation of the .lib from the .def, such lines are filtered out. Since the method is suppoed to return a MSVC-compatible lib, i think this could be integrated
Last issue is for the g77 abi wrapper dll, which is built instead of a dummy one, if mkl is in the libraries.
With that combination of gfortran/MSVC, fortran and C objects can't be linked in the same library. Distutils tried to build a library with only the fortran sources for the _fblas extension, and obviously failed with unresolved symbols to the C sources.
For now, to workaround this, i modified needs_g77_abi_wrapper() to always return false..
For a cleaner one, i guess fortran and C would have to be split in two dlls instead of one for all extensions that need that wrapper.
I have an additional issue when i try to build a 32-bit version of the extension. For some reason, the 32-bit build adds  gfortran.lib gcc.lib mingw32.lib mingwex.lib to some link commands that the 64-bit build does not. I can see at the start of the build, the copies of libgfortran.a and libgcc.a in gfortran.linb and gcc.lib, but this is not done for mingw32.lib and mingwex.lib. Manually copying those two others, i still get an unresolved error to _fprintf. Not sure if i will insist on building on that platform.

Is there any particular reason why you don't use vc 2019? Community edition is sufficient.

For consistency between all the libraries used by a project, so we know exactly what are their dependencies. Everything is custom built with the same compiler and runtime library (python, numpy, scipy, other native libraries python depends on,..).

MSVC+gfortran with MKL on Windows has not been tested, and it's a wonder it works at all. The issues you are facing should be addressed in numpy.distutils --- Scipy itself doesn't do much build customization vs. this compiler combination.
Configuration.add_library does not build a dll, just either a static library or a loose collection of object files. The dlls are built just before linking the pyd extension, so the information about lapack is known at that time.

For needs_g77_abi_wrapper --- if the MKL in question doesn't need the wrappers, then that's fine and perhaps the check could be made smarter --- but if it does you'll likely see incorrect results or crashes.
The C/Fortran linking issue for the wrappers in this compiler combination is problematic, because distutils is a bit problematic here --- you'd need two C compilers in the same project and a way to indicate which compiler to use for which files, and I'm not immediately sure how it copes with that. The wrappers might also be rewritten with F2003 iso-c bindings.
The support for MSVC+gfortran in numpy.distutils is unfortunately currently a nasty hack with several limitations. I imagine well-tested patches to numpy.distutils (or scipy, for the applicable parts) cleaning up the situation would be welcome.

It seems like there's nothing to do here. Conda-forge took over the Gfortran + MSVC hack, and in practice it works. I think we'll be living with it for a long time.
For MKL I'd say: you simply must use the Intel Fortran compiler on Windows if you use MKL.
Let's close this, because there's nothing to change in SciPy.


Fix broken tests using DataProvider

This should fix the tests externally but I'm pretty sure this will break when imported due to namespacing differences. Glancing through the other FB hacklang repos I think un-namespacing the tests might be the best thing to do?
CC @fredemmott

Uh TravisCI wya

Two changes are needed here:

Add // @oss-disable: use type DataProvider; under every OSS import
Delete the global DataProvider in tests/shipit/github/annotations.php


Update RateLimits comment

GitHub search API ratelimits are changed recently.
Reference: https://developer.github.com/v3/search/#rate-limit
Rate limit for unauthenticated requests change from 5 to 10 per minute.
And, rate limit for authenticated requests change from 20 to 30 per minute.

You mean per minute, not per second (in your commit description).
Otherwise LGTM. Thanks!

Thank you for reviewing my PR!
I've fixed the typo and overwrite the commit message.


django.contrib.auth - Missing pages

Hello @MySecondLanguage
All pages required by django.contrib.auth are missing:
The following paths should work + registration page (outside of admin section)
accounts/register/ [name='register']
accounts/login/ [name='login']
accounts/logout/ [name='logout']
accounts/password_change/ [name='password_change']
accounts/password_change/done/ [name='password_change_done']
accounts/password_reset/ [name='password_reset']
accounts/password_reset/done/ [name='password_reset_done']
accounts/reset/<uidb64>/<token>/ [name='password_reset_confirm']
accounts/reset/done/ [name='password_reset_complete']

Please take a look.
ty!

validated. closing


feat: make federation info available before joining

Fixes #3514

Oh, I didn't see that you already queued it :laughing:


[OAP-1914]Update setup-miniconda version to v2

What changes were proposed in this pull request?
Closes #1914
Change setup-miniconda v1 to v2 to fix a warning issue from Github Action.
Based on the latest release from setup-miniconda, v2 has resolve this issue and released several days ago.
https://github.com/conda-incubator/setup-miniconda/releases
How was this patch tested?
This patch has been tested in my forked repo and not receive any warning in Arrow-cpp build from Github Action.
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@yao531441
Would you please help check this?

Hi, Weiting, thank you for your patch. Arrow-cpp build workflow have been deployed on our own cluster now, so this workflow will be removed this week.

Hi, Weiting, thank you for your patch. Arrow-cpp build workflow have been deployed on our own cluster now, so this workflow will be removed this week.

Ok, got it. After remove the workflow, I think we can close this issue and no need to use this patch.

Hi, Weiting, I have removed this workflow.

Hi, Weiting, I have removed this workflow.

Thanks, I will close the PR.
Could you help to add "Closes#1914" in your PR and we can have a record to close this issue.


Prevent db query execution for registry system username

Purpose
This PR fixes the issue of execution of retrieving userId from username query is executed 4-5 times per single authentication with the username as the REGISTRY_SYSTEM_USERNAME constant "wso2.system.user". To preventing db executions this fix checks the given username is the above constant and returns null while preserving the previous behaviour.
Related Issue

https://github.com/wso2/product-is/issues/21365

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to<EMAIL_ADDRESS>and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/12253519257

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/12253519257
Status: success


StorageLibraryChangeReader not working on Windows 10 Multi Session

On two Windows 10 Enterprise Multi Session VMs on Azure I am not getting any result using StorageLibraryChangeTracker.ReadChangesAsync() - with latest 20H2 image.
On Windows 10 Pro and Windows 10 Enterprise this does work without any issues.
Why is a Windows Runtime API, available since ages, not working on Windows 10 Enterprise Multi Session?
As a developer this does not make any sense.
Unzip the attached x64_debug.zip-file (alirgh_<IP_ADDRESS>_x64_Debug.zip)
and run
Add-AppxPackage -Register -Path AppxManifest.xml

inside a PowerShell window.
Run the now installed "alirgh"-App. Copy some files to the Documents-folder, observe that there is no output whatsoever. There should be a list of all changes being registered through StorageLibraryChangeReader printed. There is no indication that this should not work in the Microsoft documentation about this API:

storagelibrarychangetracker
storagelibrarychangereader

The sample project: ConsoleApplication2.zip

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: 92eb895d-1520-9400-3574-debf943009a9
Version Independent ID: 59280650-4614-3274-0fe6-a404ee4a2c85
Content: StorageLibraryChangeReader Class (Windows.Storage) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.Storage/StorageLibraryChangeReader.xml
Product: uwp
Technology: winrt-reference
GitHub Login: @lastnameholiu
Microsoft Alias: alholiu

Hello. We apologize for the delay in resolving this issue. As we transition to a new feedback system, we are closing all outstanding issues. Any issues that can be addressed will be tracked using a different internal tool, and we regret that we won't be able to provide further updates on this particular matter. We value your input and assure you that all feedback is reviewed. We recommend visiting the Microsoft Q&A site, where your issue may have already been discussed.


Moved environment variables to pydantic base settings

Loading of environment variables is not handled with pydantic's BaseSettings

Codecov Report

Merging #35 (d4dc180) into main (daa9762) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #35   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           12        12
  Lines          366       358    -8
=========================================
- Hits           366       358    -8

Impacted Files
Coverage Δ

meilisearch_fastapi/_config.py
100.00% <100.00%> (ø)

meilisearch_fastapi/routes/document_routes.py
100.00% <100.00%> (ø)

meilisearch_fastapi/routes/index_routes.py
100.00% <100.00%> (ø)

meilisearch_fastapi/routes/meilisearch_routes.py
100.00% <100.00%> (ø)

meilisearch_fastapi/routes/search_routes.py
100.00% <100.00%> (ø)

meilisearch_fastapi/routes/settings_routes.py
100.00% <100.00%> (ø)

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 daa9762...d4dc180. Read the comment docs.


chore(main): release 0.5.0

:robot: I have created a release beep boop
0.5.0 (2022-09-12)
Features

add security_policy to l7xlb module (686e549)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/apigee/terraform-modules/releases/tag/v0.5.0 :sunflower:


[Feature | Refac] Add HamiltonianEvolution

Fixes https://github.com/pasqal-io/horqrux/issues/8

Refactored repo to resemble pyqtorch
Added simple matrix-exp HamEvo

closing since superseeded by #11


Will not accept the word “stare.”

Entering the word “stare” causes the letters to be encircled in red, which indicates that it is not recognized as a word. Please see attached screen shot. Thank you for your assistance.

Never mind, I had it set on hard mode and forgot that the “e” needed to stay in its position. Thank you!


What's the difference between develop and master branch?

Hi,
I recently had a PR merged into knowm:master. However, I see that develop is the default branch. What's the difference between the two branches?

That was a mistake then. Please submit Prs against the develop branch. I merged your PR into develop.


ESLint parsing errors excluded from Annotations

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
ESLint output counts both errors from rule violations as well as parsing errors (see: 9 errors, 10 warnings):

But the Annotations created exclude the parsing error (see: 8 errors, 10 warnings):

Expected Behavior
I would expect parsing errors to be annotated, exactly like rule violations.
Super-Linter version
v6.3.0

Relevant log output
In attached screenshots.

Steps To Reproduce

Lint JS files with eslint that contain parsing errors.
Note the exclusion of these errors from the Annotations

Anything else?
No response

Hi there! Annotations are added by each tool individually, not by super-linter. I would try reproducing this running eslint outside super-linter, and eventually opening an issue in the eslint repository.


Editable params

Give parameters a way to be disabled based on current values. An "editable" field in param definition that takes a function that is evaluated on each render could be the way.

[x] Adapt ParamInput component to expect "editable" field from parameters and evaluate it based of current values. If false, it disables the corresponding input.
[x] Add styling to inputs to show they are currently disabled.
[x] Add validation on mechanic core to check that "editable" are either functions or boolean.
[x] Add examples in dsi-logo-maker

Here is a proposal for disabled components:

Can be checked by running npm run dev in mechanic-ui-components package.


[bug-1784][console]MySQL datasource cannot be used normally

close #1784

Sorry, this issue is not a bug, when the user chooses mysql as the database needs the user to actively place the mysql driver under lib instead of adding maven denpendcy under pom.xml.

Hi @shangeyao, thanks for you feedback.
The license of mysql dependency is an category-x[1], which is not expected by the asf-project.
If you want to use mysql as the database, you can place the mysql driver under the lib.
[1] https://apache.org/legal/resolved.html#category-x

closed. cc @wolfboys


Updated HITL tool README.md

Motivation and Context
Updated HITL tool README.md example usage section.
How Has This Been Tested
Launching sandbox app locally on MacBook Pro 2021.
Types of changes

Docs change

Checklist

[x] My code follows the code style of this project.
[x] I have updated the documentation if required.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[x] I have added tests to cover my changes if required.

LGTM! do you want to add a gif with the new hitl task?

Done!


Use recognised subdivisions for Austria

As per #283, is is possible to use standard ISO 3166-2 codes for Austria?
Per wikipedia:
AT-1  Burgenland Burgenland
AT-2  Kärnten Carinthia
AT-3  Niederösterreich Lower Austria
AT-4  Oberösterreich Upper Austria
AT-5  Salzburg Salzburg
AT-6  Steiermark Styria
AT-7  Tirol Tyrol
AT-8  Vorarlberg Vorarlberg
AT-9  Wien Vienna
Per python-holidays - the codes for AT subdivisions are: 'B', 'K', 'N', 'O', 'S', 'ST', 'T', 'V', 'W' (W is the default) which appears to be the first letter of the subdivision name (see wikipedia list).

Hi, released in beta, thank you!

Hi,
in order to maintain consistency with other countries behaviour, these codes have been chosen instead:
1, 2, 3, 4, 5, 6, 7, 8, 9 (default)


About contributing a NewRelic sink

Hello, I work a New Relic as part of the K8S monitoring team, we would like to contribute a sink that pushes data to our platform, this issue is just to start the conversation and let you know what we have in mind and see if our plans fit the project.
The sink will be pretty simple, it will use the newrelic sdk to push data to an infrastructure agent, meaning that we would have to import the sdk as a dependency.
We would like it to live under it's own directory under the sinks, the reason is that we want to have our own README.md (if we could link it to the root readme it would be awesome) with examples on how to set it up and an example manifest file for installing it.
For this to work with the infrastructure agent we will need a pod with both the router and the integration, that's why we want to add the example manifest I mentioned before and extend the helm chart to add this.
Cool project and let me know what you think. cheers.

@timothysc I assigned this to you to make sure it's on your radar. Haven't been following this project much so I'm not sure who the maintainer currently is but I know you can help out here.

I'm ok with it, but please for the love of all that is good in the universe please ensure you don't have massive import dependency sprawl.  Lately every time someone wants to create a new sink, which is really a small piece of code, I get huge import PRs.

thanks for the quick response @chuckha @timothysc and thanks for the green light, we are eager to contribute :)
@timothysc we'll try to keep it the imports low, I saw the Azure PR D:

Hey @timothysc  & @chuckha
As my colleague @alejandrodnm already mentioned, we would like to contribute to this project!
Before doing so we have some questions about whether our intended changes are OK with you / Heptio.
In short, we would like to make the following changes to the repo:

Instead of dep, use go modules, which has been accepted as the community standard
Use a multistage Dockerfile to build/test the project (build & test all in a single, easier-to-maintain place. Integrates well with skaffold.dev)
For security reasons, use up-to-date versions of:

Go: v1.9 -> v1.12.x
Alpine Linux: v3.6 -> v3.9.
Go dependencies, for example: k8s.io/client_go v5.0.0 -> v12.0.0

It will be quite a large PR, seeing most of the dependencies will be upgraded.
What do you think about these changes? Any concerns/blockers?
Thanks!

Hi, we have decided to go on a different route, either way, thank you very much for being open to our colaborations.
Cheers.


Implement DTLS support

I'm interested in using a Python CoAP client library for a project that requires security. I happened upon this library and was pleased to see recent activity. Is there a likely timeframe for implementing DTLS support?

Hi,
It is in our TODO list, and I hope we will provide DTLS support in few
months.
2015-04-23 19:57 GMT+02:00 Evan Meagher<EMAIL_ADDRESS>
Is there a likely timeframe for implementing DTLS support?
—
Reply to this email directly or view it on GitHub
https://github.com/Tanganelli/CoAPthon/issues/14.

When would provide DTLS support?

Is DTLS going to happen anytime soon?

Hi Giacomo, I'm also interested in DTLS support - would really appreciate an update on this

Hi @Tanganelli ,
Update on DTLS support would be much appreciated !
Thanks,
Venkat

Hi all,
I know that everybody would like DTLS. However it is a real long work in my opinion, thus I would really appreciate if someone could help me on this.

This Repository for DTLS seems promising if this needs to be done @Tanganelli

Hi,
I am trying to use this library. Does it support DTLS now ??

Now it should support DTLS, however I still have to evaluate it.

Could you please help to provide example script ? I am able to send coap from my Pi3 to node.js coap server via Python Shell. I used coapclient.py as I need client side only.

Maybe you should have a look at test_secure.py which is all about examples on using DTLS with CoAPthon, especially function test_ok_with_handshake_on_connect() and try modifying "your version" of coapclient.py to meet your needs. Basically it is only creating a DTLS socket and giving it to HelperClient() on creation.

Thank you for your response.
Is there any other method to install Dtls ? I am not able to install Dtls via "pip install Dtls" command.

Thank you for your response.
I am getting following error while trying to execute test_secure.py. I have already installed pip install Dtls though. Please help to resolve this.
Traceback (most recent call last):
File "test_secure.py", line 23, in
from dtls.wrapper import wrap_server, wrap_client
File "/usr/local/lib/python2.7/dist-packages/dtls/init.py", line 63, in
from patch import do_patch
File "/usr/local/lib/python2.7/dist-packages/dtls/patch.py", line 44, in
from sslconnection import SSLConnection, PROTOCOL_DTLS, PROTOCOL_DTLSv1, PROTOCOL_DTLSv1_2
File "/usr/local/lib/python2.7/dist-packages/dtls/sslconnection.py", line 60, in
from x509 import _X509, decode_cert
File "/usr/local/lib/python2.7/dist-packages/dtls/x509.py", line 34, in
from openssl import *
File "/usr/local/lib/python2.7/dist-packages/dtls/openssl.py", line 811, in
((c_char_p, "ret"), (c_int, "nid")), True, None),
File "/usr/local/lib/python2.7/dist-packages/dtls/openssl.py", line 642, in
map(lambda x: _make_function(*x), (
File "/usr/local/lib/python2.7/dist-packages/dtls/openssl.py", line 562, in _make_function
for i in args[1:]))
AttributeError: /usr/lib/arm-linux-gnueabihf/libssl.so.1.0.0: undefined symbol: DTLS_server_method

How to install Openssl1.0.2 version in Debian (Raspberry Pi3) OS ?
It just installs OpenSSL1.0.1 automatically. I require version later than this i.e. 1.0.2* which supports DTLS.
I installed openssl1.0.2g from some site but it does not link lib dynamically as I could not see 'libssl.1.0.0' when I run this command '$ ldd /usr/bin/openssl'

Hi, take a look to: https://raspberrypi.stackexchange.com/questions/66782/how-to-install-openssl-1-0-2-on-raspberry-pi3/67045


Fixes Get-TargetResource and Set-TargetResource function

The Get-TargetResource function would fail because Get-HotFix was receiving the Path parameter which it does not take.
Also, when $LASTEXITCODE was not set, it would cause the Set-TargetResource function to fail. Adding a check to make sure the variable exists before using it fixed this issue.

Hi @PrahlM93, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

LGTM.

Looks clear to me!
You should add the change to the Unreleased Version section in the Readme.md as well.

Thank you @tysonjhayes and @PlagueHO for taking a look. @PlagueHO I did implement your suggestions, please let me know what you think.

Cool! Looks great :+1:

Thanks @PrahlM93 for contribution!
Thanks @tysonjhayes and @PlagueHO for reviewing!


Re-assess local models and how they are called

Before going for Version 1.0, I think we should check if we are using the local models properly. Are there better models available? How can we call the model to be a chatbot instead of a mere text completion model?

The tokenizer object knows a function named apply_chat_template, which can be called with an array of messages exactly as the OpenAI api is called. However, many models do not seem to provide such a chat template. I have wrapped the call in a function that listens for a warning and prints it as an error message in Foundry. Without such a default template, the output is pretty useless.
The current issue is therefore to find models that provide such a template.
On another node: I would really like to test the local models on a regular basis, but because Jest is not made for ES modules, it cannot use the import statement and thus has no access to transformers.js. This makes maintaining the local models... challenging.

Update: I managed to enable testing ES modules with jest. :)
The changes will enter main with the next merge.

We are currently getting an error:
An error occurred during model execution: "TypeError: A float32 tensor's data must be type of function Float32Array() { [native code] }".
The callback is:
      at new h (node_modules/onnxruntime-common/dist/webpack:/onnxruntime-common/lib/tensor-impl.ts:111:17)
      at m.run (node_modules/onnxruntime-common/dist/webpack:/onnxruntime-common/lib/inference-session-impl.ts:112:28)
      at sessionRun (node_modules/@xenova/transformers/src/models.js:207:22)
      at Function.decoderForward [as _forward] (node_modules/@xenova/transformers/src/models.js:547:26)
      at Function.forward (node_modules/@xenova/transformers/src/models.js:820:16)
      at Function.decoderRunBeam [as _runBeam] (node_modules/@xenova/transformers/src/models.js:633:18)
      at Function.runBeam (node_modules/@xenova/transformers/src/models.js:1373:16)
      at Function.generate (node_modules/@xenova/transformers/src/models.js:1087:30)
      at getResponseFromLocalLLM (src/scripts/local-llm.js:74:18)
      at Object.<anonymous> (src/scripts/local-llm.test.js:20:26)

The output of tokenier() is an Array of Bigint64. I have tried not returning a tensor object (per options argument), and I have tried converting the tensor to float (no idea if what I tried was right), both to no avail.

I learned that this probably has to do with us transpiling the ECMA Script to CommonJS with Babel, because CommonJS does not support BigInt. But well, the tokenizer is giving us BigInts. This also explains why the behaviour seems to be restricted to the test environment and appeared only recently. Do I know how to fix this? Nope. Not yet.
Man, this programming language...

The BigInt64Array is a built in type:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt64Array
The previous values are added with a hard coded float32 type:
https://github.com/xenova/transformers.js/blob/main/src/models.js (Function addPastKeyValues, Line 1346)
The error message is thrown in the constructor of a new tensor:
https://github.com/microsoft/onnxruntime/blob/main/js/common/lib/tensor-impl.ts (Line 174)

The check
if (arg1 instanceof typedArrayConstructor)
in
https://github.com/microsoft/onnxruntime/blob/main/js/common/lib/tensor-impl.ts, Line 171
fails.
According to Copilot:
"""
Yes, it could be related to the transpilation process.
When you transpile ES modules to CommonJS using Babel, it can sometimes cause issues with instanceof checks. This is because Babel's transpilation process can create copies of constructors like Float32Array, which means the instanceof check may fail even if arg1 is what you would consider an instance of Float32Array.
In other words, arg1 might be an instance of a different Float32Array constructor than typedArrayConstructor, even though they are conceptually the same thing. This is a known issue when working with transpiled code and instanceof checks.
"""

I tried fixing it with a babel plugin:
https://github.com/TheComamba/UnKenny/commit/25f350eb2ca4eda719bc8f8bfb5a7a47e7b200a1
So far, no success, but maybe this is progress?

I tried converting the whole shebang to a CommonJS model.
https://github.com/TheComamba/UnKenny/tree/dev/treating-code-as-common-js
So far, I failed.
Importing transformers seems to be a really bad idea when using Jest.
Another hurdle is that requiring from an URL is not allowed. We can download the module and then require it locally. In theory. In practice I did not manage to do that, because this introduces an asynchronicity that I failed to resolve in my frustrated state of mind.

I think it might be time to consider moving to another test framework:
https://github.com/traceypooh/js-es-modules-coverage-testing

I started doing that:
https://github.com/TheComamba/UnKenny/tree/dev/mocha-for-tests


VeloxChem writer unconditionally enables Optimize General Contractions

If one emits, e.g., the cc-pVDZ basis set for oxygen for NWChem or PSI4, enabling or disabling the "Optimize General Contractions" option will cause 8 or 9 non-zero primitives to be produced for the first two S orbitals.
However, when requesting the VeloxChem format, the result expected for the Optimize General Contractions case is unconditionally emitted.
This is confusing and makes it hard to compare codes.  While very few properties will change based on this, performance is one of them, which matters to some people.
I'll also note that it is confusing that the default is to disable "Optimize General Contractions" when NWChem's internal default is to enable this.  This means that what one gets by default out the BSE does not agree with NWChem even when the bse basis set option is used.
The molecular properties that depend on this setting include Mulliken analysis shell coefficients and the basis function weights in the molecular orbitals, for anyone who is curious.  No observable depends on the linear dependency in the basis set, as expected.
 OXYGEN       (17s,4p,1d) -> [3s,2p,1d]
@ATOMBASIS O
S    8    1
1.172000E+04      7.100000E-04
1.759000E+03      5.470000E-03
4.008000E+02      2.783700E-02
1.137000E+02      1.048000E-01
3.703000E+01      2.830620E-01
1.327000E+01      4.487190E-01
5.025000E+00      2.709520E-01
1.013000E+00      1.545800E-02
S    8    1
1.172000E+04     -1.600000E-04
1.759000E+03     -1.263000E-03
4.008000E+02     -6.267000E-03
1.137000E+02     -2.571600E-02
3.703000E+01     -7.092400E-02
1.327000E+01     -1.654110E-01
5.025000E+00     -1.169550E-01
1.013000E+00      5.573680E-01
S    1    1
3.023000E-01      1.000000E+00
P    3    1
1.770000E+01      4.301800E-02
3.854000E+00      2.289130E-01
1.046000E+00      5.087280E-01
P    1    1
2.753000E-01      1.000000E+00
D    1    1
1.185000E+00      1.0000000
@END
aa00b0494c3d1bfeed7c8556745fc324

Here are some NWChem output files in case somebody wants to see the differences.
cc-pvdz is the NWChem internal basis set.  cc-pvdz8 is the optimized general contraction basis set from BSE.  cc-pvdz9 is the unoptimized general contraction basis set from BSE.
The MO coefficients differ by more than I would have expected, even though the energies are identical.
w10_scf_cc-pvdz_property.log
w10_scf_cc-pvdz9_property.log
w10_scf_cc-pvdz8_property.log

It does seem to be forced to optimize general in the original PR: https://github.com/MolSSI-BSE/basis_set_exchange/blob/eacdd02daad32d05d794e1053b75f803849dc3f7/basis_set_exchange/writers/veloxchem.py#L45. Maybe @robertodr can comment? Straightforward to fix if needed.
About the NWChem library - I didn't realize it was being incorporated in the NWChem software directly. There is a function to create archives for a particular output format (which I assume NWChem might be using), but right now that doesn't take any options for optimizing contractions or anything. This could be easily added if that would be useful.

Nothing is needed for NWChem now. I didn't realize that the GC optimization existed or that NWChem applied it internally automatically until now.


NO-TICKET: Memory usage of BlockValidator

I've added data_size(skip) annotation on Loading variant of the enum, mostly because we shouldn't be in the Loading state for long enough for this metric to be necessary but also because it is a pain to write an implementation of DataSize  for the Event enum.

@Fraser999 @marc-casperlabs I am having troubles with cargo-audit steps in this PR: https://drone-auto.casperlabs.io/CasperLabs/casper-node/3992/1/5 . Can you help me?

@Fraser999 @marc-casperlabs I am having troubles with cargo-audit steps in this PR: https://drone-auto.casperlabs.io/CasperLabs/casper-node/3992/1/5 . Can you help me?

It looks like our dependency on raw-cpuid v8.1.2 via quanta in casper-node is to blame here.  There's a dependabot PR to quanta which updates its dependency and would probably fix this, but that PR is failing CI currently.
Until that PR is merged, we might be best to change the audit step in .drone.yml to
cargo audit --ignore RUSTSEC-2021-0013

although we need to remember to re-enable it as soon as we can.

It looks like our dependency on raw-cpuid v8.1.2 via quanta in casper-node is to blame here.  There's a dependabot PR to quanta which updates its dependency and would probably fix this, but that PR is failing CI currently.
Until that PR is merged, we might be best to change the audit step in .drone.yml to
cargo audit --ignore RUSTSEC-2021-0013

although we need to remember to re-enable it as soon as we can.

Thanks @Fraser999 for taking care of it :)
I will update the drone's instruction and create a follow-up ticket.

Thanks @Fraser999 for taking care of it :)
I will update the drone's instruction and create a follow-up ticket.

JIRA ticket https://casperlabs.atlassian.net/browse/NDRS-788

JIRA ticket https://casperlabs.atlassian.net/browse/NDRS-788

bors merge

bors merge


panda install treats already install as an errror should be a NOP

yeah if that package is already installed panda try's to install again and errors out should either do nothing or increase a dependency/reference count

To add, it not only should be a NOP, but perhaps report the version of the already installed module.
Here's Perl 5's cpanm utility's output:
$ cpanm JSON::Tiny
JSON::Tiny is up to date. (0.54)

And here's Perl 6's panda untility's output; note the extra building and testing stages:
$ panda install JSON::Tiny
==> Fetching JSON::Tiny
==> Building JSON::Tiny
==> Testing JSON::Tiny
t/01-parse.t ...... ok
t/02-structure.t .. ok
t/03-unicode.t .... ok
t/04-roundtrip.t .. ok
t/05-utf16.t ...... ok
All tests successful.
Files=5, Tests=122, 15 wallclock secs ( 0.06 usr  0.02 sys + 13.96 cusr  0.90 csys = 14.94 CPU)
Result: PASS
==> Installing JSON::Tiny
JSON::Tiny:ver<*>:auth<>:api<> already installed
  in block  at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/sources/81B39D32B12A43DA4DAA3C4A5AB514A854517A42 line 61
  in sub indir at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/sources/05F03CBBA9F3F9247B5B7D7FBEDEB6C4254D5938 line 20
  in method install at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/sources/81B39D32B12A43DA4DAA3C4A5AB514A854517A42 line 42
  in method install at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/sources/E82876E0365875EBADD64226FEC47E9CDAF9143B line 146
  in method resolve at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/sources/E82876E0365875EBADD64226FEC47E9CDAF9143B line 219
  in sub MAIN at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/resources/150CB7AB28B8F0DC3E8B153CB0AF6AD5B165A694 line 18
  in block <unit> at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/resources/150CB7AB28B8F0DC3E8B153CB0AF6AD5B165A694 line 150

Actually thrown at:
  in method install at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/sources/81B39D32B12A43DA4DAA3C4A5AB514A854517A42 line 44
  in method install at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/sources/E82876E0365875EBADD64226FEC47E9CDAF9143B line 146
  in method resolve at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/sources/E82876E0365875EBADD64226FEC47E9CDAF9143B line 219
  in sub MAIN at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/resources/150CB7AB28B8F0DC3E8B153CB0AF6AD5B165A694 line 18
  in block <unit> at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/resources/150CB7AB28B8F0DC3E8B153CB0AF6AD5B165A694 line 150

This will be much more problematic on projects with a lot of dependancies, as there will be a large amount of time spent building and testing deps just to bail out from their install.


Go ahead..

This can be done in literally two lines of code:
import socket
ip = socket.gethostbyname('example.com')

Other scripts seem a little bit more complex for me, therefore, they might be more useful,
Don't want to be toxic in any sense, but I think that if the solution can be googled within a few seconds then there's no need to include it in the repo.

This can be done in literally two lines of code:
import socket
ip = socket.gethostbyname('example.com')

Other scripts seem a little bit more complex for me, therefore, they might be more useful,
Don't want to be toxic in any sense, but I think that if the solution can be googled within a few seconds then there's no need to include it in the repo.


Fix solr config folder permissions and Supervisord restart on Wheezy

We had issues with those two things while setting up a new Zebra box.
This PR is a : Bugfix

[x] Changelog was updated

Thanks! :muscle:


AttributeError: 'SafetyWalker2dVelocityEnv' object has no attribute 'get_dataset'

I replaced environment 'OfflineCarCircle-v0' with environment 'SafetyWalker2dVelocity-v1' in dsrl/test.py,
import gymnasium as gym
import dsrl
# set seed
seed = 0
# Create the environment
env = gym.make('SafetyWalker2dVelocity-v1')
# dsrl abides by the OpenAI gym interface
# obs, info = env.reset(seed=seed)
# obs, reward, terminal, timeout, info = env.step(env.action_space.sample())
# cost = info["cost"]
# Each task is associated with a dataset
# dataset contains observations, next_observatiosn, actions, rewards, costs, terminals, timeouts
dataset = env.get_dataset()
print(dataset['observations'])  # An N x obs_dim Numpy array of observations
and the code error is as follows:

Hi @XiaohanYang2333 , can you try to add Offline before the environment name? Like: OfflineSafetyWalker2dVelocity-v1?

I changed it as what you said,and it worked.Thanks a lot.


Mobile Menu doesn't open under iOS

Hi,
the mobile menu isn't working under iOS 16.6.1 on iPhone 12 Pro.

Updating to iOS 17 hasn't solved the issue

similar issue for safari on Mac. The menu is closing without a new page opening


NAS-126861 / 24.04-RC.1 / Fix share ACL output in debug (by anodos325)

Original PR: https://github.com/truenas/ixdiagnose/pull/150
Jira URL: https://ixsystems.atlassian.net/browse/NAS-126861

This PR has been merged and conversations have been locked.
If you would like to discuss more about this issue please use our forums or raise a Jira ticket.


[Bug]: Date formatting ignored

Description of the Bug
While modifying the TIME_ZONE and all date formatting to the configuration.py, the date format and orientation are not applied and stay in original UTC/US way.
# Time zone (default: UTC)
TIME_ZONE = 'CET'

# Date/time formatting. See the following link for supported formats:
# https://docs.djangoproject.com/en/stable/ref/templates/builtins/#date
DATE_FORMAT = 'j N Y'
SHORT_DATE_FORMAT = 'd-m-Y'
TIME_FORMAT = 'G:i a'
SHORT_TIME_FORMAT = 'H:i:s'
DATETIME_FORMAT = 'j N Y, G:i'
SHORT_DATETIME_FORMAT = 'd-m-Y H:i'

I've check the docs of django for cheking what should I put over there :/
Expected behavior
It should be this

But it stayed like this

Reproduction

Edit /opt/status-page/statuspage/statuspage/configuration.py
Reload services
Check on web page

Version

2.0.0 (Preview)

Information about your Device
Desktop (please complete the following information):

OS: Debian 11.7
Browser : Firefox
Version 116.0.2

Smartphone (please complete the following information):

Device: othing Phone (1)
OS: Android 13
Browser Brave
Version 1.56.20

Relevant log output
Not sure if this related

Aug 11 12:31:05 ninja-status-vincent-d01 python3[3114]: 12:31:05 Registering birth
Aug 11 12:31:05 ninja-status-vincent-d01 python3[3114]: /opt/status-page/venv/lib/python3.10/site-packages/rq_scheduler/utils.py:28: FutureWarning: Version 0.22.0+ of crontab will use datetime.utcnow() and
Aug 11 12:31:05 ninja-status-vincent-d01 python3[3114]: datetime.utcfromtimestamp() instead of datetime.now() and
Aug 11 12:31:05 ninja-status-vincent-d01 python3[3114]: datetime.fromtimestamp() as was previous. This had been a bug, which will be
Aug 11 12:31:05 ninja-status-vincent-d01 python3[3114]: remedied. If you would like to keep the *old* behavior:
Aug 11 12:31:05 ninja-status-vincent-d01 python3[3114]: `ct.next(..., default_utc=False)` . If you want to use the new behavior *now*:
Aug 11 12:31:05 ninja-status-vincent-d01 python3[3114]: `ct.next(..., default_utc=True)`. If you pass a datetime object with a tzinfo
Aug 11 12:31:05 ninja-status-vincent-d01 python3[3114]: attribute that is not None, timezones will *just work* to the best of their
Aug 11 12:31:05 ninja-status-vincent-d01 python3[3114]: ability. There are tests...
Aug 11 12:31:05 ninja-status-vincent-d01 python3[3114]:   next_time = cron.next(now=now, return_datetime=True)

(this has already corrected on my side)

Hey @Emma0Z,
sorry for the late reply. I was kinda busy and then just forgot about the Incidents in this Project :D
It seems like this behaviour is working as designed by django and therefore shows dates as usual for you locale: https://docs.djangoproject.com/en/4.2/ref/settings/#use-l10n
As stated there, starting with Django 5, this setting wont be available anymore.


Temporariliy set dev DB to the duplicate of production

@ryscher do we still want to merge this?

Only if you need it for testing


The fps window is not closed when navigating away from angry pods

I clicked angry pods, and then clicked on another button, but the fps window in the bottom left corner keeps open.

fixed now


Remove Saucelabs from Travis CI

No UX changes in this one.  Just housekeeping our build process

@chriskacerguis I think Github is having issues.  It's not reporting back status on this PR

@chalettu yeah ditto on other outstanding prs

Yeah, Travis UI should it is done...it didn't report status.
https://travis-ci.org/ManageIQ/manageiq-ui-service/builds/252909733


exclude option for kpt fn eval and kpt fn render

First commit: add exclude functionality as described in https://github.com/GoogleContainerTools/kpt/issues/2930
Second commit: add label and annotation selection to selectors/exclusions
Third commit: e2e tests

@droot @yuwenma this PR is ready for review


How to hide references, generated by re-exports

As I'm using the typedoc-plugin-external-module-name, I don't need the "references" features, who are generated by re-exports. However, I can't find any option to exclude or hide the section. If there's an option for that, can you teach me how to use it? Otherwise, I want to request that feature.

There is no way to exclude these currently, though you could write a plugin to do this fairly easily.
I don't really want to include a toggle for this, I expect with the upcoming library mode that these will drop to very few in each project and those that remain will be important.
Simple plugin to remove references (untested)
import { Application, Converter } from 'typedoc'
export function load({ application }: { application: Application }) {
  application.converter.on(Converter.EVENT_RESOLVE_BEGIN, context => {
    for (const reflection of context.project.getReflectionsByKind(ReflectionKind.Reference)) {
      context.project.removeReflection(reflection)
    }
  })
}

@Gerrit0 Thanks for reply. Your example code is working well.

The code above is not working in<EMAIL_ADDRESS> I've written a package to fix it: https://www.npmjs.com/package/typedoc-plugin-remove-references


Implement powered minecart // minecart furnace

Description
We all love this entity, that's why I implemented it. As it's definitely one of the most used entities, I have implemented it (this is called irony). Generally furnace minecarts could be considered as the most buggy entity interface in the paper api (If someone is interested, I can show you how bad it is).
Also added some methods that gave compilation errors in PlayerMock
Checklist
The following items should be checked before the pull request can be merged.

[x] Unit tests added.
[x] Code follows existing code format.

Info on creating a pull request

Make sure that unit tests are added which test the relevant changes.
Make sure that the changes follow the existing code format.

For maintainer
When a PR is approved, the maintainer should label this PR with release/*.

If the PR fixes a bug in MockBukkit, add the release/patch Tag.
If the PR adds a new feature to MockBukkit, add  the release/minor Tag.

Note that a PR that fixes an UnimplementedOperationException should be considered a new version and not a bugfix.

If you go to the files changed view, you can select multiple suggestions to apply with one commit


Machines are not reachable after vagrant reload

Machines are not reachable from host machine after destroy / reload / etc'
Network and host machines are reachable from all guests but blocked from outside.

I had the same problem - resolved this by connecting to each vm via ssh and run:
node-start
there. After about a minute or two they became available again.


repo page 500 because of markdown render error

Gitea version (or commit ref):
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:
fatal from goldmark: interface conversion: interface {} is string, not []uint8

Description
i reproduce it on try.gitea.io: Link
but the README.md is rendering just fine on goldmark demo page
...
Screenshots

For anyone who looks in to this, you can get the README contents here

Damn this is something to do with the checkbox change I made...
## TODO List

- [x] Embed the http proxy server [privoxy](http://www.privoxy.org/), [get it](https://homebrew.bintray.com/bottles/privoxy-3.0.26.sierra.bottle.tar.gz).

- [x] ACL mode support [Shadowsocks ACL](https://github.com/shadowsocksr/shadowsocksr-libev/tree/master/acl)

Appears to be the bit that kills things

FFS! I did actually test that change but then noticed the SetAttributeString and must not have properly tested again!


jeiwan.cc is now jeiwan.net so urls fixed

Description

The urls to the go tutorials "Building Blockchain in Go" were poiting to jeiwan.cc which is now jeiwan.net so fixed all urls related to this.
Motivation and Context

Making sure the go blockchain tutorials link don't error out and point to right articles for the people looking for it.
How Has This Been Tested?

fixed it in a fork and tried the links to it now they are workingfine.
Types of changes

[ ] Content Update (change which fixes an issue or updates an already existing submission)
Link to article changed to the new url.
[ ] New Article (change which adds functionality)
[ ] Documentation change

Checklist:

[ ] My code follows the code style of this project.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have made checks to ensure URLs and other resources are valid

Correct, new links seem fine.


Broken link causes 404 error

Type of issue
Typo
Description
Broken link in section Currently supported environments for LTS versions of Node.js causes a 404 error that Page could not be found.
Link on the Node.js website for Node.js Releases is https://nodejs.org/en/about/previous-releases and noticed without the en this link will 404.
Page URL
https://learn.microsoft.com/en-us/javascript/api/overview/azure/arm-policyinsights-readme?view=azure-node-latest
Content source URL
https://github.com/MicrosoftDocs/azure-docs-sdk-node/blob/main/docs-ref-services/latest/arm-policyinsights-readme.md
Document Version Independent Id
72d4a6fe-0e26-3f2d-bdc3-6d0fa204be4d
Article author
@azure-sdk
Metadata

ID: 17e74639-d766-2dc7-f108-1df15c6315f4
Service: azure-policy

This is probably because the readme is from a version of package that was published long time ago.  Now we linked to https://github.com/nodejs/release#release-schedule
Is it possible to fix the doc site after it is published?

@jeremymeng I'm not the content owner, but I created this issue because the broken link was included in a report. It's published content that customers use, so my opinion is the content owner should fix the broken link.

so my opinion is the content owner should fix the broken link.

@davidsmatlak Yeah definitely! Thanks for reporting! My question was for docs owner.

this broken link should be fixed in https://github.com/Azure/azure-sdk-for-js/commit/f280f87f7b06f59fef449b41a2742cc381b9ac37 2 years ago, and we have never released this rp with a stable version.


Generate scratch org password with cci, not sfdx

In order to easily generate a password for a scratch org, a user can simply run a cci org command. (Currently, we must run sfdx force:user:password:generate -u ORGNAME.)

Closing this since we made the automatic generation of a password for new scratch orgs more reliable a long time ago. But willling to reconsider if there's still a need.


License

I noticed this project has no License for the code. Can you consider adding one?

Ah... you're right, I totally forgot about it!

Ah... you're right, I totally forgot about it!

Added in https://github.com/datejer/vercel-badge/pull/2 👍

Added in https://github.com/datejer/vercel-badge/pull/2 👍

Thanks so much!
I ended up using a lot of this in https://github.com/Cobertos/fitbit-sleebies . This is such a nice repository for making 1 off badges :3

Thanks so much!
I ended up using a lot of this in https://github.com/Cobertos/fitbit-sleebies . This is such a nice repository for making 1 off badges :3


Make target to test multiple spark + python version combinations

.spark_python_to_test:
3.2.1, 3.7
2.4.8, 2.7

make test should pick up those 2 lines and run test twice on each of the combinations.

Split above to two files: spark_3.2.1_python_3.7.totest
Define rules from *.totest to *.tested


dispatch-cli: Unable to install/use dotnet framework

Tool
Name: Dispatch
Version: 1.5.8
OS: Windows 10 Enterprise (10.0.18362 Build 18362)
Installed .NET Core SDKs: 2.1.505, 2.1.508, 2.1.802
Describe the bug
When running any dispatch command (e.g. dispatch refresh, dispatch add or dispatch --help) the tool outputs: Unable to install/use dotnet framework.
The only command that works is dispatch --version which returns 1.5.8 in my case.
I already tried installing the latest .NET Core 2.1 SDK via dotnet.microsoft.com/downloads/dotnet-core/2.1 and then reinstall botdispatch using npm i -g botdispatch but that didn't help. I also read through issue #807 and tried most of the things suggested over there.
To Reproduce
Steps to reproduce the behavior:

Run npm i -g botdispatch
Try to run dispatch init

Expected behavior
I expect the tool to work, or have more information about how to solve this issue.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
[bug]

Update
This might be an issue with the dotnet-2.1 npm package because I ran into a related error when trying to do a fresh install of botdispatch and .NET Core.
 There is likely additional logging output above.
123 verbose exit [ 1, true ]

Unfortuntely, I am not able to reproduce.
@tsuwandy Any thoughts?

@EdwinOtten, there was an issue with the install script for dotnet-2.1 package with node version 12 and latest package has been republished to npm.  Which version of nodejs do you have?
In any case, try the following after unintalling botdispatch:
If you are using a machine you have already installed .net npm packages previously, from powershell run :
clean the package cache
npm cache clean --force
remove any installed .net runtimes
erase -recurse "$home/.net"
Then try the install again.  Let me know if you are still having install issues.  Thanks!

@tsuwandy I'm running node 12.13.0 (latest LTS version). I tried uninstalling and running the commanda you mentioned in powershell (version 6, in admin mode)
npm uninstall -g botdispatch
npm cache clean --force
erase -recurse "$home/.net"
npm i -g botdispatch

It still throws the ELIFECYCLE error: Failed at the<EMAIL_ADDRESS>postinstall script
I could try downgrading to a LTS version of node 10, may that make a difference?

@EdwinOtten, please try node 10.  I’ll try to get a repro with node 12 and will inform dotnet team of the errors again.  Thanks!

@tsuwandy I uninstalled node, rebooted my pc. Then I installed node 10 and downgraded npm to the corresponding version. After this I tried to install botdispatch, but still the same error 😞
PS C:\Users\Eotten> node -v
v10.17.0
PS C:\Users\Eotten> npm -v
6.11.3
PS C:\Users\Eotten> npm uninstall -g botdispatch
up to date in 0.026s
PS C:\Users\Eotten> npm cache clean --force
npm WARN using --force I sure hope you know what you are doing.
PS C:\Users\Eotten> erase -recurse "$home/.net"
PS C:\Users\Eotten> npm i -g botdispatch
C:\Users\Eotten\AppData\Roaming\npm\dispatch -> C:\Users\Eotten\AppData\Roaming\npm\node_modules\botdispatch\bin\dispatch.js

><EMAIL_ADDRESS>postinstall C:\Users\Eotten\AppData\Roaming\npm\node_modules\botdispatch\node_modules\dotnet-2.1
> node -e "/*PostInstall: Installs platform-specific .NET framework */try{require('./dist/app.js')}catch(e){}"

Unable to install/use dotnet framework.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: `node -e "/*PostInstall: Installs platform-specific .NET framework */try{require('./dist/app.js')}catch(e){}"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!       Extracting by manifest.
57 silly tarball no local data for botdispatch@latest.  There is likely additional logging output above.
127 verbose exit [ 1, true ]

I could use some help...

public class Order
{
    public int OrderId { get; set; }
    public int CustomerId { get; set; }

    public List<int> Products { get; set; }
}

Oops, accidentally closed the issue but I didn't mean to..

@fearthecowboy, any ideas?  I tried installing on node 12 and worked fine for me.  @EdwinOtten copied the entries from the log above.  Thanks!

This is a different issue -- I think it's failing for some other reason.
let's try just the .net framework package:
In an powershell prompt:

# clean out anything that might be there
rmdir -recurse $home/.net

$env:debug=1
$env:NO_NET_SDK=1

npm cache clear --force
npm install -g dotnet-2.1

and it should dump out a bunch of debugging data.

Thanks! I solved the issue 😄
By setting $env:debug=1 and $env:debug=1 I've got some more info on the issue:
Creating base path: C:\Users\Eotten\.net\2.1
{"type":"info","data":"No lockfile found."}
{"type":"step","data":{"message":"Resolving packages","current":1,"total":4}}
{"type":"activityStart","data":{"id":0}}
{"type":"activityTick","data":{"id":0,"name":"dotnet-2.1-win-x64"}}
{"type":"error","data":"An unexpected error occurred: \"https://registry.npmjs.org/dotnet-2.1-win-x64: unable to get local issuer certificate\"."}
{"type":"info","data":"If you think this is a bug, please open a bug report with the information provided in \"C:\\\\Users\\\\Eotten\\\\.net\\\\2.1\\\\yarn-error.log\"."}
{"type":"info","data":"Visit \u001b[1mhttps://yarnpkg.com/en/docs/cli/add\u001b[22m for documentation about this command."}
Unable to install/use dotnet framework.

Based on the error above I discovered that dotnet-2.1 uses yarn to install some other packages, which runs into issues with our corporate firewall/proxy setup.
I've had the unable to get local issuer certificate error before, when using NPM. I already had a .npmrc file (inside %userprofile%) to make NPM work with our proxy. So after finding out about the use of yarn, I also added a .yarnrc file with strict-ssl false.
@fearthecowboy It might be a good idea to mention the use of yarn in the readme of dotnet, for those of us struggling with corporate proxies...   What's your opinion on this?

Ah.  Good to know.
Yeah, I can add that to the readme.
FWIW, I had to use Yarn -- using NPM programatically is fraught with pain and suffering.

@EdwinOtten, @fearthecowboy, thank you!!  @EdwinOtten, closing this issue. 👍

FWIW, I had to use Yarn -- using NPM programatically is fraught with pain and suffering.

It's not that I'm against using Yarn. I just didn't look for a solution in that direction.. until I noticed  yarn in the debug logs :wink:
Thanks to both of you for spending time on this and helping me out! :+1:  :tada:

Sorry, but I still do not understand how to solve this. I have the same issue. In my case, the botdispatch does not install at all

@edwardtsbaum, could you try this from @EdwinOtten comment above?
“I've had the unable to get local issuer certificate error before, when using NPM. I already had a .npmrc file to make NPM work with our proxy. So after finding out about the use of yarn, I also added a .yarnrc file with strict-ssl false. This solved the issue for me.”

I saw that comment, but I do not understand how to add a .yarnrc file to NPM.

@EdwinOtten, could you help @edwardtsbaum? Where should .yarnrc be created and what should be in there?  Thank you!

I added a .yarnrc file and it still does not work. It installs globally but it does not allow me to use any dispatch commands except for dispatch --version. it fails to install locally because it is unable to install/use dotnet framework. here is another screenshot of what it looks like

this is what it looks like when i try to install botdispatch using the yarn

i need some help, If anyone is out there.
I feel like I have done everything. I have uninstalled and installed .net runtimes and sdks, I am all out of tricks if there is anyone that can help me that would be greatly appreciated.

@edwardtsbaum, what's in your .yarnrc and where you put it?   @fearthecowboy, any ideas?

I haven't gotten back to this quite yet, but maybe we can do a quick workaround:
# turn on debug mode so we get more messages.
set debug=1

# let's install yarn so we can easily configure it.
npm install -g yarn

# set strict-ssl to false
yarn config set strict-ssl false

# try to install the dotnet package
npm install -g dotnet-2.1

Thanks guys for the help. I could not figure out what my problem was but I
figured there was a dependency issue with the dot net cli I had installed.
I backed up my system and cleaned my drives and reinstalled dot net and
node.js and reinstalled botdispatch and finally got it working.
On Mon, Jan 6, 2020, 5:47 PM Garrett Serack<EMAIL_ADDRESS>wrote:

I haven't gotten back to this quite yet, but maybe we can do a quick
workaround:
turn on debug mode so we get more messages.
set debug=1
let's install yarn so we can easily configure it.
npm install -g yarn
set strict-ssl to false
yarn config set strict-ssl false
try to install the dotnet package
npm install -g dotnet-2.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/botbuilder-tools/issues/1352?email_source=notifications&email_token=AKUN2SVOSV76E47EF5I5J53Q4OYJZA5CNFSM4JITMMJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIHBWNQ#issuecomment-571349814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKUN2SVGOMMTC2XX25IP423Q4OYJZANCNFSM4JITMMJQ
.

@fearthecowboy, thanks for the instructions!  @edwardtsbaum, glad to hear you got it working.  Thanks!

Hello - I am still getting this issue.
I am on mac, with npm 6.14.4 and dotnet 3.1.300.
Should I remove dotnet sdk 3.1.3 and install 2.1?
thanks!

@srajanpm, try removing dotnet 3.1.3.  Dispatch CLI is using dotnet 2.1.
Try turning on debugging to get more messages in the log (see above thread):
turn on debug mode so we get more messages.
set debug=1
let's install yarn so we can easily configure it.
npm install -g yarn
set strict-ssl to false
yarn config set strict-ssl false
try to install the dotnet package
npm install -g dotnet-2.1

thanks @tsuwandy
I uninstalled dotnet 3.1.3 and followed your steps above to install dotnet 2.1 and dotnet 2.1 install failed in the postinstall script.
 There is likely additional logging output above.
95 verbose exit [ 1, true ]


CI build

This PR:

Creates a CI for the repository in order to run “npm run build” in both folders packages/registry and packages/eligibility
Some slight modification on moveFile.bash which attempted to fix font symlinks was commented out.
A bit more testing has to be done to make sure that the build is successful.

@lacabra an example of a successful GitHub action run of this can be found here in my personal clone of the repo

@nathanfletcher: please note my fix in 6f4f3cd instead of b6870d9 ;)


fix: do not show spinner if data is already there

Details
Reverts https://github.com/Expensify/App/pull/44819
I tested on fresh main branch and without changes from https://github.com/Expensify/App/pull/44819 I can not reproduce https://github.com/Expensify/App/issues/44625 (so it makes me thinking that these changes are not relevant at the moment).
But without changes from https://github.com/Expensify/App/pull/44819 the issue from https://github.com/Expensify/App/issues/49964 is not reproducible.
So I think it's safe to revert https://github.com/Expensify/App/pull/44819
Fixed Issues

$ https://github.com/Expensify/App/issues/49964
PROPOSAL: N/A
Tests

open an expensify website as User A
open a conversation with User B (and scroll to top to cache messages)
close the tab
send a message from User B to User A
open an expensify website as User A
be sure that you don't see skeleton loader (because we have a data in cache and we can show it from the cache)
be sure that https://github.com/Expensify/App/pull/44819 is not reproducible as well;

Offline tests

N/A
QA Steps

open an expensify website as User A
open a conversation with User B (and scroll to top to cache messages)
close the tab
send a message from User B to User A
open an expensify website as User A
be sure that you don't see skeleton loader (because we have a data in cache and we can show it from the cache)
be sure that https://github.com/Expensify/App/pull/44819 is not reproducible as well;

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/a2cf8ee4-8d92-4009-a225-0f77dda271c3

MacOS: Desktop

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

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

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

Just merged too fast. Nothing was not passing

Still able to see skeleton
https://github.com/user-attachments/assets/292accce-6cd2-49d5-a3d0-bb53b053f7d8

@mvtglobally sorry, but at which time code do you see a skeleton? I believe I watched entire video from beginning till the end on 0.5x several times, but I don't see a skeleton 🙈

Was this deployed to hybridapp? I'm not seeing it on web anymore but I am seeing it on iOS


Blackbox tests for the Auctioneer

[ ] link to data flows described in the master doc

Add the following black box tests to the auctioneer:

[ ] Happy path
[ ] Optimistic reorg caused by multiple rounds of voting on proposals in CometBFT

Since the Auctioneer design introduces gRPC streams to the codebase, we will need additional test helpers and mocks the test against these:

[ ] https://github.com/astriaorg/astria/issues/1540

┆Issue Number: ENG-830

This issue is stale because it has been open 45 days with no activity. Remove stale label or this issue
be closed in 7 days.


'Beautify Xaml' option is not visible in VS 2015 Enterprise

I have installed Xaml Styler into VS 2015 Enterprise (version 14.0.23107.0 D14REL) and cannot find 'Beautify Xaml' option in Context Menu.
I have tried in Xaml Designer view (with split Xaml/Designer), and in XML View (open with XML (Text) Editor). In both of them, 'Beautify Xaml' is not visible.
Is there a way to fix it? Maybe is there a keyboard shortcut to beautify (I do not want to enable Beutify on Save)

Seems like uninstalling and installing again fixed the problem


Fribourg ... deaths instead of cases

Canton FR seems to have reported the wrong death-totals yesterday.

Thanks, we're checking with FR.

FR seems to have corrected the mix-up in the meantime. Can you confirm @rsalzer ?

Thank you!


Add Hackathon Download Innovation 2018

Add Hackathon Download Innovation 2018
clean 2017 hackaton

Hi @AmberBee, thanks for your PR.
Unfortunately we cannot accept it as it is, as it deletes all of the 2017 hackathons and this is something we do not want. (We are actively evaluating new options to give more visibility to newer hackathons, please feel free to make any suggestion as long as it doesn't involve deletion of data.)
Moreover, as stated in CONTRIBUTING.md, new hackathons need to be added using their start date to determine the suitable position in the list. This criterion is currently not satisfied.
We will be more than happy to merge your contribution as soon as it is compliant with the guidelines.
Thank you very much.

Nothing changed in almost a month, closing as inactive. Feel free to open a new one.