Ubuntu 23.04 Random crashes

Type: Bug

lsb_release  -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 23.04
Release:	23.04
Codename: lunar

Code keeps crashing with a generic crash dialogue.
Captured debug logs of crash attached.
code.debug.log

Error dialogue I get

Oh - BTW:
> code -v
1.85.0
af28b32d7e553898b2a91af498b1fb666fdebe0c
x64

https://github.com/microsoft/vscode/wiki/Native-Crash-Issues

vscode_crash.zip

Crash due to OOM when parsing JSON in the workbench, however the crash reports are from older stable version 1.84. @aaaaaaaalex can you repro the issue in latest stable 1.85 ? If so, can you run Profiles: Create a Temporary Profile and isolate steps to repro the crash.

Ah sorry forgot to mention I rolled back after posting the issue in an attempt to fix, but was getting the same error code and type of behaviour in 1.85. Will upgrade again and send on details, thanks.

1.85 crash attached.
vscode.1.85.0-1701902998.crash.zip
From a temp profile - the steps I can say to repro are: added the repo directories listed above to the workspace, then install Go extension, C/C++ extension, and GitLens. I have a hunch it is the Go extension in particular that may be causing this, but hard to be certain.

Update on this - I created a fresh profile and things were stable before adding extensions.
I added the recommended Go extension (the official google one), the recommended C/C++ extension pack, and GitLens.
This, in a workspace with the repo's I listed above is enough to trigger the crash for me.

versions after 1.81.1 crash for me on ubuntu 16.04.  specifically i know 1.83 and 1.85 don't work for me.  i don't remember how 1.83 crashes, but 1.85 simply ends and disappears with no message when main menu items are selected.   the workaround is install 1.81.1 over the update :)


Resolve bugs inside migrated website

Description
Currently, we are moving the website codebase to Next v14 + Typescript, as per #2636.
We are now open to resolving bugs/errors inside the migrated website. All the community members and contributors are requested to mention the bugs/errors inside this issue and do take the initiative to resolve them. Kindly note that you should adhere to Contributing guidelines and make PRs on the migrate-ts branch only.
Current website - https://www.asyncapi.com/en
Migrated website - https://deploy-preview-2710--asyncapi-website.netlify.app/
PR Link of migrate-ts branch - https://github.com/asyncapi/website/pull/2710
Format of Issue Submission
Don't create a new issue regarding each bug/error. Instead, follow the given template below to report the bugs in the issue comments only and the maintainers (@anshgoyalevil @sambhavgupta0705 @akshatnema) should approve those bugs before start working on it.
Format of issue comment:
#### Name:
#### Description:
#### Page slug or URL where bug is present:
#### Screenshot (of current website):
#### Screenshot (of migrated website):

Name
Not able to render custom JSX components from MD files
Description
Currently, the migrated website is not able to render custom JSX components from MD files like Youtube, CodeBlock, DocCards, etc. It is the issue with @mdx-js/loader that it can't able to render JSX components inside the migrated website from MD files. Instead, it can render the components from MDX files, but we can't simply migrate our Docs and Blogs to MDX as it is not the correct solution to tackle this problem.
URL
https://deploy-preview-2710--asyncapi-website.netlify.app/docs
Current website screenshot

Migrated website screenshot

Name
Size of logo decreases when clicking on the dropdown menu on mobile devices
Description
On mobile devices when clicking on the dropdown menu the size of logo should remain same but it gets smaller
URL
https://deploy-preview-2710--asyncapi-website.netlify.app/
Current Website Screenshot

Migrated Website Screenshot

Name
Size of logo decreases when clicking on the hamburger icon on navbar on mobile devices
Description
On mobile devices when clicking on the hamburger icon on navbar the size of logo should remain same but it gets smaller
URL
https://deploy-preview-2710--asyncapi-website.netlify.app/
Current Website Screenshot

Migrated Website Screenshot

Hiii
I’d like to take a look at this and fix it

Name
Text truncation styling issue with mermaid.js diagrams
Description
When the /docs/concepts/producer route is opened via navigating from other routes, the diagrams render properly. However, when you directly open the route, the text within truncates. This issue persists among most mermai.js diagrams throughout the website both new and old. I've attached a video explaining the same.
https://github.com/asyncapi/website/assets/119070798/d6a25737-8f2f-49a9-a6e1-b08f3f843d65
URL
https://deploy-preview-2710--asyncapi-website.netlify.app/docs/concepts/producer
Current website screenshot

Migrated website screenshot


Update other.md

Fixes #115 to update actor descriptions based on DCC feedback.

Reviewed by committee and accepted.


Task#314 add device building integration

Closes #314
Changed building input field to dropdown, added API call and error message if the call is not completed successfully


Support mixed time values/units in summary

I use time values for a variable in two daily notes, one in the format of 39min and another 00:30:00. For this, I get wrong results, as shown in the figure:

If I use min as the unit in both daily notes, I get the following result:

Further tests show that it seems time value of the format 00:30:00 is not supported, as it does not give correct results even if one use 00:30:00 in both notes.

Hi @wenlzhang,
Thanks for the report.
Will check it.

Is it possible to do some kind of automatic unit conversion for timing info in summary? For instance, values may be created in the format of 00:30:00 or 30min. When summing all the values up, one may want to display the info in the format of hours, days, etc., e.g. 2 hour, 2 day, etc.

You are right, I have checked it.
The summary output does not accept time values as input for now.
Will fix it.
Also, it's hard to make use of 00:30:00  and 30min together.
I suggest you use one format for one specific target.
For the case of '30 min', Tracker will retrieve the the number of 30 only, not knowing what the unit is.
There are too many possibility for units a user can use.
For the case of '00:30:00', Tracker can treat it as a time value, but we cannot mixed the two value types.
For the format of a time value output string , it's doable, will add it.

Also, it's hard to make use of 00:30:00 and 30min together.

I understand that a mixture of them can be difficult to implement.

For the format of a time value output string , it's doable, will add it.

Looking forward to this! 😃

I just realized that it's related to the duration value which we didn't support currently.
Will implement it in the next major release.

Indeed. I also realize that values of the format 00:03:00 are not actually intercepted as durations, but as time values.

I have years of duration data in human-friendly format of, for example, "5h 30m" (for 5 hours and 30 minutes), and “15m” for 15 minutes. Is it possible to implement a duration interpreter that can parse Hours (%H) and Minutes (%M) and Seconds (%S) if desired from arbitrary strings? (use strptime?)  I use "%Hh %Mm” and "%Mm” if < 1 hour. Other people, like above, might use “%M min”.


Unable to import lightning on Google Colab

Bug description
I'm trying to import lightning on Google Colab but it doesn't seem possible at the moment.
How to reproduce the bug
First thing I tried was:
import lightning

Not installed. No problem, let me install it:
%pip install lightning
import lightning

Nope, that fails too. Let's try ipython's reload feature:
%load_ext autoreload
%autoreload 2
%pip install lightning
import lightning

Nope, unable to reload. I've also played around with importlib.reload in a few different possible places but no luck so far.
Note that you have to click "Runtime > Disconnect and delete runtime" and "Reconnect" between each step.
Error messages and logs

Full stacktrace
<ipython-input-1-8f5cbb005247> in <module>
      1 get_ipython().run_line_magic('pip', 'install lightning')
----> 2 import lightning

14 frames
/usr/local/lib/python3.9/dist-packages/lightning/__init__.py in <module>
     25 from lightning.fabric.fabric import Fabric  # noqa: E402
     26 from lightning.fabric.utilities.seed import seed_everything  # noqa: E402
---> 27 from lightning.pytorch.callbacks import Callback  # noqa: E402
     28 from lightning.pytorch.core import LightningDataModule, LightningModule  # noqa: E402
     29 from lightning.pytorch.trainer import Trainer  # noqa: E402

/usr/local/lib/python3.9/dist-packages/lightning/pytorch/__init__.py in <module>
     24
     25 from lightning.fabric.utilities.seed import seed_everything  # noqa: E402
---> 26 from lightning.pytorch.callbacks import Callback  # noqa: E402
     27 from lightning.pytorch.core import LightningDataModule, LightningModule  # noqa: E402
     28 from lightning.pytorch.trainer import Trainer  # noqa: E402

/usr/local/lib/python3.9/dist-packages/lightning/pytorch/callbacks/__init__.py in <module>
     12 # See the License for the specific language governing permissions and
     13 # limitations under the License.
---> 14 from lightning.pytorch.callbacks.batch_size_finder import BatchSizeFinder
     15 from lightning.pytorch.callbacks.callback import Callback
     16 from lightning.pytorch.callbacks.checkpoint import Checkpoint

/usr/local/lib/python3.9/dist-packages/lightning/pytorch/callbacks/batch_size_finder.py in <module>
     22
     23 import lightning.pytorch as pl
---> 24 from lightning.pytorch.callbacks.callback import Callback
     25 from lightning.pytorch.tuner.batch_size_scaling import _scale_batch_size
     26 from lightning.pytorch.utilities.exceptions import _TunerExitException, MisconfigurationException

/usr/local/lib/python3.9/dist-packages/lightning/pytorch/callbacks/callback.py in <module>
     23
     24 import lightning.pytorch as pl
---> 25 from lightning.pytorch.utilities.types import STEP_OUTPUT
     26
     27

/usr/local/lib/python3.9/dist-packages/lightning/pytorch/utilities/__init__.py in <module>
     18 from lightning.fabric.utilities import LightningEnum  # noqa: F401
     19 from lightning.fabric.utilities import move_data_to_device  # noqa: F401
---> 20 from lightning.pytorch.accelerators.hpu import _HPU_AVAILABLE  # noqa: F401
     21 from lightning.pytorch.utilities.combined_loader import CombinedLoader  # noqa: F401
     22 from lightning.pytorch.utilities.enums import GradClipAlgorithmType  # noqa: F401

/usr/local/lib/python3.9/dist-packages/lightning/pytorch/accelerators/__init__.py in <module>
     14 from lightning.fabric.accelerators.registry import _AcceleratorRegistry, call_register_accelerators
     15 from lightning.pytorch.accelerators.accelerator import Accelerator  # noqa: F401
---> 16 from lightning.pytorch.accelerators.cpu import CPUAccelerator  # noqa: F401
     17 from lightning.pytorch.accelerators.cuda import CUDAAccelerator  # noqa: F401
     18 from lightning.pytorch.accelerators.hpu import HPUAccelerator  # noqa: F401

/usr/local/lib/python3.9/dist-packages/lightning/pytorch/accelerators/cpu.py in <module>
     20 from lightning.fabric.utilities.types import _DEVICE
     21 from lightning.pytorch.accelerators.accelerator import Accelerator
---> 22 from lightning.pytorch.utilities.exceptions import MisconfigurationException
     23
     24

/usr/local/lib/python3.9/dist-packages/lightning/pytorch/utilities/exceptions.py in <module>
     15
     16 from lightning.fabric.utilities.exceptions import MisconfigurationException  # noqa: F401
---> 17 from lightning.pytorch.utilities.imports import _PYTHON_GREATER_EQUAL_3_11_0
     18
     19

/usr/local/lib/python3.9/dist-packages/lightning/pytorch/utilities/imports.py in <module>
     28 _OMEGACONF_AVAILABLE = package_available("omegaconf")
     29 _POPTORCH_AVAILABLE = package_available("poptorch")
---> 30 _RICH_AVAILABLE = package_available("rich") and compare_version("rich", operator.ge, "10.2.2")
     31 _TORCHVISION_AVAILABLE = RequirementCache("torchvision")
     32 _LIGHTNING_COLOSSALAI_AVAILABLE = RequirementCache("lightning-colossalai")

/usr/local/lib/python3.9/dist-packages/lightning_utilities/core/imports.py in compare_version(package, op, version, use_base_version)
     75         else:
     76             # try pkg_resources to infer version
---> 77             pkg_version = Version(pkg_resources.get_distribution(package).version)
     78     except TypeError:
     79         # this is mocked by Sphinx, so it should return True to generate all summaries

/usr/local/lib/python3.9/dist-packages/pkg_resources/__init__.py in get_distribution(dist)
    476         dist = Requirement.parse(dist)
    477     if isinstance(dist, Requirement):
--> 478         dist = get_provider(dist)
    479     if not isinstance(dist, Distribution):
    480         raise TypeError("Expected string, Requirement, or Distribution", dist)

/usr/local/lib/python3.9/dist-packages/pkg_resources/__init__.py in get_provider(moduleOrReq)
    352     """Return an IResourceProvider for the named module or requirement"""
    353     if isinstance(moduleOrReq, Requirement):
--> 354         return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
    355     try:
    356         module = sys.modules[moduleOrReq]

/usr/local/lib/python3.9/dist-packages/pkg_resources/__init__.py in require(self, *requirements)
    907         included, even if they were already activated in this working set.
    908         """
--> 909         needed = self.resolve(parse_requirements(requirements))
    910
    911         for dist in needed:

/usr/local/lib/python3.9/dist-packages/pkg_resources/__init__.py in resolve(self, requirements, env, installer, replace_conflicting, extras)
    798                 # Oops, the "best" so far conflicts with a dependency
    799                 dependent_req = required_by[req]
--> 800                 raise VersionConflict(dist, req).with_context(dependent_req)
    801
    802             # push the new requirements onto the stack

ContextualVersionConflict: (Pygments 2.6.1 (/usr/local/lib/python3.9/dist-packages), Requirement.parse('pygments<3.0.0,>=2.13.0'), {'rich'})

Environment

Current environment
#- Lightning Component: all imports
#- PyTorch Lightning Version: 2.0.0
#- Lightning App Version: N/A
#- PyTorch Version: 1.13.1
#- Python version: 3.9.16
#- OS: Linux
#- CUDA/cuDNN version: 11.6
#- GPU models and configuration: Default Google Compute Engine backend
#- How you installed Lightning: pip
#- Running environment of LightningApp: cloud

More info
Here is what I believe to be the source of the issue.
lightning depends on rich, which depends on pygments<3.0.0,>=2.13.0. So %pip install lightning installs a newer version of pygments and uninstalls the pygments==2.6.1 that comes with the environment by default. However, Jupyter relies on pygments to render the notebook, so it has already been imported. For some reason, reload doesn't seem to work (possibly related to https://github.com/ipython/ipython/issues/13347).
So far, I've found two possible workarounds, but no fixes. One is to run the notebook, let it crash, then "Restart runtime" so that pygments has already been upgraded and the notebook imports that instead. The other is to change the install to:
%pip install lightning pygments==2.6.1

This forces pip to use an older version of rich that still supports older pygments. The former workaround is unideal because unfamiliar users won't understand the error message, while the latter workaround is unideal because it only works on Google Colab and only until pygments gets updated in the future. I'm trying to write a tutorial that works anywhere without either of these constraints.
I'm honestly not sure what if anything Lightning can do to solve this issue. One possibility would be to not check the version of rich available and instead rely on pip to do the right thing. Another possibility would be to request that Google update the default version of pygments available in Colab, but that's out of your control and may take a while. Of course, if anyone can figure out why reload isn't working, that would be the most ideal solution.

Reported to Google Colab too: https://github.com/googlecolab/colabtools/issues/3514

Been struggling with this too, thanks for opening the issue @adamjstewart! Maybe we can temporarily require pygments<=2.6.1 in Lightning until this is updated in Colab. What do you think @Borda @carmocca ?

Another workaround is to only try to import rich when it's requested to use the rich progress bar.
Using the RequirementCache and evaluating it lazily

I linked a pull request that fixes this issue temporarily.

This was also fixed on the Google side: https://github.com/googlecolab/colabtools/issues/3514
Your fix is probably more reliable though since the Google fix will be needed again the next time a newer version is required.

Thanks for confirming it!

yet another sin of rich, and respositories which require it and keep a shitty module alive


gadgets: Uniform common info they provide

This commit updates image-based gadgets to provide the same common information:

comm: Process Name
pid: Process ID
tid: Thread ID
uid: User ID
gid: Group ID

This commit specifically:

Adds the Tid field missing on some gadgets
Renames task to comm on others
Reorders the event struct to follow the same pattern on all gadgets
Adds missing description to metadata files

Ref #1567
(I'm not marking #1567 as fixed by this PR, as I still want to investigate if we can provide  a structure with this common info and some helpers to fill it).

CI is failing but it's related to #3185.


Why my commits are failing build ?

Don’t worry about it, it’s the quiz app refusing to build external PRs

hi @San1ay - thank you so much for these translations. Will you also translate the lessons themselves to Hindi (they are the README files in the translations folders)

Yup,Sure but currently I've to prepare for my upcoming exam. I'll do it soon as i get time🙂.

hi @San1ay - thank you so much for these translations. Will you also translate the lessons themselves to Hindi (they are the README files in the translations folders)

Yup,Sure but currently I've to prepare for my upcoming exam. I'll do it soon as i get time🙂.

hi @San1ay - thank you so much for these translations. Will you also translate the lessons themselves to Hindi (they are the README files in the translations folders)

Yup,Sure but currently I've to prepare for my upcoming exam. I'll do it soon as i get time🙂.

Thank you again and best of luck with your exams!

hi @San1ay - thank you so much for these translations. Will you also translate the lessons themselves to Hindi (they are the README files in the translations folders)

Yup,Sure but currently I've to prepare for my upcoming exam. I'll do it soon as i get time🙂.

Thank you again and best of luck with your exams!


Missing files in lib directory / build issues

It seems some files are missing in lib directory. index.js requires ./Multiselect, but no such file is generated by the bundle:lib npm task.
Also, dist directory seems to contain the distribution files, but those files are ignored from git, so it's not possible to update those files.
main entry point in package.json should not be minified (it's up to the final application author to minify all dependencies)

These commits may help :
https://github.com/Toilal/vue-multiselect/commit/91bedcea80df2bf9f12a336d023f8c8d7bbca551 => Removes dist from gitignore and use unminified file as entry point
https://github.com/Toilal/vue-multiselect/commit/2cebcc119d9a9b9b281091a9de2b9698291d742e => Fix CSS files generation in bundle:dist (NODE_ENV=production)

Should be fixed in a new release. The webpack config must be wrong.


Hypersonic

Extension – Hypersonic
Author:

Description
Hypersonic is not working anymore.

I cannot retrieve tasks from Hypersonic (while there are on Notion)
I can create tasks from Hypersonic and it adss it on Notion but I cannot retrieve them on hypersonic then.

There is an error message "Failed to fetch latest data"
I already disconnect the Notion and also uninstalled and re install Hypersonic on Raycast but is does not change anything
See my loom
Steps To Reproduce

The current behavior
Tasks not loading anymore
The expected behavior
Tasks loading normally and control the to do from Raycast
Raycast version

Version 1.40.3

Here are the logs, if it can help
[{"raw":"","file":"/Users/benoiteveillard/.config/raycast/extensions/baa4a90b-4452-4213-b1c0-315edd746652/index.js","line":84,"column":7292,"function":"SE"},{"raw":"","file":"/Users/benoiteveillard/.config/raycast/extensions/baa4a90b-4452-4213-b1c0-315edd746652/index.js","line":84,"column":8072,"function":"Zc.initialData"}]


Update Unit Tests in data-plane libraries for .net461

Unit tests in the data-plane libraries neet to be updated so they can run on .Net framework 4.61

@AlexGhiondea - Can you please have a look? Close this?


Add support for links with a different language

Currently, the extension is only working on https://www.crunchyroll.com/simulcastcalendar.
When I use Crunchyroll in a language other than English, the extension doesn't work because of the URL change.
Examples:
https://www.crunchyroll.com/es/simulcastcalendar
https://www.crunchyroll.com/pt-br/simulcastcalendar

Another suggestion would be to include a filter to remove a specific language like English or German.

Thanks for the issue,
To get the current filter on the language specific simulcast calendar page, I can probably modify the manifest file. Perhaps maybe I will externalize the strings so I can prep it for multiple languages. I'll work on this hopefully this week.
The second point that you raised, I'm not sure what you mean. If you go the options page you can add more languages to the bar and you show or hide the dubs. Let me know if something is not clear or if I am missing what you are looking for.

What I meant in the second point is the creation of a filter for excluding a specific language. For example, removing only the English language and keeping the rest.

Sorry for the delay, but version 1.1.4 is out now for both chrome and firefox. This does not have the externalized string but at least it should be functional.
For you second point, you can do that already:

This configuration will show only dubs that are not English, if that's what you meant

Close this as resolved, feel free to open if issue is present


xc7frames2bit: No such file or directory

I have followed the instructions and can successfully use other parts of the tools but not xc7frames2bit. How do I fix this?

Had to run sudo make install to fix this after deleting the part of the makefile that stopped me running sudo make install. Why do the instructions not tell me to run make install?


HVertHigh and HVertLow classes

Consider introducing 2 classes descended from HVert: HVertHigh and HVertLow.

I think this has been implemented for the time being."


Set logrus Formatter as early as possible

In v2.1.2-rc2, the log lines are:
$ kubectl  -n cattle-resources-system logs -l  app.kubernetes.io/name=rancher-backup   -f
time="2022-04-25T14:11:28Z" level=debug msg="Loglevel set to [debug]"
time="2022-04-25T14:11:28Z" level=info msg="Starting backup-restore controller version v0.0.0-dev (HEAD)"
INFO[2022/04/25 14:11:28] No PVC or S3 details provided for storing backups by default. User must specify storageLocation on each Backup CR
INFO[2022/04/25 14:11:28] Secrets containing encryption config files must be stored in the namespace cattle-resources-system
INFO[2022/04/25 14:11:28] Starting resources.cattle.io/v1, Kind=Backup controller
INFO[2022/04/25 14:11:28] Starting resources.cattle.io/v1, Kind=Restore controller

This shows different formatting and the reason is because formatting only happens after the first two lines.

Rancher version: v2.6.5-rc8
Rancher backups chart version: v2.1.2-rc3
I've checked the INFO, DEBUG, TRACE log levels and the logs have only one formatting now
 image: rancher/backup-restore-operator:v2.1.2-rc3
 args: ["-debug"]

Sample log with TRACE:
kubectl  -n cattle-resources-system logs -l  app.kubernetes.io/name=rancher-backup   -f
TRAC[2022/05/09 16:54:17] Loglevel set to [trace]
INFO[2022/05/09 16:54:17] Starting backup-restore controller version v0.0.0-dev (HEAD)
INFO[2022/05/09 16:54:17] No PVC or S3 details provided for storing backups by default. User must specify storageLocation on each Backup CR
INFO[2022/05/09 16:54:17] Secrets containing encryption config files must be stored in the namespace cattle-resources-system
INFO[2022/05/09 16:54:17] Starting resources.cattle.io/v1, Kind=Restore controller
INFO[2022/05/09 16:54:17] Starting resources.cattle.io/v1, Kind=Backup controller


Relax assumption that gradient is in-place

In some cases, the gradient is computed out-of-place for some reason (some AD systems don't support in-place, gradient computations done by external programs, etc).
function grad!(storage, x)
    g = grad_func(x)
    # unnecessary copy
    @. storage = g
end

Because the gradient interface currently assumes in-place modification, a copy to the storage argument is always necessary.
We should assume the gradient is returned from the grad! function. That way, the example above could just ignore the storage argument

Hi @matbesancon! So, change each definition of grad! removing storage as an argument and return the value that would have been assigned to storage?

hi, no in fact we would keep a storage I believe, but not assume the grad! function returns it, so you would have something like
# out of place
function g_out(storage, x)
    return 3x
end

# inplace
function g_in(storage, x)
    @. storage = 3x
    return storage
end

the second already works but the first wouldn't

the second version would be to have everything out of place, but then users would need to set up a closure and workspace to make it efficient and that's too much of a hassle

So, for example, instead of:
function grad!(storage, x)
    @. storage = 2 * (x - xp)
end

Something along the lines of:
function grad_iip!(storage, x)
    @. storage = 2 * (x - xp)
    return storage
end

function grad_oop(storage, x)
    return 2 * (x - xp)
end

Just making sure I understand what this is about

yes exactly. The point is that some procedures will perform an out of place anyway so forcing the API to be in-place only doesn't make sense

I have a lot of questions. I've opened #373 to facilitate communication and will drop some comments there


Backend Integration

Change Sync to Async

https://github.com/Tanger71/grocery-spending-tracker-backend/pull/16

@jason-nam can we close this?


Properly handle CSGShape parent and visibility updates, plus some refactoring

CSGShapes no longer lose collision when the root shape is made invisible. Fixes #43251.
Prevents unnecessary CSGShape updates when changing the parent's visibility or hierarchy. Fixes godotengine#40931.
Allows _update_shape to be used on invisible shapes. Fixes godotengine#41093.
Closes #43381.
Refactor: Renames parent to parent_shape.
Refactor: Cleaned up CSGShape3D::_notification.

Test projects:
40814 Test Suite - Visibility.zip
40814 Test Suite - Scene Tree.zip
40814 Test Suite - Collision.zip

Could you name a case where changing the root CSGShape's parent or visibility would require an update? I had done some testing with these changes and found no ill effects.
I do agree that it isn't a proper fix for the linked issue, however this does fix another issue I was personally experiencing where the game would stutter after toggling visibility on a large amount of CSGShapes (for culling reasons.)

As an example, take the minimal reproduction project provided in #40782 and make the CSGContainer node start invisible, with this PR the CSGBox is never displayed.

You're totally right. I had encountered that during testing and thought I fixed it for some reason.
I'll go ahead and do more testing at runtime just to confirm that there aren't any other bugs I'm missing.

Can confirm that baked lighting still breaks / un-breaks when toggling visibility of child shapes.

Including my changes, godotengine#40782 now only seems to occur when toggling visibility of a single child shape inside a CSGCombiner.
Previously it would occur when doing that and when toggling visibility of the CSGCombiner.
I'll continue attempting fixes before marking the PR as ready for review again.

Also, it may be important to note that #40880 (9be7b30f3536057b22fd70d5367268749c1a7ea9) mentions CSGShapes becoming dirty after exiting the scene tree, which was intentionally removed in this PR as part of its goal.
However, having done further testing with both this PR and the commit, they tackle separate issues and thereby don't affect each other.

@madmiraal Found a true fix for #40782 -> #40814 (comment)
I can split #40814 (comment) into its own PR if you'd prefer. Please let me know if you have any further concerns.

Well done! Yes, please split this fix into a separate PR; so it can be merged and cherry-picked for 3.2.

@madmiraal OK, it's been posted! #40919
I hope you may still consider merging this PR in the future as it does still fix issues I was having with stuttering when toggling portions of the level.

Updated to fix an issue with collisions not working.

@hoontee unrelated to this PR, but just for your information, you don't need to close the PR before force pushing. In fact, it's better to just leave the PR open. It will also result in fewer notifications for those of us watching the repo. :)

@clayjohn It keeps doing that automatically due to there being no commits. I'm clearly not using git correctly, haha.
Since it notifies everyone I'll try figuring out how to improve the way I make changes on a separate repo.
git push --force origin 227494b:master
git reset --hard origin/master
git add "modules/csg/csg_shape.cpp"
git add "modules/csg/csg_shape.h"
git commit
git push

Updated to fix an issue with shapes not updating when modified outside the scene tree.
Had to rebase, but I didn't do it properly so sorry for the spam :(

Linking #25783 because related, was long time ago...

This PR probably should have been a draft prior to today, however I feel it's now in a truly conpleted state.
I would appreciate it if someone would test this PR further to see if there are any other bugs left unfound. Here's what I tested:

Toggling visibility / changing parent of / transforming / modifying shapes with children, child shapes, and shapes with no children, both inside and outside the scene tree
Loading scene with invisible shapes with children, child shapes, and shapes with no children and later setting to visible

CSGShape3D::_notification has been refactored for simplicity. (view the change)

Added two test projects:
40814 Test Suite - Visibility.zip
40814 Test Suite - Scene Tree.zip

Updated to explain why _update_shape gets deferred. (view)
This would also explain why it's exposed since call_deferred doesn't work on private methods.

Updated to re-add a small snippet of code and added an explanation for why it's needed. (view)

Ready for review.

Rebased following 920f8c86ec7fe6172365b89a7c290af956e8e8e3 and 3044b8f15af91aac4177c59bb5455dcd33a1a6c3.
Still don't know how to rebase without getting the PR automatically closed. :/

git push --force origin 227494b:master
git reset --hard origin/master
git add "modules/csg/csg_shape.cpp"
git add "modules/csg/csg_shape.h"
git commit
git push

@hoontee The PR will be closed automatically if you force push an empty changeset with regard to the master branch, as there isn't anything to merge. You should only force push once you are done with your local changes, not before.
See https://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html#the-interactive-rebase

As of 3.2.4 beta 1, CSG collision no longer works when the shape is invisible. After some testing I can confirm that this PR fixes that issue as well.

Superseded by #43322.

Reopened as an alternative to both #43322 and #43381.

Rebased following f7209b459b4faaae9d93bfb6ac5346eb41787f92.
I tried to follow the pr workflow but I ended up pushing another empty changeset.

Needs the bug and regression labels.
The needs testing label may also need to be removed - I've also tested this thoroughly but I'm unsure if others need to test it as well.

Rebased following #52647.

Tested the fixes again and they're still working. I just wish someone could review this...

The fix still works. Now that the 4.0 alpha is out, 1.5 years after submitting this PR, perhaps it could be reviewed?

Rebased following 6553f5c242865f9aadbe2fdab6db6876c44ac472.

Thanks!


sha.d: assert msg cannot be scope

blocking https://github.com/dlang/dmd/pull/10947

@WalterBright : I can't merge here, so feel free to self-merge

@thewilsonator add "auto-merge" label for Walter plz.


Add --data-dir arguments to the src/mlmax/**.py files for easy local testing

Should be able to run python files locally with a single one data directory argument. This will make it relatively easy to run these files locally for development and testing. The convention we use in preprocessing.py is --data-dir. We can change it, but we should make all of the files in src/mlmax/**.py consistent with each other.

Closed due to inactivity.


SpringFox Model and model schema configuration is not working

Hi,
I am creating documentation for my web services using swagger. My project is not having any domain class. The architecture directly works on the payload to pull the required values using JsonPath. In this case how will I specify the model and model schema for the payload.
Thanks,
Dinesh

Since your services don't seem to enforce any contract on the json payloads/domain representations coming in, I don't see much value in generating swagger-specifications other than documenting all the endpoints. I would really question the need for using swagger.

I have a predefined perfect payload structure which the client needs to send to call the service. So I need to document the payload structure to let the client know what they need to send. If I have a model schema, I cna specify my Json Schema and in the model I can add Json Payload.

In your case, I would strongly recommend spring-restdocs instead.

Thank you. I will go through the specified documentation


add ethclassicwallet.info

submitted on etherscamdb

https://urlscan.io/result/60ead2e9-7c96-4ddf-a782-21dbe75382fd#summary
[+] Whois email<EMAIL_ADDRESS>| Pwned: Not pwned
[+] Emails<EMAIL_ADDRESS>[+] Resolved 999djce.com to <IP_ADDRESS>
[+] Domain associated with email<EMAIL_ADDRESS>999djce.com | IP: <IP_ADDRESS>
[+] Resolved bitslier.com to <IP_ADDRESS>
[+] Domain associated with email<EMAIL_ADDRESS>bitslier.com | IP: <IP_ADDRESS>
[+] Resolved ethclassicwallet.info to <IP_ADDRESS>
[+] Domain associated with email<EMAIL_ADDRESS>ethclassicwallet.info | IP: <IP_ADDRESS>

using paper wallet to send keys. have you seen this before @409H ?


What function does toggle calls?

Hi
I was wondering what function does the close/toggle of slider calls.
I mean if i press the button that opens the slider and then I press it again to close it.
Thanks in advance

(IBAction)revealToggle:(id)sender;

I mean which function of the front view (like viewdidload, viewdidappear etc)

In viewDidLoad:
class ViewController: UIViewController {

    @IBOutlet weak var revealButton: UIBarButtonItem!

    override func viewDidLoad() {
        super.viewDidLoad()

        revealButton.target = self.revealViewController()
        revealButton.action = #selector(SWRevealViewController.revealToggle(_:))
    }

No you didn't get me, I had setted up and its working fine but I want to know which function is called when I close the slider(like open and close it again)

    //MARK: - SWRevealViewControllerDelegate

    func revealController(_ revealController: SWRevealViewController!, willMoveTo position: FrontViewPosition) {
        if position == .right {
            // Will open
            NSLog("Will open")
        }
        else {
            NSLog("Will close")
        }
    }

    func revealController(_ revealController: SWRevealViewController!, didMoveTo position: FrontViewPosition) {
        if position == .right {
            NSLog("Did open")
        }
        else {
            NSLog("Did close")
        }
    }

Thank you this is what I want but I was wondering can I call these function to my main view instead of the revealviewcontroller?

You don't call these methods. SW call these delegate methods if your class adopt SWRevealViewControllerDelegate protocol and you implement them.


upgrade OT API to 0.33.0

Pull Request Test Coverage Report for Build 81

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.769%

Totals

Change from base Build 79:
0.0%

Covered Lines:
42

Relevant Lines:
52

💛  - Coveralls


FYLE-85zrkx6jk Code coverage: Pending User Service method

@jayfyle @Dimple16, the method names aren't mentioned in the spec file for other methods can I include those names too?
<method name> should do this


[Early Version] Fetch more / Infinite Scroll

Adds a fetchMore method able to fetch new data and concatenate it into the store, performing, that way, an infinite scroll behavior!
TODO:

[x] Update CHANGELOG.md with your change

[x] Make sure all of the significant new logic is covered by tests

[x] Rebase your changes on master so that they can be merged easily

[x] Make sure all tests and linter rules pass

[x] change concatPaths: Array<string> to paginationParameters: Array<string>, that way suppressing for special paths those parameters from the store ids. (ex: instead of ROOT_QUERY.allPosts({cursor: 'x', type: 'y'}), if paginationParameters: {'ROOT_QUERY.allPosts': ['cursor']} is set, it will only be ROOT_QUERY.allPosts({type: 'y'})

[x] Implement correct resolution of paths

[x] Squash!

[x] paginationParameters => paginationArguments

[ ] Global paginationArguments for all queries settable.

[x] Backwards concat possible

[ ] Make sure is correctly wired (fetchMore() to the public API, paginationParameters everytime there is some store access & `fetchMore everytime we're doing a query)

[ ] So do MORE TESTS and/or integrate with existing tests to take paginationParameters in account.

[ ] Add it to the docs!

Usage example:
let latest_name = null;
const subscription = client.watchQuery({
  query: gql`
    all_people(latest_name: $latest_name, type: $type) {
       name
    }
  `,
  paginationParameters: ['latest_name'],
  variables: {
    type: 'Jedi',
    latest_name: null,
  },
}).subscribe({
  next(result) {
    console.log(result);
    // First value => {all_people: [{name: 'Luke SkyWalker'}]}
    // Second value => {all_people: [{name: 'Luke SkyWalker'}, {name: 'Obi-Wan Kenobi'}]}
    const new_latest_name = result.all_people[result.all_people.length -1];
    if(new_latest_name !== latest_name) {
      latest_name = new_latest_name;
      subscription.fetchMore({latest_name});
    }
  }
});

I know that merging that won't be a piece of 🍰 ... I am prepared to work with you to integrate that correctly.

This looks like a really nice approach, and has huge potential! Thank you for giving it so much thought.
I just have a few questions:

How would this look if one were using the Relay connection spec? I imagine a lot of people have servers with that: https://facebook.github.io/relay/graphql/connections.htm
Is it possible to somehow make code more DRY, so that you can define a pagination behavior once, and then reuse it in multiple queries? I think it's fair to say that in a single app there will be a finite number of pagination approaches, so it would be good to make those reusable.
Does latest_name refer to latest_name: (the argument) or $latest_name (the variable)? In the example they are named the same so I can't tell (haven't read the code yet).
We should let people override where the results are added, at least give a prepend/append option. There are definitely cases like chat where you start at the bottom and scroll up.

This is definitely something we want to use in a production app. @timbotnik, can you chime in here, would this work for the Galaxy stuff?

Good point, for relay connections, this is super-straightforward: I would put the following in paginationParameters: ['first', 'last', 'after', 'before']. Those are the mandatory input parameters used by Relay.

I started out by defining a per-query rule but definitely (and especially with relay for instance) a global paginationParameters would be really great, I'll look into that!

@stubailo: I updated my PR TODO accordingly, can you tell me if that's ok for you as a PR roadmap ?

Sounds great to me.
Sounds great to me - I was thinking also filtering by __typename and field would be great. So you could say "for these types, I'm using connections. for these other types, I'm using page numbers".
Sounds great to me.
I think it could be as simple as direction: 'APPEND' or PREPEND. We're using this vocabulary already in the recently merged mutation results feature that I have yet to document.

The TODO looks good! I'll try to take a look at the code soon, haven't done that yet, so I can't confirm if the implementation approach is correct.

@stubailo: about 2., I thought about filtering by __typename , however, in a paginated results, you may want to add other arguments than just the pagination arguments. For instance, I could want to add a filter or orderBy param (this is actually one of my use case!). And by doing that with __typename , you don't take those arguments as non-pagination arguments.

About 4., I'll take the existing vocabulary, that seems great!

This is pretty cool @rricard.  Some thoughts:

I feel like trying to be smarter about global pagination params is not really an issue we should worry about (at least right now).  I feel like a global config might lead to some "magic" that results in confusing behavior, and as well the caller can keep a set of pagination configs around pretty easily and use them where appropriate.  We might also provide a few sample configs, such as a Relay config.

Is even the term pagination somewhat limiting in the effect of what this pattern could ultimately support?  For example, one thing I've been pondering with respect to the idea of "fetchMore" is around the idea of maintaining a sort order in the results, such that you could also support progressive loading of data that might be interleaved, not just appended or prepended.  We have some data sources that work like this, such as ElasticSearch results, but I can imagine many other use-cases.  In Meteor, we got this "for free" (err, at the cost of some performance) with MiniMongo, since we can apply complex queries to our data cache at will.  The current work-around we have to do here is maintain our own duplicate cache in the view layer and sort things ourselves (granted, with something like this PR, the complexity of that cache would be reduced).

So the point of all that rambling was instead of paginationParameters, I could pass something like:
moreOptions: {
  quietFields: ['timestamp'], // same as paginationParameters, name TBD
  sortResultsBy: (d) => d.timestamp, // callback which indicates caller-specified sort order
  ... other things we haven't thought of
}

I'm sure this would be going beyond the scope of this PR, but it might inform something about the API / naming that we choose.

@timbotnik Interesting ... quietFields makes sense. However, I have myself sorting issues to handle:

I don't think that's the role of the store to handle that when concatening but either:

the graphql backend that orders results and us to manage how we concat stuff in the store
the React component (or whatever you're using) to order that before rendering.

Either way, sorting in the store would be an interesting matter to take on but it should be handled independently from the fetchMore system (because we may want to leverage that at any time).

For the global quietFields, I'm not sure either, but I think having it would be good. Especially over relay-compliant backends... They would be strictly identical for each query, I'll let you discuss that with @stubailo !

Good points @rricard - re: sort, wouldn't the same apply to the APPEND vs PREPEND argument?  More concretely, could you have 2 instances of watchQuery with the same signature, one asking for APPEND and the other asking for PREPEND?

I would not associate the APPEND/PREPEND with the query but with the fetchMore. That way you control with your pagination parameters what you want next (exactly like in relay where the store concat will be different if you choose first or last)

But contrarily to what Relay does, Apollo works more in a configuration over convention manner when Relay seems to work more like magic (but enforces a strict schema form when Apollo does not). And for me, that was the point that made us adopt Apollo over relay.

I feel like a global config might lead to some "magic" that results in confusing behavior, and as well the caller can keep a set of pagination configs around pretty easily and use them where appropriate.

I agree, let's start with local configuration, and we can add global pagination config later if it turns out to be helpful.

such that you could also support progressive loading of data that might be interleaved, not just appended or prepended

Perhaps instead of sortResults or similar, we should have addResults? Then you can do:
// Simple append
addResults: (existing, new) => {
  return existing.concat(new);
}

// Append, then sort by timestamp
addResults: (existing, new) => {
  return existing.concat(new).sort((a, b) => { return a.timestamp - b.timestamp });
}

// etc.

I agree with Tim that pagination isn't uniform. If you couldn't do this here, I suppose you could easily do it in your React component:
function MyComponent(props) {
  // Sort props before rendering
  const data = props.data.myArray.sort((a, b) => { return a.timestamp - b.timestamp });
  return

;
}

@timbotnik the above doesn't seem that bad, I wouldn't consider that to be a "duplicate cache".
However, @rricard even if your server is handling the ordering, you still need append vs. prepend, because sometimes one needs to paginate from the bottom of the list up (like in the chat usecase, but I suppose you could send the timestamp anyway).

Store insertion
Another thing that we should think about, which I think isn't too complex, is how the caching should behave in this case. Let's say I do the following:

Load a list of todo items, let's say the first 10; this will update the array in the cache to have 10 items
Use fetchMore to load 10 more items, in the current version this will update the same array in the cache to have 20 items
Leave this page, and go to a different page where I have a query to load the first 10 items, just like I did in step 1

Sounds like in this implementation, (3) will now return me 20 items instead of the 10 I ask for, because the pagination parameters will be ignored when reading from the cache?
This is leading me to think that for Relay, after and before shouldn't be ignored when reading from the cache, but they should be ignored when appending to an existing list.

Oh, another concern I have when looking at the implementation - it looks like when using fetchMore, any arrays found in the result are appended to the store instead of replacing. It should probably be only the paginated array that we are interested in that is appended.

@stubailo need to move now, will respond to your concerns a bit later...

Thanks again for doing this! Really excited about having a pretty simple yet flexible pagination model.

Ok, I have a PR over at React to finish first, then back here!

@stubailo: So, here's what I did today first:

APPEND/PREPEND to control how we concat after a fetch more
while doing that, I changed the implementation to use diffFieldAgainstStore so we won't add the same items multiple times
paginationParameters becomes quietFields, I think it's the best naming so far ...

Ok, now, followup to your comments:

I agree, for now, we shouldn't do the global configuration. That is completely doable in a next PR 😉
I really like the addResults approach. I would even go further. We could provide classic addResults implementations (addByAppending/addByPrepending/addBySorting(sort: Function)/...). From where the PR stands, that shouldn't be too hard to do!
I intended at first to do the sorting at render-level in our app. Finally, having the sort going on before going into the store kinda seems more efficient (especially if I trigger multiple renderings for the same store state...)
About the store insertion, the goal of having detached refetch and fetchMore was made to control that: I was inspired by what you said in an another issue. Because, not that any force refetch or refetch with other variables without specifying it as a fetch more will exactly act as it acted before !
Any array will have results appended: that's a valid concern. However, I think it's not as ba

So my main concern right now art the APIs:

what to put on the fetchMore call ?
what to put on the at the query level ?

I pretty much agree with most of your conclusions. Some comments:

I would even go further. We could provide classic addResults implementations (addByAppending/addByPrepending/addBySorting(sort: Function)/...). From where the PR stands, that shouldn't be too hard to do!

We could provide some basics, but I think if it's only 3 lines of code to implement it would be more confusing than helpful. (like if it's literally return array.concat(otherArray))

Any array will have results appended: that's a valid concern. I think it's not as bad as expected because I'm using diffFieldAgainstStore, so if the cursors don't move, I don't see issues on other arrays that could get appended. However, linking this to the type could be smart still so we would avoid really weird situations.

I'm a bit confused about this. Like imagine this situation:
{
  todoList {
    todos(first: 10) {
      text
      tags # an array of strings
    }
  }
}

If I want to load 10 more todos, how do I make sure that the tags arrays aren't messed up?

Yes, I do agree, let's just keep it linked to the type!

what to put on the fetchMore call

I'd make it a flat object of options:
fetchMore({
  variables: { ... },
  addResults: ...,
});

Perhaps there can be some way of specifying which arrays we are actually interested in appending? Maybe that's the job of addResults somehow?
Like maybe addResults just gets the complete first result, and the complete second result, and then you merge arrays as necessary?

Let's freeze the APIs.
I propose something type-based so we avoid any weird stuff.
query options
So we could add something with this signature into the query's option:
{
  quietArguments: string[],
  mergeResults: {[type: string]: (existing: any[], new: any[]) => any[]},
}

fetchMore call
The fetchMore call will be able to control which types to fetch but not how to merge them nor which arguments will stay quiet.
fetchMore(variables: any, fetchMoreOnTypes: string[])

Yes, flat fetchMore is a good idea:
fetchMore call
The fetchMore call will be able to control which types to fetch but not how to merge them nor which arguments will stay quiet.
fetchMore({
  variables: any,
  onTypes: string[]
})

In fact, we could override the query's opts from the fetchMore

The fetchMore call will be able to control which types to fetch but not how to merge them nor which arguments will stay quiet.

It looks like with the proposed API it will actually be able to do that?
Also, does mergeResults get the arrays in the results that match onTypes?
Wait guys I have an idea - what if we just used a directive in the query to specify which fields we want to paginate on? Like this:
{
  todoList {
    todos(first: 10) @apolloFetchMore(name: "todos") {
      text
      tags # an array of strings
    }
  }
}

That way, it's totally unambiguous which array we are fetching more of.

That is very cool. I'll need some help there still, I know how to access directives in the backend (via the ast) but I'm not sure how to that on the client...
Also why the names argument and not a quietArgs instead?

@rricard Oh, this is just to annotate that part of the query with a name - so when you call fetchMore you can tell it which array to refetch. This is instead of onTypes, which seems really hacky especially since you can't see the types in the query.

Okay, yes that makes more sense. It's doing the same thing that I tried at first by hacking something with store ids (ROOT_QUERY.all_people for instance) but actually done well this time. Cool.

Okay so summing up:
Query opts:
{
  quietArguments: string[],
  mergeResults: {[fetchMoreDirectiveName: string]: (existing: any[], new: any[]) => any[]},
}

Method:
fetchMore(opts: {
  variables: any,
  onFetchMoreDirectives?: string[], // Now optional, update at all directives if not set
  quietArguments?: string[],
  mergeResults?: {[fetchMoreDirectiveName: string]: (existing: any[], new: any[]) => any[]},
})

Well, I went a bit crazy with the directive! I added tests so that will be ok but I really need to refactor the implementation is clearly not cool right now. However, tell me if you like the API!

Okay! Nothing shocks me too much in this new code. The capabilities of the features are way more extensive and the hardest part I think will be to formulate that well into the docs!

Ouh... Seems like I imported too much of GraphQL (see travis): The total gzipped size of index.min.js exceeds 34 kB. Do you guys have any advice on how to limit that ?

Okay, I won't be able to work on that this WE but let me some comments on the, I'll fix that directly on monday!

@rricard This looks really interesting, but it's a bit hard to see the proper usage. Would be great if you could add tests, because those would be the easiest way for people reading the source code to figure out the intended usage.

@helfer: I will continue to add some tests. Maybe especially on the directive system.

@rricard note that importing stuff from graphql package raises the bundle size from 32kb to over 70. Let's try not to use it at all if possible.

Ok, I internalised the types that I needed, I'm still slightly at more than 34kB: 34.6 kB

@rricard if you look in the package.json you should see the size limit, I think we should be good to bump that for this great feature!
Also, when this is merged, I'll add fetchMore to the props in react-apollo 👍
I'm really looking forward / need this! Thanks so much for the great work!

This is looking really good so far! I'm going to take an in-depth look today.
@rricard, I added you as a contributor to this repository. Do you mind re-submitting this as a branch from this repo so that I can also push commits to it? That way I can make small changes directly, instead of having to make another fork/PR.
Just link back to this for the conversation, and maybe copy the PR description into the new one.

@stubailo: yes I can do that, thanks for making me contributor!

Closing for a followup pr in the apollostack repo


[HPRO-1169] Save ID verifications in HealthPro db and add IDV column in todays participant review page

Q
A

Target Release?
Next available

Bug fix?
❌

New feature?
✅

Database migration?
❌

New configuration?
❌

Composer updates?
❌

NPM updates?
❌

Jira Ticket(s)
HPRO-1169

@jt2k I brought his up in our call yesterday with Gwen & Jessica and they are okay with switching everything over.


Stream Picard SortVcf output into gzip

This reduces I/O. I have not found a way to stream the input as well.
Runtime for ConcatVCF went down from 4h 22m to 3h 48m on the data set I tested it (a GRCh38 one).

Are you sure we are not getting an "Argument list too long" eventually?

Yes, quite sure. If we were, then we would also get it for the *vcf in the current version.
The argument list can be quite long anyway. Testing it with one million arguments, I do not get an error message:
( printf "echo "; for((i=1; i <= 1000000; i++)); do printf "1234567890 "; done; printf "\n" ) > script.sh
bash script.sh > /dev/null

yeah!


Camps user roles

Roles table for Camps module should give access to different pages in this module.
For example manage members fr camp manager only

I can do that, could you provide more details?

not sure what is needed here but we have the roles framework, you can see documentation and usage guide here:
https://github.com/Midburn/Spark/blob/master/docs/development/users-roles-and-permissions.md


Query Time Serie WHERE UNDEFINED

Hy there,
Firstful: InfluxDB is awesome.
I've a time series there is always a value product_id and an optional value for bundle_id.
is there a possibility to query something like
SELECT * FROM series WHERE bundle_id = UNDEFINED AND product_id = 'iphone-6'
To get the products without bundles?
Thanks!!

@patricklehmann You should be able to get the number of unique values by using DISTINCT().

@toddboom Hey, i just included the UNDEFINED text for these values now i can look for these. thanks!


Transaction deserialization simplifies outputs to legacy_transaction_output when possible

All the outputs in my transaction had outputs in post_alonzo_transaction_output format but after deserialization, outputs which could be simplified to legacy_transaction_output format, got simplified into it. Is this intentional? I can see it happening at wallet level (when wallet performs deserialization in signTx method) and this changing of transaction cbor is leading to inconsistency with what transaction hash we expect and what actually turns out to be.

@sourabhxyz  I don't think this should happen anymore. There was some hand-coding before that did this. We now respect formats and remember all the fiddly CBOR encoding details (e.g. how many bytes used per int, definite vs indefinite arr/maps, key order, etc) correctly now. I've tested everything on mainnet and preprod (and sancho testnet) and everything seems to roundtrip the CBOR to the original.

@rooooooooob Understood, thank you.


⚠ T:Riza Community Forum has degraded performance

In a9376c4, T:Riza Community Forum (https://community.triza.dev) experienced degraded performance:

HTTP code: 500
Response time: 8865 ms

Resolved: T:Riza Community Forum performance has improved in ce58269.


Abbreviations in the article

You've got a nice article https://github.com/fraunhoferhhi/vvenc/wiki/Encoder-Performance but it has a ton of abbreviations.
Would be great if you explained them in a new separate section of it.
Thank you!

Good point, we'll put some effort to make it more accessible soon.

You've got a nice article https://github.com/fraunhoferhhi/vvenc/wiki/Encoder-Performance but it has a ton of abbreviations.
Would be great if you explained them in a new separate section of it.
Thank you!

Can you specify what abbreviations do you mean in particular?
There are already quite a lot of references on the bottom where the main topics are cross references.


Include React on bank homepage.

Description:
Refactor existing UI elements into reusable React components to enhance modularity, maintainability, and scalability of the application.
Expected Behavior:

Each UI element should be converted into an independent, reusable React component.
Components should follow best practices, including proper state and prop management.
The new components should integrate seamlessly into the existing application without breaking functionality.
Improved code organization and reusability, making future updates and maintenance easier.

pull request #34  fixes this issue


Dependabot: submit PRs for GH action runners

I noticed a number of action runners used are out of date. Most updates are related to the Node version the action runners use under the hood updating to Node 20. Not having those updates will become problematic soonish when GHA drops support for Node 16.
So, instead of manually updating the workflows, I've added the GHA environment to the Dependabot configuration. This should take care of it via Dependabot opening PRs to do the updates.

Note: the test failure is unrelated to this PR.

Thank you for contributing! 🎉


Add lobste.rs homepage extension

Description
Read the latest stories of lobste.rs.
In this version of the app:

fetch posts from Homepage
search by category
open post in default browser
open comments in default browser
copy post link to clipboard

Type of change

New extension

Screencast
https://user-images.githubusercontent.com/6503508/137901936-05224a7f-f783-495b-8a16-55c4ff4bfa0d.mov
Checklist

[x] I read the documentation about publishing

Hey @fe9lix ! Thanks for your time and the review!
I would love to play with logic for colors, already have a few ideas.
About the second one — this is something I didn't even thought about but now I see this is pretty achievable, so I'll definitely give it a try!
Thanks again for the review and sharing ideas how to make this stuff better 👏


pypisearch requirements vs. upgrades of other packages (e.g. requests)?

Hello,
it seems that there are strict versions required for some packages needed by pypisearch:
$ /e/Python/jq-win64.exe '.installed[]|select(.metadata.name=="pypisearch").metadata.requires_dist' inspect.txt
[
  "certifi (==2020.12.5)",
  "chardet (==4.0.0)",
  "idna (==2.10)",
  "requests (==2.25.1)",
  "tabulate (==0.8.9)"
]

... which then seems to be a cause for complaints when trying to upgrade other packages in my virtual environment, e.g. requests from 2.25.1 to 2.28.1:
(miro_du) E:\Python\pokusy\miro_du>pip list --outdated
Package            Version   Latest    Type
------------------ --------- --------- -----
certifi            2020.12.5 2022.9.24 wheel
chardet            4.0.0     5.0.0     wheel
charset-normalizer 2.1.1     3.0.0     wheel
idna               2.10      3.4       wheel
requests           2.25.1    2.28.1    wheel
tabulate           0.8.9     0.9.0     wheel

(miro_du) E:\Python\pokusy\miro_du>python -m pip install --upgrade requests
Requirement already satisfied: requests in e:\python\pokusy\miro_du\lib\site-packages (2.25.1)
Collecting requests
  Using cached requests-2.28.1-py3-none-any.whl (62 kB)
Requirement already satisfied: charset-normalizer<3,>=2 in e:\python\pokusy\miro_du\lib\site-packages (from requests) (2.1.1)
Requirement already satisfied: idna<4,>=2.5 in e:\python\pokusy\miro_du\lib\site-packages (from requests) (2.10)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in e:\python\pokusy\miro_du\lib\site-packages (from requests) (1.26.12)
Requirement already satisfied: certifi>=2017.4.17 in e:\python\pokusy\miro_du\lib\site-packages (from requests) (2020.12.5)
Installing collected packages: requests
  Attempting uninstall: requests
    Found existing installation: requests 2.25.1
    Uninstalling requests-2.25.1:
      Successfully uninstalled requests-2.25.1
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
pypisearch 1.3.5 requires requests==2.25.1, but you have requests 2.28.1 which is incompatible.
Successfully installed requests-2.28.1

(miro_du) E:\Python\pokusy\miro_du>pip list --outdated
Package            Version   Latest    Type
------------------ --------- --------- -----
certifi            2020.12.5 2022.9.24 wheel
chardet            4.0.0     5.0.0     wheel
charset-normalizer 2.1.1     3.0.0     wheel
idna               2.10      3.4       wheel
tabulate           0.8.9     0.9.0     wheel

Why are pypisearch requirements set to be on those exact versions, please?
Thank you,
Martin

@shidenko97 - Serhii, any idea, please?


feat: add contributions API

@Mini256  Could you please take a look?
I wonder if sql is being written too complicated.

/lgtm

/merge


[EDGENT-447][Connectors] contribute a RabbitMQ connector

What is the purpose of the change
This PR contribute a RabbitMQ connector for edgent.
Brief change log

Implement a RabbitmqProducer and RabbitmqConsumer as a source & sink to integrate with edgent
Implement a test case to verify the connector

Verifying this change
This change added tests and can be verified as follows:

install & start RabbitMQ server then run RabbitmqStreamsTestManual.testSimple it will pass throgh

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes)
The public API, i.e., is any changed : (no)
Anything that affects deployment: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (documented with JavaDoc)

Hi @chrisdutz could you please review this PR? Thanks!

Hi, so I just did a quick check of the new dependency. It's tripple licensed and one of the available licenses is Apache 2.0, so we're good on the side I was slightly concerned about. Will check out the changes in a little more detail now.

I know this has already been merged.  Nice Job.  Couple of high level questions:

Why not follow the MQTT connector's MqttStreams API style (have RabbitmqStreams) instead of making the main API be Rabbitmq{Consumer,Producer}?  (note there's been a recent discussion on @dev about how that Kafka connector's Consumer/Producer naming style causes confusion)

Rather than introduce the RabbitmqConfigKeyConstants I wonder if it would be better to require the connector user to just construct and pass in a com.rabbitmq.client.ConnectionFactory?  The connector would have a smaller footprint / less "wrapper" to doc and maintain.  I know the MQTT connector defined a MqttConfig class but in retrospect I wonder if that was a mistake. I think the idea at the time was to make the MQTT connector's API independent of using the paho MQTT code under the covers.  That level of isolation seems unnecessary for the RabbitMQ connector.

Does this version of the connector survive transiently broken connections and/or delivery failures, or initial connection failures?

Can creating/starting/stopping a RabbitMQ server instance be embedded in the test code?  Or is there a public RabbitMQ server instance available? That way the tests could be included as part of the automated tests.  If not / until it is, then it seems like DEVELOPMENT.md should be augmented with information for the RabbitMq connector like the Kafka connector.

Your thoughts about adding a RabbitMQ connector sample to the samples https://github.com/apache/incubator-edgent-samples

Hi Dale,
Thanks for your suggestion.  The answers :

Why create two classes (RabbitmqConsumer and RabbitmqProducer), here I
followed Kafka connector and they should not share the same rabbitmq
connection and channel. I also answered in that disscuss mail about naming
style
About the RabbitmqConfigKeyConstants : the reason is the rabbitmq
client need many config arguments, I also followed the Kafka connector used
a Map<String, Object> as the argument box. I think we should not expose the
RabbitMQ client's ConnectionFactory expose to user, it's not safety  and
user will need more knowledge about RabbitMQ's client. For there many
arguments, the builder pattern would be better.
The RabbitMQ client can handle the connection failure and specific
problem with enable recovery and recovery interval setting.
The same as Kafka it do not support automated tests. I have done the
test. If anyone want to run the test case, the rabbitmq server should be
started manually. All the description (about installation and launch steps)
I have written in the test class. And there is no public rabbitmq server
could be used as test server.
Yes,  the usage of this connector should be added to samples
collection, I will do this in the future.

Vino yang
Thanks.
2018-03-23 3:13 GMT+08:00 Dale LaBossiere<EMAIL_ADDRESS>
I know this has already been merged. Nice Job. Couple of high level
questions:

Why not follow the MQTT connector's MqttStreams API style (have
RabbitmqStreams) instead of making the main API be
Rabbitmq{Consumer,Producer}? (note there's been a recent discussion on
@dev https://github.com/dev about how that Kafka connector's
Consumer/Producer naming style causes confusion)
Rather than introduce the RabbitmqConfigKeyConstants I wonder if it
would be better to require the connector user to just construct and pass in
a com.rabbitmq.client.ConnectionFactory? The connector would have a
smaller footprint / less "wrapper" to doc and maintain. I know the MQTT
connector defined a MqttConfig class but in retrospect I wonder if that was
a mistake. I think the idea at the time was to make the MQTT connector's
API independent of using the paho MQTT code under the covers. That level of
isolation seems unnecessary for the RabbitMQ connector.
Does this version of the connector survive transiently broken
connections and/or delivery failures, or initial connection failures?
Can creating/starting/stopping a RabbitMQ server instance be embedded
in the test code? Or is there a public RabbitMQ server instance available?
That way the tests could be included as part of the automated tests. If not
/ until it is, then it seems like DEVELOPMENT.md should be augmented with
information for the RabbitMq connector like the Kafka connector.
Your thoughts about adding a RabbitMQ connector sample to the samples
https://github.com/apache/incubator-edgent-samples
https://github.com/apache/incubator-edgent-samples
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-edgent/pull/348#issuecomment-375425346,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLZAmZXBbqIU8THX5SGfVj73TRpXNGTks5tg_fsgaJpZM4SbNe_
.


USR-102 fix(clerk-react): Add authStateKey field to useAuth

fix(clerk-react): Add changeset
Type of change

[ ] 🐛 Bug fix
[x] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[x] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[x] npm test runs as expected.
[x] npm run build runs as expected.

Add authStateKey field to useAuth in order to have the auth state in a hashed format.
https://github.com/clerkinc/javascript/assets/23478420/7b24e49e-7d8a-40cb-bbe6-98b358bfbb84

@nikosdouvlis all comments were addressed

!snapshot

Hey @raptisj - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
0.26.1-snapshot.e77e2ff

@clerk/chrome-extension
0.3.26-snapshot.e77e2ff

@clerk/clerk-js
4.54.3-snapshot.e77e2ff

eslint-config-custom
0.3.0

@clerk/clerk-expo
0.18.17-snapshot.e77e2ff

@clerk/fastify
0.6.3-snapshot.e77e2ff

gatsby-plugin-clerk
4.4.4-snapshot.e77e2ff

@clerk/localizations
1.24.1-snapshot.e77e2ff

@clerk/nextjs
4.23.2-snapshot.e77e2ff

@clerk/clerk-react
4.24.0-snapshot.e77e2ff

@clerk/remix
2.9.1-snapshot.e77e2ff

@clerk/clerk-sdk-node
4.12.2-snapshot.e77e2ff

@clerk/shared
0.20.0

@clerk/themes
1.7.5

@clerk/types
3.48.2-snapshot.e77e2ff

Tip: use the snippet copy button below to quickly install the required packages.
# @clerk/backend
npm i<EMAIL_ADDRESS>
# @clerk/chrome-extension
npm i<EMAIL_ADDRESS>
# @clerk/clerk-js
npm i<EMAIL_ADDRESS>
# eslint-config-custom
npm i<EMAIL_ADDRESS>
# @clerk/clerk-expo
npm i<EMAIL_ADDRESS>
# @clerk/fastify
npm i<EMAIL_ADDRESS>
# gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>
# @clerk/localizations
npm i<EMAIL_ADDRESS>
# @clerk/nextjs
npm i<EMAIL_ADDRESS>
# @clerk/clerk-react
npm i<EMAIL_ADDRESS>
# @clerk/remix
npm i<EMAIL_ADDRESS>
# @clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>
# @clerk/shared
npm i<EMAIL_ADDRESS>
# @clerk/themes
npm i<EMAIL_ADDRESS>
# @clerk/types
npm i<EMAIL_ADDRESS>

Folks I'm going to close this one for now :(
There are multiple projects running at the same time so I don't think we have enough capacity for this one right now, so let's please re-open if/when we revisit this one

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


source $ENRICO_DIR/enrico-init.sh

Stevens-MacBook-Pro:enrico StevenZakirov$ source $ENRICO_DIR/enrico-init.sh
Adding Enrico to PATH and PYTHONPATH
Setting environment variables for data file locations
mkdir: /Users/davidsanchez/Soft/enrico/Data: Permission denied
mkdir: /Users/davidsanchez/Soft/enrico/Data/diffuse: Permission denied
mkdir: /Users/davidsanchez/Soft/enrico/Data/download: Permission denied
mkdir: /Users/davidsanchez/Soft/enrico/Data/preprocessed: Permission denied
mkdir: /Users/davidsanchez/Soft/enrico/Data/catalog: Permission denied
Run enrico_setupcheck to check if you are set up correctly.
Check your PATH and PYTHONPATH if enrico_setup is not found or gives an error.

Im not sure what happened but i cant get past this step

Hi,
You have to change the scripts for your own installation . This should be in the documentation.
Cheers


folders don´t retain tags

Description
After setting a tag on a folder, the tag is removed from the folder, moments later.
Steps To Reproduce

right click on a folder to set a tag
select the tag filter
reselect the folder
the tag disappear from the folder and the tag filter is blank

Steps to fix

eg. Fix crash that occurs when...
eg. Correct action happens when clicking...

Files Version
Files (Preview) version <IP_ADDRESS>
Windows Version
Windows 11 Version 22H2 (0S Build 22621.819)
Relevant Assets/Logs
debug.log

OneDrive is not the problem, I use tags without any issues.

Has the issue been identified? Do you need more info on my part?
Thanks

Not right now, a dev may need more info when they try to fix it.

Is this still an issue in the preview version? https://files.community/download/preview

No. It's fixed. Tanks
Os meus cumprimentos,
Pedro Matos

From: Yair @.>
Sent: Wednesday, November 30, 2022 1:02:41 AM
To: files-community/Files @.>
Cc: Newguru-1 @.>; Author @.>
Subject: Re: [files-community/Files] folders don´t retain tags (Issue #10539)
Is this still an issue in the preview version? https://files.community/download/preview
—
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10539#issuecomment-1331511615, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AD7J4WSPTDTVBVYDXSZUFUTWK2RTDANCNFSM6AAAAAASIJGYJQ.
You are receiving this because you authored the thread.Message ID: @.***>


Dataflow SQL

Hello,
We can use the generic operator for templates, but I think it can be helpful to create an SQL operator as well.
Reference:
/google-cloud-sdk/lib/surface/dataflow/sql/query.py
/google-cloud-sdk/lib/googlecloudsdk/command_lib/dataflow
Best regards,
Kamil

How is it in line with guide for GCP operators?

This is in line with the guidelines if we also have operators that support generic operations.  Otherwise, the SQL task creation code will become part of the user's codebasse because it is not easy to send SQL queries.  You have to pass a lot of additional parameters.
https://github.com/PolideaInternal/airflow/issues/789

There is no documentation for Dataflow SQL yet. However, I checked how it is implemented by gcloud.
The following command:
gcloud beta dataflow sql query \
	'SELECT word FROM bigquery.table.`my-project`.input_dataset.input_table where count > @threshold' \
	--parameter=threshold:INT64:5 \
	--job-name=my-job \
	--region=us-west1 \
	--bigquery-dataset=my_output_dataset \
	--bigquery-table=my_output_table

causes the following HTTP request to be sent:
==== request start ====
uri: https://dataflow.googleapis.com/v1b3/projects/polidea-airflow/locations/us-west1/templates:launch?dynamicTemplate.gcsPath=gs%3A%2F%2Fdataflow-sql-templates-us-west1%2Flatest%2Fsql_launcher_template&alt=json&validateOnly=False
method: POST
== headers start ==
Authorization: X
accept: application/json
accept-encoding: gzip, deflate
content-length: 539
content-type: application/json
user-agent: X
== headers end ==
== body start ==
{"environment": {}, "jobName": "my-job", "parameters": {"dryRun": "false", "outputs": "[{\"type\": \"bigquery\", \"table\": {\"projectId\": \"polidea-airflow\", \"datasetId\": \"my_output_dataset\", \"tableId\": \"my_output_table\"}, \"writeDisposition\": \"WRITE_EMPTY\"}]", "queryParameters": "[{\"name\": \"threshold\", \"parameterType\": {\"type\": \"INT64\"}, \"parameterValue\": {\"value\": \"5\"}}]", "queryString": "SELECT word FROM bigquery.table.`my-project`.input_dataset.input_table where count > @threshold"}, "update": false}
== body end ==
==== request end ====

so we have the following parameters.
location
us-west1

dynamicTemplate.gcsPath
gs://dataflow-sql-templates-us-west1/latest/sql_launcher_template

body
{
   "environment":{},
   "jobName":"my-job",
   "parameters":{
      "dryRun":"false",
      "outputs":"[{\"type\": \"bigquery\", \"table\": {\"projectId\": \"polidea-airflow\", \"datasetId\": \"my_output_dataset\", \"tableId\": \"my_output_table\"}, \"writeDisposition\": \"WRITE_EMPTY\"}]",
      "queryParameters":"[{\"name\": \"threshold\", \"parameterType\": {\"type\": \"INT64\"}, \"parameterValue\": {\"value\": \"5\"}}]",
      "queryString":"SELECT word FROM bigquery.table.`my-project`.input_dataset.input_table where count > @threshold"
   },
   "update":false
}

This will correspond to the following task in Airflow:
start_template_job = DataflowTemplatedJobStartOperator(
    task_id="start-template-job",
    template='gs://dataflow-templates/latest/Word_Count',
    parameters={
      "dryRun":"false",
      "outputs": """
		[
		   {
		      "type":"bigquery",
		      "table":{
		         "projectId":"polidea-airflow",
		         "datasetId":"my_output_dataset",
		         "tableId":"my_output_table"
		      },
		      "writeDisposition":"WRITE_EMPTY"
		   }
		]
  		""",
      "queryParameters":"""
		[
		   {
		      "name":"threshold",
		      "parameterType":{
		         "type":"INT64"
		      },
		      "parameterValue":{
		         "value":"5"
		      }
		   }
		]
      """,
      "queryString":"SELECT word FROM bigquery.table.`my-project`.input_dataset.input_table where count > @threshold"
   },
   location='us-west1'
)

It is very problematic and difficult to use. A typical user will have a problem creating the above task. As a user, I'd rather create the following code, which is much easier for me.
start_template_job = DataflowStartSQLJobOperator(
    task_id="start-template-job",
    sql='SELECT word FROM bigquery.table.`my-project`.input_dataset.input_table where count > @threshold',
    parameters=['threshold:INT64:5'],
    location='us-west1',
    job='my-job',
    region='us-west1',
    bigquery_dataset='my_output_dataset',
    bigquery_table='my_output_table'
)

This query is very similar to the first gcloud command.

I hope I have convinced you that sometimes we have to think about users, not just the guide.

@potiuk WDYT?

Datafłow SQL is a new service that is based on Dataflow. Dataflow SQL uses Dataflow as the runtime environment similar to how Spark can use Kubernetes. You can also use Dataflow SQL (Apache Beam SQL) without Dataflow via Beam SQL. So this operator will provide integration with a specific program, which is available at: gs://dataflow-sql-templates-us-west1/latest/sql_launcher_template, but we do not have documentation for it.

I hope I have convinced you that sometimes we have to think about users, not just the guide.

It not about convincing me. Some marketing platform operators do not follow the guide too and that was my deliberate decision because it was similar to what you propose here for Dataflow. Simple interface instead of big objects. (@michalslowikowski00 was asking about that).
However, in general, we should avoid such approach because:

it results in 100000 arguments in operator interface
still, some arguments are missing in the interface so a user has no option to pass them to job
examples: BigQuery and Dataproc.

Definitely I agree that we should reach the POCs but as we know they sometimes are not aware how Airflow ops work and in the result, the design decision is left to us (and we usually have no idea how people really use a service). In such cases imho we should stick to hook / operator as thin layer over the API because that's what users know.


Fix jest tests

https://www.facebook.com/groups/reactnativeoss/permalink/1627334037563224/
CC: @cpojer

Travis is back green, thanks for help. I am going to ninja ship it for the sake for other pull requests awaiting.
@facebook-github-bot shipit-ninja

@grabbou My PR had one more commit that was renaming object to dataBlob - this one should fix it 👍

@mkonicek for some reason the shipit bot no longer auto-closes as the commit already landed. I think worth investigating?

Thanks Mike! This was silly; our internal diff didn't update after I canceled the land and re-shipped it.


400: Bad Request

The problem
I have home assistant running on port 8888 and i have installed the add on and it seems to have loaded just fine.
however when i access it using the url im getting a error 400: Bad Request
What version of Cloudflared has the issue?
4.1.7
What was the last working version of Cloudflared?
No response
What type of installation are you running?
Home Assistant OS
Add-on YAML Configuration
No response
Anything in the logs that might be useful for us?
[13:58:08] INFO: Connecting Cloudflare Tunnel...
2023-06-16T05:58:09Z INF Starting tunnel tunnelID=<>
2023-06-16T05:58:09Z INF Version 2023.5.1
2023-06-16T05:58:09Z INF GOOS: linux, GOVersion: go1.19.6, GoArch: arm64
2023-06-16T05:58:09Z INF Settings: map[config:/tmp/config.json cred-file:/data/tunnel.json credentials-file:/data/tunnel.json loglevel:info metrics:<IP_ADDRESS>:36500 no-autoupdate:true origincert:/data/cert.pem]
2023-06-16T05:58:09Z INF Generated Connector ID: 2e5a0183-7b3f-4be1-b105-e9666f8471d8
2023-06-16T05:58:09Z INF Initial protocol quic
2023-06-16T05:58:09Z INF ICMP proxy will use <IP_ADDRESS> as source for IPv4
2023-06-16T05:58:09Z INF ICMP proxy will use :: as source for IPv6
2023-06-16T05:58:09Z INF Starting metrics server on [::]:36500/metrics
2023-06-16T05:58:09Z WRN Your version 2023.5.1 is outdated. We recommend upgrading it to 2023.6.0
2023-06-16T05:58:10Z INF Registered tunnel connection connIndex=0 connection=<> event=0 ip=198.43 location=SIN protocol=quic
2023-06-16T05:58:11Z INF Registered tunnel connection connIndex=1 connection=<> event=0 ip=198.41 location=HKG protocol=quic
2023-06-16T05:58:12Z INF Registered tunnel connection connIndex=2 connection=<>event=0 ip=198.41. location=SIN protocol=quic
2023-06-16T05:58:13Z INF Registered tunnel connection connIndex=3 connection=<>event=0 ip=198.41 location=HKG protocol=quic

Steps to reproduce the issue

add the repo
install cloudflared
add the tunnel name
home assistant running on port 8888 on http

Additional information
No response

i realised i missed out on modifying the HA configuration.yaml file.


transaction when loop

if i want use transaction in loop
how can i do it ??

Unfortunately your question is quite vague. Can you provide more details on what you're trying to do?

if i want use transaction and run insert into 10 times
if err how can i rollback ??
if i=10 and how can i commit ??

Gotcha. This is an extension to just using callbacks in Node.js in general, but with this module :) Example for using transactions is mainly take from the readme at https://github.com/felixge/node-mysql#transactions
var async = require('async');

connection.beginTransaction(function(err) {
  if (err) throw err;
  async.times(10, function(n, next){
    connection.query('INSERT INTO counter SET n=?', [n], next);
  }, function(err, users) {
    if (err) {
      connection.rollback(function() {
        throw err;
      });
    }
    connection.commit(function(err) {
      if (err) {
        connection.rollback(function() {
          throw err;
        });
      }
    });
  });
});

if "throw err" the system will stop
but i don't want stop it
only want rollback and release() or end() the connection
how can i do it ??

That was just a starting point; I'm not really here to write our your whole app :) I'm sure you can figure it out. You didn't mention any of those requirements in your initial two posts, so I didn't know you wanted to see that in the example as well.

you use async is a good idea
i think i can do it
thank youy help ~~


New 'add' functionality

It might be useful to implement a new 'add' functionality to add specific files into an existing archive.
Syntax would be something like:
zstash add --hpss=<hpssDir> file1 file2 ...

This is basically a targeted zstash update.

It's not obvious to me that this is a feature we really need. Closing.

It's not obvious to me that this is a feature we really need. Closing.


Lumen to Laravel Shift

This pull request includes the changes for converting your Lumen application to a Laravel application. Feel free to commit any additional changes to the shift-29570 branch.
Before merging, you need to:

Checkout the shift-29570 branch
Configure your environment for Laravel 5
Verify your dependencies are compatible with Laravel
Review all pull request comments for additional changes
Run composer update (if the scripts fail, add --no-scripts)
Thoroughly test your application

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

:x: Shift could not convert the following files since they differed from the Lumen defaults. You should copy the Laravel versions and merge in any customizations.

[ ] public/index.php
[ ] tests/ExampleTest.php

:x: Shift was unable to convert some of your files to Laravel. Shift moved these files to .unshifted-lumen-files. You will need to review the files within this folder and convert them manually.

:warning: You should compare your .env file to the Laravel example .env file to ensure yours contains all of the environment variables for a full Laravel application.

:information_source: Once you have verified the conversion of your Lumen application to Laravel, you may use the Laravel Shifts to upgrade to the latest version of Laravel.


Include miq_server when retrieving worker

To try to make the way the OpenStack event catcher creates binding queues work a little better, the appliance's IP address was looked up and used as part of the binding queue's name.
However, there were a couple of things working against this fix.  First, the appliance's IP address was not readily available to the worker process.  Second, ManageIQ has a DB connection pool with only one connection.  And, threads (i.e., where event catcher workers do all their work) that attempt to run queries are opening a new DB connection.
The original fix never actually tried opening the a new connection.  Instead, it was perfectly happy to get back a nil value for the appliance and try to lookup Nil#ipaddress.
This fix gets around this problem by throwing the appliance record (miq_server, actually) into an ivar and making that available to the thread.  This keeps the thread from having to query for the miq_server, while still giving it access to the MiqServer#ipaddress.
Original PR:
https://github.com/ManageIQ/manageiq/pull/3050
Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=1232484
References:
https://bugzilla.redhat.com/show_bug.cgi?id=1224389
https://bugzilla.redhat.com/show_bug.cgi?id=1223976

@Fryguy, @jrafanie: please review

I wish we could write a generic test for worker startup that would have discovered this problem.
Note, a different solution could allow more than 1 connection for the worker to avoid the silent error that MiqServer.my_server exhibited.  I like this PR's change though although I'd like a test for it somehow.

I'm not sure what component label to put here...either we need a generic core label, we can use insight, but I don't really like that (considering whacking insight label anyway), or we create a dedicated workers label, which seems like overkill.  @chessbyte Thoughts?

@Fryguy, could almost be appliance.  But, I think a new core label sounds better.

@gtanzillo Thoughts on labels since this is your area?

@Fryguy I don't see an existing label that fits this. I think something like "workers" or "core/workers" would apply to this. Can we add that?

Yes, @gtanzillo we can make it lower case to match all the others... I can show you tomorrow if you want.

Looks good @blomquisg, let's make the other changes in a different PR.


user namespace with kata-container

Description of problem
I followed the instructions to install kata-container on Ubuntu with docker. I chose the systemd modification.
Eveything worked as expected. However, with security in mind, I tried to setup the docker namespace with the docker instructions : https://docs.docker.com/engine/security/userns-remap/
This does not work.
The runtime is kata-container; maybe this behaviour is normal... ?
Expected result
Being able to launch containers with kata-runtime while launching and running it in a specific user namespace.
Actual result
Not working:
docker: Error response from daemon: OCI runtime create failed: rpc error: code = Unknown desc = User namespaces enabled, but no user mapping found.: unknown.
ERRO[0001] error waiting for container: context canceled

Thanks for the question/report @remyd1 . I don't see it listed as a kata limitation over at https://github.com/kata-containers/documentation/blob/master/Limitations.md - so, I'll pull in some others - and hopefully we can clarify, and update that Limitations document if need be.


@conda-forge-admin, please add user @obendidi

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @obendidi in conda-forge/httpx-cache-feedstock#3.


Custom encoding method

Hi,
I encountered an incompatibility issue in the Twitter gem between http-form_data and simple_oauth. More explanation are given in this issue.
Basically here (http-form_data) and there (simple_oauth) the encoding is not done the same way.
http-form_data uses URI.encode_www_form which uses URI.encode_www_form_component which doesn't convert *, while simple_oauth encodes *. The twitter API requires * to be encoded as explained in this post.
I understand that it's not a bug in http-form_data per se, but would you be OK to merge a PR allowing users of the gem to override the method encoding data in HTTP::FormData::Urlencoded#initialize and provide their own? By default it'd obviously still be ::URI.encode_www_form so it'd be a transparent change.
If it sounds somewhat acceptable to you, I'd be glad to work on something and to submit a PR.
Thanks :slightly_smiling_face:

I'm OK with this. Please open a PR so we can start a discussion on API changes :D

Neat!
Will do :+1:

Hi @ixti, any chance of patching the version with this addition?

@clarkbab Sure. Will do shortly

Released as v2.1.1


Desktop Notification - Click and focus conversation

If a desktop notification appears from a user or event, especially a private conversation, I think when you click said notification it should automatically open the reply window and put focus on it. That way you don't have to manually click to send a reply each time and just let it work automatically, much like a traditional IM window.

Yeah that seems like a pretty reasonable enhancement.

This is a duplicate of #1996, which now has more detail than this version.


Electrum issues

Traceback

Traceback (most recent call last):
  File "site-packages\electrumg-3.2.1-py3.5.egg\electrum_gui\qt\network_dialog.py", line 446, in set_server
  File "site-packages\electrumg-3.2.1-py3.5.egg\electrum\network.py", line 471, in set_parameters
  File "site-packages\electrumg-3.2.1-py3.5.egg\electrum\network.py", line 486, in switch_lagging_interface
  File "site-packages\electrumg-3.2.1-py3.5.egg\electrum\blockchain.py", line 422, in read_header
Exception: Expected to read a full header. This was only 0 bytes

Additional information

ElectrumG version: 3.2.1
Operating system: Windows-10-10.0.10586
Wallet type: standard
Locale: en_US
Testnet: False
Regtest: False

HELLO!
PLEASE PROMPT WHY WOMAN'S WALLET DOESN'T CONNECT?
VERY LONG ON RED ROUND ICON DOWN ....
ElectrumG version: 3.2.1

HELLO!
PLEASE PROMPT WHY WHY DO I have lectrumG WALLETS WITHOUT CONNECTIONS IN ME?
VERY LONG ON RED ROUND ICON DOWN ....

Go to tools network then server then tick select server automatically.
Make sure you have working and stable internet connection.

I use electrum portable you can download it.
Check this also https://bitcoingold.org/electrumg-guide/

https://github.com/BTCGPU/electrum/releases
Download electrum portable.

THANKS FOR THE ANSWER!
I DOWNLOADED ON A NEW AND RE-INSTALLED, BUT EVERYTHING IS EQUALLY .... THE WALLET DOES NOT CONNECT!
CONSTANTLY ON RED BUTTON.
ALTHOUGH THE SERVER IS MARKED!
MAY NEED WAIT WAIT FOR IT TO CONNECT ???

Версия 3.2.1. Не подключается к серверу. Что делать?

"Not connected" v.3.2.1. THE WALLET DOES NOT CONNECT!
CONSTANTLY ON RED BUTTON.
How to be?

Hello
When the wallet starts, the status is no connection and a red button.
Wallet version 3.2.1
Windows 10 Pro
19042.1288


Merge development with master

Added message command

You forgot to update template.env and ecosystem.template.json files.

what happened here lol

Nope.
notworking1
notworking2

Here's my report:
3  admin-to-recipient-working
4  recipient-to-admin-notworking

I can confirm it reads the else part (not admin), but the bot still not able to send a message to the admin.
5  read-but-not-sending-to-admin

let me try to run it once.

Yay! 🎉🎊
messageCommand-working-fine

🤔


Implement global panic handling

Panic handling can be done in the main method, by deferring a recovery function immediately. The panic log can be displayed after a helpful message about bug reporting.

It might be helpful to use the same package that Hashicorp uses for their tools such as Terraform, namely, https://github.com/mitchellh/panicwrap.

Closed by #94


[Feature Request] Integrate Reddit

Required prerequisites

[X] I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
[ ] Consider asking first in a Discussion.

Motivation
support getting data from Reddit
Solution
No response
Alternatives
No response
Additional context
No response

close this issue as PR merged: https://github.com/camel-ai/camel/pull/886


Model is reset with resetFieldOnHide=false - v6

Although FormlyModule.forRoot/extras/resetFieldOnHide=false the model is reset.
https://stackblitz.com/edit/ngx-formly-multiple-form-groups-bug-xjhc6d?file=src%2Fapp%2Fapp.component.ts
Choose secondGroup and set hasActive.
Choose thirdGroup, press submit, hasActive is missing from the model.

v6.0.0-beta-3

The item hasActive is still present in the model object but not in the form instance which is an expected behavior since its a hidden field and not part of the form anymore.
submit() {
+  alert(JSON.stringify(this.model));
-  alert(JSON.stringify(this.form.value));
}


Constrain dev dep: pg to fix ruby 1.9.3 tests

PS: We may want to discuss dropping support for ruby 1.9.3 soon, if other important gems like pg are doing so.

IIRC rubocop has also recently dropped support for ruby 1.9.3


NavBar styles can be improved

Thank you for taking the time to file a Feature Request report.
Describe the solution you'd like

The contents of the navbar can be aligned center.
There is no space between navbar toggle button and screen edge at some screen sizes. Same goes for the logo.

Can I work on this issue?


When add 'pedestrian' and 'cyclist'  metrics are zero

When I add pedestrian and cyclist classes for TED-S metric results are become zero and it gives good result for only car so does TED-S trained with only car class ?
Thank yo so much.

Currently, the released model only trained for car cls, so the metrics are zeros. Please train 3-cls model by yourself using the similar config of CasA-V. Note that, the hyper parameters of 2D backbone, dense head, training epoch and score threshold should be further tuned to attain a good performance. In addition, the 3-cls model is scheduled to be released in my next project，TED project will do not update again.

Currently, the released model only trained for car cls, so the metrics are zeros. Please train 3-cls model by yourself using the similar config of CasA-V. Note that, the hyper parameters of 2D backbone, dense head, training epoch and score threshold should be further tuned to attain a good performance. In addition, the 3-cls model is scheduled to be released in my next project，TED project will do not update again.

Thank you so much


Switch layers to tf.keras spec

Related #416, #388
We'd like to refactor our layers module to match the keras api spec.  I'll work on this once the style guide PR has been submitted (#424)

@jvmancuso I think we can close this issue?

I'm not sure we should close this until the tfe.layers module is gone :)

@jvmancuso could you add any colour relate to switching tfe.layers over to keras.

We remove tfe.layers in TFE based on TF2.


Kana characters are displayed as horizontal characters.

The way the station name is displayed in the following items is strange.

mtr:station_name_tall_wall
mtr:station_name_tall_block

The station names are as follows.

カラフル渓谷|Colorful Valley

screenshot

Note: As a Japanese, this notation feels very strange.

Fixed in 3.1.0-unofficial-3


[RESOLVED] S100-Secundario has been restarted (uptime < 10m)

Problem started at 07:48:30 on 2023.06.20
Problem name: S100-Secundario has been restarted (uptime < 10m)
Host: S100-Secundario
Severity: Warning
Operational data: 00:06:30
Original problem ID: 28952
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23497&eventid=28952

Problem has been resolved in 3m 30s at 07:52:00 on 2023.06.20
Problem name: S100-Secundario has been restarted (uptime < 10m)
Host: S100-Secundario
Severity: Warning
Original problem ID: 28952


add note about adjusting PATH

needed to make Jupyter visible
Thanks for the nice tutorial!

Thanks Dirk!