Add Seeker interface to file

This PR implements the optional seeker interface for file

Before I start reviewing, my first question is - why? What's the use case?
Each Seek call essentially makes another call to s3 which costs you money. There are a lot of functions that can take advantage of seeker behind the scenes, potentially making your aws bill higher.
It also introduces some issues, such as you not closing the body while calling seek (if it's opened) thus leaking go routines.

Currently I am streaming 10GB files from s3 into an application. The file has a streamable format, so it can be read from most positions. It would therefore speed up my processing time, if I could seek in the file.
In addition I want to add a wrapper around a fs which allows to stream data using multipart download. For that I need the fs to support the seek operation (every part needs to seek to its starting position and read from there). This would speed up the streaming from around 30MB/s to somewhere around 200MB/s
Leaking go routines is a good point. I'll check again with that in mind

LGTM thanks!


XML files only related to the 80 'things' classes

Running:
python anno_coco2voc.py --anno_file instances_train2014.json --type instance --output_dir ./anno_trainXML
I obtain only 80 folders containing the 80 'things' classes of COCO 2014.
In reality that dataset contain also other 91 'stuff' classes (in total coco2014 contain 172 classes).
So how can I see the other classes ?

@algila I think you need to download COCO 2017 Stuff Train/Val annotations [401MB](here). I just refer to the overview document in this download website and don't dig into structure of the annotation file. So I am not sure if my script could parse it correctly for it's designed for COCO2014.


How the refinement and de-duplication is performed?

I noticed that the paper mentions an iterative training by feeding the previously predicted bbox and feature. Could you help identify which part of the code corresponds to this. And may I ask how deduplication is achieved in this process, since the paper claims to be free of NMS?

The iterative process is at: https://github.com/PeizeSun/SparseR-CNN/blob/main/projects/SparseR-CNN/sparsercnn/head.py#L103 L103-109
The deduplication is from optimal bipartite matching in training(https://github.com/PeizeSun/SparseR-CNN/blob/main/projects/SparseR-CNN/sparsercnn/loss.py#L273) and self-attention module(https://github.com/PeizeSun/SparseR-CNN/blob/main/projects/SparseR-CNN/sparsercnn/head.py#L188).

Thanks for a quick response.
Some additional tiny questions about de-duplication. I noticed the bipartite matching. I just wonder should the number of proposed bbox remain fixed after the 1st round of matching (because you have selected the best matched bboxes)?

This is a very interesting question~
In my opinion, the number of proposed boxes could be different in different rounds, for example, gradually decreasing from 1st round to final round. We haven't tried it. If you're interested, you could try it and share the result with us.

Thank you again for your response


MRG, FIX: Fix for complex

Fixes a problem found by @drammock working with complex Evoked data where the variance explained computation / message would give a warning, which made it clear it was doing something wrong.

thx @larsoner


Fix unsuccessful build issue

build.sh file doesn't work because duplicate os_name variable
change end-line formatting

@alijomeiy
CI is red, please make it green


Consider using Prettier npm package for automated code formatting

As proposed by @emmenko
https://github.com/commercetools/commercetools-adyen-integration/pull/17#discussion_r262951038
https://www.npmjs.com/package/prettier

Consider --> Use 😉


Demo Error

Hi,
So I am trying to run the test dataset. I downloaded the original citeseer data, and I am still getting the same error below when running the command: python train.py --dataset citeseer
Traceback (most recent call last):
File "train.py", line 59, in
model = model_func(placeholders, input_dim=features[2][1], logging=True)
File "build/bdist.linux-x86_64/egg/gcn/models.py", line 144, in init
self.build()
File "build/bdist.linux-x86_64/egg/gcn/models.py", line 41, in build
self._build()
File "build/bdist.linux-x86_64/egg/gcn/models.py", line 167, in _build
logging=self.logging))
File "build/bdist.linux-x86_64/egg/gcn/layers.py", line 161, in init
self._log_vars()
File "build/bdist.linux-x86_64/egg/gcn/layers.py", line 82, in _log_vars
tf.summary.histogram(self.name + '/vars/' + var, self.vars[var])
AttributeError: 'module' object has no attribute 'summary'
Thanks!

Thanks for reporting your issue. This problem is related to an old version of TensorFlow. Can you upgrade to version 0.12 or 1.0 and try again?

Alright so I upgraded from 0.9 to 1.0, errors surrounding labels.
usr/local/lib/python2.7/dist-packages/gcn-1.0-py2.7.egg/gcn/utils.py:97: RuntimeWarning: divide by zero encountered in power
Traceback (most recent call last):
File "train.py", line 59, in
model = model_func(placeholders, input_dim=features[2][1], logging=True)
File "build/bdist.linux-x86_64/egg/gcn/models.py", line 144, in init
self.build()
File "build/bdist.linux-x86_64/egg/gcn/models.py", line 55, in build
self._loss()
File "build/bdist.linux-x86_64/egg/gcn/models.py", line 153, in _loss
self.placeholders['labels_mask'])
File "build/bdist.linux-x86_64/egg/gcn/metrics.py", line 6, in masked_softmax_cross_entropy
loss = tf.nn.softmax_cross_entropy_with_logits(preds, labels)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/nn_ops.py", line 1578, in softmax_cross_entropy_with_logits
labels, logits)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/nn_ops.py", line 1533, in _ensure_xent_args
"named arguments (labels=..., logits=..., ...)" % name)
ValueError: Only call softmax_cross_entropy_with_logits with named arguments (labels=..., logits=..., ...)

Ok, looks like there are still compatibility issues with TensorFlow 1.0. I'll look into it. In the meantime you can use TensorFlow v0.12. Thanks for reporting!

I checked again and this issue was fixed in https://github.com/tkipf/gcn/commit/193c0992007610b8ff65f3d3f5d6c418b13a343b . Please pull and re-run python setup.py install.

Ok great thank you so much!
Karleigh Mezeivtch
Lieber Institute for Brain Development
Johns Hopkins Medical Campus
855 North Wolfe Street, Suite 300
Baltimore, MD 21205
<EMAIL_ADDRESS>
From: Thomas Kipf<EMAIL_ADDRESS>Sent: Wednesday, February 22, 2017 3:24 AM
To: tkipf/gcn
Cc: Karleigh Mezeivtch; Author
Subject: Re: [tkipf/gcn] Demo Error (#8)
Closed #8https://github.com/tkipf/gcn/issues/8.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/tkipf/gcn/issues/8#event-972122451, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANaIfdmu_VC67u5w__3LYfnAxUepPlggks5re_CngaJpZM4MH0Pv.


Responsive design without directional buttons only shows a subset of numbers

Angular 2 version: 2.0.0-beta.15
ng2-pagination version: 0.0.1
Description of issue: Responsive design without directional buttons only shows a subset of buttons in PaginationControlsCmp.
Steps to reproduce:
Set directionLinks to false:
<pagination-controls (pageChange)="p = $event" #api [directionLinks]="false"></pagination-controls>

and look at the page in a small screen
Expected result: All the numbers in PaginationControlsCmp  should be shown.
Actual result: Only a subset of buttons are shown:

Demo: (if possible, edit this Plunker demo and paste the link to your fork)
Demo

Thanks for the report (and the others). I'll have time to look at and hopefully resolve all of these later this week.

Excellent. Thank you!


Windows CI: Unit Tests stop running failing archive test

This unit test is failing in WindowsTP4 CI for unknown reasons (it runs fine locally). Skipping it on Windows.

Signed-off-by: Darren Stahl<EMAIL_ADDRESS>

:scream_cat: :heart_eyes_cat:  LGTM

LGTM 🐏


Support Laravel 9

When it gonna be added?

Maybe @spekulatius can bump requirements versions in https://github.com/rialto-php/rialto and here?
Or give me rights for merge :)

Hey @xtrime-ru, I don't have the permissions either. I can't help out, sorry.

Hey @xtrime-ru, I don't have the permissions either. I can't help out, sorry.

Thanks for reply!
The only way i can see right now - fork both libs and maintain them... Maybe we can start new organisation and invite there all current contributors?

For those who need this coming from a Laravel project, https://github.com/spatie/browsershot is a great alternative. :)


Locale with "nl" value loads error : "Value not in range: 3"

Hi,
First of all, thank you for this package ! It's very useful for me ! 👍
I get the following error when trying to use the "nl" locale :
════════ Exception caught by widgets library ═══════════════════════════════════════════════════════
The following RangeError was thrown building:
Value not in range: 3
When the exception was thrown, this was the stack:
#0      _StringBase.substring (dart:core-patch/string_patch.dart:388:7)
#1      _CalendarTimelineState._buildDayList. (package:calendar_timeline/calendar_timeline.dart:134:22)
#2      _PositionedListState._buildItem (package:scrollable_positioned_list/src/positioned_list.dart:247:54)
#3      _PositionedListState.build. (package:scrollable_positioned_list/src/positioned_list.dart:183:27)
#4      SliverChildBuilderDelegate.build (package:flutter/src/widgets/sliver.dart:446:22)
...
════════════════════════════════════════════════════════════════════════════════════════════════════
The error is inside (package:calendar_timeline/calendar_timeline.dart) at line 134 :
DateFormat.E(_locale).format(currentDay).substring(0, 3).capitalize()
Could you please check this out ?
Than you very much ! 👍 👍

Thanks for the report @legrandced. Fixed in version 0.6.3


Bad package.json configuration for typings

Describe the bug
The configuration for where we can find the typing of the package is wrong.
To Reproduce
Just install the package in any repo, and Typescript will throw this error:
Could not find a declaration file for module '@rnwonder/solid-date-picker'. '/home/carere/Projects/Ashiso/my-sst-app/node_modules/.pnpm/@rnwonder+solid-date-picker@0.7.7_solid-js<EMAIL_ADDRESS>implicitly has an 'any' type.
  There are types at<EMAIL_ADDRESS>but this result could not be resolved when respecting package.json "exports". The '@rnwonder/solid-date-picker' library may need to update its package.json or typings.

Expected behavior
Instead of this:
  "exports": {
    ".": {
      "types": "./dist/index.d.ts",
      "default": "./dist/index.es.js"
    }
  },

We should have this:
  "exports": {
    ".": {
      "types": "./types/index.d.ts",
      "default": "./dist/index.es.js"
    }
  },

can you raise a pr to fix this

@carere upgrade to the new version made a fix


When navigating a large codebase, rust-analyzer takes a while to load.

I have a suggestion, because it takes a while for rust-analyzer to load a file on a large codebase, maybe analyze the file that is currently open first, and all modules being used in that file first before anything else. I've been waiting about 5 minutes for rust-analyzer on vscode to give me intellisense.

That's practically what we do, but we need to run cargo metadata (which can take a while to update the cargo registry) and cargo check (for proc macros and build scripts, which can be disabled).

Ah thanks. Sorry for making this issue.

No worries. If you have a project where slowness isn't explained by an initial cargo check, you should file an issue, since it might be something fixable.


Manual rotation via CLI doesn't work if two endpoints have the same name

If a Lemur instance has two endpoints with the same name, say alb-foo-shard0 for example, it is not possible to use the CLI to perform a manual certificate rotation. Under these conditions, the CLI will fail silently like so:
$ /opt/venv/bin/lemur certificate rotate -c -o "<old cert>" -n "<new cert>" -e "alb-foo-shard0"
[!] Running in COMMIT mode.
[+] Starting endpoint rotation.

Because these types of collisions are to be expected especially when using multiple AWS accounts, I'm not sure we can impose a uniqueness constraint on the name field for an Endpoint to work around this problem. However, we may be able to slightly improve the CLI here by (1) adding support for a --endpoint-dns-name option which allows an endpoint to be selected uniquely and (2) catching the case where two or more endpoints with the same name are detected and log a warning for the user to use --endpoint-dns-name instead.

Closed via #3963


Make shadow behind the hearts.

In some backgrounds the heart is not visible. To add it a shadow of a light color.

Fixed using the Decorated Icon package.


Custom favicon

Favicon should be zazzy and invoke feelings of delight.

I have this updated locally, but need to get the self-signed cert and the new local env working so I can test it.

@sbddesign
run “npm install”, then you’ll be able to develop on using “npm run dev” and https://localhost:3000/.
If you’re using brave, you’ll need to change this setting to allow self-signed certs on localhost:
brave://flags/#allow-insecure-localhost


Pass PostURL when zipping forms and use for submission

SD Card and WiFi Direct transfer will pass the original user's PostURL along with the form so that the submitting phone can use the "correct" URL
See http://manage.dimagi.com/default.asp?217957
@ctsims open to feedback on this approach
cc @czue

:+1:
@ctsims has more context, so he should do a pass too before merge


fix issue when loading module before context is available

FYI @anarchicknight

Thanks for the PR. I have checked it out and all OK - merged :)

Thanks!


Notification controller does not start on clusters with active PSPs (runAsNonRoot)

There isn't much more to add.
Error: container has runAsNonRoot and image has non-numeric user (controller), cannot verify user is non-root

Create a PSP that allows the flux controller to run or patch them and hardcode some user id.

@stefanprodan why you closed the ticket?
Isn't the right thing to do to add a security context here:
https://github.com/fluxcd/notification-controller/blob/main/config/manager/deployment.yaml#L22-L65
Something like:
	securityContext:
      runAsUser: 1001

Please see: https://github.com/fluxcd/flux2/issues/829

FYI https://github.com/kubernetes/enhancements/pull/2582


Playground updates

Added "show me the code" option which fires a modal dialog where the users can grab the code to generate the exact same lock in their site.
Added "output" section, where users can find the output of using the lock (auth_token + id_token)

Will send PR again after some UX updates

Awesome


Address Issue #122

This is a new, better version of the PR #200. It shouldn't create merge conflicts.

LGTM


How to get presence and visibility parameters ?

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
No
OS Platform and Distribution
Android 10
MediaPipe Tasks SDK version
No response
Task name (e.g. Image classification, Gesture recognition etc.)
Pose Landmark
Programming Language and version (e.g. C++, Python, Java)
Android
Describe the actual behavior
In this documentation https://developers.google.com/mediapipe/solutions/vision/pose_landmarker/android ,
It is given that the result will be this:
PoseLandmarkerResult:
Landmarks:
Landmark #0:
x : 0.638852
y : 0.671197
z : 0.129959
visibility : 0.9999997615814209
presence : 0.9999984502792358

Describe the expected behaviour
But in the implementation, I am only getting x, y and z values but not visibility and presence.

Standalone code/steps you may have used to try to get what you need
I have used the exact same code as provided in this sample:
https://github.com/googlesamples/mediapipe/tree/main/examples/pose_landmarker/android

Other info / Complete Logs
No response

@bhaskar2728,
Sorry for the delayed response,
Could you please confirm that Are you still looking for the resolution or the issue has been resolved from your end?
Thank you!1

The issue has been resolved in the googlesamples/mediapipe github discussion . This is the link: https://github.com/googlesamples/mediapipe/issues/158


use ivar instead of getter of viewController

public extension LayoutLoading where Self: UIViewController {
    /// Default layoutNode implementation for view controllers
    var layoutNode: LayoutNode? {
        get {
            return objc_getAssociatedObject(self, &layoutNodeKey) as? LayoutNode
        }
        set {
            layoutNode?.unmount()
            objc_setAssociatedObject(self, &layoutNodeKey, newValue, .OBJC_ASSOCIATION_RETAIN_NONATOMIC)
            layoutNode?.unmount()
            if let layoutNode = layoutNode {
                do {
                    try layoutNode.mount(in: self)
                    layoutDidLoad(layoutNode)
                } catch {
                    layoutError(LayoutError(error, for: layoutNode))
                }
            }
        }
    }
}

second unmount() calls viewControllers
    public func unmount() {
        guard parent == nil else {
            // If not a root node, treat the same as `removeFromParent()`
            // TODO: should this be an error instead?
            removeFromParent()
            return
        }
        unbind()
        for controller in viewControllers {
            controller.removeFromParent()
        }
        _view?.removeFromSuperview()
    }

    public var viewControllers: [UIViewController] {
        guard let viewController = viewController else {
            return children.flatMap { $0.viewControllers }
        }
        return [viewController]
    }

which calls setUpExpressions() even before mount(in:) calls.
    public var viewController: UIViewController? {
        if _class is UIViewController.Type {
            attempt(setUpExpressions)
        }
        return _viewController
    }

Coverage increased (+1.1%) to 59.105% when pulling b0a4ee5cd95cb5feed8d37e23044acb38083ea86 on flexih:master into 2c6d11a01ebc8e48953b6a838773656314b63ae0 on schibsted:master.

@flexih thanks for catching this. I think I want to retain the behavior that calling viewControllers initializes the view though.
The solution is probably to extract the logic for the viewControllers getter into a private method that doesn't do that, but I'll think on it some more.

@flexih I’ve pushed an alternative fix to the develop branch - does that work for you?

Yes, it works. Thanks.


Do not break on -Wunused-packages

If you start a ghci session is started with "unused-packages" warning enabled you can get output like this:
<no location info>: warning: [-Wunused-packages]
    The following packages were specified via -package or -package-id flags,
    but were not needed for compilation:
      - foo-<IP_ADDRESS>
      - bar-<IP_ADDRESS>

~at the end of loading iirc~ before it start compiling the first module. This seems to break ghcid, which, on first load, reports errors as expected, but then hangs on the first reload. Of course fixing the warning (removing foo/bar or disabling the warning if your setup just adds spurious -packages) is the obvious fix, but it might be worth making ghcid more robust, as just hanging without any error output is annoying to debug.
I guess this would need an addition to https://github.com/ndmitchell/ghcid/blob/master/src/Language/Haskell/Ghcid/Parser.hs#L60, right? Or would it be better (for now) to just force the warning off for the time being (by insert a :set into the ghci session)
Do you think it is worth fixing this? Suggestion on best approach?
This happens for us on a slightly larger project; I somewhat assume it is easy to reproduce, but if it is not I can of course come up with a sample project setup for reproduction.

I'm experiencing the same.
Actually the same warning is also printed with cabal repl.
So maybe this problem should be addressed there?
cabal build works as expected at least :)
This also falls into the same category as #358.

I think the right solution is to adjust the parser to take account of this warning. Unconditionally disabling warnings is a bit annoying because it varies between GHC version, they can be set later on in the process, and you also lose warnings that are presumably useful. PR welcome!


Can't disable Mongock in unit tests

In Spring Boot unit tests that partially initialise the application context (IE: @JsonTest), the Mongock builder tries to instantiate the driver anyway, and you get exceptions because of the missing MongoTemplate:
***************************
APPLICATION FAILED TO START
***************************

Description:

Parameter 0 of method mongockConnectionDriver in com.github.cloudyrock.spring.v5.MongockSpringDataV3CoreContext required a bean of type 'org.springframework.data.mongodb.core.MongoTemplate' that could not be found.

It would be nice to have a way to completely disable mongock beans instantiation during test execution.

That's a known bug . It will be fixed in the next minor release, which e this week.

I close this issue as this as this is already in place

Can we reopen this issue, as the original problem still exists? I'm using Mongock 5.1.0 and Spring Boot 2.6.8 . When I write a test with @JsonTest, Spring tries to auto-configure Mongock, but fails with No qualifying bean of type 'io.mongock.driver.api.driver.ConnectionDriver'.
As a workaround adding @TestPropertySource(properties = ["mongock.enabled=false"]) fixes the issue (which was the linked other issue), but @JsonTest (as well as other partial-context tests like @WebMvcTest, @DataJpaTest, etc) should not load the full context with database and other initializers. Developers should not disable directly anything in these tests.

Hello @sassrobi, I get your point. I can think of multiple ways of approaching this, but to be honest all of them are involves much more work than the benefit the developer gets. Specially having the long list of features we have in our backlog and having a workaround which doesn't feel that bad to me.
However, you are welcome to raise a PR for this. It would be a pleasure to assist you in this and review it 😃

Thank you for your reply. Sadly, i don't have enough experience for doing this, and I don't have time either  😔


Upgrade to Joken 2.0

Joken 2.0 supersedes Joken 1.0. It is required for joken_jwks dep.
Refactoring guide can be found here:
https://hexdocs.pm/joken/migration_from_1.html#content
Both apps/rig_auth/lib/rig_auth/jwt/utils.ex and apps/rig/lib/rig/jwt/claims.ex require code changes.

#225 is blocked by this issue


Technical documentation

Hello,
If they could create a technical documentation, for example what does each file and each function, where it is injected in the codes of the players, ect. it would be of great help to be able to contribute
I really want to help! Especially to implement it in new versions of Jwplayer
Regards

There is no perfect documentation currently.
But the best documentation for an open-source project is the source code.
You can check existing integration with players and hls.js engine Shaka Player

Contributions are welcome!

Hello,
If they could create a technical documentation, for example what does each file and each function, where it is injected in the codes of the players, ect. it would be of great help to be able to contribute
I really want to help! Especially to implement it in new versions of Jwplayer
Regards

may i help you, ping me


[Doc] Fix variable name and hydration logic typo

Q
A

Bug fix?
no

New feature?
no

Tickets

License
MIT

There seems to be a little mistake in the section explaining logic of LiveProp hydration.
Also a small typo in a form variable name used in code block related to render overriding.

Good catch, thanks @biostaz.


Possible to build a raspberry pi version?

Hi!
It would be great if there was an image for the Raspberry Pi architecture on docker hub too, is it possible to do that?
I'm not sure what would be involved in that, I think the openjdk base image is already available for ARM.
Thanks for your attention! :)

If you already a base image with java you can just copy your fat-jars into a new layer and it should run. I can confirm that without docker, just a RPi2 and RPi3 using the available jdk package I can run vert.x applications.

Hi!
The downside of a fatjar is that it's a lot more data to deploy each time on a resource contrained device :)
But I looked at your dockerfiles and can build my own locally now: https://github.com/cranphin/vertx3-alpine-docker (on the rpi), which is easy enough and solves my issue :)
Soon it should be 'easy' to build multipe arch images from any platform too: https://engineering.docker.com/2019/04/multi-arch-images/ but it's a very relative easy.. :)

Actually, since this is Java, a trick like this would also work: https://stackoverflow.com/questions/54051697/how-to-build-docker-container-image-for-arm32-architecture-from-windows-10-os :)


Ray parallel fix

Description of changes:
cap dask and distributed to fix parallel. re-enable parallel
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@yinweisu I don't see the re-enabling of parallel in the PR changes


Plan how to manage version changes on OSrPRE review/question form

Since we are going to move forward with updating the data accessibility question (#115), let's make sure we have a plan in place to track version changes of the form.

This is a repeat issue to #115.


store: Fix inconsistent cache backend types

Signed-off-by: Kemal Akkoyun<EMAIL_ADDRESS>
[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Change memcached BucketCacheProvider constant type to MEMCACHED to be consistent with index cache backend.

https://github.com/thanos-io/thanos/blob/8bdd15e032c24fb98ed9ec69fa42f16376a9101e/pkg/store/cache/factory.go#L18-L23

Make it case-insensitive to prevent future issues.

Verification

make test-local

cc @pstibrany

One more thing. If we merge here this will not be part of 0.13.0. I guess this is ok?

One more thing. If we merge here this will not be part of 0.13.0. I guess this is ok?

Given bucket caching is marked as experimental, I would say it's OK.


Updates to Azure Function for FHIR event handling in non-CDC subscription

Add additional updates to Azure Function app in non-CDC subscription.

[ ] add app setting for boolean "flatten" (true = flatten data on export, false = leave json structure intact)
[ ] add app setting configuration reader to function app
[ ] update code to only flatten data if app setting "flatten" = true

Note: this will likely be the last updates made to the Azure Function in the non-CDC subscription before moving to the CDC subscription resource group


Improve cloud type classification

Use an ML model to differentiate all 10 major cloud types.

https://ane4bf-datap1.s3-eu-west-1.amazonaws.com/wmocms/s3fs-public/ckeditor/files/WMD2017_poster_JN162028_EN.pdf?nYgh.wIczIOQE7LTllgPL2S0Zbwwn0A3


Is there a Langchain migration guide for going from Pinecone pod-based to serverless?

Checklist

[X] I added a very descriptive title to this issue.
[X] I included a link to the documentation page I am referring to (if applicable).

Issue with current documentation:
I'm unable to find the docs for embedding and querying from Pinecone serverless when generating AI responses. Currently, I'm using the below code for pod-based indexes, but it's not working for serverless indexes:
const pineconeClient = new Pinecone({
    apiKey: pineconeApiKey,
    environment: pineconeEnvironment,
});

const pineconeIndex = pineconeClient.Index(pineconeIndexName);

vectorStore = await PineconeStore.fromExistingIndex(
    new OpenAIEmbeddings({}),
    {
        pineconeIndex: pineconeIndex,
        textKey: 'text',
        namespace: namespace,
    },
);

This is the error I get:
Request failed to reach Pinecone while calling https://controller.eu-west-1.pinecone.io/actions/whoami. This can occur for reasons such as incorrect configuration (environment, project id, index name), network problems that prevent the request from being completed, or a Pinecone API outage. Check your client configuration, check your network connection, and visit https://status.pinecone.io/ to see whether any outages are ongoing.

What do I need to change in the code so it works with Pinecone serverless? I couldn't find any documentation for it.
Idea or request for content:
No response

I'm already using the same code and it isn't working with serverless.

Solved

Solved

Having the same issue. How did you solve it?

Got the same issue.


Fix explode to use internal methods.

Koalas doesn't guarantee the underlying Spark DataFrame has columns named name_like_string(column_label). We should always retrieve the Spark column, the column name, etc. using internal methods.
Also added a negative test.

Also cc @itholic

Codecov Report

Merging #1538 into master will decrease coverage by 2.15%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1538      +/-   ##
==========================================
- Coverage   94.15%   92.00%   -2.16%
==========================================
  Files          37       37
  Lines        8507     8507
==========================================
- Hits         8010     7827     -183
- Misses        497      680     +183

Impacted Files
Coverage Δ

databricks/koalas/frame.py
92.89% <100.00%> (-2.87%)
:arrow_down:

databricks/koalas/usage_logging/__init__.py
24.32% <0.00%> (-70.28%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50.00% <0.00%> (-50.00%)
:arrow_down:

databricks/koalas/__init__.py
72.54% <0.00%> (-19.61%)
:arrow_down:

databricks/conftest.py
88.67% <0.00%> (-7.55%)
:arrow_down:

databricks/koalas/utils.py
94.03% <0.00%> (-2.30%)
:arrow_down:

databricks/koalas/generic.py
94.92% <0.00%> (-1.82%)
:arrow_down:

databricks/koalas/namespace.py
84.49% <0.00%> (-1.61%)
:arrow_down:

databricks/koalas/plot.py
93.33% <0.00%> (-0.96%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 050a301...6e4bc2b. Read the comment docs.

Oh, I got it. Thanks!
>>> kser = ks.Series([1, 2, 3])
>>> kser.name = "Koalas"
>>> column_from_label = name_like_string(kser._internal.column_labels[0])
>>> kser._internal.spark_frame[column_from_label]
Traceback (most recent call last):
...
pyspark.sql.utils.AnalysisException: 'Cannot resolve column name "Koalas" among (__index_level_0__, 0, __natural_order__);'

Is this the proper example of the inconsistency you are concerned with? 🧐

LGTM

@itholic
>>> kdf
             A  B
             X  Y
0  [-1.0, nan]  1
1   [0.0, inf]  1
2  [1.0, -inf]  1
>>> kdfA = kdf.A
>>> kdfA
             X
0  [-1.0, nan]
1   [0.0, inf]
2  [1.0, -inf]
>>> kdfA._internal.spark_frame['X']
Traceback (most recent call last):
...
pyspark.sql.utils.AnalysisException: 'Cannot resolve column name "X" among (__index_level_0__, (A, X), __natural_order__);'

Thanks, I thought it's fine to use name_like_string too. I will avoid next time too.

Thanks, @ueshin !


The site is down

e.g., when I go to this page:
https://www.lesserwrong.com/posts/GHBLFPDhzeSQHx2eM/writing-that-provokes-comments
I get this error:
502 Bad Gateway: Registered endpoints failed to handle the request. If you're the owner of this app, see this article for more information: http://bit.ly/2w0yJ4P

It's back now but taking 27.78s to load the page.


Sign In Screen Button Has Odd Click Border

For some reason only the top margin for the sign in button /signin is clickable - the full button should be clickable.

@akarasev looks good


Parameter link_targets is not working for follow_link() in TraverseEngine

I couldn't find any unit test covering this use-case so it should be created.

Follow_link is not supposed to use this parameter. This bug is not valid.


Fix: Login - Inconsistent copy in error message on 2FA entry screen

Details
To make two-factor authentication error messages consistent with the backend message, updated the translations in the file.
Fixed Issues

$ https://github.com/Expensify/App/issues/21321
PROPOSAL: https://github.com/Expensify/App/issues/21321#issuecomment-1602900892
Tests

For not 2fa enabled account, login -> Settings -> Security -> Two-factor authentication
Complete step 1(Recovery codes) and reach to step 2(Verify)
Verify the 2fa input error message shows/contains two-factor authentication code for the below cases
-> Click Next without providing 2fa code
-> Click Next with partial filled 2fa code
For 2fa enabled account, In the login page provide your login id and complete magic code step
In the authenticator code page repeat step 3 to verify the error messages

[X] Verify that no errors appear in the JS console

Offline tests

N/A
QA Steps

For not 2fa enabled account, login -> Settings -> Security -> Two-factor authentication
Complete step 1(Recovery codes) and reach to step 2(Verify)
Verify the 2fa input error message shows/contains two-factor authentication code for the below cases
-> Click Next without providing 2fa code
-> Click Next with partial filled 2fa code
For 2fa enabled account, In the login page provide your login id and complete magic code step
-> In the authenticator code page repeat step 3 to verify the error messages

[X] Verify that no errors appear in the JS console

PR Author Checklist

[X] I linked the correct issue in the ### Fixed Issues section above
[X] I wrote clear testing steps that cover the changes made in this PR

[X] I added steps for local testing in the Tests section
[X] I added steps for the expected offline behavior in the Offline steps section
[X] I added steps for Staging and/or Production testing in the QA steps section
[X] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[X] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[X] I included screenshots or videos for tests on all platforms
[X] I ran the tests on all platforms & verified they passed on:

[X] Android / native
[X] Android / Chrome
[X] iOS / native
[X] iOS / Safari
[X] MacOS / Chrome / Safari
[X] MacOS / Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[X] I followed proper code patterns (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[X] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I followed the guidelines as stated in the Review Guidelines
[X] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] I verified that if a function's arguments changed that all usages have also been updated correctly
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@Pujan92 OfflineTest Does not make sense can you remove them please

Yes, updated.

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web & Deskop
https://github.com/Expensify/App/assets/85645967/b50a612d-d35d-4105-894c-91f057b93aa9

Mobile Web - Chrome & Mobile Web - Safari
https://github.com/Expensify/App/assets/85645967/7dc49956-1d94-4cdc-b657-d80deae09355

iOS & Android
https://github.com/Expensify/App/assets/85645967/a8ebef3d-91d4-477c-a827-58eb78476cca

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/amyevans in version: 1.3.40-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.40-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Add ATraversal and cloneTraversal

Based on code from #26, but doesn't use the Lens library for the
traversals. Follows Shop for overall organization.
Fixes #26.

Looks good to me at least!
@LiamGoodacre? (Or anyone else who considers themselves an expert)


Roadmap

Let's use this issue to brainstorm on the roadmap.  The goal is to figure out the big rocks that we have to tackle and not necessarily the exact timeline.
2.0

Open sourcing
Build system
Publishing package
Lots of fixes
Package re-organization
Code style fixes
Dependency upgrades

2.x / 3.0

Support newer versions of Exchange / Exchange Online
Support OAuth
Close the gap with EWS Managed API
More fixes

Maybe in addition to the things been said we should keep track on the following tickets:
2.0

deploy gpg-signed artifacts (#238)

2.x

add streaming for attachments (#36)
use generics instead of Object  (#272)
xml-validation (#233)

3.0

extract autodiscover package and provide it as an independent project for reusability

independent tasks

github landingpage (#191)
increase test-coverage (#205)


Update to 0.0.3

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] 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)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

  error in jraph setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers; Expected end or semicolon (after name and no valid version specifier)
      python_version>="3.6"
                    ^
  error: subprocess-exited-with-error


DRILL-7413: Test and fix scan operator vectors

Enables vector validation tests for the ScanBatch and all  EasyFormat plugins. Fixes a bug in scan batch that failed to set the record count in the output container.
Fixes a number of formatting and other issues found while adding the tests.

Note: This PR builds on DRILL-7403, which is not yet merged. So, the commits from DRILL-7403 appear here as well. For review, just focus on the DRILL-7413 commit. I will rebase to include just that commit once DRILL-7403 is merged.

+1

@paul-rogers please resolve the conflicts.

Rebased on master, resolved conflicts, and reran tests.


Managed Disks for Master nodes

Right now Managed Disks are only possible for Swarm Agents whereas the Master nodes still use Storage Accounts. Please enable Managed Disks also for Master nodes.

@kbhattmsft what is the scenario that managed disks will cover if it was enabled on masters?

To clarify, i thought we have enabled managed disk for all the orchestrators' agent node. @kbhattmsft I think you were in the context of Swarm. Since @anhowe has changed the title, I will fix this one regardless of orchestrator type. Curious like Anthony, what's the scenario you need manageddisk for master nodes?

Well, I do have a scenario where I would like to have managed disks on master nodes. I need to run postgre  database over several agent nodes, as storage I cant use Azure Fie Storage since it is using SMB which is not suitable for postgre do mount permisson issues. Therefore my best call is to install managed disks on a master and create an nfs share on it, makes sense? I tested managed disks for k8s, they only work for agent nodes, not for master.

@Zenocolo er, what are you doing exactly? Kubernetes has no support for attaching or dealing with managed disks currently, and why would you be running the NFS share from the masters anyway?
Regardless of those answers, I guess I'm at a complete loss as to why we would not have managed disks for masters too. The Azure way (I know there are bumps along the way) is to get everything on VMSS + Managed DIsks, no?

@colemickens well, at the end of the day I'm trying to define best practice for MYSQL/POSTGRE on Azure Container Service/k8s. Lets take MYSQL, there will be pods running on 3 different nodes, but they need to share data, therefore they require a persistent volume available across the 3 nodes. In the Azure world that would be Azure File Storage, but since this can only be mounted via SMB protocol this is no option (there are various articles about this). Therefore I'm trying to mount managed disk into master node and creating via LVM/NFS a share that can be resized when needed. Make sense?
Managed disk did work for me using the ACS engine (https://github.com/Azure/acs-engine/blob/master/examples/disks-managed/kubernetes-preAttachedDisks-vmas.json), not sure thats they right way to do it but this tool seems quite handy to me. When not mistaken, I think managed disk support was added in 1.6 as preview.

I still don't know why you would put that on the masters though. Something
goes wrong with NFS and you've taken out your cluster.
Anyway, I highly recommend you evaluate using stateful sets for this with
normal persistent volumes and replication.
I still think we should support managed disks for masters as well as nodes,
if we don't already.
On Apr 12, 2017 5:13 AM, "Zenocolo"<EMAIL_ADDRESS>wrote:
@colemickens https://github.com/colemickens well, at the end of the day
I'm trying to define best practice for MYSQL/POSTGRE on Azure Container
Service/k8s. Lets take MYSQL, there will be pods running on 3 different
nodes, but they need to share data, therefore they require a persistent
volume available across the 3 nodes. In the Azure world that would be Azure
File Storage, but since this can only be mounted via SMB protocol this is
no option (there are various articles about this). Therefore I'm trying to
mount managed disk into master node and creating via LVM/NFS a share that
can be resized when needed. Make sense?
Managed disk did work for me using the ACS engine (
https://github.com/Azure/acs-engine/blob/master/examples/
disks-managed/kubernetes-preAttachedDisks-vmas.json), not sure thats they
right way to do it but this tool seems quite handy to me. When not
mistaken, I think managed disk support was added in 1.6 as preview.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/acs-engine/issues/371#issuecomment-293557726,
or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAT9dCWxjhhu_4NpbVvb7Gto4vS1tYkdks5rvL_lgaJpZM4MV91Z
.

(By the way, I don't mean to be too prescriptive, just some quick suggestions. If you do end up with NFS (or Gluster or whatever) underneath the DB, I'd recommend running that on a separate specialized VM rather than overloading the master for that purpose.)

@colemickens TNX for suggestion, I think you're right, running Gluster clyster on a seprate VM's is best option. I also tried to create with ACS engine a second agentpool "storage" with managed disks to put them into VMscaleSet, but turned out that this is still not supported, for whatever reason, so I guess running separate VMscaleSet for Gluster is the way to go.

RE VMSS for K8S cluster: I did some research I found that VMSS is supported for DC/OS and SWARM clusters when they use managed disk, but not for K8S, may I ask for the  reason of this? (might be my missing K8S knowledge). Error message is: VirtualMachineScaleSets are not supported with Kubernetes since Kubernetes requires the ability to attach/detach disks, but in my view that is not an issue with managed disks?

VMSS doesn't allow for disk attachment to single VMs. That restriction is true regardless of if they're managed disks or not.

@anhowe do we intentionally not allow MD for masters?

@colemickens the work for managed disks on masters has not been done yet due to resourcing.  I asked a question further up to try to understand priority: what is the scenario that we are solving if we enable managed disks on masters?

Managed disks were not added due to the principle of smallest necessary change.  Please answer question at top, and we can consider re-opening.

Re-opening issue, since we have now found the scenario where this makes sense to add managed disks to masters.  On June 13th, Microsoft announced that all managed disks are encrypted by SSE: https://azure.microsoft.com/en-us/blog/azure-managed-disks-sse/.
Having managed disks on Masters now means you can build a cluster that uses disks encrypted with SSE.


[FEAT] Auto-generate Daffodil package list for markdown files

:bulb: Feature request
Feature Name
Auto-generate Daffodil package list for markdown files
The Desired Behavior
Auto-generate the list of Daffodil packages with project name, package name, version, and stability (https://github.com/graycoreio/daffodil?tab=readme-ov-file#packages-)
Write a "generate" command that processes the package.json of all the publishable packages and the spits out content into the markdown file.
Your Use Case
As a developer, I don't want to have to manually update the list of available Daffodil packages on multiple markdown files.
Prior Work

Environment

Daffodil version: X.Y.Z
Angular version: X.Y.Z

For Tooling issues:
- Node version: XX
- Platform:

Others:

Where would this list of packages be displayed?

Where would this list of packages be displayed?

https://github.com/graycoreio/daffodil?tab=readme-ov-file#packages-

But it can be its own file or do we need to embed it in the main README? I think we might need to do this with release please.

I think it needs to be in the main README

During planning we decided that the generation should occur during release please cycle.

Although release please does have some kind of plugin system, loading custom plugins is janky, nigh impossible with the GH action. See https://github.com/ipfs-shipyard/release-please-ipfs-plugin for an example

Try to modify https://github.com/graycoreio/daffodil/blob/develop/.github/workflows/release-please.yml before release-please runs to see if it will add your changes to the diff release-please submits.

That doesn't work unfortunately. The only other solution I can see is to ditch the action and run using the CLI. Either that or wait until google lets us load plugins with the action.

@griest024 Should I just manually update the list of packages for now then?

@griest024 Try a task afterwards of the action to take the result branch, modify the README and push to the same branch as release-please.


Refund support?

The core gateway doesn't include API for refund and direct refund

@shcode i don't think so current version is support for refund. But contributing to this repo are welome 👍

Yes for now it haven't been implemented.
Our team are currently developing further on this library, but haven't publish it yet. In the mean time contribution are welcome.

Merged and fixed by https://github.com/veritrans/go-midtrans/pull/48


Linking fails on Ubuntu 20.04 (IDFGH-3342)

I just upgraded to Ubuntu 20.04, using ESP v4.0. My project compiles under Ubuntu 18.04. After updating I get the attached error.
After update, I also removed ~/.espressif and re-run install.sh (so, the system is more or less a fresh install).
[ 98%] Generating ld/esp32.project.ld
cd /home/diego/src/vayyar-smart-home/walabot-home/build/esp-idf/esp32 && python /home/diego/src/esp-idf-4.0/tools/ldgen/ldgen.py --config /home/diego/src/vayyar-smart-home/walabot-home/sdkconfig --fragments /home/diego/src/esp-idf-4.0/components/esp_ringbuf/linker.lf	/home/diego/src/esp-idf-4.0/components/spi_flash/linker.lf	/home/diego/src/esp-idf-4.0/components/esp_wifi/linker.lf	/home/diego/src/esp-idf-4.0/components/lwip/linker.lf	/home/diego/src/esp-idf-4.0/components/esp_event/linker.lf	/home/diego/src/esp-idf-4.0/components/espcoredump/linker.lf	/home/diego/src/esp-idf-4.0/components/esp32/linker.lf	/home/diego/src/esp-idf-4.0/components/esp32/ld/esp32_fragments.lf	/home/diego/src/esp-idf-4.0/components/xtensa/linker.lf	/home/diego/src/esp-idf-4.0/components/soc/linker.lf	/home/diego/src/esp-idf-4.0/components/heap/linker.lf	/home/diego/src/esp-idf-4.0/components/freertos/linker.lf	/home/diego/src/esp-idf-4.0/components/newlib/newlib.lf	/home/diego/src/esp-idf-4.0/components/app_trace/linker.lf	/home/diego/src/esp-idf-4.0/components/esp_gdbstub/linker.lf --input /home/diego/src/esp-idf-4.0/components/esp32/ld/esp32.project.ld.in --output /home/diego/src/vayyar-smart-home/walabot-home/build/esp-idf/esp32/ld/esp32.project.ld --kconfig /home/diego/src/esp-idf-4.0/Kconfig --env-file /home/diego/src/vayyar-smart-home/walabot-home/build/config.env --libraries-file /home/diego/src/vayyar-smart-home/walabot-home/build/ldgen_libraries --objdump /usr/bin/objdump
Traceback (most recent call last):
  File "/home/diego/src/esp-idf-4.0/tools/ldgen/ldgen.py", line 150, in <module>
    main()
  File "/home/diego/src/esp-idf-4.0/tools/ldgen/ldgen.py", line 126, in main
    mapping_rules = generation_model.generate_rules(sections_infos)
  File "/home/diego/src/esp-idf-4.0/tools/ldgen/generation.py", line 354, in generate_rules
    self._create_exclusions(mapping_rules, default_rules, sections_infos)
  File "/home/diego/src/esp-idf-4.0/tools/ldgen/generation.py", line 448, in _create_exclusions
    general_rule.add_exclusion(specific_rule, sections_info)
  File "/home/diego/src/esp-idf-4.0/tools/ldgen/generation.py", line 100, in add_exclusion
    expansions = do_section_expansion(self, section)
  File "/home/diego/src/esp-idf-4.0/tools/ldgen/generation.py", line 84, in do_section_expansion
    expansions = fnmatch.filter(sections_in_obj, section)
  File "/home/diego/.espressif/python_env/idf4.0_py2.7_env/lib/python2.7/fnmatch.py", line 60, in filter
    for name in names:
TypeError: 'NoneType' object is not iterable

Reminder to anyone else who uses ccache, please run ccache -c when changing distros. Now code compiles, and links for me.

@DiegoActionItem I hope the notes  of my experience with ESP-IDF with its VScode extension Espressif IDF in ubuntu 20.04  can help you:
https://notes.walidamriou.com/2020/05/my-experience-with-esp-idf-with-its.html

Note: if you have fresh install, you should have python3 instead of 2

I hope this notes of  my experience with ESP-IDF with its VScode extension Espressif IDF in ubuntu 20.04 can help you:
https://notes.walidamriou.com/2020/05/my-experience-with-esp-idf-with-its.html

@walidamriou using chmod a+rw is an horrible idea. All you need to do is add your development user to the group dialout (the devices are regenerated each time you insert them into USB, so permissions will change).
sudo adduser diegorocks dialout
# you can logout -> re-login, no need to restart
# or run this, to get a terminal with new group permissions
newgrp dialout

Anyway, the compilation works, so this issue is going to get closed.

@DiegoActionItem I'll add your note to the notes 😀 thank you.

Note: if you have fresh install, you should have python3 instead of 2

You have both, at least i got both verssions on fresh install. This solved my issue with python and prerequisities:
https://linuxconfig.org/ubuntu-20-04-python-version-switch-manager


BUG: Handling conflict with semester long workshops

I am teaching some semester long workshops.
For all workshops including non-conflicting ones, it shows
"You cannot apply for this workshop. You are teaching at a conflicting workshop: 2022-08-22-ashesiu-ds-hybrid."
because the start and end dates overlap. To correctly identify conflicts, we might need to check time conflicts, not just date overlaps.
a) Would it be possible to allow users to ignore / turn OFF certain errors like conflicting with semester long ones?
b) In case of instructor shortages, sometimes we had to teach different parts of conflicting workshops. Should we have a filter and configuration to handle this? Or somehow notify administrator that in case of urgencies, some instructors can indicate preference to be contacted for conflicting workshops, if they willingly would like to take the load of balancing between the conflicting ones.

This is a feature, not a bug. Most workshops run a few days and we do not want to have people signing up for workshops on the same day. I'm closing this here as it is being addressed with #2256


“Releases” section: Time since last release

(Not yet final) designs for P1 updates are here:
https://www.figma.com/file/d3t84J9Uzmj0GZnYROzdQX/Activity-Dashboard?node-id=1623%3A2042
I think the only thing left is to align on the proposed time buckets for both metrics. I am proposing we use the same "granularity system" of time bucketing that we use for the first Usage metric ("X installs since publicly released [insert time bucket]") for consistency, and because I think the same granularity concerns are relevant for these releases metrics. But want to see what others think, too!

@neuromusic Should we archive or close this issue since we don't have plans to pursue a "Releases" section at this time?


Deprecation warning under Ember 2.18

<EMAIL_ADDRESS>is the latest version to date and causes a deprecation warning under ember 2.18 because of its hard dependency on "ember-cli-version-checker": "^1.2.0".
Do we really need a hard dependency on ember-string-ishtmlsafe-polyfill in ember-awesome-macros?

Seems ember ~1.13.0 is tested in ember-try.js, which would justify the need for ember-string-ishtmlsafe-polyfill.
The next ember version tested in ember-try.js is ember-lts-2.12, and for this one and above, ember-string-ishtmlsafe-polyfill should be useless.
Could we release a 0.50.0 without ember-string-ishtmlsafe-polyfill and a 0.42.0 with it to maintain compatibility with ember ~1.13.0? Would that be semver compliant?

That should not be the reason to drop ember 1.13 support. You should file an issue on ember-string-ishtmlsafe-polyfill to bump their version of ember-cli-version-checker.

Actually, there is already an issue https://github.com/workmanw/ember-string-ishtmlsafe-polyfill/issues/8 and a PR https://github.com/workmanw/ember-string-ishtmlsafe-polyfill/pull/7 but no feedback has been provided yet…

lockfiles only involve this project, not consumers. There is nothing left to fix. People just need to update their own lockfiles.


Each child in a list should have a unique "key" prop.

Description
Description of what the bug is about.
Using the provided example we get a react warning:
Each child in a list should have a unique "key" prop.

Check the render method of `Hits`. See https://reactjs.org/link/warning-keys for more information.

Expected behavior
What you expected to happen.
The example should provide a unique key to each hit, so that the warning is not triggered.
Current behavior
What happened.
The code sandbox hit component has a key property, but it does not remove the warning:
const Hit = ({ hit }) => (

      <Highlight attribute="name" hit={hit} />

      <Snippet attribute="description" hit={hit} />

price: {hit.price}

release date: {hit.releaseDate}

);

Screenshots or Logs
If applicable, add screenshots or logs to help explain your problem.

Environment (please complete the following information):

OS: [e.g. Debian GNU/Linux]
Browser: [e.g. Chrome version 90.0]
Meilisearch version: [e.g. v.0.20.0]
instant-meilisearch version: [e.g. v0.5.0]
react-instantsearch version: [e.g. v6.10.3]
React version: [e.g. 16.13.1]

@CaroFG are you sure it does not come from react-isntantsearch, so on the algolia side?

A user said it appeared when he moved from Algolia to Meilisearch, see Discord. As I told the user, I guess Algolia uses by default the objectID they generate for each document, but since we don't use an objectID we should probably provide an example that does not trigger a warning.

Thanks for the context!
Pinging this as good first issue

Hello, may I work on this issue?

Go ahead @replyre!

Hi. @replyre. any news?)

Hello @voronovmaksim
Not done yet, we are waiting for a PR 😊

hey @voronovmaksim, I looked through it but wasn't able to find the root of the issue. Sorry, I forgot to mention it earlier. I will look at it again if you wish on Saturday, as I'm busy right now.
Thank you for your patience.


chdir makes code non-thread safe

Hi, while debugging my own code, stumbled over this in saml_message.rb:
  Dir.chdir(File.expand_path(File.join(File.dirname(__FILE__), '..', '..', 'schemas'))) do
      @schema = Nokogiri::XML::Schema(IO.read('saml-schema-protocol-2.0.xsd'))
      @xml = Nokogiri::XML(document.to_s)
   end

In a single threaded environment this is not an issue, but when there are more parallel threads running, there is a time window when the current working directory is changed for all threads. That could lead to random production failures on Rails using Puma for example ...

What alternative you suggest?

This at least eliminates chdir at run-time - it only does chdir once when .rb files are required. Should also improve performance since it eliminates disk IO at validation time.
https://github.com/onelogin/ruby-saml/pull/181

This is resolved as of c8deef880b7657e34b241a17478ecb49aa21ef8f