Added support for node-7 and node-8

Resolves #4
Cleans apt cache

I thank you for your contribution but there are issues with this PR that needs to be addressed.
The way you implemented it the repository is splitted in 3. It is not a clean and maintenable solution.
A cleaner way to do this would be to use build arguments to select between the node versions.

Just reverted to a single Dockerfile. Now it builds using a --build-arg
Example:
$ docker build . -t fermiumlabs/latex-docker:node-7 --build-arg node_ver=7

I'm merging, sorry for the delay. Got under the pile of mail.
Davide


[DETECTION] Cannot detect Indonesian language

Notice
I hereby announce that my raw input is not :

Too small content (<=32 characters) as I do know that ANY charset detector heavily depends on content
Encoded in a deprecated/abandoned encoding that is not even supported by my interpreter

Provide the file
A accessible way of retrieving the file concerned. Host it somewhere with untouched encoding.
id.zip
Verbose output
Using the CLI, run normalizer -v ./my-file.txt and past the result in here.
normalizer -v src/sdk/nlp/tests/text/id/10.txt
2022-12-06 15:26:15,581 | INFO | ascii passed initial chaos probing. Mean measured chaos is 8.467000 %
2022-12-06 15:26:15,582 | INFO | ascii should target any language(s) of ['Latin Based']
2022-12-06 15:26:15,586 | INFO | We detected language [('English', 1.0), ('German', 0.9332), ('French', 0.9251)] using ascii
2022-12-06 15:26:15,586 | INFO | ascii is most likely the one. Stopping the process.

Expected encoding
All 40 attached files should be Indonesian as Language, but charset-normalizer returns English
Desktop (please complete the following information):

OS: Mac
Python version: python 3.9
Package version [eg. 2.0.0]: 3.0.1

Additional context
Add any other context about the problem here.

Hi,
Well, it isn't a bug in that case. I choose to disable the language detection when it is about ASCII and return 'English' as default. This was out of performance concerns, as ASCII is often predominant (json, etc..)
If you want to, use directly https://github.com/Ousret/charset_normalizer/blob/9b216b5cbf637f0e2470c24b5942afd9c0a8aa63/charset_normalizer/cd.py#L343
from charset_normalizer.cd import coherence_ratio

I tested your files by adding a single non-ASCII characters in each, it seems to be OK.


[4.2.0][Dependency Upgrade] gson version upgrade

Description
gson version used in carbon-identity-anonimization tool (available in SI 4.2.0 /wso2/tools/) has to be upgraded to 2.8.9.
[1]. https://github.com/wso2/identity-anonymization-tool/blob/master/pom.xml#L312
Affected Component
SI
Version
4.2.0
Related Issues
No response
Suggested Labels
No response

Used in identity-anonymization-tool
anonimization tool has been removed from SI distribution as per https://github.com/wso2/streaming-integrator/pull/29


Enhancement: Ability to upload non-media files in Android

The kbfs browser in the Android app offers the possibility to upload image and video files. It would be nice to have an upload function for files in general, e.g. via the intent ACTION_OPEN_DOCUMENT without restriction to a special mime type.

Just found this as a temporary workaround: https://dxb.keybase.pub/#share-to-kbfs-on-android
The real fix should be a whole lot simpler, right?

I am really surprised that this has yet to be implemented. You'd think it would be been included when the Android KBFS was first introduced, not to mention that it's now almost been a year since this issue was opened.


*.mjs webpack error

Hey there!
When I tried to use v-img using webpack, it said it does not know the extension .mjs. Thats because the package.json points to dist/v-img.mjs. Is that a typo, or should it really be *.mjs? If so, may I ask why?

Hi @BrunnerLivio!
Did you include package with require() but not with es6 import?

I used es6 import
import VueImg from 'v-img';
Vue.use(VueImg);

Hm, it's very strange!
I've just tested it and it works good for me!
I'm so sorry, don't know how to reproduce your error.
Can you please fork the library, change *.mjs to *.js and install library from your github?
You can find how to install npm packages from github here: https://docs.npmjs.com/cli/install
You'll help a lot if tell that this will fix your issue.

@BrunnerLivio gotta get mjs back because setting 'module' to '.js' will add some nodejs stuff to the browser-file when building. Probably your setup was wrong that you got this error. Hope everything will be ok in future.


The test are failing

com.mangopay.core.ApiClientsTest > test_ClientsCreateClient FAILED
com.mangopay.core.ResponseException at ApiClientsTest.java:27
https://travis-ci.org/Mangopay/mangopay2-java-sdk

Yes, this is due to some recent changes in the API and we haven't yet updated the SDK but we'll be doing this soon.
In the meantime, there are no other impacts on the SDK/API :-)

This has since been resolved and all tests are now passing :-)


Unit test for OpenShift down

Need unit tests for #280

Shouldn't this be addressed in the PR? Why the extra issue?

Almost all code in this touches OpenShift cluster.
To test this, it will require setting up OpenShift cluster or mocking its api.
Same situation is with up/down for k8s. We will have to figure out how we will test all this.
We don't want to block PR on that. So we created this separate issue.

@cdrage @kadel, we can close this issue as functional tests are being added for kompose down by @ashetty1


Make it so u can toggle anti vm

I made the file, but I have only a windows 11 which doesn't work, and I don't have a windows 10 only a VM. I just wanna test it

Also I tried it on debug mode and it said  logging into static token 5 times then closed

if ur still looking for a solution, you have to remove some lines of code in protection.py related to vm stuff

Thank you

np!


Android Compose UI

[ ] Create module
[ ] Load data from CalendarPageLoader
[ ] Expose currently displayed month
[ ] Implement core CalendarState
[ ] Animate CalendarPageLoader changes
[ ] Snap scrolling

Repurposed this to track Compose for Android. Multiplatform has a few key issues that make life significantly harder for us


Git: abitlity to filter files in git CHANGES list

It is really nice that now one can select multiple files in CHANGES view of GIT. But it would be really great if one could also filter those files using some search input, for example, I would type /folder/ I in changes view there only files that are in ~/folder.

It'd be really great if something like this does come!! Working on js prohects has me naming a lot of files index.js, only their paths differ, so filtering makes a lot of sense.

#3918


Add support for OpenEmbedded Zeus (Yocto 3.0)

This needs to go into "zeus" branch, I cannot pick it as a base, because it doesn't exist yet.

All merged with milestone 11.


How to utilize the repo to replicate MoE-Mamba

Hello,
Thank you for providing the repo. I am actually a fan of all three of the associated papers, so I really appreciate finding it this time. I've implemented MoT myself in two projects with positive results.
I'd like to replicate some of the work you've done in your most recent paper, MoE-Mamba. However, I'm struggling to figure out how you utilized this repo to perform the experiments as described in the paper. Any information would be useful.
Thank you,
Charles

I'm fumbling around here as well.  I just came from using mamba-chat's implementation of mamba training and am trying to figure out how to integrate this in my workflow.

I am also interested in this.

This is a fun repo to watch.  Looking at https://github.com/llm-random/llm-random/pull/340/commits it still looks like they're working on trying out multiple implementations using MoE with mamba.  I'm guessing this is a WIP and giving a direct implementation could possibly take a wait or diy.  I'm just looking for the entry point into the original mamba model from state spaces.

Is there any solution to replicate the Moe-mamba now? 🤔


Chrome query performance issue with MEDIAN and STDDEV aggregators

Hi, I'm wondering if you are aware of problems with running alasql (aggregation) queries in Chrome, or if maybe there's a way to improve the performance. The query is:
alasql('SELECT count(1) AS ct, min(_date) AS minDate, max(_date) AS maxDate,  min(selectedChem) AS minparam, max(selectedChem) AS maxparam, AVG(selectedChem) AS avgparam, MEDIAN(selectedChem) AS medparam, STDEV( selectedChem) AS sdevparam FROM ? WHERE  selectedChem is not null AND selectedChem != -9999  ORDER BY _date', [ resultSet ]);

The resultSet is an alasql result object with max rows (currently) just under 6000. It's much faster in Firefox - Chrome just crawls. The query that supplies the initial resultSet is not nearly so slow in Chrome as this aggregation query. Any suggestions would be appreciated!

@agerard This is not Chrome issue, but rather AlaSQL realization of MEDIAN and STDEV aggregators. Now AlaSQL recalculate whole MEDIAN for each row. We need to rewrite them. I will see, what we can do.

Thanks so much! We really appreciate this level of responsiveness and will give prominent mention to you guys when this project - an interactive OL3 map of water sampling data - is released (hopefully with improved performance).

@agerard Thank you for request. I rewrote aggregators. Now MEDIAN and other statistical aggregators are fast (by my earlier mistake they took about O(N^2/2), but now only O(N) as it should be).
May I ask you for two things:

Test these aggregators (are they work faster and their results are ok)
What other aggregators will be useful

Looks awesome !
I have updated https://github.com/agershun/alasql/wiki/User-Defined-Functions

:+1:

I saw this in a test
+alasql.aggr.MYMEDIAN = function(v,s,acc){
 +  // Init
 +  if(typeof acc.arr == 'undefined') {
 +    acc.arr = [v];
 +    return v;
 +  // Pass
 +  } else {
 +    acc.arr.push(v);
 +    var p = acc.arr.sort();
 +    return p[(p.length/2)|0];
 +  };
 +};

I was of the impression that the 3rd parameter was only the last value, but I see now that its an object. Is it always an object, or will it be whatever you return from the first call?

This is old version of aggregator. Now we use three parameters:value, accumulator, and flag:
1 - for first line
2 - for second and lines
3 - after all lines
Отправлено с iPhone

17 янв. 2016 г., в 15:59, Mathias Rangel Wulff<EMAIL_ADDRESS>написал(а):
I saw this in a test
+alasql.aggr.MYMEDIAN = function(v,s,acc){

// Init
if(typeof acc.arr == 'undefined') {
acc.arr = [v];
return v;
// Pass
} else {
acc.arr.push(v);
var p = acc.arr.sort();
return p[(p.length/2)|0];
};
+};
I was of the impression that the 3rd parameter was only the last value, but I see now that its an object. Is it always an object, or will it be whatever you return from the first call?

—
Reply to this email directly or view it on GitHub.

But is accumulator the response from last call or is it always an object?

re: solved please test
I will gladly test, just need to clarify if these changes will already be found in http://cdn.jsdelivr.net/alasql/0.2/alasql.min.js or should I download a specific build? Using the cdn link unfortunately I don't see a significant performance difference yet, but have also seen browsers - particularly Chrome - cache scripts despite settings....
Also, should I wait a bit to test? Recent comments suggest ongoing work.

I think the speed improvement is already implemented.

will already be found in http://cdn.jsdelivr.net/alasql/0.2/alasql.min.js or should I download a specific build?

Please download and save the last development version from https://raw.githubusercontent.com/agershun/alasql/develop/dist/alasql.js to test the changes :)

Everything is implemented in develop branch, and will be included in official 0.2.4 at the end of the month. I tested these custom aggregators it with 1000000 records.

Thanks, got the dev version - it does seem faster (MUCH faster in chrome), but now I get
TypeError: s is undefined / s.arr.push(v); / alasql.js (line 10049, col 3)
in firebug and this is breaking subsequent flow.

@agerard Sorry for the bug. Could you answer on questions below to understand the problem:

Is this the problem only STDDEV() or VAR() aggregators, right?
Does this problem occur in  Firefox only or in Chrome also?
Could you show the sample of problematic SQL query?

Unfortunately, I can work on it only tomorrow.

Only stdev - if I take that out it's fine
both
same query as first submitted:
alasql('SELECT count(1) AS ct, min(_date) AS minDate, max(_date) AS maxDate,  min(selectedChem) AS minparam, max(selectedChem) AS maxparam, AVG(selectedChem) AS avgparam, MEDIAN(selectedChem) AS medparam, STDEV( selectedChem) AS sdevparam FROM ? WHERE  selectedChem is not null AND selectedChem != -9999  ORDER BY _date', [ resultSet ]);

resultSet data to which aggregators are being applied looks like:
cond_top	39.18
do_top	7.24
fc_top	22
op_top	0.22
salinity_top	25.54
tc_top	22
tkn_top	1.36

The error is in
// Standard deviation
alasql.aggr.VAR = function(v,s,stage){
	if(stage == 1) {
		return {arr:[v],sum:v};
	} else if(stage == 2) {
		s.arr.push(v);
		s.sum += v;
		return s;
	} else {
		var N = s.arr.length;
		var avg = s.sum / N;
		var std = 0;
		for(var i=0;i<N;i++) {
			std += (s.arr[i]-avg)*(s.arr[i]-avg);
		}
		std = std/(N-1);
		return std;
	}
};
```

The code looks good to me.

Could it be an error caused by mixing AVG, MEDIAN and STDEV in the same request?

Unfortunately, I cannot test it now.Could you replace STDEV() with SQRT(VAR(...))?

no, it doesn'ts with SQRT(VAR( ... either.
s is defined the first time through the stage 2 loop, as with STDEV, and s remains undefined the second time through, but once the exception has occurred the watched value of s changes from undefined to "((((typeof p['default']['do_top']==='undefined') === (typeof !(undefined)==='undefined')))&&(((p['default']['do_top'])!=((-(9999))))))"
if that helps....

Also,
alasql('SELECT  STDEV('eb_top ') AS sdevparam FROM ? WHERE eb_top is not null AND eb_top != -9999 ORDER BY _date', [ resultSet ]);
fails as a standalone query with the same resultSet (and same error)

Worst case: I can not reproduce the problem.
Here is my test code:
    var resultSet = [
      {_date:new Date("01.01.2016"), selectedChem:1},
      {_date:new Date("01.01.2015"), selectedChem:2},
      {_date:new Date("01.10.2015"), selectedChem:3},
      {_date:new Date("10.10.2015"), selectedChem:4},
    ];
    var res = alasql('SELECT count(1) AS ct, min(_date) AS minDate, max(_date) AS maxDate, min(selectedChem) AS minparam, max(selectedChem) AS maxparam, AVG(selectedChem) AS avgparam, MEDIAN(selectedChem) AS medparam, STDEV(selectedChem) AS sdevparam FROM ? WHERE selectedChem is not null AND selectedChem != -9999 ORDER BY _date', [ resultSet ]);

and the result:
[ { ct: 4,
    minDate:<PHONE_NUMBER>000,
    maxDate:<PHONE_NUMBER>000,
    minparam: 1,
    maxparam: 4,
    avgparam: 2.5,
    medparam: 3,
    sdevparam: 1.2909944487358056 } ]

Here is jsFiddle with latest version of AlaSQL. Could you say, what should I change in the example to highlight the bug?

alasql('SELECT STDEV('eb_top ') AS sdevparam FROM ? WHERE eb_top is not null AND eb_top != -9999 ORDER BY _date', [ resultSet ]);

Fails because the first string is SELECT STDEV( followed by an attempt to place the javascript variable eb_top but a + was expected. See http://jsfiddle.net/8smL2j3q/3/
If you replace  'eb_top ' with eb_top you get no error: See http://jsfiddle.net/8smL2j3q/4/

:+1:

@mathiasrw - the single quotes in the last query were just an artifact of rendering the variable from my working code - when I retested your query locally in my firebug console it still didn't work. But the good news is that after downloading alasql.js from the jsfiddle (unfortunately overwrote the previous dev download so can't compare what might have gone wrong) it now works with my code! So whether I got a transitional version, something went wrong with the earlier download, or browser held on to old code somehow, it's all good now! Thanks!

Hooray! Thank you for the issue, it helped to improve AlaSQL!

So awesome to hear - always good with a well well documented issue :+1:


Test io_uring_prep_sendto

Need to create basic test for io_uring_prep_sendto

Even though adding such a test would be welcome, but I don't think it's strictly required. It's a simple wrapper, and passing an address is exercised at least in send-zerocopy.c  for normal and as well zerocopy modes.
https://github.com/axboe/liburing/blob/master/test/send-zerocopy.c#L375

Just a basic test should do, nothing fancy, to make sure all the functions are covered with test. I know its not very important but you never know when things will be effected, even a simple type change or new attribute added could effect each other.

It's already being implicitly tested. I have a feeling you're asking for this to duplicate it in your framework? If so, please just go ahead and write it and send a PR. We're getting inundated with "please add this or that" these days, and it's not scaleable. If some tests or documentation is missing, please feel free to write them and submit them.

https://github.com/axboe/liburing/issues/1090

It took me a while to find all those, don't you use something like coverage in C? It normally tells you functions that are not covered in test, figured it would be good to let you guys know.
I would have added all those into 1 issue, but I think you mentioned somewhere to create each post per issue.

I have a feeling you're asking for this to duplicate it in your framework?

No, I don't rewrite the test since it wouldn't make much sense to redo what you have already done. I was trying to do that with futex since there was no documentation, to figure out what io_uring was doing. I mainly test to see if wrapper is working and most of the time trying to figure out how to make C function work best with Cython and Python.


oidc-client is immediately raising the access token expired and access token expiring events

This is my log output, and it happens nearly instantaneously.  I'm not having any issues yet (I don't yet rely on these events), and maybe this is by design and I'm not understanding something.

Please disregard.  I was behind on my version.


Tanks and hoses decay over time

Are tanks and hoses supposed to decay? When a tank is freshly placed it can be picked up using a pick. Over time (maybe a game restart) the tank breaks and disappears and water can not be placed into or extracted from a tank. The same goes for hoses.
Version 0.4.0 mc 1.12.2.

That's extremely weird. I didn't code such a mechanism in the mod in any case

 shows cannot fill tank and what breaks. Does this help a bit?

If it helps, I am able to reproduce this when playing single player but not on a server. In single player, when I leave the chunk and come back, it seems that the entire network of hoses and tanks stops working and drops nothing when broken.
I'm playing this pack: https://minecraft.curseforge.com/projects/real-tech (as is duncanwebb). I haven't tried reproducing it without other mods yet.


Anythingllm does not start in the browser on localhost:3001

Hello dear friends
I am installing your wonderful solution AnythingLLM on my intel 7 laptop with 16 RAM formatted and I have installed:
New linux mint virginia,
python 3.12.4,
node 22.6.0,
I can see their versions in the terminal
I have followed the steps for installing docker engine and successfully executed the command sudo docker run hello-world.
The docker pull mintplexlabs/anythingllm has been completed
and when I send the following command package I get the last line which looks like an API KEY:
root@nelson-NL40-50ZU:/home/nelson# export STORAGE_LOCATION=$HOME/anythingllm &&
mkdir -p $STORAGE_LOCATION &&
touch "$STORAGE_LOCATION/.env" &&
docker run -d -p 3001:3001
--cap-add SYS_ADMIN
-v ${STORAGE_LOCATION}:/app/server/storage
-v ${STORAGE_LOCATION}/.env:/app/server/.env
-e STORAGE_DIR="/app/server/storage"
mintplexlabs/anythingllm eda648b2e33c4954625ca38fa74648c0a0b20c7a5b23cee0c2fc9c9c1b64feb5 In the firefox browser I have NO PROXY selected in Network Settings. I try to open it at http://localhost:3001/ but it says Unable to connect • Firefox can't establish a connection to the server at localhost:3001.
• The site could be temporarily unavailable or too busy. Try again in a few moments.
• If you are unable to load any pages, check your computer’s network connection.
• If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.
There should not be any problems with the wifi provider because with other applications everything works fine
What is my mistake? Please, help me.

Are you able to pull the logs for the container? An Intel 7 is pretty old, but there is no telling what instruction set it has without the exact model of the CPU.
Possibly relevant: https://github.com/Mintplex-Labs/anything-llm/issues/1331
Also this is the documentation repo - I have said this already the last time you post this issue.
The main anythingllm repo is https://github.com/Mintplex-Labs/anything-llm


Attempting to install an invalid export template file does not display error messages

Tested versions
4.4.dev [1435247de] and 4.3.stable
System information
Godot v4.4.dev (1435247de) - macOS 14.7.0 - Multi-window, 1 monitor - Metal (Mobile) - integrated Apple M2 (Apple8) - Apple M2 (8 threads)
Issue description
Trying to install an invalid export template file ~(very easy to do, how on earth do I properly install custom export templates)~ prints a DisplayServer warning and opens a window titled "Warning!" with nothing in it. No error message for the invalid export template file is printed or displayed.
scene/main/window.cpp:735 - Entering a window while a window is hovered should never happen in DisplayServer.

~For some reason in 4.3.stable it doesn't print the console warning but still has the issue (except the window is smaller).~ Never mind, this is just because of dev_build=no, oops. The warning could be an entirely separate issue.
Steps to reproduce

Open Editor > Manage Export Templates
Pick Install from File
Select anything that's not a valid export template file

Minimal reproduction project (MRP)
N/A, editor issue

Duplicate https://github.com/godotengine/godot/issues/85862

Thanks, I don't know why I didn't see that


"Cæsáreæ Philíppi" corrected to "Cæsaréæ Philíppi"

Dear Benjamin,
I have just pushed many corrections in the Vulgate text, including yours (commit 4861c0, feb. 28). Please pull, and if everything is fine for your, I close your issue.
Thanks a lot!
United with you in prayer.
--

Gloire à Dieu +
Fr. Romain Marie
Abbaye Saint-Joseph
21150 Flavigny-sur-Ozerain
03 80 96 22 31
http://clairval.com
Services http://services.asj.com (intranet)

On 01-03-2019 20:48:24PM, Benjamin Bloomfield wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/gregorio-project/latin-ecclesiastic-accents/pull/18
-- Commit Summary --

"Cæsáreæ Philíppi" corrected to "Cæsaréæ Philíppi"

-- File Changes --
M corpus/vulgate/vulgate_with_accents.txt (2)

-- Patch Links --
https://github.com/gregorio-project/latin-ecclesiastic-accents/pull/18.patch
https://github.com/gregorio-project/latin-ecclesiastic-accents/pull/18.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/gregorio-project/latin-ecclesiastic-accents/pull/18

Looks good.  Thanks!


1.10.2 crash - ConcurrentModificationException

Occurs on world load while (I assume) iterating the dimensions in the DimensionManager.
Would fix if I had the time to look.
crash-2017-01-16_02.36.00-client.txt

Does this only happen with only LubVulpus and Advanced Rocketry?

I've seen this issue before, I've had it reported and I've run across it myself, however it is nearly impossible to replicate reliably and if the game is restarted it does not appear again in most cases which makes it kinda hard to fix.

I'm fairly sure this patch will fix the issue, will close for now unless something else comes up with 1.0.8


dependabot_alert Event missing in eventTypeMapping

Trying to use this package to parse events, but dependabot_alert is not included.
Ref: https://docs.github.com/en/webhooks-and-events/webhooks/webhook-events-and-payloads#dependabot_alert

Would you like to create a PR, or shall I open this up to other contributors to this repo?

I could do this probably, I had this basically few months back, but at that point it was a new feature and Github didn't update docs, they seem up to date now so I could take a look at this one.

Thank you, @gronsy , it is yours.

Hi @gronsy ! Are you still going to work on it? I could take it on myself.

@nikpivkin hello yes sorry you can take it. I have had pretty dynamic things on job with big version releases coming and didn't manage to take a better look at this as I should. I have some code written, but something weird is happening with my go install so probably will have to reinstall it so you just take it over. If you want I can share what I have written?

@gronsy Hi, thanks. I don't think adding an event will require much change.


Null reference exception on startup when no assets

Started a fresh server up tonight with a fresh WHIP installation (no assets) and the Halcyon region server crashed at startup generating the map tile (presumably when it couldn't fetch an image asset).  This may also be related to the fact that I had Cloud Files disabled on this startup as well. (I haven't investigated yet but I thought I'd make sure this was tracked.)
Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at InWorldz.Data.Assets.Stratus.StratusAssetClient.TryRequestAsset(UUID assetID, IAssetServer server, AssetBase& asset) in C:\DevSL\InWorldz\halcyon\InWorldz\InWorldz.Data.Assets.Stratus\StratusAssetClient.cs:line 237
   at InWorldz.Data.Assets.Stratus.StratusAssetClient.RequestAssetSync(UUID assetID) in C:\DevSL\InWorldz\halcyon\InWorldz\InWorldz.Data.Assets.Stratus\StratusAssetClient.cs:line 221
   at OpenSim.Framework.Communications.Cache.AssetCache.GetAsset(UUID assetID, AssetRequestInfo reqInfo) in C:\DevSL\InWorldz\halcyon\OpenSim\Framework\Communications\Cache\AssetCache.cs:line 267
   at OpenSim.Region.CoreModules.World.WorldMap.TexturedMapTileRenderer.fetchTexture(UUID id) in C:\DevSL\InWorldz\halcyon\OpenSim\Region\CoreModules\World\WorldMap\TexturedMapTileRenderer.cs:line 173
   at OpenSim.Region.CoreModules.World.WorldMap.TexturedMapTileRenderer.computeAverageColor(UUID textureID, Color defaultColor) in C:\DevSL\InWorldz\halcyon\OpenSim\Region\CoreModules\World\WorldMap\TexturedMapTileRenderer.cs:line 234
   at OpenSim.Region.CoreModules.World.WorldMap.TexturedMapTileRenderer.TerrainToBitmap(DirectBitmap mapbmp) in C:\DevSL\InWorldz\halcyon\OpenSim\Region\CoreModules\World\WorldMap\TexturedMapTileRenderer.cs:line 288
   at OpenSim.Region.CoreModules.World.WorldMap.MapImageModule.WriteJpeg2000Image() in C:\DevSL\InWorldz\halcyon\OpenSim\Region\CoreModules\World\WorldMap\MapImageModule.cs:line 122
   at OpenSim.Region.Framework.Scenes.Scene.CreateTerrainTexture(Boolean temporary) in C:\DevSL\InWorldz\halcyon\OpenSim\Region\Framework\Scenes\Scene.cs:line 1932
   at OpenSim.OpenSimBase.CreateRegion(RegionInfo regionInfo, Boolean portadd_flag, Boolean do_post_init, IScene& mscene) in C:\DevSL\InWorldz\halcyon\OpenSim\Base\OpenSimBase.cs:line 474
   at OpenSim.OpenSimBase.CreateRegion(RegionInfo regionInfo, Boolean portadd_flag, IScene& scene) in C:\DevSL\InWorldz\halcyon\OpenSim\Base\OpenSimBase.cs:line 395
   at OpenSim.ApplicationPlugins.LoadRegions.LoadRegionsPlugin.PostInitialize() in C:\DevSL\InWorldz\halcyon\OpenSim\ApplicationPlugins\LoadRegions\LoadRegionsPlugin.cs:line 119
   at OpenSim.OpenSimBase.StartupSpecific() in C:\DevSL\InWorldz\halcyon\OpenSim\Base\OpenSimBase.cs:line 211
   at OpenSim.OpenSim.StartupSpecific() in C:\DevSL\InWorldz\halcyon\OpenSim\Base\OpenSim.cs:line 163
   at OpenSim.Framework.Servers.BaseOpenSimServer.Startup() in C:\DevSL\InWorldz\halcyon\OpenSim\Framework\Servers\BaseOpenSimServer.cs:line 300
   at OpenSim.Application.Main(String[] args) in C:\DevSL\InWorldz\halcyon\InWorldz\Halcyon\Application.cs:line 153

The only line that could have NRE'd in there means that somehow the asset server was disabled.  Seeing as you mentioned disabling CF, dis you remember to leave LegacySupport true? Having both LegacySupport and CF being false means no asset server at all.

LegacySupport was true.  The config wasn't the problem, it was just a logic problem in the code where it always fell back to the second server if the asset wasn't found (see simple code in image below) even if the second server was null.  I needed this resolved (blocking problem) so I committed a fix (but oops in the master branch).  So it's resolved now in master.  I'm not sure why this wasn't more common, since it happens if Cloud Files is not in use, which is probably true on almost every other Halcyon server.
[InWorldz.Data.Assets.Stratus]
 CFSupport = false
 LegacySupport = true
 WriteTarget = "whip"
 WhipURL = "whip://password@host:32700"

This was resolved by commit 8b0afefc578a25cd80311bedae1c1d72d6ec965e


Collapse FHIR

Collapses stratified FHIR to only deal with Expr and not RefineArg

@nilehmann, this almost works with one small bug that I cannot seem to track down:
test [ui] pos/abstract_refinements/test03.rs ... FAILED
normalized stderr:
error: internal compiler error: crates/flux-infer/src/fixpoint_encoding.rs:1197:17: unexpected expr `VecBorrows { λi. 0 ≤ i ∧ i < len.0 }` in function position
  --> $DIR/loop_abstract_refinement.rs:45:1
   |
45 | fn foo(vec: &mut RVec<Particle>) {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

thread 'rustc' panicked at crates/flux-infer/src/fixpoint_encoding.rs:1197:17:
Box<dyn Any>
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: aborting due to 1 previous error


aws-sam-cli: 1.115.0 -> 1.116.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for aws-sam-cli is: CLI tool for local development and testing of Serverless applications
meta.homepage for aws-sam-cli is: https://github.com/aws/aws-sam-cli
meta.changelog for aws-sam-cli is: https://github.com/aws/aws-sam-cli/releases/tag/v1.116.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.116.0 with grep in /nix/store/584y3hrikz6lnr6v9nz1hbpg3ahi777s-aws-sam-cli-1.116.0
found 1.116.0 in filename of file in /nix/store/584y3hrikz6lnr6v9nz1hbpg3ahi777s-aws-sam-cli-1.116.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

aws-sam-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/584y3hrikz6lnr6v9nz1hbpg3ahi777s-aws-sam-cli-1.116.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/f39e882e4ccfaa7797f24c15ddc51ea9296fbf86#aws-sam-cli

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/584y3hrikz6lnr6v9nz1hbpg3ahi777s-aws-sam-cli-1.116.0
ls -la /nix/store/584y3hrikz6lnr6v9nz1hbpg3ahi777s-aws-sam-cli-1.116.0/bin

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

2 packages built:

aws-sam-cli
aws-sam-cli.dist

Maintainer pings
cc @lo1tuma @anthonyroussel for testing.

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

2 packages built:

aws-sam-cli
aws-sam-cli.dist


Awake feature disables Windows "Lock PC on Screensaver" security setting

We can't deploy PowerToys in our company because of the Awake feature. It disables the Screensaver and thus overrides the "Password protect the screen saver" GPO. Inactive PC's with the awake feature will never lock and therefor not comply with security policies.
If it was possible to disable/enable PowerToys features (perhaps with a GPO) on install, we could still install it.

Duplicate of #12537

See https://github.com/microsoft/PowerToys/issues/12537#issuecomment-888251732 for more details.

@b0bbyB as @franky920920 called out, the discussion on this is already in another issue. Closing this as a dupe.

I saw - that's fine.
The awake developers reasoning that there’s other ways to circumvent enterprise security, so why don’t we just offer it on a silver platter is a shame, but understandable. We can’t offer an IT approved tool/software package that has a built-in feature to circumvent security policies.
I hope you add Enterprise control over the PowerToys features; GPO or Intune Policies. That way we can have the best of both worlds.
Thank you for your time and an awesome tool.


Presets: Separate terms into synonyms and keywords

I recently had a closer look at the data in /data/presets/ and I must say, it's pretty awesome. Such a wealth of information and so well structured, great job guys! I hope this would be used more in other OSM projects. (As a matter of fact, I am currently working on a (Java-)library that should serve as a tags<->names dictionary which will exclusively scrape it's data from here)
So, to the point, I have a suggestion that could improve searchability of the presets even more. Currently, there is the name and there are the terms. I suggest to split up terms into "further names" (synonyms) and keywords.
Advantages I see

search matches with synonyms can get a higher priority than for keywords - possibly just below name and even before suggestions (brand names)
for items for which the search matches a synonym, that synonym could be displayed in the result list instead of the primary translation/most-well-known one (which might, depending on the area, not actually be the most-well-known one). Currently, only that translation is shown (Spielbank is a synonym for Kasino in German):
The current behavior is understandable because iD can't know whether a term in terms is actually a synonym or just a keyword (and a keyword shouldn't be displayed in the result list).

Dealing with current translations
An unproblematic migration in respect to the current translations could work like this: A new translatable field named synonyms is introduced (or name field being made into names) and all translations in terms (perhaps renamed to keywords for clarity) just stay where they are. The behavior does not change. Then, translators can gradually move terms that are actually synonyms into the other field to profit from the features the separation brings.
What do you think?

That would be great step towards improving the searchability of presets. +1

I recently had a closer look at the data in /data/presets/ and I must say, it's pretty awesome. Such a wealth of information and so well structured, great job guys!

@westnordost On behalf of the project, thank you! Our presets are especially great because so many individuals have contributed to them. A new preset makes for an excellent first PR.

I hope this would be used more in other OSM projects. (As a matter of fact, I am currently working on a (Java-)library that should serve as a tags<->names dictionary which will exclusively scrape it's data from here)

Sounds terrific! Be aware that the preset schema can change fairly often to suit the needs of iD.

I suggest to split up terms into "further names" (synonyms) and keywords.

This is an interesting idea. We'll need to think about this more but here are my initial thoughts:

"Synonyms" as you outline them remind me of Wikidata aliases.
I think if a preset showed up with a different label I would assume it was a different preset altogether. There are already confusingly similar presets in iD (e.g. Casino vs. Adult Gaming Center) because OSM tagging is so complex. I'd like for preset names to remain stable in the UI.
We're planning on adding an optional subtitle property to show below the preset name (see #6137). It will also be used for search results and ranking. Perhaps this alone is an okay alternative?
Can you think of any other advantages? I personally find that the presets are already pretty searchable, do you disagree? I want to make sure we have a really compelling reason to do this since it could make a lot of work for translators.

Can you think of any other advantages? I personally find that the presets are already pretty searchable, do you disagree?

I don't disagree, it is pretty well searchable and I am impressed, I just think that it may be improved if this is done.
Perhaps both the advantages I mentioned are more apparent with (at least the) German locale. The majority of terms on this locale are actually synonyms, very few keywords there. At least for me, it felt odd that for the thing I am searching for, the best match is not the text I entered and also not highlighted in any way.
Of course, that the search word actually matches a preset 100% because it is a synonym rather than a keyword could be shown in a different way, like with subtitles as you suggest. (Title:  Subtitle: a.k.a )
Another cumulative idea is to highlight the section of the the matched word that matches the input text (in bold or underlined), so when searching for "Spiel", the results that actually contain the word are highlighted, i.e.

Spielbank
Spielwarengeschäft
etc.
This cumulative idea (small I create a separate ticket?) would work better together with this idea because it would be confusing if the best match is the only match that is not highlighted.

Cool, that sounds great! I have a load of German aliases to dump into Transifex from an earlier attempt to localize primary features :-)
Where does the subtitle come from? taginfo displays a similar description, I think it comes from the wiki. An option also for iD?

Where does the subtitle come from? taginfo displays a similar description, I think it comes from the wiki. An option also for iD?

@westnordost We'll be adding the subtitle as a preset property native to iD in #6137. The wiki descriptions are unsuitable for iD since:

They require API calls to get them so we can't really display them instantly for every feature in the search results.
The don't all map directly to iD presets (which can be defined by multiple tags).
Many are longer and more detailed than we need here.
They are of varying quality.
They may not reflect how iD interprets a feature.

By the way, terms is currently a comma-separated string, I think this is for Transifex-reasons. So aliases should probably follow the same scheme. Except of course, for the final presets.json this could already be converted for consumption.

Also, maybe it would be better to not add a aliases translation key, but instead rename name to names. The first item in that list would then be the the one that is shown as the name, the others are the aliases.
Why?
As due to the nature of Transifex or any/most other translation portals, it encourages users to add something to every translation key because otherwise it is flagged as a missing translation.
So even if there is no real alias for a map feature, translators are pushed towards maybe even adding aliases that do not fit 100%. This is already a problem with the terms key. In the German translation, I often see the workaround that the name is copied into the terms field to just not have an empty translation.
This would be avoided when using the names field.
Additionally, what should be the primary name (instead of just an alias) could become the topic of smaller edit wars after the introduction of aliases. When the name+aliases are kept in one translation key, this could be defused a bit because then it just becomes a matter of rearranging the names (by importance/common-ness). Otherwise, it would involve deleting and replacing the name and hopefully adding that replaced name to the alias key in the same breath.

Also, maybe it would be better to not add a aliases translation key, but instead rename name to names. The first item in that list would then be the the one that is shown as the name, the others are the aliases.

An interesting idea, but I prefer keeping the name and the aliases separate. Using names would complicate a lot of the code in iD, plus it would entail more much work for translators compared to a purely additive change. The displayed completion percentage of a translation is ultimately arbitrary, but if it's really an issue we can consider a smarter solution like allowing an explicit null translation that iD will ignore.

Using names would complicate a lot of the code in iD, plus it would entail more much work for translators compared to a purely additive change.

iD’s build process already has to transform the strings it exports from Transifex into a suitable format at runtime, so could that transformation also partition “name” into “name” and “aliases”? (Leaving it as “name” despite the possibility of multiple lines of translations would avoid makework for translators.) The main challenge is communicating to translators that multiple names are allowed, but Transifex does show any instructions in comments in a prominent position.

The displayed completion percentage of a translation is ultimately arbitrary, but if it's really an issue we can consider a smarter solution like allowing an explicit "null" translation that iD will ignore.

The percentage may seem like a trifle from the perspective of the project’s developers, but it’s pretty much the only thing that motivates many translators. Seeing the percentage get stuck due to untranslatable strings can be discouraging.

The percentage may seem like a trifle from the perspective of the project’s developers, but it’s pretty much the only thing that motivates many translators. Seeing the percentage get stuck due to untranslatable strings can be discouraging.

@1ec5 Thanks for noting this, it's useful to hear. We'll come up with some way to allow 100% translation without encouraging bad translations.

I am now working on implementing this

iD's presets have been spun out to id-tagging-schema, so it seems time to revisit this feature.
I like the idea of allowing multiple values in the name field, and then putting everything after the first value into a separate aliases property, since it makes aliases optional for translators. Example: "name": "Indoor Corridor;Hallway;Passageway"

To summarize (@quincylvania to confirm): Idea is to have aliases and search terms for presets where aliases would be 'stronger' suggestion.

This was implemented on preset-schema level and several aliases have been added to id-tagging-schema.
What is left to do is to have iD handle 'aliases' and prioritize them in the search suggestions.

This feature is very good and a lot has already been done, I am dropping the 2.20 milestone in order to speed-up next release, however this change should go in the upcoming cycle.

Thank you for the update, Milos! I wasn't monitoring the state of the id presets (because obviously it was in hiatus) but when a new version of the id tagging presets are released that includes these and there is reasonable adoption by translators, I should revisit my https://github.com/westnordost/osmfeatures library to include searching by aliases as well.
It seems however that the differentiation between aliases and terms is not already pushed to Transifex, which means that translators can not yet start adding terms/aliases to the different presets. Before the version of iD in which this is introduced is released, it would be good to give translators a generous head start to supply the translations for this.

I see, thanks for this info. Plan is to get some work done on id-tagging-schema soon and I think alias translation should be included.

Part of this ticket would be to use the alias also in the UI, see e.g. https://github.com/openstreetmap/iD/issues/6139#issuecomment-479770690 and the following post by Quincy.


docs: fix demo site

Gets the demo site building properly

@ascorbic I set up a site with a base path for the other demo build. for this one you might need to make another site in the app and give it this base path


Demo and API doc not consistent for unmountOnExit

v 1.1 Documentation issue

demo and api not consistent for unmountOnExit for Collapse component
By looking in the code it seems like unmountOnExit property doesn't exist on Collapse which would indicate that the problem is the demo docs/src/pages/demos/cards/RecipeReviewCard.js which has the property  set:

<Collapse in={this.state.expanded} timeout="auto" unmountOnExit>

[X] This is a v1.x issue (v0.x is no longer maintained).
[X] I have searched the issues of this repository and believe that this is not a duplicate.

@fondberg I believe you are referring to this line:
https://github.com/mui-org/material-ui/blob/03ce383d1c7c10f59dd64cd31ceea16806a9dfb7/docs/src/pages/demos/cards/RecipeReviewCard.js#L102
Yes, the unmountOnExit is valid. I agree that the origin of such property can be obscure. Once you realise the inheritance pattern, that should be fine :)

The properties of the Transition component, from react-transition-group, are also available.


TabView seems to ignore state if keyboard was opened

Bug
TabView seems to be ignoring state changes - or tab taps - when some input in the scene receives focus
Environment info
React native info output:
React Native Environment Info:
    System:
      OS: Linux 5.0 Fedora 29 (Workstation Edition) 29 (Workstation Edition)
      CPU: (4) x64 Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz
      Memory: 524.91 MB / 7.66 GB
      Shell: 5.6.2 - /bin/zsh
    Binaries:
      Node: 11.12.0 - /tmp/fnm-shell-4858630/bin/node
      Yarn: 1.15.2 - /tmp/fnm-shell-4858630/bin/yarn
      npm: 6.9.0 - /tmp/fnm-shell-4858630/bin/npm
    SDKs:
      Android SDK:
        API Levels: 25, 27, 28
        Build Tools: 27.0.3, 28.0.3
        System Images: android-28 | Google Play Intel x86 Atom
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.2 => 0.59.2
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native: 0.59.2

"react-native-gesture-handler": "1.1.0",
"react-native-reanimated": "1.0.1",
"react-native-tab-view": "2.6.1",

Steps To Reproduce
The code below may help you to reproduce this, I'm not sure if this is caused by the use of react hooks, but when I click on any tab after a input focus, the state is set correctly (console.log shows that the state is set) but the tab view doesn't show the scene for the current state.
If I swipe to another scene and then click on any tab everything works fine again, if I focus on any input, the problem appears again
Describe what you expected to happen:

I type something in any input on any scene, then click on any tab
The tab view shows the correct scene based on the current state

Reproducible sample code
Running without debugger in a real device (One plus 5T):
import React, { useState } from 'react'
import { TabView } from 'react-native-tab-view'
import { Dimensions, Text, TextInput, View } from 'react-native'

export default () => {
    const [currentIndex, setCurrentIndex] = useState(0)
    const routes = [
        { key: 'dataTab', title: 'Dados' },
        { key: 'followUpTab', title: 'Follow up' }
    ]

    const renderScene = ({ route }) => {
        return (
            <View style={ { flex: 1 } }>
                <Text> { route.key } </Text>
                <TextInput />
            </View>
        )
    }

    return (
        <TabView
            navigationState={ {
                index: currentIndex,
                routes
            } }
            renderScene={ renderScene }
            onIndexChange={ setCurrentIndex }
            initialLayout={ { width: Dimensions.get('window').width } }
        />
    )
}

https://snack.expo.io/@satya164/4bf536


Compare VS platform name case insensitively

Fixes https://github.com/corrosion-rs/corrosion/issues/378 via the proposed fix.

The exact command that VSCode was trying to run (and I have been trying to run from powershell as well) is cmake -G "Visual Studio 17 2022" -T host=x64 -A win32 which does seem to compile properly with this patch. I have not tried arm64, but I could install the toolchain and give it a try.

I have not tried arm64, but I could install the toolchain and give it a try.

That would be helpful.
FYI, the CI failure on windows with rust nightly is a known issue and unrelated to your changes.


Fix read statement

Closes #163

We should wait until #196 is merged, because the right parenthesis is also causing issues.


Filetype re-name -> Image type bypass

I've found that someone can easily change the name of their file to an image even if it wasn't an image to begin with (ex. stupiddoc.pdf renamed to stupiddoc.png).  Normally this can be checked by using:
getimagesize($_FILES['Filedata']['tmp_name'])

and checking to see if it yields a result.  If I were going to place this somewhere to check if it is indeed an image, within which method would I place it?
I have some pretty 'smart' members that are able to bypass the profile image type of jpg|gif|png by renaming pdfs.

Actually, I fiddled around a little more and found where to place this code.
Within the has_error method place the following if statement:
if(!getimagesize($uploaded_file)){
	return "The uploaded file doesn't seem to be an image.";
}

This will check the image size of the "file", and if it's not an image will return false and an error message.


Zoom feature break tap zone

Hello
First of all, thanks for this amazing library, it's great!!
I'm using version 0.9.5 without problems. I can change the color of section touched and use it later to do more things. But if I use the master branch, with zoom feature, touched is detected outside section, making it impossible to select the right section. Is there a problem with this branch? When will be available a new release with zoom feature?
Thanks for all

Hi @gosdragon,
Not sure I understood your issue. Could you please provide some example demonstrating this issue with zoom feature?


Regex

Is it possible to use regex to upload/download folders on skicka? I have a series of folders on GDrive that has the same prefix and I want to transfer them.

This is a duplicate of #48.


Lay the foundation for a Swift migration

Summary
Laying the foundation for a Swift migration.
It should be easier to read/write, thus maintain, and new devs are more used to Swift than ObjC.
Is this something you would be interested in?
How did you test this change?
This is more of a PoC at this stage, that hasn't been fully tested
Built on iOS device & simulator and made sure examples worked the same.

Yes, a Swift conversion/migration would be very welcome. We'd have to thoroughly test it on hardware devices as well, obviously. I have merged a few of your other PRs which may have caused the conflict you see.
If you are up for doing it, we very much welcome a Swift migration. Please proceed :)

Thanks @scarlac for the merges! I'll rebase and move forward on the Swift conversion.
Agreed on the test, that will definitely be a big one.
Would you prefer multiple PRs that should be easier to review, or one with everything included?

I think one big one is fine unless it’s more work for you that way.

Sounds good, let's do one 👍

Here we are @scarlac. Swift conversion/rewrite.
I extracted the logic that's unrelated to the actual camera into CameraView (focus, zoom, overlay, ...), which embeds either RealCamera or SimulatorCamera. That way, we can test much more things on the simulator.
The iOS barcode scanner was checking we aren't scanning twice the same value, I replaced it by a throttle configurable with scanThrottleDelay. In some use cases it seems legit for a user to scan twice the same in a row. Could easily be implemented on Android if you are aligned with the idea.
I removed setTorchMode which shouldn't have been exposed to React. It is redundant with the torchMode props. I'll remove it on Android if you are aligned.
I updated AVCaptureStillImageOutput that's deprecated to AVCapturePhotoOutput, and did a lot of things here and there.
I fixed a bunch of small issues here and there. Let me know how I can help further, that's definitely a big one.

Here is a side by side recording of ObjC vs Swift implementation
https://github.com/teslamotors/react-native-camera-kit/assets/11665957/42741597-3c74-4187-a37d-9da8ea3db0a9
(custom ratio overlay color doesn't work on master, which is why it doesn't appear on ObjC)
Perf are very very similar (milliseconds one another, with Objc or Swift randomly being first). I'm still testing thoroughly the feature set.
I found one issue around default focusMode that should be on while not set from React. I'll check all default values.

Excellent, @DavidBertet - I've also been testing it and it generally seems good. I am however removing the CameraScreen component as well as updating the tests to use functional components. I'll commit to your branch as well.
I don't know that there is a use case for the throttled barcode scanner, but I think it's an OK for this PR.
We need a follow up PR that has the ability to toggle that behavior, for example an optional ignoreDuplicateScans={false} and then throttleScans={2000}.
I think it is most likely that people are not interested in scanning the same code twice. From experience, you either want to scan immediately, or scan multiple items, in which case you want to ignore items that you already scanned. Since the rate of scanning differs on each platform, spamming the RN bridge is not a good default due to performance issues.
As an example, QR codes, and multiple barcodes can often appear close to each other on products.

If you remove setTorchMode then be careful since it's also implemented in Android and was requested by a few users already:
https://github.com/teslamotors/react-native-camera-kit/pull/523
I honestly don't think setTorchMode is something we should have imperatively - that's what props are for, so if we remove it we need to remove on both platforms and be give an example of what to do instead in a changelog.

If you remove setTorchMode then be careful since it's also implemented in Android and was requested by a few users already: #523
I honestly don't think setTorchMode is something we should have imperatively - that's what props are for, so if we remove it we need to remove on both platforms and be give an example of what to do instead in a changelog.

Fully aligned. I wanted your insight before to put it back / remove it from Android.
It comes from a bug, where defaulting torchMode to 'on' doesn't work.
The right fix is to address the timing issue like I did on iOS. Torch should be delayed until camera is ready
The workaround should be to delay setting torchMode by a few ms, than creating another way of doing it.
I'll take a look after this PR being merge.

While looking for leaks, I noticed the CKCameraManager is retained when we go back to the main screen

It is released/deinit as soon as we open a new one.
I put that here just in case you have any idea why, might be a React Native thing

As a general comment, try to avoid making extensions. Extensions are non-obvious and global. They can come from anywhere. It makes code hard to read and understand for newcomers so it should be limited to use cases where we cannot do it in a more obvious way.

If you remove setTorchMode then be careful since it's also implemented in Android and was requested by a few users already: #523
I honestly don't think setTorchMode is something we should have imperatively - that's what props are for, so if we remove it we need to remove on both platforms and be give an example of what to do instead in a changelog.

Fully aligned. I wanted your insight before to put it back / remove it from Android.
It comes from a bug, where defaulting torchMode to 'on' doesn't work. The right fix is to address the timing issue like I did on iOS. Torch should be delayed until camera is ready The workaround should be to delay setting torchMode by a few ms, than creating another way of doing it. I'll take a look after this PR being merge.

Cool. Let's get rid of setTorchMode on both platforms then.
On a separate note, the code doesn't compile right now. Please make sure I can also run the latest commit that's pushed so I can verify we don't create a regression.

On a separate note, the code doesn't compile right now. Please make sure I can also run the latest commit that's pushed so I can verify we don't create a regression.

Did you run yarn bootstrap? I added a file, which requires a pod install

As a general comment, try to avoid making extensions. Extensions are non-obvious and global. They can come from anywhere. It makes code hard to read and understand for newcomers so it should be limited to use cases where we cannot do it in a more obvious way.
(I noticed that scaleZoomFactor was moved into the extension, which is unnecessary)

Extensions became fairly common in mobile native world, but agree might be non-obvious developers used to other paradigms.
First, I'm aligned on not spreading logic around.
I used them here only to extract uninteresting boilerplate, not related to the actual camera logic. Like locking configuration to update torchMode / zoomFactor (which can be easily missed), or converting one type to another.
Benefit of having them here is we can easily unit test them, contrary to private methods in consumer class.
However, as you said, if bypassed/duplicated because unknown, it's not any better :)
I can update the code, what do you recommend? My only advice would be to write code that could be unit tested, because there is quite a few subtle things that could be broken fairly easily

As a general comment, try to avoid making extensions. Extensions are non-obvious and global. They can come from anywhere. It makes code hard to read and understand for newcomers so it should be limited to use cases where we cannot do it in a more obvious way.

(I noticed that scaleZoomFactor was moved into the extension, which is unnecessary)

Extensions became fairly common in mobile native world, but agree might be non-obvious developers used to other paradigms.
First, I'm aligned on not spreading logic around.
I used them here only to extract uninteresting boilerplate, not related to the actual camera logic. Like locking configuration to update torchMode / zoomFactor (which can be easily missed), or converting one type to another.
Benefit of having them here is we can easily unit test them, contrary to private methods in consumer class.
However, as you said, if bypassed/duplicated because unknown, it's not any better :)
I can update the code, what do you recommend? My only advice would be to write code that could be unit tested, because there is quite a few subtle things that could be broken fairly easily

Normal functions or public functions can be unit tested. We needn’t unit test every single method though.
Private methods in this context do not help. They are a way to hide methods that we don’t want exposed but we aren’t writing a Swift API so there is no contract to keep or hide, so if it helps, feel free to make it a public method or expose any other methods too.

While looking for leaks, I noticed the CKCameraManager is retained when we go back to the main screen

It is released/deinit as soon as we open a new one.
I put that here just in case you have any idea why, might be a React Native thing

RN modules are kept in memory unless we actively delete our stuff. We probably can’t rely on deinit but must use viewDidHide (or whatever the equivalent might be that actually works here).
That’s my only thought right now.
It would be nice to fix although I’d say it’s not important to getting this particular PR merged. It’s likely an old issue if my theory holds up.

@scarlac I pushed the things we talked about. Let me know if I forgot anything.
FYI I noticed the examples are broken on Android. Bottom bar appears just below top bar

@scarlac I pushed the things we talked about. Let me know if I forgot anything.
FYI I noticed the examples are broken on Android. Bottom bar appears just below top bar

Ah yes, I'll try to have a look at that if you don't. I made some adjustments to the flexbox sizing of the elements and the viewport on Android has 0 height by default whereas iOS viewport is larger.

@scarlac I pushed the things we talked about. Let me know if I forgot anything.
FYI I noticed the examples are broken on Android. Bottom bar appears just below top bar

Ah yes, I'll try to have a look at that if you don't. I made some adjustments to the flexbox sizing of the elements and the viewport on Android has 0 height by default whereas iOS viewport is larger.

👍. I can look at it, I just need to know what's the expected behavior.
On the existing CameraScreen the preview seems to be full screen on Android, while "centered" on iOS. But it probably means Android camera preview is cropped left/right?
Same, what do you expect for the preview. Full screen or centered.
I would go centered for both platform/use case to simplify the example, but let me know what you expected

Ah yes, I'll try to have a look at that if you don't. I made some adjustments to the flexbox sizing of the elements and the viewport on Android has 0 height by default whereas iOS viewport is larger.

👍. I can look at it, I just need to know what's the expected behavior.
On the existing CameraScreen the preview seems to be full screen on Android, while "centered" on iOS. But it probably means Android camera preview is cropped left/right?
Same, what do you expect for the preview. Full screen or centered.
I would go centered for both platform/use case to simplify the example, but let me know what you expected

Centered, yes. 4:3 locked format for this example, as you've probably noticed. It's for a future update to somehow detect camera dimensions but the majority of camera/sensors are 4:3.
The challenge is that even 4:3 may be too large on some small/slim screens, so even centered can be a challenge. For the example project we shouldn't spend too much time optimizing the UI. In the end, it's just an example, not a "perfect" implementation.

I pushed a first shot.

iOS
Android

Zones

Real

My Android camera is cropped a bit, but might be acceptable.
What's not great is the Android scan target isn't centered anymore (but crop is, camera is cropped same size top/bottom)

Something to look at later

Thanks David. I'll fix the frame on Android.

Thank you so much @DavidBertet, this was extremely helpful! Hopefully this will encourage further high quality contributions now that we're mainly using Swift.
🎉


Simple chat app

This PR provides a very simple python script for beginners to get started.  It replicates the basic chatgpt-like conversational experience.

Why are these changes needed?
Many new users struggle to run the NVDA-TESLA example or the notebooks, since they all involve various kinds of complexity.

Related issue number
#919

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[X] I've made sure all auto checks have passed.

Thanks. Shall we add a link from README or https://microsoft.github.io/autogen/docs/Getting-Started to this example? cc @qingyun-wu @skzhang1 what's a good place on the website to add a link to this example?

How about putting the link in Human involvement  section with title Simple example in ChatGPT style?  If you think so, I will make a PR accordingly.
I think the examples in the readme and quick start sections are also simple, there is no need to include this example in those sections.

Thanks. Shall we add a link from README or https://microsoft.github.io/autogen/docs/Getting-Started to this example? cc @qingyun-wu @skzhang1 what's a good place on the website to add a link to this example?

How about putting the link in Human involvement section with title Simple example in ChatGPT style? If you think so, I will make a PR accordingly. I think the examples in the readme and quick start sections are also simple, there is no need to include this example in those sections.

A link in the Human Involvement section would make sense. I also think many beginners would appreciate a super-simple example mentioned on the README page. A very short section titled "Simple example in ChatGPT style" could be inserted between the current Installation and Multi-Agent Conversation Framework sections. This new section might contain just a single sentence of explanation, and a link to the example code. The Quickstart section directs readers to the notebooks, but none of those are as simple as this example.


Using Angularfire2 inside Php application

Hello Guys ,
I want to create a chat app using Angularfire2.
After that i want to insert that code inside my php application.
Will it work ?
I have seen the tutorial that , when we use ng server it creates the app at http://localhost:4200.
But i don't want to integrate the angular2 app in my php app via iframe.
I also tried doing ng build and then running http://localhost/angular2/dist/  but it didn't worked.
Any other help guys , Please ?

Hi @bhawin-bigstep. Please use Stackoverflow for these general "How To" problems, as this repo is used for troubleshooting library issues.

Okay @davideast


Option for forcing strict original post discovery

As a follow up to #154 I talked with @snarfed on IRC about the possibility of forcing the strict discovery of original posts that are mentioned in there.
This would enable those who only POSSE some of their tweets (like blog posts, images, links but not all their microblog content) to have their tweets without any rel-syndication URL:s be treated as having no original posts, while still having the tweets that have rel-syndication links to be treated as full-fledged POSSE content.
In practice this would mean that only links to pages with a rel-syndication back to the tweet will have u-in-reply-to, u-like-of etc added to them – the rest will have u-mention instead.

related to #51. finishing that will get close to this, but not all the way.

fwiw, we actually implemented this for github in 675718ca1ff015e1aaf315a0a6cfd26dc4eae426. discussion in https://chat.indieweb.org/dev/2018-02-26#t1519610412751400. the motivation was that github issues and comments often include links to examples, docs, etc that aren't either the original post or mentions per se, so they shouldn't be webmentioned.
so the remaining work to do here would be to add a per user setting.

cc @aaronpk, who'd like this, and @sebsel and @RosemaryOrchard, who are interested more generally.


Allow DnsEndpointGroups to set a negativeTtl

Motivation:
Fixes #3938
Modifications:

Wire up a negativeTtl option to the builders and classes

Result:

Closes #3938

Could you also a test case for this?
You might want to refer to the negativeTtl test of RefreshingAddressResolver:
https://github.com/line/armeria/blob/master/core/src/test/java/com/linecorp/armeria/client/RefreshingAddressResolverTest.java#L258

@ikhoon @trustin (because I see your name in the netty code related to this stuff), having trouble testing this. I exposed the resolver as visible for testing, but after creating a DnsAddressEndpointGroup with an invalid hostname, the resolveCache still seemingly has no entries. Based upon the code and the tests I saw in netty, I was expecting a cached entry for the invalid hostname

When debugging the test I can see the negativeTtl makes it way down to the resolverCache, but I just don't see any entries getting added

Checked the Netty code about DNS cache. If DnsQuestion is used for DNS query, results are not cached by resolveCache.
This might be not a problem for successful results that are cached in EndpointGroup.
https://github.com/line/armeria/blob/766812a3a0c25346c376f0dbb98511e77a7159fd/core/src/main/java/com/linecorp/armeria/internal/client/DefaultDnsNameResolver.java#L76-L85
https://github.com/netty/netty/blob/944a3e5be37bf634e4985075103cd45e618065ab/resolver-dns/src/main/java/io/netty/resolver/dns/DnsNameResolver.java#L849-L854
https://github.com/netty/netty/blob/23c0bbb9045fda365e906504b559a11bad717faa/resolver-dns/src/main/java/io/netty/resolver/dns/DnsRecordResolveContext.java#L82-L86
To support negative TTL, there are two possible workarounds on Armeria's side.

RefreshingAddressResolver caches the resolved result by itself. We can use RefreshingAddressResolver for DnsEndpointGroup.
Manually caches the cacheable failure - UnknownHostException.

What do you think? @minwoox

On second thought, as DnsEndpointGroup resolves DNS record periodically, negativeTtl makes no sense.
If a DNS query fails, the next query will be delayed by a Backoff that has almost the same effect as negativeTtl.
If you need a constant negativeTtl, Backoff.fixed() might be suitable for that.
The following line seems to be removed for clarity.
https://github.com/line/armeria/blob/5b384fbe27e7e6f9225d6db91cbb684d09dfbb5e/core/src/main/java/com/linecorp/armeria/client/endpoint/dns/DnsEndpointGroup.java#L96

On third thought(😅), I think we can clear the cache Endpoints in EndpointGroup and make it an empty EndpointGroup

if a negativeTtl is specified and 2) the cause of a DNS failure is UnknownHostExcepiton.
Afterwards, the next DNS query will be scheduled after negativeTtl.

Yeah, I agree with @ikhoon. We have Backoff for failure cases so we do not need negativeTtl from the first. 😅
@AngerM I'm really sorry about this. 😅

@minwoox @ikhoon there is one case where the negative ttl could still have effects: if you have multiple search domains. The way this all came about was that (for legacy reasons) we have multiple search domains configured in our cluster, most of these are going to fail for a given endpoint group, but we still see the slam of netty searching for all the various names when it refreshes

if you have multiple search domains. The way this all came about was that (for legacy reasons) we have multiple search domains configured in our cluster, most of these are going to fail for a given endpoint group, but we still see the slam of netty searching for all the various names when it refreshes

IIRC, it has nothing to do with the negativeTtl.
The DNS resolver appends the search domains to the DNS and sends it DNS servers to find out it it's a valid domain or not.
So, even if we configure the negativeTtl, which is basically the same using Backoff.ofFixed(negativeTtl), the process will be the same.
How about configuring the searchDomains by yourself if you feel the DNS resolver sends too many queries by appending searchDomains?
Of course, we don't have a setter for that so we should provide it via DNS endpoint group builder.

The hope was setting a (longer) negativeTtl so when the resolver appends the search domains, the 'bad' ones hit the cache most of the time with no result, and just the 'good' one end ups getting re-resolved.

The hope was setting a (longer) negativeTtl so when the resolver appends the search domains, the 'bad' ones hit the cache most of the time with no result, and just the 'good' one end ups getting re-resolved.

Now I got what you meant.
But Netty doesn't provide caching for individual queries that append search domaing.
https://github.com/netty/netty/blob/4.1/resolver-dns/src/main/java/io/netty/resolver/dns/DnsResolveContext.java#L1051
I guess we need to file an issue to the NETTY. 😅

Oops, I found out that it's not cached anyway in Netty.
https://github.com/netty/netty/blob/4.1/resolver-dns/src/main/java/io/netty/resolver/dns/DnsRecordResolveContext.java#L83-L86
In order to support caching for individual queries, we need to extract this part from Netty and implement it In Armeria's  RefreshingAddressResolver.
Then, we can use RefreshingAddressResolver for both WebClient and DnsEndpointGroup.
This is going to be pretty much a big change but I think it's worth trying. Are you still interested in it? 😄
Just let us know if you don't have time for it. We might implement it later. But before that setting the small number of search domains is the possible workaround I guess.

Hmm. I don't know if I will have time to continue on this, but I will point some of my coworkers here in the hopes one of them may be able to pick it up.

Please, don't worry. 😄
We can also implement this feature later when we have some time. Just let us know if you really need this feature then we might prioritize it. 😄


How to use node/js/etc?

I'm interested in learning how to setup and run a program like this. Can someone point me in the right direction?

Follow the instructions on the first page. You need to install node.js, there is a link within the instructions.

If you are having issues, try doing this:
git clone https://github.com/jpchip/giveaway-grabber.git
then navigate to the folder and do an
npm install
then
npm start


MaterialLocalizations.of should not return null under a MaterialApp

Example snippet that crashes when the flutter_localization package is not included:
class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return new MaterialApp(
      locale: const Locale('he'),
      home: new Scaffold(
        appBar: new AppBar(),
        body: new Container(),
        drawer: new Container(),
      ),
    );
  }
}

This can currently crash with:
I/flutter ( 3887): The following NoSuchMethodError was thrown building AppBar(dirty, state: _AppBarState#5d89b):
I/flutter ( 3887): The getter 'openAppDrawerTooltip' was called on null.
I/flutter ( 3887): Receiver: null
I/flutter ( 3887): Tried calling: openAppDrawerTooltip
I/flutter ( 3887):
I/flutter ( 3887): When the exception was thrown, this was the stack:
I/flutter ( 3887): #0      Object.noSuchMethod (dart:core-patch/dart:core/object_patch.dart:46)
I/flutter ( 3887): #1      _AppBarState.build (package:flutter/src/material/app_bar.dart:370:54)
...

The crash is because without the localization package MaterialLocalizations.of(context) is null when we do (in app_bar.dart):
          tooltip: MaterialLocalizations.of(context).openAppDrawerTooltip,

We should assert that locale is one of the locales in supportedLocales.

+1 for that.
In this case I just wanted to minimize the snippet so removed every line I could :)
To be clear, this one line longer snippet crashes the same way:
class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return new MaterialApp(
      locale: const Locale('he'),
      supportedLocales: const <Locale>[const Locale('he')],
      home: new Scaffold(
        appBar: new AppBar(),
        body: new Container(),
        drawer: new Container(),
      ),
    );
  }
}

We should also assert if you specify a supportedLocales that doesn't have a delegate provided that can service that locale. :-)

This is still not yet fixed, correct? I'm working in an application that I created a few days ago and I'm trying to display a bottom modal sheet (following this example), and I'm getting a similar error:
E/flutter (25415): [ERROR:topaz/lib/tonic/logging/dart_error.cc(16)] Unhandled exception:
E/flutter (25415): NoSuchMethodError: The getter 'modalBarrierDismissLabel' was called on null.
E/flutter (25415): Receiver: null
E/flutter (25415): Tried calling: modalBarrierDismissLabel
E/flutter (25415): #0      Object.noSuchMethod (dart:core/runtime/libobject_patch.dart:46:5)
E/flutter (25415): #1      showModalBottomSheet (package:flutter/src/material/bottom_sheet.dart:286:53)

In fact, when I evaluate just
MaterialLocalizations.of(context);

I get null. Is there any workaround in the meantime while this issue gets addressed?

This has not been fixed (yet), I will try resolve it this week.
The null is a usually a symptom of using an unsupported locale, i.e. a lcoale that's not in the app's supportedLocales list. Is that what's happening in your case?
The planned fix is to improve the error reorting. Not to fallback to a supported but possibly incomprehensible language.

Hmm, in my example I hadn't specified any locales. Do I need to? I was only planning on supporting en-US for now, so I didn't specify anything. In the localization docs I see that I can pass parameters to the MaterialApp in order to specify supported locales.
If we need to have locales properly configured in order to show bottom modal sheets, I think some documentation around that would be good, considering they seem pretty disparate to me.

@kengorab Please file a new bug, I think what you're seeing may be different.

@Hixie I submitted: #18254

If anyone is encountering this while supporting a locale that is not one of Flutter's currently supported locales, the "fix" is to implement a LocalizationsDelegate for that locale, as documented by @HansMuller  in https://github.com/flutter/flutter/pull/12645

The above snippet now provides the following warning but doesn't error yet. Of course if you don't actually provide the locale it will crash immediately after.
Performing hot restart...
Restarted application in 1,506ms.
I/flutter (18779): ════════
I/flutter (18779): Warning: This application's locale, he, is not supported by all of its
I/flutter (18779): localization delegates.
I/flutter (18779): > A MaterialLocalizations delegate that supports the he locale was not found.
I/flutter (18779): See https://flutter.io/tutorials/internationalization/ for more
I/flutter (18779): information about configuring an app's locale, supportedLocales,
I/flutter (18779): and localizationsDelegates parameters.

It will not crash immediately afterwards (otherwise many tests would crash) unless your code tries to retreive a localized string.

In this case I had the drawer open on iOS which called the modalDismissBarrier (and failed to find Localizations). So not right after, you're correct

Hi @amirh
Are you still experiencing this issue? I couldn't reproduce it
Code Sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      locale: const Locale('he'),
      title: 'Material App',
      home: new Scaffold(
        appBar: new AppBar(),
        body: new Container(),
        drawer: new Container(),
      ),
    );
  }
}

Logs
Launching lib/main.dart on SM M305F in debug mode...
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done                         1.6s
✓ Built build/app/outputs/apk/debug/app-debug.apk.
D/FlutterView(21109): Detaching from a FlutterEngine: io.flutter.embedding.engine.FlutterEngine@5974154
D/FlutterActivity(21218): Using the launch theme as normal theme.
D/FlutterActivityAndFragmentDelegate(21218): Setting up FlutterEngine.
D/FlutterActivityAndFragmentDelegate(21218): No preferred FlutterEngine was provided. Creating a new FlutterEngine for this FlutterFragment.
D/FlutterActivityAndFragmentDelegate(21218): Attaching FlutterEngine to the Activity that owns this Fragment.
D/FlutterView(21218): Attaching to a FlutterEngine: io.flutter.embedding.engine.FlutterEngine@5974154
D/FlutterActivityAndFragmentDelegate(21218): Executing Dart entrypoint: main, and sending initial route: /
Syncing files to device SM M305F...
 5,000ms (!)

🔥  To hot reload changes while running, press "r". To hot restart (and rebuild state), press "R".
An Observatory debugger and profiler on SM M305F is available at: http://<IP_ADDRESS>:52186/CLbc7LOUoiA=/
For a more detailed help message, press "h". To detach, press "d"; to quit, press "q".
D/InputMethodManager(21218): prepareNavigationBarInfo() DecorView@a7d419a[MainActivity]
D/InputMethodManager(21218): getNavigationBarColor() -855310
V/InputMethodManager(21218): Starting input: tba=com.example.stable_flutter ic=null mNaviBarColor -855310 mIsGetNaviBarColorSuccess true , NavVisible : true , NavTrans : false
D/InputMethodManager(21218): startInputInner - Id : 0
I/InputMethodManager(21218): startInputInner - mService.startInputOrWindowGainedFocus
D/InputTransport(21218): Input channel destroyed: 'ClientS', fd=85
D/ViewRootImpl@1dddd66[MainActivity](21218): stopped(true) old=false
D/SurfaceView(21218): windowStopped(true) false io.flutter.embedding.android.FlutterSurfaceView{ee8c7f9 V.E...... ........ 0,0-1080,2301} of ViewRootImpl@1dddd66[MainActivity]
D/SurfaceView(21218): surfaceDestroyed callback.size 1 #1 io.flutter.embedding.android.FlutterSurfaceView{ee8c7f9 V.E...... ........ 0,0-1080,2301}
W/libEGL  (21218): EGLNativeWindowType 0x7515193010 disconnect failed
D/SurfaceView(21218): remove() io.flutter.embedding.android.FlutterSurfaceView{ee8c7f9 V.E...... ........ 0,0-1080,2301} Surface(name=SurfaceView - com.example.stable_flutter/com.example.stable_flutter.MainActivity@ee8c7f9@0)/@0xb9c05d8
D/FlutterView(21218): Detaching from a FlutterEngine: io.flutter.embedding.engine.FlutterEngine@5974154
E/ViewRootImpl@1dddd66[MainActivity](21218): Surface is not valid.
D/ViewRootImpl@1dddd66[MainActivity](21218): MSG_WINDOW_FOCUS_CHANGED 0 1
D/InputMethodManager(21218): prepareNavigationBarInfo() DecorView@a7d419a[MainActivity]
D/InputMethodManager(21218): getNavigationBarColor() -855310

Thank you

════════
I/flutter (22601): Warning: This application's locale, de, is not supported by all of its
I/flutter (22601): localization delegates.
I/flutter (22601): > A MaterialLocalizations delegate that supports the de locale was not found.
I/flutter (22601): See https://flutter.dev/tutorials/internationalization/ for more
I/flutter (22601): information about configuring an app's locale, supportedLocales,
I/flutter (22601): and localizationsDelegates parameters.
I/flutter (22601):
════════
I get this message and cant use various widgets because Localizations.of(context, MaterialLocalizations) returns null. German is listed as a supported locale, and i have registered supportedLanguages as well as localizationDelegates. As main app I use the MaterialApp, so why do I receive an error?! Cant fix this since days.

Could we have an updated sample code? I get errors regarding localeResolutionCallback in the last sample provided.

I tried below code sample that shows a warning in the console log which indicates what we need to do in order to fix the error:

 runnable code sample

import 'package:flutter/material.dart';

void main() {
  runApp(MaterialApp(
    locale: const Locale('he'),
    supportedLocales: const <Locale>[const Locale('he')],
    home: MyApp(),
  ));
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(),
        body: Container(),
        drawer: Container(),
      ),
    );
  }
}

 console log
======== Exception caught by widgets ===============================================================
The following message was thrown:
Warning: This application's locale, he, is not supported by all of its localization delegates.

• A MaterialLocalizations delegate that supports the he locale was not found.
• A CupertinoLocalizations delegate that supports the he locale was not found.

The declared supported locales for this app are: he

See https://flutter.dev/tutorials/internationalization/ for more information about configuring an app's locale, supportedLocales, and localizationsDelegates parameters.
====================================================================================================

======== Exception caught by widgets ===============================================================
The following message was thrown:
Warning: This application's locale, he, is not supported by all of its localization delegates.

• A MaterialLocalizations delegate that supports the he locale was not found.
• A CupertinoLocalizations delegate that supports the he locale was not found.

The declared supported locales for this app are: he

See https://flutter.dev/tutorials/internationalization/ for more information about configuring an app's locale, supportedLocales, and localizationsDelegates parameters.
====================================================================================================

As we can see from the console log, it doesn't throw the null error as originally described, but a warning on how to proceed to fix the error. So the fix for it per the log is to add below inside MaterialApp() and running updated code sample then does not show the warning or any error.
localizationsDelegates: [
      GlobalMaterialLocalizations.delegate,
      GlobalCupertinoLocalizations.delegate
    ],

 fixed code sample

import 'package:flutter/material.dart';
import 'package:flutter_localizations/flutter_localizations.dart';

void main() {
  runApp(MaterialApp(
    localizationsDelegates: [
      GlobalMaterialLocalizations.delegate,
      GlobalCupertinoLocalizations.delegate
    ],
    locale: const Locale('he'),
    supportedLocales: const <Locale>[const Locale('he')],
    home: MyApp(),
  ));
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(),
        body: Container(),
        drawer: Container(),
      ),
    );
  }
}

With above, I am going ahead and closing this as fixed, as the original error reported that threw null log isn't occuring anymore.

 stable, master flutter doctor -v
[✓] Flutter (Channel stable, 3.3.9, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.3.9 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b8f7f1f986 (12 days ago), 2022-11-23 06:43:51 +0900
    • Engine revision 8f2221fbef
    • Dart version 2.18.5
    • DevTools version 2.15.0

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

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

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.7.0-6.0.pre.23, on macOS 12.2.1 21D62 darwin-x64,
    locale en-GB)
    • Flutter version 3.7.0-6.0.pre.23 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 04ee5926a2 (76 minutes ago), 2022-12-12 19:42:23 -0800
    • Engine revision 290f3a35ee
    • Dart version 3.0.0 (build 3.0.0-19.0.dev)
    • DevTools version 2.20.0
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

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

! Doctor found issues in 1 category.


Chess redesign

Closing as this was migrated to separate repo - https://github.com/PaimaStudios/paima-chess-algorand


Cherry-pick #454

This PR cherry-picks the commits from PR#454.

Need to remove PR link

Need to remove PR link

Oh! I'm sorry. I've removed it.

Bors merge


What to do if react app is not in root url?

Hello!
I have app with url site.com/some/path/before/AppItself
How to work with url like that?
I tried to specify path in createJunctions as window.basePath + route but I receive message like
Uncaught Error: Branch "branchName" uses a pattern with "anything", but another pattern or alias already uses this identifier.

Thanks

got it.
https://junctions.js.org/examples/BaseLocation


Work item ID used in destination project breaks Parent/Child work items link.

Hi, I've successfully moved all work items and after creating and new team (same as source) and assigned rights all looked good. However, most iterations have an title group called "unparented" and in it are all the unlinked work items. After investigation it seems that the work ID was already used in the destination so a new work ID was created. This breaks the linking, is there a section I missed? If not any programatic way to relink?

I'm getting this as well, @sferg-msft

Were you using the latest version when you left this comment?  About a month ago I updated link handling due to a change in VSTS.

Yes. It was latest at time of attempt.

Any update on this? I'm running into the same problem.

@brmdbr Could you please attach your logs?

@obvioussean Work item number are not in sync with source TFS in VSTS? when I run my it is returning expected result based on ID order starting from 1 .


PacketTunnelProvider crash simulation options

Please review the release process for BrowserServicesKit here.
Required:
Task/Issue URL: https://app.asana.com/0/72649045549333/1205376937712482/f
iOS PR: https://github.com/duckduckgo/iOS/pull/1978
macOS PR: https://github.com/duckduckgo/macos-browser/pull/1597
What kind of version bump will this require?: Minor
Description:
To verify that crash reporting works as expected from the PacketTunnelProvider extensions, this PR adds simulation options to trigger two types of crash: a fatal error and a memory overuse crash.
Steps to test this PR:

See macOS PR (link above)
See iOS PR (link above)

OS Testing:

[ ] iOS 14
[ ] iOS 15
[x] iOS 16
[ ] macOS 10.15
[ ] macOS 11
[x] macOS 12

—
Internal references:
Software Engineering Expectations
Technical Design Template

Looking good so far, but I'll wait to approve until the client PRs are approved.


Mocket raises exceptions

Coverage decreased (-2.0%) to 96.71% when pulling 0aed016d4abcfdc145048f9e30b55240ede2b9b0 on issue/112 into e72325250f0e98999e85ef4b98eeaa48b9f7cad1 on master.

Coverage decreased (-2.0%) to 96.71% when pulling 0aed016d4abcfdc145048f9e30b55240ede2b9b0 on issue/112 into e72325250f0e98999e85ef4b98eeaa48b9f7cad1 on master.


Basic authentication?

See mbostock/d3#2131. These need to be passed to XMLHttpRequest.open.
We also need to expose the withCredentials flag (for cookie-based authentication?)—although at least now you can use the "beforesend" event to set it, I think. This should be separate from specifying a username and password, though.

Punting on this, as it can be done using beforesend.

This can’t be done in beforesend because we need to pass the username and password to xhr.open.


ARM Template Outline Browser does not appear

I observe non-deterministic behavior regarding whether or not the ARM Template Outline Browser appears in the "Explorer" pane in VS Code.  I find I have to go through the following gymnastics to make it reliably appear.
Consider a folder "workarea" with the following layout.
.
├── arm-oraclelinux-wls-dynamic-cluster
│   ├── pom.xml
│   ├── src
│   │   └── main
│   │       ├── arm
│   │       │   ├── createUiDefinition.json
│   │       │   ├── mainTemplate.json
│   │       │   └── nestedtemplates
│   │       │       └── clusterTemplate.json

I find I must open both mainTemplate.json and clusterTemplate.json, then move the focus between the two tabs to cause the ARM Template Outline to appear.

Thanks for raising the issue Ed. This behavior is fixed in the next release (days away from release).
https://github.com/microsoft/vscode-azurearmtools/issues/470

This release went out today. The extension should auto-update and at that time will include this functionality / fix.


TLS 1.3 OCSP Status Request and SCT List Extensions

Please note that while we are transitioning from travis-ci to AWS CodeBuld, some tests are run on each platform. Non-AWS contributors will temporarily be unable to see CodeBuild results. We apologize for the inconvenience.
Issue # (if available):
Implement sending of status_request and sct_list in the correct places
related: #1340, #1641
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request head (tls13_certificate_extensions@40c7676). Click here to learn what that means.
The diff coverage is n/a.


Need better scoping for [class*=col]

Detailed description

Describe in detail the issue you're having.

Some of selectors, e.g. [class*=col] in grid code, seems to match unintended elements, e.g. <nav class="bx--interior-left-nav--collapsible">

Is this a feature request (new component, new icon), a bug, or a general issue?

A bug.

Is this issue related to a specific component?

Grid.

What did you expect to happen? What happened instead? What would you like to see changed?

Grid style does not affect other components like carbon-addons-cloud ILN.

What browser are you working in?

Chrome, but basically N/A

What version of the Carbon Design System are you using?

Latest master.

What offering/product do you work on? Any pressing ship or release dates we should be aware of?

Carbon core component library.
Steps to reproduce

Pull the code from carbon-components#1541
gulp build:dev --rollup -b
Start a HTTP server to serve static files in demo directory

BUG: The ILN's right border is dotted, where it shouldn't:

@asudoh this selector is just for the demo code, so feel free to re-write it as needed in the target env 👍


Best Approach Given Data Set Size - Pytorch Explainer

Hey there!
I'm working on a project with 9000 samples and 300k features.
These features were used in multi-class classification and regression (multi-output) problems, using a Pytorch neural network model.
I've been trying to find the shapley values for the test set (~20% of the data), but this seems to be a computationally intractable problem, as I'm either getting huge CUDA or CPU memory errors or too lengthy compute times when I try to get the shaply_values after using Kernel, Gradient or Deep Explainers.
So far I've tried to split the shap samples up (different from data set samples) for gradient/kernel explainers and take the mean shapley values to try to handle large compute memory, and am considering running shap.kmeans beforehand to reduce the number of background samples. However, with 300k features, wouldn't kmeans center close to zero and the new background samples be meaningless? Perhaps I am mistaken about how it is used...
What would you recommend to handle this computationally intense problem in any reasonable amount of time?
Are the deep or gradient explainers worth using in this case?
Looking to get array of ~3000 samples x 300k features of shapley values as end product (test set).
Thanks! This is an awesome library and looking forward to including it in my research in the years ahead if it works.

Hey! I think the most scalable one right for PyTorch is the GradientExplainer. What happens if you try and explain just 10 samples using GradientExplainer? If you get memory errors you can use the batch_size argument to control how many samples get batched.

I believe the memory is fine. But seems like it’ll take too long to compute. What can I do to speed this up?
Thanks!

I have already tried what you mentioned, which I believe addressed the memory issues. I ran the jobs on a batch system, and they were taking too long to complete so I ended up terminating them. Just need to optimize for speed.

Oh I see what you mean. Yeah I’ll try just 10 samples and see what happens. In any case, I could probably break up my test array and concatenation the Shapley values at the end.

The number of outputs is variable, but let's say about 50. It is important to be able to explain all outputs though for my use case.
Thanks for the help! Hope this helps out others looking to make explanations on Pytorch models. I'll let you know if I find some more ways to speed things up.
In any case, I'll close this issue for now.