GROOVY-11294: Make generated toList() and toMap() methods on records return immutable collections

https://issues.apache.org/jira/browse/GROOVY-11294

Codecov Report
Attention: 25 lines in your changes are missing coverage. Please review.

Comparison is base (6b8915f) 68.5474% compared to head (3f46926) 68.5163%.
Report is 15 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                 @@
##               master      #2044        +/-   ##
==================================================
- Coverage     68.5474%   68.5163%   -0.0311%
- Complexity      29119      29174        +55
==================================================
  Files            1422       1422
  Lines          113482     113535        +53
  Branches        19521      19555        +34
==================================================
+ Hits            77789      77790         +1
- Misses          29156      29201        +45
- Partials         6537       6544         +7

Files
Coverage Δ

...ava/org/codehaus/groovy/runtime/InvokerHelper.java
70.3125% <100.0000%> (+0.1867%)
:arrow_up:

...in/java/org/codehaus/groovy/vmplugin/VMPlugin.java
6.6667% <ø> (ø)

.../groovy/transform/RecordTypeASTTransformation.java
85.9649% <90.4762%> (-0.0130%)
:arrow_down:

.../java/org/codehaus/groovy/vmplugin/v16/Java16.java
51.5152% <16.6667%> (-7.7441%)
:arrow_down:

...in/java/org/codehaus/groovy/vmplugin/v8/Java8.java
76.9006% <0.0000%> (-2.2039%)
:arrow_down:

...in/java/org/codehaus/groovy/vmplugin/v9/Java9.java
59.7633% <8.3333%> (-3.9310%)
:arrow_down:

... and 41 files with indirect coverage changes

Adding reliance on the runtime library (InvokerHelper and VMPlugin) means a record can no longer be tagged @POJO and used in a vanilla java environment.  And though an immutable retval could be cached, it isn't here.  So what is the primary benefit?  It looks like a pound of cure for an ounce of problem.

Groovy records already rely on the runtime library - the generated toList() and toMap() use ScriptBytecodeAdapter#createList/createMap in Groovy 4 and Groovy 5 snapshots (pre this PR).
As explained on the mailing list, using the runtime library allows for using Java's faster immutable List.of()/Map.of() when possible without needing many changes to the AST transform or bytecode gen.
After reading some of the feedback here, on the mailing list and jira, I better understand the importance of preferring simpler approaches and will be replying to the comments and re-evaluating my PR accordingly when I have time.

As per comment in the issue, I'll close this PR. There is plenty of scope for further improvements - as noted, even with POJO, records still make calls into runtime. This is why @POJO is marked @Incubating and one of the things we still plan to improve. But it is the kind of thing we'd like to improve for more than just records if we can, so we'd target a broader change if we can make such a change.


Turn off MQTT events in log

Is your feature request related to a problem? Please describe.
My homebridge log file fills up with MQTT messages.
Describe the solution you'd like
I'd like to know what the options are to reduce the messages for this plugin in the log.
Describe alternatives you've considered
I have already tried to use "debug": false in the mqtt section of the config file, but this doesn't seem to work.

I have the same problem.

BUMP

Can you share the logs you are seeing ?
Il just disable them

[10/29/2019, 1:44:41 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON [10/29/2019, 1:44:41 PM] [Dafang] Setting Rich Motion Sensor Value to true [10/29/2019, 1:44:43 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF [10/29/2019, 1:44:45 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON [10/29/2019, 1:44:47 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF [10/29/2019, 1:45:12 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON [10/29/2019, 1:45:14 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF [10/29/2019, 1:45:16 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON [10/29/2019, 1:45:18 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF [10/29/2019, 1:45:20 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON [10/29/2019, 1:45:22 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF [10/29/2019, 1:45:50 PM] [Dafang] Checking Recordings Folder Size : /Users/theuser/Movies/Recordings/ [10/29/2019, 1:45:50 PM] [Dafang] Recorded Media Folder Size is 10.431367874145508MB [10/29/2019, 1:50:22 PM] [Dafang] Setting Rich Motion Sensor Value to false [10/29/2019, 1:50:50 PM] [Dafang] Checking Recordings Folder Size : /Users/theuser/Movies/Recordings/ [10/29/2019, 1:50:50 PM] [Dafang] Recorded Media Folder Size is 10.431367874145508MB

@sahilchaddha could we add some sort of log-level configuration option to the plugin so we can turn off and on the logs should we want to, and in case we want to debug our setups.

@sahilchaddha, I still haven't heard anything back from you on addressing the log output.
This is what I am seeing:
[1/12/2020, 12:16:13 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF
[1/12/2020, 12:16:15 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON
[1/12/2020, 12:16:17 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF
[1/12/2020, 12:16:21 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON
[1/12/2020, 12:16:24 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF
[1/12/2020, 12:16:26 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON
[1/12/2020, 12:16:28 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF
[1/12/2020, 12:16:33 PM] [Dafang] DAFANG : Setting Rich Motion Sensor Value to false
[1/12/2020, 12:16:43 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON
[1/12/2020, 12:16:43 PM] [Dafang] DAFANG : Setting Rich Motion Sensor Value to true
[1/12/2020, 12:16:45 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF
[1/12/2020, 12:16:50 PM] [Dafang] DAFANG : Setting Rich Motion Sensor Value to false
[1/12/2020, 12:20:14 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON
[1/12/2020, 12:20:14 PM] [Dafang] DAFANG : Setting Rich Motion Sensor Value to true
[1/12/2020, 12:20:16 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF
[1/12/2020, 12:20:19 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON
[1/12/2020, 12:20:21 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF
[1/12/2020, 12:20:26 PM] [Dafang] DAFANG : Setting Rich Motion Sensor Value to false
[1/12/2020, 12:21:09 PM] [Dafang] Checking Recordings Folder Size : /Users/me/Movies/Recordings/
[1/12/2020, 12:21:09 PM] [Dafang] Recorded Media Folder Size is 10.431367874145508MB
[1/12/2020, 12:21:28 PM] [Dafang] Snapshot from WyzeCam at 480x270
[1/12/2020, 12:21:28 PM] [Ring] Snapshot for Front Door Requested
[1/12/2020, 12:21:29 PM] [Ring] Snapshot for Front Door Received (1.58s)
[1/12/2020, 12:22:30 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON
[1/12/2020, 12:22:30 PM] [Dafang] DAFANG : Setting Rich Motion Sensor Value to true
[1/12/2020, 12:22:30 PM] [Dafang] Snapshot from WyzeCam at 480x270
[1/12/2020, 12:22:32 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF
[1/12/2020, 12:22:34 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON
[1/12/2020, 12:22:36 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF
[1/12/2020, 12:22:42 PM] [Dafang] DAFANG : Setting Rich Motion Sensor Value to false
[1/12/2020, 12:23:30 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : ON
[1/12/2020, 12:23:30 PM] [Dafang] DAFANG : Setting Rich Motion Sensor Value to true
[1/12/2020, 12:23:30 PM] [Dafang] Snapshot from WyzeCam at 480x270
[1/12/2020, 12:23:32 PM] [Dafang]  ** Sending MQTT event to accessory at myhome/dafang/motion with payload : OFF
[1/12/2020, 12:23:37 PM] [Dafang] DAFANG : Setting Rich Motion Sensor Value to false
[1/12/2020, 12:26:09 PM] [Dafang] Checking Recordings Folder Size : /Users/me/Movies/Recordings/
[1/12/2020, 12:26:09 PM] [Dafang] Recorded Media Folder Size is 10.431367874145508MB

Can we please get some sort of log level switch for this?


Submit button when entering instance URL is not functional

I'm trying the app v1.5.3 running the AppImage from the Linux x86_64; my HomeAssistant instance is version 2023.3.1. Right-clicked the icon on the toolbar, clicked "Add another instance" or "Show window", and on the window where the HA instance URL is entered, the Submit button is greyed out, no matter which URL I enter (even the example one). Pressing Enter doesn't work.

Logs when executing the appimage from terminal:
(base) david@ThinkpadE14-Debian:~$ ./Home-Assistant-Desktop-v1.5.3-linux-x86_64.AppImage
17:32:12.795 › homeassistant-desktop started
17:32:12.810 › Platform: linux x64
17:32:13.109 › Checking for update
[110657:0423/173213.761480:ERROR:nss_util.cc(349)] After loading Root Certs, loaded==false: NSS error code: -8018
17:32:14.532 › Update for version 1.5.3 is not available (latest version: 1.5.3, downgrade is disallowed).
17:32:14.535 › Initialized main window
17:32:15.160 › Initialized Tray menu
17:32:15.189 › Initialized availability check
[110657:0423/173215.202821:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[110657:0423/173215.202946:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[110657:0423/173215.398282:ERROR:browser_main_loop.cc(269)] Gdk: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

EDIT: Found a similar issue (https://github.com/iprodanovbg/homeassistant-desktop/issues/19) but in my case the auth provider seems to be the correct one:
(base) david@ThinkpadE14-Debian:~$ curl --insecure https://homeassistant.pi.lan/auth/providers
[{"name":"Home Assistant Local","id":null,"type":"homeassistant"}]

Maybe it has something to do with the selfsigned certificate I'm using? On the example picture above I've tried typing the example URL, but my HA instance is actually running in the address shown in the curl command above, served behind an nginx reverse proxy with selfsigned certs, not added to the OS. Seeing the #19 issue I'm now assuming the app tries to connect to the server while typing, and the Submit button is only enabled once the connection with the instance can be successfully established?

The problem in my case is, that I enabled login without password (allow_bypass_login: true) see here and therefore the login URL is not "/auth/providers" but "/auth/authorize".

In version 1.4.11 the login with these settings works fine.

Yeah that was the problem. I added the default auth provider and now also 1.5.3 is working for me:
auth_providers:
- type: homeassistant

Hello,
I have the same issue, "Submit" bouton is greyed out and I cannot click (on windows 10).
I add auth. providers, I restart but still the same.
When I check the auth providers I get:

[{"name":"Home Assistant Local","id":null,"type":"homeassistant"}]

Thanks in advance for any help !
Chrisbati
My YAML config:
`# Loads default set of integrations. Do not remove.
default_config:
homeassistant:
auth_providers:
- type: homeassistant
'# Load frontend themes from the themes folder
frontend:
themes: !include_dir_merge_named themes
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
media_player:

platform: webrtc
name: Dummy camera
stream: some_stream
audio: pcmu/48000
'

Hi All,
i have identified issue, this URL login does not work with SSL_certificate/SSL_key if you remove it will work again.
I do not want to use open text, but would love to use this app, is there any workaround to make SSL works ?


Removal of throttleRequestByServer was not mentioned in CHANGES.md

@ggetz could you please patch CHANGES.md?
See https://groups.google.com/forum/#!topic/cesium-dev/jId6viljtEE

What release should this be added under? 1.35?

Up to you.


Updates to some documentation

Description & Motivation
There are a handful of documentation updates needed, and this PR adds them.
Related Issue(s)
N/A
Testing
Docs only
Backwards-compatibility

Is this a breaking change that will not be backwards-compatible?  If yes, how so?

No
Documentation

Does the change require any updates to documentation?  If so, where?  Are they included?

Docs only

@quekyj some of the changes in here overlap with your PR for the website (https://github.com/intel/rohd/pull/221), could you merge in the changes there also?


Oggdude Importer unable to click checkboxes

I was unable to click the checkboxes in the Oggdude Importer after I loaded my file. I had confirmed that my file had indeed loaded but I still could not click the checkboxes. I saw that this was because the "disabled" attribute was not removed from the inputs after loading, shown below.

When I removed the attribute manually, I was able to click the checkboxes again.

Per discord, you need to manually zip the folder not the separate files, better yet, use the built in export dataset function from the character generator.


detect.go does not parse values for .platform/env/BP_NATIVE_IMAGE correctly

I do not use pack but rely instead on paketobuildpacks/builder:tiny directly on my .gitlab-ci.yml.
As a consequence, I write the variable like BP_NATIVE_IMAGE to .platform/env/BP_NATIVE_IMAGE and invoke cnb/lifecycle/creator -app=. -platform=$HOME/.platform in the container itself.
The native buildpack throws an error:
Paketo Buildpack for Native Image 5.8.0
  invalid value '1
  ' for key 'BP_NATIVE_IMAGE': expected one of [1, t, T, TRUE, true, True, 0, f, F, FALSE, false, False]

Searching for the string leads me to this buildpack. For the java-buildpack (where I set the BP_JVM_VERSION the same way), it works fine.
Expected Behavior
Setting the BP-*-variables should work for this build pack as denoted in https://github.com/buildpacks/spec/blob/main/platform.md#user-provided-variables
Executing the following commands in paketobuildpacks/builder:tiny should work and generate a native java application.
mkdir -p $HOME/.platform/env
echo "1" > $HOME/.platform/env/BP_NATIVE_IMAGE
echo "17" > $HOME/.platform/env/BP_JVM_VERSION
/cnb/lifecycle/creator -app=. -platform=$HOME/.platform image

Current Behavior
The commands above fail. I included some debug-code since the snippet is running in gitlab-ci to track the issue down:
$ cat $HOME/.platform/env/BP_NATIVE_IMAGE || true
cat: /home/cnb/.platform/env/BP_NATIVE_IMAGE: No such file or directory
$ rm $HOME/.platform/env/BP_NATIVE_IMAGE || true
$ echo "1" > $HOME/.platform/env/BP_NATIVE_IMAGE
rm: cannot remove '/home/cnb/.platform/env/BP_NATIVE_IMAGE': No such file or directory
$ cat $HOME/.platform/env/BP_NATIVE_IMAGE || true
1
$ echo "17" > $HOME/.platform/env/BP_JVM_VERSION
$ /cnb/lifecycle/creator -app=. -platform=$HOME/.platform $CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG-native
Warning: Not restoring or caching layer data, no cache flag specified.
===> DETECTING
======== Output<EMAIL_ADDRESS>========
Paketo Buildpack for Native Image 5.8.0
  invalid value '1
  ' for key 'BP_NATIVE_IMAGE': expected one of [1, t, T, TRUE, true, True, 0, f, F, FALSE, false, False]

Afterwards a jar-application is build without nativeness.
I tried multiple variants: 1, true, etc.
Possible Solution
I guess it is a bug in the detect.go...in the last commits some test cases where removed...but this is a guess.
Steps to Reproduce

Start paketobuildpacks/builder:tiny and enter the container: docker run --rm -it -v "$PWD":/usr/src/app -w /usr/src/app  paketobuildpacks/builder:base bash
Set the files for the platform:

mkdir -p $HOME/.platform/env
echo "1" > $HOME/.platform/env/BP_NATIVE_IMAGE
echo "17" > $HOME/.platform/env/BP_JVM_VERSION

Execute the build process and see the error

cnb@bd1dc0691ed0:/usr/src/app$ /cnb/lifecycle/creator -app=. -platform=$HOME/.platform image
Warning: Not restoring or caching layer data, no cache flag specified.
===> DETECTING
======== Output<EMAIL_ADDRESS>========

Paketo Buildpack for Native Image 5.8.0
  invalid value '1
  ' for key 'BP_NATIVE_IMAGE': expected one of [1, t, T, TRUE, true, True, 0, f, F, FALSE, false, False]

Motivations
Letting buildpacks generate native java-image and run in gitlab-ci without autodevops-magic via the builder-image directly.

This is a bit of a guess, but it looks like there's an EOL/line break character in there. Again, just a guess, but the way Go parses the value into a bool is probably not compatible with that.
Can you try using printf or echo -n? Basically, something that doesn't write an EOL after the value.

Good guess: both commands work. Funny although that the java buildpack is recognizing the 17 with the line break.
Thanks a lot!

Excellent. I've tagged this as a bug. We should be able to just trim the string before parsing it to remove the EOL characters. If anyone is looking for a good first contribution, this would be one.

hello @sebastiangraf ! Could you please share a sample .gitlab-ci.yml in this ticket?
It's not clear to me how environment variables are passed to Gitlab AutoDevops.
Thank you!

@anthonydahanne this is where we parse the BP_NATIVE_IMAGE env variable. The value that gets parsed by strconv.ParseBool, which doesn't seem to like the EOL character.
A couple of notes on this:

The native-image buildpack should be using https://github.com/paketo-buildpacks/libpak/blob/main/sherpa/env_var.go#L57-L69. We added this a while back and have gradually tried to move buildpacks to use it so we get consistent parsing of env variables to booleans.
In libpak, we should probably do a strings.Trim on s before it goes into ParseBool. Just in case there's unnecessary whitespace in the env variable. I think that will fix the issue.

@dmikusa thanks for your input; I'm still curious to see the Gitlab integration in action though; I shall try it out myself sooner or later! (curious to see / test the different buildpacks integration)
Wrt to your suggestions:

yes, that makes sense , we could probably add to ResolvBool in sherpa/env_var.go something like:

	t := strings.Trim(s, "\r \n\t")
	p, err := strconv.ParseBool(t)

but....

We would change the behavior by using  ResolvBool from sherpa/env_var.go - because this function does not make the difference between "user set to false" and "user input was neither true nor false" ; since the parse err is converted into false. If we had already the same behavior, @sebastiangraf  would not have been able to provide insightful log like he did; so I believe this distinction to be important.

I suggest in libpak we add another ResolveBoolErr signature so that the developer can decide whether or not we want the parse error; in our case (native-image property parsing), we'd use this function.
// ResolveBoolErr resolves a boolean value for a configuration option.
// Returns true, nil for 1, t, T, TRUE, true, True.
// Returns false, nil for all other values or unset.
// Returns false, error is the value could not be parsed into a bool
func ResolveBoolErr(name string) (bool, error) {
	s, ok := os.LookupEnv(name)
	if !ok {
		return false, nil
	}

	t := strings.Trim(s, "\r \n\t")
	p, err := strconv.ParseBool(t)
	if err != nil {
		return false, fmt.Errorf(
			"invalid value '%s' for key '%s': expected one of [1, t, T, TRUE, true, True, 0, f, F, FALSE, false, False]",
			s,
			name,
		)
	}

	return p, nil
}

// ResolveBool resolves a boolean value for a configuration option. Returns true for 1, t, T, TRUE, true, True. Returns
// false for all other values or unset.
func ResolveBool(name string) bool {
	resolveBool, _ := ResolveBoolErr(name)
	return resolveBool
}

Let me know what you think! Thanks!

t := strings.Trim(s, "\r \n\t")

Oops. I meant strings.TrimSpace https://pkg.go.dev/strings#TrimSpace

I suggest in libpak we add another ResolveBoolErr signature so that the developer can decide whether or not we want the parse error; in our case (native-image property parsing), we'd use this function.

I can't argue that it was helpful, it was really nice to have the error message. It would have been tricky to diagnose with the current ResolveBool implementation. I'm always in favor of good debugability.
I'm OK with adding a ResolveBoolErr as you suggested. It would be really helpful if we could log the error for the ResolveBool method, but I don't think we have a logger available.
We have to start thinking about libpak 2 soon. The libcnb 2 should hopefully be released soon, and we'll need libpak 2 for parity. That'll be a chance to revisit some of this, perhaps having a standard logger available or just having ResolveBool return an error always (you can ignore it if you want). Anyway, I'm rambling now. Your suggestions look great!


chore: Remove STL library

Proposed changes

The STL library is not used in Cpp-Client for any platform.
This PR removes STL files and its reference in /helpers/client_helpers.h.
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (improve a current implementation without adding a new feature or fixing a bug)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Build (changes that affect the build system)
[ ] Docs (documentation only changes)
[ ] Test (adding missing tests or fixing existing tests)
[x] Other... Please describe:

Checklist

[x] I have read the CONTRIBUTING documentation
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

@air1one @faustbrian - please review this in the next few days. Be sure to explicitly select labels so I know what's going on.
If no reviewer appears after a week, a reminder will be sent out.

Codecov Report

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

@@          Coverage Diff           @@
##           master     #78   +/-   ##
======================================
  Coverage    96.4%   96.4%
======================================
  Files          14      14
  Lines         250     250
======================================
  Hits          241     241
  Misses          9       9

Continue to review full report at Codecov.

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


metadata and limits

Added extra auth data
Added game metadata
Added library limits for certain calls

I would like the new overrides to have a name denoting they take a GameID (like AuthenticateWithPINAndGameID) which is wordy but more explicit.
The behavior to ignore an empty one is fine, and the existing APIs can forward to the GameID variants with a null / empty string.
Otherwise 👍


Changes md test

This PR is trying to merge into a feature branch, so concierge should not remind me about CHANGES.md !

@OmarShehata, thanks for the pull request! Maintainers, we have a signed CLA from @OmarShehata, so you can review this at any time.

:sparkles: :sparkles: :sparkles:I'm the Cesium Concierge and I'm here to test things. :sparkles: :sparkles: :sparkles:


Please update the requirements

I am having a problem finding compatible version of the torch and allennlp. from allennlp.commands.elmo import ElmoEmbedder is not working with latest version. Please fix.

same problem . can someone suggest me the solution plz


Document role of each module.

scalameta
scalahost
scalahost-nsc
scalahost-sbt
scalameta/paradise

I briefly explain a high-level vision of scalameta here: http://www.scala-lang.org/blog/2016/10/24/scalafix.html#how-does-scalafix-work Scalahost goes alongside paradise, paradise is only for macro whereas scalahost powers the semantic api too.

Closing as duplicate of #802


[Feature]: Persist connection on page refresh

Is your request related to a problem?
Sometimes, users have to refresh the page for x or y reason. I used the examples/with-nextjs-13, to check this, but unfortunately when I refresh the page, the wallet is disconnected. I assume that this is normal due to the react state, but I'm looking for a way to persist the connection.
Feature Description
I would like to know if it's possible to detect if a wallet has already been connected and connect the user to this wallet automatically without requiring any action from his part.
In the case that this is not possible, I would recommend to add this feature, but I think that this is already doable since that curve finance use web3-onboard and is able to reconnect a wallet previously connected without any user action.
Of course, I already looked for online solutions/answers to this question, but I have not been able to find it :(
Alternative Solutions
No response
Anything else?
No response

@0xARK this feature already exists, you can use the autoConnectLastWallet or autoConnectAllPreviousWallets flags within the connect object of the web3onboard initialization.
Example: https://github.com/blocknative/react-demo/blob/8e882c14f4952d3a230eac5d4e425af5e25b1d29/src/services.js#L157
Checkout the docs here: https://onboard.blocknative.com/docs/modules/core#connect
Going to close this issue as this feature exists but feel free to continue the conversation here for any support.

Great, I just tested and it works ! Thanks :)


have a look at EnOcean over IP

https://www.enocean-alliance.org/wp-content/uploads/2018/04/EnOcean_over_IP_Specification_v0.9.pdf
looks interresting. though chunked transfer encoding seems a bit outdated... would be nice to have a server with http/2 compatibility ...

can this be compatible with WAMP? #24

started implementing an EnOcean over IP gateway.

it real sucks that there is no defined mapping between the EEP Descriptions in XML and the IP Profile descriptions...


main cannot accept arguments in strong mode

Consider the following program:
main(List<String> args) {
  print(args);
}

This works fine if I run it normally using the VM, but if I pass the "--strong" flag to the VM I get the following error:
Unhandled exception:
NoSuchMethodError: Closure call with mismatched arguments: function 'main'
Receiver: Closure: (List<String>) => dynamic from Function 'main': static.
Tried calling: main()
Found: main(List<String>) => dynamic
#0      Object.noSuchMethod (dart:core-patch/dart:core/object_patch.dart:46)
#1      _startIsolate.<anonymous closure> (dart:isolate-patch/dart:isolate/isolate_patch.dart:277)
#2      _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:163)

This happens whether I supply arguments on the command line or not.

I'm guessing some type check should be changed from (effectively) is Function(dynamic) to is Function(null).

Turns out we already had a lot of RuntimeError expectations in strong-mode tests for this reason. I'm tweaking the status files now :)


[wasm] Provide stub for _NSCreateTemporaryFile on WASI

WASI does not have temp directories and wasi-libc does not provide mkstemp, so provide a stub implementation that throws ENOTSUP.

@swift-ci test


fix support variant column with index when create table

Proposed changes
Issue Number: close #xxx

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

run buildall

run feut


Issue-add moment

Automated Review Comments
Issues in package.json:

(5, 'Hardcoded string found')
(6, 'Hardcoded string found')

I got it.


[Request] Fly Enhancement when leaving region

Problem:
When leaving a region with fly to a region without fly, players often fall to their death because they don't know the edge of the region.

Ideally, these are all config options or flags in the area.

This is something I have wanted to do for some time, and surprisingly you are the first to ask for it.


add warning or trim for event handler with extra space in template

Vue.js version
2.0.1
Reproduction Link
http://jsbin.com/faremewici/2/edit?html,js,console,output
Steps to reproduce
As you can see , @click=" onClickHandler " has extra space.
then click the link in output
What is Expected?
the console should warn that event handler doesn't exist or execute onClickHandler directly
What is actually happening?
the console output nothing
Even in webpack dev environment, Vue doesn't show any warning.
I expect Vue can give a warning in this situation or just trim it to execute onClickHandler method.

@HeChenTao I'm curious, how did you find yourself with spaces around that handle?

@posva Because I find the handler is not called, so I look into the code again and find spaces.
That's not important. Just need a warning for it in dev environment.

@HeChenTao But, how were the spaces introduces in the first place?

@posva Yes. I just made a mistake. I wrote code like@click="handler ". Adding a warning in this case can make Vue more friendly.


Trivy operator reached the pull rate limit of docker.io

Describe the bug
[2022-09-30 07:20:30,444] kopf.objects         [ERROR   ] [trivy-system/trivy-system-trivy-system-helm-trivy-operator-main-config] TRIVY ERROR: return 1
[2022-09-30 07:20:30,444] kopf.objects         [ERROR   ] [trivy-system/trivy-system-trivy-system-helm-trivy-operator-main-config] You have reached your pull rate limit.

It's quite easy the reach the rate limit of docker.io, will trivy-operator use the image from the machine other than pull the image from the docker registry?
Expected behavior
Configuration file
Helm Values file
Default helm values.
Environment:

Trivy-Operator version (use trivy-operator version): trivy image: 2.4.1
Installation type (Helm, Kubernetes, OperatorFramework): Helm: 2.4.3
Kubernetes version (use kubectl version): v1.21.10
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc):

Additional context

Hi @FogDong.
The trivy-operator use trivy in a container to scan images. It dose not reach the files on the host. Mounting the containerd/docker socket and folders to a container is a very unsecure thing . If you have a user in docker you can extend your pull rate limit. trivy-operator can use pull secret or username/passwor to authenticate with docker.io.


Update version for the next release (v0.7.2)

This version makes this package compatible with MeiliSearch v0.27.0🎉
Check out the changelog of MeiliSearch v0.27.0 for more information about the changes.
🚀 Enhancements

Ensure nested field support #374 @alallema
Add new search parameters highlightPreTag, highlightPostTag and cropMarker #375 @alallema

bors merge

I merged it, but I should have checked -> not all the required files have been updated, so I cannot release
See: https://github.com/meilisearch/meilisearch-java/runs/6350903942?check_suite_focus=true


docs: add samples for JSONWriter with Default and Committed streams

Towards internal b/296042828 🦕

This PR also addresses at least part of Issue #349.


[Bug] Switch class times from string to time object

Description of the Bug
Switch class times from string to time object to make it work properly with MyTimetable.
Reproduction Steps
No response
Expected Behaviour
No response
Additional Notes
No response


Tweak UI

Tasks

[ ] Check styling
[ ] Add CSS hook classes

Views

[ ] Table summaries views
[ ] actions/resources/views/button-action.blade.php
[ ] actions/resources/views/components/action.blade.php
[ ] actions/resources/views/components/actions.blade.php
[ ] actions/resources/views/components/group.blade.php
[ ] actions/resources/views/group.blade.php
[ ] actions/resources/views/grouped-action.blade.php
[ ] actions/resources/views/icon-button-action.blade.php
[ ] actions/resources/views/link-action.blade.php
[ ] actions/resources/views/modal/actions/button-action.blade.php
[ ] actions/resources/views/modal/index.blade.php
[ ] actions/resources/views/select-action.blade.php
[ ] app/resources/views/components/avatar/index.blade.php
[ ] app/resources/views/components/avatar/tenant.blade.php
[ ] app/resources/views/components/avatar/user.blade.php
[ ] app/resources/views/components/brand.blade.php
[ ] app/resources/views/components/card/heading.blade.php
[ ] app/resources/views/components/card/index.blade.php
[ ] app/resources/views/components/footer.blade.php
[ ] app/resources/views/components/form/actions.blade.php
[ ] app/resources/views/components/form/index.blade.php
[ ] app/resources/views/components/global-search/actions/action.blade.php
[ ] app/resources/views/components/global-search/actions/index.blade.php
[ ] app/resources/views/components/global-search/index.blade.php
[ ] app/resources/views/components/global-search/input.blade.php
[ ] app/resources/views/components/global-search/no-results-message.blade.php
[ ] app/resources/views/components/global-search/result-group.blade.php
[ ] app/resources/views/components/global-search/result.blade.php
[ ] app/resources/views/components/global-search/results-container.blade.php
[ ] app/resources/views/components/header/heading.blade.php
[ ] app/resources/views/components/header/index.blade.php
[ ] app/resources/views/components/header/subheading.blade.php
[ ] app/resources/views/components/layouts/app.blade.php
[ ] app/resources/views/components/layouts/app/sidebar/group.blade.php
[ ] app/resources/views/components/layouts/app/sidebar/index.blade.php
[ ] app/resources/views/components/layouts/app/sidebar/item.blade.php
[ ] app/resources/views/components/layouts/app/topbar/breadcrumbs.blade.php
[ ] app/resources/views/components/layouts/app/topbar/database-notifications-trigger.blade.php
[ ] app/resources/views/components/layouts/base.blade.php
[ ] app/resources/views/components/layouts/card.blade.php
[ ] app/resources/views/components/page.blade.php
[ ] app/resources/views/components/resources/relation-managers/index.blade.php
[ ] app/resources/views/components/tabs/index.blade.php
[ ] app/resources/views/components/tabs/item.blade.php
[ ] app/resources/views/components/tenant-menu.blade.php
[ ] app/resources/views/components/topbar.blade.php
[ ] app/resources/views/components/user-menu.blade.php
[ ] app/resources/views/global-search/actions/button-action.blade.php
[ ] app/resources/views/global-search/actions/icon-button-action.blade.php
[ ] app/resources/views/global-search/actions/link-action.blade.php
[ ] app/resources/views/login.blade.php
[ ] app/resources/views/pages/dashboard.blade.php
[ ] app/resources/views/pages/tenancy/register-tenant.blade.php
[ ] app/resources/views/resources/pages/create-record.blade.php
[ ] app/resources/views/resources/pages/edit-record.blade.php
[ ] app/resources/views/resources/pages/list-records.blade.php
[ ] app/resources/views/resources/pages/view-record.blade.php
[ ] app/resources/views/resources/relation-manager.blade.php
[ ] app/resources/views/widgets/account-widget.blade.php
[ ] app/resources/views/widgets/filament-info-widget.blade.php
[ ] forms/resources/views/component-container.blade.php
[ ] forms/resources/views/components/actions/action.blade.php
[ ] forms/resources/views/components/actions/icon-button-action.blade.php
[ ] forms/resources/views/components/actions/modal/actions/button-action.blade.php
[ ] forms/resources/views/components/actions/modal/index.blade.php
[ ] forms/resources/views/components/builder.blade.php
[ ] forms/resources/views/components/builder/block-picker.blade.php
[ ] forms/resources/views/components/builder/block.blade.php
[ ] forms/resources/views/components/card.blade.php
[ ] forms/resources/views/components/checkbox-list.blade.php
[ ] forms/resources/views/components/checkbox.blade.php
[ ] forms/resources/views/components/color-picker.blade.php
[ ] forms/resources/views/components/date-time-picker.blade.php
[ ] forms/resources/views/components/field-wrapper/error-message.blade.php
[ ] forms/resources/views/components/field-wrapper/helper-text.blade.php
[ ] forms/resources/views/components/field-wrapper/hint.blade.php
[ ] forms/resources/views/components/field-wrapper/index.blade.php
[ ] forms/resources/views/components/field-wrapper/inline.blade.php
[ ] forms/resources/views/components/field-wrapper/label.blade.php
[ ] forms/resources/views/components/fieldset.blade.php
[ ] forms/resources/views/components/file-upload.blade.php
[ ] forms/resources/views/components/grid.blade.php
[ ] forms/resources/views/components/group.blade.php
[ ] forms/resources/views/components/hidden.blade.php
[ ] forms/resources/views/components/key-value.blade.php
[ ] forms/resources/views/components/markdown-editor.blade.php
[ ] forms/resources/views/components/markdown-editor/toolbar-button.blade.php
[ ] forms/resources/views/components/multiple-file-upload.blade.php
[ ] forms/resources/views/components/placeholder.blade.php
[ ] forms/resources/views/components/radio.blade.php
[ ] forms/resources/views/components/repeater.blade.php
[ ] forms/resources/views/components/rich-editor.blade.php
[ ] forms/resources/views/components/rich-editor/toolbar-button.blade.php
[ ] forms/resources/views/components/section.blade.php
[ ] forms/resources/views/components/select.blade.php
[ ] forms/resources/views/components/tabs.blade.php
[ ] forms/resources/views/components/tabs/tab.blade.php
[ ] forms/resources/views/components/tags-input.blade.php
[ ] forms/resources/views/components/text-input.blade.php
[ ] forms/resources/views/components/textarea.blade.php
[ ] forms/resources/views/components/toggle.blade.php
[ ] forms/resources/views/components/wizard.blade.php
[ ] forms/resources/views/components/wizard/step.blade.php
[ ] forms/stubs/scaffolding/resources/views/layouts/app.blade.php
[ ] notifications/resources/views/actions/button-action.blade.php
[ ] notifications/resources/views/actions/group.blade.php
[ ] notifications/resources/views/actions/grouped-action.blade.php
[ ] notifications/resources/views/actions/link-action.blade.php
[ ] notifications/resources/views/components/actions/action.blade.php
[ ] notifications/resources/views/components/actions/index.blade.php
[ ] notifications/resources/views/components/body.blade.php
[ ] notifications/resources/views/components/close-button.blade.php
[ ] notifications/resources/views/components/database/index.blade.php
[ ] notifications/resources/views/components/database/modal/actions.blade.php
[ ] notifications/resources/views/components/database/modal/empty-state.blade.php
[ ] notifications/resources/views/components/database/modal/heading.blade.php
[ ] notifications/resources/views/components/database/modal/index.blade.php
[ ] notifications/resources/views/components/database/trigger.blade.php
[ ] notifications/resources/views/components/date.blade.php
[ ] notifications/resources/views/components/echo.blade.php
[ ] notifications/resources/views/components/icon.blade.php
[ ] notifications/resources/views/components/notification.blade.php
[ ] notifications/resources/views/components/title.blade.php
[ ] notifications/resources/views/notification.blade.php
[ ] notifications/resources/views/notifications.blade.php
[ ] notifications/stubs/scaffolding/resources/views/layouts/app.blade.php
[ ] spatie-laravel-settings-plugin/resources/views/pages/settings-page.blade.php
[ ] support/resources/views/assets.blade.php
[ ] support/resources/views/components/button.blade.php
[ ] support/resources/views/components/dropdown/header.blade.php
[ ] support/resources/views/components/dropdown/index.blade.php
[ ] support/resources/views/components/dropdown/list/index.blade.php
[ ] support/resources/views/components/dropdown/list/item.blade.php
[ ] support/resources/views/components/dropdown/list/separator.blade.php
[ ] support/resources/views/components/grid/column.blade.php
[ ] support/resources/views/components/grid/index.blade.php
[ ] support/resources/views/components/hr.blade.php
[ ] support/resources/views/components/icon-button.blade.php
[ ] support/resources/views/components/icon.blade.php
[ ] support/resources/views/components/input/affixes.blade.php
[ ] support/resources/views/components/input/index.blade.php
[ ] support/resources/views/components/input/select.blade.php
[ ] support/resources/views/components/link.blade.php
[ ] support/resources/views/components/loading-indicator.blade.php
[ ] support/resources/views/components/modal/actions.blade.php
[ ] support/resources/views/components/modal/heading.blade.php
[ ] support/resources/views/components/modal/index.blade.php
[ ] support/resources/views/components/modal/subheading.blade.php
[ ] tables/resources/views/actions/bulk-action.blade.php
[ ] tables/resources/views/actions/button-action.blade.php
[ ] tables/resources/views/actions/group.blade.php
[ ] tables/resources/views/actions/grouped-action.blade.php
[ ] tables/resources/views/actions/icon-button-action.blade.php
[ ] tables/resources/views/actions/link-action.blade.php
[ ] tables/resources/views/actions/modal/actions/button-action.blade.php
[ ] tables/resources/views/columns/badge-column.blade.php
[ ] tables/resources/views/columns/checkbox-column.blade.php
[ ] tables/resources/views/columns/color-column.blade.php
[ ] tables/resources/views/columns/icon-column.blade.php
[ ] tables/resources/views/columns/image-column.blade.php
[ ] tables/resources/views/columns/layout/grid.blade.php
[ ] tables/resources/views/columns/layout/panel.blade.php
[ ] tables/resources/views/columns/layout/split.blade.php
[ ] tables/resources/views/columns/layout/stack.blade.php
[ ] tables/resources/views/columns/select-column.blade.php
[ ] tables/resources/views/columns/tags-column.blade.php
[ ] tables/resources/views/columns/text-column.blade.php
[ ] tables/resources/views/columns/text-input-column.blade.php
[ ] tables/resources/views/columns/toggle-column.blade.php
[ ] tables/resources/views/components/actions/action.blade.php
[ ] tables/resources/views/components/actions/cell.blade.php
[ ] tables/resources/views/components/actions/index.blade.php
[ ] tables/resources/views/components/bulk-actions/index.blade.php
[ ] tables/resources/views/components/bulk-actions/trigger.blade.php
[ ] tables/resources/views/components/cell.blade.php
[ ] tables/resources/views/components/checkbox/cell.blade.php
[ ] tables/resources/views/components/checkbox/index.blade.php
[ ] tables/resources/views/components/columns/column.blade.php
[ ] tables/resources/views/components/columns/layout.blade.php
[ ] tables/resources/views/components/container.blade.php
[ ] tables/resources/views/components/empty-state/description.blade.php
[ ] tables/resources/views/components/empty-state/heading.blade.php
[ ] tables/resources/views/components/empty-state/index.blade.php
[ ] tables/resources/views/components/filters/dropdown.blade.php
[ ] tables/resources/views/components/filters/index.blade.php
[ ] tables/resources/views/components/filters/indicators.blade.php
[ ] tables/resources/views/components/filters/trigger.blade.php
[ ] tables/resources/views/components/header-cell.blade.php
[ ] tables/resources/views/components/header/description.blade.php
[ ] tables/resources/views/components/header/heading.blade.php
[ ] tables/resources/views/components/header/index.blade.php
[ ] tables/resources/views/components/loading-cell.blade.php
[ ] tables/resources/views/components/pagination/index.blade.php
[ ] tables/resources/views/components/pagination/item.blade.php
[ ] tables/resources/views/components/pagination/records-per-page-selector.blade.php
[ ] tables/resources/views/components/reorder/cell.blade.php
[ ] tables/resources/views/components/reorder/handle.blade.php
[ ] tables/resources/views/components/reorder/indicator.blade.php
[ ] tables/resources/views/components/reorder/trigger.blade.php
[ ] tables/resources/views/components/row.blade.php
[ ] tables/resources/views/components/search-input.blade.php
[ ] tables/resources/views/components/selection-indicator.blade.php
[ ] tables/resources/views/components/table.blade.php
[ ] tables/resources/views/components/toggleable/index.blade.php
[ ] tables/resources/views/components/toggleable/trigger.blade.php
[ ] tables/resources/views/index.blade.php
[ ] tables/stubs/scaffolding/resources/views/layouts/app.blade.php
[ ] widgets/resources/views/chart-widget.blade.php
[ ] widgets/resources/views/components/card/heading.blade.php
[ ] widgets/resources/views/components/card/index.blade.php
[ ] widgets/resources/views/components/stats/card.blade.php
[ ] widgets/resources/views/components/stats/index.blade.php
[ ] widgets/resources/views/components/widget.blade.php
[ ] widgets/resources/views/components/widgets.blade.php
[ ] widgets/resources/views/stats-overview-widget.blade.php
[ ] widgets/resources/views/stats-overview-widget/card.blade.php
[ ] widgets/resources/views/table-widget.blade.php

And what exactly are we doing with all these? Lol.

Want to make sure all these views match design updates (and get rid of current inconsistencies).

Going to approach this differently.
Also added a separate roadmap entry for "Add more CSS hook classes and document them".


Improve keyboard avoid behavior for section list and Screen component with "fixed" preset variant

Please verify the following:

[x] yarn test jest tests pass with new tests, if relevant
[x] yarn lint eslint checks pass with new code, if relevant
[x] yarn format:check prettier checks pass with new code, if relevant
[x] README.md (or relevant documentation) has been updated with your changes

Describe your PR
This PR solves an issue with text inputs inside a list (e.g. SectionList, Flatlist, etc). It was first reported here.
Overall behaviour
Here are also videos with examples of variants for Screen.tsx and its preset prop.

preset="fixed" - items at top
preset="fixed" - items at bottom
preset="scroll" - items at top
preset="scroll" - items at bottom

Tried this out on Android and iOS and it looks great 👍

Is the plan to also use the KeyboardAwareScrollView from react-native-keyboard-controller in Screen.tsx for ScreenWithScrolling? Or is that going to be a separate PR?

@frankcalise Not necessarily. I started by modifying Screen.tsx but stopped because I was naive to the react-native-keyboard-controller behaviour. Then I realized the solution was to add the renderScrollComponent prop in SectionList.
I think a more generic solution is needed for Screen.tsx if we want to support not only SectionList, but also FlashList and FlatList.
Let me know your thoughts!

Hmm. I think it's possible Screen (with scrolling) and handling the lists are actually separate since you wouldn't want to nest scrollviews (one being screen, the other coming from the list).
But to that point, yeah maybe something can be done in app/components/ListView for the lists aspect of the fix

I'm seeing a weird issue on iOS, I reproduced on both simulator and physical device. It happens whether keyboard is open or not:

On demo showroom screen, open hamburger menu
Scroll all the way down the hamburger menu and select the last item ("Styling")
After screen animates to end, try to scroll up again. it will glitch and keep trying to scroll you back down.

https://github.com/user-attachments/assets/b25808cf-87b7-46df-a507-ddc3d227dfee

This is looking good! Nice work!
What are your thoughts on extending src/components/ListView.tsx similar to the way you did the demo section list?
Does that make sense or only if the list in not embedded in a <Screen /> at this point? Which I would say I typically reach for when letting the list drive the entire screen area.

@frankcalise I did a quick update to ListView to add renderScrollComponent and I'm getting an error related to MobX. I feel the scope of this PR is increasing. Would you mind if I create an extra issue to tackle that? Let me know what do you think!

@fpena yeah I agree, we can take care of that separately

Preliminary impression: the bug no longer occurs, but the scrolling animation after menu selection on my Android device (Galaxy S21) is not smooth, and I think it was before. I want to try it out in release mode to see if it's any better, and again on the older versions to compare.
I can try that out after lunch.

Fixed feels good on iOS (sim, haven't tried device just yet) and Android device.
The section list feels good on the iOS sim but not working as great on Android device? (Pixel 4).
As you can see my test for this is bringing the TextInput very low and some portion of behind the tab bar (although it makes no difference, as long as it is in the bottom half of the screen where the keyboard would be upon being shown) to make sure it has to adjust.
https://github.com/user-attachments/assets/61959b67-dc23-41b9-8e5b-e46259be3224

Okay, I just compared with a plain v10 repro and I don't see a difference. Would be ideal to get this smoother but is fine for now since this list is so big 👍  attaching videos for reference
https://github.com/user-attachments/assets/6012638a-52db-4c94-9ba1-5e0c534d7e04
https://github.com/user-attachments/assets/29880cd4-d878-4e9c-ac5e-20092775dacd

Adding a video from a Pixel 7 device as well. Similar to the Pixel 4 video above, except the Login screen also showed some weird side effects (where it didn't, on the smaller screen size)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added drawer

This looks really cool! Are the buttons not functioning yet?

This looks really cool! Are the buttons not functioning yet?

I can't make the Play Store button work as of now, obviously.
Exit works now.
What about about?

@akshansh2000 I guess link it to the github repo for now. Once we setup a website, we'll change.


Wrong login? & simple misspelling.

I came across this project from the Directus Discord.

Wrong Login
On https://docs.nuxtus.com/#/using-nuxtus it states:

User<EMAIL_ADDRESS>👍
Password: password

Which is accurate.
But upon launching http://localhost:3000/docs it incorrectly reads:

Email<EMAIL_ADDRESS>👎
Password: password

Misspelling
One page https://docs.nuxtus.com/#/cli?id=configuration under Configuration it reads:

this is done automatically for you if you are using the biolerplate

😆 Biolerplate/Boilerplate is misspelled.

I didn't have enough time to tinker any further tonight - but it looks promising!

Thanks for the feedback. I've updated the included docs and fixed the typo both of which will be deployed next release.


Update README.md

Lists scripts and JSON files in repo, provides brief description of functionality.

Accidentally submitted a duplicate PR; closing.


Warn that user is running Orbit without admin privileges

ETW won't work without admin privileges, make sure the user knows about it

Orbit client no longer requires admin privileges.


Rotors dont work

Rotors dont work, you can stage the rotors, but you cant make it "work". The rotors make sound, but dont spin or even lift and im pretty sure it is broken.

Another thing, you cant turn the rotors off, they already are on and every time you press space it will start to make sound, but as i said before, it wont lift or spin.

the beta version is screwed up because of the recent update. I also think there is a bug when you staceg my custom parts, as you can see here #31


Fix test kitchen travis tests

Hey! I'm guessing the cookbook was transferred over to you and no credentials were set up after the switch? Any chance we could get those going again and make sure the cookbook stays healthy? (Digital Ocean is $5/month the cheapest server running constantly, but since we only spin up when running tests, this should be much much less :)

This is all fixed, I'm happy to say.


AIRAVATA-2207 Admin users can't see experiment summaries

Adds the following API server methods

getExperimentByAdmin
cloneExperimentByAdmin

These methods allow an admin to see and clone experiments for which they don't have the READ sharing permission.

@scnakandala can you review this when you get a chance?


Problem of saving trained network parameters after network training

Hello, if I want to save the network parameters, henceforth make test convenience, how can I do.

I think the easiest way is just saving the entire model :pcanet by pickle.
If you want to save only network parameters, trained parameters appear in pcanet.pca_l1.components_ and pcanet.pca_l2.components_. So just save them with hyperparameters listed from L141.
I have no idea about saving network parameters with HDF5 etc. since I'm not familiar with other deep learning frameworks, sorry.

@IshitaTakeshi Thank you very much.


small wording consistency issue — ch 6 exercises

Singular/plural conventions are inconsistent. 9 should probably be 'disjunctions' (or maybe change all others to singular.

Since there were many examples using the plural, I changed 'disjunction' in example 9 to 'disjunctions'.


A working example of uploading a large fgdb to ArcGIS Online.

It would be great to see a working sample that shows uploading a large fgdb to ArcGIS online.  I have tried with the addItem sample but seem to run into many issues with timeouts or failing to get multipart uploads working.
For example I have been trying to use the latest additem sample to upload a large file geodatabase using the multi although the process seems to complete, there is an error at the end and nothing appears in ArcGIs online.
the zip file is 330Mb  the original gdb is 440mb
Using the upload sample, but setting:
itemParams.type = "File Geodatabase"
itemParams.typeKeywords = "Data,File Geodatabase"

and
multipart=True

results in the following at the end of the process
{u'messageCode': u'CONT_0001', u'message': u'Item does not exist or is inaccessible.', u'code': 400, u'details': []}

What version of ArcREST are you using?

3.0.1 release

This code works at v3.5.1.  I tested it today.
 sh = arcrest.AGOLTokenSecurityHandler(username, password)
 admin = arcrest.manageorg.Administration(securityHandler=sh)
 content = admin.content
 user = content.users.user(username)
 ip = arcrest.manageorg.ItemParameter()
 ip.title = "BigFileData"
 ip.type = "Shapefile"#"File Geodatabase"
 ip.tags = "BigDataFile"
 ip.description = "big data description"
 ip.snippet = "snippet description"
 item = user.addItem(itemParameters=ip,
                    filePath=r"C:\temp3\guam.zip",
                    multipart=True, overwrite=True)
 print (item.id)

@dstubbins  - closing due to lack of response.

I have the same issue. The zipped FGDB i am testing with is 186MB and uploads fine manually to AGOL. Once I do it with the code, the logs show processing of AddItem, but once finished, no item id is returned and nothing is visible in My Contents on AGOL.

from __future__ import print_function
from __future__ import absolute_import
import arcrest

if __name__ == "__main__":
    sh = arcrest.AGOLTokenSecurityHandler(username="username", password="password")
    admin = arcrest.manageorg.Administration(securityHandler=sh)
    user = admin.content.users.user()
    ip = arcrest.manageorg.ItemParameter()
    ip.title = "A very large fgdb"
    ip.type = "File Geodatabase"
    ip.tags = "fgdb"
    ip.description = "description"
    ip.snippet = "snippet"
    res = user.addItem(itemParameters=ip,
                       filePath=r"C:\temp3\40a87ec04f334df8bd92d9842f19570f.zip",
                       multipart=True)

    # the result object is a UserItem object, not JSON.  This is for version 3.5.3/3.5.4

Thanks for a quick response! The code works fine with multipart = False, the file geodatabase is uploaded on AGOL, its only issue when I set multipart to True.
I have created a workaround by creating an empty FGDB, zipping it, and using addItem() with multipart=False, then doing an updateItem() with multipart = True and pointing data to the full zipped FGDB to be uploaded. This seems to work fine...
I can't understand why addItem() with multipart = True is not working for me...

@SergStol what version of ArcREST are you using?

3.5.3/3.5.4, installed on 23rd of Feb

Uninstalled and installed pure 3.5.3 stable release and same issue persists

@SergStol - The fix went into dev, which you can download here: https://github.com/Esri/ArcREST/archive/master.zip

Have just tried this, can confirm that now addItem() works with multipart turned on. Thanks!


Add necessary settings so Drought will write files

Jim agreed, we are going to merge this, will revert if it breaks.


[BUG] Set-PnPHomeSite throws an error when you have multiple Viva Connections

Reporting an Issue
Running the Set-PnPHomeSite when you have multiple Viva Connections throws the following error:
"Set-PnPHomeSite: Operation is not valid due to the current state of the object."
Expected behavior
The Home site should be configured without any error.
Actual behavior
There is an error when running that cmdlet
Steps to reproduce behavior

Go to Office 365 admin center -> Settings -> Viva -> Viva connections
Ensure you have multiple Viva Connections. In my case I have the following:

https://tenantName.sharepoint.com
https://1nds5r.sharepoint.com/sites/intranet

Open up PowerShell and run the following command:
Set-PnpHomeSite -HomeSiteUrl https://tenantName.sharepoint.com/sites/intranet
(please change the HomeSiteUrl parameter accordingly)
The following exception will be thrown:
Set-PnPHomeSite: Operation is not valid due to the current state of the object.

What is the version of the Cmdlet module you are running?
2.3.0 and 2.4.0
Which operating system/environment are you running PnP PowerShell on?

[x] Windows
[ ] Linux
[ ] MacOS
[ ] Azure Cloud Shell
[ ] Azure Functions
[ ] Other : please specify

Hi @ryder-cayden
By any chance are you able to use SharePoint Online PowerShell cmdlet Set-SPOHomeSite to set the Home Site? If yes , can please confirm whether you get the same error as using set-pnphomesite?

Hi @reshmee011... The Set-SPOHomeSite works fine based on my testing. I did not get the same error.

I could reproduce the issue with set-pnphomesite. I checked the code, nothing unusual. It used to work in the past. I will try to find out why it is not working.

@reshmee011 @ryder-cayden - this issue has been fixed now. Will be available in tomorrow's nightly builds and the next major one when we release it. Thanks for reporting and looking into it.

Thanks so much @gautamdsheth for the fix.


Maybe we should sort the sections by amount of communities in them?

Coincidentally they're already sorted that way but I think it would be nice to keep it that way for better browsing experience.

I don't think we will be able to sort the sections properly across multiple posts but sorting them inside their post alone shouldn't be a problem.

I will follow this format on purpose starting now.


Added support for SameSite=None

Do you have any plans to merge this PR? Thanks!

This is working for our application, thanks @clagio! @AirisX, looks to be good for merge.


Error importing ASN JSON file

When importing the attached file, I get the following error:
Attention!
Attention: Validation failed: Name can't be blank
ASN_D2695955.zip

@stuartasutton - @excelsior noticed that there is another problem with the attached file: many properties there have duplicate names. Their IDs are unique, but the labels are not.  Seeing a bunch of identical properties on the right may be confusing.
Do you have any concerns with this? Or suggestions for us?

Can you give me an example, Joe, from the ASN JSON file. There shouldn't be any duplicate properties within the ASN namespace--i.e., unique IDs, but not the labels.

Hey @stuartasutton, we've been testing with this file: ASN_D2695955.zip (it's an RDF/JSON file in a ZIP archive, because GitHub doesn't allow uploading JSON files).
The file contains 200+ terms of the http://purl.org/ASN/schema/core/Statement type. We use the http://purl.org/ASN/schema/core/statementLabel property as the source for names during import, but there are only four unique values in that file (Benchmark, Competency,  Topic, and Topic Cluster).

@excelsior @jbaird123 could you point me to the set of test files you're using? I'll have look over them make sure that they are appropriate, not missing any important cases?

Hi @philbarker - I have attached a zip file with all of the files I'm using to test.  The ASN file is currently problematic for us, but @excelsior is working on that.  Aside from that, all other files work with the importer.
files.zip

@jbaird123, I am interested in knowing how the ASN file is "problematic"? I am the technical lead (and primary architect) of the ASN namespace.

@stuartasutton - I didn't mean that there are problems with the file.  We're having problems importing it, but we haven't been able to investigate it yet.  It's likely an issue with our code.  I'll let you know if it turns out otherwise.

Super. Thank you.

@stuartasutton The ASN_Profile.jsonld.zip file does have a problem after all. Its @context property (https://github.com/stuartasutton/asn/blob/master/asnContext.json) links to a GitHub page which responds with an HTML document. The raw version of that file (https://raw.githubusercontent.com/stuartasutton/asn/master/asnContext.json) does return a JSON document, but with a text/plain content type. We expect a JSON document with a proper MIME type when resolving a spec's context.
I'm not sure if there is a way to force GitHub to serve files with correct response headers. Do you think we should add a workaround if you plan to store contexts on GH?

@excelsior - I'm not sure that's the only issue.  I modified my local version to point the context to the raw content, and I also changed the id reference to point to the raw content as well.  I still get the "Attention: Couldn't find MergedFile with 'id'=undefined" error message when I attempt to upload. I have attached the file with my modifications for your reference.
ASN_Profile-joe.zip
.

@jbaird123 The raw version still has the wrong MIME type (it's text/plain, but should be application/json), i.e. it's the same issue. The question is, should we try to parse it as JSON anyways, disregarding the content type.

@excelsior - Since we're parsing JSON-LD, I'm ok with ignoring the MIME type and parsing all files as application/json.  @stuartasutton - Let us know if you have any issues with that.

I can change the file addressed, but I've no idea about MIME type. Seems strange since there are lots of projects that have their JSON-LD files and context files in github. Best to ask Phil. Since these files are on my github account, I can make any changes necessary.

I could put the file somewhere temporarily and serve it with the right mime type, but that would be an ad hoc fix for a single case. I suspect serving these files with the wrong MIME type is quite common, so I would suggest processing it as JSON-LD even though its MIME type if plain text. You could raise an issue about content sniffing for MIME type as a generic fall back before processing an unexpected MIME type, but I suspect if you hit a case where what you're processing really isn't JSON-LD you'll find out soon enough.
So yeah, just process remote contexts on the assumption that they are JSON-LD. Maybe log a message/warning about the wrong MIME type if that's an option, as it might help with fault finding if that doesn't work.

hmmm, should I be worried that there isn't a tast-case schema for IMS
CASE in the zip archive?
There is a JSON-Schema file for CASE as JSON-LD here:
https://github.com/philbarker/desmSchemas/tree/main/IMS Global
(case-ld.json) along with some other files that may be useful.

Phil, per your comment https://github.com/t3-innovation-network/desm/issues/247#issuecomment-1212196145, I think it is one thing to know where to gather these files from the canonical source and another to gather together in an easily accessible place some test files. The CASE files are present as well as others for 1EdTech in my github.

@stuartasutton yup, I linked to a fork I made of your github repo.


Update common/* package vendoring

This will enable ms precision for configuration. Unlikely to be relevant for the Alertmanager but configuration shouldn't be different from Prometheus.

:+1:


Building segmentation ensemble models is slow because of full image inference in the child runs

When building ensemble models, we are usually just interested in the metrics of the final ensemble. But we still do full image inference on validation and test set, before actually starting the ensemble building. We could speed that up by disabling full image inference in the child runs, and only run it with the ensemble model.
AB#3942

Ensure that we trigger full image inference on training, validation and test set separately. (current: Training set on/off, Val+Test set on/off)
Trigger full image inference for ensemble model separate from child runs (single checkpoint)
one solution could be to have a total of 6 flag, we probably want that internally in any case. Externally facing flags could be "smart"

The flags currently are:

perform_training_set_inference: bool =
param.Boolean(False,
doc="If True, run full image inference on the training set at the end of training. If False and "
"perform_validation_and_test_set_inference is True (default), only run inference on "
"validation and test set. If both flags are False do not run inference.")
perform_validation_and_test_set_inference: bool =
param.Boolean(True,
doc="If True (default), run full image inference on validation and test set after training.")

In class WorkflowParams


Recursive types cause an infinite loop in a schema defined with type language (schema.graphql)

Example schema file:
interface Thing {
  id: ID!
}

type Query {
  userList: [User]
}

type User implements Thing {
  id: ID!
  self: User
}

Using a schema like this causes requests to fail with a 504 because the type resolution step of the schema never finishes.
I've done some digging and the request makes it through AST parsing, into a BuildSchema::buildAST() call, and finally fails during schema decorating whenever the fields of User are resolved (resolved by calling the Closure that is initially returned).

I read through the source of GraphQL\Utils\BuildSchema a little looking for the issue and it seems like it might be this chain of functions:
makeTypeDefConfig => makeFieldDefMap => produceOutputType => produceType =>
typeDefNamed => makeSchemaDefConfig => makeTypeDefConfig => etc...

So it fails not when you create a schema, but when you issue a query against it, right?

It fails during a request, but the infinite loop happens during the BuildSchema::buildAST call, not during GraphQL::executeQuery

I just tried, but it worked for me. Look at the test case below and help me reproduce your situation:
    public function testRecursiveTypes()
    {
        $body = '
interface Thing {
  id: ID!
}

type Query {
  userList: [User]
}

type User implements Thing {
  id: ID!
  self: User
}
';
        $doc = Parser::parse($body);

        $schema = BuildSchema::buildAST($doc);
        $this->assertInstanceOf(Schema::class, $schema);
    }

I also tried executing a query against this schema and all worked fine. What should I add to see the bug?
Also please make sure that it's not your typeConfigDecorator which causes the error (i.e. maybe it adds fields as array vs Closure)

I'm actually leaving on a vacation, but I work with @jrichard0725 and we've been having the same issue, so he can provide the code to reproduce.
I think the issue actually is triggered by typeConfigDecorator, because at one point we call the fields Closure returned by the User type ($typeConfig['fields']()) in order to provide resolve functions for some of it's fields. It seems like whenever that Closure is called it attempts to resolve the types of the fields and recurses into oblivion.
Anyway, @jrichard0725 can get you some code to reproduce this on Monday.

@bryan-havenly I think it's because you call $typeConfig['fields']() inside typeConfigDecorator itself.
Instead you should redefine $typeConfig['fields'] with your own closure and call previous one inside it. I.e.:
$typeConfigDecorator = function ($typeConfig) {
    if ($typeConfig['name'] === 'MyObjType') {
        $fieldsFn = $typeConfig['fields'];
        // Note: you shouldn't call this $fieldsFn here, instead redefine 'fields'
        // and call from there:
        $typeConfig['fields'] = function () use ($fieldsFn) {
            $fields = $fieldsFn();
            // do whatever you need with $fields here
            return $fields;
        }
    }
    return $typeConfig;
}

@vladar I will give that a try today and see if it resolves our issue. Thanks

@vladar this indeed solved our issue. Thanks - You can close this request.


[raymath] Lerp Color

[x] I tested it on latest raylib version from master branch
[x] I checked there is no similar issue already reported
[x] My code has no errors or misuse of raylib

Issue description
Add functionality for lerping color to raymath
(feature request)
Environment
Linux, GL 4.6

Sorry, no plans to add this functionality for the moment, it can be implemented on user side.


Add Support for Ecolink Door Sensors

Which device is missing?
There's 2 versions, one looks like zwave plus (I've only got the original)
DWZWAVE1
DWZWAVE2.5-ECO
What are the IDs?
Manufacturer ID: 0x014a
Product type: 0x0001
Product ID: 0x0002
Did you check if we really don't have it?

[x] It is not in the configuration DB
[x] It was not merged recently or has a pending PR
[x] It is not in the TODO list

Do you have a link to the PDF manual?
If so, it helps in creating the config file.
https://products.z-wavealliance.org/products/790?selectedFrequencyId=2
https://products.z-wavealliance.org/products/1498?selectedFrequencyId=2

We support this device already.
packages/config/config/devices/0x014a/dwzwave2.json

That only looks like the DWZWAVE2 version of this device.  There is a DWZWAVE1.
I believe the difference is zwave plus vs zwave.
Testing against 6.4.0 results in:
Unknown manufacturer undefined |   | Unknown product undefined

You have to wake the device up. If it says undefined it will never match any device file.


enable up to 6 spot shadows

This is a trivial change since we moved the lightspace computation
in the fragment shader. The limitation to 6 is due to how we're storing
the culling result.

Wait, wasn't the limitation also because of the number of varyings required?


[1.18.1] Known Issues

The following elements are currently broken in 1.18.1.

[x] Food restrictions
[ ] Origin selection screen may not appear on previously created worlds.
[x] origins:extra_reach is broken
[x] Badges don't work and spam the console.

If you find any other system that is broken, please either open a new issue, or add a comment here.

It also seems that picking Feline can crash the game and rejoin still crashes, I removed it, and seems to work

Getting the same issue, Slimy. Also, none of the powers are working on any origin except the Shulk and Elytrian.

It seems like 1.17.1 forge addons won't work

Origins 1.18 doesn't work with optifine.

another problem, merling doesnt have either nightvision or aqua affinity working. Everything else seems fine. I checked any possible conflict with any mods, and it keeps happening even with only the mod alone. 1.18.1.

origins:phasing and origins:ignore_water are completely non-functional


Restli Client for populating espresso/oracle datasets and schema metadata

1, The espresso datasets and schema metadata population are tested
2, For oracle, need to support abstract schema and then finalize the code
3, The confidential/compliance file needs to be tested later too.
Please let me know if there is any suggestions/comments

It seems strange that even though you renamed the module to restli-client, but the source codes still under folder RestliClient.

@alyiwang some of the files are deleted because of the renaming the module of restli-client

Cleaned up the deleted files, and also update the readme file with a list of jar files

squash and merged.


offset_seconds is wrong if the samplingrate is not 44100

In __init__.py: Dejavu.align_matches(self, matches) is the following code:
nseconds = round(float(largest) / fingerprint.DEFAULT_FS *
                         fingerprint.DEFAULT_WINDOW_SIZE *
                         fingerprint.DEFAULT_OVERLAP_RATIO, 5)

This code does not take the sample rate into account. So if you you have a 22050 Hz file it will always give you the wrong time. For example if there is a match at 10 seconds, it will say "... 'offset_seconds': 5.01551, ..."
It could be fixed by replacing fingerprint.DEFAULT_FS with the real sample rate. For example by adding a sample_rate argument to the method and replacing self.dejavu.align_matches(matches) with self.dejavu.align_matches(matches, self.Fs) in the BaseRecognizer class

agree,i have same situation as you do.


Allow users to close one window in a multi-window app

What problem does this solve or what need does it fill?
The entire app is shut down if any window is closed.
What solution would you like?
Allow users to close one window at a time, building off of https://github.com/bevyengine/bevy/pull/2898.

This exiting behavior can be configured https://github.com/bevyengine/bevy/blob/0bf90bb98db0b977a35d4fb39c06e9dca9bf7f04/crates/bevy_window/src/lib.rs and handled manually.
The configuration should likely be changed to use resources-as-config, and add some built-in preset to handle several common cases: "exit when the last window is closed" (likely the default), "exit when the main window is closed" and "do not exit when windows are closed". The current "exit when any window is closed" behavior doesn't have any compelling use cases IMO.
For reference, this is the existing window exit system:
pub fn exit_on_window_close_system(
    mut app_exit_events: EventWriter<AppExit>,
    mut window_close_requested_events: EventReader<WindowCloseRequested>,
) {
    if window_close_requested_events.iter().next().is_some() {
        app_exit_events.send(AppExit);
    }
}


Fix ng component prop output override

Issue:
App component overrides output component props with handler function instead of subscribe on event.
Output properties should be EventEmitter instance, and function that defined in story, should be subscribed to that event.
What I did
app.component now subscribe handler fn on output EventEmitter if prop is function and output is EventEmitter. Fixed button.component in demo
How to test
Run angular example. Check output property type in component. It should be EventEmitter instance.
Is this testable with jest or storyshots?
no
Does this need a new example in the kitchen sink apps?
no
Does this need an update to the documentation?
no
If your answer is yes to any of these, please make sure to include it in your PR.

@alterx What do you think?

This one looks good to me, I though I had already approved this. Anyway, nice catch @ralzinov :D


feat: allow proxy to run on multiple test environments

Description 📖
Allow proxy to run on multiple test environments.
Background 📜
Let's say that you have multiple test environments with different configurations, e.g.

RAILS_ENV=test - unit tests
RAILS_ENV=test_e2e - end-to-end tests

You might want to be able to run the proxy server in each of these environments while developing or writing tests. With the current implementation of run_proxy?, the ENV name must match "test" exactly for the proxy to run.
The Fix 🔨
This PR contains a simple, but potentially hacky fix - instead of an exact match, we check if mode contains the substring "test". It's hacky because mode can be any arbitrary string, e.g. "greatest_production", that might unintentionally match the condition.
At the risk of bloat, a better way might be to add a config for it, let's say, force_proxy.
Is there already a workaround for this? If not, what would be a suitable way to handle this? I'd be happy to see this PR through.
Screenshots 📷

Hi Brian!
A potential workaround is to skip the proxy in that specific environment, but then you would still probably want dev_server_running? to return true in order to avoid reading from the manifests.
This hasn't come up before, so I'd rather wait before adding more configuration options (such as the one you proposed).
I'd recommend patching run_proxy? in your app, it's part of the public API, so it won't change until a major release (and even then it's unlikely).


[Activity 4.1.3: Queues]: Interview Questions

Issues Closed
Closes #780
Closes #972
...
Changes proposed in this pull request:

Adds 2 interview questions to queues activity, I created a new pull request since taimur's branch was a little confusing
I (Sarah) will update the READMe later

@reviewer/kavuong

never mind the pull request has very large edits which is most likely not the case

@mxthu313
I think you get emailed about me pushing commits, but I just wanted to let you know I implemented your comments


Only Homepage loads - other sites won't open

Hey guys,
the homepage loads successfully, but all other links won't open:
Homepage;

Configure Alerts (same error for other sites)

Any idea what's happening or missing here?
Any help is appreciated, thank you very much,
Christopher

Hi Christopher, for this specific issue kindly refresh the HTML5 repo twice as mentioned here: https://github.com/SAP-samples/btp-resource-consumption-monitor?tab=readme-ov-file#known-issues. This is a temporary bug in Work Zone which will be corrected in a next version.
Please confirm if, after the refresh, the application loads successfully, or whether there is a next error in retrieving the "$metadata" as I expect a bug was introduced in the last commit to this repository.

Hi Christopher, for this specific issue kindly refresh the HTML5 repo twice as mentioned here: https://github.com/SAP-samples/btp-resource-consumption-monitor?tab=readme-ov-file#known-issues. This is a temporary bug in Work Zone which will be corrected in a next version.
Please confirm if, after the refresh, the application loads successfully, or whether there is a next error in retrieving the "$metadata" as I expect a bug was introduced in the last commit to this repository.

Hello @willemi069808 thank you, in the meanwhile I found the "known issue" and I wanted to answer but you were quick. You are right, I'm facing now the $metadata error. So I assume I'll have to wait for a fix, is that correct?

Hi Christopher, I'm in the process of fixing that error, and what should help to resolve this is to make a small change in 2 files:

/cf/app/btprcreport/webapp/manifest.json
/cf/app/managealerts/webapp/manifest.json
each on line 20: change the URI: remove the first/leading slash /

Then rebuild and redeploy etc.

The $metadata error should be resolved with 97749d3. After deployment, if the same error still pops-up in the browser, you can do a clear-cache-and-reload in your browser to make sure you load the latest version.

Awesome, works great. Thank you so much


The data preprocessing card doesn't move here, do you know what the reason is?

Each print statement indicates that a new job has started but has maybe not yet completed. This likely means that all of your CPU cores are currently busy.

The problem has been solved, and I changed the multi-process data preprocessing to for loop processing.


[BUG] Problems in openapi object references

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
When i try to import openapi files in Bruno, for I don't know what reason, Bruno doesn't import the file correctly.
I think that this problem arises from a function that analize object references in the openapi (2th image in screenshots).
To avoid this problem, now I'm using the version 1.34.0.
.bru file to reproduce the bug
No response
Screenshots/Live demo link

Hi, thanks for reporting, we're looking into it.


Ninja build on Windows

Are there any plans to allow for Ninja builds on Windows? MSBuild is dreadfully slow - A simple package I build takes ~ 100 seconds to build a single wheel on Windows, whilst MacOS finishes all 6 of its builds in 125 seconds.
MSVC does have support for Ninja, and if I remember correctly SciKit-Build did once support Ninja builds on Windows, which as much faster.
What are the obstacles for supporting Ninja with MSVC builds? Can they be added in a vendored scikit-build-core for my larger complex builds?

I cannot speak of the scikit-build-core's native support, but you can always add CMAKE_GENERATOR system environment variable and set it Ninja and CMake will use it by default. This works fine with scikit-build-core.
https://cmake.org/cmake/help/latest/variable/CMAKE_GENERATOR.html

Actually the problem that I have is that I can set the generator to Ninja, but it doesn't find the correct compiler in GitHub actions. Honestly I'd like to use anything other than MSVC because of its many shortcomings, but I guess it is the only way to ensure compatibility with Windows users. I know the Numpy devs are considering using clang-cl instead, but AFAIK they haven't moved over yet for much the same reason.

You need to setup msvc to get ninja to find it. Something like https://github.com/ilammy/msvc-dev-cmd should work.

OK that's great, I'll take a look!


Using the new RNN module for speech demo

Fix a typo in executor_group.
Add one more parameter to customize metric: can modify both metric and the number of samples per batch.
Using the new RNN module
optimize frame accuracy (53% -> 63%)
Fix inconsistence of comments and actual code in optimizer (learning_rate) for Adam optimizer.

@pluskid most of the change was only on the speech-demo, except the change for metric.py
@piiswrong , I found that after the refactor of optimizer.py, the comments and actual code are inconsistent. I only fixed for Adam. Would you mind check it and also all the other solvers? Right now, it grab the learning rate from base class which is too huge for some optimizer, e.g. Adam.

yu is referring to the default value for the learning rate that was originally specified for different optimizers. they are recently refactored to inherit a single uniform default value, which might not be good  for all optimizers at the same time. i guess it might be good to consider bringing them back.

this looks good to me.

BTW: @yzhang87 after #1938 is merged, we can then set use_ignore=True and ignore_label=0 to ignore the padded examples in bucketing. Make sure to distinguish between padding and silence in this case.

@yzhang87 Can you rebase again? Let's try to get this merged tonight.

done.
On Fri, Apr 22, 2016 at 10:27 PM, Chiyuan Zhang<EMAIL_ADDRESS>wrote:

@yzhang87 https://github.com/yzhang87 Can you rebase again? Let's try
to get this merged tonight.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/pull/1930#issuecomment-213652193

--
Yu Zhang
Computer Science and Artificial Intelligence Laboratory (CSAIL)
Massachusetts Institute of Technology


Update CHANGELOG.md

What does this PR do?
updates changelog with this contribution: #2317

I'm also not used to it and realized afterwards that I missed it. But the basic procedure is to update the changelog in the same PR, right?


In code documentation with sphinx-js

I have created a documentation directory docs where I setup sphinx with the sphinx_js extension.
Using this we can create reStructuredText Files and reference the functions, classes and other values in
the JS source code of this repository to compile in an easy to read, reference and search static html site.
(Other compilation targets do exist.)
I propose creating further JSDoc documentation (since sphinx-js is based on the syntax of JSDoc) and
building a CI/CD procedure, that automatically builds and deploys the documentation to html and pins it to IPFS and IPNS. Then using a DNSLink to redirect anyone from docs.orbitdb.org to the most recent version of the docs.

If this PR is still valid, please check against version 1 release.


HDR images are either not properly generated, encoded or decoded

High roughness and metallic do cause artefacts.

Fixed here: https://github.com/KhronosGroup/glTF-WebGL-PBR/commit/0f8e470ee408453a3995d2507afaf36a2866735c


Discussion: Streamlining xskillscore

Along the lines of https://github.com/raybellwaves/xskillscore/issues/33 as the package is growing I wonder how we can streamline the package. Right now the code base is getting larger and larger. To navigate around it might help to consolidate.
Some ideas:

Testing vectorized metrics: Have a general function that checks whether _metric from np_deterministic gives the same results as metric from deterministic
Testing dask: Have a general function that checks whether functions in deterministic give the same results lazy as for .load()

Challenges:

Can have think of a template for new metrics? Many metrics are very similar (the math is one line of code) but the code to implement a metric is more than 100 lines of code

np_deterministic gives the same results as metric from deterministic

This can probably be divided into two groups: pearson_r (and maybe spearman) and the other ones. So perhaps test_correlations and the others. Since the former use the following pre-processing:
dim, _ = _preprocess_dims(dim)
    if len(dim) > 1:
        new_dim = "_".join(dim)
        a = a.stack(**{new_dim: dim})
        b = b.stack(**{new_dim: dim})
        if weights is not None:
            weights = weights.stack(**{new_dim: dim})
    else:
        new_dim = dim[0]
    weights = _preprocess_weights(a, dim, new_dim, weights)

and the others use:
dim, axis = _preprocess_dims(dim)
    weights = _preprocess_weights(a, dim, dim, weights)

If this ends up just being four test functions (with and without dask) using fixtures to loop through all the metrics, then we could have a .py file for just testing functions themselves, one for testing weights keyword, and one for testing skipna.

Can have think of a template for new metrics? Many metrics are very similar (the math is one line of code) but the code to implement a metric is more than 100 lines of code

I think this is fine. I'd be more concerned with cleaner tests so we are certain we are covering most of the code in a simple way. But I think as @raybellwaves has mentioned in a few places, it's worth having more lines of code to have each metric as a separate entity and to make sure weights/skipna is implemented correctly.

Welcome to reopen if still think relevant


bug? mobile version 500 errors

I've had it almost every time i first load page. Zrl has had it twice now too.

theoretically resolved by https://github.com/hackclub/sprig-gallery/pull/21

(am monitoring for future occurrences and keeping open for a couple of days)

Hey, for me this error is momentary, whenever a new game is added to the sprig the site crashed, yesterday, when they were adding new games, the Hack Club sites were very unstable (I have a print screen). After Sam's change (https://github.com/hackclub/sprig-gallery/pull/21), I no longer had this problem
(hope I helped :), if I just get in the way, sorry)

We love the participation @LucasHT22 and it's helpful to hear about your experience with the crashes. I also observed it seems to be related to when the site rebuilds.

Lexi added some other safety features to the code so I'll close this now and we can reassess if it comes up again.


(WIP) eq-367 Author create a survey

What is the context of this PR?
Trello card
Adds functionality for authors to add a survey and subsequently associate questionnaires with that survey.
How to review
Describe the steps required to test the changes.

[ ] Do all commits have sensible commit messages?
[ ] Is all new code unit tested?
[ ] Are there integration tests if needed?
[ ] Is there sufficient logging?
[ ] Is there documentation or is the code self-describing?

Who worked on the PR
Describe who worked on the changes, so that other people can review.

Currently, the questionnaires property of a survey is an array of ID—we need to add title, etc to be able to render the view.

 (8) Author: Create a Survey


Demo app for sliding UIView?

I didn't see any sliding UIView demo app inside your Xcode project.

Please advice. Thank you.

I updated the Demo project


[Major][pyreft-core] ReFT next release items

Descriptions:
Based on current priorities, here are a set of items will be released next with experimental results:

layerwise intervention weight sharing to further shrink down #params.
ReFT+LoRA for arithmetic reasoning related steering.
Inference-time intervention manipulations (e.g., clamping, transfer)

Using this ticket to track progress.

Hi Frank! Thanks for the excellent work here. Is it possible to add the functionality to merge the model, not just as a checkpoint, but to have the model completely modified?


Respect SemVer as Cargo understands it

Howdy,
A project I maintain uses notify v4.0, which depends upon both winapi v0.3 and (through a dependency) winapi-util v0.1. You can see a rough graph here:
notify v4.0.*
├── walkdir v2.4.*
│   ├── same-file v1.0.*
│   │   └── winapi-util v0.1.*
│   └── winapi-util v0.1.*
└── winapi v0.3.*

During dependency resolution, Cargo "uses the convention that only changes in the left-most non-zero component are considered incompatible" as defined here. So since this crate is in 0.1.Z, any change to Z is considered compatible as long as the minor version remains 1.
Despite this convention though, v0.1.7 and v0.1.8 were breaking because they altered compatibility. This violates Cargo's SemVer usage, which impacted our project. Based on some searching, I believe this also impacted cargo-watch. One must imagine it is similarly impacting every crate that uses notify v4.0, but I haven't checked.
While you're very much allowed to do whatever you want pre-1.0.0, I would very much appreciate not having to catch changes like this. Please respect Semver as Cargo uses it.

Ummm... okay... Can you please say what the specific incompatibility is? If you're going to say that I broke semver then please tell me what I did. Because it's not obvious to me. You linked to issues, but none of them obviously point to winapi-util?

So, I'd like to apologize for this. I was juggling a lot of details at once so I wasn't as thorough with this as I should've been. I was able to solve the type mismatch users started reporting by pinning winapi-util to version 0.1.6, which lead me to believe this crate was the problem. I've been burnt by crates disobeying semver before so I was made a judgement call without looking too much closer.
After giving it yet more inspection, it turns out that winapi-util is responsible indirectly. Up until 0.1.7, it was enabling several features in winapi. It turns out that some of these features are required by notify to function, but they were never enabled by notify. The result is that when winapi-util updated it caused notify to no longer have the features of winapi it needed, which breaks compilation. This is the 'incompatibility' I noticed.
I... will be frank and say I didn't know this was an issue that could even happen. A crate relying upon features that it doesn't have enabled because a downstream dependency happens to enable them is scary. I'm going to open an issue for Notify, since it's really their fault. I'm very sorry for the inconvenience this caused.

Ah yeah, that makes sense. The same thing happened when I put out a new release of regex-syntax about a year ago. It turned out that tracing-subscriber was implicitly relying on features of regex-syntax to be enabled through an intermediate dependency. There is some discussion there, but the conclusion as far as I can tell is that there is no real way to detect this. But the blame is, as you point out, certainly on the incomplete dependency specification.
winapi-util did indeed used to use winapi. But I was careful in the API design of this crate to avoid making winapi a public dependency. Which is why swapping it out for windows-sys should not have been a breaking change.

Ref https://github.com/notify-rs/notify/issues/601


Powermock & Mockito 2

As it was discussed in ML Mockito has been moved from Cglib to ByteBuddy. More important that since release 2.0.32-beta cglib classes have been moved out into  separated jar Mockito#248.
But PowerMock still depends on classes which have been moved, so users of Powermock get java.lang.NoClassDefFoundError.
In release 1.6.2 Mockito classes was copied into PowerMock, but not all. To continue support newer version of Mockito:

Repack mockito-cglib into Powermock mockito-api. I think new module should be created, like mockito2-api
Next step migrate mockito2-api to ByteBuddy.

I'm going to create a pull request with repacked mockito-cglib soon.

Really cool!! Thanks for your work. I just wonder if it would be possible to somehow extract a "mockito-base" project or similar which is used by both mockito (1) and mockito2? Or is that perhaps a bad idea if they evolve separately?

Thanks, but it's not so great job as that is waiting us in future. I mean port Powemock to Bytebuddy.
I was thinking about extra some common part, but what force me not to do it, that I'm going to change mockito-api and hard to predict what will be changed and what not.
So, I think better try to extract mockito-base, after mockito2 will be ported to bytebuddy.


PG capture does not work well with queryConfig objects.

Per the PG documentation, you should be able to pass a queryConfig object with the shape as the following.  This is not working with the AWSXRay.capturePostgres().  I think the issue is around the fact that we are not passing a callback in but that should trigger the promise returned and it is not.
interface QueryConfig {
  // the raw query text
  text: string;
  // an array of query parameters
  values?: Array<mixed>;
  // name of the query - used for prepared statements
  name?: string;
  // by default rows come out as a key/value pair for each row
  // pass the string 'array' here to receive rows as an array of values
  rowMode?: string;
  // custom type parsers just for this query result
  types?: Types;
}

Looks like you can just update this https://github.com/aws/aws-xray-sdk-node/blob/bd2a8f2554c3969a2b47afb59c1a7085b54f3cd8/packages/postgres/lib/postgres_p.js#L41
to be the following
args.callback = argsObj[2] || argsObj[1] || argsObj[0].callback;

Hi nmaves,
Thanks so much for the deep dive! If you'd like, you can open a PR and we can merge this in, and we can credit you as a contributor.
Can you confirm which version of PG you're using? We'll need to make sure we keep backwards compatibility.
Thanks!
Sandra

@awssandra We are using node-postgres 8.3.3


Would you please update CocoaLumberjack dependency to use latest?

CocoaLumberjack 3.0.0 is out, with fixes for XCode 8 and Swift. Would you please release a version of this logger with the new CocoaLumberjack dependency?
Thanks!

+1 That would be great!

Hi, thanks for the feedback. The next months ahead I will have a hard time finding time for this. All PR:s are very welcome

Hi @dkharrat and @emes LogglyLogger-CocoaLumberjack is now updated. Podspec is pushed and uses 3.0 of CocoaLumberjack.

@melke Many thanks!


Integration Test - Release - 2019/06/12 18:08:07

Auto create for integration test. IssueCommandFlow

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


systemctl enable/disable loop in centos 7 using version 2.6.8

Cookbook version
2.6.8
Chef-client version
12.4.1
Platform Details
centos 7
EC2
Scenario:
Initial converge
Steps to Reproduce:
Using centos 7 with version 2.6.8 of the docker_service lwrp:
docker_service 'default' do
  insecure_registry 'registry.prod.example.com'
  exec_opts ['native.cgroupdriver=cgroupfs']
  if direct_lvm['enabled'] then
    storage_driver 'devicemapper'
    storage_opts [
      'dm.datadev=/dev/vg-docker/data',
      'dm.metadatadev=/dev/vg-docker/data2'
    ]
  end
  action [:create, :start]
end

Expected Result:
Converge enters into a loop in systemctl that disables, daemonctl-reload and enables the docker service.
Actual Result:
https://gist.github.com/jslusher/4d643b2969b9a28c4144a493caa13dd1

Happens on Debian 8 too.

I'm running into this issue as well with version 2.9.3 of the cookbook:
https://gist.github.com/Chili-Man/68fec37d8628fd0648fcd6b80a0d9e5b

I'm surprised systemctl worked at all. I tried on CentOS and on Debian, but systemd related things just do not work for me, I'm guessing because I haven't done my homework (https://lwn.net/Articles/676831/).

I've reverted 4d6956850f79dfe62d25bbfa9bda126f4e80ea1c.

Released as 2.11.1


Unable to Install 16gb Package

Hello!
I was just trying to install the torchstudio on windows 11 on a good system. But when I clicked on install (recommended). It freezed.
The torchstudio stopped working and windows had to forcefully close this app. I reinstalled and tried again, but no luck.

Hi Arnav,A new version is coming soon fixing the installation. Cheers Robin Le 5 juil. 2022 08:56, Arnav Mehta @.***> a écrit :
Hello!
I was just trying to install the torchstudio on windows 11 on a good system. But when I clicked on install (recommended). It freezed.
The torchstudio stopped working and windows had to forcefully close this app. I reinstalled and tried again, but no luck.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


Microsoft Search- Acronym automation

Hi Team,
is there a way to automate acronym addition and publishing in microsoft search.
Scenario is like there is a set of acronym that can be added to search but before adding , it should go for approval and approved acronym can be added and published.
I want to automate this, say by using PowerShell or power automate. If there is any way , please let me know.
Thanks,
Preeti

We have APIs for administration on the horizon. The roadmap item is slightly out of date. Instead of Dec. 2021 it should read Q1CY22. Once the API is available you will be able to use that for your scenarios.