Language Server Failed

Hi!
I tried the current version e0342fde9474fdd0a36ff9692fe0031b7611a19f, as well as several previous releases based on previous issues I found,  but to no avail: using the DEBUG option I always see something similar to this:
Exception: Server port has not been properly initialized. [function codeium#Complete[58]..codeium#server#Request, line 2]
Exception: Server port has not been properly initialized. [function codeium#Complete[58]..codeium#server#Request, line 2]
Launching server with manager_dir /var/folders/xv/hh0nl6vj54jd884f4w3lgh180000gn/T/nvim.sander/3yCi25/1/codeium/manager
[SERVER] 2024/07/27 17:02:29 maxprocs: Leaving GOMAXPROCS=10: CPU quota undefined

[SERVER] I0727 17:02:29.992276 73388 main.go:494] Setting GOMAXPROCS to 10

[SERVER] I0727 17:02:29.993919 73388 main.go:629] Starting language server manager with pid 73388

[SERVER] I0727 17:02:29.997619 73388 main.go:117] Manager acquired its lock file /var/folders/xv/hh0nl6vj54jd884f4w3lgh180000gn/T/nvim.sander/3yCi25/1/codeium/manager/locks/manager.lock
I0727 17:02:29.999808 73388 main.go:256] Waiting for random port file in /var/folders/xv/hh0nl6vj54jd884f4w3lgh180000gn/T/nvim.sander/3yCi25/1/codeium/manager/child_random_port_1722092549997718000_3280701159997779502 to be created

[SERVER] 2024/07/27 17:02:30 maxprocs: Leaving GOMAXPROCS=10: CPU quota undefined

[SERVER] I0727 17:02:30.032452 73390 main.go:494] Setting GOMAXPROCS to 4

[SERVER] I0727 17:02:30.034017 73390 main.go:623] Starting language server process with pid 73390
I0727 17:02:30.034061 73390 server.go:156] Language server will attempt to listen on host <IP_ADDRESS>
F0727 17:02:30.034342 73390 main.go:626] Language server failed - listen tcp <IP_ADDRESS>:0: bind: can't assign requested address
(1) attached stack trace
  -- stack trace:
  | github.com/Exafunction/Exafunction/exa/language_server.CreateLanguageServerAndServe
  | 	exa/language_server/server.go:161
  | main.main
  | 	exa/cmd/language_server/main.go:624
  | runtime.main
  | 	GOROOT/src/runtime/proc.go:267
  | runtime.goexit
  | 	src/runtime/asm_arm64.s:1197
Wraps: (2) listen tcp <IP_ADDRESS>:0
Wraps: (3) bind
Wraps: (4) can't assign requested address
Error types: (1) *withstack.withStack (2) *net.OpError (3) *os.SyscallError (4) syscall.Errno

Exception: Server port has not been properly initialized. [function <SNR>85_SendHeartbeat[2]..codeium#server#Request, line 2]
Exception: Server port has not been properly initialized. [function <SNR>85_SendHeartbeat[2]..codeium#server#Request, line 2]

My Packer setup simply has:
   use ({         'Exafunction/codeium.vim',     })
As well as a lua file containing
vim.keymap.set("i", "<C-;>", function() 	return vim.fn["codeium#Accept"]() end, { expr = true }) vim.g.codeium_no_map_tab = 1 vim.g.codeium_log_file = "~/.codeium/codeium.log" vim.g.codeium_log_level = "DEBUG"
Any ideas?

Hi, I'm getting the same error now, but it started when I tried to bring up ad-hoc networking on my comp. Macos 15.1
sudo networksetup -createnetworkservice AdHoc lo0
sudo networksetup -setmanual AdHoc <IP_ADDRESS> <IP_ADDRESS>.255.255.

I noticed trouble with other apps and services as well and finally connected the dots. As it turned out trying to create ad-hoc networks completely bodges localhost on your machine, at least from Sonoma onwards! (try it, just ping <IP_ADDRESS> and see) After a re-install of 14.6, everything worked again as expected for me. This issue can be closed I think, since it turns out to be a MacOS problem.


Fix link to Go SDK docs

@philipkrueck This is the correct link to the Go SDK docs for this package.

@philipkrueck are you able to get this merged and in a new release? In our Pulumi Registry CI pipelines, we have a link checker and we keep on having the current incorrect link being reported.


No model size reduction seen

Hi! I do not see model size reduction after pruning using llmpcompressor framework. Kindly help

Can you share any more details of what you did?

Hi @sriyachakravarthy we'll have some examples up soon (next few weeks) to help guide this. The current issue is that we do not have full support in compressed tensors for storage of sparse models. This is currently in progress with the following PR: https://github.com/neuralmagic/compressed-tensors/pull/167

Closing due to inactivity. Please reopen if there are follow ups


Can't specify Dockerfile

I am trying to create az ml service with custom docker image.
In the documentation states that az ml service or image create I can add --docker-file argument with custom Dockerfile.
When I run az ml image create -h or service create -h, there is no --docker-file argument.
Please see below:
$ az ml image create -h
Command
az ml image create: Create an Operationalization Image. This command has two different sets of
required arguments, depending on if you want to use a previously created manifest.
Arguments
--image-name -n [Required]: The name of the image being created.
--image-description       : Description of the image.
-v                        : Verbosity flag.
Registered Manifest Arguments
--manifest-id             : [Required] Id of previously registered manifest to use in image
creation.
Unregistered Manifest Arguments
--conda-file -c           : Path to Conda Environment file.
--dependency -d           : Files and directories required by the service. Multiple dependencies
can be specified with additional -d arguments.
--model-file -m           : [Required] The model to be deployed. Multiple models can be
specified with additional -m arguments.
--schema-file -s          : Schema file to add to the manifest.
-f                        : [Required] The code file to be deployed.
-p                        : A pip requirements.txt file needed by the code file.
-r                        : [Required] Runtime of the web service. Valid runtimes are python
|spark-py.
Global Arguments
--debug                   : Increase logging verbosity to show all debug logs.
--help -h                 : Show this help message and exit.
--output -o               : Output format.  Allowed values: json, jsonc, table, tsv.  Default:
json.
--query                   : JMESPath query string. See http://jmespath.org/ for more information
and examples.
--verbose                 : Increase logging verbosity. Use --debug for full debug logs.

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

ID: d35baa32-1146-e4ae-e238-b393714d821b
Version Independent ID: 87250401-0f04-f18b-8349-c46e746bc3ac
Content: Customize the Container Image Used for Deploying Azure ML Models
Content Source: articles/machine-learning/preview/model-management-custom-container.md
Service: machine-learning
GitHub Login: @tedway
Microsoft Alias: tedway, raymondl

I was able to resolve the issue when reinstalling Azure ML Workbench.


[FEATURE] Implement unified processing for LAMBDAS and call-by-name for both built-in and user-defined operators

Since #866 exposes Apalache to call-by-name, and likely an influx in LAMBDA usage, we should come up with a unified way of representing all of these cases. Consider the following expressions:
LET A(p,q) == Append(p,q) IN FoldSeq( A, v, seq ) \* (1)

FoldSeq( Append, v, seq ) \* (2)

FoldSeq( LAMBDA p,q : Append(p,q), v, seq ) \* (3)

Currently, Apalache would fail on (2) and (3), since all of the above expressions either have different internal representations, or are incompatible with typechecking (e.g. in (2), type annotations cannot be supplied, but they should also not be necessary, as the types of built-in operators are known*).
We should preprocess all of the above expressions into the following normal form:
FoldSeq( X, v, seq ) ---> FoldSeq( LET LocalX(p,q) == X(p,q) IN LocalX , v, seq )

* possibly polymorphic/polyadic!

After some investigation, it does not seem likely that we will be supporting LAMBDAs or built-in-operators in the near future, mainly due to the constraints imposed by requiring type annotations (there's currently no way to annotate a LAMBDA).

interesting, I'm new to apalache and may not understand how it works yet, but I was able to annotate a lambda and pass a typecheck with  (* @type: MESSAGE => Bool; *) LAMBDA .....
only to get an error in checking unexpected expression: undeclared operator LAMBDA$2 :)

Yes, while this information is present at typechecking, it (as well as other bits, which cause the error you're getting) gets erased in an internal conversion step later on, because several passes (that mostly predate typechecking) were designed under the assumption that we wouldn't be supporting lambdas, so the support we do have for lambdas at the moment is often ad hoc. We need a better internal representation of lambdas before we can support them properly.
For example, the below spec passes the first typecheck, but fails the 2nd: check --inv=Inv --length=1 test.tla
---------- MODULE test ----------
EXTENDS Apalache

Init == TRUE
Next == TRUE
Inv == FoldSeq( (* @type: (Int,Int) => Int; *) LAMBDA p,q: p, 0, <<>> ) = 0

====================

...
PASS #1: TypeCheckerSnowcat                                       I@16:04:55.242
 > Running Snowcat .::.                                           I@16:04:55.242
 > Your types are great!                                          I@16:04:55.335
 > All expressions are typed
...
PASS #12: PostTypeCheckerSnowcat                                  I@16:04:55.557
 > Running Snowcat .::.                                           I@16:04:55.557
[test.tla:6:48-6:60]: No annotation found for LAMBDA$1. Make sure that you've put one in front of LAMBDA$1. E@16:04:55.563

Until this is addressed, I'd recommend writing LET-IN instead of lambdas, e.g.
LET \* @type: (T1,T2) => T1;
    NotLambda(p,q) == ...
IN FoldSeq( NotLambda , v, seq )

Right, thanks for the info, and the workaround! :)

@Kukovec is it still an issue?

I'm not sure we have consensus on whether or not we want to support lambdas at all in the future, but the annotation-before-lambda parsing hasn't been fixed yet.

Rather, I think we should use this issue to keep track of what the lambda form we end up supporting is going to be. Unless you want to make a whole new issue for that?

I guess you can close this and keep https://github.com/informalsystems/apalache/issues/2532


Roll Flutter Engine from 94f852d2348c to a8e49bb78ef1 (4 revisions)

https://github.com/flutter/engine/compare/94f852d2348c...a8e49bb78ef1
2024-09-18<EMAIL_ADDRESS>Roll Skia from a60a52a11763 to 321d7750aa07 (2 revisions) (flutter/engine#55290)
2024-09-18<EMAIL_ADDRESS>[ios] Update gesture position on every event (flutter/engine#55285)
2024-09-18<EMAIL_ADDRESS>Roll Dart SDK from 9164e2c0e994 to 379f0145421f (1 revision) (flutter/engine#55289)
2024-09-18<EMAIL_ADDRESS>Roll Skia from 760e37059fde to a60a52a11763 (2 revisions) (flutter/engine#55287)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC chinmaygarde@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Migrate changelogs to GitHub release notes

During today's meeting, @olafurpg suggested to use GitHub release notes instead of our own changelog/ folder with markdown files. The motivation for this change is to avoid non-standard approaches / tools as much as possible. I am convinced and fully support this idea.

Done. I've moved the changelogs to GitHub releases. v2.0.0 changelog is saved as a draft. I propose we keep the changelog/ directory with markdown files for at least a few more releases to preserve old links.

I propose we release v2.0.0 since RC3 seems to be working nicely for 5 days now without problems.

👍


Crashing

i am from China ,sorry for my poor English.but I need your help .my homebridge crashed .could you help me.
here is the log
{"id":-1,"method":"get_prop","params":["power"]}
send hb to: 0x00000000036fee76
{"id":-1,"method":"get_prop","params":["power"]}
/usr/lib/node_modules/homebridge-aqara/lib/AqaraAccessoryFactory.js:75
var gatewaySid = this.gatewaySids[accessory.UUID];
^
TypeError: Cannot read property 'UUID' of undefined
at AqaraAccessoryFactory.autoRemoveAccessory (/usr/lib/node_modules/homebridge-aqara/lib/AqaraAccessoryFactory.js:75:48)
at Timeout._onTimeout (/usr/lib/node_modules/homebridge-aqara/lib/AqaraPlatform.js:103:15)
at ontimeout (timers.js:386:11)
at tryOnTimeout (timers.js:250:5)
at Timer.listOnTimeout (timers.js:214:5)
here is my config.json
{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"platforms": [
{
"platform": "MiAqaraPlatform",
"sid": ["395c72b82c51413a"],
"password": ["34ce00idbd86"]
},
]
}

Hi,
As this problem is with the homebridge-aqara plugin, please raise an issue there.

On Nov 13, 2017, at 10:02 AM, stonerocky<EMAIL_ADDRESS>wrote:
/usr/lib/node_modules/homebridge-aqara


Use adminkubeconfig in migration test

How to categorize this PR?

/area testing
/kind bug
What this PR does / why we need it:
Use adminkubeconfig in migration test, instead of looking for kubeconfig secret.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Introduced with https://github.com/gardener/gardener/pull/7503
Release note:

NONE

/assign

/test pull-gardener-e2e-kind-ha-single-zone


OpenID not supported on Android

Summary
Appears according to documentation that only web interfaces support OpenID.
Using mobile platform, in this case Android, there is no option to see/use the OpenID provider; option is plain missing.
Using the community Team Edition.
Steps to reproduce
Configure OpenID, visually see it in the web and able to login.
Open the mobile app and sign in page has no option other than username/email login.
Once OpenID is configured you can no longer use username/email to authenticate.
This renders OpenID useless if you want to use the mobile app.
Signing in on the mobile app first and then link your account to OpenID subsequently signs you out on mobile.
Expected behavior
Implement support for OpenID for Android or at least allow multiple sign-ins such as OpenID and username/email login.
Observed behavior (that appears unintentional)
N/A
Possible fixes
N/A

Our upcoming Mobile V2 release will support OpenID in Team Edition: https://github.com/mattermost/mattermost-mobile/pull/6755. The release is currently scheduled for December 15th.

Our upcoming Mobile V2 release will support OpenID in Team Edition: #6755. The release is currently scheduled for December 15th.

Thats excellent, thank you for the swift response.
Look forward to the feature.

I have been looking out for the new feature but instead noticed its now completely removed from the Teams Edition.
Thought I was going nuts and then review the guide: https://docs.mattermost.com/onboard/sso-openidconnect.html
Its gone from authentication, has this now been removed?

I have been looking out for the new feature but instead noticed its now completely removed from the Teams Edition.
Thought I was going nuts and then review the guide: https://docs.mattermost.com/onboard/sso-openidconnect.html
Its gone from authentication, has this now been removed?

This is scheduled to be added for Team Edition for v7.7 and Mobile v2 releases (January 16th releases).

New ETA on this? 😊

Hey @ados8 , OpenID support isn't available in Team edition as of today. Apologies for any confusion the docs caused!

@ados8 Feel free to share this feature request on our feature request forum here https://mattermost.com/suggestions/.

How is it suddenly not supported when it was mentioned above it was about to release??

I don't know the full context, but there was an initial plan to add this to the Free version, but it was later reverted.


Live data not refreshing

Dear,
When using the plugin the live data is not refreshing unless it's triggered through a connection to the live data with the Enlighten app.
This is documented in https://support.enphase.com/s/question/0D53m00008sfiRcCAI/live-status-via-envoy-or-the-app-offline-feature-freezes?t=1683273624635
the sc_stream flag will become enabled and the MQTT data will be updating
{
"connection": {
"mqtt_state": "connected",
"prov_state": "configured",
"auth_state": "ok",
"sc_stream": "disabled",
"sc_debug": "disabled"
},
The workaround suggested by Enphase is to query   ivp/livedata/status.
API ivp/livedata/stream needs to be used in POST, json to pass: {“enable”: 1}
Field ‘mains_admin_state’ is not a required field
Response should be,
{
"sc_stream": "enabled"
}
KR
Yves

This is exactly the issue I also described here: https://github.com/grzegorz914/homebridge-enphase-envoy/issues/80. Would be great to get this fixed...

Just tried with the CURL command listed on the enphase support page listed above and this works for me. Implementing this would really make the plugin even more useful, @grzegorz914 !

will do it asap

try 6.7.33-beta.0 and let me know, debug  log please

Just installed it and it works. I had enabled LiveData with CURL already before so I cannot tell (yet) if it solves the problem permanently. Last time I did the enabling with CURL it was reporting for about 1,5 days before stopping again. I will report back here when any issue appears. Many thanks!

2023-05-11 Homebridge Enphase log.txt
@grzegorz914 Hope this contains what you have been looking for.

Is that working correct, any issue?

homebridge.log.txt
Stopped updating this night, debug log attached. Had to restart around 7:03AM

Now it also stopped on my side with Device: <IP_ADDRESS> Envoy-S, Update live data error: AxiosError: Request failed with status code 400. Reconnect in 15s. After executing the CURL again, it worked. So it seems you need to add a check and if the live data is not updated for some time, the API needs to be enabled again.

Debug Please , go to plugin settings advanced section nad enable debug, then get the whole log.

I had attached my debug log this morning
Yves

On 12 May 2023, at 16:52, Grzegorz @.***> wrote:
Debug Please , go to plugin settings advanced section nad enable debug, then get the whole log.
—
Reply to this email directly, view it on GitHub https://github.com/grzegorz914/homebridge-enphase-envoy/issues/85#issuecomment-1545869090, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWWBF6AE4VJFPCBFVLI6O73XFZFC5ANCNFSM6AAAAAAXW5KFY4.
You are receiving this because you authored the thread.

No, you have attached normal log, you need enable debug in my plugin settings advanced section.

Im pushed 6.7.34-beta.0 please install and let me know with debug log again

HI,
Stopped again today after running the latest 6.7.34-beta.0 since Friday. Restarting homebridge didn't help. Still error 400 requesting live data.  I had to force the scstream to enabled and then it started working again
Attached debug log
homebridge.log (2).txt

try beta.1

Any info?

Hello,
Last weekend it stopped working so I had put my workaround In motion again ( curl to 'enable' the sc_stream). I stopped this one again and am waiting for the issue to occur again. Once I provoke it I will share the logs
KR
Yves

Still the problem exist with latest 7.x.x versions?

yes, from time to time I have to push the  'enable:1' to /ivp/livedata/stream. But much less frequent then before

yes, from time to time I have to push the 'enable:1' to /ivp/livedata/stream. But much less frequent then before

Same here.

any debug log?  I don't have envoy with fw7.x.x and can not test this locally

I will try to create one but this will be tricky as it only occurs every couple of days...

I have pushed 7.3.6-beta.0 with enabled debug only for live data. This reduce the log.

I have pushed beta.1 to test, can you disable live data with:
curl -f -k -H "Authorization:bearer <token> -H "Content-Type:application/json" -d "{\"enable\":0}" https://envoy.local/ivp/livedata/stream
and check again with beta.1

Mmh, not really helping I guess:
[7/30/2023, 12:21:46 PM] [homebridge-enphase-envoy] Device: <IP_ADDRESS> Envoy-S, Update live data error: Enable live data stream error: AxiosError: Request failed with status code 400.. Trying again in: 5 sec. [7/30/2023, 12:21:51 PM] [homebridge-enphase-envoy] Device: <IP_ADDRESS> Envoy-S, debug: Live data: {   "connection": {     "mqtt_state": "connected",     "prov_state": "configured",     "auth_state": "ok",     "sc_stream": "enabled",     "sc_debug": "disabled"   },   "meters": {     "last_update":<PHONE_NUMBER>,     "soc": 100,     "main_relay_state": 1,     "gen_relay_state": 5,     "backup_bat_mode": 1,     "backup_soc": 0,     "is_split_phase": 0,     "phase_count": 3,     "enc_agg_soc": 100,     "enc_agg_energy": 3500,     "acb_agg_soc": 0,     "acb_agg_energy": 0,     "pv": {       "agg_p_mw": 667121,       "agg_s_mva": 851692,       "agg_p_ph_a_mw": 210791,       "agg_p_ph_b_mw": 182769,       "agg_p_ph_c_mw": 273560,       "agg_s_ph_a_mva": 244074,       "agg_s_ph_b_mva": 225773,       "agg_s_ph_c_mva": 381844     },     "storage": {       "agg_p_mw": 0,       "agg_s_mva": 0,       "agg_p_ph_a_mw": 0,       "agg_p_ph_b_mw": 0,       "agg_p_ph_c_mw": 0,       "agg_s_ph_a_mva": 0,       "agg_s_ph_b_mva": 0,       "agg_s_ph_c_mva": 0     },     "grid": {       "agg_p_mw": -338577,       "agg_s_mva": -247076,       "agg_p_ph_a_mw": 38329,       "agg_p_ph_b_mw": -182587,       "agg_p_ph_c_mw": -194320,       "agg_s_ph_a_mva": 388775,       "agg_s_ph_b_mva": -241660,       "agg_s_ph_c_mva": -394192     },     "load": {       "agg_p_mw": 328544,       "agg_s_mva": 604616,       "agg_p_ph_a_mw": 249120,       "agg_p_ph_b_mw": 182,       "agg_p_ph_c_mw": 79240,       "agg_s_ph_a_mva": 632849,       "agg_s_ph_b_mva": -15887,       "agg_s_ph_c_mva": -12348     },     "generator": {       "agg_p_mw": 0,       "agg_s_mva": 0,       "agg_p_ph_a_mw": 0,       "agg_p_ph_b_mw": 0,       "agg_p_ph_c_mw": 0,       "agg_s_ph_a_mva": 0,       "agg_s_ph_b_mva": 0,       "agg_s_ph_c_mva": 0     }   },   "tasks": {     "task_id": -2018101439,     "timestamp":<PHONE_NUMBER>   },   "counters": {     "main_CfgLoad": 1,     "main_CfgChanged": 1,     "main_taskUpdate": 31,     "MqttClient_publish": 908,     "MqttClient_respond": 66,     "MqttClient_msgarrvd": 33,     "MqttClient_create": 28,     "MqttClient_setCallbacks": 28,     "MqttClient_connect": 28,     "MqttClient_connect_err": 22,     "MqttClient_connect_Err": 22,     "MqttClient_subscribe": 6,     "SSL_Keys_Create": 28,     "sc_hdlDataPub": 609958,     "sc_SendStreamCtrl": 7,     "sc_SendDemandRspCtrl": 1,     "rest_Status": 128483   },   "dry_contacts": {     "": {       "dry_contact_id": "",       "dry_contact_type": "",       "dry_contact_load_name": "",       "dry_contact_status": 3050996     }   } }

sc_stream is enabled, the data need to be refreshed correct

sc_stream is enabled, the data need to be refreshed correct

Not really, I tried it again but I only see the data in MQTT when I enable the LIVE API again:
[7/30/2023, 1:09:45 PM] [homebridge-enphase-envoy] Device: <IP_ADDRESS> Envoy-S, Update live data error: Enable live data stream error: AxiosError: Request failed with status code 400.. Trying again in: 5 sec. [7/30/2023, 1:09:50 PM] [homebridge-enphase-envoy] Device: <IP_ADDRESS> Envoy-S, debug: Live data: {   "connection": {     "mqtt_state": "connected",     "prov_state": "configured",     "auth_state": "ok",     "sc_stream": "disabled",     "sc_debug": "disabled"   },   "meters": {     "last_update":<PHONE_NUMBER>,     "soc": 100,     "main_relay_state": 1,     "gen_relay_state": 5,     "backup_bat_mode": 1,     "backup_soc": 0,     "is_split_phase": 0,     "phase_count": 3,     "enc_agg_soc": 100,     "enc_agg_energy": 3500,     "acb_agg_soc": 0,     "acb_agg_energy": 0,     "pv": {       "agg_p_mw": 5400356,       "agg_s_mva": 5414954,       "agg_p_ph_a_mw": 1762651,       "agg_p_ph_b_mw": 1538336,       "agg_p_ph_c_mw": 2099368,       "agg_s_ph_a_mva": 1769935,       "agg_s_ph_b_mva": 1538336,       "agg_s_ph_c_mva": 2106683     },     "storage": {       "agg_p_mw": 0,       "agg_s_mva": 0,       "agg_p_ph_a_mw": 0,       "agg_p_ph_b_mw": 0,       "agg_p_ph_c_mw": 0,       "agg_s_ph_a_mva": 0,       "agg_s_ph_b_mva": 0,       "agg_s_ph_c_mva": 0     },     "grid": {       "agg_p_mw": -5069412,       "agg_s_mva": -5135115,       "agg_p_ph_a_mw": -1500953,       "agg_p_ph_b_mw": -1535226,       "agg_p_ph_c_mw": -2033233,       "agg_s_ph_a_mva": -1544777,       "agg_s_ph_b_mva": -1540709,       "agg_s_ph_c_mva": -2049630     },     "load": {       "agg_p_mw": 330944,       "agg_s_mva": 279839,       "agg_p_ph_a_mw": 261698,       "agg_p_ph_b_mw": 3110,       "agg_p_ph_c_mw": 66135,       "agg_s_ph_a_mva": 225158,       "agg_s_ph_b_mva": -2373,       "agg_s_ph_c_mva": 57053     },     "generator": {       "agg_p_mw": 0,       "agg_s_mva": 0,       "agg_p_ph_a_mw": 0,       "agg_p_ph_b_mw": 0,       "agg_p_ph_c_mw": 0,       "agg_s_ph_a_mva": 0,       "agg_s_ph_b_mva": 0,       "agg_s_ph_c_mva": 0     }   },   "tasks": {     "task_id": -2018101439,     "timestamp":<PHONE_NUMBER>   },   "counters": {     "main_CfgLoad": 1,     "main_CfgChanged": 1,     "main_taskUpdate": 31,     "MqttClient_publish": 908,     "MqttClient_respond": 66,     "MqttClient_msgarrvd": 33,     "MqttClient_create": 28,     "MqttClient_setCallbacks": 28,     "MqttClient_connect": 28,     "MqttClient_connect_err": 22,     "MqttClient_connect_Err": 22,     "MqttClient_subscribe": 6,     "SSL_Keys_Create": 28,     "sc_hdlDataPub": 612744,     "sc_SendStreamCtrl": 10,     "sc_SendDemandRspCtrl": 1,     "rest_Status": 129085   },   "dry_contacts": {     "": {       "dry_contact_id": "",       "dry_contact_type": "",       "dry_contact_load_name": "",       "dry_contact_status": 3050996     }   } } [7/30/2023, 1:09:50 PM] [homebridge-enphase-envoy] Device: <IP_ADDRESS> Envoy-S, Update live data error: Enable live data stream error: AxiosError: Request failed with status code 400.. Trying again in: 5 sec. [7/30/2023, 1:09:55 PM] [homebridge-enphase-envoy] Device: <IP_ADDRESS> Envoy-S, debug: Live data: {   "connection": {     "mqtt_state": "connected",     "prov_state": "configured",     "auth_state": "ok",     "sc_stream": "disabled",     "sc_debug": "disabled"   },   "meters": {     "last_update":<PHONE_NUMBER>,     "soc": 100,     "main_relay_state": 1,     "gen_relay_state": 5,     "backup_bat_mode": 1,     "backup_soc": 0,     "is_split_phase": 0,     "phase_count": 3,     "enc_agg_soc": 100,     "enc_agg_energy": 3500,     "acb_agg_soc": 0,     "acb_agg_energy": 0,     "pv": {       "agg_p_mw": 5400356,       "agg_s_mva": 5414954,       "agg_p_ph_a_mw": 1762651,       "agg_p_ph_b_mw": 1538336,       "agg_p_ph_c_mw": 2099368,       "agg_s_ph_a_mva": 1769935,       "agg_s_ph_b_mva": 1538336,       "agg_s_ph_c_mva": 2106683     },     "storage": {       "agg_p_mw": 0,       "agg_s_mva": 0,       "agg_p_ph_a_mw": 0,       "agg_p_ph_b_mw": 0,       "agg_p_ph_c_mw": 0,       "agg_s_ph_a_mva": 0,       "agg_s_ph_b_mva": 0,       "agg_s_ph_c_mva": 0     },     "grid": {       "agg_p_mw": -5069412,       "agg_s_mva": -5135115,       "agg_p_ph_a_mw": -1500953,       "agg_p_ph_b_mw": -1535226,       "agg_p_ph_c_mw": -2033233,       "agg_s_ph_a_mva": -1544777,       "agg_s_ph_b_mva": -1540709,       "agg_s_ph_c_mva": -2049630     },     "load": {       "agg_p_mw": 330944,       "agg_s_mva": 279839,       "agg_p_ph_a_mw": 261698,       "agg_p_ph_b_mw": 3110,       "agg_p_ph_c_mw": 66135,       "agg_s_ph_a_mva": 225158,       "agg_s_ph_b_mva": -2373,       "agg_s_ph_c_mva": 57053     },     "generator": {       "agg_p_mw": 0,       "agg_s_mva": 0,       "agg_p_ph_a_mw": 0,       "agg_p_ph_b_mw": 0,       "agg_p_ph_c_mw": 0,       "agg_s_ph_a_mva": 0,       "agg_s_ph_b_mva": 0,       "agg_s_ph_c_mva": 0     }   },   "tasks": {     "task_id": -2018101439,     "timestamp":<PHONE_NUMBER>   },   "counters": {     "main_CfgLoad": 1,     "main_CfgChanged": 1,     "main_taskUpdate": 31,     "MqttClient_publish": 908,     "MqttClient_respond": 66,     "MqttClient_msgarrvd": 33,     "MqttClient_create": 28,     "MqttClient_setCallbacks": 28,     "MqttClient_connect": 28,     "MqttClient_connect_err": 22,     "MqttClient_connect_Err": 22,     "MqttClient_subscribe": 6,     "SSL_Keys_Create": 28,     "sc_hdlDataPub": 612744,     "sc_SendStreamCtrl": 10,     "sc_SendDemandRspCtrl": 1,     "rest_Status": 129086   },   "dry_contacts": {     "": {       "dry_contact_id": "",       "dry_contact_type": "",       "dry_contact_load_name": "",       "dry_contact_status": 3050996     }   } } [7/30/2023, 1:09:55 PM] [homebridge-enphase-envoy] Device: <IP_ADDRESS> Envoy-S, Update live data error: Enable live data stream error: AxiosError: Request failed with status code 400.. Trying again in: 5 sec.

Hello Guys,
i'm owner of an enphase system since august and tryed the same thing like @ahnungsbefreit. I'm running the homebridge plugin on version v7.4.4 and got the same issue with the live data. Do you have any updates @grzegorz914 or has any body else an workaround for me?
Greetz Danny

an workaround for me?

Hi Danny, I solved it for me with a small script running in ioBroker which is checking is LiveDate is updated and if the last 5 MQTT strings did not contain an update, I re-active LiveData via an API call. This works fine so far and is triggered only every couple of days...

Good morning, and thank you very much for your prompt response! I actually implemented a similar solution yesterday. I wrote a small script in IoBroker that makes periodic API calls and checks the status of 'sc_stream.' As long as it's set to 'enabled,' nothing happens. If it switches to 'disabled,' it notifies me via Telegram, makes an API call to set it back to 'enabled,' and then sends me a success message via Telegram. If you're interested in the script, please let me know.

Hi all,
Im pushed 7.4.5-beta.6 to test, here try to fix live data refresh.
I don't have encharges installed in my environment, so is hard to test it on my side.
Please test and let me know with debug log.
Thanks

fixed with 7.6.0


missing comdecl.h

Hello there, I am trying to compile the DirectXTK but I am having problem with an header:
#include <C:\Program Files (x86)\Microsoft DirectX SDK (June 2010)\Include\comdecl.h>
At line 46 of the Audio.h it is trying to include with full path that header. By googling around it looks like now the comdecl.h should be part of the windows sdk. I dont have the (June 2010) folder at all, but my windows sdk is up to date, I am running windows 10 by the way.
I run a search for comdecl.h and the only one showed up was the one inside the unreal engine.
Anyone got an idea on the problem?
I did not find an official download fo the june 2010 directX only one hosted on other websites like cnet etc.
I don't have much experience with the win sdk or api in general so sorry if it is a dumb question

This is covered in the wiki.
If you are building an app with Windows 7 or Windows Vista compatibility, then _WIN32_WINNT is set to 0x0601 or 0x0600. In that case, you must use the legacy DirectX SDK to get a version of XAudio that is compatible with the target operating system. To resolve the error you are getting, you have to add the DirectX SDK include paths to your projects VC++ Directories--be sure to add it after the existing paths and not before. You must make sure you are using the appropriate _DXSDK vcxproj files so that you are using the XAudio 2.7 version of DirectXTK.
Alternatively, you can set your application to build with _WIN32_WINNT set to 0x0602 (Windows 8.0), 0x0603 (Windows 8.1), or 0x0A00 (Windows 10) which will make use of the XAudio 2.8 or XAudio 2.9 built into the Windows SDK. You need to make sure you are using the appropriate _Win8 or _Win10 vcxproj file so your DirectXTK is built to match.

Note this setup issue is also covered in the Adding the DirectX Tool Kit for Audio tutorial lesson.

Thanks a lot, I actually ended up on that page before, but for some reason I was convinced I needed Xaudio2.7. I am gonna try to compile when I get to my computer and let you know.
M.


screenshot

Can someone please show me how this chat looks like? I demo or at least a screenshot would be very helpful!

Well the package is primarily just the backend functionality of a messaging system. This leaves a lot more flexibility for the developer to make it into what they need it to be. I do have a few starting view files included that will give you some good basics (in Bootstrap).
Messages Index Page...

Message Thread Page...

A custom responsive templates in mobile view:

 - sry, wrong link

Like you See including twemoji, but I have to add some more replacement codes like :) ;) :P and so on

Like @cmgmyr said: it's just the Backend, so you can do whatever you want, that's why I love this package cause it doesn't force you to any routing, views or anything you don't want.

@Gummibeer your link returned: Not Found


#960 feat(UAC): change default ownership to admins for externally created resources

This change includes GUI, rest API, DB and migration
The default ownership  will be:
Container <without ownership> --> Admin
Container <with ownership>    --> Public/Private

Closes #960

@ncresswell played with this a bit, looks OK. Thing to note: all public resources will be updated to administrator restricted (be it default policy or assigned by the user).

Thanks @ricardona :+1:

Hi
We just migrated to 1.19.2 and, as expected, all our resources have migrated to admin only instead of public (we deploy apps outside of portainer)
I look for a parameter to change this behavior (default to public)
Is there a such parameter ?
Our use of portainer is to have on only portainer instance managing many clusters
Admin may have access to all clusters, but users get access only to certain endpoints
Users accessing a endpoint have all access on that endpint, so public is fine
As a workaroud, i'll soon write a batch process to change admin ownership to public, so that newly deployed apps are set to public
Thanx

I look for a parameter to change this behavior (default to public)
Is there a such parameter ?

There is none.
Although, we're planning on introducing UAC related labels in the next release, see: https://github.com/portainer/portainer/issues/1257#issuecomment-421908587
Would that be of any help to you?

Yes it should be nice with that
The API allow me to be very efficient, I just code my batch in few minutes to get what I want
So it's fine for me for now, just waiting for labels 😃
Thanx

Our use of portainer is to have an only portainer instance managing many clusters
Admin may have access to all clusters, but users get access only to certain endpoints
Users accessing a endpoint have all access on that endpint, so public is fine

@WTFKr0  Your use case is similar to #2190 Segregate logically Portainer resources using projects and it will be included in the next release too. Could that help?
@deviantony #1257 and #2190 are trying to solve the same problem "declare access privileges in the compose file or from docker CLI". Does that mean that one should be discarded?

@ricardona I don't think so.
#1257 aims to provide the ability to set-up access control policies via labels.
#2190 aims to introduce a new project entity as well as enhance Portainer views to support project visualization.


npm not registered?

Hey,
How can I install this package via the NPM?
Thanks

Package name is unzip2 and not unzip


[BUG] PHP 8.2.9 composer update failed.

uname -a
Linux debian-lijc 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22) x86_64 GNU/Linux

php -v
PHP 8.2.9 (cli) (built: Aug 29 2023 10:48:25) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.2.9, Copyright (c) Zend Technologies
    with Zend OPcache v8.2.9, Copyright (c), by Zend Technologies

composer info | grep hypref
No dependencies installed. Try running composer install or update.

php --ri swoole

swoole

Swoole => enabled
Author => Swoole Team<EMAIL_ADDRESS>Version => 5.0.1
Built => Dec  9 2022 13:55:32
coroutine => enabled with boost asm context
epoll => enabled
eventfd => enabled
signalfd => enabled
cpu_affinity => enabled
spinlock => enabled
rwlock => enabled
sockets => enabled
openssl => OpenSSL 1.1.1n  15 Mar 2022
dtls => enabled
http2 => enabled
json => enabled
curl-native => enabled
pcre => enabled
mutex_timedlock => enabled
pthread_barrier => enabled
futex => enabled
mysqlnd => enabled
async_redis => enabled

Directive => Local Value => Master Value
swoole.enable_coroutine => On => On
swoole.enable_library => On => On
swoole.enable_preemptive_scheduler => Off => Off
swoole.display_errors => On => On
swoole.use_shortname => On => On
swoole.unixsock_buffer_size => 8388608 => 8388608

Description:
run composer update report dependency failed:
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires longlang/phpkafka ^1.2.3, found longlang/phpkafka[dev-master, v1.0.0, ..., v1.2.2] but it does not match the constraint.
  Problem 2
    - laminas/laminas-mime[2.7.0, ..., 2.7.x-dev] require php ^5.6 || ^7.0 -> your php version (8.2.9) does not satisfy that requirement.
    - laminas/laminas-mime[2.8.0, ..., 2.8.x-dev] require php ^7.3 || ~8.0.0 -> your php version (8.2.9) does not satisfy that requirement.
    - laminas/laminas-mime[2.9.0, ..., 2.11.x-dev] require php ^7.3 || ~8.0.0 || ~8.1.0 -> your php version (8.2.9) does not satisfy that requirement.
    - Root composer.json requires laminas/laminas-mime ^2.7 -> satisfiable by laminas/laminas-mime[2.7.0, ..., 2.11.x-dev].

Please help.

换个源试试

镜像源问题，没有拉取到最新包版本

有推荐的源吗，我用的是 aliyun 的 @xuanyanwow

@jasli2 官方源最靠谱，结合优质的科学上网

@xuanyanwow thx
我换了腾讯的源，可以了。


Character limit in MOTD

I don't think this is a limitation of magicked administrator. Rather a limit of the web admin


Define a default User-Agent header

I'll allow the array notation this time @jabley next time I'm coming for you!!!

Not performance-critical code
:dancers:

This is problematic so I'm going to have to revert it out.


[IPCT1-355] - Refactor beneficiary transaction

This PR fixes [IPCT1-355] at https://impactmarket.atlassian.net/browse/IPCT1-355
Changes
changed beneficiarytransaction table to ubi_beneficiary_transaction
New

Tests
all tests passed

@obernardovieira  now the migration has a limit and offset


Question for fix traffic spawn

Hi! Thank you for the work!
I am new to this simulator and would like to create a multi agent intersection scenario with fix traffic flow settings for each agent, for example, starting point and ending point for each agent, each vehicle type corresponds to its vehicle ID, scheduling for each of vehicles at each time step. Will there be a way similar to SUMO i could self design the traffic flow config?
Thank you!

Hi,
Welcome and sorry for the late reply.
It can be achieved but would be a bit difficult for a beginner as we don't have such an interface like SUMO. If you check the Multi-agent environment and set the allow_respawn=False, you will find that actually all vehicles are assigned a destination and spawn point when they are created, which is pretty similar to what you want. To adapt it to your need, you have to set the spawn point and destination on your own rather than randomly picking from some candidate positions, which requires some effort.
Quanyi


Encoding Error

Is your feature request related to a problem? Please describe.
I'm receiving a compressed gzip stream message from azure service bus, when trying to print this message using str(msg), we are receiving this error: 'utf-8' coded can't decode byte 0x8b in position 5: invalid start byte.
This used to work fine in the old version (0.50.3) with msg.body.
Describe the solution you'd like
is there any alternative method to convert the default Unicode conversion?
Describe alternatives you've considered
I was not able to find any alternative solution to this problem.
Additional context
N/A

Found a alternative solution


Fix hot module replacement for RN 0.12

New in<EMAIL_ADDRESS>when using the Chrome debugger, the app bundle is now run inside a web worker: https://github.com/facebook/react-native/pull/1632, https://github.com/facebook/react-native/commit/8db35d492b846f51a758e8ee7e5e402c6bad3785
This means that an app bundle built with webpack's hot module replacement enabled will raise errors such as #99, and hot module replacement will fail.

I'm able to get HMR working on the rn-0.12-hmr branch by doing the following:

Use webpack-dev-middleware + webpack-hot-middleware instead of webpack/hot/only-dev-server + webpack-dev-server/client:
webpack-dev-server depends on window.postMessage to broadcast "webpackHotUpdate" events to any loaded scripts (usually just 'webpack/hot/dev-server' or 'webpack/hot/only-dev-server'), which does not work in the context of a web worker since web workers have a different postMessage API. webpack-hot-middleware is an alternative which combines the functionality of both webpack/hot/only-dev-server and webpack-dev-server/client.

Patch webpack so it uses importScripts inside a web worker instead of the default behaviour of appending a <script> with the new hot-reloaded module: https://github.com/elliottsj/webpack/commit/743a00a8bc491f1900ce9f49150229183f874da1.
Known issue: this inexplicable error is thrown every time a module is hot reloaded:

Not sure why this happens; the original error message & stack gets lost somewhere.

Try out rn-0.12-hmr/Examples/BabelES6 for a working example.
My patch to webpack seems quite hacky; I think the proper solution is to make something like 'WebWorkerMainTemplate.runtime.js', but I don't know enough about webpack internals to know what to do here.
Does anyone have any ideas on the proper way to do HMR from inside the web worker? cc @gaearon @sokra

WebWorkerMainTemplate.runtime.js is the way to go. Settings target: "webworker" will enabled it. Should be pretty easy to write as importScripts is sync.
WebWorkerHotUpdateChunkTemplatePlugin.js is also needed to defined the hot update chunk format for web workers, but it can be equal to JsonpHotUpdateChunkTemplatePlugin.js.
If someone want to do a PR to webpack, I would be happy...

Opened PR to support HMR in web workers: https://github.com/webpack/webpack/pull/1521

I tried using your branch, but I get this warning the first time I change a file (and HMR doesn't work):

...

Any opinions?

@dapetcu21 Hi, i'm stuck with this webworker error and maybe you can help me. Where did you put the "var worker = new Worker("bundle.js");"?

@paolorovella You don't need var worker = new Worker("bundle.js");. The RN debugger will load the bundle into a web worker for you; try out the rn-0.12-hmr/Examples/BabelES6 example.

I finally did it! I've use this example without var worker = new Worker("bundle.js"); and without target:"webworker"...thank you so much :)

@paolorovella: Yup. Exactly same setup worked for me, as well.

Just pushed an update to rn-0.12-hmr/Examples/BabelES6: it now uses the changes from https://github.com/webpack/webpack/pull/1521 instead of the hack.

Hi! Since i was very happy for the working HMR in my simulator, i've decided to try on my iPhone 6. Unfortunately it doesn't work and this is my console. Any ideas?

You need to change localhost to your computer's IP/hostname in AppDelegate.m

Also, webpack's publicPath should include your hostname as well

I've already done it but it doesn't work :/ if it can helps, if i go to http://localhost:8082/ i get "Cannot get /" but if i go to http://<IP_ADDRESS>:8082/ the page is not available.

Firewall settings?

On 22 Oct 2015, at 17:49, Paolo Rovella<EMAIL_ADDRESS>wrote:
I've already done it but it doesn't work :/ if it can helps, if i go to http://localhost:8082/ i get "Cannot get /" but if i go to http://<IP_ADDRESS>:8082/ the page is not available.
—
Reply to this email directly or view it on GitHub.

Firewall deactivated :) could it be a port forwarding router problem? 8082 closed port i mean

It could be that rnws binds only to localhost: app.listen('localhost', port)
Marius Petcu,
Software Engineer at LearnFwd
IT & Media Manager at ARGO Debate
On Thu, Oct 22, 2015 at 6:52 PM, Paolo Rovella<EMAIL_ADDRESS>wrote:

Firewall deactivated :) could it be a port forwarding router problem? 8082 closed port i mean
Reply to this email directly or view it on GitHub:
https://github.com/mjohnston/react-native-webpack-server/issues/103#issuecomment-150269126

@dapetcu21 i've changed in package.json -> HOT=1 ./node_modules/.bin/react-native-webpack-server start --hot --hostname <IP_ADDRESS> and now http://<IP_ADDRESS>:8082/index.ios.js gives me the bundle but when i update a component the HMR is not starting

@dapetcu21 i've forgotten to set 'webpack-hot-middleware/client?path=**http://<IP_ADDRESS>:8082**/__webpack_hmr&overlay=false' now everything is working :) thank you so much

@elliottsj You're missing webpack-hot-middleware/client in the package.json of https://github.com/mjohnston/react-native-webpack-server/blob/rn-0.12-hmr/Examples/BabelES6/package.json

@elliottsj Hot reloading still doesn't seem to work - and now neither does LiveReload

@elliottsj Here's some output if it helps... this occurs after I save a file (the debugger/websocket stuff is connected already, it looks like the hotpack files might not be reloading properly or triggering intent refresh or something, not sure...?)
webpack built 872a39c5ec3c5bdae6a4 in 441ms
Hash: 872a39c5ec3c5bdae6a4
Version: webpack 1.12.2
Time: 441ms
                                   Asset      Size  Chunks             Chunk Names
                            index.ios.js    117 kB       0  [emitted]  index.ios
                        index.android.js    104 kB       1  [emitted]  index.android
    0.dfd585fc6ce8bf86eb49.hot-update.js   3.79 kB       0  [emitted]  index.ios
    dfd585fc6ce8bf86eb49.hot-update.json  36 bytes          [emitted]
                        index.ios.js.map    160 kB       0  [emitted]  index.ios
0.dfd585fc6ce8bf86eb49.hot-update.js.map    4.2 kB       0  [emitted]  index.ios
                    index.android.js.map    140 kB       1  [emitted]  index.android
chunk    {0} index.ios.js, 0.dfd585fc6ce8bf86eb49.hot-update.js, index.ios.js.map, 0.dfd585fc6ce8bf86eb49.hot-update.js.map (index.ios) 86.1 kB [rendered]
chunk    {1} index.android.js, index.android.js.map (index.android) 73.9 kB [rendered]
webpack: bundle is now VALID.
[3:29:27 PM] <START> find dependencies
[3:29:27 PM] <END>   find dependencies (96ms)
[3:29:27 PM] <START> transform
transforming [========================================] 100% 314/314
[3:29:27 PM] <END>   transform (114ms)

Invalid HMR message: {"action":"built","time":441,"hash":"872a39c5ec3c5bdae6a4","warnings":[],"errors":[],"modules":{"0":"multi index.android","1":"./~/react-native/Libraries/react-native/react-native.js","2":"./~/react-transform-hmr/~/react-proxy/~/lodash/lang/isObject.js","3":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/isArrayLike.js","4":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/isObjectLike.js","5":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/getNative.js","6":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/isLength.js","7":"(webpack)/buildin/module.js","8":"./~/babel-runtime/helpers/interop-require-default.js","9":"./~/react-transform-hmr/lib/index.js","10":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/isIndex.js","11":"./~/react-transform-hmr/~/react-proxy/~/lodash/lang/isArguments.js","12":"./~/react-transform-hmr/~/react-proxy/~/lodash/lang/isArray.js","13":"./~/babel-runtime/~/core-js/library/modules/$.core.js","14":"./~/react-transform-hmr/~/react-proxy/~/lodash/function/restParam.js","15":"./~/react-transform-hmr/~/react-proxy/~/lodash/object/keys.js","16":"external \"NativeModules\"","17":"./~/react-native-button/Button.js","18":"./~/react-native-button/coalesceNonElementChildren.js","19":"./~/react-native-form/index.js","20":"./~/babel-runtime/core-js/object/assign.js","21":"./~/babel-runtime/helpers/extends.js","22":"./~/babel-runtime/~/core-js/library/fn/object/assign.js","23":"./~/babel-runtime/~/core-js/library/modules/$.assign.js","24":"./~/babel-runtime/~/core-js/library/modules/$.cof.js","25":"./~/babel-runtime/~/core-js/library/modules/$.def.js","26":"./~/babel-runtime/~/core-js/library/modules/$.defined.js","27":"./~/babel-runtime/~/core-js/library/modules/$.fails.js","28":"./~/babel-runtime/~/core-js/library/modules/$.global.js","29":"./~/babel-runtime/~/core-js/library/modules/$.iobject.js","30":"./~/babel-runtime/~/core-js/library/modules/$.js","31":"./~/babel-runtime/~/core-js/library/modules/$.to-object.js","32":"./~/babel-runtime/~/core-js/library/modules/es6.object.assign.js","33":"./~/react-transform-hmr/~/global/window.js","34":"./~/react-transform-hmr/~/react-proxy/modules/bindAutoBindMethods.js","35":"./~/react-transform-hmr/~/react-proxy/modules/createClassProxy.js","36":"./~/react-transform-hmr/~/react-proxy/modules/createPrototypeProxy.js","37":"./~/react-transform-hmr/~/react-proxy/modules/deleteUnknownAutoBindMethods.js","38":"./~/react-transform-hmr/~/react-proxy/modules/index.js","39":"./~/react-transform-hmr/~/react-proxy/~/lodash/array/difference.js","40":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/SetCache.js","41":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/arrayPush.js","42":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/assignWith.js","43":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/baseAssign.js","44":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/baseCopy.js","45":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/baseDifference.js","46":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/baseFlatten.js","47":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/baseIndexOf.js","48":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/baseProperty.js","49":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/bindCallback.js","50":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/cacheIndexOf.js","51":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/cachePush.js","52":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/createAssigner.js","53":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/createCache.js","54":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/getLength.js","55":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/indexOfNaN.js","56":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/isIterateeCall.js","57":"./~/react-transform-hmr/~/react-proxy/~/lodash/internal/shimKeys.js","58":"./~/react-transform-hmr/~/react-proxy/~/lodash/lang/isFunction.js","59":"./~/react-transform-hmr/~/react-proxy/~/lodash/lang/isNative.js","60":"./~/react-transform-hmr/~/react-proxy/~/lodash/object/assign.js","61":"./~/react-transform-hmr/~/react-proxy/~/lodash/object/keysIn.js","62":"./~/react-transform-hmr/~/react-proxy/~/lodash/utility/identity.js","63":"./~/react-transform-hmr/~/react-proxy/~/react-deep-force-update/lib/index.js","64":"external \"ActionSheetIOS\"","65":"external \"ActivityIndicatorIOS\"","66":"external \"AdSupportIOS\"","67":"external \"AlertIOS\"","68":"external \"Animated\"","69":"external \"AppRegistry\"","70":"external \"AppStateIOS\"","71":"external \"AsyncStorage\"","72":"external \"BackAndroid\"","73":"external \"CameraRoll\"","74":"external \"DatePickerIOS\"","75":"external \"Dimensions\"","76":"external \"DrawerLayoutAndroid\"","77":"external \"Easing\"","78":"external \"EdgeInsetsPropType\"","79":"external \"Image\"","80":"external \"ImagePickerIOS\"","81":"external \"InteractionManager\"","82":"external \"LayoutAnimation\"","83":"external \"LinkedStateMixin\"","84":"external \"LinkingIOS\"","85":"external \"ListView\"","86":"external \"MapView\"","87":"external \"Modal\"","88":"external \"Navigator\"","89":"external \"NavigatorIOS\"","90":"external \"NetInfo\"","91":"external \"PanResponder\"","92":"external \"PickerIOS\"","93":"external \"PixelRatio\"","94":"external \"Platform\"","95":"external \"PointPropType\"","96":"external \"ProgressBarAndroid\"","97":"external \"ProgressViewIOS\"","98":"external \"PushNotificationIOS\"","99":"external \"RCTDeviceEventEmitter\"","100":"external \"RCTNativeAppEventEmitter\"","101":"external \"React\"","102":"external \"ReactComponentWithPureRenderMixin\"","103":"external \"ReactDefaultPerf\"","104":"external \"ReactFragment\"","105":"external \"ReactTestUtils\"","106":"external \"ReactUpdates\"","107":"external \"ScrollView\"","108":"external \"SegmentedControlIOS\"","109":"external \"Settings\"","110":"external \"SliderIOS\"","111":"external \"StatusBarIOS\"","112":"external \"StyleSheet\"","113":"external \"SwitchAndroid\"","114":"external \"SwitchIOS\"","115":"external \"TabBarIOS\"","116":"external \"Text\"","117":"external \"TextInput\"","118":"external \"ToastAndroid\"","119":"external \"ToolbarAndroid\"","120":"external \"TouchableHighlight\"","121":"external \"TouchableNativeFeedback\"","122":"external \"TouchableOpacity\"","123":"external \"TouchableWithoutFeedback\"","124":"external \"VibrationIOS\"","125":"external \"View\"","126":"external \"WebView\"","127":"external \"cloneWithProps\"","128":"external \"processColor\"","129":"external \"requireNativeComponent\"","130":"external \"update\"","131":"./src/main.android.js","132":"./src/main.ios.js","133":"./~/react-native-webpack-server/hot/entry.js","134":"(webpack)-hot-middleware/client-overlay.js","135":"(webpack)-hot-middleware/client.js?path=http://localhost:8082/__webpack_hmr&overlay=false","136":"(webpack)-hot-middleware/~/querystring/decode.js","137":"(webpack)-hot-middleware/~/querystring/encode.js","138":"(webpack)-hot-middleware/~/querystring/index.js","139":"(webpack)-hot-middleware/~/strip-ansi/index.js","140":"(webpack)-hot-middleware/~/strip-ansi/~/ansi-regex/index.js","141":"(webpack)-hot-middleware/process-update.js"}}
ReferenceError: hotDownloadManifest is not defined

Here's my webpack.config.js:

var path = require('path');
var webpack = require('webpack');

var config = {
  context: __dirname,
  debug: true,
  devtool: 'source-map',
  watch: true,
  entry: {
    'index.ios': ['./src/main.ios.js']
    'index.android': ['./src/main.android.js'],
  },
  output: {
    path: path.resolve(__dirname, 'build'),
    filename: '[name].js',
  },
  module: {
    loaders: [
      {
        test: /\.(js|jsx|es6)$/,
        loader: 'babel-loader',
        include: [
          path.resolve(__dirname, 'src'),
          path.resolve(__dirname, 'node_modules/react-native-button'),
          path.resolve(__dirname, 'node_modules/react-native-form')
        ],
        query: {
          optional: [
            'runtime'
          ],
          stage: 0,
          plugins: []
        }
      }
    ]
  },
  resolve: { extensions: ['', '.js', '.jsx', '.es6'] },
  plugins: []
};

// Hot loader
if (process.env.HOT) {
  config.devtool = 'source-map';
  config.entry['index.ios'].unshift(
    'react-native-webpack-server/hot/entry',
    'webpack-hot-middleware/client?path=http://localhost:8082/__webpack_hmr&overlay=false'
  );
  config.output.publicPath = 'http://localhost:8082/';
  config.plugins.unshift(
    new webpack.optimize.OccurrenceOrderPlugin(),
    new webpack.HotModuleReplacementPlugin(),
    new webpack.NoErrorsPlugin()
  );
  config.module.loaders[0].query.plugins.push('react-transform');
  config.module.loaders[0].query.extra = {
    'react-transform': {
      transforms: [
        {
          transform: 'react-transform-hmr',
          imports: ['react-native'],
          locals: ['module']
        }
      ]
    }
  };
}

// Production config
if (process.env.NODE_ENV === 'production') {
  config.plugins.push(new webpack.optimize.OccurrenceOrderPlugin());
  config.plugins.push(new webpack.optimize.UglifyJsPlugin());
}

module.exports = config;

Here's my package.json:
{
  "name": "App",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "bundle": "react-native-webpack-server bundle",
    "start": "react-native-webpack-server start",
    "hot": "HOT=1 react-native-webpack-server start --hot",
    "start-android-webpack-server": "HOT=1 react-native-webpack-server start --hot -e index.android -P 9090 -p 9091 -w 9092",
    "install-app-to-android-device": "cd android && ./gradlew installDebug",
    "setup-reverse-tcp-for-android-device": "adb reverse tcp:8081 tcp:9090",
    "launch-android-app-on-device": "cd android && adb shell am start -n com.\"$npm_package_name\"/.MainActivity",
    "android": "npm run-script setup-reverse-tcp-for-android-device && npm run-script install-app-to-android-device && npm run-script launch-android-app-on-device && echo \"Please Reload JS on the app from the menu after the webpack server starts below\" && npm run-script start-android-webpack-server"
  },
  "dependencies": {
    "react-native": "~0.12.0",
    "react-native-button": "^1.2.1",
    "react-native-form": "^0.1.6"
  },
  "devDependencies": {
    "babel-core": "^5.8.25",
    "babel-loader": "^5.3.2",
    "babel-plugin-react-transform": "^1.1.1",
    "babel-runtime": "^5.8.25",
    "eslint-plugin-react": "^3.6.1",
    "react-native-webpack-server": "mjohnston/react-native-webpack-server#rn-0.12-hmr",
    "react-transform-hmr": "^1.0.1",
    "webpack": "elliottsj/webpack#web-worker-hmr"
  }
}

@niftylettuce You also need target: 'webworker' in your webpack config, e.g. https://github.com/mjohnston/react-native-webpack-server/blob/rn-0.12-hmr/Examples/BabelES6/webpack.config.js#L7
I'm happy to help on Discord#react-native-webpack if you need more help :smile:

That didn't work, I got hotModule not defined error above if I put
webworker:true in config
On Oct 26, 2015 4:53 PM, "Spencer Elliott"<EMAIL_ADDRESS>wrote:

@niftylettuce https://github.com/niftylettuce You also need target:
'webworker' in your webpack config, e.g.
https://github.com/mjohnston/react-native-webpack-server/blob/rn-0.12-hmr/Examples/BabelES6/webpack.config.js#L7
I'm happy to help on Discord#react-native-webpack
http://www.reactiflux.com/ if you need more help [image: :smile:]
—
Reply to this email directly or view it on GitHub
https://github.com/mjohnston/react-native-webpack-server/issues/103#issuecomment-151281886
.

Got it working! :balloon:

Then share it! Step by step :-)
Sent from my iPhone

On 27 Oct 2015, at 01:09, niftylettuce<EMAIL_ADDRESS>wrote:
Got it working!
—
Reply to this email directly or view it on GitHub.

@niftylettuce Did you make it worked? I have the same issue with you:
Invalid HMR message: ....
I also add target: 'webworker' to config file but nothing happen.
Please share your tips.

@niftylettuce I also have the same issue as you. How did you make it work? Hope you can help us, thanks!

I don't recommend to use hotloading until it has complete Android and iOS
support.   The headache and time ensued for me getting it to work, but now
having to turn it off is not worth having it.   Just CMD+R and reload.
You don't need experimental hot reloading.
On Nov 4, 2015 12:55 PM, "RyGuyM"<EMAIL_ADDRESS>wrote:

@niftylettuce https://github.com/niftylettuce I also have the same
issue as you. How did you make it work? Hope you can help us, thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/mjohnston/react-native-webpack-server/issues/103#issuecomment-153808955
.

Thanks for publishing 0.9.0! Given recent changes does the title of this still make sense? I believe this may be the root cause of https://github.com/jhabdas/react-native-webpack-starter-kit/issues/73

Not sure. I'm not really interested in hot module replacement. If somebody wants to fix it for RN 0.13+, I'd be happy to entertain PRs.


:tada:  add reaction roles

This pull request includes:
Reaction roles ;=)

I will have a proper look into this very good pull request this weekend (just working on a few bugs before anything new)

👍 let me know when i need to merge the bug fixes

If you need to contact me on discord tovade#6617

im also in listcord (thats how i found this awesome bot)


support for PKCS8 encrypted 4096 bit key

As raised in the mbed TLS support forum by Florian, 4096 bit encrypted key is not supported.
This is because the key buffer size for this format is 2376 bytes, and the internal buffer used for the decryption is 2048 bytes long.
Error returned by pk_parse_key_pkcs8_encrypted_der is MBEDTLS_ERR_PK_BAD_INPUT_DATA because:
    if( len > sizeof( buf ) )
        return( MBEDTLS_ERR_PK_BAD_INPUT_DATA );

ARM Internal Ref: IOTSSL-1566

similar to #878

Resolved by #1062 which is now merged.


build.sh: add xelatex unicode-aware pdf build if present.

! Package inputenc Error: Unicode char \u8:⨉ not set up for use with LaTeX.

this ^ may be a mac problem:
\usepackage[applemac]{inputenc}

Can you retry & make sure the build is 100% clean?
The changes I made in this PR were directly related to the 'Unicode char not setup for use' issue -
I had that error on the previous configuration, and flipped to XeLaTeX specifically because it is allegedly more unicode aware (and fixed the build issue for me).


Allow allocation of 100% of memory and 100% cores on subutai

Allow allocation of 100% of memory and 100% cores on subutai
Noticed that I only have 4GB available to subutai on hub.
I have 32, would like to allocate all of it to subutai.
Installed through vagrant in virtualbox.

Also I have a feature request!
Any way I can view the hub status for various things?
Like docker conversions.
Github/apt pulls and conversions etc.
Trying to convert my docker container here: gr1dd/nemochain:latest
Pulls fine on my debian system, curious to see what will happen. Seeing a live conversion log would be amazing, but a status page could benefit everyone probably 📦

Moving my dockerfile to this now:
FROM haskell:latest

EXPOSE 8000/udp

EXPOSE 8000

EXPOSE 3000

EXPOSE 3001

EXPOSE 3002

EXPOSE 3003

EXPOSE 3004

EXPOSE 3005

RUN apt-get update

RUN apt-get --assume-yes install libpq-dev build-essential

RUN mkdir /NemoChain

WORKDIR /NemoChain

ADD . /NemoChain

RUN stack setup

RUN stack build

CMD ["stack", "exec", "nemochain"]

Is there something I'm missing by chance :paintbrush:
Makes me wish there was a cancel conversion button/re-run conversion on the docker image upload on kurjun.

@Gr1dd Hi!
For Hub related issues we have this repo https://github.com/subutai-io/hub/issues
You can file issues there

We use predefined sizes for containers: TINY, SMALL, MEDIUM, LARGE, HUGE.
The Subutai containers operate within the resource constraints imposed by this range.
The limits apply to % of CPU, amount of RAM and HDD used. CPU cores are not limited.


Fix test skip if python binaries missing

On Debian based system, the Python binary includes the version and is named python3. The test cases that expect that a binary named python exists will fail.
Use the binary name of the running Python process for the test cases to ensure that this binary is present.

Thank You!


Exception in thread "main" java.lang.UnsupportedClassVersionError: maestro_android/MaestroDriverGrpc has been compiled by a more recent version of the Java Runtime.

When I try to ./maestro test android_flow.yaml:
Exception in thread "main" java.lang.UnsupportedClassVersionError: maestro_android/MaestroDriverGrpc has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
Host:
Windows 11
AMD Ryzen 3400g
Android Studio
Pixel 4 - API 30
Android 11.0 - Google Play - x86

Hey @ederhmaia - We now support Java 1.8 runtime so you should no longer see this error after upgrading to the latest Maestro version. Please reopen if you continue to see issues!


Please adopt semver & fixed releases

It'd be awesome if developers knew which "version" of dlite they had installed on their machines. Since there are no Releases and only a master branch that we're expected to clone, it could lead to inconsistent results for a team of developers.
Using a tool like git-flow, along with semantic versioning should be an easy way to resolve this.

yeah this is something i've been meaning to do anyway, the next release will end up being dubbed 1.0.0 and i'll use semantic versioning from there forward

as of now, semantic versioning will be respected. in addition, i've added a dlite version command to display the currently installed version of dlite

Awesome. Thanks!


Source code?

Where is the source code for the apps located? Sorry - I couldn't see the source anywhere?!

Duplicate of #23


Functions to verify hashtags

It is sometimes desirable(*) to check the plausibility of a signature over a piece of data based on its HashTag, in situations where we are unable to fully verify the signature (e.g. due to a third-party signing key being unavailable). This implements the necessary functions by mirroring the corresponding signature verification functions.
It is difficult to implement these functions at the application level, due to lack of access to private methods such as userIdSignatureHash(), serializeWithoutHeaders() etc.
(It crossed my mind that it might be worth factorising out the common code from VerifySignature and VerifyHashTag, but that would require care handling the mutated hash and the version exception)
(* https://github.com/hockeypuck/hockeypuck/issues/283)

These have been tested in hockeypuck for the last few months without known issues.

Also note that this PR did not touch the v2 API (because it didn't exist when I wrote it!). It may therefore need to be duplicated.

Ah right, my bad. Thanks!


Parsing updates

Rewrite of all game data parsing for my sanity when making updates

I don't believe the rune lock list is a feature that needs to be implemented in swarfarm, since there is no real risk in deleting a rune on the website. I have some plans for rune builds but it'll take some time to fully flesh out the feature.


⚠ Portainer-HEL has degraded performance

In f131af9, Portainer-HEL ($URL_PORTAINER_FI) experienced degraded performance:

HTTP code: 200
Response time: 6452 ms

Resolved: Portainer-HEL performance has improved in 45eb6fb after 9 minutes.


Display the specific error locations of all current errors

This branch fixes #27 .
The code differentiates between error summaries that include the count, and specific errors that include the line and column numbers.  I realize that it's a significant refactoring, but it's the easiest way I could see to split apart those two concepts.
The unit tests for the util file really save time.  To test the client, I used https://github.com/wdoug/tsc-baseline-demo to link to the build.  Thanks for setting that up @wdoug .
Does the approach in this branch make sense to you?

I raised a question, but I would also personally be happy with having this merged as-is for now and then possibly be refactored later.

Thanks for the helpful review @wdoug !  I think I'm at a stopping place.  How does it look now?

Thank you. Merged.

Published as 1.5.0

Thank you @TimMikeladze !


On-call user doesn't show during 'blank' hours on level 1 of the escalation policy

Describe the bug
I have an escalation policy with no users assigned to it during off hours, on escalation level 1 - not sure if this is the right way to do it. But I do have users on level 2 but they are not showing up. Instead I get his message on the plugin.

To Reproduce
Steps to reproduce the behavior:

Go to an escalation policy in PagerDuty
Define a schedule on level 1 and make sure to leave a blank spot.
During that blank timeslot - open Backstage - navigate to a service that uses that escalation policy
See the same information I posted below.

Expected behavior
I was expecting to see the on-call user, independent of the escalation level. If no one is on call on level 1, then level 2 is the one to be on-call.

this is fixed on #60.


bug: WallectConnect signature wrong address

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.7.5
Current Behavior
When you are connecting via WallectConnect on website using your mobile wallet, connection done wright. But if you want to make some signature using useSignMessagehook you get sign message, approved it, signature has been made but with wrong address. I tested on local computer, on my website and also one your example: https://wagmi.sh/examples/sign-message

and when you try to check signature on etherscan with your wallet address signature isn't ok because it has been signed with some address: 0xd5289Bc91E2822A23A8A9BB38E26ffc1EFEa82AF , I don't know who is owner of this address.
Expected Behavior
That recovered address is same that wallet address when using sign message.
Steps To Reproduce
Go to link: https://wagmi.sh/examples/sign-message
Connect your mobile wallet via WalletConnect
Enter some sign message
Click "Sign Message"
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
Sorry if I'm wrong :(

I wasn't able to reproduce using Rainbow or MetaMask via WalletConnect. Happy to look into further if you provide a minimal reproducible example, wallet you used, etc.
https://user-images.githubusercontent.com/6759464/198392051-c774a474-d35f-4d4c-ad37-42ba071c684d.mp4

Thx @tmm for fast response, I was using Argent wallet, maybe someone will have same issue I will leave this comment.

Running into a similar issue with Argent/WalletConnect. Our payload is a string akin to We use this cryptographic signature to verify your ownership of this wallet - UID:<PHONE_NUMBER>940.
Recovered signer address does not match the connected account.


Propagate unsupported error when server returns 200

Summary
It looks like Artifactory has some issues related to range requests:

https://github.com/pypa/pip/issues/8723
https://jfrog.atlassian.net/browse/RTFACT-23108

Specifically, the server returns Accept-Ranges: bytes:
❯ curl -I https://killjoyuvbug.jfrog.io/artifactory/api/pypi/pypi/packages/packages/70/8e/0e2d847013cb52cd35b38c009bb167a1a26b2ce6cd6965bf26b47bc0bf44/requests-2.31.0-py3-none-any.whl
HTTP/1.1 200
Date: Sat, 17 Feb 2024 04:25:58 GMT
Content-Type: application/octet-stream
Content-Length: 62574
Connection: keep-alive
X-JFrog-Version: Artifactory/7.78.3 77803900
X-Artifactory-Id: 1271c5d73fe90d4835ba98b07ae9fae097684c20
X-Artifactory-Node-Id: a0sl0mjfkim76-artifactory-primary-0
Last-Modified: Mon, 22 May 2023 15:12:44 GMT
ETag: 60b928b15e05d04a33b880a0232e44258c777740
X-Checksum-Sha1: 60b928b15e05d04a33b880a0232e44258c777740
X-Checksum-Sha256: 58cd2187c01e70e6e26505bca751777aa9f2ee0b7f4300988b709f44e013003f
X-Checksum-Md5: 0cb4b772a1a652cf3d170a6c42a69098
Accept-Ranges: bytes
X-Artifactory-Filename: requests-2.31.0-py3-none-any.whl
Content-Disposition: attachment; filename="requests-2.31.0-py3-none-any.whl"
X-Request-ID: b93813a7cd7abb1091fdd293875864bb

But if you then make a range request, it returns a 200, and it appears to stream the entire file back to you:
> GET /artifactory/api/pypi/pypi/packages/packages/70/8e/0e2d847013cb52cd35b38c009bb167a1a26b2ce6cd6965bf26b47bc0bf44/requests-2.31.0-py3-none-any.whl HTTP/1.1
> Host: killjoyuvbug.jfrog.io
> User-Agent: curl/8.4.0
> Accept: */*
> Range:bytes=100-200

< HTTP/1.1 200
< Date: Sat, 17 Feb 2024 04:26:28 GMT
< Content-Type: application/octet-stream
< Content-Length: 62574
< Connection: keep-alive
< X-JFrog-Version: Artifactory/7.78.3 77803900
< X-Artifactory-Id: 1271c5d73fe90d4835ba98b07ae9fae097684c20
< X-Artifactory-Node-Id: a0sl0mjfkim76-artifactory-primary-0
< Last-Modified: Mon, 22 May 2023 15:12:44 GMT
< ETag: 60b928b15e05d04a33b880a0232e44258c777740
< X-Checksum-Sha1: 60b928b15e05d04a33b880a0232e44258c777740
< X-Checksum-Sha256: 58cd2187c01e70e6e26505bca751777aa9f2ee0b7f4300988b709f44e013003f
< X-Checksum-Md5: 0cb4b772a1a652cf3d170a6c42a69098
< Accept-Ranges: bytes
< X-Artifactory-Filename: requests-2.31.0-py3-none-any.whl
< Content-Disposition: attachment; filename="requests-2.31.0-py3-none-any.whl"
< X-Request-ID: 4233f1f418add9e1c86ebec61a7db773

This PR validates that the responses returned once we start streaming are in fact 206s.

Thanks @charliermarsh this looks great!


Publish docs site on github pages

Hi, I found your library to be very useful but I had to pull down the source and generate and host the docs manually.
I think it could be more usable to publish the generated docs as a static site on github pages :)

Thanks for the feedback! I'll definitely be setting that up, maybe some time next month. In the meantime I'll keep this open as a reminder.

Luke has this workflow setup which you should be able to steal it straight up 😃  https://github.com/lukewilliamboswell/roc-json/blob/main/.github/workflows/generate-docs.yaml


SwiftDriver: remove unused references to Version

TSCUtility.Version is not used in these source files anymore.  Remove the reference to make it easier to identify what valid ties to TSCUtility remain in the package.

@swift-ci please test


PI8 FedRAMP remediations

What we're after: We address planned POAM items and unexpected FedRAMP complications
Benefits/why:

Squads plan to have some capacity drained off by FedRAMP surprises

@brittag are we at the point where we can accept all the issues in Awaiting Acceptance?

@mogul 7/8 of those issues are POAM items in "awaiting acceptance" since we're still waiting for an update from Veris on whether they accept our false positive / operational requirement rationales for those items. It's ok with me to close them since that's also tracked in the POAM - or we could just open a new standalone issue for tracking them rather than having 7 issues for similar topics.


Cleanup

All filenames start now with lower case letter.
Renaming classes:

GSU3 -> SU3
GSU2 -> SU2
gVect3 -> Vect3
gaugeAccessor -> SU3Accessor

Tests compile and run without issues. Merging


FIX: re-reading the typequery.mf did only read the first line.

Hello Rob,
I have imporoved re-reading of the typequery.mf as it did only read the first line.

Thanks, merging.
Note that I expect to revisit this manifest in the future in that I have thoughts about the ebean.mf file having multiple entries (giving us the ability to optionally define packages for entity enhancement, transactional enhancement and query bean enhancement).
... but yes this PR looks good, merging it - thanks.


yandex-browser: <IP_ADDRESS>0-1 -> <IP_ADDRESS>0-1

Description:

yandex-browser-beta is updated to: <IP_ADDRESS>0-1

Change-Id: I4f7c99e33ee419645e7dca09b03335337421dbd0
Signed-off-by: Ionut Nechita<EMAIL_ADDRESS>Description of changes
yandex-browser: <IP_ADDRESS>0-1 -> <IP_ADDRESS>0-1
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

This commit is verified.
I have yandex browser beta installed with latest changes from master branch on my PC.

Result of nixpkgs-review pr 221047 run on x86_64-linux 1

1 package marked as broken and skipped:

yandex-browser

It appears to still be marked as broken. Is this still the case?

I don't think that's the case. Everything should be fine. Is there anything to change in the nix file?

Perhaps it is because it has a knownVulnerabilities field.

We can keep it that way for a while.

Hi @dan4ik605743,
It's possible to review and merge this PR?

src appears to be 404ed.


fix: discrepency in attrs, msgspec and pydantic for multi-part forms

Pull Request Checklist

[x] New code has 100% test coverage
[x] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[x] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR

Description

Close Issue(s)

Fixes #2278

mmm no it breaks other tests

@euri10 Are you still working on this?

well been afk a couple of days so it stalled :)
this said I'm kind of stuck in solving this, currently the PR shows only a test that fails for multi-part attrs/msgspec while pydantic is ok (test is parametrized so it is 6 tests, 3 flibraries times 2 form encoding)
the difference with url-encoded forms is that in the multi-part parsing there is already some serialization happening here:
https://github.com/litestar-org/litestar/blob/359fa32f87d5980dcbc30d567298cbbc7319cb19/litestar/_multipart.py#L158-L162
so in essence we ask here for attrs and msgspec to decode the bytes b"1" inside the mutli-part parsing.
while debugging I also noticed something I dont get, whatever the test for the multi-part case, the type_decoders are always pydantic related, I'm not sure where these are declared or instanciated though, that may be a hint.
At first I thought it was as simple as removing the try / except above and replace with fields[field_name].append(post_data.decode(content_charset)) but while this solves this new tests, it breaks others, all have in common to have multiple items
any help appreciated

to summarize, the test added in this PR is sending 1 and 1 to a form that expects a str and int respectively
the answers are in this table, I would expect all should be a 201
the 400 error is msgspec.ValidationError: Expected str, got int- at$.data.name``

attrs
 msgspec
 pydantic

url-encoded
 201
 201
 201

multipart
 400
 400
 201

on thing I found strange is that if I add a print(type_decoders) in the https://github.com/litestar-org/litestar/blob/359fa32f87d5980dcbc30d567298cbbc7319cb19/litestar/_multipart.py#L158-L162 in all cases I get
[(<function is_pydantic_model_class at 0x7f6687549b20>, <function _dec_pydantic at 0x7f66873393a0>), (<function _is_pydantic_uuid at 0x7f66873394e0>, <function _dec_pydantic_uuid at 0x7f6687339440>)]
i dont think this has an impact in this case, since we're talking about str/int issue here
the difference in both form types is due to the fact the url-encoded parser uses parse_numbers-false so when it reaches the point it wants to convert into the attrs/msgspec/pydantic model it has no issues, while in multi-part case the bytes are directly converted to int through the decode_json method, and once it reaches the same point it errors out, the reason pydantic doesn't is because of the coercion the lib operates iirc.
the thing that bothers me is the inconcistency between the 2, is that if I have a form that expects a str input, and a user enters 1, then it will validate it in url-encoded version and not in multi-part, so in multi-part case my form object needs to have str|int

@euri10 Can you drop the changes to poetry.lock? There has been an update to time-machine in version 2.13.0 that seems to cause one of the tests to hang. We'll need to address that in a separate PR.

seems like CI is back on track @provinzkraut :)
also, this was the discord conversation about it, might be interesting if someone needs to go back to this kind of issues: https://discord.com/channels/919193495116337154/1154356189669363783

@all-contributors add @euri10 for bug


Move ReferencesArray and DynamicReferencesArray from yiisoft/di

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Fixed issues
-

Are these usable for factory?

It doesn't, but it can be useful for those who build their own container.

Should tests be moved as well?


Assay key appears when selecting custom titles on feature, ridge plots

Feature plots remove the assay key from the title by default, but when choosing a custom title, the assay key appears in the text box for choosing a custom title, and on the plot itself.

This is a duplicate of #204.


Hardhat: upgrade Solidity version

Currently, we are having Solidity 0.6.12 set for Hardhat compilation options. We need to upgrade it to Solidity ^0.8

Fixed in #14


Rendering Issue on Windows 10 (x64): GLFWError: (65539)

I know windows isn't officially supported on windows, but I managed to get dm_control working last summer and am since trying to continue that work with a new install.
dm_control and MuJoCo appears to mostly work, I can run simulations and use most functions. The only issue is that trying to render with pixels = env.physics.render() results in the following error:
runfile('C:/Users/user/OneDrive/Documents/FYP/python/DM Control Rendering.py', wdir='C:/Users/user/OneDrive/Documents/FYP/python')
Traceback (most recent call last):

  File "<ipython-input-5-346c1f7f484f>", line 1, in <module>
    runfile('C:/Users/user/OneDrive/Documents/FYP/python/DM Control Rendering.py', wdir='C:/Users/user/OneDrive/Documents/FYP/python')

  File "C:\Users\user\Anaconda3\lib\site-packages\spyder_kernels\customize\spydercustomize.py", line 827, in runfile
    execfile(filename, namespace)

  File "C:\Users\user\Anaconda3\lib\site-packages\spyder_kernels\customize\spydercustomize.py", line 110, in execfile
    exec(compile(f.read(), filename, 'exec'), namespace)

  File "C:/Users/user/OneDrive/Documents/FYP/python/DM Control Rendering.py", line 17, in <module>
    pixels = env.physics.render()

  File "C:\Users\user\Anaconda3\lib\site-packages\dm_control\mujoco\engine.py", line 183, in render
    physics=self, height=height, width=width, camera_id=camera_id)

  File "C:\Users\user\Anaconda3\lib\site-packages\dm_control\mujoco\engine.py", line 602, in __init__
    if self._physics.contexts.mujoco is not None:

  File "C:\Users\user\Anaconda3\lib\site-packages\dm_control\mujoco\engine.py", line 459, in contexts
    self._make_rendering_contexts()

  File "C:\Users\user\Anaconda3\lib\site-packages\dm_control\mujoco\engine.py", line 443, in _make_rendering_contexts
    max_width=max_width, max_height=max_height)

  File "C:\Users\user\Anaconda3\lib\site-packages\dm_control\_render\glfw_renderer.py", line 49, in __init__
    executor.PassthroughRenderExecutor)

  File "C:\Users\user\Anaconda3\lib\site-packages\dm_control\_render\base.py", line 68, in __init__
    ctx.call(self._platform_init, max_width, max_height)

  File "C:\Users\user\Anaconda3\lib\site-packages\dm_control\_render\executor\render_executor.py", line 142, in call
    return func(*args, **kwargs)

  File "C:\Users\user\Anaconda3\lib\site-packages\dm_control\_render\glfw_renderer.py", line 59, in _platform_init
    glfw.window_hint(glfw.DOUBLEBUFFER, 0)

  File "C:\Users\user\Anaconda3\lib\site-packages\glfw\__init__.py", line 1110, in window_hint
    _glfw.glfwWindowHint(hint, value)

  File "C:\Users\user\Anaconda3\lib\site-packages\glfw\__init__.py", line 609, in errcheck
    _reraise(exc[1], exc[2])

  File "C:\Users\user\Anaconda3\lib\site-packages\glfw\__init__.py", line 45, in _reraise
    raise exception.with_traceback(traceback)

  File "C:\Users\user\Anaconda3\lib\site-packages\glfw\__init__.py", line 588, in callback_wrapper
    return func(*args, **kwargs)

  File "C:\Users\user\Anaconda3\lib\site-packages\glfw\__init__.py", line 800, in _raise_glfw_errors_as_exceptions
    raise GLFWError(message)

GLFWError: (65539) b'Invalid argument for enum parameter'

While reading through other issues here on github, I have confirmed that import glfw and assert glfw.init() both work.
Any ideas? Happy to give more info. Many thanks for reading and helping.

GLFW is complaining that glfw.DOUBLEBUFFER is an invalid enum parameter for glfw.window_hint. My guess its that it's not supported for Windows - according to the GLFW docs it seems to be X11-specific. Perhaps try commenting out this line?

Hello, thank you for the response. I tried that and I got another error somewhere else instead (but still when I tried to render). I managed to fix the problem by taking a fresh mujoco200 win64 download from https://www.roboti.us/index.html. I then took the glfw3.dll from the unzipped download and replaced the glfw3.dll at C:\Users<user>\Anaconda3\Lib\site-packages\glfw with the windows64 specific .dll. This appeared to fix all problems and I got the render to work. I'm not exactly sure what was wrong with the old library, but I kept a copy of the old .dll and the working .dll for archival purposes.


I am always getting lost

This document has interwoven two different approaches and it is very hard to follow. My suggestion is to have a document that uses the older approach of using Client Id & Secret with KeyVault and a different document using MSI. Code snippets have no context after you get halfway through this existing document.

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

ID: 2cc0b77a-df21-7007-5cec-4399d98c6dc6
Version Independent ID: efe5ae5e-ff64-f1c7-6920-4512fc8f36d1
Content: Azure Key Vault Configuration Provider in ASP.NET Core
Content Source: aspnetcore/security/key-vault-configuration.md
Product: aspnet-core
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @petpipe123 ... Thanks for commenting.
The recommendation is to adopt either deployment approach, and everything for the two approaches is covered by their respective sections ...

Use an external (non-Azure) deployment with AppID and Password (Client Secret) covered by this section :point_right: https://docs.microsoft.com/aspnet/core/security/key-vault-configuration#use-application-id-and-client-secret
Use an Azure-based deployment with MSI covered by this section :point_right: https://docs.microsoft.com/aspnet/core/security/key-vault-configuration#use-the-managed-service-identity-msi-provider

Nothing is interwoven. Except for the code shown in those two sections, everything else in the topic applies equally to both approaches.
If you set the preprocessor directive at the top of the Program.cs file to Basic, you'll see VS light up the AppID/Password/external app code in the file. When that directive is set to Managed, VS lights up the MSI-based code.
We could split, but it would create a huge amount of content duplication.
I think what I need to do is ...

At the top explain the two approaches in a few lines ... the choice of how to deploy and what consequence it has for using either the AppID/Passoword or MSI sections.
Perhaps change those section headings to make them clearer.

Hi Luke,
The “In this article” right sidebar provides great navigation, but within the documentation, it is not intrinsic in the reader’s mind to understand and pay attention to “logical page breaks”, i.e. when content spans beyond the visible window.
Would it be “cheesy” to have the document highlighted text when it corresponds to the section on the right sidebar providing visual context?  To provide you an example, using the VS IDE has great visual context of where “you” are within the codebase.
Cheers,
Peter
From: Luke Latham<EMAIL_ADDRESS>Sent: Tuesday, February 5, 2019 4:01 PM
To: aspnet/Docs<EMAIL_ADDRESS>Cc: Peter Piper<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [aspnet/Docs] I am always getting lost (#10805)
Hello @petpipe123https://github.com/petpipe123 ... Thanks for commenting.
The recommendation is to adopt either deployment approach, and everything for the two approaches is covered by their respective sections ...

Use an external (non-Azure) deployment with AppID and Password (Client Secret) covered by this section 👉 https://docs.microsoft.com/aspnet/core/security/key-vault-configuration#use-application-id-and-client-secret
Use an Azure-based deployment with MSI covered by this section 👉 https://docs.microsoft.com/aspnet/core/security/key-vault-configuration#use-the-managed-service-identity-msi-provider

Nothing is interwoven. Except for the code shown in those two sections, everything else in the topic applies equally to both approaches.
If you set the preprocessor directive at the top of the Program.cs file to Basic, you'll see VS light up the AppID/Password/external app code in the file. When that directive is set to Managed, VS lights up the MSI-based code.
We could split, but it would create a huge amount of content duplication.
I think what I need to do is ...

At the top explain the two approaches in a few lines ... the choice of how to deploy and what consequence it has for using either the AppID/Passoword or MSI sections.
Perhaps change those section headings to make them clearer.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/aspnet/Docs/issues/10805#issuecomment-460838505, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AtHcyREt2Xp5iqaLK3t39fNbDjXnxYadks5vKg0kgaJpZM4akOqv.

highlighted text when it corresponds to the section on the right sidebar providing visual context

It's beyond our ability to provide that here because we mostly manage the ASP.NET Core content, but that's great feedback for the Microsoft Docs repo, where the managers receive suggestions and feedback. Make that request at https://github.com/MicrosoftDocs/feedback/issues.


Creating progress-bar dynamically

Hi @xaksis,
I am stuck in very strange issue, I actually want to create bootstrap 'progress-bar' dynamically based on some condition.
For example: let's say I have a value of 43. now I want to make it to red progress-bar if the value is less than 50, and blue progress-bar if in between 50 - 60 else > 60 to green progress-bar.
The code for progress bar is as follow:
<template slot="table-row" slot-scope="props">

                   70% Complete

</template>

Note: aria-valuenow will be dynamic value, also style =" width:70%" too.

@kashifullahwebdeveloper you need to put the progress bar within a  for this to work. I am not sure what your question is here? Can you create a jsfiddle for me to take a look?

Thank you, so much for quick reply, let me make one for you.

you can use: https://jsfiddle.net/aks9800/80dj8vug/ as a base

I think I can't make it very clear by using jsfiddle, but using your example as base, I need to make bootstrap progressbar http://bootstrapdocs.com/v3.0.3/docs/components/#progress, based on age with the following logic:
if( age <= 50) {
// show red progress bar
} else if (age > 50 && age <=80) {
// show yellow progress bar
} else if (age >80 && age <= 100) {
// show green progress bar
}
Let me know if it still not clear to you.


Add support for default secret service and config

Description
This gives users the ability to set a default secret service and secret service configuration
Initially I wrote no tests. I want to get in sync on the high level API before diving in to testing.
Before
value1 = secret(name: "test1", service: :aws_secrets_manager, config: { region: "us-west-1" })
value2 = secret(name: "test2", service: :aws_secrets_manager, config: { region: "us-west-1" })
value3 = secret(name: "test3", service: :aws_secrets_manager, config: { region: "us-west-1" })

After
default_secret_service(:aws_secrets_manager)
default_secret_config(region: "us-west-1")

value1 = secret(name: "test1")
value2 = secret(name: "test2")
value3 = secret(name: "test3")

# OR...

with_secret_service(:aws_secrets_manager) do
  with_secret_config(region: "us-west-1") do
    value1 = secret(name: "test1")
    value2 = secret(name: "test2")
    value3 = secret(name: "test3")
  end
end

Azure use case
You have multiple managed identities used to access different azure key vaults.
default_secret_service(:azure_key_vault)

with_secret_config(client_id: "3d5e5f4e-aaac-44e7-bb0d-140dfe69d6d8") do
  db_password = secret(name: "db_password")
  my_other_secret = secret(name: "my_other_secret")
end

with_secret_config(client_id: "c3874539-1bd6-49ea-a606-4637ce871690") do
  redis_password = secret(name: "redis_password")
  fun_secret = secret(name: "fun_secret")
end

Related Issue
N/A
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.

@marcparadise what do you think?

we could support blocks to do this temporarily and then restore the old settings, that would look like this:
value1 = value2 = value3 = nil

default_secret_service :aws_secrets_manager do
  default_secret_config region: "us-west-1" do

    value1 = secret(name: "test1", version: "v1")
    value2 = secret(name: "test2", version: "v1")
    value3 = secret(name: "test3", version: "v1")
  end
end

i am...   not entirely wild about this actually.

This looks good, other than our conversation in review about moving the config into the run context so that it's not persisted globally.
The way you've written this will make it pretty easy to take on the next step too, where we allow default secret config in Chef::Config.

I'm not opposed to this one, but I would like to hold off on merging it until we can have some conversations with customers around how they plan to use this resource. We get one take at how we define the defaults and we want to make sure we get it right.

we could support blocks to do this temporarily and then restore the old settings, that would look like this:
value1 = value2 = value3 = nil

default_secret_service :aws_secrets_manager do
  default_secret_config region: "us-west-1" do

    value1 = secret(name: "test1", version: "v1")
    value2 = secret(name: "test2", version: "v1")
    value3 = secret(name: "test3", version: "v1")
  end
end

i am... not entirely wild about this actually.

I just finished adding this in a separate commit. It's not exactly elegant but I think it at least captures the concept.

Alright ya'll, this is ready to go when you are.
I would love for the Chef community to give any feedback regarding this PR.

@tas50 thoughts?  this is still in a holding pattern.

Still awaiting feedback

@marcparadise this is another good one for you to look at

As a customer I'm not sure how to get on the feedback list for this feature.  We're +1 on this PR.
In our case we've had a Chef Vault wrapper from the beginning decrypt_secret(SECRETGROUP, SECRETNAME) with the desire it would be future-compatible to migrating to AWS or Azure secrets.  With this PR we should be able to keep the decrypt_secret() function and our teams would only need to provide the default config this PR provides.
Our typical case is several to dozens of secrets used by one team.  Our desired outcome would be able to document a migration path where we tell the team to add the new initialization call (this PR) and existing decrypt_secret() calls would use the Secrets Helper to fetch the secrets.
This PR would mean we wouldn't need to manage provider defaults in our decrypt_secret() function.

I just rebased onto the main branch

Hi, can you please rebase off master again, we just corrected some problems with the Windows kitchen test setup files. Look for changes in .github/workflows/kitchen.yml that move the ansidecl.h file to it's correct location. The Ubuntu test looks like it was a timeout issue. This should run now.

Hi, can you please rebase off master again, we just corrected some problems with the Windows kitchen test setup files. Look for changes in .github/workflows/kitchen.yml that move the ansidecl.h file to it's correct location. The Ubuntu test looks like it was a timeout issue. This should run now.

@johnmccrae just rebased.

Waiting on a quick review from Marc Paradise before I merge this.

This looks good, the only thing I'm wondering is if we need with_secrets_config? I remember @lamont-granquist  raised the possibility of adding this in an earlier review, but we talked through it after and were not sure that there is a valid use case for it.

yeah i'm good not having that at least for the first cut.