added border to the page

Added 6 images in pages
edited editor.js
edited editor.html
and sir in editor.html there ware 2 choosePage(6) it should be 7 in the parameter I corrected it

great work @sahebsunny 🙌. It's perfect from my side

Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

great work @sahebsunny 🙌. It's perfect from my side
@anushbhatia
Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

great work @sahebsunny 🙌. It's perfect from my side
@anushbhatia
Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

great work @sahebsunny 🙌. It's perfect from my side
@anushbhatia
Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

Can you please pull the current changes and fix the merge conflict

Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

great work @sahebsunny 🙌. It's perfect from my side
@anushbhatia
Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

Can you please pull the current changes and fix the merge conflict

Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

great work @sahebsunny 🙌. It's perfect from my side
@anushbhatia
Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

Can you please pull the current changes and fix the merge conflict

Ok sir I am making a new Pr for this

Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

great work @sahebsunny 🙌. It's perfect from my side
@anushbhatia
Thank you Sir for your review
it was for DWOC
What I need to do for it to get merge

Can you please pull the current changes and fix the merge conflict

Ok sir I am making a new Pr for this


Fix build by bumping package:file

Bumping package:process was causing conflicts with package:intl, from Travis:
Package "intl" has conflicts:
  20 sources want "/home/travis/.pub-cache/hosted/pub.dartlang.org/intl-0.14.0/lib":
    /home/travis/build/flutter/flutter/packages/flutter_tools/.packages
    /home/travis/build/flutter/flutter/examples/flutter_gallery/.packages
    /home/travis/build/flutter/flutter/examples/platform_view/.packages
    /home/travis/build/flutter/flutter/packages/flutter_test/.packages
    /home/travis/build/flutter/flutter/examples/platform_channel/.packages
    /home/travis/build/flutter/flutter/dev/integration_tests/channels/.packages
    /home/travis/build/flutter/flutter/dev/benchmarks/microbenchmarks/.packages
    /home/travis/build/flutter/flutter/dev/automated_tests/.packages
    /home/travis/build/flutter/flutter/dev/manual_tests/.packages
    /home/travis/build/flutter/flutter/examples/stocks/.packages
    /home/travis/build/flutter/flutter/dev/benchmarks/complex_layout/.packages
    /home/travis/build/flutter/flutter/packages/flutter/.packages
    /home/travis/build/flutter/flutter/dev/tools/.packages
    /home/travis/build/flutter/flutter/dev/integration_tests/ui/.packages
    /home/travis/build/flutter/flutter/examples/flutter_view/.packages
    /home/travis/build/flutter/flutter/packages/flutter_driver/.packages
    /home/travis/build/flutter/flutter/examples/layers/.packages
    /home/travis/build/flutter/flutter/examples/hello_world/.packages
    /home/travis/build/flutter/flutter/examples/platform_channel_swift/.packages
    /home/travis/build/flutter/flutter/examples/catalog/.packages
  1 source wants "/home/travis/.pub-cache/hosted/pub.dartlang.org/intl-0.15.1/lib":
    /home/travis/build/flutter/flutter/dev/devicelab/.packages

Just bumping package:file for now to fix breakage.


Create an instance for uniprot

http://sparql.uniprot.org/
@JervenBolleman ;)

hmm, what would you like us to do specifically?

Nothing! I'll set up a instance of SPARQL router that will enable the creation and sharing of queries that hit Uniprot's endpoint. That can be usesul if you want to share query results.


Osd 8517 part 1 -- shellcheck

Also if you can squash the commits if there is no special meaning for them that would be helpful

/hold
To hold the tests that are failing

/lgtm


Signaling project NTR: tyrosine dephosphorylation of STAT protein

Hi
from JAK/STAT pathway - Signaling Project #1628
Please could the following new term be created:
GO:0035335 peptidyl-tyrosine dephosphorylation

is_a NTR tyrosine dephosphorylation of STAT protein
Suggested definition: The process of removing a phosphate group from a tyrosine residue of a STAT (Signal Transducer and Activator of Transcription) protein.

If created, please add the following DbxRefs to the term:
DbxRef: GOC:ga
DbxRef: GOC:BHF
DbxRef: GOC:rl
PMID:28637459
Thanks,
Giulia
@RLovering

Perhaps better represented as 'STAT protein tyrosine phosphatase activity'?

@gantonazzo @RLovering
Can you use the generic term 'GO:0004725  protein tyrosine phosphatase activity' with the specific protein in the 'has input' field ?

Hi @pgaudet ,
That would be fine for me.


Update anchor tag to underlined by default

Linked to issue #90

@andybrewer Apologies in advance for pinging you. Do you have any comments on this PR?

Great, I like the change


Make readDir/readFile more precise and flexible

See #9599
There are historical reasons to this, I'm sure, but the current behaviour is hard to understand, document and is not as flexible as it easily could be.
So, I suggest adding a filesystem option to both of these functions:

work -- default, will search in the project work dir only
content (composite, project first)
archetypes  (composite, project first)
static  (composite, project first)
layouts  (composite, project first)
data  (composite, project first)
assets  (composite, project first)
i18n  (composite, project first)

The new default (that work is project work dir only) is a slightly breaking change, but I suspect it's going to solve more issues than it creates.

I have marked this as a "GoodFirstIssue" which I think is true, as it's very isolated. Add some failing testcases to tpl/os/integration_test.go would be a good start. I suggest adding a GetFilesystemByName or something to the BaseFS struct and use the constants infiles.


(bug) Conform check operators fail to run

alignment_base_replay(default) and alignment_base_replay fail to run.
I'm not sure that the problem is from my workflow or it's from the operators.
The log is
knime.log
The screenshot is

This is the workflow
alignment_base_replay.zip

Thanks for the report with data, I will have a look at it.

fixed the bugs now.


Fix remaining documentation lint

Believe this is the last of the lint.

Note that GridQid needed to use a raw string due to the \n in the text.

Fixes: #3388

Fixed nits.


Include Grafana Dashboard Json export

Can you also include grafana json export for the dashboard which is shown in screenshot.
It would be helpful to start with

Any news about the Grafana dashboard please 🙏 ?

Hey, sure! :)
I might need to edit the one we currently use, mainly to change the variables (cluster & namespace variables should probably be removed since it's related to our k8s env).
I'll paste it here so you can check if it works for you.

Sure, thank you @MattKetmo would be interested also with k8s version though! thank you for the help!!


Add RM option for enabling for deployment

Since Azure RM supports enabling a keyvault for deployment, it should be mentioned as an option, especially when other operations being done in this context use Azure RM.

#sign-off

Thanks!

#sign-off


Mistakes in Ch6 The Tokenizer Library

Hi, thanks for your excellent course. Recently, I found two  (maybe) mistakes during the learning process.
In Ch 6 -  The 🤗 Tokenizers library,
Specifically,
In Grouping Entities section,
import numpy as np

results = []
inputs_with_offsets = tokenizer(example, return_offsets_mapping=True)
tokens = inputs_with_offsets.tokens()
offsets = inputs_with_offsets["offset_mapping"]

idx = 0
while idx < len(predictions):
    pred = predictions[idx]
    label = model.config.id2label[pred]
    if label != "O":
        # Remove the B- or I-
        label = label[2:]
        start, _ = offsets[idx]

        # Grab all the tokens labeled with I-label
        all_scores = []
        while (
            idx < len(predictions)
            and model.config.id2label[predictions[idx]] == f"I-{label}"
        ):
-           all_scores.append(probabilities[idx][pred])
+           all_scores.append(probs[idx][predictions[idx]])
            _, end = offsets[idx]
            idx += 1

        # The score is the mean of all the scores of the tokens in that grouped entity
        score = np.mean(all_scores).item()
        word = example[start:end]
        results.append(
            {
                "entity_group": label,
                "score": score,
                "word": word,
                "start": start,
                "end": end,
            }
        )
    idx += 1

print(results)

In Handling long contexts,
candidates = []
for start_probs, end_probs in zip(start_probabilities, end_probabilities):
    scores = start_probs[:, None] * end_probs[None, :]
    idx = torch.triu(scores).argmax().item()

-   start_idx = idx // scores.shape[0]
-   end_idx = idx % scores.shape[0]
+   start_idx = idx // scores.shape[1]
+   end_idx = idx % scores.shape[1]
    score = scores[start_idx, end_idx].item()
    candidates.append((start_idx, end_idx, score))

print(candidates)

Thanks for opening this issue @SinclairCoder !
I'm not sure I understand the first problem - it looks like you're suggesting to introduce probs and predictions variables, but these don't seem to be defined anywhere. Can you please clarify?
For the second issue, the scores tensor is actually square, so it doesn't matter which dimension we use in this case. Nevertheless, for consistency, I'll refactor to match the previous logic in the section

ok! I got it.


The 3D camera FOV isn't always set correctly when using camera replication

Godot version: Git https://github.com/godotengine/godot/commit/ebdd2bc474f6bb3ff124755196fa116c4fd91385
OS/device including version: Fedora 31
Issue description:
Depending on when you change the editor camera FOV, it may not always apply to the running project when editor camera replication is enabled.
This is not limited to FOV; the same bug occurs with the camera's near and far plane values.
Steps to reproduce:

Run a project that has a Camera node and enable camera replication at the top of the 3D viewport.
Change the camera FOV using the View > Settings menu at the top of the 3D viewport. Notice how the FOV also changes in the running project.
Disable camera replication and enable it again.
Notice how the default camera FOV was restored (instead of using the current editor camera FOV).

Minimal reproduction project: Any 3D project can do, but you can use this one for testing purposes: test_dithering.zip

Still reproducible in the 3.2.3-stable.


📝 README - fixed broken link

As per my conversation with @tiagov8, one of the link was broken because the brackets in the [name](url were wrongly typed

As per my conversation with Matt W, referencing the Staging Environment URL is bad practice as it could change in the future.
Instead, we should reference a link to the Deployments which shows the latest Staging Environment URL.
Task

[ ] replace the Staging Environment URL with a link to the latest staging workflow

its not that it is bad practice, but we have environments configured in the repo and it would be safer to reference that.... in case the staging url changes again


Nonexistent items in sidebars.json causes docusaurus-start to silently fail

This is the output of docusaurus-start
Checking if port 3000 is free...
Starting Docusaurus server on port 3000...

The command exits afterward.

HI @chenglou -- hopefully #296 fixed this. If not, please feel free to reopen.


Localhost connections from Windows to WSL2 have stopped working (presumed docker desktop related)

Environment
Windows build number: Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Your Distribution version: 18.04
Whether the issue is on WSL 2 and/or WSL 1:  Linux version 4.19.104-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Wed Feb 19 06:37:35 UTC 2020

Steps to reproduce

Since it's the only thing remotely non-trivial that I did related to my WSL2 setup, I assume that the issue came from installing docker desktop, from here. I have then uninstalled docker desktop to try and resolve this issue (uninstalling hasn't fixed the issue).
E.g. running netcat from WSL2 like this:
nc -l 80
I can no longer connect to the socket from windows (e.g. from firefox) as localhost:80.
I can still connect using the IP address for WSL2 found via ifconfig though this is less convenient.

Expected behavior

Previously I could connect to sockets listening (on <IP_ADDRESS>) within WSL2 from Windows using localhost or the IP <IP_ADDRESS>
Actual behavior

I can now only connect to WSL2 from Windows using the IP address for WSL2 (e.g. found with ifconfig)

@rib unfortunately this is the case for WSL2 networking. When using WSL, it was an actual subsystem of Windows sharing all the same networking. For WSL2, it is actually running Linux within a VM and thus that VM has its very own IP address and networking.  If you want to forward ports from your local machine to the container, you can do so like this:
Open an elevated PowerShell or cmd.exe prompt:

Type ipconfig and note the IP address for Ethernet adapter vEthernet (WSL)
To forward port 80 from localhost->WSL type:

netsh interface portproxy add v4tov4 listenport=80 listenaddress=<IP_ADDRESS> connectport=80 connectaddress=<wsl_ip>

Note: it'd probably be wiser to use a different listenport just in case you actually want to run something on 80 within Windows at some point (i.e. 9080 such that you'd connect to http://localhost:9080). You might be scratching your head in the future as to why it doesn't work if you have that portproxy setup, but you had forgotten about it.
To see what portproxies you already have setup:
 netsh interface portproxy show all

Thanks for the comment @ctataryn
Right, I'm familiar with the general architectural differences between WSL1/2 and can see that it's more fiddly to support routing localhost connections from windows to WSL2 running in a VM but I believe it is intended to be a supported feature of WSL2 (for example please see https://www.bleepingcomputer.com/news/security/wsl2-now-supports-localhost-connections-from-windows-10-apps/)
Connecting to localhost has been working fine with WSL2 up until now so it's not a fundamental limitation of WSL2 - I'm saying something has recently regressed on my system.
The use of port 80 was only as a bare minimal example. In practice I've been serving http using unpriviledged ports.
My current guess is that installing docker desktop had a side effect of deleting whatever bridging/routing tricks were in place beforehand to enable connections to localhost route through to WSL2 - I'm hoping there's some way to fix that.

Have you tried restarting LxssManager service to see if it starts working again?

@rib wow, I didn't know that. I always was told WSL2 had completely different networking hence the need to port forward.  If that's not the case, I hope they figure out a way to make it work the way it was. It's a pain to have to port forward, and it really was a pleasure in the way it used to work under WSL1

@denisdifazio I had rebooted so guess the answer was yes. I found it timed out when I tried explicitly restarting the service which also left things in an inconsistent state (couldn't use wsl2).
Since I just rebooted (while I had a pending update) I'm now seeing that WSL2 is working with localhost forwarding working again too - so problem magically solved phew :)
Guess maybe the Windows update fixed something.

Restarting LxssManager solved the issue for me. Thanks @denisdifazio !
How to restart the service:
https://stackoverflow.com/questions/48407070/wsl-ubuntu-hangs-how-to-restart#:~:text=To expand on kev's answer,right-clicking and selecting Restart .&text=and it will start automatically next time you open a shell.

Restarting LxssManager solved the issue for me. Thanks @denisdifazio !
How to restart the service:
https://stackoverflow.com/questions/48407070/wsl-ubuntu-hangs-how-to-restart#:~:text=To expand on kev's answer,right-clicking and selecting Restart .&text=and it will start automatically next time you open a shell.


production build not happening automatically when releasing python packages

When I released the last versions of the packages, I had to do clean out the js builds before starting the python release process, otherwise I was ending up with some builds that were not production builds (i.e., were not minimized, etc.). I thought that I wouldn't have to do a git clean -dfx before doing the python build. This would be good to look into, as right now if you don't clean, it seems you release packages that are about 2x as big because the js is not minified.

Maybe first invoking the clean:all script: https://github.com/jupyterlab/jupyter-renderers/blob/a50d35b4ae73d2a29c36b2229b913869e51affc7/packages/fasta-extension/package.json#L41
Here:
https://github.com/jupyterlab/jupyter-renderers/blob/a50d35b4ae73d2a29c36b2229b913869e51affc7/package.json#L8
Might be enough?


Validate CSR CN against CSR.Spec.Username

Addresses #10

First of all, sorry it took a while for me to get at this. And thanks for opening the PR!
I'll leave some comments as review.


Copy/Paste of Sub-Process looses Z-Order of Boundary Event, Compensation Associations and Event Sub-Process Contents

Describe the Bug
Copy & Paste of a an embedded sub-process results in the following issues:

Z-Order issue: Boundary Events appear bellow the tasks they are attached to
Compensation Associations disappear
Event Sub-Process contents disappear

diagram.bpmn
log.txt
Steps to Reproduce
Steps to reproduce the behavior:

Open the attached BPMN model diagram.bpmn
Copy and paste all elements

Expected Behavior
The copy looks exactly the same.
Environment

OS: Ubuntu 18.04.2 LTS
Camunda Modeler Version: 3.0.1 (nightly build downloaded on 2019-04-03)

The good news is: The boundary event labels stay in position #1325

Thanks for reporting! I was able to reproduce it. Seems like we're having a very specific scenario where multiple bugs occur. When I copy the elements (e.g. the Compensation SubProcess), it works fine.

Using Camunda Modeler v3.4.1 I cannot reproduce any of the issues anymore. Therefore, I will close this issue.


2024.4.4 broken ZHA

2024.4.4 was pushed to latest/stable but it has a major bug:
https://github.com/home-assistant/core/issues/115459
Logger: homeassistant
Source: /snap/home-assistant-snap/600/lib/python3.12/site-packages/homeassistant/runner.py:146
First occurred: May 6, 2024 at 11:18:30 PM (3002 occurrences)
Last logged: 9:14:14 PM

Error doing job: Exception in callback SerialTransport._read_ready()
ValueError: (11, None) is not a valid NcpResetCode

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/snap/home-assistant-snap/600/lib/python3.12/site-packages/serial_asyncio_fast/__init__.py", line 137, in _read_ready
    self._protocol.data_received(data)
  File "/snap/home-assistant-snap/600/lib/python3.12/site-packages/bellows/uart.py", line 84, in data_received
    self.frame_received(frame)
  File "/snap/home-assistant-snap/600/lib/python3.12/site-packages/bellows/uart.py", line 119, in frame_received
    self.rstack_frame_received(data)
  File "/snap/home-assistant-snap/600/lib/python3.12/site-packages/bellows/uart.py", line 160, in rstack_frame_received
    code, version = self._get_error_code(data)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/snap/home-assistant-snap/600/lib/python3.12/site-packages/bellows/uart.py", line 193, in _get_error_code
    return t.NcpResetCode(data[2]), data[1]
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/snap/home-assistant-snap/600/lib/python3.12/site-packages/bellows/types/basic.py", line 216, in __call__
    return super().__call__(value, names, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/enum.py", line 757, in __call__
    return cls.__new__(cls, value)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/enum.py", line 1179, in __new__
    raise exc
  File "/usr/lib/python3.12/enum.py", line 1156, in __new__
    result = cls._missing_(value)
             ^^^^^^^^^^^^^^^^^^^^
  File "/snap/home-assistant-snap/600/lib/python3.12/site-packages/bellows/types/basic.py", line 225, in _missing_
    new = int_type.__new__(cls, value)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: int() argument must be a string, a bytes-like object or a real number, not 'tuple'

We are aware. See https://github.com/giaever-online-iot/home-assistant-snap/issues/31#issuecomment-2101642954

This bug is only about the 'latest/stable' tag not referring to a stable release.

Well, there will be an update when there's a fix.
It's impossible to know every bug in advance. I'm following the HA Core releases. When they consider a minor version stable, we do too. 2024.4 was the final patch release for that minor.
You can roll back to 2024.3 and wait for the final release of 2024.5


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_33b0c8a7-4f69-400d-bce3-92df7dd00bcb/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_33b0c8a7-4f69-400d-bce3-92df7dd00bcb.git

Docs Build status updates of commit 6a3406c:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_main_2021-10-11-03-13-28 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Dependabot kick.

Seeing if I can restart dependabot updates to this repo...

@dependabot

@dependabot help

@apache/dependabot is this anything?

Looks like there's a version mismatch issue going on:
https://github.com/apache/beam-starter-go/network/updates/13331218/jobs
Basically, the standard library added new packages, but our gomod version in the starter doesn't require that level of standard library yet. Fixing that should resolve dependabot problems.

Confirmed!
https://github.com/apache/beam-starter-go/pull/30


Return buffer from makeAmountInitialAndExpiration

When incrementing by certain values it looks like the buffer -> string -> buffer conversion that happens to the extras part of the header can lead to data corruption. Specifically bytes like FF are treated as multibyte string in the utf-8 conversion, so the resultant header is too long and contains the wrong info.
It's not clear to me that the buffer returned by makeAmountInitialAndExpiration should be converted to a string, and in my own usage simply removing that conversion prevents the issue. This PR removes that conversion and adds a couple tests.

Looks great other than the one nit on testMakeRequestBuffer

@alevy I've updated the method name. I also agree that testing more of the functionality is a good idea, but can probably be handled in a separate PR.


ci(postman): fix postman event.test.js for all connectors

Type of Change

[ ] Bugfix
[ ] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[x] CI/CD

Description
Some connectors had incorrect .event.json files and missing event.test.js files - which was impacting the postman import runs in the build and creating incorrect postman collection files which could not be used in the Postman UI.  This PR fixes that.
How did you test it?
Test generated postman collection in Postman UI and ensure event.test.js runs.
Checklist

[ ] I formatted the code cargo +nightly fmt --all
[ ] I addressed lints thrown by cargo clippy
[ ] I reviewed the submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

I ran the collections against Integ env locally after tests failed here:
Except forte and rapyd, rest of them passed. Failure has nothing to do with the changes made in this PR.


feat: colors convert from hex

Closes #1492

fix: resulting colors are incorrect

@emilk  🤔 that's odd one test fail with
thread 'color::test_to_hex_to_rgba' panicked at 'assertion failed: `(left == right)`
  left: `Color32([20, 1, 7, 2])`,
 right: `Color32([245, 40, 145, 255])`', epaint/src/color.rs:587:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I explicitly set rgba to Color32::from_rgba_unmultiplied(245, 40, 145, 2); but it produced [20, 1, 7, 2]
btw 2 because I wanted  0.2 not sure if this is correct

The benefit with a macro (e.g. egui::color!(#f5289133)) is that errors can be caught at compilation time. If users want to have dynamic string they should probably be using one of the many css color parsing crates.

Closed by https://github.com/emilk/egui/pull/1596


[example] Custom docker container example

Ready in https://github.com/bacalhau-project/examples/tree/custom-docker, waiting for the container to go public.

Completed a while ago: https://docs.bacalhau.org/examples/workload-onboarding/custom-containers/


docs: use master branch for latest updates

Separately, please do not send PRs to a project until you're sure they're welcome - etiquette is to discuss in issues first.

Thanks! Might want to update the CONTRIBUTING file or a PR template.

That etiquette is a universal default.


Added simultaneous multi touch events support

Added a touch identifier variable to allow multiple touches events at once.
Each Touch (start to end) works independently based on its identifier.

Nice. Did somebody test it?

Yes, i tested

identifier is started by 0..
0 and false is same...
there looks some problem with touchEnd

For touch it does not verifies if identifier is true or false. It's only verify if touchend identifier is equal to the the touchstart identifier.

@SeminYun  I agree, there is definitely a bug with touch end.

Please do not make PRs to the master branch, PRs are only accepted to the dev branch.
Please read through our Contributing Guide which details how to make good PRs and Issues.

You should so setup a GitHub PR template for that :)
On Thursday, 14 April 2016, Chad Engler<EMAIL_ADDRESS>wrote:

Please do not make PRs to the master branch, PRs are only accepted to the
dev branch.
Please read through our Contributing Guide
https://github.com/pixijs/pixi.js/blob/master/CONTRIBUTING.md which
details how to make good PRs and Issues.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/pixijs/pixi.js/pull/2415#issuecomment-210118285

--
Photon Storm Ltd.
http://www.photonstorm.com
Skype: richard.davey
Twitter: @photonstorm
Registered in England and Wales.
Company ID: 8036404
VAT Number: 136 4333 27

You should so setup a GitHub PR template for that :)

Yeah i know, I have a saved response but haven't got around to the template yet. Ideally what I want is master to be latest development, a release branch is the latest release, and to download the latest release you just go to the releases page (builds never get committed). But not sure how feasible it is now that so many are used to the current flow.


support markdown syntax (link)[#target-id]      ### section1 {#target-id} ,  click link jump to section1

https://www.markdownguide.org/basic-syntax/#formatting-links
see link code example

What's the context? Where would these links be used?

you click this url https://www.markdownguide.org/basic-syntax/#formatting-links, and find this line "I love supporting the EFF.
This is the Markdown Guide.
See the section on code.", then click word 'code', it will jump to code section which is in the same page. this syntx like html href="#section1" vscode markdown preview not support this syntax

Thanks. That syntax is non standard. We try to stick close to common mark  in core VS Code but extensions can contribute support for other markdown syntax features/flavors


Does not reload

If you click reload on the Homeseer integration, it will never reload, you just get "Failed to setup"
The only way you can get the Homeseer integration to work again is to restart Home Assistant.
Even when the Homeseer integration is working, if you try to click reload, you then get failed to setup and you have no other choice other that to restart home assistant?
Why does reload not work / break the integration?

I am experiencing something similar.  I can load the plugin on the latest version of HA it imports all my homeseer devices.  Works awesome.  When I reload home assistant-- it failed to load unless I delete the config/lsiopy directory.  I still see errors in the log but it works.
I run on Docker-- and from what I gather is the async directory that is imported here is now integrated into latest version of python...  Home Assistant runs 3.11 of pythonnow.
Not sure if just the "import async" needs to go away or if other stuff needs to change....
File "/lsiopy/lib/python3.11/site-packages/homeassistant/core.py", line 1650, in async_set
homeassistant    |     state = State(
homeassistant    |             ^^^^^^
homeassistant    |   File "/lsiopy/lib/python3.11/site-packages/homeassistant/core.py", line 1266, in init
homeassistant    |     raise InvalidStateError(
homeassistant    | homeassistant.exceptions.InvalidStateError: Invalid state encountered for entity ID: sensor.blplex_blplex_subscriptionfeatures. State max length is 255 characters.
homeassistant    | 2023-09-05 21:06:58.046 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up homeseer platform for sensor
homeassistant    | Traceback (most recent call last):
homeassistant    |   File "/lsiopy/lib/python3.11/site-packages/homeassistant/helpers/entity_platform.py", line 370, in _async_setup_platform
homeassistant    |     await asyncio.gather(*pending)
homeassistant    |   File "/lsiopy/lib/python3.11/site-packages/homeassistant/helpers/entity_platform.py", line 510, in async_add_entities
homeassistant    |     await asyncio.gather(*tasks)
homeassistant    |   File "/lsiopy/lib/python3.11/site-packages/homeassistant/helpers/entity_platform.py", line 750, in _async_add_entity
homeassistant    |     await entity.add_to_platform_finish()

Is this integration still supported? This is my first time attempting an installation. It is indeed a very useful Integration.
I also get the error “Failed to setup” after it confirms a successful installation. Reloading or rebooting HA does not help. Multiple removal and installation resulted the same outcome.
What I noticed was that there was an existing Integration using the same name “HomeSeer” which was the newly implemented official HomeSeer device support integration! Once I downloaded and installed this program, it basically replaced the official “HomeSeer” integration with the same name. Just wondering if this had anything to do with it?
Your help and opinions are much appreciated!
Thank you!

I am guessing it is not.  Posted June 22 and not a peep from the developer...


Include individual path checks in --verbose logging

This modifies ruff /path/to/file.py --verbose to include a message for each file that's checked. --verbose is, in truth, more like --debug, but this generally fits with what we include in verbose logging.
Closes #3423.

When running with --verbose, or without?

Mainly without. I'm not really concerned about performance when using verbose.

It does seem noticeably slower by a few ms (on a ~214ms baseline). I don't understand why or how though. Doesn't path.display() only execute when the log level is set to debug or higher?

Hmm, actually, this just looks like noise. I need a more reliable benchmark.


AAC Web Service server connection

Will submit in the coming days a role for adding Web Service server connection into the AAC. Currently, only LDAP role exist. Will provide as well the counterpart python code candidate implementation.

Resolved with https://github.com/IBM-Security/isam-ansible-roles/pull/60


aria-roledescription

On https://microsoft.github.io/devicescript/api/cli

This is an upstream issue with mermaid. Unlikely to fix.


[Feature]: expose repository information via v3 API

Related Problem
Most of the package metadata is exposed in the PackageDetail object. The API documentation doesn't mention it, but the server is also returning a repository string, but it seems like it's always empty.
The Elevator Pitch
The PackageDetail object should contain the repository information as well so that it is available without having to download and parse the nuspec file inside the nupkg file. It already contains the license, project URL, description, etc.
Additional Context and Details
In my case, I have the nuspec file, but it's inconsistent that I need to parse the repository URL out of the nuspec XML when the project URL and everything else is given to me in the API JSON.
This seems like it would be required for NuGet/Home#8584. The client can't cache all packages that the user might click on just to display the repository URL.

Hey @matt-phylum, this is a reasonable request. We have it already tracked here: https://github.com/NuGet/NuGetGallery/issues/6262.
Closing as a duplicate.


soft x-ray emissivity graph

Hello! I would like to reproduce the soft x-ray emissivity graph in the article about SMILE at a specific location, can you briefly explain the steps involved? Thank you!

Thank you for your reply. I don't have a timeline, but I just want to try your research results as soon as possible, hoping to help me with the data of my thesis. Thank you again!


Removed RemovedInDjango41Warning warning

Hi, and thank you! :tada:
I'll have to look into it next week, as I won't be home this weekend. I've kicked off the pipelines for now. :blush:

Seems like this would break 3.1.x support which could be a bit annoying, as it potentially could cause more backporting. However, since it does, I would like to have a 4.x release of Django to test against before I merge this.


tiup cdc changefeed list does not show the correct state in real time

Bug Report
Please answer these questions before submitting your issue. Thanks!

What did you do? If possible, provide a recipe for reproducing the error.
i tried to rename a primary key, and use the cdc to Synchronize this operation to mysql

What did you expect to see?
even if this operation is not allowed in mysql, it should not show the info after about 30min.

What did you see instead?
[2021/03/16 17:27:26.029 +08:00] [WARN] [mysql.go:202] ["execute DDL with error, retry later"]
...
[2021/03/16 18:07:57.065 +08:00] [WARN] [mysql.go:202] ["execute DDL with error, retry later"]
[2021/03/16 18:07:57.066 +08:00] [INFO] [owner.go:914] ["handle admin job"] [changefeed=test-cdc-7101] [type="stop changefeed"]
in some occasion, cdc should not try that many times

Versions of the cluster

Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
v4.0.0-beta.2-2332-gd1297376f-dirty

TiCDC version (execute cdc version):

IMHO during DDL retry, the changefeed should not be marked as failed or stopped, instead we should optimize the DDL retry mechanism, some errors can fast fail

It has been mitigated in https://github.com/pingcap/tiflow/pull/4262, we add exponential backoff to changefeed retry. Please feel free to reopen if it's still exists.


can't run ttyd on openwrt18.06

run command "ttyd bash"
show errors blow:
[2018/11/25 14:56:32:1462] NOTICE: ttyd 1.4.0 (libwebsockets 2.4.1)
[2018/11/25 14:56:32:1485] NOTICE: tty configuration:
[2018/11/25 14:56:32:1506] NOTICE:   start command: bash
[2018/11/25 14:56:32:1525] NOTICE:   reconnect timeout: 10s
[2018/11/25 14:56:32:1547] NOTICE:   close signal: SIGHUP (1)
[2018/11/25 14:56:32:1578] NOTICE: Creating Vhost 'default' port 7681, 2 protocols, IPv6 on
[2018/11/25 14:56:32:2288] ERR: ERROR opening socket
[2018/11/25 14:56:32:2292] ERR: init server failed
[2018/11/25 14:56:32:2296] ERR: Failed to create default vhost
[2018/11/25 14:56:32:2327] ERR: libwebsockets init failed
libwebsockets is installed on openwrt system.What's the problem？

I've seen this issue before, it should be an upstream issue. If you don't use IPv6, there is a workaround:
diff --git a/src/server.c b/src/server.c
index 96680d4..9eaf448 100644
--- a/src/server.c
+++ b/src/server.c
@@ -236,7 +236,7 @@ main(int argc, char **argv) {
     info.gid = -1;
     info.uid = -1;
     info.max_http_header_pool = 16;
-    info.options = LWS_SERVER_OPTION_VALIDATE_UTF8;
+    info.options = LWS_SERVER_OPTION_VALIDATE_UTF8 | LWS_SERVER_OPTION_DISABLE_IPV6;
     info.extensions = extensions;

     int debug_level = LLL_ERR | LLL_WARN | LLL_NOTICE;

I've added an option to toggle IPv6 support on master (disabled by default), you may want to try again.


this.sys.game.canvas is 0 in preload() and create()

By the delaying the init a bit, the home component has a moment to render the div/canvas. So the width and height will be set correctly in the Game Object in the Phaser Singleton
Pull request type

[ x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] E2E Test(s)
[ ] Other (please describe):

What is the current behavior?
Canvas height and width is 0 in preload() and create()
What is the new behavior?
The canvas height and width is set correctly in preload() and create()
Does this introduce a breaking change?

[ ] Yes
[ x] No

Other information
This is not the most prettiest of solutions, but fixes the issue. As well could start the discussion for a more elegant solution.

Very nice @ben-kn-app !   Approved and merging


pub.dartlang.org doesn't abort package upload on a cloud storage error

This issue was originally filed by<EMAIL_ADDRESS>
The latest version which I published appears to not have been stored correctly.
When downloading the package I get an error message. Apparently pub install also fails.
https://commondatastorage.googleapis.com/pub.dartlang.org/packages/postgresql-0.2.5.tar.gz
<Error>
NoSuchKey
<Message>The specified key does not exist.</Message>
</Error>

This issue has been moved to dart-lang/pub-dartlang#328.


Cache middleware

Caddy needs a cache middleware.
I'll be working on something basic this week. Probably just a basic LRU replacement algorithm and a configurable expiration time. In fact, if the gain is significant in nearly all cases, maybe it should be enabled by default... (a rare exception to the rule that all middleware need to be enabled explicitly using the Caddyfile).

I have a pull request with the beginnings of a solution here, https://github.com/mholt/caddy/pull/26

For anyone who is reading this thread who would like to contribute and is interested in cache middleware, feel free to pick it up - see the PR issue for details.

I just came across this thread and wondering maybe https://github.com/coocood/freecache can be used as cache middleware.

Perhaps an easier start to this middleware would be to implement some basic caching headers like ETag, Expires, Last-Modified, etc. See #191 for possible related discussion.

There is certainly a need for caching to scale Caddy. The profiling shows that the performance is hindered by File I/O being made for every request.Will soon release documents and reviews on performance and enhancement suggestion for each middleware from the profiling and performance tests I'm doing. I'm also looking at Groupcache and checking out whether it could be integrated for caching static contents

Using go-search.org, I've found two candidates to take parts from: https://github.com/gregjones/httpcache and  https://github.com/lox/httpcache .
My idea is to start small: have an in-memory response cache, with some nice eviction algorithm (W-TinyLFU, implemented by Damian Gryski: github.com/dgryski/go-tinylfu).
What we have to avoid at all cost, is caching something that shouldn't be - so take the header parsing logics from https://github.com/lox/httpcache and decide whether to cache and whether to serve from the cache, conservatively.
Maybe the "start small" method should be taken seriously: start with an in-memory TinyLFU, and cache only unambigous resources: file handlers, static file's contents.
Those static file contents could use fsnotify to avoid statting them! But I think that should be a separate PR.

I am needing basic caching for a production system.
Basic pragma tag technique would be enough for now.
I do need to be able to change the caching amount, without restarting caddy too if possible. This is because when the cache is invalidated varies by when we pump new data into the backend.
Any updates on this ?

https://github.com/lox/httpcache seems almost perfect to me, if only if it weren't for this issue. Perhaps we should see if we can sort that out first.

I'm happy to collaborate with you guys, I've recently been working on splitting out just the caching logic into a standalone library, as I think it's a separate problem to actually storing and looking up cached resources. Whether you guys would use that (called cachecontrol) or httpcache is up to you.

Pinging @weingart since interest in a cache middleware seems to be increasing. :smile:

I'm just started thinking on a cache directive, something simple like:
cache / 1h
or
cache / 1h {     except /wp-login /wp-admin     expire-key cache_delete  }
What i think is a good starting point is:
https://www.nginx.com/blog/nginx-caching-guide/
Can Benefit

proxy directive
fastcgi
futre minifys or html compressors.

Points:

On initial I think is better to focus in only caching GET and HEAD requests, and I think only for text content/types like (html, json, xml... ). Is absurd to cache binary files already served from filesystem. Actually the stdlib http server is good serving static files.
A Filesystem backend is enough. The general idea is to cache response blobs to files, and serve them directly with the send_file ( fileserver in go works this way), this way the memory managament is done by the kernel, and simplifies the problem. I can elaborate more on this, but I think that going forward on it, is out of scope of a web server (There are other good tools around to use just in case)
The cache directive should be defined per virtualhost. And should be up on the middleware chain, as starting, I think it should go just after the prometheus ...
The main principle for operation is to have a map[path]cacheitem, and on an incoming request, just check if key exists. In case it exists. The cacheitem should contain an expiration time, and a md5 of the host + path ( used to store the file on disk ). If item is not expired, it should serve directly the file.
If key doesn't exists or is expired and must be cached (is not on the exclude list), we need to record the response, store it on disk, and update the map.
We can also have some kind of manually expire mechanism ( perhaps a request with a key ) and on this case, we have to iterate over the dict, and delete matching keys. I think, something as simple as strings.HasPrefix is enough for this case, if you want to delete entries on path /posts .. (we can iterate over the map, and delete all /post (Not sure if is better to delete them or to mark them as expired, with a expired date)
Cache operations on files should be atomic. (Write first to a temp file, and move later to the correct key index? (Or we need some kind of locks on files) We don't want to serve a item from cache that is still not updated, also we don't want to duplicate efforts storing cache items in concurrent requests.

Doubts and things to solve.

I don't know what we should do with headers for cached requests.

What you think?
@mholt  @weingart @lox @jupiter

@lox That would be awesome.

I'm sorry that this has taken so long for me to respond.  Let me separate
out a few different types of caching:

using various http headers to encourage (or discourage) clients and
cache servers to cache content.  Such as cache-control, etc.    In the end, this still causes I/O to disk, possibly
optimized via sendfile(2) or other OS dependant methods.

caching small static content (such as favicon.ico, etc) in memory, such
that no I/O hits disk at all (other than swap, if you use it, please
don't!).

At one point, I was attempting to do #1 and #3 in the same shot.  I've
backed off, and am implementing #1 separately.  The only real reason that
it sort of requires some middleware, is that older browsers are more
finicky about how you tell them about content expiry.
The other half, #3, really needs to be included in the fileserver.go
(currently non-middleware) section.  I personally wish for this, so that I
can minimize the amount of I/O I incur, as "in the cloud", I/O costs money,
but I already have the memory, and serving from memory with a timeout for
the content being cached is faster and easier on the wallet.  :)
Number 2.  That one, I see so much trouble in.  I personally am not so sure
that it really belongs in a general purpose http server.  I would point at
squid, or other such, purpose built solutions for this.  Note, I don't with
to discourage people that want to implement such a beast, but I really do
think that a serious http based caching service should really be
implemented separately.  If you're really keen, using something like
groupcache, implementing a possibly distributed caching system, that can
front caddy (or possibly other http style servers), would be a large
project in itself as well.
Thoughts?
-Toby.
On Mon, Apr 4, 2016 at 12:47 AM, Pieter Raubenheimer <
<EMAIL_ADDRESS>wrote:

@lox https://github.com/lox That would be awesome.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/mholt/caddy/issues/10#issuecomment-205178125

For 1)
Separate 1 sound as the way to go. Also this should be the first part. For example, is necessary to respond with etags (I think this is already on tip)
For 2)
I think we need to focus on a target use case. We don't target users that are using varnish, or squid, or something else. As nginx, to have a small file based cache directive, is enough. There are a lot of situations where you can benefit from having it. Imagine a traffic pike on your wordpress site.. Just update the caddyfile and you are fine! Or imagine a busy backend, where you can't handle all the petitions, you can cache for an small time, and reduce notably these...
At the beginning, when we started this issue, and asked others (on the gophers slack), the common opinion is to leave the cache feature to the kernel, using the send_file. Is the same is doing nginx, and also I think is what is doing varnish.
By the way, I think that the cache storage should be decoupled from the cache middleware... At starting, it can be file based, but later, a redis backend could be implemented (also, groupcache, memcached)..
For 3)
Caching small files that can be served from disk is not a benefit. On the end, if you really need to handle big loads for static files, better you put them on a CDN, or object storage like (S3, gcloud, etc..). The cache directive must focus, on caching responses from expensive backends ( proxy, php_fpm, anewcoolmodulethatcanminifyhtml, etc... ) that is the most common bottleneck to your app.

Out of interest, what value does 1 offer without actually doing any intermediary caching in the server?

@lox

Out of interest, what value does 1 offer without actually doing any intermediary caching in the server?

A client can cache resources so it doesn't even have to ask the server for them, so the headers can enable client-side caching and inform intermediaries what to or not to cache. (Cache-Control! That should definitely be supported.)
@weingart Thanks for your brain dump :smile: I do largely agree with your points as well as what @jordic said; caching is not a light/easy task. I think Caddy should support basic caching features in its core, and leave advanced / power-user caching to optional plugins, especially if they involve third-party software/dependencies.
Tobias, what parts of this are you working on so far? It sounds like 1 and 3; but what is the caching strategy you are implementing?

I'm currently working on #1 (expiry headers, cache-control, etc).  The
other two I really think should be provided by 3rd party middleware.  I'm
also working on #3, but in part, that one is likely to be more
controversial, in that the cleanest way to implement (that I can see) is to
move the current fileserver.go into middleware, where it can still be
instantiated as an anchor, but could possibly be replaced by something that
does #3.
I think for immediate concern is #1, to be able to more easily specify
content expiry headers in a static configuration manner.  I consider #1 to
be essential, #3 to be an experiment I'm working on for myself, and #2 a
significant, non-trivial, endeavour.
A side note, the caching layer as described in #2, would make caddy now
have a "write to disk" style of code.  I'd consider this a possible
security risk/vector.  Yes, I understand that the user/content only has
minimal control over the location that things are written in (hash or hmac
values, oh, please use hmac instead of hashes, it allows for the
invalidation of the cache in a quick manner).  If nothing else, #2
incorporates the creation and management of persistent state, which is
notoriously difficult to deal with (usually).
-Toby.
On Thu, Apr 7, 2016 at 10:38 PM, Matt Holt<EMAIL_ADDRESS>wrote:

@lox https://github.com/lox
Out of interest, what value does 1 offer without actually doing any
intermediary caching in the server?
A client can cache resources so it doesn't even have to ask the server for
them, so the headers can enable client-side caching and inform
intermediaries what to or not to cache. (Cache-Control! That should
definitely be supported.)
@weingart https://github.com/weingart Thanks for your brain dump [image:
:smile:] I do largely agree with your points as well as what @jordic
https://github.com/jordic said; caching is not a light/easy task. I
think Caddy should support basic caching features in its core, and leave
advanced / power-user caching to optional plugins, especially if they
involve third-party software/dependencies.
Tobias, what parts of this are you working on so far? It sounds like 1 and
3; but what is the caching strategy you are implementing?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/mholt/caddy/issues/10#issuecomment-207223944

@mholt fairly familiar with what the caching headers are actually for (via https://github.com/lox/httpcache), trying to figure out what an http server that wasn't using the headers to actually cache/store/validate would need beyond "Add-Header" for different types of content.
@weingart out of interest, how does hmac allow for invalidation of cache in a quick manner vs non-cryptographic hashes? We are using sha256 in httpcache, but are likely going to move to fnv64a in the next release.
As I mentioned above, I'm currently extracting the validation and transport piece out of httpcache into a dedicated golang library. I've put my WIP up at https://github.com/lox/cachecontrol. Basically I want a library that is entirely BYO persistence layer. Interested in whether this will be a useful thing for you guys.

By changing the key, the hmac will generate a different hash.  In this way,
you can invalidate the whole cache (well, make it disappear) quickly.
-Toby.
On Fri, Apr 8, 2016 at 11:37 PM, Lachlan Donald<EMAIL_ADDRESS>wrote:

@mholt https://github.com/mholt fairly familiar with what the caching
headers are actually for (via https://github.com/lox/httpcache), trying
to figure out what an http server that wasn't using the headers to actually
cache/store/validate would need beyond "Add-Header" for different types of
content.
@weingart https://github.com/weingart out of interest, how does hmac
allow for invalidation of cache in a quick manner vs non-cryptographic
hashes? We are using sha256 in httpcache, but are likely going to move to
fnv64a in the next release.
As I mentioned above, I'm currently extracting the validation and
transport piece out of httpcache into a dedicated golang library. I've put
my WIP up at https://github.com/lox/cachecontrol. Basically I want a
library that is entirely BYO persistence layer. Interested in whether this
will be a useful thing for you guys.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/mholt/caddy/issues/10#issuecomment-207727967

@weingart
I don't see the point about 3).
filserver is a middleware... but is the last on the middleware onion, as I understand here:
https://github.com/mholt/caddy/blob/master/server/virtualhost.go#L30
From a middleware, you can intercept any request, and respond to it.. (using or not the subsequent layers): test if path exists on your backend, and serve with stored contents...
Ok, but, how to store items on the cache?: Build a ResponseRecorder, (execute the rest of the layers with this one, and you will have access to the written bytes blob. (@mholt, is this correct?)
Anyway, if what you want is serve files from ram.. just mount a tmpfs, and serve from them (let the OS do their job).
For the state:
I think a caddy new start should bring us a clean cache.
For the rest, i will preserve state in memory. As explained with a safe map.  And rebuild each entry as needed. Expiring all, is as easy as initializing the map. Expire a group of keys, just iterate over the map. and clean the keys ( no need to clean files on disk, they will be overwritten by new entries when arrived). Check if a key exists on the map, then check if key is expired..
Finally, I see one more important point on the main cache func... The rules to make a url eligible to be cached.
Incomming request.

Cache middleware test if url is cached, if true and not expired, serve cached content. (END)
If not cached, test if url is elegible for being cached. If not, continue with the middleware onion.
If true, start request recorder, record and store the contents.

You will want to stream the response body to the cache at the same time as to the client, blocking the downstream client until a response is cached causes timeouts for large files. Ideally concurrent requests to a resource being cached should be deduplicated too, but that is harder to do without a disk buffer.

On 10 Apr 2016, at 2:26 PM, Jordi Collell<EMAIL_ADDRESS>wrote:
@weingart
I don't see the point about 3).
filserver is a middleware... but is the last on the middleware onion, as I understand here:
https://github.com/mholt/caddy/blob/master/server/virtualhost.go#L30
From a middleware, you can intercept any request, and respond to it.. (using or not the subsequent layers): test if path exists on your backend, and serve with stored contents...
Ok, but, how to store items on the cache?: Build a ResponseRecorder, (execute the rest of the layers with this one, and you will have access to the written bytes blob. (@mholt, is this correct?)
Anyway, if what you want is serve files from ram.. just mount a tmpfs, and serve from them (let the OS do their job).
For the state:
I think a caddy new start should bring us a clean cache.
For the rest, i will preserve state in memory. As explained with a safe map. And rebuild each entry as needed. Expiring all, is as easy as initializing the map. Expire a group of keys, just iterate over the map. and clean the keys ( no need to clean files on disk, they will be overwritten by new entries when arrived). Check if a key exists on the map, then check if key is expired..
Finally, I see one more important point on the main cache func... The rules to make a url eligible to be cached.
Incomming request.

Cache middleware test if url is cached, if true and not expired, serve cached content. (END)
If not cached, test if url is elegible for being cached. If not, continue with the middleware onion.
If true, start request recorder, record and store the contents.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Good point for the first!
Not sure, but perhaps a pipe from the upstream writting the same time to disk and to downstream.
For the second, (when concurrent requests to the same resource).. two options come to my mind:
A) Lock them till resource is cached...
B) Bypass to the upstream not caching at all ...

@weingart I'm not sure I agree that solution 3, in-memory caching, would belong in the file server. One problem I see with this is accept-encoding. I would find storing gzip'd responses to be a high priority, and for this, a higher-level middleware would be required. If you want some rough numbers on why serving gzip'd content cached, in my opinion much more so than serving plain files from cache, see the table at https://kl.wtf/posts/minihttp/ (ignore the 39 seconds run for Caddy, as this is due to excessive GC pressure. With a bigger box, this is the same as "minihttp, disk, gzip").
The operation of a higher-level middleware would be a bit more complicated. If you are already progressing with injecting correct cache headers, the cache middle-ware would in theory consume these and act as a CDN-style cache proxy. If the cache-header "generator" generated a full set of cache-headers, which include different policies for CDN's and client-side caches, then this could in theory work, and would also include the benefit of automatically handling CDN's correctly (which you generally want to cache things differently than the client if there is dynamic content involved).
At this level, we would then store a response for each type of Content-Encoding. We could obey Vary to make things fancier, but the problem mainly lies in just having plain and gzip'd content.
The alternative would be some potentially complicated rules in a Caddyfile describing cache behaviour. A simple version would be "cache 2h /blog", but with dynamic content, these rules might turn less amusing, and partially duplicate the work done to ensure proper cache-headers.
I personally like the thought of the "cache-obeying" variant better, so that cache settings just relate to headers, and middleware will be able to say "DON'T CACHE THIS" (dunnnnn dun dun dun...).
Thoughts?

I've gotten https://github.com/lox/cachecontrol to the point where it captures most of the core rules around caching from rfc7234. Basically it should be useful for determining if a response is fresh or whether it needs validation.

Hi,
With nginx I use this cache method:
When the file exists on disk, nginx serve the file like any static file.
When the file doesn't exist it call the app (proxy). The app send the page and write it to disk. When the app decide to refresh the file it just need to delete the file.
http://nginx.org/en/docs/http/ngx_http_core_module.html#try_files
Don't know if it's currently possible with nginx ? And if not maybe it could be added in the cache middleware or elsewhere (a new issue for this) ?

Hey
I was wondering how we're doing on adding the caching headers (in a similar way to what @jordic described)
@weingart do you have your progress up somewhere? maybe I can pitch in to progress it, since caddy feels awesome; but I'd rather have http-server-level (basic) cache control

So any reason to not just use my httpcache library? It's exactly what it's designed for, would be useful to get some feedback on how it might better suit the usecase y'all have.

@lox I'm certainly not opposed to it (the lack of size constraints is a little worrisome, but I'm not sure what the implications there are) -- the thing about any cache implementation is that it absolutely has to be benchmarked properly to ensure that it is in fact delivering a speed boost within certain constraints of memory and disk space.

I have a suggestion for a cache library
https://github.com/golang/groupcache
I don't have intimate knowledge of the requirements for this present issue. However, the architecture, functionality and support is high quality IMHO.

@gedw99 groupcache has no expiration mechanism, it's for immutable content.

@mholt yup, agreed. I'd say that compliance with the spec is pretty important too though, and it's more complicated that first glance suggests. Happy to work with you guys to get size constrained storage and high performance. I've been working on a rewrite of httpcache that uses the cachecontrol library I wrote, should end up might leaner and quicker.

Makes sense.

Any progress on this?

Yes, i've been using caddy for some time now and this is a real necessity.
I want to help on that, there is already a PR from Thomas but someone made some progress on that?

Based on the discussion since that time, I'd recommend starting a new plugin from scratch that meets a very specific caching need, complete with carefully controlled benchmarks.

Just found this from a post on HN: https://github.com/nicolasazrak/caddy-cache - still WIP. Looks interesting.

I'll see if I can get httpcache integrated to it :)

Any progress on this lately? What is the latest status?

If that middleware above, by @nicolasazrak, is useful, I'd love to see it finished and published to the Caddy download page. (New site coming in a while.)

@mholt when I started the project the idea was to send a pr and be published in the download page but I found that doing caching was harder than I thought. I will continue with this project now that I have some free time and try to have something more polished

@nicolasazrak 🙌🏻🙌🏻🙌🏻

@nicolasazrak Sounds great. :) Yes, caching is hard. I would have attempted it myself... ;)

@nicolasazrak let me know if I can help. I am a noob at Go, but I'd love to contribute.

@azjkjensen help is always appreciated, if you want send me an email so we can work together (my email is on my profile)

Sorry for not reading all the thread ;) but if cache will be implemented, please check if its possible to make some "shared cache" in Caddy.
Like:
If I have several caddy servers (for redundancy or stanby) they are having the same cache storage. if 1-st Caddy caches something, 2-nd Caddy can use that object from cache and not fetch from backend again.
Maybe store cache in Redis or something.
That thing is really need for big prod sites. Unfortunately Varnish dont have such, will be cool if Caddy can.

Sounds like you're looking for groupcache as one option...
-Toby.
On Mon, May 8, 2017 at 12:42 AM, vladbondarenko<EMAIL_ADDRESS>wrote:

Sorry for not reading all the thread ;) but if cache will be implemented,
please check if its possible to make some "shared cache" in Caddy.
Like:
If I have several caddy servers (for redundancy or stanby) they are having
the same cache storage. if 1-st Caddy caches something, 2-nd Caddy can use
that object from cache and not fetch from backend again.
Maybe store cache in Redis or something.
That thing is really need for big prod sites. Unfortunately Varnish dont
have such, will be cool if Caddy can.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mholt/caddy/issues/10#issuecomment-299795925, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABLDSa-wW4ZancCZxtMOAYbN6bLicLsQks5r3sd4gaJpZM4EKzni
.

Very happy to close this with the near release of the http.cache plugin. :tada: https://github.com/nicolasazrak/caddy-cache


Fix: show empty cart when there is not order and cart is embedded

What does this PR do?
When the hosted cart is loaded as an iframe, we want to give the possibility to open it (empty) without the need to create a real empty order.
The scope of this PR is to emulate the empty cart state, instead of showing a generic 404 error when the order id is not passed in URL.
To achieve this a prior refactor was required:

move the internal grid inside the shared <PageLayout /> component to be used between the real <Cart />, <Skeleton /> and the new <EmptyCartEmbedded />.
when no order id is found in the getSettings() method we try to fetch at least the organization details, in this way we can show the empty cart with some branded ui (primary color)
Finally, we can show the empty cart, instead of <SettingErrors /> component when cart is embedded. This a slightly different from the real empty cart state (empty order), because it doesn't have the coupon code input or the return_url link which requires a valid order.

Some notes:

we assume that a string is still passed in url to match pages/[order.id]/index.tsx route, so /cart/empty or cart/null will work and will show empty cart state. /cart/ won't work and will show 404.
if orderId has a valid format (10 letters) but does not exist (eg: has been deleted) we still show 404 as result of getOrderDetails() method.
all other checks we do in the not-embedded cart are still applied, so if the subdomain does not match the token slug or the access token is not valid, we show 404 error message, etc...
Since we can't rely on order details, the empty cart embedded is only in English (unless we decide to pass some info as url params)

Screenshots
Cart embedded in demo-store, with no order in url  (new <EmptyCartEmbedded /> component)

Cart embedded in demo-store with real order id (eg. when all line items have been manually removed)

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


iOS10 and Swift 3 compatible.

Hi @supetronix
The actual version works great with Swift 2.3 and Swift 3.
https://github.com/dekatotoro/SlideMenuControllerSwift/commit/a74a0a26c21a49dcd4ed0c24fb352a68f89eff33
Thanks


"Boldești", "Gradiștea" are listed in the drop-down menu

Description:
When user writes "Boldești" and "Gradiștea" the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Boldești"
Expected results
The location appears in the drop-down menu as "Sat Boldești, PRAHOVA (Boldești-Gradiștea)"

Step 2
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Gradiștea"
Expected results
The location appears in the drop-down menu as "Sat Gradiștea, PRAHOVA (Boldești-Gradiștea)"


Incorrect result when using both sourceTime and tzinfo

Consider this example:
In [17]: cal = parsedatetime.Calendar()

In [18]: earlier, earlier.tzinfo
Out[18]: (datetime.datetime(2015, 6, 11, 13, 42, 27, 110402, tzinfo=<UTC>), <UTC>)

In [19]: cal.parseDT('now', sourceTime=earlier, tzinfo=timezone.get_current_timezone())
Out[19]:  (datetime.datetime(2015, 6, 11, 13, 42, 27, tzinfo=<DstTzInfo 'America/Chicago' CDT-1 day, 19:00:00 DST>),
 2)

In [20]: make_local(earlier)
Out[20]: datetime.datetime(2015, 6, 11, 8, 42, 27, 110402, tzinfo=<DstTzInfo 'America/Chicago' CDT-1 day, 19:00:00 DST>)

You can see that parseDT returns the same time of day as the sourceTime, but replaces the timezone, resulting in a different point in time. In this case I would expect either 13:42 UTC, or 8:42 CDT.

I have not studied the source to find where this is coming from, but this only seems to be a problem with exit code of 2 and relative times. Absolute times like '10AM' work as expected.

I'm experimenting with something similar. Is make_local your own function? parsedatetime and pytz don't seem to have it.

yes, that is a custom function. It is a wrapper around django timezone util that looks like this: timezone.localtime(dtm, timezone.get_current_timezone())

yes, technically this isn't a bug (well with parsedatetime ;)
parsedatetime isn't supposed to be TZ aware or care - that is up to the calling code to know.


Hapi 12+ and yar bug fix

From https://github.com/hapijs/yar

Starting with Hapi 12 the request.session placeholder was removed.
The guidance from Hapi maintainer Eran Hammer was for this and similar modules to move data storage away from request.session and use a more unique location. So, starting in 6.x.x the yar storage has been moved to request.yar

My solution:
index.js line 201 should be:
request.yar.lazy(true);
index.js line 206 should be:
session: request.yar,
Maybe you prefer a different approach to solve the issue

Thanks!  This module does require a little bit of maintenance right now to bring it up-to-date.

Come on, we can resurrect it :)

I don't think it will take much work, aside from the fact that it's officially time to write some proper tests for this plugin!

@devinivy advance thanks for test implementation of this plugin. HapiJS community will be happy to get oauth2.

@devinivy, I can take care of the testing.
What testing libraries would you use?
I like Jasmine + Frisby but they might not be the best to test chained calls... any library recommendation to dev the tests for the Oauth2 process?

@pabshazon I would personally use lab!


font tag hides text

When I use this code, sanitizeHtml removes both font tags and all contents inside fonts.
printed string is

var detail = "
" +
      "" +
      "" +
      "This is detail content.
" ;

print(sanitizeHtml(detail));

What is the expected behavior here?
Documentation says this follows rules applied for GFM sanitization.
This doesn't allow the  tag.
I think we could be open to extending sanitizeHtml with callbacks like:

bool allowTag(String tag), and,
bool allowAttribute(String tag, String attribute, String value).

I suppose one could also make the argument that we should not remove the contents of tags that are not allowed.
I think this is what the ruby library does too, see :remove_contents.
Maybe we should default to keep the contents of disallowed tags, while removing the tags, unless disallowed tag is one of: iframe math noembed noframes noscript plaintext script style svg xmp (for which contents should not be retained).


Update ICLA Link

Point new contributors to the Apereo agreement rather than the Jasig agreement to fix #847.

+1


Bash for nondeveloper

Add a bash for non-developer, who just wants to generate a .po file for a new language in order to start translation immediately and doesn't want to set up the environment.
This bash script automatically installs only what's necessary to generate a .po file from message.pot for a new language, and subsequently runs the msginit command to generate that file.

Inspire by @MathiasTELITSINE. He asked me if there is a way to only generate the .po file without all those programmers' stuff.

Hi @glihm can you review this PR? This bash is based on your translations.sh.

Thanks for this initiative @cryptonerdcn!
Here are my comments:

I think installing stuff is not "developer" related only. Because if we want your script being very generic, we must then install cargo too as we need to install the mdbook-cairo backend. Without it, even if you download mdbook, it is not running. In this case it will not only be related to translations, and it's a script like rustup that we need for the cairo-book (which can be great).

If we take apart this instalation stuff (or if we do a cairobookup script), it could be interesting that you add a command like translation.sh new xx instead of a new script, to abstract the msginit. What do you think?

If we are going your way with "on-the-fly" install of mdbook, I suggest to put this executable in the .gitignore to not confuse the user at the moment of the commit.

About the URLs you use for mdbook, you can refactor a having a MDBOOK_URL at the top, easier to maintain if the version has to change.

This is my take on the technical aspect, let's see @enitrat, @fricoben and/or others opinion on that.
But as you mentioned, it's definitely a good approach to add some abstraction for translators, but in my opinion the cursor may be adjusted and concerns well separated. :+1:

Thanks for this initiative @cryptonerdcn!
Here are my comments:

I think installing stuff is not "developer" related only. Because if we want your script being very generic, we must then install cargo too as we need to install the mdbook-cairo backend. Without it, even if you download mdbook, it is not running. In this case it will not only be related to translations, and it's a script like rustup that we need for the cairo-book (which can be great).
Thank you @glihm !  You are right I forgot cargo .

If we take apart this instalation stuff (or if we do a cairobookup script), it could be interesting that you add a command like translation.sh new xx instead of a new script, to abstract the msginit. What do you think?

Yes, it is a better way.  I just want to avoid modifying 'translations.sh' before but now you say we can change it so :p.

About the URLs you use for mdbook, you can refactor a having a MDBOOK_URL at the top, easier to maintain if the version has to change.
Agree.

This is my take on the technical aspect, let's see @enitrat, @fricoben and/or others opinion on that.
But as you mentioned, it's definitely a good approach to add some abstraction for translators, but in my opinion the cursor may be adjusted and concerns well separated. 👍

Yeah, let us discuss and then find a good way to accomplish this task.

Here's my take on this:
While it's great to have non-developer that can contribute to this book by translating content, I think that at least some familiarity with Cairo is required - that way, we're sure that the translator fully understands what he's translating.
In that case, I expect translators to have a minimum of experience in using the CLI, setting up environments, installing dependencies, etc.
I think it's a great idea to have this script available to make onboarding easier, however developing something like cairobookup seems a bit overkill. It's probably easier to just create an issue and ask to generate a translation file - but if the script helps and works, let's include it!

@glihm @enitrat I finished it, can you review my new update? Thanks!

@glihm  Thanks for your review! I fixed them.

@glihm Thanks for your review! I fixed them.

@cryptonerdcn don't hesitate to mark the review items as "resolved". :)
@enitrat look good to me.


Enable search on copy/paste

Can you explain how this feature works? I'm trying to think of what this does but i am drawing a blank.

Hacked via @mimlowe comment. Uses mouseover events...

Broken on mobile


Cleaning up zips after installation.

SUMMARY

When zips are downloaded from RHN to control node and/or control node to the target hosts, the zips are left over in the target hosts after installation. Should they be kept there or be cleaned up?
ISSUE TYPE

Feature Idea

We need to keep them there otherwise the collection will download them again. It all has to do with Ansible idempotency. If there is a customer request, at some point, to remove them, we can investigate this, but from Ansible point of view, it's a best practice to keep it there (at least IMHO).

Is that an acceptable answer @defeatedbylife ? Can we close this?


Emit change event when native "change" occurs

Description
The HTML color input supports two events: input and change.  input is already implemented, this PR introduces change.
Unlike the input which fires each time a value is changed, the change event is fired one time and occurs when the user has a selected color value and closes the color picker UI, essentially giving the user the final color value that was chosen.
Example Usage
<v-input-colorpicker v-model="my_color" v-on:change="handleChange"  />

handleChange(value) {
      console.log('You picked', value)
},

@dcustodio Thanks for creating this package. What do you think about this PR?

@bad-mushroom Thanks for contributing! That's a good use case. I'll add it!


Link to "benchmark section" in README doesn't point to anywhere

Points as non-existing hash: https://github.com/luin/ioredis#benchmark

@luin I looked into the README and it seems like there is no such section, can you elaborate on the meaning of this link? Did you mean to link to the benchmarks folder maybe?

There was a benchmark section but the content was outdated so I removed it. It was an oversight I didn't remove the link.


Compiling on Overleaf

When I compile main.tex  on overleaf, it fails to render to pdf. Here's the error log:
Package: fontspec 2019/10/19 v2.7d Font selection for XeLaTeX and LuaLaTeX

! Fatal Package fontspec Error: The fontspec package requires either XeTeX or
(fontspec)                      LuaTeX.
(fontspec)
(fontspec)                      You must change your typesetting engine to,
(fontspec)                      e.g., "xelatex" or "lualatex"instead of
(fontspec)                      "latex" or "pdflatex".

Type <return> to continue.
 ...

l.45 \msg_fatal:nn {fontspec} {cannot-use-pdftex}

And
! Emergency stop.
<read *>

l.45 \msg_fatal:nn {fontspec} {cannot-use-pdftex}

*** (cannot \read from terminal in nonstop modes)

Spoke offline and determined the resume must be compiled with XeLaTeX. Will update the readme.


Freeze on opening .otf

Hi,
when speedpunk plugin is installed .otf files won’t open.
Glyphs then does not react anymore.
When disabling plug-ins on start or after removing speedpunk it works just fine.
I then opened an .otf file and saved it as .glyphs.
This file also opens with speedpunk enabled.
Help would be very much appreciated. Thanks in advance.
Glyphs Version 2.6.6. (1352) running on MacOS 11.4

Can you reproduce it with the latest 2.6.7 beta? Go to Glyphs > Preferences > Updates, activate both checkboxes and press the Update button.

Seems to work fine in 2.6.7 (1356).
Thanks for the help and fast feedback.

Am 02.07.2021 um 14:16 schrieb Rainer Erich Scheichelbauer @.***>:
Can you reproduce it with the latest 2.6.7 beta? Go to Glyphs > Preferences > Updates, activate both checkboxes and press the Update button.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/yanone/speedpunk/issues/8#issuecomment-872953752, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUWFVPIJA76OWKO6H4OOZWDTVWUZRANCNFSM47U7TBKQ.


best practice

Nice work :clap: , we suggest the following for best practice:

DRY:

use a loop for repeated things

KISS:

use a shorter syntax

YAGNI:

delete unused functions or variables

Thank guys! :+1:


Draft version of #418 merged with workarounds removed

Edit: Issues listed below are resolved! Android should work now, just need cleanup and formal rebuilds in Jenkins. I hit one issue trying to fully gradlew build Gestalt after some recent changes but that may also be fine now and the snapshots in Artifactory may be enough for now to get this running for any further testing
Follows up on #418 by replacing the embedded source workarounds with binaries from our Artifactory, compiled once locally by me as test snapshops.
Main critical part was that @BenjaminAmos amazingly made it work with two versions of Gestalt live at the same time - the embedded Gestalt v7 for Android with the binary Gestalt v6 for the engine - somehow this didn't seem to cause any clashes, which is both cool and frightening 😁
With this (messy draft version!) I've switched over to pure v7 for everything, however that exposed a few parts of the engine that still targets v6 logic, which needs to be tweaked to work with v7.
After fixing that and officially merging the associated https://github.com/MovingBlocks/gestalt/pull/69 (which itself is a draft and needs cleanup) along with another quick Android tweak in https://github.com/MovingBlocks/DestSolAndroid/pull/2
Remaining issues in brief (really, just two classes!):

Uh oh, something went wrong with the build. Need to check on that

Uh oh, something went wrong with the build. Need to check on that

Uh oh, something went wrong with the build. Need to check on that

Outstanding work

[ ] Cleanup @Cervator's Gradle stuff
[x] Fix engine issues with Gestalt v7. Thanks @BenjaminAmos!
[ ] Cleanup and merge https://github.com/MovingBlocks/gestalt/pull/69
[ ] Merge https://github.com/MovingBlocks/DestSolAndroid/pull/2
[ ] Further Jenkins testing

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

While doing some gradle cleaning I noticed that having a code module present with the android facade causes problems. The game won't compile or run on either the desktop or android. Eek. Running gradlew android:assembleDebug with a code module fails, however it does manage to copy over the assets into the android/assets/modules directory. Thus after deleting the module from the root directory, another run of gradlew android:assembleDebug succeeds and includes the assets from the code module. Ships etc. work fine but the code doesn't run. It is evident from this that one must also delete the module from the android folder to properly get rid of it.

Were you testing using the warp module? The current android implementation dexes (translates java bytecode into android bytecode) module code using "dx" compiler, which does not support de-sugaring Java 8 bytecode, which new syntax features such as lambdas use. Without lambda de-sugaring, the minimum API level supported would be API 26 (rather than the current API 24).
The error encountered should appear like this:
com.android.dx.cf.code.SimException: ERROR in org.destinationsol.warp.research.uiScreens.ResearchUiScreen.updateCustom:(Lorg/destinationsol/SolApplication;[Lorg/destinationsol/ui/SolInputManager$InputPointer;Z)V: invalid opcode ba - invokedynamic requires --min-sdk-version >= 26 (currently 13)

Directly referenced libraries (such as gestalt and the engine library) are already dexed automatically using the newer "d8" compiler, which does support de-sugaring. I have modified the code to use the d8 compiler, although it does emit some warnings regarding missing interfaces.
The relevant changes needed to use the d8 compiler can be found here:
https://github.com/BenjaminAmos/DestSolAndroid/commit/0f924883e8fbca7231702cfb7f58995c9f34820e#diff-c197962302397baf3a4cc36463dce5eaL210-R269 .
Regarding the module not being removed, this occurs in two instances:

The first is that the modules directory is not being deleted from the android assets folder. This was unintentional, as at the time I did not realise that File.delete() only deletes empty directories or individual files.
The second was due to the caching of modules locally on the device. The cached modules were not being deleted upon re-installation of the application, so the removed modules were still being loaded from the local cache. Previously, the cache would only be updated when a new application version was detected, although removed files would not be deleted from the cache. The modules are cached on the local filesystem as gestalt does not appear to support loading the modules root directly from an archive (e.g. directly from the apk).

I have updated the module code to delete the modules sub-directory when a new build is performed. The changes I've made should cause the cache to always be re-created on start-up for debug builds and for other build types to only be re-created when a new version is detected (e.g. when the version changes from "2.0.0" to "2.0.1"). The cache is not always re-created by-default at it causes the start-up time to be slightly greater.
The commit will probably not merge cleanly, as it is based on several other un-related commits regarding support for older android versions (lowering the minimum to API 16), which I was previously planning to submit as a pull-request. The changes made should still be applicable to the current codebase, assuming that they are manually ported.
The relevant commit that should fix the module deletion issues can be found here: https://github.com/BenjaminAmos/DestSolAndroid/commit/e31541cca2d4f563f92386e36494b02579e4da44 .
The warp module does not appear to run with the android JSON parser though, due to an additional trailing comma that caused an incorrect array length to be inferred. I have pushed a commit fixing the error to my copy of the repository at https://github.com/BenjaminAmos/warp , which you may need to use instead to test the warp ships.

I tried cloning https://github.com/BenjaminAmos/codeModuleTest into modules and while it did assemble, it wouldn't install:
unknown output extension: "/home/nicholas/Documents/DestinationSol/android/assets/modules/codeModuleTest-code-0.1.0.jar"

Log is here
Now old warp does the same thing, as with your new warp so I guess I went crazy thinking it didn't assemble ¯\_(ツ)_/¯
I'll see what I can do about bringing those two changes over

Firstly, there is a bug where the modules are not dexed until the second time gradle is run. The changes made in https://github.com/BenjaminAmos/DestSolAndroid/commit/e31541cca2d4f563f92386e36494b02579e4da44?w=1 should fix that issue, which was causing the module's assets to be copied but not module's code.
The "dx" tool appears to interpret the surrounding quotes as part of the path on Linux. This does not occur on Windows. To fix this, you can change line 238 of android/build.gradle
from this:
commandLine (["$dex", '--dex', '--output', /*'--keep-classes',*/ "\"$jarOutputDir\""] + moduleClasses)

to this:
commandLine (["$dex", '--dex', '--output', /*'--keep-classes',*/ "$jarOutputDir"] + moduleClasses)

That fixed the issue for me, although the same issue will affect the d8 compiler as well. Removing the quotes does not appear to affect paths containing spaces on both Windows and Linux. The changes can be found in https://github.com/BenjaminAmos/DestSolAndroid/commit/285fa8d54cd8dec3e88f86e3dd59f08c864f36f7, which can be applied directly to the android subdirectory.
If applying the d8-relevant commits, then you will need to change lines 287-290 of android/build.gradle
from this:
 commandLine (["$dex"] + moduleClasses + ['--classpath', "\"$rootDir/engine/build/classes\"",
                         '--lib', "$path/platforms/android-$compileSdk/android.jar",
                         '--min-api', "$minSdk",
                         '--output', "\"$jarOutputDir\""])

to this:
commandLine (["$dex"] + moduleClasses + ['--classpath', "$rootDir/engine/build/classes",
                       '--lib', "$path/platforms/android-$compileSdk/android.jar",
                       '--min-api', "$minSdk",
                       '--output', "$jarOutputDir"])

I have applied the d8 changes in https://github.com/BenjaminAmos/DestSolAndroid/commit/f74e7c379a7ad9a78bc76dd81f3fbf72398d4b0c.

Thank you @BenjaminAmos that dx fix did the trick! We are getting so close to merging this. https://github.com/MovingBlocks/gestalt/pull/71 needs to be merged so that we can tweak and merge https://github.com/MovingBlocks/DestSolAndroid/pull/2 and then I can add these changes to DestSolAndroid. After that I believe it's just a matter of me cherry-picking over those other two commits (UI issue and rebase crash) and merging!

Uh oh, something went wrong with the build. Need to check on that

Hooray Jenkins reported success with all tests good!

Closing this in favour of #439 which has everything here plus those rebase fixes


Add default params_to_tune for feature selection transforms

Before submitting (must do checklist)

[x] Did you read the contribution guide?
[x] Did you update the docs? We use Numpy format for all the methods and classes.
[x] Did you write any new necessary tests?
[x] Did you update the CHANGELOG?

Proposed Changes
Look #1223. We forgot there about mrmr.
Closing issues
Closes #1223.

Codecov Report

:exclamation: No coverage uploaded for pull request base (automl-2.0@ee74651). Click here to learn what that means.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##             automl-2.0   #1250   +/-   ##
============================================
  Coverage              ?   7.60%
============================================
  Files                 ?     177
  Lines                 ?   10728
  Branches              ?       0
============================================
  Hits                  ?     816
  Misses                ?    9912
  Partials              ?       0

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


incorrect representation of nested arrays

Description
I have clickhouse database with some columns of type Array(Array(String)), Array(Array(Enum8)) or Array(Array(UUID))
When I trying to select those values I have incorrect representation of such values in results panel. Correct representation shown only when all values are fully expanded. Attached video wich would show problem
DBeaver Version
Community edition <IP_ADDRESS>409221725
Operating System
Debian GNU/Linux 12 (bookworm)
Database and driver
clickhouse 23.8
clickhouse jdbc 0.6.1
Steps to reproduce

create table with column of type Array(Array(String))
insert value like [['XXX'],['YYY']]
select value from table

Screencast from 2024-10-03 13-20-08.webm
Additional context
No response

Hello @kudrevatykh,
Can you please try the latest version of DBeaver to see if the issue is gone there? https://dbeaver.io/files/ea/

Hi @ShadelessFox
I tried ea version and it seems this version doesn't have this bug.

Thanks for checking out. I assume the issue can be closed now.


Catcher improvements

Removed catch_lured_pokemon.py
Removed catch_visible_pokemon.py
Added encounter check to catcher
Reduced list scans in catcher
Removed distance sort (no need)
Added random selection order

#4610 works but was added to depreciated files. This should accomplish the same.

CI Passed. Working fine on my tests.


rc.10 build server cause port problem when deploy on azure app service

Environment

Operating System: Windows_NT
Node Version:     v16.14.2
Nuxt Version:     3.0.0-rc.10
Nitro Version:    0.5.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
using a rc.10 nuxt 3 project
yarn run build and deploy to a azure app service
Describe the bug
RangeError [ERR_SOCKET_BAD_PORT]: options.port should be >= 0 and < 65536.
Received \.\pipe\8fdffe6b-11ec-435a-8240-a90d6391fabe.at new NodeError (node:internal/errors:372:5)at validatePort (node:internal/validators:217:11)at Server.listen (node:net:1500:5)at file:///D:/home/site/wwwroot/.output/server/chunks/node-server.mjs:575:18at ModuleJob.run (node:internal/modules/esm/module_job:198:25)at async Promise.all (index 0)at async ESMLoader.import (node:internal/modules/esm/loader:385:24)at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15)
process.env.PORT = \.\pipe\8fdffe6b-11ec-435a-8240-a90d6391fabe from azure app service
Additional context
the problem can be fix if i change the build file
.output/server/chunks/node-server.mjs
from rc.10 build server listen
const s = server.listen({ host, port }, (err) => {
to rc.9 build server listen
const s = server.listen(port, host, (err) => {
Logs
No response

this problem appear again using the Nuxt 3.7.0 with Nitro 2.6.2
currently edit .output/server/server/chunks/nitro/node-server.mjs
const listener = server.listen(path ? { path } : { port, host }, (err) => {
to
const listener = server.listen(port, host, (err) => {
can fix the problem

this problem appear again using the Nuxt 3.7.0 with Nitro 2.6.2 currently edit .output/server/server/chunks/nitro/node-server.mjs const listener = server.listen(path ? { path } : { port, host }, (err) => { to const listener = server.listen(port, host, (err) => { can fix the problem

Instead of changing the node-server.mjs file you should explicity set
NITRO_UNIX_SOCKET=.\pipe\25ca48bd-25d5-5ac8-b052-66e4d31687f7
– Or whatever path the socket is in.
This resolved the issue for me in a different environment.


Build failed with Cygwin in Windows10.Error: Cannot find module 'url/'

Describe the issue
$ npm install

$ npm run action src/www/start
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

> action
> node ./src/build/run_action.mjs "src/www/start"

       / __ \| |  | |__   __| |    |_   _| \ | |  ____|
      | |  | | |  | |  | |  | |      | | |  \| | |__
      | |  | | |  | |  | |  | |      | | | . ` |  __|
      | |__| | |__| |  | |  | |____ _| |_| |\  | |____
       \____/ \____/   |_|  |______|_____|_| \_|______|

  =========================================================
               © The Outline Authors, 2022
  =========================================================

▶ action(src/www/start):
  ▶ action(cordova/setup):
    ▶ action(www/build):
      node:internal/modules/cjs/loader:933
        const err = new Error(message);
                    ^
      Error: Cannot find module 'url/'
      Require stack:
      - C:\Users\hugetiny\WebstormProjects\outline-client\src\www\webpack_base.mjs
          at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
          at Function.resolve (node:internal/modules/cjs/helpers:108:19)
          at file:///C:/Users/hugetiny/WebstormProjects/outline-client/src/www/webpack_base.mjs:37:29
          at ModuleJob.run (node:internal/modules/esm/module_job:198:25)
          at async Promise.all (index 0)
          at async ESMLoader.import (node:internal/modules/esm/loader:385:24)
          at async loadESM (node:internal/process/esm_loader:88:5)
          at async handleMainPromise (node:internal/modules/run_main:61:12) {
        code: 'MODULE_NOT_FOUND',
        requireStack: [
          'C:\\Users\\hugetiny\\WebstormProjects\\outline-client\\src\\www\\webpack_base.mjs'
        ]
      }
    ▶ action(www/build): ❌ Failed.
  ▶ action(cordova/setup): ❌ Failed.
▶ action(src/www/start): ❌ Failed.

Environment

OS: Windows10
NPM version 8.11.0
Node.js version 16.15.1

still failed afternpm run reset


Consolidate how we set default tag and allowed tags for accurate documentation

In System arguments, we have:
All Primer ViewComponents accept a standard set of options called system arguments. This includes a tag option but it isn't necessarily true that a consumer can update tags. In reality, some of our components don't allow tags to be change since we set internally:
system_arguments[:tag] = :input

Other times, we have a default and allow tag to be changed based on user input:
system_arguments[:tag] ||= :input

OR
 def initialize(
      tag: DEFAULT_TAG,

And other times, we have a default tag which can be changed to limited tag options.
@system_arguments[:tag] = fetch_or_fallback(TAG_OPTIONS, tag, DEFAULT_TAG)

The documentation for components don't always surface this information making it unclear what the default tag is, what tags are allowed, etc.
Our Rake populates the default tag section by looking the component initializer and checking if there's a tag keyword:
 def initialize(
      tag: DEFAULT_TAG,

However, we don't always set default tag like this so that section in the doc ends up beingN/A for most components. This is a problem because it is ambiguous without looking at the component source code what tags are allowed, what the default tag is, etc.
TODOS:

[ ] update System arguments doc to make clear that some components don't accept tag prop
[ ] consolidate how we set default tag / tag options and ensure this info is reflected in the docs.
[ ] for components with no tag restrictions, think about if we actually want this.

@khiga8 off the top of my head, I think we should be explicitly allow listing tags for every component.

# remove tag from system arguments docs
# create TAG_ALLOWLIST for each component and slot we want to limit
# when tag has fixed tag, don't need to surface unless we want to
# for components that can render any tag, declare a tag parameter with default

6/21/21 Component-driven UI meeting

Leave out Tooltip because the Tooltip API itself is questionable. Debate about whether it should be a component.

@khiga8 I still think we should have an allow list of some sort for Tooltip. Do you think there's a minimal approach we could take to land something, even if it's not final?

I chatted with @manuelpuyol in my pairing session last week about what the allowed tags for Tooltip should be. The conversation shifted and both of us reached the conclusion that Tooltip is odd for a number of reasons and we should direct our efforts to either deprecating it or converting it to system_arguments. Tooltip will be out of scope of this issue, but I've opened an issue #663 to follow up.

@khiga8 sounds good. Want to close this out?


Introduce stack folders and neutral/localized stacks/global areas

See #3236
What remains to do:

[ ] import/export
[ ] stacks organized in folders when editing pages
[ ] context menu to rename/delete stack folders

This looks great. I'm sure there are a few things missing; we should start trying to build with this and see what else it needs.


question: require('app') vs. require('electron').app?

the former works for me, but i see the latter (which evals to undefined) in all the official docs. what's the blessed way to get an app instance?

If you're on v0.35 or later you should use require('electron').app, if you're on an earlier version use require('app'). If you are on v0.35+ and require('electron').app doesn't work double check you didn't accidentally install the electron module (which has nothing to do with Electron shell).
BTW, questions should go to the community, issues are for bugs/features.

that's the exact issue. thanks!
bummer that electron can't just be called "electron".