InTune Profile Save Error

I've created one Autologin multi-app kiosk profile, but on attempting to save another I get an error 'The UserAccountsConfiguration field is required' from looking at the logs. I am setting an AutoLogin account as the option, but save attempts still fail. On rechecking my settings, the user account field is not configured. Is this a known issue?

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

ID: 78038d67-04a1-f4ae-6a69-98e157688a31
Version Independent ID: c86b4460-e8be-8537-a6c8-3cb094ef14a3
Content: Create a Windows 10 kiosk that runs multiple apps (Windows 10)
Content Source: windows/configuration/lock-down-windows-10-to-specific-apps.md
Product: w10
GitHub Login: @jdeckerMS
Microsoft Alias: jdecker

@Niglb Intune Support should be able to help figure out the issue. Here are instructions for getting help with Intune: https://docs.microsoft.com/en-us/intune/get-support

So I have to upgrade my subscription to submit an intune ticket. ...

@Niglb You can post about your problem in the Intune forum: https://social.technet.microsoft.com/Forums/en-US/home?category=microsoftintune&filter=alltypes&sort=lastpostdesc

ok thank you I've done so.


Updated dev env to work on Windows with Docker Desktop and WSL2

Rebased, and merged.
Thanks for your contribution !


Building fails on macos

cargo build --release yields the following error on mac os
/Users/<username>/.cargo/registry/src/github.com-1ecc6299db9ec823/filetime-0.1.2/src/lib.rs:83:29: 83:57 error: unresolved import `std::os::macos::fs::MetadataExt`. Could not find `macos` in `std::os`
/Users/<username>/.cargo/registry/src/github.com-1ecc6299db9ec823/filetime-0.1.2/src/lib.rs:83                         use std::os::$i::fs::MetadataExt;

Cannot build on macos because of this issue. Any tips/hints would be greatly appreciated

This is actually a problem in the dependency, filetime, which was reported here: https://github.com/alexcrichton/filetime/issues/1
xsv does indeed require the Rust nightly compiler, but hopefully not for long. Can you share version info? Try running:
rustc --version
cargo --version

Thanks!

Sure thing. I'm currently using rust 1.0.0 stable
$ rustc --version
rustc 1.0.0 (built 2015-05-16)

$ cargo --version
cargo 0.2.0 (a483581 2015-05-14) (built 2015-05-16)

Yeah, xsv doesn't work on stable yet. Sorry. Hopefully soon.
If you want to give it a whirl now, you'll need to grab the nightly compiler.


Pull Request Reviews (Preview API) methods have unusual error format that is not parsed.

Pull Request Reviews (Preview API) methods were tracked in #495 and implemented in #497. They currently seem to use an unusual format for errors, and go-github does not parse that format.
Originally discovered by @haya14busa during review of #497:

As I posted request and error response example (https://github.com/google/go-github/pull/497#discussion_r92933362), error format for review API is not same as http://developer.github.com/v3/#client-errors
"errors" is list of string for review API.
{
  "message": "Validation Failed",
  "errors": [
    "Cannot return null for non-nullable field PullRequestReviewComment.position"
  ],
  "documentation_url": "https://developer.github.com/v3/pulls/reviews/#get-a-single-reviews-comments"
}

Corresponding go-github struct (ErrorResponse)  is here. https://github.com/google/go-github/blob/fbc15caccf54600900355e302a0fafabf7e2d733/github/github.go#L463
Because ErrorResponse doesn't support review API error format, error information is dropped with unmarshalling and it's really difficult to debug error using go-github.
(I tried to implement create review API in my personal project https://github.com/haya14busa/reviewdog/pull/63 using go-github, but it was really hard to debug error... )
I'll report this problem to GitHub support, but this review API error fromat could be intentional.
If so, we have to handle this problem I guess.

See https://github.com/google/go-github/pull/497#issuecomment-267810912 for full context and details.
This issue is to track that problem (which will soon be merged into master) and resolve it afterwards. The unusual error format is not documented, and we're waiting on GitHub to potentially fix the error format for those endpoints, or update documentation.

@dmitshur - have you heard anything back from the GitHub support on the issue (since it is marked "wairing for GitHub")?

https://godoc.org/github.com/google/go-github/github#PullRequestsService.ListReviewComments contains a link to this issue:

TODO: Follow up with GitHub support about an issue with this method's returned error format and remove this comment once it's fixed. Read more about it here - https://github.com/google/go-github/issues/540

It was @haya14busa that emailed GitHub, not me. See https://github.com/google/go-github/pull/497#issuecomment-270400412.
The latest status in that thread seems to be https://github.com/google/go-github/pull/497#pullrequestreview-19529473.
@haya14busa Can you let us know please if there have been any updates from GitHub since then?

I pinged 2-3 times but got no clear response from the supports.
Can anybody send a report again?
Maybe they think it's not high priority issue (or didn't understand the point from my email).


[depdive] Improve error propagation

so that just one failure somewhere crashes the entire program. Related #115

closing as not being a specific issue.


improve docstore lookup time

Lookup speeds in docstores are pretty fast, but they could probably be even faster.
cord19 (1000 documents, warm start)
pyserini: 0.2661s
ir_datasets: 0.1743s
msmarco-passage (1000 documents, warm start)
pyserini: 0.0482s
ir_datasets: 0.0179s
Replacing the gzip compression with snappy gets them down, especially for the longer cord19 documents:
cord19: ir_datasets(snappy): 0.0675s
msmarco-passage: ir_datasets(snappy): 0.0141s
But it increases the size of the docstore files (1.4G vs 870M for cord19 and 3.1G vs 2.4 G for msmarco-passage). And it introduces a dependency on libsnappy, which means the package couldn't be easily installed via pip anymore.

I should check the timings for the new lz4 implementation I added for ClueWeb's new doc cache implementation. If this is faster, I should replace the others with the new implementation.


403 on Server but not on my Desktop

as in the title, using the library works just fine on my desktop but once the code is ran on my server it just 403's.

Genius.com is probably blocking your server's IP due to too many requests. I would suggest you use it on the client-side so each client requests from its own IP.

that could be a possibility but i don't make anywhere close enough requests to have that be the main issue

That's strange. Could you please share your code so we can be sure?

I got the same problem. Its working on my computer but when I push it to the server it only returns 403. Maybe its the reverse proxy, that causes the issue.
Code is quite simple:
function getLyrics(title) { 	var searchOptions = { 		title: title, 		artist: " ", 		apiKey: "XXX", 		optimizeQuery: true 	} 	genius.getLyrics(searchOptions).then((lyrics) => { 		console.log(lyrics); 	}); }

Bump, seeing the same issue...will reply back if I find a fix!

since i just got a notification for this:
with another library i've tracked it down to that genius has probably blocked my ip. i verified this by connecting to my server with a vpn and then opening the genius website, where i was asked to fill in a captcha. so i don't think there's much you can fix here


Caused by: android.view.InflateException: Binary XML file line #26: Error inflating class com.ittianyu.bottomnavigationviewex.BottomNavigationViewEx

Caused by: android.view.InflateException: Binary XML file line #26: Error inflating class com.ittianyu.bottomnavigationviewex.BottomNavigationViewEx

按照demo来的怎么进去就崩溃，BottomNavigationViewEx这个报错呢

#108 可以看看这个


Allow auto-detection of imported enum values

Motivation
Since the introduction of enhanced enums in Dart 2.17 (https://dart.dev/language/enums#declaring-enhanced-enums), associating metadata and custom behavior to enums is a common pattern, hence dicouraging using generator tools to generate enums. As Slang allows translations of existing enums via imports / generate_enum, we still need to explicitly list again all enums values in contexts.[existing_enum].enum, which naively seems redundant in cases where we need all enums values to be translated (which, IMO, represents the majority of cases).
Developer Experience
Could we consider, instead of:
# Config
imports:
  - 'package:my_package/path_to_enum.dart' # define where your enum is
contexts:
  UserType:
    enum:
      - user
      - admin
    generate_enum: false # turn off enum generation

... just do:
# Config
imports:
  - 'package:my_package/path_to_enum.dart' # define where your enum is
contexts:
  UserType:
    generate_enum: false # turn off enum generation

... and let slang search for UserType in imported dart files + check for presence of all expected translations based oncontexts.[existing_enum].paths / auto-detected paths ?

Parsing the source code will be difficult as slang does not know where the file is located (it may be in another package), but slang could infer the enum values from the translation files

Since 3.19.0, you can leave out the enum values.


Genericize CloudFormation Templates

[ ] Genericize for non-Aptible websites
[ ] Genericize for any static websites

One thing I stumbled upon just now: while CloudFormation template "partials" aren't possible, it is possible to to reference a dependent CloudFormation stack within another stack's template: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-stack.html


Update container image to access secrets

Update the Dockerfile to read the secrets and display the value.

The container does not display the secret value. The home.handlebars needs to be udpated.


Create user documentation

In GitLab by @arisilon on Oct 15, 2019, 16:49
Should probably use ReadTheDocs site.

In GitLab by @arisilon on Oct 16, 2019, 13:40
closed

In GitLab by @arisilon on Oct 16, 2019, 13:53
unassigned @arisilon

In GitLab by @arisilon on Feb 4, 2021, 21:50
mentioned in commit<PHONE_NUMBER>8f665981cb8fe90d778182e9c458c9

In GitLab by @arisilon on Feb 3, 2021, 22:27
mentioned in commit 642d6c4c49dd0da940d892761e7a78afcb223513

In GitLab by @arisilon on Oct 16, 2019, 13:40
reopened

In GitLab by @arisilon on Feb 1, 2021, 22:09
mentioned in commit 3f51112f26b340aabe4174aa72051e9520ee51ac

In GitLab by @arisilon on Feb 15, 2021, 20:12
mentioned in commit 5cd1151c6b56ce63f33715688d98781e48112bba


Conditionally create package.json

Node.js tasks can be useful for projects that don't necesserally wish to expose a package.json file (like a theme inside a Drupal project), the package.json is installed based nodejs_install_package_json  but the package.json file is created unconditionally. The quick PR just propose to submit the Create default package.json task to nodejs_install_package_json also.
This PR is a : Improvement

True, it could be interesting to let the user provide the base package.json, I've added another commit to the pull request accordingly.

Why not split the role in two :

nodejs : only install nodejs and other relevant packages
 : optionally create package.json and run npm install ?

To be frank the npm install was moved here when the gulp role was cleaned, but I was always under the impression that it isn't really the right place. And automatically creating the package.json seems also wrong somehow.
Separating the role in two would also allow to have a better control on when the install actually occurs, for example after the modification of the package.json in a custom role.
My 2 cents

I think that would make everything more complicate for no added value. I’ve never seen a project using Node without a package.json until now and therefor think this is more the exception than the common behavior.
Separating it in a dedicated role means it would be disabled by default which goes against that. Developers would have to enable two roles instead of one in most cases. Also I can’t figure out a role name that would be self-describing enough for people to understand what it actually do and how it’s tied to the Node role.
You seems to be assuming a lot here; I would be happy to change my mind with examples of actual problems caused by the existing setup.

I was just dumping some idea, I don't have a precise usecase in mind :)
You're probably the one using this role the most.


Batched Dependabot updates

This PR was created by the Dependabot Batcher Action by combining the following PRs:
Wed Sep 07 2022

#1021
#1020
#1018
#1017

Mon Sep 12 2022

#1027
#1025
#1024

Mon Sep 19 2022

#1030

Mon Sep 26 2022

#1034

Closing this as done as part of #1093 and #1094


Support streaming AES CTR/GCM encryption/decryption

If AES CTR/GCM mode can support the following streaming types, it would be very helpful to encrypt and decrypt large files without a lot of memory. Thanks!
export type Cipher = {
  update: (data: Uint8Array) => Uint8Array;
  final: () => Uint8Array;
};

export type Decipher = Cipher;

for now something like this can be built by users https://github.com/openpgpjs/openpgpjs/blob/b2bd8a0fdd12902484d65baa4ae4eb7f146fcd32/src/crypto/cipherMode/cfb.js#L357


Live share not working for me

My liveshare not working when I click share or join is not working.

\extLiveShare


Use Rocky Linux 9 container base image by default

There are no stable releases that support CentOS Stream 8 any more, therefore rocky 9 should be the default moving forwards

Should we first change the default in yoga & earlier SKC to use CS8, or are we leaning on the submodule pinning?

Should we first change the default in yoga & earlier SKC to use CS8, or are we leaning on the submodule pinning?

I think the pinning should be fine. I'd like to update the checkout from Yoga onwards but I'd understand if you think it would be safer to only change the default in Zed+

It could be a bit risky to change the default in yoga - mainly due to the change in python version. We'll need to consider SKC CI as well as the stackhpc.kayobe_workflows collection.

Sounds sensible. We can just update the pin in Z/A

The base image was changed to RL8 in #58. Should we go ahead with this or not?

The base image was changed to RL8 in #58. Should we go ahead with this or not?

Caracal support is around the corner. How about we merge it when we officially support Caracal and drop Yoga?


Final Touches: Proof Of Existence Tutorial

[ ] Gather Feedback from Users

[ ] Add links to the tutorial from other docs

[ ] Possibly update the "test" section to a different name

[x] Fix ... with --snip--

[ ] Fix comments from // to /// where possible (breaks macros)

[x] Add code comments to front-end

[x] Update use of "forked" when referring to Git

[ ] Make code snippets copy-able.

Copyable code blocks: https://gist.github.com/yangshun/55db997ed0f8f4e6527571fc3bee4675

How can I turn ... into --snip-- while producing valid rust syntax which only takes one line?

/* --snip-- */?

#263 solves the last item on the list

Updated last chapter to "Building a Custom Front End"


Responsiveness doesn't change on parent resize

I have my Flex grid setup with a parent container.  If I resize the browser, the breakpoints seem to trigger as expected, however if I update the parent containers width to simulate a mobile preview, it doesn't seem to adjust.  Any idea if something else needs to occurs?

Media queries only detect changes in the viewport. What you're describing is often referred to as "container queries," which don't actually exist in CSS


Do M2 terminals make sense on final placed & routed design?

Does it makes sense to always export M2 pins even when we are going through multiple via layers to do so? I feel like it would make more sense to simply extend existing M2s... Or export a higher metal layer to begin with.
@stevenmburns @desmonddak @Lastdayends
While I briefly alluded to this issue in #165, it should be considered an independent enhancement and not a bugfix for the MinL issue.

#668 & #704 addresses this


Ensure timeouts do not happen during Galaxy DemoCoin Demo sync

Ensure timeouts do not happen during Galaxy DemoCoin Testnet v0.0.4-alpha-demo sync
Version: Galaxy DemoCoin Testnet v0.0.4-alpha-demo UX enhancements
Issue
Currently the syncing sometimes pauses for a very brief 15 second timeout. @faddat is going to test syncing by testing the syncing on 10, or so, different environments other than is own. This should significantly assist in ensuring a smooth sync when demoing.
Possible solutions

Change validator to 64 bit node should help

So, for this one, we unfortunately need to wait and see.  As far as I know (a few successful syncs) we no longer suffer from this issue on Testnet-3.  I'm going to do a laptop-sync against Testnet-3  now to make sure of that, and to make sure Testnet-3 is still up.

Update:  It's still up, and sync is very quick.
I do wish I knew why there was this issue on our ARM systems though.  It's not so great that we have to run on 64-bit in order for sync to happen fast.  (Pi's are 32-bit ARMv7h)

Update:
I[07-19|15:07:51.429] Recheck txs                                  module=mempool numtxs=0 height=17511
I[07-19|15:07:51.431] Indexed block                                module=txindex height=17511
I[07-19|15:07:51.432] Executed block                               module=state height=17512 validTxs=0 invalidTxs=0
E[07-19|15:07:51.453] SendTimeout                                  module=blockchain peer=bf300feed21441b5c91bc0d39569e1f01521173c reason="peer is not sending us data fast enough" curRate="7 KB/s" minRate="7 KB/s"
I[07-19|15:07:51.484] Committed state                              module=state height=17512 txs=0 appHash=204EAB6ABA5D9963069DE4D97E3062DF1D461A85
I[07-19|15:07:51.484] Recheck txs                                  module=mempool numtxs=0 height=17512
I[07-19|15:07:51.484] Indexed block                                module=txindex height=17512
E[07-19|15:07:51.484] Stopping peer for error                      module=p2p peer="Peer{MConn{<IP_ADDRESS>:26656} bf300feed21441b5c91bc0d39569e1f01521173c out}" err="error with peer bf300feed21441b5c91bc0d39569e1f01521173c: peer is not sending us data fast enough"
I[07-19|15:07:51.484] Stopping Peer                                module=p2p peer=<IP_ADDRESS>:26656 impl="Peer{MConn{<IP_ADDRESS>:26656} bf300feed21441b5c91bc0d39569e1f01521173c out}"
I[07-19|15:07:51.484] Stopping MConnection                         module=p2p peer=<IP_ADDRESS>:26656 impl=MConn{<IP_ADDRESS>:26656}
I[07-19|15:07:51.554] Stopping gossipDataRoutine for peer          module=consensus peer="Peer{MConn{<IP_ADDRESS>:26656} bf300feed21441b5c91bc0d39569e1f01521173c out}"
I[07-19|15:07:51.554] Stopping gossipVotesRoutine for peer         module=consensus peer="Peer{MConn{<IP_ADDRESS>:26656} bf300feed21441b5c91bc0d39569e1f01521173c out}"
I[07-19|15:07:52.014] Stopping queryMaj23Routine for peer          module=consensus peer="Peer{MConn{<IP_ADDRESS>:26656} bf300feed21441b5c91bc0d39569e1f01521173c out}

:/
Maybe the solution to this is to build a larger network.  For that we'd need funding and community-building.  The node it is syncing from is a 64-bit node on a decent VPS provider, so I don't really think that the problem is the node.

Timeouts happened, but Sync still happened in less than 5 minutes.

To attempt to remedy this issue, testnet 4 will have:
3 validators

Jacob
Vsund
???

10 Full nodes
????  (Can be easily spun up in the cloud if needed)

@faddat please add me to the list.. 😄

I'm not getting timeouts here.  I'm going to reinstall and use my phone as a timer.  Will post results.

13083 blocks synced in 12m 48s
Multiple timeouts observed.  :(

This issue needs to stay open.  Adding it to #50, closing #21 since TN4 is deployed and TN5 is being designed.  There are still issues with sync, particularly on the smallest devices.


Dead link in README

The Terminal codes (ANSI/VT100) link in the README.md leads to a dead (parked) domain serving only ads.
The link should be replaced with a valid alternative or removed.

Maybe:
https://en.wikipedia.org/wiki/ANSI_escape_code
?

An other possibility would be an archive.org Link, at least temporarily.


After successful building, no eigen module found!

Hi guys, I run ubuntu 16.04 on Jetson TX2, installation from apt doesn't work for me, as shown, no such python-eigen package found. Then I just followed the instruction for manual installation, after success building, import eigen still failed, no such eigen module.

nvidia@tegra-ubuntu:~$ pip install -r requirements.txt
Requirement already satisfied: cython>=0.25 in /usr/local/lib/python2.7/dist-packages (from -r requirements.txt (line 1)) (0.28.2)
Collecting coverage>=4.0 (from -r requirements.txt (line 2))
Requirement already satisfied: nose in /usr/lib/python2.7/dist-packages (from -r requirements.txt (line 3)) (1.3.7)
Requirement already satisfied: numpy>=1.8.2 in /usr/local/lib/python2.7/dist-packages (from -r requirements.txt (line 4)) (1.13.3)
Installing collected packages: coverage
nvidia@tegra-ubuntu:~/Eigen3ToPython$ pip install .
Processing /home/nvidia/Eigen3ToPython
Building wheels for collected packages: eigen
Running setup.py bdist_wheel for eigen ... done
Stored in directory: /tmp/pip-ephem-wheel-cache-T_z7yk/wheels/50/8f/01/d7fcf5aa4428cc4dd31aba6e7774f19b2a4d398bc7bcd60a02
Successfully built eigen
Installing collected packages: eigen
nvidia@tegra-ubuntu:~/Eigen3ToPython$ python
Python 2.7.12 (default, Dec  4 2017, 14:50:18)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import eigen
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named eigen

So what solution would you suggest?

I just solved this by
sudo python setup.py install
instead of
pip install .


Stop parsing language-variable cat output to make cat_dir more reliable.

Supersedes #826

Looks good, thanks!


Add smart link prefetching

Imagine we're on the Category page. A lot of links to PDP. prefetching the links themselves makes a little sense (bc. we'll prefetch the HTML server side rendered).
How to prefetch the JSONs that are utilized to display PDP (so the requests being executed via asyncData)?

Related to: #104


Get ServiceHub and Electron .dll's signed

Some the .dlls we ship seem to not be signed. Let's get those signed!

For the service hub .dll's, the service hub team is intending to get those signed themselves.
For the electron .dll's, we should find out if the internal Electron team is supposed to be signing those, or if we need to with the 3rd party cert.

Get a response from the internal Electron team. They aren't going to sign those dll's so we need to sign them ourselves.


SKBitmap.Decode return is null

using (var memoryStream = new MemoryStream(ImageData))
using (var stream = new SKManagedStream(memoryStream))
using (var bitmap = SKBitmap.Decode(stream))
ImageData is a byte array
why in v1.59.1 ,  bitmap always return null?
in v1.56.0 is normal

Do you have any details on what type of image was encoded? (png, jpg)
What you can also do is to save ImageData to a file (just a direct write bytes) and see if the OS can read the file. It may be corrupted. I don't think skia removed any decoders, so it may be something else.

sorry,It's my code problem, i will close this issue. Thx

@xiangzLL  I am also facing same issue. can you please let me know how you resolve this issue?

it's my code problem,my image byte array is wrong.maybe we are not facing the same issue.
or you can show the codes, let me help you.

I'm facing the same issue using SKBitmap.Decode(string fileName) and strangely, the results are randomly null !
It's a lot like returning the Decode method soon without having some Async operation finished first (I'm not sure if it's using async, It just looks like that cuz it's random !)


Adding python 3.12 support

Python 3.12 doesn't seem supported by all packages today

@JoOkuma Do you need to pin numba?

@ilan-theodoro, we had to do that at some point; they are always a bit behind the standard Numpy/python.
It might be time to bump every package to its latest and fix the problems.
I'm going to try to upload python-mip to conda. If that works, I think ultrack will be ready for conda, and we could use it in the CI.
Hopefully, that solves our broken CIs, and we can do this version bump with some peace of mind.

Done through #130


Cisco/MerakiLocations: NaN co-ords in Scanning API payload prevent whle payload from beign parsed

Looks like one client's Meraki Scanning api webhook posts include -NaN values for their device x/y location co-ordinates. We are seeing errors like this in core logs:
level=INFO time=2021-04-28T10:26:28Z source=mod-H5KxD_-JHwW message="unable to convert result to json executing device_locations on Cisco::Meraki::Locations
[{location: :wireless, coordinates_from: "bottom-left",
 x: -NaN, y: -NaN,
lon:<PHONE_NUMBER>49935, lat: 35.6640541069923, s2_cell_id: "60188b9a7124", mac: "28c63f315f47", variance: 25.0, last_seen:<PHONE_NUMBER>, map_width: 47.977872690998, map_height: 47.735426031652, manufacturer: "Intel", os: "Windows 10", ssid: "mwifi"}, {location: :wireless, coordinates_from: "bottom-left", x: -NaN, y: -NaN, lon:<PHONE_NUMBER>92909, lat: 35.6640012623622, s2_cell_id: "60188b9a769c", mac: "80325397db19", variance: 25.0, last_seen:<PHONE_NUMBER>, map_width: 47.977872690998, map_height: 47.735426031652, manufacturer: nil, os: nil, ssid: nil}, {location: :wireless, coordinates_from: "bottom-left", x: -NaN, y: -NaN, lon:<PHONE_NUMBER>10019, lat: 35.6639500520688, s2_cell_id: "60188b9a71d4", mac: "00804cc12e56", variance: 25.0, last_seen:<PHONE_NUMBER>, map_width: 47.977872690998, map_height: 47.7354
...

NaN not allowed in JSON (JSON::Error)
  from /usr/share/crystal/src/json/builder.cr:90:9 in 'number'
  from /usr/share/crystal/src/json/to_json.cr:55:5 in 'to_json'
  from /usr/share/crystal/src/json/to_json.cr:147:7 in 'to_json'
  from /usr/share/crystal/src/json/to_json.cr:96:14 in 'to_json'
  from /usr/share/crystal/src/json/to_json.cr:10:7 in 'to_json'
  from /usr/share/crystal/src/json/to_json.cr:4:7 in 'to_json'
  from repositories/drivers/lib/placeos-driver/src/placeos-driver/core_ext.cr:5:5 in 'try_to_json'
  from repositories/drivers/drivers/cisco/meraki/meraki_locations.cr:6:1 in '->'
  from /usr/share/crystal/src/primitives.cr:255:3 in 'execute'

one payload captured here: https://gist.github.com/w-le/cdd21677a5d4da99ce67da3f41f76c2a
Can you edit MerakiLocations for Dashboard driver such that these Nan and -Nan values are ignored and the any valid locations in the payload are still parsed?

OR was the snippet of data above already processed by placeos drivers - thus the -NaN was created by PlaceOS due to an inability to parse a valid x/y float from a Meraki payload?

I believe the data above IS already processed by PlaceOS drivers, because I see epoch values for last seen.
So first we have to check to see what raw x/y values from Meraki caused our parsed data to be -Nan


[SPARK-23754][PYTHON][FOLLOWUP][BACKPORT-2.3] Move UDF stop iteration wrapping from driver to executor

SPARK-23754 was fixed in #21383 by changing the UDF code to wrap the user function, but this required a hack to save its argspec. This PR reverts this change and fixes the StopIteration bug in the worker.
The root of the problem is that when an user-supplied function raises a StopIteration, pyspark might stop processing data, if this function is used in a for-loop. The solution is to catch StopIterations exceptions and re-raise them as RuntimeErrors, so that the execution fails and the error is reported to the user. This is done using the fail_on_stopiteration wrapper, in different ways depending on where the function is used:

In RDDs, the user function is wrapped in the driver, because this function is also called in the driver itself.
In SQL UDFs, the function is wrapped in the worker, since all processing happens there. Moreover, the worker needs the signature of the user function, which is lost when wrapping it, but passing this signature to the worker requires a not so nice hack.

@HyukjinKwon

Test build #91701 has started for PR 21538 at commit 217e730.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@e-dorigatti Can you add [BACKPORT-2.3] in the PR title? Thanks.

add to whitelist

Test build #91701 has finished for PR 21538 at commit 217e730.

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

Test build #91704 has started for PR 21538 at commit 217e730.

Merged build finished. Test PASSed.

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

Yea, it's unfortunate .. we should fix and set up the Jenkins env too.

Test build #91704 has finished for PR 21538 at commit 217e730.

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

Merged build finished. Test PASSed.

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

Test build #91716 has started for PR 21538 at commit 612781a.

Test build #91716 has finished for PR 21538 at commit 612781a.

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

Merged build finished. Test PASSed.

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

Merged to branch-2.3.

@e-dorigatti, this got merged into branch-2.3. Likewise, this also should be manually closed. Thanks for working on this.

@HyukjinKwon thank you so much for your patience :)


Periodic Recovery thread of RecoveryManagerService blocks the shutdown gracefully

I am having problem so that the applications of Batch typology (spring-batch) that use XA with Narayana stop in a friendly way when they finish their process.
From what I have been able to see, the problem resides in that when creating the RecoveryManagerService bean and performs the start(). it ends up creating the thread with name Periodic Recovery as daemon=false, which prevents the JVM from terminating when it receives a gracefully shutdown when it finishes processing its code from the main.
The only way I have been able to solve the problem is to redefine the RecoveryManagerService bean and not perform the start(), but I don't like this solution:
  @Bean(destroyMethod = "stop")
  @DependsOn({"narayanaPropertiesInitializer"})
  public RecoveryManagerService recoveryManagerService(CustomNarayanaProperties properties) {
    RecoveryManager.delayRecoveryManagerThread();
    final RecoveryManagerService recoveryManagerService = new RecoveryManagerService();
    recoveryManagerService.create();
    // if properties.getPeriodRecovery().isEnabled()==false do not start the recovery manager service because it creates a non-daemon
    // period-recovery thread that avoids the normal termination of the JVM process daemon=false that in bath applications not permits to
    // finish the application when the main process ends.
    if (properties.getPeriodRecovery().isEnabled()) {
      recoveryManagerService.start();
    }
    return recoveryManagerService;
  }

I have also tried to set the properties narayana.periodicRecoveryPeriod, narayana.expiryScanInterval with value 0 but it ends up creating the thread daemon=false.
Is there any way by configuration to create the Periodic Recovery thread as daemon=true? or just disable the recovery service?

Hi @ferblaca, thanks for you question. Isn't there a way to invoke RecoveryManagerService.stop()

I have also tried to set the properties narayana.periodicRecoveryPeriod, narayana.expiryScanInterval with value 0 but it ends up creating the thread daemon=false.
Is there any way by configuration to create the Periodic Recovery thread as daemon=true? or just disable the recovery service?

I wouldn't touch those properties for achieving what you're looking for. Also, I wouldn't disable the Recovery Manager unless you are fine with broken transactions.

Hi @jmfinelli ,
correct, in fact those properties have no effect on the creation/setting of the Periodic Recovery thread.
For me, the most appropriate solution would be to be able to set the Periodic Recovery thread as daemon=true, but currently it is not possible.

AFAIU, you would like to achieve a graceful shutdown. OTOH, if Periodic Recovery is killed without shutting it down properly, I don't think we can call this kind of shutdown "graceful".

@jmfinelli, the problem in our applications is that Periodic Recovery never finishes shutting down correctly, and therefore neither does the JVM. If at least once past the last interval defined in periodicRecoveryPeriod it would shutdown once gracefully shutdown was previously executed it wouldn't be so problematic, but that doesn't happen either.

How are you shutting down Periodic Recovery? Do you have any Narayana logs we can review to understand why Periodic Recovery's shutdown isn't completing correctly?

I wonder how your application is going to shut down. Normally every Spring application is going to destroy its created beans, which is calling stop on recovery service. Periodic recovery normally needs only a few seconds for each round. Maybe you have many broken transactions on your device?

I will try to reproduce the problem in a simpler application than ours in order to explain it better. If I don't succeed maybe it's something of our applications that I haven't seen yet.
But yes @graben, I see that the stop of the Service Recovery is executed and also the destroy of the beans, but the Periodic Recovery thread as daemon=false if alive, so it prevents to turn off the JVM.
If I can reproduce it or not in a simple way I will inform you. Thanks.

Maybe you have many broken transactions on your device?

@graben - AFAIU, even in this case it shouldn't hung (unless @ferblaca is using the new logic to graceful shutdown, i.e. RecoveryEnvironmentBean.setWaitForWorkLeftToDo(true))

@jmfinelli,
I have created a very simple demo that reproduces the problem at https://github.com/ferblaca/Narayana.
Steps to reproduce

Run the standalone application and verify that the standalone application program never ends.

Check in console log that exists a thread called Period Recovery daemon=false.
--------------------------> Thread name: Periodic Recovery, Daemon: false

To solve this behavior you can set the recovery.period.start.disabled: true  which configure a RecoveryManagerService Bean without performs the start().
Point of view

Semantics of a batch program (IMHO): A batch program / process runs over a finite amount of time, it must start and end after completing the tasks is meant to do.
A batch program cannot run indefinitely, like a web service or a message listener, that wait for client connections "forever".
A batch program can need XA/Open distributed transaction semantics among several resources, it's a legitimate use case
If the Recovery thread is needed it must be running in a batch (or not batch) program.
Current status: If the recovery thread is a non-daemon thread, it will never shutdown even if the "main" thread shuts down, so the batch program will never end; defeating the batch program (finite amount of time running) semantics.
If the recovery thread is a daemon thread, by default it will shut down when the main (parent) thread shuts down. But you said that situation will prevent the thread performing needed pre-shutdown tasks to ensure transactions are not broken.
If the recovery thread is a daemon thread but the main thread has a waiting time (configurable amount of time) to allow the recovery thread to perform the pre-shutdown tasks; and then finalize the execution, the batch semantics can be honored. I know that you can't always ensure how long the recovery thread will take to perform its tasks; but at least you have a configurable parameter to give it room for it's pre-shutdown tasks.

If we are in the situation depicted in point 5, you cannot build a batch program with Narayana because it will be running forever. This given you said the Recovery thread is NEEDED and cannot be inhibited because it could cause having broken transactions.
I think that with (6) and (7) you can keep the Recovery thread doing its work, while allowing to use Narayana for Batch processes that must end.

You're still using NSB 3.1.1, please try 3.2.0 there have been a lot of fixes and dependency updates.

@ferblaca - I tried your reproducer but I'm not sure how to reproduce the problem you're talking about. PeriodicRecovery.shutdown(boolean) is invoked and I can see that (dropping a breakpoint here) the PeriodicRecovery's Thread is not alive. I'm not sure if this can help but I also added System.out.println("Running something now"); to your contextLoads test and it gets printed after --------------------------> Thread name: Periodic Recovery, Daemon: false

@ferblaca : Same for me, program behaves as expected.  Normal run, normal shutdown, no problems occurring.

I've just run the reproducer from @ferblaca in command line with this setup:
09:45 $ mvn -v
Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Maven home: /home/user1/.asdf/installs/ivm-maven/3.9.4
Java version: 17.0.12, vendor: Eclipse Adoptium, runtime: /home/user1/.asdf/installs/ivm-java/openjdk-17.0.12
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "<IP_ADDRESS>-microsoft-standard-wsl2", arch: "amd64", family: "unix"

and
09:46 $ mvn clean install
[...]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  4.232 s
[INFO] Finished at: 2024-10-07T09:46:43+02:00
[INFO] ------------------------------------------------------------------------

then
09:46 $ java -jar target/demoBatchNarayana-0.0.1-SNAPSHOT.jar
and the execution hangs here:
[...]
2024-10-07T09:47:15.325+02:00 DEBUG 31804 --- [demoBatchNarayana] [           main] o.s.jdbc.core.JdbcTemplate               : Executing prepared SQL statement [INSERT INTO "PRODUCT" ("DISCOUNT", "NAME", "PRICE") VALUES (?, ?, ?)]
2024-10-07T09:47:15.325+02:00  INFO 31804 --- [demoBatchNarayana] [           main] c.e.b.n.d.DemoBatchNarayanaApplication   : product persisted id 10
--------------------------> Thread name: main, Daemon: false
--------------------------> Thread name: Transaction Expired Entry Monitor, Daemon: true
--------------------------> Thread name: Periodic Recovery, Daemon: false
--------------------------> Thread name: Listener:44767, Daemon: true
--------------------------> Thread name: Transaction Reaper, Daemon: true
--------------------------> Thread name: Transaction Reaper Worker 0, Daemon: true

The application  does not ever finish.
If I want to terminate the process I must issue a Ctrl-C (SIGINT) in the terminal. So I find the same problem as @ferblaca found

I'm not a Spring developer but I think that this can help:
var context = SpringApplication.run(DemoBatchNarayanaApplication.class, args);
addShutdownHook();
SpringApplication.exit(context);

I think you'll need something that will call a shutdown, like SpringApplication.exit(...). Never thought about using Narayana on a self-closing application.

Thanks @jmfinelli! with this you have given us the clue to ensure that the Shutdown signal reaches the JVM and finally stop the recovery service in an orderly way. Finally we configure de application as:
    public static void main(final String[] args) {
        System.exit(SpringApplication.exit(new SpringApplicationBuilder().sources(Application.class)
            .web(WebApplicationType.NONE).run(args)));
    }

Regards,

@ferblaca Great news! Thanks for sharing it :partying_face:


Initial item/file domain detectors

Adding initial set of implementations of classes that can scan a data item/file and detect the applicable DataDomain for its data.
Note that this branch builds off that of #564.  As such, this PR should remain in draft status until #564 is merged.

@aaraney, I think all the changes we've discussed have been made.  I'm a little puzzled by the test failures.  I'm not seeing them locally, and I created a fresh 3.10 environment to test in just to be safe.   I'm curious if you see these on your side.  FWIW, I did clear the cache entries related to this PR, and it didn't seem to help.

@aaraney, @christophertubbs, is there anything remaining for this PR that needs to be changed before it can be approved?


[docker-compose]: Fix issue about migration to postgresql 12

From postgresql 11 or 12, we can't use an empty password by default.
You may:

Define a password (POSTGRES_PASSWORD)
Set trust as auth method (POSTGRES_HOST_AUTH_METHOD=trust)

The easiest way to fix it right is to use the trust auth method, but it should be better in a production environment to set a password instead.
Thank you for your work.

Thanks!


Add Github Actions regression testing

Example: https://github.com/themperek/cocotbext-axi/actions/runs/383389174

Do I need to do anything else on the repo to enable github actions, or will that start working after adding the files to the repo?
Also, do you know what the runtime limit is for github actions?  This shouldn't be an issue for this repo, but for the PCIe DMA modules, several testbenches take quite some time to run (1-2 hours).

Do I need to do anything else on the repo to enable github actions, or will that start working after adding the files to the repo?

For me started automatically.

Also, do you know what the runtime limit is for github actions? This shouldn't be an issue for this repo, but for the PCIe DMA modules, several testbenches take quite some time to run (1-2 hours).

It seems it is 6 hours. https://docs.github.com/en/free-pro-team@latest/actions/reference/usage-limits-billing-and-administration#usage-limits

Hmm.  Well, 6 hours is better than travis-ci that IIRC cuts you off after 1 hour.  But, I did do a quick (heh) test by running the tests for the verilog-pcie repo with pytest -n 2 as it seems like it runs with two cores in github-actions, and it crashed with xdist reporting an internal error after running for 3 hours, only having completed 18 out of 72 tests.  The 72 includes the 44 current myhdl tests.  So it seems like that could very well exceed the 6 hour time limit.  But, at least for testing the simulation modules, it should work fine.

Hmm. Well, 6 hours is better than travis-ci that IIRC cuts you off after 1 hour. But, I did do a quick (heh) test by running the tests for the verilog-pcie repo with pytest -n 2 as it seems like it runs with two cores in github-actions, and it crashed with xdist reporting an internal error after running for 3 hours, only having completed 18 out of 72 tests. The 72 includes the 44 current myhdl tests. So it seems like that could very well exceed the 6 hour time limit. But, at least for testing the simulation modules, it should work fine.

There are some "tricks" one can do. I can try to look at this.


Nice work!

First of all, let me say it's a very good job. Well done!
Your code is good and I'd like to help doing some improvement.
During the next weekend, I will set up a website for my alliance and I was searching for maps on the web. Yours seems to be the best one.
If you are interested I will share my ideas and my code with you and also I'd like to help you testing you discord's bot and, eventually, bringing there also some mates to help to update and improve data from the game.

Thank you for your interest! I'd like to hear your opinions and ideas. I would definitely appreciate having some more data contributors.

https://discord.gg/ZZdWNE  <--join asap, please just you. I will boot any unexpected guests. I'm not ready to open the doors yet.


Can't download from VGTV

I'm trying to download a documentary from VGTV but I am getting an error.
C:\Users\User\Downloads>youtube-dl --verbose "http://www.vgtv.no/#!/video/127205/inside-the-mind-of-favela-funk"
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', 'http://www.vgtv.no/#!/video/127205/inside-the-mind-of-favela-funk']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2016.08.13
[debug] Python version 3.4.4 - Windows-10-10.0.14393
[debug] exe versions: none
[debug] Proxy map: {}
[VGTV] 127205: Downloading media JSON
[VGTV] 127205: Downloading m3u8 information
WARNING: Failed to download m3u8 information: HTTP Error 403: Forbidden
[VGTV] 127205: Downloading f4m manifest
WARNING: Unable to download f4m manifest: HTTP Error 403: Forbidden
ERROR: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpz_7f3hc1\build\youtube_dl\YoutubeDL.py", line 691, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpz_7f3hc1\build\youtube_dl\extractor\common.py", line 347, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpz_7f3hc1\build\youtube_dl\extractor\vgtv.py", line 199, in _real_extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpz_7f3hc1\build\youtube_dl\extractor\common.py", line 901, in _sort_formats
youtube_dl.utils.ExtractorError: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

This video is geo restricted. Can you watch it in browser in the first place?

Yeah, though through VPN since I am currently on vacation.

If it's regular VPN then it must be active when you run youtube-dl. If you're using a browser plugin like Hola VPN then it won't work since only browser is affected.

My VYPR VPN is active while running it.

Not all VPNs affect the whole system. You may want to ask the VPN provider for how to use it in applications other than browsers.


chore: fix typo (wrong path)

data/img/ocean.jpg appears to be unused throughout the project. All references are currently  /static/images/ocean.jpg.

Thanks for the fix


SCA with Php Inspections (EA Extended)

1. Why is this change necessary?
Resolves implementation defects (misplaced operator + https://bugs.php.net/bug.php?id=62577 + strings normalization), modernizes codebase according to PHP language level specified in composer.json, eliminates some of unnessecary functions/methods calls.
2. What does this change do, exactly?
Applies automatic fixes for cases reported by Php Inspections (EA Extended).
3. Describe each step to reproduce the issue or behaviour.
Run code inspection from PhpStrom with installed Php Inspections (EA Extended) plugin
4. Please link to the relevant issues (if any).
none
5. Which documentation changes (if any) need to be made because of this PR?
none
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfill them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-20375
Please use this issue to track the state of your pull request.

Hi @kalessil, thank you very much for your contribution! 💙


Replace the øbin.net by our own

Is this possible in any way?
Or currently not supported?
Thanks in advance.

Not supported and unlikely to be supported in the future. However, the Licence allows you to change it in the source code if you wish: we don't require attribution.


[Enhancement] json_extract_double Unable to parse double data of type string

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
json_extract_double function cannot parse double data of type string，can this feature be added.

Of course, I know that json_extract_string functions can achieve this function, which can parse both double and string types simultaneously to obtain the correct result.
Solution
json_extract_double add the function to parse double data of string type
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

let me see

Replace with select cast(json_extract_STRING('{"id":"123"}','$.id') as Double)


Repo sync for protected CLA branch

The pull request is created from master637569761408945082 to master to fix git push error for protected CLA branch

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


Suggestion: Msg string formatting without newline and tab characters

The Msg type should have a method that returns a properly formatted string for logging purposes. Outputting to the dig format is okay for one-offs, but when used for logging, it retains all the \t and \n strings which is painful to parse visually or programmatically.
This is similar to #163, but the problem is more generally with the whole String() method for the Msg type.

For anyone who came here looking for a string formatting function to remove the newline and tab characters from msg.String() output, here is the function I've used:
func formatMsgForLog(msg dns.Msg) string {
	return strings.ReplaceAll(strings.ReplaceAll(msg.String(), "\t", " "), "\n", " ")
}

you, indeed need to do the above are write your own formatter taking in a *dns.Msg


AR Locale getDaysNames

Is your feature request related to a problem? Please describe.
For 'ar' locale, the days' names aren't displayed properly, making it hard to distinguish between the days, please find the below screenshot.

Describe the solution you'd like
getDayNames utils/util.ts  generates the day names based on locale and week start.
it also takes only the first 2 characters from each day's name.
my suggestion is to have this method as a default one, and to allow passing a different getDaysNames method to override it if needed.

Will be added, also, you can override the default labels with a slot calendar-header


HARP-11448: Adds actual deployment step to github actions publishing …

…workflow
Signed-off-by: Frauke Fritz<EMAIL_ADDRESS>Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

rebase please

retest please


fix:[CORE-1602] Delete duplicate azure policy 'Enable Transparent Data Encryption on SQL Databases'

Description

deleted the policy  'Enable Transparent Data Encryption on SQL Databases' with policyId 'Data_Encryption_SQL_version-1_SDE_sqldatabase' from rds tables, since it is a duplicate of 'Enable Transparent Data Encryption for SQL Database'
attached ES query to remove related violation documents

Fixes # (issue)
Removes the policy 'Enable Transparent Data Encryption on SQL Databases'
Type of change
Please delete options that are not relevant.

[ ] 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

[ ] check both the user and admin Policies screen. This policy 'Enable Transparent Data Encryption on SQL Databases' must not be present
[ ] Violations for this policy are not seen in violation screen

Checklist:

[ ] My code follows the style guidelines of this project
[ ] My commit message/PR follows the contribution guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] 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

Other information:
List any documentation updates that are needed for the Wiki

closing this due to conflicts and creating new PR


Update the code demo for Link Overlay with a Routing Library

Subject
LinkOverlay
Description
When trying to hoist a link in an encapsulating component. The code demo provided by the docs results in a Hydration Error. It is an issue that is closed in the core Chakra UI library here.
If this is done the docs way, the result wraps an  tag inside another  tag that results in the above hydration error.

To work around this in Next JS 13.
 <LinkBox as="article">

        <LinkOverlay as={NextLink} href="#" passHref>
          Some blog post
        </LinkOverlay>

        As a side note, using quotation marks around an attribute value is
        required only if this value is not a valid identifier.

      Some inner link
    </LinkBox>

This would result in the following required output.

I have checked for any previous closed or related open issue. I have found none.
I would appreciate if I could change the docs demo code if possible.
Thank you.

Thanks for reporting this issue, this can be worked on 🚀

Can you please assign this to me?

Done!

I have fixed this in this PR #1355


Load Model Checkpoints with Arbitrary Output Dimensions

This adds support for pretraining and subsequent finetuning on different datasets where the number of classes / the output dimension of the model differs.
If the output dimensions of the last layer found in the checkpoint and the current model differ, the weights of the last linear layer are skipped. This also applies to the optimizer state.
If both datasets (and therefore the state dict and model) share the same output dimension, skip_last_layer: True skips the last linear layer explicitly.
Previously, we supported a pretrained attribute in the  model, optimizer, and scheduler configurations.
These attributes are now all moved to the model configuration, as they should be grouped together, and are specified as follows:

model_checkpoint: The path to the model checkpoint file.
If the output dimensions between the checkpoint and the model configuration do not match,
the checkpoint will be loaded without the last linear layer.
optimizer_checkpoint: The path to the optimizer checkpoint file.
If the output dimensions between the checkpoint and the model configuration do not match,
the checkpoint will be loaded without the last linear layer, similar to the model checkpoint.
If no model checkpoint is provided, :attr:skip_last_layer is automatically set to True.
scheduler_checkpoint: The path to the scheduler checkpoint file.

Also updated the docs explaining the usage of the new attributes (the old pretrained attribute was not mentioned) and added a simple integration test to cover loading all 3 checkpoints.

Ok i have greatly simplified the implementation here to mitigate hidden control flow that the user may not be aware of and added more clear documentation.

allow the last layer to be both linear or convolutional. I did not add a try catch block since it will raise a RuntimeError anyways if loading fails here.
skip_last_layer is now true by default, clearly distinguishing between continuing training and checkpointing with the intention of targeting a new task / dataset.
documentation now clearly outlines the flaw with the current approach: we cannot accurately identify the last layer if it is not specified last in the modules (we had this issue before as well).

Okay, thanks a lot for all the consideration, seems like a good solution to me :)

@millinma so should be ready to merge? I guess we could also release v0.2.0 afterwards as we have quite the amount of new features + fixes.

Yes, ready to merge I would say :)

Not a super expert on the versioning. So don't know if it should be 0.1.2 or 0.2.0

We should definitely follow semantic versioning to some extent, meaning major releases for incompatible changes, minor for feature releases, and patch for bug fixes only as soon as we reach v1.0.0.
Since we are below v1.0.0, i would stay with minor releases for all feature releases (including incompatible changes), and patch releases for fixes only.
This should be quite clear, as we are in a super early stage of development and things may change rapidly and drastically.
I would also collect some useful features and manually decide when a new release should be made, depending on how long the last release was made and how much new things are added, so we dont just spam releases.
However, for urgent fixes, i would instantly release a patch.


ch6 & ch7

Job d2l-zh/PR-619/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-619/

Job d2l-zh/PR-619/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-619/


Archetype Build Problem - Groovy Dependency

Expected Behaviour
Running the following command should create a new AEM SPA project and successfully execute the build:
mvn -B archetype:generate -DarchetypeGroupId=com.adobe.granite.archetypes -DarchetypeArtifactId=aem-project-archetype -DarchetypeVersion=23 -DaemVersion=6.4.8 -DappTitle="My SPA Site" -DappId="spasite" -DgroupId="com.spasite" -DfrontendModule=angular -DincludeExamples=n
Actual Behaviour
During the build process the step "Executing META-INF/archetype-post-generate.groovy post-generation script" hangs for a bit, then the build fails with the following error:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.1.2:generate (default-cli) on project standalone-pom: startup failed:

[ERROR] General error during conversion: Error grabbing Grapes -- [unresolved dependency: org.codehaus.groovy#groovy-all;2.4.8: not found]

[ERROR] java.lang.RuntimeException: Error grabbing Grapes -- [unresolved dependency: org.codehaus.groovy#groovy-all;2.4.8: not found]

Steps to Reproduce
Run the following command in a command window to create a new project:
mvn -B archetype:generate -DarchetypeGroupId=com.adobe.granite.archetypes -DarchetypeArtifactId=aem-project-archetype -DarchetypeVersion=23 -DaemVersion=6.4.8 -DappTitle="My SPA Site" -DappId="spasite" -DgroupId="com.spasite" -DfrontendModule=angular -DincludeExamples=n
Platform and Version
mvn: 3.6.3
AEM: 6.4.8
Java: 1.8

@rson25 how did you solve it?

This issues doesn't seem to be related to the archetype , see:
https://stackoverflow.com/questions/16871792/groovy-grab-download-failed
So closing this issue for now. Reopen if you think this issue needs to be solved inside the archetype project itself.

this should be fixed in archetype. What kind of archetype is this, if it's not working initially? it's useless. delete it or fix it!

In my case the problem was caused by groovy. In this step groovy-all package is downloaded. But because problems on jcenter.bintray.com download was not successful. Unfortunately the log does not tell you what the true problem is.
I manually installed groovy framework and tried to install the dependency manually: grape -V resolve org.codehaus.groovy groovy-all 2.4.8
It didn't work too, but were more verbose about what was wrong:
ERROR: SERVER ERROR: Gateway Time-out url=https://jcenter.bintray.com/org/codehaus/groovy/groovy-all/2.4.8/groovy-all-2.4.8.jar.sha1
Trying again and again I got several error types. The server was very creative in this case.
The dependency could also be downloaded from another repository or using another way.


⚠ ClamAV has degraded performance

In a3ef3ee, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 73 ms

Resolved: ClamAV performance has improved in cef3588.


Batching - managed metadata / taxonomy fields - do not query on Add-PnPListItem

When using Add-PnPListItem with Batch specified and item having managed metadata / taxonomy field value specified (term name, not guid), there are still http requests made by PnP.Powershell to get GUID for term that is set in Add-PnPListItem Values
Ideal solution would be to get GUIDs for the terms specified by name in one BATCH before executing BATCH that actually adds items to the list.
This is mostly nice to have thing as I imagine this would be quite hard to implement.

Actually it's fixed already in the latest nightly :-) If you install 1.3.16-nightly you'll notice we cache information for managed metadata fields. Batching the requests for all terms will unfortunately cause a large overhead in processing. The way it works now is:
Lookup guid and label for term and cache
Add item to batch
Check if guid and label has been cached, if not, retrieve info and add to cache, if yes, use from cache.
Add item to batch
So if you add hundreds of items to a list which use the same taxonomy terms you'll see only a few calls being made.


Added sensors for current and max CPU package temp

failing due to rebase, wait for #29 to be merged before rebase to fix

Fixed some build errors, otherwise LGTM


UI Propose: Only one classifying concept per KB

Due to limitation of the algorithm (see https://github.com/odalic/sti/issues/202), when new class is proposed for the column header, it has to replace the existing from the same KB. So it is allowed to have only one classification for each KB.
So the behavior should be the same as in case of proposing entities disambiguating cell value, where also only one selected disambiguation per KB is allowed

Does not work, I was currently testing develop - commit 8fec49023d51674fa47d21bc5ebd002bf7ac640f
and I was able to add more classes:

Not working. When you propose a second class for a header, it gladly allows it to add it to the selection. As of https://github.com/odalic/odalic-ui/commit/a1e652df81264f006a4a6eec878c77927f6fb7fc .

Tag as in-test and assign to me, @KataBoku , when the solution to #153 is pushed (which should arguably fix the reported problems by me and @tomas-knap ). I will check tomorrow.


How do I capture keypresses?

I'm able to catch keypresses on the terminal, but even if I try to stop propagation, they still make their way into xterm-pty.
I would like to add some hooks for things like arrow keys. Any suggestions? Thanks!
xterm.onKey(e => {
    e.preventDefault();
    e.stopPropagation();
});

I think it would be better for you to ask the xterm.js authors how to suppress event notifications to addons. I don't think that it would make sense for every addon like xterm-pty to provide such a hook.
If there is something wrong with xterm-pty as xterm.js addon in terms of event handling, I will be happy to fix it.
Note that xterm-pty uses onData and onBinary instead of onKey.


GIF conversion broken due to simple FreeImage misconfiguration

The ugoira to GIF conversion implemented in issue #135 is broken in the 10-12 download, but only trivially. When it encounters a ugoira file, this is what happens:
Creating ugoira archive => D:\Artist - 123456789.ugoira
Deleting zip file => D:\Artist - 123456789.zip
processing ugoira...
Imageio: 'freeimage-3.15.4-win32.dll' was not found on your computer; downloading it now.
Error while fetching file: (0, 'connection closed unexpectedly').
Error while fetching file: (0, 'connection closed unexpectedly').
Error while fetching file: (0, 'connection closed unexpectedly').
Error while fetching file: (0, 'connection closed unexpectedly').

[Previous 5 lines repeat 36 times]
Traceback (most recent call last):
  File "PixivUtil2.py", line 692, in process_image
  File "PixivHelper.pyc", line 655, in ugoira2gif
  File "imageio\core\functions.pyc", line 181, in imread
  File "imageio\core\functions.pyc", line 108, in get_reader
ValueError: Could not find a format to read the specified file in mode 'i'
Error at process_image(): (<type 'exceptions.ValueError'>, ValueError("Could not
 find a format to read the specified file in mode 'i'",), <traceback object at 0
x0404B260>)
Dumping html to: Error medium page for image 123456789.html
Stuff happened, trying again after 2 second ( 1 )
Traceback (most recent call last):
  File "PixivUtil2.py", line 412, in process_member
  File "PixivUtil2.py", line 692, in process_image
  File "PixivHelper.pyc", line 655, in ugoira2gif
  File "imageio\core\functions.pyc", line 181, in imread
  File "imageio\core\functions.pyc", line 108, in get_reader
ValueError: Could not find a format to read the specified file in mode 'i'
Processing Image Id: 123456789
Title: ????????????
Tags : ??? ???? ???? ????? Fate/GrandOrder, Live2D, ?????????????????
Date : 2016-10-05 17:58:00
Mode : ugoira_view
Image URL : http://i1.pixiv.net/img-zip-ugoira/img/2016/10/05/17/58/37/123456789_
ugoira1920x1080.zip
Filename  : D:\Artist - 123456789.zip
Checking local filename... Getting remote filesize...
Using Referer: http://www.pixiv.net/member_illust.php?mode=medium&illust_id=123456789
        File exist! (Identical Size)

#2
Processing Image Id: <next>

The FreeImage library is mentioned without explanation in the readme file. It turns out the required DLL is available [here] (https://github.com/imageio/imageio-binaries/blob/master/FreeImage-3.15.4-win32.dll). The function works again after placing this file in the Windows\System32 directory.
This was a bit confusing because the current version is 3.17 and is on the project's main page, but causes PixivUtil to ignore Ugoira files.
Could this file be distributed with the program libraries? Or at least with the program, with a better explanation in the readme? :3

The function works again after placing this file in the Windows\System32 directory

What about placing it on the app folder?I'm not comfortable placing dll on system32.
Also related for non-windows system.

current version is 3.17

Is it not working with 3.17? If yes, then I can add freeimage-3.15.4-win32.dll to the repo.

Indeed, first I tried 3.17 in the pixivutil program directory, then in the system32/64 folders.
Neither of them worked in the app folder. As I deleted all the animated files in a very long directory I was downloading, this case would skip over the ugoira files entirely and then move on. Only when I placed 3.15.4 in the system folders did it correctly re-download the animations I have previously deleted, and convert them directly to JPEG.
So speaking for windows, adding 3.15.4 to the repo would seem to be exactly what it craves. Mac and linux might require their own testing of this situation, because the only versions that were archived in the imageio-binaries project were 3.10.x, and I have no clue what in the coding made windows demand the older version it did (and since it tried to download files that are museum archived, it might indicate there's a block of old code somewhere here).
If OSX and linux don't happen to call for the 3.10.x version archived on github, it might be simplest (or at least, the only) solution to just bring everything up to speed at 3.70. Though four years have passed, the http://freeimage.sourceforge.net/changeslog.html seems to be a mixture of high-end image processing/format usage and legacy capabilities.
Though <[Mihail Naydenov] fixed GIF plugin LZW decoder failing on some image> is one of the first things they fixed after 3.15.4 ^^;;;; Or does PixivUtil use the library for anything besides the animated GIF conversion?

nope, only for gif conversion, which is working


About Impact_Qualification issue

Does anyone know how to compile this (below down XML format)?

I have tried the below down script, but it didn't work
//This is a test script (this script is right)
impact = ImpactAssessment()
impact.effects = Effects("Unintended Access")
breach.impact_assessment = impact
//This is test script(I think it will be the same impact.effects,but it didn't work)
impact.Qualifications = ImpactQualification()

How about this:
impact.impact_qualification = ImpactQualification("Distracting")

2 would not work since it's not a member of the ImpactQualification vocabulary.


Pull Request to address Issue #12

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
The changes are here to align the new "Slot Programming Mode" property  for NI-904x and NI-905x families to the setting set in Target Main Configuration page by control "FPGA / Scan mode...". Modifications done are applied during AutoDetect and also in ActionVI called at deploy.
Why should this Pull Request be merged?
Cf. Issue #12 It's not customer's specific. It would be beneficial to all users of these new families, not break existing features.
What testing has been done?
Tested with NI-VS 2018 only.
I had a NI-9049 with 3 C-Series modules inside and also a NI-9145 attached to it. I did couple of tests (switch from one mode "FPGA" to "Scan Mode" and vice-versa) and checked that modules from Local Chassis are detected correctly when set in Scan Mode. Same test done with NI-9040 chassis, same local modules and a NI-9145. I also tested a NI-9082 (PharLap based), kind of non regressive testing.

Hi @rtzoeller,
I made a new commit to integrate your changes:

I defined a TypeDef for the FPGAScanInterfaceMode to not deal with Integer Value and it's now passed to sub-VI.

To be dependent to an input list or a global, I discovered that SystemConfiguration API doesn't return same items depending on cRIO type, I did tests with cRIO-904x controllers but also NI-9068 and a NI-9082. The NI-906x and NI-908x don't support Slot Programming Mode. Only with cRIO-904x, I was getting set of properties to play with SlotProgramming Mode property.  Where it looks OK, I would like to get a confirmation but from which NI team? It's something I observed but not something I had read before testing.

I adjusted connector panes.

I couldn't revert to previous version only the 2 files you asked, So, I reverted the entire Commit.-

I built the custom device and ran the existing tests successfully.
I would like to see a test added in the same vein as the existing ones for combo devices, so that we can validate this fix does not break in the future. I envision that test doing the following (assuming a 9045 with three 9401s in the same setup as the specialty digital tests):

Configure one module in DAQmx mode, one module in scan mode, and one module in FPGA mode.
Deploy a system definition with all three modules added; it should switch them all to scan mode as part of deployment.
Undeploy after waiting for some time.
Read back the module modes and assert that they are in scan mode.
If they weren't converted to scan mode, set them back manually so other tests don't fail.

@VincentRuault do you feel comfortable expanding the existing tests to add this one? If not, I can add the test and contribute it to the pull request.

Hi Ryan,
No problem to add the test. Where do I add it? Is-it in the "What testing has been done?" section in the first post?

Sorry, I wasn't particularly clear. I was referring to adding an automated test built on top of the
testing tools. There are existing tests in the Scan Engine - Tests.lvproj project, which make use of VI Tester to run automated tests.
There is some documentation in the custom device testing tools repository and the other tests in this repo are decent examples. I am happy to write the test if that is easiest.

[ ] @VincentRuault can you explain what errors you expect to occur when getting the System Hardware Expert in Align cRIO Programming Mode.vi?

I am trying to understand what errors could occur (and if we can safely ignore them). We should not be clearing all errors unconditionally, since this will hide legitimate issues.

[ ] What is the motivation for ignoring errors inside the property nodes?

Minor nitpick: the error in terminals do not need to be marked as required, and can be marked as recommended.

I can add an automated test for this validation.

[ ] Should this be "all values match"? I believe this would remove the need to filter things (like network devices) out.

I just commit a new version of the Align Programming Mode.vi.
I followed the idea to use "all values match" and dig more with extra criterias for the filter. It now allows to retrieve only slots supporting "Slot Programming Mode" property. It simplifies a lot the logic behind.
I changed connector pane Error In to be Recommended.
About Test VI, I haven't had time to look at that. It might be faster if you created the Test yourself. I had a quick look and I installed Testing Tool repository but I'm still missing some Packages and read the documentation before doing anything.

I like the implementation cleanup!
Two things:

[ ] We should only update the FPGA Scan Interface Mode for modules present in the custom device; any slots not in the custom device should be untouched. Right now we set the mode for all modules, meaning we will take modules used by other custom devices or parts of the system out of their existing modes, e.g. X-NET modules will be broken.

[ ] (Minor) You have boolean wires running behind a case structure and overlapping other wires, which makes it unclear how things are connected.

One more minor thing:

[ ] Passing the expert into FindHardware is measurably faster than passing it into the property node. Passing it into FindHardware will restrict our search to that expert, while passing it into the property node will result in it searching all of the experts and filtering them out.

I'll fix wiring and also change how to specify the expert.
About your comment: _"We should only update the FPGA Scan Interface Mode for modules present in the custom device; any slots not in the custom device should be untouched. Right now we set the mode for all modules, meaning we will take modules used by other custom devices or parts of the system out of their existing modes, e.g. X-NET modules will be broken."_Is you comment limited to XNET? Because I don't really see any other Custom Device, correct me if I'm wrong. In terms of limitations, how would you envision that? Should we detect XNET modules Serial modules and not update them?

No, it should not just be limited to XNET.
Imagine that I have a cRIO with 8 slots, all of which are populated. I want to use the Scan Engine EtherCAT custom device with slots 1-3, but use other custom devices or control methods for slots 4-8. They could be X-NET, DAQ, or any other module type. In this case, the custom device would only have slots 1-3 populated in the local chassis; the other slots would be listed as empty. You should use the populated status of the chassis in the custom device to determine which slots to update.
The status of which modules are populated in the custom device is saved in the system definition; you can use the "Local Chassis" GUID (look in Scan Engine GUIDS.vi) to find the chassis, and then look at the children of that to find the ones with the "Slot" GUID. From there, you can use the methods on the module to get the slot number (look at Scan Engine Slot Page.vi to see how it is done there).

Do you confirm that we are not distinguishing the changes to be applied during Auto-Detect of the Configuration and during actual Sysdef Deployment, right? I would imagine that during Auto-Detect of the Configuration, we can be systematic* but during Deployment, that's when we need to take into account which slots are actually handled by SEEC CD. Am-I right?

I'm assuming that, after SEEC CD Configuration Auto-Detect, user will configure other CDs or DAQ tasks, potentially affecting some slots handling. Valid assumption?

We should not change the scan mode during auto-detect at all. We are detecting what is in the system at this point, not modifying it.
This reconfiguration should only be run during deployment, since at this point the user has explicitly told the custom device which modules it owns (by adding them to the custom device).

@VincentRuault I tried this on a 9045 and the functionality worked as expected! Thank you again
I will test this on other controllers/chassis tomorrow. I am not planning on contributing an automated test to this pull request; https://github.com/ni/niveristand-custom-device-testing-tools/issues/33 is blocking the test I have written from being generic.

I am not sure why me pushing closed this pull request. I will open another one with the same changes, since I can't re-open this one.


ServerRequestInterface::getServerParams() are mixed

For example:

GATEWAY_INTERFACE is a string
argv is an array

Options include:

making it a shape
splitting it into many methods
make it return a new ServerParams object with many methods

@fredemmott I personally like the third option as it would be easier to call a getter instead of thinking about param name.
We should probably add the interface and a basic implementation which will return params values from $_SERVER.  What do you think about it?
Also, according to the php-doc of the getServerParams() it says the following

The data IS NOT REQUIRED to originate from $_SERVER.

So that means that some users might want to extend the interface we define. How could we handle that?

So that means that some users might want to extend the interface we define. How could we handle that?

If we take the third option, callers that need extensions can explicitly require an implementatino rather than the interface, or do an instanceof check - the interface does not need to define extension points.

The data IS NOT REQUIRED to originate from $_SERVER.

I'm reading this as saying that providing fake data (e.g. for unit tests) is fine, as is supporting SAPIs that don't use $_SERVER (if any); I'm not reading it as saying we need to support arbitrary data.

So that means that some users might want to extend the interface we define. How could we handle that?

They extend the interface, literally, and use the type system to handle it :) We dont' need to handle implementation-specific data in the interfaces, and this is a source of type issues in PSR-7.


[tool_crash] _TypeError: (#0      AndroidStudioJavaGradleConflictMigration.migrate (package:flutter_tools/src/android/migrations/android_studio_java_gradle_conflict_migration.dart:107:39))

Command
flutter --no-color run --machine --track-widget-creation --device-id=emulator-5554 --start-paused --dart-define=flutter.inspector.structuredErrors=true lib\main_development.dart

Steps to Reproduce

...
...
...

Logs
_TypeError: (#0      AndroidStudioJavaGradleConflictMigration.migrate (package:flutter_tools/src/android/migrations/android_studio_java_gradle_conflict_migration.dart:107:39))
#0      AndroidStudioJavaGradleConflictMigration.migrate (package:flutter_tools/src/android/migrations/android_studio_java_gradle_conflict_migration.dart:107:39)
#1      ProjectMigration.run (package:flutter_tools/src/base/project_migrator.dart:84:16)
#2      AndroidGradleBuilder.buildGradleApp (package:flutter_tools/src/android/gradle.dart:280:15)
#3      AndroidGradleBuilder.buildApk (package:flutter_tools/src/android/gradle.dart:208:11)
#4      AndroidDevice.startApp (package:flutter_tools/src/android/android_device.dart:578:29)
<asynchronous suspension>
#5      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:468:33)
<asynchronous suspension>
#6      Future.wait.<anonymous closure> (dart:async/future.dart:525:21)
<asynchronous suspension>
#7      HotRunner.run (package:flutter_tools/src/run_hot.dart:421:34)
<asynchronous suspension>
#8      AppDomain.launch.<anonymous closure> (package:flutter_tools/src/commands/daemon.dart:649:9)
<asynchronous suspension>
#9      AppDomain.launch (package:flutter_tools/src/commands/daemon.dart:647:5)
<asynchronous suspension>
#10     RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:638:15)
<asynchronous suspension>
#11     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1294:27)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:296:9)

[✓] Flutter (Channel master, 3.10.0-17.0.pre.32, on Microsoft Windows [version 10.0.22621.1555], locale fr-FR)
    • Flutter version 3.10.0-17.0.pre.32 on channel master at C:\tools\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 9241329b46 (7 hours ago), 2023-04-30 06:40:27 -0400
    • Engine revision c796390d14
    • Dart version 3.1.0 (build 3.1.0-56.0.dev)
    • DevTools version 2.23.1

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at D:\AppData\SDK
    • Platform android-TiramisuPrivacySandbox, build-tools 33.0.1
    • Java binary at: C:\Program Files\Java\jdk-19\bin\java
    • Java version Java(TM) SE Runtime Environment (build 19.0.1+10-21)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[!] Visual Studio - develop for Windows (Visual Studio Build Tools 2019 16.11.22)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
    • Visual Studio Build Tools 2019 version 16.11.33130.400
    ✗ The current Visual Studio installation is incomplete. Please reinstall Visual Studio.

[✓] Android Studio (version 2021.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] Connected device (4 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 13 (API 33) (emulator)
    • Windows (desktop)            • windows       • windows-x64    • Microsoft Windows [version 10.0.22621.1555]
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 112.0.5615.138
    • Edge (web)                   • edge          • web-javascript • Microsoft Edge 112.0.1722.64

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 135454af32477f815a7525073027a3ff9eff1bfd
Plugins
app_links-3.4.2
package_info_plus-3.1.2
path_provider-2.0.14
path_provider_android-2.0.27
path_provider_foundation-2.2.2
path_provider_linux-2.1.10
path_provider_windows-2.1.6
sentry_flutter-7.5.0
shared_preferences-2.1.0
shared_preferences_android-2.1.4
shared_preferences_foundation-2.2.1
shared_preferences_linux-2.2.0
shared_preferences_web-2.1.0
shared_preferences_windows-2.2.0
sign_in_with_apple-4.3.0
sign_in_with_apple_web-1.0.1
sqflite-2.2.8
uni_links-0.5.1
uni_links_web-0.1.0
url_launcher-6.1.10
url_launcher_android-6.0.31
url_launcher_ios-6.1.4
url_launcher_linux-3.0.5
url_launcher_macos-3.0.5
url_launcher_web-2.0.16
url_launcher_windows-3.0.6
webview_flutter-4.2.0
webview_flutter_android-3.6.2
webview_flutter_wkwebview-3.4.0

Closing this as a duplicate of https://github.com/flutter/flutter/issues/125712 which has more details on https://github.com/flutter/flutter/issues/125712#issuecomment-1528101662 and possible fix as mentioned https://github.com/flutter/flutter/issues/125712#issuecomment-1530238853, so please upgrade to latest master and see if you still get the same crash or not. If yes, please write in the comments and I'll reopen it.


Define encoding type for multipart/form-data file upload is not possible according to the 3.0 Specification

According to the "https://swagger.io/docs/specification/describing-request-body/multipart-requests/", there's a possibility to define the content type to the multipart/form-data body part.

I tried with different jaxrs annotations, but can't able to generate the YAML in the expected format.
Here's my sample code:

And the following is the generated YAML for the above code:

But I would like to generate the YAML in the following format.

Tried in many different ways. The following file contains all the samples.
IOpenApiRestService.txt
Can someone please explain what annotations have to use exactly to generate the YAML in the expected format?
Thanks in adavance.

I tried in different ways. Attach file contains all samples.
IOpenApiRestService.txt

This is a tooling issue and not a spec one. Please file the question at the respective tool you're using.

In our project we are using following maven dependencies.

Does it mean to create the issue in https://github.com/swagger-api/swagger-core/issues?

Yup, and I see you've filled a ticket there. Thanks.

Created issue in swagger core https://github.com/swagger-api/swagger-core/issues/3387


Debug mode not printing a PANDAS dataframe

The latest update of the Microsoft Python extension was causing some weird behaviors. For example, when in debug mode it would not print a pandas dataframe, it would just print None if I typed print(df). Also, when resetting the Python Interactive window using %reset, it would open the Command Palette window to confirm with a Y or N to reset, not inline. I downgraded  the Microsoft Python extension to 2019.11.50794 from 2020.157204 and these two issues disappeared.

%reset asking is by design. That's what Jupyter notebooks do. We recently added support for reading from stdin for Jupyter commands and it brings up the VS code quick input box to handle that. You can use %reset -f to skip the prompt.
However the print(df) is not expected. I can't repro the problem though. Not sure what you mean by debug mode? Are you debugging a cell? Are you sure you didn't run %reset first?

@rchiodo I think it's just this issue with the normal debugger.
https://github.com/microsoft/ptvsd/issues/2036
@tenberg Does the above look like the issue you are hitting?

I apologize for the bad description. I'm fine with %reset asking for y/n in the quick input box when resetting in the Python Interactive window; in the previous version (2019.11.50794) it never asked, it just reset everything.
@IanMatthewHuff, yes microsoft/ptvsd#2036 is the issue I'm seeing.


Where is the code?

...

I'm a little behind on cleaning it up; hopefully I'll have it up in a few weeks.

where is your code? plz.


Appstudio update test-component-pac-rhvc

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-rhvc-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
21 seconds
clone-repository

✅ Succeeded
32 seconds
build-container

✅ Succeeded
48 seconds
deprecated-base-image-check

✅ Succeeded
47 seconds
inspect-image

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
33 seconds
clamav-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
9 seconds
optional-label-check

✅ Succeeded
9 seconds
label-check

✅ Succeeded
7 seconds
show-summary

✅ Succeeded
6 seconds
show-sbom


amplify pull not pulling down Cognito user pool trigger data

Describe the bug
In the Triggers settings in Cognito User Pools, I have set a trigger to one of my Lambda functions. After running amplify pull, it does not pull down the trigger settings to my local code. When I do the opposite, and amplify push with an empty triggers object in parameters.json, it overwrites the previously selected setting in the User Pool trigger section and nullifies it.
Amplify CLI Version
4.16.1
To Reproduce
In amplify > backend > auth > [id] > parameters.json ensure the triggers object is empty. On the Cognito console, under triggers settings, select a Lambda function as a trigger. Run amplify pull.
Expected behavior
The triggers object is populated locally with data about the Lambda function to trigger.
Desktop (please complete the following information):

OS: Mac
Node Version: 12.14.1

Amplify CLI uses cloudformation to provision resources, does not support syncing of the changes that are made using the Console. All the changes have to be pushed using CloudFormation and push operation should be done using Amplify CLI for pull command to get that change

Thanks, although I don't fully understand. So I'm able to amplify push trigger settings for Cognito set in paramters.json, but amplify pull won't pull those same setting back to the local environment?
My aim is to define all settings not in the console, but in my code. I only wanted to pull the trigger settings so I can see what the syntax is like. Is the example json here what I should use to configure a trigger from parameters.json? If so, I'm a little confused where I identify which Lambda function to call (is it callerContext.clientId?). Should the request object be empty, since Cognito would fill that in? If I'm looking in the wrong place, do you have a link to the documentation for the triggers object in parameters.json? Thanks.

@fi5u Sorry for the late response, but amplify pull wouldn't be able to pull in changes made from the cognito console. amplify pull helps in bringing down CloudFormation stack changes made by another team-member (if there are multiple devs working on the project). You can configure cognito triggers using the amplify add/update flow.


Some more cleanup

This cleanup fixes a problem where Model properties weren't getting the correct types if the string-dates flag was specified.
There's also just some other cleanup in here too.

🤖 AutoRest automatic feature coverage report 🤖
feature set version 2.3.14
❌ General: 92%
40 out of 522 features are not covered by tests
ConstantsInBody, ConstantsInPath, FileStreamVeryLarge, FormdataStreamUploadFile, HttpRedirect300Get, HttpRedirect300Head, HttpRedirect301Get, HttpRedirect301Put, HttpRedirect302Get, HttpRedirect302Head, HttpRedirect302Patch, HttpRedirect303Post, HttpRedirect307Delete, HttpRedirect307Get, HttpRedirect307Head, HttpRedirect307Patch, HttpRedirect307Post, HttpRedirect307Put, ResponsesScenarioC200MatchingModel, ResponsesScenarioC201MatchingModel, ResponsesScenarioC404MatchingModel, StreamUploadFile, UrlPathsArrayCSVInPath, UrlQueriesArrayMultiEmpty, UrlQueriesArrayMultiNull, UrlQueriesArrayMultiValid, allowedValueEnum, expectedEnum, getByteEmpty, getByteInvalid, getComplexPolymorphismComplicated, getEnumReferenced, getEnumReferencedConstant, getStringMultiByteCharacters, putComplexPolymorphismComplicated, putEnumReferenced, putEnumReferencedConstant, putStringMultiByteCharacters, roundTripEnum, unexpectedEnum
❌ Azure: 88%
14 out of 118 features are not covered by tests
AzureMethodQueryUrlEncoding, AzureODataFilter, AzurePathQueryUrlEncoding, AzureRequestClientIdInError, AzureSwaggerQueryUrlEncoding, AzureXmsCustomNamedRequestId, AzureXmsCustomNamedRequestIdParameterGroup, AzureXmsRequestClientIdNull, CustomHeaderPostAsyncSucceded, CustomHeaderPostSucceeded, CustomHeaderPutAsyncSucceded, CustomHeaderPutSucceeded, LRONonRetryPut201Creating400InvalidJson, PagingOdataMultiple

🤖 AutoRest automatic feature coverage report 🤖
feature set version 2.3.14
❌ General: 92%
40 out of 522 features are not covered by tests
ConstantsInBody, ConstantsInPath, FileStreamVeryLarge, FormdataStreamUploadFile, HttpRedirect300Get, HttpRedirect300Head, HttpRedirect301Get, HttpRedirect301Put, HttpRedirect302Get, HttpRedirect302Head, HttpRedirect302Patch, HttpRedirect303Post, HttpRedirect307Delete, HttpRedirect307Get, HttpRedirect307Head, HttpRedirect307Patch, HttpRedirect307Post, HttpRedirect307Put, ResponsesScenarioC200MatchingModel, ResponsesScenarioC201MatchingModel, ResponsesScenarioC404MatchingModel, StreamUploadFile, UrlPathsArrayCSVInPath, UrlQueriesArrayMultiEmpty, UrlQueriesArrayMultiNull, UrlQueriesArrayMultiValid, allowedValueEnum, expectedEnum, getByteEmpty, getByteInvalid, getComplexPolymorphismComplicated, getEnumReferenced, getEnumReferencedConstant, getStringMultiByteCharacters, putComplexPolymorphismComplicated, putEnumReferenced, putEnumReferencedConstant, putStringMultiByteCharacters, roundTripEnum, unexpectedEnum
❌ Azure: 88%
14 out of 118 features are not covered by tests
AzureMethodQueryUrlEncoding, AzureODataFilter, AzurePathQueryUrlEncoding, AzureRequestClientIdInError, AzureSwaggerQueryUrlEncoding, AzureXmsCustomNamedRequestId, AzureXmsCustomNamedRequestIdParameterGroup, AzureXmsRequestClientIdNull, CustomHeaderPostAsyncSucceded, CustomHeaderPostSucceeded, CustomHeaderPutAsyncSucceded, CustomHeaderPutSucceeded, LRONonRetryPut201Creating400InvalidJson, PagingOdataMultiple

Whoops! I merged this before I committed my changes for your comments. I'll get them in my next PR.


Main file ratio

adding a new config key (main_file_ratio) to deluge and transmisson plugins so that when using the main_file_only config item, you are not forced to assume that the main file must be > 90% of the total torrent size, this ratio is now configurable. This helps a lot with shows that sometimes include samples which are potentially 10-15% of the total size.
I'm getting this PR started early as I want to start the review process right away (since I'm not super familiar with flexget plugins to begin with). I believe I got things right, or close to right at least, but I'm happy to fix style/consistency issues if there are any. I tried to add as little code as possible and keep existing code as unchanged as possible, as a result I may not be doing things the best way possible, but it will be as consistent as possible with the existing code base.
I'm testing this out on my server right now but won't really be able to see it's effectiveness for a few days.

Looking good!

Looks good to me, is this ready to go?

I believe so, I haven't run into any issues with it so far

Sweet, thanks! Want to update the wiki?

should I wait for the next master build first?

Don't think it matters if we jump the gun a bit, build will be out in 10 hours or so.

roger that. i'll post the updates later today.

btw, it breaks deluge plugin:
File "/usr/lib64/python2.7/site-packages/flexget/plugins/plugin_deluge.py", line 646, in on_get_torrent_status
if file['size'] > (status['total_size'] * opts.get('main_file_ratio')):
exceptions.TypeError: unsupported operand type(s) for *: 'int' and 'NoneType'

thanks for the heads up. I don't have a deluge test environment. I'll try and fix this asap.


feat: AU-1007: Delete documents via bash for testing.

AU-1007

What was done

This thing was fixed

How to install

Make sure your instance is up and running on correct branch.

git checkout UHF-0000_insert_correct_branch
make fresh

Run make drush-cr

How to test

[ ] Check that this feature works
[ ] Check that code follows our standards

Designers review

[ ] This PR does not need designers review
[ ] This PR has been visually reviewed by a designer (Name of the designer)

Other PRs

Link to other PR

Testattu, toimii juuri kuten pitääkin!


Bug: Table cell data dissapearing with Experimental Table and showing error mesage

We tried adding a Lexical Experimental table in our code and tried to type in data but the data is disappearing once focus is out.
On clicking back on the cell where data disappeared the error is shown as below :
We were also able to reproduce the same issue in Lexical dev as well a couple of times but it isnt consistent.
https://github.com/facebook/lexical/assets/108726680/de48c24c-2de1-441e-b68f-634377b69f30
Lexical version: 0.10.0
We have also tried with Version 0.11.0 and 0.11.1 ( the issue still exisits )

Slash command add Lexical Experimental Table.
Try to add data inside the table and do random selections.
The above error is sometimes reproducible.

Any update on this anybody from the lexical team ?

Experimental table was deprecated quite some time ago. Closing.


chore(DIST-589): Update release Github Action workflow

Use admin account Github token with write permissions for semantic release to push commit with changelog and bumped version in pacakge.json.

[BOT] Preview available: https://embed.typeform.com/d24eccc399795a50f7d6b4faa837b1bc7a30412a/embed.js

[BOT] Preview available: https://embed.typeform.com/d24eccc399795a50f7d6b4faa837b1bc7a30412a/embed.js


Tree graph node overlaps with each other, as node symbol size gets bigger.

Version
4.9.0
Steps to reproduce
Use this option in the editor
option = {
        tooltip: {
            trigger: 'item',
            triggerOn: 'mousemove'
        },
        series: [
            {
                type: 'tree',

                data: [data],

                top: '1%',
                left: '7%',
                bottom: '1%',
                right: '20%',

                symbolSize: 100
                ,

                label: {
                    position: 'left',
                    verticalAlign: 'middle',
                    align: 'right',
                    fontSize: 9
                },

                leaves: {
                    label: {
                        position: 'right',
                        verticalAlign: 'middle',
                        align: 'left'
                    }
                },

                expandAndCollapse: true,
                animationDuration: 550,
                animationDurationUpdate: 750
            }
        ]
    }

What is expected?
Each node should auto adjust their margins/distance from each other as each node symbol size change.
What is actually happening?
Nodes overlaps with each other as their symbol size changes

Hi. I would like to know any updates on this issue, though I think this is more of a feature. Hoping for a solution on this.  Thanks a lot!

@IamKennethBurla Did you find any solution to avoid overlapping of nodes in a graph?

I'd also love to know if anyone has a solution for this. Not only one fixed size for all nodes, but using a variable symbolSize for each node, would be great if the tree spaced each node properly.

Hi! I stumbled with this exact problem. My current (poor) solution is to scale down the size of the symbols depending of the amount of nodes in that level.

I dynamically obtain the width of the container, and make sure the size is scaled down on resize. But this does not serve further down the tree, as the first level nodes still overlap

Any suggestions?

any updates? I have a same issue?