We can still have uncomsumed cache after ledger_catchup fails

While working on this PR https://github.com/CodaProtocol/coda/pull/3251, I had ledger catchup jobs fail. The job failed because I was catching up to a block that is a descendant of a root (which does not make sense at all and I prevent this from happening). When this happens, catchup would fail. As a result, these blocks have not been fully consumed by Cached_lib.Impl.ml. This results in the an thrown exception when the blocks are garbage collected.

After I reviewed how collected_transitions are added to transition frontier, I didn't see how this could possibly happens.
collected_transitions are dumped into primary_transition_pipe, and then Processor would validate the frontier dependencies. During this validation, disconnected transitions would be thrown away. Those should not even be added to cache.

After discussed with John, I am convinced that there still could be leaks.
I also find out the reason why those out-dated transitions got into the catchup-scheduler. It's because in validat_frontier_dependencies, the order of checks are wrong:
      let%bind () =
        Result.ok_if_true
          (Transition_frontier.find frontier parent_hash |> Option.is_some)
          ~error:`Parent_missing_from_frontier
      in
      let%map () =
        (* need pervasive (=) in scope for comparing polymorphic variant *)
        let ( = ) = Pervasives.( = ) in
        Result.ok_if_true
          ( `Take
          = Consensus.Hooks.select
              ~logger:
                (Logger.extend logger
                   [ ( "selection_context"
                     , `String
                         "External_transition.Transition_frontier_validation.validate_frontier_dependencies"
                     ) ])
              ~existing:(Protocol_state.consensus_state root_protocol_state)
              ~candidate:(Protocol_state.consensus_state protocol_state) )
          ~error:`Not_selected_over_frontier_root
      in

The above code is problematic.

@ghost-not-in-the-shell 	move the two lines around now, the cache leak we'll wait on for now

transition_handler.processor is leaking cache. See #3436


feat: run_task_batch stop on first result

@nilspalumbo this implements run_task_batch with option to stop on first result. This can be used to support async-subtasks of a task later.

Thanks, that's a great feature! Should we add an additional function argument to run_task_batch that allows us to terminate at the first valid result? That would be needed for the async subtasks.

an additional function argument to run_task_batch

It's already there -- https://github.com/langroid/langroid/blob/batch-task-early-stop/langroid/agent/batch.py#L153
or did you mean something else?

I mean a Callable argument valid, say, which takes the ChatDocument output which returns whether we should stop (say, we might want to continue if the output is NO_ANSWER). By default, we can just accept all however, which would work the same as the current version.

whether we should stop

Do you mean

(A) valid(..) would take the result of each of the tasks in the async-batch and determine if each is  "done" or should continue running? or
(B) valid(.) would check the overall batch-result (i.e. any non-None result in the group) and determine whether to continue or not?

Letting an individual task in the group "continue" seems like an unclear behavior. After r = task.run() returns some result r, letting it "continue" would mean running task.run(r) ... so I'm confused. Or maybe you mean we take a snapshot of each task's "intermediate" result and determine which ones should stop.

I was thinking that valid would operate on each of the tasks in the batch independently, and we would terminate if any returned True.

Actually I see what you mean  - you mean a valid() criterion similar what we have in task.step() that determines whether the "step" found a valid result... I have to think about that

Yeah that's right, we'd need this for async subtasks.

The batch processing functions now continue until some non-None output is returned; they all now return list[Optional[U]]. The _do_task function now optionally returns the index (avoiding the list.index(future) operation). Additionally added exception handling to the stop_on_first_result branch and fixed a minibatch bug.
The typing updates are however, a bit messy; for instance, we always return a list[U] without stop_on_first_result but we must explicitly cast at each use as mypy cannot infer this.

When I update (just pushed) the test_task_gen_batch to have sleep(10) in task 0 and task 2 (so the middle case 1 is fastest), I see two problems:

the total time taken is longer, i.e. is dependent on sleep(10) whereas I expected it to be as fast as the fastest task 2 , which doesn't have a sleep.
the task 0 finishes, and task 1 and 2 don't.

So something is still wrong with the implementation.

Also, note on the exception handling for the stop_on_first_result case: asyncio.wait does not have a handle_exceptions option, so we cannot independently handle exceptions between multiple tasks (the results of a successful task may be lost if another task in the minibatch raises an exception).

Fixed the exception handling issue for stop_on_fiirst_result

@nilspalumbo that specific test_task_gen_batch still fails so there's something we're missing -- the implementation doesn't seem to be able to get what we expect to be the fastest task result. Or maybe it has something to do with test itself, i.e. MockLM.achat not being truly async (though the test fails even if I add a await asyncio.sleep(0.1).

I added support for aresponse_fn_async  to MockLM and updated the test to use it, it should work as expected now. Note though that the expected behavior with batching is that the fastest task in the first minibatch, not the fastest task overall, should finish.

it should work as expected now

Excellent, thanks!

the fastest task in the first minibatch, not the fastest task overall, should finish.

That's right. So I guess if users want the behavior of "get the first result out of k tasks", then they shouldn't batch the tasks (i.e. choose batch size >= k)?

Yeah, that's how it'll work by default; the behavior should be intuitive enough, but it is the only case where batching would be expected to affect the output.


Overhaul Dictionary Documentation

Continuation of especially https://github.com/godotengine/godot/pull/69451 and https://github.com/godotengine/godot/pull/68838...

Made the wording match how other classes are documented a lot more closely;

Made use of [param] and several other strong references more often;

Changed words where it felt necessary, where they could be mistaken for another concept of Godot's API, where technical terms are more appropriate. For example:

"key/value pair" -> "entry".

I've most commonly seen people referring to a Dictionary's element as an "entry". Discussions are welcome, please.

Modified examples extensively, with the main goal to improve readability and variety:

Removed quotes around results when they could be misunderstood as strings (# Prints "5" -> # Prints 5);
Improved consistency all around;
Added extra padding before comments.
Avoid overly long lines.

COMPLETELY stripped away the part about Dictionary comparisons and hashes from the leading description.

Way to give nausea to users at first sight. Not that Dictionaries themselves are compared THAT much anyhow. Sheesh...

Updated Dictionary(from) constructor's description to be correct.

This is temporary. It's not something desired, and should either be modified to work as intended (copy), or removed. See https://github.com/godotengine/godot/pull/69117.

Feedback is very, very welcome.

I should've left it as a draft as I also wanted to revamp the leading description. It's better to merge it ASAP though I suppose.

Updated. Also added a small instruction on how to iterate a dictionary in the leading description, because if I didn't I would've later felt guilty about it.

Updated. Also added a small instruction on how to iterate a dictionary in the leading description, because if I didn't I would've later felt guilty about it.

Thank you very much for the feedback

Thanks!


fix: resetWidget merged

Description
Fixes # (issue)
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.

Test A
Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

As the PR which was supposed to be merged is closed. Hence closing this too https://github.com/appsmithorg/appsmith/pull/14661


Add Token authentication

Ability to use a more specific Authentication token for authentication with Cloudflare, as per https://developers.cloudflare.com/analytics/graphql-api/getting-started/authentication/api-token-auth/. Next also make it more flexible by having it configurable to use either API TOKEN or the Global API Key.

This would be awesome as this is the only cloudflare dashboard that's makes sense.


Heading menu dropdown is not fully visible on small editor views

This PR will fix the problem with hidden overflow , I tested it and everything looks fine but I’m not sure if there will be any other side-effects.

Ok so
It seems you misunderstood the problem. The issue is that if the div container the editor has a limited height, the headings menu is cut off. Media queries are not relevant here since it has nothing to do with screen size.

Ok so It seems you misunderstood the problem. The issue is that if the div container the editor has a limited height, the headings menu is cut off. Media queries are not relevant here since it has nothing to do with screen size.

@abeforgit as we agreed, the solution here was to remove overflow: hidden from main container. Please have a look in your spare time.


Problem mapping jj to activate-command-mode

Mapping 'jj' to escape is pretty common when using vim.
If 'jj' is mapped to activate-command-mode, then 'jj' will enter command mode, but it's no longer possible to type a single 'j' when in INSERT mode.
I'm using this mapping:
'.vim-mode.insert-mode:not(.mini)':
  'j j': 'vim-mode:activate-command-mode'

init.coffee
atom.commands.add 'atom-text-editor', 'custom:wait-key-press', (e)->
  oe = e.originalEvent
  char = String.fromCharCode(oe.which)
  char = char.toLowerCase() unless oe.shift
  atom.workspace.getActivePaneItem().insertText(char)

keymap.cson
'atom-text-editor.vim-mode.insert-mode':
  'j': 'custom:wait-key-press'

'.vim-mode.insert-mode:not(.mini)':
  'j j': 'vim-mode:activate-command-mode'

worked for me , atom version 0.207.0

Works for me too! Doesn't work in version 0.206.0, so make sure you're fully updated if you're trying this out.

liyaodong's solution worked for me as well! Thanks :+1:

Worked for me as well! (Version 1.0.2)

I'm 1.8.0, i use
'atom-text-editor.vim-mode.insert-mode':
  'j': 'custom:wait-key-press'

'.vim-mode.insert-mode:not(.mini)':
  'j j': 'vim-mode:reset-normal-mode'


Handle string_view dereference nullptr

https://github.com/stephenberry/glaze/issues/335
The second issue is when string_view dereference nullptr of unset char* and similar.

You shouldn't need to return a const reference. Instead, just return by decltype(auto) or just by value and the optimizer should handle it just fine.

But if I return by value the string_view will point to R-value and will dispose the std::string right after assignment.

Since the value is valid outside the lambda it is ok to return reference to r-value. I think we need to suppress this error in gcc.

Don't return a std::string from the lambda. Instead do this:

const sv str = [&]() -> sv {
                     if constexpr (std::is_pointer_v<std::decay_t<T>>) {
                        if (value == nullptr) {
                           return "");
                        }
                     }

                     return value;
                  }();

About the code, it gets to the constexpr when the type is a pointer.
I had to bypass the compiler assumption that reference can't be null error: the compiler can assume that the address of ‘value’ will never be NULL.

Thanks! I'll try to look over this fix soon.

@maor-da Can you provide a test case for what you're trying to do? You can't write to a char* buffer without memory already being allocated. We probably should guard against this with Glaze, but Glaze lets you do some dangerous things for those who handle their own memory.

@maor-da Can you provide a test case for what you are trying to accomplish?

Thanks for your changes, I think I'm going to alter the constexpr logic to only check for nullptr when writing a char* and not a char[]. I can update this pull request.

Okay, I took some of your changes here and used them in a separate pull request #340. I changed around some of the concepts and type handling so that I could compile time switch on char array types and avoid the gcc warning as well as reduce runtime overhead of the check. Let me know if this fixes your active issue.


The deployment, as written, depends on an installed keylime instance where the deployer runs

That is clearly suboptimal, although it is not an impossible requirement. @maugustosilva commented that the generation of TLS secrets requires keylime, and no one of sane mind will want to reproduce that code outside keylime just to decouple the dependency.
At least two thoughts arose during the discussion -- (a) the secret generation is trivial boilerplate operations with openssl and could probably be implemented with 3 lines of bash. (b) we could use a dockerized kubernetes instance to run, either as a job with a service account, or as an init container, to generate the secret. Either way, the generation of the secret would be done as part of the deployment rather than offline in the deployer script.

fixed by PR #8


Use GitHub App for codeowner validation and remove hacky script

We shouldn't use personal access tokens, instead we created a GitHub App with read-only access to just this repository.
While codeowners-validator supports GitHub App authentication, the same cannot be said for the hacky script I wrote because there was no support for checking write access: https://github.com/mszostok/codeowners-validator/issues/157
Instead of trying to hack the script more to make it work with GitHub App authentication, I decided to implement it into codeowners-validator itself: https://github.com/mszostok/codeowners-validator/pull/222
Because it's not merged/released yet, we need to build it ourselves, so I added some Nix to do that reproducibly.
Testing this in https://github.com/NixOS/org/pull/9

We can't make CI pass here because it uses the base branch's workflow file, which doesn't use GitHub Apps yet.
However I tested this in a separate PR where I can confirm that it works: https://github.com/NixOS/org/pull/9


can i get the details Stack Trace of the Exception of failed Thread

HI Team
can i get the Stack Trace details of Exception in pin point dashboard for tomcat ?

Hi @manojr2k
It is a function that I think it would be good to develop, but pinpoint does not yet provide such a function.
However, if you use the following function to classify logs by request, it will be helpful to find the error log.

https://pinpoint-apm.gitbook.io/pinpoint/documents/per-request_feature_guide


Error parsing empty response body

Hi there !
I ran into this exception : A JSON text must at least contain two octets! which happens on this line in your code :
message = !!(result.body) ? JSON.parse(result.body).fetch('errors').pop.fetch('message') : 'Sendgrid API Error'
as apparently, some 401 responses from Sendgrid have an empty body...
Moreover, I ran into another 401 saying :
Sendgrid delivery failed with 401 Could not authenticate
but when I tried again the same operation with the same key it got through... does that ring any bell ?
Anyway thanks for the great work :)

Hi @davydav, that's odd. !!(result.body) should catch an empty body.  That line was added in #61 to address this exact problem.  Can you confirm you are on version 3.0.0?

Yes I am, but I'm also on an old ruby 2.3.1 / rails <IP_ADDRESS>, maybe that's the issue ?

Possibly? 3.0.0 requires Mail 2.7 as a dependency.  You could try locking sendgrid-actionmailer to version 2.6.0 and see if that resolves the issue.

Did some digging, as you can see !!(result.body) returns true in the case of an empty string. Is that behaviour different for you ?
Again, not to worry, just wanted to let you know :) thanks again !

hmrph, ok. !(response.body.empty?) it is.
Version bump to 3.0.1.  Should resolve this issue. Thanks for digging.

I'm going to close this. Let me know if you have any additional problems.


Few typos on the docs - missing prefix "ADT"

the docs sometimes miss "adt" in the command or example
Expected Behavior

The command should match the doc title
Current Behavior

Possible Solution

Steps to Reproduce

https://github.com/mjr4077au/PSAppDeployToolkit.WinGet/blob/master/docs/Find-ADTWinGetPackage.mdx
Example shows: Find-WinGetPackage -Id Microsoft.PowerShell
https://github.com/mjr4077au/PSAppDeployToolkit.WinGet/blob/master/docs/Install-ADTWinGetPackage.mdx
Example shows:  Install-WinGetPackage -Id Microsoft.PowerShell
https://github.com/mjr4077au/PSAppDeployToolkit.WinGet/blob/master/docs/Uninstall-ADTWinGetPackage.mdx
Example shows:  Uninstall-WinGetPackage -Id Microsoft.PowerShell
https://github.com/mjr4077au/PSAppDeployToolkit.WinGet/blob/master/docs/Update-ADTWinGetPackage.mdx
Example shows:  Update-WinGetPackage -Id Microsoft.PowerShell
Context (Environment)

Operating System and version as reported by $PSVersionTable.OS:
PowerShell versions as reported by $PSVersionTable.PSEdition:

Detailed Description

Thanks for the report! This is fixed in https://github.com/mjr4077au/PSAppDeployToolkit.WinGet/commit/66a2d2b3a15e0bb93f30e8aa9eac051ff66c05c8, and is now in the newly released 1.0.0 final.


log=True in processor.swim() stalls the execution

I noticed that when I turn on the flag log=True while calling processor.swim() in a jupyter notebook, the code seems to run the PSO and the MCMC, but then stalls, and I have to force quit the kernel.
I tested it both on my data and on the basic example lens_system1 provided in the dolphin repo.
Since when I try to stop the execution the kernel crashes, I was not able to see the error dump and I cannot tell what caused it.
I am using the latest commit dolphin 12c5859. I have not tested it running within a .py file.
Example with log=False:

Example with log=True:

Hi @Ferr013, thanks a lot for reporting the issue. First of all, the log=True was not meant to be used in a notebook. Notebooks already have the outputs being printed out underneath a cell. The intended production mode of use for dolphin is to be run from a script on an HPC; in that case, the print-outs are saved in a log file with log=True.  Notebooks can of course be used for interactive testing of the features and for post-processing of the outputs.
Now, making log=True with notebooks can take a little work around: https://stackoverflow.com/questions/66739794/jupyter-lab-running-cell-forever-with-file-close-print-and-sys-stdout. Making this possible directly from within dolphin is not at the top of my priority list, but you are more than welcome to implement it if you need this feature ASAP.
For now, I will add in the documentation of log that it should not be set True when running from a notebook.

The documentation has been updated with #50.


Show ascii spinner / waiting animation while fuzzing

We should somehow inform the user that the fuzzer is fuzzing. While not is passive mode (i.e. woke fuzz --passive) we should print a message like Fuzzing... with an ASCII spinner (https://stackoverflow.com/questions/2685435/cooler-ascii-spinners). Maybe, we could also use indeterminate progress from rich library https://rich.readthedocs.io/en/stable/progress.html#indeterminate-progress.

Implemented in #108


test: Add an IndexedClient for testing that uses custom FieldIndexers

Fixes #
Description

Adds an IndexedClient for tests that use a custom FieldIndexer

How was this change tested?
make presubmit
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

40 of 73 (54.79%)  changed or added relevant lines in 4 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 76.873%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/utils/machine/machine.go
0
1
0.0%

pkg/test/nodes.go
0
3
0.0%

pkg/test/environment.go
26
30
86.67%

pkg/test/expectations/expectations.go
14
39
35.9%

Files with Coverage Reduction
New Missed Lines
%

pkg/test/environment.go
3
85.11%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
5714

Relevant Lines:
7433

💛  - Coveralls

Closing in favor of #145


Player page

@CodiumAI-Agent /review

PR Review

 ⏱ Estimated effort to review [1-5]
4, due to the large amount of code across multiple files and technologies (React, Node.js, MongoDB), the review requires a thorough understanding of frontend and backend integration, state management in React, and database operations. The complexity of the code, especially with the use of external libraries like axios, Swiper, and Auth0, adds to the review effort. Additionally, the security implications of handling user authentication and database connections need careful consideration.

 🧪 Relevant tests
No

 🔍 Possible issues

Possible Bug: The comparison team1_short == "CSK" uses == instead of ===, which might lead to unexpected type coercion issues. It's recommended to use strict equality checks.

Performance Concern: Fetching all players and then filtering on the client side could be inefficient for large datasets. Consider filtering on the server side.

Redundant Code: There's a significant amount of commented-out code that should be removed if it's not being used, to improve code readability and maintainability.
 🔒 Security concerns
Sensitive information exposure: The MongoDB connection string is hardcoded with credentials in the server file. This should be moved to environment variables to avoid exposing sensitive information.

 Code feedback:
relevant fileclient/src/components/data/Player.jsx
suggestion

Use strict equality checks (===) instead of loose equality checks (==) to avoid type coercion bugs. [important]

relevant lineif (team1_short == "CSK") {
relevant fileserver/index.js
suggestion

Move sensitive information like the MongoDB connection string to environment variables to avoid exposing credentials in the codebase. [important]

relevant lineconst urii = 'mongodb+srv://dev326patil:devrajcapstone326@capstone.riouq2l.mongodb.net/?retryWrites=true&w=majority&appName=Capstone';
relevant fileclient/src/components/data/Player.jsx
suggestion

Consider using a mapping object for team short codes to their respective values to simplify the if-else chain and improve code readability. [medium]

relevant lineif (team1_short == "CSK") {
relevant fileserver/index.js
suggestion

Use asynchronous middleware for Express routes to handle errors more effectively and avoid unhandled promise rejections. [medium]

relevant lineapp.get('/', async (req,res)=>{

 ✨ Review tool usage guide:
Overview:
The review tool scans the PR code changes, and generates a PR review which includes several types of feedbacks, such as possible PR issues, security threats and relevant test in the PR. More feedbacks can be added by configuring the tool.
The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.

When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

See the review usage page for a comprehensive guide on using this tool.


single-node: localhost port forward daemon sketch

This is an idea to make working with the single-node cluster easier. The basic idea would be to have something like kubectl port-forward that forwards every nodePort to localhost based on the original targetPort. So, for example:
# User does something like this
$ kubectl run --image quay.io/philips/golang-outyet outyet
$ kubectl expose deployment outyet --target-port=8080 --port=8080 --type=NodePort

# This is the part that needs automating:
$ socat tcp-listen:8080,reuseaddr,fork tcp:<IP_ADDRESS>:$(kubectl get service outyet -o template --template="{{range.spec.ports}}{{.nodePort}}{{end}}")

This would be a huge boon to people trying to use kubernetes as a development workflow for running caches, services, etc and developing against those APIs.
Psuedo code event loop:
for {
  for _, e := range kubernetesServiceEvent() {
    if e == newNodePort {
      go proxy(context, e.NodePort, e.NodeIP, "localhost", e.TargetIP)
    }
    if e == dyingNodePort {
      contexts[e.NodePort].Done()
    }
  }
}

I may be missing the motivation, but the nodePort services are available on the host (albeit not via localhost).
For example, in the single-node install the default IP given to the vm is <IP_ADDRESS>. If you launch the guestbook example using a nodePort type service (lets say it gets assigned port 32000) it would be available from your host machine via: curl http://<IP_ADDRESS>:32000

Seems to me like this would let you treat local containers in development as though they had been deployed into a pod on the cluster.

@oaojesse another idea would be to use a VPN or something. Then you could access all services and DNS as well.

The direction I had in mind for minikube was similar to what @aaronlevy pointed out above, in a local single node cluster all nodePort services will be available on the host IP. What if we provided a DNS name via /etc/hosts or similar to that IP? Then it could be as simple as:
curl http://mini.kube:32000
localhost definitely has advantages though. It would be a lot more familiar to most users. It might also come with disadvantages though, we'd have to worry about port collisions more and it would make local multi-cluster harder.

Thanks for the idea @philips I'll look into that. Hopefully something useful comes out of it.

Looks like someone has openvpn for k8s: https://github.com/offlinehacker/openvpn-k8s. If someone can try it out and report back that would be great. I will try to get to it in the next few days.

cc @offlinehacker

I'm trying this out today. Hopefully I can get the crypto figured out.

@philips @offlinehacker
Well I got openvpn-k8s running on a cluster on GCP. I was able to figure out the crypto and the vpn all seems to be working. My public IP appears in Mountain View and I can poke services on their cluster IP from my laptop.
I'm not able to use DNS service names yet (despite rebuilding the openvpn-k8s container from alpine:edge which fixes a DNS bug).
I expect that I don't understand enough about how kubernetes DNS works yet and I would love a hand if anyone has the time.

Got DNS working this morning, by copying /etc/resolv.conf out of a container in a pod and mounting it into a container running locally while connected to the VPN.
$ kubectl exec existing-pod cat /etc/resolv.conf > resolv.conf
$ docker run -it --rm -v `pwd`/resolv.conf:/etc/resolv.conf alpine:edge /bin/ash
/ # nslookup kubernetes
nslookup: can't resolve '(null)': Name does not resolve

Name:      kubernetes
Address 1: <IP_ADDRESS>

Everything seems to work great!

Hi, i'm glad my openvpn k8s image was helpfull, i haven't used it for some period, as we are now using pritunl, instead of pure openvpn. For dns to work you need to set OVPN_K8S_DNS to ip address of kube-dns service(first entry in /etc/resolv.conf) and then openvpn will push dns configuration. You still need a client that can set dns, like network manager on linux or tunnelblick on osx.

Alternative way would be to use something like https://github.com/apenwarr/sshuttle or pptp.

Yes thank you. It's working great with tunnelblick. I'll play around with getting openvpn to push dns down as that would be nice.


[#120584573] fix user expiration date

Coverage remained the same at 100.0% when pulling 61bb408a389e1588da2b8e33f0a28b04503c9290 on alemata.120584573.fix_expiration_date into dad591a9118cab9ca148793b9d9d99bb63cecd49 on master.

Coverage remained the same at 100.0% when pulling 65be7d6972054c811bf14972b902c0056956887d on alemata.120584573.fix_expiration_date into dad591a9118cab9ca148793b9d9d99bb63cecd49 on master.


no filesystem diff found for different images

Readme says:

container-diff is a tool for analyzing and comparing container images. container-diff can examine images along several different criteria, including:

Docker Image History
Image file system
...

But when I run:
 ./container-diff-darwin-amd64 diff daemon://golang:1.9-alpine daemon://golang:1.8-alpine

I actually don't get an "image filesystem diff"

-----Apt-----

Packages found only in golang:1.9-alpine: None

Packages found only in golang:1.8-alpine: None

Version differences: None

I actually expected to see something like git status diff output saying these are the files that are in image A, and not in B (or vice versa) and here are the files that are different between two images.
This tool does not seem to be doing this. So maybe the statement about "Image file system" diffing should be removed.

The default diff type is just "apt", maybe we should change that or clarify the docs. If you pass
--type=file it should give you the type of output you're looking for.

My bad, I should've read the documentation better.

Thanks for trying the tool! We disabled the file differ by default because it can be very verbose on larger images with lots of changes, but maybe we should make it more clear.


IPython notebook: SVG support

Gogs version (or commit ref): <IP_ADDRESS>2
Git version:
Operating system: Docker image
Database (use [x]):

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

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

[x] Yes: https://try.gogs.io/rubenv/ipython-notebook-svg/src/master/prob-01.ipynb
[ ] No
[ ] Not relevant

Log gist (usually found in log/gogs.log): none

Description
Hi! I'm super pleasantly surprised to see that IPython notebooks are rendered. That's totally awesome and unexpected.
It seems that rendering SVG files is currently missing:

This should be rather trivial to add, as the SVG file is embedded in the notebook file.
Sample file attached.
prob-01.zip

Looks like a bug in notebookjs: https://github.com/jsvine/notebookjs/pull/14
Sent a PR that should fix things.

@Unknwon Patch to notebookjs has landed, now we just need to update the bundled copy in gogs to 0.3.0.

PR #5084 submitted

Patch has pushed to fix this issue, please test on develop branch or https://try.gogs.io/rubenv/ipython-notebook-svg/src/master/prob-01.ipynb.

Looks exactly what it should look like, thanks for merging!


hello_world and nimbix/jarvice

Hello,
I am trying to compile the hello_world example in Nimbix following instructions https://alveo.readthedocs.io/en/latest/vitis/.
To my surprise the compilation with
TMP_WORK_DIR=$(mktemp -d) && make -C /data/Vitis_Accel_Examples/hello_world all BUILD_DIR=${TMP_WORK_DIR} TARGET=hw DEVICE=xilinx_u200_xdma_201830_2 && cp ${TMP_WORK_DIR}/*.xclbin /data/Vitis_Accel_Examples/hello_world
I get :
INFO: [v++ 204-61] Option 'relax_ii_for_timing' is enabled, will increase II to preserve clock frequency constraints.
ERROR: [v++ 200-61] /data/Vitis_Accel_Examples/hello_world/src/vadd.cpp:100: unsupported memory access on variable 'in1' which is (or contains) an array with unknown size at compile time.
ERROR: [v++ 200-70] Synthesizability check failed.
ERROR: [v++ 60-300] Failed to build kernel(ip) vadd, see log for details: /data/Vitis_Accel_Examples/hello_world/_x.hw.xilinx_u200_xdma_201830_2/vadd/vadd/vivado_hls.log
ERROR: [v++ 60-599] Kernel compilation failed to complete
ERROR: [v++ 60-592] Failed to finish compilation
Is there a problem with this simple example  in Nimbix?
I tried also with the kmeans example but it also failed with a different error:
ERROR: [CF2BD 82-34] cf_xsd: Failed to generate design file: dr.bd.tcl
ERROR: [SYSTEM_LINK 82-36] [07:24:19] cf2bd failed
Time (s): cpu = 00:00:02 ; elapsed = 00:00:02 . Memory (MB): peak = 180.418 ; gain = 0.000 ; free physical = 63829 ; free virtual = 196380
ERROR: [SYSTEM_LINK 82-61] Error generating design file dr.bd.tcl
ERROR: [SYSTEM_LINK 82-80] Unable to create top-level block diagram
INFO: [v++ 60-1442] [07:24:19] Run run_link: Step system_link: Failed
Time (s): cpu = 00:00:11 ; elapsed = 00:00:13 . Memory (MB): peak = 561.820 ; gain = 0.000 ; free physical = 63848 ; free virtual = 196399
ERROR: [v++ 60-661] v++ link run 'run_link' failed
ERROR: [v++ 60-626] Kernel link failed to complete
ERROR: [v++ 60-703] Failed to finish linking
Makefile:115: recipe for target '/tmp/tmp.FzMt2iMNkW/krnl_kmeans.xclbin' failed
make: *** [/tmp/tmp.FzMt2iMNkW/krnl_kmeans.xclbin] Error 1
make: Leaving directory '/data/Vitis_Accel_Examples/demo/kmeans'

I think the issue may be related to the Vitis version. In 2019.2, Vivado HLS was used by default. In Vitis 2020.1, Vitis-HLS is used by default. Pragmas have change from one version to another, the master is for Vitis 2020.1. If you are using Vitis 2019.2 checkout to the 2019.2 tag and try again.

OK, thanks,
That must be it. I missed that part.

From: Mario Ruiz<EMAIL_ADDRESS>Sent: 14 July 2020 22:32
To: Xilinx/Vitis_Accel_Examples<EMAIL_ADDRESS>Cc: Jose Nunez-Yanez<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Xilinx/Vitis_Accel_Examples] hello_world and nimbix/jarvice (#13)
I think the issue may be related to the Vitis version. In 2019.2, Vivado HLS was used by default. In Vitis 2020.1, Vitis-HLS is used by default. Pragmas have change from one version to another, the master is for Vitis 2020.1. If you are using Vitis 2019.2 checkout to the 2019.2 tag and try again.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Xilinx/Vitis_Accel_Examples/issues/13#issuecomment-658424671, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIFWTCAFIITEON5XD2C4VMLR3TFILANCNFSM4OPSQYRQ.

closing this as issue is resolved as per last comment.


Any processMessages type functionality

From @NathanaelA on January 1, 2016 2:45
Ok, so I'm starting up my application and I'm doing a lots of file, database and raw data processing on startup and once it is all done I switch to the main screen from the startup progress screen.   However, even though I am updating the status label and progress bar; you do NOT see any of the changes because of course the main thread has been so busy doing all its work that it never actually had a chance to pass control back down to the android layer apparently to update the screen.  (I haven't tried this on iOS yet)    Since we don't have background thread ability yet; Is their any way I can force the android runtime to run and update the screen or do I have to split everything up into really small functions that I can then use setTimeout's so that their is a break between each one?
Copied from original issue: NativeScript/NativeScript#1315

From @x4080 on January 1, 2016 3:35
What if the background process using native android library?

From @NathanaelA on January 2, 2016 17:21
I'm pretty sure a feature to force the runtimes to update the screen (or actually suspend the JS runtimes and make the Android/iOS handle their message loops) is something that doesn't exist; but I figured it couldn't hurt to ask.
@x4080 Having a background thread (which also would solve this, is bug report #85 ); as you can see  many people have commented on it.   I'm hoping that more people will +1 it so that it will become the top issue.  :grinning:

From @x4080 on January 1, 2016 9:25
Yea actually i suggested that sonehow there is 2nd javascript in the background it will be very helpful

From @NathanaelA on January 1, 2016 4:26
Actually, I might have to go that way in the future since it is so intensive.  But for the prototype I'd rather not write Java and ObjectiveC code if I don't have too.   :-)
So in the meantime, in all my exploring I haven't seen anything like this; but there might be a feature somewhere deep in the Runtimes that will allow me to push out of the JS VM back into the Android NDK/Java level and get the screen updated...

From @x4080 on January 3, 2016 11:47
Actually i wrote the last comment there :)

Just for anyone following in my footsteps; at least on Android I have to do this:
var page;
exports.navigatedTo = function(args) {
   page = args.object;
   setTimeout(startProcessing, 0);
};

function startProcessing() {
  // get progressbar & label objects
  // Do major processing
  process.processMessages();
 // Do major processing.
  process.processMessages();
 // ...
}

The initial setTimeout is required; because apparently the screen/activity hasn't fully been displayed or and/or the activity messageloop hasn't been primed or something -- Not sure what it is.
The process.processMessages() is the function I modified from @atanasovg suggestions and it will show up in my opensource nativescript-master-technology plugin when I have a chance to release it.
And yes it is a very hacky way of doing it; but based on everything I've researched and messing with several variations of the code; I think it is the only way to do it from JS currently.
The better solution for this feature would be to add a synchronous processMessages function to the runtime that would leave the vm; post a NS_RESUME_VM message to the end of the messageloop. And then drop into the message loop to allow all the message loop messages to be handled; once that message is received it jumps back into the vm as if returning from the processMessages function.  Sounds simple enough, but I haven't played with either runtimes message loop code so I couldn't really say.

I used this for a while; but I didn't really like the hackiness of it; and came up with an alternative solution for my case.   All my "busy" code is now in promises.  When a promise is resolved in that then() I call a function that does the screen updates which itself returns a promise;
so I can do:
DoBusyWork.then(updateScreen('Now Working'))
.then(DoMoreBusyWork)
.then(updateScreen('More work accomplished'))
.then(DoEvenMoreBusyWork)
.then(updateScreen('Wow More done...').
.then(done)

@N3ll this can probably be closed now.


website for application using webflow, must have content info for reporting content and terms of service.

simple 1-page site with app screenshots, blurbs about app and mission, links to  Privacy Policy, terms of service, contact info for Objectionable Content and or bugs.

[ ] Home content/text
[ ] App screenshots
[ ] Privacy Policy
[ ] Terms of service
[ ] Contact info for Objectionable Content and or bugs

Got it deployed to netlify https://eloquent-wozniak-44d709.netlify.app/
Started some basic layout stuff


Windows Touch Support

Currently, if you try to scroll in synctrayzor with you touchscreen, you mark the text instead of scrolling.

Duplicate of #286, #241, (and see also #129).
The bottom line is that the embedded browser doesn't support touch scrolling, so there's nothing I can do.


[ToDo] Add Wattage calculation to resistorcolor.c and/or resistance.c

So:
Typical values for a 1/2 watt or 1/4 watt resistor (typical/common sizes) refer to their power ratings and the current or voltage they can safely handle without overheating. The power rating of a resistor indicates how much power it can dissipate in the form of heat. This is calculated using the formula ( P = I^2R ) where ( P ) is power in watts, ( I ) is current in amperes, and ( R ) is resistance in ohms.
For a 1/4 watt resistor, the maximum current ( I_{1/4W} ) can be calculated by rearranging the formula to:

 ( I = \sqrt{\frac{P}{R}} ), and substituting ( P = 0.25 ) watts.

 So the maximum current for a 1/4 watt resistor is ( \sqrt{\frac{0.25}{R}} ) amps.

For a 1/2 watt resistor, the maximum current ( I_{1/2W} ) is ( \sqrt{\frac{0.5}{R}} ) amps.

Using these formulas, we can calculate the maximum current a resistor can handle based on its power rating and resistance value.
For example, if you have a 100-ohm resistor:
The maximum current for a 1/4 watt resistor would be ( \sqrt{\frac{0.25}{100\Omega}} = 50\ mA )
The maximum current for a 1/2 watt resistor would be ( \sqrt{\frac{0.5}{100\Omega}} = 100\ mA )

HI @gbowne1, Hi Gregory
As an electromechanical engineer, this topic suits me very well. Can I please contribute to this issue?
Best regards,
Koen

yes you can contribute if you wish. I can assign you to this if you like.
thanks @bloemenk

I have created a pull request. I have build up both functions to calculate the maximum current allowed based on a given wattage and resistance. Please let me know if this is not what you want.
regards,
Koen


MenuBar is opened by call OpenMenu even it's disabled.

Describe the bug
If a MenuBar is disabled it can't be activated either by mouse, keyboard, method or anything that can open a menu bar.
To Reproduce
Steps to reproduce the behavior:

Go to 'MenuBar' scenario
Click on 'Toggle Menu.Enable' button
Click on 'Open Menu' button
MenuBar is opened and it shouldn't

Expected behavior
MenuBar only must could open if it's enabled, right?

I think this is fixed in some of the preliminary work I've done on reworking events.
I'd suggest waiting on this one until that work can move forward, to avoid duplicating effort there.

My fix is in the OpenMenu method. Do you remember how you fixed it? Was an issue opened for this?
	/// <summary>
	///         Opens the Menu programatically, as though the F9 key were pressed.
	/// </summary>
	public void OpenMenu ()
	{
		var mbar = GetMouseGrabViewInstance (this);
		if (mbar != null) {
			mbar.CleanUp ();
		}

		if (!Enabled || _openMenu != null) {
			return;
		}

		_selected = 0;
		SetNeedsDisplay ();

		_previousFocused = SuperView == null ? Application.Current.Focused : SuperView.Focused;
		OpenMenu (_selected);
		if (!SelectEnabledItem (openCurrentMenu.BarItems.Children, openCurrentMenu._currentChild,
			    out openCurrentMenu._currentChild) && !CloseMenu (false)) {
			return;
		}

		if (!openCurrentMenu.CheckSubMenu ()) {
			return;
		}

		Application.GrabMouse (this);
	}

The thing about the work on the events is that it touches almost everything. So, as a side effect of that, methods like that one end up getting touched, usually in simple ways like that.
I don't know if there's ever been an issue for that specific problem. 🤷♂
Since the event overhaul is global, though, I didn't really have any intention of filing issues for each class or method affected, because it would be over 100 issues if I did. 🤷♂
#3209 is the master issue for that, but is mostly stalled until we get #3212 finished up.

I will commit it only to being possible I finish the PR #3181.

Coolio. Even if there's overlap, it's not a problem. I'll deal with conflicts as the happen. Just a heads up to save you time if you come across any others like that, as well.

Closing this because it was already merged onto #3181 and #3192.


Create a "ipptool --ippserver" ippserver attribute text files pool for developing/debugging

With the command
ipptool --ippserver attrs.txt ipp://... get-printer-attributes.test

an IPP attributes file from the printer with the given URI can be generated which allows emulating this printer with the `ippserver' utility.
For developers of client software (print dialogs, PPD generatoes, ...) it would be great to have a pool of such files for as many printers as possible so that they can test the support for all functionality of IPP printers by simply emulating different models with different features.
The pool could be made part of this ippsample software package.
If manufacturers do not like to publish their printer's capability list files they could, if they prefer it, anonymise them by removing make/model info.

Hey,
I just read out this attribute file my printer HP Color LaserJet M254nw.
./ipptool --ippserver attrs.txt ipp://NPI2EEE6B.local:631/ipp/print ../examples/get-printer-attributes.test
HP Color LaserJet M254nw.attr.txt

Hey, another one.
This is from a Samsung M283.
Samsung M283x Series.txt
Curious fact:

When you call lpinfo -v this printer will not produce an ipp uri. Only socket and dnssd but not the ipp which is certainly supported. The last (HP) printer returned that flawlessly.

dnssd://Samsung%20M283x%20Series%20(SEC8425192A70C2)._printer._tcp.local/
socket://<IP_ADDRESS>

The attribute file is shorter. Some of the info within the HP file is here missing. Like the collection media-size-supported .

Glade has published binary Get-Printer-Attributes responses from various printers.
For code quality tests I decode and encode again all 261 ipp messages and compare the bytes.
Another approach could be to provide a simple script that uploads printer and job attributes to a public ipp-printer-database.

@gmuth There are some privacy issues we need to address for this (printer attributes often contain personally identifying information) and the linked files don't include the printer resource files (icons and strings files) that would also be needed to fully impersonate a particular printer. But thank you for the link, might be useful as a starting point at least...

I like the direction this is moving but I agree with Mike that there are some privacy issues to be resolved. There also may be some "mechanical" issues to resolve as well, since a large repository of .conf files living in a "print" sub-directory to all be loaded b ippserver gets increasingly awkward as the number of .conf files grows.

I've written a jvm-based tool inspectprinter.sh that runs a few ipp operations and saves the ipp responses. Anyone can fork the github repository ipp-samples, run the tool, commit and push new ipp files and create a pull request. If you like the approach I'd be happy to support a shared effort. If you see privacy issues we could use a private repository.


Refs #24928 -- Added introspection support for PostgreSQL JSONField

Could maybe be documented in the django.contrib.postgres docs? inspectdb is typically run on day one of a project, they might not be aware they need to edit INSTALLED_APPS first to get JSONField support.

You're right in that people inspecting a legacy db may not know in advance that a contrib.postgres supported field is present. I'm afraid that putting a note inside django.contrib.postgres docs may not be very helpful in that regard.
What about a hint inside the inspectdb output, so instead of 'This field type is a guess.', people read 'This field type is a guess. You may try adding 'django.contrib.postgresql' in your INSTALLED_APPS setting.? This would however also favor a bit contrib.postgresql over third-party packages.

"This field is a guess. It may be supported by contrib or third party apps." ?

Tentative doc addition.

It merits a release note for django.contrib.postgres also:
* ``inspectdb`` can now introspect  ``JSONField`` (``django.contrib.postgres``
  must be in ``INSTALLED_APPS``).

See #9049 for RangeField.


have included file tag also use subdomains

Any link in an include file will currently add /site/projectname to the url. Fix this.

fixed


Branch assign fix bug

fixes #179

Codecov Report

Merging #180 (78f0d86) into master (44bcbd3) will decrease coverage by 0.18%.
The diff coverage is 22.22%.

@@             Coverage Diff              @@
##             master     #180      +/-   ##
============================================
- Coverage     59.62%   59.43%   -0.19%
  Complexity      537      537
============================================
  Files           106      106
  Lines          2130     2135       +5
  Branches        233      233
============================================
- Hits           1270     1269       -1
- Misses          782      789       +7
+ Partials         78       77       -1

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

.../java/seedu/address/logic/commands/AddCommand.java
66.66% <ø> (ø)

...a/seedu/address/logic/commands/AddTaskCommand.java
0.00% <0.00%> (ø)

...java/seedu/address/logic/commands/ExitCommand.java
100.00% <ø> (ø)

...in/java/seedu/address/storage/JsonAdaptedTask.java
0.00% <0.00%> (ø)

...eedu/address/storage/JsonSerializableTaskList.java
30.76% <0.00%> (ø)

.../seedu/address/logic/commands/EditTaskCommand.java
85.29% <100.00%> (-0.22%)
:arrow_down:

.../seedu/address/logic/commands/ListTaskCommand.java
78.57% <100.00%> (ø)

...java/seedu/address/logic/commands/ViewCommand.java
88.88% <100.00%> (+8.88%)
:arrow_up:

Continue to review full report at Codecov.

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


Does it perform static checks?

I've taken the first example from http://flowtype.org/docs/five-simple-examples.html and it compiles down to
/***/ function(module, exports) {

	'use strict';

	function foo(x) {
	    return x * 10;
	}

	foo('Hello, world!');

/***/ },

without any error messages in webpack watch log.
Whereas the second example from that page compiles as
/***/ function(module, exports) {

	'use strict';

	function foo(x, y) {
	    var _ref;

	    if (typeof x !== 'string') throw new TypeError('Value of argument \'x\' violates contract, expected string got ' + (x === null ? 'null' : x instanceof Object && x.constructor ? x.constructor.name : typeof x));
	    if (typeof y !== 'number') throw new TypeError('Value of argument \'y\' violates contract, expected number got ' + (y === null ? 'null' : y instanceof Object && y.constructor ? y.constructor.name : typeof y));
	    _ref = x.length * y;
	    if (typeof _ref !== 'string') throw new TypeError('Function \'foo\' return value violates contract, expected string got ' + (_ref === null ? 'null' : _ref instanceof Object && _ref.constructor ? _ref.constructor.name : typeof _ref));
	    return _ref;
	}

	foo('Hello', 42);

/***/ },

which is expected.
Does it mean the plugin does not perform static checks?

@zerkms it does some static checks but it's not intended as a replacement for flow, rather a companion to it. We don't do type inference, and we don't check callsites because the current babel API rather limits our ability to do it usefully. If you don't annotate a function with type information, we don't modify the function at all.
It'll currently refuse to compile cases like this, where we know the return value definitely violates the contract:
function foo (): string {
  if (true) {
    return "foo"; // ok
  }
  else {
    return false; // SyntaxError
  }
}

Given your example, if we change it to:
function foo (x: string): string {
  return x * 10;
}

We'll get a runtime type error but it's not yet clever enough to do it at compile time. It's trivial to add so I'll leave this issue open until that gets fixed.

I see. For some reason I thought it internally uses flow, but it's just another implementation for the same syntax.
Thanks.


Paging support in reader

Fixes
Issue #67 #77
Description
Allows to:

read from file partially, specifying offset and count
DataSet has extra property for getting total amount of rows in addition to actual amount of rows
Writer supports row groups which is set to 5000 by default (I needed this to test that paging works across row groups, bonus feature!)
Fixed a bug in reader which caused only last row group to be read

Todos

[x] unit/integration tests
[x] documentation

Thanks, I'll look to implement this in Parq


Crash on extracting file metadata ?

Steps to reproduce

scroll to a file

as soon as I scroll to a file it crashes
Recording
https://asciinema.org/a/81KQsPft4xzJWG7n60OtPQdnb
Crash log
https://app.warp.dev/block/153s5U7AxEtlvWIyqSTcmI

This is weird. I can't reproduce this bug on my computer.
Are u using mac?

i can reproduce this
this is something even I am encountering.
I am using mac

where have you defined et?

in function.go file

im on linux( nixos )

Ok so I found out what the problem was. The go package requires exiftool.

Does that need to be found in path

Thanks

Thanks for your report!


This is a text area. It can be resized using the resize handle at the bottom right of the field.

The website has been updated to automatically resize the textarea when needed.


i18n(ko-KR): update astro-components.mdx

Description (required)

update astro-components.mdx
Related issues & labels (optional)

Closes #
Suggested label:

Thanks! Reviewed with the Astro Docs checklist!


Unable to localize results descriptions

We should have a way of localizing "Locality in France" or "Venue in France" label under each result title IMO.
See screenshot for an example.

Thanks for bringing this up @toniopelo (and sorry for not noticing this and your other PR; something is up with my GitHub email notifications)!
I'm also quite interested to improve the localization. Let's try to specify the desired outcomes a bit better.
First, under what conditions does the subtext change? My suggestion would be that this is dependent on the user's browser (Accept-Language headers, specifically). So if, say, my device is set to prefer French, it would show some text in French.
Second, we are not entirely satisfied with the "Venue in France" style of representing things to be completely honest. These terms are rather specific to the API schema, which is itself based on Who's on First placetypes, but these terms don't actually mean anything to the average user. We have considered replacing these "place type" qualifiers with a simplified set of icons.
So, one way we could simplify things (and avoid having to localize a technical string that isn't going to be that useful to most end users anyways) is to have the subtext line just be like " France" (or, for an example where the English name is different, " Deutschland"). This would definitely result in showing less information, but I think there is probably a balance to be found. Do you have any thoughts on this?


Add reachability should run configuration

Overview
There are multiple requests to disable internet reachability check. The proposed solution is to add a reachabilityShouldRun option to configure. This new option accepts a function that returns a boolean. This boolean flag will be used in the _setExpectsConnection function to determine whether _checkInternetReachability should be called.
Proposed Solution Reference: https://github.com/react-native-netinfo/react-native-netinfo/issues/178#issuecomment-804454938
Test Plan
New set of unit tests are added to check if reachabilityShouldRun option is working correctly in both NetInfo.addEventListener and NetInfo.fetch.
Fixes: #178 #380 #440

This may have a testing issue, I had to cancel the previous run:

Fri, 05 Nov 2021 13:32:57 GMT Test Suites: 6 passed, 6 total
Fri, 05 Nov 2021 13:32:57 GMT Tests:       81 passed, 81 total
Fri, 05 Nov 2021 13:32:57 GMT Snapshots:   0 total
Fri, 05 Nov 2021 13:32:57 GMT Time:        13.545 s
Fri, 05 Nov 2021 13:32:57 GMT Ran all test suites matching /\/src\//i in 3 projects.
Fri, 05 Nov 2021 13:32:58 GMT Jest did not exit one second after the test run has completed.
Fri, 05 Nov 2021 13:32:58 GMT
Fri, 05 Nov 2021 13:32:58 GMT This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.
Fri, 05 Nov 2021 13:50:56 GMT Error: The operation was canceled.

Note the timestamps, it was sitting for 18 minutes where normally it's almost immediate

I think I have found the issue. It was the setTimeout in internetReachability.ts scheduling another _checkInternetReachability and cause jest to wait indefinitely. The fix is to use jest.useFakeTimers() to mock setTimeout so no more _checkInternetReachability will be scheduled.

:tada: This PR is included in version 6.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


await in a python lambda

I just stumbled upon this:
https://stackoverflow.com/a/66330279/674447
Maybe that could be helpful?

Thanks, I'll add it to the documentation!

Hi @cleder,
I finally decided against referencing the answer in the docs. I also added an additional answer to that StackOverflow question -- is there a glaring bit I am missing there?
I also updated the documentation on async conditions in icontract: https://icontract.readthedocs.io/en/latest/async.html#special-considerations
There are also two new functions I added to asyncstdlib 3.9.1 (https://github.com/maxfischer2781/asyncstdlib/releases/tag/v3.9.1) which hopefully alleviate the issues with lack of async lambdas.
Please let me know if you'd like me to expand on it more, or point me to what I am missing as I don't use async that much.


Add theme saving

Saves the current theme into preferences.json on exit. I'll update the tests next time I guess.

Codecov Report

Merging #118 (11ac01d) into master (75dbe5c) will increase coverage by 0.02%.
The diff coverage is 60.00%.

@@             Coverage Diff              @@
##             master     #118      +/-   ##
============================================
+ Coverage     56.16%   56.18%   +0.02%
- Complexity      535      536       +1
============================================
  Files           103      103
  Lines          2044     2052       +8
  Branches        201      202       +1
============================================
+ Hits           1148     1153       +5
- Misses          829      831       +2
- Partials         67       68       +1

Impacted Files
Coverage Δ

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

...n/java/seedu/address/commons/core/GuiSettings.java
69.69% <75.00%> (+0.46%)
:arrow_up:

...u/address/logic/commands/AddMembershipCommand.java
77.77% <0.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Hot Module Replacement doesn't notice when a symlink is changed

What is the current behavior?
We symlink our node_modules directory and change the symlink when we update node_modules. When the directory is changes HMR doesn't detect that something has changed.
If the current behavior is a bug, please provide the steps to reproduce.
Setup HMR referencing a file with the parent directory symlinked. Change the symlink to a different directory with a modified version of the file.
What is the expected behavior?
HMR should detect that files have changed. Currently does not.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Linux Ubuntu.

@webpack-bot move to webpack/watchpack


Decisions don't show up in meeting minutes.

Created a decision during the meeting, when refreshed the meeting the decision disappeared. Should be optionally linked to the minutes

decided not to link to minutes. should be fixed. to confirm on live server.

decided to link to minutes, resolved


Files not copied over into container

Firstly, I'd like to say that I am using "docker compose" instead of "docker-compose" (I ammended the Makefile), I am not sure that is the problem though.
After I run make build && make start, all the containers start ok, however the only files that are copied over are docker/dev/init-db.sql and the storage/mysql-data folder, resulting in a 404 from nginx (i am guessing because of the missing files).
I am running Linux Ubuntu 22.04, Docker 4.17.0, docker compose v2.16.0.
Any ideas on how to solve this would be greatly appreciated, thanks!

Hello
Please try to use next docker-compose.yml path mapping:
1)Nginx - ./:/var/www/html:ro,cached
2)Laravel - ./:/var/www/html:cached
And inform us if it helps

Hi, thanks for the swift response, but no, this doesn't seem to have any effect.
Although, I found that if I set
1)Nginx - ./:/var/www/html/random-folder:ro,cached
2)Laravel - ./:/var/www/html/random-folder:cached
then all the files are copied in the /html folder (supposedly correctly so + correct permissions according to Dockerfile, www-data:www-data) + html/random-folder/docker (root:root) + html/random-folder/mysql-data(root:root) in the Laravel container, but still the same as before in the nginx container (root:root).
I am not quite sure what to make of this, or how to get around it..

First of all please follow recommendations from the docker-compose Team - https://github.com/docker/compose/issues/9814
Make sure that you don't have other changes on your local docker-nginx-php-laravel
Please provide more info about the error that you have now

I followed everything I could find, but the only thing that helped eventually was to go in Docker Desktop, in resources and manually add /var/www/html as a folder sharing location. This solved the problem of files not getting copied over.
I still can't run make composer-install (I can composer install inside the container) or make env-dev (but I can cp .env.dev .env inside the container). Even After I do that I get a 502 from Nginx. The permissions also don't seem to be correct, everything is root:root.
I run the same thing on my work mac and it just took 10 minutes to download everything but is working out of the box as intended. This has definitely something to do with Linux permissions, so I guess this issue can be closed as it was about file sharing between host and containers.


Remove unneeded and invalid attribute constructor

Hi there @breyed – thanks for the PR. I'm checking in to whether or not this is actually necessary, and why. Will respond back when I find out. Thanks a bunch for calling it out!

Hi @breyed – I checked with the engineering team on this, and evidently this isn't necessary. Thanks for calling it out.


Check anvil and mending repairs for custom tools

Mending repairs were already fixed, and I can't manage to reproduce anvil repair issues. Since the original reporter is unresponsive, I'm closing this issue (for now).


chore: bump deps to pick up security fixes

Fixes #7316

Description of what you did:

My PR is a:

[ ] 💥 Breaking change
[x] 🐛 Bug fix
[ ] 💅 Enhancement
[ ] 🚀 New feature

Please confirm that your PR fulfills these requirements

[x] Multiple commits are squashed into one commit.
[x] The commit message follows Conventional Commits, which allows us to autogenerate release notes; e.g. fix(plugins/plugin-k8s): fixed annoying bugs
[x] All npm dependencies are pinned.

/lgtm


FairyGUI problems with text update

axmol version: d6781284a5b2d9b21d3f98334a93a37cb49f55e3
devices test on: all
developing environments

NDK version: r23c
Xcode version: 14.2+
Visual Studio:

VS version: 2022 (17.9+)
MSVC version: 19.39+
Windows SDK version: 10.0.22621.0+

cmake version: 3.28.1
Steps to Reproduce:

Create a FairGUI GTextField element with any custom font and a simple text, example "test"
Change the text of GTextField in runtime with characters that is not in original text, example "text"

BEFORE CHANGE TEXT

AFTER CHANGE TEXT

The letter "x" that is not in design mode don't appear when new text have it.
Code:
auto lbMessage = dynamic_cast<fairygui::GTextField *>(getContentPane()->getChild("lbMessage"));
lbMessage->setText("text");

What is wrong?

What is wrong?

Have you followed it with a debugger to narrow down where the issue is occurring?

Sure. Im try debug but i don't understand why it is cutting the chars that is not in the original text. I read all the source code, step by step with debug, but don't make sense to me.

The steps is:
void GBasicTextField::setTextFieldText()
{
    if (_templateVars != nullptr)
        _label->setText(parseTemplate(_text.c_str()));
    else
        _label->setText(_text);
}

That call FUILabel.cpp setText:
void FUILabel::setText(std::string_view value)
{
    if (_fontSize < 0)
        applyTextFormat();

    setString(value);
}

That call core/2d/Label.cpp method setString:
void Label::setString(std::string_view text)
{
    if (text.compare(_utf8Text))
    {
        _utf8Text     = text;
        _contentDirty = true;

        std::u32string utf32String;
        if (StringUtils::UTF8ToUTF32(_utf8Text, utf32String))
        {
            _utf32Text = utf32String;
        }
    }
}

And when i changed the text, it set the new string, "text" in my sample, without problems:

Don't appear be nothing specific with FairyGUI, since it use Axmol Label.

Don't appear be nothing specific with FairyGUI, since it use Axmol Label.

Have you tested the same font with an ax::Label to see if it has the same issue?  If it does not have an issue, then you should compare the behaviour of a standard ax::Label with that of the one used by FairyGUI.  Follow it in the debugger to the construction of the texture from the text itself, and you should be able to spot the difference.

Hi, sure. Is this I'm doing, but without success. I'm debugging but do not discover the problem.

Hi,
I think that there is wrong in my current project, because i create another sample with FairyGUI and axmol Label, and both works fine :(
https://github.com/paulocoutinhox/fairygui-bug

In test project it works on both devices.
In my real project it have problems on Android only:

I solve the problems settings correct resolution in design resolution and the text problems is related to threads, because i call JNI somethings and it don't render when come from JNI call (i dont know why, but i call on callback the method runInAxmolThread). Thanks.


Support BigInt64Array/BigUint64Array

Add support for typed arrays of 64-bit integers (BigInt) now available
in many browsers. Without this patch these typed arrays were given the
"generic" dtype, which then attempted to use getters and setters rather
than indexing, causing an error since typed arrays do not provide these.
These changes are compatible with browsers that do not have these 64-bit
typed arrays.
Simple tests are included.

Pinging to see if there's anything I can do to move this towards merging, e.g., more tests. Thanks!

This PR passes and looks pretty good to me, though I haven't followed the progress of bigint too closely. Does bigint64 make more sense than int64 (and uint64)? Perhaps so since usage is more subtle than int32 vs int64. Other than that, it seems reasonable to me.
Seems similar modules like typedarray-pool and dtype might need similar updates.
Pinging /cc @mikolalysenko for a second opinion.

While I personally like the consistency of int64/uint64, for whatever reason the standards committees settled on the BigInt naming scheme for the types and typedarrays, so I think having the strings here consistent with the typedarray prefixes makes the most sense.
My goal is to get this downstream to numjs (since that's the functionality I need for my use). I'm not very familiar with the scijs ecosystem. It looks like I may need to make a PR for typedarray-pool, but I don't see a dependency path through dtype.

Sounds good! The only question I have is about the official status of bigint is. Is it officially in the spec such that it's appropriate to build on it? Is chrome the spec these days?
And yes, sorry, I didn't mean those were dependencies, just that they were analogous modules in the same general ecosystem that should talk coherently about types. I've created a quick PR here for typedarray-pool: https://github.com/rreusser/typedarray-pool/tree/bigint-support

BigInt status:
The spec has been in stage 3 for 2 years.  Chrome follows the spec. Consequently it's also in V8/Node since 10.4 (last June).
Firefox is strangely a straggler, but has been moving quickly recently, largely because the rust-wasm ecosystem (which is closely tied up with Firefox) uses BigInt heavily (wasm supports 64 bit integers). Last I checked, BigInt is available behind a flag in FF, but the typedarrays are a few releases away. Note that the MDN page doesn't even have the "experimental technology" warning banner that you find elsewhere. In general I would characterize the perception as wasm becoming production implies BigInt support.
It's also been in Opera for a year or so, making 3 people very happy I'm sure.

And thanks for the typedarray-pool patch!

PRified here: https://github.com/mikolalysenko/typedarray-pool/pull/8/files


Enhancement request: Build a Directed Acyclic Graph

Dear Atif Hassan,
Many thanks for making available this package!
I read with great interest your publication, and I noticed that Pylmpetus report a complete Markov Blanket (parents, children, spouses) in a single run! Other algorithms require at least two runs to get such Markov Blanket (https://cran.r-project.org/web/packages/MXM/vignettes/MMPC_tutorial.html).
I would like to submit the following enhancements that I believe can help to facilitate the interpretation of the Markov Blanket:

Be able to recognize from selected features which ones are either parents, children, or spouses
Have a functionality to build a Directed Acyclic Graph (as shown in this R package https://github.com/malcolmbarrett/ggdag)

In the Directed Acyclic Graph, the nodes corresponding to parents have a specific color, which in turn it is different to the color assigned to either children or spouses. The remaining of features not belonging to Markov Blanket their nodes are plotted without color.
Kind regards,
Ivan

Hi Ivan!
I think these are great ideas! Due to the property of the Markov Blanket, we know that the final selected set of features comprise only of the parent, child and spouses of the target variable. Even though, I have provided a feature importance generation technique, it is not possible to understand which nodes are the parent, child and spouse. Hence, your suggestions will definitely add to the interpretability of this work.

Hi Atif Hassan,
Many thanks for paying attention to my request! I am looking forward for the addition of this new functionalities.
Kind regards,
Ivan


[OIS] Bug: System reset during commissioning

Some CI tests failed because of an issue in the lock-app integration test.
It looks like the application restarted for an unknown reason:
-------------------------------- live log call ---------------------------------
14:40:26.358   INFO   <--|FVPdev| [WRN] TFM_DUMMY_PROVISIONING is not suitable for production! This device is NOT SECURE
14:40:26.582   INFO   <--|FVPdev| [INF] [-] Secure firmware version: 1.6.1-0
14:40:26.584   INFO   <--|FVPdev|
14:40:26.593   INFO   <--|FVPdev| [INF] [-] Non-secure firmware version: 0.0.1-0
14:40:26.603   INFO   <--|FVPdev|
14:40:26.723   INFO   <--|FVPdev| [INF] [-] Open IoT SDK lock-app example application start
14:40:27.778   INFO   <--|FVPdev| [INF] [DL] Got IP address on interface: en1 IP: FE80::202:F7FF:FEEF:25F0
14:40:27.790   INFO   <--|FVPdev| [INF] [DL] Got IP address on interface: lo0 IP: ::1
14:40:27.805   INFO   <--|FVPdev| [INF] [DL] Got IP address on interface: lo0 IP: <IP_ADDRESS>
14:40:27.817   INFO   <--|FVPdev| [INF] [SVR] Server initializing...
14:40:27.828   INFO   <--|FVPdev| [INF] [TS] Last Known Good Time: [unknown]
14:40:27.850   INFO   <--|FVPdev| [INF] [TS] Setting Last Known Good Time to firmware build time 2023-01-16T14:33:13
14:40:27.951   INFO   <--|FVPdev| [INF] [DMG] AccessControl: initializing
14:40:27.963   INFO   <--|FVPdev| [INF] [DMG] Examples::AccessControlDelegate::Init
14:40:27.973   INFO   <--|FVPdev| [INF] [DMG] AccessControl: setting
14:40:27.983   INFO   <--|FVPdev| [INF] [DMG] DefaultAclStorage: initializing
14:40:27.996   INFO   <--|FVPdev| [INF] [DMG] DefaultAclStorage: 0 entries loaded
14:40:28.292   INFO   <--|FVPdev| [INF] [ZCL] Using ZAP configuration...
14:40:28.314   INFO   <--|FVPdev| [INF] [DMG] AccessControlCluster: initializing
14:40:28.326   INFO   <--|FVPdev| [INF] [ZCL] Initiating Admin Commissioning cluster.
14:40:28.342   INFO   <--|FVPdev| [INF] [ZCL] Door Lock server initialized
14:40:28.449   INFO   <--|FVPdev| [INF] [ZCL] Door Lock cluster initialized at endpoint #1
14:40:28.555   INFO   <--|FVPdev| [INF] [ZCL] Door Lock attribute changed
14:40:28.595   INFO   <--|FVPdev| [INF] [ZCL] Initialized new lock door endpoint [id=1,users=10,credentials=10,weekDaySchedulesPerUser=10,yearDaySchedulesPerUser=10,numberOfCredentialsSupportedPerUser=5]
14:40:28.617   INFO   <--|FVPdev| [INF] [DIS] Updating services using commissioning mode 1
14:40:28.632   INFO   <--|FVPdev| [INF] [DIS] CHIP minimal mDNS started advertising.
14:40:28.652   INFO   <--|FVPdev| [ERR] [DIS] Failed to get primary mac address of device. Generating a random one.
14:40:28.681   INFO   <--|FVPdev| [INF] [DIS] Advertise commission parameter vendorID=65521 productID=32769 discriminator=3840/15 cm=1
14:40:28.705   INFO   <--|FVPdev| [INF] [DIS] CHIP minimal mDNS configured as 'Commissionable node device'; instance name: A7DD013C1D703CF4.
14:40:28.727   INFO   <--|FVPdev| [INF] [DIS] mDNS service published: _matterc._udp
14:40:28.740   INFO   <--|FVPdev| [INF] [DIS] Updating services using commissioning mode 1
14:40:28.752   INFO   <--|FVPdev| [INF] [DIS] CHIP minimal mDNS started advertising.
14:40:28.779   INFO   <--|FVPdev| [ERR] [DIS] Failed to get primary mac address of device. Generating a random one.
14:40:28.800   INFO   <--|FVPdev| [INF] [DIS] Advertise commission parameter vendorID=65521 productID=32769 discriminator=3840/15 cm=1
14:40:28.823   INFO   <--|FVPdev| [INF] [DIS] CHIP minimal mDNS configured as 'Commissionable node device'; instance name: A7DD013C1D703CF4.
14:40:28.839   INFO   <--|FVPdev| [INF] [DIS] mDNS service published: _matterc._udp
14:40:28.853   INFO   <--|FVPdev| [INF] [IN] CASE Server enabling CASE session setups
14:40:28.867   INFO   <--|FVPdev| [INF] [SVR] Joining Multicast groups
14:40:28.876   INFO   <--|FVPdev| [INF] [SVR] Server Listening...
14:40:28.885   INFO   <--|FVPdev| [INF] [DL] Device Configuration:
14:40:28.894   INFO   <--|FVPdev| [INF] [DL]   Serial Number: TEST_SN
14:40:28.903   INFO   <--|FVPdev| [INF] [DL]   Vendor Id: 65521 (0xFFF1)
14:40:28.914   INFO   <--|FVPdev| [INF] [DL]   Product Id: 32769 (0x8001)
14:40:28.923   INFO   <--|FVPdev| [INF] [DL]   Hardware Version: 0
14:40:28.937   INFO   <--|FVPdev| [INF] [DL]   Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
14:40:28.954   INFO   <--|FVPdev| [INF] [DL]   Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
14:40:28.964   INFO   <--|FVPdev| [INF] [DL]   Manufacturing Date: (not set)
14:40:28.978   INFO   <--|FVPdev| [INF] [DL]   Device Type: 65535 (0xFFFF)
14:40:28.990   INFO   <--|FVPdev| [INF] [SVR] SetupQRCode: [MT:-24J0AFN00KA0648G00]
14:40:28.991   INFO   Attempting to find device on network
14:40:29.027   INFO   <--|FVPdev| [INF] [SVR] Copy/paste the below URL in a browser to see the QR Code:
14:40:29.049   INFO   <--|FVPdev| [INF] [SVR] https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0AFN00KA0648G00
14:40:29.061   INFO   <--|FVPdev| [INF] [SVR] Manual pairing code: [34970112332]
14:40:29.073   INFO   <--|FVPdev| [INF] [-] Open IoT SDK lock-app example application run
14:40:29.140   INFO   <--|FVPdev| [INF] [EM] >>> [E:3724r M:165826192] (U) Msg RX from 0:C5FF7DB4B5FA1FD0 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
14:40:29.169   INFO   <--|FVPdev| [INF] [EM] <<< [E:3724r M:174889717 (Ack:165826192)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
14:40:29.190   INFO   <--|FVPdev| [INF] [IN] (U) Sending msg 174889717 to IP address 'UDP:[FE80::1CBC:B4FF:FEE7:25F0%en1]:39504'
14:40:29.230   INFO   <--|FVPdev| [INF] [EM] <<< [E:3724r M:174889718 (Ack:165826192)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
14:40:29.[252](https://github.com/ARM-software/connectedhomeip/actions/runs/3931215828/jobs/6722192659#step:13:253)   INFO   <--|FVPdev| [INF] [IN] (U) Sending msg 174889718 to IP address 'UDP:[FE80::1CBC:B4FF:FEE7:25F0%en1]:39504'
14:40:29.265   INFO   <--|FVPdev| [ERR] [DL] Long dispatch time: 179 ms, for event type 3
14:40:29.294   INFO   <--|FVPdev| [INF] [EM] >>> [E:3724r M:165826193 (Ack:174889718)] (U) Msg RX from 0:C5FF7DB4B5FA1FD0 [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
14:40:29.323   INFO   <--|FVPdev| [INF] [EM] <<< [E:3724r M:174889719 (Ack:165826193)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
14:40:29.343   INFO   <--|FVPdev| [INF] [IN] (U) Sending msg 174889719 to IP address 'UDP:[FE80::1CBC:B4FF:FEE7:25F0%en1]:39504'
14:40:30.144   INFO   <--|FVPdev| [INF] [EM] <<< [E:3724r M:174889720 (Ack:165826193)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:23 (SecureChannel:PASE_Pake2)
14:40:30.165   INFO   <--|FVPdev| [INF] [IN] (U) Sending msg 174889720 to IP address 'UDP:[FE80::1CBC:B4FF:FEE7:25F0%en1]:39504'
14:40:30.179   INFO   <--|FVPdev| [ERR] [DL] Long dispatch time: 1417 ms, for event type 3
14:40:30.209   INFO   <--|FVPdev| [INF] [EM] >>> [E:3724r M:165826194 (Ack:174889720)] (U) Msg RX from 0:C5FF7DB4B5FA1FD0 [0000] --- Type 0000:24 (SecureChannel:PASE_Pake3)
14:40:30.238   INFO   <--|FVPdev| [INF] [EM] <<< [E:3724r M:174889721 (Ack:165826194)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
14:40:30.258   INFO   <--|FVPdev| [INF] [IN] (U) Sending msg 174889721 to IP address 'UDP:[FE80::1CBC:B4FF:FEE7:25F0%en1]:39504'
14:40:30.290   INFO   <--|FVPdev| [INF] [EM] <<< [E:3724r M:174889722 (Ack:165826194)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
14:40:30.311   INFO   <--|FVPdev| [INF] [IN] (U) Sending msg 174889722 to IP address 'UDP:[FE80::1CBC:B4FF:FEE7:25F0%en1]:39504'
14:40:30.336   INFO   <--|FVPdev| [INF] [SC] SecureSession[0x21001350]: Moving from state 'kEstablishing' --> 'kActive'
14:40:30.351   INFO   <--|FVPdev| [INF] [SVR] Commissioning completed session establishment step
14:40:30.364   INFO   <--|FVPdev| [INF] [DIS] Updating services using commissioning mode 0
14:40:30.375   INFO   <--|FVPdev| [INF] [DIS] CHIP minimal mDNS started advertising.
14:40:30.395   INFO   <--|FVPdev| [INF] [SVR] Device completed Rendezvous process
14:40:30.412   INFO   <--|FVPdev| [ERR] [DL] Long dispatch time: 290 ms, for event type 3
14:40:30.440   INFO   <--|FVPdev| [INF] [EM] >>> [E:3725r M:207006122] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
14:40:30.482   INFO   <--|FVPdev| [INF] [EM] >>> [E:3724r M:165826195 (Ack:174889722)] (U) Msg RX from 0:C5FF7DB4B5FA1FD0 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
14:40:30.610   INFO   <--|FVPdev| [INF] [EM] <<< [E:3725r M:191552179 (Ack:207006122)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
14:40:30.626   INFO   <--|FVPdev| [INF] [IN] (S) Sending msg 191552179 on secure session with LSID: 9203
[1673880030.627562][59520:59541] CHIP:CTL: ----- NetworkCommissioning Features: has Thread. endpointid = 0
[1673880030.628103][59520:59541] CHIP:CTL: Successfully finished commissioning step 'ReadCommissioningInfo'
[1673880030.628556][59520:59541] CHIP:CTL: Commissioning stage next step: 'ReadCommissioningInfo' -> 'ArmFailSafe'
[1673880030.628995][59520:59541] CHIP:CTL: Performing next commissioning step 'ArmFailSafe'
[1673880030.629403][59520:59541] CHIP:CTL: Arming failsafe (60 seconds)
[1673880030.629897][59520:59541] CHIP:EM: <<< [E:3726i M:207006123] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
[1673880030.630383][59520:59541] CHIP:IN: (S) Sending msg 207006123 on secure session with LSID: 32733
[1673880030.630907][59520:59541] CHIP:EM: <<< [E:3725i M:207006124 (Ack:191552179)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1673880030.631396][59520:59541] CHIP:IN: (S) Sending msg 207006124 on secure session with LSID: 32733
14:40:30.642   INFO   <--|FVPdev| [ERR] [DL] Long dispatch time: 145 ms, for event type 3
14:40:30.668   INFO   <--|FVPdev| [INF] [EM] >>> [E:3726r M:207006123] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
14:40:30.688   INFO   <--|FVPdev| [INF] [FS] GeneralCommissioning: Received ArmFailSafe (60s)
14:40:30.718   INFO   <--|FVPdev| [INF] [EM] <<< [E:3726r M:191552180 (Ack:207006123)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
14:40:30.734   INFO   <--|FVPdev| [INF] [IN] (S) Sending msg 191552180 on secure session with LSID: 9203
14:40:30.748   INFO   <--|FVPdev| [ERR] [DL] Long dispatch time: 119 ms, for event type 3
14:40:30.777   INFO   <--|FVPdev| [INF] [EM] >>> [E:3725r M:207006124 (Ack:191552179)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
14:40:30.803   INFO   <--|FVPdev| [INF] [EM] >>> [E:3727r M:207006125] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
14:40:31.029   INFO   <--|FVPdev| [INF] [EM] <<< [E:3727r M:191552181 (Ack:207006125)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
14:40:31.045   INFO   <--|FVPdev| [INF] [IN] (S) Sending msg 191552181 on secure session with LSID: 9203
[1673880031.046532][59520:59541] CHIP:EM: <<< [E:3728i M:207006127] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
[1673880031.047030][59520:59541] CHIP:IN: (S) Sending msg 207006127 on secure session with LSID: 32733
[1673880031.047609][59520:59541] CHIP:EM: <<< [E:3727i M:207006128 (Ack:191552181)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1673880031.048121][59520:59541] CHIP:IN: (S) Sending msg 207006128 on secure session with LSID: 32733
14:40:31.059   INFO   <--|FVPdev| [ERR] [DL] Long dispatch time: 276 ms, for event type 3
14:40:31.088   INFO   <--|FVPdev| [INF] [EM] >>> [E:3726r M:207006126 (Ack:191552180)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
14:40:31.114   INFO   <--|FVPdev| [INF] [EM] >>> [E:3728r M:207006127] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
14:40:31.130   INFO   <--|FVPdev| [INF] [ZCL] OpCreds: Certificate Chain request received for PAI
14:40:31.162   INFO   <--|FVPdev| [INF] [EM] <<< [E:3728r M:191552182 (Ack:207006127)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
[1673880031.177405][59520:59541] CHIP:EM: >>> [E:3728i M:191552182 (Ack:207006127)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
14:40:31.177   INFO   <--|FVPdev| [INF] [IN] (S) Sending msg 191552182 on secure session with LSID: 9203
[1673880031.177523][59520:59541] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0003
[1673880031.177538][59520:59541] CHIP:CTL: Received certificate chain from the device
[1673880031.177550][59520:59541] CHIP:CTL: Successfully finished commissioning step 'SendPAICertificateRequest'
[1673880031.177557][59520:59541] CHIP:CTL: Commissioning stage next step: 'SendPAICertificateRequest' -> 'SendDACCertificateRequest'
[1673880031.177568][59520:59541] CHIP:CTL: Performing next commissioning step 'SendDACCertificateRequest'
[1673880031.177570][59520:59541] CHIP:CTL: Sending request for DAC certificate
[1673880031.177639][59520:59541] CHIP:EM: <<< [E:3729i M:207006129] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
[1673880031.177650][59520:59541] CHIP:IN: (S) Sending msg 207006129 on secure session with LSID: 32733
[1673880031.177743][59520:59541] CHIP:EM: <<< [E:3728i M:207006130 (Ack:191552182)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1673880031.177758][59520:59541] CHIP:IN: (S) Sending msg 207006130 on secure session with LSID: 32733
14:40:31.192   INFO   <--|FVPdev| [ERR] [DL] Long dispatch time: 122 ms, for event type 3
14:40:31.221   INFO   <--|FVPdev| [INF] [EM] >>> [E:3727r M:207006128 (Ack:191552181)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
14:40:31.246   INFO   <--|FVPdev| [INF] [EM] >>> [E:3729r M:207006129] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
14:40:31.261   INFO   <--|FVPdev| [INF] [ZCL] OpCreds: Certificate Chain request received for DAC
14:40:31.293   INFO   <--|FVPdev| [INF] [EM] <<< [E:3729r M:191552183 (Ack:207006129)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
14:40:31.309   INFO   <--|FVPdev| [INF] [IN] (S) Sending msg 191552183 on secure session with LSID: 9203
14:40:31.323   INFO   <--|FVPdev| [ERR] [DL] Long dispatch time: 121 ms, for event type 3
14:40:31.352   INFO   <--|FVPdev| [INF] [EM] >>> [E:3728r M:207006130 (Ack:191552182)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
14:40:31.378   INFO   <--|FVPdev| [INF] [EM] >>> [E:3730r M:207006131] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
14:40:31.393   INFO   <--|FVPdev| [INF] [ZCL] OpCreds: Received an AttestationRequest command
14:40:31.421   INFO   <--|FVPdev| [INF] [EM] <<< [E:3730r M:191552184 (Ack:207006131)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
14:40:31.437   INFO   <--|FVPdev| [INF] [IN] (S) Sending msg 191552184 on secure session with LSID: 9203
14:40:31.527   INFO   <--|FVPdev| [INF] [ZCL] OpCreds: AttestationRequest successful.
14:40:31.560   INFO   <--|FVPdev| [INF] [EM] <<< [E:3730r M:191552185 (Ack:207006131)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
14:40:31.575   INFO   <--|FVPdev| [INF] [IN] (S) Sending msg 191552185 on secure session with LSID: 9203
[1673880031.576063][59520:59541] CHIP:EM: >>> [E:3730i M:191552185 (Ack:207006131)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
[1673880031.576162][59520:59541] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0001
[1673880031.576182][59520:59541] CHIP:CTL: Received Attestation Information from the device
[1673880031.576195][59520:59541] CHIP:CTL: Successfully finished commissioning step 'SendAttestationRequest'
[1673880031.576216][59520:59541] CHIP:CTL: Commissioning stage next step: 'SendAttestationRequest' -> 'AttestationVerification'
[1673880031.576228][59520:59541] CHIP:CTL: Performing next commissioning step 'AttestationVerification'
[1673880031.576232][59520:59541] CHIP:CTL: Verifying attestation
14:40:31.592   INFO   <--|FVPdev| [ERR] [DL] Long dispatch time: 318 ms, for event type 3
14:40:32.177   INFO   <--|FVPdev| [WRN] This device was provisioned with dummy keys. This device is NOT SECURE
14:40:32.242   INFO   <--|FVPdev| [INF] [-] Secure firmware version: 1.6.1-0
14:40:32.243   INFO   <--|FVPdev|
14:40:32.252   INFO   <--|FVPdev| [INF] [-] Non-secure firmware version: 0.0.1-0
14:40:32.[254](https://github.com/ARM-software/connectedhomeip/actions/runs/3931215828/jobs/6722192659#step:13:255)   INFO   <--|FVPdev|
14:40:32.[305](https://github.com/ARM-software/connectedhomeip/actions/runs/3931215828/jobs/6722192659#step:13:306)   INFO   <--|FVPdev| [INF] [-] Open IoT SDK lock-app example application start
14:40:33.[335](https://github.com/ARM-software/connectedhomeip/actions/runs/3931215828/jobs/6722192659#step:13:336)   INFO   <--|FVPdev| [INF] [DL] Got IP address on interface: en1 IP: FE80::202:F7FF:FEEF:25F0
14:40:33.[347](https://github.com/ARM-software/connectedhomeip/actions/runs/3931215828/jobs/6722192659#step:13:348)   INFO   <--|FVPdev| [INF] [DL] Got IP address on interface: lo0 IP: ::1
14:40:33.[360](https://github.com/ARM-software/connectedhomeip/actions/runs/3931215828/jobs/6722192659#step:13:361)   INFO   <--|FVPdev| [INF] [DL] Got IP address on interface: lo0 IP: <IP_ADDRESS>
14:40:33.[370](https://github.com/ARM-software/connectedhomeip/actions/runs/3931215828/jobs/6722192659#step:13:371)   INFO   <--|FVPdev| [INF] [SVR] Server initializing...
14:40:33.415   INFO   <--|FVPdev| [INF] [TS] Last Known Good Time: 2023-01-16T14:33:13
14:40:33.460   INFO   <--|FVPdev| [ERR] [FP] Error loading fabric table: 8f, we are in a bad state!
14:40:33.471   INFO   <--|FVPdev| [ERR] [SVR] ERROR setting up transport: 8f
14:40:33.484   INFO   <--|FVPdev| [ERR] [-] Initialize server failed: Error CHIP:0x0000008F
14:40:33.493   INFO   <--|FVPdev| [ERR] [-] CHIP stack run failed
14:41:07.805   INFO   Commission discovered device failed

Required more debugging and find reason of this behaviour.

https://github.com/ARM-software/connectedhomeip/actions/runs/4125749624/jobs/7126745099


Add exercise for finding the missing number in a list

Is this going to be an easy or intermediate exercise?

I think it should be considered Easy

Basic


testappend information_schema external_table_p0 case.

master :  #26846
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


1271 predictions=true for sample posterior predictive throws error

Description

The extracted group is conditional on the kwargs if predictions=True
Related Issue

[ ] Closes #
[ ] Related to #

Checklist

[ ] Checked that the pre-commit linting/style checks pass
[ ] Included tests that prove the fix is effective or that the new feature works
[ ] Added necessary documentation (docstrings and/or example notebooks)
[ ] If you are a pro: each commit corresponds to a relevant logical change

Modules affected

[x] MMM
[ ] CLV

Type of change

[ ] New feature / enhancement
[x] Bug fix
[ ] Documentation
[ ] Maintenance
[ ] Other (please specify):

This has the mypy issues. But I think they are the same as the other PR

Or maybe not 😆
Happens locally


Exclude fields_matched on single result view

Problem

The fields_matched field does not make sense on the single results view as no search has been executed that could be matched.
Description

Exclude the fields_matched field on single result serializer.
One way to do this is to remove fields_matched from the basic MediaSerializer and have an additional subclass called SearchResultSerializer (or similar) that adds the field.
The field is currently always empty on the single results page. Removing it entirely would cause a backwards compatibility issue, so this is probably not possible to implement until we have #662 completed.

Serializer fields can be dynamically modified. Combining this with an overridden get_serializer function allows us to reuse the same class with a different set of fields without the need for inheritance.


Question: Ignite issue with Mapping of Value Type Object

Hi
We are currently facing an issue with mapping cache data to value object.
We actually came across a scenario where if the data is inserted to cache through DML statements which is INSERT In our case
then after that when we try to retrieve the data using cache API which is cache.get(id) then it is trying to map all the values
in the VALUE_TYPE object except for the primary key which is coming as "NULL".
When we try to insert data to cache using cache.put(key, Value) then we are able to map the values correctly but same does not apply for above.
Is this an exepected behavior or do we need any configuration change to map the primary key value correctly.
Please suggest.

Could you please share the code? A minimal working reproducer would be ideal.

Could you please share the code? A minimal working reproducer would be ideal.

Hi @ptupitsyn -
Please find the attachments for sample code to reproduce the issue.

I have first inserted the data using INSERT statement and then tried to retrieve it using cache.get("1"). and I see below result where primary key value is NULL. Same applies when we use the query API
Employee Data: Employee{id=null, name='john'<EMAIL_ADDRESS>

Could you please share the code as text? I'm not sure how to run screenshots.

Could you please share the code as text? I'm not sure how to run screenshots.

Hi @ptupitsyn
Sorry please see the attachments for the code  as a zip and also in the word document.
IgniteEventing.zip
IgniteExample.docx

Hi @ptupitsyn - Any update on this please?

Looks like the ID is both the cache key, and a part of cache value (Employees.id) field.

When you do cache.put, you duplicate the ID in two places
When you insert via SQL, the ID only goes to the key part

To see how this works internally, try Binary Mode - inspect the resulting object fields in both cases.
I recommend removing Employees.id field to avoid confusion. The id is already in the cache key.


Indent problems with pre tags (erb, ...)

The output for the following erb code

1
2
3

is the following html

1
      2
      3

This apparently messes up indention. It seems not to be an exclusive erb problem. I can reproduce the same with  kramdown e.g. too.

Not Middleman's fault, imo.
Haml has a feature against this problem. There should be some solution for ERb as well.

@DrTom could you post a full example? Not sure when this would happen. Is there a wrapping layout involved?

@lolmaus  Unlikely because erb should have not context about html like haml does.

@lolmaus @tdreyno  Ah, there is twist here; the layout is haml. Could be that haml does even indent already rendered html which is just passed to it. I'll have a look into it.

HAML is indeed the culprit. The problem disappears if I use an ERB layout instead.
@tdreyno  is there a global configuration to make HAML not indent?

Solved: set :haml, { ugly: true }
May this should find it's way into to middleman main documentation.


MF-1278 - Add kuiper rules engine source and sink

Pull request title should be MF-XXX - description or NOISSUE - description where XXX is ID of issue that this PR relate to.
Please review the CONTRIBUTING.md file for detailed contributing guidelines.
What does this do?
Adds kuiper rules engine plugins compatible with mainflux message format. The PR adds one source and one sink.

Which issue(s) does this PR fix/relate to?
Resolves #1278

@drasko @dusanb94 Do we have a plan for this PR?

@drasko @dusanb94 Do we have a plan for this PR?
@manuio I think not. It would take too much effort to continue work on this PR, so I think it's best to close it.

Since there has been no activity and it would take too much effort to continue work on this PR, I'm closing it.


Allow to add a suffix to specific packages when publishing

Clear and concise description of the problem
As a developer I want to be able to add a custom suffix to the version of specific packages in my workspace, even when I'm running the workspace with versions aligned.
Suggested solution
Imagine that I have 3 packages, all are published using the same version (i.e. v1.9.0). I now want to add a fourth package (package-d) that for a period of time will be in beta, to avoid confusing my users I want the versioning of this package to pick up at the same version number of the others, but with a -beta suffix.
When I version the next time (npx lerna version --conventional-commits --force-publish), I would like to have a version scheme like this:
package-a 1.9.0 -> 1.9.1
package-b 1.9.0 -> 1.9.1
package-c 1.9.0 -> 1.9.1
package-d 1.9.0-beta -> 1.9.1-beta

From a config perspective, this could be as simple as providing a new section to the lerna.json under command.version, that looks like this:
{
  "packages": [
    "package-a",
    "package-b",
    "package-c",
    "package-d",
  ],
  "command": {
    "version": {
      "suffix": {
        "package-d": "-beta"
      }
    }
  }
}

Note that the above suggestion is only an example, as long as this type of customization is possible on a per-package basis I wouldn't mind other ways.
Alternative
Currently I'm relying on a prepack custom script (at publish time) that:

reads the package.json
gets the version
adds the suffix
updates the package.json

Lerna will reset the changes, so the version is present only in the tarball being published to npm.
This however causes issues when used with the publish.removePackageFields feature, which prevents me to using it in the first place - see #637
Additional context
I have tried different combinations of --conventional-prerelease but with no luck, if I can achieve what I'm describing above with the current feature set, then I'd be more than happy to use the existing API.
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Lerna-Lite is a fork of Lerna and that does not exist in Lerna. You can contribute the feature if you want, I just don't have time to implement this myself, that's not something I would ever use myself

Thank you for the reply, I understand.


incorrect parsing of comma operator in loops

Both the following examples :
while (0,1);
for (;0,1;);

compile to
while 0
1

should compile to
0
while 1

persists in 2.0.


commonJS modules

Hello, do you plan to wrap the code into commonJS modules and not to store data in a window?
I would like to connect a Waypoint at each location where it is used, not in the head of the file, like jquery.

+1 I'd like to use waypoints from Browserify and currently it doesn't have a main attribute defined in the package.json.

No plans. Used to provide this library as a module and it was more pain by people trying to use the shortcuts than it was worth. Please shim or maintain a fork that wraps in the way you wish.