[FEATURE] Add box functionality

Is your feature request related to a problem? Please describe.

Missing functionality on the Box class, Both overwrite and delete is missing.
Describe the solution you'd like

I would like an overwrite:bool flag on BoxFileWriter so you can overwrite the file on Box if it already exists.
I would like a BoxFileDeleter so I can delete files on box.
Describe alternatives you've considered

This is basic functionality, there should not be a workaround needed for this.
Additional context

See following links:
https://github.com/box/box-python-sdk/blob/main/docs/usage/files.md#move-a-file
https://github.com/box/box-python-sdk/blob/main/docs/usage/files.md#delete-a-file

alternatively, we could also do a write_mode, like what we have in SFTP. For reference: https://github.com/Nike-Inc/koheesio/blob/485ee90f9f624897d27800ecc0510df35a2cb707/src/koheesio/integrations/spark/sftp.py#L149-L152


OPTIONS:
   --id value                     ID of authentication source (default: 0)
   --custom-path value, -C value  Custom path file path (default: "/home/git/custom")
   --config value, -c value       Custom configuration file path (default: "/home/git/custom/conf/app.ini")
   --version, -v                  print the version
   --work-path value, -w value    Set the gitea working path (default: "/home/git")

BUT the --id switch does NOT specify an authentication source. Instead it is used as the user identifier (not easy to figure out, btw).  I'd think it's a bug in implementation rather than documentation, and that the implmeentation is missing a --username switch to reference users by username instead of id

Note this is as of current master (980b0df8296cdec3692482c3efdbfa68036a1114)


Please update npm version.

Hi! I'm trying to install last version: npm install<EMAIL_ADDRESS>But after installation, the module does not contain these edits:
https://github.com/reactstrap/reactstrap/pull/690

I am using<EMAIL_ADDRESS>from npm and I get the changes referenced in the release. Can you confirm the version in the node modules directory directly?

It's working for me but an alpha.5 seems due anyway. Quite a few changes to get BS4-beta.2 working are in master but not released. Would be nice to start using the Projects tab to help prioritize issues and show upcoming releases. I'd be happy to help on the project management side along with coding. LMK!


NLog adapter doesn't support global instrumentation key

I noticed that my AI wasn't receiving log messages from NLog even though I had set the instrumentation key programmatically in my Application_Start block:
TelemetryConfiguration.Active.InstrumentationKey = AppSettings.AppInsightsKey;

If I set a breakpoint inside the InitializeTarget, the global key is set before the target initializes, but the telemetryClient.Context.InstrumentationKey is blank still.
Shouldn't the log adapters fallback on checking the active configuration?
i.e.
base.InitializeTarget();
this.telemetryClient = new TelemetryClient();
if (!string.IsNullOrEmpty(TelemetryConfiguration.Active.InstrumentationKey))
{
    this.telemetryClient.Context.InstrumentationKey = TelemetryConfiguration.Active.InstrumentationKey;
}
if (!string.IsNullOrEmpty(this.InstrumentationKey))
{
    this.telemetryClient.Context.InstrumentationKey = this.InstrumentationKey;
}

My mistake, was diagnosing Web API exception and had commented out the line that logs to NLog :-1:


chore(monorepo): reinstall pnpm lock

fix outdated pnpm lock file by reinstalling

I had to do this after merging a pull request that I think carried over a bad pnpm lock from earlier


PromQL (prometheus.io) language

Very simple, based on Go, PromQL language implementation

We aren't accepting new modes into the main distribution anymore. Please distribute modes as separate NPM packages, as the Elixir mode does.


Error when running readme example: I can't find file tikzlibraryquotes.code.tex'`

python my_arch.py works fine, producing the output included below. However, when I run pdflatex , I get error:
! I can't find file `tikzlibraryquotes.code.tex'.
<argument> ...nput tikzlibrary\pgf@temp .code.tex
                                                  \catcode `\@ =\csname tikz...
l.2 \usetikzlibrary{quotes,arrows.meta}

I presume this is a simple fix requiring an install. Please may you help me diagnose what I need installed on my system for this to run? I am able to run tikz fine and create examples e.g. this one.
LaTeX info
$ pdflatex --version
pdfTeX 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
kpathsea version 6.1.1
Copyright 2013 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
There is NO warranty.  Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Compiled with libpng 1.2.50; using libpng 1.2.50
Compiled with zlib 1.2.8; using zlib 1.2.8
Compiled with poppler version 0.24.5

Python output:
\documentclass[border=8pt, multi, tikz]{standalone}
\usepackage{import}
\subimport{../layers/}{init}
\usetikzlibrary{positioning}
\usetikzlibrary{3d} %for including external image

\def\ConvColor{rgb:yellow,5;red,2.5;white,5}
\def\ConvReluColor{rgb:yellow,5;red,5;white,5}
\def\PoolColor{rgb:red,1;black,0.3}
\def\UnpoolColor{rgb:blue,2;green,1;black,0.3}
\def\FcColor{rgb:blue,5;red,2.5;white,5}
\def\FcReluColor{rgb:blue,5;red,5;white,4}
\def\SoftmaxColor{rgb:magenta,5;black,7}

\newcommand{\copymidarrow}{\tikz \draw[-Stealth,line width=0.8mm,draw={rgb:blue,4;red,1;green,1;black,3}] (-0.3,0) -- ++(0.3,0);}

\begin{document}
\begin{tikzpicture}
\tikzstyle{connection}=[ultra thick,every node/.style={sloped,allow upside down},draw=\edgecolor,opacity=0.7]
\tikzstyle{copyconnection}=[ultra thick,every node/.style={sloped,allow upside down},draw={rgb:blue,4;red,1;green,1;black,3},opacity=0.7]

\pic[shift={(0,0,0)}] at (0,0,0)
    {Box={
        name=conv1,
        caption= ,
        xlabel={{64, }},
        zlabel=512,
        fill=\ConvColor,
        height=64,
        width=2,
        depth=64
        }
    };

\pic[shift={ (0,0,0) }] at (conv1-east)
    {Box={
        name=pool1,
        caption= ,
        fill=\PoolColor,
        opacity=0.5,
        height=32,
        width=1,
        depth=32
        }
    };

\pic[shift={(1,0,0)}] at (pool1-east)
    {Box={
        name=conv2,
        caption= ,
        xlabel={{64, }},
        zlabel=128,
        fill=\ConvColor,
        height=32,
        width=2,
        depth=32
        }
    };

\draw [connection]  (pool1-east)    -- node {\midarrow} (conv2-west);

\pic[shift={ (0,0,0) }] at (conv2-east)
    {Box={
        name=pool2,
        caption= ,
        fill=\PoolColor,
        opacity=0.5,
        height=28,
        width=1,
        depth=28
        }
    };

\pic[shift={(3,0,0)}] at (pool1-east)
    {Box={
        name=soft1,
        caption=SOFT,
        xlabel={{" ","dummy"}},
        zlabel=10,
        fill=\SoftmaxColor,
        opacity=0.8,
        height=3,
        width=1.5,
        depth=25
        }
    };

\draw [connection]  (pool2-east)    -- node {\midarrow} (soft1-west);

\end{tikzpicture}
\end{document}

Yes, it was as I suspected, my tex live installation is super old. Here's how I solved my problem:

download texlive 2018 https://www.tug.org/texlive/acquire-netinstall.html
follow install instructions https://www.tug.org/texlive/quickinstall.html

additionally, this actually required that I sudo mkdir /usr/local/texlive & chmod 777 /usr/local/texlive to enable writing to the required directory
this takes 15 mins or so, so make a cup of tea

Don't forget to add the binaries to your path, e.g. add export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH to your ~/.bashrc
source ~/.bashrc now run pdflatex --version to check the changes have been applied

Notes
The platform I'm using is Linux and the distribution is Linux Mint 17 Rafaella - that's pretty close to Ubuntu

Hi. Thanks for great work. I also got the error. Does it mean I need to install texliv?

 File "my_arch.py", line 2
    sys.path.append('../')
    ^
IndentationError: unexpected indent
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) (preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
! I can't find file `my_arch.tex'.
<*> my_arch.tex

(Press Enter to retry, or Control-D to exit)

Hi. Thanks for great work. I also got the error. Does it mean I need to install texliv?

 File "my_arch.py", line 2
 \end{tikzpicture}
\end{document}

This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) (preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./my_arch.tex
LaTeX2e <2016/02/01>
Babel <3.9q> and hyphenation patterns for 3 language(s) loaded.

! LaTeX Error: File `standalone.cls' not found.

Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: cls)

Hi, I got the same problem. How do you solve?

Install texlive extra for ubuntu

hello！Thank you for sharing.
But I have the same problem.
My system is Windows. Download the installation package for 2018, I don't know how to deal with this problem.
C:\Users\lenovo>tex -version
MiKTeX-TeX 2.9.3759 (3.1415926) (MiKTeX 2.9)
Copyright (C) 1982 by D. E. Knuth; all rights are reserved.
TeX is a trademark of the American Mathematical Society.
C:\Users\lenovo>pdflatex --version
MiKTeX-pdfTeX 2.9.4307 (1.40.12) (MiKTeX 2.9)
Copyright (C) 1982 D. E. Knuth, (C) 1996-2006 Han The Thanh
TeX is a trademark of the American Mathematical Society.
The error：
I can't find file `tikzlibraryquotes.code.tex'. \usetikzlibrary{quotes,arrows.meta}
Emergency stop. \usetikzlibrary{quotes,arrows.meta}
I hope I haven't disturbed you. Thank you.
@JamesOwers @John1231983

@John1231983 @Ysoleil - you both just need to install Tex Live on your system. Follow the instructions to do so on their website (I provide a link above!).


DDS Textures are scrambled

There is something wrong with the surface created for DDS textures.
This is the original texture extracted from the game folder:

This is the surface, which I saved as a DDS file, afteer the surface is unlocked.

The texture is a DXT3 BC2_UNORM one:
18.zip
My guess is that the surface is already created with incorrect settings, so that the data layout of the memory does not align with the one from the surface.

Yes, I have seen this also.  It looks like only the top part of the file is preserved.  This could be for a couple of reasons:

The texture is created early in the and not properly backed up when the surface is recreated after getting released.
It could be that the texture is not loaded right into memory, if it is loaded by Blt() (which uses CopySurface()) or by locking the surface.
Or it is not creating the right surface to begin with.

Do you know how/when the surface is loaded into memory?

I just checked and the textures are not getting released and reloaded.  Also, the requested type of texture is being created correctly. i.e. When the game requests D3DFMT_DXT3 then a D3DFMT_DXT3 texture is getting created.
I also checked the texture size (width & height) and the requested size is getting created.
Somehow it seems there is an issue with populating the texture.  Maybe the way DirectDraw populates the texture does not work correctly with Direct3D9 textures?
Textures are done in blocks.  It looks like the first row of blocks are getting populated but none of the other rows.
Here is a good post I found:  https://www.g-truc.net/post-0335.html

So I did a test, where I instead of letting the game write into the surface buffer, I let it write into my own memory and saved that data as a DDS file. The result is the same. And the memory matches what we see, so most of it remains zero.
So it seems to me that the Unlock function is called too early.

That's weird.  I am seeing the call to Unlock, but I don't see the call to Lock the DXT textures.

I hooked into
m_IDirectDrawSurfaceX::LockD39Surface(D3DLOCKED_RECT* pLockedRect, RECT* pRect, DWORD Flags)

I hooked into m_IDirectDrawSurfaceX::LockD39Surface()

The weird thing is that Lock() and Unlock() are supposed to be a pair and LockD39Surface() and UnlockD39Surface() are supposed to be a pair.  However, I am seeing Unlock() being called without Lock() ever getting called.  Something weird is happening here and I am not sure yet if it is something weird with the game or with dxwrapper.

Perhaps completely unrelated, but on some compiles/platforms (like original Xbox) Lock got inlined, meaning any interface (re-)implementation wouldn't ever get called (instead, the code itself was compiled into the caller location)

Another idea to fix this could be to just call the other function if it is a DXT surface type.

It appears the the issue is an issue with lPitch.  DirectDraw returns 65535 whereas Direct3D9 returns 1024 for some of the DXT formats.

If you change the following line then it will be able to draw all the textures correctly:
From:
lpDDSurfaceDesc2->lPitch = LockedRect.Pitch;

to:
lpDDSurfaceDesc2->lPitch = LockedRect.Pitch * (ISDXTEX(surfaceFormat) ? 64 : 1);

OMG you are a genius!! Yes, that fixed it :)


UI Filters not updating properly

All the filters of the new UI Update only every second time.
To Reproduce
1)Run temporal server and UI-server separately.
2)Run UI separately.
3)Change the Workflow status filter to "Terminated" to display only terminated workflows.( This would change the URL but it will keep displaying previous content.)
4)Choose something else from that filter.(It will work second time)
Expected behavior
1)Filters should work every time.
This function is only getting called every second time the filter is changed.
const updateWorkflows: StartStopNotifier<WorkflowExecution[]> = (set) => {
  return parameters.subscribe(({ namespace, query }) => {
    withLoading(loading, updating, async () => {
      const { workflows } = await fetchAllWorkflows(namespace, { query });
      set(workflows);
    });
  });
};

Screenshots
Raised it here before
https://community.temporal.io/t/filters-in-ui-beta-not-working/5126
Desktop

OS: windows
Browser:-  Chrome and Firefox

Thanks for the report. I'm looking into this, but I'm having a hard time recreating the issue.

Thanks for the report. I'm looking into this, but I'm having a hard time recreating the issue.

Thanks for looking into this. Could you point out at which step you are finding it hard to recreate.


Wip readme

@greph @swellmike Please take a look at this MR when you get the chance. Simple modifications to README specifying that this is currently a WIP


Support for prednote <IP_ADDRESS>

Would it be possible to get an updated release of matches that compiles with the latest version of prednote?
http://packdeps.haskellers.com/feed?needle=matchers

Fixed, thanks.


New Release

Hello there 👋
I tried to use the composer collector #1174 in my new project where i wanted to use deptrac and realised that this i not included in the last release. I'm using the shim version and the laste release is from december 2022. Is there a new way recommended to use deptrac?

There is no new way. The maintainers are just short staffed and didn't have time to cut a release.
In the meantime, you can you use this repo as the dependency and composer require-dev the dev-main branch or a particular commit hash if you include the GitHub repo as a source in your composer.json file.

@see https://github.com/qossmic/deptrac/issues/1243

I can understand that maintainers dont have the time to cut the release. I also just read in some other PR that the next release would be the next major version. So i would need to pick the 2.0.x branch i guess if i want to use right now the "latest" version? I saw there is already a 3.0.x branch.

@DanielBadura you can savely ignore the branches 2.0.x and 3.0.x. Right now they are just placeholders for when the release is ready.
Main is this the branch with the most current changes. But you also have to be aware that the main branch already contains BC.

Just realised, cannot use the commit with deptrac-shim version which i wanted to use.. 😓


Integrationt tests: colorize: test-92369.cpp (15251ms) takes 15s to finish

At least for me on macOS the  colorize: test-92369.cpp (15251ms) takes 15s to complete, I think that is quite a bit for a single unit test, even for integration.

We do this on purpose to make sure that a stuck grammar will not cause VS Code to hang.
Alex Dima made the fix that prevents the hang a while ago so we can probably remove the test.


simple hover for systemverilog variables and parameters

Hello
I made a feature that show the line where the variable declare when mouse hover to the variable
like pictures below

If there are any problems, let me know

First of all, thank you for sending me your great PR.
I have a few comments below.

Variables defined as inout is also port. (https://www.hdlworks.com/hdl_corner/verilog_ref/items/PortDeclaration.htm)
There are some integer and real types not only int but also byte, long, etc... (https://www.doulos.com/knowhow/sysverilog/tutorial/datatypes/)

Hi,
I update the supported datatypes for byte, long, etc...
typedef, struct, and enum are not working now

Looks good to me! Cheers! 🍻


Allow compiler executable under test to be overridden

This PR adds an environment variable SPEC_COMPILER which, when set, overrides the Crystal compiler executable being used in specs.
This is mainly relevant for local development on Windows. Unlike on CI, bin\crystal.exe relative to the repository root is normally not expected to exist, because the local compiler is supposed to go into .build instead; also unlike on Unix, bin\crystal must resolve to an .exe, never some other script like bin\crystal.bat. With this PR, any installation of Crystal or wrapper script can be used in place of bin/crystal.
crystal spec automatically sets this environment variable to the compiler process itself if the variable is absent, before building the specs (not just before running, so that SPEC_COMPILER would always be available even in macros). If the specs are built and then run separately, like on CI, then SPEC_COMPILER should also be set beforehand (our workflows don't need this).

Sounds good! I think the env var name should be CRYSTAL_SPEC_COMPILER, though.

CRYSTAL_SPEC_COMPILER_FLAGS and CRYSTAL_SPEC_COMPILER_THREADS are already used by the bin/check-compiler-flag, but these are only effective for the fresh compiler class required by the specs, not any existing Crystal executable, so there would be some potential confusion.

CRYSTAL_SPEC_COMPILER_EXECUTABLE might be better.

Perhaps a bit shorter  CRYSTAL_SPEC_COMPILER_BIN?


[MRG] FIX + API : on plot topo colors

FIX : fix colors on topo with black background
+
API : add dark_background parameter to show white background

Codecov Report

Merging #4303 into master will increase coverage by <.01%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##           master    #4303      +/-   ##
==========================================
+ Coverage   86.04%   86.05%   +<.01%
==========================================
  Files         346      346
  Lines       62842    62879      +37
  Branches     9661     9668       +7
==========================================
+ Hits        54075    54109      +34
- Misses       6108     6109       +1
- Partials     2659     2661       +2

done

good to go on my end

fixed

Thanks @agramfort


Release sentinel 2024 03 01 preview biz apps agents

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

[!NOTE]
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

 Click here to see the details of Step 1
Breaking changes review (Diagram Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

 Click here to see the details of Step 2
ARM API changes review (Diagram Step 2)

For help with Step 2 / "ARM review", see https://aka.ms/azsdk/pr-arm-review.

 Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[ ] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[ ] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with PR workflow diagram Step 2 (ARM review), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Please check and fix the following errors:
❌ Swagger LintDiff
❌ Swagger ModelValidation
❌ Swagger SemanticValidation
❌ Swagger SpellCheck
❌ Swagger PrettierCheck

a PR regarding the spellcheck was submitted
https://github.com/Azure/azure-rest-api-specs/pull/27874#issuecomment-1958931347
adding the word nwrfc
https://sap.github.io/PyRFC/install.html

@ms-henglu hi
I've updated the file of the spell in this PR - https://github.com/Azure/azure-rest-api-specs/pull/27874#issuecomment-1958931347
what it's failing on the spell check...?
should I pull for that?


[DCOS-55014] add drain status to node details

Testing
There is a bug that prevents the mesos state store from loading when useFixtures is true (this does not seem to affect integration tests?) Let me know if you are affected by the same issue. If so, just bypass the state store loading by changing NodeDetailPage line 41 from mesosStateLoaded: false to mesosStateLoaded: true
Visit the node details page (details tab) and see the drain status and new section there
Dependencies
This PR is currently based on #3960
Screenshots

Build is failing because of the commit message.

Let me know if you are affected by the same issue.

I am.
Nitpick: I think it looks better with a slightly smaller margin-left:
Original 7px margin.

4px margin.

It's failing again. I think it's because it's not pointing to master.

Nitpick: I think it looks better with a slightly smaller margin-left:

i used the same paddings as are used in the services table in case someone wants to clean that up at some point. 7px is pretty nice to grep for.

Going ahead and merging on the basis of previous approvals

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


Gitolite and 1.9.x ruby requirement

I was trying today to install redmine-gitolite, but there's an issue: gitolite gem requires ruby 1.9.x while Redmine requires ruby 1.8.x.
How did you solve this?

In wingrunr21/gitolite repository README (https://github.com/wingrunr21/gitolite/blob/master/README.rdoc), it's specified that the gem is requiring ruby 1.8.x or 1.9.x.
Does it change for the new release 0.0.3.alpha ? Which issue did you got ?
For issues with the gem, I think you could post in the official repository : https://github.com/wingrunr21/gitolite

as mentioned above
Sent via Hubroid


🐞 Bug blank statement is there

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
blank statement is there
Steps To Reproduce
Go to 'circuitverse'
Click on '[Learn Logic Design]'
now select [Guidelines]
Scroll down to Workflow
See error ( the d option is black)

Expected Behavior

Screenshots
No response
Device Information [optional]
- OS:
- Browser:
- version:

Additional context
No response
Are you working on this issue?
Yes

@yogeshsshekhawat, Are you still working on this? I am going to work on this.

This issue is not from this repository. So you can raise this issue on this repository .

@tanmoysrt please assign me this issue

Raise the issue in this repo https://github.com/CircuitVerse/Interactive-Book


Add sandwich boat model and multi-boat support

Summary
First pass at sandwich boat model and multi-boat support. Uses the CoRa model as the foundation for the general structure.
Depends on vrx
To Test
roslaunch sandwich_gazebo sydney_sandwich.launch

This will launch two boat models. The joystick commands only affect the boat whose namespace is that of the default namespace args in the launch file.
Current Issues

Steering for sandwich and CoRa not as expected
Model is scaled up 10x as changing mass values causes the USV dynamics plugin to fail

I was able to run this PR using the setup described here: https://github.com/Field-Robotics-Lab/optical_swarm/wiki/workspace_setup
I'd like to have @matthewheubach do the review/approval of the PR.  Good practice.

I was able to run the launch file as described. Except for known issues #2 and #3, I did not have any problems with the launch file or sandwich boat models.


fail install - docker

Hi guys,
I followed the steps here: https://github.com/gitscrum-community-edition/docker-gitscrum

clone the repository
start with docker-compose up --build

After a few minutes, I have three containers running, but when I access http: // localhost, I get a 404 error.
Am I skipping a step?
Thank you

Hi @gerickt,
Do you config your virtual host?
Virtual Host should be app.gitscrum.dev
https://github.com/gitscrum-community-edition/docker-gitscrum/blob/master/config/server.conf#L3

I've build new schema for docker-gitscrum, based on my docker-framework. PR-6. You will able to run docker-gitscrum on localhost:8081

Hi @zeroc0d3
I meet the problem when run the command ./run.sh
Step 1/11 : FROM bhuisgen/alpine-base:latest
ERROR: Service 'consul' failed to build: pull access denied for bhuisgen/alpine-base, repository does not exist or may require 'docker login'
\033[22;32m====================================================================================\033[0m
\033[22;31m# Finish at: 2018-08-29 14:00:36  \033[0m
\033[22;31m# END PROCESS.....  \033[0m\n
the process stoped, what's wrong?
Thank you

@Monk428, i've change the Dockerfile with new repository from dockerframework...
Could you test it again ?


Assignment 2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Adding codes
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
None
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
It was tested on VScode
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended
Yes

A2: Incomplete
Q2, Q3, Q4 need to be completed

A2: Missing
Solutions are still missing and not in the markdown file

Hello,
I got this response in the first A2 assignment, 'Q2,Q3,Q4 incomplete'.
I updated it and this is the link for the updated one - Updated_assignment2 by Rantitope · Pull Request #3 · Rantitope/applying_statistical_concepts (github.com).
Is this (A2: Missing, Solutions are still missing and not in the markdown file) in response to the updated one?
On Tuesday, October 22, 2024 at 08:13:46 AM EDT, Melokazz @.***> wrote:
A2: Missing
Solutions are still missing and not in the markdown file
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Add Azure account initialization logging

Adding some more logging to help try to track down https://github.com/microsoft/azuredatastudio/issues/11260
User was seeing this error on startup so it looks like something might be wrong with the memento retrieval.
/C:/Users/a/AppData/Local/Programs/Azure Data Studio - Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:2315   ERR e is not iterable: TypeError: e is not iterable
	at p._initialize (c:\Users\a\AppData\Local\Programs\Azure Data Studio - Insiders\resources\app\extensions\azurecore\dist\extension.js:166:32362)
	at p.initialize (c:\Users\a\AppData\Local\Programs\Azure Data Studio - Insiders\resources\app\extensions\azurecore\dist\extension.js:166:32302)
	at c:\Users\a\AppData\Local\Programs\Azure Data Studio - Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:693:948
	at a._withProvider (c:\Users\a\AppData\Local\Programs\Azure Data Studio - Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:696:200)

Pull Request Test Coverage Report for Build 346308335

1 of 2 (50.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0003%) to 40.196%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/azurecore/src/account-provider/azureAccountProvider.ts
0
1
0.0%

Totals

Change from base Build 346304536:
0.0003%

Covered Lines:
21081

Relevant Lines:
48185

💛  - Coveralls


Consider adding a compiler option to not automatically build the inferred type names

TypeScript Version:  2.0.0
I have a project with several environments where js runs and in these environments, different versions of a global require function exist:
Code
{
    "dependencies": {
        "@types/node": "6.0.31",
        "@types/phantomjs":"1.9.26",
        "typescript": "2.0.0"
    }
}

var a;

When I run node_modules\.bin\tsc test.ts, I get
node_modules/@types/node/index.d.ts(69,13): error TS2300: Duplicate identifier 'require'.
node_modules/@types/phantomjs/index.d.ts(6,18): error TS2300: Duplicate identifier 'require'.

and with --traceResolution I can see these errors originate from building the internal __inferred type names__.ts.
I can fix the error by specifying any explicit --types option (but it needs a valid argument), but AFAICS I cannot explicitly turn off building the inferred types. Might be useful.

The root cause is that phantomjs.d.ts needs to not have this line https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/phantomjs/phantomjs.d.ts#L6

and with --traceResolution I can see these errors originate from building the internal inferred type names.ts.
I cannot explicitly turn off building the inferred types. Might be useful.

This isn't really a coherent description of what's going on.
If you don't want the @types/phantomjs package, you can just not install it (?), or you can fix the .d.ts file to not have an incorrect global redefinition of require, or you can manually specify a --types list as you've discovered. Those are the options.

Hmm,

I want phantomjs, because a part of my project requires it (no pun intended)
I want node, because another part of my project requires it
Both packages define a JS environment (phantomjs based on Webkit's engine, node based on V8)
Both have a global 'require' function in their environment, so I assume the .d.ts are correct and the require functions have nothing to do with each other.

Now, TypeScript helpfully (I mean it!) gathers all available @types packages by default and stumbles over the conflict. In that setup, my entire project is "tainted" and I can never go back to the default, so I just want to disable it.

It sounds like you need to split your project into two compilations depending on which environment it's targeting. It can't be the case that two different things are setting up different globals named require at the same time.

You are right, that's why I'm asking for a way to tell TypeScript not to do it :) Because right now, the default handling of @types creates that problem.
But you are right. It's probably the easiest to make a hard cut between these two worlds.

I also met this problem when using @types in conjunction with the typings definition manager:
======== Resolving type reference directive 'validator', containing file '/Users/felix/git/npm-sequelize/__inferred type names__.ts', root directory '/Users/felix/git/npm-sequelize/typings/globals
,/Users/felix/git/npm-sequelize/typings/modules'. ========
Resolving with primary search path '/Users/felix/git/npm-sequelize/typings/globals, /Users/felix/git/npm-sequelize/typings/modules'
Directory '/Users/felix/git/npm-sequelize/typings/globals' does not exist, skipping all lookups in it.
File '/Users/felix/git/npm-sequelize/typings/modules/validator/package.json' does not exist.
File '/Users/felix/git/npm-sequelize/typings/modules/validator/index.d.ts' exist - use it as a name resolution result.
Resolving real path for '/Users/felix/git/npm-sequelize/typings/modules/validator/index.d.ts', result '/Users/felix/git/npm-sequelize/typings/modules/validator/index.d.ts'
======== Type reference directive 'validator' was successfully resolved to '/Users/felix/git/npm-sequelize/typings/modules/validator/index.d.ts', primary: true. ========
node_modules/@types/validator/index.d.ts(318,3): error TS2300: Duplicate identifier 'export='.
typings/modules/validator/index.d.ts(295,1): error TS2300: Duplicate identifier 'export='.

I tried setting types to an empty array, but that doesn't work. I don't know what else I should types to. I just want TypeScript to ignore @types declarations, but not even exclude helps

Do you have typeRoots set?

Yes:
    "typeRoots": [
      "typings/globals",
      "typings/modules"
    ]

can you share a project or a sample?

Yeah, if you take a look here: https://github.com/types/npm-sequelize/tree/v4
Those are typings for sequelize I (as a maintainer of the Sequelize library) have been maintaining for the typings declarations. I got countless requests to make them usable with npm / @types because those on DT are apparently not as complete, but until Microsoft/types-publisher#4 is resolved, I wanted to make it possible to install them with npm from GitHub. For this I added the typings dependencies on bluebird and validator also to package.json dependencies. I added typeRoots for preferring the typings dependencies when running tests in CI, but it seems to get ignored for validator.

The workaround I do is installing dependencies with npm install --only=dev, but that only works for this specific project and is confusing for contributors :/

add:
  "baseUrl": ".",
    "paths": {
        "*": ["typings/modules/*"]
    }

to your tsconfig.json

@mhegazy that works, thanks a lot!

Some due explanation. there are two concepts at play here. global dependencies, and modules. typeRoots manage redirecting globals like node for instance. but module imports go through  a different resolution path, paths is what controls that. so typically you need to do both.


Evaluate Cookiecutter vs Custom CLI Tool for Project Scaffolding

As we prepare to start new projects, we need to determine the best way to scaffold them. We are considering using either Cookiecutter or developing a custom CLI tool.
We need to evaluate and recommend the better option for our specific needs. The preferred choice is cookiecutter, because we dont need to develop a custom solution and dont need to maintain it.
The Scope of this issue is evaluate if cookiecutter fits our needs or if a custom solution is needed.

POC Idea for CLI-Script:
Input the project name -> Change folder names accordingly, package names, pom.xml, package.json

Will be further handled in https://github.com/it-at-m/refarch/issues/88

Closing


Empty callback on start stop delete

Hello,
Actually when i invoke a stop/start/delete on a container, if its good (200) i have a "" callback
docker.delete = function(id, cb) {
    var container = docker.getContainer(id);
    container.remove(function(err, data) {
        if (err) {
            cb(err);
        } else {
            cb(data);
        }
    });
};

Is it a bad use or a bug ?
Thanks

I had the same experience. Guess this is because dockerode follows the API quite strictly, and the API is returning a no-content response in these situations.
For this library, it would be nice to return the container class though, for easier chaining with things like promises

ATM i have added a response, its a sad tweak but better than nothing :
example :
docker.start = function(id,cb) {
	var container = docker.getContainer(id);
	container.start(function(err,data) {
    if (err) {
      cb(err);
    } else {
      cb({id : container.id, statusCode : 200});
    }
	});
};

Yes @LaurensRietveld is right.
https://github.com/apocas/dockerode/blob/master/test/container.js#L111 data is empty in these situations.
It could return something redundant (you already have all the info, since there is no new state).
But then we were going to get in trouble if the API spec changes, it's hard to make everyone happy. So we follow API behaviour.

Oh ok,
I don't ask for change only if the return is normally empty.
So yes (i understand that is no need to change this)
thanks you all (dockerode is freaking good 👍 )


local backtesting reports fail when quote asset is BUSD

My strategy trades BUSD against various cryptos on Binance, backtests run fine, but whenever I try to create a local backtest report using lean report, I get the following error message:
Unhandled exception. System.ArgumentException: The value BUSD480000.00 cannot be converted to a decimal number
   at QuantConnect.Currencies.Parse(String value) in /LeanCloud/CI.Builder/bin/Debug/src/QuantConnect/Lean/Common/Currencies.cs:line 263
   at QuantConnect.Report.ReportElements.EstimatedCapacityReportElement.Render() in
/LeanCloud/CI.Builder/bin/Debug/src/QuantConnect/Lean/Report/ReportElements/EstimatedCapacityReportElement.cs:line 57
   at QuantConnect.Report.Report.Compile(String& html, String& reportStatistics) in /LeanCloud/CI.Builder/bin/Debug/src/QuantConnect/Lean/Report/Report.cs:line
152
   at QuantConnect.Report.Program.Main(String[] args) in /LeanCloud/CI.Builder/bin/Debug/src/QuantConnect/Lean
[1925969574 copy.json.log](https://github.com/QuantConnect/Lean/files/9449936/1925969574.copy.json.log)
/Report/Program.cs:line 77
/lean-cli-start.sh: line 3:     7 Aborted                 dotnet QuantConnect.Report.dll

Report jsons (renamed to logs as this form won't accept JSON attachments):
1925969574-order-events copy.json.log
Same backtest looks find when opened on the web: https://www.quantconnect.com/project/12660086
This is NOT happening when quote currency is USDT.
Expected Behavior
No errors, just report
Actual Behavior
Error (see above) and no report
Potential Solution
A bug needs to be fixed here: https://github.com/QuantConnect/Lean/blob/master/Common/Currencies.cs#L275
Reproducing the Problem

Unzip the archive below into backtests folder and run lean report
2022-08-29_16-08-18.zip
System Information
lean, version 1.0.104, latest docker image
MacOS Monterey
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

@Martin-Molinero ,
Thanks for such a quick response!
Reports generate fine now, but in logs I can see the following:
20220831 11:45:37.073 TRACE:: Failed to assign conversion rates for the following cash: BUSD,ADA. Attempting to request daily resolution history to resolve conversion rate
Even though I have minute data for this pair:
ubuntu@lean:~/lean$ ll data/crypto/binance/minute/adabusd
-rw-rw-r--  1 ubuntu ubuntu 69270 Aug 30 17:50 20210301_trade.zip
-rw-rw-r--  1 ubuntu ubuntu 69339 Aug 30 17:50 20210302_trade.zip
-rw-rw-r--  1 ubuntu ubuntu 68898 Aug 30 17:50 20210303_trade.zip
...
-rw-rw-r--  1 ubuntu ubuntu 63909 Aug 30 17:50 20220826_trade.zip
-rw-rw-r--  1 ubuntu ubuntu 63740 Aug 30 17:50 20220827_trade.zip
-rw-rw-r--  1 ubuntu ubuntu 63482 Aug 30 17:50 20220828_trade.zip
-rw-rw-r--  1 ubuntu ubuntu 63418 Aug 30 17:50 20220829_trade.zip

Relevant strategy piece:
    def Initialize(self):
        self.SetTimeZone("UTC+07:00")
        self.SetStartDate(2021, 3, 2)  # Set Start Date
        self.SetEndDate(2022, 3, 1)  # Set End Date
        self.SetCash("BUSD", 100000)
        # self.SetCash(1000)  # Set Strategy Cash
        self.SetBrokerageModel(BrokerageName.Binance, AccountType.Margin)
        self.SetBenchmark(Symbol.Create("BTCBUSD", SecurityType.Crypto, Market.Binance))
        self.crypto = self.AddCrypto(
            "ADABUSD", Resolution.Minute, Market.Binance
        ).Symbol

Full log:
20220831 11:45:36.033 TRACE:: QuantConnect.Report.Main(): Parsing source files...backtest-data-source-file.json,
20220831 11:45:36.363 TRACE:: QuantConnect.Report.Main(): Instantiating report...
20220831 11:45:36.395 TRACE:: QuantConnect.Report.Report(): Processing backtesting orders
20220831 11:45:36.422 TRACE:: Config.Get(): Configuration key not found. Key: plugin-directory - Using default value:
20220831 11:45:36.426 TRACE:: Config.Get(): Configuration key not found. Key: composer-dll-directory - Using default value:
20220831 11:45:36.429 TRACE:: Composer(): Loading Assemblies from /Lean/Report/bin/Debug/
20220831 11:45:36.568 TRACE:: Config.GetValue(): api-data-update-period - Using default value: 1
20220831 11:45:36.573 TRACE:: Config.Get(): Configuration key not found. Key: data-directory - Using default value: ../../../Data/
20220831 11:45:36.574 TRACE:: Config.Get(): Configuration key not found. Key: version-id - Using default value:
20220831 11:45:36.574 TRACE:: Config.Get(): Configuration key not found. Key: cache-location - Using default value: /Lean/Data
20220831 11:45:36.867 TRACE:: Config.GetValue(): scheduled-event-leaky-bucket-capacity - Using default value: 120
20220831 11:45:36.867 TRACE:: Config.GetValue(): scheduled-event-leaky-bucket-time-interval-minutes - Using default value: 1440
20220831 11:45:36.867 TRACE:: Config.GetValue(): scheduled-event-leaky-bucket-refill-amount - Using default value: 18
20220831 11:45:36.878 TRACE:: Config.Get(): Configuration key not found. Key: results-destination-folder - Using default value: /Lean/Report/bin/Debug
20220831 11:45:36.948 TRACE:: DataManager.AddSubscription(): Unable to add subscription for:
QC-UNIVERSE-USERDEFINED-BINANCE-CRYPTO,#0,QC-UNIVERSE-USERDEFINED-BINANCE-CRYPTO,Daily,TradeBar,Trade,Adjusted,OpenInterest,Internal
20220831 11:45:36.960 TRACE:: BacktestingResultHandler(): Sample Period Set: 36.72
20220831 11:45:36.961 TRACE:: Time.TradeableDates(): Security Count: 1
20220831 11:45:36.968 TRACE:: Config.GetValue(): forward-console-messages - Using default value: True
20220831 11:45:37.062 TRACE:: Config.GetValue(): show-missing-data-logs - Using default value: False
20220831 11:45:37.073 TRACE:: Failed to assign conversion rates for the following cash: BUSD,ADA. Attempting to request daily resolution history to resolve conversion rate
20220831 11:45:37.076 TRACE:: BaseSetupHandler.SetupCurrencyConversions():
Account Type: Margin

Symbol      Quantity    Conversion = Value in USD
BUSD: BUSD           0.00 @       0.00 = $0
ADA: ₳           0.00 @       0.00 = $0
USD: $      200000.00 @       1.00 = $200000.0
-------------------------------------------------
CashBook Total Value:                $200000.0

20220831 11:45:37.100 TRACE:: BacktestingResultHandler.Exit(): starting...
20220831 11:45:37.114 TRACE:: BacktestingResultHandler.Exit(): Saving logs...
20220831 11:45:37.128 TRACE:: Debug: Your log was successfully created and can be retrieved from: /Lean/Report/bin/Debug/2f46cae1d2474841a50f13b7b70056f7-log.txt
20220831 11:45:37.128 TRACE:: BacktestingResultHandler.Run(): Ending Thread...
20220831 11:45:37.128 TRACE:: StopSafely(): waiting for 'Result Thread' thread to stop...

p.s. I fetch & generate my own data streams, but from the log it's not clear whether minute data is sufficient or daily data is also required?

Just found out about VERY useful setting "show-missing-data-logs":true for project/config.json, and after enabling it, I can see what data is missing, will fetch it now and try backtesting / reporting again. But please consider changing default for this setting to true. For beginners there never can be too much logging, especially for such complex tool as LEAN.


Intergration with https://coveralls.io/ for coverage

Describe the feature you'd like to have
What new functionality do you want?
Have a link to https://coveralls.io/ and a badge in readme for test coverage in the project.
What is the value to the end user? (why is it a priority?)
Having a coverage report will enable new developers to contribute easy tests. The end user in this case is developer.

@raghavendra-talur is this something related to UT?

As we dont have much UT coverage and we have more of Functional test coverage am closing this one for now, please reopen later if requried.


computedFrom and computedAsync have been renamed without a major version bump

Recently (in version 2.3.0), both computedFrom and computedAsync have been renamed respectively to derivedFrom and derivedAsync (via the PR #303).
I believe it should have been published as a major version (3.0.0) because it is a breaking change from the previous version 2.2.1
I know that a migration schematics has been released with the change to allow to update the code automatically but, nevertheless, I don't think it is sufficient to not bump the version to 3.0.0
I have a library that uses the computedAsync function and reference ngxtension package with the version range ^2.2.1 which includes 2.3.0. When I updated the library in my project the build and tests failed because the ngxtension/computed-from entry point does not exist anymore.

Hello @FabienDehopre
Thanks for this issue.
I believe this https://github.com/ngxtension/ngxtension-platform/pull/342 should fix the issue.

Hello @FabienDehopre
We released a new patch https://github.com/ngxtension/ngxtension-platform/releases/tag/2.3.1 where we deprecate the functions which should solve the issue and also released a new major (v3.0.1) which removes the deprecated and fixes also the ng-update migrations.
Thanks for opening this issue.
Closing it now as it's complete.


[Dendrite] Polylith ingress and config fixes

Description of the change

Add an ingress configuration with correct routing for each polylith service.
Benefits

Reduces the toil in getting a polylith setup ready to go.
Possible drawbacks

Config fixes may be breaking, although unlikely to be honest.
Applicable issues

closes #1600

Additional information

Checklist

[x] Title of the PR starts with chart name (e.g. [home-assistant])
[x] Chart version bumped in Chart.yaml according to semver.
[x] Chart artifacthub.io/changes changelog annotation has been updated in Chart.yaml. See Artifact Hub documentation for more info.
[x] Variables have been documented in the values.yaml file.

Wow, nice work @onedr0p - thank you for this ;)
Could i ask for setting the .well-known/matrix/{server,client}


Back button not reloading controller

I created one angular application and used UI router.From my app need to redirect to some other website.But am getting this problem : -
Step 1: From my ui-router app to another website i was redirected.
Step 2: If i click back button from that website it will redirect to my UI-router app.
Problem is : It is not loading my controller on landing to my ui-router page.It is retaining my previous state instead of reloading it.

Why should it reload instead of retain? You are going back, not reloading the page

No.Actually think it in this way,That is a confirmation page.If user clicks on back button then i should redirect them from instead landing into confirmation page to main page right,For that at least my controller should load for that particular state.But In firefox and safari it is not loading,But in chrome it is loading that state.

Don't do the confirmation page as a state then and instead consider something like a modal

This sounds more like a usage issue - the library itself should not reload the controller, that is huge wasteful sudden processing. This would compound when the user quickly hits back on the browser to get to the particular view he/she wants. In addition, there would be no clean way to get to this proposed change that is not a large breaking change for other users of the library.
I would highly recommend structuring the application more appropriately for handling how the view is presented to the user when the user hits back. This puts less processing pressure, as well as avoids a major change in expected behavior with the library.


EAS Build failing iOS production builds

Build/Submit details page URL
https://expo.dev/accounts/quantoz/projects/qbs-test-app/builds/fbf0460d-bf13-410d-8f73-3d1fcd5d1a15
Summary
Note: the Android app builds correctly with this config, it's an iOS issue
The iOS production build fails with the following:
Configuring Xcode project

Assigning provisioning profile '*[expo] com.*******.*** AppStore 2023-03-27T09:36:37.150Z' (Apple Team ID: --------) to target 'AppName'

Could not find target 'AppName' in project.pbxproj

Some context:
After upgrading to Expo SDK 49, I have refactored my project to use different env files, per environment and also whether it has to be used locally or for builds. I have the following:

.env.development.local
.env.production.local (to test prod setup locally if needed)
.env.local (shared stuff between them)

I used eas secret to upload the latter two in order to be used also for builds, since they contain secrets I don't want in my repo.
I just added two more env files:

.env.development
.env.production

These are uploaded to the repo, and they contain info on package name, app name... Note: the app name is exactly the same as before
My eas.json:
{
  "cli": {
    "version": ">= 2.2.1",
    "appVersionSource": "remote"
  },
  "build": {
    "development": {
      "channel": "development",
      "developmentClient": true,
      "distribution": "internal",
      "ios": {
        "simulator": true
      },
      "env": {
        "APP_ENV": "development",
        "APP_NAME": "Dev App Name",
        "IOS_BUNDLE_IDENTIFIER": "com.company.app.dev",
        "ANDROID_PACKAGE_NAME": "com.company.app.dev",
        "SCHEME": "quantoz.qbs.dev"
      }
    },
    "production": {
      "autoIncrement": true,
      "channel":"test",
      "distribution": "store",
      "env": {
        "APP_ENV": "production",
        "APP_NAME": "App Name",
        "IOS_BUNDLE_IDENTIFIER": "com.company.app",
        "ANDROID_PACKAGE_NAME": "com.company.app",
        "SCHEME": "company.app"
      }
    }
  },
  "submit": {
    "test": {
      "android": {
        "serviceAccountKeyPath": "./google-service-account.json",
        "track": "internal"
      },
      "ios": {
        "ascAppId": "XXXXXXXXXX"
      }
    }
  }
}

app.config.ts:
const AppConfig = {
  name: process.env.APP_NAME,
  icon: "./assets/icon-qbs.png",
  image: "./assets/splash-qbs.png",
  ios: {
    // from .env.production
    bundleIdentifier: process.env.IOS_BUNDLE_IDENTIFIER,
  },
  android: {
    adaptiveIcon: {
      foregroundImage: "./assets/adaptive-icon-qbs.png",
    },
    // from .env.production
    package: process.env.ANDROID_PACKAGE_NAME,
  },
  extra: {
    // from EAS Secrets
    POSTMAN_MOCK_API_KEY: process.env.POSTMAN_MOCK_API_KEY,
    POSTMAN_MOCK_API_URL: process.env.POSTMAN_MOCK_API_URL,
    API_URL: process.env.API_URL,
    ...
    APP_ENV: process.env.APP_ENV || null,
    ...
  },
};

export default () => ({
  expo: {
    name: AppConfig.name,
    slug: "app-slug-here",
    version: "1.0.0",
    orientation: "portrait",
    icon: AppConfig.icon,
    userInterfaceStyle: "light",

    splash: {
      image: "./assets/splash-qbs.png",
      resizeMode: "contain",
      backgroundColor: "#ffffff",
    },
    updates: {
      fallbackToCacheTimeout: 1500,
      url: "https://u.expo.dev/508103fd-4d90-4213-98d1-045bdcd043b5",
    },
    assetBundlePatterns: ["**/*"],
    ios: {
      bundleIdentifier: AppConfig.ios.bundleIdentifier,
      infoPlist: {
        NSCameraUsageDescription:
          "This app uses the camera to take photos of your documents, in order to upgrade to a higher tier.",
        NSFaceIDUsageDescription:
          "FaceID is used to authenticate you and to access your account",
      },
    },
    android: {
      adaptiveIcon: {
        foregroundImage: AppConfig.android.adaptiveIcon.foregroundImage,
        backgroundColor: "#FFFFFF",
      },
      package: AppConfig.android.package,
    },
    owner: "company",
    web: {
      favicon: "./assets/favicon.png",
    },
    extra: {
      eas: {
        projectId: "508103fd-4d90-4213-98d1-045bdcd043b5",
      },
      ...AppConfig.extra,
    },
    plugins: [
      "sentry-expo",
      [
        "expo-image-picker",
        {
          photosPermission:
            "The app accesses your photos to let you upload the necessary documentation.",
        },
      ],
    ],
    scheme: process.env.SCHEME,
    platforms: ["ios", "android"],
    runtimeVersion: {
      policy: "sdkVersion",
    },
    hooks: {
      postPublish: [
        {
          file: "sentry-expo/upload-sourcemaps",
          config: {
            organization: process.env.SENTRY_ORG,
            project: process.env.SENTRY_PROJECT,
          },
        },
      ],
    },
  },
});

Managed or bare?
Managed
Environment
expo-env-info 1.0.5 environment info:
    System:
      OS: macOS 13.1
      Shell: 5.8.1 - /bin/zsh
    Binaries:
      Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
      Yarn: 1.22.15 - ~/.nvm/versions/node/v16.15.0/bin/yarn
      npm: 8.5.5 - ~/.nvm/versions/node/v16.15.0/bin/npm
      Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
    Managers:
      CocoaPods: 1.12.1 - /opt/homebrew/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
    IDEs:
      Android Studio: 2021.3 AI-213.7172.25.2113.9123335
      Xcode: 14.3/14E222b - /usr/bin/xcodebuild
    npmPackages:
      @expo/metro-config: ^0.10.7 => 0.10.7
      expo: ^49.0.10 => 49.0.10
      react: 18.2.0 => 18.2.0
      react-dom: 18.2.0 => 18.2.0
      react-native: 0.72.4 => 0.72.4
    npmGlobalPackages:
      eas-cli: 5.2.0
      expo-cli: 6.3.9
    Expo Workflow: managed

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✖ Check that native modules use compatible support package versions for installed Expo SDK
✖ Check that packages match versions required by installed Expo SDK

Detailed check results:

Expected package<EMAIL_ADDRESS>Found invalid:
<EMAIL_ADDRESS>  (for more info, run: npm why @expo/config-plugins)
Advice: Upgrade dependencies that are using the invalid package versions.

Some dependencies are incompatible with the installed expo version:
<EMAIL_ADDRESS>- expected version: ~2.4.10
<EMAIL_ADDRESS>- expected version: ~0.18.13
Your project may not work correctly until you install the correct versions of the packages.
Fix with: npx expo install --fix
Found outdated dependencies
Advice: Use 'npx expo install --check' to review and upgrade your dependencies.

One or more checks failed, indicating possible issues with the project.

Error output
Configuring Xcode project

Assigning provisioning profile '*[expo] com.*******.*** AppStore 2023-03-27T09:36:37.150Z' (Apple Team ID: --------) to target 'AppName'

Could not find target 'AppName' in project.pbxproj

Reproducible demo or steps to reproduce from a blank project
Not easy to do so, but I provided my whole config and can provide more

hi there! I would recommend fixing the doctor warning about the config plugins version misalignment. that may be related.
in general, this guide is a useful place to go for troubleshooting these issues: https://docs.expo.dev/build-reference/troubleshooting/
if you're still stuck after that, there are some tips on the bottom of the guide for getting further help

I solved it, my issue was the way in which I handled some env variables. I was using the EXPO_PUBLIC prefix and somehow removing it made it work, when using them inside the app.config.ts file


SwiftShims: update shims copying logic

Update the shims logic to make sure that it works for Xcode as well.
Rather than adding additional rules, just simplify it down to the one
canonical way in modern LLVM land.  The headers are always installed to
the LLVM_LIBRARY_OUTPUT_INTDIR which will be defined for us in both the
standalone and unified build mode.  This allows us to just remove all
the work to find the headers since they will always be in one location.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

preset=buildbot_incremental,tools=RA,stdlib=RA,xcode
@swift-ci please test with preset macOS

preset=buildbot_incremental,tools=RA,stdlib=RA,xcode
@swift-ci please test with preset macOS

@swift-ci please smoke test

@swift-ci please test Linux platform

CC: @davezarzycki @gwynne


Add dayformat filter, bump version

Add dayformat template filter
Forgot to do this earlier.  Gives the templates a 'DD Month' display date filter (for example '27 August').
and version bump to 6.5.2

:+1:


sat-api implementation status and lessons learned

I've got a new version of sat-api up and running at http://sat-api.developmentseed.org which includes Landsat-8 and Sentinel-2 data on AWS.  Not all the records are ingested yet, but by tomorrow night it should contain all of the landsat-8 and sentinel-2 data, around 5.5 million scenes.
sat-api a partial implementation of STAC 0.4.1 and includes the EO and Collections extensions.  Below are notes on my specific sat-api implementation, as well as questions and issues that came up about the STAC spec. Of particular note is the section on Collections below, which details how the search is able to search items by using metadata from both it and the collections they are part of.
If you don't have a JSON viewer browser plugin I suggest you install one, it will format the JSON to be readabale and will automatically make links from URLs.
sat-api endpoints
There is no documenation endpoint ATM (I could use suggestions or help with how best to creaate that), but there are two endpoints, one for collections and one for items. items and collections have a collection property which is the name of the collection, and items also have a link in the links section to the collection.
/collections: Can search on any field in the collection, e.g. https://sat-api.developmentseed.org/collections?collection=landsat-8
/search/stac: Can search on any field that appears in Items or the Collections those items link to. More on that below.
It's a little weird because both endpoints are search endpoints.  /search/stac was to be compliant with WFS3, but /items here would make more sense or an equivalent /search endpoint for collections.
Departures from STAC spec
Here is a list of things that are different between the sat-api implemenation and the STAC spec.

Not yet implemented bbox for searching. However, it does accept the more useful 'intersects' term for searches based on polygons
'collection_name' is now just 'collection'
No more CRS field, instead there is an 'eo:epsg' field. It is currently ommitted from Landsat, but is included for Sentinel
datetime field, not 'time' (some parts of the spec I think still refer to just 'time')
ISO 8601 is not implemented for date searches, so period strings are not accepted, however single datetimes, partial or full, work, as do date ranges specified with a slash, e.g., 2017-08-01/2017-08-31
The spec does not currently have specifics on how ranges should be specified for other fields. For now I used the slash notation, but think the spec should specify using separate gt and lt filters.  e.g. eo:cloud_cover=0/20 for cloud cover between 0 and 20%
The assets are currently barebones, I did not add additional fields such as descriptions, filetype, etc.

Not all fields are included for both landsat and sentinel. Landsat does not have an eo:epsg code, sentinel does not have viewing azimuth (eo:azimuth) or sun angle information (eo:sun_azimuth, eo:sun_elevation)
Links
Assets use a dictionary structure with a key. It feels like links should follow the same structure and instead of a 'rel' field, make it a key, e.g.
links = {
    "self": {"href": ...url...}
}

Also I couldn't decide whether or not provider supplied metadata files were an asset or a link. I currently made them assets (under the metadata key), but it might make more sense as a link.
Collections
The most challenging aspect of the API ended up being handling the concept of collections as presented in the Collections extension. Collections can include any abitrary fields that were part of an item, and that would apply to all STAC items in that collection (specified through the collection field). So, for landsat-8 we can specify eo:platform as "landsat-8" and it applies to all items in the landsat-8 collection.
The challenge was how to implement this using elasticsearch, because you don't actually know what fields are in the item and which are in the collection (stored in two different indices in elasticsearch).  If the field is present in one it will be missing in the other, and by default missing fields do not match. So if you search items for eo:platform and that field is in an items collection, it will not be matched.
So instead /search/stac takes a two step approach and in each it allows for missing fields.
1 - Search the collections index, but allow for either a match or a missing field. This ends up returning all collections for which each of the search fields is either a match or the field is missing. The exception to this is geometry. The geometry search in elasticsearch is a bit more complicated so for now I removed it when searching collections. So at this time, sat-api does not support geometry in collections, only items.
2 - With the list of matched collections, add these to the item search. Therefore any matched collection will now return all items that are part of it, further filtered by the additional fields. Again, a missing field is considered a match, because it is presumed to have been in the collection.
Overall this approach works well, however allowing missing fields to match does create a side effect which is both a feature and a bug. The issue comes in when a search field is missing from both the collection and the item, because this will stil return a match.

On one hand this is a feature, because it allows you to search on terms only in one collection and have that filter only apply to items in that collection.  For example we can search for landsat and sentinel imagery in an area and daterange, but also further filter landsat based on path or row (e.g., landsat:row, landsat:path) and filter sentinel also based on the MGRS grid designation. Note that I currently do not have collection-specific metadata in sat-api, but will add them as they are found useful

On the other hand this is a bug as you can search for non-existent terms by accident, for example searching for cloud_cover=0/10 instead of eo:cloud_cover=0/10. This may lead a user to think they are getting mostly cloud free imagery when they are not due to a typo.

The benefits outweigh the problem I think, and we could fix the problem other ways by validating search terms against the spec.  Also, this approach still works fine when an item has no collection, since those items will have a missing collection field.
Please feel free to test out sat-api and point out any problems, or jump into the repo and take a look at open tickets if you want to contribute!
https://github.com/sat-utils/sat-api

Regarding links:

I think the structure originates from the REST/Hypermedia principles and is somehow standardized in the HTTP specification (e.g. RFC 2068, chapter <IP_ADDRESS>). It's also how it is used in XML/HTML (). What you suggest sounds much like HAL. Whatever is chosen, it should be consistent across the whole spec.
I had the same confusion about the meta data references: links or assets? @hgs-msmith once suggested me in the chat to add them to the assets.

Regarding endpoints:

I agree that the endpoints are somehow inconsistently named and I must say that I really don't like the WFS-like naming of /search/stac. It just doesn't feel right in resource-oriented REST interfaces. I'd also expect it at /collections and /items (or similar names). If you'd follow REST you'd have to remove /stac completely. Content negotiation with aan Accept header would be the correct way to get a STAC response, I think.

Awesome work Matt. Thanks for getting real world implementation and helping evolve the spec. Psyched for the next iterations.
Regarding links:

For links, yeah, consistency across links and assets makes sense. Wish we'd thought of that at the last revision. And yes, I agree with @hgs-msmith that metadata should go in assets. I see assets are the things that a user would likely want to download, and links describing relationships with other online entities. I can see how the line is blurry, and I could see if there's a great html metadata that you don't download then using a like rel=describedBy could make good sense. But I feel like most imagery still has metadata as xml or text files.

Regarding endpoints:

I don't love the STAC in the resource either. But I do think we should make something that is compatible with WFS. I'm not sure if /search/stac is the best way - that was a request from the WFS people, but they don't have a clear search endpoint.

Though I'm not sure I understand https://sat-api.developmentseed.org/collections?collection=landsat-8 - seems like it should be https://sat-api.developmentseed.org/collections/landsat-8 And then https://sat-api.developmentseed.org/collections/landsat-8/items which enables basic single collection search. The idea with the /search endpoint is that it allows cross collection search. Those resources make sense to me a /search endpoint to do more complex searches, and individual collections under collections/{collection-name}/
Regarding CRS

Would be good to get the CRS field changed asap, I found myself not using it, and doing epsg. Maybe make an issue or PR on that specifically?

Regarding ranges:

I'm +1 on specifying these more, have no real opinions though.

What's the state of this issue?


Remote Extension host terminated unexpectedly 3 times, Error: EEXIST: file already exists, open '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock'

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:

Version: 1.86.0
Commit: 05047486b6df5eb8d44b2ecd70ea3bdf775fd937
Date: 2024-01-31T10:29:15.765Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 23.2.0

OS Version:

macOS Sonoma 14.2.1
2GHz quad core Intel Core i5

Steps to Reproduce:

select Dev Containers: Reopen in Container on command pallet.
Remote Extension host terminated unexpectedly 3 times within the last 5 minutes. is displayed.
The following is logged in the OUTPUT of the extended host (remote).

2024-02-03 10:37:36.231 [info] Extension host with pid 305 started
2024-02-03 10:37:36.704 [info] Lock '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock': Lock acquired.
2024-02-03 10:37:36.909 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2024-02-03 10:37:36.912 [info] ExtensionService#_doActivateExtension vscode.tunnel-forwarding, startup: false, activationEvent: 'onTunnel'
2024-02-03 10:37:36.914 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-02-03 10:37:36.915 [info] ExtensionService#_doActivateExtension vscode.typescript-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-02-03 10:37:38.190 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2024-02-03 10:37:39.008 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2024-02-03 10:37:39.008 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2024-02-03 10:37:40.389 [info] Eager extensions activated
2024-02-03 10:37:40.394 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2024-02-03 10:37:40.398 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2024-02-03 10:38:04.850 [info] Extension host with pid 527 started
2024-02-03 10:38:04.850 [error] Error: EEXIST: file already exists, open '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock'
2024-02-03 10:38:04.871 [info] Lock '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock': Could not acquire lock, checking if the file is stale.
2024-02-03 10:38:04.891 [info] Lock '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock': The pid 305 appears to be gone.
2024-02-03 10:38:04.891 [info] Lock '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock': Deleting a stale lock.
2024-02-03 10:38:04.929 [info] Lock '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock': Lock acquired.
2024-02-03 10:38:05.144 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2024-02-03 10:38:05.146 [info] ExtensionService#_doActivateExtension vscode.tunnel-forwarding, startup: false, activationEvent: 'onTunnel'
2024-02-03 10:38:05.147 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-02-03 10:38:05.147 [info] ExtensionService#_doActivateExtension vscode.typescript-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-02-03 10:38:05.148 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: false, activationEvent: 'onFileSystem:git', root cause: vscode.git
2024-02-03 10:38:05.892 [info] ExtensionService#_doActivateExtension vscode.git, startup: false, activationEvent: 'onFileSystem:git'
2024-02-03 10:38:06.176 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2024-02-03 10:38:06.721 [info] Eager extensions activated
2024-02-03 10:38:06.721 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2024-02-03 10:38:06.721 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2024-02-03 10:38:25.066 [info] Extension host with pid 655 started
2024-02-03 10:38:25.066 [error] Error: EEXIST: file already exists, open '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock'
2024-02-03 10:38:25.085 [info] Lock '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock': Could not acquire lock, checking if the file is stale.
2024-02-03 10:38:25.095 [info] Lock '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock': The pid 527 appears to be gone.
2024-02-03 10:38:25.095 [info] Lock '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock': Deleting a stale lock.
2024-02-03 10:38:25.241 [info] Lock '/root/.vscode-server/data/User/workspaceStorage/7532fcd6ef6afd0a168dfb6ebfbbbbc0/vscode.lock': Lock acquired.
2024-02-03 10:38:25.285 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2024-02-03 10:38:25.287 [info] ExtensionService#_doActivateExtension vscode.tunnel-forwarding, startup: false, activationEvent: 'onTunnel'
2024-02-03 10:38:25.288 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-02-03 10:38:25.289 [info] ExtensionService#_doActivateExtension vscode.typescript-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-02-03 10:38:25.290 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: false, activationEvent: 'onFileSystem:git', root cause: vscode.git
2024-02-03 10:38:25.787 [info] ExtensionService#_doActivateExtension vscode.git, startup: false, activationEvent: 'onFileSystem:git'
2024-02-03 10:38:26.307 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2024-02-03 10:38:26.528 [info] Eager extensions activated
2024-02-03 10:38:26.529 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2024-02-03 10:38:26.530 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'

I add more info.
Dev Containers
v0.338.1

Docker Desktop 4.27.1

Referring to this following issue, I changed the Docker Desktop setting from VirtioFS to gRPC FUSE and unchecked Use Virtualization framework, and this phenomenon did not occur anymore. However, the CPU consumption has increased considerably, probably because the Virtualization framework is no longer used. If possible, I hope that this problem will not occur when using the Virtualization framework.
https://github.com/microsoft/vscode/issues/195906


fix: coalesce schema issues

Which issue does this PR close?
Closes #12307.
Are these changes tested?
Yes
Are there any user-facing changes?
No

Thanks @mesejo and @alamb @findepi @andygrove for the review


Fix quickstart docs regarding scaling

Signed-off-by: Frank Mueller<EMAIL_ADDRESS>What this PR does / why we need it:
Fixing changed naming conventions for worker pools in the quickstart documents.
Which issue(s) this PR fixes
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

/assign @kron4eg

/retest


Renames the version on the repository to dev

This will help with differentiating bug reports

we should actually move it to 1.1.3 too.


Handroll Jwk class

eject from nimbusds JWK and stop exposing their type through our web5 api surface

dupe of #266


Build: Mark a build as a "reference" build (flag)

The idea is to have one reference build on an atomizer, so user can instantly create working build. Also there could be a feature to rate aromas/liquids on this reference build.
The question is: one reference build? One per draw type? One per atomizer? This should be extremely simple to do (on user side).

Reference build can be exactly one per user as idea is those "power users" know which atomizer they like to see how a liquid tastes. But still think about it.


Fix minor typo in constants.js

For #

Background

Change List

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


Documentation/project-layout.md should be replaced by package documentation.

The documentation https://github.com/coreos/torus/blob/master/Documentation/project-layout.md should be moved to package documentation, eg.
// blockset provides an implementation of the BlockSet interface.
package blockset

Then the documentation shows up on godoc automagically and you don't have to keep a markdown file up to date as you move code around.

One problem we had is that godoc is not discoverable on github. And most people will search on github. We should probably add doc.go but we probably should not remove the layout.md.

Thanks
On Fri, 3 Jun 2016, 02:28 Xiang Li<EMAIL_ADDRESS>wrote:

One problem we had is that godoc is not discoverable on github. And most
people will search on github. We should probably add doc.go but we probably
should not remove the layout.md.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/coreos/torus/issues/194#issuecomment-223346080, or mute
the thread
https://github.com/notifications/unsubscribe/AAAcA5J1yjtvfm7wTy90gEE6gkEG6_Uaks5qHwSogaJpZM4IsQv1
.


MultiDex fails to identify and split method count slighly above 65,536 (for example 65,620)

Current findings:
Works in a sample project with lots of dependencies (but not to any of our plugins)
Doesn't work in a sample project with the same dependencies as posted below.
Does work in a sample project with the same dependencies + "nativescript-telerik-ui": "next", "nativescript-platform-css": "^1.0.1", "nativescript-loading-indicator": "^2.2.1", and HockeyApp SDK
After fixing it locally for @next with @angular 2.1.2 (by adding the above mentioned dependencies) I tried to do the same on our NS 2.3 branch and when I build there I now get Cannot merge new index 65635 into 'non-jumbo' construction
Suspicion:
Dex merger fails to identify and split if there are just slightly more methods than 65,536 (for example 65,620) but works if there are more, at least that's what I could conclude from the testing.
Can we somehow verify this? Is this by any mean inspectable (the multidex split step)?
Did you verify this is a real problem by searching Stack Overflow and the other open issues in this repo?
Yes, but haven't found anything related to MultiDex not working at all
Tell us about the problem
After updating from NativeScript 2.3 to @next version and also updating @angular from 2.0.0/3.0.0 to 2.1.2/3.1.2 and nativescript-angular to 1.1.2 we started seeing Cannot merge new index 65721 into a 'non-jumbo' construction (number is just an example) error.
So far so good. So we started looking out for MultiDex and checked the sample repository (https://github.com/NativeScript/sample-Android-Multidex) and documentation (https://docs.nativescript.org/runtimes/android/advanced-topics/extend-application-activity).
The sample project works and creates multiple classes{number}.dex files and so we tried to take that approach but that didn't work at all.
After several different solution attempts we added
multiDexEnabled true to the defaultConfig in app.gradle and compile "com.android.support:multidex:1.0.1" in the dependencies section
When Android 7.0 (API 24) SDK is installed this did not help at all and the error is always present.
With Android 6.0 (API 23) SDK installed the error went away, but wait there's still just one classes{number}.dex and not multiple ones as expected.
And if I add another plugin, for example https://github.com/naderio/nativescript-google-maps-util in order to add clustering, the error appears again even though multiDex is enabled.
Please provide the following version numbers that your issue occurs with:

CLI: @next 2.5.0
Cross-platform modules: 2.5.0 (2016-11-02-4652)
Runtime(s): @next (2.5.0)
Plugin(s):   "dependencies": {
"@angular/common": "2.1.2",
"@angular/compiler": "2.1.2",
"@angular/core": "2.1.2",
"@angular/http": "2.1.2",
"@angular/platform-browser": "2.1.2",
"@angular/platform-browser-dynamic": "2.1.2",
"@angular/router": "3.1.2",
"@ourCompany/api": "^2.0.0",
"@ourCompany/nativescript-ng2-translate": "^2.1.1",
"@ourCompany/nativescript-plugin-firebase": "^3.6.3",
"@ourCompany/ns-ecdsa": "^1.0.1",
"@ourCompany/ns-google-maps": "^1.2.4",
"@ourCompany/ns-keystore": "^1.0.1",
"nativescript-angular": "1.1.2",
"nativescript-theme-core": "^0.1.3",
"nativescript-barcodescanner": "^1.4.1",
"nativescript-calendar": "^1.1.3",
"nativescript-drop-down": "^1.3.3",
"nativescript-geolocation": "0.0.14",
"nativescript-slides": "2.2.1",
"nativescript-timedatepicker": "^1.0.0",
"nativescript-unit-test-runner": "^0.3.3",
"ng2-translate": "2.4.4",
"rxjs": "5.0.0-beta.12",
"tns-core-modules": "next"
},
"devDependencies": {
"babel-traverse": "^6.18.0",
"babel-types": "^6.18.0",
"babylon": "^6.13.1",
"jasmine-core": "^2.5.2",
"karma": "^1.3.0",
"karma-jasmine": "^1.0.2",
"karma-junit-reporter": "^1.1.0",
"karma-nativescript-launcher": "^0.4.0",
"lazy": "^1.0.11",
"nativescript-dev-sass": "^0.4.0",
"nativescript-dev-typescript": "^0.3.2",
"nativescript-dev-webpack": "0.0.20",
"sharp": "^0.16.2",
"typescript": "^2.0.6",
"typings": "^1.5.0"
},

SDK Build Tools: 24.0.3
Always happens when Android 7.0 (API 24) SDK is installed
If latest installed SDK Platform is 6.0 (23) it partially works (no error, but multidex didn't do anything) and breaks when a new plugin is added
Did the error happen while the app was being constructed? (buildtime error)
Yes, see attached log at the bottom
Did the error happen while the app was executing? (runtime error)
Nope, build time
Please tell us how to recreate the issue in as much detail as possible.
NS + NG2 project with dependencies on google play services (maps, firebase and more).
I can't share our project due to client specific stuff that is in their.
I'm trying to create a repository/project which can be checked out where MultiDex doesn't work now.
Build Log: (search for myMergeDex)
http://pastebin.com/raw/N1ngdkaF

I've wrote down my findings and suspicion on what it could be.
If I can help any further I'll gladly do that. Unfortunately I don't think I can share a sample project with plugin dependencies to our npm repository but I'll clarify.
Do you have any idea if my suspicion could be right?

Hi @creambyemute
Thanks for providing the error log. I have a guess that you hit a corner case of our *.dex merging logic. The current implementation uses somewhat a naive heuristics which is not guaranteed to work in all cases. I would suggest to find this line in <your project>/platforms/android/build.gradle file and change it as follows
def shouldMergeInMainDex = false

Please let us know if this workaround solves the issue.

Hey @slavchev Thanks for your suggestion. That indeed worked, created an .apk with multiple classes.dex files (two atm) inside it and I could successfully run it on a device.
Do you already have a plan on how to proceed on this one? I'm mainly asking because we already have a copy of the build.gradle in our app/App_Resources/Android and we will for the moment probably change it and commit it to the source control but we'd like to know if we have to change it at some point again?
Cheers!

Hey @creambyemute

Do you already have a plan on how to proceed on this one?

We will fix the issue though I am not sure if the fix will be shipped with 2.4 release which is due in 9 days. One possible solution could be:

set multidex support by default (multiDexEnabled true)
always merge *.dex binding into a new *.dex file

This will require us to change the project template to use android.support.multidex.MultiDex which is a breaking change and should be carefully considered.
Another option could be making <project>/platforms/android/build.gradle part of project structure which is subject to source control so that it can be edited according the project requirements. We can use <project>/app/App_Resources/Android directory or reuse app.gradle inside it.

@slavchev As a side note to option2:
If you'd go with the second option (put build.gradle in <project>/app/App_Resources/Android or reuse app.gradle) and include multiDexEnabled true in there (maybe commented out) I'd recommend adding another comment like If you experience dex merging problems check the 'shouldMergeInMainDex' definition in the build.gradle and try setting it to false
Though I probably would rather place it in app.gradle than in build.gradle as the build.gradle may change over time (which was the case for me when I upgraded from 2.3 to @next).
Then you'd probably have to add again another comment in the app.gradle telling the user he should make sure he's using the latest build.gradle which is included in /platforms/Android if he copied it to app/App_Resources/Android.

Because we're not generating dex files anymore, the android tool chain takes care of this problem for us.


[Bugs] PDU session cannot be established if DNN contains a period(.)

Describe the bug
DNNs are stored into MongoDB as keys of documents in some collections, for example,
"db.subscriptionData.provisionedData.smData" and "db.policyData.ues.smData".
MongoDB query API treats a period(.) in the query key as a delimiter of nested documents.
So that, NFs cannot get data from MongoDB if DNN as a query key contains a period.
As a result, PDU session cannot be established with such DNN.
To Reproduce

Set DNN which contains a period like "example.net" into smfcfg.yaml, upfcfg.yaml, UE and MongoDB.
Register the UE to free5GC and try to establish a PDU session with the DNN.

You can see the following log output indicating that the SmPolicy cannot be obtained:.
2021-10-20T16:21:30+09:00 [INFO][PCF][SMpolicy] Handle CreateSmPolicy
2021-10-20T16:21:30+09:00 [INFO][UDR][DRepo] Handle PolicyDataUesUeIdSmDataGet
2021-10-20T16:21:30+09:00 [INFO][UDR][GIN] | 404 |       <IP_ADDRESS> | GET     | /nudr-dr/v1/policy-data/ues/imsi-2089300007487/sm-data?dnn=example.net&snssai=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D |
2021-10-20T16:21:30+09:00 [WARN][PCF][SMpolicy] Can't find UE[imsi-2089300007487] SM Policy Data in UDR
2021-10-20T16:21:30+09:00 [INFO][PCF][GIN] | 400 |       <IP_ADDRESS> | POST    | /npcf-smpolicycontrol/v1/sm-policies |
2021-10-20T16:21:30+09:00 [ERRO][SMF][PduSess] setup sm policy association failed: 400 Bad Request {  400 Can't find UE SM Policy Data in UDR  USER_UNKNOWN []}
2021-10-20T16:21:30+09:00 [INFO][SMF][GIN] | 403 |       <IP_ADDRESS> | POST    | /nsmf-pdusession/v1/sm-contexts |
2021-10-20T16:21:30+09:00 [WARN][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] PDU Session Establishment Request is rejected by SMF[pduSessionId:10]

Expected behavior
NFs can get data from MongoDB even if DNN contains a period, and a PDU session with the DNN can be established.
Environment (please complete the following information):

free5GC Version: 3.0.5
OS: Ubuntu 18.04
Kernel version: 5.0.0-23-generic
go version go1.14.4 linux/amd64

System architecture (Option)

To replace all periods(.) in DNN to underscores(_) which is not available to be used in DNN
before storing it into MongoDB.
To replace all periods(.) in DNN to underscores(_) before calling MongoDB query API.
To replace all underscores(_) of DNNs in the gotten data, from MongoDB by the query API, to periods(.).

Pull Request

udr

If willing to resolve an issue by submitting Pull request, please consider the points below.
Webconsole also needs to be fixed but I don't know how to fix it.

@matsumu-y
Thanks for your PR and the PR was merged.
We also merged https://github.com/free5gc/webconsole/pull/14.
Please update the udr and webconsole and try.


Re-generated apis/Google.Cloud.Compute.V1 supporting pagination

This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/248d4c9d-721b-4310-b5e1-e08f1834cf0c/targets

[ ] To automatically regenerate this PR, check this box. (May take up to 24 hours.)

On Monday I'll either pull this and add another commit to it, or just force-merge it and then fix the tests afterwards.


Account Login Module crashes on 'update profile' - CKEditor ref error

Description of bug
When a user, whose profile is missing a required field, tries to login using the Account Login Module, the "Please update your profile before continuing." crashes and is stuck loading.
In my case, this affects users having an older profile, which don't have a custom required field filled out that has been added since as well as missing the preferred language selection.
Steps to reproduce
List the precise steps to reproduce the bug:

Go to Persona Bar -> Manage -> Users -> Add user
Add names, Email and password and save. You also need to have set up required fields not showing up here
Go to a page using the Account Login Module (non modal)
Login with the new accounts username and password
See error

Current behavior
The 'Please update your profile before continuing.' part of the login loads, followed by loading.gif overlay. Loading never stops and the profile cannot be updated.
Expected behavior
Properly load the inputs and allow updating the profile.
Screenshots

Error information
Console log:
See console log and screenshot.
console-export-2021-2-23_10-53-25.txt

Additional context
Possibly related to the recent CKEditor update.
Please note, that it does work when using the native default way of loging in not using the module.
Affected version

[ ] 10.00.00 alpha build
[ ] 09.09.00 release candidate
[ X ] 09.08.01 latest supported release

Affected browser

[ X ] Chrome
[ X ] Firefox
[ ] Safari
[ ] Internet Explorer 11
[ ] Microsoft Edge (Classic)
[ ] Microsoft Edge Chromium

Still an issue

I had this on one upgrade from a really bad original site with all kinds of funky stuff. I worked around it by making the biography field not rich-text. Unstaled the issue in case anyone has some steps accurate steps to reproduce from a clean upgrade


Bank transfer status not updated when switched to other payment method

If a user pays with the bank-transfer method, since a few months, Mollie gives the customer the option to change his mind and switch to a different payment method, such as credit-card or iDeal, at a later point in time.
If the customer completes the payment using one of these different methods, then the status in Prestashop remains 'Waiting for bank transfer' although payment is completed already (in Mollie dashboard).

Hi Remco,
Thank you for taking the time to report this issue. The same issue was reported a while ago and we fixed this in one of the latest updates.
Which version of the Mollie module are you currently using? We just tested it with the latest version (v2.0.4) and everything seems te be working fine.
If you are currently using an older version of the Mollie module, please upgrade to the latest version. Please test it on your development environment first before placing it on the production site, and let us know if the issue is solved so we can close it.
If you have any questions please let us know, we are happy to help out.
Kind regards

Hi @Torrentus ,
We are closing this issue. If you have any other questions, please let us know.
Kind regards