Fixed instrumentation test runner OK sniffing

Fixed regex that looks for OK sign
Test plan (required)

circle CI results

@bestander updated the pull request.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


Validator russian individual tax number

This Merge Request proposes the implementation of a validation feature for the Russian Individual Taxpayer Identification Number (INN). This enhancement aims to improve the quality of user-entered data and prevent errors associated with incorrect INNs.

Hi @tabbols95, thanks for the contribution. Country specific validations must go under src/validators/i18n/
Please add test cases as well.

Hi @yozachar, thank you for your feedback. I have moved the changes to the i18n directory and added tests. All tests passed successfully.
Thank you for the library. I use it very actively in my work.
Best regards, Alexander.

Done


runner: force output buffers to flush logs immediately using PYTHONUN…

Logs are missing from subprocesses probably because the buffers are only flushed once full and may be lost if the subprocess crashes -- so force output buffers to flush logs immediately using PYTHONUNBUFFERED env var.

LGTM, but let's wait for @j0sh to comment if if solves his problem.

This does not work. We need this: https://github.com/livepeer/ai-worker/pull/254

Closing this one, since @j0sh sent another PR


AggressiveSplittingPlugin breaks with recordsInputPath

Do you want to request a feature or report a bug?
Report a bug.
What is the current behavior?
Using just recordsOutputPath works as expected, but specifying recordsPath or recordsInputPath causes AggressiveSplittingPlugin to hang at 100% CPU for about four hours on my machine before throwing the following exception:
path.js:78
function normalizeStringPosix(path, allowAboveRoot) {
                             ^

RangeError: Maximum call stack size exceeded
    at normalizeStringPosix (path.js:78:30)
    at Object.resolve (path.js:1161:20)
    at Object.relative (path.js:1232:18)
    at str.split.map (/node_modules/webpack/lib/optimize/AggressiveSplittingPlugin.js:14:17)
    at Array.map (native)
    at identifier.split.map (/node_modules/webpack/lib/optimize/AggressiveSplittingPlugin.js:13:26)
    at Array.map (native)
    at /node_modules/webpack/lib/optimize/AggressiveSplittingPlugin.js:12:32
    at Array.map (native)
    at Compilation.compilation.plugin (/node_modules/webpack/lib/optimize/AggressiveSplittingPlugin.js:77:46)

If the current behavior is a bug, please provide the steps to reproduce.
const cheerio	= require('cheerio');
const webpack	= require('webpack');

webpack({
	entry: {
		main: './cyph.com/main'
	},
	output: {
		filename: '[name].js',
		chunkFilename: '[name].js',
		path: '/home/gibson/.build/shared/js/cyph.com/pack'
	},
	plugins: [
		new webpack.optimize.AggressiveSplittingPlugin({
			minSize: 30000,
			maxSize: 50000
		}),
		/* Workaround for issue #3851 */
		new webpack.optimize.CommonsChunkPlugin({
			name: 'init',
			minChunks: Infinity
		})
	],
	recordsPath: '/home/gibson/.build/cyph.com/webpack.json'
}, (err, stats) => {
	if (err) {
		throw err;
	}

	const $	= cheerio.load(
		fs.readFileSync('/home/gibson/.build/cyph.com/index.html').toString()
	);

	$('script[src="/js/cyph.com/main.js"]').remove();

	for (const chunk of stats.compilation.entrypoints.main.chunks) {
		for (const file of chunk.files) {
			$('body').append(`<script src='/js/cyph.com/pack/${file}'></script>`);
		}
	}

	fs.writeFileSync('/home/gibson/.build/cyph.com/.index.html', $.html().trim());
});

Related records file: https://github.com/cyph/cyph/blob/master/cyph.com/webpack.json
What is the expected behavior?
Webpack should run successfully with no exceptions.
Please mention other relevant information such as the browser version, Node.js version, Operating System and programming language.
Webpack: 2.2.0
Browser: Chrome 56.0.2924.76
Node.js: 6.9.4
Operating system: Debian Jessie in a Docker container on OS X El Capitan
Programming language: JavaScript/TypeScript

Just did a little bit of debugging in a repl to see if I could spot any obvious issues with the code from the stack trace.
const path = require('path');

/* Copied from AggressiveSplittingPlugin.js */
function makeRelative(context) {
	return function(module) {
		let identifier = module.identifier();
		return identifier.split("|").map((str) => {
			return str.split("!").map((str) => {
				return path.relative(context, str);
			}).join("!");
		}).join("|");
	};
}

const records = JSON.parse(fs.readFileSync('/cyph/cyph.com/webpack.json').toString())

for (const chunk of records.aggressiveSplits) {
	for (const id of chunk.modules) {
		console.log(
			makeRelative('/home/gibson/.build/shared/js')({identifier: () => id})
		);
	}
}

Worked as expected with no errors, so I'm not sure what Webpack is doing differently that would cause this.

Some more debugging: no idea whether this is expected or not, but I threw in some console logs and found that the function that starts on line 64 of AggressiveSplittingPlugin.js is being invoked repeatedly at some point within both the loop from line 73 and the loop from line 109.

This looks like a bug in the Plugin. I probably will be difficult to reproduce.
Could you prepare a repo or branch with all the relavant files and the records to reproduce?

Sure, I'll try to get a minimal repro set up today.

Minimal repro:
git clone https://github.com/buu700/webpack-4121
cd webpack-4121
./webpack.js

If I delete records.json and then run webpack.js, it finishes successfully in about 45 seconds. If I run webpack.js with records.json intact, it seems to hang as reported above.
The main precondition for reproduction, as far as I can tell, is that the records input be different from what the records output would have been if it were generated from scratch by packing the same code. In this case, I generated records.json by deleting an arbitrary subset of the import statements in main.js (lines 18 - 41) and running webpack.js. If I delete those same lines again and run webpack.js with records.json present, it finishes successfully in 12 seconds.

Update: tested and confirmed that it's still reproducible with webpack 2.3.
Any thoughts on what the general timeline might look like for resolving this issue? AggressiveSplittingPlugin is great in theory with the proliferation of HTTP/2, but would be much more useful if it also supported this feature to take better advantage of client caches.

I think still valid :disappointed:

@buu700 Can you provide simple reproducible test repo?

bump

AggressiveSplittingPlugin is deprecated in favor SplitChunksPlugin for webpack v5, I don't think we should fix this given that it will be removed in the future and deprecated now, please avoid using AggressiveSplittingPlugin, also I can't reproduce... Sorry for delay


Stream is aborted unexpectedly

Confirm this is a Node library issue and not an underlying OpenAI API issue

[X] This is an issue with the Node library

Describe the bug
I'm using OpenAI SDK in the client (Next.js) and server (App Router, edge runtime) setting.
The issue is that if I passed an AbortController to the fetch call, the stream was aborted as soon as it's initialized on the client side. I received no content/error on the client side, and only "Error: aborted" on the server side.
This is my first time using this SDK, but I had read the docs and scoured the issues on GitHub. I'm sorry if I missed anything obvious.
To Reproduce
Client code:
const abort = new AbortController();
const res = await fetch('http://localhost:3000/api/chat', {
  body: JSON.stringify(params),
  headers: { 'Content-Type': 'application/json' },
  method: 'POST',
  signal: abort.signal,
});

const stream = ChatCompletionStreamingRunner.fromReadableStream(res.body);
console.log(abort.signal.aborted); // false

// not called
stream.on('content', (delta) => {...});

// not called
stream.on('error', (err) => {});

stream.on('abort', () => {
  // abort callback called
  console.log(abort.signal.aborted); // true
});

Server code:
export const POST = async (req: Request) => {
  const params: OpenAI.ChatCompletionCreateParamsStreaming = await req.json();

  const stream = openai.beta.chat.completions.stream(params, {
    signal: req.signal, // even if I removed this line, the issue still persists
  });

  return new Response(stream.toReadableStream());
};

Sanity check: if I don't pass the abort controller to the fetch call, I won't have this issue (obviously).
For personal reference, this issue is similar to #194
Code snippets
No response
OS
macOS
Node version
18
Library version
4.26.0

it was working fine from past few days now it is aborting from back end side even I haven't changed the code . did you find any fix ?
Error:-
Stream {
  iterator: [AsyncGeneratorFunction: iterator],
  controller: AbortController { signal: AbortSignal { aborted: false } }
}


[stable/redis-ha] Use readinessProbe to control DNS routing of redis-ha-service

Since all of our applications connect directly to the master node, we need redis-ha-service to always point to the master, whether or not the redis failover has occurred.
We try to use the readinessProbe, which is to use the readiness script to detect the role of the current redis node. If it is slave, which means it is not ready, redis-ha-service will not route to the slave node. Also redis-ha-service can be automatically routed to the new master node when redis failover has occurred.
I did some detailed tests and it works.
I wonder if this scheme is feasible?
The general configuration is as follows:
readinessProbe:
  exec:
    command: ["sh", "/opt/appl/redis/probes/writeness.sh", "6379"]`

#!/bin/sh
set -eu
REDIS_HOST=localhost
REDIS_PORT=6379
REDIS_PASSWORD=pwd@redis

# check localhost redis instance`s role in pod, if is not master, then return 1, means not ready, so dns will not route to this instance
CHECK_SERVER="$(redis-cli -h "$REDIS_HOST" -p "$REDIS_PORT" -a "$REDIS_PASSWORD" role | grep master)"
if [ "$CHECK_SERVER" != "master" ]; then
  echo "Server readonly: $CHECK_SERVER"
  exit 1
fi

@jackiechan1981
This will likely be solved in my PR: https://github.com/helm/charts/pull/15305
This deploys a HAProxy that will effectively always point to master.
That being said, the chart works as intended. Your sentinels are the utility you should be using for obtaining the address of the master, you should then use the library to connect to your Redis instance.
Note, most libraries that support sentinel implicitly do this.
Additional note, the current version of the chart assumes all communication is done from inside the k8 cluster.

Hi, @DandyDeveloper , thanks very much for your reply!
I just saw that this PR: #15305  has been approved and get merged into the master 4 hours ago, so it can be used directly!
I have been trying to solve this problem for a few days, until I found your great solution of HAProxy. Only because this PR has not been approved yet, so I haven't studied it in detail, but trying to find ohter solutions.
Thanks again for your reply and your great PR!

@jackiechan1981
Glad to have helped. Hope this does the job you need, if you have any problems. Feel free to open another issue.
Can you close this when you're confident it solves your problem?
All the best!


feat: Restructuring the whole development section

In this PR, I completely restructured the Docs > Platform > Actors > development, as the screenshot below shows.
Disclaimer: Some pages might be a bit empty now. After this is merged, I am going to review page-by-page and, fill in more content / remove redundant content ... so cleanup and improvements will continue.

 But there are two comments we need to resolve now as those are dictating the structure.
1. Actor Definition VS Deployment

source code and source types should probably be merged, they're kinda the same thing
maybe deployment, CI and testing could be sections under source code? It would also make it little less weird to have "Deployment" and then "Builds" which are kinda the same.
For example, nowhere under Source code we talk about the differences between Web IDE, git repository integration and all the other important source code topics

I get the point here. I was considering this, but then the:

The actor definition section gets too bloated
And mainly, we include 2 unrelated parts

the "Actor definition" describes how the actor looks like - all the files, directories, code features. I.e. basically everything you find in the Actor repository/source code.
the "Deployment" describes how to get it to Apify. The Source Type in fact has nothing to do with source code but it's a source for the deployment - Git / Gist / Zip / Web UI.

2. Placement of "Metamorph" and "Container web server"

THe container web server really feels weird under source code. It does not have a lot to do with the actor's source code, it's mostly about a platform feature that exposes a port and then its a tutorial how to use it.
I find it weird to have two such edge-case (metamorph, web server) use cases promoted with big cards on the source code index. It makes them look as the most important thing that everybody should know about.

With this, I don't really know. IMHO, it belongs to the "Actor definition" as those are basically features you can use in the Actor's code. But maybe we could have a separate item for it following the source code, like "Advanced features / Features / ...". But in the end, it's again something you use in source code so perhaps just to stress there that these are kind of advanced features, not everybody needs?

@mtrunkat Hmm, interesting. I missed that source code is under Actor definition. What you say makes sense. On the other hand, I don't think that Source code necessarily needs to be under Actor definition. To me, Actor definition is the Apify specific configuration and then source code can live in GitHub and it's... source code. Not a definition of an Actor. Similarly like package.json is the definition of a Node.js module, but I would not call the source code module definition. I don't have a strong opinion about it though. Its very philosophical... But it would make the actor definition section smaller and less nested...


[SPARK-17698] [SQL] Join predicates should not contain filter clauses

What changes were proposed in this pull request?
This is a backport of https://github.com/apache/spark/pull/15272 to 2.0 branch.
Jira : https://issues.apache.org/jira/browse/SPARK-17698
ExtractEquiJoinKeys is incorrectly using filter predicates as the join condition for joins. canEvaluate [0] tries to see if the an Expression can be evaluated using output of a given Plan. In case of filter predicates (eg. a.id='1'), the Expression passed for the right hand side (ie. '1' ) is a Literal which does not have any attribute references. Thus expr.references is an empty set which theoretically is a subset of any set. This leads to canEvaluate returning true and a.id='1' is treated as a join predicate. While this does not lead to incorrect results but in case of bucketed + sorted tables, we might miss out on avoiding un-necessary shuffle + sort. See example below:
[0] : https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala#L91
eg.
val df = (1 until 10).toDF("id").coalesce(1)
hc.sql("DROP TABLE IF EXISTS table1").collect
df.write.bucketBy(8, "id").sortBy("id").saveAsTable("table1")
hc.sql("DROP TABLE IF EXISTS table2").collect
df.write.bucketBy(8, "id").sortBy("id").saveAsTable("table2")

sqlContext.sql("""
  SELECT a.id, b.id
  FROM table1 a
  FULL OUTER JOIN table2 b
  ON a.id = b.id AND a.id='1' AND b.id='1'
""").explain(true)

BEFORE: This is doing shuffle + sort over table scan outputs which is not needed as both tables are bucketed and sorted on the same columns and have same number of buckets. This should be a single stage job.

Added a new test case for this scenario : SPARK-17698 Join predicates should not contain filter clauses
Ran all the tests in BucketedReadSuite

Test build #67396 has started for PR 15600 at commit df50838.

Test build #67396 has finished for PR 15600 at commit df50838.

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

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

Merged build finished. Test PASSed.

Thanks - merging in. Can you close this?


Chore - utils

Pull Request Test Coverage Report for Build 230

13 of 13 (100.0%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.138%

Totals

Change from base Build 229:
0.0%

Covered Lines:
414

Relevant Lines:
422

💛  - Coveralls


Faces parallel to tenon not getting removed from mortised member

Issue

Faces parallel to tenon not getting removed from mortised member when the tenon is exposed (e.g. drop in mortise, spline, etc.)

Steps to reproduce

Create a post (8" x 8" x 10') component
Create a girt (8" x 8" x 8') component
Position the girt so the top left corner meets to the top right post

Create a tenon the width of the girt (no, this is not a realistic joint, but it does quickly highlight the issue, I have run through the tutorial here and the issue persists.

Create a shop drawing of the post
You can see the edges of the mortise are not cut out of the post.  This shows up on splines (I've tested using the spline 32 example you provide) and any other 'cutting' that cuts the edge of a timber.

Additional Info
This is probably due to an update on the SketchUp Make side as this only happened when I downloaded a newer version of SketchUp Make, I think it was the change to Make 2017.  I know nothing about Ruby, so I have no ability to submit a pull request fixing this (though I have tried to figure out your code (I'm a web guy...)
Versions Affected
SketchUp MAKE 17.2.2554 & 17.3.116
TF Rubies: 2.4.7 & 2.5.0

Here you are!  Thanks for the lightning-fast response!
Andrew
From: Clark Bremer @.>
Reply-To: clarkbremer/TFRubies @.>
Date: Tuesday, January 25, 2022 at 10:58 AM
To: clarkbremer/TFRubies @.>
Cc: Andrew Engebretson @.>, Author @.***>
Subject: Re: [clarkbremer/TFRubies] Faces parallel to tenon not getting removed from mortised member (Issue #2)
Hi Andrew. Send my your test SU file, please.
On Tue, Jan 25, 2022 at 9:56 AM Andrew Engebretson @.***>
wrote:

Issue

Faces parallel to tenon not getting removed from mortised member
when the tenon is exposed (e.g. drop in mortise, spline, etc.)

Steps to reproduce

Create a post (8" x 8" x 10') component
Create a girt (8" x 8" x 8') component
Position the girt so the top left corner meets to the top right post
[image: Screen Shot 2022-01-25 at 10 34 38 AM]
https://user-images.githubusercontent.com/16763238/151007821-77ab3870-209c-4254-b399-f2c21f1ca793.png
Create a tenon the width of the girt (no, this is not a realistic
joint, but it does quickly highlight the issue, I have run through the
tutorial here https://www.youtube.com/watch?v=83BASsys4x4 and the
issue persists.
[image: Screen Shot 2022-01-25 at 10 37 57 AM]
https://user-images.githubusercontent.com/16763238/151008637-8ada1b45-9de6-479d-b3a3-866fab6d135d.png
Create a shop drawing of the post
You can see the edges of the mortise are not cut out of the post.
This shows up on splines (I've tested using the spline 32 example you
provide) and any other 'cutting' that cuts the edge of a timber.

Additional Info
This is probably due to an update on the SketchUp Make side as this only
happened when I downloaded a newer version of SketchUp Make, I think it was
the change to Make 2017. I know nothing about Ruby, so I have no ability to
submit a pull request fixing this (though I have tried to figure out your
code (I'm a web guy...)
Versions Affected
SketchUp MAKE 17.2.2554 & 17.3.116
TF Rubies: 2.4.7 & 2.5.0
—
Reply to this email directly, view it on GitHub
https://github.com/clarkbremer/TFRubies/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXS2YFFEZWF64D376AWDULUX3BZJANCNFSM5MYUSWQA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHubhttps://github.com/clarkbremer/TFRubies/issues/2#issuecomment-1021337589, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AD74SZSUY7MAIWMRMUUZY3TUX3CB5ANCNFSM5MYUSWQA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>

You seem to have missed the last step.  While editing the timber component,
right click on the tenon component, and choose "TF Create Joint".
On Tue, Jan 25, 2022 at 10:03 AM Andrew Engebretson <
@.***> wrote:

Here you are! Thanks for the lightning-fast response!
Andrew
From: Clark Bremer @.>
Reply-To: clarkbremer/TFRubies @.>
Date: Tuesday, January 25, 2022 at 10:58 AM
To: clarkbremer/TFRubies @.>
Cc: Andrew Engebretson @.>, Author @.***>
Subject: Re: [clarkbremer/TFRubies] Faces parallel to tenon not getting
removed from mortised member (Issue #2)
Hi Andrew. Send my your test SU file, please.
On Tue, Jan 25, 2022 at 9:56 AM Andrew Engebretson @.***>
wrote:

Issue

Faces parallel to tenon not getting removed from mortised member
when the tenon is exposed (e.g. drop in mortise, spline, etc.)

Steps to reproduce

Create a post (8" x 8" x 10') component
Create a girt (8" x 8" x 8') component
Position the girt so the top left corner meets to the top right post
[image: Screen Shot 2022-01-25 at 10 34 38 AM]
<
https://user-images.githubusercontent.com/16763238/151007821-77ab3870-209c-4254-b399-f2c21f1ca793.png>

Create a tenon the width of the girt (no, this is not a realistic
joint, but it does quickly highlight the issue, I have run through the
tutorial here https://www.youtube.com/watch?v=83BASsys4x4 and the
issue persists.
[image: Screen Shot 2022-01-25 at 10 37 57 AM]
<
https://user-images.githubusercontent.com/16763238/151008637-8ada1b45-9de6-479d-b3a3-866fab6d135d.png>

Create a shop drawing of the post
You can see the edges of the mortise are not cut out of the post.
This shows up on splines (I've tested using the spline 32 example you
provide) and any other 'cutting' that cuts the edge of a timber.

Additional Info
This is probably due to an update on the SketchUp Make side as this only
happened when I downloaded a newer version of SketchUp Make, I think it
was
the change to Make 2017. I know nothing about Ruby, so I have no ability
to
submit a pull request fixing this (though I have tried to figure out
your
code (I'm a web guy...)
Versions Affected
SketchUp MAKE 17.2.2554 & 17.3.116
TF Rubies: 2.4.7 & 2.5.0
—
Reply to this email directly, view it on GitHub
https://github.com/clarkbremer/TFRubies/issues/2, or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAXS2YFFEZWF64D376AWDULUX3BZJANCNFSM5MYUSWQA>

.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub<
https://github.com/clarkbremer/TFRubies/issues/2#issuecomment-1021337589>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AD74SZSUY7MAIWMRMUUZY3TUX3CB5ANCNFSM5MYUSWQA>.
Triage notifications on the go with GitHub Mobile for iOS<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android<
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
@.***>
—
Reply to this email directly, view it on GitHub
https://github.com/clarkbremer/TFRubies/issues/2#issuecomment-1021343504,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXS2YD4YMETFEJFLTOJYX3UX3CWHANCNFSM5MYUSWQA
.
You are receiving this because you commented.Message ID:
@.***>

If that were true, the mortise shouldn't show up at all though, correct?  When I right click and inspect the tenon, it is a joint

I used the file 'test.skp'.  It's not a joint in that file.
On Tue, Jan 25, 2022 at 10:09 AM Andrew Engebretson <
@.***> wrote:

If that were true, the mortise shouldn't show up at all though, correct?
When I right click and inspect the tenon, it is a joint
[image: Screen Shot 2022-01-25 at 11 08 16 AM]
https://user-images.githubusercontent.com/16763238/151014251-1046d8d1-4d20-47b8-9d44-f677a4968f88.png
—
Reply to this email directly, view it on GitHub
https://github.com/clarkbremer/TFRubies/issues/2#issuecomment-1021349747,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXS2YGNMYMOVJ7IZCKTQTTUX3DNPANCNFSM5MYUSWQA
.
You are receiving this because you commented.Message ID:
@.***>

Ah, I deleted the test file after opening the issue so rushed a recreate, here is file with the joint.
Thanks
From: Clark Bremer @.>
Reply-To: clarkbremer/TFRubies @.>
Date: Tuesday, January 25, 2022 at 11:13 AM
To: clarkbremer/TFRubies @.>
Cc: Andrew Engebretson @.>, Author @.***>
Subject: Re: [clarkbremer/TFRubies] Faces parallel to tenon not getting removed from mortised member (Issue #2)
I used the file 'test.skp'. It's not a joint in that file.
On Tue, Jan 25, 2022 at 10:09 AM Andrew Engebretson <
@.***> wrote:

If that were true, the mortise shouldn't show up at all though, correct?
When I right click and inspect the tenon, it is a joint
[image: Screen Shot 2022-01-25 at 11 08 16 AM]
https://user-images.githubusercontent.com/16763238/151014251-1046d8d1-4d20-47b8-9d44-f677a4968f88.png
—
Reply to this email directly, view it on GitHub
https://github.com/clarkbremer/TFRubies/issues/2#issuecomment-1021349747,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXS2YGNMYMOVJ7IZCKTQTTUX3DNPANCNFSM5MYUSWQA
.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHubhttps://github.com/clarkbremer/TFRubies/issues/2#issuecomment-1021353058, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AD74SZWKAZ52DCOTJZI7LH3UX3DZXANCNFSM5MYUSWQA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>

No Attachment.  BTW, we can bypass github, and use @.***
On Tue, Jan 25, 2022 at 10:16 AM Andrew Engebretson <
@.***> wrote:

Ah, I deleted the test file after opening the issue so rushed a recreate,
here is file with the joint.
Thanks
From: Clark Bremer @.>
Reply-To: clarkbremer/TFRubies @.>
Date: Tuesday, January 25, 2022 at 11:13 AM
To: clarkbremer/TFRubies @.>
Cc: Andrew Engebretson @.>, Author @.***>
Subject: Re: [clarkbremer/TFRubies] Faces parallel to tenon not getting
removed from mortised member (Issue #2)
I used the file 'test.skp'. It's not a joint in that file.
On Tue, Jan 25, 2022 at 10:09 AM Andrew Engebretson <
@.***> wrote:

If that were true, the mortise shouldn't show up at all though, correct?
When I right click and inspect the tenon, it is a joint
[image: Screen Shot 2022-01-25 at 11 08 16 AM]
<
https://user-images.githubusercontent.com/16763238/151014251-1046d8d1-4d20-47b8-9d44-f677a4968f88.png>

—
Reply to this email directly, view it on GitHub
<
https://github.com/clarkbremer/TFRubies/issues/2#issuecomment-1021349747>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAXS2YGNMYMOVJ7IZCKTQTTUX3DNPANCNFSM5MYUSWQA>

.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub<
https://github.com/clarkbremer/TFRubies/issues/2#issuecomment-1021353058>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AD74SZWKAZ52DCOTJZI7LH3UX3DZXANCNFSM5MYUSWQA>.
Triage notifications on the go with GitHub Mobile for iOS<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android<
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
@.***>
—
Reply to this email directly, view it on GitHub
https://github.com/clarkbremer/TFRubies/issues/2#issuecomment-1021356492,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXS2YGFWQQ2HDVZAJUMCC3UX3EGDANCNFSM5MYUSWQA
.
You are receiving this because you commented.Message ID:
@.***>

After talking directly with Clark, this works as expected.


Tabs with Radio Control

I was wondering if tabs could also be controlled via the Radio Input. This would avoid having to put in an extra controller just for the switching. Thank you.

You mean switching tab content without JS?

Yes, like it is in the guide for the Button Group:
https://daisyui.com/components/button-group/

  <input type="radio" name="options" data-title="1" class="btn">
  <input type="radio" name="options" data-title="2" class="btn" checked>
  <input type="radio" name="options" data-title="3" class="btn">
  <input type="radio" name="options" data-title="4" class="btn">

switching tab content without JS?

is there an example somewhere of your recommended usage for tabs?

controlled via the Radio Input.

indeed it is possible:
https://github.com/saadeghi/daisyui/discussions/577#discussioncomment-3382031

Here's another example:
https://play.tailwindcss.com/IlSZ3DVeUT?file=css
:where(.tabs input[type=radio]:checked+label){
  @apply tab-active;
}

  <input type="radio" class="hidden" name="options" id="option-1" checked />
  Tab 1

  <input type="radio" class="hidden" name="options" id="option-2" />
  Tab 2

  <input type="radio" class="hidden" name="options" id="option-3" />
  Tab 3

Yes but this example doesn't have content. Do you know a way to also show content with pure css?


Missing question mark that separate URL from query string parameters

What are the steps to reproduce this issue?
Generate react-hooks based on a Swagger-file with a GET request that need parameters in query string like this:
/api/users?name=alex&surname=ferreli
What happens?
React-hooks begin generated without question mark:
/api/usersname=alex&surname=ferreli
Backend didn't understand the request and respond 404.
What were you expecting to happen?
I expect that the API is called with question mark that separate URL from parameters.
Any logs, error output, etc?
Just a 404 on DevTools because of wrong generated URL
What versions are you using?
Operating System: Windows 10
Package Version: latest, v6.8.1
Browser Version: Chrome 103

Closing this as no response from OP and I have not had any issues with query params in any of my apps


[Security Config Mount on providing securityConfigSecret][OpenSearch]

Describe the bug
The security-config-complete was not mounting when an external secret was passed using Values.securityConfig.config.securityConfigSecret.
According to the docs, a user should be able to pass in a pre-created secret under Values.securityConfig.config.securityConfigSecret, which can be used to provide securityConfig config files. However, a bug in the statefulset.yaml was skipping the volume mount for this use case, even though the volume was being created by it.
To Reproduce
Steps to reproduce the behavior:

Pass in Values.securityConfig.config.securityConfigSecret instead of Values.securityConfig.config.data, and install the chart.
The chart installation will fail to mount the config files under /plugins/opensearch-security

Expected behavior
The  security-config-complete volume that is created by the statefulset should be attached as a volumeMount on the default mountPath.
Chart Name
helm-charts/opensearch
PR Fix
https://github.com/opensearch-project/helm-charts/pull/209

Fixed in #209


Adding enhanced hover to social icons

This will be edited to be

enhanced hover effects

Please let me if I you can assign this or not


add rust version check and install link to readme

fixes #32
I was cleaning up my account a few days back and deleted cargo without thinking about it. I got this error and realized my mistake. After reinstalling rust everything is running again!
I think you may want to add the link to install rust in your install instructions!
$ pip install sourmash_plugin_directsketch==0.3.0

Collecting sourmash_plugin_directsketch==0.3.0
  Using cached sourmash_plugin_directsketch-0.3.0.tar.gz (152 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]
      error: rustup could not choose a version of cargo to run, because one wasn't specified explicitly, and no default is configured.
      help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain.

      Cargo, the Rust package manager, is not installed or is not on PATH.
      This package requires Rust and Cargo to compile extensions. Install it through
      the system's package manager or via https://rustup.rs/

      Checking for Rust toolchain....
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Thanks for the PR! Thinking on it -- I'd like to avoid having folks install rust directly. But that means I should actually describe the install process from conda using environment.yml file in the README.
I'm not sure how this interacts with existing cargo on your system - would assume if you already had rust it would not reinstall via conda. Which is maybe why deleting cargo borked everything?

or better yet, I should go ahead and make this conda installable

That sounds like a much nicer solution!

@ccbaumler can I close this? Aka, did the conda installation solve this for you?

Sounds good to me. I believe that my issue has been solved.


Configurator [PROTOTYPE]

Added configurator prototype window to GUI (see readme for starting configurator as stand-alone project). Plus some general refactoring, cleanup and bug fixing ...

Just testing (no proper reviewing yet) I found one issue (for my stuff at least) with the following workflow:

Start MegaMol with configurater.lua project
Load CompositingExample.lua in configurator
Layout graph, then save otherwise unchanged graph to a new project file
Exit MegaMol, start it again with the newly saved project -> black screen

Note that the original CompositingExample.lua works just fine with the same MegaMol version. Also, starting MegaMol with the CompositingExample, loading the running project in the configurator and then saving it to a new file somehow seems to produce a working project file...

Some more comments after additional hands-on testing with current version:

If parts of the graph are moved out of the lower screen boundary, they won't be rendered properly after zooming out until the view is panned
Happened to me once that when loading a running project, I had two gui views in the project which I noticed when I couldn't save the project (rightly so). However, I couldn't reproduce this bug a second time yet.
Not a bug: Zooming in/out with the scroll wheel is a little slow right now.
Another feature thing: I guess a more feature-rich file browser would require quite a lot of time? Therefore no priority for current PR, but a "move up a folder" button was greatly missed during testing.


Improve error handling in Run Service.vi by chaining errors

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Run Service.vi, the main VI of a measurement service had a number of error handling deficiencies.

If the discovery service wasn't running, the front panel of the service would stay running, showing a port. It wouldn't show any error until you hit the Stop button. Now, the service stops immediately with this error

Other errors from user VIs such as Get Measurement Details.vi would not show errors. Now you get a dialog such as this immediately and the service stops

fixes #99
Why should this Pull Request be merged?
Common error conditions should be made clear to the user and fatal ones should immediately stop the service to give feedback.
What testing has been done?
Manual testing of error conditions after building the measurement service package.

Run Service.vi main flow now has mostly a single error rail. The exception is that we still unregister from the discovery service if there was an error elsewhere down the line.

Register UI Stop Event.vi now stops immediately if there is an upstream error.

Run Service.vi main flow now has mostly a single error rail. The exception is that we still unregister from the discovery service if there was an error elsewhere down the line.

In Run Service, I notice that the error line out of Stop Server terminates when it hits the flat sequence.  Even if we deliberately want errors on that wire to be ignored by the discovery unregistration calls, should we best merge it into main error line afterward, so any errors that may occur therein have a means to surface in the simple error hander call?

Run Service.vi main flow now has mostly a single error rail. The exception is that we still unregister from the discovery service if there was an error elsewhere down the line.

In Run Service, I notice that the error line out of Stop Server terminates when it hits the flat sequence. Even if we deliberately want errors on that wire to be ignored by the discovery unregistration calls, should we best merge it into main error line afterward, so any errors that may occur therein have a means to surface in the simple error hander call?

Yes, I think you're right. We should be merging those errors. I'll take a look at the old one and it was probably doing that.

.. and since the Unregister call itself is doing cleanup, we should execute it with best-effort, regardless of whether an error had occurred beforehand.  So, I think we should route the error wire around that call (effectively always passing no error into the node).
If I recall, gprc-labview generates the error handling within the Discov. Destroy node so as to execute regardless of whether there was an incoming error.  It'd be nice if we had a way to customize that paradigm of error-handling into the auto-generated Unregister node (... so that callers could wire it up with standard error tracks...), but that customization isn't yet supported in the proto files / generator.

@aepete Not convinced I did this right. How does this look?

That's pretty much what I had in mind, @dixonjoel !


Compile error: google go-github not found

at 2020/01/13, go get -u fail.
$ go get -u github.com/reviewdog/reviewdog/cmd/reviewdog
package github.com/google/go-github/v29/github: cannot find package "github.com/google/go-github/v29/github" in any of:
        c:\go\src\github.com\google\go-github\v29\github (from $GOROOT)
        C:\Users\<usr>\go\src\github.com\google\go-github\v29\github (from $GOPATH)
package github.com/google/go-github/v28/github: cannot find package "github.com/google/go-github/v28/github" in any of:
        c:\go\src\github.com\google\go-github\v28\github (from $GOROOT)
        C:\Users\<usr>\go\src\github.com\google\go-github\v28\github (from $GOPATH)
exit status 1

(windows , nyagos)
check github.com/google/go-github

Usage
import "github.com/google/go-github/v29/github"	// with go modules enabled (GO111MODULE=on or outside GOPATH)
import "github.com/google/go-github/github" // with go modules disabled

This project go get must need GO11MODULE?

This project go get must need GO11MODULE?
Yes

Thanks, OK.


Bump version no to pick up fix for failing Windows build

Checklist

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

@conda-forge-admin, please rerender

All good, merge


Align napi options for alias, fallback and main_fields.

https://github.com/webpack/enhanced-resolve/blob/58464fc7cb56673c9aa849e68e6300239601e615/types.d.ts#L486-L630

These are too complicated.


Check for SQL errors in revert and verify files [8]

###Description of the Tech Debt###
NOTE: If we decide to get rid of the revert and verify files, this issue is irrelevant.
We don't typically use/run the revert and verify files locally, so if there's an error in them, we may not know about it.
###Tech Debt Triage#
The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.
Risk Value Scoring:

Level
Value

High
3

Medium
2

Low
1

Technical Debt - Risk Types
Level
Value

Business Area Risk - Risk of business area visibility / damage to user experience

2

Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it

1

System Fault Risk - Risk of system errors or application downtime

2

Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time?

2

Time Sink Risk - How much will this tech debt slow the development process down

1

TOTAL SCORE:

8

@dleard, does your PR https://github.com/bcgov/cas-cif/pull/1190 fix this issue?

I think this card was about creating an automated check for revert/verify. I just manually checked for and fixed some errors that were introduced recently.

Dylan: We use revert in dev, but don't allow reverts past tags in production.
A discussion should be had on whether sqitch verify is actually helpful and worth maintaining.

we've had a few instances where some code was hastily pushed to dev without being checked if it runs properly - having an automated action that reverts and verifies would help a little with this as an additional check

revert is more important than verify. This card has implemented the revert check. We can talk about verify again if we decide it is a useful check.


this project is dead ?

this is cool project don't stop bro
Record Start
^CException in thread Thread-1 (_start_recording):
Traceback (most recent call last):
File "/usr/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
self.run()
File "/usr/lib/python3.10/threading.py", line 953, in run
self._target(*self._args, **self._kwargs)
File "/home/archkubi/.local/lib/python3.10/site-packages/pyscreenrec/init.py", line 75, in _start_recording
screenshot(os.path.join(self.screenshot_folder, f"s{i}.jpg"))
File "/home/archkubi/.local/lib/python3.10/site-packages/pyscreeze/init.py", line 506, in _screenshot_linux
im = Image.open(tmpFilename)
File "/usr/lib/python3.10/site-packages/PIL/Image.py", line 3068, in open
fp = builtins.open(filename, "rb")
FileNotFoundError: [Errno 2] No such file or directory: '/home/archkubi/pyscreenrec_data/s587.jpg'
Record Finish
some times this problem but this is works and so fast bro keep going
import pyscreenrec, time
recorder = pyscreenrec.ScreenRecorder()
recorder.start_recording('rec.mp4', 30)
print("Record Start")
try:
while True:
pass
except KeyboardInterrupt:
recorder.stop_recording()
print("Record Finish")
https://user-images.githubusercontent.com/80429360/174443247-63b4a041-a70d-429b-9ac2-f7f6cd1a73a0.mp4

I want to get back into maintaining this library, thanks for the appreciation.


Clean up clarify .NET contribute

Detailed the "shared" folder concept

Removed

"An accepted alternative structure contains one project per language that contains all snippets for all articles in that folder. This alternative has been used in the language reference areas because of very small snippets to demonstrate language syntax. It is discouraged in other areas."

We don't need this guidance anymore. Now that we have a "shared" folder, that's where snippets covered by this clause would go.

Moved the Example folder structure section. This is now located after the step: 5 area. It felt really strange being between step 4 and step 5

Removed

"If you're creating samples as well as updating markdown, you'll need to create a separate PR for samples." I don't undestand this clause.

Samples are in a different repo and snippets would be included in the same PR. Maybe this meant snippets but it was written prior to snippets5000.

In the section related to interactive snippets, I swapped the word "sample" to "snippet" to make it clearer as to what is being requested.

@gewarren @BillWagner @tdykstra @IEvangelist
I've clarified a bunch of information related to samples/snippets and introduced the shared folder concept.

#sign-off

@Jim-Parker

#sign-off


Update the NPM

Hey, I was testing the package, seems like you added support for youtube in the functions, but seems like that the package dist folder is from an old version, I don't know if you upload the dist folder manually to the npm package and publish it, but I would recommend you to not to and if you can fix it on npm too!
dist/index.js:

dist/functions.ts:

and yes, I doubled check the package version, it's the latest.

looks like, the published package is not even the same as the one we have on repo

The problem would be solved in PR#2

this issue is closing becuase the PR is now merged


Latest Data?

Is the latest data available for season season 18/19 . ??

I'm not sure this site is actually used much and haven't had time to check to see if the latest data is available. It would be great if someone could look into it and submit a pull request.


rekey is broken with new client structure

I removed rekey for now until we can figure out a better way of doing this with the new client structure.

rekey is now fixed in refactor. More here: #21


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.9.276",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9e2b8368b2079437c6840f3303cb0b7bc9b896ee"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "9e2b8368b2079437c6840f3303cb0b7bc9b896ee",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "virtio_console: Assure used length from device is limited\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.9.276 by commit 9e2b8368b2079437c6840f3303cb0b7bc9b896ee. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001445


The first condition should be d (I mean x value in the formula) used instead of the ascendant value found

https://github.com/0xStarcat/CircularNatalHoroscopeJS/blob/c65e40d9b901b1143ca14af831e05de9ae004835/src/utilities/astronomy.js#L112
The first condition should be x < 0 (I mean d value),
The x (d) value in the formula should be used instead of the ascendant value found in the first condition.

The Ascendant is then found in the correct quadrant (0 to 360 degrees) by using the two rules
https://wikimedia.org/api/rest_v1/media/math/render/svg/68649ded47b9e668ef643fbf313d157ed4037022

  const b = sinFromDegrees(obliquityEcliptic) * tanFromDegrees(latitude)
  const c = cosFromDegrees(obliquityEcliptic) * sinFromDegrees(localSiderealTime)
  const d = b + c
Line   if (d < 0) { ...
So, I've tried a lot and it's true that way (of course it still needs verification)
thanks a lot
Onur

Resolved by #2


Not require "Directory.Read.All" scope if "azure.activedirectory.user-group.allowed-group-names" not configured.

Fix #21284

/azp run java - spring - tests

Hi, @moarychan , @zhichengliu12581 , @yiliuTo , please help to review this PR when you have time.

/azp run java - spring - tests

LGTM.

Hi, @yiliuTo , could you please help to approve this PR?


Try out the leaner orb cache

see https://github.com/solidusio/circleci-orbs-extensions/pull/28

First run (required installing gems from scratch): 25min
Second run (with the cache hit): less than 7min

https://github.com/solidusio/circleci-orbs-extensions/pull/28


Add ability to reload schema config/cache without a restart

I would love to be able to reload the schema config without a full restart. The PostgREST project has two cool ways to do this:
https://postgrest.org/en/stable/schema_cache.html#schema-cache-reloading

listen for a SIGUSR1 signal
Using Postgres' LISTEN/NOTIFY with a dedicated channel

The second method in particular is interesting because it allows the DB admin to set up custom triggers that would send notifications to the custom channel any time a geospatial table changes.

This is a dup of #288 - could you add your notes there? I really like the LISTEN/NOTIFY idea


Polars: add SeriesDomain

Closes #762

Current dependencies on/for this PR:

main

PR #763   👈

This comment was auto-generated by Graphite.

Changes in this PR since last review:

pulled all dependencies down into the Cargo.toml
made polars an optional feature that is not enabled by default
added the polars feature to CI
addressed or responded to review comments

Sorry the diffs aren't in a new commit.

Added suggestions. One more change: when all deps are present, there's not enough disk space in the runner. I added a step to smoke-test to clear unused software that comes with the image. Will need something more for building on other platforms in release.


z-index

how to change the z-index of the date picker when using the top of the model (is comes in under the model)??

Hi! I successfully changed the z-index by using the onOpen hook.

Hi! I successfully changed the z-index by using the onOpen hook.

Thank You for your reply! Please guide me, How to find the onOpen hook in documentation ???

Hi, checkout here: https://mcdatepicker.netlify.app/docs/event-hooks

Hi, checkout here: https://mcdatepicker.netlify.app/docs/event-hooks

Thank you so much


Feather Icon 'archive' returns down arrow

Environment
Android iOS
"react-native-vector-icons": "^5.0.0",
Description
I wanted to use the Feather 'archive' icon, but it's showing the down arrow.
import FeatherIcon from 'react-native-vector-icons/Feather';
...
<FeatherIcon name='archive' color={Theme.colors.lightBlue} />

Probably same issue as in https://github.com/oblador/react-native-vector-icons/issues/881#issuecomment-436612671 🙂


fix: a bug where item status was not being printed out properly

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (b935d12) 95.13% compared to head (041cfef) 95.37%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #38      +/-   ##
==========================================
+ Coverage   95.13%   95.37%   +0.24%
==========================================
  Files          14       14
  Lines         842      843       +1
==========================================
+ Hits          801      804       +3
+ Misses         26       24       -2
  Partials       15       15

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:tada: This pull request is included in version 0.9.1 :tada:
The release is available on GitHub release :rocket:


Add client ip option while extracting url

Checklist

[x] I'm reporting a feature request
[x] I've verified that I'm running youtube-dl version 2020.01.01
[x] I've searched the bugtracker for similar feature requests including closed ones

Description

I extracted a video URL with -g, but it does not play on another machine / in my web browser. I know In many cases, requests for the video (to download/play it) must come from the same IP . Is it possible to add an option to provide the fake ip while extracting the url, for example, youtube-dl -client-ip <IP_ADDRESS> -g http://www.youtube.com/...

Technically impossible.


Missing checks

During the fw split deprecation works, I observed some checks we're missing:

Device file fw min was higher than its max
A duplicate definition existed because the device was included in one file with a range 0.0-255.255, and another where the range was less than full (e.g. 3.0-5.0).

is fixed by https://github.com/zwave-js/node-zwave-js/pull/5619


Support for multiple responses (specifically point-like AEFF and EDISP)

The current spec has some support for multiple responses via the HDU_CLASS key in the index files.
See http://gamma-astro-data-formats.readthedocs.io/en/latest/data_storage/hdu_index/index.html#hdu-type-and-hdu-class
Specifically for AEFF we do support two versions via the keyword HDUCLAS2={'EFF_AREA', 'EFF_AREA_RECO'}
http://gamma-astro-data-formats.readthedocs.io/en/latest/irfs/effective_area/index.html
This is not yet supported in the HDU index file format, there's just one key HDUCLASS='aeff_2d' defined, so it's not possible to access both AEFF via the current index file.
In HESS, in addition now we have the use case of wanting to define and access AEFF and EDISP derived from point-like responses (with a RAD_MAX cut applied) or full-enclosure responses.
Using point-like responses is very common (in HESS it's used e.g. for all AGN analyses), and we'd like to start using it for FITS analyses.
Note that there is a difference (demonstrated in HESS by @bkhelifi), EDISP is worse for events in the PSF tail, so it's not possible to get the correct EDISP from the full-enclosure responses at a high accuracy level, as another argument that we should support point-like responses in the DL3 spec.
So we would like to  extend the IACT DL3 format spec to support point-like IRFs.
Our main questions are:

Which AEFF and EDISP header keys should we use?
How should we support this via the HDU index file?

For the two different AEFF we started to use HDUCLAS2={'EFF_AREA', 'EFF_AREA_RECO'}
So we could use HDUCLAS3={'point-like', 'full-enclosure'} and add the RAD_MAX header key that's already in AEFF to EDISP also.
And then add HDUCLAS2 and HDUCLAS3 columns to the index file spec.
This would satisfy the current use cases for HESS.
It's not very pretty though, because point-like/full-enclosure is not really at a lower or higher level in the hierarchy compared to whether AEFF and EDISP were combined or not. It's just different ways to do responses / analysis.
Another option would be to change the HDUCLASS valid keys to aeff2d_point_reco, aeff2d_fullenclosure_reco, aeff2d_point_true, aeff_fullenclosure_true` instead of adding new columns.
Another option would be to replace the HDUCLASS column with a TAGS column which has a string that is a list of key-value fields, like HDU_CLASS="point=yes,energy=reco" which is super-easy to parse and then scientists or science tools can do selections based on that.
Or directly go to a hierarchical index format instead of sticking with the table.
IMO that would be the best mid-term solution (next year) to develop such a new, better format.
But short-term, my suggestion would be to either add columns or string cases to the existing index file format.
@kosack @mimayer @TarekHC @bkhelifi @registerrier @joleroi  @jknodlseder - Thoughts?
(if no-one comments on this, I will probably go ahead and make a pull request adding extra optional columns to the HDU index file next week)

Hi @cdeil ,
In my opinion, I would go for option 1: HDUCLAS3={'point-like', 'full-enclosure'} (or analogous keywords) This is exactly the use case for HDUCLASn keywords.

It's not very pretty though, because point-like/full-enclosure is not really at a lower or higher level in the hierarchy compared to whether AEFF and EDISP were combined or not. It's just different ways to do responses / analysis.

I don't really see why not. Currently HDUCLAS2 defined which "type" of effective area you are storing, and HDUCLAS3 could fix how it was calculated. Seems reasonable to me (by the way, HDUCLAS1 is not written in the current specs).
And by the way, in MAGIC we would definitely be interested to also have a "point-like" DL3 format... Also for CTA it would make sense to perform a MC point-like source simulation when observing AGNs...

Hi @TarekHC ,
I am happy that the point source analysis is not discarded! It provides a good S/N ratio and more sensitive analysis configurations...
To come back to the posted question, I do not see what is a 'type' of effective area... The use of reco or true energy is related to the algorithm used to fit the spectra. The use of Point-Like effective area or Full Enclosure one is related to an analysis configuration choice, with its own sensitivity and systematics. And of course, every combination (here 4 possibilities) can be chosen.
So, for me, there is no hierarchy between these attributes, all bringing different types of informations.
Personally, I like the 'TAG' option, bringing a lot of flexibility for the future.

:+1:  for the 'TAG' option

I personally don't like the TAG option because it has never been used with FITS files (that I know... any example?). HDUCLASn has been used by many experiments extending the FITS file format.
An example (from ftp://legacy.gsfc.nasa.gov/fits_info/ofwg_recomm/hduclas.list):
RESPONSE						Conforms to "The OGIP RMF
								& ARF File Formats",
								George et al. 1992

		EBOUNDS					specifies energy boundaries
								for response matrix.

		SPECRESP				extension contains spectral
								response vs. energy

 		RSP_MATRIX	REDIST		"Pure" redistribution matrix
								w/o anything else folded in

					FULL		Redist matrix with "everything"
								folded in

					DETECTOR 	Redist matrix with all detector
								components folded in (but NOT
								XRT + Filters).

I don't see many differences between what we want to do and what is done here... But of course, if everyone agrees to use a TAGS keyword, I would be ok with it.

Not sure if you are aware, but a team was created to share data between the 3 main IACT experiments to study LIV. There was a meeting held here in Barcelona, and there seems to be an interest to use a common format to share data. As it is just AGN flares data, they don't really need IRF vs FoV, just the minimum required for a classical "point-like analysis".
Would it make sense to encourage them to use this point-like format? Or is it still too preliminary? I think it would be ideal to have feedback from a real science use case perfective.

Hi @cdeil , @bkhelifi,
In the last few weeks, I have been thinking about this "point-like DL3 files". For 95% of extragalactic use cases this would be enough, and dramatically simplifies IRF calculation. I have some questions:

I guess we want to support point-source IRFs of different sources within the same field of view. Then we would need to add keywords within each IRF HDU denoting which source those IRFs are referring to (or simply a 'point-like' and the coordinates wrt the center of the FoV ¿?)

For the simplest use case of just a point-like source (e.g. just one AGN in our FoV) does it make sense to store the whole FoV within the event list? Or could we allow to already apply the direction cut maximizing sensitivity?

Is there any sample file of a "point-like DL3 file" that you have available? I could have a MAGIC DL3 converter ready in a short time, and also write the proposal within GitHub. Maybe we could have some discussion regarding this topic during the next DL3 telcon?
Cheers and happy new year!

I think the classical XSPEC ARF format is well suited for a point-like IRF format. And it can be "easily" derived from the generic IRF format (I put "easily" in quotes since it includes the theta-cut efficiency that can be derived from the PSF variation over the region of interest)

Le 9 janv. 2017 à 16:31, Tarek Hassan<EMAIL_ADDRESS>a écrit :
Hi @cdeil https://github.com/cdeil , @bkhelifi https://github.com/bkhelifi,
In the last few weeks, I have been thinking about this "point-like DL3 files". For 95% of extragalactic use cases this would be enough, and dramatically simplifies IRF calculation. I have some questions:
I guess we want to support point-source IRFs of different sources within the same field of view. Then we would need to add keywords within each IRF HDU denoting which source those IRFs are referring to (or simply a 'point-like' and the coordinates wrt the center of the FoV ¿?)
For the simplest use case of just a point-like source (e.g. just one AGN in our FoV) does it make sense to store the whole FoV within the event list? Or could we allow to already apply the direction cut maximizing sensitivity?
Is there any sample file of a "point-like DL3 file" that you have available? I could have a MAGIC DL3 converter ready in a short time, and also write the proposal within GitHub. Maybe we could have some discussion regarding this topic during the next DL3 telcon?
Cheers and happy new year!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/open-gamma-ray-astro/gamma-astro-data-formats/issues/71#issuecomment-271313983, or mute the thread https://github.com/notifications/unsubscribe-auth/AC2oV-Ue6-SwyIcvf3fMZjTsLABtCsWxks5rQlLGgaJpZM4KtaXG.

Adding point-source responses in FITS has become a high priority for CTA.
@TarekHC - Are you available to propose a pull request for the spec about how to store it in the coming days?
@jknodlseder - Just using XSPEC ARF is not an option here. We have the FOV dependence, and for analysis there also has to be the information about the energy-dependent THETA cut.
cc @jknodlseder @gernotmaier

@cdeil I think this topic is now closed with #79
If anyone does not agree with the solution implemented, re-open the issue.


autogenerated docs don't update sidebars

Description
https://github.com/kumahq/kuma-website/blob/master/.github/workflows/sync-generated.yml updates files but it doesn't actually update the sidebar.

We don't need this anymore because the docs are not auto-included anyway


Worker nodes are not able to register successfully.

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Have a cluster in v 2.2.6 (AWS) - 1 etc, 1 control plane and 2 worker nodes
Upgrade to rancher:master-head

Expected Result:
The cluster should be active, the nodes in the cluster should be in the active state.
Actual Result:
The worker nodes are stuck in Unavailable status.
The kubelet in the worker nodes crashes
logs:
I0731 23:53:48.988792   10028 container_manager_linux.go:286] Creating device plugin manager: true
I0731 23:53:48.988807   10028 manager.go:109] Creating Device Plugin manager at /var/lib/kubelet/device-plugins/kubelet.sock
I0731 23:53:48.988899   10028 state_mem.go:36] [cpumanager] initializing new in-memory state store
I0731 23:53:48.989001   10028 state_mem.go:84] [cpumanager] updated default cpuset: ""
I0731 23:53:48.989048   10028 state_mem.go:92] [cpumanager] updated cpuset assignments: "map[]"
I0731 23:53:48.989099   10028 state_checkpoint.go:100] [cpumanager] state checkpoint: restored state from checkpoint
I0731 23:53:48.989113   10028 state_checkpoint.go:101] [cpumanager] state checkpoint: defaultCPUSet:
I0731 23:53:48.989167   10028 server.go:996] Using root directory: /var/lib/kubelet
I0731 23:53:48.989196   10028 kubelet.go:304] Watching apiserver
I0731 23:53:48.992300   10028 client.go:75] Connecting to docker on unix:///var/run/docker.sock
I0731 23:53:48.992321   10028 client.go:104] Start docker client with request timeout=2m0s
W0731 23:53:48.993291   10028 docker_service.go:561] Hairpin mode set to "promiscuous-bridge" but kubenet is not enabled, falling back to "hairpin-veth"
I0731 23:53:48.993316   10028 docker_service.go:238] Hairpin mode set to "hairpin-veth"
I0731 23:53:49.005086   10028 plugins.go:159] Loaded network plugin "cni"
I0731 23:53:49.005184   10028 docker_service.go:253] Docker cri networking managed by cni
I0731 23:53:49.024706   10028 docker_service.go:258] Docker Info: &{ID:WNWC:6KDT:LUBX:NLE3:HKEG:D6GY:56DN:AIY4:5TZH:IMAZ:FLTB:6XCK Containers:13 ContainersRunning:10 ContainersPaused:0 ContainersStopped:3 Images:9 Driver:aufs DriverStatus:[[Root Dir /var/lib/docker/aufs] [Backing Filesystem extfs] [Dirs 91] [Dirperm1 Supported true]] SystemStatus:[] Plugins:{Volume:[local] Network:[bridge host macvlan null overlay] Authorization:[] Log:[awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog]} MemoryLimit:true SwapLimit:false KernelMemory:true CPUCfsPeriod:true CPUCfsQuota:true CPUShares:true CPUSet:true IPv4Forwarding:true BridgeNfIptables:true BridgeNfIP6tables:true Debug:false NFd:78 OomKillDisable:true NGoroutines:83 SystemTime:2019-07-31T23:53:49.006313622Z LoggingDriver:json-file CgroupDriver:cgroupfs NEventsListener:0 KernelVersion:4.4.0-1052-aws OperatingSystem:Ubuntu 16.04.4 LTS OSType:linux Architecture:x86_64 IndexServerAddress:https://index.docker.io/v1/ RegistryConfig:0xc000763b90 NCPU:2 MemTotal:4142174208 GenericResources:[] DockerRootDir:/var/lib/docker HTTPProxy: HTTPSProxy: NoProxy: Name:sowmya-aws-2-worker-node1 Labels:[provider=amazonec2] ExperimentalBuild:false ServerVersion:18.09.8 ClusterStore: ClusterAdvertise: Runtimes:map[runc:{Path:runc Args:[]}] DefaultRuntime:runc Swarm:{NodeID: NodeAddr: LocalNodeState:inactive ControlAvailable:false Error: RemoteManagers:[] Nodes:0 Managers:0 Cluster:<nil>} LiveRestoreEnabled:false Isolation: InitBinary:docker-init ContainerdCommit:{ID:894b81a4b802e4eb2a91d1ce216b8817763c29fb Expected:894b81a4b802e4eb2a91d1ce216b8817763c29fb} RuncCommit:{ID:425e105d5a03fabd737a126ad93d62a9eeede87f Expected:425e105d5a03fabd737a126ad93d62a9eeede87f} InitCommit:{ID:fec3683 Expected:fec3683} SecurityOptions:[name=apparmor name=seccomp,profile=default]}
I0731 23:53:49.024779   10028 docker_service.go:271] Setting cgroupDriver to cgroupfs
I0731 23:53:49.024869   10028 kubelet.go:632] Starting the GRPC server for the docker CRI shim.
I0731 23:53:49.024887   10028 docker_server.go:59] Start dockershim grpc server
I0731 23:53:49.043945   10028 remote_runtime.go:62] parsed scheme: ""
I0731 23:53:49.043966   10028 remote_runtime.go:62] scheme "" not registered, fallback to default scheme
I0731 23:53:49.043997   10028 remote_image.go:50] parsed scheme: ""
I0731 23:53:49.044012   10028 remote_image.go:50] scheme "" not registered, fallback to default scheme
I0731 23:53:49.044171   10028 asm_amd64.s:1337] ccResolverWrapper: sending new addresses to cc: [{/var/run/dockershim.sock 0  <nil>}]
I0731 23:53:49.044192   10028 clientconn.go:796] ClientConn switching balancer to "pick_first"
I0731 23:53:49.044231   10028 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0xc000569c50, CONNECTING
I0731 23:53:49.044367   10028 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0xc000569c50, READY
I0731 23:53:49.044391   10028 asm_amd64.s:1337] ccResolverWrapper: sending new addresses to cc: [{/var/run/dockershim.sock 0  <nil>}]
I0731 23:53:49.044399   10028 clientconn.go:796] ClientConn switching balancer to "pick_first"
I0731 23:53:49.044419   10028 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0xc000569da0, CONNECTING
I0731 23:53:49.044509   10028 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0xc000569da0, READY
I0731 23:53:49.045474   10028 kuberuntime_manager.go:210] Container runtime docker initialized, version: 18.09.8, apiVersion: 1.39.0
I0731 23:53:49.045650   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/aws-ebs"
I0731 23:53:49.045666   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/empty-dir"
I0731 23:53:49.045676   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/gce-pd"
I0731 23:53:49.045684   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/git-repo"
I0731 23:53:49.045691   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/host-path"
I0731 23:53:49.045699   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/nfs"
I0731 23:53:49.045706   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/secret"
I0731 23:53:49.045718   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/iscsi"
I0731 23:53:49.045727   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/glusterfs"
I0731 23:53:49.045738   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/rbd"
I0731 23:53:49.045745   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/cinder"
I0731 23:53:49.045753   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/quobyte"
I0731 23:53:49.045760   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/cephfs"
I0731 23:53:49.045769   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/downward-api"
I0731 23:53:49.045777   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/fc"
I0731 23:53:49.045784   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/flocker"
I0731 23:53:49.045791   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/azure-file"
I0731 23:53:49.045799   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/configmap"
I0731 23:53:49.045809   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/vsphere-volume"
I0731 23:53:49.045818   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/azure-disk"
I0731 23:53:49.045826   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/photon-pd"
I0731 23:53:49.045836   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/projected"
I0731 23:53:49.045854   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/portworx-volume"
I0731 23:53:49.045862   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/scaleio"
I0731 23:53:49.045870   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/local-volume"
I0731 23:53:49.045878   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/storageos"
I0731 23:53:49.045908   10028 plugins.go:601] Loaded volume plugin "kubernetes.io/csi"
I0731 23:53:49.047002   10028 server.go:1054] Started kubelet
E0731 23:53:49.047063   10028 kubelet.go:1282] Image garbage collection failed once. Stats initialization may not have completed yet: failed to get imageFs info: unable to find data in memory cache
I0731 23:53:49.047392   10028 server.go:141] Starting to listen on <IP_ADDRESS>:10250
I0731 23:53:49.047938   10028 fs_resource_analyzer.go:64] Starting FS ResourceAnalyzer
I0731 23:53:49.047960   10028 status_manager.go:152] Starting to sync pod status with apiserver
I0731 23:53:49.047971   10028 kubelet.go:1806] Starting kubelet main sync loop.
I0731 23:53:49.047996   10028 server.go:343] Adding debug handlers to kubelet server.
I0731 23:53:49.048385   10028 volume_manager.go:246] The desired_state_of_world populator starts
I0731 23:53:49.048392   10028 volume_manager.go:248] Starting Kubelet Volume Manager
F0731 23:53:49.048547   10028 server.go:153] open /etc/kubernetes/ssl/kube-kubelet-xxx.pem: no such file or directory

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.2.6 to master-head
Installation option (single install/HA): HA

This issue is also seen on new clusters created on master builds.
Create a AWS cluster with 1 node having etcd/control plane role and  1 worker node.
Worker node is stuck in "registering" state and kubelet keeps getting restarted.

It happens on:

Nodes having worker role only
Worker nodes provisioned by Rancher. Doesn't happen for custom nodes.

@alena1108 Happens with custom cluster as well , when nodes have  worker role only.

Windows was blocked by this issue. Window node can only be worker role. So there is no way to workaround it.

This is reverted in Rancher (https://github.com/rancher/rancher/pull/21913)

Yes, but we rebased the RKE code today... We also need to change the code in RKE. @thxCode workaround it for now. So we are good.
Thanks @superseb !

@loganhz @superseb so what needs done for this issue? very unclear

The change has been reverted in rancher and rke. It’s good now. We can move it to to-test

Verified by upgrading from v2.2.6 to master-head - commit id: ``
Steps:


R sidecar doesn't work on Windows but works on Mac

Describe the bug
I'm trying to incorporate R v4.3.3 as sidecar into my Tauri app. I basically copied all the files from Program Files where R is installed, particularly from: C:\Program Files\R\R-4.3.3
Reproduction
Here's my tauri.config.json:
{
  "build": {
    "beforeDevCommand": "npm run dev",
    "beforeBuildCommand": "npm run build",
    "devPath": "http://localhost:1420",
    "distDir": "../dist"
  },
  "package": {
    "productName": "xxx",
    "version": "0.0.0"
  },
  "tauri": {
    "allowlist": {
      "notification": {
        "all": true
      },
      "http": {
        "all": true,
        "request": true,
        "scope": ["http://*"]
      },
      "process": {
        "all": false,
        "exit": true,
        "relaunch": true
      },
      "clipboard": {
        "all": true
      },
      "shell": {
        "all": true,
        "execute": true,
        "sidecar": true,
        "open":  true,
        "scope": [
          {
            "name": "binaries/bin/x64/Rscript",
            "sidecar": true
          },
        ]
      },
      "fs": {
        "all": true,
        "scope": ["**"]
      },
      "path": {
        "all": true
      },
      "app": {
        "all": true,
        "show": true,
        "hide": true
      },
      "dialog": {
        "all": true,
        "ask": true,
        "confirm": true,
        "message": true,
        "open": true,
        "save": true
      },
      "os": {
        "all": true
      }
    },
    "windows": [
      {
        "title": "xxx",
        "width": 1200,
        "height": 900
      }
    ],
    "security": {
      "csp": null,
    },
    "bundle": {
      "active": true,
      "targets": "msi",
      "publisher": "xxx",
      "identifier": "xxx",
      "resources": [
        "resources/*"
      ],
      "externalBin": [
        "binaries/bin/x64/Rscript"
      ],
      "icon": [
        "icons/32x32.png",
        "icons/128x128.png",
<EMAIL_ADDRESS>        "icons/icon.icns",
        "icons/icon.ico"
      ]
    }
  }
}

Expected behavior
In one of my *.vue components, I have this JavaScript code:
  const command = Command.sidecar('binaries/bin/x64/Rscript', ["-e", ".libPaths()"]);
  const response = await command.execute();
  console.log(response);

Here's the actual output:
 {
    "code": -1073741515,
    "signal": null,
    "stdout": "",
    "stderr": ""
}

Here's the expected output:
 {
    "code": 0,
    "signal": null,
    "stdout": "[1] \"/src-tauri/binaries/library \"",
    "stderr": ""
}

Full tauri info output
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 122.0.2365.92
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 21.6.1
    - npm: 10.5.0

[-] Packages
    - tauri [RUST]: 1.6.1
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.7
    - @tauri-apps/api [NPM]: 1.5.3
    - @tauri-apps/cli [NPM]: 1.5.11

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite

Stack trace
No response
Additional context
No response

can you try changing the resources config to something like
"resources": [
    "resources/*": "./"
},

This makes sure that the resources are placed next to the R exe and not in a literal resources subdir. You may have to change ./ to something else depending on where R expects its files

can you try changing the resources config to something like
"resources": [
    "resources/*": "./"
},

This makes sure that the resources are placed next to the R exe and not in a literal resources subdir. You may have to change ./ to something else depending on where R expects its files

Sorry, can you clarify how resources dir is connected to the sidecar binaries?
Here's my src-tauri directory structure:
├── src-tauri
│   ├── resources
│   ├── binaries
│   │   ├── bin
│   │   │   ├── x64
│   │   │   │   ├── Rscript.exe
│   ...

Sorry, can you clarify how resources dir is connected to the sidecar binaries?

It was late and i didn't realize that the resources dir and the sidecar dir are different. The train of thought was that i assume that R needs those .dll files to run and those must be next to the executable. Tauri places sidecars at the root of the installdir but resources will have a re-constructed path unless they are directly next to tauri.conf.json or you're doing the ./ thing i showed.
I'd also recommend to install your app, open a terminal and try to run the R exe directly, maybe that gives you a more helpful error then what tauri got 🤷


Refactor object serializer class methods spec

I refactored object_serializer_class_methods_spec.rb with subject, let and shared_example since some of the examples seem to be not well organized... Also, I added some missing test cases and fixed seemingly wrong examples!

I 'm also thinking about integrating object_serializer_set_id_spec.rb and object_serializer_with_attribute_block_spec.rb to this spec file after this PR is marged.


Convert tuple to list, instead of list of tuple.

This PR modifies _to_list to convert a tuple to a list, instead of a list of tuple.
Previous case:
>>> _to_list((1,))
[(1,)]

New case:
>>> _to_list((1,))
[1]

Due to this change, custom layers can return multiple outputs.
class SpecialLayer(Layer):
	def call(self, inputs):
		a = tf.zeros((5, 5))
		b = tf.ones((5, 5))
		return a, b # this is not possible without this PR, only through returning [a, b], but semantically this makes more sense

	def compute_mask(self, inputs, mask=None):
		return [None, None]

The above layer would give an error without this PR:
Traceback (most recent call last):
  File "/tmp/special_layer.py", line 16, in <module>
    a, b = SpecialLayer()([x])
  File "/usr/lib/python3.6/site-packages/tensorflow/contrib/keras/python/keras/engine/topology.py", line 448, in __call__
    arguments=user_kwargs)
  File "/usr/lib/python3.6/site-packages/tensorflow/contrib/keras/python/keras/engine/topology.py", line 502, in _add_inbound_node
    arguments=arguments)
  File "/usr/lib/python3.6/site-packages/tensorflow/contrib/keras/python/keras/engine/topology.py", line 181, in __init__
    self.output_shapes = [K.int_shape(x) for x in output_tensors]
  File "/usr/lib/python3.6/site-packages/tensorflow/contrib/keras/python/keras/engine/topology.py", line 181, in <listcomp>
    self.output_shapes = [K.int_shape(x) for x in output_tensors]
  File "/usr/lib/python3.6/site-packages/tensorflow/contrib/keras/python/keras/backend.py", line 618, in int_shape
    shape = x.get_shape()
AttributeError: 'tuple' object has no attribute 'get_shape'

EDIT: It appears to have broken some tests. I'll check this out.

Nevermind, I forgot to define compute_output_shape.


#28: Enrich network logs with connection tag ([name:]host:port).

During debugging the issue #28 in real application where multiple clients are used I've found it valuable to have network logs annotated with connection_name, host and port to understand the conditions where issue occur. In this MR I'm adding notion of tag which is something that is logged in each log message and by default is a combination of connection_name:host:port or host:port.

Opps, accidentally created MR from wrong account, but anyway it is valid proposal.

Thank you :)


Delay property substitution

Fixes https://github.com/coursier/coursier/issues/2906

Includes https://github.com/coursier/coursier/pull/3097 for now

Still got to think about how this fixes things, and possibly about cleaning up the code that's been changed…


Logstash SNS Output to goaws SNS topic in Docker

I have docker running goaws and i added a separate container running a python daemon that i wrote. The python daemon reads from the SQS endpoint i have subscribed to my SNS topic and does a POST to a webapp in another docker container running tomcat. All of this works perfectly in one docker-compose.yml. I can publish a message directly to my goaws SNS topic using the python publish API and i recieve the output in elasticsearch which is after my webapp. I view the elasticsearch cluster in Kibana (yet another container I have running).
I wanted to take things a step further and add Logstash to the stack in docker. I cant get logstash SNS output plugin to send a messsage to the goaws SNS topic. It wants to send it to sns.us-east-1.amazonaws.com which I dont have credentials for. Do you have any idea what is causing this issue?

@jcksnvllxr80 I am not sure but I imagine that this is a logstash limitation (or there could be an 'endpoint' configuration for the logstash plugin?


AES encryption

I was messing about with some bluetooth smart devices, and they use aes 128 encryption. Does the Bangle have an implementation of AES?

typeof AES.encrypt
Uncaught ReferenceError: "AES" is not defined
at line 1 col 11
It seems bangle does not have AES support by default
require("crypto") also does not help. https://www.espruino.com/modules/crypto.js here on only SHA1 implementation

Yes I saw this old thread regarding the Puck, and assumed they had the same features  http://forum.espruino.com/conversations/319871/

Bangle.js doesn't have the implementation I'm afraid. Adding it would be as simple as adding it to the BANGLEJS.py and rebuilding but it's likely other features (tensorflow?) would have to be removed to make space.

crypto.js

Yes, the AES implementation is part of the firmware and is written in C. The JS file there is just a filler for devices that don't even have the crypto lib but want SHA1
Any chance you can ask these kinds of questions in the forum in future? Otherwise it gets hard to figure out which issues actually need stuff doing on them


sigslot::signal2<cricket::TransportChannel*, rtc::SentPacket const&, sigslot::single_threaded> crash

One of the crashes referenced in #74.
sigslot-signal2 crash.txt

Folded into #74


Remove function

Proposed changes
Implemented remove function. remove() passes a lambda expression into remove_if() then returns.
Implemented remove_if(), remove_if() takes a boolean function as a parameter then iterates through the list removing elements that return true when passed into the predicate.
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] Unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Codecov Report

Merging #45 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master    #45    +/-   ##
======================================
  Coverage     100%   100%
======================================
  Files           5      5
  Lines         408    512   +104
======================================
+ Hits          408    512   +104

Impacted Files
Coverage Δ

tests/linkedListTest.cpp
100% <100%> (ø)
:arrow_up:

src/linkedList.cpp
100% <100%> (ø)
:arrow_up:

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 b8bea68...29624bd. Read the comment docs.

For sure, I'll add some more tests. And yes, I need to pull the latest gitignore onto this branch before I merge. Also, you're right, I'm not sure why my changes collectively merged onto this commit as I was checking out branches along the way. I'll have to resolve the conflicts then merge it all once I get home.

And no, reversing the list with only one element shouldn't result in a seg fault as the head will still point to a nullptr. However, I will write a test for that and commit it before I push. Thanks for the tip.

Oh I'm sure reverse works fine, my point was we want the tests to reflect that.


Failed to resolve component 'esp_tls' (IDFGH-13798)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.3.1
Operating System used.
Linux
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
What is the expected behavior?
build
What is the actual behavior?

Executing task: ninja

[0/1] Re-running CMake...
-- git rev-parse returned 'fatal: не найден git репозиторий (или один из его каталогов вплоть до точки монтирования /run/media/vadiki)
Останавливаю поиск на границе файловой системы (так как GIT_DISCOVERY_ACROSS_FILESYSTEM не установлен).'
-- Could not use 'git describe' to determine PROJECT_VER.
-- Building ESP-IDF components for target esp32s3
Processing 2 dependencies:
[1/2] joltwallet/littlefs (1.14.8)
[2/2] idf (5.4.0)
CMake Error at /home/vadiki/esp/esp-idf/tools/cmake/build.cmake:298 (message):
Failed to resolve component 'esp_tls' required by component 'my_WiFi':
unknown name.
Call Stack (most recent call first):
/home/vadiki/esp/esp-idf/tools/cmake/build.cmake:341 (__build_resolve_and_add_req)
/home/vadiki/esp/esp-idf/tools/cmake/build.cmake:644 (__build_expand_requirements)
/home/vadiki/esp/esp-idf/tools/cmake/project.cmake:710 (idf_build_process)
CMakeLists.txt:8 (project)
-- Configuring incomplete, errors occurred!
FAILED: build.ninja
/usr/bin/cmake --regenerate-during-build -S/run/media/vadiki/250_GB_ST_1GB/projects/filamentor_v2/program/filamentor_v2 -B/run/media/vadiki/250_GB_ST_1GB/projects/filamentor_v2/program/filamentor_v2/build
ninja: error: rebuilding 'build.ninja': subcommand failed

The terminal process "ninja" terminated with exit code: 1.

Steps to reproduce.

#include "esp_tls"
build

Build or installation Logs.
*  Executing task: ninja

[0/1] Re-running CMake...
-- git rev-parse returned 'fatal: не найден git репозиторий (или один из его каталогов вплоть до точки монтирования /run/media/vadiki)
Останавливаю поиск на границе файловой системы (так как GIT_DISCOVERY_ACROSS_FILESYSTEM не установлен).'
-- Could not use 'git describe' to determine PROJECT_VER.
-- Building ESP-IDF components for target esp32s3
Processing 2 dependencies:
[1/2] joltwallet/littlefs (1.14.8)
[2/2] idf (5.4.0)
CMake Error at /home/vadiki/esp/esp-idf/tools/cmake/build.cmake:298 (message):
  Failed to resolve component 'esp_tls' required by component 'my_WiFi':
  unknown name.
Call Stack (most recent call first):
  /home/vadiki/esp/esp-idf/tools/cmake/build.cmake:341 (__build_resolve_and_add_req)
  /home/vadiki/esp/esp-idf/tools/cmake/build.cmake:644 (__build_expand_requirements)
  /home/vadiki/esp/esp-idf/tools/cmake/project.cmake:710 (idf_build_process)
  CMakeLists.txt:8 (project)

-- Configuring incomplete, errors occurred!
FAILED: build.ninja
/usr/bin/cmake --regenerate-during-build -S/run/media/vadiki/250_GB_ST_1GB/projects/filamentor_v2/program/filamentor_v2 -B/run/media/vadiki/250_GB_ST_1GB/projects/filamentor_v2/program/filamentor_v2/build
ninja: error: rebuilding 'build.ninja': subcommand failed

 *  The terminal process "ninja" terminated with exit code: 1.

More Information.
No response

Hello @sova32 , shouldn't the component name be esp-tls, with the dash instead of underscore? Could you please check that my_WiFi has esp_tls in requirements?
$ git ls-tree v5.3.1 components/ | grep tls
040000 tree 4d77415b832f8365d739e9f5232b241c4d420031	components/esp-tls
040000 tree c3f1dfdad57a4ed4ba9db9f3c9d2a0c7293e907b	components/mbedtls

Hello @sova32 , shouldn't the component name be esp-tls, with the dash instead of underscore? Could you please check that my_WiFi has esp-tls in requirements?

Yes if you see build output it shows that error:
  Failed to resolve component 'esp_tls' required by component 'my_WiFi':   unknown name.
It should be named as esp-tls


Groups: Auto-join after creation

Groups creator is already automatically invited, so he/she only need to click join without confirmation.


Develop Moderator's Guide

Develop Moderator's Guide for Usability Testing of initial AMPD wireframes.

Open Ticket @areighar @kstetsyuk @tlageman-epa

Open Ticket @areighar @kstetsyuk @tlageman-epa

Ming and Jeremy peer approval  02/09/2021


Not working with extends

It's not working with the defined @JsonMembers of the parent class.
Is there any options to be able to use the defined members of the parents class?
Best regards
Dominic

Hi, @DominicBoettger
TypedJSON is supposed to work with inheritance, properties decorated with JsonMember are inherited regarding serialization/deserialization. So far, I found no issues involved with this aspect. If you can post the relevant portions of your code, I'll do my best to try and help you out.

Did you add JsonObject to the derived class and the parent class?

I think something was wrong with my typescript compiler. Today i tried it again and it worked without any problems. Thanks for your help!

I'm glad you got it sorted out. There is a latent issue I occasionally encountered previously though, and it's possible you are facing the same problem: if you are using Visual Studio and you configure your project to Build on Save, the output produced on save will sometimes contain (or not contain?) something that breaks the entire functionality of TypedJSON. Manual building/rebuilding would solve make it go away.
I didn't investigate, as the issue was rare at most, but it could be the same as what you were facing.


feat(ecs): add requestsErrorRateThreshold prop

I am getting a lot of alarms when bots poke endpoints that don't exist.

@losnappas seems like API.md should be updated


Integrating Braze

In the native SDK, it is possible to add destinations, including Braze.
How can this be achieved with the Flutter lib?

Hi @lironzemingo you for your report, we start looking into this.

It is possible to write custom plugins.
We don't have in our plans yet to write a Braze plugin but if it's something the community wants we will prioritize.
Changing this as an enhancement. Contributions are accepted. Feel free to add a reaction too to measure how big of an audience is there for this plugin!


Scenario Steps have a redundant HasActed() flag; think about it!

It's a hassle that the flag must be set by the user by calling SetActed within Act reimplementation.

Rwmoved the HasActed flag


Search a 2D Matrix (sorted from left to right)

Type
Algorithm
Directory
Algorithm => Matrix-Algorithm
Description
Need Efficient solution
Programming Language

[ ] c++
[ ] c
[ ] python
[ ] java
[ ] kotlin
[ ] javascript
[ ] typescript
[ ] c#
[ ] swift
[ ] ruby
[ ] scala
[ ] go
[ ] php
[ ] haskell
[ ] bash

Comment In The Stated Syntax

Language In Which You Will Contribute => Time Required By You To Push The Changes
Ask for the issue that you plan to complete.
Do not wait to get assigned.
Please try to push the changes in less than or equal to the stated(by you only) time period. Failing to do that, your comment will be discarded and the language will be made available to other participants.
Try to avoid any casual communication.

Can u assign this issue to me? Thank you

Java => 1 Day

c++ => 1 day

Python=>2 hours


3rd party plugins

How do you install plugins for freeboard.io??
I'm assuming you put a link into the developer console? But this has not worked for me..
In particular, I would like to install this widget to my freeboard.io
https://github.com/daleroy1/freeboard-widget-rag

Bryan
Did you find answer on this topic?
Peter

Not yet, but I have opened up an issue with that particular plugin
https://github.com/daleroy1/freeboard-widget-rag/issues/3

fyi the solution here is to push the raw git code through a site such as http://rawgit.com/


linguist-language git attribute has no effect

Preliminary Steps
Please confirm you have...

[x] reviewed How Linguist Works,
[x] reviewed the Troubleshooting docs,
[x] considered implementing an override,
[x] verified an issue has not already been logged for your issue (linguist issues).

Problem Description
Hi,
Not a very important issues, but still...
I've set linguist-language=C++ in .gitattributes but GitHub still classifies some matching files as C instead of C++.
.gitattributes: https://github.com/roc-project/roc/blob/master/.gitattributes
checking that it works:
$ git check-attr -a src/modules/roc_core/helpers.h
src/modules/roc_core/helpers.h: linguist-language: C++

$ git check-attr -a src/modules/roc_core/target_posix/roc_core/stddefs.h
src/modules/roc_core/target_posix/roc_core/stddefs.h: linguist-language: C++

Problematic files: https://github.com/roc-project/roc/search?l=c

URL of the affected repository:
https://github.com/roc-project/roc
Last modified on:
.gitattributes file was pushed a couple weeks ago
Expected language:
C++
Detected language:
C

So, this gets "fun"... you're experiencing a caching behaviour of the search system. The search results are independent from Linguist when it comes to indexing and caching and will lag behind changes detailed in .gitattributes as the search index entry for a particular file isn't updated until you modify that file again.
In the example you've shown, the two files were last indexed before you made your .gitattributes - note the "Last indexed on Feb 24" after each file name. Both of those files were modified around this time. Your .gitattributes file was however only modified on 31 May 2019 long after these files were last changed. In order for the search results to reflect this change, you'll need to push a change to the files.
As for .gitattributes not having an effect... it most definitely is. You've only marked some of the files Linguist determines as C as C++.
If we run Linguist against a clone of your repo we see these are the files still being identified as C and they make up the 6.5% you see in the language bar:
$ github-linguist ~/tmp/trash/roc --breakdown
83.63%  C++
9.22%   Python
6.50%   C
0.65%   Shell

Python:
SConstruct
scripts/3rdparty.py
[... truncated for brevity ...]

Shell:
scripts/travis/docker.sh
[... truncated for brevity ...]

C:
src/lib/example/receiver_sox.c
src/lib/example/sender_sinewave.c
src/lib/include/roc/address.h
src/lib/include/roc/config.h
src/lib/include/roc/context.h
src/lib/include/roc/frame.h
src/lib/include/roc/log.h
src/lib/include/roc/platform.h
src/lib/include/roc/receiver.h
src/lib/include/roc/sender.h
src/pulse/module-roc-sink-input.c
src/pulse/module-roc-sink.c
src/pulse/module_helpers.c
src/pulse/module_helpers.h

C++:
src/lib/src/address.cpp
src/lib/src/config.cpp
src/lib/src/context.cpp
src/lib/src/log.cpp
src/lib/src/private.h
src/lib/src/receiver.cpp
src/lib/src/sender.cpp
src/modules/roc_audio/depacketizer.cpp
src/modules/roc_audio/depacketizer.h
src/modules/roc_audio/frame.cpp
[... truncated for brevity ...]

$

As you can see, none of those C files match your .gitattributes, hence Linguist will do its thing and determine the language itself.

Ah, I see. Thanks for a detailed explanation!

In order for the search results to reflect this change, you'll need to push a change to the files.

BTW, It would probably make sense to automatically reindex files on .gitattributes change too...
Anyway that's not an issue for me, so feel free to close this if it's not considered as a bug.

BTW, It would probably make sense to automatically reindex files on .gitattributes change too...

It would and is quite a common request from Linguist, however it's much easier said than done from a search and repo perspective - it also affects syntax highlighting which uses the blob for caching independent of the .gitattrbutes file. The search and repo teams are well aware of this issue and it is on their radars, but not very high in priority.

Closing as this is a known limitation that Linguist has no control over.


Fixed size array, or disable the 'x', '+', and '-' buttons?

I'm creating a configuration page for a hardware device that has a fixed number of pins. It looks like jsonform is fully capable of creating the form I need. The only thing I haven't found is how to make array objects a fixed size. Since the number of pins on my hardware is fixed I'd like to remove all the options that resize the array.
Thanks for all your hard work. I'm not a web developer by any stretch of the imagination, so I wouldn't have been able to get such an advanced form without this library.

Hi Will,
Try to use readonly property with the form item, or, if you allow user to
edit, use
minItems and maxItems with the array size you want in your json schema.
2017-01-23 23:44 GMT+08:00 Will Winder<EMAIL_ADDRESS>
I'm creating a configuration page for a hardware device that has a fixed
number of pins. It looks like jsonform is fully capable of creating the
form I need. The only thing I haven't found is how to make array objects a
fixed size. Since the number of pins on my hardware is fixed I'd like to
remove all the options that resize the array.
Thanks for all your hard work. I'm not a web developer by any stretch of
the imagination, so I wouldn't have been able to get such an advanced form
without this library.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/joshfire/jsonform/issues/162, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKsHZ2hCGqYjoMzwkVz_rCjOOLxKMX2ks5rVMrkgaJpZM4LrMen
.

--
Ulion

Perfect, thanks!