Expand rpg scene

Codecov Report
Patch coverage: 10.25% and project coverage change: -0.41 :warning:

Comparison is base (035cadf) 50.90% compared to head (f6c5a39) 50.50%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #159      +/-   ##
==========================================
- Coverage   50.90%   50.50%   -0.41%
==========================================
  Files         102      102
  Lines        3145     3178      +33
  Branches      202      210       +8
==========================================
+ Hits         1601     1605       +4
- Misses       1541     1570      +29
  Partials        3        3

Impacted Files
Coverage Δ

...ls-rpg-demo/src/seagulls/rpg_demo/_di_container.py
65.57% <ø> (ø)

...lls-rpg-demo/src/seagulls/rpg_demo/_rpg_scene_2.py
24.44% <10.25%> (-2.77%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[IMPROVEMENT] Fall back to a running instance-manager if a default is not available

Is your improvement request related to a feature? Please describe (👍 if you like this request)

This is an improvement as well as a subtask of https://github.com/longhorn/longhorn/issues/6001.
Some operations in controllers, such as deleting disks and reconciling backup targets, initially fetch the default instance-manager. However, these operations are not restricted to the default instance-manager; they can use any running instance-manager. To enhance resilience, if the default instance-manager is unable to start before an upgrade of the v2 data engine or for any other reason, the controller can switch to any running instance-manager as a fallback.
Describe the solution you'd like

Describe alternatives you've considered

Additional context

This should be specific to the v2 data engine. Added the v2 label.

This should be specific to the v2 data engine. Added the v2 label.

It is more for v2 data engine, but it can also be applied to v1 data engine.

I see. Removed the v2 label, since we want to do it for both.

This seems to involve v2. @derekbit see if you would like to backport this to 1.6 and 1.5.

@innobead I think we don't need to backport to v1.6.2. It is more related to v2 upgrade.

Verified pass on longhorn master(longhorn-manager ebace7)
Using longhorn-instance-manager 846c2f build test image and perform test steps, old instance-managers running well and create backup of v2 volume success.


[stable/prometheus-operator] Version bump alertmanager and prometheus

What this PR does / why we need it:
Prometheus 2.18.1 -> 2.18.2
Alertmanager 0.20.0 -> 0.21.0
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @vsliouniaev

/test pull-charts-e2e

/retest

/test pull-charts-e2e

@vsliouniaev rebased this one on master so hopefully CI should succeed.


fix: FluentUI Demo for Blazor is not launching

🐛 Bug Report

When visiting the demo website, as indicated by Microsoft's website, the page gets stuck with only a "Loading..." text and CORS errors appear in the console.

💻 Repro or Code Sample

Click here
🤔 Expected Behavior

😯 Current Behavior

💁 Possible Solution

🔦 Context

🌍 Your Environment

OS & Device: Windows 10
Browser: Microsoft Edge

Hi,
There is something in the way on your end. You seem to be stuck somewhere on gateway.zscloud.net.
If I use your 'Click here' link above, I'm getting the site as expected:

Thank you, I'll have a deeper investigation on my end.


Unable to create new account

Overview

To reproduce
[1636418886593] ERROR (185 on 643993e0280a): Bad Request
    context: "AlgorandAdapter"
    err: {
      "type": "Error",
      "message": "Bad Request",
      "stack":
          Error: Bad Request
              at Request.callback (/app/node_modules/superagent/src/node/index.js:879:15)
              at fn (/app/node_modules/superagent/src/node/index.js:1130:18)
              at IncomingMessage.<anonymous> (/app/node_modules/superagent/src/node/parsers/json.js:19:7)
              at IncomingMessage.emit (node:events:402:35)
              at endReadableNT (node:internal/streams/readable:1343:12)
              at processTicksAndRejections (node:internal/process/task_queues:83:21)
      "status": 400,
      "response": {
        "req": {
          "method": "POST",
          "url": "http://<IP_ADDRESS>:4001/v2/transactions",
          "data": {
            "type": "Buffer",
            "data": [
              130,
              163,
              ...
	      ...
              114,
              101,
              103
            ]
          },
          "headers": {
            "x-algo-api-token": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
            "content-type": "application/x-binary"
          }
        },
        "header": {
          "access-control-allow-origin": "*",
          "content-type": "application/json; charset=UTF-8",
          "vary": "Origin",
          "date": "Tue, 09 Nov 2021 00:48:06 GMT",
          "content-length": "714",
          "connection": "close"
        },
        "status": 400,
        "text": "{\"message\":\"TransactionPool.Remember: transaction OHLE3O3U2FAO6MO3V3CEVDLGDU3BLWTHUUI6V4MY2WZOE47DILMA: overspend (account A473OSLPGV7FEMMQ3VCAOX7PZNO44Y5X5VZQC34IJFL6LBHC2AMHCKH2CE,
        data {_struct:{} Status:Offline MicroAlgos:{Raw:0} RewardsBase:0 RewardedMicroAlgos:{Raw:0} VoteID:[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
        SelectionID:[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
        VoteFirstValid:0 VoteLastValid:0 VoteKeyDilution:0 AssetParams:map[] Assets:map[] AuthAddr:AAAAAAAAA                                                       AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAY5HFKQ
        AppLocalStates:map[] AppParams:map[]
        TotalAppSchema:{_struct:{} NumUint:0 NumByteSlice:0} TotalExtraAppPages:0}, tried to spend {100                                                       0})\"}\n"
      }
    }

Expected behavior
I don't have any idea what error text means.

I have testnet wallet address created by algod sandbox - A473OSLPGV7FEMMQ3VCAOX7PZNO44Y5X5VZQC34IJFL6LBHC2AMHCKH2CE,  I already funded there, but it still looks insufficient transaction.

Resolved issue myself, my test wallet is created by local node, not sync with testnet.


Close out POA&M

@pburkholder Yeah this ticket was pretty vague. Sorry about that. I believe that this was the POA&M for meeting EL1 of M-21-31. Is there even a POA&M or can this just be closed?

This can be closed.


liftIO in Widget causes strange behavior

I'm working on a nifty way to do forms, which will also hopefully be able to handle text inputs that update every key press. However, I ran into my form elements returning some really weird results, and I narrowed it down to it being caused by widgets that have liftIO in them. For example, here's a Widget I made as I was trying to figure out the problem:
testNonStateT :: Widget HTML b
testNonStateT = forever $ do
  _ <- simStateT ("one", "two", "three")
  return ()
  where
    simStateT s = do
      r <- (do
               r <- inputEnter' $ s ^. _1
               liftIO $ print "hey there!"
               return $ s & _1 .~ r)
           <|>
           (do
               r <- inputEnter' $ s ^. _2
               liftIO $ print "hey there!"
               return $ s & _2 .~ r)
           <|>
           (do
               r <- inputEnter' $ s ^. _3
               liftIO $ print "hey there!"
               return $ s & _3 .~ r )
      liftIO $ print r
      simStateT r

inputEnter' :: String -> Widget HTML String
inputEnter' t = inputEnter [ A.value . JS.pack $ t ]

When I try this, the third one will work fine, but the second one gets the third input box's return value, and the first gets the second's. However, if I uncomment the liftIO $ print "hey there!" lines, it works fine.
I'm using Concur.VDOM.

That's really weird. I'll take a look.

From initial investigation it seems to be a bug in ghcjs-vdom. I'll look at it more later today.

Did you ever find out anything more about this? If it's just a vdom bug, would you recommend that I just use a different concur backend for now?

I looked at it a little bit and then got busy with other things. Thanks for reminding me!
I'm still not sure if this is a GHCJS bug or a ghcjs-vdom bug. But I found a quick way to solve this - add some strictness. So for example you can use {-# LANGUAGE BangPatterns #-} and then do - !r <- inputEnter' $ s ^. _1 .
Of course if you wish, you can always use Concur-React instead of Concur-VDOM. The React backend doesn't seem to suffer from the same issue, and it's also relatively better maintained (Since ghcjs-vdom is bitrotten at this point).

Ok thanks! I'll try concur-react or fall back to using strictness.


chore: release  sdk 0.5.1

:package: Staging a new release
0.5.1 (2024-02-21)
Bug Fixes

update klyshko dependencies (#101) (84afdbe)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/carbynestack/carbynestack/releases/tag/sdk-v0.5.1 :sunflower:


feat: login functionality

:tada: This PR is included in version 0.20.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[ShellyMdnsScanner]: Warning in mDNS query service:

Hey,
finally, I made it to install matterbridge and the shelly plugin on my raspberry with a debian on it (Using AHK (ATV 4k) with latest iOS 18.1). In the matterbridge log I got the following error but can't see any option how to configure this:
[ShellyMdnsScanner]: Warning in mDNS query service: The value of "offset" is out of range. It must be >= 0 and <= 374. Received 375
mDNS finds all shellys and it is working somehow fine (facing also other issues). Not knowing if I can ignore this or it needs some attention. Thanks for your support!
May I ask here if I should create additional issues for the following observations a made?

After raspberry and partially also after matter bridge restart, all connected (and sorted shelly to a room) are back to the Apple Homekit room where the Bridge is located. Also, all automations, namings in AHK are lost / forgotten.
Same when I reconfigure the shelly device (e.g. changing the name) which requires a matterbridge restart. After this, those devices were again connected to the "bridge room" and everything is gone :(
When new devices were added in AHK, I can move them there to another room. It takes a while and different retries until it works.
Some devices showing a Model, Vendor, Serial information, some not. It is not depending on the shelly device itself, 1PM gen2, 1PM gen3 or 2 PM Gen 2 and 3 are affected.
In AHK when I switch the typ e.g. from switch to light, a dialog pops up stating: "Change not possible". After klicking "OK" it anyhow changes the typ of the item.

Thank you very much for your patience and support.
Best
Tom
nodeVersion | 22.11.0
osType | Linux (6.6.51+rpt-rpi-v8)
osPlatform | linux (arm64)
Matterbridge 1.6.1
Shelly Plugin 1.0.9

Hi,
thank you the logs.
There is something I have never seen before:
[08:39:40.855] [ShellyMdnsScanner] [debug] MdnsScanner discovered shelly gen: 1 device id: shelly-schalter-GARAGENLICHT host: <IP_ADDRESS> port: 9000
[08:39:40.862] [ShellyMdnsScanner] [debug] MdnsScanner discovered shelly gen: 1 device id: shelly-GARAGENTOR host: <IP_ADDRESS> port: 9000
[08:39:40.866] [ShellyMdnsScanner] [debug] MdnsScanner discovered shelly gen: 1 device id: shelly-vorgarten-DOWNLIGHTS host: <IP_ADDRESS> port: 9000
[08:39:40.903] [ShellyMdnsScanner] [debug] MdnsScanner discovered shelly gen: 1 device id: shelly-schalter-keller-LICHT host: <IP_ADDRESS> port: 9000
What devices do you have on those IP?
What configuration do you have on the device web page that cause mdns response to port 9000?
Can you please activate all these options:

and also

then restart completely, wait a few minutes and send me the whole directory Matterbridge/matterbridge-shelly.
@tammeryousef1006 did you ever see Mdns on port 9000?
Thanks.

Quick response regarding the three devices. These are Shelly Gen1 devices with a "homekit firmware" running on it:
https://github.com/mongoose-os-apps/shelly-homekit?tab=readme-ov-file
Attached the config of the plugin. I actived the debug mode as requested and restarting. Waiting a while and uploading then the package. I never changed a port nor configured something like this. Should be all standard.

Ah ok then is the firmware on those devices that create that mdns response. Load the shelly firmware or put them in the blacklist cause they will never work.
What other issues are still opened for you now?

Still 1, 2 and 4. Devices are new after every restart and all configs / automations in AHK are lost.

They are all the same issue: as I told is related to your setup.
You run matterbridge like service?
Send me the matterbridge.service file.
You can also check on the devices page of the frontend after each restart if the endpoint numbers change. That is likely the origin of the issue.
How many devices you have ?

Sorry, maybe I read it wrong. I run it as a service as documented in your readme-service.md
I needed to adjust the path.
Archive.zip
You are right, when e.g. I change just the name (for testing purposes to provoke the issue) of the shelly on the shelly WebGUI the matterbridge confirmed that there is a change and I need to restart the bridge:
[13:54:44.642] [PluginManager]: Configured plugin matterbridge-shelly type DynamicPlatform
notice - [13:55:25.601] [Vorgartenlicht]: Shelly device Vorgartenlicht id shelly1pmg3-DCDA0CB16394 host <IP_ADDRESS> sent config changed rev: 12
notice - [13:55:25.603] [Vorgartenlicht]: If the configuration on shelly device Vorgartenlicht has changed, please restart matterbridge for the change to take effect.
After restarting the bridge (via sudo systemctl restart matterbridge) the Endpoint ID has changed.
Why this also
I have up to 16 devices, now only 4 in the whitelist.
[Unit]
Description=matterbridge
After=network-online.target
[Service]
Type=simple
Environment=PATH=/home/admin/.nvm/versions/node/v22.11.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
ExecStart=/home/admin/.nvm/versions/node/v22.11.0/bin/matterbridge -service
WorkingDirectory=/home/admin/Matterbridge
Restart=always
RestartSec=10s
StandardOutput=inherit
StandardError=inherit
TimeoutStopSec=30s
User=admin
[Install]
WantedBy=multi-user.target

Hi,
your setup is modified from the standard so you have to check it yourself to understand if there are any errors.
Furthermore using nvm in production is not recommended. Nvm is more for a dev setup.
Concerning the endpoint, every time you change a device serial number (not your case) or the name (that is your case), there will be a new uniqueid on Matter and consequently a new endpoint. In this case the controller will delete the old device and create the new one. Loosing all configuration about the first.
This explain the issues on the device where you changed the name but not the issues on the other devices if also them are recreated every time.
Check the matterbridge.json after each restart or the devices page in the frontend to understand when in your setup new endpoint are generated.
My best.

Hi,
I installed everything from scratch, without using NVM. No it runs without any issues as far as I can see.
As I am not a Linux expert (more a noob) I used NVM to install node.js as it was part of the original guide here:
https://nodejs.org/en/download/package-manager
Thank you again for spending your time in supporting me!
Maybe as a last question:
What would be the best way how to get npm and node.js on a fresh raspberry linux installation?

Hi,
I’m glad you solved and thank you for pointing out your initial issues.
I will update the readme cause you are right: now nodejs point users to nvm in the main page but is fundamentally not a good choice.
Always install node with nodesource script even because in that way when you sudo apt upgrade, node will be updated too.
My best.


⚠ Bofrost.at has degraded performance

In 5f7d62e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1808 ms

Resolved: Bofrost.at performance has improved in 0e1e5c5 after 30 minutes.


An algorithm to encrypt and decrypt the passwords..

@rahulgoyal911 thank you for contributing. Please rename the encryption.cpp file to the encryption method you are implementing & move the file to the Others/ directory.
Please resolve merge conflict.


Add a type annotation to make things more clear.

Changes proposed in this PR

Add a type annotation to make things more clear.

Why are we making these changes?
Catch some bugs or other weird invocations.

Will merge when green


feat(cast): output raw tx

Motivation
Often it is useful to get the raw encoded transaction from an RPC provider.
Solution
Implement the "raw" field for cast tx which if specified returns the RLP transaction instead of the transaction fields.
cast tx 0x44f2aaa351460c074f2cb1e5a9e28cbc7d83f33e425101d2de14331c7b7ec31e raw
0xf86d824c548502743b65088275309491da5bf3f8eb72724e6f50ec6c3d199c6355c59c87a0a73f33e9e4cc8025a0428518b1748a08bbeb2392ea055b418538944d30adfc2accbbfa8362a401d3a4a07d6093ab2580efd17c11b277de7664fce56e6953cae8e925bec3313399860470

This is the same output as:
https://etherscan.io/getRawTx?tx=0x44f2aaa351460c074f2cb1e5a9e28cbc7d83f33e425101d2de14331c7b7ec31e
Some RPC (geth) endpoints support eth_GetRawTransactionByHash but this is not always available, as is the case with Alchemy.

@bernard-wagner friendly ping, this is almost done :)

@bernard-wagner friendly ping, this is almost done :)

In the next day or two. Got the --raw portion done, just trying to figure where the best place in code to handle the enum pattern.


TOOL: Clean up PROD forms tab

The PROD environment forms tab has multiple entries of the telework form. Need them cleaned out. Iman had previously looked into this issue but did not get solved yet.
Task

[ ] Confirm users can see only one instance of the telwork form to submit new

[ ] Confirm there is only one edition of SL Review form too

Iman noted the best time would be after the upgrade - should take an hour or two,
@simensma-fresh  Any dependencies on the database?

@HasanSifat  to make Fazil a new user to see what he can see

My investigation shows that the issue that causes extra entries of a form is no longer an issue on v5 as I tested this on my local and TEST environments. Neither uploading a new version of a form on top of an existing one nor deleting a form and uploading a newer version of that form causes extra form entries.
However, there are 9 Telework entries on PROD that were side-effects of a bug in the form-process association (wizard that associates a workflow to a form) which was fixed right after discovery.
Looking into different options on how to remove those extra entries on PROD and will update this ticket.

Simen took care of this with the upgrade


[POC] Add fetch job information operator

What is this PR ?

This pr add td_job_show> operator (the name is a temporary name)
td_job_show> operator gets jobId as an argument and fetch the job information of the jobId, and stores parameter ${td.stored_jobs[jobId]} (this is a temporary specification)

Example
_export:
  td:
    database: serizawa_test

+job_show1:
  td_job_show>: 8911629

+echo_fetched_job_num_records:
  echo>: "${td.stored_jobs['8911629'].num_records}"

TODO

[x] poc implementation
[ ] fix specification
[ ] add test
[ ] add document

@serihiro ${td.stored_jobs[jobId]} is interesting. I'm curious about the latency of task pulling when stored_jobs object will be large. So, I want to ask you about the following:

How many jobs will be stored by this operator?
Then, how size of the stored_jobs object you expect?

query and result_schema fields could be large. for example, query is sometimes built and generated by tools like 5MB or 10MB.

Or, adding max_available_store_jobs_size settings to digdag and adopt LIFO to the store 🤔

@muga
I did an experiment to confirm how much memory is consumed by stored_jobs.
I measured Config object size in TdJobShowOperatorFactory before execution of storing job into StoreParams by JOL
@@ -59,6 +60,7 @@ public class TdJobShowOperatorFactory
             this.systemDefaultConfig = TDOperator.systemDefaultConfig(systemConfig);
             this.jobId = params.get("_command", String.class);
             this.storeKey = params.getOptional("store_key", String.class);
+            System.out.println("config size:" + GraphLayout.parseInstance(request.getConfig()).totalSize());
         }

I tried to run a workflow which contains 5 td_job_show>: operators.
And I found that Config object size is increasing by 7KB-10KB for each execution. So this increation is a size of a job stored by td_job_show. So when 100 jobs are stored this operator consumes up to about 1MB memory. I think it does not cause a serious problem.
But as you said, query and result_schema could be large size, so it may affect a latency to serialize Config object.
So I think query and result_schema should be excluded. On the other hand, the size of other items(num_records , types , status etc) is almost static. So the total size just scales by linearly.

config size
diff with before execution

9163264
-

9531472
368208

9538648
7176

9549328
10680

9558640
9312

@serihiro Thank you for taking the PoC. It might not easy for us to make decision about how we handle query and result_schema parameters now. About the rest of parameters, we could fix td operator and handle them like https://github.com/treasure-data/digdag/pull/860
I close this ticket. will reopen if need.


Parser Report does not reflect model accuracy

Type of Issue
Select the type of issue:

[x] Bug report (to report a bug)
[ ] Feature request (to request an additional feature)
[ ] Tracker (I am just using this as a tracker)
[ ] Refactor request
[ ] Documentation Ask

Description
Commands that should fail, are passing the NSP report. See P244425511
One explanation is that we're not including literals in tree similarity, but there are other model failures that aren't accounted for eg. missing keys, extra keys.

A major issue :
After successful download, when I run interactive script with "turn right" I get:
{'dialogue_type': 'HUMAN_GIVE_COMMAND', 'action_sequence': [{'action_type': 'DANCE', 'dance_type': {'body_turn': {'relative_yaw': {'fixed_value': '90'}}}}]}

but querying the model through the dialogue_manager of FakeAgent:
{'action_sequence': [{'dance_type': {'body_turn': {'relative_yaw': '-90'}}, 'action_type': 'DANCE'}], 'dialogue_type': 'HUMAN_GIVE_COMMAND'}

Even after successful download, the unittest still seems to be using the previous version of the model.


fix: reverse TOTP code

We were looking for a 2FA library and could not find one that is maintained neither. So, we were pretty happy that this one was announced and we wanted to try it out.
However, the TOTP codes that are generated by this library don't work / are different from the authenticator apps. Debugging the issue, it looks like the codes are reversed (123456 instead of 654321) after #4.
The tests were passing before and are still passing now. Does it make sense to add a test to check for a specific OTP code with a given secret to be sure the implementation is not broken? I am happy to add a test for this.
This is not easily possible right now because generateTOTP depends on the current time and generateHOTP is not exported. Would you rather mock the time somehow or export the HOTP methods as well? If neither is preferred, a second file that re-exports the TOTP functions could work as well.

I've confirmed this bug in the Epic Stack, so I'm merging now. But I'd still welcome a test to make sure we don't regress in the future.


json ipc

Description
why did you decide against using json as message format for events ipc socket2?
I would imagine if it was json and the code just wrote to into socket on every change of data, it would make ipc plugins much more capable and flexible
Additionally to that sending a json of the same format as we get from hyprctl to socket and expecting the state of hyprland  to change accordingly, could be an easier way to script hyprland

json is not easier to parse, it's actually considerably less efficient. The events in socket2 contain very little data anyways; json makes no sense there.


Is it possible to remove the hard-coded path of cuda compiler in cmake?

When I look into the current way to set the path of Cuda compiler as listed below:
https://github.com/TiledTensor/TiledCUDA/blob/cf22ba1df7fd23e2114d853e6de0dba6c30a9626/CMakeLists.txt#L3-L5
I think this is a hotfix to bypass the below compiling issue as solution listed in this issue https://github.com/NVlabs/instant-ngp/issues/747
 ptxas fatal : Value 'sm_30' is not defined for option 'gpu-name'

In my environment, I have a local CUDA installation, which is quite common, instead of the globally installed CUDA. This hard-coded approach initially sets the nvcc compiler to the globally installed CUDA Toolkit, but then find_package(CUDA) overwrites the CUDA compiler based on the environment variable. This approach seems a little awkward.
@KuangjuX Is it necessary to fix this compiling issue by running sudo apt remove nvidia-cuda-toolkit (which I have already done on the testing machine) and keep the CMakeFiles clean?

I agree, it seems that ad-hoc solutions specific to the local machine should not be present in the project. Alternatively, another solution is to set CMAKE_CUDA_COMPILER and CUDACXX as environment variables instead of hardcoding them.

Sure. I can fix it in the next PR.


2022-01-17 00:47:19,559 [INFO] Changing light to: HsVariation(bri=1, hue=8001, sat=254)
2022-01-17 00:47:22,267 [INFO] Measured power: 1.0
2022-01-17 00:47:22,267 [INFO] Changing light to: HsVariation(bri=1, hue=10001, sat=254)
2022-01-17 00:47:25,044 [INFO] Measured power: 1.0
2022-01-17 00:47:25,044 [INFO] Changing light to: HsVariation(bri=1, hue=12001, sat=254)
2022-01-17 00:47:27,780 [INFO] Measured power: 1.0
2022-01-17 00:47:27,781 [INFO] Changing light to: HsVariation(bri=1, hue=14001, sat=254)
2022-01-17 00:47:30,518 [INFO] Measured power: 1.0
2022-01-17 00:47:30,518 [INFO] Changing light to: HsVariation(bri=1, hue=16001, sat=254)
2022-01-17 00:47:33,269 [INFO] Measured power: 1.0
2022-01-17 00:47:33,270 [INFO] Changing light to: HsVariation(bri=1, hue=18001, sat=254)
2022-01-17 00:47:35,965 [INFO] Measured power: 1.0
2022-01-17 00:47:35,965 [INFO] Changing light to: HsVariation(bri=1, hue=20001, sat=254)
2022-01-17 00:47:38,666 [INFO] Measured power: 1.0
2022-01-17 00:47:38,666 [INFO] Changing light to: HsVariation(bri=1, hue=22001, sat=254)
2022-01-17 00:47:41,415 [INFO] Measured power: 1.0
2022-01-17 00:47:41,415 [INFO] Changing light to: HsVariation(bri=1, hue=24001, sat=254)
2022-01-17 00:47:44,125 [INFO] Measured power: 1.0
2022-01-17 00:47:44,125 [INFO] Changing light to: HsVariation(bri=1, hue=26001, sat=254)
2022-01-17 00:47:47,085 [INFO] Measured power: 1.0
2022-01-17 00:47:47,085 [INFO] Changing light to: HsVariation(bri=1, hue=28001, sat=254)
2022-01-17 00:47:50,023 [INFO] Measured power: 1.0
2022-01-17 00:47:50,023 [INFO] Changing light to: HsVariation(bri=1, hue=30001, sat=254)
2022-01-17 00:47:52,767 [INFO] Measured power: 1.0
2022-01-17 00:47:52,767 [INFO] Changing light to: HsVariation(bri=1, hue=32001, sat=254)
2022-01-17 00:47:55,487 [INFO] Measured power: 1.0
2022-01-17 00:47:55,488 [INFO] Changing light to: HsVariation(bri=1, hue=34001, sat=254)
2022-01-17 00:47:58,227 [INFO] Measured power: 1.0
2022-01-17 00:47:58,228 [INFO] Changing light to: HsVariation(bri=1, hue=36001, sat=254)
2022-01-17 00:48:00,935 [INFO] Measured power: 1.0
2022-01-17 00:48:00,935 [INFO] Changing light to: HsVariation(bri=1, hue=38001, sat=254)
2022-01-17 00:48:03,725 [INFO] Measured power: 1.0
2022-01-17 00:48:03,725 [INFO] Changing light to: HsVariation(bri=1, hue=40001, sat=254)
2022-01-17 00:48:06,462 [INFO] Measured power: 1.0
2022-01-17 00:48:06,462 [INFO] Changing light to: HsVariation(bri=1, hue=42001, sat=254)
2022-01-17 00:48:09,355 [INFO] Measured power: 1.0
2022-01-17 00:48:09,356 [INFO] Changing light to: HsVariation(bri=1, hue=44001, sat=254)
2022-01-17 00:48:12,082 [INFO] Measured power: 1.0
2022-01-17 00:48:12,082 [INFO] Changing light to: HsVariation(bri=1, hue=46001, sat=254)
2022-01-17 00:48:14,808 [INFO] Measured power: 1.0
2022-01-17 00:48:14,808 [INFO] Changing light to: HsVariation(bri=1, hue=48001, sat=254)
2022-01-17 00:48:17,558 [INFO] Measured power: 1.0
2022-01-17 00:48:17,558 [INFO] Changing light to: HsVariation(bri=1, hue=50001, sat=254)
2022-01-17 00:48:20,318 [INFO] Measured power: 1.0
2022-01-17 00:48:20,319 [INFO] Changing light to: HsVariation(bri=1, hue=52001, sat=254)
2022-01-17 00:48:23,057 [INFO] Measured power: 1.0
2022-01-17 00:48:23,061 [INFO] Changing light to: HsVariation(bri=1, hue=54001, sat=254)
2022-01-17 00:48:25,842 [INFO] Measured power: 1.0
2022-01-17 00:48:25,842 [INFO] Changing light to: HsVariation(bri=1, hue=56001, sat=254)
2022-01-17 00:48:28,590 [INFO] Measured power: 1.0
2022-01-17 00:48:28,591 [INFO] Changing light to: HsVariation(bri=1, hue=58001, sat=254)
2022-01-17 00:48:31,362 [INFO] Measured power: 2.0
2022-01-17 00:48:31,362 [INFO] Changing light to: HsVariation(bri=1, hue=60001, sat=254)
2022-01-17 00:48:34,523 [INFO] Measured power: 2.0
2022-01-17 00:48:34,524 [INFO] Changing light to: HsVariation(bri=1, hue=62001, sat=254)
2022-01-17 00:48:37,293 [INFO] Measured power: 2.0
2022-01-17 00:48:37,294 [INFO] Changing light to: HsVariation(bri=1, hue=64001, sat=254)
2022-01-17 00:48:41,128 [INFO] Measured power: 2.0
2022-01-17 00:48:41,129 [INFO] Changing light to: HsVariation(bri=1, hue=65535, sat=254)
2022-01-17 00:48:43,865 [INFO] Measured power: 1.0
2022-01-17 00:48:43,866 [INFO] Changing light to: HsVariation(bri=11, hue=1, sat=1)
2022-01-17 00:48:44,010 [INFO] Extra waiting for significant SAT change...
2022-01-17 00:48:54,020 [INFO] Extra waiting for significant HUE change...
2022-01-17 00:49:01,620 [INFO] Measured power: 1.0
2022-01-17 00:49:01,621 [INFO] Changing light to: HsVariation(bri=11, hue=2001, sat=1)
2022-01-17 00:49:05,159 [INFO] Measured power: 1.0
**_BREAK_**
2022-01-17 02:55:30,444 [INFO] Measured power: 1.0
2022-01-17 02:55:30,444 [INFO] Changing light to: HsVariation(bri=31, hue=1, sat=211)
2022-01-17 02:55:30,624 [INFO] Extra waiting for significant HUE change...

@IIAIronWolf There is definitely something not right.
Seems your Sonoff S31 is not returning correct values. I expect it to return values with decimals. i.e. 0.49, 0.52, 1.87 etc.
But it's only returning 1 and 0.
I don't have this device myself and not familiar with Tasmota.
When I look at the code I see the following URL is requested: http://x.x.x.x/?m
Could you try this yourself and see what the output is?

I think the Sonoff S31 may just not be capable of such precision, especially at low power.
Tasmota is an open source firmware for ESP devices (ESP8266 wifi chip) and was actually made by Sonoff. Their Tamsota documentation for the Sonoff S31 says that this device will sometimes report erroneuous values below 5 watts and that power calibration is needed. I did this using a 65 Watt lightbulb as they suggested and believe the results are fairly accurate at higher power now.
I will try the URL later today and get back.

This is the output for that URL:
{t}{s}Voltage{m}123 V{e}{s}Current{m}0.082 A{e}{s}Power{m} 9 W{e}{s}Apparent Power{m}10 VA{e}{s}Reactive Power{m} 4 VAr{e}{s}Power Factor{m}0.90{e}{s}Energy Today{m}0.001 kWh{e}{s}Energy Yesterday{m}0.000 kWh{e}{s}Energy Total{m}0.002 kWh{e}{t}ON

For Voltage and Wattage resolution changes, I had to go into the console and type VoltRes 2 and WattRes 2 to make the display show 2 decimal places. Now I should get more detailed results.
However, I don't understand how the hs program could go any faster regardless.
There are approx 25 steps in the saturation measurement, as well as for the brightness steps. Since we choose two each time, that gives 1,225 combinations. Then you have to step through all ~30 hue levels for each of those combinations and one round of that takes 108 seconds.
It seems like the program is off.

Glad you found the issue with the precision!
Your calculations are right and the HS mode calculations will take approximately 1.5 day to complete which is also mentioned in the Wiki. brightness and color_temp mode don't take that long.
However you can tweak a few parameters to decrease the measurement session length.
# Step sizes for HS mode loop. You can increase these to improve the duration of measure session
# Don't set higher than duplicate these values!
HS_BRI_STEPS=10
HS_HUE_STEPS=2000
HS_SAT_STEPS=10

Also see https://github.com/bramstroker/homeassistant-powercalc/issues/370.
How did you set SAMPLE_COUNT parameter, is this at 3 or at 1? When you get consistent accurate readings from your Sonoff you can just set this to 1.

Hmm. Must have missed that key detail or I never would have tried. Haha
So this doesn't warrant a code overhaul? It was only getting one sample and still expected to take longer than a day. I don't feel like anyone really needs that level of power measurement for a lightbulb. I will try again if there is ever a shorter (length of time to run) version of the code.


My tasks have been deleted

Hi
I opened up the program today and all my lists and tasks have been wiped. Any idea on where I can hunt for a backup or anything.

Look at ~/.var/app/io.github.mrvladus.List/data/errands/ the should be data.json and logs

Do you use sync?

I have never used sync no. I found the old data in ~/.var/app/io.github.mrvladus.List/data/list/data.json

copy it somewhere and launch errands from terminal:
flatpak run io.github.mrvladus.List

then copy output and send me


syntax enable in plugin

Your plugin setting syntax enable, but he should not do it if this disabled

That's how vim-plug currently works. It enables syntax only during startup. So if you syntax off after plug#end(), it will not reenable it in any case.

That's how vim-plug currently works. It enables syntax only during startup. So if you syntax off after plug#end(), it will not reenable it in any case.

Still a bad idea. My syntax off odyssey:
I wanted to turn syntax highlighting off, but adding syntax off to my .vimrc didn't do anything. It took me like an hour to find out what the problem was.
Was some other setting overriding this? Debug time. My .vimrc was over 300 lines back then. Not efficient to comb through it all. Time to blindly do divide-and-conquer debugging: comment half of my .vimrc. Does the problem happen again? Yes? Okay, the problem is in the other half of the file. Comment half of that... recursively until I found that something in the plugin configuration was causing the problem.
It made sense in retrospect. Well, better get to work. Gotta do the same thing, for plugins now. Move the ones that can't possibly be causing the problem to the top, leaving something like 8 plugins left. Comment half of those and so on, all over again, but this time having to run :PlugClean every iteration. None of the plugins were causing the problem. Was I going insane? Maybe it was one of the other plugins I put at the top? Same process again. Again, none of the plugins were causing the problem. I really did feel like I was going insane.
I don't quite remember now, but eventually either deleting the whole vim-plug section or moving it to the top fixed it.
But sure, let's run syntax on for convenience!

Changing settings means that either the Plugins section must be at the top of the .vimrc or that other settings must be in the Plugins section instead of where they belong (for example, something like an UI section for syntax on). I understand filetype plugin indent on must stay for compatibility, but please consider removing setting syntax on so no one has to go through all that again. On modern Vim it's on by default anyway, and, unlike filetype plugin indent on, it won't cause problems that are hard to fix. Everyone running vim-plug knows how to turn highlighting on.
I know this will come off as overtly negative, so to fix that a bit: otherwise, vim-plug is an awesome Vim plugin solution and I'm thankful to you for making it.

see: #1083 Stop Turning syntax on


Only break at breakpoints

Hi gwomacks,
Thanks for this package, finally debugging made it to my atom installation.
I assumed, that when setting a breakpoint and start the script in the browser, the script would run until the breakpoint. Instead, I seem to have to click continue for every change of file or whatever. Unfortunately, debugging complex applications switching between hundreds of files (which all get opened) is no charm and is taking forever.
So I was wondering whether there's a setting or something, that the debugging only stops at set breakpoints, or opens files only when actually stepping in ...
Any hints, thoughts, ideas on that?

+1
Mine seems to do the same thing. Rather than halting at the line marked for debugging it seems to want to walk through the entire stack.

+1
Same.

This is likely unrelated to php-debug and has something to do with your xdebug setup. Can you share your xdebug configuration?

Here is my, this is stock brew installation, works perfectly with PhpStorm
zend_extension="/path-to-xdebug/xdebug.so"
xdebug.remote_enable=1
xdebug.remote_port=9000
xdebug.remote_handle=dbgp
even tried settings in description, same result.

Here is my current setting for my local vagrant instance. Let me know if I can give you any additional information about my environment.
xdebug.auto_trace = 0
xdebug.collect_includes = 1
xdebug.collect_params = 1
xdebug.collect_return = 0
xdebug.collect_vars = "Off"
xdebug.default_enable = "On"
xdebug.dump.COOKIE = ""
xdebug.dump.FILES = ""
xdebug.dump.GET = ""
xdebug.dump.POST = ""
xdebug.dump.REQUEST = ""
xdebug.dump.SERVER = ""
xdebug.dump.SESSION = ""
xdebug.dump_globals = 1
xdebug.dump_once = 1
xdebug.dump_undefined = 0
xdebug.extended_info = 1
xdebug.file_link_format = ""
xdebug.idekey = "VVVDEBUG"
xdebug.manual_url = "http://www.php.net"
xdebug.max_nesting_level = 100
xdebug.overload_var_dump = 1
xdebug.profiler_append = 0
xdebug.profiler_enable = 0
xdebug.profiler_enable_trigger = 1
xdebug.profiler_output_dir = "/tmp"
xdebug.profiler_output_name = "cachegrind.out.%t-%s"
xdebug.remote_autostart = 1
xdebug.remote_enable = 1
xdebug.remote_handler = "dbgp"
xdebug.remote_host = "<IP_ADDRESS>"
xdebug.remote_log = /srv/log/xdebug-remote.log
xdebug.remote_mode = "req"
xdebug.remote_port = 9000
xdebug.show_exception_trace = 0
xdebug.show_local_vars = 0
xdebug.show_mem_delta = 0
xdebug.trace_format = 0
xdebug.trace_options = 0
xdebug.trace_output_dir = "/tmp"
xdebug.trace_output_name = "trace.%c"
xdebug.var_display_max_children = -1
xdebug.var_display_max_data = -1
xdebug.var_display_max_depth = -1

Hi,
I'm having the same behaviour with TYPO3 6.2.19 on Ubuntu 15.10. Xdebug is connecting via Network, the files are on a samba share. PathMappings are good.
 I guess i'm having a serious talk with Xdebug :D

I have set the exact settings as in your readme.md
xdebug.remote_enable=1
xdebug.remote_host=<IP_ADDRESS>
xdebug.remote_connect_back=1    # Not safe for production servers
xdebug.remote_port=9000
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_autostart=true
@bluespuke So you think it's a problem with xdebug?

@kimamil, with the way php-debug works it is almost certainly something on xdebug's side. We only send xdebug a list of breakpoint locations and types of exceptions to break on. The actual breaking is performed by xdebug.

Hi again,
When disabling Php Exception Notice and Strict Standards, Xdebug and php-debug are working as expected.
Thanks,
B!

@bluespuke this solved it for me too. Seems like the code is not running through smoothly.
again - great package !!! Many Thanks!

@bluespuke your suggestion solved the issue for me as well.
Thanks @kimamil for the great work!

Hi, all! Thanks for the answers!
I've changed my php.ini here: error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED & ~E_WARNING
Is this change right? is that you are recommending?

@bluespuke Basically I did the same thing you did: My php.ini was restored and I've unabled all PHP Exceptions at my Atom/PHP-debug settings.


Create initial AR view with logged in user experience

[x] Display all pins returned from search
[x] Refresh pins when a filter is applied
[x] Allow a 2D Map view option

Started with Commit 55fc428
Finished with Commit 93f5af1


Resize textarea of JWT

The UI of the JWT encoder/decoder would be better if instead of looking like this (⏬), it looked like the UI for the Base64 encoder/decoder.
It should be full screen like the other view.

(I'll glady work on it this weekend if needed.)

@g-ongenae Thank you for your issue! I did fix that!

@g-ongenae  Fixed on https://github.com/ObuchiYuki/DevToysMac/releases/tag/0.0.8


Cannot access country ISO name in react simple maps.

Not sure I fully explained what I want on twitter. I wanted a way to find the ISO country name while using react simple maps. I understand the 50m json has it. Can you easily expose the other properties on your geography object? Right now it only exposes the ISO numeric code (see screen shot), which I realize is better to support other locales, but no harm in exposing other properties too, with the ISO numeric ID.

If you don't think this makes sense with your API design, what are my alternatives? I would hate to maintain a json mappng object just for this.

Not sure I fully understand the problem, but from what you are saying it seems like you want to access what is in geography.properties.
What is accessible there depends a little bit on how the topojson file is prepared, i.e. whether it has certain other properties specified on each feature.
Here's a full example:
export default class Home extends Component {
  handleClick(geography) {
    // Inspect a specific country in the console by clicking on it...
    console.log(geography)
  }
  render() {
    return (
      <div>
        <ComposableMap style={{ width: "100%" }}>
          <ZoomableGroup>
            <Geographies geographyUrl="/static/world-50m.json">
              {(geographies, projection) => geographies.map(geography => {
                console.group("Geography")
                // Exposes geography with geography.id === iso codes etc.
                console.log("geography object: ", geography)
                // geography also has geography.properties
                console.log("Properties: ", geography.properties)
                console.groupEnd("Geography")
                return (
                  <Geography
                    key={ geography.id }
                    geography={ geography }
                    projection={ projection }
                    onClick={ this.handleClick }
                  />
                )
              })}
            </Geographies>
          </ZoomableGroup>
        </ComposableMap>
      </div>
    )
  }
}

You can see in the screenshot that I can access the name of the country via geography.properties.name. With world-50m.json this should work, however there are other topojson files that don't have this information. A mapping object may be unavoidable there.
Again, not sure this is what you are after. Let me know if this helps.

Thanks! I will use your topojson file.


[SPARK-32492][SQL] Fulfill missing column meta information COLUMN_SIZE /DECIMAL_DIGITS/NUM_PREC_RADIX/ORDINAL_POSITION for thriftserver client tools

What changes were proposed in this pull request?
This PR fulfills some missing fields for SparkGetColumnsOperation including COLUMN_SIZE /DECIMAL_DIGITS/NUM_PREC_RADIX/ORDINAL_POSITION
and improve the test coverage.
Why are the changes needed?
make jdbc tools happier
Does this PR introduce any user-facing change?

yes,
before

after

How was this patch tested?

add unit tests

Merged build finished. Test PASSed.

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

Test build #126807 has started for PR 29303 at commit cc8c90d.

Test build #126807 has finished for PR 29303 at commit cc8c90d.

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

Merged build finished. Test PASSed.

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

cc @cloud-fan @gatorsmile @maropu @wangyum thanks very much

@yaooqinn FYI to make the GitHub Actions tests pass, you might have to rebase.

I see, thanks, @HyukjinKwon.

Merged build finished. Test PASSed.

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

retest this please

Merged build finished. Test PASSed.

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

Test build #126845 has started for PR 29303 at commit 2a319ff.

Test build #126852 has started for PR 29303 at commit 2a319ff.

Test build #126845 has finished for PR 29303 at commit 2a319ff.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ExecutorProcessLost(

Merged build finished. Test FAILed.

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

Test build #126852 has finished for PR 29303 at commit 2a319ff.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ExecutorProcessLost(

Merged build finished. Test FAILed.

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

retest this please

Test build #126867 has started for PR 29303 at commit 2a319ff.

Merged build finished. Test PASSed.

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

Test build #126867 has finished for PR 29303 at commit 2a319ff.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ExecutorProcessLost(

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

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

Test build #126887 has started for PR 29303 at commit 5ec2092.

To check if we could fetch the new metadata via DatabaseMetaData, could you add tests in SparkMetadataOperationSuite, too?

Test build #126887 has finished for PR 29303 at commit 5ec2092.

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

Merged build finished. Test PASSed.

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

Test build #126960 has started for PR 29303 at commit 66d5812.

Merged build finished. Test PASSed.

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

To check if we could fetch the new metadata via DatabaseMetaData, could you add tests in SparkMetadataOperationSuite, too?

The new test can end to end cover the meta operations both for binary and HTTP mode, but SparkMetadataOperationSuite seems only works for binary only

Test build #126960 has finished for PR 29303 at commit 66d5812.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #126965 has started for PR 29303 at commit 8e1a276.

Merged build finished. Test PASSed.

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

Test build #126965 has finished for PR 29303 at commit 8e1a276.

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

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

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

Test build #126974 has started for PR 29303 at commit cf34aa3.

Test build #126974 has finished for PR 29303 at commit cf34aa3.

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

Merged build finished. Test PASSed.

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

thanks, merging to master!


chore: bump typescript to 4.5.4, and adjust storybook story.

SUMMARY

Saw that This PR was failing due to some esoteric linting issue in a storybook issue. This makes the same bump, also bumps Superset, and fixes the Story.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

Verified Storybook works fine locally. CI passing should cover the rest.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Thanks for the review @etr2460 - that package lock was accidental, and I'm glad you stopped to notice the gigantic file.


Jupyter is not opening

Issue Type: Bug
I've jupyter installed on my system. But i'm not able to open it
Extension version: 2020.11.358541065
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz (4 x 2394)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.90GB (4.49GB free)

Process Argv
--crash-reporter-id 94c7c2c1-d4eb-4a91-875a-886cd31e395f

Screen Reader
no

VM
0%

Thanks for the bug.
Can you do the following:

Go to settings and change this value debug:

Restart VS code
Reproduce your error
Copy the contents of the Jupyter output tab to this bug (either in plain text or as a file you upload)

Thanks

Now i'm able to open it but can't run it. please see the screenshot of error

For some reason our install is failing. You can do this manually instead.

Open an anaconda prompt
Switch to the environment you want to use (looks like base from the error message)
Type 'conda install ipykernel'
Restart VS code

It should pick up ipykernel then.
If not then we need the output I asked for above.

I followed your instructions as above and it is updated successfully. but when i open jupyter notebook in cmd it is showing below error

and also i'm getting IPYkernel not installed error and if I click on install then i'm getting error as could not install. as shown below

THat sounds like this issue here:
https://github.com/jupyter/notebook/issues/3435

I tried that and now i can run jupyter in browser.  but when I start jupyter in VS code i'm getting error as beow

That sounds like a path problem. You may have to start VS code from the same environment you're running jupyter from, or follow the directions here:
https://github.com/jupyter/notebook/issues/4980

That sounds like a path problem. You may have to start VS code from the same environment you're running jupyter from, or follow the directions here:
jupyter/notebook#4980

tried this too. but still not resolved my issue


Question about the seperated and unified augmentation in UniMatch v1&2

Hi! An interesting thing can be observed is that, in the original UniMatch, while using ResNet as the backbone, seperating the feature-level and image-level perturbation into different branches can gain more performance. However in UniMatch v2, while using DINO as the backbone, both kinds of perturbations are unified in a single branch rather than seperating them. I wonder if it is associated with the type of model? Have you done the experiment of seperating the perturbation using DINO as the backbone? Whether it can bring performance gain or not? Looking forward to your reply, thank you!

Separating the two types of perturbations are slightly worse than our current practice in most settings.


array_merge on null in Indexer.php:152

Mac: 10.13.3
VS Code: 1.20.0 (I saw this just before the update on VSCode 1.19.x)
PHP Intellisense: 2.2.6
NPM: 5.6.0
In the Console for the Dev tools I see this exception:
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:253 [Extension Host] ErrorException: array_merge(): Argument #2 is not an array in /Users/do/.vscode/extensions/felixfbecker.php-intellisense-2.2.6/vendor/felixfbecker/language-server/src/Indexer.php:152
Stack trace:
#0 [internal function]: {closure}(2, 'array_merge(): ...', '/Users/do/.vsco...', 152, Array)
#1 /Users/do/.vscode/extensions/felixfbecker.php-intellisense-2.2.6/vendor/felixfbecker/language-server/src/Indexer.php(152): array_merge(Array, NULL)
#2 [internal function]: LanguageServer\Indexer->LanguageServer\{closure}()
#3 /Users/do/.vscode/extensions/felixfbecker.php-intellisense-2.2.6/vendor/sabre/event/lib/coroutine.php(70): Generator->send(NULL)
#4 /Users/do/.vscode/extensions/felixfbecker.php-intellisense-2.2.6/vendor/sabre/event/lib/Promise.php(242): Sabre\Event\{closure}(NULL)
#5 /Users/do/.vscode/extensions/felixfbecker.php-intellisense-2.2.6/vendor/sabre/event/lib/Loop/Loop.php(261): Sabre\Event\Promise->Sabre\Event\{closure}()
#6 /Users/do/.vscode/extensions/felixfbecker.php-intellisense-2.2.6/vendor/sabre/event/lib/Loop/Loop.php(215): Sabre\Event\Loop\Loop->runNextTicks()
#7 /Users/do/.vscode/extensions/felixfbecker.php-intellisense-2.2.6/vendor/sabre/event/lib/Loop/Loop.php(194): Sabre\Event\Loop\Loop->tick(true)
#8 /Users/do/.vscode/extensions/felixfbecker.php-intellisense-2.2.6/vendor/sabre/event/lib/Loop/functions.php(122): Sabre\Event\Loop\Loop->run()
#9 /Users/do/.vscode/extensions/felixfbecker.php-intellisense-2.2.6/vendor/felixfbecker/language-server/bin/php-language-server.php(50): Sabre\Event\Loop\run()
#10 {main}

Let me know if you require more information and where it might be found... Thank you.

Simple patch:
patch.txt

@janekcz69 can you submit a pull request?

Yes, I try but
Authentication failed. You may not have permission to access the repository or the repository may have been archived. Open options and verify that you're signed in with an account that has permission to access this repository.


One line daily forecast

Are we currently able to output the next few days high forecast in one line?
I'm currently using the following one line to get the current temperature:
curl wttr.in/Vegas,NV?format=1\&u
⛅  +89°F
I'd like to be able to see something like:
⛅  +89°F, ⛅  +91°F, ⛅  +87°F
Or maybe a way to just simply just print the forecast for tomorrow?
Sorry if this is has been covered before. I've searched and read through the readme and couldn't find anything.
Thanks

Yes, it is a good idea + it would be great to have one-line plots,
like this
 ⢠⣄⡴⣸

or this:
 ▅▁▁▇▇▂▂▁▁▁▂▂

+1 here. That would be great to have a one-liner like @mattyrc suggested.


auto go to first line after :Autopep8 format file

A few days ago I update vim-autopep8 to v1.1, and I find  after :Autopep8 <CR> cursor auto go to first line. But in previous version it not change position.
How can i disable this feature?

@shidenggui  Sorry. there is no setting to disable it.
However, I'll fix it. Please wait for the next version.

I'm having the same issue, is there any progress with this issue ?
Thanks for this plugins is awesome !!

Is there a fix yet?

@hmngwy

we can send a PR?
Yes,  I want your help!  Let's send PR to me.

@shidenggui @yanpozka
Sorry for the late fix.
I've fixed it, Please try new version.


Hovering as const returns any

TS stable and nightly
playground
"" as const

Heh, yep
"" as const
//     ^?

I think it would be nice to display the type of the const assertion here (as opposed to displaying nothing, which would also be acceptable)

(This is probably just a getTypeAtLocation missing case.)

I would like to take a shot at this. However, I'm not familiar with how to debug changes to the services.

Hi, If this is not assigned to anyone yet, I'm willing to work on this.

Have a look at

https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md#instructions-for-contributing-code
https://blog.andrewbran.ch/debugging-the-type-script-codebase/
https://github.com/orta/typescript-notes/tree/master/intro

We don’t actually assign community members, so if the issue still says “help wanted,” feel free to work on it. But be aware that someone else might work on it too. Once you’ve actively started and feel like you have a good chance of opening a PR, comment here so that others know not to start on it if they want a high chance of their code getting merged.

This looks like a bug with Scanner or Parser. Compiler reduces const into an Identifier instead of ConstKeyword.

That’s not a bug. A TypeReference needs an entity name (i.e., an identifier or dotted name). There’s nothing that says we can’t use an identifier node to store const in a type position, so const assertions were written that way to avoid changing the API for AsExpressions.


Add Netlify badge to README.md

This badge will enable us track the status of our Netlify builds

 Add Netlify Badge to README.md

@dpkreativ i would like to work on this.

Awesome! let's get started


consider additional OBC fields

From the original design doc:
spec:
  SSL: true | false [6]       # post phase-0, if at all
  cannedBucketACL: [7]        # post phase-0, if at all
  versioned: true | false [8] # post phase-0, if at all
...
1. SSL defines whether the connection to the bucket requires SSL authentication.
1. predefined bucket ACLs:
{"BucketCannedACLPrivate", "BucketCannedACLPublicRead", "BucketCannedACLPublicReadWrite", "BucketCannedACLAuthenticatedRead".
1. versioned determines if versioning is enabled.

See #92


Arc Postgres: Fixes for May release

Fixes to get the Arc Postgres pages working with the May release.

Regenerated swagger clients.  Most of the models are brought in by the Kubernetes pod model.
Added a route for getting a resource's pods.  The pod naming convention is more complex now, so the client can't calculate them anymore.
Added a Status column to the nodes table, which we can calculate now that we have the pods.
Deal with changes in the spec (e.g. resources requests and limits can be configured per role now)

Coverage remained the same at 34.417% when pulling ea1d6e8df523c30727fd1c29ef2a8989c01a0911 on brberger/arc-may-release-fixes into bb244e4b914dba4de4ccc131fc639747e44459d4 on master.


[BUG] Access forbidden help

It is showing access forbidden ErrorPic

i have this same issue

Please provide more information such as which hosting platform/method you are using.

Closing due to missing information.


Replaces deprecated refence paremeter with new placeid & tests.

Was using this to get details on a Place from Google but realized that the placeDetails function was using the old reference parameter. You can take a look here for confirmation. So I updated it to use the new placeid parameter where necessary.
Also added in a simple test for the placeDetails function seeing as how it didn't exist before. You will also notice an update to the .gitignore which is just ignoring my local env variables that hold my API key. Hope this helps!

Did this get merged into the repo or no?

@johnstew thank you for contributing. I couldn't merge/evaluate your code since the new library now 1.0.2 has been completely refactored.
I believe this has been fixed, as I replaced referenceId with placeId in the new code: https://github.com/moshen/node-googlemaps/blob/master/lib/config/constants.json#L28
Please let me know if this bug if fixed for you with the new library.
At this stage it is not possible to backport the fix to the previous version.

Okay cool that makes sense was just checking. Thanks for making the fix!


[feature request] bard ogcd options

currently the single target ogcd feature adds songs rotation, and the aoe one doesn't include pitch perfect. an option for both that just adds empyreal arrow+sidewinder+pitch perfect would be great!

So you want a single ogcd that doesn't add songs?

yes! but that still includes pitch perfect - and adding pitch perfect for the aoe one

pitch perfect is in the aoe one

well if it is then it isn't working for me 😅 this is with both features enabled
https://github.com/user-attachments/assets/557297ca-b589-42b5-adb5-52a144cbb667

Im going to assume you dont have action change set on wanderers to turn to PP. the code was weird. using pp hook for st but wanderers hook for aoe.
Ill just switch wanderers hook to PP hook and its all better.


Filter Rating Index

Description

Users should be able to view a list of GMs by their ratings and filter through that list according to the ratings that matter more to them.
Possible Implementation

Modify the index function on the Rating controller to take in a set of filters corresponding to rating type and only return ratings that fit the filter specified by the user.

Hey team! Please add your planning poker estimate with ZenHub @bcobo341 @IanjhPhillips @JasonGadoury @RobertoNittolo

for this task we actually want to be able to sort the index by a particular rating "score" @bcobo341 you'll need to do the following, in broad terms:

add an accessor to users to calculate their "total" / "global" score
in the index function, fetch all the users, and then sort them by that any of the individual scores (creative, flexible, etc)
return that data

you also need to be able to sort by the language they DM in, to do that

you'll need to add language to the sessions model (add migration, add language to $fillable, check tests still pass, adjust factories, maybe also the request validators)
accept a request param to decide what to sort by,
do a query on users that checks the language of sessions they DM in (you could also make an accessor for this if you'd like)
return the sorted data

Almost forgot, you'll also need to do a fuzzy search by the user's name, so something like User::where('name', 'like', '%{$variable}%')->...


Scan doesn't find variations with special characters

Describe the bug
Scanning is not able to identify variations when the common part of the filename includes characters that will be URI-encoded.
This includes spaces, symbols, and non-English characters.
To Reproduce
Steps to reproduce the behavior:

Create two map files where one basename contains the other, but the name includes spaces.
For example, "Forest Path.jpg" and "Forest Path Night.jpg".
Create a new scene using Forest Path as the background image.
Open the Scenery popup and scan for variations. Nothing is found.

Expected behavior
"Forest Path Night" should be identified as a variant.
System information (please complete the following information):

Scenery Version: 1.1.3
FoundryVTT Version: 11.315
Browser: Firefox
FoundryVTT Game System and Version: dnd5e 2.4.1

Additional context
FilePicker API returns URI-encoded paths. I will submit a PR to use decodeURI in the scan process.
Arguably it is good practice to use filenames that don't get encoded, but Foundry in general handles special characters without issue.

Hi @jacobsteffler,
sorry for taking some time to respond to your issue.
I've tried to reproduce the behavior as described (FoundryVTT v11 and v12; native Client and Firefox), but was not able to. I scanned for images with spaces in the file and path name. At first without your fix, than with your fix #18 .
In both cases the variant file was found! The only difference without your fix was, that the space character was replaced with the decoded %20 entity.
I've added another file named Forest Path Night & Rain.jpg and that was also found in both cases. And in both cases the ampersand was replaced with its decoded entity %26.
Do you have another example for me?

Hi, no worries.
I just tested this again with Foundry 12.331 and Scenery 1.2.0 (without my patch).
This seems to be working fine for me too now.
I remember when I first saw this, the Scenery popup showed the default file path with the original characters (space and &).
But this time, it shows the encoded characters, %20 and %26, from the start.
With those encoded characters in place, the search algorithm finds the variation files.
Thanks for looking into it, closing this issue.


Add flag to specify the last row to be a footer

There is no way to indicate whether the last row of the table should be considered a footer row (in the context of thead / tbody / tfoot ) if desired

Hi @Nysosis
I'm closing this issue as you've also created a PR for this. I will try to find some time looking into the PR 😉


ASMDEF for Examples

Mirror is not fully ASMDEF capable (Example scripts can't be referenced from other assemblies). This adds three additional ASMDEFs to make that work.

@Alexees check the files changed, it's only a readme from another pr as it seems

@vis2k whoopsi :)

@Alexees how to reproduce the issue that this fixes?
If I create a new 'Test' script in the Mirror folder then I can reference Examples just fine:
using UnityEngine;
using Mirror.Examples.Tanks;

public class Test : MonoBehaviour
{
    public Tank tank;
}

try deriving from the AdditiveSceneNetworkManager

works too:
using UnityEngine;
using Mirror.Examples.Tanks;
using Mirror.Examples.Additive;

public class Test : MonoBehaviour
{
    public Tank tank;
    public AdditiveNetworkManager manager;
}

is the code referencing this in an assembly itself?

right in the Mirror folder

If you put it in the very same folder as Mirror, it works. but if you have the script in some other structure, it fails. not sure if an assembly is necessary there, but the referencing script must not be part of mirror.

still compiles.
please tell us how to reproduce the issue @Alexees , otherwise it's an endless back and forth :)

ok, I'll do that on Monday ;)

closing this because we can't reproduce it.
feel free to reopen if you find a way for us to reproduce it :)

@vis2k sorry, forgot about it. To reproduce it:

Create a folder outside of Mirror in your project with a script extending the AdditiveNetworkManager
Add an ASMDEF file to that folder
Two errors will popup, because it can see neither the Mirror namespace nor the AdditiveNetworkManager

:tada: This PR is included in version 3.7.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Feedback on Later Binding SMV Plugin

Is your feature request related to a problem? Please describe.
This is some early, highly optional feedback on the excellent SMV Later Binding plugin. I did not manage to find time to comment during the review cycle, sorry.
We used this plugin (briefly) to configure some SMV subscriptions, and here is some feedback for enhancements at some stage.
Describe the solution you'd like

Initially, the person I tried out this extension on was confused about how to use it. I think perhaps some terminology changes would help.
a. For the publisher on the left-hand side, I'd like to suggest a terminology change. Instead of "List of Sampled Values Controls with linked FCDAs" we could have (as per the other SMV plugin): "Sampled Values Publisher".
b. For the subscriber on the left-hand side, I'd like to suggest we rename this from, "Selected Sampled Value data "smvcb0" / FCDA "AmpSv.instMag.i"" to: "Subscriber to". I'm not sure the control block name or the FCDA is useful if item 2 below is implemented. But if they are useful, I think including the IED name would be helpful. In many cases, merging units will have the same SMV control block name.

The selection on the LHS becomes lost when carrying out activity on the right-hand side. In other plugins (for instance, the Publisher plugin) we don't lose this, and it has a light green background (I think this is the activated property). This is valuable context for the user.

While the later binding plugin provides good functionality for the action of binding, it doesn't readily allow an overview of the configured ExtRefs which most tools provide, see the following screenshots from other applications which provide a tabular overview for each FCDA.
a. AcSELerator Architect

b. Siemens DIGSI 5

c. We could do this through a separate plugin. Perhaps this is a useful overview for all the different editors. But if you are doing the mappings for a three-phase set of currents and voltages, for example, it is helpful to be able to see what is "already done and what is still to do".
d. Another idea might be to allow clicking on the IED, and when this happens for all items in the SMV control block to be a synchronised list between the values on the left and right-hand screen, but this might not readily fit a mobile form factor.

Regarding point 3 of your feedback, I would propose to add the number of connection to the list item representing the FCDA element like so

Regarding point 3 of your feedback, I would propose to add the number of connection to the list item representing the FCDA element like so

I think that's a good idea.

Re-opening until #993 is dealt with.


Update README.md

adding vue-client-recaptcha
General

✏ Mark the necessary items without changing the structure of the PR template.

[X] Pull request template structure not broken

Type

ℹ  What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[ ] Fix
[X] Feature

Checklist

ℹ  Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉  Put an x in the boxes that apply.

[X] Title as described
[x] Make sure you put things in the right category!
[x] Always add your items to the end of a list

Open Source

[x] Link description does not contain a link to an author / third-party resource
[x] The documentation (README) contains a description of the project, illustration of the project with a demo or screenshots and a CONTRIBUTING section
[x] The documentation is in English.
[x] The project is active and maintained.
[x] The project accepts contributions.
[x] Not a commercial product

Apps/Websites

[x] The website is available without errors or ssl certificate problems, and load in a reasonable amount of time.
[x] The website is using vuejs intensively. It should detect vue with vue-devtools.

If you cannot detect vue with vue-devtools due to work at non public pages (e.g. for enterprise website), you can send Pull Request with screenshot that detected it.

[x] The website is original and not too simple. For that reason, blogs and simple landing pages are rejected.
[x] A commercial product using Vue, provided that guests could reasonably check out how Vue was used (i.e. A headless CMS which uses Vue for the Admin/editor Area and offers a free tier).

The description could be improved. Maybe let chatgpt help you if english is not you native language, but keep it short.


Feature/remove zwj contenteditable false

It may be beneficial if it was an option to use contenteditable="false" instead of the &zwj.
Purpose
Fix unusual contenteditable behavior in WebKit browsers as described in #393.
Changes

remove zero width joiner from end of span
add contenteditable="false" to inserted span

Side effects
Deleting the mention/emoji deletes the trigger (@, :, etc.).
Using contenteditable="false" may cause unexpected behavior in old browsers or IE. I only tested this in Chrome, Firefox, and Safari. This article from 2014 describes a bug when using contenteditable="false" in Chrome and Safari but I couldn't reproduce it so it appears to be fixed.

@ichord, this is ready for review. Please let me know if there are any changes that can be made to get this merged. Thanks!

Closing in favor of #423


Add proliferation and apoptosis gene sets to estimate growth rates

[ ] Additional function parameters, change functionality or change defaults?
[ ] New estimator in cr.tl.estimators?
[ ] New kernel in cr.tl.kernels?
[ ] New gene trend model in cr.ul.models?
[ ] New plotting function in cr.pl?
[ ] Other?

We need this for the external WOT kernel and for our real-time tutorial. @michalk8, could you prepare the abstraction/infrastructure for this please, I'll take care of finding the lists for the main model organisms.

@michalk8, from Schiebinger et al, Cell 2019, you should get 98 proliferation markers and 193 apoptosis markers.

For humans, use

this link for apoptosis genes (161 of them).
Following the scanpy tutorial on the cell cycle, I would recommend to use this list for proliferation. The list comes from this paper (which we should cite): https://science.sciencemag.org/content/352/6282/189

For all of these, please make sure to cite the origin. In case of the first one, a link to the website should suffice.

With mouse and human covered, we should have enough for now. We can always add more later when we come across informative resources.

closed via #630


Explictly typst blocks

It would be nice if wypst could have syntax for an explicitly typst inline or display equation, like the asciimath plugin. Then, rendering all equations as typst could be optional behavior.

Hello @joelatschool , thank you for pointing this out, I hope to include this in the next update. I'll link the relevant PR here.


[Bug]: projection mercator not working

Mapbox Implementation
Mapbox
Mapbox Version
default
Platform
iOS
@rnmapbox/maps version
^10.0.15
Standalone component to reproduce
import React, { useEffect, useState, useRef } from "react";
import { Alert, Image, StyleSheet, View } from "react-native";
import Mapbox from "@rnmapbox/maps";
import * as Location from "expo-location";
import { Button } from "react-native";

Mapbox.setAccessToken(
  "MY_TOKEN"
);

const App = () => {
  const [location, setLocation] = useState();

  useEffect(() => {
    (async () => {
      let { status } = await Location.requestForegroundPermissionsAsync();
      if (status !== "granted") {
        return;
      }

      let location = await Location.getCurrentPositionAsync({});

      setLocation(location);
    })();
  }, []);

  return (
    <View style={styles.page}>
      <View style={styles.container}>
        <Mapbox.MapView
          style={styles.map}
          followsUserLocation={true}
          region={location?.coords || []}
          projection="mercator"
          compassEnabled
          onLongPress={(f) => {
            console.log("Coordinates", f.geometry.coordinates);
          }}
        >
        </Mapbox.MapView>
      </View>
    </View>
  );
};

export default App;

const styles = StyleSheet.create({
  page: {
    flex: 1,
    justifyContent: "center",
    alignItems: "center",
  },
  container: {
    height: "100%",
    width: "100%",
  },
  map: {
    flex: 1,
  },
  annotationContainer: {
    alignItems: "center",
    backgroundColor: "white",
    borderColor: "rgba(0, 0, 0, 0.45)",
    borderRadius: 50 / 2,
    borderWidth: StyleSheet.hairlineWidth,
    height: 50,
    justifyContent: "center",
    overflow: "hidden",
    width: 50,
  },
});

Observed behavior and steps to reproduce
when I set the projection to mercator on the Mapbox.MapView I still see the globe and not the "flat" Mercator map
Expected behavior
No response
Notes / preliminary analysis
No response
Additional links and references
No response

import React, { useEffect, useState, useRef } from 'react';
import { Alert, Image, StyleSheet, View } from 'react-native';
import Mapbox from '@rnmapbox/maps';
import { Button } from 'react-native';

const App = () => {
  const [location, setLocation] = useState();

  return (
    <View style={styles.page}>
      <View style={styles.container}>
        <Mapbox.MapView
          style={styles.map}
          followsUserLocation={true}
          region={location?.coords || []}
          projection="mercator"
          compassEnabled
          onLongPress={(f) => {
            console.log('Coordinates', f.geometry.coordinates);
          }}
        />
      </View>
    </View>
  );
};

export default App;

const styles = StyleSheet.create({
  page: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
  },
  container: {
    height: '100%',
    width: '100%',
  },
  map: {
    flex: 1,
  },
  annotationContainer: {
    alignItems: 'center',
    backgroundColor: 'white',
    borderColor: 'rgba(0, 0, 0, 0.45)',
    borderRadius: 50 / 2,
    borderWidth: StyleSheet.hairlineWidth,
    height: 50,
    justifyContent: 'center',
    overflow: 'hidden',
    width: 50,
  },
});

If I run this code I don't see a global.

I have to check why in my case it get ignored then

basically It works fine on android but not on IOS

I've tested on iOS simulator. Are you trying the exact same component as described on https://github.com/rnmapbox/maps/issues/3254#issuecomment-1848367925, can you take a screenshot?

the only different is actually a  custom styleURL I've applied and it actually seems working without it

Im running in to this issue right now. Happens when i use the mapbox://styles/mapbox/dark-v11, mapbox://styles/mapbox/satellite-streets-v12, mapbox://styles/mapbox/light-v11, mapbox://styles/mapbox/outdoors-v12 or mapbox://styles/mapbox/streets-v12 styleUrl,
but not when using the others listed here: https://docs.mapbox.com/api/maps/styles/|
@Ladvace did ever solve it?

I'm seeing this issue as well. I've created a custom style with the projection set to 'mercator' when I add the style to the mapView it shows up as 'globe'.. if I remove the custom style prop the projection prop goes back to working.

@RemiHin you can solve it with custom styles. Create your own style in "Mapbox Studio" from default mapbox://styles/mapbox/streets-v12 and set projection to "mercator" as default.

@RemiHin sorry for late reply, I got the same problem, I managed to "fix" just not using the styling


Fix EthereumJS and dependent tools to remove header fields and enable the modified istanbul fork as implemented in the client

Expected Behavior
Fix EthereumJS and dependent tools to remove header fields and enable the modified istanbul fork as implemented in the client
Current Behavior
Current tools are not aligned with our client modifications w.r.t. removed header fields and istanbul fork.

Looks like @mrsmkl started already started this effort:  https://github.com/celo-org/celo-monorepo/pull/3210


Folding does not behave well for c/c++ goto(label) syntax

VSCode Version: Code 1.7.2 (7ba55c5860b152d999dda59393ca3ebeb1b5c85f, 2016-11-21T22:01:10.756Z)
OS Version: Darwin x64 15.6.0

Steps to Reproduce: Always.

The currently implemented folding strategy is based purely on the indentation of lines. A folding region starts when a line has a smaller indent than one or more following lines, and ends when there is a line with the same or smaller indent.
To be more smart and to, for example, understand c constructs such as goto, we will have to go one step further and introduce language agnostic folding regions. We have issue #3422 for this.


Make DynamicMixer and OutputStream generic

This commit adds a new trait, Mixer, and refactors some of the code around generic mixers in order to support it. This is to make more of the code reusable without rewriting - specifically, to support a feature that I would like to implement in bevy_audio where audio sources can send audio to an intermediate mixer. The motivation for this was to add a global limiter to all game audio, so that loud sounds did not cause clipping on the master bus, but another possible usecase would be to split in-game audio and menu audio into separate "worlds" and apply, for example, a low-pass filter while in the pause screen.

It looks like the test failures are due to unrelated code, and are because of the addition of redundant import checks to unused_imports.

A more-minimal version of this PR would just make OutputStream generic, which would still allow reusing rodio's mixer without adding an actual interface around creating your own.

Could you rebase this on main? (or merge main into it). Then you'll get the fixed (thanks @hamirmahal) test suite.

You're welcome, @dvdsk!

I'm going to close this given we just redesigned the mixer & stream and the code has diverged a lot now. During the design we discussed this use-case and decided to not make the mixer generic for now.
The performance and API tradeoffs where unclear and the use-cases are already possible by adding a Source to the mixer that is itself a new special mixer.
That reduced the use-case of this PR to optimization.
Once we have a better idea how the new dynamic source API will look & how the new Player will work designing this will be easier.
Feel free to re-open but the re-base is going to be hellish and its probably better to start again.


Add socket timeout settings and udp support for graphite writer

Hello,
I'm in the case where i have a central graphite server for all my datacenter (US, EU and APAC). I have seen that there is a hard coded value (200ms) on socket timeout and this PR will allow to set some additional settings for socket timeout and pool claim timeout. This add the possibility to use the UdpOutputWriter instead of the TcpOutputWriter (udp vs tcp).
I have deploy this version in production to fix the issue. I don't find where you generate the documentation to add some details for these new settings.
Some configuration examples:
"outputWriters" : [ {
        "@class" : "com.googlecode.jmxtrans.model.output.GraphiteWriterFactory",
        "port" : 2003,
        "host" : "your_host",
        "protocol" : "udp",
        "poolClaimTimeoutSeconds" : 2
      } ]

"outputWriters" : [ {
        "@class" : "com.googlecode.jmxtrans.model.output.GraphiteWriterFactory",
        "port" : 2003,
        "host" : "your_host",
        "socketTimeoutMs" : 1000,
        "poolClaimTimeoutSeconds" : 2
      } ]

Enjoy.

This looks good! Thanks (and sorry for the delay in merging this).


NotifyNeighborBlockEvent should use Positions not Directions

The NotifyNeighborBlockEvent event uses Directions to specify which block was changed. The net.minecraft.block.BlockSponge block updates neighbors up to 7 blocks, taxicab in each direction! The Direction class, which only supports up to 6 directions in each face, is not enough to determine which block the event is referring to.
Possible solutions would be:

Replace the Directions with Locationss.
Replace them with relative Vector3is.
Replace them with absolute Vector3is.

I count 6 blocks getting notified:

NORTH
SOUTH
EAST
WEST
UP
DOWN

Where is the 7th?

Maybe counting Direction.NONE?

I meant any blocks in the 8 by 8 by 8 octahedron (2d example) surrounding the sponge can be notified, up to 65 blocks max, 512 blocks to describe, and would be affected if it wasn't restricted by Mojang.
Videos:

https://youtu.be/EGVDB_qHZtw?t=39s
https://youtu.be/p8CI7AcH3h4?t=34s

Wiki:

http://minecraft.gamepedia.com/index.php?title=Sponge&oldid=957301#Usage

Source Code:

mcp/src/minecraft/net/minecraft/block/BlockSponge.java:97 (Restrict to 7 blocks away)
mcp/src/minecraft/net/minecraft/block/BlockSponge.java:104 (Restrict to 65 blocks total)
mcp/src/minecraft/net/minecraft/block/BlockSponge.java:112 (Update neighbor blocks)

Maybe some refactoring is needed then, I find it hard pressed to call blocks updating further then immediately next to the block a neighbour.
Parent event/interface that has the position of the block updating (NotifyBlockEvent), making notifyNeighbour a sub event?
Or remove notifyNeighbor in favour of the other event?

So, having worked on block notifications yesterday in the cause tracking refactor, I can safely say that the event is intended for when blocks simply tell the world to notify neighbors at a certain position. In a sense, this is a pre-notification event to determine whether the blocks will be notified and their logic is processed.
Having that said, possibly the javadoc should be clearer?

The problem is though, is that BlockSponge changes the nearby blocks, and then notifies all the blocks it changes.
If you cancel the sponge changing the water to air, how do you then prevent the sponge from updating that water source if you can't tell what block is being notified?

the event is intended for when blocks simply tell the world to notify neighbors at a certain position.

So this even shouldn't belong to sponges, and a new event for blocks updating a block at a distance needs to be made? Or that this is the correct event, it just needs an added field or something?

@ryantheleach Again, for each block position the sponge is changing to air, the world is still being told to notify neighbors, which evidently is going to throw the NotifyNeighborBlockEvent for that specific block position (again, all the block positions that the sponge has changed water to air). That being said, NotifyNeighborBlockEvent is not a ChangeBlockEvent but determines whether other blocks are neighbor notified. For the supposed up to 64 blocks being changed by a sponge, you'll end up getting 64 individual NotifyNeighborBlockEvents thrown for the 64 positions.

Yeah, sorry I understand now.
@CrystalMageX It's not that the sponge block is notifying the water/surrounding blocks, but is triggering the water/air to notify it's neighbours.
What needs to happen is to cancel the updates of those neighbours, if the cause was the sponge block, as opposed to cancelling neighbour notifies originating from the sponge block.


Consolidate unstyled button font smoothing styles

Related: https://github.com/18F/identity-idp/pull/4825#discussion_r600735686
Why:

Account for missing usa-button--unstyled:hover and usa-button--unstyled:active
Single point to remove in the future, as noted in the preceding comment

I think visual regression got confused with #214 since it runs against the live site, and the live site update was probably delayed around the latest rebase here.


Documentation

It worth to mention that allure-commandline is now available on NPM: https://www.npmjs.com/package/allure-commandline
I think that is the best way install it within node.js project, so it worth to point this out.

Thanks @just-boris


Catch Limiter Bug Fix

Added default values to daily_catch_limit and exit_on_limit_reached incase they are not found in CatchPokemon Task

👍


Date format not possible in Attributes

When creating a contact all types of input are accepted except for the date format.
I tried sending a time.Time value, or formatting the time to a string in the format "02-01-2006", day-month-year, the same as the settings in my project.
I also tried to format it: year-month-day and month-day-year. All resulting in:
Status: 400 bad Request
Code: "invalid_parameter"
Message: "Invalid date format"

var attributes interface{}
attributes = map[string]interface{}{
"BIRTHDAY": time.Now()
}
contact := sendinblue.CreateContact{
Email:               email,
Attributes:          &attributes,
}

sib := sendinblue.NewAPIClient(cfg)
_, resp, err := sib.ContactsApi.CreateContact(ctx, contact)

What am I doing wrong?

The documentation for date showed 01-02-2006, but it should have been in the form:
t.Format("2006-01-02T15:04:05.000-0700")
Maybe add automatic parsing of time.Time objects in the actual API itself?
I now wrote the helper method myself:
func GetDataAsJson(data map[string]interface{}) *interface{} {
	attributes := make(map[enums.MailFields]interface{})
	for field, value := range data {
		if t, ok := value.(time.Time); ok {
			if t.IsZero() {
				continue
			}
			attributes[field] = t.Format("2006-01-02T15:04:05.000-0700")
		} else {
			attributes[field] = value
		}
	}

	var res interface{}
	res = attributes

	return &res
}


Connection Lost during hijacking the master/slave

Hi RCayre,
I encountered some problems when performing the InjectaBLE attack. The following is my environment.
Attacker

Ubuntu 20.04.4 LTS in VMware
Kernel Version 5.4.0-117-generic
PCA10059 NRF52840 Dongle

Master Device

FusionRTLS Base Station, BLE 4.1

Slave Device

FusionRTLS Tag, BLE 4.1

I have 2 questions I want to ask for your help.

Connection Lost during hijacking the master/slave
When performing Hijacking the Master or Hijacking the Slave, I usually encounter the Connection Lost problem. The connection often breaks while sniffing packets. For example, the connection was lost after receiving lots of Encrypted Packets. Then the mirage stopped at [FAIL] Connection lost ! for a very long time.
The second example is that the injection was successful but the connection was lost in the end. So Hijacking the Master failed.

The last example is when I performed Hijacking the slave, the connection was back after I waited for a few minutes.

I want to know the cause of this problem. Why does the mirage (or maybe the dongle) keep disconnecting when attacking?
Mirage bug: usb.core.USBError: [Errno 110] Operation timed out
While I was performing both Hijacking the Master and Hijacking the Slave, the mirage showed the below error message.

Hijacking the slave

Hijacking the master

Hi,
All these issues seems related to the fact that you are trying to sniff and inject packets into an encrypted connection.
The firmware relies on connection update packets to update the channel hopping parameters during sniffing, meaning that if they are encrypted the connection will be lost if the connection is updated. Similarly, you can't inject unencrypted packets into an encrypted connection, it will lead to a connection failure according to the specification.

Oh~ I see. Thank you very much
Is it possible to inject packets before encryption procedure ( When the slave responses LL_START_ENC_RSP) ?

Theoretically, it is. However, maybe you will have to modify the firmware to make it work (you have to inject the packet soon enough to win the race condition before the encryption starts).
Let me know if you manage to perform this attack, it seems interesting.

I got it!  Thanks for your great advice.
I will research this attack recently.


Update open-graph extension

Description

Fix the link to the images in OpenGraph (#11787)

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer I got the same issue here as in one of my previous PR, see (https://github.com/raycast/extensions/pull/11742#issuecomment-2048531095)
This time the author davidho0403 seems to fail the PR, what do I need to do here?


cosmetic change

This is my first pull request. I would like to make a minor change and merge it directly to test the pull request functionality.

Tests passed. Thank you.

Tests passed. Thank you.


Add proposal for grafanaserviceaccount crd

My design document over a proposed Grafana Service Accounts as CRD as discussed in issue 1388

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

From a security point of view I'm relatively worried about this, since anyone having the possibility to create a GSA CRD would have the possibility to become admin in any instance they want to.
I'm hesitant if we even should allow crossnamespace access for this resource.
For a secret name, I'm leaning towards not letting the user providing the secret name where the token will reside.
Instead, I would build it up from the name of the <GSA-CRD-name>-<GSA-grafana-instancename>-<SA-id> to make sure that the secret name is always unique, or something like that.
The secret key could then just be the same as token name.
I think it would be good if we can get an example on how the secret should look like depending on the tokens.

Do you need me to fix the trailing white spaces and update the branch?

If you can it would be great

I think everything should be fixed now


Inview and initialisation after context has been scrolled to the bottom

Hi there, I've really been enjoying getting to know Waypoints.
I'm developing a simple comments system with a modal popup that has a scrollable div, and within that a comments div, and within that the actual comment's divs. So:

      Comment

      Comment

      Comment

The comments are displayed with the most recent at the bottom. Currently I scroll the user to the bottom, then create the waypoints (using Inview):
content.animate { scrollTop: content.prop('scrollHeight') },
  duration: 1000
  complete: ->
    for comment in content.find('.comment').has('.metadata > span.new')
      do (comment) ->
        new Waypoint.Inview
          element: comment
          context: content[0]
          entered: (direction) ->
              this.destroy()
              console.log this.element
              console.log direction

Unfortunately, when I register the waypoints, they all trigger a 'down' direction immediately, even those that aren't at all in view (i.e. way up the scrollable area).
The idea situation would be for those waypoints that are completely in view to trigger immediately, but those that are partially or not in view at all to not.
Am I pushing the capability of Inview a bit here?

I think I've found the reason, that there is an assumption that the waypoints are initialised when the context hasn't been scrolled yet (and is at the top of the page).
How would you suggest one work around this?

In terms of code, changing this:
else if (freshWaypoint && axis.oldScroll >= waypoint.triggerPoint) {
  waypoint.queueTrigger(axis.forward)
  triggeredGroups[waypoint.group.id] = waypoint.group
}

to this:
else if (freshWaypoint && axis.oldScroll <= waypoint.triggerPoint) {
  waypoint.queueTrigger(axis.backward)
  triggeredGroups[waypoint.group.id] = waypoint.group
}

Fixes the problem for me and changes the assumption that we're at the top of the context to that we're at the bottom of the context when the waypoints are first freshly triggered.
Would you be interested in turning this into a setting of some kind?

I figured that instead of hacking around the problem, it would make sense to only trigger fresh waypoints when they're actually in view. Then we're not making any assumptions about where we are scrolled at when a waypoint is initialised. Right now I think the assumption is that we're at the top of the context. I've love some input on this solution as I don't normally work in Javascript.

I had a problem relating to this when creating a waypoint that was supposed to trigger when the user scrolled past it, in the "up" direction.
Because of scroll throttling, I believe, the Waypoint was sometimes created below the current scroll position. This ment that the user had technically scrolled past the waypoint but the waypoint was never triggered.
This problem does not exists for waypoint that should trigger in the "down" direction, because of the freshWaypoint check @brendon mentions.
A solution to this would be appending the code he suggested, thereby allowing one check for fresh waypoint below the trigger point and one check for those above.
I have supplied a PR for this issue #530

Hi @Jontis00, unfortunately no one ever replied to my work. Fingers crossed for yours. :)

By the way, did my PR also solve your problem. I've not looked in detail but can see they deal with things a little differently.

I do not believe it would, also I don't really agree with the premise.

It doesn’t make sense to trigger fresh waypoints that are already
outside of the visible area of the scrollable context

Since the code your editing applies to all waypoints, not only Inview ones.
Consider a sticky navbar, if the user loads the page with an anchor link the fresh waypoint might be created after the browser already has scrolled past the point at which the navbar becomes sticky.
Currently this would result in the waypoint getting triggered because of the
freshWaypoint && axis.oldScroll >= waypoint.triggerPoint check
With your solution I believe the navbar would not get stuck until the user scrolled all the way up and then down again.
What I am instead suggesting is that the fresh waypoint logic not only gets applied waypoints created above the current scroll position, but also for once created below.
This might but us half way towards solving your issue, but I am very unsure about that.

Thanks @Jontis00, yes I see that depending on the use case, default triggering might be a desirable thing, as you demonstrate. Perhaps this functionality should be an option that can be disabled then? In my example I don't want to trigger waypoints above where I am because (in my case) that would imply that the 'thing' had been seen which isn't the case.