[Docs] Use of Scoop as the Windows package manager to install mesheryctl

Current State:
Meshery's documentation for Windows installations does not highlight the mesheryctl Scoop package as one that is available.
Desired State:
Two pages need updated:

the Using mesheryctl guide to suggest using Scoop first, before suggesting that the binary can been directly downloaded (direct download should be the catch-all option).
the Windows platform page should highlight that installing mesheryctl is the first step to deploying Meshery.

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

@tripathyprateek any luck here?

Yes @leecalcote I tried it on my local machine and it works. I will make required changes in the Docs and update accordingly. Sorry I was blocked with other works for a while.

Any luck here?

Any luck here?

@favourch, you’re help in documenting and testing this is much appreciated.

@favourch, you’re help in documenting and testing this is much appreciated.

@favourch would you like to try your hand at this?

@favourch would you like to try your hand at this?

I'm on it @leecalcote . I'll reach out for clarity on expectations on the slack channel.

I'm on it @leecalcote . I'll reach out for clarity on expectations on the slack channel.

Awesome. Thank you, @favourch

Awesome. Thank you, @favourch

@leecalcote It looks like a lot has changed in the codebase because I cant seem to navigate to /docs/guides/mesheryctl#windows

@leecalcote It looks like a lot has changed in the codebase because I cant seem to navigate to /docs/guides/mesheryctl#windows

@favourch no sweat. I think we have this covered now. I'll close this issue now. if you don't find scoop info in the docs, please reopen this issue.


the big release todo

rendering
drinkable tea items:

[x] colour based on ingredients
[x] variable transparency based on strength
[x] dynamically updated whenever ingredients change

tea cauldron

[ ] animation of placed ingredient fading into cauldron
[x] still tea cauldron - dynamic colour with crossfade out of scope for now -- may come later
[x] boiling tea cauldron - dynamic colour
[ ] boiling effect (reference: minecraft 1.18 trailer water effects)

misc

[x] automatic asset generation

functionality
tea cauldron

[x] steeping
[x] storing ingredient data
[x] works with everything in tea ingredient tag
[x] insertion and removal
[x] boiling
[x] still tea cauldron (non-boiling cauldron that has tea in it)

tea receptacles

[x] storing all necessary data
[x] custom stack names
[ ] dynamic food components
[x] automatic data updating

content

[ ] various tea ingredients (different kinds of tea leaves, different spices, berries, etc)
[ ] teacups
[ ] teapots
[ ] mugs
[ ] decorative items

all of this is now listed in https://github.com/users/ix0rai/projects/3/views/1


iCheck added

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot pleaes check the changes


fix(http-client)!: use platform native system certs

Feature or Problem
This PR enables the HTTP client provider to use the platform's native certificate store at runtime, as specified in https://crates.io/crates/hyper-rustls via rustls-native-certs. As far as I know this doesn't introduce any platform specific dependencies, but it can fail in platform specific ways.
Worth noting this would also enable loading a set of certs using the SSL_CERT_FILE environment variable, however we don't pass environment variables to providers by default. We may need to consider adding that as a separate feature.
Related Issues

Release Information
http-client v0.10.0
Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification
Draft pending verification this fixes an issue on machines with additional certificates

We could load from a config value instead for the path location. We should definitely decide how to configure local system access things in a standard way


The terminal shell CWD "my_folder" does not exist

Environment data

VS Code version: 1.3.8
Extension version (available under the Extensions sidebar): 2019.9.34911
OS and version: Windows 10 Home v.1803
Python version (& distribution if applicable, e.g. Anaconda): 3.7.1
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda

Expected behaviour
Set my_directory as started folder for the debugger on the terminal.
Run debugger and got that folder on terminal
Actual behaviour
Got The terminal shell CWD "my_folder" does not exist error
Steps to reproduce:

set a desired directory in the launch.json file in cwd parameter as follows:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File (Integrated Terminal)",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "cwd": "gapcv", // <- my_folder
            "env": {
                "DJANGO_SECRET_KEY":"***"
            },
            // "args": ["test_db"]
        }
    ]
}

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
> conda env list
> ~\Miniconda3\envs\python37\python.exe c:\Users\david\.vscode\extensions\ms-python.python-2019.9.34911\pythonFiles\testing_tools\run_adapter.py discover pytest -- -s --cache-clear
cwd: c:\Users\david\github\gapml\CV
> conda info --json
> conda info --json
> conda info --json
> ~\Miniconda3\envs\python37\python.exe c:\Users\david\.vscode\extensions\ms-python.python-2019.9.34911\pythonFiles\testing_tools\run_adapter.py discover pytest -- -s
cwd: c:\Users\david\github\gapml\CV

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
The terminal shell CWD "gapcv" does not exist
onDidNotificationChange @ notificationsAlerts.ts:40

Hello @virtualdvid 👋 Thank you for reaching out.
Could you please:

update your issue using our issue template?
and provide a sample repo we could use to reproduce the issue?

Thanks!

Instead of using a folder name, please could you try adding the fully qualified path to the CWD. I believe thats the problem.

Thanks @DonJayamanne that solved the issue. Interesting it was working with the single folder name in the version 1.3.6.


chore(samples): update Autoclass Sample for v2.1 features

Depends on https://github.com/googleapis/java-storage/pull/2258

Now that libraries-bom has been released with the feature I've rebased and updated the sample and the samples test.
@cojenco I applied the value changes in the sample you recommended.

Thanks for working on this! Could we also update the storage_get_autoclass sample to demonstrate the newly added fields?
https://github.com/googleapis/java-storage/blob/main/samples/snippets/src/main/java/com/example/storage/bucket/GetBucketAutoclass.java

LGTM, could we showcase the new fields in the get_autoclass sample too? Thank you @BenWhitehead


Cleanup code

Currently, code is a monolithic blob of routes without abstractions.
Migrate everything to helper promises and map()s.

[ ] Have proper error handling

[ ] Shared default error handler, that will always do req.flash()

[ ] Switch to async/await syntax, and Promises APIs
[ ] Split across multiple files


Google calendar sensor fails to initialize

Home Assistant release (hass --version):
0.45.0.dev0
Python release (python3 --version):
Python 3.4.2
Component/platform:
Google calendar
Description of problem:
About half of the times I start Home Assistant, the sensor throws an exception when importing the 3rd party google library. My guess is that it collides with import of the discovery component. Not sure why it works sometimes and sometimes not though.
Expected:
It should work every time I start Home Assistant.
Problem-relevant configuration.yaml entries and steps to reproduce:
google:
  client_id: !secret google_client_id
  client_secret: !secret google_client_secret

Traceback (if applicable):
2017-05-08 19:20:13 ERROR (MainThread) [homeassistant.components.calendar] Error while setting up platform google
Traceback (most recent call last):
  File "/home/homeassistant/home-assistant/homeassistant/helpers/entity_component.py", line 155, in _async_setup_platform
    entity_platform.schedule_add_entities, discovery_info
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/homeassistant/home-assistant/homeassistant/components/calendar/google.py", line 39, in setup_platform
    for data in disc_info[CONF_ENTITIES] if data[CONF_TRACK]])
  File "/home/homeassistant/home-assistant/homeassistant/components/calendar/google.py", line 39, in <listcomp>
    for data in disc_info[CONF_ENTITIES] if data[CONF_TRACK]])
  File "/home/homeassistant/home-assistant/homeassistant/components/calendar/google.py", line 50, in __init__
    super().__init__(hass, data)
  File "/home/homeassistant/home-assistant/homeassistant/components/calendar/__init__.py", line 71, in __init__
    self.update()
  File "/home/homeassistant/home-assistant/homeassistant/components/calendar/__init__.py", line 137, in update
    if not self.data or not self.data.update():
  File "/home/homeassistant/home-assistant/homeassistant/util/__init__.py", line 303, in wrapper
    result = method(*args, **kwargs)
  File "/home/homeassistant/home-assistant/homeassistant/components/calendar/google.py", line 66, in update
    service = self.calendar_service.get()
  File "/home/homeassistant/home-assistant/homeassistant/components/google.py", line 247, in get
    from googleapiclient import discovery as google_discovery
ImportError: cannot import name 'discovery'

Hi !
Problem confirmed here with version 0.44.1
I upgraded yesterday from 0.38 (was working fine) and I just noticed hass didn't started properly.
++

Was this ever fixed.  I am having the same problem

same issue here

Same here, any word on a fix?

Still having the issue on 0.51.

@antsar posted a solution that worked for me on issue #7717.


Remove --dry-run from Kani.

Description of changes:
I also ensured that --verbose was always printing the commands kani-driver invokes and I added a Running: prefix to the command being printed so they are grepable.
Resolved issues:
Resolves #1936
Related RFC:
Call-outs:
I kept the --dry-run and turned into an error for now as a reminder to people.
Testing:

How is this change tested? Modified tests

Is this a refactor change?

Checklist

[ ] Each commit message has a non-empty body, explaining why the change was made
[ ] Methods or procedures are documented
[ ] Regression or unit tests are included, or existing tests cover the modified code
[ ] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

Looks good. Thanks!
It might be useful to add a Kani-specific prefix to the "Running:" line, e.g.
[Kani] Running: ...

but the current form is fine too.
Also, might want to say "Executing command:" intead of "Running".

Sure, I can add a tag. I do prefer Running though since it is shorter and it matches cargo output. Is that OK?

Sure, I can add a tag. I do prefer Running though since it is shorter and it matches cargo output. Is that OK?

Sure.


Poetry for Rasa (tensorflow 2.x)

Proposed changes:

Add poetry to rasa (tf2 branch)
Update .travis.yml

Important: This PR doesn't update any of the dependencies — it's a relatively straightforward process since now, but it's better to wait before we finish the migration to tf2 before doing that.
Status (please check what you already did):

[x] made PR ready for code review
[x] updated the documentation
[ ] updated the changelog

How to use poetry?

Clone the repo
Install poetry (curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | python on linux/mac os)
Run poetry install and wait

Poetry manages a virtual environment and installs everything to it. You can activate your environment by running poetry shell or by executing all the commands with poetry run.
For example, after a successful installation, you'll have two ways of running executing rasa:
$ poetry shell
$ rasa

or
$ poetry run rasa

The same is true for any other command, for example:
$ poetry run black rasa tests

@tabergma you don't need to create virtual environments manually — just execute poetry install and it will care about all the rest.
It also seems like you've tried using pip install -e . — am I right about it?

now that tf2 merged in the changes from master we can start updating this I think

I've just rebased it, will continue with moving Poetry-related changes from .travis.yml to GH Actions

sounds good - I'd assume the commands should be pretty similar to the rasa-sdk ones

@tmbo yes, updating commands was relatively easy.
now finishing dealing with dependencies

@alwx please let me know once the PR is ready for another review - eager to get this into the next release 🚅

@alwx did you already check if binder still works?


Support UnitSystem in w()

Originally posted by @adrn in https://github.com/GalacticDynamics/galax/pull/96#discussion_r1468888819

Fixed.


Publish the Loop Demo

Publish the loop demo on the main branch and thus the website.

Note: Don't approve this until #45 has been merged as that needs to go onto the main branch too.


FetchError: ETimeout

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.23.1
Regression From
No response
Architecture
x64
Storage Explorer Build Number
No response
Platform
Windows
OS Version
No response
Bug Description
Unable to retrieve child resources.
Details:
{
"name": "FetchError",
"message": "request to https://neapnpepgen2.blob.core.windows.net/?comp=list&include=metadata failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443",
"stack": "FetchError: request to https://neapnpepgen2.blob.core.windows.net/?comp=list&include=metadata failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443\n    at ClientRequest. (C:\Users\Kevin.Languedoc\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\node_modules\node-fetch\lib\index.js:1491:11)\n    at ClientRequest.emit (node:events:394:28)\n    at TLSSocket.socketErrorListener (node:_http_client:447:9)\n    at TLSSocket.emit (node:events:394:28)\n    at emitErrorNT (node:internal/streams/destroy:157:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n    at processTicksAndRejections (node:internal/process/task_queues:83:21)",
"type": "system",
"errno": "ETIMEDOUT",
"code": "ETIMEDOUT"
}
Steps to Reproduce
Launch App
Expand account
trying to expand blob containers ---> error
Actual Experience
See bug description
Expected Experience
No response
Additional Context
No response

@kevinlanguedoc can you give using system proxy setting a try? You can read more about it here: https://docs.microsoft.com/en-us/azure/storage/common/storage-explorer-network#use-system-proxy-preview

Closing due to lack of response. If you are still encountering this problem we recommend opening an Azure support ticket from the portal. You can also open a new issue here.


Hello! I have trained the network, but when testing, only the ap value appears, there is no saved image, how can I get it?

thank you very much!

In addition, I ran demo.py and found that there was an error. After I modified it, the saved image was a blank image. What should I do?


Sandman Graphical/Memory Glitch/Bugs?

In one particular seed, I got the following to occur.

I decided to speed up the emulation at the end, where it eventually freezes the game. The emulator recognizes the button presses being made, but the game would not respond at that point outside of loading a save state or resetting.
At some point in round 1, past the 2:30 minute mark, Sandman might freeze up in place while attempting to do the Dreamland Express after knocking you down. Depending on when you get up, weird effects could occur. The game glitches out completely, leading to hilarious and confusing moments during fights (similar to having a physical copy having graphical glitches). The game crashes. The game freezes, then sets the timer to reach the end of the round, causing the intermission to occur with the fight music still going (which resets at the sound of the bell). There's so much that can happen from Sandman attempting a Dreamland Express past the 2:30 mark.
This is the first time I've seen this considering that the past hundred or so Sandman's I've gone up against had no guard against one, two, or every punch. This Sandman (and consequently, Bald Bull 1 and 2) had a perfect guard, being vulnerable only during specific frames during their attacks (beatable by human players, but only those who know of said vulnerabilities in the original game).
If you want the seed in question, and to attempt to replicate the issue, here's the seed ID: 2ac90c6e. Just get knocked down past the 2:30 mark, make a save state (for experimentation purposes), then get up on any count. If Sandman freezes up in preparation for the Dreamland Express (if the game doesn't freeze up, and the timer isn't set to 4:00 by this method, he'll still do the attack), you will see a variety of issues here.


draggable view coming under navigationbar

Is ther any fix for not coming under navigationBar. Currently it is coming under navigation bar.

I have also faced the same problem and I fixed this issue in this way.
if draggbleView.frame.origin.y <= 0.0 {
self.draggbleView.frame.origin.y = 0.0
}


feat(pdk): reimplement plugin queues

Summary
This change improves the robustness of plugins that use queues (formerly "batch queues")

Better logging
Implement capacity limits (both # of entries and # of bytes)
Easier to understand configuration parameters
Ability to configure sharing queues between plugin instances
Unit test for queues added

Design doc: https://docs.google.com/document/d/1F9unN4JOV8uA7cZWYSMhd4POG9O4JqJlwlls8rQJnto/edit?usp=sharing
Checklist

[X] The Pull Request has tests
[X] There's an entry in the CHANGELOG
[X] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - #5088

Issue reference
KAG-481 Reimplement plugin queues
KAG-503 http-log plugin doesn't update the config headers when sending logs to server

I started adding changes on #10197 on top of @hanshuebner 's changes. I still need to address:

removal of the assertion
using timer.every
Apart from that I think it moves this PR closer to the finish line.

using timer.every

I have seen @ADD-SP's comments about long-running timers potentially causing memory leaks. I'd like to know more, i.e. what does "long running" really mean and why do such timers cause leaks?
I'm asking because the retry logic completely lives within the handler function and it could be running for a long time, depending on how the queue is configured.  One of my goals with the refactoring was to simplify the code so that instead of creating multiple timers to organize polling and retries, there would just be one control flow.
Rather than splitting this up again, can we maybe figure out how to create a long-running background process that does not rely on timers and callbacks at all?  It seems that underneath, we already have that mechanism as both timer callbacks and worker functions can coexist and are scheduled onto the same system thread already.

using timer.every

I have seen @ADD-SP's comments about long-running timers potentially causing memory leaks. I'd like to know more, i.e. what does "long running" really mean and why do such timers cause leaks?
I'm asking because the retry logic completely lives within the handler function and it could be running for a long time, depending on how the queue is configured. One of my goals with the refactoring was to simplify the code so that instead of creating multiple timers to organize polling and retries, there would just be one control flow.
Rather than splitting this up again, can we maybe figure out how to create a long-running background process that does not rely on timers and callbacks at all? It seems that underneath, we already have that mechanism as both timer callbacks and worker functions can coexist and are scheduled onto the same system thread already.

OpenResty's timer has a memory pool (ngx_pool_t), so if some C function (such as a FFI call) was called in the callback of timer, it might get memory from this pool.
But the ngx_pool_t doesn't really free (even if you call ngx_pfree() manually) a small memory block and also doesn't reuse a small memory block. These blocks will be free when this pool was destroyed.
The pool will be destroyed when the timer was destroyed. So a long-running timer may cause memory leak.

The pool will be destroyed when the timer was destroyed. So a long-running timer may cause memory leak.

Thank you for the explanation - If I understand correctly, the problem is not really the run time, but the accumulation of allocations from the memory pool that can cause issues in the long run.  Is it possible to determine the current size of the pool?  Why is the memory pool tied to the timer callback in the first place?

Is it possible to determine the current size of the pool?

We can't get the current size of the pool.

Why is the memory pool tied to the timer callback in the first place?

In OpenResty, a timer is also a request, but a fake request, in order to adapt to the Nginx's request processing model (state machine).
For Nginx code style, we usually get memory from the pool of current request, so maybe some external lib (such as FFI function) will do this thing.

In OpenResty, a timer is also a request, but a fake request, in order to adapt to the Nginx's request processing model (state machine).

Again, thank you for the very helpful explanation!  Given that, switching from the long-running to timer.every makes a lot of sense, and we may also need implement a queue state machine so that we can run retries in separate invocations of the callback.

I have talked with hans and we think this needs more work before we can merge it in 3.2. I am pulling it out of the milestone.

@mikefero This PR is going to be merged soon.  What do you need from my end to support the integration of the new queue related parameters into Konnect?

Some additional follow-up questions:

90% is an artificial number

Supporting literature or comparable implementations?
90% feels a bit too late for my personal taste.

Plugin isolation?

Can a rogue plugin drain (and enqueue items to a non-shared queue?)
Should a "shared-mode" make sense?

Sharing queues

Ensuring configuration will match is up to the user.
This needs to be very obvious

Otherwise you'll send stuff to the wrong place

Workspace isolated naming?

In big installations people use workspaces as abstraction layer.
Could queues interfere with each other when there is a naming collision?

Performance characteristics?

Old vs new?
Under pressure?

@hbagdi I believe that all review comments are addressed, either by code changes or by adding subtasks to KAG-481.  Please approve if you agree so that I can merge.


Time taken seems longer

I am using 8GB GPU with 32GB CPU intel i5 12 Gen. For an audio file of 485kb with 4min conversation, it is taking 105s. Is this normal?

Processing a 30m file takes around 2 to 3 minutes for me on an rtx 3070 ti
You should investigate where the slowdown on your setup comes from so I can assist with it

I see it is taking longer at this command
[NeMo W 2024-10-22 12:25:31 nemo_logging:349] /root/anaconda3/envs/whisper_diar2/lib/python3.10/site-packages/huggingface_hub/file_download.py:1132: FutureWarning: resume_download is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use force_download=True.
warnings.warn(

this is an issue with model loading from disk, you need to use a faster disk or find a faster way to load the model without internet


Pyright type errors

We recently turned on type checking in tests and found that we had to add a bunch of # type: ignore comments to lines using snapshot. Here's a minimal repro:
from inline_snapshot import snapshot

snapshot({})
snapshot([])

Output:
$ pyright file.py
file.py
  file.py:3:10 - error: Argument type is partially unknown
    Argument corresponds to parameter "obj" in function "snapshot"
    Argument type is "dict[Unknown, Unknown]" (reportUnknownArgumentType)
  file.py:4:10 - error: Argument type is partially unknown
    Argument corresponds to parameter "obj" in function "snapshot"
    Argument type is "list[Unknown]" (reportUnknownArgumentType)
2 errors, 0 warnings, 0 informations

pyright wants to know the type of the argument, probably because of the snapshot(obj: T) -> T overload meaning it needs to know the type of obj to know what the return value is. And empty generic containers have unknown type arguments.
Maybe there's another way, but I think it's probably best to drop the overloads and just have def snapshot(obj: Any=undefined) -> Any:. It's not critical for users to typecheck the return value of snapshot since it will get asserted in tests anyway.

Sorry, but I'm not able to reproduce your issue.
❯ bat file.py
───────┬────────────────────────────────────────────────────────────────────────────────────────────────
       │ File: file.py
───────┼────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ from inline_snapshot import snapshot
   2   │
   3   │
   4   │ snapshot({})
   5   │ snapshot([])
   6   │
───────┴────────────────────────────────────────────────────────────────────────────────────────────────

❯ pyright --version
pyright 1.1.359

❯ pyright file.py
0 errors, 0 warnings, 0 informations

Try with this config:
[tool.pyright]
typeCheckingMode = 'strict'

ok, I can reproduce your error, but I found out that mypy --strict file.py gives me 211 errors and complains that everything in inline-snapshot needs a type.
I don't know what the best approach here is.
I will make a new release with this fix now.
I will later add types to inline-snapshot, which is probably a good idea in general.

Thanks for fixing the issue.
I don't get any errors with mypy --strict. Maybe because I installed it from PyPI it didn't check the whole library, just the snapshot function?

mypy --strict works also.
fixed in 0.8.1


Dashboard in Power BI

Creating an interactive dashboard in Power BI
1.Importing dataset
2.Data Preprocessing and DAX queries.
3.Designing Dashboard and insights

I have knowledge regarding creating meaningful insights using visualization tools like Power BI and tableau.
will be glad i get an opportunity to work on this

I would like to work on this, please assign this issue to me. I also have prior experience working on Tableau. https://drive.google.com/file/d/1DaT2B5wDwMQB8MM6BcOx3gw67KegJPhq/view?usp=drive_link

I would also like to work on this subject. Feel free to assign this issue to me.


Add /man alias for /help

Since /help is PS' equivalent to man and I keep doing this by accident all the time

...my main worry is that man is actually an English word and this could confuse people...

Vote, I guess.

What platform(s) use this alias? I've literally never used or heard of this alias myself, but I'm also not against it.

What platform(s) use this alias? I've literally never used or heard of this alias myself, but I'm also not against it.
Every POSIX-compliant OS (Linux, BSD, Solaris, etc.)

(Including macOS, for the record. Basically every common OS except Windows.)

I'm against joke commands tbh but if you're legitmately doing this wrong all the time I guess it's fine. Not feeling strongly about this

I guess this really doesn't cause any harm anyway

I don't follow how this is a "joke command," but yeah, in that case, I think this is a good idea.

Yeah I don't see how man would be a joke command, It seems like it's a shortened way to say "manual"

Looks like consensus is mostly in favor.


Retrieving function's return type

Hi,
Is there any way I can get the deduced return type of a decompiled function object (HxCFunc)?
The only solution I came up with so far was stripping the first word from the function's text (i.e. f.cstr.split()[0]), but there's probably a better way to do so.
Did I miss anything?
Thanks in advance 🙏

Hello,
So there is currently no way to get the return type directly of a function. You have to go through the type of the function (BTypeFunc accessible through BipFunction().type) and then access its return type (BipFunction().type.return_type or BipFunction().type.return_type.str if you want the string). This should work (I hope) in both cases where you have typed your function or when it is deduced by IDA. If you are at the HexRays level you will want to fetch back the BipFunction (through the bfunc property for example).
A few notes about this: I agree that getting directly the return type of a function should be made more accessible from directly the function object. The reason I did not do this yet is that there is actually a confusion in Bip (my fault) between the type from the HexRays decompiler and the one returned by the basic IDA disassembler. The type property of the BipFunction object should actually be for the HxCFunc object. I intend to fix that (and a few other things) for the next stable release of Bip which I intend to be at the end of this month.
I hope this answers the question, I am closing the issue but do not hesitate to reopen if needed. I will also send you a message on this issue for keeping you updated of the change when the next stable release is actually done.


godep: Unable to find dependent package golang.org/x/sys/unix in context of /Users/apple/workspace/go/src/github.com/Sirupsen/logrus

on go 1.5.2
I cant work out why it screams for logrus.
gedw99-MacBook-Pro:backend apple$ go env
GOARCH="amd64"
GOBIN="/Users/apple/workspace/go/bin"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/apple/workspace/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GO15VENDOREXPERIMENT=""
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common"
CXX="clang++"
CGO_ENABLED="1"

gedw99-MacBook-Pro:backend apple$ godep save -r
godep: Unable to find dependent package golang.org/x/sys/unix in context of /Users/apple/workspace/go/src/github.com/Sirupsen/logrus
gedw99-MacBook-Pro:backend apple$ go get github.com/Sirupsen/logrus
gedw99-MacBook-Pro:backend apple$ godep save -r
godep: Unable to find dependent package golang.org/x/sys/unix in context of /Users/apple/workspace/go/src/github.com/Sirupsen/logrus
gedw99-MacBook-Pro:backend apple$

This is a bug i think.
Once i did a go get golang.org/x/sys/unix, then godep was happy.
So it should be included in godep binary or whatever ?

dw99-MacBook-Pro:backend apple$ godep save -r
godep: Unable to find dependent package golang.org/x/sys/unix in context of /Users/apple/workspace/go/src/github.com/Sirupsen/logrus
gedw99-MacBook-Pro:backend apple$ go get golang.org/x/sys/unix
gedw99-MacBook-Pro:backend apple$ godep save -r
gedw99-MacBook-Pro:backend apple$

```

It is a transitive dependency that "go get" does not fetch, but can be required on other platforms to build the package. Older versions of godep relied on the go tool, but we no longer do, for exactly this reason.
I plan on enhancing this workflow, especially around GO15VENDOREXPERIMENT.
Sent from my iPhone

On Dec 22, 2015, at 06:06, Ged<EMAIL_ADDRESS>wrote:
This is a bug i think.
Once i did a go get golang.org/x/sys/unix, then godep was happy.
So it should be included in godep binary or whatever ?
dw99-MacBook-Pro:backend apple$ godep save -r
godep: Unable to find dependent package golang.org/x/sys/unix in context of /Users/apple/workspace/go/src/github.com/Sirupsen/logrus
gedw99-MacBook-Pro:backend apple$ go get golang.org/x/sys/unix
gedw99-MacBook-Pro:backend apple$ godep save -r
gedw99-MacBook-Pro:backend apple$
—
Reply to this email directly or view it on GitHub.

I've hit this as well while attempting cross platform compilations on our CI build server. I added a go get golang.org/x/sys/unix call prior to the GOOS=x GOARCH=y go build step, and it resolved the "error"... although it does seem superfluous to make a call to fetch a core Go package and/or include it in our Godeps.

@mikeatlas golang.org/x/sys/unix is not a "core" Go package. If you godep save and record that dep you can remove the need to fetch it with go get.

Also ran into this with github.com/mattn/go-isatty. GOOS=solaris godep save ./... got me the right deps, but according to #161 the platform-specific fetching was fixed with the latest versions of GoDep.
Pulling from master on godep, and re-installing resolved this for me. maybe take a look at that?

@geofffranks Yes, this should be fixed as of a month or two ago. I'm going to close this issue, but feel free to re-open if it's still failing with deps saved by v55.
Thanks!

I'm seeing this during save, it's quite confusing.
$ godep version
godep v55 (darwin/amd64/go1.6)
$ godep save ./cmd/...
godep: Package (golang.org/x/sys/unix) not found

Is this because go get doesn't bother installing golang.org/x/sys/unix anymore?

Something you are requiring is transitively pulling in golang.org/x/sys/unix across OSes.

I am running go 1.6 and godep v56, and still having this issue with logrus:
$ godep version
godep v56 (darwin/amd64/go1.6)

$godep restore
godep: Dep (github.com/Sirupsen/logrus) restored, but was unable to load it with error:
    Package (golang.org/x/sys/unix) not found
godep: Error checking some deps.

go get golang.org/x/sys/unix. After the restore you probably need to re-save to record golang.org/x/sys/unix.

I had the same issue. Saidly, chinese people can't asscess golang.org, and I had to download the package via proxy manually to solve the dependency issue...

the terminals_solaris.go  in the Logrus package has a build constraints // +build solaris, which is where golang.org/x/sys/unix get imported.
I build my project on centos, so I don't need unix package for it, but godep still claims that Unable to find dependent package golang.org/x/sys/unix
Should we add some options into godep to generate dependency following those build constraints?

Sorry. I should have replied sooner. This got lost in email. :-(
I'd much rather do this by making this configurable via an array in Godps.json. Plus ensure that our code handles all the various permutations of build tags. And maybe default to what is hard coded now.

Any updates on this? Running Go1.6 and Godep 70 on OSX and still getting this error with godep save ./...

I'm also having problems with the golang.org/x/sys/unix when saving the applications dependencies.
@freeformz
However, would this problem be related to vendoring libraries that also do vendoring?

@diogogmt This is likely due to the fact that godep ignores arch build constraints, since it doesn't know where you will finally compile code. It's very common for people to dev on macOS, but build on Linux for instance.

still facing this issue. is there a known workaround? i build everything on mac.

getting same error on
$ godep version
godep v74 (darwin/amd64/go1.7)

$ go version
go version go1.7 darwin/amd64

Weird, after updating from 1.6.2 to 1.7 on macos 10.8.x I'm running into the same error
$ godep save
godep: WARNING: Godep workspaces (./Godeps/_workspace) are deprecated and support for them will be removed when go1.8 is released.
godep: WARNING: Go version (go1.7) & $GO15VENDOREXPERIMENT= wants to enable the vendor experiment, but disabling because a Godep workspace (Godeps/_workspace) exists
godep: Package (golang.org/x/sys/unix) not found

go get golang.org/x/sys/unix
FWIW: Now that work has started for a native solution (
https://groups.google.com/forum/#!msg/go-package-management/P8TehVoFLjg/Ni6VRyOjEAAJ),
I'm likely not going to be working on godep very much. In the interim I'm
suggesting people migrate to govendor (https://github.com/kardianos/govendor)
if they are having problems with godep.
On Mon, Aug 29, 2016 at 1:47 AM thomasmodeneis<EMAIL_ADDRESS>wrote:

Weird, after updating from 1.6.2 to 1.7 on macos 10.8.x I'm running into
the same error
$ godep save
godep: WARNING: Godep workspaces (./Godeps/_workspace) are deprecated and support for them will be removed when go1.8 is released.
godep: WARNING: Go version (go1.7) & $GO15VENDOREXPERIMENT= wants to enable the vendor experiment, but disabling because a Godep workspace (Godeps/_workspace) exists
godep: Package (golang.org/x/sys/unix) not found
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tools/godep/issues/377#issuecomment-243067806, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAAZ2J3a_gmAQLRBLJ_1jKfauSK9ybhks5qkpycgaJpZM4G51iU
.

PS: You will need to add "solaris" to the list of ignores in
vendor/vendor.json if you move to govendor or you will still need
x/sys/unix.
On Mon, Aug 29, 2016 at 11:10 AM Edward Muller<EMAIL_ADDRESS>wrote:

go get golang.org/x/sys/unix http://golang.org/x/sys/unix
FWIW: Now that work has started for a native solution (
https://groups.google.com/forum/#!msg/go-package-management/P8TehVoFLjg/Ni6VRyOjEAAJ),
I'm likely not going to be working on godep very much. In the interim I'm
suggesting people migrate to govendor (
https://github.com/kardianos/govendor) if they are having problems with
godep.
On Mon, Aug 29, 2016 at 1:47 AM thomasmodeneis<EMAIL_ADDRESS>wrote:

Weird, after updating from 1.6.2 to 1.7 on macos 10.8.x I'm running into
the same error
$ godep save
godep: WARNING: Godep workspaces (./Godeps/_workspace) are deprecated and support for them will be removed when go1.8 is released.
godep: WARNING: Go version (go1.7) & $GO15VENDOREXPERIMENT= wants to enable the vendor experiment, but disabling because a Godep workspace (Godeps/_workspace) exists
godep: Package (golang.org/x/sys/unix) not found
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tools/godep/issues/377#issuecomment-243067806, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAAZ2J3a_gmAQLRBLJ_1jKfauSK9ybhks5qkpycgaJpZM4G51iU
.

I have the same problem when building docker image. It can be solved by adding below go get
RUN go get golang.org/x/sys/unix

go get golang.org/x/sys/unix

Doesn't seem to work anymore as it's become a redirect to https://godoc.org/golang.org/x/sys/unix

I encounter the same problem, my environment is:
macOS 10.12.1
godep v75 (darwin/amd64/go1.7)
go version go1.7 darwin/amd64
govendor works well.

Please specify which branch you want to merge with.
See git-pull(1) for details.
git pull <remote> <branch>

package golang.org/x/sys/unix: exit status 1

After I delete the pakage, and run go get again, it works know. :)

I am getting the same error. @ashcrow if the package is no longer hosted at golang.org why do other packages still reference that import path?
godep: error downloading dep (golang.org/x/sys/unix): unable to determine git status exit status 128

When I try to go get the package directly, I get this error:
$ go get -v -u golang.org/x/sys/...
Fetching https://golang.org/x/sys?go-get=1
https fetch failed: Get https://golang.org/x/sys?go-get=1: net/http: TLS handshake timeout
package golang.org/x/sys/...: unrecognized import path "golang.org/x/sys/..." (https fetch: Get https://golang.org/x/sys?go-get=1: net/http: TLS handshake timeout)

The odd part is that when godep restore is running/hanging, I can't access https sites on my entire system (i.e. any browser, curl, etc). I think godep is hanging because of the TLS handshake timeout, but I don't know where this timeout is stemming from - is it something on my system (like a misconfigured certificate) or is it a problem with a Go tool, or is it an issue with the code repositories' hosting?
The TLS timeout happens with this package as well:
$ go get -v gopkg.in/yaml.v2
Fetching https://gopkg.in/yaml.v2?go-get=1
https fetch failed: Get https://gopkg.in/yaml.v2?go-get=1: net/http: TLS handshake timeout
package gopkg.in/yaml.v2: unrecognized import path "gopkg.in/yaml.v2" (https fetch: Get https://gopkg.in/yaml.v2?go-get=1: net/http: TLS handshake timeout)

Turns out this was an issue with OpenDNS https://github.com/fsnotify/fsnotify/issues/204#issuecomment-294367347

I'm seeing similar errors. Has anyone identified a solution?
$ go get -v -u golang.org/x/tools/cmd/gorename
Fetching https://golang.org/x/tools/cmd/gorename?go-get=1
https fetch failed: Get https://golang.org/x/tools/cmd/gorename?go-get=1: dial tcp <IP_ADDRESS>:443: connect: host is down
package golang.org/x/tools/cmd/gorename: unrecognized import path "golang.org/x/tools/cmd/gorename" (https fetch: Get https://golang.org/x/tools/cmd/gorename?go-get=1: dial tcp <IP_ADDRESS>:443: connect: host is down)

Turns out mine was an issue with Little Snitch (a network filter), although Im still not clear why.

fix this by download packages manually.
mkdir -p $GOPATH/src/golang.org/x/
cd !$
git clone https://github.com/golang/sys.git


clean up get_activities_response duplication and inefficiency btw bridgy and a-u

bridgy's Source class have a set of methods that parallel a-u's Source class: get_activities[_response], get_comment, get_like, etc. some of bridgy's per silo Source subclasses extend these to add custom functionality that's not in a-u. notably, facebook fetches extra stuff.
this has two problems. first, it's confusing, since the methods have the same names, and do the same things, and the two base Source classes are even named the same, but they're separate class hierarchies. this is bad design.
second, it leads to inefficiency. @kylewm shrewdly discovered (despite my protestations :P) that the mf2 handlers actually go through bridgy's version of the methods to do OPD, which results in something like 7 or 8 extra unused API calls to render a simple response mf2 page.
the Right Thing here is to formalize, clean up, and move the extended functionality from bridgy into a-u, and drop all the parallel methods. not sure how much work that would be.
a smaller fix for the inefficiency might be to make OPD use the as_source methods when possible instead of bridgy's.

as mentioned in #498, as part of this, we should de-dupe photo post and photo object ids, make sure we only return one copy of their activity, and also that the id is always canonicalized. details in https://github.com/snarfed/bridgy/issues/498#issuecomment-148961255

so all of this should be a big noop refactoring...but it does change one meaningful thing: our /sharedposts?ids=... and comments?filter=stream&ids=... calls now use photo ids (ie object_id) for photos, instead of photo post ids. details in #498. testing in the graph api explorer seems to show that those calls return the same data, but it's facebook, so i still expect the worst. we'll see.


[IOTDB-578] Cluster module should use the same thrift version with io…

…tdb-parent

thrift 0.13.0 used by the stand-alone IoTDB will cause bugs in Mac OS and that is why we use a separate version in the distributed version.
PLEASE, do not merge any outside code without informing the committers who are working on this branch.


Document that "contributor" is another term for "approved submitter"

Feature Summary and Justification
This adds an example and a note saying that "contributor" is another term for "approved submitter."
Reddit's API and associated documentation use the term "contributor" where the website uses the term "approved submitter." PRAW currently follows the API documentation only, which makes it hard to find things by searching for "approved submitter."
References

https://www.reddit.com/r/redditdev/comments/72v97e/praw_invite_user_to_inviteonly_subreddit/

Thanks!


gst123: init at 0.4.1

Description of changes
GStreamer based command line media player
The program gst123 is designed to be a more flexible command line player in
the spirit of ogg123 and mpg123, based on GStreamer. It plays all file formats
supported by GStreamer, so if you have audio/video collections which contain
different file formats, like flac, ogg and mp3, you can use gst123 to play all
your audio/video files.
https://space.twc.de/~stefan/gst123.php
Other distributions (like Ubuntu) package gst123 since many years. I am the upstream developer.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

gst123

Thanks for implementing all the changes, everything is just perfect now.
This PR will be merged as soon as the CI is done.

Oops. Going to submit a PR to fix this. Nice catch!


[WIP] asset catalog suggestion

Related to #7 Support for asset catalogs

thanks for this! This code could definitely use the love.
I'm happy to merge this in.  Though how do people typically deal with version references in podspecs? Is there way to centralize the version information somehow? I don't like all the places I'll have to change it when we do another release.

@varenc I wouldn't merge it yet, I haven't tested it all yet, I'll mark the PR as WIP until it's at least in a "works for me" state. As regards the version, if you include a podspec here and use a ruby podspec it can do anything it likes to read the version from elsewhere. Typically I do just manually tag the repo in question and bump the version in the podspec. Alternatively you could generate the json podspec from a template..


Convert WNDT82 to WNDT83

Target Live Date: 2020-04-01

[x] This has been reviewed and approved by @kaycebasques
[x] I have run npm test locally and all tests pass.
[x] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

CC: @petele

Whoops!
There were 20 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2020/03/devtools.md#L223 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2020/03/devtools.md#L100 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/2020/03/devtools.md#L103 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/2020/03/devtools.md#L31 - Common typo found: 'colour' Should it be 'color'? Please use American spellings. See: https://developers.google.com/style/spelling
src/content/en/updates/2020/03/devtools.md#L31 - Common typo found: 'colour' Should it be 'color'? Please use American spellings. See: https://developers.google.com/style/spelling
src/content/en/updates/2020/03/devtools.md#L31 - Common typo found: 'colour' Should it be 'color'? Please use American spellings. See: https://developers.google.com/style/spelling
src/content/en/updates/2020/03/devtools.md#L81 - Line must be at most 100 characters
src/content/en/updates/2020/03/devtools.md#L167 - Line must be at most 100 characters
src/content/en/updates/2020/03/devtools.md#L192 - Line must be at most 100 characters
src/content/en/updates/2020/03/devtools.md#L216 - Line must be at most 100 characters
src/content/en/updates/_shared/discover.md#L252 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/_shared/discover.md#L98 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L123 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L124 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L131 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L132 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L136 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L142 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L142 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L106 - Line must be at most 100 characters


ActiveSupport Instrumentation API support

Adds ActiveSupport notification events.
Events

request.approval
cancel.approval
reject.approval
approve.approval
approve_with_execute.approval
execute.approval

Event parameters

payload[:request] Approval::Request object
payload[:user] User object
payload[:comment] Approval::Comment object, if present

Fixed!


refactor main.go

split main() into separate flagXyz() functions that should process the flag and if needed do os.Exit with 0 or 1 status on their own
fix default LogLevel. Do not set the default for flag so we can check if a user really set the flag. So it will be clear precedence from lowest to high (default -> config -> flag)

main() is still pretty big but I think this is a good balance. It shouldn't provide one clear purpose. It needs to:

create flags
check flags in the right order
run different initialization methods in the right order
run the main app in the end if needed

gocyclo before:
85 main main main.go:52:1

gocyclo after:
24 main flagServiceInstall main.go:298:1
19 main main main.go:54:1
12 main flagInputOutput main.go:196:1

LGTM. I just added some comments to make the error checking for handleFlagServiceInstall more clear


Add star lists

This PR adds star lists to Gitea. It is a feature of GitHub that was requested here.
This feature allows you to sort your stared repos into lists. So you can e.g. create a list with your favourite cli tools. This allows you to better find repos you started before and show other people repos of a specific topic you like.
Screenshots:

The Migration will be added after everything is reviewed.

This is new to me, could you share where in github I can see this feature.

You can see it on your stars page. You already have one list.

You can see it on your stars page. You already have one list.

Then i will give a review to thos Pr today on priority.

What's the status of this PR?

What's the status of this PR?

It is waiting to be reviewed

What's the status of this PR?

It is waiting to be reviewed

I don't think you have resolved all the concern reivew questions.


agent: fatal error: concurrent map writes

Bug report
Scaling out the amount of nodes of a kubernetes cluster, some of the cilium agent (~18%) failed on the first run with the following error : fatal error: concurrent map writes. They all seemed to be working fine after the very next automated restart of the agent process.
at first sight, the error seems quite similar to https://github.com/cilium/cilium/issues/8278
General Information

Cilium version: 1.8.1
Kernel version: 5.4.0-1015-aws
Orchestration system version in use: EKS/1.16.8 (eks.1)
Link to relevant artifacts: previous logs of a failed cilium agent pod

I am happy to provide the sysdump if necessary as it won't fit on this GitHub issue (>10MB).
How to reproduce the issue
I am very uncertain about which environment specifics may be in cause, all I can tell for now is that it never happened until today as I attempted to scale from 5 nodes to 75. All t3a.xlarge in a single AZ. Scaled out via the cluster-autoscaler after increasing the amount of replicas of an httpbin deployment.

Thanks for the report. I think I spotted the issue and will send a PR shortly.

awesome, thanks for the fix @tklauser! 🙇


[feature] Add crates 'relations' and 'relations_procmacro'

Need typed_index_collection to be released first.
Here is a link to the build on my fork for now.

One thought I had. For now, we would need to include both relations and relations_procmacro in our Cargo.toml if we want to use these crates. But maybe we could take inspiration from serde where they're doing something like
serde = { version = "1", features = ["derive"] }

So it might be possible to do something like
relations = { version = "1", features = ["procmacro"] }

for relations = { version = "1", features = ["procmacro"] } you can do that but I don't know if relations can be used without procmacro.
I would let procmacro required and optional later if someone needs relations without procmacro

for relations = { version = "1", features = ["procmacro"] } you can do that but I don't know if relations can be used without procmacro.
I would let procmacro required and optional later if someone needs relations without procmacro

Done in 6881a3c0fc6e2e34fd22c2f55591130ed4f78c4e.


Node is detached from document

GOAL:
I currently am building a script that checks the last few messages in each conversation to see whether i can “mark as done” from a company account. The whole can loop through the list of people and get the messages but at soon as Its time to “mark a conversation as done” the next iteration of the loop breaks because of a “node is detached from the document”

Puppeteer version:
Chrome/83.0.4103.0
Platform / OS version:
Chromium: Version 83.0.4103.0 (Developer Build) (64-bit)
URLs (if applicable):
https://business.facebook.com/
Node.js version:
v13.12.0

What steps will reproduce the problem?

Log in to a FB business account
mark more than 2 Facebook conversations as done using a certain ID

Please include code that reproduces the issue.
for (let i = 0; i < section.length; i++) {
      try {
        await section[i].click();
        await page.waitForSelector('._suc._su6._5bpf');
        await page.$eval('._suc._su6._5bpf', form => form.click() ); // Here is where the issue happens
  } catch (err) {
    if ((err.message == 'Node is either not visible or not an HTMLElement' ||
      err.message == 'Node is detached from document')) {
        delay(2000);
    } else {
      stop = true;
    }
    console.log(Error(err), err.message, err.number);
  }
}

[Screenshots]

This selector will only have one occurrence for each page you are on so the ('._suc._su6._5bpf') only has once occurrence. until the conversation moves to another person in the list like this:
as it iterates:

What is the expected result?
I expect the for loop to continue checking the conversations
What happens instead?
Error: Error: Node is detached from document
at /Users/mahirhiro/headless-chrome/index.js:61:17 ...

@mahirhiro how did you solve this? I get the same issue on a simple button.

@t1a2l I couldn't find a fix using puppeteer so I switched to selenium haha.

I had the same problem, the error was the element was available inside the HTML, but not was available for puppeter, because puppeteer needs to "see" or "needs to have something visible" to touch it or click it.
The solution was to click through HTML  instead of puppeter
//puppeteer handler
await row_element.click()

//html handler (solution)
await page.evaluate((element => {
  element.click()
}, row_element)

Hello everyone,
Thanks @KevinHCH for your solution i am trying to apply it on my project but i didn't get it yet

It’s basically same as stale element exception in selenium world.
Solution what i found is to use waitforselector and/or network idle wait.
Regards,
Gurudatt
On Mon, 17 May 2021 at 1:39 PM, Ahmad-Hendi @.***>
wrote:

Hello everyone,
Thanks @KevinHCH https://github.com/KevinHCH for your solution i am
trying to apply it on my project but i didn't get it yet
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/puppeteer/puppeteer/issues/6033#issuecomment-842113150,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLBBTD4MFKVRWRTQXOUS5LTODFLPANCNFSM4OAN4PAA
.

Thanks for your comment @gurudattgd04 , i will try it tomorrow !

In my case i use at the end of the for an a await page.waitForTimeout(1000) an it works perfect now

I had the same problem, the error was the element was available inside the HTML, but not was available for puppeter, because puppeteer needs to "see" or "needs to have something visible" to touch it or click it. The solution was to click through HTML instead of puppeter
//puppeteer handler
await row_element.click()

//html handler (solution)
await page.evaluate((element) => {
  element.click()
}, row_element)

I had this same issue and this fixed it for me.  Thanks!

We no longer support Node < 14, please try this again with the latest version of Puppeteer and Node >= 14. If the issue still occurs, please reopen this issue and update the description :)


Fix for warning after upgrade to React 0.15.2.

Guten Morgen vom Flughafen Leipzig!
Closes issue #299. Squelches messages like:
warning.js:44 Warning: LookStateless(...): childContextTypes cannot be defined on a functional component.

Greets :) Already leaving Germany? How was your time here :P? Thanks again for the ongoing PRs.


Consolidated DM5 Future Enhancements

Consolidated DM5 Outcome Improvements other than Status Bit improvements for Table A-6-1 and A-6-2.
Current DM5 Issues consolidated by this issue.
https://github.com/Equipment-and-Tool-Institute/j1939-84/issues/968
https://github.com/Equipment-and-Tool-Institute/j1939-84/issues/1032
Reduce Severity of Non OBD Responses (with no status bit support) to Info
https://github.com/Equipment-and-Tool-Institute/j1939-84/issues/515
Enhance OBD Device Recognition:
Add a warning message specifically for 0, FB, FC, FD, And FE.
Expand the definition of devices qualified as HD OBD ECUs (as needed)
Task 5 requires recognition of XEV/BEV, provide for 1Bh (27) now to avoid changing these tests twice.

Proposed Text and Rationale
Consolidated-DM5-Issues-n1099.docx

DM5 concepts reviewed 4/15/2022.  These consolidated suggestions are ready to go.

These changes in consolidated text for section 6.

The following issues were closed as consolidated text superseding them is now available.
https://github.com/Equipment-and-Tool-Institute/j1939-84/issues/968
https://github.com/Equipment-and-Tool-Institute/j1939-84/issues/1032
https://github.com/Equipment-and-Tool-Institute/j1939-84/issues/515

Were we expecting these issues to be resolved in v3.1.4 since this issue is listed as "closed"?

Blue items in The task 5 artifact may have been done early …
This was closed in favor of the consolidated text.

I am still encountering some of these issues in v3.1.9.
The proposed draft text above does not appear to include the change from WARN to INFO for DM5 responses in sections <IP_ADDRESS>.a and <IP_ADDRESS>.a.  These sections point to "Section A.6.3.a" of the specification which still includes the wording below as of the latest draft release:

Example from v3.1.9 testing:
12:05:31.4143 Global DM5 Request
12:05:31.4168 18EAFFF9 [3] CE FE 00 (TX)
12:05:31.4180 18FECE03 [8] 00 00 05 00 00 00 00 00
DM5 from Transmission #1 (3): OBD Compliance: Not intended to meet OBD II requirements (5), Active Codes: 0, Previously Active Codes: 0
WARN: <IP_ADDRESS>.a (A6.3.a) - Non-OBD ECU Transmission #1 (3) responded
12:07:17.9712 Global DM5 Request
12:07:17.9748 18EAFFF9 [3] CE FE 00 (TX)
12:07:17.9792 18FECE03 [8] 00 00 05 00 00 00 00 00
DM5 from Transmission #1 (3): OBD Compliance: Not intended to meet OBD II requirements (5), Active Codes: 0, Previously Active Codes: 0
WARN: <IP_ADDRESS>.a (A6.3.a) - Non-OBD ECU Transmission #1 (3) responded

This issue was closed with the creation of new text in the task 5 artifact.
6.1.3	DM5: Diagnostic Readiness 1
<IP_ADDRESS>	Actions
a.	Global  DM5 [send Request (PG 59904) for PG 65230 (SP 1220, OBD Compliance)].
b.	Create “OBD ECU”  list (comprised of all ECUs that indicate OBD compliance values other than 0, 5, FBh, FCh, FDh, FEh, or FFhthat indicate 13h, 14h, 22h, or 23h for OBD compliance) for use later in the test as the “OBD ECUs.”
<IP_ADDRESS>	Fail Criteria
a.	Fail if no ECU reports as an OBD ECU.
b.	Fail if any ECU responds with a NACK (to DM5, PG 65230 request).
c.	Fail if a BEV vehicle response provides a value other than 1Bh (27) for OBD compliance.
d.	Fail if any response from a function 0 device provides OBD Compliance values of 0, 5, FBh, FCh, FDh, FEh, or FFh.
e.	Fail if a vehicle with a US EPA/CARB CI or SI engine does not provide OBD Compliance values of 13h, 14h, 22h, or 23h.
<IP_ADDRESS>	Warn/Info Criteria
a.		Warn if more than one ECU responds with a value for OBD compliance where the values are not identical (e.g., if one ECU reports 13h and another reports 22h, if one reports 13h and another reports 11h, or if one ECU reports 00h and another reports 14h).
b.	Warn if any response received from a non-OBD ECU provides OBD Compliance values of 0, FBh, FCh, FDh, FEh, or FFh.
c.	Info for DM5 replies from non-OBD ECUs.
// The above changes incorporate #1099

6.1.13	DM5: Diagnostic Readiness 1: Monitor Readiness
<IP_ADDRESS>	Actions
a.	Global DM5 [send Request (PG 59904) for PG 65230 (SPs 1218-1223)].
b.	Display monitor readiness composite value in log for OBD ECU replies only.
<IP_ADDRESS>	Fail/Warn Criteria
a.	Fail/warn per Section A.6, Criteria for Readiness 1 Evaluation.
b.	Fail if no OBD ECU reports DTC counts of 0 for both active and previously active faults.
c.	Fail if no OBD ECU provides DM5 with readiness bits showing monitor support.
d.	Warn if any individual required monitor, except Continuous Component Monitoring (CCM) is supported by more than one OBD ECU.      // Delete d. Per #1151. Added strike through font format.
<IP_ADDRESS>	Actions2
a.	DS DM5 to each OBD ECU.
<IP_ADDRESS>	Fail Criteria
a.	Fail if any difference compared to data received during global request.
b.	Fail if NACK not received from OBD ECUs that did not respond to global query.
6.1.14	DM26: Diagnostic Readiness 3
<IP_ADDRESS>	Actions
a.	Global DM26 [send Request (PG 59904) for PG 64952 (SPs 3301-3305)].
i.	Create list by OBD ECU address of all data and current status for use later in the test.
b.	Display monitor readiness composite value in log for OBD ECU replies only.
<IP_ADDRESS>	Fail Criteria
a.	Fail if any response for any monitor supported in DM5 by a given ECU is reported as “0=monitor complete this cycle or not supported” in SP 3303 bits 1-4 and SP 3305 [except comprehensive components monitor (CCM)].                         // and except misfire for MY 2019+ engines.
b.	Fail if any response for each monitor not supported in DM5 by a given ECU is also reported in DM26 as “1=monitor not complete this monitoring cycle” in SP 3303 bits 5-7.
c.	Fail if any response for each monitor not supported in DM5 by a given ECU is also reported in DM26 as “0=monitor enabled for this monitoring cycle” in SP 3303 bits 1 and 2 and SP 3304.
d.	Fail if any response from an ECU indicating support for CCM monitor in DM5 reports “0=monitor disabled for rest of this cycle or not supported” in SP 3303 bit 3.
e.	Fail if any response indicates number of warm-ups since code clear (WU-SCC) (SP 3302) is not zero.
f.	Fail if any response indicates time since engine start (SP 3301) is not zero.
g.	Fail if no OBD ECU provides DM26.
// SOW Confirmed existing criteria. Check Unit Tests vs. confirmation analysis in SOW.
<IP_ADDRESS>	Warn Criteria
a.	Warn if any individual required monitor, except Continuous Component Monitoring (CCM) is supported by more than one OBD ECU.
<IP_ADDRESS>	Actions
a.	DS DM26 to each OBD ECU.
<IP_ADDRESS>	Fail Criteria
a.	Fail if any difference compared to data received during global request.
b.	Fail if NACK not received from OBD ECUs that did not respond to global query.

A.6	CRITERIA FOR READINESS 1 EVALUATION
Section A.6 describes criteria for evaluation of readiness bits in SPs 1221, 1222, and 1223 (bytes 4-8) of the DM5 message (PG 65320). Parallel construction can be applied to SPs 3303, 3304 and 3305 (bytes 4-8) in the DM26 message (PG 59904) which share the same assignments of monitors to bits, except for the monitor inhibit status in DM26, but operates on a smaller time scale.

The response from each responding device shall be evaluated separately using a through d below:
a.	Fail if no response from an OBD ECU (ECUs that indicate 13h, 14h, 22h, or 23h for OBD compliance).
b.	Fail if any response does not report supported and complete for comprehensive components support and status (SP 1221, byte 4, bit 3 = 1 and bit 7 = 0), except when all the bits in SPs 1221, 1222, and 1223 are sent as 0 as defined in SAE J1939-73 paragraph 5.7.5.
c.	Fail if any response does not report 0 = ‘complete/not supported’ for the status bit for every unsupported monitors (i.e., any of the support bits in SP 1221, byte 4 bits 1-3, 1222 byte 5 bits 1-8, or 1222 byte 6 bits 1-5 that report 0 also report 0 in the corresponding status bit in SP 1221 and 1223).
d.	Fail if any response does not report 0 for reserved bits (SP 1221 byte 4 bits 4 and 8, SP 1222 byte 6 bits 6-8, and SP1223 byte 8 bits 6-8).
All responses received from all responding OBD devices shall be combined with appropriate ‘AND/OR’ logic to create a composite vehicle readiness response: (Do not use responses from non-OBD devices to create a composite vehicle readiness response.)
a.	If one or more responses indicates 1 = supported in the support bit for a monitor,
i.	Then the composite vehicle readiness shall indicate 1 = supported for that support bit/monitor,
ii.	Else it shall indicate 0 = unsupported for that support bit/monitor;
b.	If one or more responses indicates the status bit for a supported monitor is 1 = not complete,
i.	Then the composite vehicle readiness shall indicate 1 = not complete for that status bit/monitor,
ii.	Else it shall indicate 0 = complete for that status bit/monitor).
c.	Fail if composite vehicle readiness does not meet any of the criteria in Table A4.
d.	Warn if any individual required monitor, except Continuous Component Monitoring (CCM) is supported by more than one OBD ECU.
3.	All responses received from non-OBD ECU shall be evaluated using the criteria below:
a.	Warn if any response from non-OBD ECU received.
b.	Warn if all the monitor status and support bits in any reply from a non-OBD ECU are not all binary zeros or all binary ones.
SP 1222, bit 7 (Exhaust Sensor Heater Monitor Support) may appear as a 0 with a warning message, instead of a requiring a failure message in 2013 MY engines. Future engine model years (c. 2016) shall unbundle all heater monitoring support and support both bits 7 and 6. When SP 1222, bit 7 is provided as a 0 (not supported) after the 2013 engine model year, SP 1223, bit 7 (Exhaust Sensor Heater Monitor Status) shall be provided as 0 (complete).
Specific implementations may require the immediate setting of the misfire monitor status bit to zero (complete). Refer to 13 CCR 1971.1 for such conditions. Observation of a zero (complete) for a misfire monitor status bit after fault codes have been cleared shall be marked with a warning message.


Filter Android logs by the pid of the remote process

Fixes https://github.com/flutter/flutter/issues/6849


Install Error

How can this bug be reproduced?
I get the following error when running npm install.

Please List the Following:

OS & version: 10.14
Node version (node -v) [Node v4+ is required] : v6.11.0
FoundationPress version (see line 3 in package.json): 2.10.4
Foundation version (found in node_modules/foundation-sites/package.json) : N/A

This fixed it: https://github.com/olefredrik/FoundationPress/issues/1312


[BUG] Device Command with "/" in command name not creating switch

Describe the bug
I have a device that is giving me the command InputDisc/Phono but it says "No function list found on startup when i try to make a switch to be able to select the input, because the "/" is a modifier to make toggle commands, so I can not select this because the "/" is a modifier to make toggle commands, so I can not select this input on my device.
To Reproduce
Steps to reproduce the behavior
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

IOS (please complete the following information):

Version
Device:

Logs
Your log in debug mode (-D option)
Config
{
"name": "Harmony Hub",
"hubIP": "",
"hubName": "Harmony Hub",
"TVAccessory": false,
"switchAccessories": false,
"publishGeneralMuteSwitch": false,
"publishGeneralVolumeSlider": false,
"publishGeneralVolumeSwitches": false,
"linkVolumeControlToTV": false,
"publishSwitchActivitiesAsIndividualAccessories": true,
"devicesToPublishAsAccessoriesSwitch": [
"NAD Amp|Power;PowerOn/PowerOff",
"NAD Amp|Mute;Mute",
"NAD Amp|Volume Up;VolumeUp",
"NAD Amp|Volume Down;VolumeDown",
"NAD Amp|Media Player;InputMp",
"NAD Amp|Video;InputVideo",
"NAD Amp|Turntable;InputDisc/Phono"
],
"publishDevicesAsIndividualAccessories": false,
"showCommandsAtStartup": true,
"platform": "HarmonyHubWebSocket"
},
Additional context
Add any other context about the problem here.

Hi,
thanks for reporting. Will try to sanitise names in order to be compliant. Meanwhile, can't you rename it in harmony app ?

I was not able to rename it, I had to create a new command in harmony hub from IR as a work around.

Ok right, if it is a pre learned you can't renamed . Will fix that asap

this one involves a lot of changes (probably going to json config instead of string based). Will postpone sorry.

Hey all, was just wondering if there were any updates regarding this issue 😊

Hi, like I said it involves a lot of changes in the plugin, and I don't have a lot of time to spend on it sorry.

Sure would be nice if this could be fixed. I have a number of devices that suffer from this problem.

Adding to this request, have the same issue for both zones of my Onkyo Amp.

Running into the same problem with an Onkyo Amp.
Could this be worked around by adding a \ in front of the /?

I changed the check in the code from / to \ and now I can add switches for commands with / in it.


Update Dockerfile.develop

Updated kubebuilder ,envtest for s390x. I am able to build the developer image successfully on s390x. I have added small snapshot below
[root@m1305001 modelmesh-serving]# make run fmt
make: go: Command not found
which: no controller-gen in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
Makefile:216: warning: overriding recipe for target 'fmt'
Makefile:153: warning: ignoring old recipe for target 'fmt'
./scripts/build_devimage.sh "podman"
/usr/bin/sha1sum
Pulling dev image kserve/modelmesh-controller-develop:9f6853f0cc3268cb...
Image kserve/modelmesh-controller-develop:9f6853f0cc3268cb does not exist yet
Building dev image kserve/modelmesh-controller-develop:9f6853f0cc3268cb
[1/2] STEP 1/9: FROM registry.access.redhat.com/ubi8/ubi-minimal:8.9 AS go-toolset
[1/2] STEP 2/9: ARG TARGETOS
--> Using cache b0ca21c485d0f83033c13da6d1311c30e2631ca6e0066f9cf139b82b7b642479
--> b0ca21c485d0
[1/2] STEP 3/9: ARG TARGETARCH
--> Using cache 88086c84e4af70f942ad6a10c0a383e8422f64f13fcfd6b67c83f18045217bb4
--> 88086c84e4af
[1/2] STEP 4/9: ARG GOLANG_VERSION=1.21.6
--> Using cache 0676771de5fa097afebd0a36550778231d56ce13ba4b5a5546d604d0887b1d2e
--> 0676771de5fa
.....
....
[2/2] STEP 28/31: RUN true     && go install github.com/onsi/ginkgo/v2/ginkgo     && ginkgo version     && true
Ginkgo Version 2.13.0
--> 891c5c632c98
[2/2] STEP 29/31: RUN true     && go install sigs.k8s.io/controller-runtime/tools/setup-envtest@latest     && setup-envtest use 1.29     && true
go: downloading sigs.k8s.io/controller-runtime/tools/setup-envtest v0.0.0-20240516231036-f4ca78ebc00a
go: downloading sigs.k8s.io/controller-runtime v0.18.2
go<EMAIL_ADDRESS>requires go >= 1.22.0; switching to go1.22.3
go: downloading go1.22.3 (linux/s390x)
go: downloading github.com/go-logr/zapr v1.2.4
go: downloading github.com/spf13/afero v1.6.0
go: downloading github.com/go-logr/logr v1.2.4
go: downloading golang.org/x/text v0.12.0
go: downloading go.uber.org/multierr v1.10.0
Version: 1.29.3
OS/Arch: linux/s390x
md5: 6FYdZY5YRV6GoxBEQfc/IQ==
Path: /root/.local/share/kubebuilder-envtest/k8s/1.29.3-linux-s390x
--> b8e38d2752bd
[2/2] STEP 30/31: RUN git config --system --add safe.directory /workspace
--> 8f801c4cf95c
[2/2] STEP 31/31: CMD /bin/bash
[2/2] COMMIT kserve/modelmesh-controller-develop:b6daac75d8d3248c
--> bf58bb0633ef
Successfully tagged localhost/kserve/modelmesh-controller-develop:b6daac75d8d3248c
bf58bb0633efd5a0755374845235ea5542be3090ce0fb2a0493919dc61920835
Image kserve/modelmesh-controller-develop:b6daac75d8d3248c has 62 layers
Tagging dev image kserve/modelmesh-controller-develop:b6daac75d8d3248c as latest

/assign @ckadner

I have addressed all the comments . Please review again

@ckadner This PR is not yet merged. It has been already reviewed once as well. Can you please approve the changes


Push / Pull feature sometimes broken

Issue Description:
Note: If this bug occurs in a modpack, please report this to the modpack author. I will of course be reporting this to FTB, but wanted to post here as well. FTB Infinity for minecraft 1.7.10, modpack version 2.60.
What happens:
After server restarts the push / pull features on at least sag mills and alloy smelters ceases to function until you clear all machine configs, break the machine, place it back down, and reconfigure the side you want to push / pull. This happens with ANY connected inventory, it doesn't matter weather it be chests or ME interfaces.
What you expected to happen:
Items from connected inventory get pulled into machine, processed, and returned to inventory.
Steps to reproduce:
1.Place Machine
2.Connect it to an adjacent inventory and configure a side to push / pull or both at the same time.
3.Restart server.
...

Affected Versions (Do not use "latest"):

EnderIO:
EnderCore:
Minecraft: 1.7.10
Forge:

Your most recent log file where the issue was present:
[pastebin/gist/etc link here]

Why didn't you fill out the version numbers?

Sorry i didn't notice that part.
Ender IO: 1.7.10-<IP_ADDRESS>8_beta
EnderCore: 1.7.10-<IP_ADDRESS>_beta
Minecraft: 1.7.10
Forge: <IP_ADDRESS>


Need to pack one entry as library and second entry not as library

Do you want to request a feature or report a bug?

What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Hello. I need to pack one entry as library and other entry not as library.
entry: {
    bundle: './src/client/components/ReactRouter.js',
    'selection': './src/client/components/CertificationSelection/CertificationSelection.js'
  },
  output: {
    path: path.resolve(__dirname, 'build/client'),
    filename: '[name].js',
    chunkFilename: '[id].chunk.js',
    publicPath: '/static/',
    /* I wanna use the following configurations for 'selection' entry only */
    library: '[name]',
    libraryTarget: 'umd',
    umdNamedDefine: true
  }

I don't wanna pack 'bundle' entry as a library. Is it possible now?

1
Any ideas?
Why this issue is closed?

Webpack allows to export multiple configurations. Instead of exporting one configuration I export array of configurations:
module.exports = [
  {
    entry: : './src/...',
    output: {
      path: path.resolve(__dirname, 'build/client'),
      filename: 'bundle.js',
      chunkFilename: '[id].chunk.js',
      publicPath: '/static/'
    },
  },
  {
     entry: {
      'lib': './src/...'
    },
    output: {
      path: path.resolve(__dirname, 'build/client'),
      filename: '[name].js',
      publicPath: '/static/',
      library: '[name]',
      libraryTarget: 'umd',
      umdNamedDefine: true
    },
  }
]

I don't think the multiple configurations make sense, is there any other choice?

I want to use bundle and selection on window object.
For example:
window.LIBRARYNAME.bundle & window.LIBRARYNAME.selection
both on the same LIBRARYNAME object. I tried this:
entry: {
    'bundle': './src/client/components/ReactRouter.js',
    'selection': './src/client/components/CertificationSelection/CertificationSelection.js'
  },
  output: {
    path: path.resolve(__dirname, 'build/client'),
    filename: '[name].js',
    library: "MYLIBRARY",
    libraryTarget: 'window',
  }

If I use both file on the same HTML, the last script file override the previous.
For example, if I write on my html this:
    <script src="bundle.js"></script>
    <script src="selection.js"></script>

My window object is window.MYLIBRARY.Selection, and window.MYLIBRARY.Bundle doesn't exist. How can I use both? Is possible?


GH-910 push need to pass the credentials and a specific tag

now the docker_image ressource (action push) pass the credentials for a
private registry and the specific image tag to the push api-function
Signed-off-by: Christian Leinweber<EMAIL_ADDRESS>Description
Now it is possible to push a specific image tag to a private registry.
Issues Resolved
#910
Check List

[x ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x ] New functionality includes testing.
[x ] New functionality has been documented in the README if applicable
[x ] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

great! if you can resolve the conflict i will get this merged in.


Current Stardate

Hi,
If we use LCARS... let's go full startrek mode then :)
Me and a friend have created a small python script that will show the current stardate, more information on my github repo below.
https://github.com/z3r0l1nk/StarDate
What do you think @th3jesta ?

@z3r0l1nk the actual link in your description is not the displayed text.
[https://github.com/z3r0l1nk/StarDate](https://github.com/th3jesta/ha-lcars/issues/url)
https://github.com/z3r0l1nk/StarDate is enough. Don't need to do the markdown. ;-)

I have set up the following templates for calculating stardates:
- trigger:
    - platform: time_pattern
      seconds: "/1" # Every 2 seconds
  sensor:
    - name: stardate
      icon: mdi:rocket-launch-outline
      state: >
        {% set uu = as_timestamp(utcnow()) %}
        {% set doty = states('sensor.daysintheyear')|float %}
        {{ (1000 * ((uu/86400/doty) + 25)) + ((uu/86400) % 1) }}
      attributes:
        last_updated: "{{ states('sensor.time') }}"
- sensor:
    - name: DaysInTheYear
      state: "{{strptime('12/31/'+((states('sensor.date')|as_datetime).year|string), '%m/%d/%Y').timetuple().tm_yday|float}}"

Here's how it looks on my dash:

@gridlockjoe, very nice dash...but what did you modify in the code?
the stardate is better, what is the startpoint of the date calculation?


⚡ Speed up __getattr__() by 26% in pydantic/__init__.py

Change Summary
📄 __getattr__() in pydantic/__init__.py
📈 Performance improved by 26% (0.26x faster)
⏱ Runtime went down from 42.8 microseconds to 34.0 microseconds
Explanation and details
Early Importing: Moved the importlib import statement outside of the function. Re-importing this module every time the function is called can be avoided, which slightly reduces overhead.
These changes streamline the __getattr__ method, focusing purely on its dynamic import functionality and avoiding redundant imports. The function now runs with reduced overhead which, in aggregate, can save time and memory when __getattr__ is invoked frequently.
Correctness verification
The new optimized code was tested for correctness. The results are listed below.
🔘 (none found) − ⚙ Existing Unit Tests
✅ 3 Passed − 🌀 Generated Regression Tests

(click to show generated tests)
# imports
from importlib import import_module
from unittest.mock import patch

import pytest  # used for our unit tests
# function to test
from pydantic._migration import getattr_migration
from pydantic.deprecated.tools import *
from pydantic.errors import *
from pydantic.main import *
from pydantic.networks import *
from pydantic.types import *

_getattr_migration = getattr_migration(__name__)
from pydantic.__init__ import __getattr__

# unit tests

# Basic Functionality Tests
def test_valid_attribute_basemodel():
    # Accessing a valid attribute from _dynamic_imports
    assert __getattr__('BaseModel') == BaseModel

def test_valid_attribute_emailstr():
    # Accessing another valid attribute from _dynamic_imports
    assert __getattr__('EmailStr') == EmailStr

def test_attribute_not_in_dynamic_imports():
    # Accessing an attribute not in _dynamic_imports should trigger _getattr_migration
    with patch('pydantic._migration.getattr_migration') as mock_getattr_migration:
        mock_getattr_migration.return_value = 'mocked_result'
        assert __getattr__('non_existent_attribute') == 'mocked_result'
        mock_getattr_migration.assert_called_once_with('non_existent_attribute')

# Edge Case Tests
def test_case_sensitivity():
    # Attribute names are case-sensitive
    with patch('pydantic._migration.getattr_migration') as mock_getattr_migration:
        mock_getattr_migration.return_value = 'mocked_result'
        assert __getattr__('basemodel') == 'mocked_result'
        mock_getattr_migration.assert_called_once_with('basemodel')

def test_empty_attribute_name():
    # Accessing an empty attribute name should be handled
    with patch('pydantic._migration.getattr_migration') as mock_getattr_migration:
        mock_getattr_migration.return_value = 'mocked_result'
        assert __getattr__('') == 'mocked_result'
        mock_getattr_migration.assert_called_once_with('')

def test_special_characters_in_attribute_name():
    # Accessing an attribute name with special characters should be handled
    with patch('pydantic._migration.getattr_migration') as mock_getattr_migration:
        mock_getattr_migration.return_value = 'mocked_result'
        assert __getattr__('Base@Model') == 'mocked_result'
        mock_getattr_migration.assert_called_once_with('Base@Model')

# Error Handling Tests
def test_invalid_module_import():
    # Accessing an attribute that maps to a non-existent module should raise ImportError
    with patch('importlib.import_module', side_effect=ImportError):
        with pytest.raises(ImportError):
            __getattr__('non_existent_module')

def test_attribute_not_found_in_module():
    # Accessing an attribute that does not exist in the module should raise AttributeError
    with patch('importlib.import_module') as mock_import_module:
        mock_module = mock_import_module.return_value
        del mock_module.non_existent_attribute
        with pytest.raises(AttributeError):
            __getattr__('non_existent_attribute')

# Performance and Scalability Tests
def test_large_number_of_attribute_accesses():
    # Repeatedly accessing a large number of different attributes
    for attr in _dynamic_imports.keys():
        assert __getattr__(attr) is not None

# Complex Scenario Tests
def test_nested_imports():
    # Accessing an attribute that involves nested module imports
    assert __getattr__('ValidatorFunctionWrapHandler') is not None

def test_deprecation_and_migration():
    # Accessing deprecated attributes to ensure they are handled correctly
    with patch('pydantic._migration.getattr_migration') as mock_getattr_migration:
        mock_getattr_migration.return_value = 'mocked_result'
        assert __getattr__('root_validator') == 'mocked_result'
        mock_getattr_migration.assert_called_once_with('root_validator')

# Integration with importlib Tests
def test_dynamic_import_with_module():
    # Accessing an attribute that requires dynamic import with module
    with patch('importlib.import_module') as mock_import_module:
        mock_import_module.return_value = 'mocked_module'
        assert __getattr__('dataclasses') == 'mocked_module'
        mock_import_module.assert_called_once_with('.dataclasses', package=__spec__.parent)

def test_dynamic_import_with_specific_module():
    # Accessing an attribute that requires dynamic import with specific module
    with patch('importlib.import_module') as mock_import_module:
        mock_module = mock_import_module.return_value
        mock_module.field_validator = 'mocked_validator'
        assert __getattr__('field_validator') == 'mocked_validator'
        mock_import_module.assert_called_once_with('.functional_validators', package=__spec__.parent)

# Side Effects Tests
def test_logging_or_console_output():
    # Verifying that accessing certain attributes logs specific messages or outputs to the console
    with patch('builtins.print') as mock_print:
        __getattr__('BaseModel')
        mock_print.assert_not_called()

# Large Scale Test Cases
def test_stress_testing_with_high_volume_of_accesses():
    # Simulating a high volume of attribute accesses in a short period
    for _ in range(1000):
        for attr in _dynamic_imports.keys():
            assert __getattr__(attr) is not None

def test_memory_usage_and_resource_management():
    # Monitoring memory usage and resource management
    import tracemalloc
    tracemalloc.start()
    for _ in range(1000):
        for attr in _dynamic_imports.keys():
            __getattr__(attr)
    current, peak = tracemalloc.get_traced_memory()
    tracemalloc.stop()
    assert peak < 10**7  # Ensure peak memory usage is under 10MB

🔘 (none found) − ⏪ Replay Tests
Checklist

[x] The pull request title is a good summary of the changes - it will be used in the changelog
[x] Unit tests for the changes exist
[x] Tests pass on CI
[x] Documentation reflects the changes where applicable
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Would like your feedback here. It seems like the top level init is written in a way to minimize imports and hence pushing this to the function level itself. But if that's not the case then for performance reasons taking the import statement out of the function definition might be a good idea.

Yeah, closing this, the local import is intentional, and I think the impact is quite minimal (we're talking microseconds).


res.say doesn't work for intentRequest

app.intent('tfc', {
  'slots': {
    'phonenumber': 'AMAZON.NUMBER'
  },
  'utterances': ['{|my} {|contact number} {|phone number} {|number} {|is} {-|phonenumber}']
}, (req, res)=>{
  let number - req.slot('phonenumber');
  let login = new TfcLogin();
  login.sendOtp(number).then((data)=>{
    res.say('Enter the otp received on your phone').shouldEndSession(false);
  }).catch((error)=>{}
    res.say(`${error.message}`).prompt('What is your registered contact number').shouldEndSession(false);
  )
})

This is a simple intent request, but it isn't working the way it should. TfcLogin is a class, and whole code is working fine, if there is an error it falls in the catch block, but res.say isn't working as expected. Here's the response that I received
{
  "version": "1.0",
  "response": {
    "directives": [],
    "shouldEndSession": true
  },
  "sessionAttributes": {},
  "dummy": "text"
}

What could be the reason for this?

You need to return a promise from this function, doesn't look like you're?

Are you talking about the login.sendOtp(number) function call? If so, it is working fine, I am receiving response from the server.

No, you must return a Promise from the function. Try return login.sendOtp(number).... to begin with.

I have the same problem maybe:
https://github.com/artifactdev/alexa-fahrplan-dresden/blob/api-workaround/index.js#L92
if (resultObject !== undefined) {                                     console.log(resultObject);                                     response.say(resultObject[0]).send();                                     cardArray.push(JSON.stringify(resultObject[1]));                                     return false;                                 }
The resultObject[0] is a String and console.log() gives me the String but the response is always empty.

send in promise like this return(Promise.then((res)=> response.say(res.data.name).send())


Release workflow

I'd like to generate a package with a stable hash for the next release. See https://github.com/fildesh/fildesh/issues/115 for why. Some projects go a step further and have a workflow that does the whole packaging step upon seeing a new tag. That's worth looking into.

[ ] Playbook for releasing.
[x] GitHub workflow that gives a source package with a stable hash. (More reproducible than developer machine).
[x] GitHub workflow for cutting a release?

https://github.com/ncipollo/release-action seems pretty legit.

Oops, that commit wasn't quite right. Fixed with: https://github.com/fildesh/rules_sxproto/commit/a1bcc25aede57beffad8b498edd5846e048c8a00

The workflow created https://github.com/fildesh/rules_sxproto/releases/tag/v0.0.4 and I filled in the details. Seems good enough.


reproducable numerics for loss, weights and gradients for single node (8 GPUs)

by default, torchtitan use FSDP2 mixed precision (param_dtype=bfloat16, reduce_dtype=float32)
for low-precision dtypes (float8 and int8), it's nature to compare loss curve with bfloat16 and see how well they match. (also a good idea to compare weights norm and gradients norm)
for bfloat16 itself, multiple runs will yield different loss curves and the undeterminism should be understood and documented (say NCCL gradient reduction, attention, seed). Otherwise it's hard to understand if numeric differences are coming from low-precision dtypes
I plotted gradient norms, loss = sum(model.parameters.grad), using llama3-8b with 8 GPUs with deterministic model init and deterministic data loader
for bfloat16, gradients are quite different in repeated runs

turning off gradient norm clipping helps a lot, but could not explain all of the divergence

filing the issue here and hopefully it can be a good candidate for what's next

IIUC, the default SDPA backend for us is flash, and flash backward is non-deterministic?
I think we can try to enable some deterministic SDPA: https://pytorch.org/docs/stable/generated/torch.nn.functional.scaled_dot_product_attention.html

IIUC, the default SDPA backend for us is flash, and flash backward is non-deterministic?
I think we can try to enable some deterministic SDPA: https://pytorch.org/docs/stable/generated/torch.nn.functional.scaled_dot_product_attention.html

good call out!


Warning "You are using an unsupported command-line flag"

Hello,
when launching AutoChrome, the message "You are using an unsupported command-line flag" appears. That can be fixed by adding the following line to the chrome script:
 "--test-type",

Source: https://groups.google.com/a/chromium.org/forum/#!msg/chromium-discuss/O4WpwWvGz4A/jmrypvjNEQAJ
Reference: https://peter.sh/experiments/chromium-command-line-switches/

I cannot replicate this, if it is still a problem please re-open this issue.


[pthreads] Fix crt linkage

Fix pthreads crt linkage according to VCPKG_CRT_LINKAGE.
Related: #17003.

LGTM


Users/lake/previewer

Summary
initial previewer implementation
Screenshot

Checklist

[ ] My code follows ESLint rules and passes all tests.
[ ] I have updated the documentation accordingly.

Seem like the build error ReferenceError: window is not defined is caused by server side rendering.
Fixing it by dynamic importing.


Overhaul package bundle

Is your feature request related to a problem? Please describe.
react-photo-album currently bundles the following assets within its package:

esm bundle (44K)
cjs bundle (16K)
umd bundle (16K)
TS declarations (9K)
source maps (243K)

UMD bundle is not in demand since 100% of current library consumers use bundlers in their respective projects (CRA, Next.js, Gatsby, custom webpack bundle, etc.). Also bundlers do not need the code to be excessively transpiled as it is today, which also presents an opportunity to remove source maps.
We can substantially reduce overall package size by eliminating UMD bundle and source maps.
Describe the solution you'd like

decommission UMD bundle (hopefully for good this time)
remove babel from build pipeline
transpile the code down to ES2018
remove source maps since the code will no longer be "obfuscated" by excessive transpilation
remove comments from esm and cjs bundles
don't uglify cjs bundle

Describe alternatives you've considered
No response
Additional context
No response

Overall npm package size reduced from 347 kB down to 80.5 kB
https://www.npmjs.com/package/react-photo-album/v/1.11.1
https://www.npmjs.com/package/react-photo-album/v/1.12
Minzipped bundle size reduced from 5.1 kB down to 4.5 kB

I am very happy to find Your library!
But now I become aware that version 1.11.1 is the last one for me:
"UMD bundle is not in demand since 100% of current library consumers ..."
So - 100% is not correct - here is at least one consumer of the UMD bundle! 😎😎
Any chance for Updates of the file index.umd.js?

So - 100% is not correct - here is at least one consumer of the UMD bundle! 😎😎

Well, that statement was 100% accurate at that time based on all public GitHub repos using the library 😉
Can you describe you environment that requires UMD bundle?

I don't have a build environment.
Just take your cdn example with the js files, knit some hml, js and php code around it for my own photo gallery.

Ah, I see. Unfortunately, there is no way to turn back time, and UMD is already a matter of the past. Let's move on to ESM bundle!
Here is a working snippet using the ESM bundle:

Please let me know if this works for you.

Thank You very much!
Yes - esm JS fits to my target browsers.
But at the end I want all files on my own server - or running also in offline mode.
So I downloaded the files and changed:
import React from "./js-esm/react.js";
import { createRoot } from "./js-esm/react-dom.js";
import { PhotoAlbum } from "./js-esm/react-photo-album.js";

But in Your file "react-photo-album.js" are two other imports:
/* esm.sh - esbuild<EMAIL_ADDRESS>es2022 production */
import {jsx as y, Fragment as R} from<EMAIL_ADDRESS>import {useLayoutEffect as F, useEffect as H, useRef as M, useMemo as B, useState as z, useCallback as D} from<EMAIL_ADDRESS>
The directories of these files does not fit to my use case.

Can you try downloading<EMAIL_ADDRESS>as "./js-esm/jsx-runtime.js" and changing imports to:
import {jsx as y, Fragment as R} from "./js-esm/jsx-runtime.js";
import {useLayoutEffect as F, useEffect as H, useRef as M, useMemo as B, useState as z, useCallback as D} from "./js-esm/react.js";

Current status:
1.) use case import from "https://esm.sh/...."
Your proposal was running out of the box.
But of course it needs some time until the browser has collected all the files from esm.sh.
Nevertheless worthy to become part of Your examples in Your package.
2.) use case import from own server "./js-esm/..."
To make this work 6 js files have to be downloaded manuallly.
And in all files some directory pathes have to be edited manually.
Nevertheless - at the end the photo album is running smoothly with all files on my own server.
3.) use case offline on local file system:
When opening the photo album from point 2 on my local file system the browser blocked importing module e.g.:
"Access to script at 'file:///C:/photoalbum/js-esm/react.js' from origin 'null' has been blocked by CORS policy"
=> Better to spent my time now on Your last proposal - I will keep You informed 😎

"Access to script at 'file:///C:/photoalbum/js-esm/react.js' from origin 'null' has been blocked by CORS policy"

Can you try adding crossorigin attribute to the script tag?

I succeeded in building the file "react-photo-album-standalone.js"!
=> in both use cases the photo album is now running without any problems:

from my server and
offline on local file

I am impressed:
all Your proposals in Your quick responces were working out of the box.


Traffic mirorring implementation

I'm wrapping up this huge PR, it should be done next week.

LGTM

https://github.com/aeraki-mesh/aeraki/issues/200


seconds_to_time is utility

In gitlab by @simonspa on May 26, 2017, 12:58
https://gitlab.cern.ch/simonspa/allpix-squared/blob/master/src/core/module/ModuleManager.cpp#L529
this should not be here but in the utilities I guess.

In gitlab by @Koensw on May 26, 2017, 17:24
Partly true, but is also just some local output. We can add some time utilities of course. Then https://gitlab.cern.ch/simonspa/allpix-squared/blob/master/src/core/utils/log.cpp#L345 should also move there.

In gitlab by @Koensw on May 26, 2017, 17:23
changed title from seconds_{---}to_time is utility to seconds_to_time is utility