[Feature request] Sequentially shift numbers in consecutive lines

Description
I'll often have many lines of code that should contain monotonically increasing integer values, 1 per line, often from copying+pasting a single line repeatedly, or from using the Duplicate Line command.
For example, I might have a multi-line SQL string that I've added column index numbers to (which are then used in SqlDataReader.GetFoobar(Int32) (I know I could use column-names, but sometimes it's just easier/simpler to use column ordinals), or a multi-line String.Format call with comments to remind me which args parameter argument corresponds to which format placeholder:
const String MY_SQL = @"
SELECT
    foo, -- 0
    bar, -- 1
    baz, -- 2
    qux -- 3
FROM
    table
";

using( SqlDataReader rdr = ... )
{
    String foo = rdr.GetString(0);
    Int32 bar = rdr.GetInt32(1);
    Decimal baz = rdr.GetDecimal(2);
    // etc
}

or:
String formatted = String.Format(
    format: "hello {0}, why don't you see {1} hiding in trees? because {2]. Why do {1} paint their toenails red? So they can hide in {3}. What's the loudest {4} in the {5}? {6} eating {7}",
    /*0:*/ "<yourName>",
    /*1:*/ "elephants",
    /*2:*/ "they're really good at it",
    /*3:*/ "cherry trees",
    /*4:*/ "sound",
    /*5:*/ "savanna",
    /*6:*/ "giraffes",
    /*7:*/ "cherries"
 );

...but originally those lines would have looked like this half-way through editing:
const String MY_SQL = @"
SELECT
    foo, -- 0
    foo, -- 0
    foo, -- 0
    foo -- 0
FROM
    table
";

...and...
String formatted = String.Format(
    format: "hello {0}, why don't you see {1} hiding in trees? because {2]. Why do {1} paint their toenails red? So they can hide in {3}. What's the loudest {4} in the {5}? {6} eating {7}",
    /*0:*/ , ""
    /*0:*/ , ""
    /*0:*/ , ""
    /*0:*/ , ""
    /*0:*/ , ""
    /*0:*/ , ""
    /*0:*/ , ""
    /*0:*/ , ""
 );

...respectively.
...so having some way of automatically incrementing identical integers in consecutive lines would be nice.

I'm happy to submit a PR for this functionality - though I've previously submitted PRs some of for your other projects but they're still sitting unread :(

Hi @daiplusplus,
can you update to 1.0.20 and check whether it satisfy your needs or not?

Hi,
I was long time looking for that feature and then I found that extension that needed only a little tweak to support that scenario so I tried to create pull request. :)


Jenkins e2e tests: only fail on infrastructure errors and disable colors

Since Jenkins has hopefully been set up properly to read test failures
from junit*.xml files, only exit with a nonzero status when there are
infrastructure failures. If there are only test failures, the nonzero
exit status will be ignored.

After looking at hack/e2e.go, I'm now noticing that it will only ever exit 0 or 1, so the conditional I added in this script doesn't really have any effect. If you'd like, I can remove it.

I was wondering about that. :) Yes, please, it's a bit misleading.
On Feb 17, 2015 5:33 PM, "Jeff Grafton"<EMAIL_ADDRESS>wrote:

After looking at hack/e2e.go, I'm now noticing that it will only ever exit
0 or 1, so the conditional I added in this script doesn't really have any
effect. If you'd like, I can remove it.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/4511#issuecomment-74794151
.

I've updated my branch to just ignore the exit status from Ginkgo. I've also disabled colors in Ginkgo so that the console logs in Jenkins don't have the annoying escape codes.

You need to rebase? Your branch is showing something weird here with a divergence of 13 commits.
Also, can we keep the colors for humans? If you'd like to propose a commit with an env variable to disable them for Jenkins, that's fine, but my intent to re-enable the colors was for human readability.

OK, I think I've cleaned up my branch again. \noideadog
Colors are only disabled for Jenkins - this only changes hack/jenkins/e2e.sh. I very explicitly didn't change anything in hack/e2e.go or hack/ginkgo-e2e.sh so that colors are still enabled when humans run these commands.

LGTM.


Unable to pick up orientation

In my app I have a PDF that can be printed. Because the content of these PDFs can change on a regular basis, they are not cached on the app but printed directly from a URL (server within the network).
Some of these are landscape, some are portrait. Setting the default orientation one way or another isn't going to cut it here. I found an old closed ticket that suggested setting the orientation to null to allow it to work it out at the print end which hasn't worked either.
The only other setting that I am passing is border: false otherwise the pages also go from one full-page print to a page-and-a-bit.
Can someone please assist with this?

With the new release simply don't specify the orientation and the system will automatically choose the best.


Best practice guide

First draft of the best practice guide for haddock in /software/bpg

Why are all .md files duplicated? Is there a spurious space or something behind the name?

@zuzanaj please clean up and remove the unnecessary files. There seems to be differences between some... Don't know which one is the correct one.


Put the Node timeout on SwaggerToSdk to all SDK

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Automation for azure-sdk-for-ruby


[varLib.merger] Limitation in _PairPosFormat2_merge

While trying to build a variable version of Source Sans I ran into this documented limitation,
# Currently, if the coverage of PairPosFormat2 subtables are different,
# we do NOT bother walking down the subtable list when filling in new
# rows for alignment.  As such, this is only correct if current subtable
# is the last subtable in the lookup.  Ensure that.
# TODO: Remove this requirement

I've put together a test ~case~ example in the Source Sans repository in a branch named _PairPosFormat2_merge to help addressing this limitation.

Thanks for the concise test case!!  Looking into it.  I think I know of a simple fix...

Would be great if you can add a test case for it.  Thanks.

Will do. Thanks!

Something isn't right. I've spot-checked a few kern pairs and they're not working in the variable font, whereas they're fine in the master sources. See the FontView screenshots below. The result in CoreText is the same (tested via axis-praxis).

Fix coming soon.
Note that CoreText as far as I know doesn't support GSUB / GPOS variations yet.

Thanks Behdad. The kerning now seems to be working in the Black (master1) but it's still not in the ExtraLight (master0). Do you think that this is now a FontView/FreeType/HarfBuzz issue?

I've made new master fonts that don't have Greek and Cyrillic class kerning and put them in a branch named no-greek-cyrillic-kerning. While building these fonts there was no Attempting to fix OTLOffsetOverflowError message.
The variable font made with these new masters works fine in FontView, in terms of kerning. While building the VF there were two Attempting to fix OTLOffsetOverflowError messages.
I think that based on this we can rule out a bug in FontView.

Thanks Miguel.  I'll debug.
Sorry for not properly testing my fixes.  I'm of very limited time right now :(.

No worries. I appreciate any time you can dedicate to this. I'd do it if I knew how.

Thank you very much for the fix Behdad. AFAICT the GPOS merging of that test variable font is working as expected now 🎉 🏆 🎉 🏆 🎉 🏆
However I'm sorry to say that I have another example v-font that ends up with non-functioning kern pairs 😢  The difference between the set of source TTFs referenced in this issue and my other TTFs
is that the GPOS tables of the former were made via fontmake/feaLib, whereas in the latter they were made via makeotf.
I'm going to add test cases to fontTools for the examples that are working, and then provide test files that will show what's not working. I'll open a new issue instead of reopening this one, since I don't know if it's the same exact problem.

Thanks. I'll take a look.


MouseTracker should start with tracking on

Currently the MouseTracker doesn't do anything until you call setTracking(true) on it. This is a poor default behavior.

:+1:

I'll wait a bit in case there's any strong objections to this change...

@iangilman
I don't think anyone's going to notice this change.
We do have at least one place in OpenSeadragon that can defer tracking, so I'll make the default on but add then look for a startDisabled flag in the creation options.
Sound ok?

Sounds great :-)

Fixed by #576


Create simple_agent.py

A sample code for an agent with Python api

@nickpnmrv, thanks for this nice addition! Could you rewrite this so that it uses environment variables instead of configuration files or hardcoded values? The dotenv library is quite useful for that and already listed as a requirement. See the other samples for reference.


Delete old notebook

The example-creation notebook is written in great haste and does not really contribute with anything not covered in the The Experiment Container notebook.
@QCoDeS/core

This looks fine but there is a link to this notebook in https://github.com/QCoDeS/Qcodes/blob/master/docs/dataset/introduction.rst that needs to be replaced

Whoops, that is a good point!


diagonal traversal of binary tree

Added C++ program for diagonal traversal of binary tree

Update the CONTRIBUTING.md
Read the README.md file again.
Update it in this PR only.
No need to create new PR @sahilsujeet1
Update it asap .Will Proceed for further verification.

PR accepted @sahilsujeet1
Successfully merged to HacktoberFest_22 repo.
🚀🚀👍


Resolvers not working with Query:

My resolver looks like this and it doesn't work:
export default {
  Query: {
    authors: () => {},
  },
}

But it works when I set it like this:
export default {
  authors: () => {},
}

I'm merging this way:
const rootValue = mergeResolvers(fileLoader(path.join(__dirname, './src/graphql/resolvers')));

Am I doing something wrong?

These are my types
type Author {
  id: ID!
  firstName: String!
  lastName: String!
}

type Query {
  authors: [Author]
  author(id: ID!): Author
}

Thanks @igor-ribeiro. Sounds like a bug. We'll look into this as soon as we can.

Hey @igor-ribeiro,
How many resolvers are there in your './src/graphql/resolvers' folder? My initial thought here is that you're trying to use mergeResolvers with a single resolver.
If that's the case, you should be seeing a deepmerge error, something like Error: first argument should be an array with at least two elements.
Is this it? If not, please paste the error you're getting.
Thanks!

Hi @RodMachado ,
At first I got this error, but now I have more resolvers. I'm not getting any errors, but I get null as a result.
For example, I have this resolver: author: () => []. When I set it inside a Query property and query  users { id } I get users: null. Removing the Query I get the expected result users: []

I had a console.log inside the resolver and I figured out that it's not called when is defined like
{
  Query: {
    authors: () => {
      console.log('authors resolver'); // doesn't work
      return [];
    },
  },
}

{
  authors: () => {
    console.log('authors resolver'); // works
    return [];
  },
}

Hey @igor-ribeiro,
I'm still not sure about what is happening. Can you show your server configuration?

@RodMachado I created a repo for better investigation: https://github.com/igor-ribeiro/graphql-server-example

Hey @igor-ribeiro,
It turns out that when you use graphqlHTTP you don't really need to have separate keys for Query/Mutation/Subscription in your resolvers object. All you need is to pass a function for each API endpoint. That's why what you were trying is correct.
Our documentation needs to be fixed to warn people about this.
Thanks for catching it!
Cheers!! 🍻

Our documentation needs to be fixed to warn people about this.

@igor-ribeiro Would you like to make a PR and to become a contributor? If not, I can go ahead and do it. :)

I have separate type and resolver files for each db model. I'm using the fileloader to load/merge them. I put a throw Error("...") in my resolver, it never hits. Graphiql queries are always null. So this exact thing is happening to me now. What is the solution?

Nevermind, I resolved the issue. Was missing "resolvers:" attrib name in the makeSchema...
    const schema = makeExecutableSchema({ typeDefs: mergedTypes, resolvers: mergedResolvers });

Thanks @locohost!


CLI and modelPropertyNaming

Hello,
Is there a way to use modelPropertyNaming with CLI? I went through the code and I'm missing how to use it. Very nice feature which our team would gladly benefit :)

Hi @gocjp ,
thanks for creating an issue :) . I just released version 1.7.0 with CLI option --modelPropertyNaming="camelCase" (or "PascalCase")


#540 - Create Labeled Pro Features for Circles

Adds creating features on enter for Circles Tab in Pro
See: #540 - Should look like with this branch/PR  (NOTE: includes just the layer "Lines of Bearing" from PR #563 - there is no other support in PR for LOBs)

Compiled this branch, verified working in DD add-in.


Alternative to using in-memory collection

When I load from an index with
model = RAGMultiModalModel.from_index(index_path=index_name)
then I get the following message

You are using in-memory collection. This means every image is stored in memory.
You might want to rethink this if you have a large collection!

I am not sure what the alternative is to using in-memory collection. I browsed the source files without finding anything.
Is there a way to use a database or any other persistent storage?
Thanks,
Carsten

This is poorly phrased, thank you for phrasing. in-memory collection here doesn't refer to the embeddings (there are DB providers, such as Vespa, and byaldi itself will eventually integrated better storage mechanisms if it doesn't become mainstream quickly enough among DB providers), but to the base64 encoded images. When not using in-memory collection, you'd need to store them somewhere else yourself, and use the mapping (i.e. retrieve page X of document Y) to be able to send it to an LLM. With in-memory collection enabled (which is done at indexing time), you don't need to do so, as we save the base64 version of images within the index. This is costly in terms of memory/storage, but also pretty convenient.
I'll update the doc and message to make this clearer.

Hi, love byaldi :)
Can you add an example of usage for the in-memory collection?
Reading the above answer I think I'm over complicating my demo, I do this:
def get_document_pages(index_fetch_res: list):
    index_mapping_to_files = RAG.get_doc_ids_to_file_names()
    for doc_id, file_name in index_mapping_to_files.items():
        index_mapping_to_files[doc_id] = Path(file_name).stem

    pages = []
    for res in index_fetch_res:
        doc_id = res["doc_id"]
        page_num = res["page_num"]
        page_path = Path("images-financial") / Path(index_mapping_to_files[doc_id]) / Path(f"page_{page_num}.png")
        pages.append(page_path)

    return pages

img_pages = get_document_pages(results)

Where results are the documents returned by the RAG.search().
Then, in order for the images to be passed to the vlm, I have:
def get_answer(prompt:str, images:List[str], top_1=True):
    if top_1:
        imgs_data = [Image.open(images[0])]
    else:
        imgs_data = [Image.open(image) for image in images]
    # model is instantiated elsewhere
    response = model.generate_content([*imgs_data, prompt])

    return response.text

def answer_query(prompt, images, top_1=True):
    return f"Gemini Response\n: {get_answer(prompt, images, top_1=top_1)}"

As you can see, I have the image pages for my documents saved on the file system, and I need to go get those files and open them via the PIL library.
My next step is to save the embeddings in a vector db (and I did not understand how to do this actually), but it would be great also not to fetch image files if they are in memory as base64.
Thanks!

@fvisconti Hi I'm also working on storing the embeddings into a vector database, but rightnow I dont think Byldia provides any way to store them directly to a vectorDB(like ChromaDB), alternatively we can save the embeddings from the .pt file that stores the embeddings locally, but yes its more better with vectorDB for direct loading.
Otherwise I think we have to check for other notebooks having integration examples with qdrant,vespa,milvus,astradb and weaviate for now. This is given in the repo of colpali.
I want to know if you have found any way for this?

@fvisconti Hi I'm also working on storing the embeddings into a vector database, but rightnow I dont think Byaldi provides any way to store them directly to a vectorDB(like ChromaDB), alternatively we can load the embeddings from the .pt file that stores the embeddings locally to a vectorDB's Collection, but yes its more better with vectorDB for direct loading. Otherwise I think we have to check for other notebooks having integration examples with qdrant,vespa,milvus,astradb and weaviate for now. This is given in the repo of colpali. I want to know if you have found any way for this?

Hi, I found this from Vespa, which seems definitely what we need. Probably it's not straightforward to integrate with byaldi, I'll have a look during Christmas break.
Cheers!


DB-4068 cherry-pick upstream HttpRequest/ObjectDecoder fixes (4.1.25/bdp 6.{0,7,8})

https://datastax.jira.com/browse/DB-4068
This is a relatively straightforward git cherry-pick -x [...].  The cherry series was selected as discussed in the JIRA issue and applied clean.  The last commit is just capturing mvn versions:set.  That commit's message also records the upstream cherry hashes with their PR/issue/CVE links.

I've force-pushed an amended tip-commit  updating the bom/pom.xml <version> and deleting <scm><tag> versions.  This amendment is structurally identical to the one described here: https://github.com/riptano/netty/pull/22#issuecomment-610328391.


Removing myself as a maintainer

I haven't been doing any maintenance work on this in ages! I'm removing myself.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender


Update to Angular 2.0.0

I suggest to do this after we merge all of our pending PRs that has to be merged. So that we can see where are all the places, the update is causing problem.

I agree. It would also make life hard for everyone else that would have to merge the changes. It is just easier to merge all pending PRs that we can and then do this.

I'm afraid that you cannot wait for all PRs to be merged... this issue would be blocked forever.


Increase search input's right padding & search icon's right margin

Description
I have introduced changes related to search input's padding as well as to search icon's margin.
Related Issues
No related issues.
Changes Proposed
Right now on small screens there can be an issue of search input's placeholder text being displayed under the search icon.

On the screenshot above we can also see that search bar's icon is not consistent with padding of its parent element (input). I've changed search icon's right margin value from 2.5 to 4, so both the left side of input and the right one look the same in terms of their padding.
In order to fix the above-mentioned issue related to placeholder text being displayer under the search icon the right  padding of input element was changed including right margin of the search icon, search icon's width and the same padding from it to the left side which resulted in pr-12.

Checklist

[x] I have read and followed the Contribution Guidelines.
[ ] All new and existing tests passed.
[ ] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

You can do this changes on your recent PR, I have mentioned some changes add this with that.


replace test data and lorem ipsum in english locale

#96

Current coverage is 99.20% (diff: 100%)

Merging #100 into master will not change coverage

@@             master       #100   diff @@
==========================================
  Files            41         41
  Lines          1753       1753
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1739       1739
  Misses           14         14
  Partials          0          0

Powered by Codecov. Last update 4fa189e...8eed065


TestFlight problem

Hello,
sharing to snap as stickers in IOS is working fine in debug and release mode but after upload the app to
Test Flight and tried to share SnapChat  the app crashed.
is there any way to find the problem ?

Uploading RPReplay_Final1632739809.MP4…

https://user-images.githubusercontent.com/80851543/134895208-a91816d3-1672-4b62-9b2a-d0b7889fe2ee.MP4

Hi! Has your Snapchat application been approved by Snapchat on the Snap Developer Portal? You can only use the Staging key on unreleased versions of your app.

yes it is approved,
and the android version works fine.
I tried to run on my iPhone as a release mode it works fine but not working in testflight

when I was using the old MacBook it was working good, but know I am using the new MacBook M1.

I tried to build the IOS version with old mac but still the same problem.

I tried to build the IOS version with old mac but still the same problem

I'm not able to diagnose your problem if you don't provide anything. Please include your Android manifest.xml, your Info.plist and the relevant code that is crashing Snapchat.

AndroidManifest.xml
`<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="com.app.sarahahgift">
<!-- io.flutter.app.FlutterApplication is an android.app.Application that
     calls FlutterMain.startInitialization(this); in its onCreate method.
     In most cases you can leave this as-is, but you if you want to provide
     additional functionality it is fine to subclass or reimplement
     FlutterApplication and put your custom class here. -->
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.WRITE_CONTACTS" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.RECORD_AUDIO"/>
<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />

<application
    android:name=".Application"
    android:label="@string/app_name"
    android:requestLegacyExternalStorage="true"
    android:usesCleartextTraffic="true"
    android:hardwareAccelerated="true"
    android:icon="@mipmap/ic_launcher_foreground">

    <activity
        android:name=".MainActivity"
        android:launchMode="singleTop"
        android:theme="@style/LaunchTheme"
        android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
        android:hardwareAccelerated="true"
        android:windowSoftInputMode="adjustResize">
        <!-- Specifies an Android theme to apply to this Activity as soon as
             the Android process has started. This theme is visible to the user
             while the Flutter UI initializes. After that, this theme continues
             to determine the Window background behind the Flutter UI. -->
        <meta-data
          android:name="io.flutter.embedding.android.NormalTheme"
          android:resource="@style/NormalTheme"
          />
        <!-- Displays an Android View that continues showing the launch screen
             Drawable until Flutter paints its first frame, then this splash
             screen fades out. A splash screen is useful to avoid any visual
             gap between the end of Android's launch screen and the painting of
             Flutter's first frame. -->
        <meta-data
          android:name="io.flutter.embedding.android.SplashScreenDrawable"
          android:resource="@drawable/launch_background"
          />
        <intent-filter>
            <action android:name="android.intent.action.MAIN"/>
            <category android:name="android.intent.category.LAUNCHER"/>
        </intent-filter>

        <intent-filter>
            <action android:name="FLUTTER_NOTIFICATION_CLICK" />
            <category android:name="android.intent.category.DEFAULT" />
        </intent-filter>

        <intent-filter>
            <action android:name="android.intent.action.VIEW" />
            <category android:name="android.intent.category.DEFAULT" />
            <category android:name="android.intent.category.BROWSABLE" />
            <!-- Accepts URIs that begin with YOUR_SCHEME://YOUR_HOST -->
            <data
                android:host="*.sarahah.com"
                android:scheme="https"
                />

                    </intent-filter>
            <intent-filter android:autoVerify="true">
            <action android:name="android.intent.action.VIEW" />
            <category android:name="android.intent.category.DEFAULT" />
            <category android:name="android.intent.category.BROWSABLE" />
            <!-- Accepts URIs that begin with https://YOUR_HOST -->
            <data
                android:scheme="sarahah"
                android:host="*" />
        </intent-filter>

        <intent-filter>
            <action android:name="android.intent.action.MAIN" />
            <action android:name="android.intent.action.VIEW" />
            <category android:name="android.intent.category.LAUNCHER" />
            <category android:name="android.intent.category.DEFAULT" />
            <category android:name="android.intent.category.BROWSABLE" />
            <data android:scheme="com.app.sarahahgift" />
        </intent-filter>

    </activity>

    <activity
        android:name="com.yalantis.ucrop.UCropActivity"
        android:screenOrientation="portrait"
<EMAIL_ADDRESS>    <!-- Don't delete the meta-data below.
         This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
    <meta-data
        android:name="flutterEmbedding"
        android:value="2" />
    <meta-data
        android:name="com.google.firebase.messaging.default_notification_channel_id"
        android:value="high_importance_channel" />

    <meta-data
        android:name="com.snapchat.kit.sdk.clientId"
        android:value="65a7d454-d828-4a66-9b08-9846f3658870" />

    <meta-data
        android:name="com.snapchat.kit.sdk.scopes"
        android:resource="@array/snap_connect_scopes" />

    <activity
        android:name="com.snapchat.kit.sdk.SnapKitActivity"
        android:launchMode="singleTask">

        <intent-filter>
            <action android:name="android.intent.action.VIEW" />
            <category android:name="android.intent.category.DEFAULT" />
            <category android:name="android.intent.category.BROWSABLE" />

            <!-- Change this to match your redirect URL -->
            <data
                android:scheme="sarahah"
                android:host="snapchat"
                android:path="/oauth2" />
        </intent-filter>

    </activity>

    <meta-data
        android:name="com.facebook.sdk.ApplicationId"
        android:value="@string/facebook_app_id" />

    <provider
        android:name="com.facebook.FacebookContentProvider"
        android:authorities="com.facebook.app.FacebookContentProvider[facebook_app_id]"
        android:exported="false" />
    <provider
        android:name="androidx.core.content.FileProvider"
        android:authorities="${applicationId}.fileprovider"
        android:exported="false"
        android:grantUriPermissions="true">
        <meta-data
            android:name="android.support.FILE_PROVIDER_PATHS"
            android:resource="@xml/file_paths" />
    </provider>

    <receiver
        android:name=".CheckoutBroadcastReceiver"
        android:exported="false" />

    <service
        android:name="com.oppwa.mobile.connect.service.ConnectService"
        android:exported="false" />

    <activity
        android:name="com.oppwa.mobile.connect.checkout.dialog.CheckoutActivity"
        android:configChanges="orientation"
        android:exported="false"
        android:launchMode="singleTop"
<EMAIL_ADDRESS>        android:windowSoftInputMode="adjustPan"
        tools:replace="android:windowSoftInputMode"
        />
</application>

`
*note: the android version works fine

info.pilst
`

CFBundleDevelopmentRegion
$(DEVELOPMENT_LANGUAGE)
CFBundleExecutable
$(EXECUTABLE_NAME)
CFBundleIdentifier
$(PRODUCT_BUNDLE_IDENTIFIER)
CFBundleInfoDictionaryVersion
6.0
CFBundleLocalizations

ar
en

CFBundleName
Sarahah
CFBundlePackageType
APPL
CFBundleShortVersionString
$(MARKETING_VERSION)
CFBundleSignature
????
CFBundleURLTypes

CFBundleTypeRole
Editor
CFBundleURLName
app.sarahah.com
CFBundleURLSchemes

com.sarahah.ios
com.googleusercontent.apps.248219105226-t2dmf6216e0m94j03hg69s37drgk8ajf
sarahah

CFBundleVersion
$(CURRENT_PROJECT_VERSION)
FacebookAppID
facebookid
ITSAppUsesNonExemptEncryption

LSApplicationQueriesSchemes

https
http
whatsapp
fbapi
fbauth
fbauth2
fbshareextension
fbapi20130214
fbapi20130410
fbapi20130702
fbapi20131010
fbapi20131219
fbapi20140410
fbapi20140116
fbapi20150313
fbapi20150629
fbapi20160328
fb-messenger-share-api
instagram-stories
facebook-stories
facebook
instagram
twitter
tw
telegram
tg
snapchat
bitmoji-sdk
itms-apps

LSRequiresIPhoneOS

NSAppTransportSecurity

NSAllowsArbitraryLoads

NSAllowsArbitraryLoadsForMedia

NSAllowsArbitraryLoadsInWebContent

NSExceptionDomains

localhost

NSExceptionAllowsInsecureHTTPLoads

NSCameraUsageDescription
To take a picture for your profile photo
NSContactsUsageDescription
To show you contacts who are registered in Sarahah
NSMicrophoneUsageDescription
To record a voice message
NSPhotoLibraryUsageDescription
To upload a profile photo
SCSDKClientId
I remove it from here just for privacy
UIBackgroundModes

fetch
remote-notification

UILaunchStoryboardName
LaunchScreen
UIMainStoryboardFile
Main
UIRequiresFullScreen

UISupportedInterfaceOrientations

UIInterfaceOrientationPortrait

UISupportedInterfaceOrientations~ipad

UIInterfaceOrientationPortrait
UIInterfaceOrientationPortraitUpsideDown
UIInterfaceOrientationLandscapeLeft
UIInterfaceOrientationLandscapeRight

UIViewControllerBasedStatusBarAppearance

com.apple.developer.associated-domains

applinks:*.sarahah.com
applinks:sarahah.com
applinks:sarahah.page.link

`

this the code for the IOS
snapkit.share(SnapchatMediaType.NONE,
                                    sticker: SnapchatSticker(
                                        image: FileImage(File(imagePath))),
                                    caption: "",
                                    attachmentUrl: url)

A few things make sure the ClientId in your AndroidManifest.xml matches the on in your Info.plist and please edit your comment to include more relevant code ie where both imagePath and url get set.

Hi,
I edit the code in the above comment ,
yes my friend i am sure the client Id is the same

Hi,
I share the problem with snapchat team, they said the problem resolved with the new update of the app 11.48
thanks my friend, the code is working now with new update of snapchat

Hi,
I share the problem with snapchat team, they said the problem resolved with the new update of the app 11.48
thanks my friend, the code is working now with new update of snapchat

yes it is approved,
and the android version works fine.
I tried to run on my iPhone as a release mode it works fine but not working in testflight

@gkmuhannad is sticker showing while sharing it to snapchat?

yes it works for me, the problem was from Snapchat

yes it works for me, the problem was from Snapchat

Is your sticker showing in snapchat in android because i can see the link but not sticker when sharing.
Any help would be appreciated.
Thanks


PyTorch model has two-views instead of four?

Hello there,
In the paper you say that the model has four views  and that the pipelines for four views are separate until global average pool and then concatenated. Something like following ASCII art:
R-MLO  |-a1-|-a2-|-a3-|--|--|--|--|--|--| \
L-MLO  |-b1-|-b2-|-b3-|--|--|--|--|--|--|\ \
                                           > >--|--|--|--|
R-CC   |-c1-|-c2-|-c3-|--|--|--|--|--|--|/ /
L-CC   |-d1-|-d2-|-d3-|--|--|--|--|--|--| /

But when I look at the layers for the python model, for MLO and CC, only one layer is defined for each one, instead of two. In the forward phase both MLO and CC images are put forward through same layer. Something like:
L-CC  \           \           \
       \|-a1-/|-a1-\|-a2-/|-a2-\|-a3-/|-a3-|...
R-CC        /           /           /

Which creates a bizarre architecture like:
R-MLO  |-a1-|-a2-|-a3-|--|--|--|--|--|--| \
L-MLO  |-a1-|-a2-|-a3-|--|--|--|--|--|--|\ \
                                           > >--|--|--|--|
R-CC   |-b1-|-b2-|-b3-|--|--|--|--|--|--|/ /
L-CC   |-b1-|-b2-|-b3-|--|--|--|--|--|--| /

Here is the code for conv. layers taken from layers_torch.py

    def __init__(self, in_channels, number_of_filters=32, filter_size=(3, 3), stride=(1, 1)):
        super(AllViewsConvLayer, self).__init__()
        self.cc = nn.Conv2d(
            in_channels=in_channels,
            out_channels=number_of_filters,
            kernel_size=filter_size,
            stride=stride,
        )
        self.mlo = nn.Conv2d(
            in_channels=in_channels,
            out_channels=number_of_filters,
            kernel_size=filter_size,
            stride=stride,
        )

    def forward(self, x):
        return {
            "L-CC": F.relu(self.cc(x["L-CC"])),    # [Addition] (1)
            "L-MLO": F.relu(self.mlo(x["L-MLO"])),
            "R-CC": F.relu(self.cc(x["R-CC"])),    # [Addition] (2)
            "R-MLO": F.relu(self.mlo(x["R-MLO"])),
        }

Notice that in lines (1) and (2) L-CC and R-CC is forwarded from the same layer.  Also the same issue for R-MLO and L-MLO.
Here is what I get when I try to reach for the first layer in the model, there is only two conv layers instead of four. Therefore, the model effectively has two views, not four.
model._conv_layer_ls[0]
Out[20]:
AllViewsConvLayer(
  (cc): Conv2d(1, 32, kernel_size=(3, 3), stride=(2, 2))
  (mlo): Conv2d(1, 32, kernel_size=(3, 3), stride=(2, 2))
)

For TF however, the layers seems to be in line with the paper:
def all_views_conv_layer(input_layer, layer_name, number_of_filters=32, filter_size=(3, 3), stride=(1, 1),
                         padding='VALID', biases_initializer=tf.zeros_initializer()):
    """Convolutional layers across all 4 views"""

    input_l_cc, input_r_cc, input_l_mlo, input_r_mlo = input_layer

    with tf.variable_scope(layer_name + "_CC") as cc_cope:
        h_l_cc = tf.contrib.layers.convolution2d(inputs=input_l_cc, num_outputs=number_of_filters,
                                                 kernel_size=filter_size, stride=stride, padding=padding,
                                                 scope=cc_cope, biases_initializer=biases_initializer)
        h_r_cc = tf.contrib.layers.convolution2d(inputs=input_r_cc, num_outputs=number_of_filters,
                                                 kernel_size=filter_size, stride=stride, padding=padding, reuse=True,
                                                 scope=cc_cope, biases_initializer=biases_initializer)

    with tf.variable_scope(layer_name + "_MLO") as mlo_cope:
        h_l_mlo = tf.contrib.layers.convolution2d(inputs=input_l_mlo, num_outputs=number_of_filters,
                                                  kernel_size=filter_size, stride=stride, padding=padding,
                                                  scope=mlo_cope, biases_initializer=biases_initializer)
        h_r_mlo = tf.contrib.layers.convolution2d(inputs=input_r_mlo, num_outputs=number_of_filters,
                                                  kernel_size=filter_size, stride=stride, padding=padding, reuse=True,
                                                  scope=mlo_cope, biases_initializer=biases_initializer)

    h = (h_l_cc, h_r_cc, h_l_mlo, h_r_mlo)

    return h

Is this perhaps an oversight or am I missing something? Does this pytorch model achieve similar accuracy in the dataset?
Thanks.

Hi Utku,
You are right that there are 4 separate processing columns (for the four views), but only 2 CNN "modules" (CC/MLO). This is explained in the paper:

First, we tied the weights in the corresponding columns, i.e., the parameters of the columns processing L-CC and R-CC views were shared as were those of the columns processing L-MLO and R-MLO views.

Reusing the (e.g.) CC module for both L-CC and R-CC inputs is equivalent to the desired weight-sharing. The implementation for the TF version similarly shares weights, but TF has different semantics so it's explicitly expressed as two separate computational nodes.
Incidentally, I have been following your work on implementing visualization/interpretability methods, and I'm wondering if you were trying to apply https://github.com/utkuozbulak/pytorch-cnn-visualizations to this. I also tried that! But if I'm guessing right, you also encountered issues with not being able to separate the gradients for the two forward passes on the same module.
Le me know if this answers your question.

Hello Jason,
Oh, so I was indeed missing something. I see your point! I think I was kind of deceived by Fig.3 where the figure is more likely to be interpreted as views having separate pipelines. Sorry for that.
No, I wasn't planning to use the vis. techniques there. I have a few weird ideas that I want to test on multi-view models but like you said, I think separating the gradients will be a problem. But... Thinking about it again, after the training phase is done we can duplicate two pipes (CC and MLO) which will allow us to keep track of gradients for each image. It will be similar to the architecture below but a and b, and, c and d will have the same weights. This way we can track the gradients without breaking the overall behavior of the model. Although the size of the model will be almost double what it is now.
R-MLO  |-a1-|-a2-|-a3-|--|--|--|--|--|--| \
L-MLO  |-b1-|-b2-|-b3-|--|--|--|--|--|--|\ \
                                           > >--|--|--|--|
R-CC   |-c1-|-c2-|-c3-|--|--|--|--|--|--|/ /
L-CC   |-d1-|-d2-|-d3-|--|--|--|--|--|--| /

This definitely answered my question, thank you for your time!


Specify python limitation in this doc

I have found a post in power bi community of a user asking for python in publish to web and the doc doesn't specify it. It does specify R. I think it's a good idea to include it in the same sentence.

@ibarrau : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@maggiesMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @maggiesMSFT Could you review this pull request? Thanks!

Thanks, @ibarrau ! Good suggestion. Done.
Hi, @ktoliver - yes, I was just confirming. Thanks!
@sign-off

Thanks!


Fonts on different pages don't match.

Vulnerabilities page has fonts in the .scss file that aren't being used in Developers, Code, Releases, etc.

confirmed working. closing


example Rholang contracts: RHOL-44 Voting etc.

RHOL-44 Example contract: Voting: 3 story points
RHOL-45 Example contract: Safe Remote Purchase

On Jan 8 in #176, @MParlikar  said "in flight" but I can't find the work-in-progress. @AbnerZheng, pointer please?
ref: Jira Bounties

i started on RHOL-45, https://github.com/flowpoint/rholang_playaround/blob/master/safe_r_p.rho

busy week, have the safe remote purchase working for the rholang erc20 here, it needs review.
i hope good enough. cleanup + documentation will come.


AMA/MMA support planning for SUSE 15 SP3

Regarding to AMA/MMA supported operating systems list, we found there is SUSE 15 SP4 supported already, but we didn't see SP3 on the list. Does SP3 will be supported in the roadmap and when will it be released? Thanks.
Operating system | Azure Monitor agent  | Log Analytics agent | Diagnostics extension
SUSE Linux Enterprise Server 15 SP4 | X |   |
SUSE Linux Enterprise Server 15 SP2 | X |   |
SUSE Linux Enterprise Server 15 SP1 | X | X |

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

ID: bd3dca2f-629d-36e9-f0f0-8c7e64cc04ab
Version Independent ID: f40ee991-6cb8-1eee-9a35-ebc5833d7c7f
Content: Azure Monitor Agent overview - Azure Monitor
Content Source: articles/azure-monitor/agents/agents-overview.md
Service: azure-monitor
Sub-service: agents
GitHub Login: @guywi-ms
Microsoft Alias: guywild

@tinaling
Thanks for your feedback! We will investigate and update as appropriate.

@tinaling Thanks for your feedback. SUSE 15 SP3 is supported. We will update the document accordingly.

Thanks for your feedback and follow up.
Look forward to seeing the update.
SwathiDhanwada-MSFT @.***>於 2022年9月27日 週二，下午8:20寫道：

@tinaling https://github.com/tinaling Thanks for your feedback. SUSE 15
SP3 is supported. We will update the document accordingly.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/98756#issuecomment-1259424974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7BOMKZV2BO7JUF4TYPAE3WALQ7BANCNFSM6AAAAAAQRXANXI
.
You are receiving this because you were mentioned.Message ID:
@.***>


[Epic] Python client implementation for Gravitino

Describe the proposal
This issue tracks the work of implementing the Python client for Graviton. With this Python client, Data scientists could manipulate metadata from Graviton to the underlying systems.
Task list

[ ] Proposal design document
[x] #2229 @Lanznx
[x] #2756 @xunliu
[ ] #2230 @SophieTech88
[x] #2251
[x] #2252
[x] #2253
[ ] #2254
[ ] #2255
[x] #2470 @coolderli
[x] #2518
[ ] #2549
[ ] #2550
[x] #2770
[x] #2929

hi @SophieTech88 , @FrankYang0529
Can you help me refine the Proposal design document ?

CC @coolderli FYI

@noidname01 if you're interested in Python part, can you please continue working on the missing parts in Python to be feature consistent with Java, like table-related APIs. Thanks a lot.

@jerryshao Sure, but after the meeting with @xunliu, we think that it's better to continue client-python feature development after Java client refactor has finished.


Make İ make complex numbers

Closes #1390

I wanted it to be 1 byte because normal complex syntax is 1 byte, and the num-num overload of I updot was useless anyway.


libc: newlib: add config to use custom sbrk

Add a config to use the custom _sbrk function, defined by a user.
It is possible that an application doesn't want to use the entire remaining RAM for the heap.

Friendly ping.

@niedzwiecki-dawid - we are in feature-freeze at the moment / bugfixes only, so it could be a bit of time before this is merged or reviewed.

@stephanosio please take a look.

This will also need to disable malloc_prepare and also eliminate z_malloc_partition.

This will also need to disable malloc_prepare and also eliminate z_malloc_partition.

Done. Sorry for the rebase.

@niedzwiecki-dawid - an alternative to modifying sbrk is to adjust the app with a `boards/.overlay" file. In that file, one could reduce the size of the primary memory node and create a separately labeled block for dedicated memory.
It's certainly cleaner than hacking a custom sbrk.

@niedzwiecki-dawid - an alternative to modifying sbrk is to adjust the app with a `boards/.overlay" file. In that file, one could reduce the size of the primary memory node and create a separately labeled block for dedicated memory.

Agree, but that's a case when a size of dedicated block is fixed. In my case, the amount of memory used at the end of RAM is dynamic, it depends on what happens in the application.

This will also need to disable malloc_prepare and also eliminate z_malloc_partition.

Done. Sorry for the rebase.

No worries for the rebase; it is the way things go :-)
There are still a few dangling bits; like Z_MALLOC_PARTITION_EXISTS in libc-hooks.h?

This will also need to disable malloc_prepare and also eliminate z_malloc_partition.

Done. Sorry for the rebase.

No worries for the rebase; it is the way things go :-)
There are still a few dangling bits; like Z_MALLOC_PARTITION_EXISTS in libc-hooks.h?

Done, thanks. Am I missing anything else?

Friendly ping :-)

Is anything missing to merge this PR?


[release1.8] add ignore reconcile annotation to Operator CR  (#29378)

manual cherry-pick of https://github.com/istio/istio/commit/aaf3a601512681e66e9d1874110b27e69ed1c249

add annotation to installed-state CR and ignore during reconcile

skip the post install test for operator only

@richardwxn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio_release-1.8
61c3a9f84513d325fb512afd516c7d42d2677399
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.8

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.

Note that for release1.8 the postsubmit test did not fail because of operator test before, so this change does not contain the part that bring back the disabled test so should be safe to merge: https://prow.istio.io/?repo=istio%2Fistio&type=postsubmit


"poudriere ports -uv" should exit with a non-zero status for a git+https tree when you have "unmerged files"

Prerequisites

[X] Have you checked for an existing issue describing your problem?
[X] Are you running the latest version?
[X] Is your ports tree recent?
[X] Is your FreeBSD Host on a supported release?

Describe the bug
Updating a git+https ports tree that has unmerged files prints  errors but exits with status 0.
How to reproduce
Run:
poudriere ports -uv -p current
which outputs:
[00:00:00] Updating portstree "current" with git+https...error: Pulling is not possible because you have unmerged files.
hint: Fix them up in the work tree, and then use 'git add/rm <file>'
hint: as appropriate to mark resolution and make a commit.
fatal: Exiting because of an unresolved conflict.
 done

And the exit status is 0.
Expected behavior
It's all good except it should exit 1 (or any other non-zero value)
Screenshots

Environment

Host OS [12.2 amd64]:
Jail OS [12.2 amd64]:
Browser: [firefox]:
Poudriere Version [3.3.6]:
Ports branch and revision [main 975c4836a6e01d1e62e4f075d1d00c7c3c59f196]:

Additional context

928ba1974dca3521508f9ae08200f00c25c2c6bf fixed this


Set extra.executed_at field of transactions

Summary:

Set extra.executed_at field of transactions when executed
Use extra.executed_at field in triggered functions
Save executed_at field in transaction pool
Convert transactions to an executable form (i.e., instance of 'Transaction') before being executed
Disable console logging by default to see clean messages of test cases
Remove unused code for batch transaction
Remove some redundant parameters

#287

Comments address, PTAL @liayoo

Thanks for addressing the comments & sorry for my vague comment above 😅 LGTM!

@liayoo Thanks for the fast review! Now merging..


Try the same summarization code with a 70B model

Problems with AWS endpoint timeouts. Endpoint does not support more than  500 new_tokens. Not enough for the required summary.


Fix libpod to use given CGroup parent instead of a hardcoded one

We default container.config.CgroupParent to the same hardcoded value, so in cases where a CGroup parent was not explicitly set this will do the same thing.

LGTM

bot, retest this please

LGTM, smoketested seems to have smoked too much again.

bot, retest this please

Tests green, merging
@rh-atomic-bot r=TomSweeneyRedHat


[Algo]: Add Bubble Sort in Java

Can this issue be assign to me?

Assigned 😃 @flamespt

can i do this one? is @flamespt  still working on it?


Add a global Promise polyfill.

Fixes https://github.com/zeit/next.js/issues/975
This is needed because Webpack2's dynamic loading(common chunks) code
depends on Promise.
So, we need to polyfill it.
See: https://github.com/webpack/webpack/issues/4254

How can users configure using their own implementation? E.g bluebird which is downloaded 500k times/mo

You can simply import and use it.
This is a polyfil babel already ships and we use it.
So, this gives us zero overhead.
And core-js is also so popular since it's used inside babel.

@arunoda good idea. Do you want me to merge or are you waiting for something else?

@impronunciable I think let's merge this.

@arunoda  Thanks for this fix, but since it's not in the newest release I have to add my own polyfill for now. Can I just ask when this fix will be released so I can get rid of the the script?


Installing PowerToys doesn't automatically install .NET Core

It looks like powertoys should depend on dotnet-sdk?

You must install .NET Runtime version 5, NOT 6
I also had to manually download, as I didn't want to enable "Versions" repository.
Someone should include this in setup procedure.
https://dotnet.microsoft.com/en-us/download/dotnet/5.0/runtime

Just as an update to this in case it helps anybody: I have installed PowerToys v0.64.1 through Scoop and I wasn't able to open the FancyZones editor. I had to install dotnet6-sdk from the versions bucket to get it to run. Specifically dotnet-sdk-6.0.403-win-x64


Allow automatic generation of AWS CodeArtifact tokens

@stuartwdouglas Do you want the code from Aphelia that deleted the package before attempting publishing (to avoid https://docs.aws.amazon.com/codeartifact/latest/ug/packages-overview.html#package-publishing-overwrite-assets) ported as well? Or leave that until needed?

I think we will need it at some point, but lets not worry about it right now.


ARROW-12543: [CI][Python] Fix test-conda-python-3.9 build (gdb version conflict)

@github-actions crossbow submit test-conda-python-3.9

As I suggested on the JIRA, you could also install gdb using apt-get in the base conda.dockerfile. There's no need to get it from conda-forge.

@github-actions crossbow submit test-conda-python-3.9


AGDIGGER-63

Update to create an s2i build for the  android sdk
Motivation:
With the jenkins openshift platform the mounting of an external PV for the android sdk for each instance of a slave proved to be problamatic.
A new approach is to use a s2i image to include the installed sdk.
The thinking here was to allow the admin user to download install and accept the license agreement.
The s2i build would then include the sdk into a s2i slave base image. The resultant image would then be uploaded to the internal docker openshift registry.
Changes:
A new directory structure was included into the repo , with all the valid scripts and Dockerfile to realize this functionality
Goals:
The final goal is to use the slave base s2i image within an ansible script to automate various versions of the android sdk
JIRA:
Refer to https://issues.jboss.org/browse/AGDIGGER-63

@matzew @wtrocki Please review.
I have also created a PR for the upstream https://github.com/openshift/jenkins/pull/214

ping @aliok - just to get familiar with idea and changes we doing!

will review as soon as I can!

@wtrocki - I have updated the PR with a run script. I was chatting with Ben Parees , the s2i image must have a build script. I also added a BUILD_S2I envar - this ensures the build assemble script will be called and not the original entry point /usr/local/bin/run-jnlp-client. I have closed the upstream PR as it is not needed now. I still need to do an end-to-end test though

@luigizuccarelli - Is upstream team interested in s2i capability?
In relation to your issues with checking git source code - that's bug.
You should use https url initially because ssh setup is not working properly.
I going to log ticket for that. Sorry for delay in this - I just did not realized that this was a problem because I used http in my jobs.

@wtrocki - Ok I will use https to test it out. Ben made no mention or showed any interest so I'm not going to push it

@wtrocki - Ok update and rebased - one final look please

@luigizuccarelli let's publish image to dockerhub using different label. For example: sdk24-sti then we can verify that on public cluster and change references in default kubernetes pod configuration as part of this ticket. Rebase(squash/rename) recommended for some commits.

@wtrocki @aliok - I will merge and close once I have done sync meeting with Ali tomorrow

@luigizuccarelli - we done quite productive review here and I'm really confident that logic here is really solid. Going to merge it to avoid long running PR and merge conflicts. We can extend this in different PR's. I'm going to do some standard cleanup in this repo and it would be nice to include this as well.


form object still empty after append()

I'm trying to implement form-data into my next.js application with serverless on backend, and in action i have the following code for uploading the csv file.
let FormData = require('form-data');

export const uploadCsv = file => dispatch => {
  // console.log({file})
  let form = new FormData();
  form.append('file', file);
  // console.log({form})
  form.submit(url, (err, res) => {
    if(err) console.log(err)
    console.log(res.statusCode) // should be 200 if file is successfully uploaded
  })
}

console.log({form}) show an empty form object even after i append data into it. So when i do submit(), it give me an error form.submit() is not a function. can someone help me out please?

Can you try to run this code as a standalone file in nodejs?
Since next.js bundles your code with browser in mind, it might be pulling browser version of form-data, which expects browser built-in version to be present.
https://github.com/form-data/form-data/blob/master/lib/browser.js

It looks like that in angular is the same issue.
Electron application: angular works in a render process. NodeJs is available, however creating new FormData object produces the empty object instance

@glani FWIW I came across the same problem using Electron.  I was able to get electron to load the Node version instead of the browser version by including form-data in the externals field of the webpack config.  But then it didn't work for me anyway because streaming doesn't work in the browser version.
The final way that worked was to post the form from the main process instead of the renderer process (since the main process is pure Node and form-data works fine), and use electron's IPC for the renderer process to ask the main process to do the post.


fix: add legacy/simple door sensor value to restore old behavior

https://github.com/zwave-js/node-zwave-js/pull/5394 introduced a change for the Door state notification variable that was more breaking than anticipated, due to applications automatically generating binary sensors for two-state notification values.
This PR adds a new value Door state (simple) which only has two states and behaves just like the now 4-state Door state variable did before:

Value sent from device
Door state
Door state (simple)

open
open (22)
open (22)

open in regular position
open in regular position (5632)
open (22)

open in tilt position
open in tilt position (5633)
open (22)

closed
closed (23)
closed (23)

@zwave-js-bot automerge


Add functionality to expand and collapse all property rows.

This PR fixes #20741 by adding the ability to expand or collapse all property rows for an execution plan. This functionality was added to single execution plans and to execution plans being compared.
Single Execution Plan Properties:
Expand all properties:

Collapse all properties:

Compared Execution Plan Properties:
Expand all properties:

Collapse all properties:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 32 (31.25%)  changed or added relevant lines in 2 files are covered.
87 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.005%) to 42.358%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/contrib/executionPlan/browser/executionPlanPropertiesView.ts
0
7
0.0%

src/sql/workbench/contrib/executionPlan/browser/executionPlanPropertiesViewBase.ts
10
25
40.0%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/contrib/executionPlan/browser/executionPlanPropertiesViewBase.ts
87
18.25%

Totals

Change from base Build<PHONE_NUMBER>:
0.005%

Covered Lines:
29395

Relevant Lines:
64577

💛  - Coveralls


defaultUnauthorizedResponse doesn't use a schema reference.

security {
    defaultUnauthorizedResponse {
        body<Errors.AuthenticationRequired>()
    }
}

The code above should (in my opinion) create a schema and each protected route would reference that schema's ID. This however is not the case (as seen below)

I'm pretty sure this code might be to blame?
https://github.com/SMILEY4/ktor-swagger-ui/blob/3ac9e7477dbd881413495af42819a63192e1c3c3/ktor-swagger-ui/src/main/kotlin/io/github/smiley4/ktorswaggerui/builder/openapi/ResponsesBuilder.kt#L22-L26

Hi, thanks for reporting this.
True, it should store object schemas in the components section as configured in the schema-generation config.
I fixed the bug with the next version :+1:


RFC: exhaustive-match

The compiler will no longer insert an implicit else None clause in match blocks where all possible types of the match expression are covered by pattern types of the cases.
https://github.com/ponylang/rfcs/blob/master/text/0040-exhaustive-match.md

I have a branch for this, but I have to figure out how to merge #1715 first, since it was based on that branch.


Add mathjax equation for Heidke Skill Score and Cohen's Kappa

Note - I am adding this mathjax, since I'm reviewing the score as part of #486 anyway


Is your feature request related to a problem?
Exploration of useUrlParams()
What we would like:
const UrlCounter = componnet$(() => {
  const params = useUrlParams({ count: 0 });

  return (
    <button onClick$={() => params.count++}>
      {params.count}
    </button>
  );
});

so the above should result in something like http://localhost/?count=123
useUrlParams() implementation
function useUrlParams<T>(initial: T): T {
  const params = useStore({count: 123});
  useWatch$((track) => {
    track(params);
    // put code to update `location.search`
  });
  useClientEffect$(() => {
    // code to listen to the `location.search` change
  }, {run: 'load'})
}

The above is the basic idea. However, the above has an issue, that it will always return a new instance of the params, where as we should have a way to return the same instance no matter how many times it is invoked.
Describe the solution you'd like
function useUrlParams<T>(initial: T): T {
  useWith('container', () => {
    const params = useStore({count: 123});
    useWatch$((track) => {
      track(params);
      // put code to update `location.search`
    });
    useClientEffect$(() => {
      // code to listen to the `location.search` change
    }, {run: 'load'})
  });
}

Having useWith would allow to re-scope the location of the binding code. Namely to a different element or to the container.
New API for listening on location changes
Describe alternatives you've considered
For that reason we should have a way to scope the useStore()
  const params = useStore({count: 123}, {scope: 'container'});

The proposal is to add additional parameter to the useStore which will ensure that the value it returns is scoped to the container. This in effect makes the params a singleton within the application.
The above is not ideal, because the same issue applies to all of the use method.
Additional context
https://hackmd.io/6uyg2L0IQPiCK50MB5WtXA?both

Closing as wont implement.


Throw or log an error for catch block in populate method.

In this bit of code (bundled.js) :
// If the relationship is an array of ids, fetch and resolve an object for each, otherwise just fetch the object.
var promise = Array.isArray(id) ? Promise.all(id.map(function (objectID) {
  return hook.app.service(options.service).get(objectID, hook.params);
})) : hook.app.service(options.service).get(id, hook.params);
return promise.then(function (relatedItem) {
  if (relatedItem) {
    item[target] = relatedItem;
  }
  return item;
}).catch(function () {
  return item;
});

the catch function doesn't give any indication that something went wrong.  I spent several hours debugging this to finally figure out that it was my auth.restrictToOwner({ ownerField: '_id' }) hook which was causing the populate method not to work (since the promise was rejected).  It just kept returning the original result and I couldn't figure out why it wasn't working.
Would it be possible to log or throw an error in the catch here?  Or is there another way I should have known what was happening?
Thanks!

I have no idea why I put that in there at all. I'm pretty sure that catch can be completely removed. Would you mind submitting a pull request? If the tests are passing we'll make a patch release right away.

@daffl Looks like a fix was included in https://github.com/feathersjs/feathers-hooks/pull/81
Thanks!

Yep. Closed via https://github.com/feathersjs/feathers-hooks/pull/81. Thanks @t2t2!

Yep, thanks!
On Mon, May 30, 2016 at 12:21 PM David Luecke<EMAIL_ADDRESS>wrote:

Yep. Closed via #81 https://github.com/feathersjs/feathers-hooks/pull/81.
Thanks @t2t2 https://github.com/t2t2!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/feathersjs/feathers-hooks/issues/80#issuecomment-222523282,
or mute the thread
https://github.com/notifications/unsubscribe/ALS4T35ZAvEjRhYeErKZjLGFBmSTqkDcks5qGw5qgaJpZM4Il7zh
.


Why are some strings quoted?

In the examples, some strings are quoted, and some aren't:
authors:
  - family-names: Druskat
    given-names: Stephan
    name-particle: von
    name-suffix: III
    address: "742 Evergreen Terrace"
    affiliation: "German Aerospace Center (DLR)"
    alias: "sdruskat"
    city: "Berlin"
    country: "DE"
    email<EMAIL_ADDRESS>    fax: +12-3456-7890
    orcid: "https://orcid.org/0000-0003-4925-7248"
    post-code: 90210
    region: Renfrewshire
    tel: +12-345-6789098
    website: "https://research-project.org"

and
abstract: This is my awesome research software. It does many things.
authors:
  - family-names: Druskat
    given-names: Stephan
    orcid: "https://orcid.org/0000-0003-4925-7248"
cff-version: 1.2.0
date-released: "2021-07-18"
identifiers:
  - description: This is the collection of archived snapshots of all versions of My Research Software
    type: doi
    value: 10.5281/zenodo.123456
  - description: This is the archived snapshot of version 0.11.2 of My Research Software
    type: doi
    value: 10.5281/zenodo.123457
keywords:
  - "awesome software"
  - research
license: Apache-2.0
message: If you use this software, please cite it using these metadata.
repository-code: "https://github.com/citation-file-format/my-research-software"
title: My Research Software
version: 0.11.2

What's the logic behind which strings are quoted and which aren't? Some strings with spaces are quoted, some aren't. date-released: sometimes has them, sometimes not.
Is there a simple guide to which ones need to be quoted? Would it make sense to wrap all values in quotes in the examples?

Hi, @edent, and thanks for opening this issue!

TL;DR: For most values it doesn't matter whether you quote them or not, as YAML will treat them as strings unless they conform to another data type or contain reserved characters.

You're right, this may be confusing. There are two points here:

The format that CFF uses, YAML, usually treats things as strings, as long as they don't fit another data type (e.g., a number, or a date/timestamp). Quotes force a value to be interpreted as a string. Therefore, while it is arguably safer to quote everything that should be a string, even more complex examples, such as 10.5281/zenodo.123456 are treated as a string.
The dates that are used in CFF (always in YYYY-MM-DD format, e.g., 2021-08-23) conform to the YAML timestamp data type. However, as the language we provide the schema for validation in, JSON Schema, doesn't "know" these raw datatypes, you have to convert the dates to a string if you write a validation script for example, so that you can use the JSON Schema to validate this against a specific string pattern (basically, YYYY-MM-DD). Hence, it doesn't really matter whether you provide dates in CFF quoted (as string, truly valid CFF) or unquoted (as timestamp, forcibly being made valid by any tooling that uses the schema). This is documented in a comment in the schema.

In general, we had decided to not include this information in the CFF documentation/schema guide, because we thought it may be too confusing for users not familiar with or interested in things like datatypes, and instead link to the YAML docs where this is documented, if not very obvisouly. But perhaps we should document his after all (point in case, @jspaaks)?
What would have helped you, @edent, to avoid the confusion stemming from the mixed-form examples?

OK, that makes sense. I think it would be helpful if all the strings were quoted in examples. That way there's no ambiguity.

The format that CFF uses, YAML, usually treats things as strings,

Sure, it's slightly more typing - but I guess most people don't have an innate understanding of the vagaries of YAML parsing.
Assuming all the strings can be quoted, they should be in the examples. It means people like me don't get stuck wondering where it is appropriate to use them.
Thanks for the swift response - and the brilliant .cff :-)

I’ve spent a bit of time figuring out the answer to the same question. What I found is that if it can confuse YAML, you need to quote it. This basically means if the value has a colon, you must quote it. This is why URL’s are always quoted.
I suspect the same holds if the value starts with a hyphen. I’m not sufficiently familiar with YAML to say if this is indeed the case. I don’t believe a string that starts with a number (e.g., addresses) will confuse YAML.

Assuming all the strings can be quoted, they should be in the examples. It means people like me don't get stuck wondering where it is appropriate to use them.

I think I agree with this, people who don't know YAML or don't feel like looking up the specifics every time can just quote everything, knowing that it'll work, while people who are more experienced / more particular can read an example and omit the quotes while understanding the consequences that may have.
For 1.2.0, we made sure that any key whose value could be interpreted as a number (e.g. month, issue, post-code), is also valid when quoted. See for example:
https://github.com/citation-file-format/citation-file-format/blob/396f738fb025b1d8acdb02a56ffc923f95dc8999/schema.json#L1071-L1082

Additionally, there should be an example for each of the values with mixed types (any of number or string) in the definition in the schema guide. In addition to that, I agree, let's quote all values for "pure" string fields in the guide to avoid confusion.

I respectfully disagree. YAML is supposed to be “human friendly” (quoting from the front page of the YAML website). Quoting everything makes it look like code – not human-friendly.
I spent those 3 hours in that rabbit hole because

let’s face it, YAML is not a well-known language (until I encountered CFF I’d never had to deal with it) so I was just extrapolating from the examples
there’s no explanation of YAML syntax in our schema guide
my first interactions with CFF was through GitHub (this is still the case), GitHub’s error messages are worse than useless
I would have tried to validate my CFF, except none of the validators even run on my system and there are no online validators

I had to read the actual schema.json file and went to the YAML website and read the standard to figure out CFF syntax. I strongly believe if the guide even explained CFF syntax (YAML syntax tailored to CFF’s specific circumstances) a little more it would reduce a lot of confusion.
We also need a good online validator, I believe, and by good I mean the error messages should make sense to someone whose first encounter with YAML is CFF.

I had to read the actual schema.json file and went to the YAML website and read the standard to figure out CFF syntax. I strongly believe if the guide even explained CFF syntax (YAML syntax tailored to CFF’s specific circumstances) a little more it would reduce a lot of confusion.

I see. In 1.0.3, we had a bit about formatting in the equivalent of the schema guide. It said

Formatting
CFF follows the formatting rules of YAML 1.2, of which one of
the most important ones is that the colon (:) after a key should always be
followed by a whitespace.
Structure is determined by indentation, i.e., lines
containing nested elements must be indented by at least one whitespace character,
although using at least two whitespaces as a standard for indentation preserves
readability.
Value strings can (and sometimes should) be double-quoted, e.g. "string",
especially when they contain YAML special characters, or special characters in
general. These include:
:  {  }  [  ]  ,  &  *  #  ?  |  -  <  >  =  !  %  @  \

Would something similar be useful?
This would be an alternative route to quoting everything, and I think I'd actually prefer that.
We had originally removed this from the schema guide as it is documented elsewhere (YAML docs),
and we didn't want to duplicate existing information,
but it seems to be something that would increase user-friendliness of the resources.

We also need a good online validator, I believe, and by good I mean the error messages should make sense to someone whose first encounter with YAML is CFF.

Yes, we do, and we're trying to get this work funded as well. (Similar to the new version of the initializer website.)


Handling expired tokens

In the middleware that checks the Authorization header, if the token is expired we are currently sending back a 401 Unauthorized response.  I don't think that should be handled here.  If it's an unprotected resource that doesn't require auth, shouldn't we treat it the same as if it were some anonymous user?  I think that a requireAuth hook should probably handle whether or not that request is rejected.  Any thoughts otherwise?

I'm going to fix this so that all authorization is handled through hooks.  When an expired token is provided it will allow the request to go through as it would for an anonymous user instead of punishing those who have expired tokens.

At first I wasn't sure but I think I know what you are getting at here. In the decoupling branch I've moved this to a hook called verifyToken that can be registered as opposed to blanket middleware. It is currently registered as a before hook on the /auth/token service.
My question though now that I think about is, we probably want to always check to see if there is a token (like you were doing) and attempt to validate it only if it is there. Otherwise just move on to the next hook.
The reason being is that the end user would use req.user in middleware or params.user in hooks to do any authorization but because we aren't using sessions you need to "authenticate" the user on every request.
So my proposal is actually that we have middleware that fires before any other, that attempts to authenticate the user if a token was passed in, otherwise it just moves on through.

That makes sense to me.  We can use a decodeToken hook that does only that, then use the requireAuth- or requireAuthForPrivate-type hooks to control access.

Ya that what I was thinking but decodeToken would be middleware that is applied to any route. Basically global middleware, otherwise we'd have to explicitly add a decodeToken hook to each service the developer wants to protect.
Now that I type that out, maybe that's not such a big deal???

Yeah.  It's not a big deal to do
service.before({
  all: [
    hooks.auth.decodeToken(),
    hooks.auth.requireAuth()
  ]
});

I think having it be explicit, and not automatic, will be more helpful in the long run.

k :+1:. That's makes it super easy then. If that's the case then we could just use:
service.before({
  all: [authHooks.verifyToken()]

You wouldn't even need the requireAuth call.

That works.  Then decodeToken would only be needed if you want to implement some kind of custom access control logic, then.

Alrighty, so this is how this works now...
messageService.before({
  all: [
    authHooks.verifyToken({secret: 'feathers-rocks'}),
    authHooks.populateUser(),
    authHooks.requireAuth()
  ]
});

We can't rely on just using the req.feathers.user middleware hack because we aren't using sessions. So we need to decode the token, populate the user from the user id stored in the token payload and then check hook.params.user. This should work well for when we do introduce sessions because then it won't matter which way the user authenticates.

Looks really good!


feat: maybe need a reset button

By the way, even the entire UI will be radically changed!

By the way, even the entire UI will be radically changed!

ok. I'm looking forward to it


Add "license" arg to setup() call

Problem
Services such as https://pyup.io grab license info from package metadata to display alongside each requirement. django-model-utils isn't providing that license info in it's metadata.
Solution
Add a license argument to the setup() call in setup.py
Commandments

[x] Write PEP8 compliant code.
[x] Cover it with tests.
[ ] Update CHANGES.rst file to describe the changes, and quote according issue with GH-<issue_number>.
[x] Pay attention to backward compatibility, or if it breaks it, explain why.
[x] Update documentation (if relevant).

This change doesn't add, alter, or remove functionality, so I figured a changelog entry and an issue isn't warranted.

Arguably such services ought to parse the Trove classifiers for license information, too, because that's already in there, and according to the docs on additional metadata in an ideal world the license kwarg is for indicating the license covering the package where the license is not a selection from the “License” Trove classifiers.
In the real world, I don't see why this would be a problem to include.

fyi @jayfk


Add nvim-window-picker for neo-tree plugin

neo-tree need  s1n7ax/nvim-window-picker plugin to open file in a picked window

Thank you for your contribution but I think people can customize neotree on their own.


Add a wrapper around Entity for RemovedComponents

Objective

Make the internals of RemovedComponents clearer

Solution

Add a wrapper around Entity, used in  RemovedComponents as Events<RemovedComponentsEntity>

Changelog

Iterating through RemovedComponents now returns RemovedComponentsEntity instead of Entity

Migration Guide

When iterating through RemovedComponents, the inner entity must be obtained by accessing the 0 field of RemovedComponentsEntity.

Ping @Aceeri for review, as this is modifying the code added by your PR :)

bors r+

bors retry


Can I combine PublishSubject and Observable inside the combineLatest method?

Hi, I am not sure if I am doing something wrong or it's a bug. I have the following code:
        let string = Observable("test")
        let subject = SafePublishSubject<Void>()

        combineLatest(string, subject)
            .observeNext(with: { _ in
                print("changed")
            })

        string.value = "test2"
        // Nothing happens after changing the string

        subject.next()
        // prints "changed"

Can someone help me to understand why there is no signal when I change the string value? Can I use SafePublishSubject together with Observable in the combineLatest method?

combineLatest needs both signals to emit at least one event, otherwise there is nothing to combine. Because Subject does not have a concept of current value, there is nothing to emit until you explicitly send something with next method. This differs from Property/Observable which emits its current value when you start observing it.
Your code is fine and the behavior is correct, but I guess you were expecting something else? What’s the problem you are solving?

I wanted to execute the same chunk of code whenever my Observable emits a next event or when there is an event from the Subject. I didn't want to wrap the code into a function and I was looking for a way to combine both so I could put my code into one observeNext block. I've changed the PublishSubject to Observable and I made it work:
        let string = Observable("test")
        let subject = Observable<Void>(())

        combineLatest(string, subject)
            .observeNext(with: { _ in
                print("changed")
                ...
                // Here I have a large chunk of code that needs to be executed
                // either on string or subject next event.
            })

        string.value = "test2"
        // prints "changed"

        subject.next()
        // prints "changed"

Still unsure though if this is a proper way of handling my case.

There is a couple of other ways, depending on what you need.
You could have subject start with a given element. Since you are working with Void type, you can just start the signal with ():
let string = Observable("test")
let subject = SafePublishSubject<Void>()

combineLatest(string, subject.start(with: ()))
    .observeNext  { string, _ in
        print(string)
    }

You could achieve the same with replayLatest operator. It will re-emit the latest string event when the subject emits an event. It's a bit more descriptive that above:
let string = Observable("test")
let subject = SafePublishSubject<Void>()

string.replayLatest(when: subject)
    .observeNext  { string in
        print(string)
    }

If the code within observeNext does not work/depend on the string value, you could use merge operator. Merge operator works on the signals with same type of elements, so you either need to convert String observable into Void or Void subject into String. You can use map for that:
let string = Observable("test")
let subject = SafePublishSubject<Void>()

merge(string.map { _ in }, subject)
    .observeNext {
        // note no event element (string) in this case
    }

Thanks for the very detailed answer. I end up using the start(with:) method.


React Support for XBlock frontends

Goal
Full completion would mean:

Give XBlock developers access to the same modern frontend framework (React) and accessible component library (Paragon) that micro-frontend developers use.
Support all views: student, public, author, and studio.
Equally support all blocks, including the ones in edx-platform (eg, problem) and the ones in other repositories (eg, lti_consumer). This means that the new React views cannot be baked into core repositories.
Retain parallel support for existing edx-platform-rendered XBlock frontends.
Avoid regressions in performance, accessibility, i18n, or security.

Non-goals:

A new JS-based courseware plugin system separate from XBlock. This is an interesting idea, and has explored in the "NeXBlock" writeup. For this epic, though, we're interested in evolving the existing XBlock ecosystem.
Supporting blocks above the unit level, eg sequence. The established direction of edx-platform is that XBlocks should be used to customize courseware within the unit, but customizations to course structure should be left to separate, declarative systems.

Prior Work
Enhanced editors for Text, Video, and Problem
@connorhaugh ?
Hackathon: React HTML block student view
@nsprenkle ?
Considerations & Open Questions

Where do the React frontends live?

As an NPM package in the same repository as the XBlock backend?

How would the MFEs (learning, course-authoring, library-authoring)...

discover & install the correct NPM packages for all installed XBlocks types?
discover & load the correct JS modules with the frontend React components?

How do we handle units with a mix of legacy and React-enabled blocks?

Fall back to legacy views?
Group legacy blocks into views, something like this?

<Unit>
  <iframe>
    <legacy-block ... />
    <legacy-block ... />
  </iframe>
  <ReactEnabledBlock/>
  <iframe>
    <legacy-block ... />
    <legacy-block ... />
  </iframe>
  <ReactEnabledBlock/>
</Unit>

Currently, XBlocks in the same unit can "talk" to one another with JS. Would React-enabled blocks support that? If not, is it OK to break that?
Security: Currently, the unit iframe sandboxes instructor-authored XBlock content to a certain extent, protecting site from courseware script injection. How do we retain that security when rendering React-enabled blocks directly into the Learning MFE?
Should we worry about drift between legacy frontends and React frontends?
Would we ever deprecate legacy block frontends?
This whole proposal assumes React as a framework. Should we avoid that assumption?

Tasks
### Tasks
- [ ] https://github.com/openedx/XBlock/issues/634

Here's a good summary of V2 editors atm: https://github.com/openedx/frontend-lib-content-components/blob/main/docs/decisions/0003-V2-Content-Editors.rst

@muselesscreator, in view of our recent discussions around how to get React into XBlocks, I feel it's time to get back into this particular conversation.  Since you're the current "man on the ground" trying to find a way to do it, I'd love your take on possible ways to make it happen without compromising architecture or UX.


Update dependencies.

This update required changing a few templates due to an update
in ActionView that started raising an error:
     ActionView::Template::Error:
       Please use symbols for polymorphic route arguments.

Resolves CVE-2021-22903

Coverage remained the same at 84.381% when pulling 8d7d3dde5c4f4a78d497e19e30aba9dc2f0084c7 on CVE-2021-22903 into 1cb6b022e66fa2f90623f7f6f5e4c44e30ea3f4d on master.


Discord Mockup needs placeholders in place of empty users

Add HardCoded Values in place of Empty users, i.e. below PingIt Message box

Hey i would like to work on this

Hi there!
You can work on the frontend related issues. I know I haven’t explained them clearly, but I’m sure you’ll get the idea. Let me know if you have any questions or need help!


Automator: update<EMAIL_ADDRESS>in<EMAIL_ADDRESS>

Generated by Automator - 2023-07-13T15:27:12+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio_release-1.16
6f7da361740d3d010e154d5655c6bd8d001967d9
link
true
/test integ-security-multicluster

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.

/test integ-security-multicluster


Move default_schema handling into table loading

The concept of default_schema is only a thing for information_schema
implementors, so we should handle it there.

Not sure why but this breaks some print_schema tests

It's due to how we're doing whitelisting. I'm going to roll this into another PR which rewrites print-schema


Completion of error handling

Would you like to add more error handling for return values from functions like the following?

lseek ⇒ detect_file_type
pthread_create ⇒ process_terminal

There are some update candidates left over. I suggest to avoid ignorance of return values a bit more.
Are you interested to apply aspect-oriented software development?
How do you think about to encapsulate error detection and corresponding exception handling as a reusable aspect in your software?

How do you think about to improve static source code analysis also for your software?
Do you find information sources like the following useful?

Article "A Reusable Aspect for Memory Allocation Checking"
Document "Aspect-Oriented Software Development - An Introduction" by Johan Brichau and Theo D'Hondt
Paper "On Typesafe Aspect Implementations in C++" by Daniel Lohmann and Olaf Spinczyk

Should this issue be kept open until all affected implementation details will be fixed?

I'm sorry. I had forgotten this issue.


Chinese translation of JSON APIs and Ajax

[ ] Trigger Click Events with jQuery
[ ] Change Text with Click Events
[ ] Get JSON with the jQuery getJSON Method
[ ] Convert JSON Data to HTML
[ ] Render Images from Data Sources
[ ] Prefilter JSON
[ ] Get Geo-location Data

Closing in favor of https://github.com/FreeCodeCamp/TranslationExpansion/issues/11


I can't change a component's property values in react-native IOS

Description
I can't change a component's property values in react-native IOS, android I managed to change a value or overwrite it, in IOS I can't.
 React.Children.forEach(children, (child: any) => {     if (child.props) {       Object.entries(child.props).map(([key, value]) => {         if (value === 'sd:context:action') {           child.props[key] = context.setShow;         }       });     }   });
React Native Version
0.64.4
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 13.4.1
CPU: (10) arm64 Apple M1 Pro
Memory: 438.20 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.0.0 - /opt/homebrew/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 9.6.4 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.0 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8139111
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: 11.0.14 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.4 => 0.64.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
npm notice
npm notice New minor version of npm available! 9.6.4 -> 9.8.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.8.0
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
Steps to reproduce
const ContextShare: React.FC = ({children}): JSX.Element => {
const context = React.useContext(ContextAPI);
React.Children.forEach(children, (child: any) => {
if (child.props) {
Object.entries(child.props).map(([key, value]) => {
if (value === 'sd:context:action') {
child.props[key] = context.setShow;
}
});
}
});
return <>{children}</>;
};
Snack, code example, screenshot, or link to a repository
ERROR  [TypeError: onPress is not a function. (In 'onPress(event)', 'onPress' is "sd:context:action")]

0.64.4

Sadly this version of React Native is unsupported. We'll have to close this issue as we can't really actionate anything here.


Support rustfmt_skip on statements

Closes #1810.

Thank you!
If we are not skipping, do we preserve and format attributes on statements?

If we are not skipping, do we preserve and format attributes on statements?

I just tested and we do in some cases and do not in others (macro and let).


Be able to override FirestoreClient::DEFAULT_DATABASE

Describe the feature you would like to see
As described in https://cloud.google.com/firestore/docs/manage-databases?hl=fr#create_a_database, I would like to be able to override the constant defined in FirestoreClient named DEFAULT_DATABASE.
The goal will be to allow defining it via the configuration file.
My application uses multi-tenancy, and I want to switch the configuration while bootstrapping or reverting the tenancy.
I thought I just had to extend the Factory class (impossible because it's final), or whatever, but I couldn't accomplish this.
Maybe is it another way to do this?
Thank you for your awesome work in this package.
Used versions:

laravel/framework : v10.28.0
kreait/laravel-firebase : v5.4.0
google/cloud-firestore : v1.37.3

At the moment, the Firestore (and Cloud Storage) component are just super simple bridges, allowing them to be configured with options, as setting the default database) would be a good addition, thank you for bringing it up!
Todo list for myself:

Enable the factory to accept Firestore client options
Merge them with the default client options (they define the authentication config)
Make the options configurable here in the package and pass them to the factory

I only have limited time available, so I can't give you an ETA, but it's on my radar.

Oh thank you very much @jeromegamez! Awesome!

I didn't do it in the Laravel package yet 😅🙈

I didn't do it in the Laravel package yet 😅🙈

I just realized it 😫

Happy New Year @jeromegamez!
I would like to know if any update will be done about this issue in the current month?
If not, I probably will fork the project for my personal use with database override, as it's required for my business.
Thank you very much!

Since my work on my Firebase projects isn't funded (you've probably seen it in the readme of the SDK repo), I'm not motivated to do more than keeping everything stable and working at the moment, so I can't give you an ETA.
I understand you need it for your business and to make money, so for the moment I'd recommend forking the package and changing what you need - perhaps you'll do it in a way that can be merged back into here.

Since my work on my Firebase projects isn't funded (you've probably seen it in the readme of the SDK repo), I'm not motivated to do more than keeping everything stable and working at the moment, so I can't give you an ETA.
I understand you need it for your business and to make money, so for the moment I'd recommend forking the package and changing what you need - perhaps you'll do it in a way that can be merged back into here.

I understand. I will fork it so.


Contributing cosmopy

Hello,
I would like to contribute to the project by any means (contributing to the README, code, etc.).
Is the project still in development and is there will be a chance that my work/pull requests will be merged after review ?
Thanks

Hi Arman, the project is still active - in a fairly stable state.  Are there particular features you think should be added or improved?

Thanks for the fast reply.

Hi Arman, the project is still active - in a fairly stable state.

That is great to hear.

Are there particular features you think should be added or improved?

I have not had a chance to look the code in detail...so I don't have any good ideas at the moment. But I'll look at it and get back to you, if it's okay.

Hello again,
I have looked at the code. It seems that only H0, Omega_b and Omega_m are defined for spatially flat LCDM model.
If that is the case, I can try to add radiation contribution or try to implement more general cosmological models, which are defined in the astropy. Maybe we can add the Planck18 data-set as the default (or optional) values for the cosmological parameters.
I can also try to create an online documentation. My English is not so perfect but I can try my best to help.

All of those ideas are great, thank you.  Regarding the different cosmologies: adding radiation is a great place to start.  It would also be good to generalize the code such that it could easily apply to any of the pre-build astropy cosmology classes.  This might be doable with a "class factory" type approach, instead of manually implementing them.  Let me know if you have any questions or issues with the code.  Thank you for offering to help!

adding radiation is a great place to start

I tried to add it...Let me know if anything is wrong and I'll try to fix it.

It would also be good to generalize the code such that it could easily apply to any of the pre-build astropy cosmology classes. This might be doable with a "class factory" type approach, instead of manually implementing them.

Hmm. I don't know how to do class factory approach...but if you could show me a reference I might learn and try to implement it myself.

Let me know if you have any questions or issues with the code.

Thanks a lot. My python level is not so great. I am kind of a self-learner and some of the stuff in the repository is above my knowledge, but I can understand the module itself and make some changes to it.

Thank you for offering to help!

 I hope I can help :)


KAFKA-12778: Fix QuorumController request timeouts and electLeaders

Not all RPC requests to the quorum controller include a timeout, but we
should honor the timeouts that do exist.
For electLeaders, attempt to trigger a leader election for all
partitions when the request specifies null for the topics argument.

Generally, I don't like that we need to explicitly extract the timeout from the request and pass it into the controller call. It would nice if this could be generalized or automated somehow. However, something like this is not needed for this minor fix.

If we were starting all over again, we could give all RPC requests a timeout, located in the request header itself.  But that isn't really the case today -- some requests don't have timeouts, some do, and we have to extract it from the specific request schema.


What's an integration readmap?

What's an integration readmap?
Context
A brand new verifiable credential Issuer wants to support LCWallet.
Questions

What are the integration prerequisites?
Are there development mobile applications builds to use during the integration development?
Issuers Registry extension?
How is the issuerAuthRegistry maintained?

Couldn't find any related info for those. Please, point if any.
Thanks.

@wowkalucky thanks for the heads up! We'll get back to you with the answers shortly.

@wowkalucky Apologies for the delay. I know your team has finished integration -- is there anything else we can answer?

Hey @wowkalucky - we're going to close this issue for now but feel free to re-open and reach out if we can be of assistance.

Thanks @dmitrizagidulin @kayaelle . We have  settled everything.


examples: add serde_json integration example

I hope that this implementation makes sense. This is what I just added in fnm

this is great! thank you so much :)
I think this is a super common thing to do, tbh.


RSS feed for this?

Please make it possible to subscribe to a RSS feed for this page.
https://docs.microsoft.com/en-us/windows/release-information/windows-message-center

Given that this is content-related, and is not directly related to functionality on docs.microsoft.com, I will close this item. We are constantly working to make sure that you can better keep track of content and its updates (see: bookmarks). We will continue evolving that functionality in the future, so keep the feedback coming!


Fix Java 9 Jigsaw incompatibility in native-platform

In order for the daemon to work, we need to address adammurdoch/native-platform#16.

It seems like there is nothing left to be done here on the Gradle side at the moment.


Many-to-Many Relationships Null

HI 3lvis, I believe that is a bug in Many-to-Many relationships.

First sync: I get all speakers in session 1 and 2

But when the tableview reloaded (second sync), all speakers are gone. I expected that just only speakers in session 1 should be deleted. Speakers in session 2 should not be deleted.
When I restarted the app, I still could not get any speakers. I received this error message:
"CoreData: warning: An NSManagedObjectContext delegate overrode fault handling behavior to silently delete the object with ID '0xd000000000140004 x-coredata://2D824DB1-6AFD-427B-90D3-EC789EDFEC86/Speaker/p5' and substitute nil/0 for all property values instead of throwing."
Thank you.

Hi @norikachi  I am experiencing the same issue...
I managed to solve it by removing all empty arrays in the dictionary before passing it to the sync function...
for element in originalData {
  data.append(element.emptyRemoved)
}
Sync.changes(data, inEntityNamed: myEntity, dataStack:myDataStack)

where  emptyRemoved is placed within an extension for Dictionary as suggested here http://stackoverflow.com/a/35787010
        let tup = filter {
            //if let detailsDict = details as? NSDictionary
            if let element = $0.1 as? Array<Any> {
                return !element.isEmpty
            }
            return !($0.1 is NSNull)
        }
        return tup.reduce([Key: Value]()) { $0.0.updatedValue($0.1.value, forKey: $0.1.key) }
    }

Did you find a better solution for this?
@3lvis i believe this should be the default behaviour for this case but maybe this can also be a param

A proposed fix was submitted here, please give it a try and let me know if there are any issues: https://github.com/3lvis/Sync/pull/418
Thanks for you patience <3


fix: set more modern node versions in CI

most libraries dropped node12 support, node18 is next lts and around the corner. also npm caching should be nice.

Ok, so there are things incompatible with node 18, but I don't get the issue with node 16.

node 16 fails b/c it runs the UI tests, which fail for reasons unbeknownst to me

managed to do this in https://github.com/quirrel-dev/quirrel/pull/1057! :)


Update information about BRYTER

added information that we are fully remote with (co-working) office spaces
added office space in London

Thank you 👍