Drupal sites/all/drush/drush.yml breaks multisite drush aliases

Describe the bug
I am not entirely sure if it is a bug, a feature, or a documentation request. All I know is that it broke ddev update in a strange way and took a while to troubleshoot.
Basically, ddev seems to generate web/sites/all/drush/drush.yml that sets uri parameter. Setting the parameter globally is not recommended for multisite configuration.
Granted, ddev does not support multisite natively anyway, but this is something that - I believe - worked a while ago and stopped due to drush configuration reorganization (in 1.9?).
To Reproduce
Steps to reproduce the behavior:

Setup Drupal 8 multisite with drush alias files
Run drush status in one of non-default directories
Observe the information coming from default configuration (database name, url, etc)
Delete/comment out all/drush/drush.yml
Rerun drush status and observe correct information

Expected behavior
Not sure, as I don't know what problem that file was solving. So, maybe it should be a mention in documentation instead.
Version and configuration information (please complete the following information):

Host computer OS and Version: MacOS Mojave
Docker: 18.09.2
ddev: v1.10.2
Do you have any custom configuration (nginx, php, mysql) in the .ddev folder? Yes (in override file), to declare additional hostnames and DB creation commands.

Easy solution, not sure if it's what you want:

Remove the line with #ddev-generated in sites/all/drush/drush.yml
Delete or change any contents as you see fit.
Check in the changed file. ddev will never touch it again.

The generated drush.yml makes it so people can use drush with a proper URL both inside the container and on the host.

Right. I figured that out. After a lot of trial and error. So I am trying
to save others from same struggle.
That's why I think that just a one line in the docs maybe sufficient. Just
for those desperately searching for "multisite" keyword.
On Wed, Aug 21, 2019, 8:54 PM Randy Fay<EMAIL_ADDRESS>wrote:

Easy solution, not sure if it's what you want:

Remove the line with #ddev-generated in sites/all/drush/drush.yml
Delete or change any contents as you see fit.
Check in the changed file. ddev will never touch it again.

The generated drush.yml makes it so people can use drush with a proper
URL both inside the container and on the host.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/drud/ddev/issues/1806?email_source=notifications&email_token=AAAPVGIFI2GXVSCMEZ5DYDTQFXPTHA5CNFSM4IOONIU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD43RIIQ#issuecomment-523703330,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAPVGMCAPIIIUZFD4SURJDQFXPTHANCNFSM4IOONIUQ
.

There's probably more to it than that. Would you care to draft (or outline) a multisite-drupal-on-ddev PR? Discuss multiple databases, drush.yml, etc? Or perhaps do a simple setup in github.com/drud/ddev-contrib with a recipe?

I don't know everything but I can definitely do a starter outline in the
next few days.
On Wed, Aug 21, 2019, 9:20 PM Randy Fay<EMAIL_ADDRESS>wrote:

There's probably more to it than that. Would you care to draft (or
outline) a multisite-drupal-on-ddev PR? Discuss multiple databases,
drush.yml, etc? Or perhaps do a simple setup in
github.com/drud/ddev-contrib with a recipe?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/drud/ddev/issues/1806?email_source=notifications&email_token=AAAPVGJFAC4A5IXZXX5LOILQFXSVLA5CNFSM4IOONIU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD43SL5A#issuecomment-523707892,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAPVGLQFO46UBJ2YBENHSLQFXSVLANCNFSM4IOONIUQ
.

The more I think about it ddev-contrib gives you the most flexibility and you don't have to shoehorn it in, and you can be very specific to Drupal multisite usage.  Thanks!

I do not see a mention of ddev-contrib anywhere in the main documentation
for DDev. So if - hypothetically - I already documented the whole multisite
setup there, I still would not be able to discover the information existing.
Or am I missing something?
On Wed, 21 Aug 2019 at 21:24, Randy Fay<EMAIL_ADDRESS>wrote:

The more I think about it ddev-contrib gives you the most flexibility and
you don't have to shoehorn it in, and you can be very specific to Drupal
multisite usage. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/drud/ddev/issues/1806?email_source=notifications&email_token=AAAPVGOBVPFD5RUQJFDIHR3QFXTEDA5CNFSM4IOONIU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD43SRGA#issuecomment-523708568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAPVGNO3P3R62ECMIQ7CNDQFXTEDANCNFSM4IOONIUQ
.

ddev-contrib is still new, and needs better referencing from the main docs. But the idea is that (mostly) the main docs are less specific about specific CMSs and applications, and people can go completely nuts with specific recipes for very vertical things in in ddev-contrib (and it's easier to get changes in there). This is a small open-source project. I'm the only maintainer. The docs aren't perfect :) But you can make them better with your contributions. Thanks!

(@Gonzalo2683 got troubles solved in https://github.com/drud/ddev/issues/1813)
I think after the multisite example/recipe lands, we should look at moving the drush.yml config that caused trouble here into drush/sites/self.site.yml if that seems like it will work. It would be nice for that drush/drush.yml not to be in people's way.

The environment variable DRUSH_OPTIONS_URI is less intrusive, recommended for this by @greg.1.anderson, see https://docs.drush.org/en/master/using-drush-configuration/
We would probably lose proper operation of drush uli on the host side, but it's probably OK.


pdfcpu: 0.3 -> 0.3.1

Motivation for this change
https://github.com/pdfcpu/pdfcpu/compare/v0.3.1..v0.3
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@GrahamcOfBorg build pdfcpu


[grappler] Convert identity ConjugateTranspose to Conj instead of removing it

This pr fixes the bug in #27500 where the identity conjugate transpose op was wrongly removed.
Thank you for your time on reviewing this pr.

@gbaned
This pr has been waiting for reviewing for a while... Maybe we can add someone else to review it? I believe it is a pretty simple change and won't take too much time...

@ezhulenev @gbaned
Could you help to merge this pr? Thank you! :).

@zhuzilin thanks for the fix!


Angular Directive scope bi-directional binding applies to ion-content scope

When using Angular Directive scope bi-directional binding as:

app.directive('directiveNoum', [function () {
return {
restrict: 'E',
transclude: true,
scope: {
directiveCtrl: '=?'
},
replace: true
};
};

And HTML as:

The <ion-content> scope retains the onControlNameVar that was needed to be at controllerName.

Greetings @thepipecat!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Greetings @thepipecat!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


[SPARK-16502] update depreciated ParquetFileReader()

https://issues.apache.org/jira/browse/SPARK-16502
What changes were proposed in this pull request?
During code compile, got below depreciation message.
/Users/renxin/workspace/spark/sql/core/src/main/java/org/apache/spark/sql/execution/datasources/parquet/SpecificParquetRecordReaderBase.java

Warning:(140, 19) java: ParquetFileReader(org.apache.hadoop.conf.Configuration,org.apache.hadoop.fs.Path,java.util.List<org.apache.parquet.hadoop.metadata.BlockMetaData>,java.util.List<org.apache.parquet.column.ColumnDescriptor>) in org.apache.parquet.hadoop.ParquetFileReader has been deprecated

Warning:(204, 19) java: ParquetFileReader(org.apache.hadoop.conf.Configuration,org.apache.hadoop.fs.Path,java.util.List<org.apache.parquet.hadoop.metadata.BlockMetaData>,java.util.List<org.apache.parquet.column.ColumnDescriptor>) in org.apache.parquet.hadoop.ParquetFileReader has been deprecated

Here just updated the method invocation.
from
  /** @deprecated */
  public ParquetFileReader(Configuration configuration, Path filePath, List<BlockMetaData> blocks, List<ColumnDescriptor> columns) throws IOException {
    this(configuration, (FileMetaData)null, filePath, blocks, columns);
  }

to:
  public ParquetFileReader(Configuration configuration, FileMetaData fileMetaData, Path filePath, List<BlockMetaData> blocks, List<ColumnDescriptor> columns) throws IOException {

How was this patch tested?
Tested on local machine, running unit tests.

Test build #62188 has started for PR 14160 at commit 7557e1c.

The thing we have to be careful of in general is making some change that isn't compatible with older versions of things like Hadoop (and their Parquet dependencies). This change could break older Hadoop builds. No idea, but, just suggesting that this is the thing you'd have to test, and the PR builder won't necessarily test vs, say, Hadoop 2.2

https://github.com/apache/spark/pull/14159 solves the same thing...

oh I see...sorry didn't notice it's for backward compatibility
I'll close it.

I don't know that there's actually a problem, just saying that this is the kind of thing we should be careful about. There are a number of build warnings like this. Your change could be fine.

Hi @srowen I just found it's a duplicate so I closed it.
But, when I ran ./dev/lint-java I got these style problems. I'm just wondering for these random tiny style fixes, what should I do, just submit a [MINOR] PR?
Using `mvn` from path: /usr/local/bin/mvn
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
Checkstyle checks failed at following occurrences:
[ERROR] src/main/java/org/apache/spark/unsafe/memory/HeapMemoryAllocator.java:[27,1] (imports) RedundantImport: Redundant import from the same package - org.apache.spark.unsafe.memory.MemoryAllocator.
[ERROR] src/main/java/org/apache/spark/unsafe/memory/MemoryAllocator.java:[26,3] (modifier) RedundantModifier: Redundant 'public' modifier.
[ERROR] src/main/java/org/apache/spark/unsafe/memory/MemoryAllocator.java:[30,3] (modifier) RedundantModifier: Redundant 'public' modifier.
[ERROR] src/main/java/org/apache/spark/unsafe/memory/MemoryAllocator.java:[31,3] (modifier) RedundantModifier: Redundant 'public' modifier.
[ERROR] src/main/java/org/apache/spark/sql/execution/datasources/parquet/SpecificParquetRecordReaderBase.java:[143] (sizes) LineLength: Line is longer than 100 characters (found 113).
[ERROR] src/main/java/org/apache/spark/sql/execution/datasources/parquet/SpecificParquetRecordReaderBase.java:[208] (sizes) LineLength: Line is longer than 100 characters (found 106).
[ERROR] Failed to execute goal on project spark-streaming-kafka-0-10-assembly_2.11: Could not resolve dependencies for project org.apache.spark:spark-streaming-kafka-0-10-assembly_2.11:jar:2.0.0-SNAPSHOT: Could not find artifact org.apache.spark:spark-streaming-kafka-0-10_2.11:jar:2.0.0-SNAPSHOT in apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1]

https://github.com/keypointt/spark/blob/7557e1cf5916331255bebca9d7e4682d8ca4021c/sql/core/src/main/java/org/apache/spark/sql/execution/datasources/parquet/SpecificParquetRecordReaderBase.java#L143
https://github.com/keypointt/spark/blob/7557e1cf5916331255bebca9d7e4682d8ca4021c/sql/core/src/main/java/org/apache/spark/sql/execution/datasources/parquet/SpecificParquetRecordReaderBase.java#L208

Yeah, the problem is we don't have anything that runs dev/lint-java regularly. If you find it currently shows errors in master, go ahead and fix them in a [MINOR] PR.

I'll fix these styles, thanks a lot Sean

Test build #62188 has finished for PR 14160 at commit 7557e1c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62188/
Test PASSed.


Ignition v3 to-do's

Front-end issues

[x] Safari build is broken (regex in TailwindCSS build)
[x] Tag pre-release versions
[x] Show full context key on hover
[x] Figure out solution contracts in Ignition v3
[x] Readme
[ ] Error boundaries
[ ] Share admin URLs
[ ] Error message when failed to save settings
[x] Remove Laravel docs in PHP agnostic version
[x] Figure out ignition-ui release on NPM
[x] Switch back to HighlightJS (only one with Blade support)
[x] Export SQL queries from exception in ErrorCard
[x] Hide sections that have no content
[x] Highlighted stack frames should be cached when switching frames
[x] Livewire context needs to be ported
[x] Active indicator for context
[x] Syntax highlighting for CURL & SQL CodeSnippets
[x] Debug section should disappear if there are no debug items
[x] Link to Telescope is missing
[x] Clicking outside of share/settings dialog should close the dialog
[x] Add extra information to settings dialog about saving to ~/.ignition.json
[x] Fix docs link
[x] Refactor data models in all packages
[x] Make sure the first active frame is always an application frame
[x] Stack frames without a classname should show filename
[x] ShikiJS local, no external dependencies (or Prism/Highlightjs)
[x] Ignore full path prefix option for RelaxedFilePath component (/users/alex/projects/sail/index.php -> index.php)
[x] Remove 🧨
[x] Test PHP view exceptions (so not blade)
[x] Docs site in share popup
[x] Remove exception class dropdown

Layout/design issues

[x] Debug section styling
[x] Symfony dumps additional styling (e.g. search input & darkmode)
[x] Icons: preferable bundled as SVGs. Definitely needs to be local
[x] Livewire icon
[x] "Settings saved" after saving settings should be styled
[x] Git context styling
[x] View data layout (key-value data in een DefinitionList.Row)
[x] DefinitionList.Row boolean value styling (currently weirdly spaced icons)
[x] Min-height for stacktrace (gets small when there's just a couple of lines of code)
[x] ~Multi-column layout~?
[x] Click outside Share/Settings closes dropdown
[x] Clickable context menu
[x] Anchor offset
[x] Solution runner styling
[x] Can't click on the lower half of debug tabs

Back-end/PHP issues

[x] User's local dotfile settings get overwritten by project settings
[x] Modify Flare API to accept shares with just 3 context options
[x] PR namespace change to Livewire
[x] Custom blade engine revision: do we still need it if we don't log view data?

Maybe later

[ ] Show call parameters in every frame
[ ] Support previous exceptions
[ ] Make expanded CodeSnippet collapsable again?
[ ] Look into alternatives for share admin URL?
[x] Keep code colors consistent between SFdumps and highlight.js

[ ] gebeurt ook nog iets vreemd met lange stacktrace files en line numbers:

[ ] Little glitch in highlighted SQL

Can we change the Views link to be an option as to what program we want to open it in? Currently it's set to PHPStorm

Hej @pixeldevsio,
This is configurable under the settings in the top right:

Hope this helps!


Feature: Add support for @DatabaseView annotations

This adds support for @DatabaseView annotations known from room. One test was added, further testing is needed. Implements #130. I tried to do minimal adjustments to the codebase while copying the handling of entities. I took over the Field handling from there and then just ignored the nullable property by implementing the createStatement function differently.
As I already said in #259, I may have no idea what I'm doing, so please tell me if I did something wrong or if I can do something better.
I'll try to add some more tests before this is ready to merge. Are there some specific things you would like to see tested?

The test that's currently failing is the same as in #259 and as far as I can tell, this fails even on the current developer branch. I assume that some underlying framework (dart?) got changed but I couldn't find the issue with my very limited knowledge of Streams.

At a first glance, this looks great 🎉 Thanks for your contribution! I'll review the full PR as soon as possible.

Some remarks about hacks I did and shouldn't change back myself right now:

floor_generator relies on floor_annotation via path: ../floor_annotation because it needs the new annotations. This has to be changed before the next release but can't be changed right now because nothing would work anymore.
the same for floor, which relies on floor_generator and floor_annotation.

I also messed up my branches a bit when starting out so view_processor.dart already checks for Uint8List, even if the whole rest of the code can't do anything with it. If you want to merge this PR before #259, I'll remove it. If #259 comes first, I'll rebase and use the proper getter implemented there.

floor_generator relies on floor_annotation via path: ../floor_annotation because it needs the new annotations. This has to be changed before the next release but can't be changed right now because nothing would work anymore.
the same for floor, which relies on floor_generator and floor_annotation.

No problem. Normally, I only change the paths of the library's packages to point to the versions available on pub while creating a release. I must have forgotten to revert it to referring the local version. You can leave it as it is.

I also messed up my branches a bit when starting out so view_processor.dart already checks for Uint8List, even if the whole rest of the code can't do anything with it. If you want to merge this PR before #259, I'll remove it. If #259 comes first, I'll rebase and use the proper getter there.

Let's merge #259 before.

I rebased the PR onto the current develop branch and altered view_processor.dart as written before.
I know that an integration test for the Views is still missing and maybe more, do you have any suggestions on what/how should be tested?

So, I rebased to the current develop and added some more tests (CodeCov seems to work even for PRs now, nice :) )
There is only one open question for me now: There seems to be a mechanism which checks if a table has been altered and then notifies the watchers of the concerning tables. Is that correct? If yes, do you expect this to also work with views? If yes again, then there are three ways to get the tables/entities we have to watch for a specific DatabaseView:

We try to detect them in the select query for the view (Seems pretty impossible with all the possibilities to include table names and naming things similarly)
Users have to provide the Entities on which a view depends in the @DatabaseView annotation. (easy but could lead to an unsafe/leaky way of using the library, since we can't check or guarantee the relation)
SQLite/sqflite somehow provides this (I'm not aware of that)
Any other Ideas?

Btw, if that watcher mechanism exists, how does it work and how do I access it as a library user?
PS: Ah, right, I should document the DatabaseView usage in the README, or do you want to do it yourself?

Thank you! I wont disrupt you then ;). Regarding Streams: Afaict Room seems to take the first option and includes a whole sqlite parser...

I rebased, integrated most of the suggestions and added an exception if a library user will try to use a Dao method which will stream the results of a query on a database view.

I adopted the suggestions from the review and added some documentation to the README files.

@vitusortner  When this  feature will be available as a release?

We've just created a new release with the version 0.12.0, which makes database views available and includes other features, fixes and improvements.


[Citadel Agent on VM] Fix typo and update comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: pitlv2109
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

security/OWNERS [pitlv2109]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incfly, pitlv2109
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

security/OWNERS [incfly,pitlv2109]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@pitlv2109: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
796a3bb10d60f5a2dbad21fbcd45ebcf38b83a6b
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Receive Guthix god favour from Guthixian cache

Description:
Receive Guthix god favour for divine dominion from Guthixian cache. It gave +1.6% per trip in testing.
Changes:

Change guthixian caches to give guthix god favour

Other checks:

[X] I have tested all my changes thoroughly.

Something isn't working right here..


Use PropTypes from prop-types package

This will allow project using React 16 to work.

Can we get this merged please? <3


Add: Custom pager animation

Thanks for providing the great library!
Fixes #issue(s) .

no issue

Changes proposed in this request:

Add custom pager animation

Here's examples.

Transition to page even more slowly

  .pagerTabStripViewStyle(
            .custom(
                tabItemHeight: 48,
                ...
                pagerAnimation: .interactiveSpring(response: 1.5, dampingFraction: 1.00, blendDuration: 0.25)
            )
        )

https://user-images.githubusercontent.com/52638834/192090681-c057637f-87f1-4c3e-8730-2fb90f146e40.mov

Make quick transitions ( means no animation )

  .pagerTabStripViewStyle(
            .custom(
                tabItemHeight: 48,
                ...
                pagerAnimation: .none
            )
        )

https://user-images.githubusercontent.com/52638834/192090620-3c91a5b2-4712-40f3-bd49-6654ef1292d1.mov
I hope to get a good response from you! Thanks!

@cecipirotto  I'm sorry to bother you, but would you please review?

@coffmark Thanks for contributing!


Get stable version using torbrowser updater xml

The RecommendedTBBVersions file contains current versions of Tor Browser
from all channels, including alpha or beta.
Instead of this, we can use xml file used by Tor Browser's updater in
the "release" channel:
https://dist.torproject.org/torbrowser/update_2/release/Linux_x86_64-gcc3/x/en-US

Thanks @boklm! I just tested this and it seems to work great if your locale is en-US and if your architecture is x86_64. It should be easy enough to generalize this to all locales and both architectures by changing this line:
'update_check_url': 'https://dist.torproject.org/torbrowser/update_2/release/Linux_x86_64-gcc3/x/en-US',
To this:
'update_check_url': 'https://dist.torproject.org/torbrowser/update_2/release/Linux_'+self.architecture+'-gcc3/x/'+self.language,
I've noticed that different locale URLs appear to work fine:
https://dist.torproject.org/torbrowser/update_2/release/Linux_x86_64-gcc3/x/en-US
https://dist.torproject.org/torbrowser/update_2/release/Linux_x86_64-gcc3/x/es-ES
https://dist.torproject.org/torbrowser/update_2/release/Linux_x86_64-gcc3/x/fr
https://dist.torproject.org/torbrowser/update_2/release/Linux_x86_64-gcc3/x/ru
But replacing Linux_x86_64-gcc3 with Linux_i686-gcc3 returns a 404, like with this URL:
https://dist.torproject.org/torbrowser/update_2/release/Linux_i686-gcc3/x/en-US
Do you know what the 32-bit Linux release channel URLs look like? Would you be able to add one more commit to this PR that supports different locales and architectures? Thanks!
Since there are separate release channel XML files, I imagine it would be pretty simple to enable the user to choose a branch: release, alpha, or hardened. These URLs should always remain the same, yes?

Sorry, I introduced a merge conflict. It's easy to resolve though.

Wait -- it shouldn't matter at all about the locale or architecture. We're just pulling this URL to get the version number, not a download URL. Nevermind about all that! I'll merge this now.

Isn't this new format / link be more likely to change (break)?

Yes, we are using this URL to get the version only, so it shouldn't matter which locale or architecture we use, as long as we don't push a new version for a specific locale or architecture only, which is unlikely. But if it's easy to put the real architecture and locale in the URL, we can do it, just in case. For i686, the "Linux_x86_64-gcc3" should be replaced by "Linux_x86-gcc3".


[SPARK-46835][SQL][Collations] Join support for non-binary collations

What changes were proposed in this pull request?

This change introduces support for JOINs for StringType that doesn't follow binary collations (e.g. *LCASE collations).
For intro into collation track please refer to root JIRA.
With this change we add new check that verifies whether hash based aggregations are supported (i.e. HashBroadcastJoin and ShuffleHashJoin). The check is based on existing isBinaryStable logic. If result of hash support is false logic will fallback to merge based join which works properly with non-binary collations.
Why are the changes needed?

JOINs are not working properly with StringType with non default collation at this point.
Does this PR introduce any user-facing change?

Yes - change fixes join behaviour.
How was this patch tested?

Tests in CollationSuite plus extending collations.sql golden files.
Was this patch authored or co-authored using generative AI tooling?

No

Why does this issue not seem to exist when I search it? https://issues.apache.org/jira/issues/?jql=project %3D SPARK AND text ~ SPARK-46835

Why does this issue not seem to exist when I search it? https://issues.apache.org/jira/issues/?jql=project %3D SPARK AND text ~ SPARK-46835

@GideonPotok - Not sure, here is a direct link:
https://issues.apache.org/jira/browse/SPARK-46835

thanks, merging to master!


Graphs cannot be invoked without an initial input

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.

Example Code
from langgraph.graph import StateGraph, END
from langgraph.graph.message import add_messages
from langchain_core.messages import AIMessage, HumanMessage, ToolMessage
from typing import Annotated

from typing_extensions import TypedDict

from langchain_core.runnables import chain, RunnableLambda

class State(TypedDict):
    # Messages have the type "list". The `add_messages` function
    # in the annotation defines how this state key should be updated
    # (in this case, it appends messages to the list, rather than overwriting them)
    messages: Annotated[list, add_messages]

graph_state = StateGraph(State)

welcome_message = AIMessage(content="Welcome to the hello, world! state machine.")

def emit_greeting() -> AIMessage:
    print("emit_greeting")
    return welcome_message

def handle_greeting_node(state):
    print("handle_greeting_node")
    print(state)
    state.add_message(welcome_message)
    print(state)
    return state

def handle_user_input(state):
    print("handle_user_input")
    print(state)

graph_state.add_node("handle_greeting_node", lambda state: handle_greeting_node(state))
# graph_state.add_node("handle_user_input", handle_user_input)
graph_state.set_entry_point("handle_greeting_node")
# graph_state.add_edge("handle_greeting_node", "handle_user_input")
graph_state.add_edge("handle_greeting_node", END)
app = graph_state.compile()

app.invoke()

Error Message and Stack Trace (if applicable)
Traceback (most recent call last):
File "scratch_4.py", line 51, in
app.invoke()
TypeError: Pregel.invoke() missing 1 required positional argument: 'input'
Description
It appears to be impossible to set up a LangGraph agent to send an initial message to the user from the start node. This means that the user is always presented with a "blank screen" which is unacceptable in production.  This is due to "input" being required when it should be optional.
System Info
langgraph 0.0.66
python 3.11
mac os 14.5

If you want to invoke it with an empty state, you can invoke it with an empty version of your state:
app.invoke({}) # Empty input

Could you share more about the behavior you wish to create?

If you want to invoke it with an empty state, you can invoke it with an empty version of your state:
app.invoke({}) # Empty input

If this doesn't satisfy your requirements, could you clarify why? Thanks!

This does not work. I get "langgraph.errors.InvalidUpdateError: Must write to at least one of ['messages']"

app.invoke({"messages": []}) # Empty input

then?
It depends on your graph state.

AttributeError: 'dict' object has no attribute 'add_message'

@francisjervis , the error you are seeing is because "state" in handle_greeting_node is of type State, which is a typed dict.
It doesn't have a method called add_message.
The add_messages (plural) function is a reducer
The following code seems to be what you're looking for?
from langgraph.graph import StateGraph, END
from langgraph.graph.message import add_messages
from langchain_core.messages import AIMessage, HumanMessage, ToolMessage
from typing import Annotated

from typing_extensions import TypedDict

from langchain_core.runnables import chain, RunnableLambda

class State(TypedDict):
    # Messages have the type "list". The `add_messages` function
    # in the annotation defines how this state key should be updated
    # (in this case, it appends messages to the list, rather than overwriting them)
    messages: Annotated[list, add_messages]

graph_state = StateGraph(State)

welcome_message = AIMessage(content="Welcome to the hello, world! state machine.")

def handle_greeting_node(state):
    if state["messages"]:
           # We've already greeted the user
        return {"messages": []}
    # Return a greeting ,since no message has been sent
    return {"messages": [welcome_message]}

graph_state.add_node("handle_greeting_node", lambda state: handle_greeting_node(state))
# graph_state.add_node("handle_user_input", handle_user_input)
graph_state.set_entry_point("handle_greeting_node")
# graph_state.add_edge("handle_greeting_node", "handle_user_input")
graph_state.add_edge("handle_greeting_node", END)
app = graph_state.compile()

app.invoke({"messages": []})


Spec for ErrorInvalidOpcode state

Upstream issue https://github.com/privacy-scaling-explorations/zkevm-specs/issues/350
Referenced go-ethereum code, this error is returned in opUndefined method, and it is set to JumpTable code.
So this error could be returned at code 1 and code 2 in evm.interpreter.Run method.
And evm.interpreter.Run method could be invoked via CALL, CALLCODE, DELEGATECALL, STATICCALL CREATE (and CREATE2).

Thanks for dream's code review, moved to upstream https://github.com/privacy-scaling-explorations/zkevm-specs/pull/362


Dev Console SuperchainERC20 Support

This parent issue is for the design and implementation of the console frontend to support SuperchainERC20 leading up to Devcon and includes links to static resources such as documentation and marketing content.
A design exists here but please confer with Mayank for finalization and questions.

Hey @fainashalts ,
Regarding the SuperchainERC20 Dev Console ticket, I see that it covers design and implementation leading up to DevCon. Could you clarify which elements of the console are considered P0? I want to make sure I prioritize the right features and links to documentation and marketing content.

Here is the link to the designs for the Dev console. @jvmi7
https://www.figma.com/design/JKWr4DO8BMxAB5r7qYvbIs/Dev-Console-1.2-Hi-Fi?node-id=5768-12656

@jvmi7 @tarunkhasnavis please link any PRs related to this work in this issue so we can use it as a source of truth on progress. Thank you!

Made progress on

Updating home page
Implementing Build Page (starterkit info)

Also made some design updates along the way and moving to App templates page

Hey @tarunkhasnavis, we made a minor update to the dev console homepage. We realised Supersim needed its own card, so we added that. We also moved the Superchain safe under launch and grow. You can find the updated design here.
https://www.figma.com/design/JKWr4DO8BMxAB5r7qYvbIs/Dev-Console-1.2?node-id=5768-12977&t=WfB9u7CbeBDQRih2-4
Please let me know if you have any questions.

okay, I captured all of this work in the Eng tracking issue https://github.com/ethereum-optimism/ecosystem/issues/542
the 3 main issues being here:

https://github.com/ethereum-optimism/ecosystem/issues/554
https://github.com/ethereum-optimism/ecosystem/issues/555
https://github.com/ethereum-optimism/ecosystem/issues/552

Actually, there is one more thing this image is still work in progress I am waiting on some feedback from the creative team and it's taking longer than expected. I would request that you please hide it from the frontend for now. Thank you.

Sounds good! The changes are hidden behaving a feature flag so I can just swap out the image when you have it

Hey @tarunkhasnavis
Another small change we need to make is to update the logo train according to Amanda's marketing guidelines.

https://www.figma.com/design/JKWr4DO8BMxAB5r7qYvbIs/Dev-Console-1.2?node-id=5768-12987&t=oiHsc6CyMtTFQHZt-4
The GIF for the Superchain ERC20 Starterkit is also ready. referring to this comment
Here is the Gif

Please let me know if you have any questions :)

@tarunkhasnavis, please update the copy of the SuperchainERC20 Starter kit card on the home page.
Currently, it's this.

New Copy  👇

Figma link https://www.figma.com/design/JKWr4DO8BMxAB5r7qYvbIs/Dev-Console-1.2?node-id=5812-3274&t=tiFQ08M4xVy7qfsY-4
Thank you :)

@mayanksayshi

Can I get the GIF in a downloadable format. I am unable to use it at the moment.
Just confirming that we are removing the Paymaster but we are replacing it with the Testnet Paymaster card (check figma)

Added these comments in Figma as well

@mayanksayshi
1. Can I get the GIF in a downloadable format. I am unable to use it at the moment.

2. Just confirming that we are removing the `Paymaster` but we are replacing it with the `Testnet Paymaster` card (check figma)

Added these comments in Figma as well

Hey @tarunkhasnavis we are removing all cards related to the Paymaster.
https://optimismfoundation.slack.com/archives/C050Z46S3QU/p1730822760075819?thread_ts=1730813146.919099&cid=C050Z46S3QU
I have updated the designs in Figma as well. :)

All eng tasks are completed now: https://github.com/ethereum-optimism/ecosystem/issues/542
We can see what comes out of the bug bash for more changes to be fully complete


Init bunit test

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
80 unchanged lines in 13 files lost coverage.
Overall coverage decreased (-0.6%) to 41.742%

Files with Coverage Reduction
New Missed Lines
%

Auth/ISession.cs
1
0.0%

Auth/Session.cs
1
0.0%

Session.cs
1
96.43%

Test/RpcTestRig.cs
1
98.17%

I18n/SDE.cs
2
0.0%

I18n/SEN.cs
2
0.0%

I18n/SES.cs
2
0.0%

I18n/SFR.cs
2
0.0%

I18n/SIT.cs
2
0.0%

RpcCtxExts.cs
4
90.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.6%

Covered Lines:
1428

Relevant Lines:
3421

💛  - Coveralls


Missing wheel package on PyPI

Universal wheel support was added some time ago:
https://github.com/idan/oauthlib/commit/06c7c58bac102838c46a5bef47e3d1758f7095c0
I noticed that a wheel package is not available on PyPI, only a .tar.gz file:
https://pypi.python.org/pypi/oauthlib
To upload the wheel, when you'd normally run python setup.py sdist upload, run instead python setup.py sdist bdist_wheel upload.
See https://pythonwheels.com/ for additional details. On that page, oauthlib is listed as one of the most used packages with a wheel.

It's uploaded by Travis CI.


Created single code path for Caffeine Caches with metrics

Created utility class, Caches, for creating Caffeine Cache instances. This class will optionally emit metrics via the Micrometer CaffeineStatsCounter if cache metrics are enabled and the MeterRegistry is set.
Closes #3628

This change stemmed from this comment and #3628. I did not see a good way to remove objects from the Caches using the LowMemoryDetector, so I punted on that.

It looks like this targeted the elasticity branch, but is not directly related to elasticity, and could be incorporated into the main branch. Is there another ticket that does this? Is there a reason only elasticity branch was targeted?

There is not another ticket for it. Elasticity was targeted because main is basically frozen for release and there is no 3.1 branch. I figured that it can be backported if someone wanted to do that.

I don't recall any discussion or decision that main is frozen for release. Yes, we've tried not make too many disruptive changes, but we've not agreed to freeze it. I think this isn't really a disruptive change, though... it's a nice cleanup, independent of any other features. Also, if we have stuff for a 3.1, and we know main will become the 3.1 development branch after 3.0.0 is released, we can still open a PR against main, and merge it after 3.0.0 is released from it, if we want it to go into 3.1.0. There are several PRs staged like that already. I think the main reason main hasn't forked a 3.1 branch or 3.0 release-prep branch is because the number of those situations are exceedingly few, and the risk of extra work from merging through an extra branch doesn't make it worth it for so few like that... so it's just easier to leave the few PRs staged. But in this case, it probably could have been included in 3.0 rather than left staged and deferred to 3.1.
My main concern, though, is that I don't want our community to be fractured by people starting to treat the elasticity branch as the primary development branch, while others are still focused on the mostly independent work in main. The primary development branch, as its name implies, should still be main, while the elasticity branch is still the experimental branch focused on developing elastic features. In order to support the often-discussed community goals of more frequent releases and more intermediate milestone releases (such as non-LTM ones), we need to keep features independent from one another. Too tightly coupling one feature that could be independent with another large long-running feature, instead of doing these incremental changes on the primary development branch, increases the risks of creating a situation like what we had for 2.0 and 2.1, where we had very long-running (multi-year) development cycles, or situations like what happened prior to that, where some surprising changes went overlooked because they occurred in a feature branch that got merged quickly, and ended up causing problems later (for example: all the internal API leaks that required us revisiting and churning all the affected APIs). So, for features that aren't directly elasticity-related, I don't think they should target the elasticity branch... they should target the primary development branch, if they can. This helps incorporate these changes sooner, and also helps the elasticity branch be smaller, and easier to incorporate later.
For this one, it can probably be easily backported... or omitted from 3.x entirely... but I'm more concerned about the larger principle of encouraging the use of main as the primary development branch, off of which other feature branches are based, to make sure we're still all on the same page, so we can continue to make incremental progress on multiple fronts. I would prefer we not tightly couple features together that don't need to be, as that makes incremental progress harder and take longer.


dnm: investigate TestInvalidBundle bundle log id

Signed-off-by: Asra Ali<EMAIL_ADDRESS>Does this upload to prod rekor? Why are the e2e tests using prod rekor but e2e_test.sh sets up a local rekor?

Summary

Release Note

Documentation

Codecov Report

Merging #2405 (5fc9f8e) into main (ca0959a) will decrease coverage by 0.17%.
The diff coverage is 34.17%.

@@            Coverage Diff             @@
##             main    #2405      +/-   ##
==========================================
- Coverage   30.16%   29.99%   -0.18%
==========================================
  Files         136      136
  Lines        8436     8484      +48
==========================================
  Hits         2545     2545
- Misses       5561     5611      +50
+ Partials      330      328       -2

Impacted Files
Coverage Δ

cmd/cosign/cli/verify/verify.go
18.66% <0.00%> (-0.62%)
:arrow_down:

cmd/cosign/cli/verify/verify_attestation.go
0.00% <0.00%> (ø)

cmd/cosign/cli/verify/verify_blob.go
45.77% <30.00%> (-0.64%)
:arrow_down:

pkg/cosign/tlog.go
38.55% <35.71%> (-1.51%)
:arrow_down:

pkg/cosign/verify.go
33.99% <45.00%> (-0.14%)
:arrow_down:

cmd/cosign/cli/sign/sign.go
15.84% <0.00%> (-0.28%)
:arrow_down:

cmd/cosign/cli/attest.go
0.00% <0.00%> (ø)

cmd/cosign/cli/verify.go
0.00% <0.00%> (ø)

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


Broken cached image

Any idea why do I get broken cached images sometimes?

Are the images within a loop or map function?
This may be a RN issue: https://github.com/facebook/react-native/issues/9893

I am using a ListView and a renderRow function

Are you using a unique key prop for the root component in your renderRow function? Just thinking it could be some sort of referencing issue.
Or maybe something corrupted the image when it was being cached.

here is my render function:
enderRow = (data) => {
    console.log("--- _renderRow ---")
    const timeString = moment(data.timestamp).fromNow()
    return (
      <Post
        postTitle={data.title}
        posterName={data.username}
        postTime={timeString}
        postContent={data.text}
        imagePath={data.image}
        imageWidth={data.imageWidth}
        imageHeight={data.imageHeight}
      />
    )
  }

and
<CacheableImage
          source={{ uri:this.props.imagePath }}
          resizeMode='contain'
          style={{
            height: height,
            width: screenWidth,
            alignSelf: 'center',
            marginBottom: 10,
          }}
        />

@jsappme I think your  component needs a <Post key={{'#ID'}}> prop.

it still breaks some of the images sometimes

@jsappme  Do any of the images break without CacheableImage ?  meaning using regular Image ?

no broken image with regular Image component
On Thu, Nov 24, 2016 at 2:16 PM, Jesse<EMAIL_ADDRESS>wrote:

@jsappme https://github.com/jsappme Do any of the images break without
CacheableImage ? meaning using regular Image ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jayesbe/react-native-cacheable-image/issues/27#issuecomment-262840003,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM0R9TZqZf5CkH98ZbY2rEep2Bd9mW5sks5rBfCcgaJpZM4K4fqf
.

--
Hervé Fulchiron
JSapp.me

Hmm.. too many files maybe being written to storage at once ?  maybe they need to be queued up for download.

yes I was actually thinking about this probable cause.
Any simple way to queue up those downloads?

I might have find a solution to download the images one by one for my case. I will let you know if it works

I had to go back to the RN Image component for now :-(

@jsappme I think it could be that the image is destroyed even before it's had a chance to finish downloading. I believe if that occurs the cached file just needs to be removed since it was incomplete. I will create a patch can you test it?

@jsappme  can you try the following please

diff --git a/image.js b/image.js
index c53e479..4b13ff3 100644
--- a/image.js
+++ b/image.js
@@ -18,11 +18,12 @@
         this.state = {
             isRemote: false,
             cachedImagePath: null,
+            downloadingImagePath: null,
             downloading: false,
             cacheable: true,
             jobId: null,
             networkAvailable: false
-        };
+        };
     };

     componentWillReceiveProps(nextProps) {
@@ -89,23 +90,25 @@
                     begin: this.imageDownloadBegin,
                     progress: this.imageDownloadProgress
                 };
-
+
+                this.setState({downloadingImagePath: filePath});
+
                 // directory exists.. begin download
                 RNFS
                 .downloadFile(downloadOptions)
                 .promise
                 .then(() => {
-                    this.setState({cacheable: true, cachedImagePath: filePath});
+                    this.setState({cacheable: true, cachedImagePath: filePath, downloading: false, jobId: null, downloadingImagePath: null});
                 })
                 .catch((err) => {
                     // error occurred while downloading or download stopped.. remove file if created
                     this._deleteFilePath(filePath);
-                    this.setState({cacheable: false, cachedImagePath: null});
+                    this.setState({cacheable: false, cachedImagePath: null, downloading: false, jobId: null, downloadingImagePath: null});
                 });
             })
             .catch((err) => {
                 this._deleteFilePath(filePath);
-                this.setState({cacheable: false, cachedImagePath: null});
+                this.setState({cacheable: false, cachedImagePath: null, downloading: false, jobId: null, downloadingImagePath: null});
             })
         });
     }
@@ -156,19 +159,20 @@

     componentWillMount() {
         NetInfo.isConnected.addEventListener('change', this._handleConnectivityChange);
-        // initial
-        NetInfo.isConnected.fetch().then(isConnected => {
-            this.setState({networkAvailable: isConnected});
-		});
+
+        if (this.props.checkNetwork) {
+            NetInfo.isConnected.fetch().done(this._handleConnectivityChange);
+        }

         this._processSource(this.props.source);
     }
-
+
     componentWillUnmount() {
         NetInfo.isConnected.removeEventListener('change', this._handleConnectivityChange);

         if (this.state.downloading && this.state.jobId) {
             RNFS.stopDownload(this.state.jobId);
+            this._deleteFilePath(this.state.downloadingImagePath);
         }
     }

Hi Jesse can you send me the new file to herve76 @ gmail.com?

@jsappme if you can test the latest version.

@jsappme I implemented a cache system similar to this module using react native fetch blob to download/save the images and I'm getting the exact same issue. Not sure why.
I'm also wondering if Image.prefetch could be used to do the job? And if yes how? Or I'm misunderstanding the semantic of Image.prefetch completely?

I think you're right @jayesbe. In my tests with another component it seems to occur if I have the image inside a cell of a Flatlist which destroys the cells as they move outside of the render window. I'll try this component with that fix you've mentioned to see if it fixes the issue.

I very quickly ran into this error using this component. Not sure if it's related.

That previous error may have been due to some remaining elements of the last cache component clashing with this one. It seems to be much more stable now but I still get the frequent missed images as mentioned above.

@MossP  have you tried the dev branch ?
The component has to be restructured so that data logic can be extracted into its own module that facilitates loading and cache file management. I haven't been able to get back to updating this component in some time.

Ah, no, I'm back on another component now but I'll try to take a look soon. I just thought I would test as @jsappme had gone quiet.

@jayesbe I just tried on the Dev branch. I get about 60% failure rate still when throttling the connection. I can see all images requests are complete via proxy but complete image was not received. App still shows activity indicator.
Even if I disable throttling and force close/restart App, some images do not recover although the requests to them are complete via the proxy and I can see the full image has come through.

The same problem here. Could anyone fix this bug?

Sorry guys.. I haven't been able to maintain this package as much as I need to.
I believe for the most part this package is now obsolete though may be worthwhile as a convenience.
RN now provides an ImageStore API that can be used to cache images. Adding this into the package would allow the ImageStore to maintain the cache rather than using react-native-fs. RNFS would still be used to download the file and convert to base64 encoded which would be required for ImageStore.
This requires dev.. react-native-cacheable-image doesn't work well with list components.. this is a known issue.. especially lists with a lot of elements.


Support for pit stop and f1 wear and tear as online

It would be nice to be able to bring 100% openwheel mode with pits stops and wear of wheels and vehicles, so I was testing the plugin this does not bring it and would be something very new to add to the script.

It would also be good to add the rebasar (rebufo in Spanish).

Hey, I did some research on repair zone in json file before, but I gave up because I got stuck in the tire wear function. Here are some residual codes, maybe you can use them.

For slipstream (drafting)
Add SetEnableVehicleSlipstreaming(true) to your script, but since some players don't like this, I won't add it to the script for now. Maybe I will modify the host's room UI in the future to allow the host to customize this option

For openwheel mode

stop to fix vehicle☑
tire wear ×
show vehicle health and tire hud ×

-- server-side code
RaceRoom.ConvertFromUGC = function(currentRace, lapCount)
    ---
    -- other codes
    ---
    currentRace.actualTrack.zones = {}
    if currentRace.currentTrackUGC.mission.zone and currentRace.currentTrackUGC.mission.zone.zntp then
        local zonetypes = {
            [0] = "disable npc and traffic",
            [23] = "slowdown",
            [37] = "repair",
            [40] = "explode"
        } -- From gta race modTool
        for k, v in pairs(currentRace.currentTrackUGC.mission.zone.zntp) do
            table.insert(currentRace.actualTrack.zones, {
                x = currentRace.currentTrackUGC.mission.zone.vld[i].x,
                y = currentRace.currentTrackUGC.mission.zone.vld[i].y,
                z = currentRace.currentTrackUGC.mission.zone.vld[i].z,
                type = zonetypes[currentRace.currentTrackUGC.mission.zone.zntp[i]]
            })
        end
    end
end

-- client-side code
function SetCar(_car, positionX, positionY, positionZ, heading, engine)
    local carHash = carTransformed ~= "" and carTransformed or (type(_car) == "number" and _car or _car.model)
    local ped = PlayerPedId()

    if isInOpenWheelRaceMode and GetVehicleClassFromName(carHash) == 22 then
        if not IsVehicleDriveable(lastVehicle) then
            repairCar(lastVehicle)
        end
        SetPedIntoVehicle(ped, lastVehicle, -1)
        SetEntityCoords(lastVehicle, positionX, positionY, positionZ)
        SetEntityHeading(lastVehicle, heading)
        SetGameplayCamRelativeHeading(0)
        return
    end
    ---
    -- other codes
    ---
end

function StartRace()
    ---
    -- other codes
    ---
    Citizen.CreateThread(function()
        while status == "racing" do
            ---
            -- other codes
            ---
            local ped = PlayerPedId()
            local vehicle = GetVehiclePedIsIn(ped, false)

            if isInOpenWheelRaceMode and GetVehicleClassFromName(GetEntityModel(GetHashKey(vehicle))) == 22 then
                tireWear(vehicle)
                showVehicleHealthAndTireBar(vehicle)
            end

            ---
            -- other codes
            ---
            local checkPointTouched = false
            local playerCoords = GetEntityCoords(ped)
            local _playerCoords = vector3(playerCoords.x, playerCoords.y, playerCoords.z)

            if #(_playerCoords - repair_coords) <= 15 then
                if not hasRepairCar and IsPedInAnyVehicle(ped) and GetEntitySpeed(vehicle) <= 5 then
                    repairCar(vehicle)
                    hasRepairCar = true
                end
            else
                hasRepairCar = false
            end
            ---
            -- other codes
            ---
            Citizen.Wait(0)
        end
    end)
    ---
    -- other codes
    ---
end

function repairCar(vehicle)
    SetVehicleUndriveable(vehicle, false)
    SetVehicleEngineCanDegrade(vehicle, false)
    SetVehicleEngineHealth(vehicle, 1000.0)
    SetVehiclePetrolTankHealth(vehicle, 1000.0)
    SetVehicleEngineOn(vehicle, true, true)
    SetVehicleFixed(vehicle)
    StopEntityFire(vehicle)
    SetVehicleOilLevel(vehicle, 1.0)
    SetVehicleDirtLevel(vehicle, 0)
    SetVehicleDeformationFixed(vehicle)
end

function tireWear(vehicle)
    -- Requires additional scripts to implement
    -- example: I got stuck here before, so I gave up
end

function showVehicleHealthAndTireBar(vehicle)
    -- Requires additional scripts to implement
    -- example: https://forum.cfx.re/t/release-carhud-and-helihud-modified-and-better-looking-v-1-9-new-update/97812
end

RegisterNetEvent("custom_races:loadTrack", function(_data, _track, objects, dobjects, _weatherAndHour, _laps)
    ---
    -- other codes
    ---
    for _, zone in ipairs(track.zones) do
        if zone.type == "repair" and not DoesBlipExist(repair_blip) then -- Maybe some JSON has more than 2 repair zones?
            CreateCheckpoint(5, zone.x, zone.y, zone.z, 0, 0, 0, 15, 0, 80, 100, 50)
            repair_blip = AddBlipForCoord(zone.x, zone.y, zone.z,)
            SetBlipSprite(repair_blip, 446) -- https://docs.fivem.net/docs/game-references/blips/
            isInOpenWheelRaceMode = true
            repair_coords = vector3(zone.x, zone.y, zone.z)
        end
    end
end)

Okey, thank you very much for your answer, it would be nice to implement it as customization options in the room, it would be a good thing for the future, thanks for the help I will try to investigate how I can make the wear of the wheels and show the state of the vehicle in the hud, I'm not really good at lua but if I find a way to do it I will not hesitate to share it.


Example in SentiWordNet doctest is outdated.

The example in SentiWordNet doctest is outdated given the current version of expanded SentiWordNet in NLTK, see https://github.com/nltk/nltk/blob/develop/nltk/corpus/reader/sentiwordnet.py#L19 causing failed tests on the CI server
This can be fixed easily by using these output instead of the existing one:
>>> from nltk.corpus import sentiwordnet as swn
>>> list(swn.senti_synsets('slow'))
[SentiSynset('decelerate.v.01'), SentiSynset('slow.v.02'), SentiSynset('slow.v.03'), SentiSynset('slow.a.01'), SentiSynset('slow.a.02'), SentiSynset('dense.s.04'), SentiSynset('slow.a.04'), SentiSynset('boring.s.01'), SentiSynset('dull.s.08'), SentiSynset('slowly.r.01'), SentiSynset('behind.r.03')]
>>> happy = swn.senti_synsets('happy', 'a')
>>> happy0 = list(happy)[0]
>>> happy0.pos_score()
0.875
>>> happy0.neg_score()
0.0
>>> happy0.obj_score()
0.125

Any brave soul want to try to contribute this good-first-bug?

As a start, here's some steps that one might find useful:

Fork the NLTK repository.
Clone the repository to your machine git clone https://github.com/youruser/nltk.git
Locate the nltk/nltk/corpus/reader/sentiwordnet.py file and make the modification.
(Optionally): Add your name to contributors list in the meta-information at the top of the file
Git add, commit and push changes into the repository you've forked.
Create a Pull Request (PR) to NLTK
Wait for review and merging of code
Congrats on your first step to contributing at NLTK. And thank you for your contribution!!
(Optionally) Find the next enhancement, corpus/data/model, bugfixes to contribute in NLTK =)

Fixed on https://github.com/nltk/nltk/commit/43696a171c159871ab3d8e1793292d4770b0a177


kots install for helm charts should default to the chart name

Currently it defaults to applicationABCDEF

closing this out as fixed


Car Object Detection using DL

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Car Object Detection
:red_circle: Aim : Create a DL model which will detect the objects(cars) from the given dataset.
:red_circle: Dataset : https://www.kaggle.com/datasets/dataclusterlabs/small-vehicle-images-far-vehicle-detection
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Email ID :
Participant ID (if applicable):
Approach for this Project :
What is your participant role? (Mention the Open Source program)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

please asigned this task to me. Car Object Detection using DL #241 .
FullName: Nirmal Kumar Ahirwar
Github Profile Link: https://github.com/NirmalKAhirwar
Email ID<EMAIL_ADDRESS>Approach for this Project:
1] Perform exploratory data analysis on the dataset.
2] Apply data augmentation techniques to the dataset using the Albumentations Python library.
3] Create different deep learning models for Car (object detection), such as YOLOv8, Detectron, and CNN models like VGG, EfficientNet.
4] Compare the performance of all models using accuracy metrics and perform hyperparameter tuning to achieve higher accuracy on the test dataset.
5] Implement the models using TensorFlow or PyTorch.
What is your participant role? -contributor at Social Summer of Code (SSOC), Season-2

According to the Code of Conduct and Contribution Guidelines, one contributor can be assigned one issue at a time.

please assign this task to me. Car Object Detection using DL
FullName: Devangini Shinde
Github Profile Link: https://github.com/Devangini01
Email ID<EMAIL_ADDRESS>Approach for this Project:
1] Perform exploratory data analysis on the dataset.
2] Apply data augmentation techniques to the dataset.
3] Create different deep learning models for Car (object detection), such as YOLOv8
4] Compare the performance of all models using accuracy metrics and perform hyperparameter tuning to achieve higher accuracy on the test dataset.
5] Implement the models using TensorFlow or PyTorch.
What is your participant role? -contributor at Social Summer of Code (SSOC), Season-2

Issue assigned to you @Devangini01

Please assign this task to me #241
FullName: Krish Srivastava
Github Profile Link: https://github.com/Krish-nobita903
Email ID<EMAIL_ADDRESS>Approach for this Project:
1)Preprocess the data set and perform the required analysis
2)Choose tensorflow based pre defined model like YOLO , R-CNN etc
3)Fine-tune the selected pre-trained model on your car detection dataset
4)Augment training dataset to increase its size and diversity.
5)Train the model on labeled dataset and evaluate the model on testing dataset to assess its performance.
What is  your participant role? : Contributor at SWOC(Social Winter of Code)

Let the program start officially. Issues will be assigned after that. Till then go through the repository as well as the README file.

ok thank you sir
On Fri, 29 Dec 2023 at 22:08, Abhishek Sharma @.***>
wrote:

Let the program start officially. Issues will be assigned after that. Till
then go through the repository as well as the README file.
—
Reply to this email directly, view it on GitHub
https://github.com/abhisheks008/DL-Simplified/issues/241#issuecomment-1872208844,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZGKXIJ5CMEURC375Y2TH3DYL3W2FAVCNFSM6AAAAAAYKTPVBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGIYDQOBUGQ
.
You are receiving this because you commented.Message ID:
@.***>

Hi @Krish-nobita903 do want to contribute in this issue with the approach you have given earlier?

Yes bhaiya
On Mon, 1 Jan, 2024, 11:36 Abhishek Sharma, @.***>
wrote:

Hi @Krish-nobita903 https://github.com/Krish-nobita903 do want to
contribute in this issue with the approach you have given earlier?
—
Reply to this email directly, view it on GitHub
https://github.com/abhisheks008/DL-Simplified/issues/241#issuecomment-1873175961,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZGKXIPB2IDASWHF3WSXL7LYMJG7LAVCNFSM6AAAAAAYKTPVBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZTGE3TKOJWGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Issue assigned to you @Krish-nobita903. You can start working on it. All the best!

thanks bhaiya

@abhisheks008 Hey Bro 👋, I have worked on this task earlier in my learning period , I would like to add my knowledge of YOLO algorithm and faster R-CNN inorder to identify cars , later this could be used a base for detecting vehicles in some different task
Full name : Bingumalla Likith
GitHub Profile Link : binguliki
Email ID<EMAIL_ADDRESS>Participant ID (if applicable): NA
Approach for this Project : I would be using pretrained YOLO algorithm and Faster RCNN as they are capable of detecting objects quickly , For metrics I used be using Accuracy along with Precision , Recall and F1 score
What is your participant role? GSSoC'24 | Contributor
Can you please Assign me this under GSSoC ' 24 with appropriate Level tag , You can have a bet on me I would surely complete the project and PR you soon

I like your enthusiam but one issue at a time @binguliki

@abhisheks008  Hey bro , I'll take this one , later i would go for the other one , currently i'm not assigned any issue.

Full name : Yash Sachan
GitHub Profile Link : https://github.com/YashSachan2
Email ID<EMAIL_ADDRESS>Approach: I will preprocess the images for the size suitable for the pretrained models and then fine tune and analyze the performance of pre trained models like resnet,darknet,mobilenetV2,YOLOv5,YOLOv8.Metrics for comparison  would be recall and precision.
What is your participant role?
GSSoc'24
Please assign me this issue @abhisheks008

I like your enthusiasm but one issue at a time @YashSachan2

hey , @abhisheks008 , I would like to work on this issue and I'll be using KerasCV or Pytorch for localization and detection of different types of vehicles listed using transfer learning approach

Full name : Rithish S
GitHub Profile Link : https://github.com/Rithish5513U
Email ID<EMAIL_ADDRESS>Approach for this Project :
I will use data augmentation techniques to preprocess images. I will use vgg16, mobilenet and yolo for the given problem.
I have a query, I only found vehicles other than car in the given dataset. Can u explain me about what should i do with this dataset or can i use other datasets for this project?
What is your participant role? (Mention the Open Source program)
Gssoc'24 Contributor

Hi, sir @abhisheks008 , I listed my approach down, please go through it and assign me under tag GSSOC'24
Full name : Umair Ullah
GitHub Profile Link : https://github.com/umairullah0905
Email ID<EMAIL_ADDRESS>Participant ID (if applicable):
Approach for this Project :
Algorithms - CNN architecture model such VGG16, RESNET50 can be classify the images.
Preprocessing - Image resizing, normalization, encoding and augmentation if required
Model Comparison and Selection - Evaluate Performance of all models based on the metrics obtained and will Choose the model that shows the best balance between accuracy, generalizability, and computational efficiency
What is your participant role? GSSOC'24

Full name : Rithish S GitHub Profile Link : https://github.com/Rithish5513U Email ID<EMAIL_ADDRESS>Approach for this Project : I will use data augmentation techniques to preprocess images. I will use vgg16, mobilenet and yolo for the given problem. I have a query, I only found vehicles other than car in the given dataset. Can u explain me about what should i do with this dataset or can i use other datasets for this project? What is your participant role? (Mention the Open Source program) Gssoc'24 Contributor

Can you find a compatible dataset for the same?

@abhisheks008 Check this dataset : https://www.kaggle.com/datasets/sshikamaru/car-object-detection
This dataset contains images taken from a video frame by frame. Can I use this dataset to detect cars or can I search for any other??

@abhisheks008 Check this dataset : https://www.kaggle.com/datasets/sshikamaru/car-object-detection This dataset contains images taken from a video frame by frame. Can I use this dataset to detect cars or can I search for any other??

You can go ahead with this dataset.
Assigned @Rithish5513U


Fhir version clarification

[Enter feedback here]
Under the header What FHIR version do you support? you state that "We support versions 4.0.0 and 3.0.1". When I look at the Capability Statement of a fhir api (/metadata), then I see
"fhirVersion": "4.3.0"

This means the supported version is actually R4B

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

ID: eca0f5d2-683d-902b-45ef-c4d5680fa148
Version Independent ID: 40e8e702-cebe-b8d8-633a-a22122c77fc9
Content: FAQ about FHIR service in Azure Health Data Services
Content Source: articles/healthcare-apis/fhir/fhir-faq.md
Service: healthcare-apis
Sub-service: fhir
GitHub Login: @EXPEkesheth
Microsoft Alias: kesheth

Hi @LodewijkSioen ,
Thanks for sharing this feedback. We will look into this and update as appropriate.
Hi @EXPEkesheth,
Could you please look into this, thanks.

I was mistaken, the result comes from a local docker image that was the R4B version. In azure it's R4.


Add error handling in ares-device and ares-log

:Release Notes:
Add error handling in ares-device and ares-log
:Detailed Notes:

Add error handling for resource-monitor option of ares-device
Add error handling for save option of ares-log
Change file name format to including "_" in timestamp

:Testing Performed:

Pass unit test
Pass eslint
Check error messages below test cases

ares-device.js -r -t 0

ares-device ERR! [Tips]: Please use nonnegative integer value for the "time-interval" option

ares-device.js -r -t 1 -s invalidDir/aaa

ares-device ERR! [syscall failure]: ENOENT: ...
ares-device ERR! [Tips]: Please check if the path is valid ...

ares-log.js -n 10 -s invalidDir/aaa

ares-log ERR! [syscall failure]: ENOENT: ...
ares-log ERR! [Tips]: Please check if the path is valid ...

Check file name below test cases

ares-device -c
ares-device -r -s

:Issues Addressed:
[WRN-14542] Add error handling for ares-device and ares-log

The capture and device's csv file is change on this commit. Please update related TCs.

Code :-1:
Verified :+1:

The capture file and device's csv file format will be changed by this commit. Please update related FTP TCs.

When I merge develop branch to For_QA_Test, I will update the expected result in FTP and system TCs about changed file name format.

Code :0
Verified :+1:


Drop privileges in the container

Thanks!

Hi John,
Sure, if you can release the new Docker image then my helm chart can be published since there I enforce that the pods started in Kubernetes cannot run as root.
If companies want to donate compute capacity this would a reasonable acceptance criteria :-)
Thanks,
Serge

On 19 Mar 2020, at 13:40, John Tims<EMAIL_ADDRESS>wrote:
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/johnktims/folding-at-home/pull/10#issuecomment-601155950, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN6WLKW3XBYM5G742POOJDRIIHFXANCNFSM4LPGA2GA.


Transactions for multiple write-operations

TLDR: Have a way to run multiple write-operations, if one of them fails, all is rolled back
Longer version:
The Prisma Client API should provide a way to send multiple write-operations within the same query. The result of the request can be one of two cases:

All write-operations succeeded
No write-operations succeeded

Here is what a possible API for this feature could look like:
const write1 = prisma.user.create()
const write2 = prisma.order.update()

await prisma.transaction([write1, write2])

Note that this feature is not the same as long-running transactions where the submitted mutations depend on each other.

Closing in favor of https://github.com/prisma/prisma-client-js/issues/667

Ping @nikolasburk about a comment that was posted in the replacing issue: https://github.com/prisma/prisma-client-js/issues/667#issuecomment-643750802


feat: Add article list

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


libcalico error breaks teardown

2016-02-09 11:54:54,215 [INFO] CALICOMESOS 53: Received request: {"args":{"container_id":"244a3750-3831-433f-b02a-ab3bd312ad22","hostname":"dl-agent2.c.unique-caldron-775.internal"},"command":"cleanup"}
2016-02-09 11:54:54,216 [DEBUG] CALICOMESOS 74: Executing cleanup
2016-02-09 11:54:54,216 [INFO] CALICOMESOS 336: Cleaning executor with Container ID 244a3750-3831-433f-b02a-ab3bd312ad22.
2016-02-09 11:54:54,219 [INFO] CALICOMESOS 349: Attempting to un-allocate IP <IP_ADDRESS>
2016-02-09 11:54:54,219 [INFO] CALICOMESOS 355: Un-allocate IP <IP_ADDRESS> from pool <IP_ADDRESS>/16
2016-02-09 11:54:54,220 [ERROR] CALICOMESOS 602: 'IPAMClient' object has no attribute 'unassign_address'

I thought unassign_address was removed from libcalico a while back.

Dupe of #57


Possible problem with IgnoringCyclicReferences

In version 2.0.1 the following test was passing:
using FluentAssertions;
using NUnit.Framework;

namespace FluentAssertionTests
{
    [TestFixture]
    public class Tests
    {
        [Test]
        public void ShouldBeEquivalentTo_works()
        {
            var a = new Parent();
            a.Child1 = new Child(a, 1);
            a.Child2 = new Child(a);

            var b = new Parent();
            b.Child1 = new Child(b);
            b.Child2 = new Child(b);

            a.ShouldBeEquivalentTo(b, x => x
                .Excluding(y => y.Child1)
                .IgnoringCyclicReferences());
        }
    }

    public class Parent
    {
        public Child Child1 { get; set; }
        public Child Child2 { get; set; }
    }

    public class Child
    {
        public Child(Parent parent, int stuff = 0)
        {
            Parent = parent;
            Stuff = stuff;
        }

        public Parent Parent { get; set; }
        public int Stuff { get; set; }

    }
}

This test fails in 2.1.0, and it doesn't pass in the latest nuget package (3.2.1) either.
It fails with Expected property Child2.Parent.Child1.Stuff to be 0, but found 1., even though we explicitly stated that property Child1 should be excluded and that we want to ignore cyclic references.
I'm fairly sure that the back reference Child2.Parent should be considered a cyclic reference.
Is there a cycle detection problem here, or am I using FA the wrong way?

Is this still an issue?

I would like to reassess, tomorrow.

Thanks. Let me know.

I ran update-package and got version 3.2.2. The test above does not pass.
I have two questions:

To me it seems like there was a breaking change between 2.0.1 and 2.1.0. I couldn't find any mention of it in the release notes, but that may be me not understanding the problem completely. Do you know/remember why the behavior changed?
If you look at the test, would you think that the test should pass? What do you think is the expected behavior?

Also, I now suspect that the problem I'm facing lies within the configuration. I base that assumption on the assertion message I get:
Expected property Child2.Parent.Child1.Stuff to be 0, but found 1.

With configuration:
- Include only the declared properties
- Exclude property Child1
- Match property by name (or throw)

As you can see, there is no mention of me calling IgnoringCyclicReferences().

I forked and rebuilt the latest om my machine, but no luck. Same behavior as before.
@vossad01 I'm sorry for not getting back to you earlier. Thanks for your input and the advice. In fact, we are already doing what you suggest. It doesn't seem to have any impact on the problem at hand, however.

So in short, I think your unit test initially succeeded because of a false positive. I've enhanced the logging of the configuration to better clarify the actual equivalency configuration that was used. But IMHO, the behavior you're seeing is indeed correct.

@Lette I believe type-based configuration will not work in the example you provided because that configuration does not affect the root/subject object of the assertion (the first argument to the extension method, a in this case).
That exclusion is behavior I spotted a while ago that I think should be changed, but I either need to come up with an entirely new API that does not have that exclusion or it needs to wait to 4.0 because would be a breaking change.
If that would be a valid solution for you it would help by having identified a case "in the wild" where the current exclusion is an issue.  If that would be a solution, we could also provide guidance on how to use FA's extension points to work around the issue with type-based configuration, but those are relatively heavy-weight solutions for this problem.
Regarding the actual IgnoringCyclicReferences question, I do not know how it was implemented in 2.0.1.  However given the current implementation, I do expect this case to fail.  If you are looking for that behavior to change, what would be helpful is a proposal on how cyclic-reference detection should be implemented such that your case would pass.

I can't blame you for closing this issue. I just want to leave you with my thoughts:
The test above fails, since FA decides that the two graphs are not equivalent. If I wrap each of the root objects a and b  (of type Parent) in a new type GrandParent and check equivalence of those two graphs (where the root object now is of type GrandParent), the test does not fail. FA now concludes that the two graphs in fact are equivalent.
This is counter-intuitive, and IMHO wrong. If two graphs are equivalent, then any two sub-graphs of those graphs also must be equivalent. FA thinks otherwise.
I believe that the main culprit here is that FA does not consider the root object when looking for cyclic references. Whether that is something you would consider changing or not is totally up to you, of course. I respect the time and effort you have invested in this tool, and I realize that there might be forces that push you towards the current implementation.
Thank you for all your hard work.

Let me think a


Memory Cache Forever Issue

When implementing a "forever" cache in using the memoryDriver. I recently came across some interesting behaviour, which led to me implementing the other caches in my program incorrectly causing caches to not be hit.
When using the getOrSetForever method. You are currently forced to provide ttl: undefined in the options, since Infinity. is not accepted by the LRUCache library. Without doing this the memory cache defaults to a super short ttl.

However, when using ttl: undefined on other adapters, such as the knexDriver. ttl: undefined is treated as no TTL, and that causes cache misses to occur, so when I implemented that driver I was experiencing cache misses, since it needs to have a default of ttl: Infinity

TLDR: The default TTL on the memoryDriver should be undefined rather than Number.POSITIVE_INFINITY.

Well I wasn't able to reproduce the error on my side. Using Infinity seems to work and doesn't throw any error
But, just in case, I still replaced Infinity with undefined for the memory driver since that's what's seems to be recommended by node-lru-cache.
Thanks for the issue!


Error while adding sqflite in a flutter project - Execution failed for task ':sqflite:parseDebugLocalResources'

The app doesn't run when I add the sqflite dependency to my flutter project. It shows the following error:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':sqflite:parseDebugLocalResources'.
> Could not resolve all files for configuration ':sqflite:androidApis'.
   > Failed to transform android.jar to match attributes {artifactType=android-platform-attr, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for PlatformAttrTransform: C:\Users\theak\AppData\Local\Android\sdk\platforms\android-33\android.jar.
         > C:\Users\theak\AppData\Local\Android\sdk\platforms\android-33\android.jar

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 51s

This is the dependency that I have added to my pubspec.yaml file:
dependencies:
  flutter:
    sdk: flutter
  cupertino_icons: ^1.0.2
  flutter_riverpod: ^2.4.10
  flutter_svg: ^2.0.10+1
  sqflite: ^2.0.0+4

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_lints: ^3.0.1
  flutter_launcher_icons: ^0.13.1

Here is my flutter doctor output:
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.16.9, on Microsoft Windows [Version 10.0.22621.3007], locale en-IN)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.8.6)
[√] Android Studio (version 2023.1)
[√] VS Code (version 1.87.1)
[√] Connected device (3 available)
[√] Network resources

• No issues found!

Error continues to persist. Cannot find help in Stack Overflow, GitHub, Gemini AI or Google.
We have switched from sqflite to ObjectBox database for the following reasons:

Performance: ObjectBox is a NoSQL database, designed to store and retrieve objects directly. Sqflite, on the other hand, is a relational database that requires converting Dart objects to SQL queries. This conversion process can be slower, especially for complex queries. Benchmarks show ObjectBox outperforming sqflite in CRUD operations by a significant margin [various sources].
Ease of Use: ObjectBox uses a more intuitive object-oriented approach for interacting with data. You define your Dart classes and ObjectBox handles the underlying storage. Sqflite requires writing SQL queries, which can be cumbersome and error-prone for developers unfamiliar with SQL.
Data Relationships: ObjectBox can automatically handle relationships between objects, reducing boilerplate code for managing complex data models. Sqflite requires manual creation and management of foreign keys for relationships.

Error has been solved:
Launching lib\main.dart on sdk gphone64 x86 64 in debug mode...
Parameter format not correct -
Running Gradle task 'assembleDebug'...                             83.5s
√  Built build\app\outputs\flutter-apk\app-debug.apk.
Installing build\app\outputs\flutter-apk\app-debug.apk...          16.5s
Syncing files to device sdk gphone64 x86 64...                   1,706ms

android sdk 33 was partially installed. Re-install and everything works fine (even sqflite, but we will be using ObjectBox)


Adding ide importing

Contributes to #
Added IdeImporting from ide-components
Changelog
Use the following command to list changes or manually list out new, changed and
removed files.
 If so I was assigned this issue and already have a PR open for this https://github.com/carbon-design-system/ibm-cloud-cognitive/pull/163

Hi @davidmenendez this PR is just moving across the existing CDAI Import component as-is.

I guess i'm confused about what the difference is between the two components. is the ide import supposed to be separate from the component in the issue that i linked? either way they are both essentially the same thing, so why wouldn't we have a single reusable component?

Many of the designs have changed significantly, but this component does look rather similar. The issue does refer to the existing code:
https://github.com/carbon-design-system/ibm-cloud-cognitive/issues/30#issuecomment-669259813

right, but @lee-chase assigned me #30 and i've been working on that component for some time. perhaps we need to get on slack to discuss this.

There are 2 different components @davidmenendez. The entire integration portfolio of IBM is using components from: https://pages.github.ibm.com/cloud-integration-design/ide-components/?path=/story/ide-home-experience--specifying-custom-card-content, hence we're tackling this task in 2 stages:

move accross the components as are from ide-components into this new repo
converge them all into this new repo into a single set in order to avoid duplication

Base line: yep, they might be similar, but for a flawless and seemless experience, we need integration products to not be affected by this change in any way, hence we're moving them accross as an exact copy first, then we can discuss merging these into a single set of components.
I hope this makes sense. Feel free to get in touch with me or @asfordmatt directly if you do require any more clarification on this PR.

Ok. I was unaware of this. Thank you for sharing that background information.


SharePoint Framework Environment Setup having issues with installing the trust-dev-cert

Category

[ ] Question
[ ] Typo
[ x] Bug
[ ] Additional article idea

Expected or Desired Behavior

If you are reporting a bug, please describe the expected behavior. If you are suggesting an enhancement please describe thoroughly the enhancement, how it can be achieved, and expected benefit.

In the SharePoint documentation ("Set up your SharePoint Framework development environment" at https://docs.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment), I was unable to download the developers certificate following the given steps.
Observed Behavior
After running the 'gulp trust-dev-cert' command, I received the error:
'gulp' is not recognized as an internal or external command,
operable program or batch file.
Was there a command that's needed to add gulp or yo to the path? If so, what is it?
Steps to Reproduce
Run the steps listed on the site.

installed npm lts using the msi installer
npm install -g yo gulp
npm install -g @microsoft/generator-sharepoint
gulp trust-dev-cert

Versions:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
C:\Users\linser1\SPO-Webpart-Tut>node -v
v8.11.4
C:\Users\linser1\SPO-Webpart-Tut>npm -v
5.6.0
Submission Guidelines
Thanks for your contribution! Sharing is caring.

Notice that gulp trust-dev-cert can be exected in a solution folder, so you will first need to scaffold a solution and then be in a folder to execute it. Not optimal, but a one-time thing for an individual computer.


[DOR-77] Add images & working links to cards in related website content component

Ticket URL: https://national-archives.atlassian.net/browse/DOR-77
About these changes
Add a human-readable description here
How to check these changes
Where possible, provide guidance to help your reviewer
Before assigning to reviewer, please make sure you have

[ ] Checked things thoroughly before handing over to reviewer
[ ] Checked PR title starts with ticket number as per project conventions to help us keep track of changes
[ ] Ensured that PR includes only commits relevant to the ticket
[ ] Waited for all CI jobs to pass before requesting a review
[ ] Added/updated tests and documentation where relevant

Merging PR guidance
Follow docs\developer-guide\contributing.md
Deployment guidance
Follow docs\infra\environments.md

I think this is fine. One thing to consider is that we'll be relying on those images not being deleted in beta. It might be less brittle if we include those images directly in the codebase, but I think I am just being paranoid.

I think this is fine. One thing to consider is that we'll be relying on those images not being deleted in beta. It might be less brittle if we include those images directly in the codebase, but I think I am just being paranoid.

I understand your concern but I think we're probably safe for time being, and for the sake of testing this in staging. I think the chances of the images being deleted from beta is pretty unlikely anyway


ClusterLoadAssignment load_balancing_weight with locality seems to behave differently than documentation

The ClusterLoadAssignment documentation suggests the weights of the locality and endpoint are multiplied together to get the effective weight.
https://github.com/envoyproxy/envoy/blob/fd273a65e03cb14cd46891c539b623f4126114f8/api/envoy/api/v2/eds.proto#L46-L48
In my tests, this doesn't seem to be the case. Here is my config:
      "common_lb_config": {
       "locality_weighted_lb_config": {}
      },
      "load_assignment": {
       "cluster_name": "outbound|80||google.com",
       "endpoints": [
        {
         "locality": {
          "region": "us-central3",
          "zone": "us-central1-a"
         },
         "lb_endpoints": [
          {
           "endpoint": {
            "address": {
             "socket_address": {
              "address": "identity-a",
              "port_value": 80
             }
            }
           },
           "load_balancing_weight": 1
          },
          {
           "endpoint": {
            "address": {
             "socket_address": {
              "address": "identity-b",
              "port_value": 80
             }
            }
           },
           "load_balancing_weight": 1
          }
         ],
         "load_balancing_weight": 2
        },
        {
         "locality": {
          "region": "us-central2",
          "zone": "us-central1-a"
         },
         "lb_endpoints": [
          {
           "endpoint": {
            "address": {
             "socket_address": {
              "address": "identity-c",
              "port_value": 80
             }
            }
           },
           "load_balancing_weight": 1
          }
         ],
         "load_balancing_weight": 1
        }
       ]
      }

Based on this, I would expect:
identity-a gets a weight of 2, so 40% of traffic
identity-b gets a weight of 2, so 40% of traffic
identity-c gets a weight of 1, so 20% of traffic
I am actually seeing an even 33/33/33% split though.
Is this a documentation issue or is something going wrong?

The algorithm first selects a locality, then an endpoint from within that locality.
locality A is selected 2/3 of the time
  identity-a is selected 1/2 of the time -> total 1/3
  identity-b is selected 1/2 of the time -> total 1/3
locality B is selected 1/3 of the time
  identify-c is always selected -> total 1/3

It might be a good idea to reword the documentation to be clearer here, PRs would be appreciated.

Ok great, that's how I thought it worked until I read the doc. I'll keep this open for the doc change, I can probably make one soon


Proposal: permit2-integration-template

Description

This is a developer tool, a template that explains the integration of permit2 for kaia developers to easily integrate permit2 in their codebase.
It enables kaia developers to leverage the possibilities of permit2 to build DeFi applications that improve user experience.
It contains an article that explains the architectural overview of the protocol.

Bounty track

Developer tool

Dorahack: https://dorahacks.io/buidl/20054
Repo: https://github.com/PaulElisha/permit2-test-integration

Approved for 2000 KAIA bounty.

Closing for payout


etcdmain: change default GOMAXPROCS when compiling in go1.5

Change default GOMAXPROCS to the number of CPUs available when compiling
in go1.5
This matches how go 1.5 works:
https://docs.google.com/document/d/1At2Ls5_fhJQ59kDK2DFVhFu3g5mATSXqqV5QrxinasI/edit
This is a behavior change in etcd 2.2, and should be mentioned in release note.

When I am addressing comments, I find another method that could reach the same result that I want with fewer codes, and I think it is better. Instead of setting it according to what different go versions do, it exposes the value set by go.
I will update the commit message if the method is good.

LGTM


Implement waitAndType, waitAndCheck and waitAndTap #401

The 3 methods mentioned in the subject line were implemented following the same structure and flow as  waitAndClick. Refactoring for reuse may be appropriate such as using 1 HTML file for all the tests. For the purpose of separating test cases it may also be appropriate to keep them equally segregated but it's something to consider. Please note it was a bit awkward to implement waitAndTap because the tap class derives from the wait class while the click and check class are inherited by the wait class. It may be work reconsidering the line of inheritance in that case. Should the tap class be at the same hierarchy level as click?
Please provide feedback and let me know of any suggested or required changes.
Thanks for the cool js testing repo!
Best,
Jim

Hi @castriganoj thanks for your PR
First off, I would like to explain about the inheritance line (sorry for not having proper documentation on this). It exists only to separate the huge "browser" class into different, manageable files. You can think of that inheritance, not as proper OOP inheritance but some kind of mixins (in fact, mixins would be the appropriate way of doing this, but they do not tend to go well with typescript typing system and they led to extremely complicated code to make them work in the past). So, with this in mind, the inheritance line doesn't follow a strict rule of what inherits what (apart from browserCore being the starting class). As long as it works and tests pass, you can feel free to reorder the inheritance line to maximize code reuse (in fact, technically you could use children methods as well, as a class won't be instantiated until the whole browser is ready) I really want to improve this at some point as it is quite messy. I hope this clarify a bit what's going on there.
Secondly, the CI system is complaining, all tests are passing (congrats!) but some of the linting rules are not passing, you can get a full list of these by executing the following commands:

npm run eslint
npm run tslint
npm run markdown-lint

In retrospect I should automate this process with hooks or something 😅
The linter requested changes are minimal, so I don't think you'll have a problem fixing them

Any updates @castriganoj ?
This PR will soon be closed due to inactivity if no updates are made

Sorry for the delay and thank you for the thorough feedback!
I'll have the updates and responses to your comments in by the end of the week.
@angrykoala

@castriganoj Thanks for the update :smile: I'll keep this open then

Everything looks fine and all the CI checks pass.
Thanks for the update @castriganoj :+1:
I'll need you to change the PR to dev instead of master (sorry for the inconvenience!), after that it'll be ready to merge

Manually merged into dev


Adding a managed behavior to Apps

It would be interesting to add a managed behavior to websocket connections, guaranteeing an uninterrutible release operation to be executed on connection close (success, error, timeout).
Another interest would be to be able to close a connection by releasing the managed.
This behavior can even be extended to regular Http apps.
A proposed API just for the release guarantee "app-wide" would be something like:
private val socketApp =
    SocketApp.open(open) ++                                // Called after the request is successfully upgraded to websocket
      SocketApp.message(echo merge fooBar) ++              // Called after each message being received on the channel
      SocketApp.close(_ => console.putStrLn("Closed!")) ++ // Called after the connection is closed
      SocketApp.error(_ => console.putStrLn("Error!")) ++  // Called whenever there is an error on the socket channel
      SocketApp.decoder(decoder) ++
      SocketApp.protocol(protocol) ++
      SocketApp.release( => UIO[Unit] )

On websocket protocol upgrade, in an HttpApp, we could have something like:
val app =
    HttpApp.collectManaged {
      case Method.GET -> Root / "greet" / name  => ZManaged.succeed(Response.text(s"Greetings ${name}!"))
      case Method.GET -> Root / "subscriptions" => socketApp.toManaged( f: SocketApp => UIO[Unit] )
    }

This supposes that HttpApp is extended to collect ZManaged[R, E, ResponseM[R, E]].
(The release could eventually also contain an environment requirement, to access the SocketApp environment?).
Another interest is that with this addition, we could, by keeping a reference to the created ZManaged and be able to interrupt an http response (useful?) or a SocketApp (i.e. closing the socket) by releasing the managed.
Additionally, as the Server has a managed behavior (server.make returns a managed if I'm not mistaken), it should be very easy to compose in the internal implementation..

Added #866 to support collectManaged. Resources will be release automatically and uninterruptedly when the connection closes.

Feel free to open the issue again incase your use case isn't supported this way.


don't ignore .well-known by default

Copied from https://github.com/expressjs/serve-static/issues/54
Unfortunately the RFC IETF or whoever decided it was a good idea to standardize on a directory that is, by default, hidden. Right?
So when I'm tearing my hair out wondering why my Let's Encrypt certs aren't getting validated....

https://example.com/.well-known/acme-challenge/xxxxxxxxxxxxxxx

It's the darn .well-known givin' me all the troubles.
I'd like to suggest that .well-known (and any other RFC / IETF spec'd dirs) not be ignored by default.
Perhaps the default should be the array ['.well-known'] and you can override that value with true, false, or [] (ignore)?

I'm not sure why you think there is a bug in this module. By default, we do allow that to work, unless you change it to do otherwise. You can even see it working just fine using the simple example at https://github.com/pillarjs/send#small-example and serving up the file in a directory called .well-known (I added root option to make it make more sense; I should do that to the example as well):
$ npm i send
<EMAIL_ADDRESS>node_modules\send
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>
$ cat app.js
// This is the example from the README
var http = require('http');
var send = require('send');

var app = http.createServer(function(req, res){
  send(req, req.url, { root: __dirname + '/public' }).pipe(res);
}).listen(3000);

$ mkdir public

$ mkdir public/.well-known

$ mkdir public/.well-known/acme-challenge

$ echo 'hello!' > public/.well-known/acme-challenge/xxxxxxxxxxxxxxx

$ node app &
[1] 9356

$ curl http://<IP_ADDRESS>:4000/.well-known/acme-challenge/xxxxxxxxxxxxxxx
hello!

If you still think there is an issue, please build upon the reproduction steps I have above and paste the way to reproduce here so I can try it out :)