Use an uniform tagging system across all docker istio images (manager, mixer, proxy)

Build system (jenkins/travis) applies:

"date+build#" , where date is YYYY-MM-DD-HH:SS ; required on all images

date is a must giving Bazel build produces incorrect date
build# - keep in mind that Mixer is on travis, manager + proxy + app (runtime) are on Jenkins

short SHA - required on all images
github search repo with short SHA will find the commit directly, no need to go to the build system as an extra step

"latest":  to be used only by the build system, only if we apply it explicitly and force it with any new push, otherwise we fall in this trap http://container-solutions.com/docker-latest-confusion/
only one image per repo will have this label

"alpha-XX.XX"
optional, same label used for all repos, so we can select a matching set of images
can become beta etc.

"release-XX.XX" for when time comes :)

Private builds:

username + date , where date is YYYY-MM-DD-HH:SS - this will help clean up stale images

For all types of builds, additional manual labels are permitted, for instance "demo", "featureX-working". There is virtually no penalty for using multiple labels on an image.

(@sebastienvas) we also need standalone binary releases for proxy, proxy + debug, istioctl. istioctl needs builds for each platform.

This sounds fine. But we shouldn't pollute dockerhub with hundreds of tags
or images. People browse through dockerhub.
There is also semantic versioning that we need to take into account over
time. This is the standard practice followed by several popular images on
dockerhub.
On Thu, Feb 23, 2017 at 12:33 PM Kuat<EMAIL_ADDRESS>wrote:

(@sebastienvas https://github.com/sebastienvas) we also need standalone
binary releases for proxy, proxy + debug, istioctl. istioctl needs builds
for each platform.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/manager/issues/195#issuecomment-282062786, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH0qd71z8ZeR2R5oKC_dLydCf2bIMd5zks5rfcLXgaJpZM4MKP3E
.

--
~shriram

Is this capture in an issue. What kind of platform do we support ?
On Thu, Feb 23, 2017 at 9:33 AM, Kuat<EMAIL_ADDRESS>wrote:

(@sebastienvas https://github.com/sebastienvas) we also need standalone
binary releases for proxy, proxy + debug, istioctl. istioctl needs builds
for each platform.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/manager/issues/195#issuecomment-282062786, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQ80Z0Gw9jHDurhjOcLX0V2JF2bMXalVks5rfcLXgaJpZM4MKP3E
.

istioctl needs builds for all platforms. proxy runs on linux only (there's an experimental BSD build in review.)

You need to define all platform here. I can only build in docker for now.
Windows can potentially be done in GCP, Mac is going to be tough.
On Thu, Feb 23, 2017 at 9:56 AM, Kuat<EMAIL_ADDRESS>wrote:

istioctl needs builds for all platforms. proxy runs on linux only (there's
an experimental BSD build in review.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/manager/issues/195#issuecomment-282069319, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQ80Z1Kt0IrrNExK0S48JMP3o-RyPjeCks5rfchlgaJpZM4MKP3E
.

win, darwin, and linux. It's a golang binary, so it's just setting right GOOS.

mixer will be on Jenkins shortly. I think it is better to create the build from Jenkins only.

I think this is done with jenkins across all istio projects.


Ability to create structure

In "Volunteer management", we have a "Create a new volunteer" at the top/right of the page.
It should be the same on the Structures page, for administrators only.

Once #226 is done, replace "time()" identifiers by null


Add the /vs delete command

This adds the command /vs delete which deletes a ship immediately (well on the next tick, but close enough), without copying its blocks.
Making this a PR to get opinions before putting this in master.

LGTM 👍


Document that Windows Defender may delete suspicious files from FSStore

It failed when I tried to upload and then download an EXE file using FSStore. I found that Windows Defender considers some of those 64 KB chunk files as viruses and moves them to quarantine (i.e. its own hidden directory). It was probably the first block containing EXE file header - for WD it looks like a weird executable file.
We may add this info to a "Troubleshooting" guide. Or transform data (like xor FF) before saving them.

It failed when I tried to upload and then download an EXE file using FSStore. I found that Windows Defender considers some of those 64 KB chunk files as viruses and moves them to quarantine (i.e. its own hidden directory). It was probably the first block containing EXE file header - for WD it looks like a weird executable file.
We may add this info to a "Troubleshooting" guide. Or transform data (like xor FF) before saving them.

I think there is a way to white list directories in windows defender - https://support.microsoft.com/en-us/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26.

Now I think that we should modify blocks as they are written to disk. Users don't read docs for issues like that.


Add instructions to install ninja-build

Problem
With the migration to GN and ninja to build the wi-fi echo server example code you need to have ninja-build installed.  There is a conflict between the scripts/activate.sh and idf.sh.
Summary of Changes
added instruction to install ninja-build
fixes
No ticket - small issue

 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.

@saurabhst ?


Move Utility test classes to src/main

The aim of this mv is to make the test classes (CollectionTool.java, DatasetTool, ...) available in arlas-tests.jar. Some of this classes will be used in arlas-tagger

@sfalquier I completly agree with you, I'll remove this PR


:bug: Enable mvn spinner if isRWXSupported

@mguetta1 - Can you provide some context for this change? Is there an issue or ticket for this? At face value it looks ok, but I'm not sure how the isRWXSupported flag is meant to interact with the loading spinner.

Hi @sjd78, @dymurray
I just opened a Jira ticket for this issue: https://issues.redhat.com/browse/MTA-3699

The loading state seems the consequence of the query being active. IMHO if the entire feature is disabled we should disable the query as well. React query uses enable flag for this purpose. We use in several places i.e. here.

Done in https://github.com/konveyor/tackle2-ui/pull/1963/commits/ee7c7a2220ea4d626a90c807daf443c33a95cff3
@rszwajko better to pass isRWXSupported as an argument? I saw that useFetchCache is used only in client/src/app/pages/repositories/Mvn.tsx

@mguetta1 please edit the title to better reflect the fix.


#62 Fixing the espresso test to pass

Had to change the position of the holder from 5 > 1, also changed the click to doubleClick and added a 5000 ms delay to allow the shutter notification to appear on screen

Fixes the bug. Thanks.


Make use of Param objects and migrate some hardcoded values to input parameters

Primarily this addresses the comment here to use Param objects in the deepdisc stages. https://github.com/LSSTDESC/rail_deepdisc/pull/15#discussion_r1416647180
Also want to change a couple hardcoded variables into parameters:
https://github.com/LSSTDESC/rail_deepdisc/pull/15#discussion_r1416645213
https://github.com/LSSTDESC/rail_deepdisc/pull/15#discussion_r1416644019
https://github.com/LSSTDESC/rail_deepdisc/pull/15#discussion_r1416650549

Closing as completed


Add support for optional deployment options

Specifically, I would like to see deployment options in the config.json file to handle timeout and memory size.
I will work on a PR for this feature request as well.

Actually, this seems to be supported, just not documented yet.

Support for configuration of lambda function timeout and memory size was completed in this merged PR: https://github.com/awslabs/chalice/pull/351 under this proposal: https://github.com/awslabs/chalice/issues/347. Closing out issue.


Could you provide the result on CUB dataset when using the att attribute?

I notice that you use sent attributes of CUB dataset, but we usually use att attributes  on CUB, like CLSWGAN/TF-VAEGAN and so on. Could you please provide your result when using att attributes for fair comparison?

Much appreciation for your interest!
We have tested our method on CUB using the attribute semantic descriptor, but the results are not as good (U=52.4, S=60.9, H=56.4) as using the sentence semantic descriptor. You can also replace the sent with the attribute in the codes.
Besides, we find that some other methods, like CADA-VAE[1], cycle-CLSWGAN[2], etc., also use the sentence semantic descriptor for CUB. And our results on CUB can still outperform theirs.
Best wishes!
[1] Generalized Zero- and Few-Shot Learning via Aligned Variational Autoencoders. Edgar Schonfeld, Sayna Ebrahimi, Samarth Sinha, Trevor Darrell, and Zeynep Akata. CVPR2019.
[2] Multi-modal Cycle-consistent Generalized Zero-Shot Learning. Rafael Felix, Vijay Kumar B G, Ian Reid, and Gustavo Carneiro. ECCV2018

Hi @Hanzy1996， could you provide sentence semantic or attribute semantic descriptor for all dataset? e.g. SUN, AWA

Hi @zhihou7, the semantic descriptors of other datasets have already been updated. Due to Github's limitations, I cannot upload all data as it is too large. If you need other information about the datasets, you can download them from the link in the README.md.

@Hanzy1996 Many thanks to you!

Hi @Hanzy1996, I can run the code successfully with your provide attribute. e.g.
python CE_GZSL.py --dataset AWA1 --class_embedding attri --syn_num 100 --batch_size 2048 --attSize 1024 --nz 1024 --embedSize 2048 --outzSize 512 --nhF 2048 --ins_weight 0.001 --cls_weight 0.001 --ins_temp 0.1 --cls_temp 0.1 --manualSeed 3483 --nclass_all 200 --nclass_seen 150

I suffer from an error about embedding size. Could you help me solve this? I'm not familiar with Domain Adaption.
Best Regards,

Hi @Hanzy1996, I can run the code successfully with your provide attribute. e.g.
python CE_GZSL.py --dataset AWA1 --class_embedding attri --syn_num 100 --batch_size 2048 --attSize 1024 --nz 1024 --embedSize 2048 --outzSize 512 --nhF 2048 --ins_weight 0.001 --cls_weight 0.001 --ins_temp 0.1 --cls_temp 0.1 --manualSeed 3483 --nclass_all 200 --nclass_seen 150

I suffer from an error about embedding size. Could you help me solve this? I'm not familiar with Domain Adaption.
Best Regards,

HI, @zhihou7 , for AWA1/2, attSize=85, nclass_all=50, nclass_seen=40.

Hi, @Hanzy1996, could you please provide your result on the CUB dataset when using the att attributes for conventional ZSL or the parameters for CUB dataset when using the att attribute? Thanks a lot!


Doc generator: Add related links for related cmdlets

Currently, Network's generator determines what cmdlets are related to one another and adds links to the Related Links section of the documentation automatically. We could do this for all modules in our doc generator. We would need to determine a good means of what a 'related cmdlet' is. They can be links to the other docs directly, which is useful (and what Network generator does).

p4


Resolve Buffer Clearing Issue in Summary Generation

Description: This pull request introduces critical updates to the ConversationSummaryBufferMemory class to address a bug where the summary buffer was not being cleared as expected. Due to this issue, the buffer continued to grow without respect to the max_token_limit, leading to potential performance bottlenecks and skyrocketing context token costs.

Issue: #3922

Dependencies: N/A

Changes:

Addition of chat_messages List: A new list called chat_messages has been added to track the messages within the current conversation scope. This ensures a clear boundary between messages pending summarization and those already processed.

Buffer Selection Logic: The logic for selecting the buffer contents has been refined. The system now conditionally utilizes chat_messages when moving_summary_buffer is not empty, ensuring that only new, unsummarized messages are accounted for.

Summary Message Enhancement: Summary messages are now instantiated with an additional type="system" parameter, providing clarity and aiding in the identification of system-generated summaries.

Buffer Management in predict_new_summary Method: The predict_new_summary method has been updated to assign the current buffer to chat_messages post-summary prediction, effectively managing the buffer's size.

Clear Method Update: The clear method now resets the chat_messages to an empty state, which ensures that the buffer is properly cleared when needed.

Hey there! Closing because the linked issue is unrelated to the class this PR edits, and it's unclear what this is trying to solve.
Also feel free to write your own PR descriptions to keep them concise - looks like this one was written by an LLM :)


Add response validation in ValidatorHandler for OpenAPI spec

related issue: https://github.com/networknt/light-rest-4j/issues/27
On the server side, add response validation feature to verify if the server's response satisfies the specification or not.
If there is an error, should log it.

 Add response validation in ValidatorHandler for OpenAPI spec


As a player, I would want to have different types of caves appear in the game with different gimmicks to them, for it to be dark, volcanic and has vegetation.

Acceptance Criteria

Make code that randomly assigns a cave a different theme
It doesn't change when a player returns to it
Test if it works to see if it changes once left and returned
Pull Request


Authentication support in etcd

I would like to discuss the current lack of certificate authentication in etcd configuration:
https://github.com/vitabaks/autobase/blob/master/automation/roles/etcd/templates/etcd.conf.j2
In a previous discussion, it was mentioned that sensitive information is not stored in DCS, as highlighted here:
https://github.com/vitabaks/autobase/issues/361#issuecomment-1572279916

sensitive information is not stored in DCS.

Despite this position, there remains a potential risk scenario:

A malicious archive_command can be set in DCS. This could potentially lead to Remote Code Execution (RCE) exploits, allowing unauthorized access to sensitive data, e.g. an attacker could create a superuser without a password, modify pg_hba.conf to trust, or corrupt pgdata.
It is theoretically possible to remove data, bootstrap a new cluster, and direct existing nodes to connect to a malicious master using valid replication passwords.

Given the potential risks outlined, I kindly request reconsideration of the current decision to leave etcd unprotected. Implementing certificate authentication can provide an additional layer of security and protect against these vulnerabilities.
Thanks for attention and waiting for your feedback for possible security mitigation.

Thank you so much for raising this important issue! We fully agree that security is a critical aspect, and we’ll prioritize this task accordingly.
As an open-source project, we greatly appreciate contributions from the community. If you have the time and interest, please feel free to submit a PR with your proposed solution. This will help us implement the necessary changes faster and improve the project even further.

@klention you might be interested in the implementation of this functionality: certificate authentication in etcd.

@klention you might be interested in the implementation of this functionality: certificate authentication in etcd.

Will have a look at it.

Done https://github.com/vitabaks/autobase/pull/857


miner: add client to subscribe message

This simply adds a client to the subscribe message in Handyminer as, as it currently stands, pools will register Handyminer as user agent/version whereas with these edits pools will show: handy-miner-v1.0.0.
Looks like more listing edits on my end. Will push up a PR to introduce a linter as well.

Added changes into <IP_ADDRESS> build


Add a function for the symmetric difference of two arrays

There was a previous pull request here, which explained why difference is not symmetric. The functionality hasn't changed though...
https://github.com/documentcloud/underscore/pull/277

... apparently not.

Can we re-open this?  Real-world example (names changed to keep it simple though):
I have an array of objects that contain metadata of widget A.  I have an array of objects that contain metadata of widget B.  I want to know which metadata objects are different between the two.

I should add that the commit from eikes only works with two arrays.  I'd like it to work with an arbitrary number of arrays.

Neat!

Woohoo!  Thanks!


Avatar shape="circle" does not work and avatar does not center

I've just migrated from v4.7.0 to v4.8.0 and updated to hugo 0.68.3 (the only version currently available on homebew). Now my avatar is square even though I've added the new avatar shape = "circle" parameter to config/_default/params.toml.
Also the positioning of the avatar is not correct at various window sizes. For example when the layout switches to single column, the avatar is not centered.

The repository is https://github.com/carlosmalt/ucsc-homepage. My web page is people.ucsc.edu/carlosm but that is still using academic v4.7.0.

I figured out that I needed to pull in avatar-related code from the about.html widget to my customized aboutcm.html widget. It works now.


Added let keyword to name declaration

Fixes #
Is there any particular reason why the let keyword was omitted in this declaration?

Oh I just realized name is already defined in lib.d.ts. Still this isn't explained in the docs. Maybe a different variable name would be better.

@carlosmunozrodriguez I think it should still have the declaration. Either that or have it changed to:
let color: string = "blue";
color = 'red';

I think it should be changed to color = 'red';
It looks to me that switching to name was a mistake.

Unfortunately using the keyword let generates this error
error TS2451: Cannot redeclare block-scoped variable 'name'.

I think it is probably a bug to have name declared in lib.d.ts. Node has no problem running a JavaScript file with let name = 'red';
Anyway I like @wanderer06 suggestion of using
let color: string = "blue";
color = 'red';

I don't know how I missed that, but thanks for pointing this out. I fixed the issue with f36b33012d7d03829cb7185964ceabe3a29daf8f a https://github.com/Microsoft/TypeScript-Handbook/blob/f36b33012d7d03829cb7185964ceabe3a29daf8f/pages/Basic Types.md#string.
I just figured a commit would be faster, but please feel free to send more PRs in the future. :smiley:


Add support for the nRF54H20 DK board

Add initial support for the nRF54H20 (not EngA) SoC and the nRF54H20 DK board.
Replace nRF54H20 PDK with DK.

Added some missing stuff, removed changes in snippets and tests.

Rebased.

Removed nRF54H20 PDK.

Rebased.

Rebased.


Add tilt js in collaboration section

Is your feature request related to a problem? Please describe.
Hey, I want to add tilt js in the collaboration section. It is a good improvement in UI. Please assign me this issue. Thank you!

Describe the solution you'd like
Add tilt js to the cards so that a user when hovers over it the cards get tilted by some degree and it looks like 3D.
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Please assign me this issue

Please assign me this issue so that I can start working on it.


react-native link error

Trying to link:
react-native link react-native-zendesk-ichat
Got this error:
error Something went wrong while linking. Error: Expected [\n\r] but end of input found.
React Native Environment Info:
System:
OS: macOS 10.15
CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
Memory: 167.52 MB / 8.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 10.16.0 - /usr/local/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
Android SDK:
API Levels: 23, 26, 27, 28
Build Tools: 26.0.2, 26.0.3, 27.0.3, 28.0.0, 28.0.2, 28.0.3
System Images: android-28 | Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.3 AI-182.5<IP_ADDRESS>14842
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: ^0.59.9 => 0.59.10
npmGlobalPackages:
react-native-cli: 2.0.1

Could you update your version of RN to 0.60? From that version you should not have problems.


Update scala-collection-compat to 2.4.3

Updates org.scala-lang.modules:scala-collection-compat from 2.4.2 to 2.4.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (2.4.2).
You might want to review and update them manually.
examples/project/Version.scala
project/Version.scala
project/plugins.sbt

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang.modules", artifactId = "scala-collection-compat" } ]

labels: library-update, semver-patch, old-version-remains

Superseded by #572.


Update container-runtimes.md

I propose that by adding the requisite modules to /etc/modules-load.d/ can help prevent issues with overlay and br_netfilter modules not loading after reboot.
Problem:

Modules do not persist reboots
Documentation states that they will persist across reboots.
Cluster will fail pre-flight if modules are not loaded

This is the way it is documented in the containerd installation prerequisites but appears missing from CRI-O. Modules do not appear to persist across reboots unless /etc/modules-load.d has a config reference to load at boot.

Cool @kylejep.  Please sign the CLA.

I signed it

I signed it

/lgtm

/lgtm

/sig cluster-lifecycle node

/sig cluster-lifecycle node

/approve

/approve


About the YMF825 protocol

There are already some software that can directly control the YMF825 and can make full use of the new features of the YMF825:

YMF825 tone editor written in Java:https://github.com/shigosenCCneko/YMF825MIDI_CONTROL_for_Arduino
YMF825 tone editor written in C#:https://github.com/nanase/ymf825

Indeed, there is also my own MIDI implementation project, Note Salad, that can adjust YMF825 FM parameters via NRPN messages 😄
https://youtu.be/qVMLqGQ5HB0
opl2sd1 though is specifically about providing an OPL compatible interface, so adding direct control of the YMF825 is out of scope I think.


[Bug]: TerraDraw.clear() is unreliable and should probably be a Promise

Issue Description
When clearing the map with TerraDraw.clear(), the clearing is sometimes unreliable and features remain on the map.
For example after dragging a feature, and then clearing the map, some feature artifacts remain on the map.
Reproduction
Small Example which renders a Polygon in Maplibre GL. When clicking on the EditMode Button, the same Polygon is rendered via TerraDraw. The button simply toggles between adding the feature to the map via TerraDraw, and clearing the map.

Toggle Edit Mode
Drag drawn TerraDraw polygon around a bit. Keep the polygon selected.
Toggle Edit Mode again.

Setting a timeout is also unreliable because it depends on how many features are rendered via TerraDraw( polygons need longer than points).
Vue3 : https://stackblitz.com/edit/vitejs-vite-zmfrj9?file=src%2Fcomponents%2FMaplibre.vue
Vanilla JS: https://stackblitz.com/edit/vitejs-vite-v4xsrl?file=src%2Fmain.ts
Proposal
The clear function should return a Promise, and should respect features that are still in selected state.
Sorry for opening up so many issues :D

I can reproduce this bug - I think it is just an issue with the clear up function for MapLibre. Let me take a minute to look into it.


SSL

Hi,
Many thanks for providing this.
Does it support SSL redis connections?
Thanks!
Mark

anyone can respond? I have also tried with SSL port and it doesn't work. Getting connection read timeout.

Current implementation does not support SSL, however the good news is that the underlying Jedis client does.  For some background, check out https://github.com/xetorthio/jedis/issues/1417.
The issue is that the current implementation does not fully honor the URI in that it ignores the scheme portion of the URI.  E.g., the following URI config in context.xml should trigger SSL support (note the scheme):
    <Store className="com.gopivotal.manager.redis.RedisStore"
       uri="rediss://localhost:6390/0"
     />

Parts of the URI are gleaned and, along with some other props, are used to create the pool.  Unfortunately those parts do not presently include the scheme, ie redis vs rediss.
I was able to get SSL support working without a whole lot of changes.  The change of interest was to com.gopivotal.manager.redis.RedisStore::startInternal() and was along the lines of:
    boolean ssl = ... /* does URI start with 'rediss'? */;
    RedisStore.this.jedisPool = new JedisPool(poolConfig, RedisStore.this.host,
        RedisStore.this.port, RedisStore.this.timeout, RedisStore.this.password,
        RedisStore.this.database, ssl);

Lets leave this ticket open and work on a proper solution for SSL. At least we can provide the parsing of the URI or have the attributes available to enable SSL.

Created a branch ssl-support with an initial implementation of SSL support.
See the main README for how to configure a Tomcat instance.
See the README in the redis-store/ssl directory for how to setup a development environment.


add irregular plural: tacos

Pull Request Test Coverage Report for Build 62

1 of 2 (50.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.08%) to 98.984%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

inflect.py
1
2
50.0%

Totals

Change from base Build 32:
-0.08%

Covered Lines:
1169

Relevant Lines:
1181

💛  - Coveralls


Release/91

Note: Prepared for release commit is WIP as we didn't merge R90 yet.

R90 went out, please rebase

@alexanderdean done.

Thanks, @BenFradet can you review for us?


web app build fails

building root gradle file succeeds but building web app fails.
I run: npm install; npm run serve and it complains about missing files: (common-client-js.js, web.js required from web/src/main/js/index.js). Also I could not find any actual building of common-client-js file (quick find in path..).
how can I solve that, are there any instructions how to use this project?

Sorry for that. I introduced new task to Android and I added expected declaration in common-client and I forgot to make actual declaration in common-client-js. I am adding the instruction how to start all the clients.
I am always moving to web and running gradle build and then npm run serve (although gradle :web:run should work too). Sometimes I need to make npm run serve two times because there are errors during first run (sorry for that. I will fix it whenever I will have some time)


build of PR 19 failed due to git error

Run cd $GITHUB_WORKSPACE/cactus && git checkout -t origin/$GITHUB_REF_NAME -b build-$GITHUB_RUN_ID
fatal: 'origin/19/merge' is not a commit and a branch 'build-2827148062' cannot be created from it
Error: Process completed with exit code 128.

Should be fixed by this commit - next pull request will show.


Upgrade to Gradle 8.0.2

Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 2.809% (-95.5%) from 98.315% when pulling 523d1f27bf68e80e16a0b30972b97aecfc150fe5 on gradle_8 into<PHONE_NUMBER>78437b37a1fc187f74d3e02393c405 on main.


Automatic tone mapping

It implements my idea resulting from the observation that the captured raw HDR material is quite dark, thanks to which we can recognize it if it does not exceed a certain set brightness level for a certain time. However, exceeding it will be an immediate unambiguous signal that we are dealing with an SDR source.
Implements https://github.com/awawa-dev/HyperHDR/issues/749

Hi @AstaRom
As always thanks for the PR that includes the translation of this new feature (https://github.com/awawa-dev/HyperHDR/pull/998) 👍 Based on further testing I will add some changes to the description details regarding auto calibration later.
Did you have a chance to test it? I noticed a funny thing that ms2130 reports limited range and max brightness around ~150 (Y) during the calibration, but later after returning to Windows the range is full and max brightness is around 170 (Y). That's why I rise the default Y-threshold to 180, but I'm not sure because it's just Windows and not a video player.
BTW when some threshold (Y, U or V) is exceeded, which turns off tone mapping since theoretically we have SDR signal, its value is reported in HyperHDR logs so it can be read and corrected in the config later.

Good afternoon.
I would like to try out new features, but unfortunately I won’t be able to do this in the near future (I have started a global renovation of the house, the entire installation has been disassembled, and the TV itself is now packed in the box 😀).

I understand :) Good luck with your project!


Include crcmod in cytomining Dockerfile

Closes #49
This PR also bumps up the default docker image to the newest tag 0.0.4 that includes this change.

I don't know why GitHub says I "dismissed your review"... I actually acted on your review... here's the new version


How do I change my password?

Because of #2, I'm trying to set a password so I can login. However, there's no password field on my profile.

My Bad. I forgot to add it. Will add it soon.

Added Change Password feature(profile.html) and Forgot password feature(login.html) in the development branch.


chore(github): Update GitHub Pull Request Template

Description
Summary of changes
Updating the PR template:

Remove "Dependency additions / changes" and "Test additions / changes" sections, which should be covered in the "Summary" section
Add "Example" section
Add followup options when PR requires documentation updates
Trim checklist
Minor word & formatting changes

Demo PR: https://github.com/noir-lang-test/noir/pull/12
Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt with default settings.
[ ] I have linked this PR to the issue(s) that it resolves.
[x] I have reviewed the changes on GitHub, line by line.
[x] I have ensured all changes are covered in the description.

Additional context
Once this is merged, I'll create a PR to update the template in noir-lang/.github accordingly.

Made the Example section optional and as a sub-section of Summary instead of as a comment to ease the use of it when applicable.


Installation instructions don't work

using micropython 1.10 on ESP32 with SPIRAM.
Tried both upip and mip (which is included in my micropython build).
Couldn't install micropython-ulogging.
>>> mip.install('micropython-ulogging')
Installing micropython-ulogging (latest) from https://micropython.org/pi/v2 to /lib
Package not found: https://micropython.org/pi/v2/package/6/micropython-ulogging/latest.json
Package may be partially installed

So manually installed micropython-ulogging.
Couldn't install micropython-brainelectronics-helper
So manually cloned the github repo and manually installed those files.
But some files are sill missing:
MPY: soft reboot
Traceback (most recent call last):
  File "boot.py", line 14, in <module>
  File "/lib/be_helpers/__init__.py", line 6, in <module>
  File "/lib/be_helpers/module_helper.py", line 10, in <module>
ImportError: no module named 'argparse'
Traceback (most recent call last):
  File "main.py", line 8, in <module>
  File "/lib/wifi_manager/__init__.py", line 4, in <module>
  File "/lib/wifi_manager/wifi_manager.py", line 35, in <module>
ImportError: no module named 'be_helpers.generic_helper'
MicroPython v1.20.0-117-ged7a3b11d on 2023-05-24; ESP32 module (spiram) with ESP32
Type "help()" for more information.

It appears that some files are missing from the be_helpers repo:
/home/ned/PCS/esp32> ls  /pyboard/lib/be_helpers
__init__.py      module_helper.py version.py

Could you double-check the installation instructions and package index versions using a modern version of micropython (preferably using mip)?

Should be resolved by:

Package Validation changes:

https://github.com/brainelectronics/micropython-package-validation/issues/4 and https://github.com/brainelectronics/micropython-package-validation/issues/6
https://github.com/brainelectronics/micropython-package-validation/pull/3 and https://github.com/brainelectronics/micropython-package-validation/pull/5
package-validation 0.3.0

MicroPython Modules changes:

https://github.com/brainelectronics/micropython-modules/issues/20 and https://github.com/brainelectronics/micropython-modules/issues/21
https://github.com/brainelectronics/micropython-modules/pull/22
micropython-modules 1.7.0

MicroPython ESP WiFi Manager changes:

Release 1.7.0

Thanks! closing.


README: libglm-dev is not installed as a dep

Does the ubuntu libglm-dev work for you? I tested it on a freshly-updated 14.04 and it was too old (0.9.5) hence the documentation describing how to install the version from dependencies/glm

Well, I'm using debian 8...

Feel free to add a Debian section to the readme. I only added Ubuntu under the assumption that the majority of Linux users seem to start there, and those that don't are more likely to be able to figure out what the instructions are trying to do and do the equivalent for their distro.
As an aside, I believe we need glm 0.9.6+ to allow implicit vector to vector conversions. It just happened to work on my PC as the gentoo glm package happens to be newer rather than a conscious decision. A long term fix would be to support the older glm by removing the implicit conversions, or adding the equivalent constructor to our Vec2/Vec3 wrappers.

Does this want to be merged then? What's glm used for?

Not right now - this will likely break ubuntu 14.04. And glm is used to implement the Vec2<>/Vec3<> classes (and soon transforms/rotations/even more), and therefore used all over the place.


NPM package out of date

Could you please bump version and re-publish the latest source to npm, the latest version available is 1.2.1 which does not include updated peer dependencies or React v15 compatibility fixes.
Thanks.

Fixed in 1.2.2.


No CI on pull requests?

Tests are not executed anymore on PR. Is it a bug or "a feature" 🤔 ?

That is definitely a bug. I see no sign of builds for your branches on Travis, but I have no idea why.
Thanks for all your contributions!

It looks like we had only "Build pushed branches" checked and not "Build pushed pull requests". I am going to see what happens if I check both of those instead. Could you try pushing an additional commit (or amending a commit and force pushing)  to one of your branches to see if it triggers a build now?

Ah, I see now on the requests page that your branches failed to start building with the message "Build type disabled via repository settings (pull_request)". That makes me think toggling the PR setting was the right thing to do here.

Could you try pushing an additional commit (or amending a commit and force pushing) to one of your branches to see if it triggers a build now?

Sure! Thanks for the support!

They run! Thank you :) Sadly, all of my PR is failing :D But I created a new PR to fix (I think) master :)


git integration cannot work when the filepath inclues combining character on Mac OS

VS Code Version: 1.56.0 (Universal)
OS Version: Mac OS X 10.15.7 19H2
git version: 2.31.1 via homebrew
Steps to Reproduce:

create directory named with ポ("\u30DB\u309A")
create git repo with git init command
open the directory with vscode
create some file
stage the file using vscode

you can see Git: fatal: /Users/<name>/ポ/foo.txt: '/Users/<name>/ポ/foo.txt' is outside repository

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

On Windows10 2004(19041.928), no problem.
Investigate steps:

create C++ program like below, compile with msvc(_MSC_FULL_VER: 192829913, /std:c++17)
#include <filesystem>
#include <iostream>
#include <iomanip>
namespace fs = std::filesystem;
int main()
{
    fs::create_directories(U"test\\\u30DB\u309A");
    for (const fs::directory_entry& x : fs::directory_iterator("test")) {
        const auto p = x.path().u32string();
        if (const auto pos = p.find(U"\u30D2\u309A"); std::u32string::npos != pos) {
            std::cout << "found" << std::endl;
        }
        std::cout << p.length() << std::endl;
        bool flg = false;
        for (auto&& c : p) {
            if (std::exchange(flg, true)) std::cout << ", ";
            std::cout << std::hex << c;
        }
        std::cout << std::endl;
    }
}

check the output. my output is below so that correctly the directory includes combining charactor was created.
found
7
74, 65, 73, 74, 5c, 30db, 309a

In the directory, follow steps showing first post, no problem.

@yoshi389111 says, Ubuntu on WSL on Windows + VSCode(Remote develop) env, no problem.

https://qiitadon.com/@yoshi389111/106188133990173313
LinuxのGUIは持っていないので、単なるにぎやかしですが
Windows + WSL(Ubuntu) で、vscode のリモート接続でも、結合文字の"ポ"のディレクトリで、ステージングはできますね。
確認済なのかもしれませんけど

IMHO
Summary
I can't reproduce this issue 😢
However, I ran VSCode on Flatpak and installed Flathub repository... This repository is not unofficial.
And, Git version is 2.30.2 .
So, my reproduce is not perfect 🙇🏼
My Environments

VSCode's About
Version: 1.56.0
Commit: cfa2e218100323074ac1948c885448fdf4de2a7f
Date: 2021-05-04T21:58:14.757Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.11.0-18.1-liquorix-amd64

Any Environment
$ git --version
git version 2.30.2

$ flatpak --version
Flatpak 1.11.1

Suggestion to @yumetodo
My environment git output log in VSCode at near git add:
> git ls-files --stage -- /home/<name>/ポ/poyo.py
git.stage 1
git.stage.scmResources 1
> git add -A -- /home/<name>/ポ/poyo.py
> git status -z -u

I hope this helps you if you check your logs.

According to these investigations, we can sey that this issue occurs only on mac.

It might be related with #41246...

Closing this as duplicate of https://github.com/microsoft/vscode/issues/41246


Updating the REST docs to account for the refactored endpoints

NIFI-2237:

Reorganizing the refactored REST endpoints.
Tweaking message text.

This is the second installment for NIFI-2237. There will likely be follow on PRs that complete the JIRA.

Reviewing...

Looks good, will merge to master shortly...


Docker tweaks

Codecov Report

Merging #154 (3d6d999) into develop (8613514) will decrease coverage by 50.76%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop     #154       +/-   ##
============================================
- Coverage    89.78%   39.02%   -50.77%
============================================
  Files           84       26       -58
  Lines         1283      246     -1037
  Branches         0       25       +25
============================================
- Hits          1152       96     -1056
- Misses         131      149       +18
- Partials         0        1        +1

Impacted Files
Coverage Δ

backend/src/apiurls.py

backend/src/apps/goods/migrations/0002_initial.py

backend/src/apps/goods/api/serializers.py

backend/src/apps/__init__.py

backend/src/apps/user/models.py

...rc/apps/goods/migrations/0012_dish_times_bought.py

...ontact/migrations/0004_alter_contact_added_date.py

.../apps/goods/migrations/0016_alter_dish_added_by.py

...orders/migrations/0007_alter_order_ordered_date.py

.../apps/goods/migrations/0017_alter_dish_added_by.py

... and 100 more

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


Minor problem with Help in Run-Reduce using Firefox

Hi Francis,
I have just installed Run-Reduce using run-reduce_3.0-1_amd64.deb on a new machine.
Everything seems fine except when selecting Run-Reduce User Gude from the Help Menu.
One gets the error message --- Firefox can’t find the file at /tmp/UserGuide.html
The problem is that Firefox in Ubuntu 22.04 is provided by a snap and for some reason this will only load file URLs from certain 'trusted' directory trees (which doesn't include /opt nor /tmp) and the users home directory.  Changing ones default browser to google-chrome solves the problem.
I also had this problem with help in Reduce CSL  built in /opt/reduce-algebra-code, but not with the snapshot where the HTML manual is in /usr/share/doc/reduce which is presumably a trusted location.
I now build Reduce in ~/reduce-algebra-code and put a copy of your UserGuide in my home directory to circumvent these problems, but this is not ideal.
Regards Alan Barnes

Fixed in v3.1 by using the user's home directory instead of /tmp for the User Guide.


2022 Annual Assessment pre-work: Review cg-compliance and other docs, update, and publish

In order to comply with FedRAMP requirements within our SSP, we should ensure that all docs referenced in our SSP with the "at least annually" phrase have a review, update, and our republished with the review date clear.
This includes all the XX-1 procedures, and other procedures like our IR and CP guides.
Update 2021-11-12
Notes from CoalFire Federal
Next Steps:
·         Coalfire Federal and GSA will finalize the project schedule.
·         GSA to provide control workbook outlining scope of controls for this year’s assessment
·         GSA will provide the finalize SSP.
·         GSA will provide Google Drive access within 3 business days.
·         Coalfire Federal and GSA will develop, distribute, and sign the SAP.
·         Coalfire Federal will develop and deliver a tentative interview schedule.
·         Coalfire Federal will schedule further discussions for penetration testing and vulnerability scanning.
·         Coalfire Federal and GSA will work to document all applicable information for in-scope attack vectors and schedule penetration testing activities.
·         Coordinate a weekly meeting.

Security considerations
Yes, how we do work matters.
Implementation sketch

Review all docs in https://github.com/cloud-gov/cg-compliance-docs
Review all docs that are referenced in our SSP with the phrase "at least annually"
Submit new deviation requests by (TBD) so they are in-scope for the assessment

POAMS need relevant updating too

Flesh out the WAF custom rules process so the SCR is in-scope for the assessment
Update the A-11 docs for external services
Update the bundle of GSA policies so it's up-to-date
Submit new SSP that includes A11 and attachments.
Update SSP attachment folder items

All of the following are complete:

· GSA to provide control workbook outlining scope of controls for this year’s assessment
· GSA will provide the finalize SSP.
· GSA will provide Google Drive access within 3 business days.

Moved work to Annual Assessment Board


Build Error with JS Source Set in KMP (Version 1.10.0)

Environment:
Plugin version: 1.10.0
Kotlin version: 1.7.20
Gradle version: (please include if relevant)
Operating System: (please include if relevant)
Problem:
I am using the org.kodein.mock.mockmp plugin for mock objects in unit tests for a common module in a Kotlin Multiplatform Project. While the plugin works fine with Android and iOS source sets, I encountered a build error when adding the JS source set.
Here's how I've configured the JS source set in my project:
js(IR) {
    binaries.library()
}

Error Log:
> Could not create task ':myLibrary1:compileProductionExecutableKotlinJs'.
   > Failed to apply plugin class 'org.jetbrains.kotlin.gradle.targets.js.yarn.YarnPlugin'.
      > Project#afterEvaluate(Action) on project ':myLibrary2' cannot be executed in the current context.

org.gradle.api.ProjectConfigurationException: A problem occurred configuring project ':myLibrary1-imp'.
  at org.gradle.configuration.project.LifecycleProjectEvaluator.wrapException(LifecycleProjectEvaluator.java:84)
  at org.gradle.configuration.project.LifecycleProjectEvaluator.addConfigurationFailure(LifecycleProjectEvaluator.java:77)
  at org.gradle.configuration.project.LifecycleProjectEvaluator.access$400(LifecycleProjectEvaluator.java:55)
  at org.gradle.configuration.project.LifecycleProjectEvaluator$NotifyAfterEvaluate.run(LifecycleProjectEvaluator.java:255)
  at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
  at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
  at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
  at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
  at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
  at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
  at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)

Steps to Reproduce:
Configure the plugin for a common module.
Add a JS source set as described above.
Attempt to build the project.
Expected Behavior:
The project should build successfully with the JS source set.
Actual Behavior:
The build fails with the error message provided.

At least with the new version 1.16.0, I can confirm that JS is properly supported.
See https://github.com/kosi-libs/MocKMP/blob/master/tests-projects/tests-jvm-junit4/build.gradle.kts#L19


Unable to run release APK

Steps to Reproduce

Execute flutter build APK

I am unable to run or build a release/profile APK
flutter run and flutter build apk --debug work as expected
The output of flutter build apk gets stuck at
Running Gradle task 'assembleRelease'...
Running flutter run --release -vv gets stuck at
[+1994 ms] > Task :app:compileFlutterBuildRelease
[        ] Caching disabled for task ':app:compileFlutterBuildRelease' because:
[        ]   Build cache is disabled
[        ] Task ':app:compileFlutterBuildRelease' is not up-to-date because:
[        ]   Value of input property 'dartDefines' has changed for task ':app:compileFlutterBuildRelease'
[        ]   Value of input property 'fileSystemScheme' has changed for task ':app:compileFlutterBuildRelease'
[        ]   Value of input property 'targetPath' has changed for task ':app:compileFlutterBuildRelease'
[        ] Starting process 'command '/Users/akshit-saxena/Dev/flutter/bin/flutter''. Working directory: /Users/akshit-saxena/MealGuide/mealguide
Command: /Users/akshit-saxena/Dev/flutter/bin/flutter --quiet assemble --no-version-check --depfile
/Users/akshit-saxena/MealGuide/mealguide/build/app/intermediates/flutter/release/flutter_build.d --output
/Users/akshit-saxena/MealGuide/mealguide/build/app/intermediates/flutter/release -dTargetFile=/Users/akshit-saxena/MealGuide/mealguide/lib/main.dart
-dTargetPlatform=android -dBuildMode=release -dTrackWidgetCreation=true --DartDefines=RkxVVFRFUl9XRUJfQVVUT19ERVRFQ1Q9dHJ1ZQ==
android_aot_bundle_release_android-arm64
[        ] Successfully started process 'command '/Users/akshit-saxena/Dev/flutter/bin/flutter''

Output of flutter doctor -v:
[✓] Flutter (Channel stable, 3.3.10, on macOS 12.5.1 21G83 darwin-arm, locale en-IN)
    • Flutter version 3.3.10 on channel stable at /Users/akshit-saxena/Dev/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (3 weeks ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/akshit-saxena/Library/Android/sdk
    • Platform android-33, build-tools 32.1.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
    • All Android licenses accepted.

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

[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

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

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

[✓] Connected device (2 available)
    • Pixel 7 (mobile) • 29211FDH2008YW • android-arm64 • Android 13 (API 33)
    • macOS (desktop)  • macos          • darwin-arm64  • macOS 12.5.1 21G83 darwin-arm

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

! Doctor found issues in 1 category.

Contents of android/build.gradle
buildscript {
    ext.kotlin_version = '1.6.10'
    repositories {
        google()
        mavenCentral()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:7.1.2'
        // START: FlutterFire Configuration
        classpath 'com.google.gms:google-services:4.3.10'
        // END: FlutterFire Configuration
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }
}

allprojects {
    repositories {
        google()
        mavenCentral()
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

Contents of android/gradle/wrapper/gradle-wrapper.properties
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-7.5.1-all.zip

flutter build apk --release,  try this

You can find the solution https://stackoverflow.com/questions/49874194/flutter-build-apk-on-release-mode-cannot-generate-updated-version from this link.

flutter build apk --release, try this

I've tried this, the output is stuck at
Running Gradle task 'assembleRelease'...

@Akshiiitsaxena can you build release apk for other projects?
And can you show app level build.gradle for minSdk and targetSdk versions, and packages you are using as flutter dependencies because they maybe cause for your problem.

@Akshiiitsaxena can you build release apk for other projects? And can you show app level build.gradle for minSdk and targetSdk versions, and packages you are using as flutter dependencies because they maybe cause for your problem.

yes, I am able to build release APK for other projects.
this is android/app/build.gradle
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

apply plugin: 'com.android.application'
// START: FlutterFire Configuration
apply plugin: 'com.google.gms.google-services'
// END: FlutterFire Configuration
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

def keystoreProperties = new Properties()
   def keystorePropertiesFile = rootProject.file('key.properties')
   if (keystorePropertiesFile.exists()) {
       keystoreProperties.load(new FileInputStream(keystorePropertiesFile))
   }

android {
    compileSdkVersion flutter.compileSdkVersion
    ndkVersion flutter.ndkVersion

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    kotlinOptions {
        jvmTarget = '1.8'
    }

    sourceSets {
        main.java.srcDirs += 'src/main/kotlin'
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId "com.mealguide.nutrify"
        // You can update the following values to match your application needs.
        // For more information, see: https://docs.flutter.dev/deployment/android#reviewing-the-build-configuration.
        minSdkVersion flutter.minSdkVersion
        targetSdkVersion flutter.targetSdkVersion
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        multiDexEnabled true
    }

    signingConfigs {
       release {
           keyAlias keystoreProperties['keyAlias']
           keyPassword keystoreProperties['keyPassword']
           storeFile keystoreProperties['storeFile'] ? file(keystoreProperties['storeFile']) : null
           storePassword keystoreProperties['storePassword']
       }
   }
   buildTypes {
       release {
           signingConfig signingConfigs.release
       }
   }

    // buildTypes {
    //     release {
    //         // TODO: Add your own signing config for the release build.
    //         // Signing with the debug keys for now, so `flutter run --release` works.
    //         signingConfig signingConfigs.release
    //         shrinkResources false
    //         minifyEnabled false
    //     }
    // }
}

flutter {
    source '../..'
}

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

These are the dependencies
environment:
  sdk: ">=2.17.0 <3.0.0"

# Dependencies specify other packages that your package needs in order to work.
# To automatically upgrade your package dependencies to the latest versions
# consider running `flutter pub upgrade --major-versions`. Alternatively,
# dependencies can be manually updated by changing the version numbers below to
# the latest version available on pub.dev. To see which dependencies have newer
# versions available, run `flutter pub outdated`.
dependencies:
  flutter:
    sdk: flutter
  hooks_riverpod: ^2.1.3
  flutter_hooks: ^0.18.4
  sizer: ^2.0.15
  cached_network_image: ^3.2.3
  fraction: ^4.1.4
  persistent_bottom_nav_bar_v2: ^4.2.6
  intl: ^0.17.0
  hive: ^2.2.3
  path_provider: ^2.0.11
  scrollable_positioned_list: ^0.3.5
  dio: ^4.0.6
  syncfusion_flutter_sliders: ^20.4.38
  syncfusion_flutter_core: ^20.4.38
  cupertino_icons: ^1.0.2
  firebase_core: ^2.4.0
  firebase_auth: ^4.2.3
  pin_code_fields: ^7.4.0
  percent_indicator: ^4.2.2
  flutter_native_timezone: ^2.0.0

dev_dependencies:
  flutter_test:
    sdk: flutter
  hive_generator: ^2.0.0
  build_runner: ^2.3.2

@Akshiiitsaxena Please share the complete output of flutter run --release -v so that we may verify the issue. If the log is too long, please save it into a file and attach it here. Thanks!

@Akshiiitsaxena Please share the complete output of flutter run --release -v so that we may verify the issue. If the log is too long, please save it into a file and attach it here. Thanks!

flutter run --release -v never completes, it gets stuck at this stage, I have had it running for 1+ hours:
[        ] Caching disabled for task ':app:compileFlutterBuildRelease' because:
[        ]   Build cache is disabled
[        ] Task ':app:compileFlutterBuildRelease' is not up-to-date because:
[        ]   Task has failed previously.
[        ] Starting process 'command '/Users/akshit-saxena/Dev/flutter/bin/flutter''. Working directory: /Users/akshit-saxena/MealGuide/mealguide Command:
/Users/akshit-saxena/Dev/flutter/bin/flutter --quiet assemble --no-version-check --depfile /Users/akshit-saxena/MealGuide/mealguide/build/app/intermediates/flutter/release/flutter_build.d
--output /Users/akshit-saxena/MealGuide/mealguide/build/app/intermediates/flutter/release -dTargetFile=/Users/akshit-saxena/MealGuide/mealguide/lib/main.dart -dTargetPlatform=android
-dBuildMode=release -dTrackWidgetCreation=true --DartDefines=RkxVVFRFUl9XRUJfQVVUT19ERVRFQ1Q9dHJ1ZQ== android_aot_bundle_release_android-arm64
[        ] Successfully started process 'command '/Users/akshit-saxena/Dev/flutter/bin/flutter''

Here is an output file with the complete output until this stage.
release-v-output.txt

@Akshiiitsaxena I think your problem is in flutter_native_timezone package as release-v-output.txt has lines in which written 'Registrar' is deprecated. Deprecated in Java.
Can you try building release apk without this package?

flutter_native_timezone may be the cause of the issue.
@Akshiiitsaxena: you may try @MerdanDev 's suggestion to see if it works.

flutter_native_timezone may be the cause of the issue. @Akshiiitsaxena: you may try @MerdanDev 's suggestion to see if it works.

I did remove that but it still did not work, oddly enough the problem was in one of the .dart files
I had a huge json (4MB+) that was in a dart file as data.dart
which had a variable var data = <huge JSON> and that is how I was reading it in the app.
And it seemed to have no problems in the debug version but wouldn't compile the release/profile versions.
Anyway I have added it now as an asset with a .json file ext. And reading it asynchronously parsing the asset first, and now it works fine now.

Hey @huycozy how do you think?
I think it's not flutter sdk reletad issue, sounds like more his project issue.

I think it's not flutter sdk reletad issue, sounds like more his project issue.

It might be, but we still need to confirm whether the issue can be reproducible with a sample code if any.

Anyway I have added it now as an asset with a .json file ext. And reading it asynchronously parsing the asset first, and now it works fine now.

It seems you solved the issue now, right? If so, feel free to close the issue. Thanks!


Episode boundaries in GPT-4

FormativeMemoryFactory.add_memories assumes that episodes are separated by '\n\n\n' using this code:
episodes = aggregated_result.split('\n\n\n') - line 216 in formative_memories,py
While defining agents in the three questions example, it complaints that the number of generated episodes does not match the number of formative ages.
I noticed that GPT-4 returns episodes separated by '\n\n' rather than '\n\n\n'.
Changing line 216 to use '\n\n' fixed the problem for me, but it may or may not work for other LLMs.

Yes, that should work!, exactly


The loss value didn't drop when it came down to about 7.X?

Hi, @chuanqi305 Thanks for your great job, I got some problems here. I used scrips to convert tf model to caffe model and got "deploy.caffemodel". After that, I used that weights to fine tune on my 2-class dataset. Network configurations are all as you provided in "ssdlite/voc", I changed layer names and output channels of "conf" layers. While training, learning rate is 0.0001 at the beginning, the loss start to drop util it was about 7. So weights didn't converge at all. I wondered what's wrong with
it? Eager for your reply~~~~

i have the same problem...

save question，have you solved it？

Same question.......
I0802 16:57:27.196552 21083 solver.cpp:259]     Train net output #0: mbox_loss = 6.57651 (* 1 = 6.57651 loss)
I0802 16:57:27.196557 21083 sgd_solver.cpp:138] Iteration 7310, lr = 0.05
I0802 16:57:28.975070 21083 solver.cpp:243] Iteration 7320, loss = 7.2598
I0802 16:57:28.975109 21083 solver.cpp:259]     Train net output #0: mbox_loss = 7.0054 (* 1 = 7.0054 loss)
I0802 16:57:28.975116 21083 sgd_solver.cpp:138] Iteration 7320, lr = 0.05
I0802 16:57:30.831727 21083 solver.cpp:243] Iteration 7330, loss = 7.34756
I0802 16:57:30.831763 21083 solver.cpp:259]     Train net output #0: mbox_loss = 6.6218 (* 1 = 6.6218 loss)
I0802 16:57:30.831768 21083 sgd_solver.cpp:138] Iteration 7330, lr = 0.05
I0802 16:57:32.776068 21083 solver.cpp:243] Iteration 7340, loss = 7.76406
I0802 16:57:32.776100 21083 solver.cpp:259]     Train net output #0: mbox_loss = 7.26238 (* 1 = 7.26238 loss)
I0802 16:57:32.776106 21083 sgd_solver.cpp:138] Iteration 7340, lr = 0.05
I0802 16:57:34.534003 21083 solver.cpp:243] Iteration 7350, loss = 7.65554
I0802 16:57:34.534036 21083 solver.cpp:259]     Train net output #0: mbox_loss = 7.10536 (* 1 = 7.10536 loss)
I0802 16:57:34.534042 21083 sgd_solver.cpp:138] Iteration 7350, lr = 0.05
I0802 16:57:36.399013 21083 solver.cpp:243] Iteration 7360, loss = 6.90834
I0802 16:57:36.399049 21083 solver.cpp:259]     Train net output #0: mbox_loss = 6.39814 (* 1 = 6.39814 loss)
I0802 16:57:36.399055 21083 sgd_solver.cpp:138] Iteration 7360, lr = 0.05
I0802 16:57:38.430330 21083 solver.cpp:243] Iteration 7370, loss = 7.53202
I0802 16:57:38.430369 21083 solver.cpp:259]     Train net output #0: mbox_loss = 7.61347 (* 1 = 7.61347 loss)

just continue to  train

@allenwangcheng @jimchen2018 @jimchen2018
I solved it. My dataset is quite difficult``````````

@wangzhe0623 Hello, I met the same problem with you. Could you tell me the meaning of difficult dataset? Is your dataset too complex to train?

@yulong112 YES！

@wangzhe0623 Thanks！ But what are your solutions? Just continue to train? Or change your dataset?

@wangzhe0623 Also want to know your solutions,thanks!

I have the same question, and I search some solving method , I found the batch_norm_param use_global_stats must  be false, after I  add the param , my trainning is decrease, you can try it, may be help you!!!     And the BN param like the following:
layer {
name: "conv_1/expand/bn"
type: "BatchNorm"
bottom: "conv_1/expand"
top: "conv_1/expand"
batch_norm_param {
 use_global_stats: false
 eps: 1e-5
 #eps: 0.001

}
param {
lr_mult: 0
decay_mult: 0
}
param {
lr_mult: 0
decay_mult: 0
}
param {
lr_mult: 0
decay_mult: 0
}
}

@Hanlos the value of use_global_stats is false when in phrase TRAIN, so I think it's no correctional with use_global_stats, did you modify some other values?

@wangzhe0623 Hello,I used widerface to train the SSD_Lite model, Could you please tell me how to use deploy.caffemodel to fine tune on  2-class dataset? I mean that you convert the cocomodel to  a  2-class model directly? Or convert the cocomodel to vocmodel, then you just use the part weights to fituning your model? Please help me, Thxs.

@Hanlos the value of use_global_stats is false when in phrase TRAIN, so I think it's no correctional with use_global_stats, did you modify some other values?

i have the same problem...have you been solved it? Please, help me. Thanks!

Hi, @chuanqi305 Thanks for your great job, I got some problems here. I used scrips to convert tf model to caffe model and got "deploy.caffemodel". After that, I used that weights to fine tune on my 2-class dataset. Network configurations are all as you provided in "ssdlite/voc", I changed layer names and output channels of "conf" layers. While training, learning rate is 0.0001 at the beginning, the loss start to drop util it was about 7. So weights didn't converge at all. I wondered what's wrong with
it? Eager for your reply~~~~

Increase the learning rate and adopt annealing method，using this method and the loss decreased from 4 to 2 in two hours


Rename default branch name

SSIA
Ref: https://faun.pub/git-step-by-step-renaming-a-master-branch-to-main-16390ca7577b

Since default branch at remotes have been changed via GitHub web UI, we have to update local branches.
The most quick way is to clean up local files and clone this repo again, because each client would be changed ref to remotes from ｀mastertomain`.

Create main branch via GitHub UI
Confirm no diff at remotes and delete master


Date Time handling

Basic logic is: someone would be able to build a SlackDateTime object and have the toString() representation be processed by Slack when embedded in a MessageRequest.

Currently a WIP

Should fix #8

This should be set for PR, feedback welcome

👍 but we should still think about naming the format variables a little differently if possible.
           (`-,-,
           ('(_,( )
            _   `_'
         __|_|__|_|_
       _|___________|__
      |o o o o o o o o/   hjw
     ~'`~'`~'`~'`~'`~'`~

Ship it!

Awesome, will hold on merging until docs are done.  Want to take a stab at them?

Good point @dotCipher - I can start taking a look later today.

@elektron9 any update on the docs?

@dotCipher - added some docs, but I also realized that this might not support the URL feature of Slack's DateFormatting. We can talk a bit more tomorrow too if you like.

@dotCipher - this is finally ready for review. Please have a look!


Filtering on pretranslations not working!

We're putting all verses into pretranslate.src.json!  This is causing issues.

@Enkidu93  - also, if a corpora is specified for pretranslation or training, then all other corpora should not be used.  Currently I believe the logic is "use all".  This is unintuitive.

@Enkidu93 - also, if a corpora is specified for pretranslation or training, then all other corpora should not be used. Currently I believe the logic is "use all". This is unintuitive.

@johnml1135, that could be unintuitive, I agree. Wasn't that how it already worked though with the non-parallel corpora? I think it was conceived of more as specifying a set of filters that operate on all of the associated corpora than positively specifying all data; is that right?

Multi-corpora filtering moved to #516.


Emit warnings if identifiers don't match the format of the prop.

This has escalated a bit into allowing for moving properties to a new field based on a type mapping. The idea is that this would enable cleanups where either we fix invalid type values, or we just move them to a more generic field for which no format is defined.

Looks good to me!


Assign a user a different parent automatically

Hi, what I'm trying to do is have a player enter a portal (Advanced Portals) and when they enter that portal they'll be assigned a LuckPerms group. However I can't figure out a way to assign this based on anything but their username, which I'd have to do manually.
Is there a way to have LuckPerms assign this automatically? I tried using @p to mimic command blocks but had no success there. Ideally I'd like to be able to tie LuckPerms groups to the Towny nation a player belongs to, but I've no idea how I'd go about doing that. Is there a way to do what I'm trying to do? Or should I resign myself to manually assigning permissions each time?
For context, the reason I'm doing it like this is to prevent players from being able to do anything before they join one of our server's three teams to prevent them from branching off and building elsewhere, as the point of the server is for community builds.

You can enable command selectors in the config file.
https://github.com/lucko/LuckPerms/blob/07b2df7c7e2ee141bdc30ceb96e505abba3a98a2/bukkit/src/main/resources/config.yml#L593-L595


development instructions are super confusing

Problem
The current instructions provide a terrible onboarding experience for both (a) devs just using ocean.py and (b) devs working to improve ocean.py code itself (in developers.md).
Use case: I'm an external developer and want to do a tiny code change and want to test my change locally. developers.md tells me to clone 3 repos and in the end no tests can run locally.
For testing flow, compare with this for inspiration https://github.com/oceanprotocol/ocean.js#-testing.
This needs:
For developers just using ocean.py (via import):

[ ] Get them to successfully go through "simple" and "marketplace" quickstarts in a streamlined fashion as possible. It's ok to use barge here. (How: use barge for both, and move the other stuff until after.)
[ ] And then provide them with ways to understand how to do all the things towards their own app's production usage. That is: work with networks & services that aren't just local, e.g. to use rinkeby & provider/aquarius for rinkeby. And, use test OCEAN. And, understand how config params are set.

For developers working to improve the ocean.py code itself:

[x] for developers of ocean.py, figure out most minimal instructions to get tests running locally
[x] The current development instructions provide 2 paths. Make it 1.
[x] 1 simple way of running tests locally against locally running components. Please choose barge and not manual cloning/copying
[x] same behavior between instructions and Travis (tox on Travis, pytest locally, why the difference?)

Related: #181: 'example' folder doesn't do much; either delete or flesh out

@alexcos20 @ssallam let's start by first figuring out the most basic way to run the tests locally. What else is required to make this succeed?
# 1st terminal
git clone https://github.com/oceanprotocol/barge
cd barge
./start_ocean.sh --no-dashboard

# 2nd terminal
tox

@mariacarmina what do you get when you run this?

@alexcos20 @ssallam let's start by first figuring out the most basic way to run the tests locally. What else is required to make this succeed?
# 1st terminal
git clone https://github.com/oceanprotocol/barge
cd barge
./start_ocean.sh --no-dashboard

# 2nd terminal
tox

@mariacarmina what do you get when you run this?

I'm glad to see this as an issue 👍👍

I'm glad to see this as an issue 👍👍

@alexcos20 @ssallam let's start by first figuring out the most basic way to run the tests locally. What else is required to make this succeed?
# 1st terminal
git clone https://github.com/oceanprotocol/barge
cd barge
./start_ocean.sh --no-dashboard

# 2nd terminal
tox

@mariacarmina what do you get when you run this?

So, I want tot test locally the tests from ocean.py. I updated the provider's version, then I run barge with the provider too, I wait a little and the I run in the second terminal (in ocean.py) tox and I received this error and some timeouts.

@alexcos20 @ssallam let's start by first figuring out the most basic way to run the tests locally. What else is required to make this succeed?
# 1st terminal
git clone https://github.com/oceanprotocol/barge
cd barge
./start_ocean.sh --no-dashboard

# 2nd terminal
tox

@mariacarmina what do you get when you run this?

So, I want tot test locally the tests from ocean.py. I updated the provider's version, then I run barge with the provider too, I wait a little and the I run in the second terminal (in ocean.py) tox and I received this error and some timeouts.

https://github.com/oceanprotocol/ocean.py/blob/master/READMEs/developers.md

This issue, and its related README file, are related to developers looking to improve ocean.py, vs simply use it.

.. It tells me to clone 3 repos and in the end no tests can run locally.
.. The current development instructions provide 2 paths but both of them do not allow me to run the tests locally in the end.
.. [need] figure out most minimal instructions to get tests running locally
.. [need] simple way of running tests locally against locally running components. Please choose barge and not manual cloning/copying same behavior between instructions and Travis (tox on Travis, pytest locally, why the difference?)
.. [need] testing flow, compare with this for inspiration https://github.com/oceanprotocol/ocean.js#-testing

I believe these the relevant issues that this ticket should be addressing.

Next use case: I'm a developer building a Django app and want to publish an asset.

This is a good idea. But outside the scope of this issue, since it's for developers simply using ocean.py. Go ahead and create that issue if you feel it's worth it:)

there is generally enough space in the main readme and no need to have extra development instructions, we could structure it the same as ocean.js, so a dedicated Testing part and maybe all the other sections too

90%+ users of ocean.py are just that -- users. They're looking to improve ocean.py. The README is currently structured to help them onboard the fastest, and walk through each sub-step.
Whereas people who want to learn how to improve ocean.py (including Testing part) get only a link to the developers.md file. This makes sense in terms of emphasis.

we could structure it the same as ocean.js ... and maybe all the other sections too

Remember, ocean.js has sub-READMEs for quickstarts, not in the main README. Same as ocean.py. They're what we agreed upon at the beginning of V3 work, and to me, still make lots of sense because they help a smooth onboarding.
The ocean.py READMEs they evolved based on user feedback and pain, most recently via #85 and #89. For example helping the developer find test OCEAN, and help understand how config params work. So, putting everything into a single README would be a step backward. Let's avoid that, and focus on the problems that this issue raises, copied at the top of this comment, which are to improve onboarding for developers looking to improve ocean.py.
BTW should we make a ticket to improve ocean.js README to help developers get test OCEAN, understand config params, etc?

https://github.com/oceanprotocol/ocean.py/blob/master/READMEs/developers.md

This issue, and its related README file, are related to developers looking to improve ocean.py, vs simply use it.

.. It tells me to clone 3 repos and in the end no tests can run locally.
.. The current development instructions provide 2 paths but both of them do not allow me to run the tests locally in the end.
.. [need] figure out most minimal instructions to get tests running locally
.. [need] simple way of running tests locally against locally running components. Please choose barge and not manual cloning/copying same behavior between instructions and Travis (tox on Travis, pytest locally, why the difference?)
.. [need] testing flow, compare with this for inspiration https://github.com/oceanprotocol/ocean.js#-testing

I believe these the relevant issues that this ticket should be addressing.

Next use case: I'm a developer building a Django app and want to publish an asset.

This is a good idea. But outside the scope of this issue, since it's for developers simply using ocean.py. Go ahead and create that issue if you feel it's worth it:)

there is generally enough space in the main readme and no need to have extra development instructions, we could structure it the same as ocean.js, so a dedicated Testing part and maybe all the other sections too

90%+ users of ocean.py are just that -- users. They're looking to improve ocean.py. The README is currently structured to help them onboard the fastest, and walk through each sub-step.
Whereas people who want to learn how to improve ocean.py (including Testing part) get only a link to the developers.md file. This makes sense in terms of emphasis.

we could structure it the same as ocean.js ... and maybe all the other sections too

Remember, ocean.js has sub-READMEs for quickstarts, not in the main README. Same as ocean.py. They're what we agreed upon at the beginning of V3 work, and to me, still make lots of sense because they help a smooth onboarding.
The ocean.py READMEs they evolved based on user feedback and pain, most recently via #85 and #89. For example helping the developer find test OCEAN, and help understand how config params work. So, putting everything into a single README would be a step backward. Let's avoid that, and focus on the problems that this issue raises, copied at the top of this comment, which are to improve onboarding for developers looking to improve ocean.py.
BTW should we make a ticket to improve ocean.js README to help developers get test OCEAN, understand config params, etc?

@alexcos20 @ssallam let's start by first figuring out the most basic way to run the tests locally. What else is required to make this succeed?
# 1st terminal
git clone https://github.com/oceanprotocol/barge
cd barge
./start_ocean.sh --no-dashboard

# 2nd terminal
tox

@mariacarmina what do you get when you run this?

So, I want tot test locally the tests from ocean.py. I updated the provider's version, then I run barge with the provider too, I wait a little and the I run in the second terminal (in ocean.py) tox and I received this error and some timeouts.

Problem solved. When you update the barge, you need to delete the containers first: docker container rm $(docker ps -a -q).

@alexcos20 @ssallam let's start by first figuring out the most basic way to run the tests locally. What else is required to make this succeed?
# 1st terminal
git clone https://github.com/oceanprotocol/barge
cd barge
./start_ocean.sh --no-dashboard

# 2nd terminal
tox

@mariacarmina what do you get when you run this?

So, I want tot test locally the tests from ocean.py. I updated the provider's version, then I run barge with the provider too, I wait a little and the I run in the second terminal (in ocean.py) tox and I received this error and some timeouts.

Problem solved. When you update the barge, you need to delete the containers first: docker container rm $(docker ps -a -q).

Note: @akshay-ap had made some great changes so far, so to help move briskly in master, I just merged them.
https://github.com/oceanprotocol/ocean.py/commit/25c6aeec292109e3d393b4f1c25354c0a694d35f

I just merged in https://github.com/oceanprotocol/ocean.py/commit/da350f3ab4d1df20cfe85220d97c343f78c30322, which streamlines the flow further, to be barge-only. And it has a couple tweaks to avoid barge gotchas.

Today I cleaned up the description, clarifying between (a) devs just using ocean.py and (b) devs working to improve ocean.py code itself (in developers.md).
Turns out that (b) is in much better shape now. After many iterations by @akshay-ap and me.
To handle (a), I reassigned the issue to myself. Now that we have a simple flow for developers, we can propagate things back to users. I plan to move the simple & marketplace quickstarts to first-thing in the README, both using local / barge. Users can then learn details about remote services after they get these quick wins on local.

WIP to handle (a) is in this branch.

(a) is done via commit https://github.com/oceanprotocol/ocean.py/commit/a246fe4ee5515bb63d457660df9e71554161678b

Note: (a) would be better yet with the new issue I just reported: #200. "For users of ocean-lib with ganache, getting fake OCEAN adds friction". Beyond scope of this ticket.
And we can do much better yet with readthedocs style documentation. MultiRepo#80. Beyond scope of this ticket.
@kremalicious are you satisfied for this ticket now?


[AVM Module Issue]: CosmosDB continuous backup and serverless capacity not working

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Bug
Module Name
avm/res/document-db/database-account
(Optional) Module Version
0.5.4
Description
I try to create an CosmosDB account with serverless capacity and continuous backup. This does not seem to be working with AVM. Using Bicep CLI v0.27.1.
The following Bicep creates a CosmosDB with AVM (incorrectly) and directly with Bicep (correctly):
main.bicep
targetScope = 'subscription'

@minLength(1)
@description('Primary location for all resources')
param location string = 'westeurope'

resource resourceGroup 'Microsoft.Resources/resourceGroups@2021-04-01' existing = {
  name: 'jorik-l-we-rg'
}

module cosmosDb 'br/public:avm/res/document-db/database-account:0.5.4' = {
  scope: resourceGroup
  name: 'cosmosdb'
  params: {
    name: 'jorikavmcosmos-o-we-cosmosdb'
    locations: [
      {
        failoverPriority: 0
        locationName: 'westeurope'
        isZoneRedundant: false
      }
    ]
    capabilitiesToAdd: [
       'EnableServerless'
    ]
    backupPolicyType: 'Continuous'
    backupPolicyContinuousTier: 'Continuous7Days'
  }
}

module cdb 'cosmosdb.bicep' = {
  scope: resourceGroup
  name: 'cdb'
}

cosmosdb.bicep
resource symbolicname 'Microsoft.DocumentDB/databaseAccounts@2023-11-15' = {
  name: 'joriknietavmcosmos-o-we-cosmosdb'
  location: 'westeurope'
  kind: 'GlobalDocumentDB'
  properties: {
    backupPolicy: {
      type: 'Continuous'
      continuousModeProperties: {
        tier: 'Continuous7Days'
      }
    }
    capabilities: [
      {
        name: 'EnableServerless'
      }
    ]
    capacity: {
      totalThroughputLimit: 4000
    }
    databaseAccountOfferType: 'Standard'
    enableFreeTier: false
    locations: [
      {
        failoverPriority: 0
        isZoneRedundant: false
        locationName: 'westeurope'
      }
    ]
  }
}

(Optional) Correlation Id
e8f9993f-d7b1-4292-bb29-e1c7d276b122

Hello @jorik90 try adding at least 1 database to see the continuous backup configured

Why is it mandatory to have at least on database created during provisioning of CosmosDB Account to set Serverless capability:
((!empty(sqlDatabases) || !empty(mongodbDatabases) || !empty(gremlinDatabases) || !empty(tables))
? {
....
capabilities: capabilities
....
}
: {}),
At least capabilities property should be set accordingly to capacity mode.


only pass required fields for patients page json

With a larger number of patient records, the patients page takes increasingly longer to load since it is passing the entire Patient Cache json document for each patient.
This will only pass the required attributes e.g. id, name, dob, gender and MRN.

Waiting on full load test on new server with better specs

Replaced with pull request #33 - Improve patient load due to inability to update the forked branch


ceph-csi-rbd configmap rbac broken

We have had breakage after we moved to the newest chart. We tracked down the issue to this commit:
5c600a1bc5193b35c1f050fda527bd83be6d04c7
This fixed a bug where too many permissions were given to the provisioner but exposed a bug where the driver was always writing configmaps to the default namespace, not the configured namespace and after that commit, the provisioner no longer has permissions to write to all namespaces.
So, we need to come up with a migration plan to fix this...

@plnordquist @rootfs

I'm having this same issue when using the ceph-csi-rbd chart (v1.0.0). Until this is fixed, I'm using a temporary solution for granting the provisioner service account permissions:
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: ceph-csi-rbd-provisioner
  namespace: default
rules:
  - apiGroups: [""]
    resources: ["configmaps"]
    verbs: ["get", "list", "watch", "create", "delete"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: ceph-csi-rbd-provisioner
  namespace: default
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: ceph-csi-rbd-provisioner
subjects:
- kind: ServiceAccount
  name: ceph-csi-rbd-provisioner
  namespace: ceph-csi-rbd

Yeah, that should work around the issue.

now we have configmaps in provisioner role, am closing this one, please reopen if issue still persists


Revert "BAU: Ignore unchanged k8s resources"

Reverts alphagov/gsp#519
sandbox-deployer is failing and we're not sure why.

@andy-paine sorry, forgot we can't use github's auto-committing things. Have amended to re-sign it, and force-pushed. Please re-review.

Even more unexpectedly, this revert seems to have fixed the apply step by itself.

Though I don't know about that PIPESTATUS[0] magic


How to get the textview from an item?

Hi there,
How can I change one atribute for an item when I click on it?
I want to change the color of the textview when the user select an item on multiselect. How can I have access to the views inside the itens?
And if I delete itens on a list and press back before the snackbar is dismissed, the item is not deleted when I back to the list... there's a fix for this?

@Spotik if you change an attribute you have to call a notifyAdapterItemChanged event. Which will call the bindView again.
In general you should not directly access the view as this is all handled by the RecyclerView and optimal caching is not possible otherwise.
What you can do is that you get the view from the onClick event and search for your view, and that you update it then. Also remember that the bindView has to handle the same logic otherwise you get inconsistent behavior.
If you delete an item you also have to call notifyAdapterItemRemoved() (and all those notify methods have to be called on the main UI thread)


Add kubectl kcp crd snapshot command

Summary
Add a new command, kubectl kcp crd snapshot, to make it easy to convert.
	crdExample = `
	# Convert a CRD in a yaml file to an APIResourceSchema. For a CRD named widgets.example.io, and a prefix value of
	# 'today', the new APIResourceSchema's name will be today.widgets.example.io.
	%[1]s crd snapshot -f crd.yaml --prefix 2022-05-07 > api-resource-schema.yaml
	# Convert a CRD from STDIN
	%[1]s crd snapshot -f - --prefix today > output.yaml

Related issue(s)
Fixes #

Example:
$ go run ./cmd/crd-to-apiresourceschema/main.go testing contrib/crds/core/_endpoints.yaml
apiVersion: apis.kcp.dev/v1alpha1
kind: APIResourceSchema
metadata:
  creationTimestamp: null
  name: testing.endpoints.core
spec:
  group: ""
  names:
    kind: Endpoints
    listKind: EndpointsList
    plural: endpoints
    singular: endpoints
  scope: Namespaced
  versions:
  - name: v1
    schema:
      description: 'Endpoints is a collection of endpoints that implement the actual
        service. Example:   Name: "mysvc",   Subsets: [     {       Addresses: [{"ip":
        "<IP_ADDRESS>"}, {"ip": "<IP_ADDRESS>"}],       Ports: [{"name": "a", "port": 8675},
        {"name": "b", "port": 309}]     },     {       Addresses: [{"ip": "<IP_ADDRESS>"}],       Ports:
        [{"name": "a", "port": 93}, {"name": "b", "port": 76}]     },  ]'
      properties:
        apiVersion:
          description: 'APIVersion defines the versioned schema of this representation
            of an object. Servers should convert recognized schemas to the latest
            internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
          type: string
        kind:
          description: 'Kind is a string value representing the REST resource this
            object represents. Servers may infer this from the endpoint the client
            submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
          type: string
        metadata:
          type: object
        subsets:
          description: The set of all endpoints is the union of all subsets. Addresses
            are placed into subsets according to the IPs they share. A single address
            with multiple ports, some of which are ready and some of which are not
            (because they come from different containers) will result in the address
            being displayed in different subsets for the different ports. No address
            will appear in both Addresses and NotReadyAddresses in the same subset.
            Sets of addresses and ports that comprise a service.
          items:
            description: 'EndpointSubset is a group of addresses with a common set
              of ports. The expanded set of endpoints is the Cartesian product of
              Addresses x Ports. For example, given:   {     Addresses: [{"ip": "<IP_ADDRESS>"},
              {"ip": "<IP_ADDRESS>"}],     Ports:     [{"name": "a", "port": 8675}, {"name":
              "b", "port": 309}]   } The resulting set of endpoints can be viewed
              as:     a: [ <IP_ADDRESS>:8675, <IP_ADDRESS>:8675 ],     b: [ <IP_ADDRESS>:309,
              <IP_ADDRESS>:309 ]'
            properties:
              addresses:
                description: IP addresses which offer the related ports that are marked
                  as ready. These endpoints should be considered safe for load balancers
                  and clients to utilize.
                items:
                  description: EndpointAddress is a tuple that describes single IP
                    address.
                  properties:
                    hostname:
                      description: The Hostname of this endpoint
                      type: string
                    ip:
                      description: 'The IP of this endpoint. May not be loopback (<IP_ADDRESS>/8),
                        link-local (<IP_ADDRESS>/16), or link-local multicast ((<IP_ADDRESS>/24).
                        IPv6 is also accepted but not fully supported on all platforms.
                        Also, certain kubernetes components, like kube-proxy, are
                        not IPv6 ready. TODO: This should allow hostname or IP, See
                        #4447.'
                      type: string
                    nodeName:
                      description: 'Optional: Node hosting this endpoint. This can
                        be used to determine endpoints local to a node.'
                      type: string
                    targetRef:
                      description: Reference to object providing the endpoint.
                      properties:
                        apiVersion:
                          description: API version of the referent.
                          type: string
                        fieldPath:
                          description: 'If referring to a piece of an object instead
                            of an entire object, this string should contain a valid
                            JSON/Go field access statement, such as desiredState.manifest.containers[2].
                            For example, if the object reference is to a container
                            within a pod, this would take on a value like: "spec.containers{name}"
                            (where "name" refers to the name of the container that
                            triggered the event) or if no container name is specified
                            "spec.containers[2]" (container with index 2 in this pod).
                            This syntax is chosen only to have some well-defined way
                            of referencing a part of an object. TODO: this design
                            is not final and this field is subject to change in the
                            future.'
                          type: string
                        kind:
                          description: 'Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
                          type: string
                        name:
                          description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
                          type: string
                        namespace:
                          description: 'Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
                          type: string
                        resourceVersion:
                          description: 'Specific resourceVersion to which this reference
                            is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
                          type: string
                        uid:
                          description: 'UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
                          type: string
                      type: object
                  required:
                  - ip
                  type: object
                type: array
              notReadyAddresses:
                description: IP addresses which offer the related ports but are not
                  currently marked as ready because they have not yet finished starting,
                  have recently failed a readiness check, or have recently failed
                  a liveness check.
                items:
                  description: EndpointAddress is a tuple that describes single IP
                    address.
                  properties:
                    hostname:
                      description: The Hostname of this endpoint
                      type: string
                    ip:
                      description: 'The IP of this endpoint. May not be loopback (<IP_ADDRESS>/8),
                        link-local (<IP_ADDRESS>/16), or link-local multicast ((<IP_ADDRESS>/24).
                        IPv6 is also accepted but not fully supported on all platforms.
                        Also, certain kubernetes components, like kube-proxy, are
                        not IPv6 ready. TODO: This should allow hostname or IP, See
                        #4447.'
                      type: string
                    nodeName:
                      description: 'Optional: Node hosting this endpoint. This can
                        be used to determine endpoints local to a node.'
                      type: string
                    targetRef:
                      description: Reference to object providing the endpoint.
                      properties:
                        apiVersion:
                          description: API version of the referent.
                          type: string
                        fieldPath:
                          description: 'If referring to a piece of an object instead
                            of an entire object, this string should contain a valid
                            JSON/Go field access statement, such as desiredState.manifest.containers[2].
                            For example, if the object reference is to a container
                            within a pod, this would take on a value like: "spec.containers{name}"
                            (where "name" refers to the name of the container that
                            triggered the event) or if no container name is specified
                            "spec.containers[2]" (container with index 2 in this pod).
                            This syntax is chosen only to have some well-defined way
                            of referencing a part of an object. TODO: this design
                            is not final and this field is subject to change in the
                            future.'
                          type: string
                        kind:
                          description: 'Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
                          type: string
                        name:
                          description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
                          type: string
                        namespace:
                          description: 'Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
                          type: string
                        resourceVersion:
                          description: 'Specific resourceVersion to which this reference
                            is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
                          type: string
                        uid:
                          description: 'UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
                          type: string
                      type: object
                  required:
                  - ip
                  type: object
                type: array
              ports:
                description: Port numbers available on the related IP addresses.
                items:
                  description: EndpointPort is a tuple that describes a single port.
                  properties:
                    appProtocol:
                      description: The application protocol for this port. This field
                        follows standard Kubernetes label syntax. Un-prefixed names
                        are reserved for IANA standard service names (as per RFC-6335
                        and http://www.iana.org/assignments/service-names). Non-standard
                        protocols should use prefixed names such as mycompany.com/my-custom-protocol.
                        Field can be enabled with ServiceAppProtocol feature gate.
                      type: string
                    name:
                      description: The name of this port.  This must match the 'name'
                        field in the corresponding ServicePort. Must be a DNS_LABEL.
                        Optional only if one port is defined.
                      type: string
                    port:
                      description: The port number of the endpoint.
                      format: int32
                      type: integer
                    protocol:
                      default: TCP
                      description: The IP protocol for this port. Must be UDP, TCP,
                        or SCTP. Default is TCP.
                      type: string
                  required:
                  - port
                  type: object
                type: array
            type: object
          type: array
      type: object
    served: true
    storage: true
    subresources: {}

kubectl kcp crd snapshot -f crd.yaml --prefix may7 > apiresourceschema.yaml
kubectl kcp crd snapshot foos.bla.com > apiresourceschema.yaml

@sttts I was fiddling some over the weekend to try to reduce copy/pasting in the plugin code. Definitely low priority, but PTAL when you have a moment & let me know what you think.

LGTM