switch to core and pin

I think you need to specify at least some extras, otherwise it doesn't install anything?
extras = {
# Core
"required": ["numpy>=1.11.1", "scipy>=0.18.1", "pandas>=0.19.2", sklearn_dep],
"debug": ["psutil>=5.6.2"],
"notebook": ["ipykernel>=5.1.0", "ipython>=7.4.0"],
# Plotly (required if .visualize is ever called)
"plotly": ["plotly>=3.8.1"],
# Explainers
"lime": ["lime>=<IP_ADDRESS>"],
"sensitivity": ["SALib>=1.3.3"],
"shap": ["shap>=0.28.5", "dill>=0.2.5"],
"ebm": [joblib_dep],
"linear": [],
"decisiontree": [joblib_dep],
"skoperules": ["skope-rules>=1.0.0"],
"treeinterpreter": ["treeinterpreter>=0.2.2"],
# Dash
"dash": [
"dash>=1.0.0",
"dash-cytoscape>=0.1.1",
"dash-table>=4.1.0",
"gevent>=1.3.6",
"requests>=2.19.0",
],
# Testing
"testing": [
"pytest>=4.3.0",
"pytest-runner>=4.4",
"pytest-xdist>=1.29",
"nbconvert>=5.4.1",
"selenium>=3.141.0",
"pytest-cov>=2.6.1",
"flake8>=3.7.7",
"jupyter>=1.0.0",
"ipywidgets>=7.4.2",
],
}

https://github.com/microsoft/interpret/blob/master/python/interpret-core/setup.py

discussed, I guess we actually don't need any extras for now


stepping problems with enumerator

Working on https://youtrack.jetbrains.com/issue/RUBY-16770 (which is a problem in debase) I've noticed that byebug doesn't work well with the following code.
require 'byebug'
triangular_numbers = Enumerator.new do |yielder|
  number = 0
  count = 1
  byebug
  loop do
    number += count
    count += 1
    yielder.yield number
  end
end

byebug
print triangular_numbers.next, " "

5.times do
  # byebug
  print triangular_numbers.next, " "
end

exit

if call "next" when you stopped at byebug inside enumerator  I'd expect it will exit the block and stop somewhere (either "5.times" or "print") but actually it works like continue :(
Another problem is that if uncomment  3rd "byebug" call and run next there I'd expect byebug will step over "print" and stop at byebug again, but it actually goes into "loop" inside enumarator's block.
It looks like enumarator implementation does something strange (unexpected) in term of stack: it actually completely changes it and thus all byebug's code which relies on stack size works in unexpected way.
As soon as I will fix the crash inside debase I expect the same problems there too, thus I'm filing the ticket to discuss ways to resolve it or decide what we will need from Ruby VM to fix it.

Thanks! Keep me posted on your findings!

It looks like we see enumerator's implementation details: it replace whole call stack.
But all four debugging gems I know (byebug, debugger, debase, and ruby-debug-base) are written in assumption that the only possible stack modifications are push/pop and thus stepping is implemented in term of stack size.
I, personally, do not see simple way to handle stack's swap we have in case of enumerators because we need to keep at stack size we had before the next call and also somehow detect that we are in the call (e.g. check if topmost frame has (nil:0) (file:line_no), though this is rather fragile heuristic :(
@deivid-rodriguez do you have any ideas/suggestions how to approach/resolve the problem?

@os97673 You mean instead of pushing a new frame, it replaces the top most frame? Can you point at ruby's source code where that happens?
Sorry I can't be of more help right now, I need to find some time to study both Enumerator and its implementation just to able to answer your question...

As far as I can see Enumarator#next uses fiber (https://github.com/ruby/ruby/blob/trunk/enumerator.c#L610) which in turn does all dirty hacks (e.g. see https://github.com/ruby/ruby/blob/trunk/cont.c#L1337)

So this is not specific to Enumerator but has to do with Fiber? In that case I guess the next step would be reproducing using Fiber only?

Here is the test
fiber = Fiber.new do
  number = 0
  count = 1
  loop do
    number += count
    count += 1
    Fiber.yield number
  end
end

puts fiber.resume

5.times do
  puts fiber.resume
end

Nice. Now I need to study fibers instead of enumerators... :smile:

I've performed more tests and it looks like we receive no events for creation/switching of Fibers :(
Imho we need them but it also mean that we will need to keep context for every fiber and (if we decide to support them) we will need to decide what step, step into and step out should do in case of fibers.
What do you think?

I agree... But it might be worth opening an issue in ruby-core maybe?

As soon as we both agree that it looks like a reasonable API, I will file the issue there and link it to this one.

https://bugs.ruby-lang.org/issues/11348 created

Thanks @os97673


Geolocation throw error on android

In android, using this code
let x = await geoLocation.getCurrentLocation()
    return x.longitude+","+x.longitude;

Throw NOT_SUPPORTED_ON_PLATFORM  error, or error 100.
In desktop and in Web works, but not on android.
How I can fix that?

@SebastianAviles - Could you please check this sample and let us know if you are able to find the location or not in Android device?
https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/tab-device-permissions/nodejs

Not work, in android not show the GeoLocation module.

In code, the NonWebVersion has comented the lines of GeoLocation Module.

I enabled by hand the modules, but still throw error 100.

@SebastianAviles - Okay, we will check this with concerned team and will get back to you.

@SebastianAviles - Could you please let us know if you are using "geoLocation" component
const x = await geoLocation.getCurrentLocation();
Refer the below code ,
microsoft-teams-library-js/apps/teamsjs-cc-app/tabs/src/components/capabilities/GeoLocation.tsx at vikramtha/teamsjs-cc-app · vikramtha/microsoft-teams-library-js · GitHub
Please note that below are the supported platforms as mentioned here:
https://learn.microsoft.com/en-us/microsoftteams/platform/m365-apps/teamsjs-support-m365#geolocation

Yes, I using geoLocation component.
But location is deprecated.

Hi @SebastianAviles - We got update from engineering team that, "Currently geoLocation is not supported in Android."
Please note that below are the supported platforms as mentioned here:
https://learn.microsoft.com/en-us/microsoftteams/platform/m365-apps/teamsjs-support-m365#geolocation

We are closing this issue for now, please feel free to reopen it, if required.


Fixing the local mkdocs serve using the described versions of mkdocs

#419 This pull request fixes the issues that are described in the issue.

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

I see. Earlier on I was using python 3.5 and had some other issue, upgrading to python 3.7.2 and building with latest mkdocs + mkdocs-material seems to solve the issue. Will create another pull request changing the readme.md then.


Lock memory usage in ping

Do not merge yet. I'll merge next week

Superseed by https://github.com/micro-ROS/rmw_microxrcedds/pull/200


museum: photos-v0.9.35 -> photos-v0.9.42

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ente-io/ente/releases.
meta.description for museum is: API server for ente.io
meta.homepage for museum is: https://github.com/ente-io/ente/tree/main/server
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found photos-v0.9.42 in filename of file in /nix/store/rrx6ihsxy4hicq7r9d28kk6hzfzaw1xc-museum-photos-v0.9.42

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

museum

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rrx6ihsxy4hicq7r9d28kk6hzfzaw1xc-museum-photos-v0.9.42 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A museum https://github.com/r-ryantm/nixpkgs/archive/cfe89b1f1ba835dbf846369b44322b051cc0b0b5.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/cfe89b1f1ba835dbf846369b44322b051cc0b0b5#museum

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rrx6ihsxy4hicq7r9d28kk6hzfzaw1xc-museum-photos-v0.9.42
ls -la /nix/store/rrx6ihsxy4hicq7r9d28kk6hzfzaw1xc-museum-photos-v0.9.42/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

museum

Maintainer pings
cc @surfaceflinger @pinpox for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

PR is outdated. v0.9.44 is already out


Add documentation for trace performance metrics

A draft of documentation can be found at this link https://gist.github.com/nazavode/5d804bfc2f7cb7d6a5da99ce48381593.
Include in repository, possibly in the source code, or in an alternative easily maintainable form.

Added in https://github.com/pulp-platform/snitch_cluster/pull/149.


fix(dialog): default dialog actions alignment to end

Switches to defaulting the alignment for mat-dialog-actions to the end, rather than the start.
Fixes #13618.

Closing since this fix is for the legacy mat-dialog which has been superseded by the MDC based one.


Update the game over message

Update the game over message so people know how to play again!

I see we moved from step 2 to 3 using GH actions.


Environmental vars might be set on build, not on run. Audit this.

Setup app with env vars. Build. Push to a different environment server. Run and check env vars. Are they the env vars or the build env, or of the running env?
This might have been introduced in an attempt to log these env vars only once. Used to be the case the these were logged when defined to build, when testing, when starting server, and upon responding to requests- which resulted in a lot of noise in logs.

Reproduced. need to remove ^:const in constants.clj

merged directly to master. removed ^:const.


video-only demo can't execute at weixin browser

Excuse me .I ran the video-only demo at weixin browser of mobile.when I pressed the camera button, there is no response for my click.could you tell me how can I run the demo at weixin browser.

@dbxiaoqiang I'm not familiar with the 'weixin' browser. Can you give me a link that shows the specifications of the browser?

I have known the reason why 'weixin' browser can't execute the demo because it doesn't support the new browser api such as 'getMediaDevice'. Now we only could use the h5 native element(input type=file) to achieve our requirement.
By the way my friend, you can download a 'weixin' app to research its browser at phone app store


OLH-1130: updated from alphagov to govuk-one-login

As part of transferring ownership of repo from alphagov to govuk-one-login (a trust initiative) this PR has updated any old package references to point to new location.

I believe this has already been resolved, so I will be closing this!


Pytest for notebooks in allowed_fail build

Overview
This PR fixes #203
Changes:

Added a Travis CI build to explicitly test the notebooks and is allowed to fail.

Related Issue / Discussion
Additional Information
Links to other issues or sources.

That was fast !
Looks like it's working. Thanks.
Have you heard of a way to reuse the conda environment from one test environment to the other ? This would probably speed up the tests.
Will merge for now, but if you see something, please open a ticket to discuss it.

Unfortunately, I don't think that's a feature in Jenkins/Travis CI. I think that the only way to do this would be to run the tests in one of the build and ignore the failing flags if raised. In a makefile, these are commands run with a hyphen, e.g.:
.PHONY: clean
clean: srcclean env_clean raven_clean ostrich_clean
	@echo "Cleaning generated files ..."
	@-for i in $(TEMP_FILES); do test -e $$i && rm -v -rf $$i; done

The same is true for Travis CI builds. We can try modifying an existing build to perform these tests, but we can't know if they fail unless we look closely at the logs.
All the same, I'll give it a quick look and keep an eye open. I agree that it would be useful to shave machine time off of some builds.


Enhance module

Include: https://github.com/NixOS/nixpkgs/pull/265270
Now be able to auto reload dae while using config (corresponding to configFile) option after rebuilding the system. But this's not recommended since it will expose the config file in nix store with global readable.

also cherry-pick this the merge commit into the unstable and exp branches

Done.


Firmware images not downloaded properly

I tried downloading the firmware adter recreating my docker machine. The download finished but the firmware list is empty. I am using the latest version of IDE and local compiller package.
This is the output from docker images (truncated to have only relevant info)
REPOSITORY                           TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
<none>                               <none>              b87840083bfd        10 days ago         1.903 GB
<none>                               <none>              e14133c6adfe        2 weeks ago         258.4 MB
<none>                               <none>              b0bce4ca3f23        3 weeks ago         1.971 GB
<none>                               <none>              e14e854d6850        3 weeks ago         2.079 GB
<none>                               <none>              c0952bcd5e9f        3 weeks ago         2.053 GB
<none>                               <none>              f502a15cf224        3 weeks ago         2 GB
<none>                               <none>              2dc50bc70b7f        3 weeks ago         1.999 GB
<none>                               <none>              c5b61b0f9789        4 weeks ago         1.926 GB
<none>                               <none>              da483b2047ad        4 weeks ago         1.908 GB
<none>                               <none>              e308d4494b7f        9 weeks ago         1.04 GB
<none>                               <none>              2f2b07641e92        9 weeks ago         1.317 GB
<none>                               <none>              9edb451a40ee        11 weeks ago        1.209 GB
<none>                               <none>              d151d5c43ac5        11 weeks ago        1.224 GB
<none>                               <none>              4a048d9fceaf        11 weeks ago        1.307 GB

I tried requesting another download and it finishes in about 4 seconds but nothing changes.
@suda any ideas?
Thanks,
Robert

Hmm this looks like pull hasn't finished properly. Could you try restarting it and wait a bit longer?

I tried requesting a new firmware update. I did nothing.
I deleted all orphaned layers and tried again. I started from the beginning (as it should) and it managed to download only one firmware version before stoping and acting like everything is done.


Switch to psalm

Fix issues found with psalm.
Switch github action to psalm.
Remove phan configuration.
Fix use of exceptions.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

👍


⚠ eaglestorage.com.au has degraded performance

In 82450b2, eaglestorage.com.au (https://eaglestorage.com.au) experienced degraded performance:

HTTP code: 200
Response time: 6973 ms

Resolved: eaglestorage.com.au performance has improved in 4ffbffe after 10 minutes.


Set a limit on how many alerts can be merged

to: @jacknagz
cc: @airbnb/streamalert-maintainers
size: small
Background
We saw some errors in our test deployment due to messages being too large to deliver to their outputs. One such message had merged 89 alerts together!
Changes

Limit the maximum number of alerts which can be merged to 50. This won't always solve the problem of a message which is too large, but it's a helpful guardrail which prevents a total runaway merge

Testing

Added a new unit test to ensure the MAX_ALERTS_PER_GROUP is honored
Deploy to a test account, sent many alerts in rapid succession, confirmed that they were grouped together

Coverage increased (+0.002%) to 97.196% when pulling 5a50644598b4adc56d73c75b06727edaf5a08d04 on austin-max-merging into 2bc4e29e0862bedbc4e79f50fb3a060e1e0cfaca on master.


Refine helm package and add installation docs

Refine current helm package of arcadia and add installation docs.

Testcase might fail if arcadia-apiserver restart too many times before arcadia-minio datasource is created, as arcadia-minio creation is a post-install action for helm install, use separate issue to track.


Update default examples to llama3.2

Background
Our current default examples are implemented with llama3.1 as the LLM used. Now that llama3.2 dropped we want to update the core examples in the repo.
What to update

[ ] https://github.com/i-am-bee/bee-agent-framework?tab=readme-ov-file#example
[ ] https://github.com/i-am-bee/bee-agent-framework/blob/main/examples/llms/providers/ollama.ts
[ ] https://github.com/i-am-bee/bee-agent-framework/blob/main/examples/agents/bee_advanced.ts
[ ] https://github.com/i-am-bee/bee-agent-framework/blob/main/examples/agents/bee.ts
[ ] https://github.com/i-am-bee/bee-agent-framework/blob/main/examples/agents/sql.ts
[ ] https://github.com/i-am-bee/bee-agent-framework/blob/main/examples/llms/providers/watsonx.ts
[ ] https://github.com/i-am-bee/bee-agent-framework/blob/main/examples/llms/providers/watsonx_verbose.ts

Acceptance criteria

[ ] Validate that the model swap doesn't impact the performance of the example. Compare example performance before and after switch.

@mmurad2  Interested in working on this issue could you assign this to me so that i can work on it ?

Great @Abiji-2020!
Firstly you need to define the model template in src/adapters/shared/llmChatTemplates.ts. then you have to updates presets for BAM and WatsonX, finally update the examples.

@Tomas2D I have updated the templates and then updated the presets for the both. The PR #51 was updated on that


Intelligent Cody: Extract identifiers with Treesitter

This is a WIP we should discuss about finishing. This currently replaces the looks-like-an-identifier parsing with a treesitter node walk. This should be equivalent in functionality with fewer false positives (trying to extract definitions from strings or in block comments, for example).
Where this shines is the ability (in the future, not implemented here) to try to reduce multiple requests to different occurrences of the same variable. We should be able to do a quick tree walk to see which variables reside in the same scope and deduplicate them in a semantically intelligent way.
Test plan

Uhh exiciting. I'll be OOO tomorrow so pinging @valerybugakov for his eyes too 👀


Move integration loop into lowered cell implementation.

Now (nearly) with the batched sampling implementation (PR #347), there is no need to expose the integration loop through explicit setup_integration and step_integration methods. Rolling them into a single integrate method will:

Simplify mc_cell_group–fvm_multicell API.
Ensure cell times are synchronized between API calls, simplifying implementation.

Tasks:

Move integration loop sitting in mc_cell_group::advance() into a new method fvm_multicell::integrate().
Simplify fvm_multicell time handling code.
Implement voltage out of bounds check in lowered cell (possibly with GPU kernel to reduce overhead).
Patch up the unit tests that use the current interface.

Note: this is already incorporated into the big mechanism refactor work.

Fixed by PR #484.


Wow so you are 160 commits ahead of jiangmiao should we just use your fork then?

Happy to do it and super confused right now about how to disable autopairs it says the command is  which on a Mac Meta is mapped to the ESC key right so should be ESC-p, but this just bleeps at me

Assuming you don't find another plugin you like more, sure. I've also been keeping up to date on upstream issues
The meta mappings have been partially phased out; they're enabled by default purely for backwards compatibility. If you set g:AutoPairsCompatibleMaps to 0, <C-p><C-t> (mnemonic: c-pairs c-toggle). Is that what you meant, or did I misunderstand?
The meta mappings, at least in insert mode, inherently have several problems - I had no idea weird mac behavior was one of them ^^" I guess that's another reason to throw in the pile of justification for changing the maps
And as always, if you don't like the maps (or they for other reasons cause problems, like by conflict, or various specific OS behavior), there's variables to change them; g:AutoPairsShortcutToggle.

Yes that’s great. I flipped this on. And it works great. The document is pretty unclear about the four command. As I try to parse the doc I don’t really get what jump does b
Sent via Superhuman iOS<EMAIL_ADDRESS>)
On Mon, Mar 1 2021 at 11:12, Olivia <<EMAIL_ADDRESS>> wrote:

Assuming you don't find another plugin you like more, sure. I've also been
keeping up to date on upstream issues
The meta mappings have been partially phased out; they're enabled by
default purely for backwards compatibility. If you set g:AutoPairsCompatibleMaps
(
https://github.com/LunarWatcher/auto-pairs/blob/master/doc/AutoPairs.txt#L932-L948
) to 0,  (mnemonic: c-pairs c-toggle). Is that what you meant, or
did I misunderstand?
The meta mappings, at least in insert mode, inherently have several
problems - I had no idea weird mac behavior was one of them ^^" I guess
that's another reason to throw in the pile of justification for changing
the maps
And as always, if you don't like the maps (or they for other reasons cause
problems, like by conflict, or various specific OS behavior), there's
variables to change them; g:AutoPairsShortcutToggle (
https://github.com/LunarWatcher/auto-pairs/blob/master/doc/AutoPairs.txt#L361-L367
).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (
https://github.com/LunarWatcher/auto-pairs/issues/24#issuecomment-788198029
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AANTCR3VORSPI6346O4EPQ3TBPRIBANCNFSM4YNDGOFQ
).

It's largely explained in the name, but I can rewrite those sections a bit. The jump keybind is literally just "jump to the first closed pair after the cursor"

Ah got it!!!
Sent via Superhuman iOS<EMAIL_ADDRESS>)
On Mon, Mar 1 2021 at 22:58, Olivia <<EMAIL_ADDRESS>> wrote:

It's largely explained in the name, but I can rewrite those sections a
bit. The jump keybind is literally just "jump to the first closed pair
after the cursor"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (
https://github.com/LunarWatcher/auto-pairs/issues/24#issuecomment-788667117
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AANTCR7BPVNAR7VUAFTV5MDTBSEBDANCNFSM4YNDGOFQ
).


[DismissableLayer] Layering breaks with different component versions

Initially raised on Discord.
If two components (e.g. DropdownMenu and Dialog) are using different versions of DismissableLayer internally, then the layering breaks because of the different context instances.
We never added scoping to DismissableLayer since it should always cross component boundaries, however, I wonder if scoping could help here since it effectively passes context through a private prop that it expects the component to use. It might be worth looking into as a solution.

Hmmm yeah that's where these multi-package distributions become complicated sometimes, these types of issues are really hard to stay on top of.
I'm worried the scoped context would kinda break the intention of DismissableLayer though.

could this be solved by changing the "@radix-ui/react-dismissable-layer": "workspace:*" dependency in each of the package.jsons to "@radix-ui/react-dismissable-layer": "latest" ? 🤔

I don't think that would help as ultimately this is already the case, when a new change is made in @radix-ui/react-dismissable-layer the other packages would have a new version with the version of @radix-ui/react-dismissable-layer being latest. But it doesn't prevent anybody from installing versions that use different version of @radix-ui/react-dismissable-layer. Hardcoding to "latest" instead of a said version would kinda solve that, but I'm not sure it's viable or even makes sense from a code perspective as potentially changes could be introduced and older versions of popover for example might not be compatible with those changes forced by the latest.
Interestingly though, I had a somewhat similar thought process a few weeks back. I was thinking potentially we could "solve" this issue by making the incompatibility visible at install time by making @radix-ui/react-dismissable-layer a peer dependency.

Hardcoding to "latest" instead of a said version would kinda solve that, but [...] changes could be introduced and older versions of popover for example might not be compatible with those changes forced by the latest.

i had considered this but since DismissableLayer is a "global" component I had thought maybe changes to its apis could be handled withy deprecation warnings and things. given that it's a pretty stable comp at this point and not likely to change much, that might not be so bad. it seems better than the current state of things anyway where things just completely break for folk.
making it a peer dependency would surely suffer the same issues except radix would be adding an extra step for consumer by requiring them to manage the dependency.

Hi, just want to start out by saying thank you for building such a useful and headless primitive UI library. It really had helped our team when it comes to building with speed and reliability. I just wanted to throw in our scenario into the mix. We currently have an open source library that utilizes radix to build out the UI. I think it's ok for us to make sure that the dependencies are all on the same version (especially for those that use DismissableLayer). The issue arises when others install our library into their react application and they so happen to be using radix internally. I think at the moment it's not likely that this will happen too often but it would be nice in those cases to specify that we only allow using a specific version of DismissableLayer. In those cases either a warning or an error would suffice.
I also tried adding "@radix-ui/react-dismissable-layer": "1.0.1-rc.2" as a peerDependency and this did warn me when installing into our demo application but after installing that I was left with two versions of react-dismissable-layer. We'll add this to our docs to warn users but it does make things a bit more complicated when someone wants to use our library and radix primitives. Maybe a better approach would be to detect it at run time and throw an error in the console when multiple DismissableLayer contexts are detected.

Hardcoding to "latest" instead of a said version would kinda solve that, but [...] changes could be introduced and older versions of popover for example might not be compatible with those changes forced by the latest.

i had considered this but thought maybe changes to its apis could be handled with a deprecation warning. given that it's a pretty stable comp at this point and not likely to change much, that might not be so bad. it seems better than the current state of things anyway where things break for folk.

I'm more worried about dependency changes, whilst the API of DismissableLayer might not change much, even a small change in any underlying dep (@radix-ui/primitive, @radix-ui/react-primitive for example) will generate a new version which will bring the issue again.

something like:

A component is using a deprecated DismissableLayer api. To solve this, upgrade your components to the same version number.

Also on this, "the same version number" is very hard to communicate as they're independently versioned so unlikely to be aligned, so effectively you have to say, make sure the primitives that use DismissableLayer are all aligned in terms of its version. It's very difficult… :(

even a small change in any underlying dep (@radix-ui/primitive, @radix-ui/react-primitive for example) will generate a new version which will bring the issue again.

ofc, but what i'm saying is that radix would know that those sorts of changes will be the only scenario that will cause this issue for consumers so you can add a note to release notes / code warnings on with a migration path when you make changes to the underlying deps/apis (which again, its deps are pretty minimal/stable so rarely likely to change).
at the moment, the current state of things means that this could happen any time for any consumer just by changing their configuration of dependencies which radix has zero control over.
i agree that the suggestion isn't perfect but it seems better than the current alternative, and is a relatively simple change.

For all having this issue now:
Our current solution to this is using pnpm's dependency override functionality.
Adding this to package.json forces everything to use DismissableLayer version 1.0.2.
"pnpm": {
	"overrides": {
		"@radix-ui/react-dismissable-layer": "1.0.2"
	}
},

@benoitgrelard

The only way to resolve this would be to use some global on window probably, which wouldn't be a good idea for many reasons

Don't know if this will work for you, but I solved this in my library by using a Symbol: https://github.com/liqvidjs/plugins/blob/4f19efbd15399cecc1721142936b4f191de52d70/packages/playback/src/react.ts#L6-L14

I wonder if we can detect this and throw loudly in dev? The possibility that installing a new primitive silently creates a serious production bug is concerning (pointer-events: none stuck on body element).
My scenario was a Select inside of a Dialog... with both open, pressing escape closed both and pointer-events: none was stuck on the body element. I originally thought it was a bug in my code and spent a while debugging. It can be tricky to debug with dev servers and npm quirks, lots of variables.
Select and Dialog were both updated to the newest package version, but some of the other primitives were not. Once I updated everything the issue was resolved.

Here's how mobx handles cross-environment global for the purpose of detecting multiple versions of the package at runtime. Basically use globalThis where it's supported and then fall back to individual environment global names. react-dismissable-layer could register itself to a global in this way and, if it's already there, throw an error.
The peerDependencies route seems promising as well but I think that would require the app author to install react-dismissble-layer manually in addition to the primitives?

This worked for me:

Overriding the react-dismissable-layer version in package.json

  "resolutions": {
    "@radix-ui/react-dismissable-layer": "^1.0.5"
  }

Deleting and reinstalling node_modules

The above solution also worked for me, but I had to include the dialog library as well:
"resolutions": {
    "@radix-ui/react-dismissable-layer": "^1.0.5",
    "@radix-ui/react-dialog": "^1.0.5"
  }

And +1 for deleting node_modules and re-installing.

We're facing this issue in https://github.com/strapi/strapi. We use radix as a bedrock for https://github.com/strapi/design-system but because we're extensible there appears to be some conflicts happening in specific projects.
We're looking to recommending using resolutions as a workaround – but is there any appetite to investigate into solutions further? I appreciate it's very difficult & I'm not gonna pretend I know where to start in solving it either 😅

Yes, definitely appetite to work on this! There isn't a straightforward answer but this one is very much top of mind for me. We're going to take another look.
Looking for opinions on this: At minimum, I'd like this situation to break loudly in development, so you at least know you have mismatched versions.

@StephenHaney the DismisssableLayer props and context shape (external interface) hasn't changed in 2+ years. my original proposal here that was to hardcode the "latest" string into each package for their react-dismissable-layer dependency wld have solved this quickly and easily.
we're perhaps overthinking how imperfect this solution might be. while i agree it isn't ideal it wld have at least solved it for the past 2+ years while the team thinks on it some more.
it would allow your proposal of loudly breaking in development bcos when DismissableLayer context shape/props change, it can check if something is still using a legacy version of those interfaces and scream. they wouldn't know which component is relying on an old API but it can propose upgrading them all to the same version.
the benefit of this solution is that it would only ever break loudly if the DismissableLayer interface changes, which again, that hasn't happened in 2+ years 😛

@jjenzz I completely agree, I think we need to take a pragmatic approach here and remove the trap.
How do you contrast your solution against using a global this type solution – which is actually pretty reliable across envs now – to detect multiple versions of DismissableLayer and throw in dev? So basically keeping a global that DismissableLayer registers itself onto (this is what mobx does).

@StephenHaney the difference is that a globalThis solution means they will have different versions of DismissableLayer in their bundle still (bundle size) and the chances of someone hitting this issue are the same as they are currently, we've just improved the messaging.
radix could remove the DismissableLayerContext altogether and useSyncExternalStore so all packages reference the same version of global state, however, that'd just move where breaking changes can occur—instead of them occurring when the consumer API changes (my proposal) they would occur when an implementation detail changes (the context shape/global store shape).
Radix usually treats context as internal so the expectation is that it is safe to change at will w/o introducing breaking changes. therefore, i'd be more concerned about that approach resulting in breaking changes for consumers. props are always the public facing API and a change there is expected to be a breaking change for all components.
yes your understanding is correct. all packages wld always be on the same DismissableLayer version so only one version in bundle, and a change to props shape is the only scenario this issue can occur regardless of mix 'n' matched comp versions.
a breaking change wld be handled the same way a breaking change is handled when props API changes for any of the comps (all packages bumped a major etc.). there is no need to create a new package for breaking changes. radix can just log in dev mode if DismissableLayer sniffs an old version of its public facing API being called.
type DismissableLayerProps {
- foo: boolean;
+ bar: boolean;
}

const DismissableLayer = props => {
   if (props.foo !== undefined && process.NODE_ENV = 'development') {
    // stack trace wld likely show which comp used this prop
    throw new Error('A component is using an outdated version of DissmissableLayer. Please upgrade comp to latest');
   }
}

Don't know if this will work for you, but I solved this in my library by using a Symbol: https://github.com/liqvidjs/plugins/blob/4f19efbd15399cecc1721142936b4f191de52d70/packages/playback/src/react.ts#L6-L14

i've just seen this btw and that is a neat solution ☺ that wld work! it wld just suffer the issues i mentioned of breaking changes occurring when implementation detail changes, and consumer having multiple versions in their bundle unnecessarily.

Don't know if this will work for you, but I solved this in my library by using a Symbol: https://github.com/liqvidjs/plugins/blob/4f19efbd15399cecc1721142936b4f191de52d70/packages/playback/src/react.ts#L6-L14

i've just seen this btw and that is a neat solution ☺ that wld work! it wld just suffer the issues i mentioned of breaking changes occurring when implementation detail changes, and consumer having multiple versions in their bundle unnecessarily.

This seems like a good approach – do I understand correctly that using a symbol protects against collision with other libraries? Is there any known environment where this wouldn't work well?

perhaps i'm misunderstanding but as mentioned before, context shape is an implementation detail in radix. as far as i understand it, the symbol approach makes changes to an implementation detail become a breaking change for consumers.
for example, if you have a context shape with a "foo" property in V1 and that property is removed in V2, an old comp could be looking for "foo" on the symbol's context but it won't exist.
tmk, the "latest" approach i proposed before makes changes to props (not context) the only potential breaking change. that is consistent with how changes in other primitives become breaking. props changes are the only potentially breaking changes for radix primitives tmk, since props are the public facing API. keeping that consistency seems more maintainable.

none of the solutions worked for me, even downgraded for testing select is unusable inside of a modal

would still have to solve it the way radix suggests today but this would rarely be necessary because the api hardly ever changes.
@leognmotta
Update the dependencies to –latest.

Try adding the overrides:
"overrides": {
"@radix-ui/react-dismissable-layer": "^1.0.5",
"@radix-ui/react-focus-scope": "^1.0.4"
}
Delete the yarn.lock, pnpm-lock.yaml, or package-lock.json file and the node_modules folder, then run the installation again.
https://github.com/shadcn-ui/ui/issues/1647

My problem was caused by these versions:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
The latest version of react-dropdown-menu was 2.1.4, and the latest version of react-popover was 1.1.4. Updating to keep all 3 at *.1.4 fixed my issue.
Is there a way for us to get installation warnings or a runtime warning for the mismatch? Is it safe to assume that matching minor versions means compatibility? Could any of this be fixed by using a non-locked peer dependency of react-dismissable-layer if not already?


Add spinner to camper news search

This looks like a good spinner: http://lea.verou.me/2013/11/cleanest-css-spinner-ever/

I'm not seeing any mention of a license on that page, open or not; could FCC legally use it?

I'll have to check with the author. I'll tweet at her.

Quincy Larson
"Anyone who has begun to think, places some portion of the world in
jeopardy." - John Dewey

On Wed, Jun 17, 2015 at 6:45 AM, Anton Strömkvist<EMAIL_ADDRESS>wrote:

I'm not seeing any mention of a license on that page, open or not; could
FCC legally use it?
—
Reply to this email directly or view it on GitHub
https://github.com/FreeCodeCamp/freecodecamp/issues/546#issuecomment-112805253
.

Smart. I'm trying to implement it in the meantime. A small concern, the background color of FCC (#eee) is the same as some of the parts of the spinner. This could easily be rectified by changing the colors, but I kind of like how it looks. Example here

Okay, so I think I got this to work over here, but my local database is completely empty, so searches are over in fractions of a second. If you can try it out and see if it works (and Lea approves), I'll create a PR and we'll be good to go.

No response from Lea yet, @QuincyLarson?

@ahstro Did you ever form a PR for this?

I did not because we had not gotten a response from Lea and I didn't want to clog up the PR section. I can create on now if you want to?

Yeah if you are up for it.

You're going to want to test it with your database as well. I my empty one loaded very quickly; I tried making it infinite, and that looked good, but it's not the real thing.

We are going to move away from this for now. We may revisit in the future.


Tool cover

Updating xcelium coverage scripts to support test case ranking.
Unfortunately xcelium does not support the same granularity as VCS when using IMC at command line.
the script has been updated to create a file with a path to the coverage output directory.
this file is read when raking the tests cases.
the resulting output can be found under cov_report/grading/rank_sub_dir/rank.html
a link to this file can be added to our run summary pages.

we upload the entire $cov_report_dir, not sure if there is a link to the rank page in the generated coverage dashboard, like VCS provides
https://reports.opentitan.org/hw/ip/aes/dv/latest/cov_report/index.html

we upload the entire $cov_report_dir, not sure if there is a link to the rank page in the generated coverage dashboard, like VCS provides
https://reports.opentitan.org/hw/ip/aes/dv/latest/cov_report/index.html

@Weicai I am not sure what you are asking.
do you want a quick call today?

Hi @rasmus-madsen! What's the status of this PR?

hi @rswarbrick
The status is I didn't find an easy solution - and never got back around to find a better solution.
so still TBD

it was at the time - I will put on my TODO to check that this still holds and get it in this week


Extension causes high cpu load

Issue Type: Performance
Extension Name: LiveServer
Extension Version: 5.5.1
OS Version: Windows_NT x64 10.0.17134
VSCode version: 1.32.3

:warning: Make sure to attach this file from your home-directory: C:\Users\manua\ritwickdey.LiveServer-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Hello, few questions,
When you're getting this issue? after load of vscode or after clicking to Go Live ?
Is this happen every-time ? or random ?
Please reply here https://github.com/ritwickdey/vscode-live-server/issues/278
Duplicate of https://github.com/ritwickdey/vscode-live-server/issues/278

[Note: This issue is closed by a javascript code (written by me).
https://gist.github.com/ritwickdey/36682dabe4a992c57e4562c935bfbbdd ]


Zsh completion shows "deprecated command" warning when completing installed casks

Bug report
Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
Use Zsh tab completion when uninstalling a cask.
What happened (include command output)
The completion shows the warning about deprecated command brew cask list after pressing tab.
$ brew cask uninstall Warning: Calling brew cask list is deprecated! Use brew list --cask instead.

What you expected to happen
Not show any warning.
Step-by-step reproduction instructions (by running brew commands)
Press tab to autocomplete installed casks using Zsh.
Output of brew config and brew doctor commands
Doesn't apply.

Here is the line in _brew_cask that is still using brew cask list to get the list of all installed casks.
https://github.com/Homebrew/brew/blob/d0e1595fcf5c0a256aa9645d061c89385fdb594f/completions/zsh/_brew_cask#L35
That calls:
https://github.com/Homebrew/brew/blob/d0e1595fcf5c0a256aa9645d061c89385fdb594f/completions/zsh/_brew_cask#L15-L17

Can you open a pull request to fix this? The code should be in completions/zsh.

I can do this


[Request] Allow to edit animations speed

It would be nice to be able to modify the speed at which all the animations are done. I'd like to accelerate it in my case so that it takes less time between the click and the moment the ball reaches its goal and merges with another ball.

I tried this before, but accelerating animations make them much less smooth.
I also want to limit complexity of setting as much as possible.
I let it open to discussion…


Subscription class not in autoloader

<?php

require_once('vendor/autoload.php');

// Configuration
define('SANDBOX', 1);
define('BASE_URL', SANDBOX ? 'https://platform.devtest.ringcentral.com' : 'https://platform.ringcentral.com');
define('KEY', 'my_app_key');
define('SECRET', 'my_app_secret');
define('USERNAME', 'my_username'); // Main Phone Number
define('PASSWORD', 'my_password');

$rcsdk = new RC\SDK(KEY, SECRET, BASE_URL);
$rcsdk->getPlatform()->authorize(USERNAME, '', PASSWORD, true);
$rcsdk->getPlatform()->isAuthorized();

function getVoiceMails() {
    if ($rcsdk->getPlatform()->isAuthorized()) {
        try {
            $response = $rcsdk->getPlatform()->get('/account/~/extension/~/message-store?messageType=VoiceMail');
        } catch (RC\http\HttpException $e) {
            print 'Expected HTTP Error: ' . $e->getResponse()->getError() . PHP_EOL;
        }

        return $response->getJson();
    }
}

$rcsdk->getSubscription()
    ->addEvents(array('/restapi/v1.0/account/~/extension/~/presence'))
    ->on(Subscription::EVENT_NOTIFICATION, function (NotificationEvent $e) {

        print_r($e->getPayload());

    })
    ->register();

PHP Fatal error:  Class 'Subscription' not found in /home/rafael/PhpstormProjects/ringcentral-vm/program.php on line 37

Was this done intentionally?

You have to add
'''php
use RC\subscription\Subscription;
'''
statement or refer to the full name of class: 'RC\subscription\Subscription'.

Should it not be included in the autoloader?

Autoloader only tells php where to locate files, so it's already covered by Autoloader.
In the rest of your code you use full class names and it works, so do the same for subscription. Or have one use statement at the top of your file.

Okay thank you very much. I was confused about autoloading but you cleared it up.

No problem :)

Receiving this error. I don't want to change protected to public without your advice.
Stack Trace
PHP Fatal error:  Call to protected method RC\subscription\Subscription::notify() from context 'Pubnub\Pubnub' in /home/rafael/PhpstormProjects/ringcentral-vm/vendor/pubnub/pubnub/composer/lib/Pubnub/Pubnub.php on line 468
PHP Stack trace:
PHP   1. {main}() /home/rafael/PhpstormProjects/ringcentral-vm/program.php:0
PHP   2. VMDownloader->startListener() /home/rafael/PhpstormProjects/ringcentral-vm/program.php:62
PHP   3. RC\subscription\Subscription->register($options = *uninitialized*) /home/rafael/PhpstormProjects/ringcentral-vm/program.php:44
PHP   4. RC\subscription\Subscription->subscribe($options = *uninitialized*) /home/rafael/PhpstormProjects/ringcentral-vm/vendor/ringcentral/php-sdk/lib/RC/subscription/Subscription.php:76
PHP   5. RC\subscription\Subscription->subscribeAtPubnub() /home/rafael/PhpstormProjects/ringcentral-vm/vendor/ringcentral/php-sdk/lib/RC/subscription/Subscription.php:119
PHP   6. Pubnub\Pubnub->subscribe($channel = *uninitialized*, $callback = *uninitialized*, $timeToken = *uninitialized*, $presence = *uninitialized*) /home/rafael/PhpstormProjects/ringcentral-vm/vendor/ringcentral/php-sdk/lib/RC/subscription/Subscription.php:241
PHP   7. Pubnub\Pubnub->_subscribe($channel = *uninitialized*, $channelGroup = *uninitialized*, $callback = *uninitialized*, $timeToken = *uninitialized*, $presence = *uninitialized*) /home/rafael/PhpstormProjects/ringcentral-vm/vendor/pubnub/pubnub/composer/lib/Pubnub/Pubnub.php:365

Program.php
<?php

require_once('vendor/autoload.php');

use \RC\SDK;
use \RC\subscription\events\NotificationEvent;
use \RC\subscription\Subscription;

class VMDownloader
{
    // Configuration
    const KEY         = 'C3Kovxb2T9a7MYMmyhnv3A';
    const SECRET      = 'JJ-NjL0MSHyjdywa5t4B4QHE-AF_NRRcq-ePM-o6Chbg';
    const SERVER      = 'https://platform.devtest.ringcentral.com';
    const MAIN_NUMBER = '15856234168';
    const PASSWORD    = 'HKWXMX75934&H';

    private $sdk;

    function __construct()
    {
        $this->sdk = new SDK(self::KEY, self::SECRET, self::SERVER);
        $this->sdk->getPlatform()->authorize(self::MAIN_NUMBER, '', self::PASSWORD, true);
    }

    public function getVoicemails()
    {
        return $this->sdk->getPlatform()
            ->get('/account/~/extension/~/message-store', ['messageType' => 'VoiceMail'])
            ->getJson();
    }

    /**
     * Listens for new messages
     */
    public function startListener()
    {
        $this->sdk->getSubscription()
            ->addEvents(['/restapi/v1.0/account/~/extension/~/message-store'])
            ->on(Subscription::EVENT_NOTIFICATION, function (NotificationEvent $e) {

                print_r($e->getPayload());

                // TODO: Add curl downloader

            })
            ->register();
    }

    /**
     * @todo finish function definition
     */
    private function download()
    {
    }

    function __destructor()
    {
        print 'Destroyed';
    }
}

$t = new VMDownloader();

$t->startListener();

What version of PHP do you have?

rafael@rcepeda:~/Downloads/PhpStorm-141.1912/bin$ php -v
PHP 5.6.4-4ubuntu6.2 (cli) (built: Jul  2 2015 15:29:28)

I've pushed a small fix for your case, go ahead and try. The fix is in DEVELOP branch.

Thank you sir.
On Jul 17, 2015 3:28 PM, "Kirill Konshin"<EMAIL_ADDRESS>wrote:

I've pushed a small fix for your case, go ahead and try. The fix is in
DEVELOP branch.
—
Reply to this email directly or view it on GitHub
https://github.com/ringcentral/php-sdk/issues/2#issuecomment-122403736.

@ralph3991: I replaced the app and user credentials with placeholders in your posts. For security purposes, please don't post your app and user credentials online.

okay, since it was a sandbox, I did not mind it. But I gotcha


Add reboot in progress prometheus metric

Signed-off-by: Aaron Lucas<EMAIL_ADDRESS>Added a new metric to give a heads up when a node is in the process of rebooting.
We occasionally run into alerting issues during reboot when daemonsets or pods crashloop and eventually recover.
Adding this gives us the ability to run inhibits on these crashloops during the reboot window.

But, this new metric is not "faster" to recognize than the existing metrics from kube-state-metrics unless you set a very low scrape-interval for kured. I'm not sure if this is the way to go.
The problem with monitoring is, that it is always delayed and situations which dissappear very fast can't handled correctly very often.

But, this new metric is not "faster" to recognize than the existing metrics from kube-state-metrics unless you set a very low scrape-interval for kured. I'm not sure if this is the way to go. The problem with monitoring is, that it is always delayed and situations which dissappear very fast can't handled correctly very often.

Certainly possible to export this in kube-state-metrics however it will either be null or 1 and working with labels versus metrics you generally lose a lot of flexibility.
I understand that it's possible to miss this metric in scraping, I figured setting the metric at lock time would give enough headroom to scrape within reason.
Looking back on it now an empty node still might miss that window since the lock to reboot time is pretty low, however I think decreasing scrape interval is pretty low overhead unless I'm mistaken. Happy to go either way with this.

@jackfrancis @evrardjp What are your thoughts on this?


Statistics operators

Statistics operators e.g. RMS, or STD_DEV, etc.

For members vs members within an ensemble.
For member vs member between two ensembles.
For obs vs ensemble mean and ensemble member.
For one deterministic config vs another.

I expect these to be wrappers for existing MET capability utilising pointstat and ensemblestat.


Update LiveKit audio transport for changes introduced in v0.0.42

Updated to match Daily transport behavior:

Use InputAudioRawFrame and OutputAudioRawFrame. This should make the transport compatible with #541
Makes sure that if the participant joins before the bot, it will still trigger on_first_participant_joined.

LGTM!


Redesign Footer

Hi @ajaynegi45,
A footer is an excellent tool for overview introduction, Social handle promotion and ease of navigation for users.
The current footer of your website is very basic, I'd appreciate it if you could give me a chance to enhance it for more user engagement.
Happy Developing :)
Note:- Add the Hacktoberfest, Hacktoberfest-accepted and related labels.

Assignee:  @bhalerao-2002
Hi @bhalerao-2002
Thank you for your enthusiasm and willingness to enhance our footer! I've assigned the task to you, and we appreciate your dedication to improving the user experience.
Feel free to get started, and if you have any questions or need access to any specific resources, please don't hesitate to reach out. We look forward to seeing your enhancements to the footer.
Additionally, we've added the "Hacktoberfest" and "Hacktoberfest-accepted" labels to this issue, as per your note.
Happy developing, and thank you for your contributions!

@bhalerao-2002  are you currently working on this issue ?

Hi @ajaynegi45,
I am out of town for now.  I hade done Layouts, Just issues in position, I had committed you work and will get you done with it. Have some patience.
Happy Developing :)
Thanks for waiting.

Hello! I would like to contribute to this issue, please assign me this issue

Hey I would like to work on these issue

Hello @Sanketmane2323 and @Raghu1124,
Thank you all for your interest in contributing to this task. I appreciate your willingness to help us on "Redesign Footer" issue.
To make this process more collaborative, I'm assigning this task to all of you. You can each work on your own version. In the end, we will evaluate the contributions and choose the one that best aligns with our project's needs and goals.
Please coordinate among yourselves and feel free to discuss any questions or ideas you may have during the process. Once you've completed your contributions, please submit them for review.
Looking forward to seeing your work and thank you for your valuable contributions! ❤

Footer design should be like this. Add small description under the name


Change PyObject.typ to PyClassRef

To do this I replaced a few PyObject::new with PyValue::{into_ref, into_ref_with_type}.

Codecov Report

Merging #737 into master will decrease coverage by 1.12%.
The diff coverage is 44%.

@@            Coverage Diff             @@
##           master     #737      +/-   ##
==========================================
- Coverage   45.81%   44.68%   -1.13%
==========================================
  Files          81       81
  Lines       16168    16373     +205
  Branches     3995     4099     +104
==========================================
- Hits         7408     7317      -91
- Misses       6956     7268     +312
+ Partials     1804     1788      -16

Impacted Files
Coverage Δ

vm/src/obj/objcode.rs
40.21% <ø> (+8.39%)
:arrow_up:

src/main.rs
11.46% <0%> (-1.87%)
:arrow_down:

vm/src/obj/objmemory.rs
21.73% <0%> (+3.22%)
:arrow_up:

vm/src/obj/objsequence.rs
32.93% <0%> (ø)
:arrow_up:

vm/src/obj/objobject.rs
49% <0%> (-0.4%)
:arrow_down:

wasm/lib/src/browser_module.rs
0% <0%> (ø)
:arrow_up:

vm/src/import.rs
32.83% <0%> (ø)
:arrow_up:

vm/src/obj/objfloat.rs
47.89% <0%> (ø)
:arrow_up:

wasm/lib/src/vm_class.rs
0% <0%> (ø)
:arrow_up:

wasm/lib/src/convert.rs
0% <0%> (ø)
:arrow_up:

... and 35 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 cecc2e1...47d9602. Read the comment docs.


New version: PowerModelsAnnex v0.4.3

Registering package: PowerModelsAnnex
Repository: https://github.com/lanl-ansi/PowerModelsAnnex.jl
Created by: @ccoffrin
Version: v0.4.3
Commit: 2b36a4c744513b3539424d04567c510a8a77a161
Reviewed by: @ccoffrin
Reference: https://github.com/lanl-ansi/PowerModelsAnnex.jl/issues/50#issuecomment-605527477

@DilumAluthge I am not sure wait failed here.  Any suggestions?

Thanks!


attribute ‘localtime’ missing

Hey :)
Issue description
After updating my nixpkgs to a more current version I am unable to deploy a system via NixOps:
λ becky nixos.wiki → λ git master* → nixops deploy -d wiki --copy-only                                                            ~/documents/code/nixos.wiki
building all machine configurations...
trace: warning: The services.postfix.extraConfig option was deprecated. Please use services.postfix.config instead.
error: attribute ‘localtime’ missing, at /home/fadenb/nixpkgs/nixos/modules/services/scheduling/cron.nix:125:31
(use ‘--show-trace’ to show detailed location information)
error: unable to build all machine configurations

It seems to be related to a0d464033c2bacffa9c05d27903fb03cd09ace46 (4f901203e8d1a0ded90a73e2670ce493ed051299).
I did not have time.timeZone configured. Once I set time.timeZone = "UTC"; everything works as expected.
The documentation stated
This is additionally now the default value for the option, which means that systems where the option has not been set explicitly will continue to use UTC but allow imperative timezone adjustments now.
but has been changed to
This value allows changing the timezone of a system imperatively using <command>timedatectl set-timezone</command>. The default timezone is still UTC..
Both variants do not imply I need to configure the timezone as it defaults to UTC. I believe this is a bug.
/cc @lheckemann

Yep looks like my fault. On it!

So this should be fixed by 85cab748c7.
However, this does not cause cron to restart when the timezone is changed imperatively so it doesn't fully solve the issue. I'll look into what can be done, but I'm not sure systemd supports taking additional actions on timezone change. Wrapping timedatectl could work, but it's really ugly IMHO. Not supporting this use case (i.e. "users have to restart cron manually if they change the timezone imperatively, or just use systemd timers instead of cron") is not optimal either, but it's the best solution I can think of. Any opinions are very welcome!

Could you edit the issue title to mention cron?
I've just found out that we can probably use a .path unit to watch /etc/localtime and restart services as appropriate.

I believe this is fixed by #28185.


Develop branch is up to date

Personal information updated and resume looks pretty for me :heart:

Waiting for expected results


Feedback on Tutorial: Installing the VM Image

Hello guys,
In the documentation/mini-guide to install the HXEDownloadManager it should be mentioned that you need to have a JRE 8 64bit version otherwise the program will NOT run. Also maybe a little background on how to set JAVA_HOME and PATH (for Windows users at least).
Cheers.

Thanks for the comment. We are updating the documentation.


fix(frontend): Load info in filter component

Resolves #483
What does this PR do?
Remove unnecessary filters from the offer table
How should this be tested?

Make run
Login as a Sponsor
Go to Offers Management
Select filter icon

@steph222 that works looks awesome, but just an idea, why not to add start date and end date in the same row, what you think?

@steph222 that works looks awesome, but just an idea, why not to add start date and end date in the same row, what you think?

It was not clear to me, Take them separately but on the same line. Or have them together?

@steph222 that works looks awesome, but just an idea, why not to add start date and end date in the same row, what you think?

It was not clear to me, Take them separately but on the same line. Or have them together?
For example, lets take a look at this:

Current design
Offer name --------- Start date
End date --------- Status
Suggested design
Offer name --------- Status
Start date --------- End date

I think it is better, thanks 🤗


Releasing the modules

Our repo has been split up into ready-to-publish modules. This issue will track what needs to be done before we can get the next release out.

[ ] Make a module-friendly docs site: PR
[ ] Modify our JSDocs -> JSON build process to suit the changes from the docs site PR
[ ] Publish all @google-cloud/service modules to npm at 0.1.0
[ ] Publish the umbrella package, google-cloud, at 0.38.0

// cc @callmehiphop

@callmehiphop please update the post if I got any of those steps wrong / left anything out.

Publish the umbrella package, google-cloud
next time, please, update readme at the same time you publish new npm package or change the active branch on github so people do not read broken readme/doc or add notices like kubernetes repo does.

Yep, we should have left a message for users directing them to the accurate docs here: https://googlecloudplatform.github.io/gcloud-node/#/docs/v0.37.0/gcloud. I'll do that now, sorry for the confusion.

We're published!


Ethan: Blacklist 2023[\W_]*+oscars

Ethan requests the blacklist of the keyword 2023[\W_]*+oscars. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

2023[\W_]*+oscars has been seen in 18 true positives, 0 false positives, and 0 NAAs.


yarn dev fails with Uncaught Error related to registerTldrawLibraryVersion

Clone repos
yarn
yarn dev

Expected:
Runs servers as documented in readme with no errors
Actual:
Errors with below output.
Note:
Tried older versions of node, no joy. I tried with version 3.0.1 and 3.0.0 with the same result, however, using version 2.4.6 of @tldraw libraries worked.
% yarn dev
yarn run v1.22.22
$ concurrently --kill-others --names client,worker --prefix-colors blue,red yarn:dev:client yarn:dev:worker
$ vite
$ wrangler dev
[client] Re-optimizing dependencies because vite config has changed
[client]
[client]   VITE v5.4.5  ready in 1531 ms
[client]
[client]   ➜  Local:   http://localhost:5173/
[client]   ➜  Network: use --host to expose
[worker]
[worker]  ⛅ wrangler 3.78.2
[worker] -------------------
[worker]
[worker] Your worker has access to the following bindings:
[worker] - Durable Objects:
[worker]   - TLDRAW_DURABLE_OBJECT: TldrawDurableObject
[worker] - R2 Buckets:
[worker]   - TLDRAW_BUCKET: tldraw-content-preview
[worker] [wrangler:inf] Ready on http://<IP_ADDRESS>:5172
[wrangler:inf] - http://<IP_ADDRESS>:5172
[wrangler:inf] - http://<IP_ADDRESS>:5172
⎔ Starting local server...

[worker] ✘ [ERROR] service core:user:worker: Uncaught Error: Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope. To fix this error, perform this operation within a handler. https://developers.cloudflare.com/workers/runtime-apis/handlers/
[worker]
[worker]     at null.<anonymous> (worker.js:1612:28) in registerTldrawLibraryVersion
[worker]     at null.<anonymous> (worker.js:2757:1)
[worker]

[worker] ✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
[worker]

[worker] ⎔ Shutting down local server...

macOS: 13.6.7 (22G720)
node: Node.js v20.12.2
npm: 10.8.1

@SomeHats thank you for the fix!!
However it seems like it's not yet included in the latest tldraw release 3.0.3. Can we please update the dependency version in this repo once the fix gets released?


Specifying or detecting the average CPC currency used by KeywordPlanHistoricalMetrics / getAverageCpcMicros

I'm using this snippet to get the average CPC for a keyword. The problem is that the currency isn't specified. Is it AUD since the target location is Australia? can I ask for it to be returned in a specific currency for any target location, let's say USD?
    HistoricalMetricsOptions options = HistoricalMetricsOptions.newBuilder().setIncludeAverageCpc(true).build();

    GenerateKeywordHistoricalMetricsRequest request = GenerateKeywordHistoricalMetricsRequest.newBuilder()
        .setCustomerId(String.valueOf(customerId))
        .addAllKeywords(Arrays.asList("tennis racquets"))
        .addGeoTargetConstants(ResourceNames.geoTargetConstant(2036)) // australia
        .setKeywordPlanNetwork(KeywordPlanNetwork.GOOGLE_SEARCH)
        .setHistoricalMetricsOptions(options)
        .build();

    try (KeywordPlanIdeaServiceClient keywordPlanIdeaServiceClient = googleAdsClient.getLatestVersion().createKeywordPlanIdeaServiceClient())
    {
      GenerateKeywordHistoricalMetricsResponse response = keywordPlanIdeaServiceClient.generateKeywordHistoricalMetrics(request);

      for (GenerateKeywordHistoricalMetricsResult result : response.getResultsList())
      {
        KeywordPlanHistoricalMetrics metrics = result.getKeywordMetrics();
        System.out.println("cpc: " + metrics.getAverageCpcMicros() / 1000000f);

The currency should be the currency of the Google Ads account, which you can retrieve from the Customer.currency_code field. The API does not support overriding the currency for that request.
If you have additional questions about API functionality that is not specifically related to the library for Java, please reach out to our API support using the form at https://developers.google.com/google-ads/api/support/contact.
Thanks,
Josh


CPP/taskcpp/FindUnique.cpp

Complete the task and attach a screenshot of your code and output. You may take the input yourself according to the task.

Can you please assign this issue?

APPROACH

I have used two Pointer approach to solve this problem.
Initially the first pointer will point to second element of vector, and traverses till last second element of vector.
I will create a pointer immediate previous to the first pointer , now I will check whether the elements of previous pointer and current-pointer are different & element pointed by current pointer and immediate next element is different .
If this condition satisfies then , I will add the element into the variable and return boolean value specifying that the unique element exists or not.
Further I have added two conditions to handle , what if first element or last element of vector is unique.
In any case , if the unique Element does not exist then I have printed the verdict in console.

Program

Output


Fix TSan failure on Darwin.

We could end up logging after Matter stack shutdown and when a different stack was being configured, which would cause a thread race.
Also fixes a situation where we could try to resubscribe to things after our MTRDevice has been invalidated.
Fixes https://github.com/project-chip/connectedhomeip/issues/27425

Fast-tracking platform-specific change with platform owner review.

Looks like this hit: https://github.com/project-chip/connectedhomeip/issues/27427


Add timeout for clickhousemetricswrite

The context timeout could cause the abrupt connection closing and cause broken pipe errors. I don't have much idea as to why the default 5s is not enough. This adjusts the setting to a little higher till I get to figure out the underlying reason.
Part of https://github.com/SigNoz/engineering-pod/issues/1148

@prashant-shahi please include this in the next release


fix: kill process regurlarly, for cache and bootstrap

I recent refactos I removed the logic to kill the process in the Watch.

Actually we can merge because I remove the code to reset the bootstrap with timeToRedoBootstrap
I'll reintroduce it after everything is done 👍


Doesn't work witj lens 6

apple silicone (m1 pro)
Lens: 2024.1.300751-latest
Extension API: 6.10.33
Electron: 27.2.4
Chrome: 118.0.5993.159
Node: 18.17.1

Since Lens is closed source, I'm not able to test the extension anymore.
Sorry.

That's a great pity! I loved to see the cert info in lens!
@jkroepke If there is no chance to update that, could you please add a notification to the README.md or archive the project?  However, I'd love to see the continued ... :(

Its still working for OpenLens

I see :+1:


[main] Update actions

v1.3 Release prep -xtreme-sameer-vohra
/cc knative/networking-wg-leads
/assign knative/networking-wg-leads
Produced by: knative-sandbox/knobots/actions/update-actions
Details:

assuming flake in downstream tests due to mostly green history - https://github.com/knative/networking/actions/workflows/knative-downstream.yaml
/retest

/lgtm
/approve


[testing] Visual / e2e testing with Puppeteer

The experimental support for Firefox in Puppeteer has been just announced: https://github.com/GoogleChrome/puppeteer/tree/master/experimental/puppeteer-firefox#readme
From now on, it is possible to run visual or e2e tests in 2 browsers, making more sense to use Puppeteer - especially because you can run both Chrome and Firefox locally in Travis or CircleCI, without using cloud automation like SauceLabs which takes much more time.
I'm planning to investigate this and will report my findings here. Feel free to join.

hey, yes I think for testing we will have probably multiple systems covering different parts of an application/component/microfrontend (uh buzzword :p).
As it's now:

everything in karma

However that is not going to be be enough for all testing needs.
There are some options:

pure js tests with karma

Why not: jest? I think jest will sadly not be enough - as we still need to make sure all used javascript functions are available in every supported browser

"integration" tests with karma (e.g. "small - medium" ui elements and their dom api)
end 2 end tests with?

cypress seems like a very nicest solution with lot's of features (and they are working on (for quite some time now) supporting multiple browsers) Note: Discussion about how to query shadowdom is still ongoing.
webdriverio a little more low level but also very promising Note: Discussion about how to query shadowdom is still ongoing.

So lets add Puppeteer there as well :) So what would it make it the best out of these options?

We should definitely have a pro/cons overview and/or have a "why not" section with very good reasons.

I've worked a lot of webdriver io and puppeteer. I don't really like selenium, but it's the best cross browser option there is now. I'm a huge fan of puppeteer, it's very very stable for all that it does.
With Edge moving to Chromium and Firefox support coming we're only missing out on Safari for cross browser then, so that's a good sign at least.

AFAIK current prototype for Firefox is using the special build so it might be a bit early to switch to it at this point. I will keep an eye on the status of that project and see how it evolves.
For the screenshot testing, there are other solutions, too. Some are listed here: argos-ci/argos-cli#11
Note there is a storybook example, in particular.
In the lit-components project I'm currently using the vrtest, same library as Material UI is using. See config here: https://github.com/web-padawan/lit-components/blob/master/test/vrtest.config.js

I am not sure how we ended up discussing visual regression tests :see_no_evil:
anyways I think we should go as much as possible with storyboook as this is what we will actually test right?
So here are their infos: https://storybook.js.org/testing/automated-visual-testing/
So of course chromatic would be best as it's actually the guys that now are responsible for storybook itself.
However as it's not free (even for open source) I think we need an alternative... I took a quick look at everything I could find and for me, it seems percy could looks the nicest.
So I guess this will need multiple POCs first to find what makes the most sense.

As an alternative, consider Cypress. It can support shadow DOM with some helper functions.
https://github.com/cypress-io/cypress/issues/830#issuecomment-402262740

FYI it looks like they are looking into WebKit via Puppeteer!
https://github.com/GoogleChrome/puppeteer/issues/3879#issuecomment-459865627

Sharing the setup I'm currently using in Aybolit:
https://github.com/web-padawan/aybolit/pull/3

Regarding the tests, one thing where we could use Puppeteer is performance testing.
Created an example: https://github.com/web-padawan/wc-jest-puppeteer-demo

Closing as this is not in my current list of priorities.

As an update, we ended up going with WebDriver, although we have some pain points around shadow dom/setting input fields on Firefox.


Reduce the technical debt accumulated from the begining :(

Refactored server side routes. Previously it was in a shambles. Obviously this code was written by me.

It will be done along other developments


pip install breaks pip / fails

I've googled around and I think there's some kind of dependency problem; after installing flask-sentinel with pip, pip itself breaks (we get this error):
cffi.api.CDefError: 'point_conversion_form_t' has no values explicitly defined: refusing to guess which integer type it is meant to be (unsigned/signed, int/long)
It looks to be related to this discussion: https://github.com/graphite-project/graphite-web/issues/1721, which in turn references others—but all of these look like they should be fixed at this point in time.
I'm able to fix pip with apt-get remove python-cffi, per this thread, but then attempts to pip install flask-sentinel result in some kind of cryptography compile error.
This issue may need to be passed along to whatever dependency is causing it, but as pip install flask-sentinel is the entry point for the problem for me, this seems like the best place to file the issue.

I think I may have figured it out... this seems to work:
apt-get install libssl-dev
pip install flask-sentinel


Demo

Hello, can I specify a setting somewhere so that I can test your product on a demo account?

Thank you!

Is this an error due to time or is there something wrong with the api key?api key for demo account
`qwe@qwe-virtual-machine:~/Sunflow-Cryptobot$ python3 sunflow.py

*** Sunflow Cryptobot ***

Symbol    : MNTUSDT
Spread    : 0.1 %
Profit    : 0.1 %
Limit     : 250
*** Preloading ***
2024-07-16 14:47:48.92 | MNTUSDT: preload.py: check_files: All folders and files checked
2024-07-16 14:47:48.92 | MNTUSDT: preload.py: get_ticker: session: get_tickers
2024-07-16 14:47:49.45 | MNTUSDT: preload.py: get_ticker: Initial ticker loaded
2024-07-16 14:47:49.45 | MNTUSDT: preload.py: get_info: session: get_instruments_info
2024-07-16 14:47:49.76 | MNTUSDT: database.py: load: Database contains 0 buy transactions and 0.00 MNT was bought
2024-07-16 14:47:49.76 | MNTUSDT: preload.py: check_orders: Checking all order on exchange
2024-07-16 14:47:49.76 | MNTUSDT: database.py: save: Database contains 0 buy transactions and 0.00 MNT was bought
2024-07-16 14:47:49.76 | MNTUSDT: orders.py: rebalance: session: get_wallet_balance
2024-07-16 14:47:50.31 | MNTUSDT: defs.py: log_error: Exception: API key is invalid. (ErrCode: 10003) (ErrTime: 14:47:50).
Request → GET https://api.bybit.com/v5/account/wallet-balance: accountType=UNIFIED&coin=MNT.
2024-07-16 14:47:50.31 | MNTUSDT: defs.py: log_error: *** Terminating Sunflow, error to severe! ***
2024-07-16 14:47:50.31 | MNTUSDT: defs.py: log_error: API key is invalid. (ErrCode: 10003) (ErrTime: 14:47:50).
Request → GET https://api.bybit.com/v5/account/wallet-balance: accountType=UNIFIED&coin=MNT.
Traceback (most recent call last):
File "/home/qwe/Sunflow-Cryptobot/sunflow.py", line 636, in
if config.database_rebalance: all_buys = orders.rebalance(all_buys, info)
File "/home/qwe/Sunflow-Cryptobot/orders.py", line 383, in rebalance
equity_wallet = equity_safe(wallet['result']['list'][0]['coin'][0]['equity'])
KeyError: 'result'
`

2024-07-16 14:56:29.70 | MNTUSDT: preload.py: get_ticker: {'time':<PHONE_NUMBER>578, 'lastPrice': 0.7566, 'symbol': 'MNTUSDT'}
I don't understand what the problem is, I turned on debug, it showed what is above, I switched it to normal time and it coincides with my time on the computer. I also tried to change the time zones, it didn't help, I changed the time itself manually to the one that indicates and still the same error

2024-07-16 14:56:29.70 | MNTUSDT: preload.py: get_ticker: {'time':<PHONE_NUMBER>578, 'lastPrice': 0.7566, 'symbol': 'MNTUSDT'}  I don't understand what the problem is, I turned on debug, it showed what is above, I switched it to normal time and it coincides with my time on the computer. I also tried to change the time zones, it didn't help, I changed the time itself manually to the one that indicates and still the same error

FYI Sunflow always works with UTC time.

Okay, thank you


Pretrained model which can be loaded with 'load_from_train_checkpoint' method

Hello, I would like to load your pretrained model by using the "load_from_train_checkpoint" in train.py in order to continue the training. The idea is to do transfer learning by learning a few steps on new images. It looks like that the pretrained model you provided (e4e_ffhq_encode.pt) is not suitable because it's missing some information like 'discriminator_state_dict' and more. I believe it is only for inference. Do you have a model which is suitable for further training? Thank you very much!
Edit: Got it running. I just loaded the wrong model.

Sorry to bother, do you find checkpoint of ffhq latent discriminator?


New Landing Page Layout: PhoneGap Build

I've revised the layout of the PhoneGap Build docs landing page, and am suggesting that the overview content (currently displayed on the landing page on staging) be moved to a sub-section titled "Overview" - refer to #191 .
Otherwise, the mock-up (PSD - Layer Comp "PhoneGap Build Landing") includes revised intro content and the page content navigation.

Related to what is on staging:

[ ] The first paragraph beneath the page title should be styled with slightly larger than body, grey text (mimicking what is found on the homepage). Currently, the styling on the docs homepage is inline as
style="color:#888888;font-size:1.35rem;line-height:1.9rem;"
[ ] The first paragraph text should be edited to read: PhoneGap Build is a cloud service for compiling PhoneGap applications. These docs will get you started, but if your question isn’t answered here you can always check out the community forum.

The first paragraph on staging includes the text "The first paragraph text should be edited to read" - that needs to be deleted.
Also in the first paragraph, funky characters being displayed in place of apostrophe in the word "isn't"

The text below the content sub-menu ("Here are some of the benefits that PhoneGap Build provides:"....through to "...ensuring everyone is working on the most up-to-date version.") is contained on the "Overview" page, and should be deleted from the landing page.

The benefits text below the content sub-nav is still there. it needs to be deleted.

ah sorry I missed it. Fixing now.

looks good on staging


bug: extraDeploy is defined as a value under values.yaml but there is no implementation

Hello,
extraDeploy is defined under values.yaml but there is no implementation around it: https://github.com/backstage/charts/blob/main/charts/backstage/values.yaml#L38-L39
Seems like this helm chart is following Bitnami's chart structure (together with Bitnami's common), so it would be a matter of creating a new template file as such: https://github.com/bitnami/charts/blob/main/bitnami/argo-cd/templates/extra-list.yaml.

Hah, no worries! Thank you for fixing this!


pass parameters to new forms when model is namespaced

When model is namespaced, the prepopulation of the new form via params didn't work.
That should fix it.

Why is this fix needed? Isn't it enought to pass 'cms~basic_page' => {title: 'Hello'}?

No it didn't work, I committed a test for this case.

@mshibuya i see the same issue.

@loicginoux could you rebase these commits in one ? (might this is blocker for merge)

I am having the same issues with forms.. Would be great if proposed PR would be merged

Merged in, thanks!


Issue-141: Turn on jwt validation for host-api

Added the new parameters for turning on jwt validation for host-api

PR for py-agent code for enabling JWT-Auth

Please rebase

Rebasing done.


Add Publisher Success and Failure Channels

Similar to RabbitMQ ConfirmAck and ConfirmNack channels.
Requires https://github.com/spring-projects/spring-kafka/pull/396
See https://github.com/spring-cloud/spring-cloud-stream/issues/916

I don't think we need this level of abstraction.
The KinesisMessageHandler exposes standard AWS AsyncHandler for similar approach.
But here we can rely on the org.apache.kafka.clients.producer.Callback or at least ProducerListener.
That would be already end-user implementation to send to some channel or not.

I think it's a common use case; and we have a precedence with the AMQP endpoints.

Also, SCSt needs access to the Message<?> object, which is not available outside of handleRequestInternal.


Ban Innards Out from BH

http://www.smogon.com/forums/threads/bh7-suspect-vote-2-innards-out.3598631/

Apparently I was misinformed and this hasn't actually been announced by E4 Flint yet, so I've been advised by Chloe to say wait until E4 Flint announces it to merge this. Or just close it and do it yourself if you want to.

ok it's been announced, this is safe to be merged now


Fix refs/remotes/origin/HEAD is not a symbolic ref

Fixes #5

Thank you 🙏

https://rubygems.org/gems/rubocop-changed/versions/0.0.5


Wechaty is All You Need: Python, Go, and Java Translation Project

We already have Wechaty in TypeScript, It will be not too hard to translate the TypeScript(TS) to Python, Go, and Java languages because wechaty has only 3,000 lines of the TS code, they are well designed and de-coupled by the wechaty-puppet abstraction. So after we have translated those 3,000 lines of TypeScript code, we will almost be done.
As we have already an ecosystem of Wechaty in TypeScript, so we will not have to implement everything in other languages, especially, in Feb 2020, we have finished the @chatie/grpc service abstracting module with the wechaty-puppet-hostie implementation.
The Wechaty Way
Python Wechaty

Announcement: Issue #13
Repo: https://github.com/wechaty/python-wechaty

Go Wechaty

Announcement: Issue #1
Repo: https://github.com/wechaty/go-wechaty

Java Wechaty

Announcement: Issue #1
Repo: https://github.com/wechaty/java-wechaty

Architecture
The following diagram shows out that we can reuse almost everything in TypeScript, and what we need to do is only the block located at the top right of the diagram: Wechaty (Python).
  +--------------------------+ +--------------------------+
  |                          | |                          |
  |   Wechaty (TypeScript)   | | Wechaty(Other Languages) |
  |                          | |  Python, Go, Java, etc.  |
  +--------------------------+ +--------------------------+

  +-------------------------------------------------------+
  |                 Wechaty Puppet Hostie                 |
  |                                                       |
  |                (wechaty-puppet-hostie)                |
  +-------------------------------------------------------+

+---------------------  @chatie/grpc  ----------------------+

  +-------------------------------------------------------+
  |                Wechaty Puppet Abstract                |
  |                                                       |
  |                   (wechaty-puppet)                    |
  +-------------------------------------------------------+

  +--------------------------+ +--------------------------+
  |      Pad Protocol        | |      Web Protocol        |
  |                          | |                          |
  | wechaty-puppet-padplus   | |(wechaty-puppet-puppeteer)|
  +--------------------------+ +--------------------------+
  +--------------------------+ +--------------------------+
  |    Windows Protocol      | |       Mac Protocol       |
  |                          | |                          |
  | (wechaty-puppet-windows) | | (wechaty-puppet-macpro)  |
  +--------------------------+ +--------------------------+

Example: How to Translate TypeScript to Python
There's a 100 lines class named Image in charge of downloading the WeChat image to different sizes.
It is a great example for demonstrating how do we translate the TypeScript to Python in Wechaty Way:
Image Class Source Code

TypeScript: https://github.com/wechaty/wechaty/blob/master/src/user/image.ts
Python: https://github.com/wechaty/python-wechaty/blob/master/src/wechaty/user/image.py

If you are interested in the translation and want to look at how it works, it will be a good start from reading and comparing those two Image class files in TypeScript and Python at the same time.
To-do List

TS: TypeScript
SLOC: Source Lines Of Code

Wechaty Internal Modules

[ ] Class Wechaty @wj-mCat

TS SLOC(1160): https://github.com/wechaty/wechaty/blob/master/src/wechaty.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class Contact

TS SLOC(804): https://github.com/wechaty/wechaty/blob/master/src/user/contact.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class ContactSelf

TS SLOC(199): https://github.com/wechaty/wechaty/blob/master/src/user/contact-self.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class Message

TS SLOC(1054): https://github.com/wechaty/wechaty/blob/master/src/user/message.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class Room

TS SLOC(1194): https://github.com/wechaty/wechaty/blob/master/src/user/room.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class Image @wj-mCat

TS SLOC(60): https://github.com/wechaty/wechaty/blob/master/src/user/image.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[x] Class Accessory @huan

TS SLOC(179): https://github.com/wechaty/wechaty/blob/master/src/accessory.ts
[x] Code
[x] Unit Tests
[ ] Documentation

[ ] Class Config @wj-mCat

TS SLOC(187): https://github.com/wechaty/wechaty/blob/master/src/config.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class Favorite

TS SLOC(52): https://github.com/wechaty/wechaty/blob/master/src/user/favorite.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class Friendship

TS SLOC(417): https://github.com/wechaty/wechaty/blob/master/src/user/friendship.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class MiniProgram

TS SLOC(70): https://github.com/wechaty/wechaty/blob/master/src/user/mini-program.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class RoomInvitation

TS SLOC(317): https://github.com/wechaty/wechaty/blob/master/src/user/room-invitation.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class Tag

TS SLOC(190): https://github.com/wechaty/wechaty/blob/master/src/user/tag.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class UrlLink

TS SLOC(107): https://github.com/wechaty/wechaty/blob/master/src/user/url-link.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

Wechaty External Modules

[ ] Class FileBox

TS SLOC(638): https://github.com/huan/file-box/blob/master/src/file-box.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class MemoryCard

TS SLOC(376): https://github.com/huan/memory-card/blob/master/src/memory-card.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class WechatyPuppet

TS SLOC(1115): https://github.com/wechaty/wechaty-puppet/blob/master/src/puppet.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

[ ] Class WechatyPuppetHostie

TS SLOC(909): https://github.com/wechaty/wechaty-puppet-hostie/blob/master/src/grpc/puppet-client.ts
[ ] Code
[ ] Unit Tests
[ ] Documentation

Multi-language Wechaty Getting Started Repositories:

Python: https://github.com/wechaty/python-wechaty-getting-started/issues/1
Java: https://github.com/wechaty/java-wechaty-getting-started/issues/1
Go: https://github.com/wechaty/go-wechaty-getting-started/issues/1

If you want to get started with Wechaty in those languages, please feel free to use them and let us know what you think!

Multi-language Wechaty Beta Released!

TypeScript Wechaty Getting Started
Python Wechaty Getting Started
Go Wechaty Getting Started
Java Wechaty Getting Started
Scala Wechaty Getting Started

Multi-language Wechaty Beta Released! We have Python, Go, Java, and Scala released on June 19, 2020!
See: https://wechaty.github.io/2020/06/19/multi-language-wechaty-beta-release/

After eight months, we now have lots of language of Wechaty available for all our developers who are using different programming languages!
:point_down: Multi-language Wechaty

Wechaty - Conversatioanl SDK for Chatot Makers (TypeScript)
Python Wechaty - Conversational SDK for Chatbot Makers written in Python
Go Wechaty - Conversational SDK for Chatbot Makers written in Go
Java Wechaty - Conversational SDK for Chatbot Makers written in Java(Kotlin)
Scala Wechaty - Conversational SDK for Chatbot Makers written in Scala
PHP Wechaty - Conversational SDK for Chatbot Makers written in PHP
.Net(C#) Wechaty - Conversational SDK for Chatbot Makers written in .NET(C#)

Thank you to all our contributors and authors of our multi-language wechaty projects, Wechaty get better and better with great works from you, and I appreciate all the efforts from our community, let's close this issue and keep moving on, to make the chatbot to be easy to be developed!


[Question] Performance.

Hey there!
Thanks for the great library.
I'm curious why FFI calls are so slow. In my experience Python's ctypes library is much faster, but in general Node.js is faster. I understand this isn't really related, but I'm really curious.
Is this just a Node.js limitation?

Would be nice, if anybody can answer here.
I also thought about implementing some calculations with rust and execute that from REST/JSON API (node/express).

I believe that the reason of this gap is because of libffi version that ffi uses is a bit of old one. We have a 2012ish version, but the actual release dated 2014: https://github.com/atgreen/libffi/releases/tag/v3.2.1. Moving forward would be a huge amount of work because libffi uses Autoconf and ffi uses GYP, and those ain't compatible. There are many hand carfted source files that would be a huge effort to reproduce for new versions without having a test system for each supported platforms.
I really doubt that this module should be the way that node provides for ffi in the future. There should be an integrated and supported way in the core that gotta do this properly. There is an active discussion about it: https://github.com/nodejs/NG/issues/3


Fix the (re)loading of database from LDAP

When the database has a large number of users the current batch method will not work - it needs to be done on a per-user basis.

LDAP interface is being deprecated in COmanage - switch to using REST interface.

Implemented COmanage REST-API-based method of retrieving users. Slow, but reliable. Requires multiple queries for each user to get all the data, unlike LDAP. First COmanage is queried for all active users, then for each active user using OIDC claim sub and numeric id, get name, email and insert with a new UUID.
Required redefining COmanage parameters under database/init.py (in addition to init.py) due to circular dependencies.

Implemented COmanage REST-API-based method of retrieving users. Slow, but reliable. Requires multiple queries for each user to get all the data, unlike LDAP. First COmanage is queried for all active users, then for each active user using OIDC claim sub and numeric id, get name, email and insert with a new UUID.
Required redefining COmanage parameters under database/init.py (in addition to init.py) due to circular dependencies.


Update considerations to match the new design

Decisions
Added new Consideration model over updating the existing LocalPolicy and LocalPolicyArea models. This means it will need the reviewing component of the new structure before it can be merged.
Screenshots

Updated the assessment report that's used in a couple of places:

Also updated the conditions component that's used in an accordion as part of other assessment tasks:


Do not run calico and overlay metrics test on Windows

High-level description
Calico and Overlay is currently not supported on Windows.
Corresponding DC/OS tickets (required)

D2IQ-ID JIRA title / short description.

Related tickets (optional)

D2IQ-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot request-review @jongiddy @jeschkies @DominikDary

@mesosphere-mergebot changelog-not-required test only change

@mesosphere-mergebot label Ship It


The visualizer for traffic light perception module doesn't pop out anything?

Hello everyone,
I am trying to use the tl_visualizer.cc under modules/perception/traffic_light/visualizer to visualize traffic lights. I wanted to know the procedure to use the visualizer given a map which was already run on a testing car.
I tried to load the map into apollo's map folder and tried to check the topics which are being published upon when that particular map was selected while apollo was running. Then, I tried to run the executable(perception traffic light visualizer) which is in bazel bin. Can someone confirm if it is the same procedure?

visualizer will show image when a light can be queried from map. May be you're not in the map zone or no signal is in front of you

There's another way to see the visualization:
vim modules/perception/conf/perception.conf
find --output_debug_img
set to true
rerun perception , when querying hdmap successful,you will see the video

Thanks. That worked.


Device dehydration v2

add support for device dehydration v2 i.e. org.matrix.msc3814
implement rest client methods and models
implement flows for creating and storing the dehydrated device pickle in in 4s as well as recovering it to use for device rehydration
implement methods for creating, retrieving, deleting dehydrated devices as well as consuming the messages stored on the backend in between sessions
delete previous implementation

NB: this requires a new Crypto SDK releases, current implementation based on https://github.com/matrix-org/matrix-rust-sdk/tree/poljar/device-dehydration

@poljar, are we ok to remove the previous device dehydration implementation? Are we sure it is not use somewhere?

I'm afraid I have no idea.

I might have missed it, but I don't see the sharing part of 4S for the new secret?
m.secret.request/m.secret.send?

That's not part of this, even if it were it wouldn't implemented here. The only thing the client would need to do is persist the pickle key in the crypto store so Rust has access to it.
But for this initial version of device dehydration, resumption of the rehydration process and periodic rotation of the dehydrated device didn't make the cut.


Building Extension Catalog Image on Mac results in empty files.txt

Setup

Rancher version: v2.8.5
Rancher UI Extensions: 1.2.0
Browser type & version: Chrome Version 127.0.6533.88 (Official Build) (arm64)

Describe the bug

I am able to build an ECI image on my MacBook Pro with the following command:
yarn publish-pkgs -cf -r <harbor_registry> -o <project> -i ''

but the output includes the following error:
Extension version: 0.1.0
find: -printf: unknown primary or operator

which results in an empty dist-pkg/<pkg>-<version>/files.txt file and causes the following error to show up when attempting to install my extension in the Rancher UI:

The reason for this is that the -printf option is not supported by the defaultfind command on macOS because it uses the BSD version of find, which doesn't have this option. The -printf option is available in the GNU version of find, commonly found on Linux systems.
The problematic code is https://github.com/rancher/dashboard/blob/master/shell/scripts/extension/bundle#L46.
To Reproduce

Run the yarn publish-pkgs -c ... command on a Mac that uses the BSD version of find.
Result
The image gets build but it has an invalid/empty files.txt file which causes issues in Rancher during the installation of the extension because it can't find the code for that package in the extension.
Expected Result

The bundle script should be able to populate files.txt using a command that works on any *nix OS.

/backport v2.9.3

/backport v2.8.9