Can't pass cli args.

Neovide: Build from source
Rust: rustc 1.49.0 (e1884a8e3 2020-12-29)
OS: macOS 10.15.7 / Windows 10 Version 20H2 Build 19042.804

macOS:

Windows 10

Same here when downloaded from releases (Windows 10). Just doing .\\neovide.exe (from cmd.exe) works but .\\neovide.exe --version returns nothing on console and just flashes a window for split second, redirecting the output .\\neovide.exe --version 2> cmd.txt to a file shows the content ERROR [neovide::bridge] Neovide requires version 0.4 or higher.
However for me after building from source (5c6d84a4f1cbec26ed72f41a0c1f058aaaaeffd8) it works fine for neovide -v.

I can't reproduce this error when built from main source. Does it still happen from current main?

Not sure about @TENX-S but as I said it worked for me on the HEAD commit given in my comment, 0.7.0 from releases also works. 0.5.0, 0.6.0 did not work.

I think it's fixed.


model.py assumes weights file exists

It seems models.py assumes a weights file exists. With the repository as is it doesn't, did you initialize with imagenet weights or something or simply comment those lines the first time you run?

Thanks looks clear enough


Integrating jQuery-File-upload with Struts/Jsp

Hello all,
Since I'm a newbie to Web-Development mainly to Struts, JSP & jquery. So I need to integrate the plugin into Struts app. There is no any sample code to this reference so guide how to integrate this plugin in Struts/Jsp app. Any sample code reference will  be greatly helpful to learn.
Thanks,
Aravindh

The easiest way to integrate this plugin into a Java EE application is using a Java Servlet to handle the upload/delete events.
public class UploadServlet extends HttpServlet {

	private static final String BASE_DIR = "/Users/daniel/fileupload";

	/**
	 * @see HttpServlet#doGet(HttpServletRequest request, HttpServletResponse response)
	 */
	protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
		response.setContentType("application/json");
		File dir = new File(BASE_DIR);
		String[] files = dir.list();
		JSONArray array = toJSON(files);
		response.getWriter().write(array.toString());
	}

	/**
	 * @see HttpServlet#doPost(HttpServletRequest request, HttpServletResponse response)
	 */
	protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
		DiskFileItemFactory factory = new DiskFileItemFactory();
		factory.setRepository(new File(BASE_DIR));
		factory.setSizeThreshold(1024);
		ServletFileUpload upload = new ServletFileUpload(factory);
		try {
			@SuppressWarnings("rawtypes")
			List items = upload.parseRequest(request);
			for (Object object : items) {
				FileItem item = (FileItem)object;
				if(!item.isFormField()) {
  				    String fileName = item.getName();
				    File file = new File(BASE_DIR+File.separator+fileName);
				    item.write(file);
				    JSONArray array = toJSON(fileName);
					response.getWriter().write(array.toString());
				}
			}
		} catch (Exception e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		}
	}

	@Override
	protected void doDelete(HttpServletRequest request, HttpServletResponse response)
			throws ServletException, IOException {
		String name = request.getParameter("name");
		File f = new File(BASE_DIR+File.separator+name);
		if(f.exists())
			f.delete();
		response.setStatus(HttpServletResponse.SC_OK);
	}

	private JSONArray toJSON(String... fileNames) {
		JSONArray array = new JSONArray();
		JSONObject json = new JSONObject();
		for (String fileName : fileNames) {
			File currentFile = new File(BASE_DIR+File.separator+fileName);
			json.put("name", fileName);
			json.put("size", currentFile.length());
			json.put("url", String.format(URI_TEMPLATES.get("url"),fileName));
			json.put("thumbnail_url", String.format(URI_TEMPLATES.get("thumbnail_url"),fileName));
			json.put("delete_url", String.format(URI_TEMPLATES.get("delete_url"),fileName));
			json.put("delete_type", "DELETE");
			array.add(json);
		}
		return array;
	}
}

Daniel - I am trying to integrate this plugin with a web server unlike anything currently supported (SWI-Prolog's http libraries). I can do regular form file upload, and construct JSON responses, but I can't find any specification of the HTTP requests which must be handled, only obscure code for platforms of which I hope to remain forever oblivious ;-) and your Java Servlet skeleton implementation is my best hope so far, although I have only used Java SE, not EE. I have satisfied most of its dependencies with json-lib-2.4 and commons-fileupload-1.2.2 but how do I provide URI_TEMPLATES?

Hey there.
The URI_TEMPLATE is just a java.util.Map object holding the uri schemes for
deleting and retrieving a given file, so you dont really need to care about
it in you Prolog implementation.
On Wednesday, December 7, 2011, anionic <
<EMAIL_ADDRESS>wrote:

Daniel - I am trying to integrate this plugin with a web server unlike
anything currently supported (SWI-Prolog's http libraries). I can do
regular form file upload, and construct JSON responses, but I can't find
any specification of the HTTP requests which must be handled, only obscure
code for platforms of which I hope to remain forever oblivious ;-) and your
Java Servlet skeleton implementation is my best hope so far, although I
have only used Java SE, not EE. I have satisfied most of its dependencies
with json-lib-2.4 and commons-fileupload-1.2.2 but how do I provide
URI_TEMPLATES?

Reply to this email directly or view it on GitHub:

https://github.com/blueimp/jQuery-File-Upload/issues/766#issuecomment-3052742

--
Daniel Quirino Oliveira
http://nullability.org

May i know when i integrating this plugin with Struts2, did i still need the index.php ? what should i put for the action name in the jsp ? i found that this is a great plugin but a bit hard to a newbie..


Updated marten to v 4.3.1. Changed test file accordingly.

Updated MassTransit.MartenIntegration to use Marten 4.3.1.
How I verified the changes:

Ran unit tests in SagaPersistenceTests.cs
Extracted MassTransit.MartenIntegration code and included it into our own code base, referenced it and updated Marten to v4, and tested our solution (unit tests and manually) with it to see that it persited states as expected.

Marten was already updated for the v8 codebase. Thanks anyway though!

Oh right, I missed that. Great!


fixed resource flavor flaky test

What type of PR is this?
/kind bug
/kind failing-test
/kind flake

What this PR does / why we need it:
Flaky test
Which issue(s) this PR fixes:

Fixes #704

/ok-to-test

/lgtm

/approve

/release-note-none


Update Passenger

The passenger server running in development alerted me to a security vulnerability in the version I have been using, so I updated it.

Deploying to stage

Looks good on stage. Going to prod.


no sample[ 'mask_path']

keyerrot:'mask_path'
the sample does not have the part of ’mask_path'

and why “ cls_acc.append(sum(cls_acc_stage) / len(cls_acc_stage))
ZeroDivisionError: division by zero  ”

Which config do you use?
If using small batch size, it might have images with no positive samples. You can add eps like:

sum(cls_acc_stage) / (len(cls_acc_stage) + 1e-6)

sorry，i still have a question why once load dataset，later load the dataset all the time but do not load another dataset which path i have change


Opt into some Rails 7 defaults

Summary
I ran bundle exec rake app:update and picked sensible changes, like replacing single with double quotes. I also tried rearranging some code to reduce the diff produced by the app:update task, which might help in future updates.
Then, I opted into Rails 7 defaults, following https://docs.google.com/document/d/12xORkFvfQzPc3RC9A1HeDKdaom3cKr-hPSPqJBjU6XY. There are some defaults that need testing, so I'll leave them for a future PR.
Other Information

If there's anything else that's important and relevant to your pull
request, mention that information here. This could include
benchmarks, or other information.

Thanks for contributing to TestTrack!

/domain

Had some time to put https://github.com/Betterment/test_track/pull/197 together. As with chronos, it seems only specs related to cookies broke, so we should be good. We can try to update to the defaults in a single PR or I can revert if we'd rather do it in two steps.


test(pd): add client test script

Used this script to generate loadtests against a local pd instance, for memory profiling efforts. Steps I used to test:
pd testnet unsafe-reset-all
pd testnet join https://rpc.testnet-preview.penumbra.zone
# start pd & tendermint, wait for genesis to complete
./deployments/scripts/pcli-client-test -n 1000 -p 100

Refs #2867.

 After CI runs, I'm going to merge this, then cherry-pick the pd changes onto a release branch and tag as v0.56.1. As such, refs #2761. We still plan to release Testnet 57 tomorrow (#2827).


GitHub

metrics implemented...

Can one of the admins please verify this patch?

I guess the PR wasn't meant for this target repository.

sorry, this pull request is an error..

Still keeping an eye out on all the good work you guys are doing! Happy to see you still at it :-)


Incorrect team number in blog 4

Nice blog! I noticed that in your recent blog post on the project, you referred to the team of TabColor as Team 6, but instead it should be Team 8.
The issue is at here. And the full team list is here.

Thanks for pointing out! I will fix that in my next push.


Language model only returns runtime-retained annotations in build compatible extensions

The language model API itself doesn't specify what annotations are
accessible. In the CDI context, only runtime-retained annotations
make sense, because that's the only way all implementation strategies
can be consistent.

An alternative would be to specify that the language model always
returns only runtime-retained annotations. That would be just fine
strictly from the CDI perspective, but unforeseen cases may exist
where the language model API would be useful, but nothing would
prevent providing access to class-retained or even source-retained
annotations. Hence, I believe it is better to make the restriction
on the CDI level, and not on the language model level.

FTR the support for RetentionPolicy.CLASS was added into Jandex only recently and that's the reason why ArC does not consider this retention policy at all.

I think CDI is just built around runtime-retained annotations and I don't see a reason why (or even a way how) to change that.
It's true that Jandex ignores class-retained annotations right now (in version 2.x), and hence ArC does too, so my statement above is factually incorrect (until Jandex 3.0). But it's correct in principle :-)

Since we process the source those annotations are visible and we have methods in our metadata to differentiate whether an annotation is source or runtime. It would add overhead to filter out these annotations, I am not sure if there is any value if doing so. However I have no issue with the wording of only supporting runtime retention

My reasoning is that different CDI implementations should all present the same view of the world -- in this case, the same set of annotations.
This happened to me recently: I created an annotation, ran a test with it in the development version of Jandex and everything was fine. So I backported the test to Jandex 2.4, and it started failing for no obvious reason. Took me a little while to realize that the annotation didn't have a @Retention, so it was class-retained -- upcoming Jandex will return those just fine, while Jandex 2.4 ignores them.
I'd like to avoid similar situation between different CDI implementations.

I'm not sure we reached consensus on this, so just want to say that I'm open to changes. While I'd obviously prefer to specify it the way this PR did, I could probably be persuaded to softening the requirement to something like:

In build compatible extensions, attempting to obtain annotations from {@link jakarta.enterprise.lang.model.AnnotationTarget}
with a retention policy different than the {@linkplain java.lang.annotation.RetentionPolicy#RUNTIME runtime} retention policy
leads to non-portable behavior.


Add support for user-patches.sh

While using this helm chart, I have encountered permissions issues. For example, during startup, the script sets ownership of /var/mail to 5000:5000 (docker:docker). This results in sieve scripts to fail with permission issues. There is an article about being able to fix these kinds of issues using user_patches  . The default user-patch script looks as documented here. Some thing like
#! /bin/bash
##
# This user patches script runs right before starting the daemons. That means, all the other configuration is in place, so the script can make final adjustments.
# If you modify any supervisord configuration, make sure to run "supervisorctl update" or "supervisorctl reload" afterwards.
# To enable the script, you must save it in your config directory as "user-patches.sh".
##
echo "Default user-patches.sh successfully executed"

We should provide support for this in helm chart. Logic should be similar to how it is for am-i-healthy.sh in the file configmap.yaml.
The user should then be able to override these using values.

In the file configmap.yaml, we add the below section:

  {{ if .Values.userPatches }}
  {{- if .Values.userPatches.enabled }}
  user-patches.sh: |
    #!/bin/bash
    ##
    # This user patches script runs right before starting the daemons. That means, all the other configuration is in place, so the script can make final adjustments.
    # If you modify any supervisord configuration, make sure to run "supervisorctl update" or "supervisorctl reload" afterwards.
    # To enable the script, you must save it in your config directory as "user-patches.sh".
    ##
    {{- range .Values.userPatches.commands }}
    {{ . }} && \
    {{- end }}
    echo "user-patches.sh successfully executed"
    {{- end }}
    {{- end }}

In values.yaml, we add the below section:
userPatches:
  enabled: true
  commands: []

That sounds like a good improvement :) Would you be willing to submit a PR?

I have zero experience submitting a PR in an open source project...

Hi, @RangaSamudrala
This is funny, I came here exactly because of the same permission issue, and wanted to fix it using the user-patch :D
Do you have any estimated time to create the PR?

Yes, you can do this now by adding it to a mail-config volume. See https://github.com/docker-mailserver/docker-mailserver-helm/blob/master/charts/docker-mailserver/README.md#volume


Streamline the is_reentrant() library function.

I had some strange errors I think related to trying to get the previous call frame with the current one is zero.  Otherwise this change isn't much different to the existing code, just a little simpler.

Closes #1128


HHH-9570: Auto-detect SQL Server 2014

Copying a previous workaround for the same issue: https://github.com/hibernate/hibernate-orm/pull/395

Previously, SQL Server version 12 (SQL Server 2014) was an unknown version, resulting in the SQLServerDialect
Added version 12 to the switch statement so that SQLServer2012Dialect  is now returned by default, as SQL Server 2014 is much more similar to SQL Server 2012 than SQL Server 2000
Added test case

Thanks for the Pull Request.

Applied PR on 5.1 and master. Thanks for contributing.


[WIP] add VLLMModel

Motivation
Add VLLMModel for fast inference. Test result of ceval(gen) and WSC(ppl) on qwen-7b-chat:

Use cases
Example model config for qwen-7b-chat
from opencompass.models import VLLMModel

_meta_template = dict(
    round=[
        dict(role="HUMAN", begin="\n<|im_start|>user\n", end="<|im_end|>"),
        dict(
            role="BOT",
            begin="\n<|im_start|>assistant\n",
            end="<|im_end|>",
            generate=True,
        ),
    ],
    stop=["<|im_end|>", "<|im_start|>", "<|endoftext|>"],
)

models = [
    dict(
        type=VLLMModel,
        abbr="qwen-7b-chat-hf-vllm",
        path="Qwen/Qwen-7B-Chat",
        tokenizer_path="Qwen/Qwen-7B-Chat",
        tokenizer_kwargs=dict(
            padding_side="left",
            truncation_side="left",
            trust_remote_code=True,
            use_fast=False,
        ),
        pad_token_id=151643,
        max_out_len=100,
        max_seq_len=2048,
        batch_size=8,
        meta_template=_meta_template,
        model_kwargs=dict(
            trust_remote_code=True,
            dtype="float16",
        ),
        run_cfg=dict(num_gpus=1, num_procs=1),
    )
]

Things to note in the configuration file compared to HuggingFaceCausalLM:

In the _meta_template, you need to pass a stop. If not passed, the default is to use eos_token.
model_kwargs set dtype float32/float16/bfloat16

TODO:
The results of the get_ppl function seem to have problems, and this function is now very slow.

The prompt logprobs returned by vllm is a list of dict, not a tensor. It needs to be post-processed to calculate ppl, which is currently VERY slow, and I haven't found a better method.
The PPL result of WSC seems to have a problem, the result here is 67.31.

Cann not start vllm model using torchrun
If I use torchrun to start a Task, vllm will hang here, and I don't know how to solve this problem：https://github.com/vllm-project/vllm/blob/1f24755bf802a2061bd46f3dd1191b7898f13f45/vllm/worker/worker.py#L360

Motivation
Add VLLMModel for fast inference. Test result of ceval(gen) and WSC(ppl) on qwen-7b-chat:

## Use cases
Example model config for `qwen-7b-chat`
from opencompass.models import VLLMModel

_meta_template = dict(
    round=[
        dict(role="HUMAN", begin="\n<|im_start|>user\n", end="<|im_end|>"),
        dict(
            role="BOT",
            begin="\n<|im_start|>assistant\n",
            end="<|im_end|>",
            generate=True,
        ),
    ],
    stop=["<|im_end|>", "<|im_start|>", "<|endoftext|>"],
)

models = [
    dict(
        type=VLLMModel,
        abbr="qwen-7b-chat-hf-vllm",
        path="Qwen/Qwen-7B-Chat",
        tokenizer_path="Qwen/Qwen-7B-Chat",
        tokenizer_kwargs=dict(
            padding_side="left",
            truncation_side="left",
            trust_remote_code=True,
            use_fast=False,
        ),
        pad_token_id=151643,
        max_out_len=100,
        max_seq_len=2048,
        batch_size=8,
        meta_template=_meta_template,
        model_kwargs=dict(
            trust_remote_code=True,
            dtype="float16",
        ),
        run_cfg=dict(num_gpus=1, num_procs=1),
    )
]

Things to note in the configuration file compared to HuggingFaceCausalLM:

In the _meta_template, you need to pass a stop. If not passed, the default is to use eos_token.
model_kwargs set dtype float32/float16/bfloat16

TODO:
The results of the get_ppl function seem to have problems, and this function is now very slow.

The prompt logprobs returned by vllm is a list of dict, not a tensor. It needs to be post-processed to calculate ppl, which is currently VERY slow, and I haven't found a better method.
The PPL result of WSC seems to have a problem, the result here is 67.31.

Cann not start vllm model using torchrun
If I use torchrun to start a Task, vllm will hang here, and I don't know how to solve this problem：https://github.com/vllm-project/vllm/blob/1f24755bf802a2061bd46f3dd1191b7898f13f45/vllm/worker/worker.py#L360

@yingfhu Any idea about this problem?

Hi, @Sanster will you update this PR recently?

I have no plans to address the issues mentioned in todo, so I will close this PR for now.


Negative limit returns empty

Hi,
I've spotted some issues with negative limits in mongomock, they seem to return an empty batch. According to the doc, they should return the first batch similar to their positive counterparts, but they should close the cursor after that (https://docs.mongodb.com/v4.2/reference/method/cursor.limit/#negative-values)
mongomock from git from https://github.com/mongomock/mongomock/commit/5fe78c7030e1033d1b81964781ec173be92707e9.

Indeed, that's not OK. We should at least raise a NotImplementedError if we cannot implement the normal pymongo behavior.


move to scastie

Fixes #848
Problem
The scalafiddle link doesn't update automatically to the latest Quill version. Also, scalafiddle has limitations since it runs on javascript.
Solution
Move to scastie, it's stable now.
Notes
The scastie link points to the latest Quill version automatically using this SBT config:
libraryDependencies += "io.getquill" %% "quill-sql" % "2.+"

Checklist

[x] Unit test all changes
[x] Update README.md if applicable
[x] Add [WIP] to the pull request title if it's work in progress
[x] Squash commits that aren't meaningful changes
[x] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

@fwbrasil Do you mind removing wildcard in favor of lambda alias in quoted block? e.g. .filter(p => p.name == "John") It will generate query with p instead of x1 as table alias :)

@mentegy good point. Fixed

It's also possible to embed scastie into the quill website:
https://codepen.io/MasseGuillaume/pen/XzYzNb
more info:
https://github.com/scalacenter/scastie#embedded-resources

@MasseGuillaume I’ve opened another issue for that: https://github.com/getquill/quill/issues/970. I’d prefer to have scastie as a tab that expands similarly to Gitter ‘s sidecar


New Features: Background Image and Header

I added 2 features, which may be useful to others.

You can simply pass in a custom component as a Header to your Swiper
You can add a background image to your swiper
The README docs were updated with the new properties and an example was included in /examples/components/Header/
Let me know if you catch anything.

Enjoy!

Feel free to reopen this PR if needed, resolving conflicts at the same time. I would take a look at this PR then :)

@arribbar did you see conflicts somewhere?

Sorry, I do some cleaning. I can check it later and merge it if you need it. Just reopen it and I'll do it

@arribbar I will re open, thanks.


Simplify statistics class structure

Right now, the statistics classes all have interfaces and implementations. The interfaces were needed, because of the lack of multiple inheritance in Java where the event-bases statistics need to extend both the lower level statistic and the EventProducer. With the new event package, it is now much easier to embed an EventProducer rather than extend the LocalEventProducer. The additional advantage is that another EventProducer can be used, such as the RmiEventProducer.
The change involves:

embed the EventProducer in the event-based statistics classes
make event-based statistics inherit from the lower-level statsitics
remove the interfaces that are no longer needed

Embedding the EventProducer has as additional benefit that other types of EventProducers can be used. In the current version, all event-based statistics extend the LocalEventProducer, which means that using the RmiEventProducer is impossible. Embedding the EventProducer and adding an extra constructor that accepts an EventProducer also solves this problem.

Class structure simplified and above changes have been implemented.


fix attr for yolo_box

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


[SPGEMM] Bug Fix for indexing

The SPGEMM of indexing:
target value: mask[warp_id, mask->ind[edge]]
So I think the B_ind here should be mask_csrColInd[edge]

That looks right to me. Thank you for the fix!


Support MJPG pixel format

I've added support for MJPG, which is supported by my USB webcam. When using MJPG, the frame doesn't have to be re-encoded because it is already in the JPG pixel format. This drastically improves the performance – for me at least.

good job...


Client disappeared

The client connected but after 10 min he disappeared automatically while he still on. then never connected back

the antivirus is probably reactivated

Client antivirus?

Client antivirus?

Yes.

Any way to bypass antivirus?

Add exclusion within your AV software...

How?

Which AV are you using?

What is AV?

Antivirus software

I don't use any antivirus in my computer and windows defender also turned off

On Windows 10 (fully up to date) Defender will turn back on automatically after a short while..

That's my windows defender why it make disappear my client from RAT?

Why? It's a RAT, Add exclusion

Open Defender where you turn it off(manage settings). Scroll down and you will see "Exclusions" click on "Add and remove exclusions" choose folder where you have client or just the file your choice.

Yesterday I tested this RAT. The client which I was testing disappears from RAT. Before it was connected then suddenly disappeared

I am not talking about the file which I build but the victim disappeared after connected for 10 min

It seems problem with Remote Desktop because when I open Remote Desktop it disappears

port conflict?

I farwarded port and checked they were open

Please use the correct issue template. https://github.com/quasar/Quasar/issues/new?template=bug_report.md

Please use the correct issue template. https://github.com/quasar/Quasar/issues/new?template=bug_report.md


622 standardize all input fields

This PR:
Resolves #622
1.   Standardize New Message Modal
2.   Standardize Add Contact Modal
Screenshots (if applicable):

Only just noticing this. When using different browsers I got different margins for the same modal.
Chromium:

Firefox:

Haven't looked too much into this, but it may have to do with that modal using
 rather than setting the margins as "normal" the way other ones do. Add Contact uses margin="normal" rather than
 and looks the same on both browsers.

Thanks for finding that. This is why I didn't want to finalize the PR yet. Because there are different modals I haven't checkout yet. I'll be sure to check that out and see if I can find any other issues once I'm back from work.

Thanks for finding that. This is why I didn't want to finalize the PR yet. Because there are different modals I haven't checkout yet. I'll be sure to check that out and see if I can find any other issues once I'm back from work.

A long while back we were talking about not using
s and just use MUI's styling. But we never really settled on a plan so it's become a hodgepodge. This would be a good opportunity to standardize them.

I just decided to remove all the
 tags from the modals. It seems to be running fine on my firefox and chrome. Hopefully thats everything I'll be moving this over to review.

I'm in favor of using styling/CSS to adjust for spacing over
 since we'll have more control over margin and padding sizes.


TextInput prevent scroll on ScrollView

In a too long form, scroll is only available if the touch start outside the TextInput fields
React Native version:
info Fetching system and libraries information...
System:
    OS: Linux 4.15 Ubuntu 18.04.2 LTS (Bionic Beaver)
    CPU: (4) x64 Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
    Memory: 1.92 GB / 7.67 GB
    Shell: 5.4.2 - /usr/bin/zsh
  Binaries:
    Node: 8.10.0 - /usr/bin/node
    npm: 3.5.2 - /usr/bin/npm
  SDKs:
    Android SDK:
      API Levels: 22, 23, 26, 27, 28
      Build Tools: 23.0.1, 27.0.3, 28.0.3
      System Images: android-27 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
  npmPackages:
    react: 16.8.6 => 16.8.6
    react-native: 0.60.0 => 0.60.0
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native-debugger: 1.1.0
    react-native: 0.59.3

Steps To Reproduce

create a ScrollView with flex: 1
put more TextInputs than your screen can handle
try to scroll with your touch starting on a field

Describe what you expected to happen:
I expect the page to scroll
Snack, code example, or link to a repository:
     <ScrollView style={{ flex: 1, }}>
            <TextInput placeholder="test" textAlign='center'/>
            <TextInput placeholder="test" textAlign='center'/>
            <TextInput placeholder="test" textAlign='center'/>
            <TextInput placeholder="test" textAlign='center'/>
            <TextInput placeholder="test" textAlign='center'/>
            <View style={{ height: 150, }} />
            <TextInput placeholder="test" textAlign='center'/>
            <TextInput placeholder="test" textAlign='center'/>
            <TextInput placeholder="test" textAlign='center'/>
            <TextInput placeholder="test" textAlign='center'/>
        </ScrollView>

snack: https://snack.expo.io/@aiiros/react-native-issue-25594
this is a duplicate of https://github.com/facebook/react-native/issues/15962 which has not yet been answered.
Edit:
Turns out textAlign='center' is causing all of this

Hi @Aiiros,
I tried to reproduce your issue on Expo Snack: https://snack.expo.io/@robincsl/https:-github.com-facebook-react-native-issues-25594
and it seems to be working as intended: the TextInput components won't respond to touch when scrolling.
Can you provide a Snack/repository where you encounter this issue? This would help to reproduce it.

Hi @RobinCsl , thanks for answering.
After your example i stripped down my code to find out  that textAlign="center" was causing all of this.
expo exemple : https://snack.expo.io/@aiiros/textinput-prevent-scroll-on-scrollview-#25594

Exact same issue here, without textAlign="center" everything works fine

Also I am on a mac, so I guess we can remove the Linux tag?

@RobinCsl
I quickly changed your snack to show the issue. For the textInputs that are centering their text the scrolling doesn't work.
https://snack.expo.io/@markuscosinus/https:-github.com-facebook-react-native-issues-25594

@markuscosinus and this happens only on Android, right?
style={{textAlign: "right"}} shows the same behaviour as style={{textAlign: "center"}}. However, style={{textAlign: "left"}} works fine.
And yes, multiline={true} with style={{textAlign: "center"}} makes it work too.
Might be time to dig into the native code deciding on this behaviour! 🙂

I don't have an iOS device, but it works fine on the simulator.

Might be time to dig into the native code deciding on this behaviour! 🙂

That would be amazing. Thanks a lot!

It seems like this would be the place where touch events are handled:
https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/views/textinput/ReactEditText.java#L156-L179
@Override
  public boolean onTouchEvent(MotionEvent ev) {
    switch (ev.getAction()) {
      case MotionEvent.ACTION_DOWN:
        mDetectScrollMovement = true;
        // Disallow parent views to intercept touch events, until we can detect if we should be
        // capturing these touches or not.
        this.getParent().requestDisallowInterceptTouchEvent(true);
        break;
      case MotionEvent.ACTION_MOVE:
        if (mDetectScrollMovement) {
          if (!canScrollVertically(-1)
              && !canScrollVertically(1)
              && !canScrollHorizontally(-1)
              && !canScrollHorizontally(1)) {
            // We cannot scroll, let parent views take care of these touches.
            this.getParent().requestDisallowInterceptTouchEvent(false);
          }
          mDetectScrollMovement = false;
        }
        break;
    }
    return super.onTouchEvent(ev);
  }

I don't know Java enough, but my guess is that setting the alignment to center or right somehow makes the component think that it can scroll vertically or horizontally. I'm referring to this block:
https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/views/textinput/ReactEditText.java#L167-L173
          if (!canScrollVertically(-1)
              && !canScrollVertically(1)
              && !canScrollHorizontally(-1)
              && !canScrollHorizontally(1)) {
            // We cannot scroll, let parent views take care of these touches.
            this.getParent().requestDisallowInterceptTouchEvent(false);
          }

and searching the whole codebase for canScrollVertically or for canScrollHorizontally does not yield anything apart from the occurrences in this file.
I must say I'm a bit confused!

I don't know Java enough, but my guess is that setting the alignment to center or right somehow makes the component think that it can scroll vertically or horizontally.

That sounds logical.

and searching the whole codebase for canScrollVertically or for canScrollHorizontally does not yield anything apart from the occurrences in this file

canScrollHorizontally seems to be an method provided by android:
https://developer.android.com/reference/android/view/View.html#canScrollHorizontally(int)
But I have no idea, why it would return true just because of the text alignment

Okay, I think I found a solution!
I will create a PR later today!

Any updates ?

I created a PR 30 days ago and it hasn’t been reviewed yet. I don’t know if I should tag someone specifically to review it?

@RobinCsl Would your PR also fix this issue I opened a couple days ago?
https://github.com/facebook/react-native/issues/26526
If so, I can close that issue and include my snack.io examples in the comments here.

Don't close this issue. It's a major one and definitely deserves attention.

@RobinCsl Do you know if your fix ever found its way into a release?

Hi @edreyyo, as you can see, my PR is still open and I did not update it in a while since I've been busy. Feel free to push it further!
https://github.com/facebook/react-native/pull/25749

This is an important issue and still needs attention.

I am working on a pr https://github.com/facebook/react-native/pull/25749#discussion_r433079311

The issue is caused by canScrollHorizontally returns allways true for:
<TextInput multiline={false} textAlign="center" />

The method definition of canScrollHorizontally.
https://github.com/facebook/react-native/blob/9d6d39de86057f92d41a9f7eed7fdddf1ac09582/ReactAndroid/src/main/java/com/facebook/react/views/textinput/ReactEditText.java#L183-L184
I'll prepare a workaround

<TextInput
      multiline={true}
      numberOfLines={1}
    />

Set multiline=true and limit the numberOfLines can solve this problem temporarily

This is an important issue and still needs attention.

Any progress with your PR, @fabriziobertoglio1987?

@edreyyo I found a solution to this issue and included it in pr https://github.com/facebook/react-native/pull/29025
The problem is that my solution is a workaround, I have to disable the textAlign Center when editing the input field as some Android callbacks do not work with gravity Center on Android.
For this reason, my pr could cause rather then solve issues. Thanks.

@fabriziobertoglio1987 Alright, thanks for the update. Hopefully there's a fix available soon.

I fix this temporary whit this props (if this can help some one else)
multiline={true}  numberOfLines={1}  blurOnSubmit={true}  returnKeyType={"done"}

for my case I remove padding and it worked

Does this fix have any predictions for leaving? I tried this temporary fix but to no avail:
multiline={true} numberOfLines={1} blurOnSubmit={true} returnKeyType={"done"}

I fix this temporary with this props (if this can help some one else)
multiline={true} numberOfLines={1} blurOnSubmit={true} returnKeyType={"done"}

Thanks a lot, it is working

Does this fix have any predictions for leaving? I tried this temporary fix but to no avail:
multiline={true} numberOfLines={1} blurOnSubmit={true} returnKeyType={"done"}
Edit: I change the height the textinput and solved my problems

height is fail in case of Hebrew language or when you performing rtl activity.

I had the exact same issue. In my case, the problem was the default vertical padding in text inputs.
This padding takes some space and makes the input content scrollable. This is problematic for the outer ScrollView because it thinks you're trying to scroll the input content.
I fixed the issue by adding a paddingVertical: 0 style to my text inputs.

has this still not been fixed?

Any news on this issue?

still major issue

Can't we solve this without multiline = true ?

I'm still having the issue event if tried all those. Does any one have a better solution

@rvenky125 I figured out that editable prop when is set to false is the cause of the scroll issue, so I solved it (kinda) adding a readOnly prop and a validation in onChangeText method.
<ChildFieldText editable={true} multiline={true} numberOfLines={2} readOnly {...props} />

And in parent component:
onChangeText = (e: any) => {
    if (this.props.readOnly) return;
   ...
}

It's not the best solution but it works for me

@rvenky125 I figured out that editable prop when is set to false is the cause of the scroll issue, so I solved it (kinda) by adding a readOnly prop and a validation in onChangeText method.
<ChildFieldText editable={true} multiline={true} numberOfLines={2} readOnly {...props} />

And in parent component:
onChangeText = (e: any) => {
    if (this.props.readOnly) return;
   ...
}

It's not the best solution but it works for me

Thanks for your reply. But in my case, there is no need to change the editable. It's always true to me. Still, I'm having the problem.

I solved the issue by including these properties to the TextInput :
multiline
numberOfLines={1}

Multiline is not a proper solution because the return button on keyboard changes from default and also you wont be able to apply password type

So far it's serving me well:
https://github.com/facebook/react-native/issues/12167#issuecomment-1343804368

Thank you, your tip helped me to solve the problem in my case, as on android it does not use the files from the node_modules folder changing the files directly there had no effect, so I tried to build react native from source as instructed on the website: https://reactnative.dev/contributing/how-to-build-from-source to apply the fix, but I wasn't successful, maybe because the page is out of date, so I improvised and encapsulated the entire TextInput component in a package and changed the code snippet in question https://github.com/lucassouza16/react-native-reanimated-textinput/commit/49f04b6727d87fe80cf38f88e596b653b2de7910, the only downside is that the package only works for the react version I extracted it from, but I plan to recreate this component from scratch in case the developers don't solve these bugs in the future, it's sad to think that fixing the problem is so simple, even for me who have little knowledge, but the framework developers neglected it, and even sadder is going to your client and saying that you can't do something t It's not as simple as lining up a text in an input, without leaving usability a tragedy.

I fix this temporary with this props (if this can help some one else)
multiline={true} numberOfLines={1} blurOnSubmit={true} returnKeyType={"done"}

cool

If ScrollView working fine on Android and creating issue on IOS, then simply use scroll view property automaticallyAdjustKeyboardInsets= {true}

I am using RN 0.71, I have faced the same issue in my textInput, to solve this don't give any height to the textInput instead use extra view to adjust the heights. Thanks

I am using RN 0.71, I have faced the same issue in my textInput, to solve this don't give any height to the textInput instead use extra view to adjust the heights. Thanks

This solved the issue. Just dont give height. Thank you so much dude.

I am using RN 0.71, I have faced the same issue in my textInput, to solve this don't give any height to the textInput instead use extra view to adjust the heights. Thanks

its working, instead use minHeight

In my case, I noticed I was using import {TextInput} from 'react-native-gesture-handler'; instead import {TextInput} from 'react-native';.
Switching from the react-native-gesture-handler to react-native worked for me

Not stale

This issue still needs to be fixed.

A dirty workaround is to make the input multiline only when it is touched (to scroll)
`import { useState } from 'react';
import { TextInput as RNTextInput } from 'react-native';
function TextInput({ multiline, innerRef, ...props }) {
const [isMultiline, setIsMultiline] = useState(!!multiline);
return (
<RNTextInput
ref={innerRef}
{...props}
onTouchStart={() => setIsMultiline(true)}
onTouchEnd={() => setIsMultiline(false)}
onTouchCancel={() => setIsMultiline(false)}
onTouchMove={() => setIsMultiline(false)}
multiline={multiline || isMultiline}
/>
);
}
export default TextInput;
`

still issue

5 years later and this is still an issue lmao


Current logged user can't able see own sign-ins activity.

[Enter feedback here]
As mentioned in the document Any user (non-admins) can access their own sign-ins however in the azure portal user can't able to see and sign-ins link is disabled. Please correct the document or enable the link.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1558e7c0-eaaf-d081-30c3-5c13e0876071
Version Independent ID: 1106c01b-1e4c-5b04-be84-432f99ec4d8f
Content: Sign-in activity reports in the Azure Active Directory portal
Content Source: articles/active-directory/reports-monitoring/concept-sign-ins.md
Service: active-directory
Sub-service: report-monitor
GitHub Login: @MarkusVi
Microsoft Alias: markvi

Please refer the URL:- https://stackoverflow.microsoft.com/questions/232220

@jitendraRai
Thanks for your feedback! I have assigned this issue to the author who will investigate and update as appropriate.

I have clarified this in the article.
#please-close


[AutoDiff] fix _Differentiation rpath

I'm not very confident that this is the right thing to do. @compnerd could you take a look and let me know what you think?
The problem that this is fixing:
# In a SwiftPM package with a single main file:
$ cat Sources/testpackage/main.swift
import _Differentiation
print(gradient(at: Float(6), in: { $0 * $0 }))
$ swift run
dyld: Library not loaded: /usr/lib/swift/libswift_Differentiation.dylib
  Referenced from: /Users/marcrasi/testpackage/.build/x86_64-apple-macosx/debug/testpackage
  Reason: image not found
Abort trap: 6

Some commands that I ran for debugging:
$ otool -L /Users/marcrasi/testpackage/.build/x86_64-apple-macosx/debug/testpackage
/Users/marcrasi/testpackage/.build/x86_64-apple-macosx/debug/testpackage:
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1675.129.0)
	/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.100.1)
	/usr/lib/swift/libswift_Differentiation.dylib (compatibility version 1.0.0, current version 0.0.0)
	@rpath/libswiftCore.dylib (compatibility version 1.0.0, current version 0.0.0)
	@rpath/libswiftDarwin.dylib (compatibility version 1.0.0, current version 0.0.0, weak)
	@rpath/libswiftSwiftOnoneSupport.dylib (compatibility version 1.0.0, current version 0.0.0)

$ otool -l /Users/marcrasi/testpackage/.build/x86_64-apple-macosx/debug/testpackage | grep RPATH -A2
          cmd LC_RPATH
      cmdsize 32
         path /usr/lib/swift (offset 12)
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
--
          cmd LC_RPATH
      cmdsize 192
         path /Users/marcrasi/swift-base/build/Ninja-ReleaseAssert/toolchain-macosx-x86_64/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx (offset 12)

$ otool -l /Users/marcrasi/swift-base/build/Ninja-ReleaseAssert/toolchain-macosx-x86_64/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx/libswift_Differentiation.dylib | grep ID_DYLIB -A2
          cmd LC_ID_DYLIB
      cmdsize 72
         name /usr/lib/swift/libswift_Differentiation.dylib (offset 24)

This PR fixes the problem by changing the "install name" of libswift_Differentiation.dylib to @rpath/libswift_Differentiation.dylib which makes it get found in the toolchain. Here are the same commands after rebuilding the toolchain with this PR:
$ swift run
12.0

$ otool -L /Users/marcrasi/testpackage/.build/x86_64-apple-macosx/debug/testpackage
/Users/marcrasi/testpackage/.build/x86_64-apple-macosx/debug/testpackage:
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1675.129.0)
	/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.100.1)
	@rpath/libswiftCore.dylib (compatibility version 1.0.0, current version 0.0.0)
	@rpath/libswiftDarwin.dylib (compatibility version 1.0.0, current version 0.0.0, weak)
	@rpath/libswiftSwiftOnoneSupport.dylib (compatibility version 1.0.0, current version 0.0.0)
	@rpath/libswift_Differentiation.dylib (compatibility version 1.0.0, current version 0.0.0)

$ otool -l /Users/marcrasi/swift-base/build/Ninja-ReleaseAssert/toolchain-macosx-x86_64/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx/libswift_Differentiation.dylib | grep ID_DYLIB -A2
          cmd LC_ID_DYLIB
      cmdsize 64
         name @rpath/libswift_Differentiation.dylib (offset 24)

@swift-ci please test

Apologies for chiming in late -- it turns out we need a different change (#34216), since we need the install name in the dylib to be absolute (while allowing this scenario to work)

I think /usr/lib/swift/libFoo.dylib is the right install_name for these libraries -- after all, this is where they are expected to install when they get released, and it matches the configuration of other libraries. (Ignoring the pre-5.0 compatibility overrides in magic-symbols-for-install-name, which don't apply here.)
To test locally built libraries, our test configuration uses DYLD_LIBRARY_PATH to override the install_name. Would setting that be an acceptable workflow?


Use of the Date Format on the Source Data page?

What steps will reproduce the problem?
1. Go to a source page for a resource: /ipt/manage/source.do
2. The Date Format can be specified in the last field
3. This information is - to my knowledge - not used: what is is for?

What version of the provider software are you using? The version should be
displayed in the footer of any page.
IPT version 2.0.2-r3299

What browser are you using?
Chrome

Please provide any additional information below.
This information could potentially be used to transform non-ISO dates to ISO dates
in the mapping (would be very neat!), although I believe it might be more useful on
a field basis than a source basis.

Original issue reported on code.google.com by peter.desmet.cubc on 2011-07-28 22:05:13

Has there been an update in the Darwin Core Archive reader since?

A few related updates:

significant improvements have been made to the GBIF Parsers project with respect to date handling, see https://github.com/gbif/parsers/blob/master/assets/DateParsingDocumentation.md
Darwin Core Archive reader has been renamed dwca-io
dwca-io still doesn't handle date formats


The issue with issues

I suggested a while back that we should add an explanation about the use of issues in the readme.
@SmItH197 said it wasnt really neccessary so i dropped the subject, but I wasnt really happy with it.
SteamAuthentication has always had this problem with new developers trying to get their first project running with a steam login.
Lets face it, around 80% of all downloads are for the "next big" CSGO gambling site. Many inexperienced developers try that as their first project because it seems relatively easy at first.
When they then run into problems like mysql-integration, they ask here without having done any research. That is not accepted on any programing platform/forum (SO and the like) and why should we provide support for people that are not even willing to read through the closed issue list?
For that matter, I think we should indeed include a warning about off-topic issues getting closed.
And, if possible, someone more active should get the rights to close said issues.

I'm 100% with it - it's just annoying to get all the "how to use my brain" issues in my notifications instead of real issues. https://github.com/SmItH197/SteamAuthentication/issues/121#issuecomment-200257375
I'm willed to help guys to learn php and so on, but for that there are other places that are made for this reason like forums, chats or real-life meetups.

See my response on #121, I'll come up with something this week.

unfortunately i think no matter what comments are in the read me people will still continue to create "issues" based on not knowing how to use php/sql.
i agree someone else should also be granted the rights to close/label threads & in the readme a warning about off topic issues being closed
also im fairly sure i read somewhere recently that they are going to be shutting down csgo gambling sites (also EZSkins announced they are shutting down) which should help minimize these sorts of problems - don't quote me on it though [=

I'm having to do a lot of overtime at work at the moment as it's tax year end, I have a long weekend this week so I will be posting a few commits and tidying everything up and hopefully finishing the new example/demo site.
I've tidied up a lot of the issues, but will get round to the pull requests and commits on Friday. Thanks for your help with everything everyone, much appreciated! :)

you should just add a "general php" tag to bad questions and give more people rights to close it

Just merged #133, the number of crappy issues has definitely dropped off recently. I have created a new issues tag called "General PHP Query" and will be much more proactive with shutting down these kind of issues.
I will also close issues if the requester is using this library for gambling sites (Although it is up to them to disclose that - see #147.


Added additional element interfaces

Types of Changes
Prerequisites
Please make sure you can check the following two boxes:

[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project

Contribution Type
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
[x] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Description
I didn't realise when I did #977/#978 there were a number of other elements that didn't have corresponding interfaces. This PR doesn't currently fix all of them but adds a few more interfaces for common elements.
If you'd like, I can go through all the concrete types and add the same missing interfaces to them - just let me know.
(I didn't raise a new issue for this as I felt this kinda continued from the other issue and otherwise felt a little repetitive - if you'd rather I still do it, happy to do so)

My main reason for the interfaces is so I can go myElement is IHtmlWhateverTheElementIs myWhateverElement and access whatever properties that may (or may not) be mapped. Because the implementations are all internal, I'd need corresponding interfaces to do this instead.
I've used element.TagName == "A" etc but it felt weird doing that for some elements but not for others. Plus if I want to access the helper properties that match to attributes, I'd still need to cast.
But you've hit the nail on the head with your other comment, explaining the purpose of the interfaces. See, I thought they were more-or-less arbitrary but you mentioned the point was to match the W3C interfaces. With that in mind, I don't think these should be added then.
What I'll probably do in my code is use the tag name comparison and avoid any interfaces, instead use the HasAttribute/GetAttribute methods directly to get what I want. That way my code can at least stay consistent within itself.


Fix with_coverage

After merging #4414 with_coverage is failing

FYI This is 6th February using the new grcov report from Vasiliy

As of 2cf50c0da I2::Dev::Tests / with_coverage is failing due to -p iroha_client --test mod (client/tests/integration/). It seems to happen with the following combination:

nightly-2024-04-18
RUSTFLAGS="-C instrument-coverage"
-p iroha_client --test mod

not filtered out, because #[cfg(not(coverage))] is allowed by cargo-llvm-cov and does not work with grcov

I don't know the exact cause, but we can work around this. Just exclude the client integration tests in command without attributes


fix: filtering and sorting in useNotifyProjects

Description

Change sort order from descending to ascending Slack thread Resolves #321
Fix bug in filtering. Resolves #334

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Draft PR (breaking/non-breaking change which needs more work for having a proper functionality [Mark this PR as ready to review only when completely ready])
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Fixes/Resolves (Optional)

Resolves #334
Resolves #321

Checklist:

[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

LGTM :+1:


compatibility with numpy 1.18

Description
Fixes #826 caused by an expired deprecation in numpy:

np.linspace parameter num must be an integer. Deprecated in NumPy 1.12.

https://numpy.org/devdocs/release/1.18.0-notes.html
sorry that I missed this is #800.  somehow I thought it was due to code outside of napari... will take another look at our deprecations and follow up with additional PRs if any are found.
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

References
https://numpy.org/devdocs/release/1.18.0-notes.html
How has this been tested?

[x] all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality

ah crap... sorry about that. i missed that it used my (ambiguous) first title for the commit message instead of the edited one.  I'm afraid to amend and --force push that last commit to master.  So unless you'd prefer me to do that, let's just remember to put a more intelligible message in the next release notes.

That’s fine - what should the message in the release notes be? Just so we have it here in the PR

the current title of this PR is fine: "fix compatibility with numpy 1.18"


Refactor argparse options

Just a warning, a lot of this is just moving code around and renaming it, but in some of those instance its fixing bugs (see below about SMB opts).

Allows us to pass in top level (universal) options ANYWHERE, meaning we can just append --debug to a command and it will work as intended.
Fixes some other parsing issues, like some argparse groups in SMB were named the same (not sure how that didn't cause issues), and a lot of the groups had nonsense names.
Adds a default option parser (DisplayDefaultsNotNone), so we do not have to include "Default: xyz" in the help information for options - it will automatically display those if they are not an empty string, None, False, etc.
Updates commands into better groupings
Adds testing the help for each protocol (might not need this, like the --options we just removed, @NeffIsBack?)

Fixed conflicts with newly merged stuff (only big one was setting the retries to 10)

Updated to include the new DNS options, so you can put them at the end now :)

Functionality looking good so far


Release baresip version 0.6.3

We are planning to make a new release of baresip.
Please help with review, testing, documentation etc.

compile testing on supported platforms
basic testing against other SIP endpoints
make should pass with no warnings
make test should pass with no errors

Platforms:

[x]  Debian 8
[x]  Debian 9
[x] iOS 11.2
[x]  Mingw (Debian 8, gcc 4.9.1, wine 1.6.2)
[x]  OSX 10.14
[x] Raspbian 9.6 (arm)
[x]  Ubuntu 16.04
[ ]  Ubuntu 18.04 LTS
[ ]  Windows 8.1
[ ]  Windows 10

SIP Testing:

[ ]  Linphone 4.1.1 (OSX Desktop)
[ ]  Jitsi
[ ] FreeSwitch
[ ] iptel.org (ser 3.3.0)
[ ] sip.antisip.com (kamailio 5.2.1)
[x]  Zoiper 5.2 (OSX)

also please have a look at the new Wiki page with modules:
https://github.com/alfredh/baresip/wiki/Modules
if you want to maintain a module, please add your name to the list :)

I have set the target release date to Saturdag 22. June 2019
unless there is any critical bug report before that, the release
will go ahead as planned.
Alfred

baresip 0.6.3 is now released:
http://lists.creytiv.com/pipermail/re-devel/2019-June/001372.html


pbxProject.prototype.addFramework: automatically create Frameworks Group if it does not exist

This is a feature proposal
Initial Situation:
Your xcode project tree looks like this:

You have a Xcode project without a Framworks group and you want to add a new framework using pbxProject.prototype.addFramework.
Current behaviour:
The Frameworks group is created but not added to the mainGroup of the project which references all files (that are not part of a subgroup) and all groups (that are no subgroups).
If you open the updated xcode project with xcode you see the following:

This is because xcode cannot find a reference to the Frameworks group on the mainGroup and therefore "autofixes" the project by adding the library added with pbxProject.prototype.addFramework to a newly generated group Recovered References.
Expected behaviour:
The Framework group is created and also automatically added to the mainGroup.
When you open the project in xcode it should look like this:

Current workaround:
Add the Frameworks group to mainGroupmanually:
  const project = xcode.project(projectPath);
  project.parseSync();

  project.addFramework(path.resolve(frameworksDirectory, 'GoogleInterchangeUtilities.framework'), {
    customFramework: true,
    embed: true,
    link: true,
  });

  const mainProject = project.getPBXGroupByKey(project.getFirstProject().firstProject.mainGroup);
  if (!mainProject.children.some(children => children.comment === 'Frameworks')) {
    const [groupKey] = Object.entries(project.hash.project.objects['PBXGroup']).find(
      ([, group]) => group.name === 'Frameworks',
    );
    project.addToPbxGroup(groupKey, project.getFirstProject().firstProject.mainGroup);
  }

If you are okay with this feature proposal I would love to implement it!

Idk actually if this is a bug or intended behaviour

I think we never encountered an issue with this since we would always create the iOS or mac osx project from a template with Frameworks group already in the right place.
I like the idea of fixing this but would love to better understand the need and use case. How is your Xcode project initially created?
If you are using this in an open-source project can you give us a pointer?

Actually it is a project that was created using npx react-native-cli init TestApp but modified a.k.a the Frameworks group was dropped.
I just tried setting up a new project using Xcode and it has not Frameworks group.

[...]
I just tried setting up a new project using Xcode and it has not Frameworks group.

Got it. This looks not quite standard for React Native. According to https://facebook.github.io/react-native/docs/native-modules-ios#native-module-setup is that native modules would normally be distributed as npm packages, which the React Native tooling would import when you build an application.
But we should do something better than putting frameworks into a "Recovered References" group, as proposed here.

@n1ru4l
In my project,there is no "Resouces" in PBXGroup.
It will throw an error when I try to add some images to project with addResourceFile function.
And this is my project file project.pbxproj


the relationship between indoor3d_sem_seg_hdf5_data_test and indoor3d_sem_seg_hdf5_data？

Excuse me, the relationship between indoor3d_sem_seg_hdf5_data_test and indoor3d_sem_seg_hdf5_data？

indoor3d_sem_seg_hdf5_data_test is for testing set, and indoor3d_sem_seg_hdf5_data is for training set.

请问，这俩都是完整的数据集吗，那怎么区分测试的时候在指定area测试？

See https://github.com/AnTao97/dgcnn.pytorch/issues/6

好的，感谢，明白了


Add more images

Simply add strings of the full url path to the array backgroundUrls.

@emt1166

@DanTheManGude  I can

Hello @DanTheManGude
Can you accept to merge my solution. I have been submit it.


[PHPStanRules] Remove parent from NoMissingDirPathRule

@clxmstaab Hi Markus,
as to your question on Twitter, this was quite a challange to figure out :) I had to sleep on that to get the idea. Let me know what you think.

This solution is now pretty simple, but getting there was like 4 blind paths :D you should've seen that
It's simple :) That's a node, that contains class node that has available class reflection in scope. Nothing more.

Btw, Rector is using principle of least surprise and adds the scope directly to Class_ node 👍


Column formats in data quality objectives file for accuracy

@ben-wetherill just adding this here for the record.  On importing the accuracy file, the Spike/Check Accuracy is formatted incorrectly because Excel stores the values as numbers.  There is no way to know which value is a numeric or percentage range for the checks because the values are all imported as numbers, e.g., a number is imported exactly as visually shown, whereas a percentage is converted to a decimal value. Unfortunately, there is no way to have R identify values differently because of how Excel stores the information, i.e., what you see when you open the spreadsheet in Excel is not how the values are stored.  The issue is explained in depth here: https://github.com/tidyverse/readxl/issues/462 One of the many reasons Excel is problematic...
The solution is to convert the column to text in Excel.  I've done this for the example accuracy file, so we should be good to go.  Users will just have to know this is a requirement to correctly use the accuracy check functions.  I've added a better check for the accuracy file to verify that the column formats are correct on import.  See this commit: 100584d348fc43806eacb08093b64763b9c82086

@ben-wetherill I think adding a "<=" sign for entries in the spike/check accuracy clumn would force the cell as text, percent or no, so that would work.  I agree that asking users to save the whole column as text is problematic.
For your second comment, consistency is usually better, so my vote is to enter everything similarly across the columns.  However, the code evaluates the equality operators written exactly as is, if they are provided, i.e., "<" does not include the value, "<=" does.  I'm not sure this is intentional.  It makes sense for the value range column since this describes the entire set of values in question for a parameter.  But, for example, Field Duplicates always include "<=", whereas Field Blanks only include "<".  Was this on purpose or should they all be changed to "<="?  And anything that doesn't have an equality operator is evaluated as "<=" based on absolute difference.

Thanks @ben-wetherill, my vote is for the second file (equality operators in cells, not headers), because it would work with the existing import functions.  I'd have to reprogram the checks and figure out how to transfer the equality opeators to each cell if we were using the first file.  I'd like to continue with the second file if you're okay with that.

I'm fine with keeping the equality operators in the cells vs the headings to avoid undoing work you've already done, @fawda123. With the DQO file only being created once it's not a big ask for groups to format it this way and I find it more flexible as well (e.g. perhaps a group would rather have a field blank DQO for Spec Conductance reported at <=24 as opposed to <25). Not sure how likely that scenario is but added flexibility is rarely a bad thing.

Sounds good to me.


fix: performance issue

LGTM

Does this exist in master, too?

Does this exist in master, too?

@Qix- master is ok

Released as<EMAIL_ADDRESS>


flutter app throws so many non-fatal exceptions from Firebase storage links

In our Flutter app, we are loading the images from Firebase Storage.
Crashlytics shows so many exceptions from the firebase storage links.
I believe it has nothing to do with the firebase plugin because the images are loaded from the URL with the widget CachedNetworkImage.
    CachedNetworkImage(
          imageUrl: content.image,
          fit: BoxFit.cover,
          width: double.maxFinite,
          placeholder: (context, url) => placeHolder,
          errorWidget: (context, url, error) => placeHolder,
     );

Exceptions:
Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
SocketException: Failed host lookup: 'firebasestorage.googleapis.com' (OS Error: No address associated with hostname, errno = 7). Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: SocketException: Failed host lookup: 'firebasestorage.googleapis.com' (OS Error: No address associated with hostname, errno = 7). Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
SocketException: Connection reset by peer (OS Error: Connection reset by peer, errno = 104), address = firebasestorage.googleapis.com, port = 48848. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: SocketException: Connection reset by peer (OS Error: Connection reset by peer, errno = 104), address = firebasestorage.googleapis.com, port = 48848. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
Connection closed before full header was received. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Connection closed before full header was received. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
Connection closed while receiving data. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Connection closed while receiving data. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
Software caused connection abort. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
HandshakeException: Connection terminated during handshake. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: HandshakeException: Connection terminated during handshake. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
HandshakeException: Handshake error in client (OS Error: CERTIFICATE_VERIFY_FAILED: unable to get local issuer certificate(handshake.cc:393)). Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: HandshakeException: Handshake error in client (OS Error:
	CERTIFICATE_VERIFY_FAILED: unable to get local issuer certificate(handshake.cc:393)). Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
Connection reset by peer. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Connection reset by peer. Error thrown Instance of 'oda'.

Example Image URL:
https://firebasestorage.googleapis.com/v0/b/agenda-boa-test.appspot.com/o/content feed test.jpg?alt=media&token=999a7d13-dfcd-477b-b44e-e307cfc4bdcb

flutter doctor -v
[✓] Flutter (Channel stable, 2.10.3, on macOS 12.3.1 21E258 darwin-x64, locale
    en-US)
    • Flutter version 2.10.3 at /Library/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7e9793dee1 (8 weeks ago), 2022-03-02 11:23:12 -0600
    • Engine revision bd539267b4
    • Dart version 2.16.1
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/appleapple/Library/Android/sdk
    • Platform android-31, build-tools 30.0.2
    • ANDROID_HOME = /Users/appleapple/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] IntelliJ IDEA Community Edition (version 2019.3.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.66.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.26.1

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 100.0.4896.127

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

@danagbemava-nc I'm not able to reproduce this locally. Just getting these exceptions in Crashlytics from the users.

another one:
Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
SocketException: Connection timed out (OS Error: Connection timed out, errno = 110), address = firebasestorage.googleapis.com, port = 40952. Error thrown Instance of 'uda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: SocketException: Connection timed out (OS Error: Connection timed out, errno = 110), address = firebasestorage.googleapis.com, port = 40952. Error thrown Instance of 'uda'.

Hi @deepak786, these exceptions all seem like they might be issues that the user is experiencing with connectivity. I'm not certain there's anything that we can do about it from our end. A similar issue was reported in the firebase repo and it seems to have come to the same conclusion.
See https://github.com/firebase/flutterfire/issues/6508#issuecomment-872072295.
Unfortunately, I don't think there's much we can do about network issues your users might be facing.
Closing from here.
Thank you

another exceptions:
Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
HttpException: Invalid statusCode: 503, uri = https://firebasestorage.googleapis.com/v0/b/agenda-boa-test.appspot.com/o/content%20feed%20test.jpg?alt=media&token=999a7d13-dfcd-477b-b44e-e307cfc4bdcb. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: HttpException: Invalid statusCode: 503, uri = https://firebasestorage.googleapis.com/v0/b/agenda-boa-test.appspot.com/o/content%20feed%20test.jpg?alt=media&token=999a7d13-dfcd-477b-b44e-e307cfc4bdcb. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
SocketException: No route to host (OS Error: No route to host, errno = 113), address = firebasestorage.googleapis.com, port = 48077. Error thrown Instance of 'oda'.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: SocketException: No route to host (OS Error: No route to host, errno = 113), address = firebasestorage.googleapis.com, port = 48077. Error thrown Instance of 'oda'.

@danagbemava-nc and FYI, there was no such issue in the native Android version. So there is something the Flutter is causing these exceptions.

Hi @deepak786, kindly report this over on the CachedNetworkImage repo, I just took a look at the source code, and it looks like there are some dependencies it has to go through before it gets to the Image widget that flutter uses. Any of them could be a point of failure and will need to be investigated on their end.
Thank you


can pocketbase integrate with arduino ?

if yes, can i know how to setup that integration.
if no, can i request that integration as features?

When using the cgo-free port (aka. CGO_ENABLED=0), PocketBase can compile only on the following platforms:
darwin	amd64   3.41.2
darwin	arm64   3.41.2
freebsd	amd64   3.41.2
freebsd	arm64   3.41.2
linux	386     3.41.2
linux	amd64   3.41.2
linux	arm     3.41.2
linux	arm64   3.41.2
linux	ppc64le 3.41.2
linux	riscv64 3.41.2
linux	s390x   3.41.2
windows	amd64   3.41.2
windows	arm64   3.41.2

When using cgo (CGO_ENABLED=1) technically it can compile to any Go supported environment - https://go.dev/doc/install/source#environment.
For Arduino - I guess it depends what hardware you have but in general I'm not sure if that will be possible as you'll have to probably use TinyGo, which doesn't support several of the packages that we rely on - https://tinygo.org/docs/reference/lang-support/stdlib/#nethttp.
This is out of the scope of the project for now, but user contribution to the documentation are welcomed.


Finding Label Names

I see there is a list of supported label names, but where do I find on the actual label itself what it is?  The only thing i see is dk-2251

see https://github.com/MenelicSoftware/cordova-plugin-brother-label-printer#interface-reference
Its W62RB

see https://github.com/MenelicSoftware/cordova-plugin-brother-label-printer#interface-reference Its W62RB

How do I know that though?

https://support.brother.co.jp/j/s/support/html/mobilesdk/reference/android/labelinfo.html
On the box, it says 62mm and red/black

Closing as issues seems to be resolved


MethodCaptor cannot capture methods with default visibility

When I try to use MethodCaptor for a non-final method with default visibility (i.e., not private), then getCapturedMethod asserts with the message "Method could not be captured. This can happen when no method was invoked or the method is private or final."
Tested with version 2.8.0.

Unfortunately we currently cannot capture methods with default visibility. I’ve improved the exception message in dcfcfa0.


Allow carrying certain items in an inventory

What happens if two objects created in different rooms with the same name get together? Maybe movable items should have names different to any other item, movable or not.

I've been thinking more about this, and I've reached some ideas:
About item name uniqueness

Object names doesn't necessarily have to be unique in a room.
If they are more than one item with the same name in a room, they don't have to be equal. It just means that the players can't distinguish them right away, which may be interesting in some cases.
In the case above, access to one of those items may be done at random. This way interesting mechanics could be implemented, specially with the use of custom verbs.
Alternatively, the "first" of those objects may be the one accessed.
Alternatively, players may have the ability to choose what of those equally named items they want to interact with, like:

User: look door
Server: There are more than one door here. Select the one you want to look at:
1. door
2. door

In the case above, each door must maintain it's position so users can know which is each one.
If allowing multiple items with the same name in a room, each item should have a unique way of identifying itself, like room aliases.
In that "select the item you want" case every verb that target an item would be interactive in the case of duplicated item names, which will complicate a lot the creation of custom verbs.

Forcing name uniqueness

This would be the simplest of solutions.
When creating a takable item, it's name must be different from that of any other item in the world, takable or not.

About inventory management:

For the user, items in his inventory will be treated just as items present in the room.
If duplicated item names are allowed, there must be a way of distinguishing between the item present in the room and the item you have with you.

Items you can or can't carry

Users won't be able to take all items with them.
"Takable" items should always be listed, because:

Obvious items should appear in the description on the room. And once the item is taken, the description will describe an item that isn't there.
The same stands for hidden items, since users find them from room's or other items' descriptions.

Because of this, "Takable" can simply be another entry in the visibility list, when choosing a visibility at the item creation process.
For the user, understanding that they can't carry items not present in the "You see" list is a good way of mitigating the "Hey! Why I can't carry that with me? NOSENSE!" issue.

This is the design that I have chosen, with the things that have to be implemented:

[ ] Add "inventory" field in entities.User.
[ ] New possible value for an item's visibility: "Takable".
[ ] Give the option to create a item with "Takable" visibility from the craft verb. Force name uniqueness as in "Forcing name uniqueness" in the previous comment.
[ ] Give the option to change an item's visibility to "Takable" from the edit item verb. Also force name uniqueness.
[ ] Implement "take" verb to take items to the user's inventory. It should only work for items in the current room (not your inventory!)
[ ] Implement "drop" verb to leave in the room items that are in your inventory. It should only work for items in your inventory.
[ ] Implement "inventory" verb to list the items that you have in your inventory.
[ ] Change the "look" verb so that you can also look to items in your inventory.
[ ] Allow using custom verbs of items in your inventory.

Other verbs may affect items in your inventory, like deleteitem and edititem. But since this verbs are used during world creation and not during usual gameplay, we won't implement the change on them for now.


Allowing for "fixing" data

During the mid-year meeting there were some concerns raised about the ability to correct for bad offsets. Our current coverage shape approach would require the geospatial translation operation to move the shape (laterally or along-track) based on the heading. While possible, this is complex. This might we more easily solvable by including the section center latitude and longitude as representation. This still does NOT require the offsets to be tracked/preserved since the point has been resolved to the section center.

My initial reaction is that this is some of the same pushback that we all felt upon contemplating changing the model away from points and offsets.  We have historic frames of reference, and it is uncomfortable to think that we are losing control over the data.   Looking at it from our principle that ADAPT is the transfer data from one party to another, there is nothing implicit in that specifying that ADAPT also contain all of the necessary antecedents so that data can be reconstructed from first principles.
In this case, if a consumer suspects that offsets are wrong, then they should request the source data from the provider in ISOXML and from there build their own polygons.


Provide more examples for pkg_rpm()

This PR does three things:

moves the existing rpm example into a subdirectory to make the examples easier to collect
adds examples using the system rpmbuild (bzlmod and non-bzlmod)
adds an example that uses pure pkg_rpm() with no specfile

i wlll look when i get back from vacation
On Sat, Feb 24, 2024 at 11:32 AM Chuck Grindel @.***>
wrote:

@.**** approved this pull request.
This looks good to me. I noticed that CI is failing on Windows. @aiuto
https://github.com/aiuto is that a flaky test?
—
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_pkg/pull/823#pullrequestreview-1899519262,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC22ZWLBKMSTA5YBFDTPRODYVIBYRAVCNFSM6AAAAABDWAXBAGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQOJZGUYTSMRWGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

This looks good to me. I noticed that CI is failing on Windows. @aiuto is that a flaky test?

Looks like the failure was in pulling the repo, which I assume to be unrelated to my changes.

Thanks.


SOS! SOS! emergency!emergency! Why can‘t i modify the ap_mac???

I use the command "set ap_mac xx:xx:xx:xx:xx:xx" to modify the esp8266's mac.   And the tool display i have modify the mac.

But!!!But!!!  when i upload the program to esp8266, it still display the old mac!!!

moreover!!   I use my computer to connect the esp8266, and catch the packet ,   the destination mac still the old mac

SOS! Help!

please help me , thank you !
My we-chat:<PHONE_NUMBER>6
My phone :<PHONE_NUMBER>6
My e-mail<EMAIL_ADDRESS>

Change is only temporary for the wifi_repeater. Other programs will still read the original MAC from ROM.

Oh，thank you very much for your help. I have found the question. I don’t execute the command to save the config. Oh，my god. I am so idiot！


Integrate Chat in the sidepanel

Integrate LiveKit chat in the custom Side Panel

Few comments, after a quick auto review. In the next PR I should fix :

Wrap the current text area into a component that states it's an auto-resize TextArea
Extract CSS magic value in global CSS variables for consistent layout.
Support newline in message formatter.
Set up chat notifications.


Add support to flash external flash  (IDFGH-4513)

This is to keep track the future enhancement request that was asked in the esp32 forum.
[https://www.esp32.com/viewtopic.php?f=13&t=18727](Unable to flash FAT FS on External Flash)
Problem statement:
Not able to preprogram external flash with predefined content. Flashing external spi flash that was supported by espressif using similar way like internal flashing using mkspiffs and esptool or any equivalent approach to provide such functionality.
This could be added in the road map to be deliver in Q1 2021.

@tsctrl thanks for posting this feature request. One part (generating FATFS images on host) is tracked in #5785. The other part (flashing something to external flash) is already possible with esptool.py, by specifying --spi-connection argument. We will consider how and whether to integrate this part into idf.py.

It will be a nice feature to save data directly in an external SPI flash during bootloading?
I would like to save graphic elements, e.g. bitmaps and fonts, in a SPIFFS partition in an external SPI flash.
How can I save the data directly in the external flash at flashing or bootloading?
Comparable to a partition in main flash, which I can define in partitions.csv.
Is of course also interesting for a FAT file system


Are there DB changes? like the Owner column?
it seems only chart pages are affected.

No DB changes.  This is a no-op, but it indicates a memory leak in your application.

I just logged in from my phone and it’s working
so I guess it’s from the local storage
I’ll confirm when I get back home

Just to add onto this, i got the same client side error trying to set a default date range in the settings, local storage had it set to undefined no matter which value i selected

Facing the same issue,
When the All Time value is set from the Settings page, then it crashed because the value is set as undefined

yes, confirmed, clearing the local storage fixed it for me

.

Just to add onto this, i got the same client side error trying to set a default date range in the settings, local storage had it set to undefined no matter which value i selected

Same for me, reproduced it in different browsers.

Still happen using dev branch

Fixed in v1.26.0.

Still having the same problem with v1.26.

Certainly so...
Changing 'Default date range' in Profile settings results in 'umami.date-range:undefined'

Same here. Was able to reproduce this. Whenever I change the "default date range" the local storage entry comes back. (v1.26)


MacOS wine: NeutralResourcesLanguageAttribute specifies an invalid culture name "en"

A user is reporting this when trying to run a Windows EXE that uses PromptPlus, via wine on MacOS:

Unhandled exception. System.TypeInitializationException: The type initializer for 'PPlus.PromptPlus' threw an exception
System.ArgumentException: The NeutralResourcesLanguageAttribute on the assembly 'PromptPlus, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' specifies an invalid culture name "en"

Some more info on this-
Here's the full output of the crash in Wine. I've tried every dotnet winetrick available to see if maybe there's a specific version I needed, but nothing worked. Even manually installed the dotnet sdk to see if that would work, but no dice there either. No clue why this is fully incompatible.


Request data input validation improvements

In the case from the screenshot below, the adapter is not properly handling the undefined field.
Instead, an uncaught JavaScript error occurs.
Input data

Result

Expected behaviour - adapter should abort (with a helpful message, indicating the source attribute) whenever an attribute is undefined

Potentially links #740


kSysLogLoggerId defined but not used

Hi,
This PR follows #620 and https://github.com/amrayn/easyloggingpp/commit/b96d4895fb3dee44be16d5ab9dd98fcfee49bd30, and fixes the following warning :
‘el::base::consts::kSysLogLoggerId’ defined but not used [-Wunused-variable]
783 static const char* kSysLogLoggerId                         =      "syslog";

It then closes #742.
Thank you 👍

@abumusamq do you think we could merge this tiny patch please ?
Thank you very much 👍

Thank you for the change, all changes must go to develop branch. could you pleas change that?

Thank you for your feedback @abumusamq, I then just moved to develop branch 👍


fix:CI Error: Resource not accessible by integration

Describe what this PR does / why we need it
fix:CI Error: Resource not accessible by integration
Does this pull request fix one issue?

#2031
Describe how you did it
add statuses: write permission
Describe how to verify it
Special notes for reviews

Codecov Report
Base: 18.34% // Head: 18.34% // No change to project coverage :thumbsup:

Coverage data is based on head (a200d0f) compared to base (462034d).
Patch has no changes to coverable lines.

: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
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2034   +/-   ##
=======================================
  Coverage   18.34%   18.34%
=======================================
  Files         101      101
  Lines        9222     9222
=======================================
  Hits         1692     1692
  Misses       7299     7299
  Partials      231      231

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


iOS background notification not working with -env.uglify build option

Which platform(s) does your issue occur on?
iOS only
Any iOS version(i tested on 11.0.3)
iPhone 6( also reproducible in any iOS device)
Please, provide the following version numbers that your issue occurs with:
$ tns --version
3.5.0-2017-12-20-10289
tns-core-module - version 3.4.0
{
  "description": "NativeScript Application",
  "license": "SEE LICENSE IN <your-license-filename>",
  "readme": "NativeScript Application",
  "repository": "<fill-your-repository-here>",
  "nativescript": {
    "id": "com.x.y.z",
    "tns-ios": {
      "version": "3.5.0-rc-2018-01-08-02"
    },
    "tns-android": {
      "version": "3.5.0-rc-2<IP_ADDRESS>"
    }
  },
  "dependencies": {
    "@angular/animations": "~5.2.0",
    "@angular/common": "~5.2.0",
    "@angular/compiler": "~5.2.0",
    "@angular/core": "~5.2.0",
    "@angular/forms": "~5.2.0",
    "@angular/http": "~5.2.0",
    "@angular/platform-browser": "~5.2.0",
    "@angular/platform-browser-dynamic": "~5.2.0",
    "@angular/router": "~5.2.0",
    "angular2-moment": "^1.7.0",
    "nativescript-angular": "^5.2.0",
    "nativescript-appversion": "^1.4.1",
    "nativescript-pro-ui": "3.3.0",
    "nativescript-theme-core": "~1.0.4",
    "nativescript-toast": "^1.4.6",
    "nativescript-web-image-cache": "^4.2.2",
    "reflect-metadata": "~0.1.8",
    "rxjs": "~5.5.2",
    "tns-core-modules": "3.4.0",
    "tns-platform-declarations": "^3.4.1",
    "zone.js": "~0.8.2"
  },
  "devDependencies": {
    "@angular/compiler-cli": "~5.2.0",
    "@ngtools/webpack": "^1.10.2",
    "babel-traverse": "6.25.0",
    "babel-types": "6.25.0",
    "babylon": "6.17.4",
    "copy-webpack-plugin": "~4.3.0",
    "css-loader": "~0.28.7",
    "extract-text-webpack-plugin": "~3.0.2",
    "lazy": "1.0.11",
    "nativescript-dev-typescript": "~0.6.0",
    "nativescript-dev-webpack": "^0.9.1",
    "nativescript-worker-loader": "~0.8.1",
    "raw-loader": "~0.5.1",
    "resolve-url-loader": "~2.2.1",
    "typescript": "~2.6.2",
    "uglifyjs-webpack-plugin": "~1.1.6",
    "webpack": "~3.10.0",
    "webpack-bundle-analyzer": "^2.9.1",
    "webpack-sources": "~1.1.0"
  }
}

Please, tell us how to recreate the issue in as much detail as possible.
When i build the iOS app with "--env.uglify" options, background notification doesn't work. I am able to receive foreground notification.
(Background Notification doesn't works for the below build with uglify)
tns build ios --release --bundle --env.uglify --env.aot

Same code base if i build without uglify option background notification works as expected
(Background and Foreground Notification works for the below build)
tns build ios --release --bundle  --env.aot

Note: The same code base works fine for Android build with uglify option. So, this is iOS only issue
tns build android --release --bundle --env.uglify --env.aot --env.snapshot

I have the same problem using
tns 3.4.3
tns-core-modules 3.4.1
tns-ios 3.4.1
nativescript-push-notifications 1.1.2

I tried to reproduce your case with the app from the repo but to no avail.
I was using:
tns 3.4.3
tns-core-modules 3.4.1
tns-ios 3.4.0
nativescript-push-notifications 1.1.3 (current version from the repo)
Can you reproduce the issue using the current plugin version and the app in the repo? If it is only reproducible with your app can you isolate and send over a sample app demonstrating it?

Closing due to inactivity.

What's the status on this?


Create the initial data in the database, which should include examples of information about the availability of tickets, details about tickets that have been purchased, user purchase history, and other pertinent entities for testing.

I verified the issue, which should include examples of information about the availability of tickets, details about tickets that have been purchased, user purchase history, and other pertinent entities for testing.
I think it might work and it will be useful for further application creation.

I  have made the following changes
Added scripts to insert sample data into the respective tables.
Populated the ticket availability table with a range of ticket types, prices, and quantities to simulate real-world scenarios.
Created test user accounts and associated purchase history to emulate user interactions.
Included additional entities necessary for testing, such as theaters, showtimes, and event information.

i have gone through th issue .
This is an excellent strategy as populating the database with initial data, including ticket availability, purchased tickets, and user purchase history, greatly facilitates robust testing, ensuring comprehensive evaluation and accurate analysis of system functionalities

By having this data, we can effectively evaluate the functionality, performance, and stability of the application.


chore(CI): Start Redis for tests

@homu r

@homu r+

@homu r+

:pushpin: Commit c3101d0 has been approved by badboy

:zap: Test exempted - status


upgrade api related dependencies to 0.27.1

fix breaking import

wait until controller-runtime next version, atm, is not compatible with k8s.io/apimachinery v0.27.1


Fix for navigation scrolling on small devices.

overflow fix for navigation scrolling on small devices.

The hero we all needed!  Thank you so much for fixing this!

Cheers and thank you again!


Tool functionality when AD passwords are salted

Hello There,
How this tools works when the AD password is salted especially during cross forest password quality test.
Thanks
Manu.

Hi @manulalath , I am not sure which exact command do you have in mind. The Set-SamAccountPasswordHash cmdlet only sets NT hashes, which are definitely not salted. The Set-ADDBAccountPasswordHash cmdlet also sets Kerberos AES keys, including the salt, which is then sent by the KDC to the client, so there is no issue either.

Thanks @MichaelGrafnetter , I indeed use Get-ADReplAccount to test the password quality in cross forest domains. Want to understand cross forest password quality checks works 100% when one of the domain or some case both domain passwords are salted? Appreciate your response.

OK, now I understand the question. The Test-PasswordQuality cmdlet only compares NT hashes, which are NOT salted. So no problem there. Sample code:
$accountsA = Get-ADReplAccount ...
$accountsB = Get-ADReplAccount ...
@($accountsA + $accountsB) | Test-PasswordQuality ...

Make sense, thanks @MichaelGrafnetter


Wrong use of aria-hidden

Describe the bug
Carousel items are marked as aria-hidden=true when not visible. Aria-hidden should only be applied to non-interactive elements.
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-hidden
The attribute causes WCAG errors when using focusable elements (buttons, inputs, links) in carousel items.
To Reproduce
Steps to reproduce the behavior:

Render a carousel with two items, one of them using a focusable element (ie a button)
Click on the non-button item
Copy page html to https://validator.w3.org/#validate_by_input
See error related to
https://accessibilityinsights.io/info-examples/web/aria-hidden-focus/

Expected behavior
No accessibility errors

I second this. During my migration to vue 3, its compatibility mode keeps logging the aria-hidden property's false-value.

I'm also noting that the carousel has a tabindex="0" so it's focusable, but then it does nothing with the focus (like using arrow keys to slide prev and next)