Omit Billing Address and Payment Info in the Subscription Process

This change is

Reviewed 1 of 40 files at r1.
Review status: 1 of 40 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 39 of 40 files at r1.
Review status: 40 of 42 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Current coverage is 0.00%

Merging #53 into master will not affect coverage as of b3c3add

No diff could be generated. No reports for #53 found.
Review entire Coverage Diff as of b3c3add

Powered by Codecov. Updated on successful CI builds.

Reviewed 2 of 10 files at r3, 12 of 16 files at r4, 39 of 40 files at r5, 6 of 9 files at r6, 2 of 8 files at r7, 3 of 3 files at r8.
Review status: 66 of 85 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 10 files at r3.
Review status: 62 of 90 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 10 files at r3, 1 of 8 files at r7, 1 of 4 files at r9, 3 of 5 files at r10.
Review status: 68 of 90 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: 68 of 90 files reviewed at latest revision, 2 unresolved discussions.

oscm-portal/javares/org/oscm/ui/resources/Messages_de.properties, line 1720 [r11] (raw file):
Translation is missing.

oscm-portal/javares/org/oscm/ui/resources/Messages_ja.properties, line 1721 [r11] (raw file):
Translation is missing.

Comments from Reviewable

Reviewed 2 of 8 files at r7.
Review status: 70 of 90 files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

Reviewed 2 of 5 files at r10.
Review status: 72 of 90 files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

Reviewed 3 of 10 files at r3, 1 of 40 files at r5.
Review status: 76 of 90 files reviewed at latest revision, 4 unresolved discussions.

oscm-subscriptionmgmt/javasrc/org/oscm/subscriptionservice/bean/SubscriptionServiceBean.java, line 387 [r11] (raw file):
Please change method name.

oscm-subscriptionmgmt/javasrc/org/oscm/subscriptionservice/dao/BillingContactDao.java, line 30 [r11] (raw file):
Please change method name.

Comments from Reviewable

Reviewed 2 of 2 files at r12, 1 of 1 files at r13.
Review status: 79 of 90 files reviewed at latest revision, 4 unresolved discussions.

Comments from Reviewable

Reviewed 1 of 10 files at r3, 3 of 16 files at r4, 2 of 8 files at r7, 1 of 4 files at r9, 7 of 7 files at r11.
Review status: all files reviewed at latest revision, 4 unresolved discussions.

Comments from Reviewable

Reviewed 1 of 40 files at r1, 5 of 10 files at r3, 1 of 40 files at r5, 3 of 8 files at r7, 1 of 4 files at r9, 5 of 5 files at r10, 2 of 2 files at r12, 1 of 1 files at r13.
Review status: all files reviewed at latest revision, 4 unresolved discussions.

Comments from Reviewable

Review status: all files reviewed at latest revision, 4 unresolved discussions.

oscm-portal/javares/org/oscm/ui/resources/Messages_de.properties, line 1720 [r11] (raw file):
Done.

Comments from Reviewable

Review status: all files reviewed at latest revision, 4 unresolved discussions.

oscm-portal/javares/org/oscm/ui/resources/Messages_ja.properties, line 1721 [r11] (raw file):
Done

Comments from Reviewable

Reviewed 248 of 249 files at r14, 1 of 1 files at r15, 2 of 2 files at r16, 3 of 3 files at r17, 1 of 1 files at r18.
Review status: all files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

Comments from Reviewable

Reviewed 4 of 22 files at r19.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Reviewed 11 of 12 files at r20.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Pinecone Ingest Error

It seems like there was an update to "chunk" it out while I was working on this, so it looks like a known problem. But, even with the chunking I am still getting:
error [Error: PineconeClient: Error calling upsert: Error: PineconeClient: Error calling upsertRaw: FetchError: The request failed and the interceptors did not return an alternative response]
/Users/n****l/gpt4-pdf-chatbot-langchain/scripts/ingest-data.ts:50
throw new Error('Failed to ingest your data');
^
[Error: Failed to ingest your data]
Node.js v18.15.0
Any ideas would be great, thanks!

Hi, did you have the same error before the chunk function was added?

I believe it was the same error yes.
And, yes, finished the troubleshooting list, restart and all. No dice. I'll keep trying.

I'm uploading a 12mb PDF that had some trouble. This helped me get ingest it:

Re: instructions to add Dimensions: I had to go into my default project and create a new index, with the same name as I set in pinecone.ts, e.g. const PINECONE_INDEX_NAME = 'langchainjs-pdf-test';

I also added async-sema from here: https://github.com/vercel/async-sema which helps slow your code down.
Full ingest-data.ts looks like this:

import { RecursiveCharacterTextSplitter } from 'langchain/text_splitter';
import { OpenAIEmbeddings } from 'langchain/embeddings';
import { PineconeStore } from 'langchain/vectorstores';
import { pinecone } from '@/utils/pinecone-client';
import { PDFLoader } from 'langchain/document_loaders';
import { PINECONE_INDEX_NAME, PINECONE_NAME_SPACE } from '@/config/pinecone';

import { Sema } from 'async-sema';
const s = new Sema(
  2, // Allow 4 concurrent async calls
  {
    capacity: 20 // Prealloc space for 100 tokens
  }
);

/* Name of directory to retrieve files from. You can change this as required */
// const filePath = 'docs/MorseVsFrederick.pdf';
const filePath = 'docs/Sacher_Jessica_C_201807_PhD.pdf';

export const run = async () => {
  try {
    /*load raw docs from the pdf file in the directory */
    const loader = new PDFLoader(filePath);
    // const loader = new PDFLoader(filePath);
    const rawDocs = await loader.load();

    console.log(rawDocs);

    /* Split text into chunks */
    const textSplitter = new RecursiveCharacterTextSplitter({
      chunkSize: 1000,
      chunkOverlap: 200,
    });

    const docs = await textSplitter.splitDocuments(rawDocs);
    console.log('split docs', docs);

    console.log('creating vector store...');
    /*create and store the embeddings in the vectorStore*/
    const embeddings = new OpenAIEmbeddings();
    const index = pinecone.Index(PINECONE_INDEX_NAME); //change to your own index name

    //embed the PDF documents

    /* Pinecone recommends a limit of 100 vectors per upsert request to avoid errors*/
    const chunkSize = 50;
    for (let i = 0; i < docs.length; i += chunkSize) {
      const chunk = docs.slice(i, i + chunkSize);
      console.log('chunk', i, chunk);
      await s.acquire()
      try {
        await PineconeStore.fromDocuments(
          index,
          chunk,
          embeddings,
          'text',
          PINECONE_NAME_SPACE,
        );
      } finally {
        s.release()
      }
    }
  } catch (error) {
    console.log('error', error);
    throw new Error('Failed to ingest your data');
  }
};

(async () => {
  await run();
  console.log('ingestion complete');
})();

I believe it was the same error yes.
And, yes, finished the troubleshooting list, restart and all. No dice. I'll keep trying.

What version of LangChain and Pinecone are you using?

I'm uploading a 12mb PDF that had some trouble. This helped me get ingest it:

Re: instructions to add Dimensions: I had to go into my default project and create a new index, with the same name as I set in pinecone.ts, e.g. const PINECONE_INDEX_NAME = 'langchainjs-pdf-test';
I also added async-sema from here: https://github.com/vercel/async-sema which helps slow your code down.
Full ingest-data.ts looks like this:

import { RecursiveCharacterTextSplitter } from 'langchain/text_splitter';
import { OpenAIEmbeddings } from 'langchain/embeddings';
import { PineconeStore } from 'langchain/vectorstores';
import { pinecone } from '@/utils/pinecone-client';
import { PDFLoader } from 'langchain/document_loaders';
import { PINECONE_INDEX_NAME, PINECONE_NAME_SPACE } from '@/config/pinecone';

import { Sema } from 'async-sema';
const s = new Sema(
  2, // Allow 4 concurrent async calls
  {
    capacity: 20 // Prealloc space for 100 tokens
  }
);

/* Name of directory to retrieve files from. You can change this as required */
// const filePath = 'docs/MorseVsFrederick.pdf';
const filePath = 'docs/Sacher_Jessica_C_201807_PhD.pdf';

export const run = async () => {
  try {
    /*load raw docs from the pdf file in the directory */
    const loader = new PDFLoader(filePath);
    // const loader = new PDFLoader(filePath);
    const rawDocs = await loader.load();

    console.log(rawDocs);

    /* Split text into chunks */
    const textSplitter = new RecursiveCharacterTextSplitter({
      chunkSize: 1000,
      chunkOverlap: 200,
    });

    const docs = await textSplitter.splitDocuments(rawDocs);
    console.log('split docs', docs);

    console.log('creating vector store...');
    /*create and store the embeddings in the vectorStore*/
    const embeddings = new OpenAIEmbeddings();
    const index = pinecone.Index(PINECONE_INDEX_NAME); //change to your own index name

    //embed the PDF documents

    /* Pinecone recommends a limit of 100 vectors per upsert request to avoid errors*/
    const chunkSize = 50;
    for (let i = 0; i < docs.length; i += chunkSize) {
      const chunk = docs.slice(i, i + chunkSize);
      console.log('chunk', i, chunk);
      await s.acquire()
      try {
        await PineconeStore.fromDocuments(
          index,
          chunk,
          embeddings,
          'text',
          PINECONE_NAME_SPACE,
        );
      } finally {
        s.release()
      }
    }
  } catch (error) {
    console.log('error', error);
    throw new Error('Failed to ingest your data');
  }
};

(async () => {
  await run();
  console.log('ingestion complete');
})();

Thanks, but I'm not sure async-sema should be necessary here to work.

You're right, it worked without async-sema! For some reason I was getting timeouts that seemed to error from hitting the endpoint too much, but maybe I just misread the errors. Removed it and it works!

Hello everyones,
I'm having the same issue if we can re-open here?
I've not made any changes to ingest-data.ts and not using async-sema as it's noticed that's not mandatory.
The pdf document I have have been trimed from images (it's a phd) and got ~60 pages with 21,000 words.
File size is 646ko.
Here is the error:
error [Error: PineconeClient: Error calling upsert: Error: PineconeClient: Error calling upsertRaw: FetchError: The request failed and the interceptors did not return an alternative response]
c:\Users\Administrator\source\repos\gpt4-pdf-chatbot-langchain\scripts\ingest-data.ts:51
    throw new Error('Failed to ingest your data');

Thanks in advance.


THEEDGE-2572 - [UI] Add test to cover Groups.js

Description
This PR adds an end-to-end cypress test for the Groups page.
Fixes # THEEDGE-2572
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[x] Tests update

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I run npm run lint:js:fix to check that my code is properly formatted

Codecov Report
Base: 30.53% // Head: 30.68% // Increases project coverage by +0.15% :tada:

Coverage data is based on head (b425ab2) compared to base (0af5674).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #560      +/-   ##
==========================================
+ Coverage   30.53%   30.68%   +0.15%
==========================================
  Files         126      126
  Lines        2702     2708       +6
  Branches      831      831
==========================================
+ Hits          825      831       +6
  Misses       1723     1723
  Partials      154      154

Impacted Files
Coverage Δ

src/components/general-table/ToolbarKebab.js
87.50% <0.00%> (ø)

src/Routes/ImageManagerDetail/DetailsHeader.js
86.66% <0.00%> (+0.95%)
:arrow_up:

src/Routes/GroupsDetail/GroupsDetail.js
42.69% <0.00%> (+1.99%)
:arrow_up:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Tracking python lists (or ListWrapper) in keras custom preprocessing layers

System information

Custom code
OS Platform and Distribution:

PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian

TensorFlow installed from binaries:
TensorFlow version: 2.4.0
Python version: 3.6.8

Problem
Hi,
My problem is the following: I try to create a custom keras preprocessing layer in which I absolutely need an attribute which is a regular python list computed via adapt method. When I include my layer in model and I save it (via SavedModel), my list attribute becomes empty at load time. Is there anyway to make this list (or any other python object) trackable so that it is properly loaded?
Some additional points:

It can be made trackable if I use a variable instead of a list but in my case a list is necessary.
I still can use a variable and transform it to a list at call time, but this will work only in eager mode and I need it to work at graph mode also

Source code / logs
Here a simple example to reproduce my issue:
import numpy as np
import tensorflow as tf

from tensorflow.python.ops import math_ops

@tf.keras.utils.register_keras_serializable()
class BucketizeLayer(tf.keras.layers.experimental.preprocessing.PreprocessingLayer):

    def __init__(self, quantiles, **kwargs):
        self.quantiles = quantiles
        super(BucketizeLayer, self).__init__(**kwargs)
        self._boundaries = None

    def adapt(self, data):
        if isinstance(data, tf.Tensor):
            data = data.numpy()

        self._boundaries = np.nanquantile(data, self.quantiles).tolist()

    def call(self, data):
        return math_ops.bucketize(data, self._boundaries)

    def get_config(self):
        config = {'quantiles': self.quantiles}
        base_config = super(BucketizeLayer, self).get_config()
        return dict(**config, **base_config)

data = 3 * np.random.randn(100) + 5
bucketize = BucketizeLayer(quantiles=[0.1, 0.5, 0.9])
bucketize.adapt(data)
print(bucketize(data))

inp = tf.keras.Input(shape=(1,), dtype=tf.float32)
model = tf.keras.models.Model(inp, bucketize(inp))
model.save('bucketize/')
del model
model = tf.keras.models.load_model('bucketize/')
model.layers[1]._boundaries
# output: ListWrapper([])

@ianqouda
i ran the code shared and do not see an empty list, please refer to the gist here and share a colab gist with the error reported.

@Saduf2019 thank you for your reponse, here is a https://colab.research.google.com/gist/Saduf2019/ac2b96a3d295f7744050b242d95fffb4/untitled565.ipynb#scrollTo=DlvaRQRQr97I with more detailed code. The problem is that the attribute '_boubdaries' becomes empty after loading the model.

I am able to replicate the issue reported on tf 2.4 and nightly, please find the gist here

@ianqouda I updated your code (mainly adding get_config method and self._boundaries = boundaries). With those modifications, everything works as expected. Please check the gist here.
Please verify once and close the issue if this was resolved for you. Thanks!

@jvishnuvardhan Thank you very much! This works fine for this example I showed here but in more complexe context (which is my case) this solution alters a little bit the behaviour of my layer. More precisely if I have this boundary as an argument which I can set manually and force the adapt method not to override it then this solution would not work any more.
In the mean time I found another way to do it by creating a trackable list through inhereting from this object from tensorflow.train.experimental.PythonState and it works fine!


TODO: Build CI container from GitHub Actions

Requested feature
Add a GitHub Action workflow to build CI Docker Image.
Motivation
Make refreshing CI image easier and more repeatable by replacing the manual process. Include some best practices like image signing.

What should trigger this action? Should it be manual only?

Yes, only manual. I don't think we want to generate for each commit, and you have to be a member to trigger it.


[#4183] Cleanup plugin dependency

Introduce maven BOM for plugin dependency

Codecov Report

Merging #4184 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4184      +/-   ##
==========================================
- Coverage   41.17%   41.16%   -0.02%
==========================================
  Files        2365     2365
  Lines       74343    74343
  Branches    10064    10064
==========================================
- Hits        30614    30606       -8
- Misses      40903    40911       +8
  Partials     2826     2826

Impacted Files
Coverage Δ

...npoint/rpc/server/SimpleServerMessageListener.java
80% <0%> (-20%)
:arrow_down:

...vercorp/pinpoint/rpc/packet/ServerClosePacket.java
52% <0%> (-16%)
:arrow_down:

...rp/pinpoint/rpc/server/PinpointServerAcceptor.java
85.13% <0%> (-4.73%)
:arrow_down:

...m/navercorp/pinpoint/test/OrderedSpanRecorder.java
70.19% <0%> (-3.85%)
:arrow_down:

...navercorp/pinpoint/rpc/common/SocketStateCode.java
82.92% <0%> (-2.44%)
:arrow_down:

...java/com/navercorp/pinpoint/rpc/DefaultFuture.java
72.5% <0%> (-1.67%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
81.25% <0%> (+0.69%)
:arrow_up:

...point/rpc/client/DefaultPinpointClientHandler.java
72.34% <0%> (+0.96%)
:arrow_up:

...pinpoint/profiler/monitor/DeadlockMonitorTask.java
19.76% <0%> (+1.16%)
:arrow_up:

.../com/navercorp/pinpoint/profiler/context/Span.java
50% <0%> (+1.72%)
:arrow_up:

... and 2 more

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 4692188...b15bfa2. Read the comment docs.


IPv6-related problems with run_simple on "localhost"

I have a Linux Mint system. Domain name "localhost" is resolved to both "::1" (IPv6) and "<IP_ADDRESS>" (IPv4).
When Werkzeug's run_simple binds to "localhost", it uses the first corresponding address - in case of my system, the IPv6 one. But, for some reason, Mozilla Firefox seems to interpret "localhost" as <IP_ADDRESS> only. Thus, opening "localhost:5000" in Firefox results in error - while in Chrome it works fine.
I think, for the time being, Werkzeug should prefer IPv4 addresses over IPv6 ones when binding to a domain name (or, at least, when binding to localhost).

<IP_ADDRESS> does seem to be the default.


Allow to configure the number of nodes in the deployments?

The number of nodes in the deployments is currently hard-coded to 2. Maybe this should be configurable, although I don't really see a good use case: more nodes is easier for the user, and doesn't cost anything...
I leave this here as a placeholder.

Also, it's very easy to change the 'Number of copies' in the UI for the deployment.


Added undo/redo support for lock/unlock and "children not selectable" buttons.

Added undo/redo support for lock/unlock button and "children not selectable" button for both the canvas and spatial editor. Fixes #27769

@akien-mga this is ok, but should play together with @JFonS changes?

Indeed, this will need to be rebased to take #28130 into account.

This PR looked good. @Sintinium do you plan on adding support for 3D grouping? Or should I work on that? Either way is fine for me :)

@JFonS Thanks! I'll be able to get 3D grouping supported this weekend hopefully. When pulling master I broke my local branch. I might have to end up opening a separate pull request since I'm not the best at git on large projects still.


scrollbar-test is causing incorrect layout

What happens?
The following file:
https://github.com/scalar/scalar/blob/a792002867dc0785c5fb1736b1451c2295f7073d/packages/themes/src/utilities/hasObtrusiveScrollbars.ts#L14
is messing with the layout:
https://github.com/user-attachments/assets/829d98f4-54d1-4ced-8f3b-5ec0c73a64f3
What did you expect to happen?
A correct layout as shown in previous versions (tested with<EMAIL_ADDRESS>https://github.com/user-attachments/assets/6aa104f1-77c8-4044-b2d5-e71703c876dd
How can we reproduce the issue?

Create a new fastify app
Install @fastify/swagger and<EMAIL_ADDRESS>(latest at this point in time)
Make an example project:

import fastify from "fastify";
import swagger from "@fastify/swagger";
import scalar from "@scalar/fastify-api-reference";

export const app = fastify({ logger: true });

app.register(swagger, {
	openapi: {
		openapi: "3.1.0",
		info: {
			title: "Example API",
			description: "Example api documentation",
			version: "1.0.0",
		},
	},
});

app.register(scalar, {
	routePrefix: "/reference",
	configuration: {
		theme: "none",
		spec: {
			content: () => app.swagger(),
		},
	},
});

app.listen({ port: 8080 }, (err, address) => {
	if (err) {
		console.error(err);
		process.exit(1);
	}

	app.log.info(`Server listening at ${address}`);
});

The incorrect layout should now be visible.

OpenAPI Document
No needed

Hey @emilio-toledo, sorry about that! That test div is supposed to be removed after the test runs. Opened a PR with a fix.

No problem @hwkr, thank you for the fast response!
I have just downgraded to 1.25.3 in the meantime.


[1.20.1] Compacting Drawers seems locked always

Functional Storage Version:1.20.1-1.2.8
Titanium Version:3.8.25
ModPack:ATM9 9-0.2.39
Crashlog If Applicable : No crash
Issue : Item don't go inside any compacting drawer unless items are already present in compacting drawer.
To reproduce : Place unlocked compacting drawer in world, place hopper into it, place any item in hopper. Item stay in hopper.
Tested with : Compacting Drawer, Simple Compacting Drawer / Hopper, Integrated Dyn exporter, Modular Router
I found out about this trying to compress all combs into combs blocks with only one drawer. With non compacting drawers, the issue is not present.

This is how they work, they need to be configured first


Is there any evidence that softmax one can takes advantages over normal softmax?

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

Personal experimentation reported decreased performance and unstable training process with the softmax_one function with DeiT3 trained on ImageNet1K .
Training Log

Followed training ViT-Small configuration of DeiT III: Revenge of the ViT.
ViT-S with normal softmax: 80.8% validation set top1 accuracy.
ViT-S with softmax_one: 80.7% validation set top1 accuracy + fluctuations in loss and accuracy.

Implementation using Jax
def softmax_one(
    x,
    axis: Optional[Union[int, Tuple[int, ...]]] = -1,
    where: Optional[Array] = None,
    initial: Optional[Array] = None) -> Array:

    # subtract the max for stability and compute exponentials
    x_max = jnp.max(x, axis, where=where, initial=initial, keepdims=True)
    exp_x = jnp.exp(x - x_max)
    #compute softmax values and add on in the denominator
    result = exp_x / (1 + jnp.sum(exp_x, axis=axis, keepdims=True))
    if where is not None:
        result = jnp.where(where, result, 0)
    return result

Please let me know if I've done any mistakes.
I will run same experimentations again if that's the case.
Personal Thoughts
I think adding zero token for the attention score aggravates attention collapse problem in the Transformer architecture. Attention collapse problem is stated in DeepViT: Towards Deeper Vision Transformer as following:

We empirically observed that as the depth of ViTs increases, the attention maps, used for aggregating the features for each transformer block, tend to be overly similar after certain layers, which makes the representations stop evolving after certain layers. We name this specific issue as attention collapse. This indicates that as the ViT goes deeper, the self-attention mechanism becomes less effective for generating diverse attentions to capture rich representations.

Query-Key Normalization for Transformers(EMNLP 2020) suggested that their method of L2 normalization on Queries and Keys lead to diffuse attention patterns and increased performance. Their visualization of attention map with/without the normalization is given below.

Another paper Scaling Vision Transformers to 22 Billion Parameters(ICML 2023)  also proposed that instability of training large-scale transformers can be controlled by normalization on Queries and Keys. The graph below show that attention score almost becomes one-hot vector(5th graph), preceding the divergence of training loss(1st graph).

On my personal opinion, dense/diverse attention scores benefits the training rather than attention maps consisted with zeros and ones. Thus I think softmax_one may comparably aggravate attention collapse since previous legacy softmax couldn't reach zero value for the attention score, but softmax_one can.


Add Crossroad

Project URL
https://github.com/giginet/Crossroad
Category
Routing
Description
Crossroad is an URL router focused on handling Custom URL Schemes. Using this, you can route multiple URL schemes and fetch arguments and parameters easily.
Why it should be included to awesome-ios (optional)
This library is used with various apps.
Checklist

[x] Only one project/change is in this pull request
[x] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 3 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

1
302
https://github.com/vsouza/awesome-ios/blob/master/header.png?raw=true redirects tohttps://github.com/vsouza/awesome-ios/raw/master/header.png

313
301
https://github.com/yuzushioh/EthereumKit redirects tohttps://github.com/D-Technologies/EthereumKit

3026
301
http://bgr.com/ios-7/ redirects tohttps://bgr.com/ios-7/

  Generated by :no_entry_sign: Danger

This change is not useful for my adding library.
However, in this time, I fixed broken CI.
https://github.com/vsouza/awesome-ios/pull/2553/commits/81762c8f788a1fad563d79bd4e9f5193f5a9dbaa

@giginet Thanks for fixing CI.

Thanks for contributing, @giginet 🎉


Capture lost information of number values in JS floats

Since we are interpreting in JS it makes sense to use JS floats for all numbers and their operations wherever possible. However, I think there are a few problems with that:

NaN: There are many different NaN representations containing a payload. I don't think that there is a way to access the payload in JS (or that it is propagated through operations at all). But the WebAssembly spec says that the payloads should propagate through operations according to well-defined rules https://webassembly.github.io/spec/core/exec/numerics.html#aux-nans. I think this is important, because the bits of a NaN could be reinterpreted as an i64 integer for example. The same applies to the sign bit I think.

+-0:  It is possible to distinguish +0 and -0 in JS but not with ===. That is why test cases with these values are currently useless, because the testing framework in JS treats them as the same. Again, I think we need to store some extra information about the sign.

I will try to come up with some simple examples and run them through the reference interpreter to make the issue more clear. We dont have enough implemented yet to show the NaN issues, but here is a sample test case with the +-0 issue https://github.com/xtuc/js-webassembly-interpreter/blob/master/test/interpreter/kernel/exec/numeric-instructions.js#L383-L398.

It's clear enough to me.
I would box every numbers in JS and add this informations.
Btw I recommend you testing with https://mbebenita.github.io/WasmExplorer/

#49 Fixes the test issue with +-0. I think its enough to store the extra information for NaNs. My idea would be to make a maybeNumber type that looks something like this (pseudocode):
{
  isNaN: false|true,
  value: number
}

The payload of a NaN is a positive integer, so we can store the sign with it. If the value is negative, then its absolute value is the payload and the NaN has a negative sign.
We'd have to change all existing floating point operations though, such that they work with this kind of inputs instead of numbers.
What do you think @xtuc ? I'm happy to do it, but maybe there is a simpler way.

Lgtm. We need to make sure to not use Number.isNaN anymore.
I think that we can store the sign too. We could use it for faster comparaison or for the i64 (2x i32) type.


Feature/translated consent docs

Adresses issue 401. Ask whether the consent forms will need to be translated eventually. Added new attributes to the proposal model and added a new page in the process, before uploading the consent forms. The implementation has been discussed with Desiree.

Migrations seem to be fine, so this can be merged! (once translations fixed)


Update getGCData in SharedObject / DDS to not use full summarize

The getGCData uses the data generated during summary to find list of outbound routes from a DDS. For this, it runs the full snapshot logic. This needs to be changed to make it more efficient and not run full snapshot.

@agarwal-navin, I was looking at how to avoid serialization here, related to async summarization. I tried a couple of approaches (see linked commits).

Effectively force all implementations of SharedObject to override getGCDataCore, with a utility function that will walk any object to find handles. SharedObject.ts and utils.ts are the most interesting things in here: https://github.com/scarlettjlee/FluidFramework/commit/7dd4d9883879e7dbba5f36db8330267dca50b4a6 (This is not complete, there are some more DDSs to be fixed up.)
This is a bigger change, which seems counter to [I think] the original motivation of reusing snapshotCore to reduce the burden on DDS creators.
I tried to make it a little less painful by adding an abstract method get GCRoot to return the object to be examined but it's not saving much and leads to some ugliness of having to implement it unnecessarily when getGCDataCore is overridden.
Change SummarySerializer to GCSerializer which is used only during GC (summarization uses regular FluidSerializer) and have it only collect handles and not serialize. It's totally lying about being a serializer though, which could theoretically result in unexpected behaviour. https://github.com/scarlettjlee/FluidFramework/commit/975b1c0229bbfd1b5c90f4ce8a751b4abbca8637

Thoughts?
FYI, @DLehenbauer.

I like the approach for #2 more because #1 is too complex and like you said adds burden to DDS creators. I wouldn't want to do this unless necessary.
For #2, if we can somehow limit the scope of where and how the GCSerializer is used, we should be fine for now. For example, serialize could return only the serialized handles in the data - we can serialize the existing serializedRoutes array and return it or we can store the serialized handles (output of serializeHandle API), serialize this list and return it. I am guessing that serializing these simple array / object list should not be that expensive?

Okay, we'll go with some variation of option 2. In that case, that doesn't change the work for async summarization. (Option 1 would have removed summarization code path from GC so it wouldn't have needed to be also split into sync and async passes.)

Tracked by AB#406


Unable to build from pypi source tarball

Hi there,
while I was working on a Spack recipe for PennyLane and PennyLane-Lightning, I have noticed two small issues:

the tarball from pypi does not contain CMakeLists.txt, hence the build fails; I resorted to using the github tarball for now
CMake is not documented as source build dependency for PennyLane-Lightning; it might be useful for users to have it explicitly mentioned for this special type of builds.

For reference my Spack PR: https://github.com/spack/spack/pull/34838

Thank you for reporting this issue @marcodelapierre.
We will definitely look into this.

Hi @marcodelapierre thanks for reporting this. Just an FYI, there was some prior work started on adding Spack support back last year, but we never opened a PR due to additional commitments needed to complete this (https://github.com/mlxd/spack/tree/pennylane_lightning)
I'll try to take a look at your PR later this week, and see if we need to combine anything from my branch onto yours for this.


Slurm collector: Add more filter options for sacct call

This closes #472

Codecov Report

Merging #511 (67247cd) into main (25a2fbe) will decrease coverage by 1.28%.
The diff coverage is 0.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #511      +/-   ##
==========================================
- Coverage   56.80%   55.53%   -1.28%
==========================================
  Files          45       44       -1
  Lines        3929     3567     -362
  Branches       58        0      -58
==========================================
- Hits         2232     1981     -251
+ Misses       1697     1586     -111

Components
Coverage Δ

apel_plugin
∅ <ø> (∅)

auditor
81.90% <ø> (ø)

slurm_collector
35.98% <0.00%> (-0.41%)
:arrow_down:

slurm_epilog_collector
0.00% <ø> (ø)

htcondor_collector
∅ <ø> (∅)

priority_plugin
37.92% <ø> (ø)


KnexTimeoutError: Knex: Timeout acquiring a connection

Expected Behavior
The Backstage app should normally connect to the PostgresSQL DB hosted on an external service in this case hosted on ScaleGrid.
Actual Behavior
Upon starting the Backstage app (yarn dev), I get this error: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
Steps to Reproduce

Configure a ScaleGrid cluster & create a PostgresSQL DB hosted on that cluster with basic (default) parameters & get the credentials
Add the database credentials (host, username, password, port) to the app-config.yaml under the database group directly or via environment variables.
Start the backstage app yarn dev & you should the error being produced in the start-up logs
(Attempted solution/remedy) I also attempted this connection pool override configuration but it still produces the same error:

database:
    client: pg
    connection:
      host: ${POSTGRES_HOST}
      port: ${POSTGRES_PORT}
      user: ${POSTGRES_USER}
      password: ${POSTGRES_PASSWORD}
    knexConfig:
      pool:
        min: 3
        max: 12
        acquireTimeoutMillis: 60000
        createTimeoutMillis: 30000
        destroyTimeoutMillis: 5000
        idleTimeoutMillis: 60000
        reapIntervalMillis: 1000
        createRetryIntervalMillis: 200
        propagateCreateError: false

Context
Not an ideal situation especially if we have to build a Docker image using an external DB host.

We are having the same issue.

Hey @cvrlnolan How did you fix this?

Hey @Hanyman8, @angeliski
We're not fully confident that we've solved it yet, but it's been 24 hours without seeing the issue so we're hoping it's resolved. We simply increased the min number of available pools with the code that @cvrlnolan posted above.
here's what we used.
database:     client: pg     connection:       host: ${POSTGRES_HOST}       port: ${POSTGRES_PORT}       user: ${POSTGRES_USER}       password: ${POSTGRES_PASSWORD}     knexConfig:       pool:         min: 15         max: 30         acquireTimeoutMillis: 60000         createTimeoutMillis: 30000         destroyTimeoutMillis: 5000         idleTimeoutMillis: 60000         reapIntervalMillis: 1000         createRetryIntervalMillis: 200         propagateCreateError: false
Hope this helps!


v2.3.0 breaks plugin

Before opening the issue, have you...?

[X] Searched for existing issues
[X] Looked through common issues
[X] Updated plugin to the latest version (if applicable)

Describe the bug
after updating the plugin is stuck in a boot look with a syntax error
To Reproduce
updated and rebooted plugin
Expected behavior
the plug to update and run as normal
Logs
log from homebridge:
[8/19/2024, 9:21:42 AM] [@o-lukas/homebridge-smartthings-tv] Child bridge process ended
[8/19/2024, 9:21:42 AM] [@o-lukas/homebridge-smartthings-tv] Process Ended. Code: 1, Signal: null
[8/19/2024, 9:21:49 AM] [@o-lukas/homebridge-smartthings-tv] Restarting Process...
[8/19/2024, 9:21:50 AM] [@o-lukas/homebridge-smartthings-tv] Launched child bridge with PID 24742
SyntaxError: Unexpected token 'with'
at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:118:18)
at callTranslator (node:internal/modules/esm/loader:273:14)
at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:278:30)
[8/19/2024, 9:21:50 AM] [@o-lukas/homebridge-smartthings-tv] Child bridge process ended
Logs
log from homebridge:
[8/19/2024, 9:21:42 AM] [@o-lukas/homebridge-smartthings-tv] Child bridge process ended
[8/19/2024, 9:21:42 AM] [@o-lukas/homebridge-smartthings-tv] Process Ended. Code: 1, Signal: null
[8/19/2024, 9:21:49 AM] [@o-lukas/homebridge-smartthings-tv] Restarting Process...
[8/19/2024, 9:21:50 AM] [@o-lukas/homebridge-smartthings-tv] Launched child bridge with PID 24742
SyntaxError: Unexpected token 'with'
at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:118:18)
at callTranslator (node:internal/modules/esm/loader:273:14)
at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:278:30)
[8/19/2024, 9:21:50 AM] [@o-lukas/homebridge-smartthings-tv] Child bridge process ended
Environment Information
- Plugin Version:
- Homebridge Version: 1.8.4
- Node.js version: 20.9.0
- NPM version: <!-- npm -v -->
- Operating System: synology

Must be a problem with loading a JSON file. I changed something when updating eslint. I will have a look at it.
For now please go back to v2.1.3. Issue should be present since v2.2.0.

Broke it for me too. I came back down to 2.1.3 as well and now it says: MSmartThings Tv Bridgesmartthings-tvERRORError when getting devices: _a.at is not a function

Import assertion syntax I used was not yet supported by older versions of Node. So I went back to older syntax.
Hope everything works for you again with version v2.3.1


feat: added change-password request added in strapi v. 4.3.3

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other changes (could be a refactor, documentation change ect...)

Description

Resolves #141
Checklist:

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes (if not applicable, please state why)

missing 3 commits, need to figure out how to push from codespaces to other repo haha

Workflow is failing, see #144

Hey 👋🏼 Sorry for late reply, I've had some changes in my life that have taken me away from this package for a while.
Are you still up to end this PR? If so could you please rebase on develop branch pls 👼🏼

Hiya,
Sure, it's pretty much ready I think, just need to rerun the ci.
I'll check if everything still works when I get home. :)

@AnnikenYT Can you rebase this PR on develop as it is the default branch now and some changes has been made?

Changed the base to develop, but I don't have write access to this repo. You should be able to rebase it from here, no?


re-fix task NVIDIA drivers

Coming from discord
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

I have confirmed it too.

duplicated of https://github.com/iterative/cml/issues/1065#issuecomment-1157607462

Actually... won't TPI task need this?

@dacbd might want to add a basic test for new GPU models to https://github.com/iterative/cml-playground :)

Going to close this, I have now tested with Ampere, Turing, Volta, and Pascal architectures with no issues. The CML created instances where able to perform work and run nvidia-smi with no additional or special setup/considerations.


add v4l-utils rhel key

v4l-utils was missing a key for rhel so just adding it in as discussed over at this PR for the usb_cam package.
https://rpms.remirepo.net/rpmphp/zoom.php?rpm=v4l-utils

not sure why the nose-tests are failing....maybe v4l-utils should be v4l-devel for rhel instead?

so it looks like in the rosdep/base.yaml file v4l is listed twice? once for the libv4l-devel package and the other just for v4l-utils package. im guessing the devel one also includes the v4l-utils.

I pretty sure that v4l-utils is not packaged for RHEL 8 at the moment - at least not in any repositories that rosdep targets. It is packaged for RHEL 7, but that won't help you with usb_cam.
Here's the RHEL 7 package: http://mirror.centos.org/centos/7/os/x86_64/Packages/v4l-utils-0.9.5-4.el7.x86_64.rpm
libv4l-devel doesn't proved the same utilities that v4l-utils does, so that's not an appropriate package to satisfy this key.
So this is the only RHEL rule for v4l-utils that would be correct right now, and like I said, it won't help when Blooming usb_cam.
  rhel:
    '7': [v4l-utils]

@cottsay  ah that makes sense. so maybe ill just close this then, or do you think there would be any value with adding only the rhel 7 v4l-utils key?

@flynneva I guess this is your call, since it's your package that prompted you to add this. Do you want it? We can merge this if you still want it. Otherwise you can close it.

@mabelzhang I mean, sure? If it won't hurt anyone by merging I think it'd be good to at least show in rosdep what version of rhel is supported?
Not a high priority for me though honestly so if it's better just to wait until v4l is available for rhel 8 as well then that works too


replacement of "request.getRemoteHost()" by "WebUtils.getRemoteAddr()"

help our‘s web server behind the proxy server get the true client ip

@zhengyanbin Can you fix the comments please? We can add this PR into the next release.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Shiro-pr/164/Build result: FAILURE[...truncated 1.09 MB...][JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/core/target/shiro-core-1.3.3-SNAPSHOT-tests.jar to org.apache.shiro/shiro-core/1.3.3-SNAPSHOT/shiro-core-1.3.3-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/core/target/shiro-core-1.3.3-SNAPSHOT-javadoc.jar to org.apache.shiro/shiro-core/1.3.3-SNAPSHOT/shiro-core-1.3.3-SNAPSHOT-javadoc.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/core/target/shiro-core-1.3.3-SNAPSHOT-sources.jar to org.apache.shiro/shiro-core/1.3.3-SNAPSHOT/shiro-core-1.3.3-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/support/spring/pom.xml to org.apache.shiro/shiro-spring/1.3.3-SNAPSHOT/shiro-spring-1.3.3-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/support/spring/target/shiro-spring-1.3.3-SNAPSHOT.jar to org.apache.shiro/shiro-spring/1.3.3-SNAPSHOT/shiro-spring-1.3.3-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/support/spring/target/shiro-spring-1.3.3-SNAPSHOT-javadoc.jar to org.apache.shiro/shiro-spring/1.3.3-SNAPSHOT/shiro-spring-1.3.3-SNAPSHOT-javadoc.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/support/spring/target/shiro-spring-1.3.3-SNAPSHOT-sources.jar to org.apache.shiro/shiro-spring/1.3.3-SNAPSHOT/shiro-spring-1.3.3-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/pom.xml to org.apache.shiro/shiro-root/1.3.3-SNAPSHOT/shiro-root-1.3.3-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/target/shiro-root-1.3.3-SNAPSHOT-site.xml to org.apache.shiro/shiro-root/1.3.3-SNAPSHOT/shiro-root-1.3.3-SNAPSHOT-site.xml[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/support/guice/pom.xml to org.apache.shiro/shiro-guice/1.3.3-SNAPSHOT/shiro-guice-1.3.3-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/support/guice/target/shiro-guice-1.3.3-SNAPSHOT.jar to org.apache.shiro/shiro-guice/1.3.3-SNAPSHOT/shiro-guice-1.3.3-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/support/guice/target/shiro-guice-1.3.3-SNAPSHOT-javadoc.jar to org.apache.shiro/shiro-guice/1.3.3-SNAPSHOT/shiro-guice-1.3.3-SNAPSHOT-javadoc.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/support/guice/target/shiro-guice-1.3.3-SNAPSHOT-sources.jar to org.apache.shiro/shiro-guice/1.3.3-SNAPSHOT/shiro-guice-1.3.3-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/samples/aspectj/pom.xml to org.apache.shiro.samples/samples-aspectj/1.3.3-SNAPSHOT/samples-aspectj-1.3.3-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/samples/aspectj/target/samples-aspectj-1.3.3-SNAPSHOT.jar to org.apache.shiro.samples/samples-aspectj/1.3.3-SNAPSHOT/samples-aspectj-1.3.3-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/samples/aspectj/target/samples-aspectj-1.3.3-SNAPSHOT-javadoc.jar to org.apache.shiro.samples/samples-aspectj/1.3.3-SNAPSHOT/samples-aspectj-1.3.3-SNAPSHOT-javadoc.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/samples/aspectj/target/samples-aspectj-1.3.3-SNAPSHOT-sources.jar to org.apache.shiro.samples/samples-aspectj/1.3.3-SNAPSHOT/samples-aspectj-1.3.3-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/samples/quickstart-guice/pom.xml to org.apache.shiro.samples/samples-quickstart-guice/1.3.3-SNAPSHOT/samples-quickstart-guice-1.3.3-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/all/pom.xml to org.apache.shiro/shiro-all/1.3.3-SNAPSHOT/shiro-all-1.3.3-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/Shiro-pr/samples/spring-client/pom.xml to org.apache.shiro.samples/samples-spring-client/1.3.3-SNAPSHOT/samples-spring-client-1.3.3-SNAPSHOT.pomchannel stoppedSetting status of 984eac24edc66b9d1979f867dcd604bd63b0c798 to FAILURE with url https://builds.apache.org/job/Shiro-pr/164/ and message: 'FAILURE 'Using context: Jenkins: mvn clean install


Update socket.go

Thanks for your request. As a result of the file conflict, I have been directly modified.


Delete obsolete packages from appveyor feed

If somebody has the API key, can you please delete these two obsolete packages from the Appveyor feed? Should be something like this:
nuget delete FSharp.Compiler.Service.netcore 1.0.0 -ApiKey somekey -Source https://ci.appveyor.com/nuget/fsgit-fsharp-compiler-service

nuget delete FSharp.Compiler.Service.ProjectCracker.netcore 1.0.0 -ApiKey somekey -Source https://ci.appveyor.com/nuget/fsgit-fsharp-compiler-service

This is obsolete as the netcore was merged back into the main project, so I'm closing it.


The Syrian flag emoji needs to be updated

I suggest that Syrian flag needs to be updated to reflect current changes
Specifications of the Syrian independence flag:

Three horizontal stripes: green (top), white (middle), black (bottom)
Three red stars centered on white stripe
Standard flag proportions

How it would look like in Twemoji-styled flag (Edited using GIMP 2.10.38):

There is an issue #495 in the googlefonts/noto-emoji repository

Issue transfered to https://github.com/jdecked/twemoji/issues/119


pubs page

Until pubs page is ready can we redirect to Google Scholar?

@pfaendtner have you checked out the update-pubs branch and associated PR #17? The approach for continued updates is semi-automated for now.

I can’t even see any branches on the new version - is it there?!
/Users/jpfaendt/Research Group/UWPRG.github.iohttp://UWPRG.github.io
Jims-MBP-2:UWPRG.github.iohttp://UWPRG.github.io jpfaendt$ git branch -l

master

On Sep 5, 2018, at 4:42 PM, Josh Smith <notifications<EMAIL_ADDRESS>wrote:
@pfaendtnerhttps://github.com/pfaendtner have you checked out the update-pubs branch and associated PR #17https://github.com/UWPRG/UWPRG.github.io/pull/17? The approach for continued updates is semi-automated for now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/UWPRG/UWPRG.github.io/issues/23#issuecomment-418916042, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8sz3gLH1dwm6Rij6IdhoFOHHIoq_Dxks5uYGFIgaJpZM4Wbznr.

try: git branch --remote to see the branches.
git checkout update-pubs  should work if you have cloned the new repo

all good now

Addressed by #17


Iterate stargazers from both directions

For repos with lots of stars, we should be able to traverse all the stars in half as many GraphQL requests by iterating the stargazers simultaneously from the start and end.
Before:
repository(owner: "...", name: "...") {
  stargazers(after: "...", first: 100) {
    pageInfo {
      hasNextPage
      endCursor
    }
    edges {...}
  }
}

After:
repository(owner: "...", name: "...") {
  forward: stargazers(after: "...", first: 100) {
    pageInfo {
      hasNextPage
      endCursor
    }
    edges {...}
  }
  backward: stargazers(before: "...", last: 100) {
    pageInfo {
      hasPreviousPage
      startCursor
    }
    edges {...}
  }
}

I can take this one!
Here are some thoughts I have on how to approach this.
High Level
We're currently only iterating over stargazers starting from the beginning. If we go both directions in the same request, we should be able to do it in half as many requests as you say.
To do this, we would need to:

modify the GraphQL request in the query_repo fn to iterate forward and backward
modify the loop to use the current data (forward) and the new data (backward)

Random Notes

as you mentioned, we should probably find something with less than 10K stars (due to issue #1)
need to understand how exactly the current data is being used
may need to refactor or create a new struct to match the new shape of the data

Okay I forked and I'm going through the program line by line to understand how it works. Sharing for transparency. Once I have some actual questions, I'll add them here.
Opened up a Draft PR to show progress as I'm working on this. Right now, all it has are code comments as I understand how things work.
Don't feel obligated to answer anything yet - I'd rather put in the time and effort to understand things, then ask questions when I'm stuck.
https://github.com/dtolnay/star-history/pull/3

I've read through the code and have a decent understanding. I understand the problem now that I've laid it out a bit in this chart.

Next is figuring out the implementation.
Link to load this in Excalidraw

Based on my understanding, we'd like to iterate the stargazers simultaneously from the start and end. However, without any boundaries, we will go from first 100 to the end and last 100 to the beginning. This would cause 2x the overlap.

How do we prevent data fetching overlap?
In the ideal world, we would fetch from the first 100 to the middle and last 100 to the middle. How can we do this though? Based on the query arguments, I'm not sure how we might achieve this.
The only thing that comes to mind is comparing the starredAt dates for the last node on the forward and backward stargazers.
example

Grab the last node in forward.edges and backward.edges
Compare the starredAt property
If the forward.edge.starredAt is > backward.edge.starredAt, then there is overlap and we can stop.

@dtolnay thoughts?

Comparing by starredAt time seems good to me. Some notes:

It's possible you'll need to add orderBy to the stargazers query to get them back in guaranteed timestamp order.
Some popular repos can have hundreds of stars with the same timestamp, so observing an equal timestamp from the two directions isn't a sufficient stopping condition, the timestamps need to  pass each other.

Benchmarking
Before any work is done, I did some lightweight benchmarking using this suggestion.
// Starting with where the program begins
fn try_main() -> Result<()> {
    let start = PreciseTime::now();
    // ...logic
    let end = PreciseTime::now();
    println!("{} seconds for whatever you did.", start.to(end));
    // and ending right before the program ends
    Ok(())
}

Results
For this test, I used the project dtolnay/cxx and run the project locally 10 times using cargo run dtolnay/cxx. At the time, this project had 1.1k stars.

iteration
time (seconds)

1
6.100639575

2
6.378565638

3
4.614419264

4
3.981658091

5
3.806677116

6
3.710274895

7
4.493894649

8
3.630218908

9
3.526228069

10
3.460886556

Fastest: 3.460886556
Slowest: 6.378565638
Average: 4.370346276

Made a little bit of progress today. Through in some println statements to better understand what the structs look like with data in them.

Next I need to better grasp how cursor is used because that will change with the new query


Connection lost when bitcoind restarts

Probably because the cookie changed.
bwt can maybe try rereading the cookie if auth fail.

Related: https://github.com/chris-belcher/electrum-personal-server/commit/dce6bff4768756c4ac2b0856d29ff9fe08348a15 and https://github.com/chris-belcher/electrum-personal-server/issues/39.


Update walkdown algorithm for selecting codes for display tables

As we get more and more custom codes to check for in display table builders, it may be helpful to do some database inspection before building queries. something like 'Check if a code is found, if so, then grab that data, and try to get a filtered dataset for checking the next code'. This might help with performance/query bloat.

Resolved via #196


Compilation error when compress conditionals is true

See repo: https://github.com/danbopes/webpack-uglify-react-form-issue
Trying to diagnose an error. When compress conditionals is false, webpack compiles and runs correctly. When compress conditionals is true or mangle is false, webpack compiles but shows the following error:

The cause of the error appears to be this line in the minified dist of react-form:
    e.exports = require("babel-runtime/helpers/extends")

Additional information located in the react-form issue here, but I believe this issue is internal to uglifyjs, and nothing in react-form.

Reproduce via repository here: https://github.com/danbopes/webpack-uglify-react-form-issue
Compile with:
$ yarn
$ webpack -p

<EMAIL_ADDRESS>is not compatible with the -p flag of<EMAIL_ADDRESS>The -p flag of<EMAIL_ADDRESS>will use<EMAIL_ADDRESS>unconditionally.
For<EMAIL_ADDRESS>on UNIX use this instead:
webpack --config webpack.config.js --define process.env.NODE_ENV='"production"'

On Windows the quoting may be different. I don't know.

@danbopes See @kzc comment @kzc Thx :) Feel free to reopen if still regressions

I confirmed the repro worked with the command above. It would have been helpful if the code actually displayed something. :-)
diff --git a/src/index.jsx b/src/index.jsx
index 5fe1742..ebcdea6 100644
--- a/src/index.jsx
+++ b/src/index.jsx
@@ -4,9 +4,10 @@ import { Form, Text } from 'react-form';

 const app = () => (
     <div>
+      Hello dude.
     </div>
 );

 const root = document.getElementById('root');

I thought it had It works!. Anyways, thanks for the assistance.
Would be helpful if the documentation reflected the '-p' flag.
On Dec 4, 2017 8:05 PM, "kzc"<EMAIL_ADDRESS>wrote:

I confirmed the repro worked with the command above. It would have been
helpful if the code actually displayed something. :-)
diff --git a/src/index.jsx b/src/index.jsx
index 5fe1742..ebcdea6 100644--- a/src/index.jsx+++ b/src/index.jsx@@ -4,9 +4,10 @@ import { Form, Text } from 'react-form';
const app = () => (
+      Hello dude.

);
const root = document.getElementById('root');
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/webpack-contrib/uglifyjs-webpack-plugin/issues/179#issuecomment-349160789,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEYJEEFA93ZWE-NZfsStIGPxcsFSYTIgks5s9JbUgaJpZM4Qygmx
.


Bolierplate code not working on new React project

I was testing out react-resizable-panels on my project and couldn't get the resizable panels to show.  I thought it could be to do with some dependencies I had installed but then just tried it again on a brand new react project:

npx create-react-app .
yarn install
yarn add react-resizable-panels
add code found here: https://react-resizable-panels.vercel.app/examples/horizontal
yarn start
result:

The html is not rendering the same html as the demo examples:

From what I can tell, the "code" is working. You just haven't added any styling to your panels.
This library doesn't provide a default visual style for panels because that's a huge problem space. It just provides the functionality of resizing. If you want to copy the visual styles from the demo website though, you can find them here
https://github.com/bvaughn/react-resizable-panels/blob/main/packages/react-resizable-panels-website/src/routes/examples/shared.module.css


Step 15: Run the notebook - Python code issue

Step 15:
This line:
workspacepath removes the extension, so now add it back.
fullworkspacepath = workspacepath + '/' + name + file_extension

I found when calling the API to run a job, it needs the notebook name (fullworkspacepath) to not include the extension otherwise it cannot find the notebook.
The same steps shown here:
https://docs.databricks.com/dev-tools/ci-cd/ci-cd-jenkins.html
use the line as just:
ullworkspacepath = workspacepath + '/' + name

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

ID: 56b86f59-7a22-90c6-9aa6-652b85975612
Version Independent ID: b333ab7b-847b-7129-9b62-4b9b934747d7
Content: Continuous integration and delivery on Azure Databricks using Azure DevOps - Azure Databricks
Content Source: databricks/dev-tools/ci-cd/ci-cd-azure-devops.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

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

@mssaperla
Could you please review add comments on this, update as appropriate.

@cholmes90s
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.

@cholmes90s
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Fixes require Backporting to rel/6.2 (at least)

The following PRs were merged into master, but should have been merged into rel/6.2:

#189
#211

Closing, as we re-created the rel/6.2 branches on top of master. (Thanks to @RachedBenMustapha  for the simpler suggestion given the current state of the project)


Fix code signing with Xcode 8

Automatic provisioning is enabled for the targets that require signing (frameworks, tests, and test host). Signing is explicitly disabled on OS X as it is not necessary for our purposes.
Both of Xcode 8's approaches to provisioning appear to require hard-coding a development team identifier in the project file. This will likely prevent people outside of Realm from building from source using Xcode 8 without first changing the team used for code signing for each target via Xcode's target editor. Hopefully this situation is improved before Xcode 8 GMs.
These changes have no effect on Xcode 7's behavior.

👍 , per our conversation.

Do we know how CocoaPods/Carthage are dealing with this?

CocoaPods is dealing with this by disabling signing. That works for their purposes as they're only concerned with building frameworks, and they can defer the signing of those frameworks to when they're copied into the user's app bundle.


offline use

What problem does this feature solve?
With the new vue-cli, can I create projects offline?
I say this because we do not all have the internet of the rich countries, and it would be a pity not to be able to use it vue-cli for living in Cuba for example.
What does the proposed API look like?
I propose that you can create projects by installing vue-cli, but that when creating a vue proyect you do not have to connect to the internet

Unfortunately this is not possible because you'd have to install npm dependencies... there's no way around that. The alternative is install @vue/cli-service-global once and then use vue serve and vue build while offline.

This could be achieved by passing the parameter --prefer-offline to yarn (when using it as package manager) so that dependencies can be installed from cache and you dont have to wait for network timeouts.

@yyx990803 i got a problem when i yarn serve/npm run serve without connection , after a longtime developing same project, if i turn the wifi on it's work well turn it off again doesn't work !!!???


artisan package:discover causing symfony errors.

Package discover is throwing errors for me when I have sentry-laravel in place.
I uninstalled it, and it works just fine, re-installing fails due to package:discover.
Here is the result (formatter is Collision, without it, I get even less info):
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

   Symfony\Component\OptionsResolver\Exception\UndefinedOptionsException

  The option "enabled" does not exist. Defined options are: "attach_stacktrace", "before_breadcrumb", "before_send", "capture_silenced_errors", "class_serializers", "context_lines", "default_integrations", "dsn", "enable_compression", "environment", "error_types", "excluded_exceptions", "http_proxy", "in_app_exclude", "in_app_include", "integrations", "logger", "max_breadcrumbs", "max_request_body_size", "max_value_length", "prefixes", "project_root", "release", "sample_rate", "send_attempts", "send_default_pii", "server_name", "tags".

  at vendor/symfony/options-resolver/OptionsResolver.php:798
    794|         if (\count($diff) > 0) {
    795|             ksort($clone->defined);
    796|             ksort($diff);
    797|
  > 798|             throw new UndefinedOptionsException(sprintf((\count($diff) > 1 ? 'The options "%s" do not exist.' : 'The option "%s" does not exist.').' Defined options are: "%s".', $this->formatOptions(array_keys($diff)), implode('", "', array_keys($clone->defined))));
    799|         }
    800|
    801|         // Override options set by the user
    802|         foreach ($options as $option => $value) {

      +23 vendor frames
  24  [internal]:0
      Illuminate\Foundation\Application::Illuminate\Foundation\{closure}(Object(Sentry\Laravel\ServiceProvider))

      +5 vendor frames
  30  artisan:37
      Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

Installation failed, reverting ./composer.json to its original content.

I have to stop using Sentry if this is the case.

You should remove the enabled option in config/sentry.php.
Any custom options you might have in there have to be removed because Sentry validates that the options in config/sentry.php are the correct ones and enabled is not one of them.

Ahhhh, that's interesting. Alrighty, good to know.
You may close this now then.


feature: Prospective study information menu

Feature Request
Describe the Feature Request

On Prospectyve study menu panel, the information is the one related to Feature set. Change information panel to Prospectyve information:
This is where you make predictions for future.
Select an existing model, provide patient data and see predictions of FAIR4Health,
Check the accuracy of predictions later.
Is your feature request related to a problem? Please describe

Describe Preferred Solution

Additional Context

It is done on PR


Attempt to expand macros before processing conditions

Fixes #391.
RELEASE NOTES BEGIN
specfile now tries to expand macros before processing conditions to be able to resolve conditional expressions defined by macros, for example OpenSUSE Tumbleweed defines %ifpython3 macro as %if "%{python_flavor}" == "python3".
RELEASE NOTES END

/packit rebuild-failed


refactor(contracts): Standardize WZETA contract version

In order to unify the contract versions, so that external projects can make the code more concise when relying on the contract of the project, the version of the WZETA.sol contract was changed to use the 0.8.7 version syntax.
Relevant issue: #128

We actually have WZETA in protocol contracts. Ideally, we don't have duplicate versions of the same contract.
@andresaiello would it be possible to update WZETA in protocol contracts to 0.8.7?

We actually have WZETA in protocol contracts. Ideally, we don't have duplicate versions of the same contract.
@andresaiello would it be possible to update WZETA in protocol contracts to 0.8.7?

the reason why we use that version on protocol is to have the same bytecode as ethereum WETH. it's some kind of guarantee. But I'm pro having an updated version on examples and other stuff


Feature Request:ScreenShot

Please Describe The Feature To Be Added
Integration of ScreenShoting
Suggest A Solution
https://pub.dev/packages/screenshot

I think you made a typo here ;)

Yeah, what package is that?

let me check all the posts once again.... 😅

I hope to have such a similar feature
How to get a control ui image?
I want to implement such a report for printing function, but I don't want to use MatplotlibChart and PlotlyChart,
Although MatplotlibChart and PlotlyChart can do this, flush control cannot be used inside them

I hope to have such a similar feature
How to get a control ui image?
I want to implement such a report for printing function, but I don't want to use MatplotlibChart and PlotlyChart,
Although MatplotlibChart and PlotlyChart can do this, flush control cannot be used inside them

Closing in favor of https://github.com/flet-dev/flet/issues/317


Add link caching using SQLite

This PR adds link caching using a local SQLite file, .mdoxcache which is suitable for GitHub Actions. It introduces the following:
Adds following fields to links.validate.config:

cacheType:  Specifies type of cache. Can be set to 'SQLite' or 'None'. 'SQLite' creates a database in .mdoxcache. 'None' or setting it to empty will ensure no .mdoxcache file is created. Will throw error if set to anything else.
cacheValidity which specifies duration till which link in the cache database is valid. Default is 120h or 5 days.

Also adds following flag in case cache needs to be cleared but there is no filesystem access:

--cache.clear which instructs mdox to drop the entire cache database and start afresh.

#TODO(bwplotka): Uncomment once we upstream merrors package: @/tmp/.bin/faillint-v1.5.0 -paths "errors=github.com/pkg/errors" ./...
Error: /home/runner/work/mdox/mdox/pkg/mdformatter/linktransformer/link_test.go:225:50: too few arguments in call to MustNewValidator
faillint: error during loading

🤔 Hmmm, let me check today/Monday

Let's try rebasing, maybe there is some old dep? (:

Yup! Rebasing fixed this!

I'm wondering what's status of this PR? It was looking good enough for merging for me but I'm wondering if @bwplotka had a chance to look at the latest state as well? cc @saswatamcode

I didn't get a chance to look through the dbHandle flow that was mentioned in the last review. 😅
I think this is in a mergeable state once @bwplotka has had a look and we can iterate on this (will possibly need to once we use it in a repo and come across some new issues anyway), @matej-g ! 🙂

Still to be addressed I believe (:

Any chance of progress? Before this PR celebrates it's 1st birthday in a week :birthday: :joy:

Oh no! Yup, let me get to it soon, it's been on my backlog for a long time now! 🙈

@bwplotka @matej-g I've addressed most of the feedback here. But yes, there are some code smells due to cache, that I think arise from not having a dedicated Cache interface. We try to support multiple CacheTypes here but use only the sqlite Storage struct, which makes it a bit confusing.
Let's get this merged, I will refactor this in another PR, without changing configuration semantics. 🙂


[DEVOPS - BUG] Storyblok doesn't trigger deployment and post to discourse

Steps to reproduce

Publish a new story on storyblok with the (post to discourse toggle enabled)

Expected:

Story is posted to discourse
deploy hook is triggered in vercel to deploy palomachain.com
logs are posted to storyblok_log.txt

Actual:
Nothing happens, no entry in the logs and no service journal output

Some additional notes:
Repo: https://github.com/VolumeFi/paloma-storyblokupdates
Server: bots-server
the last successful post was on July 16, the day before the cutover to namecheap. The sb.palomachain.com domain was added to namecheap today, but it is unclear if that is needed. It is listed as the webhook url in storyblok, but according to the logs this webhook has been failing for a long time (before July 16)
~app/paloma-storyblokupdates/storyblok_log.txt has the last entry from March 28. This is not a blocker and probably unrelated, but this log was helpful in the past.
storyblok API returns the stories when queried manually - tokens in the .env file are correct
vercel tokens in the .env file are correct
the last story in stories.txt is the one from July 16

worked again today. potentially the missing domain did the trick


Enables pagination for Saves & Follows views

Fixes: https://github.com/artsy/collector-experience/issues/729
Skip new tests

Fails

:no_entry_sign:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artists/__tests__/index-tests.tsx
src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Favorites/Components/Categories/__tests__/index-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Warnings

:warning:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artists/__tests__/index-tests.tsx
src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Favorites/Components/Categories/__tests__/index-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Warnings

:warning:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artists/__tests__/index-tests.tsx
src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Favorites/Components/Categories/__tests__/index-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Warnings

:warning:

Missing Test Files:

src/lib/Scenes/Favorites/Components/Artists/__tests__/index-tests.tsx
src/lib/Scenes/Favorites/Components/Artworks/__tests__/index-tests.tsx
src/lib/Scenes/Favorites/Components/Categories/__tests__/index-tests.tsx
src/lib/Scenes/Favorites/__tests__/index-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS


samples: net: zperf: Remove config files for Galileo board

The support for Galileo board is bitrotted as the config file
contains obsolete values. As testing this old board is difficult
lets remove the config files. These can be re-introduced with
proper and tested settings if needed.
Fixes #7814
Signed-off-by: Jukka Rissanen<EMAIL_ADDRESS>

Codecov Report

Merging #7843 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7843   +/-   ##
=======================================
  Coverage   55.02%   55.02%
=======================================
  Files         483      483
  Lines       53968    53968
  Branches    10501    10501
=======================================
  Hits        29694    29694
  Misses      19986    19986
  Partials     4288     4288

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 e9174c6...e367070. Read the comment docs.


change ember build output path

Make it so that from within the docker container, simply running ember build will replace the current script: ember build --output-path /opt/edctf/edctf/static/ember

I went ahead and did this

Closing per @x64x6a


feat(wip): removed signer from viewMethods by dropping NAJ account.ViewFunction

In this PR, I remove account.ViewFunction to drop dependency on using a Signer for view methods. We instead use the providers from near-api-js to write a utility method for viewFunction.

Description

Type of change

[x ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] 🏗 Build configuration (CI configuration, scaffolding etc.)
[ ] 🐛 Bug fix (non-breaking change which fixes an issue)
[x ] 📝 Documentation update(s)
[ ] 📦 Dependency update(s)
[ ] 👩🏽💻 Improve developer experience
[ ] ⚡ Improve performance
[x ] ✨ New feature (non-breaking change which adds functionality)
[x ] ♻ Refactor
[ ] ⏪ Revert changes
[ x] 🧪 New tests or updates to existing tests

:tada: This PR is included in version 1.1.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

@race-of-sloths

@jaswinder6991 Thank you for your contribution! Your pull request is now a part of the Race of Sloths!
New Sloth joined the Race! Welcome!

Current status: waiting for scoring
We're waiting for maintainer to score this pull request with @race-of-sloths score [0,1,2,3,5,8,13] command
What is the Race of Sloths

Race of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow
For contributors:

Tag @race-of-sloths inside your pull requests
Wait for the maintainer to review and score your pull request
Check out your position in the Leaderboard
Keep weekly and monthly streaks to reach higher positions
Boast your contributions with a dynamic picture of your Profile

For maintainers:

Score pull requests that participate in the Race of Sloths
Engage contributors with fair scoring and fast responses so they keep their streaks
Promote the Race to the point where the Race starts promoting you
Grow the community of your contributors

Feel free to check our website for additional details!

Bot commands

For contributors

Include a PR: @race-of-sloths include to enter the Race with your PR

For maintainers:

Assign points: @race-of-sloths score [1/2/3/5/8/13] to award points based on your assessment.
Reject this PR: @race-of-sloths exclude to send this PR back to the drawing board.
Exclude repo: @race-of-sloths pause to stop bot activity in this repo until @race-of-sloths unpause command is called

✅ PR is finalized!
Your contribution is much appreciated with a final score of 0!
You have received 10 (0 base + 10 weekly bonus) Sloth points for this contribution
Another weekly streak completed, well done @jaswinder6991! To keep your weekly streak and get another bonus make pull request next week! Looking forward to see you in race-of-sloths


command line output in cp866

Does atom work in general with those characters?

yes. problem only with parsing cyrillic characters from windows command line.
executeShell("chcp 65001"); - It solves the problem of the output these characters from the code, but the error output is still in the cp866

Do CP866 work if you input them into an atom TextEditor?

i dont know. I am working with utf-8 in code. only windows cmd output in cp866 by default.
screenshot...

copy characters from cmd to atom
atom parse characters from cmd
visual cmd output

atom-build output in utf-8? maybe choose output encoding in atom-build (utf-8 or cp866)

Hmm. So I guess the problem originates from here: https://github.com/noseglid/atom-build/blob/master/lib/build-view.js#L235
Since the output really is not UTF-8.
I did some quick googling and found another issue on node. Do any of those work-around help you?

ok thank you

it is not a is not the way.
maybe something like "cmd" : "chcp 65001 | D:\Dropbox\dmd2\windows\bin\dmd.exe" in .atom-build.json

Yes. Some way to get the output into utf8 is probably the best solution. build just assumes it is UTF-8 since there is no way to detect it from the executed command alone.


Feature: Active records

In this PR, I worked on the following features:

Add migrations
Create models and add validation
Add devise for authentication
Update layout

Approved ✅✅✅


Chained Pipelines not Triggering Properly

I'm having and issue with pipeline not being triggered by certain commits. Here's my setup, i have four repos connected like so:
C <-- B <-- A
^
|
| ------ D
Here's my order of events with what I expected to happen:

create repo A
create repo D
commit to repo A
commit to repo D
create pipeline connecting B to A
create pipeline connecting C to B and D
one job get triggered for C (once B and D both have data) and C sees data in both B and D

Here's what I actually see (note difference in last step)

create repo A
create repo D
commit to repo A
commit to repo D
create pipeline connecting B to A
create pipeline connecting C to B and D
one job get triggered for C (once B and D both have data) and C sees data in D, but C doesn't see and data in B

When I try creating the pipelines before making the initial commits the job between A and B gets triggered, but the job to from B and D to C doesn't get triggered.
I've looked at the environment variables pachyderm generates and PACH_D_COMMIT_ID is a commit id but PACH_B_COMMIT_ID is an empty string.
If I take repo A out the equation, then C sees data from both B and D as expected
Here's what my pipeline spec looks like:
{
  "pipeline": {
    "name": "B"
  },
  "transform": {
    "image": "custom_image",
    "cmd": [ "/usr/bin/R", "--vanilla"],
    "stdin": [
       CODE]
  },
  "parallelism": 1,
  "inputs": [
    {
      "repo": {
        "name": "A"
      },
      "method": {
        "partition": "file",
        "incremental": "DIFF"
      }
    }
  ]
}
{
  "pipeline": {
    "name": "C"
  },
  "transform": {
    "image": "custom_image",
    "cmd": [ "/usr/bin/R", "--vanilla"],
    "stdin": [
       CODE]
  },
  "parallelism": 1,
  "inputs": [
    {
      "repo": {
        "name": "B"
      },
      "method": {
        "partition": "file",
        "incremental": "DIFF"
      }
    },
    {
      "repo": {
        "name": "D"
      },
      "method": {
        "partition": "block",
        "incremental": "DIFF"
      }
    }
  ]
}

I've tried this on 1.1.0-ba43f31be2be7e013f1373eac6581f9093f37f48 of pachctl and pachd as well as version 1.1.0 and have seen the same results.
I've been struggling with this for a couple of days and have had to reinstall a couple of different of versions of pachyderm to confirm what i'm seeing. I can run the fruitstand example fine, so its not like all chained commits are causing the problem. Does anyone know what the issue could be? Am I missing something obvious?

As some additional info, when my job for repo C runs and it tries to copy the file it expects in repo B, i'm seeing the following error:
ERROR fuse.DirectoryLookup {"directory":{"file":{"commit":{"repo":{}}}},"name":"B","err":"operation not permitted"}

Hi @alexsbromberg, sorry you ran into this. Definitely doesn't sound like the behavior I'd expect either. Would you mind gathering a bit more information for me about which jobs run? You can do this with: pachctl list-job which will show you all the jobs that have run. Then for each of those do pachctl inspect-job <job-id> which will give extended information about the jobs and what they're running on.

Here's the output from pachctl list-job
ID                                 OUTPUT                                               STARTED             DURATION            STATE
5d51743c6f52cf4e18257a26aa7e8984   C/e68bffd9ed71483f9949ab5841ba1ede   10 seconds ago      3 seconds           success
055ba2f24ca92c1d56b110772039fdbc   B/6de392756ce04674a79b4b492164e434        20 seconds ago      9 seconds           success

From pachctl inspect-job 5d51743c6f52cf4e18257a26aa7e8984
ID: 5d51743c6f52cf4e18257a26aa7e8984
Started: 53 seconds ago
Duration: 3 seconds
State: success
Parallelism: 1
Inputs:
NAME                 COMMIT                             PARTITION           INCREMENTAL
D   46d854308eab498abeec4d61321e0e1c   BLOCK               %!t(pps.Incremental=1)
Transform:
{
  "image": "custom_image",
  "cmd": [
    "/usr/bin/R",
    "--vanilla"
  ],
 "stdin": [
  <code truncated>
 ]
}

From pachctl inspect-job 055ba2f24ca92c1d56b110772039fdbc
ID: 055ba2f24ca92c1d56b110772039fdbc
Started: 3 minutes ago
Duration: 9 seconds
State: success
Parallelism: 1
Inputs:
NAME                COMMIT                             PARTITION           INCREMENTAL
A          f82b0531fac84cdc9159a5a2bc64f3f1   FILE                %!t(pps.Incremental=1)
Transform:
{
  "image": "custom_image",
  "cmd": [
    "/usr/bin/R",
    "--vanilla"
  ],
  "stdin": [
    <code truncated>
  ]
}

Thanks for that, was able to reproduce your issue with a test here: https://github.com/pachyderm/pachyderm/pull/805. Will take a crack at fixing the issue tomorrow.

Just tried reproducing on the pfs-refactor branch. It still fails but differently than on the the previous pfs. Rather than triggering a job that can only see data from 1 repo it doesn't trigger a job at all.
@derekchiang could you try running the test on the pfs refactor branch when you get a chance and see if you can understand the behavior?

Fixed in the refactor branch.  Will keep the issue open until we merge.

:rocket:! What was the issue?


HIVE-27288 : Backport of HIVE-23262 : Remove dependency on activemq

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

@vihangk1 Can you please approve and merge this


Choice's title can't contain inline conditions or alternatives

Plain text and variables only.

The official documentation talks escaping a whitespace \  before { in order to allow for alternatives.
That would also allow to set choice titles through variables (which would be great as I haven't found an alternative way to achieve that) like so: * \ {textVariable} or even * {condition} \ {textVariable}

Sounds lika an option, didn't know about the official solution before.

So the narrator doesn't have a way to use vars in the choice title? Hm, not good.
For some reason I used to think it was present. Now it's part of this ticket, definitely.


Soft labels

The correctness (or concordance with the equations in your paper) of the one_side_w (and also asymmetric_w below) relies on the fact that your labels (or targets y) are hard labels (0 or 1). However, when one uses soft labels (using label smoothing), the concordance would fail.
I think the following code works for both hard labels (identical) and soft labels (not considering efficiency)
    def forward(self, x, y):
        """"
        Parameters
        ----------
        x: input logits
        y: targets (multi-label binarized vector)
        """

        # Calculating Probabilities
        x_sigmoid = torch.sigmoid(x)
        xs_pos = x_sigmoid
        xs_neg = 1 - x_sigmoid

        # Asymmetric Clipping
        if self.clip is not None and self.clip > 0:
            xs_neg = (xs_neg + self.clip).clamp(max=1)

        # Basic CE calculation
        los_pos = y*torch.log(xs_pos.clamp(min=self.eps))
        los_neg = (1-y)*torch.log(xs_neg.clamp(min=self.eps))
        # loss = los_pos + los_neg

        # Asymmetric Focusing
        if self.gamma_neg > 0 or self.gamma_pos > 0:
            if self.disable_torch_grad_focal_loss:
                prev = torch.is_grad_enabled()
                torch.set_grad_enabled(False)
            los_pos *= torch.pow(1-xs_pos, self.gamma_pos)
            los_neg *= torch.pow(xs_pos, self.gamma_neg)
            if self.disable_torch_grad_focal_loss:
                torch.set_grad_enabled(prev)
        loss = los_pos + los_neg

        return -loss.sum()

@wenh06 Thanks for the comment. Indeed, in this work, we basically assumed hard labels.

@wenh06 Thanks for the comment. Indeed, in this work, we basically assumed hard labels.

OK, thank you!


better use for generators, file handlers, and iterators

for wsgi and large files, it would be cool to be able to just return an open file handler or a generator or iterator and wsgi will iterate through it correctly and return it.
I'd like to see this work:
class Foo(Controller):
  def GET(self):
    fp = open("/some/path.ext", 'rb')
    return fp

I'd also love to see support for this working:
class Foo(Controller):
  def GET(self):
    for x in range(100):
      yield x

This would involve modifying the simple server to work similar to uwsgi also, where yield doesn't finish the request like it currently does, I'm cool with that though since we removed Mongrel2 support. This would allow us to get rid of all that hacky generator code also which would simplify Call quite a bit

the file pointer portion of this is implemented as of 1.0.27, still need to add generator support


Corrections to subsetting lecture and lab

https://github.com/jhudsl/intro_to_R_class/issues/89

hmm I don't see the = assignments... maybe this was out-of-date or maybe I just missed them but I will move more questions to bonus

done!


Getting an Error while I call  method "scrape"

line 14, in
google_reel.scrape(headers=headers)
File "/opt/virtualenvs/python3/lib/python3.8/site-packages/instascrape/scrapers/post.py", line 88, in scrape
return_instance.upload_date = datetime.datetime.fromtimestamp(return_instance.timestamp)
ValueError: Invalid value NaN (not a number)
I am getting this error every time i am calling scrape method regardless of  its type on what i am calling it for example it is coming on anything like posts, profile, IGTV, reel.
The whole code is this:
from instascrape import Reel
SESSIONID = "Session_id"
headers = {
"User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.74 Safari/537.36 Edg/79.0.309.43",
"cookie":f'sessionid={SESSIONID};'
}
google_reel=Reel(link)
google_reel.scrape(headers=headers)
google_reel.download(fp=f"video.mp4")

I am also facing the same issue

same, help please


AuditLogEventType 144/145 missing

Library Version
5.0.1
Describe the Bug
Two audit log event types are missing:
144 - flagged a message
145 - timed out a member

Steps to Reproduce
Set up an automod role and tick all options (block message, send alert, time out member) and let someone trigger this role.
Expected Results
That the two events are integrated
Minimal Reproducible Code
No response
Traceback
No response
Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.
[X] I have attempted to debug this myself, and I believe this issue is with the library

Additional Information
No response

Thanks for reporting! This has been resolved in V5.1.0 which is due for release within the next week.
In the meantime, don't worry about that warning; the library will create a temporary enum entry for any unknown values. That way you won't miss any events


export: Added "promtest" framework allowing tests against GCM and Prometheus; Added counter test.

This PR:

Adds pkg/export/gcm/promtest pkg that contains "IngestionTest" framework.
(The only change to export pkg) pkg/export: Adding a config option that allows passing credentials content instead of files.
Adds pkg/export/gcm/export_gcm_test.go that implements a simple counter test that showcases the framework use.

This uses docker the e2e framework I maintain with some Thanos maintainers for Prometheus test and local export code for "GMP" test. The "local export" is so we can use local debugger and test EVERY export change in this repo.
Tests with Prometheus enabled, takes N samples * 5 seconds. We could take scrape interval to 1s, but it might kill our CI CPU. We can also disable Prometheus tests for CI and run it only locally.
Those tests will also NOT run for contributors as it requires secret.
In future PRs we can:

Move to Cloud build for stronger security guarantees for our test SA.
Add test for new logic for resets.
Add GMP + GCM test (docker container too)
Add tests for other types, different queries (e.g. rates) etc - sky is the limit.

Tests passed without mention about skipping anything, but I see it ran within 3s which is not realistic so assuming it was skipped - investigating.

All should work, PTAL @TheSpiritXIII @pintohutch

Address all comments so far @TheSpiritXIII  (:

@bwplotka I'm going to approve. Only nit is the Println. Please address and then you can merge. 🙂👍

This is great! We'd love a demo walkthrough of the e2e package at some point 😄
In general, this PR was a little intimidating in size. Can we try to put up smaller diffs for review?
WDYT about daisy-chaining baby PRs so we don't hinder development while lowering the review burden?

Thanks @TheSpiritXIII for review and @pintohutch for feedback.
This could be split a bit yea (e.g I could split local export AND e2e Prometheus into two), let's try that next time! The beauty of one atomic PR is that reviewer understands clearly why this complexity and e2e dependency is needed. There is also question PR author time, given chaining PRs in on GitHub is non trivial - definitely it would be good idea to document how we want to do it as a team 🤗


FileNotFoundError

Thank you very very much for your work. It was the first repository for Spotify to Tonie Sync i got running and had no further problems.
Small issue with file names that have special characters in the name.
Probably because of the artist name with the dot in the name.
2024-04-01 05:30:07,900 | [Errno 2] No such file or directory: '/app/data/download/Josh. - Cordula Grün.mp3'
Traceback (most recent call last):
  File "/app/spoonie.py", line 449, in main
    tonie_api.upload_file_to_tonie(creative_tonie,value,key)
  File "/usr/local/lib/python3.12/site-packages/tonie_api/api.py", line 129, in upload_file_to_tonie
    with file.open("rb") as _fs:
         ^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/pathlib.py", line 1013, in open
    return io.open(self, mode, buffering, encoding, errors, newline)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/app/data/download/Josh. - Cordula Grün.mp3'

Hi, today i had some time to look at the code. I cannot reproduce the issue (tested on windows and linux ). Maybe i fixed it 'accidentally' while fixing the other things. can you test it again with the latest version?


Replace coroutines with iterators

Let's avoid using coroutines in Penlight for iterators, and use closures instead. Coroutines in Lua do not compose well at a library level, so they are better left to the application who controls the main loop to own and manage. (An exception to this rule of thumb is libraries which are the main loop, such as Copas.)
For more background on this general issue of coroutine composability, see for example:

https://github.com/mascarenhas/taggedcoro
https://github.com/saucisson/lua-coronest

This PR also drop OpenResty hacks from Penlight.

Thanks for this. I actually banged my head against this just last night and went to bed without figuring out what was going screwy. In light of this I poked at the same problem today and this solves it. I'm still kind of foggy on why, but my app using coroutines does seem related.
One question though: might it be useful to keep the OpenResty compatibility shim: not for use in Penlight itself but to provide to apps?

I'll buy that, thanks.


Runtimes slow down dramatically proportionally with feature file size

We maintain a large collection of feature files that feed nightly regression tests, the runtime of which has grown significantly recently. These are generally maintained in logically separated feature files, and leverage Scenario Outline tables, sometimes with 100-200 scenarios per feature file.
In experimenting with optimizations on a single tag, I tried splitting a feature file into 4 and observed a massive performance gain. Here is my baseline:
[Summary]
1 feature
257 scenarios (226 passed, 31 failed)
1663 steps (1632 passed, 31 failed)
Tests completed in 266 sec

Here are the same exact tests divided over 4 feature files:
[Summary]
4 features
257 scenarios (226 passed, 31 failed)
1663 steps (1632 passed, 31 failed)
Tests completed in 99 sec

For reference,  here is how we're running (note that local_test_jobs keeps Bazel from trying to do its own parallelism, instead delegating the concurrency to the cucumber engine):
$ bazel run //my-crate:my-test-suite \
    --local_test_jobs=1 -- \
    --concurrency 16 \
    --tags="@my-cool-tag"

Several questions I have after observing this major performance difference:

How is concurrency actually affecting the runtime? I was under the impression concurrency was at the scenario level, but now I'm wondering whether it's actually at the feature level
Is there any guidance you can give on tuning concurrency to the number of feature files?
Is there any further guidance on how tests should be broken up to get the best performance out of the cucumber-rs engine?

@tgsmith61591

How is concurrency actually affecting the runtime? I was under the impression concurrency was at the scenario level, but now I'm wondering whether it's actually at the feature level

concurrency is the maximum number of scenarios running concurrently (in async manner).

Is there any guidance you can give on tuning concurrency to the number of feature files?
Is there any further guidance on how tests should be broken up to get the best performance out of the cucumber-rs engine?

Actually, you shouldn't. The behavior you observe, that splitting source files leads to a significant performance gain, seems to be buggy, weird and unexpected. There shouldn't be any significant difference. Should be investigated and fixed.
The idea we have in mind for now is that a Parser returns a Stream of features being consumed by a Runner, executing them concurrently on scenario level. Seems like the current Runner implementation breaks up those features into scenarios in some weird manner, affecting the performance.

@ilslv do you have any suggestions on this?

@tgsmith61591 can you share a little bit more about the characteristics of the testing suite? Is it async or sync heavy, or maybe appropriately both? Can you share the World setup: number of concurrency and other options?

Hey @ilslv and @tyranron, the test suite is very async heavy. While I cannot share the world setup (highly complex, and belongs to the company, not me) I can share a small repo I set up to reproduce this issue.
tl;dr

Execute 500 scenarios that sleep for 1 second
Example A puts 500 scenarios into a single file
Example B spreads 500 scenarios over 10 files
Example A takes 5:30 - 6 minutes at -c 32
Example B takes <20 seconds at -c 32 (!!!)

Thank you for the reproduction repo! I'll definitely take a look hopefully this weekend.

Hey @ilslv, any chance you got a chance to look at this?

not yet, unfortunately 😢

We might be able to take a look into this if you could provide any pointers @ilslv ?  We have 1000 tests or more that currently eat up around 40 minutes instead of around 5 minutes!

We've come up with a simple workaround using a wrapper around the basic parser that splits each scenario into its own gherkin feature:
#[derive(Debug, Default)]
struct SingletonParser {
    basic: cucumber::parser::Basic,
}

impl<I: AsRef<Path>> cucumber::Parser<I> for SingletonParser {
    type Cli = <cucumber::parser::Basic as cucumber::Parser<I>>::Cli;
    type Output = stream::FlatMap<
        stream::Iter<std::vec::IntoIter<Result<Feature, cucumber::parser::Error>>>,
        Either<
            stream::Iter<std::vec::IntoIter<Result<Feature, cucumber::parser::Error>>>,
            stream::Iter<iter::Once<Result<Feature, cucumber::parser::Error>>>,
        >,
        fn(
            Result<Feature, cucumber::parser::Error>,
        ) -> Either<
            stream::Iter<std::vec::IntoIter<Result<Feature, cucumber::parser::Error>>>,
            stream::Iter<iter::Once<Result<Feature, cucumber::parser::Error>>>,
        >,
    >;

    fn parse(self, input: I, cli: Self::Cli) -> Self::Output {
        self.basic.parse(input, cli).flat_map(|res| match res {
            Ok(mut feature) => {
                let scenarios = mem::take(&mut feature.scenarios);
                let singleton_features = scenarios
                    .into_iter()
                    .map(|scenario| {
                        Ok(Feature {
                            name: feature.name.clone() + " :: " + &scenario.name,
                            scenarios: vec![scenario],
                            ..feature.clone()
                        })
                    })
                    .collect_vec();
                Either::Left(stream::iter(singleton_features))
            }
            Err(err) => Either::Right(stream::iter(iter::once(Err(err)))),
        })
    }
}

Before:
[Summary]
1 feature
702 scenarios (702 passed)
41957 steps (41957 passed)
test test ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2013.41s

After:
[Summary]
702 features
702 scenarios (702 passed)
41957 steps (41957 passed)
test test ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 165.86s


Add Indian Video streaming sites.

just a suggestion.
JioCinema
Hotstar (I don't think it needs one as it Auto-Redirects from Disney+)
SonyLIV
JioCinema is one of the biggest video streaming services in India.
Licenses and exclusively has shows from Paramount+,HBO (Max) and peacock
Site link: https://www.jiocinema.com/
Logo: https://www.jiocinema.com/images/jc_logo_v2.svg

@YaseenHQ Added!