Integrate language translation data to our platform

Use react-i18n to integrate translated data from Lokalise to our platform!

For integrating translated data from Lokalise to our platform, we need to finish the following stuff:

[ ] Install the package react-i18n and its associated packages
[ ] Initialise react-i18n and add translate function to every displayed word
[ ] Find all missing words that don't have in Lokalise data and add them to Lokalise
[ ] Design and create the button for switching the language

Hey @CeesWang, do you remember the context around this bit of code? https://github.com/FightPandemics/FightPandemics/blob/bd6529ef50e1825f35f95996b214ce82b6b6a4e1/client/src/components/Feed/FilterBox.js#L30-L36
Just want to confirm that it's safe to remove this fromWhom to providers conversion.

Changes have been made and I'm not 100% if it's safe to be removed. Might
have to look where the method is potentially being called.
On Fri, Aug 7, 2020, 10:35 PM John<EMAIL_ADDRESS>wrote:

Hey @CeesWang https://github.com/CeesWang, do you remember the context
around this bit of code?
https://github.com/FightPandemics/FightPandemics/blob/bd6529ef50e1825f35f95996b214ce82b6b6a4e1/client/src/components/Feed/FilterBox.js#L30-L36
Just want to confirm that it's safe to remove this fromWhom to providers
conversion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FightPandemics/FightPandemics/issues/1286#issuecomment-670811409,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIAFWLUJHTSQZMMTVMUBX73R7S2Y5ANCNFSM4PLCXDLQ
.


Visualize predicted Scan-paths on input image

Hi,
I'm new to both python as well as deep learning environment. I successfully implemented the code by giving an image as an input and saving the predicted scan-path output as a .mat file. Can someone kindly help me with how to visualize the scan-path over the input image?
Thanks a lot :D

SalGAN does not generate scanpaths, but saliency maps. In case you would like scanpaths, you may be interested in our other work SaltiNet.


Change value of several fields based on a field name pattern

In the words of the community user that initially requested the functionality:

Do you think it could be possible to develop an enhanced  put operator to change the value of several columns based on a column name pattern ? Something along the line of put pattern expr which would set the value of all fields which name matches pattern to expr ? Of course we would need to define a token to define the source field in expr.

This particular user also confirmed that want to be able to target any fields in the hierarchy which match the pattern, e.g., given this input:
{
  "foo": "bar",
  "fun": "times",
  "inner": {
    "foo": "hello"
  }
}

A pattern of f* would therefore target all of foo, fun, and inner.foo.
We discussed this as a team and reached consensus that the building blocks exist that would allow this to be implemented without much difficulty. The harder part would be making it a seamless part of the language. An incomplete list of possible approaches considered:

Adding functionality to the put operator as proposed above
Creating a new operator
Mix/extend some smaller building blocks, e.g., using something like over to iterate through the fields, then do the pattern matching & assignment using existing conditional logic, put, etc.

Incidentally, the requesting user also uses zync for database transformations, so they offered a specific example use case:
put *date* time($token*1ms)`

i.e., converting a database datetime column in ms increment.

We've been pursuing the third approach ("building blocks") in the list above. We've got something that seems to be functional. Here's a working example with Zed commit f75be28 that changes all fields that match pattern f*.
$ cat records.json
{
  "foo": "bar",
  "WontChange": "untouched one",
  "fun": "times",
  "inner": {
    "notfoo": "untouched two",
    "foo": "hello",
    "LeaveAlone": "untouched three"
  }
}
{
  "first": "one",
  "second": "two",
  "obj": {
    "a": "b",
    "f": "g",
    "m": "n"
  }
}

$ zq -version
Version: v1.2.0-30-gf75be28d

$ zq -Z 'over flatten(this) => ( value:=grep(f*) ? "changed":value | collect(this) | unflatten(collect) )' records.json
{
    foo: "changed",
    WontChange: "untouched one",
    fun: "changed",
    inner: {
        notfoo: "untouched two",
        foo: "changed",
        LeaveAlone: "untouched three"
    }
}
{
    first: "changed",
    second: "two",
    obj: {
        a: "b",
        f: "changed",
        m: "n"
    }
}

Unfortunately when the community user went to apply this to their real data, it failed. This led to the discovery of new bug #4058. Once we have a fix or workaround for that we'll revisit.

The bug #4058 has been addressed and the community user is now satisfied with the approach shown above that combines flatten(), collect() and unflatten() to iterate recursively through the key/value pairs in their objects. Therefore we'll move this issue to the back burner to possibly revisit later if we see the need for shorthand that could achieve the same via simpler syntax. Note that the planned into operator (#4066) will be a building block that may assist here.

Update: The changes in #4420 make it such that unflatten() part of the Zed shown above needs to be adjusted to:
$ zq -version
Version: v1.8.1-55-ged3b0865

$ zq -Z 'over flatten(this) => ( value:=grep(f*) ? "changed":value | collect(this) | unflatten(this))' records.json
{
    foo: "changed",
    WontChange: "untouched one",
    fun: "changed",
    inner: {
        notfoo: "untouched two",
        foo: "changed",
        LeaveAlone: "untouched three"
    }
}
{
    first: "changed",
    second: "two",
    obj: {
        a: "b",
        f: "changed",
        m: "n"
    }
}


CIS Check Ensure 'Server Authentication' Property is set to 'Windows Authentication Mode'

Ensure 'Server Authentication' Property is set to 'Windows Authentication Mode'

Close #741


Split-attrs merge message

Closes #5585
During consideration of #5585 with @trexfeathers, we realised that although the way merge compares attributes is OK,  the way it constructs a report of an attribute matching failure has some subtle problems in the "new world" of split attributes.
As stated in part of the testing code here,
        # Since Cube.attributes is now a "split-attributes" dictionary, it is now
        # possible to have "cube1.attributes != cube1.attributes", but also
        # "set(cube1.attributes.keys()) == set(cube2.attributes.keys())".
        # I.E. it is now necessary to specifically compare ".globals" and ".locals" to
        # see *what* differs between two attributes dictionaries.

This also affects the code where it works out which keys are different in existence ("cube.attributes keys differ: ") or value ("cube.attributes values differ for keys:") between two cubes whose attributes don't match.
Hence the changes here.
As so often, it was also useful to add some new tests to pin down existing behaviour,
When run against the prior feature-branch, behaviour looks like this :
$ pytest lib/iris/tests/test_merge_NEWSTUFF.py::TestCubeMerge__split_attributes__error_messages
================================================================================= test session starts ==================================================================================
platform linux -- Python 3.11.6, pytest-7.4.2, pluggy-1.3.0
rootdir: /net/home/h05/itpp/git/iris/iris_main
configfile: pyproject.toml
collected 6 items

lib/iris/tests/test_merge_NEWSTUFF.py ..FF..                                                                                [100%]

======================================================================================= FAILURES =======================================================================================
______________________________________________ TestCubeMerge__split_attributes__error_messages.test_splitattrs_keys_local_global_mismatch ______________________________________________
iris.exceptions.MergeError: failed to merge into a single cube.
  cube.attributes keys differ: 'b'

During handling of the above exception, another exception occurred:

self = <iris.tests.test_merge_NEWSTUFF.TestCubeMerge__split_attributes__error_messages testMethod=test_splitattrs_keys_local_global_mismatch>

    def test_splitattrs_keys_local_global_mismatch(self):
        # Since Cube.attributes is now a "split-attributes" dictionary, it is now
        # possible to have "cube1.attributes != cube1.attributes", but also
        # "set(cube1.attributes.keys()) == set(cube2.attributes.keys())".

E     cube.attributes values differ for keys: "
=================================================================================== warnings summary ===================================================================================
lib/iris/tests/test_merge_NEWSTUFF.py::TestCubeMerge__split_attributes__error_messages::test_keys_differ__multiple
  <frozen importlib._bootstrap>:241: RuntimeWarning: numpy.ndarray size changed, may indicate binary incompatibility. Expected 16 from C header, got 96 from PyObject

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=============================================================================== short test summary info ================================================================================
FAILED lib/iris/tests/test_merge_NEWSTUFF.py::TestCubeMerge__split_attributes__error_messages::test_splitattrs_keys_local_global_mismatch - AssertionError: "cube.attributes keys differ: 'a', 'b'" does not match "failed to merge into a single cube.
FAILED lib/iris/tests/test_merge_NEWSTUFF.py::TestCubeMerge__split_attributes__error_messages::test_splitattrs_keys_local_match_masks_global_mismatch - AssertionError: "cube.attributes values differ for keys: 'a'" does not match "failed to merge into a single cube.
======================================================================== 2 failed, 4 passed, 1 warning in 2.18s ========================================================================

NOTE: it was also noted in the above that sometimes the list of differing keys appears in a different order, due to use of set logic.
I have also now added sorted to fix that in a couple of places

Consult Iris pull request check list

@trexfeathers for your consideration ?
Enjoy !!


API catchup with Java and C++ embedded API V4

Get the domain objects and main command objects to the same level as V4.

domain and main objects are in alignment between Java and C#


text size

Hi Thanks for your great library, very usefull.
Is it possible to change the size of the text for the radioButton ?
Thank you

This is a duplicate of another issue, but currently you'd need a custom adapter


Terrain checkbox in OV2 export dialog does not work properly

In ExportOV2Form.cs line 88:
PluginSettings.Instance.gcTerrain = this.checkBoxOwner.Checked;
should be:
PluginSettings.Instance.gcTerrain = this.checkBoxTerrain.Checked;

Thanks for reporting this. Fix is committed and will be available in next release (<IP_ADDRESS>)


Fix warnings which arise from running the notebooks

Describe the Bug
Discovered in the unintentional run in #367
To Reproduce
import glass
...
Expected Behaviour
No response
Actual Behaviour
No response
Version In Use
N/A
Additional Context

Python version:
Operating system:

Fixed in #380


Showing PropertFieldNumber, Descriptor, etc. in the docs doesn't help.

It clutters the docs.  I don't want to see it.  Example:
https://googlecloudplatform.github.io/google-cloud-dotnet/1.0.0-beta01/docfx/api/Google.Datastore.V1Beta3.Projection.html

Well, they're part of the public API... it would be odd not to show them, IMO. (They'll definitely be shown in Intellisense, and it would be very confusing for a user to see them there, try to find them in the API documentation, and then not see them appear...)
There's certainly an argument for some sort of levels of filtering - for example, most users won't need to see the request proto messages at all if they're using the higher-level abstractions. That said, all of the way that documentation is built/consumed is in a certain amount of flux... I don't anticipate us working on filtering any time particularly soon. (I don't think I've seen it in any other API documentation, even though it's a potentially useful feature.)

I agree it is a deviation from the standard pattern to hide these elements in the docs.  But as a user, I find myself constantly scrolling passed and annoyed by these elements.  I'll never need to use them.
They will pop up in Intellisense, but I'm used to ignoring things in Intellisense like the .Equals() method and the like.

Thinking about it, I believe we may be able to do this with a tool to just prune the generated metadata. Will experiment and present a reduced docset in my repo.

Cool.  Thank you for the continuing effort.
On Tue, Sep 13, 2016 at 1:51 AM, Jon Skeet<EMAIL_ADDRESS>wrote:

Thinking about it, I believe we may be able to do this with a tool to just
prune the generated metadata. Will experiment and present a reduced docset
in my repo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-dotnet/issues/305#issuecomment-246617295,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALO54lgslReNaH_bZWJ3TfU63H8t68mzks5qpmQqgaJpZM4Jhd8U
.

Okay, it turns out docfx supports exclusion filters.  Ah well.
Have a look at https://jskeet.github.io/google-cloud-dotnet/ and see what you think. I was pleasantly surprised.

I like it!
On Tue, Sep 13, 2016 at 9:20 AM, Jon Skeet<EMAIL_ADDRESS>wrote:

Okay, it turns out docfx supports exclusion filters.  Ah well.
Have a look at https://jskeet.github.io/google-cloud-dotnet/ and see what
you think. I was pleasantly surprised.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-dotnet/issues/305#issuecomment-246738281,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALO54rcmmU01UihbcAEAeTSndOIEVRQaks5qps1YgaJpZM4Jhd8U
.

Have discovered that we were filtering a bit too aggressively. We have a new plan which will still remove all of these from protos, but shouldn't touch handwritten code such as BigqueryTable.ToString. Hope to get that done in the next day or two, and the new docs deployed then. Will keep this issue open until it's really done.

Done now. The new version even omits the constructors for protos - which was unintentional, but turns out to be quite handy.


Missing random uuid generator and address generator classes as defined at Java client

Added UuidUtil and AddressHelper classes. UuidUtil lets you to generate random uuid. AddressHelper gets possible address list for a provided hostname. These will be used by the client services.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test PASSed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test PASSed.

Test FAILed.

Test PASSed.

Test FAILed.

verify-linux

Test FAILed.

Test FAILed.

Test PASSed.

Test PASSed.


Updates to violin/split-violin/line/bullet

Updates made to violin, split violin, bullet, line, and coloredBar.


tox-dashboard: update for nautilus

We don't need to use dev_setup playbook on stable branch. We also
need to remove the dev container image variables and update the
value to match nautilus.
Signed-off-by: Dimitri Savineau<EMAIL_ADDRESS>

needs https://github.com/ceph/ceph-build/pull/1317 first

jenkins test nautilus-centos-non_container-dashboard

jenkins test nautilus-centos-non_container-dashboard

jenkins test nautilus-centos-non_container-dashboard

jenkins test nautilus-centos-non_container-dashboard


Update TEMPLATECONF path

Updates the TEMPLATECONF to the new distro path (https://github.com/jhnc-oss/meta-protos/issues/79).

Missing distro layer added by https://github.com/jhnc-oss/protos/pull/3.


Custom PdoAdapter methods not overriding original Pdo methods

I have my own users table and authentication methods that I use to authenticate so I created a custom PdoAdapter for this that extends \OAuth2\Storage\Pdo. I was previously using apigility 1.0 beta where this was working and have upgraded to 1.5. Everything is working fine except for my custom PdoAdapter and PdoAdapterFactory which I also updated to reflect the latest changes. The custom PdoAdapter gets called, however, it is not overriding the necessary methods in \OAuth2\Storage\Pdo like it's supposed to.
global.php
...
  'service_manager' => [
        'factories' => [
            'PdoAdapter'   => '\Custom\Factory\PdoAdapterFactory',
...

local.php
...
'zf-oauth2' => [
        'storage' => 'PdoAdapter',
...

When I try the above. it also breaks the admin interface. The main interface loads, but it doesn't populate my apis or services and I get a popup error that says "Unable to fetch dashboard!".
I've also tried to go direct and change storage to the full path of my custom PdoAdapter like so:
local.php
'zf-oauth2' => [
        'storage' => '\Path\To\Custom\PdoAdapter',

The methods I'm overriding are checkClientCredentials(), checkUserCredentials(), getUser(), and setAccessToken()
The usernames in my custom table are stored in a field called 'email' Doing a password grant_type I see that it is trying to call Pdo->getUser() which is looking for db column 'username' instead of 'email' like it is in the method I'm using to override.
So, I expect this to use the methods I'm using to override instead of the original bshaffer Pdo class method, but that is not the case.
Has something changed that I'm unaware of?

My mistake. There were some composer components I needed to upgrade which i thought were up to date.


question 64

I found a miswrite:
const multiply = (x = { ...value }) => {
  console.log((x.number * 2)); // console.log(x.number *= 2);
};

PR to fix: https://github.com/lydiahallie/javascript-questions/pull/154


Sbt plugin for dumping event schema

For clarity: I changed the name of the PR, it's supposed to be events first and foremost (message compatibility is a concern but minor relative to event compatibility)

@MarconZet since you're online, pls catch up with Slack (PM and the new channel) :whip:


fix: Fixed Recording of test cases

This pr fixes the behavior of recording when terminal is closed.

After recording test cases in zsh shell

Great work! Works great with replay, please check on the record side

also add semicolons in your files, will cause havoc later if not present

This is making, default running shell as bash, this isnt ideal,please look into the same

if any terminal is open it is also closed please try to fix it

Well done @ayush3160


Rework Test Application using Entity Class

As a user, I want to test cobigen code generation using an entity class with the following tutorial:
https://github.com/devonfw/cobigen/wiki/howto-devonfw-ide-CobiGen-PoC-E2E
The tutorial should show a step-by-step process using the current version of cobigen instead of an old version.

We suggest fully reworking the wiki tutorial as it is too extensive with only a little focus on the CobiGen part. Moreover, it is hard to follow, as the descriptions and images provided no longer fit, since the devon version is outdated.
Shortening the tutorial would be helpful to shift the focus on the functionalities of CobiGen. We would also introduce the CLI  to the user, which was not mentioned before.


Us018 load variable event dates

This PR adds in the ability for the user to view variable dates for a collection exercise (employment, ref p start, ref p end, reminders).
You'll need to load in the new event dates from the RM tools to be able to view the dates.
Best to look at the qbs survey to view the dates as that all all the new variable dates added.

Codecov Report

Merging #58 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #58   +/-   ##
=======================================
  Coverage   95.86%   95.86%
=======================================
  Files          24       24
  Lines         556      556
=======================================
  Hits          533      533
  Misses         23       23

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 2605bea...e905f16. Read the comment docs.

 US018: INT Load variable event dates for a collection exercise [M]


chore: fix ci pipeline and enable black/ruff linting

This PR fixes the CI pipeline and adds the following tools for parity between the pipeline and local env:

tox
black
ruff
The linting rules can be found in pyproject.toml while the testing rules can be found in tox.ini

It is now also easier to install the package, its dependencies, and any dev requirement locally using pip install -e ".[dev]" so there is no need for a redundant requirements.txt file

Thanks @IdoKendo
please notice there is a conflict with the master branch

@royashcenazi Fixed! 😃


Azure Netapp Files - az netappfiles list-mount-targets

Running this command through automation on azure devops pipelines on ubuntu machine:
az netappfiles list-mount-targets --resource-group ${RESOURCE_GROUP_NAME} \
        --account-name ${ANF_ACCOUNT} \
        --pool-name ${ANF_POOL} \
        --volume-name ${ANF_VOL}

I get this error:
Command group 'netappfiles' is in preview. It may be changed/removed in a future release.
Azure Error: InvalidResourceType
Message: The resource type 'netAppAccounts/capacityPools/volumes/mountTargets' could not be found in the namespace 'Microsoft.NetApp' for api version '2019-10-01'. The supported api-versions are '2017-08-15,2019-05-01,2019-06-01,2019-07-01,2019-08-01'.

It seems around April 9 or 10 that this error started happening. It is not happening on my local machine so I am assuming that the Azure-Cli or Azure-Cli-Extension had a version change that either  recently and that it is installed on the machines that the versions are running. None of my requirements or versions changed. When I was going through cli / extensions changes it looks like there was a release on april 9? I just am not getting a clear error message and nothing in process changed through automation. Since az-cli is already installed on ubuntu machines for azure devops I am assuming something with newest version of that or extension.
Also added apt list to pipelines to get cli version:
azure-cli/xenial,now 2.3.1-1~xenial all [installed]

netappfiles

I am having the same issue, any update on it?
Thanks

Having the same again today with azcli 2.3.1 on a devops agent I've built with the latest azcli, while it works on Cloud shell which is azcli 2.2.0

What is the status on this issue ? it still happening on 2.5.1.

Reverting to azcli 2.2.0 and it works. Any of the newer cli versions it is broke.

@rebecca-makar this workaround is not always possible. CloudShell is on 2.4.0 and can't be reverted I guess

@xpillons  completely agree. Wanted to say where I noticed the difference

@yonzhan any updates on this? Still broken

@rebecca-makar netappfiles service team should look into this.

@yonzhan how do I contact them?

@leonardbf could you please help with this?

Quick test using Azure CLI docker images shows this working the same in latest and 2.2.0.
However note that list-mount-targets is due for deprecation/removal in upcoming version of the CLI, as mount target information can be retrieved using volume show.
az netappfiles volume show -g TestRG -a test-account -p test-pool -v tests-vol-1
. .   "mountTargets": [     {       "endIp": "",       "fileSystemId": "3fcf5730-6f36-0900-7228-5effdea724bd",       "gateway": "",       "ipAddress": "<IP_ADDRESS>",       "mountTargetId": "3fcf5730-6f36-0900-7228-5effdea724bd",       "netmask": "",       "provisioningState": "",       "startIp": "",       "subnet": ""     }   ], . .

Related to #13011 - this seems resolved in version 2.10.1. This can probably be closed.


Document that you do not support environment variables

This is missing information from https://prometheus.io/docs/alerting/configuration/
Support for environment variables was bizarrely removed in https://github.com/prometheus/alertmanager/pull/308 and it makes deploying alertmanager a total PITA as a result.

That page already documents what we do support, I don't think it's sane to list everything we don't support. For example we don't take configuration from other files, etcd or secure enclaves either.


Custom domain for secret vault

Is your feature request related to a problem? Please describe.
If the suse sandbox goes down, we could incur downtime.
Describe the solution you'd like
Use a custom domain to point to the vault (e.g. vault.kubecf.suse.dev).

The vault is currently reached at https://volt.cap.explore.suse.dev/.
How different is that from the custom domain ?
Where would the domain be registered/made ?
Is this possibly something for Chris Olstrom, our system admin ?

@viovanov we need more details about where the data lives and how to deploy an instance?

@andreas-kupries this was meant as a separate installation of vault, that's not dependent on the sandbox.
I still think hosting on the sandbox is a good idea, but we should chat with Chris, yes.


Error when opening application.

I run the application (v0.9.2-alpha), either as normal user or as administrator and I receive an error.
Header with name 'parameters' was not found. If youa re expecting some headers to be missing and want to ignore this validation, set the configuration HeaderValidated to null. You can also change the functionality to do something else, like logging the issue.
I assume something goes wrong here? I'm sadly on Windows 10 and was hoping for a simple quick app launcher. But this seems to not really work as of yet. The app loads but I can't really do much within the options. I assume this related to this error message?

Hi, I have looked into your issue and found the cause.
Turns out the program wasn't creating the data files correctly, I have fixed it in 0.9.3-alpha.
For a quick fix, follow the steps below:

Make sure FLauncher is open
Right click the tray icon (the blue square with the arrow)
Click Open Data Location
Open Aliases.csv
Quit Flauncher (right click tray icon > quit)
Replace the contents of Aliases.csv with: alias,full_path,parameters
Save file
Open FLauncher and it should work

Issue solved


Delete debug_api.rs

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #367", "re #367".):

[ ] N
[x] Y

2. What is the scope of this PR (e.g. component or file name):
kclvm/runtime/src/stdlib/debug_api.rs
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[x] Other
debud_api.rs file is no longer needed.

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

I have read the CLA Document and I hereby sign the CLA

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.712%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1369

Relevant Lines:
1526

💛  - Coveralls

Hi, @Rishav1707. Welcome to KCLVM! Thanks for your contribution! Maybe you forgot to deal with the related function calls in debug_api.rs, please delete them to ensure that the KCLVM rust project compilation passes.

Hi, @Rishav1707. Welcome to KCLVM! Thanks for your contribution! Maybe you forgot to deal with the related function calls in debug_api.rs, please delete them to ensure that the KCLVM rust project compilation passes.

But, I have already deleted all the related function calls.

Hi, @Rishav1707. Welcome to KCLVM! Thanks for your contribution! Maybe you forgot to deal with the related function calls in debug_api.rs, please delete them to ensure that the KCLVM rust project compilation passes.

But, I have already deleted all the related function calls.

For example, https://github.com/KusionStack/KCLVM/compare/main...Peefy:KCLVM:remove-debug-api?expand=1, If you delete this file, you also need to delete the corresponding module declaration in mod.rs.

Hi, @Rishav1707. Welcome to KCLVM! Thanks for your contribution! Maybe you forgot to deal with the related function calls in debug_api.rs, please delete them to ensure that the KCLVM rust project compilation passes.

But, I have already deleted all the related function calls.

For example, https://github.com/KusionStack/KCLVM/compare/main...Peefy:KCLVM:remove-debug-api?expand=1, If you delete this file, you also need to delete the corresponding module declaration in mod.rs.

Thank you for your help😊


[PACKER] Fatpack DOT net install/build fails

On the local packer build process of the fatpack - it seems to fail regularly:

At the moment we install DOT net thru tar.gz-binaries ... @openoms maybe installing thru Microsofts debians repos would provide better compatibility? See install instructions recommended by GPT:
Yes, Debian provides a relatively straightforward way to install the .NET Core SDK (v8.0 or above). Here’s how you can do it:
1. Install the Microsoft Package Repository
First, you need to add the Microsoft package repository to your system. This will allow you to install .NET SDK directly using Debian's package management system.

Add Microsoft’s GPG key:wget https://packages.microsoft.com/config/debian/$(lsb_release -rs)/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb

2. Update Package Lists
After adding the repository, update your package lists:
sudo apt-get update

3. Install the .NET SDK
Now, you can install the .NET SDK (v8.0 or above):
sudo apt-get install dotnet-sdk-8.0

This command will install .NET 8.0 SDK on your Debian system. If you need a different version, you can adjust the version number accordingly (e.g., dotnet-sdk-7.0 for version 7.0).
4. Verify the Installation
After installation, you can verify that it’s correctly installed by checking the version:
dotnet --version

This approach integrates .NET Core SDK with Debian's native package management, making it easy to install, update, and manage the SDK versions as needed.

Hmm .. looks like there is no DOTnet available in https://packages.microsoft.com/debian/12/prod/dists/bookworm/main/binary-arm64/Packages

There is an dont-net version in some edge snap repo .. but following that path I just ended up with:
admin@<IP_ADDRESS>:~ ₿ dotnet --version
/snap/dotnet-sdk/79/snap/command-chain/snapcraft-runner: 3: exec: /snap/dotnet-sdk/79/dotnet: not found

So looks like using the tar.gz-binaries install is the only feasable way for now. And to solve this problem with packer we have to check if we can optimze the VM env.

The install by using the microsoft install script is also not helping - results in the same error.
  sudo -u btcpay wget https://dot.net/v1/dotnet-install.sh -O dotnet-install.sh
  sudo -u btcpay chmod +x dotnet-install.sh
  sudo -u btcpay ./dotnet-install.sh --channel 8.0
  sudo -u btcpay export DOTNET_ROOT=$HOME/.dotnet
  sudo -u btcpay export PATH=$PATH:$DOTNET_ROOT:$DOTNET_ROOT/tools
  echo "DOTNET_CLI_TELEMETRY_OPTOUT=1" | sudo tee -a /etc/environment

TODOs:

[ ] Try when deactivating BTCPay fatpack if it then runs thru
[ ]   try preview of dotNET 9.0 : sudo -u btcpay ./dotnet-install.sh --channel 9.0

Its not just BTCPay Server dotNET framework failing to build in packer VM ... also the build the ElectrsRS with Rust fails (when I deactivate BTCPay from fatpack builds):


bot proactive message debug error: Missing environment variables

Due to PR change manifest file "app name variable" from "CONFIG__MANIFEST__APPNAME__SHORT" to "CONFIG__APPNAME__SHORT", now follow readme to debug will get  Error: Missing environment variables 'CONFIG__APPNAME__SHORT' for file: XXX.
if this name change is necessary, env and related file still need to update also.

repo step:

install teams toolkit vsc extension
clone sample: https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-proactive-messaging-teamsfx
local debug follow readme

@ayachensiyuan - Thank you for your inquiry about your Teams app development issue! We will test this and update you soon.

@Nivedipa-MSFT @Mohammed-MSFT Local debug is work, but provision in to azure still have missing environment variables issue.
repo step: "teamsapp provision --env dev"

Hi @ayachensiyuan
Thank you for your inquiry about azure provision issue, I have tested and fixed the issue, and the Azure provisioning was successfully executed. Will create the PR and update the sample as soon as possible.
FYI

Today's test result shows that your PR change is work, thanks @Mohammed-MSFT

@ayachensiyuan - Glad to hear that the issue has been resolved!
Could you please share your valuable feedback via the Microsoft Teams Developer Community Response Feedback link? Your input helps us improve our support.

We are closing this issue for now, please feel free to reopen it, if required.


Incorrect throughput value in desc-wfmon

The monexp notebook evaluates the time for the job to complete and prints in on the throughput plot. But I can see in one case that the value is being overestimated. Nb version is 6.1.dev1 and pkg version is 0.11.1.

This was fixed.


fix: add messagingEndpointPath to Options in restify integration lib

Description
Adds messagingEndpointPath: string to botbuilder-runtime-integration-restify.Options for configurability of messaging endpoint. start() uses ternary and spread operators to combine defaultOptions with the optional passed in options.
https://github.com/microsoft/botbuilder-js/blob/d44179f6f344b2882cc585bd373509852ba91e10/libraries/botbuilder-runtime-integration-restify/src/index.ts#L37-L45
The value for defaultOptions.messagingEndpointPath is '/api/messages'.
makeServer() now takes the messagingEndpointPath as its first argument.
To avoid annoying JS runtime errors around the incorrect type being passed in for options, botbuilder-stdlib was added to make use of tests.isObject in the ternary operator.
https://github.com/microsoft/botbuilder-js/blob/1774d5104b1e40073e577955212ec859819418f2/libraries/botbuilder-stdlib/src/types.ts#L453-L455

Pull Request Test Coverage Report for Build 615562901

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.003%) to 84.716%

Files with Coverage Reduction
New Missed Lines
%

libraries/botbuilder-lg/src/templateExtensions.ts
1
84.48%

Totals

Change from base Build 614831139:
0.003%

Covered Lines:
18611

Relevant Lines:
20933

💛  - Coveralls


Cap Text line-width at 80 chars in Help page

Per WebAIM WCAG 1.4.8

Can't style this way for some reason.


I have a problem coping data from a parquet file stored on ASDL Gen2 to SQL Server 2019 run on a virtual machine.

I have a problem coping data from a parquet file stored on ASDL Gen2 to SQL Server 2019 run on a virtual machine.
The error is as below:
{
'errorCode': '2200',
'message': 'ErrorCode=DataTypeNotSupported,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=The data type UTF8 is not supported.,Source=Microsoft.DataTransfer.Common,'',
'failureType': 'UserError',
'target': 'Copy_w11',
'details': []
}

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

ID: 16b565fd-5303-cfcb-73f7-e2fd54a9c3a1
Version Independent ID: bcbd827a-09e5-3990-2a42-1a0d35cc9415
Content: Copy and transform data in Azure Data Lake Storage Gen2 - Azure Data Factory
Content Source: articles/data-factory/connector-azure-data-lake-storage.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@lukaszgolebiewski Since the issue is not a feedback on the doc in reference, I would recommend you to create a thread on the forums - MSDN  or stack overflow.
Once you post your issue on forums, it will have visibility across the community which is a better suited audience for such types of issues.
Please create a Forum thread and post it's link here and tag me so that we can track that thread. We would love to work with you on the issue on the forums.
I will now proceed to close this issue. Feel free to comment if you have any other queries.

@lukaszgolebiewski To get you unblocked for now, here's a similar thread :
https://social.msdn.microsoft.com/Forums/en-US/6f124db9-4594-4703-b4f7-43c9bc800671/copying-from-sql-server-to-azure-datalake-error-converting-byte-array-to-json?forum=AzureDataFactory
Please have a look at the proposed answers and see if it helps.


[SPARK-47197] Failed to connect HiveMetastore when using iceberg with HiveCatalog on spark-sql or spark-shell

What changes were proposed in this pull request?

Make spark-sql, spark-shell be able to access iceberg with HiveCatalog.
If a user want to access iceberg table with HiveCatalog through spark-sql, spark-shell, the user should specify additional configuration:
$ spark-sql --conf spark.sql.extensions=org.apache.iceberg.spark.extensions.IcebergSparkSessionExtensions \
--conf spark.sql.catalog.hadoop_prod=org.apache.iceberg.spark.SparkCatalog \
--conf spark.sql.catalog.hadoop_prod.type=hive \
--conf spark.sql.catalog.hadoop_prod.uri=thrift://hms1.example.com:9083,thrift://hms2.example.com:9083 \
--conf spark.hadoop.iceberg.engine.hive.enabled=true \
--conf spark.jars=hdfs:///some/path/to/iceberg-spark-runtime-3.2_2.12-1.4.3.jar \
--conf spark.hadoop.hive.aux.jars.path=hdfs:///some/path/to/iceberg-hive-runtime-1.4.3.jar \
--conf spark.security.credentials.hive.enabled=true

Why are the changes needed?

spark-sql and spark-shell cannot access iceberg table with HiveCatalog because there is no HIVE_DELEGATION_TOKEN.
Does this PR introduce any user-facing change?

If there is a user who specify --conf spark.security.credentials.hive.enabled=true, spark will get HIVE_DELEGATION_TOKEN even though deploy mode is not "cluster".
How was this patch tested?

Manually tested on on-premise internal cluster with Hadoop 3.3.4, Iceberg 1.4.3, and Spark 3.2.3.
Was this patch authored or co-authored using generative AI tooling?

No.

HiveDelegationTokenProvider takes care of the Spark built-in HMS client token refresh, Iceberg uses its own implemented HMS client, and should take care of itself.
As an example, Apache Kyuubi implements a Hive Connector based on Spark DSv2 API, which allows connecting to multi HMSs, and implements KyuubiHiveConnectorDelegationTokenProvider to take care of the token refresh for its managed HMS clients https://github.com/apache/kyuubi/pull/4560

Thanks for reply.
With spark-sql or spark-shell, it is impossible to use iceberg with HiveCatalog? only iceberg with HadoopCatalog is supported?

IMO it's an Iceberg side issue, and in addition to the case you listed above, accessing multiple Kerberized HMS cases should be considered, e.g. the Spark built-in HMS and Iceberg HMS are different, configure more than one Iceberg Hive catalogs
+cc @pvary @szehon-ho @sunchao

Thanks for explanation. I think I need to review spark, iceberg codes more...

Oh! I finally figure out why it fails.
I should not use iceberg-hive-runtime jar on spark-sql or spark-shell.
I forgot to specify database and query with "catalog".
SELECT * FROM prod.db.table; # correct
SELECT * FROM db.table; # wrong


README: Update clone url to use imba/imba.io

The README is currently telling you to clone somebee/imba.io.git but it should say imba/imba.io instead.
https://github.com/imba/imba.io/blame/master/README.md#L6

I have a requested a pr, please check @scanf

@globefire Thank you.


docker image can't find when i restart my pc

dear everyone:
my pc is window10 ,when i restart my pc, i run the ( Docker Quickstart Terminal) then Kitematic (Alpha),  last when i run docker images,there nothing,but before there has ,such su zookeep,redis ....and so on

Can you provide the output of docker info and the version of the Docker for windows app, please?

Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 1.12.1
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 0
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.17-boot2docker
Operating System: Boot2Docker 1.12.1 (TCL 7.2); HEAD : ef7d0b4 - Thu Aug 18 21:18:06 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.955 GiB
Name: default
ID: RZTS:J7SC:3FIH:27N7:QPUI:XJER:MYR5:4QQJ:NR6G:KSMO:FJWL:BBOI
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 13
Goroutines: 23
System Time: 2016-09-01T08:25:25.865668761Z
EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
provider=virtualbox
Insecure Registries:
<IP_ADDRESS>/8

Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 1.12.1
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 0
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.17-boot2docker
Operating System: Boot2Docker 1.12.1 (TCL 7.2); HEAD : ef7d0b4 - Thu Aug 18 21:18:06 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.955 GiB
Name: default
ID: RZTS:J7SC:3FIH:27N7:QPUI:XJER:MYR5:4QQJ:NR6G:KSMO:FJWL:BBOI
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 13
Goroutines: 23
System Time: 2016-09-01T08:25:25.865668761Z
EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
provider=virtualbox
Insecure Registries:
<IP_ADDRESS>/8

Based on these symptoms, I suspect that upgrading Docker Toolbox created a new Virtual Machine, causing your old images to disappear. This is not a bug in docker (engine), but if you're still running into this, please open an issue in the Docker Toolbox issue tracker https://github.com/docker/toolbox/issues
I'll close this issue here, but feel free to comment


Uds documentation

Description

documentation update:

UDS knowledge base in diagnostic messages (and related) topics
user documentation of messages subpackge

rename NPDU -> UDS Packet
bugfix: unknown SID value was considered as invalid SID value

How Has This Been Tested?

unit tests
static code analysis
documentation is compiling

Process
I know the process and did my best to follow it

Pull Request Test Coverage Report for Build 412

58 of 58 (100.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 396:
0.0%

Covered Lines:
344

Relevant Lines:
344

💛  - Coveralls


Hide the debugging article

Fixes https://dev.azure.com/fluidframework/internal/_workitems/edit/1190
It should no longer appear in the Table of Contents (under the Testing folder)

I suggest adding draft: true to the front matter of the debugging page instead.

Done


CircleCI frequently fails

CircleCI frequently fails

For reference, we don't really want to re-add the SCP dependency in the integration test suite, at least not this one. See https://github.com/bpfkorea/agora/commit/87ae5d05143d758363de9ed1d3aa75b084b48a49#diff-3d9bd18baf7bf8355b12b9baad7bc07c where it was removed.


Microsoft.EntityFrameworkCore.RawSqlStringInjectionDiagnosticAnalyzer cannot be created after updating EfCore to 2.10

When I upgraded to Entity Framework core 2.1, I got the below warning each time I try to build the application
Output Warning
CSC : warning CS8032: An instance of analyzer Microsoft.EntityFrameworkCore.RawSqlStringInjectionDiagnosticAnalyzer cannot be created from C:\Users\Mohamed.Shousha\.nuget\packages\microsoft.entityframeworkcore.analyzers\2.1.0\analyzers\dotnet\cs\Microsoft.EntityFrameworkCore.Analyzers.dll : Could not load file or assembly 'Microsoft.CodeAnalysis, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified..

dotnet info details
.NET Command Line Tools (2.1.105)

Product Information:
 Version:            2.1.105
 Commit SHA-1 hash:  141cc8d976

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.10586
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.105\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.7
  Build    : 2d61d0b043915bc948ebf98836fefe9ba942be11

Further technical details
EF Core version:  2.1.0
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Project .Net Core Version: 2.0
Operating system: Windows 10 Enterprise
IDE: Visual Studio 2017 15.5.2

Duplicate of #12222

Can you upgrade your VS to 15.7.3 & install .NET Core SDK 2.1.0 and see if the problem goes away?

@Moudybasha We believe that when using Visual Studio with EF Core 2.1 will require VS 15.7.3 to avoid this warning. Or you can live with the warning--there is no runtime functionality in the analyzer package.


Fix MacosPulldownMenuItem.onTap doesn't open alert dialog

fixes MacosPulldownMenuItem onTap doesnt call showMacosAlertDialog
Code sample

expand to view the code sample
import 'package:flutter/cupertino.dart';
import 'package:macos_ui/macos_ui.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MacosApp(
      debugShowCheckedModeBanner: false,
      home: HomePage(),
    );
  }
}

class HomePage extends StatelessWidget {
  const HomePage({super.key});

  @override
  Widget build(BuildContext context) {
    return MacosScaffold(
      toolBar: ToolBar(
        title: const Text('macos_ui'),
        actions: [
          ToolBarPullDownButton(
            label: 'Actions',
            icon: CupertinoIcons.ellipsis_circle,
            tooltipMessage: 'Perform tasks with the selected items',
            items: [
              MacosPulldownMenuItem(
                label: 'New Folder',
                title: const Text('New Folder'),
                onTap: () => showMacosAlertDialog(
                  context: context,
                  builder: (context) => MacosAlertDialog(
                    appIcon: const FlutterLogo(size: 64),
                    title: const Text('Title'),
                    message: const Text('Message'),
                    //horizontalActions: false,
                    primaryButton: PushButton(
                      controlSize: ControlSize.large,
                      onPressed: Navigator.of(context).pop,
                      child: const Text('Label'),
                    ),
                  ),
                ),
              ),
              MacosPulldownMenuItem(
                label: 'Open',
                title: const Text('Open'),
                onTap: () => debugPrint('Opening...'),
              ),
            ],
          ),
        ],
      ),
    );
  }
}

Preview

Pre-launch Checklist

[x] I have incremented the package version as appropriate and updated CHANGELOG.md with my changes
[ ] I have added/updated relevant documentation
[x] I have run "optimize/organize imports" on all changed files
[x] I have addressed all analyzer warnings as best I could

Just gonna run the checks manually since you're a first time contributor

Looks like we've got some failing tests

Looks like we've got some failing tests

For some reason test passes locally with FlutterLogo but not in the CI so i just replaced it.


Using PHPUnit installed by composer.

Interesting, good call. I think we may need to update our skeleton project.


Mouse icon is not reset after unblock happens in Chrome Version 39.0.2171.95 m

Reproducible at http://angular-block-ui.nullest.com/#!/examples/documentation
Any example will show the issue, as long as mouse pointer is not moved after blocking started, the icon remains to be a spinner until pointer is moved. Chrome Version 39.0.2171.95 m
Works fine in IE/FF.

Moving cursor: wait; from .block-ui-container to .block-ui-active > .block-ui-container seems to help

Thanks for the fix!
Implemented in 0.2


Roll percentile dice - d00

Feature Request:
Roll only the % die.  For % games such as Call of Cthulhu you do not need the 10s die.

I misspoke a bit with CoC rules. So your typical rolls are the d100 as it is here. There is an advantage rule where you can roll % dice twice and take the lower result. If I understand rules correctly you keep the d10 as it is.
We're just doing a 2d100 as a work around.
As for notation. We have been using d00 but d% may be more intuitive.

I just discovered yesterday that this feature is available if the notation is passed as an object.
Box.roll({qty: 1, sides: '100'})

This should make it easier to create a string alias.


Disable the log in state tracker for previous debug

Description
Previously, we use the error log to make the debug easily and now it is unnecessary

Coverage increased (+0.007%) to 42.627% when pulling ab208c76c1d4815b155848242b370fc6a709b778 on xingtanzjr/disable_debug_log into 39db994138c878b9e4f055d4c62e56f9ceb86693 on master.


isort: Set src_paths, remove unnecessary known_third_party overrides

Tim thought commit 51acca2672ef0f583b65066ff0ab21750c5dc54d was needed because he had an extra social_django directory in his checkout.

It's great that this lets us remove a bunch of other things that shouldn't be there too :)

Feel free to merge once CI passes.


Dumplicate class error

Type xxxAspect$ajcMightHaveAspect is defined multiple times: xxx\build\intermediates\runtime_library_classes_jar\release\classes.jar:xxx/xxxAspect$ajcMightHaveAspect.class, xxx\app\build\postWeave\xxx\xxxAspect$ajcMightHaveAspect.class
The error only occurs when using with pertarget Aspect, why?

Thanks, but this project is no longer maintained (as indicated on the root README). Sorry.


Code OSS Dev: crash when trying to reload a crashed window

Steps to Reproduce:

add a process.crash() somewhere in workbench after 5s timeout
wait for crash dialog
click "Reload"

=> the app crashes entirely now
bcb54806-8a20-4222-b08e-ca19484a3b55.dmp.zip
Not sure if this is an Electron 11 regression or not.

/duplicate 117343


Create/Destroy timeouts API

@mergify backport main foxy

Codecov Report

:exclamation: No coverage uploaded for pull request base (galactic@b996df1). Click here to learn what that means.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             galactic     #166   +/-   ##
===========================================
  Coverage            ?   47.43%
===========================================
  Files               ?       42
  Lines               ?     1562
  Branches            ?      311
===========================================
  Hits                ?      741
  Misses              ?      612
  Partials            ?      209

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 b996df1...389c39a. Read the comment docs.


Allow Docker pushes on release branches

As outlined in https://github.com/lycheeverse/lychee/issues/1432#issuecomment-2477830138, the current workflow won't push to the Docker registry when a release is cut because releases now include a pull request.
This pull request increases the number of conditions under which a Docker image can be pushed.
Closes https://github.com/lycheeverse/lychee/issues/1432.

Thanks for your contribution (and your patience), @eread. 🥳
Let's see if it works. 🤞

Thanks for your contribution (and your patience), @eread. 🥳 Let's see if it works. 🤞

Thanks for the merge @mre! I didn't see of an easy way test it for sure. Hopefully a new release isn't too far away 😄

@mre @thomas-zahner We got a run of the new logic: https://github.com/lycheeverse/lychee/actions/runs/12389086296/job/34581417146
It looks like push still evaluated to false.
Also, the Docker command was run with --tag lycheeverse/lychee:pr-1554 --tag lycheeverse/lychee:sha-007d93a, rather than --tag lycheeverse/lychee:0.18.0. So still more to do there. 🤔

@mre @thomas-zahner We got a run of the new logic: https://github.com/lycheeverse/lychee/actions/runs/12389086296/job/34581417146
It looks like push still evaluated to false.
Also, the Docker command was run with --tag lycheeverse/lychee:pr-1554 --tag lycheeverse/lychee:sha-007d93a, rather than --tag lycheeverse/lychee:0.18.0. So still more to do there. 🤔

@trask I don't suppose you know how to resolve this?

The tags are because the pipeline didn't run on a release. The version tag is missing.
So either we're not listening to the right event or the logs belong to a different pipeline run.

Yeah, so we don't trigger a pull request on releases.
Typically this is done with
on:
  release:
    types: [published]

However, in our case we have a wait until the release binaries are created; otherwise the build would fail.
I don't know if there's a way to say that the workflow depends on another one. Alternatively, we could just have a "wait" step in the pipeline, which tries to curl the binary every 30 seconds or so until it succeeds.

We could trigger on release as shown above and use an action like https://github.com/marketplace/actions/wait-on to wait until the binaries were created.


Credo checks integration broken in 0.1.7

When I upgrade from 0.1.6 to 0.1.7 I no longer get excellent_migrations errors via Credo (I'm testing with Credo 1.7.7 but it appears to apply to most any version).
The culprit appears to be https://github.com/Artur-Sulej/excellent_migrations/pull/24
The PR itself looks fine to my eyes so I wonder if there is another part of excellent_migrations that was inadvertently depending on the swap.
I also tested with 0.1.7 but undoing the swap and when I do that I do get excellent_migrations error reported by mix credo.

Ah, nevermind. I wasn't running my credo check properly (I was running mix credo priv/repo/migrations which doesn't match any files, instead I needed to run mix credo priv/repo/migrations/*). And I was also misinterpreting the errors (which were in fact swapped on 0.1.6)


Update documents with Client-only build instructions

#132

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


Very strange issue with gmail.observe.after('send_message')

Hello !
I'm using the
gmail.observe.after('send_message', function (url, body, data, xhr) {
    console.log(JSON.stringify(xhr));
    // Some code
 } );

event in order to get the email id, like I explained in the end of this topic.
There is a VERY strange behavior I'm not able to debug successfully. Sometimes, apparently randomly when I forward or answer to a mail containing an image signature, the returned xhr is much shorter than usual. And it doesn't contains the data I need for the email ID...
All the beginning of the xhr is the same, it's just shorter. And I don't get it. How come the answer from Google's server is not the same just because something changes in the mail body ?!
If someone has any idea on how to debug that or why is it happening, I will gladly take it.
Thanks,
JB

If what you need to do is just get the email-id, what I've used to (seemingly reliably) get the ID of the sent email is one of the following two things:

from an "inline" reply or forward compose window, simply get the latest email-data for the thread and pick out the latest email ID after email is sent.
observe for the "email sent" toast presented on top of the screen. It will contain a link with the final email ID in it.

None of this is entirely clean, but I can't see how it's worse than relying on the XHR line-format directly in "application-level" code :)

@josteink thanks I will try to use that, will update the question with a solution when I find one !

@josteink how do you reliably observe for the email sent toast ? I tried to look for an event but the only one I find is sm which is mapped to send_message and occurs a condition race (will it be in the dom before or after the gmail.observe.after('send_message' happens).

I probed the GUI after the appropriate CSS classes :)

Worked (kinda), thanks


add markdown format for pipy

Add information for a markdown long description in pipy (which is now compatible).
This aim at avoiding this:
https://pypi.org/project/POT/0.4.0/
and getting something such as this:
https://pypi.org/project/POT/0.3.1/
The fail was due to  lack of pandoc on my machine at the time.

maybe:
python setup.py check --restructuredtext
can help.


[WIP] Add nuclear missile!

Still a lot to do:

[ ] Add missile sprite
[ ] Add some kind of 'projectile' thing flies from A to B with a given speed
[ ] Let projectile detonate (create explosion) upon arrival at destination
[ ] Introduce particle engine to show explosions
[ ] Add shockwave
[ ] Draw stuff accordingly to viewport/camera position
[ ] Produce sound on explosion?

And for the fun of it:

[ ] spawn and fly a nuclear missile where the mouse is clicked (would be nice for testing purposes)

Things it won't be able to do:

Do damage (to what? there is nothing! :))

Particle system implementation of Slick2d used, how it looks so far:

rebased on master - clearly shows problems with drawing as there is no way to draw shroud over fire or whatsoever. So it is very important to tackle https://github.com/stefanhendriks/dune2themaker4j/issues/15 first.

Drop this PR in favor of getting to issue #15 first


quite some character level bboxes are of zero width or zero height

thanks again for open sourcing your dataset and generation code. When training a model that requires character level labelling, I found that many of the character level bboxes either have zero width or zero height. May I know a suggested way to clean the data ?

Can you provide some examples that have zero width or heights? There should not be such data.
FYI, when I did the experiments with detection models, I filtered out bbox that are smaller than 10 px in either side. It should be enough to help.

In the current setting, some text are very small. This may boost detection performance but harm recognition performance.  There are still 17 character level bboxes that are either of zero width or zero height.

I filtered out bbox that are smaller than 10 px in either side.

I am not sure whether this filtering is proper since there are characters or symbols that are thin ( like I ) or short ( like " )

In my experiments, small words/characters can be beneficial in detection but may harm recognition. It makes better sense to only train on characters that are not too small.


debug_helpers.hpp uses ARCH_NAME specific include path for dev_msgs.h

https://github.com/tenstorrent/tt-metal/blob/6a463c115d07ff5af893b0526ce9675a6c01730a/tt_metal/impl/debug/debug_helpers.hpp#L59
dprint_buf_msg_t comes from dev_msgs.h which requires ARCH_NAME specific include path at the time of this writing.
The current usage forces ARCH_NAME specific compilation.

dev_msgs.h is no longer ARCH_NAME specfic


Create SMI Conformance badge

Current Behavior

Users are able to run SMI Conformance test and view the percentage of the tests passed in Meshery.
Desired Behavior

Create a badge that can be used in the README to show the pass percentage of the SMI Conformance test that was most recently done. Something similar to this:
Implementation

This might require more changes around the action but here is what I'm proposing:

Use the custom endpoints feature from Shields IO to generate the dynamic badge.
Create a JSON endpoint in meshery.io/service-mesh-interface to fetch the details to create the dynamic badge. This assumes that each of the participating service mesh has an official account that updates this data as they make new releases.

Blockers

No official accounts for service mesh projects.
Schedule of reporting: How quickly are the changes in test results reflected on the SMI Conformance Dashboard?

This issue might require more thought so this is just a draft proposal.

Contributor Guide

Hi @navendu-pottekkat
I would like to start contributing through this one.

Hello, I'm an contributor at open-force, can this issue be assigned to me? @Nikhil-Ladha  @navendu-pottekkat

Hello, I'm a contributor at Open-Force. Can this issue be assigned to me? @Nikhil-Ladha @navendu-pottekkat @leecalcote

Closing out as undesired.
What would be helpful instead is the addition of test version # on the results dashboards on meshery.io/smi and layer5.io/landscape#smi. The test that is run is versioned, but the results that are shown on the dashboards don’t allow users to navigate between result sets by test version #.


Is the FCS Dependency on System.Data.SqlClient intended?

@nojaf on the Foundation Slack noted that between versions 25 and 26 of FCS a new nuget dependency on System.Data.SqlClient appeared. From what we can see, the reason was to include the System.Data dll in the set of default references for FSI, is this the core reasoning? There's some worry about Fable and other FCS consumers now requiring the System.Data.SqlClient dependency and if that might be untenable for them, so I wanted to ask the question and at least get an answer on record.
It looks like it was introduced as part of #5923, if that helps narrow it down.

No it's not particularly intended.  I don't really know where it came from to be honest.  I don't think it's the default references
https://github.com/Microsoft/visualfsharp/pull/5923/files#diff-a2fc4429830a9bc94312ff5d413e3f1aR644

@dsyme It is the default references for non-.NET Framework. But if it's not a part of the shared framework then it shouldn't be included.
We need to re-evaluate this default set, see #6215

I just ran a quick test using fsharpi on mono 5.18, and open System.Data.SqlClient;; works out of the box there. This suggests to me that the dll is already included in the reference set on .Net Framework, and also should be included in the default set on .Net Core, so that scripts are more portable.

Gotcha, though things are also a bit different for framework. Given that the package is for working with Windows, perhaps it doesn't make sense to include for .NET Core/.NET Standard.

@dsyme It is the default references for non-.NET Framework. But if it's not a part of the shared framework then it shouldn't be included.

I don't know why that would mean it gets included as a dependency of the compiler bits.  The default references for scripting aren't read from the compilation directory, they are read from wherever we read the framework/reference assemblies from.
So we should just remove this dependency, it is not needed for the compiler bits.

@baronfel My understanding is that you can just remove this as a dependency of the compiler bits in the FCS repository.

If I remember correctly, it was added to get some tests that pass on desktop, to also pass on coreclr, that may not not be what we actually want, so I shall take a look.
I doubt if just removing the reference will work in the FCS repo because of:
https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/CompileOps.fs#L1857
I will take a look and see what is actually broken without this.  We may want it to not work anyway.

Oh I see, yes, well, that line was added by me I think - it was nothing particularly thought out, and certainly wasn't intended to added a hard dependency for the compiler bits.

Blame blames me ....  lol.
It was I think in the middle of a huge batch of let's get stuff working.  So I think it makes sense to actually analyze what's broken, and see what we intend to happen, and how best to resolve the issue.
As it is, it certainly doesn't crash on Linus, but our bar for that may be higher.  Anyway, I have a PR to see what breaks.
https://github.com/Microsoft/visualfsharp/pull/6274

@dsyme this is where we get the default set of references for FSI though - so if we need this, it's needed in the compiler unless we can factor it out. Or am I misunderstanding something?

Removed in #6274 - tests pass without it. We should think a bit more about what else to include separately.

@baronfel thanks for noticing and following up on this.
Good eyes :-)


json embedded in json is not working with json.loads

Here is the json I'm grabbing, which includes a log field that appears to have additional json.
https://qa-reports.linaro.org/api/testruns/2554178/tests_file/
What seems to be happening is when that string is loaded via json.loads quotes and other whitespace items are converted?
Here is an example of what I'm doing:
ep = 'api/testruns/%d/tests_file' % (tr.id)
 response = SquadApi.get(ep)
tests = response.json()
pprint.pprint(tests)

Notice how all the escape characters are gone and there are a bunch of single quotes now.
I see none of the tests seem to account for that.

Leave this alone for a bit until I get my head around it. Thanks!

This was actually caused by inconsistent data. See https://github.com/Linaro/squad/issues/719.


zsdx 1.11.0 (new formula)

Zelda Mystery of Solarus DX is a Zelda fan game created with the solarus engine.

SOLARUS_INSTALL_DATADIR is set to share, not pkgshare, and it's prepended by the package name.
test actually tests solarus engine.

Added a simple test to check if the data files are archived to a valid zip file. It's pretty naive, but maybe better than checking a mere existence.

@BrewTestBot test this please

Thanks!


Financial statements not working

Hello,
It seems the financial statements (income statement, bal sheet, cashflow) are not working as intended.
It's not showing an error, but is not returning any data.

Hello,
It seems the financial statements (income statement, bal sheet, cashflow) are not working as intended.
It's not showing an error, but is not returning any data.

https://github.com/ranaroussi/yfinance/issues/191
check here.


Update whats-new-in-v72.rst

Updated the summary to reflect the delayed release schedule.

Summary

Ticket Link

@wuwinson - Would you be open to applying this update directly to the v7.2-documentation branch? Doing so ensures that we can release all v7.2 functionality at once without having to manage individual PRs for the release.

@wuwinson - Given that this page is already live in production, please disregard my request to add this to the v7.2-documentation branch. :)


Fix typo in trajectory_writer.h

presense -> presence

Thank you for contributing to Reverb!
The PR was merged in https://github.com/deepmind/reverb/commit/945de5f6ff0aef9db93f45dbb2a6f71e6088c42b


resinhup: new flag to set supervisor to the target release's default version

Check the target resinOS release's default supervisor version, if the current
version is older, then tag the device for the new version in the API so that
it's updated after reboot, if the update is successful.

According to arch call, this is not correct, and discussing different approach.

In resinhup find what what version should be running
that in the api
docker pull the new version in Python part of resinHUP, and preload it.

Close for now, as working on new approach.


Fixed a typo in docstring

Fixed a minor typo in docstring of 'BigQueryExtractTask' from "depening" to "depending" in bigquery.py on line 689

Thanks @gmedinak !

No problem @dlstadther ! Glad I could do something small for my first commit 👍


Linux Support

Hi, huge fan of the project and the absolute speed it brings to the table. I was wondering if there were any plans to add some Linux functionality. I am aware that this project is currently not intended for Linux, but I find that if this speed could be brought to Linux down the line, you can successfully put MSS out of business.

Hi thanks for the support. Right now I have no plan for Linux support. Since the original goal of this project is only for small and specific usage scenarios on windows. If we add Linux support this will become a full-featured screen capture project. I would consider that if there are no other well-maintained libraries.
Btw in terms of speed, I believe Linux is not an issue. A default implementation using xlib11 will get decent fps.


Location prevalence data stopped updating 2/6/22

Describe the bug
The site no longer shows up-to-date location prevalence data, instead showing only data for 2/6 despite numbers weeks newer being available.
Link to microCOVID scenario
Link to a random US scenario
To Reproduce
Steps to reproduce the behavior:

Enter location USA (or any other region AFAIK)
Click on 'Details'
See 'Data last updated: 2/6/2022'

Expected behavior
See 'Data last updated: 2/21/2022' since that data appears available from Johns Hopkins CSSE and Covid Act Now. As a result, all calculations are based on data that is many weeks out of date.
Is this a regression?
No idea
Additional context / screenshots
Happens in every region/country I checked.
I assume the problem is that the automatic prevalence update bot broke.

Fixed in #1354


Choose metalsmith collection from .md file

I've been using Metalsmith static site generator for some time and I believe is a great tool. Now I started using metalsmith-collections plugin but I stumbled across this issue.
Given the case that I have two collections defined, for instance "en_news" and "sp_news" and the following news.hbt file:

{{title}}

{{contents}}

    {{#each collections.en_news}}

{{this.title}}

{{this.contents}}

    {{/each}}

Now in the .md file I want the collection to be either collection.en_news:
---
title: News
template: news.hbt
lang-collection: en_news
---
News in english language

...or collection.sp_news:
---
title: Noticias
template: news.hbt
lang-collection: sp_news
---
News in spanish language

How can I use "lang-collection" inside test.hbt to define the used collection?
Of course the following does not work:
{{#each collections.{{lang-collection}}}}

Thanks in advance!

@fracu I just accomplished this today using Handlebars' lookup helper:
My handlebars layout:
{{#each (lookup collections rollup)}}

{{ this.title }}

    {{{ this.excerpt }}}

{{/each}}

My yaml front-matter:
---
title: Recent Articles
layout: rollup.html
rollup: recent-articles
associated-collection: articles
---


freebsd support

I think you can have FreeBSD support already:
I have the following packages installed:
# pkg install -r FreeBSD lang/zig lang/erlang-runtime22 devel/elixir-hex devel/llvm80

This gives us zig-0.5.0 and the rest should be self explanatory.
I suppressed the side-effect-only Logger https://github.com/ityonemo/zigler/blob/master/lib/zigler/compiler.ex#L24
$ export NIFTY_LLVM_VERSION=80
$ mix do deps.get --all, deps.compile, compile
$ mix zigler.get_zig 0.5.0
...
$ mix test --trace

Compiling 17 files (.ex)

13:19:58.168 [info]  compiling using command: `/repos/zigler/zig/zig-freebsd-x86_64-0.5.0/zig build-lib zig_nif.zig -dynamic --disable-gen-h --override-lib-dir /repos/zigler/zig/zig-freebsd-x86_64-0.5.0/lib/zig`

13:19:58.176 [info]  compiling using command: `/repos/zigler/zig/zig-freebsd-x86_64-0.5.0/zig build-lib zig_nif.zig -dynamic --disable-gen-h --override-lib-dir /repos/zigler/zig/zig-freebsd-x86_64-0.5.0/lib/zig`

13:20:04.925 [info]  compiling using command: `/repos/zigler/zig/zig-freebsd-x86_64-0.5.0/zig build-lib zig_nif.zig -dynamic --disable-gen-h --override-lib-dir /repos/zigler/zig/zig-freebsd-x86_64-0.5.0/lib/zig --release-safe`
Generated zigler app

ZiglerTest.CompilerErrorParserTest
  * test the compiler line parser (0.04ms)

ZiglerTest.CompilerErrorTest
  * test compiler error catches and rewrites internal error (270.6ms)
  * test compiler error catches mismatched arity (35.3ms)
  * test compiler error catches and rewrites external error (485.7ms)
  * test compiler error catches mismatched nif (7.9ms)

ZiglerTest.ParserTest
  * test the nif parser can identify nifs (0.01ms)
  * test the docstring multiline parser can identify multiline docstrings (0.05ms)
  * test the function header parser can identify bool function headers (0.07ms)
  * test the function header parser can identify one-arity function headers (0.04ms)
  * test the docstring line parser will ignore a non docline (0.00ms)
  * test the function header parser can identify zero-arity function headers (0.02ms)
  * test the docstring line parser can identify a single docline (0.02ms)
  * test the function header parser can identify two-arity function headers (0.05ms)
  * test the function header parser can identify beam.env headers (0.05ms)
  * test the docstring line parser can identify a single docline when it's got indentation (0.01ms)
  * test the function header parser can identify string function headers (0.04ms)
  * test the function header parser can identify erlnifenv headers (0.06ms)

ZiglerTest.UnitParserTest
  * test the identifier parser fails on non_identifiers (0.00ms)
  * test the test header parser can identify test headers (0.08ms)
  * test the identifier parser can correctly identify identifiers (0.01ms)
  * test the import parser leaves pub imports alone (0.02ms)
  * test the identifier parser fails on strange symbols (0.00ms)
  * test the import parser can identify import statements (0.01ms)

ZiglerTest.CodeTest
  * test when given a code multiline string the code module can return plain code with no nifs, and assign files and lines correctly (0.04ms)
  * test when given a code multiline string the code module can do the correct thing with multiple functions (0.1ms)
  * test when given a code multiline string the code module can identify more complex nif headers (0.09ms)
  * test when given a code multiline string the code module can find a nif and correctly assign it, adding line numbers (0.07ms)

ZiglerTest.Types.EmptyTest
  * test zero arity zig functions work (0.06ms)

ZiglerTest.MutationTest
  * test passing binaries across a function self-call works (0.07ms)
  * test we can mutate binaries (0.00ms)

ZigTest.TypespecTest
  * test zigler correctly creates typespecs for degenerate (2.0ms)
  * test zigler correctly creates typespecs for generic beam types (23.0ms)
  * test zigler correctly creates typespecs for floats (0.5ms)
  * test zigler correctly creates typespecs for integers (0.9ms)
  * test zigler correctly creates typespecs for bools (0.7ms)
  * test zigler correctly creates typespecs for float lists (0.4ms)
  * test zigler correctly creates typespecs for strings (0.7ms)
  * test zigler correctly creates typespecs for int lists (2.8ms)

ZiglerTest.ZigdocTest
  * test gets the docs (695.7ms)

ZiglerTest.AllocatorsTest
  * test elixir persistent memory works (0.1ms)
  * test elixir basic allocator works (0.1ms)

ZiglerTest.DoubleZigTest
  * test two zig definitions in the different sigils (0.06ms)
  * test two zig definitions in the same sigil (0.05ms)

ZiglerTest.ExternalFilesTest
  * test a recursive external file can be called (0.05ms)
  * test a relative external file can be called (0.04ms)

ZiglerTest.Types.EgressTest
  * test lists can be egressed from c_int lists (0.1ms)
  * test lists can be egressed from internal literals (0.00ms)
  * test integers can be egressed c_int (0.00ms)
  * test lists can be egressed from f16 lists (0.00ms)
  * test lists can be egressed from i32 lists (0.00ms)
  * test floats can be egressed f32 (0.00ms)
  * test floats can be egressed f64 (0.00ms)
  * test lists can be egressed from c_long lists (0.00ms)
  * test strings can be egressed from a slice (0.06ms)
  * test integers can be egressed i32 (0.00ms)
  * test integers can be egressed c_long (0.00ms)
  * test lists can be egressed from i64 lists (0.00ms)
  * test bools can be exported correctly (0.00ms)
  * test characters can be egressed correctly (0.00ms)
  * test strings can be egressed from a c_string (0.00ms)
  * test lists can be egressed from f32 lists (0.00ms)
  * test lists can be egressed from f64 lists (0.00ms)
  * test integers can be egressed i64 (0.00ms)

ZiglerTest.Types.IngressTest
  * test 32-bit integers can be ingressed and are guarded for invalid values (3.5ms)
  * test binaries can be ingressed as slices and are guarded for invalid values (0.09ms)
  * test atoms can be ingressed and are guarded for invalid values (0.02ms)
  * test f32 lists can be ingressed correctly (0.07ms)
  * test pids can be ingressed as beam.pid correctly (0.00ms)
  * test f16 lists can be ingressed and are guarded for invalid values (0.09ms)
  * test binaries can be ingressed as binary structs and are guarded for invalid values (0.01ms)
  * test pids can be ingressed as e.ErlNifPid correctly (0.00ms)
  * test binaries can be ingressed as binary structs via e.ErlNifBinary and are guarded for invalid values (0.01ms)
  * test i32 lists can be ingressed correctly (0.00ms)
  * test 16-bit floats can be ingressed and are guarded for invalid values (0.01ms)
  * test f64 lists can be ingressed even with empties (0.00ms)
  * test binaries can be ingressed as slices correctly (0.00ms)
  * test atoms can be ingressed correctly (0.00ms)
  * test 16-bit floats can be ingressed correctly (0.00ms)
  * test pids can be ingressed as beam.pid and are guarded for invalid values (0.01ms)
  * test f32 lists can be ingressed and are guarded for invalid values (0.02ms)
  * test i64 lists can be ingressed even with empties (0.00ms)
  * test i64 lists can be ingressed and are guarded for invalid values (0.02ms)
  * test binaries can be ingressed as c_strings correctly (0.00ms)
  * test usize can be ingressed correctly (0.00ms)
  * test 64-bit integers can be ingressed correctly (0.00ms)
  * test binaries can be ingressed as binary structs correctly (0.00ms)
  * test c integers can be ingressed and are guarded for invalid values (0.01ms)
  * test 32-bit integers can be ingressed correctly (0.00ms)
  * test c integers can be ingressed correctly (0.00ms)
  * test f32 lists can be ingressed even with empties (0.00ms)
  * test f16 lists can be ingressed correctly (0.00ms)
  * test binaries can be ingressed as binary structs via e.ErlNifBinary correctly (0.00ms)
  * test i32 lists can be ingressed and are guarded for invalid values (0.02ms)
  * test i32 lists can be ingressed even with empties (0.00ms)
  * test usize can be ingressed and are guarded for invalid values (0.02ms)
  * test c longs can be ingressed and are guarded for invalid values (0.02ms)
  * test 64-bit floats can be ingressed correctly (0.00ms)
  * test 64-bit integers can be ingressed and are guarded for invalid values (0.02ms)
  * test f64 lists can be ingressed correctly (0.00ms)
  * test bools can be ingressed and are guarded for invalid values (0.02ms)
  * test characters can be ingressed correctly (0.00ms)
  * test pids can be ingressed as e.ErlNifPid and are guarded for invalid values (0.01ms)
  * test f16 lists can be ingressed even with empties (0.00ms)
  * test 32-bit floats can be ingressed correctly (0.00ms)
  * test isize can be ingressed and are guarded for invalid values (0.01ms)
  * test c longs can be ingressed correctly (0.00ms)
  * test binaries can be ingressed as c_strings and are guarded for invalid values (0.01ms)
  * test f64 lists can be ingressed and are guarded for invalid values (0.02ms)
  * test 64-bit floats can be ingressed and are guarded for invalid values (0.02ms)
  * test 32-bit floats can be ingressed and are guarded for invalid values (0.01ms)
  * test characters can be ingressed and are guarded for invalid values (0.02ms)
  * test bools can be ingressed correctly (0.00ms)
  * test isize can be ingressed correctly (0.00ms)
  * test i64 lists can be ingressed correctly (0.00ms)

ZiglerTest.ReadmeTest
  * test allocations (0.1ms)
  * test example_zig (0.05ms)
  * test zig_collections (0.09ms)

ZiglerTest
  * test sigil-Z2 creates a function of the correct arity (0.05ms)
  * test sigil-Z creates a public function (0.06ms)

ZiglerTest.ZigTest
  * zigtest the truth (0.00ms)

ZiglerTest.ZigFailingTest
  * test if we have a failing test, it can be caught (5.8ms)

ZiglerTest.ZigIndirectTest
  * zigtest function one (0.00ms)

ZiglerTest.ZigDeepTest
  * zigtest function one (0.00ms)

Finished in 31.5 seconds
120 tests, 3 zigtests, 0 failures

Randomized with seed 960707

Which looks perfect to me. It would be nice if zigler knew to use the pre-installed lang/zig port, rather than needing to download stuff.

@dch
Amazing.  It's just so great when software just works.  I'm going to push an 0.1.1 with freebsd support.

I'm afraid that it's been about 10 years since I have used FreeBSD... does "which" work?  Because if it does I'm happy to just use "which" to determine the path of the local zig version, and that ought to work for linux too.

Is there a public CI system for freebsd?  I think elixir now uses Cirrus, which supports it, would be happy to get an account for this project.

FreeBSD has "which".
Unsure on public CI

reviewed the option of using a "local" version of zig.  The executable itself is fine, but I'm unsure of where zig will put its standard library code.  In the tar.gz it lives in lib/.  Dismayingly, in linux, this might not be in a consistent path.  usr/lib/? usr/local/lib?, and it may depend on what packaging system you use.  Will explore further in: https://github.com/ityonemo/zigler/issues/72
implemented freebsd enablement in 7a8fc56252f6e48fcb6f42729016c666edaaa1b


Adding compiled code to Deployment package:

Hi there,
This is an awesome package and using it have been a dream for novice AWS users like me.
Recently I'm trying to deploy a SIFT algorithm package written and compiled in C, namely:
https://github.com/rdguez-mariano/fast_imas_IPOL
The result is a compiled executable, but I'm not sure how to put this executable on PyWren to run, since PyWren packages I assume only python routines.
So I've been thinking of modifying the deployment package that is referred in PyWrenconfig.py, I noticed this deploy.zip is pulled from another account. My question is, can we pull and modify this package? If so, where do we do that?
So this isn't an issue per say but I'm not sure where I can ask the group of people also using PyWren. Here's the information I pulled from Lambda:
PyWrenconfig.py:

PACKAGE_FILE = "deploy.zip"

MEMORY = 512 * 3
TIMEOUT = 300
AWS_ACCOUNT_ID =<PHONE_NUMBER>19
AWS_ROLE = "helloworld_exec_role"

Hi Billy,
We actually have a concept of a "runtime" to account for modules that aren't pure python.
A runtime  is a compressed python installation that contains a prepackaged list of packages (some which include native object code). If you look at .pywren_config you'll see:
runtime:
    s3_bucket: <BUCKET_NAME>
    s3_key: <KEY>

You can download  (which is a JSON file) to see what packages are currently installed in the default runtime. This runtime does contain some C code but packaged in a special compressed way so that the 512 MB disk space restriction on the lambdas isn't a problem.
There is some public code for generating these runtimes yourself (you can put whatever C code you want in there). https://github.com/pywren/runtimes. Unfortunately since we currently only use it as an internal tool its not super well documented.

Hey Billy, did you ever get this to work? If so, could you provide some example code?

I did, but was unable to setup a separate Lamda server running pywren, so what ends up happening is I ran the algorithm sequentially instead. I can't share the code since I'm at a private enterprise, but my algorithm is:
Reduce both original image sizes, get approximate match.
Change transform function to match larger image
transform large image for 1st order match, then cut both images for smaller image chunks
match each image chunck, reduce and save data points
Use spline transform for the matching data points using GDAL
voila, a synchronized image.

Thank you!


add OnBeforeUpdateLines event to "VAT Amount Line".UpdateLines procedure

Describe the request
Hello, could you please add OnBeforeUpdateLines event to "VAT Amount Line "table, with all parameters from UpdateLines procedure + IsHandled parameter + IncludeSender attribute?  Like here:
    procedure UpdateLines(var TotalVATAmount: Decimal; Currency: Record Currency; CurrencyFactor: Decimal; PricesIncludingVAT: Boolean; VATBaseDiscountPercHeader: Decimal; TaxAreaCode: Code[20]; TaxLiable: Boolean; PostingDate: Date)
    var
        PrevVATAmountLine: Record "VAT Amount Line";
        SalesTaxCalculate: Codeunit "Sales Tax Calculate";
        VATBaseDiscountPerc: Decimal;
        IsHandled: Boolean;  // << New Variable
    begin
        // New Code >>
        IsHandled := false;
        OnBeforeUpdateLines(TotalVATAmount, Currency, CurrencyFactor, PricesIncludingVAT, VATBaseDiscountPercHeader, TaxAreaCode, TaxLiable, PostingDate, IsHandled);
        if IsHandled then
            exit;
        // New Code <<
        if FindSet() then
            repeat ..

// New Event >>
    [IntegrationEvent(true, false)]
    procedure OnBeforeUpdateLines(var TotalVATAmount: Decimal; Currency: Record Currency; CurrencyFactor: Decimal; PricesIncludingVAT: Boolean; VATBaseDiscountPercHeader: Decimal; TaxAreaCode: Code[20]; TaxLiable: Boolean; PostingDate: Date; var IsHandled: Boolean)
    begin
    end;
 // New Event <<

Additional context
VATAmountLine.UpdateLines procedure already has 10 events, but for our PTE scenario at least two more events are required. I think it would be better to add an "IsHandled" event with all parameters from the UpdateLines procedure and the IncludeSender attribute, which should cover all possible extensibility scenarios.
Internal work item: AB#556049

Availability update: We will publish a fix for this issue in the next update for release 25.
Build ID to track: 26491.


Shared Variables between decoder and encoder in the basic architecture

@una-dinosauria
Hi,
I congratulate you for this paper being cited multiple times recently,
I am just confused about the basic architecture written in the code, as it was mentioned in the basic form the variables of encoder and decoder are not shared , it means each decoder and encoder have their own variables, but when I checked in the basic architecture the same GRUcell  is used for decoder and encoder, and when I check the number of variables it was as same as the number of variables in "tied" architecture ,
I mean I guess in the basic architecture variables of encoder and decider are not separated??
I would appreciate you if you help me understanding my mistake.
Thanks,

Hi @smakaviani,
Thanks for pointing that out.
Could you please provide a MWE that shows the problem that you mention?
Cheers,

Thank you so much for your quick response,
When I run  basic architecture I got following variables in basic  rnn-scope
<class 'list'>: [<tf.Variable 'Variable:0' shape=() dtype=float32_ref>, <tf.Variable 'Variable_1:0' shape=() dtype=int32_ref>, <tf.Variable 'proj_w_out:0' shape=(1024, 69) dtype=float32_ref>, <tf.Variable 'proj_b_out:0' shape=(69,) dtype=float32_ref>, <tf.Variable 'basic_rnn_seq2seq/rnn/gru_cell/gates/kernel:0' shape=(1093, 2048) dtype=float32_ref>, <tf.Variable 'basic_rnn_seq2seq/rnn/gru_cell/gates/bias:0' shape=(2048,) dtype=float32_ref>, <tf.Variable 'basic_rnn_seq2seq/rnn/gru_cell/candidate/kernel:0' shape=(1093, 1024) dtype=float32_ref>, <tf.Variable 'basic_rnn_seq2seq/rnn/gru_cell/candidate/bias:0' shape=(1024,) dtype=float32_ref>]
and when I run tied architecture  I got following variables
<class 'list'>: [<tf.Variable 'Variable:0' shape=() dtype=float32_ref>, <tf.Variable 'Variable_1:0' shape=() dtype=int32_ref>, <tf.Variable 'proj_w_out:0' shape=(1024, 69) dtype=float32_ref>, <tf.Variable 'proj_b_out:0' shape=(69,) dtype=float32_ref>, <tf.Variable 'combined_tied_rnn_seq2seq/tied_rnn_seq2seq/gru_cell/gates/kernel:0' shape=(1093, 2048) dtype=float32_ref>, <tf.Variable 'combined_tied_rnn_seq2seq/tied_rnn_seq2seq/gru_cell/gates/bias:0' shape=(2048,) dtype=float32_ref>, <tf.Variable 'combined_tied_rnn_seq2seq/tied_rnn_seq2seq/gru_cell/candidate/kernel:0' shape=(1093, 1024) dtype=float32_ref>, <tf.Variable 'combined_tied_rnn_seq2seq/tied_rnn_seq2seq/gru_cell/candidate/bias:0' shape=(1024,) dtype=float32_ref>]
which are not different from the basic one ,from dimension point of view, in spite of my expectation
I can not figure out the difference between tied and untied architecture from the code some how,

Is this in tesorboard? What command do you use? Did you change the code?
Please provide some code I can run to reproduce the error.

No, I have not changed the code, I debug that in pycharm, and after following lines in  seq2seq_model.py
   if architecture == "basic":
      # Basic RNN does not have a loop function in its API, so copying here.
      with vs.variable_scope("basic_rnn_seq2seq"):
        _, enc_state = tf.contrib.rnn.static_rnn(cell, enc_in, dtype=tf.float32) # Encoder
        outputs, self.states = tf.contrib.legacy_seq2seq.rnn_decoder( dec_in, enc_state, cell, loop_function=lf ) # Decoder
    elif architecture == "tied":
      outputs, self.states = tf.contrib.legacy_seq2seq.tied_rnn_seq2seq( enc_in, dec_in, cell, loop_function=lf )
    else:
      raise(ValueError, "Uknown architecture: %s" % architecture )

I use the command of tf.global_variables() command to see variables of architecture.


Check if internal J_cols definition is necessary

See https://github.com/stack-of-tasks/pinocchio/issues/2171

Hi ! This project doesn't usually accept pull requests on the main branch.
If this wasn't intentionnal, you can change the base branch of this PR to devel
(No need to close it for that). Best, a bot.

The quantity J_cols is exploited in the remainings sweeps of the computMinv of the algorithm.


prometheus-adapter: failed querying node metrics

What happened?
when using network policies, I noticed kubernetes dashboard was not showing metrics anymore.
This is caused by traffic being rejected from prometheus-adapter to prometheus-k8s.
this is confimed  by prometheus-adapter logs were the is the following error:
E0521 13:20:03.515525       1 provider.go:272] failed querying node metrics: unable to fetch node CPU metrics: unable to execute query: Get "http://prometheus-k8s.monitoring.svc:9090/api/v1/query?query=sum+by+%28node%29+%28%0A++1+-+irate%28%0A++++node_cpu_seconds_total%7Bmode%3D%22idle%22%7D%5B60s%5D%0A++%29%0A++%2A+on%28namespace%2C+pod%29+group_left%28node%29+%28%0A++++node_namespace_pod%3Akube_pod_info%3A%7Bnode%3D%22ns344288%22%7D%0A++%29%0A%29%0Aor+sum+by+%28node%29+%28%0A++1+-+irate%28%0A++++windows_cpu_time_total%7Bmode%3D%22idle%22%2C+job%3D%22windows-exporter%22%2Cnode%3D%22ns344288%22%7D%5B4m%5D%0A++%29%0A%29%0A&time=1653139173.515": dial tcp <IP_ADDRESS>:9090: i/o timeout

Did you expect to see some different?
the following ingress peer must be added to the NetworkPolicy of prometheus:
  - from:
    - podSelector:
        matchLabels:
          app.kubernetes.io/name: prometheus-adapter
    ports:
    - port: 9090
      protocol: TCP

How to reproduce it (as minimally and precisely as possible):
 (import 'kube-prometheus/main.libsonnet') +
      (import 'kube-prometheus/addons/all-namespaces.libsonnet') +

Environment
k8s 1.24 deployed with kubeadm

Prometheus Operator version:

{
  "alertmanager": "0.24.0",
  "blackboxExporter": "0.20.0",
  "grafana": "8.5.2",
  "kubeStateMetrics": "2.4.2",
  "nodeExporter": "1.3.1",
  "prometheus": "2.35.0",
  "prometheusAdapter": "0.9.1",
  "prometheusOperator": "0.56.2",
  "kubeRbacProxy": "0.12.0",
  "configmapReload": "0.5.0",
  "pyrra": "0.3.4"
}

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.0", GitCommit:"4ce5a8954017644c5420bae81d72b09b735c21f0", GitTreeState:"clean", BuildDate:"2022-05-03T13:46:05Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.0", GitCommit:"4ce5a8954017644c5420bae81d72b09b735c21f0", GitTreeState:"clean", BuildDate:"2022-05-03T13:38:19Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:

kubeadm

Manifests:
?

Prometheus Operator Logs:
no issue with the operator

Prometheus Logs:
no issue with prometheus

Anything else we need to know?:

same problem
prometheus-adapter log
E0914 02:18:28.625558       1 provider.go:284] failed querying node metrics: unable to fetch node CPU metrics: unable to execute query: Get "http://prometheus-k8s.monitoring.svc:9090/api/v1/query?query=sum+by+%28node%29+%28%0A++1+-+irate%28%0A++++node_cpu_seconds_total%7Bmode%3D%22idle%22%7D%5B60s%5D%0A++%29%0A++%2A+on%28namespace%2C+pod%29+group_left%28node%29+%28%0A++++node_namespace_pod%3Akube_pod_info%3A%7Bnode%3D~%22m1%7Cw1%7Cw2%22%7D%0A++%29%0A%29%0Aor+sum+by+%28node%29+%28%0A++1+-+irate%28%0A++++windows_cpu_time_total%7Bmode%3D%22idle%22%2C+job%3D%22windows-exporter%22%2Cnode%3D~%22m1%7Cw1%7Cw2%22%7D%5B4m%5D%0A++%29%0A%29%0A&time=1663121878.624": dial tcp <IP_ADDRESS>:9090: i/o timeout

kubectl top command query failure
$ kubectl get apiservice v1beta1.metrics.k8s.io
NAME                     SERVICE                         AVAILABLE   AGE
v1beta1.metrics.k8s.io   monitoring/prometheus-adapter   True        18h

$ kubectl top node
error: metrics not available yet

$ kubectl top pod -n monitoring
error: Metrics not available for pod monitoring/alertmanager-main-0, age: 18h9m40.422618556s

Was having this issue and was able to resolve it by adding a NetworkPolicy to allow prometheus-adapter to talk to prometheus.
We use calico for netpol, not exactly sure the best way to do this with normal netpol (didn't try), but IMO this definitely should be part of the default policy set.
---
apiVersion: crd.projectcalico.org/v1
kind: NetworkPolicy
metadata:
  name: ingress-prometheus-adapter-to-prometheus
spec:
  serviceAccountSelector: app.kubernetes.io/name == 'prometheus'
  ingress:
    - action: Allow
      protocol: TCP
      source:
        serviceAccounts:
          selector: app.kubernetes.io/name == 'prometheus-adapter'
        namespaceSelector: projectcalico.org/name == 'metrics-system'
      destination:
        ports:
        - 9090

I think this is solved by https://github.com/prometheus-operator/kube-prometheus/pull/1870
As a quick fix here is a network policy that is not calico dependent and can be applied as patch:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  labels:
    app.kubernetes.io/component: prometheus
    app.kubernetes.io/instance: k8s
    app.kubernetes.io/name: prometheus
    app.kubernetes.io/part-of: kube-prometheus
    app.kubernetes.io/version: 2.36.1
  name: prometheus-k8s-adapter
  namespace: monitoring
spec:
  egress:
  - {}
  ingress:
  - from:
    - podSelector:
        matchLabels:
          app.kubernetes.io/name: prometheus-adapter
    ports:
    - port: 9090
      protocol: TCP
  podSelector:
    matchLabels:
      app.kubernetes.io/component: prometheus
      app.kubernetes.io/instance: k8s
      app.kubernetes.io/name: prometheus
      app.kubernetes.io/part-of: kube-prometheus
  policyTypes:
  - Egress
  - Ingress
status: {}

I think this is solved by #1870 As a quick fix here is a network policy that is not calico dependent and can be applied as patch:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  labels:
    app.kubernetes.io/component: prometheus
    app.kubernetes.io/instance: k8s
    app.kubernetes.io/name: prometheus
    app.kubernetes.io/part-of: kube-prometheus
    app.kubernetes.io/version: 2.36.1
  name: prometheus-k8s-adapter
  namespace: monitoring
spec:
  egress:
  - {}
  ingress:
  - from:
    - podSelector:
        matchLabels:
          app.kubernetes.io/name: prometheus-adapter
    ports:
    - port: 9090
      protocol: TCP
  podSelector:
    matchLabels:
      app.kubernetes.io/component: prometheus
      app.kubernetes.io/instance: k8s
      app.kubernetes.io/name: prometheus
      app.kubernetes.io/part-of: kube-prometheus
  policyTypes:
  - Egress
  - Ingress
status: {}

now kubectl top node command can be output normally, but the kubectl top pod command still fails.

I fixed the problem by allowing TCP traffic on port 9090 on each kubernetes node:
# iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 9090 -j ACCEPT

now both commands work for me: kubectl top nodes as well as kubectl top pods -A

I made a PR #1982 to fix this.
for workaround, I resolved this by adding these line into my config (only relevant configs):
local kp =
  (import 'kube-prometheus/main.libsonnet') +
  {
    // ... some other configuration here
    prometheus+:: {
      networkPolicy+: {
        spec+: {
          ingress+: [
            {
              // allow prometheus adapter to access prometheus
              from: [{
                podSelector: {
                  matchLabels: {
                    'app.kubernetes.io/name': 'prometheus-adapter',
                  },
                },
              }],
              ports: [{
                port: 'web',
                protocol: 'TCP',
              }],
            },
          ],
        },
      },
    },
  };


Unable to evaluate mAP scores

Hi, I've just been following along the documentation here: https://imageai.readthedocs.io/en/latest/customdetection/ to try and train a custom object detector.
I've just finished training and now want to evaluate the models. However, I'm just getting outputs like this:

Evaluation samples:  97
Using IoU:  0.5
Using Object Threshold:  0.3
Using Non-Maximum Suppression:  0.5
QIS: 0.0000
mAP: 0.0000
WARNING:tensorflow:No training configuration found in the save file, so the model was not compiled. Compile it manually.

I'm not sure where to go from here and hope I don't have to retrain everything again.

Did you set the JSON path correctly?
The JSON file is in the cache folder created by image ai itself

Yes, I've set the JSON path correctly and can see it in the cache folder

Here is a potential workaround if you are getting an mAP of 0.0 at the evaluation step (and have verified the h5 model and the training/evaluation data is not corrupted):

Flush the workspace cache with: !rm -r .../<name_of_workspace>/cache/
During the evaluation step, ImageAI will recreate this folder along with the .pkl files. Between model training and evaluation, sometimes the file becomes "corrupted", which will give a default mAP of 0.0. Flushing the cache after training resolved this issue every time it occurred for me.