Default user 'ubuntu' in Vagrant not 'vagrant'

I've completed the Vagrant setup as per the instructions however I note that the default user when I ssh into the vagrant box is ubuntu and not vagrant. Whilst this isn't the problem, I can't seem to SSH into the box using the password vagrant. The second implication is that when I'm connecting my mysql client to the vagrant box using SSH it is prompting me for the password. In both cases I'm using the SSH key ~/.vagrant.d/insecure_private_key.
I've searched around and it seems this password issue has happened for other Vagrant installs, however I'm not sure the relevance of my problem to theirs.
Given that you just completed this commit https://github.com/xyu/heroku-wp/commit/af3cd22f3eb1059f0a7140551722f5d88843b1d6 I was wondering if this is something that may have recently changed in the Vagrant file.
I've typically used MAMP on my Mac to run wordpress sites so using Vagrant is new to me. Apologies if this is a newbie question.
Thanks!

An update that answers the mystery of the password but not whether the config is as you intended.
I found the password for ubuntu in: ~/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-xenial64/20170119.1.0/virtualbox/Vagrantfile
Using this to ssh into the server with ubuntu and into the mysql instance worked correctly.
However when trying to access http://herokuwp.local/  I receive the error 'File not found.' printed on the screen. There could be something else going on with the local setup?

@toddheslin I think PR #88 should resolve your issue by using a different Vagrant base box. Can you test and see if it works on your machine?

Thanks @xyu just trying this now. Removed the old VM and started fresh with vagrant up but I'm seeing the continual error:
 herokuwp: Warning: Authentication failure. Retrying...
I wish I knew more about Vagrant.

Alright! So with the help of this thread on stack overflow, here is how I fixed it.

In the Vagrantfile I added these lines in the Vagrant.configure block:

  # Add system SSH key
  config.ssh.private_key_path = "~/.ssh/id_rsa"
  config.ssh.forward_agent = true

I SSH'd the local machine and copied by id_rsa.pub

vagrant ssh
nano ~/.ssh/authorized_keys

I copied the public key below the existing entry. Then,
chmod 0600 ~/.ssh/authorized_keys
exit

Then it was as simple as:
vagrant reload
vagrant provision

Thanks for your help @xyu Add these changes in this branch and it should be good to go.

Okay and then this happened after the provisioning.  I thought we were good to go but this is one more to fix:

@toddheslin I think with the new image you should not need those SSH hacks for this to work. Perhaps the problem is the vagrant image is dirty. Can you try destroying the image with $ vagrant destroy then reprovision from scratch with $ vagrant up again?

@xyu I thought I did this but for completeness I tried again.

Commented out the key changes suggested above
Destroyed the existing box with $ vagrant destroy
Attempted to rebuild the box with $ vagrant up

This error occurred:

Destroyed the box again, just in case there was any issue
Uncommented by few lines of keys suggested above
Same error, so canceled the operation after it was complaining about the key.
SSH'd in, as per my suggestion above and made those changes.
Instead of $ vagrant reload I decided to continue with $ vagrant up

Error was a bit different this time:

I've been playing around with this a bit. Here is what I've found:

Running vagrant up fails because the public key on the machine didn't match my ~/.vagrant.d/insecure_private_key
Once changing it, it still didn't work until I did vagrant reload which reloaded the config.

However this still didn't load. @xyu hoping you might have some thoughts on this.

@toddheslin What version of Vagrant do you have? Looks like in 1.7 vagrant up generates a random key pair instead of relying on the insecure key that comes with vagrant itself:
https://github.com/mitchellh/vagrant/pull/4707
I think https://github.com/xyu/heroku-wp/commit/fb644421b9f964ef876c68b9b5983a0c5eff6c0d should fix your ssh issues because it configures Vagrant to use user and password auth for ssh instead of keys which I guess now vary between versions.

@xyu  I've got 1.9.1
Just tried the change you made in https://github.com/xyu/heroku-wp/commit/fb644421b9f964ef876c68b9b5983a0c5eff6c0d
It did proceed without complaining during the authentication stage however I came across this error:

Ok I think the timeout is a different problem, I think the easy way to solve that is to set a longer timeout for Composer:
https://getcomposer.org/doc/03-cli.md#composer-process-timeout
However I'm not sure why it's taking over 5 minutes to execute for you. I think it might be best if we open another issue to debug that problem so we can get this SSH auth and chef.io ubuntu image fix closed and merged in.

Thanks @xyu you got it!
Problem was that my theme file (with node_modules etc) was quite large. I just added:
COMPOSER_PROCESS_TIMEOUT=420
under the MYSQL env variables within install.sh
Then I destroyed the Vagrant box, removed the tmp folder from the project and tried vagrant up again. Works perfectly 💯


Uniformisation of block's title spacing

While producing a poster with this template, which is beautiful and perfect for what I need, I encountered a small alignment bug with the titles of blocks. In fact, the line of alert blocks seemed a little bit off compared to the line of normal blocks, when compared from the top of the body frame. Setting the first \vskip of alert blocks to 0pt seems to solve this problem.
Here is a working example of this problem (compare blocks at the top of the page).
Poster_alignement.zip
poster.pdf
Poster after this fix :
poster.pdf

Ooh nice find, I hadn't noticed that before. Thank you for the fix! Merged in 23dcd18.


Remove admin urls

Fix #6

Solved this issue with f6add21136bb32c53e1948df214ac76b4789a82e
Different approach:
Admin site url pattern is in a variable now. It will be different for dev and prod


Update variable X to x

Hi @WildanJR09 ,
Thank you for this, however, it's quite often in machine learning that X is used rather than x.
A capital instead of a small letter.
This is because in mathematics a matrix (or tensor) is usually represented by a capital (e.g. X is often a matrix/tensor) where as a vector is often represented as a lower case letter (e.g. y is often a vector).
Though this is confusing in ML since X can also often be a vector.
See more here: https://www.britannica.com/science/matrix-mathematics


Fix memory leak cache for get_contract

closes #322

define maxsize to 1024*100 (Would be enough?)
add cachetools to requirements
replaces @cache  with @cached defining that the key to storage the cache is the safe_address
add a test to check that currsize have correct values
cache maxsize defined in environment var

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
13 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.3%) to 89.765%

Files with Coverage Reduction
New Missed Lines
%

gnosis/eth/oracles/oracles.py
2
89.27%

gnosis/eth/typing.py
2
83.33%

gnosis/protocol/gnosis_protocol_api.py
2
89.25%

gnosis/safe/api/relay_service_api.py
2
52.27%

gnosis/safe/safe_tx.py
2
90.53%

gnosis/eth/ethereum_client.py
3
86.91%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
3359

Relevant Lines:
3742

💛  - Coveralls

define maxsize to 1024*100 (Would be enough?)

What's the unit for this?

define maxsize to 1024*100 (Would be enough?)

What's the unit for this?

define maxsize to 1024*100 (Would be enough?)

What's the unit for this?

define maxsize to 1024*100 (Would be enough?)

What's the unit for this?

Reviewing the documentation, maxsize is the number of elements. Then with the default value we have for 1024*100 safe contracts, maybe is too much :) 1000 would be enough? What do you think?

define maxsize to 1024*100 (Would be enough?)

What's the unit for this?

Reviewing the documentation, maxsize is the number of elements. Then with the default value we have for 1024*100 safe contracts, maybe is too much :) 1000 would be enough? What do you think?

So if I'm not mistaken this Cache is tied to a specific Safe. A new instance of the safe would have its own def get_contract(self) -> Contract.
The contract behind a proxy doesn't change that often so I'd say a max_size of 1 should be good. The question is if a Proxy is upgraded (new master copy) how would you invalidate this? I'm assuming a new Safe instance with the same address is created.

define maxsize to 1024*100 (Would be enough?)

What's the unit for this?

Reviewing the documentation, maxsize is the number of elements. Then with the default value we have for 1024*100 safe contracts, maybe is too much :) 1000 would be enough? What do you think?

So if I'm not mistaken this Cache is tied to a specific Safe. A new instance of the safe would have its own def get_contract(self) -> Contract.
The contract behind a proxy doesn't change that often so I'd say a max_size of 1 should be good. The question is if a Proxy is upgraded (new master copy) how would you invalidate this? I'm assuming a new Safe instance with the same address is created.
This cache is shared between instances, if we have maxsize=10 means that we would could cached 10 Safe(<address>).get_contract() where each address is different.
Regarding your question, maybe we could use TTLCache and define ttl=60*10 (the unit are seconds). Then each 10 minutes we are going to invalidate the cache.

This cache is shared between instances, if we have maxsize=10 means that we could cached 10 Safe(<address>).get_contract() where each address is different. Regarding your question, maybe we could use TTLCache and define ttl=60*10 (the unit are seconds). Then each 10 minutes we are going to invalidate the cache.

Oh ok. I just double checked and it seems that there's an instance specific cache – https://docs.python.org/3/library/functools.html#functools.cached_property
I will come back to this next Monday. Need to rethink the size of the cache.

This cache is shared between instances, if we have maxsize=10 means that we could cached 10 Safe(<address>).get_contract() where each address is different. Regarding your question, maybe we could use TTLCache and define ttl=60*10 (the unit are seconds). Then each 10 minutes we are going to invalidate the cache.

Oh ok. I just double checked and it seems that there's an instance specific cache – https://docs.python.org/3/library/functools.html#functools.cached_property
I will come back to this next Monday. Need to rethink the size of the cache.

Similar to what was mentioned here: https://github.com/safe-global/safe-eth-py/pull/325#discussion_r944407632 since this is a library that might have different use-cases I'd leave this option in a configuration file with some "sensible" default like 100?
The Safe Transaction Service would then set this variable to one according to our needs.

Hi, my point of view on this:
@moisses89 , indeed you found the origin of at least some big memory issues and that's related to my understanding on how things work. I thought Cache was binded to every object but when used on a method it was binded to the class, and this way it only grows bigger every time a new Safe is created. Really nice work.
Regarding the implementation, I don't like too much adding cachetools or using a LRUcache, I don't think it's needed as every instance of Safe will only have one contract, and that memory will be released by Python as soon as we stop using the Safe object. I will propose a new PR handling this.

and that memory will be released by Python as soon as we stop using the Safe object.
This issue was created from this one
https://github.com/safe-global/safe-transaction-service/issues/1008#issuecomment-1210637658
I think that when the object is created from maybe gunicorn, the memory is not released any more. what do you think @Uxio0 ?

What do you think of https://github.com/safe-global/safe-eth-py/pull/339 ? I think is easier and more adequate for this case

I think that when the object is created from maybe gunicorn, the memory is not released any more. what do you think @Uxio0 ?

That's not right. As long as you stop using an object Python garbage collector should clean it at some point. If that's not true we would see memory leaks everywhere.

What do you think of #339 ? I think is easier and more adequate for this case
Ok, I was proposing store the contract for different instances meanwhile the address was the same. In this case the idea is keep on cache while the object is live, I got it correctly?

What do you think of #339 ? I think is easier and more adequate for this case

Ok, I was proposing store the contract for different instances meanwhile the address was the same. In this case the idea is keep on cache while the object is live, I got it correctly?

That's right

Other option would be define __eq__ and __hash__ for the Safe object so a new object with the same Safe address stores the contract in the same cache, but I don't know... We can talk about it tomorrow

Closing this PR to continue with #339 proposal.


Doing so with the -debug flag doesn't fare much better.
ERROR    root: compiler frontend failed to generate LLVM bitcode, halting

clang --version returns this:
clang version 3.8.1-svn268518-1~exp1 (branches/release_38)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

And I'm running Kubuntu 15.10.
However, I have several versions of LLVM installed, with the version managed through update-alternatives (though admittedly it may not be set up properly or completely).

I have not tested Emscripten support in a while, compilation of the Lime binary should still work, but if there are other issues like these, it is probably caused by needed updates to the HXCPP library for better Emscripten support. If you are interested, try the latest HXCPP, and see if it performs better?
When last tested, OpenFL HTML5 output compiles much faster, is smaller and runs much better than Emscripten, but this could change in the future. I would love to hear what you find, and would be happy to assist more on Slack or the forums if you dig into this.
I apologize for the long delay in adding a comment here :smile:


Charging State

Describe the bug

How to reproduce

Expected behavior

YAML configuration

# please paste here your card config

Screenshots

Version

Dear All,
I have an issue to get charging state icon when the mobile is plugged !

the attribute is good as show on the secondary_info text !
have you an idea to get same icon as presented on your cards
Thanks

It looks like attribute is a string not a boolean value so in your config you should have value: "True"

It's works, thanks for the fast answer !

Sorry, now it's works but if i use an auto entry include filter and if the entity didn't have this battery_charging attibute the system put it as True -> Bug ?

It is by design (this way you can set any custom text as a secondary text).
The solution in such cases is to list explicitly the entities which have charging state. Similarly what you have for vanessa/william etc. So basically you don't set secondary_info property in the root config but you put it individually for each entity on the entities list.

Yes agree for the secondary_info, my issue is more for the charging state where i look on the battery_charging attribute as "True" value but if the entities didn't have this one the Card consider as ok or it will return not ok so no charging icon for those entities !!

Ok I see it now and will take a look


[#112503901] Test for curl in cf-cli container

The CF acceptance-test helpers depend on curl, so we should verify it's presence in the container.

Going to rename this container...


Profile Manager: Add a message to indicate that the public ssh key was successfully updated/generated

Description
A message should be added after successfully updating or generating a public ssh key.
Implementation

Once the Updating/Generating is successfully completed a Message should be added to indicate that the key was successfully updated/generated and saved (preferably in green).

The message should appear in the same place as the error message (under the public ssh key  field) as seen in the screenshot below.

Verified on devnet.
The massage was added.


Add support for Person Tracking

Rollbar gem for RoR or Django has support for tracking people affected by a bug. I think it's a cool feature to have it in Rollbax as well.
Details here: https://docs.rollbar.com/docs/person-tracking
Would a PR be accepted for this?

@shankardevy person can be added in the occurrence data in your Plug error handler. Example can be found at https://hexdocs.pm/rollbax/using-rollbax-in-plug-based-applications.html.

Thanks!


Application api support added

We're currently processing your upload.  This comment will be updated when the results are available.


Misc sound issues

mousing doesn't make selection sounds
door sounds

glyphEd has no sounds

default equip/remove sounds

sounds attached to actions


32-bit int overflow in heap profile

Originally https://github.com/golang/go/issues/48580
I'm profiling a long-running program using LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libtcmalloc_and_profiler.so.4 HEAPPROFILE=shadow.heap HEAP_PROFILE_TIME_INTERVAL=180
The initial profiles are parsed fine by pprof, but after a point pprof refuses to parse any subsequent profiles.
Inspecting the profiles themselves, it looks like a 32-bit integer is overflowing.
First line from the last parseable profile:
heap profile: 2237252: 888238604 [2144665071:<PHONE_NUMBER>38] @ heapprofile

And from the first un-parseable profile:
heap profile: 2250136: 892383061 [-2147316050:<PHONE_NUMBER>94] @ heapprofile

I've confirmed that editing the files to change the negative number to a positive number allows pprof to parse it. It also works if I put a number there too large to be represented by a 32-bit int, suggesting that pprof supports a larger integer size.

I think this issue corresponds to https://github.com/gperftools/gperftools.

@ckennelly moved; thanks


error deploying chaincode at node startup -

Hi all, on the local blockchain, I tried to deploy the marbles v2 but it failed.
I failed with #58 before and it was resolved after setting the CORE_CHAINCODE_DEPLOYTIMEOUT. And then I met this error after the deploy was said to be success. After a number of retrying, it stopped and the deploy is not completed at the end.

[ibc-js] Deploy Chaincode - Starting
[ibc-js]        function: init , arg: [ '99' ]
     Waiting...

     deploy success [waiting another 30 seconds]
     16e655c0fce6a9882896d3d6d11f7dcd4f45027fd4764004440ff1e61340910a9d67685c4bb723272a497f3cf428e6cf6b009618612220e1471e03b6c0aa76cb

[ibc-js] Deploy Chaincode - Complete
[preflight check] 1 : testing if chaincode is ready
[ibc-js] read  - success: { jsonrpc: '2.0',
error:
{ code: -32003,
message: 'Query failure',
data: 'Error when querying chaincode: Error:Failed to launch chaincode spec(Could not get deployment transaction for 16e655c0fce6a9882896d3d6d11f7dcd4f45027fd4764004440ff1e61340910a9d67685c4bb723272a497f3cf428e6cf6b009618612220e1471e03b6c0aa76cb - LedgerError - ResourceNotFound: ledger: resource not found)' },
id:<PHONE_NUMBER>171 }
[preflight check] 1 : failed, trying again
[preflight check] 2 : testing if chaincode is ready

on the peer I saw there are new blocks after each time the deploy was said to success
(on localhost:7050/chain/blocks/{X})
Does anyone have idea why the "testing" is failed?
More information:
I host the hyperledger fabric from hyperledger's dockerhub image, running on a Ubuntu VM over my PC.
The docker-compose.yml is:
     vp0:
       image: hyperledger/fabric-peer
       ports:
         - "7050:7050"
         - "7051:7051"
         - "7052:7052"
       environment:
         - CORE_PEER_ID=vp0
         - CORE_PEER_ADDRESSAUTODETECT=true
         - CORE_VM_ENDPOINT=http://<IP_ADDRESS>:2375
         - CORE_LOGGING_LEVEL=DEBUG
         - CORE_CHAINCODE_DEPLOYTIMEOUT=500000
       command: peer node start

the mycred_docker_compose.json is
     {
             "credentials": {
                     "peers": [{
                             "api_host": "<IP_ADDRESS>",
                             "api_port": 7050,
                             "type": "peer",
                             "id": "vp0"
                     }],
                     "users": []
             }
     }

Check the logs on the peer (the port 7050 peer). The peer might be having some issue with starting the container for the chaincode.

@dshuffma-ibm  sorry for late reply as I was out of office for few days...
I got the log by command docker logs <container ID>

01:12:58.705 [dockercontroller] deployImage -> ERRO 070 Error building images: cannot connect to > Docker endpoint
01:12:58.706 [dockercontroller] deployImage -> ERRO 071 Image Output:
********************

********************

And then I tried to change my docker-compose.yml to

vp0:
image: hyperledger/fabric-peer
ports:
- "7050:7050"
- "7051:7051"
- "7052:7052"
environment:
- CORE_PEER_ID=vp0
- CORE_PEER_ADDRESSAUTODETECT=true
#- CORE_VM_ENDPOINT=http://<IP_ADDRESS>:2375
- CORE_VM_ENDPOINT=unix:///var/run/docker.sock
- CORE_LOGGING_LEVEL=DEBUG
- CORE_CHAINCODE_DEPLOYTIMEOUT=500000
command: peer node start

It comes another error

01:19:42.488 [dockercontroller] deployImage -> ERRO 073 Error building images: dial unix /var/run/docker.sock: connect: no such file or directory

I found some hints from the fabric-composer project sample's setup, here is my final docker-compose.yml
The marbles demo can be started using this config.

vp0:
image: hyperledger/fabric-peer
ports:
- "7050:7050"
- "7051:7051"
- "7052:7052"
environment:
- CORE_PEER_ID=vp0
- CORE_PEER_ADDRESSAUTODETECT=true
- CORE_VM_ENDPOINT=unix:///var/run/docker.sock
- CORE_LOGGING_LEVEL=DEBUG
- CORE_CHAINCODE_DEPLOYTIMEOUT=500000
command: peer node start
volumes:
- /var/run/docker.sock:/var/run/docker.sock

Thanks for your help!


Update 2.0.x version to 2.0.7.

Signed-off-by: Pan Li<EMAIL_ADDRESS>

Codecov Report

Merging #352 into 2.0.x will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            2.0.x     #352   +/-   ##
=======================================
  Coverage   80.79%   80.79%
=======================================
  Files          42       42
  Lines        1078     1078
  Branches      138      138
=======================================
  Hits          871      871
  Misses        133      133
  Partials       74       74

Continue to review full report at Codecov.

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


Minor fixes

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @dhalperi

LGTM (and I merged it)

Backported via https://github.com/GoogleCloudPlatform/DataflowJavaSDK/pull/222


[BUG] Maybe a typo in base.py

Hi all, looks like the SUPPORTED_SHARDS should be SUPPORTS_SHARDS
  File "/dataHDD16T/v-leiwang3/GPTQModel/debug/rebuttal_ppl.py", line 87, in <module>

  File "/dataHDD16T/v-leiwang3/GPTQModel/debug/rebuttal_ppl.py", line 64, in main
    model = GPTQModel.from_pretrained(pretrained_model_id, quantize_config)
  File "/dataHDD16T/v-leiwang3/GPTQModel/gptqmodel/models/base.py", line 686, in save_quantized
    if not self.qlinear_kernel.SUPPORTED_SHARDS and max_shard_size is not None:
AttributeError: type object 'TritonV2QuantLinear' has no attribute 'SUPPORTED_SHARDS'. Did you mean: 'SUPPORTS_SHARDS'?

@ZX-ModelCloud  Looks like the latest naming refractor missed a spot.

@LeiWang1999  Should be fixed in https://github.com/ModelCloud/GPTQModel/pull/417. We are running CI on master now to make sure we didn't miss other regressions.

There are more regressions. CI has found that the in/out features padding fix is causing more quant linear types to fail.

Closing issue as all CI passing with latest master.


ci: e2e job for ceph-csi operator

Describe what this PR does
This commit adds new job mini-e2e-operator for running ceph-csi e2e tests deployed via ceph-csi-operator.
Checklist:

[x] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
[x] Reviewed the developer guide on Submitting a Pull Request
[x] Pending release notes updated with breaking and/or notable changes for the next major release.
[x] Documentation has been updated, if necessary.
[x] Unit tests have been added, if necessary.
[x] Integration tests have been added, if necessary.

Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:

/retest ci/centos/<job-name>: retest the <job-name> after unrelated
failure (please report the failure too!)

@nixpanic, does the changes look good? Are there any other configuration required on Jenkins dashboard?


Highlighting in textarea

Is there a chance shadcn/ui has a feature for highlighting specific text in a textarea?

@kul-sudo  As far as I have used this library, there is nothing like that.

@kul-sudo As far as I have used this library, there is nothing like that.

That'd definitely be a great feature though!

@kul-sudo As far as I have used this library, there is nothing like that.

That'd definitely be a great feature though!

I agree! But I can't find it too.
Do you have any ideas?

@kul-sudo As far as I have used this library, there is nothing like that.

That'd definitely be a great feature though!

I agree! But I can't find it too.
Do you have any ideas?

You can only artificially put something over the areas you need to highlight. I haven't found any other ideas so far.

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

@shadcn we need this to stop using react-highlight-within-textarea hhhhhh
I tried to add something but it was laggy etc so I didn't add a pr :melting_face:
thanks

if anyone wanna improve lemme know
import * as React from "react";
import { cn } from "@/lib/utils";
import { HighlightWithinTextarea } from "react-highlight-within-textarea";
import { type HWTAProps } from "react-highlight-within-textarea/lib/esm/HighlightWithinTextarea";

type Highlight =
  | string
  | RegExp
  | (string | RegExp)[]
  | ((value: string) => string | RegExp | (string | RegExp)[]);

const TextareaHighlight = ({
  value,
  highlightString,
  onChange,
  className,
  ...restProps
}: {
  value: string;
  highlightString: Highlight;
  onChange: (value: string) => void;
  className?: string;
} & HWTAProps) => {
  return (
    <div
      className={cn(
        "relative rounded border border-input p-1 focus-within:ring-2 focus-within:ring-ring focus-within:ring-offset-2",
        className,
      )}
    >
      <HighlightWithinTextarea
        value={value}
        highlight={highlightString}
        onChange={onChange}
        {...restProps}
      />
    </div>
  );
};

TextareaHighlight.displayName = "TextareaHighlight";

export { TextareaHighlight };


Change ReadPolicy to FindPolicy and fix output

Changes to using FindPolicy to get policy settings for an object and updates the output from various commands to only include custom field info when it is set and when there is a policy set to add the info as to where it is being set.

@wilddev65 that change looks good, but CustomFieldGuid still doesn't show unless the field has a value.  is this the behavior we want?

The released version of the script had some issues with regards to both CustomFieldGuid and PolicyPath showing empty values on attributes where they would not ever be set on them. For example:
Last Renewed On: @{Value=09/16/2019 19:52:42; CustomFieldGuid=; Overridden=False; Locked=False; PolicyPath=}
I think it's confusing to have these attributes show when they have no value. The fix I added was just to not add them if they didn't have a value set. They will still have the custom field label in the output.
If someone needs the CustomFieldGuid, using Get-TppCustomField or simply looking it up in $VenafiSession should give them it.

Lol, cause I thought that was what you were asking for. Won't be hard to add 'customfield=' to it.

Lol, cause I thought that was what you were asking for. Won't be hard to add 'customfield=' to it.

Ah, nope, want it to be consistent.

Okay, this should give you what you need. It just removes the 'Value' if it is blank from the output, so custom fields show both their guid and if they are locked.


Allowing more flexible precision for TIMESTAMP, DATETIME fields.

Fixes #22558

Run PostCommit_Java_DataflowV2

Run PostCommit_Java_DataflowV2

R: @reuvenlax

R: @chamikaramj

R: @yirutang could you take a look?


Implement copied()

https://doc.rust-lang.org/nightly/std/option/enum.Option.html#method.copied
TODO

[ ] Implement copied operator for Maybe
[ ] Implement copied operator for Nullable
[ ] Implement copied operator for Undefinable
[x] #1606
[ ] Implement copied operator for PlainResult

To implement this, we should introduce Copy as the type bound.
interface Copy {
    copy(): self;
}

However, in JavaScript semantics, it might be a bit strange to think about copying.
I hesitate to implement this...

It's enough to use structuredClone + map() instead.


Mereged DHT unit test folders

There were two different folders for dht unit tests. Merge them.

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

          1 Message

:book:
See http://keepachangelog.com/en/0.3.0/ for details on good changelog guidelines

  Generated by :no_entry_sign: Danger


Develop

Coverage decreased (-33.01%) to 5.297% when pulling b5cf0a8cbbe61ace6ccf5cc844a0a43b0c0feb9a on develop into 4687a85ec6c83665b9583ebcf1a3827c6be0174b on master.

merged manually


Teleport user to warps instead of spawn when mine resets

as title says <--

idk bro ://

I have decided against this and I am instead using getSafeSpawn. This will teleport the player to a nearby location where they won't suffocate.


Fill out the documentation

Write user guide, some how-tos and finish the docstrings for automatic API documentation.
Release on Readthedocs.

A first rough version of the documentation is now up and running on Readthedocs.


[SPARK-23901][SQL] Removing masking functions

The PR reverts #21246.

@rxin @cloud-fan @gatorsmile @mgaido91

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Test build #93120 has started for PR 21786 at commit eb34d46.

Test build #93120 has finished for PR 21786 at commit eb34d46.

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/93120/
Test FAILed.

retest this please

Test build #93131 has started for PR 21786 at commit eb34d46.

Test build #93131 has finished for PR 21786 at commit eb34d46.

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/93131/
Test FAILed.


[Bug]:  Responsive object not working in options object for ReactJS

Contact Details
<EMAIL_ADDRESS>What happened?
Using

NextJS 14
TailwindCSS 3
Typescript
@tsparticles/engine ^3.3.0
@tsparticles/react ^3.0.0

Problem
The responsive object does not seem to work
In my options, I want to disable interactivity below a screen width of 1024px, I am trying to accomplish this by adding a responsive array in the options but it has no effect.
I am loading the options object here (being passed as props)
particles-background.tsx
"use client";

import { useEffect, useState } from "react";
import Particles, { initParticlesEngine } from "@tsparticles/react";
import { IOptions, RecursivePartial, type Container, type ISourceOptions } from "@tsparticles/engine";
import { loadSlim } from "@tsparticles/slim";
import { cn } from "@/lib/utils";

interface Props {
  options: RecursivePartial<IOptions>;
  className?: string;
}

export const ParticleBackground = ({ options, className }: Props) => {
  const [init, setInit] = useState(false);

  useEffect(() => {
    initParticlesEngine(async (engine) => {
      await loadSlim(engine);
    }).then(() => {
      setInit(true);
    });
  }, []);

  const particlesLoaded = async (container?: Container): Promise<void> => {};

  if (init) {
    return (
      <>
        <Particles id="tsparticles" particlesLoaded={particlesLoaded} options={options} className={cn(className)} />
      </>
    );
  }

  return <></>;
};

Expected results
Interactivity is disabled below a screen width of 1024px
Actual results
No effect is made to interactivity at all no matter the screen size
Tried

using loadFull instead of loadSlim.
reversing the interactivityDisabled and interactivityEnabled objects positions.
restarting the NextJS app.
searching the internet for any available solutions.

tsParticles Version

@tsparticles/engine ^3.3.0 * @tsparticles/react ^3.0.0

tsParticles Configuration
`particles-data.ts`

import type { ISourceOptions } from "@tsparticles/engine";

const theme = {
  particleColor: "#E44805",
  linkColor: "#B41817",
  zindex: {
    value: -50,
  },
  background: {
    color: "#0F0909",
  },
};

// Object containing code for the interactivity being enabled
const interactivityEnabled = {
  events: {
    onHover: {
      enable: true,
      mode: "grab",
      parallax: {
        enable: true,
        smooth: 10,
        force: 60,
      },
    },
    onClick: {
      enable: true,
      mode: "push",
    },
    onDiv: {
      enable: true,
      mode: "repulse",
    },
  },
  modes: {
    grab: {
      distance: 400,
      links: {
        opacity: 1,
      },
    },
    bubble: {
      distance: 400,
      size: 40,
      duration: 2,
      opacity: 0.8,
    },
    repulse: {
      distance: 200,
    },
    push: {
      quantity: 4,
    },
    remove: {
      quantity: 2,
    },
  },
};

// Object containing code for the interactivity being enabled
const interactivityDisabled = {
  events: {},
  modes: {},
};

// Actual options being passed to the Particles component
export const particlesConfig: ISourceOptions = {
  key: "parallax",
  name: "Parallax",
  responsive: [
    {
      maxWidth: 1024,
      mode: "canvas",
      options: {
        interactivity: interactivityEnabled,
      },
    },
  ],
  interactivity: interactivityDisabled,
  particles: {
    zIndex: {
      value: -50,
    },
    number: {
      value: 70,
      density: {
        enable: true,
      },
    },
    color: {
      value: theme.particleColor,
    },
    shape: {
      type: "circle",
    },
    opacity: {
      value: {
        min: 0.1,
        max: 0.5,
      },
      animation: {
        enable: true,
        speed: 3,
        sync: false,
      },
    },
    size: {
      value: {
        min: 1,
        max: 10,
      },
      animation: {
        enable: true,
        speed: 20,
        sync: false,
      },
    },
    links: {
      enable: true,
      distance: 150,
      color: theme.linkColor,
      opacity: 0.4,
      width: 1,
    },
    move: {
      enable: true,
      speed: 2,
    },
  },
  background: theme.background,
};

You can see in the `responsive` object I am defining a `maxLength` of 1024 pixels. I want the interactivity to be enabled after 1024 pixels and be disabled below 1024 pixels however no such effect is made.

What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge
Relevant log output
No response
Code of Conduct

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

I've found a workaround for now which is simply render two different components using javascript / typescript. Instead of using css to display none on the components (which doesn't work for some reason) I am rendering two entirely different components based on the window.innerWidth. Thought this might help!
"use client";

import { useEffect, useState } from "react";
import Particles, { initParticlesEngine } from "@tsparticles/react";
import { IOptions, RecursivePartial, type Container, type ISourceOptions } from "@tsparticles/engine";
import { loadSlim } from "@tsparticles/slim";
// import { loadFull } from "tsparticles";
import { cn } from "@/lib/utils";

interface Props {
  optionsMobile: RecursivePartial<IOptions>;
  optionsLaptop: RecursivePartial<IOptions>;
  className?: string;
}

export const ParticleBackground = ({ optionsMobile, optionsLaptop, className }: Props) => {
  const [init, setInit] = useState(false);

  useEffect(() => {
    initParticlesEngine(async (engine) => {
      await loadSlim(engine);
    }).then(() => {
      setInit(true);
    });
  }, []);

  const particlesLoaded = async (_container?: Container): Promise<void> => {};

  if (init) {
    return window.innerWidth > 1024 ? (
      <Particles id="tsparticles" particlesLoaded={particlesLoaded} options={optionsLaptop} className={cn(className)} />
    ) : (
      <Particles id="tsparticles" particlesLoaded={particlesLoaded} options={optionsMobile} className={cn(className)} />
    );
  }

  return <></>;
};

I've tested this in a vanilla environment, and it worked. I don't know if it's some issues with the React environment or Next.js but nice that you find a workaround.


Dissolve "test & troubleshoot" user journey into "build model", "build que…

…ry", and "create apis" user journeys

/easycla


422 Response on Account resource update

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Terraform Version

Terraform v1.7.5
on darwin_arm64
+ provider registry.terraform.io/prefecthq/prefect v2.0.0

Affected Resource(s)

prefect_account

Terraform Configuration Files

# Copy-paste your Terraform configurations here.
#
# For large Terraform configs, please use a service like Dropbox and share a link to the ZIP file.
# For security, you can also encrypt the files using our GPG public key:
#    https://www.hashicorp.com/security
#
# If reproducing the bug involves modifying the config file (e.g., apply a config,
# change a value, apply the config again, see the bug), then please include both:
# * the version of the config before the change, and
# * the version of the config after the change.
resource "prefect_account" "test_tf_account" {
  handle        = "robertprefectio"
  name          = "robertprefectio"
  billing_email =<EMAIL_ADDRESS>  allow_public_workspaces = false
}

Debug Output
prefect_account.test_tf_account: Modifying... [id=a0461d35-5351-4284-bb93-de0975f46b7d]
╷
│ Error: Error during update Account
│
│   with prefect_account.test_tf_account,
│   on resource.tf line 9, in resource "prefect_account" "test_tf_account":
│    9: resource "prefect_account" "test_tf_account" {
│
│ Could not update Account, unexpected error: status code 422 Unprocessable Entity, error={"exception_message":"Invalid request
│ received.","exception_detail":[{"loc":["body","allow_public_workspaces"],"msg":"extra fields not
│<EMAIL_ADDRESS>

Panic Output

Expected Behavior
Prefect account should be updated with the billing_email and allow_public_workspaces fields.
Actual Behavior
Unable to update Prefect account fields due to 422 error on tf apply.
Steps to Reproduce

terraform import prefect_account.test_tf_account a0461d35-5351-4284-bb93-de0975f46b7d
Specify prefect_account resource (see code above)
terraform apply

Important Factoids

References
Looks like the 'allow_public_workspaces' field for the update accounts API call is under a 'settings' field now. Most likely just needs a quick update to reflect the new nested structure.

#0000

thanks @robfreedy - we'll take a look

@robfreedy - this should be fixed now 👍🏼
We haven't cut a release yet, but you can:

Clone this project and switch to the directory
Run go install
Copy the ~/.terraformrc file to your system
Run your terraform commands

@parkedwards - is it worth considering a patch release here? If so, what does that process look like? (I can kick it off)


Change something in _read_packets

I've some trouble to connect to socket.io server 2.1.1
I've made this change, and now everything works well.

Yeah, for some reason the old code checks for a 0xFF byte, when the [https://github.com/socketio/engine.io-protocol#payload](protocol specification) says that the packet length is followed by a :.


HW1 submission - Austen Fourkas

Q1
wavelength, frequency, energy axis: +10
logarithmic axis with exp. ticks: +5
wavelength SI units: +5
labeled EM spectrum regions: +10
aesthetics: +3
Q2
Filter plot: +10
Atmospheric transmission plot: +10
Relative flux plot: +10
Q3
BD-11 3759 mags: +15
Sun mags: +15
Vega mags: +10
103/100


New package: JuliaCon v0.1.0

Registering package: JuliaCon
Repository: https://github.com/JuliaCon/JuliaCon.jl
Created by: @crstnbr
Version: v0.1.0
Commit: 59a8afab14839bd74622c18e2ffdb1f8868dc02c
Reviewed by: @crstnbr
Reference: https://github.com/JuliaCon/JuliaCon.jl/commit/59a8afab14839bd74622c18e2ffdb1f8868dc02c#commitcomment-51545417

Well, the code on the T-Shirt won't work if I change the package name :) Would be great if someone could merge this manually.
(cc @ViralBShah, @IanButterworth)


Google home suddenly not working any more with ha-bridge

It was working until yesterday suddenly google home has no control over ha-bridge device any more.  I have reset my google home and relink the ha-bridge but it doesn't seem to help.
i just want to confirm whether i am the only one facing this issue.
Google home still can control lifx and wemo but not ha-bridge any more.
Now if I ask google home to turn on and off my fibaro device, it will simply reply "i don't understand" or "power control is not available"
I

the bridge version is 4.5.5 and my Hub is Fibaro HC2

I wondered if anyone else had that problem. But I assumed it was Google screwing something up because my tp-link smart plug connected directly to Google doesn't work either now.

someone has complaint this issue in the following link.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/googlehome/uPKJ0PH36kI/OErsgABYBAAJ

just tried and its working for me on 4.5.6.

i have upgraded to 4.5.6 the result is the same.  In fact I notice all my wemo and lifx are not working at all if I have the philips hue linked.   I have to unlink then Wemo and lifx are working again.  It doesnt help either using google home 1.2.9 and perform are link of the hue

I had a loss of functionality a couple of days ago. Fixed it by updating to the latest jar, deleting and re-adding all my entries.
HTH someone

yesterday I have tried to relink and link couple of time.  i managed to be able to control the link but only a while (less than 4 sec) then i lost all control.   I will try reset tonight

I find out that by deleting the data folder and allowing it to create new files seems to resolve the issue but you're still unable to add an additional user once one link is established

I seriously don't think this is a ha-bridge issue.   it is the communication between google home and habridge seem to be gone.   From the ha-bridge using the test on/off I was able to turn off and on my device without any issue.

my problem resolved.  I delete the entire PI folder and setup from scratch.   No idea what is going on but everything work now.

my happiness is only a short while again google home stop working with habridge

Hmm, maybe I'll need to have a reset whitelist as that controls the id's that are given to the items that link.

This spontaneously resolved for me, I figured Google changed something. I didn't change anything and it started working again a couple days ago. As was mentioned before though Google Home app won't add/discover devices from a second gmail account linked to the same Google home.

yes for me i also noticed it must be some screw up by google because it was ok again

I'm also facing the issue with my Google Home Mini When I tell my mini to "turn off", it replies with "sorry, power control is not supported". I've to turn off it manually. But this solution fixes this annoying problem.


Use a ternary if for checking main_op is None in Saved Model Builder

Fixes a minor bug in saved_model which raises an
exception since evaluating ops as booleans are
forbidden in TF 2.x
Fixes #38041
I haven't added a test case yet, but the fix is quite simple.

@googlebot I signed it!


Client side ready to use cropper function added to readme.md

this issue #127 can be closed now since everybody that will read the What about showing the crop on the client? will copy and paste an easy to use/understand function that can be edited since it has a few line of code 👍

Nice, thanks


[#71] New rule unused_callbacks

Issue: https://github.com/AdRoll/rebar3_hank/issues/71
WIP!

The first acceptable version of this rule is done, but the macro cases are still unsupported!
Issues to handle macros were created:

https://github.com/AdRoll/rebar3_hank/issues/81
https://github.com/AdRoll/rebar3_hank/issues/82


[BUG] Rancher Monitoring - Grafana Visibility - user cannot create resource "services/proxy"

Rancher Server Setup

Rancher version: 2.7.3
Installation option (Docker install/Helm Chart): Helm Chart
Kubernetes version: 1.23 (EKS)

Information about the [Downstream] Cluster

Kubernetes version: 1.23
Cluster Type (Local/Downstream): Downstream (EKS)

Information about the Chart

Chart: rancher-monitoring
Chart Version: 102.0.0+up40.1.2

User Information

What is the role of the user logged in? Custom (View Only User)
Inherited from View All Projects
Inherited from View Cluster Catalogs
Inherited from View Cluster Members
Inherited from View Nodes
Additional settings (as per monitoring-ui-view):

[get] > "services/proxy"
[list] > "endpoints"

Describe the bug
After installing rancher-monitoring version 102.0.0+up40.1.2 our end users (with custom view only permissions using Rancher RBACs) can no longer see the metrics shown within Grafana. They can access the page, but the page displays a number of errors (see screenshots below).
To Reproduce

Login to Rancher as a restricted view-only user (permissions listed above)
Navigate the the Cluster in question
Select 'Monitoring' from the Menu, and select 'Grafana'
The screen will initially show a 404 (reported in a number of other tickets), but click the link to 'home dashboard'
The home screen will now display, but with a number of errors (see screenshots below)

Actual Result
Grafana displays no metrics, and 413 Forbidden is shown if viewing the Network Dev Tools (see screenshot below)
Expected Result
Grafana should display the metrics without error
Screenshots

Additional context
We have identified a workaround, but as this introduces a potential attack vector it is not a solution we want to entertain.
We can allow the Grafana dashboards to function by increasing the users permissions by updating the ClusterRole to:

[get,create] > "services/proxy"

This appears to be because the Grafana query is now a POST rather than a GET. But adding create permissions to all read-only users could allow them to create Kubernetes resources, which is a security risk.
There is no mention in any rancher documentation about needing to elevate levels to access Grafana.

I don´t know if I have a different issue or the same, but since I have upgraded to Rancher 2.7.5 and rancher-monitoring version 102.0.1+up40.1.2 Users with the roles Project Member and View Monitoring can no longer access grafana. Site is grayed out and not clickable.

Hi, any ideas about how to resolve this issue. I'm in the same situation using Rancher 2.7.9

You can see the current mitigation in the Downstream Cluster adjust ClusterRole “monitoring-ui-view” accordingly, however unfortunately gone again with the next upgrade of the monitoring HelmChart.

ClusterRole monitoring-ui-view
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  annotations:
    meta.helm.sh/release-name: rancher-monitoring
    meta.helm.sh/release-namespace: cattle-monitoring-system
  labels:
    app.kubernetes.io/instance: rancher-monitoring
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/part-of: rancher-monitoring
    app.kubernetes.io/version: 102.0.1_up40.1.2
    chart: rancher-monitoring-102.0.1_up40.1.2
    heritage: Helm
    release: rancher-monitoring
  name: monitoring-ui-view
rules:
- apiGroups:
  - ""
  resourceNames:
  - http:rancher-monitoring-prometheus:9090
  - https:rancher-monitoring-prometheus:9090
  - http:rancher-monitoring-alertmanager:9093
  - https:rancher-monitoring-alertmanager:9093
  - http:rancher-monitoring-grafana:80
  - https:rancher-monitoring-grafana:80
  resources:
  - services/proxy
  verbs:
  - get

>   - create            # Issue GH#2734

apiGroups:

""
resourceNames:
rancher-monitoring-prometheus
rancher-monitoring-alertmanager
rancher-monitoring-grafana
resources:
endpoints
verbs:
list
**> - apiGroups:          # Issue GH#42104
catalog.cattle.io
resources:
apps
verbs:
get**

You can edit the Cluster Role monitoring-ui-view in the downstream clusters. Afterwards it is working for me. Only drawback after running upgrade of Monitoring this change is gone

ClusterRole monitoring-ui-view
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  annotations:
    meta.helm.sh/release-name: rancher-monitoring
    meta.helm.sh/release-namespace: cattle-monitoring-system
  labels:
    app.kubernetes.io/instance: rancher-monitoring
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/part-of: rancher-monitoring
    app.kubernetes.io/version: 102.0.1_up40.1.2
    chart: rancher-monitoring-102.0.1_up40.1.2
    heritage: Helm
    release: rancher-monitoring
  name: monitoring-ui-view
rules:
- apiGroups:
  - ""
  resourceNames:
  - http:rancher-monitoring-prometheus:9090
  - https:rancher-monitoring-prometheus:9090
  - http:rancher-monitoring-alertmanager:9093
  - https:rancher-monitoring-alertmanager:9093
  - http:rancher-monitoring-grafana:80
  - https:rancher-monitoring-grafana:80
  resources:
  - services/proxy
  verbs:
  - get
  - create            # Issue GH#2734
- apiGroups:
  - ""
  resourceNames:
  - rancher-monitoring-prometheus
  - rancher-monitoring-alertmanager
  - rancher-monitoring-grafana
  resources:
  - endpoints
  verbs:
  - list
- apiGroups:          # Issue GH#42104
  - catalog.cattle.io
  resources:
  - apps
  verbs:
  - get

Hi
Created user (Project Member and View Monitoring):

Modified ClusterRole monitoring-ui-view in the downstream cluster, but in the same situation. Did you know if I'm doing in the right way or there is any mistake?:
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
annotations:
meta.helm.sh/release-name: rancher-monitoring
meta.helm.sh/release-namespace: cattle-monitoring-system
creationTimestamp: '2023-04-20T06:12:10Z'
labels:
app.kubernetes.io/instance: rancher-monitoring
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/part-of: rancher-monitoring
app.kubernetes.io/version: 102.0.2_up40.1.2
chart: rancher-monitoring-102.0.2_up40.1.2
heritage: Helm
release: rancher-monitoring
managedFields:
- apiVersion: rbac.authorization.k8s.io/v1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.: {}
f:meta.helm.sh/release-name: {}
f:meta.helm.sh/release-namespace: {}
f:labels:
.: {}
f:app.kubernetes.io/instance: {}
f:app.kubernetes.io/managed-by: {}
f:app.kubernetes.io/part-of: {}
f:app.kubernetes.io/version: {}
f:chart: {}
f:heritage: {}
f:release: {}
manager: helm
operation: Update
time: '2023-10-05T06:12:10Z'
- apiVersion: rbac.authorization.k8s.io/v1
fieldsType: FieldsV1
fieldsV1:
f:rules: {}
manager: agent
operation: Update
time: '2023-11-08T11:52:54Z'
name: monitoring-ui-view
resourceVersion: '134198420'
uid: cb72714a-a4e1-43f7-add1-48133c3f4a81
rules:

apiGroups:

'*'
resourceNames:
http:rancher-monitoring-prometheus:9090
https:rancher-monitoring-prometheus:9090
http:rancher-monitoring-alertmanager:9093
https:rancher-monitoring-alertmanager:9093
http:rancher-monitoring-grafana:80
https:rancher-monitoring-grafana:80
resources:
services/proxy
verbs:
get
create
list

apiGroups:

'*'
resourceNames:
rancher-monitoring-prometheus
rancher-monitoring-alertmanager
rancher-monitoring-grafana
resources:
endpoints
verbs:
get
list

apiGroups:

project.cattle.io
resources:
apps
verbs:
get

Thanks in advanced

You can edit the Cluster Role monitoring-ui-view in the downstream clusters. Afterwards it is working for me. Only drawback after running upgrade of Monitoring this change is gone

ClusterRole monitoring-ui-view
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  annotations:
    meta.helm.sh/release-name: rancher-monitoring
    meta.helm.sh/release-namespace: cattle-monitoring-system
  labels:
    app.kubernetes.io/instance: rancher-monitoring
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/part-of: rancher-monitoring
    app.kubernetes.io/version: 102.0.1_up40.1.2
    chart: rancher-monitoring-102.0.1_up40.1.2
    heritage: Helm
    release: rancher-monitoring
  name: monitoring-ui-view
rules:
- apiGroups:
  - ""
  resourceNames:
  - http:rancher-monitoring-prometheus:9090
  - https:rancher-monitoring-prometheus:9090
  - http:rancher-monitoring-alertmanager:9093
  - https:rancher-monitoring-alertmanager:9093
  - http:rancher-monitoring-grafana:80
  - https:rancher-monitoring-grafana:80
  resources:
  - services/proxy
  verbs:
  - get
  - create            # Issue GH#2734
- apiGroups:
  - ""
  resourceNames:
  - rancher-monitoring-prometheus
  - rancher-monitoring-alertmanager
  - rancher-monitoring-grafana
  resources:
  - endpoints
  verbs:
  - list
- apiGroups:          # Issue GH#42104
  - catalog.cattle.io
  resources:
  - apps
  verbs:
  - get

Hi
Created user (Project Member and View Monitoring):
Modified ClusterRole monitoring-ui-view in the downstream cluster, but in the same situation. Did you know if I'm doing in the right way or there is any mistake?:
apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: annotations: meta.helm.sh/release-name: rancher-monitoring meta.helm.sh/release-namespace: cattle-monitoring-system creationTimestamp: '2023-04-20T06:12:10Z' labels: app.kubernetes.io/instance: rancher-monitoring app.kubernetes.io/managed-by: Helm app.kubernetes.io/part-of: rancher-monitoring app.kubernetes.io/version: 102.0.2_up40.1.2 chart: rancher-monitoring-102.0.2_up40.1.2 heritage: Helm release: rancher-monitoring managedFields: - apiVersion: rbac.authorization.k8s.io/v1 fieldsType: FieldsV1 fieldsV1: f:metadata: f:annotations: .: {} f:meta.helm.sh/release-name: {} f:meta.helm.sh/release-namespace: {} f:labels: .: {} f:app.kubernetes.io/instance: {} f:app.kubernetes.io/managed-by: {} f:app.kubernetes.io/part-of: {} f:app.kubernetes.io/version: {} f💹 {} f:heritage: {} f:release: {} manager: helm operation: Update time: '2023-10-05T06:12:10Z' - apiVersion: rbac.authorization.k8s.io/v1 fieldsType: FieldsV1 fieldsV1: f:rules: {} manager: agent operation: Update time: '2023-11-08T11:52:54Z' name: monitoring-ui-view resourceVersion: '134198420' uid: cb72714a-a4e1-43f7-add1-48133c3f4a81 rules:

apiGroups:

'*'
resourceNames:
http:rancher-monitoring-prometheus:9090
https:rancher-monitoring-prometheus:9090
http:rancher-monitoring-alertmanager:9093
https:rancher-monitoring-alertmanager:9093
http:rancher-monitoring-grafana:80
https:rancher-monitoring-grafana:80
resources:
services/proxy
verbs:
get
create
list

apiGroups:

'*'
resourceNames:
rancher-monitoring-prometheus
rancher-monitoring-alertmanager
rancher-monitoring-grafana
resources:
endpoints
verbs:
get
list

apiGroups:

project.cattle.io
resources:
apps
verbs:
get

Thanks in advanced

That´s the only difference I find to my configuration. Perhpas that helps
* apiGroups:
  **- project.catalog.cattle.io -->catalog.cattle.io**
  resources:

  * apps
    verbs:
  * get

Ups, I changed to "catalog.cattle.io" but still not working :-(


Whether rocketmq need to authenticate from mysql? I want pull a request

My company has such a requirement that the client needs to use a different username and password to consume different queues. If rocketmq need it, I intend to contribute these functions to rocketmq.

Could you detail the concrete credential need in email http://rocketmq.apache.org/about/contact/.


Build scripts ignore GFlags version installed locally

Standard approach to build the third party dependencies: make third_party does not check if a different GFlags version is available in the system. Currently the version 2.2 of the library is always downloaded and linked statically.
This approach causes linking problems when or-tools is used as a library to build a project that has its own dependency on GFlags.

Agreed. A hard problem though.
You can tweak the makefiles to use the system one:

delete the gflags libs and  includes in dependencies/install
change the LNK libraries in Makefile.{unix|win} not to link to the one
in dependencies.

Longer term, we will switch to cmake all around. But this is a bit fragile
at the time being.
Thanks
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
2017-10-21 12:37 GMT+00:00 pmateusz<EMAIL_ADDRESS>
Standard approach to build the third party dependencies: make third_party
does not check if a different GFlags version is available in the system.
Currently the version 2.2 of the library is always downloaded and linked
statically.
This approach causes linking problems when or-tools is used as a library
to build a project that has its own dependency on GFlags.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/507, or mute the thread
https://github.com/notifications/unsubscribe-auth/AKj17aQ9G_EhsGooZpbOZfUDBoEZeaOQks5sueV-gaJpZM4QBjN6
.

If you want to incorporate OR-Tools C++ in a existing project, I would suggest to use the CMake Support of OR-Tools.
note: currently CMake OR-Tools will also download all its dependencies if external targets are not defined cf https://github.com/google/or-tools/blob/master/cmake/external/CMakeLists.txt.
So if in your meta cmake you already integrate gflags::gflags then OR-Tools will use it.
I also would like to add an option to use find_package() instead of recompiling deps but in this case we have to test against any supported distro that their dependencies provided version work with OR-Tools...


Update Gentoo Latest template for Stage3 date 20170504

Updates the template for gentoo_latest to work with the latest Stage3, dated 20170504.
Changes include:

Corrections for allow SSHD from the boot medium.
Install kernel 4.9.16
Corrections for install Grub
There's also also some additional, optional, logic to make repeated attempts to get a successful automated build faster.

In regards to this last point, Gentoo requires 3 big files:

The bootable ISO
A stage3 tar file
The portage tree

Even though they are each only a few hundred MB, I find these all to be very slow to download (upwards of 1 hour each.)  Veewee saves some time by pre-downloading the ISO, but the Stage3 and Portage tree still adds a lot of time.
I'm not a Ruby programmer, so I hobbled together a strategy where I manuall download Stage3 and Portage and package them in a single TAR and then use a veewee hook to transfer to the virtual machine.  The script will extract and use these files if they exists.
I'm sure there would be a smarter strategy to achieve this, but I don't have the background in Ruby to see how. I'm open to suggestions if there is concerns about accepting this PR with this logic.  Or I can remove it and save it for myself.

I approve. Should I just merge PRs like this on my own or wait for your opinion, @mpapis?

@FunTimeCoding if it looks good just merge :)


HIVE-26268: Upgrade Snappy to <IP_ADDRESS>

What changes were proposed in this pull request?
Upgrade Snappy Java lib
Why are the changes needed?
To be able to run build and tests locally on macOS M1 (aarm64)
Does this PR introduce any user-facing change?
How was this patch tested?
locally

replaces #1513


python3Packages.bsblan: init at 0.4.1

Motivation for this change
Python client for BSB-Lan.
https://github.com/liudger/python-bsblan
This is a Home Assistant dependency.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110453 run on x86_64-linux 1

6 packages built:

python37Packages.bsblan
python37Packages.cattrs
python38Packages.bsblan
python38Packages.cattrs
python39Packages.bsblan
python39Packages.cattrs

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110453 run on x86_64-linux 1

6 packages built:

python37Packages.bsblan
python37Packages.cattrs
python38Packages.bsblan
python38Packages.cattrs
python39Packages.bsblan
python39Packages.cattrs


Add voluptuous config validation to scenes

Description:

Add platform schema to scene component and homeassistant platform.
Clean up code and add constants.
Add unit test and clean up tests.

Related issue (if applicable):
fixes #6641, closes #6815
Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Nice! 🐬

I had some time to try this out and so far it works perfectly. Scenes within packages get merged! Thanks a lot :)


[CCXDEV-6982] Check category labels in recommendation page

Add test for category labels
Set base for other test of single recommendation page. Follow up https://issues.redhat.com/browse/CCXDEV-8415

CCXDEV-6982

Codecov Report

Merging #313 (0ab058c) into master (206701f) will decrease coverage by 5.39%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #313      +/-   ##
==========================================
- Coverage   85.14%   79.75%   -5.40%
==========================================
  Files          24       26       +2
  Lines         983     1126     +143
  Branches      366      427      +61
==========================================
+ Hits          837      898      +61
- Misses        146      228      +82

Impacted Files
Coverage Δ

src/Components/MessageState/MessageState.js
100.00% <100.00%> (ø)

src/Components/Recommendation/Recommendation.js
54.20% <0.00%> (ø)

src/Components/Modals/ViewHostAcks.js
8.33% <0.00%> (ø)

Continue to review full report at Codecov.

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

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


Add options to handle invalid documents

Resolves #188

Hey, @ShaunBulbrook!
I've made a few changes, and would like a little sanity check before I do a release of the new features.
Could you take a look at the changes and see that it makes sense, or if I'm missing something?

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added s3 tests and docker-compose example

Had to move csvs to datadir to get minio to find them. this might still affect the benchmarks!

Thanks, @jhnnsrs ! Looks good to me!


Add logging in case type inference fails.

Release note:

release-note-none

This change is

@mandarjog friendly ping

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-e2e-smoketest.sh
78e51720c90068a678f01b1d4eea67a3eb60cf22
link
/test mixer-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@mandarjog @douglas-reid @ZackButcher  Friendly ping. I think without this PR our logs don't show if the attribute is invalid and eval of it failed.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-e2e-smoketest.sh
28e0745253bf4f6f24a8ac735f93e39a96e0d1dc
link
/test mixer-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-e2e-smoketest.sh
28e0745253bf4f6f24a8ac735f93e39a96e0d1dc
link
/test mixer-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/lgtm

/retest

Codecov Report

Merging #1266 into master will increase coverage by 1.63%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1266      +/-   ##
==========================================
+ Coverage   83.35%   84.98%   +1.63%
==========================================
  Files         124      129       +5
  Lines       12098    13251    +1153
==========================================
+ Hits        10084    11262    +1178
+ Misses       1803     1779      -24
+ Partials      211      210       -1

Impacted Files
Coverage Δ

pkg/runtime/handler.go
89.92% <100%> (+0.07%)
:arrow_up:

pkg/attribute/emptyBag.go
75% <0%> (-25%)
:arrow_down:

pkg/attribute/protoBag.go
92.53% <0%> (-6.43%)
:arrow_down:

pkg/attribute/mutableBag.go
92.47% <0%> (-5.53%)
:arrow_down:

pkg/runtime/resolver.go
96.05% <0%> (-3.95%)
:arrow_down:

pkg/config/store/convert.go
96.96% <0%> (-3.04%)
:arrow_down:

pkg/runtime/controller.go
96.9% <0%> (-1.03%)
:arrow_down:

adapter/stdio/stdio.go
99.46% <0%> (-0.54%)
:arrow_down:

pkg/config/inventory.go
0% <0%> (ø)
:arrow_up:

cmd/server/cmd/test_server.go
0% <0%> (ø)
:arrow_up:

... and 29 more

Continue to review full report at Codecov.

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


fix: Prevent app stalling on update

[X] I did all of the following:

search for a solution in the discussions
search for duplicate or closed issues
read the bug report contributing guidelines

Describe the bug
After a new update of the app has been published, visiting the app in a browser or from an iOS WebClip results in the app only showing the loading animation forever.
Steps to reproduce

Publish a new app version
Open the app, likely requiring a  previous version to be already cached
Observe the loading animation forever

Expected behavior
The app should instead proceed to show the home page (or the get instructions animation for the first 5 visits)
Environment

Device: iPhone, Mac, PC
OS: iOS 15, MacOS Big Sur, Ubuntu 20.04
Browser Chrome, Safari, WebClip

Additional context
Safari console error message:
[Error] SyntaxError: Unexpected token '<'
	(anonymous function) (chunk-vendors.cef59a30.js:1)

Network log:
Summary
URL: https://xn--p8st22e.com/js/chunk-vendors.cef59a30.js
URL: https://xn--p8st22e.com/js/chunk-vendors.cef59a30.js/
Status: 304
Source: Memory Cache
Address: <IP_ADDRESS>:443

Request
GET /js/chunk-vendors.cef59a30.js
Accept: */*
Referer: https://xn--p8st22e.com/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15
If-Modified-Since: Thu, 02 Dec 2021 11:03:17 GMT
If-None-Match: W/"cb99fd2a7f8431256aea4de614415b96"

Redirect Response
301
Location: /js/chunk-vendors.cef59a30.js/
Date: Thu, 02 Dec 2021 12:16:47 GMT

Request
:method: GET
:scheme: https
:authority: xn--p8st22e.com
:path: /js/chunk-vendors.cef59a30.js/
Accept: */*
Accept-Encoding: gzip, deflate, br
If-None-Match: W/"cb99fd2a7f8431256aea4de614415b96"
Host: xn--p8st22e.com
If-Modified-Since: Thu, 02 Dec 2021 11:03:17 GMT
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15
Accept-Language: en-GB,en;q=0.9
Referer: https://xn--p8st22e.com/
Connection: keep-alive

Response
:status: 304
Cache-Control: public, max-age=0, s-maxage=2
Last-Modified: Thu, 02 Dec 2021 11:03:17 GMT
Via: 1.1 60f2c4b6c07455537be83f75f12576e8.cloudfront.net (CloudFront)
Date: Thu, 02 Dec 2021 12:16:49 GMT
ETag: W/"cb99fd2a7f8431256aea4de614415b96"
Vary: Accept-Encoding
Server: AmazonS3
x-cache: Miss from cloudfront
x-amz-cf-pop: ARN1-C1
x-amz-server-side-encryption: AES256
x-amz-cf-id: zhEJStsxJYNiZ6oPgsWK8vLQTX-7qWlBRfyngTja_6WvrSqP0_c6og==

Seems to resolve itself after a delayed reload.

Probably related to Amplify configuration.


Add Proxy Interface

Client interface.

Provides a "virtual class" which access remote methods, properties, and signals.

If properties support signals cache values and only update on incoming signals.
If Object Manager update when new Objects added.
Provide a Tree View, including all Nodes
Not sure how to handle Interface names for Properties, Methods, and Signals, there isn't a clean equivalent in Python,


UUID confusion?

ble.cmd_set_le_advertising_data(create_advertising_data(&[
            AdStructure::Flags(LE_GENERAL_DISCOVERABLE | BR_EDR_NOT_SUPPORTED),
            AdStructure::ServiceUuids16(&[Uuid::Uuid16(0x1809)]),
            AdStructure::CompleteLocalName("BLE_TO_ISOTP"),
        ])).unwrap();

could you help explain AdStructure::ServiceUuids16(&[Uuid::Uuid16(0x1809)]),
versus
gatt!([service {
            uuid: "0000abf0-0000-1000-8000-00805f9b34fb", // SPP_SERVICE
            characteristics: [
                characteristic {
                    uuid: "0000abf2-0000-1000-8000-00805f9b34fb", // DATA_NOTIFY
                    read: rf,
                },
                characteristic {
                    uuid: "0000abf3-0000-1000-8000-00805f9b34fb", // COMMAND_WRITE
                    write: wf,
                },
            ],
        },]);

is the service UUID duplicated?

The advertising data is just what the device announces and the gatt! macro is what the central device will get during discovery.
e.g. 0x1809 is HEALTH_THERMOMETER_SERVICE but the example doesn't really have that service. It's unusual but it's just a simple example here

does the 0x1809 HEALTH_THERMOMETER_SERVICE need to match the service UUID used in the gatt! macro?

Technically it doesn't need to match. The advertising data is what a device "sees" when scanning for BLE devices while the services it will see during discovery (i.e. when it connects to the device) might be different ones.
Also, the amount of data you can fit into the advertising packet is limited. If you control both ends of the communication you can use whatever works for you for the advertising data. If you don't control the BLE central device then you need to know what the central device is looking for to match that


Upload update alertaccordion

Description
update AlertAccordion to use czifui StyledAlert
Issue
no issue
Test plan
Write how your changes are tested, or give a convincing reason why they can't be tested automatically.

PTAL updated czifui PR 🙏 https://github.com/chanzuckerberg/sci-components/pull/29
And proof that it works in this PR!

Thanks so much!!

thank you Timmy!!! 🥇


Fix all Psalm errors at level 6 or above

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 71.14%. Comparing base (dc2548d) to head (7c2e87a).

Additional details and impacted files
@@              Coverage Diff              @@
##             develop     #140      +/-   ##
=============================================
- Coverage      71.17%   71.14%   -0.04%
+ Complexity       238      237       -1
=============================================
  Files             38       38
  Lines            902      901       -1
=============================================
- Hits             642      641       -1
  Misses           260      260

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[CSS Anchored Positioning] Does the anchor IDL attribute reflect to the content attribute?

The anchor positioning proposal contains this proposed syntax:
document.getElementById('myPopup').anchor = document.getElementById('myButton');

Quick question: when you execute that line on <popup id=myPopup>, do you get <popup id=myPopup anchor=myButton>? What if you instead assign anchor to document.createElement('button'), which doesn't have an id?

Hmm, maybe we should just change the syntax to Element.setAttribute('anchor', 'someIdHere'); and the usual behavior + processing of IDREFs occurs. WDYT, @BoCupp-Microsoft?

Hmm, maybe we should just change the syntax to Element.setAttribute('anchor', 'someIdHere'); and the usual behavior + processing of IDREFs occurs. WDYT, @BoCupp-Microsoft?

I like that approach. It cuts off a number of potential issues. Like another one I just thought of:
const myButton = document.getElementById('myButton');
const myPopup = document.getElementById('myPopup');
myPopup.anchor = myButton;
myButton.id = 'something-else';
myPopup.getAttribute('anchor'); // myButton? something-else?
myPopup.anchor; // null? still myButton?


Write a coding style guide

Write down all conventional rules we want to agree on

use types instead of typing helpers (Tuple -> tuple)
only simple quotes
... ?

Thank you for that 😍 I have tracked most of them in a dirty note, I'll tidy it up.

In our discussions, let's refrain from relying solely on subjective arguments, as their value lies solely in the opinions of the individuals expressing them. General statements such as "I don't like it," "it's odd," or "it's simpler" lack the specificity needed to advance the debate. Instead, let's articulate our concerns by providing concrete reasons:

"I don't like it because [it's slow/lengthy/error-prone/...]"
"It's odd because in X/Y library, they follow a different approach."
"It's simpler" ➡ "It will prevent errors" / "It requires fewer steps."

By identifying specific points of concern, we can effectively address and evaluate them, either leading to the modification or abandonment of proposed solutions based on well-founded reasons. This approach will enable us to make informed decisions and make progress in our discussions.

See https://linear.app/dynamiqs/issue/DYN-86/write-a-coding-style-guide.


Which time ratios are supported?

Hey, I see that in inference image by default you use powers of 2 for interpolation, but also support passing arbitrary "ratio". I'm trying to understand how RIFE is being trained and what are the actual possible inference timestamps.
Do you use random [0, 1] during training or only use powers of 2 as possible options? If powers of 2, what is the largest i can use? The reason i ask is because generally models don't work well for values outside of their training domain, so i'm being very cautious here

During training, I will randomly select three frames from 1-9. For example, if I select 1 5 8, then time=0.571.


Goals of the Kinematics Model

We should put into the world our actual goals for the kinematics model.

What should it be able to do?

Kinematic equations?
Expand to include a more generalized equations of motions?

Best approach for implementing our goals?

First step will be to just write some code that can answer basic kinematic questions. Here are 20 questions that if we have different functions or some kind of foundation to answer these questions we will have a great place to expand from later.

Okay! I think I've gotten started a good base for the kinematics model to continue to grow from. It now has included basic kinematic equations solving for a couple of final conditions based on initial conditions. The accepted initial conditions are limited currently and the final outputs reflect that. A goal will be to expand what we can solve for and what we might have been given.


vite_ssr_import_meta.hot.send is not a function

UnoCSS version
unocss nuxt 0.51.4
Describe the bug
starting histoire with unocss nuxt throws this error.
Histoire version: 0.16.1
https://github.com/unocss/unocss/issues/1823 seems to be an equal problem, bit is marked as closed
Reproduction
https://github.com/sfxcode/nuxt3-primevue-starter
System Info

Operating System: Darwin
Node Version:     v18.15.0
Nuxt Version:     3.4.1
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      devtools, ssr, runtimeConfig, modules, content, unocss, primevue, css, pinia, build, sourcemap
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Fixed in https://github.com/vitest-dev/vitest/commit/b1624db5d3baf26f7e1c69b23cf4c1335562ccde


Please merge revision e121d95b1b168a50942a874d66247a3ff72ff892 into dev channel

@whesse @mit-mit @kasperl
Merge fix for strong mode type inference regression when mixing upwards and downwards information on map literals: https://github.com/dart-lang/sdk/issues/29231 .
Please merge e121d95b1b168a50942a874d66247a3ff72ff892 to dev.
This merges cleanly, and analyzer tests pass.

cc @vsmenon

Merged in 1.23.0-dev.11.4


add changelog for 1.18.0-rc1

Missing #21410?

#21381
#21550
#21554 (not sure why it has the skip-changelog label)

its about a month ago that RC.0 was released, given that its out now quite a while compared to previous released, is it not possible to make it 1.18 stable and if not, what is missing to make it a stable release?

All bug fixes has been backport to v1.17 or the bug affected by a feature which introduced in the same release should be ignored.

#21554 makes more sense for changelog than #21533

#21554 makes more sense for changelog than #21533

Done.

make L-G-T-M work

Important! #20153 is breaking, very breaking!

Important! #20153 is breaking, very breaking!

Strange, it's labeled breaking, not sure why it wasn't put in the right section.


06 2024 update

trying to update the site to have the past 2 years of bells and whistles

woops, meant to pr my own repo


[skrifa] floating point COLR

Internal interface for color outline loading in full floating point.
This copies ColrInstance & co from read-fonts to skrifa and updates it to process all values/deltas in floating point. Additionally, adds methods to ItemVariationStore to compute scalars/deltas in floating point. It's f32 all the way down.
This doesn't remove the code in read-fonts and also contains a module for printing the paint graph so it's not ready to merge.
Printing the graph for a glyph:
use skrifa::prelude::*;
use skrifa::raw::TableProvider;

let font_data = std::fs::read("/path/to/colrv1font.ttf").unwrap();
let font = FontRef::new(&font_data).unwrap();
let colr = font.colr().unwrap();
let coords = [NormalizedCoord::from_f32(-0.6021); 64];
skrifa::scale::print_color_glyph(&colr, GlyphId::new(94), LocationRef::new(&coords));

For the COLRv1 test font, glyph 94 (radial_horizontal_gradient_extend_mode_pad) with all coords set to -0.6021 loads as follows with skrifa maintaining fractional values from deltas:
freetype:
Glyph 2
    RadialGradient p0: (-202.000000,-102.000000) r0: -502.000000 p1: (98.000000,-102.000000) r1: -402.000000 extend: Pad stops: (-1.204224 3 1.000000), (-0.704224 9 1.000000), (-0.204224 0 1.000000)

skrifa:
Glyph GID_2
    RadialGradient p0: (-202.11182,-102.11182) r0: -502.11182 p1: (97.88818,-102.11182) r1: -402.11182 extend: Pad stops: (-1.2042236 3 1), (-0.70422363 9 1), (-0.20422363 0 1)

Thanks for this - the fact that FreeType returns rounded values is the bug in FreeType at the moment that @tursunova is in the process of fixing  - so it's a bit hard to tell how war the fixed computation would be off.  I am a bit concerned about the code duplication - if it's COLR related, could we perhaps shift read_fonts to do this in floats right away? I don't think we have a huge legacy there from FreeType (rather, we have bugs that we need to fix, like https://bugs.chromium.org/p/chromium/issues/detail?id=1473020

I am also curious to see how the issue will be resolved in FreeType and how big the diffs might be.
re duplication: if we go this route, my intent was to just remove this functionality from read-fonts. I think your new ColorPainter code does a better job of providing a nice semantic model of a paint graph. For people wanting low level access, that would still be available from our codegen'd types in read-fonts.

Can we close this, is this superceded by #725?


Remove broken links

Those repo links are broken as the callsmusis org no longer exists

They're not broken. Calls Music org still exists. It's just hidden from public atm.

They're not broken. Calls Music org still exists. It's just hidden from public atm.

But links doesn’t work for me too…

@MarshalX maybe you can give us some time, we might move to GitLab soon.
Also, you might change the links to these (temporarily): https://t.me/CallsMusicUpdates/48

#35

fixed in #35, thanks


Touch through transparent areas of svg

I'm trying to implement tutorial view which will focus user attention on certain elements, like on this screenshot:

This is fullscreen overlay View with absolute position and svg inside it. Other elements (text with description and dismiss button) should be placed inside this view above svg. Only touches inside the 'hole' should pass through to underlying views.
This is how my code looks like:
<View style={styles.overlay} pointerEvents="box-none">
  <Svg width={width} height={height}>
    <Defs>
      <ClipPath id="clip">
        <G>
          <Rect width="100%" height="100%" />
          <Circle cx={this._cx} cy={this._cy} r={this._radius} />
        </G>
      </ClipPath>
    </Defs>
    <Rect
      onPress={() => console.log('Press')}
      width="100%"
      height="100%"
      fill="rgba(255, 0, 0, 0.5)"
      clipPath="url(#clip)"
      clipRule="evenodd"
    />
  </Svg>
</View>

onPress works as expected, logs to console when I press on red area and does nothing when I press inside the hole. The problem is that underlying view does not receive touch events.
I checked react-native-svg android sources and it seems that there is no easy way to fix this. ViewGroup that contains SvgView determines if view should receive touch event based its bounds, so SvgView will always consume touch event.
Am I wrong? Any ideas on how this can be done?

I'm also interested in this..

try messing around with pointerEvents. you might need to create multiple  elements wrapped in 's

Use the gesture responder system and the grant/responder termination request logic https://facebook.github.io/react-native/docs/gesture-responder-system.html


Failing to run/launch D435i while D435 works fine

Required Info

Camera Model
D435i

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 22

Kernel Version (Linux Only)
5.15.136-tegra

Platform
NVIDIA Jetson

SDK Version
v2.55.1

Issue Description
Within docker on an NVIDIA Jetson Orin NX with realsense packages installed
RealSense ROS v4.55.1
Built with LibRealSense v2.55.1
When connecting a D435 camera with firmware version <IP_ADDRESS> and running either
ros2 run realsense2_camera realsense2_camera_node / ros2 launch realsense2_camera rs_launch.py
the node runs/launches correctly without issue.
However, when doing the same thing with a D435i with the same firmware version connected, I get the following error:
[INFO] [1723966735.515221692] [camera.camera]: RealSense ROS v4.55.1
[INFO] [1723966735.515402496] [camera.camera]: Built with LibRealSense v2.55.1
[INFO] [1723966735.515435521] [camera.camera]: Running with LibRealSense v2.55.1
 18/08 10:38:55,537 ERROR [281473072294112] (librealsense-exception.h:52) xioctl(VIDIOC_S_EXT_CTRLS) failed Last Error: Invalid argument
 18/08 10:38:55,537 ERROR [281473072294112] (rs.cpp:237) [rs2_create_device( info_list:0xffff800112e0, index:0 ) Backend] xioctl(VIDIOC_S_EXT_CTRLS) failed Last Error: Invalid argument
 18/08 10:38:55,538 ERROR [281473072294112] (rs.cpp:237) [rs2_delete_device( device:nullptr ) UNKNOWN] null pointer passed for argument "device"
 18/08 10:38:55,538 WARNING [281473072294112] (rs.cpp:373) null pointer passed for argument "device"
[WARN] [1723966735.538083617] [camera.camera]: Device 1/1 failed with exception: xioctl(VIDIOC_S_EXT_CTRLS) failed Last Error: Invalid argument
[ERROR] [1723966735.538194724] [camera.camera]: The requested device with  is NOT found. Will Try again.

Runninng rs_enumerate_devices also errors:
 18/08 10:39:50,003 ERROR [281472868743808] (librealsense-exception.h:52) xioctl(VIDIOC_S_EXT_CTRLS) failed Last Error: Invalid argument
 18/08 10:39:50,004 ERROR [281472868743808] (rs.cpp:237) [rs2_create_device( info_list:0xaaaaf327d4f0, index:0 ) Backend] xioctl(VIDIOC_S_EXT_CTRLS) failed Last Error: Invalid argument
 18/08 10:39:50,004 ERROR [281472868743808] (rs.cpp:237) [rs2_delete_device( device:nullptr ) UNKNOWN] null pointer passed for argument "device"
Could not create device - xioctl(VIDIOC_S_EXT_CTRLS) failed Last Error: Invalid argument . Check SDK logs for details
No device detected. Is it plugged in?

Hi @akupferb  Are you using JetPack 6 on your Jetson, please?  If you are then the MIPI driver at the link below needs to be installed in order to add support for HID devices (RealSense cameras equipped with an IMU).  This is because JP6 does not support hidraw.
https://github.com/IntelRealSense/realsense_mipi_platform_driver
If you are using JP6 and are able to downgrade your JetPack, using JetPack 5.13 should resolve the issue.
If you need to use JP6 then an alternative solution that avoids the need to install the MIPI driver is to install the librealsense SDK with a build script using the libuvc backend procedure at the link below.
https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md

Thanks for the quick response!
I am indeed using Jetpack 6 as a requirement for my system and cannot downgrade, so I will try out the SDK installation from source with libuvc backend to see if that solves it
Thanks

I first purged my instances of realsense packages for a clean install of the SDK using dpkg -l | grep "realsense" | cut -d " " -f 3 | xargs sudo dpkg --purge and then ran the install commands for the libuvc_installation.
After the installation was completed successfully, running rs-enumerate-devices outputs the following:
$ rs-enumerate-devices
 18/08 12:03:39,516 ERROR [281473118367968] (handle-libusb.h:53) failed to open usb interface: 0, error: RS2_USB_STATUS_NO_DEVICE
 18/08 12:03:39,517 ERROR [281473159297632] (uvc-sensor.cpp:412) acquire_power failed: failed to set power state
 18/08 12:03:39,517 ERROR [281473159297632] (rs.cpp:237) [rs2_create_device( info_list:0xaaab0f2cfdb0, index:0 ) UNKNOWN] failed to set power state
 18/08 12:03:39,517 ERROR [281473159297632] (rs.cpp:237) [rs2_delete_device( device:nullptr ) UNKNOWN] null pointer passed for argument "device"
Could not create device - failed to set power state . Check SDK logs for details

This occurred for both my D435 and D435i...
As the debian install of the Realsense ROS wrapper (ros-humble-realsense2_camera...) has a dependency on 'ros-humble-librealsense2', I re-installed the wrapper from source and made sure to build and source it, but that did not help.

If you are accessing the camera within a Docker container, have you tried launching Docker in sudo admin permissions mode with sudo docker run and including the --privileged flag?  For example:
sudo docker run -it --rm  --privileged -v $HOME/.ros:/root/.ros

I am already running the Docker container with sudo permissions and using --privileged.
I will check out the other solution of installing the MIPI driver...

@MartyG-RealSense Is there a method to complete the MIPI driver installation from this page's instructions without have the "RealSense De-Serialize board" to connect the camera?
Can the Enable d4xx overlay: step be accomplished while the camera is plugged in using a regular USB 3?  The "jetson-io" interface only utilizes the pin connectors and M.2 slot...

Note also that I am using a Jetson Orin NX, not the Jetson AGX Xavier...

Thanks for the explanation. I fill follow up on their page.


One user can use other user's generated access token and invoke the resource.

Description:
Assume we have two users, userA and userB, assigned to 'Accounts' role. 'Accounts' role is configured with scope:search_user. UserA's access token can be used by UserB and invoke the resource.
Suggested Labels:
Type/Bug
Severity/Major
Priority/High
Affected/apim-2.1.0 update 6
Suggested Assignees:
N/A
Affected Product Version:
apim-2.1.0 update 6
OS, DB, other environment details and versions:
OS: macOS high sierra
Steps to reproduce:

Login to carbon console and create a role called Accounts and assign userA and userB to it.
Login to Publisher, create an API.
Edit the API, add a scope and assign the above-created role Accounts and assign it to a resource.
Publish the API.
Now login to Store as userA and create an application. App-A
Subscribe the API from App-A and generate the access token as below in order to invoke the resource.
curl -k -d "grant_type=password&username=userA&password=Test123&scope=search_user" -H "Authorization: Basic R1ROZ1dOZldQbGZJZGhmU1phaXlOeEF3MWVzYTpKVVNQeXBRaDk1cXo3V1I3bW1oczVpME0xcE1h"  -H "Content-Type: application/x-www-form-urlencoded" https://localhost:8243/token
Try to invoke the resource and it will be invoked successfully.
Now login as userB and perform 5-6 steps.
Now invoke the resource by using the access token of userA.

Expected: userB should not be able to invoke the resource using userA's access token.
Actual: Resource is invoked successfully.

This working as expected


Add sample code for "Combining Validators and Transformers in NestJS"

Disregard this pull request, please.


Prevent Select onValueChange from firing on init

I have onValueChange on the Select.Root so I can monitor when a Select's value has changed, much like a native Select HTML element. The issue is, that it fires when the component is mounted.
<Select.Root onValueChange={handleChange} bind:value={itemId}>

My solution was to check whether the initial value  that is bound was the same as the "changed" value, and return if it is.
let itemId;

function handleChange(id: string) {
    if (id === itemId) return;
    ....
}

It would be great if the Select onValueChange did not call when mounted.

+1 Ohh this is bothering me too, great that you confirmed this!
I am using raw melt-ui though, that would need to be fixed there I assume.

@mcmxcdev , I believe I know why this is happening, if you wouldn't mind opening an issue on Melt explaining some situations that you've run into this, it would be incredible!

I believe I may have fixed this, can you confirm using the latest version of bits-ui?

I believe I may have fixed this, can you confirm using the latest version of bits-ui?

It seems to work but...it's not liking the new prop: selected.
Type 'string' is not assignable to type 'SelectOption<unknown>'
I am just passing a Store with a string in it.
Also, should it be onSelectChange instead of onSelectedChange to match melt-ui?

Yeah it should be onSelectedChange I will make that fix! So SelectOption looks like this:
type SelectOption<T> = {
	value: T;
    label?: string
}

So you'd need to set the value to that string!

I was wondering, is the default value that displays in the Select  always supposed to be the placeholder, even if the selected value matches one of the Options? This seems to go against the native Select behavior, but I wasn't sure if this was intentional or not.
As an example...
If the user has the value "apple"  value already selected when loading the page, one would assume the Select shows this:

But it's actually showing...

I think that was also an issue I had with Select, the label was not synced up with the value.

Also, on another note, is there a reason why we need to pass:
type SelectOption<T> = {
	value: T;
    label?: string
}

to the selected prop, as opposed to just a string value?
This seems odd to me because

What purpose would the label serve in this situation?
It strays away from the native Select where you just pass a straight value.

It's not a huge deal but  it does (unless I am missing an easy way), prevent me from binding selected to a single writable store String, since it is now an object.
I'm sure there could be reasons for this so I don't want to sound rude!

On a possibly related note, <Select.Input name="favoriteFruit" /> doesn't appear to work, the value of the hidden input field is set to "[object Object]". It used to be set to the option.value automatically.

Also having this issue atm with Superforms. If anyone has a solution that would be pretty cool in the meantime.

I think that was also an issue I had with Select, the label was not synced up with the value.

I found the answer to this. Basically whatever the selected label is:
type SelectOption<T> = {
	value: T;
    label?: string
}

will show up as the default label (even if the value is set to the correct associated item.
If there is no label property present for selected, it will default to the Select.Trigger Select.Value placeholder value.

^ @saturnonearth that is correct. We had issues with SSR & attempting to keep the select label/value combo in sync, especially when you're conditionally rendering the options under an {#if open} (which we're doing in bits to support transitions).
I'm working on trying to fix the issues you all are experiencing though!

Yeah it should be onSelectedChange I will make that fix! So SelectOption looks like this:
type SelectOption<T> = {
	value: T;
    label?: string
}

So you'd need to set the value to that string!

I don't get typing for the SelectOption in my onSelectedChange function.
(property) selected?: SelectOption<unknown> | undefined
I'm doing something like this to make a select component that I can reuse in my app, built on the blocks that shadcn gives me. Which in turn uses bits ui.
<script lang="ts">
	import * as Select from '$components/ui/select';
	import type { SelectOption } from '@melt-ui/svelte';
	import type { OnChangeFn } from 'bits-ui/dist/internal';

	export let data: Record<string, string>[];
	export let inputName: string;
	export let onSelectedChange: OnChangeFn<SelectOption<any> | undefined> | undefined;

	export let defaultSelected: SelectOption<string>;
</script>

<Select.Root
	selected={{ value: defaultSelected.value, label: defaultSelected.label }}
	{onSelectedChange}
>
	<Select.Trigger class="w-[180px]">
		<Select.Value />
	</Select.Trigger>
	<Select.Content>
		{#each data as { value, label }}
			<Select.Item {value} {label}>{label}</Select.Item>
		{/each}
	</Select.Content>
	<Select.Input name={inputName} />
</Select.Root>

The select primitive from shadcn
<script lang="ts">
	import { Select as SelectPrimitive } from 'bits-ui';

	type $$Props = SelectPrimitive.Props;

	export let selected: $$Props['selected'] = undefined;
	export let open: $$Props['open'] = undefined;
</script>

<SelectPrimitive.Root bind:selected bind:open {...$$restProps}>
	<slot />
</SelectPrimitive.Root>

Atm it's set to any, but I'd like it to set to the type of the selected. If I understand correctly that should be the case. I'm using bits and shadcn.
export let onSelectedChange: OnChangeFn<SelectOption<any> | undefined> | undefined;

Closed by #184


Crew search examples are not mobile friendly

The main page (crew search) has a list of example search filters, which is shown on a mouse hover on desktop. None of this is user friendly on mobile devices.
In portrait mode the question mark is not displayed at all:

In landscape mode one can see the question mark and tapping on it makes the information stick around, but most of it lies outside of the screen and can't be scrolled to:

Would it break the flow to add a button which opens a modal with the information?

I think modal is the right call here - although you may want to go with tooltip for desktop/large width devices, and modal for mobile/small width devices.

Also modal formatting is kind of miserable by default, I am not at all happy with the one I made on the player tools upload page. So you may need to spend a bit of time tweaking.